Wireless Access

hi all, i am doing config in my new aruba controller 650 an acess points ap-135. there is a problem that Unprovisioned Access Points is not detected in my controller. i have already configured dhcp server in my controller and the ap is get dynamic ip from controller. i can ping the controller from acces points. i have read the forum and CP Sec disabled.

this is the ping  :

PING 10.200.50.253 (10.200.50.253): 56 data bytes
64 bytes from 10.200.50.253: icmp_seq=0 ttl=64 time=2.4 ms
64 bytes from 10.200.50.253: icmp_seq=1 ttl=64 time=1.0 ms
64 bytes from 10.200.50.253: icmp_seq=2 ttl=64 time=1.0 ms
64 bytes from 10.200.50.253: icmp_seq=3 ttl=64 time=1.5 ms
64 bytes from 10.200.50.253: icmp_seq=4 ttl=64 time=1.4 ms

--- 10.200.50.253 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss

this is controller ip :

#show controller-ip

Switch IP Address: 172.16.0.254

Switch IP is configured to be Vlan Interface: 1

Switch IPv6 address is not configured.

this is ap database :

#show ap database

AP Database
-----------
Name Group AP Type IP Address Status Flags Switch IP
---- ----- ------- ---------- ------ ----- ---------

Flags: U = Unprovisioned; N = Duplicate name; G = No such group; L = Unlicensed
I = Inactive; H = Using 802.11n license; D = Dirty or no config
X = Maintenance Mode; P = PPPoE AP; B = Built-in AP
R = Remote AP; R- = Remote AP requires Auth; C = Cellular RAP; c = CERT-b
ased RAP; 1 = 802.1x authenticated AP; 2 = Using IKE version 2
M = Mesh node; Y = Mesh Recovery

Total APs:0

Yes is detected...

Look check that its not in access denied on the monitoring tab on the summery it should appear in read you click on it and it will say access denied...

Now at this poing you need to give it permission.

If you want to do it the easy way you can go to the configuration tab, and go to the  control security plane

Check autocert provisioning... and then click ok

When you done then you revert that change... thats for security reasons... but well you can do it like that faster... 

Oh didnt read you have CP off...

IF you dont see it on the controller try consoling the AP to see if he find the Aruba master with the correct ip address

I see you got the AP on another network

Did you put the aruba-master record on the DNS pinting to 172.16.0.254

So when the AP comes up he knows thats the ip of the master?

And of course ont he DHCP server did you configured the DNS server i mean the internal DNS server which tells the AP which will be the aruba master?

how to find the Aruba master with the correct ip address in ap console ?

I see you got the AP on another network

Did you put the aruba-master record on the DNS pinting to 172.16.0.254

I still using default ip address for the controller.

i have already set vlan 800 with ip address 10.200.50.253 with dhcp server and the ap get an ip 10.200.50.252

i have already set gi1/5 access with vlan 800 and connect my ap to that.

sorry if i ask a basic question :)

this is ap log :

cli| ADRS provision failed, code: connection-failed
Jan 1 00:32:22 cli[1177]: <341004> <WARN> |AP 6c:f3:7f:c3:67:28@10.200.50.252
cli| Isc_send_request
Jan 1 00:32:53 cli[1177]: <341005> <ERRS> |AP 6c:f3:7f:c3:67:28@10.200.50.252
cli| ADRS provision failed, code: connection-failed
Jan 1 00:33:24 cli[1177]: <341004> <WARN> |AP 6c:f3:7f:c3:67:28@10.200.50.252
cli| Isc_send_request

okay let see

you got set this way up

you got the Controller set on 172.16.0.254

You also did an interface vlan with the ip 10.200.50.253

Okay go the webgui go to configuration go to controller and on the controller ip details you will see this address on it

172.16.0.254 which should be on vlan 1

On the dropdown choose vlan800 10.200.50.253 it should appear

click apply

save the configuration

And you will need to reboot the controller...

Now the thing is that you should always point the AP  to the master IP address and now the master ip address is 172.16.0.254

For him aruba-master = 172.16.0.254 not 10.200.50.253

With the change i just told you the aruba-master will be  10.200.50.253 and it should find it correctly after you reboot

Now if you trunking that vlan 800 to your internal network then you shoud put the default gatway of that network pointing to the switch that is routing that vlan...

But for now just do the change i just told you and the AP should come up...

Before rebooting you can put another port on vlan 800 if you would like and you can plug your laptop or computer there and well save the config

