Recently my colleagues changed the IP-addresses of our 2 WLC (Master and Local).
Since then no new AP:s have appeared in the Airwave.
The configuration in our Airwave in Device Setup -> Discover is first the 2 WLC:s and then under Network they have configured 2 networks. Each is the ip-address to the controller with at netmask of 255.255.255.255
In this configuration the WLC are still on the old ip-addresses. Am i Correct when i assume that this is the reasson for no new AP:s appearing in the Airwave?
And also, is it safe to just change these settings to the new IP-addresses under Network? We currently have a large number of devices monitored in this Airwave and i dont want to interuppt operations doing any sudden changes.
Airwave obtains information by polling a controller at its ip address. It also receives AMON messages with the source address of its ip address. If it cannot poll that ip address, it will not receive information. If it is not receiving information, you need to change the ip address to the proper management ip address of the controller.
When the IP address was changed, did the change get made directly on the WLCs? If so, we need to mirror the change in AMP.
To make the change:
Navigate to Devices -> jump to folder where the WLCs are -> select WLC. On the monitor page - check WLC IP address, I'd expect up/down status of the WLC to be down if the IP address is incorrect. Go to manage tab - update IP address to the new address, then Save and Apply. Once you correct the IP, you can force a 'poll now' from the WLC monitor page.
Once you do the above for both WLCs, and then you can adjust the Device Setup -> Network Scan for the correct IP block if the subnet or address range has changed.
The ip address on the controllers are correct. But the configuration is "missmatched". Could this be the cause for this problem?
So i dont have to change the network configuration under device setup -> Discover?
Config mismatch wouldn't affect device discovery. What AMP version are you on? If on 8.2.7/184.108.40.206 - you can use the Enter Commands menu of the AMPCLI to run some SNMPwalks to test.
I usually do a walk of the .1 OID to get the entire MIB table -> if you do that and see the portion that has the AP list, then you can spot check to see how many APs there should be vs how many we actually have in AirWave.
Im on 220.127.116.11.
I cant access the cli yet, it seems my permission level isnt enough.
Will fix this asap.
Another issue i have noticed is that the Airwave have shown the same client-numer for a while now. The actual client number if much larger when looking at the local controller.
I assume this might go hand in hand with no new AP:s appearing?
Yes, client count and the missing APs are connected issues. Once the AP issue is resolved, the client count should be taken care of as well.
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 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.