![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to rfc1156.txt CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / rfcs|
Return to rfc1156.txt CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / rfcs |
1.1 root 1:
2:
3:
4:
5:
6:
7: Network Working Group K. McCloghrie
8: Request For Comments: 1156 Hughes LAN Systems
9: Obsoletes: RFC 1066 M. Rose
10: Performance Systems International
11: May 1990
12:
13:
14: Management Information Base for Network Management
15: of TCP/IP-based internets
16:
17: Table of Contents
18:
19: 1. Status of this Memo ................................... 1
20: 2. IAB Policy Statement .................................. 2
21: 3. Introduction .......................................... 2
22: 4. Objects ............................................... 6
23: 4.1 Object Groups ........................................ 6
24: 4.2 Format of Definitions ................................ 7
25: 5. Object Definitions .................................... 8
26: 5.1 The System Group ..................................... 9
27: 5.2 The Interfaces Group ................................. 11
28: 5.2.1 The Interfaces Table ............................... 11
29: 5.3 The Address Translation Group ........................ 23
30: 5.4 The IP Group ......................................... 26
31: 5.4.1 The IP Address Table ............................... 34
32: 5.4.2 The IP Routing Table ............................... 36
33: 5.5 The ICMP Group ....................................... 43
34: 5.6 The TCP Group ........................................ 53
35: 5.7 The UDP Group ........................................ 62
36: 5.8 The EGP Group ........................................ 64
37: 5.8.1 The EGP Neighbor Table ............................. 65
38: 6. Definitions ........................................... 68
39: 7. Acknowledgements ...................................... 89
40: 8. References ............................................ 90
41: 9. Security Considerations................................ 91
42: 10. Authors' Addresses.................................... 91
43:
44: 1. Status of this Memo
45:
46: This RFC is a re-release of RFC 1066, with a changed "Status of this
47: Memo", "IAB Policy Statement", and "Introduction" sections plus a few
48: minor typographical corrections. The technical content of the
49: document is unchanged from RFC 1066.
50:
51: This memo provides the initial version of the Management Information
52: Base (MIB) for use with network management protocols in TCP/IP-based
53: internets in the short-term. In particular, together with its
54: companion memos which describe the structure of management
55:
56:
57:
58: McCloghrie & Rose [Page 1]
59:
60: RFC 1156 MIB May 1990
61:
62:
63: information along with the initial network management protocol, these
64: documents provide a simple, workable architecture and system for
65: managing TCP/IP-based internets and in particular the Internet.
66:
67: This memo specifies a Standard Protocol for the Internet community.
68: TCP/IP implementations in the Internet which are network manageable
69: are expected to adopt and implement this specification.
70:
71: The Internet Activities Board recommends that all IP and TCP
72: implementations be network manageable. This implies implementation
73: of the Internet MIB (RFC-1156) and at least one of the two
74: recommended management protocols SNMP (RFC-1157) or CMOT (RFC-1095).
75: It should be noted that, at this time, SNMP is a full Internet
76: standard and CMOT is a draft standard. See also the Host and Gateway
77: Requirements RFCs for more specific information on the applicability
78: of this standard.
79:
80: Please refer to the latest edition of the "IAB Official Protocol
81: Standards" RFC for current information on the state and status of
82: standard Internet protocols.
83:
84: Distribution of this memo is unlimited.
85:
86: 2. IAB Policy Statement
87:
88: This MIB specification is the first edition of an evolving document
89: defining variables needed for monitoring and control of various
90: components of the Internet. Not all groups of defined variables are
91: mandatory for all Internet components.
92:
93: For example, the EGP group is mandatory for gateways using EGP but
94: not for hosts which should not be running EGP. Similarly, the TCP
95: group is mandatory for hosts running TCP but not for gateways which
96: aren't running it. What IS mandatory, however, is that all variables
97: of a group be supported if any element of the group is supported.
98:
99: It is expected that additional MIB groups and variables will be
100: defined over time to accommodate the monitoring and control needs of
101: new or changing components of the Internet. The responsible working
102: group(s) will continue to refine this specification.
103:
104: 3. Introduction
105:
106: As reported in RFC 1052, IAB Recommendations for the Development of
107: Internet Network Management Standards [1], the Internet Activities
108: Board has directed the Internet Engineering Task Force (IETF) to
109: create two new working groups in the area of network management. One
110: group was charged with the further specification and definition of
111:
112:
113:
114: McCloghrie & Rose [Page 2]
115:
116: RFC 1156 MIB May 1990
117:
118:
119: elements to be included in the Management Information Base. The
120: other was charged with defining the modifications to the Simple
121: Network Management Protocol (SNMP) to accommodate the short-term
122: needs of the network vendor and operator communities. In the long-
123: term, the use of the OSI network management framework was to be
124: examined using the ISO CMIS/CMIP [2,3] framework as a basis. Two
125: documents were produced to define the management information: RFC
126: 1065, which defined the Structure of Management Information (SMI)
127: [4], and RFC 1066, which defined the Management Information Base
128: (MIB) [5]. Both of these documents were designed so as to be
129: compatible with both the SNMP and the OSI network management
130: framework.
131:
132: This strategy was quite successful in the short-term: Internet-based
133: network management technology was fielded, by both the research and
134: commercial communities, within a few months. As a result of this,
135: portions of the Internet community became network manageable in a
136: timely fashion.
137:
138: As reported in RFC 1109, Report of the Second Ad Hoc Network
139: Management Review Group [6], the requirements of the SNMP and the OSI
140: network management frameworks were more different than anticipated.
141: As such, the requirement for compatibility between the SMI/MIB and
142: both frameworks was suspended.
143:
144: The IAB has designated the SNMP, SMI, and the initial Internet MIB to
145: be full "Standard Protocols" with "Recommended" status. By this
146: action, the IAB recommends that all IP and TCP implementations be
147: network manageable and that the implementations that are network
148: manageable are expected to adopt and implement the SMI, MIB, and
149: SNMP.
150:
151: As such, the current network management framework for TCP/IP- based
152: internets consists of: Structure and Identification of Management
153: Information for TCP/IP-based Internets, which describes how managed
154: objects contained in the MIB are defined as set forth in RFC 1155
155: [7]; Management Information Base for Network Management of TCP/IP-
156: based Internets, which describes the managed objects contained in the
157: MIB as set forth in this memo; and, the Simple Network Management
158: Protocol, which defines the protocol used to manage these objects, as
159: set forth in RFC 1157 [8].
160:
161: The IAB also urged the working groups to be "extremely sensitive to
162: the need to keep SNMP simple," and recommends that the MIB working
163: group take as its starting inputs the MIB definitions found in the
164: High-Level Entity Management Systems (HEMS) RFC 1024 [9], the initial
165: SNMP specification [10], and the CMIS/CMIP memos [11,12].
166:
167:
168:
169:
170: McCloghrie & Rose [Page 3]
171:
172: RFC 1156 MIB May 1990
173:
174:
175: Thus, the list of managed objects defined here, has been derived by
176: taking only those elements which are considered essential. Since
177: such elements are essential, there is no need to allow the
178: implementation of individual objects, to be optional. Rather, all
179: compliant implementations will contain all applicable (see below)
180: objects defined in this memo.
181:
182: This approach of taking only the essential objects is NOT
183: restrictive, since the SMI defined in the companion memo provides
184: three extensibility mechanisms: one, the addition of new standard
185: objects through the definitions of new versions of the MIB; two, the
186: addition of widely-available but non-standard objects through the
187: multilateral subtree; and three, the addition of private objects
188: through the enterprises subtree. Such additional objects can not only
189: be used for vendor-specific elements, but also for experimentation as
190: required to further the knowledge of which other objects are
191: essential.
192:
193: The primary criterion for being considered essential was for an
194: object to be contained in all of the above referenced MIB
195: definitions. A few other objects have been included, but only if the
196: MIB working group believed they are truly essential. The detailed
197: list of criteria against which potential inclusions in this (initial)
198: MIB were considered, was:
199:
200: 1) An object needed to be essential for either fault or
201: configuration management.
202:
203: 2) Only weak control objects were permitted (by weak, it
204: is meant that tampering with them can do only limited
205: damage). This criterion reflects the fact that the
206: current management protocols are not sufficiently secure
207: to do more powerful control operations.
208:
209: 3) Evidence of current use and utility was required.
210:
211: 4) An attempt was made to limit the number of objects to
212: about 100 to make it easier for vendors to fully
213: instrument their software.
214:
215: 5) To avoid redundant variables, it was required that no
216: object be included that can be derived from others in the
217: MIB.
218:
219: 6) Implementation specific objects (e.g., for BSD UNIX)
220: were excluded.
221:
222: 7) It was agreed to avoid heavily instrumenting critical
223:
224:
225:
226: McCloghrie & Rose [Page 4]
227:
228: RFC 1156 MIB May 1990
229:
230:
231: sections of code. The general guideline was one counter
232: per critical section per layer.
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: McCloghrie & Rose [Page 5]
283:
284: RFC 1156 MIB May 1990
285:
286:
287: 4. Objects
288:
289: Managed objects are accessed via a virtual information store, termed
290: the Management Information Base or MIB. Objects in the MIB are
291: defined using Abstract Syntax Notation One (ASN.1) [13].
292:
293: The mechanisms used for describing these objects are specified in the
294: companion memo. In particular, each object has a name, a syntax, and
295: an encoding. The name is an object identifier, an administratively
296: assigned name, which specifies an object type. The object type
297: together with an object instance serves to uniquely identify a
298: specific instantiation of the object. For human convenience, we
299: often use a textual string, termed the OBJECT DESCRIPTOR, to also
300: refer to the object type.
301:
302: The syntax of an object type defines the abstract data structure
303: corresponding to that object type. The ASN.1 language is used for
304: this purpose. However, the companion memo purposely restricts the
305: ASN.1 constructs which may be used. These restrictions are
306: explicitly made for simplicity.
307:
308: The encoding of an object type is simply how that object type is
309: represented using the object type's syntax. Implicitly tied to the
310: notion of an object type's syntax and encoding is how the object type
311: is represented when being transmitted on the network. This memo
312: specifies the use of the basic encoding rules of ASN.1 [14].
313:
314: 4.1. Object Groups
315:
316: Since this list of managed objects contains only the essential
317: elements, there is no need to allow individual objects to be
318: optional. Rather, the objects are arranged into the following
319: groups:
320:
321: - System
322: - Interfaces
323: - Address Translation
324: - IP
325: - ICMP
326: - TCP
327: - UDP
328: - EGP
329:
330: There are two reasons for defining these groups: one, to provide a
331: means of assigning object identifiers; two, to provide a method for
332: implementations of managed agents to know which objects they must
333: implement. This method is as follows: if the semantics of a group is
334: applicable to an implementation, then it must implement all objects
335:
336:
337:
338: McCloghrie & Rose [Page 6]
339:
340: RFC 1156 MIB May 1990
341:
342:
343: in that group. For example, an implementation must implement the EGP
344: group if and only if it implements the EGP protocol.
345:
346: 4.2. Format of Definitions
347:
348: The next section contains the specification of all object types
349: contained in the MIB. Following the conventions of the companion
350: memo, the object types are defined using the following fields:
351:
352: OBJECT:
353: -------
354: A textual name, termed the OBJECT DESCRIPTOR, for the
355: object type, along with its corresponding OBJECT
356: IDENTIFIER.
357:
358: Syntax:
359: The abstract syntax for the object type, presented using
360: ASN.1. This must resolve to an instance of the ASN.1
361: type ObjectSyntax defined in the SMI.
362:
363: Definition:
364: A textual description of the semantics of the object
365: type. Implementations should ensure that their
366: interpretation of the object type fulfills this
367: definition since this MIB is intended for use in multi-
368: vendor environments. As such it is vital that object
369: types have consistent meaning across all machines.
370:
371: Access:
372: One of read-only, read-write, write-only, or
373: not-accessible.
374:
375: Status:
376: One of mandatory, optional, or obsolete.
377:
378:
379:
380:
381:
382:
383:
384:
385:
386:
387:
388:
389:
390:
391:
392:
393:
394: McCloghrie & Rose [Page 7]
395:
396: RFC 1156 MIB May 1990
397:
398:
399: 5. Object Definitions
400:
401: RFC1156-MIB
402:
403: DEFINITIONS ::= BEGIN
404:
405: IMPORTS
406: mgmt, OBJECT-TYPE, NetworkAddress, IpAddress,
407: Counter, Gauge, TimeTicks
408: FROM RFC1155-SMI;
409:
410: mib OBJECT IDENTIFIER ::= { mgmt 1 }
411:
412: system OBJECT IDENTIFIER ::= { mib 1 }
413: interfaces OBJECT IDENTIFIER ::= { mib 2 }
414: at OBJECT IDENTIFIER ::= { mib 3 }
415: ip OBJECT IDENTIFIER ::= { mib 4 }
416: icmp OBJECT IDENTIFIER ::= { mib 5 }
417: tcp OBJECT IDENTIFIER ::= { mib 6 }
418: udp OBJECT IDENTIFIER ::= { mib 7 }
419: egp OBJECT IDENTIFIER ::= { mib 8 }
420:
421: END
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: McCloghrie & Rose [Page 8]
451:
452: RFC 1156 MIB May 1990
453:
454:
455: 5.1. The System Group
456:
457: Implementation of the System group is mandatory for all
458: systems.
459:
460: OBJECT:
461: -------
462: sysDescr { system 1 }
463:
464: Syntax:
465: OCTET STRING
466:
467: Definition:
468: A textual description of the entity. This value should
469: include the full name and version identification of the
470: system's hardware type, software operating-system, and
471: networking software. It is mandatory that this only
472: contain printable ASCII characters.
473:
474: Access:
475: read-only.
476:
477: Status:
478: mandatory.
479:
480:
481: OBJECT:
482: -------
483: sysObjectID { system 2 }
484:
485: Syntax:
486: OBJECT IDENTIFIER
487:
488: Definition:
489: The vendor's authoritative identification of the network
490: management subsystem contained in the entity. This value
491: is allocated within the SMI enterprises subtree
492: (1.3.6.1.4.1) and provides an easy and unambiguous means
493: for determining "what kind of box" is being managed. For
494: example, if vendor "Flintstones, Inc." was assigned the
495: subtree 1.3.6.1.4.1.42, it could assign the identifier
496: 1.3.6.1.4.1.42.1.1 to its "Fred Router".
497:
498: Access:
499: read-only.
500:
501: Status:
502: mandatory.
503:
504:
505:
506: McCloghrie & Rose [Page 9]
507:
508: RFC 1156 MIB May 1990
509:
510:
511: OBJECT:
512: -------
513: sysUpTime { system 3 }
514:
515: Syntax:
516: TimeTicks
517:
518: Definition:
519: The time (in hundredths of a second) since the network
520: management portion of the system was last re-initialized.
521:
522: Access:
523: read-only.
524:
525: Status:
526: mandatory.
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: McCloghrie & Rose [Page 10]
563:
564: RFC 1156 MIB May 1990
565:
566:
567: 5.2. The Interfaces Group
568:
569: Implementation of the Interfaces group is mandatory for all
570: systems.
571:
572: OBJECT:
573: -------
574: ifNumber { interfaces 1 }
575:
576: Syntax:
577: INTEGER
578:
579: Definition:
580: The number of network interfaces (regardless of their
581: current state) on which this system can send/receive IP
582: datagrams.
583:
584: Access:
585: read-only.
586:
587: Status:
588: mandatory.
589:
590: 5.2.1. The Interfaces Table
591:
592: OBJECT:
593: -------
594: ifTable { interfaces 2 }
595:
596: Syntax:
597: SEQUENCE OF IfEntry
598:
599: Definition:
600: A list of interface entries. The number of entries is
601: given by the value of ifNumber.
602:
603: Access:
604: read-write.
605:
606: Status:
607: mandatory.
608:
609: OBJECT:
610: -------
611: ifEntry { ifTable 1 }
612:
613: Syntax:
614: IfEntry ::= SEQUENCE {
615:
616:
617:
618: McCloghrie & Rose [Page 11]
619:
620: RFC 1156 MIB May 1990
621:
622:
623: ifIndex
624: INTEGER,
625: ifDescr
626: OCTET STRING,
627: ifType
628: INTEGER,
629: ifMtu
630: INTEGER,
631: ifSpeed
632: Gauge,
633: ifPhysAddress
634: OCTET STRING,
635: ifAdminStatus
636: INTEGER,
637: ifOperStatus
638: INTEGER,
639: ifLastChange
640: TimeTicks,
641: ifInOctets
642: Counter,
643: ifInUcastPkts
644: Counter,
645: ifInNUcastPkts
646: Counter,
647: ifInDiscards
648: Counter,
649: ifInErrors
650: Counter,
651: ifInUnknownProtos
652: Counter,
653: ifOutOctets
654: Counter,
655: ifOutUcastPkts
656: Counter,
657: ifOutNUcastPkts
658: Counter,
659: ifOutDiscards
660: Counter,
661: ifOutErrors
662: Counter,
663: ifOutQLen
664: Gauge
665: }
666:
667: Definition:
668: An interface entry containing objects at the subnetwork
669: layer and below for a particular interface.
670:
671:
672:
673:
674: McCloghrie & Rose [Page 12]
675:
676: RFC 1156 MIB May 1990
677:
678:
679: Access:
680: read-write.
681:
682: Status:
683: mandatory.
684:
685:
686: We now consider the individual components of each interface
687: entry:
688:
689:
690: OBJECT:
691: -------
692: ifIndex { ifEntry 1 }
693:
694: Syntax:
695: INTEGER
696:
697: Definition:
698: A unique value for each interface. Its value ranges
699: between 1 and the value of ifNumber. The value for each
700: interface must remain constant at least from one re-
701: initialization of the entity's network management system
702: to the next re-initialization.
703:
704: Access:
705: read-only.
706:
707: Status:
708: mandatory.
709:
710:
711: OBJECT:
712: -------
713: ifDescr { ifEntry 2 }
714:
715: Syntax:
716: OCTET STRING
717:
718: Definition:
719: A text string containing information about the interface.
720: This string should include the name of the manufacturer,
721: the product name and the version of the hardware
722: interface. The string is intended for presentation to a
723: human; it must not contain anything but printable ASCII
724: characters.
725:
726:
727:
728:
729:
730: McCloghrie & Rose [Page 13]
731:
732: RFC 1156 MIB May 1990
733:
734:
735: Access:
736: read-only.
737:
738: Status:
739: mandatory.
740:
741:
742: OBJECT:
743: -------
744: ifType { ifEntry 3 }
745:
746: Syntax:
747: INTEGER {
748: other(1), -- none of the following
749: regular1822(2),
750: hdh1822(3),
751: ddn-x25(4),
752: rfc877-x25(5),
753: ethernet-csmacd(6),
754: iso88023-csmacd(7),
755: iso88024-tokenBus(8),
756: iso88025-tokenRing(9),
757: iso88026-man(10),
758: starLan(11),
759: proteon-10MBit(12),
760: proteon-80MBit(13),
761: hyperchannel(14),
762: fddi(15),
763: lapb(16),
764: sdlc(17),
765: t1-carrier(18),
766: cept(19), -- european equivalent of T-1
767: basicIsdn(20),
768: primaryIsdn(21),
769: -- proprietary serial
770: propPointToPointSerial(22)
771: }
772:
773: Definition:
774: The type of interface, distinguished according to the
775: physical/link/network protocol(s) immediately "below" IP
776: in the protocol stack.
777:
778: Access:
779: read-only.
780:
781: Status:
782: mandatory.
783:
784:
785:
786: McCloghrie & Rose [Page 14]
787:
788: RFC 1156 MIB May 1990
789:
790:
791: OBJECT:
792: -------
793: ifMtu { ifEntry 4 }
794:
795: Syntax:
796: INTEGER
797:
798: Definition:
799: The size of the largest IP datagram which can be
800: sent/received on the interface, specified in octets.
801:
802: Access:
803: read-only.
804:
805: Status:
806: mandatory.
807:
808:
809: OBJECT:
810: -------
811: ifSpeed { ifEntry 5 }
812:
813: Syntax:
814: Gauge
815:
816: Definition:
817: An estimate of the interface's current bandwidth in bits
818: per second. For interfaces which do not vary in
819: bandwidth or for those where no accurate estimation can
820: be made, this object should contain the nominal
821: bandwidth.
822:
823: Access:
824: read-only.
825:
826: Status:
827: mandatory.
828:
829:
830: OBJECT:
831: -------
832: ifPhysAddress { ifEntry 6 }
833:
834: Syntax:
835: OCTET STRING
836:
837: Definition:
838: The interface's address at the protocol layer immediately
839:
840:
841:
842: McCloghrie & Rose [Page 15]
843:
844: RFC 1156 MIB May 1990
845:
846:
847: "below" IP in the protocol stack. For interfaces which
848: do not have such an address (e.g., a serial line), this
849: object should contain an octet string of zero length.
850:
851: Access:
852: read-only.
853:
854: Status:
855: mandatory.
856:
857:
858: OBJECT:
859: -------
860: ifAdminStatus { ifEntry 7 }
861:
862: Syntax:
863: INTEGER {
864: up(1), -- ready to pass packets
865: down(2),
866: testing(3) -- in some test mode
867: }
868:
869: Definition:
870: The desired state of the interface. The testing(3) state
871: indicates that no operational packets can be passed.
872:
873: Access:
874: read-write.
875:
876: Status:
877: mandatory.
878:
879:
880: OBJECT:
881: -------
882: ifOperStatus { ifEntry 8 }
883:
884: Syntax:
885: INTEGER {
886: up(1), -- ready to pass packets
887: down(2),
888: testing(3) -- in some test mode
889: }
890:
891: Definition:
892: The current operational state of the interface. The
893: testing(3) state indicates that no operational packets
894: can be passed.
895:
896:
897:
898: McCloghrie & Rose [Page 16]
899:
900: RFC 1156 MIB May 1990
901:
902:
903: Access:
904: read-only.
905:
906: Status:
907: mandatory.
908:
909:
910: OBJECT:
911: -------
912: ifLastChange { ifEntry 9 }
913:
914: Syntax:
915: TimeTicks
916:
917: Definition:
918: The value of sysUpTime at the time the interface entered
919: its current operational state. If the current state was
920: entered prior to the last re-initialization of the local
921: network management subsystem, then this object contains a
922: zero value.
923:
924: Access:
925: read-only.
926:
927: Status:
928: mandatory.
929:
930:
931: OBJECT:
932: -------
933: ifInOctets { ifEntry 10 }
934:
935: Syntax:
936: Counter
937:
938: Definition:
939: The total number of octets received on the interface,
940: including framing characters.
941:
942: Access:
943: read-only.
944:
945: Status:
946: mandatory.
947:
948:
949:
950:
951:
952:
953:
954: McCloghrie & Rose [Page 17]
955:
956: RFC 1156 MIB May 1990
957:
958:
959: OBJECT:
960: -------
961: ifInUcastPkts { ifEntry 11 }
962:
963: Syntax:
964: Counter
965:
966: Definition:
967: The number of (subnet) unicast packets delivered to a
968: higher-layer protocol.
969:
970: Access:
971: read-only.
972:
973: Status:
974: mandatory.
975:
976:
977: OBJECT:
978: -------
979: ifInNUcastPkts { ifEntry 12 }
980:
981: Syntax:
982: Counter
983:
984: Definition:
985: The number of non-unicast (i.e., subnet broadcast or
986: subnet multicast) packets delivered to a higher-layer
987: protocol.
988:
989: Access:
990: read-only.
991:
992: Status:
993: mandatory.
994:
995:
996: OBJECT:
997: -------
998: ifInDiscards { ifEntry 13 }
999:
1000: Syntax:
1001: Counter
1002:
1003: Definition:
1004: The number of inbound packets which were chosen to be
1005: discarded even though no errors had been detected to
1006: prevent their being deliverable to a higher-layer
1007:
1008:
1009:
1010: McCloghrie & Rose [Page 18]
1011:
1012: RFC 1156 MIB May 1990
1013:
1014:
1015: protocol. One possible reason for discarding such a
1016: packet could be to free up buffer space.
1017:
1018: Access:
1019: read-only.
1020:
1021: Status:
1022: mandatory.
1023:
1024:
1025: OBJECT:
1026: -------
1027: ifInErrors { ifEntry 14 }
1028:
1029: Syntax:
1030: Counter
1031:
1032: Definition:
1033: The number of inbound packets that contained errors
1034: preventing them from being deliverable to a higher-layer
1035: protocol.
1036:
1037: Access:
1038: read-only.
1039:
1040: Status:
1041: mandatory.
1042:
1043:
1044: OBJECT:
1045: -------
1046: ifInUnknownProtos { ifEntry 15 }
1047:
1048: Syntax:
1049: Counter
1050:
1051: Definition:
1052: The number of packets received via the interface which
1053: were discarded because of an unknown or unsupported
1054: protocol.
1055:
1056: Access:
1057: read-only.
1058:
1059: Status:
1060: mandatory.
1061:
1062:
1063:
1064:
1065:
1066: McCloghrie & Rose [Page 19]
1067:
1068: RFC 1156 MIB May 1990
1069:
1070:
1071: OBJECT:
1072: -------
1073: ifOutOctets { ifEntry 16 }
1074:
1075: Syntax:
1076: Counter
1077:
1078: Definition:
1079: The total number of octets transmitted out of the
1080: interface, including framing characters.
1081:
1082: Access:
1083: read-only.
1084:
1085: Status:
1086: mandatory.
1087:
1088:
1089: OBJECT:
1090: -------
1091: ifOutUcastPkts { ifEntry 17 }
1092:
1093: Syntax:
1094: Counter
1095:
1096: Definition:
1097: The total number of packets that higher-level protocols
1098: requested be transmitted to a subnet-unicast address,
1099: including those that were discarded or not sent.
1100:
1101: Access:
1102: read-only.
1103:
1104: Status:
1105: mandatory.
1106:
1107:
1108: OBJECT:
1109: -------
1110: ifOutNUcastPkts { ifEntry 18 }
1111:
1112: Syntax:
1113: Counter
1114:
1115: Definition:
1116: The total number of packets that higher-level protocols
1117: requested be transmitted to a non-unicast (i.e., a subnet
1118: broadcast or subnet multicast) address, including those
1119:
1120:
1121:
1122: McCloghrie & Rose [Page 20]
1123:
1124: RFC 1156 MIB May 1990
1125:
1126:
1127: that were discarded or not sent.
1128:
1129: Access:
1130: read-only.
1131:
1132: Status:
1133: mandatory.
1134:
1135:
1136: OBJECT:
1137: -------
1138: ifOutDiscards { ifEntry 19 }
1139:
1140: Syntax:
1141: Counter
1142:
1143: Definition:
1144: The number of outbound packets which were chosen to be
1145: discarded even though no errors had been detected to
1146: prevent their being transmitted. One possible reason for
1147: discarding such a packet could be to free up buffer
1148: space.
1149:
1150: Access:
1151: read-only.
1152:
1153: Status:
1154: mandatory.
1155:
1156:
1157: OBJECT:
1158: -------
1159: ifOutErrors { ifEntry 20 }
1160:
1161: Syntax:
1162: Counter
1163:
1164: Definition:
1165: The number of outbound packets that could not be
1166: transmitted because of errors.
1167:
1168: Access:
1169: read-only.
1170:
1171: Status:
1172: mandatory.
1173:
1174:
1175:
1176:
1177:
1178: McCloghrie & Rose [Page 21]
1179:
1180: RFC 1156 MIB May 1990
1181:
1182:
1183: OBJECT:
1184: -------
1185: ifOutQLen { ifEntry 21 }
1186:
1187: Syntax:
1188: Gauge
1189:
1190: Definition:
1191: The length of the output packet queue (in packets).
1192:
1193: Access:
1194: read-only.
1195:
1196: Status:
1197: mandatory.
1198:
1199:
1200:
1201:
1202:
1203:
1204:
1205:
1206:
1207:
1208:
1209:
1210:
1211:
1212:
1213:
1214:
1215:
1216:
1217:
1218:
1219:
1220:
1221:
1222:
1223:
1224:
1225:
1226:
1227:
1228:
1229:
1230:
1231:
1232:
1233:
1234: McCloghrie & Rose [Page 22]
1235:
1236: RFC 1156 MIB May 1990
1237:
1238:
1239: 5.3. The Address Translation Group
1240:
1241: Implementation of the Address Translation group is mandatory
1242: for all systems.
1243:
1244: The Address Translation group contains one table which is the
1245: union across all interfaces of the translation tables for
1246: converting a NetworkAddress (e.g., an IP address) into a
1247: subnetwork-specific address. For lack of a better term, this
1248: document refers to such a subnetwork-specific address as a
1249: "physical" address.
1250:
1251: Examples of such translation tables are: for broadcast media
1252: where ARP is in use, the translation table is equivalent to
1253: the ARP cache; or, on an X.25 network where non-algorithmic
1254: translation to X.121 addresses is required, the translation
1255: table contains the NetworkAddress to X.121 address
1256: equivalences.
1257:
1258: OBJECT:
1259: -------
1260: atTable { at 1 }
1261:
1262: Syntax:
1263: SEQUENCE OF AtEntry
1264:
1265: Definition:
1266: The Address Translation tables contain the NetworkAddress
1267: to "physical" address equivalences. Some interfaces do
1268: not use translation tables for determining address
1269: equivalences (e.g., DDN-X.25 has an algorithmic method);
1270: if all interfaces are of this type, then the Address
1271: Translation table is empty, i.e., has zero entries.
1272:
1273: Access:
1274: read-write.
1275:
1276: Status:
1277: mandatory.
1278:
1279:
1280: OBJECT:
1281: -------
1282: atEntry { atTable 1 }
1283:
1284: Syntax:
1285: AtEntry ::= SEQUENCE {
1286: atIfIndex
1287:
1288:
1289:
1290: McCloghrie & Rose [Page 23]
1291:
1292: RFC 1156 MIB May 1990
1293:
1294:
1295: INTEGER,
1296: atPhysAddress
1297: OCTET STRING,
1298: atNetAddress
1299: NetworkAddress
1300: }
1301:
1302: Definition:
1303: Each entry contains one NetworkAddress to "physical"
1304: address equivalence.
1305:
1306: Access:
1307: read-write.
1308:
1309: Status:
1310: mandatory.
1311:
1312: We now consider the individual components of each Address
1313: Translation table entry:
1314:
1315:
1316: OBJECT:
1317: -------
1318: atIfIndex { atEntry 1 }
1319:
1320: Syntax:
1321: INTEGER
1322:
1323: Definition:
1324: The interface on which this entry's equivalence is
1325: effective. The interface identified by a particular
1326: value of this index is the same interface as identified
1327: by the same value of ifIndex.
1328:
1329: Access:
1330: read-write.
1331:
1332: Status:
1333: mandatory.
1334:
1335:
1336: OBJECT:
1337: -------
1338: atPhysAddress { atEntry 2 }
1339:
1340: Syntax:
1341: OCTET STRING
1342:
1343:
1344:
1345:
1346: McCloghrie & Rose [Page 24]
1347:
1348: RFC 1156 MIB May 1990
1349:
1350:
1351: Definition:
1352: The media-dependent "physical" address.
1353:
1354: Access:
1355: read-write.
1356:
1357: Status:
1358: mandatory.
1359:
1360:
1361: OBJECT:
1362: -------
1363: atNetAddress { atEntry 3 }
1364:
1365: Syntax:
1366: NetworkAddress
1367:
1368: Definition:
1369: The NetworkAddress (e.g., the IP address) corresponding to
1370: the media-dependent "physical" address.
1371:
1372: Access:
1373: read-write.
1374:
1375: Status:
1376: mandatory.
1377:
1378:
1379:
1380:
1381:
1382:
1383:
1384:
1385:
1386:
1387:
1388:
1389:
1390:
1391:
1392:
1393:
1394:
1395:
1396:
1397:
1398:
1399:
1400:
1401:
1402: McCloghrie & Rose [Page 25]
1403:
1404: RFC 1156 MIB May 1990
1405:
1406:
1407: 5.4. The IP Group
1408:
1409: Implementation of the IP group is mandatory for all systems.
1410:
1411:
1412: OBJECT:
1413: -------
1414: ipForwarding { ip 1 }
1415:
1416: Syntax:
1417: INTEGER {
1418: gateway(1), -- entity forwards datagrams
1419: host(2) -- entity does NOT forward datagrams
1420: }
1421:
1422: Definition:
1423: The indication of whether this entity is acting as an IP
1424: gateway in respect to the forwarding of datagrams
1425: received by, but not addressed to, this entity. IP
1426: gateways forward datagrams; Hosts do not (except those
1427: Source-Routed via the host).
1428:
1429: Access:
1430: read-only.
1431:
1432: Status:
1433: mandatory.
1434:
1435:
1436: OBJECT:
1437: -------
1438: ipDefaultTTL { ip 2 }
1439:
1440: Syntax:
1441: INTEGER
1442:
1443: Definition:
1444: The default value inserted into the Time-To-Live field of
1445: the IP header of datagrams originated at this entity,
1446: whenever a TTL value is not supplied by the transport
1447: layer protocol.
1448:
1449: Access:
1450: read-write.
1451:
1452: Status:
1453: mandatory.
1454:
1455:
1456:
1457:
1458: McCloghrie & Rose [Page 26]
1459:
1460: RFC 1156 MIB May 1990
1461:
1462:
1463: OBJECT:
1464: -------
1465: ipInReceives { ip 3 }
1466:
1467: Syntax:
1468: Counter
1469:
1470: Definition:
1471: The total number of input datagrams received from
1472: interfaces, including those received in error.
1473:
1474: Access:
1475: read-only.
1476:
1477: Status:
1478: mandatory.
1479:
1480:
1481: OBJECT:
1482: -------
1483: ipInHdrErrors { ip 4 }
1484:
1485: Syntax:
1486: Counter
1487:
1488: Definition:
1489: The number of input datagrams discarded due to errors in
1490: their IP headers, including bad checksums, version number
1491: mismatch, other format errors, time-to-live exceeded,
1492: errors discovered in processing their IP options, etc.
1493:
1494: Access:
1495: read-only.
1496:
1497: Status:
1498: mandatory.
1499:
1500:
1501: OBJECT:
1502: -------
1503: ipInAddrErrors { ip 5 }
1504:
1505: Syntax:
1506: Counter
1507:
1508: Definition:
1509: The number of input datagrams discarded because the IP
1510: address in their IP header's destination field was not a
1511:
1512:
1513:
1514: McCloghrie & Rose [Page 27]
1515:
1516: RFC 1156 MIB May 1990
1517:
1518:
1519: valid address to be received at this entity. This count
1520: includes invalid addresses (e.g., 0.0.0.0) and addresses
1521: of unsupported Classes (e.g., Class E). For entities
1522: which are not IP Gateways and therefore do not forward
1523: datagrams, this counter includes datagrams discarded
1524: because the destination address was not a local address.
1525:
1526: Access:
1527: read-only.
1528:
1529: Status:
1530: mandatory.
1531:
1532:
1533: OBJECT:
1534: -------
1535: ipForwDatagrams { ip 6 }
1536:
1537: Syntax:
1538: Counter
1539:
1540: Definition:
1541: The number of input datagrams for which this entity was
1542: not their final IP destination, as a result of which an
1543: attempt was made to find a route to forward them to that
1544: final destination. In entities which do not act as IP
1545: Gateways, this counter will include only those packets
1546: which were Source-Routed via this entity, and the
1547: Source-Route option processing was successful.
1548:
1549: Access:
1550: read-only.
1551:
1552: Status:
1553: mandatory.
1554:
1555:
1556: OBJECT:
1557: -------
1558: ipInUnknownProtos { ip 7 }
1559:
1560: Syntax:
1561: Counter
1562:
1563: Definition:
1564: The number of locally-addressed datagrams received
1565: successfully but discarded because of an unknown or
1566: unsupported protocol.
1567:
1568:
1569:
1570: McCloghrie & Rose [Page 28]
1571:
1572: RFC 1156 MIB May 1990
1573:
1574:
1575: Access:
1576: read-only.
1577:
1578: Status:
1579: mandatory.
1580:
1581:
1582: OBJECT:
1583: -------
1584: ipInDiscards { ip 8 }
1585:
1586: Syntax:
1587: Counter
1588:
1589: Definition:
1590: The number of input IP datagrams for which no problems
1591: were encountered to prevent their continued processing,
1592: but which were discarded (e.g. for lack of buffer space).
1593: Note that this counter does not include any datagrams
1594: discarded while awaiting re-assembly.
1595:
1596: Access:
1597: read-only.
1598:
1599: Status:
1600: mandatory.
1601:
1602:
1603: OBJECT:
1604: -------
1605: ipInDelivers { ip 9 }
1606:
1607: Syntax:
1608: Counter
1609:
1610: Definition:
1611: The total number of input datagrams successfully
1612: delivered to IP user-protocols (including ICMP).
1613:
1614: Access:
1615: read-only.
1616:
1617: Status:
1618: mandatory.
1619:
1620: OBJECT:
1621: -------
1622: ipOutRequests { ip 10 }
1623:
1624:
1625:
1626: McCloghrie & Rose [Page 29]
1627:
1628: RFC 1156 MIB May 1990
1629:
1630:
1631: Syntax:
1632: Counter
1633:
1634: Definition:
1635: The total number of IP datagrams which local IP user-
1636: protocols (including ICMP) supplied to IP in requests for
1637: transmission. Note that this counter does not include
1638: any datagrams counted in ipForwDatagrams.
1639:
1640: Access:
1641: read-only.
1642:
1643: Status:
1644: mandatory.
1645:
1646:
1647: OBJECT:
1648: -------
1649: ipOutDiscards { ip 11 }
1650:
1651: Syntax:
1652: Counter
1653:
1654: Definition:
1655: The number of output IP datagrams for which no problem
1656: was encountered to prevent their transmission to their
1657: destination, but which were discarded (e.g., for lack of
1658: buffer space). Note that this counter would include
1659: datagrams counted in ipForwDatagrams if any such packets
1660: met this (discretionary) discard criterion.
1661:
1662: Access:
1663: read-only.
1664:
1665: Status:
1666: mandatory.
1667:
1668:
1669: OBJECT:
1670: -------
1671: ipOutNoRoutes { ip 12 }
1672:
1673: Syntax:
1674: Counter
1675:
1676:
1677:
1678:
1679:
1680:
1681:
1682: McCloghrie & Rose [Page 30]
1683:
1684: RFC 1156 MIB May 1990
1685:
1686:
1687: Definition:
1688: The number of IP datagrams discarded because no route
1689: could be found to transmit them to their destination.
1690: Note that this counter includes any packets counted in
1691: ipForwDatagrams which meet this "no-route" criterion.
1692:
1693: Access:
1694: read-only.
1695:
1696: Status:
1697: mandatory.
1698:
1699:
1700: OBJECT:
1701: -------
1702: ipReasmTimeout { ip 13 }
1703:
1704: Syntax:
1705: INTEGER
1706:
1707: Definition:
1708: The maximum number of seconds which received fragments
1709: are held while they are awaiting reassembly at this
1710: entity.
1711:
1712: Access:
1713: read-only.
1714:
1715: Status:
1716: mandatory.
1717:
1718:
1719: OBJECT:
1720: -------
1721: ipReasmReqds { ip 14 }
1722:
1723: Syntax:
1724: Counter
1725:
1726: Definition:
1727: The number of IP fragments received which needed to be
1728: reassembled at this entity.
1729:
1730: Access:
1731: read-only.
1732:
1733: Status:
1734: mandatory.
1735:
1736:
1737:
1738: McCloghrie & Rose [Page 31]
1739:
1740: RFC 1156 MIB May 1990
1741:
1742:
1743: OBJECT:
1744: -------
1745: ipReasmOKs { ip 15 }
1746:
1747: Syntax:
1748: Counter
1749:
1750: Definition:
1751: The number of IP datagrams successfully re-assembled.
1752:
1753: Access:
1754: read-only.
1755:
1756: Status:
1757: mandatory.
1758:
1759:
1760: OBJECT:
1761: -------
1762: ipReasmFails { ip 16 }
1763:
1764: Syntax:
1765: Counter
1766:
1767: Definition:
1768: The number of failures detected by the IP re-assembly
1769: algorithm (for whatever reason: timed out, errors, etc).
1770:
1771: Note that this is not necessarily a count of discarded IP
1772: fragments since some algorithms (notably RFC 815's) can
1773: lose track of the number of fragments by combining them
1774: as they are received.
1775:
1776: Access:
1777: read-only.
1778:
1779: Status:
1780: mandatory.
1781:
1782:
1783: OBJECT:
1784: -------
1785: ipFragOKs { ip 17 }
1786:
1787: Syntax:
1788: Counter
1789:
1790:
1791:
1792:
1793:
1794: McCloghrie & Rose [Page 32]
1795:
1796: RFC 1156 MIB May 1990
1797:
1798:
1799: Definition:
1800: The number of IP datagrams that have been successfully
1801: fragmented at this entity.
1802:
1803: Access:
1804: read-only.
1805:
1806: Status:
1807: mandatory.
1808:
1809:
1810: OBJECT:
1811: -------
1812: ipFragFails { ip 18 }
1813:
1814: Syntax:
1815: Counter
1816:
1817: Definition:
1818: The number of IP datagrams that have been discarded
1819: because they needed to be fragmented at this entity but
1820: could not be, e.g., because their "Don't Fragment" flag
1821: was set.
1822:
1823: Access:
1824: read-only.
1825:
1826: Status:
1827: mandatory.
1828:
1829:
1830: OBJECT:
1831: -------
1832: ipFragCreates { ip 19 }
1833:
1834: Syntax:
1835: Counter
1836:
1837: Definition:
1838: The number of IP datagram fragments that have been
1839: generated as a result of fragmentation at this entity.
1840:
1841: Access:
1842: read-only.
1843:
1844: Status:
1845: mandatory.
1846:
1847:
1848:
1849:
1850: McCloghrie & Rose [Page 33]
1851:
1852: RFC 1156 MIB May 1990
1853:
1854:
1855: 5.4.1. The IP Address Table
1856:
1857: The Ip Address table contains this entity's IP addressing
1858: information.
1859:
1860:
1861: OBJECT:
1862: -------
1863: ipAddrTable { ip 20 }
1864:
1865: Syntax:
1866: SEQUENCE OF IpAddrEntry
1867:
1868: Definition:
1869: The table of addressing information relevant to this
1870: entity's IP addresses.
1871:
1872: Access:
1873: read-only.
1874:
1875: Status:
1876: mandatory.
1877:
1878:
1879: OBJECT:
1880: -------
1881: ipAddrEntry { ipAddrTable 1 }
1882:
1883: Syntax:
1884: IpAddrEntry ::= SEQUENCE {
1885: ipAdEntAddr
1886: IpAddress,
1887: ipAdEntIfIndex
1888: INTEGER,
1889: ipAdEntNetMask
1890: IpAddress,
1891: ipAdEntBcastAddr
1892: INTEGER
1893: }
1894:
1895: Definition:
1896: The addressing information for one of this entity's IP
1897: addresses.
1898:
1899: Access:
1900: read-only.
1901:
1902:
1903:
1904:
1905:
1906: McCloghrie & Rose [Page 34]
1907:
1908: RFC 1156 MIB May 1990
1909:
1910:
1911: Status:
1912: mandatory.
1913:
1914:
1915: OBJECT:
1916: -------
1917: ipAdEntAddr { ipAddrEntry 1 }
1918:
1919: Syntax:
1920: IpAddress
1921:
1922: Definition:
1923: The IP address to which this entry's addressing
1924: information pertains.
1925:
1926: Access:
1927: read-only.
1928:
1929: Status:
1930: mandatory.
1931:
1932:
1933: OBJECT:
1934: -------
1935: ipAdEntIfIndex { ipAddrEntry 2 }
1936:
1937: Syntax:
1938: INTEGER
1939:
1940: Definition:
1941: The index value which uniquely identifies the interface
1942: to which this entry is applicable. The interface
1943: identified by a particular value of this index is the
1944: same interface as identified by the same value of
1945: ifIndex.
1946:
1947: Access:
1948: read-only.
1949:
1950: Status:
1951: mandatory.
1952:
1953:
1954: OBJECT:
1955: -------
1956: ipAdEntNetMask { ipAddrEntry 3 }
1957:
1958:
1959:
1960:
1961:
1962: McCloghrie & Rose [Page 35]
1963:
1964: RFC 1156 MIB May 1990
1965:
1966:
1967: Syntax:
1968: IpAddress
1969:
1970: Definition:
1971: The subnet mask associated with the IP address of this
1972: entry. The value of the mask is an IP address with all
1973: the network bits set to 1 and all the hosts bits set to
1974: 0.
1975:
1976: Access:
1977: read-only.
1978:
1979: Status:
1980: mandatory.
1981:
1982:
1983: OBJECT:
1984: -------
1985: ipAdEntBcastAddr { ipAddrEntry 4 }
1986:
1987: Syntax:
1988: INTEGER
1989:
1990: Definition:
1991: The value of the least-significant bit in the IP
1992: broadcast address used for sending datagrams on the
1993: (logical) interface associated with the IP address of
1994: this entry. For example, when the Internet standard
1995: all-ones broadcast address is used, the value will be 1.
1996:
1997: Access:
1998: read-only.
1999:
2000: Status:
2001: mandatory.
2002:
2003: 5.4.2. The IP Routing Table
2004:
2005: The IP Routing Table contains an entry for each route
2006: presently known to this entity. Note that the action to be
2007: taken in response to a request to read a non-existent entry,
2008: is specific to the network management protocol being used.
2009:
2010:
2011: OBJECT:
2012: -------
2013: ipRoutingTable { ip 21 }
2014:
2015:
2016:
2017:
2018: McCloghrie & Rose [Page 36]
2019:
2020: RFC 1156 MIB May 1990
2021:
2022:
2023: Syntax:
2024: SEQUENCE OF IpRouteEntry
2025:
2026: Definition:
2027: This entity's IP Routing table.
2028:
2029: Access:
2030: read-write.
2031:
2032: Status:
2033: mandatory.
2034:
2035:
2036: OBJECT:
2037: -------
2038: ipRouteEntry { ipRoutingTable 1 }
2039:
2040: Syntax:
2041: IpRouteEntry ::= SEQUENCE {
2042: ipRouteDest
2043: IpAddress,
2044: ipRouteIfIndex
2045: INTEGER,
2046: ipRouteMetric1
2047: INTEGER,
2048: ipRouteMetric2
2049: INTEGER,
2050: ipRouteMetric3
2051: INTEGER,
2052: ipRouteMetric4
2053: INTEGER,
2054: ipRouteNextHop
2055: IpAddress,
2056: ipRouteType
2057: INTEGER,
2058: ipRouteProto
2059: INTEGER,
2060: ipRouteAge
2061: INTEGER
2062: }
2063:
2064: Definition:
2065: A route to a particular destination.
2066:
2067: Access:
2068: read-write.
2069:
2070:
2071:
2072:
2073:
2074: McCloghrie & Rose [Page 37]
2075:
2076: RFC 1156 MIB May 1990
2077:
2078:
2079: Status:
2080: mandatory.
2081:
2082: We now consider the individual components of each route in the
2083: IP Routing Table:
2084:
2085:
2086: OBJECT:
2087: -------
2088: ipRouteDest { ipRouteEntry 1 }
2089:
2090: Syntax:
2091: IpAddress
2092:
2093: Definition:
2094: The destination IP address of this route. An entry with
2095: a value of 0.0.0.0 is considered a default route.
2096: Multiple such default routes can appear in the table, but
2097: access to such multiple entries is dependent on the
2098: table-access mechanisms defined by the network management
2099: protocol in use.
2100:
2101: Access:
2102: read-write.
2103:
2104: Status:
2105: mandatory.
2106:
2107:
2108: OBJECT:
2109: -------
2110: ipRouteIfIndex { ipRouteEntry 2 }
2111:
2112: Syntax:
2113: INTEGER
2114:
2115: Definition:
2116: The index value which uniquely identifies the local
2117: interface through which the next hop of this route should
2118: be reached. The interface identified by a particular
2119: value of this index is the same interface as identified
2120: by the same value of ifIndex.
2121:
2122: Access:
2123: read-write.
2124:
2125: Status:
2126: mandatory.
2127:
2128:
2129:
2130: McCloghrie & Rose [Page 38]
2131:
2132: RFC 1156 MIB May 1990
2133:
2134:
2135: OBJECT:
2136: -------
2137: ipRouteMetric1 { ipRouteEntry 3 }
2138:
2139: Syntax:
2140: INTEGER
2141:
2142: Definition:
2143: The primary routing metric for this route. The semantics
2144: of this metric are determined by the routing-protocol
2145: specified in the route's ipRouteProto value. If this
2146: metric is not used, its value should be set to -1.
2147:
2148: Access:
2149: read-write.
2150:
2151: Status:
2152: mandatory.
2153:
2154:
2155: OBJECT:
2156: -------
2157: ipRouteMetric2 { ipRouteEntry 4 }
2158:
2159: Syntax:
2160: INTEGER
2161:
2162: Definition:
2163: An alternate routing metric for this route. The
2164: semantics of this metric are determined by the routing-
2165: protocol specified in the route's ipRouteProto value. If
2166: this metric is not used, its value should be set to -1.
2167:
2168: Access:
2169: read-write.
2170:
2171: Status:
2172: mandatory.
2173:
2174:
2175: OBJECT:
2176: -------
2177: ipRouteMetric3 { ipRouteEntry 5 }
2178:
2179: Syntax:
2180: INTEGER
2181:
2182:
2183:
2184:
2185:
2186: McCloghrie & Rose [Page 39]
2187:
2188: RFC 1156 MIB May 1990
2189:
2190:
2191: Definition:
2192: An alternate routing metric for this route. The
2193: semantics of this metric are determined by the routing-
2194: protocol specified in the route's ipRouteProto value. If
2195: this metric is not used, its value should be set to -1.
2196:
2197: Access:
2198: read-write.
2199:
2200: Status:
2201: mandatory.
2202:
2203:
2204: OBJECT:
2205: -------
2206: ipRouteMetric4 { ipRouteEntry 6 }
2207:
2208: Syntax:
2209: INTEGER
2210:
2211: Definition:
2212: An alternate routing metric for this route. The
2213: semantics of this metric are determined by the routing-
2214: protocol specified in the route's ipRouteProto value. If
2215: this metric is not used, its value should be set to -1.
2216:
2217: Access:
2218: read-write.
2219:
2220: Status:
2221: mandatory.
2222:
2223:
2224: OBJECT:
2225: -------
2226: ipRouteNextHop { ipRouteEntry 7 }
2227:
2228: Syntax:
2229: IpAddress
2230:
2231: Definition:
2232: The IP address of the next hop of this route.
2233:
2234: Access:
2235: read-write.
2236:
2237: Status:
2238: mandatory.
2239:
2240:
2241:
2242: McCloghrie & Rose [Page 40]
2243:
2244: RFC 1156 MIB May 1990
2245:
2246:
2247: OBJECT:
2248: -------
2249: ipRouteType { ipRouteEntry 8 }
2250:
2251: Syntax:
2252: INTEGER {
2253: other(1), -- none of the following
2254:
2255: invalid(2), -- an invalidated route
2256:
2257: -- route to directly
2258: direct(3), -- connected (sub-)network
2259:
2260: -- route to a non-local
2261: remote(4), -- host/network/sub-network
2262: }
2263:
2264: Definition:
2265: The type of route.
2266:
2267: Access:
2268: read-write.
2269:
2270: Status:
2271: mandatory.
2272:
2273:
2274: OBJECT:
2275: -------
2276: ipRouteProto { ipRouteEntry 9 }
2277:
2278: Syntax:
2279: INTEGER {
2280: other(1), -- none of the following
2281:
2282: -- non-protocol information,
2283: -- e.g., manually configured
2284: local(2), -- entries
2285:
2286: -- set via a network management
2287: netmgmt(3), -- protocol
2288:
2289: -- obtained via ICMP,
2290: icmp(4), -- e.g., Redirect
2291:
2292: -- the remaining values are
2293: -- all gateway routing protocols
2294: egp(5),
2295:
2296:
2297:
2298: McCloghrie & Rose [Page 41]
2299:
2300: RFC 1156 MIB May 1990
2301:
2302:
2303: ggp(6),
2304: hello(7),
2305: rip(8),
2306: is-is(9),
2307: es-is(10),
2308: ciscoIgrp(11),
2309: bbnSpfIgp(12),
2310: oigp(13)
2311: }
2312:
2313: Definition:
2314: The routing mechanism via which this route was learned.
2315: Inclusion of values for gateway routing protocols is not
2316: intended to imply that hosts should support those
2317: protocols.
2318:
2319: Access:
2320: read-only.
2321:
2322: Status:
2323: mandatory.
2324:
2325:
2326: OBJECT:
2327: -------
2328: ipRouteAge { ipRouteEntry 10 }
2329:
2330: Syntax:
2331: INTEGER
2332:
2333: Definition:
2334: The number of seconds since this route was last updated
2335: or otherwise determined to be correct. Note that no
2336: semantics of "too old" can be implied except through
2337: knowledge of the routing protocol by which the route was
2338: learned.
2339:
2340: Access:
2341: read-write.
2342:
2343: Status:
2344: mandatory.
2345:
2346:
2347:
2348:
2349:
2350:
2351:
2352:
2353:
2354: McCloghrie & Rose [Page 42]
2355:
2356: RFC 1156 MIB May 1990
2357:
2358:
2359: 5.5. The ICMP Group
2360:
2361: Implementation of the ICMP group is mandatory for all systems.
2362:
2363: The ICMP group contains the ICMP input and output statistics.
2364:
2365: Note that individual counters for ICMP message (sub-)codes have been
2366: omitted from this (version of the) MIB for simplicity.
2367:
2368:
2369: OBJECT:
2370: -------
2371: icmpInMsgs { icmp 1 }
2372:
2373: Syntax:
2374: Counter
2375:
2376: Definition:
2377: The total number of ICMP messages which the entity
2378: received. Note that this counter includes all those
2379: counted by icmpInErrors.
2380:
2381: Access:
2382: read-only.
2383:
2384: Status:
2385: mandatory.
2386:
2387:
2388: OBJECT:
2389: -------
2390: icmpInErrors { icmp 2 }
2391:
2392: Syntax:
2393: Counter
2394:
2395: Definition:
2396: The number of ICMP messages which the entity received but
2397: determined as having errors (bad ICMP checksums, bad
2398: length, etc.).
2399:
2400: Access:
2401: read-only.
2402:
2403: Status:
2404: mandatory.
2405:
2406:
2407:
2408:
2409:
2410: McCloghrie & Rose [Page 43]
2411:
2412: RFC 1156 MIB May 1990
2413:
2414:
2415: OBJECT:
2416: -------
2417: icmpInDestUnreachs { icmp 3 }
2418:
2419: Syntax:
2420: Counter
2421:
2422: Definition:
2423: The number of ICMP Destination Unreachable messages
2424: received.
2425:
2426: Access:
2427: read-only.
2428:
2429: Status:
2430: mandatory.
2431:
2432:
2433: OBJECT:
2434: -------
2435: icmpInTimeExcds { icmp 4 }
2436:
2437: Syntax:
2438: Counter
2439:
2440: Definition:
2441: The number of ICMP Time Exceeded messages received.
2442:
2443: Access:
2444: read-only.
2445:
2446: Status:
2447: mandatory.
2448:
2449:
2450: OBJECT:
2451: -------
2452: icmpInParmProbs { icmp 5 }
2453:
2454: Syntax:
2455: Counter
2456:
2457: Definition:
2458: The number of ICMP Parameter Problem messages received.
2459:
2460: Access:
2461: read-only.
2462:
2463:
2464:
2465:
2466: McCloghrie & Rose [Page 44]
2467:
2468: RFC 1156 MIB May 1990
2469:
2470:
2471: Status:
2472: mandatory.
2473:
2474:
2475: OBJECT:
2476: -------
2477: icmpInSrcQuenchs { icmp 6 }
2478:
2479: Syntax:
2480: Counter
2481:
2482: Definition:
2483: The number of ICMP Source Quench messages received.
2484:
2485: Access:
2486: read-only.
2487:
2488: Status:
2489: mandatory.
2490:
2491:
2492: OBJECT:
2493: -------
2494: icmpInRedirects { icmp 7 }
2495:
2496: Syntax:
2497: Counter
2498:
2499: Definition:
2500: The number of ICMP Redirect messages received.
2501:
2502: Access:
2503: read-only.
2504:
2505: Status:
2506: mandatory.
2507:
2508:
2509: OBJECT:
2510: -------
2511: icmpInEchos { icmp 8 }
2512:
2513: Syntax:
2514: Counter
2515:
2516: Definition:
2517: The number of ICMP Echo (request) messages received.
2518:
2519:
2520:
2521:
2522: McCloghrie & Rose [Page 45]
2523:
2524: RFC 1156 MIB May 1990
2525:
2526:
2527: Access:
2528: read-only.
2529:
2530: Status:
2531: mandatory.
2532:
2533:
2534: OBJECT:
2535: -------
2536: icmpInEchoReps { icmp 9 }
2537:
2538: Syntax:
2539: Counter
2540:
2541: Definition:
2542: The number of ICMP Echo Reply messages received.
2543:
2544: Access:
2545: read-only.
2546:
2547: Status:
2548: mandatory.
2549:
2550:
2551: OBJECT:
2552: -------
2553: icmpInTimestamps { icmp 10 }
2554:
2555: Syntax:
2556: Counter
2557:
2558: Definition:
2559: The number of ICMP Timestamp (request) messages received.
2560:
2561: Access:
2562: read-only.
2563:
2564: Status:
2565: mandatory.
2566:
2567:
2568: OBJECT:
2569: -------
2570: icmpInTimestampReps { icmp 11 }
2571:
2572: Syntax:
2573: Counter
2574:
2575:
2576:
2577:
2578: McCloghrie & Rose [Page 46]
2579:
2580: RFC 1156 MIB May 1990
2581:
2582:
2583: Definition:
2584: The number of ICMP Timestamp Reply messages received.
2585:
2586: Access:
2587: read-only.
2588:
2589: Status:
2590: mandatory.
2591:
2592:
2593: OBJECT:
2594: -------
2595: icmpInAddrMasks { icmp 12 }
2596:
2597: Syntax:
2598: Counter
2599:
2600: Definition:
2601: The number of ICMP Address Mask Request messages
2602: received.
2603:
2604: Access:
2605: read-only.
2606:
2607: Status:
2608: mandatory.
2609:
2610:
2611: OBJECT:
2612: -------
2613: icmpInAddrMaskReps { icmp 13 }
2614:
2615: Syntax:
2616: Counter
2617:
2618: Definition:
2619: The number of ICMP Address Mask Reply messages received.
2620:
2621: Access:
2622: read-only.
2623:
2624: Status:
2625: mandatory.
2626:
2627:
2628: OBJECT:
2629: -------
2630: icmpOutMsgs { icmp 14 }
2631:
2632:
2633:
2634: McCloghrie & Rose [Page 47]
2635:
2636: RFC 1156 MIB May 1990
2637:
2638:
2639: Syntax:
2640: Counter
2641:
2642: Definition:
2643: The total number of ICMP messages which this entity
2644: attempted to send. Note that this counter includes all
2645: those counted by icmpOutErrors.
2646:
2647: Access:
2648: read-only.
2649:
2650: Status:
2651: mandatory.
2652:
2653:
2654: OBJECT:
2655: -------
2656: icmpOutErrors { icmp 15 }
2657:
2658: Syntax:
2659: Counter
2660:
2661: Definition:
2662: The number of ICMP messages which this entity did not
2663: send due to problems discovered within ICMP such as a
2664: lack of buffers. This value should not include errors
2665: discovered outside the ICMP layer such as the inability
2666: of IP to route the resultant datagram. In some
2667: implementations there may be no types of error which
2668: contribute to this counter's value.
2669:
2670: Access:
2671: read-only.
2672:
2673: Status:
2674: mandatory.
2675:
2676:
2677: OBJECT:
2678: -------
2679: icmpOutDestUnreachs { icmp 16 }
2680:
2681: Syntax:
2682: Counter
2683:
2684: Definition:
2685: The number of ICMP Destination Unreachable messages sent.
2686:
2687:
2688:
2689:
2690: McCloghrie & Rose [Page 48]
2691:
2692: RFC 1156 MIB May 1990
2693:
2694:
2695: Access:
2696: read-only.
2697:
2698: Status:
2699: mandatory.
2700:
2701:
2702: OBJECT:
2703: -------
2704: icmpOutTimeExcds { icmp 17 }
2705:
2706: Syntax:
2707: Counter
2708:
2709: Definition:
2710: The number of ICMP Time Exceeded messages sent.
2711:
2712: Access:
2713: read-only.
2714:
2715: Status:
2716: mandatory.
2717:
2718:
2719: OBJECT:
2720: -------
2721: icmpOutParmProbs { icmp 18 }
2722:
2723: Syntax:
2724: Counter
2725:
2726: Definition:
2727: The number of ICMP Parameter Problem messages sent.
2728:
2729: Access:
2730: read-only.
2731:
2732: Status:
2733: mandatory.
2734:
2735:
2736: OBJECT:
2737: -------
2738: icmpOutSrcQuenchs { icmp 19 }
2739:
2740: Syntax:
2741: Counter
2742:
2743:
2744:
2745:
2746: McCloghrie & Rose [Page 49]
2747:
2748: RFC 1156 MIB May 1990
2749:
2750:
2751: Definition:
2752: The number of ICMP Source Quench messages sent.
2753:
2754: Access:
2755: read-only.
2756:
2757: Status:
2758: mandatory.
2759:
2760:
2761: OBJECT:
2762: -------
2763: icmpOutRedirects { icmp 20 }
2764:
2765: Syntax:
2766: Counter
2767:
2768: Definition:
2769: The number of ICMP Redirect messages sent.
2770:
2771: Access:
2772: read-only.
2773:
2774: Status:
2775: mandatory.
2776:
2777:
2778: OBJECT:
2779: -------
2780: icmpOutEchos { icmp 21 }
2781:
2782: Syntax:
2783: Counter
2784:
2785: Definition:
2786: The number of ICMP Echo (request) messages sent.
2787:
2788: Access:
2789: read-only.
2790:
2791: Status:
2792: mandatory.
2793:
2794:
2795: OBJECT:
2796: -------
2797: icmpOutEchoReps { icmp 22 }
2798:
2799:
2800:
2801:
2802: McCloghrie & Rose [Page 50]
2803:
2804: RFC 1156 MIB May 1990
2805:
2806:
2807: Syntax:
2808: Counter
2809:
2810: Definition:
2811: The number of ICMP Echo Reply messages sent.
2812:
2813: Access:
2814: read-only.
2815:
2816: Status:
2817: mandatory.
2818:
2819:
2820: OBJECT:
2821: -------
2822: icmpOutTimestamps { icmp 23 }
2823:
2824: Syntax:
2825: Counter
2826:
2827: Definition:
2828: The number of ICMP Timestamp (request) messages sent.
2829:
2830: Access:
2831: read-only.
2832:
2833: Status:
2834: mandatory.
2835:
2836:
2837: OBJECT:
2838: -------
2839: icmpOutTimestampReps { icmp 24 }
2840:
2841: Syntax:
2842: Counter
2843:
2844: Definition:
2845: The number of ICMP Timestamp Reply messages sent.
2846:
2847: Access:
2848: read-only.
2849:
2850: Status:
2851: mandatory.
2852:
2853:
2854:
2855:
2856:
2857:
2858: McCloghrie & Rose [Page 51]
2859:
2860: RFC 1156 MIB May 1990
2861:
2862:
2863: OBJECT:
2864: -------
2865: icmpOutAddrMasks { icmp 25 }
2866:
2867: Syntax:
2868: Counter
2869:
2870: Definition:
2871: The number of ICMP Address Mask Request messages sent.
2872:
2873: Access:
2874: read-only.
2875:
2876: Status:
2877: mandatory.
2878:
2879:
2880: OBJECT:
2881: -------
2882: icmpOutAddrMaskReps { icmp 26 }
2883:
2884: Syntax:
2885: Counter
2886:
2887: Definition:
2888: The number of ICMP Address Mask Reply messages sent.
2889:
2890: Access:
2891: read-only.
2892:
2893: Status:
2894: mandatory.
2895:
2896:
2897:
2898:
2899:
2900:
2901:
2902:
2903:
2904:
2905:
2906:
2907:
2908:
2909:
2910:
2911:
2912:
2913:
2914: McCloghrie & Rose [Page 52]
2915:
2916: RFC 1156 MIB May 1990
2917:
2918:
2919: 5.6. The TCP Group
2920:
2921: Implementation of the TCP group is mandatory for all systems
2922: that implement the TCP protocol.
2923:
2924: Note that instances of object types that represent information
2925: about a particular TCP connection are transient; they persist
2926: only as long as the connection in question.
2927:
2928: OBJECT:
2929: -------
2930: tcpRtoAlgorithm { tcp 1 }
2931:
2932: Syntax:
2933: INTEGER {
2934: other(1), -- none of the following
2935: constant(2), -- a constant rto
2936: rsre(3), -- MIL-STD-1778, Appendix B
2937: vanj(4) -- Van Jacobson's algorithm [15]
2938: }
2939:
2940: Definition:
2941: The algorithm used to determine the timeout value used
2942: for retransmitting unacknowledged octets.
2943:
2944: Access:
2945: read-only.
2946:
2947: Status:
2948: mandatory.
2949:
2950:
2951: OBJECT:
2952: -------
2953: tcpRtoMin { tcp 2 }
2954:
2955: Syntax:
2956: INTEGER
2957:
2958: Definition:
2959: The minimum value permitted by a TCP implementation
2960: for the retransmission timeout, measured in
2961: milliseconds. More refined semantics for objects
2962: of this type depend upon the algorithm used to
2963: determine the retransmission timeout. In particular,
2964: when the timeout algorithm is rsre(3), an object
2965: of this type has the semantics of the LBOUND
2966: quantity described in RFC 793.
2967:
2968:
2969:
2970: McCloghrie & Rose [Page 53]
2971:
2972: RFC 1156 MIB May 1990
2973:
2974:
2975: Access:
2976: read-only.
2977:
2978: Status:
2979: mandatory.
2980:
2981:
2982: OBJECT:
2983: -------
2984: tcpRtoMax { tcp 3 }
2985:
2986: Syntax:
2987: INTEGER
2988:
2989: Definition:
2990: The maximum value permitted by a TCP implementation
2991: for the retransmission timeout, measured
2992: in milliseconds. More refined semantics for objects
2993: of this type depend upon the algorithm used to
2994: determine the retransmission timeout. In particular,
2995: when the timeout algorithm is rsre(3), an object of
2996: this type has the semantics of the UBOUND quantity
2997: described in RFC 793.
2998:
2999: Access:
3000: read-only.
3001:
3002: Status:
3003: mandatory.
3004:
3005:
3006: OBJECT:
3007: -------
3008: tcpMaxConn { tcp 4 }
3009:
3010: Syntax:
3011: INTEGER
3012:
3013: Definition:
3014: The limit on the total number of TCP connections the
3015: entity can support. In entities where the maximum
3016: number of connections is dynamic, this object should
3017: contain the value "-1".
3018:
3019: Access:
3020: read-only.
3021:
3022:
3023:
3024:
3025:
3026: McCloghrie & Rose [Page 54]
3027:
3028: RFC 1156 MIB May 1990
3029:
3030:
3031: Status:
3032: mandatory.
3033:
3034:
3035: OBJECT:
3036: -------
3037: tcpActiveOpens { tcp 5 }
3038:
3039: Syntax:
3040: Counter
3041:
3042: Definition:
3043: The number of times TCP connections have made a direct
3044: transition to the SYN-SENT state from the CLOSED
3045: state.
3046:
3047: Access:
3048: read-only.
3049:
3050: Status:
3051: mandatory.
3052:
3053:
3054: OBJECT:
3055: -------
3056: tcpPassiveOpens { tcp 6 }
3057:
3058: Syntax:
3059: Counter
3060:
3061: Definition:
3062: The number of times TCP connections have made a direct
3063: transition to the SYN-RCVD state from the LISTEN
3064: state.
3065:
3066: Access:
3067: read-only.
3068:
3069: Status:
3070: mandatory.
3071:
3072:
3073: OBJECT:
3074: -------
3075: tcpAttemptFails { tcp 7 }
3076:
3077: Syntax:
3078: Counter
3079:
3080:
3081:
3082: McCloghrie & Rose [Page 55]
3083:
3084: RFC 1156 MIB May 1990
3085:
3086:
3087: Definition:
3088: The number of times TCP connections have made a direct
3089: transition to the CLOSED state from either the
3090: SYN-SENT state or the SYN-RCVD state, plus the number
3091: of times TCP connections have made a direct transition
3092: to the LISTEN state from the SYN-RCVD state.
3093:
3094: Access:
3095: read-only.
3096:
3097: Status:
3098: mandatory.
3099:
3100:
3101: OBJECT:
3102: -------
3103: tcpEstabResets { tcp 8 }
3104:
3105: Syntax:
3106: Counter
3107:
3108: Definition:
3109: The number of times TCP connections have made a direct
3110: transition to the CLOSED state from either the
3111: ESTABLISHED state or the CLOSE-WAIT state.
3112:
3113: Access:
3114: read-only.
3115:
3116: Status:
3117: mandatory.
3118:
3119:
3120: OBJECT:
3121: -------
3122: tcpCurrEstab { tcp 9 }
3123:
3124: Syntax:
3125: Gauge
3126:
3127: Definition:
3128: The number of TCP connections for which the current
3129: state is either ESTABLISHED or CLOSE-WAIT.
3130:
3131: Access:
3132: read-only.
3133:
3134:
3135:
3136:
3137:
3138: McCloghrie & Rose [Page 56]
3139:
3140: RFC 1156 MIB May 1990
3141:
3142:
3143: Status:
3144: mandatory.
3145:
3146:
3147: OBJECT:
3148: -------
3149: tcpInSegs { tcp 10 }
3150:
3151: Syntax:
3152: Counter
3153:
3154: Definition:
3155: The total number of segments received, including those
3156: received in error. This count includes segments
3157: received on currently established connections.
3158:
3159: Access:
3160: read-only.
3161:
3162: Status:
3163: mandatory.
3164:
3165:
3166: OBJECT:
3167: -------
3168: tcpOutSegs { tcp 11 }
3169:
3170: Syntax:
3171: Counter
3172:
3173: Definition:
3174: The total number of segments sent, including those on
3175: current connections but excluding those containing
3176: only retransmitted octets.
3177:
3178: Access:
3179: read-only.
3180:
3181: Status:
3182: mandatory.
3183:
3184:
3185: OBJECT:
3186: -------
3187: tcpRetransSegs { tcp 12 }
3188:
3189: Syntax:
3190: Counter
3191:
3192:
3193:
3194: McCloghrie & Rose [Page 57]
3195:
3196: RFC 1156 MIB May 1990
3197:
3198:
3199: Definition:
3200: The total number of segments retransmitted - that is,
3201: the number of TCP segments transmitted containing one
3202: or more previously transmitted octets.
3203:
3204: Access:
3205: read-only.
3206:
3207: Status:
3208: mandatory.
3209:
3210:
3211: OBJECT:
3212: -------
3213: tcpConnTable { tcp 13 }
3214:
3215: Syntax:
3216: SEQUENCE OF TcpConnEntry
3217:
3218: Definition:
3219: A table containing TCP connection-specific
3220: information.
3221:
3222: Access:
3223: read-only.
3224:
3225: Status:
3226: mandatory.
3227:
3228:
3229: OBJECT:
3230: -------
3231: tcpConnEntry { tcpConnTable 1 }
3232:
3233: Syntax:
3234: TcpConnEntry ::= SEQUENCE {
3235: tcpConnState
3236: INTEGER,
3237: tcpConnLocalAddress
3238: IpAddress,
3239: tcpConnLocalPort
3240: INTEGER (0..65535),
3241: tcpConnRemAddress
3242: IpAddress,
3243: tcpConnRemPort
3244: INTEGER (0..65535)
3245: }
3246:
3247:
3248:
3249:
3250: McCloghrie & Rose [Page 58]
3251:
3252: RFC 1156 MIB May 1990
3253:
3254:
3255: Definition:
3256: Information about a particular current TCP connection.
3257: An object of this type is transient, in that it ceases
3258: to exist when (or soon after) the connection makes the
3259: transition to the CLOSED state.
3260:
3261: Access:
3262: read-only.
3263:
3264: Status:
3265: mandatory.
3266:
3267:
3268: OBJECT:
3269: -------
3270: tcpConnState { tcpConnEntry 1 }
3271:
3272: Syntax:
3273: INTEGER {
3274: closed(1),
3275: listen(2),
3276: synSent(3),
3277: synReceived(4),
3278: established(5),
3279: finWait1(6),
3280: finWait2(7),
3281: closeWait(8),
3282: lastAck(9),
3283: closing(10),
3284: timeWait(11)
3285: }
3286:
3287: Definition:
3288: The state of this TCP connection.
3289:
3290: Access:
3291: read-only.
3292:
3293: Status:
3294: mandatory.
3295:
3296:
3297: OBJECT:
3298: -------
3299: tcpConnLocalAddress { tcpConnEntry 2 }
3300:
3301: Syntax:
3302: IpAddress
3303:
3304:
3305:
3306: McCloghrie & Rose [Page 59]
3307:
3308: RFC 1156 MIB May 1990
3309:
3310:
3311: Definition:
3312: The local IP address for this TCP connection.
3313:
3314: Access:
3315: read-only.
3316:
3317: Status:
3318: mandatory.
3319:
3320:
3321: OBJECT:
3322: -------
3323: tcpConnLocalPort { tcpConnEntry 3 }
3324:
3325: Syntax:
3326: INTEGER (0..65535)
3327:
3328: Definition:
3329: The local port number for this TCP connection.
3330:
3331: Access:
3332: read-only.
3333:
3334: Status:
3335: mandatory.
3336:
3337:
3338: OBJECT:
3339: -------
3340: tcpConnRemAddress { tcpConnEntry 4 }
3341:
3342: Syntax:
3343: IpAddress
3344:
3345: Definition:
3346: The remote IP address for this TCP connection.
3347:
3348: Access:
3349: read-only.
3350:
3351: Status:
3352: mandatory.
3353:
3354:
3355: OBJECT:
3356: -------
3357: tcpConnRemPort { tcpConnEntry 5 }
3358:
3359:
3360:
3361:
3362: McCloghrie & Rose [Page 60]
3363:
3364: RFC 1156 MIB May 1990
3365:
3366:
3367: Syntax:
3368: INTEGER (0..65535)
3369:
3370: Definition:
3371: The remote port number for this TCP connection.
3372:
3373: Access:
3374: read-only.
3375:
3376: Status:
3377: mandatory.
3378:
3379:
3380:
3381:
3382:
3383:
3384:
3385:
3386:
3387:
3388:
3389:
3390:
3391:
3392:
3393:
3394:
3395:
3396:
3397:
3398:
3399:
3400:
3401:
3402:
3403:
3404:
3405:
3406:
3407:
3408:
3409:
3410:
3411:
3412:
3413:
3414:
3415:
3416:
3417:
3418: McCloghrie & Rose [Page 61]
3419:
3420: RFC 1156 MIB May 1990
3421:
3422:
3423: 5.7. The UDP Group
3424:
3425: Implementation of the UDP group is mandatory for all systems
3426: which implement the UDP protocol.
3427:
3428: OBJECT:
3429: -------
3430: udpInDatagrams { udp 1 }
3431:
3432: Syntax:
3433: Counter
3434:
3435: Definition:
3436: The total number of UDP datagrams delivered to UDP
3437: users.
3438:
3439: Access:
3440: read-only.
3441:
3442: Status:
3443: mandatory.
3444:
3445:
3446: OBJECT:
3447: -------
3448: udpNoPorts { udp 2 }
3449:
3450: Syntax:
3451: Counter
3452:
3453: Definition:
3454: The total number of received UDP datagrams for which
3455: there was no application at the destination port.
3456:
3457: Access:
3458: read-only.
3459:
3460: Status:
3461: mandatory.
3462:
3463:
3464: OBJECT:
3465: -------
3466: udpInErrors { udp 3 }
3467:
3468: Syntax:
3469: Counter
3470:
3471:
3472:
3473:
3474: McCloghrie & Rose [Page 62]
3475:
3476: RFC 1156 MIB May 1990
3477:
3478:
3479: Definition:
3480: The number of received UDP datagrams that could not be
3481: delivered for reasons other than the lack of an
3482: application at the destination port.
3483:
3484: Access:
3485: read-only.
3486:
3487: Status:
3488: mandatory.
3489:
3490:
3491: OBJECT:
3492: -------
3493: udpOutDatagrams { udp 4 }
3494:
3495: Syntax:
3496: Counter
3497:
3498: Definition:
3499: The total number of UDP datagrams sent from this
3500: entity.
3501:
3502: Access:
3503: read-only.
3504:
3505: Status:
3506: mandatory.
3507:
3508:
3509:
3510:
3511:
3512:
3513:
3514:
3515:
3516:
3517:
3518:
3519:
3520:
3521:
3522:
3523:
3524:
3525:
3526:
3527:
3528:
3529:
3530: McCloghrie & Rose [Page 63]
3531:
3532: RFC 1156 MIB May 1990
3533:
3534:
3535: 5.8. The EGP Group
3536:
3537: Implementation of the EGP group is mandatory for all systems
3538: which implement the EGP protocol.
3539:
3540: OBJECT:
3541: -------
3542: egpInMsgs { egp 1 }
3543:
3544: Syntax:
3545: Counter
3546:
3547: Definition:
3548: The number of EGP messages received without error.
3549:
3550: Access:
3551: read-only.
3552:
3553: Status:
3554: mandatory.
3555:
3556:
3557: OBJECT:
3558: -------
3559: egpInErrors { egp 2 }
3560:
3561: Syntax:
3562: Counter
3563:
3564: Definition:
3565: The number of EGP messages received that proved to be
3566: in error.
3567:
3568: Access:
3569: read-only.
3570:
3571: Status:
3572: mandatory.
3573:
3574:
3575: OBJECT:
3576: -------
3577: egpOutMsgs { egp 3 }
3578:
3579: Syntax:
3580: Counter
3581:
3582:
3583:
3584:
3585:
3586: McCloghrie & Rose [Page 64]
3587:
3588: RFC 1156 MIB May 1990
3589:
3590:
3591: Definition:
3592: The total number of locally generated EGP messages.
3593:
3594: Access:
3595: read-only.
3596:
3597: Status:
3598: mandatory.
3599:
3600:
3601: OBJECT:
3602: -------
3603: egpOutErrors { egp 4 }
3604:
3605: Syntax:
3606: Counter
3607:
3608: Definition:
3609: The number of locally generated EGP messages not sent
3610: due to resource limitations within an EGP entity.
3611:
3612: Access:
3613: read-only.
3614:
3615: Status:
3616: mandatory.
3617:
3618: 5.8.1. The EGP Neighbor Table
3619:
3620: The Egp Neighbor table contains information about this entity's EGP
3621: neighbors.
3622:
3623:
3624: OBJECT:
3625: -------
3626: egpNeighTable { egp 5 }
3627:
3628: Syntax:
3629: SEQUENCE OF EgpNeighEntry
3630:
3631: Definition:
3632: The EGP neighbor table.
3633:
3634: Access:
3635: read-only.
3636:
3637: Status:
3638: mandatory.
3639:
3640:
3641:
3642: McCloghrie & Rose [Page 65]
3643:
3644: RFC 1156 MIB May 1990
3645:
3646:
3647: OBJECT:
3648: -------
3649: egpNeighEntry { egpNeighTable 1 }
3650:
3651: Syntax:
3652: EgpNeighEntry ::= SEQUENCE {
3653: egpNeighState
3654: INTEGER,
3655: egpNeighAddr
3656: IpAddress
3657: }
3658:
3659: Definition:
3660: Information about this entity's relationship with a
3661: particular EGP neighbor.
3662:
3663: Access:
3664: read-only.
3665:
3666: Status:
3667: mandatory.
3668:
3669:
3670: We now consider the individual components of each EGP
3671: neighbor entry:
3672:
3673:
3674: OBJECT:
3675: -------
3676: egpNeighState { egpNeighEntry 1 }
3677:
3678: Syntax:
3679: INTEGER {
3680: idle(1),
3681: acquisition(2),
3682: down(3),
3683: up(4),
3684: cease(5)
3685: }
3686:
3687: Definition:
3688: The EGP state of the local system with respect to this
3689: entry's EGP neighbor. Each EGP state is represented
3690: by a value that is one greater than the numerical
3691: value associated with said state in RFC 904.
3692:
3693: Access:
3694: read-only.
3695:
3696:
3697:
3698: McCloghrie & Rose [Page 66]
3699:
3700: RFC 1156 MIB May 1990
3701:
3702:
3703: Status:
3704: mandatory.
3705:
3706:
3707: OBJECT:
3708: -------
3709: egpNeighAddr { egpNeighEntry 2 }
3710:
3711: Syntax:
3712: IpAddress
3713:
3714: Definition:
3715: The IP address of this entry's EGP neighbor.
3716:
3717: Access:
3718: read-only.
3719:
3720: Status:
3721: mandatory.
3722:
3723:
3724:
3725:
3726:
3727:
3728:
3729:
3730:
3731:
3732:
3733:
3734:
3735:
3736:
3737:
3738:
3739:
3740:
3741:
3742:
3743:
3744:
3745:
3746:
3747:
3748:
3749:
3750:
3751:
3752:
3753:
3754: McCloghrie & Rose [Page 67]
3755:
3756: RFC 1156 MIB May 1990
3757:
3758:
3759: 6. Definitions
3760:
3761: RFC1156-MIB
3762:
3763: DEFINITIONS ::= BEGIN
3764:
3765: IMPORTS
3766: mgmt, OBJECT-TYPE, NetworkAddress, IpAddress,
3767: Counter, Gauge, TimeTicks
3768: FROM RFC1155-SMI;
3769:
3770: mib OBJECT IDENTIFIER ::= { mgmt 1 }
3771:
3772: system OBJECT IDENTIFIER ::= { mib 1 }
3773: interfaces OBJECT IDENTIFIER ::= { mib 2 }
3774: at OBJECT IDENTIFIER ::= { mib 3 }
3775: ip OBJECT IDENTIFIER ::= { mib 4 }
3776: icmp OBJECT IDENTIFIER ::= { mib 5 }
3777: tcp OBJECT IDENTIFIER ::= { mib 6 }
3778: udp OBJECT IDENTIFIER ::= { mib 7 }
3779: egp OBJECT IDENTIFIER ::= { mib 8 }
3780:
3781: -- object types
3782:
3783: -- the System group
3784:
3785: sysDescr OBJECT-TYPE
3786: SYNTAX OCTET STRING
3787: ACCESS read-only
3788: STATUS mandatory
3789: ::= { system 1 }
3790:
3791: sysObjectID OBJECT-TYPE
3792: SYNTAX OBJECT IDENTIFIER
3793: ACCESS read-only
3794: STATUS mandatory
3795: ::= { system 2 }
3796:
3797: sysUpTime OBJECT-TYPE
3798: SYNTAX TimeTicks
3799: ACCESS read-only
3800: STATUS mandatory
3801: ::= { system 3 }
3802:
3803: -- the Interfaces group
3804:
3805: ifNumber OBJECT-TYPE
3806: SYNTAX INTEGER
3807:
3808:
3809:
3810: McCloghrie & Rose [Page 68]
3811:
3812: RFC 1156 MIB May 1990
3813:
3814:
3815: ACCESS read-only
3816: STATUS mandatory
3817: ::= { interfaces 1 }
3818:
3819: -- the Interfaces table
3820:
3821: ifTable OBJECT-TYPE
3822: SYNTAX SEQUENCE OF IfEntry
3823: ACCESS read-write
3824: STATUS mandatory
3825: ::= { interfaces 2 }
3826:
3827: ifEntry OBJECT-TYPE
3828: SYNTAX IfEntry
3829: ACCESS read-write
3830: STATUS mandatory
3831: ::= { ifTable 1 }
3832:
3833: IfEntry ::= SEQUENCE {
3834: ifIndex
3835: INTEGER,
3836: ifDescr
3837: OCTET STRING,
3838: ifType
3839: INTEGER,
3840: ifMtu
3841: INTEGER,
3842: ifSpeed
3843: Gauge,
3844: ifPhysAddress
3845: OCTET STRING,
3846: ifAdminStatus
3847: INTEGER,
3848: ifOperStatus
3849: INTEGER,
3850: ifLastChange
3851: TimeTicks,
3852: ifInOctets
3853: Counter,
3854: ifInUcastPkts
3855: Counter,
3856: ifInNUcastPkts
3857: Counter,
3858: ifInDiscards
3859: Counter,
3860: ifInErrors
3861: Counter,
3862: ifInUnknownProtos
3863:
3864:
3865:
3866: McCloghrie & Rose [Page 69]
3867:
3868: RFC 1156 MIB May 1990
3869:
3870:
3871: Counter,
3872: ifOutOctets
3873: Counter,
3874: ifOutUcastPkts
3875: Counter,
3876: ifOutNUcastPkts
3877: Counter,
3878: ifOutDiscards
3879: Counter,
3880: ifOutErrors
3881: Counter,
3882: ifOutQLen
3883: Gauge
3884: }
3885:
3886: ifIndex OBJECT-TYPE
3887: SYNTAX INTEGER
3888: ACCESS read-only
3889: STATUS mandatory
3890: ::= { ifEntry 1 }
3891:
3892: ifDescr OBJECT-TYPE
3893: SYNTAX OCTET STRING
3894: ACCESS read-only
3895: STATUS mandatory
3896: ::= { ifEntry 2 }
3897:
3898: ifType OBJECT-TYPE
3899: SYNTAX INTEGER {
3900: other(1), -- none of the following
3901: regular1822(2),
3902: hdh1822(3),
3903: ddn-x25(4),
3904: rfc877-x25(5),
3905: ethernet-csmacd(6),
3906: iso88023-csmacd(7),
3907: iso88024-tokenBus(8),
3908: iso88025-tokenRing(9),
3909: iso88026-man(10),
3910: starLan(11),
3911: proteon-10MBit(12),
3912: proteon-80MBit(13),
3913: hyperchannel(14),
3914: fddi(15),
3915: lapb(16),
3916: sdlc(17),
3917: t1-carrier(18),
3918: cept(19),
3919:
3920:
3921:
3922: McCloghrie & Rose [Page 70]
3923:
3924: RFC 1156 MIB May 1990
3925:
3926:
3927: basicIsdn(20),
3928: primaryIsdn(21),
3929: -- proprietary serial
3930: propPointToPointSerial(22)
3931: }
3932: ACCESS read-only
3933: STATUS mandatory
3934: ::= { ifEntry 3 }
3935:
3936: ifMtu OBJECT-TYPE
3937: SYNTAX INTEGER
3938: ACCESS read-only
3939: STATUS mandatory
3940: ::= { ifEntry 4 }
3941:
3942: ifSpeed OBJECT-TYPE
3943: SYNTAX Gauge
3944: ACCESS read-only
3945: STATUS mandatory
3946: ::= { ifEntry 5 }
3947:
3948: ifPhysAddress OBJECT-TYPE
3949: SYNTAX OCTET STRING
3950: ACCESS read-only
3951: STATUS mandatory
3952: ::= { ifEntry 6 }
3953:
3954: ifAdminStatus OBJECT-TYPE
3955: SYNTAX INTEGER {
3956: up(1), -- ready to pass packets
3957: down(2),
3958: testing(3) -- in some test mode
3959: }
3960: ACCESS read-write
3961: STATUS mandatory
3962: ::= { ifEntry 7 }
3963:
3964: ifOperStatus OBJECT-TYPE
3965: SYNTAX INTEGER {
3966: up(1), -- ready to pass packets
3967: down(2),
3968: testing(3) -- in some test mode
3969: }
3970: ACCESS read-only
3971: STATUS mandatory
3972: ::= { ifEntry 8 }
3973:
3974: ifLastChange OBJECT-TYPE
3975:
3976:
3977:
3978: McCloghrie & Rose [Page 71]
3979:
3980: RFC 1156 MIB May 1990
3981:
3982:
3983: SYNTAX TimeTicks
3984: ACCESS read-only
3985: STATUS mandatory
3986: ::= { ifEntry 9 }
3987:
3988: ifInOctets OBJECT-TYPE
3989: SYNTAX Counter
3990: ACCESS read-only
3991: STATUS mandatory
3992: ::= { ifEntry 10 }
3993:
3994: ifInUcastPkts OBJECT-TYPE
3995: SYNTAX Counter
3996: ACCESS read-only
3997: STATUS mandatory
3998: ::= { ifEntry 11 }
3999:
4000: ifInNUcastPkts OBJECT-TYPE
4001: SYNTAX Counter
4002: ACCESS read-only
4003: STATUS mandatory
4004: ::= { ifEntry 12 }
4005:
4006: ifInDiscards OBJECT-TYPE
4007: SYNTAX Counter
4008: ACCESS read-only
4009: STATUS mandatory
4010: ::= { ifEntry 13 }
4011:
4012: ifInErrors OBJECT-TYPE
4013: SYNTAX Counter
4014: ACCESS read-only
4015: STATUS mandatory
4016: ::= { ifEntry 14 }
4017:
4018: ifInUnknownProtos OBJECT-TYPE
4019: SYNTAX Counter
4020: ACCESS read-only
4021: STATUS mandatory
4022: ::= { ifEntry 15 }
4023:
4024: ifOutOctets OBJECT-TYPE
4025: SYNTAX Counter
4026: ACCESS read-only
4027: STATUS mandatory
4028: ::= { ifEntry 16 }
4029:
4030: ifOutUcastPkts OBJECT-TYPE
4031:
4032:
4033:
4034: McCloghrie & Rose [Page 72]
4035:
4036: RFC 1156 MIB May 1990
4037:
4038:
4039: SYNTAX Counter
4040: ACCESS read-only
4041: STATUS mandatory
4042: ::= { ifEntry 17 }
4043:
4044: ifOutNUcastPkts OBJECT-TYPE
4045: SYNTAX Counter
4046: ACCESS read-only
4047: STATUS mandatory
4048: ::= { ifEntry 18 }
4049:
4050: ifOutDiscards OBJECT-TYPE
4051: SYNTAX Counter
4052: ACCESS read-only
4053: STATUS mandatory
4054: ::= { ifEntry 19 }
4055:
4056: ifOutErrors OBJECT-TYPE
4057: SYNTAX Counter
4058: ACCESS read-only
4059: STATUS mandatory
4060: ::= { ifEntry 20 }
4061:
4062: ifOutQLen OBJECT-TYPE
4063: SYNTAX Gauge
4064: ACCESS read-only
4065: STATUS mandatory
4066: ::= { ifEntry 21 }
4067:
4068: -- the Address Translation group
4069:
4070: atTable OBJECT-TYPE
4071: SYNTAX SEQUENCE OF AtEntry
4072: ACCESS read-write
4073: STATUS mandatory
4074: ::= { at 1 }
4075:
4076: atEntry OBJECT-TYPE
4077: SYNTAX AtEntry
4078: ACCESS read-write
4079: STATUS mandatory
4080: ::= { atTable 1 }
4081:
4082: AtEntry ::= SEQUENCE {
4083: atIfIndex
4084: INTEGER,
4085: atPhysAddress
4086: OCTET STRING,
4087:
4088:
4089:
4090: McCloghrie & Rose [Page 73]
4091:
4092: RFC 1156 MIB May 1990
4093:
4094:
4095: atNetAddress
4096: NetworkAddress
4097: }
4098:
4099: atIfIndex OBJECT-TYPE
4100: SYNTAX INTEGER
4101: ACCESS read-write
4102: STATUS mandatory
4103: ::= { atEntry 1 }
4104:
4105: atPhysAddress OBJECT-TYPE
4106: SYNTAX OCTET STRING
4107: ACCESS read-write
4108: STATUS mandatory
4109: ::= { atEntry 2 }
4110:
4111: atNetAddress OBJECT-TYPE
4112: SYNTAX NetworkAddress
4113: ACCESS read-write
4114: STATUS mandatory
4115: ::= { atEntry 3 }
4116:
4117: -- the IP group
4118:
4119: ipForwarding OBJECT-TYPE
4120: SYNTAX INTEGER {
4121: gateway(1), -- entity forwards datagrams
4122: host(2) -- entity does NOT forward datagrams
4123: }
4124: ACCESS read-only
4125: STATUS mandatory
4126: ::= { ip 1 }
4127:
4128: ipDefaultTTL OBJECT-TYPE
4129: SYNTAX INTEGER
4130: ACCESS read-write
4131: STATUS mandatory
4132: ::= { ip 2 }
4133:
4134: ipInReceives OBJECT-TYPE
4135: SYNTAX Counter
4136: ACCESS read-only
4137: STATUS mandatory
4138: ::= { ip 3 }
4139:
4140: ipInHdrErrors OBJECT-TYPE
4141: SYNTAX Counter
4142: ACCESS read-only
4143:
4144:
4145:
4146: McCloghrie & Rose [Page 74]
4147:
4148: RFC 1156 MIB May 1990
4149:
4150:
4151: STATUS mandatory
4152: ::= { ip 4 }
4153:
4154: ipInAddrErrors OBJECT-TYPE
4155: SYNTAX Counter
4156: ACCESS read-only
4157: STATUS mandatory
4158: ::= { ip 5 }
4159:
4160: ipForwDatagrams OBJECT-TYPE
4161: SYNTAX Counter
4162: ACCESS read-only
4163: STATUS mandatory
4164: ::= { ip 6 }
4165:
4166: ipInUnknownProtos OBJECT-TYPE
4167: SYNTAX Counter
4168: ACCESS read-only
4169: STATUS mandatory
4170: ::= { ip 7 }
4171:
4172: ipInDiscards OBJECT-TYPE
4173: SYNTAX Counter
4174: ACCESS read-only
4175: STATUS mandatory
4176: ::= { ip 8 }
4177:
4178: ipInDelivers OBJECT-TYPE
4179: SYNTAX Counter
4180: ACCESS read-only
4181: STATUS mandatory
4182: ::= { ip 9 }
4183:
4184: ipOutRequests OBJECT-TYPE
4185: SYNTAX Counter
4186: ACCESS read-only
4187: STATUS mandatory
4188: ::= { ip 10 }
4189:
4190: ipOutDiscards OBJECT-TYPE
4191: SYNTAX Counter
4192: ACCESS read-only
4193: STATUS mandatory
4194: ::= { ip 11 }
4195:
4196: ipOutNoRoutes OBJECT-TYPE
4197: SYNTAX Counter
4198: ACCESS read-only
4199:
4200:
4201:
4202: McCloghrie & Rose [Page 75]
4203:
4204: RFC 1156 MIB May 1990
4205:
4206:
4207: STATUS mandatory
4208: ::= { ip 12 }
4209:
4210: ipReasmTimeout OBJECT-TYPE
4211: SYNTAX INTEGER
4212: ACCESS read-only
4213: STATUS mandatory
4214: ::= { ip 13 }
4215:
4216: ipReasmReqds OBJECT-TYPE
4217: SYNTAX Counter
4218: ACCESS read-only
4219: STATUS mandatory
4220: ::= { ip 14 }
4221:
4222: ipReasmOKs OBJECT-TYPE
4223: SYNTAX Counter
4224: ACCESS read-only
4225: STATUS mandatory
4226: ::= { ip 15 }
4227:
4228: ipReasmFails OBJECT-TYPE
4229: SYNTAX Counter
4230: ACCESS read-only
4231: STATUS mandatory
4232: ::= { ip 16 }
4233:
4234: ipFragOKs OBJECT-TYPE
4235: SYNTAX Counter
4236: ACCESS read-only
4237: STATUS mandatory
4238: ::= { ip 17 }
4239:
4240: ipFragFails OBJECT-TYPE
4241: SYNTAX Counter
4242: ACCESS read-only
4243: STATUS mandatory
4244: ::= { ip 18 }
4245:
4246: ipFragCreates OBJECT-TYPE
4247: SYNTAX Counter
4248: ACCESS read-only
4249: STATUS mandatory
4250: ::= { ip 19 }
4251:
4252: -- the IP Interface table
4253:
4254: ipAddrTable OBJECT-TYPE
4255:
4256:
4257:
4258: McCloghrie & Rose [Page 76]
4259:
4260: RFC 1156 MIB May 1990
4261:
4262:
4263: SYNTAX SEQUENCE OF IpAddrEntry
4264: ACCESS read-only
4265: STATUS mandatory
4266: ::= { ip 20 }
4267:
4268: ipAddrEntry OBJECT-TYPE
4269: SYNTAX IpAddrEntry
4270: ACCESS read-only
4271: STATUS mandatory
4272: ::= { ipAddrTable 1 }
4273:
4274: IpAddrEntry ::= SEQUENCE {
4275: ipAdEntAddr
4276: IpAddress,
4277: ipAdEntIfIndex
4278: INTEGER,
4279: ipAdEntNetMask
4280: IpAddress,
4281: ipAdEntBcastAddr
4282: INTEGER
4283: }
4284:
4285: ipAdEntAddr OBJECT-TYPE
4286: SYNTAX IpAddress
4287: ACCESS read-only
4288: STATUS mandatory
4289: ::= { ipAddrEntry 1 }
4290:
4291: ipAdEntIfIndex OBJECT-TYPE
4292: SYNTAX INTEGER
4293: ACCESS read-only
4294: STATUS mandatory
4295: ::= { ipAddrEntry 2 }
4296:
4297: ipAdEntNetMask OBJECT-TYPE
4298: SYNTAX IpAddress
4299: ACCESS read-only
4300: STATUS mandatory
4301: ::= { ipAddrEntry 3 }
4302:
4303: ipAdEntBcastAddr OBJECT-TYPE
4304: SYNTAX INTEGER
4305: ACCESS read-only
4306: STATUS mandatory
4307: ::= { ipAddrEntry 4 }
4308:
4309:
4310:
4311:
4312:
4313:
4314: McCloghrie & Rose [Page 77]
4315:
4316: RFC 1156 MIB May 1990
4317:
4318:
4319: -- the IP Routing table
4320:
4321: ipRoutingTable OBJECT-TYPE
4322: SYNTAX SEQUENCE OF IpRouteEntry
4323: ACCESS read-write
4324: STATUS mandatory
4325: ::= { ip 21 }
4326:
4327: ipRouteEntry OBJECT-TYPE
4328: SYNTAX IpRouteEntry
4329: ACCESS read-write
4330: STATUS mandatory
4331: ::= { ipRoutingTable 1 }
4332:
4333: IpRouteEntry ::= SEQUENCE {
4334: ipRouteDest
4335: IpAddress,
4336: ipRouteIfIndex
4337: INTEGER,
4338: ipRouteMetric1
4339: INTEGER,
4340: ipRouteMetric2
4341: INTEGER,
4342: ipRouteMetric3
4343: INTEGER,
4344: ipRouteMetric4
4345: INTEGER,
4346: ipRouteNextHop
4347: IpAddress,
4348: ipRouteType
4349: INTEGER,
4350: ipRouteProto
4351: INTEGER,
4352: ipRouteAge
4353: INTEGER
4354: }
4355:
4356: ipRouteDest OBJECT-TYPE
4357: SYNTAX IpAddress
4358: ACCESS read-write
4359: STATUS mandatory
4360: ::= { ipRouteEntry 1 }
4361:
4362: ipRouteIfIndex OBJECT-TYPE
4363: SYNTAX INTEGER
4364: ACCESS read-write
4365: STATUS mandatory
4366: ::= { ipRouteEntry 2 }
4367:
4368:
4369:
4370: McCloghrie & Rose [Page 78]
4371:
4372: RFC 1156 MIB May 1990
4373:
4374:
4375: ipRouteMetric1 OBJECT-TYPE
4376: SYNTAX INTEGER
4377: ACCESS read-write
4378: STATUS mandatory
4379: ::= { ipRouteEntry 3 }
4380:
4381: ipRouteMetric2 OBJECT-TYPE
4382: SYNTAX INTEGER
4383: ACCESS read-write
4384: STATUS mandatory
4385: ::= { ipRouteEntry 4 }
4386:
4387: ipRouteMetric3 OBJECT-TYPE
4388: SYNTAX INTEGER
4389: ACCESS read-write
4390: STATUS mandatory
4391: ::= { ipRouteEntry 5 }
4392:
4393: ipRouteMetric4 OBJECT-TYPE
4394: SYNTAX INTEGER
4395: ACCESS read-write
4396: STATUS mandatory
4397: ::= { ipRouteEntry 6 }
4398:
4399: ipRouteNextHop OBJECT-TYPE
4400: SYNTAX IpAddress
4401: ACCESS read-write
4402: STATUS mandatory
4403: ::= { ipRouteEntry 7 }
4404:
4405: ipRouteType OBJECT-TYPE
4406: SYNTAX INTEGER {
4407: other(1), -- none of the following
4408:
4409: invalid(2), -- an invalidated route
4410:
4411: -- route to directly
4412: direct(3), -- connected (sub-)network
4413:
4414: -- route to a non-local
4415: remote(4), -- host/network/sub-network
4416: }
4417: ACCESS read-write
4418: STATUS mandatory
4419: ::= { ipRouteEntry 8 }
4420:
4421: ipRouteProto OBJECT-TYPE
4422: SYNTAX INTEGER {
4423:
4424:
4425:
4426: McCloghrie & Rose [Page 79]
4427:
4428: RFC 1156 MIB May 1990
4429:
4430:
4431: other(1), -- none of the following
4432:
4433: -- non-protocol information
4434: -- e.g., manually
4435: local(2), -- configured entries
4436:
4437: -- set via a network
4438: netmgmt(3), -- management protocol
4439:
4440: -- obtained via ICMP,
4441: icmp(4), -- e.g., Redirect
4442:
4443: -- the following are
4444: -- gateway routing protocols
4445: egp(5),
4446: ggp(6),
4447: hello(7),
4448: rip(8),
4449: is-is(9),
4450: es-is(10),
4451: ciscoIgrp(11),
4452: bbnSpfIgp(12),
4453: oigp(13)
4454: }
4455: ACCESS read-only
4456: STATUS mandatory
4457: ::= { ipRouteEntry 9 }
4458:
4459: ipRouteAge OBJECT-TYPE
4460: SYNTAX INTEGER
4461: ACCESS read-write
4462: STATUS mandatory
4463: ::= { ipRouteEntry 10 }
4464:
4465: -- the ICMP group
4466:
4467: icmpInMsgs OBJECT-TYPE
4468: SYNTAX Counter
4469: ACCESS read-only
4470: STATUS mandatory
4471: ::= { icmp 1 }
4472:
4473: icmpInErrors OBJECT-TYPE
4474: SYNTAX Counter
4475: ACCESS read-only
4476: STATUS mandatory
4477: ::= { icmp 2 }
4478:
4479:
4480:
4481:
4482: McCloghrie & Rose [Page 80]
4483:
4484: RFC 1156 MIB May 1990
4485:
4486:
4487: icmpInDestUnreachs OBJECT-TYPE
4488: SYNTAX Counter
4489: ACCESS read-only
4490: STATUS mandatory
4491: ::= { icmp 3 }
4492:
4493: icmpInTimeExcds OBJECT-TYPE
4494: SYNTAX Counter
4495: ACCESS read-only
4496: STATUS mandatory
4497: ::= { icmp 4 }
4498:
4499: icmpInParmProbs OBJECT-TYPE
4500: SYNTAX Counter
4501: ACCESS read-only
4502: STATUS mandatory
4503: ::= { icmp 5 }
4504:
4505: icmpInSrcQuenchs OBJECT-TYPE
4506: SYNTAX Counter
4507: ACCESS read-only
4508: STATUS mandatory
4509: ::= { icmp 6 }
4510:
4511: icmpInRedirects OBJECT-TYPE
4512: SYNTAX Counter
4513: ACCESS read-only
4514: STATUS mandatory
4515: ::= { icmp 7 }
4516:
4517: icmpInEchos OBJECT-TYPE
4518: SYNTAX Counter
4519: ACCESS read-only
4520: STATUS mandatory
4521: ::= { icmp 8 }
4522:
4523: icmpInEchoReps OBJECT-TYPE
4524: SYNTAX Counter
4525: ACCESS read-only
4526: STATUS mandatory
4527: ::= { icmp 9 }
4528:
4529: icmpInTimestamps OBJECT-TYPE
4530: SYNTAX Counter
4531: ACCESS read-only
4532: STATUS mandatory
4533: ::= { icmp 10 }
4534:
4535:
4536:
4537:
4538: McCloghrie & Rose [Page 81]
4539:
4540: RFC 1156 MIB May 1990
4541:
4542:
4543: icmpInTimestampReps OBJECT-TYPE
4544: SYNTAX Counter
4545: ACCESS read-only
4546: STATUS mandatory
4547: ::= { icmp 11 }
4548:
4549: icmpInAddrMasks OBJECT-TYPE
4550: SYNTAX Counter
4551: ACCESS read-only
4552: STATUS mandatory
4553: ::= { icmp 12 }
4554:
4555: icmpInAddrMaskReps OBJECT-TYPE
4556: SYNTAX Counter
4557: ACCESS read-only
4558: STATUS mandatory
4559: ::= { icmp 13 }
4560:
4561: icmpOutMsgs OBJECT-TYPE
4562: SYNTAX Counter
4563: ACCESS read-only
4564: STATUS mandatory
4565: ::= { icmp 14 }
4566:
4567: icmpOutErrors OBJECT-TYPE
4568: SYNTAX Counter
4569: ACCESS read-only
4570: STATUS mandatory
4571: ::= { icmp 15 }
4572:
4573: icmpOutDestUnreachs OBJECT-TYPE
4574: SYNTAX Counter
4575: ACCESS read-only
4576: STATUS mandatory
4577: ::= { icmp 16 }
4578:
4579: icmpOutTimeExcds OBJECT-TYPE
4580: SYNTAX Counter
4581: ACCESS read-only
4582: STATUS mandatory
4583: ::= { icmp 17 }
4584:
4585: icmpOutParmProbs OBJECT-TYPE
4586: SYNTAX Counter
4587: ACCESS read-only
4588: STATUS mandatory
4589: ::= { icmp 18 }
4590:
4591:
4592:
4593:
4594: McCloghrie & Rose [Page 82]
4595:
4596: RFC 1156 MIB May 1990
4597:
4598:
4599: icmpOutSrcQuenchs OBJECT-TYPE
4600: SYNTAX Counter
4601: ACCESS read-only
4602: STATUS mandatory
4603: ::= { icmp 19 }
4604:
4605: icmpOutRedirects OBJECT-TYPE
4606: SYNTAX Counter
4607: ACCESS read-only
4608: STATUS mandatory
4609: ::= { icmp 20 }
4610:
4611: icmpOutEchos OBJECT-TYPE
4612: SYNTAX Counter
4613: ACCESS read-only
4614: STATUS mandatory
4615: ::= { icmp 21 }
4616:
4617: icmpOutEchoReps OBJECT-TYPE
4618: SYNTAX Counter
4619: ACCESS read-only
4620: STATUS mandatory
4621: ::= { icmp 22 }
4622:
4623: icmpOutTimestamps OBJECT-TYPE
4624: SYNTAX Counter
4625: ACCESS read-only
4626: STATUS mandatory
4627: ::= { icmp 23 }
4628:
4629: icmpOutTimestampReps OBJECT-TYPE
4630: SYNTAX Counter
4631: ACCESS read-only
4632: STATUS mandatory
4633: ::= { icmp 24 }
4634:
4635: icmpOutAddrMasks OBJECT-TYPE
4636: SYNTAX Counter
4637: ACCESS read-only
4638: STATUS mandatory
4639: ::= { icmp 25 }
4640:
4641: icmpOutAddrMaskReps OBJECT-TYPE
4642: SYNTAX Counter
4643: ACCESS read-only
4644: STATUS mandatory
4645: ::= { icmp 26 }
4646:
4647:
4648:
4649:
4650: McCloghrie & Rose [Page 83]
4651:
4652: RFC 1156 MIB May 1990
4653:
4654:
4655: -- the TCP group
4656:
4657: tcpRtoAlgorithm OBJECT-TYPE
4658: SYNTAX INTEGER {
4659: other(1), -- none of the following
4660: constant(2), -- a constant rto
4661: rsre(3), -- MIL-STD-1778, Appendix B
4662: vanj(4) -- Van Jacobson's algorithm [15]
4663: }
4664: ACCESS read-only
4665: STATUS mandatory
4666: ::= { tcp 1 }
4667:
4668: tcpRtoMin OBJECT-TYPE
4669: SYNTAX INTEGER
4670: ACCESS read-only
4671: STATUS mandatory
4672: ::= { tcp 2 }
4673:
4674: tcpRtoMax OBJECT-TYPE
4675: SYNTAX INTEGER
4676: ACCESS read-only
4677: STATUS mandatory
4678: ::= { tcp 3 }
4679:
4680: tcpMaxConn OBJECT-TYPE
4681: SYNTAX INTEGER
4682: ACCESS read-only
4683: STATUS mandatory
4684: ::= { tcp 4 }
4685:
4686: tcpActiveOpens OBJECT-TYPE
4687: SYNTAX Counter
4688: ACCESS read-only
4689: STATUS mandatory
4690: ::= { tcp 5 }
4691:
4692: tcpPassiveOpens OBJECT-TYPE
4693: SYNTAX Counter
4694: ACCESS read-only
4695: STATUS mandatory
4696: ::= { tcp 6 }
4697:
4698: tcpAttemptFails OBJECT-TYPE
4699: SYNTAX Counter
4700: ACCESS read-only
4701: STATUS mandatory
4702: ::= { tcp 7 }
4703:
4704:
4705:
4706: McCloghrie & Rose [Page 84]
4707:
4708: RFC 1156 MIB May 1990
4709:
4710:
4711: tcpEstabResets OBJECT-TYPE
4712: SYNTAX Counter
4713: ACCESS read-only
4714: STATUS mandatory
4715: ::= { tcp 8 }
4716:
4717: tcpCurrEstab OBJECT-TYPE
4718: SYNTAX Gauge
4719: ACCESS read-only
4720: STATUS mandatory
4721: ::= { tcp 9 }
4722:
4723: tcpInSegs OBJECT-TYPE
4724: SYNTAX Counter
4725: ACCESS read-only
4726: STATUS mandatory
4727: ::= { tcp 10 }
4728:
4729: tcpOutSegs OBJECT-TYPE
4730: SYNTAX Counter
4731: ACCESS read-only
4732: STATUS mandatory
4733: ::= { tcp 11 }
4734:
4735: tcpRetransSegs OBJECT-TYPE
4736: SYNTAX Counter
4737: ACCESS read-only
4738: STATUS mandatory
4739: ::= { tcp 12 }
4740:
4741: -- the TCP connections table
4742:
4743: tcpConnTable OBJECT-TYPE
4744: SYNTAX SEQUENCE OF TcpConnEntry
4745: ACCESS read-only
4746: STATUS mandatory
4747: ::= { tcp 13 }
4748:
4749: tcpConnEntry OBJECT-TYPE
4750: SYNTAX TcpConnEntry
4751: ACCESS read-only
4752: STATUS mandatory
4753: ::= { tcpConnTable 1 }
4754:
4755: TcpConnEntry ::= SEQUENCE {
4756: tcpConnState
4757: INTEGER,
4758: tcpConnLocalAddress
4759:
4760:
4761:
4762: McCloghrie & Rose [Page 85]
4763:
4764: RFC 1156 MIB May 1990
4765:
4766:
4767: IpAddress,
4768: tcpConnLocalPort
4769: INTEGER (0..65535),
4770: tcpConnRemAddress
4771: IpAddress,
4772: tcpConnRemPort
4773: INTEGER (0..65535)
4774: }
4775:
4776: tcpConnState OBJECT-TYPE
4777: SYNTAX INTEGER {
4778: closed(1),
4779: listen(2),
4780: synSent(3),
4781: synReceived(4),
4782: established(5),
4783: finWait1(6),
4784: finWait2(7),
4785: closeWait(8),
4786: lastAck(9),
4787: closing(10),
4788: timeWait(11)
4789: }
4790: ACCESS read-only
4791: STATUS mandatory
4792: ::= { tcpConnEntry 1 }
4793:
4794: tcpConnLocalAddress OBJECT-TYPE
4795: SYNTAX IpAddress
4796: ACCESS read-only
4797: STATUS mandatory
4798: ::= { tcpConnEntry 2 }
4799:
4800: tcpConnLocalPort OBJECT-TYPE
4801: SYNTAX INTEGER (0..65535)
4802: ACCESS read-only
4803: STATUS mandatory
4804: ::= { tcpConnEntry 3 }
4805:
4806: tcpConnRemAddress OBJECT-TYPE
4807: SYNTAX IpAddress
4808: ACCESS read-only
4809: STATUS mandatory
4810: ::= { tcpConnEntry 4 }
4811:
4812: tcpConnRemPort OBJECT-TYPE
4813: SYNTAX INTEGER (0..65535)
4814: ACCESS read-only
4815:
4816:
4817:
4818: McCloghrie & Rose [Page 86]
4819:
4820: RFC 1156 MIB May 1990
4821:
4822:
4823: STATUS mandatory
4824: ::= { tcpConnEntry 5 }
4825:
4826: -- the UDP group
4827:
4828: udpInDatagrams OBJECT-TYPE
4829: SYNTAX Counter
4830: ACCESS read-only
4831: STATUS mandatory
4832: ::= { udp 1 }
4833:
4834: udpNoPorts OBJECT-TYPE
4835: SYNTAX Counter
4836: ACCESS read-only
4837: STATUS mandatory
4838: ::= { udp 2 }
4839:
4840: udpInErrors OBJECT-TYPE
4841: SYNTAX Counter
4842: ACCESS read-only
4843: STATUS mandatory
4844: ::= { udp 3 }
4845:
4846: udpOutDatagrams OBJECT-TYPE
4847: SYNTAX Counter
4848: ACCESS read-only
4849: STATUS mandatory
4850: ::= { udp 4 }
4851:
4852: -- the EGP group
4853:
4854: egpInMsgs OBJECT-TYPE
4855: SYNTAX Counter
4856: ACCESS read-only
4857: STATUS mandatory
4858: ::= { egp 1 }
4859:
4860: egpInErrors OBJECT-TYPE
4861: SYNTAX Counter
4862: ACCESS read-only
4863: STATUS mandatory
4864: ::= { egp 2 }
4865:
4866: egpOutMsgs OBJECT-TYPE
4867: SYNTAX Counter
4868: ACCESS read-only
4869: STATUS mandatory
4870: ::= { egp 3 }
4871:
4872:
4873:
4874: McCloghrie & Rose [Page 87]
4875:
4876: RFC 1156 MIB May 1990
4877:
4878:
4879: egpOutErrors OBJECT-TYPE
4880: SYNTAX Counter
4881: ACCESS read-only
4882: STATUS mandatory
4883: ::= { egp 4 }
4884:
4885: -- the EGP Neighbor table
4886:
4887: egpNeighTable OBJECT-TYPE
4888: SYNTAX SEQUENCE OF EgpNeighEntry
4889: ACCESS read-only
4890: STATUS mandatory
4891: ::= { egp 5 }
4892:
4893: egpNeighEntry OBJECT-TYPE
4894: SYNTAX EgpNeighEntry
4895: ACCESS read-only
4896: STATUS mandatory
4897: ::= { egpNeighTable 1 }
4898:
4899: EgpNeighEntry ::= SEQUENCE {
4900: egpNeighState
4901: INTEGER,
4902: egpNeighAddr
4903: IpAddress
4904: }
4905:
4906: egpNeighState OBJECT-TYPE
4907: SYNTAX INTEGER {
4908: idle(1),
4909: acquisition(2),
4910: down(3),
4911: up(4),
4912: cease(5)
4913: }
4914: ACCESS read-only
4915: STATUS mandatory
4916: ::= { egpNeighEntry 1 }
4917:
4918: egpNeighAddr OBJECT-TYPE
4919: SYNTAX IpAddress
4920: ACCESS read-only
4921: STATUS mandatory
4922: ::= { egpNeighEntry 2 }
4923:
4924: END
4925:
4926:
4927:
4928:
4929:
4930: McCloghrie & Rose [Page 88]
4931:
4932: RFC 1156 MIB May 1990
4933:
4934:
4935: 7. Acknowledgements
4936:
4937: The initial draft of this memo was heavily influenced by the the HEMS
4938: [9] and SNMP [10] MIBs.
4939:
4940: Its final form is the result of the suggestions, the dicussions, and
4941: the compromises reached by the members of the IETF MIB working group:
4942:
4943: Karl Auerbach, Epilogue Technology
4944: K. Ramesh Babu, Excelan
4945: Lawrence Besaw, Hewlett-Packard
4946: Jeffrey D. Case, University of Tennessee at Knoxville
4947: James R. Davin, Proteon
4948: Mark S. Fedor, NYSERNet
4949: Robb Foster, BBN
4950: Phill Gross, The MITRE Corporation
4951: Bent Torp Jensen, Convergent Technology
4952: Lee Labarre, The MITRE Corporation
4953: Dan Lynch, Advanced Computing Environments
4954: Keith McCloghrie, The Wollongong Group
4955: Dave Mackie, 3Com/Bridge
4956: Craig Partridge, BBN (chair)
4957: Jim Robertson, 3Com/Bridge
4958: Marshall T. Rose, The Wollongong Group
4959: Greg Satz, cisco
4960: Martin Lee Schoffstall, Rensselaer Polytechnic Institute
4961: Lou Steinberg, IBM
4962: Dean Throop, Data General
4963: Unni Warrier, Unisys
4964:
4965:
4966:
4967:
4968:
4969:
4970:
4971:
4972:
4973:
4974:
4975:
4976:
4977:
4978:
4979:
4980:
4981:
4982:
4983:
4984:
4985:
4986: McCloghrie & Rose [Page 89]
4987:
4988: RFC 1156 MIB May 1990
4989:
4990:
4991: 8. References
4992:
4993: [1] Cerf, V., "IAB Recommendations for the Development of Internet
4994: Network Management Standards", RFC 1052, IAB, April 1988.
4995:
4996: [2] Information processing systems - Open Systems Interconnection,
4997: "Management Information Services Definition", International
4998: Organization for Standardization, Draft Proposal 9595/2,
4999: December 1987.
5000:
5001: [3] Information processing systems - Open Systems Interconnection,
5002: "Management Information Protocol Specification", International
5003: Organization for Standardization, Draft Proposal 9596/2,
5004: December 1987.
5005:
5006: [4] Rose M., and K. McCloghrie, "Structure and Identification of
5007: Management Information for TCP/IP-based internets", RFC 1065,
5008: TWG, August 1988.
5009:
5010: [5] Partridge C., and G. Trewitt, "The High-Level Entity Management
5011: System (HEMS)", RFCs 1021-1024, BBN and Stanford, October 1987.
5012:
5013: [6] Cerf, V., "Report of the Second Ad Hoc Network Management Review
5014: Group", RFC 1109, IAB, August 1989.
5015:
5016: [7] Rose, M., and K. McCloghrie, "Structure and Identification of
5017: Management Information for TCP/IP-based Internets", RFC 1155,
5018: Performance Systems International and Hughes LAN Systems, May
5019: 1990.
5020:
5021: [8] Case, J., M. Fedor, M. Schoffstall, and J. Davin, The Simple
5022: Network Management Protocol", RFC 1157, University of Tennessee
5023: at Knoxville, Performance Systems International, Performance
5024: Systems International, and the MIT Laboratory for Computer
5025: Science, May 1990.
5026:
5027: [9] Partridge C., and G. Trewitt, "HEMS Variable Definitions", RFC
5028: 1024, BBN and Stanford, October 1987.
5029:
5030: [10] Case, J., M. Fedor, M. Schoffstall, and J. Davin, "A Simple
5031: Network Management Protocol", RFC 1067, University of Tennessee
5032: At Knoxville, NYSERNet, Rensselaer Polytechnic, Proteon, August
5033: 1988.
5034:
5035: [11] LaBarre, L., "Structure and Identification of Management
5036: Information for the Internet", Internet Engineering Task Force
5037: working note, Network Information Center, SRI International,
5038: Menlo Park, California, April 1988.
5039:
5040:
5041:
5042: McCloghrie & Rose [Page 90]
5043:
5044: RFC 1156 MIB May 1990
5045:
5046:
5047: [12] LaBarre, L., "Transport Layer Management Information: TCP",
5048: Internet Engineering Task Force working note in preparation.
5049: Network Information Center, SRI International, Menlo Park,
5050: California, (unpublished).
5051:
5052: [13] Information processing systems - Open Systems Interconnection,
5053: "Specification of Abstract Syntax Notation One (ASN.1)",
5054: International Organization for Standardization, International
5055: Standard 8824, December 1987.
5056:
5057: [14] Information processing systems - Open Systems Interconnection,
5058: "Specification of Basic Encoding Rules for Abstract Notation One
5059: (ASN.1)", International Organization for Standardization,
5060: International Standard 8825, December 1987.
5061:
5062: [15] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM, 1988,
5063: Stanford, California.
5064:
5065: Security Considerations
5066:
5067: Security issues are not discussed in this memo.
5068:
5069: Authors' Addresses
5070:
5071: Keith McCloghrie
5072: The Wollongong Group
5073: 1129 San Antonio Road
5074: Palo Alto, CA 04303
5075:
5076: Phone: (415) 962-7160
5077:
5078: EMail: [email protected]
5079:
5080:
5081: Marshall T. Rose
5082: PSI, Inc.
5083: PSI California Office
5084: P.O. Box 391776
5085: Mountain View, CA 94039
5086:
5087: Phone: (415) 961-3380
5088:
5089: EMail: [email protected]
5090:
5091:
5092:
5093:
5094:
5095:
5096:
5097:
5098: McCloghrie & Rose [Page 91]
5099:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.