13
[IRF-Ten-GigabitEthernet1/0/10] quit
# Observe the output on the server configuration terminal.
Pinging 10.153.116.111 with 32 bytes of data:
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
Request timed out.
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
The output shows that the IP address can be pinged after transient traffic disruption.
# On the IRF fabric at the access layer, shut down Ten-GigabitEthernet 1/0/49 and
Ten-GigabitEthernet 1/0/50 (member ports of Bridge-Aggregation 2). The server cannot access the
distribution layer through Device A.
[IRF] interface range ten-gigabitethernet 1/0/49 ten-gigabitethernet 1/0/50
[IRF-if-range] shutdown
[IRF-if-range] quit
# Observe the output on the server configuration terminal.
Pinging 10.153.116.111 with 32 bytes of data:
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
Request timed out.
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
Reply from 10.153.116.111: bytes=32 time<1ms TTL=128
The output shows that the IP address can be pinged after transient traffic disruption. The server
accesses the distribution layer through another device in the access-layer IRF fabric.
Verifying link failure protection of the ring topology
# Disconnect all IRF links between two IRF member devices. (Details not shown.)
# Verify that the IRF fabric operates correctly in daisy-chain topology. (Details not shown.)
Verifying the LACP MAD configuration
# As shown in
, disconnect two IRF connections: one between Device A and Device D, and
the other between Device B and Device C. The disconnect actions cause the IRF fabric to break up
into two parts.
Figure 6 IRF split
# Observe the output messages to verify that LACP MAD takes the following actions:
