Firmware Cluster F - XIQ "Classic" Versus EP1

[DeVoID]

Ok Extreme, what the heck are you doing with terribly released, buggy firmware?

This started about 8-12 months ago, where you would release firmware - AP650 - only for the update to fail and either leave "device update failed" message next to the AP, or that message and an unreachable, un-ping-able AP and the only solution (only resolved when you released  .a version of it) is to unplug it at the AP or switch level, neither of which is easy or desired!

And it appears to get WORSE!!  In XIQ I did two AP650 AP's, ones I knew I could get to if needed (with a ladder) and sure enough one failed and went offline (cant ping, etc.) and the other EXACT MODEL with the same uptime, same Policy, etc, updated without issue.  The firmware is 10.8.6.0 BTW.

Now this is where I have to shake my head and wonder what the heck Extreme is thinking.

As I put, in XIQ Classic the firmware version is 10.8.6.0, and when I go into EP1, the version is 10.8.6.1 for the SAME AP MODEL!  Not only that, but of the three AP's I pushed new firmware, to it shows as failed in EP1, and showed as successful in XIQ Classic AT THE SAME TIME!!!!!  WTH.. see my appropriately named attachments to this post.  

I mean REALLY....  if we are going to be transitioned to XIQ New, or EP1 by the end of this year then you at Extreme need to figure your **** out!  WHY TWO versions of firmware depending on what Interface/Platform you happen to use... Because of our licenses, we have access to Classic and EP1, but again, I should not see TWO versions of the same firmware for the SAME AP right?  That is not "a thing" in IT, and never has been.

I would LOVE to hear your answer Extreme.

I do apologize for coming off pissy, but being pushed and shoved into the new interface, and see this, has me standing at the edge of an anger cliff (metaphorical).

DeVoiD

 

 

[DeVoID]

My Switches are PoE+ but remember if im not quick enough to SSH into the switch and run a "sh mac-address" command against the AP's MAC address, I have no idea which port its plugged into.  Ive been able to disable the port entirely via the switch interface, but only if the switches  tables havent cleared, because if they have ill have no way of knowing which port the AP is in.

Some of my switches have 8-10 AP's plugged into them.

But appreciate your response.

DeVoiD

[wwillingham]

You can get the port number on the switch from XIQ. In XIQ, you can add the columns Eth0 LLDP Port # and Eth0 LLDP Sys-Name which will give you the switch port # and switch name, respectively, that the AP is connected to. I can provide screenshots of any of this if that would help. Unfortunately, EP1 isn't even close to having all the features of XIQ, so you'll have to do this in XIQ (which I still use more than EP1).

[DeVoID]

@wwillingham Thank you, appreciated.  Yeah, EP1, thats a whole other story.  I got LLDP enabled on my AP's, found the column in XIQ and w00t... fantastic.  I appreciate you and @daniel1 .  I take it, that EP1 doe not have this as an option... why am I not that surprised.  :). 

EDIT: Nope, no column for LLDP in EP1... sigh....

DeVoiD 

[daniel1]

@DeVoID you don't have to use MACs, just enable LLDP on your switches and APs.
So you can check the XIQ interface (LLDP columns must be added manually) and also your switch CLI to check which AP is on which port, here an example from us:

Advantage XIQ over switch cli: You see the information also when the AP is down (you may need to select a time range where the AP was up).

[DeVoID]

Thanks @daniel1 ooooooohhh... Pretty..... Ill make that happen - might not be today -.  I didnt see that as a column in XIQ, so I didnt even think about it.  Thats fantastic. You sir, are a star!  Got that on my "To Do" list for some point this week.  That is soooo very helpful.

Thanks mate, DeVoiD