CISCO-HEALTH-MONITOR-MIB.mib object view, vendor Cisco
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-HEALTH-MONITOR-MIB and use it to monitor vendor specific OID's.
CISCO-HEALTH-MONITOR-MIB file content
Object view of CISCO-HEALTH-MONITOR-MIB:
| Scalar Object |
| ciscoHealthMonitorEntry |
.1.3.6.1.4.1.9.9.243.1.1.1 |
|
A Health Monitor statistics entry.
The entPhysicalIndex identifies the physical entity (chassis
or container), while the ciscoHealthMonitorSubsysName
identifies by name the appropriate subsystem for which these
statistics apply.
If there are other entities such as peer routers or line
cards then, in the context of this MIB, these are also
defined to be in the same system. If these entities also
run an instance of the Health Monitor then the summary
information from the distributed Health Monitors is
obtained here.
|
| Tabular Object |
| ciscoHealthMonitorSubsysName |
.1.3.6.1.4.1.9.9.243.1.1.1.1 |
|
A textual string containing the name of the hardware or
software subsystem. A management station wishing to obtain
summary statistics for a physical entity should use a value
of 'summary' for this object.
|
| ciscoHealthMonitorHealth |
.1.3.6.1.4.1.9.9.243.1.1.1.2 |
|
The computed current health of this subsystem on the
specified entity.
This health metric is based on predefined rules that
specify how the health should be adjusted in response to
certain events of varying severity and frequency. As these
events are encountered by each subsystem or physical entity,
the appropriate rules are applied and the health is modified
accordingly.
|
| ciscoHealthMonitorHealthNotifyEnable |
.1.3.6.1.4.1.9.9.243.1.1.1.3 |
|
Enables or disables health level notifications. When set
to true(1), the ciscoHealthMonitorHealthLevel notification
is enabled. When set to false(0), the
ciscoHealthMonitorHealthLevel notification is disabled.
If such a notification is desired, it is the responsibility of
the management entity to ensure that the SNMP administrative
model is configured in such a way as to allow the notification
to be delivered.
|
| ciscoHealthMonitorHealthNotifyHighThreshold |
.1.3.6.1.4.1.9.9.243.1.1.1.4 |
|
Specifies the health level at which a
ciscoHealthMonitorHealthLevel notification will be
generated for the specified subsystem and entity.
A notification will only be generated if the health
level had previously reached the low threshold level
prior to reaching this high threshold level.
Health levels oscillating within the high and the low
threshold levels do not generate notifications.
A health level going from low threshold (or below)
to high threshold (or above) represents a return
to normal health for the specified subsystem.
Set your optimal health level to this threshold.
|
| ciscoHealthMonitorHealthNotifyLowThreshold |
.1.3.6.1.4.1.9.9.243.1.1.1.5 |
|
Specifies the health level at which a
ciscoHealthMonitorHealthLevel notification will be
generated for the specified subsystem and entity.
A notification will only be generated if the health
level had previously reached the high threshold level
prior to reaching this low threshold level.
Health levels oscillating within the high and the low
threshold levels do not generate notifications.
A health level going from high threshold (or above)
to low threshold (or below) represents a deterioration
of the health for the specified subsystem.
Set your unacceptable health level to this threshold.
|
| ciscoHealthMonitorCatastrophicFaults |
.1.3.6.1.4.1.9.9.243.1.1.1.6 |
|
The number of catastrophic faults that have occurred in
this subsystem on the specified entity since the system
was initialized.
|
| ciscoHealthMonitorCriticalFaults |
.1.3.6.1.4.1.9.9.243.1.1.1.7 |
|
The number of critical faults that have occurred in this
subsystem on the specified entity since the system was
initialized.
|
| ciscoHealthMonitorHighSeverityFaults |
.1.3.6.1.4.1.9.9.243.1.1.1.8 |
|
The number of high severity faults that have occurred in
this subsystem on the specified entity since the system
was initialized.
|
| ciscoHealthMonitorMediumSeverityFaults |
.1.3.6.1.4.1.9.9.243.1.1.1.9 |
|
The number of medium severity faults that have occurred in
this subsystem on the specified entity since the system
was initialized.
|
| ciscoHealthMonitorLowSeverityFaults |
.1.3.6.1.4.1.9.9.243.1.1.1.10 |
|
The number of low severity faults that have occurred in
this subsystem on the specified entity since the system
was initialized.
|
| ciscoHealthMonitorPositiveEvents |
.1.3.6.1.4.1.9.9.243.1.1.1.11 |
|
The number of positive events that have occurred in this
subsystem on the specified entity since the system was
initialized.
|
| Table |
| ciscoHealthMonitorTable |
.1.3.6.1.4.1.9.9.243.1.1 |
|
This table contains Health Monitor statistics for physical
entities and their constituent hardware and/or software
subsystems.
The Health Monitor statistics present in each row provide
information such as the computed health of the indicated
subsystem and the number of faults it has experienced.
|
| Trap |
| ciscoHealthMonitorHealthLevel |
.1.3.6.1.4.1.9.9.243.0.1 |
|
A ciscoHealthMonitorHealthLevel notification is sent when
the health of a subsystem reaches either the
ciscoHealthMonitorHealthNotifyLowThreshold or
ciscoHealthMonitorHealthNotifyHighThreshold threshold
as described above.
|
| Object Identifier |
| ciscoHealthMonitorMIB |
.1.3.6.1.4.1.9.9.243 |
|
Health Monitor MIB module.
The Health Monitor uses a model based on events of varying
severity and frequency, and predefined rules, to generate
a metric that represents a system's (and its subsystems')
level of health.
The events are typically internally generated notifications
in response to detrimental or correctional changes in the
state of the hardware or software of the system. Detrimental
events are classified under one of the following severity
levels:
Catastrophic - Causes or leads to system failure
Critical - Major subsystem or functionality failure
High - Potential for major impact to important
functions
Medium - Potential for minor impact to functionality
Low - Negligible impact to functionality
Whilst correctional events fall under the following
classification:
Positive - Not a fault event. May cause or lead to
the return of functionality
This MIB module provides information for tracking occurrences
of the above events, and presents the associated health
metric for the system and its component subsystems.
|
| ciscoHealthMonitorMIBObjects |
.1.3.6.1.4.1.9.9.243.1 |
| ciscoHealthMonitorMIBNotifs |
.1.3.6.1.4.1.9.9.243.0 |
| ciscoHealthMonitorMIBConform |
.1.3.6.1.4.1.9.9.243.2 |
| ciscoHealthMonitorMIBCompliances |
.1.3.6.1.4.1.9.9.243.2.1 |
| ciscoHealthMonitorMIBGroups |
.1.3.6.1.4.1.9.9.243.2.2 |
| Group |
| ciscoHealthMonitorGroup |
.1.3.6.1.4.1.9.9.243.2.2.1 |
|
The collection of objects providing health information.
|
| ciscoHealthMonitorMIBNotificationGroup |
.1.3.6.1.4.1.9.9.243.2.2.2 |
|
Set of notifications implemented in this module.
|
