02-06-2012 09:50 PM
I am having HA master and local controller, I would like to upgrade my controller from 22.214.171.124 to 126.96.36.199, I have two 3400 controller on HA mode and 1 650 local controller. so what should be the process I need to follow...
Note:- 1, I am not looking for take backup etc.. which version to which version, the steps.. by steps OS version and which is the best version for RAP and AP devices...
I have 145 RAP device connected with MPLS and LMS over internet, also some RAPs on pure internet connectivity.
Also I wanted to deploy AP 135 after the upgrade..
02-07-2012 01:41 AM
I had to perform a simmilar task once and what I did was:
- Break HA/Master-local bindings
- Free one of the controllers (I'd start with the 650) of all its APs
- Upgrade OS of that controller
- Move APs to that controller - Careful, this reboots the APs, you'll need maintenance window -
- Repeat procedure with the other 2 controllers
- Once you've all controllers and APs upgraded reconfigure HA
- When you have that done, reconfigure master-local binding
I did things in this way 'cause I needed my maintenance windows to be as short as possible. If that's not your case, you may want to rethink your strategy.
ACMP, ACCP, ACDX#100
If I answerd your question, please click on "Accept as Solution".
If you find this post useful, give me kudos for it ;)
02-07-2012 07:08 PM
Thanks a lot for the reply..
I had performed twice this activity and I was not able to succeed.
what I had done. I had uploaded the image on all three controllers (MASTER, and local) and rebooted every one together, and all the RAP device also got updated with latest Firmware, but after upgrading to 188.8.131.52 or 184.108.40.206, the RAP devices are getting boot strap issue ( radio turn off and turn on ), which is causing a packet drop issue for the clients or disconnecting the clients from the controller. As per the Tech team, there is a heart beat issue with the RAP and the controller
so finally I had to roll back to 220.127.116.11.
Steps I had followed >> 18.104.22.168>> 22.214.171.124>>> 126.96.36.199 or 188.8.131.52
02-13-2012 08:24 AM
Did you notice page 57 of the 184.108.40.206 release notes? When your RAP's are RAP5, then you first need to flash the backup firmware of the RAP5 from the latest 5.0.4.x release; otherwise the RAP5's will not reconnect after the upgrade.
You did not tell the RAP type, but this may be the issue when they are RAP5's.
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.
1. Check the provisioning image version on your RAP-5/RAP-5WN Access Points by executing the
show ap image version
2. If the Flash (Provisioning/Backup) Image Version String shows the letters “rn” for example as 220.127.116.11-
rn-3.0, note down those AP names and IP addresses.
3. For each of the RAP-5/RAP-5WN noted in the step-ii, upgrade the provisioning image on the backup flash
partition by executing the following command:
apflash ap-name <Name_of_RAP> backup-partition
The RAP-5/RAP-5WN will reboot to complete the provisioning image upgrade.
4. When all the RAP-5/RAP-5WN with a 3.3.2.x-based RN provisioning image have successfully upgraded,
verify that the provisioning image by executing the following command:
show ap image version
The Flash (Provisioning/Backup) Image Version String should now show for example 18.104.22.168 and not
contain the letters “rn”.
5. If you omit the above process or fail to complete the Flash (Provisioning/Backup) Image upgrade to
5.0.4.x and the RAP-5/RAP-5WN was reset to factory defaults, the RAP will not be able to connect to the
controller running 6.1.2.x and upgrade its production software image.
If you have urgent issues, please contact your Aruba partner or Aruba TAC.
02-23-2012 07:17 PM
I forgot to say RAP Model, it is RAP 5WN, and the controller is 3400 on HA mode. and presently I devices are having a flash image as 22.214.171.124, and presently it is with 126.96.36.199, and when I am upgrading to 188.8.131.52, it is coming up with same image 184.108.40.206,but it is boot straping. (radio is getting on and off) so the users get connected and disconnected very frequently.
Access Points Image Version
AP Running Image Version String Flash (Production) Image Version String Flash (Provisioning/Backup) Image Version String Matches Num Matches Num Mismatches Bad Checksums Bad Provisioning Checksums Image Load Status
220.127.116.11 18.104.22.168(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 22.214.171.124(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 126.96.36.199(p4build@cyprus)#27734 Tue Apr 5 13:02:25 PDT 2011 Yes 1 0 0 0 Done
188.8.131.52 184.108.40.206(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 220.127.116.11(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 18.104.22.168(p4build@cyprus)#27734 Tue Apr 5 13:02:25 PDT 2011 Yes 3 0 0 0 Done
22.214.171.124 126.96.36.199(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 188.8.131.52(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 184.108.40.206(p4build@cyprus)#27734 Tue Apr 5 13:02:25 PDT 2011 Yes 68 0 0 0 Done
220.127.116.11 18.104.22.168(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 22.214.171.124(p4build@corsica)#31056 Wed Nov 9 14:41:32 PST 2011 126.96.36.199(p4build@cyprus)#27734 Tue Apr 5 13:02:25 PDT 2011 Yes 4 0 0 0 Done