How to set DNA Center IP on a switch without DHCP or DNS

[EddyFonseca3815]

I would like to know how I can add the DNA center IP to a Switch so it can call DNA center and I can anchor to a site.  I have environment were I might not have access to DHCP option 43 or DNS A-record so is there a way I can add to a set or config line where I can enter the DNA center IP and let the switch reach out to the controller.

I understand we can do it to can console into an AP and set the Primary or secondary controller with a simple command.  If there is a way I can do the same for DNA on a switch I would like to understand the commands.

Thank you

Eddy

[Preston Chilcote]

It's not clear to me if you're asking about a brand new switch without any config, or a brownfield switch with an existing config.  DHCP option 43 or DNS queries for pnpserver.<domain> are used for PnP where there is no config on the switch at all and we want to onboard it.

 If your switch has a config, then you simply need to discover the device from Cisco DNA and assign it to a site.  Those steps will take care of configuring the SNMP and logging for the switch to give Cisco DNA the telemetry it needs.

[EddyFonseca3815]

This is a New Install but no DHCP or DNS option are available at this time.  I will config the switch with IP address on vlan 90 and need to have the switch call DNA center.  I located a PNP agent document that allows we to enter a http ip address of DNA center but it also asks for port and interface.  It did not explain why it needs the port or interface.  I would assume the transport http ipv4 <ip_add-DNA> is all I need as long as the switch IP has a default gateway and IP and it can ping DNA, it should send a request and add the switch into inventory on DNA Center. 

I also would like to know what is the command to run the PNP script on the switch without the reload option. If this agent can be run from CLI that can help me tell if it reg the switch on DNA works or not.

thank you

Eddy

[Preston Chilcote]

I don't think PnP is the right solution for what you are trying to do.  If you have to statically assign an IP address, that's fine, but it means you will lose the benefits of being able to do a true zero touch deployment.  So, think about doing this without PnP.  Give the switch enough information so that DNA is reachable (has a route), discover the device from Cisco DNA, then use the day-N provisioning tools in Cisco DNA to do the rest of the config. That will still let you manage your site or network's standard config in a centralized place and automate a large majority of your network configuration.

[EddyFonseca3815]

 Thank you for the information and suggestion that is helpful but I would still like to use PNP in this very large environment.  I can get DHCP to provide IP to the switch but config options to each dhcp scope is not an option or available to me.  So if I can get the Switch to get Default route, IP address, DNS information then I can plug in a usb device to each switch I rack and stack to get it to call home via cli and I do not have to enable discovery on DNA. The device will already be reg with DNA and I just have to assign it to a site/building/floor on the map and push the configs to it as they come in. This also helps with the amount of Switches that are reg with DNA. I can control the reg of each device and locations since I will have each device reg separately to DNA.  

Note since vlan 1 is not enable on this network I have to change the vlan pnp will use to access the network. I have to touch each device anyway, this allows me what is reg and what is not.

I hope I have given you somewhat of a view how I would like to use DNA center to install , inventory and control the network I am in.

Thank you

Eddy

[Preston Chilcote]

Ok, if you can get DHCP but can't use option 43, then you can use your own DNS server or PnP Connect (in Cisco's Cloud) to help tell the new switch where the DNA is.  Then you won't need a USB or any manual config.  There isn't a way to trigger PnP from the switch side once any manual config is done. The goal is to claim the device from the Cisco DNA GUI.  It's perfectly fine to have some switches that DNA knows about (from this PnP process) but not claimed and managed.

If you haven't talked to your sales team, you should ask them to put you in touch with your Cisco Customer Success representative (or DM me your .  They can help train you on more details.

If you can't use Vlan 1, you can configure upstream switch interface with "pnp starup-vlan X" to tell PnP on the new switch which vlan to use, so no manual config is needed for that either.

[Goncalo.Contente]

Hi,

PnP relies on DHCP or DNS to be able to contact the DNAC. If you cannot use this options perhaps you could try the other way around. As long as the switch as an IP address and a DF route you can use the discovery option in DNAC to find the switch.

HTH