27Acting as the intermediate device, Device C needs to support LACP to forward and process LACPprotocol packets, and help Device A and Device B implement MAD detection. An LACP-supported switchis used here to save the cost.# Create a dynamic aggregation interface. system-view[DeviceC] interface bridge-aggregation 2[DeviceC-Bridge-Aggregation2] link-aggregation mode dynamic[DeviceC-Bridge-Aggregation2] quit# Add ports GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to the aggregation interface and theyare used for the LACP MAD detection.[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 2ARP MAD detection-enabled IRF configuration exampleNetwork requirementsThe network (see Figure 13) is outgrowing the forwarding capability of the existing core switch, namely,Device A. To address business growth, the network must be scaled up to extend its forwarding capabilitywhile the present investments of the customer are protected. Ease of management and maintenance mustalso be ensured.Figure 13 Network diagramConfiguration considerations• Device A is located at the distribution layer of the network. To improve the forwarding capability atthis layer, additional devices are needed. In this example, Device B is added.• To address the requirements for high availability, ease of management and maintenance, use IRF2technology to create an IRF fabric with Device A and Device B at the access layer. The IRF fabric isconnected to Device C with dual links.