What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Where can I find a lot of different libraries *.oidlib?

Votes:

0

Where can I find a lot of different libraries *.oidlib?

Regards

printers prtg snmp

Created on Jul 12, 2011 10:55:39 AM



Best Answer

Accepted Answer

Votes:

0

at the moment PRTG MIB importer only imports OIDs that return integers, no strings.

Created on Jul 19, 2011 7:14:23 AM by  Aurelio Lombardi [Paessler Support]



15 Replies

Votes:

0

you can create your own libraries using our free MIB importer.

Created on Jul 12, 2011 11:17:26 AM by  Aurelio Lombardi [Paessler Support]



Votes:

0

Thank you for your response, Aurelio! I’ve read about this possibility, but did not understand how to use. I've a printer HP 2727nf and I need to create a sensor for monitoring the quantity toner in print cartridge by PRTG. I can't find a suitable for this in C:\Program Files\Paessler MIB Importer V2\stdmib

Maybe it's impossible?

Created on Jul 12, 2011 11:41:07 AM



Votes:

0

Our MIB Importer does not include the necessary MIB files. You would need to request the same from the hardware vendor (in this case HP).

Created on Jul 12, 2011 1:03:33 PM by  Patrick Hutter [Paessler Support] (7,225) 3 3



Votes:

0

Thank you so much!

Created on Jul 13, 2011 4:54:04 AM



Votes:

0

Hello! The vendor gave me a HP-LASERJET-COMMON-MIB I imported the MIB in OIDLIB library (PRTG), but I do not see the object hrprinterdetectederrorstate. Maybe I'm using the noncorrect OID? Please let me know OID that use the import

......

hrprinterdetectederrorstate OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS mandatory DESCRIPTION "This object represents any error conditions detected by the printer. The error conditions are encoded as bits in an octet string, with the following definitions: Condition Bit # hrDeviceStatus lowPaper 0 warning(3) noPaper 1 down(5) lowToner 2 warning(3) noToner 3 down(5) doorOpen 4 down(5) jammed 5 down(5) offline 6 down(5) serviceRequested 7 warning(3)

.....

Regards!

Created on Jul 13, 2011 9:26:17 AM



Votes:

0

hallo,

please open a ticket by sending a mail to [email protected] and include the MIB so that we can take a look at it.

Created on Jul 15, 2011 10:15:46 AM by  Aurelio Lombardi [Paessler Support]



Votes:

0

-- THIS MIB CREATED TO REDUCE DUPLICATION BETWEEN HP LASERJET MIBS

HP-LASERJET-COMMON-MIB DEFINITIONS ::= BEGIN

hp OBJECT IDENTIFIER ::= { enterprises 11 } nm OBJECT IDENTIFIER ::= { hp 2 } hpsystem OBJECT IDENTIFIER ::= { nm 3 } net-peripheral OBJECT IDENTIFIER ::= { hpsystem 9 } netdm OBJECT IDENTIFIER ::= { net-peripheral 4 } dm OBJECT IDENTIFIER ::= { netdm 2}

DisplayString ::= OCTET STRING

