topic Re: 3850 PnP using DHCP option43 in Controllers

3850 PnP using DHCP option43

daz_efx_2000 — Fri, 01 Mar 2019 12:30:37 GMT

I have a 3850 and want it to download its config from APIC-EM with NO intervention of the switch i.e power the switch on and it automagicly connects to the APIC-EM and installs its confg.

So...I have a 3850 with new software ---- cat3k_caa-universalk9.SPA.03.06.05.E.152-2.E5

I have cleared the config using the following commands below .... as per the following link

==============Website screen output========================

configure terminal

crypto key zeroize

no crypto pki certificate pool

no pnp profile pnp-zero-touch

end

delete nvram:*.cer

delete stby-nvram:*.cer (if the device has stack members)

write erase

reload

====================End of output======================

(all related networking is ok as it works with manual intervention... keep reading and you will see what I mean)

if i boot up the switch and just monitor it this is what it does please note when it asks if i want to enter config mode i have not entered anything as i want to simulate zero intervention. The second line appears after a while and will then just keep looping to no avail.

==============3850 screen output========================

Would you like to enter the initial configuration dialog? [yes/no]:

Loading http://devicehelper.cisco.com/ca/trustpool !

%Error opening tftp://255.255.255.255/network-confg (Timed out)

%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)

%Error opening tftp://255.255.255.255/router-confg (Timed out)

%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)

%Error opening tftp://255.255.255.255/network-confg (Timed out)

%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)

%Error opening tftp://255.255.255.255/router-confg (Timed out)

%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)

%Error opening tftp://255.255.255.255/network-confg (Timed out)

%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)

Loading http://devicehelper.cisco.com/ca/trustpool !

%Error opening tftp://255.255.255.255/router-confg (Timed out)

%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)

====================End of output======================

So the reason why it is trying to get to http://devicehelper.cisco.com/ca/trustpool is because when I check the config which at this point is at factory default, the following appears.

====================3850 screen output=================

pnp profile pnp_cco_profile

transport https host devicehelper.cisco.com port 443

====================End of output======================

If I go in and change the PnP profile and replace the url with the IP of my APIC-EM it conects and gets its config fine.

so the question is ....

How is the 3850 at factory default with no intervention ever going to connect to the APIC-EM if the factory default profile is making it go to the devicehelper.cisco.com URL. I could point internal DNS for that url to my APIC-EM but then what is the point of having option 43 with the APIC-EM IP in it.

Can you dig it.. can you diiiiiiiggggg iiiiiitttttttttt ???

Also how can I check ALL the DHCP values the 3850 has received from the DHCP server?

Re: 3850 PnP using DHCP option43

daz_efx_2000 — Thu, 11 Aug 2016 16:34:16 GMT

Also here is the config for the dhcp server

=========DHCP server output============

ip dhcp pool pnp_device_pool

network 10.1.1.0 255.255.255.0

default-router 10.1.1.1

dns-server 192.168.64.14

option 43 ascii "5A1N;B2;K4;I192.168.64.18;J80"

option 60 ascii "ciscopnp"

============End===================

I have done a debug DHCP on the 3850 and all the above values are received just fine.

https://uk.linkedin.com/in/sajidtheciscokid

Re: 3850 PnP using DHCP option43

Joe Clarke — Thu, 11 Aug 2016 17:33:43 GMT

You're using HTTP and tcp/80 in your DHCP config. But when you got it work, you used HTTPS and tcp/443 (which is what you want). Try:

5A1N;B2;K5;I192.168.64.18;J443

See if that works.

Re: 3850 PnP using DHCP option43

davidlin# — Thu, 11 Aug 2016 17:52:18 GMT

Your DHCP server setup has both DNS and Option 43 configs. When your 3850 booted, there will be two discovery methods competing with each other. In your case, DNS was able to resolve devicehelper.cisco.com first before Option 43. Try to remove " dns-server 192.168.64.14" from DHCP server and restart your test with factory default again.

Re: 3850 PnP using DHCP option43

nikbhati — Thu, 11 Aug 2016 18:15:08 GMT

Hi Sajid,

Op43 gets precedence over CCO discovery. From your output seems like the APIC EM at 192.168.64.18 did not respond to the device, hence, the device moved on to CCO. Can you do "sh pnp trace" and it will show you why was op43 not successful.

Please let me know how it goes.

Thanks,

Nikita

Re: 3850 PnP using DHCP option43

daz_efx_2000 — Fri, 12 Aug 2016 10:47:34 GMT

Ok get ready here comes an epic reply of log output.

Still no joy

just want to reply to everyone before I start.

Joseph Clark - Thanks for reply, I have tested by changing option 43 to use https, outcome below.

