Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Controller reboot

This thread has been viewed 9 times

  • 1.  Controller reboot

    Posted Feb 20, 2018 01:41 PM

    Our local controller rebooted on it's own yesterday (this happens occasionally_ and this is what I found on the controller:

     

    Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2)

    Supervisor Card

     

    There is no crash log file. We called TAC a couple of times but with no log there's not much they could do..



  • 2.  RE: Controller reboot

    Posted Feb 20, 2018 02:32 PM

    Could this be a AOS 8.x error? fixed in 8.2.0.2: 

     

    163066 Symptom: A managed device rebooted unexpectedly.

    The log files for the event listed the reason as Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:60).

     

    The fix ensures that the
    managed device works as expected.
    Scenario: This issue was observed in managed devices running
    ArubaOS 8.0.0.0 or later versions.

    Resolved in 8.2.0.2

     

    more here: https://support.arubanetworks.com/Documentation/tabid/77/DMXModule/512/Command/Core_Download/Default.aspx?EntryId=28753 - page 12



  • 3.  RE: Controller reboot

    Posted Feb 20, 2018 02:40 PM
    Thanks for the update.. We are running 6.5.4.0 at the moment.. planning on
    upgrading this summer after the classes have ended

    --

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


    *Lehigh University(610)758-5099*


  • 4.  RE: Controller reboot

    EMPLOYEE
    Posted Feb 20, 2018 03:38 PM

    magnumpi83, the best thing you can do is to put a console cable on the controller and have a PC that captures the output there constantly.  It is entirely possible that there is crash information on the console that would help TAC get to the bottom of it.