Cisco Nexus 93180YC-FX3 and VPC

[JCAA]

Hi

I would like to have information regarding configuration for Nexus 93180YC-FX3 switches. I'm not familar with Nexus family (I managed until now only Catalyst). 

We plan to deploy this model of switch (93180YC-FX3 ) to connect our new Dell VxRail infrastructure (4 servers). My question is about "stack" approach. With Calatyst, I kwnow we can connect switches together with stack module and create a logical switch. When I apply a configuration, this conf is apply on the logical switch (with x physical member switches). 

I read some documents regarding Nexus and if I understand, for this switch family, the "stack" concept is different without logical switch such as we have with Catalyst. For Nexus family, we talk about VPC based on aggregate link between physical switches in a same domain. In this case, each modification must be apply on each physcal switch ? For example, if I have  93180YC-FX3-sw1 and 93180YC-FX3-sw2 with VPC configured between these switches, if I need to add VLAN, I need to apply the new vlan configuration on 93180YC-FX3-sw1 and apply the same command on 93180YC-FX3-sw2 ? There is no logical approach ? 

Thank you for your help

[MHM Cisco World]

you add two vlan to both NSK and you use HSRP 
the host in this vlan will use HSRP VIP 
in normal two SW only the active is forward traffic (have the VIP IP and have vMAC of this VIP of HSRP)
in NSK both SW is active and standby forward traffic (both have VIP IP and have vMAC of this VIP of HSRP)

MHM

[M02@rt37]

Hello @JCAA 

Yes, the Nexus 93180YC-FX3 switches belong to the Nexus family, and they use Virtual PortChannel, called 'vPC',  for achieving high availability and load balancing between the switches. Unlike the Catalyst switches, the Nexus switches don't use the traditional stacking concept. Instead, they rely on vPC to create a multi-chassis system.

In a vPC setup, the switches are connected using a peer link, forming a vPC domain. The connected devices, like your Dell VxRail infrastructure, can then connect to both switches as if they are connected to a single logical switch. This provides redundancy and load balancing.

In a vPC setup, you need to apply the configuration on each physical switch. This is because each switch is an independent entity, and while they work together in a vPC domain, they still have their own individual configurations.

So, if you want to add a VLAN, for example, you would need to configure it on both 93180YC-FX3-sw1 and 93180YC-FX3-sw2. 

Note that you can "associate" vPC and HSRP together ; it's a common practice to provide both high availability and load balancing in a network. You can adjust the HSRP priorities to control which switch becomes the primary router for a particular VLAN. The switch with the higher priority will be the primary router.

Design and Configuration Guide: Best Practices for Virtual Port Channels (vPC) on Cisco Nexus Series Switches