Network Device Onboarding (switching C9300) using Plug and Play (PnP) with Cisco DNA Center
Вставка
- Опубліковано 25 вер 2022
- In this video I'll be demoing the Plug-and-Play (PnP) feature in Cisco DNA Center for switching.
If you have any questions feel free to drop them in the comment section or reach out directly to me in LinkedIn.
Apologies I had misconfigured the screen recording tool and I cropped too much of the top and bottom parts of the screen. The content can still be seen however, some buttons I'm clicking particularly at the very top left or bottom left can't be seen.
Great work sir. Thank you.
Nice work!
Have you tried using the DNS Discovery method with the PnP agent, and if so, do you have any insights on the best way to set it up please?
Hi, yes I've tried that and works fine. I just prefer the option 43 as it's quick and easy. For DNS you have to include the domain in your DHCP offer. The device will then look for PNPSERVER.domain.com, you can see more in the user guide: www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center/2-3-7/user_guide/b_cisco_dna_center_ug_2_3_7/m_onboard-and-provision-devices-with-plug-and-play.html#id_90879
Pablo this is excellent and well explained video. Thanks for sharing.
Glad it was helpful!
@@pabmart I haven't tried it yet but I hope I will get this scenario soon.
I have L3 SVI for vlan 10 on my router and expect switch to get connected with it using a routed interface (no vlan on switch, just like a P2P configuration). Will this dhcp part work with this scenario ?
@@vaibhavbhosle6511 You will need VLAN 1 subinterface on the upstream router and provide the DHCP on that vlan. PNP Agent works on VLAN 1 by default.
You can remove VLAN 1 once PNP has finished and your device has been fully provisioned with desired config.
@@pabmart Can this PnP method be used for deploying Fabric edge switches as well ? What about smart licensing will there be any issue if choose deploying using PnP instead of LAN Automation
Thnx@@pabmart
Hi Pablo very informative video, can you also upload the templete configuration just for the referece thanks
Hi, glad to hear.
The template is adapted to my lab environment, there is nothing exceptional in it. Some of the things I've put:
username/pass/secret (so DNAC can use that once provisioned), enable ip routing, hostname, ssh v2, some vlans, enable netconf, loopbacks and L3/L2/Trunk physical interfaces, a static route, line console, line vty. That's pretty much it. It's just the very basic setup to allow DNAC to reach, and take over it via GUI.
Where did you configure the DHCP server in the topology diagram?
At the Fusion device.
@@pabmart when you do a Pnp service restart in pnp agents, it will automatically do the discovery to the fusion device?
Also, don’t you have to configure the interface where the discover message goes to in DNAC?
@@estebangomez1823 Hi, no config needed in the device to be discovered. Just let it boot into out of the box state, where it runs a PNP agent. The agent will try to get an IP address and Default GW along with Option 43 via DHCP from any interface in UP status. Ideally, that will be the interface connecting upstream (to the Fusion in this case). It will use that configuration to reach out to DNAC. You have to make sure reachability is there between PNP device and DNAC (now known as Catalyst Center). Hope it helps.