- This topic is empty.
-
Posts
-
We have a fleet of a few hundred 1200LE terminals which to this date haven’t really been managed. They simply download their wnos.ini file and work away.
We are trying to track the terminals in our management system (Altiris).
What I’m trying to figure out is if the 1200LE’s are SNMP-discoverable.I see in the wnos.ini file we can specify a SNMP community string – but what is this for? Does Blazer run a very light version of snmpd, or is the string for the benefit of Rapport?
When I contacted Wyse Support to ask the same question I was simply given an answer that it’s EOL.
Any help is appreciated
WTOS is still supporting SNMP. You should contact Wyse again and ask for the WTOS MIB. Maybe you shouldn’t tell them that you are using EOLed units but eg V10L.
SNMP support for WTOS is compliant to SNMPv2 standards.
The ASN.1 prefix to, and including the Wyse Enterprise is 1.3.6.1.4.1.714, where the following OID references will be used:
–The Wyse enterprise {1.3.6.1.4.1.714}
–Product Group {1.3.6.1.4.1.714.1}
–ThinClient Group {1.3.6.1.4.1.714.1.2}
–wyseIT Group {1.3.6.1.4.1.714.1.2.6}The following portions of MIB II are implemented (the System group). Refer to RFC 1213 for details:
• (1) sysDescr – A textual description of the entity including HW type and software versions
• (2) sysObjectID – vendor’s authoritative identification of the network management subsystem contained in the entity
• (3) sysUpTime – time (in hundredths of a second) since the network management portion of the system was last re-initialized.
• (4) sysContact – contact person for this managed node.
• (5) sysName – domain name assigned to this node by the administrator
• (6) sysLocation – physical location of this node
• (7) sysServices – a value describing the set of services that this entity offersThe WTOS MIB is as follows, number in parenthesis is the OID reference:
• Administrative Group (1)
• (1) Trigger external reboot
• -1 cancel previously sent reboot trigger
• 0 send reboot trigger to reboot now
• 1 – 1440 reboot in # of minutes
• (2) send administrative message
• message will appear as part of the desktop, making the user switch back to the session they were in. The message will remain displayed on the desktop level until the reboot occurs.
• this message is informational only, and cannot be refused
• Current Information group (2)
• (1) Serial number – same value as serial number on Thin Appliance labelThanks for that great answer, however I’m just trying to get my head around SNMP on Blazer in the first place.
Our terminals are only running 5.0, which I’m not sure (I can’t see any information about it) is not running snmpd.
When I try to do a SNMP walk on one of the terminals, one app tells me it’s not responding to SNMP queries and the other tells me the terminal is does not respond using the “public” community string.Any ideas?
Yeah I did that, but same result.
Perhaps it didn’t download the updated ini file.Does it need quotation marks in the string name?
No quotation marks needed.
Check your WTOS eventlog. It should say something like Community set to blablabla.CG
I find there to be a lack of detail for the beginner. what I have done is create the wnos.ini with generator. made simple changes and successfully loaded them to the Wyse 1200LE. I was unsure on how to write the SNMP dialog so I told the generator to disable it so that it would write a line that I could understand. after that I made the following changes where my SNMP utility stil does not see it. My SNMP utility is not having any issue seeing other devices. Is there a MIB I need to add to the device. (I dont even know what that means but it would help to know if I were on the right track)
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 6.4.010 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************autoload=2
;*************************************************************
;* Network *
;*************************************************************SignOn=No
;*************************************************************
;* Services *
;*************************************************************Service=SNMPD disable=no
community=public;*************************************************************
;* RDP *
;*************************************************************;
;- RDP Session 1 –
;- Each line but the last must end with a ” –
;
CONNECT=RDP
Host=172.16.10.251
Description=”TS1″
Fullscreen=yes
LocalCopy=no
- You must be logged in to reply to this topic.