Wireless Access

Dear All, For a short while, we had lost wireless connectivity. I downloaded the logs of the Access Point, but I am not able to make sense out of it. Can anyone please assist me in this.

Mahesh,

 

Is this an IAP (instant AP) or a controller-based AP.

 

What version of Code are you running?

 

Hi, It is a Controller based AP Model: Aruba3400 Version: 6.1.3.4

AP is of model 93

Did all your clients lose connectivity or some of them?  The log from that access point does not point to anything..

 

All the clients lost the connectivity. :smileysad: But I only have these logs.Is there anywhere else I can lookout for ?

The aruba controller itself is flash-based so it does not have much memory.  On a busy controller the logs will roll in hours.  The best thing to do is to send logs to an external syslog server or use Airwave to monitor issues.

 

You might be able to catch it next time...

 

Alternatively, you can type  "show log system 100" or "show log error 100" to see if you see anything.

 

 

Would these be of any use ?Got them from the system logs.

 

Time	Log
12/27/2012 11:27	<311005> <WARN> |AP SW-L-3-Stage-II-(C)@1.1.3.154 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
12/27/2012 15:27	<311005> <WARN> |AP SW-L-3-Stage-II-(C)@1.1.3.185 sapd|  Missed 30 heartbeats on wired AP interface 3; rebootstrapping
12/27/2012 15:53	<303073> <ERRS> |AP SW-L-3-Stage-II-(C)@1.1.3.200 nanny|  Process /aruba/bin/stm [pid 584] died: got signal SIGABRT
12/27/2012 15:53	<303079> <ERRS> |AP SW-L-3-Stage-II-(C)@1.1.3.200 nanny|  Restarted process /aruba/bin/stm
12/27/2012 15:55	<311020> <ERRS> |AP SW-L-3-Stage-II-(C)@1.1.3.200 sapd|  An internal system error has occurred at file key_mgmt.c function set80211priv line 132 error dev aruba001: ioctl[IEEE80211_IOCTL_DELKEY.
12/27/2012 15:55	<311020> <ERRS> |AP SW-L-3-Stage-II-(C)@1.1.3.200 sapd|  An internal system error has occurred at file key_mgmt.c function set80211priv line 132 error dev aruba001: ioctl[IEEE80211_IOCTL_SETKEY.

There is a connectivity issue between the controller and the access points.  What do you have the controller plugged into and what do you have the access points physically plugged into?

 

The Access Points are plugged into an Access Layer Switch.  Our Controller is installed at a remote location and the AP's and the controller are connected via WAN Link.

Please check the reliability of the link between the access points and the controller.  Missing 30 heartbeats means a connectivity issue usually.  Make sure the port that the access point is connected to and the point that the controller is connected to has negotiated properly and there are no errors on it.

 

We faced the same issue again today at around 12:15. The dhcp logs talk of the same thing.

<311005> |AP SW-L-3-Stage-II-(C)@1.1.3.200 sapd| Missed 30 heartbeats on wired AP interface 3; rebootstrapping <304035> |stm| PAPI_Send failed: 145; from 8345 to 1.1.3.200:8451 len 8 type 3116 <303073> |AP SW-L-3-Stage-II-(C)@1.1.3.240 nanny| Process /aruba/bin/stm [pid 584] died: got signal SIGABRT <303079> |AP SW-L-3-Stage-II-(C)@1.1.3.240 nanny| Restarted process /aruba/bin/stm <311020> |AP SW-L-3-Stage-II-(C)@1.1.3.240 sapd| An internal system error has occurred at file key_mgmt.c function set80211priv line 132 error dev aruba001: ioctl[IEEE80211_IOCTL_DELKEY. <311020> |AP SW-L-3-Stage-II-(C)@1.1.3.240 sapd| An internal system error has occurred at file key_mgmt.c function set80211priv line 132 error dev aruba001: ioctl[IEEE80211_IOCTL_SETKEY.

How do I check if the AP 's and the controller have negotiated properly plz?

 

 

---

@mahesh_shirke wrote:

How do I check if the AP 's and the controller have negotiated properly plz?

---

negotiated what? if you see the AP in the controller without any error flags you can assume all is well.

 

do you have any other monitoring active for the WAN link, might be very possible it just fails causing this to happen.

---

@mahesh_shirke wrote:

How do I check if the AP 's and the controller have negotiated properly plz?

 

 

---

Check the switchport that the AP is connected to, and the switchport that the controller is connected to to see if you have any errors, or if the switchport has negotiated at half duplex.

 

What is the size of the WAN link between the access point and the controller?  Do you have any congestion on what WAN link?

What type of WLAN is being served to the users on that access point?  Does it use encryption?  Are bridging or tunneling traffic back to the controller?

 

The "bootstrap" message is seen when an access point has lost connectivity to the controller.  The other messages "internal error...." is a message that is seen when the access point attempts to reestablish connectivity, so it is merely a symptom of the connectivity issue, not an "error" in itself..