Cisco vPC could be a virtual port-channel which permits links physically associated to two diverse switches to seem as a single gadget to a downstream gadget as portion of a single port-channel.

A vPC is designed on a Cisco Nexus switch and permits Layer 2 port-channels from a downstream gadget to span two partitioned switches. vPC comprises of two vPC peer switches associated by a vPC peer interface.

One switch is essential and the other is auxiliary. A vPC space is shaped by both Nexus switches. A Nexus can as it were be portion of one vPC space and as it were two switches can make up a vPC space.

Cisco vPC could be a virtual port-channel which permits links physically associated to two diverse switches to seem as a single gadget to a downstream gadget as portion of a single port-channel. A vPC is designed on a Cisco Nexus switch and permits Layer 2 port-channels from a downstream gadget to span two partitioned switches. vPC comprises of two vPC peer switches associated by a vPC peer interface. One switch is essential and the other is auxiliary.

A vPC space is shaped by both Nexus switches. A Nexus can as it were be portion of one vPC space and as it were two switches can make up a vPC space.

Components of a vPC

- One essential switch and one auxiliary switch (vPC peers)

- Layer 3 interface for peer-keepalives (settle dual-active scenarios)

- Duplicate port channel for a peer link between vPC peers.

- vPC port members forming the virtual Port Channel.

Configuration

Connect each switch together to make a vPC peer interface. You would like two 10 GbE interfaces. Connect the administration interfacing to each switch to create the vPC keepalive interface. You lose out on utilizing the administration interface. In my situation, these two Nexus switches will be racked together.

Enable the vPC

conf t

feature vpc

Configure the management surface.

switch1(config)#interface mgmt0 switch1(config-if)#ip address 192.168.1.1/30 switch1(config-if)#vrf member management switch2(config)#interface mgmt0 switch2(config-if)#ip address 192.168.1.2/30 switch2(config-if)#vrf member management

Create port-channel for the vPC peer link.

interface po24

switchport mode trunk

Add the vPC peer link interfaces as a member of the port-channel.

interface e1/22

channel-group 24 mode active

Now we convert the port-channel into a vPC peer link.

interface po24

vpc peer-link

The switch will change over the port-channel into a organize harbour sort for spanning-tree.

The as it were time activity ought to go over the vPC peer-link is on the off chance that the Nexus loses its upstream association.

Network would still be available through the peer switch but over the peer-link connection. Now we are going create a vPC domain which ought to be interesting within the layer 2 space. When characterizing a vPC space, you must indicate the peer keepalive goal and source addresses.

 

vPC Resources

http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/design_guide_c07-625857.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_vpc_ops.html

http://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf
https://mobileinfoworld.com/configuring-cisco-nexus-vpc/