1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
|
<pre>Network Working Group B. Stewart, Editor
Request for Comments: 1318 Xyplex, Inc.
April 1992
<span class="h1">Definitions of Managed Objects</span>
<span class="h1">for Parallel-printer-like Hardware Devices</span>
Status of this Memo
This document specifies an IAB standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "IAB
Official Protocol Standards" for the standardization state and status
of this protocol. Distribution of this memo is unlimited.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Abstract</span>
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets.
In particular, it defines objects for the management of
parallel-printer-like devices.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Network Management Framework</span>
The Internet-standard Network Management Framework consists
of three components. They are:
<a href="./rfc1155">RFC 1155</a> which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management.
<a href="./rfc1212">RFC 1212</a> defines a more concise description mechanism, which
is wholly consistent with the SMI.
<a href="./rfc1156">RFC 1156</a> which defines MIB-I, the core set of managed
objects for the Internet suite of protocols. <a href="./rfc1213">RFC 1213</a>,
defines MIB-II, an evolution of MIB-I based on
implementation experience and new operational requirements.
<a href="./rfc1157">RFC 1157</a> which defines the SNMP, the protocol used for
network access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Objects</span>
Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB.
<span class="grey">Character MIB Working Group [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
Objects in the MIB are defined using the subset of Abstract
Syntax Notation One (ASN.1) [<a href="#ref-7" title=" International Organization for Standardization">7</a>] defined in the SMI. In
particular, each object has a name, a syntax, and an
encoding. The name is an object identifier, an
administratively assigned name, which specifies an object
type.
The object type together with an object instance serves to
uniquely identify a specific instantiation of the object.
For human convenience, we often use a textual string, termed
the OBJECT DESCRIPTOR, to also refer to the object type.
The syntax of an object type defines the abstract data
structure corresponding to that object type. The ASN.1
language is used for this purpose. However, the SMI [<a href="#ref-3" title=""Structure and Identification of Management Information for TCP/IP-based internets"">3</a>]
purposely restricts the ASN.1 constructs which may be used.
These restrictions are explicitly made for simplicity.
The encoding of an object type is simply how that object
type is represented using the object type's syntax.
Implicitly tied to the notion of an object type's syntax and
encoding is how the object type is represented when being
transmitted on the network.
The SMI specifies the use of the basic encoding rules of
ASN.1 [<a href="#ref-8" title=" International Standard 8825">8</a>], subject to the additional requirements imposed by
the SNMP.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Format of Definitions</span>
<a href="#section-5">Section 5</a> contains the specification of all object types
contained in this MIB module. The object types are defined
using the conventions defined in the SMI, as amended by the
extensions specified in [<a href="#ref-9" title=""Concise MIB Definitions"">9</a>,<a href="#ref-10" title=""A Convention for Defining Traps for use with the SNMP"">10</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Overview</span>
The Parallel-printer-like Hardware Device MIB applies to
interface ports that might logically support the Interface
MIB, a Transmission MIB, or the Character MIB (most likely
the latter). The most common example is a Centronics or
Data Products type parallel printer port.
The Parallel-printer-like MIB is one of a set of MIBs
designed for complementary use. At this writing, the set
comprises:
<span class="grey">Character MIB Working Group [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
Character MIB
PPP MIB
RS-232-like MIB
Parallel-printer-like MIB
The RS-232-like MIB and the Parallel-printer-like MIB
represent the physical layer, providing service to higher
layers such as the Character MIB or PPP MIB. Further MIBs
may appear above these.
The following diagram shows two possible "MIB stacks", each
using the RS-232-like MIB.
.-----------------.
.-----------------. | Standard MIB |
| Telnet MIB | | Interface Group |
|-----------------| |-----------------|
| Character MIB | | PPP MIB |
|-----------------| |-----------------|
| RS-232-like MIB | | RS-232-like MIB |
`-----------------' `-----------------'
The intent of the model is for the physical-level MIBs to
represent the lowest level, regardless of the higher level
that may be using it. In turn, separate higher level MIBs
represent specific applications, such as a terminal (the
Character MIB) or a network connection (the PPP MIB).
The Parallel-printer-like MIB is mandatory for all systems
that have such a hardware port supporting services managed
through some other MIB, for example, the Character MIB.
The Parallel-printer-like MIB includes multiple similar
types of hardware, and as a result contains objects not
applicable to all of those types. Such objects are in a
separate branch of the MIB, which is required when
applicable and otherwise absent.
The Parallel-printer-like MIB includes Centronics, Data
Products, and other parallel physical links with a similar
set of control signals.
The MIB contains objects that relate to physical layer
connections. Such connections may provide interesting
hardware signals (other than for basic data transfer), such
as Power and PaperOut.
The MIB comprises one base object and three tables, detailed
<span class="grey">Character MIB Working Group [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
in the following sections. The tables contain objects for
ports and input and output control signals.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Definitions</span>
<a href="./rfc1318">RFC1318</a>-MIB DEFINITIONS ::= BEGIN
IMPORTS
Counter
FROM <a href="./rfc1155">RFC1155</a>-SMI
transmission
FROM <a href="./rfc1213">RFC1213</a>-MIB
OBJECT-TYPE
FROM <a href="./rfc1212">RFC-1212</a>;
-- this is the MIB module for Parallel-printer-like
-- hardware devices
para OBJECT IDENTIFIER ::= { transmission 34 }
-- the generic Parallel-printer-like group
-- Implementation of this group is mandatory for all
-- systems that have Parallel-printer-like hardware
-- ports supporting higher level services such as
-- character streams
paraNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of ports (regardless of their current
state) in the Parallel-printer-like port table."
::= { para 1 }
-- the Parallel-printer-like Port table
paraPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF ParaPortEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of port entries. The number of entries is
given by the value of paraNumber."
::= { para 2 }
<span class="grey">Character MIB Working Group [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
paraPortEntry OBJECT-TYPE
SYNTAX ParaPortEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Status and parameter values for a port."
INDEX { paraPortIndex }
::= { paraPortTable 1 }
ParaPortEntry ::=
SEQUENCE {
paraPortIndex
INTEGER,
paraPortType
INTEGER,
paraPortInSigNumber
INTEGER,
paraPortOutSigNumber
INTEGER
}
paraPortIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique value for each port. Its value ranges
between 1 and the value of paraNumber. By
convention and if possible, hardware port numbers
map directly to external connectors. The value for
each port must remain constant at least from one
re-initialization of the network management agent to
the next."
::= { paraPortEntry 1 }
paraPortType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
centronics(2),
dataproducts(3)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The port's hardware type."
::= { paraPortEntry 2 }
paraPortInSigNumber OBJECT-TYPE
<span class="grey">Character MIB Working Group [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of input signals for the port in the
input signal table (paraPortInSigTable). The table
contains entries only for those signals the software
can detect."
::= { paraPortEntry 3 }
paraPortOutSigNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of output signals for the port in the
output signal table (paraPortOutSigTable). The
table contains entries only for those signals the
software can assert."
::= { paraPortEntry 4 }
-- the Input Signal table
paraInSigTable OBJECT-TYPE
SYNTAX SEQUENCE OF ParaInSigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A list of port input control signal entries."
::= { para 3 }
paraInSigEntry OBJECT-TYPE
SYNTAX ParaInSigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Input control signal status for a hardware port."
INDEX { paraInSigPortIndex, paraInSigName }
::= { paraInSigTable 1 }
ParaInSigEntry ::=
SEQUENCE {
paraInSigPortIndex
INTEGER,
paraInSigName
INTEGER,
paraInSigState
<span class="grey">Character MIB Working Group [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
INTEGER,
paraInSigChanges
Counter
}
paraInSigPortIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of paraPortIndex for the port to which
this entry belongs."
::= { paraInSigEntry 1 }
paraInSigName OBJECT-TYPE
SYNTAX INTEGER { power(1), online(2), busy(3),
paperout(4), fault(5) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Identification of a hardware signal."
::= { paraInSigEntry 2 }
paraInSigState OBJECT-TYPE
SYNTAX INTEGER { none(1), on(2), off(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current signal state."
::= { paraInSigEntry 3 }
paraInSigChanges OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the signal has changed from
'on' to 'off' or from 'off' to 'on'."
::= { paraInSigEntry 4 }
-- the Output Signal table
paraOutSigTable OBJECT-TYPE
SYNTAX SEQUENCE OF ParaOutSigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
<span class="grey">Character MIB Working Group [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
"A list of port output control signal entries."
::= { para 4 }
paraOutSigEntry OBJECT-TYPE
SYNTAX ParaOutSigEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Output control signal status for a hardware port."
INDEX { paraOutSigPortIndex, paraOutSigName }
::= { paraOutSigTable 1 }
ParaOutSigEntry ::=
SEQUENCE {
paraOutSigPortIndex
INTEGER,
paraOutSigName
INTEGER,
paraOutSigState
INTEGER,
paraOutSigChanges
Counter
}
paraOutSigPortIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of paraPortIndex for the port to which
this entry belongs."
::= { paraOutSigEntry 1 }
paraOutSigName OBJECT-TYPE
SYNTAX INTEGER { power(1), online(2), busy(3),
paperout(4), fault(5) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Identification of a hardware signal."
::= { paraOutSigEntry 2 }
paraOutSigState OBJECT-TYPE
SYNTAX INTEGER { none(1), on(2), off(3) }
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current signal state."
<span class="grey">Character MIB Working Group [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
::= { paraOutSigEntry 3 }
paraOutSigChanges OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of times the signal has changed from
'on' to 'off' or from 'off' to 'on'."
::= { paraOutSigEntry 4 }
END
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
Based on several private MIBs, this document was produced by the
Character MIB Working Group:
Anne Ambler, Spider
Charles Bazaar, Emulex
Christopher Bucci, Datability
Anthony Chung, Hughes LAN Systems
George Conant, Xyplex
John Cook, Chipcom
James Davin, MIT-LCS
Shawn Gallagher, DEC
Tom Grant, Xylogics
Frank Huang, Emulex
David Jordan, Emulex
Satish Joshi, SynOptics
Frank Kastenholz, Clearpoint
Ken Key, University of Tennessee
Jim Kinder, Fibercom
Rajeev Kochhar, 3Com
John LoVerso, Xylogics
Keith McCloghrie, Hughes LAN Systems
Donald Merritt, BRL
David Perkins, 3Com
Jim Reinstedler, Ungerman-Bass
Marshall Rose, PSI
Ron Strich, SSDS
Dean Throop, DG
Bill Townsend, Xylogics
Jesse Walker, DEC
David Waitzman, BBN
Bill Westfield, cisco
<span class="grey">Character MIB Working Group [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
[<a id="ref-1">1</a>] Cerf, V., "IAB Recommendations for the Development of Internet
Network Management Standards", <a href="./rfc1052">RFC 1052</a>, NRI, April 1988.
[<a id="ref-2">2</a>] Cerf, V., "Report of the Second Ad Hoc Network Management Review
Group", <a href="./rfc1109">RFC 1109</a>, NRI, August 1989.
[<a id="ref-3">3</a>] Rose M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", <a href="./rfc1155">RFC 1155</a>,
Performance Systems International, Hughes LAN Systems, May 1990.
[<a id="ref-4">4</a>] McCloghrie K., and M. Rose, "Management Information Base for
Network Management of TCP/IP-based internets", <a href="./rfc1156">RFC 1156</a>, Hughes
LAN Systems, Performance Systems International, May 1990.
[<a id="ref-5">5</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple
Network Management Protocol", <a href="./rfc1157">RFC 1157</a>, SNMP Research,
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[<a id="ref-6">6</a>] McCloghrie K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets", <a href="./rfc1213">RFC 1213</a>,
Performance Systems International, March 1991.
[<a id="ref-7">7</a>] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization, International
Standard 8824, December 1987.
[<a id="ref-8">8</a>] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One
(ASN.1), International Organization for Standardization,
International Standard 8825, December 1987.
[<a id="ref-9">9</a>] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
<a href="./rfc1212">RFC 1212</a>, Performance Systems International, Hughes LAN Systems,
March 1991.
[<a id="ref-10">10</a>] Rose, M., Editor, "A Convention for Defining Traps for use with
the SNMP", <a href="./rfc1215">RFC 1215</a>, Performance Systems International, March
1991.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
Security issues are not discussed in this memo.
<span class="grey">Character MIB Working Group [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc1318">RFC 1318</a> PARALLEL-PRINTER-LIKE-MIB April 1992</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Author's Address</span>
Bob Stewart
Xyplex, Inc.
330 Codman Hill Road
Boxborough, MA 01719
Phone: (508) 264-9900
EMail: rlstewart@eng.xyplex.com
Character MIB Working Group [Page 11]
</pre>
|
