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