topic Re: AP7522 RFS4010 in ExtremeWireless (WiNG)

AP7522 RFS4010

Andrey — Mon, 15 Mar 2021 19:18:29 GMT

The AP7522 point has a link to the RFS4010 controller over the mint protocol, but the point does not receive settings from the controller.The point and the controller are in the same network. The point was connected to three other controllers and the rf-domain for training. Now I can't return it to the work shop. What is the reason for the failure to get settings from the controller?

Re: AP7522 RFS4010

Christoph_S — Mon, 15 Mar 2021 19:56:50 GMT

Hello Andrey,

Is the AP adopting but not pulling the config or is it not adopting at all?

If this AP has been connected to 3 controllers and used for training, I would recommend that you factory reset it prior to any attempt at adoption.

Second thing would be to check the firmware version. Both the controller and AP should be on the same firmware version.(on controller: #show adoption status)

Thank you

Re: AP7522 RFS4010

Andrey — Mon, 15 Mar 2021 20:43:30 GMT

The controller and the dot are on the same firmware. I reset the point repeatedly. When you enter the "shadow history" command, the connection records to the controllers are visible, even after resetting to default. After resetting, I go in with the default password, change the password. I execute requests: sh mint link shows the id of the mint controller, mint ping id controller-goes. sh ip dhcp-vendor-displays the address of the controller, sh run-all default settings. I write on the point controller host and the region - does not help. Stubbornly does not get the settings. It is not visible on the controller. Ping passes both ip and mind in both directions.

Re: AP7522 RFS4010

Andrey — Mon, 15 Mar 2021 20:48:55 GMT

#show adoption status - no point in the list

Re: AP7522 RFS4010

ckelly — Mon, 15 Mar 2021 21:25:58 GMT

Andrey,

Do you have an auto-provisioning policy created with a rule for the AP...and the auto-provisioning policy applied to the RFS4010?

run:

show running-config auto-provisioning-policy <insert auto-provisioning policy name>

Also run:

show adoption pending

Re: AP7522 RFS4010

Christoph_S — Mon, 15 Mar 2021 22:58:45 GMT

In addition to above, do you have enough licenses? #show lic

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 11:46:39 GMT

EFKO-RFS-1>show running-config auto-provisioning-policy lan105
auto-provisioning-policy lan105
evaluate-always
adopt ap7522 precedence 1 profile efko-7522 rf-domain WMS-EFKO-SiM ip 10.2.78.1 10.2.78.4
adopt ap7632 precedence 2 profile efko-AP7632 rf-domain WMS-Zip-TMC ip 10.2.96. 0/22
adopt ap7522 precedence 3 profile yogurt_7522 rf-domain WMS-EFKO-SiM ip 10.2.78 .6 10.2.78.7
-----------------------------

EFKO-RFS-1>EFKO-RFS-1>show adoption pending
-----------------------------------------------------------------------------------------------------------------------------------------------------------
MAC TYPE IP-ADDRESS/VLAN REASON DISCOVERY-OPTION LAST-SEEN CONNECTED-TO
-----------------------------------------------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Total number of devices displayed: 0

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 11:48:14 GMT

Cluster Licenses:
AP-LICENSE
Value : 12
Used : 0
AAP-LICENSE
Value : 12
Used : 12

Cluster MAX AP Capacity:
Value : 24
Used : 12

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 12:05:58 GMT

EFKO-RFS-1>EFKO-RFS-1>show running-config auto-provisioning-policy lan105
^
% Invalid input detected 9999 at '^' marker.

EFKO-RFS-1>auto-provisioning-policy lan105
^
% Invalid input detected 9999 at '^' marker.

EFKO-RFS-1> evaluate-always
^
% Invalid input detected 9999 at '^' marker.

EFKO-RFS-1> adopt ap7522 precedence 1 profile efko-7522 rf-domain WMS-EFKO-SiM ip 10.2.78.1
10.2.78.4
^
% Invalid input detected 9999 at '^' marker.

EFKO-RFS-1> adopt ap7632 precedence 2 profile efko-AP7632 rf-domain WMS-Zip-TMC ip 10.2.96.
0/22
^
% Invalid input detected 9999 at '^' marker.

EFKO-RFS-1> adopt ap7522 precedence 3 profile yogurt_7522 rf-domain WMS-EFKO-SiM ip 10.2.78
.6 10.2.78.7
^
% Invalid input detected 9999 at '^' marker.

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 12:19:28 GMT

The controller serves two rf-domains in different subnets. Another one will be added. 1 profile - was created initially. 4 points worked. Two were dismantled for testing purposes. When you try to return the point to work, the point does not get the auto-provisioning-policy settings. After unsuccessful attempts, we added 3 profiles to the auto-provisioning-policy. The point receives the reserved address 10.2.78.6, receives the option 191 of dhcp(tried to change Level 2 to Level1). Controller address 10.2.77.77 / 21

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 12:22:20 GMT

EFKO-RFS-1>sh adop log adopter
2021-03-16 09:17:15:Unadopted 48-9B-D5-B3-96-8C (55.B3.96.8C), cfgd notified
2021-03-16 09:17:15:Unadopting 48-9B-D5-B3-96-8C (55.B3.96.8C) because of new adoption request
2021-03-16 09:16:50:Sending MLCP Reply to (00.00.00.00,34,0,10.2.78.6:24576/60-00-01-00-0A-02)
2021-03-16 09:16:45:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=143)
2021-03-16 09:16:45:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=143)
2021-03-16 09:16:45:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=143)
2021-03-16 09:16:44:Adopted 48-9B-D5-B3-96-8C (55.B3.96.8C), cfgd notified
2021-03-16 09:16:38:Unadopted 48-9B-D5-B3-96-8C (55.B3.96.8C), cfgd notified
2021-03-16 09:16:38:Unadopting 48-9B-D5-B3-96-8C (55.B3.96.8C) because of new adoption request
2021-03-16 09:16:08:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=142)
2021-03-16 09:16:08:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=142)
2021-03-16 09:16:08:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=142)
2021-03-16 09:16:07:Adopted 48-9B-D5-B3-96-8C (55.B3.96.8C), cfgd notified
2021-03-16 09:16:02:Unadopted 48-9B-D5-B3-96-8C (55.B3.96.8C), cfgd notified
2021-03-16 09:16:02:Unadopting 48-9B-D5-B3-96-8C (55.B3.96.8C) because of new adoption request
2021-03-16 09:15:32:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=142)
2021-03-16 09:15:32:Sending MLCP Offer to 55.B3.96.8C (link_level=1, preferred=0, capacity=142)
2021-03-16 09:15:31:Adopted 48-9B-D5-B3-96-8C (55.B3.96.8C), cfgd notified

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 17:03:02 GMT