device OBJECT IDENTIFIER ::= { dm 1 } channel OBJECT IDENTIFIER ::= { device 6 } channelTable OBJECT IDENTIFIER ::= { channel 3 } channelEntry OBJECT IDENTIFIER ::= { channelTable 1 } system OBJECT IDENTIFIER ::= { device 1 } settings-system OBJECT IDENTIFIER ::= { system 1 } status-system OBJECT IDENTIFIER ::= { system 2 } display OBJECT IDENTIFIER ::= { status-system 20 } display-status OBJECT IDENTIFIER ::= { display 1 } status-message OBJECT IDENTIFIER ::= { display 2 } status-message1 OBJECT IDENTIFIER ::= { status-message 1 } background-message OBJECT IDENTIFIER ::= { status-system 37 } background-message1 OBJECT IDENTIFIER ::= { background-message 1 } background-message2 OBJECT IDENTIFIER ::= { background-message 2 } id OBJECT IDENTIFIER ::= { system 3 } interface OBJECT IDENTIFIER ::= { system 4 } at OBJECT IDENTIFIER ::= { interface 2 } at1 OBJECT IDENTIFIER ::= { at 1 } simm OBJECT IDENTIFIER ::= { interface 1 } simm1 OBJECT IDENTIFIER ::= { simm 1 } simm2 OBJECT IDENTIFIER ::= { simm 2 } simm3 OBJECT IDENTIFIER ::= { simm 3 } simm4 OBJECT IDENTIFIER ::= { simm 4 } simm5 OBJECT IDENTIFIER ::= { simm 5 } simm6 OBJECT IDENTIFIER ::= { simm 6 } simm7 OBJECT IDENTIFIER ::= { simm 7 } simm8 OBJECT IDENTIFIER ::= { simm 8 } test OBJECT IDENTIFIER ::= { system 5 } job OBJECT IDENTIFIER ::= { system 6 } settings-job OBJECT IDENTIFIER ::= { job 1 } errorlog OBJECT IDENTIFIER ::= { system 11 } error1 OBJECT IDENTIFIER ::= { errorlog 1 } error2 OBJECT IDENTIFIER ::= { errorlog 2 } error3 OBJECT IDENTIFIER ::= { errorlog 3 } error4 OBJECT IDENTIFIER ::= { errorlog 4 } error5 OBJECT IDENTIFIER ::= { errorlog 5 } error6 OBJECT IDENTIFIER ::= { errorlog 6 } error7 OBJECT IDENTIFIER ::= { errorlog 7 } error8 OBJECT IDENTIFIER ::= { errorlog 8 } error9 OBJECT IDENTIFIER ::= { errorlog 9 } error10 OBJECT IDENTIFIER ::= { errorlog 10 } error11 OBJECT IDENTIFIER ::= { errorlog 11 } error12 OBJECT IDENTIFIER ::= { errorlog 12 } error13 OBJECT IDENTIFIER ::= { errorlog 13 } error14 OBJECT IDENTIFIER ::= { errorlog 14 } error15 OBJECT IDENTIFIER ::= { errorlog 15 } error16 OBJECT IDENTIFIER ::= { errorlog 16 } error17 OBJECT IDENTIFIER ::= { errorlog 17 } error18 OBJECT IDENTIFIER ::= { errorlog 18 } error19 OBJECT IDENTIFIER ::= { errorlog 19 } error20 OBJECT IDENTIFIER ::= { errorlog 20 } error21 OBJECT IDENTIFIER ::= { errorlog 21 } error22 OBJECT IDENTIFIER ::= { errorlog 22 } error23 OBJECT IDENTIFIER ::= { errorlog 23 } error24 OBJECT IDENTIFIER ::= { errorlog 24 } error25 OBJECT IDENTIFIER ::= { errorlog 25 } error26 OBJECT IDENTIFIER ::= { errorlog 26 } error27 OBJECT IDENTIFIER ::= { errorlog 27 } error28 OBJECT IDENTIFIER ::= { errorlog 28 } error29 OBJECT IDENTIFIER ::= { errorlog 29 } error30 OBJECT IDENTIFIER ::= { errorlog 30 } error31 OBJECT IDENTIFIER ::= { errorlog 31 } error32 OBJECT IDENTIFIER ::= { errorlog 32 } error33 OBJECT IDENTIFIER ::= { errorlog 33 } error34 OBJECT IDENTIFIER ::= { errorlog 34 } error35 OBJECT IDENTIFIER ::= { errorlog 35 } error36 OBJECT IDENTIFIER ::= { errorlog 36 } error37 OBJECT IDENTIFIER ::= { errorlog 37 } error38 OBJECT IDENTIFIER ::= { errorlog 38 } error39 OBJECT IDENTIFIER ::= { errorlog 39 } error40 OBJECT IDENTIFIER ::= { errorlog 40 } error41 OBJECT IDENTIFIER ::= { errorlog 41 } error42 OBJECT IDENTIFIER ::= { errorlog 42 } error43 OBJECT IDENTIFIER ::= { errorlog 43 } error44 OBJECT IDENTIFIER ::= { errorlog 44 } error45 OBJECT IDENTIFIER ::= { errorlog 45 } error46 OBJECT IDENTIFIER ::= { errorlog 46 } error47 OBJECT IDENTIFIER ::= { errorlog 47 } error48 OBJECT IDENTIFIER ::= { errorlog 48 } error49 OBJECT IDENTIFIER ::= { errorlog 49 } error50 OBJECT IDENTIFIER ::= { errorlog 50 } source-subsystem OBJECT IDENTIFIER ::= { device 2 } io OBJECT IDENTIFIER ::= { source-subsystem 1 } settings-io OBJECT IDENTIFIER ::= { io 1 } status-io OBJECT IDENTIFIER ::= { io 2 } ports OBJECT IDENTIFIER ::= { io 3 } port1 OBJECT IDENTIFIER ::= { ports 1 } parallel OBJECT IDENTIFIER ::= { port1 1 } processing-subsystem OBJECT IDENTIFIER ::= { device 3 } pdl OBJECT IDENTIFIER ::= { processing-subsystem 3 } pdl-esc-p OBJECT IDENTIFIER ::= { pdl 5 } settings-pdl OBJECT IDENTIFIER ::= { pdl 1 } pdl-pcl OBJECT IDENTIFIER ::= { pdl 3 } pdl-postscript OBJECT IDENTIFIER ::= { pdl 4 } pjl OBJECT IDENTIFIER ::= { processing-subsystem 5 } destination-subsystem OBJECT IDENTIFIER ::= { device 4 } print-engine OBJECT IDENTIFIER ::= { destination-subsystem 1 } settings-prt-eng OBJECT IDENTIFIER ::= { print-engine 1 } status-prt-eng OBJECT IDENTIFIER ::= { print-engine 2 } intray OBJECT IDENTIFIER ::= { print-engine 3 } settings-intray OBJECT IDENTIFIER ::= { intray 1 } status-intray OBJECT IDENTIFIER ::= { intray 2 } marking-agent OBJECT IDENTIFIER ::= { print-engine 5 } settings-marking-agent OBJECT IDENTIFIER ::= { marking-agent 1 } imaging OBJECT IDENTIFIER ::= { print-engine 6 } hrm OBJECT IDENTIFIER ::= { dm 3 } hrStorage OBJECT IDENTIFIER ::= { hrm 2 } hrStorageTable OBJECT IDENTIFIER ::= { hrStorage 3 } hrStorageEntry OBJECT IDENTIFIER ::= { hrStorageTable 1 } hrDevice OBJECT IDENTIFIER ::= { hrm 3 } hrDeviceTable OBJECT IDENTIFIER ::= { hrDevice 2 } hrDeviceEntry OBJECT IDENTIFIER ::= { hrDeviceTable 1 } hrPrinterTable OBJECT IDENTIFIER ::= { hrDevice 5 } hrPrinterEntry OBJECT IDENTIFIER ::= { hrPrinterTable 1 } printmib OBJECT IDENTIFIER ::= { dm 2 } prtGeneral OBJECT IDENTIFIER ::= { printmib 5 } prtGeneralTable OBJECT IDENTIFIER ::= { prtGeneral 1 } prtGeneralEntry OBJECT IDENTIFIER ::= { prtGeneralTable 1 } prtLocalization OBJECT IDENTIFIER ::= { printmib 7 } prtLocalizationTable OBJECT IDENTIFIER ::= { prtLocalization 1 } prtLocalizationEntry OBJECT IDENTIFIER ::= { prtLocalizationTable 1 } prtStorageRefTable OBJECT IDENTIFIER ::= { prtGeneral 2 } prtStorageRefEntry OBJECT IDENTIFIER ::= { prtStorageRefTable 1 } prtDeviceRefTable OBJECT IDENTIFIER ::= { prtGeneral 3 } prtDeviceRefEntry OBJECT IDENTIFIER ::= { prtDeviceRefTable 1 } prtMarker OBJECT IDENTIFIER ::= { printmib 10 } prtMarkerTable OBJECT IDENTIFIER ::= { prtMarker 2 } prtMarkerEntry OBJECT IDENTIFIER ::= { prtMarkerTable 1 } prtMarkerColorant OBJECT IDENTIFIER ::= { printmib 12 } prtMarkerColorantTable OBJECT IDENTIFIER ::= { prtMarkerColorant 1 } prtMarkerColorantEntry OBJECT IDENTIFIER ::= { prtMarkerColorantTable 1 } prtConsoleDisplayBuffer OBJECT IDENTIFIER ::= { printmib 16 } prtConsoleDisplayBufferTable OBJECT IDENTIFIER ::= { prtConsoleDisplayBuffer 5 } prtConsoleDisplayBufferEntry OBJECT IDENTIFIER ::= { prtConsoleDisplayBufferTable 1 } prtConsoleLights OBJECT IDENTIFIER ::= { printmib 17 } prtConsoleLightTable OBJECT IDENTIFIER ::= { prtConsoleLights 6 } prtConsoleLightEntry OBJECT IDENTIFIER ::= { prtConsoleLightTable 1 } prtAlert OBJECT IDENTIFIER ::= { printmib 18 } prtAlertTable OBJECT IDENTIFIER ::= { prtAlert 1 } prtAlertEntry OBJECT IDENTIFIER ::= { prtAlertTable 1 } phd OBJECT IDENTIFIER ::= { interface 5 } phd2 OBJECT IDENTIFIER ::= { phd 2 } phd3 OBJECT IDENTIFIER ::= { phd 3 } phd4 OBJECT IDENTIFIER ::= { phd 4 } phd5 OBJECT IDENTIFIER ::= { phd 5 } phd6 OBJECT IDENTIFIER ::= { phd 6 } intrays OBJECT IDENTIFIER ::= { intray 3 } intray1 OBJECT IDENTIFIER ::= { intrays 1 } outbin OBJECT IDENTIFIER ::= { print-engine 4 } settings-outbin OBJECT IDENTIFIER ::= { outbin 1 } outbins OBJECT IDENTIFIER ::= { outbin 3 } outbin1 OBJECT IDENTIFIER ::= { outbins 1 } outbin2 OBJECT IDENTIFIER ::= { outbins 2 } outbin3 OBJECT IDENTIFIER ::= { outbins 3 } outbin4 OBJECT IDENTIFIER ::= { outbins 4 } outbin5 OBJECT IDENTIFIER ::= { outbins 5 } outbin6 OBJECT IDENTIFIER ::= { outbins 6 } outbin7 OBJECT IDENTIFIER ::= { outbins 7 } outbin8 OBJECT IDENTIFIER ::= { outbins 8 } outbin9 OBJECT IDENTIFIER ::= { outbins 9 } outbin10 OBJECT IDENTIFIER ::= { outbins 10 } outbin11 OBJECT IDENTIFIER ::= { outbins 11 } ph OBJECT IDENTIFIER ::= { print-engine 7 } ph-devices OBJECT IDENTIFIER ::= { ph 3 } ph2 OBJECT IDENTIFIER ::= { ph-devices 2 } ph3 OBJECT IDENTIFIER ::= { ph-devices 3 } ph4 OBJECT IDENTIFIER ::= { ph-devices 4 } ph5 OBJECT IDENTIFIER ::= { ph-devices 5 } ph6 OBJECT IDENTIFIER ::= { ph-devices 6 } print-media OBJECT IDENTIFIER ::= { print-engine 8 } settings-print-media OBJECT IDENTIFIER ::= { print-media 1 } media-info OBJECT IDENTIFIER ::= { print-media 3 } media1 OBJECT IDENTIFIER ::= { media-info 1 } media2 OBJECT IDENTIFIER ::= { media-info 2 } media3 OBJECT IDENTIFIER ::= { media-info 3 } media4 OBJECT IDENTIFIER ::= { media-info 4 } media5 OBJECT IDENTIFIER ::= { media-info 5 } media6 OBJECT IDENTIFIER ::= { media-info 6 } media7 OBJECT IDENTIFIER ::= { media-info 7 } media8 OBJECT IDENTIFIER ::= { media-info 8 } media9 OBJECT IDENTIFIER ::= { media-info 9 } media10 OBJECT IDENTIFIER ::= { media-info 10 } media11 OBJECT IDENTIFIER ::= { media-info 11 } media12 OBJECT IDENTIFIER ::= { media-info 12 } media13 OBJECT IDENTIFIER ::= { media-info 13 } media14 OBJECT IDENTIFIER ::= { media-info 14 } media15 OBJECT IDENTIFIER ::= { media-info 15 } media16 OBJECT IDENTIFIER ::= { media-info 16 } media17 OBJECT IDENTIFIER ::= { media-info 17 } prtCover OBJECT IDENTIFIER ::= { printmib 6 } prtCoverTable OBJECT IDENTIFIER ::= { prtCover 1 } prtCoverEntry OBJECT IDENTIFIER ::= { prtCoverTable 1 } prtMarkerSupplies OBJECT IDENTIFIER ::= { printmib 11 } prtMarkerSuppliesTable OBJECT IDENTIFIER ::= { prtMarkerSupplies 1 } prtMarkerSuppliesEntry OBJECT IDENTIFIER ::= { prtMarkerSuppliesTable 1 } prtMediaPath OBJECT IDENTIFIER ::= { printmib 13 } prtMediaPathTable OBJECT IDENTIFIER ::= { prtMediaPath 4 } prtMediaPathEntry OBJECT IDENTIFIER ::= { prtMediaPathTable 1 } file-system OBJECT IDENTIFIER ::= { system 10 } settings-file-system OBJECT IDENTIFIER ::= { file-system 1 } status-file-system OBJECT IDENTIFIER ::= { file-system 2 } file-systems OBJECT IDENTIFIER ::= { file-system 3 } file-system1 OBJECT IDENTIFIER ::= { file-systems 1 } file-system2 OBJECT IDENTIFIER ::= { file-systems 2 } file-system3 OBJECT IDENTIFIER ::= { file-systems 3 } file-system4 OBJECT IDENTIFIER ::= { file-systems 4 } resource-manager OBJECT IDENTIFIER ::= { system 12 } mass-storage-resources OBJECT IDENTIFIER ::= { resource-manager 3 } hrDiskStorageTable OBJECT IDENTIFIER ::= { hrDevice 6 } hrDiskStorageEntry OBJECT IDENTIFIER ::= { hrDiskStorageTable 1 } hrPartitionTable OBJECT IDENTIFIER ::= { hrDevice 7 } hrPartitionEntry OBJECT IDENTIFIER ::= { hrPartitionTable 1 } hrFSTable OBJECT IDENTIFIER ::= { hrDevice 8 } hrFSEntry OBJECT IDENTIFIER ::= { hrFSTable 1 } mio OBJECT IDENTIFIER ::= { interface 3 } mio1 OBJECT IDENTIFIER ::= { mio 1 } mio2 OBJECT IDENTIFIER ::= { mio 2 } mio3 OBJECT IDENTIFIER ::= { mio 3 } active-print-jobs OBJECT IDENTIFIER ::= { job 2 } job-being-parsed OBJECT IDENTIFIER ::= { active-print-jobs 1 } job-info OBJECT IDENTIFIER ::= { job 5 } job-info-attribute OBJECT IDENTIFIER ::= { job-info 23 } status-pdl OBJECT IDENTIFIER ::= { pdl 2 } jetsend-proc-sub OBJECT IDENTIFIER ::= { processing-subsystem 8 } settings-jetsend OBJECT IDENTIFIER ::= { jetsend-proc-sub 1 } jetsend-contact OBJECT IDENTIFIER ::= { jetsend-proc-sub 3 } settings-jetsend-contact OBJECT IDENTIFIER ::= { jetsend-contact 1 } held-job OBJECT IDENTIFIER ::= { job 7 } held-job-info OBJECT IDENTIFIER ::= { held-job 1 } held-job-control OBJECT IDENTIFIER ::= { held-job 2 } accounting OBJECT IDENTIFIER ::= { system 16 } printer-accounting OBJECT IDENTIFIER ::= { accounting 1 } scanner-accounting OBJECT IDENTIFIER ::= { accounting 2 } scanned-media-usage OBJECT IDENTIFIER ::= { scanner-accounting 1 } scanner OBJECT IDENTIFIER ::= { source-subsystem 2 } settings-scanner OBJECT IDENTIFIER ::= { scanner 1 } remote-procedure-call OBJECT IDENTIFIER ::= { system 13 } settings-rpc OBJECT IDENTIFIER ::= { remote-procedure-call 1 } status-rpc OBJECT IDENTIFIER ::= { remote-procedure-call 2 } rpc-services OBJECT IDENTIFIER ::= { remote-procedure-call 3 } mount OBJECT IDENTIFIER ::= { rpc-services 1 } settings-mount OBJECT IDENTIFIER ::= { mount 1 } nfs-server OBJECT IDENTIFIER ::= { rpc-services 2 } settings-nfs-server OBJECT IDENTIFIER ::= { nfs-server 1 } status-nfs-server OBJECT IDENTIFIER ::= { nfs-server 2 } rpc-bind OBJECT IDENTIFIER ::= { rpc-services 3 } settings-rpc-bind OBJECT IDENTIFIER ::= { rpc-bind 1 } status-rpc-bind OBJECT IDENTIFIER ::= { rpc-bind 2 } xport-interface OBJECT IDENTIFIER ::= { system 14 } status-xip OBJECT IDENTIFIER ::= { xport-interface 2 } prtInterpreter OBJECT IDENTIFIER ::= { printmib 15 } prtInterpreterTable OBJECT IDENTIFIER ::= { prtInterpreter 1 } prtInterpreterEntry OBJECT IDENTIFIER ::= { prtInterpreterTable 1 } simm1-bank OBJECT IDENTIFIER ::= { simm1 6 } simm1-bank1 OBJECT IDENTIFIER ::= { simm1-bank 1 } simm1-bank2 OBJECT IDENTIFIER ::= { simm1-bank 2 } simm2-bank OBJECT IDENTIFIER ::= { simm2 6 } simm2-bank1 OBJECT IDENTIFIER ::= { simm2-bank 1 } simm2-bank2 OBJECT IDENTIFIER ::= { simm2-bank 2 } simm3-bank OBJECT IDENTIFIER ::= { simm3 6 } simm3-bank1 OBJECT IDENTIFIER ::= { simm3-bank 1 } simm3-bank2 OBJECT IDENTIFIER ::= { simm3-bank 2 } mass-storage-block-driver OBJECT IDENTIFIER ::= { system 15 } settings-mass-storage-bd OBJECT IDENTIFIER ::= { mass-storage-block-driver 1 } status-mass-storage-bd OBJECT IDENTIFIER ::= { mass-storage-block-driver 2 } mass-storage-block-drivers OBJECT IDENTIFIER ::= { mass-storage-block-driver 3 } mass-storage-bd2 OBJECT IDENTIFIER ::= { mass-storage-block-drivers 2 } settings-msbd2 OBJECT IDENTIFIER ::= { mass-storage-bd2 1 } spooler OBJECT IDENTIFIER ::= { source-subsystem 4 } settings-spooler OBJECT IDENTIFIER ::= { spooler 1 } media-modes OBJECT IDENTIFIER ::= { print-media 4 } media-mode-details OBJECT IDENTIFIER ::= { print-media 6 } media-mode1 OBJECT IDENTIFIER ::= { media-mode-details 1 } media-mode2 OBJECT IDENTIFIER ::= { media-mode-details 2 } media-mode3 OBJECT IDENTIFIER ::= { media-mode-details 3 } media-mode4 OBJECT IDENTIFIER ::= { media-mode-details 4 } media-mode5 OBJECT IDENTIFIER ::= { media-mode-details 5 } phd1 OBJECT IDENTIFIER ::= { phd 1 } intray2 OBJECT IDENTIFIER ::= { intrays 2 } intray3 OBJECT IDENTIFIER ::= { intrays 3 } intray4 OBJECT IDENTIFIER ::= { intrays 4 } intray5 OBJECT IDENTIFIER ::= { intrays 5 } intray6 OBJECT IDENTIFIER ::= { intrays 6 } intray7 OBJECT IDENTIFIER ::= { intrays 7 } outbin3 OBJECT IDENTIFIER ::= { outbins 3 } media-size OBJECT IDENTIFIER ::= { print-media 5 } prtInput OBJECT IDENTIFIER ::= { printmib 8 } prtInputTable OBJECT IDENTIFIER ::= { prtInput 2 } prtInputEntry OBJECT IDENTIFIER ::= { prtInputTable 1 } prtOutput OBJECT IDENTIFIER ::= { printmib 9 } prtOutputTable OBJECT IDENTIFIER ::= { prtOutput 2 } prtOutputEntry OBJECT IDENTIFIER ::= { prtOutputTable 1 } tables OBJECT IDENTIFIER ::= { device 7 } channel-table OBJECT IDENTIFIER ::= { tables 2 } channel-entry OBJECT IDENTIFIER ::= { channel-table 1 } prtChannel OBJECT IDENTIFIER ::= { printmib 14 } prtChannelTable OBJECT IDENTIFIER ::= { prtChannel 1 } prtChannelEntry OBJECT IDENTIFIER ::= { prtChannelTable 1 } printed-media-usage OBJECT IDENTIFIER ::= { printer-accounting 1 }

