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

We ran into a similar issue with another SNMP Class. You might have already done this, but just to double check if you have ensured the OID exists in the SNMP OID Classifications table against the Class you expect the CI to be classified into.

TT21
Tera Contributor

Unfortunately I can't rely on the sysObjectId 1.3.6.1.4.1.8072.3.2.8 as they've chosen to use a very generic Id that resolves to freebsd so I am classifing it using data from sysDescr 

 

anurag92
Kilo Sage

What's the exact error you get when you run a quick discovery on this IP?

TT21
Tera Contributor

I don't get an error it's simply not classified and the return in the ECC queue doesn't contain the same response as the unit that is - The screen shots of the values in the payload coming back are in the original post.

sample of the ECC queue for discovery below - a good result 

TT21_0-1708483102033.png

Sample of a poor result

TT21_1-1708483152986.png