H3C Technologies H3C S7500E Series Switches - Manual (Page 33)

1-26
4) When the IRF links fail, the system outputs error messages for detecting multi-active devices and
prompts you to repair the links.
%May 6 15:10:05:477 2010 H3C MAD/1/MAD_COLLISION_DETECTED: Multi-active devices
detected, please fix it.
Because the member ID of Device B is 2, when the MAD mechanism detects errors, the state of Device
B changes to recovery and all ports on Device B except for the reserved ones are shut down.
# Repair IRF links. Then, you are prompted that an IRF virtual device merge will happen and you need
to reboot the IRF virtual device.
%May 6 15:12:52:935 2010 H3C STM/6/STM_LINK_STATUS_UP:
IRF port 1 is up.
%May 6 15:13:02:828 2010 H3C 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 and reboot the device.
<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 H3C DEVM/1/REBOOT:
Reboot device by command.
%May 6 15:31:09:734 2010 H3C DEVM/5/SYSTEM_REBOOT: System is rebooting now.
# After device reboot, Device B re-joins the IRF virtual device. You can use the display irf command to
view the topology information about the IRF virtual device.
<Sysname> display irf topology
Topology Info
-------------------------------------------------------------------------
IRF-Port1 IRF-Port2
Switch Link neighbor Link neighbor Belong To
2 DOWN -- UP 1 00e0-fc0f-8c02
1 UP 2 DIS -- 00e0-fc0f-8c02
Configuration Example of Using the LACP MAD Detection
Network requirements
As shown in Figure 1-11 , the network is outgrowing the forwarding capability of the existing core switch,
namely, Device A. To accommodate to business growth, the network must be scaled up to extend its
forwarding capability while the present investments of the customer are protected. In addition, the ease
of management and maintenance must be ensured.