localization-language OBJECT-TYPE SYNTAX INTEGER { eEnglish(1), eFrench(2), eGerman(3), eSpanish(4), eItalian(5), eSwedish(6), eDanish(7), eNorwegian(8), eDutch(9), eFinnish(10), eJapanese(11), ePortuguese(12), ePolish(13), eTurkish(14) } ACCESS read-only STATUS optional DESCRIPTION "Localization language used by the device for device generated PML strings, control panel messages, and text contained in any of the printer generated printed pages. The order is the same order that is defined in MIO. Since the MIO values start at zero, one has been added to each value." ::= { status-system 1 }

not-ready-printer OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS mandatory DESCRIPTION "Indicates if any of the sub-systems in the printer are not ready. A sub-system is not ready if the sub-system is unable to perform its function until some sort of intervention occurs. If there are no items in the NOT- READY-PRINTER collection (i.e. no bits are set), then all printer sub- systems are ready. Each sub-system has a sub-system specific not ready object. If a sub-system specific not ready object contains any items, then the associated item will be in the NOT-READY collection." ::= { status-system 2 }

not-ready-controller OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional 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." ::= { status-system 3 }

not-idle OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "Indicates if any of the sub-systems in the device are not idle. The I/O source sub-system is considered not idle if there is unprocessed PDL data in the device. The PDL processing sub-system is considered not idle if the device is processing a print job. The print engine destination sub-system is considered not idle if media is moving (i.e. the device is printing). [other text here describing what causes the other sub-systems to be considered not idle]." ::= { status-system 4 }

