TIMETRA-SAS-LOG-MIB

All MIBs › TIMETRA-SAS-LOG-MIB

Organization: Alcatel

Last Updated: 2011-08-01

Category: Network Management Infrastructure, Nokia SR OS / Alcatel-Lucent 7750 SR

Description: Manages Nokia/Alcatel-Lucent 7210 SAS event log configuration and notification policy.

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 TIMETRA-SAS-LOG-MIB?

TIMETRA-SAS-LOG-MIB is a Nokia/Alcatel-Lucent proprietary SNMP module for the 7210 SAS platform that manages and monitors event-logging configuration, including where log events are sent and how notification/trap targets are structured. It exposes objects for configuring primary, secondary, and tertiary log-forwarding targets (e.g. for gasp/emergency logging) and extended log-application settings tying log IDs to target names. Its monitoring value is confirming that critical system events (including hardware and software faults reported elsewhere in the device) are being correctly routed to the intended log destinations, since a misconfigured logging target can mean an operator misses fault notifications entirely. It complements the standard SNMPv2-MIB notification-logging framework and other TIMETRA fault-reporting MIBs whose traps rely on this logging infrastructure being correctly configured. It is deployed on Nokia/Alcatel 7210 SAS switches in access/aggregation networks where centralized event log collection is required. Engineers can download the TIMETRA-SAS-LOG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TIMETRA-SAS-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

Nokia/Alcatel-Lucent 7210 SAS switches
SAS access/aggregation platforms

Monitoring Examples

An operator polls tmnxDygGaspPriLogId/tmnxDygGaspPriTgtName to confirm the primary emergency ("gasp") log target is correctly pointed at the expected log ID and destination, and checks the secondary/tertiary equivalents as failover targets. The tmnxLogApExtnTable/tmnxLogApExtnEntry rows are checked when validating that a specific log application's events are being forwarded as expected. If expected log entries stop arriving at a monitoring server, reviewing these target-name bindings is a first troubleshooting step to rule out a logging misconfiguration.

What Can Be Monitored

primary/secondary/tertiary log target configuration
log ID to target-name bindings
log application extension settings

Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMP-FRAMEWORK-MIB

SnmpAdminString
SnmpMessageProcessingModel
SnmpSecurityLevel

From SNMP-NOTIFICATION-MIB

snmpNotifyEntry

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-MIB

sysDescr	OBJECT-TYPE
sysObjectID	OBJECT-TYPE

From SNMPv2-SMI

Counter32
Counter64
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
RowStatus
StorageType
TEXTUAL-CONVENTION
TimeStamp
TruthValue

From TIMETRA-FILTER-MIB

TFilterAction
TFilterActionOrDefault

From TIMETRA-GLOBAL-MIB

timetraSRMIBModules	OBJECT-IDENTITY
tmnxSRConfs	OBJECT-IDENTITY
tmnxSRNotifyPrefix	OBJECT-IDENTITY
tmnxSRObjs	OBJECT-IDENTITY

From TIMETRA-LOG-MIB

TmnxLogIdIndex
tmnxLogApEntry	OBJECT-TYPE
tmnxSnmpTrapDestEntry	OBJECT-TYPE

From TIMETRA-SAS-GLOBAL-MIB

timetraSASConfs	OBJECT-IDENTITY
timetraSASModules	OBJECT-IDENTITY
timetraSASNotifyPrefix	OBJECT-IDENTITY
timetraSASObjs	OBJECT-IDENTITY

From TIMETRA-TC-MIB

THsmdaCounterIdOrZero
THsmdaCounterIdOrZeroOrAll
TItemDescription
TNamedItem
TNamedItemOrEmpty
TQueueId
TQueueIdOrAll
TmnxAccPlcyAACounters
TmnxAccPlcyOECounters
TmnxAccPlcyOICounters
TmnxAccPlcyQECounters
TmnxAccPlcyQICounters
TmnxActionType
TmnxAdminState
TmnxOperState

OIDs

