Controllerless Networks

I have IAP network of two IAP225's which is work fine. I cannot get either of my  IAP-205H to join the APs avilble as shown in the GUI.  I am running poe and plugging into the E0 port on the back of the iap 205.  Yes I am in the same L2 network. from the VC CLI I see the AP dynamically joins the AP-allow list but is not part of the IAP network. show aps only show my two existing 225's

Any idea's

Upgrade the AP205 code to match the IAP-225 code.

 

Typically the existing cluster will send the code to a new AP if it is the same model.  If it is a different model that wants to join, it will redirect it to the Aruba cloud to download the code.  It is possible that your firewall is blocking the code.  I would boot the IAP-205 on a different network, connect to the "instant" SSID and upgrade the code to match that of the IAP-225.  When that is done, boot it up on the same VLAN as the IP-225.

Thank-you Joseph, you nailed it !!  :)

Okay new problem..

-My existing network cluster consists of 2x  IAP-225-RW has firmware 6.4.2.6-4.1.1.11_52666

-My new IAP-205H-RW, that I want to join the cluster, has firmware 6.4.3.0-4.2.0.0_49453

 

Using "Check for new version" from cloud, both the existing network and the new 205H, --No new version availible-- 

 

So how do I get both these IAP 225 and 205H on the same firmware so they can be on the same IAP cluster ??

I went support.arubanetworks.com and downloaded ArubaInstant_Taurus_6.4.2.6-4.1.1.11_52666 and tried a manual update to the 205H so that it would have the same version as the 225's. However the 205H complained it did not like the the firmware file. It would not accept it..

 

Suggestions ??

 

 

What was the exact error?  That should work...

Upgrade Failed

Invalid Image File

 

 

see attached

Can you please check the md5 sum on that download:

 

md5 ArubaInstant_Taurus_6.4.2.6-4.1.1.11_52666 
MD5 (ArubaInstant_Taurus_6.4.2.6-4.1.1.11_52666) = 918454e223767ba0c8e8f4ef884305b9

 

 Also, make sure you didn't change the filename.  if you downloaded it more than once, it might put a (1) in the filename...

918454e223767ba0c8e8f4ef884305b9

 

I downloaded twice and saved in diferrent directories.  I did not rename it...  Same MD5 for both files

hmm...  Are your IAP-225s in production?  Would you be against upgrading those to match the IAP 205H?  I can send you code for both...

 

no problem send me the code

Great the new code applied to both 225's and the 205H resolved the issue..  Life is Good. Thanks for your excellent Support !!!

Hi,

 

I have exactly the same problem in my network.

The 205H runs on 6.4.3.0-4.2.0.0_49453 and the 225 on 6.4.2.6-4.1.1.11_52666

The 205H shows the same error massage when I try to upgrade the image via WebGUI.

 

Could you please provide me the code that works?

 

Thanks!

Please do the following

Power down the 225s

Power up the 205Hs in the same VLAN.

Configure the new IAP205H to match the configuration of the previous 225s.

Power on the 225s.

225s should upgrade themselves to 4.2 to match the 205H, as long as they have Internet access to device.arubanetworks.com

Yan Liu
Director of Product Management
Aruba Instant
US: +1 650 996 3520
China: +86 136 212 16844

Sent from my iPhone

Sir i am also facing the same issue. Can you please share me the code and procedure to add to cluster.

 

Email ID:- rajan.kumar@targustech.com and prakash.t@targustech.com

What problem are you having specifically?  Make sure both APs have the same version of code from here:  http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/EntryId/21998/Default.aspx

 

Hi Guys,

 

I have the same problem as i think the other guys have, but unlike them no solution. 

It has been a interesting  process of understanding how the management clustering is working on IAP has been an interesting proccess. Almost seems to work like the Cisco Small Business AP clustering units.

 

 

I tried to upgrade my existing model 205...Dont poo poo me,  i know these models are old, but dont want to throw something out that still works really well. 

You can see from the GUI capture below the resident firmware and the version i wanted to upgrade to.

 

and i get the following

 

 

Even tried doing it via a CLI , but no luck.

 

 

But my second model 205 successfully upgraded when i tried to upgrade to the newer firmware.

This demonstrates that the firmware downloaded was good and that  i have a issue with the first model 205 that wont upgrade..

 

 

So I thought i would try the following and  try upgrading in a  single LAN domain  cluster.

 

step 1. Turn on first the AP that successfully upgraded with the newer firmware.and plug it into a LAN segment.

 

My rationale was to allow this AP to upgrade the second 205 in the cluster automatically.

 

step 2.  Attach the errant Model 205 with the older firmware  to see if it will upgrade its firmware.

 

result:

It is observed that the second 205 is  rebooting every few minutes, so i guess it is trying to upgrade to the newer code, but it's not coming online

 

I am getting an alert on my Instant GUI which follows;

 

 

My question Is,  any suggestions  to get this errant 205 to upgrade to the newer firmware ?

 

regards Dave