ZTP Advantages/Disadvantages

ZTP is a system in which devices such as white Box switches are connected to the network in which they are to be installed, and once they are turned on, they are automatically configured and ready to use.
The advantages and disadvantages of ZTP alone are as follows:

[merit]
・Because the setting is simple, it is not difficult to build a ZTP environment

[Demerit]
・It is necessary to create Config for each white Box switch in advance
・If there is no mechanism to automatically correct any changes to the initial settings, it is necessary to manually correct all Configs.

The construction of the ZTP environment itself is not difficult, but it is necessary to prepare Config for each white Box switch, and the larger the number, the more time it takes to prepare manually.

For more details about ZTP, please see the fourth article, which provides a detailed explanation.

Eliminate the disadvantages of ZTP with ZTP x Ansible

By combining ZTP with Ansible, you can automate the creation of configs themselves, significantly reducing the amount of work required.
We will explain the basic steps using ZTP and Ansible.

① Apply the config of each white Box switch with ZTP (config is created with Ansible)
② When changing settings, you can change the settings in real time by editing/executing the playbook on the Ansible host (useful when applying the same settings to many switches).
③ Using the Ansible host, you can periodically back up the configuration of each device.
※ Playbook is a file that describes the process to be executed.

This makes configuration creation and changes more efficient and simplifies management.
There is a learning cost to Ansible, but once you have learned it, subsequent operations will be very smooth.

How to create a config using AnsibleArticle 3We have provided a more detailed introduction, so please take a look if you are interested.

Ansible directory structure

├── hosts # inventory file
│
├── set_crontab.yml # Playbook file to execute
│
└── backup.yml # Playbook file executed by cron job

Set the playbook (set_crontab.yml) as below and create a script that executes the cron job (backup.yml) every minute.

set_crontab.yml

---
- hosts: localhost
  gather_facts: false
  tasks:
    - name: set crontab
      cron:
        name: backup_config
        job: "/usr/bin/ansible-playbook -i ~/Ansible/ocnos-bgp-ansible/hosts  ~/Ansible/ocnos-bgp-ansible/backup.yml

---
- name: Buck up running-config
  gather_facts: no
  hosts: OCNOS
  vars:
    now_date: "{{ lookup('pipe','date +%Y%m%d%H%M') }}"
  tasks:
    - ocnos_config:
          exec_cmds:
                - 'copy running-config scp scp://tecstar:tecstar@192.168.0.80/tmp/configs/{{ inventory_hostname }}_bk.conf.{{ now_date }} vrf management'

Execute Playbook commands with Ansible

By executing the playbook (set_crontab.yml) from the command below, the regular backup setting is completed.

ansible-playbook set_crontab.yml

After running the playbook, make sure your crontabs are set correctly.

コマンド実行
#Ansible: backup_config
* * * * * /usr/bin/ansible-playbook -i ~/Ansible/ocnos-bgp-ansible/hosts  ~/Ansible/ocnos-bgp-ansible/backup.yml　　---->正常に設定されていることが確認できる-->tecstar@tecstar:~$ crontab -l　　　　----->コマンド実行 #Ansible: backup_config * * * * * /usr/bin/ansible-playbook -i ~/Ansible/ocnos-bgp-ansible/hosts ~/Ansible/ocnos-bgp-ansible/backup.yml　　---->正常に設定されていることが確認できる

Also, as shown below, Config is actually acquired every minute, and it can be confirmed that it is operating normally.
(This time, the file name has a time stamp, and the backup was taken at 16:53, 16:54, 16:55, and 16:56)

tecstar@tecstar:/tmp/configs$ ls AS7726-A_bk.conf.202107191653 AS7726-A_bk.conf.202107191654 AS7726-A_bk.conf.202107191655 AS7726-A_bk.conf.202107191656

That was the introduction of the automation solution using ZTP and Ansible.
Next time, we plan to introduce monitoring/visualization methods using OSS tools.

These people are using the remote verification service.

Here are some testimonials from people who have actually used the service.

 

Furukawa Network Solution Co., Ltd.

“Recently, the number of remote service environments is increasing, but I was impressed with the ease of access to the evaluation equipment.

The materials you provided were easy to understand, and we were able to proceed smoothly with the intended verification. ”

Related information

How to automatically configure white Box switches using Ansible for beginners

How to automatically configure white Box switches using Ansible for beginners part 2

Automated construction and configuration of white Box switches that even beginners can do ~ZTP x OcNOS~