Remote Management Data and Test Results

Displays the date and time when the device successfully established an outbound SSH session with Routing Director or when the session got terminated. Hover over the timestamp to view the possible states. The states are:

• Connected: The device has established an outbound SSH session with Routing Director.

  The connected state is also Indicated by a green circle with a white tick.

• Disconnected: The outbound SSH session that the device established with Routing Director is terminated.

  The disconnected state is also indicated by a red circle with a white cross.

Displays the date and time when the system log message from the device was last received by Routing Director. Hover over the timestamp to view details on the latest system log generated by the device. The details displayed are:

• Severity—Severity level of the log message. The levels can be:

  • Critical

  • Error

  • Warning

• Timestamp—Date and time when the device generated the system log message.

• Appname—Application on the device that generated the log message.

• Raw Message—Unprocessed system log message generated by the device. The unprocessed message contains additional log information such as, date and time when the message was generated, process and the ID of the process that generated the log message, and the device that generated the log message.

• Org ID—Identifier of the organization to which the device belongs.

• Host—Host name of the device.

• Message—Processed message sent by the device, without any additional log information.

Click the timestamp link to view additional details about all system logs generated in the organization from the Device Logs tab on the Events page (Observability > Health > Events > Device Logs).

• Device—Name of the device that generated the alarm.

• Description—Description of the latest alarm raised on the device.

• Last Received Time—Date and time when the latest alarm notification was received from the device.

Click the timestamp link to view additional details about all alarms generated in the organization from the Alarms tab on the Events page (Observability > Health > Events > Alarms).

Displays the date and time when the device successfully established or terminated a gNMI session with Routing Director. Hover over the timestamp to view the possible states. The states are:

• Connected: The device has established a gNMI session with Routing Director.

• Disconnected: The gNMI session that the device established with Routing Director got terminated.

Displays whether the connection between the device and the NTP server is synchronized or not. The states are:

• Synchronized: The device clock and the NTP server are synchronized.

• Not Synchronized: The device clock and the NTP server are not synchronized.

Click the link to view detailed history of synchronization between the NTP server and the device clock. The details displayed are:

• Time—Date and time when the synchronization between the device and the NTP server was last tested.

• Reference—IP address of the NTP server used as reference for synchronizing the clock on the device. If the IP address is unknown, then the field displays 0.0.0.0.

• Status—Details about the synchronization including leap second measure, the current synchronization state, and so on.

  For more information about the NTP status, see Show NTP Status.

• Time Offset—Difference in time between the NTP server and the device, before synchronization.

You can release a device when:

• The device is no longer in use.

• You want to reuse the device in another role or in another network.

• You want to replace the device with another device.

You can release a device by:

• Clicking Release Device in this accordion or the Inventory page (Inventory > Devices > Network Inventory). You must be a user with the Super User role to release a device from this accordion.

  When you release a device by using this option, all the device configurations are retained on the device but the outbound SSH configuration on the device is deleted. Without the outbound SSH connection, the device is disconnected from Routing Director. You must manually delete the device configurations.

• You can also release a device by removing the device from the Network Implementation Plan (Inventory> Device Onboarding > Network Implementation Plan). When you release a device by using the network implementation plan, all the device configurations that were committed on the device through the plan are deleted, but the outbound SSH connection is retained. You must manually delete the outbound SSH configuration.

  Alternatively, if you want to release all the devices that are part of the plan, you can delete the Network Implementation Plan (known as offboarding) that is used to onboard and manage the devices.

  Note:

  Deleting a Network Implementation Plan impacts all the devices that are part of the plan.

  For more information about releasing devices by using a Network Implementation Plan, see Offboard a Network Implementation Plan.