E7-Notifications-MIB

Description: Notification definitions for the Calix E7 access platform covering system and service event traps.

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.

E7-Notifications-MIB defines the trap/notification objects for the Calix E7 access platform family (E7, E5-400, E5-312), which are broadband access/aggregation systems used by service providers. Rather than exposing polled runtime data tables, this module defines the varbind objects carried within traps: a sequence number, alarm type, alarm status (raise/clear), the object class and up to several instance identifiers pinpointing which managed object triggered the event. Its monitoring value is entirely fault/event-oriented: it lets a management system correlate an incoming trap to a specific alarm type and severity and to the exact hardware or service object instance affected (e.g., a specific card, port, or service), which is how hardware faults and service-affecting events on the E7 platform are surfaced in near-real time. This module depends on the broader Calix E7 enterprise MIB tree that defines the objects referenced by e7TrapObjectClass/e7TrapObjectInstance. It is deployed on Calix E7, E5-400, and E5-312 access platforms in service-provider access networks, feeding alarms to an EMS/NMS. Engineers can download the E7-Notifications-MIB file directly to load it into their MIB browser.

A management system receiving a trap would read e7TrapSequenceNo to order events, e7TrapAlarmType and e7TrapAlarmStatus to determine what kind of alarm fired and whether it is being raised or cleared, and e7TrapObjectClass together with the e7TrapObjectInstance1 through e7TrapObjectInstance8 fields to identify exactly which object instance (e.g., a specific line card or port) is affected. A sequence of raise-then-clear traps for the same object class/instance pair would show an admin that a transient fault (e.g., a card reset) occurred and self-resolved, versus a raised alarm with no matching clear indicating an ongoing fault needing attention.

Vendor-private MIB for E7 platform notification management; defines trap and notification objects for system alerts and event reporting.