CISCO-UNIFIED-COMPUTING-EVENT-MIB

Description: MIB for event logging policy and condition management on Cisco UCS, tracking event codes, severity, cause, action indicators, and event endpoint control levels for audit and alerting

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.

CISCO-UNIFIED-COMPUTING-EVENT-MIB is part of the Cisco UCS MIB family and models the internal event-logging and alerting subsystem of UCS Manager, covering event codes, severity, cause, and administrative control over event endpoints. It exposes configuration for how strictly/verbosely events are captured at given control points (endpoint control level and revert timeout) and maintains holders that reference logged events. This MIB supports fault and audit monitoring rather than raw hardware sensor data: it lets an operator understand what event-logging policy is in force and, via associated event objects, review the severity/cause/action indicators tied to significant UCS domain occurrences (hardware faults, configuration changes, etc.). It relies on the shared Cisco UCS object-model conventions (Dn, Rn, instance ID) common to the whole CISCO-UNIFIED-COMPUTING-* family and complements the fault/status data produced by other UCS hardware MIBs. It is used exclusively within Cisco UCS domains for audit trails and alerting configuration, typically consumed by UCS-aware monitoring integrations alongside UCS Manager's own fault summary. Engineers can download the CISCO-UNIFIED-COMPUTING-EVENT-MIB file directly to load it into their MIB browser.

An administrator would poll cucsEventEpCtrlTable/cucsEventEpCtrlEntry to check cucsEventEpCtrlLevel (the configured event verbosity/control level) and cucsEventEpCtrlRevertTimeout for a given endpoint, confirming that event logging has not been left in an unexpectedly restrictive or verbose state after a maintenance change. cucsEventHolderTable/cucsEventHolderEntry, identified by cucsEventHolderDn, would be checked to see which managed objects currently have events attached, helping correlate a recent hardware fault with its logged event record. This MIB is more about event-policy and holder bookkeeping than a raw sensor-reading table.

Event and condition management for Cisco Unified Computing System infrastructure monitoring.