Ethernet Switches & Routers

Reply
Frequent Contributor
Posts: 90
Registered: ‎12-26-2010

control packet exchange off

I am looking at switch configuration requirements for vifs(netapp virtual interface) and see the following for static multimode

you switch must support "aggregates (but must not have control packet exchange for configuring an aggregate)"

what does this mean? Any one familiar with this concept/requirement

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: control packet exchange off

Hi

     Configure the switch with a static LACP on the ports you are connecting the Filer to.

Creating a Link Aggregation Group (LAG)

Before setting-up ports or configuring any other aspects of a LAG, you must create it as shown in the following

BigIron RX(config)# lag blue static

BigIron RX(config-lag-blue)#

Adding Ports to a LAG

A static or dynamic LAG can consist of from 2 to 20 ports of the same type and speed that are on any interface module within the BigIron RX chassis. A keep alive LAG consists of only one port.

To configure the static LAG named “blue” with two ports, use the following command:

BigIron RX(config)# lag blue static

BigIron RX(config-lag-blue)# ports ethernet 3/1 ethernet 7/2

Configuring the Primary Port for a LAG

In previous versions of the Multi-Service IronWare software, the lowest number port was assigned as the primary port in a trunk or LACP configuration. In version 02.6.00 and later, the primary port must be explicitly assigned. using the

Pimary port  command.

To designate the primary port for the static LAG “blue”, use the following command:

BigIron RX(config)# lag blue static

BigIron RX(config-lag-blue)# primary port 3/2

Deploying a LAG

After configuring a LAG, you must explicitly enable it before it takes begins aggregating traffic. This is

accomplished using the

deploy command within the LAG configuration. Once the deploy command is executed, the LAG is in the aggregating mode. Only the primary port within the LAG is available at the individual interface level. Any configuration performed on the primary port applies to all ports within the LAG. The running configuration will no longer display deployed LAG ports other than the primary port.

To deploy a LAG, at least one port must be in the LAG and the primary port must be specified for non keep-alive LAGs. Once a non keep-alive LAG is deployed, a trunk is formed. If there is only one port in the LAG, a single port trunk is formed. For a dynamic LAG, LACP is stared for each LAG port. For a keep-alive LAG, no trunk is formed and LACP is started on the LAG port.

You can deploy a LAG as shown in the following for the “blue” LAG:

BigIron RX(config)# lag blue static

BigIron RX(config-lag-blue)# deploy

Thanks

Michael.

Frequent Contributor
Posts: 90
Registered: ‎12-26-2010

Re: control packet exchange off

nice draft, but i feel i am still missing the control packet exchang off part

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: control packet exchange off

Ok sure

What Netapp are saying is that "do not configure you switch for active LACP as this sends control (LACP-BPDUs) packets as we do not support the form forming of LAG's in this way".

So by setting up a static LAG on both ends (switch end and Filer end) manualy (this is what a VIF is) we do not send any control packets.

Hope this helps.

Thanks

Michael.

Super Contributor
Posts: 1,087
Registered: ‎12-13-2009

Re: control packet exchange off

Hi SKT,

     Does this answer your question or would you like to go into it  a bit more?

Thanks

Michael.

Frequent Contributor
Posts: 90
Registered: ‎12-26-2010

Re: control packet exchange off

that helps; By the way netapp does support dynamic link-aggregate/LAG (with LACP); what i understand from u we should have either static or dynamic at both ends.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook