02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - 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.

View <strong>the</strong> status of a failover group member using <strong>the</strong> command show interface port-channel, as shown in<br />

Figure 126.<br />

Figure 126 Viewing Status of a Failover Group Member<br />

R2#show interface Port-channel 2<br />

Port-channel 2 is up, line protocol is down (Failover-group 1 is down)<br />

Hardware address is 00:01:e8:05:e8:4c, Current address is 00:01:e8:05:e8:4c<br />

Interface index is 1107755010<br />

Minimum number of links to bring Port-channel up is 1<br />

Port-channel is part of failover-group 1<br />

Internet address is not set<br />

MTU 1554 bytes, IP MTU 1500 bytes<br />

LineSpeed 1000 Mbit<br />

Members in this channel: Gi 1/17(U)<br />

ARP type: ARPA, ARP Timeout 04:00:00<br />

Last clearing of "show interface" counters 00:01:28<br />

Queueing strategy: fifo<br />

Note: The set of console messages shown in Message 18 appear only if Shared LAG State Tracking is<br />

configured on that router (<strong>the</strong> feature can be configured on one or both sides of a link). For example, in<br />

Figure 125, if Shared LAG State Tracking is configured on R2 only, <strong>the</strong>n no messages appear on R4<br />

regarding <strong>the</strong> state of LAGs in a failover group.<br />

Important Points about Shared LAG State Tracking<br />

• This feature is available <strong>for</strong> static and dynamic LAGs.<br />

• Only a LAG can be a member of a failover group.<br />

• Shared LAG State Tracking can be configured on one side of a link or on both sides.<br />

• If a LAG that is part of a failover group is deleted, <strong>the</strong> failover group is deleted.<br />

• If a LAG moves to <strong>the</strong> down state due to this feature, its members may still be in <strong>the</strong> up state.<br />

Hitless LACP<br />

Hitless LACP is supported on plat<strong>for</strong>m e<br />

LACP on <strong>Force10</strong> systems can be configured to be hitless. When configured as hitless, <strong>the</strong>re is no<br />

noticeable impact on dynamic LAG state upon an RPM failover. Critical LACP state in<strong>for</strong>mation<br />

is synchronized between <strong>the</strong> two RPMs. See Hitless Feature Definition on page 383.<br />

216 Link Aggregation Control Protocol (LACP)

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

Saved successfully!

Ooh no, something went wrong!