All MIBs › RMON2-MIB › probeDateTime
probeDateTime
Module: RMON2-MIB
OID (symbolic): RMON2-MIB::probeDateTime
OID (numeric): 1.3.6.1.2.1.16.19.4
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description:
Probe's current date and time.
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..11
10 11 minutes from UTC 0..59
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, and if no time information is known, the null
string is returned.What is probeDateTime?
This object holds the probe's current date and time including timezone offset, stored as a byte string that can be read or set by operators. Time synchronization is critical for correlation of events across network devices and accurate log timestamps. For example, setting this to "2024-6-25,14:30:15.0,-5:0" synchronizes the probe to June 25, 2024 at 2:30:15 PM Eastern time.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.19.4 snmpwalk -v2c -c public <target> RMON2-MIB::probeDateTime
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.16.19.4.1 snmpget -v2c -c public <target> RMON2-MIB::probeDateTime.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.16.19.4.1 s <value>
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.2 | mgmt | BKTEL-HFC862-BASE-MIB |
| 1.3.6.1.2.1 | mib_2 | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.16 | rmon | LBHUB-BOOM-MIB |
| 1.3.6.1.2.1.16.19 | tftp | REMOTEACCESS-MIB |
| 1.3.6.1.2.1.16.19.4 | probeDateTime | RMON2-MIB |