Header Only - DO NOT REMOVE - Extreme Networks

WING MESHPOINT NON-ROOT AP not connecting after ROOT AP reboot


WING MESHPOINT

After rebooting the ROOT AP the NON-ROOT can't connect, and I have wait a lot of hours ...

In the ROOT AP after the rebbot I see:

ROOT#sh wireless meshpoint statistics detail
==========================================================================================
meshpoint MESH01, meshid MESH01
Note: TX = MP->MP, RX = MP->MP
------------------------------------------------------------------------------------------
Data bytes : ( TX + RX = Total ), 0 + 0 = 0 bytes
throughput : ( TX + RX = Total ), 0 kbps + 0 kbps = 0 kbps
packets : ( TX + RX = Total ), 0 + 14.581 K = 14.581 K pkts
pkts/sec : ( TX + RX = Total ), 0 + 0 = 0 pps
MU-MIMO Data bytes : ( TX Total ), unknown bytes
throughput : ( TX Total ), unknownbps
packets : ( TX Total ), unknown pkts
pkts/sec : ( TX Total ), None pps
SU-MIMO Data bytes : ( TX Total ), unknown bytes
throughput : ( TX Total ), unknownbps
packets : ( TX Total ), unknown pkts
pkts/sec : ( TX Total ), None pps
BCMC Packets : ( TX + RX = Total ), 0 + 0 = 0 pkts
Management Packets : ( TX + RX = Total ), 0 + 14.581 K = 14.581 K pkts
Packets Discarded : 0 - Tx Dropped, 0 - Rx Errors
Indicators : T = 0 @ Max user rate of 150 Mbps, RF-Quality Index = 24
Distribution : 1 Neighbors, 1 radios
------------------------------------------------------------------------------------------

After rebooting the NON-ROOT AP , it Connects

ROOT#sh wireless meshpoint statistics detail
==========================================================================================
meshpoint MESH01, meshid MESH01
Note: TX = MP->MP, RX = MP->MP
------------------------------------------------------------------------------------------
Data bytes : ( TX + RX = Total ), 162.217 KB + 123.833 KB = 286.050 KB bytes
throughput : ( TX + RX = Total ), 1 kbps + 1 kbps = 2 kbps
packets : ( TX + RX = Total ), 1.079 K + 24.033 K = 25.112 K pkts
pkts/sec : ( TX + RX = Total ), 1 + 1 = 2 pps
MU-MIMO Data bytes : ( TX Total ), unknown bytes
throughput : ( TX Total ), unknownbps
packets : ( TX Total ), unknown pkts
pkts/sec : ( TX Total ), None pps
SU-MIMO Data bytes : ( TX Total ), unknown bytes
throughput : ( TX Total ), unknownbps
packets : ( TX Total ), unknown pkts
pkts/sec : ( TX Total ), None pps
BCMC Packets : ( TX + RX = Total ), 0 + 0 = 0 pkts
Management Packets : ( TX + RX = Total ), 8 + 23.016 K = 23.024 K pkts
Packets Discarded : 0 - Tx Dropped, 0 - Rx Errors
Indicators : T = 0 @ Max user rate of 150 Mbps, RF-Quality Index = 24
Distribution : 1 Neighbors, 1 radios
------------------------------------------------------------------------------------------

Is there any setting to enable ?

8 replies

Userlevel 4
Hello Valter,
What model of access points are deployed and what version of firmware are the access points running?
Model AP7662 version 5.9.2.4-004R, but was happening in previous version 5.9.2.3 and 5.9.2.2
It only happens when, the MeshPoint is established, and you only reboot the Root AP.
Userlevel 4
How are the MCX radio channels setup? Have you statically assigned a channel for this connection or did you set the radios to ACS? If yes, then the list of channels that the radio will attempt to use is defined in the AP's RF-Domain under the "Smart Scan" setup.

Wondering if there's an issue here with the channels being used.
5GHz-WLAN Channel 100 - no smart scan
Userlevel 4
Hello Valter,
I am seeing the same thing in the lab on any v5.9.2 release. I am currently working with engineering on this issue and data collection has been provided. I see that you created support case 01761006, which our GTAC EMEA Support Team would usually own. I am in GTAC US and my hours are 8am - 4:30pm (PST). I can yank the case and work with you on this or we can have GTAC EMEA run with it when they arrive back into the office. Right now, we don't have resolution on this issue and the only way to recover is to power cycle the non-root AP or if you can gain access via console, you can perform a shut/no shut on radio 2.
Hello Christopher, please "yank" the case. This is critical manufator 24/7 production line.
This is a remote AP, the local possibility is power cycle.
I have another Wing case open … probably you are the right person.
Userlevel 4
Hello Valter,
I will yank/manage support case 01761006. I will download the data that is attached and reach out to engineering. I will provide status via the support case and no longer use this forum moving forward. Thanks.

Reply