35
10.214.20.0/24 Direct 0 0 10.214.20.1 Vlan20
10.214.20.1/32 Direct 0 0 127.0.0.1 InLoop0
10.214.50.0/30 Direct 0 0 10.214.50.1 Vlan40
10.214.50.1/32 Direct 0 0 127.0.0.1 InLoop0
10.214.50.4/30 Direct 0 0 10.214.50.5 Vlan41
10.214.50.5/32 Direct 0 0 127.0.0.1 InLoop0
10.214.50.8/30 OSPF 10 2 10.214.50.2 Vlan40
10.214.60.0/30 OSPF 10 2 10.214.50.2 Vlan40
10.214.70.0/30 OSPF 10 2 10.214.50.6 Vlan41
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
The output shows that the IRF fabric has learned routing information from the core routers correctly.
Verifying the link backup function of multichassis
aggregations
# Ping 10.214.50.2 (Router A) from any server.
C:\Users>ping 10.214.50.2 –t
# On the IRF fabric, shut down Ten-GigabitEthernet 1/0/13, a member port of Bridge-Aggregation 40.
[IRF] interface ten-gigabitethernet 1/0/13
[IRF-Ten-GigabitEthernet1/0/13] shutdown
[IRF-Ten-GigabitEthernet1/0/13] quit
# Observe the output on the configuration terminal for the server.
Pinging 10.214.50.2 with 32 bytes of data:
Reply from 10.214.50.2: bytes=32 time=8ms TTL=127
Reply from 10.214.50.2: bytes=32 time=7ms TTL=127
Reply from 10.214.50.2: bytes=32 time=2ms TTL=127
Reply from 10.214.50.2: bytes=32 time=278ms TTL=127
Reply from 10.214.50.2: bytes=32 time=7ms TTL=127
The output shows that the address can be pinged after a short delay.
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 BFD MAD configuration
# 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 down into two parts, as
shown in
