All MIBs › TN-LOG-MIB
Organization: Nokia
Last Updated: 2012-12-05
Category: Network Management Infrastructure, Nokia Carrier Ethernet
Description: Manages Nokia carrier Ethernet event log configuration, destinations, and filter policies.
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 TN-LOG-MIB?
TN-LOG-MIB (despite its generic name, actually branded as tnEventAppTable/tnSRLogObjs) is a Nokia proprietary SNMP module for managing the event logging utility on Nokia 7x50-series service routers, part of Nokia's carrier Ethernet/IP product line. It exposes configuration data describing logging applications, such as an indexed table of event application names used to categorize and filter log/event sources on the router. Its monitoring relevance is centered on software-side operational status: tracking which logging applications are registered and active helps confirm that fault and event reporting subsystems are functioning, rather than exposing hardware sensors directly. It depends on the broader Nokia event/log and SR (service router) MIB family for actual log record content and severity data. It is deployed in service provider and carrier networks running Nokia 7x50 routers where centralized event logging and alerting is required for operations visibility. Engineers can download the TN-LOG-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TN-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 1830 PSS (Photonic Service Switch) optical transport platform
Monitoring Examples
An administrator would poll tnEventAppTable, keyed by tnEventAppIndex, to enumerate configured logging application names (tnEventAppName) and confirm that expected subsystems (e.g. routing, security) are registered as event sources. A missing or unexpectedly absent entry in this table could indicate that a logging application failed to initialize after a reboot or software upgrade, which would be a signal to check the associated tnSRLogObjs branch for further detail.
What Can Be Monitored
- registered logging application names
- logging application index assignments
- event source configuration presence
Imported Objects
From INET-ADDRESS-MIB
| InetAddress |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString | |
| SnmpSecurityLevel |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-MIB
| sysObjectID | OBJECT-TYPE |
From SNMPv2-SMI
| Counter32 | |
| Counter64 | |
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
From TN-FILTER-MIB
| TFilterActionOrDefault |
From TN-TC-MIB
| TNamedItem |
From TROPIC-GLOBAL-REG
| tnSRMIBModules | OBJECT-IDENTITY |
| tnSRObjs | OBJECT-IDENTITY |
From TROPIC-SYSTEM-MIB
| tnSysSwitchId | OBJECT-TYPE |
OIDs
RFC description
Triplet Node logging MIB; manages event logging, syslog, and diagnostic logging on Triplet communication systems.
Start monitoring Nokia 7x50 series service router (event-logging application registration 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.