22.10.2013 Views

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

7.8.1.0 - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Step Task Command Command Mode<br />

2<br />

Create a failover group and specify<br />

the two port-channels that will be<br />

members of the group.<br />

In Figure 271, LAGs 1 and 2 have been placed into to the same failover group.<br />

Figure 271 Configuring Shared LAG State Tracking<br />

R2#config<br />

R2(conf)#port-channel failover-group<br />

R2(conf-po-failover-grp)#group 1 port-channel 1 port-channel 2<br />

View the failover group configuration using the show running-configuration po-failover-group<br />

command, as shown in Figure 272.<br />

Figure 272 Viewing Shared LAG State Tracking in the Running-configuration<br />

R2#show running-config po-failover-group<br />

!<br />

port-channel failover-group<br />

group 1 port-channel 1 port-channel 2<br />

In Figure 273, LAGs 1 and 2 are members of a failover group. LAG 1 fails and LAG 2 is brought down<br />

upon the failure. This effect is logged by Message 13, in which a console message declares both LAGs<br />

down at the same time.<br />

Figure 273 Shared LAG State Tracking<br />

R2(conf)# port-channel failover-group<br />

R2(conf-po-failover-grp)# group 1 port-channel 1 port-channel 2<br />

R1<br />

Message 13 Shared LAG State Tracking Console Message<br />

group number port-channel<br />

number port-channel<br />

number<br />

FTOS Configuration Guide, version <strong>7.8.1.0</strong> 439<br />

Po 1<br />

Po 2<br />

R4<br />

R2 R3<br />

CONFIG-PO-FAILOVER-GRP<br />

fnC0049mp<br />

2d1h45m: %RPM0-P:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Po 1<br />

2d1h45m: %RPM0-P:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Po 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!