All MIBs › STN-LOG-MIB
Organization: Spring Tide Networks, Inc.
Last Updated: 2000-02-16
Category: Spring Tide Networks
Description: Manages Spring Tide Networks event log configuration, severity filtering, and log destination settings.
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 STN-LOG-MIB?
STN-LOG-MIB is a proprietary Spring Tide Networks MIB for configuring the event logging subsystem on the vendor's IP services switch platform, covering log severity filtering and log destination settings. It exposes primarily configuration objects rather than the log messages themselves, letting an operator control what gets logged and where. Its monitoring relevance is indirect: verifying the logging configuration is correctly set (appropriate severity threshold, valid destination) ensures that subsequent fault/event traps and diagnostic messages are actually captured, which underpins broader software and hardware fault monitoring on the device. It likely complements the standard SNMPv2 notification framework and possibly syslog-style (RFC 3164) conventions for its destination settings. Typical deployment is on Spring Tide IP services switches where administrators need to confirm event logging is active and properly scoped before relying on it for fault diagnosis. Engineers can download the STN-LOG-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in STN-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
- Spring Tide Networks IP services switch
Monitoring Examples
No sample object or table names were provided in the source data for this module; based on the short description, a realistic use would be checking the configured log severity filter and destination objects to confirm critical/error-level events are being sent to the intended log server, since a misconfigured severity threshold could silently suppress important fault events.
What Can Be Monitored
- log severity filter level
- log destination configuration
Imported Objects
From SNMPv2-CONF
| MODULE-COMPLIANCE |
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString | |
| TruthValue |
| stnNotification | OBJECT-IDENTITY |
| stnSystems | OBJECT-IDENTITY |
From STN-CHASSIS-MIB
| stnEngineCpu | OBJECT-TYPE |
| stnEngineIndex | OBJECT-TYPE |
| stnEngineSlot | OBJECT-TYPE |
OIDs
RFC description
Spring Tide Networks event logger MIB managing system logging state, message delivery, and log configuration.
Start monitoring Spring Tide Networks (Lucent) IP services switch (event-logging config) 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.