idnits 2.17.1 draft-ietf-snmpv2-ip-ds-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' ** Obsolete normative reference: RFC 1354 (ref. '6') (Obsoleted by RFC 2096) Summary: 11 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 SNMPv2 Management Information Base 2 for the Internet Protocol 4 Fri Jun 30 23:59:59 1995 6 draft-ietf-snmpv2-ip-ds-02.txt 8 Jeffrey D. Case 9 SNMP Research, Inc. 10 case@snmp.com 12 Keith McCloghrie 13 Cisco Systems, Inc. 14 kzm@cisco.com 16 Marshall T. Rose 17 Dover Beach Consulting, Inc. 18 mrose@dbc.mtview.ca.us 20 Steven Waldbusser 21 Carnegie Mellon University 22 waldbusser@cmu.edu 24 Status of this Memo 26 This document is an Internet-Draft. Internet-Drafts are working 27 documents of the Internet Engineering Task Force (IETF), its areas, and 28 its working groups. Note that other groups may also distribute working 29 documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet- Drafts as reference material 34 or to cite them other than as ``work in progress.'' 36 To learn the current status of any Internet-Draft, please check the 37 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 38 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 39 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 41 1. Introduction 43 A management system contains: several (potentially many) nodes, each 44 with a processing entity, termed an agent, which has access to 45 management instrumentation; at least one management station; and, a 46 management protocol, used to convey management information between the 47 agents and management stations. Operations of the protocol are carried 48 out under an administrative framework which defines authentication, 49 authorization, access control, and privacy policies. 51 Management stations execute management applications which monitor and 52 control managed elements. Managed elements are devices such as hosts, 53 routers, terminal servers, etc., which are monitored and controlled via 54 access to their management information. 56 Management information is viewed as a collection of managed objects, 57 residing in a virtual information store, termed the Management 58 Information Base (MIB). Collections of related objects are defined in 59 MIB modules. These modules are written using a subset of OSI's Abstract 60 Syntax Notation One (ASN.1) [1], termed the Structure of Management 61 Information (SMI) [2]. 63 This document is the MIB module which defines managed objects for 64 managing implementations of the Internet Protocol (IP) [3] and its 65 associated Internet Control Message Protocol (ICMP) [4]. 67 The managed objects in this MIB module were originally defined using the 68 SNMPv1 framework as a part of MIB-II [5]. Since then, the managed 69 objects related to managing routes in an IP internet were updated by RFC 70 1354 [6]. This document takes the remaining MIB-II objects for these 71 protocols, and defines them using the SNMPv2 framework. 73 2. Definitions 75 IP-MIB DEFINITIONS ::= BEGIN 77 IMPORTS 78 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 79 experimental, -- to be removed later 80 Counter32, IpAddress, mib-2 FROM SNMPv2-SMI 81 PhysAddress FROM SNMPv2-TC 82 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 84 ipMIB MODULE-IDENTITY 85 LAST-UPDATED "9411010000Z" 86 ORGANIZATION "IETF SNMPv2 Working Group" 87 CONTACT-INFO 88 " Keith McCloghrie 90 Postal: Cisco Systems, Inc. 91 170 West Tasman Drive 92 San Jose, CA 95134-1706 93 US 95 Phone: +1 408 526 5260 96 Email: kzm@cisco.com" 97 DESCRIPTION 98 "The MIB module for managing IP and ICMP implementations, 99 but excluding their management of IP routes." 100 REVISION "9103310000Z" 101 DESCRIPTION 102 "The initial revision of this MIB module was part of MIB- 103 II." 104 ::= { experimental xx } -- to be assigned as {mib-2 xx} by IANA 106 -- the IP group 108 ip OBJECT IDENTIFIER ::= { mib-2 4 } 110 ipForwarding OBJECT-TYPE 111 SYNTAX INTEGER { 112 forwarding(1), -- acting as a router 113 notForwarding(2) -- NOT acting as a router 114 } 115 MAX-ACCESS read-write 116 STATUS current 117 DESCRIPTION 118 "The indication of whether this entity is acting as an IP 119 router in respect to the forwarding of datagrams received 120 by, but not addressed to, this entity. IP routers forward 121 datagrams. IP hosts do not (except those source-routed via 122 the host)." 123 ::= { ip 1 } 125 ipDefaultTTL OBJECT-TYPE 126 SYNTAX INTEGER (1..255) 127 MAX-ACCESS read-write 128 STATUS current 129 DESCRIPTION 130 "The default value inserted into the Time-To-Live field of 131 the IP header of datagrams originated at this entity, 132 whenever a TTL value is not supplied by the transport layer 133 protocol." 134 ::= { ip 2 } 136 ipInReceives OBJECT-TYPE 137 SYNTAX Counter32 138 MAX-ACCESS read-only 139 STATUS current 140 DESCRIPTION 141 "The total number of input datagrams received from 142 interfaces, including those received in error." 143 ::= { ip 3 } 145 ipInHdrErrors OBJECT-TYPE 146 SYNTAX Counter32 147 MAX-ACCESS read-only 148 STATUS current 149 DESCRIPTION 150 "The number of input datagrams discarded due to errors in 151 their IP headers, including bad checksums, version number 152 mismatch, other format errors, time-to-live exceeded, errors 153 discovered in processing their IP options, etc." 154 ::= { ip 4 } 156 ipInAddrErrors OBJECT-TYPE 157 SYNTAX Counter32 158 MAX-ACCESS read-only 159 STATUS current 160 DESCRIPTION 161 "The number of input datagrams discarded because the IP 162 address in their IP header's destination field was not a 163 valid address to be received at this entity. This count 164 includes invalid addresses (e.g., 0.0.0.0) and addresses of 165 unsupported Classes (e.g., Class E). For entities which are 166 not IP routers and therefore do not forward datagrams, this 167 counter includes datagrams discarded because the destination 168 address was not a local address." 169 ::= { ip 5 } 171 ipForwDatagrams OBJECT-TYPE 172 SYNTAX Counter32 173 MAX-ACCESS read-only 174 STATUS current 175 DESCRIPTION 176 "The number of input datagrams for which this entity was not 177 their final IP destination, as a result of which an attempt 178 was made to find a route to forward them to that final 179 destination. In entities which do not act as IP routers, 180 this counter will include only those packets which were 181 Source-Routed via this entity, and the Source-Route option 182 processing was successful." 183 ::= { ip 6 } 185 ipInUnknownProtos OBJECT-TYPE 186 SYNTAX Counter32 187 MAX-ACCESS read-only 188 STATUS current 189 DESCRIPTION 190 "The number of locally-addressed datagrams received 191 successfully but discarded because of an unknown or 192 unsupported protocol." 193 ::= { ip 7 } 195 ipInDiscards OBJECT-TYPE 196 SYNTAX Counter32 197 MAX-ACCESS read-only 198 STATUS current 199 DESCRIPTION 200 "The number of input IP datagrams for which no problems were 201 encountered to prevent their continued processing, but which 202 were discarded (e.g., for lack of buffer space). Note that 203 this counter does not include any datagrams discarded while 204 awaiting re-assembly." 205 ::= { ip 8 } 207 ipInDelivers OBJECT-TYPE 208 SYNTAX Counter32 209 MAX-ACCESS read-only 210 STATUS current 211 DESCRIPTION 212 "The total number of input datagrams successfully delivered 213 to IP user-protocols (including ICMP)." 214 ::= { ip 9 } 216 ipOutRequests OBJECT-TYPE 217 SYNTAX Counter32 218 MAX-ACCESS read-only 219 STATUS current 220 DESCRIPTION 221 "The total number of IP datagrams which local IP user- 222 protocols (including ICMP) supplied to IP in requests for 223 transmission. Note that this counter does not include any 224 datagrams counted in ipForwDatagrams." 225 ::= { ip 10 } 227 ipOutDiscards OBJECT-TYPE 228 SYNTAX Counter32 229 MAX-ACCESS read-only 230 STATUS current 231 DESCRIPTION 232 "The number of output IP datagrams for which no problem was 233 encountered to prevent their transmission to their 234 destination, but which were discarded (e.g., for lack of 235 buffer space). Note that this counter would include 236 datagrams counted in ipForwDatagrams if any such packets met 237 this (discretionary) discard criterion." 238 ::= { ip 11 } 240 ipOutNoRoutes OBJECT-TYPE 241 SYNTAX Counter32 242 MAX-ACCESS read-only 243 STATUS current 244 DESCRIPTION 245 "The number of IP datagrams discarded because no route could 246 be found to transmit them to their destination. Note that 247 this counter includes any packets counted in ipForwDatagrams 248 which meet this `no-route' criterion. Note that this 249 includes any datagrams which a host cannot route because all 250 of its default routers are down." 251 ::= { ip 12 } 253 ipReasmTimeout OBJECT-TYPE 254 SYNTAX Integer32 255 MAX-ACCESS read-only 256 STATUS current 257 DESCRIPTION 258 "The maximum number of seconds which received fragments are 259 held while they are awaiting reassembly at this entity." 260 ::= { ip 13 } 262 ipReasmReqds OBJECT-TYPE 263 SYNTAX Counter32 264 MAX-ACCESS read-only 265 STATUS current 266 DESCRIPTION 267 "The number of IP fragments received which needed to be 268 reassembled at this entity." 269 ::= { ip 14 } 271 ipReasmOKs OBJECT-TYPE 272 SYNTAX Counter32 273 MAX-ACCESS read-only 274 STATUS current 275 DESCRIPTION 276 "The number of IP datagrams successfully re-assembled." 277 ::= { ip 15 } 279 ipReasmFails OBJECT-TYPE 280 SYNTAX Counter32 281 MAX-ACCESS read-only 282 STATUS current 283 DESCRIPTION 284 "The number of failures detected by the IP re-assembly 285 algorithm (for whatever reason: timed out, errors, etc). 287 Note that this is not necessarily a count of discarded IP 288 fragments since some algorithms (notably the algorithm in 289 RFC 815) can lose track of the number of fragments by 290 combining them as they are received." 291 ::= { ip 16 } 293 ipFragOKs OBJECT-TYPE 294 SYNTAX Counter32 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "The number of IP datagrams that have been successfully 299 fragmented at this entity." 300 ::= { ip 17 } 302 ipFragFails OBJECT-TYPE 303 SYNTAX Counter32 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "The number of IP datagrams that have been discarded because 308 they needed to be fragmented at this entity but could not 309 be, e.g., because their Don't Fragment flag was set." 310 ::= { ip 18 } 312 ipFragCreates OBJECT-TYPE 313 SYNTAX Counter32 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The number of IP datagram fragments that have been 318 generated as a result of fragmentation at this entity." 319 ::= { ip 19 } 321 -- the IP address table 323 ipAddrTable OBJECT-TYPE 324 SYNTAX SEQUENCE OF IpAddrEntry 325 MAX-ACCESS not-accessible 326 STATUS current 327 DESCRIPTION 328 "The table of addressing information relevant to this 329 entity's IP addresses." 330 ::= { ip 20 } 332 ipAddrEntry OBJECT-TYPE 333 SYNTAX IpAddrEntry 334 MAX-ACCESS not-accessible 335 STATUS current 336 DESCRIPTION 337 "The addressing information for one of this entity's IP 338 addresses." 339 INDEX { ipAdEntAddr } 340 ::= { ipAddrTable 1 } 342 IpAddrEntry ::= SEQUENCE { 343 ipAdEntAddr IpAddress, 344 ipAdEntIfIndex INTEGER, 345 ipAdEntNetMask IpAddress, 346 ipAdEntBcastAddr INTEGER, 347 ipAdEntReasmMaxSize INTEGER 348 } 350 ipAdEntAddr OBJECT-TYPE 351 SYNTAX IpAddress 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The IP address to which this entry's addressing information 356 pertains." 357 ::= { ipAddrEntry 1 } 359 ipAdEntIfIndex OBJECT-TYPE 360 SYNTAX INTEGER (1..2147483647) 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The index value which uniquely identifies the interface to 365 which this entry is applicable. The interface identified by 366 a particular value of this index is the same interface as 367 identified by the same value of RFC 1573's ifIndex." 368 ::= { ipAddrEntry 2 } 370 ipAdEntNetMask OBJECT-TYPE 371 SYNTAX IpAddress 372 MAX-ACCESS read-only 373 STATUS current 374 DESCRIPTION 375 "The subnet mask associated with the IP address of this 376 entry. The value of the mask is an IP address with all the 377 network bits set to 1 and all the hosts bits set to 0." 378 ::= { ipAddrEntry 3 } 380 ipAdEntBcastAddr OBJECT-TYPE 381 SYNTAX INTEGER (0..1) 382 MAX-ACCESS read-only 383 STATUS current 384 DESCRIPTION 385 "The value of the least-significant bit in the IP broadcast 386 address used for sending datagrams on the (logical) 387 interface associated with the IP address of this entry. For 388 example, when the Internet standard all-ones broadcast 389 address is used, the value will be 1. This value applies to 390 both the subnet and network broadcasts addresses used by the 391 entity on this (logical) interface." 392 ::= { ipAddrEntry 4 } 394 ipAdEntReasmMaxSize OBJECT-TYPE 395 SYNTAX INTEGER (0..65535) 396 MAX-ACCESS read-only 397 STATUS current 398 DESCRIPTION 399 "The size of the largest IP datagram which this entity can 400 re-assemble from incoming IP fragmented datagrams received 401 on this interface." 402 ::= { ipAddrEntry 5 } 404 -- ipRouteTable ::= { ip 21 } obsolete 405 -- the IP Address Translation table 407 -- The Address Translation tables contain the IpAddress to 408 -- "physical" address equivalences. Some interfaces do not 409 -- use translation tables for determining address 410 -- equivalences (e.g., DDN-X.25 has an algorithmic method); 411 -- if all interfaces are of this type, then the Address 412 -- Translation table is empty, i.e., has zero entries. 414 ipNetToMediaTable OBJECT-TYPE 415 SYNTAX SEQUENCE OF IpNetToMediaEntry 416 MAX-ACCESS not-accessible 417 STATUS current 418 DESCRIPTION 419 "The IP Address Translation table used for mapping from IP 420 addresses to physical addresses." 421 ::= { ip 22 } 423 ipNetToMediaEntry OBJECT-TYPE 424 SYNTAX IpNetToMediaEntry 425 MAX-ACCESS not-accessible 426 STATUS current 427 DESCRIPTION 428 "Each entry contains one IpAddress to `physical' address 429 equivalence." 430 INDEX { ipNetToMediaIfIndex, 431 ipNetToMediaNetAddress } 432 ::= { ipNetToMediaTable 1 } 434 IpNetToMediaEntry ::= SEQUENCE { 435 ipNetToMediaIfIndex INTEGER, 436 ipNetToMediaPhysAddress PhysAddress, 437 ipNetToMediaNetAddress IpAddress, 438 ipNetToMediaType INTEGER 439 } 441 ipNetToMediaIfIndex OBJECT-TYPE 442 SYNTAX INTEGER (1..2147483647) 443 MAX-ACCESS read-write 444 STATUS current 445 DESCRIPTION 446 "The interface on which this entry's equivalence is 447 effective. The interface identified by a particular value 448 of this index is the same interface as identified by the 449 same value of RFC 1573's ifIndex." 451 ::= { ipNetToMediaEntry 1 } 453 ipNetToMediaPhysAddress OBJECT-TYPE 454 SYNTAX PhysAddress 455 MAX-ACCESS read-write 456 STATUS current 457 DESCRIPTION 458 "The media-dependent `physical' address." 459 ::= { ipNetToMediaEntry 2 } 461 ipNetToMediaNetAddress OBJECT-TYPE 462 SYNTAX IpAddress 463 MAX-ACCESS read-write 464 STATUS current 465 DESCRIPTION 466 "The IpAddress corresponding to the media-dependent 467 `physical' address." 468 ::= { ipNetToMediaEntry 3 } 470 ipNetToMediaType OBJECT-TYPE 471 SYNTAX INTEGER { 472 other(1), -- none of the following 473 invalid(2), -- an invalidated mapping 474 dynamic(3), 475 static(4) 476 } 477 MAX-ACCESS read-write 478 STATUS current 479 DESCRIPTION 480 "The type of mapping. 482 Setting this object to the value invalid(2) has the effect 483 of invalidating the corresponding entry in the 484 ipNetToMediaTable. That is, it effectively disassociates 485 the interface identified with said entry from the mapping 486 identified with said entry. It is an implementation- 487 specific matter as to whether the agent removes an 488 invalidated entry from the table. Accordingly, management 489 stations must be prepared to receive tabular information 490 from agents that corresponds to entries not currently in 491 use. Proper interpretation of such entries requires 492 examination of the relevant ipNetToMediaType object." 493 ::= { ipNetToMediaEntry 4 } 495 ipRoutingDiscards OBJECT-TYPE 496 SYNTAX Counter32 497 MAX-ACCESS read-only 498 STATUS current 499 DESCRIPTION 500 "The number of routing entries which were chosen to be 501 discarded even though they are valid. One possible reason 502 for discarding such an entry could be to free-up buffer 503 space for other routing entries." 504 ::= { ip 23 } 506 -- the ICMP group 508 icmp OBJECT IDENTIFIER ::= { mib-2 5 } 510 icmpInMsgs OBJECT-TYPE 511 SYNTAX Counter32 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The total number of ICMP messages which the entity 516 received. Note that this counter includes all those counted 517 by icmpInErrors." 518 ::= { icmp 1 } 520 icmpInErrors OBJECT-TYPE 521 SYNTAX Counter32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The number of ICMP messages which the entity received but 526 determined as having ICMP-specific errors (bad ICMP 527 checksums, bad length, etc.)." 528 ::= { icmp 2 } 530 icmpInDestUnreachs OBJECT-TYPE 531 SYNTAX Counter32 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "The number of ICMP Destination Unreachable messages 536 received." 537 ::= { icmp 3 } 539 icmpInTimeExcds OBJECT-TYPE 540 SYNTAX Counter32 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "The number of ICMP Time Exceeded messages received." 545 ::= { icmp 4 } 547 icmpInParmProbs OBJECT-TYPE 548 SYNTAX Counter32 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "The number of ICMP Parameter Problem messages received." 553 ::= { icmp 5 } 555 icmpInSrcQuenchs OBJECT-TYPE 556 SYNTAX Counter32 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The number of ICMP Source Quench messages received." 561 ::= { icmp 6 } 563 icmpInRedirects OBJECT-TYPE 564 SYNTAX Counter32 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION 568 "The number of ICMP Redirect messages received." 569 ::= { icmp 7 } 571 icmpInEchos OBJECT-TYPE 572 SYNTAX Counter32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The number of ICMP Echo (request) messages received." 577 ::= { icmp 8 } 579 icmpInEchoReps OBJECT-TYPE 580 SYNTAX Counter32 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The number of ICMP Echo Reply messages received." 585 ::= { icmp 9 } 587 icmpInTimestamps OBJECT-TYPE 588 SYNTAX Counter32 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "The number of ICMP Timestamp (request) messages received." 593 ::= { icmp 10 } 595 icmpInTimestampReps OBJECT-TYPE 596 SYNTAX Counter32 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The number of ICMP Timestamp Reply messages received." 601 ::= { icmp 11 } 603 icmpInAddrMasks OBJECT-TYPE 604 SYNTAX Counter32 605 MAX-ACCESS read-only 606 STATUS current 607 DESCRIPTION 608 "The number of ICMP Address Mask Request messages received." 609 ::= { icmp 12 } 611 icmpInAddrMaskReps OBJECT-TYPE 612 SYNTAX Counter32 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "The number of ICMP Address Mask Reply messages received." 617 ::= { icmp 13 } 619 icmpOutMsgs OBJECT-TYPE 620 SYNTAX Counter32 621 MAX-ACCESS read-only 622 STATUS current 623 DESCRIPTION 624 "The total number of ICMP messages which this entity 625 attempted to send. Note that this counter includes all 626 those counted by icmpOutErrors." 627 ::= { icmp 14 } 629 icmpOutErrors OBJECT-TYPE 630 SYNTAX Counter32 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "The number of ICMP messages which this entity did not send 635 due to problems discovered within ICMP such as a lack of 636 buffers. This value should not include errors discovered 637 outside the ICMP layer such as the inability of IP to route 638 the resultant datagram. In some implementations there may 639 be no types of error which contribute to this counter's 640 value." 642 ::= { icmp 15 } 644 icmpOutDestUnreachs OBJECT-TYPE 645 SYNTAX Counter32 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "The number of ICMP Destination Unreachable messages sent." 650 ::= { icmp 16 } 652 icmpOutTimeExcds OBJECT-TYPE 653 SYNTAX Counter32 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "The number of ICMP Time Exceeded messages sent." 658 ::= { icmp 17 } 660 icmpOutParmProbs OBJECT-TYPE 661 SYNTAX Counter32 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The number of ICMP Parameter Problem messages sent." 666 ::= { icmp 18 } 668 icmpOutSrcQuenchs OBJECT-TYPE 669 SYNTAX Counter32 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "The number of ICMP Source Quench messages sent." 674 ::= { icmp 19 } 676 icmpOutRedirects OBJECT-TYPE 677 SYNTAX Counter32 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "The number of ICMP Redirect messages sent. For a host, 682 this object will always be zero, since hosts do not send 683 redirects." 684 ::= { icmp 20 } 686 icmpOutEchos OBJECT-TYPE 687 SYNTAX Counter32 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "The number of ICMP Echo (request) messages sent." 692 ::= { icmp 21 } 694 icmpOutEchoReps OBJECT-TYPE 695 SYNTAX Counter32 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "The number of ICMP Echo Reply messages sent." 700 ::= { icmp 22 } 702 icmpOutTimestamps OBJECT-TYPE 703 SYNTAX Counter32 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "The number of ICMP Timestamp (request) messages sent." 708 ::= { icmp 23 } 710 icmpOutTimestampReps OBJECT-TYPE 711 SYNTAX Counter32 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The number of ICMP Timestamp Reply messages sent." 716 ::= { icmp 24 } 718 icmpOutAddrMasks OBJECT-TYPE 719 SYNTAX Counter32 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "The number of ICMP Address Mask Request messages sent." 724 ::= { icmp 25 } 726 icmpOutAddrMaskReps OBJECT-TYPE 727 SYNTAX Counter32 728 MAX-ACCESS read-only 729 STATUS current 730 DESCRIPTION 731 "The number of ICMP Address Mask Reply messages sent." 733 ::= { icmp 26 } 735 -- conformance information 737 ipMIBConformance OBJECT IDENTIFIER ::= { ipMIB 2 } 739 ipMIBCompliances OBJECT IDENTIFIER ::= { ipMIBConformance 1 } 740 ipMIBGroups OBJECT IDENTIFIER ::= { ipMIBConformance 2 } 742 -- compliance statements 744 ipMIBCompliance MODULE-COMPLIANCE 745 STATUS current 746 DESCRIPTION 747 "The compliance statement for SNMPv2 entities which 748 implement IP." 749 MODULE -- this module 750 MANDATORY-GROUPS { ipGroup, 751 icmpGroup } 752 ::= { ipMIBCompliances 1 } 754 -- units of conformance 756 ipGroup OBJECT-GROUP 757 OBJECTS { ipForwarding, ipDefaultTTL, ipInReceives, 758 ipInHdrErrors, ipInAddrErrors, 759 ipForwDatagrams, ipInUnknownProtos, 760 ipInDiscards, ipInDelivers, ipOutRequests, 761 ipOutDiscards, ipOutNoRoutes, 762 ipReasmTimeout, ipReasmReqds, ipReasmOKs, 763 ipReasmFails, ipFragOKs, 764 ipFragFails, ipFragCreates, 765 ipAdEntAddr, ipAdEntIfIndex, ipAdEntNetMask, 766 ipAdEntBcastAddr, ipAdEntReasmMaxSize, 767 ipNetToMediaIfIndex, ipNetToMediaPhysAddress, 768 ipNetToMediaNetAddress, ipNetToMediaType, 769 ipRoutingDiscards } 770 STATUS current 771 DESCRIPTION 772 "The ip group of objects providing for basic management of 773 IP entities, exclusive of the management of IP routes." 774 ::= { ipMIBGroups 1 } 776 icmpGroup OBJECT-GROUP 777 OBJECTS { icmpInMsgs, icmpInErrors, 778 icmpInDestUnreachs, icmpInTimeExcds, 779 icmpInParmProbs, icmpInSrcQuenchs, 780 icmpInRedirects, icmpInEchos, 781 icmpInEchoReps, icmpInTimestamps, 782 icmpInTimestampReps, icmpInAddrMasks, 783 icmpInAddrMaskReps, icmpOutMsgs, 784 icmpOutErrors, icmpOutDestUnreachs, 785 icmpOutTimeExcds, icmpOutParmProbs, 786 icmpOutSrcQuenchs, icmpOutRedirects, 787 icmpOutEchos, icmpOutEchoReps, 788 icmpOutTimestamps, icmpOutTimestampReps, 789 icmpOutAddrMasks, icmpOutAddrMaskReps } 790 STATUS current 791 DESCRIPTION 792 "The icmp group of objects providing ICMP statistics." 793 ::= { ipMIBGroups 2 } 795 END 796 3. Acknowledgements 798 This document contains a modified subset of RFC 1213. 800 4. References 802 [1] Information processing systems - Open Systems Interconnection - 803 Specification of Abstract Syntax Notation One (ASN.1), 804 International Organization for Standardization. International 805 Standard 8824, (December, 1987). 807 [2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Structure 808 of Management Information for version 2 of the Simple Network 809 Management Protocol (SNMPv2)", Internet Draft, SNMP Research, Inc., 810 Cisco Systems, Dover Beach Consulting, Inc., Carnegie Mellon 811 University, March 1995. 813 [3] Postel, J., "Internet Protocol - DARPA Internet Program Protocol 814 Specification", STD 5, RFC 791, DARPA, September 1981. 816 [4] Postel, J., "Internet Control Message Protocol - DARPA Internet 817 Program Protocol Specification", STD 5, RFC 792, USC/Information 818 Sciences Institute, September 1981. 820 [5] McCloghrie, K., and Rose, M., "Management Information Base for 821 Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 822 1213, March 1991. 824 [6] Baker, F., "IP Forwarding Table MIB", RFC 1354, ACC, July 1992. 826 5. Security Considerations 828 Security issues are not discussed in this memo. 830 6. Authors' Addresses 832 Jeffrey D. Case 833 SNMP Research, Inc. 834 3001 Kimberlin Heights Rd. 835 Knoxville, TN 37920-9716 836 US 838 Phone: +1 615 573 1434 839 Email: case@snmp.com 841 Keith McCloghrie 842 Cisco Systems, Inc. 843 170 West Tasman Drive 844 San Jose, CA 95134-1706 845 US 847 Phone: +1 408 526 5260 848 Email: kzm@cisco.com 850 Marshall T. Rose 851 Dover Beach Consulting, Inc. 852 420 Whisman Court 853 Mountain View, CA 94043-2186 854 US 856 Phone: +1 415 968 1052 857 Email: mrose@dbc.mtview.ca.us 859 Steven Waldbusser 860 Carnegie Mellon University 861 5000 Forbes Ave 862 Pittsburgh, PA 15213 863 US 865 Phone: +1 412 268 6628 866 Email: waldbusser@cmu.edu 868 Table of Contents 870 1 Introduction .................................................... 3 871 2 Definitions ..................................................... 4 872 2.1 The IP Group .................................................. 5 873 2.2 The ICMP Group ................................................ 15 874 2.3 Conformance Information ....................................... 21 875 2.3.1 Compliance Statements ....................................... 21 876 2.3.2 Units of Conformance ........................................ 21 877 3 Acknowledgements ................................................ 23 878 4 References ...................................................... 23 879 5 Security Considerations ......................................... 24 880 6 Authors' Addresses .............................................. 24