HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
150 # Display the sFlow configuration and operation information. [Device-GigabitEthernet1/0/1] display sflow sFlow Version: 5 sFlow Global Information: Agent IP:3.3.3.1 Collector Information: ID IP Port Aging Size Descript\ ion 1 6343 0 1400 2 3.3.3.2 6543 N/A 1400 netserve\ r 3 6343 0 1400 4 6343 0 1400 5 6343 0 1400 6 6343 0 1400 7 6343 0 1400 8 6343 0 1400 9 6343 0 1400 10 6343 0 1400 sFlow Port Information: Interface CID Interval(s) FID MaxHLen Rate Mode Status GE1/0/1 2 120 2 128 4000 Random Active The output shows that GigabitEthernet 1/0/1 enabled with sFlow is active, the counter sampling interval is 120 seconds, the Flow sampling interval is 4000, all of which indicate sFlow operates normally. Troubleshooting sFlow configuration Symptom The remote sFlow collector cannot receive sFlow packets. Analysis • The sFlow collector has no IP address specified. • No interface is enabled with sFlow to sample data. • The IP address of the sFlow collector specified on the sFlow agent is different fr om that of the remote sFlow collector. • No IP address is configured for the Layer 3 interface on the device, or the IP address is configured, but the UDP packets with the IP address being the source cannot reach the sFlow collector. • The physical link between the devi ce and the sFlow collector fails. Solution 1. Check whether sFlow is correctly configured by displaying sFlow configuration with the display sflow command. 2. Check whether the correct IP address is configured for the device to communicate with the sFlow collector. 3. Check whether the physical link between the device and the sFlow collector is normal.
151 Configuring IPC This chapter provides an overview of IPC and describes the IPC monitoring commands. Overview Inter-Process Communication (IPC) provides a reliable communication mechanism among processing units, typically CPUs. IPC is typically used on a distributed device or in an IRF fabric to provide reliable inter-card or inter-device transmission. This section describes the basic IPC concepts. Node An IPC node is an independent IPC-capable processing unit, typically, a CPU. This series of devices are centralized devices that have only one CPU. The IRF fabrics formed by them have multiple CPUs, or IPC nodes. Link An IPC link is a connection between any two IPC nodes. Any two IPC nodes have one and only one IPC link for sending and receiving packets. All IPC nodes are fully meshed. IPC links are created when the system is initialized. An IPC node, upon startup, sends handshake packets to other nodes. If the handshake su cceeds, a connection is established. The system uses link status to identify the link connectivity between two nodes. An IPC node can have multiple links, and each link has its own status. Channel A channel is the communication interface between peer upper layer application modules that use different IPC nodes. Each node assigns a locally uniq ue channel number to each upper layer application module for identification. An upper layer application module sends data to an IPC module in a channel, and the IPC module sends the data to a peer node across a link, as shown in Figure 54.
152 Figure 54 Relationship between a node, link and channel Packet sending modes IPC uses one of the following modes to send packets for upper layer application modules: • Unicast —One node sends packets to another node. • Multicast —One node sends packets to multiple nodes. This mode includes broadcast, a special multicast. To use multicast mode, an application module must create a multicast group that includes a set of nodes. Multicasts destined for this group are sent to all the nodes in the group. An application module can create multiple multicast groups. Creation and deletion of a multicast group or group member depend on the application module. • Mixcast —Supports both unicast and multicast. IPC assigns one queue for each mode. An upper layer application module automatically selects one mode as needed. Enabling IPC performance statistics The IPC performance statistics function provides the mo st recent 10-second, 1-minute, and 5-minute traffic input and output statistics for IPC node s. If this function is disabled, the display ipc performance command displays the statistics collected before IPC performance statistics was disabled. To enable IPC performance statistics: Task Command Remarks Enable IPC performance statistics in user view. ipc performance enable { node node-id | self-node } [ channel channel-id ] By default, the function is disabled. LinkCh an ne l 2
153 Displaying and maintaining IPC Task Command Remarks Display IPC node information. display ipc node [ | { begin | exclude | include } regular-expression ] Available in any view Display channel information for a node. display ipc channel { node node-id | self-node } [ | { begin | exclude | include } regular-expression ] Available in any view Display queue information for a node. display ipc queue { node node-id | self-node } [ | { begin | exclude | include } regular-expression ] Available in any view Display multicast group information for a node. display ipc multicast-group { node node-id | self-node } [ | { begin | exclude | include } regular-expression ] Available in any view Display packet information for a node. display ipc packet { node node-id | self-node } [ | { begin | exclude | include } regular-expression ] Available in any view Display link status information for a node. display ipc link { node node-id | self-node } [ | { begin | exclude | include } regular-expression ] Available in any view Display IPC performance statistics of a node. display ipc performance { node node-id | self-node } [ channel channel-id ] [ | { begin | exclude | include } regular-expression ] Available in any view Clear IPC performance statistics of a node. reset ipc performance [ node node-id | self-node ] [ channel channel-id ] Available in user view
154 Configuring PoE Overview Power over Ethernet (PoE) enables a power sourcing equipment (PSE) to supply power to powered devices (PDs) through Ethernet inte rfaces over twisted pair cables. Advantages • Reliable —Power is supplied in a centralized way so that it is very convenient to provide a backup power supply. • Easy to connect — A n e t wo rk t e r m i n a l re q u i re s n o ex t e r n a l power supply but only an Ethernet cable. • Standard—In compliance with IEEE 802.3af, and a globally uniform power interface is adopted. • Promising —It can be applied to IP telephones, wireless LAN access points (APs), portable chargers, card readers, web cameras, and data collectors. PoE concepts As shown in Figure 55, a P oE system comprises PoE power, PSE, power interface (PI), and PD: • Po E p owe r —The whole PoE system is powered by the PoE power. • PSE—A PSE supplies power for PDs. A PSE can examine the Ethernet cables connected to PoE interfaces, search for PDs, classify them, and supply power to them. When detecting that a PD is unplugged, the PSE stops supplying power to the PD. A PSE can be built-in (Endpoint) or external (Midspan). The switch uses built-in PSEs. To display the mapping between a PSE ID and the slot number of an interface card, execute the display poe device command. The PSE ID is the switch member ID × 3 + 1. For example, if the member ID of the device is 3, the PSE ID of the device is 3 × 3 + 1 = 10. • PI—An Ethernet interface with the PoE capability is called PoE interface. • PD—A PD accepts power from the PSE, including IP phones, wireless APs, chargers of portable devices, POS, and web cameras. The PD that is being powered by the PSE can be connected to another power supply unit for redundancy power backup. Figure 55 PoE system diagram Protocol specification The protocol specification related to PoE is IEEE 802.3af.
155 PoE configuration task list You can configure a PoE interface by using either of the following methods: • At the command line interface (CLI). • Through configuring the PoE profile and applying the PoE profile to the PoE interface. To configure a single PoE interface, configure it at th e CLI. To configure PoE interfaces in batches, use the PoE profile. For a PoE configuration parameter of a PoE interface, you can only select one mode (including modification and removal of a PoE interface). Configuration guidelines • Before configuring PoE, make sure the PoE power supply and PSE are operating normally. Otherwise, you cannot configure PoE or the configured PoE function does not take effect. • Turning off the PoE power supply during the startup of the device might cause the PoE configuration in the PoE profile invalid. Complete these tasks to configure PoE: Task Remarks Enabling PoE: Enabling PoE for a PoE interface Required. Detecting PDs: Enabling the PSE to detect nonstandard PDs Optional. Configuring a PD disconnection detection mode Optional. Configuring the PoE power: Configuring the maximum PoE interface power Optional. Configuring PoE power management: Configuring PoE interface power management Optional. Configuring the PoE monitoring function: Configuring PSE power monitoring Optional. Monitoring PD Optional. The device automatically monitors PDs when supplying power to them, so no configuration is required. Configuring PoE interface through PoE profile: Configuring PoE profile Optional. Applying PoE profile Optional. Upgrading PSE processing software in service Optional.
156 Enabling PoE Enabling PoE for a PoE interface The system does not supply power to or reserve power for the PDs connected to a PoE interface if the PoE interface is not enabled with the PoE function. You are allowed to enable PoE for a PoE interface if the PoE interface will not result in PoE power overload; otherwise, whether you can enable PoE for the PoE interface depends on whether the PoE interface is enabled with the PoE power management function. For more information about the PoE interface power management function, see Configuring PoE interface power management . • If the P oE interface is not enabled with the PoE power management function, you are not allowed t o e n a b l e Po E f o r t h e Po E i n t e r f a c e. • If the PoE interface is enabled with the PoE power management function, you are allowed to enable PoE for the PoE interface (whether the PDs can be powered depends on other factors, for example, the power supply priority of the PoE interface). The PSE supplies power over category 3/5 twisted pair cable for a PoE interface in the following modes: • Over signal wires —The PSE uses data pairs (pins 1, 2 and 3, 6) to supply DC power to PDs. • Over spare wires —The PSE uses spare pairs (pins 4, 5 and 7, 8) to supply DC power to PDs. Configuration guidelines • When the sum of the power consumption of all powered PoE interfaces on a PSE exceeds the maximum power of the PSE, the system considers the PSE overloaded (The maximum PSE power is decided by the user configuration). • A PSE can supply power to a PD only when the selected power supply mode is supported by both the PSE and PD. If the PSE and PD support differen t power supply modes (for example, the PSE does not support power over spare wires, while the PD supports power over spare wires), you have to change the order of the lines in the twisted pair cable to supply power to the PD. • The switchs PoE interfaces can supply power only over signal wires. To e n a b l e Po E f o r a Po E i n t e r f a c e : Step Command Remarks 1. Enter system view. system-view N/A 2. Enter PoE interface view. interface interface-type interface-number N/A 3. Enable PoE for the PoE interface. poe enable By default, this function is disabled. 4. Configure a description for the PD connected to the PoE interface. poe pd-description text Optional. By default, no description for the PD connected to the PoE interface is available.
157 Detecting PDs Enabling the PSE to detect nonstandard PDs There are standard PDs and nonstandard PDs. Usually, the PSE can detect only standard PDs and supply power to them. The PSE can detect nonstandard PDs and supply power to them only after the PSE is enabled to detect nonstandard PDs. To enable the PSE to detect nonstandard PDs: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable the PSE to detect nonstandard PDs. poe legacy enable pse pse-id By default, the PSE can detect standard PDs rather than non standard PDs. Configuring a PD disconnection detection mode To detect the PD connection with PSE, PoE provides two detection modes: AC detection and DC detection. The AC detection mode is energy saving relative to the DC detection mode. To configure a PD disconnection detection mode: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure a PD disconnection detection mode. poe disconnect { ac | dc } Optional. The default PD disconnection detection mode is AC detection. If you change the PD disconnection detection mode when the device is running, the connected PDs will be powered off. Therefore, be cautious to do so. Configuring the PoE power Configuring the maximum PoE interface power The maximum PoE interface power is the maximum po wer that the PoE interface can provide to the connected PD. If the power required by the PD is larger than the maximum PoE interface power, the PoE interface will not supply power to the PD. For HP 5500-48G-PoE+ EI Switch with 2 Interface Slots(JG240A), HP 5500-48G-PoE+ EI TAA Switch with 2 Interface Slots(JG253A), and HP 5500-48G-PoE+ SI Switch with 2 Interface Slots(JG239A), the total PoE power of ports numbered 1 through 24 is 370 W, and that of ports numbered 25 through 48 is 370 W. To configure the maximum PSE power:
158 Step Command Remarks 1. Enter system view. system-view N/A 2. Enter PoE interface view. interface interface-type interface-number N/A 3. Configure the maximum power for the PoE interface. poe max-power max-power Optional. By default, 30000 milliwatts is the maximum power for the PoE interface for PoE+ switches. Configuring PoE power management PoE power management involves PSE power management and PoE interface power management. Configuring PoE interface power management The power supply priority of a PD depends on the priority of the PoE interface. The priority levels of PoE interfaces are critical, high and low in descending or der. Power supply to a PD is subject to PoE interface power management policies. All PSEs implement the same PoE interface power ma nagement policies. When a PSE supplies power to a PD, the following actions occur: • If the PoE interface power management is not en abled, no power will be supplied to a new PD when the PSE power is overloaded. • If the PoE interface power management priority policy i s e n a b l e d , t h e P D w i t h a l o w e r p r i o r i t y i s f i r s t powered off to guarantee the power supply to the PD with a higher priority when the PSE power is overloaded. 19 watts guard band is reserved for each PoE interface on the device to prevent a PD from being powered off because of a sudden increase of the PD power. When the remaining power of the PSE where the PoE interface resides is lower than 19 watts and no priority is configured for the PoE interface, the PSE does not supply power to the new PD; when the remaining power of the PSE where the PoE interface resides is lower than 19 watts, but priority is configured for the PoE interface, the interface with a higher priority can preempt the power of the interface with a lower priority to ensure the normal working of the higher priority interface. If the sudden increase of the PD power results in PSE power overload, power supply to the PD on the PoE interface with a lower priority will be stopped to ensure the power supply to the PD with a higher priority. If the guaranteed remaining PSE power (the maximum PSE power minus the power allocated to the critical PoE interface, regardless of whether PoE is enabled for the PoE interface) is lower than the maximum power of the PoE interface, you will fail to set the priority of the PoE interface to critical. Otherwise, you can succeed in setting the priority to critical, and this PoE interface will preempt the power of other PoE interfaces with a lower priority level. In the latter case, the PoE interfaces whose power is preempted will be powered off, but their configurations will remain unchanged. When you change the priority of a PoE interface from critical to a lower level, the PDs connecting to other PoE interfaces will have an opportunity of being powered. Configuration prerequisites Enable PoE for PoE interfaces.
159 Configuration procedure To configure PoE interface power management: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure PoE interface power management priority policy. poe pd-policy priority By default, this policy is not configured. 3. Enter PoE interface view. interface interface-type interface-number N/A 4. Configure the power supply priority for a PoE interface. poe priority { critical | high | low } Optional. By default, low is the power supply priority for the PSE. Configuring the PoE monitoring function With the PoE monitoring function enabled, the system monitors the parameter values related to PoE power supply, PSE, PD, and device temperature in real time. When a specific value exceeds the limited range, the system automatically take s some measures to protect itself. Configuring PSE power monitoring When the PSE power exceeds or drops below the specified threshold, the system sends trap messages. To configure a power alarm threshold for the PSE: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure a power alarm threshold for the PSE. poe utilization-threshold utilization-threshold-value pse pse-id Optional. The default setting is 80%. Monitoring PD When a PSE starts or ends power supply to a PD, the system sends a trap message. Configuring PoE interface through PoE profile You can configure a PoE interface either at the CLI or by using a PoE profile and applying the PoE profile to the specified PoE interface(s). To configure a single PoE interface, configure it at the CLI; to configure PoE interfaces in batches, use a Po E p ro fi l e. A PoE profile is a collection of configurations that contain multiple PoE features. On large-scale networks, you can apply a PoE profile to multiple PoE interfaces , and these interfaces have the same PoE features. If the PoE interface connecting to a PD changes to another one, apply the PoE profile applied on the