All MIBs › TN-TC
Category: Enterprise SMI and Textual Conventions, Network Management Infrastructure, Nokia Carrier Ethernet, Transition Networks Media Converters
Description:
Defines Transition Networks textual conventions shared across TN media converter MIB modules.
Imported Objects
From SNMPv2-SMI
| Gauge32 | |
| Integer32 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
What Is TN-TC?
TN-TC is a textual-conventions-only MIB module published by Transition Networks, a manufacturer of media converters and Ethernet extension equipment, defining shared data types and enumerations reused across that vendor's family of device-specific MIB modules. It contains no object definitions of its own tables or scalars; instead it standardizes things like status enumerations, port-type conventions, or alarm-severity codes so that multiple Transition Networks MIBs can reference a single, consistent type definition. Its role in monitoring is indirect: by supplying the shared vocabulary for status and configuration values, it underlies the hardware/software status reporting done in the vendor's other MIBs (for example media converter port link state, optical signal status, or environmental alarms). It is a dependency consumed by other Transition Networks enterprise MIB modules rather than something with its own standards dependency, and there is no meaningful TN-TC OID to poll on its own since every definition here is a textual convention consumed by name. It is typically loaded automatically as a prerequisite whenever an NMS compiles any Transition Networks device MIB for media converters, switches, or NIDs.
IPNetwork Monitor allows you to monitor SNMP objects defined in TN-TC. 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
- Transition Networks media converter/switch/NID product line, entire range (shared textual conventions)
Monitoring Examples
No sample objects or module description text were provided in the source data, consistent with this being a pure textual-conventions module with no scalars or tables of its own. As such there is no direct monitoring scenario to describe here -- an admin would never poll TN-TC itself, but an NMS must successfully compile it before loading any Transition Networks device MIB that imports its type definitions. Its practical value is ensuring consistent decoding of status/enumeration values (e.g. port or alarm states) reported by those dependent MIBs.
RFC description
Textual Conventions MIB for Telecommunications equipment defining reusable SNMP data types and conventions used by vendor telecommunications MIBs.
Start monitoring Transition Networks media converter/switch/NID product line, entire range (shared textual conventions) 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.