David Da-Wei Lin - Thanks for reply I did not know about this order of operation (so something learnt!) have removed DNS, outcome below.

Nikita Bhatia - Thanks for your reply out put of "sh pnp trace" to follow.

When I change the DHCP with no DNS but using k4 & port80 in option43 string

ip dhcp pool pnp_device_pool

network 10.1.1.0 255.255.255.0

default-router 10.1.1.1

option 43 ascii "5A1N;B2;K4;I192.168.64.18;J80"

option 60 ascii "ciscopnp"

=================3850 sh pnp trace output ====================

[08/12/16 09:28:59.189 UTC 1 439] Info: Startup config does not exists

[08/12/16 09:28:59.189 UTC 2 439] start_pnpa_discovery: PnP Discovery trial number[1]

[08/12/16 09:28:59.190 UTC 3 439] start_pnpa_discovery: Initiating PnP discovery manager

[08/12/16 09:28:59.190 UTC 4 439] pnpa_discovery_autoinstall_pid_create: waiting for autoinstall

[08/12/16 09:30:01.705 UTC 5 439] pnpa_discovery_autoinstall_pid_create:Received autoinstall complete status

[08/12/16 09:30:06.700 UTC 6 439] pnpa_autonomic_discovery: Starting autonomic discovery

[08/12/16 09:30:06.700 UTC 7 439] pnpa_autonomic_discovery: Starting autonomic discovery

[08/12/16 09:30:11.701 UTC 8 439] pnpa_disc_dhcp_option_43: op43 strict protocol: Yes, must secure: No

[08/12/16 09:30:11.701 UTC 9 439] pnpa_disc_dhcp_option_43: op43 profile pnp-zero-touch

[08/12/16 09:30:11.701 UTC A 439] pnpa_disc_dhcp_option_43: op43 ipaddr 192.168.64.18

[08/12/16 09:30:11.701 UTC B 439] pnpa_disc_dhcp_option_43: op43 transport 1

[08/12/16 09:30:11.701 UTC C 439] pnpa_disc_dhcp_option_43: transport http

[08/12/16 09:30:11.702 UTC D 439] pnpa_validate_port_type: Port is 80

[08/12/16 09:30:11.702 UTC E 439] pnpa_disc_dhcp_option_43: op43 port 80

[08/12/16 09:30:11.702 UTC F 439] pnpa_validate_ip_type: op43 iptype ipv4

[08/12/16 09:30:11.702 UTC 10 439] pnp_httpc_register: PnP httpc registered

[08/12/16 09:30:11.702 UTC 11 439] get_pnp_work_req_url: Port is 80

[08/12/16 09:30:11.702 UTC 12 439] pnp_httpc_send_get: url http://192.168.64.18:80/pnp/HELLO

[08/12/16 09:30:11.703 UTC 13 439] pnp_httpc_send_get: HTTP SEND SUCCESS

[08/12/16 09:30:12.723 UTC 14 334] pnp_http_resp_data_alloc: PnP response data alloc 4096 bytes

[08/12/16 09:30:12.723 UTC 15 334] pnp_resp_data: request status Response data recieved, successfully

[08/12/16 09:30:12.723 UTC 16 334] pnp_resp_data: DATA STARTS HERE

[08/12/16 09:30:12.723 UTC 17 334] pnp_resp_data: DATA ENDS HERE

[08/12/16 09:30:12.723 UTC 18 334] pnp_resp_data: Status of this transaction is 200

[08/12/16 09:30:12.723 UTC 19 334] pnp_resp_data: Length of data handed over 21

[08/12/16 09:30:12.723 UTC 1A 334] pnp_resp_data: session id : 3

[08/12/16 09:30:12.723 UTC 1B 334] pnp_resp_data: transaction id : 1

[08/12/16 09:30:12.724 UTC 1C 334] pnp_resp_data: status_code : 200

[08/12/16 09:30:12.724 UTC 1D 334] pnp_resp_data: status_string : OK

[08/12/16 09:30:12.724 UTC 1E 334] pnp_resp_data: content_type : application/json;charset=UTF-8

[08/12/16 09:30:12.724 UTC 1F 334] pnp_resp_data: content_encoding :

[08/12/16 09:30:12.724 UTC 20 334] pnp_resp_data: content_length : 21

[08/12/16 09:30:12.724 UTC 21 334] pnp_resp_data: Location :

[08/12/16 09:30:12.724 UTC 22 334] pnp_resp_data: Server : Jetty(9.0.z-SNAPSHOT)

[08/12/16 09:30:12.724 UTC 23 334] pnp_resp_data: Data has not been cached

[08/12/16 09:30:12.725 UTC 24 334] pnp_http_resp_data_free: pnp response data freed

[08/12/16 09:30:12.725 UTC 25 439] pnp_httpc_send_get: HTTP send success()

