topic AP4620 adopted (not configured) on WM3400. in ExtremeWireless (WiNG)

AP4620 adopted (not configured) on WM3400.

Sean_Tutor — Tue, 30 Nov 2021 19:23:49 GMT

I know it's an older model however we still have these in use. We just purchased these AP4620s for use with the WM3400. The APs power up but have solid lights indicating that they're adopted but not configured. However the WM3400 doesn't see the devices and doesn't even show them as pending adoption or adopted.

Re: AP4620 adopted (not configured) on WM3400.

Douglas_Novell — Wed, 08 Dec 2021 21:08:49 GMT

Hello,

Use 'show adoption status' to verify if the APs are adopted. If not it will state if there is a 'version-mismatch' or 'error'. If in 'version-mismatch' state please upgrade the APs to match the controller firmware. If in 'error' state please check the AP profile from proper configuration.

Re: AP4620 adopted (not configured) on WM3400.

Christoph_S — Wed, 08 Dec 2021 21:32:47 GMT

Hello Sean,

What firmware version is the WM3400 on?
Any clue what firmware the AP4620s are running on? (may be on 4.x code while the WM is on 5.x code)
Is the AP4620 pulling an IP address, i.e are you able to ping it?
Do you have enough licenses on your controller?

Re: AP4620 adopted (not configured) on WM3400.

Sean_Tutor — Wed, 08 Dec 2021 21:58:08 GMT

I guess I can't reply directly to folks. So the APs aren't showing up any where in adoption. In fact the lights stay solid the whole time making me think that perhaps they're not getting past the boot phase. We're running 5.5.5.0-18R on the WM3400. Doesn't appear to be pulling an IP on and we've got enough licenses on the WM3400.

Re: AP4620 adopted (not configured) on WM3400.

Christoph_S — Wed, 08 Dec 2021 22:36:58 GMT

Per the LED status info, 2 solid lights (if in code 5.x) means booting up. So as you said, may be stuck in boot mode.

https://extremeportal.force.com/ExtrArticleDetail?an=000083876

It's tricky with these APs since they don't offer console access and we don't have any visibility into what settings, if any, had been previously configured.

Try show lldp neighbor or show cdp neighbor from the switch to see if anything comes up that will allow us to access the AP.

If AP is not accessible via the ge port and it's not seen by the controller and may be stuck in boot, looks like there is not much that can be done to recover it.

Rgds,

Christoph

Re: AP4620 adopted (not configured) on WM3400.

Sean_Tutor — Thu, 09 Dec 2021 21:22:22 GMT

So I've got the amber light blinking (no green light) on one of these and this info came up on show lldp neighbors.

Chassis ID: 00-04-96-88-88-F4
System Name: ap4600-8888F4
Platform: AP4620-US, Version 5.5.5.0-018R
Capabilities: WLAN Access Point Router
Enabled Capabilities: WLAN Access Point Router
Local Interface: ge3, Port ID (outgoing port): 00-04-96-88-88-F5
TTL: 175 sec
Management Addresses: 169.254.136.244

GUI doesn't show it as adopted or pending adoption, also noticing no management IP address like the others have.

All the other devices are stuck at boot and aren't showing anything, which is a shame because it means we essentially got scammed.

Re: AP4620 adopted (not configured) on WM3400.

Sean_Tutor — Thu, 09 Dec 2021 21:26:59 GMT

Device Licenses:
AP-LICENSE
String : DEFAULT-6AP-LICENSE
Value : 6
Borrowed : 0
Total : 6
Used : 3
ADVANCED-SECURITY
String : DEFAULT-ADV-SEC-LICENSE

Re: AP4620 adopted (not configured) on WM3400.

Christoph_S — Thu, 09 Dec 2021 23:05:47 GMT

try the following:

Configure your computer with a static IP in the 169.254.x.x/16 range and try to ping 169.254.136.244. If unable to try IP 169.254.136.x/24. If you are able to ping it, using putty, SSH into the AP. At the login prompt, if AP had been defaulted, you should be able to use the following credentials:
Login as: admin
Password: motorola
or whatever the default credentials were for the Brocade APs.

If unable to log in, try the following credentials:
Login as: reset
Password: OQTEa4rT

I hope this helps,

Chris