Wireless Access

Good afternoon all,

I'm trapped into an issue which I'm unable to sort it out.

Our environment has a redundant 7205 Wireless Manager running 8.3.0.1.

I have a bunch of AP-304 and AP-305 that works fine. I had to add additional AP to our env, in particular AP-375 outdoor. I would expect that AP would join WM automatically as other AP has done but it wasn't.

Then I connect to the serial console and forced AP conversion via cmdline specifying CAP mode and WM VRRP ip address.

Then AP download the new firmware and reboots. Once it boots then it stops at:

[ 56.917838] br0 address=80:8d:b7:cf:58:7c
[ 56.965760] wifi0: AP type AP-375, radio 0, max_bssids 16
[ 57.030365] aruba_mods_radio_attach() INT setting antenna polarization to 1 radio 0
[ 57.123117] Resetting spectral chainmask to Rx chainmask
[ 57.187191] Init the PCAP for radio0 offload 1.
[ 57.241080] aruba_mods_radio_attach: radio: 0, init txq work cpu: core-0
[ 57.337675] pktlog_init: Initializing Pktlog for AR900B, pktlog_hdr_size = 16
[ 57.412621] pktlog_init: Initializing Pktlog for AR900B, pktlog_hdr_size = 16
AP rebooted Thu Jan 1 08:16:13 UTC 1970; System cmd at uptime 0D 0H 16M 26S: Image Upgrade Successful
shutting down watchdog process (nanny will restart it)...

<<<<< Welcome to the Access Point >>>>>

~ #

On WM no AP appears to be provisioned. After 60-70 secs AP reboots to factory image.

Does anybody has some suggestions?

Thank you

Davide Bortolini

Thanks for the update on the firmware version running on the mobility controller (8.3.0.1 vs 8.0.3.1). That addresses the first concern.

Can you attach the full console log from the AP-375 booting up? Specifically, I'm looking for the part where the AP gets an IP address and then does master discovery to try and find the controller to connect to.

The AP-375 will behave a little differently than the AP-300 series, as it is a single image universal image that can run in either Instant or controller based architectures, depending on what it discovers during boot up. Since it appears the AP did discover your mobility controller in order to update code, those boot details will help diagnose further what is going on.

Hi Charlie,

here you will find the full console log captured BEFORE and AFTER the AP conversion to managed AP. It boots the same Wireless Manager Version but stops at # prompt. Then it rebbots automatically to factory after 60-70 secs.

Thanks

Davide Bortolini

Attachment(s)

log.txt   20 KB 1 version

Thanks for the logs. Is CPSec enabled in this environment, and has the new AP-375 been added to the whitelist so that it can communicate with the controller?

Hi Charlie,

yes the CPSec is enabled and the AP is whitelisted. I have tried as well as to disable UAP controller less env but same issue.

I have also captured the datapath table once the AP is booted after conversion.

(W11NWLAC01) [mynode] #show datapath session table 10.11.48.105

Datapath Session Table Entries
------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT
D - deny, R - redirect, Y - no syn
H - high prio, P - set prio, T - set ToS
C - client, M - mirror, V - VOIP
Q - Real-Time Quality analysis
u - Upstream Real-Time Quality analysis
I - Deep inspect, U - Locally destined
E - Media Deep Inspect, G - media signal
r - Route Nexthop, h - High Value
A - Application Firewall Inspect
B - Permanent, O - Openflow
L - Log

Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets Bytes Flags CPU ID
--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ---- --------- --------- --------------- -------
10.11.48.253 10.11.48.105 17 514 54462 0/0 0 0 0 pc0 9 0 0 FY 11

10.11.48.105 10.11.48.253 17 54462 514 1/15785 0 0 1 pc0 9 1 216 FC 11

No way to hook it up. It still reboots.

Thank you

Davide Bortolini

Is there anything interesting in the mobility controller's log?

show log system 50

Hi Charlie,

thi is what I captured from system log just after issuing AP converion command and rebooted it.

Aug 9 20:23:40 KERNEL(APBNU02@10.11.48.16): [15306.132105] DFS min filter rssiThresh = 15
Aug 9 20:23:40 KERNEL(APBNU02@10.11.48.16): [15306.132116] DFS max pulse dur = 61 ticks
Aug 9 20:23:40 KERNEL(APBNU02@10.11.48.16): [15306.132124] DFS max pulse pri = 5004, min pulse pri = 246
Aug 9 20:23:40 KERNEL(APBNU02@10.11.48.16): [15306.132162] dfs_radar_enable: firpwr=0, rssi=0, height=0, prssi=0, inband=0, relpwr=0, relstep=0, maxlen=0
Aug 9 20:23:40 KERNEL(APBNU02@10.11.48.16): [15306.132171] Enabled radar detection on channel 5260
Aug 9 20:23:40 KERNEL(APBNU02@10.11.48.16): [15306.132179] dfs_radar_enable: duration multiplier is 72
Aug 9 20:26:34 :303022: <WARN> |AP 80:8d:b7:cf:57:be@10.11.48.21 nanny| Reboot Reason: AP rebooted Thu Jan 1 08:15:47 UTC 1970; System cmd at uptime 0D 0H 16M 2S: Image Upgrade Successful
Aug 9 20:28:36 :311002: <WARN> |AP 80:8d:b7:cf:57:be@10.11.48.21 sapd| Rebooting: SAPD: UAP controller less
Aug 9 20:28:37 :303086: <ERRS> |AP 80:8d:b7:cf:57:be@10.11.48.21 nanny| Process Manager (nanny) shutting down - AP will reboot!

