The biggest limitation to a classic port-channel communication is that port-channel operates only between two devices. To overcome this limitation, NX-OS has a technology called virtual Port Channel (vPC). A pair of switches acting as a vPC peer endpoint look like a single logical entity to port-channel attached devices; the two devices that act as the logical port-channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by port-channel, e.g loop management.
A virtual port channel (vPC) allows links that are physically connected to two different Cisco Nexus 7000 Series devices to appear as a single port channel by a third device. The third device can be a switch, server, or any other networking device that supports port channels. You can use only Layer 2 port channels in the vPC. A vPC domain is associated to a single VDC, so all vPC interfaces belonging to a given vPC domain must be defined in the same VDC. You must have a separate vPC peer-link and peer-keepalive link infrastructure for each VDC deployed. Consolidating a vPC pair (two vPC peer devices of the same domain) in two VDCs of the same physical device is not supported. The vPC peer link must use 10-Gigabit Ethernet ports for both ends of the link or the link will not form.
vPC Control Plane Recommendations
For the Peer Link, it is good to use two 10GbE ports on separate line cards for resilent connectivity.
Also, for the Peer Link, make sure that the ports are in dedicated mode (not Shared).
If using the Management Interface for Peer-Keepalive traffic, the management interface should be connected to a Layer 2 management switch, not back to back.
The Peer Keepalive traffic should be over a separate keepalive link and not over the Peer Link.
vPC Member Connectivity Recommendations
Make sure to dual attach all devices into the vPC Domain.
It is good to use LACP for the Port Channels of vPC Member ports.
vPC Spanning Tree Recommendations
Check that the Spanning Tree parameters match across vPC peers in accordance with vPC requirements.
Do not use Bridge Assurance feature on vPC Member ports.
Use Bridge Assurance feature on vPC Peer Link.
Ensure all switches in the Layer 2 domain are using Rapid-PVST to avoid slow STP convergence time.
Configure Portfast on Edge ports, to avoid slow STP convergence.
vPC Layer 3 Connectivity Recommendations
Use separate layer 3 links to connect routers to the vPC Domain.
Enable Layer 3 routing between vPC peers over a separate layer 3 link.
Do not enable routing over vPC for vPC members. In the DCI environment, use HSRP tracking to ensure Layer 3 failover between Data Center.
Do not use Link tracking for HSRP, use extended Object tracking.
Hello, Can someone give me simple and clearcut explanation pdf to understand multi-pod and multi-site features? differences between multi-pod and multi-site?how they work?how to configure them ? thank you very much
Hello,we have two pairs of Nexus 5672UP (one pair/site). They are running 7.3(3)N1(1) with LAN base license LAN_BASE_SERVICES_PKG. We want to configure Switch-to-Switch encryption between the two sites, by using TrustSec MacSec (Switch-to-Switch link secu...
Hi, I'm trying to understand under which scenarios it is recommended to enable GARP (and hence, ARP Floding). According to the ACI Fabric Endpoint Learning White Paper: Cisco ACI can detect MAC and IP address movement between leaf switch po...
HiI have a Problem in symmetric hashing on port channel in nexus 3172PQ.In my design i want to use two Nexus 3172PQ that ether channel together. between these switches, there is a layer 2 devices that capture traffic flow. But when enable port channel on ...
Hello, we have a DCNM 11.1(1) classic LAN installation. On our environment we have Nexus 5K with FEX N2K-C2248TP-E-1GE and Nexus 7K with FEX N2K-C2348TQ-10G-E. DCNM Monitor > LAN > Ethernet shows the interfaces for the N2K-C2248TP-E-...