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+.
![Page 2463
162
Task Command Remarks
Display the power supply
states of all PoE interfaces
connected to the PSE. display poe pse
pse-id interface [ | { begin |
exclude | include } regular-expression ] Available in any view
Display power information for
all PoE interfaces connected to
the PSE. display
poe pse pse-id interface power [ | { begin |
exclude | include } regular-expression ] Available in any view
Display the configurations and
applications of the PoE profile. display
poe...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2462.png "Page 2463
162
Task Command Remarks
Display the power supply
states of all PoE interfaces
connected to the PSE. display poe pse
pse-id interface [ | { begin |
exclude | include } regular-expression ] Available in any view
Display power information for
all PoE interfaces connected to
the PSE. display
poe pse pse-id interface power [ | { begin |
exclude | include } regular-expression ] Available in any view
Display the configurations and
applications of the PoE profile. display
poe...")
![Page 2464
163
[Sysname-GigabitEthernet1/0/1] quit
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] poe enable
[Sysname-GigabitEthernet1/0/2] poe priority critical
[Sysname-GigabitEthernet1/0/2] quit
[Sysname] interface gigabitethernet 1/0/3
[Sysname-GigabitEthernet1/0/3] poe enable
[Sysname-GigabitEthernet1/0/3] poe priority critical
[Sysname-GigabitEthernet1/0/3] quit
# Enable PoE on GigabitEthernet 1/0/1 1 and GigabitEthernet 1/0/12, and configure the maximum
power of...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2463.png "Page 2464
163
[Sysname-GigabitEthernet1/0/1] quit
[Sysname] interface gigabitethernet 1/0/2
[Sysname-GigabitEthernet1/0/2] poe enable
[Sysname-GigabitEthernet1/0/2] poe priority critical
[Sysname-GigabitEthernet1/0/2] quit
[Sysname] interface gigabitethernet 1/0/3
[Sysname-GigabitEthernet1/0/3] poe enable
[Sysname-GigabitEthernet1/0/3] poe priority critical
[Sysname-GigabitEthernet1/0/3] quit
# Enable PoE on GigabitEthernet 1/0/1 1 and GigabitEthernet 1/0/12, and configure the maximum
power of...")
160
originally connected interface to the currently connected interface instead of reconfiguring the features
defined in the PoE profile one by one, simplifying the PoE configurations.
The device supports multiple PoE profiles. You can define PoE configurations based on each PD, save the
configurations for different PDs into different PoE profiles, and apply the PoE profiles to the access
interfaces of PDs accordingly.
Configuration guidelines
• If a PoE profile is applied, it cannot be delete d or modified before you cancel its application.
• The poe max-power max-power and poe priority { critical | high | low } commands must be
configured in only one way, that is, either at the CLI or by configuring PoE profile.
• A PoE parameter on a PoE interface must be configured, modified and deleted in only one way. If
a parameter configured in a way (for example, at th e CLI) is then configured in the other way (for
example, through PoE profile), the latter configuratio n fails and the original one is still effective. To
make the latter configuration effective, you must cancel the original one first.
Configuring PoE profile
Step Command Remarks
1. Enter system view.
system-view N/A
2. Create a PoE profile, and
enter PoE profile view. poe-profile
profile-name [ index ] N/A
3. Enable PoE for the PoE
interface. poe enable
By default, this function is disabled.
4. 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.
5.
Configure power supply
priority for the PoE interface. poe priority
{ critical | high | low }
Optional.
By default, low is the power supply
priority for the PoE interface.
Applying PoE profile
You can apply a PoE profile in either system view or interface view. If you perform application to a PoE
interface in both views, the latter application takes ef fect. To apply a PoE profile to multiple PoE interfaces,
the system view is more efficient.
To apply the PoE profile in system view:
Step Command
1. Enter system view.
system-view
2. Apply the PoE profile to one or multiple PoE
interfaces. apply poe-profile
{ index index | name profile-name }
interface interface-range
To apply the PoE profile in interface view:
161
Step Command
1. Enter system view.
system-view
2. Enter PoE interface view.
interface interface-type interface-number
3. Apply the PoE profile to the current PoE interface. apply poe-profile { index index | name profile-name }
A PoE profile can be applied to multiple PoE interfaces, while a PoE interface can be applied with only
one PoE profile.
Upgrading PSE processing software in service
You can upgrade the PSE processing software in service in either of the following two modes:
• refresh mode —Enables you to update the PSE processing software without deleting it. Normally,
you can upgrade the PSE processing software in the refresh mode through the command line.
• full mode —Deletes the PSE processing software and relo ads it. If the PSE processing software is
damaged (in this case, you can execute none of PoE commands successfully), you can upgrade the
PSE processing software in full mode to restore the PSE function.
An in-service PSE processing software upgrade may be unexpectedly interrupted (for example, an error
results in device reboot). If you fail to upgrade the PSE processing software in full mode after reboot, you
can power off the device and restart it before upgrading it in full mode again. After upgrade, restart the
device manually to make the new PSE processing software take effect.
Configuration guidelines
To upgrade the PSE processing software in service:
Step Command
1. Enter system view.
system-view
2. Upgrade the PSE processing software in service. poe update { full | refresh } filename pse pse-id
Displaying and maintaining PoE
Task Command Remarks
Display PSE information. display poe device
[ | { begin | exclude | include }
regular-expression ] Available in any view
Display the power supplying
state of the specified PoE
interface. display poe interface
[ interface -type
interface-number ] [ | { begin | exclude | include }
regular-expression ] Available in any view
Display power information for
PoE interfaces. display poe interface power
[ interface-type
interface-number ] [ | { begin | exclude | include }
regular-expression ] Available in any view
Display information about PSE.
display poe pse [ pse
-id ] [ | { begin | exclude |
include } regular-expression ] Available in any view
162
Task Command Remarks
Display the power supply
states of all PoE interfaces
connected to the PSE. display poe pse
pse-id interface [ | { begin |
exclude | include } regular-expression ] Available in any view
Display power information for
all PoE interfaces connected to
the PSE. display
poe pse pse-id interface power [ | { begin |
exclude | include } regular-expression ] Available in any view
Display the configurations and
applications of the PoE profile. display
poe -profile [ index index | name
profile-name ] [ | { begin | exclude | include }
regular-expression ] Available in any view
Display the configurations and
applications of the PoE profile
applied to the specified PoE
interface. display
poe -profile interface interface-type
interface-number [ | { begin | exclude | include }
regular-expression ] Available in any view
PoE configuration example
Network requirements
As shown in
Figure 56, the de vice supplies power to PDs through its PoE interfaces:
• GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, and GigabitEthernet 1/0/3 are connected to IP
telephones.
• GigabitEthernet 1/0/1 1 and GigabitEthernet 1/0/12 are connected to APs.
• The power supply priority of IP telephones is higher than that of the APs, for which the PSE supplies
power to IP telephones first when the PSE power is overloaded.
• The maximum power of AP2 connected to GigabitEthernet 1/0/12 does not exceed 9000
milliwatts.
Figure 56 Network diagram
Configuration procedure
# Enable PoE and specify the critical power supply priority on GigabitEthernet 1/0/1, GigabitEthernet
1/0/2, and GigabitEthernet 1/0/3.
system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] poe enable
[Sysname-GigabitEthernet1/0/1] poe priority critical
GE1/0/12
G E1/
0
/3
163 [Sysname-GigabitEthernet1/0/1] quit [Sysname] interface gigabitethernet 1/0/2 [Sysname-GigabitEthernet1/0/2] poe enable [Sysname-GigabitEthernet1/0/2] poe priority critical [Sysname-GigabitEthernet1/0/2] quit [Sysname] interface gigabitethernet 1/0/3 [Sysname-GigabitEthernet1/0/3] poe enable [Sysname-GigabitEthernet1/0/3] poe priority critical [Sysname-GigabitEthernet1/0/3] quit # Enable PoE on GigabitEthernet 1/0/1 1 and GigabitEthernet 1/0/12, and configure the maximum power of GigabitEthernet 1/0/12 as 9000 milliwatts. [Sysname] interface gigabitethernet 1/0/11 [Sysname-GigabitEthernet1/0/11] poe enable [Sysname-GigabitEthernet1/0/11] quit [Sysname] interface gigabitethernet 1/0/12 [Sysname-GigabitEthernet1/0/12] poe enable [Sysname-GigabitEthernet1/0/12] poe max-power 9000 After the configuration takes effect, the IP telephones and AP devices are powered and can work normally. Troubleshooting PoE Setting the priority of a PoE interface to critical fails Analysis • The guaranteed remaining power of the PSE is lower than the maximum power of the PoE interface. • The priority of the PoE interface is already set. Solution • In the first case, you can solve the problem by increasing the maximum PSE power, or by reducing the maximum power of the PoE interface when the guaranteed remaining power of the PSE cannot be modified. • In the second case, you should first remove the priority already configured. Applying a PoE profile to a PoE interface fails Analysis • Some configurations in the PoE profile are already configured. • Some configurations in the PoE profile do not meet the configuration requirements of the PoE interface. • Another PoE profile is already applied to the PoE interface. Solution • In the first case, you can solve the problem by removing the original configurations of those configurations. • In the second case, you need to modify some configurations in the PoE profile.
164 • In the third case, you need to remove the application of the undesired PoE profile to the PoE interface. Configuring an AC input under-voltage threshold fails Analysis The AC input under-voltage threshold is greater than or equal to the AC input over-voltage threshold. Solution You can drop the AC input under-voltage threshold below the AC input over-voltage threshold.
165 Configuring cluster management Overview Cluster management is an effective way to manage large numbers of dispersed network switches in groups. Cluster management offers the following advantages: • Saves public IP address resources. You do not have to assign one public IP address for every cluster member switch. • Simplifies configuration and management tasks. By configuring a public IP address on one switch, you can configure and manage a group of switches wi thout the trouble of logging in to each switch separately. • Provides a useful topology discovery and displa y function for network monitoring and debugging. • Allows simultaneous software upgrading and parameter configuration on multiple switches, free from topology and distance limitations. Roles in a cluster The switches in a cluster play different roles accord ing to their different functions and status. You can specify the following three roles for the switches: • Management device (Administrator) —A switch providing management interfaces for all switches in a cluster and the only switch configured with a public IP address. You can specify one and only one management switch for a cluster. Any configurat ion, management, and monitoring of the other switches in a cluster can only be implemented through the management switch. When a switch is specified as the management switch, it collects related information to discover and define candidate switches. • Member device (Member) —A switch managed by the management switch in a cluster. • Candidate device (Candidate) —A switch that does not yet belo ng to any cluster but can be added to a cluster. Different from a member switch, it s topology information has been collected by the management switch but it has not been added to the cluster. Figure 57 Network diagram
166
As shown in Figure 57, the s witch configured with a public IP address and performing the management
function is the management switch, the other managed switches are member switches, and the switch
that does not belong to any cluste r but can be added to a cluster is a candidate switch. The management
switch and the member switches form the cluster.
Figure 58 Role change in a cluster
As shown in Figure 58, a s witch in a cluster changes its ro le according to the following rules:
• A candidate switch becomes a mana gement switch when you create a cluster on it. A management
switch becomes a candidate switch only after the cluster is removed.
• A candidate switch becomes a me mber switch after being added to a cluster. A member switch
becomes a candidate switch after it is removed from the cluster.
How a cluster works
Cluster management is implemented through HW Group Management Protocol version 2 (HGMPv2),
which consists of the following three protocols:
• Neighbor Discovery Protocol (NDP)
• Neighbor Topology Discovery Protocol (NTDP)
• Cluster
A cluster configures and manages the switches in it through the above three protocols. Cluster
management involves topology information collect ion and the establishment and maintenance of a
cluster. Topology information collection and cluste r maintenance are independent from each other; in
fact, topology information collection starts before the cluster is created. The following workflow applies:
• All switches use NDP to collect the information of directly connected neighbors, including their
software version, host name, MAC address and port number.
• The management switch uses NTDP to do the following:
{ Collect information about the switches within user-specified hops.
{ Collect the topology information of all switches.
{ Specifies the candidate switches of the cluster based on the collected information.
• The management switch adds or deletes a memb er switch and modifies cluster management
configuration according to the candidate sw itch information collected through NTDP.
About NDP
NDP discovers information about directly connected neighbors, including the switch name, software
version, and connecting port of the adjacent switches. NDP works in the following ways:
• A switch running NDP periodically sends NDP packets to its neighbors. An NDP packet carries
NDP information (including the switch name, software version, and connecting port, etc.) and the
holdtime, which is how long the receiving switches will keep the NDP information. At the same time,
the switch also receives (but does not forward) NDP packets from its neighbors.
• A switch running NDP stores and maintains an NDP table. The switch creates an entry in the NDP
table for each neighbor. If a new neighbor is found, meaning the switch receives an NDP packet
sent by the neighbor for the first time, the switch adds an entry in the NDP table. If the NDP
167 information carried in the NDP packet is different from the stored information, the corresponding entry and holdtime in the NDP table are updated; otherwise, only the holdtime of the entry is updated. If an entry’s holdtime ex pires (in other words, no NDP information from the neighbor is received to restart the hold time before it ages out), the entry is removed from the NDP table. NDP runs on the data link layer, and supports different network layer protocols. About NTDP NTDP provides information required for cluster management; it collects topology information about the switches within the specified hop count. Based on the neighbor information stored in the neighbor table maintained by NDP, NTDP on the management switch advertises NTDP topology-collection requests to collect the NDP information of all the switches in a specific network range as well as the connection information of all its neighbors. The information collected will be used by the management switch or the network management software to implement required functions. When a member switch detects a change on its neighbors through its NDP table, it informs the management switch through handshake packets. Then the management switch triggers its NTDP to collect specific topology information, so that its NTDP can discover topology changes promptly. The management switch collects topology informatio n periodically. You can also administratively launch a topology information collection. The process of topology information collection is as follows: • The management switch periodically sends NTDP topology-collection request from the NTDP-enabled ports. • Upon receiving the request, the switch send s NTDP topology-collection response to the management switch, copies this response packet on the NTDP-enabled port and sends it to the adjacent switch. Topology-collection response incl udes the basic information of the NDP-enabled switch and NDP information of all adjacent switches. • The adjacent switch performs the same operation un til the NTDP topology-collection request is sent to all the switches within specified hops. To avoid concurrent responses to an NTDP topology -collection request causing congestion and deny of service on the management device, a delay mechanism was introduced. You configure the delay parameters for NTDP on the management device. As a result: • Each device waits for a period of time before forwarding an NTDP topology-collection request on the first NTDP-enabled port. • After the first NTDP-enabled port forwards the re quest, all other NTDP-enabled ports wait for a period of time and forward the NTDP topology-collection request. Cluster management maintenance 1. Adding a candidate switch to a cluster You should specify the management switch before creating a cluster. The management switch discovers and defines a candidate switch through NDP and NTDP protocols. The candidate switch can be automatically or manually added to the cluster. After the candidate switch is added to the cluster, it can obtain the member number assigned by the management switch and the private IP address used for cluster management. 2. Communication within a cluster In a cluster the management switch communicates with its member switches by sending handshake packets to maintain connection between them. Th e management/member switch state change is shown in Figure 59 .
168 Figure 59 Management/member switch state change A cluster manages the state of its member devices as follows: • After a cluster is created and a candidate switch is added to the cluster and becomes a member switch, the management switch saves the state information of the member switch and identifies it as Active. And the member switch also saves its stat e information and identifies itself as Active. • After a cluster is created, its management switch and member switches begin to send handshake packets. Upon receiving the handshake packets from the other, the management switch or a member switch simply remains its state as Active, without sending a response. • If the management switch does not receive the handshake packets from a member switch in an interval three times of the interval to send handsh ake packets, it changes the status of the member switch from Active to Connect. Likewise, if a member switch fails to receive the handshake packets from the management switch in an interval three times of the interval to send handshake packets, the status of itself will also be changed from Active to Connect. • During information holdtime, if the management switch receives handshake or management packets from a member swi tch that i s i n Conne ct st ate, it changes the state of the member switch to Active. Otherwise, it considers the member switch to be disconnected, and changes the state of the member switch to Disconnect. • During information holdtime, if a member switch in Connect state changes its state to Active if it receives handshake or management packets from the management switch; otherwise, it changes its state to Disconnect. • If communication between the management switch and a member switch is recovered, the member switch which is in Disconnect state will be added to the cluster, and the state of the member switch locally and on the management switch will be changed to Active. • Also, a member switch sends handshake packets to inform the management switch when there is a neighbor topology change. Management VLAN The management VL AN is a VL AN used for communicatio n in a cluster; it limits the cluster management range. Through configuration of the management VL AN, the following functions can be implemented: • Management packets (including NDP, NTDP and handshake packets) are restricted within the management VLAN. This isolates them from other packets, which enhances security. • The management switch and the member switches communicate with each other through the management VLAN. R ece iv e s th e h andsh ak e o r m a nagem en t p ac ke ts F a il s to r e c e i v e h and s h a k e p a c k e ts i n t h re e c o nse cu t iv e in t e rv a l s D is co n nec t s ta te is r e c o ve re d
169 For a cluster to work normally, you must set the packets from the management VLAN to pass the ports connecting the management switch and the member/candidate switches (including the cascade ports). Therefore: • If the packets from the management VLAN cannot pass a port, the switch connected with the port cannot be added to the cluster. Therefore, if th e ports (including the cascade ports) connecting the management switch and the me mber/candidate switches prohibit the packets from the management VLAN, you can set the packets from the management VLAN to pass the ports on candidate switches with the management VLAN auto-negotiation function. • Normally, only the packets with tags from the management VLAN can pass the ports. However, you can set packets without tags from the management VLAN to pass the ports if the default VLAN ID of the cascade ports and of the ports connecting the management switch and the member/candidate switches is the same as that of the management VLAN. If a candidate switch is connected to a management switch through another candidate switch, the ports between the two candidate switches are cascade ports. For more information about VLAN, see Layer 2—LAN Switching Configuration Guide . Cluster management configuration task list Before configuring a cluster, you need to determine the roles and functions the switches play. You also need to configure the related functions, preparing for the communication between switches within the cluster. Configuration guidelines • Disabling the NDP and NTDP functions on the management switch and member switches after a cluster is created will not cause the cluster to be dismissed, but will influence the normal operation of the cluster. • In a cluster, if a member switch enabled with the 802.1X or MAC address authentication function has other member switches connected to it, you must enable HW Authentication Bypass Protocol (HABP) server on the switch. Otherwise, the management switch of the cluster cannot manage the switches connected with it. For more information about the HABP, see Security Configuration Guide. • If the routing table of the management switch is full when a cluster is established, that is, entries with the destination address as a candidate switch cann ot be added to the routing table, all candidate switches will be added to and removed from the cluster repeatedly. • If the routing table of a candidate switch is full wh en the candidate switch is added to a cluster, that is, the entry with the destination address as the management switch cannot be added to the routing table, the candidate switch will be added to and removed from the cluster repeatedly. Complete these tasks to configure cluster management functions: Task Remarks Configuring the management switch: Enabling NDP globally and for specific ports Optional Configuring NDP parameters Optional Enabling NTDP globally and for specific ports Optional Configuring NTDP parameters Optional