Wireless Access

Changing IP address of the Aruba controller caused all APs to be disconnected.  All APs are connected directly to the Aruba Controler, and "show int" command shows that all APs are still connected, but none of the APs are accessible/visiable in WebUI.

Per "show ap database", APs are still referring to an old IP address of the Aruba controller.  

Any ideas/suggestions on how to make APs visible to Aruba Controller?

Thank you,

Hi, 

How many APs are deployed ?

How the AP is identifying the master ? (static, dhcp, DNS)?

please share "show datapath sess table <ip of AP> " output and show ip interface brief ouput. 

also let me  know the old IP. 

Thank you for the reply.

Old IP: 172.25.2.2

New IP: 172.25.2.4

loopback: 172.25.2.3

Number of AP: 20

(aruba) #show ip interface brief

Interface IP Address / IP Netmask Admin Protocol
vlan 711 172.25.2.4 / 255.255.254.0 up up
vlan 1 unassigned / unassigned down down
vlan 501 192.168.0.2 / 255.255.240.0 up up
loopback 172.25.2.3 / 255.255.255.255 up up

(aruba) #show datapath session

Datapath Session Table Entries
------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT
D - deny, R - redirect, Y - no syn
H - high prio, P - set prio, T - set ToS
C - client, M - mirror, V - VOIP
I - Deep inspect, U - Locally destined

Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Flags
-------------- -------------- ---- ----- ----- ---- ---- --- --- ----------- ---- -----
172.25.2.1 172.25.2.4 6 1023 22 0/0 0 0 0 local 1c4
172.25.2.4 172.25.2.1 6 22 1023 0/0 0 0 0 local 1c4 C
172.25.2.1 224.0.0.2 17 1985 1985 0/0 0 0 0 1/21 36c3 FC
172.25.2.3 224.0.0.2 17 1985 1985 0/0 0 0 0 1/21 36c2 FC
10.9.1.12 172.25.2.15 17 53 49152 0/0 0 0 1 1/12 12 FI
172.25.2.15 10.9.1.12 17 49152 53 0/0 0 0 1 1/12 12 FCI
172.25.2.37 10.51.0.110 17 8211 8211 0/0 0 0 1 1/8 25 FC

172.25.2.47 10.51.0.110 17 8211 8211 0/0 0 0 1 1/2 6a FC
172.25.2.42 10.51.0.110 17 8211 8211 0/0 0 0 0 1/14 f FC
172.25.2.11 10.51.0.110 17 8211 8211 0/0 0 0 0 1/18 20 FC
172.25.2.17 10.51.0.110 17 8211 8211 0/0 0 0 1 1/6 1a FC
172.25.2.31 10.51.0.110 17 8211 8211 0/0 0 0 0 1/3 3 FC
172.25.2.26 10.51.0.110 17 8211 8211 0/0 0 0 0 1/4 c FC
172.25.2.27 10.51.0.110 17 8211 8211 0/0 0 0 0 1/19 71 FC
172.25.2.4 172.24.250.128 1 945 0 0/0 0 0 1 1/21 1c FI

(aruba) #

I see that APs are trying to communicate to a different Ip (10.51.0.110) ?

can  you tell what that  IP is ?

172.25.2.37 10.51.0.110 17 8211 8211 0/0 0 0 1 1/8 25 FC

172.25.2.47 10.51.0.110 17 8211 8211 0/0 0 0 1 1/2 6a FC
172.25.2.42 10.51.0.110 17 8211 8211 0/0 0 0 0 1/14 f FC
172.25.2.11 10.51.0.110 17 8211 8211 0/0 0 0 0 1/18 20 FC

Ho ware they discovering the MASTER ?

 what is the dhcp server ? 

It seems that there was a problem with our RADIUS server - it was blocking request coming from APs

Thank you for the help

I seem to be having the same issue.  My master is 10.130.60.3 that contains half of my AP's.  The Local is 10.130.60.4 which contains the of half of AP's.  Several of the older AP's still have the msater IP yet should be using the Local.  Can I configure the AP's via CLI to have there switch IP/serverIP to point to the local.  I have tried provisioniing via GUI and it has not taken.  In the enclosed document you will see the group SR-RAP-2 should point to the local controller.

Also would this cause a heartbeat issue?

Attachment(s)

Heartbeats.txt   5 KB 1 version

A controller can have multiple ip addresses, but only one controller ip.  That is the main ip address that the controller uses to communicate with other devices.  If an access point discovers or is redirected to an ip address on a controller, the controller responds with the controller ip and that is what the access point communicates with.  You can find out what the controller ip address is by typing "show controller-ip".

Changing the controller ip address typically requires a controller reboot.

EDIT:

An access point typically will stay on the controller it first discovers, unless there is an LMS-IP address in its ap-group, in which case it would be redirected to that controller.  Again if an access point is provisioned to only point to a single controller it will stay there, unless there is an LMS-IP address in its ap system profile.

How are those access points discovering the controller?

Thank you a quit response, but I want to change the switch IP on the AP.  Everything on the controller is correct.  I would like to ensure that the switch IP reflects the correct information.  In the show ap dataebase long command it show that some of my AP's are pointing to the master instead of the local.  Can we change that parameter via CLI?

How does the AP discover the master controller?  Is it dynamic (dhcp option, dns discovery), or is it statically configured?

Type 

show ap provisioning ap-name <name of ap>

If there is a "Master" or "ServerIP" parameter, that means that access point is statically provisioned and that ip address would need to be removed using the ap provisioning dialog.  Before removing that ip address, you would need to ensure that dynamic discovery is working.

Initially I configured each AP.  Each AP has a static IP due to the bridging between the guest and secured network.  When I tried to insert the new serverip, some would take and some would not...

When you say "some would take", you mean you would provision them and then what would happen? 

If in the ap system profile of the ap-group there is an lms-ip, the access point will be redirected to a different controller, regardless. 

Statically configuring the AP to a controller only tells the access point what controller to receive its configuration from.  If the ap-group of that access point has an ap system profile that has an LMS-IP, the access point will be redirected away from the initial controller and to the LMS-IP.

Thank you for the information,