11-07-2019 02:10 PM
I am trying to automate the whole provisioning of the AP in DNA via API.
Something strange it is happening in our DNA that we are not able to understand. After we connect out the box AP (Cisco Catalyst 9120AXI Series Unified Access Points) to the network the below actions will happen:
1. Device will be part of the PnP in status Unclaimed
2. After 20-30min the device will change status to Error
3. Device is part of the Inventory.
Could you explain please why we are experiencing this behaviour?
We are facing also another issue when we trigger API POST "AP provision": /dna/intent/api/v1/wireless/ap-provision:
data we send:
payload:
[
{
"rfProfile": "TYPICAL",
"siteId": "XXXXXXX-XXXX-XXXX-XXXX-dXXXXXXXXX",
"type": "Unified AP",
"deviceName": "XXXXXX.XXXX.XXX"
}
]
Error we receive from the excecution ID:
{ "bapiKey" : "XXXX-XXXX-XXXX-XXXX", "bapiName" : "AP Provision", "bapiExecutionId" : "XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX", "startTime" : "Thu Nov 07 21:47:11 UTC 2019", "startTimeEpoch" : 1573163231726,ing.a.cepele@gmail.com "endTime" : "Thu Nov 07 21:47:11 UTC 2019", "endTimeEpoch" : 1573163231980, "timeDuration" : 254, "status" : "FAILURE", "bapiError" : "Validation error" }
Do you have any suggestion what we get this Error?
What do we lose if we do not Provision the AP?
11-07-2019 04:41 PM
For the first issue, you should be able to get details on the error by clicking the hyperlink of the device name. Then go to the "History" tab of the popover window. Then "Info->History Details" for the entry that corresponds to error. Any detail on the error there?
For the second issue, I recommend opening a TAC case. Ask them why the API can't return a more specific error than "Validation Error". I also suggest using the "Make a Wish" button in the Cisco DNA GUI to request directory from product management that their API errors be more specific (perhaps about the field that is invalid).
-Preston
Cisco Customer Success Specialist
11-08-2019 02:37 AM
Please find below the history for AP PnP:
11/07/2019 02:24:43 PM | NCOB02074: Initialized Timed Out, Please check the device connectivity with the Server. | Info | |
11/07/2019 01:50:11 PM | Task: System Task Completed | Info | |
11/07/2019 01:50:08 PM | Executing System Workflow to Initialize Device | Info | |
11/07/2019 01:50:08 PM | Executing Task: System Task | Info | |
11/07/2019 01:49:56 PM | Device Authenticated Successfully | Info | |
11/07/2019 01:49:50 PM | Secured Device | Info | |
11/07/2019 01:49:22 PM | Network Device Created | Info | |
11/07/2019 01:49:22 PM | Securing Device | Info | |
11/07/2019 01:49:22 PM | Device Discovered | Info | |
11/07/2019 12:31:58 PM | Deleted Device | Info | |
11/04/2019 01:51:43 PM | NCOB02074: Initialized Timed Out, Please check the device connectivity with the Server. | Info | |
11/04/2019 01:17:11 PM | Task: System Task Completed | Info | |
11/04/2019 01:17:07 PM | Executing System Workflow to Initialize Device | Info | |
11/04/2019 01:17:07 PM | Executing Task: System Task | Info | |
11/04/2019 01:16:57 PM | Device Authenticated Successfully | Info | |
11/04/2019 01:16:53 PM | Secured Device | Info | |
11/04/2019 01:16:25 PM | Securing Device | Info | |
11/04/2019 01:16:25 PM | Network Device Created | Info | |
11/04/2019 01:16:25 PM | Device Discovered | Info | |
11/01/2019 12:53:21 PM | Deleted Device | Info | |
10/29/2019 03:27:03 PM | NCOB02074: Initialized Timed Out, Please check the device connectivity with the Server. | Info | |
10/29/2019 03:09:43 PM | Claimed Device | Info | |
10/29/2019 02:52:37 PM | Task: System Task Completed | Info | |
10/29/2019 02:52:35 PM | Executing System Workflow to Initialize Device | Info | |
10/29/2019 02:52:35 PM | Executing Task: System Task | Info | |
10/29/2019 02:52:23 PM | Device Authenticated Successfully | Info | |
10/29/2019 02:52:19 PM | Secured Device | Info | |
10/29/2019 02:51:53 PM | Network Device Created | Info | |
10/29/2019 02:51:53 PM | Securing Device | Info | |
10/29/2019 02:51:53 PM | Device Discovered | Info | |
10/29/2019 02:38:40 PM | Deleted Device | Info | |
10/25/2019 01:22:16 PM | NCOB02074: Executing Reset Timed Out, Please check the device connectivity with the Server. | Info | |
10/25/2019 01:22:02 PM | Reset Initiated | Info | |
10/25/2019 12:28:16 PM | NCOB02074: Initialized Timed Out, Please check the device connectivity with the Server. | Info | |
10/25/2019 11:52:55 AM | Task: System Task Completed | Info | |
10/25/2019 11:52:50 AM | Executing System Workflow to Initialize Device | Info | |
10/25/2019 11:52:50 AM | Executing Task: System Task | Info | |
10/25/2019 11:52:39 AM | Device Authenticated Successfully | Info | |
10/25/2019 11:52:36 AM | Secured Device | Info | |
10/25/2019 11:52:13 AM | Network Device Created | Info | |
10/25/2019 11:52:13 AM | Securing Device | Info | |
10/25/2019 11:52:13 AM | Device Discovered | Info | |
10/25/2019 11:46:50 AM | Deleted Device | Info | |
10/25/2019 11:44:16 AM | NCOB02074: Executing Reset Timed Out, Please check the device connectivity with the Server. | Info | |
10/25/2019 11:43:32 AM | Reset Initiated | Info | |
10/25/2019 11:39:16 AM | NCOB02074: Initialized Timed Out, Please check the device connectivity with the Server. | Info | |
10/25/2019 11:04:16 AM | Task: System Task Completed | Info | |
10/25/2019 11:04:14 AM | Executing System Workflow to Initialize Device | Info | |
10/25/2019 11:04:14 AM | Executing Task: System Task | Info | |
10/25/2019 11:04:05 AM | Device Authenticated Successfully | Info | |
10/25/2019 11:04:02 AM | Secured Device | Info | |
10/25/2019 11:03:36 AM | Network Device Created | Info | |
10/25/2019 11:03:36 AM | Securing Device | Info | |
10/25/2019 11:03:36 AM | Device Discovered | Info | |
10/25/2019 10:48:20 AM | Deleted Device | Info | |
10/22/2019 06:50:16 PM | NCOB02074: Initialized Timed Out, Please check the device connectivity with the Server. | Info | |
10/22/2019 06:28:22 PM | Device Authenticated Successfully | Info | |
10/22/2019 06:10:21 PM | Task: System Task Completed | Info | |
10/22/2019 06:10:17 PM | Executing System Workflow to Initialize Device | Info | |
10/22/2019 06:10:17 PM | Executing Task: System Task | Info | |
10/22/2019 06:10:05 PM | Device Authenticated Successfully | Info | |
10/22/2019 06:09:58 PM | Secured Device | Info | |
10/22/2019 06:09:31 PM | Network Device Created | Info | |
10/22/2019 06:09:31 PM | Securing Device | Info | |
10/22/2019 06:09:31 PM | Device Discovered |
I am not aware of the "Make a Wish" button. Could you please give a guidline where I can locate it?
Many thanks
11-12-2019 09:48 AM
03-28-2020 01:16 AM
Not sure if you resolved this, but this is not the right API call for PnP.
You should use the following API with a payload similar to below
dna/intent/api/v1/onboarding/pnp-device/site-claim
{
"hostname": "pnp3800",
"rfProfile": "LOW",
"type": "AccessPoint",
"siteId" : "e3756afc-abbc-4581-a29b-f972c6db006f",
"deviceId" : "5e7d25b5b26aef000841e167"
}
The provisioning API is for a different use case, if you onboard the API via traditional WLC discovery..
{
"hostname": "pnp3800",
"rfProfile": "LOW",
"type": "AccessPoint",
"siteId" : "e3756afc-abbc-4581-a29b-f972c6db006f",
"deviceId" : "5e7d25b5b26aef000841e167"
}
{
"hostname": "pnp3800",
"rfProfile": "LOW",
"type": "AccessPoint",
"siteId" : "e3756afc-abbc-4581-a29b-f972c6db006f",
"deviceId" : "5e7d25b5b26aef000841e167"
}
04-01-2020 05:17 AM
The problem we face is that we cannot use PnP APIs, since after no action taken the device goes automatically to inventory after 30min. Later we had to use other APIs in order to provision the devices.
04-10-2021 05:17 AM
Which API call did you use to provision the AP finally?
07-19-2021 04:36 AM - edited 07-19-2021 05:27 AM
delete, double post
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide