Unplanned Maintenance; Maintenance Mode Timer - Cisco Nexus 5600 Series Configuration Manual

Unplanned Maintenance

system can have either a system-generated normal-mode profile or a custom normal-mode profile at a time.
The scenarios are as given in the figure below:
Figure 4: Maintenance Profile Scenarios
We recommend using Scenario 1 or 2.
Note
Unplanned Maintenance
You can put the switch in unplanned maintenance mode when the switch reloads due to a critical failure. For
switches with a single supervisor, configure a reset reason CLI using the system mode maintenance on-reload
reset-reason command to enable the switch to go into maintenance mode after a switch reloads due to a
critical failure. For switches with dual supervisors, SUP switchover occurs when there is a critical failure of
the switch and the switch will not go into maintenance mode. The maintenance-mode profile existing in the
startup configuration is applied when the switch goes in to unplanned maintenance mode. If no maintenance
mode profile exists in the startup configuration, a system-generated maintenance-mode profile is created and
applied when the switch goes in to unplanned maintenance mode.

Maintenance Mode Timer

Use the system mode maintenance timeout command before entering maintenance mode to keep the switch
in maintenance mode for a specified number of minutes. You can also use this command while the switch is
in maintenance mode to change the number of minutes for which the switch will be in maintenance mode.
The timer will then restart from that instant with the new timer value. Once the configured time elapses, the
switch returns to normal mode automatically without using the no system mode maintenance mode command.
Use the no system mode maintenance timeout command to disable the timer.
Cisco Nexus 5600 Series NX-OS System Management Configuration Guide, Release 7.x
286
Configuring GIR (Cisco NX-OS Release 7.3(0)N1(1))
OL-31641-01