![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to rfc1158.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 rfc1158.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 M. Rose, Editor
8: Request for Comments: 1158 Performance Systems International
9: May 1990
10:
11:
12: Management Information Base for Network Management
13: of TCP/IP-based internets:
14: MIB-II
15:
16: 1. Status of this Memo
17:
18: This memo defines the second version of the Management Information
19: Base (MIB-II) for use with network management protocols in TCP/IP-
20: based internets. In particular, together with its companion memos
21: which describe the structure of management information (RFC 1155)
22: along with the network management protocol (RFC 1157) for TCP/IP-
23: based internets, these documents provide a simple, workable
24: architecture and system for managing TCP/IP-based internets and in
25: particular the Internet community.
26:
27: This document on MIB-II incorporates all of the technical content of
28: RFC 1156 on MIB-I and extends it, without loss of compatibilty.
29: However, MIB-I as described in RFC 1156 is full Standard Protocol of
30: the Internet, while the MIB-II described here is Proposed Standard
31: Protocol of the Internet.
32:
33: This memo defines a mandatory extension to the base MIB (RFC 1156)
34: and is a Proposed Standard for the Internet community. The
35: extensions described here are currently Elective, but when they
36: become a standard, they will have the same status as RFC 1156, that
37: is, Recommended. The Internet Activities Board recommends that all
38: IP and TCP implementations be network manageable. This implies
39: implementation of the Internet MIB (RFC 1156 and the extensions in
40: RFC 1158) and at least one of the two recommended management
41: protocols SNMP (RFC 1157) or CMOT (RFC 1095).
42:
43: This version of the MIB specification, MIB-II, is an incremental
44: refinement of MIB-I. As such, it has been designed according to two
45: criteria: first, changes have been made in response to new
46: operational requirements in the Internet; and, second, the changes
47: are entirely upwards compatible in order to minimize impact on the
48: network as the managed nodes in the Internet transition from MIB-I to
49: MIB-II.
50:
51: It is expected that additional MIB groups and variables will be
52: defined over time to accommodate the monitoring and control needs of
53: new or changing components of the Internet.
54:
55:
56:
57:
58: IETF SNMP Working Group [Page 1]
59:
60: RFC 1158 MIB II May 1990
61:
62:
63: Please refer to the latest edition of the "IAB Official Protocol
64: Standards" RFC for current information on the state and status of
65: standard Internet protocols.
66:
67: Distribution of this memo is unlimited.
68:
69: Table of Contents
70:
71:
72: 1. Status of this Memo .................................. 1
73: 2. Introduction ......................................... 3
74: 3. Changes from MIB-I ................................... 4
75: 3.1 Deprecated Objects .................................. 4
76: 3.2 Display Strings ..................................... 5
77: 3.3 The System Group .................................... 5
78: 3.4 The Interfaces Group ................................ 5
79: 3.5 The Address Translation Group ....................... 6
80: 3.6 The IP Group ........................................ 7
81: 3.7 The ICMP Group ...................................... 7
82: 3.8 The TCP Group ....................................... 7
83: 3.9 The UDP Group ....................................... 7
84: 3.10 The EGP Group ...................................... 8
85: 3.11 The Transmission Group ............................. 8
86: 3.12 The SNMP Group ..................................... 8
87: 4. Objects .............................................. 8
88: 4.1 Object Groups ....................................... 9
89: 4.2 Format of Definitions ............................... 10
90: 5. Object Definitions ................................... 10
91: 5.1 The System Group .................................... 11
92: 5.2 The Interfaces Group ................................ 14
93: 5.2.1 The Interfaces table .............................. 15
94: 5.3 The Address Translation Group ....................... 27
95: 5.4 The IP Group ........................................ 30
96: 5.4.1 The IP Address table .............................. 38
97: 5.4.2 The IP Routing table .............................. 41
98: 5.4.3 The IP Address Translation table .................. 48
99: 5.5 The ICMP Group ...................................... 51
100: 5.6 The TCP Group ....................................... 61
101: 5.6.1 The TCP Connection table .......................... 66
102: 5.6.2 Additional TCP Objects ............................ 69
103: 5.7 The UDP Group ....................................... 70
104: 5.7.1 The UDP Listener table ............................ 72
105: 5.8 The EGP Group ....................................... 73
106: 5.8.1 The EGP Neighbor table ............................ 75
107: 5.8.2 Additional EGP variables .......................... 83
108: 5.9 The Transmission Group .............................. 83
109: 5.10 The SNMP Group ..................................... 83
110: 6. Definitions .......................................... 95
111:
112:
113:
114: IETF SNMP Working Group [Page 2]
115:
116: RFC 1158 MIB II May 1990
117:
118:
119: 7. Identification of OBJECT instances for use with the
120: SNMP ................................................. 126
121: 7.1 ifTable Object Type Names ........................... 127
122: 7.2 atTable Object Type Names ........................... 127
123: 7.3 ipAddrTable Object Type Names ....................... 128
124: 7.4 ipRoutingTable Object Type Names .................... 128
125: 7.5 ipNetToMediaTable Object Type Names ................. 129
126: 7.6 tcpConnTable Object Type Names ...................... 129
127: 7.7 udpTable Object Type Names .......................... 130
128: 7.8 egpNeighTable Object Type Names ..................... 130
129: 8. Acknowledgements .................................... 130
130: 9. References .......................................... 131
131: 10. Security Considerations.............................. 133
132: 11. Author's Address..................................... 133
133:
134: 2. Introduction
135:
136: As reported in RFC 1052, IAB Recommendations for the
137: Development of Internet Network Management Standards [1], a
138: two-prong strategy for network management of TCP/IP-based
139: internets was undertaken. In the short-term, the Simple
140: Network Management Protocol (SNMP) was to be used to manage
141: nodes in the Internet community. In the long-term, the use of
142: the OSI network management framework was to be examined. Two
143: documents were produced to define the management information:
144: RFC 1065, which defined the Structure of Management
145: Information (SMI) [2], and RFC 1066, which defined the
146: Management Information Base (MIB) [3]. Both of these
147: documents were designed so as to be compatible with both the
148: SNMP and the OSI network management framework.
149:
150: This strategy was quite successful in the short-term:
151: Internet-based network management technology was fielded, by
152: both the research and commercial communities, within a few
153: months. As a result of this, portions of the Internet
154: community became network manageable in a timely fashion.
155:
156: As reported in RFC 1109, Report of the Second Ad Hoc Network
157: Management Review Group [4], the requirements of the SNMP and
158: the OSI network management frameworks were more different than
159: anticipated. As such, the requirement for compatibility
160: between the SMI/MIB and both frameworks was suspended. This
161: action permitted the operational network management framework,
162: the SNMP, to respond to new operational needs in the Internet
163: community by producing this document.
164:
165: As such, the current network management framework for TCP/IP-
166: based internets consists of: Structure and Identification of
167:
168:
169:
170: IETF SNMP Working Group [Page 3]
171:
172: RFC 1158 MIB II May 1990
173:
174:
175: Management Information for TCP/IP-based internets, RFC 1155 [13],
176: which describes how managed objects contained in the MIB are
177: defined; Management Information Base for Network Management of
178: TCP/IP-based internets (version 2), this memo, which describes
179: the managed objects contained in the MIB; and, the Simple
180: Network Management Protocol, RFC 1157 [14], which defines the
181: protocol used to manage these objects.
182:
183: Consistent with the IAB directive to produce simple, workable
184: systems in the short-term, the list ofc objects (e.g., for BSD UNIX)
185: were excluded.
186:
187: 7) It was agreed to avoid heavily instrumenting critical
188: sections of code. The general guideline was one counter
189: per critical section per layer.
190:
191: 3. Changes from MIB-I
192:
193: Features of this MIB include:
194:
195: 1) incremental additions to reflect new operational
196: requirements;
197:
198: 2) upwards compatibility with the SMI/MIB and the SNMP;
199:
200: 3) improved support for multi-protocol entities; and,
201:
202: 4) textual clean-up of the MIB to improve clarity and
203: readability.
204:
205: The objects defined in MIB-II have the OBJECT IDENTIFIER prefix:
206:
207: mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
208:
209: 3.1. Deprecated Objects
210:
211: In order to better prepare implementors for future changes in the
212: MIB, a new term "deprecated" may be used when describing an object.
213: A deprecated object in the MIB is one which must be supported, but
214: one which will most likely be removed from the next version of the
215: MIB (e.g., MIB-III).
216:
217: MIB-II marks one object as being deprecated:
218:
219: atTable
220:
221: As a result of deprecating the atTable object, the entire Address
222: Translation group is deprecated.
223:
224:
225:
226: IETF SNMP Working Group [Page 4]
227:
228: RFC 1158 MIB II May 1990
229:
230:
231: Note that no functionality is lost with the deprecation of these
232: objects: new objects providing equivalent or superior functionality
233: are defined in MIB-II.
234:
235: 3.2. Display Strings
236:
237: In the past, there have been misinterpretations of the MIB as to when
238: a string of octets should contain printable characters, meant to be
239: displayed to a human. As a textual convention in the MIB, the
240: datatype
241:
242: DisplayString ::= OCTET STRING
243:
244: is introduced. A DisplayString is restricted to the NVT ASCII
245: character set, as defined in pages 10-11 of [7].
246:
247: The following objects are now defined in terms of DisplayString:
248:
249: sysDescr
250: ifDescr
251:
252: It should be noted that this change has no effect on either the
253: syntax nor semantics of these objects. The use of the DisplayString
254: notation is merely an artifact of the explanatory method used in
255: MIB-II and future MIBs.
256:
257: Further, it should be noted that any object defined in terms of OCTET
258: STRING may contain arbitrary binary data, in which each octet may
259: take any value from 0 to 255 (decimal).
260:
261: 3.3. The System Group
262:
263: Four new objects are added to this group:
264:
265: sysContact
266: sysName
267: sysLocation
268: sysServices
269:
270: These provide contact, administrative, location, and service
271: information regarding the managed node.
272:
273: 3.4. The Interfaces Group
274:
275: The definition of the ifNumber object was incorrect, as it required
276: all interfaces to support IP. (For example, devices without IP, such
277: as MAC-layer bridges, could not be managed if this definition was
278: strictly followed.) The description of the ifNumber object is changed
279:
280:
281:
282: IETF SNMP Working Group [Page 5]
283:
284: RFC 1158 MIB II May 1990
285:
286:
287: accordingly.
288:
289: The ifTable object was mistaken marked as read-write, it has been
290: (correctly) re-designated as read-only. In addition, several new
291: values have been added to the ifType column in the ifTable object:
292:
293: ppp(23)
294: softwareLoopback(24)
295: eon(25)
296: ethernet-3Mbit(26)
297: nsip(27)
298: slip(28)
299:
300: Finally, a new column has been added to the ifTable object:
301:
302: ifSpecific
303:
304: which provides information about information specific to the media
305: being used to realize the interface.
306:
307: 3.5. The Address Translation Group
308:
309: In MIB-I, this group contained a table which permitted mappings from
310: network addresses (e.g., IP addresses) to physical addresses (e.g.,
311: MAC addresses). Experience has shown that efficient implementations
312: of this table make two assumptions: a single network protocol
313: environment, and mappings occur only from network address to physical
314: address.
315:
316: The need to support multi-protocol nodes (e.g., those with both the
317: IP and CLNP active), and the need to support the inverse mapping
318: (e.g., for ES-IS), have invalidated both of these assumptions. As
319: such, the atTable object is declared deprecated.
320:
321: In order to meet both the multi-protocol and inverse mapping
322: requirements, MIB-II and its successors will allocate up to two
323: address translation tables inside each network protocol group. That
324: is, the IP group will contain one address translation table, for
325: going from IP addresses to physical addresses. Similarly, when a
326: document defining MIB objects for the CLNP is produced (e.g., [8]),
327: it will contain two tables, for mappings in both directions, as this
328: is required for full functionality.
329:
330: It should be noted that the choice of two tables (one for each
331: direction of mapping) provides for ease of implementation in many
332: cases, and does not introduce undue burden on implementations which
333: realize the address translation abstraction through a single internal
334: table.
335:
336:
337:
338: IETF SNMP Working Group [Page 6]
339:
340: RFC 1158 MIB II May 1990
341:
342:
343: 3.6. The IP Group
344:
345: The access attribute of the variable ipForwarding has been changed
346: from read-only to read-write.
347:
348: In addition, there is a new column to the ipAddrTable object,
349:
350: ipAdEntReasmMaxSize
351:
352: which keeps track of the largest IP datagram that can be re-
353: assembled on a particular interface. There is also a new column in
354: the ipRoutingTable object,
355:
356: ipRouteMask
357:
358: which is used for IP routing subsystems that support arbitrary subnet
359: masks.
360:
361: One new object is added to the IP group:
362:
363: ipNetToMediaTable
364:
365: which is the address translation table for the IP group (providing
366: identical functionality to the now deprecated atTable in the address
367: translation group).
368:
369: 3.7. The ICMP Group
370:
371: There are no changes to this group.
372:
373: 3.8. The TCP Group
374:
375: Two new variables are added:
376:
377: tcpInErrs
378: tcpOutRsts
379:
380: which keep track of the number of incoming TCP segments in error and
381: the number of resets generated by a TCP.
382:
383: 3.9. The UDP Group
384:
385: A new table:
386:
387: udpTable
388:
389: is added.
390:
391:
392:
393:
394: IETF SNMP Working Group [Page 7]
395:
396: RFC 1158 MIB II May 1990
397:
398:
399: 3.10. The EGP Group
400:
401: Experience has indicated a need for additional objects that are
402: useful in EGP monitoring. In addition to making several additions to
403: the egpNeighborTable object, a new variable is added:
404:
405: egpAs
406:
407: which gives the autonomous system associated with this EGP entity.
408:
409: 3.11. The Transmission Group
410:
411: MIB-I was lacking in that it did not distinguish between different
412: types of transmission media. A new group, the Transmission group, is
413: allocated for this purpose:
414:
415: transmission OBJECT IDENTIFIER ::= { mib-2 10 }
416:
417: When Internet-standard definitions for managing transmission media
418: are defined, the transmission group is used to provide a prefix for
419: the names of those objects.
420:
421: Typically, such definitions reside in the experimental portion of the
422: MIB until they are "proven", then as a part of the Internet
423: standardization process, the definitions are accordingly elevated and
424: a new object identifier, under the transmission group is defined. By
425: convention, the name assigned is:
426:
427: type OBJECT IDENTIFIER ::= { transmission number }
428:
429: where "type" is the symbolic value used for the media in the ifType
430: column of the ifTable object, and "number" is the actual integer
431: value corresponding to the symbol.
432:
433: 3.12. The SNMP Group
434:
435: The application-oriented working groups of the IETF have been tasked
436: to be receptive towards defining MIB variables specific to their
437: respective applications.
438:
439: For the SNMP, it is useful to have statistical information. A new
440: group, the SNMP group, is allocated for this purpose:
441:
442: snmp OBJECT IDENTIFIER ::= { mib-2 11 }
443:
444: 4. Objects
445:
446: Managed objects are accessed via a virtual information store, termed
447:
448:
449:
450: IETF SNMP Working Group [Page 8]
451:
452: RFC 1158 MIB II May 1990
453:
454:
455: the Management Information Base or MIB. Objects in the MIB are
456: defined using Abstract Syntax Notation One (ASN.1) [9].
457:
458: The mechanisms used for describing these objects are specified the
459: companion memo, the SMI. In particular, each object has a name, a
460: syntax, and an encoding. The name is an object identifier, an
461: administratively assigned name, which specifies an object type. The
462: object type together with an object instance serves to uniquely
463: identify a specific instantiation of the object. For human
464: convenience, we often use a textual string, termed the OBJECT
465: DESCRIPTOR, to also refer to the object type.
466:
467: The syntax of an object type defines the abstract data structure
468: corresponding to that object type. The ASN.1 language is used for
469: this purpose. However, the companion memo purposely restricts the
470: ASN.1 constructs which may be used. These restrictions are
471: explicitly made for simplicity.
472:
473: The encoding of an object type is simply how that object type is
474: represented using the object type's syntax. Implicitly tied to the
475: notion of an object type's syntax and encoding is how the object type
476: is represented when being transmitted on the network. This memo
477: specifies the use of the basic encoding rules (BER) of ASN.1 [10],
478: subject to the additional requirements imposed by the SNMP [14].
479:
480: 4.1. Object Groups
481:
482: Since this list of managed objects contains only the essential
483: elements, there is no need to allow individual objects to be
484: optional. Rather, the objects are arranged into the following
485: groups:
486:
487: - System
488: - Interfaces
489: - Address Translation (deprecated)
490: - IP
491: - ICMP
492: - TCP
493: - UDP
494: - EGP
495: - Transmission
496: - SNMP
497:
498: There are two reasons for defining these groups: to provide a means
499: of assigning object identifiers; and, to provide a method for
500: implementations of managed agents to know which objects they must
501: implement. This method is as follows: if the semantics of a group is
502: applicable to an implementation, then it must implement all objects
503:
504:
505:
506: IETF SNMP Working Group [Page 9]
507:
508: RFC 1158 MIB II May 1990
509:
510:
511: in that group. For example, an implementation must implement the EGP
512: group if and only if it implements the EGP.
513:
514: 4.2. Format of Definitions
515:
516: The next section contains the specification of all object types
517: contained in the MIB. Following the conventions of the companion
518: memo, the object types are defined using the following fields:
519:
520: OBJECT:
521: -------
522: A textual name, termed the OBJECT DESCRIPTOR, for the
523: object type, along with its corresponding OBJECT
524: IDENTIFIER.
525:
526: Syntax:
527: The abstract syntax for the object type, presented using
528: ASN.1. This must resolve to an instance of the ASN.1
529: type ObjectSyntax defined in the SMI.
530:
531: Definition:
532: A textual description of the semantics of the object
533: type. Implementations should ensure that their
534: interpretation of the object type fulfills this
535: definition since this MIB is intended for use in multi-
536: vendor environments. As such it is vital that object
537: types have consistent meaning across all machines.
538:
539: Access:
540: A keyword, one of read-only, read-write, write-only, or
541: not-accessible. Note that this designation specifies the
542: minimum level of support required. As a local matter,
543: implementations may support other access types (e.g., an
544: implementation may elect to permitting writing a variable
545: marked herein as read-only). Further, protocol-specific
546: "views" (e.g., those implied by an SNMP community) may
547: make further restrictions on access to a variable.
548:
549: Status:
550: A keyword, one of mandatory, optional, obsolete, or
551: deprecated. Use of deprecated implies mandatory status.
552:
553: 5. Object Definitions
554:
555: RFC1158-MIB
556:
557: DEFINITIONS ::= BEGIN
558:
559:
560:
561:
562: IETF SNMP Working Group [Page 10]
563:
564: RFC 1158 MIB II May 1990
565:
566:
567: IMPORTS
568: mgmt, OBJECT-TYPE, NetworkAddress, IpAddress,
569: Counter, Gauge, TimeTicks
570: FROM RFC1155-SMI;
571:
572: DisplayString ::=
573: OCTET STRING
574:
575:
576: mib-2 OBJECT IDENTIFIER ::= { mgmt 1 } -- MIB-II
577:
578: system OBJECT IDENTIFIER ::= { mib-2 1 }
579: interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
580: at OBJECT IDENTIFIER ::= { mib-2 3 }
581: ip OBJECT IDENTIFIER ::= { mib-2 4 }
582: icmp OBJECT IDENTIFIER ::= { mib-2 5 }
583: tcp OBJECT IDENTIFIER ::= { mib-2 6 }
584: udp OBJECT IDENTIFIER ::= { mib-2 7 }
585: egp OBJECT IDENTIFIER ::= { mib-2 8 }
586: -- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
587: transmission OBJECT IDENTIFIER ::= { mib-2 10 }
588: snmp OBJECT IDENTIFIER ::= { mib-2 11 }
589: END
590:
591: 5.1. The System Group
592:
593: Implementation of the System group is mandatory for all systems.
594:
595:
596: OBJECT:
597: -------
598: sysDescr { system 1 }
599:
600: Syntax:
601: DisplayString (SIZE (0..255))
602:
603: Definition:
604: A textual description of the entity. This value should
605: include the full name and version identification of the
606: system's hardware type, software operating-system, and
607: networking software. It is mandatory that this only
608: contain printable ASCII characters.
609:
610: Access:
611: read-only.
612:
613: Status:
614: mandatory.
615:
616:
617:
618: IETF SNMP Working Group [Page 11]
619:
620: RFC 1158 MIB II May 1990
621:
622:
623: OBJECT:
624: -------
625: sysObjectID { system 2 }
626:
627: Syntax:
628: OBJECT IDENTIFIER
629:
630: Definition:
631: The vendor's authoritative identification of the network
632: management subsystem contained in the entity. This value
633: is allocated within the SMI enterprises subtree
634: (1.3.6.1.4.1) and provides an easy and unambiguous means
635: for determining "what kind of box" is being managed. For
636: example, if vendor "Flintstones, Inc." was assigned the
637: subtree 1.3.6.1.4.1.4242, it could assign the identifier
638: 1.3.6.1.4.1.4242.1.1 to its "Fred Router".
639:
640: Access:
641: read-only.
642:
643: Status:
644: mandatory.
645:
646:
647: OBJECT:
648: -------
649: sysUpTime { system 3 }
650:
651: Syntax:
652: TimeTicks
653:
654: Definition:
655: The time (in hundredths of a second) since the network
656: management portion of the system was last re-initialized.
657:
658: Access:
659: read-only.
660:
661: Status:
662: mandatory.
663:
664:
665: OBJECT:
666: -------
667: sysContact { system 4 }
668:
669: Syntax:
670: DisplayString (SIZE (0..255))
671:
672:
673:
674: IETF SNMP Working Group [Page 12]
675:
676: RFC 1158 MIB II May 1990
677:
678:
679: Definition:
680: The textual identification of the contact person for this
681: managed node, together with information on how to contact
682: this person.
683:
684: Access:
685: read-write.
686:
687: Status:
688: mandatory.
689:
690:
691: OBJECT:
692: -------
693: sysName { system 5 }
694:
695: Syntax:
696: DisplayString (SIZE (0..255))
697:
698: Definition:
699: An administratively-assigned name for this managed node.
700: By convention, this is the node's fully-qualified domain
701: name.
702:
703: Access:
704: read-write.
705:
706: Status:
707: mandatory.
708:
709:
710: OBJECT:
711: -------
712: sysLocation { system 6 }
713:
714: Syntax:
715: DisplayString (SIZE (0..255))
716:
717: Definition:
718: The physical location of this node (e.g., "telephone
719: closet, 3rd floor").
720:
721: Access:
722: read-only.
723:
724: Status:
725: mandatory.
726:
727:
728:
729:
730: IETF SNMP Working Group [Page 13]
731:
732: RFC 1158 MIB II May 1990
733:
734:
735: OBJECT:
736: -------
737: sysServices { system 7 }
738:
739: Syntax:
740: INTEGER (0..127)
741:
742: Definition:
743: A value which indicates the set of services that this
744: entity potentially offers. The value is a sum. This
745: sum initially takes the value zero, Then, for each layer,
746: L, in the range 1 through 7, that this node performs
747: transactions for, 2 raised to (L - 1) is added to the
748: sum. For example, a node which performs only routing
749: functions would have a value of 4 (2^(3-1)). In
750: contrast, a node which is a host offering application
751: services would have a value of 72 (2^(4-1) + 2^(7-1)).
752: Note that in the context of the Internet suite of
753: protocols, values should be calculated accordingly:
754:
755: layer functionality
756: 1 physical (e.g., repeaters)
757: 2 datalink/subnetwork (e.g., bridges)
758: 3 internet (e.g., supports the IP)
759: 4 end-to-end (e.g., supports the TCP)
760: 7 applications (e.g., supports the SMTP)
761:
762: For systems including OSI protocols, layers 5 and 6 may
763: also be counted.
764:
765: Access:
766: read-only.
767:
768: Status:
769: mandatory.
770:
771: 5.2. The Interfaces Group
772:
773: Implementation of the Interfaces group is mandatory for all systems.
774:
775:
776: OBJECT:
777: -------
778: ifNumber { interfaces 1 }
779:
780: Syntax:
781: INTEGER
782:
783:
784:
785:
786: IETF SNMP Working Group [Page 14]
787:
788: RFC 1158 MIB II May 1990
789:
790:
791: Definition:
792: The number of network interfaces (regardless of their
793: current state) present on this system.
794:
795: Access:
796: read-only.
797:
798: Status:
799: mandatory.
800:
801: 5.2.1. The Interfaces table
802:
803: The Interfaces table contains information on the entity's interfaces.
804: Each interface is thought of as being attached to a "subnetwork".
805: Note that this term should not be confused with "subnet" which refers
806: to an addressing partitioning scheme used in the Internet suite of
807: protocols.
808:
809:
810: OBJECT:
811: -------
812: ifTable { interfaces 2 }
813:
814: Syntax:
815: SEQUENCE OF IfEntry
816:
817: Definition:
818: A list of interface entries. The number of entries is
819: given by the value of ifNumber.
820:
821: Access:
822: read-only.
823:
824: Status:
825: mandatory.
826:
827:
828: OBJECT:
829: -------
830: ifEntry { ifTable 1 }
831:
832:
833:
834:
835:
836:
837:
838:
839:
840:
841:
842: IETF SNMP Working Group [Page 15]
843:
844: RFC 1158 MIB II May 1990
845:
846:
847: Syntax:
848: IfEntry ::= SEQUENCE {
849: ifIndex
850: INTEGER,
851: ifDescr
852: DisplayString,
853: ifType
854: INTEGER,
855: ifMtu
856: INTEGER,
857: ifSpeed
858: Gauge,
859: ifPhysAddress
860: OCTET STRING,
861: ifAdminStatus
862: INTEGER,
863: ifOperStatus
864: INTEGER,
865: ifLastChange
866: TimeTicks,
867: ifInOctets
868: Counter,
869: ifInUcastPkts
870: Counter,
871: ifInNUcastPkts
872: Counter,
873: ifInDiscards
874: Counter,
875: ifInErrors
876: Counter,
877: ifInUnknownProtos
878: Counter,
879: ifOutOctets
880: Counter,
881: ifOutUcastPkts
882: Counter,
883: ifOutNUcastPkts
884: Counter,
885: ifOutDiscards
886: Counter,
887: ifOutErrors
888: Counter,
889: ifOutQLen
890: Gauge,
891: ifSpecific
892: OBJECT IDENTIFIER
893: }
894:
895:
896:
897:
898: IETF SNMP Working Group [Page 16]
899:
900: RFC 1158 MIB II May 1990
901:
902:
903: Definition:
904: An interface entry containing objects at the subnetwork
905: layer and below for a particular interface.
906:
907: Access:
908: read-only.
909:
910: Status:
911: mandatory.
912:
913:
914: We now consider the individual components of each interface
915: entry:
916:
917:
918: OBJECT:
919: -------
920: ifIndex { ifEntry 1 }
921:
922: Syntax:
923: INTEGER
924:
925: Definition:
926: A unique value for each interface. Its value ranges
927: between 1 and the value of ifNumber. The value for each
928: interface must remain constant at least from one re-
929: initialization of the entity's network management system
930: to the next re-initialization.
931:
932: Access:
933: read-only.
934:
935: Status:
936: mandatory.
937:
938:
939: OBJECT:
940: -------
941: ifDescr { ifEntry 2 }
942:
943: Syntax:
944: DisplayString (SIZE (0..255))
945:
946: Definition:
947: A textual string containing information about the
948: interface. This string should include the name of the
949: manufacturer, the product name and the version of the
950: hardware interface.
951:
952:
953:
954: IETF SNMP Working Group [Page 17]
955:
956: RFC 1158 MIB II May 1990
957:
958:
959: Access:
960: read-only.
961:
962: Status:
963: mandatory.
964:
965:
966: OBJECT:
967: -------
968: ifType { ifEntry 3 }
969:
970: Syntax:
971: INTEGER {
972: other(1), -- none of the following
973: regular1822(2),
974: hdh1822(3),
975: ddn-x25(4),
976: rfc877-x25(5),
977: ethernet-csmacd(6),
978: iso88023-csmacd(7),
979: iso88024-tokenBus(8),
980: iso88025-tokenRing(9),
981: iso88026-man(10),
982: starLan(11),
983: proteon-10Mbit(12),
984: proteon-80Mbit(13),
985: hyperchannel(14),
986: fddi(15),
987: lapb(16),
988: sdlc(17),
989: t1-carrier(18),
990: cept(19), -- european equivalent of T-1
991: basicISDN(20),
992: primaryISDN(21),
993: -- proprietary serial
994: propPointToPointSerial(22),
995: ppp(23),
996: softwareLoopback(24),
997: eon(25), -- CLNP over IP [12]
998: ethernet-3Mbit(26)
999: nsip(27), -- XNS over IP
1000: slip(28) -- generic SLIP
1001: }
1002:
1003: Definition:
1004: The type of interface, distinguished according to the
1005: physical/link protocol(s) immediately "below" the network
1006: layer in the protocol stack.
1007:
1008:
1009:
1010: IETF SNMP Working Group [Page 18]
1011:
1012: RFC 1158 MIB II May 1990
1013:
1014:
1015: Access:
1016: read-only.
1017:
1018: Status:
1019: mandatory.
1020:
1021:
1022: OBJECT:
1023: -------
1024: ifMtu { ifEntry 4 }
1025:
1026: Syntax:
1027: INTEGER
1028:
1029: Definition:
1030: The size of the largest datagram which can be
1031: sent/received on the interface, specified in octets. For
1032: interfaces that are used for transmitting network
1033: datagrams, this is the size of the largest network
1034: datagram that can be sent on the interface.
1035:
1036: Access:
1037: read-only.
1038:
1039: Status:
1040: mandatory.
1041:
1042:
1043: OBJECT:
1044: -------
1045: ifSpeed { ifEntry 5 }
1046:
1047: Syntax:
1048: Gauge
1049:
1050: Definition:
1051: An estimate of the interface's current bandwidth in bits
1052: per second. For interfaces which do not vary in
1053: bandwidth or for those where no accurate estimation can
1054: be made, this object should contain the nominal
1055: bandwidth.
1056:
1057: Access:
1058: read-only.
1059:
1060: Status:
1061: mandatory.
1062:
1063:
1064:
1065:
1066: IETF SNMP Working Group [Page 19]
1067:
1068: RFC 1158 MIB II May 1990
1069:
1070:
1071: OBJECT:
1072: -------
1073: ifPhysAddress { ifEntry 6 }
1074:
1075: Syntax:
1076: OCTET STRING
1077:
1078: Definition:
1079: The interface's address at the protocol layer immediately
1080: "below" the network layer in the protocol stack. For
1081: interfaces which do not have such an address (e.g., a
1082: serial line), this object should contain an octet string
1083: of zero length.
1084:
1085: Access:
1086: read-only.
1087:
1088: Status:
1089: mandatory.
1090:
1091:
1092: OBJECT:
1093: -------
1094: ifAdminStatus { ifEntry 7 }
1095:
1096: Syntax:
1097: INTEGER {
1098: up(1), -- ready to pass packets
1099: down(2),
1100: testing(3) -- in some test mode
1101: }
1102:
1103: Definition:
1104: The desired state of the interface. The testing(3) state
1105: indicates that no operational packets can be passed.
1106:
1107: Access:
1108: read-write.
1109:
1110: Status:
1111: mandatory.
1112:
1113:
1114: OBJECT:
1115: -------
1116: ifOperStatus { ifEntry 8 }
1117:
1118:
1119:
1120:
1121:
1122: IETF SNMP Working Group [Page 20]
1123:
1124: RFC 1158 MIB II May 1990
1125:
1126:
1127: Syntax:
1128: INTEGER {
1129: up(1), -- ready to pass packets
1130: down(2),
1131: testing(3) -- in some test mode
1132: }
1133:
1134: Definition:
1135: The current operational state of the interface. The
1136: testing(3) state indicates that no operational packets
1137: can be passed.
1138:
1139: Access:
1140: read-only.
1141:
1142: Status:
1143: mandatory.
1144:
1145:
1146: OBJECT:
1147: -------
1148: ifLastChange { ifEntry 9 }
1149:
1150: Syntax:
1151: TimeTicks
1152:
1153: Definition:
1154: The value of sysUpTime at the time the interface entered
1155: its current operational state. If the current state was
1156: entered prior to the last re-initialization of the local
1157: network management subsystem, then this object contains a
1158: zero value.
1159:
1160: Access:
1161: read-only.
1162:
1163: Status:
1164: mandatory.
1165:
1166:
1167: OBJECT:
1168: -------
1169: ifInOctets { ifEntry 10 }
1170:
1171: Syntax:
1172: Counter
1173:
1174:
1175:
1176:
1177:
1178: IETF SNMP Working Group [Page 21]
1179:
1180: RFC 1158 MIB II May 1990
1181:
1182:
1183: Definition:
1184: The total number of octets received on the interface,
1185: including framing characters.
1186:
1187: Access:
1188: read-only.
1189:
1190: Status:
1191: mandatory.
1192:
1193:
1194: OBJECT:
1195: -------
1196: ifInUcastPkts { ifEntry 11 }
1197:
1198: Syntax:
1199: Counter
1200:
1201: Definition:
1202: The number of subnetwork-unicast packets delivered to a
1203: higher-layer protocol.
1204:
1205: Access:
1206: read-only.
1207:
1208: Status:
1209: mandatory.
1210:
1211:
1212: OBJECT:
1213: -------
1214: ifInNUcastPkts { ifEntry 12 }
1215:
1216: Syntax:
1217: Counter
1218:
1219: Definition:
1220: The number of non-unicast (i.e., subnetwork-broadcast or
1221: subnetwork-multicast) packets delivered to a higher-layer
1222: protocol.
1223:
1224: Access:
1225: read-only.
1226:
1227: Status:
1228: mandatory.
1229:
1230:
1231:
1232:
1233:
1234: IETF SNMP Working Group [Page 22]
1235:
1236: RFC 1158 MIB II May 1990
1237:
1238:
1239: OBJECT:
1240: -------
1241: ifInDiscards { ifEntry 13 }
1242:
1243: Syntax:
1244: Counter
1245:
1246: Definition:
1247: The number of inbound packets which were chosen to be
1248: discarded even though no errors had been detected to
1249: prevent their being deliverable to a higher-layer
1250: protocol. One possible reason for discarding such a
1251: packet could be to free up buffer space.
1252:
1253: Access:
1254: read-only.
1255:
1256: Status:
1257: mandatory.
1258:
1259:
1260: OBJECT:
1261: -------
1262: ifInErrors { ifEntry 14 }
1263:
1264: Syntax:
1265: Counter
1266:
1267: Definition:
1268: The number of inbound packets that contained errors
1269: preventing them from being deliverable to a higher-layer
1270: protocol.
1271:
1272: Access:
1273: read-only.
1274:
1275: Status:
1276: mandatory.
1277:
1278:
1279: OBJECT:
1280: -------
1281: ifInUnknownProtos { ifEntry 15 }
1282:
1283: Syntax:
1284: Counter
1285:
1286:
1287:
1288:
1289:
1290: IETF SNMP Working Group [Page 23]
1291:
1292: RFC 1158 MIB II May 1990
1293:
1294:
1295: Definition:
1296: The number of packets received via the interface which
1297: were discarded because of an unknown or unsupported
1298: protocol.
1299:
1300: Access:
1301: read-only.
1302:
1303: Status:
1304: mandatory.
1305:
1306:
1307: OBJECT:
1308: -------
1309: ifOutOctets { ifEntry 16 }
1310:
1311: Syntax:
1312: Counter
1313:
1314: Definition:
1315: The total number of octets transmitted out of the
1316: interface, including framing characters.
1317:
1318: Access:
1319: read-only.
1320:
1321: Status:
1322: mandatory.
1323:
1324:
1325: OBJECT:
1326: -------
1327: ifOutUcastPkts { ifEntry 17 }
1328:
1329: Syntax:
1330: Counter
1331:
1332: Definition:
1333: The total number of packets that higher-level protocols
1334: requested be transmitted to a subnetwork-unicast address,
1335: including those that were discarded or not sent.
1336:
1337: Access:
1338: read-only.
1339:
1340: Status:
1341: mandatory.
1342:
1343:
1344:
1345:
1346: IETF SNMP Working Group [Page 24]
1347:
1348: RFC 1158 MIB II May 1990
1349:
1350:
1351: OBJECT:
1352: -------
1353: ifOutNUcastPkts { ifEntry 18 }
1354:
1355: Syntax:
1356: Counter
1357:
1358: Definition:
1359: The total number of packets that higher-level protocols
1360: requested be transmitted to a non-unicast (i.e., a
1361: subnetwork-broadcast or subnetwork-multicast) address,
1362: including those that were discarded or not sent.
1363:
1364: Access:
1365: read-only.
1366:
1367: Status:
1368: mandatory.
1369:
1370:
1371: OBJECT:
1372: -------
1373: ifOutDiscards { ifEntry 19 }
1374:
1375: Syntax:
1376: Counter
1377:
1378: Definition:
1379: The number of outbound packets which were chosen to be
1380: discarded even though no errors had been detected to
1381: prevent their being transmitted. One possible reason for
1382: discarding such a packet could be to free up buffer
1383: space.
1384:
1385: Access:
1386: read-only.
1387:
1388: Status:
1389: mandatory.
1390:
1391:
1392: OBJECT:
1393: -------
1394: ifOutErrors { ifEntry 20 }
1395:
1396: Syntax:
1397: Counter
1398:
1399:
1400:
1401:
1402: IETF SNMP Working Group [Page 25]
1403:
1404: RFC 1158 MIB II May 1990
1405:
1406:
1407: Definition:
1408: The number of outbound packets that could not be
1409: transmitted because of errors.
1410:
1411: Access:
1412: read-only.
1413:
1414: Status:
1415: mandatory.
1416:
1417:
1418: OBJECT:
1419: -------
1420: ifOutQLen { ifEntry 21 }
1421:
1422: Syntax:
1423: Gauge
1424:
1425: Definition:
1426: The length of the output packet queue (in packets).
1427:
1428: Access:
1429: read-only.
1430:
1431: Status:
1432: mandatory.
1433:
1434:
1435: OBJECT:
1436: -------
1437: ifSpecific { ifEntry 22 }
1438:
1439: Syntax:
1440: OBJECT IDENTIFIER
1441:
1442: Definition:
1443: A reference to MIB definitions specific to the particular
1444: media being used to realize the interface. For example,
1445: if the interface is realized by an ethernet, then the
1446: value of this object refers to a document defining
1447: objects specific to ethernet. If an agent is not
1448: configured to have a value for any of these variables,
1449: the object identifier
1450:
1451: nullSpecific OBJECT IDENTIFIER ::= { 0 0 }
1452:
1453: is returned. Note that "nullSpecific" is a syntatically
1454: valid object identifier, and any conformant
1455:
1456:
1457:
1458: IETF SNMP Working Group [Page 26]
1459:
1460: RFC 1158 MIB II May 1990
1461:
1462:
1463: implementation of ASN.1 and BER must be able to generate
1464: and recognize this value.
1465:
1466: Access:
1467: read-only.
1468:
1469: Status:
1470: mandatory.
1471:
1472: 5.3. The Address Translation Group
1473:
1474: Implementation of the Address Translation group is mandatory for all
1475: systems. Note however that this group is deprecated by MIB-II. That
1476: is, it is being included solely for compatibility with MIB-I nodes,
1477: and will most likely be excluded from MIB-III nodes. From MIB-II and
1478: onwards, each network protocol group contains its own address
1479: translation tables.
1480:
1481: The Address Translation group contains one table which is the union
1482: across all interfaces of the translation tables for converting a
1483: NetworkAddress (e.g., an IP address) into a subnetwork-specific
1484: address. For lack of a better term, this document refers to such a
1485: subnetwork-specific address as a "physical" address.
1486:
1487: Examples of such translation tables are: for broadcast media where
1488: ARP is in use, the translation table is equivalent to the ARP cache;
1489: or, on an X.25 network where non-algorithmic translation to X.121
1490: addresses is required, the translation table contains the
1491: NetworkAddress to X.121 address equivalences.
1492:
1493:
1494: OBJECT:
1495: -------
1496: atTable { at 1 }
1497:
1498: Syntax:
1499: SEQUENCE OF AtEntry
1500:
1501: Definition:
1502: The Address Translation tables contain the NetworkAddress
1503: to "physical" address equivalences. Some interfaces do
1504: not use translation tables for determining address
1505: equivalences (e.g., DDN-X.25 has an algorithmic method);
1506: if all interfaces are of this type, then the Address
1507: Translation table is empty, i.e., has zero entries.
1508:
1509: Access:
1510: read-write.
1511:
1512:
1513:
1514: IETF SNMP Working Group [Page 27]
1515:
1516: RFC 1158 MIB II May 1990
1517:
1518:
1519: Status:
1520: deprecated.
1521:
1522:
1523: OBJECT:
1524: -------
1525: atEntry { atTable 1 }
1526:
1527: Syntax:
1528: AtEntry ::= SEQUENCE {
1529: atIfIndex
1530: INTEGER,
1531: atPhysAddress
1532: OCTET STRING,
1533: atNetAddress
1534: NetworkAddress
1535: }
1536:
1537: Definition:
1538: Each entry contains one NetworkAddress to "physical"
1539: address equivalence.
1540:
1541: Access:
1542: read-write.
1543:
1544: Status:
1545: deprecated.
1546:
1547: We now consider the individual components of each Address
1548: Translation table entry:
1549:
1550:
1551: OBJECT:
1552: -------
1553: atIfIndex { atEntry 1 }
1554:
1555: Syntax:
1556: INTEGER
1557:
1558: Definition:
1559: The interface on which this entry's equivalence is
1560: effective. The interface identified by a particular
1561: value of this index is the same interface as identified
1562: by the same value of ifIndex.
1563:
1564: Access:
1565: read-write.
1566:
1567:
1568:
1569:
1570: IETF SNMP Working Group [Page 28]
1571:
1572: RFC 1158 MIB II May 1990
1573:
1574:
1575: Status:
1576: deprecated.
1577:
1578:
1579: OBJECT:
1580: -------
1581: atPhysAddress { atEntry 2 }
1582:
1583: Syntax:
1584: OCTET STRING
1585:
1586: Definition:
1587: The media-dependent "physical" address.
1588:
1589: Setting this object to a null string (one of zero length) has
1590: the effect of invaliding the corresponding entry in the
1591: atTable object. That is, it effectively disassociates the
1592: interface identified with said entry from the mapping
1593: identified with said entry. It is an implementation-specific
1594: matter as to whether the agent removes an invalidated entry
1595: from the table. Accordingly, management stations must be
1596: prepared to receive tabular information from agents that
1597: corresponds to entries not currently in use. Proper
1598: interpretation of such entries requires examination of the
1599: relevant atPhysAddress object.
1600:
1601: Access:
1602: read-write.
1603:
1604: Status:
1605: deprecated.
1606:
1607:
1608: OBJECT:
1609: -------
1610: atNetAddress { atEntry 3 }
1611:
1612: Syntax:
1613: NetworkAddress
1614:
1615: Definition:
1616: The NetworkAddress (e.g., the IP address) corresponding
1617: to the media-dependent "physical" address.
1618:
1619: Access:
1620: read-write.
1621:
1622:
1623:
1624:
1625:
1626: IETF SNMP Working Group [Page 29]
1627:
1628: RFC 1158 MIB II May 1990
1629:
1630:
1631: Status:
1632: deprecated.
1633:
1634: 5.4. The IP Group
1635:
1636: Implementation of the IP group is mandatory for all systems.
1637:
1638:
1639:
1640: OBJECT:
1641: -------
1642: ipForwarding { ip 1 }
1643:
1644: Syntax:
1645: INTEGER {
1646: forwarding(1), -- i.e., acting as a gateway
1647: not-forwarding(2) -- i.e., NOT acting as a gateway
1648: }
1649:
1650: Definition:
1651: The indication of whether this entity is acting as an IP
1652: gateway in respect to the forwarding of datagrams
1653: received by, but not addressed to, this entity. IP
1654: gateways forward datagrams. IP hosts do not (except
1655: those source-routed via the host).
1656:
1657: Access:
1658: read-write.
1659:
1660: Status:
1661: mandatory.
1662:
1663:
1664: OBJECT:
1665: -------
1666: ipDefaultTTL { ip 2 }
1667:
1668: Syntax:
1669: INTEGER
1670:
1671: Definition:
1672: The default value inserted into the Time-To-Live field of
1673: the IP header of datagrams originated at this entity,
1674: whenever a TTL value is not supplied by the transport
1675: layer protocol.
1676:
1677: Access:
1678: read-write.
1679:
1680:
1681:
1682: IETF SNMP Working Group [Page 30]
1683:
1684: RFC 1158 MIB II May 1990
1685:
1686:
1687: Status:
1688: mandatory.
1689:
1690:
1691: OBJECT:
1692: -------
1693: ipInReceives { ip 3 }
1694:
1695: Syntax:
1696: Counter
1697:
1698: Definition:
1699: The total number of input datagrams received from
1700: interfaces, including those received in error.
1701:
1702: Access:
1703: read-only.
1704:
1705: Status:
1706: mandatory.
1707:
1708:
1709: OBJECT:
1710: -------
1711: ipInHdrErrors { ip 4 }
1712:
1713: Syntax:
1714: Counter
1715:
1716: Definition:
1717: The number of input datagrams discarded due to errors in
1718: their IP headers, including bad checksums, version number
1719: mismatch, other format errors, time-to-live exceeded,
1720: errors discovered in processing their IP options, etc.
1721:
1722: Access:
1723: read-only.
1724:
1725: Status:
1726: mandatory.
1727:
1728:
1729: OBJECT:
1730: -------
1731: ipInAddrErrors { ip 5 }
1732:
1733: Syntax:
1734: Counter
1735:
1736:
1737:
1738: IETF SNMP Working Group [Page 31]
1739:
1740: RFC 1158 MIB II May 1990
1741:
1742:
1743: Definition:
1744: The number of input datagrams discarded because the IP
1745: address in their IP header's destination field was not a
1746: valid address to be received at this entity. This count
1747: includes invalid addresses (e.g., 0.0.0.0) and addresses
1748: of unsupported Classes (e.g., Class E). For entities
1749: which are not IP Gateways and therefore do not forward
1750: datagrams, this counter includes datagrams discarded
1751: because the destination address was not a local address.
1752:
1753: Access:
1754: read-only.
1755:
1756: Status:
1757: mandatory.
1758:
1759:
1760: OBJECT:
1761: -------
1762: ipForwDatagrams { ip 6 }
1763:
1764: Syntax:
1765: Counter
1766:
1767: Definition:
1768: The number of input datagrams for which this entity was
1769: not their final IP destination, as a result of which an
1770: attempt was made to find a route to forward them to that
1771: final destination. In entities which do not act as IP
1772: Gateways, this counter will include only those packets
1773: which were Source-Routed via this entity, and the
1774: Source-Route option processing was successful.
1775:
1776: Access:
1777: read-only.
1778:
1779: Status:
1780: mandatory.
1781:
1782:
1783: OBJECT:
1784: -------
1785: ipInUnknownProtos { ip 7 }
1786:
1787: Syntax:
1788: Counter
1789:
1790:
1791:
1792:
1793:
1794: IETF SNMP Working Group [Page 32]
1795:
1796: RFC 1158 MIB II May 1990
1797:
1798:
1799: Definition:
1800: The number of locally-addressed datagrams received
1801: successfully but discarded because of an unknown or
1802: unsupported protocol.
1803:
1804: Access:
1805: read-only.
1806:
1807: Status:
1808: mandatory.
1809:
1810:
1811: OBJECT:
1812: -------
1813: ipInDiscards { ip 8 }
1814:
1815: Syntax:
1816: Counter
1817:
1818: Definition:
1819: The number of input IP datagrams for which no problems
1820: were encountered to prevent their continued processing,
1821: but which were discarded (e.g., for lack of buffer
1822: space). Note that this counter does not include any
1823: datagrams discarded while awaiting re-assembly.
1824:
1825: Access:
1826: read-only.
1827:
1828: Status:
1829: mandatory.
1830:
1831:
1832: OBJECT:
1833: -------
1834: ipInDelivers { ip 9 }
1835:
1836: Syntax:
1837: Counter
1838:
1839: Definition:
1840: The total number of input datagrams successfully
1841: delivered to IP user-protocols (including ICMP).
1842:
1843: Access:
1844: read-only.
1845:
1846:
1847:
1848:
1849:
1850: IETF SNMP Working Group [Page 33]
1851:
1852: RFC 1158 MIB II May 1990
1853:
1854:
1855: Status:
1856: mandatory.
1857:
1858:
1859: OBJECT:
1860: -------
1861: ipOutRequests { ip 10 }
1862:
1863: Syntax:
1864: Counter
1865:
1866: Definition:
1867: The total number of IP datagrams which local IP user-
1868: protocols (including ICMP) supplied to IP in requests for
1869: transmission. Note that this counter does not include
1870: any datagrams counted in ipForwDatagrams.
1871:
1872: Access:
1873: read-only.
1874:
1875: Status:
1876: mandatory.
1877:
1878:
1879: OBJECT:
1880: ipOutDiscards { ip 11 }
1881:
1882: Syntax:
1883: Counter
1884:
1885: Definition:
1886: The number of output IP datagrams for which no problem
1887: was encountered to prevent their transmission to their
1888: destination, but which were discarded (e.g., for lack of
1889: buffer space). Note that this counter would include
1890: datagrams counted in ipForwDatagrams if any such packets
1891: met this (discretionary) discard criterion.
1892:
1893: Access:
1894: read-only.
1895:
1896: Status:
1897: mandatory.
1898:
1899:
1900: OBJECT:
1901: -------
1902: ipOutNoRoutes { ip 12 }
1903:
1904:
1905:
1906: IETF SNMP Working Group [Page 34]
1907:
1908: RFC 1158 MIB II May 1990
1909:
1910:
1911: Syntax:
1912: Counter
1913:
1914: Definition:
1915: The number of IP datagrams discarded because no route
1916: could be found to transmit them to their destination.
1917: Note that this counter includes any packets counted in
1918: ipForwDatagrams which meet this "no-route" criterion.
1919: Note that this includes any datagarms which a host cannot
1920: route because all of its default gateways are down.
1921:
1922: Access:
1923: read-only.
1924:
1925: Status:
1926: mandatory.
1927:
1928:
1929: OBJECT:
1930: -------
1931: ipReasmTimeout { ip 13 }
1932:
1933: Syntax:
1934: INTEGER
1935:
1936: Definition:
1937: The maximum number of seconds which received fragments
1938: are held while they are awaiting reassembly at this
1939: entity.
1940:
1941: Access:
1942: read-only.
1943:
1944: Status:
1945: mandatory.
1946:
1947:
1948: OBJECT:
1949: -------
1950: ipReasmReqds { ip 14 }
1951:
1952: Syntax:
1953: Counter
1954:
1955: Definition:
1956: The number of IP fragments received which needed to be
1957: reassembled at this entity.
1958:
1959:
1960:
1961:
1962: IETF SNMP Working Group [Page 35]
1963:
1964: RFC 1158 MIB II May 1990
1965:
1966:
1967: Access:
1968: read-only.
1969:
1970: Status:
1971: mandatory.
1972:
1973:
1974: OBJECT:
1975: -------
1976: ipReasmOKs { ip 15 }
1977:
1978: Syntax:
1979: Counter
1980:
1981: Definition:
1982: The number of IP datagrams successfully re-assembled.
1983:
1984: Access:
1985: read-only.
1986:
1987: Status:
1988: mandatory.
1989:
1990:
1991: OBJECT:
1992: -------
1993: ipReasmFails { ip 16 }
1994:
1995: Syntax:
1996: Counter
1997:
1998: Definition:
1999: The number of failures detected by the IP re-assembly
2000: algorithm (for whatever reason: timed out, errors, etc).
2001: Note that this is not necessarily a count of discarded IP
2002: fragments since some algorithms (notably the algorithm in
2003: RFC 815) can lose track of the number of fragments by
2004: combining them as they are received.
2005:
2006: Access:
2007: read-only.
2008:
2009: Status:
2010: mandatory.
2011:
2012:
2013:
2014:
2015:
2016:
2017:
2018: IETF SNMP Working Group [Page 36]
2019:
2020: RFC 1158 MIB II May 1990
2021:
2022:
2023: OBJECT:
2024: -------
2025: ipFragOKs { ip 17 }
2026:
2027: Syntax:
2028: Counter
2029:
2030: Definition:
2031: The number of IP datagrams that have been successfully
2032: fragmented at this entity.
2033:
2034: Access:
2035: read-only.
2036:
2037: Status:
2038: mandatory.
2039:
2040:
2041: OBJECT:
2042: -------
2043: ipFragFails { ip 18 }
2044:
2045: Syntax:
2046: Counter
2047:
2048: Definition:
2049: The number of IP datagrams that have been discarded
2050: because they needed to be fragmented at this entity but
2051: could not be, e.g., because their "Don't Fragment" flag
2052: was set.
2053:
2054: Access:
2055: read-only.
2056:
2057: Status:
2058: mandatory.
2059:
2060:
2061: OBJECT:
2062: -------
2063: ipFragCreates { ip 19 }
2064:
2065: Syntax:
2066: Counter
2067:
2068: Definition:
2069: The number of IP datagram fragments that have been
2070: generated as a result of fragmentation at this entity.
2071:
2072:
2073:
2074: IETF SNMP Working Group [Page 37]
2075:
2076: RFC 1158 MIB II May 1990
2077:
2078:
2079: Access:
2080: read-only.
2081:
2082: Status:
2083: mandatory.
2084:
2085: 5.4.1. The IP Address table
2086:
2087: The Ip Address table contains this entity's IP addressing
2088: information.
2089:
2090:
2091:
2092: OBJECT:
2093: -------
2094: ipAddrTable { ip 20 }
2095:
2096: Syntax:
2097: SEQUENCE OF IpAddrEntry
2098:
2099: Definition:
2100: The table of addressing information relevant to this
2101: entity's IP addresses.
2102:
2103: Access:
2104: read-only.
2105:
2106: Status:
2107: mandatory.
2108:
2109:
2110: OBJECT:
2111: -------
2112: ipAddrEntry { ipAddrTable 1 }
2113:
2114: Syntax:
2115: IpAddrEntry ::= SEQUENCE {
2116: ipAdEntAddr
2117: IpAddress,
2118: ipAdEntIfIndex
2119: INTEGER,
2120: ipAdEntNetMask
2121: IpAddress,
2122: ipAdEntBcastAddr
2123: INTEGER,
2124: ipAdEntReasmMaxSize
2125: INTEGER (0..65535)
2126: }
2127:
2128:
2129:
2130: IETF SNMP Working Group [Page 38]
2131:
2132: RFC 1158 MIB II May 1990
2133:
2134:
2135: Definition:
2136: The addressing information for one of this entity's IP
2137: addresses.
2138:
2139: Access:
2140: read-only.
2141:
2142: Status:
2143: mandatory.
2144:
2145:
2146: OBJECT:
2147: -------
2148: ipAdEntAddr { ipAddrEntry 1 }
2149:
2150: Syntax:
2151: IpAddress
2152:
2153: Definition:
2154: The IP address to which this entry's addressing
2155: information pertains.
2156:
2157: Access:
2158: read-only.
2159:
2160: Status:
2161: mandatory.
2162:
2163:
2164: OBJECT:
2165: -------
2166: ipAdEntIfIndex { ipAddrEntry 2 }
2167:
2168: Syntax:
2169: INTEGER
2170:
2171: Definition:
2172: The index value which uniquely identifies the interface
2173: to which this entry is applicable. The interface
2174: identified by a particular value of this index is the
2175: same interface as identified by the same value of
2176: ifIndex.
2177:
2178: Access:
2179: read-only.
2180:
2181: Status:
2182: mandatory.
2183:
2184:
2185:
2186: IETF SNMP Working Group [Page 39]
2187:
2188: RFC 1158 MIB II May 1990
2189:
2190:
2191: OBJECT:
2192: -------
2193: ipAdEntNetMask { ipAddrEntry 3 }
2194:
2195: Syntax:
2196: IpAddress
2197:
2198: Definition:
2199: The subnet mask associated with the IP address of this
2200: entry. The value of the mask is an IP address with all
2201: the network bits set to 1 and all the hosts bits set to
2202: 0.
2203:
2204: Access:
2205: read-only.
2206:
2207: Status:
2208: mandatory.
2209:
2210:
2211: OBJECT:
2212: -------
2213: ipAdEntBcastAddr { ipAddrEntry 4 }
2214:
2215: Syntax:
2216: INTEGER
2217:
2218: Definition:
2219: The value of the least-significant bit in the IP
2220: broadcast address used for sending datagrams on the
2221: (logical) interface associated with the IP address of
2222: this entry. For example, when the Internet standard
2223: all-ones broadcast address is used, the value will be 1.
2224: This value applies to both the subnet and network
2225: broadcasts addresses used by the entity on this (logical)
2226: interface.
2227:
2228: Access:
2229: read-only.
2230:
2231: Status:
2232: mandatory.
2233:
2234:
2235: OBJECT:
2236: -------
2237: ipAdEntReasmMaxSize { ipAddrEntry 5 }
2238:
2239:
2240:
2241:
2242: IETF SNMP Working Group [Page 40]
2243:
2244: RFC 1158 MIB II May 1990
2245:
2246:
2247: Syntax:
2248: INTEGER (0..65535)
2249:
2250: Definition:
2251: The size of the largest IP datagram which this entity can
2252: re-assemble from incoming IP fragmented datagrams
2253: received on this interface.
2254:
2255: Access:
2256: read-only.
2257:
2258: Status:
2259: mandatory.
2260:
2261: 5.4.2. The IP Routing table
2262:
2263: The IP Routing table contains an entry for each route presently known
2264: to this entity.
2265:
2266:
2267: OBJECT:
2268: -------
2269: ipRoutingTable { ip 21 }
2270:
2271: Syntax:
2272: SEQUENCE OF IpRouteEntry
2273:
2274: Definition:
2275: This entity's IP Routing table.
2276:
2277: Access:
2278: read-write.
2279:
2280: Status:
2281: mandatory.
2282:
2283:
2284: OBJECT:
2285: -------
2286: ipRouteEntry { ipRoutingTable 1 }
2287:
2288: Syntax:
2289: IpRouteEntry ::= SEQUENCE {
2290: ipRouteDest
2291: IpAddress,
2292: ipRouteIfIndex
2293: INTEGER,
2294: ipRouteMetric1
2295:
2296:
2297:
2298: IETF SNMP Working Group [Page 41]
2299:
2300: RFC 1158 MIB II May 1990
2301:
2302:
2303: INTEGER,
2304: ipRouteMetric2
2305: INTEGER,
2306: ipRouteMetric3
2307: INTEGER,
2308: ipRouteMetric4
2309: INTEGER,
2310: ipRouteNextHop
2311: IpAddress,
2312: ipRouteType
2313: INTEGER,
2314: ipRouteProto
2315: INTEGER,
2316: ipRouteAge
2317: INTEGER,
2318: ipRouteMask
2319: IpAddress
2320: }
2321:
2322: Definition:
2323: A route to a particular destination.
2324:
2325: Access:
2326: read-write.
2327:
2328: Status:
2329: mandatory.
2330:
2331: We now consider the individual components of each route in the
2332: IP Routing table:
2333:
2334:
2335: OBJECT:
2336: -------
2337: ipRouteDest { ipRouteEntry 1 }
2338:
2339: Syntax:
2340: IpAddress
2341:
2342: Definition:
2343: The destination IP address of this route. An entry with
2344: a value of 0.0.0.0 is considered a default route.
2345: Multiple routes to a single destination can appear in the
2346: table, but access to such multiple entries is dependent
2347: on the table-access mechanisms defined by the network
2348: management protocol in use.
2349:
2350:
2351:
2352:
2353:
2354: IETF SNMP Working Group [Page 42]
2355:
2356: RFC 1158 MIB II May 1990
2357:
2358:
2359: Access:
2360: read-write.
2361:
2362: Status:
2363: mandatory.
2364:
2365:
2366: OBJECT:
2367: -------
2368: ipRouteIfIndex { ipRouteEntry 2 }
2369:
2370: Syntax:
2371: INTEGER
2372:
2373: Definition:
2374: The index value which uniquely identifies the local
2375: interface through which the next hop of this route should
2376: be reached. The interface identified by a particular
2377: value of this index is the same interface as identified
2378: by the same value of ifIndex.
2379:
2380: Access:
2381: read-write.
2382:
2383: Status:
2384: mandatory.
2385:
2386:
2387: OBJECT:
2388: -------
2389: ipRouteMetric1 { ipRouteEntry 3 }
2390:
2391: Syntax:
2392: INTEGER
2393:
2394: Definition:
2395: The primary routing metric for this route. The semantics
2396: of this metric are determined by the routing-protocol
2397: specified in the route's ipRouteProto value. If this
2398: metric is not used, its value should be set to -1.
2399:
2400: Access:
2401: read-write.
2402:
2403: Status:
2404: mandatory.
2405:
2406:
2407:
2408:
2409:
2410: IETF SNMP Working Group [Page 43]
2411:
2412: RFC 1158 MIB II May 1990
2413:
2414:
2415: OBJECT:
2416: -------
2417: ipRouteMetric2 { ipRouteEntry 4 }
2418:
2419: Syntax:
2420: INTEGER
2421:
2422: Definition:
2423: An alternate routing metric for this route. The
2424: semantics of this metric are determined by the routing-
2425: protocol specified in the route's ipRouteProto value. If
2426: this metric is not used, its value should be set to -1.
2427:
2428: Access:
2429: read-write.
2430:
2431: Status:
2432: mandatory.
2433:
2434:
2435: OBJECT:
2436: -------
2437: ipRouteMetric3 { ipRouteEntry 5 }
2438:
2439: Syntax:
2440: INTEGER
2441:
2442: Definition:
2443: An alternate routing metric for this route. The
2444: semantics of this metric are determined by the routing-
2445: protocol specified in the route's ipRouteProto value. If
2446: this metric is not used, its value should be set to -1.
2447:
2448: Access:
2449: read-write.
2450:
2451: Status:
2452: mandatory.
2453:
2454:
2455: OBJECT:
2456: -------
2457: ipRouteMetric4 { ipRouteEntry 6 }
2458:
2459: Syntax:
2460: INTEGER
2461:
2462:
2463:
2464:
2465:
2466: IETF SNMP Working Group [Page 44]
2467:
2468: RFC 1158 MIB II May 1990
2469:
2470:
2471: Definition:
2472: An alternate routing metric for this route. The
2473: semantics of this metric are determined by the routing-
2474: protocol specified in the route's ipRouteProto value. If
2475: this metric is not used, its value should be set to -1.
2476:
2477: Access:
2478: read-write.
2479:
2480: Status:
2481: mandatory.
2482:
2483:
2484: OBJECT:
2485: -------
2486: ipRouteNextHop { ipRouteEntry 7 }
2487:
2488: Syntax:
2489: IpAddress
2490:
2491: Definition:
2492: The IP address of the next hop of this route. (In the
2493: case of a route bound to an interface which is realized
2494: via a broadcast media, the value of this field is the
2495: agent's IP address on that interface.)
2496:
2497: Access:
2498: read-write.
2499:
2500: Status:
2501: mandatory.
2502:
2503:
2504: OBJECT:
2505: -------
2506: ipRouteType { ipRouteEntry 8 }
2507:
2508: Syntax:
2509: INTEGER {
2510: other(1), -- none of the following
2511:
2512: invalid(2), -- an invalidated route
2513:
2514: -- route to directly
2515: direct(3), -- connected (sub-)network
2516:
2517: -- route to a non-local
2518: remote(4) -- host/network/sub-network
2519:
2520:
2521:
2522: IETF SNMP Working Group [Page 45]
2523:
2524: RFC 1158 MIB II May 1990
2525:
2526:
2527: }
2528:
2529: Definition:
2530: The type of route.
2531:
2532: Setting this object to the value invalid(2) has the effect of
2533: invalidating the corresponding entry in the ipRoutingTable
2534: object. That is, it effectively disassociates the destination
2535: identified with said entry from the route identified with said
2536: entry. It is an implementation-specific matter as to whether
2537: the agent removes an invalidated entry from the table.
2538: Accordingly, management stations must be prepared to receive
2539: tabular information from agents that corresponds to entries
2540: not currently in use. Proper interpretation of such entries
2541: requires examination of the relevant ipRouteType object.
2542:
2543: Access:
2544: read-write.
2545:
2546: Status:
2547: mandatory.
2548:
2549:
2550: OBJECT:
2551: -------
2552: ipRouteProto { ipRouteEntry 9 }
2553:
2554: Syntax:
2555: INTEGER {
2556: other(1), -- none of the following
2557:
2558: -- non-protocol information,
2559: -- e.g., manually configured
2560: local(2), -- entries
2561:
2562: -- set via a network management
2563: netmgmt(3), -- protocol
2564:
2565: -- obtained via ICMP,
2566: icmp(4), -- e.g., Redirect
2567:
2568: -- the remaining values are
2569: -- all gateway routing protocols
2570: egp(5),
2571: ggp(6),
2572: hello(7),
2573: rip(8),
2574: is-is(9),
2575:
2576:
2577:
2578: IETF SNMP Working Group [Page 46]
2579:
2580: RFC 1158 MIB II May 1990
2581:
2582:
2583: es-is(10),
2584: ciscoIgrp(11),
2585: bbnSpfIgp(12),
2586: ospf(13),
2587: bgp(14)
2588: }
2589:
2590: Definition:
2591: The routing mechanism via which this route was learned.
2592: Inclusion of values for gateway routing protocols is not
2593: intended to imply that hosts should support those
2594: protocols.
2595:
2596: Access:
2597: read-only.
2598:
2599: Status:
2600: mandatory.
2601:
2602:
2603: OBJECT:
2604: -------
2605: ipRouteAge { ipRouteEntry 10 }
2606:
2607: Syntax:
2608: INTEGER
2609:
2610: Definition:
2611: The number of seconds since this route was last updated
2612: or otherwise determined to be correct. Note that no
2613: semantics of "too old" can be implied except through
2614: knowledge of the routing protocol by which the route was
2615: learned.
2616:
2617: Access:
2618: read-write.
2619:
2620: Status:
2621: mandatory.
2622:
2623:
2624: OBJECT:
2625: -------
2626: ipRouteMask { ipRouteEntry 11 }
2627:
2628: Syntax:
2629: IpAddress
2630:
2631:
2632:
2633:
2634: IETF SNMP Working Group [Page 47]
2635:
2636: RFC 1158 MIB II May 1990
2637:
2638:
2639: Definition:
2640: Indicate the mask to be logical-ANDed with the
2641: destination address before being compared to the value in
2642: the ipRouteDest field. For those systems that do not
2643: support arbitrary subnet masks, an agent constructs the
2644: value of the ipRouteMask by determining whether the value
2645: of the correspondent ipRouteDest field belong to a
2646: class-A, B, or C network, and then using one of:
2647:
2648: mask network
2649: 255.0.0.0 class-A
2650: 255.255.0.0 class-B
2651: 255.255.255.0 class-C
2652:
2653: If the value of the ipRouteDest is 0.0.0.0 (a default
2654: route), then the mask value is also 0.0.0.0. It should
2655: be noted that all IP routing subsystems implicitly use
2656: this mechanism.
2657:
2658: Access:
2659: read-write.
2660:
2661: Status:
2662: mandatory.
2663:
2664: 5.4.3. The IP Address Translation table
2665:
2666: The Address Translation tables contain the IpAddress to "physical"
2667: address equivalences. Some interfaces do not use translation tables
2668: for determining address equivalences (e.g., DDN-X.25 has an
2669: algorithmic method); if all interfaces are of this type, then the
2670: Address Translation table is empty, i.e., has zero entries.
2671:
2672:
2673: OBJECT:
2674: -------
2675: ipNetToMediaTable { ip 22 }
2676:
2677: Syntax:
2678: SEQUENCE OF IpNetToMediaEntry
2679:
2680: Definition:
2681: The IP Address Translation table used for mapping from IP
2682: addresses to physical addresses.
2683:
2684: Access:
2685: read-write.
2686:
2687:
2688:
2689:
2690: IETF SNMP Working Group [Page 48]
2691:
2692: RFC 1158 MIB II May 1990
2693:
2694:
2695: Status:
2696: mandatory.
2697:
2698:
2699: OBJECT:
2700: -------
2701: IpNetToMediaEntry { ipNetToMediaTable 1 }
2702:
2703: Syntax:
2704: IpNetToMediaEntry ::= SEQUENCE {
2705: ipNetToMediaIfIndex
2706: INTEGER,
2707: ipNetToMediaPhysAddress
2708: OCTET STRING,
2709: ipNetToMediaNetAddress
2710: IpAddress,
2711: ipNetToMediaType
2712: INTEGER
2713: }
2714:
2715: Definition:
2716: Each entry contains one IpAddress to "physical" address
2717: equivalence.
2718:
2719: Access:
2720: read-write.
2721:
2722: Status:
2723: mandatory.
2724:
2725: We now consider the individual components of each IP Address
2726: Translation table entry:
2727:
2728:
2729: OBJECT:
2730: -------
2731: ipNetToMediaIfIndex { ipNetToMediaEntry 1 }
2732:
2733: Syntax:
2734: INTEGER
2735:
2736: Definition:
2737: The interface on which this entry's equivalence is
2738: effective. The interface identified by a particular
2739: value of this index is the same interface as identified
2740: by the same value of ifIndex.
2741:
2742:
2743:
2744:
2745:
2746: IETF SNMP Working Group [Page 49]
2747:
2748: RFC 1158 MIB II May 1990
2749:
2750:
2751: Access:
2752: read-write.
2753:
2754: Status:
2755: mandatory.
2756:
2757:
2758: OBJECT:
2759: -------
2760: ipNetToMediaPhysAddress { ipNetToMediaEntry 2 }
2761:
2762: Syntax:
2763: OCTET STRING
2764:
2765: Definition:
2766: The media-dependent "physical" address.
2767:
2768: Access:
2769: read-write.
2770:
2771: Status:
2772: mandatory.
2773:
2774:
2775: OBJECT:
2776: -------
2777: ipNetToMediaNetAddress { ipNetToMediaEntry 3 }
2778:
2779: Syntax:
2780: IpAddress
2781:
2782: Definition:
2783: The IpAddress corresponding to the media-dependent
2784: "physical" address.
2785:
2786: Access:
2787: read-write.
2788:
2789: Status:
2790: mandatory.
2791:
2792:
2793: OBJECT:
2794: -------
2795: ipNetToMediaType { ipNetToMediaEntry 4 }
2796:
2797: Syntax:
2798: INTEGER {
2799:
2800:
2801:
2802: IETF SNMP Working Group [Page 50]
2803:
2804: RFC 1158 MIB II May 1990
2805:
2806:
2807: other(1), -- none of the following
2808:
2809: invalid(2), -- an invalidated mapping
2810:
2811: dynamic(3),
2812:
2813: static(4)
2814: }
2815:
2816: Definition:
2817: The type of mapping.
2818:
2819: Setting this object to the value invalid(2) has the effect of
2820: invalidating the corresponding entry in the ipNetToMediaTable.
2821: That is, it effectively disassociates the interface identified
2822: with said entry from the mapping identified with said entry.
2823: It is an implementation-specific matter as to whether the
2824: agent removes an invalidated entry from the table.
2825: Accordingly, management stations must be prepared to receive
2826: tabular information from agents that corresponds to entries
2827: not currently in use. Proper interpretation of such entries
2828: requires examination of the relevant ipNetToMediaType object.
2829:
2830: Access:
2831: read-write.
2832:
2833: Status:
2834: mandatory.
2835:
2836: 5.5. The ICMP Group
2837:
2838: Implementation of the ICMP group is mandatory for all systems.
2839:
2840: The ICMP group contains the ICMP input and output statistics.
2841:
2842:
2843: OBJECT:
2844: -------
2845: icmpInMsgs { icmp 1 }
2846:
2847: Syntax:
2848: Counter
2849:
2850: Definition:
2851: The total number of ICMP messages which the entity
2852: received. Note that this counter includes all those
2853: counted by icmpInErrors.
2854:
2855:
2856:
2857:
2858: IETF SNMP Working Group [Page 51]
2859:
2860: RFC 1158 MIB II May 1990
2861:
2862:
2863: Access:
2864: read-only.
2865:
2866: Status:
2867: mandatory.
2868:
2869:
2870: OBJECT:
2871: -------
2872: icmpInErrors { icmp 2 }
2873:
2874: Syntax:
2875: Counter
2876:
2877: Definition:
2878: The number of ICMP messages which the entity received but
2879: determined as having ICMP-specific errors (bad ICMP
2880: checksums, bad length, etc.).
2881:
2882: Access:
2883: read-only.
2884:
2885: Status:
2886: mandatory.
2887:
2888:
2889: OBJECT:
2890: -------
2891: icmpInDestUnreachs { icmp 3 }
2892:
2893: Syntax:
2894: Counter
2895:
2896: Definition:
2897: The number of ICMP Destination Unreachable messages
2898: received.
2899:
2900: Access:
2901: read-only.
2902:
2903: Status:
2904: mandatory.
2905:
2906:
2907: OBJECT:
2908: -------
2909: icmpInTimeExcds { icmp 4 }
2910:
2911:
2912:
2913:
2914: IETF SNMP Working Group [Page 52]
2915:
2916: RFC 1158 MIB II May 1990
2917:
2918:
2919: Syntax:
2920: Counter
2921:
2922: Definition:
2923: The number of ICMP Time Exceeded messages received.
2924:
2925: Access:
2926: read-only.
2927:
2928: Status:
2929: mandatory.
2930:
2931:
2932: OBJECT:
2933: -------
2934: icmpInParmProbs { icmp 5 }
2935:
2936: Syntax:
2937: Counter
2938:
2939: Definition:
2940: The number of ICMP Parameter Problem messages received.
2941:
2942: Access:
2943: read-only.
2944:
2945: Status:
2946: mandatory.
2947:
2948:
2949: OBJECT:
2950: -------
2951: icmpInSrcQuenchs { icmp 6 }
2952:
2953: Syntax:
2954: Counter
2955:
2956: Definition:
2957: The number of ICMP Source Quench messages received.
2958:
2959: Access:
2960: read-only.
2961:
2962: Status:
2963: mandatory.
2964:
2965:
2966:
2967:
2968:
2969:
2970: IETF SNMP Working Group [Page 53]
2971:
2972: RFC 1158 MIB II May 1990
2973:
2974:
2975: OBJECT:
2976: -------
2977: icmpInRedirects { icmp 7 }
2978:
2979: Syntax:
2980: Counter
2981:
2982: Definition:
2983: The number of ICMP Redirect messages received.
2984:
2985: Access:
2986: read-only.
2987:
2988: Status:
2989: mandatory.
2990:
2991:
2992: OBJECT:
2993: -------
2994: icmpInEchos { icmp 8 }
2995:
2996: Syntax:
2997: Counter
2998:
2999: Definition:
3000: The number of ICMP Echo (request) messages received.
3001:
3002: Access:
3003: read-only.
3004:
3005: Status:
3006: mandatory.
3007:
3008:
3009: OBJECT:
3010: -------
3011: icmpInEchoReps { icmp 9 }
3012:
3013: Syntax:
3014: Counter
3015:
3016: Definition:
3017: The number of ICMP Echo Reply messages received.
3018:
3019: Access:
3020: read-only.
3021:
3022:
3023:
3024:
3025:
3026: IETF SNMP Working Group [Page 54]
3027:
3028: RFC 1158 MIB II May 1990
3029:
3030:
3031: Status:
3032: mandatory.
3033:
3034:
3035: OBJECT:
3036: -------
3037: icmpInTimestamps { icmp 10 }
3038:
3039: Syntax:
3040: Counter
3041:
3042: Definition:
3043: The number of ICMP Timestamp (request) messages received.
3044:
3045: Access:
3046: read-only.
3047:
3048: Status:
3049: mandatory.
3050:
3051:
3052: OBJECT:
3053: -------
3054: icmpInTimestampReps { icmp 11 }
3055:
3056: Syntax:
3057: Counter
3058:
3059: Definition:
3060: The number of ICMP Timestamp Reply messages received.
3061:
3062: Access:
3063: read-only.
3064:
3065: Status:
3066: mandatory.
3067:
3068:
3069: OBJECT:
3070: -------
3071: icmpInAddrMasks { icmp 12 }
3072:
3073: Syntax:
3074: Counter
3075:
3076: Definition:
3077: The number of ICMP Address Mask Request messages
3078: received.
3079:
3080:
3081:
3082: IETF SNMP Working Group [Page 55]
3083:
3084: RFC 1158 MIB II May 1990
3085:
3086:
3087: Access:
3088: read-only.
3089:
3090: Status:
3091: mandatory.
3092:
3093:
3094: OBJECT:
3095: -------
3096: icmpInAddrMaskReps { icmp 13 }
3097:
3098: Syntax:
3099: Counter
3100:
3101: Definition:
3102: The number of ICMP Address Mask Reply messages received.
3103:
3104: Access:
3105: read-only.
3106:
3107: Status:
3108: mandatory.
3109:
3110:
3111: OBJECT:
3112: -------
3113: icmpOutMsgs { icmp 14 }
3114:
3115: Syntax:
3116: Counter
3117:
3118: Definition:
3119: The total number of ICMP messages which this entity
3120: attempted to send. Note that this counter includes all
3121: those counted by icmpOutErrors.
3122:
3123: Access:
3124: read-only.
3125:
3126: Status:
3127: mandatory.
3128:
3129:
3130: OBJECT:
3131: -------
3132: icmpOutErrors { icmp 15 }
3133:
3134:
3135:
3136:
3137:
3138: IETF SNMP Working Group [Page 56]
3139:
3140: RFC 1158 MIB II May 1990
3141:
3142:
3143: Syntax:
3144: Counter
3145:
3146: Definition:
3147: The number of ICMP messages which this entity did not
3148: send due to problems discovered within ICMP such as a
3149: lack of buffers. This value should not include errors
3150: discovered outside the ICMP layer such as the inability
3151: of IP to route the resultant datagram. In some
3152: implementations there may be no types of error which
3153: contribute to this counter's value.
3154:
3155: Access:
3156: read-only.
3157:
3158: Status:
3159: mandatory.
3160:
3161:
3162: OBJECT:
3163: -------
3164: icmpOutDestUnreachs { icmp 16 }
3165:
3166: Syntax:
3167: Counter
3168:
3169: Definition:
3170: The number of ICMP Destination Unreachable messages sent.
3171:
3172: Access:
3173: read-only.
3174:
3175: Status:
3176: mandatory.
3177:
3178:
3179: OBJECT:
3180: -------
3181: icmpOutTimeExcds { icmp 17 }
3182:
3183: Syntax:
3184: Counter
3185:
3186: Definition:
3187: The number of ICMP Time Exceeded messages sent.
3188:
3189: Access:
3190: read-only.
3191:
3192:
3193:
3194: IETF SNMP Working Group [Page 57]
3195:
3196: RFC 1158 MIB II May 1990
3197:
3198:
3199: Status:
3200: mandatory.
3201:
3202:
3203: OBJECT:
3204: -------
3205: icmpOutParmProbs { icmp 18 }
3206:
3207: Syntax:
3208: Counter
3209:
3210: Definition:
3211: The number of ICMP Parameter Problem messages sent.
3212:
3213: Access:
3214: read-only.
3215:
3216: Status:
3217: mandatory.
3218:
3219:
3220: OBJECT:
3221: -------
3222: icmpOutSrcQuenchs { icmp 19 }
3223:
3224: Syntax:
3225: Counter
3226:
3227: Definition:
3228: The number of ICMP Source Quench messages sent.
3229:
3230: Access:
3231: read-only.
3232:
3233: Status:
3234: mandatory.
3235:
3236:
3237: OBJECT:
3238: -------
3239: icmpOutRedirects { icmp 20 }
3240:
3241: Syntax:
3242: Counter
3243:
3244: Definition:
3245: The number of ICMP Redirect messages sent. For a host,
3246: this object will always be zero, since hosts do not send
3247:
3248:
3249:
3250: IETF SNMP Working Group [Page 58]
3251:
3252: RFC 1158 MIB II May 1990
3253:
3254:
3255: redirects.
3256:
3257: Access:
3258: read-only.
3259:
3260: Status:
3261: mandatory.
3262:
3263:
3264: OBJECT:
3265: -------
3266: icmpOutEchos { icmp 21 }
3267:
3268: Syntax:
3269: Counter
3270:
3271: Definition:
3272: The number of ICMP Echo (request) messages sent.
3273:
3274: Access:
3275: read-only.
3276:
3277: Status:
3278: mandatory.
3279:
3280:
3281: OBJECT:
3282: -------
3283: icmpOutEchoReps { icmp 22 }
3284:
3285: Syntax:
3286: Counter
3287:
3288: Definition:
3289: The number of ICMP Echo Reply messages sent.
3290:
3291: Access:
3292: read-only.
3293:
3294: Status:
3295: mandatory.
3296:
3297:
3298: OBJECT:
3299: -------
3300: icmpOutTimestamps { icmp 23 }
3301:
3302:
3303:
3304:
3305:
3306: IETF SNMP Working Group [Page 59]
3307:
3308: RFC 1158 MIB II May 1990
3309:
3310:
3311: Syntax:
3312: Counter
3313:
3314: Definition:
3315: The number of ICMP Timestamp (request) messages sent.
3316:
3317: Access:
3318: read-only.
3319:
3320: Status:
3321: mandatory.
3322:
3323:
3324: OBJECT:
3325: -------
3326: icmpOutTimestampReps { icmp 24 }
3327:
3328: Syntax:
3329: Counter
3330:
3331: Definition:
3332: The number of ICMP Timestamp Reply messages sent.
3333:
3334: Access:
3335: read-only.
3336:
3337: Status:
3338: mandatory.
3339:
3340:
3341: OBJECT:
3342: -------
3343: icmpOutAddrMasks { icmp 25 }
3344:
3345: Syntax:
3346: Counter
3347:
3348: Definition:
3349: The number of ICMP Address Mask Request messages sent.
3350:
3351: Access:
3352: read-only.
3353:
3354: Status:
3355: mandatory.
3356:
3357:
3358:
3359:
3360:
3361:
3362: IETF SNMP Working Group [Page 60]
3363:
3364: RFC 1158 MIB II May 1990
3365:
3366:
3367: OBJECT:
3368: -------
3369: icmpOutAddrMaskReps { icmp 26 }
3370:
3371: Syntax:
3372: Counter
3373:
3374: Definition:
3375: The number of ICMP Address Mask Reply messages sent.
3376:
3377: Access:
3378: read-only.
3379:
3380: Status:
3381: mandatory.
3382:
3383: 5.6. The TCP Group
3384:
3385: Implementation of the TCP group is mandatory for all systems that
3386: implement the TCP.
3387:
3388: Note that instances of object types that represent information about
3389: a particular TCP connection are transient; they persist only as long
3390: as the connection in question.
3391:
3392:
3393: OBJECT:
3394: -------
3395: tcpRtoAlgorithm { tcp 1 }
3396:
3397: Syntax:
3398: INTEGER {
3399: other(1), -- none of the following
3400: constant(2), -- a constant rto
3401: rsre(3), -- MIL-STD-1778, Appendix B
3402: vanj(4) -- Van Jacobson's algorithm [11]
3403: }
3404:
3405: Definition:
3406: The algorithm used to determine the timeout value used
3407: for retransmitting unacknowledged octets.
3408:
3409: Access:
3410: read-only.
3411:
3412: Status:
3413: mandatory.
3414:
3415:
3416:
3417:
3418: IETF SNMP Working Group [Page 61]
3419:
3420: RFC 1158 MIB II May 1990
3421:
3422:
3423: OBJECT:
3424: -------
3425: tcpRtoMin { tcp 2 }
3426:
3427: Syntax:
3428: INTEGER
3429:
3430: Definition:
3431: The minimum value permitted by a TCP implementation for
3432: the retransmission timeout, measured in milliseconds.
3433: More refined semantics for objects of this type depend
3434: upon the algorithm used to determine the retransmission
3435: timeout. In particular, when the timeout algorithm is
3436: rsre(3), an object of this type has the semantics of the
3437: LBOUND quantity described in RFC 793.
3438:
3439: Access:
3440: read-only.
3441:
3442: Status:
3443: mandatory.
3444:
3445:
3446: OBJECT:
3447: -------
3448: tcpRtoMax { tcp 3 }
3449:
3450: Syntax:
3451: INTEGER
3452:
3453: Definition:
3454: The maximum value permitted by a TCP implementation for
3455: the retransmission timeout, measured in milliseconds.
3456: More refined semantics for objects of this type depend
3457: upon the algorithm used to determine the retransmission
3458: timeout. In particular, when the timeout algorithm is
3459: rsre(3), an object of this type has the semantics of the
3460: UBOUND quantity described in RFC 793.
3461:
3462: Access:
3463: read-only.
3464:
3465: Status:
3466: mandatory.
3467:
3468:
3469:
3470:
3471:
3472:
3473:
3474: IETF SNMP Working Group [Page 62]
3475:
3476: RFC 1158 MIB II May 1990
3477:
3478:
3479: OBJECT:
3480: -------
3481: tcpMaxConn { tcp 4 }
3482:
3483: Syntax:
3484: INTEGER
3485:
3486: Definition:
3487: The limit on the total number of TCP connections the
3488: entity can support. In entities where the maximum number
3489: of connections is dynamic, this object should contain the
3490: value "-1".
3491:
3492: Access:
3493: read-only.
3494:
3495: Status:
3496: mandatory.
3497:
3498:
3499: OBJECT:
3500: -------
3501: tcpActiveOpens { tcp 5 }
3502:
3503: Syntax:
3504: Counter
3505:
3506: Definition:
3507: The number of times TCP connections have made a direct
3508: transition to the SYN-SENT state from the CLOSED state.
3509:
3510: Access:
3511: read-only.
3512:
3513: Status:
3514: mandatory.
3515:
3516:
3517: OBJECT:
3518: -------
3519: tcpPassiveOpens { tcp 6 }
3520:
3521: Syntax:
3522: Counter
3523:
3524: Definition:
3525: The number of times TCP connections have made a direct
3526: transition to the SYN-RCVD state from the LISTEN state.
3527:
3528:
3529:
3530: IETF SNMP Working Group [Page 63]
3531:
3532: RFC 1158 MIB II May 1990
3533:
3534:
3535: Access:
3536: read-only.
3537:
3538: Status:
3539: mandatory.
3540:
3541:
3542: OBJECT:
3543: -------
3544: tcpAttemptFails { tcp 7 }
3545:
3546: Syntax:
3547: Counter
3548:
3549: Definition:
3550: The number of times TCP connections have made a direct
3551: transition to the CLOSED state from either the SYN-SENT
3552: state or the SYN-RCVD state, plus the number of times TCP
3553: connections have made a direct transition to the LISTEN
3554: state from the SYN-RCVD state.
3555:
3556: Access:
3557: read-only.
3558:
3559: Status:
3560: mandatory.
3561:
3562:
3563: OBJECT:
3564: -------
3565: tcpEstabResets { tcp 8 }
3566:
3567: Syntax:
3568: Counter
3569:
3570: Definition:
3571: The number of times TCP connections have made a direct
3572: transition to the CLOSED state from either the
3573: ESTABLISHED state or the CLOSE-WAIT state.
3574:
3575: Access:
3576: read-only.
3577:
3578: Status:
3579: mandatory.
3580:
3581:
3582:
3583:
3584:
3585:
3586: IETF SNMP Working Group [Page 64]
3587:
3588: RFC 1158 MIB II May 1990
3589:
3590:
3591: OBJECT:
3592: -------
3593: tcpCurrEstab { tcp 9 }
3594:
3595: Syntax:
3596: Gauge
3597:
3598: Definition:
3599: The number of TCP connections for which the current state
3600: is either ESTABLISHED or CLOSE-WAIT.
3601:
3602: Access:
3603: read-only.
3604:
3605: Status:
3606: mandatory.
3607:
3608:
3609: OBJECT:
3610: -------
3611: tcpInSegs { tcp 10 }
3612:
3613: Syntax:
3614: Counter
3615:
3616: Definition:
3617: The total number of segments received, including those
3618: received in error. This count includes segments received
3619: on currently established connections.
3620:
3621: Access:
3622: read-only.
3623:
3624: Status:
3625: mandatory.
3626:
3627:
3628: OBJECT:
3629: -------
3630: tcpOutSegs { tcp 11 }
3631:
3632: Syntax:
3633: Counter
3634:
3635: Definition:
3636: The total number of segments sent, including those on
3637: current connections but excluding those containing only
3638: retransmitted octets.
3639:
3640:
3641:
3642: IETF SNMP Working Group [Page 65]
3643:
3644: RFC 1158 MIB II May 1990
3645:
3646:
3647: Access:
3648: read-only.
3649:
3650: Status:
3651: mandatory.
3652:
3653:
3654: OBJECT:
3655: -------
3656: tcpRetransSegs { tcp 12 }
3657:
3658: Syntax:
3659: Counter
3660:
3661: Definition:
3662: The total number of segments retransmitted - that is, the
3663: number of TCP segments transmitted containing one or more
3664: previously transmitted octets.
3665:
3666: Access:
3667: read-only.
3668:
3669: Status:
3670: mandatory.
3671:
3672: 5.6.1. The TCP Connection table
3673:
3674: The TCP connection table contains information about this entity's
3675: existing TCP connections.
3676:
3677:
3678: OBJECT:
3679: -------
3680: tcpConnTable { tcp 13 }
3681:
3682: Syntax:
3683: SEQUENCE OF TcpConnEntry
3684:
3685: Definition:
3686: A table containing TCP connection-specific information.
3687:
3688: Access:
3689: read-only.
3690:
3691: Status:
3692: mandatory.
3693:
3694:
3695:
3696:
3697:
3698: IETF SNMP Working Group [Page 66]
3699:
3700: RFC 1158 MIB II May 1990
3701:
3702:
3703: OBJECT:
3704: -------
3705: tcpConnEntry { tcpConnTable 1 }
3706:
3707: Syntax:
3708: TcpConnEntry ::= SEQUENCE {
3709: tcpConnState
3710: INTEGER,
3711: tcpConnLocalAddress
3712: IpAddress,
3713: tcpConnLocalPort
3714: INTEGER (0..65535),
3715: tcpConnRemAddress
3716: IpAddress,
3717: tcpConnRemPort
3718: INTEGER (0..65535)
3719: }
3720:
3721: Definition:
3722: Information about a particular current TCP connection.
3723: An object of this type is transient, in that it ceases to
3724: exist when (or soon after) the connection makes the
3725: transition to the CLOSED state.
3726:
3727: Access:
3728: read-only.
3729:
3730: Status:
3731: mandatory.
3732:
3733:
3734: OBJECT:
3735: -------
3736: tcpConnState { tcpConnEntry 1 }
3737:
3738: Syntax:
3739: INTEGER {
3740: closed(1),
3741: listen(2),
3742: synSent(3),
3743: synReceived(4),
3744: established(5),
3745: finWait1(6),
3746: finWait2(7),
3747: closeWait(8),
3748: lastAck(9),
3749: closing(10),
3750: timeWait(11)
3751:
3752:
3753:
3754: IETF SNMP Working Group [Page 67]
3755:
3756: RFC 1158 MIB II May 1990
3757:
3758:
3759: }
3760:
3761: Definition:
3762: The state of this TCP connection.
3763:
3764: Access:
3765: read-only.
3766:
3767: Status:
3768: mandatory.
3769:
3770:
3771: OBJECT:
3772: -------
3773: tcpConnLocalAddress { tcpConnEntry 2 }
3774:
3775: Syntax:
3776: IpAddress
3777:
3778: Definition:
3779: The local IP address for this TCP connection. In the
3780: case of a connection in the listen state which is willing
3781: to accept connections for any IP interface associated
3782: with the node, the value 0.0.0.0 is used.
3783:
3784: Access:
3785: read-only.
3786:
3787: Status:
3788: mandatory.
3789:
3790:
3791: OBJECT:
3792: -------
3793: tcpConnLocalPort { tcpConnEntry 3 }
3794:
3795: Syntax:
3796: INTEGER (0..65535)
3797:
3798: Definition:
3799: The local port number for this TCP connection.
3800:
3801: Access:
3802: read-only.
3803:
3804: Status:
3805: mandatory.
3806:
3807:
3808:
3809:
3810: IETF SNMP Working Group [Page 68]
3811:
3812: RFC 1158 MIB II May 1990
3813:
3814:
3815: OBJECT:
3816: -------
3817: tcpConnRemAddress { tcpConnEntry 4 }
3818:
3819: Syntax:
3820: IpAddress
3821:
3822: Definition:
3823: The remote IP address for this TCP connection.
3824:
3825: Access:
3826: read-only.
3827:
3828: Status:
3829: mandatory.
3830:
3831:
3832: OBJECT:
3833: -------
3834: tcpConnRemPort { tcpConnEntry 5 }
3835:
3836: Syntax:
3837: INTEGER (0..65535)
3838:
3839: Definition:
3840: The remote port number for this TCP connection.
3841:
3842: Access:
3843: read-only.
3844:
3845: Status:
3846: mandatory.
3847:
3848: 5.6.2. Additional TCP Objects
3849:
3850:
3851: OBJECT:
3852: -------
3853: tcpInErrs { tcp 14 }
3854:
3855: Syntax:
3856: Counter
3857:
3858: Definition:
3859: The total number of segments received in error (e.g., bad
3860: TCP checksums).
3861:
3862:
3863:
3864:
3865:
3866: IETF SNMP Working Group [Page 69]
3867:
3868: RFC 1158 MIB II May 1990
3869:
3870:
3871: Access:
3872: read-only.
3873:
3874: Status:
3875: mandatory.
3876:
3877:
3878: OBJECT:
3879: -------
3880: tcpOutRsts { tcp 15 }
3881:
3882: Syntax:
3883: Counter
3884:
3885: Definition:
3886: The number of TCP segments sent containing the RST flag.
3887:
3888: Access:
3889: read-only.
3890:
3891: Status:
3892: mandatory.
3893:
3894: 5.7. The UDP Group
3895:
3896: Implementation of the UDP group is mandatory for all systems which
3897: implement the UDP.
3898:
3899:
3900: OBJECT:
3901: -------
3902: udpInDatagrams { udp 1 }
3903:
3904: Syntax:
3905: Counter
3906:
3907: Definition:
3908: The total number of UDP datagrams delivered to UDP users.
3909:
3910: Access:
3911: read-only.
3912:
3913: Status:
3914: mandatory.
3915:
3916:
3917:
3918:
3919:
3920:
3921:
3922: IETF SNMP Working Group [Page 70]
3923:
3924: RFC 1158 MIB II May 1990
3925:
3926:
3927: OBJECT:
3928: -------
3929: udpNoPorts { udp 2 }
3930:
3931: Syntax:
3932: Counter
3933:
3934: Definition:
3935: The total number of received UDP datagrams for which
3936: there was no application at the destination port.
3937:
3938: Access:
3939: read-only.
3940:
3941: Status:
3942: mandatory.
3943:
3944:
3945: OBJECT:
3946: -------
3947: udpInErrors { udp 3 }
3948:
3949: Syntax:
3950: Counter
3951:
3952: Definition:
3953: The number of received UDP datagrams that could not be
3954: delivered for reasons other than the lack of an
3955: application at the destination port.
3956:
3957: Access:
3958: read-only.
3959:
3960: Status:
3961: mandatory.
3962:
3963:
3964: OBJECT:
3965: -------
3966: udpOutDatagrams { udp 4 }
3967:
3968: Syntax:
3969: Counter
3970:
3971: Definition:
3972: The total number of UDP datagrams sent from this entity.
3973:
3974:
3975:
3976:
3977:
3978: IETF SNMP Working Group [Page 71]
3979:
3980: RFC 1158 MIB II May 1990
3981:
3982:
3983: Access:
3984: read-only.
3985:
3986: Status:
3987: mandatory.
3988:
3989: 5.7.1. The UDP Listener table
3990:
3991: The UDP listener table contains information about this entity's UDP
3992: end-points on which a local application is currently accepting
3993: datagrams.
3994:
3995:
3996: OBJECT:
3997: -------
3998: udpTable { udp 5 }
3999:
4000: Syntax:
4001: SEQUENCE OF UdpEntry
4002:
4003: Definition:
4004: A table containing UDP listener information.
4005:
4006: Access:
4007: read-only.
4008:
4009: Status:
4010: mandatory.
4011:
4012:
4013: OBJECT:
4014: -------
4015: udpEntry { udpTable 1 }
4016:
4017: Syntax:
4018: UdpEntry ::= SEQUENCE {
4019: udpLocalAddress
4020: IpAddress,
4021: udpLocalPort
4022: INTEGER (0..65535)
4023: }
4024:
4025: Definition:
4026: Information about a particular current UDP listener.
4027:
4028: Access:
4029: read-only.
4030:
4031:
4032:
4033:
4034: IETF SNMP Working Group [Page 72]
4035:
4036: RFC 1158 MIB II May 1990
4037:
4038:
4039: Status:
4040: mandatory.
4041:
4042:
4043: OBJECT:
4044: -------
4045: udpLocalAddress { udpEntry 1 }
4046:
4047: Syntax:
4048: IpAddress
4049:
4050: Definition:
4051: The local IP address for this UDP listener. In the case
4052: of a UDP listener which is willing to accept datagrams
4053: for any IP interface associated with the node, the value
4054: 0.0.0.0 is used.
4055:
4056: Access:
4057: read-only.
4058:
4059: Status:
4060: mandatory.
4061:
4062:
4063: OBJECT:
4064: -------
4065: udpLocalPort { udpEntry 2 }
4066:
4067: Syntax:
4068: INTEGER (0..65535)
4069:
4070: Definition:
4071: The local port number for this UDP listener.
4072:
4073: Access:
4074: read-only.
4075:
4076: Status:
4077: mandatory.
4078:
4079: 5.8. The EGP Group
4080:
4081: Implementation of the EGP group is mandatory for all systems which
4082: implement the EGP.
4083:
4084:
4085:
4086:
4087:
4088:
4089:
4090: IETF SNMP Working Group [Page 73]
4091:
4092: RFC 1158 MIB II May 1990
4093:
4094:
4095: OBJECT:
4096: -------
4097: egpInMsgs { egp 1 }
4098:
4099: Syntax:
4100: Counter
4101:
4102: Definition:
4103: The number of EGP messages received without error.
4104:
4105: Access:
4106: read-only.
4107:
4108: Status:
4109: mandatory.
4110:
4111:
4112: OBJECT:
4113: -------
4114: egpInErrors { egp 2 }
4115:
4116: Syntax:
4117: Counter
4118:
4119: Definition:
4120: The number of EGP messages received that proved to be in
4121: error.
4122:
4123: Access:
4124: read-only.
4125:
4126: Status:
4127: mandatory.
4128:
4129:
4130: OBJECT:
4131: -------
4132: egpOutMsgs { egp 3 }
4133:
4134: Syntax:
4135: Counter
4136:
4137: Definition:
4138: The total number of locally generated EGP messages.
4139:
4140: Access:
4141: read-only.
4142:
4143:
4144:
4145:
4146: IETF SNMP Working Group [Page 74]
4147:
4148: RFC 1158 MIB II May 1990
4149:
4150:
4151: Status:
4152: mandatory.
4153:
4154:
4155: OBJECT:
4156: -------
4157: egpOutErrors { egp 4 }
4158:
4159: Syntax:
4160: Counter
4161:
4162: Definition:
4163: The number of locally generated EGP messages not sent due
4164: to resource limitations within an EGP entity.
4165:
4166: Access:
4167: read-only.
4168:
4169: Status:
4170: mandatory.
4171:
4172: 5.8.1. The EGP Neighbor table
4173:
4174: The Egp Neighbor table contains information about this entity's EGP
4175: neighbors.
4176:
4177:
4178: OBJECT:
4179: -------
4180: egpNeighTable { egp 5 }
4181:
4182: Syntax:
4183: SEQUENCE OF EgpNeighEntry
4184:
4185: Definition:
4186: The EGP neighbor table.
4187:
4188: Access:
4189: read-only.
4190:
4191: Status:
4192: mandatory.
4193:
4194:
4195: OBJECT:
4196: -------
4197: egpNeighEntry { egpNeighTable 1 }
4198:
4199:
4200:
4201:
4202: IETF SNMP Working Group [Page 75]
4203:
4204: RFC 1158 MIB II May 1990
4205:
4206:
4207: Syntax:
4208: EgpNeighEntry ::= SEQUENCE {
4209: egpNeighState
4210: INTEGER,
4211: egpNeighAddr
4212: IpAddress,
4213: egpNeighAs
4214: INTEGER,
4215: egpNeighInMsgs
4216: Counter,
4217: egpNeighInErrs
4218: Counter,
4219: egpNeighOutMsgs
4220: Counter,
4221: egpNeighOutErrs
4222: Counter,
4223: egpNeighInErrMsgs
4224: Counter,
4225: egpNeighOutErrMsgs
4226: Counter,
4227: egpNeighStateUps
4228: Counter,
4229: egpNeighStateDowns
4230: Counter,
4231: egpNeighIntervalHello
4232: INTEGER,
4233: egpNeighIntervalPoll
4234: INTEGER,
4235: egpNeighMode
4236: INTEGER,
4237: egpNeighEventTrigger
4238: INTEGER
4239: }
4240:
4241: Definition:
4242: Information about this entity's relationship with a
4243: particular EGP neighbor.
4244:
4245: Access:
4246: read-only.
4247:
4248: Status:
4249: mandatory.
4250:
4251:
4252: We now consider the individual components of each EGP neighbor
4253: entry:
4254:
4255:
4256:
4257:
4258: IETF SNMP Working Group [Page 76]
4259:
4260: RFC 1158 MIB II May 1990
4261:
4262:
4263: OBJECT:
4264: -------
4265: egpNeighState { egpNeighEntry 1 }
4266:
4267: Syntax:
4268: INTEGER {
4269: idle(1),
4270: acquisition(2),
4271: down(3),
4272: up(4),
4273: cease(5)
4274: }
4275:
4276: Definition:
4277: The EGP state of the local system with respect to this
4278: entry's EGP neighbor. Each EGP state is represented by a
4279: value that is one greater than the numerical value
4280: associated with said state in RFC 904.
4281:
4282: Access:
4283: read-only.
4284:
4285: Status:
4286: mandatory.
4287:
4288:
4289: OBJECT:
4290: -------
4291: egpNeighAddr { egpNeighEntry 2 }
4292:
4293: Syntax:
4294: IpAddress
4295:
4296: Definition:
4297: The IP address of this entry's EGP neighbor.
4298:
4299: Access:
4300: read-only.
4301:
4302: Status:
4303: mandatory.
4304:
4305:
4306: OBJECT:
4307: -------
4308: egpNeighAs { egpNeighEntry 3 }
4309:
4310:
4311:
4312:
4313:
4314: IETF SNMP Working Group [Page 77]
4315:
4316: RFC 1158 MIB II May 1990
4317:
4318:
4319: Syntax:
4320: INTEGER
4321:
4322: Definition:
4323: The autonomous system of this EGP peer. Zero should be
4324: specified if the autonomous system number of the neighbor
4325: is not yet known.
4326:
4327: Access:
4328: read-only.
4329:
4330: Status:
4331: mandatory.
4332:
4333:
4334: OBJECT:
4335: -------
4336: egpNeighInMsgs { egpNeighEntry 4 }
4337:
4338: Syntax:
4339: Counter
4340:
4341: Definition:
4342: The number of EGP messages received without error from
4343: this EGP peer.
4344:
4345: Access:
4346: read-only.
4347:
4348: Status:
4349: mandatory.
4350:
4351:
4352: OBJECT:
4353: -------
4354: egpNeighInErrs { egpNeighEntry 5 }
4355:
4356: Syntax:
4357: Counter
4358:
4359: Definition:
4360: The number of EGP messages received from this EGP peer
4361: that proved to be in error (e.g., bad EGP checksum).
4362:
4363: Access:
4364: read-only.
4365:
4366:
4367:
4368:
4369:
4370: IETF SNMP Working Group [Page 78]
4371:
4372: RFC 1158 MIB II May 1990
4373:
4374:
4375: Status:
4376: mandatory.
4377:
4378:
4379: OBJECT:
4380: -------
4381: egpNeighOutMsgs { egpNeighEntry 6 }
4382:
4383: Syntax:
4384: Counter
4385:
4386: Definition:
4387: The number of locally generated EGP messages to this EGP
4388: peer.
4389:
4390: Access:
4391: read-only.
4392:
4393: Status:
4394: mandatory.
4395:
4396:
4397: OBJECT:
4398: -------
4399: egpNeighOutErrs { egpNeighEntry 7 }
4400:
4401: Syntax:
4402: Counter
4403:
4404: Definition:
4405: The number of locally generated EGP messages not sent to
4406: this EGP peer due to resource limitations within an EGP
4407: entity.
4408:
4409: Access:
4410: read-only.
4411:
4412: Status:
4413: mandatory.
4414:
4415:
4416: OBJECT:
4417: -------
4418: egpNeighInErrMsgs { egpNeighEntry 8 }
4419:
4420: Syntax:
4421: Counter
4422:
4423:
4424:
4425:
4426: IETF SNMP Working Group [Page 79]
4427:
4428: RFC 1158 MIB II May 1990
4429:
4430:
4431: Definition:
4432: The number of EGP-defined error messages received from
4433: this EGP peer.
4434:
4435: Access:
4436: read-only.
4437:
4438: Status:
4439: mandatory.
4440:
4441:
4442: OBJECT:
4443: -------
4444: egpNeighOutErrMsgs { egpNeighEntry 9 }
4445:
4446: Syntax:
4447: Counter
4448:
4449: Definition:
4450: The number of EGP-defined error messages sent to this EGP
4451: peer.
4452:
4453: Access:
4454: read-only.
4455:
4456: Status:
4457: mandatory.
4458:
4459:
4460: OBJECT:
4461: -------
4462: egpNeighStateUps { egpNeighEntry 10 }
4463:
4464: Syntax:
4465: Counter
4466:
4467: Definition:
4468: The number of EGP state transitions to the UP state with
4469: this EGP peer.
4470:
4471: Access:
4472: read-only.
4473:
4474: Status:
4475: mandatory.
4476:
4477:
4478:
4479:
4480:
4481:
4482: IETF SNMP Working Group [Page 80]
4483:
4484: RFC 1158 MIB II May 1990
4485:
4486:
4487: OBJECT:
4488: -------
4489: egpNeighStateDowns { egpNeighEntry 11 }
4490:
4491: Syntax:
4492: Counter
4493:
4494: Definition:
4495: The number of EGP state transitions from the UP state to
4496: any other state with this EGP peer.
4497:
4498: Access:
4499: read-only.
4500:
4501: Status:
4502: mandatory.
4503:
4504:
4505: OBJECT:
4506: -------
4507: egpNeighIntervalHello { egpNeighEntry 12 }
4508:
4509: Syntax:
4510: INTEGER
4511:
4512: Definition:
4513: The interval between EGP Hello command retransmissions
4514: (in hundredths of a second). This represents the t1
4515: timer as defined in RFC 904.
4516:
4517: Access:
4518: read-only.
4519:
4520: Status:
4521: mandatory.
4522:
4523:
4524: OBJECT:
4525: -------
4526: egpNeighIntervalPoll { egpNeighEntry 13 }
4527:
4528: Syntax:
4529: INTEGER
4530:
4531: Definition:
4532: The interval between EGP poll command retransmissions (in
4533: hundredths of a second). This represents the t3 timer as
4534: defined in RFC 904.
4535:
4536:
4537:
4538: IETF SNMP Working Group [Page 81]
4539:
4540: RFC 1158 MIB II May 1990
4541:
4542:
4543: Access:
4544: read-only.
4545:
4546: Status:
4547: mandatory.
4548:
4549:
4550: OBJECT:
4551: -------
4552: egpNeighMode { egpNeighEntry 14 }
4553:
4554: Syntax:
4555: INTEGER {
4556: active(1),
4557: passive(2)
4558: }
4559:
4560: Definition:
4561: The polling mode of this EGP entity, either passive or
4562: active.
4563:
4564: Access:
4565: read-only.
4566:
4567: Status:
4568: mandatory.
4569:
4570:
4571: OBJECT:
4572: -------
4573: egpNeighEventTrigger { egpNeighEntry 15 }
4574:
4575: Syntax:
4576: INTEGER {
4577: start(1),
4578: stop(2)
4579: }
4580:
4581: Definition:
4582: A control variable used to trigger operator-initiated
4583: Start and Stop events. When read, this variable always
4584: returns the most recent value that egpNeightEventTrigger
4585: was set to. If it has not been set since the last
4586: initialization of the network management subsystem on the
4587: node, it returns a value of "stop".
4588:
4589: Access:
4590: read-write
4591:
4592:
4593:
4594: IETF SNMP Working Group [Page 82]
4595:
4596: RFC 1158 MIB II May 1990
4597:
4598:
4599: Status:
4600: mandatory.
4601:
4602: 5.8.2. Additional EGP variables
4603:
4604:
4605: OBJECT:
4606: -------
4607: egpAs { egp 6 }
4608:
4609: Syntax:
4610: INTEGER
4611:
4612: Definition:
4613: The autonomous system number of this EGP entity.
4614:
4615: Access:
4616: read-only.
4617:
4618: Status:
4619: mandatory.
4620:
4621: 5.9. The Transmission Group
4622:
4623: Based on the transmission media underlying each interface on a
4624: system, the corresponding portion of the Transmission group is
4625: mandatory for that system.
4626:
4627: When Internet-standard definitions for managing transmission media
4628: are defined, the transmission group is used to provide a prefix for
4629: the names of those objects.
4630:
4631: Typically, such definitions reside in the experimental portion of the
4632: MIB until they are "proven", then as a part of the Internet
4633: standardization process, the definitions are accordingly elevated and
4634: a new object identifier, under the transmission group is defined. By
4635: convention, the name assigned is:
4636:
4637: type OBJECT IDENTIFIER ::= { transmission number }
4638:
4639: where "type" is the symbolic value used for the media in the ifType
4640: column of the ifTable object, and "number" is the actual integer
4641: value corresponding to the symbol.
4642:
4643: 5.10. The SNMP Group
4644:
4645: Implementation of the SNMP group is mandatory for all systems which
4646: support an SNMP protocol entity. Some of the objects defined below
4647:
4648:
4649:
4650: IETF SNMP Working Group [Page 83]
4651:
4652: RFC 1158 MIB II May 1990
4653:
4654:
4655: will be zero-valued in those SNMP implementations that are optimized
4656: to support only those functions specific to either a management agent
4657: or a management client.
4658:
4659:
4660: OBJECT:
4661: -------
4662: snmpInPkts { snmp 1 }
4663:
4664: Syntax:
4665: Counter
4666:
4667: Definition:
4668: The total number of PDUs delivered to the SNMP entity
4669: from the transport service.
4670:
4671: Access:
4672: read-only.
4673:
4674: Status:
4675: mandatory.
4676:
4677:
4678: OBJECT:
4679: -------
4680: snmpOutPkts { snmp 2 }
4681:
4682: Syntax:
4683: Counter
4684:
4685: Definition:
4686: The total number of SNMP PDUs which were passed from the
4687: SNMP protocol entity to the transport service.
4688:
4689: Access:
4690: read-only.
4691:
4692: Status:
4693: mandatory.
4694:
4695:
4696: OBJECT:
4697: -------
4698: snmpInBadVersions { snmp 3 }
4699:
4700: Syntax:
4701: Counter
4702:
4703:
4704:
4705:
4706: IETF SNMP Working Group [Page 84]
4707:
4708: RFC 1158 MIB II May 1990
4709:
4710:
4711: Definition:
4712: The total number of syntactically correct SNMP PDUs which
4713: were delivered to the SNMP protocol entity and were for
4714: an unsupported SNMP version.
4715:
4716: Access:
4717: read-only.
4718:
4719: Status:
4720: mandatory.
4721:
4722:
4723: OBJECT:
4724: -------
4725: snmpInBadCommunityNames { snmp 4 }
4726:
4727: Syntax:
4728: Counter
4729:
4730: Definition:
4731: The total number of SNMP PDUs delivered to the SNMP
4732: protocol entity which used a SNMP community name not
4733: known to said entity.
4734:
4735: Access:
4736: read-only.
4737:
4738: Status:
4739: mandatory.
4740:
4741:
4742: OBJECT:
4743: -------
4744: snmpInBadCommunityUses { snmp 5 }
4745:
4746: Syntax:
4747: Counter
4748:
4749: Definition:
4750: The total number of SNMP PDUs delivered to the SNMP
4751: protocol entity which represented an SNMP operation which
4752: was not allowed by the SNMP community named in the PDU.
4753:
4754: Access:
4755: read-only.
4756:
4757: Status:
4758: mandatory.
4759:
4760:
4761:
4762: IETF SNMP Working Group [Page 85]
4763:
4764: RFC 1158 MIB II May 1990
4765:
4766:
4767: OBJECT:
4768: -------
4769: snmpInASNParseErrs { snmp 6 }
4770:
4771: Syntax:
4772: Counter
4773:
4774: Definition:
4775: The total number of ASN.1 parsing errors (either in
4776: encoding or syntax) encountered by the SNMP protocol
4777: entity when decoding received SNMP PDUs.
4778:
4779: Access:
4780: read-only.
4781:
4782: Status:
4783: mandatory.
4784:
4785:
4786: OBJECT:
4787: -------
4788: snmpInBadTypes { snmp 7 }
4789:
4790: Syntax:
4791: Counter
4792:
4793: Definition:
4794: The total number of SNMP PDUs delivered to the SNMP
4795: protocol entity which had an unknown PDU type.
4796:
4797: Access:
4798: read-only.
4799:
4800: Status:
4801: mandatory.
4802:
4803:
4804: OBJECT:
4805: -------
4806: snmpInTooBigs { snmp 8 }
4807:
4808: Syntax:
4809: Counter
4810:
4811: Definition:
4812: The total number valid SNMP PDUs which were delivered to
4813: the SNMP protocol entity and for which the value of the
4814: "ErrorStatus" component is "tooBig."
4815:
4816:
4817:
4818: IETF SNMP Working Group [Page 86]
4819:
4820: RFC 1158 MIB II May 1990
4821:
4822:
4823: Access:
4824: read-only.
4825:
4826: Status:
4827: mandatory.
4828:
4829:
4830: OBJECT:
4831: -------
4832: snmpInNoSuchNames { snmp 9 }
4833:
4834: Syntax:
4835: Counter
4836:
4837: Definition:
4838: The total number valid SNMP PDUs which were delivered to
4839: the SNMP protocol entity and for which the value of the
4840: "ErrorStatus" component is "noSuchName."
4841:
4842: Access:
4843: read-only.
4844:
4845: Status:
4846: mandatory.
4847:
4848:
4849: OBJECT:
4850: -------
4851: snmpInBadValues { snmp 10 }
4852:
4853: Syntax:
4854: Counter
4855:
4856: Definition:
4857: The total number valid SNMP PDUs which were delivered to
4858: the SNMP protocol entity and for which the value of the
4859: "ErrorStatus" component is "badValue."
4860:
4861: Access:
4862: read-only.
4863:
4864: Status:
4865: mandatory.
4866:
4867:
4868: OBJECT:
4869: -------
4870: snmpInReadOnlys { snmp 11 }
4871:
4872:
4873:
4874: IETF SNMP Working Group [Page 87]
4875:
4876: RFC 1158 MIB II May 1990
4877:
4878:
4879: Syntax:
4880: Counter
4881:
4882: Definition:
4883: The total number valid SNMP PDUs which were delivered to
4884: the SNMP protocol entity and for which the value of the
4885: "ErrorStatus" component is "readOnly."
4886:
4887: Access:
4888: read-only.
4889:
4890: Status:
4891: mandatory.
4892:
4893:
4894: OBJECT:
4895: -------
4896: snmpInGenErrs { snmp 12 }
4897:
4898: Syntax:
4899: Counter
4900:
4901: Definition:
4902: The total number valid SNMP PDUs which were delivered to
4903: the SNMP protocol entity and for which the value of the
4904: "ErrorStatus" component is "genErr."
4905:
4906: Access:
4907: read-only.
4908:
4909: Status:
4910: mandatory.
4911:
4912:
4913: OBJECT:
4914: -------
4915: snmpInTotalReqVars { snmp 13 }
4916:
4917: Syntax:
4918: Counter
4919:
4920: Definition:
4921: The total number of MIB objects which have been retrieved
4922: successfully by the SNMP protocol entity as the result of
4923: receiving valid SNMP Get-Request and Get-Next PDUs.
4924:
4925: Access:
4926: read-only.
4927:
4928:
4929:
4930: IETF SNMP Working Group [Page 88]
4931:
4932: RFC 1158 MIB II May 1990
4933:
4934:
4935: Status:
4936: mandatory.
4937:
4938:
4939: OBJECT:
4940: -------
4941: snmpInTotalSetVars { snmp 14 }
4942:
4943: Syntax:
4944: Counter
4945:
4946: Definition:
4947: The total number of MIB objects which have been altered
4948: successfully by the SNMP protocol entity as the result of
4949: receiving valid SNMP Set-Request PDUs.
4950:
4951: Access:
4952: read-only.
4953:
4954: Status:
4955: mandatory.
4956:
4957:
4958: OBJECT:
4959: -------
4960: snmpInGetRequests { snmp 15 }
4961:
4962: Syntax:
4963: Counter
4964:
4965: Definition:
4966: The total number of SNMP Get-Request PDUs which have been
4967: accepted and processed by the SNMP protocol entity.
4968:
4969: Access:
4970: read-only.
4971:
4972: Status:
4973: mandatory.
4974:
4975:
4976: OBJECT:
4977: -------
4978: snmpInGetNexts { snmp 16 }
4979:
4980: Syntax:
4981: Counter
4982:
4983:
4984:
4985:
4986: IETF SNMP Working Group [Page 89]
4987:
4988: RFC 1158 MIB II May 1990
4989:
4990:
4991: Definition:
4992: The total number of SNMP Get-Next PDUs which have been
4993: accepted and processed by the SNMP protocol entity.
4994:
4995: Access:
4996: read-only.
4997:
4998: Status:
4999: mandatory.
5000:
5001:
5002: OBJECT:
5003: -------
5004: snmpInSetRequests { snmp 17 }
5005:
5006: Syntax:
5007: Counter
5008:
5009: Definition:
5010: The total number of SNMP Set-Request PDUs which have been
5011: accepted and processed by the SNMP protocol entity.
5012:
5013: Access:
5014: read-only.
5015:
5016: Status:
5017: mandatory.
5018:
5019:
5020: OBJECT:
5021: -------
5022: snmpInGetResponses { snmp 18 }
5023:
5024: Syntax:
5025: Counter
5026:
5027: Definition:
5028: The total number of SNMP Get-Response PDUs which have
5029: been accepted and processed by the SNMP protocol entity.
5030:
5031: Access:
5032: read-only.
5033:
5034: Status:
5035: mandatory.
5036:
5037:
5038:
5039:
5040:
5041:
5042: IETF SNMP Working Group [Page 90]
5043:
5044: RFC 1158 MIB II May 1990
5045:
5046:
5047: OBJECT:
5048: -------
5049: snmpInTraps { snmp 19 }
5050:
5051: Syntax:
5052: Counter
5053:
5054: Definition:
5055: The total number of SNMP Trap PDUs which have been
5056: accepted and processed by the SNMP protocol entity.
5057:
5058: Access:
5059: read-only.
5060:
5061: Status:
5062: mandatory.
5063:
5064:
5065: OBJECT:
5066: -------
5067: snmpOutTooBigs { snmp 20 }
5068:
5069: Syntax:
5070: Counter
5071:
5072: Definition:
5073: The total number valid SNMP PDUs which were generated by
5074: the SNMP protocol entity and for which the value of the
5075: "ErrorStatus" component is "tooBig."
5076:
5077: Access:
5078: read-only.
5079:
5080: Status:
5081: mandatory.
5082:
5083:
5084: OBJECT:
5085: -------
5086: snmpOutNoSuchNames { snmp 21 }
5087:
5088: Syntax:
5089: Counter
5090:
5091: Definition:
5092: The total number valid SNMP PDUs which were generated by
5093: the SNMP protocol entity and for which the value of the
5094: "ErrorStatus" component is "noSuchName."
5095:
5096:
5097:
5098: IETF SNMP Working Group [Page 91]
5099:
5100: RFC 1158 MIB II May 1990
5101:
5102:
5103: Access:
5104: read-only.
5105:
5106: Status:
5107: mandatory.
5108:
5109:
5110: OBJECT:
5111: -------
5112: snmpOutBadValues { snmp 22 }
5113:
5114: Syntax:
5115: Counter
5116:
5117: Definition:
5118: The total number valid SNMP PDUs which were generated by
5119: the SNMP protocol entity and for which the value of the
5120: "ErrorStatus" component is "badValue."
5121:
5122: Access:
5123: read-only.
5124:
5125: Status:
5126: mandatory.
5127:
5128:
5129: OBJECT:
5130: -------
5131: snmpOutReadOnlys { snmp 23 }
5132:
5133: Syntax:
5134: Counter
5135:
5136: Definition:
5137: The total number valid SNMP PDUs which were generated by
5138: the SNMP protocol entity and for which the value of the
5139: "ErrorStatus" component is "readOnly."
5140:
5141: Access:
5142: read-only.
5143:
5144: Status:
5145: mandatory.
5146:
5147:
5148: OBJECT:
5149: -------
5150: snmpOutGenErrs { snmp 24 }
5151:
5152:
5153:
5154: IETF SNMP Working Group [Page 92]
5155:
5156: RFC 1158 MIB II May 1990
5157:
5158:
5159: Syntax:
5160: Counter
5161:
5162: Definition:
5163: The total number valid SNMP PDUs which were generated by
5164: the SNMP protocol entity and for which the value of the
5165: "ErrorStatus" component is "genErr."
5166:
5167: Access:
5168: read-only.
5169:
5170: Status:
5171: mandatory.
5172:
5173:
5174: OBJECT:
5175: -------
5176: snmpOutGetRequests { snmp 25 }
5177:
5178: Syntax:
5179: Counter
5180:
5181: Definition:
5182: The total number of SNMP Get-Request PDUs which have been
5183: generated by the SNMP protocol entity.
5184:
5185: Access:
5186: read-only.
5187:
5188: Status:
5189: mandatory.
5190:
5191:
5192: OBJECT:
5193: -------
5194: snmpOutGetNexts { snmp 26 }
5195:
5196: Syntax:
5197: Counter
5198:
5199: Definition:
5200: The total number of SNMP Get-Next PDUs which have been
5201: generated by the SNMP protocol entity.
5202:
5203: Access:
5204: read-only.
5205:
5206:
5207:
5208:
5209:
5210: IETF SNMP Working Group [Page 93]
5211:
5212: RFC 1158 MIB II May 1990
5213:
5214:
5215: Status:
5216: mandatory.
5217:
5218:
5219: OBJECT:
5220: -------
5221: snmpOutSetRequests { snmp 27 }
5222:
5223: Syntax:
5224: Counter
5225:
5226: Definition:
5227: The total number of SNMP Set-Request PDUs which have been
5228: generated by the SNMP protocol entity.
5229:
5230: Access:
5231: read-only.
5232:
5233: Status:
5234: mandatory.
5235:
5236:
5237: OBJECT:
5238: -------
5239: snmpOutGetResponses { snmp 28 }
5240:
5241: Syntax:
5242: Counter
5243:
5244: Definition:
5245: The total number of SNMP Get-Response PDUs which have
5246: been generated by the SNMP protocol entity.
5247:
5248: Access:
5249: read-only.
5250:
5251: Status:
5252: mandatory.
5253:
5254:
5255: OBJECT:
5256: -------
5257: snmpOutTraps { snmp 29 }
5258:
5259: Syntax:
5260: Counter
5261:
5262:
5263:
5264:
5265:
5266: IETF SNMP Working Group [Page 94]
5267:
5268: RFC 1158 MIB II May 1990
5269:
5270:
5271: Definition:
5272: The total number of SNMP Trap PDUs which have been
5273: generated by the SNMP protocol entity.
5274:
5275: Access:
5276: read-only.
5277:
5278: Status:
5279: mandatory.
5280:
5281:
5282: OBJECT:
5283: -------
5284: snmpEnableAuthTraps { snmp 30 }
5285:
5286: Syntax:
5287: INTEGER {
5288: enabled(1),
5289: disabled(2)
5290: }
5291:
5292: Definition:
5293: Indicates whether the SNMP agent process is configured to
5294: generate authentication-failure traps.
5295:
5296: Access:
5297: read-write.
5298:
5299: Status:
5300: mandatory.
5301:
5302: 6. Definitions
5303:
5304: RFC1158-MIB
5305:
5306: DEFINITIONS ::= BEGIN
5307:
5308: IMPORTS
5309: mgmt, OBJECT-TYPE, NetworkAddress, IpAddress,
5310: Counter, Gauge, TimeTicks
5311: FROM RFC1155-SMI;
5312:
5313: mib-2 OBJECT IDENTIFIER ::= { mgmt 1 } -- MIB-II
5314: -- (same prefix as MIB-I)
5315:
5316: system OBJECT IDENTIFIER ::= { mib-2 1 }
5317: interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
5318: at OBJECT IDENTIFIER ::= { mib-2 3 }
5319:
5320:
5321:
5322: IETF SNMP Working Group [Page 95]
5323:
5324: RFC 1158 MIB II May 1990
5325:
5326:
5327: ip OBJECT IDENTIFIER ::= { mib-2 4 }
5328: icmp OBJECT IDENTIFIER ::= { mib-2 5 }
5329: tcp OBJECT IDENTIFIER ::= { mib-2 6 }
5330: udp OBJECT IDENTIFIER ::= { mib-2 7 }
5331: egp OBJECT IDENTIFIER ::= { mib-2 8 }
5332: -- cmot OBJECT IDENTIFIER ::= { mib-2 9 }
5333: transmission OBJECT IDENTIFIER ::= { mib-2 10 }
5334: snmp OBJECT IDENTIFIER ::= { mib-2 11 }
5335:
5336:
5337: -- object types
5338:
5339: -- the System group
5340:
5341: sysDescr OBJECT-TYPE
5342: SYNTAX DisplayString (SIZE (0..255))
5343: ACCESS read-only
5344: STATUS mandatory
5345: ::= { system 1 }
5346:
5347: sysObjectID OBJECT-TYPE
5348: SYNTAX OBJECT IDENTIFIER
5349: ACCESS read-only
5350: STATUS mandatory
5351: ::= { system 2 }
5352:
5353: sysUpTime OBJECT-TYPE
5354: SYNTAX TimeTicks
5355: ACCESS read-only
5356: STATUS mandatory
5357: ::= { system 3 }
5358:
5359: sysContact OBJECT-TYPE
5360: SYNTAX DisplayString (SIZE (0..255))
5361: ACCESS read-write
5362: STATUS mandatory
5363: ::= { system 4 }
5364:
5365: sysName OBJECT-TYPE
5366: SYNTAX DisplayString (SIZE (0..255))
5367: ACCESS read-write
5368: STATUS mandatory
5369: ::= { system 5 }
5370:
5371: sysLocation OBJECT-TYPE
5372: SYNTAX DisplayString (SIZE (0..255))
5373: ACCESS read-only
5374: STATUS mandatory
5375:
5376:
5377:
5378: IETF SNMP Working Group [Page 96]
5379:
5380: RFC 1158 MIB II May 1990
5381:
5382:
5383: ::= { system 6 }
5384:
5385: sysServices OBJECT-TYPE
5386: SYNTAX INTEGER (0..127)
5387: ACCESS read-only
5388: STATUS mandatory
5389: ::= { system 7 }
5390:
5391:
5392: -- the Interfaces group
5393:
5394: ifNumber OBJECT-TYPE
5395: SYNTAX INTEGER
5396: ACCESS read-only
5397: STATUS mandatory
5398: ::= { interfaces 1 }
5399:
5400: -- the Interfaces table
5401:
5402: ifTable OBJECT-TYPE
5403: SYNTAX SEQUENCE OF IfEntry
5404: ACCESS read-only
5405: STATUS mandatory
5406: ::= { interfaces 2 }
5407:
5408: ifEntry OBJECT-TYPE
5409: SYNTAX IfEntry
5410: ACCESS read-only
5411: STATUS mandatory
5412: ::= { ifTable 1 }
5413:
5414: IfEntry ::= SEQUENCE {
5415: ifIndex
5416: INTEGER,
5417: ifDescr
5418: DisplayString,
5419: ifType
5420: INTEGER,
5421: ifMtu
5422: INTEGER,
5423: ifSpeed
5424: Gauge,
5425: ifPhysAddress
5426: OCTET STRING,
5427: ifAdminStatus
5428: INTEGER,
5429: ifOperStatus
5430: INTEGER,
5431:
5432:
5433:
5434: IETF SNMP Working Group [Page 97]
5435:
5436: RFC 1158 MIB II May 1990
5437:
5438:
5439: ifLastChange
5440: TimeTicks,
5441: ifInOctets
5442: Counter,
5443: ifInUcastPkts
5444: Counter,
5445: ifInNUcastPkts
5446: Counter,
5447: ifInDiscards
5448: Counter,
5449: ifInErrors
5450: Counter,
5451: ifInUnknownProtos
5452: Counter,
5453: ifOutOctets
5454: Counter,
5455: ifOutUcastPkts
5456: Counter,
5457: ifOutNUcastPkts
5458: Counter,
5459: ifOutDiscards
5460: Counter,
5461: ifOutErrors
5462: Counter,
5463: ifOutQLen
5464: Gauge,
5465: ifSpecific
5466: OBJECT IDENTIFIER
5467: }
5468:
5469: ifIndex OBJECT-TYPE
5470: SYNTAX INTEGER
5471: ACCESS read-only
5472: STATUS mandatory
5473: ::= { ifEntry 1 }
5474:
5475: ifDescr OBJECT-TYPE
5476: SYNTAX DisplayString (SIZE (0..255))
5477: ACCESS read-only
5478: STATUS mandatory
5479: ::= { ifEntry 2 }
5480:
5481: ifType OBJECT-TYPE
5482: SYNTAX INTEGER {
5483: other(1), -- none of the
5484: -- following
5485: regular1822(2),
5486: hdh1822(3),
5487:
5488:
5489:
5490: IETF SNMP Working Group [Page 98]
5491:
5492: RFC 1158 MIB II May 1990
5493:
5494:
5495: ddn-x25(4),
5496: rfc877-x25(5),
5497: ethernet-csmacd(6),
5498: iso88023-csmacd(7),
5499: iso88024-tokenBus(8),
5500: iso88025-tokenRing(9),
5501: iso88026-man(10),
5502: starLan(11),
5503: proteon-10Mbit(12),
5504: proteon-80Mbit(13),
5505: hyperchannel(14),
5506: fddi(15),
5507: lapb(16),
5508: sdlc(17),
5509: t1-carrier(18),
5510: cept(19), -- european
5511: --equivalent of T-1
5512: basicISDN(20),
5513: primaryISDN(21),
5514: -- proprietary
5515: -- serial
5516: propPointToPointSerial(22),
5517: terminalServer-asyncPort(23),
5518: softwareLoopback(24),
5519: eon(25), -- CLNP over IP
5520: ethernet-3Mbit(26),
5521: nsip(27), -- XNS over IP
5522: slip(28) -- generic SLIP
5523: }
5524: ACCESS read-only
5525: STATUS mandatory
5526: ::= { ifEntry 3 }
5527:
5528: ifMtu OBJECT-TYPE
5529: SYNTAX INTEGER
5530: ACCESS read-only
5531: STATUS mandatory
5532: ::= { ifEntry 4 }
5533:
5534: ifSpeed OBJECT-TYPE
5535: SYNTAX Gauge
5536: ACCESS read-only
5537: STATUS mandatory
5538: ::= { ifEntry 5 }
5539:
5540: ifPhysAddress OBJECT-TYPE
5541: SYNTAX OCTET STRING
5542: ACCESS read-only
5543:
5544:
5545:
5546: IETF SNMP Working Group [Page 99]
5547:
5548: RFC 1158 MIB II May 1990
5549:
5550:
5551: STATUS mandatory
5552: ::= { ifEntry 6 }
5553:
5554: ifAdminStatus OBJECT-TYPE
5555: SYNTAX INTEGER {
5556: up(1), -- ready to pass packets
5557: down(2),
5558: testing(3) -- in some test mode
5559: }
5560: ACCESS read-write
5561: STATUS mandatory
5562: ::= { ifEntry 7 }
5563:
5564: ifOperStatus OBJECT-TYPE
5565: SYNTAX INTEGER {
5566: up(1), -- ready to pass packets
5567: down(2),
5568: testing(3) -- in some test mode
5569: }
5570: ACCESS read-only
5571: STATUS mandatory
5572: ::= { ifEntry 8 }
5573:
5574: ifLastChange OBJECT-TYPE
5575: SYNTAX TimeTicks
5576: ACCESS read-only
5577: STATUS mandatory
5578: ::= { ifEntry 9 }
5579:
5580: ifInOctets OBJECT-TYPE
5581: SYNTAX Counter
5582: ACCESS read-only
5583: STATUS mandatory
5584: ::= { ifEntry 10 }
5585:
5586: ifInUcastPkts OBJECT-TYPE
5587: SYNTAX Counter
5588: ACCESS read-only
5589: STATUS mandatory
5590: ::= { ifEntry 11 }
5591:
5592: ifInNUcastPkts OBJECT-TYPE
5593: SYNTAX Counter
5594: ACCESS read-only
5595: STATUS mandatory
5596: ::= { ifEntry 12 }
5597:
5598: ifInDiscards OBJECT-TYPE
5599:
5600:
5601:
5602: IETF SNMP Working Group [Page 100]
5603:
5604: RFC 1158 MIB II May 1990
5605:
5606:
5607: SYNTAX Counter
5608: ACCESS read-only
5609: STATUS mandatory
5610: ::= { ifEntry 13 }
5611:
5612: ifInErrors OBJECT-TYPE
5613: SYNTAX Counter
5614: ACCESS read-only
5615: STATUS mandatory
5616: ::= { ifEntry 14 }
5617:
5618: ifInUnknownProtos OBJECT-TYPE
5619: SYNTAX Counter
5620: ACCESS read-only
5621: STATUS mandatory
5622: ::= { ifEntry 15 }
5623:
5624: ifOutOctets OBJECT-TYPE
5625: SYNTAX Counter
5626: ACCESS read-only
5627: STATUS mandatory
5628: ::= { ifEntry 16 }
5629:
5630: ifOutUcastPkts OBJECT-TYPE
5631: SYNTAX Counter
5632: ACCESS read-only
5633: STATUS mandatory
5634: ::= { ifEntry 17 }
5635:
5636: ifOutNUcastPkts OBJECT-TYPE
5637: SYNTAX Counter
5638: ACCESS read-only
5639: STATUS mandatory
5640: ::= { ifEntry 18 }
5641:
5642: ifOutDiscards OBJECT-TYPE
5643: SYNTAX Counter
5644: ACCESS read-only
5645: STATUS mandatory
5646: ::= { ifEntry 19 }
5647:
5648: ifOutErrors OBJECT-TYPE
5649: SYNTAX Counter
5650: ACCESS read-only
5651: STATUS mandatory
5652: ::= { ifEntry 20 }
5653:
5654: ifOutQLen OBJECT-TYPE
5655:
5656:
5657:
5658: IETF SNMP Working Group [Page 101]
5659:
5660: RFC 1158 MIB II May 1990
5661:
5662:
5663: SYNTAX Gauge
5664: ACCESS read-only
5665: STATUS mandatory
5666: ::= { ifEntry 21 }
5667:
5668: ifSpecific OBJECT-TYPE
5669: SYNTAX OBJECT IDENTIFIER
5670: ACCESS read-only
5671: STATUS mandatory
5672: ::= { ifEntry 22 }
5673:
5674: nullSpecific OBJECT IDENTIFIER ::= { 0 0 }
5675:
5676: -- the Address Translation group (deprecated)
5677:
5678: atTable OBJECT-TYPE
5679: SYNTAX SEQUENCE OF AtEntry
5680: ACCESS read-write
5681: STATUS deprecated
5682: ::= { at 1 }
5683:
5684: atEntry OBJECT-TYPE
5685: SYNTAX AtEntry
5686: ACCESS read-write
5687: STATUS deprecated
5688: ::= { atTable 1 }
5689:
5690: AtEntry ::= SEQUENCE {
5691: atIfIndex
5692: INTEGER,
5693: atPhysAddress
5694: OCTET STRING,
5695: atNetAddress
5696: NetworkAddress
5697: }
5698:
5699: atIfIndex OBJECT-TYPE
5700: SYNTAX INTEGER
5701: ACCESS read-write
5702: STATUS deprecated
5703: ::= { atEntry 1 }
5704:
5705: atPhysAddress OBJECT-TYPE
5706: SYNTAX OCTET STRING
5707: ACCESS read-write
5708: STATUS deprecated
5709: ::= { atEntry 2 }
5710:
5711:
5712:
5713:
5714: IETF SNMP Working Group [Page 102]
5715:
5716: RFC 1158 MIB II May 1990
5717:
5718:
5719: atNetAddress OBJECT-TYPE
5720: SYNTAX NetworkAddress
5721: ACCESS read-write
5722: STATUS deprecated
5723: ::= { atEntry 3 }
5724:
5725:
5726: -- the IP group
5727:
5728: ipForwarding OBJECT-TYPE
5729: SYNTAX INTEGER {
5730: gateway(1), -- entity forwards
5731: -- datagrams
5732: host(2) -- entity does NOT
5733: -- forward datagrams
5734: }
5735: ACCESS read-write
5736: STATUS mandatory
5737: ::= { ip 1 }
5738:
5739: ipDefaultTTL OBJECT-TYPE
5740: SYNTAX INTEGER
5741: ACCESS read-write
5742: STATUS mandatory
5743: ::= { ip 2 }
5744:
5745: ipInReceives OBJECT-TYPE
5746: SYNTAX Counter
5747: ACCESS read-only
5748: STATUS mandatory
5749: ::= { ip 3 }
5750:
5751: ipInHdrErrors OBJECT-TYPE
5752: SYNTAX Counter
5753: ACCESS read-only
5754: STATUS mandatory
5755: ::= { ip 4 }
5756:
5757: ipInAddrErrors OBJECT-TYPE
5758: SYNTAX Counter
5759: ACCESS read-only
5760: STATUS mandatory
5761: ::= { ip 5 }
5762:
5763: ipForwDatagrams OBJECT-TYPE
5764: SYNTAX Counter
5765: ACCESS read-only
5766: STATUS mandatory
5767:
5768:
5769:
5770: IETF SNMP Working Group [Page 103]
5771:
5772: RFC 1158 MIB II May 1990
5773:
5774:
5775: ::= { ip 6 }
5776:
5777: ipInUnknownProtos OBJECT-TYPE
5778: SYNTAX Counter
5779: ACCESS read-only
5780: STATUS mandatory
5781: ::= { ip 7 }
5782:
5783: ipInDiscards OBJECT-TYPE
5784: SYNTAX Counter
5785: ACCESS read-only
5786: STATUS mandatory
5787: ::= { ip 8 }
5788:
5789: ipInDelivers OBJECT-TYPE
5790: SYNTAX Counter
5791: ACCESS read-only
5792: STATUS mandatory
5793: ::= { ip 9 }
5794:
5795: ipOutRequests OBJECT-TYPE
5796: SYNTAX Counter
5797: ACCESS read-only
5798: STATUS mandatory
5799: ::= { ip 10 }
5800:
5801: ipOutDiscards OBJECT-TYPE
5802: SYNTAX Counter
5803: ACCESS read-only
5804: STATUS mandatory
5805: ::= { ip 11 }
5806:
5807: ipOutNoRoutes OBJECT-TYPE
5808: SYNTAX Counter
5809: ACCESS read-only
5810: STATUS mandatory
5811: ::= { ip 12 }
5812:
5813: ipReasmTimeout OBJECT-TYPE
5814: SYNTAX INTEGER
5815: ACCESS read-only
5816: STATUS mandatory
5817: ::= { ip 13 }
5818:
5819: ipReasmReqds OBJECT-TYPE
5820: SYNTAX Counter
5821: ACCESS read-only
5822: STATUS mandatory
5823:
5824:
5825:
5826: IETF SNMP Working Group [Page 104]
5827:
5828: RFC 1158 MIB II May 1990
5829:
5830:
5831: ::= { ip 14 }
5832:
5833: ipReasmOKs OBJECT-TYPE
5834: SYNTAX Counter
5835: ACCESS read-only
5836: STATUS mandatory
5837: ::= { ip 15 }
5838:
5839: ipReasmFails OBJECT-TYPE
5840: SYNTAX Counter
5841: ACCESS read-only
5842: STATUS mandatory
5843: ::= { ip 16 }
5844:
5845: ipFragOKs OBJECT-TYPE
5846: SYNTAX Counter
5847: ACCESS read-only
5848: STATUS mandatory
5849: ::= { ip 17 }
5850:
5851: ipFragFails OBJECT-TYPE
5852: SYNTAX Counter
5853: ACCESS read-only
5854: STATUS mandatory
5855: ::= { ip 18 }
5856:
5857: ipFragCreates OBJECT-TYPE
5858: SYNTAX Counter
5859: ACCESS read-only
5860: STATUS mandatory
5861: ::= { ip 19 }
5862:
5863: -- the IP Interface table
5864:
5865: ipAddrTable OBJECT-TYPE
5866: SYNTAX SEQUENCE OF IpAddrEntry
5867: ACCESS read-only
5868: STATUS mandatory
5869: ::= { ip 20 }
5870:
5871: ipAddrEntry OBJECT-TYPE
5872: SYNTAX IpAddrEntry
5873: ACCESS read-only
5874: STATUS mandatory
5875: ::= { ipAddrTable 1 }
5876:
5877: IpAddrEntry ::= SEQUENCE {
5878: ipAdEntAddr
5879:
5880:
5881:
5882: IETF SNMP Working Group [Page 105]
5883:
5884: RFC 1158 MIB II May 1990
5885:
5886:
5887: IpAddress,
5888: ipAdEntIfIndex
5889: INTEGER,
5890: ipAdEntNetMask
5891: IpAddress,
5892: ipAdEntBcastAddr
5893: INTEGER,
5894: ipAdEntReasmMaxSize
5895: INTEGER (0..65535)
5896: }
5897:
5898: ipAdEntAddr OBJECT-TYPE
5899: SYNTAX IpAddress
5900: ACCESS read-only
5901: STATUS mandatory
5902: ::= { ipAddrEntry 1 }
5903:
5904: ipAdEntIfIndex OBJECT-TYPE
5905: SYNTAX INTEGER
5906: ACCESS read-only
5907: STATUS mandatory
5908: ::= { ipAddrEntry 2 }
5909:
5910: ipAdEntNetMask OBJECT-TYPE
5911: SYNTAX IpAddress
5912: ACCESS read-only
5913: STATUS mandatory
5914: ::= { ipAddrEntry 3 }
5915:
5916: ipAdEntBcastAddr OBJECT-TYPE
5917: SYNTAX INTEGER
5918: ACCESS read-only
5919: STATUS mandatory
5920: ::= { ipAddrEntry 4 }
5921:
5922: ipAdEntReasmMaxSiz OBJECT-TYPE
5923: SYNTAX INTEGER (0..65535)
5924: ACCESS read-only
5925: STATUS mandatory
5926: ::= { ipAddrEntry 5 }
5927:
5928: -- the IP Routing table
5929:
5930: ipRoutingTable OBJECT-TYPE
5931: SYNTAX SEQUENCE OF IpRouteEntry
5932: ACCESS read-write
5933: STATUS mandatory
5934: ::= { ip 21 }
5935:
5936:
5937:
5938: IETF SNMP Working Group [Page 106]
5939:
5940: RFC 1158 MIB II May 1990
5941:
5942:
5943: ipRouteEntry OBJECT-TYPE
5944: SYNTAX IpRouteEntry
5945: ACCESS read-write
5946: STATUS mandatory
5947: ::= { ipRoutingTable 1 }
5948:
5949: IpRouteEntry ::= SEQUENCE {
5950: ipRouteDest
5951: IpAddress,
5952: ipRouteIfIndex
5953: INTEGER,
5954: ipRouteMetric1
5955: INTEGER,
5956: ipRouteMetric2
5957: INTEGER,
5958: ipRouteMetric3
5959: INTEGER,
5960: ipRouteMetric4
5961: INTEGER,
5962: ipRouteNextHop
5963: IpAddress,
5964: ipRouteType
5965: INTEGER,
5966: ipRouteProto
5967: INTEGER,
5968: ipRouteAge
5969: INTEGER,
5970: ipRouteMask
5971: IpAddress
5972: }
5973:
5974: ipRouteDest OBJECT-TYPE
5975: SYNTAX IpAddress
5976: ACCESS read-write
5977: STATUS mandatory
5978: ::= { ipRouteEntry 1 }
5979:
5980: ipRouteIfIndex OBJECT-TYPE
5981: SYNTAX INTEGER
5982: ACCESS read-write
5983: STATUS mandatory
5984: ::= { ipRouteEntry 2 }
5985:
5986: ipRouteMetric1 OBJECT-TYPE
5987: SYNTAX INTEGER
5988: ACCESS read-write
5989: STATUS mandatory
5990: ::= { ipRouteEntry 3 }
5991:
5992:
5993:
5994: IETF SNMP Working Group [Page 107]
5995:
5996: RFC 1158 MIB II May 1990
5997:
5998:
5999: ipRouteMetric2 OBJECT-TYPE
6000: SYNTAX INTEGER
6001: ACCESS read-write
6002: STATUS mandatory
6003: ::= { ipRouteEntry 4 }
6004:
6005: ipRouteMetric3 OBJECT-TYPE
6006: SYNTAX INTEGER
6007: ACCESS read-write
6008: STATUS mandatory
6009: ::= { ipRouteEntry 5 }
6010:
6011: ipRouteMetric4 OBJECT-TYPE
6012: SYNTAX INTEGER
6013: ACCESS read-write
6014: STATUS mandatory
6015: ::= { ipRouteEntry 6 }
6016:
6017: ipRouteNextHop OBJECT-TYPE
6018: SYNTAX IpAddress
6019: ACCESS read-write
6020: STATUS mandatory
6021: ::= { ipRouteEntry 7 }
6022:
6023: ipRouteType OBJECT-TYPE
6024: SYNTAX INTEGER {
6025: other(1), -- none of the following
6026:
6027: invalid(2), -- an invalidated route
6028:
6029: -- route to directly
6030: direct(3), -- connected
6031: -- (sub-)network
6032:
6033: -- route to a non-local
6034: remote(4) -- host/network/
6035: -- sub-network
6036: }
6037: ACCESS read-write
6038: STATUS mandatory
6039: ::= { ipRouteEntry 8 }
6040:
6041: ipRouteProto OBJECT-TYPE
6042: SYNTAX INTEGER {
6043: other(1), -- none of the following
6044:
6045: -- non-protocol
6046: -- information
6047:
6048:
6049:
6050: IETF SNMP Working Group [Page 108]
6051:
6052: RFC 1158 MIB II May 1990
6053:
6054:
6055: -- e.g., manually
6056: local(2), -- configured entries
6057:
6058: -- set via a network
6059: netmgmt(3), -- management protocol
6060:
6061: -- obtained via ICMP,
6062: icmp(4), -- e.g., Redirect
6063:
6064: -- the following are
6065: -- gateway routing
6066: -- protocols
6067: egp(5),
6068: ggp(6),
6069: hello(7),
6070: rip(8),
6071: is-is(9),
6072: es-is(10),
6073: ciscoIgrp(11),
6074: bbnSpfIgp(12),
6075: ospf(13)
6076: bgp(14)
6077: }
6078: ACCESS read-only
6079: STATUS mandatory
6080: ::= { ipRouteEntry 9 }
6081:
6082: ipRouteAge OBJECT-TYPE
6083: SYNTAX INTEGER
6084: ACCESS read-write
6085: STATUS mandatory
6086: ::= { ipRouteEntry 10 }
6087:
6088: ipRouteMask OBJECT-TYPE
6089: SYNTAX IpAddress
6090: ACCESS read-write
6091: STATUS mandatory
6092: ::= { ipRouteEntry 11 }
6093:
6094: -- the IP Address Translation tables
6095:
6096: ipNetToMediaTable OBJECT-TYPE
6097: SYNTAX SEQUENCE OF IpNetToMediaEntry
6098: ACCESS read-write
6099: STATUS mandatory
6100: ::= { ip 22 }
6101:
6102: ipNetToMediaEntry OBJECT-TYPE
6103:
6104:
6105:
6106: IETF SNMP Working Group [Page 109]
6107:
6108: RFC 1158 MIB II May 1990
6109:
6110:
6111: SYNTAX IpNetToMediaEntry
6112: ACCESS read-write
6113: STATUS mandatory
6114: ::= { ipNetToMediaTable 1 }
6115:
6116: IpNetToMediaEntry ::= SEQUENCE {
6117: ipNetToMediaIfIndex
6118: INTEGER,
6119: ipNetToMediaPhysAddress
6120: OCTET STRING,
6121: ipNetToMediaNetAddress
6122: IpAddress,
6123: ipNetoToMediaType
6124: INTEGER
6125: }
6126:
6127: ipNetToMediaIfIndex OBJECT-TYPE
6128: SYNTAX INTEGER
6129: ACCESS read-write
6130: STATUS mandatory
6131: ::= { ipNetToMediaEntry 1 }
6132:
6133: ipNetToMediaPhysAddress OBJECT-TYPE
6134: SYNTAX OCTET STRING
6135: ACCESS read-write
6136: STATUS mandatory
6137: ::= { ipNetToMediaEntry 2 }
6138:
6139: ipNetToMediaNetAddress OBJECT-TYPE
6140: SYNTAX IpAddress
6141: ACCESS read-write
6142: STATUS mandatory
6143: ::= { ipNetToMediaEntry 3 }
6144:
6145: ipNetToMediaType OBJECT-TYPE
6146: SYNTAX INTEGER {
6147: other(1), -- none of the following
6148:
6149: invalid(2), -- an invalidated mapping
6150: dynamic(3), -- connected (sub-)network
6151:
6152: static(4)
6153: }
6154: ACCESS read-write
6155: STATUS mandatory
6156: ::= { ipNetToMediaEntry 4 }
6157:
6158:
6159:
6160:
6161:
6162: IETF SNMP Working Group [Page 110]
6163:
6164: RFC 1158 MIB II May 1990
6165:
6166:
6167: -- the ICMP group
6168:
6169: icmpInMsgs OBJECT-TYPE
6170: SYNTAX Counter
6171: ACCESS read-only
6172: STATUS mandatory
6173: ::= { icmp 1 }
6174:
6175: icmpInErrors OBJECT-TYPE
6176: SYNTAX Counter
6177: ACCESS read-only
6178: STATUS mandatory
6179: ::= { icmp 2 }
6180:
6181: icmpInDestUnreachs OBJECT-TYPE
6182: SYNTAX Counter
6183: ACCESS read-only
6184: STATUS mandatory
6185: ::= { icmp 3 }
6186:
6187: icmpInTimeExcds OBJECT-TYPE
6188: SYNTAX Counter
6189: ACCESS read-only
6190: STATUS mandatory
6191: ::= { icmp 4 }
6192:
6193: icmpInParmProbs OBJECT-TYPE
6194: SYNTAX Counter
6195: ACCESS read-only
6196: STATUS mandatory
6197: ::= { icmp 5 }
6198:
6199: icmpInSrcQuenchs OBJECT-TYPE
6200: SYNTAX Counter
6201: ACCESS read-only
6202: STATUS mandatory
6203: ::= { icmp 6 }
6204:
6205: icmpInRedirects OBJECT-TYPE
6206: SYNTAX Counter
6207: ACCESS read-only
6208: STATUS mandatory
6209: ::= { icmp 7 }
6210:
6211: icmpInEchos OBJECT-TYPE
6212: SYNTAX Counter
6213: ACCESS read-only
6214: STATUS mandatory
6215:
6216:
6217:
6218: IETF SNMP Working Group [Page 111]
6219:
6220: RFC 1158 MIB II May 1990
6221:
6222:
6223: ::= { icmp 8 }
6224:
6225: icmpInEchoReps OBJECT-TYPE
6226: SYNTAX Counter
6227: ACCESS read-only
6228: STATUS mandatory
6229: ::= { icmp 9 }
6230:
6231: icmpInTimestamps OBJECT-TYPE
6232: SYNTAX Counter
6233: ACCESS read-only
6234: STATUS mandatory
6235: ::= { icmp 10 }
6236:
6237: icmpInTimestampReps OBJECT-TYPE
6238: SYNTAX Counter
6239: ACCESS read-only
6240: STATUS mandatory
6241: ::= { icmp 11 }
6242:
6243: icmpInAddrMasks OBJECT-TYPE
6244: SYNTAX Counter
6245: ACCESS read-only
6246: STATUS mandatory
6247: ::= { icmp 12 }
6248:
6249: icmpInAddrMaskReps OBJECT-TYPE
6250: SYNTAX Counter
6251: ACCESS read-only
6252: STATUS mandatory
6253: ::= { icmp 13 }
6254:
6255: icmpOutMsgs OBJECT-TYPE
6256: SYNTAX Counter
6257: ACCESS read-only
6258: STATUS mandatory
6259: ::= { icmp 14 }
6260:
6261: icmpOutErrors OBJECT-TYPE
6262: SYNTAX Counter
6263: ACCESS read-only
6264: STATUS mandatory
6265: ::= { icmp 15 }
6266:
6267: icmpOutDestUnreachs OBJECT-TYPE
6268: SYNTAX Counter
6269: ACCESS read-only
6270: STATUS mandatory
6271:
6272:
6273:
6274: IETF SNMP Working Group [Page 112]
6275:
6276: RFC 1158 MIB II May 1990
6277:
6278:
6279: ::= { icmp 16 }
6280:
6281: icmpOutTimeExcds OBJECT-TYPE
6282: SYNTAX Counter
6283: ACCESS read-only
6284: STATUS mandatory
6285: ::= { icmp 17 }
6286:
6287: icmpOutParmProbs OBJECT-TYPE
6288: SYNTAX Counter
6289: ACCESS read-only
6290: STATUS mandatory
6291: ::= { icmp 18 }
6292:
6293: icmpOutSrcQuenchs OBJECT-TYPE
6294: SYNTAX Counter
6295: ACCESS read-only
6296: STATUS mandatory
6297: ::= { icmp 19 }
6298:
6299: icmpOutRedirects OBJECT-TYPE
6300: SYNTAX Counter
6301: ACCESS read-only
6302: STATUS mandatory
6303: ::= { icmp 20 }
6304:
6305: icmpOutEchos OBJECT-TYPE
6306: SYNTAX Counter
6307: ACCESS read-only
6308: STATUS mandatory
6309: ::= { icmp 21 }
6310:
6311: icmpOutEchoReps OBJECT-TYPE
6312: SYNTAX Counter
6313: ACCESS read-only
6314: STATUS mandatory
6315: ::= { icmp 22 }
6316:
6317: icmpOutTimestamps OBJECT-TYPE
6318: SYNTAX Counter
6319: ACCESS read-only
6320: STATUS mandatory
6321: ::= { icmp 23 }
6322:
6323: icmpOutTimestampReps OBJECT-TYPE
6324: SYNTAX Counter
6325: ACCESS read-only
6326: STATUS mandatory
6327:
6328:
6329:
6330: IETF SNMP Working Group [Page 113]
6331:
6332: RFC 1158 MIB II May 1990
6333:
6334:
6335: ::= { icmp 24 }
6336:
6337: icmpOutAddrMasks OBJECT-TYPE
6338: SYNTAX Counter
6339: ACCESS read-only
6340: STATUS mandatory
6341: ::= { icmp 25 }
6342:
6343: icmpOutAddrMaskReps OBJECT-TYPE
6344: SYNTAX Counter
6345: ACCESS read-only
6346: STATUS mandatory
6347: ::= { icmp 26 }
6348:
6349:
6350: -- the TCP group
6351:
6352: tcpRtoAlgorithm OBJECT-TYPE
6353: SYNTAX INTEGER {
6354: other(1), -- none of the following
6355: constant(2), -- a constant rto
6356: rsre(3), -- MIL-STD-1778,
6357: -- Appendix B
6358: vanj(4) -- Van Jacobson's
6359: -- algorithm
6360: }
6361: ACCESS read-only
6362: STATUS mandatory
6363: ::= { tcp 1 }
6364:
6365: tcpRtoMin OBJECT-TYPE
6366: SYNTAX INTEGER
6367: ACCESS read-only
6368: STATUS mandatory
6369: ::= { tcp 2 }
6370:
6371: tcpRtoMax OBJECT-TYPE
6372: SYNTAX INTEGER
6373: ACCESS read-only
6374: STATUS mandatory
6375: ::= { tcp 3 }
6376:
6377: tcpMaxConn OBJECT-TYPE
6378: SYNTAX INTEGER
6379: ACCESS read-only
6380: STATUS mandatory
6381: ::= { tcp 4 }
6382:
6383:
6384:
6385:
6386: IETF SNMP Working Group [Page 114]
6387:
6388: RFC 1158 MIB II May 1990
6389:
6390:
6391: tcpActiveOpens OBJECT-TYPE
6392: SYNTAX Counter
6393: ACCESS read-only
6394: STATUS mandatory
6395: ::= { tcp 5 }
6396:
6397: tcpPassiveOpens OBJECT-TYPE
6398: SYNTAX Counter
6399: ACCESS read-only
6400: STATUS mandatory
6401: ::= { tcp 6 }
6402:
6403: tcpAttemptFails OBJECT-TYPE
6404: SYNTAX Counter
6405: ACCESS read-only
6406: STATUS mandatory
6407: ::= { tcp 7 }
6408:
6409: tcpEstabResets OBJECT-TYPE
6410: SYNTAX Counter
6411: ACCESS read-only
6412: STATUS mandatory
6413: ::= { tcp 8 }
6414:
6415: tcpCurrEstab OBJECT-TYPE
6416: SYNTAX Gauge
6417: ACCESS read-only
6418: STATUS mandatory
6419: ::= { tcp 9 }
6420:
6421: tcpInSegs OBJECT-TYPE
6422: SYNTAX Counter
6423: ACCESS read-only
6424: STATUS mandatory
6425: ::= { tcp 10 }
6426:
6427: tcpOutSegs OBJECT-TYPE
6428: SYNTAX Counter
6429: ACCESS read-only
6430: STATUS mandatory
6431: ::= { tcp 11 }
6432:
6433: tcpRetransSegs OBJECT-TYPE
6434: SYNTAX Counter
6435: ACCESS read-only
6436: STATUS mandatory
6437: ::= { tcp 12 }
6438:
6439:
6440:
6441:
6442: IETF SNMP Working Group [Page 115]
6443:
6444: RFC 1158 MIB II May 1990
6445:
6446:
6447: -- the TCP connections table
6448:
6449: tcpConnTable OBJECT-TYPE
6450: SYNTAX SEQUENCE OF TcpConnEntry
6451: ACCESS read-only
6452: STATUS mandatory
6453: ::= { tcp 13 }
6454:
6455: tcpConnEntry OBJECT-TYPE
6456: SYNTAX TcpConnEntry
6457: ACCESS read-only
6458: STATUS mandatory
6459: ::= { tcpConnTable 1 }
6460:
6461: TcpConnEntry ::= SEQUENCE {
6462: tcpConnState
6463: INTEGER,
6464: tcpConnLocalAddress
6465: IpAddress,
6466: tcpConnLocalPort
6467: INTEGER (0..65535),
6468: tcpConnRemAddress
6469: IpAddress,
6470: tcpConnRemPort
6471: INTEGER (0..65535)
6472: }
6473:
6474: tcpConnState OBJECT-TYPE
6475: SYNTAX INTEGER {
6476: closed(1),
6477: listen(2),
6478: synSent(3),
6479: synReceived(4),
6480: established(5),
6481: finWait1(6),
6482: finWait2(7),
6483: closeWait(8),
6484: lastAck(9),
6485: closing(10),
6486: timeWait(11)
6487: }
6488: ACCESS read-only
6489: STATUS mandatory
6490: ::= { tcpConnEntry 1 }
6491:
6492: tcpConnLocalAddress OBJECT-TYPE
6493: SYNTAX IpAddress
6494: ACCESS read-only
6495:
6496:
6497:
6498: IETF SNMP Working Group [Page 116]
6499:
6500: RFC 1158 MIB II May 1990
6501:
6502:
6503: STATUS mandatory
6504: ::= { tcpConnEntry 2 }
6505:
6506: tcpConnLocalPort OBJECT-TYPE
6507: SYNTAX INTEGER (0..65535)
6508: ACCESS read-only
6509: STATUS mandatory
6510: ::= { tcpConnEntry 3 }
6511:
6512: tcpConnRemAddress OBJECT-TYPE
6513: SYNTAX IpAddress
6514: ACCESS read-only
6515: STATUS mandatory
6516: ::= { tcpConnEntry 4 }
6517:
6518: tcpConnRemPort OBJECT-TYPE
6519: SYNTAX INTEGER (0..65535)
6520: ACCESS read-only
6521: STATUS mandatory
6522: ::= { tcpConnEntry 5 }
6523:
6524: -- additional TCP variables
6525:
6526: tcpInErrs OBJECT-TYPE
6527: SYNTAX Counter
6528: ACCESS read-only
6529: STATUS mandatory
6530: ::= { tcp 14 }
6531:
6532: tcpOutRsts OBJECT-TYPE
6533: SYNTAX Counter
6534: ACCESS read-only
6535: STATUS mandatory
6536: ::= { tcp 15 }
6537:
6538:
6539: -- the UDP group
6540:
6541: udpInDatagrams OBJECT-TYPE
6542: SYNTAX Counter
6543: ACCESS read-only
6544: STATUS mandatory
6545: ::= { udp 1 }
6546:
6547: udpNoPorts OBJECT-TYPE
6548: SYNTAX Counter
6549: ACCESS read-only
6550: STATUS mandatory
6551:
6552:
6553:
6554: IETF SNMP Working Group [Page 117]
6555:
6556: RFC 1158 MIB II May 1990
6557:
6558:
6559: ::= { udp 2 }
6560:
6561: udpInErrors OBJECT-TYPE
6562: SYNTAX Counter
6563: ACCESS read-only
6564: STATUS mandatory
6565: ::= { udp 3 }
6566:
6567: udpOutDatagrams OBJECT-TYPE
6568: SYNTAX Counter
6569: ACCESS read-only
6570: STATUS mandatory
6571: ::= { udp 4 }
6572:
6573: -- the UDP listener table
6574:
6575: udpTable OBJECT-TYPE
6576: SYNTAX SEQUENCE OF UdpEntry
6577: ACCESS read-only
6578: STATUS mandatory
6579: ::= { udp 5 }
6580:
6581: udpEntry OBJECT-TYPE
6582: SYNTAX UdpEntry
6583: ACCESS read-only
6584: STATUS mandatory
6585: ::= { udpTable 1 }
6586:
6587: UdpEntry ::= SEQUENCE {
6588: udpLocalAddress
6589: IpAddress,
6590: udpLocalPort
6591: INTEGER (0..65535)
6592: }
6593:
6594: udpLocalAddress OBJECT-TYPE
6595: SYNTAX IpAddress
6596: ACCESS read-only
6597: STATUS mandatory
6598: ::= { udpEntry 1 }
6599:
6600: udpLocalPort OBJECT-TYPE
6601: SYNTAX INTEGER (0..65535)
6602: ACCESS read-only
6603: STATUS mandatory
6604: ::= { udpEntry 2 }
6605:
6606:
6607:
6608:
6609:
6610: IETF SNMP Working Group [Page 118]
6611:
6612: RFC 1158 MIB II May 1990
6613:
6614:
6615: -- the EGP group
6616:
6617: egpInMsgs OBJECT-TYPE
6618: SYNTAX Counter
6619: ACCESS read-only
6620: STATUS mandatory
6621: ::= { egp 1 }
6622:
6623: egpInErrors OBJECT-TYPE
6624: SYNTAX Counter
6625: ACCESS read-only
6626: STATUS mandatory
6627: ::= { egp 2 }
6628:
6629: egpOutMsgs OBJECT-TYPE
6630: SYNTAX Counter
6631: ACCESS read-only
6632: STATUS mandatory
6633: ::= { egp 3 }
6634:
6635: egpOutErrors OBJECT-TYPE
6636: SYNTAX Counter
6637: ACCESS read-only
6638: STATUS mandatory
6639: ::= { egp 4 }
6640:
6641: -- the EGP Neighbor table
6642:
6643: egpNeighTable OBJECT-TYPE
6644: SYNTAX SEQUENCE OF EgpNeighEntry
6645: ACCESS read-only
6646: STATUS mandatory
6647: ::= { egp 5 }
6648:
6649: egpNeighEntry OBJECT-TYPE
6650: SYNTAX EgpNeighEntry
6651: ACCESS read-only
6652: STATUS mandatory
6653: ::= { egpNeighTable 1 }
6654:
6655: EgpNeighEntry ::= SEQUENCE {
6656: egpNeighState
6657: INTEGER,
6658: egpNeighAddr
6659: IpAddress,
6660: egpNeighAs
6661: INTEGER,
6662: egpNeighInMsgs
6663:
6664:
6665:
6666: IETF SNMP Working Group [Page 119]
6667:
6668: RFC 1158 MIB II May 1990
6669:
6670:
6671: Counter,
6672: egpNeighInErrs
6673: Counter,
6674: egpNeighOutMsgs
6675: Counter,
6676: egpNeighOutErrs
6677: Counter,
6678: egpNeighInErrMsgs
6679: Counter,
6680: egpNeighOutErrMsgs
6681: Counter,
6682: egpNeighStateUps
6683: Counter,
6684: egpNeighStateDowns
6685: Counter,
6686: egpNeighIntervalHello
6687: INTEGER,
6688: egpNeighIntervalPoll
6689: INTEGER,
6690: egpNeighMode
6691: INTEGER,
6692: egpNeighEventTrigger
6693: INTEGER
6694: }
6695:
6696: egpNeighState OBJECT-TYPE
6697: SYNTAX INTEGER {
6698: idle(1),
6699: acquisition(2),
6700: down(3),
6701: up(4),
6702: cease(5)
6703: }
6704: ACCESS read-only
6705: STATUS mandatory
6706: ::= { egpNeighEntry 1 }
6707:
6708: egpNeighAddr OBJECT-TYPE
6709: SYNTAX IpAddress
6710: ACCESS read-only
6711: STATUS mandatory
6712: ::= { egpNeighEntry 2 }
6713:
6714: egpNeighAs OBJECT-TYPE
6715: SYNTAX INTEGER
6716: ACCESS read-only
6717: STATUS mandatory
6718: ::= { egpNeighEntry 3 }
6719:
6720:
6721:
6722: IETF SNMP Working Group [Page 120]
6723:
6724: RFC 1158 MIB II May 1990
6725:
6726:
6727: egpNeighInMsgs OBJECT-TYPE
6728: SYNTAX Counter
6729: ACCESS read-only
6730: STATUS mandatory
6731: ::= { egpNeighEntry 4 }
6732:
6733: egpNeighInErrs OBJECT-TYPE
6734: SYNTAX Counter
6735: ACCESS read-only
6736: STATUS mandatory
6737: ::= { egpNeighEntry 5 }
6738:
6739: egpNeighOutMsgs OBJECT-TYPE
6740: SYNTAX Counter
6741: ACCESS read-only
6742: STATUS mandatory
6743: ::= { egpNeighEntry 6 }
6744:
6745: egpNeighOutErrs OBJECT-TYPE
6746: SYNTAX Counter
6747: ACCESS read-only
6748: STATUS mandatory
6749: ::= { egpNeighEntry 7 }
6750:
6751: egpNeighInErrMsgs OBJECT-TYPE
6752: SYNTAX Counter
6753: ACCESS read-only
6754: STATUS mandatory
6755: ::= { egpNeighEntry 8 }
6756:
6757: egpNeighOutErrMsgs OBJECT-TYPE
6758: SYNTAX Counter
6759: ACCESS read-only
6760: STATUS mandatory
6761: ::= { egpNeighEntry 9 }
6762:
6763: egpNeighStateUps OBJECT-TYPE
6764: SYNTAX Counter
6765: ACCESS read-only
6766: STATUS mandatory
6767: ::= { egpNeighEntry 10 }
6768:
6769: egpNeighStateDowns OBJECT-TYPE
6770: SYNTAX Counter
6771: ACCESS read-only
6772: STATUS mandatory
6773: ::= { egpNeighEntry 11 }
6774:
6775:
6776:
6777:
6778: IETF SNMP Working Group [Page 121]
6779:
6780: RFC 1158 MIB II May 1990
6781:
6782:
6783: egpNeighIntervalHello OBJECT-TYPE
6784: SYNTAX INTEGER
6785: ACCESS read-only
6786: STATUS mandatory
6787: ::= { egpNeighEntry 12 }
6788:
6789: egpNeighIntervalPoll OBJECT-TYPE
6790: SYNTAX INTEGER
6791: ACCESS read-only
6792: STATUS mandatory
6793: ::= { egpNeighEntry 13 }
6794:
6795: egpNeighMode OBJECT-TYPE
6796: SYNTAX INTEGER {
6797: active(1),
6798: passive(2)
6799: }
6800: ACCESS read-only
6801: STATUS mandatory
6802: ::= { egpNeighEntry 14 }
6803:
6804: egpNeighEventTrigger OBJECT-TYPE
6805: SYNTAX INTEGER {
6806: start(1),
6807: stop(2)
6808: }
6809: ACCESS read-write
6810: STATUS mandatory
6811: ::= { egpNeighEntry 15 }
6812:
6813: -- additional EGP variables
6814:
6815: egpAs OBJECT-TYPE
6816: SYNTAX INTEGER
6817: ACCESS read-only
6818: STATUS mandatory
6819: ::= { egp 6 }
6820:
6821:
6822: -- the Transmission group (empty at present)
6823:
6824: -- the SNMP group
6825:
6826: snmpInPkts OBJECT-TYPE
6827: SYNTAX Counter
6828: ACCESS read-only
6829: STATUS mandatory
6830: ::= { snmp 1 }
6831:
6832:
6833:
6834: IETF SNMP Working Group [Page 122]
6835:
6836: RFC 1158 MIB II May 1990
6837:
6838:
6839: snmpOutPkts OBJECT-TYPE
6840: SYNTAX Counter
6841: ACCESS read-only
6842: STATUS mandatory
6843: ::= { snmp 2 }
6844:
6845: snmpInBadVersions OBJECT-TYPE
6846: SYNTAX Counter
6847: ACCESS read-only
6848: STATUS mandatory
6849: ::= { snmp 3 }
6850:
6851: snmpInBadCommunityNames OBJECT-TYPE
6852: SYNTAX Counter
6853: ACCESS read-only
6854: STATUS mandatory
6855: ::= { snmp 4 }
6856:
6857: snmpInBadCommunityUses OBJECT-TYPE
6858: SYNTAX Counter
6859: ACCESS read-only
6860: STATUS mandatory
6861: ::= { snmp 5 }
6862:
6863: snmpInASNParseErrs OBJECT-TYPE
6864: SYNTAX Counter
6865: ACCESS read-only
6866: STATUS mandatory
6867: ::= { snmp 6 }
6868:
6869: snmpInBadTypes OBJECT-TYPE
6870: SYNTAX Counter
6871: ACCESS read-only
6872: STATUS mandatory
6873: ::= { snmp 7 }
6874:
6875: snmpInTooBigs OBJECT-TYPE
6876: SYNTAX Counter
6877: ACCESS read-only
6878: STATUS mandatory
6879: ::= { snmp 8 }
6880:
6881: snmpInNoSuchNames OBJECT-TYPE
6882: SYNTAX Counter
6883: ACCESS read-only
6884: STATUS mandatory
6885: ::= { snmp 9 }
6886:
6887:
6888:
6889:
6890: IETF SNMP Working Group [Page 123]
6891:
6892: RFC 1158 MIB II May 1990
6893:
6894:
6895: snmpInBadValues OBJECT-TYPE
6896: SYNTAX Counter
6897: ACCESS read-only
6898: STATUS mandatory
6899: ::= { snmp 10 }
6900:
6901: snmpInReadOnlys OBJECT-TYPE
6902: SYNTAX Counter
6903: ACCESS read-only
6904: STATUS mandatory
6905: ::= { snmp 11 }
6906:
6907: snmpInGenErrs OBJECT-TYPE
6908: SYNTAX Counter
6909: ACCESS read-only
6910: STATUS mandatory
6911: ::= { snmp 12 }
6912:
6913: snmpInTotalReqVars OBJECT-TYPE
6914: SYNTAX Counter
6915: ACCESS read-only
6916: STATUS mandatory
6917: ::= { snmp 13 }
6918:
6919: snmpInTotalSetVars OBJECT-TYPE
6920: SYNTAX Counter
6921: ACCESS read-only
6922: STATUS mandatory
6923: ::= { snmp 14 }
6924:
6925: snmpInGetRequests OBJECT-TYPE
6926: SYNTAX Counter
6927: ACCESS read-only
6928: STATUS mandatory
6929: ::= { snmp 15 }
6930:
6931: snmpInGetNexts OBJECT-TYPE
6932: SYNTAX Counter
6933: ACCESS read-only
6934: STATUS mandatory
6935: ::= { snmp 16 }
6936:
6937: snmpInSetRequests OBJECT-TYPE
6938: SYNTAX Counter
6939: ACCESS read-only
6940: STATUS mandatory
6941: ::= { snmp 17 }
6942:
6943:
6944:
6945:
6946: IETF SNMP Working Group [Page 124]
6947:
6948: RFC 1158 MIB II May 1990
6949:
6950:
6951: snmpInGetResponses OBJECT-TYPE
6952: SYNTAX Counter
6953: ACCESS read-only
6954: STATUS mandatory
6955: ::= { snmp 18 }
6956:
6957: snmpInTraps OBJECT-TYPE
6958: SYNTAX Counter
6959: ACCESS read-only
6960: STATUS mandatory
6961: ::= { snmp 19 }
6962:
6963: snmpOutTooBigs OBJECT-TYPE
6964: SYNTAX Counter
6965: ACCESS read-only
6966: STATUS mandatory
6967: ::= { snmp 20 }
6968:
6969: snmpOutNoSuchNames OBJECT-TYPE
6970: SYNTAX Counter
6971: ACCESS read-only
6972: STATUS mandatory
6973: ::= { snmp 21 }
6974:
6975: snmpOutBadValues OBJECT-TYPE
6976: SYNTAX Counter
6977: ACCESS read-only
6978: STATUS mandatory
6979: ::= { snmp 22 }
6980:
6981: snmpOutReadOnlys OBJECT-TYPE
6982: SYNTAX Counter
6983: ACCESS read-only
6984: STATUS mandatory
6985: ::= { snmp 23 }
6986:
6987: snmpOutGenErrs OBJECT-TYPE
6988: SYNTAX Counter
6989: ACCESS read-only
6990: STATUS mandatory
6991: ::= { snmp 24 }
6992:
6993: snmpOutGetRequests OBJECT-TYPE
6994: SYNTAX Counter
6995: ACCESS read-only
6996: STATUS mandatory
6997: ::= { snmp 25 }
6998:
6999:
7000:
7001:
7002: IETF SNMP Working Group [Page 125]
7003:
7004: RFC 1158 MIB II May 1990
7005:
7006:
7007: snmpOutGetNexts OBJECT-TYPE
7008: SYNTAX Counter
7009: ACCESS read-only
7010: STATUS mandatory
7011: ::= { snmp 26 }
7012:
7013: snmpOutSetRequests OBJECT-TYPE
7014: SYNTAX Counter
7015: ACCESS read-only
7016: STATUS mandatory
7017: ::= { snmp 27 }
7018:
7019: snmpOutGetResponses OBJECT-TYPE
7020: SYNTAX Counter
7021: ACCESS read-only
7022: STATUS mandatory
7023: ::= { snmp 28 }
7024:
7025: snmpOutTraps OBJECT-TYPE
7026: SYNTAX Counter
7027: ACCESS read-only
7028: STATUS mandatory
7029: ::= { snmp 29 }
7030:
7031: snmpEnableAuthTraps OBJECT-TYPE
7032: SYNTAX INTEGER {
7033: enabled(1),
7034: disabled(2)
7035: }
7036: ACCESS read-write
7037: STATUS mandatory
7038: ::= { snmp 30 }
7039:
7040: END
7041:
7042: 7. Identification of OBJECT instances for use with the SNMP
7043:
7044: The names for all object types in the MIB are defined explicitly
7045: either in the Internet-standard MIB or in other documents which
7046: conform to the naming conventions of the SMI. The SMI requires that
7047: conformant management protocols define mechanisms for identifying
7048: individual instances of those object types for a particular network
7049: element.
7050:
7051: Each instance of any object type defined in the MIB is identified in
7052: SNMP operations by a unique name called its "variable name." In
7053: general, the name of an SNMP variable is an OBJECT IDENTIFIER of the
7054: form x.y, where x is the name of a non-aggregate object type defined
7055:
7056:
7057:
7058: IETF SNMP Working Group [Page 126]
7059:
7060: RFC 1158 MIB II May 1990
7061:
7062:
7063: in the MIB and y is an OBJECT IDENTIFIER fragment that, in a way
7064: specific to the named object type, identifies the desired instance.
7065:
7066: This naming strategy admits the fullest exploitation of the semantics
7067: of the powerful SNMP get-next operator, because it assigns names for
7068: related variables so as to be contiguous in the lexicographical
7069: ordering of all variable names known in the MIB.
7070:
7071: The type-specific naming of object instances is defined below for a
7072: number of classes of object types. Instances of an object type to
7073: which none of the following naming conventions are applicable are
7074: named by OBJECT IDENTIFIERs of the form x.0, where x is the name of
7075: said object type in the MIB definition.
7076:
7077: For example, suppose one wanted to identify an instance of the
7078: variable sysDescr. The object class for sysDescr is:
7079:
7080: iso org dod internet mgmt mib system sysDescr
7081: 1 3 6 1 2 1 1 1
7082:
7083: Hence, the object type, x, would be 1.3.6.1.2.1.1.1 to which is
7084: appended an instance sub-identifier of 0. That is, 1.3.6.1.2.1.1.1.0
7085: identifies the one and only instance of sysDescr.
7086:
7087: 7.1. ifTable Object Type Names
7088:
7089: The name of a subnetwork interface, s, is the OBJECT IDENTIFIER value
7090: of the form i, where i has the value of that instance of the ifIndex
7091: object type associated with s. For each object type, t, for which
7092: the defined name, n, has a prefix of ifEntry, an instance, i, of t is
7093: named by an OBJECT IDENTIFIER of the form n.s, where s is the name of
7094: the subnetwork interface about which i represents information.
7095:
7096: For example, suppose one wanted to identify the instance of the
7097: variable ifType associated with interface 2. Accordingly, ifType.2
7098: would identify the desired instance.
7099:
7100: 7.2. atTable Object Type Names
7101:
7102: The name of an address translation entry, x, is an OBJECT IDENTIFIER
7103: of the form s.1.a.b.c.d, such that s is the value of that instance of
7104: the atIfIndex object type associated with x, the subidentifer "1"
7105: signifies the translation of an IP protocol address, and a.b.c.d is
7106: the IP address value (in the familiar "dot" notation) of that
7107: instance of the atNetAddress object type associated with x.
7108:
7109: For each object type, t, for which the defined name, n, has a prefix
7110: of atEntry, an instance, i, of t is named by an OBJECT IDENTIFIER of
7111:
7112:
7113:
7114: IETF SNMP Working Group [Page 127]
7115:
7116: RFC 1158 MIB II May 1990
7117:
7118:
7119: the form n.y, where y is the name of the address translation entry
7120: about which i represents information.
7121:
7122: For example, suppose one wanted to find the physical address of an
7123: entry in the address translation table (ARP cache) associated with an
7124: IP address of 89.1.1.42 and interface 3. Accordingly,
7125: atPhysAddress.3.1.89.1.1.42 would identify the desired instance.
7126:
7127: 7.3. ipAddrTable Object Type Names
7128:
7129: The name of an IP-addressable network element, x, is the OBJECT
7130: IDENTIFIER of the form a.b.c.d such that a.b.c.d is the value (in the
7131: familiar "dot" notation) of that instance of the ipAdEntAddr object
7132: type associated with x.
7133:
7134: For each object type, t, for which the defined name, n, has a prefix
7135: of ipAddrEntry, an instance, i, of t is named by an OBJECT IDENTIFIER
7136: of the form n.y, where y is the name of the IP- addressable network
7137: element about which i represents information.
7138:
7139: For example, suppose one wanted to find the network mask of an entry
7140: in the IP interface table associated with an IP address of 89.1.1.42.
7141: Accordingly, ipAdEntNetMask.89.1.1.42 would identify the desired
7142: instance.
7143:
7144: At the option of the agent, multiple entries for the same IP address
7145: may be visible. To realize this, the agent, while required to return
7146: a single entry for an IP address, x, of the form n.y, may also return
7147: information about other entries for the same IP address using the
7148: form n.y.z, where z is a implementation-dependendent small, non-
7149: negative integer. It is strongly recommended that the value of z
7150: correspond to the value of ipAddrIfIndex for that entry.
7151:
7152: 7.4. ipRoutingTable Object Type Names
7153:
7154: The name of an IP route, x, is the OBJECT IDENTIFIER of the form
7155: a.b.c.d such that a.b.c.d is the value (in the familiar "dot"
7156: notation) of that instance of the ipRouteDest object type associated
7157: with x.
7158:
7159: For each object type, t, for which the defined name, n, has a prefix
7160: of ipRoutingEntry, an instance, i, of t is named by an OBJECT
7161: IDENTIFIER of the form n.y, where y is the name of the IP route about
7162: which i represents information.
7163:
7164: For example, suppose one wanted to find the next hop of an entry in
7165: the IP routing table associated with the destination of 89.1.1.42.
7166: Accordingly, ipRouteNextHop.89.1.1.42 would identify the desired
7167:
7168:
7169:
7170: IETF SNMP Working Group [Page 128]
7171:
7172: RFC 1158 MIB II May 1990
7173:
7174:
7175: instance.
7176:
7177: At the option of the agent, multiple routes to the same destination
7178: may be visible. To realize this, the agent, while required to return
7179: a single entry for an IP route, x, of the form n.y, may also return
7180: information about other routes to the same destination using the form
7181: n.y.z, where z is a implementation-dependendent small, non-negative
7182: integer.
7183:
7184: 7.5. ipNetToMediaTable Object Type Names
7185:
7186: The name of a cached IP address, x, is an OBJECT IDENTIFIER of the
7187: form s.a.b.c.d, such that s is the value of that instance of the
7188: ipNetToMediaIfIndex object type associated with the entry and a.b.c.d
7189: is the value (in the familiar "dot" notation) of the
7190: ipNetToMediaNetAddress object type associated with x.
7191:
7192: For each object type, t, for which the defined name, n, has a prefix
7193: of ipNetToMediaEntry, an instance, i, of t is named by an OBJECT
7194: IDENTIFIER of the form n.y, where y is the name of the cached IP
7195: address about which i represents information.
7196:
7197: For example, suppose one wanted to find the media address of an entry
7198: in the address translation table associated with a IP address of
7199: 192.52.180.1 and interface 3. Accordingly,
7200: ipNetToMediaPhysAddress.3.192.52.180.1 would identify the desired
7201: instance.
7202:
7203: 7.6. tcpConnTable Object Type Names
7204:
7205: The name of a TCP connection, x, is the OBJECT IDENTIFIER of the form
7206: a.b.c.d.e.f.g.h.i.j such that a.b.c.d is the value (in the familiar
7207: "dot" notation) of that instance of the tcpConnLocalAddress object
7208: type associated with x and such that f.g.h.i is the value (in the
7209: familiar "dot" notation) of that instance of the tcpConnRemoteAddress
7210: object type associated with x and such that e is the value of that
7211: instance of the tcpConnLocalPort object type associated with x and
7212: such that j is the value of that instance of the tcpConnRemotePort
7213: object type associated with x.
7214:
7215: For each object type, t, for which the defined name, n, has a prefix
7216: of tcpConnEntry, an instance, i, of t is named by an OBJECT
7217: IDENTIFIER of the form n.y, where y is the name of the TCP connection
7218: about which i represents information.
7219:
7220: For example, suppose one wanted to find the state of a TCP connection
7221: between the local address of 89.1.1.42 on TCP port 21 and the remote
7222: address of 10.0.0.51 on TCP port 2059. Accordingly,
7223:
7224:
7225:
7226: IETF SNMP Working Group [Page 129]
7227:
7228: RFC 1158 MIB II May 1990
7229:
7230:
7231: tcpConnState.89.1.1.42.21.10.0.0.51.2059 would identify the desired
7232: instance.
7233:
7234: 7.7. udpTable Object Type Names
7235:
7236: The name of a UDP listener, x, is the OBJECT IDENTIFIER of the form
7237: a.b.c.d.e. such that a.b.c.d is the value (in the familiar "dot"
7238: notation) of that instance of the udpLocalAddress object type
7239: associated with x and such that e is the value of that instance of
7240: the udpLocalPort object type associated with x.
7241:
7242: For each object type, t, for which the defined name, n, has a prefix
7243: of udpEntry, an instance, i, of t is named by an OBJECT IDENTIFIER of
7244: the form n.y, where y is the name of the UDP listener about which i
7245: represents information.
7246:
7247: For example, suppose one wanted to determine if a UDP listener was
7248: present at the local address of 89.1.1.42 on UDP port 21.
7249: Accordingly, a successful retrieval of either
7250: udpLocalAddress.89.1.1.42.21 or udpLocalPort.89.1.1.42.21 would
7251: indicate this.
7252:
7253: 7.8. egpNeighTable Object Type Names
7254:
7255: The name of an EGP neighbor, x, is the OBJECT IDENTIFIER of the form
7256: a.b.c.d such that a.b.c.d is the value (in the familiar "dot"
7257: notation) of that instance of the egpNeighAddr object type associated
7258: with x.
7259:
7260: For each object type, t, for which the defined name, n, has a prefix
7261: of egpNeighEntry, an instance, i, of t is named by an OBJECT
7262: IDENTIFIER of the form n.y, where y is the name of the EGP neighbor
7263: about which i represents information.
7264:
7265: For example, suppose one wanted to find the neighbor state for the IP
7266: address of 89.1.1.42. Accordingly, egpNeighState.89.1.1.42 would
7267: identify the desired instance.
7268:
7269: 8. Acknowledgements
7270:
7271: This document was produced by the SNMP Working Group:
7272:
7273: Karl Auerbach, Epilogue Technology
7274: David Bridgham, Epilogue Technology
7275: Brian Brown, Synoptics
7276: John Burress, Wellfleet
7277: Jeffrey D. Case, University of Tennessee at Knoxville
7278: James R. Davin, MIT-LCS
7279:
7280:
7281:
7282: IETF SNMP Working Group [Page 130]
7283:
7284: RFC 1158 MIB II May 1990
7285:
7286:
7287: Mark S. Fedor, PSI, Inc.
7288: Stan Froyd, ACC
7289: Satish Joshi, Synoptics
7290: Ken Key, University of Tennessee at Knoxville
7291: Gary Malkin, Proteon
7292: Randy Mayhew, University of Tennessee at Knoxville
7293: Keith McCloghrie, Hughes LAN Systems
7294: Marshall T. Rose, PSI, Inc. (chair)
7295: Greg Satz, cisco
7296: Martin Lee Schoffstall, PSI, Inc.
7297: Bob Stewart, Xyplex
7298: Geoff Thompson, Synoptics
7299: Bill Versteeg, Network Research Corporation
7300: Wengyik Yeong, PSI, Inc.
7301:
7302: In addition, the comments of the following individuals are also
7303: acknolwedged:
7304:
7305: Craig A. Finseth, Minnesota Supercomputer Center, Inc.
7306: Jeffrey C. Honig, Cornell University Theory Center
7307: Philip R. Karn, Bellcore
7308: David Waitzman, BBN
7309:
7310: 9. References
7311:
7312: [1] Cerf, V., "IAB Recommendations for the Development of Internet
7313: Network Management Standards", RFC 1052, IAB, April 1988.
7314:
7315: [2] Rose, M., and K. McCloghrie, "Structure and Identification of
7316: Management Information for TCP/IP-based internets", RFC 1065,
7317: TWG, August 1988.
7318:
7319: [3] McCloghrie K., and M. Rose,"Management Information Base for
7320: Network Management of TCP/IP-based internets", RFC 1066, TWG,
7321: August 1988.
7322:
7323: [4] Cerf, V., "Report of the Second Ad Hoc Network Management Review
7324: Group", RFC 1109, IAB, August 1989.
7325:
7326: [5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple
7327: Network Management Protocol (SNMP)", RFC 1098, University of
7328: Tennessee at Knoxville, NYSERNet, Inc., Rensselaer Polytechnic
7329: Institute, MIT Laboratory for Computer Science, April 1989.
7330:
7331: [6] Warrier, U., and L. Besaw, "Common Management Information
7332: Services and Protocol over TCP/IP (CMOT)", RFC 1095, Unisys
7333: Corporation, Hewlett-Packard, April 1989.
7334:
7335:
7336:
7337:
7338: IETF SNMP Working Group [Page 131]
7339:
7340: RFC 1158 MIB II May 1990
7341:
7342:
7343: [7] Postel, J., "Telnet Protocol Specification", RFC 854,
7344: USC/Information Sciences Institute, May 1983.
7345:
7346: [8] Satz, G., "Experimental MIB Objects for the CLNP", Internet
7347: Working Group Request for Comments draft. Network Information
7348: Center, SRI International, Menlo Park, California, (in
7349: preparation).
7350:
7351: [9] Information processing systems - Open Systems Interconnection,
7352: "Specification of Abstract Syntax Notation One (ASN.1)",
7353: International Organization for Standardization, International
7354: Standard 8824, December 1987.
7355:
7356: [10] Information processing systems - Open Systems Interconnection,
7357: "Specification of Basic Encoding Rules for Abstract Notation One
7358: (ASN.1)", International Organization for Standardization.
7359: International Standard 8825, December 1987.
7360:
7361: [11] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1988,
7362: Stanford, California.
7363:
7364: [12] Hagens, R., Hall, N., and M. Rose, "Use of the Internet as a
7365: subnetwork for experimentation with the OSI network layer",
7366: February, 1989.
7367:
7368: [13] Rose, M., and K. McCloghrie, "Structure and Identification of
7369: Management Information for TCP/IP-based Internets", RFC 1155,
7370: Performance Systems International and Hughes LAN Systems, May
7371: 1990.
7372:
7373: [14] Case, J., Fedor, M., Schoffstall, M., and J. Davin, The Simple
7374: Network Management Protocol", RFC 1157, University of Tennessee
7375: at Knoxville, Performance Systems International, Performance
7376: Systems International, and the MIT Laboratory for Computer
7377: Science, May 1990.
7378:
7379:
7380:
7381:
7382:
7383:
7384:
7385:
7386:
7387:
7388:
7389:
7390:
7391:
7392:
7393:
7394: IETF SNMP Working Group [Page 132]
7395:
7396: RFC 1158 MIB II May 1990
7397:
7398:
7399: 10. Security Considerations
7400:
7401: Security issues are not discussed in this memo.
7402:
7403: 11. Author's Address:
7404:
7405: Marshall T. Rose
7406: PSI, Inc.
7407: PSI California Office
7408: P.O. Box 391776
7409: Mountain View, CA 94039
7410:
7411: Phone: (415) 961-3380
7412:
7413: Email: [email protected]
7414:
7415:
7416:
7417:
7418:
7419:
7420:
7421:
7422:
7423:
7424:
7425:
7426:
7427:
7428:
7429:
7430:
7431:
7432:
7433:
7434:
7435:
7436:
7437:
7438:
7439:
7440:
7441:
7442:
7443:
7444:
7445:
7446:
7447:
7448:
7449:
7450: IETF SNMP Working Group [Page 133]
7451:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.