The following output is an example of provisioning file information.
dns {
primary 192.0.2.1
secondary 192.0.2.2
tertiary 192.0.2.3
domain sample.domain.com
}
download {
image "cf3:/both.tim" {
primary-url "http://192.168.40.140:81/both.tim"
secondary-url "http://192.168.40.140:81/both.tim"
tertiary-url "http://192.168.40.140:81/both.tim"
}
image "cf3:/support.tim" {
primary-url "http://192.168.40.140:81/support.tim"
secondary-url "http://192.168.40.140:81/support.tim"
tertiary-url "http://192.168.40.140:81/support.tim"
}
config "cf3:/config.cfg" {
primary-url "ftp://ftpserv:name@192.168.194.50/./images/dut-a.cfg"
secondary-url "http://192.168.41.140:81/dut-a.cfg"
tertiary-url "http://192.168.42.140:81/dut-a.cfg"
}
file "cf3:/license.txt" {
primary-url "ftp://ftpserv:name@192.168.194.50/./images/provision_example.cfg"
secondary-url "http://192.168.41.140:81/dut-a.cfg"
tertiary-url "http://192.168.42.140:81/dut-a.cfg"
}
}
bof {
primary-image cf3:/both.tim
primary-config cf3:/config.tim
address 192.168.100.1 active
autonegotiate
duplex full
speed 100
wait 3
persist off
console-speed 115200
}
For an HTTPS URL, the trust anchor needs to be referenced in the provisioning file. The trust anchor name references the entry in the import>trust-anchor section of the file. In the following example, the trust anchor name is TRUST_ANCHOR.
import {
client {
cert "cf3:/client.crt" {
format pem
primary-url http://10.10.10.67:81/client.crt
}
key "cf3:/client.key" {
format pem
primary-url http://10.10.10.67:81/client.key
}
}
trust-anchor TRUST_ANCHOR{
cert "cf3:/ca.crt" {
format pem
primary-url ftp://user-name:password@10.10.10.66//user-name/logs/
fileserver-4/ca.crt
}
crl "cf3:/ca.crl" {
format der
primary-url ftp://user-name:password@10.10.10.66//user-name/logs/
fileserver-4/ca.crl
}
}
}
<snip>
download {
config "cf3:/ztp/ztp_dut-a.cfg" {
primary-url "https://10.10.10.64:81/ztp_dut-a.cfg"
primary-trust-anchor "TRUST_ANCHOR"
}