Apstra ZTP - Arista
Arista EOS
Apstra ZTP has limited support and known issues for virtual Arista EOS (vEOS) devices.
- ZTP EOS upgrades are not supported on vEOS devices. EOS versions for vEOS
device must match
eos-versionsset inztp.jsonfile. - ZTP Logging to the controller does not work for vEOS devices due to the lack of a device serial number. This will be addressed in a future version.
As part of the ZTP process a new OS image is copied to the switch. Before installing Apstra ZTP ensure that the switch has sufficient disk space for the OS image.
switch1#dir flash: Directory of flash:/ <...> 3957878784 bytes total (3074723840 bytes free)
If ZTP is installing Arista EOS image, the image (EOS-4.22.3M.swi for example) you
must copy to the /containers_data/tftp directory.
Example: Arista EOS - ztp.json
Arista EOS On-box Agent / Apstra ZTP 4.0
{
"eos": {
"eos-versions": [ "4.24.5M" ],
"eos-image": "http://192.168.59.3/EOS-4.24.5M.swi",
"custom-config": "eos_custom.sh",
"device-root-password": "admin-password",
"device-user": "admin",
"device-user-password": "admin-password",
"system-agent-params": {
"agent_type": "onbox",
"job_on_create": "install"
}
}
}Arista EOS Custom Config File
When configuring custom-config for Arista EOS devices, refer to the
example eos_custom.sh, a bash executable file executed during the
ZTP process. It can execute EOS configuration commands to set the SSH login banner
or other system configuration to be set prior to device system agent
installation.
#!/bin/sh FastCli -p 15 -c $'conf t\n service routing protocols model multi-agent\n hardware tcam\n system profile vxlan-routing\n banner login\n ######################################################## UNAUTHORIZED ACCESS TO THIS DEVICE IS PROHIBITED ########################################################\n EOF\n'
During the ZTP process, the EOS banner login is set to text saying "The device is in Zero Touch Provisioning mode ...". By default, the ZTP script copies this to the permanent configuration.
To prevent this, you must configure the custom-config
pointing to a script (eos_custom.sh for example), which
configures a different banner login or configure no
banner login.
There must be a space after any \n.
If you're using EOS 4.22, Apstra recommends adding the service routing
protocols model multi-agent to the device configuration along with
any other configuration during ZTP which requires a device reboot to activate
(system profile vxlan-routing for example). This ensures
that this configuration is applied on reboot and added to the device pristine
configuration.
Restart Arista EOS ZTP
If an agent is already installed on the device, before you restart the device ZTP process remove the agent extension either via the UI Device Agent Installer or manually via the device CLI.
l2-virtual-001-leaf1#sho extensions Name Version/Release Status Extension ----------------------------------------- ------------------ --------- --------- aos-device-agent-3.1.0-0.1.205.i386.rpm 3.1.0/0.1.205 A, I 1 A: available | NA: not available | I: installed | NI: not installed | F: forced l2-virtual-001-leaf1#delete extension:aos-device-agent-3.1.0-0.1.205.i386.rpm l2-virtual-001-leaf1#no extension aos-device-agent-3.1.0-0.1.205.i386.rpm l2-virtual-001-leaf1#copy installed-extensions boot-extensions Copy completed successfully. l2-virtual-001-leaf1#delete /recursive flash:aos* l2-virtual-001-leaf1#
See Arista Device Agents for more information.
To restart Arista EOS ZTP process:
localhost# delete flash:zerotouch-config localhost# write erase Proceed with erasing startup configuration? [confirm]y localhost# reload