Log in to ask questions, share your expertise, or stay connected to content. Don’t have a login? Join now.
One of out local controllers (7420) rebooted on it's own. The show boot history showed the following?
Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2)
Any ideas on this one?
Thanks
142376 142378
Symptom: The datapath process in a controller crashed and the controller rebooted unexpectedly. The log file for the event listed the reason as Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). The fix ensures that the controller does not reboot due to a datapath timeout.
Scenario: This issue occurred under the following circumstances:l WhentheARPentryforanIPaddressagedoutorforcefullydeleted
while traffic was running.l Whenjumboprocessingwasenabledandthecontrollerreceiveda
management multi-buffer IP frame.This issue was observed in controllers running ArubaOS 6.4.4.5.
Controller-Datapath
All platforms
ArubaOS 6.4.4.5
ArubaOS 6.5.1.0
All,
Has anyone know what exactly is the cause of this? and what firmware release solved this?
Thank you
STILL OUT THERE, FIX'ED ??
Mon Oct 1 15:59:29 GMT 2018: Version(6.5.4.2) Build(61807): Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2)
@Steinar Grande wrote:STILL OUT THERE, FIX'ED ?? Mon Oct 1 15:59:29 GMT 2018: Version(6.5.4.2) Build(61807): Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2)
Please open a TAC case to confirm the source of your datapath timeout.
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.