vPC Best Practices for Nexus 3K and non NX-OS device.

[mhiyoshi]

Dear all 

I have been investigating the above solution however I can not find the exact document so I have created this discussion. 

So basically if Nexus vPC support switch can be conntected with non-NX-OS switch such as Catalyst switch. other vendors, or just virtual swtch etc. 

Then these devices are defined nomally Non-LACP-compliant right?

Cisco's recommendation is to set "no lacp graceful-convergence" for everything except NX-OS devices. however are there any other related recommendation between Neuxs3K and Non-NX-OS Switches? 

According to the CCO within my investigation. except to turn off the lacp graceful-convergence I can not find at the moment.

[Nexus, LACP, Graceful Convergence]
https://supportforums.cisco.com/t5/server-networking/nexus-lacp-graceful-convergence/td-p/2908703

The following is the basic vPC design recommendation in my understanding.

[vPC Best Practices for Nexus 7000 and 5000]
https://supportforums.cisco.com/t5/data-center-documents/vpc-best-practices-for-nexus-7000-and-5000/ta-p/3149258

So I appreciate if there are any information related to this.

Best Regards,

Masanobu Hiyoshi

[Mark Malone]

So basically if Nexus vPC support switch can be conntected with non-NX-OS switch such as Catalyst switch. other vendors, or just virtual swtch etc. 

Then these devices are defined nomally Non-LACP-compliant right?

i have loads of different types of switches connected into my DC , from 36s, 38s to my vpc setups in opur DC regions globally , i only use LACP on these and would not use on mode and specifcally i dont use PAGP , my understanding of LACP non compliant is firewalls and load balancers connected , we ne

when im connecting aything lacp to my nexus kit i always use this command to make sure the packets are going back and forth as its forming

xxxxxx# sh lacp counters interface port-channel 1
                    LACPDUs         Marker      Marker Response    LACPDUs
Port              Sent   Recv     Sent   Recv     Sent   Recv      Pkts Err
---------------------------------------------------------------------
port-channel1
Ethernet1/45       694383 694376   0      0        0      0        0
Ethernet1/46       694383 694376   0      0        0      0        0
Ethernet1/47       694385 694374   0      0        0      0        0
Ethernet1/48       694385 694374   0      0        0      0        0

convergence command is on by default and i never ran into any issues and always left it on but i always use this on the pos too

no lacp suspend-individual

Default PO

interface port-channel2
  description xxxxxxxxxxxxxxx
  switchport
  switchport mode trunk
  no switchport monitor
  no switchport dot1q ethertype
  no switchport priority extend
  priority-flow-control mode auto
  no lacp suspend-individual
  lacp min-links 1
  lacp max-bundle 16
  no port-channel port load-defer
  lacp fast-select-hot-standby
  lacp graceful-convergence
  no switchport block unicast
  no switchport block multicast
  no hardware multicast hw-hash
  no hardware vethernet mac filtering per-vlan
  switchport trunk allowed vlan 2,10-11,17-18,20,28,31,33-34,36-39,48,50,64-65,70,72,74,76,78,80,90-96,102-103,105,107,226,400,1226,2224
  spanning-tree port-priority 128
  spanning-tree cost auto
  spanning-tree link-type auto
  spanning-tree port type normal
  no spanning-tree bpduguard
  no spanning-tree bpdufilter
  logging event port link-status
  logging event port trunk-status
  speed 10000
  duplex auto
  flowcontrol receive off
  flowcontrol send off
  negotiate auto
  mtu 1500
  delay 1
  snmp trap link-status
  bandwidth 40000000
  no bandwidth inherit
  storm-control broadcast level 100.00
  storm-control multicast level 100.00
  storm-control unicast level 100.00
  no shutdown lan
  load-interval counter 1 30
  load-interval counter 2 300
  no load-interval counter 3
  medium broadcast
  vpc 2
  no shutdown

without sh run all int po2

interface port-channel2
  description xxxxxxx
  switchport mode trunk
  no lacp suspend-individual
  switchport trunk allowed vlan 2,10-11,17-18,20,28,31,33-34,36-39,48,50,64-65,70,72,74,76,78,80,90-96,102-103,105,107,226,400,1226,2224
  logging event port link-status
  logging event port trunk-status
  speed 10000
  vpc 2

[mhiyoshi]

Hi Mark

Thank you very much. Well I have read your information and I appreiciate to ask more questions below.

＞my understanding of LACP non compliant is firewalls and load balancers connected

If I check the parameter on the Nexus port-channel it says Non-Nexus peer.
So in my understanding lacp graceful-convergence recommendation is to turn off with Non-Nexus devices right?

N3048-1(config)# int po10
N3048-1(config-if)# no lacp ?
graceful-convergence Configure port-channel lacp graceful convergence.
Disable this only with lacp ports connected to
Non-Nexus peer. Disabling this with Nexus peer can lead
to port suspension

>convergence command is on by default and i never ran into any issues and always left it on but i always use this on the pos too
>no lacp suspend-individual

I think by default lacp suspend-individual is disabled. but if it is enabled, what is the merit?

In my understanding if one of physical interfaces (example: E1/1, E1/2 : Po10) can not
receive LACP PDU then the status of the physical inteface (example: E1/1) should be change to suspend.

N3048-1(config-if)# lacp suspend-individual

N3048-1# sh run int po1
*omit
interface port-channel1
shutdown
switchport mode trunk
spanning-tree port type network
lacp suspend-individual
vpc peer-link

Best Regards,

Masanobu Hiyoshi

[jkilleda]

Hello Masanobu,

vPC Best Practices for Nexus 3K and non NX-OS device.
If you don't disable lacp graceful-convergence in non NX-OS device then there will be packet loss as it will move to standby state