All MIBs › NBS-OTNOH-MIB
Organization: NBS
Last Updated: 2012-12-20
Category: Optical Networking
Description: Manages OTN overhead bytes and section/path overhead configuration on NBS optical transport equipment.
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 NBS-OTNOH-MIB?
NBS-OTNOH-MIB is a private MRV/NBS MIB that models overhead byte fields used in OTN and SONET framing, specifically the Trail Trace Identifier (TTI) fields exchanged between transport network endpoints. It exposes configuration and status data for the sent and expected Source/Destination Access Point Identifiers (SAPI/DAPI) and operator-specific fields on each optical interface. In monitoring terms, it is used to verify that overhead-level path/section identity information matches between transmit and receive ends, catching TTI mismatches that indicate misprovisioned fiber connections or unintended cross-connects on the optical transport layer. It depends on the ITU-T G.709 OTN and SONET/SDH overhead standards it represents in SNMP form. It is deployed on NBS/MRV optical transport network elements used in metro and long-haul carrier networks. Engineers can download the NBS-OTNOH-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in NBS-OTNOH-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
- MRV/NBS optical transport network element
- OTN/SONET carrier equipment
Monitoring Examples
An operator would check nbsOtnohTtiTable/nbsOtnohTtiEntry per nbsOtnohTtiIfIndex, comparing nbsOtnohTtiSendSapi/nbsOtnohTtiSendDapi against nbsOtnohTtiExpectSapi/nbsOtnohTtiExpectDapi to confirm the received overhead matches what was configured as expected. A mismatch between sent and expected identifiers typically indicates a fiber patched to the wrong far-end port or an unplanned network change. The nbsOtnohTtiRowStatus and nbsOtnohTtiScope objects are used to provision and scope which overhead fields are actively monitored on a given interface.
What Can Be Monitored
- sent vs expected SAPI/DAPI identifiers
- operator-specific overhead fields
- TTI scope per interface
- overhead row provisioning status
Imported Objects
From IF-MIB
| InterfaceIndex |
From NBS-MIB
| nbs | OBJECT-IDENTITY |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| RowStatus |
OIDs
RFC description
Manages OTN/SONET overhead fields and Trail Trace Identifier (TTI) values for optical transport network interfaces.
Start monitoring MRV/NBS optical transport network element (OTN/SONET overhead/TTI) 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.