S e n d d o c u m e n t a t i o n c o m m e n t s t o n e x u s 5 k d o c s @ c i s c o . c o m
The correct VLAN tag is applied on the frame as it goes out the SPAN destination. The only
exception is if frames ingress on a SPAN source port on an invalid VLAN. In this case, vlan 0 will
be applied on a spanned frame.
•
RADIUS and AAA startup configuration is lost when you upgrade from 4.0(0)N based releases to
4.0(1a)N based releases and later releases or when you downgrade to 4.0(0)N based releases. Save
the startup configuration to bootflash memory before an upgrade or a downgrade, and restore it from
bootflash memory after the upgrade or downgrade.
Spanned Fibre Channel over Ethernet (FCoE) frames do not preserve original SMAC and DMAC
•
fields. The Ethernet header gets modified as the frame is spanned to the destination. The modified
header fields are displayed when monitored on the SPAN destination.
•
The CoS value in spanned Fibre Channel over Ethernet (FCoE) frames on the Ethernet SPAN
destination port does not match with the CoS value in the SPAN FCoE source frame. The CoS value
on the captured SPAN FCoE frame should be ignored.
•
Ethernet and Fibre Channel frames with bad CRC or invalid SOF and EOF are not dropped. The
Cisco Nexus 5000 Series switch operates in cut-through switching mode, so frames are forwarded
through the system before they are completely received. The Ethernet and Fibre Channel CRCs are
overwritten in the frame and the EOF code is set to EOFa. A downstream switch or the destination
end station will drop the bad frames.
The class-fcoe cannot be removed even if Fibre Channel is not enabled on a switch.
•
VACLs of more than one type on a single VLAN are unsupported. 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 gets 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 overcome this situation, use IP ACLs to apply
access control to IP traffic instead of using a MAC ACL that matches the Ethertype to Ipv4 or Ipv6.
If a port drains traffic at a rate less than 100 Kbps, it is errdisabled in 10 seconds to avoid buffer
•
exhaustion. However, if the drain rate is larger than 100 Kbps, the port may not be consistently
errdisabled within 10 seconds. This could cause ingress buffers to be exhausted leading to frames
being discarded. Use the shut command to disable the slow-draining port.
•
The multicast storm control functionality in the Nexus 5000 Series hardware does not distinguish
between IP, non-IP, registered, or unregistered multicast traffic. All multicast traffic is subject to a
single multicast storm control policer when configured.
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
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 41 - kernel
These messages are informational only, and result in no loss of functionality.
OL-16601-01
Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a)
Limitations
11
Stampa la pagina