HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes Release 4.1(3)N1(1) - Page 19
Symptom, Workaround, how startup-config, show startup-config, Symptom, copy startup, running, copy
View all HP Cisco Nexus 5000 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 19 highlights
Caveats Send documentation comments to [email protected] • 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). Workaround: After a downgrade, manually copy the startup configuration to the running configuration and reboot the system. • CSCsv10783 Symptom: The show startup-config command does not show the correct mode for a channel group. It shows the current mode for the channel group. The correct mode is stored. On a subsequent reload, the correct mode is configured on the channel group. The show startup-config always shows the current mode instead of the mode that was saved to startup. On a subsequent reload, the correct mode is configured. This is only a show command issue. Workaround: None. • CSCsu93313 Symptom: Within a configuration session, 125 unique VACLs are created with a total of 1023 TCAM entries. The verify command fails with the following message: d2-switch-2(config)# configure session 30 Config Session started, Session ID is 1 d2-switch-2(config-s)# verify Failed to start Verification: Message Timed Out d2-switch-2(config-s)# commit Failed to complete Verification: no free label This problem occurs with large VACL configurations. Once the Cisco Nexus 5000 Series switch is in this state, subsequent VACL configurations fail. Workaround: Reload to recover the configuration. • CSCsv00402 Symptom: When you downgrade from the Cisco NX-OS 4.0(1a)N1 release to a previous software release, any static IGMP entries that have been configured over an Ether channel are lost after the downgrade. 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. • 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. • CSCsw79515 Symptom: If a Cisco Nexus 2000 Series Fabric Extender is power cycled multiple times in quick succession, some links between the Cisco Nexus 5000 Series switches and the Cisco Nexus 2000 Series Fabric Extenders may go into an error disabled state. Workaround: Fabric ports recover after few seconds. No user intervention is required. OL-16601-01 Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, Release 4.1(3)N1(1) 19