Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Unmanaged Devices Overview

 

Unmanaged devices are non-DMI devices made by vendors other than Juniper Networks, Inc. You can add such devices to Junos Space Edge Services Director manually, or by importing multiple devices simultaneously from a CSV file. You need to provide the IP address or the host name of the unmanaged device, name of the vendor, username of the device, password for the device, SNMP credentials, loopback address details, and key-values that are needed for the device driver to operate. The currently supported SNMP versions are SNMP V1, SNMP V2C, and SNMP V3. You are any other user may need to enter the key and the value for the device driver to operate. You can add multiple key-value pairs for an unmanaged device. The key-value pairs supported are plain-text string or password. If Junos Space Network Management Platform can communicate with the device using SNMP, the information gathered via SNMP overrides the information that you enter.

When you have added the unmanaged device and installed the appropriate device drivers, the inventory data is fetched from the device. Physical interface and logical interface details can be fetched for an unmanaged device. You can resynchronize the device with the network both in SSOR and NSOR mode. This action will resynchronize the inventory data for the device based on the capabilities supported by the device. Junos Space Network Management Platform does not monitor the connection status of the unmanaged device for which the device driver is installed in Junos Space Network Management Platform. The Device Management table lists NA in the Connection Status column for unmanaged devices.

You need to package the driver code into a JAR file and add it to the Jboss 7 shared module directory. Junos Space Network Management Platform accesses the driver class using module based class loading. You also need to make an entry into the driver registration XML file. Junos Space Network Management Platform reads this XML file when JBOSS starts and populates this XML file into the database. The XML file should include the following parameters:

Parameter

Description

Name

Name of the device driver.

Vendor

Vendor of the device.

DeviceFamily

The family of the device.

Platform

The platform of the device.

DriverClassName

The full class name of the class which extends the driver class from the device platform.

MgtAttrColl

Holds a collection of key-value pairs that are populated in the Advanced Properties section when creating an unmanaged device. This can be omitted if you want to enter the key-value pairs when creating an umanaged device.

IsDefaultForVendor

When set to true, the driver is used as a default driver for devices of other device family or platform, but from the same vendor.

IsDefaultForFamily

When set to true, the driver is used as a default driver for devices of a different platform, but from the same vendor and device family.

Creating an unmanaged device from a vendor other than Juniper Networks also creates a tag for that vendor (for example, CISCO) and assigns that tag to the device. If you have successfully installed the device driver on Junos Space Network Management Platform, you will be able to fetch the information related to physical and logical interface, manually resynchronize inventory data, and edit the unmanaged device configuration using the Junos Space applications. You can view the changes in the unmanaged device configuration using the View Configuration Change Log action.