An individual stack member can be rebooted from a CLI command.
  • The member will reboot and re-join the stack, with the same role that it had prior to the reboot.

  • If the stack topology is a ring, no traffic disruption is expected on any other stack members when a single member is rebooted.

  • If the stack topology is a chain, rebooting a member may cause a stack split, resulting in members being unreachable from the master. This result can cause significant disruption of the stack, so use this option with caution.

  • If the member is the stack Standby, there will be no Standby in the stack until the member reboots and re-joins the stack. At this point, the member will again have the role of Standby.

  • If the member is the stack Master, the command will trigger a failover and the Standby switch will take over as Master of the stack.

  • If the Standby is unavailable at the time of master reboot, the whole stack will reboot.

The whole stack can also be rebooted by using the boot system command.
  • All members will reboot and the stack will re-form.

  • Traffic will be disrupted for the duration of the reboot.

Refer to vsf member reboot for information about rebooting a member.