Lacp Mad Detection-Enabled Configuration Example (Non Pre-Configuration Mode); Network Requirements - H3C S9500E Series Configuration Manual

Routing switches irf configuration guide
Hide thumbs Also See for S9500E Series:
Table of Contents

Advertisement

NOTE:
By default, Ethernet, VLAN, and aggregate interfaces are down. To configure these types of interfaces,
execute the undo shutdown command to bring them up.
LACP MAD detection-enabled configuration example (non
pre-configuration mode)

Network requirements

The network as shown in
(Device A).
To address business growth, increase the number of ports at the access layer while protecting the current
investments of the customer and maintaining ease of management and maintenance.
Figure 15 Network diagram
Device A
Note: The solid orange line represents the IRF link; the
solid magenta lines represent links used for LACP MAD;
the solid black lines represent Ethernet links.
Configuration considerations
To increase the number of access ports, additional devices are needed. In this example, Device B
is added.
To offset the risk of IRF fabric partition, configure MAD to detect multi-active collisions. In this
example, LACP MAD is adopted because there are many access switches. For LACP MAD, use an
intermediate switch that supports extended LACPDUs.
Configuration procedure
Configure Device A
1.
# Change the operating mode of Device A to IRF.
<Sysname> system-view
[Sysname] irf member 1
Info: Member ID change will take effect after the switch reboots and operates in IRF mode.
[Sysname] chassis convert mode irf
Figure 15
is outgrowing the forwarding capability of the existing core switch,
GE4/0/1
GE4/0/2
Device C
GE1/4/0/2
XGE1/3/0/1
(IRF-port1/2)
IRF
IP network
GE2/4/0/2
XGE 2/3/0/1
(IRF-port2/1)
Device B
35

Advertisement

Table of Contents
loading

Table of Contents