Cisco Mesh Access Points - Viewing AP Last Reboot Reason

Viewing AP Last Reboot Reason
Cisco Prime Infrastructure reports the reason for the most recent reboot on the general panel of the access
point details page (Monitor > Access Points > AP Name).
Listed below is a summary of each of the possible Last Reboot Reasons that might be reported and its definition:
• none–Access point reported a reboot reason unknown to the controller
• dot11gModeChange–Change of 802.11g mode change occurred
• ipAddressSet–Set of static IP address
• ip AddressReset–Reset of static IP address
• rebootFromController–Reboot of access point initiated from the controller
• dhcpFallbackFail–Fallback to DHCP did not occur
• discoveryFail–Discovery was not sent
• noJoinResponse–Join response was not received
• denyJoin–Join attempt at the controller was denied
• noConfigResponse–Config Response was not received
• configController–Configured or master controller found
• imageUpgrade Success–Upgrade of image successful
• imageOpcodeInvalid–Invalid image data opcode
• imageCheckSumInvalid–Invalid image md 5 checksum
• imageDataTimeout–Image data message timed-out
• configFileInvalid–Invalid config file
• imageDownloadError–Process error during the image download
• rebootFromConsole–Reboot command initiated from AP console
• rapOverAir–Root access point (RAP) is connected over the air
• brownout–Power failure caused reboot
• powerLow–Low power caused a reboot
• crash–Software failure caused crash
• powerHigh–Power spike caused reboot
• powerLoss–Power loss caused reboot
• powerCharge–Change in power source caused reboot
• componentFailure–Component failure caused reboot
• watchdog–Watch dog timer reset caused reboot
Cisco Mesh Access Points, Design and Deployment Guide, Release 7.3
OL-27593-01 257
Managing Mesh Access Points with Cisco Prime Infrastructure
Viewing AP Last Reboot Reason