Wireless Access

Can someone help to see why my AP does not come up on the controller Please?

AP discovered  the master as below.

Got all network params from APboot env. Skipping DHCP
172.16.0.101 255.255.255.0 172.16.0.20
Running ADP...Done. Master is 172.16.0.252
PHY: eth0 (mdio@ffe24000:00) - Link is Up
 - 1000/Full

Is your master controller at 172.16.0.252?  If yes, type "show log system 50" to see the logs for that access point and "show ap database" to see if the access point has flags.

Thanks for your help!

Yes.

No ap under show ap database

Show log system 50:

Sep  5 15:11:33  KERNEL: [15988.285000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

Sep  5 15:18:15  KERNEL: [16390.053000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

Sep  5 15:18:36  KERNEL: [16411.289000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

Sep  5 15:20:18  KERNEL: [16513.246000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

Sep  5 15:20:39  KERNEL: [16534.482000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

Sep  5 15:27:20  KERNEL: [16935.246000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

Sep  5 15:27:41  KERNEL: [16956.487000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

Sep  5 15:38:16  KERNEL: [17591.413000]   0:Nae: configuring port/hw 5/17 iftype 1 for speed=2, duplex=1

can the controller ping the AP?  Why does the AP have a static ip address?

Yes, controller can ping ap.

It is a lab system to test mobility master and MD.

So set the static ip.

Have you checked the whitelist?

Did you mean ACL White list?

I mean if you have a Mobility Master then go to Managed Network/ Configuration/Access Points then go to Whitelist and check if there is the AP waiting to be approved.

Do you have AP licenses installed?

I post ap boot info to see anyone can help if anything wrong.

apboot> boot
Checking image @ 0xee000000
Invalid image format version: 0xffffffff
Checking image @ 0xeee00000
Copying image from 0xeee00000

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.

Aruba Networks
ArubaOS Version 6.3.1.0 (build 39345 / label #39345)
Built by p4build@tortuga on 2013-08-08 at 16:30:24 PDT (gcc version 4.5.1)

Memory: 510348k/524288k available (8348k kernel code, 13940k reserved, 540k data, 352k bss, 5008k init)
Processor 1 found.
Brought up 2 CPUs
PCI: Probing PCI hardware
pci 0000:00:00.0: PCI bridge to [bus 01-ff]
pci 0001:02:00.0: PCI bridge to [bus 03-ff]
pci 0000:00:00.0: enabling device (0106 -> 0107)
pci 0001:02:00.0: enabling device (0106 -> 0107)
ee000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
/proc/gfar_eth0_stats created
/proc/gfar_eth1_stats created
Enabling watchdog on CPU 1
Enabling watchdog on CPU 0

Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
Starting Kernel DES KAT ...Completed Kernel DES KAT
Starting Kernel AES KAT ...Completed Kernel AES KAT

Domain Name: arubanetworks.com
No panic info available
Ethernet port 1 mode: active-standby
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): bond0: link is not ready
bonding: bond0: enslaving eth0 as a backup interface with a down link.
ADDRCONF(NETDEV_UP): eth1: link is not ready
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 66, num_radios 2 (jiffies 3274)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 16
radio 1: band 0 ant 0 max_ssid 16
ethernet_device_event: dev eth0 is up
ASAP Slowpath initialized
Starting watchdog process...
Got all network params from APboot env. Skipping DHCP
172.16.0.10 255.255.255.0 172.16.0.20
Running ADP...Done. Master is 172.16.0.252
PHY: eth0 (mdio@ffe24000:00) - Link is Up - 1000/Full
bonding: bond0: link status definitely up for interface eth0.
bonding: bond0: making interface eth0 the new active one.
bonding: bond0: first active interface up!
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
wifi0: AP type AP-225, radio 0, max_bssids 16
wifi1: AP type AP-225, radio 1, max_bssids 16
shutting down watchdog process (nanny will restart it)...

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

~ #

See if the controller can ping the access point.

I would remove all of the access point variables and allow the controller to give the access point dhcp.  One wrong static configuration can keep an access point from coming up.

Hi,
I had a similar problem once, and I finally solved it by resetting the APs. (via console or reset button)
After returning to Instant, I converted back to Controller AP Campus and ended up resolving.

mTonini
ACMA 

Thanks for everyone's help! The issuse was the MM license was not allocated to controller pool though AP, PEF RF protect were allocated.

Assumed controllers do not need MM license and MM needs mm license.

Cheers!