-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RfProfile is required in pnp_device_claim_to_site #52
Comments
Hi @beye91 , We are working on it, we will keep you updated. |
Hey @beye91, version 2.4.7 of dnacentersdk and 6.1.0 of dnacenter-ansible have been published, try these new versions and let us know if it is working for you now. |
Hey @fmunozmiranda thank you so much! The issue has been solved. I have been able to claim the device 👍
|
With pleasure @beye91, in case of any other issue you just open the case. |
fmunozmiranda
pushed a commit
that referenced
this issue
Dec 19, 2023
Add code for Inventory Module with more update operations
syed-khadeerahmed
pushed a commit
to syed-khadeerahmed/dnacenter-ansible
that referenced
this issue
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
Describe the bug
For onboarding on access point to the site the rfProfile is needed. The rfProfile is of course not needed for an switch!
A successful call from the API directly would look like this:
--data-raw '{"siteId":"ebb73862-9e5d-4405-8551-83677ffe9199","deviceId":"6239b85c64ffdd425b7a786d","hostname":"TEST","type":"AccessPoint","rfProfile":"TYPICAL"}'
The following playbook, which has all required variables will generate an error:
Expected behavior
rfProfile needs to be set once the type AccessPoint is defined.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: