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 and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1) Current Release: 4.1(3)N1(1) -July 31, 2009 Part Number: OL-16601-01 H0 This document describes the features, caveats, and limitations for Cisco Nexus 5000 Series switches and the Cisco Necus 2000 Series Fabric Extenders.
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 G0 December 03, 2008 Added information for Release 4.0(1a)N1(1). OL-16601-01 H0 February 26, 2009 Added information for Release 4.0(1a)N2(1). OL-16601-01 F0 July 26, 2009 Added information for Release 4.1(3)N1(1).
Introduction 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 5020 Switch The Cisco Nexus 5020 is a 56-port switch. It is a two rack unit (2 RU), 10-Gigabit Ethernet, Cisco Data Center Ethernet, FCoE, and Fibre Channel switch that provides 1.04 terabits per second (Tbps) throughput with very low latency.
Introduction 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 Scaling across a multitude of 1-Gigabit Ethernet, 10-Gigabit Ethernet, unified fabric, rack, and blade server environments, the Fabric Extender is designed to simplify data center architecture and operations. The Fabric Extender integrates with its parent switch, allowing zero-touch provisioning as well as automatic configuration.
New and Changed Features in Cisco NX-OS Release 4.1(3)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 The Cisco Nexus 2148T Fabric Extender forwards all traffic to a parent Cisco Nexus 5000 Series switch over 10-Gigabit Ethernet fabric uplinks, allowing all traffic to be inspected by policies established on the Cisco Nexus 5000 Series switch. No software is included with the Nexus 2148T.
Cisco NX-OS Release 4.1(3) N1(1) Upgrade/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 Upgrading from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.1(3)N1-Based Releases When you upgrade your Cisco Nexus 5000 Series switch from Cisco NX-OS 4.0(1a)N1-Based Releases to 4.
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 Limitations This section describes the limitations in Nexus 5000 Series switches and the Cisco Nexus 2000 Series Fabric Extenders, Release 4.1(3)N1(1). • In large scale configurations some Cisco Nexus 2000 Series Fabric Extenders may take up to 3 minutes to appear online after a reload command is issued.
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 • 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.
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 11 and the switch port 1/5 sends multicast traffic on VLAN 11 in a multicast group, and hosts connected to FEX ports 100/1/3-12 are interested in receiving that mutlicast traffic (through IGMP), then that multicast traffic goes out on FEX ports 100/1/3-12, but not on 100/1/1-2.
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 • CSCta00231 Symptom: After a downgrade, the interface policy may silently get added to the system level without a warning message. This may change the entire qos queuing policy. Workaround: Remove the system policy BW/SPQ parameters, configure the queuing policy and add the parameters again to the interfaces.
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 • CSCsx60187 Symptom: Configure duplicate IP address for multiple SVI interfaces. Workaround: Do not configure two or more SVIs with the same IP address. • CSCsx80279 Symptom: When traffic is sent at line rate as a single burst, all addresses are not learned when egress interfaces are FEX facing ports. This problem does not occur if sustained traffic is sent for more than 0.4 seconds.
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: None. This is a display issue only. • CSCsx68778 Symptom: You cannot configure commands under the interface range Workaround: Configure command sunder HIF ports of one FEX at a time. • CSCsx60187 Symptom: Duplicate IP addresses are configured for multiple SVI interfaces. Workaround: Do not configure two more SVIs with the same IP address.
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 • CSCsu01188 Symptom: No traps are sent when SFPs for Gigabit Ethernet and 10-Gigabit Ethernet are removed or inserted. Workaround: None. • CSCsv56881 Symptom: Each Switched Virtual Interface (SVI) for inband management must be configured with a different IP address. IPv6 has an error check feature.
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 • CSCsq64251 Symptom: TACACS+ fails if the user name input at login initiates a directed request authentication. The syntax to authenticate a directed request to a switch is username@(IP address or name of TACACS+ server). Workaround: Use RADIUS for directed request authentication.
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 • 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 • CSCsq17571 Symptom: When an SNMP user creates or deletes virtual interface group (VIG), virtual Ethernet (VEth) or virtual FC (VFC) interfaces, the accounting log displayed by the show accounting log command does not get updated. Workaround: Use the CLI for the configuration, which will update the accounting log.
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 Ethernet SPAN destination port to SPAN Fibre Channel traffic. FCoE packet going out of the Ethernet SPAN destination port will contain VSAN information in the Ethernet VLAN tag. • CSCsv93278 Symptom:The logging server vrf command works only with the management vrf. There is no functional impact if the syslog is to be sent over management vrf. 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 • CSCsw64952 Symptom: If the Cisco Nexus 5000 Series switch has more than 3K STP instances and an STP hello time of 1 second is used in the Bridge assurance configuration, the STP may not converge. Workaround: Use aa STP hello time of 2 second in the Bridge Assurance mode.
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 • CSCsv24214 Symptom: When downgrading a Cisco Nexus 5000 Series switch from running a 4.0(1a)N1 image to a 4.0(0)N1(1) or 4.0(0)N1(1a) image, the startup configuration is not restored. This is caused by the defect CSCsq74395, which was resolved in 4.0(0)N1(2) and 4.0(0)N1(2a).
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 • CSCsw66216 Symptom: When member fex-fabric ports are added or removed from a channel-group, frames could be lost for few seconds until the Cisco Nexus 5000 Series switch and the Cisco Nexus 2000 Series Fabric Extender complete updating port-channel forwarding configurations.
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 • CSCsu66201 Symptom: If the name server IP address is unreachable, the TACACS daemon gets stuck trying to resolve the server names. While it is stuck, TACACS commands, including common commands such as show running-config and copy running-config startup-config, are not processed. Workaround: Fix the network connectivity to the name server IP address.
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: None. • 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.
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.
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 Related Documentation The Nexus 5000 Series documentation is available at the following URL: http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.html The following are related Cisco Nexus 5000 Series documents: • Cisco Nexus 5000 Series Switch CLI Software Configuration Guide , Cisco NX-OS Release 4.
