Reboots the switch, bridge port extenders (BPEs), or SummitStack in the specified slot at a specified date and time.
| time | Specifies a reboot date in mm dd yyyy format and reboot time in hh mm ss format. |
| cancel | Cancels a previously scheduled reboot. |
| slot slot-number | Specifies the slot number currently being used by the active stack node or BPE that is to be rebooted. |
| all | Specifies rebooting all attached BPEs and the controlling bridge switch. Using this option requires a Core License or above. |
| rolling | Specifies to reboot or upgrade a stack by rebooting one node at a time. |
N/A.
If you do not specify a reboot time, the switch reboots immediately following the command, and any previously scheduled reboots are cancelled.
Prior to rebooting, the switch returns the following message:
Do you want to save configuration changes to primary and reboot? (y - save and reboot, n - reboot without save, <cr> - cancel command)
To cancel a previously scheduled reboot, use the cancel option.
After selecting the rolling option, if a new image was not installed, a rolling reboot of all the nodes will be performed.
The reboot command used without any parameters on the master node reboots all members of the same active topology to which the master node belongs.
This version can only be used on the master node.
The reboot slot slot-number command can be used on any active node. The command will reboot the active node that is currently using the specified slot number in the same active topology as the issuing node. This variation cannot be used on a node that is not in stacking mode.
The reboot node-address node-address command can be used on any node whether or not the node is in stacking mode. It will reboot the node whose MAC address is supplied.
The reboot stack-topology {as-standby} command reboots every node in the stack topology. The command can be issued from any node whether or not the node is in stacking mode. If the as-standby option is used, every node in the stack topology restarts with master-capability disabled. This option is useful when manually resolving a dual master situation.
The reboot rolling command initiates a Stack Rolling Software Upgrade (Rolling Upgrade), which reboots each node in a stack one-by-one, allowing the stack to continue functioning during the reboot. The rolling upgrade process reboots all the Standby nodes, reboots the Backup node, and then initiates a failover to make the old Backup node the new Primary. The failover results in the old Primary node rebooting. Since the selected software version on each node is the newer, upgraded software version, after each node reboots, they will run the new software version. Performing a Rolling Upgrade does not change the current method of installing software, only how the stack is rebooted.
Under normal circumstances, it is not necessary to reboot the BPEs slots. After rebooting a controlling switch, BPE upstream port down events cause the BPE's software to bring down all extended ports. This makes the BPE slot appear as down to any adjacently attached devices, and traffic properly re-converges on any redundant paths. When the controlling bridge switch comes back up, the BPE comes back up without any intervention. Therefore, using the commands reboot or unconfigure switch {all | erase [all | nvram]} does not reboot the attached BPEs. To reboot attached BPEs, you must use the all option.
The following example reboots the switch at 8:00 AM on April 15, 2005:
reboot time 04 15 2005 08 00 00
This command was first available in ExtremeXOS 10.1.
The alternate BootROM image was added in ExtremeXOS 11.1.
The slot, node-address, stack-topology, and as-standby options were added in ExtremeXOS 12.0.
The all option for rebooting attached BPEs was added in ExtremeXOS 22.5.
The rolling option was added in ExtremeXOS 31.6.