01-08-2013 10:39 AM
I have a problem after migration an A6000 in master mode, with nearly 300 APs mixing AP61 and AP125.
Migration consist in pass from 18.104.22.168 to 22.214.171.124. Upgrade was realize with an upgrade path to 126.96.36.199 to 188.8.131.52 to 184.108.40.206
After migration, i have 170 Aps up and 150 down. Ap up are a mix of AP61 and AP125, same for those are down...
All ap down retained old ip address of master controller... I try to clear Ap down in database, and poweroff /poweron Ap, but no result...
I have no idea... Please help :)
Thanks a lot.
Solved! Go to Solution.
01-08-2013 05:55 PM
I would go to one of those APS and console it to see whts the issue...
If APS are down and you cannot do anything... go to the AP 125 which is down console it and see if the values of the master ip address server ip address, ip and default gateway everything is correct....
Are those Campus APs?
How do they find the master? do they get DHCP and find it with DNS? or you statically assigned it?
If you statically assigned the values, you can always console the aruba 125 and can correct it via console. Now check one of those aps 125 through console... probably what happened to one of those happened to all the otheres
Product Manager - Aruba Networks
01-10-2013 01:24 AM
Hi and thanks for your answer.
I am connecting to the AP 125 throught serial port, and see, AP125 is still in 220.127.116.11...
Below log to the master controller :
Jan 10 10:21:52 sapd: <311013> <ERRS> |AP 00:1a:1e:c9:7e:firstname.lastname@example.org sapd| Image upgrade failed; details follow.
Jan 10 10:21:52 sapd: <311014> <ERRS> |AP 00:1a:1e:c9:7e:email@example.com sapd| ERROR: File size exceeded 5242880 bytes
Jan 10 10:21:52 sapd: <311014> <ERRS> |AP 00:1a:1e:c9:7e:c8@1xxxx..xxx.145 sapd| Local write failed: Success.
Jan 10 10:21:52 sapd: <311014> <ERRS> |AP 00:1a:1e:c9:7e:c8@1xxx..xxx.145 sapd| ncftpget mips64.ari: no space.
Jan 10 10:21:52 sapd: <311014> <ERRS> |AP 00:1a:1e:c9:7e:c8@1xxx...xxx.145 sapd| FTP Failed: 3. Trying TFTP.
Jan 10 10:21:52 sapd: <311014> <ERRS> |AP 00:1a:1e:c9:7e:c8@1xxx...xxx.145 sapd| transfer timed out
Jan 10 10:21:52 sapd: <311014> <ERRS> |AP 00:1a:1e:c9:7e:c8@1xxx...xxx.145 sapd| Flash Image upgrade failed: 255
Jan 10 10:21:53 sapd: <311002> <WARN> |AP 00:1a:1e:c9:7e:c8@1xxx..x.xxx.145 sapd| Rebooting: SAPD: Reboot after image upgrade
Jan 10 10:21:53 nanny: <303086> <ERRS> |AP 00:1a:1e:c9:7e:c8@1xxx..x.xxx145 nanny| Process Manager (nanny) shutting down - AP will reboot!
So i try to make a purgeenv, saveenv and reset, but no improvment ...
An idea ?
01-10-2013 05:59 AM
It would be nice if you could show the output of what you see on the console... I want to see if i can see an error or where is failing
You can try doing
This will delete the OS and it will come with the OS that originally came when it was shipped...
Product Manager - Aruba Networks
01-10-2013 11:58 AM
Thanks for reply, but it was a software version.
I have validate upgrade process with ARUBA, in order to be sure to pass A6000 in 18.104.22.168 to 22.214.171.124.
Aruba tell me i have to pass 126.96.36.199 to 188.8.131.52 and pass 184.108.40.206 to 220.127.116.11.
But in this migration i have about 300 Aps, and 100 Aps stay in down status ... They don't flash and stay in 18.104.22.168...
So to have Ap up, i have to downgrade my A6000, in 22.214.171.124, to have all my AP flash in 126.96.36.199, and once it was ok, upgrade A6000 in 188.8.131.52, to reflash my AP in 184.108.40.206.
So to recover Ap down i have to pass controller in 220.127.116.11, and my goes up...
Once in 18.104.22.168 upgrade in 22.214.171.124 and all works ...
Hope it help you in futur deployments :)