Votes:
I need to check if real date & time of my devices differ too much from real actual time (given to PRTG server by my secure ntp server). How can read this standard oid from host-resource-mib: .iso.org.dod.internet.mgmt.mib-2.host.hrSystem.hrSystemDate.0 (.1.3.6.1.2.1.25.1.2.0) ? integer returns error and string too..
Thanks a lot!
Gianluca
Last change on Aug 3, 2016 1:40:54 PM by
Votes:
With Custom Sensor PTF CheckTimeSNMP you can check the time difference between a device and your PRTG server/probe in seconds.
The sensor gets the time from the device using SNMP and compares it with the local time of your PRTG server/probe.
-s=device [-c=community string] [-v=SNMP version] [-p=SNMP port] -s= IP address or DNS name of the device to check.") -c= Optional, SNMP community string for SNMP v1/v2c. Default=public.") -v= Optional, SNMP version. Supported version: 1 or 2c. Default=1.") -p= Optional, SNMP port number on remote host. Default=161")
The Custom Sensor can be downloaded from this page.
Last change on Jan 8, 2011 8:30:26 PM by
4 Replies
Votes:
I am sorry, PRTG does not directly support datetime OIDs at this time. The only viable solution is a custom sensor.
Created on Jan 7, 2011 8:25:37 AM by
Last change on Jan 7, 2011 3:18:19 PM by
Votes:
With Custom Sensor PTF CheckTimeSNMP you can check the time difference between a device and your PRTG server/probe in seconds.
The sensor gets the time from the device using SNMP and compares it with the local time of your PRTG server/probe.
-s=device [-c=community string] [-v=SNMP version] [-p=SNMP port] -s= IP address or DNS name of the device to check.") -c= Optional, SNMP community string for SNMP v1/v2c. Default=public.") -v= Optional, SNMP version. Supported version: 1 or 2c. Default=1.") -p= Optional, SNMP port number on remote host. Default=161")
The Custom Sensor can be downloaded from this page.
Last change on Jan 8, 2011 8:30:26 PM by
Votes:
There are not plans for native support for this datatype, the reason for this is that this can usually not be directly translated as a numerical value which PRTG can use, meaning there's only a handful of scenarios were this would be useful.
The only alternatives are PRTGToolsFamily script above or creating the custom sensor with NET-SNMP + PRTG yourself. Please note that the output of the script must be an integer or double numerical value, and the output of the script must comply with PRTG's API for custom sensors.
Please check the following NET-SNMP + Powershell Examples:
Note: PRTG does not provide parameters for credentials in SNMPV3, in that case hard-code them in the script or define them as parameters in the sensor's settings (without placeholders).
For reference, this is the definition for the TEXTUAL-CONVENTION which defines the DateandTime format as documented in the SNMPv2-TC MIB.
DateAndTime ::= TEXTUAL-CONVENTION
DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"
STATUS current
DESCRIPTION
"A date-time specification.
field octets contents range
----- ------ -------- -----
1 1-2 year* 0..65536
2 3 month 1..12
3 4 day 1..31
4 5 hour 0..23
5 6 minutes 0..59
6 7 seconds 0..60
(use 60 for leap-second)
7 8 deci-seconds 0..9
8 9 direction from UTC '+' / '-'
9 10 hours from UTC* 0..13
10 11 minutes from UTC 0..59
* Notes:
- the value of year is in network-byte order
- daylight saving time in New Zealand is +13
For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
displayed as:
1992-5-26,13:30:15.0,-4:0
Note that if only local time is known, then timezone
information (fields 8-10) is not present."
SYNTAX OCTET STRING (SIZE (8 | 11))
Best Regards,
Luciano Lingnau [Paessler Support]
Created on Aug 3, 2016 1:54:17 PM by
Add comment