Debian Codegraph @

rfc2666.html

raw
1 <pre>Network Working Group J. Flick
2 Request for Comments: 2666 Hewlett-Packard Company
3 Category: Informational August 1999
4
5
6 <span class="h1">Definitions of Object Identifiers for</span>
7 <span class="h1">Identifying Ethernet Chip Sets</span>
8
9 Status of this Memo
10
11 This memo provides information for the Internet community. It does
12 not specify an Internet standard of any kind. Distribution of this
13 memo is unlimited.
14
15 Copyright Notice
16
17 Copyright (C) The Internet Society (1999). All Rights Reserved.
18
19 Abstract
20
21 This memo defines OBJECT IDENTIFIER values for use with network
22 management protocols in the Internet community. In particular, it
23 contains registered OID values for use with the dot3StatsEtherChipSet
24 object in the EtherLike-MIB [<a href="#ref-16" title="&quot;Definitions of Managed Objects for the Ethernet-like Interface Types&quot;">16</a>]. These registrations have been
25 split from [<a href="#ref-16" title="&quot;Definitions of Managed Objects for the Ethernet-like Interface Types&quot;">16</a>] into a separate document for maintenance purposes.
26
27 Table of Contents
28
29 <a href="#section-1">1</a>. Introduction ............................................... <a href="#page-2">2</a>
30 <a href="#section-2">2</a>. The SNMP Management Framework .............................. <a href="#page-2">2</a>
31 <a href="#section-3">3</a>. Definitions ................................................ <a href="#page-3">3</a>
32 <a href="#section-4">4</a>. Intellectual Property ...................................... <a href="#page-14">14</a>
33 <a href="#section-5">5</a>. Acknowledgements ........................................... <a href="#page-15">15</a>
34 <a href="#section-6">6</a>. References ................................................. <a href="#page-15">15</a>
35 <a href="#section-7">7</a>. Security Considerations .................................... <a href="#page-16">16</a>
36 <a href="#section-8">8</a>. Author's Address ........................................... <a href="#page-17">17</a>
37 <a href="#section-9">9</a>. Full Copyright Statement ................................... <a href="#page-18">18</a>
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Flick Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 This memo defines OBJECT IDENTIFIER values for use with network
60 management protocols in the Internet community. In particular, it
61 contains registered OID values for use with the dot3StatsEtherChipSet
62 object in the EtherLike-MIB [<a href="#ref-16" title="&quot;Definitions of Managed Objects for the Ethernet-like Interface Types&quot;">16</a>]. These registrations have been
63 split from [<a href="#ref-16" title="&quot;Definitions of Managed Objects for the Ethernet-like Interface Types&quot;">16</a>] into a separate document for maintenance purposes.
64
65 The dot3StatsEtherChipSet object has recently been deprecated. The
66 purpose of this document is to capture historic assignments made by
67 the various IETF working groups that have been responsible for
68 maintaining the EtherLike-MIB. Implementations which support the
69 dot3StatsEtherChipSet object for backwards compatability may continue
70 to use the OBJECT IDENTIFIER values assigned in this document.
71
72 For those chipsets not represented in this document, implementors
73 should assign OBJECT IDENTIFIER values within that part of the
74 registration tree delegated to individual enterprises.
75
76 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The SNMP Management Framework</span>
77
78 The SNMP Management Framework presently consists of five major
79 components:
80
81 o An overall architecture, described in <a href="./rfc2571">RFC 2571</a> [<a href="#ref-1" title="&quot;An Architecture for Describing SNMP Management Frameworks&quot;">1</a>].
82
83 o Mechanisms for describing and naming objects and events for the
84 purpose of management. The first version of this Structure of
85 Management Information (SMI) is called SMIv1 and described in STD
86 16, <a href="./rfc1155">RFC 1155</a> [<a href="#ref-2" title="&quot;Structure and Identification of Management Information for TCP/IP-based Internets&quot;">2</a>], STD 16, <a href="./rfc1212">RFC 1212</a> [<a href="#ref-3" title="&quot;Concise MIB Definitions&quot;">3</a>] and <a href="./rfc1215">RFC 1215</a> [<a href="#ref-4" title="&quot;A Convention for Defining Traps for use with the SNMP&quot;">4</a>]. The
87 second version, called SMIv2, is described in STD 58, <a href="./rfc2578">RFC 2578</a>
88 [<a href="#ref-5" title="&quot;Structure of Management Information Version 2 (SMIv2)&quot;">5</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="#ref-6" title="&quot;Textual Conventions for SMIv2&quot;">6</a>] and STD 58, <a href="./rfc2580">RFC 2580</a> [<a href="#ref-7" title="&quot;Conformance Statements for SMIv2&quot;">7</a>].
89
90 o Message protocols for transferring management information. The
91 first version of the SNMP message protocol is called SNMPv1 and
92 described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title="&quot;Simple Network Management Protocol&quot;">8</a>]. A second version of the SNMP
93 message protocol, which is not an Internet standards track
94 protocol, is called SNMPv2c and described in <a href="./rfc1901">RFC 1901</a> [<a href="#ref-9" title="&quot;Introduction to Community-based SNMPv2&quot;">9</a>] and <a href="./rfc1906">RFC</a>
95 <a href="./rfc1906">1906</a> [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>]. The third version of the message protocol is called
96 SNMPv3 and described in <a href="./rfc1906">RFC 1906</a> [<a href="#ref-10" title="&quot;Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">10</a>], <a href="./rfc2572">RFC 2572</a> [<a href="#ref-11" title="&quot;Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)&quot;">11</a>] and <a href="./rfc2574">RFC 2574</a>
97 [<a href="#ref-12" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">12</a>].
98
99 o Protocol operations for accessing management information. The
100 first set of protocol operations and associated PDU formats is
101 described in STD 15, <a href="./rfc1157">RFC 1157</a> [<a href="#ref-8" title="&quot;Simple Network Management Protocol&quot;">8</a>]. A second set of protocol
102 operations and associated PDU formats is described in <a href="./rfc1905">RFC 1905</a>
103 [<a href="#ref-13" title="&quot;Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">13</a>].
104
105
106
107
108 <span class="grey">Flick Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
111
112
113 o A set of fundamental applications described in <a href="./rfc2573">RFC 2573</a> [<a href="#ref-14" title="&quot;SNMPv3 Applications&quot;">14</a>] and
114 the view-based access control mechanism described in <a href="./rfc2575">RFC 2575</a>
115 [<a href="#ref-15" title="&quot;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)&quot;">15</a>].
116
117 Managed objects are accessed via a virtual information store, termed
118 the Management Information Base or MIB. Objects in the MIB are
119 defined using the mechanisms defined in the SMI.
120
121 This memo specifies a MIB module that is compliant to the SMIv2. A
122 MIB conforming to the SMIv1 can be produced through the appropriate
123 translations. The resulting translated MIB must be semantically
124 equivalent, except where objects or events are omitted because no
125 translation is possible (use of Counter64). Some machine readable
126 information in SMIv2 will be converted into textual descriptions in
127 SMIv1 during the translation process. However, this loss of machine
128 readable information is not considered to change the semantics of the
129 MIB.
130
131 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Definitions</span>
132
133 ETHER-CHIPSET-MIB DEFINITIONS ::= BEGIN
134
135 IMPORTS
136 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
137 FROM SNMPv2-SMI
138 dot3
139 FROM EtherLike-MIB;
140
141 etherChipsetMIB MODULE-IDENTITY
142 LAST-UPDATED "9908240400Z" -- August 24, 199
143 ORGANIZATION "IETF 802.3 Hub MIB Working Group"
144 CONTACT-INFO
145 "WG E-mail: [email protected]
146 To subscribe: [email protected]
147
148 Chair: Dan Romascanu
149 Postal: Lucent Technologies
150 Atidum Technology Park, Bldg. 3
151 Tel Aviv 61131
152 Israel
153 Tel: +972 3 645 8414
154 E-mail: [email protected]
155
156 Editor: John Flick
157 Postal: Hewlett-Packard Company
158 8000 Foothills Blvd. M/S 5556
159 Roseville, CA 95747-5556
160 USA
161
162
163
164 <span class="grey">Flick Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
167
168
169 Tel: +1 916 785 4018
170 Fax: +1 916 785 3583
171 E-mail: [email protected]"
172
173 DESCRIPTION "This MIB module contains registered values for
174 use by the dot3StatsEtherChipSet object in
175 the EtherLike-MIB. This object is used to
176 identify the MAC hardware used to communicate
177 on an interface.
178
179 Note that the dot3StatsEtherChipSet object
180 has been deprecated. The primary purpose of
181 this module is to capture historic assignments
182 made by the various IETF working groups that
183 have been responsible for maintaining the
184 EtherLike-MIB. Implementations which support
185 the dot3StatsEtherChipSet object for backwards
186 compatability may continue to use these values.
187 For those chipsets not represented in this
188 module, registration is required in other
189 documentation, e.g., assignment within that
190 part of the registration tree delegated to
191 individual enterprises (see <a href="./rfc1155">RFC 1155</a> and <a href="./rfc1902">RFC</a>
192 <a href="./rfc1902">1902</a>)."
193
194 REVISION "9908240400Z" -- August 24, 1999
195 DESCRIPTION "Initial version of this module created by
196 splitting the chipset registration information
197 out from the EtherLike-MIB.
198 Version published as <a href="./rfc2666">RFC 2666</a>."
199 ::= { mib-2 70 }
200
201 dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
202
203 dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
204
205 dot3ChipSetAMD7990 OBJECT-IDENTITY
206 STATUS current
207 DESCRIPTION "The authoritative identifier for the Advanced
208 Micro Devices Am7990 Local Area Network
209 Controller for Ethernet (LANCE)."
210 ::= { dot3ChipSetAMD 1 }
211
212 dot3ChipSetAMD79900 OBJECT-IDENTITY
213 STATUS current
214 DESCRIPTION "The authoritative identifier for the Advanced
215 Micro Devices Am79900 chip."
216 ::= { dot3ChipSetAMD 2 }
217
218
219
220 <span class="grey">Flick Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
223
224
225 dot3ChipSetAMD79C940 OBJECT-IDENTITY
226 STATUS current
227 DESCRIPTION "The authoritative identifier for the Advanced
228 Micro Devices Am79C940 Media Access Controller
229 for Ethernet (MACE)."
230 ::= { dot3ChipSetAMD 3 }
231
232 dot3ChipSetAMD79C90 OBJECT-IDENTITY
233 STATUS current
234 DESCRIPTION "The authoritative identifier for the Advanced
235 Micro Devices Am79C90 CMOS Local Area Network
236 Controller for Ethernet (C-LANCE)."
237 ::= { dot3ChipSetAMD 4 }
238
239 dot3ChipSetAMD79C960 OBJECT-IDENTITY
240 STATUS current
241 DESCRIPTION "The authoritative identifier for the Advanced
242 Micro Devices Am79C960 PCnet-ISA Single Chip
243 Ethernet Controller for ISA."
244 ::= { dot3ChipSetAMD 5 }
245
246 dot3ChipSetAMD79C961 OBJECT-IDENTITY
247 STATUS current
248 DESCRIPTION "The authoritative identifier for the Advanced
249 Micro Devices Am79C961 PCnet-ISA+ Single Chip
250 Plug &amp; Play Full-Duplex Ethernet Controller
251 for ISA."
252 ::= { dot3ChipSetAMD 6 }
253
254 dot3ChipSetAMD79C961A OBJECT-IDENTITY
255 STATUS current
256 DESCRIPTION "The authoritative identifier for the Advanced
257 Micro Devices Am79C961A PCnet-ISA II Single Chip
258 Plug &amp; Play Full-Duplex Ethernet Controller
259 for ISA."
260 ::= { dot3ChipSetAMD 7 }
261
262 dot3ChipSetAMD79C965 OBJECT-IDENTITY
263 STATUS current
264 DESCRIPTION "The authoritative identifier for the Advanced
265 Micro Devices Am79C965 PCnet-32 Single Chip
266 Ethernet Controller for PCI."
267 ::= { dot3ChipSetAMD 8 }
268
269 dot3ChipSetAMD79C970 OBJECT-IDENTITY
270 STATUS current
271 DESCRIPTION "The authoritative identifier for the Advanced
272 Micro Devices Am79C970 PCnet PCI Single Chip
273
274
275
276 <span class="grey">Flick Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
279
280
281 Ethernet Controller for PCI Local Bus."
282 ::= { dot3ChipSetAMD 9 }
283
284 dot3ChipSetAMD79C970A OBJECT-IDENTITY
285 STATUS current
286 DESCRIPTION "The authoritative identifier for the Advanced
287 Micro Devices AM79C970A PCnet PCI II Single Chip
288 Full-Duplex Ethernet Controller for PCI Local
289 Bus."
290 ::= { dot3ChipSetAMD 10 }
291
292 dot3ChipSetAMD79C971 OBJECT-IDENTITY
293 STATUS current
294 DESCRIPTION "The authoritative identifier for the Advanced
295 Micro Devices Am79C971 PCnet-FAST Single Chip
296 Full-Duplex 10/100 Mbps Ethernet Controller for
297 PCI Local Bus."
298 ::= { dot3ChipSetAMD 11 }
299
300 dot3ChipSetAMD79C972 OBJECT-IDENTITY
301 STATUS current
302 DESCRIPTION "The authoritative identifier for the Advanced
303 Micro Devices Am79C972 PCnet-FAST+ Enhanced
304 10/100 Mbps PCI Ethernet Controller with OnNow
305 Support."
306 ::= { dot3ChipSetAMD 12 }
307
308 dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
309
310 dot3ChipSetIntel82586 OBJECT-IDENTITY
311 STATUS current
312 DESCRIPTION "The authoritative identifier for the Intel
313 82586 IEEE 802.3 Ethernet LAN Coprocessor."
314 ::= { dot3ChipSetIntel 1 }
315
316 dot3ChipSetIntel82596 OBJECT-IDENTITY
317 STATUS current
318 DESCRIPTION "The authoritative identifier for the Intel
319 82596 High-Performance 32-Bit Local Area Network
320 Coprocessor."
321 ::= { dot3ChipSetIntel 2 }
322
323 dot3ChipSetIntel82595 OBJECT-IDENTITY
324 STATUS current
325 DESCRIPTION "The authoritative identifier for the Intel
326 82595 High Integration Ethernet Controller."
327 ::= { dot3ChipSetIntel 3 }
328
329
330
331
332 <span class="grey">Flick Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
335
336
337 dot3ChipSetIntel82557 OBJECT-IDENTITY
338 STATUS current
339 DESCRIPTION "The authoritative identifier for the Intel
340 82557 Fast Ethernet PCI Bus Lan Controller."
341 ::= { dot3ChipSetIntel 4 }
342
343 dot3ChipSetIntel82558 OBJECT-IDENTITY
344 STATUS current
345 DESCRIPTION "The authoritative identifier for the Intel
346 82558 Fast Ethernet PCI Bus LAN Controller with
347 Integrated PHY."
348 ::= { dot3ChipSetIntel 5 }
349
350 dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
351
352 dot3ChipSetSeeq8003 OBJECT-IDENTITY
353 STATUS current
354 DESCRIPTION "The authoritative identifier for the SEEQ
355 8003 chip set."
356 ::= { dot3ChipSetSeeq 1 }
357
358 dot3ChipSetSeeq80C03 OBJECT-IDENTITY
359 STATUS current
360 DESCRIPTION "The authoritative identifier for the SEEQ
361 80C03 Full-Duplex CMOS Ethernet Data Link
362 Controller (MAC)."
363 ::= { dot3ChipSetSeeq 2 }
364
365 dot3ChipSetSeeq84C30 OBJECT-IDENTITY
366 STATUS current
367 DESCRIPTION "The authoritative identifier for the SEEQ
368 4-Port 84C30 Full-Duplex CMOS Ethernet 10
369 MBit/Sec Data Link Controller (MAC)."
370 ::= { dot3ChipSetSeeq 3 }
371
372 dot3ChipSetSeeq8431 OBJECT-IDENTITY
373 STATUS current
374 DESCRIPTION "The authoritative identifier for the SEEQ
375 4-Port 8431 Full-Duplex CMOS Ethernet 10
376 MBit/Sec Data Link Controller (MAC)."
377 ::= { dot3ChipSetSeeq 4 }
378
379 dot3ChipSetSeeq80C300 OBJECT-IDENTITY
380 STATUS current
381 DESCRIPTION "The authoritative identifier for the SEEQ
382 80C300 Full-Duplex CMOS Ethernet 10/100
383 Mbit/Sec Data Link Controller (MAC)."
384 ::= { dot3ChipSetSeeq 5 }
385
386
387
388 <span class="grey">Flick Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
391
392
393 dot3ChipSetSeeq84C300 OBJECT-IDENTITY
394 STATUS current
395 DESCRIPTION "The authoritative identifier for the SEEQ
396 4-Port 84C300 Fast Ethernet Controller (MAC)."
397 ::= { dot3ChipSetSeeq 6 }
398
399 dot3ChipSetSeeq84301 OBJECT-IDENTITY
400 STATUS current
401 DESCRIPTION "The authoritative identifier for the SEEQ
402 4-Port 84301 Fast Ethernet Controller (MAC)."
403 ::= { dot3ChipSetSeeq 7 }
404
405 dot3ChipSetSeeq84302 OBJECT-IDENTITY
406 STATUS current
407 DESCRIPTION "The authoritative identifier for the SEEQ
408 4-Port 84302 Fast Ethernet Controller (MAC)."
409 ::= { dot3ChipSetSeeq 8 }
410
411 dot3ChipSetSeeq8100 OBJECT-IDENTITY
412 STATUS current
413 DESCRIPTION "The authoritative identifier for the SEEQ
414 8100 Gigabit Ethernet Controller (MAC &amp; PCS)."
415 ::= { dot3ChipSetSeeq 9 }
416
417 dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
418
419 dot3ChipSetNational8390 OBJECT-IDENTITY
420 STATUS current
421 DESCRIPTION "The authoritative identifier for the National
422 Semiconductor DP8390 Network Interface
423 Controller."
424 ::= { dot3ChipSetNational 1 }
425
426 dot3ChipSetNationalSonic OBJECT-IDENTITY
427 STATUS current
428 DESCRIPTION "The authoritative identifier for the National
429 Semiconductor DP83932 Systems-Oriented Network
430 Interface Controller (SONIC)."
431 ::= { dot3ChipSetNational 2 }
432
433 dot3ChipSetNational83901 OBJECT-IDENTITY
434 STATUS current
435 DESCRIPTION "The authoritative identifier for the National
436 Semiconductor DP83901 Serial Network Interface
437 Controller (SNIC)."
438 ::= { dot3ChipSetNational 3 }
439
440 dot3ChipSetNational83902 OBJECT-IDENTITY
441
442
443
444 <span class="grey">Flick Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
447
448
449 STATUS current
450 DESCRIPTION "The authoritative identifier for the National
451 Semiconductor DP83902 Serial Network Interface
452 Controller for Twisted Pair (ST-NIC)."
453 ::= { dot3ChipSetNational 4 }
454
455 dot3ChipSetNational83905 OBJECT-IDENTITY
456 STATUS current
457 DESCRIPTION "The authoritative identifier for the National
458 Semiconductor DP83905 AT Local Area Network
459 Twisted-Pair Interface (AT/LANTIC)."
460 ::= { dot3ChipSetNational 5 }
461
462 dot3ChipSetNational83907 OBJECT-IDENTITY
463 STATUS current
464 DESCRIPTION "The authoritative identifier for the National
465 Semiconductor DP83907 AT Twisted-Pair Enhanced
466 Coaxial Network Interface Controller
467 (AT/LANTIC II)."
468 ::= { dot3ChipSetNational 6 }
469
470 dot3ChipSetNational83916 OBJECT-IDENTITY
471 STATUS current
472 DESCRIPTION "The authoritative identifier for the National
473 Semiconductor DP83916 Systems-Oriented Network
474 Interface Controller (SONIC-16)."
475 ::= { dot3ChipSetNational 7 }
476
477 dot3ChipSetNational83934 OBJECT-IDENTITY
478 STATUS current
479 DESCRIPTION "The authoritative identifier for the National
480 Semiconductor DP83934 Systems-Oriented Network
481 Interface Controller with Twisted Pair Interface
482 (SONIC-T)."
483 ::= { dot3ChipSetNational 8 }
484
485 dot3ChipSetNational83936 OBJECT-IDENTITY
486 STATUS current
487 DESCRIPTION "The authoritative identifier for the National
488 Semiconductor DP83936AVUL Full-Duplex Systems-
489 Oriented Network Interface Controller with
490 Twisted Pair Interface (SONIC-T)."
491 ::= { dot3ChipSetNational 9 }
492
493 dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
494
495 dot3ChipSetFujitsu86950 OBJECT-IDENTITY
496 STATUS current
497
498
499
500 <span class="grey">Flick Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
503
504
505 DESCRIPTION "The authoritative identifier for the Fujitsu
506 86950 chip."
507 ::= { dot3ChipSetFujitsu 1 }
508
509 dot3ChipSetFujitsu86960 OBJECT-IDENTITY
510 STATUS current
511 DESCRIPTION "The authoritative identifier for the Fujitsu
512 MB86960 Network Interface Controller with
513 Encoder/Decoder (NICE)."
514 ::= { dot3ChipSetFujitsu 2 }
515
516 dot3ChipSetFujitsu86964 OBJECT-IDENTITY
517 STATUS current
518 DESCRIPTION "The authoritative identifier for the Fujitsu
519 MB86964 Ethernet Controller with 10BASE-T
520 Tranceiver."
521 ::= { dot3ChipSetFujitsu 3 }
522
523 dot3ChipSetFujitsu86965A OBJECT-IDENTITY
524 STATUS current
525 DESCRIPTION "The authoritative identifier for the Fujitsu
526 MB86965A EtherCoupler Single-Chip Ethernet
527 Controller."
528 ::= { dot3ChipSetFujitsu 4 }
529
530 dot3ChipSetFujitsu86965B OBJECT-IDENTITY
531 STATUS current
532 DESCRIPTION "The authoritative identifier for the Fujitsu
533 MB86965B EtherCoupler Single-Chip Ethernet
534 Controller (supports full-duplex)."
535 ::= { dot3ChipSetFujitsu 5 }
536
537 dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
538
539 dot3ChipSetDigitalDC21040 OBJECT-IDENTITY
540 STATUS current
541 DESCRIPTION "The authoritative identifier for the Digital
542 Semiconductor DC21040 chip."
543 ::= { dot3ChipSetDigital 1 }
544
545 dot3ChipSetDigital21041 OBJECT-IDENTITY
546 STATUS current
547 DESCRIPTION "The authoritative identifier for the Digital
548 Semiconductor 21041 PCI Ethernet LAN
549 Controller."
550 ::= { dot3ChipSetDigital 2 }
551
552 dot3ChipSetDigital21140 OBJECT-IDENTITY
553
554
555
556 <span class="grey">Flick Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
559
560
561 STATUS current
562 DESCRIPTION "The authoritative identifier for the Digital
563 Semiconductor 21140 PCI Fast Ethernet LAN
564 Controller."
565 ::= { dot3ChipSetDigital 3 }
566
567 dot3ChipSetDigital21143 OBJECT-IDENTITY
568 STATUS current
569 DESCRIPTION "The authoritative identifier for the Digital
570 Semiconductor 21143 PCI/CardBus 10/100-Mb/s
571 Ethernet LAN Controller."
572 ::= { dot3ChipSetDigital 4 }
573
574 dot3ChipSetDigital21340 OBJECT-IDENTITY
575 STATUS current
576 DESCRIPTION "The authoritative identifier for the Digital
577 Semiconductor 21340 10/100-MB/s managed buffered
578 port switch."
579 ::= { dot3ChipSetDigital 5 }
580
581 dot3ChipSetDigital21440 OBJECT-IDENTITY
582 STATUS current
583 DESCRIPTION "The authoritative identifier for the Digital
584 Semiconductor 21440 Multiport 10/100Mbps
585 Ethernet Controller."
586 ::= { dot3ChipSetDigital 6 }
587
588 dot3ChipSetDigital21540 OBJECT-IDENTITY
589 STATUS current
590 DESCRIPTION "The authoritative identifier for the Digital
591 Semiconductor 21540 PCI/CardBus Ethernet LAN
592 Controller with Modem Interface."
593 ::= { dot3ChipSetDigital 7 }
594
595 dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 }
596
597 dot3ChipSetTIE100 OBJECT-IDENTITY
598 STATUS current
599 DESCRIPTION "The authoritative identifier for the Texas
600 Instruments TNETE100 ThunderLAN PCI Fast
601 Ethernet Controller."
602 ::= { dot3ChipSetTI 1 }
603
604 dot3ChipSetTIE110 OBJECT-IDENTITY
605 STATUS current
606 DESCRIPTION "The authoritative identifier for the Texas
607 Instruments TNETE110 ThunderLAN PCI 10BASE-T
608 Ethernet Adapter."
609
610
611
612 <span class="grey">Flick Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
615
616
617 ::= { dot3ChipSetTI 2 }
618
619 dot3ChipSetTIX3100 OBJECT-IDENTITY
620 STATUS current
621 DESCRIPTION "The authoritative identifier for the Texas
622 Instruments TNETX3100 Desktop ThunderSWITCH
623 8/2."
624 ::= { dot3ChipSetTI 3 }
625
626 dot3ChipSetTIX3150 OBJECT-IDENTITY
627 STATUS current
628 DESCRIPTION "The authoritative identifier for the Texas
629 Instruments TNETX3150 ThunderSWITCH 12/3."
630 ::= { dot3ChipSetTI 4 }
631
632 dot3ChipSetTIX3270 OBJECT-IDENTITY
633 STATUS current
634 DESCRIPTION "The authoritative identifier for the Texas
635 Instruments TNETX3270 ThunderSWITCH 24/3."
636 ::= { dot3ChipSetTI 5 }
637
638 dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 }
639
640 dot3ChipSetToshibaTC35815F OBJECT-IDENTITY
641 STATUS current
642 DESCRIPTION "The authoritative identifier for the Toshiba
643 TC35815F PCI-Based 100/10Mbps Ethernet
644 Controller."
645 ::= { dot3ChipSetToshiba 1 }
646
647 dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
648
649 dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY
650 STATUS current
651 DESCRIPTION "The authoritative identifier for the Lucent
652 Technologies ATT1MX10 (Spinnaker) Quad MAC and
653 Tranceiver for Ethernet Frame Switching."
654 ::= { dot3ChipSetLucent 1 }
655
656 dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY
657 STATUS current
658 DESCRIPTION "The authoritative identifier for the Lucent
659 Technologies LUC3M08 Eight Ethernet MACs for
660 10/100 Mbits/s Frame Switching."
661 ::= { dot3ChipSetLucent 2 }
662
663 dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
664
665
666
667
668 <span class="grey">Flick Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
671
672
673 dot3ChipSetGalileoGT48001 OBJECT-IDENTITY
674 STATUS current
675 DESCRIPTION "The authoritative identifier for the Galileo
676 Technology GT-48001A Switched Ethernet
677 Controller."
678 ::= { dot3ChipSetGalileo 1 }
679
680 dot3ChipSetGalileoGT48002 OBJECT-IDENTITY
681 STATUS current
682 DESCRIPTION "The authoritative identifier for the Galileo
683 Technology GT-48002A Switched Fast Ethernet
684 Controller."
685 ::= { dot3ChipSetGalileo 2 }
686
687 dot3ChipSetGalileoGT48004 OBJECT-IDENTITY
688 STATUS current
689 DESCRIPTION "The authoritative identifier for the Galileo
690 Technology GT-48004A Four Port Fast Ethernet
691 Switch for Multiport 10/100BASE-X Systems."
692 ::= { dot3ChipSetGalileo 3 }
693
694 dot3ChipSetGalileoGT48207 OBJECT-IDENTITY
695 STATUS current
696 DESCRIPTION "The authoritative identifier for the Galileo
697 Technology GT-48207 Low-Cost 10 Port Switched
698 Ethernet Controller for 10+10/100BASE-X."
699 ::= { dot3ChipSetGalileo 4 }
700
701 dot3ChipSetGalileoGT48208 OBJECT-IDENTITY
702 STATUS current
703 DESCRIPTION "The authoritative identifier for the Galileo
704 Technology GT-48208 Advanced 10 Port Switched
705 Ethernet Controller for 10+10/100BASE-X."
706 ::= { dot3ChipSetGalileo 5 }
707
708 dot3ChipSetGalileoGT48212 OBJECT-IDENTITY
709 STATUS current
710 DESCRIPTION "The authoritative identifier for the Galileo
711 Technology GT-48212 Advanced 14 Port Switched
712 Ethernet Controller for 10+10/100BASE-X."
713 ::= { dot3ChipSetGalileo 6 }
714
715 dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 }
716
717 dot3ChipSetJatoJT1001 OBJECT-IDENTITY
718 STATUS current
719 DESCRIPTION "The authoritative identifier for the Jato
720 Technologies JT1001 GigEMAC Server
721
722
723
724 <span class="grey">Flick Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
727
728
729 10/100/1000Mbps Ethernet Controller with PCI
730 interface."
731 ::= { dot3ChipSetJato 1 }
732
733 dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 }
734
735 dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY
736 STATUS current
737 DESCRIPTION "The authoritative identifier for the XaQTI
738 XQ11800FP XMAC II Gigabit Ethernet Media Access
739 Controller."
740 ::= { dot3ChipSetXaQti 1 }
741
742 dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY
743 STATUS current
744 DESCRIPTION "The authoritative identifier for the XaQTI
745 XQ18110FP GigaPower Protocol Accelerator."
746 ::= { dot3ChipSetXaQti 2 }
747
748 END
749
750 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Intellectual Property</span>
751
752 The IETF takes no position regarding the validity or scope of any
753 intellectual property or other rights that might be claimed to
754 pertain to the implementation or use of the technology described in
755 this document or the extent to which any license under such rights
756 might or might not be available; neither does it represent that it
757 has made any effort to identify any such rights. Information on the
758 IETF's procedures with respect to rights in standards-track and
759 standards-related documentation can be found in <a href="https://www.rfc-editor.org/bcp/bcp11">BCP-11</a>. Copies of
760 claims of rights made available for publication and any assurances of
761 licenses to be made available, or the result of an attempt made to
762 obtain a general license or permission for the use of such
763 proprietary rights by implementors or users of this specification can
764 be obtained from the IETF Secretariat.
765
766 The IETF invites any interested party to bring to its attention any
767 copyrights, patents or patent applications, or other proprietary
768 rights which may cover technology that may be required to practice
769 this standard. Please address the information to the IETF Executive
770 Director.
771
772
773
774
775
776
777
778
779
780 <span class="grey">Flick Informational [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
783
784
785 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
786
787 This document was produced by the Ethernet Interfaces and Hub MIB
788 Working Group.
789
790 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
791
792 [<a id="ref-1">1</a>] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
793 Describing SNMP Management Frameworks", <a href="./rfc2571">RFC 2571</a>, May 1999.
794
795 [<a id="ref-2">2</a>] Rose, M. and K. McCloghrie, "Structure and Identification of
796 Management Information for TCP/IP-based Internets", STD 16, <a href="./rfc1155">RFC</a>
797 <a href="./rfc1155">1155</a>, May 1990.
798
799 [<a id="ref-3">3</a>] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
800 <a href="./rfc1212">RFC 1212</a>, March 1991.
801
802 [<a id="ref-4">4</a>] M. Rose, "A Convention for Defining Traps for use with the
803 SNMP", <a href="./rfc1215">RFC 1215</a>, March 1991
804
805 [<a id="ref-5">5</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
806 M. and S Waldbusser, "Structure of Management Information
807 Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, April 1999.
808
809 [<a id="ref-6">6</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
810 M. and S Waldbusser, "Textual Conventions for SMIv2", STD 58,
811 <a href="./rfc2579">RFC 2579</a>, April 1999.
812
813 [<a id="ref-7">7</a>] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
814 M. and S Waldbusser, "Conformance Statements for SMIv2", STD 58,
815 <a href="./rfc2580">RFC 2580</a>, STD 58, April 1999.
816
817 [<a id="ref-8">8</a>] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
818 Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, May 1990.
819
820 [<a id="ref-9">9</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
821 "Introduction to Community-based SNMPv2", <a href="./rfc1901">RFC 1901</a>, January
822 1996.
823
824 [<a id="ref-10">10</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
825 Mappings for Version 2 of the Simple Network Management Protocol
826 (SNMPv2)", <a href="./rfc1906">RFC 1906</a>, January 1996.
827
828 [<a id="ref-11">11</a>] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
829 Processing and Dispatching for the Simple Network Management
830 Protocol (SNMP)", <a href="./rfc2572">RFC 2572</a>, May 1999.
831
832
833
834
835
836 <span class="grey">Flick Informational [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
839
840
841 [<a id="ref-12">12</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
842 for version 3 of the Simple Network Management Protocol
843 (SNMPv3)", <a href="./rfc2574">RFC 2574</a>, May 1999.
844
845 [<a id="ref-13">13</a>] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
846 Operations for Version 2 of the Simple Network Management
847 Protocol (SNMPv2)", <a href="./rfc1905">RFC 1905</a>, January 1996.
848
849 [<a id="ref-14">14</a>] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", <a href="./rfc2573">RFC</a>
850 <a href="./rfc2573">2573</a>, May 1999.
851
852 [<a id="ref-15">15</a>] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
853 Control Model (VACM) for the Simple Network Management Protocol
854 (SNMP)", <a href="./rfc2575">RFC 2575</a>, May 1999.
855
856 [<a id="ref-16">16</a>] Flick, J. and J. Johnson, "Definitions of Managed Objects for
857 the Ethernet-like Interface Types", <a href="./rfc2665">RFC 2665</a>, August 1999.
858
859 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
860
861 There are no management objects actually defined in this MIB module.
862 It merely contains a list of OBJECT IDENTIFIER values for use in
863 other MIB modules. As such, it does not, by itself, have any effect
864 on the security of the Internet.
865
866 The values in this module are expected to be used only for backwards
867 compatability with the deprecated dot3StatsEtherChipSet object in the
868 EtherLike-MIB [<a href="#ref-16" title="&quot;Definitions of Managed Objects for the Ethernet-like Interface Types&quot;">16</a>]. That object may be considered sensitive in some
869 environments, since it would allow an intruder to obtain information
870 about which vendor's equipment is in use on the network.
871
872 Therefore, it may be important in some environments, where the
873 dot3StatsEtherChipSet object is implemented for backwards
874 compatability, to control read access to that object and possibly to
875 even encrypt the values of that object when sending it over the
876 network via SNMP. Not all versions of SNMP provide features for such
877 a secure environment.
878
879 SNMPv1 by itself is such an insecure environment. Even if the
880 network itself is secure (for example by using IPSec), even then,
881 there is no control as to who on the secure network is allowed to
882 access and GET (read) the objects in this MIB.
883
884 It is recommended that the implementors consider the security
885 features as provided by the SNMPv3 framework. Specifically, the use
886 of the User-based Security Model <a href="./rfc2574">RFC 2574</a> [<a href="#ref-12" title="&quot;User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)&quot;">12</a>] and the View-based
887 Access Control Model <a href="./rfc2575">RFC 2575</a> [<a href="#ref-15" title="&quot;View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)&quot;">15</a>] is recommended.
888
889
890
891
892 <span class="grey">Flick Informational [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
895
896
897 It is then a customer/user responsibility to ensure that the SNMP
898 entity giving access to a managed object whose values are defined in
899 this MIB, is properly configured to give access to those objects only
900 to those principals (users) that have legitimate rights to access
901 them.
902
903 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span>
904
905 John Flick
906 Hewlett-Packard Company
907 8000 Foothills Blvd. M/S 5557
908 Roseville, CA 95747-5557
909
910 Phone: +1 916 785 4018
911 EMail: [email protected]
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Flick Informational [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2666">RFC 2666</a> Ethernet Chipset MIB August 1999</span>
951
952
953 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span>
954
955 Copyright (C) The Internet Society (1999). All Rights Reserved.
956
957 This document and translations of it may be copied and furnished to
958 others, and derivative works that comment on or otherwise explain it
959 or assist in its implementation may be prepared, copied, published
960 and distributed, in whole or in part, without restriction of any
961 kind, provided that the above copyright notice and this paragraph are
962 included on all such copies and derivative works. However, this
963 document itself may not be modified in any way, such as by removing
964 the copyright notice or references to the Internet Society or other
965 Internet organizations, except as needed for the purpose of
966 developing Internet standards in which case the procedures for
967 copyrights defined in the Internet Standards process must be
968 followed, or as required to translate it into languages other than
969 English.
970
971 The limited permissions granted above are perpetual and will not be
972 revoked by the Internet Society or its successors or assigns.
973
974 This document and the information contained herein is provided on an
975 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
976 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
977 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
978 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
979 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
980
981 Acknowledgement
982
983 Funding for the RFC Editor function is currently provided by the
984 Internet Society.
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004 Flick Informational [Page 18]
1005 </pre>