idnits 2.17.1 draft-ietf-printmib-printer-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 129 form feeds but 862 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 105 instances of too long lines in the document, the longest one being 6 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 52 has weird spacing: '... system prin...' == Line 53 has weird spacing: '...manager opera...' == Line 314 has weird spacing: '...e media that ...' == Line 363 has weird spacing: '... set of chara...' == Line 424 has weird spacing: '...ify the indep...' == (27 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 19, 1994) is 10843 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 11 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 draft Printer MIB August 19, 1994 4 Printer MIB Internet-Draft 5 7 Status of this Memo 9 This document is an Internet-Draft. Internet-Drafts are working 10 documents of the Internet Engineering Task Force (IETF), its 11 areas, and its working groups. Note that other groups may also 12 distribute working documents as Internet-Drafts. 14 Internet-Drafts are draft documents valid for a maximum of six 15 months and may be updated, replaced, or obsoleted by other 16 documents at any time. It is inappropriate to use Internet- 17 Drafts as reference material or to cite them other than as 18 ``work in progress.'' 20 To learn the current status of any Internet-Draft, please check 21 the ``1id-abstracts.txt'' listing contained in the Internet- 22 Drafts Shadow Directories on ds.internic.net (US East Coast), 23 nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or 24 munnari.oz.au (Pacific Rim). 26 Please send comments about this document to the mailing list: 27 pmi@hpbs907.boi.hp.com. 29 All trademarks and registered trademarks are the property of their 30 respective owners. 32 draft Printer MIB August 19, 1994 34 1. Introduction 36 1.1. Network Printing Environment 38 The management of producing a printed document, in any computer environ- 39 ment, is a complex subject. Basically, the task can be divided into two 40 overlapping pieces, the management of printing and the management of the 41 printer. Printing encompasses the entire process of producing a printed 42 document from generation of the file to be printed, selection of a 43 printer, choosing printing properties, routing, queuing, resource 44 management, scheduling, and final printing including notifying the user. 45 Most of the printing process is outside the scope of the model presented 46 here; only the management of the printer is covered. 48 draft Printer MIB August 19, 1994 50 Figure 1 - One Printer's View of the Network 52 system printer asset user user user 53 manager operator manager 54 O O O O O O 55 /|\ /|\ /|\ /|\ /|\ /|\ 56 / \ / \ / \ / \ / \ / \ 57 | | | | | | 58 +---------+ +-------+ +-------+ +-------+ +-----------+ +-----------+ 59 |configur-| |printer| | asset | |printer| | user | | user | 60 |ator | |manager| |manager| |browser| |application| |application| 61 +---------+ +-------+ +-------+ +-------+ +-----------+ +-----------+ 62 ^ ^ ^ ^ | | 63 |R/W |R/W |R |R +-----------+ +-----------+ 64 | | | | | spooler | | spooler | 65 | | | | +-----------+ +-----------+ 66 | | | | | | 67 | | | | +-----------+ +-----------+ 68 | | | | |supervisor | |supervisor | 69 | | | | +-----------+ +-----------+ 70 | | | | ^ ^ ^ ^ 71 | | | | |R |R/W |R |R/W 72 v v | | | | | | 73 ================================================== | ===== | 74 | print| print| 75 |SNMP data| data| 76 +-----+ +-------+ PCL| PCL| 77 | MIB |<------>| agent | PostScript| PostScript| 78 +-----+ +-------+ NPAP| NPAP| 79 |unspecified etc.| etc.| 80 +=============+ +-----------------+ | | 81 | |--|channel/interface|<--+ | 82 | | +-----------------+ | 83 | PRINTER | | 84 | | +-----------------+ | 85 | |--|channel/interface|<----------------+ 86 +=============+ +-----------------+ 88 1.2. Printer Device Overview 90 A printer is the physical device that takes media from an input source, 91 produces marks on that media according to some page description or page 92 control language and puts the result in some output destination, possi- 93 bly with finishing applied. Printers are complex devices that consume 94 draft Printer MIB August 19, 1994 96 supplies, produce waste and have mechanical problems. In the management 97 of the physical printing device the description, status and alert infor- 98 mation concerning the printer and its various subparts has to be made 99 available to the management application so that it can be reported to 100 the end user, key operators for the replenishment of supplies or the 101 repair or maintenance of the device. The information needed in the 102 management of the physical printer and the management of a printing job 103 overlap highly and many of the tasks in each management area require the 104 same or similar information . 106 1.3. Categories of Printer Information 108 Information about printers is classified into three basic categories, 109 descriptions, status and alerts. 111 1.3.1. Descriptions 113 Descriptions convey information about the configuration and capabilities 114 of the printer and its various sub-units. This information is largely 115 static information and does not generally change during the operation of 116 the system but may change as the printer is repaired, reconfigured or 117 upgraded. The descriptions are one part of the visible state of the 118 printer where state means the condition of being of the printer at any 119 point in time. 121 1.3.2. Status 123 Status is the information regarding the current operating state of the 124 printer and its various sub-units. Status is the rest of the visible 125 state of the printer. As an example of the use of status, a management 126 application must be able to determine if the various sub-units are ready 127 to print or are in some state that prevents printing or may prevent 128 printing in the future. 130 1.3.3. Alerts 132 An Alert is the representation of a reportable event in the printer. An 133 event is a change in the state of the printer. Some of those state 134 changes are of interest to a management application and are therefore 135 reportable. Typically, these are the events that affect the printer's 136 ability to print. Alerts usually occur asynchronously to the operation 137 draft Printer MIB August 19, 1994 139 of the computer system(s) to which the printer is attached. For conveni- 140 ence below, "alert" will be used for both the event caused by a change 141 in the printer's state and for the representation of that event. 143 Alerts can be classified into two basic categories, critical and non- 144 critical. A critical alert is one that is triggered by entry into a 145 state in which the printer is stopped and printing can not continue 146 until the condition that caused critical alert is eliminated. "Out of 147 paper", "toner empty" and "output bin full" are examples of critical 148 alerts. Non-critical alerts are triggered by those events that enter a 149 state in which printing is not stopped. Such a non-critical state may, 150 at some future time, lead to a state in which printing may be stopped. 151 Examples of this kind of non-critical alerts are "input media low", 152 "toner low" and "output bin nearly full". Or, a non-critical alert may 153 simply provide information, such as signaling a configuration changed in 154 the printer. 156 Description, status and alert information about printer can be thought 157 of as a data base describing the printer. The management application for 158 a printer will want to view the printer data base differently depending 159 on how and for what purposes the information in the data base is needed. 161 2. Printer Model 163 In order to accomplish the management of the printer, an abstract model 164 of the printer is needed to represent the sub-units from which the 165 printer is composed. A printer can be described as consisting of 13 166 types of sub-units. It is important to note that the sub-units of a 167 printer do not necessarily relate directly to any physically identifi- 168 able mechanism. Sub-units can also be a set of definable logical 169 processes, such as interpreters for page description languages or com- 170 mand processors that set various operating modes of the printer. 172 Figure 2 shows a block diagram of the printer and its basic 13 sub- 173 units. 175 draft Printer MIB August 19, 1994 176 draft Printer MIB August 19, 1994 178 Figure 2 - Printer Block Diagram 180 Physical Connections 181 | 182 +-----------+ 183 | | 184 +-------------+ | 185 | Interface |-+ 186 | (RFC1213) | 187 +-------------+ 188 | 189 +-----------+ 190 | | 191 +-------------+ | +-----------+ 192 | Channel |-+ | Operator | 193 | | | Console | 194 +-------------+ +-----------+ 195 | 196 +-----------+ +---------+ 197 | | | | 198 +-----------+ +-------------+ | +-----------+ | 199 | General | | Interpreter |-+ | Alerts |-+ 200 | Printer | | | | | 201 +-----------+ +-------------+ +-----------+ 202 | 203 +-------------------------------+ 204 | System Controller | 205 | (This is the Host MIB) | 206 +-------------------------------+ 208 +------+ +--------+ +--------+ 209 | | | | | | 210 +-------+ | +-------+ +---------+ | +-------+ +--------+ | 211 | Input |-+ +--------+| | Marker |-+ +--------+| | Output |-+ 212 | |===>| |+<==>| |<==>| |+==>| | 213 +-------+ +--+ +--+ +---------+ +--+ +--+ +--------+ 214 \ | || | || \ 215 \ | || | || \ 216 \ | || | || \ 217 +--------+ | |+-------------------------| || +---------+ 218 | | | +--------------------------+ || | | 219 +----------+ | | Media Path |+ +----------+ | 220 | Media |-+ +--------------------------------+ | Finisher |-+ 221 |(optional)| |(optional)| 222 draft Printer MIB August 19, 1994 224 +----------+ +----------+ 226 2.1. Overview of the Printer Model 228 The model has three basic parts: (1) the flow of a print file into an 229 interpreter and onto the marker, (2) the flow of media through the 230 marker and (3) the auxiliary sub-units that control and facilitate the 231 two prior flows. The flow of the print data comes through a physical 232 connection on which some form of transport protocol stack is running. 233 The data provided by the transport protocol (interface) appears on a 234 channel which is the input to an interpreter. The interpreter converts 235 the print data into a form suitable for marking on the media. 237 The media resides in Input sub-units from which the media is selected 238 and then transported via a Media Path first to a Marking sub-unit and 239 then onto an Output sub-unit with (optionally) some finishing operations 240 being performed. The auxiliary sub-units facilitate control of the 241 printer, inquiry/control of the operator panel, reporting of alerts, and 242 the adaptation of the printer to various natural languages and charac- 243 ters sets. All the software sub-units run on the System Controller which 244 represents the processor, memory and storage systems of the Printer. 245 Each of the sub-units is discussed in more detail below. 247 All of the sub-units other than the Alerts report only state informa- 248 tion, either a description or a status. The Alerts sub-unit reports 249 event information. 251 2.2. Printer Sub-Units 253 A printer is composed of 13 types of sub-units, called groups. The fol- 254 lowing sections describe the different types of sub-units. 256 2.2.1. General Printer 258 The general printer sub-unit is responsible for the overall control and 259 status of the printer. There is exactly one general printer sub-unit in 260 a printer. The general printer sub-unit is represented by the General 261 Printer Group in the model. In addition to the providing the status of 262 the whole printer and allowing the printer to be reset, this Group pro- 263 vides information on the status of the packaging of the printer, in par- 264 ticular, the covers. The general printer sub-unit is usually implemented 265 on the system controller. 267 draft Printer MIB August 19, 1994 269 The localization portion of the general printer sub-unit is responsible 270 for identifying the natural language, country, and character set in 271 which character strings are expressed. There may be one or more locali- 272 zations supported per printer. The available localizations are 273 represented by the Localization table. Localization is only performed 274 on those strings in the MIB that are explicitely marked as being local- 275 ized. All other character strings are returned in ASCII. 277 The character set portion of the general printer sub-unit is responsible 278 for identifying the possible character sets that are used by the inter- 279 preters, the operator console, and in network management requests for 280 display objects. There may be one or more character sets per printer. 281 The understood character sets are represented by the Character Set 282 Table. 284 2.2.2. Inputs 286 Input sub-units are mechanisms that feed media to be marked on into the 287 printer. A printer contains one or more input sub-units. These are 288 represented by the Input Group in the model. The model does not distin- 289 guish fixed input bins from removable trays, except to report when a 290 removable tray has been removed. 292 There are as many input sub-units as there are distinctly selectable 293 input "addresses". For example, if a tray has an option for manually 294 feeding paper as well as automatically feeding from the tray, then this 295 is two input sub-units if these two sources can be (must be) separately 296 selected and is one input sub-unit if putting a sheet in the manual feed 297 slot overrides feeding from the contents of the tray; that is, in the 298 second case there is no way to separately select or address the manual 299 feed slot. 301 2.2.3. Media 303 An input sub-unit can hold one or more instances of the media on which 304 marking is to be done. Typically, there is a large set of possible media 305 that can be associated with an input. The Media Group is an extension of 306 the Input Group which represents that media that is in an input sub- 307 unit. The Media Group only describes the current contents of each input 308 and not the possible content of the input sub-unit. 310 draft Printer MIB August 19, 1994 312 2.2.4. Outputs 314 Output sub-units are mechanisms that receive media that has been marked 315 on. A printer contains one or more output mechanisms. These are 316 represented by the Output Group in the model. The model does not distin- 317 guish fixed output bins from removable output bins, except to report 318 when a removable bin has been removed. 320 There are as many output sub-units as there are distinctly selectable 321 output "addresses". Output sub-units can be addressed in two different 322 ways: (1) as a set of "mailboxes" which are addressed by a specific 323 mailbox selector such as a bin number or a bin name, or (2) as a set of 324 "slots" into which multiple copies are collated. Sometimes both modes of 325 using the output sub-units can be used on the same printer. All that is 326 important from the viewpoint of the model is that the output units can 327 be separately selected. 329 2.2.5. Finishers 331 A finisher is a sub-unit that performs some operations on the media 332 other than marking. The finisher sub-units are represented by the Fin- 333 isher Group in the model. Some examples of finishing processes are sta- 334 pling, punching, binding, inserting, or folding. Finishing processes 335 may have supplies asssociated with the process. Stapling, binding, and 336 punching are examples of processes that have supplies. A printer may 337 have more than one finishing sub-unit and each finishing sub-unit may be 338 associated with one or more output sub-units. Finishers are not 339 described in this MIB. 341 The exact interaction and sequencing between an output device and its 342 associated finisher is not specified by the model. It depends on the 343 type of finishing process and the exact implementation of the printer 344 system. This standard allows for the logical association of a finishing 345 process with an output device but does not put any restrictions on the 346 exact sequence or interaction with the associated output device. The 347 output and finisher sub-units may or may not be separate identifiable 348 physical mechanisms depending on the exact implementation of a printer. 349 In addition, a single output device may be associated with multiple fin- 350 ishing sub-units and a single finishing sub-unit may be associated with 351 multiple output devices. 353 draft Printer MIB August 19, 1994 355 2.2.6. Markers 357 A marker is the mechanism that produces marks on the print media. The 358 marker sub-units and their associated supplies are represented by the 359 Marker Group in the model. A printer can contain one or more marking 360 mechanisms. Some examples of multiple marker sub-units are: a printer 361 with separate markers for normal and magnetic ink or an imagesetter that 362 can output to both a proofing device and final film. Each marking device 363 can have its own set of characteristics associated with it, such as 364 marking technology and resolution. 366 In this model the marker sub-unit is viewed as very generalized and 367 encompasses all aspects of a marking process. For example, in a xero- 368 graphic process, the marking process as well as the fusing process would 369 be included in the generalized concept of the marker. With the general- 370 ized concept of a marking process, the concept of multiple marking sup- 371 plies associated with a single marking sub-unit results. For example, in 372 the xerographic process, there is not only a supply of toner, but there 373 can also be other supplies such as a fuser supply that can be consumed 374 and replaced separately. In addition there can be multiple supplies of 375 toner for a single marker device, as in a color process. 377 2.2.7. Media Paths 379 The media paths encompass the mechanisms in the printer that move the 380 media through the printer and connect all other media related sub-units: 381 inputs, outputs, markers and finishers. A printer contains one or more 382 media paths. These are represented by the Media Path Group in the model. 383 The Media Path group has some attributes that apply to all paths plus a 384 table of the separate media paths. 386 In general, the design of the media paths determines the maximum speed 387 of the printer as well as the maximum media size that the printer can 388 handle. Media paths are complex mechanisms and can contain many dif- 389 ferent identifiable sub-mechanisms such as media movement devices, media 390 buffers, duplexing units and interlocks. Not all of the various sub- 391 mechanisms reside on every media path. For example, one media path may 392 provide printing only on one surface of the media (a simplex path) and 393 another media path may have a sub-mechanism that turns the media over 394 and feeds it a second time through the marker sub-unit (a duplex path). 395 The duplex path may even have a buffer sub-mechanism that allows multi- 396 ple copies of the obverse side to be held before the reverse side of all 397 the copies are marked. 399 draft Printer MIB August 19, 1994 401 2.2.8. System Controller 403 The System Controller is the sub-unit upon which the software components 404 of the Printer run. The System Controller is represented in the model by 405 the Host MIB. This MIB allows for the specification of the processor(s), 406 memory, disk storage, file system and other underlying sub-mechanisms of 407 the printer. The controller can range from simple single processor sys- 408 tems to multiprocessor systems. In addition, controllers can have a full 409 range of resources such as hard disks. The printer is modeled to have 410 one system controller even though it may have more than one processor 411 and multiple other resources associated with it. 413 2.2.9. Interfaces 415 An interface is the communications port and associated protocols that 416 are responsible for the transport of data to the printer. A printer has 417 one or more interface sub-units. The interfaces are represented by the 418 Interfaces Group of MIB-II (RFC 1213). Some examples of interfaces are 419 serial ports (with little or no protocol) and EtherNet ports on which 420 one might run InterNet IP, Novell IPX, etc. 422 2.2.10. Channels 424 The channel sub-units identify the independent sources of print data 425 (here print data is the information that is used to construct printed 426 pages and may have both data and control aspects). A printer may have 427 one or more channels. The channel sub-units are represented by the Chan- 428 nel Group in the Model. Each channel is typically identified by the 429 electronic path and service protocol used to deliver print data to the 430 printer. A channel sub-unit may be independently enabled (allowing print 431 data to flow) or disabled (stopping the flow of print data). It has a 432 current Control Language which can be used to specify which interpreter 433 is to be used for the print data and to query and change environment 434 variables used by the interpreters (and SNMP). There is also a default 435 interpreter that is to be used if an interpreter is not explicitly 436 specified using the Control Language. Channel sub-units are based on an 437 underlying interface. 439 2.2.11. Interpreters 441 The interpreter sub-units are responsible for the conversion of a 442 description of intended print instances into images that are to be 443 draft Printer MIB August 19, 1994 445 marked on the media. A printer may have one or more interpreters. The 446 interpreter sub-units are represented by the Interpreter Group in the 447 Model. Each interpreter is generally implemented with software running 448 on the System Controller sub-unit. The Interpreter Table has one entry 449 per interpreter where the interpreters include both Page Description 450 Language (PDL) Interpreters and Control Language Interpreters. 452 2.2.12. Console 454 Many printers have a console on the printer, the operator console, that 455 is used to display and modify the state of the printer. The console can 456 be as simple as a few indicators and switches or as complicated as full 457 screen displays and keyboards. There can be at most one such console. 458 This console sub-unit is represented by the Console Group in the model. 459 Although most of the information displayed there is also available in 460 the state of the printer as represented by the various Groups, it is 461 useful to be able to query and modify the operator console remotely. 462 For example, a management application might like to display to its user 463 the current message on the operator console of the remote printer or the 464 management application user might like to modify the current message on 465 the operators console of the remote printer. As another example, one 466 might have a remote application that puts up a pseudo console on a 467 workstation screen. Since the rules by which the printer state is mapped 468 onto the console and vice versa are not standardized, it is not possible 469 to reproduce the console state or the action of console buttons and 470 menus. Therefore, the Console Group provides access to the console. The 471 operator console is usually implemented on the system controller with 472 additional hardware for input and display. 474 2.2.13. Alerts 476 The alert sub-unit is responsible for detecting reportable events, mak- 477 ing an entry in the alert table and, if and only if the event is a crit- 478 ical event, initiating a trap. The alert sub-unit is represented by the 479 Alerts Group and, in particular, the Alert Table. This table contains 480 information on the severity, sub-unit, detailed location within the 481 sub-unit, alert code and description of each critical alert that is 482 currently active within the printer. Each reportable event causes an 483 entry to be made in the Alert Table. 485 draft Printer MIB August 19, 1994 487 2.2.13.1. Status and Alerts 489 Summary information about the state of the printer is reported at three 490 separate levels: (1) there is the status of the printer as a whole 491 reported in the Host MIB, (2) there is the status of various sub-units 492 reported in the principle table of the Group that represents the sub- 493 unit, and (3) there are alert codes reported in the Alert Table. 495 2.2.13.2. Overall Printer Status 497 The Printer Working Group postulated a set of status "objects" (quotes 498 used because they did not become SNMP objects) that characterized the 499 overall status of a printer. These named states are: 501 Non Critical Alert Active - there are one or more Non Critical alerts 502 in the Alert Table. This is the logical or of all of the Non 503 Critical Alert Active bits from all Sub-unit status octets. 505 Critical Alert Active - There are one or more Critical Alerts in the 506 Alert Table. This the logical or of all of the Critical Alert 507 Active bits from all Sub-unit Status octets. 509 On Request - The Printer is not currently available to service 510 requests, but could be made available (brought to the ready state) 511 with some human interaction. 513 Unavailable - The sub-unit is unavailable for use (this is the same as 514 "broken" or "down" in other terminologies) 516 Busy / Temporarily Unavailable - The sub-unit is operational but 517 currently occupied with a request for activity. The sub-unit will 518 become available without the need of human interaction. 520 Moving on-line or off-line - The sub-unit is either off-line, in the 521 process of moving off-line or in the process of moving back on- 522 line; 523 for example on high end printers reloading paper involves a 524 transition to off-line to open the paper bin, it is then filled 525 and, finally, there is a transition back to on-line as the paper 526 bin is repositioned for printing. 528 Standby - The sub-unit is unavailable for use because 529 it is partially powered down and may need some 530 period of time to become fully operational again. 532 draft Printer MIB August 19, 1994 534 A unit in Standby state shall respond to network management 535 requests. 537 Rather than define new status objects to indicate these states, the 538 Printer Working Group recognized that the existing status objects in the 539 Host MIB provided much of the information that was desired. Thus, the 540 overall status of the printer can be determined by reading three objects 541 in the Host MIB: (1) hrDeviceStatus in the entry in the Host MIB hrDevi- 542 ceTable; (2) hrPrinterStatus in the hrPrinterTable; and (3) hrPrinter- 543 DetectedErrorState in the hrPrinterTable. The following table shows the 544 mapping of the postulated printer status into particular values for the 545 three status objects related to Printers in the Host MIB: 547 Printer hrDeviceStatus hrPrinterStatus hrPrinterDetectedErrorState 548 Status 550 Normal running(2) idle(3) none set 552 Busy/ running(2) printing(4) 553 Temporarily 554 Unavailable 556 Non Critical warning(3) idle(3) or could be: lowPaper, or 557 Alert Active printing(4) lowToner 559 Critical down(5) other(1) could be: jammed, or 560 Alert Active noPaper, or noToner, or 561 coverOpen 563 On Request down(5) other(1) serviceRequested 565 Unavailable down(5) other(1) 567 Moving off- warning(3) idle(3) or offline 568 line printing(4) 570 Off-line down(5) other(1) offline 572 Moving down(5) warmup(5) 573 on-line 575 Standby warning(3) other(1) 577 This mapping does not exactly capture the intent of the Status 578 "objects" above. It is not possible to do so simultaneously should 579 draft Printer MIB August 19, 1994 581 both Critical and Non-Critical Alerts be active. If a Critical Alert 582 is active any Non-Critical Alerts are masked. But, it is possible to 583 detect the Non-Critical Alerts by scanning the Alert Table. The 584 representation of the On Request status uses serviceRequested with the 585 down(5) value of hrDeviceStatus although the Host MIB indicates that a 586 warning(3) value is thought more appropriate when serviceRequested is 587 set. Moving off- line is represented as a warning(3) (indicating that 588 printing may still be possible) when printing may have already ceased 589 in which case hrPrinterStatus should be idle(3). Standby is 590 represented by the combination of warning(3) and other(1), but this 591 like the representation of Offline is really an indirect indication of 592 the state. With these exceptions, the representation in terms of the 593 Host MIB objects is workable. 595 Although the above mapping is workable, it would be considerably 596 improved with a few additions to hrDeviceStatus and hrPrinterStatus in 597 the Host Resources MIB. In particular, because it is not unique to 598 printers, it would be appropriate to add a "standby" or "powersave" 599 enumeration to hrDeviceStatus. Similarly, it would be useful to add 600 the following to hrPrinterStatus: "offline" to indicate that reason 601 for the printer being down (instead of having to use "other") which 602 allows both "warning" and "offline" to indicate going offline and 603 "down" and "offline" to indicate offline and "notapplicable" to cover 604 cases, such as "standby", where the device state completely describes 605 the state of the device. 607 Detailed status is reported in the sub-unit status fields. 609 2.2.13.2.1. Host MIB Printer Status 611 For completeness, the definitions of the Printer Status objects of the 612 Host MIB are given below: 614 hrDeviceStatus OBJECT-TYPE 615 SYNTAX INTEGER { 616 unknown(1), 617 running(2), 618 warning(3), 619 testing(4), 620 down(5) 621 } 622 ACCESS read-only 623 STATUS mandatory 624 DESCRIPTION 626 draft Printer MIB August 19, 1994 628 "The current operational state of the device 629 described by this row of the table. A value 630 unknown(1) indicates that the current state of the 631 device is unknown. running(2) indicates that the 632 device is up and running and that no unusual error 633 conditions are known. The warning(3) state 634 indicates that agent has been informed of an 635 unusual error condition by the operational software 636 (e.g., a disk device driver) but that the device is 637 still 'operational'. An example would be high 638 number of soft errors on a disk. A value of 639 testing(4), indicates that the device is not 640 available for use because it is in the testing 641 state. The state of down(5) is used only when the 642 agent has been informed that the device is not 643 available for any use." 644 ::= { hrDeviceEntry 5 } 646 hrPrinterStatus OBJECT-TYPE 647 SYNTAX INTEGER { 648 other(1), 649 unknown(2), 650 idle(3), 651 printing(4), 652 warmup(5) 653 } 654 ACCESS read-only 655 STATUS mandatory 656 DESCRIPTION 657 "The current status of this printer device. When 658 in the idle(1), printing(2), or warmup(3) state, 659 the corresponding hrDeviceStatus should be 660 running(2) or warning(3). When in the unknown 661 state, the corresponding hrDeviceStatus should be 662 unknown(1)." 663 ::= { hrPrinterEntry 1 } 665 hrPrinterDetectedErrorState OBJECT-TYPE 666 SYNTAX OCTET STRING 667 ACCESS read-only 668 STATUS mandatory 669 DESCRIPTION 670 "This object represents any error conditions 671 detected by the printer. The error conditions are 672 encoded as bits in an octet string, with the 674 draft Printer MIB August 19, 1994 676 following definitions: 678 Condition Bit # hrDeviceStatus 680 lowPaper 0 warning(3) 681 noPaper 1 down(5) 682 lowToner 2 warning(3) 683 noToner 3 down(5) 684 doorOpen 4 down(5) 685 jammed 5 down(5) 686 offline 6 down(5) 687 serviceRequested 7 warning(3) 689 If multiple conditions are currently detected and 690 the hrDeviceStatus would not otherwise be 691 unknown(1) or testing(4), the hrDeviceStatus shall 692 correspond to the worst state of those indicated, 693 where down(5) is worse than warning(3) which is 694 worse than running(2). 696 Bits are numbered starting with the most 697 significant bit of the first byte being bit 0, the 698 least significant bit of the first byte being bit 699 7, the most significant bit of the second byte 700 being bit 8, and so on. A one bit encodes that 701 the condition was detected, while a zero bit 702 encodes that the condition was not detected. 704 This object is useful for alerting an operator to 705 specific warning or error conditions that may 706 occur, especially those requiring human 707 intervention." 708 ::= { hrPrinterEntry 2 } 710 2.2.13.2.2. Sub-unit Status 712 Sub-unit status is reported in the entries of the principle table in the 713 Group that represents the sub-unit. For sub-units that report a status, 714 there is a status column in the table and the value of this column is 715 always the following enumeration: 717 1 other 719 draft Printer MIB August 19, 1994 721 2 unknown 723 3 Available 725 4 In Critical state 727 5 In Non-critical, warning state 729 6 State is a Combination of Critical and Warning 731 7 On request (intervention required) 733 8 Unavailable 735 9 Busy/Temporarily Unavailable 737 For example, an input (tray) that jammed on the next to the last page 738 may show a status of 6 (both a critical state, jammed, and a non 739 critical state, low paper). 741 2.2.13.3. Alert Tables 743 The Alert Group consists of a single table in which all active alerts 744 are represented. This section provides and overview of the table and a 745 description of how it is managed. The basic content of the alert table 746 is the severity (critical or non-critical) of the alert, the Group and 747 entry where a state change caused the alert, additional information 748 about the alert (a more detailed location, an alert code, and a descrip- 749 tion), and an indication of the level of training needed to service the 750 alert. 752 The Alert Table contains some information that is redundant, for example 753 that an event has occurred, and some information that is only 754 represented in the Alert Table, for example the additional information. 755 A single table was used because a single entry in a Group could cause 756 more than one alert, for example paper jams in more than one place in a 757 media path. Associating the additional information with the entry in the 758 affected group would only allow one report where associating the addi- 759 tional information with the alert makes multiple reports possible. 761 Every time an alert occurs in the printer, the printer makes one or more 762 entries into the Alert Table. The printer determines if an event is to 763 be classified as critical or non-critical. If the severity of the Alert 764 draft Printer MIB August 19, 1994 766 is "critical", the printer sends a trap or event notification to the 767 host indicating that the table has changed. Whether or not a trap is 768 sent, the management application is expected to poll the printer on a 769 regular basis and to read and parse the table to determine what condi- 770 tions have changed, in order to provide reliable information to the 771 management application user. 773 2.2.13.4. Alert Table Management 775 The alert tables are sparsely populated tables. This means the tables 776 will only contain entries of the alerts that are currently active and 777 the number of rows, or entries in the table will be dynamic. More than 778 one event can be added or removed from the event tables at a time 779 depending on the implementation of the printer. 781 There are basically two kinds of events that produce alerts: binary 782 change events and simple change events. Binary change events come in 783 pairs: the leading edge event and the trailing edge event. The leading 784 edge event enters a state from which there is only one exit; for exam- 785 ple, going from running to stopped with a paper jam. The only exit from 786 this state is fixing the paper jam and it is clear when that is accom- 787 plished. The trailing edge event is the event which exits the state the 788 was entered by the leading edge event; in the example above fixing the 789 paper jam is the trailing edge event. 791 It is relatively straightforward to manage binary change events in the 792 Alert Table. Only the leading edge event makes an entry in the alert 793 table. This entry persists in the Alert Table until the trailing edge 794 event occurs at which point this event is signal by the removal of the 795 leading edge event entry in the Alert Table. That is, a trailing edge 796 event does not create an entry; it removes the corresponding leading 797 edge event. With binary events it is possible to compute the maximum 798 number that can occur at the same time and construct an Alert Table that 799 would hold that many events. There would be no possibility of table 800 overflow and no information about outstanding events would be lost. 802 Unfortunately, there are some events that are not binary changes. This 803 other category of event, the simple change event, is illustrated by the 804 configuration change event. With this kind of event the state of the 805 machine has changed, but to a state which is (often) just as valid as 806 the state that was left and from which no return is necessary. For 807 example, an operator may change the paper that is in the primary input 808 source from letter to legal. At some time in the future the paper may be 809 changed back to letter, but it might be changed to executive instead. 811 draft Printer MIB August 19, 1994 813 This is where the problem occurs. It is not obvious how long to keep 814 simple change event entries in the Alert Table. It they were never 815 removed, the Alert Table would continue to grow indefinitely. 817 The agent needs to have an algorithm implemented for the management of 818 the alert table, especially in the face of combinations of binary and 819 simple alerts that would overflow the storage capaciity of the table. 820 When the table is full and a new alert needs to be added, an old alert 821 needs to be deleted. The alert to be deleted should be chosen using the 822 following rules: 824 1. Find a non-critical simple alert and delete it. If there are 825 multiple non-critical simple alerts, it is suggested that the 826 oldest one be chosen. If there are no non-critical simple 827 alerts, then, 829 2. Find a non-critical binary alert and delete it. If there are 830 multiple non-critical binary alerts, it is suggested that the 831 oldest one be chosen. If there are no non-critical binary 832 alerts, then, 834 3. Find a critical (binary) alert and delete it. If there are 835 multiple critical alerts, it is suggested that the 836 oldest one be chosen. Agent implementors are encouraged to 837 provide at least enough storage space for the maximum number 838 of critical alerts that could occur simultaneously. Note that 839 all critical alerts are binary. 841 Note that because the Alert Index is a monotonically increasing integer 842 there will be gaps in the values in the table when an alert is deleted. 843 Such gaps can be detected by the management application to indicate that 844 the management application may want to re-acquire the Printer state and 845 check for state changes it did not observe in the Alert Table. 847 2.3. Read-Write Objects/Attributes 849 Some of the objects/attributes in the printer MIB report on the 850 existence of or amount of a given resource used with the printer. Some 851 examples of such resources are the size and number of sheets of paper in 852 a paper tray or the existence of certain output options. On some 853 printers there are sensors that allow these resources to be sensed. 854 Other printers, however, lack sensors that can detect (all of) the pro- 855 perties of the resource. Because the printer needs to know of the 856 existence or properties of these resources for the printer to function 857 draft Printer MIB August 19, 1994 859 properly some other way of providing this information is needed. The 860 chosen way to solve this problem is to allow a management application to 861 write into object/attributes which hold the descriptive or existence 862 values for printers that cannot sense the values. Thus many of the 863 objects/attributes in the MIB are given read-write access, but a printer 864 implementation might only permit a management operation to change the 865 value if the printer could not sense the value itself. Therefore, the 866 ability to change the value of a read-write object may depend on the 867 implementation of the agent. Note that even though some objects expli- 868 citely state the behaviour of conditional ability to change values, any 869 read-write object may act that way. 871 Generally, an object/attribute is given read-write access in the Printer 872 MIB specification if: 873 1.The object/attribute involves installation of a resource that some 874 printers cannot themselves detect. Therefore, external means are 875 needed to inform the printer of the installation. (Here external 876 means include using the operator console, or remote management 877 application) and 878 2.The printer will behave differently if the installation of the 879 resource is reported than the printer would if the installation 880 were not reported; that is, the object/attribute is not to be used 881 as a place to put information not used by the printer, i.e., not a 882 "PostIt". Another way of saying this is that the printer believes 883 that information given it and acts as if the information were 884 true. For example, on a printer that cannot sense the size, if 885 one paper size is loaded, but another size is set into the paper 886 size object/attribute, then the printer will use the size that was 887 set as its current paper size in its imaging and paper handling. 889 The printer may get hints that it may not know about the existence or 890 properties of certain resources. For example, a paper tray may be 891 removed and re-inserted. When this removal and insertion happens, the 892 printer may either assume that a property, such as the size of paper in 893 the tray, has not changed or the printer may change the value of the 894 associated object/attribute to "unknown", as might be done for the 895 amount of paper in the tray. As long as the printer acts according to 896 the value in the object/attribute either strategy is acceptable. 898 It is an implementation-specific matter as to whether or not MIB 899 object values are persistent across power cycles or cold starts. It 900 is particularly important that the values of the prtMarkerLifeCount 901 object persist throughout the lifetime of the printer. Therefore, if 902 the value of any MIB object persists across power cycles, then the 903 prtMarkerLifeCount object must also persist. 905 draft Printer MIB August 19, 1994 907 2.4. Notational Conventions 909 This section describes the notational conventions used in this specifi- 910 cation in order to be able to completely specify the common syntax and 911 semantics for the corresponding MIB and MIF specifications. A strong 912 goal is to be able to have a corresponding MIF that specifies identical 913 naming, syntax, and semantics so that a product described by a MIF can 914 be managed using SNMP and the Printer MIB via a trivial translation. 916 2.4.1. Object/Attribute Names 918 This section specifies the syntax of MIB object names and MIF attribute 919 names and the notation used in the common specification so that the 920 respective MIB and MIF syntaxes are unambiguous. 922 2.4.1.1. SNMP MIB Object Names 924 SNMP requires that object names start with a lower case letter followed 925 by uppercase and lowercase letters and digits; no other characters are 926 allowed. By convention, each word in an SNMP object name starts with an 927 uppercase letter, except the first. Words that are acronyms are all 928 uppercase. All object names defined in the Printer MIB start with the 929 prefix `prt' in order to distinguish them from objects defined in other 930 MIBs and to meet the requirement that the first letter must be lower 931 case. As a further convention, the next word(s) in the object name is 932 the Group name. Examples of Printer MIB object names in the General, 933 Input, and MediaPath groups: prtGeneralConfigChanges, prtInputDefaultIn- 934 putIndex, prtInputIndex, and prtMediaPathMaxSpeed. These are the names 935 for objects that are most accessable to simple management applications 936 that may just display object-name/value pairs. 938 As a notational convention to save space in this specification, the prt 939 and the group name prefix will not be shown in the MS-WORD tables defin- 940 ing objects/attributes. Instead the prefix and group name is given at 941 the top left of each MS-WORD table. When a description of an 942 object/attribute refers to another object/attribute, the name of that 943 other object/attribute is given in boldface. Such references to another 944 object/attribute include neither the prt prefix nor the group name pre- 945 fix, if the object/attribute is in the same group. In the rare cases 946 that a reference is made to an object in another group, both the prt 947 prefix and the group name are included in the reference. For example, 948 the description of the prtInputDescription object/attribute in the Input 949 group contains a reference to the prtGeneralCurrentLocalization 950 draft Printer MIB August 19, 1994 952 object/attribute in the General group. 954 2.4.1.2. DMTF MIF Attribute Names 956 DMTF allows attribute names to be quoted strings containing any ISO 957 Latin-1 character, including SPACE. These attribute names are used to 958 display to users of the management applications, so there is consider- 959 able advantage to including a space between each word in a MIF attribute 960 name. However, in order to make the translation to MIB syntax, the 961 Printer MIF will use no special characters such as -, / etc. (even 962 though the MIF to MIB translator would just eliminate them in the 963 conversion). Therefore, the Printer MIF attribute names will consist of 964 words separated by a SPACE and all starting with an uppercase letter, 965 except the prefix prt. The corresponding examples of Printer MIF attri- 966 bute names in the General, Input, and MediaPath groups are: "prt General 967 Config Changes", "prt Input Default Index", "prt Input Index", and "prt 968 Media Path Max Speed". 970 2.4.2. Defined Data Types 972 Both MIBs and MIFs permit the definition of data types to be used else- 973 where. For example, enumerated values that are used in more that one 974 object/attribute will be defined as a data type. SNMP requires that 975 datatype name start with an uppercase letter. The data type names will 976 be mixed case with the first letter of each word being uppercase. Since 977 these data type names are for programmers, and are not seen by end 978 users, the words will contain no spaces. Example of MIB and MIF data 979 types are: IntpLangFam and SubUnitStatus. 981 2.4.3. Enumerations 983 Enumerations (enums) are sets of symbolic values defined for use with 984 one or more objects/attributes. Some common enumeration sets are 985 assigned a symbolic data type name (textual convention). These enumera- 986 tions are listed at the beginning of this specification. 988 2.4.3.1. SNMP MIB enumeration symbols 990 SNMP requires that the syntax of an enumeration (defined using the data 991 type Integer) start with a lower case letter followed by uppercase and 992 draft Printer MIB August 19, 1994 994 lowercase letters and digits, no other characters are allowed. By con- 995 vention, each word in an SNMP enum name starts with an uppercase letter, 996 except the first. Words that are acronyms are all uppercase. For most 997 enums there is no special (lowercase) prefix. However, for Interpreter 998 Family and Channel Type for which the names are often proper names or 999 acronyms (e.g., PCL, PostScript, ISO6429), the lower case prefixes: lang 1000 and chan, respectively are used. Examples of the Printer MIB enumera- 1001 tions for the SubUnitStatus and IntpLangFam data types, respectively, 1002 are: criticalAndNonCritical, and langPCL, langPS, and langISO6429. 1004 2.4.3.2. DMTF MIF enumeration symbols 1006 Like MIF attribute names, MIF enum symbols can contain any ISO Latin-1 1007 character, including SPACE. However, for the same reasons, the Printer 1008 MIF will restrict enum names to words starting with an uppercase letter, 1009 including the first word (the MIF to MIB translator will automatically 1010 lower case the first letter to follow the SNMP requirements). The 1011 corresponding examples of Printer MIF enumerations for the SubUnitStatus 1012 and IntpLangFam data types, respectively, are: "Critical And Non Criti- 1013 cal", and "lang PCL", "lang PostScript", and "lang ISO 6429". 1015 2.4.3.3. Registering Additional Enumerated Values 1017 This working group has defined several type of enumerations. These 1018 enumerations differ in the method employed to control the addition of 1019 new enumerations. Throughout this document, references to "enum (n)", 1020 where n can be 1, 2 or 3 can be found in the various tables. The defin- 1021 itions of these types of enumerations are: 1022 enum (1) All the values are defined in the Printer MIB 1023 specification (RFC for the Printer MIB). Additional enumerated 1024 values require a new RFC. 1025 enum (2) An initial set of values are defined in the Printer 1026 MIB specification. Additional enumerated values are 1027 registered after review by this working group. The initial 1028 versions of the MIB will contain the values registered so far. 1029 After the MIB is approved, additional values will be 1030 registered through IANA after approval by this working group. 1031 enum (3) An initial set of values are defined in the Printer 1032 MIB specification. Additional enumerated values are 1033 registered without working group review. The initial versions of 1034 the MIB will contain the values registered so far. After the MIB 1035 is approved, additional values will be registered 1036 through IANA without approval by this working group. 1038 draft Printer MIB August 19, 1994 1040 3. Objects/Attributes from other MIB/MIF Specifications 1042 This section lists the objects/attributes from other IETF MIB specifica- 1043 tions and other DMTF MIF specifications that are mandatory for confor- 1044 mance to this Printer MIB specification. 1046 To be supplied by DMTF to correspond to MIB II 1048 DMTF MIF "Component ID: (From DMI Specification - Draft 4.2 - 12 January 1049 1994) 1051 1. Manufacturer 1052 String64 1053 Name of the organization that produces this component. 1055 2. Product 1056 String64 1057 Name of this Printer 1059 3. Version 1060 String64 1062 4. SerialNumber 1063 String64 1065 5. Installation 1066 Date 1067 Time and Date of the Last Installation 1069 6. Verify 1070 Integer 1071 Verification Level for this printer 1073 "Asking for the 'Verify' attribute causes the component 1074 instrumentation code to perform checks to verify that 1075 the component is still in the system and working 1076 properly. It should return on of the following values: 1078 Value Meaning 1080 0 An error occurred; Check status code 1082 1 Component does not exist 1084 2 Verify not supported 1086 draft Printer MIB August 19, 1994 1088 4 Component exists, functionally untested 1090 5 Component exists, functionally unknown 1092 6 Component exists, functionally no good 1094 7 Component exists, functionally good 1096 3.1. System Group objects 1098 All objects in the system group of MIB-II (RFC 1213) must be imple- 1099 mented. 1101 3.2. System Controller 1103 The System Controller is represented by the Storage and Device Groups of 1104 the Host Resources MIB (RFC 1514). These are the only groups that are 1105 required to be implemented. Other Groups (System, Running Software, 1106 Running Software Performance, and Installed Software) may be implemented 1107 at the discretion of the implementor. 1109 3.3. Interface Group objects 1111 All objects in the Interfaces Group of MIB-II (RFC 1213) shall be imple- 1112 mented. 1114 Printer-MIB DEFINITIONS ::= BEGIN 1116 IMPORTS 1117 MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, Integer32, 1118 TimeTicks, NOTIFICATION-TYPE, OBJECT-IDENTITY FROM SNMPv2-SMI 1119 TEXTUAL-CONVENTION FROM SNMPv2-TC 1120 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 1121 hrDeviceIndex, hrStorageIndex FROM HOST-RESOURCES-MIB; 1123 printmib MODULE-IDENTITY 1124 LAST-UPDATED "9407050000Z" 1125 ORGANIZATION "IETF Printer MIB Working Group" 1126 CONTACT-INFO 1127 " Steven Waldbusser 1128 Postal: Carnegie Mellon University 1129 4910 Forbes Ave 1131 draft Printer MIB August 19, 1994 1133 Pittsburgh, PA, 15213 1135 Tel: 412-268-6628 1136 Fax: 412-268-4987 1137 E-mail: waldbusser@cmu.edu" 1138 DESCRIPTION 1139 "The MIB module for management of printers." 1140 ::= { printmibDraft 1 } 1142 -- Upon publication as RFC, delete this comment and the line following 1143 -- this comment and change the reference of { printmibDraft 1 } 1144 -- (above) to { mib-2 X }. 1145 -- This will result in changing: 1146 -- 1 3 6 1 3 54 printmib(1) to: 1147 -- 1 3 6 1 2 1 printmib(X) 1148 -- This will make it easier to translate prototypes to 1149 -- the standard namespace because the lengths of the OID's won't change. 1150 printmibDraft OBJECT IDENTIFIER ::= { experimental 54 } 1152 -- Textual conventions for this MIB module 1154 MediaUnit ::= TEXTUAL-CONVENTION 1155 STATUS current 1156 DESCRIPTION 1157 "Units of measure for media dimensions. 1159 This is a type 1 enumeration." 1160 SYNTAX INTEGER { 1161 tenThousandthsOfInches(3), -- .0001 1162 micrometers(4) 1163 } 1165 CapacityUnit ::= TEXTUAL-CONVENTION 1166 STATUS current 1167 DESCRIPTION 1168 "Units of measure for media capacity. 1170 This is a type 1 enumeration." 1171 SYNTAX INTEGER { 1172 tenThousandthsOfInches(3), -- .0001 1173 micrometers(4), 1174 sheets(8), 1175 feet(16), 1176 meters(17) 1177 } 1179 draft Printer MIB August 19, 1994 1181 SubUnitStatus ::= TEXTUAL-CONVENTION 1182 STATUS current 1183 DESCRIPTION 1184 "Status of a printer sub-unit. 1186 This is a type 1 enumeration." 1187 SYNTAX INTEGER { 1188 other(1), 1189 unknown(2), 1190 available(3), 1191 critical(4), -- unavailable, with critical alert 1192 nonCritical(5), -- available, with noncritical alert 1193 criticalAndNonCritical(6), -- unavailable, with 1194 -- both critical and noncritical alerts 1195 onRequest(7), -- printer capable, but 1196 -- intervention required 1197 unavailable(8), 1198 busyTemporarilyUnavailable(9) 1199 } 1201 PresentOnOff ::= TEXTUAL-CONVENTION 1202 STATUS current 1203 DESCRIPTION 1204 "Presence and configuration of a device or feature. 1206 This is a type 1 enumeration." 1207 SYNTAX INTEGER { 1208 other(1), 1209 on(3), 1210 off(4), 1211 notPresent(5) 1212 } 1214 CodedCharSet ::= TEXTUAL-CONVENTION 1215 STATUS current 1216 DESCRIPTION 1217 "A coded character set value that specifies both a set of 1218 characters that may be used and an encoding (as one or more 1219 octets) that is used to represent the characters in the 1220 set. These values are to be used to identify the encoding 1221 employed for strings in the MIB where this is not fixed by the 1222 MIB. 1224 Some objects that allow a choice of coded character set 1225 are: the prtLocalizationCharacterSet object in the 1227 draft Printer MIB August 19, 1994 1229 LocalizationTable and prtInterpreterDefaultCharSetIn. 1230 The prtGeneralCurrentLocalization and prtConsoleLocalization 1231 objects in turn contain the index in the LocalizationTable 1232 of the current localization (country, language, and coded 1233 character set) of the `description' objects and the console, 1234 respectively. 1236 The space of the coded character set enumeration has been 1237 divide into three regions. The first region (3-999) consists 1238 of coded character sets that have been standardized by some 1239 standard setting organization. This region is intended for 1240 standards that do not have subset implementations. The second 1241 region (1000-1999) is for the Unicode and ISO/IEC 10646 coded 1242 character sets together with a specification of a (set of) 1243 sub-repetoires that may occur. The third region (>1999) is 1244 intended for vendor specific coded character sets. 1246 Where a given coded character set may be known by more than 1247 one name, the most commonly known name is used as the name of 1248 the enumeration and other names are shown in the comments. The 1249 comments also indicate where to find detailed information on 1250 the coded character set and briefly characterize its 1251 relationship to other similar coded character sets. 1253 This is a type 3 ennumeration." 1254 SYNTAX INTEGER { 1255 other(1), -- used if the designated coded 1256 -- character set is not currently in 1257 -- the enumeration 1259 -- standard sets in the range 3-999: 1261 csASCII(3), -- ASCII 1262 -- ISO 646-1991 IRV with the dollar 1263 -- sign as the currency symbol. 1264 -- Note that this set is 7-bit ASCII 1265 -- with either the 8th bit omitted, or 1266 -- zero; this set is not 8-bit ASCII 1267 -- which is the same as ISO 8859-1 (ISO 1268 -- Latin-1) 1269 csISOLatin1(4), -- ISO Latin Alphabet No. 1 1270 -- 8-bit Latin for Western Europe and 1271 -- Western Hemisphere. See ISO 8859-1 1272 csISOLatin2(5), -- ISO Latin Alphabet No. 2 1273 -- 8-bit Latin for Eastern Europe 1275 draft Printer MIB August 19, 1994 1277 -- See ISO 8859-2 1278 csISOLatin3(6), -- ISO Latin Alphabet No. 3 1279 -- 8-bit Latin for Southern Europe and 1280 -- Western Hemisphere. See ISO 8859-3 1281 csISOLatin4(7), -- ISO Latin Alphabet No. 4 1282 -- 8-bit Latin for Northern Europe 1283 -- See ISO 8859-4 1284 -- see ISO 8859-4 1285 csISOLatinCyrillic(8), -- ISO Latin/Cyrillic Alphabet 1286 -- 8-bit ASCII plus Cyrillic. 1287 -- see ISO 8859-5 1288 csISOLatinArabic(9), -- ISO Latin/Arabic Alphabet 1289 -- 8-bit ASCII plus Arabic 1290 -- see ISO 8859-6 1291 csISOLatinGreek(10), -- ISO Latin/Greek Alphabet 1292 -- 8-bit ASCII plus Greek 1293 -- see ISO 8859-7 1294 csISOLatinHebrew(11), -- ISO Latin/Hebrew Alphabet 1295 -- 8-bit ASCII plus Hebrew 1296 -- see ISO 8859-8 1297 csISOLatin5(12), -- ISO Latin Alphabet No. 5 1298 -- 8-bit Latin for EU Member countries. 1299 -- See ISO 8859-9 1300 csISOLatin6(13), -- ISO Latin Alphabet No. 6 1301 -- 8-bit Latin for Scandanavian countries 1302 -- better than Latin4 for those countries 1303 -- See ISO 8859-10 1304 csISOTextComm(14), -- ISO Latin 8-bit Text Communication 1305 -- Used in ISO ASN.1 T61String 1306 -- see ISO 6937 1307 csHalfWidthKatakana(15), -- Half Width Katakana 1308 -- One byte only, this is equivalent 1309 -- to JIS/Roman (similar to ASCII) 1310 -- plus eight-bit half-width Katakana 1311 -- See JIS X 0201-1976 1312 csJISEncoding(16), -- JIS Encoding 1313 -- Uses ISO 2022 escape sequences to 1314 -- shift code sets as documented in 1315 -- JIS X 0202-1991 1316 csShiftJIS(17), -- Shift JIS 1317 -- Also known as MS Kanji 1318 -- A Microsoft code that extends 1319 -- csHalfWidthKatakana(15) to include 1320 -- kanji by adding a second byte when 1321 -- the value of the first byte is in 1323 draft Printer MIB August 19, 1994 1325 -- the ranges 81-9F or E0-EF. 1326 csEUCPkdFmtJapanese(18), -- Extended UNIX Code Packed Format 1327 -- for Japanese 1328 -- Standardized by OSF, UNIX 1329 -- International, and UNIX Systems 1330 -- Laboratories Pacific. 1331 -- Uses ISO 2022 rules to select 1332 -- code set 0: JIS Roman (a single 1333 -- 7-bit byte set) 1334 -- code set 1: JIS X0208-1990 (a double 1335 -- 8-bit byte set) 1336 -- restricted to A0-FF in both bytes 1337 -- code set 2: Half Width Katakana (a 1338 -- single 7-bit byte set) 1339 -- requiring SS2 as the character prefix 1340 -- code set 3: JIS X0212-1990 (a double 1341 -- 7-bit byte set) 1342 -- restricted to A0-FF in both bytes 1343 -- requiring SS3 as the character prefix 1344 -- PCL Symbol Set id: 17K 1345 csEUCFixWidJapanese(19),-- Extended UNIX Code Fixed Width for 1346 -- Japanese 1347 -- Used in Japan. 1348 -- Each character is 2 octets. 1349 -- code set 0: JIS Roman (a single 1350 -- 7-bit byte set) 1351 -- 1st byte = 00 1352 -- 2nd byte = 20-7E 1353 -- code set 1: JIS X0208-1990 (a double 1354 -- 7-bit byte set 1355 -- restricted to A0-FF in both bytes 1356 -- code set 2: Half Width Katakana (a 1357 -- single 7-bit byte set) 1358 -- 1st byte = 00 1359 -- 2nd byte = A0-FF 1360 -- code set 3: JIS X0212-1990 (a double 1361 -- 7-bit byte set) 1362 -- restricted to A0-FF in the first byte 1363 -- and 21-7E in the second byte 1364 csISO4UnitedKingdom(20), 1365 -- United Kingdom national std set 1366 -- See registration 4 - ISO 2375 1367 -- Registration Authority: ECMA. 1368 csISO11SwedishforNames(21), 1369 -- Swedish for Names national std set 1371 draft Printer MIB August 19, 1994 1373 -- See registration 11 - ISO 2375 1374 -- Registration Authority: ECMA. 1375 csISO15Italian(22), -- Italian national set 1376 -- See registration 15 - ISO 2375 1377 -- Registration Authority: ECMA. 1378 csISO17Spanish(23), -- Spanish national set 1379 -- See registration 17 - ISO 2375 1380 -- Registration Authority: ECMA. 1381 csISO21German(24), -- German national std set 1382 -- See registration 21 - ISO 2375 1383 -- Registration Authority: ECMA. 1384 csISO60DanishNorwegian(25), 1385 -- Danish Norwegian national std set 1386 -- See registration 60 - ISO 2375 1387 -- Registration Authority: ECMA. 1388 csISO69French(26), -- French - see ISO Reg No 69 1389 -- See registration 69 - ISO 2375 1390 -- Registration Authority: ECMA. 1392 -- Unicode and vendor-supplied combinations of ISO collections 1393 -- (in the range 1000-1999): 1395 -- NOTE: Unicode and ISO 10646 character coded data may be 1396 -- processed and stored in either Big Endian (most significant 1397 -- octet first) or Little Endian (least significant octet first) 1398 -- order. Intel x86, VAX, and Alpha/AXP architectures are 1399 -- examples of Little Endian processor architectures. 1400 -- Furthermore, in environments where either order may occur, 1401 -- so-called Unicode BYTE ORDER MARK (BOM) character (which is ISO 1402 -- 10646 ZERO WIDTH NO BREAK SPACE), coded as FEFF in two octets 1403 -- and 0000FEFF in four octets is used at the beginning of the 1404 -- data as a signature to indicate the order of the following data 1405 -- (See ISO 10646 Annex F). Thus either ordering and BOM may 1406 -- occur in print data streams sent to the interpreter. 1408 -- However, ISO 8824/8825 (ASN.1/BER) used by SNMP 1409 -- is quite clear that Big Endian order shall be used and BOM 1410 -- shall NOT be used in transmission in the protocol. Transmitting 1411 -- Unicode in Big Endian order in SNMP should not prove to be a 1412 -- hardship for Little Endian machines, since SNMP ASN.1/BER 1413 -- requires integers to be transmitted in Big Endian order as 1414 -- well. So SNMP implementations on Little Endian machines are 1415 -- already reversing the order of integers to make them Big Endian 1417 draft Printer MIB August 19, 1994 1419 -- for transmission via SNMP. Also Unicode characters are usually 1420 -- treated as two-octet integers, not short text strings, so that 1421 -- it will be straightforward for Little Endian machines to reverse 1422 -- the order of Unicode character octets as well before 1423 -- transmitting them and after receiving them via the SNMP protocol. 1425 csUnicode(1000), -- Unicode 1426 -- Universal Coded Character set. 1427 -- Any character. See ISO 10646 1428 -- two-octet representation, 1429 -- implementation level 3 1430 csUCS4(1001), -- Four-octet Universal Coded Character 1431 -- Set 1432 -- Any character. See ISO 10646 1433 -- four-octet representation, 1434 -- implementation level 3 1435 csUnicodeASCII(1002), -- ASCII subset of Unicode 1436 -- Basic Latin = collection 1 1437 -- See ISO 10646, Appendix A 1438 csUnicodeLatin1(1003), -- ISO Latin-1 subset of Unicode 1439 -- Basic Latin and Latin-1 Supplement 1440 -- = collections 1 and 2 1441 -- See ISO 10646, Appendix A 1442 csUnicodeIBM2039(1004),-- IBM Latin-1 SAA Core Coded Character 1443 -- Set 1444 -- Extended ISO 8859-1 1445 -- Presentation Set, GCSGID: 2039 1446 csUnicodeIBM1261(1005),-- IBM Latin-2, -3, -5, Extended 1447 -- Presentation Set, GCSGID: 1261 1448 csUnidoceIBM1268(1006),-- IBM Latin-4 Extended 1449 -- Presentation Set, GCSGID: 1268 1450 csUnicodeIBM1276(1007),-- IBM Cyrillic Greek Extended 1451 -- Presentation Set, GCSGID: 1276 1452 csUnicodeIBM1264(1008),-- IBM Arabic 1453 -- Presentation Set, GCSGID: 1264 1454 csUnicodeIBM1265(1009),-- IBM Hebrew 1455 -- Presentation Set, GCSGID: 1265 1457 -- Vendor developed coded character sets (in the range 2000-xxx): 1459 csWindows30Latin1(2000), 1461 draft Printer MIB August 19, 1994 1463 -- Windows Latin-1 1464 -- Extended ISO 8859-1 for Windows 3.0 1465 -- PCL Symbol Set id: 9U 1466 csWindows31Latin1(2001), 1467 -- Windows Latin-1 1468 -- Extended ISO 8859-1 for Windows 3.1 1469 -- PCL Symbol Set id: 19U 1470 csWindows31Latin2(2002), 1471 -- Windows Latin-2 1472 -- Extended ISO 8859-2 for Windows 3.1 1473 -- PCL Symbol Set id: 9E 1474 csWindows31Latin5(2003), 1475 -- Windows Latin-5 1476 -- Extended ISO 8859-5 for Windows 3.1 1477 -- PCL Symbol Set id: 5T 1478 csHPRoman8(2004), -- HP Roman8 1479 -- HP 8-bit Latin set, ASCII in LH 1480 -- PCL Symbol Set id: 8U 1481 csAdobeStandardEncoding(2005), 1482 -- Adobe Standard Encoding 1483 -- PCL Symbol Set id: 10J 1484 csVenturaUS(2006), -- Ventura US 1485 -- ASCII plus characters typically used 1486 -- in publishing, like pilcrow, 1487 -- copyright, registered, trade mark, 1488 -- section, dagger, and double dagger 1489 -- in the range A0 (hex) to FF (hex). 1490 -- PCL Symbol Set id: 14J 1491 csVenturaInternational(2007), 1492 -- Ventura International 1493 -- ASCII plus coded characters similar 1494 -- to Roman8 1495 -- PCL Symbol Set id: 13J 1496 csDECMCS(2008), -- DEC Multinational 1497 -- Similar to ISO 8859-1 1498 -- Digital Equipement Corp. 1499 csPC850Multilingual(2009), 1500 -- ASCII in the LH 1501 -- Other Latin characters in the RH 1502 -- PCL Symbol Set id: 12U 1503 -- PCL Symbol Set id: 17U 1504 -- US PC code page 1506 draft Printer MIB August 19, 1994 1508 -- PCL Symbol Set id: 10U 1509 csPC8DanishNorwegian(2012), 1510 -- PC Danish Norwegian 1511 -- 8-bit PC set for Danish Norwegian 1512 -- PCL Symbol Set id: 11U 1513 csPC862LatinHebrew(2013), 1514 -- PCL Symbol Set id: 15H 1515 csPC8Turkish(2014), -- PC Latin Turkish 1516 -- PCL Symbol Set id: 9T 1517 csIBMSymbols(2015), -- IBM Symbols 1518 -- Presentation Set, CPGID: 259 1519 csIBMThai(2016), -- IBM Thai 1520 -- Presentation Set, CPGID: 838 1521 csHPLegal(2017), -- HP Legal 1522 -- PCL Symbol Set id: 1U 1523 csHPPiFont(2018), -- HP PI font 1524 -- PCL Symbol Set id: 15U 1525 csHPMath8(2019), -- HP Mathematics set 1526 -- HP 8-bit math set 1527 -- PCL Symbol Set id: 8M 1528 csHPPSMath(2020), -- HP PostScript Math 1529 -- Similar to AdobeSymbolEncoding 1530 -- PCL Symbol Set id: 5M 1531 csHPDesktop(2021), -- HP Desktop 1532 -- PCL Symbol Set id: 7J 1533 csVenturaMath(2022), -- Ventura Math 1534 -- PCL Symbol Set id: 6M 1535 csMicrosoftPublishing(2023), 1536 -- Microsoft Publishing 1537 -- PCL Symbol Set id: 6J 1538 csWindows31J(2024), -- Windows Japanese 1539 -- A further extension of csShiftJIS 1540 -- to include several OEM-specific 1541 -- kanji extensions. 1542 -- Like csShiftJIS, it adds a second 1543 -- byte when the value of the first 1544 -- byte is in the ranges 81-9F or E0-EF. 1545 -- PCL Symbol Set id: 19K 1546 csGB2312(2025), -- Chinese for People's Republic of 1547 -- China (PRC) 1548 -- mixed one byte, two byte set: 1549 -- 20-7E = one byte ASCII 1550 -- A1-FE = two byte PRC Kanji 1551 -- See GB 2312-80 1553 draft Printer MIB August 19, 1994 1555 -- PCL Symbol Set Id: 18C 1556 csBig5(2026) -- Chinese for Taiwan 1557 -- Multi-byte set. 1558 -- PCL Symbol Set Id: 18T 1559 } 1561 draft Printer MIB August 19, 1994 1563 -- The General Printer Group 1564 -- 1565 -- The general printer sub-unit is responsible for the overall control and 1566 -- status of the printer. There is exactly one general printer sub-unit in 1567 -- a printer. 1568 -- 1569 -- Implementation of every object in this group is mandatory. 1571 prtGeneral OBJECT IDENTIFIER ::= { printmib 5 } 1573 prtGeneralTable OBJECT-TYPE 1574 SYNTAX SEQUENCE OF PrtGeneralEntry 1575 MAX-ACCESS not-accessible 1576 STATUS current 1577 DESCRIPTION 1578 "A table of general information per printer. 1579 Objects in this table are defined in various 1580 places in the MIB, nearby the groups to 1581 which they apply. They are all defined 1582 here to minimize the number of tables that would 1583 otherwise need to exist." 1584 ::= { prtGeneral 1 } 1586 prtGeneralEntry OBJECT-TYPE 1587 SYNTAX PrtGeneralEntry 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "An entry exists in this table for each 1592 device entry in the hostmib device table who's type 1593 is `printer'" 1594 INDEX { hrDeviceIndex } 1595 ::= { prtGeneralTable 1 } 1597 PrtGeneralEntry ::= SEQUENCE { 1598 -- Note that not all of the objects in this sequence are in the 1599 -- general printer group. 1600 prtGeneralConfigChanges Counter32, 1601 prtGeneralCurrentLocalization Integer32, 1602 prtGeneralReset INTEGER, 1603 prtGeneralCurrentOperator OCTET STRING, 1604 prtGeneralServicePerson OCTET STRING, 1605 prtInputDefaultIndex Integer32, 1606 prtOutputDefaultIndex Integer32, 1607 prtMarkerDefaultIndex Integer32, 1609 draft Printer MIB August 19, 1994 1611 prtMediaPathDefaultIndex Integer32, 1612 prtConsoleLocalization Integer32, 1613 prtConsoleNumberOfDisplayLines Integer32, 1614 prtConsoleNumberOfDisplayChars Integer32, 1615 prtConsoleDisable INTEGER 1616 } 1618 prtGeneralConfigChanges OBJECT-TYPE 1619 SYNTAX Counter32 1620 MAX-ACCESS read-only 1621 STATUS current 1622 DESCRIPTION 1623 "Counts configuration changes that change the capabilities of 1624 a printer, such as the addition/deletion of input/output bins, 1625 the addition/deletion of interpreters, or changes in media 1626 size. Such changes will often affect the capability of the 1627 printer to service certain types of print jobs. 1629 Management applications may cache infrequently changed 1630 configuration information about sub-units on the printer. 1631 This object should be incremented whenever the agent wishes 1632 such applications to invalidate that cache and re-download 1633 all of this configuration information, thereby signalling a 1634 change in the printer's configuration. 1636 For example, if an input tray that contained paper of 1637 different dimensions was added, this counter would be 1638 incremented. 1640 As an additional example, this counter would not be 1641 incremented when an input tray is removed or the level of an 1642 input device changes." 1643 ::= { prtGeneralEntry 1 } 1645 prtGeneralCurrentLocalization OBJECT-TYPE 1646 SYNTAX Integer32 (1..65535) 1647 MAX-ACCESS read-write 1648 STATUS current 1649 DESCRIPTION 1650 "The value of the prtLocalizationIndex corresponding to the 1651 current language, country, and character set to be used for 1652 localized string values that are identified as being dependent 1653 on the value of this object. Note that this object does not 1654 apply to localized strings in the prtConsole group or any 1655 object that is not identified as above." 1657 draft Printer MIB August 19, 1994 1659 ::= { prtGeneralEntry 2 } 1661 prtGeneralReset OBJECT-TYPE 1662 SYNTAX INTEGER { 1663 notResetting(3), 1664 powerCycleReset(4), -- Cold Start 1665 resetToNVRAM(5), -- Warm Start 1666 resetToFactoryDefaults(6) -- Reset contents of 1667 -- NVRAM to factory defaults 1668 } 1669 MAX-ACCESS read-write 1670 STATUS current 1671 DESCRIPTION 1672 "Setting this value to `powerCycleReset', `resetToNVRAM', or 1673 `resetToFactoryDefaults' will result in the resetting of the 1674 printer. When read, this object will always have the value 1675 `notResetting(3)', and a SET of the value `notResetting' shall 1676 have no effect on the printer. Some of the defined values are 1677 optional. However, every implementation must support at least 1678 the values `notResetting' and resetToNVRAM'. 1680 This value is a type 3 enum." 1681 ::= { prtGeneralEntry 3 } 1683 -- The Cover Table 1684 -- 1685 -- The cover portion of the General print sub-unit describes the covers and 1686 -- interlocks of the printer. The Cover Table has an entry for each cover 1687 -- and interlock. 1689 prtCover OBJECT IDENTIFIER ::= { printmib 6 } 1691 prtCoverTable OBJECT-TYPE 1692 SYNTAX SEQUENCE OF PrtCoverEntry 1693 MAX-ACCESS not-accessible 1694 STATUS current 1695 DESCRIPTION 1696 "A table of the covers and interlocks of the printer." 1697 ::= { prtCover 1 } 1699 prtCoverEntry OBJECT-TYPE 1700 SYNTAX PrtCoverEntry 1701 MAX-ACCESS not-accessible 1702 STATUS current 1703 DESCRIPTION 1705 draft Printer MIB August 19, 1994 1707 "Information about a cover or interlock. 1708 Entries may exist in the table for each device 1709 index who's device type is `printer'." 1710 INDEX { hrDeviceIndex, prtCoverIndex } 1711 ::= { prtCoverTable 1 } 1713 PrtCoverEntry ::= SEQUENCE { 1714 prtCoverIndex Integer32, 1715 prtCoverDescription OCTET STRING, 1716 prtCoverStatus INTEGER 1717 } 1719 prtCoverIndex OBJECT-TYPE 1720 SYNTAX Integer32 (1..65535) 1721 MAX-ACCESS not-accessible 1722 STATUS current 1723 DESCRIPTION 1724 "A unique value used by the printer to identify this Cover sub-unit. 1725 Although these values may change due to a major reconfiguration of 1726 the device (e.g. the addition of new cover sub-units to the printer), 1727 values are expected to remain stable across successive printer 1728 power cycles." 1729 ::= { prtCoverEntry 1 } 1731 prtCoverDescription OBJECT-TYPE 1732 SYNTAX OCTET STRING (SIZE(0..255)) 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "The manufacturer provided cover sub-mechanism name in the 1737 localization specified by prtGeneralCurrentLocalization." 1738 ::= { prtCoverEntry 2 } 1740 prtCoverStatus OBJECT-TYPE 1741 SYNTAX INTEGER { 1742 other(1), 1743 doorOpen(3), 1744 doorClosed(4), 1745 interlockOpen(5), 1746 interlockClosed(6) 1747 } 1748 MAX-ACCESS read-only 1749 STATUS current 1750 DESCRIPTION 1751 "The status of this cover sub-unit. This value is a type 2 enum." 1753 draft Printer MIB August 19, 1994 1755 ::= { prtCoverEntry 3 } 1757 -- The Localization Table 1758 -- 1759 -- The localization portion of the General printer sub-unit is responsible 1760 -- for identifying the natural language, country, and character set in 1761 -- which character strings are expressed. There may be one or more 1762 -- localizations supported per printer. The available localizations are 1763 -- represented by the Localization table. 1765 prtLocalization OBJECT IDENTIFIER ::= { printmib 7 } 1767 prtLocalizationTable OBJECT-TYPE 1768 SYNTAX SEQUENCE OF PrtLocalizationEntry 1769 MAX-ACCESS not-accessible 1770 STATUS current 1771 DESCRIPTION 1772 "The available localizations in this printer." 1773 ::= { prtLocalization 1 } 1775 prtLocalizationEntry OBJECT-TYPE 1776 SYNTAX PrtLocalizationEntry 1777 MAX-ACCESS not-accessible 1778 STATUS current 1779 DESCRIPTION 1780 "A description of a localization. 1782 Entries may exist in the table for each device 1783 index who's device type is `printer'." 1784 INDEX { hrDeviceIndex, prtLocalizationIndex } 1785 ::= { prtLocalizationTable 1 } 1787 PrtLocalizationEntry ::= SEQUENCE { 1788 prtLocalizationIndex Integer32, 1789 prtLocalizationLanguage OCTET STRING, 1790 prtLocalizationCountry OCTET STRING, 1791 prtLocalizationCharacterSet CodedCharSet 1792 } 1794 prtLocalizationIndex OBJECT-TYPE 1795 SYNTAX Integer32 (1..65535) 1796 MAX-ACCESS not-accessible 1797 STATUS current 1798 DESCRIPTION 1799 "A unique value used by the printer to identify this 1801 draft Printer MIB August 19, 1994 1803 localization entry. Although these values may change due to a major 1804 reconfiguration of the device (e.g., the addition of new Cover 1805 sub-units to the printer), values are expected to remain stable 1806 across successive printer power cycles." 1807 ::= { prtLocalizationEntry 1 } 1809 prtLocalizationLanguage OBJECT-TYPE 1810 SYNTAX OCTET STRING (SIZE(0..2)) 1811 MAX-ACCESS read-only 1812 STATUS current 1813 DESCRIPTION 1814 "A two character language code from ISO 639. Examples EN, GB, 1815 CA, FR, DE." 1816 ::= { prtLocalizationEntry 2 } 1818 prtLocalizationCountry OBJECT-TYPE 1819 SYNTAX OCTET STRING (SIZE(0..2)) 1820 MAX-ACCESS read-only 1821 STATUS current 1822 DESCRIPTION 1823 "A two character country code from ISO 3166, a blank string (two space 1824 characters) shall indicate that the country is not defined. 1825 Examples: US, FR, DE, ..." 1826 ::= { prtLocalizationEntry 3 } 1828 prtLocalizationCharacterSet OBJECT-TYPE 1829 SYNTAX CodedCharSet 1830 MAX-ACCESS read-only 1831 STATUS current 1832 DESCRIPTION 1833 "The coded character set used for this localization." 1834 ::= { prtLocalizationEntry 4 } 1836 -- The System Resources Tables 1838 -- The Printer MIB makes use of the Host MIB to 1839 -- define system resources by referencing the storage 1840 -- and device groups of the print group. In order to 1841 -- determine, amongst multiple printers serviced by 1842 -- one agent, which printer owns a particular 1843 -- resource, the prtStorageRef and prtDeviceRef tables 1844 -- associate particular storage and device entries to 1845 -- printers. 1847 prtStorageRefTable OBJECT-TYPE 1848 draft Printer MIB August 19, 1994 1850 SYNTAX SEQUENCE OF PrtStorageRefEntry 1851 MAX-ACCESS not-accessible 1852 STATUS current 1853 DESCRIPTION 1854 "" 1855 ::= { prtGeneral 2 } 1857 prtStorageRefEntry OBJECT-TYPE 1858 SYNTAX PrtStorageRefEntry 1859 MAX-ACCESS not-accessible 1860 STATUS current 1861 DESCRIPTION 1862 "This table will have an entry for each entry in 1863 the host MIB storage table that represents storage associated 1864 with a printer managed by this agent." 1865 INDEX { hrStorageIndex } 1866 ::= { prtStorageRefTable 1 } 1868 PrtStorageRefEntry ::= SEQUENCE { 1869 prtStorageRefIndex Integer32 1870 } 1872 prtStorageRefIndex OBJECT-TYPE 1873 SYNTAX Integer32 (0..65535) 1874 MAX-ACCESS read-only 1875 STATUS current 1876 DESCRIPTION 1877 "The value of the hrDeviceIndex of the printer device that this 1878 storageEntry is associated with. If this value is 0, then 1879 this storageEntry is associated with more than one printer device." 1880 ::= { prtStorageRefEntry 1 } 1882 prtDeviceRefTable OBJECT-TYPE 1883 SYNTAX SEQUENCE OF PrtDeviceRefEntry 1884 MAX-ACCESS not-accessible 1885 STATUS current 1886 DESCRIPTION 1887 "" 1888 ::= { prtGeneral 3 } 1890 prtDeviceRefEntry OBJECT-TYPE 1891 SYNTAX PrtDeviceRefEntry 1892 MAX-ACCESS not-accessible 1893 STATUS current 1894 DESCRIPTION 1896 draft Printer MIB August 19, 1994 1898 "This table will have an entry for each entry in 1899 the host MIB device table that represents a device associated 1900 with a printer managed by this agent." 1901 INDEX { hrDeviceIndex } 1902 ::= { prtDeviceRefTable 1 } 1904 PrtDeviceRefEntry ::= SEQUENCE { 1905 prtDeviceRefIndex Integer32 1906 } 1908 prtDeviceRefIndex OBJECT-TYPE 1909 SYNTAX Integer32 (0..65535) 1910 MAX-ACCESS read-only 1911 STATUS current 1912 DESCRIPTION 1913 "The value of the hrDeviceIndex of the printer device that this 1914 deviceEntry is associated with. If this value is 0, then 1915 this deviceEntry is associated with more than one printer device." 1916 ::= { prtDeviceRefEntry 1 } 1918 -- The Responsible Party group 1919 -- 1920 -- This group is optional. However, to claim conformance to this 1921 -- group, it is necessary to implement every object in the group. 1923 prtGeneralCurrentOperator OBJECT-TYPE 1924 SYNTAX OCTET STRING (SIZE(0..127)) 1925 MAX-ACCESS read-write 1926 STATUS current 1927 DESCRIPTION 1928 "The name of the current human operator responsible for 1929 operating this printer. It is suggested that this string 1930 include information that would enable other humans to reach 1931 the operator, such as a phone number." 1932 ::= { prtGeneralEntry 4 } 1934 prtGeneralServicePerson OBJECT-TYPE 1935 SYNTAX OCTET STRING (SIZE(0..127)) 1936 MAX-ACCESS read-write 1937 STATUS current 1938 DESCRIPTION 1939 "The name of the last human responsible for servicing 1940 this printer. It is suggested that this string 1941 include information that would enable other humans to reach 1942 the service person, such as a phone number." 1944 draft Printer MIB August 19, 1994 1946 ::= { prtGeneralEntry 5 } 1948 -- The Input Group 1949 -- 1950 -- Input sub-units are managed as a tabular, indexed collection of 1951 -- possible devices capable of providing media for input to the printing 1952 -- process. Input sub-units typically have a location, a type, an 1953 -- identifier, a set of constraints on possible media sizes and 1954 -- potentially other media characteristics, and may be capable of 1955 -- indicating current status or capacity. 1956 -- 1957 -- Implementation of every object in this group is mandatory. 1959 prtInput OBJECT IDENTIFIER ::= { printmib 8 } 1961 prtInputDefaultIndex OBJECT-TYPE 1962 SYNTAX Integer32 (1..65535) 1963 MAX-ACCESS read-write 1964 STATUS current 1965 DESCRIPTION 1966 "The value of prtInputIndex corresponding to the default input 1967 sub-unit: that is, this object selects the default source of 1968 input media." 1969 ::= { prtGeneralEntry 6 } 1971 prtInputTable OBJECT-TYPE 1972 SYNTAX SEQUENCE OF PrtInputEntry 1973 MAX-ACCESS not-accessible 1974 STATUS current 1975 DESCRIPTION 1976 "A table of the devices capable of providing media for input 1977 to the printing process." 1978 ::= { prtInput 2 } 1980 prtInputEntry OBJECT-TYPE 1981 SYNTAX PrtInputEntry 1982 MAX-ACCESS not-accessible 1983 STATUS current 1984 DESCRIPTION 1985 "Attributes of a device capable of providing media for input 1986 to the printing process. 1988 Entries may exist in the table for each device 1989 index who's device type is `printer'." 1991 draft Printer MIB August 19, 1994 1993 INDEX { hrDeviceIndex, prtInputIndex } 1994 ::= { prtInputTable 1 } 1996 PrtInputEntry ::= SEQUENCE { 1997 prtInputIndex Integer32, 1998 prtInputType INTEGER, 1999 prtInputDimUnit MediaUnit, 2000 prtInputMediaDimXFeedDirDeclared Integer32, 2001 prtInputMediaDimFeedDirDeclared Integer32, 2002 prtInputMediaDimXFeedDirChosen Integer32, 2003 prtInputMediaDimFeedDirChosen Integer32, 2004 prtInputCapacityUnit CapacityUnit, 2005 prtInputMaxCapacity Integer32, 2006 prtInputCurrentLevel Integer32, 2007 prtInputStatus SubUnitStatus, 2008 prtInputMediaName OCTET STRING, 2009 prtInputName OCTET STRING, 2010 prtInputVendorName OCTET STRING, 2011 prtInputModel OCTET STRING, 2012 prtInputVersion OCTET STRING, 2013 prtInputSerialNumber OCTET STRING, 2014 prtInputDescription OCTET STRING, 2015 prtInputSecurity PresentOnOff, 2016 prtInputMediaWeight Integer32, 2017 prtInputMediaType OCTET STRING, 2018 prtInputMediaColor OCTET STRING, 2019 prtInputMediaFormParts Integer32 2020 } 2022 prtInputIndex OBJECT-TYPE 2023 SYNTAX Integer32 (1..65535) 2024 MAX-ACCESS not-accessible 2025 STATUS current 2026 DESCRIPTION 2027 "A unique value used by the printer to identify this input sub-unit. 2028 Although these values may change due to a major reconfiguration of 2029 the device (e.g. the addition of new input sub-units to the printer), 2030 values are expected to remain stable across successive printer 2031 power cycles." 2032 ::= { prtInputEntry 1 } 2034 prtInputType OBJECT-TYPE 2035 SYNTAX INTEGER { 2036 other(1), 2037 unknown(2), 2039 draft Printer MIB August 19, 1994 2041 sheetFeedAutoRemovableTray(3), 2042 sheetFeedAutoNonRemovableTray(4), 2043 sheetFeedManual(5), 2044 continuousRoll(6), 2045 continuousFanFold(7) 2046 } 2047 MAX-ACCESS read-only 2048 STATUS current 2049 DESCRIPTION 2050 "The type of technology (discriminated primarily according to feeder 2051 mechanism type) employed by the input sub-unit. Note, the Optional 2052 Input Class provides for a descriptor field to further qualify the 2053 other choice. This value is a type 2 enum." 2054 ::= { prtInputEntry 2 } 2056 prtInputDimUnit OBJECT-TYPE 2057 SYNTAX MediaUnit 2058 MAX-ACCESS read-only 2059 STATUS current 2060 DESCRIPTION 2061 "The unit of measurement for use calculating and relaying 2062 dimensional values for this input sub-unit." 2063 ::= { prtInputEntry 3 } 2065 prtInputMediaDimFeedDirDeclared OBJECT-TYPE 2066 SYNTAX Integer32 2067 MAX-ACCESS read-write 2068 STATUS current 2069 DESCRIPTION 2070 "This object provides the value of the declared dimension, in 2071 the feed direction, of the media that is (or, if empty, was or 2072 will be) in this input sub-unit. The feed direction is the 2073 direction in which the media is fed on this sub-unit. This 2074 dimension is measured in input sub-unit dimensional units 2075 (prtInputDimUnit). If this input sub-unit can reliably sense 2076 this value, the value is sensed by the printer and may not be 2077 changed by management requests. Otherwise, the value may be 2078 changed. The value (-1) means other and specifically means 2079 that this sub-unit places no restriction on this parameter. 2080 The value (-2) indicates unknown." 2081 ::= { prtInputEntry 4 } 2083 prtInputMediaDimXFeedDirDeclared OBJECT-TYPE 2084 SYNTAX Integer32 2085 MAX-ACCESS read-write 2087 draft Printer MIB August 19, 1994 2089 STATUS current 2090 DESCRIPTION 2091 "This object provides the value of the declared dimension, in 2092 the cross feed direction, of the media that is (or, if empty, 2093 was or will be) in this input sub-unit. The cross feed 2094 direction is ninety degrees relative to the feed direction 2095 associated with this sub-unit. This dimension is measured in 2096 input sub-unit dimensional units (prtInputDimUnit). If this 2097 input sub-unit can reliably sense this value, the value is 2098 sensed by the printer and may not be changed by management 2099 requests. Otherwise, the value may be changed. The value (-1) 2100 means other and specifically means that this sub-unit places 2101 no restriction on this parameter. The value (-2) indicates 2102 unknown." 2103 ::= { prtInputEntry 5 } 2105 prtInputMediaDimFeedDirChosen OBJECT-TYPE 2106 SYNTAX Integer32 2107 MAX-ACCESS read-only 2108 STATUS current 2109 DESCRIPTION 2110 "The printer will act as if media of the chosen dimension (in 2111 the feed direction) is present in this input source. Note 2112 that this value will be used even if the input tray is empty. 2113 Feed dimension measurements 2114 are taken parallel relative to the feed direction 2115 associated with that sub-unit and are in input sub-unit 2116 dimensional units (DimUnit). If the printer supports the 2117 declared dimension, the granted dimension is the same as 2118 the declared dimension. If not, the granted dimension is 2119 set to the closest dimension that the printer supports 2120 when the declared dimension is set. The value (-1) means 2121 other and specifically indicates that this sub-unit 2122 places no restriction on this parameter. The value (-2) 2123 indicates unknown." 2124 ::= { prtInputEntry 6 } 2126 prtInputMediaDimXFeedDirChosen OBJECT-TYPE 2127 SYNTAX Integer32 2128 MAX-ACCESS read-only 2129 STATUS current 2130 DESCRIPTION 2131 "The printer will act as if media of the chosen dimension (in 2132 the cross feed direction) is present in this input source. 2133 Note that this value will be used even if the input tray is 2135 draft Printer MIB August 19, 1994 2137 empty. The cross feed direction is ninety degrees relative 2138 to the feed direction associated with this sub-unit. This 2139 dimension is measured in input sub-unit dimensional units 2140 (DimUnit). If the printer supports the declared 2141 dimension, the granted dimension is the same as the 2142 declared dimension. If not, the granted dimension is set 2143 to the closest dimension that the printer supports when 2144 the declared dimension is set. The value (-1) means other 2145 and specifically indicates that this sub-unit places no 2146 restriction on this parameter. The value (-2) indicates 2147 unknown." 2148 ::= { prtInputEntry 7 } 2150 prtInputCapacityUnit OBJECT-TYPE 2151 SYNTAX CapacityUnit 2152 MAX-ACCESS read-only 2153 STATUS current 2154 DESCRIPTION 2155 "The unit of measurement for use in calculating and relaying capacity 2156 values for this input sub-unit." 2157 ::= { prtInputEntry 8 } 2159 prtInputMaxCapacity OBJECT-TYPE 2160 SYNTAX Integer32 2161 MAX-ACCESS read-write 2162 STATUS current 2163 DESCRIPTION 2164 "The maximum capacity of the input sub-unit in input 2165 sub-unit capacity units (CapacityUnit). There is no 2166 convention associated with the media itself so this value 2167 reflects claimed capacity. If this input sub-unit can 2168 reliably sense this value, the value is sensed by the 2169 printer and may not be changed by management requests; 2170 otherwise, the value may be written (by a Remote 2171 Contol Panel or a Management Application). 2172 The value (-1) means other and specifically 2173 indicates that the sub-unit places no restrictions 2174 on this parameter. The value (-2) means unknown." 2175 ::= { prtInputEntry 9 } 2177 prtInputCurrentLevel OBJECT-TYPE 2178 SYNTAX Integer32 -- in capacity units (CapacityUnit). 2179 MAX-ACCESS read-write 2180 STATUS current 2181 DESCRIPTION 2183 draft Printer MIB August 19, 1994 2185 "The current capacity of the input sub-unit in input 2186 sub-unit capacity units (CapacityUnit). If this input 2187 sub-unit can reliably sense this value, the value is 2188 sensed by the printer and may not be changed by 2189 management requests; otherwise, the value may 2190 be written (by a Remote Contol Panel or a 2191 Management Application). The value (-1) means other and 2192 specifically indicates that the sub-unit places no 2193 restrictions on this parameter. The value (-2) means unknown. 2194 The value (-3) means that the printer knows that at least one 2195 unit remains." 2196 ::= { prtInputEntry 10 } 2198 prtInputStatus OBJECT-TYPE 2199 SYNTAX SubUnitStatus 2200 MAX-ACCESS read-only 2201 STATUS current 2202 DESCRIPTION 2203 "The current status of this input sub-unit." 2204 ::= { prtInputEntry 11 } 2206 prtInputMediaName OBJECT-TYPE 2207 SYNTAX OCTET STRING (SIZE(0..63)) 2208 MAX-ACCESS read-write 2209 STATUS current 2210 DESCRIPTION 2211 "A description of the media contained in this input sub-unit; 2212 This description is intended for display to a human operator. 2213 This description is not processed by the printer. It is used 2214 to provide information not expressible in terms of the other 2215 media attributes (e.g. prtInputMediaDimFeedDirChosen, 2216 prtInputMediaDimXFeedDirChosen, prtInputMediaWeight, 2217 prtInputMediaType). An example would be `Hillary's Pink 2218 Presidential Letterhead'." 2219 ::= { prtInputEntry 12 } 2221 -- INPUT MEASUREMENT 2222 -- 2223 -- _______ | | 2224 -- ^ | | 2225 -- | | | | 2226 -- | |_ _ _ _ _ _ _ _ _ _ _| _________________ |direction 2227 -- | | | ^ v 2228 -- MaxCapacity | | | 2229 -- | | Sheets left in tray | CurrentLevel 2230 draft Printer MIB August 19, 1994 2232 -- | | | | 2233 -- v | | v 2234 -- _______ +_____________________+ _______ 2236 -- The Extended Input Group 2237 -- 2238 -- This group is optional. However, to claim conformance to this 2239 -- group, it is necessary to implement every object in the group. 2241 prtInputName OBJECT-TYPE 2242 SYNTAX OCTET STRING (SIZE(0..63)) 2243 MAX-ACCESS read-write 2244 STATUS current 2245 DESCRIPTION 2246 "The name assigned to this input sub-unit." 2247 ::= { prtInputEntry 13 } 2249 prtInputVendorName OBJECT-TYPE 2250 SYNTAX OCTET STRING (SIZE(0..63)) 2251 MAX-ACCESS read-only 2252 STATUS current 2253 DESCRIPTION 2254 "The vendor name of this input sub-unit." 2255 ::= { prtInputEntry 14 } 2257 prtInputModel OBJECT-TYPE 2258 SYNTAX OCTET STRING (SIZE(0..63)) 2259 MAX-ACCESS read-only 2260 STATUS current 2261 DESCRIPTION 2262 "The model name of this input sub-unit." 2263 ::= { prtInputEntry 15 } 2265 prtInputVersion OBJECT-TYPE 2266 SYNTAX OCTET STRING (SIZE(0..63)) 2267 MAX-ACCESS read-only 2268 STATUS current 2269 DESCRIPTION 2270 "The version of this input sub-unit." 2271 ::= { prtInputEntry 16 } 2273 prtInputSerialNumber OBJECT-TYPE 2274 SYNTAX OCTET STRING (SIZE(0..32)) 2275 MAX-ACCESS read-only 2277 draft Printer MIB August 19, 1994 2279 STATUS current 2280 DESCRIPTION 2281 "The serial number assigned to this input sub-unit." 2282 ::= { prtInputEntry 17 } 2284 prtInputDescription OBJECT-TYPE 2285 SYNTAX OCTET STRING (SIZE(0..255)) 2286 MAX-ACCESS read-only 2287 STATUS current 2288 DESCRIPTION 2289 "A free-form text description of this input 2290 sub-unit in the localization specified by 2291 prtGeneralCurrentLocalization." 2292 ::= { prtInputEntry 18 } 2294 prtInputSecurity OBJECT-TYPE 2295 SYNTAX PresentOnOff 2296 MAX-ACCESS read-write 2297 STATUS current 2298 DESCRIPTION 2299 "Indicates if this input sub-unit has some security 2300 associated with it." 2301 ::= { prtInputEntry 19 } 2303 -- The Input Media Group 2304 -- 2305 -- The Input Media Group supports identification of media installed or 2306 -- available for use on a printing device. Medium resources are identified 2307 -- by name, and include a collection of characteristic attributes that may 2308 -- further be used for selection and management of them. The Input 2309 -- Media group consists of a set of optional "columns" in the 2310 -- Input Table. In this manner, a minimally conforming implementation 2311 -- may choose to not support reporting of media resources if it cannot 2312 -- do so. 2313 -- 2314 -- This group is optional. However, to claim conformance to this 2315 -- group, it is necessary to implement every object in the group. 2317 prtInputMediaWeight OBJECT-TYPE 2318 SYNTAX Integer32 2319 MAX-ACCESS read-write 2320 STATUS current 2321 DESCRIPTION 2322 "The weight of the medium associated with this input 2323 sub-unit in grams / per meter squared. The value (-2) means 2325 draft Printer MIB August 19, 1994 2327 unknown." 2328 ::= { prtInputEntry 20 } 2330 prtInputMediaType OBJECT-TYPE 2331 SYNTAX OCTET STRING (SIZE(0..63)) 2332 MAX-ACCESS read-write 2333 STATUS current 2334 DESCRIPTION 2335 "The name of the type of medium associated with this input 2336 sub-unit. This name need not be processed by the printer; it 2337 might simply be displayed to an operator. The standardized 2338 string values from ISO 10175 (DPA) and ISO 10180 (SPDL) are: 2340 stationery Separately cut sheets of an opaque material 2341 transparency Separately cut sheets of a transparent material 2342 envelope Envelopes that can be used for conventional 2343 mailing purposes 2344 envelope-plain Envelopes that are not preprinted and have no windows 2345 envelope-window Envelopes that have windows for addressing purposes 2346 continuous-long Continuously connected sheets of an opaque material 2347 connected along the long edge 2348 continuous-short Continuously connected sheets of an opaque 2349 material connected along the short edge 2350 tab-stock Media with tabs 2351 multi-part-form Form medium composed of multiple layers not 2352 pre-attached to one another; each sheet may be 2353 drawn separately from an input source 2354 labels Label stock 2355 multi-layer Form medium composed of multiple layers which are 2356 pre- attached to one another; e.g., for use with 2357 impact printers" 2358 ::= { prtInputEntry 21 } 2360 prtInputMediaColor OBJECT-TYPE 2361 SYNTAX OCTET STRING (SIZE(0..63)) 2362 MAX-ACCESS read-write 2363 STATUS current 2364 DESCRIPTION 2365 "The name of the color of the medium associated with 2366 this input sub-unit using standardized string values 2367 from ISO 10175 (DPA) and ISO 10180 (SPDL) which are: 2369 other 2370 unknown 2371 white 2373 draft Printer MIB August 19, 1994 2375 pink 2376 yellow 2377 buff 2378 goldenrod 2379 blue 2380 green 2381 transparent 2383 Implementors may add additional string values. The naming conventions 2384 in ISO 9070 are recommended in order to avoid potential name clashes." 2385 ::= { prtInputEntry 22 } 2387 prtInputMediaFormParts OBJECT-TYPE 2388 SYNTAX Integer32 2389 MAX-ACCESS read-write 2390 STATUS current 2391 DESCRIPTION 2392 "The number of parts associated with the medium 2393 associated with this input sub-unit if the medium is a 2394 multi-part form. The value (-1) means other and 2395 specifically indicates that the device places no 2396 restrictions on this parameter. The value (-2) means 2397 unknown." 2398 ::= { prtInputEntry 23 } 2400 -- The Output Group 2401 -- 2402 -- Output sub-units are managed as a tabular, indexed collection of 2403 -- possible devices capable of receiving media delivered from the printing 2404 -- process. Output sub-units typically have a location, a type, an 2405 -- identifier, a set of constraints on possible media sizes and 2406 -- potentially other characteristics, and may be capable of indicating 2407 -- current status or capacity. 2408 -- 2409 -- Implementation of every object in this group is mandatory. 2411 prtOutput OBJECT IDENTIFIER ::= { printmib 9 } 2413 prtOutputDefaultIndex OBJECT-TYPE 2414 SYNTAX Integer32 2415 MAX-ACCESS read-write 2416 STATUS current 2417 DESCRIPTION 2418 "The value of prtOutputIndex corresponding to the default 2419 output sub-unit; that is, this object selects the default 2421 draft Printer MIB August 19, 1994 2423 output destination." 2424 ::= { prtGeneralEntry 7 } 2426 prtOutputTable OBJECT-TYPE 2427 SYNTAX SEQUENCE OF PrtOutputEntry 2428 MAX-ACCESS not-accessible 2429 STATUS current 2430 DESCRIPTION 2431 "A table of the devices capable of receiving media delivered 2432 from the printing process." 2433 ::= { prtOutput 2 } 2435 prtOutputEntry OBJECT-TYPE 2436 SYNTAX PrtOutputEntry 2437 MAX-ACCESS not-accessible 2438 STATUS current 2439 DESCRIPTION 2440 "Attributes of a device capable of receiving media delivered 2441 from the printing process. 2443 Entries may exist in the table for each device 2444 index who's device type is `printer'." 2445 INDEX { hrDeviceIndex, prtOutputIndex } 2446 ::= { prtOutputTable 1 } 2448 PrtOutputEntry ::= SEQUENCE { 2449 prtOutputIndex Integer32, 2450 prtOutputType INTEGER, 2451 prtOutputCapacityUnit CapacityUnit, 2452 prtOutputMaxCapacity Integer32, 2453 prtOutputRemainingCapacity Integer32, 2454 prtOutputStatus SubUnitStatus, 2455 prtOutputName OCTET STRING, 2456 prtOutputVendorName OCTET STRING, 2457 prtOutputModel OCTET STRING, 2458 prtOutputVersion OCTET STRING, 2459 prtOutputSerialNumber OCTET STRING, 2460 prtOutputDescription OCTET STRING, 2461 prtOutputSecurity PresentOnOff, 2462 prtOutputDimUnit MediaUnit, 2463 prtOutputMaxDimFeedDir Integer32, 2464 prtOutputMaxDimXFeedDir Integer32, 2465 prtOutputMinDimFeedDir Integer32, 2466 prtOutputMinDimXFeedDir Integer32, 2467 prtOutputStackingOrder INTEGER, 2469 draft Printer MIB August 19, 1994 2471 prtOutputPageDeliveryOrientation INTEGER, 2472 prtOutputBursting PresentOnOff, 2473 prtOutputDecollating PresentOnOff, 2474 prtOutputPageCollated PresentOnOff, 2475 prtOutputOffsetStacking PresentOnOff 2476 } 2478 prtOutputIndex OBJECT-TYPE 2479 SYNTAX Integer32 2480 MAX-ACCESS not-accessible 2481 STATUS current 2482 DESCRIPTION 2483 "A unique value used by this printer to identify this 2484 output sub-unit. Although these values may change due 2485 to a major reconfiguration of the sub-unit (e.g. the 2486 addition of new output devices to the printer), values 2487 are expected to remain stable across successive printer 2488 power cycles." 2489 ::= { prtOutputEntry 1 } 2491 prtOutputType OBJECT-TYPE 2492 SYNTAX INTEGER { 2493 other(1), 2494 unknown(2), 2495 removableBin(3), 2496 unRemovableBin(4), 2497 continuousRollDevice(5), 2498 mailBox(6) 2499 } 2500 MAX-ACCESS read-only 2501 STATUS current 2502 DESCRIPTION 2503 "The type of technology supported by this output sub-unit. 2504 This value is a type 2 enum." 2505 ::= { prtOutputEntry 2 } 2507 prtOutputCapacityUnit OBJECT-TYPE 2508 SYNTAX CapacityUnit 2509 MAX-ACCESS read-only 2510 STATUS current 2511 DESCRIPTION 2512 "The unit of measurement for use in calculating and relaying 2513 capacity values for this output sub-unit." 2514 ::= { prtOutputEntry 3 } 2516 draft Printer MIB August 19, 1994 2518 prtOutputMaxCapacity OBJECT-TYPE 2519 SYNTAX Integer32 2520 MAX-ACCESS read-write 2521 STATUS current 2522 DESCRIPTION 2523 "The maximum capacity of this output sub-unit in output 2524 sub-unit capacity units (CapacityUnit). There is no 2525 convention associated with the media itself so this value 2526 essentially reflects claimed capacity. If this output 2527 sub-unit can reliably sense this value, the value is 2528 sensed by the printer and may not be changed by management 2529 requests; otherwise, the value may be written 2530 (by a Remote Contol Panel or a Management Application). 2531 The value (-1) means other and specifically indicates 2532 that the sub-unit places no restrictions on this parameter. 2533 The value (-2) means unknown." 2534 ::= { prtOutputEntry 4 } 2536 prtOutputRemainingCapacity OBJECT-TYPE 2537 SYNTAX Integer32 2538 MAX-ACCESS read-write 2539 STATUS current 2540 DESCRIPTION 2541 "The remaining capacity of the possible output sub-unit 2542 capacity in output sub-unit capacity units (CapacityUnit) 2543 of this output sub-unit. If this output sub-unit can 2544 reliably sense this value, the value is sensed by the 2545 printer and may not be modified by management requests; 2546 otherwise, the value may be written (by 2547 a Remote Contol Panel or a Management 2548 Application). The value (-1) means other and 2549 specifically indicates that the sub-unit places no 2550 restrictions on this parameter. The value (-2) means 2551 unknown. The value (-3) means that the printer knows that 2552 there remains capacity for at least one unit." 2553 ::= { prtOutputEntry 5 } 2555 prtOutputStatus OBJECT-TYPE 2556 SYNTAX SubUnitStatus 2557 MAX-ACCESS read-only 2558 STATUS current 2559 DESCRIPTION 2560 "The current status of this output sub-unit." 2561 ::= { prtOutputEntry 6 } 2563 draft Printer MIB August 19, 1994 2565 -- OUTPUT MEASUREMENT 2566 -- 2567 -- _______ | | _______ 2568 -- ^ | | ^ 2569 -- | | | | 2570 -- | | | RemainingCapacity 2571 -- MaxCapacity | | | 2572 -- | | | v ^ 2573 -- | |_ _ _ _ _ _ _ _ _ _ _| ___________________ |direction 2574 -- | | | | 2575 -- | | Sheets in output | 2576 -- v | | 2577 -- _______ +_____________________+ 2579 -- The Extended Output Group 2580 -- 2581 -- This group is optional. However, to claim conformance to this 2582 -- group, it is necessary to implement every object in the group. 2584 prtOutputName OBJECT-TYPE 2585 SYNTAX OCTET STRING (SIZE(0..63)) 2586 MAX-ACCESS read-write 2587 STATUS current 2588 DESCRIPTION 2589 "The name assigned to this output sub-unit." 2590 ::= { prtOutputEntry 7 } 2592 prtOutputVendorName OBJECT-TYPE 2593 SYNTAX OCTET STRING (SIZE(0..63)) 2594 MAX-ACCESS read-only 2595 STATUS current 2596 DESCRIPTION 2597 "The vendor name of this output sub-unit." 2598 ::= { prtOutputEntry 8 } 2600 prtOutputModel OBJECT-TYPE 2601 SYNTAX OCTET STRING (SIZE(0..63)) 2602 MAX-ACCESS read-only 2603 STATUS current 2604 DESCRIPTION 2605 "The name assigned to this output sub-unit." 2606 ::= { prtOutputEntry 9 } 2608 prtOutputVersion OBJECT-TYPE 2609 SYNTAX OCTET STRING (SIZE(0..63)) 2611 draft Printer MIB August 19, 1994 2613 MAX-ACCESS read-only 2614 STATUS current 2615 DESCRIPTION 2616 "The version of this output sub-unit." 2617 ::= { prtOutputEntry 10 } 2619 prtOutputSerialNumber OBJECT-TYPE 2620 SYNTAX OCTET STRING (SIZE(0..63)) 2621 MAX-ACCESS read-only 2622 STATUS current 2623 DESCRIPTION 2624 "The serial number assigned to this output sub-unit." 2625 ::= { prtOutputEntry 11 } 2627 prtOutputDescription OBJECT-TYPE 2628 SYNTAX OCTET STRING (SIZE(0..255)) 2629 MAX-ACCESS read-only 2630 STATUS current 2631 DESCRIPTION 2632 " A free-form text description of this output sub-unit in the 2633 localization specified by prtGeneralCurrentLocalization." 2634 ::= { prtOutputEntry 12 } 2636 prtOutputSecurity OBJECT-TYPE 2637 SYNTAX PresentOnOff 2638 MAX-ACCESS read-write 2639 STATUS current 2640 DESCRIPTION 2641 "Indicates if this output sub-unit has some security associated 2642 with it and if that security is enabled or not." 2643 ::= { prtOutputEntry 13 } 2645 -- The Output Dimensions Group 2646 -- 2647 -- This group is optional. However, to claim conformance to this 2648 -- group, it is necessary to implement every object in the group. 2650 prtOutputDimUnit OBJECT-TYPE 2651 SYNTAX MediaUnit 2652 MAX-ACCESS read-only 2653 STATUS current 2654 DESCRIPTION 2655 "The unit of measurement for use in calculating and relaying 2656 dimensional values for this output sub-unit." 2657 ::= { prtOutputEntry 14 } 2659 draft Printer MIB August 19, 1994 2661 prtOutputMaxDimFeedDir OBJECT-TYPE 2662 SYNTAX Integer32 2663 MAX-ACCESS read-write 2664 STATUS current 2665 DESCRIPTION 2666 "The maximum dimensions supported by this output sub-unit 2667 for measurements taken parallel relative to the feed 2668 direction associated with that sub-unit in output 2669 sub-unit dimensional units (DimUnit). If this output 2670 sub-unit can reliably sense this value, the value is 2671 sensed by the printer and may not be changed with 2672 management protocol operations." 2673 ::= { prtOutputEntry 15 } 2675 prtOutputMaxDimXFeedDir OBJECT-TYPE 2676 SYNTAX Integer32 2677 MAX-ACCESS read-write 2678 STATUS current 2679 DESCRIPTION 2680 "The maximum dimensions supported by this output sub-unit 2681 for measurements taken ninety degrees relative to the 2682 feed direction associated with that sub-unit in output 2683 sub-unit dimensional units (DimUnit). If this output 2684 sub-unit can reliably sense this value, the value is 2685 sensed by the printer and may not be changed with 2686 management protocol operations." 2687 ::= { prtOutputEntry 16 } 2689 prtOutputMinDimFeedDir OBJECT-TYPE 2690 SYNTAX Integer32 2691 MAX-ACCESS read-write 2692 STATUS current 2693 DESCRIPTION 2694 "The minimum dimensions supported by this output sub-unit 2695 for measurements taken parallel relative to the feed 2696 direction associated with that sub-unit in output 2697 sub-unit dimensional units (DimUnit). If this output 2698 sub-unit can reliably sense this value, the value is 2699 sensed by the printer and may not be changed with 2700 management protocol operations." 2701 ::= { prtOutputEntry 17 } 2703 prtOutputMinDimXFeedDir OBJECT-TYPE 2704 SYNTAX Integer32 2705 MAX-ACCESS read-write 2707 draft Printer MIB August 19, 1994 2709 STATUS current 2710 DESCRIPTION 2711 "The minimum dimensions supported by this output sub-unit 2712 for measurements taken ninety degrees relative to the 2713 feed direction associated with that sub-unit in output 2714 sub-unit dimensional units (DimUnit). If this output 2715 sub-unit can reliably sense this value, the value is 2716 sensed by the printer and may not be changed with 2717 management protocol operations." 2718 ::= { prtOutputEntry 18 } 2720 -- The Output Features Group 2721 -- 2722 -- This group is optional. However, to claim conformance to this 2723 -- group, it is necessary to implement every object in the group. 2725 prtOutputStackingOrder OBJECT-TYPE 2726 SYNTAX INTEGER { 2727 unknown(2), 2728 firstToLast(3), 2729 lastToFirst(4) 2730 } 2731 MAX-ACCESS read-write 2732 STATUS current 2733 DESCRIPTION 2734 "The current state of the stacking order for the 2735 associated output sub-unit. `FirstToLast' means 2736 that as pages are output the front of the next page is 2737 placed against the back of the previous page. 2738 `LasttoFirst' means that as pages are output the back 2739 of the next page is placed against the front of the 2740 previous page. This value is a type 1 enum." 2741 ::= { prtOutputEntry 19 } 2743 prtOutputPageDeliveryOrientation OBJECT-TYPE 2744 SYNTAX INTEGER { 2745 faceUp(3), 2746 faceDown(4) 2747 } 2748 MAX-ACCESS read-write 2749 STATUS current 2750 DESCRIPTION 2751 "The reading surface that will be `up' when pages are 2752 delivered to the associated output sub-unit. Values are 2753 Face-Up and Face-Down. (Note: interpretation of these 2755 draft Printer MIB August 19, 1994 2757 values is in general context-dependent based on locale; 2758 presentation of these values to an end-user should be 2759 normalized to the expectations of the user). This value 2760 is a type 1 enum." 2761 ::= { prtOutputEntry 20 } 2763 prtOutputBursting OBJECT-TYPE 2764 SYNTAX PresentOnOff 2765 MAX-ACCESS read-write 2766 STATUS current 2767 DESCRIPTION 2768 "This object indicates that the outputing sub-unit 2769 supports bursting, and if so, whether the feature is enabled. 2770 Bursting is the process by which continuous media is separated into 2771 individual sheets, typically by bursting along pre-formed 2772 perforations." 2773 ::= { prtOutputEntry 21 } 2775 prtOutputDecollating OBJECT-TYPE 2776 SYNTAX PresentOnOff 2777 MAX-ACCESS read-write 2778 STATUS current 2779 DESCRIPTION 2780 "This object indicates that the output supports 2781 supports decollating, and if so, whether the feature 2782 is enabled. Decollating is the process by which the 2783 individual parts within a multi-part form are separated 2784 and sorted into separate stacks for each part." 2785 ::= { prtOutputEntry 22 } 2787 prtOutputPageCollated OBJECT-TYPE 2788 SYNTAX PresentOnOff 2789 MAX-ACCESS read-write 2790 STATUS current 2791 DESCRIPTION 2792 "This object indicates that the output sub-unit 2793 supports page collation, and if so, whether the feature is 2794 enabled." 2795 ::= { prtOutputEntry 23 } 2797 prtOutputOffsetStacking OBJECT-TYPE 2798 SYNTAX PresentOnOff 2799 MAX-ACCESS read-write 2800 STATUS current 2801 DESCRIPTION 2803 draft Printer MIB August 19, 1994 2805 "This object indicates that the output supports 2806 supports offset stacking, and if so, whether the feature is 2807 enabled." 2808 ::= { prtOutputEntry 24 } 2810 -- The Marker Group 2811 -- 2812 -- A marker is the mechanism that produces marks on the print media. The 2813 -- marker sub-units and their associated supplies are represented by the 2814 -- Marker Group in the model. A printer can contain one or more marking 2815 -- mechanisms. Some examples of multiple marker sub-units are: a printer 2816 -- with separate markers for normal and magnetic ink or an imagesetter 2817 -- that can output to both a proofing device and final film. Each marking 2818 -- device can have its own set of characteristics associated with it, 2819 -- such as marking technology and resolution. 2820 -- 2821 -- Implementation of every object in this group is mandatory. 2823 prtMarker OBJECT IDENTIFIER ::= { printmib 10 } 2825 prtMarkerDefaultIndex OBJECT-TYPE 2826 SYNTAX Integer32 (1..65535) 2827 MAX-ACCESS read-write 2828 STATUS current 2829 DESCRIPTION 2830 "The value of prtMarkerIndex corresponding to the 2831 default markersub-unit; that is, this object selects the 2832 default marker." 2833 ::= { prtGeneralEntry 8 } 2835 -- The printable area margins as listed below define an area of the print 2836 -- media which is guaranteed to be printable for all combinations of 2837 -- input, media paths, and interpreters for this marker. 2839 prtMarkerTable OBJECT-TYPE 2840 SYNTAX SEQUENCE OF PrtMarkerEntry 2841 MAX-ACCESS not-accessible 2842 STATUS current 2843 DESCRIPTION 2844 "" 2845 ::= { prtMarker 2 } 2847 prtMarkerEntry OBJECT-TYPE 2848 SYNTAX PrtMarkerEntry 2849 MAX-ACCESS not-accessible 2851 draft Printer MIB August 19, 1994 2853 STATUS current 2854 DESCRIPTION 2855 "Entries may exist in the table for each device 2856 index who's device type is `printer'." 2857 INDEX { hrDeviceIndex, prtMarkerIndex } 2858 ::= { prtMarkerTable 1 } 2860 PrtMarkerEntry ::= SEQUENCE { 2861 prtMarkerIndex Integer32, 2862 prtMarkerMarkTech INTEGER, 2863 prtMarkerCounterUnit INTEGER, 2864 prtMarkerLifeCount Counter32, 2865 prtMarkerPowerOnCount Counter32, 2866 prtMarkerProcessColorants Integer32, 2867 prtMarkerSpotColorants Integer32, 2868 prtMarkerAddressabilityUnit INTEGER, 2869 prtMarkerAddressabilityFeedDir Integer32, 2870 prtMarkerAddressabilityXFeedDir Integer32, 2871 prtMarkerNorthMargin Integer32, 2872 prtMarkerSouthMargin Integer32, 2873 prtMarkerWestMargin Integer32, 2874 prtMarkerEastMargin Integer32, 2875 prtMarkerStatus SubUnitStatus 2876 } 2878 prtMarkerIndex OBJECT-TYPE 2879 SYNTAX Integer32 (1..65535) 2880 MAX-ACCESS not-accessible 2881 STATUS current 2882 DESCRIPTION 2883 "A unique value used by the printer to identify this marking 2884 SubUnitStatus. Although these values may change due to a major 2885 reconfiguration of the device (e.g. the addition of new marking 2886 sub-units to the printer), values are expected to remain stable across 2887 successive printer power cycles." 2888 ::= { prtMarkerEntry 1 } 2890 prtMarkerMarkTech OBJECT-TYPE 2891 SYNTAX INTEGER { 2892 other(1), 2893 unknown(2), 2894 electrophotographicLED(3), 2895 electrophotographicLaser(4), 2896 electrophotographicOther(5), 2898 draft Printer MIB August 19, 1994 2900 impactMovingHeadDotMatrix9pin(6), 2901 impactMovingHeadDotMatrix24pin(7), 2902 impactMovingHeadDotMatrixOther(8), 2903 impactMovingHeadFullyFormed(9), 2904 impactBand(10), 2905 impactOther(11), 2906 inkjetAqueous(12), 2907 inkjetSolid(13), 2908 inkjetOther(14), 2909 pen(15), 2910 thermalTransfer(16), 2911 thermalSensitive(17), 2912 thermalDiffusion(18), 2913 thermalOther(19), 2914 electroerosion(20), 2915 electrostatic(21), 2916 photographicMicrofiche(22), 2917 photographicImagesetter(23), 2918 photographicOther(24), 2919 ionDeposition(25), 2920 eBeam(26), 2921 typesetter(27) 2922 } 2923 MAX-ACCESS read-only 2924 STATUS current 2925 DESCRIPTION 2926 "The type of marking technology used for this marking sub-unit. 2927 This value is a type 2 enum." 2928 ::= { prtMarkerEntry 2 } 2930 prtMarkerCounterUnit OBJECT-TYPE 2931 SYNTAX INTEGER { 2932 tenThousandthsOfInches(3), -- .0001 2933 micrometers(4), 2934 characters(5), 2935 lines(6), 2936 impressions(7), 2937 sheets(8), 2938 dotRow(9), 2939 hours(11), 2940 feet(16), 2941 meters(17) 2942 } 2943 MAX-ACCESS read-only 2944 STATUS current 2946 draft Printer MIB August 19, 1994 2948 DESCRIPTION 2949 "The unit that will be used by the printer when reporting 2950 counter values for this marking sub-unit. The 2951 time units of measure are provided for a device like a 2952 strip recorder that does not or cannot track the physical 2953 dimensions of the media and does not use characters, 2954 lines or sheets. This value is a type 1 enum." 2955 ::= { prtMarkerEntry 3} 2957 prtMarkerLifeCount OBJECT-TYPE 2958 SYNTAX Counter32 2959 MAX-ACCESS read-only 2960 STATUS current 2961 DESCRIPTION 2962 "The count of the number of units of measure counted during 2963 the life of printer using units of measure as specified by 2964 CounterUnit." 2965 ::= { prtMarkerEntry 4 } 2967 prtMarkerPowerOnCount OBJECT-TYPE 2968 SYNTAX Counter32 2969 MAX-ACCESS read-only 2970 STATUS current 2971 DESCRIPTION 2972 "The count of the number of units of measure counted since the 2973 equipment was most recently powered on using units of measure as 2974 specified by CounterUnit." 2975 ::= { prtMarkerEntry 5 } 2977 prtMarkerProcessColorants OBJECT-TYPE 2978 SYNTAX Integer32 (0..65535) 2979 MAX-ACCESS read-only 2980 STATUS current 2981 DESCRIPTION 2982 "The number of process colors supported by this marker. A 2983 process color of 1 implies monochrome. The value of this object and 2984 SpotColorants cannot both be 0. Must be 0 or greater." 2985 ::= { prtMarkerEntry 6 } 2987 prtMarkerSpotColorants OBJECT-TYPE 2988 SYNTAX Integer32 (0..65535) 2989 MAX-ACCESS read-only 2990 STATUS current 2991 DESCRIPTION 2992 "The number of spot colors supported by this marker. The 2994 draft Printer MIB August 19, 1994 2996 value of this object and ProcessColorants cannot 2997 both be 0. Must be 0 or greater." 2998 ::= { prtMarkerEntry 7 } 3000 prtMarkerAddressabilityUnit OBJECT-TYPE 3001 SYNTAX INTEGER { 3002 tenThousandthsOfInches(3), -- .0001 3003 micrometers(4) 3004 } 3005 MAX-ACCESS read-only 3006 STATUS current 3007 DESCRIPTION 3008 "The unit of measure of distances. This value is a 3009 type 1 enum." 3010 ::= { prtMarkerEntry 8 } 3012 prtMarkerAddressabilityFeedDir OBJECT-TYPE 3013 SYNTAX Integer32 3014 MAX-ACCESS read-only 3015 STATUS current 3016 DESCRIPTION 3017 "The number of addressable marking positions in the feed 3018 direction per 10000 units of measure specified by 3019 AddressabilityUnit. A value of (-1) implies 'other' or 3020 'infinite' while a value of (-2) implies 'unknown'." 3021 ::= { prtMarkerEntry 9 } 3023 prtMarkerAddressabilityXFeedDir OBJECT-TYPE 3024 SYNTAX Integer32 3025 MAX-ACCESS read-only 3026 STATUS current 3027 DESCRIPTION 3028 "The number of addressable marking positions in the cross 3029 feed direction in 10000 units of measure specified by 3030 AddressabilityUnit. A value of (-1) implies 'other' or 3031 'infinite' while a value of (-2) implies 'unknown'." 3032 ::= { prtMarkerEntry 10 } 3034 prtMarkerNorthMargin OBJECT-TYPE 3035 SYNTAX Integer32 3036 MAX-ACCESS read-only 3037 STATUS current 3038 DESCRIPTION 3039 "The margin, in units identified by AddressabilityUnit, 3040 from the leading edge of the medium as the medium flows 3042 draft Printer MIB August 19, 1994 3044 throught the marking engine with the side to be imaged 3045 facing the observer. The leading edge is the North edge 3046 and the other edges are defined by the normal compass 3047 layout of directions with the compass facing the 3048 observer. Printing within the area bounded by all four 3049 margins is guaranteed for all interpreters. The value 3050 (-2) means unknown." 3051 ::= { prtMarkerEntry 11 } 3053 prtMarkerSouthMargin OBJECT-TYPE 3054 SYNTAX Integer32 3055 MAX-ACCESS read-only 3056 STATUS current 3057 DESCRIPTION 3058 "The margin from the South edge (see NorthMargin) 3059 of the medium in units identified by 3060 AddressabilityUnit. Printing within the area bounded by 3061 all four margins is guaranteed for all interpreters. 3062 The value (-2) means unknown." 3063 ::= { prtMarkerEntry 12 } 3065 prtMarkerWestMargin OBJECT-TYPE 3066 SYNTAX Integer32 3067 MAX-ACCESS read-only 3068 STATUS current 3069 DESCRIPTION 3070 "The margin from the West edge (see NorthMargin) of the 3071 medium in units identified by AddressabilityUnit. 3072 Printing within the area bouned by all four margins is 3073 guaranteed for all interpreters. The value (-2) means 3074 unknown." 3075 ::= { prtMarkerEntry 13 } 3077 prtMarkerEastMargin OBJECT-TYPE 3078 SYNTAX Integer32 3079 MAX-ACCESS read-only 3080 STATUS current 3081 DESCRIPTION 3082 "The margin from the East edge (see NorthMargin) of the 3083 medium in units identified by AddressabilityUnit. 3084 Printing within the area bounded by all four margins is 3085 guaranteed for all interpreters. The value (-2) means 3086 unknown." 3087 ::= { prtMarkerEntry 14 } 3089 draft Printer MIB August 19, 1994 3091 prtMarkerStatus OBJECT-TYPE 3092 SYNTAX SubUnitStatus 3093 MAX-ACCESS read-only 3094 STATUS current 3095 DESCRIPTION 3096 "The current status of this marker sub-unit." 3097 ::= { prtMarkerEntry 15 } 3099 -- The Marker Supplies Group 3100 -- 3101 -- This group is optional. However, to claim conformance to this 3102 -- group, it is necessary to implement every object in the group. 3104 prtMarkerSupplies OBJECT IDENTIFIER ::= { printmib 11 } 3106 prtMarkerSuppliesTable OBJECT-TYPE 3107 SYNTAX SEQUENCE OF PrtMarkerSuppliesEntry 3108 MAX-ACCESS not-accessible 3109 STATUS current 3110 DESCRIPTION 3111 "A table of the marker supplies available on this printer." 3112 ::= { prtMarkerSupplies 1 } 3114 prtMarkerSuppliesEntry OBJECT-TYPE 3115 SYNTAX PrtMarkerSuppliesEntry 3116 MAX-ACCESS not-accessible 3117 STATUS current 3118 DESCRIPTION 3119 "Attributes of a marker supply. 3121 Entries may exist in the table for each device 3122 index who's device type is `printer'." 3123 INDEX { hrDeviceIndex, prtMarkerSuppliesIndex } 3124 ::= { prtMarkerSuppliesTable 1 } 3126 PrtMarkerSuppliesEntry ::= SEQUENCE { 3127 prtMarkerSuppliesIndex Integer32, 3128 prtMarkerSuppliesMarkerIndex Integer32, 3129 prtMarkerSuppliesColorantIndex Integer32, 3130 prtMarkerSuppliesClass INTEGER, 3131 prtMarkerSuppliesType INTEGER, 3132 prtMarkerSuppliesDescription OCTET STRING, 3133 prtMarkerSuppliesSupplyUnit INTEGER, 3134 prtMarkerSuppliesMaxCapacity Integer32, 3135 prtMarkerSuppliesLevel Integer32 3137 draft Printer MIB August 19, 1994 3139 } 3141 prtMarkerSuppliesIndex OBJECT-TYPE 3142 SYNTAX Integer32 (1..65535) 3143 MAX-ACCESS not-accessible 3144 STATUS current 3145 DESCRIPTION 3146 "A unique value used by the printer to identify this marker 3147 supply. Although these values may change due to a major 3148 reconfiguration of the device (e.g. the addition of new marker 3149 supplies to the printer), values are expected to remain stable across 3150 successive printer power cycles." 3151 ::= { prtMarkerSuppliesEntry 1 } 3153 prtMarkerSuppliesMarkerIndex OBJECT-TYPE 3154 SYNTAX Integer32 (0..65535) 3155 MAX-ACCESS read-only 3156 STATUS current 3157 DESCRIPTION 3158 "The value of prtMarkerIndex corresponding to the 3159 marking sub-unit with which this marker supply 3160 sub-unit is associated." 3161 ::= { prtMarkerSuppliesEntry 2 } 3163 prtMarkerSuppliesColorantIndex OBJECT-TYPE 3164 SYNTAX Integer32 (0..65535) 3165 MAX-ACCESS read-only 3166 STATUS current 3167 DESCRIPTION 3168 "The value of prtMarkerColorantIndex 3169 corresponding to the colorant with which this 3170 marker supply sub-unit is associated. This value 3171 shall be 0 if there is no colorant table." 3172 ::= { prtMarkerSuppliesEntry 3 } 3174 prtMarkerSuppliesClass OBJECT-TYPE 3175 SYNTAX INTEGER { 3176 other(1), 3177 supplyThatIsConsumed(3), 3178 receptacleThatIsFilled(4) 3179 } 3180 MAX-ACCESS read-only 3181 STATUS current 3182 DESCRIPTION 3184 draft Printer MIB August 19, 1994 3186 "Indicates whether this supply entity represents a supply 3187 container that is consumed or a receptacle that is filled. This value 3188 is a type 1 enum." 3189 ::= { prtMarkerSuppliesEntry 4 } 3191 prtMarkerSuppliesType OBJECT-TYPE 3192 SYNTAX INTEGER { 3193 other(1), 3194 unknown(2), 3195 toner(3), 3196 wasteToner(4), 3197 ink(5), 3198 inkCartridge(6), 3199 inkRibbon(7), 3200 wasteInk(8), 3201 opc(9), 3202 developer(10), 3203 fuserOil(11), 3204 solidWax(12), 3205 ribbonWax(13), 3206 wasteWax(14) 3207 } 3208 MAX-ACCESS read-only 3209 STATUS current 3210 DESCRIPTION 3211 "The type of this supply. This value is a type 3 enum." 3212 ::= { prtMarkerSuppliesEntry 5 } 3214 prtMarkerSuppliesDescription OBJECT-TYPE 3215 SYNTAX OCTET STRING (SIZE(0..255)) 3216 MAX-ACCESS read-only 3217 STATUS current 3218 DESCRIPTION 3219 "The description of this supply container/receptacle in the 3220 localization specified by prtGeneralCurrentLocalization." 3221 ::= { prtMarkerSuppliesEntry 6 } 3223 prtMarkerSuppliesSupplyUnit OBJECT-TYPE 3224 SYNTAX INTEGER { 3225 tenThousandthsOfInches(3), -- .0001 3226 micrometers(4), 3227 thousandthsOfOunces(12), 3228 tenthsOfGrams(13), 3229 hundrethsOfFluidOunces(14), 3230 tenthsOfMilliliters(15) 3232 draft Printer MIB August 19, 1994 3234 } 3235 MAX-ACCESS read-only 3236 STATUS current 3237 DESCRIPTION 3238 "Unit of this marker supply container/receptacle. 3239 This value is a type 1 enum." 3240 ::= { prtMarkerSuppliesEntry 7 } 3242 prtMarkerSuppliesMaxCapacity OBJECT-TYPE 3243 SYNTAX Integer32 3244 MAX-ACCESS read-write 3245 STATUS current 3246 DESCRIPTION 3247 "The maximum capacity of this supply container/receptacle 3248 expressed in SupplyUnit. If this supply 3249 container/receptacle can reliably sense this value, the 3250 value is sensed by the printer and is read-only; 3251 otherwise, the value may be written (by a Remote Contol 3252 Panel or a Management Application). The value (-1) means 3253 other and specifically indicates that the sub-unit places 3254 no restrictions on this parameter. The value (-2) means 3255 unknown." 3256 ::= { prtMarkerSuppliesEntry 8 } 3258 prtMarkerSuppliesLevel OBJECT-TYPE 3259 SYNTAX Integer32 3260 MAX-ACCESS read-write 3261 STATUS current 3262 DESCRIPTION 3263 "The current level if this supply is a container; the 3264 remaining space if this supply is a receptacle. If this 3265 supply container/receptacle can reliably sense this 3266 value, the value is sensed by the printer and is 3267 read-only; otherwise, the value may be written (by a 3268 Remote Contol Panel or a Management Application). The 3269 value (-1) means other and specifically indicates that 3270 the sub-unit places no restrictions on this parameter. 3271 The value (-2) means unknown. A value of (-3) means that the 3272 printer knows that there is some supply/remaining space, 3273 respectively." 3274 ::= { prtMarkerSuppliesEntry 9 } 3276 -- The Marker Colorant Group 3277 -- 3278 -- This group is optional. However, to claim conformance to this 3279 draft Printer MIB August 19, 1994 3281 -- group, it is necessary to implement every object in the group. 3283 prtMarkerColorant OBJECT IDENTIFIER ::= { printmib 12 } 3285 prtMarkerColorantTable OBJECT-TYPE 3286 SYNTAX SEQUENCE OF PrtMarkerColorantEntry 3287 MAX-ACCESS not-accessible 3288 STATUS current 3289 DESCRIPTION 3290 "A table of all of the colorants available on the printer." 3291 ::= { prtMarkerColorant 1 } 3293 prtMarkerColorantEntry OBJECT-TYPE 3294 SYNTAX PrtMarkerColorantEntry 3295 MAX-ACCESS not-accessible 3296 STATUS current 3297 DESCRIPTION 3298 "Attributes of a colorant available on the printer. 3300 Entries may exist in the table for each device 3301 index who's device type is `printer'." 3302 INDEX { hrDeviceIndex, prtMarkerColorantIndex } 3303 ::= { prtMarkerColorantTable 1 } 3305 PrtMarkerColorantEntry ::= SEQUENCE { 3306 prtMarkerColorantIndex Integer32, 3307 prtMarkerColorantMarkerIndex Integer32, 3308 prtMarkerColorantRole INTEGER, 3309 prtMarkerColorantValue OCTET STRING, 3310 prtMarkerColorantTonality Integer32 3311 } 3313 prtMarkerColorantIndex OBJECT-TYPE 3314 SYNTAX Integer32 (1..65535) 3315 MAX-ACCESS not-accessible 3316 STATUS current 3317 DESCRIPTION 3318 "A unique value used by the printer to identify this colorant. 3319 Although these values may change due to a major 3320 reconfiguration of the device (e.g. the addition of new 3321 colorants to the printer), values are expected to remain 3322 stable across successive printer power cycles." 3323 ::= { prtMarkerColorantEntry 1 } 3325 prtMarkerColorantMarkerIndex OBJECT-TYPE 3326 draft Printer MIB August 19, 1994 3328 SYNTAX Integer32 (0..65535) 3329 MAX-ACCESS read-only 3330 STATUS current 3331 DESCRIPTION 3332 "The value of prtMarkerIndex corresponding to the 3333 marker sub-unit with which this colorant entry is 3334 associated." 3335 ::= { prtMarkerColorantEntry 2 } 3337 prtMarkerColorantRole OBJECT-TYPE 3338 SYNTAX INTEGER { -- Colorant Role 3339 other(1), 3340 process(3), 3341 spot(4) 3342 } 3343 MAX-ACCESS read-only 3344 STATUS current 3345 DESCRIPTION 3346 "The role played by this colorant. This value is a type 1 enum." 3347 ::= { prtMarkerColorantEntry 3 } 3349 prtMarkerColorantValue OBJECT-TYPE 3350 SYNTAX OCTET STRING (SIZE(0..63)) 3351 MAX-ACCESS read-only 3352 STATUS current 3353 DESCRIPTION 3354 "The name of the color of this The name of the color of this 3355 colorant using standardized string names from ISO 10175 (DPA) and ISO 3356 10180 (SPDL) which are: 3357 other 3358 unknown 3359 white 3360 red 3361 green 3362 blue 3363 cyan 3364 magenta 3365 yellow 3366 black 3367 Implementors may add additional string values. The naming 3368 conventions in ISO 9070 are recommended in order to avoid potential 3369 name clashes" 3370 ::= { prtMarkerColorantEntry 4 } 3372 prtMarkerColorantTonality OBJECT-TYPE 3373 draft Printer MIB August 19, 1994 3375 SYNTAX Integer32 3376 MAX-ACCESS read-only 3377 STATUS current 3378 DESCRIPTION 3379 "The distinct levels of tonality realizable by a marking 3380 sub-unit when using this colorant. This value does not 3381 include the number of levels of tonal difference that an 3382 interpreter can obtain by techniques such as half toning. 3383 This value must be at least 2." 3384 ::= { prtMarkerColorantEntry 5 } 3386 -- The Media Path Group 3387 -- 3388 -- The media paths encompass the mechanisms in the printer that move the 3389 -- media through the printer and connect all other media related sub- 3390 -- units: inputs, outputs, markers and finishers. A printer contains one 3391 -- or more media paths. These are represented by the Media Path Group in 3392 -- the model. The Media Path group has some attributes that apply to all 3393 -- paths plus a table of the separate media paths. 3394 -- 3395 -- This group is optional. However, to claim conformance to this 3396 -- group, it is necessary to implement every object in the group. 3398 prtMediaPath OBJECT IDENTIFIER ::= { printmib 13 } 3400 prtMediaPathDefaultIndex OBJECT-TYPE 3401 SYNTAX Integer32 (1..65535) 3402 MAX-ACCESS read-write 3403 STATUS current 3404 DESCRIPTION 3405 "The value of prtMediaPathIndex corresponding to 3406 the default media path; that is, the selection of the 3407 default media path." 3408 ::= { prtGeneralEntry 9 } 3410 prtMediaPathTable OBJECT-TYPE 3411 SYNTAX SEQUENCE OF PrtMediaPathEntry 3412 MAX-ACCESS not-accessible 3413 STATUS current 3414 DESCRIPTION 3415 "" 3416 ::= { prtMediaPath 4 } 3418 prtMediaPathEntry OBJECT-TYPE 3419 SYNTAX PrtMediaPathEntry 3421 draft Printer MIB August 19, 1994 3423 MAX-ACCESS not-accessible 3424 STATUS current 3425 DESCRIPTION 3426 "Entries may exist in the table for each device 3427 index who's device type is `printer'." 3428 INDEX { hrDeviceIndex, prtMediaPathIndex } 3429 ::= { prtMediaPathTable 1 } 3431 PrtMediaPathEntry ::= SEQUENCE { 3432 prtMediaPathIndex Integer32, 3433 prtMediaPathMaxSpeedPrintUnit INTEGER, 3434 prtMediaPathMediaSizeUnit MediaUnit, 3435 prtMediaPathMaxSpeed Integer32, 3436 prtMediaPathMaxMediaFeedDir Integer32, 3437 prtMediaPathMaxMediaXFeedDir Integer32, 3438 prtMediaPathMinMediaFeedDir Integer32, 3439 prtMediaPathMinMediaXFeedDir Integer32, 3440 prtMediaPathType INTEGER, 3441 prtMediaPathDescription OCTET STRING, 3442 prtMediaPathStatus SubUnitStatus 3443 } 3445 prtMediaPathIndex OBJECT-TYPE 3446 SYNTAX Integer32 (1..65535) 3447 MAX-ACCESS not-accessible 3448 STATUS current 3449 DESCRIPTION 3450 "A unique value used by the printer to identify this media 3451 path. Although these values may change due to a major reconfiguration 3452 of the device (e.g. the addition of new media paths to the printer), 3453 values are expected to remain stable across successive printer power 3454 cycles." 3455 ::= { prtMediaPathEntry 1 } 3457 prtMediaPathMaxSpeedPrintUnit OBJECT-TYPE 3458 SYNTAX INTEGER { 3459 tenThousandthsOfInchesPerHour(3), -- .0001/hour 3460 micrometersPerHour(4), 3461 charactersPerHour(5), 3462 linesPerHour(6), 3463 impressionsPerHour(7), 3464 sheetsPerHour(8), 3465 dotRowPerHour(9), 3466 feetPerHour(16), 3468 draft Printer MIB August 19, 1994 3470 metersPerHour(17) 3471 } 3472 MAX-ACCESS read-only 3473 STATUS current 3474 DESCRIPTION 3475 "The unit of measure used in specifying the speed of all media 3476 paths in the printer. This value is a type 1 enum." 3477 ::= { prtMediaPathEntry 2 } 3479 prtMediaPathMediaSizeUnit OBJECT-TYPE 3480 SYNTAX MediaUnit 3481 MAX-ACCESS read-only 3482 STATUS current 3483 DESCRIPTION 3484 "The units of measure of media size for use in calculating and 3485 relaying dimensional values for all media paths in the printer." 3486 ::= { prtMediaPathEntry 3 } 3488 prtMediaPathMaxSpeed OBJECT-TYPE 3489 SYNTAX Integer32 3490 MAX-ACCESS read-only 3491 STATUS current 3492 DESCRIPTION 3493 "The maximum printing speed of this media path expressed in 3494 prtMediaPathMaxSpeedUnit's. A value of (-1) implies 3495 'other'." 3496 ::= { prtMediaPathEntry 4 } 3498 prtMediaPathMaxMediaFeedDir OBJECT-TYPE 3499 SYNTAX Integer32 3500 MAX-ACCESS read-only 3501 STATUS current 3502 DESCRIPTION 3503 "The maximum physical media size in the feed direction of this 3504 media path expressed in units of measure specified by MediaSizeUnit. 3505 A value of (-1) implies 'unlimited'. A value of (-2) 3506 implies 'unknown'" 3507 ::= { prtMediaPathEntry 5 } 3509 prtMediaPathMaxMediaXFeedDir OBJECT-TYPE 3510 SYNTAX Integer32 3511 MAX-ACCESS read-only 3512 STATUS current 3513 DESCRIPTION 3514 "The maximum physical media size across the feed direction of 3516 draft Printer MIB August 19, 1994 3518 this media path expressed in units of measure specified by 3519 MediaSizeUnit. A value of (-2) implies 'unknown'." 3520 ::= { prtMediaPathEntry 6 } 3522 prtMediaPathMinMediaFeedDir OBJECT-TYPE 3523 SYNTAX Integer32 3524 MAX-ACCESS read-only 3525 STATUS current 3526 DESCRIPTION 3527 "The minimum physical media size in the feed direction of this 3528 media path expressed in units of measure specified by MediaSizeUnit. 3529 A value of (-2) implies 'unknown'." 3530 ::= { prtMediaPathEntry 7 } 3532 prtMediaPathMinMediaXFeedDir OBJECT-TYPE 3533 SYNTAX Integer32 3534 MAX-ACCESS read-only 3535 STATUS current 3536 DESCRIPTION 3537 "The minimum physical media size across the feed direction of 3538 this media path expressed in units of measure specified by 3539 MediaSizeUnit. A value of (-2) implies 'unknown'." 3540 ::= { prtMediaPathEntry 8 } 3542 prtMediaPathType OBJECT-TYPE 3543 SYNTAX INTEGER { 3544 other(1), 3545 unknown(2), 3546 longEdgeBindingDuplex(3), 3547 shortEdgeBindingDuplex(4), 3548 simplex(5) 3549 } 3550 MAX-ACCESS read-only 3551 STATUS current 3552 DESCRIPTION 3553 "The type of the media path for this media path. This 3554 value is a type 2 enum." 3555 ::= { prtMediaPathEntry 9 } 3557 prtMediaPathDescription OBJECT-TYPE 3558 SYNTAX OCTET STRING (SIZE(0..255)) 3559 MAX-ACCESS read-only 3560 STATUS current 3561 DESCRIPTION 3562 "The manufacturer-provided description of this media path in 3564 draft Printer MIB August 19, 1994 3566 the localization specified by prtGeneralCurrentLocalization." 3567 ::= { prtMediaPathEntry 10 } 3569 prtMediaPathStatus OBJECT-TYPE 3570 SYNTAX SubUnitStatus 3571 MAX-ACCESS read-only 3572 STATUS current 3573 DESCRIPTION 3574 "The current status of this media path." 3575 ::= { prtMediaPathEntry 11 } 3577 -- The Channel Group 3578 -- 3579 -- Implementation of every object in this group is mandatory. 3581 -- Channels are independent sources of print data. Here, 3582 -- print data is the term used for the information that is 3583 -- used to construct printed pages and may have both data 3584 -- and control aspects. The output of a channel is in a form 3585 -- suitable for input to one of the interpreters as a 3586 -- stream. A channel may be independently enabled (allowing 3587 -- print data to flow) or disabled (stopping the flow of 3588 -- print data). A printer may have one or more channels. 3589 -- 3590 -- Basically, the channel abstraction is intended to cover 3591 -- all the aspects of getting the print data to an 3592 -- interpreter. This might include transporting the data 3593 -- from one place to another, it might include (invisible) 3594 -- compression, it might include encoding or packetizing to 3595 -- provide multiple information sources over a single 3596 -- physical interface and it might include filtering 3597 -- characters that were destined for another kind of 3598 -- channel. All of these aspects are hidden in the channel 3599 -- abstraction.(Note some Page Description Languages have 3600 -- compression built into them so "invisible" compression 3601 -- refers to compression done by the transport medium and 3602 -- removed before the data is presented to the interpreter.) 3603 -- 3604 -- There are many kinds of channels;some of which are based 3605 -- on networks and others which are not. For example, a 3606 -- channel can be a serial (or parallel) connection; it can 3607 -- be a service, such as the Unix Line Printer Daemon (LPD), 3608 -- offering itself over a network connection (interface); or 3609 -- it could be a disk drive into which a floppy disks with 3610 -- the print data is inserted. Each channel is typically 3611 draft Printer MIB August 19, 1994 3613 -- identified by the electronic path and/or service protocol 3614 -- used to deliver print data to the printer. 3615 -- 3616 -- Channel example Implementation 3617 -- 3618 -- serial port channel bi-directional data channel 3619 -- parallel port channel often uni-directional channel 3620 -- IEEE 1284 port channel bi-directional channel 3621 -- SCSI port channel bi-directional 3622 -- Apple PAP channel may be based on Local-, Ether-or TokenTalk 3623 -- LPD Server channel typically TCP/IP based, port 515 3624 -- Novell Remote Printer typically SPX/IPX based channel 3625 -- Novell Print Server typically SPX/IPX based channel 3626 -- port 9100 channel HP and friends 3627 -- Adobe AppSocket(9101) channel a bi-directional extension of LPD 3628 -- 3629 -- It is easy to note that this is a mixed bag. There are 3630 -- some physical connections over which no (or very meager) 3631 -- protocols are run (e.g. the serial or old parallel ports) 3632 -- and there are services which often have elaborate 3633 -- protocols that run over a number of protocol stacks. In 3634 -- the end what is important is the delivery of print data 3635 -- thru the channel. 3636 -- 3637 -- The channel sub-units are represented by the Channel 3638 -- Group in the Model. It has a current Control Language 3639 -- which can be used to specify which interpreter is to be 3640 -- used for the print data and to query and change 3641 -- environment variables used by the interpreters (and 3642 -- Mangement Applications). There is also a default 3643 -- interpreter that is to be used if an interpreter is not 3644 -- explicitly specified using the Control Language. Channel 3645 -- sub-units are based on an underlying interface. 3647 -- The channel table and its underlying structure 3648 -- 3649 -- The first seven items in the Channel Table define the 3650 -- "channel" itself. A channel typically depends on other 3651 -- protocols and interfaces to provide the data that flows 3652 -- thru the channel. It is necessary to provide control of 3653 -- the (perhaps complex) process by which print data arrives 3654 -- at an interpreter. Control is largely limited to enabling 3655 -- or disabling the whole channel. It is likely, however, 3656 -- that more control of the process of accessing print data 3657 -- will be needed over time. Thus, the ChannelType will 3658 draft Printer MIB August 19, 1994 3660 -- allow type specific data to be associated with each 3661 -- channel (using ChannelType specific groups in a fashion 3662 -- analogous to the media specific MIBs that are associated 3663 -- with the IANAIfType in the Interfaces Table). As a first 3664 -- step in this direction, each channel will identify the 3665 -- underlying Interface on which it is based. This is the 3666 -- eighth object in each row of the table. 3668 -- Some examples of the kind of control are where 3669 -- compression or encoding is used; and whether the data is 3670 -- filtered to remove file storage anomolies such as those 3671 -- created by using MS-DOS/PC-DOS LPT1:. 3672 -- 3673 -- The Channel Table 3674 -- 3675 -- The prtChannelTable represents the set of input data sources which can 3676 -- provide print data to one or more of the interpreters available on a 3677 -- printer 3679 prtChannel OBJECT IDENTIFIER ::= { printmib 14 } 3681 prtChannelTable OBJECT-TYPE 3682 SYNTAX SEQUENCE OF PrtChannelEntry 3683 MAX-ACCESS not-accessible 3684 STATUS current 3685 DESCRIPTION 3686 "" 3687 ::= { prtChannel 1 } 3689 prtChannelEntry OBJECT-TYPE 3690 SYNTAX PrtChannelEntry 3691 MAX-ACCESS not-accessible 3692 STATUS current 3693 DESCRIPTION 3694 "Entries may exist in the table for each device 3695 index who's device type is `printer'." 3696 INDEX { hrDeviceIndex, prtChannelIndex } 3697 ::= { prtChannelTable 1 } 3699 PrtChannelEntry ::= SEQUENCE { 3700 prtChannelIndex Integer32, 3701 prtChannelType INTEGER, 3702 prtChannelProtocolVersion OCTET STRING, 3703 prtChannelCurrentJobCntlLangIndex Integer32, 3704 prtChannelDefaultPageDescLangIndex Integer32, 3706 draft Printer MIB August 19, 1994 3708 prtChannelState INTEGER, 3709 prtChannelIfIndex Integer32, 3710 prtChannelStatus SubUnitStatus 3711 } 3713 prtChannelIndex OBJECT-TYPE 3714 SYNTAX Integer32 3715 MAX-ACCESS not-accessible 3716 STATUS current 3717 DESCRIPTION 3718 "A unique value used by the printer to identify this data 3719 channel. Although these values may change due to a major 3720 reconfiguration of the device (e.g. the addition of new data channels 3721 to the printer), values are expected to remain stable across 3722 successive printer power cycles." 3723 ::= { prtChannelEntry 1 } 3725 prtChannelType OBJECT-TYPE 3726 SYNTAX INTEGER { 3727 other(1), 3728 chSerialPort(3), 3729 chParallelPort(4), 3730 chIEEE1284Port(5), 3731 chSCSIPort(6), 3732 chAppleTalkPAP(7), -- AppleTalk Printer Achess Protocol 3733 chLPDServer(8), 3734 chNetwareRPrinter(9), -- Netware 3735 chNetwarePServer(10), -- Netware 3736 chPort9100(11), 3737 chAppSocket(12), -- a bi-directional, LPD-like 3738 -- protocol using 9101 for 3739 -- control and 9100 for data. 3740 -- Adobe Systems, Inc. 3741 chFTP(13), -- FTP "PUT" to printer 3742 chTFTP(14), 3743 chDLCLLCPort(15), 3744 chIBM3270(16), 3745 chIBM5250(17), 3746 chFax(18), 3747 chIEEE1394(19), 3748 chTransport1(20), -- port 35 3749 chCPAP(21), -- port 170 3750 chDCERemoteProcCall(22), -- OSF 3751 chONCRemoteProcCall(23), -- Sun Microsystems 3752 chOLE(24), -- Microsoft 3754 draft Printer MIB August 19, 1994 3756 chNamedPipe(25), 3757 chPCPrint(26), -- Banyan 3758 chServerMessageBlock(27), 3759 -- File/Print sharing protocol used by 3760 -- various network operating systems 3761 -- from IBM 3Com, Microsoft and others 3762 chDPMF(28), -- Distributed Print Mgt. Framework, IBM 3763 chDLLAPI(29), -- Microsoft 3764 chVxDAPI(30), -- Microsoft 3765 chSystemObjectManager(31), -- IBM 3766 chDECLAT(32), -- Digital Equipment Corp. 3767 chNPAP(33) 3768 } 3769 MAX-ACCESS read-only 3770 STATUS current 3771 DESCRIPTION 3772 "The type of this print data channel. This 3773 object provides the linkage to ChannelType-specific 3774 groups that may (conceptually) extend the prtChannelTable 3775 with additional details about that channel. This value is 3776 a type 2 enum." 3777 ::= { prtChannelEntry 2 } 3779 prtChannelProtocolVersion OBJECT-TYPE 3780 SYNTAX OCTET STRING (SIZE(0..63)) 3781 MAX-ACCESS read-only 3782 STATUS current 3783 DESCRIPTION 3784 "The version of the protocol used on this 3785 channel. The format used for version numbering depends 3786 on prtChannelType." 3787 ::= { prtChannelEntry 3 } 3789 prtChannelCurrentJobCntlLangIndex OBJECT-TYPE 3790 SYNTAX Integer32 3791 MAX-ACCESS read-write 3792 STATUS current 3793 DESCRIPTION 3794 "The value of prtInterpreterIndex corresponding to the 3795 Control Language Interpreter for this channel. This 3796 interpreter defines the syntax used for control 3797 functions, such as querying or changing environment 3798 variables and identifying job boundaries (e.g. PJL, 3799 PostScript, NPAP). Must be 1 or greater." 3800 ::= { prtChannelEntry 4 } 3802 draft Printer MIB August 19, 1994 3804 prtChannelDefaultPageDescLangIndex OBJECT-TYPE 3805 SYNTAX Integer32 3806 MAX-ACCESS read-write 3807 STATUS current 3808 DESCRIPTION 3809 "The value of prtInterpreterIndex corresponding to the 3810 Page Description Language Interpreter for this channel. 3811 This interpreter defines the default Page Description 3812 Language interpreter to be used for the print data unless 3813 the Control Language is used to select a specific 3814 interpreter (e.g., PCL, PostScript Language, 3815 auto-sense). Must be 1 or greater." 3816 ::= { prtChannelEntry 5 } 3818 prtChannelState OBJECT-TYPE 3819 SYNTAX INTEGER { 3820 other(1), 3821 printDataAccepted(3), 3822 noDataAccepted(4) 3823 } 3824 MAX-ACCESS read-write 3825 STATUS current 3826 DESCRIPTION 3827 "The state of this print data channel. The value determines 3828 whether control information and print data is allowed through this 3829 channel or not. This value is a type 1 enum." 3830 ::= { prtChannelEntry 6 } 3832 prtChannelIfIndex OBJECT-TYPE 3833 SYNTAX Integer32 3834 MAX-ACCESS read-write 3835 STATUS current 3836 DESCRIPTION 3837 "The value of ifIndex (in the ifTable; see the interface 3838 section of MIB-2/RFC 1213) which corresponds to this channel. When 3839 more than one row of the ifTable is relevant, this is the index 3840 of the row representing the topmost layer in the interface 3841 hierarchy. A value of zero indicates that no interface 3842 is associated with this channel." 3843 ::= { prtChannelEntry 7 } 3845 prtChannelStatus OBJECT-TYPE 3846 SYNTAX SubUnitStatus 3847 MAX-ACCESS read-only 3848 STATUS current 3850 draft Printer MIB August 19, 1994 3852 DESCRIPTION 3853 "The current status of the channel." 3854 ::= { prtChannelEntry 8 } 3856 -- The Interpreter Group 3857 -- 3858 -- The interpreter sub-units are responsible for the conversion of a 3859 -- description of intended print instances into images that are to be 3860 -- marked on the media. A printer may have one or more interpreters. The 3861 -- interpreter sub-units are represented by the Interpreter Group in the 3862 -- Model. Each interpreter is generally implemented with software running 3863 -- on the System Controller sub-unit. The Interpreter Table has one entry 3864 -- per interpreter where the interpreters include both Page Description 3865 -- Language (PDL) Interpreters and Control Language Interpreters. 3866 -- 3867 -- Implementation of every object in this group is mandatory. 3869 prtInterpreter OBJECT IDENTIFIER ::= { printmib 15 } 3871 -- Interpreter Table 3872 -- 3873 -- The prtInterpreterTable is a table representing the interpreters in the 3874 -- printer. An entry shall be placed in the interpreter table for each 3875 -- interpreter on the printer. 3877 prtInterpreterTable OBJECT-TYPE 3878 SYNTAX SEQUENCE OF PrtInterpreterEntry 3879 MAX-ACCESS not-accessible 3880 STATUS current 3881 DESCRIPTION 3882 "" 3883 ::= { prtInterpreter 1 } 3885 prtInterpreterEntry OBJECT-TYPE 3886 SYNTAX PrtInterpreterEntry 3887 MAX-ACCESS not-accessible 3888 STATUS current 3889 DESCRIPTION 3890 "Entries may exist in the table for each device 3891 index who's device type is `printer'." 3892 INDEX { hrDeviceIndex, prtInterpreterIndex } 3893 ::= { prtInterpreterTable 1 } 3895 PrtInterpreterEntry ::= SEQUENCE { 3896 prtInterpreterIndex Integer32, 3898 draft Printer MIB August 19, 1994 3900 prtInterpreterLangFamily INTEGER, 3901 prtInterpreterLangLevel OCTET STRING, 3902 prtInterpreterLangVersion OCTET STRING, 3903 prtInterpreterDescription OCTET STRING, 3904 prtInterpreterVersion OCTET STRING, 3905 prtInterpreterDefaultOrientation INTEGER, 3906 prtInterpreterFeedAddressability Integer32, 3907 prtInterpreterXFeedAddressability Integer32, 3908 prtInterpreterDefaultCharSetIn CodedCharSet, 3909 prtInterpreterDefaultCharSetOut CodedCharSet, 3910 prtInterpreterTwoWay INTEGER 3911 } 3913 prtInterpreterIndex OBJECT-TYPE 3914 SYNTAX Integer32 3915 MAX-ACCESS not-accessible 3916 STATUS current 3917 DESCRIPTION 3918 "A unique value for each PDL or control language for which 3919 there exists an interpreter or emulator in the printer. The value is 3920 used to identify this interpreter. Although these values may change 3921 due to a major reconfiguration of the device (e.g. the addition of new 3922 interpreters to the printer), values are expected to remain stable 3923 across successive printer power cycles." 3924 ::= { prtInterpreterEntry 1 } 3926 prtInterpreterLangFamily OBJECT-TYPE 3927 SYNTAX INTEGER { 3928 other(1), 3929 langPCL(3), -- PCL. Starting with PCL version 5, HP-GL/2 3930 -- is included as part of the PCL language. 3931 -- PCL and HP-GL/2 are registered trademarks 3932 -- of Hewlett-Packard Company. 3933 langHPGL(4), -- Hewlett-Packard Graphics Language. HP-GL is 3934 -- a registered trademark of Hewlett-Packard 3935 -- Company. 3936 langPJL(5), -- Peripheral Job Language. Appears in the 3937 -- data stream between data intended for a 3938 -- page description language. 3939 -- Hewlett-Packard Co. 3940 langPS(6), -- PostScript Language (tm) 3941 -- Postscript - a trademark of Adobe 3942 -- Systems Incorporated which may be 3943 -- registered in certain jurisdictions 3944 langPSPrinter(42), -- The PostScript Language used for 3946 draft Printer MIB August 19, 1994 3948 -- control (with any PDLs) 3949 -- Adobe Systems Incorporated 3950 langIPDS(7), -- Intelligent Printer Data Stream 3951 -- Bi-directional print data stream for 3952 -- documents consisting of data objects 3953 -- (text, image, graphics, bar codes), 3954 -- resources (fonts, overlays) and page, 3955 -- form and finishing instructions. 3956 -- Facilitates system level device 3957 -- control, document tracking and error 3958 -- recovery throughout the print process. 3959 -- Pennant Systems, IBM 3960 langPPDS(8), -- IBM Personal Printer Data Stream. 3961 -- Originally called IBM ASCII, the name 3962 -- was changed to PPDS when the Laser 3963 -- Printer was introduced in 1989. 3964 -- Lexmark International, Inc. 3965 langEscapeP(9), 3966 langEpson(10), 3967 langDDIF(11), -- Digital Document Interchange Format 3968 -- Digital Equipment Corp., Maynard MA 3969 langInterpress(12), 3970 langISO6429(13), -- ISO 6429. Control functions for Coded 3971 -- Character Sets (has ASCII control 3972 -- characters, plus additional controls for 3973 -- character imaging devices.) 3974 -- ISO Standard, Geneva, Switzerland 3975 langLineData(14), -- line-data: Lines of data as separate 3976 -- ASCII or EBCDIC records and containing 3977 -- no control functions (no CR, LF, HT, FF, 3978 -- etc.). For use with traditional line 3979 -- printers. May use CR and/or LF to 3980 -- delimit lines, instead of records. See 3981 -- ISO 10175 Document Printing Application 3982 -- (DPA) 3983 -- ISO standard, Geneva, Switzerland 3984 langMODCA(15), -- Mixed Object Document Content Architecture 3985 -- Definitions that allow the composition, 3986 -- interchange -- and presentation of final 3987 -- form documents as a collection of data 3988 -- objects (text, image, graphics, bar 3989 -- codes), resources (fonts, overlays) and 3990 -- page, form and finishing instructions. 3991 -- Pennant Systems, IBM 3992 langREGIS(16), -- Remote Graphics Instruction Set, 3994 draft Printer MIB August 19, 1994 3996 -- Digital Equipment Corp., Maynard MA 3997 langSCS(17), -- SNA Character String 3998 -- Bi-directional print data stream for SNA 3999 -- LU-1 mode of communications 4000 -- IBM 4001 langSPDL(18), -- ISO 10180 Standard Page Description 4002 -- Language 4003 -- ISO Standard 4004 langTEK4014(19), 4005 langPDS(20), 4006 langIGP(21), 4007 langCodeV(22), -- Magnum Code-V, Image and printer control 4008 -- language used to control impact/dot- 4009 -- matrix printers. 4010 -- QMS, Inc., Mobile AL 4011 langDSCDSE(23), -- DSC-DSE: Data Stream Compatible and Emulation 4012 -- Bi-directional print data stream for non- 4013 -- SNA (DSC) and SNA LU-3 3270 controller 4014 -- (DSE) communications 4015 -- IBM 4016 langWPS(24), -- Windows Printing System, Resource based 4017 -- command/data stream used by Microsoft At 4018 -- Work Peripherals. 4019 -- Developed by the Microsoft Corporation. 4020 langLN03(25), -- Early DEC-PPL3, Digital Equipment Corp. 4021 langCCITT(26), 4022 langQUIC(27), -- QUIC (Quality Information Code), Page 4023 -- Description Language for laser printers. 4024 -- Included graphics, printer control 4025 -- capability and emulation of other well- 4026 -- known printer . 4027 -- QMS, Inc. 4028 langCPAP(28), -- Common Printer Access Protocol 4029 -- Digital Equipment Corp. 4030 langDecPPL(29), -- Digital ANSI-Compliant Printing Protocol 4031 -- (DEC-PPL) 4032 -- Digital Equipment Corp. 4033 langSimpleText(30),-- simple-text: character coded data, 4034 -- including NUL, CR , LF, HT, and FF 4035 -- control characters. See ISO 10175 4036 -- Document Printing Application (DPA) 4037 -- ISO standard, Geneva, Switzerland 4038 langNPAP(31), -- Network Printer Alliance Protocol 4039 -- IEEE 1284.1 4040 langDOC(32), -- Document Option Commands, Appears in the 4042 draft Printer MIB August 19, 1994 4044 -- data stream between data intended for a 4045 -- page description . 4046 -- QMS, Inc. 4047 langimPress(33), -- imPRESS, Page description language 4048 -- originally developed for the ImageServer 4049 -- line of systems. A binary language 4050 -- providing representations for text, 4051 -- simple graphics (rules, lines, conic 4052 -- sections), and some large forms (simple 4053 -- bit-map and CCITT group 3/4 encoded).The 4054 -- language was intended to be sent over an 4055 -- 8-bit channel and supported early 4056 -- document preparation languages (e.g. TeX 4057 -- and TROFF). 4058 -- QMS, Inc. 4059 langPinwriter(34), -- 24 wire dot matrix printer for 4060 -- USA, Europe, and Asia except Japan. 4061 -- More widely used in Germany, and some 4062 -- Asian countries than in US. 4063 -- NEC 4064 langNPDL(35), -- Page printer for Japanese 4065 -- market. 4066 -- NEC 4067 langNEC201PL(36), -- Serial printer language used in the 4068 -- Japanese market. 4069 -- NEC 4070 langAutomatic(37), -- Automatic PDL sensing. Automatic 4071 -- sensing of the interpreter language 4072 -- family by the printer examining the 4073 -- document content. Which actual 4074 -- interpreter language families are sensed 4075 -- depends on the printer implementation. 4076 langPages(38), -- Page printer Advanced Graphic Escape Set 4077 -- IBM Japan 4078 langLIPS(39), -- LBP Image Processing System 4079 langTIFF(40), -- Tagged Image File Format (Aldus) 4080 langDiagnostic(41),-- A hex dump of the input to the interpreter 4081 langCaPSL(43), -- Canon Print Systems Language 4082 langEXCL(44), -- Extended Command Language 4083 -- Talaris Systems Inc. 4084 langLCDS(45), -- Line Conditioned Data Stream 4085 -- Xerox Corporation 4086 langXES(46) -- Xerox Escape Sequences 4087 -- Xerox Corporation 4088 } 4090 draft Printer MIB August 19, 1994 4092 MAX-ACCESS read-only 4093 STATUS current 4094 DESCRIPTION 4095 "The family name of a Page Description Language (PDL) or 4096 control language which this interpreter in the printer can interpret 4097 or emulate. This type 2 list of enumerations requires review before 4098 additional entries are made. This value is a type 2 enum." 4099 ::= { prtInterpreterEntry 2 } 4101 prtInterpreterLangLevel OBJECT-TYPE 4102 SYNTAX OCTET STRING (SIZE(0..31)) 4103 MAX-ACCESS read-only 4104 STATUS current 4105 DESCRIPTION 4106 "The level of the language which this interpreter is 4107 interpreting or emulating. This might contain a value like '5e' for 4108 an interpreter which is emulating level 5e of the PCL language. It 4109 might contain '2' for an interpreter which is emulating level 2 of the 4110 PostScript language. Similarly it might contain '2' for an 4111 interpreter which is emulating level 2 of the HPGL language." 4112 ::= { prtInterpreterEntry 3 } 4114 prtInterpreterLangVersion OBJECT-TYPE 4115 SYNTAX OCTET STRING (SIZE(0..31)) 4116 MAX-ACCESS read-only 4117 STATUS current 4118 DESCRIPTION 4119 "The date code or version of the language which this interpreter 4120 is interpreting or emulating." 4121 ::= { prtInterpreterEntry 4 } 4123 prtInterpreterDescription OBJECT-TYPE 4124 SYNTAX OCTET STRING (SIZE(0..255)) 4125 MAX-ACCESS read-only 4126 STATUS current 4127 DESCRIPTION 4128 "A string to identify this interpreter in the localization specified 4129 by prtGeneralCurrentLocalization as opposed to the language which 4130 is being interpreted. It is anticipated that this string will 4131 allow manufacturers to unambiguously identify their interpreters." 4132 ::= { prtInterpreterEntry 5 } 4134 prtInterpreterVersion OBJECT-TYPE 4135 SYNTAX OCTET STRING (SIZE(0..31)) 4136 MAX-ACCESS read-only 4138 draft Printer MIB August 19, 1994 4140 STATUS current 4141 DESCRIPTION 4142 "The date code, version number, or other product specific 4143 information tied to this interpreter. This value is associated with 4144 the interpreter, rather than with the version of the language which is 4145 being interpreted or emulated." 4146 ::= { prtInterpreterEntry 6 } 4148 prtInterpreterDefaultOrientation OBJECT-TYPE 4149 SYNTAX INTEGER { 4150 other(1), 4151 portrait(3), 4152 landscape(4) 4153 } 4154 MAX-ACCESS read-write 4155 STATUS current 4156 DESCRIPTION 4157 "The current orientation default for this interpreter. This 4158 value may be overridden for a particular job (e.g., by a 4159 command in the input data stream). This value is a type 1 enum." 4160 ::= { prtInterpreterEntry 7 } 4162 prtInterpreterFeedAddressability OBJECT-TYPE 4163 SYNTAX Integer32 4164 MAX-ACCESS read-only 4165 STATUS current 4166 DESCRIPTION 4167 "The maximum interpreter addressability in the feed 4168 direction in 10000 prtMarkerAddressabilityUnit s (see 4169 prtMarkerAddressabilityFeedDir ) for this interpreter. 4170 The value (-1) means other and specifically indicates 4171 that the sub-unit places no restrictions on this parameter." 4172 ::= { prtInterpreterEntry 8 } 4174 prtInterpreterXFeedAddressability OBJECT-TYPE 4175 SYNTAX Integer32 4176 MAX-ACCESS read-only 4177 STATUS current 4178 DESCRIPTION 4179 "The maximum interpreter addressability in the cross feed 4180 direction in 10000 prtMarkerAddressabilityUnit s (see 4181 prtMarkerAddressabilityXFeedDir) for this interpreter. 4182 The value (-1) means other and specifically indicates 4183 that the sub-unit places no restrictions on this 4184 parameter." 4186 draft Printer MIB August 19, 1994 4188 ::= { prtInterpreterEntry 9 } 4190 prtInterpreterDefaultCharSetIn OBJECT-TYPE 4191 SYNTAX CodedCharSet 4192 MAX-ACCESS read-write 4193 STATUS current 4194 DESCRIPTION 4195 "The default coded character set for input octets 4196 encountered outside a context in which the Page 4197 Description Language established the interpretation 4198 of the octets. 4200 This value shall be (0) if there is no default." 4201 ::= { prtInterpreterEntry 10 } 4203 prtInterpreterDefaultCharSetOut OBJECT-TYPE 4204 SYNTAX CodedCharSet 4205 MAX-ACCESS read-write 4206 STATUS current 4207 DESCRIPTION 4208 "The default character set for data coming from this interpreter 4209 through the printer's output channel. 4211 This value shall be (0) if there is no default." 4212 ::= { prtInterpreterEntry 11 } 4214 prtInterpreterTwoWay OBJECT-TYPE 4215 SYNTAX INTEGER { 4216 yes(3), 4217 no(4) 4218 } 4219 MAX-ACCESS read-only 4220 STATUS current 4221 DESCRIPTION 4222 "Indicates whether or not this interpreter returns information back 4223 to the host. This value is a type 1 enum." 4224 ::= { prtInterpreterEntry 12 } 4226 -- The Console Group 4227 -- 4228 -- Many printers have a console on the printer, the operator console, that 4229 -- is used to display and modify the state of the printer. The console can 4230 -- be as simple as a few indicators and switches or as complicated as full 4231 -- screen displays and keyboards. There can be at most one such console. 4233 draft Printer MIB August 19, 1994 4235 -- 4236 -- Implementation of every object in this group is mandatory. 4238 prtConsole OBJECT IDENTIFIER ::= { printmib 16 } 4240 prtConsoleLocalization OBJECT-TYPE 4241 SYNTAX Integer32 (1..65535) 4242 MAX-ACCESS read-write 4243 STATUS current 4244 DESCRIPTION 4245 "The value of the prtLocalizationIndex corresponding to 4246 the language, country, and character set to be used for the 4247 console. This localization applies both to the actual display 4248 on the console as well as the encoding of these console 4249 objects in management operations." 4250 ::= { prtGeneralEntry 10 } 4252 prtConsoleNumberOfDisplayLines OBJECT-TYPE 4253 SYNTAX Integer32 (0..65535) 4254 MAX-ACCESS read-only 4255 STATUS current 4256 DESCRIPTION 4257 "The number of lines on the printer's physical 4258 display. This value is 0 if there are no lines on the 4259 physical display or if there is no physical display" 4260 ::= { prtGeneralEntry 11 } 4262 prtConsoleNumberOfDisplayChars OBJECT-TYPE 4263 SYNTAX Integer32 (0..65535) 4264 MAX-ACCESS read-only 4265 STATUS current 4266 DESCRIPTION 4267 "The number of characters per line displayed on the physical 4268 display. This value is 0 if there are no lines on the 4269 physical display or if there is no physical display" 4270 ::= { prtGeneralEntry 12 } 4272 prtConsoleDisable OBJECT-TYPE 4273 SYNTAX INTEGER { 4274 enabled(3), 4275 disabled(4) 4276 } 4277 MAX-ACCESS read-write 4278 STATUS current 4279 DESCRIPTION 4281 draft Printer MIB August 19, 1994 4283 "This object enables or disables manual input from the 4284 operators console." 4285 ::= { prtGeneralEntry 13 } 4287 -- The Display Buffer Table 4289 prtConsoleDisplayBufferTable OBJECT-TYPE 4290 SYNTAX SEQUENCE OF PrtConsoleDisplayBufferEntry 4291 MAX-ACCESS not-accessible 4292 STATUS current 4293 DESCRIPTION 4294 "" 4295 ::= { prtConsole 5 } 4297 prtConsoleDisplayBufferEntry OBJECT-TYPE 4298 SYNTAX PrtConsoleDisplayBufferEntry 4299 MAX-ACCESS not-accessible 4300 STATUS current 4301 DESCRIPTION 4302 "This table contains one entry for each physical line on 4303 the display. Lines cannot be added or deleted. 4305 Entries may exist in the table for each device 4306 index who's device type is `printer'." 4307 INDEX { hrDeviceIndex, prtConsoleDisplayBufferIndex } 4308 ::= { prtConsoleDisplayBufferTable 1 } 4310 PrtConsoleDisplayBufferEntry ::= SEQUENCE { 4311 prtConsoleDisplayBufferIndex Integer32, 4312 prtConsoleDisplayBufferText OCTET STRING 4313 } 4315 prtConsoleDisplayBufferIndex OBJECT-TYPE 4316 SYNTAX Integer32 (1..65535) 4317 MAX-ACCESS not-accessible 4318 STATUS current 4319 DESCRIPTION 4320 "A unique value for each console line in the printer. The 4321 value is used to identify this console line. Although 4322 these values may change due to a major reconfiguration of 4323 the device (e.g. the addition of new console lines to the 4324 printer), values are expected to remain stable across 4325 successive printer power cycles." 4326 ::= { prtConsoleDisplayBufferEntry 1 } 4328 draft Printer MIB August 19, 1994 4330 prtConsoleDisplayBufferText OBJECT-TYPE 4331 SYNTAX OCTET STRING (SIZE(0..255)) 4332 MAX-ACCESS read-write 4333 STATUS current 4334 DESCRIPTION 4335 "The content of a line in the logical display buffer of 4336 the operator's console of the printer. When a write 4337 operation occurs, normally a critical message, to one of 4338 the LineText strings, the agent should make that line 4339 displayable if a physical display is present. Writing 4340 a zero length string clears the line. It is an 4341 implementation-specific matter as to whether the agent allows 4342 a line to be overwritten before it has been cleared. 4343 Printer generated strings shall be in the localization 4344 specified by ConsoleLocalization. Management Application 4345 generated strings should be localized by the Management 4346 Application." 4347 ::= { prtConsoleDisplayBufferEntry 2 } 4349 -- The Console Light Table 4351 prtConsoleLightTable OBJECT-TYPE 4352 SYNTAX SEQUENCE OF PrtConsoleLightEntry 4353 MAX-ACCESS not-accessible 4354 STATUS current 4355 DESCRIPTION 4356 "" 4357 ::= { prtConsole 6 } 4359 prtConsoleLightEntry OBJECT-TYPE 4360 SYNTAX PrtConsoleLightEntry 4361 MAX-ACCESS not-accessible 4362 STATUS current 4363 DESCRIPTION 4364 "Entries may exist in the table for each device 4365 index who's device type is `printer'." 4366 INDEX { hrDeviceIndex, prtConsoleLightIndex } 4367 ::= { prtConsoleLightTable 1 } 4369 PrtConsoleLightEntry ::= SEQUENCE { 4370 prtConsoleLightIndex Integer32, 4371 prtConsoleOnTime Integer32, 4372 prtConsoleOffTime Integer32, 4373 prtConsoleColor INTEGER, 4374 prtConsoleDescription OCTET STRING 4376 draft Printer MIB August 19, 1994 4378 } 4380 prtConsoleLightIndex OBJECT-TYPE 4381 SYNTAX Integer32 (0..65535) 4382 MAX-ACCESS not-accessible 4383 STATUS current 4384 DESCRIPTION 4385 "A unique value used by the printer to identify this light. 4386 Although these values may change due to a major reconfiguration of the 4387 device (e.g. the addition of new lights to the printer), values are 4388 expected to remain stable across successive printer power cycles." 4389 ::= { prtConsoleLightEntry 1 } 4391 prtConsoleOnTime OBJECT-TYPE 4392 SYNTAX Integer32 4393 MAX-ACCESS read-write 4394 STATUS current 4395 DESCRIPTION 4396 "The on time in milliseconds of blinking of this light; 0 4397 indicates off always. If both prtConsoleOnTime 4398 and prtConsoleOffTime are 0, then the light is 4399 always off." 4400 ::= { prtConsoleLightEntry 2 } 4402 prtConsoleOffTime OBJECT-TYPE 4403 SYNTAX Integer32 4404 MAX-ACCESS read-write 4405 STATUS current 4406 DESCRIPTION 4407 "The off time in milliseconds of blinking of this light; 0 4408 indicates on always. If both prtConsoleOnTime 4409 and prtConsoleOffTime are 0, then the light is 4410 always off." 4411 ::= { prtConsoleLightEntry 3 } 4413 prtConsoleColor OBJECT-TYPE 4414 SYNTAX INTEGER { 4415 other(1), 4416 unknown(2), 4417 white(3), 4418 red(4), 4419 green(5), 4420 blue(6), 4421 cyan(7), 4422 magenta(8), 4424 draft Printer MIB August 19, 1994 4426 yellow(9) 4427 } 4428 MAX-ACCESS read-only 4429 STATUS current 4430 DESCRIPTION 4431 "The color of this light. This value is a type 2 enum." 4432 ::= { prtConsoleLightEntry 4 } 4434 prtConsoleDescription OBJECT-TYPE 4435 SYNTAX OCTET STRING (SIZE(0..255)) 4436 MAX-ACCESS read-only 4437 STATUS current 4438 DESCRIPTION 4439 "The vendor description or label of this light in the 4440 localization specified by prtConsoleLocalization." 4441 ::= { prtConsoleLightEntry 5 } 4443 -- The Alerts Group 4444 -- 4445 -- The prtAlertTable lists all the critical and non-critical alerts 4446 -- currently active in the printer. A critical alert is one that stops 4447 -- the printer from printing immediately and printing can not continue 4448 -- until the critical alert condition is eliminated. Non-critical alerts 4449 -- are those items that do not stop printing but may at some future time. 4450 -- The table contains information on the severity, component, detail 4451 -- location within the component, alert code and description of each 4452 -- critical alert that is currently active within the printer. See 2.2.13 4453 -- for a more complete description of the alerts table and its management. 4454 -- 4455 -- Implementation of every object in this group is mandatory. 4457 prtAlert OBJECT IDENTIFIER ::= { printmib 17 } 4459 prtAlertTable OBJECT-TYPE 4460 SYNTAX SEQUENCE OF PrtAlertEntry 4461 MAX-ACCESS not-accessible 4462 STATUS current 4463 DESCRIPTION 4464 "" 4465 ::= { prtAlert 1 } 4467 prtAlertEntry OBJECT-TYPE 4468 SYNTAX PrtAlertEntry 4469 MAX-ACCESS not-accessible 4471 draft Printer MIB August 19, 1994 4473 STATUS current 4474 DESCRIPTION 4475 "Entries may exist in the table for each device 4476 index who's device type is `printer'." 4477 INDEX { hrDeviceIndex, prtAlertIndex } 4478 ::= { prtAlertTable 1 } 4480 PrtAlertEntry ::= SEQUENCE { 4481 prtAlertIndex Integer32, 4482 prtAlertSeverityLevel INTEGER, 4483 prtAlertTrainingLevel INTEGER, 4484 prtAlertGroup INTEGER, 4485 prtAlertGroupIndex Integer32, 4486 prtAlertLocation Integer32, 4487 prtAlertCode INTEGER, 4488 prtAlertDescription OCTET STRING, 4489 prtAlertTime TimeTicks 4490 } 4492 prtAlertIndex OBJECT-TYPE 4493 SYNTAX Integer32 4494 MAX-ACCESS not-accessible 4495 STATUS current 4496 DESCRIPTION 4497 "The index value used to determine which alerts 4498 have been added or removed from the alert table. 4499 This is an incrementing integer starting from zero 4500 every time the printer is reset. When the printer 4501 adds an alert to the table, that alert is assigned 4502 the next higher integer value from the last item 4503 entered into the table. If the index value reaches 4504 its maximum value, the next item entered will cause 4505 the index value to roll over and start at zero 4506 again. The first event placed in the alert table 4507 after a reset of the printer shall 4508 have an index value of 1. NOTE: The management 4509 application will read the alert table when a trap 4510 or event notification occurs or at a periodic rate 4511 and then parse the table to determine if any new 4512 entries were added by comparing the last known index 4513 value with the current highest index value. The 4514 management application will then update its copy of 4515 the alert table. When the printer discovers that 4516 an alert is no longer active, the printer shall 4517 remove the row for that alert from the table and 4519 draft Printer MIB August 19, 1994 4521 shall reduce the number of rows in the table. The 4522 printer may add or delete any number of rows from 4523 the table at any time. The management station 4524 can detect when binary alerts have been deleted by 4525 requesting an attribute of each alert, and noting 4526 alerts as deleted when that retrieval is not possible." 4527 ::= { prtAlertEntry 1 } 4529 prtAlertSeverityLevel OBJECT-TYPE 4530 SYNTAX INTEGER { 4531 other(1), 4532 critical(3), 4533 warning(4) 4534 } 4535 MAX-ACCESS read-only 4536 STATUS current 4537 DESCRIPTION 4538 "The level of severity of this alert table entry. The printer 4539 determines the severity level assigned to each entry into the table. 4540 This value is a type 1 enum." 4541 ::= { prtAlertEntry 2 } 4543 prtAlertTrainingLevel OBJECT-TYPE 4544 SYNTAX INTEGER { 4545 other(1), 4546 unknown(2), 4547 untrained(3), 4548 trained(4), 4549 fieldService(5), 4550 management(6) 4551 } 4552 MAX-ACCESS read-only 4553 STATUS current 4554 DESCRIPTION 4555 "The level of training required to handle this alert. The 4556 training level is an enumeration that is determined and assigned by 4557 the printer manufacturer based on the information or the training 4558 required to handle this alert. The printer will break alerts into 4559 these different training levels. It is the responsibility of the 4560 management application in the system to determine how a particular 4561 alert is handled and how and to whom that alert is routed. The 4562 following are the four training levels of alerts: 4564 Field Service - Alerts that typically require advanced 4565 training and technical knowledge of the printer 4567 draft Printer MIB August 19, 1994 4569 and its sub-units. An example of a technical 4570 person would be a manufacture's Field Service 4571 representative, or other person formally 4572 trained by the manufacturer or similar 4573 representative. 4574 Trained - Alerts that require an intermediate or moderate 4575 level of knowledge of the printer and its 4576 sub-units. A typical examples of alerts that 4577 a trained operator can handle is replacing 4578 toner cartridges. 4579 Untrained - Alerts that can be fixed without prior training 4580 either because the action to correct the alert 4581 is obvious or the printer can help the 4582 untrained person fix the problem. A typical 4583 example of such an alert is reloading paper 4584 trays and emptying output bins on a low end 4585 printer. 4586 Management - Alerts that have to do with overall operation of 4587 and configuration of the printer. Examples of 4588 management events are configuration change of 4589 sub-units. 4591 This value is a type 2 enum." 4592 ::= { prtAlertEntry 3 } 4594 prtAlertGroup OBJECT-TYPE 4595 SYNTAX INTEGER { 4596 other(1), 4597 hostResourcesMIBStorageTable(3), 4598 hostResourcesMIBDeviceTable(4), 4599 generalPrinter(5), 4600 cover(6), 4601 localization(7), 4602 input(8), 4603 output(9), 4604 marker(10), 4605 markerSupplies(11), 4606 markerColorant(12), 4607 mediaPath(13), 4608 channel(14), 4609 interpreter(15), 4610 console(16) 4611 } 4612 MAX-ACCESS read-only 4613 STATUS current 4615 draft Printer MIB August 19, 1994 4617 DESCRIPTION 4618 "The type of sub-unit within the printer model that this alert 4619 is related. Input, output, and markers are examples of 4620 printer model groups, i.e., examples of types of sub-units. 4621 This value is a type 1 enum. 4623 Whereever possible, these enumerations match the 4624 sub-identifier that identifies the relevant table in the 4625 printmib." 4626 ::= { prtAlertEntry 4 } 4628 prtAlertGroupIndex OBJECT-TYPE 4629 SYNTAX Integer32 4630 MAX-ACCESS read-only 4631 STATUS current 4632 DESCRIPTION 4633 "An index of the row within the principle table in the 4634 group identified by prtAlertGroup that represents the 4635 sub-unit of the printer that caused this alert. The 4636 combination of the Group and the GroupIndex defines 4637 exactly which printer sub-unit caused the alert.; for 4638 example, Input #3, Output #2, and Marker #1. 4640 Every object in this MIB is indexed with hrDeviceIndex and 4641 optionally, another index variable. If this other index 4642 variable is present in the table that generated the alert, it 4643 will be used as the value for this object. Otherwise, this 4644 value shall be -1." 4645 ::= { prtAlertEntry 5 } 4647 prtAlertLocation OBJECT-TYPE 4648 SYNTAX Integer32 4649 MAX-ACCESS read-only 4650 STATUS current 4651 DESCRIPTION 4652 "The sub-unit location that is defined by the printer 4653 manufacturer to further refine the location of this alert 4654 within the designated sub-unit. The location is used in 4655 conjunction with the Group and GroupIndex values; for 4656 example, there is an alert in Input #2 at location number 7." 4657 ::= { prtAlertEntry 6 } 4659 prtAlertCode OBJECT-TYPE 4660 SYNTAX INTEGER { 4661 other(1), 4663 draft Printer MIB August 19, 1994 4665 unknown(2), 4666 -- codes common to serveral groups 4667 coverOpen(3), 4668 coverClosed(4), 4669 interlockOpen(5), 4670 interlockClosed(6), 4671 configurationChange(7), 4672 jam(8), 4673 -- general Printer group 4674 doorOpen(501), 4675 doorClosed(502), 4676 powerUp(503), 4677 powerDown(504), 4678 -- Input Group 4679 inputMediaTrayMissing(801), 4680 inputMediaSizeChange(802), 4681 inputMediaWeightChange(803), 4682 inputMediaTypeChange(804), 4683 inputMediaColorChange(805), 4684 inputMediaFormPartsChange(806), 4685 inputMediaSupplyLow(807), 4686 inputMediaSupplyEmpty(808), 4687 -- Output Group 4688 outputMediaTrayMissing(901), 4689 outputMediaTrayAlmostFull(902), 4690 outputMediaTrayFull(903), 4691 -- Marker group 4692 markerFuserUnderTemperature(1001), 4693 markerFuserOverTemperature(1002), 4694 -- Marker Supplies group 4695 markerTonerEmpty(1101), 4696 markerInkEmpty(1102), 4697 markerPrintRibbonEmpty(1103), 4698 markerTonerAlmostEmpty(1104), 4699 markerInkAlmostEmpty(1105), 4700 markerPrintRibbonAlmostEmpty(1106), 4701 markerWasteTonerReceptacleAlmostFull(1107), 4702 markerWasteInkReceptacleAlmostFull(1108), 4703 markerWasteTonerReceptacleFull(1109), 4704 markerWasteInkReceptacleFull(1110), 4705 markerOpcLifeAlmostOver(1111), 4706 markerOpcLifeOver(1112), 4707 markerDeveloperAlmostEmpty(1113), 4708 markerDeveloperEmpty(1114), 4709 -- Media Path Device Group 4711 draft Printer MIB August 19, 1994 4713 mediaPathMediaTrayMissing(1301), 4714 mediaPathMediaTrayAlmostFull(1302), 4715 mediaPathMediaTrayFull(1303), 4716 -- interpreter Group 4717 interpreterMemoryIncrease(1501), 4718 interpreterMemoryDecrease(1502), 4719 interpreterCartridgeAdded(1503), 4720 interpreterCartridgeDeleted(1504), 4721 interpreterResourceAdded(1505), 4722 interpreterResourceDeleted(1506), 4723 interpreterResourceUnavailable(1507) 4724 } 4725 MAX-ACCESS read-only 4726 STATUS current 4727 DESCRIPTION 4728 "The code that describes the type of alert for this entry in 4729 the table. There are different codes for each 4730 sub-unit type: for example, Media Supply Low and Media 4731 Supply Empty are Aler codes for the Input sub-unit. 4732 This value is a type 2 enum." 4733 ::= { prtAlertEntry 7} 4735 prtAlertDescription OBJECT-TYPE 4736 SYNTAX OCTET STRING (SIZE(0..255)) 4737 MAX-ACCESS read-only 4738 STATUS current 4739 DESCRIPTION 4740 "A description of this alert entry in the localization 4741 specified by prtGeneralCurrentLocalization. The description is 4742 provided by the printer to further elaborate on the enumerated alert 4743 or provide information in the case where the code is classified as 4744 `other' or `unknown'. The printer is required to return a description 4745 string but the string may be a null string." 4746 ::= { prtAlertEntry 8 } 4748 printerV1Alert OBJECT-IDENTITY 4749 STATUS current 4750 DESCRIPTION 4751 "The value of the enterprise-specific oid in a SNMPv1 trap sent 4752 signalling a critical event in the prtAlertTable." 4753 ::= { prtAlert 2 } 4755 printerV2AlertPrefix OBJECT IDENTIFIER ::= { printerV1Alert 0 } 4757 printerV2Alert NOTIFICATION-TYPE 4758 draft Printer MIB August 19, 1994 4760 OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, 4761 prtAlertGroupIndex, prtAlertLocation, prtAlertCode } 4762 STATUS current 4763 DESCRIPTION 4764 "This trap is sent whenever a critical event is added to the 4765 prtAlertTable." 4766 ::= { printerV2AlertPrefix 1 } 4768 -- Note that the SNMPv2 to SNMPv1 translation rules dictate that the 4769 -- preceding structure will result in SNMPv1 traps of the following 4770 -- form: 4771 -- 4772 -- printerAlert TRAP-TYPE 4773 -- ENTERPRISE printerV1Alert 4774 -- VARIABLES { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, 4775 -- prtAlertGroupIndex, prtAlertLocation, prtAlertCode } 4776 -- DESCRIPTION 4777 -- "This trap is sent whenever a critical event is added to the 4778 -- prtAlertTable." 4779 -- ::= 1 4781 -- The Alert Time Group 4782 -- 4783 -- This group is optional. However, to claim conformance to this 4784 -- group, it is necessary to implement every object in the group. 4786 prtAlertTime OBJECT-TYPE 4787 SYNTAX TimeTicks 4788 MAX-ACCESS read-only 4789 STATUS current 4790 DESCRIPTION 4791 "The value of sysUpTime at the time that this alert was 4792 generated." 4793 ::= { prtAlertEntry 9 } 4795 draft Printer MIB August 19, 1994 4797 -- Conformance Information 4799 prtMIBConformance OBJECT IDENTIFIER ::= { printmib 2 } 4801 -- compliance statements 4802 prtMIBCompliance MODULE-COMPLIANCE 4803 STATUS current 4804 DESCRIPTION 4805 "The compliance statement for agents that implement the 4806 printer MIB." 4807 MODULE -- this module 4808 MANDATORY-GROUPS { prtGeneralGroup, prtInputGroup, prtOutputGroup, 4809 prtMarkerGroup, prtChannelGroup, 4810 prtInterpreterGroup, prtConsoleGroup, 4811 prtAlertTableGroup } 4813 OBJECT prtGeneralReset 4814 SYNTAX INTEGER { 4815 notResetting(3), 4816 resetToNVRAM(5) 4817 } 4818 DESCRIPTION 4819 "It is conformant to implement just these two states in 4820 this object. Any additional states are optional." 4822 OBJECT prtConsoleOnTime 4823 MIN-ACCESS read-only 4824 DESCRIPTION 4825 "It is conformant to implement this object as read-only." 4827 OBJECT prtConsoleOffTime 4828 MIN-ACCESS read-only 4829 DESCRIPTION 4830 "It is conformant to implement this object as read-only." 4832 -- the prtResponsiblePartyGroup, prtExtendedInputGroup, 4833 -- prtInputMediaGroup, prtExtendedOutputGroup, 4834 -- prtOutputDimensionsGroup, prtOutputFeaturesGroup, 4835 -- prtMarkerSuppliesGroup, prtMarkerColorantGroup, 4836 -- prtMediaPathGroup, and the prtAlertTimeGroup are completely optional. 4837 ::= { prtMIBConformance 1 } 4839 prtMIBGroups OBJECT IDENTIFIER ::= { prtMIBConformance 2 } 4841 prtGeneralGroup OBJECT-GROUP 4842 draft Printer MIB August 19, 1994 4844 OBJECTS { prtGeneralConfigChanges, prtGeneralCurrentLocalization, 4845 prtGeneralReset, prtCoverDescription, prtCoverStatus, 4846 prtLocalizationLanguage, prtLocalizationCountry, 4847 prtLocalizationCharacterSet, prtStorageRefIndex, 4848 prtDeviceRefIndex } 4849 STATUS current 4850 DESCRIPTION 4851 "The general printer group." 4852 ::= { prtMIBGroups 1 } 4854 prtResponsiblePartyGroup OBJECT-GROUP 4855 OBJECTS { prtGeneralCurrentOperator, prtGeneralServicePerson } 4856 STATUS current 4857 DESCRIPTION 4858 "The responsible party group contains contact information for 4859 humans responsible for the printer." 4860 ::= { prtMIBGroups 2 } 4862 prtInputGroup OBJECT-GROUP 4863 OBJECTS { prtInputDefaultIndex, prtInputType, prtInputDimUnit, 4864 prtInputMediaDimFeedDirDeclared, 4865 prtInputMediaDimXFeedDirDeclared, 4866 prtInputMediaDimFeedDirChosen, 4867 prtInputMediaDimXFeedDirChosen, prtInputCapacityUnit, 4868 prtInputMaxCapacity, prtInputCurrentLevel, 4869 prtInputStatus, prtInputMediaName } 4870 STATUS current 4871 DESCRIPTION 4872 "The input group." 4873 ::= { prtMIBGroups 3 } 4875 prtExtendedInputGroup OBJECT-GROUP 4876 OBJECTS { prtInputName, prtInputVendorName, prtInputModel, 4877 prtInputVersion, prtInputSerialNumber, 4878 prtInputDescription, prtInputSecurity } 4879 STATUS current 4880 DESCRIPTION 4881 "The extended input group." 4882 ::= { prtMIBGroups 4 } 4884 prtInputMediaGroup OBJECT-GROUP 4885 OBJECTS { prtInputMediaWeight, prtInputMediaType, 4886 prtInputMediaColor, prtInputMediaFormParts } 4887 STATUS current 4888 DESCRIPTION 4890 draft Printer MIB August 19, 1994 4892 "The input media group." 4893 ::= { prtMIBGroups 5 } 4895 prtOutputGroup OBJECT-GROUP 4896 OBJECTS { prtOutputDefaultIndex, prtOutputType, 4897 prtOutputCapacityUnit, prtOutputMaxCapacity, 4898 prtOutputRemainingCapacity, prtOutputStatus } 4899 STATUS current 4900 DESCRIPTION 4901 "The output group." 4902 ::= { prtMIBGroups 6 } 4904 prtExtendedOutputGroup OBJECT-GROUP 4905 OBJECTS { prtOutputName, prtOutputVendorName, prtOutputModel, 4906 prtOutputVersion, prtOutputSerialNumber, 4907 prtOutputDescription, prtOutputSecurity } 4908 STATUS current 4909 DESCRIPTION 4910 "The extended output group." 4911 ::= { prtMIBGroups 7 } 4913 prtOutputDimensionsGroup OBJECT-GROUP 4914 OBJECTS { prtOutputDimUnit, prtOutputMaxDimFeedDir, 4915 prtOutputMaxDimXFeedDir, prtOutputMinDimFeedDir, 4916 prtOutputMinDimXFeedDir } 4917 STATUS current 4918 DESCRIPTION 4919 "The output dimensions group" 4920 ::= { prtMIBGroups 8 } 4922 prtOutputFeaturesGroup OBJECT-GROUP 4923 OBJECTS { prtOutputStackingOrder, 4924 prtOutputPageDeliveryOrientation, prtOutputBursting, 4925 prtOutputDecollating, prtOutputPageCollated, 4926 prtOutputOffsetStacking } 4927 STATUS current 4928 DESCRIPTION 4929 "The output features group." 4930 ::= { prtMIBGroups 9 } 4932 prtMarkerGroup OBJECT-GROUP 4933 OBJECTS { prtMarkerDefaultIndex, prtMarkerMarkTech, 4934 prtMarkerCounterUnit, prtMarkerLifeCount, 4935 prtMarkerPowerOnCount, prtMarkerProcessColorants, 4936 prtMarkerSpotColorants, prtMarkerAddressabilityUnit, 4938 draft Printer MIB August 19, 1994 4940 prtMarkerAddressabilityFeedDir, 4941 prtMarkerAddressabilityXFeedDir, prtMarkerNorthMargin, 4942 prtMarkerSouthMargin, prtMarkerWestMargin, 4943 prtMarkerEastMargin, prtMarkerStatus } 4944 STATUS current 4945 DESCRIPTION 4946 "The marker group." 4947 ::= { prtMIBGroups 10 } 4949 prtMarkerSuppliesGroup OBJECT-GROUP 4950 OBJECTS { prtMarkerSuppliesMarkerIndex, 4951 prtMarkerSuppliesColorantIndex, prtMarkerSuppliesClass, 4952 prtMarkerSuppliesType, prtMarkerSuppliesDescription, 4953 prtMarkerSuppliesSupplyUnit, 4954 prtMarkerSuppliesMaxCapacity, prtMarkerSuppliesLevel } 4955 STATUS current 4956 DESCRIPTION 4957 "The marker supplies group." 4958 ::= { prtMIBGroups 11 } 4960 prtMarkerColorantGroup OBJECT-GROUP 4961 OBJECTS { prtMarkerColorantMarkerIndex, prtMarkerColorantRole, 4962 prtMarkerColorantValue, prtMarkerColorantTonality } 4963 STATUS current 4964 DESCRIPTION 4965 "The marker colorant group." 4966 ::= { prtMIBGroups 12 } 4968 prtMediaPathGroup OBJECT-GROUP 4969 OBJECTS { prtMediaPathDefaultIndex, prtMediaPathMaxSpeedPrintUnit, 4970 prtMediaPathMediaSizeUnit, prtMediaPathMaxSpeed, 4971 prtMediaPathMaxMediaFeedDir, 4972 prtMediaPathMaxMediaXFeedDir, 4973 prtMediaPathMinMediaFeedDir, 4974 prtMediaPathMinMediaXFeedDir, prtMediaPathType, 4975 prtMediaPathDescription, prtMediaPathStatus} 4976 STATUS current 4977 DESCRIPTION 4978 "The media path group." 4979 ::= { prtMIBGroups 13 } 4981 prtChannelGroup OBJECT-GROUP 4982 OBJECTS { prtChannelType, prtChannelProtocolVersion, 4983 prtChannelCurrentJobCntlLangIndex, 4984 prtChannelDefaultPageDescLangIndex, prtChannelState, 4986 draft Printer MIB August 19, 1994 4988 prtChannelIfIndex, prtChannelStatus } 4989 STATUS current 4990 DESCRIPTION 4991 "The channel group." 4992 ::= { prtMIBGroups 14 } 4994 prtInterpreterGroup OBJECT-GROUP 4995 OBJECTS { prtInterpreterLangFamily, prtInterpreterLangLevel, 4996 prtInterpreterLangVersion, prtInterpreterDescription, 4997 prtInterpreterVersion, prtInterpreterDefaultOrientation, 4998 prtInterpreterFeedAddressability, 4999 prtInterpreterXFeedAddressability, 5000 prtInterpreterDefaultCharSetIn, 5001 prtInterpreterDefaultCharSetOut, prtInterpreterTwoWay } 5002 STATUS current 5003 DESCRIPTION 5004 "The interpreter group." 5005 ::= { prtMIBGroups 15 } 5007 prtConsoleGroup OBJECT-GROUP 5008 OBJECTS { prtConsoleLocalization, prtConsoleNumberOfDisplayLines, 5009 prtConsoleNumberOfDisplayChars, prtConsoleDisable, 5010 prtConsoleDisplayBufferText, prtConsoleOnTime, 5011 prtConsoleOffTime, prtConsoleColor, 5012 prtConsoleDescription } 5013 STATUS current 5014 DESCRIPTION 5015 "The console group." 5016 ::= { prtMIBGroups 16 } 5018 prtAlertTableGroup OBJECT-GROUP 5019 OBJECTS { prtAlertSeverityLevel, prtAlertTrainingLevel, 5020 prtAlertGroup, prtAlertGroupIndex, prtAlertLocation, 5021 prtAlertCode, prtAlertDescription } 5022 STATUS current 5023 DESCRIPTION 5024 "The alert table group." 5025 ::= { prtMIBGroups 17 } 5027 prtAlertTimeGroup OBJECT-GROUP 5028 OBJECTS { prtAlertTime } 5029 STATUS current 5030 DESCRIPTION 5031 "The alert time group." 5032 ::= { prtMIBGroups 18 } 5034 draft Printer MIB August 19, 1994 5036 END 5038 Appendix A - Glossary of Terms 5040 Addressability -- on the marker, the number of distinctly setable mark- 5041 ing units (pels) per unit of addressability unit; for example, 300 dots 5042 per inch is expressed as 300 per 1000 Thousandths Of Inches and 4 dots 5043 per millimeter is 4 per 1000 Micrometers. Addressability is not resolu- 5044 tion because marks that are one addressability position apart may not be 5045 independently resolvable by the eye due to factors such as gain in the 5046 area of marks so they overlap or nearly touch. 5048 Alert -- a reportable event for which there is an entry in the alert 5049 table 5051 Attribute - a data item that has a name, a syntax, and a value (DMTF 5052 usage). Analogous to the SNMP MIB concept of object. 5054 Bin -- an output sub-unit which may or may not be removable 5056 Bursting -- the process by which continuous media is separated into 5057 individual sheets, typically by bursting along pre-formed perforations. 5059 Channel -- A term used to describe a single source of data which is 5060 presented to a printer. The model that we use in describing a printer 5061 allows for an arbitrary number of channels. Multiple channels can exist 5062 on the same physical port. This is commonly done over EtherNet ports 5063 where EtherTalk, TCP/IP, and SPX/IPX protocols can be supplying dif- 5064 ferent data streams simultaneously to a single printer on the same phy- 5065 sical port. 5067 Collation -- in multiple copy output, placing the pages from separate 5068 copies into separte output bins 5070 Component -- a complete product, such as a printer. (DMTF usage) 5072 Control Language - a data syntax or language for controlling the printer 5073 through the print data channel. 5075 Critical Alert -- an alert triggered by an event which leads to a state 5076 in which printing is no longer possible; the printer is stopped 5078 Decollating -- the process by which the individual parts within a 5079 multi-part form are separated and sorted into separate stacks for each 5080 part. 5082 draft Printer MIB August 19, 1994 5084 Description -- information about the configuration and capabilities of 5085 the printer and its various sub-units 5087 DMTF - Desktop Management Task Force - a group of companies that has 5088 defined a management framework for PCs and other hosts for local manage- 5089 ment of hardware and software with automatic interworking with SNMP for 5090 remote management 5092 DPA - ISO 10175 Document Printing Application standard. A standard for 5093 a client server protocol for a print system, including (1) submitting 5094 print jobs to and (2) managing print jobs in a spooler 5096 Event - a state change in the printer 5098 Group -- a collection of attributes or objects that represent a type of 5099 sub-unit of the printer 5101 IANA - Internet Registration Authority. See RFC 1340 5103 Idempotent -- Idempotence is the property of an operation that results 5104 in the same state no matter how many times it is executed (at least 5105 once). This is a property that is shared by true databases in which 5106 operations on data items only change the state of the data item and do 5107 not have other side effects. Because the SNMP data model is that of 5108 operations on a database, SNMP MIB objects should be assumed to be idem- 5109 potent. If a MIB object is defined in a non-idempotent way, the this 5110 data model can break in subtle ways when faced with packet loss, multi- 5111 ple managers, and other common conditions. 5113 In order to fulfill the common need for actions to result from SNMP Set 5114 operations, SNMP MIB objects can be modeled such that the change in 5115 state from one state to another has the side effect of causing an 5116 action. It is important to note that with this model, an SNMP operation 5117 that sets a value equal to its current value will cause no action. This 5118 retains the idempotence of a single command, while allowing actions to 5119 be initiated by SNMP SET requests. 5121 For example, a switch like the foot switch that changes from high beams 5122 to low beams is not idempotent. If the command is received multiple 5123 times the result may be different than if the command was received a 5124 single time. In the SNMP world preferred commands would be "set lights 5125 to high beam" and "set lights to low beam". These commands yield 5126 predictable results when executed perhaps multiple times. A command 5127 like "press foot toggle switch", is not idempotent because when executed 5128 an unknown number of times, it yields an indeterminate result. 5130 draft Printer MIB August 19, 1994 5132 Input -- a tray or bin from which instances of the media are obtained 5133 and fed into the Media Path 5135 Interpreter - the embodiment of an algorithm that processes a data 5136 stream consisting of a Page Description Language (PDL) and/or a Control 5137 Language. 5139 Localization -- the specification of human language, country, and char- 5140 acter set needed to present information to people in their native 5141 languages. 5143 Management Application (a.k.a. Manager) -- a program which queries and 5144 controls one or more managed nodes 5146 Management Station -- a physical computer on which one or more manage- 5147 ment applications can run 5149 Media Path -- the mechanisms that transport instances of the media from 5150 an input, through the marker, possibly through media buffers and duplex- 5151 ing pathways, out to the output with optional finishing applied. The 5152 inputs and outputs are not part of the Media Path. 5154 MIB - Management Information Base - the specification for a set of 5155 management objects to be managed using SNMP or other management proto- 5156 col; also an instance of the data for such a set 5158 MIF - Management Information Format - the specification for a set of 5159 management attributes to be managed locally on a PC or other host using 5160 the Desktop Management Task Force (DMTF) Management Framework.; also an 5161 instance of the data for such a set 5163 Non-critical Alert -- an alert triggered by a reportable event which 5164 does not lead to a state in which printing is no longer possible; such 5165 an alert may lead to a state from which printing may no longer be possi- 5166 ble in the future, such as the low toner state or the alert may be pure 5167 informational, such as a configuration change at the printer. 5169 Object - a data item that has a name, a syntax, and a value (IETF SNMP 5170 usage). Analogous to the DMTF MIF concept of attribute 5172 Object/attribute - a term used to mean an object in a MIB and an attri- 5173 bute in a MIF 5175 Output -- a bin or stacker which accepts instances of media that have 5176 been processed by a printer 5177 draft Printer MIB August 19, 1994 5179 Page Description Language (PDL) - a data syntax or language for the 5180 electronic representation of a document as a sequence of page images. 5182 Printer -- a physical device that takes media from an input source, pro- 5183 duces marks on that media according to some page description or page 5184 control language and puts the result in some output destination, possi- 5185 bly with finishing applied. 5187 Printing -- the entire process of producing a printed document from gen- 5188 eration of the file to be printed, choosing printing properties, selec- 5189 tion of a printer, routing, queuing, resource management, scheduling, 5190 and finally printing including notifying the user 5192 Reportable event -- an event that is deemed of interest to a management 5193 station watching the printer 5195 Status -- information regarding the current operating state of the 5196 printer and its various sub-units. This is an abstraction of the exact 5197 physical condition of the printer. 5199 Sub-mechanism -- a distinguishable part of a sub-unit 5201 Sub-unit -- a part of the printer which may be a physical part, such as 5202 one of the input sources or a logical part such as an interpreter. 5204 Tray -- an input sub-unit which is typically removable 5206 Visible state -- that portion of the state of the printer that can be 5207 examined by a management application 5209 Appendix B - Media Size Names from ISO/IEC 10175 Document Printing 5210 Architecture 5212 For the convenience of management application developers, this appendix 5213 lists the standardized media size names from ISO/IEC 10175 Document 5214 Printing Application (DPA). Management applications that present a 5215 dialogue for choosing or displaying media size are encouraged to present 5216 relevant names from this list to avoid requiring the user to remember 5217 the physical dimensions used to describe the size of the media. A 5218 printer implementing the Printer MIB has no knowledge of these names, 5219 however; all media sizes in the MIB are given in terms of media dimen- 5220 sions as the values of prtInputChosenMediaDimFeedDir and prtInputChosen- 5221 MediaDimXFeedDir. 5223 String name Description 5224 draft Printer MIB August 19, 1994 5226 other 5227 unknown 5228 na-letter or letter North American letter 5229 size: 8.5 by 11 inches 5230 na-legal or legal North American legal 5231 size: 8.5 by 14 inches 5232 na-10x13-envelope North American 10x13 envelope 5233 size: 10 by 13 inches 5234 na-9x12-envelope North American 9x12 envelope 5235 size: 9 by 12 inches 5236 na-number-10-envelope North American number 10 business envelope 5237 size: 4.125 by 9.5 inches 5238 na-7x9-envelope North American 7x9 5239 size: 7 by 9 inches 5240 na-9x11-envelope North American 9x11 5241 size: 9 by 11 inches 5242 na-10x14-envelope North American 10x14 envelope 5243 size: 10 by 14 inches 5244 na-number-9-envelope North American number 9 business envelope 5245 na-6x9-envelope North American 6x9 envelope 5246 size: 6 by 9 inches 5247 na-10x15-envelope North American 10x15 envelope 5248 size: 10 by 15 inches 5249 a engineering A size 8.5 inches by 11 inches 5250 b engineering B size 11 inches by 17 inches 5251 c engineering C size 17 inches by 22 inches 5252 d engineering D size 22 inches by 34 inches 5253 e engineering E size 34 inches by 44 inches 5254 iso-a0 ISO A0 size: 841 mm by 1189 mm 5255 iso-a1 ISO A1 size: 594 mm by 841 mm 5256 iso-a2 ISO A2 size: 420 mm by 594 mm 5257 iso-a3 ISO A3 size: 297 mm by 420 mm 5258 iso-a4 ISO A4 size: 210 mm by 297 mm 5259 iso-a5 ISO A5 size: 148 mm by 210 mm 5260 iso-a6 ISO A6 size: 105 mm by 148 mm 5261 iso-a7 ISO A7 size: 74 mm by 105 mm 5262 iso-a8 ISO A8 size: 52 mm by 74 mm 5263 iso-a9 ISO A9 size: 37 mm by 52 mm 5264 iso-a10 ISO A10 size: 26 mm by 37 mm 5265 iso-b0 ISO B0 size: 1000 mm by 1414 mm 5266 iso-b1 ISO B1 size: 707 mm by 1000 mm 5267 iso-b2 ISO B2 size: 500 mm by 707 mm 5268 iso-b3 ISO B3 size: 353 mm by 500 mm 5269 iso-b4 ISO B4 size: 250 mm by 353 mm 5270 iso-b5 ISO B5 size: 176 mm by 250 mm 5271 draft Printer MIB August 19, 1994 5273 iso-b6 ISO B6 size: 125 mm by 176 mm 5274 iso-b7 ISO B7 size: 88 mm by 125 mm 5275 iso-b8 ISO B8 size: 62 mm by 88 mm 5276 iso-b9 ISO B9 size: 44 mm by 62 mm 5277 iso-b10 ISO B10 size: 31 mm by 44 mm 5278 iso-c0 ISO C0 size: 917 mm by 1297 mm 5279 iso-c1 ISO C1 size: 648 mm by 917 mm 5280 iso-c2 ISO C2 size: 458 mm by 648 mm 5281 iso-c3 ISO C3 size: 324 mm by 458 mm 5282 iso-c4 ISO C4 size: 229 mm by 324 mm 5283 iso-c5 ISO C5 size: 162 mm by 229 mm 5284 iso-c6 ISO C6 size: 114 mm by 162 mm 5285 iso-c7 ISO C7 size: 81 mm by 114 mm 5286 iso-c8 ISO C8 size: 57 mm by 81 mm 5287 iso-designated ISO Designated Long 5288 size: 110 mm by 220 mm 5289 jis-b0 JIS B0 size 1030 mm by 1456 mm 5290 jis-b1 JIS B1 size 728 mm by 1030 mm 5291 jis-b2 JIS B2 size 515 mm by 728 mm 5292 jis-b3 JIS B3 size 364 mm by 515 mm 5293 jis-b4 JIS B4 size 257 mm by 364 mm 5294 jis-b5 JIS B5 size 182 mm by 257 mm 5295 jis-b6 JIS B6 size 128 mm by 182 mm 5296 jis-b7 JIS B7 size 91 mm by 128 mm 5297 jis-b8 JIS B8 size 64 mm by 91 mm 5298 jis-b9 JIS B9 size 45 mm by 64 mm 5299 jis-b10 JIS B10 size 32 mm by 45 mm 5301 Appendix C - Media Names 5303 For the convenience of management application developers, this appendix 5304 lists the standardized media names from ISO/IEC 10175 Document Printing 5305 Application (DPA). Management applications that present a dialogue for 5306 choosing media may wish to use these names as an alternative to 5307 separately specifying, size, color, and/or type. Using standard media 5308 names will mean that a single management application dealing with 5309 printers from different vendors and under different system mangers will 5310 tend to use the same names for the same media. If selection of media by 5311 name is used, the attributes (size, type or color) implied by the name 5312 must be explicitly mapped to the appropriate attributes/object (prtIn- 5313 putDeclaredMediaDimFeedDir, prtInputDeclaredMediaDimXFeedDir, prtInput- 5314 MediaType and prtInputMediaColor) in the MIF/MIB. The attribute/object 5315 prtInputMediaName is intended for display to an operator and is purely 5316 descriptive. The value in prtInputMediaName is not interpreted by the 5317 printer so using a standard name for this value will not change any of 5318 draft Printer MIB August 19, 1994 5320 the other media attributes nor will it cause an alert if the media in 5321 the input sub-unit does not match the name. 5323 Simple Name Descriptor Text 5325 other 5326 unknown 5327 iso-a4-white Specifies the ISO A4 white medium with 5328 size: 210 mm by 297 mm as defined in ISO 216 5329 iso-a4-coloured Specifies the ISO A4 coloured medium with 5330 size: 210 mm by 297 mm as defined in ISO 216 5331 iso-a4-transparent Specifies the ISO A4 transparent medium with 5332 size: 210 mm by 297 mm as defined in ISO 216 5333 iso-a3-white Specifies the ISO A3 white medium with 5334 size: 297 mm by 420 mm as defined in ISO 216 5335 iso-a3-coloured Specifies the ISO A3 coloured medium with 5336 size: 297 mm by 420 mm as defined in ISO 216 5337 iso-a5-white Specifies the ISO A5 white medium with 5338 size: 148 mm by 210 mm as defined in ISO 216 5339 iso-a5-coloured Specifies the ISO A5 coloured medium with 5340 size: 148 mm by 210 mm as defined in ISO 216 5341 iso-b4-white Specifies the ISO B4 white medium with 5342 size: 250 mm by 353 mm as defined in ISO 216 5343 iso-b4-coloured Specifies the ISO B4 coloured medium with 5344 size: 250 mm by 353 mm as defined in ISO 216 5345 iso-b5-white Specifies the ISO B5 white medium with 5346 size: 176 mm by 250 mm as defined in ISO 216 5347 iso-b5-coloured Specifies the ISO B5 coloured medium with 5348 size: 176 mm by 250 mm as defined in ISO 216 5349 jis-b4-white Specifies the JIS B4 white medium with 5350 size: 257 mm by 364 mm as defined in JIS P0138 5351 jis-b4-coloured Specifies the JIS B4 coloured medium with 5352 size: 257 mm by 364 mm as defined in JIS P0138 5353 jis-b5-white Specifies the JIS B5 white medium with 5354 size: 182 mm by 257 mm as defined in JIS P0138 5355 jis-b5-coloured Specifies the JIS B5 coloured medium with 5356 size: 182 mm by 257 mm as defined in JIS P0138 5358 The following standard values are defined for North American media: 5360 na-letter-white Specifies the North American letter white 5361 medium with size: 8.5 inches by 11 inches 5362 na-letter-coloured Specifies the North American letter coloured 5363 medium with size: 8.5 inches by 11 inches 5364 na-letter-transparent 5366 draft Printer MIB August 19, 1994 5368 Specifies the North American letter transparent 5369 medium with size: 8.5 inches by 11 inches 5370 na-legal-white Specifies the North American legal white 5371 medium with size: 8.5 inches by 14 inches 5372 na-legal-coloured Specifies the North American legal coloured 5373 medium with size: 8.5 inches by 14 inches 5375 The following standard values are defined for envelopes: 5377 iso-b5-envelope Specifies the ISO B5 envelope medium 5378 with size: 176 mm by 250 mm 5379 as defined in ISO 216 and ISO 269 5380 iso-b4-envelope Specifies the ISO B4 envelope medium 5381 with size: 250 mm by 353 mm 5382 as defined in ISO 216 5383 iso-c4-envelope Specifies the ISO C4 envelope medium 5384 with size: 229 mm by 324 mm 5385 as defined in ISO 216 and ISO 269 5386 iso-c5-envelope Specifies the ISO C5 envelope medium 5387 with size: 162 mm by 229 mm 5388 as defined in ISO 269 5389 iso-designated-long-envelope 5390 Specifies the ISO Designated Long envelope medium 5391 with size: 110 mm by 220 mm 5392 as defined in ISO 269 5394 na-10x13-envelope Specifies the North American 10x13 envelope medium 5395 with size: 10 inches by 13 inches 5396 na-9x12-envelope Specifies the North American 9x12 envelope medium 5397 with size: 9 inches by 12 inches 5398 na-number-10-envelope 5399 Specifies the North American number 10 business 5400 envelope medium 5401 with size: 4.125 inches by 9.5 inches 5402 na-7x9-envelope Specifies the North American 7x9 inch envelope 5404 na-9x11-envelope Specifies the North American 9x11 inch envelope 5406 na-10x14-envelope Specifies the North American 10x14 inch envelope 5408 na-number-9-envelope 5409 Specifies the North American number 9 business 5410 envelope 5411 na-6x9-envelope Specifies the North American 6x9 inch envelope 5413 draft Printer MIB August 19, 1994 5415 na-10x15-envelope Specifies the North American 10x15 inch envelope 5417 The following standard values are defined for the less commonly used 5418 media (white-only): 5420 iso-a0-white Specifies the ISO A0 white medium 5421 with size: 841 mm by 1189 mm 5422 as defined in ISO 216 5423 iso-a1-white Specifies the ISO A1 white medium 5424 with size: 594 mm by 841 mm 5425 as defined in ISO 216 5426 iso-a2-white Specifies the ISO A2 white medium 5427 with size: 420 mm by 594 mm 5428 as defined in ISO 216 5429 iso-a6-white Specifies the ISO A6 white medium 5430 with size: 105 mm by 148 mm 5431 as defined in ISO 216 5432 iso-a7-white Specifies the ISO A7 white medium 5433 with size: 74 mm by 105 mm 5434 as defined in ISO 216 5435 iso-a8-white Specifies the ISO A8 white medium 5436 with size: 52 mm by 74 mm 5437 as defined in ISO 216 5438 iso-a9-white Specifies the ISO A9 white medium 5439 with size: 39 mm by 52 mm 5440 as defined in ISO 216 5441 iso-10-white Specifies the ISO A10 white medium 5442 with size: 26 mm by 37 mm 5443 as defined in ISO 216 5444 iso-b0-white Specifies the ISO B0 white medium 5445 with size: 1000 mm by 1414 mm 5446 as defined in ISO 216 5447 iso-b1-white Specifies the ISO B1 white medium 5448 with size: 707 mm by 1000 mm 5449 as defined in ISO 216 5450 iso-b2-white Specifies the ISO B2 white medium 5451 with size: 500 mm by 707 mm 5452 as defined in ISO 216 5453 iso-b3-white Specifies the ISO B3 white medium 5454 with size: 353 mm by 500 mm 5455 as defined in ISO 216 5456 iso-b6-white Specifies the ISO B6 white medium 5457 with size: 125 mm by 176 mm i 5458 as defined in ISO 216 5460 draft Printer MIB August 19, 1994 5462 iso-b7-white Specifies the ISO B7 white medium 5463 with size: 88 mm by 125 mm 5464 as defined in ISO 216 5465 iso-b8-white Specifies the ISO B8 white medium 5466 with size: 62 mm by 88 mm 5467 as defined in ISO 216 5468 iso-b9-white Specifies the ISO B9 white medium 5469 with size: 44 mm by 62 mm 5470 as defined in ISO 216 5471 iso-b10-white Specifies the ISO B10 white medium 5472 with size: 31 mm by 44 mm 5473 as defined in ISO 216 5475 jis-b0-white Specifies the JIS B0 white medium with size: 5476 1030 mm by 1456 mm 5477 jis-b1-white Specifies the JIS B1 white medium with size: 5478 728 mm by 1030 mm 5479 jis-b2-white Specifies the JIS B2 white medium with size: 5480 515 mm by 728 mm 5481 jis-b3-white Specifies the JIS B3 white medium with size: 5482 364 mm by 515 mm 5483 jis-b6-white Specifies the JIS B6 white medium with size: 5484 257 mm by 364 mm 5485 jis-b7-white Specifies the JIS B7 white medium with size: 5486 182 mm by 257 mm 5487 jis-b8-white Specifies the JIS B8 white medium with size: 5488 128 mm by 182 mm 5489 jis-b9-white Specifies the JIS B9 white medium with size: 5490 91 mm by 128 mm 5491 jis-b10-white Specifies the JIS B10 white medium with size: 5492 64 mm by 91 mm 5494 The following standard values are defined for engineering media: 5495 a Specifies the engineering A size medium with size: 5496 8.5 inches by 11 inches 5497 b Specifies the engineering B size medium with size: 5498 11 inches by 17 inches 5499 c Specifies the engineering C size medium with size: 5500 17 inches by 22 inches 5501 d Specifies the engineering D size medium with size: 5502 22 inches by 34 inches 5503 e Specifies the engineering E size medium with size: 5504 34 inches by 44 inches 5506 Appendix D - Roles of Users 5507 draft Printer MIB August 19, 1994 5509 Background 5511 The need for Role Models stemmed in large part from the need to under- 5512 stand the importance any given managed object under consideration for 5513 inclusion in the specification. Many times the presence or nature of a 5514 particular proposed object would be debated within the group; the debate 5515 would typically end when one or more persons would describe the poten- 5516 tial usage for the object, usually in terms of a "live" person operating 5517 in some target environment. 5519 Steve Zilles (Adobe) first mentioned that he had considered this general 5520 problem and had come up with a short list of categories by which the 5521 group can evaluate the relative utility of a proposed object. The list 5522 Steve described was: 5524 - User 5526 - Trained Operator 5528 - Service 5530 Upon further examination of the overall problem I found it useful to 5531 expand the list of categories, as well as attempt to define a basic set 5532 of "requirements areas" that can help define the basic nature of each 5533 category. 5535 Every concept needs a name, and this concept is no different. For lack 5536 of better alternatives, I refer to these categories as "Role Models" in 5537 this document. This name was chosen in light of the fact that many 5538 times we try to find a "person" (or similar entity) for which the use of 5539 a proposed object is targeted. (I resisted the temptation to use the 5540 term "Usage Models," as I felt the term was too generic in nature.) 5542 In presenting the initial list of Role Models, the initial set of 5543 "requirements areas" are presented, followed by the set of Role Model 5544 definitions. Finally, a simple matrix is presented in which Role Models 5545 and requirements areas are cross-compared. 5547 It should be emphasized at this point that all of this is proposed as 5548 initial information for further discussion. No doubt major changes will 5549 be proposed by members of the group as time goes on. 5551 Proposed Print System Requirements Areas 5553 Surrounding printers and printing systems, the following list of 5554 draft Printer MIB August 19, 1994 5556 "requirement areas" is proposed as a "check list" of needs for the vari- 5557 ous Role Models: 5558 Printer job state - Determine the status of a job without a printer. 5559 Printer capabilities - Determine the current capabilities of a 5560 printer, for example, the available media sizes, two-sided 5561 printing, a particular type of interpreter, etc. 5562 Printer job submission - Submit a print job to a printer. 5563 Printer job removal - Remove a job from a printer. 5564 Notification of events - Receive notification of the existence of a 5565 defined printer event. An event can be of many types, including 5566 warnings, errors, job stage completion (e.g., "job done"), etc. 5567 Printer configuration - Query the current configuration of a 5568 printer. 5569 Printer consumables - Determine the current state of any and all 5570 consumables within a printer. 5571 Print job identification - Determine the identification of a job 5572 within a printer. 5573 Internal printer status - Determine the current status of the 5574 printer. 5575 Printer identification - Determine the identify of a printer. 5576 Printer location - Determine the physical location of a printer. 5577 Local system configuration - Determine various aspects of the 5578 current configuration of the local system involved with the 5579 operation of a printer. 5581 These "requirements" cover a large spectrum of requirements surrounding 5582 the operation of a printer in a network environment. This list is by no 5583 means complete, but serves as a starting point for assessing major 5584 requirements of the various Role Models described below. 5586 Proposed Role Models 5588 Following is a proposed list of "Role Models" to be used in evaluating 5589 the requirements for any given object defined within the Printer MIF. 5590 Note that the keyword enclosed in parentheses represents an abbreviation 5591 for the particular Role Model in the matrix described later in this 5592 document. 5593 User (USER) - A person or application that submits print jobs to 5594 the printer; typically viewed as the "end user" within the overall 5595 printing environment. 5596 Operator (OP) - A person responsible for maintaining a printer on a 5597 day-to-day basis, including such tasks as filling empty media 5598 trays, emptying full output trays, replacing toner cartridges, 5599 etc. 5600 Technician (TECH) - A person responsible for repairing a 5602 draft Printer MIB August 19, 1994 5604 malfunctioning printer, performing routine preventive maintenance, 5605 and other tasks that typically require advanced training on the 5606 printer internals. An example of a "technician" would be a 5607 manufacturer's Field Service representative, or other person 5608 formally trained by the manufacturer or similar representative. 5609 System Manager (MGR) - A person responsible for configuration and 5610 troubleshooting of components involved in the overall printing 5611 environment, including printers, print queues and network 5612 connectivity issues. This person is typically responsible for 5613 ensuring the overall operational integrity of the print system 5614 components, and is typically viewed as the central point of 5615 coordination among all other Role Models. 5616 Help Desk (HELP) - A person responsible for supporting Users in 5617 their printing needs, including training Users and troubleshooting 5618 Users' printing problems. 5619 Asset Manager (AM) - A person responsible for managing an 5620 organizations printing system assets (primarily printers). Such a 5621 person needs to be able to identify and track the location of 5622 printing assets on an ongoing basis. 5623 Capacity Planner (CP) - A person responsible for tracking the usage 5624 of printing resources on an ongoing basis. An optional related 5625 activity might be to acquire printing resource utilization 5626 information for the purposes of charging Users for resources used. 5627 Installer (INST) - A person or application responsible for 5628 installing or configuring printing system components on a local 5629 system. 5631 The purpose of these Role Models is to evaluate the relative merit of 5632 any given managed object. Whenever a managed object is proposed for 5633 inclusion into the specification, discussion on its expected value 5634 should be geared around which Role Models benefit from its presence and 5635 operation. 5637 Matrix of Requirement Areas and Role Models 5639 To better understand the relationship between the set of defined 5640 "Requirements Areas" and the various "Role Models," the following matrix 5641 is offered. 5643 It is important to recognize that many of the requirements areas will 5644 appear to be applicable to many of the Role Models. However, when con- 5645 sidering the actual context of a requirement area, it is very important 5646 to realize that often the actual context of a requirement is such the 5647 Role Model can change. 5649 draft Printer MIB August 19, 1994 5651 For example, it is obvious that a "System Manager" must be able to sub- 5652 mit print jobs to a printer; however, when submitting a print job a per- 5653 son identified as a "System Manager" is actually operating in the con- 5654 text of a "User" in this case; hence, the requirement to submit a print 5655 job is not listed as a requirement for a System Manager. 5657 Conversely, while a "User" must be able to remove a job previously sub- 5658 mitted to a printer, an "Operator" is often expected to be able to 5659 remove any print job from any printer; hence, print job removal is a 5660 (subtly different) requirement for both "User" and an "Operator" Role 5661 Models. 5663 That being said, I'm sure you'll find some inconsistencies in the fol- 5664 lowing matrix, depending on your particular interpretations of the vari- 5665 ous requirements areas. 5667 Role Models 5668 Requirement Area USER OP TECH MGR HELP AM CP INST 5669 Print job status xx xx xx xx xx 5670 Printer capabilities xx xx xx 5671 Print job submission xx 5672 Print job removal xx xx 5673 Notification of events xx xx 5674 Printer configuration xx xx 5675 Printer consumables xx xx 5676 Print job identification xx xx xx xx 5677 Internal printer status xx xx xx 5678 Printer identification xx xx xx xx xx xx 5679 Printer location xx 5680 Local system configuration xx xx 5682 Appendix E - Participants 5684 The following people attended at least one meeting of the Printer Work- 5685 ing Group meeting; many attended most meetings. 5687 Appendix E - Participants 5689 The following people attended at least one meeting of the 5690 Printer Working Group meeting; many attended most meetings. 5692 Azmy Abouased - Compaq 5693 Avi Basu - HP 5694 Kerry Bott - Intel 5695 Michael Bringmann - QMS 5697 draft Printer MIB August 19, 1994 5699 Ted Brunner - Tektronix 5700 Jeff Case - SNMP Inc. 5701 Rong Chang - IBM 5702 Andy Davidson - Tektronix 5703 Jack Demcak - Jadtech 5704 Andria Demetroulakos - Digital Products 5705 Mike Evans - ESI 5706 Richard Everman - uci.edu 5707 Neal Fischer - Fujitsu 5708 Joseph Flick - HP 5709 Rod Gerhart - Ricoh 5710 Christine Gressley - University of Illinois 5711 Joel Gyllenskog - HP 5712 Tom Hastings - DEC 5713 Tim Hathaway - Pacific Data 5714 Mark Held - CMU 5715 Bob Herriot - SUN 5716 Jeff Johnson - Cisco 5717 Jeff Johnson - Microsoft 5718 Theodore Kearley - QMS 5719 Barry Kelman - Microsoft 5720 Charles Kimber - Dataproducts 5721 Andrew Knutsen - SCO 5722 Peter Leunig - Leunig GmbH 5723 Harry Lewis - IBM Pennant Systems 5724 Bill Lott - QMS 5725 Mike MacKay - Xerox 5726 Jay Martin - Underscore 5727 Mike Mayes - Brother 5728 Kevin McBride - Underscore 5729 Stan McConnell - XEROX 5730 Gaylord Miyata - Underscore 5731 Michael Moore - Ricoh 5732 Rudy Nedved - CMU Computer Science Dept. 5733 Pete Neergaard - CMU 5734 Bill Norton - merit.edu 5735 Ron Norton - Printronix 5736 Roman Orzol - Okidata 5737 Alan Perelman - Emulex 5738 Noga Prat - Intel 5739 Dave Roach - Unisys 5740 Marshall Rose - Dover Beach Consulting 5741 John Saperia - BGS Systems Inc. 5742 Mike Scanlon - FTP Software 5743 Avi Schlank - Canon 5745 draft Printer MIB August 19, 1994 5747 Ron Smith - TI 5748 Larry Stein - Farpoint 5749 Koji Tashiro - NEC Technologies 5750 Jody Terrill - Extended Systems 5751 Chris Thomas - Intel Products 5752 Mike Timperman - Lexmark 5753 Randy Turner - QMS 5754 Bill Wagner - Digital Products 5755 Steve Waldbusser - CMU 5756 Tim Wells - Microsoft 5757 Craig Whittle - Compaq 5758 Don Wright - Lexmark 5759 Lloyd Young - Lexmark International Inc. 5760 Steve Zilles - Adobe 5761 Jim Zuber - Genoa 5763 draft Printer MIB August 19, 1994 5765 Authors' Addresses 5767 Ronald L. Smith Texas Instruments email: rlsmith@nb.ppd.ti.com phone: 5768 (817) 774-6151 5770 F.D. Wright Lexmark International email: don@lexmark.com phone: (606) 5771 232-4808 5773 Thomas N. Hastings Digital Equipment Corp. email: 5774 hastings@hannah.enet.dec.com phone: (508) 467-8299 5776 Stephen N. Zilles Adobe Systems, Inc email: szilles@mv.us.adobe.com 5777 phone: (415) 962-4766 5779 Joel Gyllenskog Hewlett-Packard Company email: 5780 jgyllens@hpdmd48.boi.hp.com phone: (208) 396-4515 5781 draft Printer MIB August 19, 1994 5783 Table of Contents 5785 1 Introduction .................................................... 2 5786 1.1 Network Printing Environment .................................. 2 5787 1.2 Printer Device Overview ....................................... 3 5788 1.3 Categories of Printer Information ............................. 4 5789 1.3.1 Descriptions ................................................ 4 5790 1.3.2 Status ...................................................... 4 5791 1.3.3 Alerts ...................................................... 4 5792 2 Printer Model ................................................... 5 5793 2.1 Overview of the Printer Model ................................. 8 5794 2.2 Printer Sub-Units ............................................. 8 5795 2.2.1 General Printer ............................................. 8 5796 2.2.2 Inputs ...................................................... 9 5797 2.2.3 Media ....................................................... 9 5798 2.2.4 Outputs ..................................................... 10 5799 2.2.5 Finishers ................................................... 10 5800 2.2.6 Markers ..................................................... 11 5801 2.2.7 Media Paths ................................................. 11 5802 2.2.8 System Controller ........................................... 12 5803 2.2.9 Interfaces .................................................. 12 5804 2.2.10 Channels ................................................... 12 5805 2.2.11 Interpreters ............................................... 12 5806 2.2.12 Console .................................................... 13 5807 2.2.13 Alerts ..................................................... 13 5808 2.2.13.1 Status and Alerts ........................................ 14 5809 2.2.13.2 Overall Printer Status ................................... 14 5810 2.2.13.2.1 Host MIB Printer Status ................................ 16 5811 2.2.13.2.2 Sub-unit Status ........................................ 18 5812 2.2.13.3 Alert Tables ............................................. 19 5813 2.2.13.4 Alert Table Management ................................... 20 5814 2.3 Read-Write Objects/Attributes ................................. 21 5815 2.4 Notational Conventions ........................................ 23 5816 2.4.1 Object/Attribute Names ...................................... 23 5817 2.4.1.1 SNMP MIB Object Names ..................................... 23 5818 2.4.1.2 DMTF MIF Attribute Names .................................. 24 5819 2.4.2 Defined Data Types .......................................... 24 5820 2.4.3 Enumerations ................................................ 24 5821 2.4.3.1 SNMP MIB enumeration symbols .............................. 24 5822 2.4.3.2 DMTF MIF enumeration symbols .............................. 25 5823 2.4.3.3 Registering Additional Enumerated Values .................. 25 5824 3 Objects/Attributes from other MIB/MIF Specifications ............ 26 5825 3.1 System Group objects .......................................... 27 5826 3.2 System Controller ............................................. 27 5827 draft Printer MIB August 19, 1994 5829 3.3 Interface Group objects ....................................... 27 5830 4 Textual Conventions ............................................. 28 5831 5 The General Printer Group ....................................... 38 5832 5.1 The Cover Table ............................................... 40 5833 5.2 The Localization Table ........................................ 42 5834 5.3 The System Resources Tables ................................... 43 5835 6 The Responsible Party group ..................................... 45 5836 7 The Input Group ................................................. 46 5837 8 The Extended Input Group ........................................ 52 5838 9 The Input Media Group ........................................... 53 5839 10 The Output Group ............................................... 55 5840 11 The Extended Output Group ...................................... 59 5841 12 The Output Dimensions Group .................................... 60 5842 13 The Output Features Group ...................................... 62 5843 14 The Marker Group ............................................... 64 5844 15 The Marker Supplies Group ...................................... 70 5845 16 The Marker Colorant Group ...................................... 73 5846 17 The Media Path Group ........................................... 76 5847 18 The Channel Group .............................................. 80 5848 18.1 The Channel Table and its underlying structure ............... 81 5849 18.2 The Channel Table ............................................ 82 5850 19 The Interpreter Group .......................................... 86 5851 20 The Console Group .............................................. 93 5852 20.1 The Display Buffer Table ..................................... 95 5853 20.2 The Console Light Table ...................................... 96 5854 21 The Alerts Group ............................................... 98 5855 21.1 The Alert Time Group ......................................... 105 5856 22 Appendix A - Glossary of Terms ................................. 111 5857 23 Appendix B - Media Size Names .................................. 114 5858 24 Appendix C - Media Names ....................................... 116 5859 25 Appendix D - Roles of Users .................................... 120 5860 26 Appendix E - Participants ...................................... 124 5861 27 Authors' Addresses ............................................. 127