Device Discovery Overview
You use device discovery to add devices to Junos Space. Discovery is the process of finding a device and then synchronizing the device’s inventory and configuration with the Junos Space database. To use device discovery, Junos Space must be able to connect to the device.
To discover network devices, Junos Space uses the SSH and SNMP protocols. Device authentication 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 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 connects to the physical device and retrieves running configuration and status information of the device. To connect with and configure devices, Junos Space uses Juniper Network’s Device Management Interface (DMI), which is an extension to the NETCONF network management protocol.
When discovery succeeds, Junos Space creates an object in the Junos Space database to represent the physical device and maintains a connection between the object and the physical device so their information is linked.
When configuration changes are made in Junos Space, for example, when you deploy service orders to activate a service on your network devices, the configuration is pushed to the physical device.
When configuration changes are made on the physical device, (out-of-band CLI commits and change-request updates), Junos Space automatically resychronizes with the device, so that the device inventory information in the Junos Space database matches the current device inventory and configuration information.
The following device inventory and configuration data is captured and stored in relational tables in the Junos Space database:
- Devices: hostname, IP address, credentials
- Physical Inventory:
chassis, FPM board, PEM, Routing Engine, CB, FPCs, CPU, PICs, Xcvrs,
fan trays
Junos Space displays the model number, part number, serial number, and description for each inventory component, when applicable.
- Logical Inventory: sub-interfaces, encapsulation (link-level), type, speed, MTU, VLAN ID
- Loopback interface
Other device configuration data is stored in the Junos Space database as Binary Large Objects, and is only available to NBI users.
