Automatic Deployment and Configuration


This feature requires version 1.9.0 or later

This section contains information related to the automatic deployment and configuration features on the ExaLINK Fusion.

The automatic deployment and configuration functionality allows a user to setup their network in such a way that new Fusion devices added to that network will query a DHCP server to download and execute a script defined by the user. Executing this script means a user can configure or communcaite to and from the Fusion remotely at the time of deployment.

Displaying Automatic Configuration State

When inspecting the Fusion the show auto-config command can be invoked to see the current enabled or disabled state of the automatic configuration functionality.

For Fusion devices the initial empty configuration should look as follows:

[email protected]> show auto-config
Automatic startup configuration enabled


Newly purchased Fusion devices will have this feature enabled to allow for streamlined deployment. Once configured or if not desired a user can disable this feature.

Configuring Automatic Configuration

First enter configuration mode of the Fusion.

[email protected]> configure

When in configuration mode a user can enable this feature with the auto-config enable command.

[email protected](config)> auto-config enable
Enabled auto-configuration

To disable this feature

[email protected](config)> auto-config disable
Disabled auto-configuration


[email protected](config)> no auto-config
Disabled auto-configuration

Running show auto-config will now show it is in the disabled state

[email protected]> show auto-config
Automatic startup configuration disabled

The automatic configuration feature will only execute when the Fusion is connecting to a DHCP server (which is the factory default mode). This can either happen at start up or when the user configures the Fusion for DHCP mode. To do this run management address dhcp

[email protected](config)> management address dhcp
Enabled DHCP on management interface

Remember to save the running configuration to the startup configuration if you want these settings to take remain over a reboot.

[email protected](config)> copy running-config startup-config
Saved running config to startup config
Configuring a DHCP Server

If desired when a DHCP client starts, and after it receives a DHCPOFFER response from a DHCP server, the client can communicate directly with a boot server (instead of the DHCP server) to download a boot file.

The Fusion auto-config feature relies on this behaviour, that is its DHCP client being able to contact a DHCP server on a local LAN. The DHCP server can then be configured to provide a boot file address to the Fusion. The Fusion will fetch this file and apply it once downloaded. Note the boot file may have various names depending on the DHCP server e.g. boot-file, filename etc

Example script for dhcpd

# DHCP Server Configuration file.
option domain-name "";
default-lease-time 600;
max-lease-time 7200;
log-facility local7;

filename "";

subnet netmask {

The Fusion can download a boot file via HTTP:

filename "";

or TFTP:

filename "tftp://";


When downloading via HTTP boot file names should use HTTP encoding for special characters such as spaces. For example:

filename "";

Example script files

The script files will execute as if executed by the admin user on the Fusion. Therefore can operate standard tools like ip a, journalctl or Fusion tools such as cli. Calling cli allows execution of commands from bash that you would normally execute through the Fusion command line interpreter (cli)

A simple bash example to configure basic management details:

cli -c 'configure management name-server'
cli -c 'configure hostname MYFUSION'
cli -c 'configure timesync gps'
cli -c 'configure copy running-config startup-config'

A simple bash example to configure the data path:

cli -c 'conf patch A1 A2'
cli -c 'conf tap B1 B15'
cli -c 'conf tap B1 B16'
cli -c 'conf copy running-config startup-config'

A bash example configuring remote logging and snmp and then turning off auto-config once complete:

cli -c 'conf snmp read community public'
cli -c 'conf snmp enable'
cli -c 'conf remote-logging target udp my-logging-server all all'
cli -c 'conf remote-logging enable'
cli -c 'conf auto-config disable'
cli -c 'conf copy running-config startup-config'

A Python example utilising the Fusion API which fetches a firmware update and applies it:


# Example python script for running on Fusions
# Uses python bindings for the Fusion API
# Refer to for full API details

import exalink

exalink.set_management_address_ipv4(mode="static", static={"address":"","netmask":"", "gateway":""})
exalink.update_tftp(server="", file="exalink_fusion_1.9.0.tar")
# note that when update_tftp() completes it will automatically reboot the box

A Python example configuring the data path:


import exalink

exalink.create_tap(port="A16", src_port="A10", direction="input")
exalink.create_object(type="mux", name="my_mux", mode="layer2")
exalink.add_object_port(object={"type":"mux","name":"my_mux"}, port="B1", side="up")
exalink.add_object_port(object={"type":"mux","name":"my_mux"}, port="B10", side="down")

This page was last updated on Oct-13-2018.