LOG-MIB :: logCurrentDate

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LOG-MIB › logCurrentDate

logCurrentDate

Module: LOG-MIB

OID (symbolic): LOG-MIB::logCurrentDate

OID (numeric): 1.3.6.1.4.1.1038.105.105.1.2

Node type: OBJECT-TYPE

Type: IntDateTime

Access: read-only

Description: When the event had happened.

What is logCurrentDate?

The date and time the alarm recorded in this current-alarms table entry actually occurred, letting an admin see how long a still-active alarm has been outstanding.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1038.105.105.1.2
snmpwalk -v2c -c public <target> LOG-MIB::logCurrentDate

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1038.105.105.1.2.1
snmpget -v2c -c public <target> LOG-MIB::logCurrentDate.1

Start monitoring SAGEM telecom/network equipment (alarm/event log) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LOG-MIB::logCurrentDate OID value, configure state conditions and alerts, and monitor any SAGEM telecom/network equipment (alarm/event log) from a single console.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1038sagemDrSAGEM-DR-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1038.105logLOG-MIB
1.3.6.1.4.1.1038.105.105logCurrentTableLOG-MIB
1.3.6.1.4.1.1038.105.105.1logCurrentEntryLOG-MIB
1.3.6.1.4.1.1038.105.105.1.2logCurrentDateLOG-MIB