Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch
Design Guide
© 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 9 of 15
The configuration of the hashing algorithm follows the same syntax in Cisco NX-OS, but on the Cisco Nexus 7000
Series, it can be specified per module:
Series, it can be specified per module:
NXOS : (config)# port-channel load-balance ethernet { various options } [module]
The show command is slightly different between Cisco NX-OS and Cisco IOS Software:
NXOS : # show port-channel summary
Catalyst IOS: # show etherchannel summary
Commands Specific to the Cisco Nexus 1000V Series
On the Cisco Nexus 1000V Series Switches, the port channel configuration varies slightly from the regular port
channel configuration, mostly because dual-homed VMware ESX servers require that the channel be split between
two upstream switches.
channel configuration, mostly because dual-homed VMware ESX servers require that the channel be split between
two upstream switches.
The syntax is as follows:
channel-group auto mode {on | active | passive} [subgroup cdp]
If the network adapters on the VMware ESX host are connected to a single upstream switch, the port channel
configuration is very simple:
configuration is very simple:
n1000v(config)# port-profile uplink-profile
n1000v(config-port-prof)# channel-group auto
n1000v(config-port-prof)# capability uplink
If the network adapters on the ESX host are connected to two upstream switches that are virtual PortChanel (vPC)-
or VSS-capable, the port channel configuration is a regular port-channel configuration as follows:
or VSS-capable, the port channel configuration is a regular port-channel configuration as follows:
n1000v(config)# port-profile uplink-profile
n1000v(config-port-prof)# channel-group auto
n1000v(config-port-prof)# capability uplink
If the network adapters on the ESX host are connected to two upstream switches that are neither vPC- nor VSS-
capable, and if these adapters can use Cisco Discovery Protocol, the configuration is as follows:
capable, and if these adapters can use Cisco Discovery Protocol, the configuration is as follows:
n1000v(config)# port-profile uplink-profile
n1000v(config-port-prof)# channel-group auto subgroup cdp
n1000v(config-port-prof)# capability uplink
If the network adapters on the ESX host are connected to two upstream switches that are not vPC or VSS-capable
and do not use Cisco Discovery Protocol, the configuration is as follows:
and do not use Cisco Discovery Protocol, the configuration is as follows:
n1000v(config)# port-profile uplink-profile
n1000v(config-port-prof)# channel-group auto subgroup cdp
n1000v(config-port-prof)# capability uplink
n1000v(config)# interface Ethernet <ESX ports going to switch 1>
n1000v(config-if-range)# sub-group-id 0
n1000v(config-if-range)# interface Ethernet <ESX ports going to switch 2>
n1000v(config-if-range)# sub-group-id 1
Notice that the cdp keyword is used even when the upstream devices don’t run Cisco Discovery Protocol. The
manual configuration of the sub-group-id ensures that the links are correctly split into two different port channels,
one per upstream switch (group 0 to switch 1, group 1 to switch 2).
manual configuration of the sub-group-id ensures that the links are correctly split into two different port channels,
one per upstream switch (group 0 to switch 1, group 1 to switch 2).