Send documentation comments to mdsfeedback-doc@cisco.com
23-22
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
Chapter 23 Configuring PortChannels
PortChannel Protocols
Note Autocreation is not supported as of MDS NX-OS Release 4.1(1b) and later.
About Autocreation
The autocreation protocol has the following functionality:
• A port is not allowed to be configured as part of a PortChannel when the autocreation feature is
enabled. These two configurations are mutually exclusive.
• Autocreation must be enabled in both the local and peer ports to negotiate a PortChannel.
• Aggregation occurs in one of two ways:
–
A port is aggregated into a compatible autocreated PortChannel.
–
A port is aggregated with another compatible port to form a new PortChannel.
• Newly created PortChannels are allocated from the maximum possible PortChannel (128 for
Generation 1 or a combination of Generation 1 and Generation 2 switches, or 256 for Generation 2
switches) in a decreasing order based on availability. If all 128 (or 256) numbers are used up,
aggregation is not allowed.
• You cannot change the membership or delete an autocreated PortChannel.
• When you disable autocreation, all member ports are removed from the autocreated PortChannel.
Table 23-2 Channel Group Configuration Differences
User-Configured Channel Group Autocreated Channel Group
Manually configured by the user. Created automatically when compatible links come
up between two compatible switches, if channel
group autocreation is enabled in all ports at both
ends.
Member ports cannot participate in autocreation
of channel groups. The autocreation feature
cannot be configured.
None of these ports are members of a
user-configured channel group.
You can form the PortChannel with a subset of the
ports in the channel group. Incompatible ports
remain in a suspended or isolated state depending
on the ON or ACTIVE mode configuration.
All ports included in the channel group participate
in the PortChannel—no member port becomes
isolated or suspended; instead, the member port is
removed from the channel group when the link is
found to be incompatible.
Any administrative configuration made to the
PortChannel is applied to all ports in the channel
group, and you can save the configuration for the
PortChannel interface.
Any administrative configuration made to the
PortChannel is applied to all ports in the channel
group, but the configurations are saved for the
member ports; no configuration is saved for the
PortChannel interface. You can explicitly convert
this channel group, if required.
You can remove any channel group and add
members to a channel group.
You cannot remove a channel group, or add/remove
any of its members. The channel group is removed
when no member ports exist.
To Next Page
Loading...
Need help?
General