OID symbolic	OID numeric	Type	Access	Description
timetraSASLogMIBModule	1.3.6.1.4.1.6527.6.2.1.1.14			This document is the SNMP MIB module to manage and provision the Alcatel 7210 Logging utility. Copyright 2003-2012 Alcatel-Lucent. All rights reserved. Reproduction of this document is authorized on the condition that the foregoing copyright notice is included. This SNMP MIB module (Specification) embodies Alcatel's proprietary intellectual property. Alcatel retains all title and ownership in the Specification, including any revisions. Alcatel grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of Alcatel products, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'as is', and Alcatel makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.
tmnxSASLogConformance	1.3.6.1.4.1.6527.6.2.2.1.9
tmnxSASLogGroups	1.3.6.1.4.1.6527.6.2.2.1.9.1
tmnxSASLogObjs	1.3.6.1.4.1.6527.6.2.2.2.14
tmnxSASLogGlobObjs	1.3.6.1.4.1.6527.6.2.2.2.14.1
INT tmnxDygGaspPriLogId	1.3.6.1.4.1.6527.6.2.2.2.14.1.1	INTEGER	read-write	Primary SNMP trap group number to which dying gasp trap needs to be sent. An entry with this id and tmnxDygGaspPriTgtName has to exist in tmnxSnmpTrapDestEntry before tmnxDygGaspPriLogId can be set
STR tmnxDygGaspPriTgtName	1.3.6.1.4.1.6527.6.2.2.2.14.1.2	SnmpAdminString	read-write	Primary SNMP trap target to which dying gasp trap needs to be sent. An entry with this name and tmnxDygGaspPriLogId has to exist in tmnxSnmpTrapDestEntry before tmnxDygGaspPriTgtName can be set
INT tmnxDygGaspSecLogId	1.3.6.1.4.1.6527.6.2.2.2.14.1.3	INTEGER	read-write	Secondary SNMP trap group number to which dying gasp trap needs to be sent. An entry with this id and tmnxDygGaspSecTgtName has to exist in tmnxSnmpTrapDestEntry before tmnxDygGaspSecLogId can be set
STR tmnxDygGaspSecTgtName	1.3.6.1.4.1.6527.6.2.2.2.14.1.4	SnmpAdminString	read-write	Secondary SNMP trap target to which dying gasp trap needs to be sent. An entry with this name and tmnxDygGaspSecLogId has to exist in tmnxSnmpTrapDestEntry before tmnxDygGaspSecTgtName can be set
INT tmnxDygGaspTerLogId	1.3.6.1.4.1.6527.6.2.2.2.14.1.5	INTEGER	read-write	Tertiary SNMP trap group number to which dying gasp trap needs to be sent. An entry with this id and tmnxDygGaspSecTgtName has to exist in tmnxSnmpTrapDestEntry before tmnxDygGaspTerLogId can be set
STR tmnxDygGaspTerTgtName	1.3.6.1.4.1.6527.6.2.2.2.14.1.6	SnmpAdminString	read-write	Tertiary SNMP trap target to which dying gasp trap needs to be sent. An entry with this name and tmnxDygGaspTerLogId has to exist in tmnxSnmpTrapDestEntry before tmnxDygGaspTerTgtName can be set
tmnxLogApExtnTable	1.3.6.1.4.1.6527.6.2.2.2.14.1.7		not-accessible
tmnxLogApExtnEntry	1.3.6.1.4.1.6527.6.2.2.2.14.1.7.1		not-accessible
T/F tmnxLogApLogMemory	1.3.6.1.4.1.6527.6.2.2.2.14.1.7.1.1	TruthValue	read-create	This parameter specifies if Accounting record policy records are cached in order to reduce frequent flash write operations
TLO tmnxLogApLogMemSize	1.3.6.1.4.1.6527.6.2.2.2.14.1.7.1.2	TLogMemSize	read-only	This parameter is a read only object specifying the log memory size that is currently in use

RFC description

Nokia/Alcatel-Lucent TimeT vendor-private MIB for logging and event management in Service Assurance Server (SAS) systems.

Start monitoring Nokia/Alcatel-Lucent 7210 SAS switches (event-logging destination/target config 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.

Download TIMETRA-SAS-LOG-MIB

What Is TIMETRA-SAS-LOG-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description