Remove switch-profile in Nexus 5K (conf-sync) to allow traditional mode (conf term) without impact and maintaining configuration of running-config

[demonio.tazmania]

Hello Cisco Community!!!

I have two Nexus 5548UP (NX-OS 7.x) in Dual-homed with a "xxx" switch-profile for conf-sync.
Given "mutually exclusive" problems, I want to completely remove the switch-profile so that the two N5k can only be configured with the traditional mode (configure terminal).
Currently the two 5K switches have the same configuration in the running-config and most of the configuration part was done from the conf-sync mode, although some interfaces have always had to be configured in the traditional way because otherwise the verify and the Commit failed.
The question is: How can I completely eliminate the switch-profile of both switches without impact on the service? ... Attention, not only I am interested in deleting the configuration of the switch-profile, I am interested in removing the switch-profile completely without losing the Running configuration ...
I want the two N5k to be left with the configuration of the running-config (which is equal to the startup-config), but never again allow the config-sync mode.
This also interests me because our BMC automation tool does not allow the conf-sync mode and when they are in normal mode all the tasks can be done unattended and safely on both Nexus 5K.

Thank you.

[Peter Paluch]

Hello,

As much as I regret it, removing a config-sync profile is always disruptive, and will always cause the configuration to be lost - because, essentially, that configuration is not a part of running-config, rather, it is a part of the config-sync profile, so when the config-sync profile is gone, so is the configuration it contained.

I know that this is a pitiable limitation - unfortunately, it's just the way it is.

Best regards,
Peter

[demonio.tazmania]

Good morning, thanks for your quick response.
So, if I use the following command in the two N5k of the Dual-Homed, what do I get?
Switch (config-sync) # no switch-profile abc profile-only all

Once this command is applied. Could I configure the two N5K with the traditional "conf t" mode for all the configuration p would also have to continue with the "config-sync" mode? ...
If this command is not the procedure to get rid of the switch-profile and therefore the config-sync. What would be the procedure to disable this functionality? ...
And the last question: The execution of this command would erase some of the configuration "running-config" with respect to interfaces, vlanes, etc .... If affirmative, it can be deduced that its execution is diruptiva.

Summarizing this topic: We want to leave these two N5K to be configured independently, although they will obviously have the same configuration. This involves removing the switch-profile to get rid of the "config-sync", and we do not really know the procedure; If it is with this command or directly deleting the configuration and starting from zero in each one of them. In any case, we would like to know the procedure is the least disruptive, because the dual-homed is composed of a primary and a secondary.

Thank you.

[Peter Paluch]

Hello,

An update and a correction to my previous response: If your particular NX-OS version under config sync supports the following syntax:

no switch-profile profile_name profile-only { all | local }

then this syntax will allow you to remove only the config sync profile itself; however, all commands it contained will still remain in the running-config, so there will be no disruption. The all keyword will cause the config sync profile to be removed from both peers; the local keyword will only remove the config sync profile from the local switch. Once again, however, the profile-only keyword will make sure that the active running-config will remain unchanged even if the config sync profile is removed.

If the profile-only keyword is not available then removing the config sync profile will remove all the configuration that was present in the config sync profile from the current running-config. In other words, all the commands that have been present in config sync will be set to their default values in the running-config when the profile is removed. This will obviously be disruptive, as you will need to restore the configuration manually - having a backup of "show running-config" captured before the removal of config sync profile would be essential.

So, if I use the following command in the two N5k of the Dual-Homed, what do I get?
Switch (config-sync) # no switch-profile abc profile-only all

If this command is available and entered, it will delete the config sync profile from both peers but the running-config will not be modified. Just the config sync profile will be removed, but the running-config will not be changed, so the switches will continue operating without any change.

Once this command is applied. Could I configure the two N5K with the traditional "conf t" mode for all the configuration p would also have to continue with the "config-sync" mode?

Once you apply the no switch-profile abc profile-only all, you can simply exit the config sync mode, and after you verify that the switch-profile has been successfully removed from both peers (use show run switch-profile and show switch-profile), simply forget about config sync and never use it again :) Configure your switches using the usual configure (or conf t) mode.

Would this answer your questions? Please feel welcome to ask further.

Best regards,
Peter

[demonio.tazmania]

Thank you very much.
Your response has been very clear and helpful.

Regard:)

[Peter Paluch]

Hi,

Glad to hear that. Thank you for the kind words!

Best regards,
Peter

P.S.: Just to be on an absolutely safe side, have a backup of your running-config from both switches before you do the change, and plan the activity during non-business hours or during a maintenance window. It's always better to be safe rather than sorry.