MITEL-MN3100-T1-TRAP-MIB

Description: Defines MITEL MN3100 T1 interface trap notifications for line alarms.

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.

MITEL-MN3100-T1-TRAP-MIB is a vendor-specific MIB from Mitel Networks defining SNMP trap/notification objects for T1 line alarm conditions on the MN3100 platform, which is associated with Mitel's IP-PBX/call-server product line (referenced via mitelIdCsIpera1000). Rather than exposing polled runtime counters, its scope is centered on identification objects and fault notifications, so its data category is primarily faults/traps for T1 interface alarms. Its monitoring role is to alert administrators in near real time to T1 line-level hardware problems, such as loss of signal, alarm indication signal, or frame slips, which affect voice trunk availability on the call server. As a T1-specific trap MIB it likely depends on or complements standard DS1/T1 MIB definitions (e.g., RFC 3895's DS1-MIB) for the underlying interface counters that trigger these traps. It would typically be deployed on Mitel MN3100/Ipera 1000-based call server systems where T1 trunks carry PSTN voice traffic and rapid trap-based alerting is important for telephony service assurance, and administrators can download the MITEL-MN3100-T1-TRAP-MIB file to load its trap definitions into their NMS.

The sample objects available (mitel, mitelProprietary, mitelIdentification, mitelIdCallServers, mitelIdCsIpera1000) are identification/registration nodes rather than runtime data objects, consistent with a trap-oriented MIB whose real content is its NOTIFICATION-TYPE definitions for T1 alarms. An administrator would configure their NMS to receive these T1 alarm traps from an MN3100/Ipera 1000 call server to be alerted the moment a T1 span goes into alarm (e.g., red alarm/loss of signal), rather than relying on periodic polling. No polled counter tables are represented in the available sample objects, so a granular polling scenario cannot be constructed beyond the trap-alert use case.

MITEL Mn3100 T1/E1 line status change traps and monitoring for telephony systems.