Wireless Access

Reply
New Contributor
Posts: 1
Registered: ‎04-04-2013

I have an AP that wants to party like it's 1999!

I can understand a first message after a reboot being the wrong year, but this one perplexes me. We did have a power outage last night, so I expected rebooting. But really wondering about those multiple last-millenium rebootstraps. 

 

The "recent control messages" obviously collected the correct time, but the 1999 messages seem to range across 40 minutes or so. 

 

Anyone have any ideas what this might mean?  

 

 

 

Rebootstrap Information
-----------------------
Date Time Reason (Latest 10)
--------------------------------------
1999-12-31 16:04:27 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:08:20 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:12:28 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:16:09 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:20:28 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:24:44 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:28:22 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:32:11 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:36:00 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0
1999-12-31 16:40:05 Switching to LMS 172.18.252.25: HELLO-TIMEOUT. Last Ctrl message: HELLO len=1140 dest=172.18.252.25 tries=10 seq=0


HA Failover Information
-----------------------
Date Time Reason (Latest 10)
--------------------------------------
(none found)


Recent Control Messages from AP to Controller
---------------------------------------------
Date Time Message Description
-------------------------------------------------
Fri Sep 4 14:22:49 2015(267 secs ago): SENT REQ type=KEEPALIVE len=45 peer=172.18.252.25 seq_num=76 num_attempts=1 rtt=0 secs 0400000028040000000205AC126C4D04386D4CE5040000004C0455E9E17905FFFFFF0005AC126C010000000000
Fri Sep 4 14:12:49 2015(867 secs ago): SENT REQ type=KEEPALIVE len=45 peer=172.18.252.25 seq_num=75 num_attempts=1 rtt=0 secs 0400000028040000000205AC126C4D04386D4CE5040000004B0455E9DF2105FFFFFF0005AC126C010000000000
Fri Sep 4 14:02:49 2015(1467 secs ago): SENT REQ type=KEEPALIVE len=45 peer=172.18.252.25 seq_num=74 num_attempts=1 rtt=0 secs 0400000028040000000205AC126C4D04386D4CE5040000004A0455E9DCC905FFFFFF0005AC126C010000000000


Rebootstrap LMS
---------------
(none found)
------------

Crash Information
-----------------
(none found)
------------

Guru Elite
Posts: 21,517
Registered: ‎03-29-2007

Re: I have an AP that wants to party like it's 1999!

A 1999 or 1969 date means it did not contact a controller to get its time. It looks like the controller was unavailable when it first booted, so it kept bootstrapping. Eventually it found a controller, so those logs with the correct time was after it made contact.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: