topic Re: Unadopting because of new adoption request in ExtremeWireless (WiNG)

Unadopting because of new adoption request

Brama — Wed, 25 Nov 2020 00:01:46 GMT

Hello,

I'm having a weird issue in my wireless environment (VX9000 / AP7522).

At random I have AP7522 disconnecting issues, I found this in the “show mint mlcp history” log:

first it start with:
2020-11-24 10:02:07:Sending MLCP Offer to 1B.A8.2F.A8 (link_level=2, preferred=0, capacity=25563)

then:

2020-11-24 10:02:12:Sending MLCP Reply to (00.00.00.00,8704,0,x,x,x,x:24576/60-00-01-00-0A-1F)

then:

2020-11-24 10:02:18:Adopted B8-50-01-76-CE-CC (1B.76.CE.CC), cfgd notified
2020-11-24 10:02:17:Unadopted B8-50-01-76-CE-CC (1B.76.CE.CC), cfgd notified
2020-11-24 10:02:17:Unadopting B8-50-01-76-CE-CC (1B.76.CE.CC) because adopter changed to 00.00.00.00

and then:

2020-11-24 10:02:20:Unadopted B8-50-01-A8-42-28 (1B.A8.42.28), cfgd notified
2020-11-24 10:02:20:Unadopting B8-50-01-A8-42-28 (1B.A8.42.28) because of new adoption request

I have taken only one line per event, because the whole rf domain unadopts and adopts back so there is an event for every single AP.

Except for:

This happens only once between the sending MLCP reply's to all AP's and the unadopting events.

Can anyone explain what is happenig?

Thank you.

Re: Unadopting because of new adoption request

SamPirok — Wed, 25 Nov 2020 22:44:54 GMT

Hi Brama, do you have another controller, virtual controller or standby controller, on the network? You can check to see if the AP sees another controller with the command “show adoption history” without quotations.

Re: Unadopting because of new adoption request

Brama — Wed, 25 Nov 2020 23:02:02 GMT

Hi Sam Pirok, did not check that, but from what I see, it looks like a network issue:

ap7522-A84228>show adoption history
----------------------------------------------------------------------------------------------------
MAC TYPE EVENT TIME-STAMP REASON
----------------------------------------------------------------------------------------------------
00-50-56-99-50-FD VX9000 adopted 2020-11-24 17:05:38 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-24 17:05:26 Adopter 12.99.50.FD is no longer reachable
00-50-56-99-50-FD VX9000 adopted 2020-11-24 17:05:22 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-24 17:05:03 Adopter 12.99.50.FD is no longer reachable
00-50-56-99-50-FD VX9000 adopted 2020-11-24 10:07:02 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-24 10:06:47 Adopter 12.99.50.FD is no longer reachable
00-50-56-99-50-FD VX9000 adopted 2020-11-24 10:02:39 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-24 10:02:07 Adopter 12.99.50.FD is no longer reachable
00-50-56-99-50-FD VX9000 adopted 2020-11-23 12:05:22 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-23 12:05:06 Adopter 12.99.50.FD is no longer reachable
00-50-56-99-50-FD VX9000 adopted 2020-11-23 12:02:59 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-23 12:02:47 Adopter 12.99.50.FD is no longer reachable
00-50-56-99-50-FD VX9000 adopted 2020-11-23 12:02:32 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-23 12:02:16 Adopter 12.99.50.FD is no longer reachable
00-50-56-99-50-FD VX9000 adopted 2020-11-20 12:41:13 N.A.
00-50-56-99-50-FD VX9000 un-adopted 2020-11-20 12:41:02 Adopter 12.99.50.FD is no longer reachable
----------------------------------------------------------------------------------------------------

Re: Unadopting because of new adoption request

RobertZ — Mon, 30 Nov 2020 23:06:01 GMT

can you share the output of CLI command ‘ show mint lsp-db’

and ‘ show mint neighbors’

Re: Unadopting because of new adoption request

Valter_Veiga — Wed, 17 Feb 2021 03:38:51 GMT

Hi Brama,

Are you still with the issue ?

Are the AP’s in a different Vlan, or the same as the controller ?