Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

howto upgrade firmware on new 325: the X-over way

This thread has been viewed 4 times
  • 1.  howto upgrade firmware on new 325: the X-over way

    Posted Oct 18, 2016 07:12 AM

    Hi all,

    No question, just something I like to share on how I succeeded in upgrading a new 325. I read all the articles on mixed 205 and 325 cluster. And the trouble on first getting the 325 on the correct firmware level before it showed up in an existing 205 Instant cluster.

    This is what I did:

    • X-over LAN cable between PC and 325

    • Connect console cable to 325

       

    • Have 325 new firmware ready on desktop of W7 PC
    • watch boot of 325 and notice the default IP address of 169.254.241.188 (at least in my case)
    • Put PC LAN IP to 169.254.241.10 (for example)
    • web browse to the 325 IP and login with admin/admin
    • from there, do the firmware upgrade procedure in the GUI

    During this, my 325 rebooted once, if I was not fast enough (say 3 minutes) in doing the browser connection. Why? I dont know. Probably some timer issue.

    Anyhow, after the upgrade I put the 325 online and it nicely showed up in the Instant cluster.

     

    besr regards

    Tjekker



  • 2.  RE: howto upgrade firmware on new 325: the X-over way

    EMPLOYEE
    Posted Oct 18, 2016 11:38 PM

    That's one way of doing it. :-) Easier would be to boot up the IAP-325 on a separate VLAN so it does not try to join the IAP205 cluster. The AP would advertise "instant" SSID, which you can connect to. Then browse to "instant.arubanetworks.com" when connected to the "instant" SSID and upgrade as per your note.

     

    Good to know the option you outlined as well.

     

    -Mike



  • 3.  RE: howto upgrade firmware on new 325: the X-over way

    Posted Oct 19, 2016 03:22 AM

    Thx, Mike. Correct.

    But I didnt have quick access to a separate VLAN and DHCP.

    So, I tried this solution. And, besides, it was fun mucking around again with a serial session :-)