Service ControlΒΆ
Services controlled directly by TNSR can be restarted from within the TNSR CLI in configuration mode.
To control a service, use the service command as follows:
tnsr# configure
tnsr(config)# service (backend|bgp|dataplane|dhcp4|ike|ospf|ospf6|restconf|rip|unbound) <action>
tnsr(config)# service (http|ntp|prometheus|snmp|ssh) <namespace> <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)- http
HTTP for RESTCONF API (
nginx)- ike
IKE daemon for IPsec (
charon)- 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)- snmp
SNMP Server (
snmpd)- 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.
- action
The action to take on the service. Must be one of:
- 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. This action is not available for the dhcp4 service.
- reload
Reload the service configuration without restarting. This action is available for the dhcp4 and unbound services.
- 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.