Nexus 4001I System Code v4.1.2.E1.1e - IBM BladeCenter H (7989, 8852), HT (8740, 8750)

Download Description

• New IBM xSeries firmware and device driver file naming convention
• New firmware update file formats

Change history

Severity: Suggested

06 August 2010 4.1.2.E1.1E

• CSCth87833
  • Symptom: The switch reloads and generates a core dump, once in every two to four weeks of up-time.
  • Conditions: This behavior is noticed when the LST feature is enabled on the switch. The crash and the subsequent core dump is caused by a memory leak in the LST process and when the RSSmem usage increases to about 15613952 KB.
  • Workaround: This issue is resolved in Cisco NX-OS Release 4.1(2)E1(1e).
    
    
• CSCth88944
  • Symptom: When the switch reloads, the interfaces that are on the switch that connect to upstream switches go into the Spanning-tree blocking mode. Output such as the following is displayed: STP-2-BRIDGE_ASSURANCE_BLOCK: Bridge Assurance blocking port port-channel10 VLAN0011
    n4k# show spanning-tree interface port-channel 10
    
    

    Vlan	Role	Sts Cost	Prio.Nbr	Type
    VLAN0001	Root	FWD 1	128.4105	Network P2p
    VLAN0010	Desg	BKN*1	128.4105	Network P2p *BA_Inc
    VLAN0011	Desg	BKN*1	128.4105	Network P2p *BA_Inc

    
    
  • Conditions: This behavior occurs when the spanning-tree bridge assurance option is enabled and the port type is set to network at the global or interface level.
  • Workaround: This issue is resolved in Cisco NX-OS Release 4.1(2)E1(1e).
    
    
• CSCth05183
  • Symptom: SVI configuration is lost on changing the management interface (mgmt1) IP Address from AMM.
  • Conditions: You may see this symptom when you create an SVI IP address on the switch, and then change the management interface (mgmt1) IP address through the AMM. The SVI configuration on the switch is lost after a reload.
  • Workaround: This issue is resolved.
    
    
• CSCth05266
  • Symptom: The management interface (mgmt1) IP Address is not reachable after reloading the switch.
  • Conditions: You may see this symptom after reloading the switch when SVI is configured in the system.
  • Workaround: This issue is resolved.
    
    
• CSCth05293
  • Symptom: A memory leak in the Netstack process causes the switch to crash.
  • Conditions: You may see this symptom when any traffic is directed to the control plane, using ping, ssh, or Simple Network Management Protocol (SNMP). This symptom was observed in release 4.1(2)E1(1b).
  • Workaround: This issue is resolved.
    
    
• CSCtg78861
  • Symptom: After a Spanning Tree Protocol (STP) state change, SVI traffic on the affected ports does not egress from the switch.
  • Conditions: You may see this symptom when during the STP state change, the physical port information changes for a SVI interface. Since the Adjmgr database is not updated to the new "fwd" physical interface, the packet is sent to the STP blocked port, resulting in the packets being dropped. This results in a failure to ping the SVI after the STP state change.
  • Workaround: This issue is resolved.
    
    
• CSCtf91116
  • Symptom: The Simple Network Management Protocol (SNMP) process on a switch that runs Cisco NX-OS
    Release 4.1(2)E1(1b) slowly leaks memory causing the SNMP agent process (snmpd) to crash and the switch to reload.
  • Conditions: You may see this symptom when you poll the ifEntry (1.3.6.1.2.1.2.2.1) Management Information Base (MIB) object.
  • Workaround: This issue is resolved.

07 June 2010 4.1.2.E1.1D

• CSCth05183
  • Symptom: SVI configuration is lost on changing the management interface (mgmt1) IP Address from AMM.
  • Conditions: You may see this symptom when you create an SVI IP address on the switch, and then change the management interface (mgmt1) IP address through the AMM. The SVI configuration on the switch is lost after a reload.
  • Workaround: This issue is resolved.
    
    
• CSCth05266
  • Symptom: The management interface (mgmt1) IP Address is not reachable after reloading the switch.
  • Conditions: You may see this symptom after reloading the switch when SVI is configured in the system.
  • Workaround: This issue is resolved.
    
    
• CSCth05293
  • Symptom: A memory leak in the Netstack process causes the switch to crash. Cisco Nexus 4001I and 4005I Switch Module for IBM BladeCenter NX-OS Release Notes, Release 4.1(2)E1(1d)
  • Conditions: You may see this symptom when any traffic is directed to the control plane, using ping, ssh, or Simple Network Management Protocol (SNMP). This symptom was observed in release 4.1(2)E1(1b).
  • Workaround: This issue is resolved.
    
    
• CSCtg78861
  • Symptom: After a Spanning Tree Protocol (STP) state change, SVI traffic on the affected ports does not egress from the switch.
  • Conditions: You may see this symptom when during the STP state change, the physical port information changes for a SVI interface. Since the Adjmgr database is not updated to the new "fwd" physical interface, the packet is sent to the STP blocked port, resulting in the packets being dropped. This results in a failure to ping the SVI after the STP state change.
  • Workaround: This issue is resolved.
    
    
• CSCtf91116
  • Symptom: The Simple Network Management Protocol (SNMP) process on a switch that runs Cisco NX-OS Release 4.1(2)E1(1b) slowly leaks memory causing the SNMP agent process (snmpd) to crash and the switch to reload.
  • Conditions: You may see this symptom when you poll the ifEntry (1.3.6.1.2.1.2.2.1) Management Information Base (MIB) object.
  • Workaround: This issue is resolved.

18 December 2009

• CSCtb04248
  • Symptom: The Qlogic converged network adapter (CNA) is unable to bring up the FCoE link, using the FIP session with the switch, when FCoE CoS is changed to a non-default value.
  • Conditions: You may see this symptom when CoS=3 is configured as a "drop" CoS in QoS configuration, instead of " pause no-drop". As the default CoS for FCoE traffic is CoS=3, the change in the configuration causes the DCBXP
    protocol not to converge between the CNA and the switch. As a result the FIP/FCoE session cannot start.
  • Workaround: This issue is resolved.
    
    
• CSCtb96623
  • Symptom: After typing the copy r s command, the startup configuration has no information about the Priority Flow Control (PFC) mode.
  • Conditions: You may see this symptom when you type the command copy running-config startup-config.
  • Workaround: This issue is resolved.
    
    
• CSCtc37793
  • Symptom: In certain configurations and with a certain kind of traffic flowing in the system, when you apply a new network-qos policy that changes the MTU of any CoS from what is currently programmed or you change the MTU settings in the currently active network-qos policy, the following failure may occur: switch (config-sys-qos)# service-policy type network-qos policy-fcoe
    
    
    Note: Operation in progress, please check the status using "show system internal ipqos status".
    
    
  • Conditions: You may see this symptom when FIP snooping is enabled on the switch, and a certain type of traffic is flowing in the system when the MTU change is made.
  • Workaround: This issue is resolved.
    
    
• CSCtc42989
  • Symptom: When the traffic stops and the switch enters a near idle condition, stale entries remain in the MAC table.
  • Conditions: You may see this symptom when the aging timer is set to be greater than 251 seconds.
  • Workaround: This issue is resolved.

05 November 2009

• Initial release