Updating a devices sysDescr using the CLI so it can be discovered

The sysDescr can be set with in the GUI using the Device Details report > Description > Enter a sysDescr > Save

Or by using the Admin Tool > Expert Tools > Config tool
 Which is the graphical version of the CLI entries below:

Find the real sysDescr

Use the SNMP Walk feature to get the real sysDescr

In the example of a device that wasnt being discovered it should have been 

VeloCloud EDGE6X0

But VeloCloud was used as the sysDescr as this was in the sysDescr rules file in statseeker

Ordinarily the device will respond with the sysDescr and we pick this value up for the device discovery process.

Some vendors do not use the sysDescr to describe what the device actually is or sometimes the device won’t allow us to read this value using SNMP.
Either way, for the discovery process to complete successfully, the value we get from the device must contain one of the entries in the Admin Tool > Network Discovery - Advanced Options > SysDescr Rules

Get the sysDescr from the device:
nim-snmpwalk 10.254.0.1 port 161 2 v2password-here sysDescr
nim-snmpwalk 10.254.0.1 auth sha sha-user-here SHA-Password-Here priv aes PRIV-Password-Here nocontext sysDescr

To set the sysDescr on the CLI
nim-cfg set 10.254.0.1:SNMPv2-MIB:sysDescr:0 cfg VeloCloud

Optionally set the use GetNext for Discovery
nim-cfg set 10.254.0.1::discover_getNext:0 cfg 1

Run a discovery and send the output to a file
nim-discover -r -e -d 10.254.0.1 -t 30 -l /tmp/10.254.0.1_Discover.log

We are telling/forcing Statseeker to use the sysDescr VeloCloud for that IP address in the discovery process
This usually works without any intervention but some devices can be problematic