Im guessing you are doing this offline you your pc and the controller and the AP just to test though....

But when you connect it ot the real Network you will have your APs on another vlan

Let say

You got your controller with vlan 800 with the ip you said 10.200.50.253

You got that vlan trunked to your switch core and then trunked that vlan 800 back and on the switch core an ip interface vlan which will be the default gateway of that Wireless controller... let say you will have an ip interface vlan with the ip 10.200.50.1 on the SwitchCORE

And your default gateway will be the CORE switch which is routing that vlan(for now thecontroller should be just a layer 2 at this momment which is recommended.

Now just with that you should have aministration on the network of the Wireless contorller.

Now the APs might not be on that vlan... they will be in X vlan...

So now you got the dilema that you need your APS can find the controller.

It can be done in many ways....

1-By statically configuring it

2-by DNS

3-by DHCP

4-with ADP protocol(which will find it if the AP is on the same vlan of the Wireless controller)

I llike the DNS one

On the DNS server you put a new record aruba-master which willl be 10.200.50.253

Now if you connect the AP on any vlan that has a DHCP server that distribute the DNS server ip on that dhcp scope  he willl get the IP in X vlan and also but as he will resolve with the DNS server that the master is 10.200.50.253 he willl find the controller and you should see it ont he screen.

Hope this help you

@ Im guessing you are doing this offline you your pc and the controller and the AP just to test though....

you are right :)

I am still looking for how to configure this stuff 

Can you explain in details this :

1-By statically configuring it >> might be this is the easy way but i have to do it on ap's console ?

2-by DNS

3-by DHCP

4-with ADP protocol(which will find it if the AP is on the same vlan of the Wireless controller)

Lets go step by step

Can you see the AP now you did what i told you ?

i have done this :

okay let see

you got set this way up

you got the Controller set on 172.16.0.254

You also did an interface vlan with the ip 10.200.50.253

Okay go the webgui go to configuration go to controller and on the controller ip details you will see this address on it

172.16.0.254 which should be on vlan 1

On the dropdown choose vlan800 10.200.50.253 it should appear

click apply

save the configuration

And you will need to reboot the controller...

Now the thing is that you should always point the AP  to the master IP address and now the master ip address is 172.16.0.254

For him aruba-master = 172.16.0.254 not 10.200.50.253

With the change i just told you the aruba-master will be  10.200.50.253 and it should find it correctly after you reboot

but still cant detect it

this is tha ap sum

# show sum

Name :AP1
Domain :
Address :0.0.0.0
Content Filtering :disable
Terminal Access :disable
Organization :
Airwave Address :0.0.0.0
Airwave Shared Key :
Airwave Config Via :DHCP
Syslog Server :0.0.0.0
Syslog Level :warn
Band :all
Master *:10.200.50.252
Master Key :6191342201c1e2d5c326e7e9c7023749e56da72af4c1e967da
Elected Time :12m:51s
Mesh :enable
Dynamic Radius Proxy :disable
NTP Server :
Configuration Dirty :disable
Allow New APs :enable
Classification :disable
Wireless Containment :disable
Wired Containment :disable
Rogue Containment :disable
LED Off :disable
Airwave :Not Set Up
Image Server State :success
Image Server Message :Success
New Image Version :
New Image URL :
Factory SSID :instant
Image Sync Via :Master
Client Alerts :0
Active Faults :0
IP Address :10.200.50.252
Serial Number :AX0141813
OpenDNS Status :Not connected
TFTP Dump Server :0.0.0.0
VPN Status :Not Set Up
0 Clients
---------
MAC Name IP Address Network Access Point
--- ---- ---------- ------- ------------
1 Network
---------
Key Name Clients
--- ---- -------
instant instant 0
1 Access Point
--------------
MAC IP Address Name Clients Need Antenna Confi
g
--- ---------- ---- ------- ------------------
-
6c:f3:7f:c3:67:28 10.200.50.252 6c:f3:7f:c3:67:28 0 No
RADIUS Servers
--------------
Name IP Address Port Key
Timeout Retry Count NAS IP Address NAS Identifier RFC3576
---- ---------- ---- ---
------- ----------- -------------- -------------- -------
InternalServer 127.0.0.1 1616 4b4f5340018718468e84e46eebb559ae8fbcb438a87415
bb05 5 3
RTLS Servers
------------
Type IP Address Port Key Frequency
---- ---------- ---- --- ---------
Aeroscout 0.0.0.0 0
Airwave 0.0.0.0 0 0
1 AP Class
----------
Name APs
---- ---
Cassiopeia 1
Uplink type :Ethernet
Uplink status :UP
Manual Blacklist Count :0
Dyn Blacklist Count :0
Certificate Installed: :No
Internal Radius Users: :0
Internal Guest Users: :0
Info timestamp :813

