Controller Based WLANs

Why does the controller reboot reason shows wrong date?
Q:

Sometimes the controller may get rebooted with reboot reason showing a wrong timestamp such as "Thu Jan 1 00:00:00 1970" or "Wed Dec 31 19:00:00 1969" as below. 

 

show boot history  

Reboot History Table
--------------------
No  Description                                                   User     Role  IP              Timestamp
--  -----------                                                   ----     ----  --              ---------

33  Controller Reboot initiated from Web-UI.                      user1    root  172.16.150.61   Thu Dec 17 22:20:00 2015

34  REBOOTCAUSE                                                   user1    root  serial-console  Thu Jan  1 00:00:00 1970

 

show boot history  


Reboot History Table
--------------------
No  Description                                                   User          Role  IP              Timestamp
--  -----------                                                   ----          ----  --              ---------
30  Boot partition is changed from 0 to 1                         user2         root  192.168.10.11   Wed Jan  6 06:10:16 2016

31  REBOOTCAUSE                                                   user2         root  serial-console  Wed Dec 31 19:00:00 1969

 



A:

The time on the controller is maintained by the CMOS battery also known as RTC (Real Time Clock) battery. The reboot reason with wrong timestamp can be see if the RTC battery has gone bad. 

RTC battery cannot be replaced on the field. Hence the entire controller has to be replaced. Customer has to contact Aruba TAC to RMA the controller. 

Version History
Revision #:
2 of 2
Last update:
‎03-29-2017 11:55 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.