[08/12/16 09:30:12.725 UTC 26 439] send_work_req: HTTP SEND GET REQUEST SUCCESS

[08/12/16 09:30:12.725 UTC 27 439] HA registry indicates presence of standby

[08/12/16 09:30:12.725 UTC 28 439] HA, config safe check [NOT OK], for configuring[try:0]

[08/12/16 09:30:12.725 UTC 29 439] HA, config safe check [NOT OK], for configuring[try:1]

[08/12/16 09:30:12.725 UTC 2A 439] configure_profile: after parse configure rc is 1

[08/12/16 09:30:12.726 UTC 2B 439] pnpa_dhcp_discovery:PnP profile config unsuccessful

[08/12/16 09:30:12.732 UTC 2C 439] pnpa_disc_dhcp_option_43: op43 strict protocol: Yes, must secure: No

[08/12/16 09:30:12.732 UTC 2D 439] pnpa_disc_dhcp_option_43: op43 profile pnp-zero-touch

[08/12/16 09:30:12.732 UTC 2E 439] pnpa_disc_dhcp_option_43: op43 ipaddr 192.168.64.18

[08/12/16 09:30:12.732 UTC 2F 439] pnpa_disc_dhcp_option_43: op43 transport 1

[08/12/16 09:30:12.732 UTC 30 439] pnpa_disc_dhcp_option_43: transport http

[08/12/16 09:30:12.732 UTC 31 439] pnpa_validate_port_type: Port is 80

[08/12/16 09:30:12.732 UTC 32 439] pnpa_disc_dhcp_option_43: op43 port 80

[08/12/16 09:30:12.732 UTC 33 439] pnpa_validate_ip_type: op43 iptype ipv4

[08/12/16 09:30:12.733 UTC 34 439] pnp_httpc_register: PnP Already registered with httpc

[08/12/16 09:30:12.733 UTC 35 439] get_pnp_work_req_url: Port is 80

[08/12/16 09:30:12.733 UTC 36 439] pnp_httpc_send_get: url http://192.168.64.18:80/pnp/HELLO

[08/12/16 09:30:12.733 UTC 37 439] pnp_httpc_send_get: HTTP SEND SUCCESS

[08/12/16 09:30:12.740 UTC 38 334] pnp_http_resp_data_alloc: PnP response data alloc 4096 bytes

[08/12/16 09:30:12.740 UTC 39 334] pnp_resp_data: request status Response data recieved, successfully

[08/12/16 09:30:12.740 UTC 3A 334] pnp_resp_data: DATA STARTS HERE

[08/12/16 09:30:12.740 UTC 3B 334] pnp_resp_data: DATA ENDS HERE

[08/12/16 09:30:12.740 UTC 3C 334] pnp_resp_data: Status of this transaction is 200

[08/12/16 09:30:12.740 UTC 3D 334] pnp_resp_data: Length of data handed over 21

[08/12/16 09:30:12.740 UTC 3E 334] pnp_resp_data: session id : 3

[08/12/16 09:30:12.740 UTC 3F 334] pnp_resp_data: transaction id : 2

[08/12/16 09:30:12.740 UTC 40 334] pnp_resp_data: status_code : 200

[08/12/16 09:30:12.740 UTC 41 334] pnp_resp_data: status_string : OK

[08/12/16 09:30:12.740 UTC 42 334] pnp_resp_data: content_type : application/json;charset=UTF-8

[08/12/16 09:30:12.740 UTC 43 334] pnp_resp_data: content_encoding :

[08/12/16 09:30:12.740 UTC 44 334] pnp_resp_data: content_length : 21

[08/12/16 09:30:12.740 UTC 45 334] pnp_resp_data: Location :

[08/12/16 09:30:12.740 UTC 46 334] pnp_resp_data: Server : Jetty(9.0.z-SNAPSHOT)

[08/12/16 09:30:12.740 UTC 47 334] pnp_resp_data: Data has not been cached

[08/12/16 09:30:12.740 UTC 48 334] pnp_http_resp_data_free: pnp response data freed

[08/12/16 09:30:12.740 UTC 49 439] pnp_httpc_send_get: HTTP send success()

[08/12/16 09:30:12.740 UTC 4A 439] send_work_req: HTTP SEND GET REQUEST SUCCESS

[08/12/16 09:30:12.740 UTC 4B 439] HA registry indicates presence of standby

[08/12/16 09:30:12.740 UTC 4C 439] HA, config safe check [NOT OK], for configuring[try:0]

[08/12/16 09:30:12.740 UTC 4D 439] HA, config safe check [NOT OK], for configuring[try:1]

[08/12/16 09:30:12.740 UTC 4E 439] configure_profile: after parse configure rc is 1

