CISCO-ENTITY-DIAG-MIB: View SNMP OID List / Download MIB

This MIB module defines the managed objects that describe the online diagnostics capabilities supported by the physical entities contained by the system, including chassis, modules, ports, power supplies, fans, and sensors. In order to manage the online diagnostic capabilities supported by a physical entity, it must be represented by a conceptual row in the entPhysicalTable of the ENTITY-MIB (RFC-2737). GLOSSARY Boot-up Diagnostic - a diagnostic consisting of tests intended to be executed in a reasonable timeframe when a physical entity boots. Diagnostic - a suite of tests intended to exercise the functional integrity of a physical entity. Diagnostic Level - the degree of completeness that a diagnostic will exercise a physical entity. Field Diagnostic - a special suite of tests intended to exercise the functional integrity of a physical entity in a manner that is possible when a physical entity is operational or running an operational image. Field Diagnostic Image - an image supporting field diagnostics. A physical entity has to be loaded with a field diagnostic image before field diagnostics can be executed on the physical entity. Health Monitoring - the process of running special non-intrusive online tests periodically on a physical entity for the purpose of tracking the overall condition of a physical entity. On-Demand Diagnostic - a diagnostic intended to be executed immediately upon request. Offline Diagnostic - a diagnostic that consists of tests that are disruptive in nature, and thus requires the physical entity being evaluated to be taken offline for the duration. Online Diagnostic - a diagnostic that consists of tests that are not disruptive in nature, and thus can be done without taking the physical entity offline. Physical Entity - an identifiable physical resource, such as a chassis, line card, power supply, or communication port. See RFC-2737, 'Entity MIB (Version 2)', K. McCloghrie and A. Bierman. Scheduled Diagnostic - a diagnostic intended to execute at some time in the future. There exist two types of scheduled diagnostics: 1) one-shot, which execute only once; and 2) periodic, which executes at a specific interval. Test - an exercise intended to determine the functional integrity of a component comprising a physical entity (e.g., a port might support an internal loopback test). Diagnostic Job - Consists of a diagnostic suite (i.e., a collection of tests) to be executed by a physical entity.

A ceDiagBootUpFailedNotif is sent if the online diagnostic discovers a boot up failure for a physical entity.

A ceDiagHMThresholdReachedNotif is sent if the number of consecutive failure of a Health Monitoring test reaches the configured threshold.

A ceDiagHMTestRecoverNotif is sent when no error is detected for the first time on the same Health Monitoring test which previously triggered ceDiagHMThresholdReachedNotif.

A ceDiagScheduledTestFailedNotif is sent if a scheduled test failed.

This table describes the tests supported by each physical entity supporting online diagnostics. The table organizes tests into sets associated with the physical entity supporting those tests. The SNMP entity adds a set of tests corresponding to a physical entity upon detection of a physical entity supporting online diagnostics. The SNMP entity deletes a set of tests corresponding to a physical entity upon removal of the physical entity. The SNMP entity replaces a set of tests corresponding to a physical entity when the physical entity has been successfully loaded with a different image (e.g., the field diagnostic image).

The description of a single test supported by a corresponding physical entity.

This object indicates an arbitrary positive integer arbitrarily identifying the test.

This object indicates a human-readable description of the test. Examples include: 'Marching Pattern DRAM Test' 'Data Pins DRAM Test' 'Internal Loopback Test' 'External Loopback Test'

This object indicates a set of attributes characterizing the test: 'minimal' - indicates that this test will be executed during boot-up if ceDiagBootupLevel is set to 'minimal' or 'complete'. This test is also included in the minimal or complete test suites. 'complete' - indicates that this test will be executed during boot-up if ceDiagBootupLevel is set to 'complete'. This test is also included in the complete test suites. 'perPort' - indicates that this test is a executed for each port contained by the module. This test is also included in the perPort test suites. 'fatal' - indicates that if this test fails, then the diagnostic should fail indicating that a major error occurred. 'basicOnDemand' - indicates that this test will be run during the basic on demand job is run. 'standby' - indicates that this test can only be run if the physical entity is a standby unit and can only be executed from the standby unit. 'parallel' - indicates that this test can be executed in parallel with other tests without checking for resource availability. 'nonDisruptive' - indicates this test can be executed without disrupting the physical entity's normal operation. This test is also included in the nonDisruptive test suites. 'hmAlwaysEnabled' - indicates that a management application can not disable the use of this test for the purpose of health monitoring. 'hmFixedInterval' - indicates that a management application can not change the interval at which health monitoring executes this test. 'nonHM' - indicates that this test can not be used for health monitoring. 'proxy' - indicates that the test must be executed through a proxy. 'activeToStandby' - indicates that this test can only be run if the physical entity is a standby unit and can only be executed from the active unit. 'offline' - indicates that this test will not get a user confirmation when it is run. 'perDevice' - indicates that this test is a per device test. 'disruptive' - indicates that this test can be executed with disrupting the physical entity's normal operation. This test is also included in the disruptive test suites. Bits: 'nonDisruptive': 7, 'complete': 1, 'hmAlwaysEnable': 8, 'standby': 5, 'hmFixedInterval': 9, 'activeToStandby': 12, 'nonHM': 10, 'basicOnDemand': 4, 'proxy': 11, 'perDevice': 14, 'perPort': 2, 'offline': 13, 'fatal': 3, 'parallel': 6, 'minimal': 0, 'disruptive': 15.

