WLC > AP Details > Uptime

[Jason Aarons]

Looking at our  AP’s in WLC, we have several have different uptimes for unknown reasons. Thoughts?

Do  RRM changes effect the Uptime?

[pcroak]

Hi Jason,

There will be 2 uptime values for the access points. AP uptime and Join uptime. AP uptime is referring to the amount of time the AP has been operational without a reboot/power cycle. Join uptime is going to be the amount of time that the AP has been joined to the WLC.

Which value are you referring to in this situation?

If we are dealing with AP uptime, we need to check if there have been any power outages, or we also would want to check for any AP crashes (in WLC GUI: Management > Tech Support > AP Crash logs).

If we are dealing with Join time, it basically means there must have been a portion of time where AP/WLC heartbeats were not making it and the AP dropped off the WLC. (By deafult the heartbeat is every 30 seconds, with 5 1-second interval fast retries upon a failure).

-Patrick Croak

Wireless TAC

[Leo Laohoo]

Looking at our  AP’s in WLC, we have several have different uptimes for unknown reasons.

I've never seen this before so here are my thoughts (feel free to correct my incorrect mind):

1.  WLC firmware bug?  What is the model of the AP you see this happening?

2.  Maybe the WLC didn't have time to update the details via SNMP?

Is this sporadic or all over the place?

[the_birdy.v]

Mine is a little different. It says Not avail in the WLC, but is actually responding to ICMP from its gateway and from remote management a PC.

Any ideas ?

(Cisco Controller) >show ap uptime

Number of APs.................................... 5
Global AP User Name.............................. Not Configured
Global AP Dot1x User Name........................ Not Configured

AP Name              Ethernet MAC       AP Up Time               Association Up Time
------------------   -----------------  -----------------------  -----------------------
AP503d.e55a.2460     50:3d:e5:5a:24:60  661 days, 05 h 36 m 21 s   628 days, 10 h 21 m 22 s
AP503d.e5be.5dd6     50:3d:e5:be:5d:d6  661 days, 05 h 37 m 17 s   628 days, 10 h 21 m 18 s
AP70ca.9bd9.e3a2     70:ca:9b:d9:e3:a2  661 days, 05 h 34 m 47 s   628 days, 10 h 21 m 16 s
AP649e.f30e.8aba     64:9e:f3:0e:8a:ba  233 days, 19 h 55 m 43 s   233 days, 19 h 54 m 49 s
AP503d.e55a.247a     50:3d:e5:5a:24:7a   Not Available           Not Available

arp -show -hw=50-3d-e5-5a-24-7a
ARP cache of iface vlan_Management
  Dynamic 10.145.176.222   = 50-3d-e5-5a-24-7a   Expire=212

PING from Gateway

ping 10.145.176.222

Sending 1 4-byte ICMP ping to 10.145.176.222 from 10.145.176.193 using PBR table "main"
ICMP Reply from 10.145.176.222  seq=0  time=<10 ms  TTL=255

Ping Results:  Sent: 1, Received:1, Avg RTT: 10.0 ms

PING from Remote PC

C:\Users\ASIA>ping 10.145.176.222

Pinging 10.145.176.222 with 32 bytes of data:
Reply from 10.145.176.222: bytes=32 time=625ms TTL=251
Reply from 10.145.176.222: bytes=32 time=625ms TTL=251
Reply from 10.145.176.222: bytes=32 time=628ms TTL=251
Reply from 10.145.176.222: bytes=32 time=627ms TTL=251

Ping statistics for 10.145.176.222:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 625ms, Maximum = 628ms, Average = 626ms