Send documentation comments to nexus5kdocs@cisco.com Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1a) Current Release: 4.0(1a)N1(1a) -April 23, 2009 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 26. Note Release notes are sometimes updated with new information about restrictions and caveats.
Contents Send documentation comments to nexus5kdocs@cisco.com Contents This document includes the following sections: • Introduction, page 2 • New and Changed Features in Cisco NX-OS Release 4.0(1a)N1(1a), page 3 • Release 4.
New and Changed Features in Cisco NX-OS Release 4.0(1a)N1(1a) Send documentation comments to nexus5kdocs@cisco.com Cisco Nexus 5010 Switch The Cisco Nexus 5010 is a 28-port switch. It is a 1RU, 10-Gigabit Ethernet, Cisco Data Center Ethernet, FCoE, and Fibre Channel switch providing more than 500-Gbps throughput with very low latency. It has the following features: • Twenty fixed 10-Gigabit Ethernet, Cisco Data Center Ethernet, and FCoE SFP+ ports.
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues Send documentation comments to nexus5kdocs@cisco.
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues Send documentation comments to nexus5kdocs@cisco.com • If the startup-config has an RBAC role configured with more than 35 rules, then after a downgrade to the 4.0(0)N1(2a) release, the show running-config command causes the vshd process to core dump. This is due to a caveat (CSCsy37432). The workaround is to remove rules from the roles configuration in a way that a role does not have more than 35 rules before downgrading to the 4.0(0)N1(2a) release.
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues Send documentation comments to nexus5kdocs@cisco.com The following table describes the changes to the interface level QoS service policy, 4.0(0)-based releases Interface level QoS service policy is not aware of the EtherChannel. QoS strictly follows a per-member port configuration. The only service policy supported on the interface level is egress queue scheduling. 4.0(1a)N1(1a) No configuration is allowed on member ports.
Release 4.0(1a)N1(1a) Upgrade and Downgrade Issues Send documentation comments to nexus5kdocs@cisco.
Changes to the FCoE Model and Related Configuration Send documentation comments to nexus5kdocs@cisco.com Changes to the FCoE Model and Related Configuration In the previous Cisco NX-OS 4.0(0)-based releases, the FCoE model allowed Ethernet and FCoE to co-exist on the interface. The virtual interfaces, virtual Ethernet and virtual Fibre Channel (VFC), did not affect each other. For example, if the virtual Ethernet interface was errdisabled, the VFC interface could still be up. With Cisco NX-OS Release 4.
Changes to the FCoE Model and Related Configuration Send documentation comments to nexus5kdocs@cisco.com Each virtual Fibre Channel interface is bound directly to an FCoE-enabled physical Ethernet interface in Release 4.0(1a)N1(1a).
Limitations Send documentation comments to nexus5kdocs@cisco.com interface vfc 1/1 no shutdown vsan database vsan 1 interface vfc 1/1 Release 4.0(1a)N1(1a) Converted Configuration vlan 101 fcoe vsan 1 interface Ethernet 1/1 switchport mode trunk switchport trunk native vlan 2 switchport trunk allowed vlan 2,101 spanning-tree bpduguard enable spanning-tree port type edge trunk interface vfc 1 no shutdown vsan database vsan 1 interface vfc 1 Upgrading from Cisco NX-OS 4.
Limitations Send documentation comments to nexus5kdocs@cisco.com 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.
Caveats Send documentation comments to nexus5kdocs@cisco.com Caveats This section includes the following topics: • Open Caveats, page 12 • Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1a), page 18 • Resolved Caveats—Cisco NX-OS Release 4.0(1a)N1(1), page 19 • Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2a), page 21 • Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(2), page 22 • Resolved Caveats—Cisco NX-OS Release 4.0(0)N1(1a), page 23 • Resolved Caveats—Cisco NX-OS Release 4.
Caveats Send documentation comments to nexus5kdocs@cisco.com • CSCsv70815 Symptom: The default VRF is the system default for a VRF setting. Ideally, applications using VRF (such as TACACS+) assume a default VRF value if a VRF configuration is not specified by the administrator. However, TACACS+ is not set up properly unless the default VRF is configured. Workaround: The Cisco Nexus 5000 Series switches support two possible VRFs, the default and the management.
Caveats Send documentation comments to nexus5kdocs@cisco.com • CSCsv00989 Symptom: The command show interface ethernet transceiver details may show all zero values for DOM-capable 1 G SFP. Workaround: None. • CSCsu48008 Symptom: When a Virtual Fibre Channel (VFC) interface is down, the fcIfOperStatusCause MIB object does not report the correct reason. Workaround: Get the OperStatus from the CLI using the show interface vfc x command.
Caveats Send documentation comments to nexus5kdocs@cisco.com Workaround: After you downgrade to the previous release and reload the switch, reconfigure any static IGMP groups configured over an Etherchannel. Alternately you can also do a copy startup running to reload the startup configuration. After that do a copy running startup to make sure the static IGMP entries are re added properly to the startup configuration.
Caveats Send documentation comments to nexus5kdocs@cisco.com • CSCsr64291 Symptom: When a port is congested due to traffic from multiple inputs, the traffic mapped to a user-defined QoS class can get discarded at a very slow rate (fewer frames per second) in spite of being configured with strict priority scheduling. Workaround: None. • CSCsr68690 Symptom: When an egress SPAN is configured on a port transmitting jumbo or large frames, the spanned frames are truncated to 2384 bytes. Workaround: None.
Caveats Send documentation comments to nexus5kdocs@cisco.com • CSCso65934 Symptom: Virtual interfaces are created by specifying the interface name in configuration mode. If the interface does not exist, the system creates the interface, and then enters interface configuration mode. If the user role prohibits access to that interface, this CLI is rejected and the user does not enter interface configuration mode, although the interface is created.
Caveats Send documentation comments to nexus5kdocs@cisco.com Workaround: Configure a shorter query interval on the IGMP router to reduce the time it takes for ip-multicast traffic to converge in this topology. • CSCsq35728 Symptom: When a SAN port channel is created, the following syslog message is displayed: 2008 May 20 06:09:13 switch %PORT_CHANNEL-3-MSG_SEND_FAILURE: failed to send MAP_PARAM_FROM_CHANNEL to sap 45: Broken pipe" There is no functionality loss and this message can be ignored.
Caveats Send documentation comments to nexus5kdocs@cisco.com Workaround: Before downgrading to the Cisco NX-OS 4.0(1a)N1(1) release, remove rules from the roles configuration such that a role does not have more than 67 rules. • CSCsv55655 Symptom: The Cisco Nexus 5000 Series switch Ethernet port is configured in the 1 G mode of operation using the speed 1000 command. It does not advertise and auto-negotiate the flow control configuration.
Caveats Send documentation comments to nexus5kdocs@cisco.com • CSCso91286 Symptom: When TACACS+ authentication is used to authenticate AAA users using ACS, the Cisco Nexus 5000 Series switch ignores the user to role binding information specified in the ACS. Users are logged in with their default roles. The default role for a new user is network-operator and for a user who is an administrator is network-admin.
Caveats Send documentation comments to nexus5kdocs@cisco.com • CSCsr39670 Symptom: Although SNMP notification is enabled on the switch, traps for the power supply and fan modules are not received. Workaround: None. • CSCsr47531 Symptom: When a VSAN is configured as SPAN source, traffic from all the member ports is spanned to the SPAN destination port. When a switch is rebooted, the VSAN SPAN source remains in the down state. Workaround: Delete and add the VSAN sources for the SPAN session.
Caveats Send documentation comments to nexus5kdocs@cisco.com • The syslog displays warnings at bootup. Although the hardware supports the 110 V input, the operating system incorrectly logs the warning message. • The show environment power command incorrectly displays the available power as a negative value. Workaround: The problem is not significant and the system operates normally with 110 V power supply input. There is no workaround to avoid the syslog message.
Caveats Send documentation comments to nexus5kdocs@cisco.com • CSCsq27576 Symptom: FC-SP authentication is supported only with a switch over the E/TE port. Authentication with native Fibre Channel (FC) and Fibre Channel over Ethernet (FCoE) initiator or target is not supported. Workaround: None. • CSCsq32710 Symptom: SNMP users configured with a user-defined roles cannot retrieve any Fibre Channel interfaces.
Cisco Fabric Manager Send documentation comments to nexus5kdocs@cisco.com no lldp receive no lldp transmit • CSCsq36609 Symptom: For a virtual Ethernet or virtual Fibre Channel interface configured as a SPAN source, changing the interface administrative state results in a memory leak. Deleting and adding SPAN sessions also causes memory leaks. The memory leaks eventually cause a switch reboot. Workaround: Avoid using virtual Ethernet and virtual Fibre Channel interfaces as SPAN sources.
Cisco Fabric Manager Send documentation comments to nexus5kdocs@cisco.com Zoning In the Edit Local Full Zone Database tool, virtual Fibre Channel interfaces must be specified using the Switch Port WWN method of adding members to a zone. In the Add Members to Zone dialog box, the Switch & Port method and the Domain & Port method are not supported for virtual Fibre Channel interfaces. Caveats This section lists the Cisco Fabric Manager caveats related to managing Nexus 5000 series switches.
Related Documentation Send documentation comments to nexus5kdocs@cisco.com 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, Release 4.0 • Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide, Release 4.
