Service Control¶
Services controlled directly by TNSR can be restarted from within the TNSR CLI.
To control a service, use the service command as follows:
tnsr# service (backend|bgp|dataplane|dhcp4|dhcp|ike|isis|ospf|ospf6|restconf|rip|unbound) <action>
tnsr# service (ntp|prometheus|rsyslog|snmp|ssh) <namespace> <action>
tnsr# service (dhcp4-host|dhcp6-host) <interface> <action>
tnsr# service snort <instsance> <action>
- name:
The name of the service to configure. Must be one of:
- backend:
Configuration backend (
clixon_backend)- bgp:
BGP routing (
bgpd,zebra)- dataplane:
Dataplane (
vpp)- dhcp4:
IPv4 DHCP (
kea)- dhcp4-host, dhcp6-host:
DHCP clients for host interface (
dhclient)- ike:
IKE daemon for IPsec (
charon)- isis:
IS-IS routing daemon (
isisd)- ntp:
Time service (
ntpd)- ospf:
OSPF Routing (
ospfd,zebra)- ospf6:
OSPF6 Routing (
ospf6d,zebra)- prometheus:
Prometheus exporter (
vpp_prometheus_export)- restconf:
RESTCONF API (
clixon_restconf)- rip:
RIP Routing (
ripd,zebra)- rsyslog:
Remote System Logging (
rsyslogd)- snmp:
SNMP Server (
snmpd)- snort:
IDS/IPS daemon (
snort)- ssh:
Secure Shell server (
sshd)- unbound:
DNS Resolver (
unbound)
- namespace:
Services which are capable of running in more than one namespace (Networking Namespaces) take the namespace as a second parameter. The namespace can be:
- dataplane:
Control the service instance running in the dataplane namespace This service will be reachable on interfaces and addresses managed by TNSR.
- host:
Control the service instance running in the host OS namespace. This service will be reachable on interfaces and addresses managed by the host OS.
- interface:
Services which have separate processes for each interface take the interface name as second parameter.
- instance:
Services which have separate processes for each instance take the instance name or ID as second parameter.
- action:
The action to take on the service. Available actions vary by service.
Possible actions include:
- start:
Start the service if it is not already running.
- stop:
Stop the service if it is currently running.
- restart:
Stop and restart the service, or start the service if it is not running.
- reload:
Reload the service configuration without restarting.
- status:
Show the current status of the service daemon(s) and the last few log entries.
- coredump (enable|disable):
Enable or disable core dumps, which are generated if the service encounters a problem. See Diagnosing Service Issues.
Note
The
restconfservice usestrueandfalseinstead ofenableanddisable.