SNMP discovery Wyse thin client issue

TT21
Tera Contributor

We have an issue with discovery of Wyse thin clients. The responses from similiar clients are inconsistent.

An example is we have 2 Wyse 3040 clients both running ThinOS 2211. We have a pattern to identify these and add them to the CMDB and it works fine on some and not on others. An example we have 2 devices are on the same subnet. The SNMP - classify on the working unit returns sysName and sysDesc fields amoungst others to allow classification - payload from the ECC Queue SNMP - Classify input

TT21_0-1708456559766.png

 

The same step on the unit that doesn't get classified returns only the sysObjectID

TT21_1-1708456559769.png

 

 I've install an SNMP scanner tool on the Mid server to check what the response looks and both return reponses for sysName and sysDesc 

Not working

TT21_2-1708456559781.png

 

Working

TT21_3-1708456559776.png

 

I did post this question on https://www.servicenow.com/community/cmdb-forum/snmp-discovery-wyse-thin-clients/m-p/2832642#M9082 and it was suggested this was a more appropriate forum

 

I was asked about checking I had SNMP configured correctly and my repsonse was 

Do you have proper snmp configured ?

I've confirmed I can connect and the credentials are correct as we are using v3 and the credentials are the same in Paessler (the SNMP tool) also the crendetials are set accross all thin clients as part of the config policy applied via Wyse Managament Suite. I have been through the SNMP troubleshooting guide and it says "A target device must answer to both 1.3.6.1.2.1.1.1 and 1.3.6.1.2.1.1.2 to be discovered successfully." I can confirm using Paessler tool both devices provide responses to those IDs.

 

Suggestions please on where to look next to fix this issue

 

9 REPLIES 9

anurag92
Kilo Sage

Sorry doesn't tell us much from ECC queue. In the Devices tab, is the Completed activity indicating that the device has been classified but failed to identify?

TT21
Tera Contributor

TT21_0-1708490361293.png

Yes

 

anurag92
Kilo Sage

Can you also check the SNMP classifier defined for this class? I would say something is missing in the condition to not trigger the Identifier probe / pattern.

TT21
Tera Contributor

Correct the classifier for this device relies on the SNMP query returning a value in the sysDescr as can been seen in the 1st screen shot the value returned from the 2nd machine is blank but when queried via SNMP tool the value is available

 

anurag92
Kilo Sage

 Also, have a look at the last section of this article

 

You may be able to find the exact reason for the Classification failure.