The access point looks for connections to the old controllers. Factory default doesn't help. The current controllers are green, and the other cluster is yellow. Naturally, it does not accept it..

----------

2021-03-11 18:38:36:Ignoring MLCP Offer, vlan_state MLCP_REPLY_WAIT != MLCP_DISCOVERING / MLCP_STP_WAITING

2021-03-11 18:38:36:Sending MLCP Request to B4-C7-99-FB-3A-DB vlan 1

2021-03-11 18:38:36:All adopters lost, restarting MLCP

2021-03-11 18:38:36:Ignoring MLCP Offer, vlan_state MLCP_DONE != MLCP_DISCOVERING / MLCP_STP_WAITING

2021-03-11 18:38:36:MLCP created VLAN link on VLAN 1, offer from B4-C7-99-F9-BF-A3

2021-03-11 18:38:36:Ignoring MLCP Offer, vlan_state MLCP_REPLY_WAIT != MLCP_DISCOVERING / MLCP_STP_WAITING

2021-03-11 18:38:36:MLCP Offer CAP:142 pref 0, already have a better offer CAP:142 pref:0

2021-03-11 18:38:36:Received MLCP offer from 10.2.77.77:24576 preferred=0 capacity = 142 (force:0, level 1)

2021-03-11 18:38:36:Received MLCP offer from 10.2.77.78:24576 preferred=0 capacity = 142 (force:0, level 1)

2021-03-11 18:38:36:Sending MLCP Request to B4-C7-99-F9-BF-A3 vlan 1

2021-03-11 18:38:36:MLCP link vlan-1 offerer 19.FB.3A.DB lost, restarting discovery

2021-03-11 18:38:36:Sending MLCP_DISCOVER to IP 10.2.77.77, UDP port 0

2021-03-11 18:38:36:Sending MLCP_DISCOVER to IP 10.2.77.78, UDP port 0

2021-03-11 18:38:36:Start MLCP IP Discover

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 17:04:27 GMT

2021-03-11 18:31:45:Start MLCP IP Discover

2021-03-11 18:31:45:All adjacencies on MLCP link ip-10.2.77.77 lost, restarting discovery

2021-03-11 18:31:45:Adoption state change: 'Waiting for cfgd OK' to 'Adoption failed': rejected due to auto provisioning

2021-03-11 18:31:45:Waiting for cfgd OK, adopter should be 19.F9.BF.A3

