All MIBs › IJ8060-MIB
Category: Device Management, Hardware and Environment
Description: MIB for the IJ8060 device providing hardware status and management objects for this network equipment.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is IJ8060-MIB?
This is a printer/imaging device MIB for the IJ8060 device; object naming and "hp"/"dm" branches suggest an HP-derived or HP-compatible print-engine MIB, tracking print job usage and consumable/billing counters. It exposes simplex/duplex page counts and their associated billing charge values, total pages printed, maximum pixels per page, and usage counters for total charge and staple count, plus usage instruction/status lines. Rather than classic CPU/temperature hardware health, its monitoring role is print-usage and consumable status: tracking pages printed (simplex vs duplex), staple usage, and billing charges lets an operator monitor the device's operational load and detect abnormal usage patterns or billing/metering discrepancies. It appears related to standard printer-MIB conventions (page counters) given the naming, though the exact relationship to a base printer MIB is not explicit from the available data. It is typically deployed on office/production multifunction printers or copiers for usage tracking, billing/chargeback, and consumable monitoring, with IJ8060-MIB SNMP monitoring providing the page-count and staple-usage data those workflows depend on.
IPNetwork Monitor allows you to monitor SNMP objects defined in IJ8060-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- HP-compatible printer/multifunction device (IJ8060 print engine)
Monitoring Examples
An operator polls printed-media-simplex-count and printed-media-duplex-count to see the page-volume split, and usage-printer-total-charge to reconcile metered billing charges against actual print volume. printed-media-combined-total gives the overall page count, while usage-staple-count tracks finishing-unit usage; a sudden jump in usage-staple-count without a corresponding rise in printed-media-total-charge could indicate the staple unit is malfunctioning or being triggered independently of actual print jobs, and usage-instructions-line1 likely surfaces an operator-panel status message such as "add staples" or "load paper".
What Can Be Monitored
- simplex/duplex page counts
- total pages printed
- billing/charge counters
- staple usage count
- device status/instruction messages
- maximum pixels per page
Related MIBs
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| INT _pysmi_continue | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.6 | INTEGER | write-only | 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 . Additional information: See the CLEARABLE-WARNING and AUTO-CONTINUE objects for the errors that this object will clear. |
| accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16 | |||
| active_print_jobs | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.2 | |||
| OCT asset_number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.12 | OCTET STRING | read-write | 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 .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 status. |
| INT auto_continue | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.7 | INTEGER | read-write | 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. |
| INT automatic_daylight_savings | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.100 | INTEGER | read-write | Determines whether or not the automatic adjustment for daylight savings time is enabled. If it's enabled the device local time will be automatically adjusted for DST period. Additional information: Determines whether or not the automatic adjustment for daylight savings time is enabled. If its enabled the device local time will be automatically adjusted for DST period |
| background_message | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37 | |||
| background_message1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.1 | |||
| background_message2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.2 | |||
| OCT background_status_msg_higher_priority | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.5 | OCTET STRING | read-write | The string displayed on the device's front panel in place of the printer's built-in background status string. It would alternate with warning messages and would overwrite highest Regular Priority Status message such as PAUSED. The object could be used to display higher priority third party messages which are important to be displayed even if printer is offline. This would not overwrite any HighStatus or Error type message. Additional information: 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 lower than the PAUSED message. In other words, this messages can replace all the regular priority status messages as EPOffline is the highest regular status priority. To clear the message, write a null string to BACKGROUND-STATUS-MSG-HIGHER-PRIORITY. |
| OCT background_status_msg_line1_part1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.1.1 | OCTET STRING | read-write | 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 Inkjet 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. |
| OCT background_status_msg_line2_part1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.37.2.1 | OCTET STRING | read-write | 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 |
| INT cancel_job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.2 | INTEGER | write-only | Cancels the print job whose ID matches the value written to the CANCEL-JOB object. The host first learns the job ID using the CURRENT-JOB-PARSING-ID command. If the printer has completely processed the job, the printer responds with . If the value of the CURRENT-JOB-PARSING-ID is smaller than the value written to the CANCEL-JOB object, then the printer responds with . When read, returns the value of the last job ID what was canceled, or -1 to indicate no job has been canceled. Additional information: If the value written matches the ID of a job that is currently being canceled (for any reason), the printer responds with . It uses job ID's in the range of -1..32767. Because the ID number can wrap to zero, CURRENT-JOB-PARSING-ID may be smaller than the value written to this object; when this occurs, no error will result as long as the ID is for a currently processing job. This object is write only, so the comment in the general description stating the job ID will be returned on a read does not apply. A -1 represents the current job |
| INT cartridge_out_override_control | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.27 | INTEGER | write-only | This PML object is used to control Cartridge Out Override feature. Additional information: This object is used for the following purposes: 1. Set MarkEmptyOverride for a given cartridge. 2. Set/clear NonHPEnabled for a given cartridge. 3. Query internal variable SupplyUserConfirm for a given cartridge. 4. Query internal variable ConfirmedNonHP for a given cartridge. |
| INT clearable_warning | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.1 | INTEGER | read-write | Returns or controls how the device will track clearable warnings. A clearable warning indicates a transient event in the device. The device will continue after the transient event occurs. If CLEARABLE-WARNING is eOff, the device does not track clearable warnings. If CLEARABLE-WARNING is eOn, all clearable warnings will be tracked until cleared (acknowledged). If CLEARABLE-WARNING is eJob, a clearable warning generated due to an event that occurs because of the print job being processed will be automatically cleared when the device has finished processing the job. Example clearable warning events include the device altering resolution or page protection due to memory constraints. The POS will document what transient events are treated as clearable warnings. Additional information: If set to eOn, the warning is displayed until the GO key is pressed or the CONTINUE object is set. If set to eJob, the warning is displayed until the end of the job in which it was generated. |
| INT cold_reset_media_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.19 | INTEGER | read-write | Returns or sets the media size that is used as the DEFAULT-MEDIA-SIZE when a cold reset occurs. |
| OCT collated_originals_support | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.42 | OCTET STRING | read-only | Indicates that the printer can create multiple, collated 'originals' of a job and shows the level of support for this capability. cCollatedOriginals - The printer can create multiple collated originals, or 'mopies'. This is the base functionality required by the other collection items. cProofAndHold - The printer saves a copy of the job while printing the first mopy. Later, this held job can be released and the rest of the mopies will print. cSecurityPrint - The printer spools the job and holds the job until the user releases the job by entering a > at the printer's control panel. cAutoHighlight - The printer prints the job a number of times with a mail distribution list prepended to each job. A different mailing address is highlighted on each mopy. cCollatedAtSpeed - The printer can create multiple collated copies where all copies after the original are printed at engine speed. Additional information: Indicates that the printer can create multiple, collated originals of a job and shows the level of support for this capability. cCollatedOriginals - The printer can create multiple collated originals, or mopies. This is the base functionality required by the other collection items. Without disk, this object will not exist. This will be set at boot-up initialization. If the disk fails, in any way, then the disk error functionality will handle the situation. A color printer that only has a RAMDISK installed is treated like there is no disk and therefore this object will not exist. The value of this object will be: !cCollatedOriginals - Only FLASH installed cCollatedOriginals - IDE is installed combined with/without FLASH cCollatedOriginals - RAMDISK is On combined with/without FLASH |
| INT configurable_low_threshold_setting | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.24 | INTEGER | read-write | This PML object can be used to configure the low threshold for supplies. Additional information: This PML object can be used to configure the Low Threshold for Supplies. |
| OCT consumable_current_state | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.7 | OCTET STRING | read-only | This PML object returns the current state of the particular consumable. cAuthLevel1 - Consumable is at Authentication Level 1 cAuthLevel2 - Consumable is at Authentication Level 2 cAuthLevel3 - Consumable is at Authentication Level 3 cAuthLevel4 - Consumable is at Authentication Level 4 cAuthLevel5 - Consumable is at Authentication Level 5 cGenuineHPUnsupported - Cartridge is GenuineHP intended for another product cDefectiveMemory - Cartridge has a defective memory tag cMissingMemory - Memory tag is missing from the cartridge cLowCondition - Consumable has reached the engine low threshold cOutCondition - Consumable has reached its out threshold cIncorrect - Cartridge inserted is not the correct one cMissing - Consumable is missing from the printer cConfigurableLow - Consumable has reached the configurable low threshold value cStatusArevalid - The status reported on other bits are valid only if the bit is set to 1. If it is 0, the values are invalid. cExpired - Is the cartridge expired, which is determined by the formatter. cFailure - Cartridge has failed determined by the engine. cLeak - Cartridge has a leak as determined by the engine. cUnknownManufacturer - the brand of the cartridge is unknown as determined by the engine. cUnsupported --- Cartridge is not supported as determined by the engine. These are the possible states and whenever the consumable is in any of these states, the appropriate bit will be set. The cLowCondition will be set when the consumable reaches the engine low threshold, and cConfigurableLow will be set when the consumable reaches the Configurable Low threshold value. For non-cartridge supplies only cLowCondition, cOutCondition, and cMissing will be supported. Additional information: This object returns the current state of the particular consumable. cAuthLevel1 - HP genuine cAuthLevel2 - Condor's Non-HP (Canon's Clone) cAuthLevel3 - refilled cAuthLevel5 - Condor's ApprovedOEM cOutCondition - empty cMissing - not installed cConfigurableLow - configurable low cExpired - cartridge, determined by formatter cFailure - failure cLeak - leak cUnknownManufacturer - Non-HP cartridge which has not been enabled cUnsupported - something wrong on a new cartridge, not compatable cStatusAreValid - The Status reported on other bits are valid only if this bit is set to 1. If it is 0, the values are invalid. These are the possible states and whenever a Consumable is in any of these states, the appropriate bit will be set. |
| INT consumable_life_low_threshold | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.5.1.3 | INTEGER | read-only | This object is used to report and modify a threshold value indicating the point in the life of a consumable or supply at which a transition to a LOW state will occur. |
| INT consumable_life_usage_units | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.5.1.2 | INTEGER | read-only | This object reports current usage units in use by the corresponding CONSUMABLE-LIFE-USAGE-UNITS-REMAINING object. Additional information: This object returns the units that CONSUMABLE-LIFE-USAGE-UNITS-REMAINING is returned in. Either ePagesRemaining(1) or eEstimatedPagesRemaining(2). |
| INT consumable_life_usage_units_remaining | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.5.1.1 | INTEGER | read-only | This object reports the current estimate of the number of usage units that remain before this supply is depleted. An installed supply that cannot report such a number will return a value of -2. It is the reponsibility of the host application to query each supply in order to determine an overall device USAGE-UNITS-REMAINING number - the lowest value returned. The unit of measure for this life estimate is determined by reading the corresponding CONSUMABLE-LIFE-USAGE-UNITS object. Additional information: This object will return the Pages or Estimated Pages remaining for the speciffic supply requested by the leaf node of this object. |
| OCT consumable_notification_status | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.10 | OCTET STRING | read-write | This object is used to read and write the various status flags supported by this consumable. For gandalf the collection bits supported include: cClient1ReorderNotificationSent - indicates whether EWS (Embedded Web Server) has already sent the reorder notification e-mail for this consumable. This bit can be both read and written. cClient2ReorderNotificationSent - indicates whether WJA (Web Jet Admin) has already sent the reorder notification e-mail for this consumable. This bit can be both read and written. cClient3ReorderNotificationSent - for future implementation cClient4ReorderNotificationSent - for future implementation cClient5ReorderNotificationSent - for future implementation cClient1ReplaceNotificationSent - indicates whether EWS (Embedded Web Server) has already sent the replace notification e-mail for this consumable. This bit can be both read and written. cClient2ReplaceNotificationSent - indicates whether WJA (Web Jet Admin) has already sent the replace notification e-mail for this consumable. This bit can be both read and written. cClient3ReplaceNotificationSent - for future implementation cClient4ReplaceNotificationSent - for future implementation cClient5ReplaceNotificationSent - for future implementation Additional information: This object will have 1 sub arrays for the consumable. The client1 and 2 currently are assingned to EWS and WJA the remaining client are reserved for the future third party pml tools. A client is requiered to set only his assigned bit for reorder or replace notification. A client using other client's bit for reorder replace will result in the other client being not able to set the notification. Ex: For EWS ReOrderNotification it will send 0x00010000 and For EWS ReplaceNotification it will send 0x00000001 For WJA ReOrderNotification it will send 0x00020000 and For WJA ReplaceNotification it will send 0x00000002 |
| INT consumable_pages_printed_with_supply | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.11 | INTEGER | read-only | This PML object returns the number of pages printed with a cartridge consumable. This PML object returns the value that should be displayed under 'Pages Printed With This Supply' for cartridges in color products. Additional information: This PML object returns the number of pages printed with a Cartridge Consumable. This PML object returns the value that should be displayed underPages Printed With This Supply for Cartridges in Color products. |
| OCT consumable_reorder_url | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.2 | OCTET STRING | read-write | This object is used to read and write the URL that can be used to reorder consumables for this device. This URL is set at the factory but can be updated by a reseller or third party. Additional information: The URL can be up to 64 characters long. |
| consumable_status | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.1.1 | |||
| INT consumable_status_capacity_units | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.1.1.4 | INTEGER | read-only | This object is used to report the usage units used by the CONSUMABLE-STATUS-TOTAL-CAPACITY object. Additional information: Defines the units for the total capacity of a supply, which is given by CONSUMABLE-STATUS-TOTAL-CAPACITY |
| OCT consumable_status_expiration_date | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.1.1.79 | OCTET STRING | read-only | Indicates the ink cartridge expiration date in yyyymmdd format. An unknown date is represented by the date 00000000. Additional information: Indicates the ink cartridge expiration date in yyyymmdd format. An unknown date is represented by the date 00000000 |
| INT consumable_status_total_capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.1.1.5 | INTEGER | read-only | This object is used to report the total capacity of a new consumable of this type. The PML object CONSUMABLE-STATUS-CAPACITY-UNITS can be used to determine the units of measure for this PML object. Additional information: Return capacity of cartridge in units defined in CONSUMABLE-STATUS-CAPACITY-UNITS. |
| consumable_string | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.8 | |||
| OCT consumable_string_information | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.8.1 | OCTET STRING | read-write | This object is used to read and write the string value that describes the consumable information. |
| INT consumable_string_information_reset | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.8.2 | INTEGER | read-write | This object is used to reset (set back to factory default) or read the current status of the corresponding information string. When Set to eResetToDefault, this object can be used to reset the corresponding information object back to its factory default value. Setting this object with an enumerated value of eCustomized has no effect. When a Get operation is performed on this object it will return a value eResetToDefault if still set to its factory value. It will return eCustomized if the corresponding information value has been set to a custom value. Additional information: This object returns ePresetToNVRAM(1) if CONSUMABLE-STRING-INFORMATION is currently set to the default string. It will return eCustomized(2) otherwise. However, we can explicitly set this object only to ePresetToNVRAM(1) and not eCustomized(2). |
| consumables | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10 | |||
| consumables_1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.1 | |||
| consumables_life | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.5.1 | |||
| consumables_status | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.5 | |||
| INT control_panel_button_press | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.60 | INTEGER | write-only | Writing this object simulates pressing a button on the control panel. Reading it will return the last key pressed either on the control panel or via PML. The device POS will specify which keys are supported. |
| control_panel_display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.65 | |||
| INT control_panel_display_contents_change_counter | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.63 | INTEGER | read-only | A counter which increments whenever the contents of the front panel display changes. This object is implemented as a 32-bit signed integer which rolls over to zero when it reaches a maximum value. |
| INT control_panel_display_contents_crc | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.64 | INTEGER | read-only | Reading this object returns a 32-bit Cyclical Redundancy Check (CRC) which represents the current contents of the display. Additional information: This object has been implimented as an 32-bit CRC for this product. |
| OCT control_panel_display_graphical_contents | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.65.1 | OCTET STRING | read-only | Reading this object returns a graphical file format image representing the current pixel content of the display. The device POS will specify the expected screen resolution, color depth of the display and graphics file format for a given product (eg. 160x64x1 GIF format OR 640x240x4 JPEG format). If the image is large enough that it needs to be returned in multiple objects then each array object will contain a portion of the image. The image will then need to be reconstructed by a host application. An application that needs to determine if their is an additional object to be retreived will need to perform a GETNEXT operation until there are no more objects in the sub-tree. Additional information: This object returns a GIF image that represents the current contents of the 640x240x2 control panel display. Most display images require more than one instance of this object in order to retreive the complete GIF image. |
| INT control_panel_key_press | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.66 | INTEGER | write-only | Writing this object simulates pressing a key on the control panel. Reading it will return the last key pressed either on the control panel or via PML. This object obsoletes/replaces CONTROL-PANEL-BUTTON-PRESS object which was unable to represent each of the possible key combinations of our current control panels (ie. Full QWERTY keyboard). The device POS will specify the full range of keys supported by this object. Additional information: >>>>This object is write-only for hw_rom variant but it is read-write for all other variants.<<<<< Writing this object simulates pressing a key on the control panel. Reading it will return the last key pressed either on the control panel or via PML. This object obsoletes/replaces CONTROL-PANEL-BUTTON-PRESS object which was unable to represent each of the possible key combinations of our current control panels (ie. Full QWERTY keyboard). The device POS will specify the full range of keys supported by this object. The implementation of this object supports the Unified Key Encoding Scheme. |
| INT control_panel_supplies_status_message | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.44 | INTEGER | read-write | This PML object can be used to enable or disable supplies status messages from being displayed on the control panel. eShow - show the status messages on the control panel. eDontShow - do not show the status messages on the control panel. Additional information: . This PML Object can be used to enable or disable the supplies status messages from being displayed on the control panel. eShow Show the status messages on the control panel. eDontShow Do not show the status messages on the control panel. |
| INT current_job_parsing_id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.2.1.1 | INTEGER | read-only | Contains the printer assigned job identification for the job currently being processed by the processing PDL sub-system. The job ID is a monotonically increasing number. The job ID may be reset to zero at power-up and may roll over to zero after reaching some maximum value. Additional information: A value of -1 is returned when the printer is not parsing a job. When data for a new job is detected, this object is updated (the job may or may not turn out to be a Null Job); however, the trap does not occur until the printer determines that it is not a Null Job. (A job is considered to be a 'null job' if it has no name or job attribute, causes no pages to be printed, and consumes MIN_JOB_SIZE (9) or fewer bytes.) A trapped value will differ from the previous value by one or more. See the Job Boundary ERS for details on what constitutes a job boundary. Some job-info- objects are created when the first data bytes are received. If the printer determines that the job is a Null Job, the job-info- objects related to the Null Job are deleted. InkJet retains the job-info- objects for the MAX_JOBS_IN_LIST (32) most recent jobs that are not Null Jobs. The first job received after power-up will have job ID 1, and the job ID will increment to 2,147,483,647 before rolling to zero. To distinguish whether a power cycle or a rollover causes a reduction in the job ID value, the object prtGeneralConfigChanges can be watched and if it increments at the same time as the drop is observed in the value of CURRENT-JOB-PARSING-ID, then a power cycle is the most likely cause. |
| INT custom_paper_feed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.8 | INTEGER | read-write | Sets the printer's custom paper dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Get/Set custom paper dimension (height). The return/set value is either in micrometers or 10,000ths of inches. A tray has to be in custom switch or without media size sensor to be able to set the custom dimension. If it is successfully setting the dimension value, the size of a tray is set to CUSTOM. If the current XFeed value is greater than the new Feed value, the firmware will silently set the XFeed to match the new Feed value. |
| INT custom_paper_xfeed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.9 | INTEGER | read-write | Sets the printer's custom paper dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Get/Set custom paper dimension (width). The return/set value is either in micrometers or 10,000ths of inches. A tray has to be in custom switch or without media size sensor to be able to set the custom dimension. If it is successfully setting the dimension value, the size of a tray is set to CUSTOM. If the new XFeed Dim is greater than the current Feed Dim, INVALID_OR_UNSUPPORTED_VALUE is returned. |
| OCT date_and_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.17 | OCTET STRING | read-write | A C structure containing the following fields: typedef struct { ubyte yr; /* year: 0 to 99 */ ubyte mon; /* month: 1 to 12 */ ubyte day; /* day: 1 to 31 */ ubyte wday; /* Day of week: 1 to 07 */ ubyte hr; /* hour: 0 to 23 */ ubyte min; /* minute: 0 to 59 */ ubyte sec; /* second: 0 to 59 */ } date_t; where ubyte is an unsigned byte (0-255). Additional information: A C structure containing the following fields: typedef struct { ubyte yr; /* year: 3 to 99 */ ubyte mon; /* month: 1 to 12 */ ubyte day; /* day: 1 to 31 */ ubyte wday; /* Day of week: 1 to 07 */ ubyte hr; /* hour: 0 to 23 */ ubyte min; /* minute: 0 to 59 */ ubyte sec; /* second: 0 to 59 */ } date_t; where ubyte is an unsigned byte (0-255). |
| INT date_display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.22 | INTEGER | read-write | Controls front-panel date display format. Additional information: Controls front-panel date display format. |
| OCT daylight_savings_end | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.102 | OCTET STRING | read-write | A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255). Additional information: A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255). |
| INT daylight_savings_offset | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.103 | INTEGER | read-write | Controls the offset in minutes to be added to the time when DST is in effect. Additional information: Controls the offset in minutes to be added to the time when DST is in effect |
| INT daylight_savings_reset | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.104 | INTEGER | read-write | This object is used to reset (set back to factory default for the current time zone) or read the current status of the DST settings. When Set to eResetToDefault, this object can be used to reset all the DST related objects back to their factory default values. Setting this object with an enumerated value of eCustomized has no effect. When a Get operation is performed on this object it will return a value eResetToDefault if all DST settings are still set to they factory value. It will return eCustomized if any DST parameter has been set to a custom value. Additional information: This object is used to reset (set back to factory default for the current time zone) or read the current status of the DST settings. When Set to eResetToDefault, this object can be used to reset all the DST related objects back to their factory default values. Setting this object with an enumerated value of eCustomized has no effect. When a Get operation is performed on this object it will return a value eResetToDefault if all DST settings are still set to they factory value. It will return eCustomized if any DST parameter has been set to a custom value. |
| OCT daylight_savings_start | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.101 | OCTET STRING | read-write | A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255). Additional information: A C structure containing the following fields: typedef struct { ubyte hour; /* hour: 0 to 23 */ ubyte weekday; /* weekday: 0(Sunday) to 6 */ ubyte occurrence; /* occurrence in the month: 1 to 5 */ ubyte month; /* month: 1 to 12 */ } dst; where ubyte is an unsigned byte (0-255). |
| INT default_bits_per_pixel | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.39 | INTEGER | read-write | Controls the number of levels used (per pixel) when printing grayscale or color images. |
| INT default_copies | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.4 | INTEGER | read-write | Returns or changes default copies. Default copies is the default values used by the PDL to control the number of copies of each page in the print job that are printed. The print job can override this value. The list of supported values should be documented in the device POS. Additional information: The supported values are 1 through 32000. Setting to an unsupported value causes the printer to substitute in a snap value and to return status. The snaps are as follows: 999 snaps to 32000 |
| INT default_custom_paper_dim_unit | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.10 | INTEGER | read-write | The units of measure used to specify the width and height of the printer's default custom paper size. The unit of measure of eTenThousandthsOfInches is 0.0001 inches. Additional information: The units of measure used to specify the width and height of the printer's default custom paper size. The unit of measure of eTenThousandthsOfInches is 0.0001 inches. |
| INT default_custom_paper_feed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.11 | INTEGER | read-write | Sets the printer's default custom paper size dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printer's default custom paper size dimension in the feed direction (direction parallel to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. |
| INT default_custom_paper_xfeed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.12 | INTEGER | read-write | Sets the printer's default custom paper size dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. Additional information: Sets the printer's default custom paper size dimension in the cross-feed direction (direction ninety degrees relative to the direction of paper feeding). The value for this object is specified in micrometers or tenthousandths of an inch, depending upon the value of DEFAULT-CUSTOM-PAPER-DIM-UNIT. The valid range is engine-dependent and should be documented in the POS for each product. |
| INT default_horizontal_black_resolution | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.9 | INTEGER | read-write | Returns or changes the value of the default horizontal black resolution. The units are dots per inch. Additional information: In InkJet changing this object also causes DEFAULT-VERTICAL-BLACK RESOLUTION to change. DEFAULT-HORIZONTAL-BLACK-RESOLUTION and DEFAULT-VERTICAL-BLACK-RESOLUTION must always be the same. The supported values are: Grizzly: 300, 600, 1200 Color Products: 600 Cayenne: 300, 600 Setting to an unsupported value causes the printer to substitute in a snap value and to return status. The snap values are as follow: Grizzly: n = n = 900 snaps to 1200 Color Products: n snaps to 600 Cayenne: n =450 snaps to 600 |
| INT default_lines_per_page | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.11 | INTEGER | read-write | Returns or changes the default number of lines per page. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return the . Additional information: The supported values in InkJet are 5 to 128. Setting to an unsupported value causes the the printer to substitute in a snap value and to return status. The snap values are as follow: 128 snaps to 128 |
| OCT default_media_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.22 | OCTET STRING | read-write | Returns or sets the media name that is used until the media name is changed by a print job command. Additional information: Returns or sets the media name that is used until the media name is changed by a print job command. This string must be one of the MEDIAn-NAME objects. This object is localized if the corresponding MEDIAn-NAME object is localized. The data for this object is stored in NVRAM. |
| INT default_media_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.13 | INTEGER | read-write | This indicates the default media size. A write of an unsupported value causes an . Complete list of supported media sizes along with their dimensions are listed in the ''Media Size Table'' near the end of this document. (for a full list of media size enums see the end of this file) |
| INT default_page_protect | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.10 | INTEGER | read-write | Returns or changes the default page protection behavior. If eOff, the device does not reserve memory for holding the entire raster form of a processed page. If eOn, then memory is reserved. If eAuto, the device determines the amount of memory to reserve. Additional information: Setting to eOn causes MET to be more conservative, but it will not allocate memory to hold an entire rasterized page. |
| INT default_vertical_black_resolution | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.8 | INTEGER | read-write | Returns or changes the value of the default vertical black resolution. The units are dots per inch. Additional information: In InkJet changing this OID also causes DEFAULT-HORIZONTAL-BLACK RESOLUTION to change. DEFAULT-HORIZONTAL-BLACK-RESOLUTION and DEFAULT-VERTICAL-BLACK-RESOLUTION must always be the same. The supported values are: Grizzly: 300, 600, 1200 Color Products: 600 Cayenne: 300, 600 Setting to an unsupported value causes the printer to substitute in a snap value and to return status. The snap values are as follow: Grizzly: 450 >= n = 900 snaps to 1200 Color Products: n snaps to 600 Cayenne: n =450 snaps to 600 |
| INT default_vmi | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.12 | INTEGER | read-write | Returns or changes the default vertical motion index. The unit of measure for VMI is centipoints per line. The POS indicates the supported values. An unsupported value causes the printer to use the closest supported value, causing the printer to return . |
| destination_bin_accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.6 | |||
| destination_bin_usage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.6.1 | |||
| INT destination_bin_usage_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.6.1.1 | INTEGER | read-only | Total number of pages printed to this destination bin. Additional information: This object will track how many images have been printed with the original destination bin as one of the following: 1. Face Down Bin 2. Face Up Bin 3. Bin 1 4. Bin 2 5. Bin 3 6. Bin 4 7. Bin 5 8. Other |
| INT destination_bin_usage_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.11 | INTEGER | read-only | This object reports the total destination bin usage for the life of the printer. This value is reported on the usage page. |
| destination_subsystem | 1.3.6.1.4.1.11.2.3.9.4.2.1.4 | |||
| device | 1.3.6.1.4.1.11.2.3.9.4.2.1 | |||
| device_configure | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.32 | |||
| OCT device_configure_printer_parameters | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.32.12 | OCTET STRING | read-write | Allow the printer to be configured as a duplex or simplex printer. There will be a > encoded in this string and decoded by the printer firmware. If the > check passes the printer will be configured accordingly. Additional information: Used to configure engines for duplex enabled or not. Encoded configuration string is passed in, which is decoded by firmware. Firmware verifies config. string is valid, and retrieves device Configuration data. Expandable to accommodate future products configuration needs. |
| OCT device_location | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.11 | OCTET STRING | read-write | 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 .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 status. |
| OCT device_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.10 | OCTET STRING | read-write | User defined device name. 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 .Additional information: The maximum supported string length is 32 characters. If the user entered string is too long, the device will store the first 32 characters and will return the status. |
| device_system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1 | |||
| INT direct_connect_ports_enable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.43 | INTEGER | read-write | This object specifies whether all direct connect ports (parallel and USB) are available or ignored. JetDirect, embedded network connectivity, and third party add-on cards (such as Firewire) will be unaffected by setting this object. |
| display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.20 | |||
| INT display_long_grain_optimization_warning | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.84 | INTEGER | read-write | Display or DoNotDisplay the warning message on control panel of long grain optimiation. Additional information: nothing beyond old description |
| display_status | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.20.1 | |||
| dm | 1.3.6.1.4.1.11.2.3.9.4.2 | |||
| INT duplex_blank_pages | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.28 | INTEGER | read-write | When the value of the system variable is set to eDuplexBlankPagesAuto, it means to Smart Duplex in any of the specified conditions. This selection is logically equivalent to 'NO, do not duplex blank pages if not duplexing them obtains a performance enhancement'. When the value of the system variable is set to eDuplexBlankPagesYes, it means to disable Smart Duplexing. Additional information: When the value of the system variable is set to eDuplexBlankPagesAuto, it means to Smart Duplex in any of the specified conditions. This selection is logically equivalent to 'NO, do not duplex blank pages if not duplexing them obtains a performance enhancement'. When the value of the system variable is set to eDuplexBlankPagesYes, it means to disable Smart Duplexing. This PML object setting is only valid when the job has not requested a source tray. If the source tray has not been requested and setting is YES, then we disable smart duplexing. If the source tray has not been requested and setting is AUTO, then we do smart duplexing in some cases |
| INT duplex_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.22 | INTEGER | read-only | Total number of sheets of media that have been duplex printed. A sheet is counted if it travels through the duplex page path, regardless of whether or not marks are made on the page. The POS will indicate if the value is kept in NVRAM. Additional information: Total number of sheets of media that have been duplex printed. A sheet is counted if it travels through the duplex page path, regardless of whether or not marks are made on the page. This value is kept in NVRAM however the NVRAM value is only updated every 10 sheets. NOTE: The value returned by this object will be incremented every sheet but if power is lost between NVRAM updates up to 9 sheets of the count may be lost. The counter will be reset to zero after 16,777,215 (2^24-1) pages. |
| INT email_service_operational | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.111 | INTEGER | read-only | To check if Email service is operational on the device. Email is operational if email feature is enabled on the device and the SMTP gateway is configured. |
| INT energy_star | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.1 | INTEGER | read-write | Returns or changes the Energy Star sleep value. If the value is greater than zero, then the device will go into energy saving sleep mode after the print engine has been idle for the number of seconds specified by this object. A value of zero means Energy Star is disabled and the device will not go to sleep based on print engine idle time. The value must be non-negative. Additional information: Returns or changes the Energy Star sleep value. The device will go into energy saving sleep mode after the print engine has been idle for the number of seconds specified by this object. InkJet supports values of 0, 60, 900, 1800, 3600, 5400, 7200, 14400 seconds. A value of 0 means never enter sleep mode based on the print engine idle time. Setting to an unsupported value causes the printer to substitute a value (listed below) and to return status. Setting this value when the printer is in sleep mode will not cause it to wakeup unless it is set to 0. The values are as follow: =1 and =480 and =1350 and =2250 and =3150 and =4500 and =2700 and =5400 and =10800 snap to 14400 (4 hours). |
| INT error_log_clear | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.38 | INTEGER | write-only | 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. |
| error1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.1 | |||
| INT error1_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.1.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: Returns a device specific error code. If the error code returned is '0', then the printer has not yet logged an error for this object. When the maximum number of errors is reached (30 on InkJet printers), and a new error occurs, the error in ERROR1-CODE will be replaced by the one in ERROR2-CODE, and so on until the last error object will be given the value of the new error. The error number is returned in the upper 16 bits. If it is 68, 69, 79, or 80, then the sub code is returned in the lower 16 bits (eg. 68 001C, where the subcode is already a hexadecimal value). If the error number is any other number, then the 1st sub code (XX) will be in bits 15-8 and the 2nd sub code (YY) will be in bits 7-0 (eg. 55.04.02) where XX=04 and YY=02). See the Control Panel ERS for specific information about the meaning of each code. Example: If the error is 68 001A, then the value returned will be 4456474. To break it down: 4456474 = 0x0044001A The upper 16 bits: 0x0044 = 68 The lower 16 bits: 0x001A = 001A Which is the error: 68 001A Example: If the error is 55.04.241, then the error code will be 3605745. To break it down: 3605745 = 0x003704F1 The upper 16 bits: 0x0037 = 55 The upper byte of the lower 16 bits: 0x04 = 04 The lower byte of the lower 16 bits: 0xF1 = 241 Which is the error: 55.04.241 |
| OCT error1_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.1.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: This item contains the date and the time when the error occurred. It returns the date and the time at which the error occured in hexadecimal. For instance, if date is 2004-Jul-13 and time is 03:15 am when the error was logged, then we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month 07 0d(hex) - corresponds to date 13 03(hex) - corresponds to hour- 03 0f(hex) - corresponds to min- 15. If there is currently no error entry , '00 00 00 00 00' will be returned. See ERROR1-CODE for an explanation of the order used for storing errors. |
| INT error1_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.1.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 1 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: This item contains the engine page count when the error occurred. If there is currently no error entry for this object, a '0' will be returned. Note that '0' may also be returned when there is a valid error, but a current page count was unavailable. If ERROR1-CODE object also returns '0', then an error has not yet been logged for this object. See ERROR1-CODE for an explanation of the order used for storing errors. |
| error10 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.10 | |||
| INT error10_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.10.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error10_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.10.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error10_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.10.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 10 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error11 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.11 | |||
| INT error11_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.11.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error11_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.11.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error11_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.11.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 11 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error12 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.12 | |||
| INT error12_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.12.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error12_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.12.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error12_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.12.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 12 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error13 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.13 | |||
| INT error13_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.13.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error13_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.13.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error13_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.13.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 13 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error14 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.14 | |||
| INT error14_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.14.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error14_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.14.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error14_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.14.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 14 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error15 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.15 | |||
| INT error15_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.15.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error15_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.15.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error15_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.15.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 15 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error16 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.16 | |||
| INT error16_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.16.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error16_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.16.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error16_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.16.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 16 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error17 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.17 | |||
| INT error17_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.17.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error17_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.17.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error17_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.17.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 17 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error18 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.18 | |||
| INT error18_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.18.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error18_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.18.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error18_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.18.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 18 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error19 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.19 | |||
| INT error19_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.19.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error19_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.19.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error19_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.19.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 19 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.2 | |||
| INT error2_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.2.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error2_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.2.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error2_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.2.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 2 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error20 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.20 | |||
| INT error20_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.20.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error20_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.20.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error20_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.20.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 20 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error21 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.21 | |||
| INT error21_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.21.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error21_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.21.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error21_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.21.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 21 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error22 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.22 | |||
| INT error22_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.22.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error22_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.22.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error22_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.22.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 22 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error23 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.23 | |||
| INT error23_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.23.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error23_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.23.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error23_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.23.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 23 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error24 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.24 | |||
| INT error24_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.24.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error24_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.24.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error24_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.24.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 24 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error25 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.25 | |||
| INT error25_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.25.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error25_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.25.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error25_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.25.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 25 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error26 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.26 | |||
| INT error26_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.26.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error26_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.26.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error26_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.26.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 26 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error27 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.27 | |||
| INT error27_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.27.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error27_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.27.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error27_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.27.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 27 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error28 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.28 | |||
| INT error28_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.28.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error28_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.28.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error28_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.28.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 28 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error29 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.29 | |||
| INT error29_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.29.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error29_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.29.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error29_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.29.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 29 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.3 | |||
| INT error3_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.3.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error3_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.3.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error3_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.3.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 3 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error30 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.30 | |||
| INT error30_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.30.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error30_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.30.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error30_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.30.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 30 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error31 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.31 | |||
| INT error31_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.31.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error31_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.31.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error31_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.31.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 31 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error32 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.32 | |||
| INT error32_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.32.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error32_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.32.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error32_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.32.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 32 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error33 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.33 | |||
| INT error33_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.33.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error33_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.33.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error33_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.33.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 33 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error34 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.34 | |||
| INT error34_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.34.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error34_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.34.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error34_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.34.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 34 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error35 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.35 | |||
| INT error35_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.35.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error35_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.35.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error35_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.35.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 35 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error36 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.36 | |||
| INT error36_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.36.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error36_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.36.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error36_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.36.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 36 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error37 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.37 | |||
| INT error37_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.37.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error37_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.37.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error37_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.37.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 37 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error38 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.38 | |||
| INT error38_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.38.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error38_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.38.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error38_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.38.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 38 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error39 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.39 | |||
| INT error39_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.39.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error39_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.39.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error39_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.39.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 39 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.4 | |||
| INT error4_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.4.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error4_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.4.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error4_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.4.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 4 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error40 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.40 | |||
| INT error40_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.40.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error40_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.40.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error40_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.40.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 40 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error41 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.41 | |||
| INT error41_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.41.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error41_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.41.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error41_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.41.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 41 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error42 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.42 | |||
| INT error42_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.42.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error42_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.42.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error42_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.42.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 42 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error43 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.43 | |||
| INT error43_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.43.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error43_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.43.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error43_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.43.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 43 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error44 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.44 | |||
| INT error44_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.44.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error44_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.44.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error44_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.44.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 44 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error45 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.45 | |||
| INT error45_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.45.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error45_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.45.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error45_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.45.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 45 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error46 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.46 | |||
| INT error46_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.46.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error46_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.46.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error46_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.46.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 46 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error47 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.47 | |||
| INT error47_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.47.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error47_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.47.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error47_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.47.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 47 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error48 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.48 | |||
| INT error48_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.48.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error48_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.48.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error48_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.48.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 48 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error49 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.49 | |||
| INT error49_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.49.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error49_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.49.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error49_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.49.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 49 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.5 | |||
| INT error5_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.5.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error5_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.5.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error5_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.5.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 5 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error50 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.50 | |||
| INT error50_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.50.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error50_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.50.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error50_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.50.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 50 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.6 | |||
| INT error6_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.6.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error6_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.6.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error6_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.6.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 6 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error7 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.7 | |||
| INT error7_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.7.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error7_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.7.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error7_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.7.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 7 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error8 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.8 | |||
| INT error8_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.8.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error8_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.8.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error8_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.8.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 8 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| error9 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.9 | |||
| INT error9_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.9.2 | INTEGER | read-only | Contains a device specific error code. Each device POS should list what errors are logged to the error log and the meaning of each supported error code value. Additional information: See ERROR1-CODE. |
| OCT error9_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.9.3 | OCTET STRING | read-only | This item contains the date and the time at which an error occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See ERROR1-DATE-TIME. |
| INT error9_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11.9.1 | INTEGER | read-only | Contains some sort of time stamp indicating when error 9 occurred. Example time stamps include the actual time the error occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See ERROR1-TIME-STAMP. |
| errorlog | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.11 | |||
| INT ews_request_control_panel_supplies_status | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.6.1.5 | INTEGER | read-write | System variable EWS_REQUEST_CONTROL_PANEL_SUPPPLIES_STATUS requires a PML interface so that WJA can directly access it without needing EWS support for that. Additional information: If this object is set to eEnable, the Supplies Status messages will not be shown on the CP. |
| INT factory_reset | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.68 | INTEGER | write-only | writing an integer 0 will do factory reset on system variables, MFP Settings and the .NET database without a reboot. Additional information: nothing beyond old description |
| OCT fax_billing_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.2.18 | OCTET STRING | read-only | The actual Billing Code applicable for Faxes sent from the device |
| INT fax_billing_code_enabled | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.2.16 | INTEGER | read-only | To check if Billing Code is enabled on the device for Faxes sent |
| INT fax_billing_code_minlength | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.2.17 | INTEGER | read-only | The Minimum number of Billing Code digits that has to be specified for Faxes sent from the device. Range: 1 - 16 |
| INT fax_job_scan_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.90 | INTEGER | read-only | The number of fax scan jobs. Additional information: The number of fax scan jobs. |
| INT fax_notification_available | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.2.15 | INTEGER | read-only | To check if the embedded Fax accessory or the Fax Service available on the device supports Notification for Faxes Sent |
| INT fax_print_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.1.32 | INTEGER | read-only | This object tracks the page count for the pages sent to the print engine for fax jobs. In order to write this object > must be set correctly. Additional information: Returns the number of fax pages printed. |
| fax_proc_sub | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7 | |||
| INT fih_extra_pulses_feature | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.8.2 | INTEGER | read-write | This object allows one to get/set the setting of the FIH EXTRA PULSES FEATURE item. This either turns the feature on or off based on customer requirement. |
| file_system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10 | |||
| OCT file_system_delete_files | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.8 | OCTET STRING | write-only | Setting this object causes the specified filename to be deleted, after first validating that the authentication data is correct for the specified user ID. The format for this object is a C structure: typedef struct { sint32 UserId; uint16 AuthenticationDataLen ubyte AuthenticationData[] char Filename[]; } fs_delete_files_t; which is described below: Bytes 0 - 3: contains a user id represented as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 4 - 5 : Length of the Athentication data that follows starting at offset 6. Stored as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 6 - 6+AuthenticationDataLen : a ubyte array containing the Authentication data used to verify access for this operation. Bytes starting at offset (6+AuthenticationDataLen+1): A null terminated character array representing the ASCII file name to be deleted. The length of the string will be limited by the remaining space in the object. This string represents a fully-qualified path name which may specify a filename or a regular expression that may match multiple files (e.g /*.exe). Access to this command is controlled by the UserId and the authentication data. If the UserID or authentication data supplied is incorrect the command will fail. The device POS will specify any limitations to the length of the filename string, what constitutes a correct user ID, what constitutes correct authentication data, and the significance of any return values. Additional information: Setting this object causes the specified filename to be deleted, after first validating that the authentication data is correct for the specified user ID. This object is always present. The format for this object is a C structure: typedef struct { sint32 UserId; uint16 AuthenticationDataLen ubyte AuthenticationData[] char Filename[]; } fs_delete_files_t; Bytes 0 - 3: contains a user id represented as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 4 - 5 : Length of the authentication data that follows starting at offset 6. Stored as a multi-byte value that is stored in big-endian format, where the most significant byte occurs first. Bytes 6 - 6+AuthenticationDataLen : a ubyte array containing the authentication data used to verify access for this operation. Bytes starting at offset (6+AuthenticationDataLen+1): A null terminated character array representing the ASCII file name to be deleted. The length of the string will be limited by the remaining space in the object. This string represents a fully-qualified path name which may specify a filename or a file-type regular expression that may match multiple files (e.g., /*.exe). Access to this command is controlled by the UserId and the authentication data. If the UserID or authentication data supplied is incorrect the command will fail. The device POS will specify any limitations to the length of the filename string, what constitutes a correct user ID, what constitutes correct authentication data, and the significance of any return values. |
| OCT file_system_erase_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.11 | OCTET STRING | read-write | This object is used to control how file data is handled when files are deleted. It is always readable. It is writable when > is the empty string or when a write to > with the current > has preceeded the write to the object. When > is not the empty string then this object becomes read-only after a successful write to it. > must then be written to again with the current > in order to make another write operation on the object possible. If the > is incorrectly set, this object becomes read-only until the > is correctly set. The logical settings for this object are: NonSecureFastErase - When a file is deleted, only the reference to it in the file system tables is removed. No file data is overwritten. This is the default setting. This is the setting when both bits in the collection are set to 0. SecureFastErase - File information is overwritten with identical, random character pattern when it is deleted. This is the setting when cEraseMode0 is set to 1 and cEraseMode1 is set to 0. SecureSanitizeErase - Secure, repetitive algorithm used to overwrite all deleted file information and remove any residual data persistence. A random character is written to all bytes of deleted sectors. Then the complement of that character and finally, another random character is written. This is the setting when cEraseMode0 is set to 0 and cEraseMode1 is set to 1. Note that an error will be returned for an attempt to set both bits of the collection to 1. |
| OCT file_system_external_access_capabilities | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.10 | OCTET STRING | read-write | This object is used to control access to the file system of the device. It is always readable. It is writable when > is not the empty string, and a successful write to that object with the current > has preceded the write to this object. In other words, the > must be in the 'authenticated state' for a write on FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES to succeed. After the object has successfully been written to, it becomes read-only, and the > object exits the authenticated state. > must then be written to again with the current > in order to make another write operation on FILE-SYSTEM-EXTERNAL-ACCESS-CAPABILITIES possible. cDisablePJLFileSystemAccess - All file system access through PJL will be disabled. cDisablePMLFileSystemWrite - All file-systems-related PML objects such as FILE-SYSTEM-DELETE-FILES or hrPartitionLabel become read-only. For objects that are normally write-only this means that no successful operations can now be performed on them. cDisableNFSFileSystemAccess - All NFS file system access will be disabled. cDisablePSFileSystemAccess - All file system access through PostScript will be disabled. cDisableEWSFileSystemAccess - All access to the file system by the Embedded Web Server will be disabled. |
| INT file_system_max_open_files | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.2 | INTEGER | read-only | The number of open files allowed at one time. Opening a file when the maximum number of files are currently open will fail. Additional information: Indicates the number of open files a personality (e.g. PCL or PostScript) is guaranteed to be able to open before the file system runs out of file handles. This object is between 1 and 500. Returns status if attempting to access this object and there is no storage device is installed. |
| INT file_system_set_system_partition_readonly | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.7 | INTEGER | write-only | Changes a system partition to be READ-ONLY. The value is the volume number to change. If the volume number specified is NOT a system partition an error is returned. Additional information: Returns status if attempting to access this object and there is no storage device is installed. Returns if the volume requested is not present. |
| OCT file_system_set_system_partition_writeable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.6 | OCTET STRING | write-only | This object allows the system partition to be written to. It consists of a C structure containing the following fields: typedef struct { ubyte >[8]; ubyte volumenumber; } fs_writeable_system_partition_t; which is described below: Bytes 0 - 7: contain the > Byte 8 : is the volume number Access to this command is controlled by the >. If the > supplied is incorrect the command will fail. The volumenumber is a volume number of an existing system partition. Additional information: Returns status if attempting to access this object and there is no storage device is installed. Returns if the > is incorrect or if the volume requested is not present. |
| INT file_system_wipe_disk | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.12 | INTEGER | read-write | This object is a non-leaf node which will have one leaf node under it for each file system in the printer. The leaf nodes will be in a 1-to-1 correspondence with the hrDeviceIndex objects. This object specifies for each leaf node whether the file system on the device is going to be erased according to the setting of the FILE-SYSTEM-ERASE-MODE referenced by the corresponding hrDeviceIndex. A file system will be overwritten on system reboot if this object is set to 1. It will be unchanged if this object is set to 0. If this object's value is -1 then the file system cannot be wiped. If the file system contains the permstore, the permstore will be saved off and restored after the file-system wipe is completed. This object is always readable. It is writable when > is the empty string or when a write to > with the current > has preceeded the write to the object. When > is not the empty string then this object becomes read-only after a successful write to it. > must then be written to again with the current > in order to make another write operation on the object possible. If the > is incorrectly set, this object becomes read-only until the > is correctly set. |
| INT file_system_wipe_disk_status | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1.13 | INTEGER | read-only | This object is a non-leaf node which will have one leaf node under it for each file system in the printer. The leaf nodes will be in a 1-to-1 correspondence with the hrDeviceIndex objects. This object specifies for each leaf node the status of a disk wipe in progress. A return value of -1 indicates that no disk wipe is in progress. A return value in the range of 0 to 100 indicates the percent done for a disk wipe in progress. All other values are illegal. |
| file_system2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.2 | |||
| INT file_system2_initialize_volume | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.2.6 | INTEGER | write-only | Setting this object to eInitializing causes file system 2 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 physical mass storage device, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM2-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 1st device. |
| file_system3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.3 | |||
| INT file_system3_initialize_volume | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.3.6 | INTEGER | write-only | Setting this object to eInitializing causes file system 3 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 physical mass storage device, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM3-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 2nd device. |
| file_system4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.4 | |||
| INT file_system4_initialize_volume | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3.4.6 | INTEGER | write-only | Setting this object to eInitializing causes file system 4 to be initialized. Reading this object indicates if the file system is currently being initialized. Additional information: The hrDeviceIndex value for the mass storage device is the same value that is used to index into the FILE-SYSTEM sub-tree. Since this product supports up to 3 physical mass storage devices, and since the hrDeviceIndex for the mass storage devices will start at 2 if the mass storage device is installed, the FILE-SYSTEM4-INITIALIZE-VOLUME object will be the object that allows the mass storage device to be initialized that is the 3rd device. |
| file_systems | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.3 | |||
| OCT finisher_image_rotation | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.31 | OCTET STRING | read-write | This PML object will provide the additional image rotation that is applied to a printed job depending on the presence or absence of a finisher device or the value of the SVM_ALWAYS_MATCH_OUTPUT_ORIENTATION variable. Additional information: This PML object will provide the additional image rotation that is applied to a printed job depending on the presence or absence of a finisher device and/or the state of the IMAGE ROTATION menu element. |
| firmware_download | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18 | |||
| INT firmware_download_current_state | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.4 | INTEGER | read-write | Provides the current or last reportable state of the firmware download process. The current state may not necessarily be the current state, but could be the post-mortem state. |
| INT firmware_download_maximum_write_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.5 | INTEGER | read-only | Reports the manufacturer specified number of times that firmware can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that firmware can be downloaded to the flash part. Additional information: Reports the manufacturer specified number of times that firmware can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that firmware can be downloaded to the flash part. The current maximum write count is 500. This may change as flash technology evolves. |
| OCT firmware_download_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.6 | OCTET STRING | read-only | This returns the name of the printer. This should match the name in the header of the upgrade image being sent to the flash part. If the name does not match with the name returned then the image that we are attempting to download does not upgrade the printer firmware. Additional information: This object returns the HP name of the printer. This should match what is in the PJL header of the RFU job Web Jet Admin uses this to ensure the printer is available to be upgraded. |
| OCT firmware_download_version | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.7 | OCTET STRING | read-only | This object will return a string value representing the current revision of firmware that the printer is operating with. This is used to determine if code needs to be upgraded when an firmware bundle comes in, in an upgrade job. Additional information: Web Jet Admin uses the version string that is returned to determine what peices of an RFU bundle need to be upgraded when an RFU job is being built. This objects will return the version string of the printer. |
| INT firmware_download_write_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.3 | INTEGER | read-only | Tells the number of times that firmware has been downloaded to the flash part. Additional information: Tells the number of times that firmware has been downloaded to the flash part. The default value will vary depending on how many times the firmware is rolled before shipping. |
| INT firmware_download_write_status_supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.1 | INTEGER | read-only | This object provides information on whether the printer has the ability to communicate the write-status of the firmware download while the download is taking place. |
| INT firmware_download_write_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.18.2 | INTEGER | read-only | If the design of the firmware-download implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the printer will not be able to engage in PML communication. Additional information: If the design of the firmware-download implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the printer will not be able to engage in PML communication. The calculated time is expected to be 140 secs. However, this time may increase as high as 280 secs as the flash part nears the maximum flash count. |
| foreign_interface | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.8 | |||
| INT form_feed | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.5 | INTEGER | write-only | Instructs the PDL processing sub-system to finishing processing the current page of the current job. Form feed is also known as close page or eject page. If the PDL processing sub-system is in a FORM-FEED-NEEDED state, this causes the device to flush or finish processing the current page of the current job. If the device is not in the FORM-FEED-NEEDED state, an will occur. |
| INT form_feed_needed | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.2.2 | INTEGER | read-only | Indicates if the PDL processing sub-system has made marks on the current page and the source subsystem has been idle for a device specific amount of time. Additional information: InkJet will set this object to eTrue when it has made marks on the current page, the IO-TIMEOUT has expired while PCL was running in `backward-compatibility mode' (which is caused by jobs consisting purely of PCL data with no prepended PJL commands), and no data is pending on another I/O. Once it is set to eTrue, more data on the same I/O will cause this object to be set to eFalse, until the above conditions are met again. |
| OCT formatter_serial_number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.20 | OCTET STRING | read-only | This object returns the formatter serial number for the device. The value returned from this object is the FORMATTERNUMBER system variable. 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: Returns the formatter serial number, prefixed with the PML_UNICODE_PREFIX.. |
| OCT fw_rom_datecode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.5 | OCTET STRING | read-only | 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. |
| OCT fw_rom_revision | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.6 | OCTET STRING | read-only | This identifies the system code firmware ROM revision code. The format for a revision is major_revision.minor_revision. There may be other ROM revision code objects for other specific ROMs such as font ROMs, localization ROMs, etc; these other ROM revision code objects are device specific. |
| held_job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7 | |||
| held_job_control | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2 | |||
| INT held_job_delete | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.2 | INTEGER | write-only | Instructs the printer to delete the specified held job from the list. The job-id is used to identify which job to delete. A held job can also be deleted from the control panel. Additional information: Setting this to a value that is not a Held Job on the system or is a Private Held Job returns . To delete a private Held Job, you must use the PML object HELD-JOB-PRINT with a quantity of 0 and supply the correct HELD-JOB-PIN with the request. (See HELD-JOB-PRINT) |
| INT held_job_enable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.4 | INTEGER | read-write | Enables or disables Job Retention (Job Hold). The valid values are eDisabled and eEnabled. (Specifying an invalid mode causes an error to be returned.) When eDisabled is specified all Job Retention (Hold, Proof, Store, PIN Printing) is disabled. When eEnabled is specified, the Job Retention characteristics of a given job are defined by the PJL variable SET HOLD. Additional information: When disabled, held jobs are not removed, but must be explicitly removed through the Control Panel or the PML object HELD-JOB-DELETE. |
| held_job_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1 | |||
| OCT held_job_job_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.2 | OCTET STRING | read-only | The job name may be generated by the driver or obtained from user input. |
| OCT held_job_pin | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.6 | OCTET STRING | read-only | A string that is specified in the job stream and then required to be entered in order to release the job for printing. PIN stands for Personal Identification Number. Additional information: Must be a 4 digit string, each digit must be 0..9 or a null string if there is no pin. For security purposes, you can no longer get the value of the PIN. |
| OCT held_job_print | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.1 | OCTET STRING | write-only | Instructs the printer to schedule the specified held job for printing with the specified number of copies. The job-id is used to identify which job to print. A held job can also be printed from the control panel. Additional information: Bytes 0-3 is the job id of the job to print. Bytes 4-7 is the number of copies to print. Bytes 8-11 (optional) contain the PIN for a Private job. |
| INT held_job_quantity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.5 | INTEGER | read-only | Number of copies to print. |
| INT held_job_retention | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.3 | INTEGER | read-only | Indicates the retention classification of the job. The values indicate whether the job is printed immediately or stored. There are 4 options: eHoldOff: The job is printed but not retained on the disk. eHoldOn: The job is printed and stored temporarily on the disk. eHoldStore: The job is not printed but stored on the disk. eHoldProof: One copy of the job is printed and the remaining copies are stored on the disk. |
| INT held_job_security | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.4 | INTEGER | read-only | The variable specifies the security level of the job. eHoldTypePublic: The job does not require a PIN in order to release the job for printing. eHoldTypePrivate: The job requires a PIN in order to be released for printing. |
| INT held_job_set_queue_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.2.3 | INTEGER | read-only | Sets the maximum number of jobs which can be stored in the held job list. Additional information: Sets the size of the temporary job lists queue. |
| OCT held_job_user_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.7.1.1 | OCTET STRING | read-only | User name that is obtained by the driver through some internal method or from user input. Additional information: The following is a general description for all the JOB-MANAGEMENT objects described below. These object describe the attributes of the dynamic list containing all the stored jobs on the disk available for printing or deleting via the job-management feature. The jobs on this list are not deleted from the disk unless explicitly specified by the user. A print job may be specified for retention by PJL commands in the data stream. Following is a list of the PJL commands (i.e. these comments describe the PJL implementation and in some cases do not reflect the PML implementation.): @PJL SET HOLD=OFF|ON|PROOF|STORE|PRINT GENERAL DESCRIPTION: This variable specifies the retention classification of the job. The values indicate whether the job is printed immediately and/or stored. OFF: The job is printed but not retained on disk after printing. This is the default value. ON: This setting may be thought of as free proof-and-hold. The requested number of copies will be printed and the job will be temporarily stored on disk. The job will then be available for printing additional copies through the control panel and through PML. There will be a limit to the number of these temporary jobs that may be stored, and when the limit is exceeded the oldest job will be removed from the disk. PROOF: One copy of the job is printed and remaining copies are stored on disk. The job is then available to select for printing via the control panel menus or PML. The job will be deleted from the disk when the disk space is needed for another proof and hold job but only after the additional copies have been printed. It will also be deleted when the user sends down another proof and hold job with the same job name, or the user explicitly deletes the job. STORE: The job is not printed immediately but is retained on disk. The job is available to select for printing via the control panel DEFAULT VALUE: OFF The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET USERNAME= GENERAL DESCRIPTION: Eighty-character user name that is obtained by the driver through some internal method or from user input. If the job stream does not contain a USERNAME the default value will be NO USER NAME. The driver is responsible for determining the size of the printers control panel and sending a string of appropriate length. DEFAULT VALUE: NO USER NAME The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and, INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET JOBNAME= GENERAL DESCRIPTION: Eighty-character job name that may be generated by the driver or obtained from user input. This value may be used in conjunction with the USERNAME to select a job from the front panel. If the job stream does not contain a JOBNAME, the printer will assume no job name; each subsequent job that is sent down by the same user would replace the users last job on disk. The driver is responsible for determining the size of the printers control panel and sending a string of appropriate length. NOTE: The limit of 80 bytes is a PJL limit. The limit for PML will be 40 bytes. DEFAULT VALUE: NULL STRING The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET HOLDTYPE=PUBLIC|PRIVATE GENERAL DESCRIPTION: This variable specifies the privacy level of the job. PUBLIC: The job does not require a PIN in order to be released for printing. This is the default value. PRIVATE: The job requires a PIN in order to be released for printing. The PIN is specified by the HOLDKEY variable. If the HOLDTYPE is set to PRIVATE, a HOLDKEY value must be specified. If no HOLDKEY is specified, the job will be considered PUBLIC. DEFAULT VALUE: PUBLIC The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. @PJL SET HOLDKEY=4 digits, 0000...9999 GENERAL DESCRIPTION: A 4-digit string, each digit 0-9, that is specified in the job stream and then required to be entered in order to release the job for printing. If a HOLDTYPE is PRIVATE, a HOLDKEY value must be specified. If no HOLDKEY value is specified, a job will be considered PUBLIC. DEFAULT VALUE: NULL STRING The value will be stored in RAM only, not in NVRAM. The legal PJL commands are SET and INQUIRE. DEFAULT is not allowed. The variable will appear in the PJL INFO VARIABLES list. The format for the OID is as follows: 3.4.1.6.x.y | | | | \ / | job-id in the system / \ PML_JOB_MGNT_ROOT_OID \ job attribute 1..6 x values are 1..6: 1) user-name: user name that is obtained by the driver through some internal method or from user input. 2) job-name: job name may be generated by the driver or obtained from user input. 3) hold: indicates the retention classification of the job. The values indicate whether the job is printed immediately and/or stored. There are 4 options: OFF: The job is printed but not retained on the disk. ON: The job is printed and stored temporarily on the disk. STORE: The job is not printed but stored on the disk. PROOF: One copy of the job is printed and the remaining copies are stored on the disk. 4) holdtype: The variable specifies the security level of the job. PUBLIC: The job does not require a PIN in order to release the job for printing. PRIVATE: The job requires a PIN in order to be released for printing. 5) quantity: number of copies to print. Valid values are 0..999. 6) pin: A 4 digit string, each digit is 0-9, that is specified in the job stream and then required to be entered in order to release the job for printing. y : an unsigned 32-bit number which uniquely identifies the job. The job id for the job remains the same for the job until it is deleted from the held jobs list. For example, the OID below is asking for the user name of the job whose id is 3. The application would issue: OID get 3.4.1.6.1.3 For example, the OID values sequence is as follows: OID returned OID getnext 3.4.1.6 3.4.1.6.1.1 getnext 3.4.1.6.1.1 3.4.1.6.1.2 getnext 3.4.1.6.2.1 3.4.1.6.2.2 *** getnext 3.4.1.6.1.6 3.4.1.6.1.7 getnext 3.4.1.6.2.1 3.4.1.6.2.2 getnext 3.4.1.6.5.2828 3.4.1.6.6.1 NOTE: for example above, job id 2828 is the last job in the list of held jobs. *** Also supported is on the job attributes: OID returned OID getnext 3.4.1.6.1 3.4.1.6.1.1 getnext 3.4.1.6.6 3.4.1.6.6.1 |
| INT hold_job_timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.10 | INTEGER | read-write | The time, in minutes, that the printer will wait before automatically deleting a held job. This allows the printer to automatically clean up jobs that have been forgotten (held but never released). Additional information: This only applies to temporary held jobs, i.e., HOLD=ON or PROOF. This is a global timer that only affects the jobs that are sent after it is set. A value of 0 means never delete the jobs. Setting it to an unsupported value causes the printer to substitute a value (listed below) and to return status. Smokey supports values of 0, 60, 240, 1440, and 10080 The values are as follows: =1 and =151 and =841 and =2881 snap to 10080 (1 week) |
| INT host_application_available_memory | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.59 | INTEGER | read-only | Returns the amount of memory, in bytes, that the device has available for job-related processing or resources. Also known as driver work space (DWS) memory. |
| hp | 1.3.6.1.4.1.11 | |||
| id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3 | |||
| imaging | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.6 | |||
| INT input_tray_auto_select | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.2 | INTEGER | read-write | Indicates if the device will automatically try to load media from the next input media tray in the auto-select sequence (defined by each device) when it cannot load media from the current tray. Locked trays will not be permitted in the auto-select sequence. This object has no meaning if there is only one unlocked input media tray. Additional information: Indicates if the device will automatically try to load media from the next input media tray in the auto-select sequence (defined by each device) when it cannot load media from the current tray. Locked trays will not be permitted in the auto-select sequence. This object has no meaning if there is only one unlocked input media tray. |
| INT input_tray_max_media_feed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.14 | INTEGER | read-only | The maximum physical media size in the feed direction of this input device expressed in units of measure specified by INPUT- TRAY-MIN-MAX-DIM-UNIT. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Additional information: The maximum physical media size in the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB. |
| INT input_tray_max_media_xfeed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.15 | INTEGER | read-only | The maximum physical media size across the feed direction of a particular input device expressed in units of measure specified by INPUT-TRAY-MIN-MAX-DIM-UNIT. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Additional information: The maximum physical media size across the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, f or more details in the original format of the Standard Printer MIB. |
| INT input_tray_min_media_feed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.16 | INTEGER | read-only | The minimum physical media size in the feed direction of a particular input device expressed in units of measure specified by PrtInputMinMaxDimUnit. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Additional information: The minimum physical media size in the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB. |
| INT input_tray_min_media_xfeed_dim | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.17 | INTEGER | read-only | The minimum physical media size across the feed direction of a particular input device expressed in units of measure specified by PrtInputMinMaxDimUnit. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Additional information: The minimum physical media size across the feed direction of this input device expressed in units of measure specified by PrtInputDimUnit. A value of (-1) implies 'unlimited', a value of (-2) implies 'unknown'. Refer to Printer Management Standards web page, http://bldlabs.boi.hp.com/BLDPrinterLab/Project/PrinterManagement, for more details in the original format of the Standard Printer MIB. |
| OCT install_date | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.8 | OCTET STRING | read-write | Identifies the date that the device was installed. The format of the string is 'YYYYMMDDHHmmZ'. Where: YYYY is the year. MM is the month (1-12). DD is the day (1-31). HH is the hour of the day (0-23). mm are the minutes (0-59). 'Z' designates Greenwich Mean Time; if 'Z' not specified, value is local time. Device POS must specify the conditions for setting this object. Additional information: Setting the > object will enable setting this object. |
| interface | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4 | |||
| intray | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3 | |||
| intray1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.1 | |||
| intray2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.2 | |||
| intray3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.3 | |||
| intray5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.5 | |||
| intray6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.6 | |||
| intrays | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3 | |||
| io | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1 | |||
| INT io_switch | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.1.2 | INTEGER | read-only | Indicates if the device will switch between I/O channels when a job boundary is encountered and print job data is available on another I/O channel. |
| INT io_timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.1.1 | INTEGER | read-write | The amount of time, in seconds, to wait for more print job data to be received before an I/O timeout occurs. The I/O channel being timed is the I/O channel that received the data associated with the current print job. If an I/O timeout occurs, the PDL processing sub-system assumes all the data associated with the current print job has been received, and processes the end of job in a PDL specific manner. The POS specifies the supported values. Additional information: If an I/O timeout occurs,the PDL processing sub-system will consider it an end of job condition only if there is data from another I/O subsystem waiting to be processed. The supported values are 5 to 300 seconds. Setting to a value outside the supported range returns status and the value will be snapped to the nearest supported value. |
| job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6 | |||
| job_being_parsed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.2.1 | |||
| job_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5 | |||
| job_info_accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28 | |||
| INT job_info_accounting_black_dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.8 | INTEGER | read-only | Contains the total number of black pixels used in a particular job. |
| INT job_info_accounting_color_impression_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.7 | INTEGER | read-only | Contains the total number of color pages printed in a particular job. |
| INT job_info_accounting_cyan_dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.10 | INTEGER | read-only | Contains the total number of cyan pixels used in a particular job. |
| INT job_info_accounting_finishing_options | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.3 | INTEGER | read-only | Contains the finishing option used on the printed job. The finishing option specified for the first page will decide the finishing option of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job. |
| INT job_info_accounting_fixer_dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.33 | INTEGER | read-only | Contains the total number of fixer pixels used in a particular job. |
| INT job_info_accounting_grayscale_impression_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.6 | INTEGER | read-only | Contains the total number of monochrome pages printed in a particular job. |
| INT job_info_accounting_job_type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.14 | INTEGER | read-only | Keeps track of what type of job is processed. |
| INT job_info_accounting_magenta_dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.11 | INTEGER | read-only | Contains the total number of magenta pixels used in a particular job. |
| INT job_info_accounting_media_duplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.5 | INTEGER | read-only | Contains the total number of duplex pages printed in a particular job. |
| INT job_info_accounting_media_simplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.4 | INTEGER | read-only | Contains the total number of simplex pages printed in a particular job. |
| INT job_info_accounting_media_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.1 | INTEGER | read-only | Contains the media size of the printed job. The media size of the first page will decide the media size of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job. |
| INT job_info_accounting_media_type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.2 | INTEGER | read-only | Contains the media type of the printed job. The media type of the first page will decide the media type of the entire job. The return value of this object will only be valid when the printer finishes printing the entire job. |
| INT job_info_accounting_yellow_dots | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.28.9 | INTEGER | read-only | Contains the total number of yellow pixels used in a particular job. |
| OCT job_info_attr_1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.1 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. Attribute objects are saved sequentially, starting with 1, after the start of a job. If more attributes are set than there are objects to store them, the excess JOBATTR values are ignored. If the corresponding SET JOBATTR= command has not been received when a get is done for this object, a status of will be returned. |
| OCT job_info_attr_10 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.10 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_11 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.11 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_12 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.12 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_13 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.13 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_14 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.14 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_15 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.15 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_16 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.16 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.2 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.3 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.4 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.5 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.6 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_7 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.7 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_8 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.8 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| OCT job_info_attr_9 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23.9 | OCTET STRING | read-only | Returns the value that was set in PJL via the SET JOBATTR= command. See JOB-INFO-ATTR-1 for details. |
| job_info_attribute | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.23 | |||
| OCT job_info_change_id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1.3 | OCTET STRING | read-only | Returns the current value of an object in the job-info sub-tree whose value has changed. Define the object identifier for the object whose value has changed as job-info.required-field.optional-field.job-id. job-info represents the OID prefix of all objects in the job-info sub-tree. Required-field represents the OID field value that follows the job-info prefix. Since some objects in the job-info sub-tree have two OID fields between the job-info prefix and the job-id, the optional-field represents the OID field between the required-field and the job-id field, if present. Using this definition, the format for the JOB-INFO-CHANGE-ID binary value can be described as follows: Bytes 0-3 : required-field Bytes 4-7 : optional-field, or all zeros if there is no optional field Bytes 8-11: Job ID. Bytes 12-n : The value of the object job-info. required-field.optional-field.job-id. All multi-byte values stored in Motorola (big-endian) format, where the most significant byte occurs first. Additional information: InkJet will use this object to report changes to the job-info-pages-printed and job-info-state objects. The required-field (bytes 0 through 3) will designate whether the change to be reported involves the pages printed (13) or job state (15). The optional-field (bytes 4 through 7) will always be zeroes. The value-field (bytes 12 through 15) will contain the new value for pages printed or job state cast to a 32-bit integer. Note: It is possible that traps generated by this object have the same value. This is caused by the architecture of the InkJet System. In the InkJet System, it is highly probable that the object value will change so rapidly that when the trap is processed, PML will read the same value twice. This is timing related and will generally be seen at the end of a job. |
| INT job_info_io_source | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.11 | INTEGER | read-only | Indicates which I/O source, the print job was received over. The value maps to port numbering scheme supported in the DEVICE/SOURCE-SUBSYSTEM/IO/PORTS sub-tree. |
| OCT job_info_name1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.1 | OCTET STRING | read-only | Contains the first part of this print job's name. The last OID field for this dynamic object contains the job ID. Additional information: The job name is the string specified by the NAME= parameter of the @PJL JOB command which allows a maximum of 80 characters. The first 40 characters are in this object and the second 40 are in job-info-name2. The symbol set is Roman-8. When jobs are nested, the value assigned to this object is the name provided by the most recent @PJL JOB NAME= command. If no name is provided, a null string is returned. |
| OCT job_info_name2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.2 | OCTET STRING | read-only | Contains the second part of this print job's name. The last OID field for this dynamic object contains the job ID. Additional information: See job-info-name1. |
| INT job_info_outcome | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.19 | INTEGER | read-only | Indicates if any warning or error conditions were encountered while processing the assoicated job. The last OID field for this dynamic object contains the job ID. Additional information: In InkJet, warnings and errors are not recorded in this object. Although no meaningful information can be obtained from this object, it is kept around for the compatibility needs of existing software. |
| INT job_info_pages_printed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.13 | INTEGER | read-only | Indicates the number of pages printed by the destination subsystem. If none of the cSourceSubsystem, cProcessingSubsystem or cDestinationSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the total number of pages printed for this job. This value may increase by two each time for duplex jobs. The last OID field for this dynamic object contains the job ID. Additional information: If multiple copies of a page are printed, each copy is counted individually. |
| INT job_info_pages_processed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.12 | INTEGER | read-only | Indicates the number of pages processed by the processing subsystem. If neither the cSourceSubsystem or the cProcessingSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the total number of pages processed for this job. The last OID field for this dynamic object contains the job ID. Additional information: This object is incremented by one when a page is processed (`closed' by the personality), regardless of the number of pages that are printed as a result of the single page processed. In other words, it does not matter how many identical copies of a page are printed or no pages may be printed if operating in silent run mode, this count is incremented exactly once. A page is considered processed when all of the input data has been processed for a page (that is, when the intermediate has been produced, and the personality has `closed' the page. At this time, the image of the page is not necessarily completely formed.) |
| INT job_info_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.14 | INTEGER | read-only | Indicates the number of bytes of data processed by the processing subsystem. If neither of the cSourceSubsystem or cProcessingSubsystem items are in the associated JOB-INFO-STAGE object, then this object contains the size of this job, in bytes. The last OID field for this dynamic object contains the job ID. Additional information: This count may be incremented by values other than one as blocks of data are processed; blocks of data (which may be as large as 2K bytes) will be processed in a varying amount of time. During the processing of a job and even when a job completes, an exact count of the number of I/O bytes processed by the job is not necessarily to be expected. |
| OCT job_info_stage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.10 | OCTET STRING | read-only | Indicates what printer sub-systems are currently processing this print job. The last OID field for this dynamic object contains the job ID. cSourceSubsystem - some of the job is in the printer I/O subsystem. cProcessingSubsystem - some of the job is in the printer imaging processing subsystem. cDestinationSubsystem - some of the job is being printed. Additional information: For InkJet, cSourceSubsystem and cProcessingSubsystem will always be set and cleared together. They are set when the beginning of the job is detected, and they are cleared when the end of the job is parsed. A non-printing job will never set cDestinationSubsystem. When a page is ready to be printed (the intermediate has been built and the page is `closed' by the personality), cDestinationSubsystem will be set even if a page of a previous job is currently being printed. cDestinationSubsystem remains set until the last page of the job has finished printing. If a page requires extensive processing and allows all the previous pages of a job to complete printing, cDestinationSubsystem will remain set until the last page of the job has finished printing. |
| INT job_info_state | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.5.15 | INTEGER | read-only | Indicates the state of the job. The last OID field for this dynamic object contains the job ID. eAborted - the print job was aborted. eWaitingForResources - the print job requires resources that are not currently available. Example resources that can cause the job to wait include the print engine or PDL processor being unavailable. The print engine could be unavailable due to paper out, paper jam, staple out, stapler jam, marking agent low, output bin full, etc. The PDL processor could be unavailable due to an off-line condition. Each printer specific object specification should state which conditions cause a job to be waiting for resources and also state which objects can be retrieved by an application to determine the exact cause of a resource being unavailable. ePrinted - the job has printed. The related JOB-INFO- OUTCOME object indicates if any problems were encountered while the job was processed. eRetained - the job can be reprinted. eTerminating - the job was aborted or cancelled and is currently is terminating. eInterrupted - the job has been interrupted. The job can be continued. ePaused - the job has been paused. The job can be continuted. eCancelled - the job has been cancelled. eProcessing - the job is currently being printed normally. |
| OCT job_input_auto_continue_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.36 | OCTET STRING | read-write | Returns or sets the device behavior when the desired media is not currently available. cCancelJob - The device cancels the job. The device POS should explain what happens if this item is not the only item in the collection. cAutoMediaSizeOverride - The device is allowed to substitute a different size media. cAutoMediaNameOverride - The device is allowed to substitute a different media name. cUSMediaSizeOverride - The device is allowed to substitute US media sizes (letter, etc.) for ISO media sizes (A4, etc.). cISOMediaSizeOverride - The device is allowed to substitute ISO media sizes (A4, etc.) for US media sizes (letter, etc.). Additional information: Returns or sets the device behavior when the desired media is not currently available. cCancelJob - The device cancels the job regardless of other item settings. cAutoMediaSizeOverride - The device is allowed to substitute a different size media. cAutoMediaNameOverride - The device is allowed to substitute a different media name. -- cUSMediaSizeOverride - The device is allowed to substitute -- US media sizes (letter, etc.) for ISO media sizes -- (A4, etc.). -- cISOMediaSizeOverride - The device is allowed to substitute -- ISO media sizes (A4, etc.) for US media sizes -- (letter, etc.). At least one bit of the collection must be set; setting this object to zero will cause a status of to be returned. This object describes the action that is performed when the JOB-INPUT-AUTO-CONTINUE-TIMEOUT expires. |
| INT job_input_auto_continue_timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.35 | INTEGER | read-write | The number of seconds the device waits after a job related continuable error occurs before automatically continuing. An example job related continuable error is the job requesting a media size that is not available. After the timeout expires, the device will continue processing the job as if a continue event occurred, such as the front panel continue key being pressed. If the value is -1, the device does not automatically continue after a job related continuable error occurs. If the value is 0, the device immediately continues. If the value is greater than 0, the value represents the timeout value in seconds. Additional information: The number of seconds the device waits after a job related continuable error occurs before automatically continuing. An example job related continuable error is the job requesting a media size that is not available. After the timeout expires, the device will continue processing the job accourding to the action defined by JOB-INPUT-AUTO-CONTINUE-MODE. If the value is -1, the device does not automatically continue after a job related continuable error occurs. If the value is 0, the device immediately continues. If the value is greater than 0, the value represents the timeout value in seconds. The data for this object is stored in NVRAM. |
| INT job_output_auto_continue_timeout | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.40 | INTEGER | read-write | Returns or sets the time that the printer will wait after an output bin becomes full and the printer is trying to deliver a sheet of media to that output bin. When the timeout expires, the job is processed according to the OUTBINn-OVERRIDE-MODE. A value of -1 indicates that the printer will wait for a continue event. A non-negative value is the number of seconds to wait. Additional information: Returns or sets the time that the printer will wait after an output bin becomes full and the printer is trying to deliver a sheet of media to that output bin. When the timeout expires, the job is processed according to the OUTBINn-OVERRIDE-MODE. A value of -1 indicates that the printer will wait for a continue event. A non- negative value is the number of seconds to wait. |
| OCT localization_countries_supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.53 | OCTET STRING | read-only | 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. |
| OCT localization_languages_supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.52 | OCTET STRING | read-only | 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. |
| mass_storage_block_driver | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15 | |||
| INT mass_storage_resource_change_counter | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12.3.1 | INTEGER | read-only | A counter which changes when a mass storage based resource has been added or deleted. Additional information: The value of this counter changes each time the MASS-STORAGE-RESOURCE-CHANGED object is set to eTrue. The value also changes when the mass storage device is initialized. However, the value does not change when a mass storage device is removed and a different mass storage device is installed. Initializing all volumes sets this object back to the factory default value. A reboot sets this object back to the factory devalut value. Returns status if attempting to access this object and there is no storage device is installed. |
| INT mass_storage_resource_changed | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12.3.2 | INTEGER | write-only | Setting to eTrue causes MASS-STORAGE-RESOURCE-CHANGE-COUNTER to be incremented. Additional information: Returns status if attempting to access this object and there is no storage device is installed. |
| mass_storage_resources | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12.3 | |||
| INT maximum_ram_disk_memory | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.2.1 | INTEGER | read-only | This object's name is misleading. This object does not return the maximum configurable RAM disk size. Instead, it returns the maximum amount of memory, in bytes, that can used to increase the size of the RAM disk. Additional information: This object returns the maximum amount of additional memory that is available for increasing the size of the RAM disk. |
| media_counts | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.7 | |||
| media_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3 | |||
| OCT media_names_available | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.1.1 | OCTET STRING | read-write | The value of this object controls which of the MEDIAx-NAME objects are supported. If a bit is set to zero, then attempting to get or set the corresponding MEDIAx-NAME objects will return . Additional information: Setting a bit to one will cause the corresponding MEDIAn- objects to be available (attempting to access an unavailable object will return ). MEDIA1- objects are always present, as this is the default media. If this object is set to a value that does not include cMediaName2Available, that bit will be set and a status of will be returned. |
| INT media_number_of_type_supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.8.1 | INTEGER | read-only | Indicates the maximum number of supported media types. Additional information: Indicates the number of supported media type. This also indicates which bit in MEDIA-NAMES-AVAILABLE is significant |
| media_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5 | |||
| INT media_size_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5.1 | INTEGER | read-only | The number of impressions printed on sheets of this media size. The device POS should state whether this value is lost across a power cycle or is kept in permanent storage. Additional information: The value of this object is persistent across a power cycle. The index for these objects, the last number of the OID, uniquely identifies the paper size. This value corresponds to the page sizes listed below. These values are also documented in the PCL Implementor's Guide and the PML Master MIB. 1 US-Executive 2 US-Letter 3 US-Legal 10 Foolscap 11 Ledger 15 Statement 17 ROC 16K 19 eROC8K 25 ISO and JIS A5 26 ISO and JIS A4 27 ISO and JIS A3 36 RA4 37 SRA4\ 38 SRA3 39 RA3 44 JIS B6 45 JIS B5 46 JIS B4 72 Japanese Postcard Double 74 4x6 75 5x8 101 Custom 120 Tabloid Extended 12x18 122 5x7 32767 Unknown Paper Size |
| INT media_size_west_edge_first_side_offset | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5.2 | INTEGER | read-write | Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the first printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the first printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. The values in the sub array index are from the media size table in the hpmib. This adjustment is done on a paper size by paper size basis. The standard PCL5 codes for paper size are used for the value used in the OID. Please see S_ARRAY_SUB1 for legal |
| INT media_size_west_edge_second_side_offset | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5.3 | INTEGER | read-write | Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the second printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). The adjustment is for the second printed side of the medium only. A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. The values in the sub array index are from the media size table in the hpmib. This adjustment is done on a paper size by paper size basis. The standard PCL5 codes for paper size are used for the value used in the OID. Please see S_ARRAY_SUB1 for legal values. The data for this object is stored in NVRAM. |
| INT media_size_west_edge_side_offset_by_tray | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.5.4 | INTEGER | read-write | Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Each OID binding corresponds to a valid tray number for this product. There can be a maximum of 15 trays, a combination of internal and external trays. Products that support other combinations of trays will specify this information in the device pos. The data for this object is stored in NVRAM. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted relative to the west edge of the medium (see NORTH-EDGE-OFFSET). A positive value moves the image away from the west edge of the medium. A negative value moves the image closer to the west edge of the medium. The value 0 will return the image to its factory default position. Each OID binding corresponds to a valid tray number for this product. There can be a maximum of 15 trays, a combination of internal and external trays. Products that support other combinations of trays will specify this information in the device pos. The data for this object is stored in NVRAM. |
| media_types | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.8 | |||
| media1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1 | |||
| OCT media1_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1.1 | OCTET STRING | read-only | Media 1 name. Additional information: The order of these objects is determined by the order of SysOD_MediaTypeEnum. The symbol set for this string is Roman-8. |
| INT media1_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1.3 | INTEGER | read-only | Number of sheets of media 1 that have been printed. The device POS should state whether this value is lost across a power cycle or kept in NVRAM. Additional information: Number of sheets of media 1 that have been printed. This page count is saved in NVRAM after every 10 pages. The maximum value is 4,294,967,295 which will never be reached in normal operation. The page count is incremented when a sheet of media is pulled from an input tray. A duplex printed sheet will cause this counter to be incremented by one. |
| OCT media1_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.1.2 | OCTET STRING | read-only | Length restricted version of the media name 1. The length restriction is required to allow the media name to be displayed on the device's control panel. The device POS must state the maximum number of characters allowed. If the device also has a limitation on what characters in a character set can be used (e.g. only uppercase characters allowed), the POS should also state character restrictions. Additional information: The order of these objects is determined by the order of SysOD_MediaTypeEnum. Length restricted version of the media name 1. The length restriction is required to allow the media name to be displayed on the device's control panel. The maximum supported string length is 9 characters. If the user entered string is too long, the device will store the first 9 characters and will return the status. The characters must be in the range 20H to 7FH except 5C cannot be used. The default symbol set is Roman-8 for English; additional legal symbol sets are ISOLatin5, ISOLatin2 and Windows31J. Setting this object with characters outside of the range or of an illegal symbol set will cause an error status of to be returned. This string is localized according to prtConsoleLocalization. If this object represents a standard type, and the user attempts to set the object, 'OK Nearest Legal Value Substituted' will be returned, and the standard value is retained. If this object represents a user defined type, and the user attempts to set the object, then the set will be successfull. |
| media10 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10 | |||
| OCT media10_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10.1 | OCTET STRING | read-only | Media 10 name. Additional information: See MEDIA1-NAME. |
| INT media10_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10.3 | INTEGER | read-only | Number of sheets of media 10 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media10_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.10.2 | OCTET STRING | read-only | Length restricted version of the media name 10. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media11 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11 | |||
| OCT media11_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11.1 | OCTET STRING | read-only | Media 11 name. Additional information: See MEDIA1-NAME. |
| INT media11_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11.3 | INTEGER | read-only | Number of sheets of media 11 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media11_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.11.2 | OCTET STRING | read-only | Length restricted version of the media name 11. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media12 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12 | |||
| OCT media12_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12.1 | OCTET STRING | read-only | Media 12 name. Additional information: See MEDIA1-NAME. |
| INT media12_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12.3 | INTEGER | read-only | Number of sheets of media 12 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media12_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.12.2 | OCTET STRING | read-only | Length restricted version of the media name 12. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media13 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13 | |||
| OCT media13_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13.1 | OCTET STRING | read-only | Media 13 name. Additional information: See MEDIA1-NAME. |
| INT media13_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13.3 | INTEGER | read-only | Number of sheets of media 13 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media13_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.13.2 | OCTET STRING | read-only | Length restricted version of the media name 13. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media14 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14 | |||
| OCT media14_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14.1 | OCTET STRING | read-only | Media 14 name. Additional information: See MEDIA1-NAME. |
| INT media14_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14.3 | INTEGER | read-only | Number of sheets of media 14 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media14_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.14.2 | OCTET STRING | read-only | Length restricted version of the media name 14. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media15 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15 | |||
| OCT media15_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15.1 | OCTET STRING | read-only | Media 15 name. Additional information: See MEDIA1-NAME. |
| INT media15_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15.3 | INTEGER | read-only | Number of sheets of media 15 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media15_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.15.2 | OCTET STRING | read-only | Length restricted version of the media name 15. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media16 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16 | |||
| OCT media16_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16.1 | OCTET STRING | read-only | Media 16 name. Additional information: See MEDIA1-NAME. |
| INT media16_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16.3 | INTEGER | read-only | Number of sheets of media 16 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media16_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.16.2 | OCTET STRING | read-only | Length restricted version of the media name 16. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media17 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17 | |||
| OCT media17_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17.1 | OCTET STRING | read-only | Media 17 name. Additional information: See MEDIA1-NAME. |
| INT media17_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17.3 | INTEGER | read-only | Number of sheets of media 17 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media17_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.17.2 | OCTET STRING | read-only | Length restricted version of the media name 17. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media18 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18 | |||
| OCT media18_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18.1 | OCTET STRING | read-only | Media 18 name. Additional information: See MEDIA1-NAME. |
| INT media18_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18.3 | INTEGER | read-only | Number of sheets of media 18 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media18_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.18.2 | OCTET STRING | read-only | Length restricted version of the media name 18. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media19 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.19 | |||
| OCT media19_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.19.1 | OCTET STRING | read-only | Media 19 name. Additional information: See MEDIA1-NAME. |
| INT media19_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.19.3 | INTEGER | read-only | Number of sheets of media 19 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media19_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.19.2 | OCTET STRING | read-only | Length restricted version of the media name 19. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2 | |||
| OCT media2_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2.1 | OCTET STRING | read-only | Media 2 name. Additional information: See MEDIA1-NAME. |
| INT media2_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2.3 | INTEGER | read-only | Number of sheets of media 2 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media2_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.2.2 | OCTET STRING | read-only | Length restricted version of the media name 2. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3 | |||
| OCT media3_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3.1 | OCTET STRING | read-only | Media 3 name. Additional information: See MEDIA1-NAME. |
| INT media3_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3.3 | INTEGER | read-only | Number of sheets of media 3 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media3_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.3.2 | OCTET STRING | read-only | Length restricted version of the media name 3. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4 | |||
| OCT media4_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4.1 | OCTET STRING | read-only | Media 4 name. Additional information: See MEDIA1-NAME. |
| INT media4_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4.3 | INTEGER | read-only | Number of sheets of media 4 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media4_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.4.2 | OCTET STRING | read-only | Length restricted version of the media name 4. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5 | |||
| OCT media5_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5.1 | OCTET STRING | read-only | Media 5 name. Additional information: See MEDIA1-NAME. |
| INT media5_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5.3 | INTEGER | read-only | Number of sheets of media 5 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media5_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.5.2 | OCTET STRING | read-only | Length restricted version of the media name 5. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6 | |||
| OCT media6_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6.1 | OCTET STRING | read-only | Media 6 name. Additional information: See MEDIA1-NAME. |
| INT media6_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6.3 | INTEGER | read-only | Number of sheets of media 6 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media6_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.6.2 | OCTET STRING | read-only | Length restricted version of the media name 6. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media7 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7 | |||
| OCT media7_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7.1 | OCTET STRING | read-only | Media 7 name. Additional information: See MEDIA1-NAME. |
| INT media7_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7.3 | INTEGER | read-only | Number of sheets of media 7 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media7_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.7.2 | OCTET STRING | read-only | Length restricted version of the media name 7. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media8 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8 | |||
| OCT media8_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8.1 | OCTET STRING | read-only | Media 8 name. Additional information: See MEDIA1-NAME. |
| INT media8_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8.3 | INTEGER | read-only | Number of sheets of media 8 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media8_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.8.2 | OCTET STRING | read-only | Length restricted version of the media name 8. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| media9 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9 | |||
| OCT media9_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9.1 | OCTET STRING | read-only | Media 9 name. Additional information: See MEDIA1-NAME. |
| INT media9_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9.3 | INTEGER | read-only | Number of sheets of media 9 that have been printed. See MEDIA1-PAGE-COUNT for details. Additional information: See MEDIA1-PAGE-COUNT. |
| OCT media9_short_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.3.9.2 | OCTET STRING | read-only | Length restricted version of the media name 9. See MEDIA1-SHORT-NAME for details. Additional information: See MEDIA1-SHORT-NAME. |
| mio | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3 | |||
| mio1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1 | |||
| OCT mio1_manufacturing_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1.3 | OCTET STRING | read-only | Returns information describing the manufacture of the I/O card installed in MIO/EIO slot 1. May include serial number and firmware revision. Additional information: The format of the string returned is determined by the manufacturer of the EIO device. There is no standard for content of the string. |
| OCT mio1_model_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1.2 | OCTET STRING | read-only | Returns product information identifying the I/O card. Example: XXXX. |
| INT mio1_type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.1.4 | INTEGER | read-only | Returns an indication of the type of option installed in MIO/EIO slot 1. See SIMM1-TYPE for an explanation of the enumerations. |
| mio4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.4 | |||
| OCT mio4_manufacturing_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.4.3 | OCTET STRING | read-only | Returns information describing the manufacture of the I/O card installed in MIO/EIO interface 4. May include serial number and firmware revision. Additional information: Returns a string describing the embedded JDI LAN card. |
| OCT mio4_model_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.4.2 | OCTET STRING | read-only | Returns product information identifying the I/O card. Example: XXXX. Additional information: Returns a string describing the firmware version of the embedded JDI LAN card. |
| INT mio4_type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.3.4.4 | INTEGER | read-only | Returns an indication of the type of option installed in MIO/EIO interface 4. See SIMM1-TYPE for an explanation of the enumerations. Additional information: Returns eEmpty if the embedded JDI LAN card is disabled. Returns eIOCard if the embedded JDI LAN card is enabled. |
| OCT model_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.2 | OCTET STRING | read-only | Identifies the device model name (e.g. ''DeskJet 1200C''). The string is as specific as possible. Capitalization and spacing should match family naming conventions. Products should note in POS if the model name on the HP corporate price list changes but the device reports the previous device name. If the model name changes based on the installed options, the POS should indicate if only the base model name is returned, or if the device senses the installed options and returns the correct model name. If possible, encode the model name in a symbol set (like Roman-8) that matches the ASCII character set and limit the characters used to ASCII characters. Additional information: Since the value of this object is frequently used in displaying a list of printers, it is kept relatively short in case systems have limited width for their display area. The model name does not change based on sensing of installed options. |
| OCT model_number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.1 | OCTET STRING | read-only | 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: 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. The value of this object does not change based on the installed options. The default of this object is the same on all InkJet printers. |
| INT mono_color_switching_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.31 | INTEGER | read-write | This object allows the user to view/change the color/mono switching mode for a device. Additional information: This object allows the user to view/change the color/mono switching mode for a device. The behavior of each setting may vary depending on the device. The value will be stored in NVRAM |
| INT non_assured_oht_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.7.1 | INTEGER | read-only | This is a count of the number of invalid (non-HP Laser Jet) transparencies that have been printed on. This value is incremented every time an invalid OHT is printed on It is reset whenever the fuser count is set to 0. Additional information: This is a count of the number of invalid (non HP Laser Jet) transparencies that have been printed on. This value is incremented every time an invalid OHT is printed on. It is reset whenever the fuser count is set to 0. |
| INT north_edge_offset | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.1.2 | INTEGER | read-write | Returns or sets the number of 300 dpi dots by which the image is shifted. Shift is relative to the leading edge of the medium as the medium flows through the marking engine with the side to be imaged facing the observer. The leading edge is the North edge and the other edges are defined by the normal compass layout of directions with the compass facing the observer. The adjustment is for all pages printed. A positive value moves the image away from the leading edge of the medium. A negative value moves the image closer to the leading edge of the medium. The value 0 will return the image to its factory default position. Additional information: Returns or sets the number of 300 dpi dots by which the image is shifted. Shift is relative to the leading edge of the medium as the medium flows through the marking engine with the side to be imaged facing the observer. The leading edge is the North edge and the other edges are defined by the normal compass layout of directions with the compass facing the ob server. The adjustment is for all pages printed. A positive value moves the image away from the leading edge of the medium. A negative value moves the image closer to the leading edge of the medium. The value 0 will return the image to its factory default position. The value of this object is stored in NVRAM. |
| INT on_off_line | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.5 | INTEGER | read-write | 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; 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; status is returned (see the Control Panel ERS for a list of error conditions). Setting to eOffline has the following affect: Printer will immediately go to or remain in the Offline state; 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; 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; 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. |
| operating_system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.19 | |||
| OCT os_execute_file | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.19.1 | OCTET STRING | write-only | This object's input is a null-terminated string representing a fully-qualified path name for an executable file. This object causes the file to be executed by the OS. Additional information: This object's input is a null-terminated string of two or more whitespace-separated tokens. The first token is a path to a directory to make the current working directory. The second token is a path to an executable file to be executed. Any remaining whitespace-separated tokens are optional and will be passed as parameters to the executable. The paths to the directory and executable can be either PJL style (e.g., 1:\app\example) or UNIX-style (e.g., /hpmnt/dsk_ide1a/app/example). The executable is run in a separate process. |
| outbin | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4 | |||
| outbin1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.1 | |||
| OCT outbin1_error_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.1.12 | OCTET STRING | read-only | A device specific description of the last error encountered for output bin 1. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return . The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages aren't aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING |
| INT outbin1_maximum_binding | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.1.10 | INTEGER | read-only | The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. |
| OCT outbin1_override_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.1.9 | OCTET STRING | read-write | Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait). |
| INT outbin1_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.1.11 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin. |
| outbin2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.2 | |||
| OCT outbin2_error_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.2.12 | OCTET STRING | read-only | A device specific description of the last error encountered for output bin 2. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return . The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages aren't aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING |
| INT outbin2_maximum_binding | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.2.10 | INTEGER | read-only | The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. |
| OCT outbin2_override_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.2.9 | OCTET STRING | read-write | Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait). |
| INT outbin2_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.2.11 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin. |
| outbin3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.3 | |||
| OCT outbin3_error_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.3.12 | OCTET STRING | read-only | A device specific description of the last error encountered for output bin 3. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return . The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages aren't aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING |
| INT outbin3_maximum_binding | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.3.10 | INTEGER | read-only | The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. |
| OCT outbin3_override_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.3.9 | OCTET STRING | read-write | Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait). |
| INT outbin3_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.3.11 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin. |
| outbin4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.4 | |||
| OCT outbin4_error_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.4.12 | OCTET STRING | read-only | A device specific description of the last error encountered for output bin 4. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return . The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages aren't aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING |
| INT outbin4_maximum_binding | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.4.10 | INTEGER | read-only | The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. |
| OCT outbin4_override_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.4.9 | OCTET STRING | read-write | Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait). |
| INT outbin4_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.4.11 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin. |
| outbin5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.5 | |||
| OCT outbin5_error_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.5.12 | OCTET STRING | read-only | A device specific description of the last error encountered for output bin 5. Each POS should document the meaning of all supported error information. Additional information: This is a description of the current error state of a finishing device. (ie stapler). If the bin does not support any finishing capabilities then the object will return . The possible return values are as follows: Byte1, Byte2, and Byte3 should be 0x00. as they are reserved for future use. Byte4 is a bit field that can be interpreted as follows: bit 0 - unused bit 1 - eBinderOut Out of staples bit 2 - eBinderLimit Too many pages to finish bit 3 - eBinderJam Staple jammed in stapler bit 4 - eBinderAlign Pages aren't aligned correctly to finish. bit 5 - unused bit 6 - unused bit 7 - unused NOTE: Because HP is marketing a device with a max of 16 bins the OUTBIN-MAXIMUM-BINDING objects are 3-18 but the external device specification requires support of up to 315 output bins. Therefore if these bins exist above 16, then the coresponding objects will also exist OUTBIN19-MAXIMUM-BINDING ... OUTBIN317-MAXIMUM-BINDING |
| INT outbin5_maximum_binding | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.5.10 | INTEGER | read-only | The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. Additional information: The maximum number of sheets of 20 pound paper that can be bound by the binding device that serves this output bin. If a job exceeds this number and the job has requested binding, cBindingError will be set in NOT- READY-DESTINATION-PRINT-ENGINE. |
| OCT outbin5_override_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.5.9 | OCTET STRING | read-write | Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job. cOutbinFullOverride - The device sends subsequent media to the overflow bin. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. Additional information: Returns or sets the device behavior when this output bin condition causes printing to stop. cCancelJob - The device cancels the job, regardless of other bit settings. cOutbinFullOverride - The device sends subsequent media to the overflow bin. If this bin is the overflow bin, this bit is ignored. cOutbinAttentionOverride - The device ignores the attention condition and continues printing. cBinderAttentionOverride - The device ignores the binder attention condition and continues printing. This object describes the action that is performed when the JOB-OUTPUT-AUTO-CONTINUE-TIMEOUT expires. If no bits are set, no override action is taken (the printer will continue to wait). |
| INT outbin5_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3.5.11 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this output bin. Additional information: Provides the number of the Paper Handling Device that contains this output bin. |
| outbins | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.3 | |||
| INT overflow_bin | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.1.4 | INTEGER | read-write | Returns or sets the bin that will be used for additional sheets of media when the current bin is full and printing is allowed to continue. Additional information: Returns or sets the bin that will be used for additional sheets of media when the current bin is full and printing is allowed to continue. The data for this object is stored in NVRAM. |
| OCT override_media_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.2 | OCTET STRING | read-write | Sets a string identifying the media name that is to be used in place of the currently requested media. The substitution will continue until another media is selected. If set to a named media that is not currently available the requested media is not overridden. Additional information: When a request is received to print on a size and type of media that is not currently available, this object contains the desired media name as set by the print job. This object should be set to a media name that is currently available in the printer. If a paper mount request is not pending, attempting to get or set this object will cause to be returned. Setting this object to a string other than one of the MEDIAn-NAME objects (MEDIA-NAMES-AVAILABLE is applied) will cause a status of to be returned. |
| INT override_media_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1.3 | INTEGER | read-write | Sets the media size that is to be used in place of the currently requested media size. Additional information: When a request is received to print on a size and type of media that is not currently available, this object contains the desired size as set by the print job. This object should be set to a media size that is currently available to the printer. If a paper mount request is not pending, attempting to get or set this object will cause to be returned. |
| INT pcfax_send_enabled | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.2.13 | INTEGER | read-only | To check if PC Fax Send is enabled on the device. Also used by administrators to enable or disable PC Fax Send on the device |
| INT pcfax_send_operational | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.2.14 | INTEGER | read-only | To check if a fax can be sent from a PC to the device. This checks if a Fax service is supported on the MFP and if the administrator has enabled PC Fax Send for the device. Additional return types may be supported later to indicate why PC Fax Send is not operational on the device |
| INT pcl_default_font_number | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.15 | INTEGER | read-write | Returns or changes the value of the default font number variable in NVRAM. Writing an unsupported value causes the printer to generate an . Additional information: Valid numbers or 0 - 255, but only font numbers that are included in the PCL FONT LIST are selectable. |
| INT pcl_default_font_source | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.14 | INTEGER | read-write | Returns or changes the value of the default font source variable in NVRAM. |
| INT pcl_total_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3.5 | INTEGER | read-only | Total number of PCL pages printed by the device. Additional information: In InkJet the PCL page count is kept in NVRAM, and the NVRAM value is updated at least every 10 pages. NOTE: The value returned by this object will be incremented every page but if power is lost between NVRAM updates, up to 9 pages of the page count may be lost. The page count counter will be reset to zero after 16,777,215 (2^24-1) pages. The page count is incremented when a sheet of media is pulled from an input tray. A duplex printed sheet will cause this counter to be incremented by two. |
| INT pdf_enabled | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.15.3 | INTEGER | read-only | Used to tell whether the device supports PDF. |
| INT pdf_print_errors | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.15.4 | INTEGER | read-write | Returns or changes the value of the print PDF errors setting. If eOn, PDF prints an error page showing the error encountered and the stack at the time of the error. |
| INT pdf_total_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.15.2 | INTEGER | read-only | Total number of PDF pages printed by the device. |
| OCT pdf_version | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.15.1 | OCTET STRING | read-only | Contains version of PDF that is supported on the device. |
| pdl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3 | |||
| pdl_pcl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.3 | |||
| pdl_pdf | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.15 | |||
| pdl_postscript | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.4 | |||
| OCT perm_store_init_occurred | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.10 | OCTET STRING | read-only | This object will set the cAllPermDevices bit when a full perm storage initialization occurs (as would be the case for a brand new system or as a result of a powerup key sequence or > object request). If only one device was initialized (as would be the case if a disk were added to an existing system or a formatter were swapped out), then only the appropriate collection bits will be returned. If there are no collection bits set then this indicates that no initialization took place. |
| ph | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.7 | |||
| ph_devices | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.7.3 | |||
| ph2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.7.3.2 | |||
| phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5 | |||
| phd1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5.1 | |||
| OCT phd1_diagnostics_nvram_data | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5.1.9 | OCTET STRING | read-only | The NVRAM Diagnostics information consist of e-serial number, born-on date, manufacturing date, page counter, finisher counter, jam rate history, event log, and any other device-specific information that the PHD1 stores in NVRAM. This information will be returned as a string with XML format within XML tags. Additional information: The NVRAM Diagnostics information consist of e-serial number, born-on date, manufacturing date, page counter, finisher counter, jam rate history, event log, and any other device-specific information that the PHD2 stores in NVRAM. This information will be returned as a string with XML format within XML tags. |
| phd2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5.2 | |||
| INT phd2_capacity | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5.2.4 | INTEGER | read-only | 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: Returns an indication of the capacity of the installed option. For eInputPHD or eOutputPHD, or eBindingPHD the number of input trays or output bins is returned. If PHD 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned. |
| OCT phd2_device_specific_command | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.7.3.2.2 | OCTET STRING | write-only | This object is used to send device-specific data to the paper handling device. The meaning of the device-specific command is dependent on the paper handling device and must be specified in the POS. If the paper handling device does not accept the command, then an will be returned. If the device accepts the command, it may still be processing the command after the response has been returned. Depending on the device, the application may need to query PHDx-DEVICE-MEMORY to see when the command has completed. Additional information: This object is used to send device-specific data to the paper handling device. The meaning of the device- specific command is dependent on the paper handling device and must be specified in the POS. If the paper handling device does not accept the command, then an will be returned. If the device accepts the command, it may still be processing the command after the response has been returned. Depending on the device, the application may need to query PHDx-DEVICE-MEMORY to see when the command has completed. |
| OCT phd2_manufacturing_info | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5.2.2 | OCTET STRING | read-only | Returns information describing the manufacture of PHD 2. May include serial number and firmware revision. Additional information: Returns information describing the manufacture of PHD 2. If PHD 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned. |
| OCT phd2_model | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5.2.1 | OCTET STRING | read-only | Returns product information identifying PHD device 2. Example: XXXX. Additional information: Returns product information identifying the first paper handling device in the device chaing, PHD device 2. If PDH device 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned. |
| INT phd2_type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.5.2.3 | INTEGER | read-only | Returns an indication of the type of option installed in PHD interface 2. See SIMM1-TYPE for an explanation of the enumerations. Additional information: Returns an indication of the type of option installed in PHD interface 2. If PHD 2 does not exist, ERROR-UNKNOWN-OBJECT-IDENTIFIER will be returned. |
| port1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3.1 | |||
| INT port1_parallel_bidirectionality | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3.1.5 | INTEGER | read-write | Returns or changes whether the parallel I/O port supports bidirectional communication for port 1. This object is only supported if this port is a parallel port. Additional information: A get on this object returns the current mode for the parallel port. Setting this object specifies whether or not bidirectional communications will be allowed. |
| INT port1_parallel_speed | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3.1.4 | INTEGER | read-write | Returns or changes the maximum parallel I/O port speed, for port 1. This object is only supported if this port is a parallel port. An eSlow setting causes a 10 us busy pulse per received byte of data. An eFast setting causes a 1.5 us busy pulse per received byte of data. In rare cases, setting this value to eFast can cause the parallel port to no longer transfer data reliably. Additional information: When the value of this object is changed, it takes effect immediately. It is recommended that the printer be offline and not in a job when this object is changed. |
| ports | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.3 | |||
| INT postscript_defer_media | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.4.14 | INTEGER | read-write | This object will be used to enable or disable the use of the Adobe Postscript Paper Handling Model in the printer firmware. By default it is enabled which means that PostScript will always defer the media selection to HP Paper Handling Model. Additional information: nothing beyond old description |
| INT postscript_print_errors | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.4.11 | INTEGER | read-write | Returns or changes the value of the print PostScript errors setting. If eOn, PostScript prints an error page showing the error encountered and the stack at the time of the error. Additional information: This object is only supported if the PostScript option is installed. |
| INT postscript_total_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.4.5 | INTEGER | read-only | Total number of PostScript pages printed by the device. Additional information: This object is only supported if the PostScript option is installed. In InkJet the count is kept in NVRAM, and the NVRAM value is updated at least every 10 sheets. NOTE: The value returned by this object will be incremented every sheet but if power is lost between NVRAM updates up to 9 sheets of the count may be lost. The counter will be reset to zero after 16,777,215 (2^24-1) pages. |
| INT power_state | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.65 | INTEGER | read-write | This object is used to inquire about and to control the 'power state' of the device. The exact meaning of each enumeration may vary from device to device, but the general interpretation is as follows: ePowerStateAwake: The device is idle (immediately ready to process a job) or processing a job. ePowerStatePowerSave: The device is in a low power state and will not be immediately available to process an incoming job. A 'warm-up time' of several seconds can be expected. ePowerStateSleep: The device is in a sleep state. It uses less power than when in the power save state. It can also be expected to need a substantially longer warm-up time than when in the power save state. ePowerStateOff: The device is powered off. Note that when the device is powered off then SNMP/PML requests obviously cannot be honored. Therefore ePowerStateOff will likely never be returned from a PML get operation. However, ePowerStateOff could potentially be used in a PML set operation to power down the device if it has a software/firmware controllable power switch. For a given product it may not be possible to have the device enter the requested state due to the current state of the device. E.g., it may not be possible to enter the power save state if the device currently is in the sleep state. In this case a set operation will have an execution outcome of . The same execution outcome can be expected if the device is processing a job and an attempt is made to e.g. bring the device into the power save state or the sleep state. A get operation on the object returns the current power state of the device. While the device is transitioning from one state to another one of the values ePowerStateTransitioningToAwake, ePowerStateTransitioningToPowerSave, ePowerStateTransitioningToSleep or ePowerStateTransitioningToOff will be returned from a PML get operation. An attempt to perform a PML set with any of these four values will yield . Additional information: nothing beyond old description |
| INT powersave_enable_type | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.89 | INTEGER | read-write | ePowerSaveOff - printer stays awake all the time, can only sleep if sleep button is hit. ePowerSaveUseSleepDelay - use sleep delay the old way, sleep schedule is ignored . ePowerSaveUseSleepSchedule - sleep delay time is ignored, stay awake in wake period, sleep in 15 minutes in sleep period. ePowerSaveMaximize - set the sleep delay to 15 minutes, so wether in wake or sleep period it will sleep in 15 minutes. ePowerSaveCustom - set the sleep delay to 45 minutes, use sleep delay during wake period, sleep in 15 minutes in sleep period. Additional information: nothing beyond old description |
| print_engine | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1 | |||
| OCT print_engine_revision | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.26 | OCTET STRING | read-only | Print engine revision string. Additional information: Print engine revision string. The symbol set for this string is Roman-8. |
| print_media | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8 | |||
| OCT print_meter_category_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.10 | OCTET STRING | read-only | Total number of simplex plus duplex pages printed for this category of printed pages. |
| INT print_meter_dimplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.7 | INTEGER | read-only | Total number of dimplex pages printed for this category of printed pages. |
| INT print_meter_dimplex_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.11 | INTEGER | read-only | Total number of dimplex pages printed for this category of printed pages. |
| INT print_meter_duplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.5 | INTEGER | read-only | Total number of duplex pages printed for this category of printed pages. |
| INT print_meter_duplex_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.9 | INTEGER | read-only | Total number of duplex pages printed for this category of printed pages. |
| INT print_meter_print_quality | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.3 | INTEGER | read-only | This enumeration describes the selected print quality for this category of printed pages. |
| INT print_meter_simplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.4 | INTEGER | read-only | Total number of simplex pages printed for this category of printed pages. Additional information: The usage (simplex/duplex/dimplex count and charge objects described here and below detail the usage for the printer for each catagory of threshold/PQ and media size - as defined in the PCL Implementor's Guide and in the Media Size Table in the hpmib.txt. The OID bindings are based on the coverage threshold/PQ and media size. For example: The format for the OID is as follows: 1.1.16.7.1.1.m.n | | | | | / | \ Base OID | media size [1..32768] \ \ Threshold/PQ Category [1..4] m - Threshold/PQ values are 1..4: 1) Color Threshold 1 - Print Quality Best 2) Color Threshold 2 - Print Quality Best 3) Color Threshold 1 - Print Quality Good 4) Color Threshold 2 - Print Quality Good n - media size integer as defined in the Media Size Table in the hpmib.txt. The sum of all PML object values with the same base OID and 'm' value for a given media size will be returned by the corresponding PRINTED-MEDIA-COLOR-XXX-COUNT/CHARGE object. |
| INT print_meter_simplex_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.8 | INTEGER | read-only | Total number of simplex pages printed for this category of printed pages. |
| OCT print_meter_total_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.6 | OCTET STRING | read-only | Total number of simplex plus duplex pages printed multiplied by the unit charge for each given media size for this category of printed pages. |
| print_meter_usage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14 | |||
| INT print_meter_usage_threshold | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.14.2 | INTEGER | read-only | A value indicating the threshold value for this category of pages. The device POS will indicate the units of measure for this threshold value. Additional information: This usage threshold represents the number of 600dpi color pixels requested for a given image. The OID bindings for this object are as follows: 1 = Professional (BEST) - Full Color > 90K color pixels 2 = Professional (BEST) - Accent Color 90K color pixels 4 = General Office (GOOD) - Accent Color <= 90K color pixels These objects are normally read-only. |
| INT print_quality_level | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.6.9 | INTEGER | read-write | Returns or sets the print quality level. This value is used when print jobs do not indicate the desired print quality. Additional information: nothing beyond old description |
| INT printed_media_color_dimplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.3.1.6 | INTEGER | read-only | Total number of color dimplex pages printed in this media size. A color dimplex page is a color page that has been printed in duplex mode but the back side is blank. Dimplex pages occur when the printer firmware inserts a blank page in order to complete a duplexed job which is sent to the printer with an odd number of pages. |
| INT printed_media_color_duplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.3.1.3 | INTEGER | read-only | Total number of color duplex pages printed in this media size. |
| INT printed_media_color_simplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.3.1.1 | INTEGER | read-only | Total number of color simplex pages printed in this media size. |
| OCT printed_media_color_total_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.3.1.5 | OCTET STRING | read-only | The total count for color pages printed in this media size. |
| printed_media_color_usage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.3.1 | |||
| OCT printed_media_combined_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.7 | OCTET STRING | read-only | Total number of letter equivalently weighted pages both color and mono combined with this printer. Additional information: The combined total per page size of simplex and duplex color pages plus simplex and duplex mono pages. |
| INT printed_media_dimplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.10 | INTEGER | read-only | Total number of mono dimplex pages printed in this media size. A dimplex page is one that has been printed in duplex mode but the back side is blank. Dimplex pages occur when the printer firmware inserts a blank page in order to complete a duplexed job which is sent to the printer with an odd number of pages. |
| OCT printed_media_duplex_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.4 | OCTET STRING | read-write | Charge for each duplex page printed in this media size. Additional information: The click charges for duplex printed media. |
| INT printed_media_duplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.3 | INTEGER | read-only | Total number of duplex pages printed in this media size. |
| INT printed_media_maximum_pixels_per_page | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.6 | INTEGER | read-only | The number of pixels required to completely fill a page of this media size. The device POS will specify the resolution at which this pixel count was calculated. Additional information: The number of pixels required to fill a page of a specific media size. The OID binding is the media size you to query for. Only media sizes which the printer supports will be available. |
| OCT printed_media_simplex_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.2 | OCTET STRING | read-write | Charge for each simplex page printed in this media size. Additional information: This is a volatile set of charge values that will always reset to the default values after a power-cycle. The default values represent a ratio of the page size as compared to a letter or A4 page size. Setting this object has the effect of altering PRINTED-MEDIA-DUPLEX-CHARGE to have a value that is twice that of the simplex charge. |
| INT printed_media_simplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.1 | INTEGER | read-only | Total number of simplex pages printed in this media size. Additional information: The 5 usage (simplex/duplex count, simplex/duplex click charge and paper size total) objects described here and below detail the usage for the printer for each paper size defined in the PCL Implementor's Guide and in the Media Size Table in the hpmib.txt. The OID binding is based on the click attribute and paper size. For example: The format for the OID is as follows: 3.4.1.5.x.y | | | | \ / | paper size / \ PRINTER-CLICK_TOTALS ROOT \ OID click attribute 1..5 x values are 1..5: 1) simplex count 2) simplex click charge 3) duplex count 4) duplex click charge 5) printer or scanner paper size total (i.e. depends if the root OID is referrring to the printer or scanner). y : paper size as defined in the Media Size Table in the hpmib.txt |
| OCT printed_media_total_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1.5 | OCTET STRING | read-only | The total charge for pages printed in this media size. |
| printed_media_usage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.1 | |||
| printer_accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1 | |||
| INT printer_cal_cpr_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.38.1 | INTEGER | read-only | Provides the page count when last CPR calibration occurred. A '-1' indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers. Additional information: Provides the page count when last CPR calibration occurred. A -1 indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers. |
| INT printer_cal_cpr_utc | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.38.2 | INTEGER | read-only | Provides the time (in UTC - Universal Time Code format) when the last CPR calibration occurred. This value could be zero if no calibration has taken place or if the printer lacked real-time. This object exists (and is meaningful) only in color printers. Additional information: Provides the time (in UTC - Universal Time Code format) when last CPR calibration occurred. This value could be zero if no calibration has taken place and / or if the printer lacked real-time. This object exists (and is meaningful) only in color printers. |
| INT printer_cal_dhalf_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.37.1 | INTEGER | read-only | Provides the page count when the last DHALF calibration occurred. A '-1' indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers. Additional information: Provides the page count when last DHALF calibration occurred. A -1 indicates that a calibration of this kind has not taken place yet. This object exists (and is meaningful) only in color printers. |
| INT printer_cal_dhalf_utc | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.37.2 | INTEGER | read-only | Provides the time (in UTC - Universal Time Code format) when the last DHALF calibration occurred. This value could be zero if no calibration has taken place or if the printer lacked real-time. This object exists (and is meaningful) only in color printers. Additional information: Provides the time (in UTC - Universal Time Code format) when last DHALF calibration occurred. This value could be zero if no calibration has taken place and / or if the printer lacked real-time. This object exists (and is meaningful) only in color printers. |
| printer_calibration_cpr | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.38 | |||
| printer_calibration_dhalf | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.37 | |||
| printer_color_accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.3 | |||
| processing_subsystem | 1.3.6.1.4.1.11.2.3.9.4.2.1.3 | |||
| INT ram_disk_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.1.1 | INTEGER | read-write | Returns or controls RAM disk support. eOFF turns off the RAM disk functionality. eOn turns on the RAM disk functionality and creates a RAM disk whose size is controlled by the RAM-DISK-SIZE object. eAuto turns on the RAM disk functionality and creates a RAM disk size determined by the printer based on installed options and other memory related settings. Additional information: Returns or controls RAM disk support. eOFF turns off the RAM disk functionality. eAuto turns on the RAM disk functionality and creates a RAM disk size determined by the printer based on the amount of installed memory. |
| INT ram_disk_size | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.1.2 | INTEGER | read-only | Returns or controls the size of the RAM disk. The device POS specifies the minimum memory requirements. The object MAXIMUM-RAM-DISK-MEMORY specifies the maximum memory available for the RAM disk. Additional information: Returns the size of the RAM disk. |
| remote_procedure_call | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13 | |||
| INT remote_upgrade_enable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.8 | INTEGER | read-write | Enables or disables the ability to upgrade the firmware associated with any device that is available to be upgraded. This will be set to on or off at the RFU level in that if this mode is on any available device can be upgraded and if this mode is off none of the devices can be upgraded. There is not an individual mode for each device. Trying to set this to a value other than eOn or eOff will cause an UnsupportedValue error to occur. |
| INT reprint | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1.36 | INTEGER | read-write | Returns or changes the reprint (jam recovery) setting. If eOn, then the device will reprint pages jammed pages. If eOff, the device will not attempt to reprint jammed pages. If eAuto, a device dependent algorithm (which should be documented in the POS) will be used to determine if the page gets reprinted. This object controls all PDLs, unless a specific PDL supports its own reprint control mechanism. To date, only PostScript has a PDL reprint control mechanism. |
| resource_manager | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.12 | |||
| OCT rpc_bind_protocol_address | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1.2 | OCTET STRING | read-only | Array of Berkeley sockets style protocol addresses used to bind RPC to a communications protocol family. Setting an instance of this array object to a zero length binary value disables the transport protocol indicated by that instance. All multi-bytes fields are in network (or big-endian) order. Bytes 1 and 2 indicate the transport protocol. Some of the transport protocol mapping information can be found in RFC 1010 Assigned Numbers. A list of interesting transport protocol number mappings include: Protocol | Number ---------+------- UDP/IP | 17 IPX | 1000 MLC | 4660 Bytes 3 and 4 indicate the address family. The address family uses the same mapping as the BSD sockets address family. A list of interesting address family mappings include: Address Family | Number ---------------+------- Internet | 2 NetWare | 6 MLC | 22136 The format the fifth and following bytes is dependent on the address family. For the Internet address family, bytes 5 and 6 contain the port number, bytes 7 through 10 contain the IP address, and the following eight bytes are unused. For NetWare, bytes 5 through 8 are the network number, bytes 9 through 14 are the node number, and bytes 15 and 16 are the socket number. Additional information: The length of the binary value is zero if the instance of an object in the rpc-bind-protocol-address array is not in use. Returns status if attempting to access this object and there is no storage device is installed. |
| OCT rpc_bound_protocol_address | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.2.3 | OCTET STRING | read-only | An array of Berkeley sockets style protocol addresses that the NFS service has been bound to successful. The format is that same as the array of RPC-BIND-PROTOCOL-ADDRESS of objects. Additional information: Returns status if attempting to access this object and there is no storage device is installed. |
| INT rtc_time_zone | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.99 | INTEGER | read-write | Controls the time zone, which can be chosen from a list of time zones similar to the one used by Microsoft Windows operating system: eTzDateline -12:00 International Date Line West eTzSamoa -11:00 Midway Island, Samoa eTzHawaiian -10:00 Hawaii eTzAlaskan -09:00 Alaska eTzPacific -08:00 Pacific Time (US & Canada); Tijuana eTzUSMountain -07:00 Arizona eTzMexico2 -07:00 Chihuahua, La Paz, Mazatlan eTzMountain -07:00 Mountain Time (US & Canada) eTzCentralAmerica -06:00 Central America eTzCentral -06:00 Central Time (US & Canada) eTzMexico -06:00 Guadalajara, Mexico City, Monterrey eTzCanadaCentral -06:00 Saskatchewan eTzSAPacific -05:00 Bogota, Lima, Quito eTzEastern -05:00 Eastern Time (US & Canada) eTzUSEastern -05:00 Indiana (East) eTzAtlantic -04:00 Atlantic Time (Canada) eTzSAWestern -04:00 Caracas, La Paz eTzPacificSA -04:00 Santiago eTzNewfoundland -03:30 Newfoundland eTzESouthAmerica -03:00 Brasilia eTzSAEastern -03:00 Buenos Aires, Georgetown eTzGreenland -03:00 Greenland eTzMidAtlantic -02:00 Mid-Atlantic eTzAzores -01:00 Azores eTzCapeVerde -01:00 Cape Verde Is. eTzGreenwich 00:00 Casablanca, Monrovia eTzGMT 00:00 Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London eTzWEurope +01:00 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna eTzCentralEurope +01:00 Belgrade, Bratislava, Budapest, Ljubljana, Prague eTzRomance +01:00 Brussels, Copenhagen, Madrid, Paris eTzCentralEuropean +01:00 Sarajevo, Skopje, Warsaw, Zagreb eTzWCentralAfrica +01:00 West Central Africa eTzGTB +02:00 Athens, Beirut, Istanbul, Minsk eTzEeurope +02:00 Bucharest eTzEgypt +02:00 Cairo eTzSouthAfrica +02:00 Harare, Pretoria eTzFLE +02:00 Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius eTzJerusalem +02:00 Jerusalem eTzArabic +03:00 Baghdad eTzArab +03:00 Kuwait, Riyadh eTzRussian +03:00 Moscow, St. Petersburg, Volgograd eTzEAfrica +03:00 Nairobi eTzIran +03:30 Tehran eTzArabian +04:00 Abu Dhabi, Muscat eTzCaucasus +04:00 Baku, Tbilisi, Yerevan eTzAfghanistan +04:30 Kabul eTzEkaterinburg +05:00 Ekaterinburg eTzWestAsia +05:00 Islamabad, Karachi, Tashkent eTzIndia +05:30 Chennai, Kolkata, Mumbai, New Delhi eTzNepal +05:45 Kathmandu eTzNCentralAsia +06:00 Almaty, Novosibirsk eTzCentralAsia +06:00 Astana, Dhaka eTzSriLanka +06:00 Sri Jayawardenepura eTzMyanmar +06:30 Rangoon eTzSEAsia +07:00 Bangkok, Hanoi, Jakarta eTzNorthAsia +07:00 Krasnoyarsk eTzChina +08:00 Beijing, Chongqing, Hong Kong, Urumqi eTzNorthAsiaEast +08:00 Irkutsk, Ulaan Bataar eTzMalayPeninsula +08:00 Kuala Lumpur, Singapore eTzWAustralia +08:00 Perth eTzTaipei +08:00 Taipei eTzTokyo +09:00 Osaka, Sapporo, Tokyo eTzKorea +09:00 Seoul eTzYakutsk +09:00 Yakutsk eTzCenAustralia +09:30 Adelaide eTzAUSCentral +09:30 Darwin eTzEAustralia +10:00 Brisbane eTzAUSEastern +10:00 Canberra, Melbourne, Sydney eTzWestPacific +10:00 Guam, Port Moresby eTzTasmania +10:00 Hobart eTzVladivostok +10:00 Vladivostok eTzCentralPacific +11:00 Magadan, Solomon Is., New Caledonia eTzNewZealand +12:00 Auckland, Wellington eTzFiji +12:00 Fiji, Kamchatka, MarshallIs. eTzTonga +13:00 Nuku'alofa Additional information: Controls the time zone, which can be chosen from a list of time zones similar to the one used by Microsoft Windows operating system: eTzDateline -12:00 International Date Line West eTzSamoa -11:00 Midway Island, Samoa eTzHawaiian -10:00 Hawaii eTzAlaskan -09:00 Alaska eTzPacific -08:00 Pacific Time (US & Canada); Tijuana eTzUSMountain -07:00 Arizona eTzMexico2 -07:00 Chihuahua, La Paz, Mazatlan eTzMountain -07:00 Mountain Time (US & Canada) eTzCentralAmerica -06:00 Central America eTzCentral -06:00 Central Time (US & Canada) eTzMexico -06:00 Guadalajara, Mexico City, Monterrey eTzCanadaCentral -06:00 Saskatchewan eTzSAPacific -05:00 Bogota, Lima, Quito eTzEastern -05:00 Eastern Time (US & Canada) eTzUSEastern -05:00 Indiana (East) eTzAtlantic -04:00 Atlantic Time (Canada) eTzSAWestern -04:00 Caracas, La Paz eTzPacificSA -04:00 Santiago eTzNewfoundland -03:30 Newfoundland eTzESouthAmerica -03:00 Brasilia eTzSAEastern -03:00 Buenos Aires, Georgetown eTzGreenland -03:00 Greenland eTzMidAtlantic -02:00 Mid-Atlantic eTzAzores -01:00 Azores eTzCapeVerde -01:00 Cape Verde Is. eTzGreenwich 00:00 Casablanca, Monrovia eTzGMT 00:00 Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London eTzWEurope +01:00 Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna eTzCentralEurope +01:00 Belgrade, Bratislava, Budapest, Ljubljana, Prague eTzRomance +01:00 Brussels, Copenhagen, Madrid, Paris eTzCentralEuropean +01:00 Sarajevo, Skopje, Warsaw, Zagreb eTzWCentralAfrica +01:00 West Central Africa eTzGTB +02:00 Athens, Beirut, Istanbul, Minsk eTzEeurope +02:00 Bucharest eTzEgypt +02:00 Cairo eTzSouthAfrica +02:00 Harare, Pretoria eTzFLE +02:00 Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius eTzJerusalem +02:00 Jerusalem eTzArabic +03:00 Baghdad eTzArab +03:00 Kuwait, Riyadh eTzRussian +03:00 Moscow, St. Petersburg, Volgograd eTzEAfrica +03:00 Nairobi eTzIran +03:30 Tehran eTzArabian +04:00 Abu Dhabi, Muscat eTzCaucasus +04:00 Baku, Tbilisi, Yerevan eTzAfghanistan +04:30 Kabul eTzEkaterinburg +05:00 Ekaterinburg eTzWestAsia +05:00 Islamabad, Karachi, Tashkent eTzIndia +05:30 Chennai, Kolkata, Mumbai, New Delhi eTzNepal +05:45 Kathmandu eTzNCentralAsia +06:00 Almaty, Novosibirsk eTzCentralAsia +06:00 Astana, Dhaka eTzSriLanka +06:00 Sri Jayawardenepura eTzMyanmar +06:30 Rangoon eTzSEAsia +07:00 Bangkok, Hanoi, Jakarta eTzNorthAsia +07:00 Krasnoyarsk eTzChina +08:00 Beijing, Chongqing, Hong Kong, Urumqi eTzNorthAsiaEast +08:00 Irkutsk, Ulaan Bataar eTzMalayPeninsula +08:00 Kuala Lumpur, Singapore eTzWAustralia +08:00 Perth eTzTaipei +08:00 Taipei eTzTokyo +09:00 Osaka, Sapporo, Tokyo eTzKorea +09:00 Seoul eTzYakutsk +09:00 Yakutsk eTzCenAustralia +09:30 Adelaide eTzAUSCentral +09:30 Darwin eTzEAustralia +10:00 Brisbane eTzAUSEastern +10:00 Canberra, Melbourne, Sydney eTzWestPacific +10:00 Guam, Port Moresby eTzTasmania +10:00 Hobart eTzVladivostok +10:00 Vladivostok eTzCentralPacific +11:00 Magadan, Solomon Is., New Caledonia eTzNewZealand +12:00 Auckland, Wellington eTzFiji +12:00 Fiji, Kamchatka, Marshall Is. eTzTonga +13:00 Nuku'alofa |
| INT scan_to_folder_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.89 | INTEGER | read-only | The number of scan-to-folder scan jobs. Additional information: The number of scan-to-folder scan jobs. |
| OCT scanned_media_duplex_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2.1.4 | OCTET STRING | read-write | Charge for each duplex page scanned, for this media size. Additional information: Setting this object has the effect of also altering the corresponding value for SCANNED-MEDIA-SIMPLEX-CHARGE with exactly half the value of the Duplex charge. Since the simplex charge is always half the duplex charge - this means that the first decimal place of the duplex charge must be evenly divisible by 2. This means that a Set operation to this object with a value of 2.3 will generate a PML response of OK_NEAREST_LEGAL_VALUE_SUBSTITUTED and the value written will snap to 2.2. The simplex charge will also take on a value of 1.1. The snap behavior for this object will always be as follows based on the first decimal place: if even then accept, otherwise snap to the next lower tenth. |
| INT scanned_media_duplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2.1.3 | INTEGER | read-only | Total number of duplex pages scanned, for this media size. |
| OCT scanned_media_simplex_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2.1.2 | OCTET STRING | read-write | Charge for each simplex page printed in this media size. Additional information: This is a volatile set of charge values that will always reset to the default values after a power-cycle. The default values represent a ratio of the page size as compared to a letter or A4 page size. Setting this object has the effect of altering SCANNED-MEDIA-DUPLEX-CHARGE to have a value that is twice that of the simplex charge. |
| INT scanned_media_simplex_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2.1.1 | INTEGER | read-only | Total number of simplex pages scanned, for this media size. Additional information: The 5 usage (simplex/duplex count, simplex/duplex click charge and paper size total) objects described here and below detail the usage for the scanner for each paper size defined in the PCL Implementor's Guide and in the Media Size Table in the hpmib.txt. The OID binding is based on the click attribute and paper size. For example: The format for the OID is as follows: 3.4.1.5.x.y | | | | \ / | paper size / \ PRINTER-CLICK_TOTALS ROOT \ OID click attribute 1..5 x values are 1..5: 1) simplex count 2) simplex click charge 3) duplex count 4) duplex click charge 5) printer or scanner paper size total (i.e. depends if the root OID is referrring to the printer or scanner). y : paper size as defined in the Media Size Table in the hpmib.txt The click charge objects are of data type real and have a single digit of precision. Setting these objects to more than a single digit of precision will cause truncation at a single digit, for example, if click charge is set to 15.475 and later retrieved with a get, the value will be 15.400 for this object. |
| OCT scanned_media_total_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2.1.5 | OCTET STRING | read-only | The total charge for pages scanned, for this media size. |
| scanned_media_usage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2.1 | |||
| scanner | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2 | |||
| INT scanner_accessory_adf_one_sided_sheet_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.59 | INTEGER | read-only | This item is incremented by 1 for each sheet that is scanned through the ADF in 1-sided scan mode. Additional information: The value will be updated at the end of every scan job. |
| INT scanner_accessory_adf_sheet_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.20 | INTEGER | read-only | Total number of sheets that have been fed through the Automatic Document Feed (ADF) accessory. Additional information: The Automatic Document Feed (ADF) count is incremented each time a sheet feeds through the ADF. The value will be updated at the end of every scan job. |
| INT scanner_accessory_adf_two_sided_sheet_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.60 | INTEGER | read-only | This item is incremented by 2 for each sheet that is scanned through the ADF in 2-sided scan mode. Additional information: The value will be updated at the end of every scan job. |
| INT scanner_accessory_copy_job_scan_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.61 | INTEGER | read-only | This relates to the number of pages scanned for copying. This item is incremented by 2 for each sheet scanned through the ADF in 2-sided scan mode, and it is incremented by 1 for flatbed scans. Scanning for testing and calibration purposes are NOT TO BE INCLUDED in this count. Additional information: The value will be updated at the end of every scan job. |
| INT scanner_accessory_flatbed_scan_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.21 | INTEGER | read-only | Total number of scans performed by a flatbed scanner accessory. Additional information: The count is only incremented when a sheet is scanned on the FLATBED. The return value of this object will reset to the lower multiple of 10 at a power cycle. The value will be updated at the end of every scan job. |
| INT scanner_accessory_send_job_scan_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1.62 | INTEGER | read-only | This relates to the number of pages scanned for fax/send. This item is incremented by 2 for each sheet scanned through the ADF in 2-sided scan mode, and it is incremented by 1 for flatbed scans. Scanning for testing and calibration purposes are NOT TO BE INCLUDED in this count. Additional information: The value will be updated at the end of every scan job. |
| scanner_accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2 | |||
| security | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.23 | |||
| OCT serial_number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.3.3 | OCTET STRING | read-only | 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 > 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. |
| OCT service_id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.19 | OCTET STRING | read-write | A read of this object will return the current SERVICE ID value in the printer. The format is 'YYDDD' where: YY = calendar year - 1990 DDD = (calendar month - 1) * 30 + (calendar day of the month or 30, if > 30) A write of this object will only succeed if the MANUFACTURING-CONTROL PML object has been set with the correct >. If the write operation is not allowed, this object will return an status. Additional information: Setting the > object will enable setting this object. |
| settings_fax_proc_sub | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.1 | |||
| settings_file_system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.10.1 | |||
| settings_intray | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1 | |||
| settings_io | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.1.1 | |||
| settings_job | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.6.1 | |||
| settings_mass_storage_bd | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.1 | |||
| settings_outbin | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.4.1 | |||
| settings_pdl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.1 | |||
| settings_ph | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.7.1 | |||
| settings_print_media | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.8.1 | |||
| settings_prt_eng | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.1 | |||
| settings_rpc | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.1 | |||
| settings_scanner | 1.3.6.1.4.1.11.2.3.9.4.2.1.2.2.1 | |||
| settings_security | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.23.1 | |||
| settings_system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1 | |||
| settings_web_server | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.6.1 | |||
| settings_webserver | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.9.1 | |||
| INT show_address | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.20.1.3 | INTEGER | read-write | If this object is set to eAuto, and the device has an IP address, the IP address of the device will be shown with the READY message. If this object is set to eOff, the IP address will not be shown. |
| INT sleep_mode | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.1.2 | INTEGER | read-write | Returns eTrue if the device is in energy saving sleep mode, otherwise returns eFalse. Setting SLEEP-MODE to eFalse causes the device to wake up, if it is in sleep mode. Setting SLEEP-MODE to eTrue causes the device to go into sleep mode. Additional information: This object returns eTrue if the device is in energy saving sleep mode, otherwise it returns eFalse. Setting this object to eTrue while the printer is awake will not change the printer's current state and will return status. NOTE: This object should behave this way when the printer does not have an instant-on fuser. Setting this object to eTrue while printer is already in Sleep Mode will not change the printer's current state and will return status. Setting this object to eFalse while printer is already awake will not change the printer's current state and will return status. Setting this object to eFalse while the printer is asleep causes the device to wake up. |
| source_subsystem | 1.3.6.1.4.1.11.2.3.9.4.2.1.2 | |||
| source_tray_accounting | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.5 | |||
| source_tray_usage | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.5.1 | |||
| INT source_tray_usage_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.5.1.1 | INTEGER | read-only | Total number of pages printed from this source tray. Additional information: This object will track how many images have been printed with the original source tray as one of the following: 1. Envelope Feeder 2. Manual Feed Tray 3. Tray 1 4. Tray 2 5. Tray 3 6. Tray 4 7. Tray 5 8. External Tray 9. Other |
| INT source_tray_usage_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.10 | INTEGER | read-only | This object reports the total source tray usage for the life of the printer. This value is reported on the usage page. |
| status_fax_proc_sub | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.7.2 | |||
| status_mass_storage_bd | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.15.2 | |||
| status_pdl | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.3.2 | |||
| status_prt_eng | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2 | |||
| status_rpc | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.13.2 | |||
| status_system | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2 | |||
| INT supports_pjl_user_groups | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.23.1.1 | INTEGER | read-only | Returns eTrue if the device is able to process PJL user group variables. See the PJL Technical Reference for the proper syntax for setting these variables. Because there may be many user groups in some environments, this object allows a client application to optimize the print job by including user groups only when the device is able to process them. Additional information: This device will always return eTrue. |
| INT time_display | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.28 | INTEGER | read-write | Controls front-panel time display format. Set to eTimeDisplayTwelveHour for AM/PM display. Set to eTimeDisplayTwentyFourHour for military-type display. Additional information: Controls front-panel time display format. Set to eTimeDisplayTwelveHour for AM/PM display. Set to eTimeDisplayTwentyFourHour for military-type display. |
| OCT timestamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.2.13 | OCTET STRING | write-only | Sets the printer's current time in (UTC). The format of the string is 'YYYYMMDDHHMMSS'. Where YYYY is the year. MM is the month (1-12) DD is the day of the month (1-31) HH is the hour of the day (0-23) MM is the minutes (0-59) SS is the seconds (0-59) Device POS must specify the conditions for setting this object. |
| INT total_color_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.7 | INTEGER | read-only | Total number of color pages printed by the device. Additional information: Total number of color pages printed by the device. The valid range of this object is 0 to 2^24-1. When the number of color pages printed exceeds the maximum color page count, the value will roll to zero. A duplexed sheet of media will cause the counter to be incremented by two. |
| INT total_engine_page_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.2.5 | INTEGER | read-write | Total number of pages printed by the device. POS indicates if the total engine page count is kept in NVRAM, and the maximum supported value before the page count rolls over to zero. Additional information: nothing beyond old description |
| INT tray_disable_use_instead | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.7.1.1 | INTEGER | read-write | If this object is set to eEnabled, the paper mount message that is normally posted('To use another tray....') is turned off thereby disallowing the user to specify another tray from which paper can be taken for printing. However, on setting this object to eDisabled the paper mount message is posted allowing the user to specify another tray for paper feed. Additional information: The feature provides a menu item under TRAY BEHAVIOUR, i.e USE ANOTHER TRAY which has two options ENABLED and DISABLED. Whenever the menu item is set to ENABLED, it provides the user with the ability to select another tray from which paper could be provided for the job. However on selecting DISABLED forces the user to provide paper through the same tray, after the paper mount message is posted, in either cases. |
| INT tray_prompt | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.1.19 | INTEGER | read-write | If this object is set to eDisplay, whenever a paper tray is opened, refilled, and closed in a printer, the end user is prompted with a message 'To change size or type press check' on the control panel. If this object is set to eDoNotDisplay, then the end user will not be prompted with this message whenever a paper tray is opened, refilled, and closed in a printer. Additional information: Whenever a paper tray is opened and closed, the user is provided with two options Display and Do Not Display, through the menu item Size/Type Prompt.On selecting Display he chooses to get prompted with the message to change the size or type of paper. Whereas he is not prompted with this message in case he chooses Do Not Display. |
| INT tray1_media_size_loaded | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.1.1 | INTEGER | read-write | Returns the media size that is currently configuredconfigured in tray #1. This object can be set to indicate the media size currently loaded, if the printer supports input trays that can not sense the media size. Complete list of supported media sizes along with their dimensions are listed in the ''Media Size Table'' near the end of this document. Additional information: Returns the media size that is currently configuredconfigured in tray #1. This object can be set to indicate the media size currently loaded, if the printer supports input trays that can not sense the media size. Complete list of supported media sizes along with their dimensions are listed in the ''Media Size Table'' near the end of this document. |
| INT tray1_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.1.12 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray. |
| INT tray2_media_size_loaded | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.2.1 | INTEGER | read-write | Returns the media size that is currently configured in tray #2. Complete list of supported media sizes along with their dimensions are listed in the ''Media Size Table'' near the end of this document. Additional information: Returns the media size that is currently configured in tray #2. |
| INT tray2_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.2.12 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray. |
| INT tray3_media_size_loaded | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.3.1 | INTEGER | read-write | Returns the media size that is currently configured in tray #3. Complete list of supported media sizes along with their dimensions are listed in the ''Media Size Table'' near the end of this document. Additional information: Returns the media size that is currently configured in tray #3. |
| INT tray3_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.3.12 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray. |
| INT tray5_media_size_loaded | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.5.1 | INTEGER | read-write | Returns the media size that is currently configured in tray #5. Complete list of supported media sizes along with their dimensions are listed in the ''Media Size Table'' near the end of this document. Additional information: Returns the media size that is currently configured in tray #5. |
| INT tray5_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.5.12 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray. |
| INT tray6_media_size_loaded | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.6.1 | INTEGER | read-write | Returns the media size that is currently configured in tray #5. Complete list of supported media sizes along with their dimensions are listed in the ''Media Size Table'' near the end of this document. Additional information: Returns the media size that is currently configured in tray #5. |
| INT tray6_phd | 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.3.3.6.12 | INTEGER | read-only | Provides the number of the Paper Handling Device that contains this input tray. Additional information: Provides the number of the Paper Handling Device that contains this input tray. |
| upgradable_devices | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20 | |||
| INT upgradable_devices_current_state | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.4 | INTEGER | read-only | Provides the current or last reportable state of the device upgrade process. The current state may not necessarily be the current state, but could be the post-mortem state. |
| INT upgradable_devices_max_write_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.5 | INTEGER | read-only | Reports the manufacturer specified number of times that firmware for device X can be downloaded to the flash part. A value of -1 means that there is no limit. A value of 0 means that downloading firmware is not permitted by this part. Any other positive integer value corresponds to the number of times that the firmware for device X can be downloaded to the flash part. The current maximum write count is 500. This may change as flash technology evolves. |
| OCT upgradable_devices_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.6 | OCTET STRING | read-only | This returns the name of the upgradable device. This should match the name in the header of the upgrade image being sent to the flash part. If the name does not match with any of the names returned then the device that we are attempting to upgrade is unavailable for upgrading. Additional information: This object returns the HP name of the printer and the upgradable devices. There is one Name object per upgradable device. This should match what is in the PJL header of the RFU job Web Jet Admin uses this to ensure the printer or device is available to be upgraded. |
| OCT upgradable_devices_version | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.7 | OCTET STRING | read-only | This object will return a string value representing the current revision of firmware that device X is operating with. This is used to determine if code needs to be upgraded when a firmware bundle comes in, in an upgrade job. Additional information: Web Jet Admin uses the version string that is returned to determine what peices of an RFU bundle need to be upgraded when an RFU job is being built. This internal object will return the current version string of the printer or device that it corresponds to. |
| INT upgradable_devices_write_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.3 | INTEGER | read-only | Tells the number of times that firmware for device X has been downloaded to the flash part. The default value will vary depending on how many times the firmware is rolled before shipping. |
| INT upgradable_devices_write_status_supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.1 | INTEGER | read-only | This object provides information on whether the upgradable device has the ability to communicate the write-status of the upgrade while the upgrade is taking place. |
| INT upgradable_devices_write_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.20.2 | INTEGER | read-only | If the design of the device upgrade implementation does not allow PML interaction during the download process, this value provides an estimation of the time where the device will not be able to engage in PML communication. The time returned will depend upon what device is attempting to be upgraded. |
| OCT usage_instructions_line1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.5 | OCTET STRING | read-write | The first line of usage instructions for the device user.Appears on Line 1 of the usage page. |
| OCT usage_instructions_line2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.6 | OCTET STRING | read-write | The second line of usage instructions for the device user.Appears on Line 1 of the usage page. |
| OCT usage_instructions_line3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.7 | OCTET STRING | read-write | The third line of usage instructions for the device user.Appears on Line 1 of the usage page. |
| OCT usage_instructions_line4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.8 | OCTET STRING | read-write | The fourth line of usage instructions for the device user.Appears on Line 1 of the usage page. |
| OCT usage_printer_color_total_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.13 | OCTET STRING | read-only | Total printer charge for all paper sizes printed in color only. Additional information: This is the total charge over the range of all supported media sizes for duplex and simplex color pages. |
| INT usage_printer_mono_dimplex_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.17 | INTEGER | read-only | This object reports the total of monochrome dimplex pages printed on this device. This value is the sum of all PRINTED-MEDIA-DIMPLEX-COUNT.n counter values. |
| INT usage_printer_mono_duplex_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.16 | INTEGER | read-only | This object reports the total of monochrome duplex pages printed on this device. This value is the sum of all PRINTED-MEDIA-DUPLEX-COUNT.n counter values. |
| INT usage_printer_mono_simplex_total | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.15 | INTEGER | read-only | This object reports the total of monochrome simplex pages printed on this device. This value is the sum of all PRINTED-MEDIA-SIMPLEX-COUNT.n counter values. |
| OCT usage_printer_mono_total_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.12 | OCTET STRING | read-only | Total printer charge for all paper sizes printed in monochrome only. Additional information: This is the total charge over the range of all supported media sizes for duplex and simplex mono pages. |
| OCT usage_printer_total_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.2 | OCTET STRING | read-only | Total printer charge for all paper sizes printed. |
| OCT usage_scanner_total_charge | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.2.2 | OCTET STRING | read-only | Total scanner charge or cost for all paper sizes scanned. |
| INT usage_staple_count | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.16.1.4 | INTEGER | read-only | Total number of staples used. |
| usb | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2 | |||
| INT usb_device_kind | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2.6 | INTEGER | read-only | The USB-DEVICE-KIND object classifies a USB device into one of four broad categories: \ eUSBStorageDevice(1): The USB device is strictly a device for storing data. \ eUSBNonStorageDevice(2): The USB device has no storage capability (e.g., a card reader). \ eUSBCompositeDevice(3): The USB device has storage capability and additional functionality normally not associated with a storage device. \ eUSBUnsupportedDevice(4): The USB device was detected, but no driver exists for the device or the device draws more current than allowed. \ |
| OCT usb_driver_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2.7 | OCTET STRING | read-only | Returns the name of the low-level USB driver supporting this device. |
| INT usb_host_supported | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.1 | INTEGER | read-only | The USB Host protocol is supported by the device when the value returned is eTrue. The USB Host protocol is not supported when the value returned is eFalse. |
| usb_interface | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9 | |||
| OCT usb_manufacturer_name | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2.2 | OCTET STRING | read-only | Returns the description of the manufacturer of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0. |
| OCT usb_product_description | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2.3 | OCTET STRING | read-only | Returns the product description of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0. |
| INT usb_product_id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2.5 | INTEGER | read-only | Returns the Product ID of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0. The value will be in the range 0..65535. |
| OCT usb_serial_number | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2.1 | OCTET STRING | read-only | Returns the serial number of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0. |
| INT usb_vendor_id | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.9.2.4 | INTEGER | read-only | Returns the Vendor ID of a connected USB device as defined in the Standard Device Descriptor of the Universal Serial Bus Specification Version 2.0. The value will be in the range 0..65535. |
| warning1 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.1 | |||
| INT warning1_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.1.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: Returns a device specific WARNING code. If the WARNING code returned is '0', then the printer has not yet logged an WARNING for this object. When the maximum number of WARNINGs is reached (30 on InkJet printers), and a new WARNING occurs, the WARNING in WARNING1-CODE will be replaced by the one in WARNING2-CODE, and so on until the last WARNING object will be given the value of the new WARNING. The WARNING number is returned in the upper 16 bits. If it is 68, 69, 79, or 80, then the sub code is returned in the lower 16 bits (eg. 68 001C, where the subcode is already a hexadecimal value). If the WARNING number is any other number, then the 1st sub code (XX) will be in bits 15-8 and the 2nd sub code (YY) will be in bits 7-0 (eg. 55.04.02) where XX=04 and YY=02). See the Control Panel ERS for specific information about the meaning of each code. Example: If the WARNING is 68 001A, then the value returned will be 4456474. To break it down: 4456474 = 0x0044001A The upper 16 bits: 0x0044 = 68 The lower 16 bits: 0x001A = 001A Which is the WARNING: 68 001A Example: If the WARNING is 55.04.241, then the WARNING code will be 3605745. To break it down: 3605745 = 0x003704F1 The upper 16 bits: 0x0037 = 55 The upper byte of the lower 16 bits: 0x04 = 04 The lower byte of the lower 16 bits: 0xF1 = 241 Which is the WARNING: 55.04.241 |
| OCT warning1_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.1.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: This item contains the date and the time when the WARNING occurred. It returns the date and the time at which the WARNING occured in hexadecimal. For instance, if date is 2004-Jul-13 and time is 03:15 am when the WARNING was logged, then we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month 07 0d(hex) - corresponds to date 13 03(hex) - corresponds to hour- 03 0f(hex) - corresponds to min- 15. If there is currently no WARNING entry , '00 00 00 00 00' will be returned. See WARNING1-CODE for an explanation of the order used for storing WARNINGs. |
| INT warning1_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.1.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 1 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: This item contains the engine page count when the WARNING occurred. If there is currently no WARNING entry for this object, a '0' will be returned. Note that '0' may also be returned when there is a valid WARNING, but a current page count was unavailable. If WARNING1-CODE object also returns '0', then an WARNING has not yet been logged for this object. See WARNING1-CODE for an explanation of the order used for storing WARNINGs. |
| warning10 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.10 | |||
| INT warning10_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.10.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning10_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.10.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning10_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.10.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 10 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning11 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.11 | |||
| INT warning11_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.11.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning11_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.11.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning11_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.11.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 11 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning12 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.12 | |||
| INT warning12_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.12.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning12_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.12.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning12_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.12.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 12 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning13 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.13 | |||
| INT warning13_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.13.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning13_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.13.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning13_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.13.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 13 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning14 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.14 | |||
| INT warning14_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.14.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning14_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.14.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning14_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.14.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 14 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning15 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.15 | |||
| INT warning15_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.15.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning15_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.15.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning15_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.15.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 15 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning16 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.16 | |||
| INT warning16_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.16.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning16_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.16.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning16_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.16.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 16 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning17 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.17 | |||
| INT warning17_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.17.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning17_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.17.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning17_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.17.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 17 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning18 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.18 | |||
| INT warning18_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.18.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning18_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.18.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning18_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.18.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 18 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning19 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.19 | |||
| INT warning19_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.19.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning19_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.19.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning19_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.19.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 19 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning2 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.2 | |||
| INT warning2_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.2.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning2_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.2.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning2_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.2.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 2 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning20 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.20 | |||
| INT warning20_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.20.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning20_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.20.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning20_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.20.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 20 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning21 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.21 | |||
| INT warning21_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.21.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning21_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.21.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning21_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.21.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 21 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning22 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.22 | |||
| INT warning22_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.22.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning22_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.22.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning22_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.22.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 22 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning23 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.23 | |||
| INT warning23_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.23.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning23_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.23.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning23_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.23.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 23 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning24 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.24 | |||
| INT warning24_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.24.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning24_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.24.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning24_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.24.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 24 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning25 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.25 | |||
| INT warning25_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.25.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning25_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.25.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning25_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.25.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 25 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning26 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.26 | |||
| INT warning26_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.26.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning26_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.26.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning26_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.26.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 26 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning27 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.27 | |||
| INT warning27_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.27.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning27_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.27.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning27_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.27.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 27 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning28 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.28 | |||
| INT warning28_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.28.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning28_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.28.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning28_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.28.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 28 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning29 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.29 | |||
| INT warning29_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.29.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning29_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.29.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning29_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.29.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 29 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning3 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.3 | |||
| INT warning3_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.3.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning3_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.3.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning3_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.3.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 3 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning30 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.30 | |||
| INT warning30_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.30.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning30_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.30.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning30_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.30.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 30 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning31 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.31 | |||
| INT warning31_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.31.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning31_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.31.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning31_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.31.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 31 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning32 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.32 | |||
| INT warning32_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.32.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning32_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.32.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning32_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.32.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 32 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning33 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.33 | |||
| INT warning33_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.33.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning33_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.33.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning33_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.33.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 33 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning34 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.34 | |||
| INT warning34_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.34.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning34_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.34.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning34_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.34.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 34 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning35 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.35 | |||
| INT warning35_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.35.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning35_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.35.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning35_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.35.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 35 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning36 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.36 | |||
| INT warning36_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.36.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning36_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.36.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning36_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.36.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 36 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning37 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.37 | |||
| INT warning37_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.37.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning37_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.37.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning37_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.37.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 37 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning38 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.38 | |||
| INT warning38_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.38.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning38_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.38.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning38_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.38.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 38 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning39 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.39 | |||
| INT warning39_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.39.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning39_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.39.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning39_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.39.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 39 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning4 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.4 | |||
| INT warning4_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.4.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning4_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.4.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning4_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.4.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 4 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning40 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.40 | |||
| INT warning40_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.40.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning40_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.40.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning40_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.40.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 40 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning41 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.41 | |||
| INT warning41_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.41.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning41_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.41.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning41_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.41.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 41 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning42 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.42 | |||
| INT warning42_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.42.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning42_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.42.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning42_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.42.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 42 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning43 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.43 | |||
| INT warning43_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.43.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning43_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.43.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning43_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.43.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 43 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning44 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.44 | |||
| INT warning44_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.44.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning44_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.44.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning44_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.44.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 44 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning45 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.45 | |||
| INT warning45_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.45.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning45_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.45.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning45_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.45.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 45 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning46 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.46 | |||
| INT warning46_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.46.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning46_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.46.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning46_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.46.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 46 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning47 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.47 | |||
| INT warning47_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.47.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning47_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.47.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning47_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.47.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 47 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning48 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.48 | |||
| INT warning48_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.48.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning48_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.48.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning48_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.48.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 48 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning49 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.49 | |||
| INT warning49_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.49.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning49_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.49.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning49_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.49.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 49 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning5 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.5 | |||
| INT warning5_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.5.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning5_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.5.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning5_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.5.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 5 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning50 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.50 | |||
| INT warning50_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.50.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning50_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.50.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning50_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.50.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 50 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning6 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.6 | |||
| INT warning6_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.6.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning6_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.6.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning6_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.6.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 6 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning7 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.7 | |||
| INT warning7_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.7.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning7_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.7.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning7_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.7.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 7 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning8 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.8 | |||
| INT warning8_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.8.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning8_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.8.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning8_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.8.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 8 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warning9 | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.9 | |||
| INT warning9_code | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.9.2 | INTEGER | read-only | Contains a device specific warning code. Each device POS should list what warnings are logged to the warning log and the meaning of each supported warning code value. Additional information: See WARNING1-CODE. |
| OCT warning9_date_time | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.9.3 | OCTET STRING | read-only | This item contains the date and the time at which an warning occurred. The values returned will be in hexadecimal. If the date is 2004-Jul-13 and the time is 03:15 a.m., we get 04 07 0d 03 0f where, 04 (hex) - corresponds to the year 2004. 07 (hex) - corresponds to month, 07 0d (hex) - corresponds to date, 13 03 (hex) - corresponds to hour, 3 a.m. 0f (hex) - corresponds to min, 15. Additional information: See WARNING1-DATE-TIME. |
| INT warning9_time_stamp | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22.9.1 | INTEGER | read-only | Contains some sort of time stamp indicating when warning 9 occurred. Example time stamps include the actual time the warning occurred (in seconds since Jan. 1, 1970), and the total engine page count. The device POS documents the meaning of the time stamp. Additional information: See WARNING1-TIME-STAMP. |
| warninglog | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.22 | |||
| INT web_proxy_config_enable | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.6.1.4 | INTEGER | read-only | This object is a binary enumeration which the peripheral uses to inform the JetDirect card that the Jet-Direct card embedded web server should display the web proxy configuration settings. The Jet Direct card web server will display the if and only if this object is both implemented and set to eOn. A peripheral may implement this object in order to have another host, like a JetDirect card, include a reference to the peripheral's web content. The peripheral will read the proxy configuration using the XIP2 sysInfo Get methods. |
| web_server | 1.3.6.1.4.1.11.2.3.9.4.2.1.1.4.6 | |||
| OCT web_server_security | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.9.1.3 | OCTET STRING | read-write | Each collection bit represents a device or Embedded Web Server feature that can be enabled or disabled via this object. |
| OCT web_server_url | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.9.1.2 | OCTET STRING | read-write | A Universal Resource Locator (URL) from which the Embedded Web Server can be configured. Any limitation on the size of this URL will be specified in the device POS. |
| webserver_proc_sub | 1.3.6.1.4.1.11.2.3.9.4.2.1.3.9 |
RFC description
HP Inkjet IJ8060 printer model-specific MIB for JetDirect networked device management.
Start monitoring HP-compatible printer/multifunction device (IJ8060 print engine) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.