Vx9000+ap7532 provisioning issue
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-04-2019 06:36 PM
Hello community.
I have an issue with VX with provisioning of ap profile. Ap is adopting to vx with l3 and receiving the default profile instead of relevant one.
What is the most common configuration error in this case?
Suggest please wich process I need to debug.
Thanks
Aviv
I have an issue with VX with provisioning of ap profile. Ap is adopting to vx with l3 and receiving the default profile instead of relevant one.
What is the most common configuration error in this case?
Suggest please wich process I need to debug.
Thanks
Aviv
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-04-2019 06:43 PM
Hello Aviv,
Most common issue is that the auto-provisioning policy is not mapped to the VX9000 after creation. Ensure that 'Adopt if No Rules Match' is not enabled on the auto-provisioning policy. Ensure that the provisioning policy is mapped to the VX9000 and commit/save. Remove/Delete the AP from the VX9000 and let the AP perform adoption process and come in clean.
Most common issue is that the auto-provisioning policy is not mapped to the VX9000 after creation. Ensure that 'Adopt if No Rules Match' is not enabled on the auto-provisioning policy. Ensure that the provisioning policy is mapped to the VX9000 and commit/save. Remove/Delete the AP from the VX9000 and let the AP perform adoption process and come in clean.