on-off-line OBJECT-TYPE SYNTAX INTEGER { eOnline(1), eOffline(2), eOfflineAtEndOfJob(3) } ACCESS read-write STATUS optional DESCRIPTION "To bring the PDL processing sub-system on or off line. If the device is a printer, then the printer does not process print job data when the printer is off line. PML communication persists. Additional information: When the printer is in the Offline state, printing will stop as soon as possible (no more sheets of media are pulled from input trays). The I/O is taken offline also.

Setting to eOnline has the following affect: Printer will immediately go to or remain in the Online state; <noError> status is returned. If the printer's current state is Offline with a pending error condition that prevents the printer from going to the Online state, the printer will remain in the Offline state; <genErr> status is returned

Setting to eOffline has the following affect: Printer will immediately go to or remain in the Offline state; <noError> status is returned. If pages are being printed, those pages will complete with the printer in the Offline state.

Setting to eOfflineAtEndOfJob has the following affect: If not in a job or already in the Offline state, the printer will immediately go to or remain in the Offline state; <noError> status is returned. If in a job and the current state is Online, the printer will remain in the Online state, with the value of this object as eOfflineAtEndOfJob, until the end of the job; <noError> status is returned. At the end of the job, the printer goes to the Offline state and the value of this object becomes eOffline. Setting this object to eOffline or eOnline before the end of the job causes the action for that value to be taken immediately." ::= { status-system 5 }

continue OBJECT-TYPE SYNTAX INTEGER { eInitiateAction(1) } ACCESS write-only STATUS optional DESCRIPTION "A device can support a class of errors called continuable errors. When a continuable error is encountered, the device requires a continue event to occur before the device will continue operation. One continue event is setting the CONTINUE object to eInitiateAction. Devices can support other continue events, like auto-continue. A continue event causes the continuable error to be acknowledged, thus allowing the device to continue. Each device needs to list the continuable errors. If the device doesn't currently have an unacknowledged continuable error, the response will contain <genErr>. Additional information: See the CLEARABLE-WARNING and AUTO-CONTINUE objects for the errors that this object will clear." ::= { status-system 6 }

user-nvram-reset OBJECT-TYPE SYNTAX INTEGER { eTrue(1) } ACCESS write-only STATUS optional DESCRIPTION "Setting to eTrue causes all user NVRAM settings to factory default settings. May also perform POWER-ON- RESET functionality thus loosing print job data. The POS will list which objects are effected by a user NVRAM reset. Some items are NVRAM settings, but not user controllable, so this action may not cause all of NVRAM to be reset. Some examples of NVRAM settings that may not be affected are page count, internally used pen information, line configuration information, etc. Additional information: Setting to eTrue returns the NVRAM items listed below to their factory default values. Performs the same function as the 'MENU RESET' function supported by the control panel except when printer is in Offline state, setting this OID to eTrue will not take the printer to the Online state. DEFAULT-COPIES DEFAULT-MEDIA-SIZE DEFAULT-ORIENTATION DEFAULT-LINES-PER-PAGE DEFAULT-MANUAL-FEED DEFAULT-RET DEFAULT-PRINT-QUALITY PCL-DEFAULT-FONT-SOURCE PCL-DEFAULT-FONT-NUMBER PCL-DEFAULT-FONT-HEIGHT PCL-DEFAULT-FONT-WIDTH PCL-DEFAULT-SYMBOL-SET DEFAULT-VERTICAL-BLACK-RESOLUTION DEFAULT-HORIZONTAL-BLACK-RESOLUTION DEFAULT-PDL CONTEXT-SENSITIVE-PDL-SELECTION ENERGY-STAR IO-TIMEOUT DEFAULT-PAGE-PROTECT POSTSCRIPT-JAM-RECOVERY (PostScript installed) POSTSCRIPT-PRINT-ERRORS (PostScript installed)" ::= { status-system 12 }

