Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Edit Device Details

Use this topic to edit the details of a device in inventory.

Details of a device in the inventory such as the device name, the site the device is located, the Operating System (OS) running on the device and so on can be edited.

Note: You can only edit the details of non-Juniper devices (Cisco devices and Nokia devices) in this release.

To edit the details of a device in the inventory:

  1. On the left navigation menu, click Inventory > Devices > Network Inventory.
    The Network Inventory page appears.
  2. Select a device to edit its details and click the Edit icon (pen).

    The Edit Device page appears.

  3. Enter values by referring to table.
  4. Click OK.

    A confirmation message appears indicating that the device details are updated.

Table 1: Non-Juniper Device Parameters

Field

Description

Device Name

Enter the device hostname.

Address/GRPC Port*

Enter the IPv4 address and gRPC port configured on the device.

Site

Click the drop-down list to select a site where the device is deployed.

Selecting a site to onboard a device is optional.

Timeout (in minutes)

Enter the time (in minutes) of inactivity after which the device disconnects with Routing Director.

Retry Delay (in minutes)

If Routing Director is unable to connect with a device, enter the time (in minutes) after which Routing Director retries to connect with the device.

TLS Encryption

Configure TLS encryption on devices.

Insecure*

This option is disabled by default, ensuring that connections between the device and Routing Director are secure (encrypted and authenticated).

When enabled, the connection is established without encryption or authentication. An insecure connection is vulnerable to man-in-the-middle attacks and other security risks. This option should be enabled only in local development or testing environments where security is not a concern.

Skip Verify*

This option is disabled by default and cannot be used when the Insecure option is enabled. Leave this option disabled if the device uses a certificate issued by a trusted Certificate Authority (CA).

Enable this option only if the device uses a self-signed or untrusted certificate that cannot be verified. When enabled, certificate validation is skipped during the connection process. Skipping certificate verification makes the connection vulnerable to man-in-the-middle attacks. Therefore, this option should be enabled only for development or testing purposes.

Certificate*

Click Browse to upload the TLS certificate for the device. Certificate is mandatory if you disable Insecure. See Enable TLS Authentication for information about obtaining certificates for third-party devices.

Key Certificate

Click Browse to upload the TLS certificate key for the device.

Certificate Authority

Certificate Authority: Click Browse to upload the TLS root certificate from the certificate authority.

NETCONF Configuration

Configure NETCONF on the devices.

NETCONF Enabled

Click to enable or disable NETCONF on Routing Director. By default, this option is disabled allowing Routing Director to establish NETCONF over SSH connections with the device.

If you enable NETCONF, enter the SSH port that can be used to establish connection with the device.

Port

Type the port number that Routing Director can use NETCONF for SSH connections with Routing Director.

Range: 1 through 65,535.

Key

Click Browse to upload the key that Routing Director can use for the NETCONF over SSH connections.

If you do not assign a key, Routing Director uses the username and password in the device configuration to establish connection with the device.

Credentials—Use this option to enter the username and password for the device to authenticate Routing Director.

Username

Enter a username for Routing Director to connect with the device.

Password

Enter the password for the username.

Related Documentation