Extreme Networks

systemscsn · ‎08-20-2021

This started way before summer, and I thought it was fixed.

I made a minor change to the power on wifi1 interface (but basically any change i make), select the device, click on Update Device. Leave the default Update Network Policy and Configuration » Delta Configuration Update checked. I see the progress bar area show Queued for a few seconds, and then Device Update Failed is displayed next to the AP.

Hovering my pointer on the Device Failed to Update, i see this “Could not generate CLI configuration. Execute Method failed, with class”…………………….

Here are all the steps I tried, all of which failed:

I rebooted the AP, once it came back up, i tried a Delta Configuration Update. It failed.

I tried a Complete Configuration Update on the AP. It failed.

Rebooted the AP again, once it came back up I tried a Complete Configuration Update. It failed.

Went into the Aruba 2920 switch, disabled the port that the AP is plugged into (its like unplugging the AP), waited 10 minutes and then re-enabled the port. Once the AP came back up I tried a Delta Configuration Update. It failed.

Went back into the Aruba 2920 switch, disabled the same port again, waited 10 minutes and then re-enabled the port. Once the AP came back up I tried a Complete Configuration Update. It failed.

This is insane. This issue is going on with any of my 160 AP’s, doesn't matter what change I've made to the AP, whether its changing the channel its on, or the power on one of the interfaces. I remember when this first reared its ugly head, we just had the banner show up at the top of the web interface, stating it had been upgraded (IQ Engine?). We have not changed our network infrastructure in any way, so I'm absolutely positive its nothing we have done.

I need to make small changes to most the AP’s on campus. I need to fine tune all of our AP’s because of Cross Channel Interference, and so need to make changes with power and channels on the AP’s. This issue is holding me back.

How can this be resolved? We have 160 AP’s most of them are attached to the ceilings, so whatever the fix, it better not involve grabbing a paperclip, ladder and interrupting classes.

Whats going on? this is an AP650(AH), and all I did this time, was change the power from Auto to 5db.

I didnt realize my issue was still going on. But it never happened until an ExtremeIQ update (i remember seeing a banner ages ago, and thats when this started). The AP is running 10.0.r5.

Any help to get this resolved that does require a paperclip and ladder is appreciated.

Thanks,

J.

systemscsn · ‎09-27-2021

UPDATE and Possible Solution.

Let me start by saying the “fix” I was told to do, was to basically set the AP back to factory. After that, of course, id have to go back into it and give it a name, its original IP (no im not doing reservations), apply its network policy, and do a complete update. For 140+ AP’s that is not a very good fix, and quite honestly if other AP’s on the same firmware, plus the same model of AP were not failing, then of course this would work.

The reason I was given for the error, and something i’m very… VERY… upset about, was that when the backend was updated - im thinking multiple times - from Hive to ExtremeIQ, it messed something up on our end because of the version of firmware we are running. While i do believe it was something done on the backend (we had not made any changes on anything, network, AP, server related on our end) that for reasons i dont know, messed up most of our AP’s so they wouldn't do any kind of update, i dont think im convinced it was our firmware version. Because if that were true then all of our AP’s on that version would fail, and they are not. However im mad because if they went into updating the backend knowing it could mess up a customers AP’s, then an email to their customers telling them to upgrade to whatever version would have been appropriate, and i know I never received an email of a possible issue with their backend messing my AP’s up! To me, there was a basic lack of any kind of Quality Assurance when the backend was updated/migrated from Hive to XIQ and for that someone should take a spanking.

While they have escalated my support ticket, i have found a workaround. For any AP thats failing to Update, and has those errors about Bonjour. You MUST go into the AP, click on Configure and then select Bonjour Gateway Settings. Make sure you have the default value of 250 in the Priority Field (some of mine were either blank or had 10 as the value), Check the box for “Override the default realm name”, then Save the Bonjour Settings, Click on Update, Delta and then Update.

