LOG-MIB :: logCurrentPC

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › LOG-MIB › logCurrentPC

logCurrentPC

Module: LOG-MIB

OID (symbolic): LOG-MIB::logCurrentPC

OID (numeric): 1.3.6.1.4.1.1038.105.105.1.6

Node type: OBJECT-TYPE

Type: DisplayString

Access: read-only

Description: Probable cause. A short string which identifies the event type. For a failure it is its mnemonique.

What is logCurrentPC?

The probable-cause mnemonic for this currently active alarm, mirroring logPC but scoped to the current-alarms table, giving the admin the specific failure reason behind an alarm that is still outstanding.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1038.105.105.1.6
snmpwalk -v2c -c public <target> LOG-MIB::logCurrentPC

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1038.105.105.1.6.1
snmpget -v2c -c public <target> LOG-MIB::logCurrentPC.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::logCurrentPC 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.6logCurrentPCLOG-MIB