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]
39
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: Sometimes "show switch-profile <name> status" or "show switch-profile <name> status
commit" displays error message in truncated form.
switch(config-sync-sp)# show switch-profile test status
switch-profile : test
----------------------------------------------------------
Start-time: 876054 usecs after Fri Oct 15 05:30:35 2010
End-time: 939787 usecs after Fri Oct 15 05:30:54 2010
Profile-Revision: 16
Session-type: Commit
Session-subtype: -
Peer-triggered: No
Profile-status: Commit Failed
Local information:
----------------
Status: Commit Failure
Error(s):
Failed command(s):
interface Ethernet1/12
inherit port-profile x
ERROR: Operation Inherit Interface failed
nfiguring active mode << Error message truncated here.
Peer information:
----------------
IP-address: 10.65.121.100
Sync-status: In Sync.
Status: Commit Failure
Error(s):
Failed command(s):
interface Ethernet1/12
Syntax error while parsing ' inherit port-profile x'
This occurs when switch-profile buffer contains port-profile configuration and the following commit
fails due to port-profile config and ppm returns error.
Workaround: None.There is no functionality impact and only the display issue in show command
output.
• CSCtj27662
Symptom: On a Cisco Nexus 5548 iIn NPV mode, TNP ports may take more than a minute to come
up the first time after a reload. The switch has to be Nexus 5548 and NPV should be enabled.
Workaround: None. This happens only the first time after reload.
• CSCtj29657
Symptom: System does not throw an error when two classes are configured as priority in
switch-port profile, it throws an error when user configures in config-terminal.
Workaround:Don't configure two classes as priority in switch-port profile.
• CSCtj31760
Symptom: If the beacon is enabled on the interface and the switch is reloaded, the interface beacon
stops blinking even though the running configurations shows it as enabled.The beacon needs to be
configured at interface level configuration and a reload needs to be done
Workaround:Disable and re-enable the beacon configuration on the interface to enable the port
beacon.