LOG-MIB

All MIBs › LOG-MIB

Organization: SAGEM/DR Tolbiac Centre

Last Updated: 2002-11-15

Category: Technology: Logging/Syslog

Description: SAGEM MIB covering logging configuration and log entry management for recording telecom and network equipment events.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is LOG-MIB?

LOG-MIB is a SAGEM-defined proprietary module used to manage event logging on SAGEM telecommunications and network equipment. It exposes objects for configuring log entry storage, event severity/probable-cause classification, and trap re-notification behavior for events that may have been missed by a management station. Its main monitoring value is operational and fault status: it tracks lost-trap conditions (lostTrapBool, lostTrapBegin, lostTrapEnd, lostTrap), threshold-overflow events, maintenance events, and general log/event history rather than raw hardware sensors. It builds on standard SNMPv2 NOTIFICATION-TYPE conventions (having migrated away from older SMIv1 TRAP-TYPE definitions) and works alongside other SAGEM enterprise MIBs for full device management. It is typically deployed on SAGEM carrier-grade transmission or access equipment where reliable delivery of alarm/event history to an NMS is important, and operators typically start with a LOG-MIB download to load these objects into their SNMP management platform.

IPNetwork Monitor allows you to monitor SNMP objects defined in LOG-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

SAGEM telecom/network equipment

Monitoring Examples

An operator would poll the LodEvent-related objects to see a running log of device events such as qualityThresholdOverflow, otherThresholdOverflow, and maintenance conditions, using probableCause to triage root cause. The lostTrapBool/lostTrapBegin/lostTrapEnd/lostTrap objects let a management station detect and reconstruct a window during which traps were dropped, re-requesting the missed notifications. A sustained non-zero lostTrap count would reveal an unreliable trap channel or an overloaded SNMP agent needing attention.

What Can Be Monitored

logged event entries
lost trap detection window
quality threshold overflow events
other threshold overflow events
maintenance events
event probable cause

Imported Objects

From EQUIPMENT-MIB

IntDateTime
SagemBoolean
Severity

From SAGEM-DR-MIB

sagemDr

