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 195
29
Task Command Remarks
Display the load sharing mode for
IRF links. display irf-port load-sharing mode
[ irf-port
[ member-id /port-number ] ] [ |
{ begin | exclude | include }
regular-expression ] Available in any view
Display the master/subordinate
switchover state of IRF members.
display switchover state
[ slot
member-id ] [ | { begin | exclude |
include } regular-expression ] Available in any view
Display MAD configuration. display mad [
verbose ] [ | { begin
| exclude...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-194.png "Page 195
29
Task Command Remarks
Display the load sharing mode for
IRF links. display irf-port load-sharing mode
[ irf-port
[ member-id /port-number ] ] [ |
{ begin | exclude | include }
regular-expression ] Available in any view
Display the master/subordinate
switchover state of IRF members.
display switchover state
[ slot
member-id ] [ | { begin | exclude |
include } regular-expression ] Available in any view
Display MAD configuration. display mad [
verbose ] [ | { begin
| exclude...")
![Page 196
30
# Change the member ID of Device B to 2.
system-view
[DeviceB] irf member 1 renumber 2
Warning: Renumbering the switch number may result in configuration chang\
e or loss.
Continue? [Y/N]:y
[DeviceB]
2. Power off the devices, connect IRF links as shown in Figure 14, and power on the two devices.
3. Configure IRF port bindings:
# Create IRF port 2 on Device A, bind Ten-GigabitEthernet 1/1/2 to the IRF port, and save the
configuration.
system-view
[DeviceA] interface ten-gigabitethernet...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-195.png "Page 196
30
# Change the member ID of Device B to 2.
system-view
[DeviceB] irf member 1 renumber 2
Warning: Renumbering the switch number may result in configuration chang\
e or loss.
Continue? [Y/N]:y
[DeviceB]
2. Power off the devices, connect IRF links as shown in Figure 14, and power on the two devices.
3. Configure IRF port bindings:
# Create IRF port 2 on Device A, bind Ten-GigabitEthernet 1/1/2 to the IRF port, and save the
configuration.
system-view
[DeviceA] interface ten-gigabitethernet...")
25
Step Command Remarks
1. Enter system view.
system-view N/A
2. Create a VLAN dedicated to
BFD MAD. vlan
vlan-id The default VLAN on the switch
is VLAN 1.
3.
Return to system view.
quit N/A
4. Enter Ethernet interface view. interface
interface-type
interface-number N/A
5.
Assign the port to the BFD
MAD VLAN.
• Assign the port to the VLAN as an
access port:
port access vlan vlan-id
• Assign the port to the VLAN as a
trunk port:
port trunk permit vlan vlan-id
• Assign the port to the VLAN as a
hybrid port:
port hybrid vlan vlan-id { tagged |
untagged } Choose one command
depending on the port type.
BFD MAD detection has no
requirement for the link type of
the detection port.
The default link type of a port is
access.
6.
Return to system view.
quit N/A
7. Enter VLAN interface view. interface vlan-interface
interface-number N/A
8.
Enable BFD MAD.
mad bfd enable By default, BFD MAD is
disabled.
9.
Configure a MAD IP address
for the specified member on
the VLAN interface. mad ip address
ip-address { mask |
mask-length } member member-id By default, no MAD IP address is
configured on any VLAN
interface.
The MAD IP address must not on
the same subnet as any IP
address configured on any
member device.
NOTE:
After a BFD MAD-enabled IRF fabric splits, route conflict messages (for example, %May 5
16:15:47:733 2010 ARP/3/ROUTECONFLICT: Slot=5;Route conflict found,
IP:192.168.2.1, VrfIndex:0 ) might appear on the fabric part that does not have the original
master, because this fabric part still keeps the fo rwarding entries with the original master as the
destination. This message does not affect forwarding . The system stops generating it after the forwardin
g
entries are aged out.
Configuring ARP MAD
When you configure ARP MAD, follow these guidelines:
• If an intermediate device is used, you can us e common data links as ARP MAD links. If no
intermediate device is used, set up dedicate d ARP MAD links between IRF member devices.
• Use a VLAN dedicated to ARP MAD.
• If an intermediate device is used, do the following:
{ Run the spanning tree feature between the IRF fabric and the intermediate device.
26
{ Enable the IRF fabric to change its bridge MAC address as soon as the master leaves.
{ Create the ARP MAD VLAN and assign the ports on the ARP MAD links to the VLAN.
{ If the intermediate device is in an IRF fabric, as sign this fabric a different domain ID than the
ARP MAD-enabled fabric to avoid false detection of IRF partition.
To c o n fig u re A R P M A D :
Step Command Remarks
1. Enter system view.
system-view N/A
2. Assign a domain ID to the IRF
fabric. irf domain
domain-id The default IRF domain ID is 0.
3. Create a VLAN dedicated to
ARP MAD. vlan
vlan-id The default VLAN on the device
is VLAN 1.
4.
Return to system view.
quit N/A
5. Enter Layer 2 Ethernet
interface view. interface
interface-type
interface-number N/A
6.
Assign the port to the ARP
MAD VLAN.
• Assign the port to the VLAN as an
access port:
port access vlan vlan-id
• Assign the port to the VLAN as a
trunk port:
port trunk permit vlan vlan-id
• Assign the port to the VLAN as a
hybrid port:
port hybrid vlan vlan-id { tagged |
untagged } Choose one command
depending on the port type.
ARP MAD detection has no
requirement for the link type.
The default link type of a port is
access.
7.
Return to system view.
quit N/A
8. Enter VLAN interface view. interface
vlan-interface
vlan-interface-id N/A
9.
Assign the interface an IP
address. ip address
ip-address { mask |
mask-length } By default, no IP address is
assigned to any VLAN interface.
10.
Enable ARP MAD.
mad arp enable By default, ARP MAD is
disabled.
Excluding a port from the shutdown action upon detection of
multi-active collision
When the IRF fabric transits to the Recovery state,
all ports but the console and physical IRF ports by
default automatically shut down.
You can exclude a port from the shutdown action for management or other special purposes. For
example:
• Exclude a port from the shutdown action, so you can telnet to the port for managing the switch.
• Exclude a VLAN interface and its Layer 2 ports from the shutdown action, so you can log in through
the VLAN interface.
27 CAUTION: Excluding a VLAN interface and its Layer 2 ports from the shutdown action introduces IP collision risks because the VLAN interface might be active on both th e IRF fabric in Active state and the IRF fabric in Recovery state. To configure a port to not shut down when the IRF fabric transits to the recovery state: Step Command Remarks 1. Enter system view. system-view N/A 2. Configure a port to not shut down when the IRF fabric transits to the Recovery state. mad exclude interface interface-type interface-number By default, when an IRF fabric transits to the Recovery state, all its network ports except the IRF physical ports and console port are shut down. Recovering an IRF fabric After the failed IRF link between two split IRF fabrics is recovered, log in to the Recovery-state IRF fabric, and use the reboot command to reboot all its members. After these member switches join the Active-state IRF fabric as subordinates, IRF merge is complete, as shown in Figure 12. Figure 12 Recovering the IRF fabric If the Active-state fabric has failed, for example, because of device or link failures, before the IRF link is recovered (see Figure 13) , use the mad restore c o m m a n d o n t h e Re c ove r y - s ta te fab ric to ch a n g e i t s s ta te to Active for forwarding traffic. After you repair the IRF link, the two parts merge into a unified IRF fabric.
28
Figure 13 Active-state IRF fabric fails be fore the IRF link is recovered
To manually recover an IRF fabric in Recovery state:
Step Command
1. Enter system view.
system-view
2. Change the state of the IRF fabric from
Recovery to Active. mad restore
After the IRF fabric is recovered, all ports that have been shut down by MAD automatically come up.
Displaying and maintaining an IRF fabric
Task Command Remarks
Display information about all IRF
members. display irf
[ | { begin | exclude |
include } regular-expression ] Available in any view
Display the IRF fabric topology. display irf topology
[ | { begin |
exclude | include }
regular-expression ] Available in any view
Display the IRF settings that take
effect at the next startup. display irf configuration
[ | { begin
| exclude | include }
regular-expression ] Available in any view
29
Task Command Remarks
Display the load sharing mode for
IRF links. display irf-port load-sharing mode
[ irf-port
[ member-id /port-number ] ] [ |
{ begin | exclude | include }
regular-expression ] Available in any view
Display the master/subordinate
switchover state of IRF members.
display switchover state
[ slot
member-id ] [ | { begin | exclude |
include } regular-expression ] Available in any view
Display MAD configuration. display mad [
verbose ] [ | { begin
| exclude | include }
regular-expression ] Available in any view
Configuration examples
This section provides IRF configuration examples fo
r IRF fabrics that use different MAD mechanisms.
LACP MAD-enabled IRF configuration example
Network requirements
Set up a two-member IRF fabric at the access layer of the enterprise network in Figure 14. C onfigure LACP
MAD in the IRF fabric, because the IRF fabric has a multi-chassis aggregate link to Device C, an HP
device that supports extended LACP.
Figure 14 Network diagram
Configuration procedure
This example assumes that the system names of Device A, Device B and Device C are DeviceA, DeviceB ,
and DeviceC respectively before the IRF fabric is formed.
1. Assign member IDs:
# Keep the default member ID of Device A unchanged.
30 # Change the member ID of Device B to 2. system-view [DeviceB] irf member 1 renumber 2 Warning: Renumbering the switch number may result in configuration chang\ e or loss. Continue? [Y/N]:y [DeviceB] 2. Power off the devices, connect IRF links as shown in Figure 14, and power on the two devices. 3. Configure IRF port bindings: # Create IRF port 2 on Device A, bind Ten-GigabitEthernet 1/1/2 to the IRF port, and save the configuration. system-view [DeviceA] interface ten-gigabitethernet 1/1/2 [DeviceA-Ten-GigabitEthernet1/1/2] shutdown [DeviceA] irf-port 1/2 [DeviceA-irf-port1/2] port group interface ten-gigabitethernet 1/1/2 [DeviceA-irf-port1/2] quit [DeviceA] interface ten-gigabitethernet 1/1/2 [DeviceA-Ten-GigabitEthernet1/1/2] undo shutdown [DeviceA-Ten-GigabitEthernet1/1/2] save # Create IRF port 1 on Device B, bind Ten-Gig abitEthernet 2/1/1 to the IRF port, and save the configuration. system-view [DeviceB] interface ten-gigabitethernet 2/1/1 [DeviceB-Ten-GigabitEthernet2/1/1] shutdown [DeviceB] irf-port 2/1 [DeviceB-irf-port2/1] port group interface ten-gigabitethernet 2/1/1 [DeviceB-irf-port2/1] quit [DeviceB] interface ten-gigabitethernet 2/1/1 [DeviceB-Ten-GigabitEthernet2/1/1] undo shutdown [DeviceB-Ten-GigabitEthernet2/1/1] save # Activate IRF port conf iguration on Device A. [DeviceA-Ten-GigabitEthernet1/1/2] quit [DeviceA] irf-port-configuration active # Activate IRF port configuration on Device B. [DeviceB-Ten-GigabitEthernet2/1/1] quit [DeviceB] irf-port-configuration active After the IRF port configuration is activated, the two devices automatically elect a master. In this example, Device A is the master. Device B auto matically reboots and joins the Device A as a subordinate switch to form an IRF fabric. The system name of the IRF fabric is DevcieA. 4. Configure LACP MAD: # Create a dynamic aggregation interface and enable LACP MAD. Because LACP MAD is not run between IRF domains, you can use the default value 0. system-view [DeviceA] interface bridge-aggregation 2 [DeviceA-Bridge-Aggregation2] link-aggregation mode dynamic [DeviceA-Bridge-Aggregation2] mad enable You need to assign a domain ID (range: 0-4294967295)
31 [Current domain is: 0]: The assigned domain ID is: 0 Info: MAD LACP only enable on dynamic aggregation interface. # Add GigabitEthernet 1/0/1 and GigabitEthernet 2/0/1 to the aggregation interface. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] port link-aggregation group 2 [DeviceA-GigabitEthernet1/0/1] quit [DeviceA] interface gigabitethernet 2/0/1 [DeviceA-GigabitEthernet2/0/1] port link-aggregation group 2 5. Configure Device C as the intermediate device: # Create a dynamic aggregation interface. system-view [DeviceC] interface bridge-aggregation 2 [DeviceC-Bridge-Aggregation2] link-aggregation mode dynamic [DeviceC-Bridge-Aggregation2] quit # Add GigabitEthernet 1/0/1 and GigabitEther net 1/0/2 to the aggregation interface. [DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] port link-aggregation group 2 [DeviceC-GigabitEthernet1/0/1] quit [DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] port link-aggregation group 2 BFD MAD-enabled IRF configuration example This configuration example applies only to the 5500 EI switches. Network requirements Set up an IRF fabric at the distribution layer of the network in Figure 15. C onfigure BFD MAD in the IRF fabric and set up BFD MAD links between the member devices. Disable the spanning tree function on the ports used for BFD MAD, because the two features conflict with each other. Assign the highest member priority to Device A so it can be elected as the master.
32 Figure 15 Network diagram Configuration procedure This example assumes that the system names of Device A and Device B are DeviceA and DeviceB respectively before the IRF fabric is formed. 1. Assign member IDs: # Keep the default member ID of Device A unchanged. # Change the member ID of Device B to 2. system-view [DeviceB] irf member 1 renumber 2 Warning: Renumbering the switch number may result in configuration chang\ e or loss. Continue? [Y/N]:y [DeviceB] 2. Power off the member devices, connect IRF links as shown in Figure 15, and power on the two devices. 3. Configure IRF port bindings: # Create IRF port 2 on Device A, bind Ten-GigabitEthernet 1/1/2 to the IRF port, and save the configuration. system-view [DeviceA] interface ten-gigabitethernet 1/1/2 [DeviceA-Ten-GigabitEthernet1/1/2] shutdown [DeviceA] irf-port 1/2 [DeviceA-irf-port1/2] port group interface ten-gigabitethernet 1/1/2 [DeviceA-irf-port1/2] quit [DeviceA] interface ten-gigabitethernet 1/1/2 [DeviceA-Ten-GigabitEthernet1/1/2] undo shutdown [DeviceA-Ten-GigabitEthernet1/1/2] save
33 # Create IRF port 1 on Device B, bind Ten-GigabitEthernet 2/1/1 to the IRF port, and save the configuration. system-view [DeviceB] interface ten-gigabitethernet 2/1/1 [DeviceB-Ten-GigabitEthernet2/1/1] shutdown [DeviceB] irf-port 2/1 [DeviceB-irf-port2/1] port group interface ten-gigabitethernet 2/1/1 [DeviceB-irf-port2/1] quit [DeviceB] interface ten-gigabitethernet 2/1/1 [DeviceB-Ten-GigabitEthernet2/1/1] undo shutdown [DeviceB-Ten-GigabitEthernet2/1/1] save # Activate IRF port conf iguration on Device A. [DeviceA-Ten-GigabitEthernet1/1/2] quit [DeviceA] irf-port-configuration active # Activate IRF port configuration on Device B. [DeviceB-Ten-GigabitEthernet2/1/1] quit [DeviceB] irf-port-configuration active After the IRF port configuration is activated, the two devices automatically elect a master. In this example, Device A is the master. Device B auto matically reboots and joins the Device A as a subordinate switch to form an IRF fabric. The system name of the IRF fabric is DevcieA. 4. Configure BFD MAD: # Create VLAN 3, and add port GigabitEtherne t 1/0/1 on Device A (member ID 1) and port GigabitEthernet 2/0/1 on Device B (member ID 2) to VLAN 3. system-view [DeviceA] vlan 3 [DeviceA-vlan3] port gigabitethernet 1/0/1 gigabitethernet 2/0/1 [DeviceA-vlan3] quit # Create VLAN-interface 3 and configure a MA D IP address for each member device on the interface. [DeviceA] interface vlan-interface 3 [DeviceA-Vlan-interface3] mad bfd enable [DeviceA-Vlan-interface3] mad ip address 192.168.2.1 24 member 1 [DeviceA-Vlan-interface3] mad ip address 192.168.2.2 24 member 2 [DeviceA-Vlan-interface3] quit # Connect the BFD MAD links as shown in Figure 15. # Disable the spanning tree function on Gig abitEthernet 1/0/1 and GigabitEthernet 2/0/1. [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-Gigabitethernet1/0/1] undo stp enable [DeviceA-Gigabitethernet1/0/1] quit [DeviceA] interface gigabitethernet 2/0/1 [DeviceA-Gigabitethernet2/0/1] undo stp enable
34 ARP MAD-enabled IRF configuration example Network requirements Se t u p a n I R F fab ric i n t h e e n te rp ri se n e t work i n Figure 16. C onfigure ARP MAD in the IRF fabric and use the links connected to Device C for transmitting ARP MAD packets. To prevent loops, run the spanning tree function between Device C and the IRF fabric. Figure 16 Network diagram Configuration procedure This example assumes that the system names of Device A, Device B and Device C are DeviceA, DeviceB , and DeviceC , respectively, before the IRF fabric is formed. 1. Assign member IDs: # Keep the default member ID of Device A unchanged. # Change the member ID of Device B to 2. system-view [DeviceB] irf member 1 renumber 2 Warning: Renumbering the switch number may result in configuration chang\ e or loss. Continue? [Y/N]:y [DeviceB] 2. Power off the member devices, connect IRF links as shown in Figure 16, and power on the two devices. 3. Configure IRF port bindings: # Create IRF port 2 on Device A, and bind Ten-Gi gabitEthernet 1/1/2 to the IRF port, and save the configuration. system-view [DeviceA] interface ten-gigabitethernet 1/1/2 [DeviceA-Ten-GigabitEthernet1/1/2] shutdown [DeviceA] irf-port 1/2 [DeviceA-irf-port1/2] port group interface ten-gigabitethernet 1/1/2 [DeviceA-irf-port1/2] quit [DeviceA] interface ten-gigabitethernet 1/1/2