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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Important Points to Remember<br />

• LACP enables you to add members to a port channel (LAG) as long as it has no static members.<br />

Conversely, if <strong>the</strong> LAG already contains a statically defined member (channel-member command),<br />

<strong>the</strong> port-channel mode command is not permitted.<br />

• A static LAG cannot be created if a dynamic LAG using <strong>the</strong> selected number already exists.<br />

• No dual membership in static and dynamic LAGs:<br />

• If a physical interface is a part of a static LAG, <strong>the</strong>n <strong>the</strong> command port-channel-protocol lacp<br />

will be rejected on that interface.<br />

• If a physical interface is a part of a dynamic LAG, it cannot be added as a member of a static<br />

LAG. The command channel-member gigabite<strong>the</strong>rnet x/y will be rejected in <strong>the</strong> static LAG<br />

interface <strong>for</strong> that physical interface.<br />

• A dynamic LAG can be created with any type of configuration.<br />

• There is a difference between <strong>the</strong> shutdown and no interface port-channel:<br />

— The shutdown command on LAG “xyz” disables <strong>the</strong> LAG and retains <strong>the</strong> user commands.<br />

However, <strong>the</strong> system does not allow <strong>the</strong> channel number “xyz” to be statically created.<br />

— The command no interface port-channel channel-number deletes <strong>the</strong> specified LAG, including a<br />

dynamically created LAG. This command causes all LACP-specific commands on <strong>the</strong> member<br />

interfaces to be removed. The interfaces are restored to a state that is ready to be configured.<br />

Note: There will be no configuration on <strong>the</strong> interface since that condition is required <strong>for</strong> an<br />

interface to be part of a LAG.<br />

• Link dampening can be configured on individual members of a LAG. See Link Dampening on<br />

page 276 <strong>for</strong> more in<strong>for</strong>mation.<br />

• LACP cannot add an interface to a LAG if one of <strong>the</strong> LAG members is shut down on <strong>the</strong> remote<br />

interface. If a remote LAG member is shut down, Message 17 appears on <strong>the</strong> local system when you<br />

attempt to add a member. In this case, enable all members of <strong>the</strong> LAG on <strong>the</strong> remote system, and <strong>the</strong>n<br />

add any new members on <strong>the</strong> local system.<br />

Message 17 LACP Remote Port Down Error Message<br />

% Error: This port property does not match with o<strong>the</strong>r LAG member.<br />

LACP modes<br />

<strong>FTOS</strong> provides <strong>the</strong> following three modes <strong>for</strong> configuration of LACP:<br />

• Off—In this state, an interface is not capable of being part of a dynamic LAG. LACP does not run on<br />

any port that is configured to be in this state.<br />

• Active—In this state, <strong>the</strong> interface is said to be in <strong>the</strong> “active negotiating state.” LACP runs on any<br />

link that is configured to be in this state. A port in Active state also automatically initiates negotiations<br />

with o<strong>the</strong>r ports by initiating LACP packets.<br />

• Passive—In this state, <strong>the</strong> interface is not in an active negotiating state, but LACP will run on <strong>the</strong> link.<br />

A port in Passive state also responds to negotiation requests (from ports in Active state). Ports in<br />

Passive state respond to LACP packets.<br />

210 Link Aggregation Control Protocol (LACP)

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

Saved successfully!

Ooh no, something went wrong!