A few things here.

You can check the Interface group status with

ifgrp show

Looking for all active members (full) and it show what ports are in the group. Ideally, you should see multimode_lacp. If not, another discussion! (like why not?)

You can enable CDP/LLDP on your NetApp nodes:

system node run -node * options cdpd.enable on ; options lldp.enable on

You may only need LLDP or CDP to talk to switches. Some may have only one or the other turned on. After enabling CDP/LLDP on the nodes, wait about 3 minutes for the communication to establish.

Check what is connected with

network device-discovery show

If you are getting results from BOTH CDP and LLDP, you can disable one or the other. CDP usually gives better info so if needed, disable LLDP

system node run -node * options lldp.enable off

Additionally to limit what you are looking at to CDP or LLDP:

network device-discovery show -protocol cdp network device-discovery show -protocol lldp

Adding another argument can also be useful:

network device-discovery show -fields device-ip

This will show you the reporting IP of the switches that the NetApp Ports connect to. Occasionally though, depending on the switch config, it may display false info (like 1.1.1.1)

Armed with the above info, you potentially know which switches the NetApp is connected to. Which ifgroups are in use and what ports they use.

You can add ports to an ifgrp. Configure the switch to add more ports. Note: Best practice is to ha 2, 4 or 8 ports in the group (not 3 or 5 or 6 or 7) Simply use the

ifgrp add-port

command to add ports to an existing group.

VLANs, depends on the switch config. If the ports are in TRUNK mode, then you can easily add VLANs to any port two ways to do this, creating vlans 123 and 345

network port vlan create -node nodex -port a0a -vlan-id 123 (to create vlan a0a-123) network port vlan create -node nodex -vlan-name a0a-345 (to create vlan a0a-345)

Another best practice with VLANs is if you have a native VLAN, it should not be tagged at the same time. i.e. port a0a with native vlan of 2 is fine but do not create a0a-2 at the same time. If the ports on the switch are not trunk ports, they will need to be in order to do VLANs. Otherwise, they are just access ports.

--tmac

*Tim McCarthy, **Principal Consultant*

*Proud Member of the #NetAppATeam https://twitter.com/NetAppATeam*

*I Blog at TMACsRack https://tmacsrack.wordpress.com/*

On Fri, Mar 8, 2019 at 9:41 AM Tony Bar tbar@berkcom.com wrote:

You can also view which switches the ports are connected to if cdp/lldp is enabled on the switches if you’re concerned about which ports are connected & where. You may need to have your network admin enable cdp/lldp on the switches.

One other thing to keep in mind is that many modern switches support LACP across switches if they are configured for it — for example Cisco has VPC, Arista uses mlag domains & so on.

Anyway the command to view switch info is:

`network device-discovery show -node *` Best of luck to you.

*Anthony Bar*

tbar@berkcom.com

*Berkeley Communications*

www.berkcom.com

On Mar 8, 2019, at 6:12 AM, Tony Bar tbar@berkcom.com wrote:

You can check this pretty easily with `net port show -port a0a`

*Anthony Bar*

tbar@berkcom.com

*Berkeley Communications*

www.berkcom.com

On Mar 8, 2019, at 2:51 AM, Alexander Griesser AGriesser@anexia-it.com wrote:

Alright – with regards to Chris‘ question: I did assume that a0a currently is not LACP or connected to a different set of switches, which is probably the reason, why you cannot just add the physical ports in a0b to the existing ifgrp a0a, right?

*Alexander Griesser*

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia-it.com

Web: http://www.anexia-it.com

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

*From:* Yuvaraja Shivaram yuvaraja.kishan@gmail.com *Sent:* Friday, March 8, 2019 11:48 AM *To:* Alexander Griesser AGriesser@anexia-it.com *Subject:* Re: please provide the complete steps for creating new lacp ports..

Thanks a lot Alexander for your update, since it is prod, i do not want to take any risk...

will send you the complete step before monday(may be tommorrow), let me know if i am missing anything in that..

Regards

Yuvaraja

On Fri, Mar 8, 2019 at 4:08 PM Alexander Griesser AGriesser@anexia-it.com wrote:

CDOT is non disruptive with most network operations, so you could either migrate all LIFs off from one physical node to the other one, reconfigure the interface group on node A then to be LACP with the new ports and move the LIFs back then, if what you’re trying to achieve is a seamless migration of your services to different physical ports with a different aggregation method.

You can use the same VLAN on both physical interfaces, of course – no problem and it won’t affect the availability of the first tagged interface on a0a.

*Alexander Griesser*

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia-it.com

Web: http://www.anexia-it.com

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

*From:* Yuvaraja Shivaram yuvaraja.kishan@gmail.com *Sent:* Friday, March 8, 2019 11:36 AM *To:* Alexander Griesser AGriesser@anexia-it.com *Cc:* toasters toasters@teaparty.net *Subject:* Re: please provide the complete steps for creating new lacp ports..

very good question...Alexander,

earlier we were using only 2 ports, leaving other 2 ports keeping idle, so we are configuring other 2 ports and configuring LACP out of it,,,as of now do not have any plan to use any other vlan id's other than 608, ,which is already functional in the interface group as a0a, so now that same vlan id can be used for the new interface group a0b...? will that create any outage (since i am not getting vlan add..options similar to 7mode)...

Regards

Raj,

On Fri, Mar 8, 2019 at 3:54 PM Alexander Griesser AGriesser@anexia-it.com wrote:

Hey,

why do you want to have the same VLAN on two different interface groups?

*Alexander Griesser*

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia-it.com

Web: http://www.anexia-it.com

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

*From:* toasters-bounces@teaparty.net toasters-bounces@teaparty.net *On Behalf Of *Yuvaraja Shivaram *Sent:* Friday, March 8, 2019 11:22 AM *To:* toasters toasters@teaparty.net *Subject:* please provide the complete steps for creating new lacp ports..

Hi All,

Is there any way to add vlan to existing vlan-id, just how we do at 7mode...

curretly we are using 9.4p1 cmode....

below vlan already exists....so now if i want to create a0b for the same vlan id 608, am not getting vlan add here, so..

if i use ,network port vlan create -node cluster-01 -vlan-name a0b-608... is there any outage to this id 608, which is already running in production...?

Network Network

Node VLAN Name Port VLAN ID MAC Address

---

cluster-01

   a0a-608

             a0a     608      xxxx

cluster-02

   a0a-608

             a0a     608     xxxx

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters