This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Wireless
- ExtremeWireless (WiNG)
- Re: AP7522 RFS4010
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
AP7522 RFS4010
AP7522 RFS4010
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-15-2021 12:18 PM
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?
17 REPLIES 17
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-16-2021 01:15 PM
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.
- 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.
- 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.”
- Which controller is 10.2.77.77 ? Is this one of the RFS4010 in the cluster?
- Which controller is 10.2.77.78 ? Is this one of the RFS4010 in the cluster?
- 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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-16-2021 10:04 AM
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.
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: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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-16-2021 10:03 AM
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: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: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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-16-2021 05:22 AM
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
03-16-2021 05:19 AM
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
