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.

MAC*

Enter the MAC address of 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.

Vendor*

Click the drop-down list to select the vendor of the device—Cisco or Nokia.

Model*

Enter the device model. For example, Cisco NCS-57C3

Operating System Name*

Enter the name of the operating system (OS) deployed on the device. For example, IOS XR.

Version*

Enter the version of the operating system. For example 7.10.1.

For a list of software versions supported on the Cisco and Nokia devices, see Supported Junos OS Releases, Devices, and Browsers .

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.

Authorization

Insecure*

This option is disabled by default and the connection between the device and Routing Director is secure (encrypted and/or authenticated).

Enable this option when TLS is disabled on the device so that the connection between Routing Director and the device is established without any encryption.

The insecure connection is vulnerable to man-in-the-middle attacks and other security threats. We recommend that you use an insecure connection between the Routing Director and the device only during local development and in testing environments where security is not a concern.

Skip Verify*

This option is disabled by default and the device verifies the identity of Routing Director when Routing Director establishes a connection with the device.

Enable this option when TLS is enabled on the device and the device should skip verifying Routing Director's identity when Routing Director establishes a connection. This option is useful when you have a self-signed certificate that cannot be verified against a certificate authority, so that the device skips the verification process.

When you skip verifying Routing Director's identity, the connection is vulnerable to man-in-the-middle attacks. Therefore, this option should be enabled only during development or testing the connection between the device and Routing Director.

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

Certificate*

Click Browse to upload the TLS certificate for the device.

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.

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

Username

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

Password

Enter the password for the username.

NETCONF Enabled

Click to enable or disable (default) NETCONF on Routing Director to establish SSH connections with the device.

If you enable NETCONF, enter the SSH port for establishing 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 NETCONF for the 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.

Related Documentation