52
[Sysname-Vlan-interface3] mad ip address 192.168.2.1 24 member 1
[Sysname-Vlan-interface3] mad ip address 192.168.2.2 24 member 2
[Sysname-Vlan-interface3] mad ip address 192.168.2.3 24 member 3
[Sysname-Vlan-interface3] mad ip address 192.168.2.4 24 member 4
[Sysname-Vlan-interface3] quit
# Disable the spanning tree function on ports GigabitEthernet 1/2/0/1, GigabitEthernet 2/3/0/1,
GigabitEthernet 3/3/0/1, and GigabitEthernet 4/3/0/1.
[Sysname] interface gigabitethernet 1/2/0/1
[Sysname-gigabitethernet-1/2/0/1] undo stp enable
[Sysname-gigabitethernet-1/2/0/1] quit
[Sysname] interface gigabitethernet 2/3/0/1
[Sysname-gigabitethernet-2/3/0/1] undo stp enable
[Sysname-gigabitethernet-2/3/0/1] quit
[Sysname] interface gigabitethernet 3/3/0/1
[Sysname-gigabitethernet-3/3/0/1] undo stp enable
[Sysname-gigabitethernet-3/3/0/1] quit
[Sysname] interface gigabitethernet 4/3/0/1
[Sysname-gigabitethernet-4/3/0/1] undo stp enable
[Sysname-gigabitethernet-4/3/0/1] quit
6. Configure Device E as the intermediate switch
To make Device E act as the intermediate switch to transparently forwards BFD protocol packets
exchanged between the member switches for MAD detection, add all ports for BFD MAD on Device E to
one VLAN dedicated for BFD MAD. (Details not shown)
7. Troubleshoot the IRF when the MAD mechanism detects errors
Because the member switches are connected with a ring connection, when a single IRF link fails, the
connection turns into a daisy chain connection and the IRF is not partitioned. When both the IRF link
between Device A and Device C and the IRF link between Device B and Device D go down, however, the
IRF fabric will break into two IRF fabrics: one (IRF 1) with Device A and Device C, and one (IRF 2) with
Device B and Device D. In addition, IRF link status error and card failure messages will be displayed. The
following takes IRF 1 for example:
%May 6 15:10:05:477 2010 HP MAD/1/MAD_COLLISION_DETECTED: Multi-active devices
detected, please fix it.
Because the master member ID of IRF 2 is bigger, when the MAD mechanism detects errors, the state of
IRF 2 changes to recovery and all ports on the member devices except for the reserved ones are shut
down.
# Fix the IRF link. When the IRF link recovers, an IRF merge occurs, and you must reboot the IRF fabric.
%May 6 15:12:52:935 2010 HP STM/6/STM_LINK_STATUS_UP:
IRF port 1 is up.
%May 6 15:13:02:828 2010 HP STM/4/STM_MERGE_NEED_REBOOT:
IRF merge occurs and the IRF system needs a reboot.
# Log in to the console port of Device B or Device D and reboot IRF 2.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait.
.........DONE!
This command will reboot the device. Continue? [Y/N]:y
#May 6 15:31:09:724 2010 HP DEVM/1/REBOOT:
To Next Page
Loading...
Need help?
General