total-ram-size OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Identifies total amount of RAM, in bytes, available to the controller for general computing." ::= { status-system 21 }

status-printer OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS mandatory DESCRIPTION "Indicates if any of the sub-systems in the device in a warning condition. A warning condition exists if the sub-system is useable, but not at its highest state of functionality." ::= { status-system 22 }

status-controller OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-only STATUS optional DESCRIPTION "Indicates if the hardware controller sub-system in a warning condition." ::= { status-system 23 }

auto-continue OBJECT-TYPE SYNTAX INTEGER { eOff(1), eOn(2) } ACCESS read-write STATUS optional DESCRIPTION "Indicates if the device will automatically continue after encountering a continuable error. If AUTO- CONTINUE is set to eOn, the device will automatically generate continue event to acknowledge continuable errors. If AUTO-CONTINUE is set to eOff, then some other continue event will have to acknowledge the continuable error. Additional information: If this is set to eOn the device displays an error message and goes offline for ten seconds. After ten seconds the printer automatically returns to the online state.

If this is set to eOff then the device displays an error message and goes offline. It remains offline until the operator presses the GO key or until the CONTINUE object is set.

If the printer is not idle, the new value may not take effect until a job boundary is reached. If a get is done on this object before the job boundary is reached, the value last set will be returned." ::= { status-system 7 }

display-column-size OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Indicates the number of characters displayable on each row of the printer's display." ::= { display-status 1 }

display-number-of-rows OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Indicates the number of rows displayable on the printer's display." ::= { display-status 2 }

status-msg-line1-part1 OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "First part of the first line of the printer's status message. Additional information: In the Offline state, device only returns 00 OFFLINE and not the actual content of control panel display." ::= { status-message1 1 }

background-status-msg-line1-part1 OBJECT-TYPE SYNTAX DisplayString (SIZE(0..16)) ACCESS read-write STATUS optional DESCRIPTION "The string displayed on the device's front panel in place of the printer's built-in background status string. An example built-in background status string is '00 READY'. Additional information: The display size for the LaserJet 4050 Series printers is 2 X 16. The value of this object and the current value of BACKGROUND-STATUS-MSG-LINE2-PART1 are displayed together on the 2-line display, but they must be set independently. If line 2 has been set, and the next message to be displayed only requires line 1, BACKGROUND-STATUS-MSG-LINE2-PART1 must be set to the null string to clear it. This object allows a message to be displayed when it is the highest priority message. Setting this object does not guarantee the message will be displayed; and reading it returns the value last written, not the currently displayed message (use prtConsoleDisplayBufferText to read the display). The priority assigned for displaying this message is one lower than the READY message. In other words, the only message that can be replaced by these objects is the READY message. To clear the message, write a null string to both this object and BACKGROUND-STATUS-MSG-LINE2-PART1." ::= { background-message1 1 }

background-status-msg-line2-part1 OBJECT-TYPE SYNTAX DisplayString (SIZE(0..16)) ACCESS read-write STATUS optional DESCRIPTION "The string displayed on the device's front panel in place of the printer's built-in background status string. An example built-in background status string is '00 READY'. Additional information: See BACKGROUND-STATUS-MSG-LINE1-PART1" ::= { background-message2 1 }

error-log-clear OBJECT-TYPE SYNTAX INTEGER { eClearErrorLog(1) } ACCESS write-only STATUS optional DESCRIPTION "Setting this object clears all the entries in the error log sub-tree. Additional information: Setting this object removes all errors that have been stored in the printer's non-volatile memory." ::= { status-system 38 }

