Unadopted AP

[fabriciocostadn]

Hello everyone!

AP not into in controller vx9000

AP model: ap7532

Problem:  

Vx9000#show adoption log adopter

2024-01-03 21:31:15:Sending MLCP Offer to 75.03.18.C0 (link_level=2, preferred=0, capacity=25567)
2024-01-03 21:31:15:Adopted 74-67-F7-03-18-C0 (75.03.18.C0), cfgd notified
2024-01-03 21:31:10:Unadopted 74-67-F7-03-18-C0 (75.03.18.C0), cfgd notified
2024-01-03 21:31:10:Unadopting 74-67-F7-03-18-C0 (75.03.18.C0) because of new adoption request
2024-01-03 21:30:45:Sending MLCP Reply to (00.00.00.00,8704,0,192.168.28.92:24576/60-00-01-00-C0-A8)
2024-01-03 21:30:40:Sending MLCP Offer to 75.03.18.C0 (link_level=2, preferred=0, capacity=25567)
2024-01-03 21:30:39:Adopted 74-67-F7-03-18-C0 (75.03.18.C0), cfgd notified
2024-01-03 21:30:34:Unadopted 74-67-F7-03-18-C0 (75.03.18.C0), cfgd notified

Does anyone know how to solve it?

[Christoph_S · Accepted solution]

Hello @fabriciocostadn,

1 - What adoption method are you using (DHCP option 191, Controller host, DNS...)?

2 - Do you have a cluster in place?

3 - When you run the command #show mint known-adopters, what are the results?

4 - Are other APs adopted without issue in the same rf-domain?

5 - Is this a replacement AP and has it been reset before adoption?

6 - Is this a remote site?

7 - Is the VX in the broadcast domain as the APs and is MLCP vlan enabled on the APs?

8 - Is the AP on the same firmware version as the controller?

9 - Do you see the AP when you run the following commands on the controller:

#show adoption status

#show adoption pending

#show adoption offline

We'll need more information to be able to get to root cause. 

BR,

[ckelly · Accepted solution]

On the AP7532 that is having trouble adopting, run the commands:

show mint mlcp history

show mint known-adopters

show mint links

show mint neighbors

[Christoph_S]

In addition to what @ckelly mentioned, please add the following commands:

On AP

show adoption history

On controller:

Show adoption offline

Show adoption pending

Show adoption status | incl <AP mac or hostname>

You can also try plugging the AP into the port of another working AP to see if it'll adopt.

What firmware versions are the AP and controller running on?

BR,

[Christoph_S · Accepted solution]

Hello @fabriciocostadn,

1 - What adoption method are you using (DHCP option 191, Controller host, DNS...)?

2 - Do you have a cluster in place?

3 - When you run the command #show mint known-adopters, what are the results?

4 - Are other APs adopted without issue in the same rf-domain?

5 - Is this a replacement AP and has it been reset before adoption?

6 - Is this a remote site?

7 - Is the VX in the broadcast domain as the APs and is MLCP vlan enabled on the APs?

8 - Is the AP on the same firmware version as the controller?

9 - Do you see the AP when you run the following commands on the controller:

#show adoption status

#show adoption pending

#show adoption offline

We'll need more information to be able to get to root cause. 

BR,

[fabriciocostadn]

1 - What adoption method are you using (DHCP option 191, Controller host, DNS...)?

 - Controller

 controller host x.x.x.x pool 1 level 2
adoption-mode controller

2 - Do you have a cluster in place?

- No, the AP is in the Branch, and controller in the head office.

3 - When you run the command #show mint known-adopters, what are the results?

- Nothing. 

4 - Are other APs adopted without issue in the same rf-domain?

- Yes, There's outher AP in the same Branch adopted. 

5 - Is this a replacement AP and has it been reset before adoption?

-Yes

6 - Is this a remote site?

- Yes, it is.

7 - Is the VX in the broadcast domain as the APs and is MLCP vlan enabled on the APs?

Yes, the vx9000 controller responds to pings from the AP

because, it sends messages MLCP Reply and Offer for this AP, too