This is the documentation for the 22.02 version. Looking for the documentation of the latest version? Have a look here.
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>
The name of the service to configure. Must be one of:
Configuration backend (
BGP routing (
IPv4 DHCP (
HTTP for RESTCONF API (
IKE daemon for IPsec (
Time service (
OSPF Routing (
OSPF6 Routing (
Prometheus exporter (
RESTCONF API (
RIP Routing (
SNMP Server (
Secure Shell server (
DNS Resolver (
Services which are capable of running in more than one namespace (Networking Namespaces) take the namespace as a second parameter. The namespace can be:
Control the service instance running in the dataplane namespace This service will be reachable on interfaces and addresses managed by TNSR.
Control the service instance running in the host OS namespace. This service will be reachable on interfaces and addresses managed by the host OS.
The action to take on the service. Must be one of:
Start the service if it is not already running.
Stop the service if it is currently running.
Stop and restart the service, or start the service if it is not running. This action is not available for the dhcp4 service.
Reload the service configuration without restarting. This action is available for the dhcp4 and unbound services.
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.