localization-languages-supported OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "The list of languages supported by the device. The languages are primarily, but not limited to, two character codes from ISO 639, each separated by a comma character. Additional information: This string will always be in the Roman-8 character set. See prtLocalizationLanguage for details about each language value." ::= { status-system 52 }

localization-countries-supported OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "The list of countries supported by the device. The countries are primarily, but not limited to, two character codes from ISO 3166, each separated by a comma character. Additional information: This string will always be in the Roman-8 character set. See prtLocalizationCountry for details about each country value." ::= { status-system 53 }

control-panel-button-press OBJECT-TYPE SYNTAX INTEGER { eGoButton(1), eMenuPlusButton(2), eMenuMinusButton(3), eItemPlusButton(4), eItemMinusButton(5), eValuePlusButton(6), eValueMinusButton(7), eSelectButton(8), eCancelJobButton(9) } ACCESS write-only STATUS optional DESCRIPTION "Writing this object simulates pressing a button on the control panel." ::= { status-system 60 }

model-number OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "Identifies the device model number as listed in the HP corporate price list (e.g. C2121A for DeskJet 500C). The string is as specific as possible. Products should note in POS if the model number on the CPL changes but the device reports the previous model number. If the model number changes based on the installed options, the POS should indicate if only the base model number is returned, or if the device senses the installed options and returns the correct model number. If possible, encode the model number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: The value of this object does not change based on the installed options. The default of this object is the same on all LaserJet 4050 Series printers." ::= { id 1 }

serial-number OBJECT-TYPE SYNTAX DisplayString (SIZE(0..10)) ACCESS read-only STATUS optional DESCRIPTION "Identifies the serial number for the device. If the SERIAL-NUMBER object is set by the user, then setting the object does not need to be protected. If the SERIAL-NUMBER object is set at the factory, then the SERVICE-PASSWORD object must be set correctly before the SERIAL-NUMBER object is writable. If this is a writable object, the POS should indicate the maximum supported string length. If possible, encode the serial number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: This value IS AFFECTED BY NVRAM resets, it is set to the default value of XXXXXXXXXX, when a NVRAM init is done." ::= { id 3 }

fw-rom-datecode OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "Identifies the base system firmware date code. The date code will be encoded in the yyyymmdd format. There may be several versions of the base system firmware. The date code associated with the version of the base system firmware that is being used is reported. There may be other date code objects for other specific modules such as fonts, localization modules, etc.; these other datecode objects are device specific." ::= { id 5 }

device-location OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS optional DESCRIPTION "User defined device location. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <noError>.

Additional information: The maximum supported string length is 16 characters. If the user entered string is too long, the device will store the first 16 characters and will return the <noError> status." ::= { id 11 }

asset-number OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS optional DESCRIPTION "User defined asset number. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <noError>.

Additional information: The maximum supported string length is 8 characters. If the user entered string is too long, the device will store the first 8 characters and will return the <noError> status." ::= { id 12 }

system-contact OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS optional DESCRIPTION "User defined string containing the name of the person or group that is responsible for the device. The POS should indicate the maximum supported string length. If the user entered string is too long, the device will store as much as possible and will return the <noError>. Additional information: User defined system contact. The maximum supported string length is 16 characters. If the user entered string is too long, the device will store as much as possible and will return the <noError> status." ::= { id 13 }

at1-model-number OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "Identifies the AT model number. If the disk was manufactured by HP, then the model number is the one listed in the HP corporate price list. If possible, encode the model number in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: The model number is obtained from the disk using the IDE (Intelligent Drive Electronics) Identify command. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed." ::= { at1 1 }

at1-model-name OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "Returns product information identifying the AT storage device. Example: C3014A Additional information: The product information is obtained from the disk using the IDE (Intelligent Drive Electronics) Identify command. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed." ::= { at1 2 }

at1-manufacturing-info OBJECT-TYPE SYNTAX DisplayString ACCESS read-only STATUS optional DESCRIPTION "Returns information describing the manufacture of this particular AT. May include serial number and firmware revision. Additional information: Returns the model number, serial number, and firmware revision of the installed disk. This information is obtained from the disk using the IDE (Intelligent Drive Electronics) Identify command. Example: HP C3014A JP932412W9 K2A4A059. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed." ::= { at1 3 }

at1-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eDiskDrive(8) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in this particular AT interface. See SIMM1-TYPE for an explanation of the enumerations. Additional information: eEmpty means the device did not detect any AT. eDiskDrive means the AT contains a disk drive." ::= { at1 4 }

at1-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the installed option. See SIMM1-CAPACITY for an explanation of the meaning of the value of this object. Additional information: This object contains the size, in bytes, of the installed disk option. This objects is only supported if a disk is installed. Returns <noSuchName> status if attempting to perform a Get on this OID with no disk installed. Returns <noSuchName> status if attempting to perform a Set, EnableTrap, or DisableTrap on this OID with no disk installed." ::= { at1 5 }

simm1-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5), eFlashMemory(7), eRamRom(9) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 1. eEmpty means the device did not detect any option installed in the interface slot. eUnknown means the device doesn't recognize the installed option. eUnSupported means the device recognizes the installed option, but does not support the option. eReadOnlyMemory means the installed option contains ROM Ics. eVolatileRandomAccessMemory means the installed option contains RAM ICs that loose data when the power is turned off. eNonVolatileRandomAccessMemory means that the installed option contains RAM ICs that do not loose data when the power is turned off. eFlashMemory means that the installed option contains a type of non-volatile RAM that needs to be erased before it can be written. eDiskDrive means the installed option contains a disk drive. eRamRom means the installed option contains both volatile random access memory and read only memory. eInputPHD means the installed option is an input paper handling device. eOutputPHD means the installed option is an output paper handling device. eIOCard means the installed option is an I/O card. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. eRamRom is used to denote LaserJet 4050 Series's combo simm." ::= { simm1 4 }