This table describes the additional custom based attributes of the tests listed in ceDiagTestInfoTable. These are attributes which have been customized by the platform supporting the tests.

The description of a single custom based attribute for a test supported by a corresponding physical entity.

An arbitrary integer which identifies the custom based attribute of a test.

This object provides a textual description of the custom based attribute of this test.

This table describes the errors indicated by a system supporting online diagnostics.

The description of a single online error.

This object indicates an arbitrary positive integer arbitrarily identifying the error.

This object indicates a human-readable description of the error. Examples include: 'DIAG_SUCCESS' 'DIAG_FAILURE' 'DIAG_NOT_SUPPORT' 'DIAG_SKIPPED'

This object specifies the level that physical entities will execute their boot-up diagnostic.

This table supports online diagnostic control and status for each physical entity that supporting the feature. The SNMP entity adds a conceptual row to this table corresponding to a physical entity upon detection of a physical entity supporting online diagnostics. The SNMP entity deletes a conceptual row from this table corresponding to a physical entity upon removal of the physical entity.

Online diagnostic control and status for a single physical entity supporting the feature. Observe that this data may not be accurate if the corresponding cefcModuleOperStatus (see the CISCO-ENTITY-FRU-CONTROL-MIB for further details) has a value of 'boot'.

This object indicates the level that the physical entity executed its boot-up diagnostic.

This object specifies the desired image the physical entity should be running: 'operational' - the physical entity should be running the operational image. 'fieldDiagnostic' - the physical entity should be running the field diagnostic image. Enumeration: 'fieldDiagnostic': 2, 'operational': 1.

This object indicates the actual image the physical entity is running: 'operational' - the physical entity is running the operational image. 'fieldDiagnostic' - the physical entity is running the field diagnostic image. 'booting' - the physical entity is booting; that is, there is no way of determining what image the physical entity is running because it is currently booting. Enumeration: 'booting': 3, 'fieldDiagnostic': 2, 'operational': 1.

This object specifies a URL (see RFC-1630) that specifies the location of the field diagnostic image. The following list provides some examples of URLs for the field diagnostic: file://disk0:/images/fd001 Describes a file with the path '/images/fd001' on 'disk0:' accessed locally. ftp://pop-server/usr/bin/fd001 Describes a file with the path '/usr/bin/fd001' on the host 'pop-server' accessed via FTP. tftp://pop-server/tftpout/fd001 Describes a file with the path '/tftpout/fd001' on the host 'pop-server' accessed via TFTP.

This table contains the information about the current test executing on a physical entity.

A test which is currently executing on a particular physical entity.

This object indicates the method used to invoke the diagnostic that is executing this test.

This object specifies the number of errors the physical entities will allow before aborting an on demand diagnostic job. A value of '0' indicates that the an unlimited number of errors are allowed for the on demand diagnostic job.

This object specifies how the physical entities in the system are to proceed when they encounter an error during an on demand diagnostic job. 'continue' - indicates that the physical entities will continue executing the on demand job. 'stop' - indicates that the physical entities will abort the on demand job. Enumeration: 'continue': 1, 'stop': 2.

This object specifies the maximum number of iterations of an on demand job.

This table contains a list of on demand jobs currently in the system. A row in this table can be created by setting the corresponding instance of ceDiagOnDemandJobRowStatus to 'createAndGo'. A row can be deleted by setting the corresponding instance of ceDiagOnDemandJobRowStatus to 'destroy'. Once the job is completed the corresponding row is deleted from the table. The individual results of the tests executed by this job are updated in ceDiagTestPerfTable.

A on demand job currently executing on a particular physical entity which supports on demand diagnostics.

