LOG-MIB :: logCurrentClear

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LOG-MIB › logCurrentClear

logCurrentClear

Module: LOG-MIB

OID (symbolic): LOG-MIB::logCurrentClear

OID (numeric): 1.3.6.1.4.1.1038.105.101

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: When a set command is issued on this variable the entire log event is cleared.

This command is optional

What is logCurrentClear?

Setting this object to setToClear(0) clears the current-alarms log (as opposed to the full historical log cleared by logClear). Admins use it to reset the active-alarm table, for example after confirming all listed alarms have been resolved.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1038.105.101
snmpwalk -v2c -c public <target> LOG-MIB::logCurrentClear

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1038.105.101.1
snmpget -v2c -c public <target> LOG-MIB::logCurrentClear.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.1038.105.101.1 i <value>

SNMPv3 example:

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