LaserJet4V-MIB :: not_ready_controller

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsLaserJet4V-MIBnot_ready_controller

not_ready_controller

Module: LaserJet4V-MIB

OID (symbolic): LaserJet4V-MIB::not_ready_controller

OID (numeric): 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.3

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: Indicates if the hardware controller sub-system in the device is not ready. If there are no items in the collection (i.e. no bits are set), then the hardware controller sub-system is ready. If there is an item present, then the item indicates what is causing the hardware controller sub-system to be not ready. If the cControllerFailure item is in the collection, then a hardware error was detected on the main controller PC board, sometimes called the formatter or the logic broad. Example controller hardware errors include DRAM controller failure, clock failure, memory parity error, and ROM CRC error. The cFirmwareFailure item is in the collection if a firmware/software error was detected. Device specific detailed error information can be retrieved from the error log objects, if the device supports those objects. The POS will list which device failures cause each item to be included in the collection. Additional information: A controller failure occurrence will set the cControllerFailure bit (bit 1). The controller failures are: 62.X Service, 63 Service, 65 Service, 67 Service, 68 Service, and 68 Error. A SIMM failure occurrence will set the cSIMMFailure bit (bit 2). The SIMM failures are 61.X Service, 53-XY-ZZ Error, and 72 Service. A DISK failure occurrence will set the cATFailure bit (bit 3). The DISK failure is FS DISK FAILURE.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.3
snmpwalk -v2c -c public <target> LaserJet4V-MIB::not_ready_controller

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.3.1
snmpget -v2c -c public <target> LaserJet4V-MIB::not_ready_controller.1

Start monitoring HP LaserJet 4V printer with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LaserJet4V-MIB::not_ready_controller OID value, configure state conditions and alerts, and monitor any HP LaserJet 4V printer from a single console.

OID Breakdown

Upper-level ancestors (15 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.11hpCLJ8500-MIB
1.3.6.1.4.1.11.2nmCLJ8500-MIB
1.3.6.1.4.1.11.2.3hpsystemCLJ8500-MIB
1.3.6.1.4.1.11.2.3.9net_peripheralCLJ8500-MIB
1.3.6.1.4.1.11.2.3.9.4netdmCLJ8500-MIB
1.3.6.1.4.1.11.2.3.9.4.2dmCLJ8500-MIB
1.3.6.1.4.1.11.2.3.9.4.2.1deviceCLJ8500-MIB
1.3.6.1.4.1.11.2.3.9.4.2.1.1systemCLJ8500-MIB
1.3.6.1.4.1.11.2.3.9.4.2.1.1.2status_systemCLJ8500-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.3not_ready_controllerLaserJet4V-MIB