Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 94 of 119
vPC Baseline Configuration
vPC Roles and Priority
vPC needs to be enabled on both vPC peers:
nexus5000(config)# feature vpc
You need to define a domain and configure priorities to define primary and secondary roles in the vPC
configuration on both vPC peers. The lower number has higher priority.
Note that the role is nonpreemptive, so a device may be operationally primary but secondary from a configuration
perspective.
nexus5000(config)# vpc domain 2
nexus5000-1(config-vpc-domain)# role priority 100
nexus5000-2(config-vpc-domain)# role priority 110
vPC Domain ID
When configuring the vPC domain ID, make sure that this ID is different from the one used by a neighboring vPC-
capable device with which you may configure a double-sided vPC. This unique ID is needed because the system
ID (see the discussion of LACP earlier in this chapter) is derived from the MAC address ID of the switch, and for
vPC this MAC address is derived from the domain ID. As a result, in a back-to-back vPC configuration, if the
neighboring switches use the same domain ID, a conflicting system ID may occur in the LACP negotiation, which
may cause an unsuccessful LACP negotiation.
vPC Peer Link
The vPC peer link connects the vPC peers and carries all access VLANs (to be defined by the user). This link also
carries additional traffic that the user does not need to define: specifically, BPDUs, IGMP reports, and MAC
address table synchronization messages.
This PortChannel should be configured to trunk all VLANs, so do not clear VLANs on this link because you will
have to add them manually anyway.
nexus5000(config)# interface port-channel10
nexus5000(config-if)# vpc peer-link
nexus5000(config-if)# switchport mode trunk
nexus5000(config-if)# switchport trunk allowed vlan <all access vlans>
By default, making the PortChannel a peer link also enables Bridge Assurance.
Do not enable loop guard on this PortChannel.
Repeat the preceding configurations on both vPC peers.
To reduce the amount of multicast traffic sent over the peer link, you need to first verify whether there are orphan
ports on each vPC device, and if there are, you need to make sure that they are not multicast receivers. If they are,
you can then configure the following:
no ip igmp snooping mrouter vpc-peer-link
Repeat the configuration on both vPC peers.