Cisco Nexus 5000 Series Release Notes for Release 5.0(3)N2(2) (June 2011)

Send documentation comments to [e-mail]
13
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(3)N2(2) and Release 5.0(3)N2(1)
Limitations
In a vPC configuration, the MTU per class needs to be consistent on both switches in the vPC
domain for the vPC peer link to come up. When upgrading/downgrading a working vPC setup
between pre-4.2(1)N1(1) and 4.2(1)N1(1) releases, the MTU is adjusted to make sure that the MCT
peer-link always comes up.
However if you add a peer-link between two switches in a vPC domain that are identically
configured (MTU in particular) with one switch running Cisco NX-OS Release 4.2(1)N1(1) and
another switch running an earlier release, then the vPC peer link does not come up because the MTU
is inconsistent between the two switches.
This is not an issue when upgrading or downgrading peer switches in a vPC domain; this is only an
issue when adding a peer link between two switches running Cisco NX-OS Release 4.2(1)N1(1) and
earlier releases that were not previously in the same vPC domain.
To resolve this issue, upgrade or downgrade one switch to match the version on the other switch and
reconfigure the MTU to be consistent on both sides. For details, see CSCtg27538.
• The channel-group configuration is not applied to the Cisco Nexus 2000 Series downlink interface
after downgrading to the Cisco NX-OS Release 4.1(3)N1(1) software. This issue occurs if the speed
1000 command is present under the context of the port channel. To work around this issue,
reconfigure the channel-group command after the system comes up and reapply the configuration
from the saved configuration in the bootflash. For details, see CSCtc06276.
• When a private VLAN port is configured as a TX (egress) SPAN source, the traffic seen at the SPAN
destination port is marked with the VLAN of the ingressed frame. There is no work around.
• In large-scale configurations, some Cisco Nexus 2000 Series Fabric Extenders may take up to 3
minutes to appear online after entering the reload command. A configuration can be termed large
scale when the maximum permissible Cisco Nexus 2000 Series Fabric Extenders are connected to a
Cisco Nexus 5000 Series switch, and all host-facing ports are connected and each host-facing
interface has a large configuration (that supports the maximum permissible ACEs per interface).
• The Cisco Nexus 2000 Fabric Extender does not support PVLANs over VLAN trunks used to
connect to another switch. The PVLAN trunks are used only on inter-switch links but the FEX ports
are only meant to connect to servers. Because it is not a valid configuration to have an isolated
secondary VLAN as part of a Fabric Extender port configured as a VLAN trunk, all frames on
isolated secondary VLANs are pruned from going out to a FEX.
• Egress scheduling is not supported across the drop/no-drop class. Each Fabric Extender host port
does not support simultaneous drop and no drop traffic. Each Fabric Extender host port can support
drop or no drop traffic.
• The Cisco Nexus 2148 Fabric Extender does not support frames with the dot1p vlan 0 tag.
• VACLs of more than one type on a single VLAN are unsupported. Cisco NX-OS software supports
only a single type of VACL (either MAC, IPv4, or IPv6) applied on a VLAN. When a VACL is
applied to a VLAN, it replaces the existing VACL if the new VACL is a different type. For instance,
if a MAC VACL is configured on a VLAN and then an IPv6 VACL is configured on the same VLAN,
the IPv6 VACL is applied and the MAC VACL is removed.
• A MAC ACL is applied only on non-IP packets. Even if there is a match eth type = ipv4 statement
in the MAC ACL, it does not match an IP packet. To avoid this situation, use IP ACLs to apply access
control to the IP traffic instead of using a MAC ACL that matches the EtherType to IPv4 or IPv6.
• Multiple boot kickstart statements in the configuration are not supported.
• If you remove an expansion module with Fibre Channel ports, and the cable is still attached, the
following FCP_ERRFCP_PORT errors are displayed:
2008 May 14 15:55:43 switch %KERN-3-SYSTEM_MSG: FCP_ERRFCP_PORT:
gat_fcp_isr_ip_fcmac_sync_intr@424, jiffies = 0x7add9a:Unknown intr src_id 42 - kernel