Wireless Access

Dear Airheads,

We are struggling to change the IP address of the controller.

Controller current IP: 10.105.24.6/22 (VLAN 124)

Controller new IP: 10.105.24.10/22 (same subnet)

WiFi system is working fine with the existing controller IP address. Client need to change it with new IP to uniform the IP of controller in all location.

- Changed the controller IP to VLAN 1

- Then remove the IP from VLAN 124

- Rebooted the controller (reloaded)

- Gave the new IP to VLAN 124 (10.105.24.10/22)

- Changed the controller IP back to VLAN 124

- Rebooted the controller

- None of the AP registering on the controller with new IP

- Rebooted some APs physically (no good result)

- Verified the ADP in controller (enabled)

- Configured option 43 and 60 (note: controller is the DHCP server)

- Tested again with restart the APs.

- None of the APs comes UP

- Rolled back to the old IP (all APs registered and working fine)

Any one can help and give a clue?

Setup:

Switching: Nortel

Controller:  Aruba 7210 (Qty:1)

Reg,
Shamz

It is possible that the access points were statically configured (pointed) to the old ip address, so that no discovery is occurring?

Dear Cjoseph, 

All APs are configured with Dynamic (DHCP)

Right, but it is possible that the master ip is hardcoded.  I would attempt to provision an access point and see if there are any static ip addresses for the master ip address or server ip address...

Dear Cjoseph,

Many thanks for your quick response.

We scheduled a maintenance window on next Monday.

let me access to an working through console and verify your concern.

I'll update

Reg,

shamz

If you can SSH to the controller, type this to see if any of the information is hardcoded:

show ap provisioning ap-name <name of ap>

NOTE:  No need to use the console with the command above.

Dear Joseph,

i think you pointed the issue

here the output

(Arjaan-WLC) # show ap provisioning ap-name ADMC-AP-101-11 01

AP "ADMC-AP-1001" Provisioning Parameters
-----------------------------------------
Item Value
---- -----
AP Name ADMC-AP-1001
AP Group ArjaanWiFi
Location name N/A
SNMP sysLocation N/A
Master N/A
Gateway N/A
IPv6 Gateway N/A
Netmask N/A
IP Addr N/A
IPv6 Addr N/A
IPv6 Prefix 64
DNS IP N/A
DNS IPv6 N/A
Domain Name N/A
Server Name aruba-master
Server IP N/A
Antenna gain for 802.11a N/A
Antenna gain for 802.11g N/A
Antenna for 802.11a both
Antenna for 802.11g both
PKCS12 PASSPHRASE N/A
Single chain mode for Radio 0 0
Single chain mode for Radio 1 0
External antenna polarization for 5GHz Radio 0
External antenna polarization for 2.4GHz Radio 0
IKE PSK N/A
ikepsk-hex-based No
PAP User Name N/A
PAP Password N/A
PPPOE User Name N/A
PPPOE Password N/A
PPPOE Service Name N/A
PPPOE CHAP Secret N/A
USB User Name N/A
USB Password N/A
USB Device Type none
USB CSR-Key Storage No
USB Device Identifier N/A
USB Dial String N/A
USB Initialization String N/A
USB TTY device data path N/A
USB TTY device control path N/A
USB modeswitch parameters N/A
Uplink VLAN 0
Remote AP No
OCSP Default N/A
--More-- (q) quit (u) pageup (/) search (n) repeat certificate DN N/A
Link Priority Ethernet 0
Link Priority Cellular 0
Cellular modem network preference auto
AP POE Power optimization disabled
AP LLDP PSE detection disabled
AP2xx prestandard POE detection Disabled
Mesh Role none
Installation default
Latitude N/A
Longitude N/A
Altitude N/A
Antenna bearing for 802.11a N/A
Antenna bearing for 802.11g N/A
Antenna tilt angle for 802.11a N/A
Antenna tilt angle for 802.11g N/A
Username of AP so that AP can authenticate to 802.1x using PEAP N/A
Password of AP so that AP can authenticate to 802.1x using PEAP N/A
Mesh SAE sae-disable

Attachment(s)

Arjaan Wireless_.txt   4 KB 1 version

Dear Joseph,

Here the output

Attachment(s)

Arjaan Wireless_.txt   4 KB 1 version

Why doesn't the customer just use the console to just  change the ip address and subnet mask of the interface VLAN 124?

That's the thing we did. just changed the iP address of VLAN 124. 

But after the APs didn't comes up.

Can i change the master discovery to master controller IP address instead or host controller name. will work out ?

Are the access points on the same VLAN as the controller management ip address?

If you change the management ip address the AP looks at, if it is orphaned, you have to take it down from the ceiling and reprogram it via the console, unfortunately.

All APs and Controller in same VLAN 

How long did you wait for the access points to come up?  You should type "show log system 50" and "show ap database" to see if there are any messages and if any access points have any flags...

The controller-ip is vlan 124, right?

We waited more than 30 minutes. None of the AP comes up. 

the controller-Ip is VLAN 124,Correct.

Regarding the log commands, I am trying for a maintenance window for today first half itself. Let me update. 

Is it possible that you are supplying dhcp options 43 and 60 that are pointing the access  points to the old ip address?

Initially we didn't configure any options. Once we notify that the APs not coming up, we configured the option 43 (NEW IP of controller) and option 60 (ArubaAP). But even though APs didn't come up.

You should put a console on an AP during that time to see what the discovery process is...

Dear Cjoseph,

Here the provision details of another AP which is not working (sorry the previous one was fresh AP). 

Attachment(s)

Arjaan Wireless-2_.txt   4 KB 1 version

Based on those provisioning details the masterip has been hard set.  As Colin mentioned this means that discovery is not taking place.

What you could do is this,

1. configure a VRRP address to be that old one (10.105.24.6).  This will allow the APs to all come up.

2. Reprovision the APs with the new masterip or better yet make it dynamic and use something like dhcp or dns.

3. Once all the APs are sorted out, you can then go ahead and remove the VRRP.