01-11-2012 10:38 AM
So I had a RAP5 up and working fine, provisioned from our master which at the time was a 6000.
Last night I demoted the 6000 to be a local controller and promoted our 3600 to be the master. Everything seemed fine with our APs, but since then my RAP5 is stuck in a constant upgrade-reboot-upgrade loop.
SInce it was having problems I held down the reset on the RAP and let it reboot to defaults. It came up with the crazy old 3.x software load. I give it the IP of the new master controller. It connects fine, says it has to upgrade and then reboots. After that it come up in the new 6.x WebUI, and the connectivity tabs reads
Retrieving IP info... check
Initializing TPM certs ... check
establishing connection to master IP ... check
Upgrading Image. This process may take a few minutes. Please be patient... spinny wheel
the it will reboot and cycle through that again and again
I checked on the master and I do see my external IP coming in on port 4500 with a 'show datapath session table'
so I know connectivity is good. That and it worked fine until the promotion/demotion so nothing should have changed access wise.
The RAP5s MAC is in the RAP whitelist for both the master and the local controller.
If I look in the syslog I see
Jan 11 13:08:50 a6000-0.blah.EDU authmgr: <522038> <INFO> <a6000-0 x.x.x.18> username=00:0b:86:66:a0:79 MAC=00:00:00:00:00:00 IP=y.y.y.y Authentication result=Authentication Successful method=VPN server=Internal
Jan 11 13:08:50 a6000-0.blah.EDU authmgr: <522008> <NOTI> <a6000-0 x.x.x.18> User Authentication Successful: username=00:0b:86:66:a0:79 MAC=00:00:00:00:00:00 IP=10.10.10.14 role=ap-role VLAN=1 AP=N/A SSID=N/A AAA profile=default auth method=VPN auth server=N/A
If I let the RAP5 sit, it will iterate through all the IPs in my RAP-pool (10.10.10.10 -> 20) and on the 11th time hang and not reboot. Until then it will cycle like that.
Anyone seen a RAP cycle like this, or know what my next step should be. I feel like its probably something simple I've missed, but comparing configs between the two controllers I'm not seeing it.
01-11-2012 11:17 AM
If that RAP5 has 3.x in it's provisioning/backup partition (the one that loads when you factory reset it) then you can't connect it to a controller that's running 6.x. It kind of sounds like that's your case? If it is, you need to first provision that RAP5 to a controller running 5.x, then upgrade it's backup partition. Then you can provision it to a 6.x controller.
(5.x Controller)# apflash ap-name <ap name> backup-partition
01-11-2012 11:34 AM
Sadly I just got done upgrading all our controllers to 188.8.131.52 from 184.108.40.206, so we don't have a 5.x controller to use at the moment. I wasn't aware that there was an upgrade issue with the RAPs and 3.x.
01-11-2012 12:21 PM
I really hate to say this because I am just as guilty as the next person.
This issue was documented in the Release Notes. Here is a snip from the 220.127.116.11 Release Notes.
Upgrading With RAP-5s and RAP-5WNs
If you have completed the first upgrade hop to the latest ArubaOS 5.0.4.x version, and your WLAN includes
RAP-5/RAP-5WN, do not proceed until completing the following process. Once complete, proceed to step 21
on page 57.
It goes on to describe how to check the backup partition and the steps required to upgrade it before moving forward with an upgrade.
08-20-2012 08:57 AM
I am currently running into the same problem with a RAP-5. I don't have any controllers on 5.x so I cannot upgrade the backup partition. Did you find a way around this?
06-05-2013 02:08 PM
I'm guilty of this as well but was fortunate enough to have 2 M3 controllers available. I'm fixing one of my RAP-5WNs now by downgrading one of the controllers to 5.x (after breaking VRRP). The other provides wireless to a corporate motor coach and I'll fix that when it returns.
This doesn't affect RAP-2WGs, correct?
06-07-2013 10:49 AM
I've checked multiple RAP-2WGs and they all have version 18.104.22.168 as their Provisioning/Backup image. I did not update these. So far, only the RAP-5WNs have given me issues with the provisioning image after updating ArubaOS.
06-07-2013 10:54 AM
Aruba no longer ships RAPs with an image below 5.x anymore, meaning that you are much less likely to see those in the field.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base