Re: PnP profile issues.

gm.watson · ‎08-23-2018

We are testing APIC-EM to do day zero deployment of our 3850's. Everything goes smoothly with the configuration push. Unfortunately the APIC-EM server is creating a pnp profile which upon rebooting will contact the APIC-EM server and re-download the config file.

Is there a way to prevent this from happening? Other than putting a "no pnp profile pnp-zero-touch" statement the config.

aradford · ‎08-23-2018

That should not happen.

If the PnP process is successful it is not supposed to run again.

Are you sure the config gets saved? What is the config register for the device?

3850-core#show ver | inc regi

Configuration register is 0x102

gm.watson · ‎08-27-2018

The reg is set properly and the config is getting saved. APIC-EM is completing with it showing as "Provisioned", but after a reboot is shows up in the APIC-EM server as unclaimed. Also if it was in a Project it re-runs the process. We plan on using APIC-EM to deploy over a 1000 switches, so getting these little bugs worked out is imperative. Could it have to do with the version of code we are running?

Here is the sh ver:

Switch Ports Model SW Version SW Image Mode

------ ----- ----- ---------- ---------- ----

* 1 56 WS-C3850-48P 16.3.6 CAT3K_CAA-UNIVERSALK9

Configuration register is 0x

And the show pnp profile "pnp-zero-touch" AFTER a completed successful config push and re-start:

SWCORP16A-02#sh pnp profile

PnP Profiles: Active:1, Created:1, Deleted:0, Hidden:0

Name CBType Node Primary-Path Primary-Trans Backup-Trans

pnp-zero-touch User visible pnp/WORK-REQUEST HTTPS none

Initiator Profile pnp-zero-touch: 1 open connections: 0 closing connections

Encap: pnp

WSSE header is not required. Configured authorization level is 1

SID:[ab21e154-ed54-4bbf-880a-a6c92d89aa69], LastSID:[-], ChangedCount:1, SIDAuthOnly:No, MustValidate:No, MustRenew:No

Work-Request Tracking: Validation Yes, Total 44, SID=[ab21e154-ed54-4bbf-880a-a6c92d89aa69], Violation 0, PSR 0, PSB 0

Pending-WR: X/M/R=0/1/0, UDI=[PID:WS-C3850-48F-S,VID:V02,SN:FOC1740U0E3], SID=[ab21e154-ed54-4bbf-880a-a6c92d89aa69], Correlator=[CiscoPnP-1.0-44-514-FFA778EA38-44]

Last-WR: X/M/R=0/1/0, UDI=[PID:WS-C3850-48F-S,VID:V02,SN:FOC1740U0E3], SID=[ab21e154-ed54-4bbf-880a-a6c92d89aa69], Correlator=[CiscoPnP-1.0-43-514-FFA778F1F0-43]

PnP Request Tracking: Current:[backoff], Last:[backoff], First:[device-authentication]

Total:43, OK:43, Failed:0, LastFailed:[-]

PnP Response Tracking: Retry-Allowed 0, Total 0

Last-PR: X/M/R=0/1/0, UDI=[PID:WS-C3850-48F-S,VID:V02,SN:FOC1740U0E3], SID=[ab21e154-ed54-4bbf-880a-a6c92d89aa69], Correlator=[CiscoPnP-1.0-44-514-FFA778EA38-44]

PnP Backoff Time Tracking: Default 60, Current 60, Last 60, First:60, OK:22, Failed:0

Countdown: Security Unlock: S=1/F=0/T=2048, Service Lock: S=22/F=0/T=37, Service Req Wait: S=0/F=0/T=37, Prxoy Req Wait S=289/F=0/T=1, Service Resp Ack: S=43/F=0/T=0

Max message (RX) is 50 Kbytes

XEP Faults are sent

Idle timeout infinite

Keepalive not configured

Reconnect time 60 seconds

Primary Transport:https to Host:-, IP:170.xxx.xxx.xxx, Port:443, Src-Intf:-, VRF:-, URL pnp/WORK-REQUEST

Connected to the primary transport via https

Remote connection via HTTP client. URL https://170.2.49.31:443/pnp/WORK-REQUEST, post

Established at 11:02:55.974 PDT Mon Aug 27 2018

Tx 47224 bytes (86 msg), Tx 0 errors,

Last message sent at 11:26:20.644 PDT Mon Aug 27 2018

Rx 23790 bytes (86 msg), 0 empty msg

Last message received at 11:26:20.900 PDT Mon Aug 27 2018

Statistics for profile pnp-zero-touch

incoming total 86, bad XML 0, authentication errors 0, oversized 0

outgoing total 87, absorbed 0

message internal errors 43

Connection Accepts 2, local hangup 0, remote hangup 1, keepalive hangup 0

session internal errors 0, continuous faults 0, total faults 0