All MIBs › KENYA-COMPONENT-TRAPS
Category: Alarm and Event Management, Hardware and Environment
Description: MIB defining SNMP trap notifications for hardware component failures and state changes in KENYA platform network 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 KENYA-COMPONENT-TRAPS?
KENYA-COMPONENT-TRAPS is a MIB defining trap notifications and supporting status objects for internal software-component health checks within a network management/data-collection platform (indicated by object names like nmDataCollector, procRespawner, and nmsGolbalStatusProcessor). It exposes objects describing failed SNMP polling attempts (snmpFailedComponent, snmpRequestedOid), process-respawn events (prMissingProcName, prRespawnCommand), and self-test/diagnostic results (dcCheckedOid, dcErrorString, dcTestDescr, dcSystemErrorDate) along with a general trapSeverity indicator. This is fundamentally a software/process health MIB: it monitors whether internal monitoring processes and data collectors are alive and functioning correctly, and generates traps when a required process has died and had to be respawned, or when an SNMP check against a target OID has failed — service/process status rather than hardware sensor data. It appears to be an internal component of a larger network management system (the collector/respawner architecture) rather than a device-facing MIB, so it may have implicit dependencies on that platform's own object model. It is deployed on network management servers/data collectors to self-monitor their own component health and alert operators to internal failures. Engineers can download the KENYA-COMPONENT-TRAPS file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in KENYA-COMPONENT-TRAPS. 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
- network management server / SNMP data-collection platform (vendor-neutral, internal monitoring component, not a network device itself)
Monitoring Examples
An operator monitoring the management platform itself can watch for traps carrying trapSeverity alongside prMissingProcName and prRespawnCommand to learn which internal process died and how it was restarted, and check snmpFailedComponent/snmpRequestedOid to see which target device or OID a data collector failed to poll. dcSystemErrorDate and dcErrorString provide the timestamp and detail of a failed self-test (dcCheckedOid) run by the system requirement checker (dcSystemRequirement).
What Can Be Monitored
- failed SNMP poll target/OID
- process respawn events and command used
- trap severity of internal alerts
- self-test/diagnostic error details and timestamp
Imported Objects
From KENYA-COMPONENT-MIB
| nmSoftwares | OBJECT-IDENTITY |
| pxSoftwares | OBJECT-IDENTITY |
| scSoftwares | OBJECT-IDENTITY |
From RFC-1215
| TRAP-TYPE |
From RFC1155-SMI
| OBJECT-TYPE |
From VOLUBILL-ROOT-MIB
| vlbComponents | OBJECT-IDENTITY |
| volubill | OBJECT-IDENTITY |
OIDs
RFC description
Defines trap objects for component monitoring on Kenya systems, including data collector errors and process respawner notifications.
Start monitoring Network management server/SNMP data-collection platform (internal process health) 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.