wait a second! is that an instant AP???

When you connect it do you see on the wireless a instant SSID?

Look if its an instant AP and you DO NOT want to use it as instant AP and it will be a managed AP by the wireless controller you need to convert it to managed AP...

Remenber this is if you dont want to use it as Instant AP.

Let say you dont want it to use it as INSTANT AP and you would like to use it as a AP managed by the wireless controller which i see is what you want

You connect to the SSID instant,

user

admin

pass

admin

Go to maintanience tab i think its the name

And you should see a tab in there to convert it... he will ask you whats the IP of the controller you put in there.. and he will convert...

yes i thought that this thread http://community.arubanetworks.com/t5/Access-Points-and-Mesh-Routers/AP-105-s-are-unable-to-be-provisioned-anymore/td-p/35213 is have a problem same with me right?

Yes thats what i think!

how i can convert user console because i have tried it using web but still cant convert it

See if the access point is broadcasting the "Instant" wireless network.  If it is connect to it using your laptop and see if you get an ip address....

If you get an ip address with your laptop, open a browser and try to go to http://instant.arubanetworks.com.  If a page comes up for the Instant virtual controller, login with "admin" and "admin".  If you get in go to Maintenence> Convert and Convert to Campus AP and point it to the ip address of your controller to convert it.

thank you, now i can convert my 135 ap's 

Awesome.  Happy Holidays!

now ia have a problem with this one.

Model: AP-13x
CPU: 88F6560 A0 (DDR3)
Clock: CPU 1600MHz, L2 533MHz, SysClock 533MHz, TClock 200MHz
DRAM: 256MB
POST1: passed
Flash: 16 MB
Power: DC
LAN: done
PHY: done
PEX 0: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00.00 00 11ab 6560 00005 02 f1000000 00000000 00000000 00000000
00.01 00 168c 0030 00002 01 90000000 00000000 00000000 00000000
PEX 1: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
01.00 00 11ab 6500 00005 02 f1000000 00000000 00000000 00000000
01.01 00 168c 0030 00002 01 94000000 00000000 00000000 00000000
Net: eth0, eth1
Radio: ar9390#0, ar9390#1

Hit <Enter> to stop autoboot: 0
Checking image @ 0xf8100000
Invalid image format version: 0xffffffff
Checking image @ 0xf8800000
Invalid image format version: 0xc

This AP is delivered without os image. Can i copy the os image from another ap? I have already searching ap's os image but still cant find it. 

Is that the only AP with the problem?  What is the controller's OS version?

The controller should deliver the OS to the AP.

this is my cotroller

i have config 2 of them but this one is came with that messege

Okay.

On the console of that AP, press enter to interrupt the boot until you get to the "apboot>" prompt.

type "clear os" and reboot.

It should come up as an instant AP again.  Connect to the "instant" SSID and try to convert once more...

still with that message :

apboot> clear os
Erasing flash sector @ 0xf8100000....done
Erased 1 sectors
apboot> ?
? - alias for 'help'
boot - boot the OS image
clear - clear the OS image or other information
dhcp - invoke DHCP client to obtain IP/boot params
factory_reset - reset to factory defaults
help - print online help
mfginfo - show manufacturing info
osinfo - show the OS image version(s)
ping - send ICMP ECHO_REQUEST to network host
printenv - print environment variables
purgeenv - restore default environment variables
reset - Perform RESET of the CPU
saveenv - save environment variables to persistent storage
setenv - set environment variables
tftpboot - boot image via network using TFTP protocol
upgrade - upgrade the APBoot or OS image
version - display version
ÿpboot> reset

APBoot 1.2.6.7 (build 30025)
Built: 2011-08-30 at 17:41:16

Model: AP-13x
CPU: 88F6560 A0 (DDR3)
Clock: CPU 1600MHz, L2 533MHz, SysClock 533MHz, TClock 200MHz
DRAM: 256MB
POST1: passed
Flash: 16 MB
Power: DC
LAN: done
PHY: done
PEX 0: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00.00 00 11ab 6560 00005 02 f1000000 00000000 00000000 00000000
00.01 00 168c 0030 00002 01 90000000 00000000 00000000 00000000
PEX 1: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
01.00 00 11ab 6500 00005 02 f1000000 00000000 00000000 00000000
01.01 00 168c 0030 00002 01 94000000 00000000 00000000 00000000
Net: eth0, eth1
Radio: ar9390#0, ar9390#1