[08/12/16 09:30:12.740 UTC 4F 439] pnpa_dhcp_discovery:PnP profile config unsuccessful

[08/12/16 09:30:17.740 UTC 50 439] pnpa_dns_discovery: Starting PnP DNS discovery

[08/12/16 09:30:17.740 UTC 51 439] pnpa_disc_dhcp_dns: failed to obtain the domain name

[08/12/16 09:30:17.740 UTC 52 439] pnpa_dns_discovery:DNS discovery not successful

[08/12/16 09:30:17.740 UTC 53 439] pnpa_dns_discovery: Starting PnP DNS discovery

[08/12/16 09:30:17.740 UTC 54 439] pnpa_disc_dhcp_dns: failed to obtain the domain name

[08/12/16 09:30:17.740 UTC 55 439] pnpa_dns_discovery:DNS discovery not successful

[08/12/16 09:30:22.738 UTC 56 439] pnpa_cco_discovery: starting CCO discovery

[08/12/16 09:30:31.739 UTC 57 439] pnpa_cco_discovery: Hostname resolution failed

[08/12/16 09:30:31.739 UTC 58 439] pnpa_cco_discovery: starting CCO discovery

[08/12/16 09:30:31.739 UTC 59 439] pnpa_cco_discovery: Hostname resolution failed

[08/12/16 09:30:36.739 UTC 5A 439] pnpa_discovery_manager: Starting NAPP

[08/12/16 09:30:36.739 UTC 5B 439] pnpa_napp_discovery: starting NAPP discovery

[08/12/16 09:30:36.739 UTC 5C 439] set_intf_state_for_napp: Setting interface state for NAPP

[08/12/16 09:30:36.740 UTC 5D 439] pnp_pxc_recv_init: enter

[08/12/16 09:30:36.740 UTC 5E 439] pnp_pxc_send_init: pnp_pxc_xmt_process created. listener_pid=213

[08/12/16 09:30:36.740 UTC 5F 166] pnp_pxc_rcv_process: Begin

[08/12/16 09:30:36.741 UTC 60 166] pnp_pxd_new_workspace: New packet workspace 0x3682BAF8

[08/12/16 09:30:36.741 UTC 61 166] pnp_pxc_create_recv_socket: enter

[08/12/16 09:30:36.746 UTC 62 166] pnp_pxc_create_recv_socket: done

[08/12/16 09:30:36.746 UTC 63 166] pnp_pxc_rcv_loop: enter

[08/12/16 09:30:36.746 UTC 64 213] pnp_pxc_xmt_process: Entering sending loop.

[08/12/16 09:30:36.809 UTC 65 213] pnp_pxc_xmt_loop: str_port_len = 4

[08/12/16 09:30:36.809 UTC 66 213] pnp_pxc_xmt_loop: client_port_no = 1027

[08/12/16 09:30:36.810 UTC 67 213] pnp_pxc_xmt_loop: str_client_ip_len = 7

[08/12/16 09:30:36.810 UTC 68 213] pnp_pxc_xmt_loop: pxy_client_ip = 0.0.0.0

[08/12/16 09:30:36.810 UTC 69 213] pnp_pxc_xmt_loop: String hello = OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP1212:WS-C3850-48POP133:1.0OP144:1027OP157:0.0.0.0

[08/12/16 09:30:36.815 UTC 6A 213] pnp_pxc_xmt_loop: sendto returns 97

[08/12/16 09:30:36.816 UTC 6B 213] pnp_pxc_xmt_loop: PROXY CLIENT: sent data = OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP1212:WS-C3850-48POP133:1.0OP144:1027OP157:0.0.0.0

[08/12/16 09:31:36.810 UTC 6C 213] pnpa_discovery_reset_intf_state: Resetting interface state for NAPP

[08/12/16 09:31:36.811 UTC 6D 213] pnp_pxc_rcv_cleanup: setting FAIL discovery

[08/12/16 09:31:36.811 UTC 6E 213] pnp_pxc_xmt_loop - Killing proxy client sending and receiving processes

[08/12/16 09:31:36.811 UTC 6F 213] send_timeout_response: Timeout status response sent for client 'PID:WS-C3850-48P,VID:V03,SN:FOC1751X06Z' : OPRESPSTATUS:OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP123:1.0OP13OPTRANSS19:TRANSACTION TIMEOUTOPSTATUS33:PROXY CLIENT RETRY COUNT EXCEEDEDOPERRMSG75:Proxy client retry count exceeded. Proxy client process is no longer active

[08/12/16 09:31:36.811 UTC 70 213] create_pnp_pxc_timeout_response_socket: Socket open succeeded

[08/12/16 09:31:36.817 UTC 71 213] destroy_pnp_pxc_timeout_response_socket: Closing socket

