CISCO-BOOT-HWDIAGS-MIB
AI MIB Summary
The CISCO-BOOT-HWDIAGS-MIB enables configuration and retrieval of pre-IOS boot-time hardware diagnostic results for Cisco devices, specifically monitoring EDAC, EEPROM, and FPGA test statuses across defined hardware banks. This module allows administrators to query pass/fail outcomes for critical components like FPGAs and memory controllers before the IOS subsystem initializes, facilitating early detection of hardware faults during the boot sequence.
This MIB is used to configure those devices that support boot-time hardware diagnostics. It provides the reports about the respective diagnostic tests executed by the devices as well.
Boot-time diagnostics are run after the ROMMON has transferred control to the start code of IOS and before any IOS subsystem has started.
Such diagnostics may or may not include those that are destructive to the operation of IOS or communications links that are serviced by IOS and, as such, must be run before IOS has completed booting and before any subsystem has started.
During boot-up from either power-on or a reload, and before IOS starts, a loop of all such diagnostics is executed according to the following flow:
bank = current_bank for index = 1 to number of diagnostics { if diag[index] is configured AND armed for bank { call diagnostic_function[index]; store results in memory = structure.bank.index; }
After all the IOS subsystems have started, one can use either the CLI or this MIB to query the status of the diagnostic tests for each bank.
The diagnostic tests are tabulated on the CLI as follows.
Information for Hardware Diagnostics Bank 0 (Current bank = 0)
Last Boot Next Boot
-
Diagnostic Ran? Pass/Failed? Configured? Armed?
EDAC test YES PASSED YES NO EEPROM test YES PASSED YES NO FPGA(s) test YES FAILED YES NO
FPGA Diags: FPGA1:F, FPGA2-REG:P, FPGA2-SRAM:P, FPGA3:F
In the table above, there are 3 diagnostic_function
categories:
EDAC, EEPROM, and FPGA(s). The FPGA category has 4 subtests one associated with FPGA1, two with FPGA2, and one with FPGA3.
The MIB shall be used to configure the diagnostic tests to be run on each bank and read the results of the same. The selection of a particular bank to run the tests is hardware- dependent.
GLOSSARY CLI - Command Line Interface diags - abbreviation for diagnostics EDAC - Error Detection and Correction EEPROM - Electrically Eraseable Programmable Read-Only Memory FPGA - Field Programmable Gate Array IOS - Internet Operating System MIB - Management Information Base NVRAM - Non-volatile Random Access Memory SRAM - Static Random Access Memory
Main OID:
ciscoBootHwDiagsMIB.1.3.6.1.4.1.9.9.696
20
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
20 total| Object Name |
|---|
ciscoBootHwDiagsMIBThis MIB is used to configure those devices that support
boot-time hardware diagnostics. It provides the reports
about the respective diagnostic tests executed by the
devices as well.
Boot-time diagnostics are run after the ROMMON has
transferred control to the start code of IOS and before
any IOS subsystem has started.
Such diagnostics may or may not include those that are
destructive to the operation of IOS or communications
links that are serviced by IOS and, as such, must be run
before IOS has completed booting and before any subsystem
has started.
During boot-up from either power-on or a reload, and
before IOS starts, a loop of all such diagnostics is executed
according to the following flow:
bank = current_bank
for index = 1 to number of diagnostics {
if diag[index] is configured AND armed for bank {
call diagnostic_function[index];
store results in memory = structure.bank.index;
}
After all the IOS subsystems have started, one can
use either the CLI or this MIB to query the status of the
diagnostic tests for each bank.
The diagnostic tests are tabulated on the CLI as
follows.
Information for Hardware Diagnostics Bank 0
(Current bank = 0)
Last Boot Next Boot
-
Diagnostic Ran? Pass/Failed? Configured? Armed?
EDAC test YES PASSED YES NO
EEPROM test YES PASSED YES NO
FPGA(s) test YES FAILED YES NO
FPGA Diags: FPGA1:F, FPGA2-REG:P, FPGA2-SRAM:P, FPGA3:F
In the table above, there are 3 diagnostic_function
categories:
EDAC, EEPROM, and FPGA(s). The FPGA category has 4
subtests one associated with FPGA1, two with FPGA2, and one
with FPGA3.
The MIB shall be used to configure the diagnostic tests
to be run on each bank and read the results of the same. The
selection of a particular bank to run the tests is hardware-
dependent.
GLOSSARY
CLI - Command Line Interface
diags - abbreviation for diagnostics
EDAC - Error Detection and Correction
EEPROM - Electrically Eraseable Programmable Read-Only Memory
FPGA - Field Programmable Gate Array
IOS - Internet Operating System
MIB - Management Information Base
NVRAM - Non-volatile Random Access Memory
SRAM - Static Random Access Memory MODULE-IDENTITY .1.3.6.1.4.1.9.9.696 |
ciscoBootHwDiagsMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.696.0 |
ciscoBootHwDiagsMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.696.1 |
ciscoBootHwDiagsMIBCurrentBankThis object identifies the current bank the device has booted
with and executed the diagnostic tests.ro Unsigned32 .1.3.6.1.4.1.9.9.696.1.1 |
ciscoBootHwDiagsMIBTestTableThis table gives the list of possible diagnostic test
'categories' that may be configured, armed, and run for
each bank. The categories are the same for all banks.
In the CLI example given above, the categories are:
EDAC test, EEPROM test, and FGPA(s) test. SEQUENCE OF CiscoBootHwDiagsMIBTestEntry .1.3.6.1.4.1.9.9.696.1.2 |
ciscoBootHwDiagsMIBTestEntryEach entry represents a row in ciscoBootHwDiagsMIBTestTable
and corresponds to the information about the various
categories of diagnostic tests. CiscoBootHwDiagsMIBTestEntry .1.3.6.1.4.1.9.9.696.1.2.1 |
ciscoBootHwDiagsMIBTestIndexThis object uniquely identifies the information about a
particular category of test. Unsigned32 .1.3.6.1.4.1.9.9.696.1.2.1.1 |
ciscoBootHwDiagsMIBTestNameThis object represents the name of the diagnostic test.ro DisplayString .1.3.6.1.4.1.9.9.696.1.2.1.2 |
ciscoBootHwDiagsMIBTableThe table lists the configuration and results of the tests run
on the banks. The results correspond to the execution of the
respective tests run at the most recent boot of the device. SEQUENCE OF CiscoBootHwDiagsMIBEntry .1.3.6.1.4.1.9.9.696.1.3 |
ciscoBootHwDiagsMIBEntryEach entry represents a row in ciscoBootHwDiagsMIBTable and
corresponds to the information about the diagnostic tests for a
particular
bank. CiscoBootHwDiagsMIBEntry .1.3.6.1.4.1.9.9.696.1.3.1 |
ciscoBootHwDiagsMIBBankIndexThis object, together with ciscoBootHwDiagsMIBTestIndex,
uniquely identifies the information about a particular
diagnostic test. Unsigned32 .1.3.6.1.4.1.9.9.696.1.3.1.1 |
ciscoBootHwDiagsMIBLastBootExecutedThis object represents the execution status of the test. A
value of 'true' indicates that the test has been executed on
the most recent boot of the device. A value of 'false'
indicates that the test has not been executed.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.696.1.3.1.2 |
ciscoBootHwDiagsMIBLastBootPassedThis object represents the result of the test on the most
recent boot of the device. A value of 'true' indicates that the
test passed. A value of 'false' indicates that the test
failed.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.696.1.3.1.3 |
ciscoBootHwDiagsMIBNextBootConfiguredThis object indicates the action to be taken on this bank at
the next boot. A value of 'true' indicates that the test
identified by ciscoBootHwDiagsMIBTestName will be executed at
the next boot, provided the device chooses this bank for
diagnosis.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.696.1.3.1.4 |
ciscoBootHwDiagsMIBNextBootArmedA value of 'true' indicates that, for a particular numbered
bank, all the configured tests for that same numbered bank are
run.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.696.1.3.1.5 |
ciscoBootHwDiagsMIBConfigCodeThis object provides additional optional detailed configuration
options (sub-tests configurations) for a diagnostics test
category. The decoding of this unsigned 32-bit integer is
platform-specific and allows for many platform-specific
configurations. For the CLI example above, a
ciscoBootHwDiagsMIBConfigCode for the FPGA(s) test category
will cause all FPGA tests to be disabled, whereas,
a ciscoBootHwDiagsMIBConfigCode of 1 will enable FPGA1 test.
A ciscoBootHwDiagsMIBConfigCode of 3 will enable FPGA1 AND
FPGA2-subtest1, and so forth (since there is only one test
for FPGA1, but two tests for FPGA2). Hence the encoding is
platform dependent and flexible.rw Unsigned32 .1.3.6.1.4.1.9.9.696.1.3.1.6 |
ciscoBootHwDiagsMIBResultCodeThis object represents a return code that may be mapped to
detailed testresults in an analogous way to how the
ciscoBootHwDiagsMIBConfigCode is mapped to configurations.
That is, for the CLI example above, a
ciscoBootHwDiagsMIBResultCode of F (hex) indicates that all
FPGA tests passed. A ciscoBootHwDiagsMIBResultCode of
1 (hex), indicates that ONLY FPGA1 test passed. A
ciscoBootHwDiagsMIBResultCode of 3 (hex) indicates that only
FPGA1 AND FPGA2-subtest1 passed, and so forth (since there is
only one test for FPGA1, but two tests for FPGA2). Hence the
encoding is platform dependent and flexible.ro Unsigned32 .1.3.6.1.4.1.9.9.696.1.3.1.7 |
ciscoBootHwDiagsMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.696.2 |
ciscoBootHwDiagsMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.696.2.1 |
ciscoBootHwDiagsMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.696.2.2 |