Update Mesh AP130 (used by Hivemanager Classic) now in progress from XIQ

[NetAdmLWL]

Hi Community!

We are actually moving our (300+) AP130/AP150W from Hivemanager Classic to ExtremeCloud Pilot (on Premise)

Now I run in problems when I want to deploy the new Network-Policy on 1-3 APs which are in meshing mode. The first AP is cable bound, I do not want to update this first of config-trouble. So I want to start on the last AP in the mesh. My Problem is, I have no physical access to the devices, so I cannot plug them into an ethernet-port.

So the update must run while meshing.

Now the problem: I have changed the AP template to “Client Access” AND “Backhaul Mesh Link”. The APs running the old config from hivemanager. While pushing the new config, it seems that the AP mesh link goes down, so that a huge part of the config does not reach the AP. The AP then “hangs” and I think, it reboots, then comes up with the old config and starts meshing again, but there was no update done.

Firmware-Update was working fine, using now IQ Engine 10.0r10b build-254127 (from XIQ onboard)

How can I update Mesh-APs without putting them into ethernet again? If it was only one or two locations, this can be done, but we have running about 48 locations far away in the WAN; so going to these locations and fix the ethernet port is nearly not feasible…

Can anybody help?

Is there another or better way?

Is there a workaround?

Thanks in advance and

Regards from Muenster/Germany

Frank Cordes

[SamPirok]

Hi Frank,

Sorry for the long wait here. I’d recommend SSHing in to the remote AP in the Mesh connection (meaning the AP that is not physically connected to an ethernet cable) and running the following command to stop the AP rolling it’s configuration back right away: 

No cono config rollback enable

After that command is applied, you’ll want to update the remote AP first, and then the Portal AP (the one in the mesh connection that is connected to an ethernet cable). It’s important that the remote AP is updated first, and has completely finished the update before you try to update the Portal AP. If there are multiple remote APs, start with the one farthest away from the portal, then the second to farther away from the portal, etc working your way back until the Portal AP is the last to be updated. 

I’d also recommend checking your device template to make sure that ETH 0 is set to an Access port. Finally, you’ll want to make sure all APs in the Mesh set up together are using the same firmware versions for best results. Hope that helps!