Wireless Access

Reply
Occasional Contributor II
Posts: 24
Registered: ‎04-03-2007

Beware Ortronics users and 6.3.1.2 Upgrade

We were using 6.3.1.1 just fine with our Ortronics OR-61 (AP-61) wireless APs just fine. This morning I upgraded to 6.3.1.2 and the OR-61 is no longer supported or working. Just a warning if anyone else out there still has some Ortronics OR-61 APs in service do NOT upgrade to 6.3.1.2.

Super Contributor I
Posts: 300
Registered: ‎12-01-2010

Re: Beware Ortronics users and 6.3.1.2 Upgrade

AP61 should be supported according to the release notesCapture.JPG

Normal Guy
Guru Elite
Posts: 21,279
Registered: ‎03-29-2007

Re: Beware Ortronics users and 6.3.1.2 Upgrade

The end of sale/end of life notice here:  http://www.arubanetworks.com/pdf/support/EOL_Ortronics_AP.pdf unfortunately does not specify the OR-61 part, but it was end of lifed, along with the licenses in the document that are required to support the OR-61 July 2010.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 24
Registered: ‎04-03-2007

Re: Beware Ortronics users and 6.3.1.2 Upgrade

Yes that EOS notice does NOT show the correct part numbers hence the problems. 

New Contributor
Posts: 2
Registered: ‎03-14-2014

Re: Beware Ortronics users and 6.3.1.2 Upgrade

How did you resolve this issue? We upgraded, and the or-ap-61's will not check in even after reverting the controllers back to the working code.

 

Now I cannot get them back up at all.

 

Thanks!

Occasional Contributor II
Posts: 24
Registered: ‎04-03-2007

Re: Beware Ortronics users and 6.3.1.2 Upgrade

[ Edited ]

We replaced all the failed APs with new ones we had on hand for a different project. 

 

I was able to take one of the OR-AP-61 and via local serial console commands boot the Old 6.3.1.1 code and then it would revert back to a working AP. You will have to interrupt the AP boot process then purge the Environment variables on the AP. Then you can add the environment variables back to force the load of the 6.3.1.1 code from the tftp on the controller. It was a painful process but as long as the controller had 6.3.1.1 running the AP would roll back. Then you had to re-provision the AP as the AP had lost all the provisioning parameters. 

New Contributor
Posts: 2
Registered: ‎03-14-2014

Re: Beware Ortronics users and 6.3.1.2 Upgrade

Thanks for the reply! We used soe to get into the connection on the AP's however even after purging, the OS image remained on the same 6.3.1.2 code.

 

If anyone else has this issue, it was resolved by doing the following:

 

 Interupt the boot, make sure the controller running working code is listed as the serverip by running

printenv

If it is not you can set it with

setenv serveripx.x.x.x

*where x.x.x.x is the ip address of the controller

saveenv

 

After it is set run

 

 tftpboot

 

The problem was that after doing this if the AP's rebooted again, they would revert back to the 6.3.1.2 code. This was fixed by running tftpboot again, then running the following from ssh on the controller:

 

flashap  ip-addr x.x.x.x

where x.x.x.x is the the IP address of the ap.

 

The good thing about this was that I did not have to purge the AP's so I did not have to reprovision.

 

Hope this saves someone some time in the future.

 

 

Search Airheads
Showing results for 
Search instead for 
Did you mean: