AP7522 RFS4010

[Andrey]

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?

[Andrey]

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

[Andrey]

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

[ckelly]

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

[Andrey]

1)

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

2)

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.