Wireless Access

I'm sure I'm doing something stupid...but...

I'm setting up a new master-master pair for RAPs in our organization. The controllers are up in the DMZ and CPS is off. I can ping them from anywhere internally.

I plug in a new AP and it comes up on my Aruba-master. I provision the AP and change the master hostname to rap-master.domain.com. I've consoled into the AP and it finds the rap-master with no problems. It has an address and it can ping the rap-master with an excellent respose times. 

However, the AP never shows up in the new controller (rap-master). The devices can ping each other so I'm wondering what could be left. The AP system profile for the "default" group is default. Eventually, the AP goes over to the original master again and I'm back at square one (shows as "up" for original amount of time. Doesn't reboot). 

end of console:

Getting an IP address...
[   14.565548] ADDRCONF(NETDEV_UP): bond0: link is not ready
[   20.569836] PHY: bond0 (mdio@ffe24000:00) - Link is Up - 1000/Full
[   20.643911] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
172.20.69.41 255.255.254.0 172.20.68.254
Running ADP...Done. Master is 192.168.241.0
[   51.129608] wifi0: AP type AP-215, radio 0, max_bssids 16
[   51.275152] wifi1: AP type AP-215, radio 1, max_bssids 16
ardmore: Insmod BT modules
[   51.610592] usbcore: registered new interface driver usbfs
[   51.676631] usbcore: registered new interface driver hub
[   51.740375] usbcore: registered new device driver usb
[   51.830123] usbcore: registered new interface driver usbserial
[   51.900168] USB Serial support registered for generic
[   51.960798] usbcore: registered new interface driver usbserial_generic
[   52.038979] usbserial: USB Serial Driver core
[   52.113982] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   52.192236] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
[   52.271498] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
[   52.389315] fsl-ehci fsl-ehci.0: irq 28, io base 0xffe22000
[   52.463284] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
[   52.530041] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   52.611338] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   52.697829] usb usb1: Product: Freescale On-Chip EHCI Host Controller
[   52.774943] usb usb1: Manufacturer: Linux 2.6.35 ehci_hcd
[   52.839567] usb usb1: SerialNumber: fsl-ehci.0
[   52.893435] hub 1-0:1.0: USB hub found
[   52.938280] hub 1-0:1.0: 1 port detected
[   53.005383] usbcore: registered new interface driver cdc_acm
[   53.073177] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
ardmore: Start hotplug
AP rebooted Tue Nov 29 10:24:51 EST 2016; SAPD: Rebooting after provisioning
shutting down watchdog process (nanny will restart it)...

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

~ #

Have you configured  DHCP service for VPN at the conroller? 

go to Configuration > VPN Services > IPSEC > Address Pools and add an DHCP pool for RAP  

I have not, but i'm not setting it up as a RAP yet. Its just an AP215. Shouldn't need that parameter yet.

RAP will not show up if you don’t have a VPN DHCP pool at the controller that RAP is going to terminate. 

You only need a small private IP addesse pool for the number of RAPs you have. 

There is no RAP right now. Its just a normal AP215 that i'm trying to provision on an internal secondary controller set.

and just in case...  Yes, the controller VRRP address is the 192.168.241.0 address. Its a /23 network. 

If you provision AP as RAP, you need VPN DHCP pool.  You can create DHCP pool at both controllers that VRRP. 

I have not gotten to the RAP portion yet. For now I'm setting up the AP internally. The AP gets dhcp and can associate to the Aruba-master. I want to to associate to a different master. Both controllers are internal. Ignore this being a RAP for now.

-JF
Network Engineer

in that case, the easy way is point LMS IP in ap system profile to the controller you want your AP terminate.

go to: Configuration > Advanced Services > All Profile Management > AP > AP system

I've tried that as well with no change.

Here's an update. whent he AP reboots it shows this message:  

52.934225] hub 1-0:1.0: 1 port detected
[ 53.001338] usbcore: registered new interface driver cdc_acm
[ 53.069105] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
ardmore: Start hotplug
AP rebooted Wed Dec 31 16:44:44 PST 1969; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last rebootstrap reason: HELLO-TIMEOUT, 228 sec before: Last Ctrl msg: HELLO len=1185 dest=192.168.241.0 tries=10 seq=0
shutting down watchdog process (nanny will restart it)...

EDIT:   Answered my own question from your console output.

Its all internal so far. I wanted to get an AP provisioned on it before messing with external DNS records and such.