Cisco Nexus Vpc Practical Series

Cisco Nexus Vpc
What you'll learn
Cisco Nexus VPC Deep Knowledge
NEXUS VPC Practicals
CISCO NEXUS VPC Design
All about the VPC Design
Requirements
CCNA DATA center
Description
I am a CCIE LAB certified Network Engineer. My CCIE number is 57391. I have been working in network for almost 10 years now. I have designed this CISCO Nexus VPC Series. In this vPC (Virtual Port-Channel), also known as multichassis EtherChannel (MEC) is a feature on the Cisco Nexus switches that provides the ability to configure a Port-Channel across multiple switches (i.e. vPC peers).vPC is similar to Virtual Switch System (VSS) on the Catalyst 6500s. However, the key difference between vPC and VSS is that VSS creates a single logical switch. This results in a single control plane for both management and configuration purposes. Whereas with vPC each switch is managed and configured independently. It is important to remember that with vPC both switches are managed independently. This means you will need to create and permit your VLANs on both Nexus switches. vPC Domain - Includes the vPC Peers, KeepAlive Links and the Port-Channels that use the vPC technology. vPC Peer Switch - The other switch within the vPC domain. Each switch is connected via the vPC peer link. It's also worth noting that one device is selected as primary and the other secondary. vPC Member Port - Ports included within the vPCs. vPC Peer-Keepalive Link - Connects both vPC peer switches and carries monitoring traffic to/from each peer switch. Monitoring is performed to ensure the switches are both operational and running vPC. vPC Peer Link - Connects both vPC peer switches and carries BPDUs, HSRPs, and MAC addresses to its vPC peer.
Who this course is for
Network Engineer working in DATA Center networks
Homepage