12-14-2022 02:53 AM
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?
Solved! Go to Solution.
12-14-2022 07:36 AM - edited 12-14-2022 07:36 AM
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
BR
12-14-2022 03:05 AM
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)