Send documentation comments to nexus5kdocs@cisco.com Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(2)N1(1) and NX-OS Release 5.0(2)N2(1) Release: 5.0(2)N2(1) December 20, 2010 Part Number: OL-22747-02 This document describes the features, caveats, and limitations for Cisco Cisco Nexus 5000 Series switches and the Cisco Nexus 2000 Series Fabric Extenders.
Contents Send documentation c omment s to nexus5kdocs@cisco.com Table 1 Online History Change Revision Date Description B0 December 20, 2010 Created release notes for Release 5.0(2)N2(1) C0 January 26, 2010 Added resolved bugs for NX-OS Release 5.0(2)N1(1). Updated New Features sections. Moved Configuration Synchronization Best Practices to the Cisco Nexus 5000 Series NX-OS Operations Guide. Updated the Upgrading the Power Sequencer on the Cisco Nexus 5010 and Cisco Nexus 5020 Switches section.
Introduction Send documentation c omment s to nexus5kdocs@cisco.com Cisco Nexus 5500 Platform Cisco NX-OS Release 5.0(2)N1(1) introduces the Cisco Nexus 5500 platform which extends the industry-leading versatility of the Cisco Nexus 5000 Series of purpose-built, 10-Gigabit Ethernet data center class switches and provides higher density, lower latency, and multilayer services.
Introduction Send documentation c omment s to nexus5kdocs@cisco.com It has the following features: • Forty fixed 10-Gigabit Ethernet, Cisco Data Center Ethernet, and FCoE Small Form Factor Pluggable Plus (SFP+) ports. Sixteen of the forty fixed ports support both Gigabit Ethernet and 10-Gigabit Ethernet. The default is 10-Gigabit Ethernet.
Introduction Send documentation c omment s to nexus5kdocs@cisco.com The Fabric Extender integrates with its parent switch, allowing zero-touch provisioning as well as automatic configuration. This integration allows large numbers of servers and hosts to be supported using the same feature set as the parent Cisco Nexus 5000 Series switch, including security and quality of service (QoS) configuration parameters, with a single point of management as shown in Figure 1.
New and Changed Features Send documentation c omment s to nexus5kdocs@cisco.com 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 Cisco Nexus 2148T. Software is downloaded and upgraded from its parent Cisco Nexus 5000 Series switch.
New and Changed Features Send documentation c omment s to nexus5kdocs@cisco.com Beginning with Cisco NX-OS Release 5.0(2)N2(1), VTP client/server modes are supported for VTP version 1 and 2. Prior to this release, VTP transparent was the only supported mode. This feature allows you to provision VLANs at a central point and distribute the VLAN database across a Layer 2 domain.
New and Changed Features Send documentation c omment s to nexus5kdocs@cisco.com Hardware Features Cisco NX-OS Release 5.0(2)N1(1) includes the following new or changed hardware features: • Support for the Cisco Nexus 5548P Platform switch which is a 1 RU chassis with 32 fixed ports and 1 expansion slot.
Upgrading or Downgrading to a New Release Send documentation c omment s to nexus5kdocs@cisco.com This feature allows configuration of access control for the switch for a VTY, regardless of where the connection is established (mgmt0 or an external interface). • AAA Command Authorization with RBAC Allows you to authorize every command that a user can execute.
Upgrading or Downgrading to a New Release Send documentation c omment s to nexus5kdocs@cisco.com Table 2 Cisco NX-OS Release 5.0(2)N2(1) Supported Upgrades and Downgrades Current Cisco NX-OS Release Upgrade to Cisco NX-OS Release 5.0(2)N2(1) Downgrade from Cisco NX-OS 5.0(2)N2(1) 5.0(2)N1(1) Nondisruptive upgrade (ISSU) Disruptive downgrade 4.
Upgrading or Downgrading to a New Release Send documentation c omment s to nexus5kdocs@cisco.com • Upgrading from NX-OS Release 4.2(1) to NX-OS Release 5.0(2) is a nondisruptive upgrade (ISSU). • Upgrading from a Cisco NX-OS Release 4.2(1)-based release to NX-OS Release 5.0(2)N1(1) is nondisruptive. • Downgrading from Cisco NX-OS Release 5.0(2)N1(1) to a previous release is disruptive.
Installing Expansion Modules Send documentation c omment s to nexus5kdocs@cisco.com Installing Expansion Modules When you install an expansion module on a Cisco Nexus 5000 Series switch, use the show module command to check the status of the module installation in the system logs as follows: Note Hot swap expansion modules are not supported in Cisco NX-OS Release 5.0(2)N1(1) and earlier releases. Power down the switch before you insert or remove an expansion module.
Limitations Send documentation c omment s to nexus5kdocs@cisco.com Mod --1 2 Sw -------------5.0(2)N1(1) 5.0(2)N1(1) Hw -----1.0 1.0 World-Wide-Name(s) (WWN) --------------------------------------------------20:41:00:05:9b:23:40:c0 to 20:48:00:05:9b:23:40:c0 Mod --1 2 MAC-Address(es) -------------------------------------0005.9b23.40d0 to 0005.9b23.40ef badb.414b.4245 to badb.414b.
Limitations Send documentation c omment s to nexus5kdocs@cisco.com Non-Edge Designated Forwarding Ports is required for an ISSU. For additional information, see CSCtf51577. For information topologies that a nondisruptive upgrade is supported, refer to the Cisco Nexus 5000 Series NX-OS Upgrade and Downgrade Guide. • IGMP queries sent in CSCtf94558 are group-specific queries that are sent with the destination IP/MAC address as the group's address. GS queries are sent for IP address: 224.1.14.1 to 224.1.14.
Limitations Send documentation c omment s to nexus5kdocs@cisco.com • In large-scale configurations, some Cisco Nexus 2000 Series Fabric Extenders may take up to 3 minutes to appear online after issuing the reload command.
Limitations Send documentation c omment s 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 is applied on a spanned frame. • Spanned 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.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com • When a FEX port is configured as both SPAN rx-source and tx-source, the broadcast, non-IGMP Layer-2 multicast, and unknown unicast frames originating from that port may be seen twice on the SPAN destination, once on the ingress and once on the egress path. On the egress path, the frames are filtered by the FEX to prevent them from going out on the same port on which they were received.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com • CSCtj85867 Symptom: The show running-config command does not show the switchport trunk allowed VLAN configuration for an interface. This happens when the interface inherits a port-profile and the allowed VLAN list that contains VLANs configured directly on interface are such that the number of contiguous VLAN ranges are greater than 64.
Caveats Send documentation c omment s to nexus5kdocs@cisco.
Caveats Send documentation c omment s to nexus5kdocs@cisco.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com • CSCti51365 Symptom: During ISSU, if NP port channels are flapped, the reason for downtime is displayed incorrectly, as follows: NPV-switch# show int fc 2/1 fc2/1 is down (No operational members) Workaround: None. This is only a display issue. No functional impact • CSCti61513 Symptom: match ip rtp cannot be configured in a type qos class-map of type match-all. Workaround: Configure match any classp-map.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: Sometimes, SPAN stops working on the Cisco Nexus 5000 Series. Workaround: Flapping the SPAN destination again recovers the SPAN traffic • CSCti84186 Symptom: When an interface is pre-provisioned with non-default config, issuing a show running command with the all keyword at the end, default config is still displayed along with the newly configured non-default config.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Workaround: Change the running configuration to make the pause no-drop configuration for class-fcoe same as the checkpointed configuration. • CSCti87913 Symptom: A Cisco Nexus 5000 Series switch may not be able to login any servers after following steps: a. Performing an ISSU to the Cisco NX-OS 5.0(2)N1(1) release from a previous release with feature fcoe configuration enabled. b. Disabling feature fcoe and then re-enabling feature fcoe. c.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: Deletion of switch-profile fails when switch-profile contains port channel definitions and some interfaces are members of the port channel. This happens when switch profile contains configurations imported from a running-config. Workaround: Execute resync-database command and then delete the switch-profile.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: If the eth1/39 is up with traffic running and you configure a channel-group command under the eth1/39, it displays junk values after the port channel is created. Eugene1(config-monitor)# show interface port-channel 1 port-channel1 is up input rate 1.22 Gbps, 2.36 Mpps; output rate 867.62 Mbps, 1.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com switchport trunk allowed vlan add 413-418,429-434,445-450,461-466 .... .... b. VLANs created on the switch themselves comprise of 10 or more discontinuous ranges. vlan 1,101-103,127-129,153-154,160-161,167-168,174-175,181-182,188-189,195-196,202-203,209222,237-238,253-254,269-270,285-286,301-302,317-318,333-334,349-350,365-366,381-382,39 7-398,413-414,429-430,445-446,461-462,477-478 .... ....
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Workaround: Configure the egress points of Fibre channel traffic as SPAN sources on the Cisco Nexus 5548 switch. • CSCth69160 Symptom: The SVI on secondary VLAN does not work. Workaround: Assign SVI to non Private VLANs • CSCti11823 Symptom: The Cisco NX-OS version 4.2(1)N1() supports only 10 Gigabit Ethernet on the Nexus 2232 host ports. If the administrator plugs in 1Gig SFPs on Nexus 2232 host ports with Cisco NX-OS 4.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: This is the case of having an STP topology with parallel links (there is a loop) on the secondary switch with a path cost for the non-vpc ports is smaller than the vpc ports. Therefore, peer-link would end up being blocked by STP. In this case, transient traffic loop could be formed. Workaround: Recommended best practice topology for deployment does not have parallel links to vPCs that have their cost tweaked to be higher than vPCs.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com • CSCta77490 Symptom: When the type of a pVLAN is toggled from being a regular VLAN to a pVLAN and back to regular VLAN in very small interval of time, the type change fails. Workaround: Issue the type change commands with a 5 seconds gap in between. • CSCtb34546 Symptom: When a PACL with deny ip any any is applied on mgmt0, CFS discovery gets stuck.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: With a san port channel as the source and ethernet interface as the destination, removing the channel-group config from the san port channel member causes monitor session to go to error state. Workaround: Unconfigure and reconfigure the monitor session. • CSCtb53820 Symptom: After save and reload with a monitor session configuration where source is a vsan and destination is an fc port, the monitor session goes to error state.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Workaround: Perform shut and no shut on the error disabled interfaces.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Workaround: If system configuration is to be restored from a configuration file (copied locally or through tftp), you can separate the FEX interface part of the configuration (if any) into a different file. Copy the main file first, then wait for FEX to come online, and then copy the separate FEX interface configuration file. Alternately, you can copy twice.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com 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. • 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.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: CFS does not support RADIUS 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.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com 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. Workaround: None.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: When priority tagged frames are received on Cisco Nexus 2000 Series Fabric Extender ports, they are dropped and not forward on the native or default VLAN of the port. The MAC addresses are not learned. Workaround: None. • CSCtl87240 Symptom: Switch profile commands are removed from the running configuration when the switch profile is deleted. This occurs when you issue the no switch-profile name all-config | local-config command.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Workaround: Modify the switch-profile by logging in as the user who initially created the switch-profile. • CSCtk37139 Symptom: CDP syslog message (add and remove) are logged at level 6. This issue logged to change the Sev level from 6 to 5. Not from 2 to 5. Workaround: None.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com 3001 100.1.1.1 /237.1.0.1 Eth101/1/130.1.1.1 3001 100.1.1.1 /237.1.0.1 Eth111/1/130.1.1.1 3001 100.1.1.1 /237.1.0.2 Eth101/1/130.1.1.1 3001 100.1.1.1 /237.1.0.2 Eth111/1/130.1.1.1 3001 100.1.1.1 /237.1.0.3 Eth101/1/130.1.1.1 3001 100.1.1.1 /237.1.0.3 Eth111/1/130.1.1.1 3001 100.1.1.1 /237.1.0.4 Eth101/1/130.1.1.1 3001 100.1.1.1 /237.1.0.4 Eth111/1/130.1.1.1 3001 100.1.1.1 /237.1.0.5 Eth101/1/130.1.1.1 3001 100.1.1.1 /237.1.0.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom: Sometimes "show switch-profile status" or "show switch-profile status commit" displays error message in truncated form.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com • CSCtj39025 Symptom: On a Cisco Nexus 5000 Series switch after upgrading to a 5.0(2)N1(1) release, if the partner side of the LACP port channel is configured as lacp rate fast and there are more than 10 ports connected through a Cisco Nexus 2148 Fabric Extender, these ports flap periodically. The partner side of the LACP port channel is configured as lacp rate fast. The Cisco Nexus 2148 image is upgraded through ISSU.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Example: banner motd # No Unauthorized Access # Remove the preceding spaces to become left-aligned: banner motd # No Unauthorized Access # 2) Downgrade back to 4.2(1)N2(1) and remove the Banner. Then retry upgrade back to 5.0(2)N1(1) 3) Perform a 'write erase', after which the device wont be in a boot loop. You can then paste your configuration back - however be sure to either remove the banner motd text or modify it to become left-aligned.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Switch(config)# interface Port-channel 100 Switch(config-if)# switchport trunk allowed vlan add 123 Check the status on vpc peer-link Ensure vlan 123 is operational on vpc peer-link using "show vpc" Configure the vpc ports Switch(config)# interface Port-channel 101-102 Switch(config-if)# switchport trunk allowed vlan add 123 2) Remove and re-add the VLAN to the nexus 5000 pair.
Caveats Send documentation c omment s to nexus5kdocs@cisco.com Symptom:The DWRR scheduling on the Cisco Nexus 2248 and Cisco Nexus 2232 Fabric Extenders is not accurate. As a result, the class of traffic that presents more traffic is given a larger share of the bandwidth. Workaround: Strict priority scheduling can be used (enter the priority keyword in the queuing policy command) to provide scheduling precedence.
Related Documentation Send documentation c omment s to nexus5kdocs@cisco.com Workaround: For a differientiated count of 802.3 Pause frames vs. PFC Pause frames, use the show hardware internal gatos port e1/3 | beg MAC command: n5kswitch# show hardware internal gatos port e1/3 | beg MAC • RX_PKT_802.3x_PAUSE RX_PKT_PER_PRIORITY_PAUSE | 0x4bfacc | 0xc6758da RX_PKT_802.
Related Documentation Send documentation c omment s to nexus5kdocs@cisco.
Related Documentation Send documentation c omment s to nexus5kdocs@cisco.com Troubleshooting Guide Cisco Nexus 5000 Troubleshooting Guide Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.
