Send documentation comments to mdsfeedback-doc@cisco.com
23-8
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
Chapter 23 Configuring PortChannels
About PortChannels
• If you execute the write erase command on a 32-port switching module, and then copy a saved
configuration to the switch from a text file that contains the no system default switchport
shutdown command, you need to copy the text file to the switch again for the E ports to come up
without manual configuration.
• Any (or all) full line rate port(s) in the Cisco MDS 9100 Series can be included in a PortChannel.
• The host-optimized ports in the Cisco MDS 9100 Series are subject to the same PortChannel rules
as 32-port switching modules; only the first port of each group of 4 ports is included in a
PortChannel.
–
You can configure only the first port in each 4-port group as an E port (for example, the first
port in ports 1–4, the fifth port in ports 5–8, and so on). If the first port in the group is configured
as a PortChannel, the other three ports in each group (ports 2–4, 6–8, and so on) are not usable
and remain in the shutdown state.
–
If any of the other three ports are configured in a no shutdown state, you cannot configure the
first port to be a PortChannel. The other three ports continue to remain in a no shutdown state.
F and TF PortChannel Restrictions
The following guidelines and restrictions are applicable for F and TF PortChannels:
• The ports must be in F mode.
• Automatic creation is not supported.
• ON mode is not supported. Only ACTIVE-ACTIVE mode is supported. By default, the mode is
ACTIVE on the NPV switches.
• Devices logged in through F PortChannel on an MDS switch are not supported in IVR non-NAT
configuration. The devices are supported only in IVR NAT configuration.
• Port security rules are enforced only on physical PWWNs at the single link level.
• FC-SP authenticates only the first physical FLOGI of every PortChannel member.
• Since the FLOGI payload carries only the VF bits to trigger the use of a protocol after the FLOGI
exchange, those bits will be overridden. In the case of the NPV switches, the core has a Cisco WWN
and will try to initiate the PCP protocol.
• The name server registration of the N ports logging in through an F PortChannel will use the FWWN
of the PortChannel interface.
• DPVM configuration is not supported.
• The PortChannel port VSAN cannot be configured using DPVM.
• The Dynamic Port VSAN Management (DPVM) database will be queried only for the first physical
FLOGI of each member, so that the port VSAN can be configured automatically.
• DPVM does not bind FC_IDs to VSANs, but PWWNs to VSANs. It will be queried only for the
physical FLOGI.
To Next Page
Loading...
Need help?
General