This object indicates the various system predefined test suites the on demand job can choose from. If the value of this object is 'none', this job will run the tests specified by ceDiagOnDemandJobTestList. If the value of this object is 'complete', 'minimal', 'nonDisruptive' or 'perPort' the value of ceDiagOnDemandJobTestList is ignored.

This object specifies the user specified diagnostic suite (i.e., a set of tests) to be executed by the corresponding physical entity. The set of tests supported by this physical entity are specified in ceDiagTestInfoTable.

This object specifies the list of ports to be exercised by the corresponding physical entity when executing the diagnostic suite specified for the job.

The status object used to manage the rows in this table. When set to active(1) the on demand job is submitted. When set to destroy(6) the on demand job is stopped. When the value of this object is 'active', values within this row cannot be modified, except by deleting and re-creating the row.

This table contains a list of scheduled jobs on the system. A row in this table can be created by setting the corresponding instance of ceDiagScheduledJobRowStatus to 'createAndGo'. A row can be deleted by setting the corresponding instance of ceDiagScheduledJobRowStatus to 'destroy'. Once the job is completed the corresponding row is deleted from the table. The individual results of the tests executed by this job are updated in ceDiagTestPerfTable.

A job currently scheduled on a particular physical entity.

An arbitrary non-zero integer value that uniquely identifies a single scheduled job with respect to a physical entity.

This object specifies the type of the scheduled job. 'scheduledOneShot' - the physical entity will invoke this job at the time specified by ceDiagScheduledJobStart. 'scheduledPeriodicDaily' - the physical entity will first invoke this job at the time specified by ceDiagScheduledJobStart and continue invoking it daily at the same time. 'scheduledPeriodicWeekly' - the corresponding physical entity will first invoke this job at the time and day of the week specified by ceDiagScheduledJobStart and ceDiagScheduledJobDayOfWeek, and continue to invoke it weekly at the same time and day. Enumeration: 'scheduledOneShot': 1, 'scheduledPeriodicWeekly': 3, 'scheduledPeriodicDaily': 2.

This object specifies when a scheduled job will be executed. If the value of ceDiagScheduledJobType is 'scheduledOneShot', then this object only applies to the first execution of the job. If the value of ceDiagScheduledJobType is 'scheduledPeriodicDaily' or 'scheduledPeriodicWeekly', then the first four octets of this objects should be zero. If the physical entity's job queue already contains a job scheduled for execution at this time, then the process of submitting the job will fail.

This object specifies the day of the week for a weekly periodic scheduled job. The value of of this object must be specified if the value of ceDiagScheduledJobType is 'scheduledPeriodicWeekly'. This value of this object is set to 'notApplicable' if the value of ceDiagScheduledJobType is 'scheduledOneShot' or 'scheduledPeriodicDaily'. Enumeration: 'monday': 2, 'tuesday': 3, 'friday': 6, 'wednesday': 4, 'thursday': 5, 'notApplicable': 8, 'sunday': 1, 'saturday': 7.

This object specifies the diagnostic suite (i.e., a set of tests) to be executed by the corresponding physical entity. The set of tests supported by this physical entity are specified in ceDiagTestInfoTable.

This object specifies the list of ports to be tested by the corresponding physical entity when executing the diagnostic suite specified for the job.

The status object used to manage the rows in this table. When set to 'active' the scheduled job is submitted. When set to destroy(6) the scheduled job is cleared. When the value of this object is 'active', values within this row cannot be modified, except by deleting and re-creating the row.

This object indicates the various system predefined test suites the on scheduled job can choose from. If the value of this object is 'none', this job will run the tests specified by ceDiagScheduledJobTestList. If the value of this object is 'complete', 'minimal', 'nonDisruptive' or 'perPort' the value of ceDiagScheduledJobTestList is ignored.

This table maintains data concerning the performance of tests executed by each physical entity supporting the online diagnostic feature. The table organizes tests into sets associated with the physical entity supporting those tests. The SNMP entity adds a set of tests corresponding to a physical entity upon detection of a physical entity supporting online diagnostics. The SNMP entity deletes a set of tests corresponding to a physical entity upon removal of the physical entity. The SNMP entity replaces a set of tests corresponding to a physical entity when the physical entity has been successfully loaded with a different image (e.g., the field diagnostic image).

Data concerning the performance of a single test.

This object indicates the result the last time this test was executed by the corresponding physical entity: 'unknown' - the corresponding physical entity has not executed the test. 'fail' - the test executed and detected at least one failure. 'pass' - the test executed without detecting a failure. 'skipped' - the test was skipped due to insufficient resources. Enumeration: 'fail': 2, 'unknown': 1, 'skipped': 4, 'pass': 3.