Thanks

Davide Bortolini

There's not enough information from the log entries to show the AP-375 attempting to connect. The datapath output you provided shows the AP sending syslog to the controller (port 514), but there is no PAPI for control plane. The AP and controller are on the same subnet, so unless there's a layer 2 firewall blocking traffic, there should not be anything keeping a whitelisted AP from joining.

Two thoughts. The AP-375 is not trying to come up as a mesh point, correct?

What is the current license state on your controller? 

show ap license-usage

Are there enough valid licenses available for the new AP to join the controller?

Hi Charlie,

that's exactly our issue. AP won't come as mes point.

What drives me crazy is that I have this issue ONLY with AP-375 (I have 5 of them and no one joins the controller). The behavior is the same: connect to WLC, get latest firmware, reboot and try to connect, then reboot in factory mode. I have already joined several 304 and 305 models with no issues.

Below there's my license info:

(W11NWLAC01) [mynode] #show ap license-usage

AP Licenses
-----------
Type Number
---- ------
AP Licenses 60
PEF Licenses 60
Controller License True
Overall AP License Limit 60

AP Usage
--------
Type Count
---- -----
Active CAPs 17
Active RAPs 0
Remote-node APs 0
Tunneled nodes 0
Total APs 17

Remaining AP Capacity
---------------------
Type Number
---- ------
CAPs 43
RAPs 43

Thank you again for your support.

Davide Bortolini

---

sistemi.informativi@speedline.it wrote:

Hi Charlie,

that's exactly our issue. AP won't come as mes point.

What drives me crazy is that I have this issue ONLY with AP-375 (I have 5 of them and no one joins the controller). The behavior is the same: connect to WLC, get latest firmware, reboot and try to connect, then reboot in factory mode. I have already joined several 304 and 305 models with no issues.

 

---

The license info looks good. I don't see a problem there.

To make sure I understand completely, the AP-375s ARE intended to be mesh points ... meaning they will not have a wired connection to the infrastructure where the mobility controller exists, but will instead talk over wireless back to a mesh point that does have wired access. Understanding that none of your AP-375s are operational, is it an existing AP-304/305 that is configured to operate as the mesh portal?

---

@cclemmer

 

To make sure I understand completely, the AP-375s ARE intended to be mesh points ... meaning they will not have a wired connection to the infrastructure where the mobility controller exists, but will instead talk over wireless back to a mesh point that does have wired access. Understanding that none of your AP-375s are operational, is it an existing AP-304/305 that is configured to operate as the mesh portal?

---

No, all AP are wired to the network within the same subnet/vlan of Wireless controller. They act as Campus AP and none of AP-375 joins WLC. All AP-304/305 are configured as Campus AP wired to the network and are joined to our WLC.

Davide

Hmm...I have tried once again to join AP as CAP to Wireless controller and I was able to catch some interestin info from datapath table:

It seems that AP and WLC tries to setup the PAPI channel but for some reason AP doesn't go further and give up after some seconds.

Could be this info useful?

Davide

Okay, so we do see PAPI traffic from the AP hit the controller's datapath.

Now if you view the logs on the controller, do you see anything related to the AP's join attempt?

Nope :(

I've also increased the log level of system log to debug and attacched an external syslog server but no logs referred to AP. Only syslog messages sento by AP to WLC.

I tried also to install IAP (the same version as I have inside WLC) and it boots properly in IAP mode. Then I converted it to CAP via web interface.

Same issue. It downloads and install firmware package from WLC, reboots, discover master via ADP and then get stuck at # prompt.

After that nanny process reboot AP since it hasn't join WLC.

Then I did a third attemp by downgrading WLC to 8.2.1.0 but got exactly the same behavior.

Thank you

Davide

---

sistemi.informativi@speedline.it wrote:

Then I did a third attemp by downgrading WLC to 8.2.1.0 but got exactly the same behavior.

 

Thank you

 

Davide

---

Downgrading to 8.2.1.0 is not an option that should work, since the AP-375s require 8.3.0.0 as a minimum release level.

The lack of logs showing the AP connection attempts is concerning. It may be best to open a TAC case for live debugging to see what's going on when the AP tries to connect.

ADP is disabled by uap_controller_less

Please see the thread here:  http://community.arubanetworks.com/t5/Controllerless-Networks/CAP-back-to-IAP-on-Mobility-Controller/m-p/298618