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.
Is the old Cisco Fabric manager the only GUI to manage my fabric? I'm upgrading to MDS 9148S switches and was under the impression there was a new way to manage the fabric, but all I can find is the old Fabric Manager.
We are Planning to have an upgrade on the Nexus 7000 to the version 7.3.3.D1.1.In our infrastructure, we have FEX , some of them are dual home and other are single Homed..As described in the link below the ISSU is not supported when we have Dual Home...
Please note, I am no where close to be a SAN expert/specialist... Here is the scenario:Customer has two DCs (Primary and DR). Both are using FC SAN for storage (Brocade 7800). Customer wants to migrate to ACI, ACI Multi-Site particularly. The connect...
Hello all,I have BGP configured on my Nexus 7010 and all seems to be working normally. But I am seeing a couple things that don't seem normal and am looking for inputs / suggestions. Here is my BGP config on the Nexus 7010router bgp 65172 route...
We are running an Oracle RAC database 2 node cluster on Cisco B200M4 / Firmware 3.2(3i)B / enic 22.214.171.124 / and see RX drops for one VNIC interface. We then have increased RX/TX queues, ring sizes and RSS in Ethernet Policy and will enable MTU 9000 t...