Discovery and Wyse/Thin Clients
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2010 12:50 PM
I'm having trouble finding our terminals when doing a discovery on an IP range.
Is it able to find these types of devices and list all their information as it does for PC's?
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2014 10:53 AM
Chris you would need to create a specific wyse identifier probe that calls the specific OIDs in that MIB

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2014 01:29 PM
Chris,
On your classify payload return, are you seeing the data you expect to see from the device specific OIDs? If so, then you might have to add a flag in your classify script.
You'll probably see code like this already in your analyze method of the classify script:
// is this thing a switch?
var ports = snmp.getOIDInt( oid_dot1dBridge + 'dot1dBase.dot1dBaseNumPorts' );
var isSwitch = ports > 0;
capabilities['switching'] = '' + isSwitch;
capabilities['block_switch_exploration'] = 'false';
So, now, check your OID by name (if you installed a MIB) or by number (if you didn't). If that OID exists, then capabilities['wyse'] = 'true'
From there, go into your snmp classification table, add a new record, and set the capability to match for 'wyse' = 'true'. Make sure to put it in the order to execute prior to the windows or it'll get classified in the wrong spot.
That should help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2014 01:47 PM
Stephen - good recommendations. I think our main issue is that the classify payload return is returning limited data - i.e. the only OID's returned are in the same tree as that "MS Windows CE v.4.20" and the WYSE OID (1.3.6.1.4.1.714) isn't even being referenced. Doug provided me a workaround to test. I'll reply to the post if I get a chance to try your recommendation on a different WYSE device that actually returns the correct OID's..

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-15-2014 09:56 PM
Let me know how it works out. You have specified a full 'walk' on the WYSE OID (1.3.6.1.4.1.714) yeah? Just to capture everything? (It's the related record to the classify probe in a table called 'snmp fields')
Command: Walk
OID: 1.3.6.1.4.1.714
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-01-2015 08:45 AM
Just curious if you ever made any headway here? I am just beginning testing a similar environment and would love to hear about how this all worked out.