A3COM0024-EVENT-EXTENSION

Description: Extends RMON event and alarm objects for 3Com device-specific notification handling.

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.

This MIB extends the standard RMON event and alarm MIB with 3Com-specific event-action objects, adding vendor-defined behavior when an RMON alarm fires. It exposes an extended event table with an eventAction object specifying what the device should do (beyond the standard log/trap actions) when a monitored alarm condition triggers. Its monitoring role is indirect: it doesn't expose new hardware counters itself, but rather governs how the device responds to threshold-crossing events already being monitored via RMON alarms/statistics on interface or other performance counters. It directly depends on and extends the IETF RMON MIB (RFC 2819) event/alarm mechanism, requiring RMON to already be configured and running. It's deployed on 3Com switches/routers that support RMON-based threshold alerting. Engineers can download the A3COM0024-EVENT-EXTENSION file directly to load it into their MIB browser.

An admin configuring an RMON alarm on an interface error counter would set extEventTable's eventAction for the corresponding extEventEntry to define the vendor-specific response beyond a standard SNMP trap, then verify via the same table that the intended action is correctly bound to that RMON event, ensuring the device reacts appropriately (not just logs) when the threshold is crossed.

Extends RMON event functionality with custom event generation and configuration capabilities for 3Com devices.