All MIBs › KENYA-COMPONENT-MIB
Category: Hardware and Environment
Description: MIB for managing hardware component inventory and status for equipment produced by a network device manufacturer using the KENYA platform.
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-MIB?
KENYA-COMPONENT-MIB is a vendor MIB for managing hardware component inventory and status on equipment built on the "KENYA" platform, organized around functional units such as LMS (license management server), Proxy, and Billing components. It exposes global activation and status objects for each logical unit (lmsUnitGlobalStatus, proxyUnitGlobalStatus, lmsUnitActivation, proxyUnitActivation) alongside software resource usage metrics. Its monitoring focus is squarely on software/process health: proxyUnitScagentCpuUse, proxyUnitScagentMemoryUse, proxyUnitHttpdCpuUse, and proxyUnitHttpdMemoryUse let an operator track CPU and memory consumption of the proxy's internal service-control agent and HTTP daemon processes, directly surfacing resource exhaustion or runaway processes. No explicit dependency on other standard MIBs is evident from the available definitions, suggesting a largely self-contained vendor schema. It would be deployed on a bay/chassis-style access or billing-and-proxy platform where LMS, proxy, and billing subsystems run as separate managed components, as defined in the KENYA-COMPONENT-MIB MIB.
IPNetwork Monitor allows you to monitor SNMP objects defined in KENYA-COMPONENT-MIB. 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 devices/appliances built on the KENYA platform (bay/chassis-style access or billing-and-proxy systems)
Monitoring Examples
An operator would poll proxyUnitScagentCpuUse and proxyUnitHttpdCpuUse together to detect when the proxy component's control agent or web server process is consuming excessive CPU, a sign of a runaway process or overload. proxyUnitGlobalStatus and proxyUnitActivation would be checked to confirm the proxy subsystem is active and healthy before drilling into resource metrics. Similarly, lmsUnitGlobalStatus and lmsUnitActivation would be polled to verify the license management server component is up, since a down LMS unit could explain downstream licensing or billing failures under the isBilling/isLms subtrees.
What Can Be Monitored
- LMS unit global status and activation
- proxy unit global status and activation
- proxy service-control agent CPU/memory use
- proxy HTTP daemon CPU/memory use
- billing subsystem status
Imported Objects
From RFC1155-SMI
| OBJECT-TYPE |
From SNMPv2-SMI
| Integer32 | |
| IpAddress |
From VOLUBILL-ROOT-MIB
| vlbComponents | OBJECT-IDENTITY |
OIDs
RFC description
SNMP MIB module for managing component-level information and metrics on Kenya-based network devices or infrastructure equipment. Provides access to hardware component status and operational data.
Start monitoring Network device/appliance built on the KENYA platform (LMS/proxy/billing components) 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.