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