simm1-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 1. The capacity is dependent on the type of option, as indicated by the SIMM1-TYPE object. This object has no meaning if the installed option type is eUnknown or eReadOnlyMemory. This object contains the size, in bytes, if the installed option type is eVolatileRandomAccessMemory, eNonVolatileRandomAccessMemory, eFlashMemory, or eDiskDrive. If the type of the installed option is eRamRom, this object contains the size, in bytes, of the random access memory. If the type of the installed option is eInputPHD, the capacity indicates the number of input trays supported by the installed option. If the type of the installed option is eOutputPHD, the capacity indicates the number of output bins supported by the installed option. If the type of the installed option is eIOCard, the capacity indicates the number of logical I/O ports supported by the I/O card. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM1-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the SIMM is returned." ::= { simm1 5 }

simm2-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5), eFlashMemory(7), eRamRom(9) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 2. See SIMM1-TYPE for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. eRamRom is used to denote LaserJet 4050 Series's combo simm." ::= { simm2 4 }

simm2-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 2. See SIMM1-CAPACITY for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM2-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the SIMM is returned." ::= { simm2 5 }

simm3-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5), eFlashMemory(7), eRamRom(9) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 3. See SIMM1-TYPE for a description." ::= { simm3 4 }

simm3-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 3. See SIMM1-CAPACITY for a description. Additional information: This object is used for describing DIMMs instead of SIMMs on LaserJet 4050 Series. Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM3-TYPE type is eVolatileRandomAccessMemory, eRamRom, or eFlashMemory. For eRamRom only the size of the Ram portion of the simm is returned." ::= { simm3 5 }

simm4-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 4. See SIMM1-TYPE for a description." ::= { simm4 4 }

simm4-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 4. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM4-TYPE type is eVolatileRandomAccessMemory." ::= { simm4 5 }

simm5-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 5. See SIMM1-TYPE for a description." ::= { simm5 4 }

simm5-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 5. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM5-TYPE type is eVolatileRandomAccessMemory." ::= { simm5 5 }

simm6-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 6. See SIMM1-TYPE for a description." ::= { simm6 4 }

simm6-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 6. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM6-TYPE type is eVolatileRandomAccessMemory." ::= { simm6 5 }

simm7-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 7. See SIMM1-TYPE for a description." ::= { simm7 4 }

simm7-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 7. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM7-TYPE type is eVolatileRandomAccessMemory." ::= { simm7 5 }

simm8-type OBJECT-TYPE SYNTAX INTEGER { eEmpty(1), eUnknown(2), eUnSupported(3), eReadOnlyMemory(4), eVolatileRandomAccessMemory(5) } ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the type of option installed in SIMM slot 8. See SIMM1-TYPE for a description." ::= { simm8 4 }

simm8-capacity OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS optional DESCRIPTION "Returns an indication of the capacity of the SIMM installed in SIMM slot 8. See SIMM1-CAPACITY for a description. Additional information: Returns an indication of the capacity of the installed option in bytes. This object is not supported unless the SIMM8-TYPE type is eVolatileRandomAccessMemory." ::= { simm8 5 }

self-test OBJECT-TYPE SYNTAX INTEGER { eNotInASelfTest(1), eNonDestructiveSelfTest(4) } ACCESS read-write STATUS optional DESCRIPTION "Writing this object allows a device self test to be started. Reading this object provides an indication what self-test is currently executing, if any. Actual self-test operation is device specific. A self test may not be allowed at any arbitrary time. If the device supports the requested self test, but can not start the execution of the self test when requested, the device will respond with <genErr>. If a non-destructive self test is being started, the device will generate a response before the self test is co

Created on Jul 15, 2011 10:23:53 AM



Votes:

0

I think that there is no possibility monitoring toner level, offline status, or jammed, and so on Only the state is ready / not ready Am I right?

Created on Jul 15, 2011 10:30:38 AM



Votes:

0

I think that there is no possibility monitoring toner level, offline status, or jammed, and so on Only the state is ready / not ready Am I right?

Created on Jul 15, 2011 10:30:59 AM



Votes:

0

Use of this MIB, I compile oidlib. But the list of sensors is not hrPrinterDetectedErrorState, which can take Condition ​​noPaper, lowToner, doorOpen and so on.

PS sorry for my english, because it is a compilation of translation by my self and ggle )))

Created on Jul 15, 2011 12:18:55 PM



Votes:

0

Hello! And why when I imported MIB I can not create a sensor hrPrinterDetectedErrorState. Simply it is not listed. Although I used the correct OID, obtained using snmpwalk.

Missing all objects OCTET STRING. Available only INTEGER

Created on Jul 19, 2011 6:02:05 AM



Accepted Answer

Votes:

0

at the moment PRTG MIB importer only imports OIDs that return integers, no strings.

Created on Jul 19, 2011 7:14:23 AM by  Aurelio Lombardi [Paessler Support]



Votes:

0

If you say that does not support strings value, then you have to use prtMarkerSuppliesLevel object (for toner level), it is INTEGER value and is supported by PRTG. I think it's right or at least I can see when to change cartridge. Problem solved. Thanks to everyone who helped me.

Regards

Created on Jul 19, 2011 8:54:13 AM



Votes:

0

Can you please tell me when PRTG will be able to handle SNMP Octet strings and counters?

Created on Nov 4, 2011 10:05:37 AM



Votes:

0

Importing String Counters with the MIB Importer is definitely in the pipeline, but I'm afraid we can't give you an ETA when it'll be available.

In the meantime you can help yourself by adding SNMP Custom String sensors manually.

Kind regards,

- Volker

Created on Nov 7, 2011 11:51:01 AM by  Volker Uffelmann [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.