Device showing offline in Security Director

In Network Management Platform at Device > Device Management, the device looks Down in the  Connection Status column.

This causes issues when managing the device from the Web Gui console of  Junos Space or Security Director

Device appears Down in the  Connection Status column in the Network Management Platform at Device > Device Management

Device Authentication Modes in Junos Space Platform:

1. Credentials-Based Authentication: Ensure that device login credentials are properly configured in Junos Space. You can modify or reenter the credentials by navigating to: Devices > Device Management > right-click any column > Device Access > Modify Authentication.

2. Key-Based Authentication: The device may become unreachable if keys are modified, and the authentication status may change to "Key Conflict." Use the "Resolve Key Conflicts" workflow to manually trigger the process of uploading new keys to these devices. Navigate to: Devices > Device Management > right-click any column > Device Access > Resolve Key Conflict.

3. SSH Fingerprint-Based Device Authentication: Junos Space Platform stores the SSH fingerprint of the device in the database and validates the fingerprint during subsequent connections. If the fingerprint on the device does not match the fingerprint stored in the Junos Space Platform database, the connection will be dropped. The connection status will be displayed as "Down" and the authentication status as "Fingerprint Conflict" on the Device Management page.

Device Connectivity Check:

Ensure the following prerequisites are met regarding device connectivity before rediscovering the device:

1. The IP address of the device should be reachable via ICMP, PING, and SSH from your Junos Space Platform CLI.

2. When the eth3 interface is configured as a device management interface, Junos Space Platform does not forward ICMP packets through the eth3 interface. To allow ICMP packets through this interface, routes must be added manually. If the managed devices are not reachable through the default gateway configured for the eth3 interface, you must configure static routes for the eth3 interface.

3. Ensure SSHv2 is enabled on the device (use the command set system services ssh protocol-version v2), and any firewalls along the way should allow Junos Space to connect to the SSH port (default TCP/22) on the device.

4. If there is an issue with the TCP/22 port, a DMI session will not be established between Junos Space and the device. This DMI session typically operates on top of an SSHv2 connection with the device.

Once all the above prerequisites are satisfied, you can delete and rediscover the device in the Junos Space Platform.