Cisco Cisco Nexus 5010 Switch Guida Alla Progettazione

Page 23 of 32

After a port is defined as part of a vPC, any further configurations, such as enabling or disabling bridge assurance

or trunking mode, are performed under the interface port channel configuration mode. Trying to configure

spanning-tree properties for the physical interface instead of the PortChannel will result in an error message.

Orphaned Ports with non-vPC VLANs

As previously described, when the peer link is lost, vPC shuts down the SVI on the secondary switch and, as a

result, orphaned ports on the operational secondary may become isolated. For this reason you can either trunk the

non-vPC VLANs on a different link, or you should remove the non-vPC VLANs from this behavior, as described

next.

First, you may want to execute the following command to learn which ports are considered orphan ports from the

Cisco Nexus 7000 Series perspective:

Nexus7000#show vpc orphan-ports

Second, you can remove the non-vPC VLANs in the vPC domain configuration:

vpc domain 1

role priority 100

dual-active exclude interface-vlan <non-vPC VLANs>

peer-keepalive destination 192.168.1.2 source 192.168.1.1 vrf vpc-keepalive

HSRP

The use of HSRP in the context of vPC doesn’t require any special configuration. With vPC, only the active HSRP

interface answers ARP requests, but both HSRP interfaces (active and standby) can forward traffic.

If an ARP request coming from a server arrives on the secondary HSRP device, it is forwarded to the active HSRP

device through the peer link.

HSRP Configuration and Best Practices for vPC

The configuration on the primary Cisco Nexus 7000 Series looks like this:

interface Vlan50

no shutdown

ip address 10.50.0.251/24

hsrp 50

preempt delay minimum 180

priority 150

timers 1 3

ip 10.50.0.1

The configuration on the secondary Cisco Nexus 7000 Series looks as follows: