If SNMP is enabled, and SNMP credentials are supplied, the device server attempts to determine which SNMP credentials are valid for the device. The device server starts with SNMPv1, then SNMPv2c, and finally SNMPv3. This order is used for performance reasons. Once a valid SNMP credential is found, the device is queried for its SysObjectID. This allows the device server to know which device driver to use for the remainder of the process.
Depending on the settings for the discovered device class, the device server now attempts to determine credentials for SSH, Telnet, FTP, and/or SCP. The management mechanism is set for the device based on the discovered credentials and the ordering options set in the application.
If SNMP is disabled, the device server attempts first to SSH, and failing that, Telnet to each device and determine the proper login credentials. Once the proper credentials are determined, the device server traverses through the device drivers to determine what the device class is for the connected device.
This is attempted based on the order contained in the addev.order file on the device server. Once a device class is determined, the appropriate commands are sent to the device to determine it's model information, which is then cross referenced with Voyence's database to determine the SysObjectID for the device.
Depending on the settings for the discovered device class, the device server now attempts to determine if FTP and/or SCP are enabled. The management mechanism is set for the device, based on the discovered credentials and the ordering options set in the application.