Wireless Access

Reply
Occasional Contributor I

Aruba controller reboot

Hi,

I have Aruba controllers 7010 (version 6.5.4.3) that gets rebooted (wlsxColdStart Detected),

From the Webgui, the logs show that the controller was down and back up,

From CLI, I noticed that the logs were showing (killing dogma and watchdog) before and after the reboot,

It doesn't really say what caused the reboot,

Is there some other ways to find out what cause the reboot?

thanks

JF

Highlighted
Frequent Contributor I

Re: Aruba controller reboot

Is there a crash.tar file? We are having the same problem and TAC is
looking into it but we never get a crash.tar file

--

*Jon Hutchinson*
*8B Packer Ave rm 185*


*Lehigh University(610)758-5099*
Occasional Contributor I

Re: Aruba controller reboot

I ran the command (show switchinfo) from the CLI and I got the result below.

No crash information avalaible.

Reboot cause: Power Cycle

 

Re: Aruba controller reboot

Is the controller connected to a UPS? Did anything else connected to the same device go down?

 

ColdStart makes me think it lost power. WarmStart usually indicates a reboot initiated by command.


Michael Haring
ACMP, ACCP, BCNE, CCENT, Palo Alto ACE 7.0
Occasional Contributor I

Re: Aruba controller reboot

no, there is no UPS connected on that one.

It seemed that there was a lost of power that caused this

 

Re: Aruba controller reboot

I would see if you can check a switch or something in the same rack or connected to a close outlet. Check the uptime and see if anything else went down.

 

There is a known bug in AOS 6.5.4.3 that causes controller to reboot, but the reason is different, so I don't suspect that to be the issue.


Michael Haring
ACMP, ACCP, BCNE, CCENT, Palo Alto ACE 7.0
Occasional Contributor I

Re: Aruba controller reboot

Do you have more information on the known bug in AOS 6.5.4.3?

MVP

Re: Aruba controller reboot

Bug id : 167418

 

Symptom: A master controller rebooted after DPI was disabled. The log file listed the reason for the event as Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). The fix ensures that the controller works as expected.

Scenario: This issue was observed in controllers running ArubaOS 6.5.3.1.

Regards,
Borja
ACMX #567 //ACCP//CWNA//CWAP
Occasional Contributor I

Re: Aruba controller reboot

thanks for the info

 

Re: Aruba controller reboot

There's quite a lot of resolved issues in the latest ArubaOS 6.5.4.x release which related to a unexpected reboot due to various reasons. Some of these appear to be written to the log file. The log file won't survive a reboot, do you have a syslog server you could set up in order to capture some logs?

 

http://www.arubanetworks.com/techdocs/ArubaOS/6.5.x.x/Default.htm#ReleaseNotes/ResolvedIssues/ResolvedIssues6.5.x.htm%3FTocPath%3D_____4


ACMA, ACMP, ACSA
If my post addresses your query, give kudos:)
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: