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) OL-22747-02, December 2010)

Send documentation comments to [e-mail]
24
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)
OL-22747-02
Caveats
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.
• CSCtj13786
• CSCtj16996
Symptom:
Rollback fails and output for show rollback log exec contains following:
Note This example features feature vpc as an example. The failed configuration is different for other
conditional features:
...
...
========================================================
`config sync `
`switch-profile Test`
Switch-Profile started, Profile ID is 1
`interface port-channel100`
`switchport mode trunk`
Syntax error while parsing 'vpc peer-link'
========================================================
...
...
Workaround: Prior to rollback, you should configure the conditional feature (feature vpc in this
case). In case of feature vpc, you should also configure vpc domain and peer-keepalive.
• CSCtj19861
Symptoms a Cisco Nexus 5548 switch, in NPV mode, performing a shut on a non-trunking san-port
channel uplink takes more than 30 seconds (the CLI is not responsive for 30 seconds).
Workaround: None. There is no functionality impact.
• CSCtj22747
Symptom: When you pre-provision a module and insert an incompatible module and then later fix
the configuration and provision a new module, and the module does not come online, the module
needs to be pre-provisioned and replaced with a different type of module.
Workaround: Physically remove and re-insert the module.
• CSCtj23007
Symptom:
On a Cisco Nexus 5000 Series switch, running a 5.0(2)N1(1) image, multiple
checkpoints with same name could get created. This problem is seen only when checkpoint names
are 31 character long.
Workaround: The checkpoint names used must be less than 31 character long.
• CSCtj26673
Symptom:
Import verification may not work for certain class configurations that are implicitly
generated on configuring policy-maps of type network-qos and queuing.
Workaround: Use resync-database command to resynchronize the config-sync database with
system configuration and then issue the verify/commit in import mode again.
• CSCtj26863