HP 5500 Ei 5500 Si Switch Series Configuration Guide

 
170 
Task Remarks 
Manually collecting topology information  Optional 
Enabling the cluster function Optional 
Establishing a cluster Required 
Enabling management VLAN auto-negotiation Required 
Configuring communication between the management switch and the member switches 
within a cluster  Optional 
Configuring cluster management protocol packets 
Optional 
Cluster member management Optional 
Configuring the member switches: 
Enabling NDP  Optional 
Enabling NTDP Optional 
Manually collecting...

 
171 
Step Command Remarks 
3.  Enable the NDP feature on ports. 
• In system view: 
ndp enable 
interfaceinterface-list  
• In Ethernet interface view or 
Layer 2 aggregate interface 
view: 
a.  interface  interface-type  
interface-number 
b.  ndp enable   Use either command. 
By default, NDP is enabled 
globally and also on all 
ports. 
 
HP recommends that you disable NDP on a port which connects with the switches that do not need to join 
the cluster. This prevents the management switch fr
om...

 
172 
Step Command Remarks 
4.  Enable NTDP for the port. 
ntdp enable Optional. 
By default, NTDP is enabled on all ports. 
 
HP recommends that you disable NTDP on a port which connects with the switches that do not need to 
join the cluster. This prevents the management sw
itch from adding and collecting topology information 
from switches which do not need to join the cluster. 
Configuring NTDP parameters 
By configuring the maximum hops for collecting topo logy information, you can get topology...

 
173 
switch, thus managing and monitoring switches in real time, regardless of whether a cluster is created. 
To configure to manually collect topology information: 
 
Task Command 
Manually collect topology information.  ntdp explore 
 
Enabling the cluster function  
Step Command Remarks 
1.  Enter system view. 
system-view  N/A 
2.  Enable the cluster function 
globally.  cluster enable  Optional. 
By default, this function is enabled.
 
 
Establishing a cluster 
Before establishing a cluster, you...

 
174 
Step Command Remarks 
5.  Establish a cluster. 
• Manually establish a cluster: 
build  cluster-name  
• Automatically establish a 
cluster: 
auto-build  [ recover ]   Use either approach. 
By default, the switch is not the 
management switch. 
 
Handshake packets use UDP port 40000. For a cluster to
 be established successfully, make sure that the 
port is not in use before establishing it. 
Enabling management VLAN auto-negotiation 
The management VLAN limits the cluster manageme nt range. If...

 
175 
holdtime, it changes the state of the member switch to Disconnect. When the communication is 
recovered, the member switch needs to be re-added to the cluster (this process is automatically 
performed). 
•   If the management switch receives handshake packe ts from the member switch within the holdtime, 
the state of the member switch remains Active and the holdtime is restarted. 
To configure communication between the management sw itch and the member switches within a cluster: 
 
Step Command...

 
176 
Step Command Remarks 
3.  Configure the 
destination MAC 
address for cluster 
management protocol 
packets.  cluster-mac
 mac-address  By default, the destination MAC address is 
0180-C200-000A. 
The following are the configurable MAC 
addresses: 
•
 0180-C200-0000 
• 0180-C200-000A 
• 0180-C200-0020 through 
0180-C200-002F 
• 010F-E200-0002 
4.   Configure the interval for 
sending MAC address 
negotiation broadcast 
packets.  cluster-mac
 syn-interval  
interval   Optional. 
The default...

 
177 
Configuring the member switches 
Enabling NDP 
See Enabling NDP globally and for specific ports .  
Enabling NTDP 
See Enabling NTDP globally and for specific ports .  
Manually collecting topology information 
See Manually collecting topology information .  
Enabling the cluster function 
See Enabling the cluster function . 
Deleting a member switch from a cluster  
Step Command 
1.  Enter system view. 
system-view 
2.  Enter cluster view. 
cluster 
3.  Delete a member switch from the cluster....

 
178 
(including the management switch and member switches) of the cluster; otherwise, the switching 
may fail because of an authentication failure. 
•   If the member specified in this command does not exist, the system prompts error when you execute 
the command; if the switching succeeds, your user level on the management switch is retained. 
•   If the Telnet users on the switch to be logged in reach the maximum number, the switching fails. 
•   To prevent resource waste, avoid ring switching  when...

 
179 
another switch not included in the blacklist, the MAC address and access port of the latter are also 
included in the blacklist. The cand idate switches in a blacklist can be added to a cluster only if the 
administrator manually removes them from the list.  
The whitelist and blacklist are mutually exclusive. A  whitelist member cannot be a blacklist member, and 
the blacklist member cannot be a whitelist member. Ho wever, a topology node can belong to neither the 
whitelist nor the blacklist....