WiNG v.7.5.1 not applying hostname changes for some RF Domain Access Points

[keknet1337]

Some access points within a RF Domain won’t update their hostnames unless I do so logging in through SSH remotely. It only happens on some APs I got. I didn’t set up the config and will document myself a bit on how to initially configure a RF Domain for clues, but meanwhile it could have happened to someone else already so I’m putting it up here in case anyone has or had the same issue.

[keknet1337]

Perfect! Thank you for your help. 

[Christopher_Fra]

From the VX CLI (Command Line Interface), enter the following:

enable [enter]

show adoption status [enter]

If using the UI via VX

Statistics > Rf-domain VX is in > Highlight VX > Adoption > Adopted Devices and look under “Status”

[keknet1337]

Thanks for the info, I just connected the dots a few minutes ago and found this post as well:

Mismatch between the controller and AP firmware versions | Extreme Networks Support Community

I’ll see about updating our firmware on applicable APs, thank you.

One question though: how could I see a log for the version mismatch as pointed in the document URL you linked? Should I enable logging at the VX9000 and then see the logs in the WiNG tool?

Could you please point me to a document on how to enable logging without breaking my VX9000? I fear that if done incorrectly I may saturate the device and become unmanageable without a reboot or something.

[Christopher_Fra · Accepted solution]

Appreciated and due to the AP/VX being on different firmware, this is expected. No configuration pushes from VX9 to adopted APs will occur until firmware is matching. 

The following is a Knowledgebase Article explaining:

https://extremeportal.force.com/ExtrArticleDetail?an=000085427&q=wing%20version%20mismatch