This object indicates the last error code of this test. Details of the non-zero error code can be found in the corresponding entry in ceDiagErrorInfoTable.

This object indicates the last time the corresponding physical entity executed this test. If the value of ceDiagTestPerfLastResult is 'unknown', then the value of this object is irrelevant.

This object indicates the first time the corresponding physical entity executed this test and it failed. The value of this object is irrelevant if the value of ceDiagTestPerfTotalFails is 0.

This object indicates the last time the corresponding physical entity executed this test and it passed. The value 0x0000010100000000 indicates that the corresponding physical entity has not passed this test yet.

This object indicates the last time the corresponding physical entity executed this test and it failed. If the value of ceDiagTestPerfTotalFails is 0, then the value of this object is irrelevant.

This object indicates the total number of times the corresponding physical entity has executed the test.

This object indicates the total number of times the corresponding physical entity has executed the test and the test resulted with a failure.

This object indicates the consecutive number of times the corresponding physical entity has executed the test and it has failed. The value of this object will be reset to '0' when the physical entity executes the test and it succeeds.

This object indicates the testing method used for the last time this test was executed by the corresponding physical entity.

This object specifies whether the system will generate syslog messages due to the tests run by health monitor.

This table describes attributes specific to the health monitor for tests supported by a physical entity.

The attributes of a single test specific to the health monitor.

This object specifies whether this test is enabled for health monitor.

This object indicates the minimum interval which the health monitor can periodically invoke this test.

This object indicates the default interval which the health monitor will periodically invoke this test. A value of '0' indicates that the health monitor will not invoke the test.

This object specifies the interval at which the health monitor periodically invokes this test. A value of '0' indicates that the health monitor will not invoke the test. A value of '0' cannot be set.

This object indicates the default consecutive failure count threshold. When the specified failure count threshold is reached, the diagnostic test result is set to failure. A value of '0' indicates that the health monitor will not invoke this test.

This object specifies the consecutive failure count threshold for this test. When the specified failure count threshold is reached, the diagnostic test result is set to failure. A value of '0' indicates that there is no failure count threshold for this test. This object is used in combination with ceDiagHMTestThreshWindowSuite and ceDiagHMTestThreshWindowSize to specify a sliding history window for which the threshold is monitored. When the value of ceDiagHMTestThreshWindowSuite is 'default', the sliding history window is in number of test runs, with a window size the same as the value of this object. If ceDiagHMTestThreshWindowSuite and ceDiagHMTestThreshWindowSize are not supported, the failure count threshold will be the consecutive failure count threshold.

This object specifies a sliding history window parameter which is used in combination with ceDiagHMTestThreshold. When the specified failure count threshold is reached in this sliding history window, the diagnostic test result is set to failure. 'default' - The sliding history window is in number of test runs or executions, with a window size the same as ceDiagHMTestThreshold. 'milliseconds' - The sliding history window is in milli-seconds specified by ceDiagHMTestThreshWindowSize. 'seconds' - The sliding history window is in seconds specified by ceDiagHMTestThreshWindowSize. 'minutes' - The sliding history window is in minutes specified by ceDiagHMTestThreshWindowSize. 'hours' - The sliding history window is in hours specified by ceDiagHMTestThreshWindowSize. 'days' - The sliding history window is in days specified by ceDiagHMTestThreshWindowSize. 'runs' - The sliding history window is in number of test runs or executions specified by ceDiagHMTestThreshWindowSize. When the value of this object is 'default' the user cannot set any value for ceDiagHMTestThreshWindowSize. When the value of this object is not 'default', then the value of ceDiagHMTestThreshWindowSize cannot be zero (0). Enumeration: 'runs': 7, 'default': 1, 'days': 6, 'hours': 5, 'seconds': 3, 'minutes': 4, 'milliseconds': 2.

This object indicates the sliding history window size. When the value of ceDiagHMTestThreshWindowSuite is 'default', the user cannot set any value for this object. The value of zero (0) cannot be set.

This object specifies the maximum number of entries which the event log buffer can contain.

This object specifies the number of entries currently stored in the event log buffer.

Maximum number of query entries allowed in the ceDiagEventQueryTable.

A control table used to query the event log buffer. Each row instance in the table represents a query with its parameters. The resulting data for each instance of a query in this table is stored in the ceDiagEventResultTable. A row in this table can be created by setting the corresponding instance of ceDiagEventQueryStatus to 'createAndGo'. A row can be deleted by setting the corresponding instance of ceDiagEventQueryStatus to 'destroy'.

