We have standalone rackmounted dell servers and we want to use the load balancing Route based on Original port id. In order to accomplish the same we need to use LACP using vDS with Nexus9000 with vPC. Wanted to know whether this is supported
Nexus9000 VPC with LACP with Virtual Distributed switch in VMware using LACP with Loadbalancing selected as route based on virtual port. Please clarify.
You mention you want to use route based on originating port id? That is not an LACP mode and would be used with standalone ports (not a port-channel or vpc) on an esxi standard switch. I'm guessing you meant that is your current mode and you want to move to LACP in the vDS.
If so, then yes. LACP in a vDS to N9k vpc is supported. We run currently run in this configuration.
vPC LACP to vDS is supported, but you should load balance based on IP hash when using LACP or it really doesn't do you any benefit.
Please, could you send us a sample of your config.
We are trying setting up vPC LACP between n9K and DVS vsphere 6.7.
2 N9K, 4 ESX. Each ESX has got one port on each N9K.
Our config seems really good, but one port keeps getting on "Hot Standby", while the other one is Up in port-channel.
When shutting down the active port, the "hot standby" goes up into Port-channel. When no shut down on the previously shut down port, then, it is going to Hot standby.
So, I am not able to get both ports UP in the port-channel at the same time.
We have applied the same config for connecting to linux box or Xen server, with no problem. LACP gets both vPC ports active.
Finally, seems to be a bug on nexus device.
Cisco says we should disable graceful convergence on LACP when peer is not Nexus, in order to avoid some latency and loss of packets when link status change.
In our case, we have enabled graceful convergence.. and immediately, ESX hot standby interfaces become UP and part of the vPC.
Have a look at CSCuy84084 (applies to NX-OS too, not only ACI)