- Had successfully provisioned several C899G routers by using a small bootstrap configuration, giving the device the necessary certificates and the PnP template (the APIC-EM is behind a reverse proxy).
- Recently changed the provisioning process to use the PnP redirect service on Cisco Software Central.
- So the now unconfigured device contacts devicehelper.cisco.com for the IP address of the APIC-EM.
- That redirection seems to work fine, but the PnP process on the APIC-EM fails with the following error messages:
2017-05-17 10:21:21 (CEST) | Failed health check since device is stuck in non-terminal state LOCATION_TAG_REQUESTED for more than threshold time: 0 hours, 16 minutes, 0 seconds |
2017-05-17 10:04:37 (CEST) | Received new work request from Agent while expecting work response. Retrying operation LOCATION_TAG_REQUESTED |
2017-05-17 10:00:38 (CEST) | Device first contact |
2017-05-17 09:59:38 (CEST) | Detected a reboot on errored device and cleaned up error state |
2017-05-17 09:56:21 (CEST) | Failed health check since device is stuck in non-terminal state LOCATION_TAG_REQUESTED for more than threshold time: 0 hours, 16 minutes, 0 seconds |
2017-05-17 09:55:57 (CEST) | Received new work request from Agent while expecting work response. Retrying operation LOCATION_TAG_REQUESTED |
2017-05-17 09:52:26 (CEST) | Received new work request from Agent while expecting work response. Retrying operation LOCATION_TAG_REQUESTED |
2017-05-17 09:48:54 (CEST) | Received new work request from Agent while expecting work response. Retrying operation LOCATION_TAG_REQUESTED |
2017-05-17 09:45:20 (CEST) | Received new work request from Agent while expecting work response. Retrying operation LOCATION_TAG_REQUESTED |
2017-05-17 09:41:45 (CEST) | Received new work request from Agent while expecting work response. Retrying operation LOCATION_TAG_REQUESTED |
2017-05-17 09:37:21 (CEST) | Device first contact |
if you have a bootstrap and just point it to the RP it all works fine. The only difference is the bootstrap used to have the PnP profile, and now it does not (as it relies on devicehelper.cisco.com)
Comments
0 comments
Please sign in to leave a comment.