All MIBs › ADTRAN-AOS-MUX-MIB
Organization: ADTRAN, Inc.
Last Updated: 2004-10-15
Category: Vendor: ADTRAN
Description: Manages multiplexing configuration and channel status on ADTRAN AOS multiservice access devices.
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 ADTRAN-AOS-MUX-MIB?
This MIB module is part of ADTRAN's AOS (Adtran Operating System) product line and manages time-division multiplexing (TDM) configuration and cross-connect mapping on multiservice access devices. It exposes configuration data describing how TDM channels/timeslots are cross-connected between interfaces, subinterfaces, and DS0 groups. Administrators use it primarily to verify the software configuration of TDM cross-connects rather than hardware health per se, though the cross-connect index and status tables can reveal misconfigured or broken circuit mappings behind a service outage. It builds on ADTRAN's proprietary AOS enterprise MIB tree and assumes standard interface-indexing conventions (as in IF-MIB) for referencing the physical/logical interfaces involved. It is typically deployed on ADTRAN multiservice routers and access devices carrying legacy TDM/T1/E1 traffic alongside IP services, where ADTRAN-AOS-MUX-MIB SNMP monitoring verifies cross-connect mappings remain intact.
IPNetwork Monitor allows you to monitor SNMP objects defined in ADTRAN-AOS-MUX-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
- ADTRAN AOS multiservice access router
- ADTRAN TDM/T1/E1 access device
Monitoring Examples
An administrator polling adGenAOSXConnectTable would examine adGenAOSXConnectFirstIfType, adGenAOSXConnectFirstIfSlot, and adGenAOSXConnectFirstIfPort together with adGenAOSXConnectFirstTdmGroup and adGenAOSXConnectFirstTdmGroupDS0 to confirm which physical slot/port and DS0 timeslot group are cross-connected to a circuit. If adGenAOSXConnectSecondIfType shows an unexpected value or the entry is missing entirely, it indicates a TDM cross-connect was never provisioned or was torn down, explaining a T1/E1 circuit outage.
What Can Be Monitored
- TDM cross-connect mappings
- cross-connect first/second interface type
- slot and port assignment
- TDM group and DS0 timeslot assignment
Imported Objects
From ADTRAN-AOS
| adGenAOSCommon | OBJECT-IDENTITY |
| adGenAOSConformance | OBJECT-IDENTITY |
From ADTRAN-MIB
| adIdentity | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| RowStatus |
OIDs
RFC description
TDM multiplexing and cross-connect configuration for ADTRAN AOS platforms.
Start monitoring ADTRAN NetVanta/SDG-series AOS devices 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.