[08/12/16 09:31:36.817 UTC 72 213] pnp_pxc_xmt_process: Sending loop exited.

[08/12/16 09:31:36.817 UTC 73 213] pnp_pxc_xmt_cleanup: enter

[08/12/16 09:31:36.817 UTC 74 213] pnp_pxc_xmt_cleanup: Closing socket

[08/12/16 09:31:36.817 UTC 75 213] pnp_pxc_xmt_cleanup: Killing process

[08/12/16 09:31:36.817 UTC 76 439] pnp_wait_on_napp:Received NAPP complete status

[08/12/16 09:31:36.818 UTC 77 439] Info: PnP profile configuration was unsuccessful

[08/12/16 09:31:36.818 UTC 78 439] start_pnpa_discovery: PnP discovery process failed

[08/12/16 09:31:36.818 UTC 79 439] start_pnpa_discovery: User had entered console.Not retrying PnP.

=========================END OF OUTPUT=================================

When I change the DHCP with no DNS but using k5 & port443 in option43 string

ip dhcp pool pnp_device_pool

network 10.1.1.0 255.255.255.0

default-router 10.1.1.1

option 60 ascii "ciscopnp"

option 43 ascii "5A1N;B2;K5;I192.168.64.18;J443"

=================3850 sh pnp trace output ====================

[08/12/16 09:44:28.242 UTC 1 439] Info: Startup config does not exists

[08/12/16 09:44:28.242 UTC 2 439] start_pnpa_discovery: PnP Discovery trial number[1]

[08/12/16 09:44:28.242 UTC 3 439] start_pnpa_discovery: Initiating PnP discovery manager

[08/12/16 09:44:28.242 UTC 4 439] pnpa_discovery_autoinstall_pid_create: waiting for autoinstall

[08/12/16 09:45:31.459 UTC 5 439] pnpa_discovery_autoinstall_pid_create:Received autoinstall complete status

[08/12/16 09:45:36.452 UTC 6 439] pnpa_autonomic_discovery: Starting autonomic discovery

[08/12/16 09:45:36.452 UTC 7 439] pnpa_autonomic_discovery: Starting autonomic discovery

[08/12/16 09:45:41.451 UTC 8 439] pnpa_disc_dhcp_option_43: op43 strict protocol: Yes, must secure: No

[08/12/16 09:45:41.451 UTC 9 439] pnpa_disc_dhcp_option_43: op43 profile pnp-zero-touch

[08/12/16 09:45:41.452 UTC A 439] pnpa_disc_dhcp_option_43: op43 ipaddr 192.168.64.18

[08/12/16 09:45:41.452 UTC B 439] pnpa_disc_dhcp_option_43: op43 transport 2

[08/12/16 09:45:41.452 UTC C 439] pnpa_disc_dhcp_option_43: transport https

[08/12/16 09:45:41.452 UTC D 439] pnpa_validate_port_type: Port is 443

[08/12/16 09:45:41.452 UTC E 439] pnpa_disc_dhcp_option_43: op43 port 443

[08/12/16 09:45:41.452 UTC F 439] pnpa_validate_ip_type: op43 iptype ipv4

