Arista vEOS, Configuration Manual, Page: 69 / 128

File Path Markers Entity
N/A
%EOS-STARTUP-CONFIG-START%
%EOS-STARTUP-CONFIG-END%
EOS CLI configuration file
/mnt/flash/cloud_ha_config.json
%CLOUDHA-CONFIG-START%
%CLOUDHA-CONFIG-END%
Cloud HA configuration file
Note the following regarding the custom-data.
• Markers must be at the beginning of the line.
• The user is expected to have tested the configurations on a live system before using the configurations to deploy
the new vEOS Router. Mis-configuration may result in an unrecoverable instance.
• EOS configuration for all interfaces can be passed in during deployment. The configuration takes effect as the
new instances attach to the vEOS Router.
Sample Instance Custom-Data
Illustrates a sample Instance with custom-data.
%EOS-STARTUP-CONFIG-START%
! EOS startup config
username admin nopassword
username admin sshkey file flash:key.pub
%EOS-STARTUP-CONFIG-END%
Providing Startup-Configuration using Azure Custom-Data
Adding custom-data to an instance.
Currently, custom-data can only be used on instances deployed using the Azure CLI 2.0.
In order to add custom-data to an instance, the custom-data must be provided as a single-line value with
'\n'
delimiting newlines.
Use the
single_line_json.sh
script to convert your custom-data into this format.
#!/usr/bin/bash
cat $1 | python -c 'import json, sys; print( json.dumps( sys.stdin.read()
) )'
Usage of the script is as follows:
./single_line_json.sh user_data.txt
Copy and paste the generated output into the customData value field of the JSON parameters file.
Troubleshooting Instance
To troubleshoot the instance, complete the following steps.
1. Select the resource group containing your vEOS Router deployment from the Resource groups list.
2. Select the item vEOS Router.
69
Using the vEOS Router on Microsoft Azure