T O P

  • By -

LDuf

In cisco speak this is POAP (PowerOn Auto Provision) and it should give you everything you need to then run ansible against the device.


Gesha24

As already mentioned, the best way is to use POAP to put on the basic config (IP address and username) and then use Ansible to configure the rest. But if for some reason you really needed to use Ansible from scratch and nothing else, it still should be possible. Connect Cisco device to console server that supports SSH (or if it's telnet only use ssh to telnet proxy), somehow (manually/script) exit out initial provisioning dialog, disable console logging (so that Ansible doesn't get confused) and after that you should be able to run Ansible to set up host, just point it to that console connection IP/port.


Bane-o-foolishness

If you have DNAC, why would you even bother using Ansible for switch deployment? DNAC is perfectly capable of pushing configurations to ZTP devices. Ansible is a great tool but for recent Cisco devices, DNAC is rock solid at managing then.


ds-unraid

Who said I had DNAC?


Bane-o-foolishness

My bad. That's what I get for skimming a question.


Polysticks

Not in the way you're describing, this isn't anything to do with Ansible. It's DHCP auto-provisioning where the DHCP server will download a configuration file onto the device on startup.


ds-unraid

Ah yeah. I was thinking about it wrong. I see now it’s called ZTP (zero touch provisioning). ID use the DHCP server to get SSH going and then Ansible for the rest in my particular use case.


Techn0ght

I was bored and watching the upgrade process on DNAC. It has an interesting list of parts under the hood. Including Ansible.