Tip

This is the documentation for the 19.02 version. Looking for the documentation of the latest version? Have a look here.

orphan:

Starting TNSR

The services required by TNSR to run are enabled by the installer, and they will automatically start at boot time. There is no need to manually stop or start TNSR services during normal operation.

TNSR Service Relationships

TNSR requires the vpp, clixon-backend, and clixon-restconf services.

The clixon-backend service is configured to depend on vpp, thus:

• If the vpp service is restarted, clixon-backend will also restart if it is running.

• If the vpp service is stopped, clixon-backend will stop if it is running.

• If both vpp and clixon-backend are stopped, then starting clixon-backend will also start vpp.

Note

TNSR may require additional services depending on features enabled by the TNSR configuration. These will be automatically managed as needed.

Manual TNSR Service Operations

Stop TNSR services:

$ sudo systemctl stop vpp clixon-restconf

Start TNSR services:

$ sudo systemctl start clixon-backend clixon-restconf

Restarting TNSR services if they are already running:

$ sudo systemctl restart vpp clixon-restconf

These services are all daemons and not interactive. To configure TNSR, the administrator must initiate the TNSR CLI separately, as described in Entering the TNSR CLI.

Convenience Alias

For convenience, an alias in the shell can be used to handle this task. For example, the following single line can be added to ~/.bashrc:

alias restarttnsr='sudo systemctl stop vpp clixon-restconf;
   sudo systemctl start clixon-backend clixon-restconf'

Note

The changes to ~/.bashrc will not take effect immediately. Either logout and login again, or source the file by running source ~/.bashrc or . ~/.bashrc.

The above actions can then be accomplished all at once by running restarttnsr.