idnits 2.17.1 draft-ietf-ipngwg-rfc2011-update-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 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. ** There are 16 instances of too long lines in the document, the longest one being 17 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1553: '...scope identifier MUST disambiguate ide...' RFC 2119 keyword, line 1563: '...he default scope SHOULD NOT be used as...' RFC 2119 keyword, line 1719: '...whether an agent MUST support system-w...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1209 has weird spacing: '... used for o...' -- 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.) -- The document date (July 2001) is 8321 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2011 (ref. '2') (Obsoleted by RFC 4293) ** Obsolete normative reference: RFC 2461 (ref. '3') (Obsoleted by RFC 4861) ** Obsolete normative reference: RFC 2465 (ref. '4') (Obsoleted by RFC 4293, RFC 8096) ** Obsolete normative reference: RFC 2466 (ref. '5') (Obsoleted by RFC 4293, RFC 8096) ** Obsolete normative reference: RFC 2571 (ref. '6') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '9') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '13') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '14') ** Obsolete normative reference: RFC 1906 (ref. '15') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '16') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '17') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '18') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '19') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '20') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '21') (Obsoleted by RFC 3410) Summary: 20 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPv6 MIB Revision Design Team Bill Fenner 2 INTERNET-DRAFT AT&T Research 3 Expires: January 2002 Brian Haberman 4 Nortel Networks 5 Juergen Schoenwalder 6 TU Braunschweig 7 Dave Thaler 8 Microsoft 9 July 2001 11 Management Information Base 12 for the Internet Protocol (IP) 13 draft-ietf-ipngwg-rfc2011-update-00.txt 15 Status of this Document 17 This document is an Internet-Draft and is in full conformance with all 18 provisions of Section 10 of RFC2026. 20 Internet-Drafts are working documents of the Internet Engineering Task 21 Force (IETF), its areas, and its working groups. Note that other groups 22 may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference material 27 or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This document is a product of the IPv6 MIB Revision Design Team. 36 Comments should be addressed to the authors, or the mailing list at 37 ipng@sunroof.eng.sun.com. 39 Copyright Notice 41 Copyright (C) The Internet Society (2001). All Rights Reserved. 43 Abstract 45 This memo defines a portion of the Management Information Base (MIB) for 46 use with network management protocols in the Internet community. In 47 particular, it describes managed objects used for implementations of the 48 Internet Protocol (IP) in an IP version independent manner. 50 Table of Contents 52 1. The SNMP Management Framework . . . . . . . . . . . . . . . . . . 3 53 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 4 54 3. Updating Implementations. . . . . . . . . . . . . . . . . . . . . 5 55 3.1. Updating an implementation of the IPv4-only 56 IP-MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 57 3.2. Updating an implementation of the IPv6-MIB . . . . . . . . . . 5 58 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 5. Open Issues / To Do . . . . . . . . . . . . . . . . . . . . . . . 58 60 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 59 61 7. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 62 8. Security Considerations . . . . . . . . . . . . . . . . . . . . . 60 63 9. Editor's Address. . . . . . . . . . . . . . . . . . . . . . . . . 61 64 10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 61 66 1. The SNMP Management Framework 68 The SNMP Management Framework presently consists of five major 69 components: 71 o An overall architecture, described in RFC 2571 [6]. 73 o Mechanisms for describing and naming objects and events for the 74 purpose of management. The first version of this Structure of 75 Management Information (SMI) is called SMIv1 and described in STD 16, 76 RFC 1155 [7], STD 16, RFC 1212 [8] and RFC 1215 [9]. The second 77 version, called SMIv2, is described in STD 58, RFC 2578 [10], STD 58, 78 RFC 2579 [11] and STD 58, RFC 2580 [12]. 80 o Message protocols for transferring management information. The first 81 version of the SNMP message protocol is called SNMPv1 and described in 82 STD 15, RFC 1157 [13]. A second version of the SNMP message protocol, 83 which is not an Internet standards track protocol, is called SNMPv2c 84 and described in RFC 1901 [14] and RFC 1906 [15]. The third version of 85 the message protocol is called SNMPv3 and described in RFC 1906 [15], 86 RFC 2572 [16] and RFC 2574 [17]. 88 o Protocol operations for accessing management information. The first 89 set of protocol operations and associated PDU formats is described in 90 STD 15, RFC 1157 [13]. A second set of protocol operations and 91 associated PDU formats is described in RFC 1905 [18]. 93 o A set of fundamental applications described in RFC 2573 [19] and the 94 view-based access control mechanism described in RFC 2575 [20]. 96 A more detailed introduction to the current SNMP Management Framework 97 can be found in RFC 2570 [21]. 99 Managed objects are accessed via a virtual information store, termed the 100 Management Information Base or MIB. Objects in the MIB are defined 101 using the mechanisms defined in the SMI. 103 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 104 conforming to the SMIv1 can be produced through the appropriate 105 translations. The resulting translated MIB must be semantically 106 equivalent, except where objects or events are omitted because no 107 translation is possible (use of Counter64). Some machine readable 108 information in SMIv2 will be converted into textual descriptions in 109 SMIv1 during the translation process. However, this loss of machine 110 readable information is not considered to change the semantics of the 111 MIB. 113 2. Revision History 115 Changes from draft-ops-rfc2011-update-00.txt: 117 12 Jul 2001 119 Changed to IPNG working group work item. 121 Removed mention of SIIT, since it's just for transition 123 Added lots of counters to ipIfStats table, and 124 ipIfStatsDiscontinuityTime 126 Changed ipAddressIfIndex and ScopeIdentifier to refer to IF-MIB 127 instead of RFC 2863 or RFC 2233 129 Removed text about agents supporting a subset of values from 130 ipv6Forwarding; this belongs in an AGENT-CAPABILITIES. 132 Un-deprecated ipReasmTimeout. XXX Do we need ipv6ReasmTimeout too? 133 I think not; RFC2460 seems to say that it's a constant 60 seconds. 135 Changes from first draft posted to v6mib mailing list: 137 23 Feb 2001 139 Added ipv4InterfaceTable 141 Added ipv6InterfaceTable 142 Added ipAddressPrefixTable and slightly reworked ipAddressTable 143 (nee inetAddressTable). 145 Deprecated ipMIBCompliance. Still need to finish updated ones. 147 Added copyright and table of contents. 149 7 Feb 2001 151 Renamed inetIfStats to ipIfStats 153 Added ipv6ScopeTable 155 Added ScopeIdentifier TC, which should be in INET-ADDRESS-MIB. 157 Added SIZE to inetAddrAddr and inetNetToMediaAddress 159 Wrote some boilerplate for multi-interface-or-system-wide counter 160 tables. 162 3. Updating Implementations 164 Boy, does this need more text. XXX 166 3.1. Updating an implementation of the IPv4-only IP-MIB 168 o New counters: InTooBigErrors, InTruncatedPkts, InMcastPkts, 169 OutMcastPkts. 171 o Can report existing counters as system-wide in ipIfStatsTable (0 for 172 ifindex) or can implement per-interface counters and report those. 174 o Move ipAdEntReasmMaxSize to ipIfReasmMaxSize 176 3.2. Updating an implementation of the IPv6-MIB 178 o New counters: ReasmTimeout 180 o Don't need to implement per-interface stats. 182 o Reimplement ipv6IfLowerLayer with the TUNNEL-MIB (note: can't 183 represent IPv6-over-IPv6 since the TUNNEL-MIB is IPv4-only) 185 4. Definitions 187 IP-MIB DEFINITIONS ::= BEGIN 189 IMPORTS 190 MODULE-IDENTITY, OBJECT-TYPE, 191 Integer32, Counter32, IpAddress, mib-2, Unsigned32, Counter64 192 FROM SNMPv2-SMI 193 PhysAddress, TruthValue, TimeStamp, RowPointer, 194 TEXTUAL-CONVENTION -- XXX 195 FROM SNMPv2-TC 196 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 197 InetAddress, InetAddressType, 198 InetAddressPrefixLength FROM INET-ADDRESS-MIB 199 InterfaceIndex, 200 InterfaceIndexOrZero, ifIndex FROM IF-MIB; 202 ipMIB MODULE-IDENTITY 203 LAST-UPDATED "200107130000Z" 204 ORGANIZATION "IETF IPv6 MIB Revision Team" 205 CONTACT-INFO 206 "Editor: 207 Bill Fenner 208 AT&T Labs - Research 209 75 Willow Rd 210 Menlo Park, CA 212 Phone: +1 650 330-7893 213 Email: " 214 DESCRIPTION 215 "The MIB module for managing IP and ICMP implementations, but 216 excluding their management of IP routes." 217 REVISION "200107130000Z" 218 DESCRIPTION 219 "IP version neutral revision, published as RFC XXXX." 220 REVISION "9411010000Z" 221 DESCRIPTION 222 "Published seperately as RFC 2011." 223 REVISION "9103310000Z" 224 DESCRIPTION 225 "The initial revision of this MIB module was part of MIB-II." 226 ::= { mib-2 48} 228 -- the IP general group 230 ip OBJECT IDENTIFIER ::= { mib-2 4 } 232 ipForwarding OBJECT-TYPE 233 SYNTAX INTEGER { 234 forwarding(1), -- acting as a router 235 notForwarding(2) -- NOT acting as a router 236 } 238 MAX-ACCESS read-write 239 STATUS current 240 DESCRIPTION 241 "The indication of whether this entity is acting as an IPv4 242 router in respect to the forwarding of datagrams received 243 by, but not addressed to, this entity. IPv4 routers forward 244 datagrams. IPv4 hosts do not (except those source-routed 245 via the host)." 246 ::= { ip 1 } 248 ipDefaultTTL OBJECT-TYPE 249 SYNTAX INTEGER (1..255) 250 MAX-ACCESS read-write 251 STATUS current 252 DESCRIPTION 253 "The default value inserted into the Time-To-Live field of 254 the IPv4 header of datagrams originated at this entity, 255 whenever a TTL value is not supplied by the transport layer 256 protocol." 257 ::= { ip 2 } 259 ipReasmTimeout OBJECT-TYPE 260 SYNTAX Integer32 261 MAX-ACCESS read-only 262 STATUS current 263 DESCRIPTION 264 "The maximum number of seconds which received fragments are 265 held while they are awaiting reassembly at this entity." 266 ::= { ip 13 } 268 -- the IPv6 general group 270 ipv6MIB OBJECT IDENTIFIER ::= { mib-2 55 } 272 ipv6MIBObjects OBJECT IDENTIFIER ::= { ipv6MIB 1 } 274 ipv6Forwarding OBJECT-TYPE 275 SYNTAX INTEGER { 276 forwarding(1), -- acting as a router 277 notForwarding(2) -- NOT acting as a router 278 } 279 MAX-ACCESS read-write 280 STATUS current 281 DESCRIPTION 282 "The indication of whether this entity is acting as an IPv6 283 router in respect to the forwarding of datagrams received 284 by, but not addressed to, this entity. IPv6 routers forward 285 datagrams. IPv6 hosts do not (except those source-routed 286 via the host)." 287 ::= { ipv6MIBObjects 1 } 289 ipv6DefaultHopLimit OBJECT-TYPE 290 SYNTAX INTEGER (0..255) 291 MAX-ACCESS read-write 292 STATUS current 293 DESCRIPTION 294 "The default value inserted into the Hop Limit field of the 295 IPv6 header of datagrams originated at this entity, whenever 296 a Hop Limit value is not supplied by the transport layer 297 protocol." 298 ::= { ipv6MIBObjects 2 } 300 -- 301 -- IPv4 Interface Table 302 -- 304 ipv4IfTable OBJECT-TYPE 305 SYNTAX SEQUENCE OF Ipv4IfEntry 306 MAX-ACCESS not-accessible 307 STATUS current 308 DESCRIPTION 309 "The table containing per-interface IPv4-specific 310 information." 311 ::= { ip 25 } 313 ipv4IfEntry OBJECT-TYPE 314 SYNTAX Ipv4IfEntry 315 MAX-ACCESS not-accessible 316 STATUS current 317 DESCRIPTION 318 "An entry containing IPv4-specific information for a specific 319 interface." 320 INDEX { ipv4IfIndex } 321 ::= { ipv4IfTable 1 } 323 Ipv4IfEntry ::= SEQUENCE { 324 ipv4IfIndex InterfaceIndex, 325 ipv4IfReasmMaxSize Integer32 326 } 328 ipv4IfIndex OBJECT-TYPE 329 SYNTAX InterfaceIndex 330 MAX-ACCESS not-accessible 331 STATUS current 332 DESCRIPTION 333 "The interface to which these values apply." 335 ::= { ipv4IfEntry 1 } 337 ipv4IfReasmMaxSize OBJECT-TYPE 338 SYNTAX Integer32 (0..65535) 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "The size of the largest IPv4 datagram which this entity can 343 re-assemble from incoming IPv4 fragmented datagrams received 344 on this interface." 345 ::= { ipv4IfEntry 2 } 347 -- 348 -- v6 interface table 349 -- XXX I suspect that most of these objects can go away. 350 -- 351 -- Open Issues: 352 -- ipv6InterfaceAdminStatus: does it make sense to enable/disable 353 -- IPv6 on its own on the interface? 354 -- ipv6InterfaceOperStatus: other than the above, noIfIdentifier(3) 355 -- is this one's only useful state, which can be determined from 356 -- the Address table if DAD failed or there is no v6 address on 357 -- this interface. [not efficiently, though] 359 ipv6InterfaceTable OBJECT-TYPE 360 SYNTAX SEQUENCE OF Ipv6InterfaceEntry 361 MAX-ACCESS not-accessible 362 STATUS current 363 DESCRIPTION 364 "The table containing per-interface IPv6-specific 365 information." 366 ::= { ip 31 } 368 ipv6InterfaceEntry OBJECT-TYPE 369 SYNTAX Ipv6InterfaceEntry 370 MAX-ACCESS not-accessible 371 STATUS current 372 DESCRIPTION 373 "An entry containing IPv6-specific information for a given 374 interface." 375 INDEX { ipv6InterfaceIfIndex } 376 ::= { ipv6InterfaceTable 1 } 378 Ipv6InterfaceEntry ::= SEQUENCE { 379 ipv6InterfaceIfIndex InterfaceIndex, 380 ipv6InterfaceEffectiveMtu Unsigned32, 381 ipv6InterfaceReasmMaxSize Unsigned32, 382 ipv6InterfaceIdentifier Ipv6AddressIfIdentifier, 383 ipv6InterfaceIdentifierLength INTEGER, 384 ipv6InterfacePhysicalAddress PhysAddress 385 } 387 ipv6InterfaceIfIndex OBJECT-TYPE 388 SYNTAX InterfaceIndex 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "The interface for which this row contains IPv6-specific 393 information." 394 ::= { ipv6InterfaceEntry 1 } 396 ipv6InterfaceEffectiveMtu OBJECT-TYPE 397 SYNTAX Unsigned32 398 UNITS "octets" 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "The size of the largest IPv6 packet which can be 403 sent/received on the interface, specified in octets. 405 XXX - why isn't this ifMtu - sizeof(ipv6 header)?" 406 ::= { ipv6InterfaceEntry 2 } 408 ipv6InterfaceReasmMaxSize OBJECT-TYPE 409 SYNTAX Unsigned32 (0..65535) 410 UNITS "octets" 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The size of the largest IPv6 datagram which this entity can 415 re-assemble from incoming IPv6 fragmented datagrams received 416 on this interface." 417 ::= { ipv6InterfaceEntry 3 } 419 -- XXX ugh: I want to get rid of this, which is why it's in the middle 420 -- of nowhere 421 Ipv6AddressIfIdentifier ::= TEXTUAL-CONVENTION 422 DISPLAY-HINT "2x:" 423 STATUS current 424 DESCRIPTION 425 "This data type is used to model IPv6 address 426 interface identifiers. This is a binary string 427 of up to 8 octets in network byte-order." 428 SYNTAX OCTET STRING (SIZE (0..8)) 430 ipv6InterfaceIdentifier OBJECT-TYPE 431 SYNTAX Ipv6AddressIfIdentifier 432 MAX-ACCESS read-write 433 STATUS current 434 DESCRIPTION 435 "The Interface Identifier for this interface that is (at 436 least) unique on the link this interface is attached to. The 437 Interface Identifier is combined with an address prefix to 438 form an interface address. 440 By default, the Interface Identifier is autoconfigured 441 according to the rules of the link type this interface is 442 attached to. 444 XXX - is this an EUI64 that belongs more in the IF-MIB?" 445 ::= { ipv6InterfaceEntry 4 } 447 ipv6InterfaceIdentifierLength OBJECT-TYPE 448 SYNTAX INTEGER (0..64) 449 UNITS "bits" 450 MAX-ACCESS read-write 451 STATUS current 452 DESCRIPTION 453 "The length of the Interface Identifier in bits." 454 ::= { ipv6InterfaceEntry 5 } 456 ipv6InterfacePhysicalAddress OBJECT-TYPE 457 SYNTAX PhysAddress 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "The interface's physical address. For example, for an IPv6 462 interface attached to an 802.x link, this object normally 463 contains a MAC address. Note that in some cases this address 464 may differ from the address of the interface's protocol sub- 465 layer. The interface's media-specific MIB must define the 466 bit and byte ordering and the format of the value of this 467 object. For interfaces which do not have such an address 468 (e.g., a serial line), this object should contain an octet 469 string of zero length. 471 XXX When can this be different from the address of the 472 interface's protocol sub-layer, and why?" 473 ::= { ipv6InterfaceEntry 6 } 475 -- 476 -- Per-Interface or System-Wide IP statistics. 477 -- 478 -- Open issues: 479 -- Add octet counters similar to ifTable and ifXTable? 481 ipIfStatsTable OBJECT-TYPE 482 SYNTAX SEQUENCE OF IpIfStatsEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "The table containing traffic statistics. These statistics 487 may be kept per-interface and/or system-wide." 488 ::= { ip 26 } 490 ipIfStatsEntry OBJECT-TYPE 491 SYNTAX IpIfStatsEntry 492 MAX-ACCESS not-accessible 493 STATUS current 494 DESCRIPTION 495 "An interface statistics entry containing objects for a 496 particular interface, or system-wide. 498 A row with an ipIfStatsIfIndex value of zero indicates a 499 system-wide value; a row with a non-zero ipIfStatsIfIndex 500 indicates an interface-specific value. A system may provide 501 both system-wide and interface-specific values, in which 502 case it is important to note that the system-wide value may 503 not be equal to the sum of the interface-specific values 504 across all interfaces due to e.g. dynamic interface 505 creation/deletion." 506 INDEX { ipIfStatsAFType, ipIfStatsIfIndex } 507 ::= { ipIfStatsTable 1 } 509 IpIfStatsEntry ::= SEQUENCE { 510 ipIfStatsAFType InetAddressType, 511 ipIfStatsIfIndex InterfaceIndexOrZero, 512 ipIfStatsInReceives Counter32, 513 ipIfStatsInHdrErrors Counter32, 514 ipIfStatsInTooBigErrors Counter32, 515 ipIfStatsInNoRoutes Counter32, 516 ipIfStatsInAddrErrors Counter32, 517 ipIfStatsInUnknownProtos Counter32, 518 ipIfStatsInTruncatedPkts Counter32, 519 ipIfStatsInDiscards Counter32, 520 ipIfStatsInDelivers Counter32, 521 ipIfStatsOutForwDatagrams Counter32, 522 ipIfStatsOutRequests Counter32, 523 ipIfStatsOutDiscards Counter32, 524 ipIfStatsOutFragOKs Counter32, 525 ipIfStatsOutFragFails Counter32, 526 ipIfStatsOutFragCreates Counter32, 527 ipIfStatsReasmReqds Counter32, 528 ipIfStatsReasmOKs Counter32, 529 ipIfStatsReasmFails Counter32, 530 ipIfStatsInMcastPkts Counter32, 531 ipIfStatsOutMcastPkts Counter32, 532 ipIfStatsInOctets Counter32, 533 ipIfStatsOutOctets Counter32, 534 ipIfStatsInBcastPkts Counter32, 535 ipIfStatsOutBcastPkts Counter32, 536 ipIfStatsHCInOctets Counter64, 537 ipIfStatsHCInUcastPkts Counter64, 538 ipIfStatsHCInMcastPkts Counter64, 539 ipIfStatsHCInBcastPkts Counter64, 540 ipIfStatsHCOutOctets Counter64, 541 ipIfStatsHCOutUcastPkts Counter64, 542 ipIfStatsHCOutMcastPkts Counter64, 543 ipIfStatsHCOutBcastPkts Counter64, 544 ipIfStatsInMcastOctets Counter32, 545 ipIfStatsOutMcastOctets Counter32, 546 ipIfStatsHCInMcastOctets Counter64, 547 ipIfStatsHCOutMcastOctets Counter64, 548 ipIfStatsDiscontinuityTime TimeStamp 549 } 551 ipIfStatsAFType OBJECT-TYPE 552 SYNTAX InetAddressType 553 MAX-ACCESS not-accessible 554 STATUS current 555 DESCRIPTION 556 "The address family for this row. May only be IPv4 or IPv6." 557 ::= { ipIfStatsEntry 1 } 559 ipIfStatsIfIndex OBJECT-TYPE 560 SYNTAX InterfaceIndexOrZero 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "The interface index, or zero for system-wide counters." 565 ::= { ipIfStatsEntry 2 } 567 ipIfStatsInReceives OBJECT-TYPE 568 SYNTAX Counter32 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The total number of input IP datagrams received by the 573 interface, including those received in error." 574 ::= { ipIfStatsEntry 3 } 576 ipIfStatsInHdrErrors OBJECT-TYPE 577 SYNTAX Counter32 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "The number of input IP datagrams discarded due to errors in 582 their IP headers, including version number mismatch, other 583 format errors, hop count exceeded, errors discovered in 584 processing their IP options, etc. 586 Discontinuities in the value of this counter can occur at 587 re-initialization of the management system, and at other 588 times as indicated by the value of 589 ipIfStatsDiscontinuityTime." 590 ::= { ipIfStatsEntry 4 } 592 ipIfStatsInTooBigErrors OBJECT-TYPE 593 SYNTAX Counter32 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "The number of input IP datagrams that could not be forwarded 598 because their size exceeded the link MTU of the outgoing 599 interface. 601 Discontinuities in the value of this counter can occur at 602 re-initialization of the management system, and at other 603 times as indicated by the value of 604 ipIfStatsDiscontinuityTime." 605 ::= { ipIfStatsEntry 5 } 607 ipIfStatsInNoRoutes OBJECT-TYPE 608 SYNTAX Counter32 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "The number of input IP datagrams discarded because no route 613 could be found to transmit them to their destination. 615 Discontinuities in the value of this counter can occur at 616 re-initialization of the management system, and at other 617 times as indicated by the value of 618 ipIfStatsDiscontinuityTime." 620 ::= { ipIfStatsEntry 6 } 622 ipIfStatsInAddrErrors OBJECT-TYPE 623 SYNTAX Counter32 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The number of input IP datagrams discarded because the IP 628 address in their IP header's destination field was not a 629 valid address to be received at this entity. This count 630 includes invalid addresses (e.g., ::0) and unsupported 631 addresses (e.g., addresses with unallocated prefixes). For 632 entities which are not IP routers and therefore do not 633 forward datagrams, this counter includes datagrams discarded 634 because the destination address was not a local address. 636 Discontinuities in the value of this counter can occur at 637 re-initialization of the management system, and at other 638 times as indicated by the value of 639 ipIfStatsDiscontinuityTime." 640 ::= { ipIfStatsEntry 7 } 642 ipIfStatsInUnknownProtos OBJECT-TYPE 643 SYNTAX Counter32 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "The number of locally-addressed IP datagrams received 648 successfully but discarded because of an unknown or 649 unsupported protocol. This counter is incremented at the 650 interface to which these datagrams were addressed which 651 might not be necessarily the input interface for some of the 652 datagrams. 654 Discontinuities in the value of this counter can occur at 655 re-initialization of the management system, and at other 656 times as indicated by the value of 657 ipIfStatsDiscontinuityTime." 658 ::= { ipIfStatsEntry 8 } 660 ipIfStatsInTruncatedPkts OBJECT-TYPE 661 SYNTAX Counter32 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The number of input IP datagrams discarded because datagram 666 frame didn't carry enough data. 668 Discontinuities in the value of this counter can occur at 669 re-initialization of the management system, and at other 670 times as indicated by the value of 671 ipIfStatsDiscontinuityTime." 672 ::= { ipIfStatsEntry 9 } 674 ipIfStatsInDiscards OBJECT-TYPE 675 SYNTAX Counter32 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The number of input IP datagrams for which no problems were 680 encountered to prevent their continued processing, but which 681 were discarded (e.g., for lack of buffer space). Note that 682 this counter does not include any datagrams discarded while 683 awaiting re-assembly. 685 Discontinuities in the value of this counter can occur at 686 re-initialization of the management system, and at other 687 times as indicated by the value of 688 ipIfStatsDiscontinuityTime." 689 ::= { ipIfStatsEntry 10 } 691 ipIfStatsInDelivers OBJECT-TYPE 692 SYNTAX Counter32 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "The total number of datagrams successfully delivered to IP 697 user-protocols (including ICMP). This counter is 698 incremented at the interface to which these datagrams were 699 addressed which might not be necessarily the input interface 700 for some of the datagrams. 702 Discontinuities in the value of this counter can occur at 703 re-initialization of the management system, and at other 704 times as indicated by the value of 705 ipIfStatsDiscontinuityTime." 706 ::= { ipIfStatsEntry 11 } 708 ipIfStatsOutForwDatagrams OBJECT-TYPE 709 SYNTAX Counter32 710 MAX-ACCESS read-only 711 STATUS current 712 DESCRIPTION 713 "The number of output datagrams which this entity received 714 and forwarded to their final destinations. In entities 715 which do not act as IP routers, this counter will include 716 only those packets which were Source-Routed via this entity, 717 and the Source-Route processing was successful. Note that 718 for a successfully forwarded datagram the counter of the 719 outgoing interface is incremented. 721 Discontinuities in the value of this counter can occur at 722 re-initialization of the management system, and at other 723 times as indicated by the value of 724 ipIfStatsDiscontinuityTime." 725 ::= { ipIfStatsEntry 12 } 727 ipIfStatsOutRequests OBJECT-TYPE 728 SYNTAX Counter32 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "The total number of IP datagrams which local IP user- 733 protocols (including ICMP) supplied to IP in requests for 734 transmission. Note that this counter does not include any 735 datagrams counted in ipIfStatsOutForwDatagrams. 737 Discontinuities in the value of this counter can occur at 738 re-initialization of the management system, and at other 739 times as indicated by the value of 740 ipIfStatsDiscontinuityTime." 741 ::= { ipIfStatsEntry 13 } 743 ipIfStatsOutDiscards OBJECT-TYPE 744 SYNTAX Counter32 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "The number of output IP datagrams for which no problem was 749 encountered to prevent their transmission to their 750 destination, but which were discarded (e.g., for lack of 751 buffer space). Note that this counter would include 752 datagrams counted in ipIfStatsOutForwDatagrams if any such 753 packets met this (discretionary) discard criterion. 755 Discontinuities in the value of this counter can occur at 756 re-initialization of the management system, and at other 757 times as indicated by the value of 758 ipIfStatsDiscontinuityTime." 759 ::= { ipIfStatsEntry 14 } 761 ipIfStatsOutFragOKs OBJECT-TYPE 762 SYNTAX Counter32 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "The number of IP datagrams that have been successfully 767 fragmented at this output interface. 769 Discontinuities in the value of this counter can occur at 770 re-initialization of the management system, and at other 771 times as indicated by the value of 772 ipIfStatsDiscontinuityTime." 773 ::= { ipIfStatsEntry 15 } 775 ipIfStatsOutFragFails OBJECT-TYPE 776 SYNTAX Counter32 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "The number of IP datagrams that have been discarded because 781 they needed to be fragmented at this output interface but 782 could not be. 784 Discontinuities in the value of this counter can occur at 785 re-initialization of the management system, and at other 786 times as indicated by the value of 787 ipIfStatsDiscontinuityTime." 788 ::= { ipIfStatsEntry 16 } 790 ipIfStatsOutFragCreates OBJECT-TYPE 791 SYNTAX Counter32 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "The number of output datagram fragments that have been 796 generated as a result of IP fragmentation at this output 797 interface. 799 Discontinuities in the value of this counter can occur at 800 re-initialization of the management system, and at other 801 times as indicated by the value of 802 ipIfStatsDiscontinuityTime." 803 ::= { ipIfStatsEntry 17 } 805 ipIfStatsReasmReqds OBJECT-TYPE 806 SYNTAX Counter32 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The number of IP fragments received which needed to be 811 reassembled at this interface. Note that this counter is 812 incremented at the interface to which these fragments were 813 addressed which might not be necessarily the input interface 814 for some of the fragments. 816 Discontinuities in the value of this counter can occur at 817 re-initialization of the management system, and at other 818 times as indicated by the value of 819 ipIfStatsDiscontinuityTime." 820 ::= { ipIfStatsEntry 18 } 822 ipIfStatsReasmOKs OBJECT-TYPE 823 SYNTAX Counter32 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "The number of IP datagrams successfully reassembled. Note 828 that this counter is incremented at the interface to which 829 these datagrams were addressed which might not be 830 necessarily the input interface for some of the fragments. 832 Discontinuities in the value of this counter can occur at 833 re-initialization of the management system, and at other 834 times as indicated by the value of 835 ipIfStatsDiscontinuityTime." 836 ::= { ipIfStatsEntry 19 } 838 ipIfStatsReasmFails OBJECT-TYPE 839 SYNTAX Counter32 840 MAX-ACCESS read-only 841 STATUS current 842 DESCRIPTION 843 "The number of failures detected by the IP re-assembly 844 algorithm (for whatever reason: timed out, errors, etc.). 845 Note that this is not necessarily a count of discarded IP 846 fragments since some algorithms (notably the algorithm in 847 RFC 815) can lose track of the number of fragments by 848 combining them as they are received. This counter is 849 incremented at the interface to which these fragments were 850 addressed which might not be necessarily the input interface 851 for some of the fragments. 853 Discontinuities in the value of this counter can occur at 854 re-initialization of the management system, and at other 855 times as indicated by the value of 856 ipIfStatsDiscontinuityTime." 857 ::= { ipIfStatsEntry 20 } 859 ipIfStatsInMcastPkts OBJECT-TYPE 860 SYNTAX Counter32 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "The number of IP multicast packets received by the interface 866 Discontinuities in the value of this counter can occur at 867 re-initialization of the management system, and at other 868 times as indicated by the value of 869 ipIfStatsDiscontinuityTime." 870 ::= { ipIfStatsEntry 21 } 872 ipIfStatsOutMcastPkts OBJECT-TYPE 873 SYNTAX Counter32 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "The number of IP multicast packets transmitted by the 878 interface 880 Discontinuities in the value of this counter can occur at 881 re-initialization of the management system, and at other 882 times as indicated by the value of 883 ipIfStatsDiscontinuityTime." 884 ::= { ipIfStatsEntry 22 } 886 ipIfStatsInOctets OBJECT-TYPE 887 SYNTAX Counter32 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "The total number of octets in input IP datagrams received by 892 the interface, including those received in error. 894 Discontinuities in the value of this counter can occur at 895 re-initialization of the management system, and at other 896 times as indicated by the value of 897 ipIfStatsDiscontinuityTime." 898 ::= { ipIfStatsEntry 23 } 900 ipIfStatsOutOctets OBJECT-TYPE 901 SYNTAX Counter32 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "The total number of octets in output IP datagrams delivered 906 to the lower layer on this interface. 908 Discontinuities in the value of this counter can occur at 909 re-initialization of the management system, and at other 910 times as indicated by the value of 911 ipIfStatsDiscontinuityTime." 912 ::= { ipIfStatsEntry 24 } 914 ipIfStatsInBcastPkts OBJECT-TYPE 915 SYNTAX Counter32 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION 919 " 921 Discontinuities in the value of this counter can occur at 922 re-initialization of the management system, and at other 923 times as indicated by the value of 924 ipIfStatsDiscontinuityTime." 925 ::= { ipIfStatsEntry 25 } 927 ipIfStatsOutBcastPkts OBJECT-TYPE 928 SYNTAX Counter32 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 " 934 Discontinuities in the value of this counter can occur at 935 re-initialization of the management system, and at other 936 times as indicated by the value of 937 ipIfStatsDiscontinuityTime." 938 ::= { ipIfStatsEntry 26 } 940 ipIfStatsHCInOctets OBJECT-TYPE 941 SYNTAX Counter64 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 " 947 Discontinuities in the value of this counter can occur at 948 re-initialization of the management system, and at other 949 times as indicated by the value of 950 ipIfStatsDiscontinuityTime." 951 ::= { ipIfStatsEntry 27 } 953 ipIfStatsHCInUcastPkts OBJECT-TYPE 954 SYNTAX Counter64 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 " 960 Discontinuities in the value of this counter can occur at 961 re-initialization of the management system, and at other 962 times as indicated by the value of 963 ipIfStatsDiscontinuityTime." 964 ::= { ipIfStatsEntry 28 } 966 ipIfStatsHCInMcastPkts OBJECT-TYPE 967 SYNTAX Counter64 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 " 973 Discontinuities in the value of this counter can occur at 974 re-initialization of the management system, and at other 975 times as indicated by the value of 976 ipIfStatsDiscontinuityTime." 977 ::= { ipIfStatsEntry 29 } 979 ipIfStatsHCInBcastPkts OBJECT-TYPE 980 SYNTAX Counter64 981 MAX-ACCESS read-only 982 STATUS current 983 DESCRIPTION 984 " 986 Discontinuities in the value of this counter can occur at 987 re-initialization of the management system, and at other 988 times as indicated by the value of 989 ipIfStatsDiscontinuityTime." 990 ::= { ipIfStatsEntry 30 } 992 ipIfStatsHCOutOctets OBJECT-TYPE 993 SYNTAX Counter64 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 " 999 Discontinuities in the value of this counter can occur at 1000 re-initialization of the management system, and at other 1001 times as indicated by the value of 1002 ipIfStatsDiscontinuityTime." 1003 ::= { ipIfStatsEntry 31 } 1005 ipIfStatsHCOutUcastPkts OBJECT-TYPE 1006 SYNTAX Counter64 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 " 1012 Discontinuities in the value of this counter can occur at 1013 re-initialization of the management system, and at other 1014 times as indicated by the value of 1015 ipIfStatsDiscontinuityTime." 1016 ::= { ipIfStatsEntry 32 } 1018 ipIfStatsHCOutMcastPkts OBJECT-TYPE 1019 SYNTAX Counter64 1020 MAX-ACCESS read-only 1021 STATUS current 1022 DESCRIPTION 1023 " 1025 Discontinuities in the value of this counter can occur at 1026 re-initialization of the management system, and at other 1027 times as indicated by the value of 1028 ipIfStatsDiscontinuityTime." 1029 ::= { ipIfStatsEntry 33 } 1031 ipIfStatsHCOutBcastPkts OBJECT-TYPE 1032 SYNTAX Counter64 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 " 1038 Discontinuities in the value of this counter can occur at 1039 re-initialization of the management system, and at other 1040 times as indicated by the value of 1041 ipIfStatsDiscontinuityTime." 1042 ::= { ipIfStatsEntry 34 } 1044 ipIfStatsInMcastOctets OBJECT-TYPE 1045 SYNTAX Counter32 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 " 1051 Discontinuities in the value of this counter can occur at 1052 re-initialization of the management system, and at other 1053 times as indicated by the value of 1054 ipIfStatsDiscontinuityTime." 1055 ::= { ipIfStatsEntry 35 } 1057 ipIfStatsOutMcastOctets OBJECT-TYPE 1058 SYNTAX Counter32 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 " 1064 Discontinuities in the value of this counter can occur at 1065 re-initialization of the management system, and at other 1066 times as indicated by the value of 1067 ipIfStatsDiscontinuityTime." 1068 ::= { ipIfStatsEntry 36 } 1070 ipIfStatsHCInMcastOctets OBJECT-TYPE 1071 SYNTAX Counter64 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 " 1077 Discontinuities in the value of this counter can occur at 1078 re-initialization of the management system, and at other 1079 times as indicated by the value of 1080 ipIfStatsDiscontinuityTime." 1081 ::= { ipIfStatsEntry 37 } 1083 ipIfStatsHCOutMcastOctets OBJECT-TYPE 1084 SYNTAX Counter64 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 " 1090 Discontinuities in the value of this counter can occur at 1091 re-initialization of the management system, and at other 1092 times as indicated by the value of 1093 ipIfStatsDiscontinuityTime." 1094 ::= { ipIfStatsEntry 38 } 1096 ipIfStatsDiscontinuityTime OBJECT-TYPE 1097 SYNTAX TimeStamp 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The value of sysUpTime on the most recent occasion at which 1102 any one or more of this entry's counters suffered a 1103 discontinuity. 1105 If no such discontinuities have occurred since the last 1106 reinitialization of the local management subsystem, then 1107 this object contains a zero value." 1108 ::= { ipIfStatsEntry 39 } 1110 -- 1111 -- Internet Address Prefix table 1112 -- 1113 -- Open Issues: 1114 -- What's OnLinkFlag for IPv4? 1115 -- What's AutonomousFlag for IPv4? 1116 -- What are PreferredLifetime and ValidLifetime for IPv4? 1117 -- Is there a better SMI data type for *Lifetime objects? 1119 ipAddressPrefixTable OBJECT-TYPE 1120 SYNTAX SEQUENCE OF IpAddressPrefixEntry 1121 MAX-ACCESS not-accessible 1122 STATUS current 1123 DESCRIPTION 1124 "inet prefix table" 1125 ::= { ip 27 } 1127 ipAddressPrefixEntry OBJECT-TYPE 1128 SYNTAX IpAddressPrefixEntry 1129 MAX-ACCESS not-accessible 1130 STATUS current 1131 DESCRIPTION 1132 "inet prefix entry" 1133 INDEX { ipAddressPrefixIfIndex, ipAddressPrefixType, 1134 ipAddressPrefixPrefix, ipAddressPrefixLength } 1135 ::= { ipAddressPrefixTable 1 } 1137 IpAddressPrefixEntry ::= SEQUENCE { 1138 ipAddressPrefixIfIndex InterfaceIndex, 1139 ipAddressPrefixType InetAddressType, 1140 ipAddressPrefixPrefix InetAddress, 1141 ipAddressPrefixLength InetAddressPrefixLength, 1142 ipAddressPrefixOrigin INTEGER, 1143 ipAddressPrefixOnLinkFlag TruthValue, 1144 ipAddressPrefixAutonomousFlag TruthValue, 1145 ipAddressPrefixAdvPreferredLifetime Unsigned32, 1146 ipAddressPrefixAdvValidLifetime Unsigned32 1147 } 1149 ipAddressPrefixIfIndex OBJECT-TYPE 1150 SYNTAX InterfaceIndex 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "The interface on which this prefix is configured." 1155 ::= { ipAddressPrefixEntry 1 } 1157 ipAddressPrefixType OBJECT-TYPE 1158 SYNTAX InetAddressType 1159 MAX-ACCESS not-accessible 1160 STATUS current 1161 DESCRIPTION 1162 "The address type of ipAddressPrefix. Only IPv4 and IPv6 1163 addresses are expected." 1164 ::= { ipAddressPrefixEntry 2 } 1166 ipAddressPrefixPrefix OBJECT-TYPE 1167 SYNTAX InetAddress (SIZE(0..36)) 1168 MAX-ACCESS not-accessible 1169 STATUS current 1170 DESCRIPTION 1171 "The address prefix. Bits after ipAddressPrefixLength must 1172 be zero." 1173 ::= { ipAddressPrefixEntry 3 } 1175 ipAddressPrefixLength OBJECT-TYPE 1176 SYNTAX InetAddressPrefixLength 1177 MAX-ACCESS not-accessible 1178 STATUS current 1179 DESCRIPTION 1180 "The prefix length associated with this prefix." 1181 ::= { ipAddressPrefixEntry 4 } 1183 ipAddressPrefixOrigin OBJECT-TYPE 1184 SYNTAX INTEGER { 1185 other(1), 1186 manual(2), 1187 wellknown(3), 1188 dhcp(4), 1189 routeradv(5) 1190 } 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "The origin of this prefix. manual(2) indicates a prefix 1195 that was manually configured. wellknown(3) indicates a 1196 well-known prefix, e.g. 169.254/16 for IPv4 1197 autoconfiguration or fe80::/10 for IPv6 link-local 1198 addresses. dhcp(4) indicates a prefix that was assigned by 1199 a DHCP server. routeradv(5) indicates a prefix learned from 1200 a router advertisement." 1201 ::= { ipAddressPrefixEntry 5 } 1203 ipAddressPrefixOnLinkFlag OBJECT-TYPE 1204 SYNTAX TruthValue 1205 MAX-ACCESS read-only 1206 STATUS current 1207 DESCRIPTION 1208 "This object has the value 'true(1)', if this prefix can be 1209 used for on-link determination and the value 'false(2)' 1210 otherwise." 1211 ::= { ipAddressPrefixEntry 6 } 1213 ipAddressPrefixAutonomousFlag OBJECT-TYPE 1214 SYNTAX TruthValue 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "Autonomous address configuration flag. When true(1), 1219 indicates that this prefix can be used for autonomous 1220 address configuration (i.e. can be used to form a local 1221 interface address). If false(2), it is not used to 1222 autoconfigure a local interface address." 1223 ::= { ipAddressPrefixEntry 7 } 1225 ipAddressPrefixAdvPreferredLifetime OBJECT-TYPE 1226 SYNTAX Unsigned32 1227 UNITS "seconds" 1228 MAX-ACCESS read-only 1229 STATUS current 1230 DESCRIPTION 1231 "The length of time in seconds that this prefix will remain 1232 preferred, i.e. time until deprecation. A value of 1233 4,294,967,295 represents infinity. 1235 The address generated from a deprecated prefix should no 1236 longer be used as a source address in new communications, 1237 but packets received on such an interface are processed as 1238 expected." 1239 ::= { ipAddressPrefixEntry 8 } 1241 ipAddressPrefixAdvValidLifetime OBJECT-TYPE 1242 SYNTAX Unsigned32 1243 UNITS "seconds" 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "The length of time in seconds that this prefix will remain 1248 valid, i.e. time until invalidation. A value of 1249 4,294,967,295 represents infinity. 1251 The address generated from an invalidated prefix should not 1252 appear as the destination or source address of a packet." 1253 ::= { ipAddressPrefixEntry 9 } 1255 -- 1256 -- Internet Address Table 1257 -- 1258 -- Open Issues: 1259 -- should ipAddressv4BcastAddr go somewhere else? 1260 -- meeting notes said: dave: pointer to prefix table. What's that mean? 1262 ipAddressTable OBJECT-TYPE 1263 SYNTAX SEQUENCE OF IpAddressEntry 1264 MAX-ACCESS not-accessible 1265 STATUS current 1266 DESCRIPTION 1267 "inet addr table" 1268 ::= { ip 28 } 1270 ipAddressEntry OBJECT-TYPE 1271 SYNTAX IpAddressEntry 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "inet addr entry" 1276 INDEX { ipAddressAddrType, ipAddressAddr } 1277 ::= { ipAddressTable 1 } 1279 IpAddressEntry ::= SEQUENCE { 1280 ipAddressAddrType InetAddressType, 1281 ipAddressAddr InetAddress, 1282 ipAddressIfIndex InterfaceIndex, 1283 ipAddressType INTEGER, 1284 ipAddressPrefix RowPointer, 1285 ipAddressOrigin INTEGER, 1286 ipAddressStatus INTEGER 1288 } 1290 ipAddressAddrType OBJECT-TYPE 1291 SYNTAX InetAddressType 1292 MAX-ACCESS not-accessible 1293 STATUS current 1294 DESCRIPTION 1295 "The address type of ipAddressAddr." 1296 ::= { ipAddressEntry 1 } 1298 ipAddressAddr OBJECT-TYPE 1299 SYNTAX InetAddress (SIZE(0..36)) 1300 MAX-ACCESS not-accessible 1301 STATUS current 1302 DESCRIPTION 1303 "The IP address to which this entry's addressing information 1304 pertains." 1305 ::= { ipAddressEntry 2 } 1307 ipAddressIfIndex OBJECT-TYPE 1308 SYNTAX InterfaceIndex 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "The index value which uniquely identifies the interface to 1313 which this entry is applicable. The interface identified by 1314 a particular value of this index is the same interface as 1315 identified by the same value of the IF-MIB's ifIndex." 1316 ::= { ipAddressEntry 3 } 1318 ipAddressType OBJECT-TYPE 1319 SYNTAX INTEGER { 1320 unicast(1), 1321 anycast(2), 1322 broadcast(3) 1323 } 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "The type of address. broadcast(3) is not a valid value for 1328 IPv6 addresses [draft-ietf-ipngwg-addr-arch-v3-05.txt]." 1329 ::= { ipAddressEntry 4 } 1331 ipAddressPrefix OBJECT-TYPE 1332 SYNTAX RowPointer 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "A pointer to the row in the prefix table to which this 1337 address belongs. May be { 0 0 } if there is no such row." 1338 ::= { ipAddressEntry 5 } 1340 ipAddressOrigin OBJECT-TYPE 1341 SYNTAX INTEGER { 1342 other(1), 1343 manual(2), 1344 wellknown(3), 1345 dhcp(4),-- XXX or assignedbyserver ? 1346 linklayer(5), 1347 random(6) 1348 } 1349 MAX-ACCESS read-only 1350 STATUS deprecated 1351 DESCRIPTION 1352 "The origin of the address. manual(2) indicates that the 1353 address was manually configured. wellknown(3) indicates an 1354 address constructed from a well-known value, e.g. an IANA- 1355 assigned anycast address. dhcp(4) indicates an address that 1356 was assigned to this system by a DHCP server. linklayer(5) 1357 indicates an address created by IPv6 stateless 1358 autoconfiguration. random(6) indicates an address chosen by 1359 random, e.g. an IPv4 address within 169.254/16, or an RFC 1360 3041 privacy address." 1361 ::= { ipAddressEntry 6 } 1363 ipAddressStatus OBJECT-TYPE 1364 SYNTAX INTEGER { 1365 preferred(1), 1367 deprecated(2), 1369 invalid(3), 1371 inaccessible(4), 1373 unknown(5), -- status can not be determined 1374 -- for some reason. 1375 tentative(6), 1377 duplicate(7) 1378 } 1379 MAX-ACCESS read-only 1380 STATUS deprecated 1381 DESCRIPTION 1382 "Address status. The preferred(1) state indicates that this 1383 is a valid address that can appear as the destination or 1384 source address of a packet. The deprecated(2) state 1385 indicates that this is a valid but deprecated address that 1386 should no longer be used as a source address in new 1387 communications, but packets addressed to such an address are 1388 processed as expected. The invalid(3) state indicates that 1389 this is not valid address which should not appear as the 1390 destination or source address of a packet. The 1391 inaccessible(4) state indicates that the address is not 1392 accessible because the interface to which this address is 1393 assigned is not operational. The tentative(6) state 1394 indicates the uniqueness of the address on the link is being 1395 verified. The duplicate(7) state indicates the address has 1396 been determined to be non-unique on the link and so must not 1397 be used. 1399 In the absence of other information, an IPv4 address is 1400 always preferred(1)." 1401 ::= { ipAddressEntry 7 } 1403 -- the Internet Address Translation table 1405 inetNetToMediaTable OBJECT-TYPE 1406 SYNTAX SEQUENCE OF InetNetToMediaEntry 1407 MAX-ACCESS not-accessible 1408 STATUS current 1409 DESCRIPTION 1410 "The IP Address Translation table used for mapping from IP 1411 addresses to physical addresses. 1413 The Address Translation tables contain the IP address to 1414 'physical' address equivalences. Some interfaces do not use 1415 translation tables for determining address equivalences 1416 (e.g., DDN-X.25 has an algorithmic method); if all 1417 interfaces are of this type, then the Address Translation 1418 table is empty, i.e., has zero entries." 1419 ::= { ip 29 } 1421 inetNetToMediaEntry OBJECT-TYPE 1422 SYNTAX InetNetToMediaEntry 1423 MAX-ACCESS not-accessible 1424 STATUS current 1425 DESCRIPTION 1426 "Each entry contains one IP address to `physical' address 1427 equivalence." 1428 INDEX { ifIndex, 1429 inetNetToMediaNetAddressType, 1430 inetNetToMediaNetAddress } 1431 ::= { inetNetToMediaTable 1 } 1433 InetNetToMediaEntry ::= SEQUENCE { 1434 inetNetToMediaNetAddressType InetAddressType, 1435 inetNetToMediaNetAddress InetAddress, 1436 inetNetToMediaPhysAddress PhysAddress, 1437 inetNetToMediaLastUpdated TimeStamp, 1438 inetNetToMediaType INTEGER, 1439 inetNetToMediaState INTEGER 1440 } 1442 inetNetToMediaNetAddressType OBJECT-TYPE 1443 SYNTAX InetAddressType 1444 MAX-ACCESS not-accessible 1445 STATUS current 1446 DESCRIPTION 1447 "The type of inetNetToMediaNetAddress." 1448 ::= { inetNetToMediaEntry 1 } 1450 inetNetToMediaNetAddress OBJECT-TYPE 1451 SYNTAX InetAddress (SIZE(0..36)) 1452 MAX-ACCESS not-accessible 1453 STATUS current 1454 DESCRIPTION 1455 "The IP Address corresponding to the media-dependent 1456 `physical' address." 1457 ::= { inetNetToMediaEntry 2 } 1459 inetNetToMediaPhysAddress OBJECT-TYPE 1460 SYNTAX PhysAddress 1461 MAX-ACCESS read-create 1462 STATUS current 1463 DESCRIPTION 1464 "The media-dependent `physical' address." 1465 ::= { inetNetToMediaEntry 3 } 1467 inetNetToMediaLastUpdated OBJECT-TYPE 1468 SYNTAX TimeStamp 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "The value of sysUpTime at the time this entry was last 1473 updated. If this entry was updated prior to the last re- 1474 initialization of the local network management subsystem, 1475 then this object contains a zero value." 1476 ::= { inetNetToMediaEntry 4 } 1478 inetNetToMediaType OBJECT-TYPE 1479 SYNTAX INTEGER { 1480 other(1), -- none of the following 1481 invalid(2), -- an invalidated mapping 1482 dynamic(3), 1483 static(4), 1484 local(5) -- local interface 1485 } 1486 MAX-ACCESS read-create 1487 STATUS current 1488 DESCRIPTION 1489 "The type of mapping. 1491 Setting this object to the value invalid(2) has the effect 1492 of invalidating the corresponding entry in the 1493 inetNetToMediaTable. That is, it effectively disassociates 1494 the interface identified with said entry from the mapping 1495 identified with said entry. It is an implementation- 1496 specific matter as to whether the agent removes an 1497 invalidated entry from the table. Accordingly, management 1498 stations must be prepared to receive tabular information 1499 from agents that corresponds to entries not currently in 1500 use. Proper interpretation of such entries requires 1501 examination of the relevant inetNetToMediaType object. 1503 The 'dynamic(3)' type indicates that the IP address to 1504 physical addresses mapping has been dynamically resolved 1505 using e.g. IPv4 ARP or the IPv6 Neighbor Discovery protocol. 1506 The 'static(4)' type indicates that the mapping has been 1507 statically configured. The 'local(5)' type indicates that 1508 the mapping is provided for an entity's own interface 1509 address." 1510 ::= { inetNetToMediaEntry 5 } 1512 inetNetToMediaState OBJECT-TYPE 1513 SYNTAX INTEGER { 1514 reachable(1), -- confirmed reachability 1516 stale(2), -- unconfirmed reachability 1518 delay(3), -- waiting for reachability 1519 -- confirmation before entering 1520 -- the probe state 1522 probe(4), -- actively probing 1524 invalid(5), -- an invalidated mapping 1525 unknown(6), -- state can not be determined 1526 -- for some reason. 1527 incomplete(7) -- address resolution is being performed. 1528 } 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "The Neighbor Unreachability Detection [3] state for the 1533 interface when the address mapping in this entry is used. 1534 If Neighbor Unreachability Detection is not in use (e.g. for 1535 IPv4), this object is always unknown(6)." 1536 REFERENCE "RFC2461" 1537 ::= { inetNetToMediaEntry 6 } 1539 -- 1540 -- The IPv6 Scope Identifier Table. 1541 -- 1542 -- Open Issues: 1543 -- Should there be associated objects to provide a scope description, 1544 -- similar to ipMRouteScopeNameString? 1546 -- XXX ScopeIdentifier TC should move to INET-ADDRESS-MIB 1547 ScopeIdentifier ::= TEXTUAL-CONVENTION 1548 STATUS current 1549 DESCRIPTION 1550 "A Scope Identifier identifies an instance of a specific 1551 scope. 1553 The scope identifier MUST disambiguate identical address 1554 values. For link-local addresses, the scope identifier will 1555 typically be the interface index (ifIndex as defined in the 1556 IF-MIB) of the interface on which the address is configured. 1558 The scope identifier may contain the special value 0 which 1559 refers to the default scope. The default scope may be used 1560 in cases where the valid scope identifier is not known 1561 (e.g., a management application needs to write a site-local 1562 InetAddressIPv6 address without knowing the site identifier 1563 value). The default scope SHOULD NOT be used as an easy way 1564 out in cases where the scope identifier for a non-global 1565 IPv6 address is known." 1566 SYNTAX Unsigned32 1568 ipv6ScopeIdTable OBJECT-TYPE 1569 SYNTAX SEQUENCE OF Ipv6ScopeIdEntry 1570 MAX-ACCESS not-accessible 1571 STATUS current 1572 DESCRIPTION 1573 "The table used to describe IPv6 unicast and multicast scope 1574 zones." 1575 ::= { ip 30 } 1577 ipv6ScopeIdEntry OBJECT-TYPE 1578 SYNTAX Ipv6ScopeIdEntry 1579 MAX-ACCESS not-accessible 1580 STATUS current 1581 DESCRIPTION 1582 "Each entry contains the list of scope identifiers on a given 1583 interface." 1584 INDEX { ipv6ScopeIdIfIndex } 1585 ::= { ipv6ScopeIdTable 1 } 1587 Ipv6ScopeIdEntry ::= SEQUENCE { 1588 ipv6ScopeIdIfIndex InterfaceIndex, 1589 ipv6ScopeIdLinkLocal ScopeIdentifier, 1590 ipv6ScopeIdSubnetLocal ScopeIdentifier, 1591 ipv6ScopeIdAdminLocal ScopeIdentifier, 1592 ipv6ScopeIdSiteLocal ScopeIdentifier, 1593 ipv6ScopeId6 ScopeIdentifier, 1594 ipv6ScopeId7 ScopeIdentifier, 1595 ipv6ScopeIdOrganizationLocal ScopeIdentifier, 1596 ipv6ScopeId9 ScopeIdentifier, 1597 ipv6ScopeIdA ScopeIdentifier, 1598 ipv6ScopeIdB ScopeIdentifier, 1599 ipv6ScopeIdC ScopeIdentifier, 1600 ipv6ScopeIdD ScopeIdentifier 1601 } 1603 ipv6ScopeIdIfIndex OBJECT-TYPE 1604 SYNTAX InterfaceIndex 1605 MAX-ACCESS not-accessible 1606 STATUS current 1607 DESCRIPTION 1608 "The interface to which these scopes belong." 1609 ::= { ipv6ScopeIdEntry 1 } 1611 ipv6ScopeIdLinkLocal OBJECT-TYPE 1612 SYNTAX ScopeIdentifier 1613 MAX-ACCESS read-only 1614 STATUS current 1615 DESCRIPTION 1616 "The Scope Identifier for the link-local scope on this 1617 interface." 1618 ::= { ipv6ScopeIdEntry 2 } 1620 ipv6ScopeIdSubnetLocal OBJECT-TYPE 1621 SYNTAX ScopeIdentifier 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "The Scope Identifier for the subnet-local scope on this 1626 interface." 1627 ::= { ipv6ScopeIdEntry 3 } 1629 ipv6ScopeIdAdminLocal OBJECT-TYPE 1630 SYNTAX ScopeIdentifier 1631 MAX-ACCESS read-only 1632 STATUS current 1633 DESCRIPTION 1634 "The Scope Identifier for the admin-local scope on this 1635 interface." 1636 ::= { ipv6ScopeIdEntry 4 } 1638 ipv6ScopeIdSiteLocal OBJECT-TYPE 1639 SYNTAX ScopeIdentifier 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "The Scope Identifier for the site-local scope on this 1644 interface." 1645 ::= { ipv6ScopeIdEntry 5 } 1647 ipv6ScopeId6 OBJECT-TYPE 1648 SYNTAX ScopeIdentifier 1649 MAX-ACCESS read-only 1650 STATUS current 1651 DESCRIPTION 1652 "The Scope Identifier for scope 6 on this interface." 1653 ::= { ipv6ScopeIdEntry 6 } 1655 ipv6ScopeId7 OBJECT-TYPE 1656 SYNTAX ScopeIdentifier 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "The Scope Identifier for scope 7 on this interface." 1661 ::= { ipv6ScopeIdEntry 7 } 1663 ipv6ScopeIdOrganizationLocal OBJECT-TYPE 1664 SYNTAX ScopeIdentifier 1665 MAX-ACCESS read-only 1666 STATUS current 1667 DESCRIPTION 1668 "The Scope Identifier for the orgainzation-local scope on 1669 this interface." 1670 ::= { ipv6ScopeIdEntry 8 } 1672 ipv6ScopeId9 OBJECT-TYPE 1673 SYNTAX ScopeIdentifier 1674 MAX-ACCESS read-only 1675 STATUS current 1676 DESCRIPTION 1677 "The Scope Identifier for scope 9 on this interface." 1678 ::= { ipv6ScopeIdEntry 9 } 1680 ipv6ScopeIdA OBJECT-TYPE 1681 SYNTAX ScopeIdentifier 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "The Scope Identifier for scope A on this interface." 1686 ::= { ipv6ScopeIdEntry 10 } 1688 ipv6ScopeIdB OBJECT-TYPE 1689 SYNTAX ScopeIdentifier 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "The Scope Identifier for scope B on this interface." 1694 ::= { ipv6ScopeIdEntry 11 } 1696 ipv6ScopeIdC OBJECT-TYPE 1697 SYNTAX ScopeIdentifier 1698 MAX-ACCESS read-only 1699 STATUS current 1700 DESCRIPTION 1701 "The Scope Identifier for scope C on this interface." 1702 ::= { ipv6ScopeIdEntry 12 } 1704 ipv6ScopeIdD OBJECT-TYPE 1705 SYNTAX ScopeIdentifier 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "The Scope Identifier for scope D on this interface." 1710 ::= { ipv6ScopeIdEntry 13 } 1712 icmp OBJECT IDENTIFIER ::= { mib-2 5 } 1713 -- 1714 -- ICMP non-message-specific counters 1715 -- 1716 -- 1717 -- To do: 1718 -- expand table DESCRIPTION to describe index 1719 -- (including whether an agent MUST support system-wide, per-if, 1720 -- both, or neither, to be compliant to this MIB. 1721 -- Also, it might be useful to remind readers that the 1722 -- system-wide value is not the sum of the per-if counters.) 1723 -- ************************************************************* 1725 inetIcmpTable OBJECT-TYPE 1726 SYNTAX SEQUENCE OF InetIcmpEntry 1727 MAX-ACCESS not-accessible 1728 STATUS current 1729 DESCRIPTION 1730 "The table of generic ICMP counters. These counters may be 1731 kept per-interface and/or system-wide." 1732 ::= { icmp 27 } 1734 inetIcmpEntry OBJECT-TYPE 1735 SYNTAX InetIcmpEntry 1736 MAX-ACCESS not-accessible 1737 STATUS current 1738 DESCRIPTION 1739 "A conceptual row in the inetIcmpTable. 1741 A row with an inetIcmpIfIndex value of zero indicates a 1742 system-wide value; a row with a non-zero inetIcmpIfIndex 1743 indicates an interface-specific value. A system may provide 1744 both system-wide and interface-specific values, in which 1745 case it is important to note that the system-wide value may 1746 not be equal to the sum of the interface-specific values 1747 across all interfaces due to e.g. dynamic interface 1748 creation/deletion." 1749 INDEX { inetIcmpAFType, inetIcmpIfIndex } 1750 ::= { inetIcmpTable 1 } 1752 InetIcmpEntry ::= SEQUENCE { 1753 inetIcmpAFType InetAddressType, 1754 inetIcmpIfIndex InterfaceIndexOrZero, 1755 inetIcmpInMsgs Counter32, 1756 inetIcmpInErrors Counter32, 1757 inetIcmpOutMsgs Counter32, 1758 inetIcmpOutErrors Counter32 1759 } 1761 inetIcmpAFType OBJECT-TYPE 1762 SYNTAX InetAddressType 1763 MAX-ACCESS not-accessible 1764 STATUS current 1765 DESCRIPTION 1766 "The IP address family of the statistics." 1767 ::= { inetIcmpEntry 1 } 1769 inetIcmpIfIndex OBJECT-TYPE 1770 SYNTAX InterfaceIndexOrZero 1771 MAX-ACCESS not-accessible 1772 STATUS current 1773 DESCRIPTION 1774 "The ifindex of the interface, or zero for system-wide 1775 stats." 1776 ::= { inetIcmpEntry 2 } 1778 inetIcmpInMsgs OBJECT-TYPE 1779 SYNTAX Counter32 1780 MAX-ACCESS read-only 1781 STATUS current 1782 DESCRIPTION 1783 "The total number of ICMP messages which the entity received. 1784 Note that this counter includes all those counted by 1785 inetIcmpInErrors." 1786 ::= { inetIcmpEntry 3 } 1788 inetIcmpInErrors OBJECT-TYPE 1789 SYNTAX Counter32 1790 MAX-ACCESS read-only 1791 STATUS current 1792 DESCRIPTION 1793 "The number of ICMP messages which the entity received but 1794 determined as having ICMP-specific errors (bad ICMP 1795 checksums, bad length, etc.)." 1796 ::= { inetIcmpEntry 4 } 1798 inetIcmpOutMsgs OBJECT-TYPE 1799 SYNTAX Counter32 1800 MAX-ACCESS read-only 1801 STATUS current 1802 DESCRIPTION 1803 "The total number of ICMP messages which the entity received. 1804 Note that this counter includes all those counted by 1805 inetIcmpOutErrors." 1806 ::= { inetIcmpEntry 5 } 1808 inetIcmpOutErrors OBJECT-TYPE 1809 SYNTAX Counter32 1810 MAX-ACCESS read-only 1811 STATUS current 1812 DESCRIPTION 1813 "The number of ICMP messages which this entity did not send 1814 due to problems discovered within ICMP such as a lack of 1815 buffers. This value should not include errors discovered 1816 outside the ICMP layer such as the inability of IP to route 1817 the resultant datagram. In some implementations there may 1818 be no types of error which contribute to this counter's 1819 value." 1820 ::= { inetIcmpEntry 6 } 1822 -- 1823 -- per-AF, per-interface(optionally), per-msg type and code ICMP counters 1824 -- 1826 inetIcmpMsgTable OBJECT-TYPE 1827 SYNTAX SEQUENCE OF InetIcmpMsgEntry 1828 MAX-ACCESS not-accessible 1829 STATUS current 1830 DESCRIPTION 1831 "The table of per-message ICMP counters. These counters may 1832 be kept per-interface and/or system-wide." 1833 ::= { icmp 28 } 1835 inetIcmpMsgEntry OBJECT-TYPE 1836 SYNTAX InetIcmpMsgEntry 1837 MAX-ACCESS not-accessible 1838 STATUS current 1839 DESCRIPTION 1840 "A conceptual row in the inetIcmpMsgTable. 1842 A row with an inetIcmpMsgIfIndex value of zero indicates a 1843 system-wide value; a row with a non-zero inetIcmpMsgIfIndex 1844 indicates an interface-specific value. A system may provide 1845 both system-wide and interface-specific values, in which 1846 case it is important to note that the system-wide value may 1847 not be equal to the sum of the interface-specific values 1848 across all interfaces due to e.g. dynamic interface 1849 creation/deletion. 1851 XXX How to phrase this if? If the system keeps track of 1852 individual ICMP code values (e.g. destination unreachable, 1853 code administratively prohibited), it creates several rows 1854 for each inetIcmpMsgType, each with an appropriate value of 1855 inetIcmpMsgCode. A row with the special value of 1856 inetIcmpMsgCode, 256, counts all packets with type 1857 inetIcmpMsgType that aren't counted in rows with a value of 1858 inetIcmpMsgCode other than 256." 1859 INDEX { inetIcmpMsgAFType, inetIcmpMsgIfIndex, inetIcmpMsgType, 1860 inetIcmpMsgCode } 1861 ::= { inetIcmpMsgTable 1 } 1863 InetIcmpMsgEntry ::= SEQUENCE { 1864 inetIcmpMsgAFType InetAddressType, 1865 inetIcmpMsgIfIndex InterfaceIndexOrZero, 1866 inetIcmpMsgType Integer32, 1867 inetIcmpMsgCode Integer32, 1868 inetIcmpMsgInPkts Counter32, 1869 inetIcmpMsgOutPkts Counter32 1870 } 1872 inetIcmpMsgAFType OBJECT-TYPE 1873 SYNTAX InetAddressType 1874 MAX-ACCESS not-accessible 1875 STATUS current 1876 DESCRIPTION 1877 "The IP address family of the statistics." 1878 ::= { inetIcmpMsgEntry 1 } 1880 inetIcmpMsgIfIndex OBJECT-TYPE 1881 SYNTAX InterfaceIndexOrZero 1882 MAX-ACCESS not-accessible 1883 STATUS current 1884 DESCRIPTION 1885 "The ifindex of the interface, or zero for system-wide 1886 stats." 1887 ::= { inetIcmpMsgEntry 2 } 1889 inetIcmpMsgType OBJECT-TYPE 1890 SYNTAX Integer32 (0..255) 1891 MAX-ACCESS not-accessible 1892 STATUS current 1893 DESCRIPTION 1894 "The ICMP type field of the message type being counted by 1895 this row." 1896 ::= { inetIcmpMsgEntry 3 } 1898 inetIcmpMsgCode OBJECT-TYPE 1899 SYNTAX Integer32 (0..256) 1900 MAX-ACCESS not-accessible 1901 STATUS current 1902 DESCRIPTION 1903 "The ICMP code field of the message type being counted by 1904 this row, or the special value 256 if no specific ICMP code 1905 is counted by this row." 1906 ::= { inetIcmpMsgEntry 4 } 1908 inetIcmpMsgInPkts OBJECT-TYPE 1909 SYNTAX Counter32 1910 MAX-ACCESS read-only 1911 STATUS current 1912 DESCRIPTION 1913 "The number of input packets for this AF, ifindex, type, 1914 code." 1915 ::= { inetIcmpMsgEntry 5 } 1917 inetIcmpMsgOutPkts OBJECT-TYPE 1918 SYNTAX Counter32 1919 MAX-ACCESS read-only 1920 STATUS current 1921 DESCRIPTION 1922 "The number of output packets for this AF, ifindex, type, 1923 code." 1924 ::= { inetIcmpMsgEntry 6 } 1926 -- XXX 1927 -- To do: move current conformance information here. 1929 -- 1930 -- Deprecated objects 1931 -- 1933 ipInReceives OBJECT-TYPE 1934 SYNTAX Counter32 1935 MAX-ACCESS read-only 1936 STATUS deprecated 1937 DESCRIPTION 1938 "The total number of input datagrams received from 1939 interfaces, including those received in error." 1940 ::= { ip 3 } 1942 ipInHdrErrors OBJECT-TYPE 1943 SYNTAX Counter32 1944 MAX-ACCESS read-only 1945 STATUS deprecated 1946 DESCRIPTION 1947 "The number of input datagrams discarded due to errors in 1948 their IPv4 headers, including bad checksums, version number 1949 mismatch, other format errors, time-to-live exceeded, errors 1950 discovered in processing their IPv4 options, etc." 1951 ::= { ip 4 } 1953 ipInAddrErrors OBJECT-TYPE 1954 SYNTAX Counter32 1955 MAX-ACCESS read-only 1956 STATUS deprecated 1957 DESCRIPTION 1958 "The number of input datagrams discarded because the IPv4 1959 address in their IPv4 header's destination field was not a 1960 valid address to be received at this entity. This count 1961 includes invalid addresses (e.g., 0.0.0.0) and addresses of 1962 unsupported Classes (e.g., Class E). For entities which are 1963 not IPv4 routers and therefore do not forward datagrams, 1964 this counter includes datagrams discarded because the 1965 destination address was not a local address." 1966 ::= { ip 5 } 1968 ipForwDatagrams OBJECT-TYPE 1969 SYNTAX Counter32 1970 MAX-ACCESS read-only 1971 STATUS deprecated 1972 DESCRIPTION 1973 "The number of input datagrams for which this entity was not 1974 their final IPv4 destination, as a result of which an 1975 attempt was made to find a route to forward them to that 1976 final destination. In entities which do not act as IPv4 1977 routers, this counter will include only those packets which 1978 were Source-Routed via this entity, and the Source-Route 1979 option processing was successful." 1980 ::= { ip 6 } 1982 ipInUnknownProtos OBJECT-TYPE 1983 SYNTAX Counter32 1984 MAX-ACCESS read-only 1985 STATUS deprecated 1986 DESCRIPTION 1987 "The number of locally-addressed datagrams received 1988 successfully but discarded because of an unknown or 1989 unsupported protocol." 1990 ::= { ip 7 } 1992 ipInDiscards OBJECT-TYPE 1993 SYNTAX Counter32 1994 MAX-ACCESS read-only 1995 STATUS deprecated 1996 DESCRIPTION 1997 "The number of input IPv4 datagrams for which no problems 1998 were encountered to prevent their continued processing, but 1999 which were discarded (e.g., for lack of buffer space). Note 2000 that this counter does not include any datagrams discarded 2001 while awaiting re-assembly." 2002 ::= { ip 8 } 2004 ipInDelivers OBJECT-TYPE 2005 SYNTAX Counter32 2006 MAX-ACCESS read-only 2007 STATUS deprecated 2008 DESCRIPTION 2009 "The total number of input datagrams successfully delivered 2010 to IPv4 user-protocols (including ICMP)." 2011 ::= { ip 9 } 2013 ipOutRequests OBJECT-TYPE 2014 SYNTAX Counter32 2015 MAX-ACCESS read-only 2016 STATUS deprecated 2017 DESCRIPTION 2018 "The total number of IPv4 datagrams which local IPv4 user 2019 protocols (including ICMP) supplied to IPv4 in requests for 2020 transmission. Note that this counter does not include any 2021 datagrams counted in ipForwDatagrams." 2022 ::= { ip 10 } 2024 ipOutDiscards OBJECT-TYPE 2025 SYNTAX Counter32 2026 MAX-ACCESS read-only 2027 STATUS deprecated 2028 DESCRIPTION 2029 "The number of output IPv4 datagrams for which no problem was 2030 encountered to prevent their transmission to their 2031 destination, but which were discarded (e.g., for lack of 2032 buffer space). Note that this counter would include 2033 datagrams counted in ipForwDatagrams if any such packets met 2034 this (discretionary) discard criterion." 2035 ::= { ip 11 } 2037 ipOutNoRoutes OBJECT-TYPE 2038 SYNTAX Counter32 2039 MAX-ACCESS read-only 2040 STATUS deprecated 2041 DESCRIPTION 2042 "The number of IPv4 datagrams discarded because no route 2043 could be found to transmit them to their destination. Note 2044 that this counter includes any packets counted in 2045 ipForwDatagrams which meet this `no-route' criterion. Note 2046 that this includes any datagrams which a host cannot route 2047 because all of its default routers are down." 2048 ::= { ip 12 } 2050 ipReasmReqds OBJECT-TYPE 2051 SYNTAX Counter32 2052 MAX-ACCESS read-only 2053 STATUS deprecated 2054 DESCRIPTION 2055 "The number of IPv4 fragments received which needed to be 2056 reassembled at this entity." 2057 ::= { ip 14 } 2059 ipReasmOKs OBJECT-TYPE 2060 SYNTAX Counter32 2061 MAX-ACCESS read-only 2062 STATUS deprecated 2063 DESCRIPTION 2064 "The number of IPv4 datagrams successfully re-assembled." 2065 ::= { ip 15 } 2067 ipReasmFails OBJECT-TYPE 2068 SYNTAX Counter32 2069 MAX-ACCESS read-only 2070 STATUS deprecated 2071 DESCRIPTION 2072 "The number of failures detected by the IPv4 re-assembly 2073 algorithm (for whatever reason: timed out, errors, etc). 2074 Note that this is not necessarily a count of discarded IPv4 2075 fragments since some algorithms (notably the algorithm in 2076 RFC 815) can lose track of the number of fragments by 2077 combining them as they are received." 2078 ::= { ip 16 } 2080 ipFragOKs OBJECT-TYPE 2081 SYNTAX Counter32 2082 MAX-ACCESS read-only 2083 STATUS deprecated 2084 DESCRIPTION 2085 "The number of IPv4 datagrams that have been successfully 2086 fragmented at this entity." 2087 ::= { ip 17 } 2089 ipFragFails OBJECT-TYPE 2090 SYNTAX Counter32 2091 MAX-ACCESS read-only 2092 STATUS deprecated 2093 DESCRIPTION 2094 "The number of IPv4 datagrams that have been discarded 2095 because they needed to be fragmented at this entity but 2096 could not be, e.g., because their Don't Fragment flag was 2097 set." 2098 ::= { ip 18 } 2100 ipFragCreates OBJECT-TYPE 2101 SYNTAX Counter32 2102 MAX-ACCESS read-only 2103 STATUS deprecated 2104 DESCRIPTION 2105 "The number of IPv4 datagram fragments that have been 2106 generated as a result of fragmentation at this entity." 2107 ::= { ip 19 } 2109 ipRoutingDiscards OBJECT-TYPE 2110 SYNTAX Counter32 2111 MAX-ACCESS read-only 2112 STATUS deprecated 2113 DESCRIPTION 2114 "The number of routing entries which were chosen to be 2115 discarded even though they are valid. One possible reason 2116 for discarding such an entry could be to free-up buffer 2117 space for other routing entries." 2118 ::= { ip 23 } 2120 -- the deprecated IPv4 address table 2122 ipAddrTable OBJECT-TYPE 2123 SYNTAX SEQUENCE OF IpAddrEntry 2124 MAX-ACCESS not-accessible 2125 STATUS deprecated 2126 DESCRIPTION 2127 "The table of addressing information relevant to this 2128 entity's IPv4 addresses." 2129 ::= { ip 20 } 2131 ipAddrEntry OBJECT-TYPE 2132 SYNTAX IpAddrEntry 2133 MAX-ACCESS not-accessible 2134 STATUS deprecated 2135 DESCRIPTION 2136 "The addressing information for one of this entity's IPv4 2137 addresses." 2138 INDEX { ipAdEntAddr } 2139 ::= { ipAddrTable 1 } 2141 IpAddrEntry ::= SEQUENCE { 2142 ipAdEntAddr IpAddress, 2143 ipAdEntIfIndex INTEGER, 2144 ipAdEntNetMask IpAddress, 2145 ipAdEntBcastAddr INTEGER, 2146 ipAdEntReasmMaxSize INTEGER 2147 } 2149 ipAdEntAddr OBJECT-TYPE 2150 SYNTAX IpAddress 2151 MAX-ACCESS read-only 2152 STATUS deprecated 2153 DESCRIPTION 2154 "The IPv4 address to which this entry's addressing 2155 information pertains." 2156 ::= { ipAddrEntry 1 } 2158 ipAdEntIfIndex OBJECT-TYPE 2159 SYNTAX INTEGER (1..2147483647) 2160 MAX-ACCESS read-only 2161 STATUS deprecated 2162 DESCRIPTION 2163 "The index value which uniquely identifies the interface to 2164 which this entry is applicable. The interface identified by 2165 a particular value of this index is the same interface as 2166 identified by the same value of RFC 2863's ifIndex." 2167 ::= { ipAddrEntry 2 } 2169 ipAdEntNetMask OBJECT-TYPE 2170 SYNTAX IpAddress 2171 MAX-ACCESS read-only 2172 STATUS deprecated 2173 DESCRIPTION 2174 "The subnet mask associated with the IPv4 address of this 2175 entry. The value of the mask is an IPv4 address with all 2176 the network bits set to 1 and all the hosts bits set to 0." 2177 ::= { ipAddrEntry 3 } 2179 ipAdEntBcastAddr OBJECT-TYPE 2180 SYNTAX INTEGER (0..1) 2181 MAX-ACCESS read-only 2182 STATUS deprecated 2183 DESCRIPTION 2184 "The value of the least-significant bit in the IPv4 broadcast 2185 address used for sending datagrams on the (logical) 2186 interface associated with the IPv4 address of this entry. 2187 For example, when the Internet standard all-ones broadcast 2188 address is used, the value will be 1. This value applies to 2189 both the subnet and network broadcasts addresses used by the 2190 entity on this (logical) interface." 2191 ::= { ipAddrEntry 4 } 2193 ipAdEntReasmMaxSize OBJECT-TYPE 2194 SYNTAX INTEGER (0..65535) 2195 MAX-ACCESS read-only 2196 STATUS deprecated 2197 DESCRIPTION 2198 "The size of the largest IPv4 datagram which this entity can 2199 re-assemble from incoming IPv4 fragmented datagrams received 2200 on this interface." 2201 ::= { ipAddrEntry 5 } 2203 -- the deprecated IPv4 Address Translation table 2205 -- The Address Translation tables contain the IpAddress to 2206 -- "physical" address equivalences. Some interfaces do not 2207 -- use translation tables for determining address 2208 -- equivalences (e.g., DDN-X.25 has an algorithmic method); 2209 -- if all interfaces are of this type, then the Address 2210 -- Translation table is empty, i.e., has zero entries. 2212 ipNetToMediaTable OBJECT-TYPE 2213 SYNTAX SEQUENCE OF IpNetToMediaEntry 2214 MAX-ACCESS not-accessible 2215 STATUS deprecated 2216 DESCRIPTION 2217 "The IPv4 Address Translation table used for mapping from 2218 IPv4 addresses to physical addresses." 2219 ::= { ip 22 } 2221 ipNetToMediaEntry OBJECT-TYPE 2222 SYNTAX IpNetToMediaEntry 2223 MAX-ACCESS not-accessible 2224 STATUS deprecated 2225 DESCRIPTION 2226 "Each entry contains one IpAddress to `physical' address 2227 equivalence." 2228 INDEX { ipNetToMediaIfIndex, 2229 ipNetToMediaNetAddress } 2230 ::= { ipNetToMediaTable 1 } 2232 IpNetToMediaEntry ::= SEQUENCE { 2233 ipNetToMediaIfIndex INTEGER, 2234 ipNetToMediaPhysAddress PhysAddress, 2235 ipNetToMediaNetAddress IpAddress, 2236 ipNetToMediaType INTEGER 2237 } 2239 ipNetToMediaIfIndex OBJECT-TYPE 2240 SYNTAX INTEGER (1..2147483647) 2241 MAX-ACCESS read-create 2242 STATUS deprecated 2243 DESCRIPTION 2244 "The interface on which this entry's equivalence is 2245 effective. The interface identified by a particular value 2246 of this index is the same interface as identified by the 2247 same value of RFC 2863's ifIndex." 2248 ::= { ipNetToMediaEntry 1 } 2250 ipNetToMediaPhysAddress OBJECT-TYPE 2251 SYNTAX PhysAddress 2252 MAX-ACCESS read-create 2253 STATUS deprecated 2254 DESCRIPTION 2255 "The media-dependent `physical' address." 2256 ::= { ipNetToMediaEntry 2 } 2258 ipNetToMediaNetAddress OBJECT-TYPE 2259 SYNTAX IpAddress 2260 MAX-ACCESS read-create 2261 STATUS deprecated 2262 DESCRIPTION 2263 "The IpAddress corresponding to the media-dependent 2264 `physical' address." 2265 ::= { ipNetToMediaEntry 3 } 2267 ipNetToMediaType OBJECT-TYPE 2268 SYNTAX INTEGER { 2269 other(1), -- none of the following 2270 invalid(2), -- an invalidated mapping 2271 dynamic(3), 2272 static(4) 2273 } 2274 MAX-ACCESS read-create 2275 STATUS deprecated 2276 DESCRIPTION 2277 "The type of mapping. 2279 Setting this object to the value invalid(2) has the effect 2280 of invalidating the corresponding entry in the 2281 ipNetToMediaTable. That is, it effectively disassociates 2282 the interface identified with said entry from the mapping 2283 identified with said entry. It is an implementation- 2284 specific matter as to whether the agent removes an 2285 invalidated entry from the table. Accordingly, management 2286 stations must be prepared to receive tabular information 2287 from agents that corresponds to entries not currently in 2288 use. Proper interpretation of such entries requires 2289 examination of the relevant ipNetToMediaType object." 2290 ::= { ipNetToMediaEntry 4 } 2292 -- the deprecated ICMP group 2294 icmpInMsgs OBJECT-TYPE 2295 SYNTAX Counter32 2296 MAX-ACCESS read-only 2297 STATUS deprecated 2298 DESCRIPTION 2299 "The total number of ICMP messages which the entity received. 2300 Note that this counter includes all those counted by 2301 icmpInErrors." 2302 ::= { icmp 1 } 2304 icmpInErrors OBJECT-TYPE 2305 SYNTAX Counter32 2306 MAX-ACCESS read-only 2307 STATUS deprecated 2308 DESCRIPTION 2309 "The number of ICMP messages which the entity received but 2310 determined as having ICMP-specific errors (bad ICMP 2311 checksums, bad length, etc.)." 2312 ::= { icmp 2 } 2314 icmpInDestUnreachs OBJECT-TYPE 2315 SYNTAX Counter32 2316 MAX-ACCESS read-only 2317 STATUS deprecated 2318 DESCRIPTION 2319 "The number of ICMP Destination Unreachable messages 2320 received." 2321 ::= { icmp 3 } 2323 icmpInTimeExcds OBJECT-TYPE 2324 SYNTAX Counter32 2325 MAX-ACCESS read-only 2326 STATUS deprecated 2327 DESCRIPTION 2328 "The number of ICMP Time Exceeded messages received." 2329 ::= { icmp 4 } 2331 icmpInParmProbs OBJECT-TYPE 2332 SYNTAX Counter32 2333 MAX-ACCESS read-only 2334 STATUS deprecated 2335 DESCRIPTION 2336 "The number of ICMP Parameter Problem messages received." 2337 ::= { icmp 5 } 2339 icmpInSrcQuenchs OBJECT-TYPE 2340 SYNTAX Counter32 2341 MAX-ACCESS read-only 2342 STATUS deprecated 2343 DESCRIPTION 2344 "The number of ICMP Source Quench messages received." 2345 ::= { icmp 6 } 2347 icmpInRedirects OBJECT-TYPE 2348 SYNTAX Counter32 2349 MAX-ACCESS read-only 2350 STATUS deprecated 2351 DESCRIPTION 2352 "The number of ICMP Redirect messages received." 2353 ::= { icmp 7 } 2355 icmpInEchos OBJECT-TYPE 2356 SYNTAX Counter32 2357 MAX-ACCESS read-only 2358 STATUS deprecated 2359 DESCRIPTION 2360 "The number of ICMP Echo (request) messages received." 2361 ::= { icmp 8 } 2363 icmpInEchoReps OBJECT-TYPE 2364 SYNTAX Counter32 2365 MAX-ACCESS read-only 2366 STATUS deprecated 2367 DESCRIPTION 2368 "The number of ICMP Echo Reply messages received." 2369 ::= { icmp 9 } 2371 icmpInTimestamps OBJECT-TYPE 2372 SYNTAX Counter32 2373 MAX-ACCESS read-only 2374 STATUS deprecated 2375 DESCRIPTION 2376 "The number of ICMP Timestamp (request) messages received." 2377 ::= { icmp 10 } 2379 icmpInTimestampReps OBJECT-TYPE 2380 SYNTAX Counter32 2381 MAX-ACCESS read-only 2382 STATUS deprecated 2383 DESCRIPTION 2384 "The number of ICMP Timestamp Reply messages received." 2385 ::= { icmp 11 } 2387 icmpInAddrMasks OBJECT-TYPE 2388 SYNTAX Counter32 2389 MAX-ACCESS read-only 2390 STATUS deprecated 2391 DESCRIPTION 2392 "The number of ICMP Address Mask Request messages received." 2393 ::= { icmp 12 } 2395 icmpInAddrMaskReps OBJECT-TYPE 2396 SYNTAX Counter32 2397 MAX-ACCESS read-only 2398 STATUS deprecated 2399 DESCRIPTION 2400 "The number of ICMP Address Mask Reply messages received." 2401 ::= { icmp 13 } 2403 icmpOutMsgs OBJECT-TYPE 2404 SYNTAX Counter32 2405 MAX-ACCESS read-only 2406 STATUS deprecated 2407 DESCRIPTION 2408 "The total number of ICMP messages which this entity 2409 attempted to send. Note that this counter includes all 2410 those counted by icmpOutErrors." 2411 ::= { icmp 14 } 2413 icmpOutErrors OBJECT-TYPE 2414 SYNTAX Counter32 2415 MAX-ACCESS read-only 2416 STATUS deprecated 2417 DESCRIPTION 2418 "The number of ICMP messages which this entity did not send 2419 due to problems discovered within ICMP such as a lack of 2420 buffers. This value should not include errors discovered 2421 outside the ICMP layer such as the inability of IP to route 2422 the resultant datagram. In some implementations there may 2423 be no types of error which contribute to this counter's 2424 value." 2425 ::= { icmp 15 } 2427 icmpOutDestUnreachs OBJECT-TYPE 2428 SYNTAX Counter32 2429 MAX-ACCESS read-only 2430 STATUS deprecated 2431 DESCRIPTION 2432 "The number of ICMP Destination Unreachable messages sent." 2433 ::= { icmp 16 } 2435 icmpOutTimeExcds OBJECT-TYPE 2436 SYNTAX Counter32 2437 MAX-ACCESS read-only 2438 STATUS deprecated 2439 DESCRIPTION 2440 "The number of ICMP Time Exceeded messages sent." 2441 ::= { icmp 17 } 2443 icmpOutParmProbs OBJECT-TYPE 2444 SYNTAX Counter32 2445 MAX-ACCESS read-only 2446 STATUS deprecated 2447 DESCRIPTION 2448 "The number of ICMP Parameter Problem messages sent." 2449 ::= { icmp 18 } 2451 icmpOutSrcQuenchs OBJECT-TYPE 2452 SYNTAX Counter32 2453 MAX-ACCESS read-only 2454 STATUS deprecated 2455 DESCRIPTION 2456 "The number of ICMP Source Quench messages sent." 2457 ::= { icmp 19 } 2459 icmpOutRedirects OBJECT-TYPE 2460 SYNTAX Counter32 2461 MAX-ACCESS read-only 2462 STATUS deprecated 2463 DESCRIPTION 2464 "The number of ICMP Redirect messages sent. For a host, this 2465 object will always be zero, since hosts do not send 2466 redirects." 2467 ::= { icmp 20 } 2469 icmpOutEchos OBJECT-TYPE 2470 SYNTAX Counter32 2471 MAX-ACCESS read-only 2472 STATUS deprecated 2473 DESCRIPTION 2474 "The number of ICMP Echo (request) messages sent." 2475 ::= { icmp 21 } 2477 icmpOutEchoReps OBJECT-TYPE 2478 SYNTAX Counter32 2479 MAX-ACCESS read-only 2480 STATUS deprecated 2481 DESCRIPTION 2482 "The number of ICMP Echo Reply messages sent." 2483 ::= { icmp 22 } 2485 icmpOutTimestamps OBJECT-TYPE 2486 SYNTAX Counter32 2487 MAX-ACCESS read-only 2488 STATUS deprecated 2489 DESCRIPTION 2490 "The number of ICMP Timestamp (request) messages sent." 2491 ::= { icmp 23 } 2493 icmpOutTimestampReps OBJECT-TYPE 2494 SYNTAX Counter32 2495 MAX-ACCESS read-only 2496 STATUS deprecated 2497 DESCRIPTION 2498 "The number of ICMP Timestamp Reply messages sent." 2499 ::= { icmp 24 } 2501 icmpOutAddrMasks OBJECT-TYPE 2502 SYNTAX Counter32 2503 MAX-ACCESS read-only 2504 STATUS deprecated 2505 DESCRIPTION 2506 "The number of ICMP Address Mask Request messages sent." 2507 ::= { icmp 25 } 2509 icmpOutAddrMaskReps OBJECT-TYPE 2510 SYNTAX Counter32 2511 MAX-ACCESS read-only 2512 STATUS deprecated 2513 DESCRIPTION 2514 "The number of ICMP Address Mask Reply messages sent." 2515 ::= { icmp 26 } 2517 -- conformance information 2518 ipMIBConformance OBJECT IDENTIFIER ::= { ipMIB 2 } 2520 ipMIBCompliances OBJECT IDENTIFIER ::= { ipMIBConformance 1 } 2521 ipMIBGroups OBJECT IDENTIFIER ::= { ipMIBConformance 2 } 2523 ipv6Conformance OBJECT IDENTIFIER ::= { ipv6MIB 3 } 2525 ipv6Compliances OBJECT IDENTIFIER ::= { ipv6Conformance 1 } 2526 ipv6Groups OBJECT IDENTIFIER ::= { ipv6Conformance 2 } 2528 -- ipv6IcmpConformance OBJECT IDENTIFIER ::= { ipv6IcmpMIB 2 } 2529 -- 2530 -- ipv6IcmpCompliances OBJECT IDENTIFIER ::= { ipv6IcmpConformance 1 } 2531 -- ipv6IcmpGroups OBJECT IDENTIFIER ::= { ipv6IcmpConformance 2 } 2533 -- compliance statements 2535 ipMIBCompliance MODULE-COMPLIANCE 2536 STATUS deprecated 2537 DESCRIPTION 2538 "The compliance statement for systems which implement only 2539 IPv4. For version-independence, this compliance statement 2540 is deprecated in favor of ipMIBCompliance2." 2541 MODULE -- this module 2542 MANDATORY-GROUPS { ipGroup, 2543 icmpGroup } 2544 ::= { ipMIBCompliances 1 } 2546 -- ipv6Compliance MODULE-COMPLIANCE 2547 -- .ST c 2548 -- .(D 2549 -- "The compliance statement for systems which 2550 -- implement ipv6 MIB." 2551 -- .)D 2552 -- MODULE -- -- this module 2553 -- MANDATORY-GROUPS { ipv6GeneralGroup, 2554 -- ipv6NotificationGroup } 2555 -- OBJECT ipv6Forwarding 2556 -- MIN-ACCESS read-only 2557 -- .(D 2558 -- "An agent is not required to provide write 2559 -- access to this object" 2560 -- .)D 2561 -- OBJECT ipv6DefaultHopLimit 2562 -- MIN-ACCESS read-only 2563 -- .(D 2564 -- "An agent is not required to provide write 2565 -- access to this object" 2566 -- .)D 2567 -- OBJECT ipv6IfDescr 2568 -- MIN-ACCESS read-only 2569 -- .(D 2570 -- "An agent is not required to provide write 2571 -- access to this object" 2572 -- .)D 2573 -- OBJECT ipv6IfIdentifier 2574 -- MIN-ACCESS read-only 2575 -- .(D 2576 -- "An agent is not required to provide write 2577 -- access to this object" 2578 -- .)D 2579 -- OBJECT ipv6IfIdentifierLength 2580 -- MIN-ACCESS read-only 2581 -- .(D 2582 -- "An agent is not required to provide write 2583 -- access to this object" 2584 -- .)D 2585 -- 2586 -- OBJECT ipv6IfAdminStatus 2587 -- MIN-ACCESS read-only 2588 -- .(D 2589 -- "An agent is not required to provide write 2590 -- access to this object" 2591 -- .)D 2592 -- OBJECT ipv6RouteValid 2593 -- MIN-ACCESS read-only 2594 -- .(D 2595 -- "An agent is not required to provide write 2596 -- access to this object" 2597 -- .)D 2598 -- OBJECT ipv6NetToMediaValid 2599 -- MIN-ACCESS read-only 2600 -- .(D 2601 -- "An agent is not required to provide write 2602 -- access to this object" 2603 -- .)D 2604 -- ::= { ipv6Compliances 1 } 2606 -- units of conformance 2608 ipGroup2 OBJECT-GROUP 2609 OBJECTS { ipForwarding, ipDefaultTTL } 2610 STATUS current 2611 DESCRIPTION 2612 "The group of IPv4-specific objects for basic management of 2613 IPv4 entities." 2614 ::= { ipMIBGroups 3 } 2616 ipIfStatsGroup OBJECT-GROUP 2617 OBJECTS { ipIfStatsInReceives, ipIfStatsInHdrErrors, 2618 ipIfStatsInTooBigErrors, ipIfStatsInNoRoutes, 2619 ipIfStatsInAddrErrors, ipIfStatsInUnknownProtos, 2620 ipIfStatsInTruncatedPkts, ipIfStatsInDiscards, 2621 ipIfStatsInDelivers, ipIfStatsOutForwDatagrams, 2622 ipIfStatsOutRequests, ipIfStatsOutDiscards, 2623 ipIfStatsOutFragOKs, ipIfStatsOutFragFails, 2624 ipIfStatsOutFragCreates, ipIfStatsReasmReqds, 2625 ipIfStatsReasmOKs, ipIfStatsReasmFails, 2626 ipIfStatsInMcastPkts, ipIfStatsOutMcastPkts, 2627 ipIfStatsInOctets, ipIfStatsOutOctets, 2628 ipIfStatsInBcastPkts, ipIfStatsOutBcastPkts, 2629 ipIfStatsInMcastOctets, ipIfStatsOutMcastOctets } 2630 STATUS current 2631 DESCRIPTION 2632 "IP per-interface or per-system statistics." 2633 ::= { ipMIBGroups 4 } 2635 -- XXX some HC statistics groups 2637 ipv6ScopeGroup OBJECT-GROUP 2638 OBJECTS { ipv6ScopeIdLinkLocal, ipv6ScopeIdSubnetLocal, 2639 ipv6ScopeIdAdminLocal, ipv6ScopeIdSiteLocal, 2640 ipv6ScopeId6, ipv6ScopeId7, 2641 ipv6ScopeIdOrganizationLocal, ipv6ScopeId9, 2642 ipv6ScopeIdA, ipv6ScopeIdB, 2643 ipv6ScopeIdC, ipv6ScopeIdD } 2644 STATUS current 2645 DESCRIPTION 2646 "The group of objects for managing IPv6 scope zones." 2647 ::= { ipMIBGroups 5 } 2649 ipGroup OBJECT-GROUP 2650 OBJECTS { ipForwarding, ipDefaultTTL, ipInReceives, 2651 ipInHdrErrors, ipInAddrErrors, 2652 ipForwDatagrams, ipInUnknownProtos, 2653 ipInDiscards, ipInDelivers, ipOutRequests, 2654 ipOutDiscards, ipOutNoRoutes, 2655 ipReasmTimeout, ipReasmReqds, ipReasmOKs, 2656 ipReasmFails, ipFragOKs, 2657 ipFragFails, ipFragCreates, 2658 ipAdEntAddr, ipAdEntIfIndex, ipAdEntNetMask, 2659 ipAdEntBcastAddr, ipAdEntReasmMaxSize, 2660 ipNetToMediaIfIndex, ipNetToMediaPhysAddress, 2661 ipNetToMediaNetAddress, ipNetToMediaType, 2662 ipRoutingDiscards } 2663 STATUS deprecated 2664 DESCRIPTION 2665 "The ip group of objects providing for basic management of IP 2666 entities, exclusive of the management of IP routes." 2667 ::= { ipMIBGroups 1 } 2669 icmpGroup OBJECT-GROUP 2670 OBJECTS { icmpInMsgs, icmpInErrors, 2671 icmpInDestUnreachs, icmpInTimeExcds, 2672 icmpInParmProbs, icmpInSrcQuenchs, 2673 icmpInRedirects, icmpInEchos, 2674 icmpInEchoReps, icmpInTimestamps, 2675 icmpInTimestampReps, icmpInAddrMasks, 2676 icmpInAddrMaskReps, icmpOutMsgs, 2677 icmpOutErrors, icmpOutDestUnreachs, 2678 icmpOutTimeExcds, icmpOutParmProbs, 2679 icmpOutSrcQuenchs, icmpOutRedirects, 2680 icmpOutEchos, icmpOutEchoReps, 2681 icmpOutTimestamps, icmpOutTimestampReps, 2682 icmpOutAddrMasks, icmpOutAddrMaskReps } 2683 STATUS deprecated 2684 DESCRIPTION 2685 "The icmp group of objects providing ICMP statistics." 2686 ::= { ipMIBGroups 2 } 2688 ipv6GeneralGroup2 OBJECT-GROUP 2689 OBJECTS { ipv6Forwarding, 2690 ipv6DefaultHopLimit } 2691 STATUS current 2692 DESCRIPTION 2693 "The IPv6 group of objects providing for basic management of 2694 IPv6 entities." 2695 ::= { ipv6Groups 3 } 2697 END 2699 5. Open Issues / To Do 2701 Need descriptive intro text, or LOTS more stuff in DESCRIPTIONs. 2703 Any other objects from ipv6IfTable that we need? What's 2704 ipv6IfEffectiveMtu good for? When can ipv6IfPhysicalAddress be 2705 different than the interface's ifPhysAddress? ipv6IfOperStatus? 2707 In the old IPv6 MIBs, the ipv6IfTable could have one ipv6InterfaceIndex 2708 per address to allow keeping stats per address. Should we allow for 2709 this? 2711 How to describe what stats are required, especially in the ICMP Msg 2712 table? Require per-interface, per-system, both, some? Require tracking 2713 every ICMP message type or just the ones the system cares about? What 2714 about ICMP codes? 2716 Need to update conformance info. 2718 Note: more open issues / to do items scattered in comments in MIB. 2720 6. Acknowledgments 2722 This document contains objects modified from RFC 1213 [1], RFC 2011 [2], 2723 RFC 2465 [4], and RFC 2466 [5]. 2725 7. References 2727 [1] Rose, M. and K. McCloghrie, "Management Information Base for Network 2728 Management of TCP/IP-based internets", RFC 1213, March 1991. 2730 [2] K. McCloghrie, "SNMPv2 Management Information Base for the Internet 2731 Protocol using SMIv2", RFC 2011, November 1996. 2733 [3] Narten, T., E. Nordmark and W. Simpson, "Neighbor Discovery for IP 2734 Version 6 (IPv6)", RFC 2461, December 1998. 2736 [4] Haskin, D. and S. Onishi, "Management Information Base for IP 2737 Version 6: Textual Conventions and General Group", RFC 2465, 2738 December 1998. 2740 [5] Haskin, D. and S. Onishi, "Management Information Base for IP 2741 Version 6: ICMPv6 Group", RFC 2466, December 1998. 2743 [6] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2744 Describing SNMP Management Frameworks", RFC 2571, April 1999. 2746 [7] Rose, M., and K. McCloghrie, "Structure and Identification of 2747 Management Information for TCP/IP-based Internets", STD 16, RFC 2748 1155, May 1990. 2750 [8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 2751 1212, March 1991. 2753 [9] Rose, M., "A Convention for Defining Traps for use with the SNMP", 2754 RFC 1215, March 1991. 2756 [10] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2757 and S. Waldbusser, "Structure of Management Information Version 2 2758 (SMIv2)", STD 58, RFC 2578, April 1999. 2760 [11] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2761 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2762 2579, April 1999. 2764 [12] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2765 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2766 2580, April 1999. 2768 [13] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2769 Management Protocol", STD 15, RFC 1157, May 1990. 2771 [14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2772 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 2774 [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2775 Mappings for Version 2 of the Simple Network Management Protocol 2776 (SNMPv2)", RFC 1906, January 1996. 2778 [16] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2779 Processing and Dispatching for the Simple Network Management 2780 Protocol (SNMP)", RFC 2572, April 1999. 2782 [17] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 2783 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2784 2574, April 1999. 2786 [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2787 Operations for Version 2 of the Simple Network Management Protocol 2788 (SNMPv2)", RFC 1905, January 1996. 2790 [19] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2791 2573, April 1999. 2793 [20] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2794 Control Model (VACM) for the Simple Network Management Protocol 2795 (SNMP)", RFC 2575, April 1999. 2797 [21] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 2798 Version 3 of the Internet-standard Network Management Framework", 2799 RFC 2570, April 1999. 2801 8. Security Considerations 2803 There are a number of management objects defined in this MIB that have a 2804 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 2805 considered sensitive or vulnerable in some network environments. The 2806 support for SET operations in a non-secure environment without proper 2807 protection can have a negative effect on network operations. 2809 There are a number of managed objects in this MIB that may contain 2810 sensitive information. These are: 2812 -- not yet evaluated 2814 It is thus important to control even GET access to these objects and 2815 possibly to even encrypt the values of these object when sending them 2816 over the network via SNMP. Not all versions of SNMP provide features 2817 for such a secure environment. 2819 SNMPv1 by itself is not a secure environment. Even if the network 2820 itself is secure (for example by using IPSec), even then, there is no 2821 control as to who on the secure network is allowed to access and GET/SET 2822 (read/change/create/delete) the objects in this MIB. 2824 It is recommended that the implementers consider the security features 2825 as provided by the SNMPv3 framework. Specifically, the use of the User- 2826 based Security Model RFC 2574 [17] and the View-based Access Control 2827 Model RFC 2575 [20] is recommended. 2829 It is then a customer/user responsibility to ensure that the SNMP entity 2830 giving access to an instance of this MIB, is properly configured to give 2831 access to the objects only to those principals (users) that have 2832 legitimate rights to indeed GET or SET (change/create/delete) them. 2834 9. Editor's Address 2835 Bill Fenner 2836 AT&T Labs -- Research 2837 75 Willow Rd 2838 Menlo Park, CA 94025 2839 USA 2841 Email: fenner@research.att.com 2843 10. Full Copyright Statement 2845 Copyright (C) The Internet Society (2001). All Rights Reserved. 2847 This document and translations of it may be copied and furnished to 2848 others, and derivative works that comment on or otherwise explain it or 2849 assist in its implementation may be prepared, copied, published and 2850 distributed, in whole or in part, without restriction of any kind, 2851 provided that the above copyright notice and this paragraph are included 2852 on all such copies and derivative works. However, this document itself 2853 may not be modified in any way, such as by removing the copyright notice 2854 or references to the Internet Society or other Internet organizations, 2855 except as needed for the purpose of developing Internet standards in 2856 which case the procedures for copyrights defined in the Internet 2857 Standards process must be followed, or as required to translate it into 2858 languages other than English. 2860 The limited permissions granted above are perpetual and will not be 2861 revoked by the Internet Society or its successors or assigns. 2863 This document and the information contained herein is provided on an "AS 2864 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2865 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2866 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2867 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2868 FITNESS FOR A PARTICULAR PURPOSE.