topic AP310 and AP310-1 in ExtremeWireless (WiNG)

AP310 and AP310-1

AlexeyUs — Wed, 14 Dec 2022 10:53:56 GMT

Hello!

I have 2 APs of AP310-1 and one of AP310. VC is running on one of AP310-1. Profiles created for AP310 and AP310-1. All firmwares identicall (7.7.1.4).

One AP310-1 is adopted normal (other is VC), but AP310 won't adopt with message: 'Auto-Provisioning-Policy, failed to get profile/rf-domain from the NOC' (from adoption history from VC)

I'm tried create default auto-provisioning-policy and tried without him (AP310-1 adopted without him normal)

What did i miss?

Re: AP310 and AP310-1

AlexeyUs — Wed, 14 Dec 2022 11:05:57 GMT

From AP310 (show adoption log adoptee)

ap310-386773>show adoption log adoptee
2022-01-01 21:43:19:MLCP created VLAN link on VLAN 1, offer from B0-27-CF-CF-1C-E6
2022-01-01 21:43:19:MLCP VLAN link already exists
2022-01-01 21:43:19:Sending MLCP Request to B0-27-CF-CF-1C-E6 vlan 1
2022-01-01 21:43:19:All adopters lost, restarting MLCP
2022-01-01 21:43:19:MLCP created VLAN link on VLAN 1, offer from B0-27-CF-CF-1C-E6
2022-01-01 21:43:19:Sending MLCP Request to B0-27-CF-CF-1C-E6 vlan 1
2022-01-01 21:43:19:MLCP link vlan-1 offerer 4F.CF.1C.E6 lost, restarting discovery
2022-01-01 21:43:19:Adoption state change: 'Waiting for cfgd OK' to 'Adoption failed': rejected due to auto provisioning
2022-01-01 21:43:19:Waiting for cfgd OK, adopter should be 4F.CF.1C.E6
2022-01-01 21:43:19:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2022-01-01 21:43:19:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-01-01 21:43:19:Try to adopt to 4F.CF.1C.E6 (cluster master 00.00.00.00 in adopters)
2022-01-01 21:43:14:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': Malformed/no response
2022-01-01 21:43:14:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2022-01-01 21:43:14:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2022-01-01 21:43:14:Try to adopt to 4F.CF.1C.E6 (cluster master 4F.CF.1C.E6 in adopters)

Re: AP310 and AP310-1

Christoph_S — Wed, 14 Dec 2022 15:36:51 GMT

Hello Alexey,

For the VC to adopt heterogenous APs, you will have to use the ANYAP profile.

Please follow this link for instructions: https://extremeportal.force.com/ExtrArticleDetail?an=000089072

Re: AP310 and AP310-1

Christopher_Fra — Wed, 14 Dec 2022 17:01:27 GMT

The AP310 will need to be the VC for this deployment in order to adopt the AP310-1. ANYAP profile will be required with auto-provisioning policy for the AP310-1 to adopt to the AP310. Firmware must match.

Re: AP310 and AP310-1

AlexeyUs — Thu, 15 Dec 2022 06:43:16 GMT

Many thanks!

Re: AP310 and AP310-1

AlexeyUs — Thu, 15 Dec 2022 06:45:49 GMT

But I'm a little confused. If controller have the profile for device (AP310, AP310-1) why his not apply him by profile type?