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]
21
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
• 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.
• CSCti63620
Symptom:
For the config-sync feature, implicit configs generated on account of another
configuration are not added into the data-structures maintained by the config-sync module. When
this situation occurs, the import command may result in failure.
For example, consider member interfaces of a port channel. If a configuration is applied on the port
channel, it could be implicitly updated on the member interfaces and could be reflected in the show
running-config output of the member interface.
Workaround: This problem is generally encountered with the import command where the you can
use the option import running-config. In this command all the commands that appear in the
member interfaces are to be verified and committed to make it a part of switch-profile. Now if the
implicit commands are not updated in the internal data-structures the import fails.
There two workarounds
a) The import command is generally used after a reload (or ISSU) in which case all the commands
including the implicit ones are updated in the config-sync data-structures and hence this problem is
not encountered.
b) Another work around is if reload or ISSU is not possible, a command called resync database can
be used from within the switch-profile context to update the internal data-structures.
• CSCti68764
Symptom:
On a Cisco Nexus 5000 Series switch, running a 5.0(2)N1(1) image, The following
commands are currently not supported under a switch-profile:
1.spanning-tree vlan <> priority <>
2.spanning-tree vlan <> forward-time <>
3.spanning-tree vlan <> hello-time <>
4.spanning-tree vlan <> max-age <>
5.spanning-tree vlan <> root primary | spanning-tree vlan <> root secondary
This happens when a spanning tree configuration is made in a switch-profile.
Workaround: None.
• CSCti77835
Symptom:
Rollback fails with following failure in rollback exec logs (show rollback log exec):
#Generating Rollback Patch
Executing Rollback Patch ========================================================
`config t ` `no vlan 1, 100-199, 201-602`
Error: Command is not mutually exclusive
========================================================
Vlans are configured partially inside and outside the switch-profile.
Workaround: All Vlans should be configured either completely inside or outside the switch-profile.
• CSCti82599