Wireless Access

last person joined: 5 hours ago 

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

Datapath failure caused controller reboot

This thread has been viewed 2 times

  • 1.  Datapath failure caused controller reboot

    Posted Sep 26, 2012 03:31 PM

    I had a controller reboot a couple days ago and the reason in the logs was a datapath failure.  Has anyone seen or heard of this before?  I have a case open but wanted to get any input from the group.



  • 2.  RE: Datapath failure caused controller reboot

    EMPLOYEE
    Posted Sep 26, 2012 04:48 PM

    You need to contact support ASAP.

     



  • 3.  RE: Datapath failure caused controller reboot

    EMPLOYEE
    Posted Sep 26, 2012 07:25 PM

    can I ask what version it was and the controller please?



  • 4.  RE: Datapath failure caused controller reboot

    Posted Sep 28, 2012 11:17 AM

    I'm running 5.0.4.0.  Support suggested upgrading to 5.0.4.6 or 5.0.4.9.  I don't see that happening in the near furture.  I'm at a large healthcare facility so getting downtime is difficult to say the least.

     

    I guess I'll need to stay on 5.0.4.0 until it really becomes an issue.  Controller has been stable and has only booted once.



  • 5.  RE: Datapath failure caused controller reboot

    Posted Oct 02, 2012 12:58 PM

    We've had this issue before and only an upgrade has fixed it.

     

    I would suggest getting the process going to get the controller or controllers upgraded. If it takes a while at least the wheels are turning.