MODULE-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
log	1.3.6.1.4.1.1038.105			Modification: Date: 15 11 2002 Description: sagemDr replace sagem-dr NOTIFICATION-TYPE replace TRAP-TYPE Modification: Date: 20 12 1999 Description: Modification of comments Modification of trap re-notification quality-threshold-overflow replaced by performance. New Object: Date: 30 11 1999 Name: lostTrapBool,lostTrapBegin,lostTrapEnd,lostTrap Description: System of re-notification of lost traps, Name: LodEvent Description: Add of qualityThresholdOverflow (20), otherThresholdOverflow (21), maintenance (30) Name: probableCause Description: SIZE (0..20) replaced by SIZE (0..50) Creation: This MIB module describes alarmes and event log records. It also describes associated trap
logTraps	1.3.6.1.4.1.1038.105.0
NTF logTrap	1.3.6.1.4.1.1038.105.0.1			A trap of this type indicates that a threshold has been crossed in the corresponding interface/function. It also gives the date and time when the trap was sent, and the equipment status
NTF thresholdTrap	1.3.6.1.4.1.1038.105.0.2			A trap of this type indicates that a threshold has been crossed in the corresponding interface/function. It also gives the date and time when the trap was sent, and the equipment status
INT logClear	1.3.6.1.4.1.1038.105.1	INTEGER	read-write	When a set command is issued on this variable the entire log event is cleared. This command is optional
INT logCapacity	1.3.6.1.4.1.1038.105.2	INTEGER	read-only	The maximum number of event in the log database
INT logLastEvent	1.3.6.1.4.1.1038.105.3	INTEGER	read-only	The index of the last event number that have been logged. This is usefull for trap lost detection.
INT logNumber	1.3.6.1.4.1.1038.105.4	INTEGER	read-only	Number of current log in equipment.
logTable	1.3.6.1.4.1.1038.105.5		not-accessible	List of log trap that come from the equipment.
logEntry	1.3.6.1.4.1.1038.105.5.1		not-accessible	A particular log of the equipment.
INT logIndex	1.3.6.1.4.1.1038.105.5.1.1	INTEGER	read-only	A unique value which identify a particular log entry. The index value cannot exced logCapacity and then returns to zero when the number of events exceds the capacity of equipement log table. Its value is : logIndex = %logCapacity. It is mandatory for the equipment to respond to get-next in anti-chronological order (youngest first) no matter to the index value. Get-next(LogEntry.logEntry) is logEntry.logIndex[logLastEvent]
NUM logDate	1.3.6.1.4.1.1038.105.5.1.2	IntDateTime	read-only	When the event had happened.
OID logObject	1.3.6.1.4.1.1038.105.5.1.3	OBJECT IDENTIFIER	read-only	A reference to the function/interface who produced the event
STR logName	1.3.6.1.4.1.1038.105.5.1.4	DisplayString	read-only	A text string which identifies the particular entry among the log entries.
LOG logEvent	1.3.6.1.4.1.1038.105.5.1.5	LogEvent	read-only	indicates the type of event which had occured
STR logPC	1.3.6.1.4.1.1038.105.5.1.6	DisplayString	read-only	Probable cause. A short string which identifies the event type. For a failure it is its mnemonique.
STR logAI	1.3.6.1.4.1.1038.105.5.1.7	DisplayString	read-only	A short string which gives additional information on the event
SEV logEquipStatusV2	1.3.6.1.4.1.1038.105.5.1.8	Severity	read-only	logEquipStatusV2 is the value of equipStatusV2 stored in logTable each time a trap is sent
SAG logTrapEnable	1.3.6.1.4.1.1038.105.6	SagemBoolean	read-write	When set to false the equipment stops to send logTraps. It has no effect on event log recording. It also has no effects on quality traps and on status trap used for the manager IONOS-ANM-V1. The default value is true.
lostTrap	1.3.6.1.4.1.1038.105.7
SAG resendTrapBool	1.3.6.1.4.1.1038.105.7.1	SagemBoolean	read-write	The manager set this variable to receive all the current traps of the equipment. The equipment must use resentLogTrap and resentNetworkAlarmeTrap to do it(not in P0).
INT logCurrentClear	1.3.6.1.4.1.1038.105.101	INTEGER	read-write	When a set command is issued on this variable the entire log event is cleared. This command is optional
INT logCurrentCapacity	1.3.6.1.4.1.1038.105.102	INTEGER	read-only	The maximum number of event in the log database This variable is optional
INT logCurrentLastEvent	1.3.6.1.4.1.1038.105.103	INTEGER	read-only	The index of the last current alarm number that have been logged. This variable is optional
INT logCurrentNumber	1.3.6.1.4.1.1038.105.104	INTEGER	read-only	Number of current log in equipment.
logCurrentTable	1.3.6.1.4.1.1038.105.105		not-accessible	List of log trap that come from the equipment.
logCurrentEntry	1.3.6.1.4.1.1038.105.105.1		not-accessible	A particular log of the equipment.
INT logCurrentIndex	1.3.6.1.4.1.1038.105.105.1.1	INTEGER	read-only	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.
NUM logCurrentDate	1.3.6.1.4.1.1038.105.105.1.2	IntDateTime	read-only	When the event had happened.
OID logCurrentObject	1.3.6.1.4.1.1038.105.105.1.3	OBJECT IDENTIFIER	read-only	A reference to the function/interface who produced the event
STR logCurrentName	1.3.6.1.4.1.1038.105.105.1.4	DisplayString	read-only	A text string which identifies the particular entry among the log entries.
LOG logCurrentEvent	1.3.6.1.4.1.1038.105.105.1.5	LogEvent	read-only	indicates the type of event which had occured
STR logCurrentPC	1.3.6.1.4.1.1038.105.105.1.6	DisplayString	read-only	Probable cause. A short string which identifies the event type. For a failure it is its mnemonique.
STR logCurrentAI	1.3.6.1.4.1.1038.105.105.1.7	DisplayString	read-only	A short string which gives additional information on the event
SEV logCurrentStatusV2	1.3.6.1.4.1.1038.105.105.1.8	Severity	read-only	logEquipStatusV2 is the value of equipStatusV2 stored in logTable each time a trap is sent

RFC description

SAGEM MIB defining logging configuration and log entry management objects for telecom and network equipment event recording.

Start monitoring SAGEM telecom/network equipment (alarm/event log) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download LOG-MIB

What Is LOG-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description