Having trouble classifying Wyse thin clients using SNMP

[paulc1974]

So I created a custom probe and loaded it up with the relevant OID's.

When I test the probe it returns the payload showing the info I want i.e. device name, Ip, serial number, etc.

When I run discovery it completes just fine but the devices tab just shows current activity "classifying" and the device never gets sent to the cmdb.  The ECC queue doesn't display any classification activity at all and just shows the following information:

The input from the snmp probe shows as follows and has all the info I want highlight but like I say, nothing happens beyond this i.e. no classification/exploration, etc.

If anyone can offer any help, please do.

Regards

Paul

[robertgeen]

Hello,

It's hard to tell here what you have customized but I am going to assume you did a custom SNMP classifier. If so it's probably because identification isn't triggering because you haven't told it what probes to trigger on the sensor. Check your sensor and make sure it has the identification and exploration probes added to it that you want to trigger. 

[Darth Jed]

I was working on Wyse thin client discovery last July and had a similar problem. I had created a custom probe and sensor as well. Robert is correct that you are missing part of the PCIE process that Discovery follows. Here are the steps I followed. On a related note, I didn't actually get finished with this effort. I had problems getting all the data I needed from my test thin clients.

I created a SNMP Classification record called Wyse Thin Client. This sets the manufacturer and is paired with an SNMP OID Classification record for Wyse on the OID 1.3.6.1.4.1.714.1.2.6. The classification record triggers four probes: DNS, SNMP - Identity, and two custom probes to capture firmware info and thin client info. The thin client info probe is just an exploration phase probe configured with the following SNMP fields. I also added a MIB file to the platform (http://www.oidview.com/mibs/714/WYSE-MIB.html). No guarantees that the MIB will work for you.

iso.org.dod.internet.directory.mib.system.sysName

1.3.6.1.2.1.1.5 (same thing as above)

iso.org.dod.internet.directory.mib.system.sysDescr

1.3.6.1.2.1.1.1 (same thing as above)

iso.org.dod.internet.private.enterprises.wyse.product.thinClient.wbt3.wbt3Display

iso.org.dod.internet.private.enterprises.wyse.product.thinClient.wbt3.wbt3TrapDHCPBuildMismatch.wbt3Ram.wbt3RamNum

iso.org.dod.internet.private.enterprises.wyse.product.thinClient.wbt3.wbt3MibRev

1.3.6.1.4.1.714.1.2.6.2.1  (This gave me a serial number.)

iso.org.dod.internet.private.enterprises.wyse.product.thinClient.wbt3.wbt3TrapDHCPBuildMismatch.wbt3Rom.wbt3.RomNum

I had the numbers listed in the SNMP fields because I was testing which worked better. Anyway, I hope some of this is helpful. If you to look at my code, let me know and I can send it to you. I don't think the unfinished code is ready for public use, so I'm not posting it.

[stevenfroggattk]

Hi darthjed, I’m currently trying to work out how I can discover wyse thin os using snmp. I saw that you mentioned you made some custom probes and sensors, would it be possible for you to supply these? Thanks Steve

[Darth Jed]

I can't provide support for the update set, but you can take a crack at solving the problem with it.

After testing against a Wyse WT5050, the probe could identify the sysDescr, sysName, sysUptime, and sysObjectID. It returned a value that might have been a serial number, but it didn't match the sysName. Also, the probe didn't return a model number or manufacturer.

I misspoke on having created a sensor. I didn't get that far. Good luck!