That seems to fix the issue. Of course, you can never uncheck that box, or the error will come back (and it doesn't matter what version of firmware running).

basically its getting that realm name from your Network 360 Plan, if you have created one, and placed the AP on its map. You wont see the update failed message if you have a value in Priority and dont have the AP within the Network 360 Plan.

This whole thing has been a pain, and will continue to be a pain until ive gone through every AP we have and make that change.

Once I've gone though that nightmare, i plan on upgrading the firmware to the latest version, even though i can only update them after hours - which is going to take an age to do -. To think this all came about from wanting to reduce the Transmission Power. Speaking of which, i did that on an AP that I made the above change to, and while it took the update, wifi0 is still showing auto instead of 5db, which i set it to. So, who knows, maybe checking the box gets rid of the error message, but doesn't update… really….. personally i think it just takes an age for the XIQ interface to reflect the changes on the AP, so i’m leaving it alone, and carrying on clicking!

Hope this helps the next poor bugger that may get this issue.

Ill post again if the person who got my escalated support ticket gets back to me with a better, less manual way to fix this problem.

Best,

Jason.

View solution in original post

Ash_Finch · ‎08-24-2021

Quite possible that something was broken in an update somehow. Would make sense anyway if it previously worked and you haven’t made any changes to bonjour since.
Yeah that method would make sense in proving it’s something in that policy.

As long as you don’t push a delta/complete to the AP, any changes in XIQ are just shown in XIQ. It won’t change the AP in any way. So yeah that’s correct that the test SSID will only show once the config update is pushed to the test AP.

systemscsn · ‎08-24-2021

Hi Ash,

yeah, i think thats whats tripping it up. its just crazy that nothing has changed on our end. Ive been scratching my head, and i know ive done delta config pushes without any issues, and I want to say this didnt start happening until around 3 banners ago. By banners, i mean the one that shows up at the top of the interface after you login, and says there has been an update (im guessing on the backend stuff, such as features, etc.).

So, im wondering if something got broken on the back end of things. We literally havent changed anything infrastructure-wise.

Thats a really good point, just create the policy with almost anything in it, without bonjour, push and see. and how about this:

See if it fails or not (im with you, i don think it will fail) I change the AP putting it back in the original policy (which has bonjour) and then try pushing the config and see if it takes it or not.

Thoughts?

OH, question. If i create the new network policy, go through all the settings that I have to. If i click on save instead of deploy (ill have to do this first thing tomorrow morning before kids show up), it just saves it and the temp SSID wont show up? Im a little fragged with all the things ive had to to do today, a bit punchy, hence probably a dumb question.

To elaborate, the test SSID I just created inside the test network policy will only show up, once i go into the test AP, change its policy to my test one, and push the config update, right?

🙂

Ash_Finch · ‎08-24-2021

To be honest I guess the main thing is the bonjour piece, so you could just literally create a new network policy > add any SSID that’s WPA2 or something > push the update out. Just no bonjour.
I don’t think that would fail, but we’ll see!
Then add the bonjour and try and update again. I suspect it would fail at this point given what’s been said so far.

And yes, just go to the AP in that section change the policy or alternatively can be done via manage > tick AP > actions > assign network policy, select the new one and try to push it out.

systemscsn · ‎08-24-2021

Hi Ash,

Wish there was a way to duplicate a network policy, as doing that and just editing it so that people dont accidently attach to the AP that you apply the new policy to, would be great. thats my worry. I create the policy, put that spare AP into it, and people attach to that AP. Then again, i can give it a different SSID and WPA2 on it, they wont be able to join/connect to it…

Now of course, its about finding time to do that.

This whole deal has been passed along to our Tech Rep with Extreme, and the link to this page as well. So we will see. But i still plan on updating this frequently, as i dig a bit more into this. Being at my desk about 50% of the day, and the other 50% out and about taking care of work orders, I can try things in the interface and see if that resolves the issue. First thing, would be for me to plug in that spare, make a change (same change - disable Auto power on wifi1, setting it to 5db), and then applying the delta and see if that one fail (it will fail… i was being optimistic). I have that spare in storage here. Next will be the policy. I know that spare is already onboarded, so ill have to go into it and set it to use the other policy that ive got to create. never done that before. But i believe all I have to do, is go into the AP, select Configure » Device Configuration, and select the dropdown, and select the new policy i just created. Sound right?

Thanks much, really appreciated,

J.

Ash_Finch · ‎08-24-2021

Yeah using a spare AP as a test would also be worth a go as you’ve mentioned, and may make it easier to factory reset also! It may not get you much further, but at least then support would be able to jump straight into the bonjour and work out what’s going on with that and gives them an AP to try stuff to!

Extreme Networks

Delta and Complete config update fails

Delta and Complete config update fails