09-25-2013 05:28 AM
I really wonder why this very neat Cisco Nexus feature is so much buggy...
I have configured switch-profiles on two Cisco Nexus 5596 that already had some configuration (mostly identical).
In general it is working fine, I was able to import the required configuration for QoS, FEX pre-provision, vPC port-channel, FEX A/A port channels... but now I have one port that I can not configure at all. Basically, I can do nothing to it and don't understand what is wrong with it.
Here it is.
CS01(config-sync-sp)# sh run int eth128/1/40
version 6.0(2)N1(2)
interface Ethernet128/1/40
description iLO and Management
CS02# sh run int eth128/1/40
version 6.0(2)N1(2)
interface Ethernet128/1/40
description iLO and Management
This "description" is the only command I was able to apply here...
Synchronization is configured in a right way (I was able to synchronize configuration for other ports). Here is the proof
CS01(config-sync-sp)# show switch-p status
switch-profile : DC02
----------------------------------------------------------
Start-time: 737030 usecs after Wed Sep 25 13:04:29 2013
End-time: 738581 usecs after Wed Sep 25 13:05:02 2013
Profile-Revision: 66
Session-type: Initial-Exchange
Session-subtype: Init-Exchange-All
Peer-triggered: Yes
Profile-status: Sync Success
Local information:
----------------
Status: Commit Success
Error(s):
Peer information:
----------------
IP-address: 192.168.0.12
Sync-status: In sync
Status: Commit Success
Error(s):
When I try to inherit port-profile or even simply set port's speed on Eth128/1/40 I get this
CS01(config-sync-sp)# int eth128/1/40
CS01(config-sync-sp-if)# inherit port-profile PP-iLO-n-Management
CS01(config-sync-sp-if)# verify
Failed: Verify Failed
CS01(config-sync-sp)# show switch-p status
switch-profile : DC02
----------------------------------------------------------
Start-time: 198769 usecs after Wed Sep 25 13:16:31 2013
End-time: 358966 usecs after Wed Sep 25 13:16:32 2013
Profile-Revision: 66
Session-type: Verify
Session-subtype: -
Peer-triggered: No
Profile-status: Verify Failed
Local information:
----------------
Status: Verify Failure
Error(s):
Following commands failed mutual-exclusion checks:
interface Ethernet128/1/40
inherit port-profile PP-iLO-n-Management
Peer information:
----------------
IP-address: 192.168.0.12
Sync-status: In sync
Status: Verify Success
Error(s):
Or....
CS01(config-sync-sp)# buffer-del all
CS01(config-sync-sp)# int eth128/1/40
CS01(config-sync-sp-if)# speed 1000
CS01(config-sync-sp-if)# verify
Failed: Verify Failed
Even, if I try to do this only on a local peer (or remote) separately with SYNC switched off I get the same
CS01(config-sync-sp)# buffer-del all
CS01(config-sync-sp)# no sync-peers destination
CS01(config-sync-sp)# int eth128/1/40
CS01(config-sync-sp-if)# speed 1000
CS01(config-sync-sp-if)# verify
Failed: Verify Failed
I am kind of lost... I tried to import empty interfaces config into switch profile with no luck, I tried to configure this interface on each peer with sync off with no luck... and what is BAD in this situation - this interface belong to the switch profile (although with no config, only description), meaning I cannot configure it under configure terminal. Literally can do nothing with it...
Has anyone encountered same? Is it possible to delete only specific interface from the switch-profile and try to re-apply it from scratch or at least configure from the global configuration mode?
Although other interfaces seem to be ok, I wasn't able to apply some specific commands to them previously using conf sync... I had to disable sync, apply separately to each switch using global configuration mode, then import, then enable sync... it was accepting commands and sync'd fine. In this case, it does not allow me to apply any config from the global configuration mode:
CS01(config-sync-sp)# buffer-d all
CS01(config-sync-sp)# conf t
CS01(config)# int eth128/1/40
CS01(config-if)# inherit port-profile PP-iLO-n-Management
Error: Command is not mutually exclusive
HOW?!!! What's wrong with it?
10-09-2013 07:03 AM
Ok... I found the source of the problem (looks to be buggy behaviour).
Here's my recent blog post that covers a detailed description and a fix/workaround:
http://nexp.com.ua/technologies/nx-os/troubleshooting-nx-os-config-sync/
Hope this will help anyone.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide