SNMP discovery Wyse thin clients

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-1708393297924.png

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

TT21_1-1708393444506.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_3-1708393843284.png

Working

TT21_2-1708393723230.png

Suggestions please on where to look next to fix this issue

 

 

4 REPLIES 4

Tony Branton
ServiceNow Employee
ServiceNow Employee

Hi, you'll have better luck getting a response to your question if you post it in the ITOM forum. Although Discovery updates data in the CMDB, it is an ITOM solution and not part of the CMDB.

Thanks I'll try that

Sohail Khilji
Kilo Patron
Kilo Patron

Hi @TT21 

 

Do you have proper snmp configured ? I belive its an issue realted to access as your unable to get sysObjectID and only name and desc is rerurned in response.

 

Question  : Which snmp walk tool your using ?

 

 


☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....

LinkedIn - Lets Connect

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.