Debian Codegraph @

rfc2239.html

raw
1 <pre>Network Working Group K. de Graaf
2 Request for Comments: 2239 3Com Corporation
3 Category: Standards Track D. Romascanu
4 Madge Networks Ltd.
5 D. McMaster
6 Cisco Systems Inc.
7 K. McCloghrie
8 Cisco Systems Inc.
9 S. Roberts
10 Farallon Computing, Inc.
11 November 1997
12
13
14 <span class="h1">Definitions of Managed Objects for IEEE 802.3</span>
15 <span class="h1">Medium Attachment Units (MAUs) using SMIv2</span>
16
17
18 Status of this Memo
19
20 This document specifies an Internet standards track protocol for the
21 Internet community, and requests discussion and suggestions for
22 improvements. Please refer to the current edition of the "Internet
23 Official Protocol Standards" (STD 1) for the standardization state
24 and status of this protocol. Distribution of this memo is unlimited.
25
26 Copyright Notice
27
28 Copyright (C) The Internet Society (1997). All Rights Reserved.
29
30 Table of Contents
31
32 <a href="#section-1">1</a> The SNMPv2 Network Management Framework ............... <a href="#page-2">2</a>
33 <a href="#section-1.1">1.1</a> Object Definitions .................................. <a href="#page-2">2</a>
34 <a href="#section-2">2</a> Overview .............................................. <a href="#page-3">3</a>
35 <a href="#section-2.1">2.1</a> Relationship to <a href="./rfc1515">RFC 1515</a> ............................ <a href="#page-3">3</a>
36 <a href="#section-2.2">2.2</a> MAU Management ...................................... <a href="#page-3">3</a>
37 <a href="#section-2.3">2.3</a> Relationship to Other MIBs .......................... <a href="#page-3">3</a>
38 <a href="#section-2.3.1">2.3.1</a> Relationship to the MIB-II 'interfaces' group ..... <a href="#page-3">3</a>
39 <a href="#section-2.3.2">2.3.2</a> Relationship to the 802.3 Repeater MIB ............ <a href="#page-4">4</a>
40 <a href="#section-2.4">2.4</a> Management of Internal MAUs ......................... <a href="#page-4">4</a>
41 <a href="#section-3">3</a> Definitions ........................................... <a href="#page-4">4</a>
42 <a href="#section-4">4</a> Acknowledgements ...................................... <a href="#page-39">39</a>
43 <a href="#section-5">5</a> References ............................................ <a href="#page-40">40</a>
44 <a href="#section-6">6</a> Security Considerations ............................... <a href="#page-41">41</a>
45 <a href="#section-7">7</a> Authors' Addresses .................................... <a href="#page-41">41</a>
46 <a href="#section-8">8</a> Full Copyright Statement .............................. <a href="#page-43">43</a>
47
48
49
50
51
52 <span class="grey">de Graaf, et. al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
55
56
57 Abstract
58
59 This memo defines an portion of the Management Information Base (MIB)
60 for use with network management protocols in the Internet community.
61 In particular, it defines objects for managing 10 and 100 Mb/second
62 Medium Attachment Units (MAUs) based on IEEE Std 802.3 <a href="#section-30">Section 30</a>,
63 "10 &amp; 100 Mb/s Management," October 26, 1995.
64
65 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The SNMPv2 Network Management Framework</span>
66
67 The SNMPv2 Network Management Framework presently consists of three
68 major components. They are:
69
70 o the SMI, described in <a href="./rfc1902">RFC 1902</a> [<a href="#ref-6" title="&quot;Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">6</a>] - the mechanisms used
71 for describing and naming objects for the purpose of management.
72
73 o the MIB-II, STD 17, <a href="./rfc1213">RFC 1213</a> [<a href="#ref-5" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">5</a>] - the core set of
74 managed objects for the Internet suite of protocols.
75
76 o the protocol, STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-10" title="&quot;Simple Network Management Protocol&quot;">10</a>] and/or <a href="./rfc1905">RFC 1905</a> [<a href="#ref-9" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">9</a>] -
77 the protocol used for accessing managed information.
78
79 Textual conventions are defined in <a href="./rfc1903">RFC 1903</a> [<a href="#ref-7" title="&quot;Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>], and conformance
80 statements are defined in <a href="./rfc1904">RFC 1904</a> [<a href="#ref-8" title="&quot;Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">8</a>].
81
82 The Framework permits new objects to be defined for the purpose of
83 experimentation and evaluation.
84
85 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Object Definitions</span>
86
87 Managed objects are accessed via a virtual information store, termed
88 the Management Information Base or MIB. Objects in the MIB are
89 defined using the subset of Abstract Syntax Notation One (ASN.1)
90 defined in the SMI. In particular, each object type is named by an
91 OBJECT IDENTIFIER, an administratively assigned name. The object
92 type together with an object instance serves to uniquely identify a
93 specific instantiation of the object. For human convenience, we
94 often use a textual string, termed the descriptor, to refer to the
95 object type.
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">de Graaf, et. al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
111
112
113 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Overview</span>
114
115 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Relationship to <a href="./rfc1515">RFC 1515</a></span>
116
117 This MIB is intended to be a superset of that defined by <a href="./rfc1515">RFC 1515</a>
118 [<a href="#ref-11" title="&quot;Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)&quot;">11</a>], which will go to historic status. This MIB includes all of the
119 objects contained in that MIB, plus several new ones which provide
120 additional capabilities. Implementors are encouraged to support all
121 applicable conformance groups in order to make the best use of the
122 new functionality provided by this MIB. The new objects provide
123 management support for:
124
125 o management of 100 Mb/s devices
126
127 o auto-negotiation on interface MAUs
128
129 o jack management
130
131 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. MAU Management</span>
132
133 Instances of these object types represent attributes of an IEEE 802.3
134 MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD
135 standard [<a href="#ref-1">1</a>] and [<a href="#ref-2" title="&quot;MAC Parameters, Physical Layer, Medium Attachment Units and Repeater for 100 Mb/s Operation, Type 100BASE-T,&quot;">2</a>]. These MAUs may be connected to IEEE 802.3
136 repeaters or to 802.3 (Ethernet-like) interfaces. For convenience
137 this document refers to these devices as "repeater MAUs" and
138 "interface MAUs."
139
140 The definitions presented here are based on <a href="#section-30.5">Section 30.5</a>, "Layer
141 Management for 10 &amp; 100 Mb/s Medium Attachment Units (MAUs)", and
142 Annex 30A, "GDMO Specifications for 802.3 managed objects" of IEEE
143 Std 802.3u-1995. That specification includes definitions for both
144 10Mb/s and 100Mb/s devices, and is essentially a superset of the
145 10Mb/s definitions given by IEEE 802.3 <a href="#section-20">Section 20</a>. This
146 specification is intended to serve the same purpose: to provide for
147 management of both 10Mb/s and 100Mb/s MAUs.
148
149 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Relationship to Other MIBs</span>
150
151 It is assumed that an agent implementing this MIB will also implement
152 (at least) the 'system' group defined in MIB-II [<a href="#ref-5" title="&quot;Management Information Base for Network Management of TCP/IP-based internets: MIB-II&quot;">5</a>]. The following
153 sections identify other MIBs that such an agent should implement.
154
155 <span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Relationship to the MIB-II 'interfaces' group</span>
156
157 The sections of this document that define interface MAU-related
158 objects specify an extension to the 'interfaces' group of MIB-II. An
159 agent implementing these interface-MAU related objects must also
160
161
162
163
164 <span class="grey">de Graaf, et. al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
167
168
169 implement the 'interfaces' group of MIB-II. The value of the object
170 ifMauIfIndex is the same as the value of 'ifIndex' used to
171 instantiate the interface to which the given MAU is connected.
172
173 It is expected that an agent implementing the interface-MAU related
174 objects in this MIB will also implement the Ethernet- like Interfaces
175 MIB, <a href="./rfc1650">RFC 1650</a>.
176
177 (Note that repeater ports are not represented as interfaces in the
178 sense of MIB-II's 'interfaces' group.)
179
180 <span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a>. Relationship to the 802.3 Repeater MIB</span>
181
182 The section of this document that defines repeater MAU-related
183 objects specifies an extension to the 802.3 Repeater MIB defined in
184 [<a href="#ref-4" title="&quot;Definitions of Managed Objects for IEEE 802.3 Repeater Devices using SMIv2&quot;">4</a>]. An agent implementing these repeater-MAU related objects must
185 also implement the 802.3 Repeater MIB.
186
187 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to
188 instantiate a repeater MAU variable shall be the same as the values
189 of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the
190 port to which the given MAU is connected.
191
192 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Management of Internal MAUs</span>
193
194 In some situations, a MAU can be "internal" -- i.e., its
195 functionality is implemented entirely within a device. For example,
196 a managed repeater may contain an internal repeater- MAU and/or an
197 internal interface-MAU through which management communications
198 originating on one of the repeater's external ports pass in order to
199 reach the management agent associated with the repeater. Such
200 internal MAUs may or may not be managed. If they are managed,
201 objects describing their attributes should appear in the appropriate
202 MIB subtree:
203
204 dot3RpMauBasicGroup for internal repeater-MAUs and
205 dot3IfMauBasicGroup for internal interface-MAUs.
206
207 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Definitions</span>
208
209 MAU-MIB DEFINITIONS ::= BEGIN
210
211 IMPORTS
212 Counter32, Integer32,
213 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
214 OBJECT-IDENTITY, mib-2
215 FROM SNMPv2-SMI
216 TruthValue, TEXTUAL-CONVENTION
217
218
219
220 <span class="grey">de Graaf, et. al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
223
224
225 FROM SNMPv2-TC
226 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
227 FROM SNMPv2-CONF;
228
229 mauMod MODULE-IDENTITY
230 LAST-UPDATED "9710310000Z"
231 ORGANIZATION "IETF HUB MIB Working Group"
232 CONTACT-INFO
233 "WG E-mail: [email protected]
234
235 Chair: Dan Romascanu
236 Postal: Madge Networks (Israel) Ltd.
237 Atidim Technology Park, Bldg. 3
238 Tel Aviv 61131, Israel
239 Tel: 972-3-6458414, 6458458
240 Fax: 972-3-6487146
241 E-mail: [email protected]
242
243 Editor: Kathryn de Graaf
244 Postal: 3Com Corporation
245 118 Turnpike Rd.
246 Southborough, MA 01772
247 USA
248 Tel: (508)229-1627
249 Fax: (508)490-5882
250 E-mail: [email protected]"
251 DESCRIPTION
252 "Management information for 802.3 MAUs.
253
254 The following references are used throughout this
255 MIB module:
256
257 [IEEE 802.3 Std]
258 refers to IEEE 802.3/ISO 8802-3 Information
259 processing systems - Local area networks -
260 Part 3: Carrier sense multiple access with
261 collision detection (CSMA/CD) access method
262 and physical layer specifications (1993),
263 and to IEEE Std 802.3u-1995, Supplement to
264 IEEE Std 802.3, clauses 22 through 29.
265
266 [IEEE 802.3 Mgt]
267 refers to IEEE 802.3u-1995, - 10 Mb/s &amp;
268 100 Mb/s Management, <a href="#section-30">Section 30</a> -
269 Supplement to IEEE Std 802.3."
270 ::= { snmpDot3MauMgt 6 }
271
272
273
274
275
276 <span class="grey">de Graaf, et. al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
279
280
281 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
282
283
284 -- textual conventions
285
286 JackType ::= TEXTUAL-CONVENTION
287 STATUS current
288 DESCRIPTION
289 "Common enumeration values for repeater and
290 interface MAU jack types."
291 SYNTAX INTEGER {
292 other(1),
293 rj45(2),
294 rj45S(3), -- rj45 shielded
295 db9(4),
296 bnc(5),
297 fAUI(6), -- female aui
298 mAUI(7), -- male aui
299 fiberSC(8),
300 fiberMIC(9),
301 fiberST(10),
302 telco(11)
303 }
304
305
306 dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
307 dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
308 dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
309
310 dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
311
312 -- object identities for MAU types
313 -- (see rpMauType and ifMauType for usage)
314
315 dot3MauType
316 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
317
318 dot3MauTypeAUI OBJECT-IDENTITY
319 STATUS current
320 DESCRIPTION
321 "no internal MAU, view from AUI"
322 ::= { dot3MauType 1 }
323
324 dot3MauType10Base5 OBJECT-IDENTITY
325 STATUS current
326 DESCRIPTION
327 "thick coax MAU (per 802.3 <a href="#section-8">section 8</a>)"
328 ::= { dot3MauType 2 }
329
330
331
332 <span class="grey">de Graaf, et. al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
335
336
337 dot3MauTypeFoirl OBJECT-IDENTITY
338 STATUS current
339 DESCRIPTION
340 "FOIRL MAU (per 802.3 <a href="#section-9.9">section 9.9</a>)"
341 ::= { dot3MauType 3 }
342
343 dot3MauType10Base2 OBJECT-IDENTITY
344 STATUS current
345 DESCRIPTION
346 "thin coax MAU (per 802.3 <a href="#section-10">section 10</a>)"
347 ::= { dot3MauType 4 }
348
349 dot3MauType10BaseT OBJECT-IDENTITY
350 STATUS current
351 DESCRIPTION
352 "UTP MAU (per 802.3 <a href="#section-14">section 14</a>)"
353 ::= { dot3MauType 5 }
354
355 dot3MauType10BaseFP OBJECT-IDENTITY
356 STATUS current
357 DESCRIPTION
358 "passive fiber MAU (per 802.3 <a href="#section-16">section 16</a>)"
359 ::= { dot3MauType 6 }
360
361 dot3MauType10BaseFB OBJECT-IDENTITY
362 STATUS current
363 DESCRIPTION
364 "sync fiber MAU (per 802.3 <a href="#section-17">section 17</a>)"
365 ::= { dot3MauType 7 }
366
367 dot3MauType10BaseFL OBJECT-IDENTITY
368 STATUS current
369 DESCRIPTION
370 "async fiber MAU (per 802.3 <a href="#section-18">section 18</a>)"
371 ::= { dot3MauType 8 }
372
373 dot3MauType10Broad36 OBJECT-IDENTITY
374 STATUS current
375 DESCRIPTION
376 "broadband DTE MAU (per 802.3 <a href="#section-11">section 11</a>). Note
377 that 10BROAD36 MAUs can be attached to interfaces
378 but not to repeaters."
379 ::= { dot3MauType 9 }
380
381 ------ new since <a href="./rfc1515">RFC 1515</a>:
382
383 dot3MauType10BaseTHD OBJECT-IDENTITY
384 STATUS current
385
386
387
388 <span class="grey">de Graaf, et. al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
391
392
393 DESCRIPTION
394 "UTP MAU (per 802.3 <a href="#section-14">section 14</a>), half duplex mode"
395 ::= { dot3MauType 10 }
396
397 dot3MauType10BaseTFD OBJECT-IDENTITY
398 STATUS current
399 DESCRIPTION
400 "UTP MAU (per 802.3 <a href="#section-14">section 14</a>), full duplex mode"
401 ::= { dot3MauType 11 }
402
403 dot3MauType10BaseFLHD OBJECT-IDENTITY
404 STATUS current
405 DESCRIPTION
406 "async fiber MAU (per 802.3 <a href="#section-18">section 18</a>), half
407 duplex mode"
408 ::= { dot3MauType 12 }
409
410 dot3MauType10BaseFLFD OBJECT-IDENTITY
411 STATUS current
412 DESCRIPTION
413 "async fiber MAU (per 802.3 <a href="#section-18">section 18</a>), full
414 duplex mode"
415 ::= { dot3MauType 13 }
416
417 dot3MauType100BaseT4 OBJECT-IDENTITY
418 STATUS current
419 DESCRIPTION
420 "4 pair categ. 3 UTP (per 802.3 <a href="#section-23">section 23</a>)"
421 ::= { dot3MauType 14 }
422
423 dot3MauType100BaseTXHD OBJECT-IDENTITY
424 STATUS current
425 DESCRIPTION
426 "2 pair categ. 5 UTP (per 802.3 <a href="#section-25">section 25</a>), half
427 duplex mode"
428 ::= { dot3MauType 15 }
429
430 dot3MauType100BaseTXFD OBJECT-IDENTITY
431 STATUS current
432 DESCRIPTION
433 "2 pair categ. 5 UTP (per 802.3 <a href="#section-25">section 25</a>), full
434 duplex mode"
435 ::= { dot3MauType 16 }
436
437 dot3MauType100BaseFXHD OBJECT-IDENTITY
438 STATUS current
439 DESCRIPTION
440 "X fiber over PMT (per 802.3 <a href="#section-26">section 26</a>), half
441
442
443
444 <span class="grey">de Graaf, et. al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
447
448
449 duplex mode"
450 ::= { dot3MauType 17 }
451
452 dot3MauType100BaseFXFD OBJECT-IDENTITY
453 STATUS current
454 DESCRIPTION
455 "X fiber over PMT (per 802.3 <a href="#section-26">section 26</a>), full
456 duplex mode"
457 ::= { dot3MauType 18 }
458
459 dot3MauType100BaseT2HD OBJECT-IDENTITY
460 STATUS current
461 DESCRIPTION
462 "2 pair categ. 3 UTP (per 802.3 <a href="#section-32">section 32</a>), half
463 duplex mode"
464 ::= { dot3MauType 19 }
465
466 dot3MauType100BaseT2FD OBJECT-IDENTITY
467 STATUS current
468 DESCRIPTION
469 "2 pair categ. 3 UTP (per 802.3 <a href="#section-32">section 32</a>), full
470 duplex mode"
471 ::= { dot3MauType 20 }
472
473
474 --
475 -- The Basic Repeater MAU Table
476 --
477
478 rpMauTable OBJECT-TYPE
479 SYNTAX SEQUENCE OF RpMauEntry
480 MAX-ACCESS not-accessible
481 STATUS current
482 DESCRIPTION
483 "Table of descriptive and status information about
484 the MAU(s) attached to the ports of a repeater."
485 ::= { dot3RpMauBasicGroup 1 }
486
487 rpMauEntry OBJECT-TYPE
488 SYNTAX RpMauEntry
489 MAX-ACCESS not-accessible
490 STATUS current
491 DESCRIPTION
492 "An entry in the table, containing information
493 about a single MAU."
494 INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex }
495 ::= { rpMauTable 1 }
496
497
498
499
500 <span class="grey">de Graaf, et. al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
503
504
505 RpMauEntry ::=
506 SEQUENCE {
507 rpMauGroupIndex
508 Integer32,
509 rpMauPortIndex
510 Integer32,
511 rpMauIndex
512 Integer32,
513 rpMauType
514 OBJECT IDENTIFIER,
515 rpMauStatus
516 INTEGER,
517 rpMauMediaAvailable
518 INTEGER,
519 rpMauMediaAvailableStateExits
520 Counter32,
521 rpMauJabberState
522 INTEGER,
523 rpMauJabberingStateEnters
524 Counter32,
525 rpMauFalseCarriers
526 Counter32
527 }
528
529 rpMauGroupIndex OBJECT-TYPE
530 SYNTAX Integer32 (1..2147483647)
531 MAX-ACCESS read-only
532 STATUS current
533 DESCRIPTION
534 "This variable uniquely identifies the group
535 containing the port to which the MAU described by
536 this entry is connected.
537
538 Note: In practice, a group will generally be a
539 field-replaceable unit (i.e., module, card, or
540 board) that can fit in the physical system
541 enclosure, and the group number will correspond to
542 a number marked on the physical enclosure.
543
544 The group denoted by a particular value of this
545 object is the same as the group denoted by the
546 same value of rptrGroupIndex."
547 ::= { rpMauEntry 1 }
548
549 rpMauPortIndex OBJECT-TYPE
550 SYNTAX Integer32 (1..2147483647)
551 MAX-ACCESS read-only
552 STATUS current
553
554
555
556 <span class="grey">de Graaf, et. al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
559
560
561 DESCRIPTION
562 "This variable uniquely identifies the repeater
563 port within group rpMauGroupIndex to which the MAU
564 described by this entry is connected."
565 REFERENCE
566 "Reference <a href="./rfc1516">RFC 1516</a>, rptrPortIndex."
567 ::= { rpMauEntry 2 }
568
569 rpMauIndex OBJECT-TYPE
570 SYNTAX Integer32 (1..2147483647)
571 MAX-ACCESS read-only
572 STATUS current
573 DESCRIPTION
574 "This variable uniquely identifies the MAU
575 described by this entry from among other MAUs
576 connected to the same port (rpMauPortIndex)."
577 REFERENCE
578 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
579 ::= { rpMauEntry 3 }
580
581 rpMauType OBJECT-TYPE
582 SYNTAX OBJECT IDENTIFIER
583 MAX-ACCESS read-only
584 STATUS current
585 DESCRIPTION
586 "This object identifies the 10 or 100 Mb/s
587 baseband MAU type. An initial set of MAU types
588 are defined above. The assignment of OBJECT
589 IDENTIFIERs to new types of MAUs is managed by the
590 IANA. If the MAU type is unknown, the object
591 identifier
592
593 unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
594
595 is returned. Note that unknownMauType is a
596 syntactically valid object identifier, and any
597 conformant implementation of ASN.1 and the BER
598 must be able to generate and recognize this
599 value."
600 REFERENCE
601 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
602 ::= { rpMauEntry 4 }
603
604 rpMauStatus OBJECT-TYPE
605 SYNTAX INTEGER {
606 other(1),
607 unknown(2),
608 operational(3),
609
610
611
612 <span class="grey">de Graaf, et. al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
615
616
617 standby(4),
618 shutdown(5),
619 reset(6)
620 }
621 MAX-ACCESS read-write
622 STATUS current
623 DESCRIPTION
624 "The current state of the MAU. This object may be
625 implemented as a read-only object by those agents
626 and MAUs that do not implement software control of
627 the MAU state. Some agents may not support
628 setting the value of this object to some of the
629 enumerated values.
630
631 The value other(1) is returned if the MAU is in a
632 state other than one of the states 2 through 6.
633
634 The value unknown(2) is returned when the MAU's
635 true state is unknown; for example, when it is
636 being initialized.
637
638 A MAU in the operational(3) state is fully
639 functional, operates, and passes signals to its
640 attached DTE or repeater port in accordance to its
641 specification.
642
643 A MAU in standby(4) state forces DI and CI to idle
644 and the media transmitter to idle or fault, if
645 supported. Standby(4) mode only applies to link
646 type MAUs. The state of rpMauMediaAvailable is
647 unaffected.
648
649 A MAU in shutdown(5) state assumes the same
650 condition on DI, CI, and the media transmitter as
651 though it were powered down or not connected. The
652 MAU may return other(1) value for the
653 rpMauJabberState and rpMauMediaAvailable objects
654 when it is in this state. For an AUI, this state
655 will remove power from the AUI.
656
657 Setting this variable to the value reset(6) resets
658 the MAU in the same manner as a power-off, power-
659 on cycle of at least one-half second would. The
660 agent is not required to return the value reset
661 (6).
662
663 Setting this variable to the value operational(3),
664 standby(4), or shutdown(5) causes the MAU to
665
666
667
668 <span class="grey">de Graaf, et. al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
671
672
673 assume the respective state except that setting a
674 mixing-type MAU or an AUI to standby(4) will cause
675 the MAU to enter the shutdown state."
676 REFERENCE
677 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState,
678 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
679 acRESETMAU."
680 ::= { rpMauEntry 5 }
681
682 rpMauMediaAvailable OBJECT-TYPE
683 SYNTAX INTEGER {
684 other(1),
685 unknown(2),
686 available(3),
687 notAvailable(4),
688 remoteFault(5),
689 invalidSignal(6),
690 remoteJabber(7),
691 remoteLinkLoss(8),
692 remoteTest(9)
693 }
694 MAX-ACCESS read-only
695 STATUS current
696 DESCRIPTION
697 "If the MAU is a link or fiber type (FOIRL,
698 10BASE-T, 10BASE-F) then this is equivalent to the
699 link test fail state/low light function. For an
700 AUI or a coax (including broadband) MAU this
701 indicates whether or not loopback is detected on
702 the DI circuit. The value of this attribute
703 persists between packets for MAU types AUI,
704 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
705
706 The value other(1) is returned if the
707 mediaAvailable state is not one of 2 through 6.
708
709 The value unknown(2) is returned when the MAU's
710 true state is unknown; for example, when it is
711 being initialized. At power-up or following a
712 reset, the value of this attribute will be unknown
713 for AUI, coax, and 10BASE-FP MAUs. For these MAUs
714 loopback will be tested on each transmission
715 during which no collision is detected. If DI is
716 receiving input when DO returns to IDL after a
717 transmission and there has been no collision
718 during the transmission then loopback will be
719 detected. The value of this attribute will only
720 change during non-collided transmissions for AUI,
721
722
723
724 <span class="grey">de Graaf, et. al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
727
728
729 coax, and 10BASE-FP MAUs.
730
731 For 100BASE-T4, 100BASE-TX and 100BASE-FX the
732 enumerations match the states within the
733 respective link integrity state diagrams, fig 23-
734 12 and 24-15 of sections <a href="#section-23">23</a> and <a href="#section-24">24</a> of [<a href="#ref-2" title="&quot;MAC Parameters, Physical Layer, Medium Attachment Units and Repeater for 100 Mb/s Operation, Type 100BASE-T,&quot;">2</a>]. Any
735 MAU which implements management of auto-
736 negotiation will map remote fault indication to
737 remote fault.
738
739 The value available(3) indicates that the link,
740 light, or loopback is normal. The value
741 notAvailable(4) indicates link loss, low light, or
742 no loopback.
743
744 The value remoteFault(5) indicates that a fault
745 has been detected at the remote end of the link.
746 This value applies to 10BASE-FB, 100BASE-T4 Far
747 End Fault Indication and non-specified remote
748 faults from a system running auto-negotiation.
749 The values remoteJabber(7), remoteLinkLoss(8), and
750 remoteTest(9) should be used instead of
751 remoteFault(5) where the reason for remote fault
752 is identified in the remote signaling protocol.
753
754 The value invalidSignal(6) indicates that an
755 invalid signal has been received from the other
756 end of the link. InvalidSignal(6) applies only to
757 MAUs of type 10BASE-FB.
758
759 Where an IEEE Std 802.3u-1995 clause 22 MII is
760 present, a logic one in the remote fault bit
761 (reference <a href="#section-22.2.4.2.8">section 22.2.4.2.8</a> of that document)
762 maps to the value remoteFault(5), and a logic zero
763 in the link status bit (reference <a href="#section-22.2.4.2.10">section</a>
764 <a href="#section-22.2.4.2.10">22.2.4.2.10</a> of that document) maps to the value
765 notAvailable(4). The value notAvailable(4) takes
766 precedence over the value remoteFault(5)."
767 REFERENCE
768 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
769 ::= { rpMauEntry 6 }
770
771 rpMauMediaAvailableStateExits OBJECT-TYPE
772 SYNTAX Counter32
773 MAX-ACCESS read-only
774 STATUS current
775 DESCRIPTION
776 "A count of the number of times that
777
778
779
780 <span class="grey">de Graaf, et. al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
783
784
785 rpMauMediaAvailable for this MAU instance leaves
786 the state available(3)."
787 REFERENCE
788 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
789 ::= { rpMauEntry 7 }
790
791 rpMauJabberState OBJECT-TYPE
792 SYNTAX INTEGER {
793 other(1),
794 unknown(2),
795 noJabber(3),
796 jabbering(4)
797 }
798 MAX-ACCESS read-only
799 STATUS current
800 DESCRIPTION
801 "The value other(1) is returned if the jabber
802 state is not 2, 3, or 4. The agent must always
803 return other(1) for MAU type dot3MauTypeAUI.
804
805 The value unknown(2) is returned when the MAU's
806 true state is unknown; for example, when it is
807 being initialized.
808
809 If the MAU is not jabbering the agent returns
810 noJabber(3). This is the 'normal' state.
811
812 If the MAU is in jabber state the agent returns
813 the jabbering(4) value."
814 REFERENCE
815 "[IEEE 802.3 Mgt], 30.5.1.1.6,
816 aJabber.jabberFlag."
817 ::= { rpMauEntry 8 }
818
819 rpMauJabberingStateEnters OBJECT-TYPE
820 SYNTAX Counter32
821 MAX-ACCESS read-only
822 STATUS current
823 DESCRIPTION
824 "A count of the number of times that
825 mauJabberState for this MAU instance enters the
826 state jabbering(4). For MAUs of type
827 dot3MauTypeAUI, dot3MauType100BaseT4,
828 dot3MauType100BaseTX, and dot3MauType100BaseFX,
829 this counter will always indicate zero."
830 REFERENCE
831 "[IEEE 802.3 Mgt], 30.5.1.1.6,
832 aJabber.jabberCounter."
833
834
835
836 <span class="grey">de Graaf, et. al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
839
840
841 ::= { rpMauEntry 9 }
842
843 rpMauFalseCarriers OBJECT-TYPE
844 SYNTAX Counter32
845 MAX-ACCESS read-only
846 STATUS current
847 DESCRIPTION
848 "A count of the number of false carrier events
849 during IDLE in 100BASE-X links. This counter does
850 not increment at the symbol rate. It can
851 increment after a valid carrier completion at a
852 maximum rate of once per 100 ms until the next
853 carrier event.
854
855 This counter increments only for MAUs of type
856 dot3MauType100BaseT4, dot3MauType100BaseTX, and
857 dot3MauType100BaseFX. For all other MAU types,
858 this counter will always indicate zero.
859
860 The approximate minimum time for rollover of this
861 counter is 7.4 hours."
862 REFERENCE
863 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
864 ::= { rpMauEntry 10 }
865
866
867 -- The rpJackTable applies to MAUs attached to repeaters
868 -- which have one or more external jacks (connectors).
869
870 rpJackTable OBJECT-TYPE
871 SYNTAX SEQUENCE OF RpJackEntry
872 MAX-ACCESS not-accessible
873 STATUS current
874 DESCRIPTION
875 "Information about the external jacks attached to
876 MAUs attached to the ports of a repeater."
877 ::= { dot3RpMauBasicGroup 2 }
878
879 rpJackEntry OBJECT-TYPE
880 SYNTAX RpJackEntry
881 MAX-ACCESS not-accessible
882 STATUS current
883 DESCRIPTION
884 "An entry in the table, containing information
885 about a particular jack."
886
887 INDEX { rpMauGroupIndex,
888 rpMauPortIndex,
889
890
891
892 <span class="grey">de Graaf, et. al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
895
896
897 rpMauIndex,
898 rpJackIndex }
899 ::= { rpJackTable 1 }
900
901 RpJackEntry ::=
902 SEQUENCE {
903 rpJackIndex
904 Integer32,
905 rpJackType
906 JackType
907 }
908
909 rpJackIndex OBJECT-TYPE
910 SYNTAX Integer32 (1..2147483647)
911 MAX-ACCESS not-accessible
912 STATUS current
913 DESCRIPTION
914 "This variable uniquely identifies the jack
915 described by this entry from among other jacks
916 attached to the same MAU (rpMauIndex)."
917 ::= { rpJackEntry 1 }
918
919 rpJackType OBJECT-TYPE
920 SYNTAX JackType
921 MAX-ACCESS read-only
922 STATUS current
923 DESCRIPTION
924 "The jack connector type, as it appears on the
925 outside of the system."
926 ::= { rpJackEntry 2 }
927
928
929 --
930 -- The Basic Interface MAU Table
931 --
932
933 ifMauTable OBJECT-TYPE
934 SYNTAX SEQUENCE OF IfMauEntry
935 MAX-ACCESS not-accessible
936 STATUS current
937 DESCRIPTION
938 "Table of descriptive and status information about
939 MAU(s) attached to an interface."
940
941 ::= { dot3IfMauBasicGroup 1 }
942
943 ifMauEntry OBJECT-TYPE
944 SYNTAX IfMauEntry
945
946
947
948 <span class="grey">de Graaf, et. al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
951
952
953 MAX-ACCESS not-accessible
954 STATUS current
955 DESCRIPTION
956 "An entry in the table, containing information
957 about a single MAU."
958 INDEX { ifMauIfIndex, ifMauIndex }
959 ::= { ifMauTable 1 }
960
961 IfMauEntry ::=
962 SEQUENCE {
963 ifMauIfIndex
964 Integer32,
965 ifMauIndex
966 Integer32,
967 ifMauType
968 OBJECT IDENTIFIER,
969 ifMauStatus
970 INTEGER,
971 ifMauMediaAvailable
972 INTEGER,
973 ifMauMediaAvailableStateExits
974 Counter32,
975 ifMauJabberState
976 INTEGER,
977 ifMauJabberingStateEnters
978 Counter32,
979 ifMauFalseCarriers
980 Counter32,
981 ifMauTypeList
982 Integer32,
983 ifMauDefaultType
984 OBJECT IDENTIFIER,
985 ifMauAutoNegSupported
986 TruthValue
987 }
988
989 ifMauIfIndex OBJECT-TYPE
990 SYNTAX Integer32 (1..2147483647)
991 MAX-ACCESS read-only
992 STATUS current
993 DESCRIPTION
994 "This variable uniquely identifies the interface
995 to which the MAU described by this entry is
996 connected."
997 REFERENCE
998 "<a href="./rfc1213">RFC 1213</a>, ifIndex"
999 ::= { ifMauEntry 1 }
1000
1001
1002
1003
1004 <span class="grey">de Graaf, et. al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1007
1008
1009 ifMauIndex OBJECT-TYPE
1010 SYNTAX Integer32 (1..2147483647)
1011 MAX-ACCESS read-only
1012 STATUS current
1013 DESCRIPTION
1014 "This variable uniquely identifies the MAU
1015 described by this entry from among other MAUs
1016 connected to the same interface (ifMauIfIndex)."
1017 REFERENCE
1018 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
1019 ::= { ifMauEntry 2 }
1020
1021 ifMauType OBJECT-TYPE
1022 SYNTAX OBJECT IDENTIFIER
1023 MAX-ACCESS read-only
1024 STATUS current
1025 DESCRIPTION
1026 "This object identifies the 10 or 100 Mb/s
1027 baseband or broadband MAU type. An initial set of
1028 MAU types are defined above. The assignment of
1029 OBJECT IDENTIFIERs to new types of MAUs is managed
1030 by the IANA. If the MAU type is unknown, the
1031 object identifier
1032
1033 unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
1034
1035 is returned. Note that unknownMauType is a
1036 syntactically valid object identifier, and any
1037 conformant implementation of ASN.1 and the BER
1038 must be able to generate and recognize this value.
1039
1040 This object represents the operational type of the
1041 MAU, as determined by either (1) the result of the
1042 auto-negotiation function or (2) if auto-
1043 negotiation is not enabled or is not implemented
1044 for this MAU, by the value of the object
1045 ifMauDefaultType. In case (2), a set to the
1046 object ifMauDefaultType will force the MAU into
1047 the new operating mode."
1048 REFERENCE
1049 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
1050 ::= { ifMauEntry 3 }
1051
1052 ifMauStatus OBJECT-TYPE
1053 SYNTAX INTEGER {
1054 other(1),
1055 unknown(2),
1056 operational(3),
1057
1058
1059
1060 <span class="grey">de Graaf, et. al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1063
1064
1065 standby(4),
1066 shutdown(5),
1067 reset(6)
1068 }
1069 MAX-ACCESS read-write
1070 STATUS current
1071 DESCRIPTION
1072 "The current state of the MAU. This object may be
1073 implemented as a read-only object by those agents
1074 and MAUs that do not implement software control of
1075 the MAU state. Some agents may not support
1076 setting the value of this object to some of the
1077 enumerated values.
1078
1079 The value other(1) is returned if the MAU is in a
1080 state other than one of the states 2 through 6.
1081
1082 The value unknown(2) is returned when the MAU's
1083 true state is unknown; for example, when it is
1084 being initialized.
1085
1086 A MAU in the operational(3) state is fully
1087 functional, operates, and passes signals to its
1088 attached DTE or repeater port in accordance to its
1089 specification.
1090
1091 A MAU in standby(4) state forces DI and CI to idle
1092 and the media transmitter to idle or fault, if
1093 supported. Standby(4) mode only applies to link
1094 type MAUs. The state of ifMauMediaAvailable is
1095 unaffected.
1096
1097 A MAU in shutdown(5) state assumes the same
1098 condition on DI, CI, and the media transmitter as
1099 though it were powered down or not connected. The
1100 MAU may return other(1) value for the
1101 ifMauJabberState and ifMauMediaAvailable objects
1102 when it is in this state. For an AUI, this state
1103 will remove power from the AUI.
1104
1105 Setting this variable to the value reset(6) resets
1106 the MAU in the same manner as a power-off, power-
1107 on cycle of at least one-half second would. The
1108 agent is not required to return the value reset
1109 (6).
1110
1111 Setting this variable to the value operational(3),
1112 standby(4), or shutdown(5) causes the MAU to
1113
1114
1115
1116 <span class="grey">de Graaf, et. al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1119
1120
1121 assume the respective state except that setting a
1122 mixing-type MAU or an AUI to standby(4) will cause
1123 the MAU to enter the shutdown state."
1124 REFERENCE
1125 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState,
1126 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
1127 acRESETMAU."
1128 ::= { ifMauEntry 4 }
1129
1130 ifMauMediaAvailable OBJECT-TYPE
1131 SYNTAX INTEGER {
1132 other(1),
1133 unknown(2),
1134 available(3),
1135 notAvailable(4),
1136 remoteFault(5),
1137 invalidSignal(6),
1138 remoteJabber(7),
1139 remoteLinkLoss(8),
1140 remoteTest(9)
1141 }
1142 MAX-ACCESS read-only
1143 STATUS current
1144 DESCRIPTION
1145 "If the MAU is a link or fiber type (FOIRL,
1146 10BASE-T, 10BASE-F) then this is equivalent to the
1147 link test fail state/low light function. For an
1148 AUI or a coax (including broadband) MAU this
1149 indicates whether or not loopback is detected on
1150 the DI circuit. The value of this attribute
1151 persists between packets for MAU types AUI,
1152 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
1153
1154 The value other(1) is returned if the
1155 mediaAvailable state is not one of 2 through 6.
1156
1157 The value unknown(2) is returned when the MAU's
1158 true state is unknown; for example, when it is
1159 being initialized. At power-up or following a
1160 reset, the value of this attribute will be unknown
1161 for AUI, coax, and 10BASE-FP MAUs. For these MAUs
1162 loopback will be tested on each transmission
1163 during which no collision is detected. If DI is
1164 receiving input when DO returns to IDL after a
1165 transmission and there has been no collision
1166 during the transmission then loopback will be
1167 detected. The value of this attribute will only
1168 change during non-collided transmissions for AUI,
1169
1170
1171
1172 <span class="grey">de Graaf, et. al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1175
1176
1177 coax, and 10BASE-FP MAUs.
1178
1179 For 100BASE-T4, 100BASE-TX and 100BASE-FX the
1180 enumerations match the states within the
1181 respective link integrity state diagrams, fig 23-
1182 12 and 24-15 of sections <a href="#section-23">23</a> and <a href="#section-24">24</a> of [<a href="#ref-2" title="&quot;MAC Parameters, Physical Layer, Medium Attachment Units and Repeater for 100 Mb/s Operation, Type 100BASE-T,&quot;">2</a>]. Any
1183 MAU which implements management of auto-
1184 negotiation will map remote fault indication to
1185 remote fault.
1186
1187 The value available(3) indicates that the link,
1188 light, or loopback is normal. The value
1189 notAvailable(4) indicates link loss, low light, or
1190 no loopback.
1191
1192 The value remoteFault(5) indicates that a fault
1193 has been detected at the remote end of the link.
1194 This value applies to 10BASE-FB, 100BASE-T4 Far
1195 End Fault Indication and non-specified remote
1196 faults from a system running auto-negotiation.
1197 The values remoteJabber(7), remoteLinkLoss(8), and
1198 remoteTest(9) should be used instead of
1199 remoteFault(5) where the reason for remote fault
1200 is identified in the remote signaling protocol.
1201
1202 The value invalidSignal(6) indicates that an
1203 invalid signal has been received from the other
1204 end of the link. InvalidSignal(6) applies only to
1205 MAUs of type 10BASE-FB.
1206
1207 Where an IEEE Std 802.3u-1995 clause 22 MII is
1208 present, a logic one in the remote fault bit
1209 (reference <a href="#section-22.2.4.2.8">section 22.2.4.2.8</a> of that document)
1210 maps to the value remoteFault(5), and a logic zero
1211 in the link status bit (reference <a href="#section-22.2.4.2.10">section</a>
1212 <a href="#section-22.2.4.2.10">22.2.4.2.10</a> of that document) maps to the value
1213 notAvailable(4). The value notAvailable(4) takes
1214 precedence over the value remoteFault(5)."
1215 REFERENCE
1216 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
1217 ::= { ifMauEntry 5 }
1218
1219 ifMauMediaAvailableStateExits OBJECT-TYPE
1220 SYNTAX Counter32
1221 MAX-ACCESS read-only
1222 STATUS current
1223 DESCRIPTION
1224 "A count of the number of times that
1225
1226
1227
1228 <span class="grey">de Graaf, et. al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1231
1232
1233 ifMauMediaAvailable for this MAU instance leaves
1234 the state available(3)."
1235 REFERENCE
1236 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
1237 ::= { ifMauEntry 6 }
1238
1239 ifMauJabberState OBJECT-TYPE
1240 SYNTAX INTEGER {
1241 other(1),
1242 unknown(2),
1243 noJabber(3),
1244 jabbering(4)
1245 }
1246 MAX-ACCESS read-only
1247 STATUS current
1248 DESCRIPTION
1249 "The value other(1) is returned if the jabber
1250 state is not 2, 3, or 4. The agent must always
1251 return other(1) for MAU type dot3MauTypeAUI.
1252
1253 The value unknown(2) is returned when the MAU's
1254 true state is unknown; for example, when it is
1255 being initialized.
1256
1257 If the MAU is not jabbering the agent returns
1258 noJabber(3). This is the 'normal' state.
1259
1260 If the MAU is in jabber state the agent returns
1261 the jabbering(4) value."
1262 REFERENCE
1263 "[IEEE 802.3 Mgt], 30.5.1.1.6,
1264 aJabber.jabberFlag."
1265 ::= { ifMauEntry 7 }
1266
1267 ifMauJabberingStateEnters OBJECT-TYPE
1268 SYNTAX Counter32
1269 MAX-ACCESS read-only
1270 STATUS current
1271 DESCRIPTION
1272 "A count of the number of times that
1273 mauJabberState for this MAU instance enters the
1274 state jabbering(4). For MAUs of type
1275 dot3MauTypeAUI, dot3MauType100BaseT4,
1276 dot3MauType100BaseTX, and dot3MauType100BaseFX,
1277 this counter will always indicate zero."
1278 REFERENCE
1279 "[IEEE 802.3 Mgt], 30.5.1.1.6,
1280 aJabber.jabberCounter."
1281
1282
1283
1284 <span class="grey">de Graaf, et. al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1287
1288
1289 ::= { ifMauEntry 8 }
1290
1291 ifMauFalseCarriers OBJECT-TYPE
1292 SYNTAX Counter32
1293 MAX-ACCESS read-only
1294 STATUS current
1295 DESCRIPTION
1296 "A count of the number of false carrier events
1297 during IDLE in 100BASE-X links. This counter does
1298 not increment at the symbol rate. It can
1299 increment after a valid carrier completion at a
1300 maximum rate of once per 100 ms until the next
1301 carrier event.
1302
1303 This counter increments only for MAUs of type
1304 dot3MauType100BaseT4, dot3MauType100BaseTX, and
1305 dot3MauType100BaseFX. For all other MAU types,
1306 this counter will always indicate zero.
1307
1308 The approximate minimum time for rollover of this
1309 counter is 7.4 hours."
1310 REFERENCE
1311 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
1312 ::= { ifMauEntry 9 }
1313
1314 ifMauTypeList OBJECT-TYPE
1315 SYNTAX Integer32
1316 MAX-ACCESS read-only
1317 STATUS current
1318 DESCRIPTION
1319 "A value that uniquely identifies the set of
1320 possible IEEE 802.3 types that the MAU could be.
1321 The value is a sum which initially takes the value
1322 zero. Then, for each type capability of this MAU,
1323 2 raised to the power noted below is added to the
1324 sum. For example, a MAU which has the capability
1325 to be only 10BASE-T would have a value of 512
1326 (2**9). In contrast, a MAU which supports both
1327 10Base-T (full duplex) and 100BASE-TX (full
1328 duplex) would have a value of ((2**11) + (2**16))
1329 or 67584.
1330
1331 The powers of 2 assigned to the capabilities are
1332 these:
1333
1334 Power Capability
1335 0 other or unknown
1336 1 AUI
1337
1338
1339
1340 <span class="grey">de Graaf, et. al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1343
1344
1345 2 10BASE-5
1346 3 FOIRL
1347 4 10BASE-2
1348 5 10BASE-T duplex mode unknown
1349 6 10BASE-FP
1350 7 10BASE-FB
1351 8 10BASE-FL duplex mode unknown
1352 9 10BROAD36
1353 10 10BASE-T half duplex mode
1354 11 10BASE-T full duplex mode
1355 12 10BASE-FL half duplex mode
1356 13 10BASE-FL full duplex mode
1357 14 100BASE-T4
1358 15 100BASE-TX half duplex mode
1359 16 100BASE-TX full duplex mode
1360 17 100BASE-FX half duplex mode
1361 18 100BASE-FX full duplex mode
1362 19 100BASE-T2 half duplex mode
1363 20 100BASE-T2 full duplex mode
1364
1365 If auto-negotiation is present on this MAU, this
1366 object will map to ifMauAutoNegCapability."
1367
1368 ::= { ifMauEntry 10 }
1369
1370 ifMauDefaultType OBJECT-TYPE
1371 SYNTAX OBJECT IDENTIFIER
1372 MAX-ACCESS read-write
1373 STATUS current
1374 DESCRIPTION
1375 "This object identifies the default administrative
1376 10 or 100 Mb/s baseband MAU type, to be used in
1377 conjunction with the operational MAU type denoted
1378 by ifMauType.
1379
1380 The set of possible values for this object is the
1381 same as the set defined for the ifMauType object.
1382
1383 This object represents the administratively-
1384 configured type of the MAU. If auto-negotiation
1385 is not enabled or is not implemented for this MAU,
1386 the value of this object determines the
1387 operational type of the MAU. In this case, a set
1388 to this object will force the MAU into the
1389 specified operating mode.
1390
1391 If auto-negotiation is implemented and enabled for
1392 this MAU, the operational type of the MAU is
1393
1394
1395
1396 <span class="grey">de Graaf, et. al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1399
1400
1401 determined by auto-negotiation, and the value of
1402 this object denotes the type to which the MAU will
1403 automatically revert if/when auto-negotiation is
1404 later disabled.
1405
1406 NOTE TO IMPLEMENTORS: It may be necessary to
1407 provide for underlying hardware implementations
1408 which do not follow the exact behavior specified
1409 above. In particular, when
1410 ifMauAutoNegAdminStatus transitions from enabled
1411 to disabled, the agent implementation must ensure
1412 that the operational type of the MAU (as reported
1413 by ifMauType) correctly transitions to the value
1414 specified by this object, rather than continuing
1415 to operate at the value earlier determined by the
1416 auto-negotiation function."
1417 REFERENCE
1418 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID, and [IEEE
1419 802.3 Std], 22.2.4.1.4."
1420 ::= { ifMauEntry 11 }
1421
1422 ifMauAutoNegSupported OBJECT-TYPE
1423 SYNTAX TruthValue
1424 MAX-ACCESS read-only
1425 STATUS current
1426 DESCRIPTION
1427 "This object indicates whether or not auto-
1428 negotiation is supported on this MAU."
1429 ::= { ifMauEntry 12 }
1430
1431
1432
1433 -- The ifJackTable applies to MAUs attached to interfaces
1434 -- which have one or more external jacks (connectors).
1435
1436 ifJackTable OBJECT-TYPE
1437 SYNTAX SEQUENCE OF IfJackEntry
1438 MAX-ACCESS not-accessible
1439 STATUS current
1440 DESCRIPTION
1441 "Information about the external jacks attached to
1442 MAUs attached to an interface."
1443 ::= { dot3IfMauBasicGroup 2 }
1444
1445 ifJackEntry OBJECT-TYPE
1446 SYNTAX IfJackEntry
1447 MAX-ACCESS not-accessible
1448 STATUS current
1449
1450
1451
1452 <span class="grey">de Graaf, et. al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1455
1456
1457 DESCRIPTION
1458 "An entry in the table, containing information
1459 about a particular jack."
1460 INDEX { ifMauIfIndex,
1461 ifMauIndex,
1462 ifJackIndex }
1463 ::= { ifJackTable 1 }
1464
1465 IfJackEntry ::=
1466 SEQUENCE {
1467 ifJackIndex
1468 Integer32,
1469 ifJackType
1470 JackType
1471 }
1472
1473
1474 ifJackIndex OBJECT-TYPE
1475 SYNTAX Integer32 (1..2147483647)
1476 MAX-ACCESS not-accessible
1477 STATUS current
1478 DESCRIPTION
1479 "This variable uniquely identifies the jack
1480 described by this entry from among other jacks
1481 attached to the same MAU."
1482 ::= { ifJackEntry 1 }
1483
1484 ifJackType OBJECT-TYPE
1485 SYNTAX JackType
1486 MAX-ACCESS read-only
1487 STATUS current
1488 DESCRIPTION
1489 "The jack connector type, as it appears on the
1490 outside of the system."
1491 ::= { ifJackEntry 2 }
1492
1493
1494 -- The ifMauAutoNegTable applies to systems in which
1495 -- auto-negotiation is supported on one or more MAUs
1496 -- attached to interfaces. Note that if auto-negotiation
1497 -- is present and enabled, the ifMauType object reflects
1498 -- the result of the auto-negotiation function.
1499
1500 ifMauAutoNegTable OBJECT-TYPE
1501 SYNTAX SEQUENCE OF IfMauAutoNegEntry
1502 MAX-ACCESS not-accessible
1503 STATUS current
1504 DESCRIPTION
1505
1506
1507
1508 <span class="grey">de Graaf, et. al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1511
1512
1513 "Configuration and status objects for the auto-
1514 negotiation function of MAUs attached to
1515 interfaces."
1516 ::= { dot3IfMauAutoNegGroup 1 }
1517
1518 ifMauAutoNegEntry OBJECT-TYPE
1519 SYNTAX IfMauAutoNegEntry
1520 MAX-ACCESS not-accessible
1521 STATUS current
1522 DESCRIPTION
1523 "An entry in the table, containing configuration
1524 and status information for the auto-negotiation
1525 function of a particular MAU."
1526 INDEX { ifMauIfIndex, ifMauIndex }
1527 ::= { ifMauAutoNegTable 1 }
1528
1529 IfMauAutoNegEntry ::=
1530 SEQUENCE {
1531 ifMauAutoNegAdminStatus
1532 INTEGER,
1533 ifMauAutoNegRemoteSignaling
1534 INTEGER,
1535 ifMauAutoNegConfig
1536 INTEGER,
1537 ifMauAutoNegCapability
1538 Integer32,
1539 ifMauAutoNegCapAdvertised
1540 Integer32,
1541 ifMauAutoNegCapReceived
1542 Integer32,
1543 ifMauAutoNegRestart
1544 INTEGER
1545
1546 }
1547
1548
1549 ifMauAutoNegAdminStatus OBJECT-TYPE
1550 SYNTAX INTEGER {
1551 enabled(1),
1552 disabled(2)
1553 }
1554 MAX-ACCESS read-write
1555 STATUS current
1556 DESCRIPTION
1557 "Setting this object to enabled(1) will cause the
1558 interface which has the auto-negotiation signaling
1559 ability to be enabled.
1560
1561
1562
1563
1564 <span class="grey">de Graaf, et. al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1567
1568
1569 If the value of this object is disabled(2) then
1570 the interface will act as it would if it had no
1571 auto-negotiation signaling. Under these
1572 conditions, an IEEE 802.3 MAU will immediately be
1573 forced to the state indicated by the value of the
1574 object ifMauDefaultType.
1575
1576 NOTE TO IMPLEMENTORS: When
1577 ifMauAutoNegAdminStatus transitions from enabled
1578 to disabled, the agent implementation must ensure
1579 that the operational type of the MAU (as reported
1580 by ifMauType) correctly transitions to the value
1581 specified by the ifMauDefaultType object, rather
1582 than continuing to operate at the value earlier
1583 determined by the auto-negotiation function."
1584 REFERENCE
1585 "[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState
1586 and 30.6.1.2.2, acAutoNegAdminControl."
1587 ::= { ifMauAutoNegEntry 1 }
1588
1589 ifMauAutoNegRemoteSignaling OBJECT-TYPE
1590 SYNTAX INTEGER {
1591 detected(1),
1592 notdetected(2)
1593 }
1594 MAX-ACCESS read-only
1595 STATUS current
1596 DESCRIPTION
1597 "A value indicating whether the remote end of the
1598 link is using auto-negotiation signaling. It takes
1599 the value detected(1) if and only if, during the
1600 previous link negotiation, FLP Bursts were
1601 received."
1602 REFERENCE
1603 "[IEEE 802.3 Mgt], 30.6.1.1.3,
1604 aAutoNegRemoteSignaling."
1605 ::= { ifMauAutoNegEntry 2 }
1606
1607 ifMauAutoNegConfig OBJECT-TYPE
1608 SYNTAX INTEGER {
1609 other(1),
1610 configuring(2),
1611 complete(3),
1612 disabled(4),
1613 parallelDetectFail(5)
1614 }
1615 MAX-ACCESS read-only
1616 STATUS current
1617
1618
1619
1620 <span class="grey">de Graaf, et. al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1623
1624
1625 DESCRIPTION
1626 "A value indicating the current status of the
1627 auto-negotiation process. The enumeration
1628 parallelDetectFail(5) maps to a failure in
1629 parallel detection as defined in 28.2.3.1 of [IEEE
1630 802.3 Std]."
1631 REFERENCE
1632 "[IEEE 802.3 Mgt], 30.6.1.1.4,
1633 aAutoNegAutoConfig."
1634 ::= { ifMauAutoNegEntry 4 }
1635
1636 ifMauAutoNegCapability OBJECT-TYPE
1637 SYNTAX Integer32
1638 MAX-ACCESS read-only
1639 STATUS current
1640 DESCRIPTION
1641 "A value that uniquely identifies the set of
1642 capabilities of the local auto-negotiation entity.
1643 The value is a sum which initially takes the value
1644 zero. Then, for each capability of this
1645 interface, 2 raised to the power noted below is
1646 added to the sum. For example, an interface which
1647 has the capability to support only 100Base-TX half
1648 duplex would have a value of 32768 (2**15). In
1649 contrast, an interface which supports both
1650 100Base-TX half duplex and and 100Base-TX full
1651 duplex would have a value of 98304 ((2**15) +
1652 (2**16)).
1653
1654 The powers of 2 assigned to the capabilities are
1655 these:
1656
1657 Power Capability
1658 0 other or unknown
1659 (1-9) (reserved)
1660 10 10BASE-T half duplex mode
1661 11 10BASE-T full duplex mode
1662 12 (reserved)
1663 13 (reserved)
1664 14 100BASE-T4
1665 15 100BASE-TX half duplex mode
1666 16 100BASE-TX full duplex mode
1667 17 (reserved)
1668 18 (reserved)
1669 19 100BASE-T2 half duplex mode
1670 20 100BASE-T2 full duplex mode
1671
1672 Note that interfaces that support this MIB may
1673
1674
1675
1676 <span class="grey">de Graaf, et. al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1679
1680
1681 have capabilities that extend beyond the scope of
1682 this MIB."
1683 REFERENCE
1684 "[IEEE 802.3 Mgt], 30.6.1.1.5,
1685 aAutoNegLocalTechnologyAbility."
1686 ::= { ifMauAutoNegEntry 5 }
1687
1688 ifMauAutoNegCapAdvertised OBJECT-TYPE
1689 SYNTAX Integer32
1690 MAX-ACCESS read-write
1691 STATUS current
1692 DESCRIPTION
1693 "A value that uniquely identifies the set of
1694 capabilities advertised by the local auto-
1695 negotiation entity. Refer to
1696 ifMauAutoNegCapability for a description of the
1697 possible values of this object.
1698
1699 Capabilities in this object that are not available
1700 in ifMauAutoNegCapability cannot be enabled."
1701 REFERENCE
1702 "[IEEE 802.3 Mgt], 30.6.1.1.6,
1703 aAutoNegAdvertisedTechnologyAbility."
1704 ::= { ifMauAutoNegEntry 6 }
1705
1706 ifMauAutoNegCapReceived OBJECT-TYPE
1707 SYNTAX Integer32
1708 MAX-ACCESS read-only
1709 STATUS current
1710 DESCRIPTION
1711 "A value that uniquely identifies the set of
1712 capabilities received from the remote auto-
1713 negotiation entity. Refer to
1714 ifMauAutoNegCapability for a description of the
1715 possible values of this object.
1716
1717 Note that interfaces that support this MIB may be
1718 attached to remote auto-negotiation entities which
1719 have capabilities beyond the scope of this MIB."
1720 REFERENCE
1721 "[IEEE 802.3 Mgt], 30.6.1.1.7,
1722 aAutoNegReceivedTechnologyAbility."
1723 ::= { ifMauAutoNegEntry 7 }
1724
1725 ifMauAutoNegRestart OBJECT-TYPE
1726 SYNTAX INTEGER {
1727 restart(1),
1728 norestart(2)
1729
1730
1731
1732 <span class="grey">de Graaf, et. al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1735
1736
1737 }
1738 MAX-ACCESS read-write
1739 STATUS current
1740 DESCRIPTION
1741 "If the value of this object is set to restart(1)
1742 then this will force auto-negotiation to begin
1743 link renegotiation. If auto-negotiation signaling
1744 is disabled, a write to this object has no effect.
1745
1746 Setting the value of this object to norestart(2)
1747 has no effect."
1748 REFERENCE
1749 "[IEEE 802.3 Mgt], 30.6.1.2.1,
1750 acAutoNegRestartAutoConfig."
1751 ::= { ifMauAutoNegEntry 8 }
1752
1753
1754 --
1755 -- The Basic Broadband MAU Table
1756 --
1757
1758 broadMauBasicTable OBJECT-TYPE
1759 SYNTAX SEQUENCE OF BroadMauBasicEntry
1760 MAX-ACCESS not-accessible
1761 STATUS current
1762 DESCRIPTION
1763 "Table of descriptive and status information about
1764 the broadband MAUs connected to interfaces."
1765 ::= { dot3BroadMauBasicGroup 1 }
1766
1767 broadMauBasicEntry OBJECT-TYPE
1768 SYNTAX BroadMauBasicEntry
1769 MAX-ACCESS not-accessible
1770 STATUS current
1771 DESCRIPTION
1772 "An entry in the table, containing information
1773 about a single broadband MAU."
1774 INDEX { broadMauIfIndex, broadMauIndex }
1775 ::= { broadMauBasicTable 1 }
1776
1777 BroadMauBasicEntry ::=
1778 SEQUENCE {
1779 broadMauIfIndex
1780 Integer32,
1781 broadMauIndex
1782 Integer32,
1783 broadMauXmtRcvSplitType
1784 INTEGER,
1785
1786
1787
1788 <span class="grey">de Graaf, et. al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1791
1792
1793 broadMauXmtCarrierFreq
1794 Integer32,
1795 broadMauTranslationFreq
1796 Integer32
1797 }
1798
1799 broadMauIfIndex OBJECT-TYPE
1800 SYNTAX Integer32 (1..2147483647)
1801 MAX-ACCESS read-only
1802 STATUS current
1803 DESCRIPTION
1804 "This variable uniquely identifies the interface
1805 to which the MAU described by this entry is
1806 connected."
1807 REFERENCE
1808 "Reference <a href="./rfc1213">RFC 1213</a>, ifIndex."
1809 ::= { broadMauBasicEntry 1 }
1810
1811 broadMauIndex OBJECT-TYPE
1812 SYNTAX Integer32 (1..2147483647)
1813 MAX-ACCESS read-only
1814 STATUS current
1815 DESCRIPTION
1816 "This variable uniquely identifies the MAU
1817 connected to interface broadMauIfIndex that is
1818 described by this entry."
1819 REFERENCE
1820 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID."
1821 ::= { broadMauBasicEntry 2 }
1822
1823 broadMauXmtRcvSplitType OBJECT-TYPE
1824 SYNTAX INTEGER {
1825 other(1),
1826 single(2),
1827 dual(3)
1828 }
1829 MAX-ACCESS read-only
1830 STATUS current
1831 DESCRIPTION
1832 "This object indicates the type of frequency
1833 multiplexing/cabling system used to separate the
1834 transmit and receive paths for the 10BROAD36 MAU.
1835
1836 The value other(1) is returned if the split type
1837 is not either single or dual.
1838
1839 The value single(2) indicates a single cable
1840 system. The value dual(3) indicates a dual cable
1841
1842
1843
1844 <span class="grey">de Graaf, et. al. Standards Track [Page 33]</span></pre>
1845 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1846 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1847
1848
1849 system, offset normally zero."
1850 REFERENCE
1851 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
1852 aBbMAUXmitRcvSplitType."
1853 ::= { broadMauBasicEntry 3 }
1854
1855 broadMauXmtCarrierFreq OBJECT-TYPE
1856 SYNTAX Integer32
1857 MAX-ACCESS read-only
1858 STATUS current
1859 DESCRIPTION
1860 "This variable indicates the transmit carrier
1861 frequency of the 10BROAD36 MAU in MHz/4; that is,
1862 in units of 250 kHz."
1863 REFERENCE
1864 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
1865 aBroadbandFrequencies.xmitCarrierFrequency."
1866 ::= { broadMauBasicEntry 4 }
1867
1868 broadMauTranslationFreq OBJECT-TYPE
1869 SYNTAX Integer32
1870 MAX-ACCESS read-only
1871 STATUS current
1872 DESCRIPTION
1873 "This variable indicates the translation offset
1874 frequency of the 10BROAD36 MAU in MHz/4; that is,
1875 in units of 250 kHz."
1876 REFERENCE
1877 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
1878 aBroadbandFrequencies.translationFrequency."
1879 ::= { broadMauBasicEntry 5 }
1880
1881
1882
1883 -- Notifications for use by 802.3 MAUs
1884
1885 rpMauJabberTrap NOTIFICATION-TYPE
1886 OBJECTS { rpMauJabberState }
1887 STATUS current
1888 DESCRIPTION
1889 "This trap is sent whenever a managed repeater MAU
1890 enters the jabber state.
1891
1892 The agent must throttle the generation of
1893 consecutive rpMauJabberTraps so that there is at
1894 least a five-second gap between them."
1895 REFERENCE
1896 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
1897
1898
1899
1900 <span class="grey">de Graaf, et. al. Standards Track [Page 34]</span></pre>
1901 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1902 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1903
1904
1905 notification."
1906 ::= { snmpDot3MauMgt 0 1 }
1907
1908 ifMauJabberTrap NOTIFICATION-TYPE
1909 OBJECTS { ifMauJabberState }
1910 STATUS current
1911 DESCRIPTION
1912 "This trap is sent whenever a managed interface
1913 MAU enters the jabber state.
1914
1915 The agent must throttle the generation of
1916 consecutive ifMauJabberTraps so that there is at
1917 least a five-second gap between them."
1918 REFERENCE
1919 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
1920 notification."
1921 ::= { snmpDot3MauMgt 0 2 }
1922
1923
1924 -- Conformance information
1925
1926 mauModConf
1927 OBJECT IDENTIFIER ::= { mauMod 1 }
1928 mauModCompls
1929 OBJECT IDENTIFIER ::= { mauModConf 1 }
1930 mauModObjGrps
1931 OBJECT IDENTIFIER ::= { mauModConf 2 }
1932 mauModNotGrps
1933 OBJECT IDENTIFIER ::= { mauModConf 3 }
1934
1935
1936 -- Object groups
1937
1938 mauRpGrpBasic OBJECT-GROUP
1939 OBJECTS { rpMauGroupIndex,
1940 rpMauPortIndex,
1941 rpMauIndex,
1942 rpMauType,
1943 rpMauStatus,
1944 rpMauMediaAvailable,
1945 rpMauMediaAvailableStateExits,
1946 rpMauJabberState,
1947 rpMauJabberingStateEnters }
1948 STATUS current
1949 DESCRIPTION
1950 "Basic conformance group for MAUs attached to
1951 repeater ports. This group is also the
1952 conformance specification for <a href="./rfc1515">RFC 1515</a>
1953
1954
1955
1956 <span class="grey">de Graaf, et. al. Standards Track [Page 35]</span></pre>
1957 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1958 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
1959
1960
1961 implementations."
1962 ::= { mauModObjGrps 1 }
1963
1964 mauRpGrp100Mbs OBJECT-GROUP
1965 OBJECTS { rpMauFalseCarriers }
1966 STATUS current
1967 DESCRIPTION
1968 "Conformance group for MAUs attached to
1969 repeater ports with 100 Mb/s capability."
1970 ::= { mauModObjGrps 2 }
1971
1972 mauRpGrpJack OBJECT-GROUP
1973 OBJECTS { rpJackType }
1974 STATUS current
1975 DESCRIPTION
1976 "Conformance group for MAUs attached to
1977 repeater ports with managed jacks."
1978 ::= { mauModObjGrps 3 }
1979
1980 mauIfGrpBasic OBJECT-GROUP
1981 OBJECTS { ifMauIfIndex,
1982 ifMauIndex,
1983 ifMauType,
1984 ifMauStatus,
1985 ifMauMediaAvailable,
1986 ifMauMediaAvailableStateExits,
1987 ifMauJabberState,
1988 ifMauJabberingStateEnters }
1989 STATUS current
1990 DESCRIPTION
1991 "Basic conformance group for MAUs attached to
1992 interfaces. This group also provides a
1993 conformance specification for <a href="./rfc1515">RFC 1515</a>
1994 implementations."
1995 ::= { mauModObjGrps 4 }
1996
1997 mauIfGrp100Mbs OBJECT-GROUP
1998 OBJECTS { ifMauFalseCarriers,
1999 ifMauTypeList,
2000 ifMauDefaultType,
2001 ifMauAutoNegSupported }
2002 STATUS current
2003 DESCRIPTION
2004 "Conformance group for MAUs attached
2005 to interfaces with 100 Mb/s capability."
2006 ::= { mauModObjGrps 5 }
2007
2008 mauIfGrpJack OBJECT-GROUP
2009
2010
2011
2012 <span class="grey">de Graaf, et. al. Standards Track [Page 36]</span></pre>
2013 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2014 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
2015
2016
2017 OBJECTS { ifJackType }
2018 STATUS current
2019 DESCRIPTION
2020 "Conformance group for MAUs attached
2021 to interfaces with managed jacks."
2022 ::= { mauModObjGrps 6 }
2023
2024 mauIfGrpAutoNeg OBJECT-GROUP
2025 OBJECTS { ifMauAutoNegAdminStatus,
2026 ifMauAutoNegRemoteSignaling,
2027 ifMauAutoNegConfig,
2028 ifMauAutoNegCapability,
2029 ifMauAutoNegCapAdvertised,
2030 ifMauAutoNegCapReceived,
2031 ifMauAutoNegRestart }
2032 STATUS current
2033 DESCRIPTION
2034 "Conformance group for MAUs attached to
2035 interfaces with managed auto-negotiation."
2036 ::= { mauModObjGrps 7 }
2037
2038 mauBroadBasic OBJECT-GROUP
2039 OBJECTS { broadMauIfIndex,
2040 broadMauIndex,
2041 broadMauXmtRcvSplitType,
2042 broadMauXmtCarrierFreq,
2043 broadMauTranslationFreq }
2044 STATUS current
2045 DESCRIPTION
2046 "Conformance group for broadband MAUs
2047 attached to interfaces. This group
2048 provides a conformance specification
2049 for <a href="./rfc1515">RFC 1515</a> implementations."
2050 ::= { mauModObjGrps 8 }
2051
2052 -- Notification groups
2053
2054 rpMauNotifications NOTIFICATION-GROUP
2055 NOTIFICATIONS { rpMauJabberTrap }
2056 STATUS current
2057 DESCRIPTION
2058 "Notifications for repeater MAUs."
2059 ::= { mauModNotGrps 1 }
2060
2061 ifMauNotifications NOTIFICATION-GROUP
2062 NOTIFICATIONS { ifMauJabberTrap }
2063 STATUS current
2064 DESCRIPTION
2065
2066
2067
2068 <span class="grey">de Graaf, et. al. Standards Track [Page 37]</span></pre>
2069 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2070 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
2071
2072
2073 "Notifications for interface MAUs."
2074 ::= { mauModNotGrps 2 }
2075
2076
2077 -- Compliances
2078
2079 mauModRpCompl MODULE-COMPLIANCE
2080 STATUS current
2081 DESCRIPTION
2082 "Compliance for MAUs attached to repeater ports."
2083
2084 MODULE -- this module
2085 MANDATORY-GROUPS { mauRpGrpBasic }
2086
2087 GROUP mauRpGrp100Mbs
2088 DESCRIPTION
2089 "Implementation of this optional group is
2090 recommended for MAUs which have 100Mb/s
2091 capability."
2092
2093 GROUP mauRpGrpJack
2094 DESCRIPTION
2095 "Implementation of this optional group is
2096 recommended for MAUs which have one or more
2097 external jacks."
2098
2099 GROUP rpMauNotifications
2100 DESCRIPTION
2101 "Implementation of this group is
2102 recommended for MAUs attached to repeater
2103 ports."
2104
2105 ::= { mauModCompls 1 }
2106
2107
2108 mauModIfCompl MODULE-COMPLIANCE
2109 STATUS current
2110 DESCRIPTION
2111 "Compliance for MAUs attached to interfaces."
2112
2113 MODULE -- this module
2114 MANDATORY-GROUPS { mauIfGrpBasic }
2115
2116 GROUP mauIfGrp100Mbs
2117 DESCRIPTION
2118 "Implementation of this optional group is
2119 recommended for MAUs which have 100Mb/s
2120 capability."
2121
2122
2123
2124 <span class="grey">de Graaf, et. al. Standards Track [Page 38]</span></pre>
2125 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2126 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
2127
2128
2129 GROUP mauIfGrpJack
2130 DESCRIPTION
2131 "Implementation of this optional group is
2132 recommended for MAUs which have one or more
2133 external jacks."
2134
2135 GROUP mauIfGrpAutoNeg
2136 DESCRIPTION
2137 "Implementation of this group is
2138 mandatory for MAUs which support
2139 managed auto-negotiation."
2140
2141 GROUP mauBroadBasic
2142 DESCRIPTION
2143 "Implementation of this group is
2144 mandatory for broadband MAUs."
2145
2146 GROUP ifMauNotifications
2147 DESCRIPTION
2148 "Implementation of this group is
2149 recommended for MAUs attached to
2150 interfaces."
2151
2152 ::= { mauModCompls 2 }
2153
2154 END
2155
2156 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span>
2157
2158 This document was produced by the IETF Hub MIB Working Group, whose
2159 efforts were greatly advanced by the contributions of the following
2160 people:
2161
2162 Chuck Black
2163 John Flick
2164 Jeff Johnson
2165 Leon Leong
2166 Mike Lui
2167 Dave Perkins
2168 Geoff Thompson
2169 Maurice Turcotte
2170 Paul Woodruff
2171
2172 Special thanks as well to Dave Perkins for his excellent work on the
2173 SMICng compiler, which made it easy to take advantage of the latest
2174 SNMPv2 constructs in this MIB.
2175
2176
2177
2178
2179
2180 <span class="grey">de Graaf, et. al. Standards Track [Page 39]</span></pre>
2181 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2182 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
2183
2184
2185 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
2186
2187 [<a id="ref-1">1</a>] IEEE 802.3/ISO 8802-3 Information processing systems -
2188 Local area networks - Part 3: Carrier sense multiple
2189 access with collision detection (CSMA/CD) access method
2190 and physical layer specifications, 1993.
2191
2192 [<a id="ref-2">2</a>] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium
2193 Attachment Units and Repeater for 100 Mb/s Operation,
2194 Type 100BASE-T," Sections <a href="#section-21">21</a> through <a href="#section-29">29</a>, Supplement to
2195 IEEE Std 802.3, October 26, 1995.
2196
2197 [<a id="ref-3">3</a>] IEEE 802.3u-1995, "10 &amp; 100 Mb/s Management," <a href="#section-30">Section 30</a>,
2198 Supplement to IEEE Std 802.3, October 26, 1995.
2199
2200 [<a id="ref-4">4</a>] de Graaf, K., D. Romascanu, D. McMaster and K.
2201 McCloghrie, "Definitions of Managed Objects for IEEE
2202 802.3 Repeater Devices using SMIv2", <a href="./rfc2108">RFC 2108</a>, February
2203 1997.
2204
2205 [<a id="ref-5">5</a>] McCloghrie, K. and M. Rose, Editors, "Management
2206 Information Base for Network Management of TCP/IP-based
2207 internets: MIB-II", STD 17, <a href="./rfc1213">RFC 1213</a>, March 1991.
2208
2209 [<a id="ref-6">6</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2210 "Structure of Management Information for version 2 of the
2211 Simple Network Management Protocol (SNMPv2)", <a href="./rfc1902">RFC 1902</a>,
2212 January 1996.
2213
2214 [<a id="ref-7">7</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
2215 Conventions for version 2 of the Simple Network Management
2216 Protocol (SNMPv2)", <a href="./rfc1903">RFC 1903</a>, January 1996.
2217
2218 [<a id="ref-8">8</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
2219 "Conformance Statements for version 2 of the Simple Network
2220 Management Protocol (SNMPv2)", <a href="./rfc1904">RFC 1904</a>, January 1996.
2221
2222 [<a id="ref-9">9</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
2223 Operations for version 2 of the Simple Network Management
2224 Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
2225
2226 [<a id="ref-10">10</a>] Case, J., M. Fedor, M. Schoffstall and J. Davin, "Simple
2227 Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, May 1990.
2228
2229 [<a id="ref-11">11</a>] McMaster, D., K. McCloghrie and S. Roberts, "Definitions of
2230 Managed Objects for IEEE 802.3 Medium Attachment Units
2231 (MAUs)", <a href="./rfc1515">RFC 1515</a>, September 1993.
2232
2233
2234
2235
2236 <span class="grey">de Graaf, et. al. Standards Track [Page 40]</span></pre>
2237 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2238 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
2239
2240
2241 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
2242
2243 Certain management information defined in this MIB may be considered
2244 sensitive in some network environments. Therefore, authentication of
2245 received SNMP requests and controlled access to management
2246 information should be employed in such environments. The method for
2247 this authentication is a function of the SNMP Administrative
2248 Framework, and has not been expanded by this MIB.
2249
2250 Several objects in this MIB allow write access. Setting these
2251 objects can have a serious effect on the operation of the network,
2252 including enabling or disabling a MAU, changing a MAU's default type,
2253 enabling, disabling or restarting autonegotiation, or modifying the
2254 capabilities that a MAU advertizes during autonegotiation. It is
2255 recommended that implementers seriously consider whether set
2256 operations should be allowed without providing, at a minimum,
2257 authentication of request origin.
2258
2259 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Authors' Addresses</span>
2260
2261 Kathryn de Graaf
2262 3Com Corporation
2263 118 Turnpike Rd.
2264 Southborough, MA 01772 USA
2265
2266 Phone: (508)229-1627
2267 Fax: (508)490-5882
2268 EMail: [email protected]
2269
2270
2271 Dan Romascanu
2272 Madge Networks (Israel) Ltd.
2273 Atidim Technology Park, Bldg. 3
2274 Tel Aviv 61131, Israel
2275
2276 Phone: 972-3-6458414, 6458458
2277 Fax: 972-3-6487146
2278 EMail: [email protected]
2279
2280
2281 Donna McMaster
2282 Cisco Systems Inc.
2283 170 West Tasman Drive
2284 San Jose, CA 95134
2285
2286 Phone:: (408) 526-5260
2287 EMail: [email protected]
2288
2289
2290
2291
2292 <span class="grey">de Graaf, et. al. Standards Track [Page 41]</span></pre>
2293 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2294 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
2295
2296
2297 Keith McCloghrie
2298 Cisco Systems Inc.
2299 170 West Tasman Drive
2300 San Jose, CA 95134
2301
2302 Phone: (408) 526-5260
2303 EMail: [email protected]
2304
2305
2306 Sam Roberts
2307 Farallon Computing, Inc.
2308 2470 Mariner Square Loop
2309 Alameda, CA 94501-1010
2310
2311 Phone:: (510) 814-5215
2312 EMail: [email protected]
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348 <span class="grey">de Graaf, et. al. Standards Track [Page 42]</span></pre>
2349 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2350 <span class="grey"><a href="./rfc2239">RFC 2239</a> Managed Objects for IEEE 802.3 MAUs November 1997</span>
2351
2352
2353 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Full Copyright Statement</span>
2354
2355 Copyright (C) The Internet Society (1997). All Rights Reserved.
2356
2357 This document and translations of it may be copied and furnished to
2358 others, and derivative works that comment on or otherwise explain it
2359 or assist in its implementation may be prepared, copied, published
2360 and distributed, in whole or in part, without restriction of any
2361 kind, provided that the above copyright notice and this paragraph are
2362 included on all such copies and derivative works. However, this
2363 document itself may not be modified in any way, such as by removing
2364 the copyright notice or references to the Internet Society or other
2365 Internet organizations, except as needed for the purpose of
2366 developing Internet standards in which case the procedures for
2367 copyrights defined in the Internet Standards process must be
2368 followed, or as required to translate it into languages other than
2369 English.
2370
2371 The limited permissions granted above are perpetual and will not be
2372 revoked by the Internet Society or its successors or assigns.
2373
2374 This document and the information contained herein is provided on an
2375 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
2376 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
2377 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
2378 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
2379 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404 de Graaf, et. al. Standards Track [Page 43]
2405 </pre>