Switch Reboot Reasons

The switch Health card displays the last reboot reason. For more information, see Health.

Reboot reasons for AOS-CX switches

Table 1: Reboot reasons for AOS-CX

Reboot Reasons	Description
Reboot requested by user	A user requested a switch reboot through the CLI or web UI.
Reset button pressed	The switch detected a short-press of the reset button.
Front panel factory reset	The switch was factory reset via reset button.
Backplane fault	A backplane fault occurred.
Configuration change	A configuration change resulted in a reboot
Configuration version migration	A configuration version migration occurred, which required a reboot
Console error	Console failed to start.
Fabric fault	A fabric fault occurred.
All line modules faulted	A zero line card condition occurred.
Redundancy switchover requested	A user requested a redundancy switchover.
Redundant Management communication timeout	The standby management module has taken over from an unresponsive active management module.
Redundant Management election timeout	A failure to elect a standby management module in the allotted time.
Critical service fault (error)	A daemon critical to switch operation has stopped functioning. An extra error string may be present to describe the error in detail.
VSF autojoin renumber	Reset triggered by VSF autojoin.
VSF member renumbered	A user requested a renumber of a VSF member.
VSF switchover requested	A user requested a VSF switchover.
VSX software update	Reset triggered by a VSX software update.
Chassis critical temperature	Chassis operating temperature exceeded.
Chassis low critical temperature	Chassis temperature below the minimum operating threshold.
Chassis insufficient fans	Insufficient fans to cool the chassis.
Chassis unsupported PSUs/fans	Unsupported or misconfigured PSUs or system fans.
Management module critical temperature	Management module operating temperature exceeded.
ISSU SMM update	Standby management module reboot triggered by an In-Service Software Upgrade
ISSU switchover	Redundancy switchover triggered by an In-Service Software Upgrade
ISSU aborted	Standby management module reset triggered by failure during an In-Service Software Upgrade.
Rollback timer expired	Reset triggered by the ISSU rollback timer expiration.
JitterEntropy selftest failed	JitterEntropy selftest failed on the system.
Crypto selftest failed	Crypto selftest failed on the system.
MACsec selftest failed	MACsec selftest failed on one or more interfaces.
Hibernation requested	Reboot triggered by a user hibernation request.
PSU initiated reboot	Reboot triggered by the PSU due to fault in the input voltage or if PSU input fault is detected.
Uncontrolled Reboots
ops-switchd crashed	Reboot triggered due to ops-switchd deamon crash.
ovsdb-server crashed	Reboot triggered due to ovsdb server crash.

Reboot reasons for AOS-S switches

The following are some of the possible reboot reasons for AOS-S switches:

• Operator reboot from SSH session

• Reboot of Member ID 1, User reboot

• Operator reboot from Aruba CENTRAL session

• Operator reboot from TELNET session

• Operator reboot from CONSOLE session

• Operator reboot from Aruba ACTIVATE session

• Rebooting the device because the module compatibility mode has changed.

• Rebooting after deleting configuration file.

• Interface module boot failure

• Wrong OS reboot

  Stack members have different versions compare with the conductor.

• RFS Error reboot

  Flie syncing error across stack members

• Bad code in flash

• Non Responsive member

  Non responsive member in a stack

• Removed and rebooted by user

• Removed by user

• No remove in progress

• Lost conductor and standby

• Lost merge

• Rebooting for Stacking Admin State change

• Hardware Access Error reboot

• Standby not yet sync'd reboot

• Conductor deassert reboot

• Member reboot

• Member shutdown

• Standby lost during boot

• Commander lost during boot

• HeartBeat failure

  Heartbeat failure between members in a stack.

• Backplane communication error

• Greater than Max Members

• Mismatch product ID