A conceptual row of the ceDiagEventQueryTable used to setup a event log buffer query to search for diagnostic events. The actual search is started by when the value of ceDiagEventQueryStatus is set to 'active'.

An arbitrary integer in the range of 1 to ceDiagEventMaxQueries to identify this control query.

This object specifies the physical entity for the event log buffer query. A value of zero indicates that the query will return events of all physical entities.

This object specifies the severity of the event log buffer query. A value of 'all' indicates that the search will return events of all severities. Enumeration: 'info': 1, 'all': 0, 'warning': 2, 'error': 3.

The manager entity that configured this entry and is therefore using the resources assigned to it. It is used to model an administratively assigned name of the owner of a resource. It is recommended that this object have one or more the following information: IP address, management station name, network manager's name, location, or phone number.

The result status of the query. Possible values are: -1 - Either the query has not been initiated or the agent is busy processing this query instance. Time to completion of the query processing depends on the complexity of the query and the number of matches that satisfy this query. 0..2147483647 - The search has ended and this is the number of rows in the ceDiagEventResultTable, resulting from this query.

The status object used to manage rows in this table. When set to 'active', the query to search for diagnostic events is initiated. Once a row becomes active, values within the row cannot be modified, except by deleting and re-creating the row.

A table containing event log information corresponding to all the completed queries set up in ceDiagEventQueryTable. The query result will not become available until the current search is completed.

A conceptual row in ceDiagEventResultTable, containing information about an event that matches the search criteria set in the corresponding row of ceDiagEventQueryTable.

A positive integer which uniquely identifies a result entry matching a particular query.

This object specifies the physical entity corresponding to this event.

This object specifies a textual description of physical entity corresponding to this event.

This object specifies the time at which this event occurred.

This object indicates the severity of this event. Enumeration: 'info': 1, 'warning': 2, 'error': 3.

The text message of this event.

The error message related to the notification.

This variable specifies whether the system produces the ceDiagBootUpFailedNotif. A 'false' value will prevent ceDiagBootUpFailedNotif notifications from being generated by this system.

This variable specifies whether the system produces the ceDiagHMThresholdReachedNotif. A 'false' value will prevent ceDiagHMThresholdReachedNotif notifications from being generated by this system.

This variable specifies whether the system produces the ceDiagHMTestRecoverNotif. A 'false' value will prevent ceDiagHMTestRecoverNotif notifications from being generated by this system.

This variable specifies whether the system produces the ceDiagScheduledTestFailedNotif. A 'false' value will prevent ceDiagScheduledTestFailedNotif notifications from being generated by this system.

The compliance statement for SNMP entities that implement the CISCO-ENTITY-DIAG-MIB. Implementation of this MIB module is strongly recommended for any platform implementing the online diagnostic feature.

The compliance statement for SNMP entities that implement the CISCO-ENTITY-DIAG-MIB. Implementation of this MIB module is strongly recommended for any platform implementing the online diagnostic feature. This statement is deprecated and superceded by ciscoEntityDiagMIBComplianceRev3.

The compliance statement for SNMP entities that implement the CISCO-ENTITY-DIAG-MIB. Implementation of this MIB module is strongly recommended for any platform implementing the online diagnostic feature. This statement is deprecated and superceded by ciscoEntityDiagMIBComplianceRev4.

The compliance statement for SNMP entities that implement the CISCO-ENTITY-DIAG-MIB. Implementation of this MIB module is strongly recommended for any platform implementing the online diagnostic feature.

A collection of managed objects that describe tests and errors supported by each physical entity.

A collection of managed objects that describe global configuration of the online diagnostic feature.

A collection of managed objects that describe the state of a physical entity with respect ot the online diagnostic feature.

A collection of managed objects that describe the diagnostic image which the physical entity is running.

A collection of managed objects that describe the diagnostic on demand diagnostic jobs on the system.

A collection of managed objects that describe the diagnostic on demand diagnostic jobs on the system.

A collection of managed objects that describe the performance of tests supported by each physical entity.

A collection of managed objects that describe tests and test configuration with relating to the health monitor.

A collection of managed objects that describe online diagnostic event history.

A collection of managed objects that describe the test suite information for a diagnostic scheduled job.

A collection of objects providing enabling/disabling of the boot up failed, health monitoring, and scheduled job notifications for online diagnostics.

A collection of objects providing error message used by various notifications.

A collection of notifications providing for boot up failed, health monitoring, and scheduled job within online diagnostics.

A collection of managed objects that describe the last testing method for a diagnostic test.

A collection of managed objects that describe the sliding history window parameters for a Health Monitor diagnostic test.