2021-03-11 18:31:45:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'

2021-03-11 18:31:45:Adoption state change: 'Adoption failed' to 'Connecting to adopter'

2021-03-11 18:31:45:Try to adopt to 19.F9.B3.23 (cluster master 19.F9.B3.23 in adopters)

2021-03-11 18:31:44:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': redirected to 19.F9.B3.23

2021-03-11 18:31:44:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'

2021-03-11 18:31:44:Adoption state change: 'Adoption failed' to 'Connecting to adopter'

2021-03-11 18:31:44:Try to adopt to 19.F9.BF.A3 (cluster master 00.00.00.00 in adopters)

2021-03-11 18:31:39:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': Malformed/no response

2021-03-11 18:31:39:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'

2021-03-11 18:31:39:Adoption state change: 'Adoption failed' to 'Connecting to adopter'

2021-03-11 18:31:39:Try to adopt to 19.FB.3A.DB (cluster master 19.FB.3A.DB in adopters)

2021-03-11 18:31:14:Sending MLCP_REQUEST to 10.2.77.77:0

2021-03-11 18:31:11:MLCP created VLAN link on VLAN 1, offer from B4-C7-99-FB-3A-DB

2021-03-11 18:31:11:Sending MLCP Request to B4-C7-99-FB-3A-DB vlan 1

2021-03-11 18:31:09:All adopters lost, restarting MLCP

2021-03-11 18:31:09:Ignoring MLCP Offer. Current offer: is pref 0 is_switch 1 vlan 1. New offer: is pref 0 is_switch 1 vlan 1.

2021-03-11 18:31:09:MLCP Offer CAP:142 pref 0, already have a better offer CAP:142 pref:0

2021-03-11 18:31:09:Received MLCP offer from 10.2.77.78:24576 preferred=0 capacity = 142 (force:0, level 1)

2021-03-11 18:31:09:Ignoring MLCP Offer. Current offer: is pref 0 is_switch 1 vlan 1. New offer: is pref 0 is_switch 1 vlan 1.

ap7522-B3968C*>sh adop log adoptee on ap7522-B3968C

2021-03-11 18:38:41:Sending MLCP_REQUEST to 10.2.77.78:0

2021-03-11 18:38:36:MLCP created VLAN link on VLAN 1, offer from B4-C7-99-FB-3A-DB

2021-03-11 18:38:36:MLCP VLAN link already exists

2021-03-11 18:38:36:Ignoring MLCP Offer, vlan_state MLCP_REPLY_WAIT != MLCP_DISCOVERING / MLCP_STP_WAITING

Re: AP7522 RFS4010

ckelly — Tue, 16 Mar 2021 20:15:08 GMT

Andrey, seems like a few things might be happening here and need more information.

Looking at the output for the licensing, under the AAP type, it shows that you have 12 licenses and 12 have been USED. This tells me that you have already adopted 12 APs.
1. Each RFS4010 comes with 6 included AAP licenses, so with a cluster, you get 12 AAP licenses. If you need more, they have to be purchased.
2. Even if you are no longer using any of those APs and they are not connected, they still exist in the RFS4010 (they’re just offline) and each one continues to consumes a license. If any of these 12 are no longer used and you want to free up the license for it, you need to first DELETE the AP from the controller.
It sounds like you are saying that you have OTHER controllers besides the RFS4010 cluster? You said, “The current controllers are green, and the other cluster is yellow.”
1. Which controller is 10.2.77.77 ? Is this one of the RFS4010 in the cluster?
2. Which controller is 10.2.77.78 ? Is this one of the RFS4010 in the cluster?
3. What is controller 10.2.77.77 ? (is this a 3rd controller?) This is what you said the AP was receiving in the DHCP Option 191 as a controller address”
Before being able to make any sense of the MLCP logs, we have to understand what you have in place and what their addresses are.

Re: AP7522 RFS4010

Andrey — Tue, 16 Mar 2021 21:16:31 GMT

cluster №1

rfs4010-10.2.77.78 19.FB.81.67

rfs4010-10.2.77.77 19.FB.3A.DB

Cluster Runtime Information

Protocol version : 1

Cluster operational state : active

AP license : 12 - embedded in the controller 6+6 (included)

AAP license : 12 - Licenses purchased

AP count : 0 - Currently in use

AAP count : 12 - Currently in use

Max AP adoption capacity : 144

Number of connected member(s): 1

-two rf-domains are set up

- 13 points are connected, one of them without power. That leaves 12, just a match.

- sh adoption info = 12 devices

there is a second cluster, in a different network segment.

cluster№2

rfs4010-10.2.65.65 19.F9.BF.A3

