10-24-2011 03:47 PM
The master is running 220.127.116.11
The local is running 18.104.22.168
The local controller shows up status on the crypto tunnel to the master, the master shows likewise to the local.
The APs are all AP 125s. They are connected to a local subnet with DNS settings that are pointing the DNS name aruba-master to the local controller at IP address 172.20.60.10.
If I shutdown the local controller, the APs register and fallback to the master as desired. They will stay up, but the local controller will not allow the APs to show any SSIDs. (Second problem).
If I no-shut the local controller and reboot the APs from the master, the APs continuously reboot and upgrade...reboot and upgrade.
What do I need to do to fix the reboot/upgrade cycling?
What might I need to look at for the SSID's not showing up on the local controller?
The virtual-ap group is there, the ap system-profile is there, the virtual ap-group references an existing and working wlan ssid-profile .
Any advice would be appreciated.
10-24-2011 03:55 PM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
10-24-2011 04:05 PM
Since they don't match in your environment, that is why you see the upgrade, cycle, upgrade, cycle routine going on, on the AP side.
Equalize the versions (up to 5.x :) ) and that should work much better.
10-24-2011 07:52 PM
I will downgrade the local controller then test again tomorrow and report back.
10-24-2011 07:54 PM
10-25-2011 06:16 AM
The APs that are too old aren't 70s, they are 60, 61, and 65s. Would those work with the newer ArubOS?
10-25-2011 08:43 AM
3.8 dbi for 2.4 and
5.8 dbi for 5 Ghz is what it appears to me from the order.
Is that correct? It still squawks back that I need to enter a valid 5 ghz antenna gain value.