In this lab I try to figure out back to back Switch VPC between 2 NX7K Switch named : Leaf01 and Leaf 02.
Most Important port must be there is :
- Keep Alive Port: this port function to take care heard beat between to switch, this keep-alive port must dedicated VRF in this example I use MGMT0 port because its already its own vrf by default
- VPC Peer-Link : The vPC peer link is the link used to synchronize states between the vPC peer devices. The vPC peer link carries control traffic between two vPC switches and also multicast, broadcast data traffic. In some link failure scenarios, it also carries unicast traffic. You should have at least two 10 Gigabit Ethernet interfaces for peer links. ( got this from http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/configuration_guide_c07-543563.html
Configuration :
conf t feature VPC feature LACP vpc domain 10 peer-switch peer-keepalive destination 192.168.1.1 source 192.168.1.2 delay restore 150 peer-gateway ip arp synchronize interface port-channel1 description Link_to_Leaf02 switchport mode trunk switchport trunk allowed vlan 890,900 spanning-tree port type network vpc peer-link Keep Alive link --------------- interface mgmt0 description vPC peer-keepalive vrf member management << Need to used separated VRF to manage keep-alive, we can use any interface we have rather than MGMT0 ip address 192.168.1.2/30 Peer Link ------------- interface port-channel1 vpc peer-link Trunk and Access-link ----------------------------- Trunk: interface port-channel11 switchport mode trunk speed 10000 vpc 11 Access: interface port-channel23 switchport access vlan 890 spanning-tree port type edge speed 10000 vpc 23 interface Ethernet1/22 description Link_to_MGT002-C3850-UDC1-LT01NWB01 switchport mode trunk switchport trunk allowed vlan 890 !! port e1/22 call orphand port because its not member of VPC community Note for Trunk: Leaf01# sh port-channel sum interface po11 | beg Group Group Port- Type Protocol Member Ports Channel ---------------------------------------------------------------------------- 11 Po11(SU) Eth LACP Eth1/30(P) Leaf02# sh port-channel sum interface po11 | beg Group Group Port- Type Protocol Member Ports Channel ---------------------------------------------------------------------------- 11 Po11(SU) Eth LACP Eth1/30(P)
port doesn’t need to be same the more important is it have same VPC# (vpc 11).
verification command using :
- show VPC brief : to check summary VPC
- show orphand-port : to check who member orphand ports / port not member for VPC.
- sh vpc peer-keepalive : this is impportant for troubleshooting that display any keep alive to its neighboor
Reference:
- http://jasonnash.com/2009/08/10/vpc-virtual-port-channel-and-the-nexus-platform/
- http://www.netcraftsmen.com/how-vpc-works/
- http://orbit-computer-solutions.com/Understanding-and-Configuring-EtherChannel.php#sthash.xzIc1SR4.dpuf
- http://packetlife.net/blog/2012/may/7/some-cisco-nexus-design-considerations/
- https://www.fir3net.com/Switches/Cisco/cisco-vpc.html
- http://www.netcraftsmen.com/configuring-back-to-back-vpcs-on-cisco-nexus-switches/