Audiocodes, KEMP, Fortinet, Zyxel network device management with Ansible

It uses docker container images and can be deployed on various platforms, here is a CentOS v7.  Once deployed there are containers running tasks, web, Database, queue and cache:

As docker images are maintained by RedHat, you do not need to go deep into how it works, but just profit from nice web GUI and start your development.

So, we want to create a job and template to backup Audiocodes SBC – it will be based on a playbook (YAML ansible code)

The playbook code may look like this:

It opens Audiocodes SBC via REST API with a predefined user (we store credentials in AWX database securely and not in YAML open text) and saves SBC backup ini file in a folder and add timestamp to the filename. The API information from Audiocodes can be found here: https://www.audiocodes.com/media/13528/rest-api-for-mediant-devices-ver-72.pdf

Workflows in AWX

In AWX we can create more complex workflows in a visual way:

Here is example of taking backup and then copying file to a NAS for long term storage and retention. Finally we will schedule this job to run on a monthly basis. In case of job failure we can set system to send email to an administrator.

The same way we can backup KEMP load balancer:

Or Zyxel switches

Fortigate REST API requires firmware 6.x and you can find the required information here: https://docs.fortinet.com/document/fortimail/6.0.4/rest-api-reference

Do not waste your time using fortios_config and FW 5.x – it is not very stable method.

The full power of Ansible is scalability, once you have created a unit code for a function you can multiply its use, delegate operation and manage this way many devices. For production use, you need obviously have isolated  DEV and PROD platforms, keep your playbook is an environment with versioning, etc.