455:. It enhances and adds to the SMIv1-specific data types, such as including bit strings, network addresses, and counters. Bit strings are defined only in SMIv2 and comprise zero or more named bits that specify a value. Network addresses represent an address from a particular protocol family. Counters are non-negative integers that increase until they reach a maximum value and then return to zero. In SMIv1, a 32-bit counter size is specified. In SMIv2, 32-bit and 64-bit counters are defined.
565:└── SNMPv2-MIB(.1.3.6.1.2.1) └── system(.1) ├── sysDescr (.1) ├── sysObjectID (.2) ├── sysUpTime (.3) ├── sysName (.5) ├── sysContact (.4) ├── sysLocation (.6) ├── sysServices (.7) ├── sysORLastChange (.8) └── sysORTable (.9) └── sysOREntry (.1) ├── sysORIndex (.1) ├── sysORID (.2) ├── sysORDescr (.3) └── sysORUpTime (.4)
25:
418:
The SNMPv1 SMI defines highly structured tables that are used to group the instances of a tabular object (that is, an object that contains multiple variables). Tables are composed of zero or more rows, which are indexed in a way that allows an SNMP manager to retrieve or alter an entire row with a
245:
The MIB hierarchy can be depicted as a tree with a nameless root, the levels of which are assigned by different organizations. The top-level MIB OIDs belong to different standards organizations, while lower-level object IDs are allocated by associated organizations. This model permits management
375:
are non-negative integers that can increase or decrease between specified minimum and maximum values. Whenever the system property represented by the gauge is outside of that range, the value of the gauge itself will vary no further than the respective maximum or minimum, as specified in
273:
A managed object (sometimes called a MIB object or object) is one of any number of specific characteristics of a managed device. Managed objects are made up of one or more object instances, which are essentially variables. An OID uniquely identifies a managed object in the MIB hierarchy.
221:
for representing, encoding, transmitting, and decoding data. It provides a set of formal rules for describing the structure of objects that are independent of machine-specific encoding techniques and is a precise, formal notation that removes ambiguities.
362:
represent addresses from a particular protocol family. SMIv1 supports only 32-bit (IPv4) addresses. SMIv2 uses Octet
Strings to represent addresses generically, and thus are usable in SMIv1 too. SMIv1 had an explicit IPv4 address
468:
Capability statements are used to indicate the precise level of support that an agent claims with respect to a MIB group. An NMS can adjust its behavior toward agents according to the capabilities statements associated with each
229:
standard, originally defined in 1984 as part of CCITT X.409:1984. ASN.1 moved to its own standard, X.208, in 1988 due to its broader applicability. The substantially revised 1995 version is covered by the X.680 standards series.
408:
represent unsigned integer-valued information, which is useful when values are always non-negative. This data type redefines the integer data type, which has arbitrary precision in ASN.1 but bounded precision in the
458:
SMIv2 also specifies information modules, which specify a group of related definitions. Three types of SMI information modules exist: MIB modules, compliance statements, and capability statements.
148:. While intended to refer to the complete collection of management information available on an entity, it is often used to refer to a particular subset, more correctly referred to as MIB-module.
889:
have agreed to move MIBs relating to IEEE work (for example
Ethernet and bridging) to their respective IEEE workgroup. This is in process and a few items are complete.
402:
represent signed integer-valued information. This data type redefines the integer data type, which has arbitrary precision in ASN.1 but bounded precision in the SMI.
42:
318:(SMIv1) specifies the use of a number of SMI-specific data types, which are divided into two categories: simple data types and application-wide data types.
478:
MIB modules are occasionally updated to add new functionality, remove ambiguities and fix defects. These changes are made in conformance to section 10 of
396:
represent an arbitrary encoding that is used to pass arbitrary information strings that do not conform to the strict data typing used by the SMI.
369:
are non-negative integers that increase until they reach a maximum value and then roll over to zero. SNMPv1 specifies a counter size of 32 bits.
674:
644:
There are 318 RFCs in the first 5000 RFCs from the IETF that contain MIBs. This list is a mere fraction of the MIBs that have been written:
465:
Compliance statements provide a systematic way to describe a group of managed objects that must be implemented for conformance to a standard.
89:
695:
315:
234:
61:
134:
108:
68:
494:. An example of a MIB module that has been updated many times is the important set of objects that was originally defined in
75:
46:
986:
519:
303:
214:
138:
57:
1111:
999:
35:
965:
145:
237:(SMI), is specified for use in SNMP to define sets of related MIB objects; these sets are termed MIB modules.
898:
IEEE 802.1ap-2008 consolidated the IEEE and IETF RFCs related to bridging networks into eight related MIBs.
502:, also known as "MIB-II". This MIB module has since been split up and can be found in MIB modules such as
267:
82:
130:
1011:
255:
175:
251:
247:
167:
869:
853:
836:
817:
803:
789:
775:
761:
747:
733:
719:
705:
687:
666:
652:
555:
539:
531:
523:
511:
503:
495:
487:
479:
448:
440:
377:
199:
191:
179:
156:
1015:
969:
346:
represent object identifiers that are allocated according to the rules specified in ASN.1.
284:
Tabular objects define multiple related object instances that are grouped in MIB tables.
893:
546:"Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)".
218:
1021:
198:, "Management Information Base for Network Management of TCP/IP-based internets", and
166:
The database is hierarchical (tree-structured) and each entry is addressed through an
1105:
1003:
843:
827:
726:— Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)
1073:
975:
996:
873:
857:
840:
821:
807:
793:
779:
765:
751:
737:
723:
709:
691:
670:
656:
559:
543:
535:
527:
515:
507:
499:
491:
483:
452:
444:
381:
270:, as MIBs can be defined for all such area-specific information and operations.
203:
195:
183:
160:
24:
1092:. Load MIB files and issue SNMP requests, available on Windows, OS X and Linux.
1067:
860:
Definitions of
Managed Objects for the Fabric Element in Fibre Channel Standard
151:
Objects in the MIB are defined using a subset of
Abstract Syntax Notation One (
1026:
712:— Management Information Base for Network Management of TCP/IP-based internets
632:
There are a large number of MIBs defined by standards organizations like the
1050:
299:
1056:
1044:
938:
1089:
1083:
1038:
740:— Management Information Base for the Transmission Control Protocol (TCP)
259:
171:
922:
1062:
1059:(as of 2010-05-18, this project is no longer under active development).
295:
294:, which is a scalar object that contains a single object instance, the
962:
137:(SNMP), the term is also used more generically in contexts such as in
903:
187:
530:"Management Information Base for the User Datagram Protocol (UDP)",
390:
represent time since some event, measured in hundredths of a second.
1051:
BlackOwl MIB Browser: A graphical MIB browser for
Windows and Linux
355:
The following application-wide data types exist in the SNMPv1 SMI:
754:— Management Information Base for the User Datagram Protocol (UDP)
263:
226:
155:) called "Structure of Management Information Version 2 (SMIv2)"
152:
16:
Database used for managing the entities in a communication network
1090:
iReasoning MIB Browser: A graphical MIB browser, written in Java
1079:
886:
678:
633:
462:
MIB modules contain definitions of interrelated managed objects.
956:
510:"Management Information Base for the Internet Protocol (IP)",
186:, "Structure and Identification of Management Information for
142:
18:
163:. The software that performs the parsing is a MIB compiler.
876:— Definitions of Managed Objects for APPN/HPR in IP Networks
768:— Management Information Base for the Internet Protocol (IP)
1008:
217:(ASN.1) is a standard and flexible notation that describes
1095:
1070:. It can send SNMP requests and dynamically load MIB data.
959:, a free online MIB repository for thousands of SNMP MIBs.
334:
data type is a signed integer in the range of −2 to 2−1.
326:
Three simple data types are defined in the SNMPv1 SMI:
659:— Defines the Structure of Management Information (SMI)
1074:
JManager: An open-source SNMP manager, written in Java
904:
439:
The second version of the SMI (SMIv2) is described in
1068:
JMibBrowser: A graphical MIB browser, written in Java
1053:
which can extract MIBs from RFCs and display graphs.
129:) is a database used for managing the entities in a
49:. Unsourced material may be challenged and removed.
694:— Structure of Management Information Version 2 (
1082:written in C++. It is built as a front-end for
1045:mbrowse: A graphical SNMP MIB browser for Linux
298:value that indicates the total number of input
281:Scalar objects define a single object instance.
1076:. Capable of importing MIBs, support for IPv6.
1096:tkmib: A graphical MIB browser, using Tk/perl
1063:MBJ: A graphical MIB browser, written in Java
622:SNMPv2-MIB::sysName.0 = STRING: SOME_HOSTNAME
602:SNMPv2-MIB::sysName.0 = STRING: SOME_HOSTNAME
582:SNMPv2-MIB::sysName.0 = STRING: SOME_HOSTNAME
8:
569:To call the value of sysName one would use:
340:are ordered sequences of 0 to 65,535 octets.
1080:qtmib: An open source graphical MIB browser
1039:SnmpB: A graphical open source MIB browser
636:, private enterprises and other entities.
206:, "A Simple Network Management Protocol".
190:based internets", and its two companions,
824:— Alarm Management Information Base (MIB)
109:Learn how and when to remove this message
1057:SMI-Mib Browser: A graphical MIB browser
1022:PEN (Private Enterprise Number) registry
620:.32.13.36-v2c-cpublic.1.3.6.1.2.1.1.5.0
914:
600:.32.13.36-v2c-cpublic.1.3.6.1.2.1.1.5
518:"Management Information Base for the
277:Two types of managed objects exist:
7:
47:adding citations to reliable sources
316:Structure of Management Information
235:Structure of Management Information
310:SNMPv1 and SMI-specific data types
288:An example of a managed object is
135:Simple Network Management Protocol
14:
133:. Most often associated with the
23:
1047:, based upon GTK+ and Net-SNMP.
538:"The Interfaces Group MIB" and
34:needs additional citations for
988:MIB Compilers and Loading MIBs
1:
580:.32.13.36-v2c-cpublicsysName
520:Transmission Control Protocol
58:"Management information base"
233:An adapted subset of ASN.1,
215:Abstract Syntax Notation One
1041:for Windows, OSX and Linux.
351:Application-wide data types
123:management information base
1128:
782:— The Interfaces Group MIB
1098:. Included with Net-SNMP.
957:ByteSphere's MIB Database
673:— Historically used with
314:The first version of the
225:ASN.1 is a joint ISO and
1018:— extensive list of MIBs
796:— Entity MIB (Version 3)
611:
591:
571:
563:
554:Example of MIB for SNMP
146:Network management model
997:ipMonitor's SNMP Center
677:, not to be used with
178:discuss MIBs, notably
1027:PEN request authority
131:communication network
924:Recommendation X.680
850:FIBRE-CHANNEL-FE-MIB
474:Updating MIB modules
302:packets on a router
268:Java reference model
43:improve this article
252:OSI reference model
1112:Network management
1014:2008-12-23 at the
968:2012-06-19 at the
810:— Entity State MIB
486:and section 5 of
414:SNMPv1 MIB tables
406:Unsigned integers
360:Network addresses
322:Simple data types
254:, extending into
168:object identifier
119:
118:
111:
93:
1119:
992:
981:
945:
944:
935:
929:
928:
919:
800:ENTITY-STATE-MIB
623:
619:
615:
603:
599:
595:
583:
579:
575:
430:
426:
422:
292:
114:
107:
103:
100:
94:
92:
51:
27:
19:
1127:
1126:
1122:
1121:
1120:
1118:
1117:
1116:
1102:
1101:
1035:
1016:Wayback Machine
985:
974:
970:Wayback Machine
953:
948:
937:
936:
932:
921:
920:
916:
912:
883:
881:IEEE maintained
642:
640:IETF maintained
630:
625:
624:
621:
617:
613:
605:
604:
601:
597:
593:
585:
584:
581:
577:
573:
567:
566:
552:
476:
437:
428:
424:
420:
416:
353:
324:
312:
290:
243:
219:data structures
212:
115:
104:
98:
95:
52:
50:
40:
28:
17:
12:
11:
5:
1125:
1123:
1115:
1114:
1104:
1103:
1100:
1099:
1093:
1087:
1077:
1071:
1065:
1060:
1054:
1048:
1042:
1034:
1031:
1030:
1029:
1024:
1019:
1006:
1002:2013-01-03 at
994:
983:
972:
963:SimpleWeb MIBs
960:
952:
951:External links
949:
947:
946:
930:
913:
911:
908:
907:
906:
901:
900:
899:
894:Network bridge
882:
879:
878:
877:
863:
862:
861:
847:
846:Management MIB
825:
811:
797:
783:
769:
755:
741:
727:
713:
699:
681:
660:
641:
638:
629:
626:
612:
610:
609:
592:
590:
589:
572:
564:
551:
548:
475:
472:
471:
470:
466:
463:
436:
433:
415:
412:
411:
410:
403:
397:
391:
385:
370:
364:
352:
349:
348:
347:
341:
335:
323:
320:
311:
308:
286:
285:
282:
242:
239:
211:
208:
174:documentation
117:
116:
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
1124:
1113:
1110:
1109:
1107:
1097:
1094:
1091:
1088:
1085:
1081:
1078:
1075:
1072:
1069:
1066:
1064:
1061:
1058:
1055:
1052:
1049:
1046:
1043:
1040:
1037:
1036:
1032:
1028:
1025:
1023:
1020:
1017:
1013:
1010:
1007:
1005:
1004:archive.today
1001:
998:
995:
990:
989:
984:
979:
978:
973:
971:
967:
964:
961:
958:
955:
954:
950:
942:
941:
934:
931:
926:
925:
918:
915:
909:
905:
902:
897:
896:
895:
892:
891:
890:
888:
885:The IETF and
880:
875:
871:
867:
864:
859:
855:
851:
848:
845:
844:Fibre Channel
842:
838:
834:
831:
830:
829:
828:Fibre Channel
826:
823:
819:
815:
812:
809:
805:
801:
798:
795:
791:
787:
784:
781:
777:
773:
770:
767:
763:
759:
756:
753:
749:
745:
742:
739:
735:
731:
728:
725:
721:
717:
714:
711:
707:
703:
700:
697:
693:
689:
685:
682:
680:
676:
672:
668:
664:
661:
658:
654:
650:
647:
646:
645:
639:
637:
635:
627:
607:
606:
587:
586:
570:
562:
561:
557:
549:
547:
545:
541:
537:
533:
529:
525:
521:
517:
513:
509:
505:
501:
497:
493:
489:
485:
481:
473:
467:
464:
461:
460:
459:
456:
454:
450:
446:
442:
434:
432:
413:
407:
404:
401:
398:
395:
392:
389:
386:
383:
379:
374:
371:
368:
365:
361:
358:
357:
356:
350:
345:
342:
339:
338:Octet strings
336:
333:
329:
328:
327:
321:
319:
317:
309:
307:
305:
301:
297:
293:
283:
280:
279:
278:
275:
271:
269:
265:
261:
257:
253:
249:
241:MIB hierarchy
240:
238:
236:
231:
228:
223:
220:
216:
209:
207:
205:
201:
197:
193:
189:
185:
181:
177:
173:
169:
164:
162:
158:
154:
149:
147:
144:
140:
136:
132:
128:
124:
113:
110:
102:
99:February 2009
91:
88:
84:
81:
77:
74:
70:
67:
63:
60: –
59:
55:
54:Find sources:
48:
44:
38:
37:
32:This article
30:
26:
21:
20:
1033:MIB browsers
987:
976:
939:
933:
923:
917:
884:
865:
849:
832:
813:
799:
785:
771:
757:
743:
729:
715:
701:
683:
662:
648:
643:
631:
568:
553:
477:
457:
438:
417:
405:
399:
393:
387:
372:
366:
359:
354:
343:
337:
331:
325:
313:
289:
287:
276:
272:
256:applications
244:
232:
224:
213:
165:
150:
126:
122:
120:
105:
96:
86:
79:
72:
65:
53:
41:Please help
36:verification
33:
833:FC-MGMT-MIB
246:across all
943:, IEEE 802
910:References
866:HPR-IP-MIB
786:ENTITY-MIB
716:SNMPv2-MIB
684:SNMPv2-SMI
649:SNMP - SMI
388:Time ticks
344:Object IDs
266:, and the
69:newspapers
1009:MIB Depot
977:MIB index
814:ALARM-MIB
431:command.
363:datatype.
304:interface
300:AppleTalk
260:databases
1106:Category
1084:Net-SNMP
1012:Archived
1000:Archived
966:Archived
616:snmpwalk
596:snmpwalk
576:snmpwalk
522:(TCP)",
400:Integers
367:Counters
258:such as
172:Internet
991:, Cisco
744:UDP-MIB
730:TCP-MIB
550:Example
425:GetNext
419:single
394:Opaques
332:integer
296:integer
291:atInput
250:of the
170:(OID).
83:scholar
980:, ICIR
872:
856:
839:
820:
806:
792:
778:
772:IF-MIB
764:
758:IP-MIB
750:
736:
722:
708:
702:MIB-II
690:
669:
655:
558:
542:
534:
526:
514:
506:
498:
490:
482:
469:agent.
451:
443:
380:
373:Gauges
248:layers
202:
194:
188:TCP/IP
182:
159:
85:
78:
71:
64:
56:
927:, ITU
663:MIB-I
628:Index
435:SMIv2
427:, or
264:email
227:ITU-T
210:ASN.1
153:ASN.1
90:JSTOR
76:books
940:MIBs
887:IEEE
874:2584
858:2837
841:4044
822:3877
808:4268
794:4133
780:2863
766:4293
752:4113
738:4022
724:3418
710:1213
696:SMIv
692:2578
679:SNMP
675:CMOT
671:1156
657:1155
634:IETF
560:3418
544:3418
536:2863
528:4113
516:4022
508:4293
500:1213
492:2579
484:2578
453:2579
447:and
445:2578
409:SMI.
382:2578
330:The
204:1157
196:1213
184:1155
176:RFCs
161:2578
62:news
870:RFC
854:RFC
837:RFC
818:RFC
804:RFC
790:RFC
776:RFC
762:RFC
748:RFC
734:RFC
720:RFC
706:RFC
688:RFC
667:RFC
653:RFC
556:RFC
540:RFC
532:RFC
524:RFC
512:RFC
504:RFC
496:RFC
488:RFC
480:RFC
449:RFC
441:RFC
429:Set
421:Get
378:RFC
200:RFC
192:RFC
180:RFC
157:RFC
143:ISO
139:OSI
127:MIB
45:by
1108::
868::
852::
835::
816::
802::
788::
774::
760::
746::
732::
718::
704::
698:2)
686::
665::
651::
618:10
614:#
608:or
598:10
594:#
588:or
578:10
574:#
423:,
306:.
262:,
121:A
1086:.
993:.
982:.
384:.
141:/
125:(
112:)
106:(
101:)
97:(
87:·
80:·
73:·
66:·
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
