Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 103 of 119
Note that both Cisco Nexus 5000 Series Switches can see every host interface on any fabric extender, and that
they view these single HIFs as if they belonged to a PortChannel; in fact, the configuration on both Cisco Nexus
5000 Series Switches must match. Configurations that do not match for the same host port result in a vPC
inconsistency.
If an interface is not active, the configurations may not be matched, as in this example:
tc-nexus5k01# show int eth100/1/35
Ethernet100/1/35 is down (inactive)
tc-nexus5k01# show vpc consistency-parameters int eth100/1/35
Legend:
Type 1 : vPC will be suspended in case of mismatch
Name Type Local Value Peer Value
------------- ---- ---------------------- -----------------------
Speed 1 1000 Mb/s 1000 Mb/s
Duplex 1 full full
Port Mode 1 access trunk
Shut Lan 1 No No
Allowed VLANs - 50 23-24,30,50,60
If you are using the Cisco Nexus 2248TP or 2232PP, you can also configure fabric extender active-active HIF ports
in PortChannel mode as follows:
interface Ethernet101/1/35 - 36
description tc-esx07
switchport mode access
spanning-tree port type edge
channel-group 7 mode active
vPC Host PortChannels with Fabric Extender Active-Active Topology
On both Cisco Nexus 5000 Series Switches, you need to configure the same PortChannel, but you do not need to
define this as a vPC, as shown in Figure 44:
Nexus 5k01:
interface eth100/1/1-2
channel-group 1001
interface eth101/1/1-2
channel-group 1001
interface port-channel 1001
<other po configs>
Nexus 5k02:
interface eth100/1/1-2
channel-group 1001