Rebooting Nexus 7000 vs rebooting supervisor

[Mokhalil82]

Hi

We have 2 x Nexus 7k switches each with a dual SUP2 supervisor. I want to carry out a maintenance reboot on each as I have an issue with one of them that requires a reload.

My question is, when just rebooting each supervisor, is this like rebooting the whole switch. Can I carry out a reload without downtime if I failover the active supervisor to standby, and then reload the standby slot.

Is it different if I just do the reload command in CLI, does this just reload the active supervisor or the whole switch.

Thanks

[Mark Malone]

Hey If you do a reload on the active sup it will move straight to standby SUP once its setup correctly in HA  should not effect traffic , make sure it is though with commands below and outputs are similar first or you will have disruption

Have you tested your HA before , takes about 30 seconds to flip but if it does not work by then it both SUPs will flip so be careful if you have not done it before plan for a maintenance window to cover yourself

Switchover Characteristics

An HA switchover has the following characteristics:

• It is stateful (nondisruptive) because control traffic is not affected.

• It does not disrupt data traffic because the switching modules are not affected.

• Switching modules are not reset.

• It does not reload the Connectivity Management Processor (CMP).

  CMP is a Supervisor 1 only feature.

C7KA# show system redundancy ha status
VDC No    This supervisor                         Other supervisor
------    ---------------                         ---------------

vdc 1     Active with HA standby                  HA standby

C7KA# show system redundancy status

Redundancy mode
---------------
      administrative:   HA
         operational:   HA

This supervisor (sup-1)
-----------------------
    Redundancy state:   Active
    Supervisor state:   Active
      Internal state:   Active with HA standby

Other supervisor (sup-2)
------------------------
    Redundancy state:   Standby
    Supervisor state:   HA standby
      Internal state:   HA standby

https://supportforums.cisco.com/discussion/12921886/rebooting-nexus-7000-vs-rebooting-supervisor

Is it different if I just do the reload command in CLI, does this just reload the active supervisor or the whole switch.

This will prob reboot whole switch

[Mokhalil82]

Thanks Mark

Looks like from the commands it is setup ok. The issue I face is that I cannot save any configs as I keep getting an error "Configuration update aborted: request was aborted"

I have also made many changes that have not been saved yet so I need to do a reload that possibly is a fix for the above error but also does not lose my unsaved config. Hopefully after the reboot I will be able to save.

So if I reload a supervisor at a time and wait for it to fully come up, does this mean unsaved data will not be lost

[Mark Malone · Accepted solution]

Yes unfortunately if you reboot you will loose the config if its not saved , there is known bugs on certain versions , did you try wr and copy run start , or try and save config to another location so that way after reboot you can transfer file straight back in or last resort use putty capture the whole run config locally and then reapply it

Every bug not matter what ID says contact TAC regarding these issues , its a process that gets jammed in most cases and that's why it requires the reboot

I would though due to this being a 7K and such a serious effecting bug contact TAC , you don't want to go to all the trouble of rebooting and it doesn't fix it

If you reboot active sup and its not saved you loose the config as before switchover config needs to be synced to standby

[Mokhalil82]

Thanks Mark for the useful info. I will go through TAC. Just for info, this is the bug CSCus22805