[08/12/16 09:45:41.452 UTC 10 439] pnpa_dhcp_discovery:URL[http://192.168.64.18/ca/trustpool]

[08/12/16 09:45:42.478 UTC 11 439] pnp_validate_ca_bundle_url:CA bundle [http://192.168.64.18/ca/trustpool] not present

[08/12/16 09:45:42.485 UTC 12 439] pnpa_disc_dhcp_option_43: op43 strict protocol: Yes, must secure: No

[08/12/16 09:45:42.485 UTC 13 439] pnpa_disc_dhcp_option_43: op43 profile pnp-zero-touch

[08/12/16 09:45:42.485 UTC 14 439] pnpa_disc_dhcp_option_43: op43 ipaddr 192.168.64.18

[08/12/16 09:45:42.485 UTC 15 439] pnpa_disc_dhcp_option_43: op43 transport 2

[08/12/16 09:45:42.485 UTC 16 439] pnpa_disc_dhcp_option_43: transport https

[08/12/16 09:45:42.485 UTC 17 439] pnpa_validate_port_type: Port is 443

[08/12/16 09:45:42.485 UTC 18 439] pnpa_disc_dhcp_option_43: op43 port 443

[08/12/16 09:45:42.485 UTC 19 439] pnpa_validate_ip_type: op43 iptype ipv4

[08/12/16 09:45:42.485 UTC 1A 439] pnpa_dhcp_discovery:URL[http://192.168.64.18/ca/trustpool]

[08/12/16 09:45:42.509 UTC 1B 439] pnp_validate_ca_bundle_url:CA bundle [http://192.168.64.18/ca/trustpool] not present

[08/12/16 09:45:47.512 UTC 1C 439] pnpa_dns_discovery: Starting PnP DNS discovery

[08/12/16 09:45:47.513 UTC 1D 439] pnpa_disc_dhcp_dns: failed to obtain the domain name

[08/12/16 09:45:47.513 UTC 1E 439] pnpa_dns_discovery:DNS discovery not successful

[08/12/16 09:45:47.513 UTC 1F 439] pnpa_dns_discovery: Starting PnP DNS discovery

[08/12/16 09:45:47.513 UTC 20 439] pnpa_disc_dhcp_dns: failed to obtain the domain name

[08/12/16 09:45:47.513 UTC 21 439] pnpa_dns_discovery:DNS discovery not successful

[08/12/16 09:45:52.513 UTC 22 439] pnpa_cco_discovery: starting CCO discovery

[08/12/16 09:46:01.512 UTC 23 439] pnpa_cco_discovery: Hostname resolution failed

[08/12/16 09:46:01.512 UTC 24 439] pnpa_cco_discovery: starting CCO discovery

[08/12/16 09:46:01.512 UTC 25 439] pnpa_cco_discovery: Hostname resolution failed

[08/12/16 09:46:06.512 UTC 26 439] pnpa_discovery_manager: Starting NAPP

[08/12/16 09:46:06.512 UTC 27 439] pnpa_napp_discovery: starting NAPP discovery

[08/12/16 09:46:06.512 UTC 28 439] set_intf_state_for_napp: Setting interface state for NAPP

[08/12/16 09:46:06.513 UTC 29 439] pnp_pxc_recv_init: enter

[08/12/16 09:46:06.513 UTC 2A 439] pnp_pxc_send_init: pnp_pxc_xmt_process created. listener_pid=213

[08/12/16 09:46:06.513 UTC 2B 166] pnp_pxc_rcv_process: Begin

[08/12/16 09:46:06.513 UTC 2C 166] pnp_pxd_new_workspace: New packet workspace 0x3975CFB8

[08/12/16 09:46:06.513 UTC 2D 166] pnp_pxc_create_recv_socket: enter

[08/12/16 09:46:06.518 UTC 2E 166] pnp_pxc_create_recv_socket: done

[08/12/16 09:46:06.518 UTC 2F 166] pnp_pxc_rcv_loop: enter

[08/12/16 09:46:06.519 UTC 30 213] pnp_pxc_xmt_process: Entering sending loop.

[08/12/16 09:46:06.582 UTC 31 213] pnp_pxc_xmt_loop: str_port_len = 4

[08/12/16 09:46:06.582 UTC 32 213] pnp_pxc_xmt_loop: client_port_no = 1027

[08/12/16 09:46:06.582 UTC 33 213] pnp_pxc_xmt_loop: str_client_ip_len = 7

[08/12/16 09:46:06.582 UTC 34 213] pnp_pxc_xmt_loop: pxy_client_ip = 0.0.0.0

[08/12/16 09:46:06.582 UTC 35 213] pnp_pxc_xmt_loop: String hello = OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP1212:WS-C3850-48POP133:1.0OP144:1027OP157:0.0.0.0

[08/12/16 09:46:06.588 UTC 36 213] pnp_pxc_xmt_loop: sendto returns 97

[08/12/16 09:46:06.588 UTC 37 213] pnp_pxc_xmt_loop: PROXY CLIENT: sent data = OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP1212:WS-C3850-48POP133:1.0OP144:1027OP157:0.0.0.0

[08/12/16 09:47:06.583 UTC 38 213] pnpa_discovery_reset_intf_state: Resetting interface state for NAPP

[08/12/16 09:47:06.583 UTC 39 213] pnp_pxc_rcv_cleanup: setting FAIL discovery

[08/12/16 09:47:06.583 UTC 3A 213] pnp_pxc_xmt_loop - Killing proxy client sending and receiving processes

[08/12/16 09:47:06.584 UTC 3B 213] send_timeout_response: Timeout status response sent for client 'PID:WS-C3850-48P,VID:V03,SN:FOC1751X06Z' : OPRESPSTATUS:OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP123:1.0OP13OPTRANSS19:TRANSACTION TIMEOUTOPSTATUS33:PROXY CLIENT RETRY COUNT EXCEEDEDOPERRMSG75:Proxy client retry count exceeded. Proxy client process is no longer active

[08/12/16 09:47:06.584 UTC 3C 213] create_pnp_pxc_timeout_response_socket: Socket open succeeded

[08/12/16 09:47:06.589 UTC 3D 213] destroy_pnp_pxc_timeout_response_socket: Closing socket

[08/12/16 09:47:06.590 UTC 3E 213] pnp_pxc_xmt_process: Sending loop exited.

[08/12/16 09:47:06.590 UTC 3F 213] pnp_pxc_xmt_cleanup: enter

[08/12/16 09:47:06.590 UTC 40 213] pnp_pxc_xmt_cleanup: Closing socket

[08/12/16 09:47:06.590 UTC 41 213] pnp_pxc_xmt_cleanup: Killing process

[08/12/16 09:47:06.590 UTC 42 439] pnp_wait_on_napp:Received NAPP complete status

[08/12/16 09:47:06.590 UTC 43 439] Info: PnP profile configuration was unsuccessful

[08/12/16 09:47:06.591 UTC 44 439] start_pnpa_discovery: PnP discovery process failed

[08/12/16 09:47:16.592 UTC 45 439] Info: Startup config does not exists

[08/12/16 09:47:16.592 UTC 46 439] start_pnpa_discovery: PnP Discovery trial number[2]

[08/12/16 09:47:16.592 UTC 47 439] start_pnpa_discovery: Initiating PnP discovery manager

[08/12/16 09:47:21.592 UTC 48 439] pnpa_autonomic_discovery: Starting autonomic discovery

[08/12/16 09:47:21.592 UTC 49 439] pnpa_autonomic_discovery: Starting autonomic discovery

[08/12/16 09:47:26.592 UTC 4A 439] pnpa_disc_dhcp_option_43: op43 strict protocol: Yes, must secure: No

[08/12/16 09:47:26.592 UTC 4B 439] pnpa_disc_dhcp_option_43: op43 profile pnp-zero-touch

[08/12/16 09:47:26.592 UTC 4C 439] pnpa_disc_dhcp_option_43: op43 ipaddr 192.168.64.18

[08/12/16 09:47:26.592 UTC 4D 439] pnpa_disc_dhcp_option_43: op43 transport 2

[08/12/16 09:47:26.592 UTC 4E 439] pnpa_disc_dhcp_option_43: transport https

[08/12/16 09:47:26.592 UTC 4F 439] pnpa_validate_port_type: Port is 443

[08/12/16 09:47:26.592 UTC 50 439] pnpa_disc_dhcp_option_43: op43 port 443

[08/12/16 09:47:26.592 UTC 51 439] pnpa_validate_ip_type: op43 iptype ipv4

[08/12/16 09:47:26.592 UTC 52 439] pnpa_dhcp_discovery:URL[http://192.168.64.18/ca/trustpool]

[08/12/16 09:47:26.617 UTC 53 439] pnp_validate_ca_bundle_url:CA bundle [http://192.168.64.18/ca/trustpool] not present

[08/12/16 09:47:26.621 UTC 54 439] pnpa_disc_dhcp_option_43: op43 strict protocol: Yes, must secure: No

[08/12/16 09:47:26.621 UTC 55 439] pnpa_disc_dhcp_option_43: op43 profile pnp-zero-touch

[08/12/16 09:47:26.621 UTC 56 439] pnpa_disc_dhcp_option_43: op43 ipaddr 192.168.64.18

[08/12/16 09:47:26.621 UTC 57 439] pnpa_disc_dhcp_option_43: op43 transport 2

[08/12/16 09:47:26.621 UTC 58 439] pnpa_disc_dhcp_option_43: transport https

[08/12/16 09:47:26.621 UTC 59 439] pnpa_validate_port_type: Port is 443

[08/12/16 09:47:26.621 UTC 5A 439] pnpa_disc_dhcp_option_43: op43 port 443

[08/12/16 09:47:26.621 UTC 5B 439] pnpa_validate_ip_type: op43 iptype ipv4

[08/12/16 09:47:26.621 UTC 5C 439] pnpa_dhcp_discovery:URL[http://192.168.64.18/ca/trustpool]

[08/12/16 09:47:26.645 UTC 5D 439] pnp_validate_ca_bundle_url:CA bundle [http://192.168.64.18/ca/trustpool] not present

[08/12/16 09:47:31.646 UTC 5E 439] pnpa_dns_discovery: Starting PnP DNS discovery

[08/12/16 09:47:31.646 UTC 5F 439] pnpa_disc_dhcp_dns: failed to obtain the domain name

[08/12/16 09:47:31.646 UTC 60 439] pnpa_dns_discovery:DNS discovery not successful

[08/12/16 09:47:31.646 UTC 61 439] pnpa_dns_discovery: Starting PnP DNS discovery

[08/12/16 09:47:31.646 UTC 62 439] pnpa_disc_dhcp_dns: failed to obtain the domain name

[08/12/16 09:47:31.646 UTC 63 439] pnpa_dns_discovery:DNS discovery not successful

[08/12/16 09:47:36.641 UTC 64 439] pnpa_cco_discovery: starting CCO discovery

[08/12/16 09:47:45.644 UTC 65 439] pnpa_cco_discovery: Hostname resolution failed

[08/12/16 09:47:45.644 UTC 66 439] pnpa_cco_discovery: starting CCO discovery

[08/12/16 09:47:45.644 UTC 67 439] pnpa_cco_discovery: Hostname resolution failed

[08/12/16 09:47:50.641 UTC 68 439] pnpa_discovery_manager: Starting NAPP

[08/12/16 09:47:50.641 UTC 69 439] pnpa_napp_discovery: starting NAPP discovery

[08/12/16 09:47:50.641 UTC 6A 439] set_intf_state_for_napp: Setting interface state for NAPP

[08/12/16 09:47:50.641 UTC 6B 439] pnp_pxc_recv_init: enter

[08/12/16 09:47:50.641 UTC 6C 439] pnp_pxc_send_init: pnp_pxc_xmt_process created. listener_pid=213

[08/12/16 09:47:50.641 UTC 6D 166] pnp_pxc_rcv_process: Begin

[08/12/16 09:47:50.641 UTC 6E 166] pnp_pxd_new_workspace: New packet workspace 0x39743170

[08/12/16 09:47:50.641 UTC 6F 166] pnp_pxc_create_recv_socket: enter

[08/12/16 09:47:50.646 UTC 70 166] pnp_pxc_create_recv_socket: done

[08/12/16 09:47:50.646 UTC 71 166] pnp_pxc_rcv_loop: enter

[08/12/16 09:47:50.646 UTC 72 213] pnp_pxc_xmt_process: Entering sending loop.

[08/12/16 09:47:50.646 UTC 73 213] pnp_pxc_xmt_loop: str_port_len = 4

[08/12/16 09:47:50.646 UTC 74 213] pnp_pxc_xmt_loop: client_port_no = 1037

[08/12/16 09:47:50.646 UTC 75 213] pnp_pxc_xmt_loop: str_client_ip_len = 7

[08/12/16 09:47:50.646 UTC 76 213] pnp_pxc_xmt_loop: pxy_client_ip = 0.0.0.0

[08/12/16 09:47:50.646 UTC 77 213] pnp_pxc_xmt_loop: String hello = OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP1212:WS-C3850-48POP133:1.0OP144:1037OP157:0.0.0.0

[08/12/16 09:47:50.651 UTC 78 213] pnp_pxc_xmt_loop: sendto returns 97

[08/12/16 09:47:50.651 UTC 79 213] pnp_pxc_xmt_loop: PROXY CLIENT: sent data = OP1139:PID:WS-C3850-48P,VID:V03,SN:FOC1751X06ZOP1212:WS-C3850-48POP133:1.0OP144:1037OP157:0.0.0.0

=========================END OF OUTPUT=================================

Re: 3850 PnP using DHCP option43

daz_efx_2000 — Tue, 16 Aug 2016 09:20:47 GMT

ok thanks all have managed to get this working with the following string in option 43 with no DNS

"5A;B2;K4;I192.168.64.18;J80"

Re: 3850 PnP using DHCP option43

bsestan71 — Tue, 13 Sep 2016 10:46:43 GMT

Hi,

Is the '1N' missing on purpose or is it just a typo? I am facing some similiar issues.

And does the pnp discovery even go through if there is some configuration present on a switch?

All my devices in my network are reachable and 'managed' but I was expecting them to be also in the unplanned section (I want to do some tests). I have option 43 configured/ with HTTP on my DHCP server and I can see in wireshark that all requests/ack are present.

Thank you in advance for your help!

-B

Re: 3850 PnP using DHCP option43

davidlin# — Wed, 21 Sep 2016 17:11:01 GMT

PnP discovery will not initiate if there is existing configuration on your switch.

1N missing is a typo. For more detail, check solution guide: Solution Guide for Cisco Network Plug and Play - Cisco

First section of option 43 string:

■5A1N;—Specifies the DHCP suboption for Plug and Play, active operation, version 1, no debug information. It is not necessary to change this part of the string.

Re: 3850 PnP using DHCP option43

bsestan71 — Thu, 22 Sep 2016 07:33:28 GMT

Hi David,

It was because of a present startup configuration (even though it was just one inputed line).

The devices are present now in the unplanned device section.. I am wondering if there is some kind of "command" to invoke the pnp discovery process manually?

-B

Re: 3850 PnP using DHCP option43

davidlin# — Thu, 22 Sep 2016 20:59:33 GMT

Hi Belma,

PnP is designed so a default router/switch out of box can contact PnP server without any user input on device side. There is a test command "test pnp discovery process". But this is only for debugging purpose.