08-09-2017 11:54 AM - edited 03-01-2019 04:40 AM
Hello Experts,
I was trying to provision an ASR901 and ME3600 devices via APIC-EM PnP.
Now, I do know that both are not officially supported (https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Plug-and-Play/release/notes/pnp-release-notes15.pdf) but since both have the pnp protocol support, i thoutht that it might work.
Well, it did not
The ME-3600 reached the DHCP server, pulled an IP address but was not directed to the controller, instead, it was trying to poll the configuration from the DHCP (yes, I saw many threads about that issue... - see CLI output below)
The ASR901 didnt even reach the DHCP. In addition, creating manually pap profile (following Adam's advice - Design Recommendation for APIC-EM Network | Cisco Communities) didn't help (found several pap errors post reload)
So my questions are:
Thanks!
*Aug 7 22:49:39.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Aug 7 22:49:59.615: %SYS-5-RESTART: System restarted --
Cisco IOS Software, ME360x Software (ME360x-UNIVERSAL-M), Version 15.3(1)S2, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 30-Apr-13 20:17 by prod_rel_team
*Aug 7 22:50:01.547: %PM-4-ERR_DISABLE: gbic-invalid error detected on Te0/1, putting Te0/1 in err-disable state
*Aug 7 22:50:01.575: %LICENSE-1-REQUEST_FAILED: License request for feature 10GEUpgrade 1.0 failed. UDI=ME-3600X-24FS-M:FOC1722X48A
*Aug 7 22:50:02.783: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*Aug 7 22:50:03.783: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*Aug 7 22:50:24.527: AUTOINSTALL: GigabitEthernet0 is assigned 8.20.0.194 -> IP assingment from DHCP
*Aug 7 22:50:24.527: AUTOINSTALL: Obtain siaddr 8.20.0.207 (as config server) -> Wrong config server.. (8.20.0.207 is the DHCP server not the controller)
*Aug 7 22:50:31.783: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
%Error opening tftp://8.20.0.207/network-confg (Timed out)
%Error opening tftp://8.20.0.207/cisconet.cfg (Timed out)
%Error opening tftp://8.20.0.207/router-confg (Timed out)
%Error opening tftp://8.20.0.207/ciscortr.cfg (Timed out)
08-09-2017 12:48 PM
We have evolved the PnP protocol quite a lot over the last 2 years.
Older products that are not officially supported will not have these enhancements.
There are some interesting interactions with Vlans, etherchannels, DHCP startup, certificates etc, bootstrap configs etc. We have also added capabilities like PnP Connect (cloud redirect) and trust-bundle verification.
The best way to get PnP support is to make a request from the product management team for the platform.
I would not recommend using older unsupported versions as you will definitely find issues.
Adam
08-09-2017 01:14 PM
Thank you Adam!
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