Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) Current Release: 4.0(1a)N1(1) -December 3, 2008 Part Number: OL-16601-01 G0 This document describes the features, caveats, and limitations for Nexus 5000 Series switches. Use this document in combination with documents listed in the “Related Documentation” section on page 23.
Contents Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Table 1 Online History Change Part Number Revision Date Description OL-16601-01 F0 September 29, 2008 Added information for Release 4.0(0)N1(2a). OL-16601-01 G0 December 03, 2008 Added information for Release 4.0(1a)N1(1). Contents This document includes the following sections: • Introduction, page 2 • New and Changed Features in NX-OS 4.0(1a)N1(1), page 3 • Release 4.
New and Changed Features in NX-OS 4.0(1a)N1(1) Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • Two expansion module slots that can be configured to support up to 12 additional 10 Gigabit Ethernet, Cisco Data Center Ethernet, and FCoE SFP+ ports, up to 16 Fibre Channel switch ports, or a combination of both. • Serial console port and an out-of-band 10/100/1000-Mbps Ethernet management port. • 1+1 redundant, hot-pluggable power supplies.
Release 4.0(1a)N1(1) Upgrade and Downgrade Issues Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m For more information about the features listed, refer to the documentation set listed in the“Related Documentation” section on page 23. Release 4.0(1a)N1(1) Upgrade and Downgrade Issues This section describes issues that you may encounter when you upgrade or downgrade the Cisco NX-OS software release on the Nexus 5000 Series switch.
Release 4.0(1a)N1(1) Upgrade and Downgrade Issues Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m The following table describes the changes to the priority flow control configuration. 4.0(0)-based releases Priority flow control is an interface level configuration. This CLI option is used to override results of DCBX negotiation. Priority flow control function is not aware of the EtherChannel. It strictly follows a per-member port configuration.
Changes to the FCoE Model and Related Configuration Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Fibre Channel Port Shutdown The following table describes the changes to the interface shutdown command syntax. 4.0(0)-based releases The system default switchport shutdown command causes all Fibre Channel ports, virtual or physical, to default to shutdown. 4.
Changes to the FCoE Model and Related Configuration Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m The changes to the virtual interfaces are described in the following topics: • Virtual Interface Groups, page 7 • Virtual Ethernet Interfaces, page 7 • Virtual Fibre Channel Interfaces, page 7 • VSAN-to-VLAN Mapping, page 8 Virtual Interface Groups In previous Cisco NX-OS 4.
Changes to the FCoE Model and Related Configuration Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m VSAN-to-VLAN Mapping In previous Cisco NX-OS 4.0(0)-based releases, FCoE had no dependence on the VLANs defined on the switch. In Release 4.0(1a)N1(1), each virtual Fibre Channel interface is associated with only one VSAN.
Limitations Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m interface vfc 1 no shutdown vsan database vsan 1 interface vfc 1 Upgrading to Cisco NX-OS Release 4.0(1a)N1(1) When you upgrade your Cisco Nexus 5000 Series switch to Cisco NX-OS Release 4.0(1a)N1(1) all virtual Fibre Channel and virtual Ethernet interface configuration will be lost because the applicable CLI is incompatible with the previous releases.
Limitations Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m was originally tagged or untagged, as it appeared in the SPAN source, is not preserved in the SPAN destination. The spanned traffic exiting the SPAN destination port always has the VLAN tag on it. 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.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Caveats This section includes the following topics: • Open Caveats, page 11 • Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1), page 17 • Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2a), page 18 • Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2), page 19 • Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1a), page 21 • Resolved Caveats—Cisco NX-OS Release 4.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • CSCsv56881 Symptom: Each Switched Virtual Interface (SVI) for inband management must be configured with a different IP address. IPv6 has an error check feature. When an administrator enters a duplicate IPv6 address across two SVIs, the software fails the command due to the duplicate address. A similar error check should exist for IPv4 address configuration on SVIs.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • CSCsu93313 Symptom: Within a configuration session, 125 unique VACLs are created with a total of 1023 TCAM entries.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Workaround: Use RADIUS for directed request authentication. • CSCsq76688 Symptom: The neighboring device for the Cisco Discovery Protocol (CDP) is not removed after shutting down the port for CDP hold time interval. Workaround: None. • CSCsl62545 Symptom: The fan LED on the Device Manager (DM) displays in amber color even though the fan is working properly. Workaround: None.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Workaround: Use the CLI to set the mgmt0 IP address. • CSCsm16222 Symptom: CFS does not support roles configuration distribution. Enter the show cfs application command to see the registered applications. Workaround: Any features not registered with CFS need to be configured locally on the switch. • CSCsl73766 Symptom: CFS does not support RADIUS configuration distribution.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m The problem occurs when you execute the following steps: • Delete all role scopes for a role. • Insert new role scopes for the same role. Workaround: Repeat the above steps once again.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m information that helps distinguish traffic for various VSANs. This applies to any Fibre Channel SPAN source. By default, EISL encap is not added and packets are sent out without a VFT header, and independent of the type of SPAN source port. For a Nexus 5000 Series switch, the switchport encap EISL command does not have any effect.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • CSCsv30392 Symptom: The Cisco Nexus 5020 switch has a Pktmgr memory leak in version 4.0(0)N1(2). This causes STP to stop functioning after awhile causing a Layer 2 Loop. After breaking the redundant connections, the switch is unable to be managed, due to a No buffer space available message. Condition: The Cisco Nexus 5020 switch is setup in a triangle topology with two 6500 switches.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • CSCsu32247 Symptom: The Nexus 5000 Series switch executes the power-on self-test (POST) at bootup to validate hardware integrity of the ASICs. When a Fibre Channel port is connected to a host bus adapter (HBA), the HBA driver can trigger a signal loss that causes a false failure to be reported by POST for one of the ASICs.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • CSCsq67305 Symptom: When the switch is operating in theN-port virtualization (NPV) mode, traffic may be disrupted on active Fibre Channel links if you enter the shutdown or no shutdown command on any of the NP mode uplink interfaces. The disruption also occurs if you change the interface mode of a port from F to NP or from NP to F.
Caveats Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • CSCsq39683 Symptom: Fibre Channel links with traffic running on it might generate syslog errors such as the following: 2008 May 21 15:08:55 switch %KERN-3-SYSTEM_MSG: FCP_ERRFCP_PORT: gat_fcp_isr_process_blk_intr@1441, jiffies = 0xb1cec:ISR threshold reached, reg_block = 0x8, num_regs = 6, idx = 0, src_bit = 11 - kernel There is no loss in functionality and these messages can be ignored.
Cisco Fabric Manager Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Cisco Fabric Manager Beginning with Cisco Fabric Manager release 3.4(1a), Nexus 5000 Series switches are supported by Fabric Manager. If you are deploying Nexus 5000 Series switches with FCoE, you should operate Fabric Manager in Display FCoE mode. Display FCoE mode displays additional tree nodes, menu items, toolbar buttons, and topology nodes and links related to FCoE.
Related Documentation Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m Open Caveats • CSCq57019 Symptom: The Fabric Manager N-Port Virtualization (NPV) Wizard does not list the Nexus 5000 Series switches that are operating in NPV mode. Workaround: None. • CSCsq06170 Symptom: In Fabric Manager, only one power supply is displayed for a Nexus 5000 Series switch with two power supplies.
Obtaining Documentation and Submitting a Service Request Se 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 x 5 0 0 0 - d o c f e e d b a ck @ c i s c o . c o m • Cisco Nexus 5000 Series Command Reference, Release 4.0 • Cisco Nexus 5000 Series Hardware Installation Guide, Release 4.
