LOG-MIB :: logCurrentIndex

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LOG-MIB › logCurrentIndex

logCurrentIndex

Module: LOG-MIB

OID (symbolic): LOG-MIB::logCurrentIndex

OID (numeric): 1.3.6.1.4.1.1038.105.105.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: A unique value which identify a particular logCurrent entry. The index value is comprised between 1 and logCurrentNumber. There is no relation between the index Value and the date of the alarm.

What is logCurrentIndex?

A unique index (between 1 and logCurrentNumber) identifying one entry in the current-alarms table; unlike the historical log's index, it has no relation to the alarm's date. Admins use it simply to enumerate the currently active alarms.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1038.105.105.1.1
snmpwalk -v2c -c public <target> LOG-MIB::logCurrentIndex

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1038.105.105.1.1.1
snmpget -v2c -c public <target> LOG-MIB::logCurrentIndex.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> logCurrentIndex.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::logCurrentIndex 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.1logCurrentIndexLOG-MIB