Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Device Discovery Overview

 

You use device discovery to add devices to Junos Space Edge Services Director application. Discovery is the process of finding a device and then synchronizing the device inventory and configuration with the Junos Space Edge Services Director application database. To use device discovery, Junos Space Edge Services Director application must be able to connect to the device.

To discover network devices, Junos Space Edge Services Director application uses the SSH and SNMP protocols. Device authentication initially is handled through administrator login SSH v2 credentials and SNMP v1/v2c or v3 settings, which are part of the device discovery configuration. You can continue to use credentials for these devices thereafter, or you can create and upload RSA keys to devices to allow Junos Space Edge Services Director application to authenticate itself to them automatically during later discoveries.

You can specify a single IP address, a DNS hostname, an IP range, or an IP subnet to discover devices on a network. During discovery, Junos Space Edge Services Director application connects to the physical device and retrieves the running configuration and the status information of the device. To connect with and configure devices, Junos Space Edge Services Director application uses Juniper Network’s Device Management Interface (DMI), which is an extension to the NETCONF network configuration protocol.

When discovery succeeds, Junos Space Edge Services Director application creates an object in the Junos Space Edge Services Director application database to represent the physical device and maintains a connection between the object and the physical device so their information is linked.

Junos Space can manage devices in either of the following ways:

  • Junos Space initiates and maintains a connection to the device.

  • The device initiates and maintains a connection to Junos Space.

By default, Junos Space manages devices by initiating and maintaining a connection to the device. When Junos Space initiates the connection to the device, you can discover and manage devices provided that the management system is behind Network Address Translation (NAT), as Junos Space establishes the SSH tunnel directly to the device. For WW Junos devices, Junos Space uses SSH with an adapter to manage the devices.

If device-initiated connection to Junos Space is enabled, the DMI channel and port 7804 are used and the following (sample) configuration is added on the device to establish the connection to Junos Space:

When configuration changes are made in Junos Space Edge Services Director application, for example, when you deploy service orders to activate a service on your network devices, the configuration is pushed to the physical device.

If the network is the system of record (NSOR), when configuration changes are made on the physical device (out-of-band CLI commits and change-request updates), Junos Space Edge Services Director application automatically resynchronizes with the device so that the device inventory information in the Junos Space Edge Services Director application database matches the current device inventory and configuration information. If Junos Space Edge Services Director application is the system of record (SSOR), this resynchronization does not occur and the database is unchanged.

The following device inventory and configuration data is captured and stored in relational tables in the Junos Space Edge Services Director application database:

  • Devices—hostname, IP address, credentials

  • Physical Inventory—chassis, FPM board, Power Entry Module (PEM), Routing Engine, Control Board (CB), Flexible PIC Concentrator (FPC), CPU, Physical Interface Card (PIC), transceiver (Xcvr), fan tray

    Junos Space Edge Services Director application displays the model number, part number, serial number, and description for each inventory component, when applicable.

  • Logical Inventory—subinterfaces, encapsulation (link-level), type, speed, maximum transmission unit (MTU), VLAN ID

  • License information:

    • License usage summary—license feature name, feature description, licensed count, used count, given count, needed count

    • Licensed feature information—original time allowed, time remaining

    • License SKU information—start date, end date, and time remaining

  • Loopback interface

Other device configuration data is stored in the Junos Space Edge Services Director application database as binary large objects, and is available only to northbound interface (NBI) users.