QBSYS-SYSTEM-MIB :: qbSysBootDiagsCode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsQBSYS-SYSTEM-MIBqbSysBootDiagsCode

qbSysBootDiagsCode

Module: QBSYS-SYSTEM-MIB

OID (symbolic): QBSYS-SYSTEM-MIB::qbSysBootDiagsCode

OID (numeric): 1.3.6.1.4.1.4323.2.2.1.1.4

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: An error code giving more details about a boot diagnostics failure indicated by qbSysOperStatus 'warning(1)' or 'down(2)'. The value 0 indicates no failure detected.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4323.2.2.1.1.4
snmpwalk -v2c -c public <target> QBSYS-SYSTEM-MIB::qbSysBootDiagsCode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4323.2.2.1.1.4.1
snmpget -v2c -c public <target> QBSYS-SYSTEM-MIB::qbSysBootDiagsCode.1

Start monitoring Quantum Bridge Technologies chassis-based network device (system inventory/software version) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the QBSYS-SYSTEM-MIB::qbSysBootDiagsCode OID value, configure state conditions and alerts, and monitor any Quantum Bridge Technologies chassis-based network device (system inventory/software version) from a single console.

How to Use in IPNetwork Monitor

Select a Quantum Bridge Technologies chassis-based network device as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type qbSysBootDiagsCode into the Find box to locate it in the OID tree, then select it and click OK. It reports the boot-diagnostics error code from the device's last startup — 0 means no failure was detected. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 0, since that indicates the device detected a boot diagnostics failure. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.4323quantumBridgeQUANTUMBRIDGE-REG
1.3.6.1.4.1.4323.2qbMibsQUANTUMBRIDGE-REG
Numeric OIDNameModule
1.3.6.1.4.1.4323.2.2qbSysMIBQBSYS-SYSTEM-MIB
1.3.6.1.4.1.4323.2.2.1qbSysObjectsQBSYS-SYSTEM-MIB
1.3.6.1.4.1.4323.2.2.1.1qbSysGeneralGroupQBSYS-SYSTEM-MIB
1.3.6.1.4.1.4323.2.2.1.1.4qbSysBootDiagsCodeQBSYS-SYSTEM-MIB