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?
Controller: Aruba 7210 (Qty:1)
It is possible that the access points were statically configured (pointed) to the old ip address, so that no discovery is occurring?
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...
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.
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.
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-1001AP Group ArjaanWiFiLocation name N/ASNMP sysLocation N/AMaster N/AGateway N/AIPv6 Gateway N/ANetmask N/AIP Addr N/AIPv6 Addr N/AIPv6 Prefix 64DNS IP N/ADNS IPv6 N/ADomain Name N/AServer Name aruba-masterServer IP N/AAntenna gain for 802.11a N/AAntenna gain for 802.11g N/AAntenna for 802.11a bothAntenna for 802.11g bothPKCS12 PASSPHRASE N/ASingle chain mode for Radio 0 0Single chain mode for Radio 1 0External antenna polarization for 5GHz Radio 0External antenna polarization for 2.4GHz Radio 0IKE PSK N/Aikepsk-hex-based NoPAP User Name N/APAP Password N/APPPOE User Name N/APPPOE Password N/APPPOE Service Name N/APPPOE CHAP Secret N/AUSB User Name N/AUSB Password N/AUSB Device Type noneUSB CSR-Key Storage NoUSB Device Identifier N/AUSB Dial String N/AUSB Initialization String N/AUSB TTY device data path N/AUSB TTY device control path N/AUSB modeswitch parameters N/AUplink VLAN 0Remote AP NoOCSP Default N/A--More-- (q) quit (u) pageup (/) search (n) repeat certificate DN N/ALink Priority Ethernet 0Link Priority Cellular 0Cellular modem network preference autoAP POE Power optimization disabledAP LLDP PSE detection disabledAP2xx prestandard POE detection DisabledMesh Role noneInstallation defaultLatitude N/ALongitude N/AAltitude N/AAntenna bearing for 802.11a N/AAntenna bearing for 802.11g N/AAntenna tilt angle for 802.11a N/AAntenna tilt angle for 802.11g N/AUsername of AP so that AP can authenticate to 802.1x using PEAP N/APassword of AP so that AP can authenticate to 802.1x using PEAP N/AMesh SAE sae-disable
Here the output
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...
Here the provision details of another AP which is not working (sorry the previous one was fresh AP).
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.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.