All MIBs › EthernetSubagentPvt-MIB
Category: Network Interfaces
Description: Defines private Ethernet subagent objects for vendor-specific Ethernet interface management.
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 EthernetSubagentPvt-MIB?
This is a vendor-specific private MIB defining objects for an SNMP subagent architecture used to manage Ethernet-related agent processes on a network device, rather than describing the Ethernet interfaces themselves. It exposes process-level management data: agent/process names, process state, running software version, program file path, process priority, and process/group/user IDs, plus references to primary and backup CPU modules. Its clear emphasis is on software/process health monitoring — zesaAgentState and zesaProcessName/zesaProcessVersion let an operator confirm the SNMP subagent process is alive and running the expected version, and zesaPrimaryCPU/zesaBackupCPU/zesaPrimaryPIN/zesaBackupPIN expose the redundant CPU hardware backing that subagent. No module description text was available, and the object naming (zesa-prefixed) suggests a narrowly-scoped OEM/vendor implementation with no explicit dependency on other standard MIBs beyond the base SNMP framework. It would typically be deployed on modular/chassis-based network equipment where redundant supervisor/CPU modules host distributed SNMP subagents for Ethernet management functions. Engineers can download the EthernetSubagentPvt-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in EthernetSubagentPvt-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
- Tandem Computers/HP NonStop fault-tolerant server — Enterprise OID 169 resolves to Tandem Computers Inc, and the module's primary/backup-CPU redundancy model matches Tandem NonStop's fault-tolerant dual-CPU architecture — not a generic unnamed 'vendor-specific chassis network equipment' as previously described.
Monitoring Examples
An admin would poll zesaAgentState and zesaProcessName to verify the Ethernet management subagent process is running, and check zesaProcessVersion against the expected build to catch a stale or mismatched software load after an upgrade. zesaPrimaryCPU and zesaBackupCPU with their zesaPrimaryPIN/zesaBackupPIN identify which physical CPU module is currently active versus standby, useful for confirming failover status on redundant hardware. zesaProcessPriority, zesaProcessGroupID, and zesaProcessUserID give low-level OS process context useful for debugging resource contention.
What Can Be Monitored
- subagent process name/state
- process software version
- process priority
- process group/user ID
- primary/backup CPU identity
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC-1215
| TRAP-TYPE |
From RFC1155-SMI
| Counter | |
| private |
From RFC1213-MIB
| DisplayString |
OIDs
RFC description
Tandem Ethernet subagent configuration MIB for managing SNMP subagent process state and Ethernet agent parameters.
Start monitoring Tandem Computers/HP NonStop fault-tolerant server (Ethernet SNMP subagent, dual-CPU redundant) 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.