Controllerless Networks

We deleted several AP's from our switch/controller.  They have now been repurposed and when we plug them in they pull the correct IP for the controller but we do not see them appear in the Campus WL.  Is there a command we need to run to allow them to appear again?  We have rebooted controller and AP's several times with no luck.

 

What do you see from the AP Console ?

 

Can you ping the APs from the controller ?

 

Have you made any changes on the controller ?

 

On the controller run the following command :

 

show log system all

 

a few troubleshooting tips

 

• Check if control-plane-security enabled...do auto-cert (Just to see if the AP'S starting to show up under ap installison window)
• Connect console to one of the AP'S and see if they getting an IP + master IP/server in order to contact your controller. **Does thoese AP connected to the same VLAN / PORT / Switch they were connected before (With the same settings?)
• Does thoese AP units got static IP ? (does it fitted to the VLAN they are in)
• Maybe u added some more Ap'S in between - Did you have enough licensees ?

 

 

1st I will explain what was changed.  We did run out of licenses.  I deleted the 2 AP's in our lab from the AP list and from the Security Plane AP White List.  So we could bring other AP's online.  We have since added more liceses, I have been able to bring new AP's out of the box online in the lab.  The two AP's I deleted continue to timeout after resolving the correct IP for the controller.

• Check if control-plane-security enabled...do auto-cert (Just to see if the AP'S starting to show up under ap installison window).  >>>>Did Auto cert and also added one of the two AP's to WL manually no change for either AP.
• Connect console to one of the AP'S and see if they getting an IP + master IP/server in order to contact your controller. **Does thoese AP connected to the same VLAN / PORT / Switch they were connected before (With the same settings?)>>> AP's pull IP via DHCP and correctly identify the correct IP of the controller before timing out.
• Does thoese AP units got static IP ? (does it fitted to the VLAN they are in)
• Maybe u added some more Ap'S in between - Did you have enough licensees ?>>> Yes

Can u connect a console cable to one of the problemtic AP'S and copy&paste all the output from the start of the boot process please.

Did u maybe upgrade the AOS version of the controller?

are these AP'S configured as RAP'S or as CAP'S? (and if they are configured as RAP - do u have enough address for vpn connectivity ?

We did not upgrade the firmware.

 

The AP's are configured as CAPs

 

Here is AP boot up process from Console Cable-

 

APBoot 1.2.4.4 (build 26618)
Built: 2011-01-07 at 13:42:04

Model: AP-10x
CPU: AR7161 revision: A2
Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
DRAM: 128 MB
POST1: passed
Copy: done
Flash: 16 MB
PCI: scanning bus 0 ...
dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00 00 168c 0029 00002 01 10000000 00000000 00000000 00000000
01 00 168c 0029 00002 01 10010000 00000000 00000000 00000000
Net: eth0
Radio: ar922x#0, ar922x#1

Hit <Enter> to stop autoboot: 0
Checking image @ 0xbf100000
Invalid image format version: 0xffffffff
Checking image @ 0xbf800000
Invalid image format version: 0xffffffff
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 10.130.99.243
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 10.130.99.254
DHCP DNS server: 192.168.19.147
DHCP DNS domain: bebe.com
ADP multicast 1
ADP broadcast 1
ADP multicast 2
ADP broadcast 2
ADP multicast 3

Retry count exceeded
DNS request 1 for aruba-master.bebe.com to 192.168.19.147
T Using eth0 device
TFTP from server 192.168.19.148; our IP address is 10.130.99.243; sending throug
h gateway 10.130.99.254
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: #T T #T T #T T ##

It's seems like your AP can't get the AOS as needed. (failed doing all the TFTP needed process)

 

A.What is the IP of your aruba master?

192.168.19.148 or 192.168.19.147?

 

B.Can u stop the AP from boot (with fasdt click on enter key) and run:

factory_reset

(it will clearos/purgeenv and will set the ap to default settings)

 

No change after factory defualting the AP.

 

19.147 is DNS server

19.148 is Controller

Can u try to stop before boot (enter key)

 

and write:

 

setenv master 192.168.19.148

setenv serverip 192.168.19.148

saveenv

boot

 

copy&paste the output , please.

Any update?

After purgeenv on AP it showed up in Controller as down(denied).  I went to the Campus Whitelist and moved it to factory-cert with a state of certified-factory-cert. rebooted AP and no change.  New AP's I am able to bring into WL and set profile to without any problem.

Can u configure auto-cert under control plane security? and try agian to bringup thoese denied units please.

---

@cnswireless wrote:

After purgeenv on AP it showed up in Controller as down(denied).  I went to the Campus Whitelist and moved it to factory-cert with a state of certified-factory-cert. rebooted AP and no change.  New AP's I am able to bring into WL and set profile to without any problem.

---

For those AP's under Flags what do you have. (when you do the show ap database long - even if they are down they will have some flags there).

• is there any Firewall / NAC on on 10.130.99.254 ?
• does the needed ports are open? TFTP ports?

I had problems with some RAP's too that with a factory_reset wouldn't work. The only way we were able to get them back online was to do a purgeenv instead of the factory_reset.