rfs4010-10.2.65.66 19.F9.B3.23

There is another RFS 4010, which is used for training and experiments (cluster № 3)

3) The problem point was connected to cluster №2, then deleted. connected to another controller (cluster №3). And there was a need to connect it to cluster №1. At the first connection, cluster№1 saw it, but did not accept it in the rf-domain. After resetting the settings to default ( this was done with each new move from cluster to cluster), the point stopped accepting cluster №1. Ping and ping mint passes from the point to the controller and in the opposite direction. The point receives the ip address of the controller with dhcp ( also specified manually, with the same negative result) The Cluster refuses to accept the point, the point does not receive auto-settings according to the auto-provisioning-policy.

Re: AP7522 RFS4010

ckelly — Tue, 16 Mar 2021 22:03:51 GMT

Thanks for the more detailed layout.

Next: This problematic AP - Can you confirm that you WANT it to adopt to cluster #1 ?

I can see where the AP is attempting to adopt to the controllers in Cluster #1 but there’s an ‘adoption failed’ message.

On the AP, run:

show adoption info

show mint known-adopters

On the Cluster #1 controllers, run:

show adoption history

Re: AP7522 RFS4010

Andrey — Wed, 17 Mar 2021 12:18:19 GMT

AP: ap7522-B3968C*>sh adop info
Not available to this target

ap7522-B3968C*>show mint known-adopters
19.F9.B3.23, 19.F9.BF.A3, 19.FB.3A.DB, 19.FB.81.67
----------------

Cluster#1 show adoption history:

48-9B-D5-B3-96-8C ap7522 un-adopted 2021-03-12 19:15:07 Auto-Provisioning-Policy, failed to get profile/rf-domain from the NOC

every 20 seconds

Re: AP7522 RFS4010

Andrey — Thu, 18 Mar 2021 12:36:44 GMT

There was an attempt to connect another access point. The point is displayed in the server connections. The point was reset to the factory settings.

EFKO-RFS-1>sh adopt i

----------------------------------------------------------------------------------------------------

HOST-NAME MAC TYPE MODEL SERIAL-NUMBER

----------------------------------------------------------------------------------------------------

efko-yogurt-ap7522-3 94-9B-2C-2B-83-BC ap7522 AP-7522-67040-WR 19165522200552

efko-yogurt-ap7522-4 94-9B-2C-2B-83-D0 ap7522 AP-7522-67040-WR 19165522200557

ap7522-2B83E4 94-9B-2C-2B-83-E4 ap7522 AP-7522-67040-WR 19165522200562

1sclad-3 DC-B8-08-6D-B7-9D ap7632 AP-7632-680B30-WR 1920Y-1253900000

2sclad-3 DC-B8-08-6D-B8-47 ap7632 AP-7632-680B30-WR 1920Y-1257300000

1sclad-7 DC-B8-08-6D-B8-EC ap7632 AP-7632-680B30-WR 1920Y-1260600000

2sclad-1 DC-B8-08-6D-B9-2D ap7632 AP-7632-680B30-WR 1920Y-1261900000

1sclad-6 DC-B8-08-6E-51-44 ap7632 AP-7632-680B30-WR 1922Y-1191900000

1sclad-1 DC-B8-08-6E-51-AD ap7632 AP-7632-680B30-WR 1922Y-1194000000

1sclad-5 DC-B8-08-6E-52-8E ap7632 AP-7632-680B30-WR 1922Y-1198500000

1sclad-2 DC-B8-08-6E-53-42 ap7632 AP-7632-680B30-WR 1922Y-1202100000

1sclad-4 DC-B8-08-6E-53-C9 ap7632 AP-7632-680B30-WR 1922Y-1204800000

2sclad-2 DC-B8-08-6E-54-32 ap7632 AP-7632-680B30-WR 1922Y-1206900000

I got my license.

Cluster MAX AP Capacity:
Value : 24
Used : 13

BUT, I didn't get the settings.

Adopted Devices:

--------------------------------------------------------------------------------------------------------------------------------

DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME IPv4-ADDRESS

--------------------------------------------------------------------------------------------------------------------------------

efko-yo...p7522-3 5.9.6.0-007R configured No EFKO-RFS-1 222 days 12:25:54 222 days 12:28:04 10.2.78.3

efko-yo...p7522-4 5.9.6.0-007R configured No EFKO-RFS-1 222 days 12:11:23 222 days 12:28:14 10.2.78.4

ap7522-2B83E4 5.9.6.0-007R error Yes EFKO-RFS-2 0 days 18:32:46 0 days 18:34:34 10.2.78.1