If controller reboots unexpectedly

MVP
MVP
Q:

What steps to be performed if controller reboots unexpectedly?
 



A:

You can follow below steps if controller was rebooted

1. Check the reason of reboot using command

#show switchinfo
Hostname is arubalab-MD
System Time:Wed May  6 17:41:25 EDT 2020
No crash information available.                                             ------> Check if there is any crash available  
No kernel crash information available.
Reboot Cause: User reboot (Intent:cause:register 78:86:50:60)

show syslocation 

Location not configured

show version 

Aruba Operating System Software.
ArubaOS (MODEL: Aruba7010-US), Version 8.5.0.6
Website: http://www.arubanetworks.com
(c) Copyright 2020 Hewlett Packard Enterprise Development LP.
Compiled on 2020-01-24 at 06:35:12 UTC (build 74058) by p4build

ROM: System Bootstrap, Version CPBoot 1.0.7.0 (build 65676)
Built: 2018-07-06 04:23:32
Built by: p4build@re_client_65676

Switch uptime is 2 days 21 hours 24 minutes 22 seconds
Reboot Cause: User reboot (Intent:cause:register 78:86:50:60)                    ----> Check the reason
Supervisor Card
Processor (XLP208 Rev B1 (Secure Boot) , 800 MHz) with 3797M bytes of memory.
32K bytes of non-volatile configuration memory.
1936M bytes of Supervisor Card system flash.

2. If we have crash available, then extarct crash and copy it out of controller

#tar crash
#copy flash: crash.tar tftp: <ip address of tftp server> crash.tar

3. Check if any process is stuck on controller

#show process monitor statistics 

4. Check for cpu and memory

#show cpuload
#show memory

5. Collect controller's logs.tar and copy out of controller

#tar logs tech-support
#copy flash: logs.tar tftp: <ip address of tftp server> logs.tar

 

Once you have all the logs and outputs collected, open TAC ticket for further analysis. 

Version history
Revision #:
2 of 2
Last update:
‎07-03-2020 06:25 PM
Updated by:
 
Labels (1)
Contributors