Wireless Access

I'm having a strange issue that seems to be spreading around my network. Now *almost all AP's are stuck in an infinite boot cycle. They do pull good IP's and will authenticate prior to the next restart. 

 

Output of the CLI where the access point gets stuck is as follows:

Getting an IP address...
x.x.x.x x.x.x.x x.x.x.x (receives IP)
Running ADP...

cat: /tmp/master: No such file or directory
Done. Master is
killall: nanny: no process killed
killall: sapd: no process killed
Sending SIGKILL to all processes.
Please stand by while rebooting the system.
Restarting system.

It seems to cycle through the startup process continuously. 

Additional information:

APBoot 1.5.3.4 (Build 43264)
Built: 2014-04-16 at 15:35:03

Model: AP-13X
CPU: 88F6560 A0 (DDR3)
Clock: CPU 1600MHz
DRAM: 256MB
POST1: passed
Flash: 16 MB
Power: 802.3af POE
Lan: done
PHY: done

What software version are you running on your controller?

 

From the output you provided, it looks like the AP is not discovering the controller IP to boot from, thus the rebooting. How should your APs be discovering the controller? (DHCP, DNS, ADP, etc?)

The software version of the controller is 6.3.1.16-FIPS.

 

The AP's should be getting their IP's from DHCP. Option 43 and 60 are configured and should direct the AP to our master controller. 

Is this a new environment ? or this used to work ? any changes ?

How Aps discovering the controller ? DNS , DHCP , etc..

Sent from Mail for Windows 10

The AP's have previously been working, and we have gone through a fairly major network upgrade changing our core switches to Juniper from Cisco. The issue had existed before this changeover started, and kind of started spreading during the switch. 

 

From a network perspective, there is no access-list applied to any of the interface vlan's that would block this traffic. I can ping both the AP, and the controller with a source IP of the interface vlan. They are authenticating in ACS.. The list goes on, if you have more specific questions I can definitely answer you. 

 

As mentioned in my other response, they are discovering the controller with DHCP. 

From this output below:

 

Running ADP...

cat: /tmp/master: No such file or directory
Done. Master is
killall: nanny: no process killed

It appears that the AP is not receiving option 43 via DHCP and is failing to discover the controller. A wired packet capture taken at the APs switch port should verify the DHCP server and included options specified,

Can you ping the controller from the AP console ?

If you run “show log system 50 | include < ap name or MAC address > can you see if the AP shows up at all

Have you tried removing the authentication from one of the ports and see if the AP comes up ?

Did you guys upgraded your controllers during this process ?





Thank you

Victor Fabian

Pardon typos sent from Mobile


Thank you

Victor Fabian

Pardon typos sent from Mobile