WING problems - connection VX and AP

Alexandr_P — Wed, 15 Jan 2020 18:19:55 GMT

Hello!

APs - 7632, VX9000. WiNG 5.9.7.0

APs had no possibility to adopt to VX.

vx9000#show mint neighbors
2 mint neighbors of 12.18.67.49:
(ap7632) at level 1, best adjacency vlan-1
(ap7632) at level 1, best adjacency vlan-1

vx9000#show adoption status
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------
Total number of devices displayed: 0

After configure on APs controller’s IP - APs adopted, but now I can’t see statistics from APs and can’t upgrade them.

vx9000>show adoption status
--------------------------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS
--------------------------------------------------------------------------------------------------------------------------------
ap7632-XXXXXX 5.9.2.5-001R version-mismatch No vx9000 0 days 02:03:35 0 days 02:18:24 10.10.222.4
ap7632-YYYYYY 5.9.2.5-001R version-mismatch No vx9000 0 days 18:56:19 0 days 19:41:31 10.10.222.2
---------------------------------------------------------------------------------------------------------------------------------
Total number of devices displayed: 2

Statistics:

Detail :Not Available
Message :Timed out waiting for remote device: xpath=wing-stats/device[mac='XX-XX-XX-XX-XX-XX']/system
ErrorPath :
Severity :error
Type :Application Error

Upgrade - failed.

APs in DC1(APs + X460 stack +X670 stack + FortiGate) 2 providers DC2 (Mellanox switches and Servers with HyperV and VX9000)

Any ideas how to debug this issue?

(MINT MTU decrease don’t help)

Also, what is address is pointed in #sh mint nei?

2 mint neighbors of 12.18.67.49

Thank you!

Re: WING problems - connection VX and AP

Tomasz — Sat, 18 Jan 2020 06:09:45 GMT

Hi Alexandr,

I’ll raise couple of general things, sorry if you are already familiar with these:

When you see ‘show adoption status’, the APs have ‘version-mismatch‘ info. What is the controller version? Mismatched version APs will not get any config from the controller even though being adopted.

Did you configure DHCP Option 191 or DNS-based discovery for the APs? If not, then you indeed have to deliver the controller’s IP to the APs manually.

Regarding the upgrade issue, if you have reduced the MINT MTU value 86 bytes below the MTU available through providers and it still doesn’t help, someone in an older thread recommended to call GTAC for further investigation (https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Collect-a-Tech-Support-file-from-WiNG-Wireless-Controllers-and-or-Access-Points ).

Numbers like 12.18.67.49 are MINT IDs, some identifier used by the APs in MINT protocol (which is based on IS-IS by the way). First byte is hardcoded, last three are derived from the device MAC address.

Hope that helps,

Tomasz

topic WING problems - connection VX and AP in ExtremeWireless (WiNG)

WING problems - connection VX and AP

Re: WING problems - connection VX and AP