ztp->bootstrap->basic configuration via a yaml

[guateton]

I'm using ZTP/CVASS/AVD 5.0, would it be possible for bootstrap.py to call up a yaml file to a basic config on switches, and then drop them into the Undefined or some other container.

documentation on that?

[ClausHolbechArista]

Hi @guateton
I am not sure exactly why you want this. Can you elaborate a bit on your use-case?

Answering with some background which may help:

• It is not possible to use AVD-based configs during ZTP itself. It is possible to onboard devices with a full AVD config, but they have to be registered to CloudVision first using regular ZTP.
• Normally you would not want any config on the device while it is in the ZTP state. EOS will behave differently if you put on a config, as it will exit ZTP mode.
• While in ZTP mode EOS will reboot and retry in certain intervals, which is great to recover from intermittent issues. If you put a config on the device you may leave it in a state where you cannot recover it remotely.

[guateton]

Normally, we let ZTP do it's thing, resulting in switches being placed in the Undefined container, we then "manually":

1. Logon to CVAAS
2. Manually move them from the Undefined container, into a container with basic config configlet's
3. They receive a base config (i.e. MGMT IP, local username+password)
4. Then we run AVD to configure

Any recommendations, how to remove some of these steps? Could we skip the UNDEFINED container have them placed in our in house container?

[ClausHolbechArista]

As you may know, CloudVision is migrating from the "Network Provisioning" page to "Studios". AVD currently supports both, but I strongly recommend moving the AVD configs to "Studios", specifically the "Static Config Studio", since we will deprecate the AVD integration to "Network Provisioning" some time in the near(ish) future.

1. With Network Provisioning you can use the Ansible role arista.avd.eos_config_deploy_cvp. It will move the devices automatically from the undefined container and apply the full AVD config on those devices. So you only need step 4 from your list.

2. With Static Config Studio you instead use the Ansible role arista.avd.cv_deploy. It will not move the devices out of the "Undefined" container in the old privioning, instead it will onboard the devices into the Inventory and Topology Studio and add their configs in Static Config Studio. So again you only need step 4 from your list.

I suggest you work with your Arista account team to discuss the options and maybe have them demonstrate the different methods.