Hit <Enter> to stop autoboot: 0
Checking image @ 0xf8100000
Invalid image format version: 0xffffffff
Checking image @ 0xf8800000
Invalid image format version: 0xc
eth0: down
eth1: down
ADP multicast 1
ADP broadcast 1

Abort
apboot>

Don't worry about that message.  Type "dhcp" at the apboot> prompt to see if it gets an ip address.  I don't see that happening...

I also do not see the link coming up on eth0...

apboot> dhcp
eth0: up, 100 Mb/s, full duplex
DHCP broadcast 1
DHCP IP address: 10.200.50.251
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 10.200.50.254
DHCP DNS server: 10.200.50.254
DHCP DNS domain: xxxxxxxxxxx
Controller address: 2xx.1xx.2xx.4x

okay.  type "boot" and let us see the output..

apboot> boot
Checking image @ 0xf8100000
Invalid image format version: 0xffffffff
Checking image @ 0xf8800000
Invalid image format version: 0xc
eth0: up, 100 Mb/s, full duplex
Using eth0 device
TFTP from server 2xx.1xx.2xx.4x; our IP address is 10.200.50.251; sending throug
h gateway 10.200.50.254
Filename 'armv5te.ari'.
Loading: ###########T ######T #########T ##T ###T ######T ############T #T ###T
##T ##T #T #T
done
Bytes transferred = 3858304 (3adf80 hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Automatic boot of image at addr 0x02000000 ...
## Booting image at 02000200 ...
Uncompressing... done

Aruba Networks
ArubaOS Version 6.1.3.5 (build 35523 / label #35523)
Built by p4build@corsica.arubanetworks.com on 2012-09-28 at 07:20:25 PDT (gcc ve
rsion 4.3.3)
Memory: 256MB = 256MB total
Memory: 245376KB available (2564K code, 8864K data, 2768K init, 0K highmem)
Calibrating delay loop... 1597.44 BogoMIPS (lpj=1597440)
PEX0 interface detected Link X1
PEX1 interface detected Link X1
wdt: registered with refresh
Enabling Watchdog
i2c /dev entries driver
i2c-arran: using default base 0xf1018100

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-staEthernet Channel Bonding Driver: v3.5.0 (Novembe
r 4, 2008)
ndby
eth0: link up, full duplex, speed 100 Mbps
ADDRCONF(NETDEV_UP): bond0: link is not ready
eth0: link up, full duplex, speed 100 Mbps
bonding: bond0: making interface eth0 the new active one.
bonding: bond0: first active interface up!
bonding: bond0: enslaving eth0 as an active interface with an up link.
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
eth1: link down
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth1: link down
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 51, num_radios 2 (jiffies 1845)
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 register
ethernet_device_event: dev eth0 is up
setting bond0 as bridge child
setting gre0 as split child
Starting watchdog process...
Got all network params from APboot env. Skipping DHCP
172.16.1.3 255.255.255.0 172.16.1.1
Running ADP...eth0: link up, full duplex, speed 100 Mbps                    >>>> i press ctrl+c
^C~ #

That looks right...

On the controller, type "show log system 50" and then type "show ap database"

Cotroller log :

Dec 21 14:18:43 KERNEL: 2:<4>process `trapd' is using obsolete setsockopt SO_BSDCOMPAT
Dec 21 14:18:52 :304001: <ERRS> |stm| Unexpected stm (Station management) runtime error
at data_path_handler, 642, data_path_handler: recv - Network is down
Dec 24 09:48:30 :303022: <WARN> |AP d8:c7:c8:cc:36:c2@10.200.50.251 nanny| Reboot Reaso
n: No reboot message found.
Dec 24 09:50:58 :311010: <WARN> |AP d8:c7:c8:cc:36:c2@10.200.50.251 sapd| AP could not b
oot from flash -- bad checksum                         >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> i think this the one right ?
Dec 24 13:35:16 :303022: <WARN> |AP 6c:f3:7f:c3:67:30@10.200.50.250 nanny| Reboot Reaso
n: AP rebooted Sat Jan 1 00:13:00 UTC 2000; Image Upgrade Successful
Dec 24 13:58:39 :311002: <WARN> |AP 6c:f3:7f:c3:67:30@10.200.50.250 sapd| Rebooting: SA
PD: Rebooting after provisioning
Dec 24 13:58:39 :303086: <ERRS> |AP 6c:f3:7f:c3:67:30@10.200.50.250 nanny| Process Manag
er (nanny) shutting down - AP will reboot!
Dec 24 13:59:17 :303022: <WARN> |AP 6c:f3:7f:c3:67:30@10.200.50.250 nanny| Reboot Reaso
n: AP rebooted Mon Dec 24 13:58:39 SAST 2012; SAPD: Rebooting after provisioning
Dec 24 14:04:29 :311002: <WARN> |AP 6c:f3:7f:c3:67:30@10.200.50.250 sapd| Rebooting: SA
PD: Rebooting after provisioning
Dec 24 14:04:29 :303086: <ERRS> |AP 6c:f3:7f:c3:67:30@10.200.50.250 nanny| Process Manag
er (nanny) shutting down - AP will reboot!

AP Database :

# show ap database

AP Database
-----------
Name Group AP Type IP Address Status Flags Switch IP
---- ----- ------- ---------- ------ ----- ---------
AP-135-01 xxxxxxx 135 1.1.1.7 Up 54m:38s R 2xx.1xx.2xx.4x
AP-135-02 xxxxxxx 135 1.1.1.6 Down R 2xx.1xx.2xx.4x

Flags: U = Unprovisioned; N = Duplicate name; G = No such group; L = Unlicensed
I = Inactive; H = Using 802.11n license; D = Dirty or no config
X = Maintenance Mode; P = PPPoE AP; B = Built-in AP
R = Remote AP; R- = Remote AP requires Auth; C = Cellular RAP; c = CERT-based RAP;
1 = 802.1x authenticated AP; 2 = Using IKE version 2
M = Mesh node; Y = Mesh Recovery

Total APs:2

I have already configured 2 aps

the new one is not detected

The message "Dec 24 09:50:58 :311010: <WARN> |AP d8:c7:c8:cc:36:c2@10.200.50.251 sapd| AP could not b
oot from flash -- bad checksum" just says why it rebooted.  The fact that the message is there means that it recovered and it contacted the controller.  It should show up in "show ap database"

at the "apboot>" prompt, type "purge" then "save", then "boot"

how i can change the boot method from tftp boot to flash. i still looking for the image of the ap but cant find it. can i copy the image ap from the other one? 

so it will be the same with other ap that i have configured

When the AP boots with the message:

ArubaOS Version 6.1.3.5 (build 35523 / label #35523)
Built by p4build@corsica.arubanetworks.com on 2012-09-28 at 07:20:25 PDT (gcc ve
rsion 4.3.3)
Memory: 256MB = 256MB total
Memory: 245376KB available (2564K code, 8864K data, 2768K init, 0K highmem)
Calibrating delay loop... 1597.44 BogoMIPS (lpj=1597440)

It already has an image....  The next thing you need to see is if it is finding the controller.

At the beginning of this thread you sent this output:

#show controller-ip

Switch IP Address: 172.16.0.254

Switch IP is configured to be Vlan Interface: 1

Switch IPv6 address is not configured.

That means if the AP contacts the controller on ANY ip address, it will redirect the AP to 172.16.0.254.  That happens because the controller by default assigns its switch IP to the LOWEST vlan on the box.  You can change this by:

config t

controller-ip vlan <vlan#>

thank you verry much, you are verry helpfull. i have configured all of the APs

#show ap database

AP Database
-----------
Name Group AP Type IP Address Status Flags Switch IP
---- ----- ------- ---------- ------ ----- ---------
AP-135-01 Indosat 135 1.1.1.7 Up 1h:33m:31s R 202.138.246.46
AP-135-02 Indosat 135 1.1.1.6 Down R 202.138.246.46
AP-135-03 Indosat 135 1.1.1.8 Up 3m:1s R 202.138.246.46

Flags: U = Unprovisioned; N = Duplicate name; G = No such group; L = Unlicensed
I = Inactive; H = Using 802.11n license; D = Dirty or no config
X = Maintenance Mode; P = PPPoE AP; B = Built-in AP
R = Remote AP; R- = Remote AP requires Auth; C = Cellular RAP; c = CERT-based RAP;
1 = 802.1x authenticated AP; 2 = Using IKE version 2
M = Mesh node; Y = Mesh Recovery

Total APs:3

#