C.4.3. General::snmp Check - Red Hat NETWORK SATELLITE 5.1.1 Reference Manual

Appendix C. Probes
• <item key =" "> </item>
The remote program will need to output some iteration of the following code to STDOUT:
<perldata> <hash> <item
key="data">10</item> <item
key="status_message">status message here</item>
</hash> </perldata>
The required value for data is the data point to be inserted in the database for time-series trending.
The status_message is optional and can be whatever text string is desired with a maximum length
of 1024 bytes. Remote programs that do not include a status_message still report the value and
status returned.
Requirements — The Red Hat Network Monitoring Daemon (rhnmd) must be running on the
monitored system to execute this probe. XML is case-sensitive. The data item key name cannot be
changed and it must collect a number as its value.
Field
Command*
OK Exit Status*
Warning Exit Status*
Critical Exit Status*
Timeout
Table C.10. General::Remote Program with Data settings

C.4.3. General::SNMP Check

The General::SNMP Check probe tests your SNMP server by specifying a single object identifier (OID)
in dotted notation (such as 1.3.6.1.2.1.1.1.0) and a threshold associated with the return value. It
collects the following metric:
• Remote Service Latency — The time it takes in seconds for the SNMP server to answer a
connection request.
Requirements — SNMP must be running on the monitored system to perform this probe. Only integers
can be used for the threshold values.
This probe's transport protocol is User Datagram Protocol (UDP).
Field
SNMP OID*
SNMP Community String*
SNMP Port*
SNMP Version*
Timeout*
Critical Maximum Value
Warning Maximum Value
210
Value
0
1
2
15
Value
public
161
2
15