idnits 2.17.1 draft-ietf-ipv6-rfc2011-update-10.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 == The page length should not exceed 58 lines per page, but there was 133 longer pages, the longest (page 4) being 74 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 134 pages 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.) ** There are 37 instances of too long lines in the document, the longest one being 4 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 412: '... makes the lastChange objects a SHOULD...' RFC 2119 keyword, line 558: '...us & ipv6InterfaceAdminStatus - SHOULD...' RFC 2119 keyword, line 566: '...s & inetNetToMediaType - SHOULD NOT be...' RFC 2119 keyword, line 1379: '... is written the entity SHOULD save the...' RFC 2119 keyword, line 1394: '... is written the entity SHOULD save the...' (22 more instances...) -- The abstract seems to indicate that this document obsoletes RFC2011, but the header doesn't have an 'Obsoletes:' line to match this. -- The abstract seems to indicate that this document obsoletes RFC2465, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 3444 has weird spacing: '... used for o...' == Line 3550 has weird spacing: '...ould be allow...' == Line 6288 has weird spacing: '...imed to perta...' -- 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 (May 2004) is 7279 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) == Unused Reference: '6' is defined on line 6083, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 6086, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2461 (ref. '4') (Obsoleted by RFC 4861) ** Obsolete normative reference: RFC 2462 (ref. '5') (Obsoleted by RFC 4862) ** Obsolete normative reference: RFC 3291 (ref. '7') (Obsoleted by RFC 4001) -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Obsolete informational reference (is this intentional?): RFC 2011 (ref. '12') (Obsoleted by RFC 4293) -- Obsolete informational reference (is this intentional?): RFC 2465 (ref. '13') (Obsoleted by RFC 4293, RFC 8096) -- Obsolete informational reference (is this intentional?): RFC 2466 (ref. '14') (Obsoleted by RFC 4293, RFC 8096) -- Obsolete informational reference (is this intentional?): RFC 3041 (ref. '15') (Obsoleted by RFC 4941) -- Obsolete informational reference (is this intentional?): RFC 2096 (ref. '16') (Obsoleted by RFC 4292) Summary: 7 errors (**), 0 flaws (~~), 9 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IPv6 MIB Revision Design Team Shawn A. Routhier, Editor 3 INTERNET-DRAFT Wind River 4 Expires: November 2004 May 2004 6 Management Information Base 7 for the Internet Protocol (IP) 8 draft-ietf-ipv6-rfc2011-update-10.txt 10 Status of this Document 12 This document is an Internet-Draft and is in full conformance with all 13 provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF), its areas, and its working groups. Note that other groups 17 may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference material 22 or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This document is a product of the IPv6 MIB Revision Design Team. 31 Comments should be addressed to the authors, or the mailing list at 32 ipng@sunroof.eng.sun.com. 34 Copyright Notice 36 Copyright (C) The Internet Society (2004). All Rights Reserved. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) for 41 use with network management protocols in the Internet community. In 42 particular, it describes managed objects used for implementations of the 43 Internet Protocol (IP) in an IP version independent manner. This memo 44 obsoletes RFCs 2011, 2465 and 2466. 46 Table of Contents 48 1. The Internet-Standard Management Framework. . . . . . . . . . . . 2 49 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 2 50 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 51 3.1. Multi-Stack Implementations. . . . . . . . . . . . . . . . . . 15 52 3.2. Discussion of Tables and Groups. . . . . . . . . . . . . . . . 15 53 3.2.1. General Objects . . . . . . . . . . . . . . . . . . . . . . 15 54 3.2.2. Interface Tables. . . . . . . . . . . . . . . . . . . . . . 16 55 3.2.3. IP Statistics Tables. . . . . . . . . . . . . . . . . . . . 16 56 3.2.4. Internet Address Prefix Table . . . . . . . . . . . . . . . 19 57 3.2.5. Internet Address Table. . . . . . . . . . . . . . . . . . . 19 58 3.2.6. Internet Address Translation Table. . . . . . . . . . . . . 19 59 3.2.7. IPv6 Scope Zone Index . . . . . . . . . . . . . . . . . . . 20 60 3.2.8. Default Router Table. . . . . . . . . . . . . . . . . . . . 20 61 3.2.9. Router Advertisement Table. . . . . . . . . . . . . . . . . 20 62 3.2.10. ICMP Statistics Tables . . . . . . . . . . . . . . . . . . 20 63 3.2.11. Conformance and Compliance . . . . . . . . . . . . . . . . 21 64 3.2.12. Deprecated Objects . . . . . . . . . . . . . . . . . . . . 21 65 4. Updating Implementations. . . . . . . . . . . . . . . . . . . . . 21 66 4.1. Updating an implementation of the IPv4-only 67 IP-MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 68 4.2. Updating an implementation of the IPv6-MIB . . . . . . . . . . 23 69 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 70 6. Previous Work . . . . . . . . . . . . . . . . . . . . . . . . . . 126 71 7. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 72 7.1. Normative. . . . . . . . . . . . . . . . . . . . . . . . . . . 127 73 7.2. Informative. . . . . . . . . . . . . . . . . . . . . . . . . . 127 74 8. Security Considerations . . . . . . . . . . . . . . . . . . . . . 128 75 9. Editor's Contact Information. . . . . . . . . . . . . . . . . . . 130 76 10. Authors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 77 11. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . 131 78 12. Intellectual Property Notice . . . . . . . . . . . . . . . . . . 132 79 13. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 132 80 14. RFC Editor Notes . . . . . . . . . . . . . . . . . . . . . . . . 133 82 1. The Internet-Standard Management Framework 84 For a detailed overview of the documents that describe the current 85 Internet-Standard Management Framework, please refer to section 7 of RFC 86 3410 [9]. 88 Managed objects are accessed via a virtual information store, termed the 89 Management Information Base or MIB. MIB objects are generally accessed 90 through the Simple Network Management Protocol (SNMP). Objects in the 91 MIB are defined using the mechanisms defined in the Structure of 92 Management Information (SMI). This memo specifies a MIB module that is 93 compliant to the SMIv2, which is described in STD 58, RFC 2578 [1], STD 94 58, RFC 2579 [2] and STD 58, RFC 2580 [3]. 96 2. Revision History 98 One of the primary purposes of this revision of the IP MIB is to create 99 a single set of objects to describe and manage IP modules in an IP 100 version independent manner. Where RFCs 2465 and 2466 created a set of 101 objects independent from RFC2011 this document merges those three 102 documents into a single unified set of objects. The ipSystemStatsTable 103 and ipIfStatsTable tables are examples of updating objects to be 104 independent of IP version. Both of these tables contain counters to 105 reflect IP traffic statistics that originated in much earlier MIBs and 106 both include an IP address type in order to separate the information 107 based on IP version. 109 Another purpose of this document is to increase the manageability of a 110 node running IPv6 by adding new objects. Some of these tables, such as 111 ipDefaultRouterTable, may be useful on both IPv4 and IPv6 nodes while 112 others, such as ipv6RouterAdvertTable, are specific to a single 113 protocol. 115 -- RFC Editor 116 -- The remainder of this section (up to the section header "Overview") 117 -- is to be removed before publication. 118 -- 120 Changes from draft-ietf-ipv6-rfc2011-update-09.txt 122 May 2004 124 Renamed icmpNeutralMsg to icmpMsgStats and icmpNeutralTable et al 125 to icmpStats et al. 127 Corrected the OID of icmpMsgStatsTable to 30 from 28. 129 Changes from draft-ietf-ipv6-rfc2011-update-08.txt 131 April 2004 133 Renamed ipv4IfTableLastChange and ipv6IfTableLastChange to 134 ipv4InterfaceTableLastChange and ipv6InterfaceTableLastChange for 135 consistency with other names. 137 Renamed inetNetToMedia to ipNetToPhysical in order to avoid 138 conflicts with either the INET TC module or the previous versions 139 of the NetToMedia table. 141 Renamed inetIcmp to icmpNeutral in order to avoid conflicts with 142 either the INET TC module or the previous versions of the icmp 143 objects. 145 Renamed icmpGroup2 to icmpNeutralGroup to bring it in line with the 146 previous change. 148 Changes from draft-ietf-ipv6-rfc2011-update-07.txt 150 April 2004 152 Modified ipv4InterfaceAdminStatus and ipv6InterfaceAdminStatus to 153 be ipv4InterfaceEnableStatus and ipv6InterfaceEnableStatus 155 Removed ipv6InterfacePhysicalAddress and skipped over it's OID 157 Corrected the descriptions for ipIfStatsHCOutMcastOctets and 158 ipSystemStatsHCOutMcastOctets to be for octets transmitted rather 159 than for octets received. 161 Modified the OIDs for inetIcmpTable and inetIcmpMsgTable to skip 162 OIDs {icmp 27} and {icmp 28} 164 Changed ipNetToMediaGroup to inetNetToMediaGroup 166 Modifications per IESG review comments: 168 Removed mention of inalid prefixes from ipIfStatsInAddrErrors. 170 Removed mention of "unique on link" from ipv6InterfaceIdentifier. 172 Removed the "wellknown(3)" enum from the IpAddressOriginTC, but 173 didn't modify other values. 175 Changes from draft-ietf-ipv6-rfc2011-update-06.txt 177 February 2004 179 Removed the (0..128) constraint on ipAddressPrefixLength as a 180 better constraint, (0..2040) the maximum number of bits, has been 181 added to the TC. 183 Removed the comment characters on the syntax restriction for the 184 ipAddressRowStatus instance in the compliance statement. 186 Changes from draft-ietf-ipv6-rfc2011-update-05.txt 187 January 2004 189 Minor typographical updates. 191 Removed ipIfStatsOutNoRoutes and updated ipSystemStatsOutNoRoutes 192 to remove the description of ipIfStatsOutNoRoutes. 194 Added a size constraint on ipv6InterfacePhysicalAddress, 195 inetNetToMediaphysAddress and ipNetToMediaPhysAddress. 197 Added a value constraint on ipAddressPrefixLength 199 Added text to explain why ipNetToMediaIfIndex and 200 ipNetToMediaNetAddress have a max access value of read-create 201 rather than not-accessible. 203 Modified several objects to use a syntax of Integer32 instead of 204 INTEGER: ipDefaultTTL and ip6DefaultHopLimit. 206 Added the suffix 'TC' to IpAddressPrefixOriginTC, 207 IpAddressOriginTC, ipAddressStatusTC, and ipv6InterfaceIdentifierTC 208 to separate them from the objects of the similar name. 210 Modified 'Multi-Stack Implementations' to remove the mention of 211 communities and to add the Context table. 213 Updated the revision stamps in the MIB. 215 Added a units clause to ipReasmTimeout. 217 Modified ip6Forwarding and ip6DefaultHopLimit to be 218 ipv6IpForwarding and ipv6IpDefaultHopLimit. 220 Added text to all of the objects with syntax InetAddress specifying 221 which object determines the type of their addresses. 223 Added text to the description of the stats tables and to the 224 compliance statements of the HC groups to reinforce that the 32 bit 225 counters are the low order 32 bits of the 64 bit counters and that 226 the 32 bit counters are required even if the 64 bit counters are 227 included. 229 Added text suggesting that the spinlocks be the first varbind for 230 their objects in a PDU. 232 Specified that if ipAddressStorageType is permanent, no other 233 objects in the row are required to be able to be modified. 235 Added text to ipAddressTable to describe the philosophy behind 236 objects being read-only or read-create. 238 Added a reference clause to inetNetToMediaTable. 240 Added inetNetToMediaRowStatus and a defval to inetNetToMediaType. 242 Added some text to ipv6RouterAdvertMinInterval to try and clear up 243 its minimum value. 245 Added test to ipv6RouterAdvertRowStatus describing when a row can 246 go active. 248 Added text to ipMIBCompliance2 to make it clear that the required 249 address sizes match the required address types. 251 Made MIN-ACCESS for ipAddressSpinLock be not-accessible. 253 Tagged the syntax for ipAddressRowStatus as 'active(1)' the 254 compliance statement. 256 Added description of zero to ipv6InterfaceIdentifier and 257 ipAddressPrefixLength. 259 Added a informative references for the address architecture 260 document in the scope zone table. 262 Modified ipv6RouterAdvertCurHopLimit to refer to www.iana.org. 264 Added IPR statement. 266 Added ipAddressTable to the security section. 268 Added OutFragOks to the case diagram and a note describing the 269 intended relationship between the various fragment counters. 271 Changes from draft-ietf-ipv6-rfc2011-update-04.txt 273 December 2003 275 Corrected descriptive text for inetIcmpOutMsgs. It was referring 276 to messages received, it now refers to messages sent. 278 Modified several objects to use InetVersion instead of 279 InetAddressType. These objects were using the address type to 280 specify a version and can now make use of the more specific TC. 281 Changed ipSystemStatsAFType to ipSystemStatsIPVersion, changed 282 ipIfStatsAFType to ipIfStatsIPVersion, changed inetIcmpAFType to 283 inetIcmpIPVersion and inetIcmpMsgAFType to inetIcmpMsgIPVersion. 285 Modified the ipAddressTable to allow entries to be created or 286 modified. This entailed the addition of ipAddressSpinLock, 287 ipAddressRowStatus and ipAddressStorageType objects. Also 288 ipAddressIfIndex, ipAddressType and ipAddressStatus were made read- 289 create. 291 In the case diagram moved the incrementing of InHdrErrors to occur 292 before the incrementing of InMcastPkts and InBcastPkts. 294 Moved the broadcast counters into separate groups to allow them to 295 be tagged as required only for systems including IPv4. 297 Added note 5 to the case diagram describing the desired outcome 298 when counting short packets (header errors vs truncated packets). 300 Added text to note 2 of the case diagram to specify which discard 301 counter may be incremented. 303 Clarified text about summing interface levels statistics into 304 system level statistics. 306 Added ipv6InterfaceForwarding and made the object mandatory. Also 307 included text suggesting that a simple system that doesn't allow 308 forwarding to be enabled on a per-interface basis could set these 309 objects to "forward" and rely on ip6Forwarding to enable or disable 310 forwarding for the system. 312 Modified the size restrictions on ipv6InterfaceReasmMaxSize to be 313 (1500..65535). 315 Added ipv4InterfaceRetransmitTime and made it mandatory for IPv4 316 entities. 318 Made ipDefaultRouterIfIndex part of the index for 319 ipDefaultRouterTable. 321 Changed ipv6ScopeZoneIndexSubnetLocal to ipv6ScopeZoneIndex3. 323 Modified the size restrictions on ipv6RouterAdvertDefaultLifetime 324 to be (0 | 4..9000). 326 Added HC counters for InForwDatagrams, InDelivers, OutRequests and 327 OutForwDatagrams. 329 Modified the text for OutForwDatagrams to allow for forwarding of 330 locally generated packets. Also added a note to the Case diagram 331 mentioning that the forwarding counters may be incremented even if 332 the packets are generated by or destined for the local host. 334 Added references for the router selection draft and the update to 335 2096. 337 Removed the size constraint on indexes of type InetAddress. 339 Changed ipDefaultRouterAFType to ipDefaultRouterAddressType 341 Changes from draft-ietf-ipv6-rfc2011-update-03.txt 343 September 2003 345 Deprecated the ipRoutingDiscards object and add some text to 346 describe why and that the new version specific object can be found 347 in the IP-FORWARD-MIB. 349 Modified the syntax for ipIfStatsIfIndex to be InterfaceIndex 350 instead of InterfaceIndexOrZero as we no longer need the capability 351 of using zero within the index. (The MIB originally used a zero 352 index to specify the system level statistics.) 354 Added a description clause to the ipAddressGroup object. 356 Added the ipLastChangeGroup to ipMIBComliance2 with a description 357 of optional. 359 Changed draft-ietf-ipngwg-addr-arch-v3-11.txt to RFC3513. 361 Changes from draft-ietf-ipv6-rfc2011-update-02.txt 363 June 2003 365 Removed the ipv4 and ipv6 only requirements on the 366 ipSystemStatsAFType and ipIfStatsAFType objects. Instead added a 367 pseudo compliance statement requiring only global ipv4 and ipv6 368 types for those two objects as well as inetIcmpAFType and 369 inetIcmpMsgAFType. 371 Added a pseudo compliance statement requiring only global ipv4 and 372 ipv6 types for ipAddressPrefixType. 374 Added a pseudo compliance statement requiring only global and non 375 global ipv4 and ipv6 types for ipAddressAddrType, 376 inetNetToMediaNetAddressType and ipDefaultRouterAFType 377 In response to a question about the size constraint on the various 378 InetAddress objects (0..36). I have decided to leave this as is 379 for now. The actually size will be one of 4, 8, 16 or 20 depending 380 on the type in use and the syntax could be reduced to cover those 381 sizes. However using such a small limit might require a new mib if 382 a new address type is added to the InetAddress MIB that uses a 383 larger size. 36 seems to be a reasonable compromise for allowing 384 possible growth but avoiding problems with index length 385 limitations. 387 May 2003 389 Restored ipRoutingDiscards to a current object from the deprecated 390 group per discussions with previous MIB authors. The argument to 391 move it to deprecated relied on the fact that it really belongs 392 with the routing group rather than the main IP group. However as 393 it already exists in the IP group and any router must contain the 394 IP group it is not reasonable to remove it and create a new object 395 in the routing area simply to adjust where the object is rooted in 396 the MIB tree. This object was placed in a new group 397 "ipRoutingGroup" and the group was made mandatory in order to mimic 398 the previous MIB. 400 Changed the text to use "address type" or "address types" instead 401 of "address family" or "address families" in order to avoid any 402 confusion with the term as used by IANA in the assignment of 403 address family numbers. 405 Added some text to the description of ipAddressTable to remind 406 users that link-local addresses must use the "ipv6z" type. 408 Changes from draft-ietf-ipv6-rfc2011-update-01.txt 410 February 2003 412 Added ipLastChangeGroup which makes the lastChange objects a SHOULD 413 for agents that have the proper values available. 415 Added normative references for IMPORTed mibs. 417 January 2003 419 Editorial cleanup. 421 Renamed the ipv4If entries to ipv4Interface in order to be similar 422 to the ipv6Interface entries. 424 Updated the SNMP boilerplate. 426 Updated the references to remove many SNMP specific entries and 427 split the remainder into normative and informative. 429 Updated the security considerations section. 431 Decided not to add the netmask or BcastAddr information from the 432 deprecated ipAddrTable into the new mib as there was no major 433 support for them. 435 Removed IPv6 conformance and compliance OIDs as they are no longer 436 in use. 438 Renamed ipv6Forwarding and ipv6DefaultHopLimit to ip6Forwarding and 439 ip6DefaultHopLimit and moved them from the IPv6 branch to the IP 440 branch, thus removing the last objects in the IPv6 branch. 442 Added ipv6RouterAdvertSpinLock and ipv6RouterAdvertRowStatus 444 Added ipv4IfTableLastChange, ipv6IfTableLastChange and 445 ipIfStatsTableLastChange. 447 Renumbered pretty much everything at the IP branch level in order 448 to rationalize things and fit in the new objects. 450 Changes from draft-ops-rfc2011-update-02.txt: 452 October 2002 454 Renumbered objects in groups that had objects removed from one 455 draft to another. As per SMI rules no objects that have been 456 published in an RFC have been renumbered. The affected areas are: 457 ipv6InterfaceTable, ipIfStatsTable, inetIcmpTable and 458 inetIcmpMsgTable 460 Split the ipIfStatsTable into two tables under a common OID. The 461 two tables are ipSystemStatsTable which contains system-wide 462 statistics and ipIfStatsTable which contains interface-specific 463 statistics. The same counters are available from both tables. 465 The compliance and conformance section was rebuilt. ipGroup2 was 466 renamed to ipv4GeneralGroup and ipReasmTimeout was added to it. 467 The following groups were created: ipv4IfGroup, ipv6Ifgroup, 468 ipSystemStatsGroup, ipSystemStatsHCOctetGroup, 469 ipSystemStatsHCPacketGroup, ipIfStatsGroup, ipIfStatsHCOctetGroup, 470 ipIfStatsHCPacketGroup, ipAddressPrefixGroup, ipAddressGroup, 471 ipNetToMediaGroup, ipDefaultRouterGroup, ipv6RouterAdvertGroup and 472 icmpGroup2. The compliance section allows a compliant agent to 473 provide read-only access to all of the nominally read-write 474 objects. 476 Many minor changes to deal with errors found from mib compilers. 478 Changed the indexing from inetNetToMediaEntry to use a local copy 479 of the ifIndex. 481 Import InetZoneIndex for use a scope index. Previously this was 482 the ScopeIdentifier TC defined within this document. Also change 483 the naming convention for scopes to use index instead of 484 identifier. 486 Close several issues without changes: 488 Should we include an object or objects to express the capability of 489 an implementation with respect to items like extension headers for 490 IPv6. I have decided to not include such objects. I believe that 491 we should wait for some deployment experience to see if such 492 objects would be useful and to determine their proper granularity. 494 Are there other items that could be added to the ipv{4 6}IfTables 495 such as (for v4) directed broadcast, proxy arp, header compression, 496 broadcast address and arp cache timeout. As I receive only one 497 request for such objects I have not added them. 499 Is there a better SMI data type for the lifetime objects in the 500 ipAddressPrefixTable, ipDefaultRouterTable and 501 ipv6RouterAdvertTable. I don't think there is a better SMI data 502 type. We could generate some TCs for them (there are several 503 classes of lifetime) but I don't think that would be useful. 505 There was a note in the v6 interface table suggesting that some of 506 the objects could be removed. I think we have now removed all of 507 those objects and don't intend to remove more without comments. 509 Should the ipv6ScopeZoneIndexTable include associated objects to 510 provide a scope description similar to ipMRouteScopeNameString 511 (rfc2932)? 513 My current decision is to NOT add such an object or set of objects. 514 Should the ipv6AddressIfIdentifier be dropped? I think this 515 provides some utility in specifying the how addresses are formed 516 (at least some of them). There is also the further question of 517 moving the Ipv6AddressIfIdentifier TC somewhere else. I don't 518 think it is completely an EUI and therefore it should have a TC 519 somewhere other than the IF-MIB and here seems reasonable. 521 Any other objects from ipv6IfTable that we need? I don't think so. 523 Are there other possible sources for ipAddressPrefixOrigin? No 524 additions were suggested and no action was taken. 526 Changes from draft-ops-rfc2011-update-00.txt: 528 May 2002 530 Removed ipv6InterfaceEffectiveMtu and 531 ipv6InterfaceIdentifierLength. 533 Added text to ipAddressPrefixTable to describe its utility. 535 Added text to ipAddressTable to state that multicast addresses are 536 described in their own table(s). 538 Added ipv4IfAdminStatus and ipv6InterfaceAdminStatus. 540 Added text to ipAddressPrefixOrigin to describe that an address 541 becomes well known by assignment from IANA or the address 542 registries or by specification in a standards track RFC. 544 Added text to ipAddressOrigin to clarify the manual vs random 545 difference. 547 Added text to inetNetToMediaType to clarify the difference between 548 static and local. 550 Created textual conventions for the following IpAddressOrigin, 551 IpAddressStatus and IpAddressPrefixOrigin. 553 Added persistence information to all read-write and read-create 554 objects: 556 ipForwarding & ipDefaultTTL - should be persistent 558 ipv6Forwarding, ipv4AdminStatus & ipv6InterfaceAdminStatus - SHOULD 559 be persistent 561 ipv6InterfaceIdentifier - modified from RW to Read-only 563 ipNetToMediaPhysAddress & ipNetToMediaType - should not be 564 persistent 566 inetNetToMediaPhysAddress & inetNetToMediaType - SHOULD NOT be 567 persistent 568 Added text to specify that ifIndex objects (ipv4IfIndex, 569 ipv6InterfaceIfIndex, ipIfStatsIfIndex, ipAddressPrefixIfIndex, 570 ipAddressIfIndex and ipv6ScopeIdIfIndex) use the same indexes as 571 ifIndex. 573 Removed ifIndex and code from the descriptions of inetIcmpMsg{In 574 Out}Pkts. 576 Updated the text for the objects in the ipIfStatsTable. The new 577 text allows them to be either system wide or interface specific. 578 It also clarifies which interface should be used for some objects. 579 Finally descriptions were added to some newer objects. 581 Added ipIfStatsRefreshRate 583 Modified the author information. The main author list has been 584 moved to a section within the document and replaced on the front 585 page with the editor's name. The MIB contact information has been 586 modified. 588 Added text mentioning that ARP (RFC826) and ND (RFC2461) are the 589 two most likely ways of populating the Net to Media table. 591 Added a reference clause to inetIcmpMsgType pointing to the IANA 592 pages for ICMP and ICMPv6 parameters. 594 Added text mentioning that ipIfStatsInTooBigErrors is only valid 595 for IPv6 but that it should be instantiated for IPv4 as well. 597 Added text to the ipAddressPrefixTable and it's objects mentioning 598 that it isn't tuned for IPv4 and defaults to use for IPv4 599 addresses. 601 Added the ipAddressLastChanged object. 603 Added reference clauses to ipv6DefaultHopLimit and several objects 604 in the ipAddressPrefix table. I don't think that any other objects 605 that don't already have some text have something to reference. 607 Modified the IP statistics table. 609 ipIfStatsHCInUcastPkts became ipIfStatsHCInReceives 611 removed ipIfStatsInTooBigErrors and include those packets in 612 ipIfStatsOutFragFails 614 added ipIfStatsInForwDatagrams to count packets that we attempt to 615 forward 616 clarified the text in ipIfStatsOutForwDatagrams to make it clear 617 that "success" was related to the forwarding step and not the 618 transmission step 620 added ipIfStatsOutTransmits and ipIfStatsHCOutTransmits as counters 621 of the packets sent to the lower layers and pointed the OutOctet 622 counters to them 624 added ipIfStatsOutNoRoutes to count the number of locally generated 625 datagrams that couldn't be transmitted as no route was found 627 added ipIfStatsOutFragReqds to count the number of datagrams that 628 require fragmentation 630 Added text and a Case diagram describing the statistics table. 632 Added the ipAddressCreated object. 634 Removed ipIfStatsHCOutUcastPkts as HCOutTransmits replaces it. 636 Also re-arranged the statsTable sequence to try and group the 637 objects more rationally. 639 Added reachable and retransmit times to the ipv6InterfaceTable 641 Added Default router list. 643 Added router advertisement configuration table. 645 November 2001 647 Modified the ICMP message table to remove some indexes. The table 648 no longer tracks counters with per-interface or per-ICMP code 649 granularity. 651 12 Jul 2001 653 Changed to IPNG working group work item. 655 Removed mention of SIIT, since it's just for transition 657 Added lots of counters to ipIfStats table, and 658 ipIfStatsDiscontinuityTime 660 Changed ipAddressIfIndex and ScopeIdentifier to refer to IF-MIB 661 instead of RFC 2863 or RFC 2233 662 Removed text about agents supporting a subset of values from 663 ipv6Forwarding; this belongs in an AGENT-CAPABILITIES. 665 Un-deprecated ipReasmTimeout. XXX Do we need ipv6ReasmTimeout too? 666 I think not; RFC2460 seems to say that it's a constant 60 seconds. 668 Changes from first draft posted to v6mib mailing list: 670 23 Feb 2001 672 Added ipv4InterfaceTable 674 Added ipv6InterfaceTable 676 Added ipAddressPrefixTable and slightly reworked ipAddressTable 677 (nee inetAddressTable). 679 Deprecated ipMIBCompliance. Still need to finish updated ones. 681 Added copyright and table of contents. 683 7 Feb 2001 685 Renamed inetIfStats to ipIfStats 687 Added ipv6ScopeTable 689 Added ScopeIdentifier TC, which should be in INET-ADDRESS-MIB. 691 Added SIZE to inetAddrAddr and inetNetToMediaAddress 693 Wrote some boilerplate for multi-interface-or-system-wide counter 694 tables. 696 3. Overview 698 3.1. Multi-Stack Implementations 700 This MIB does not provide native support for implementations of multiple 701 stacks sharing the same address type. One option for supporting such 702 designs is to assign each stack within an address type to a separate 703 context. These contexts could then be selected based upon the context 704 name, with the Entity MIB and VACM Context Table providing methods for 705 listing the supported contexts. 707 3.2. Discussion of Tables and Groups 709 This MIB is composed of a small number of discrete objects and a series 710 of tables meant to form the base for managing IPv4 and IPv6 entities. 712 While some of the objects are meant to be included in all entities some 713 of the objects are only conditionally mandatory. The unconditionally 714 mandatory objects are mostly counters for IP and ICMP statistics. The 715 conditionally mandatory objects fall into one of several groups: objects 716 for use in higher bandwidth situations, objects for use with IPv4, 717 objects for use with IPv6 and objects for use on IPv6 routers. In short 718 it is not expected that every entity will implement all of the objects 719 within this MIB. The reader should consult the conformance and 720 compliance section to determine which objects are appropriate for a 721 given entity. 723 3.2.1. General Objects 725 In both IPv4 and IPv6 there are only a small number of "knobs" for 726 controlling the general IP stack. Most controls will be in a more 727 specific setting, such as for controlling a router or TCP engine. 729 This MIB defines a total of three general knobs only two of which are 730 used for both IPv4 and IPv6. 732 Objects are included for both protocols to enable or disable forwarding 733 and to set limits on the lifetime of a packet (ttl or hop count). 735 The third knob, the timeout period for reassembling fragments, is only 736 defined for IPv4 as IPv6 specifies this value directly. 738 Each group of objects is required when implementing their respective 739 protocols. 741 3.2.2. Interface Tables 743 This MIB includes a pair of tables to convey information about the IPv4 744 and IPv6 protocols that is interface specific. 746 Special note should be taken of the administrative status objects. 747 These are defined to allow each protocol to selectively enable or 748 disable interfaces. These objects can be used in conjunction with the 749 ifAdminStatus object to manipulate the interfaces as necessary. With 750 these three objects an interface may be enabled or disabled completely 751 as well as connected to the IPv4 stack, the IPv6 stack or both stacks. 752 Setting ifAdminStatus to "down" should not affect the protocol specific 753 status objects. 755 Each interface table is required when implementing their respective 756 protocols. 758 3.2.3. IP Statistics Tables 760 The IP statistics tables (ipSystemStatsTable and ipIfStatsTable) contain 761 objects to count the number of datagrams and octets that a given entity 762 has processed. Unlike the previous attempt this document uses a single 763 table for multiple address types. Typically the only two types of 764 interest are IPv4 and IPv6; however the table can support other types if 765 necessary. 767 The first table, ipSystemStatsTable, conveys system wide information. 768 (That is, the various counters are for all interfaces and not a specific 769 set of interfaces.) Its index is formed from a single sub-id that 770 represents the address type for which the statistics were counted. 772 The second table, ipIfStatsTable, conveys interface specific 773 information. Its index is formed from two sub-ids. The first 774 represents the address type (IPv4 and IPv6) and the interface within 775 that address type is represented by the second sub-id. 777 The two tables have a similar set of objects which are intended to count 778 the same things except for the difference in granularity. The object ID 779 "ipSystemStatsEntry.2" is reserved in order to align the object ids of 780 the counters in the first table with their counterparts in the second 781 table. 783 Several objects of note are ipSystemStatsDiscontinuityTime, 784 ipIfStatsDiscontinuityTime, ipSystemsStatsRefreshRate and 785 ipIfStatsRefreshRate. These objects provide information about the row 786 in the table more than about the system itself. 788 The discontinuity objects allow a management entity to determine if a 789 discontinuity event which would invalidate the management entity's 790 understanding of the counters has occurred. The system being re- 791 initialized or the interface being cycled are possible examples of a 792 discontinuity event. 794 The refresh objects allow a management entity to determine a proper 795 polling interval for the rest of the objects. 797 The following Case diagram represents the general ordering of the packet 798 counters. In order to avoid extra clutter the prefixes "ipSystemStats" 799 and "ipIfStats" have been removed from each of the counter names. 801 from from 802 interface upper 803 layers 804 V V 805 | | 806 + InReceives (1) + OutRequests 807 | | 808 | | 809 +--> InHdrErrors (5) +--> OutNoRoutes 810 | | 811 | | 812 +->-+ InMcastPkts (1) | 813 | V | 814 +-<-+ | 815 | | 816 +->-+ InBcastPkts (1) | 817 | V | 818 +-<-+ | 819 | | 820 | | 821 +--> InTruncatedPkts (5) | 822 | | 823 | | 824 +--> InAddrErrors | 825 | | 826 | | 827 +--> InDiscards (2) | 828 | | 829 | | 830 +--------+------->------+----->-----+----->-----+ 831 | InForwDatagrams (6) | OutForwDatagrams (6)| 832 | V +->-+ OutFragReqds 833 | InNoRoutes | | (packets) 834 / (local packet (3) | | 835 | IF is that of the address | +--> OutFragFails 836 | and may not be the receiving IF) | | (packets) 837 | | | 838 | | V OutFragOks 839 | | | (packets) (7) 840 | | | 841 +->-+ ReasmReqds (fragments) +-<-+ OutFragCreates 842 | | | (fragments) 843 | | | 844 | +--> ReasmFails (fragments (4)) +->-+ OutMcastPkts (1) 845 | | | V 846 | | +-<-+ 847 +-<-+ ReasmOKs (reassembled packets) | 848 | +->-+ OutBcastPkts (1) 849 | | V 850 +--> InUnknownProtos +-<-+ 851 | | 852 | | 853 +--> InDiscards (2) +--> OutDiscards (2) 854 | | 855 | | 856 + InDelivers + OutTransmits (1) 857 | | 858 V V 859 to to 860 upper interface 861 layers 863 (1) The HC counters and octet counters are also found at these points 864 but have been left out for clarity. 866 (2) The discard counters may increment at any time in the processing 867 path. Packets discarded to the left of InNoRoutes cause the InDiscards 868 counter to increment while those discarded to the right are counted in 869 the OutDiscards counters. 871 (3) Local packets on the input side are counted on the interface 872 associated with their destination address, which may not be the 873 interface on which they were received. This requirement is caused by 874 the possibility of losing the original interface during processing, 875 especially re-assembly. 877 (4) Some re-assembly algorithms may lose track of the number of 878 fragments during processing and so some fragments may not be counted in 879 this object. 881 (5) InTruncatedPkts should only be incremented if the frame contained a 882 valid header but was otherwise shorter than required. Frames that are 883 too short to contain a valid header should be counted as InHdrErrors. 885 (6) The forwarding objects may be incremented even for packets that were 886 originated locally or are destined for the local host if their addresses 887 are such that the local host would need to forward the packet to pass it 888 to the correct interface. 890 (7) When fragmenting a packet an entity should increment the 891 OutFragFails counter rather than the OutDiscards counter in order to 892 preserve the equation FragOks + FragFails == FragRqds. 894 The objects in both tables are spread amongst several conformance groups 895 based on the bandwidth required to wrap the counters within an hour. 896 The base system group is mandatory for all entities. The other system 897 groups are optional depending on bandwidth. The interface specific- 898 groups are optional. 900 3.2.4. Internet Address Prefix Table 902 This table provides information about the prefixes that this entity is 903 using including their lifetimes. This table provides a convenient place 904 to which other tables that make use of prefixes, such as the 905 ipAddressTable, may point. By including this table the MIB can supply 906 the prefix information for all addresses yet minimize the amount of 907 duplication required in storing and accessing this data. This 908 arrangement also makes the relationship between addresses that have the 909 same prefix clear. 911 This table is required for IPv6 entities. 913 3.2.5. Internet Address Table 915 This table lists the IP addresses (both IPv4 and IPv6) used by this 916 entity. It also includes some basic information about how and when the 917 address was formed and last updated. This table allows a manager to 918 determine who a given entity thinks it is. 920 This table is required for all IP entities. 922 3.2.6. Internet Address Translation Table 924 This table provides a mapping between IP layer addresses and physical 925 addresses as would be formed by either ARP for IPv4 or the neighbor 926 discovery protocol for IPv6. 928 3.2.7. IPv6 Scope Zone Index 930 This table specifies the zone index to interface mapping. By examining 931 the table a manager can determine which groups of interfaces are within 932 a particular zone for a given scope. 934 The zone index information is only valid within a given entity, the 935 indexes used on one entity may not be comparable to those used on a 936 different entity. 938 This table is required for IPv6 entities. 940 3.2.8. Default Router Table 942 This table lists the default routers known to this entity. This table 943 is intended to be a simple list to display the information end nodes may 944 have been configured with or acquired through a simple system such as 945 IPv6 router advertisements. Managers attempting to view more 946 complicated routing information should examine the routing specific 947 tables from other MIBs. 949 This table is required for all entities. 951 3.2.9. Router Advertisement Table 953 This table contains the non-routing information that an IPv6 router 954 would use in constructing a router advertisement message. It does not 955 contain information about the prefixes or other routing specific 956 information that the router might advertise. The router should acquire 957 such information from either the routing tables or from some routing 958 table specific MIB. 960 This table is only required for IPv6 router entities. 962 3.2.10. ICMP Statistics Tables 964 There are two sets of statistics for ICMP. The first contains a simple 965 set of counters to track the number of ICMP messages and errors 966 processed by this entity. 968 The second supplies more detail about the ICMP messages processed by 969 this entity. Its index is formed from two sub-ids. The first 970 represents the address type (IPv4 and IPv6) and the particular message 971 type being counted is represented by the second sub-id. 973 Both of these tables are required for all entities. 975 3.2.11. Conformance and Compliance 977 This MIB contains several sets of objects. Some of these sets are 978 useful on all types of entities while others are only useful on a 979 limited subset of entities. The conformance section attempts to group 980 the objects into sets that may be discussed as units and the compliance 981 section then details which of these units are required in various 982 circumstances. 984 The circumstances used in the compliance section are implementing IPv4, 985 IPv6 or IPv6 router functions and having bandwidth less than 20MB, 986 between 20MB and 650MB or greater than 650MB. 988 3.2.12. Deprecated Objects 990 This MIB also includes a set of deprecated objects from previous 991 iterations. They are included as part of the historical record. 993 4. Updating Implementations 995 There are several general classes of change that are required. 997 The first and most major change is that most of the previous objects 998 have different object ids and additional indexes to support the 999 possibility of different address types. The general counters for IP and 1000 ICMP are examples of this. They have been moved to the 1001 ipSystemStatsTable and icmpMsgStatsTable respectively. 1003 The second change is the extension of all address objects to allow for 1004 both IPv4 and IPv6 addresses and the addition of an address type object 1005 to specify what address type is in use. 1007 The third change is the addition of several new objects to the 1008 replacement for a previously existing table such as ipNetToPhysical. 1010 The fourth change is the addition of completely new tables such as 1011 ipIfStatsTable and ipDefaultRouterTable. The first is based on the 1012 previous statistics groups while the second is completely new to this 1013 MIB. 1015 4.1. Updating an implementation of the IPv4-only IP-MIB 1017 The somewhat more specific changes that are required for IPv4 follow. 1018 Note well: this is not meant to be an exhaustive list and the reader 1019 should examine the MIB for full details. 1021 Several of the general objects (ipForwarding, ipDefaultTTL, 1022 ipReasmTimeout) remain unchanged. 1024 Most of the rest of the general objects were counters and have been 1025 moved into the ipSystemStatsTable. The basic instrumentation should 1026 remain the same though the object definitions should be checked for any 1027 clarifications. If they aren't already in a structure putting the 1028 counter variables in one would be useful. Several new objects have been 1029 added to count additional items, instrumentation code must be added for 1030 these objects. Finally the SNMP routines must be updated to handle the 1031 new indexing. 1033 In addition to the ipSystemStatsTable the MIB includes the 1034 ipIfStatsTable. This table counts the same items as the system table 1035 but does so on a per interface basis. It is optional and may be 1036 ignored. If you decide to implement it you may wish to arrange to 1037 collect the data on a per-interface basis and then sum those counters in 1038 order to provide the aggregate system level statistics. However if you 1039 choose to provide the system level statistics by summing the interface 1040 level counters no interface level statistics can be lost - if an 1041 interface is removed the statistics associated with it must be retained. 1043 The ipAddrTable has, loosely, been converted to the ipAddressTable. 1044 While the general idea remains the same the ipAddressTable is 1045 sufficiently different that writing new code may be easier than updating 1046 old code. The primary difference is the addition of several new 1047 objects. In addition the ipAdEntReasmMaxSize has been moved to another 1048 table, ipv4InterfaceTable. As above the SNMP routines will need to be 1049 updated to handle the new indexing. 1051 The ipNetToMediaTable has been moved to the ipNetToPhysicalTable. These 1052 tables are fairly similar and updating the old code may be 1053 straightforward. As above the SNMP routines will need to be updated to 1054 handle the new indexing. 1056 Two new tables, ipv4InterfaceTable and ipDefaultRouterTable, are 1057 required as well as several new ICMP counters. 1059 Finally there are several tables that are required for IPv6 but are 1060 optional for IPv4 that you may elect to implement. 1062 4.2. Updating an implementation of the IPv6-MIB 1064 The somewhat more specific changes that are required for IPv6 follow. 1065 Note well: this is not meant to be an exhaustive list and the reader 1066 should examine the MIB for full details. 1068 Two of the general objects, ipv6Forwarding and ipv6DefaultHopLimit, have 1069 been renamed and given new object identifiers within the ip branch but 1070 are otherwise unchanged. The new names are ipv6IpForwarding and 1071 ipv6IpDefaultHopLimit. 1073 While there is an ipv6InterfaceTable that contains some of the pieces 1074 from the ipv6IfTable the two are somewhat different in concept. The 1075 ipv6IfTable was meant to replicate the ifTable while the 1076 ipv6InterfaceTable is meant to be an addition to the ifTable. As such 1077 items that were duplicated between the ifTable and ipv6IfTable have been 1078 removed and some new objects added. 1080 The ipv6IfStatsTable most closely resembles the ipIfStatsTable with an 1081 additional index for the address type and most of the instrumentation 1082 should be re-usable. Some new objects have been added to the 1083 ipIfStatsTable. As above the SNMP routines will need to be updated to 1084 handle the new indexing. Finally the ipIfStatsTable is optional and may 1085 be ignored. 1087 The ipSystemStatsTable is effectively new, but it may be able to make 1088 use of most of the instrumentation from the old ipv6IfStatsTable. As 1089 with the IPv4 discussion one implementation strategy would be to count 1090 the statistics for the ipIfStatsTable and aggregate them when queried 1091 for this table. Again, as with the IPv4 discussion, this strategy only 1092 works if the interfaces can not be removed or if the statistics for 1093 removed interfaces are somehow retained. 1095 The ipv6AddrPrefixTable is now the ipAddressPrefixTable. The new table 1096 contains an extra object and the additional index required for IPv4 1097 compatibility. As above the SNMP routines will need to be updated to 1098 handle the new indexing. 1100 The ipAddressTable is loosely based on the ipv6AddrTable but has changed 1101 considerably with the addition of several new objects and the removal of 1102 one of its indexes. 1104 The IPv6 routing information (ipv6RouteNumber, ipv6DiscardedRoutes and 1105 ipv6RouteTable) has been removed from this MIB. The replacements or 1106 updates for this information is in the update to the IP Forwarding Table 1107 MIB [16]. The ipv6NetToMediaTable has been converted to the 1108 ipNetToPhysicalTable. The new table contains an extra object and the 1109 additional index required for IPv4 compatibility. As above the SNMP 1110 routines will need to be updated to handle the new indexing. 1112 The ICMP tables have been substantially changed. The previous tables 1113 required counting on a per-message and per-interface basis. The new 1114 tables only require counting on a per-message per-protocol basis and 1115 include an aggregate of all messages on a per-protocol basis. 1117 In addition to the above several new tables have been added. Both the 1118 ipv6ScopeZoneIndexTable and ipDefaultRouterTable are required on all 1119 IPv6 entities. The ipv6RouterAdvertTable is only required on IPv6 1120 routers. 1122 5. Definitions 1124 IP-MIB DEFINITIONS ::= BEGIN 1126 IMPORTS 1127 MODULE-IDENTITY, OBJECT-TYPE, 1128 Integer32, Counter32, IpAddress, 1129 mib-2, Unsigned32, Counter64, 1130 zeroDotZero FROM SNMPv2-SMI 1131 PhysAddress, TruthValue, 1132 TimeStamp, RowPointer, 1133 TEXTUAL-CONVENTION, TestAndIncr, 1134 RowStatus, StorageType FROM SNMPv2-TC 1135 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 1136 InetAddress, InetAddressType, 1137 InetAddressPrefixLength, 1138 InetVersion, InetZoneIndex FROM INET-ADDRESS-MIB 1139 InterfaceIndex FROM IF-MIB; 1141 ipMIB MODULE-IDENTITY 1142 LAST-UPDATED "200404260000Z" 1143 ORGANIZATION "IETF IPv6 MIB Revision Team" 1144 CONTACT-INFO 1145 "Editor: 1146 Shawn A. Routhier 1147 Wind River 1148 500 Wind River Way 1149 Alameda, CA 1150 USA 1152 Phone: +1 510 749 2095 1153 EMail: " 1154 DESCRIPTION 1155 "The MIB module for managing IP and ICMP implementations, but 1156 excluding their management of IP routes. 1158 Copyright (C) The Internet Society (2004). This version of 1159 this MIB module is part of RFC xxxx; see the RFC itself for 1160 full legal notices." 1161 -- RFC Editor 1162 -- Please update this reference as the RFC number is assigned. 1163 -- 1164 REVISION "200404260000Z" 1165 DESCRIPTION 1166 "The IP version neutral revision with added IPv6 objects for 1167 ND, default routers and router advertisements. As well as 1168 being the successor to RFC2011 this MIB is also the 1169 successor to RFC2465 and RFC 2466. Published as RFC xxxx." 1171 -- RFC Editor 1172 -- Please update this reference as the RFC number is assigned. 1173 -- 1175 REVISION "199411010000Z" 1176 DESCRIPTION 1177 "A separate MIB module (IP-MIB) for IP and ICMP management 1178 objects. Published as RFC 2011." 1180 REVISION "199103310000Z" 1181 DESCRIPTION 1182 "The initial revision of this MIB module was part of MIB-II, 1183 which was published as RFC 1213." 1184 ::= { mib-2 48} 1186 -- 1187 -- The textual conventions we define and use in this MIB. 1188 -- 1190 IpAddressOriginTC ::= TEXTUAL-CONVENTION 1191 STATUS current 1192 DESCRIPTION 1193 "The origin of the address. 1195 manual(2) indicates that the address was manually configured 1196 to a specified address, e.g. by user configuration. 1198 dhcp(4) indicates an address that was assigned to this 1199 system by a DHCP server. 1201 linklayer(5) indicates an address created by IPv6 stateless 1202 auto-configuration. 1204 random(6) indicates an address chosen by the system at 1205 random, e.g. an IPv4 address within 169.254/16, or an RFC 1206 3041 privacy address." 1207 SYNTAX INTEGER { 1208 other(1), 1209 manual(2), 1210 dhcp(4), 1211 linklayer(5), 1212 random(6) 1213 } 1215 IpAddressStatusTC ::= TEXTUAL-CONVENTION 1216 STATUS current 1217 DESCRIPTION 1218 "The status of an address. Most of the states correspond to 1219 states from the IPv6 Stateless Address Autoconfiguration 1220 protocol [5]. 1222 The preferred(1) state indicates that this is a valid 1223 address that can appear as the destination or source address 1224 of a packet. 1226 The deprecated(2) state indicates that this is a valid but 1227 deprecated address that should no longer be used as a source 1228 address in new communications, but packets addressed to such 1229 an address are processed as expected. 1231 The invalid(3) state indicates that this isn't a valid 1232 address and it shouldn't appear as the destination or source 1233 address of a packet. 1235 The inaccessible(4) state indicates that the address is not 1236 accessible because the interface to which this address is 1237 assigned is not operational. 1239 The unknown(5) state indicates that the status can not be 1240 determined for some reason. 1242 The tentative(6) state indicates the uniqueness of the 1243 address on the link is being verified. Addresses in this 1244 state should not be used for general communication and 1245 should only be used to determine the uniqueness of the 1246 address. 1248 The duplicate(7) state indicates the address has been 1249 determined to be non-unique on the link and so must not be 1250 used. 1252 In the absence of other information, an IPv4 address is 1253 always preferred(1)." 1254 REFERENCE "RFC 2462" 1255 SYNTAX INTEGER { 1256 preferred(1), 1257 deprecated(2), 1258 invalid(3), 1259 inaccessible(4), 1260 unknown(5), 1261 tentative(6), 1262 duplicate(7) 1263 } 1265 IpAddressPrefixOriginTC ::= TEXTUAL-CONVENTION 1266 STATUS current 1267 DESCRIPTION 1268 "The origin of this prefix. 1270 manual(2) indicates a prefix that was manually configured. 1272 wellknown(3) indicates a well-known prefix, e.g. 169.254/16 1273 for IPv4 auto-configuration or fe80::/10 for IPv6 link-local 1274 addresses. Well known prefixes may be assigned by IANA or 1275 the address registries or by specification in a standards 1276 track RFC. 1278 dhcp(4) indicates a prefix that was assigned by a DHCP 1279 server. 1281 routeradv(5) indicates a prefix learned from a router 1282 advertisement. 1284 Note: while IpAddressOriginTC and IpAddressPrefixOriginTC 1285 are similar they are not identical. The first defines how 1286 an address was created while the second defines how a prefix 1287 was found." 1288 SYNTAX INTEGER { 1289 other(1), 1290 manual(2), 1291 wellknown(3), 1292 dhcp(4), 1293 routeradv(5) 1294 } 1296 Ipv6AddressIfIdentifierTC ::= TEXTUAL-CONVENTION 1297 DISPLAY-HINT "2x:" 1298 STATUS current 1299 DESCRIPTION 1300 "This data type is used to model IPv6 address 1301 interface identifiers. This is a binary string 1302 of up to 8 octets in network byte-order." 1303 SYNTAX OCTET STRING (SIZE (0..8)) 1305 -- 1306 -- the IP general group 1307 -- some objects that affect all of IPv4 1308 -- 1310 ip OBJECT IDENTIFIER ::= { mib-2 4 } 1312 ipForwarding OBJECT-TYPE 1313 SYNTAX INTEGER { 1314 forwarding(1), -- acting as a router 1315 notForwarding(2) -- NOT acting as a router 1316 } 1317 MAX-ACCESS read-write 1318 STATUS current 1319 DESCRIPTION 1320 "The indication of whether this entity is acting as an IPv4 1321 router in respect to the forwarding of datagrams received 1322 by, but not addressed to, this entity. IPv4 routers forward 1323 datagrams. IPv4 hosts do not (except those source-routed 1324 via the host). 1326 When this object is written the entity should save the 1327 change to non-volatile storage and restore the object from 1328 non-volatile storage upon re-initialization of the system. 1329 Note: a stronger requirement is not used because this object 1330 was previously defined." 1331 ::= { ip 1 } 1333 ipDefaultTTL OBJECT-TYPE 1334 SYNTAX Integer32 (1..255) 1335 MAX-ACCESS read-write 1336 STATUS current 1337 DESCRIPTION 1338 "The default value inserted into the Time-To-Live field of 1339 the IPv4 header of datagrams originated at this entity, 1340 whenever a TTL value is not supplied by the transport layer 1341 protocol. 1343 When this object is written the entity should save the 1344 change to non-volatile storage and restore the object from 1345 non-volatile storage upon re-initialization of the system. 1346 Note: a stronger requirement is not used because this object 1347 was previously defined." 1348 ::= { ip 2 } 1350 ipReasmTimeout OBJECT-TYPE 1351 SYNTAX Integer32 1352 UNITS "seconds" 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "The maximum number of seconds which received fragments are 1357 held while they are awaiting reassembly at this entity." 1358 ::= { ip 13 } 1360 -- 1361 -- the IPv6 general group 1362 -- Some objects that affect all of IPv6 1363 -- 1365 ipv6IpForwarding OBJECT-TYPE 1366 SYNTAX INTEGER { 1367 forwarding(1), -- acting as a router 1368 notForwarding(2) -- NOT acting as a router 1369 } 1370 MAX-ACCESS read-write 1371 STATUS current 1372 DESCRIPTION 1373 "The indication of whether this entity is acting as an IPv6 1374 router on any interface in respect to the forwarding of 1375 datagrams received by, but not addressed to, this entity. 1376 IPv6 routers forward datagrams. IPv6 hosts do not (except 1377 those source-routed via the host). 1379 When this object is written the entity SHOULD save the 1380 change to non-volatile storage and restore the object from 1381 non-volatile storage upon re-initialization of the system." 1382 ::= { ip 25 } 1384 ipv6IpDefaultHopLimit OBJECT-TYPE 1385 SYNTAX Integer32 (0..255) 1386 MAX-ACCESS read-write 1387 STATUS current 1388 DESCRIPTION 1389 "The default value inserted into the Hop Limit field of the 1390 IPv6 header of datagrams originated at this entity, whenever 1391 a Hop Limit value is not supplied by the transport layer 1392 protocol. 1394 When this object is written the entity SHOULD save the 1395 change to non-volatile storage and restore the object from 1396 non-volatile storage upon re-initialization of the system." 1397 REFERENCE "RFC2461 Section 6.3.2" 1398 ::= { ip 26 } 1400 -- 1401 -- IPv4 Interface Table 1402 -- 1404 ipv4InterfaceTableLastChange OBJECT-TYPE 1405 SYNTAX TimeStamp 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "The value of sysUpTime on the most recent occasion at which 1410 a row in the ipv4InterfaceTable was added or deleted or when 1411 an ipv4InterfaceReasmMaxSize or an ipv4InterfaceEnableStatus 1412 object was modified. 1414 If new objects are added to the ipv6InterfaceTable that 1415 require the ipv6InterfaceTableLastChange to be updated when 1416 they are modified they must specify that requirement in 1417 their description clause." 1418 ::= { ip 27 } 1420 ipv4InterfaceTable OBJECT-TYPE 1421 SYNTAX SEQUENCE OF Ipv4InterfaceEntry 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 "The table containing per-interface IPv4-specific 1426 information." 1427 ::= { ip 28 } 1429 ipv4InterfaceEntry OBJECT-TYPE 1430 SYNTAX Ipv4InterfaceEntry 1431 MAX-ACCESS not-accessible 1432 STATUS current 1433 DESCRIPTION 1434 "An entry containing IPv4-specific information for a specific 1435 interface." 1436 INDEX { ipv4InterfaceIfIndex } 1437 ::= { ipv4InterfaceTable 1 } 1439 Ipv4InterfaceEntry ::= SEQUENCE { 1440 ipv4InterfaceIfIndex InterfaceIndex, 1441 ipv4InterfaceReasmMaxSize Integer32, 1442 ipv4InterfaceEnableStatus INTEGER, 1443 ipv4InterfaceRetransmitTime Unsigned32 1444 } 1446 ipv4InterfaceIfIndex OBJECT-TYPE 1447 SYNTAX InterfaceIndex 1448 MAX-ACCESS not-accessible 1449 STATUS current 1450 DESCRIPTION 1451 "The index value which uniquely identifies the interface to 1452 which this entry is applicable. The interface identified by 1453 a particular value of this index is the same interface as 1454 identified by the same value of the IF-MIB's ifIndex." 1455 ::= { ipv4InterfaceEntry 1 } 1457 ipv4InterfaceReasmMaxSize OBJECT-TYPE 1458 SYNTAX Integer32 (0..65535) 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "The size of the largest IPv4 datagram which this entity can 1463 re-assemble from incoming IPv4 fragmented datagrams received 1464 on this interface." 1465 ::= { ipv4InterfaceEntry 2 } 1467 ipv4InterfaceEnableStatus OBJECT-TYPE 1468 SYNTAX INTEGER { 1469 up(1), 1470 down(2) 1471 } 1472 MAX-ACCESS read-write 1473 STATUS current 1474 DESCRIPTION 1475 "The indication of whether IPv4 is enabled (up) or disabled 1476 (down) on this interface. This object does not affect the 1477 state of the interface itself, only its connection to an 1478 IPv4 stack. The IF-MIB should be used to control the state 1479 of the interface." 1480 ::= { ipv4InterfaceEntry 3 } 1482 ipv4InterfaceRetransmitTime OBJECT-TYPE 1483 SYNTAX Unsigned32 1484 UNITS "milliseconds" 1485 MAX-ACCESS read-only 1486 STATUS current 1487 DESCRIPTION 1488 "The time between retransmissions of ARP requests to a 1489 neighbor when resolving the address or when probing the 1490 reachability of a neighbor." 1491 REFERENCE "RFC1122" 1492 DEFVAL { 1000 } 1493 ::= { ipv4InterfaceEntry 4 } 1495 -- 1496 -- v6 interface table 1497 -- 1499 ipv6InterfaceTableLastChange OBJECT-TYPE 1500 SYNTAX TimeStamp 1501 MAX-ACCESS read-only 1502 STATUS current 1503 DESCRIPTION 1504 "The value of sysUpTime on the most recent occasion at which 1505 a row in the ipv6InterfaceTable was added or deleted or when 1506 an ipv6InterfaceReasmMaxSize, ipv6InterfaceIdentifier, 1507 ipv6InterfaceEnableStatus, ipv6InterfaceReachableTime, 1508 ipv6InterfaceRetransmitTime or ipv6InterfaceForwarding 1509 object was modified. 1511 If new objects are added to the ipv6InterfaceTable that 1512 require the ipv6InterfaceTableLastChange to be updated when 1513 they are modified they must specify that requirement in 1514 their description clause." 1515 ::= { ip 29 } 1517 ipv6InterfaceTable OBJECT-TYPE 1518 SYNTAX SEQUENCE OF Ipv6InterfaceEntry 1519 MAX-ACCESS not-accessible 1520 STATUS current 1521 DESCRIPTION 1522 "The table containing per-interface IPv6-specific 1523 information." 1524 ::= { ip 30 } 1526 ipv6InterfaceEntry OBJECT-TYPE 1527 SYNTAX Ipv6InterfaceEntry 1528 MAX-ACCESS not-accessible 1529 STATUS current 1530 DESCRIPTION 1531 "An entry containing IPv6-specific information for a given 1532 interface." 1533 INDEX { ipv6InterfaceIfIndex } 1534 ::= { ipv6InterfaceTable 1 } 1536 Ipv6InterfaceEntry ::= SEQUENCE { 1537 ipv6InterfaceIfIndex InterfaceIndex, 1538 ipv6InterfaceReasmMaxSize Unsigned32, 1539 ipv6InterfaceIdentifier Ipv6AddressIfIdentifierTC, 1540 ipv6InterfaceEnableStatus INTEGER, 1541 ipv6InterfaceReachableTime Unsigned32, 1542 ipv6InterfaceRetransmitTime Unsigned32, 1543 ipv6InterfaceForwarding INTEGER 1544 } 1546 ipv6InterfaceIfIndex OBJECT-TYPE 1547 SYNTAX InterfaceIndex 1548 MAX-ACCESS not-accessible 1549 STATUS current 1550 DESCRIPTION 1551 "The index value which uniquely identifies the interface to 1552 which this entry is applicable. The interface identified by 1553 a particular value of this index is the same interface as 1554 identified by the same value of the IF-MIB's ifIndex." 1555 ::= { ipv6InterfaceEntry 1 } 1557 ipv6InterfaceReasmMaxSize OBJECT-TYPE 1558 SYNTAX Unsigned32 (1500..65535) 1559 UNITS "octets" 1560 MAX-ACCESS read-only 1561 STATUS current 1562 DESCRIPTION 1563 "The size of the largest IPv6 datagram which this entity can 1564 re-assemble from incoming IPv6 fragmented datagrams received 1565 on this interface." 1566 ::= { ipv6InterfaceEntry 2 } 1568 ipv6InterfaceIdentifier OBJECT-TYPE 1569 SYNTAX Ipv6AddressIfIdentifierTC 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "The Interface Identifier for this interface. The Interface 1574 Identifier is combined with an address prefix to form an 1575 interface address. 1577 By default, the Interface Identifier is auto-configured 1578 according to the rules of the link type this interface is 1579 attached to. 1581 A zero length identifier may be used where appropriate. One 1582 possible example is a loopback interface." 1583 ::= { ipv6InterfaceEntry 3 } 1585 -- This object ID is reserved as it was used in earlier drafts of 1586 -- the MIB module. In theory OIDs are not assigned until the specification 1587 -- is released as an RFC, however as some companies may have shipped 1588 -- code based on earlier versiosn of the MIB it seems best to reserve 1589 -- this OID. This OID had been ipv6InterfacePhysicalAddress 1590 -- ::= { ipv6InterfaceEntry 4} 1592 ipv6InterfaceEnableStatus OBJECT-TYPE 1593 SYNTAX INTEGER { 1594 up(1), 1595 down(2) 1596 } 1597 MAX-ACCESS read-write 1598 STATUS current 1599 DESCRIPTION 1600 "The indication of whether IPv6 is enabled (up) or disabled 1601 (down) on this interface. This object does not affect the 1602 state of the interface itself, only its connection to an 1603 IPv6 stack. The IF-MIB should be used to control the state 1604 of the interface. 1606 When this object is written the entity SHOULD save the 1607 change to non-volatile storage and restore the object from 1608 non-volatile storage upon re-initialization of the system." 1609 ::= { ipv6InterfaceEntry 5 } 1611 ipv6InterfaceReachableTime OBJECT-TYPE 1612 SYNTAX Unsigned32 1613 UNITS "milliseconds" 1614 MAX-ACCESS read-only 1615 STATUS current 1616 DESCRIPTION 1617 "The time a neighbor is considered reachable after receiving 1618 a reachability confirmation." 1619 REFERENCE "RFC2461, Section 6.3.2" 1620 ::= { ipv6InterfaceEntry 6 } 1622 ipv6InterfaceRetransmitTime OBJECT-TYPE 1623 SYNTAX Unsigned32 1624 UNITS "milliseconds" 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "The time between retransmissions of Neighbor Solicitation 1629 messages to a neighbor when resolving the address or when 1630 probing the reachability of a neighbor." 1631 REFERENCE "RFC2461, Section 6.3.2" 1632 ::= { ipv6InterfaceEntry 7 } 1634 ipv6InterfaceForwarding OBJECT-TYPE 1635 SYNTAX INTEGER { 1636 forwarding(1), -- acting as a router 1637 notForwarding(2) -- NOT acting as a router 1638 } 1639 MAX-ACCESS read-write 1640 STATUS current 1641 DESCRIPTION 1642 "The indication of whether this entity is acting as an IPv6 1643 router on this interface with respect to the forwarding of 1644 datagrams received by, but not addressed to, this entity. 1645 IPv6 routers forward datagrams. IPv6 hosts do not (except 1646 those source-routed via the host). 1648 This object is constrained by ipv6IpForwarding and is 1649 ignored if ipv6IpForwarding is set to notForwarding. Those 1650 systems that do not provide per-interface control of the 1651 forwarding function should set this object to forwarding for 1652 all interfaces and allow the ipv6IpForwarding object to 1653 control the forwarding capability. 1655 When this object is written the entity SHOULD save the 1656 change to non-volatile storage and restore the object from 1657 non-volatile storage upon re-initialization of the system." 1658 ::= { ipv6InterfaceEntry 8 } 1660 -- 1661 -- Per-Interface or System-Wide IP statistics. 1662 -- 1663 -- The following two tables, ipSystemStatsTable and ipIfStatsTable 1664 -- are intended to provide the same counters at different granularities. 1665 -- The ipSystemStatsTable provides system wide counters aggregating 1666 -- the traffic counters for all interfaces for a given address type. 1667 -- The ipIfStatsTable provides the same counters but for specific 1668 -- interfaces rather than as an aggregate. 1669 -- 1670 -- Note well: If a system provides both system-wide and interface-specific 1671 -- values the system-wide value may not be equal to the sum of the 1672 -- interface-specific values across all interfaces due to e.g. dynamic 1673 -- interface creation/deletion. 1674 -- 1675 -- Note well: Both of these tables contain some items that are represented 1676 -- by two objects, representing the value in either 32 or 64 bits. For 1677 -- those objects the 32 bit value MUST be the low order 32 bits of the 1678 -- 64 bit value. Also note that the 32 bit counters must be when the 1679 -- 64 bit counters are included. 1681 ipTrafficStats OBJECT IDENTIFIER ::= { ip 31 } 1683 ipSystemStatsTable OBJECT-TYPE 1684 SYNTAX SEQUENCE OF IpSystemStatsEntry 1685 MAX-ACCESS not-accessible 1686 STATUS current 1687 DESCRIPTION 1688 "The table containing system wide, IP version specific 1689 traffic statistics. This table and the ipIfStatsTable 1690 contain similar objects whose difference is in their 1691 granularity. Where this table contains system wide traffic 1692 statistics the ipIfStatsTable contains the same statistics 1693 but counted on a per-interface basis." 1694 ::= { ipTrafficStats 1 } 1696 ipSystemStatsEntry OBJECT-TYPE 1697 SYNTAX IpSystemStatsEntry 1698 MAX-ACCESS not-accessible 1699 STATUS current 1700 DESCRIPTION 1701 "A statistics entry containing system-wide objects for a 1702 particular IP version." 1703 INDEX { ipSystemStatsIPVersion } 1704 ::= { ipSystemStatsTable 1 } 1706 IpSystemStatsEntry ::= SEQUENCE { 1707 ipSystemStatsIPVersion InetVersion, 1708 ipSystemStatsInReceives Counter32, 1709 ipSystemStatsHCInReceives Counter64, 1710 ipSystemStatsInOctets Counter32, 1711 ipSystemStatsHCInOctets Counter64, 1712 ipSystemStatsInHdrErrors Counter32, 1713 ipSystemStatsInNoRoutes Counter32, 1714 ipSystemStatsInAddrErrors Counter32, 1715 ipSystemStatsInUnknownProtos Counter32, 1716 ipSystemStatsInTruncatedPkts Counter32, 1717 ipSystemStatsInForwDatagrams Counter32, 1718 ipSystemStatsHCInForwDatagrams Counter64, 1719 ipSystemStatsReasmReqds Counter32, 1720 ipSystemStatsReasmOKs Counter32, 1721 ipSystemStatsReasmFails Counter32, 1722 ipSystemStatsInDiscards Counter32, 1723 ipSystemStatsInDelivers Counter32, 1724 ipSystemStatsHCInDelivers Counter64, 1725 ipSystemStatsOutRequests Counter32, 1726 ipSystemStatsHCOutRequests Counter64, 1727 ipSystemStatsOutNoRoutes Counter32, 1728 ipSystemStatsOutForwDatagrams Counter32, 1729 ipSystemStatsHCOutForwDatagrams Counter64, 1730 ipSystemStatsOutDiscards Counter32, 1731 ipSystemStatsOutFragReqds Counter32, 1732 ipSystemStatsOutFragOKs Counter32, 1733 ipSystemStatsOutFragFails Counter32, 1734 ipSystemStatsOutFragCreates Counter32, 1735 ipSystemStatsOutTransmits Counter32, 1736 ipSystemStatsHCOutTransmits Counter64, 1737 ipSystemStatsOutOctets Counter32, 1738 ipSystemStatsHCOutOctets Counter64, 1739 ipSystemStatsInMcastPkts Counter32, 1740 ipSystemStatsHCInMcastPkts Counter64, 1741 ipSystemStatsInMcastOctets Counter32, 1742 ipSystemStatsHCInMcastOctets Counter64, 1743 ipSystemStatsOutMcastPkts Counter32, 1744 ipSystemStatsHCOutMcastPkts Counter64, 1745 ipSystemStatsOutMcastOctets Counter32, 1746 ipSystemStatsHCOutMcastOctets Counter64, 1747 ipSystemStatsInBcastPkts Counter32, 1748 ipSystemStatsHCInBcastPkts Counter64, 1749 ipSystemStatsOutBcastPkts Counter32, 1750 ipSystemStatsHCOutBcastPkts Counter64, 1751 ipSystemStatsDiscontinuityTime TimeStamp, 1752 ipSystemStatsRefreshRate Unsigned32 1753 } 1755 ipSystemStatsIPVersion OBJECT-TYPE 1756 SYNTAX InetVersion 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "The IP version of this row." 1761 ::= { ipSystemStatsEntry 1 } 1763 -- This object ID is reserved to allow the IDs for this table's objects 1764 -- to align with the objects in the ipIfStatsTable. 1765 -- ::= { ipSystemStatsEntry 2 } 1767 ipSystemStatsInReceives OBJECT-TYPE 1768 SYNTAX Counter32 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "The total number of input IP datagrams received, including 1773 those received in error. 1775 Discontinuities in the value of this counter can occur at 1776 re-initialization of the management system, and at other 1777 times as indicated by the value of 1778 ipSystemStatsDiscontinuityTime." 1779 ::= { ipSystemStatsEntry 3 } 1781 ipSystemStatsHCInReceives OBJECT-TYPE 1782 SYNTAX Counter64 1783 MAX-ACCESS read-only 1784 STATUS current 1785 DESCRIPTION 1786 "The total number of input IP datagrams received, including 1787 those received in error. This object counts the same 1788 datagrams as ipSystemStatsInReceives but allows for larger 1789 values. 1791 Discontinuities in the value of this counter can occur at 1792 re-initialization of the management system, and at other 1793 times as indicated by the value of 1794 ipSystemStatsDiscontinuityTime." 1795 ::= { ipSystemStatsEntry 4 } 1797 ipSystemStatsInOctets OBJECT-TYPE 1798 SYNTAX Counter32 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 "The total number of octets received in input IP datagrams, 1803 including those received in error. Octets from datagrams 1804 counted in ipSystemStatsInReceives MUST be counted here. 1806 Discontinuities in the value of this counter can occur at 1807 re-initialization of the management system, and at other 1808 times as indicated by the value of 1809 ipSystemStatsDiscontinuityTime." 1810 ::= { ipSystemStatsEntry 5 } 1812 ipSystemStatsHCInOctets OBJECT-TYPE 1813 SYNTAX Counter64 1814 MAX-ACCESS read-only 1815 STATUS current 1816 DESCRIPTION 1817 "The total number of octets received in input IP datagrams, 1818 including those received in error. This object counts the 1819 same octets as ipSystemStatsInOctets but allows for larger 1820 values. 1822 Discontinuities in the value of this counter can occur at 1823 re-initialization of the management system, and at other 1824 times as indicated by the value of 1825 ipSystemStatsDiscontinuityTime." 1826 ::= { ipSystemStatsEntry 6 } 1828 ipSystemStatsInHdrErrors OBJECT-TYPE 1829 SYNTAX Counter32 1830 MAX-ACCESS read-only 1831 STATUS current 1832 DESCRIPTION 1833 "The number of input IP datagrams discarded due to errors in 1834 their IP headers, including version number mismatch, other 1835 format errors, hop count exceeded, errors discovered in 1836 processing their IP options, etc. 1838 Discontinuities in the value of this counter can occur at 1839 re-initialization of the management system, and at other 1840 times as indicated by the value of 1841 ipSystemStatsDiscontinuityTime." 1842 ::= { ipSystemStatsEntry 7 } 1844 ipSystemStatsInNoRoutes OBJECT-TYPE 1845 SYNTAX Counter32 1846 MAX-ACCESS read-only 1847 STATUS current 1848 DESCRIPTION 1849 "The number of input IP datagrams discarded because no route 1850 could be found to transmit them to their destination. 1852 Discontinuities in the value of this counter can occur at 1853 re-initialization of the management system, and at other 1854 times as indicated by the value of 1855 ipSystemStatsDiscontinuityTime." 1856 ::= { ipSystemStatsEntry 8 } 1858 ipSystemStatsInAddrErrors OBJECT-TYPE 1859 SYNTAX Counter32 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "The number of input IP datagrams discarded because the IP 1864 address in their IP header's destination field was not a 1865 valid address to be received at this entity. This count 1866 includes invalid addresses (e.g., ::0) and unsupported 1867 addresses (e.g., addresses with unallocated prefixes). For 1868 entities which are not IP routers and therefore do not 1869 forward datagrams, this counter includes datagrams discarded 1870 because the destination address was not a local address. 1872 Discontinuities in the value of this counter can occur at 1873 re-initialization of the management system, and at other 1874 times as indicated by the value of 1875 ipSystemStatsDiscontinuityTime." 1876 ::= { ipSystemStatsEntry 9 } 1878 ipSystemStatsInUnknownProtos OBJECT-TYPE 1879 SYNTAX Counter32 1880 MAX-ACCESS read-only 1881 STATUS current 1882 DESCRIPTION 1883 "The number of locally-addressed IP datagrams received 1884 successfully but discarded because of an unknown or 1885 unsupported protocol. 1887 When tracking interface statistics the counter of the 1888 interface to which these datagrams were addressed is 1889 incremented. This interface might not be the same as the 1890 input interface for some of the datagrams. 1892 Discontinuities in the value of this counter can occur at 1893 re-initialization of the management system, and at other 1894 times as indicated by the value of 1895 ipSystemStatsDiscontinuityTime." 1896 ::= { ipSystemStatsEntry 10 } 1898 ipSystemStatsInTruncatedPkts OBJECT-TYPE 1899 SYNTAX Counter32 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "The number of input IP datagrams discarded because the 1904 datagram frame didn't carry enough data. 1906 Discontinuities in the value of this counter can occur at 1907 re-initialization of the management system, and at other 1908 times as indicated by the value of 1909 ipSystemStatsDiscontinuityTime." 1910 ::= { ipSystemStatsEntry 11 } 1912 ipSystemStatsInForwDatagrams OBJECT-TYPE 1913 SYNTAX Counter32 1914 MAX-ACCESS read-only 1915 STATUS current 1916 DESCRIPTION 1917 "The number of input datagrams for which this entity was not 1918 their final IP destination and for which this entity 1919 attempted to find a route to forward them to that final 1920 destination. In entities which do not act as IP routers, 1921 this counter will include only those datagrams which were 1922 Source-Routed via this entity, and the Source-Route 1923 processing was successful. 1925 When tracking interface statistics the counter of the 1926 incoming interface is incremented for each datagram. 1928 Discontinuities in the value of this counter can occur at 1929 re-initialization of the management system, and at other 1930 times as indicated by the value of 1931 ipSystemStatsDiscontinuityTime." 1932 ::= { ipSystemStatsEntry 12 } 1934 ipSystemStatsHCInForwDatagrams OBJECT-TYPE 1935 SYNTAX Counter64 1936 MAX-ACCESS read-only 1937 STATUS current 1938 DESCRIPTION 1939 "The number of input datagrams for which this entity was not 1940 their final IP destination and for which this entity 1941 attempted to find a route to forward them to that final 1942 destination. This object counts the same packets as 1943 ipSystemStatsInForwDatagrams but allows for larger values. 1945 Discontinuities in the value of this counter can occur at 1946 re-initialization of the management system, and at other 1947 times as indicated by the value of 1948 ipSystemStatsDiscontinuityTime." 1949 ::= { ipSystemStatsEntry 13 } 1951 ipSystemStatsReasmReqds OBJECT-TYPE 1952 SYNTAX Counter32 1953 MAX-ACCESS read-only 1954 STATUS current 1955 DESCRIPTION 1956 "The number of IP fragments received which needed to be 1957 reassembled at this interface. 1959 When tracking interface statistics the counter of the 1960 interface to which these fragments were addressed is 1961 incremented. This interface might not be the same as the 1962 input interface for some of the fragments. 1964 Discontinuities in the value of this counter can occur at 1965 re-initialization of the management system, and at other 1966 times as indicated by the value of 1967 ipSystemStatsDiscontinuityTime." 1968 ::= { ipSystemStatsEntry 14 } 1970 ipSystemStatsReasmOKs OBJECT-TYPE 1971 SYNTAX Counter32 1972 MAX-ACCESS read-only 1973 STATUS current 1974 DESCRIPTION 1975 "The number of IP datagrams successfully reassembled. 1977 When tracking interface statistics the counter of the 1978 interface to which these datagrams were addressed is 1979 incremented. This interface might not be the same as the 1980 input interface for some of the datagrams. 1982 Discontinuities in the value of this counter can occur at 1983 re-initialization of the management system, and at other 1984 times as indicated by the value of 1985 ipSystemStatsDiscontinuityTime." 1986 ::= { ipSystemStatsEntry 15 } 1988 ipSystemStatsReasmFails OBJECT-TYPE 1989 SYNTAX Counter32 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 "The number of failures detected by the IP re-assembly 1994 algorithm (for whatever reason: timed out, errors, etc.). 1995 Note that this is not necessarily a count of discarded IP 1996 fragments since some algorithms (notably the algorithm in 1997 RFC 815) can lose track of the number of fragments by 1998 combining them as they are received. 2000 When tracking interface statistics the counter of the 2001 interface to which these fragments were addressed is 2002 incremented. This interface might not be the same as the 2003 input interface for some of the fragments. 2005 Discontinuities in the value of this counter can occur at 2006 re-initialization of the management system, and at other 2007 times as indicated by the value of 2008 ipSystemStatsDiscontinuityTime." 2009 ::= { ipSystemStatsEntry 16 } 2011 ipSystemStatsInDiscards OBJECT-TYPE 2012 SYNTAX Counter32 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "The number of input IP datagrams for which no problems were 2017 encountered to prevent their continued processing, but which 2018 were discarded (e.g., for lack of buffer space). Note that 2019 this counter does not include any datagrams discarded while 2020 awaiting re-assembly. 2022 Discontinuities in the value of this counter can occur at 2023 re-initialization of the management system, and at other 2024 times as indicated by the value of 2025 ipSystemStatsDiscontinuityTime." 2026 ::= { ipSystemStatsEntry 17 } 2028 ipSystemStatsInDelivers OBJECT-TYPE 2029 SYNTAX Counter32 2030 MAX-ACCESS read-only 2031 STATUS current 2032 DESCRIPTION 2033 "The total number of datagrams successfully delivered to IP 2034 user-protocols (including ICMP). 2036 When tracking interface statistics the counter of the 2037 interface to which these datagrams were addressed is 2038 incremented. This interface might not be the same as the 2039 input interface for some of the datagrams. 2041 Discontinuities in the value of this counter can occur at 2042 re-initialization of the management system, and at other 2043 times as indicated by the value of 2044 ipSystemStatsDiscontinuityTime." 2045 ::= { ipSystemStatsEntry 18 } 2047 ipSystemStatsHCInDelivers OBJECT-TYPE 2048 SYNTAX Counter64 2049 MAX-ACCESS read-only 2050 STATUS current 2051 DESCRIPTION 2052 "The total number of datagrams successfully delivered to IP 2053 user-protocols (including ICMP). This object counts the 2054 same packets as ipSystemStatsInDelivers but allows for 2055 larger values. 2057 Discontinuities in the value of this counter can occur at 2058 re-initialization of the management system, and at other 2059 times as indicated by the value of 2060 ipSystemStatsDiscontinuityTime." 2061 ::= { ipSystemStatsEntry 19 } 2063 ipSystemStatsOutRequests OBJECT-TYPE 2064 SYNTAX Counter32 2065 MAX-ACCESS read-only 2066 STATUS current 2067 DESCRIPTION 2068 "The total number of IP datagrams which local IP user- 2069 protocols (including ICMP) supplied to IP in requests for 2070 transmission. Note that this counter does not include any 2071 datagrams counted in ipSystemStatsOutForwDatagrams. 2073 Discontinuities in the value of this counter can occur at 2074 re-initialization of the management system, and at other 2075 times as indicated by the value of 2076 ipSystemStatsDiscontinuityTime." 2077 ::= { ipSystemStatsEntry 20 } 2079 ipSystemStatsHCOutRequests OBJECT-TYPE 2080 SYNTAX Counter64 2081 MAX-ACCESS read-only 2082 STATUS current 2083 DESCRIPTION 2084 "The total number of IP datagrams which local IP user- 2085 protocols (including ICMP) supplied to IP in requests for 2086 transmission. This object counts the same packets as 2087 ipSystemStatsHCOutRequests but allows for larger values. 2089 Discontinuities in the value of this counter can occur at 2090 re-initialization of the management system, and at other 2091 times as indicated by the value of 2092 ipSystemStatsDiscontinuityTime." 2093 ::= { ipSystemStatsEntry 21 } 2095 ipSystemStatsOutNoRoutes OBJECT-TYPE 2096 SYNTAX Counter32 2097 MAX-ACCESS read-only 2098 STATUS current 2099 DESCRIPTION 2100 "The number of locally generated IP datagrams discarded 2101 because no route could be found to transmit them to their 2102 destination. 2104 Discontinuities in the value of this counter can occur at 2105 re-initialization of the management system, and at other 2106 times as indicated by the value of 2107 ipSystemStatsDiscontinuityTime." 2108 ::= { ipSystemStatsEntry 22 } 2110 ipSystemStatsOutForwDatagrams OBJECT-TYPE 2111 SYNTAX Counter32 2112 MAX-ACCESS read-only 2113 STATUS current 2114 DESCRIPTION 2115 "The number of datagrams for which this entity was not their 2116 final IP destination and for which it was successful in 2117 finding a path to their final destination. In entities 2118 which do not act as IP routers, this counter will include 2119 only those datagrams which were Source-Routed via this 2120 entity, and the Source-Route processing was successful. 2122 When tracking interface statistics the counter of the 2123 outgoing interface is incremented for a successfully 2124 forwarded datagram. 2126 Discontinuities in the value of this counter can occur at 2127 re-initialization of the management system, and at other 2128 times as indicated by the value of 2129 ipSystemStatsDiscontinuityTime." 2130 ::= { ipSystemStatsEntry 23 } 2132 ipSystemStatsHCOutForwDatagrams OBJECT-TYPE 2133 SYNTAX Counter64 2134 MAX-ACCESS read-only 2135 STATUS current 2136 DESCRIPTION 2137 "The number of datagrams for which this entity was not their 2138 final IP destination and for which it was successful in 2139 finding a path to their final destination. This object 2140 counts the same packets as ipSystemStatsOutForwDatagrams but 2141 allows for larger values. 2143 Discontinuities in the value of this counter can occur at 2144 re-initialization of the management system, and at other 2145 times as indicated by the value of 2146 ipSystemStatsDiscontinuityTime." 2147 ::= { ipSystemStatsEntry 24 } 2149 ipSystemStatsOutDiscards OBJECT-TYPE 2150 SYNTAX Counter32 2151 MAX-ACCESS read-only 2152 STATUS current 2153 DESCRIPTION 2154 "The number of output IP datagrams for which no problem was 2155 encountered to prevent their transmission to their 2156 destination, but which were discarded (e.g., for lack of 2157 buffer space). Note that this counter would include 2158 datagrams counted in ipSystemStatsOutForwDatagrams if any 2159 such datagrams met this (discretionary) discard criterion. 2161 Discontinuities in the value of this counter can occur at 2162 re-initialization of the management system, and at other 2163 times as indicated by the value of 2164 ipSystemStatsDiscontinuityTime." 2165 ::= { ipSystemStatsEntry 25 } 2167 ipSystemStatsOutFragReqds OBJECT-TYPE 2168 SYNTAX Counter32 2169 MAX-ACCESS read-only 2170 STATUS current 2171 DESCRIPTION 2172 "The number of IP datagrams that would require fragmentation 2173 in order to be transmitted. 2175 When tracking interface statistics the counter of the 2176 outgoing interface is incremented for a successfully 2177 fragmented datagram. 2179 Discontinuities in the value of this counter can occur at 2180 re-initialization of the management system, and at other 2181 times as indicated by the value of 2182 ipSystemStatsDiscontinuityTime." 2183 ::= { ipSystemStatsEntry 26 } 2185 ipSystemStatsOutFragOKs OBJECT-TYPE 2186 SYNTAX Counter32 2187 MAX-ACCESS read-only 2188 STATUS current 2189 DESCRIPTION 2190 "The number of IP datagrams that have been successfully 2191 fragmented. 2193 When tracking interface statistics the counter of the 2194 outgoing interface is incremented for a successfully 2195 fragmented datagram. 2197 Discontinuities in the value of this counter can occur at 2198 re-initialization of the management system, and at other 2199 times as indicated by the value of 2200 ipSystemStatsDiscontinuityTime." 2201 ::= { ipSystemStatsEntry 27 } 2203 ipSystemStatsOutFragFails OBJECT-TYPE 2204 SYNTAX Counter32 2205 MAX-ACCESS read-only 2206 STATUS current 2207 DESCRIPTION 2208 "The number of IP datagrams that have been discarded because 2209 they needed to be fragmented but could not be. This 2210 includes IPv4 packets that have the DF bit set and IPv6 2211 packets that are being forwarded and exceed the outgoing 2212 link MTU. 2214 When tracking interface statistics the counter of the 2215 outgoing interface is incremented for an unsuccessfully 2216 fragmented datagram. 2218 Discontinuities in the value of this counter can occur at 2219 re-initialization of the management system, and at other 2220 times as indicated by the value of 2221 ipSystemStatsDiscontinuityTime." 2222 ::= { ipSystemStatsEntry 28 } 2224 ipSystemStatsOutFragCreates OBJECT-TYPE 2225 SYNTAX Counter32 2226 MAX-ACCESS read-only 2227 STATUS current 2228 DESCRIPTION 2229 "The number of output datagram fragments that have been 2230 generated as a result of IP fragmentation. 2232 When tracking interface statistics the counter of the 2233 outgoing interface is incremented for a successfully 2234 fragmented datagram. 2236 Discontinuities in the value of this counter can occur at 2237 re-initialization of the management system, and at other 2238 times as indicated by the value of 2239 ipSystemStatsDiscontinuityTime." 2240 ::= { ipSystemStatsEntry 29 } 2242 ipSystemStatsOutTransmits OBJECT-TYPE 2243 SYNTAX Counter32 2244 MAX-ACCESS read-only 2245 STATUS current 2246 DESCRIPTION 2247 "The total number of IP datagrams that this entity supplied 2248 to the lower layers for transmission. This includes 2249 datagrams generated local and those forwarded by this 2250 entity. 2252 Discontinuities in the value of this counter can occur at 2253 re-initialization of the management system, and at other 2254 times as indicated by the value of 2255 ipSystemStatsDiscontinuityTime." 2256 ::= { ipSystemStatsEntry 30 } 2258 ipSystemStatsHCOutTransmits OBJECT-TYPE 2259 SYNTAX Counter64 2260 MAX-ACCESS read-only 2261 STATUS current 2262 DESCRIPTION 2263 "The total number of IP datagrams that this entity supplied 2264 to the lower layers for transmission. This object counts 2265 the same datagrams as ipSystemStatsOutTransmits but allows 2266 for larger values. 2268 Discontinuities in the value of this counter can occur at 2269 re-initialization of the management system, and at other 2270 times as indicated by the value of 2271 ipSystemStatsDiscontinuityTime." 2273 ::= { ipSystemStatsEntry 31 } 2275 ipSystemStatsOutOctets OBJECT-TYPE 2276 SYNTAX Counter32 2277 MAX-ACCESS read-only 2278 STATUS current 2279 DESCRIPTION 2280 "The total number of octets in IP datagrams delivered to the 2281 lower layers for transmission. Octets from datagrams 2282 counted in ipSystemStatsOutTransmits MUST be counted here. 2284 Discontinuities in the value of this counter can occur at 2285 re-initialization of the management system, and at other 2286 times as indicated by the value of 2287 ipSystemStatsDiscontinuityTime." 2288 ::= { ipSystemStatsEntry 32 } 2290 ipSystemStatsHCOutOctets OBJECT-TYPE 2291 SYNTAX Counter64 2292 MAX-ACCESS read-only 2293 STATUS current 2294 DESCRIPTION 2295 "The total number of octets in IP datagrams delivered to the 2296 lower layers for transmission. This objects counts the same 2297 octets as ipSystemStatsOutOctets but allows for larger 2298 values. 2300 Discontinuities in the value of this counter can occur at 2301 re-initialization of the management system, and at other 2302 times as indicated by the value of 2303 ipSystemStatsDiscontinuityTime." 2304 ::= { ipSystemStatsEntry 33 } 2306 ipSystemStatsInMcastPkts OBJECT-TYPE 2307 SYNTAX Counter32 2308 MAX-ACCESS read-only 2309 STATUS current 2310 DESCRIPTION 2311 "The number of IP multicast datagrams received. 2313 Discontinuities in the value of this counter can occur at 2314 re-initialization of the management system, and at other 2315 times as indicated by the value of 2316 ipSystemStatsDiscontinuityTime." 2317 ::= { ipSystemStatsEntry 34 } 2319 ipSystemStatsHCInMcastPkts OBJECT-TYPE 2320 SYNTAX Counter64 2321 MAX-ACCESS read-only 2322 STATUS current 2323 DESCRIPTION 2324 "The number of IP multicast datagrams received. This object 2325 counts the same datagrams as ipSystemStatsInMcastPkts but 2326 allows for larger values. 2328 Discontinuities in the value of this counter can occur at 2329 re-initialization of the management system, and at other 2330 times as indicated by the value of 2331 ipSystemStatsDiscontinuityTime." 2332 ::= { ipSystemStatsEntry 35 } 2334 ipSystemStatsInMcastOctets OBJECT-TYPE 2335 SYNTAX Counter32 2336 MAX-ACCESS read-only 2337 STATUS current 2338 DESCRIPTION 2339 "The total number of octets received in IP multicast 2340 datagrams. Octets from datagrams counted in 2341 ipSystemStatsOutMcastPkts MUST be counted here. 2343 Discontinuities in the value of this counter can occur at 2344 re-initialization of the management system, and at other 2345 times as indicated by the value of 2346 ipSystemStatsDiscontinuityTime." 2347 ::= { ipSystemStatsEntry 36 } 2349 ipSystemStatsHCInMcastOctets OBJECT-TYPE 2350 SYNTAX Counter64 2351 MAX-ACCESS read-only 2352 STATUS current 2353 DESCRIPTION 2354 "The total number of octets received in IP multicast 2355 datagrams. This object counts the same octets as 2356 ipSystemStatsInMcastOctets but allows for larger values. 2358 Discontinuities in the value of this counter can occur at 2359 re-initialization of the management system, and at other 2360 times as indicated by the value of 2361 ipSystemStatsDiscontinuityTime." 2362 ::= { ipSystemStatsEntry 37 } 2364 ipSystemStatsOutMcastPkts OBJECT-TYPE 2365 SYNTAX Counter32 2366 MAX-ACCESS read-only 2367 STATUS current 2368 DESCRIPTION 2369 "The number of IP multicast datagrams transmitted. 2371 Discontinuities in the value of this counter can occur at 2372 re-initialization of the management system, and at other 2373 times as indicated by the value of 2374 ipSystemStatsDiscontinuityTime." 2375 ::= { ipSystemStatsEntry 38 } 2377 ipSystemStatsHCOutMcastPkts OBJECT-TYPE 2378 SYNTAX Counter64 2379 MAX-ACCESS read-only 2380 STATUS current 2381 DESCRIPTION 2382 "The number of IP multicast datagrams transmitted. This 2383 object counts the same datagrams as 2384 ipSystemStatsOutMcastPkts but allows for larger values. 2386 Discontinuities in the value of this counter can occur at 2387 re-initialization of the management system, and at other 2388 times as indicated by the value of 2389 ipSystemStatsDiscontinuityTime." 2390 ::= { ipSystemStatsEntry 39 } 2392 ipSystemStatsOutMcastOctets OBJECT-TYPE 2393 SYNTAX Counter32 2394 MAX-ACCESS read-only 2395 STATUS current 2396 DESCRIPTION 2397 "The total number of octets transmitted in IP multicast 2398 datagrams. Octets from datagrams counted in 2399 ipSystemStatsInMcastPkts MUST be counted here. 2401 Discontinuities in the value of this counter can occur at 2402 re-initialization of the management system, and at other 2403 times as indicated by the value of 2404 ipSystemStatsDiscontinuityTime." 2405 ::= { ipSystemStatsEntry 40 } 2407 ipSystemStatsHCOutMcastOctets OBJECT-TYPE 2408 SYNTAX Counter64 2409 MAX-ACCESS read-only 2410 STATUS current 2411 DESCRIPTION 2412 "The total number of octets transmitted in IP multicast 2413 datagrams. This object counts the same octets as 2414 ipSystemStatsOutMcastOctets but allows for larger values. 2416 Discontinuities in the value of this counter can occur at 2417 re-initialization of the management system, and at other 2418 times as indicated by the value of 2419 ipSystemStatsDiscontinuityTime." 2420 ::= { ipSystemStatsEntry 41 } 2422 ipSystemStatsInBcastPkts OBJECT-TYPE 2423 SYNTAX Counter32 2424 MAX-ACCESS read-only 2425 STATUS current 2426 DESCRIPTION 2427 "The number of IP broadcast datagrams received. 2429 Discontinuities in the value of this counter can occur at 2430 re-initialization of the management system, and at other 2431 times as indicated by the value of 2432 ipSystemStatsDiscontinuityTime." 2433 ::= { ipSystemStatsEntry 42 } 2435 ipSystemStatsHCInBcastPkts OBJECT-TYPE 2436 SYNTAX Counter64 2437 MAX-ACCESS read-only 2438 STATUS current 2439 DESCRIPTION 2440 "The number of IP broadcast datagrams received. This object 2441 counts the same datagrams as ipSystemStatsInBcastPkts but 2442 allows for larger values. 2444 Discontinuities in the value of this counter can occur at 2445 re-initialization of the management system, and at other 2446 times as indicated by the value of 2447 ipSystemStatsDiscontinuityTime." 2448 ::= { ipSystemStatsEntry 43 } 2450 ipSystemStatsOutBcastPkts OBJECT-TYPE 2451 SYNTAX Counter32 2452 MAX-ACCESS read-only 2453 STATUS current 2454 DESCRIPTION 2455 "The number of IP broadcast datagrams transmitted. 2457 Discontinuities in the value of this counter can occur at 2458 re-initialization of the management system, and at other 2459 times as indicated by the value of 2460 ipSystemStatsDiscontinuityTime." 2461 ::= { ipSystemStatsEntry 44 } 2463 ipSystemStatsHCOutBcastPkts OBJECT-TYPE 2464 SYNTAX Counter64 2465 MAX-ACCESS read-only 2466 STATUS current 2467 DESCRIPTION 2468 "The number of IP broadcast datagrams transmitted. This 2469 object counts the same datagrams as 2470 ipSystemStatsOutBcastPkts but allows for larger values. 2472 Discontinuities in the value of this counter can occur at 2473 re-initialization of the management system, and at other 2474 times as indicated by the value of 2475 ipSystemStatsDiscontinuityTime." 2476 ::= { ipSystemStatsEntry 45 } 2478 ipSystemStatsDiscontinuityTime OBJECT-TYPE 2479 SYNTAX TimeStamp 2480 MAX-ACCESS read-only 2481 STATUS current 2482 DESCRIPTION 2483 "The value of sysUpTime on the most recent occasion at which 2484 any one or more of this entry's counters suffered a 2485 discontinuity. 2487 If no such discontinuities have occurred since the last re- 2488 initialization of the local management subsystem, then this 2489 object contains a zero value." 2490 ::= { ipSystemStatsEntry 46 } 2492 ipSystemStatsRefreshRate OBJECT-TYPE 2493 SYNTAX Unsigned32 2494 UNITS "milli-seconds" 2495 MAX-ACCESS read-only 2496 STATUS current 2497 DESCRIPTION 2498 "The minimum reasonable polling interval for this entry. 2499 This object provides an indication of the minimum amount of 2500 time required to update the counters in this entry." 2501 ::= { ipSystemStatsEntry 47 } 2503 ipIfStatsTableLastChange OBJECT-TYPE 2504 SYNTAX TimeStamp 2505 MAX-ACCESS read-only 2506 STATUS current 2507 DESCRIPTION 2508 "The value of sysUpTime on the most recent occasion at which 2509 a row in the ipIfStatsTable was added or deleted. 2511 If new objects are added to the ipIfStatsTable that require 2512 the ipIfStatsTableLastChange to be updated when they are 2513 modified they must specify that requirement in their 2514 description clause." 2515 ::= { ipTrafficStats 2 } 2517 ipIfStatsTable OBJECT-TYPE 2518 SYNTAX SEQUENCE OF IpIfStatsEntry 2519 MAX-ACCESS not-accessible 2520 STATUS current 2521 DESCRIPTION 2522 "The table containing per-interface traffic statistics. This 2523 table and the ipSystemStatsTable contain similar objects 2524 whose difference is in their granularity. Where this table 2525 contains per-interface statistics the ipSystemStatsTable 2526 contains the same statistics but counted on a system wide 2527 basis." 2528 ::= { ipTrafficStats 3 } 2530 ipIfStatsEntry OBJECT-TYPE 2531 SYNTAX IpIfStatsEntry 2532 MAX-ACCESS not-accessible 2533 STATUS current 2534 DESCRIPTION 2535 "An interface statistics entry containing objects for a 2536 particular interface and version of IP." 2537 INDEX { ipIfStatsIPVersion, ipIfStatsIfIndex } 2538 ::= { ipIfStatsTable 1 } 2540 IpIfStatsEntry ::= SEQUENCE { 2541 ipIfStatsIPVersion InetVersion, 2542 ipIfStatsIfIndex InterfaceIndex, 2543 ipIfStatsInReceives Counter32, 2544 ipIfStatsHCInReceives Counter64, 2545 ipIfStatsInOctets Counter32, 2546 ipIfStatsHCInOctets Counter64, 2547 ipIfStatsInHdrErrors Counter32, 2548 ipIfStatsInNoRoutes Counter32, 2549 ipIfStatsInAddrErrors Counter32, 2550 ipIfStatsInUnknownProtos Counter32, 2551 ipIfStatsInTruncatedPkts Counter32, 2552 ipIfStatsInForwDatagrams Counter32, 2553 ipIfStatsHCInForwDatagrams Counter64, 2554 ipIfStatsReasmReqds Counter32, 2555 ipIfStatsReasmOKs Counter32, 2556 ipIfStatsReasmFails Counter32, 2557 ipIfStatsInDiscards Counter32, 2558 ipIfStatsInDelivers Counter32, 2559 ipIfStatsHCInDelivers Counter64, 2560 ipIfStatsOutRequests Counter32, 2561 ipIfStatsHCOutRequests Counter64, 2562 ipIfStatsOutForwDatagrams Counter32, 2563 ipIfStatsHCOutForwDatagrams Counter64, 2564 ipIfStatsOutDiscards Counter32, 2565 ipIfStatsOutFragReqds Counter32, 2566 ipIfStatsOutFragOKs Counter32, 2567 ipIfStatsOutFragFails Counter32, 2568 ipIfStatsOutFragCreates Counter32, 2569 ipIfStatsOutTransmits Counter32, 2570 ipIfStatsHCOutTransmits Counter64, 2571 ipIfStatsOutOctets Counter32, 2572 ipIfStatsHCOutOctets Counter64, 2573 ipIfStatsInMcastPkts Counter32, 2574 ipIfStatsHCInMcastPkts Counter64, 2575 ipIfStatsInMcastOctets Counter32, 2576 ipIfStatsHCInMcastOctets Counter64, 2577 ipIfStatsOutMcastPkts Counter32, 2578 ipIfStatsHCOutMcastPkts Counter64, 2579 ipIfStatsOutMcastOctets Counter32, 2580 ipIfStatsHCOutMcastOctets Counter64, 2581 ipIfStatsInBcastPkts Counter32, 2582 ipIfStatsHCInBcastPkts Counter64, 2583 ipIfStatsOutBcastPkts Counter32, 2584 ipIfStatsHCOutBcastPkts Counter64, 2585 ipIfStatsDiscontinuityTime TimeStamp, 2586 ipIfStatsRefreshRate Unsigned32 2587 } 2589 ipIfStatsIPVersion OBJECT-TYPE 2590 SYNTAX InetVersion 2591 MAX-ACCESS not-accessible 2592 STATUS current 2593 DESCRIPTION 2594 "The IP version of this row." 2595 ::= { ipIfStatsEntry 1 } 2597 ipIfStatsIfIndex OBJECT-TYPE 2598 SYNTAX InterfaceIndex 2599 MAX-ACCESS not-accessible 2600 STATUS current 2601 DESCRIPTION 2602 "The index value which uniquely identifies the interface to 2603 which this entry is applicable. The interface identified by 2604 a particular value of this index is the same interface as 2605 identified by the same value of the IF-MIB's ifIndex." 2606 ::= { ipIfStatsEntry 2 } 2608 ipIfStatsInReceives OBJECT-TYPE 2609 SYNTAX Counter32 2610 MAX-ACCESS read-only 2611 STATUS current 2612 DESCRIPTION 2613 "The total number of input IP datagrams received, including 2614 those received in error. 2616 Discontinuities in the value of this counter can occur at 2617 re-initialization of the management system, and at other 2618 times as indicated by the value of 2619 ipIfStatsDiscontinuityTime." 2620 ::= { ipIfStatsEntry 3 } 2622 ipIfStatsHCInReceives OBJECT-TYPE 2623 SYNTAX Counter64 2624 MAX-ACCESS read-only 2625 STATUS current 2626 DESCRIPTION 2627 "The total number of input IP datagrams received, including 2628 those received in error. This object counts the same 2629 datagrams as ipIfStatsInReceives but allows for larger 2630 values. 2632 Discontinuities in the value of this counter can occur at 2633 re-initialization of the management system, and at other 2634 times as indicated by the value of 2635 ipIfStatsDiscontinuityTime." 2636 ::= { ipIfStatsEntry 4 } 2638 ipIfStatsInOctets OBJECT-TYPE 2639 SYNTAX Counter32 2640 MAX-ACCESS read-only 2641 STATUS current 2642 DESCRIPTION 2643 "The total number of octets received in input IP datagrams, 2644 including those received in error. Octets from datagrams 2645 counted in ipIfStatsInReceives MUST be counted here. 2647 Discontinuities in the value of this counter can occur at 2648 re-initialization of the management system, and at other 2649 times as indicated by the value of 2650 ipIfStatsDiscontinuityTime." 2651 ::= { ipIfStatsEntry 5 } 2653 ipIfStatsHCInOctets OBJECT-TYPE 2654 SYNTAX Counter64 2655 MAX-ACCESS read-only 2656 STATUS current 2657 DESCRIPTION 2658 "The total number of octets received in input IP datagrams, 2659 including those received in error. This object counts the 2660 same octets as ipIfStatsInOctets but allows for larger 2661 values. 2663 Discontinuities in the value of this counter can occur at 2664 re-initialization of the management system, and at other 2665 times as indicated by the value of 2666 ipIfStatsDiscontinuityTime." 2667 ::= { ipIfStatsEntry 6 } 2669 ipIfStatsInHdrErrors OBJECT-TYPE 2670 SYNTAX Counter32 2671 MAX-ACCESS read-only 2672 STATUS current 2673 DESCRIPTION 2674 "The number of input IP datagrams discarded due to errors in 2675 their IP headers, including version number mismatch, other 2676 format errors, hop count exceeded, errors discovered in 2677 processing their IP options, etc. 2679 Discontinuities in the value of this counter can occur at 2680 re-initialization of the management system, and at other 2681 times as indicated by the value of 2682 ipIfStatsDiscontinuityTime." 2683 ::= { ipIfStatsEntry 7 } 2685 ipIfStatsInNoRoutes OBJECT-TYPE 2686 SYNTAX Counter32 2687 MAX-ACCESS read-only 2688 STATUS current 2689 DESCRIPTION 2690 "The number of input IP datagrams discarded because no route 2691 could be found to transmit them to their destination. 2693 Discontinuities in the value of this counter can occur at 2694 re-initialization of the management system, and at other 2695 times as indicated by the value of 2696 ipIfStatsDiscontinuityTime." 2697 ::= { ipIfStatsEntry 8 } 2699 ipIfStatsInAddrErrors OBJECT-TYPE 2700 SYNTAX Counter32 2701 MAX-ACCESS read-only 2702 STATUS current 2703 DESCRIPTION 2704 "The number of input IP datagrams discarded because the IP 2705 address in their IP header's destination field was not a 2706 valid address to be received at this entity. This count 2707 includes invalid addresses (e.g., ::0). For entities which 2708 are not IP routers and therefore do not forward datagrams, 2709 this counter includes datagrams discarded because the 2710 destination address was not a local address. 2712 Discontinuities in the value of this counter can occur at 2713 re-initialization of the management system, and at other 2714 times as indicated by the value of 2715 ipIfStatsDiscontinuityTime." 2716 ::= { ipIfStatsEntry 9 } 2718 ipIfStatsInUnknownProtos OBJECT-TYPE 2719 SYNTAX Counter32 2720 MAX-ACCESS read-only 2721 STATUS current 2722 DESCRIPTION 2723 "The number of locally-addressed IP datagrams received 2724 successfully but discarded because of an unknown or 2725 unsupported protocol. 2727 When tracking interface statistics the counter of the 2728 interface to which these datagrams were addressed is 2729 incremented. This interface might not be the same as the 2730 input interface for some of the datagrams. 2732 Discontinuities in the value of this counter can occur at 2733 re-initialization of the management system, and at other 2734 times as indicated by the value of 2735 ipIfStatsDiscontinuityTime." 2736 ::= { ipIfStatsEntry 10 } 2738 ipIfStatsInTruncatedPkts OBJECT-TYPE 2739 SYNTAX Counter32 2740 MAX-ACCESS read-only 2741 STATUS current 2742 DESCRIPTION 2743 "The number of input IP datagrams discarded because the 2744 datagram frame didn't carry enough data. 2746 Discontinuities in the value of this counter can occur at 2747 re-initialization of the management system, and at other 2748 times as indicated by the value of 2749 ipIfStatsDiscontinuityTime." 2750 ::= { ipIfStatsEntry 11 } 2752 ipIfStatsInForwDatagrams OBJECT-TYPE 2753 SYNTAX Counter32 2754 MAX-ACCESS read-only 2755 STATUS current 2756 DESCRIPTION 2757 "The number of input datagrams for which this entity was not 2758 their final IP destination and for which this entity 2759 attempted to find a route to forward them to that final 2760 destination. In entities which do not act as IP routers, 2761 this counter will include only those datagrams which were 2762 Source-Routed via this entity, and the Source-Route 2763 processing was successful. 2765 When tracking interface statistics the counter of the 2766 incoming interface is incremented for each datagram. 2768 Discontinuities in the value of this counter can occur at 2769 re-initialization of the management system, and at other 2770 times as indicated by the value of 2771 ipIfStatsDiscontinuityTime." 2772 ::= { ipIfStatsEntry 12 } 2774 ipIfStatsHCInForwDatagrams OBJECT-TYPE 2775 SYNTAX Counter64 2776 MAX-ACCESS read-only 2777 STATUS current 2778 DESCRIPTION 2779 "The number of input datagrams for which this entity was not 2780 their final IP destination and for which this entity 2781 attempted to find a route to forward them to that final 2782 destination. This object counts the same packets as 2783 ipIfInForwDatagrams but allows for larger values. 2785 Discontinuities in the value of this counter can occur at 2786 re-initialization of the management system, and at other 2787 times as indicated by the value of 2788 ipSystemStatsDiscontinuityTime." 2789 ::= { ipIfStatsEntry 13 } 2791 ipIfStatsReasmReqds OBJECT-TYPE 2792 SYNTAX Counter32 2793 MAX-ACCESS read-only 2794 STATUS current 2795 DESCRIPTION 2796 "The number of IP fragments received which needed to be 2797 reassembled at this interface. 2799 When tracking interface statistics the counter of the 2800 interface to which these fragments were addressed is 2801 incremented. This interface might not be the same as the 2802 input interface for some of the fragments. 2804 Discontinuities in the value of this counter can occur at 2805 re-initialization of the management system, and at other 2806 times as indicated by the value of 2807 ipIfStatsDiscontinuityTime." 2808 ::= { ipIfStatsEntry 14 } 2810 ipIfStatsReasmOKs OBJECT-TYPE 2811 SYNTAX Counter32 2812 MAX-ACCESS read-only 2813 STATUS current 2814 DESCRIPTION 2815 "The number of IP datagrams successfully reassembled. 2817 When tracking interface statistics the counter of the 2818 interface to which these datagrams were addressed is 2819 incremented. This interface might not be the same as the 2820 input interface for some of the datagrams. 2822 Discontinuities in the value of this counter can occur at 2823 re-initialization of the management system, and at other 2824 times as indicated by the value of 2825 ipIfStatsDiscontinuityTime." 2826 ::= { ipIfStatsEntry 15 } 2828 ipIfStatsReasmFails OBJECT-TYPE 2829 SYNTAX Counter32 2830 MAX-ACCESS read-only 2831 STATUS current 2832 DESCRIPTION 2833 "The number of failures detected by the IP re-assembly 2834 algorithm (for whatever reason: timed out, errors, etc.). 2835 Note that this is not necessarily a count of discarded IP 2836 fragments since some algorithms (notably the algorithm in 2837 RFC 815) can lose track of the number of fragments by 2838 combining them as they are received. 2840 When tracking interface statistics the counter of the 2841 interface to which these fragments were addressed is 2842 incremented. This interface might not be the same as the 2843 input interface for some of the fragments. 2845 Discontinuities in the value of this counter can occur at 2846 re-initialization of the management system, and at other 2847 times as indicated by the value of 2848 ipIfStatsDiscontinuityTime." 2849 ::= { ipIfStatsEntry 16 } 2851 ipIfStatsInDiscards OBJECT-TYPE 2852 SYNTAX Counter32 2853 MAX-ACCESS read-only 2854 STATUS current 2855 DESCRIPTION 2856 "The number of input IP datagrams for which no problems were 2857 encountered to prevent their continued processing, but which 2858 were discarded (e.g., for lack of buffer space). Note that 2859 this counter does not include any datagrams discarded while 2860 awaiting re-assembly. 2862 Discontinuities in the value of this counter can occur at 2863 re-initialization of the management system, and at other 2864 times as indicated by the value of 2865 ipIfStatsDiscontinuityTime." 2866 ::= { ipIfStatsEntry 17 } 2868 ipIfStatsInDelivers OBJECT-TYPE 2869 SYNTAX Counter32 2870 MAX-ACCESS read-only 2871 STATUS current 2872 DESCRIPTION 2873 "The total number of datagrams successfully delivered to IP 2874 user-protocols (including ICMP). 2876 When tracking interface statistics the counter of the 2877 interface to which these datagrams were addressed is 2878 incremented. This interface might not be the same as the 2879 input interface for some of the datagrams. 2881 Discontinuities in the value of this counter can occur at 2882 re-initialization of the management system, and at other 2883 times as indicated by the value of 2884 ipIfStatsDiscontinuityTime." 2885 ::= { ipIfStatsEntry 18 } 2887 ipIfStatsHCInDelivers OBJECT-TYPE 2888 SYNTAX Counter64 2889 MAX-ACCESS read-only 2890 STATUS current 2891 DESCRIPTION 2892 "The total number of datagrams successfully delivered to IP 2893 user-protocols (including ICMP). This object counts the 2894 same packets as ipIfStatsInDelivers but allows for larger 2895 values. 2897 Discontinuities in the value of this counter can occur at 2898 re-initialization of the management system, and at other 2899 times as indicated by the value of 2900 ipSystemStatsDiscontinuityTime." 2901 ::= { ipIfStatsEntry 19 } 2903 ipIfStatsOutRequests OBJECT-TYPE 2904 SYNTAX Counter32 2905 MAX-ACCESS read-only 2906 STATUS current 2907 DESCRIPTION 2908 "The total number of IP datagrams which local IP user- 2909 protocols (including ICMP) supplied to IP in requests for 2910 transmission. Note that this counter does not include any 2911 datagrams counted in ipIfStatsOutForwDatagrams. 2913 Discontinuities in the value of this counter can occur at 2914 re-initialization of the management system, and at other 2915 times as indicated by the value of 2916 ipIfStatsDiscontinuityTime." 2917 ::= { ipIfStatsEntry 20 } 2919 ipIfStatsHCOutRequests OBJECT-TYPE 2920 SYNTAX Counter64 2921 MAX-ACCESS read-only 2922 STATUS current 2923 DESCRIPTION 2924 "The total number of IP datagrams which local IP user- 2925 protocols (including ICMP) supplied to IP in requests for 2926 transmission. This object counts the same packets as 2927 ipIfStatsHCOutRequests but allows for larger values. 2929 Discontinuities in the value of this counter can occur at 2930 re-initialization of the management system, and at other 2931 times as indicated by the value of 2932 ipSystemStatsDiscontinuityTime." 2933 ::= { ipIfStatsEntry 21 } 2935 -- This object ID is reserved to allow the IDs for this table's objects 2936 -- to align with the objects in the ipSystemStatsTable. 2937 -- ::= {ipIfStatsEntry 22} 2939 ipIfStatsOutForwDatagrams OBJECT-TYPE 2940 SYNTAX Counter32 2941 MAX-ACCESS read-only 2942 STATUS current 2943 DESCRIPTION 2944 "The number of datagrams for which this entity was not their 2945 final IP destination and for which it was successful in 2946 finding a path to their final destination. In entities 2947 which do not act as IP routers, this counter will include 2948 only those datagrams which were Source-Routed via this 2949 entity, and the Source-Route processing was successful. 2951 When tracking interface statistics the counter of the 2952 outgoing interface is incremented for a successfully 2953 forwarded datagram. 2955 Discontinuities in the value of this counter can occur at 2956 re-initialization of the management system, and at other 2957 times as indicated by the value of 2958 ipIfStatsDiscontinuityTime." 2959 ::= { ipIfStatsEntry 23 } 2961 ipIfStatsHCOutForwDatagrams OBJECT-TYPE 2962 SYNTAX Counter64 2963 MAX-ACCESS read-only 2964 STATUS current 2965 DESCRIPTION 2966 "The number of datagrams for which this entity was not their 2967 final IP destination and for which it was successful in 2968 finding a path to their final destination. This object 2969 counts the same packets as ipIfStatsOutForwDatagrams but 2970 allows for larger values. 2972 Discontinuities in the value of this counter can occur at 2973 re-initialization of the management system, and at other 2974 times as indicated by the value of 2975 ipSystemStatsDiscontinuityTime." 2976 ::= { ipIfStatsEntry 24 } 2978 ipIfStatsOutDiscards OBJECT-TYPE 2979 SYNTAX Counter32 2980 MAX-ACCESS read-only 2981 STATUS current 2982 DESCRIPTION 2983 "The number of output IP datagrams for which no problem was 2984 encountered to prevent their transmission to their 2985 destination, but which were discarded (e.g., for lack of 2986 buffer space). Note that this counter would include 2987 datagrams counted in ipIfStatsOutForwDatagrams if any such 2988 datagrams met this (discretionary) discard criterion. 2990 Discontinuities in the value of this counter can occur at 2991 re-initialization of the management system, and at other 2992 times as indicated by the value of 2993 ipIfStatsDiscontinuityTime." 2994 ::= { ipIfStatsEntry 25 } 2996 ipIfStatsOutFragReqds OBJECT-TYPE 2997 SYNTAX Counter32 2998 MAX-ACCESS read-only 2999 STATUS current 3000 DESCRIPTION 3001 "The number of IP datagrams that would require fragmentation 3002 in order to be transmitted. 3004 When tracking interface statistics the counter of the 3005 outgoing interface is incremented for a successfully 3006 fragmented datagram. 3008 Discontinuities in the value of this counter can occur at 3009 re-initialization of the management system, and at other 3010 times as indicated by the value of 3011 ipIfStatsDiscontinuityTime." 3012 ::= { ipIfStatsEntry 26 } 3014 ipIfStatsOutFragOKs OBJECT-TYPE 3015 SYNTAX Counter32 3016 MAX-ACCESS read-only 3017 STATUS current 3018 DESCRIPTION 3019 "The number of IP datagrams that have been successfully 3020 fragmented. 3022 When tracking interface statistics the counter of the 3023 outgoing interface is incremented for a successfully 3024 fragmented datagram. 3026 Discontinuities in the value of this counter can occur at 3027 re-initialization of the management system, and at other 3028 times as indicated by the value of 3029 ipIfStatsDiscontinuityTime." 3030 ::= { ipIfStatsEntry 27 } 3032 ipIfStatsOutFragFails OBJECT-TYPE 3033 SYNTAX Counter32 3034 MAX-ACCESS read-only 3035 STATUS current 3036 DESCRIPTION 3037 "The number of IP datagrams that have been discarded because 3038 they needed to be fragmented but could not be. This 3039 includes IPv4 packets that have the DF bit set and IPv6 3040 packets that are being forwarded and exceed the outgoing 3041 link MTU. 3043 When tracking interface statistics the counter of the 3044 outgoing interface is incremented for an unsuccessfully 3045 fragmented datagram. 3047 Discontinuities in the value of this counter can occur at 3048 re-initialization of the management system, and at other 3049 times as indicated by the value of 3050 ipIfStatsDiscontinuityTime." 3051 ::= { ipIfStatsEntry 28 } 3053 ipIfStatsOutFragCreates OBJECT-TYPE 3054 SYNTAX Counter32 3055 MAX-ACCESS read-only 3056 STATUS current 3057 DESCRIPTION 3058 "The number of output datagram fragments that have been 3059 generated as a result of IP fragmentation. 3061 When tracking interface statistics the counter of the 3062 outgoing interface is incremented for a successfully 3063 fragmented datagram. 3065 Discontinuities in the value of this counter can occur at 3066 re-initialization of the management system, and at other 3067 times as indicated by the value of 3068 ipIfStatsDiscontinuityTime." 3069 ::= { ipIfStatsEntry 29 } 3071 ipIfStatsOutTransmits OBJECT-TYPE 3072 SYNTAX Counter32 3073 MAX-ACCESS read-only 3074 STATUS current 3075 DESCRIPTION 3076 "The total number of IP datagrams that this entity supplied 3077 to the lower layers for transmission. This includes 3078 datagrams generated local and those forwarded by this 3079 entity. 3081 Discontinuities in the value of this counter can occur at 3082 re-initialization of the management system, and at other 3083 times as indicated by the value of 3084 ipIfStatsDiscontinuityTime." 3085 ::= { ipIfStatsEntry 30 } 3087 ipIfStatsHCOutTransmits OBJECT-TYPE 3088 SYNTAX Counter64 3089 MAX-ACCESS read-only 3090 STATUS current 3091 DESCRIPTION 3092 "The total number of IP datagrams that this entity supplied 3093 to the lower layers for transmission. This object counts 3094 the same datagrams as ipIfStatsOutTransmits but allows for 3095 larger values. 3097 Discontinuities in the value of this counter can occur at 3098 re-initialization of the management system, and at other 3099 times as indicated by the value of 3100 ipIfStatsDiscontinuityTime." 3101 ::= { ipIfStatsEntry 31 } 3103 ipIfStatsOutOctets OBJECT-TYPE 3104 SYNTAX Counter32 3105 MAX-ACCESS read-only 3106 STATUS current 3107 DESCRIPTION 3108 "The total number of octets in IP datagrams delivered to the 3109 lower layers for transmission. Octets from datagrams 3110 counted in ipIfStatsOutTransmits MUST be counted here. 3112 Discontinuities in the value of this counter can occur at 3113 re-initialization of the management system, and at other 3114 times as indicated by the value of 3115 ipIfStatsDiscontinuityTime." 3116 ::= { ipIfStatsEntry 32 } 3118 ipIfStatsHCOutOctets OBJECT-TYPE 3119 SYNTAX Counter64 3120 MAX-ACCESS read-only 3121 STATUS current 3122 DESCRIPTION 3123 "The total number of octets in IP datagrams delivered to the 3124 lower layers for transmission. This objects counts the same 3125 octets as ipIfStatsOutOctets but allows for larger values. 3127 Discontinuities in the value of this counter can occur at 3128 re-initialization of the management system, and at other 3129 times as indicated by the value of 3130 ipIfStatsDiscontinuityTime." 3131 ::= { ipIfStatsEntry 33 } 3133 ipIfStatsInMcastPkts OBJECT-TYPE 3134 SYNTAX Counter32 3135 MAX-ACCESS read-only 3136 STATUS current 3137 DESCRIPTION 3138 "The number of IP multicast datagrams received. 3140 Discontinuities in the value of this counter can occur at 3141 re-initialization of the management system, and at other 3142 times as indicated by the value of 3143 ipIfStatsDiscontinuityTime." 3144 ::= { ipIfStatsEntry 34 } 3146 ipIfStatsHCInMcastPkts OBJECT-TYPE 3147 SYNTAX Counter64 3148 MAX-ACCESS read-only 3149 STATUS current 3150 DESCRIPTION 3151 "The number of IP multicast datagrams received. This object 3152 counts the same datagrams as ipIfStatsInMcastPkts but allows 3153 for larger values. 3155 Discontinuities in the value of this counter can occur at 3156 re-initialization of the management system, and at other 3157 times as indicated by the value of 3158 ipIfStatsDiscontinuityTime." 3159 ::= { ipIfStatsEntry 35 } 3161 ipIfStatsInMcastOctets OBJECT-TYPE 3162 SYNTAX Counter32 3163 MAX-ACCESS read-only 3164 STATUS current 3165 DESCRIPTION 3166 "The total number of octets received in IP multicast 3167 datagrams. Octets from datagrams counted in 3168 ipIfStatsOutMcastPkts MUST be counted here. 3170 Discontinuities in the value of this counter can occur at 3171 re-initialization of the management system, and at other 3172 times as indicated by the value of 3173 ipIfStatsDiscontinuityTime." 3174 ::= { ipIfStatsEntry 36 } 3176 ipIfStatsHCInMcastOctets OBJECT-TYPE 3177 SYNTAX Counter64 3178 MAX-ACCESS read-only 3179 STATUS current 3180 DESCRIPTION 3181 "The total number of octets received in IP multicast 3182 datagrams. This object counts the same octets as 3183 ipIfStatsInMcastOctets but allows for larger values. 3185 Discontinuities in the value of this counter can occur at 3186 re-initialization of the management system, and at other 3187 times as indicated by the value of 3188 ipIfStatsDiscontinuityTime." 3189 ::= { ipIfStatsEntry 37 } 3191 ipIfStatsOutMcastPkts OBJECT-TYPE 3192 SYNTAX Counter32 3193 MAX-ACCESS read-only 3194 STATUS current 3195 DESCRIPTION 3196 "The number of IP multicast datagrams transmitted. 3198 Discontinuities in the value of this counter can occur at 3199 re-initialization of the management system, and at other 3200 times as indicated by the value of 3201 ipIfStatsDiscontinuityTime." 3202 ::= { ipIfStatsEntry 38 } 3204 ipIfStatsHCOutMcastPkts OBJECT-TYPE 3205 SYNTAX Counter64 3206 MAX-ACCESS read-only 3207 STATUS current 3208 DESCRIPTION 3209 "The number of IP multicast datagrams transmitted. This 3210 object counts the same datagrams as ipIfStatsOutMcastPkts 3211 but allows for larger values. 3213 Discontinuities in the value of this counter can occur at 3214 re-initialization of the management system, and at other 3215 times as indicated by the value of 3216 ipIfStatsDiscontinuityTime." 3217 ::= { ipIfStatsEntry 39 } 3219 ipIfStatsOutMcastOctets OBJECT-TYPE 3220 SYNTAX Counter32 3221 MAX-ACCESS read-only 3222 STATUS current 3223 DESCRIPTION 3224 "The total number of octets transmitted in IP multicast 3225 datagrams. Octets from datagrams counted in 3226 ipIfStatsInMcastPkts MUST be counted here. 3228 Discontinuities in the value of this counter can occur at 3229 re-initialization of the management system, and at other 3230 times as indicated by the value of 3231 ipIfStatsDiscontinuityTime." 3232 ::= { ipIfStatsEntry 40 } 3234 ipIfStatsHCOutMcastOctets OBJECT-TYPE 3235 SYNTAX Counter64 3236 MAX-ACCESS read-only 3237 STATUS current 3238 DESCRIPTION 3239 "The total number of octets transmitted in IP multicast 3240 datagrams. This object counts the same octets as 3241 ipIfStatsOutMcastOctets but allows for larger values. 3243 Discontinuities in the value of this counter can occur at 3244 re-initialization of the management system, and at other 3245 times as indicated by the value of 3246 ipIfStatsDiscontinuityTime." 3247 ::= { ipIfStatsEntry 41 } 3249 ipIfStatsInBcastPkts OBJECT-TYPE 3250 SYNTAX Counter32 3251 MAX-ACCESS read-only 3252 STATUS current 3253 DESCRIPTION 3254 "The number of IP broadcast datagrams received. 3256 Discontinuities in the value of this counter can occur at 3257 re-initialization of the management system, and at other 3258 times as indicated by the value of 3259 ipIfStatsDiscontinuityTime." 3260 ::= { ipIfStatsEntry 42 } 3262 ipIfStatsHCInBcastPkts OBJECT-TYPE 3263 SYNTAX Counter64 3264 MAX-ACCESS read-only 3265 STATUS current 3266 DESCRIPTION 3267 "The number of IP broadcast datagrams received. This object 3268 counts the same datagrams as ipIfStatsInBcastPkts but allows 3269 for larger values. 3271 Discontinuities in the value of this counter can occur at 3272 re-initialization of the management system, and at other 3273 times as indicated by the value of 3274 ipIfStatsDiscontinuityTime." 3275 ::= { ipIfStatsEntry 43 } 3277 ipIfStatsOutBcastPkts OBJECT-TYPE 3278 SYNTAX Counter32 3279 MAX-ACCESS read-only 3280 STATUS current 3281 DESCRIPTION 3282 "The number of IP broadcast datagrams transmitted. 3284 Discontinuities in the value of this counter can occur at 3285 re-initialization of the management system, and at other 3286 times as indicated by the value of 3287 ipIfStatsDiscontinuityTime." 3288 ::= { ipIfStatsEntry 44 } 3290 ipIfStatsHCOutBcastPkts OBJECT-TYPE 3291 SYNTAX Counter64 3292 MAX-ACCESS read-only 3293 STATUS current 3294 DESCRIPTION 3295 "The number of IP broadcast datagrams transmitted. This 3296 object counts the same datagrams as ipIfStatsOutBcastPkts 3297 but allows for larger values. 3299 Discontinuities in the value of this counter can occur at 3300 re-initialization of the management system, and at other 3301 times as indicated by the value of 3302 ipIfStatsDiscontinuityTime." 3303 ::= { ipIfStatsEntry 45 } 3305 ipIfStatsDiscontinuityTime OBJECT-TYPE 3306 SYNTAX TimeStamp 3307 MAX-ACCESS read-only 3308 STATUS current 3309 DESCRIPTION 3310 "The value of sysUpTime on the most recent occasion at which 3311 any one or more of this entry's counters suffered a 3312 discontinuity. 3314 If no such discontinuities have occurred since the last re- 3315 initialization of the local management subsystem, then this 3316 object contains a zero value." 3317 ::= { ipIfStatsEntry 46 } 3319 ipIfStatsRefreshRate OBJECT-TYPE 3320 SYNTAX Unsigned32 3321 UNITS "milli-seconds" 3322 MAX-ACCESS read-only 3323 STATUS current 3324 DESCRIPTION 3325 "The minimum reasonable polling interval for this entry. 3326 This object provides an indication of the minimum amount of 3327 time required to update the counters in this entry." 3328 ::= { ipIfStatsEntry 47 } 3330 -- 3331 -- Internet Address Prefix table 3332 -- 3334 ipAddressPrefixTable OBJECT-TYPE 3335 SYNTAX SEQUENCE OF IpAddressPrefixEntry 3336 MAX-ACCESS not-accessible 3337 STATUS current 3338 DESCRIPTION 3339 "This table allows the user to determine the source of an IP 3340 address or set of IP addresses and allows other tables to 3341 share the information via pointer rather than by copying. 3343 For example when the node configures both a unicast and 3344 anycast address for a prefix the ipAddressPrefix objects for 3345 those addresses will point to a single row in this table. 3347 This table primarily provides support for IPv6 prefixes and 3348 several of the objects are less meaningful for IPv4. The 3349 table continues to allow IPv4 addresses to allow future 3350 flexibility. In order to promote a common configuration 3351 this document includes suggestions for default values for 3352 IPv4 prefixes. Each of these values may be overridden if an 3353 object is meaningful to the node. 3355 All prefixes used by this entity should be included in this 3356 table independent of how the entity learned the prefix. 3357 (This table isn't limited to prefixes learned from router 3358 advertisements.) " 3359 ::= { ip 32 } 3361 ipAddressPrefixEntry OBJECT-TYPE 3362 SYNTAX IpAddressPrefixEntry 3363 MAX-ACCESS not-accessible 3364 STATUS current 3365 DESCRIPTION 3366 "An entry in the ipAddressPrefixTable." 3367 INDEX { ipAddressPrefixIfIndex, ipAddressPrefixType, 3368 ipAddressPrefixPrefix, ipAddressPrefixLength } 3369 ::= { ipAddressPrefixTable 1 } 3371 IpAddressPrefixEntry ::= SEQUENCE { 3372 ipAddressPrefixIfIndex InterfaceIndex, 3373 ipAddressPrefixType InetAddressType, 3374 ipAddressPrefixPrefix InetAddress, 3375 ipAddressPrefixLength InetAddressPrefixLength, 3376 ipAddressPrefixOrigin IpAddressPrefixOriginTC, 3377 ipAddressPrefixOnLinkFlag TruthValue, 3378 ipAddressPrefixAutonomousFlag TruthValue, 3379 ipAddressPrefixAdvPreferredLifetime Unsigned32, 3380 ipAddressPrefixAdvValidLifetime Unsigned32 3381 } 3383 ipAddressPrefixIfIndex OBJECT-TYPE 3384 SYNTAX InterfaceIndex 3385 MAX-ACCESS not-accessible 3386 STATUS current 3387 DESCRIPTION 3388 "The index value which uniquely identifies the interface on 3389 which this prefix is configured. The interface identified 3390 by a particular value of this index is the same interface as 3391 identified by the same value of the IF-MIB's ifIndex." 3392 ::= { ipAddressPrefixEntry 1 } 3394 ipAddressPrefixType OBJECT-TYPE 3395 SYNTAX InetAddressType 3396 MAX-ACCESS not-accessible 3397 STATUS current 3398 DESCRIPTION 3399 "The address type of ipAddressPrefix." 3400 ::= { ipAddressPrefixEntry 2 } 3402 ipAddressPrefixPrefix OBJECT-TYPE 3403 SYNTAX InetAddress 3404 MAX-ACCESS not-accessible 3405 STATUS current 3406 DESCRIPTION 3407 "The address prefix. The address type of this object is 3408 specified in ipAddressPrefixType. The length of this object 3409 is the standard length for objects of that type (4 or 16 3410 bytes). Any bits after ipAddressPrefixLength must be zero. 3412 Implementors need to be aware that if the size of 3413 ipAddressPrefixPrefix exceeds 114 octets then OIDS of 3414 instances of columns in this row will have more than 128 3415 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c 3416 or SNMPv3." 3417 ::= { ipAddressPrefixEntry 3 } 3419 ipAddressPrefixLength OBJECT-TYPE 3420 SYNTAX InetAddressPrefixLength 3421 MAX-ACCESS not-accessible 3422 STATUS current 3423 DESCRIPTION 3424 "The prefix length associated with this prefix. 3426 The value 0 has no special meaning for this object. It 3427 simply refers to address '::/0'." 3428 ::= { ipAddressPrefixEntry 4 } 3430 ipAddressPrefixOrigin OBJECT-TYPE 3431 SYNTAX IpAddressPrefixOriginTC 3432 MAX-ACCESS read-only 3433 STATUS current 3434 DESCRIPTION 3435 "The origin of this prefix." 3436 ::= { ipAddressPrefixEntry 5 } 3438 ipAddressPrefixOnLinkFlag OBJECT-TYPE 3439 SYNTAX TruthValue 3440 MAX-ACCESS read-only 3441 STATUS current 3442 DESCRIPTION 3443 "This object has the value 'true(1)', if this prefix can be 3444 used for on-link determination and the value 'false(2)' 3445 otherwise. 3447 The default for IPv4 prefixes is 'true(1)'." 3448 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and 3449 RFC2462" 3450 ::= { ipAddressPrefixEntry 6 } 3452 ipAddressPrefixAutonomousFlag OBJECT-TYPE 3453 SYNTAX TruthValue 3454 MAX-ACCESS read-only 3455 STATUS current 3456 DESCRIPTION 3457 "Autonomous address configuration flag. When true(1), 3458 indicates that this prefix can be used for autonomous 3459 address configuration (i.e. can be used to form a local 3460 interface address). If false(2), it is not used to auto- 3461 configure a local interface address. 3463 The default for IPv4 prefixes is 'false(2)'." 3464 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and 3465 RFC2462" 3466 ::= { ipAddressPrefixEntry 7 } 3468 ipAddressPrefixAdvPreferredLifetime OBJECT-TYPE 3469 SYNTAX Unsigned32 3470 UNITS "seconds" 3471 MAX-ACCESS read-only 3472 STATUS current 3473 DESCRIPTION 3474 "The remaining length of time in seconds that this prefix 3475 will continue to be preferred, i.e. time until deprecation. 3477 A value of 4,294,967,295 represents infinity. 3479 The address generated from a deprecated prefix should no 3480 longer be used as a source address in new communications, 3481 but packets received on such an interface are processed as 3482 expected. 3484 The default for IPv4 prefixes is 4,294,967,295 (infinity)." 3485 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and 3486 RFC2462" 3487 ::= { ipAddressPrefixEntry 8 } 3489 ipAddressPrefixAdvValidLifetime OBJECT-TYPE 3490 SYNTAX Unsigned32 3491 UNITS "seconds" 3492 MAX-ACCESS read-only 3493 STATUS current 3494 DESCRIPTION 3495 "The remaining length of time, in seconds, that this prefix 3496 will continue to be valid, i.e. time until invalidation. A 3497 value of 4,294,967,295 represents infinity. 3499 The address generated from an invalidated prefix should not 3500 appear as the destination or source address of a packet. 3502 The default for IPv4 prefixes is 4,294,967,295 (infinity)." 3503 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and 3504 RFC2462" 3505 ::= { ipAddressPrefixEntry 9 } 3507 -- 3508 -- Internet Address Table 3509 -- 3511 ipAddressSpinLock OBJECT-TYPE 3512 SYNTAX TestAndIncr 3513 MAX-ACCESS read-write 3514 STATUS current 3515 DESCRIPTION 3516 "An advisory lock used to allow cooperating SNMP managers to 3517 coordinate their use of the set operation in creating or 3518 modifying rows within this table. 3520 In order to use this lock to coordinate the use of set 3521 operations managers should first retrieve 3522 ipvAddressTableSpinLock. They should then determine the 3523 appropriate row to create or modify. Finally they should 3524 issue the appropriate set command including the retrieved 3525 value of ipAddressSpinLock. If another manager has altered 3526 the table in the meantime, then the value of 3527 ipAddressSpinLock will have changed and the creation will 3528 fail as it will be specifying an incorrect value for 3529 ipAddressSpinLock. It is suggested, but not required, that 3530 the ipAddressSpinLock be the first var bind for each set of 3531 objects representing a 'row' in a PDU. " 3532 ::= { ip 33 } 3534 ipAddressTable OBJECT-TYPE 3535 SYNTAX SEQUENCE OF IpAddressEntry 3536 MAX-ACCESS not-accessible 3537 STATUS current 3538 DESCRIPTION 3539 "This table contains addressing information relevant to the 3540 entity's interfaces. 3542 This table does not contain multicast address information. 3543 Tables for such information should be contained in multicast 3544 specific MIBs such as RFC3019. 3546 While this table is writable the user will note that several 3547 objects, such as ipAddressOrigin, are not. The intention in 3548 allowing a user to write to this table is to allow them to 3549 add or remove any entry that isn't permanent. The user 3550 should be allowed to modify objects and entries when that 3551 would not cause inconsistencies within the table. Allowing 3552 write access to objects such as ipAddressOrigin could allow 3553 a user to insert an entry and then label it incorrectly. 3555 Note well: When including IPv6 link-local addresses in this 3556 table the entry must use an InetAddressType of 'ipv6z' in 3557 order to differentiate between the possible interfaces. 3559 " 3560 ::= { ip 34 } 3562 ipAddressEntry OBJECT-TYPE 3563 SYNTAX IpAddressEntry 3564 MAX-ACCESS not-accessible 3565 STATUS current 3566 DESCRIPTION 3567 "An address mapping for a particular interface." 3568 INDEX { ipAddressAddrType, ipAddressAddr } 3569 ::= { ipAddressTable 1 } 3571 IpAddressEntry ::= SEQUENCE { 3572 ipAddressAddrType InetAddressType, 3573 ipAddressAddr InetAddress, 3574 ipAddressIfIndex InterfaceIndex, 3575 ipAddressType INTEGER, 3576 ipAddressPrefix RowPointer, 3577 ipAddressOrigin IpAddressOriginTC, 3578 ipAddressStatus IpAddressStatusTC, 3579 ipAddressCreated TimeStamp, 3580 ipAddressLastChanged TimeStamp, 3581 ipAddressRowStatus RowStatus, 3582 ipAddressStorageType StorageType 3583 } 3585 ipAddressAddrType OBJECT-TYPE 3586 SYNTAX InetAddressType 3587 MAX-ACCESS not-accessible 3588 STATUS current 3589 DESCRIPTION 3590 "The address type of ipAddressAddr." 3591 ::= { ipAddressEntry 1 } 3593 ipAddressAddr OBJECT-TYPE 3594 SYNTAX InetAddress 3595 MAX-ACCESS not-accessible 3596 STATUS current 3597 DESCRIPTION 3598 "The IP address to which this entry's addressing information 3599 pertains. The address type of this object is specified in 3600 ipAddressAddrType. 3602 Implementors need to be aware that if the size of 3603 ipAddressAddr exceeds 116 octets then OIDS of instances of 3604 columns in this row will have more than 128 sub-identifiers 3605 and cannot be accessed using SNMPv1, SNMPv2c or SNMPv3." 3606 ::= { ipAddressEntry 2 } 3608 ipAddressIfIndex OBJECT-TYPE 3609 SYNTAX InterfaceIndex 3610 MAX-ACCESS read-create 3611 STATUS current 3612 DESCRIPTION 3613 "The index value which uniquely identifies the interface to 3614 which this entry is applicable. The interface identified by 3615 a particular value of this index is the same interface as 3616 identified by the same value of the IF-MIB's ifIndex." 3617 ::= { ipAddressEntry 3 } 3619 ipAddressType OBJECT-TYPE 3620 SYNTAX INTEGER { 3621 unicast(1), 3622 anycast(2), 3623 broadcast(3) 3624 } 3625 MAX-ACCESS read-create 3626 STATUS current 3627 DESCRIPTION 3628 "The type of address. broadcast(3) is not a valid value for 3629 IPv6 addresses (RFC3513). " 3630 DEFVAL { unicast } 3631 ::= { ipAddressEntry 4 } 3633 ipAddressPrefix OBJECT-TYPE 3634 SYNTAX RowPointer 3635 MAX-ACCESS read-only 3636 STATUS current 3637 DESCRIPTION 3638 "A pointer to the row in the prefix table to which this 3639 address belongs. May be { 0 0 } if there is no such row." 3640 DEFVAL { zeroDotZero } 3641 ::= { ipAddressEntry 5 } 3643 ipAddressOrigin OBJECT-TYPE 3644 SYNTAX IpAddressOriginTC 3645 MAX-ACCESS read-only 3646 STATUS current 3647 DESCRIPTION 3648 "The origin of the address." 3649 ::= { ipAddressEntry 6 } 3651 ipAddressStatus OBJECT-TYPE 3652 SYNTAX IpAddressStatusTC 3653 MAX-ACCESS read-create 3654 STATUS current 3655 DESCRIPTION 3656 "The status of the address, describing if the address can be 3657 used for communication. 3659 In the absence of other information, an IPv4 address is 3660 always preferred(1)." 3661 DEFVAL { preferred } 3662 ::= { ipAddressEntry 7 } 3664 ipAddressCreated OBJECT-TYPE 3665 SYNTAX TimeStamp 3666 MAX-ACCESS read-only 3667 STATUS current 3668 DESCRIPTION 3669 "The value of sysUpTime at the time this entry was created. 3670 If this entry was created prior to the last re- 3671 initialization of the local network management subsystem, 3672 then this object contains a zero value." 3673 ::= { ipAddressEntry 8 } 3675 ipAddressLastChanged OBJECT-TYPE 3676 SYNTAX TimeStamp 3677 MAX-ACCESS read-only 3678 STATUS current 3679 DESCRIPTION 3680 "The value of sysUpTime at the time this entry was last 3681 updated. If this entry was updated prior to the last re- 3682 initialization of the local network management subsystem, 3683 then this object contains a zero value." 3684 ::= { ipAddressEntry 9 } 3686 ipAddressRowStatus OBJECT-TYPE 3687 SYNTAX RowStatus 3688 MAX-ACCESS read-create 3689 STATUS current 3690 DESCRIPTION 3691 "The status of this conceptual row. 3693 The RowStatus TC requires that this DESCRIPTION clause 3694 states under which circumstances other objects in this row 3695 can be modified. The value of this object has no effect on 3696 whether other objects in this conceptual row can be 3697 modified. 3699 A conceptual row can not be made active until the 3700 ipAddressIfIndex has been set to a valid index. " 3701 ::= { ipAddressEntry 10 } 3703 ipAddressStorageType OBJECT-TYPE 3704 SYNTAX StorageType 3705 MAX-ACCESS read-create 3706 STATUS current 3707 DESCRIPTION 3708 "The storage type for this conceptual row. If this object 3709 has a value of 'permanent' then no other objects are 3710 required to be able to be modified." 3711 DEFVAL { volatile } 3712 ::= { ipAddressEntry 11 } 3714 -- 3715 -- the Internet Address Translation table 3716 -- 3718 ipNetToPhysicalTable OBJECT-TYPE 3719 SYNTAX SEQUENCE OF IpNetToPhysicalEntry 3720 MAX-ACCESS not-accessible 3721 STATUS current 3722 DESCRIPTION 3723 "The IP Address Translation table used for mapping from IP 3724 addresses to physical addresses. 3726 The Address Translation tables contain the IP address to 3727 'physical' address equivalences. Some interfaces do not use 3728 translation tables for determining address equivalences 3729 (e.g., DDN-X.25 has an algorithmic method); if all 3730 interfaces are of this type, then the Address Translation 3731 table is empty, i.e., has zero entries. 3733 While many protocols may be used to populate this table, ARP 3734 [10] and Neighbor Discovery [4] are the most likely 3735 options." 3736 REFERENCE "RFC0826 and RFC2461" 3737 ::= { ip 35 } 3739 ipNetToPhysicalEntry OBJECT-TYPE 3740 SYNTAX IpNetToPhysicalEntry 3741 MAX-ACCESS not-accessible 3742 STATUS current 3743 DESCRIPTION 3744 "Each entry contains one IP address to `physical' address 3745 equivalence." 3746 INDEX { ipNetToPhysicalIfIndex, 3747 ipNetToPhysicalNetAddressType, 3748 ipNetToPhysicalNetAddress } 3749 ::= { ipNetToPhysicalTable 1 } 3751 IpNetToPhysicalEntry ::= SEQUENCE { 3752 ipNetToPhysicalIfIndex InterfaceIndex, 3753 ipNetToPhysicalNetAddressType InetAddressType, 3754 ipNetToPhysicalNetAddress InetAddress, 3755 ipNetToPhysicalPhysAddress PhysAddress, 3756 ipNetToPhysicalLastUpdated TimeStamp, 3757 ipNetToPhysicalType INTEGER, 3758 ipNetToPhysicalState INTEGER, 3759 ipNetToPhysicalRowStatus RowStatus 3760 } 3762 ipNetToPhysicalIfIndex OBJECT-TYPE 3763 SYNTAX InterfaceIndex 3764 MAX-ACCESS not-accessible 3765 STATUS current 3766 DESCRIPTION 3767 "The index value which uniquely identifies the interface to 3768 which this entry is applicable. The interface identified by 3769 a particular value of this index is the same interface as 3770 identified by the same value of the IF-MIB's ifIndex." 3771 ::= { ipNetToPhysicalEntry 1 } 3773 ipNetToPhysicalNetAddressType OBJECT-TYPE 3774 SYNTAX InetAddressType 3775 MAX-ACCESS not-accessible 3776 STATUS current 3777 DESCRIPTION 3778 "The type of ipNetToPhysicalNetAddress." 3779 ::= { ipNetToPhysicalEntry 2 } 3781 ipNetToPhysicalNetAddress OBJECT-TYPE 3782 SYNTAX InetAddress 3783 MAX-ACCESS not-accessible 3784 STATUS current 3785 DESCRIPTION 3786 "The IP Address corresponding to the media-dependent 3787 `physical' address. The address type of this object is 3788 specified in ipNetToPhysicalAddressType. 3790 Implementors need to be aware that if the size of 3791 ipNetToPhysicalNetAddress exceeds 115 octets then OIDS of 3792 instances of columns in this row will have more than 128 3793 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c 3794 or SNMPv3." 3795 ::= { ipNetToPhysicalEntry 3 } 3797 ipNetToPhysicalPhysAddress OBJECT-TYPE 3798 SYNTAX PhysAddress (SIZE(0..65535)) 3799 MAX-ACCESS read-create 3800 STATUS current 3801 DESCRIPTION 3802 "The media-dependent `physical' address. 3804 As the entries in this table are typically not persistent 3805 when this object is written the entity SHOULD NOT save the 3806 change to non-volatile storage." 3807 ::= { ipNetToPhysicalEntry 4 } 3809 ipNetToPhysicalLastUpdated OBJECT-TYPE 3810 SYNTAX TimeStamp 3811 MAX-ACCESS read-only 3812 STATUS current 3813 DESCRIPTION 3814 "The value of sysUpTime at the time this entry was last 3815 updated. If this entry was updated prior to the last re- 3816 initialization of the local network management subsystem, 3817 then this object contains a zero value." 3818 ::= { ipNetToPhysicalEntry 5 } 3820 ipNetToPhysicalType OBJECT-TYPE 3821 SYNTAX INTEGER { 3822 other(1), -- none of the following 3823 invalid(2), -- an invalidated mapping 3824 dynamic(3), 3825 static(4), 3826 local(5) -- local interface 3827 } 3828 MAX-ACCESS read-create 3829 STATUS current 3830 DESCRIPTION 3831 "The type of mapping. 3833 Setting this object to the value invalid(2) has the effect 3834 of invalidating the corresponding entry in the 3835 ipNetToPhysicalTable. That is, it effectively dis- 3836 associates the interface identified with said entry from the 3837 mapping identified with said entry. It is an 3838 implementation- specific matter as to whether the agent 3839 removes an invalidated entry from the table. Accordingly, 3840 management stations must be prepared to receive tabular 3841 information from agents that corresponds to entries not 3842 currently in use. Proper interpretation of such entries 3843 requires examination of the relevant ipNetToPhysicalType 3844 object. 3846 The 'dynamic(3)' type indicates that the IP address to 3847 physical addresses mapping has been dynamically resolved 3848 using e.g. IPv4 ARP or the IPv6 Neighbor Discovery protocol. 3850 The 'static(4)' type indicates that the mapping has been 3851 statically configured. Both of these refer to entries that 3852 provide mappings for other entities addresses. 3854 The 'local(5)' type indicates that the mapping is provided 3855 for an entity's own interface address. 3857 As the entries in this table are typically not persistent 3858 when this object is written the entity SHOULD NOT save the 3859 change to non-volatile storage." 3860 DEFVAL { static } 3861 ::= { ipNetToPhysicalEntry 6 } 3863 ipNetToPhysicalState OBJECT-TYPE 3864 SYNTAX INTEGER { 3865 reachable(1), -- confirmed reachability 3867 stale(2), -- unconfirmed reachability 3869 delay(3), -- waiting for reachability 3870 -- confirmation before entering 3871 -- the probe state 3873 probe(4), -- actively probing 3875 invalid(5), -- an invalidated mapping 3877 unknown(6), -- state can not be determined 3878 -- for some reason. 3880 incomplete(7) -- address resolution is being performed. 3881 } 3882 MAX-ACCESS read-only 3883 STATUS current 3884 DESCRIPTION 3885 "The Neighbor Unreachability Detection [4] state for the 3886 interface when the address mapping in this entry is used. 3887 If Neighbor Unreachability Detection is not in use (e.g. for 3888 IPv4), this object is always unknown(6)." 3889 REFERENCE "RFC2461" 3890 ::= { ipNetToPhysicalEntry 7 } 3892 ipNetToPhysicalRowStatus OBJECT-TYPE 3893 SYNTAX RowStatus 3894 MAX-ACCESS read-create 3895 STATUS current 3896 DESCRIPTION 3897 "The status of this conceptual row. 3899 The RowStatus TC requires that this DESCRIPTION clause 3900 states under which circumstances other objects in this row 3901 can be modified. The value of this object has no effect on 3902 whether other objects in this conceptual row can be 3903 modified. 3905 A conceptual row can not be made active until the 3906 ipNetToPhysicalPhysAddress object has been set. 3908 Note that if the ipNetToPhysicalType is set to 'invalid' the 3909 managed node may delete the entry independent of the state 3910 of this object." 3911 ::= { ipNetToPhysicalEntry 8 } 3913 -- 3914 -- The IPv6 Scope Zone Index Table. 3915 -- 3917 ipv6ScopeZoneIndexTable OBJECT-TYPE 3918 SYNTAX SEQUENCE OF Ipv6ScopeZoneIndexEntry 3919 MAX-ACCESS not-accessible 3920 STATUS current 3921 DESCRIPTION 3922 "The table used to describe IPv6 unicast and multicast scope 3923 zones. 3925 For those objects that have names rather than numbers the 3926 names were chosen to coincide with the names used in the 3927 IPv6 address architecture document, [17]. " 3928 REFERENCE "Section 2.7 of draft-ietf-ipv6-addr-arch-v4-00.txt" 3929 -- RFC Editor 3930 -- If the address architecture document precedes this document as an RFC 3931 -- please update this reference to use the proper RFC number. 3932 ::= { ip 36 } 3934 ipv6ScopeZoneIndexEntry OBJECT-TYPE 3935 SYNTAX Ipv6ScopeZoneIndexEntry 3936 MAX-ACCESS not-accessible 3937 STATUS current 3938 DESCRIPTION 3939 "Each entry contains the list of scope identifiers on a given 3940 interface." 3941 INDEX { ipv6ScopeZoneIndexIfIndex } 3942 ::= { ipv6ScopeZoneIndexTable 1 } 3944 Ipv6ScopeZoneIndexEntry ::= SEQUENCE { 3945 ipv6ScopeZoneIndexIfIndex InterfaceIndex, 3946 ipv6ScopeZoneIndexLinkLocal InetZoneIndex, 3947 ipv6ScopeZoneIndex3 InetZoneIndex, 3948 ipv6ScopeZoneIndexAdminLocal InetZoneIndex, 3949 ipv6ScopeZoneIndexSiteLocal InetZoneIndex, 3950 ipv6ScopeZoneIndex6 InetZoneIndex, 3951 ipv6ScopeZoneIndex7 InetZoneIndex, 3952 ipv6ScopeZoneIndexOrganizationLocal InetZoneIndex, 3953 ipv6ScopeZoneIndex9 InetZoneIndex, 3954 ipv6ScopeZoneIndexA InetZoneIndex, 3955 ipv6ScopeZoneIndexB InetZoneIndex, 3956 ipv6ScopeZoneIndexC InetZoneIndex, 3957 ipv6ScopeZoneIndexD InetZoneIndex 3958 } 3960 ipv6ScopeZoneIndexIfIndex OBJECT-TYPE 3961 SYNTAX InterfaceIndex 3962 MAX-ACCESS not-accessible 3963 STATUS current 3964 DESCRIPTION 3965 "The index value which uniquely identifies the interface to 3966 which these scopes belong. The interface identified by a 3967 particular value of this index is the same interface as 3968 identified by the same value of the IF-MIB's ifIndex." 3969 ::= { ipv6ScopeZoneIndexEntry 1 } 3971 ipv6ScopeZoneIndexLinkLocal OBJECT-TYPE 3972 SYNTAX InetZoneIndex 3973 MAX-ACCESS read-only 3974 STATUS current 3975 DESCRIPTION 3976 "The zone index for the link-local scope on this interface." 3977 ::= { ipv6ScopeZoneIndexEntry 2 } 3979 ipv6ScopeZoneIndex3 OBJECT-TYPE 3980 SYNTAX InetZoneIndex 3981 MAX-ACCESS read-only 3982 STATUS current 3983 DESCRIPTION 3984 "The zone index for the subnet-local scope on this 3985 interface." 3986 ::= { ipv6ScopeZoneIndexEntry 3 } 3988 ipv6ScopeZoneIndexAdminLocal OBJECT-TYPE 3989 SYNTAX InetZoneIndex 3990 MAX-ACCESS read-only 3991 STATUS current 3992 DESCRIPTION 3993 "The zone index for the admin-local scope on this interface." 3994 ::= { ipv6ScopeZoneIndexEntry 4 } 3996 ipv6ScopeZoneIndexSiteLocal OBJECT-TYPE 3997 SYNTAX InetZoneIndex 3998 MAX-ACCESS read-only 3999 STATUS current 4000 DESCRIPTION 4001 "The zone index for the site-local scope on this interface." 4003 ::= { ipv6ScopeZoneIndexEntry 5 } 4005 ipv6ScopeZoneIndex6 OBJECT-TYPE 4006 SYNTAX InetZoneIndex 4007 MAX-ACCESS read-only 4008 STATUS current 4009 DESCRIPTION 4010 "The zone index for scope 6 on this interface." 4011 ::= { ipv6ScopeZoneIndexEntry 6 } 4013 ipv6ScopeZoneIndex7 OBJECT-TYPE 4014 SYNTAX InetZoneIndex 4015 MAX-ACCESS read-only 4016 STATUS current 4017 DESCRIPTION 4018 "The zone index for scope 7 on this interface." 4019 ::= { ipv6ScopeZoneIndexEntry 7 } 4021 ipv6ScopeZoneIndexOrganizationLocal OBJECT-TYPE 4022 SYNTAX InetZoneIndex 4023 MAX-ACCESS read-only 4024 STATUS current 4025 DESCRIPTION 4026 "The zone index for the organization-local scope on this 4027 interface." 4028 ::= { ipv6ScopeZoneIndexEntry 8 } 4030 ipv6ScopeZoneIndex9 OBJECT-TYPE 4031 SYNTAX InetZoneIndex 4032 MAX-ACCESS read-only 4033 STATUS current 4034 DESCRIPTION 4035 "The zone index for scope 9 on this interface." 4036 ::= { ipv6ScopeZoneIndexEntry 9 } 4038 ipv6ScopeZoneIndexA OBJECT-TYPE 4039 SYNTAX InetZoneIndex 4040 MAX-ACCESS read-only 4041 STATUS current 4042 DESCRIPTION 4043 "The zone index for scope A on this interface." 4044 ::= { ipv6ScopeZoneIndexEntry 10 } 4046 ipv6ScopeZoneIndexB OBJECT-TYPE 4047 SYNTAX InetZoneIndex 4048 MAX-ACCESS read-only 4049 STATUS current 4050 DESCRIPTION 4051 "The zone index for scope B on this interface." 4052 ::= { ipv6ScopeZoneIndexEntry 11 } 4054 ipv6ScopeZoneIndexC OBJECT-TYPE 4055 SYNTAX InetZoneIndex 4056 MAX-ACCESS read-only 4057 STATUS current 4058 DESCRIPTION 4059 "The zone index for scope C on this interface." 4060 ::= { ipv6ScopeZoneIndexEntry 12 } 4062 ipv6ScopeZoneIndexD OBJECT-TYPE 4063 SYNTAX InetZoneIndex 4064 MAX-ACCESS read-only 4065 STATUS current 4066 DESCRIPTION 4067 "The zone index for scope D on this interface." 4068 ::= { ipv6ScopeZoneIndexEntry 13 } 4070 -- 4071 -- The Default Router Table 4072 -- This table simply lists the default routers, for more information 4073 -- about routing tables see the routing MIBs 4074 -- 4076 ipDefaultRouterTable OBJECT-TYPE 4077 SYNTAX SEQUENCE OF IpDefaultRouterEntry 4078 MAX-ACCESS not-accessible 4079 STATUS current 4080 DESCRIPTION 4081 "The table used to describe the default routers known to this 4082 entity." 4083 ::= { ip 37 } 4085 ipDefaultRouterEntry OBJECT-TYPE 4086 SYNTAX IpDefaultRouterEntry 4087 MAX-ACCESS not-accessible 4088 STATUS current 4089 DESCRIPTION 4090 "Each entry contains information about a default router known 4091 to this entity." 4092 INDEX {ipDefaultRouterAddressType, ipDefaultRouterAddress, 4093 ipDefaultRouterIfIndex} 4094 ::= { ipDefaultRouterTable 1 } 4096 IpDefaultRouterEntry ::= SEQUENCE { 4097 ipDefaultRouterAddressType InetAddressType, 4098 ipDefaultRouterAddress InetAddress, 4099 ipDefaultRouterIfIndex InterfaceIndex, 4100 ipDefaultRouterLifetime Unsigned32, 4101 ipDefaultRouterPreference INTEGER 4102 } 4104 ipDefaultRouterAddressType OBJECT-TYPE 4105 SYNTAX InetAddressType 4106 MAX-ACCESS not-accessible 4107 STATUS current 4108 DESCRIPTION 4109 "The address type for this row." 4110 ::= { ipDefaultRouterEntry 1 } 4112 ipDefaultRouterAddress OBJECT-TYPE 4113 SYNTAX InetAddress 4114 MAX-ACCESS not-accessible 4115 STATUS current 4116 DESCRIPTION 4117 "The IP address of the default router represented by this 4118 row. The address type of this object is specified in 4119 ipDefaultRouterAddressType. 4121 Implementers need to be aware that if the size of 4122 ipDefaultRouterAddress exceeds 115 octets then OIDS of 4123 instances of columns in this row will have more than 128 4124 sub-identifiers and cannot be accessed using SNMPv1, SNMPv2c 4125 or SNMPv3." 4126 ::= { ipDefaultRouterEntry 2 } 4128 ipDefaultRouterIfIndex OBJECT-TYPE 4129 SYNTAX InterfaceIndex 4130 MAX-ACCESS not-accessible 4131 STATUS current 4132 DESCRIPTION 4133 "The index value which uniquely identifies the interface by 4134 which the router can be reached. The interface identified 4135 by a particular value of this index is the same interface as 4136 identified by the same value of the IF-MIB's ifIndex." 4137 ::= { ipDefaultRouterEntry 3 } 4139 ipDefaultRouterLifetime OBJECT-TYPE 4140 SYNTAX Unsigned32 (0..65535) 4141 UNITS "seconds" 4142 MAX-ACCESS read-only 4143 STATUS current 4144 DESCRIPTION 4145 "The remaining length of time, in seconds, that this router 4146 will continue to be useful as a default router. A value of 4147 zero indicates that it is no longer useful as a default 4148 router. It is left to the implementer of the MIB as to 4149 whether a router with a lifetime of zero is removed from the 4150 list. 4152 For IPv6 this value should be extracted from the router 4153 advertisement messages. " 4154 REFERENCE "For IPv6 RFC2462 sections 4.2 and 6.3.4" 4155 ::= { ipDefaultRouterEntry 4 } 4157 ipDefaultRouterPreference OBJECT-TYPE 4158 SYNTAX INTEGER { 4159 reserved (-2), 4160 low (-1), 4161 medium (0), 4162 high (1) 4163 } 4164 MAX-ACCESS read-only 4165 STATUS current 4166 DESCRIPTION 4167 "An indication of preference given to this router as a 4168 default router as described in [8]. Treating the value as a 4169 2 bit signed integer allows for simple arithmetic 4170 comparisons. 4172 For IPv4 routers or IPv6 routers that are not using the 4173 updated router advertisement format this object is set to 4174 medium (0). " 4175 REFERENCE "draft-ietf-ipv6-router-selection-02.txt, section 2.1" 4176 -- RFC Editor 4177 -- Please update this reference as the RFC number is assigned. 4178 -- 4180 ::= { ipDefaultRouterEntry 5 } 4182 -- 4183 -- Configuration information for constructing router advertisements 4184 -- 4186 ipv6RouterAdvertSpinLock OBJECT-TYPE 4187 SYNTAX TestAndIncr 4188 MAX-ACCESS read-write 4189 STATUS current 4190 DESCRIPTION 4191 "An advisory lock used to allow cooperating SNMP managers to 4192 coordinate their use of the set operation in creating or 4193 modifying rows within this table. 4195 In order to use this lock to coordinate the use of set 4196 operations managers should first retrieve 4197 ipv6RouterAdvertSpinLock. They should then determine the 4198 appropriate row to create or modify. Finally they should 4199 issue the appropriate set command including the retrieved 4200 value of ipv6RouterAdvertSpinLock. If another manager has 4201 altered the table in the meantime, then the value of 4202 ipv6RouterAdvertSpinLock will have changed and the creation 4203 will fail as it will be specifying an incorrect value for 4204 ipv6RouterAdvertSpinLock. It is suggested, but not 4205 required, that the ipv6RouterAdvertSpinLock be the first var 4206 bind for each set of objects representing a 'row' in a PDU. 4207 " 4208 ::= { ip 38 } 4210 ipv6RouterAdvertTable OBJECT-TYPE 4211 SYNTAX SEQUENCE OF Ipv6RouterAdvertEntry 4212 MAX-ACCESS not-accessible 4213 STATUS current 4214 DESCRIPTION 4215 "The table containing information used to construct router 4216 advertisements." 4217 ::= { ip 39 } 4219 ipv6RouterAdvertEntry OBJECT-TYPE 4220 SYNTAX Ipv6RouterAdvertEntry 4221 MAX-ACCESS not-accessible 4222 STATUS current 4223 DESCRIPTION 4224 "An entry containing information used to construct router 4225 advertisements. 4227 Information in this table is persistent and when this object 4228 is written the entity SHOULD save the change to non-volatile 4229 storage." 4230 INDEX { ipv6RouterAdvertIfIndex } 4231 ::= { ipv6RouterAdvertTable 1 } 4233 Ipv6RouterAdvertEntry ::= SEQUENCE { 4234 ipv6RouterAdvertIfIndex InterfaceIndex, 4235 ipv6RouterAdvertSendAdverts TruthValue, 4236 ipv6RouterAdvertMaxInterval Unsigned32, 4237 ipv6RouterAdvertMinInterval Unsigned32, 4238 ipv6RouterAdvertManagedFlag TruthValue, 4239 ipv6RouterAdvertOtherConfigFlag TruthValue, 4240 ipv6RouterAdvertLinkMTU Unsigned32, 4241 ipv6RouterAdvertReachableTime Unsigned32, 4242 ipv6RouterAdvertRetransmitTime Unsigned32, 4243 ipv6RouterAdvertCurHopLimit Unsigned32, 4244 ipv6RouterAdvertDefaultLifetime Unsigned32, 4245 ipv6RouterAdvertRowStatus RowStatus 4246 } 4248 ipv6RouterAdvertIfIndex OBJECT-TYPE 4249 SYNTAX InterfaceIndex 4250 MAX-ACCESS not-accessible 4251 STATUS current 4252 DESCRIPTION 4253 "The index value which uniquely identifies the interface on 4254 which router advertisements constructed with this 4255 information will be transmitted. The interface identified 4256 by a particular value of this index is the same interface as 4257 identified by the same value of the IF-MIB's ifIndex." 4258 ::= { ipv6RouterAdvertEntry 1 } 4260 ipv6RouterAdvertSendAdverts OBJECT-TYPE 4261 SYNTAX TruthValue 4262 MAX-ACCESS read-create 4263 STATUS current 4264 DESCRIPTION 4265 "A flag indicating whether or not the router sends periodic 4266 router advertisements and responds to router solicitations 4267 on this interface." 4268 REFERENCE "RFC2461 Section 6.2.1" 4269 DEFVAL { false } 4270 ::= { ipv6RouterAdvertEntry 2 } 4272 ipv6RouterAdvertMaxInterval OBJECT-TYPE 4273 SYNTAX Unsigned32 (4..1800) 4274 UNITS "seconds" 4275 MAX-ACCESS read-create 4276 STATUS current 4277 DESCRIPTION 4278 "The maximum time allowed between sending unsolicited router 4279 advertisements from this interface." 4280 REFERENCE "RFC2461 Section 6.2.1" 4281 DEFVAL { 600 } 4282 ::= { ipv6RouterAdvertEntry 3 } 4284 ipv6RouterAdvertMinInterval OBJECT-TYPE 4285 SYNTAX Unsigned32 (3..1350) 4286 UNITS "seconds" 4287 MAX-ACCESS read-create 4288 STATUS current 4289 DESCRIPTION 4290 "The minimum time allowed between sending unsolicited router 4291 advertisements from this interface. 4293 The default is 0.33 * ipv6RouterAdvertMaxInterval, however 4294 in the case of a low value for ipv6RouterAdvertMaxInterval 4295 the minimum value for this object is restricted to 3." 4296 REFERENCE "RFC2461 Section 6.2.1" 4297 ::= { ipv6RouterAdvertEntry 4 } 4299 ipv6RouterAdvertManagedFlag OBJECT-TYPE 4300 SYNTAX TruthValue 4301 MAX-ACCESS read-create 4302 STATUS current 4303 DESCRIPTION 4304 "The true/false value to be placed into the 'managed address 4305 configuration' flag field in router advertisements sent from 4306 this interface." 4307 REFERENCE "RFC2461 Section 6.2.1" 4308 DEFVAL { false } 4309 ::= { ipv6RouterAdvertEntry 5 } 4311 ipv6RouterAdvertOtherConfigFlag OBJECT-TYPE 4312 SYNTAX TruthValue 4313 MAX-ACCESS read-create 4314 STATUS current 4315 DESCRIPTION 4316 "The true/false value to be placed into the 'other stateful 4317 configuration' flag field in router advertisements sent from 4318 this interface." 4319 REFERENCE "RFC2461 Section 6.2.1" 4320 DEFVAL { false } 4321 ::= { ipv6RouterAdvertEntry 6 } 4323 ipv6RouterAdvertLinkMTU OBJECT-TYPE 4324 SYNTAX Unsigned32 4325 MAX-ACCESS read-create 4326 STATUS current 4327 DESCRIPTION 4328 "The value to be placed in MTU options sent by the router on 4329 this interface. 4331 A value of zero indicates that no MTU options are sent." 4332 REFERENCE "RFC2461 Section 6.2.1" 4333 DEFVAL { 0 } 4334 ::= { ipv6RouterAdvertEntry 7 } 4336 ipv6RouterAdvertReachableTime OBJECT-TYPE 4337 SYNTAX Unsigned32 (0..3600000) 4338 UNITS "milliseconds" 4339 MAX-ACCESS read-create 4340 STATUS current 4341 DESCRIPTION 4342 "The value to be placed in the reachable time field in router 4343 advertisement messages sent from this interface. 4345 A value of zero in the router advertisement indicates that 4346 the advertisement isn't specifying a value for reachable 4347 time." 4348 REFERENCE "RFC2461 Section 6.2.1" 4349 DEFVAL { 0 } 4350 ::= { ipv6RouterAdvertEntry 8 } 4352 ipv6RouterAdvertRetransmitTime OBJECT-TYPE 4353 SYNTAX Unsigned32 4354 UNITS "milliseconds" 4355 MAX-ACCESS read-create 4356 STATUS current 4357 DESCRIPTION 4358 "The value to be placed in the retransmit timer field in 4359 router advertisements sent from this interface. 4361 A value of zero in the router advertisement indicates that 4362 the advertisement isn't specifying a value for retrans 4363 time." 4364 REFERENCE "RFC2461 Section 6.2.1" 4365 DEFVAL { 0 } 4366 ::= { ipv6RouterAdvertEntry 9 } 4368 ipv6RouterAdvertCurHopLimit OBJECT-TYPE 4369 SYNTAX Unsigned32 (0..255) 4370 MAX-ACCESS read-create 4371 STATUS current 4372 DESCRIPTION 4373 "The default value to be placed in the current hop limit 4374 field in router advertisements sent from this interface. 4375 The value should be set to the current diameter of the 4376 Internet. 4378 A value of zero in the router advertisement indicates that 4379 the advertisement isn't specifying a value for curHopLimit. 4381 The default should be set to the value specified in the IANA 4382 web pages (www.iana.org) at the time of implementation." 4383 REFERENCE "RFC2461 Section 6.2.1" 4384 ::= { ipv6RouterAdvertEntry 10 } 4386 ipv6RouterAdvertDefaultLifetime OBJECT-TYPE 4387 SYNTAX Unsigned32 (0|4..9000) 4388 UNITS "seconds" 4389 MAX-ACCESS read-create 4390 STATUS current 4391 DESCRIPTION 4392 "The value to be placed in the router lifetime field of 4393 router advertisements sent from this interface. This value 4394 MUST be either 0 or between ipv6RouterAdvertMaxInterval and 4395 9000 seconds. 4397 A value of zero indicates that the router is not to be used 4398 as a default router. 4400 The default is 3 * ipv6RouterAdvertMaxInterval." 4401 REFERENCE "RFC2461 Section 6.2.1" 4402 ::= { ipv6RouterAdvertEntry 11 } 4404 ipv6RouterAdvertRowStatus OBJECT-TYPE 4405 SYNTAX RowStatus 4406 MAX-ACCESS read-create 4407 STATUS current 4408 DESCRIPTION 4409 "The status of this conceptual row. 4411 As all objects in this conceptual row have default values a 4412 row can be created and made active by setting this object 4413 appropriately. 4415 The RowStatus TC requires that this DESCRIPTION clause 4416 states under which circumstances other objects in this row 4417 can be modified. The value of this object has no effect on 4418 whether other objects in this conceptual row can be 4419 modified." 4420 ::= { ipv6RouterAdvertEntry 12 } 4422 -- 4423 -- ICMP section 4424 -- 4426 icmp OBJECT IDENTIFIER ::= { mib-2 5 } 4428 -- 4429 -- ICMP non-message-specific counters 4430 -- 4432 -- These object IDs are reserved as they were used in earlier drafts of 4433 -- the MIB module. In theory OIDs are not assigned until the specification 4434 -- is released as an RFC, however as some companies may have shipped 4435 -- code based on earlier versiosn of the MIB it seems best to reserve 4436 -- these OIDs. 4437 -- ::= { icmp 27 } 4438 -- ::= { icmp 28 } 4440 icmpStatsTable OBJECT-TYPE 4441 SYNTAX SEQUENCE OF IcmpStatsEntry 4442 MAX-ACCESS not-accessible 4443 STATUS current 4444 DESCRIPTION 4445 "The table of generic system-wide ICMP counters." 4446 ::= { icmp 29 } 4448 icmpStatsEntry OBJECT-TYPE 4449 SYNTAX IcmpStatsEntry 4450 MAX-ACCESS not-accessible 4451 STATUS current 4452 DESCRIPTION 4453 "A conceptual row in the icmpStatsTable." 4454 INDEX { icmpStatsIPVersion } 4455 ::= { icmpStatsTable 1 } 4457 IcmpStatsEntry ::= SEQUENCE { 4458 icmpStatsIPVersion InetVersion, 4459 icmpStatsInMsgs Counter32, 4460 icmpStatsInErrors Counter32, 4461 icmpStatsOutMsgs Counter32, 4462 icmpStatsOutErrors Counter32 4463 } 4465 icmpStatsIPVersion OBJECT-TYPE 4466 SYNTAX InetVersion 4467 MAX-ACCESS not-accessible 4468 STATUS current 4469 DESCRIPTION 4470 "The IP version of the statistics." 4471 ::= { icmpStatsEntry 1 } 4473 icmpStatsInMsgs OBJECT-TYPE 4474 SYNTAX Counter32 4475 MAX-ACCESS read-only 4476 STATUS current 4477 DESCRIPTION 4478 "The total number of ICMP messages which the entity received. 4479 Note that this counter includes all those counted by 4480 icmpStatsInErrors." 4481 ::= { icmpStatsEntry 2 } 4483 icmpStatsInErrors OBJECT-TYPE 4484 SYNTAX Counter32 4485 MAX-ACCESS read-only 4486 STATUS current 4487 DESCRIPTION 4488 "The number of ICMP messages which the entity received but 4489 determined as having ICMP-specific errors (bad ICMP 4490 checksums, bad length, etc.)." 4491 ::= { icmpStatsEntry 3 } 4493 icmpStatsOutMsgs OBJECT-TYPE 4494 SYNTAX Counter32 4495 MAX-ACCESS read-only 4496 STATUS current 4497 DESCRIPTION 4498 "The total number of ICMP messages which the entity attempted 4499 to send. Note that this counter includes all those counted 4500 by icmpStatsOutErrors." 4501 ::= { icmpStatsEntry 4 } 4503 icmpStatsOutErrors OBJECT-TYPE 4504 SYNTAX Counter32 4505 MAX-ACCESS read-only 4506 STATUS current 4507 DESCRIPTION 4508 "The number of ICMP messages which this entity did not send 4509 due to problems discovered within ICMP such as a lack of 4510 buffers. This value should not include errors discovered 4511 outside the ICMP layer such as the inability of IP to route 4512 the resultant datagram. In some implementations there may 4513 be no types of error which contribute to this counter's 4514 value." 4515 ::= { icmpStatsEntry 5 } 4517 -- 4518 -- per-version, per-message type ICMP counters 4519 -- 4520 icmpMsgStatsTable OBJECT-TYPE 4521 SYNTAX SEQUENCE OF IcmpMsgStatsEntry 4522 MAX-ACCESS not-accessible 4523 STATUS current 4524 DESCRIPTION 4525 "The table of system-wide per-version, per-message type ICMP 4526 counters." 4527 ::= { icmp 30 } 4529 icmpMsgStatsEntry OBJECT-TYPE 4530 SYNTAX IcmpMsgStatsEntry 4531 MAX-ACCESS not-accessible 4532 STATUS current 4533 DESCRIPTION 4534 "A conceptual row in the icmpMsgStatsTable. 4536 The system should track each ICMP type value, even if that 4537 ICMP type is not supported by the system." 4538 INDEX { icmpMsgStatsIPVersion, icmpMsgStatsType } 4539 ::= { icmpMsgStatsTable 1 } 4541 IcmpMsgStatsEntry ::= SEQUENCE { 4542 icmpMsgStatsIPVersion InetVersion, 4543 icmpMsgStatsType Integer32, 4544 icmpMsgStatsInPkts Counter32, 4545 icmpMsgStatsOutPkts Counter32 4546 } 4548 icmpMsgStatsIPVersion OBJECT-TYPE 4549 SYNTAX InetVersion 4550 MAX-ACCESS not-accessible 4551 STATUS current 4552 DESCRIPTION 4553 "The IP version of the statistics." 4554 ::= { icmpMsgStatsEntry 1 } 4556 icmpMsgStatsType OBJECT-TYPE 4557 SYNTAX Integer32 (0..255) 4558 MAX-ACCESS not-accessible 4559 STATUS current 4560 DESCRIPTION 4561 "The ICMP type field of the message type being counted by 4562 this row. 4564 Note that ICMP message types are scoped by the address type 4565 in use." 4566 REFERENCE "http://www.iana.org/assignments/icmp-parameters and 4567 > http://www.iana.org/assignments/icmpv6-parameters" 4568 ::= { icmpMsgStatsEntry 2 } 4570 icmpMsgStatsInPkts OBJECT-TYPE 4571 SYNTAX Counter32 4572 MAX-ACCESS read-only 4573 STATUS current 4574 DESCRIPTION 4575 "The number of input packets for this AF and type." 4576 ::= { icmpMsgStatsEntry 3 } 4578 icmpMsgStatsOutPkts OBJECT-TYPE 4579 SYNTAX Counter32 4580 MAX-ACCESS read-only 4581 STATUS current 4582 DESCRIPTION 4583 "The number of output packets for this AF and type." 4584 ::= { icmpMsgStatsEntry 4 } 4586 -- 4587 -- conformance information 4588 -- 4590 ipMIBConformance OBJECT IDENTIFIER ::= { ipMIB 2 } 4592 ipMIBCompliances OBJECT IDENTIFIER ::= { ipMIBConformance 1 } 4593 ipMIBGroups OBJECT IDENTIFIER ::= { ipMIBConformance 2 } 4595 -- compliance statements 4596 ipMIBCompliance2 MODULE-COMPLIANCE 4597 STATUS current 4598 DESCRIPTION 4599 "The compliance statement for systems which implement IP - 4600 either 4601 IPv4 or IPv6. 4603 There are a number of INDEX objects that cannot be represented 4604 in 4605 the form of OBJECT clauses in SMIv2, but for which we have the 4606 following compliance requirements, expressed in OBJECT clause 4607 form 4608 in this description clause: 4610 -- OBJECT ipSystemStatsIPVersion 4611 -- SYNTAX InetVersion {ipv4(1), ipv6(2)} 4612 -- DESCRIPTION 4613 -- This MIB requires support for only IPv4 and IPv6 4614 versions. 4615 -- 4616 -- OBJECT ipIfStatsIPVersion 4617 -- SYNTAX InetVersion {ipv4(1), ipv6(2)} 4618 -- DESCRIPTION 4619 -- This MIB requires support for only IPv4 and IPv6 4620 versions. 4621 -- 4622 -- OBJECT icmpStatsIPVersion 4623 -- SYNTAX InetVersion {ipv4(1), ipv6(2)} 4624 -- DESCRIPTION 4625 -- This MIB requires support for only IPv4 and IPv6 4626 versions. 4627 -- 4628 -- OBJECT icmpMsgStatsIPVersion 4629 -- SYNTAX InetVersion {ipv4(1), ipv6(2)} 4630 -- DESCRIPTION 4631 -- This MIB requires support for only IPv4 and IPv6 4632 versions. 4633 -- 4634 -- OBJECT ipAddressPrefixType 4635 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 4636 -- DESCRIPTION 4637 -- This MIB requires support for only global IPv4 and IPv6 4638 -- address types. 4639 -- 4640 -- OBJECT ipAddressPrefixPrefix 4641 -- SYNTAX InetAddress (Size(4 | 16)) 4642 -- DESCRIPTION 4643 -- This MIB requires support for only global IPv4 and IPv6 4644 -- address and so the size can be either 4 or 16 bytes. 4645 -- 4646 -- OBJECT ipAddressAddrType 4647 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), 4648 -- ipv4z(3), ipv6z(4)} 4649 -- DESCRIPTION 4650 -- This MIB requires support for only global and non-global 4651 -- IPv4 and IPv6 address types. 4652 -- 4653 -- OBJECT ipAddressAddr 4654 -- SYNTAX InetAddress (Size(4 | 8 | 16 | 20)) 4655 -- DESCRIPTION 4656 -- This MIB requires support for only global and non-global 4657 -- IPv4 and IPv6 address and so the size can be 4, 8 16 or 4658 -- 20 bytes. 4659 -- 4660 -- OBJECT ipNetToPhysicalNetAddressType 4661 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), 4662 -- ipv4z(3), ipv6z(4)} 4663 -- DESCRIPTION 4664 -- This MIB requires support for only global and non-global 4665 -- IPv4 and IPv6 address types. 4666 -- 4667 -- OBJECT ipNetToPhysicalNetAddress 4668 -- SYNTAX InetAddress (Size(4 | 8 | 16 | 20)) 4669 -- DESCRIPTION 4670 -- This MIB requires support for only global and non-global 4671 -- IPv4 and IPv6 address and so the size can be 4, 8 16 or 4672 -- 20 bytes. 4673 -- 4674 -- OBJECT ipDefaultRouterAddressType 4675 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), 4676 -- ipv4z(3), ipv6z(4)} 4677 -- DESCRIPTION 4678 -- This MIB requires support for only global and non-global 4679 -- IPv4 and IPv6 address types. 4680 -- 4681 -- OBJECT ipDefaultRouterAddress 4682 -- SYNTAX InetAddress (Size(4 | 8 | 16 | 20)) 4683 -- DESCRIPTION 4684 -- This MIB requires support for only global and non-global 4685 -- IPv4 and IPv6 address and so the size can be 4, 8 16 or 4686 -- 20 bytes. 4688 " 4690 MODULE -- this module 4692 MANDATORY-GROUPS { ipSystemStatsGroup, ipAddressGroup, 4693 ipNetToPhysicalGroup, ipDefaultRouterGroup, 4694 icmpStatsGroup } 4696 GROUP ipSystemStatsHCOctetGroup 4697 DESCRIPTION 4698 "This group is mandatory for systems that have an aggregate 4699 bandwidth greater than 20MB. Including this group does not 4700 allow an entity to neglect the 32 bit versions of these 4701 objects." 4703 GROUP ipSystemStatsHCPacketGroup 4704 DESCRIPTION 4705 "This group is mandatory for systems that have an aggregate 4706 bandwidth greater than 650MB. Including this group does not 4707 allow an entity to neglect the 32 bit versions of these 4708 objects." 4710 GROUP ipIfStatsGroup 4711 DESCRIPTION 4712 "This group is optional for all systems." 4714 GROUP ipIfStatsHCOctetGroup 4715 DESCRIPTION 4716 "This group is mandatory for systems that include the 4717 ipIfStatsGroup and include links with bandwidths greater 4718 than 20MB. Including this group does not allow an entity to 4719 neglect the 32 bit versions of these objects." 4721 GROUP ipIfStatsHCPacketGroup 4722 DESCRIPTION 4723 "This group is mandatory for systems that include the 4724 ipIfStatsGroup and include links with bandwidths greater 4725 than 650MB. Including this group does not allow an entity 4726 to neglect the 32 bit versions of these objects." 4728 GROUP ipv4GeneralGroup 4729 DESCRIPTION 4730 "This group is mandatory for all systems supporting IPv4." 4732 GROUP ipv4IfGroup 4733 DESCRIPTION 4734 "This group is mandatory for all systems supporting IPv4." 4736 GROUP ipv4SystemStatsGroup 4737 DESCRIPTION 4738 "This group is mandatory for all systems supporting IPv4." 4740 GROUP ipv4SystemStatsHCPacketGroup 4741 DESCRIPTION 4742 "This group is mandatory for all systems supporting IPv4 and 4743 that have an aggregate bandwidth greater than 650MB. 4744 Including this group does not allow an entity to neglect the 4745 32 bit versions of these objects." 4747 GROUP ipv4IfStatsGroup 4748 DESCRIPTION 4749 "This group is mandatory for all systems supporting IPv4 and 4750 including the ipIfStatsGroup." 4752 GROUP ipv4IfStatsHCPacketGroup 4753 DESCRIPTION 4754 "This group is mandatory for all systems supporting IPv4 and 4755 including the ipIfStatsHCPacketGroup. Including this group 4756 does not allow an entity to neglect the 32 bit versions of 4757 these objects." 4759 GROUP ipv6GeneralGroup2 4760 DESCRIPTION 4761 "This group is mandatory for all systems supporting IPv6." 4763 GROUP ipv6IfGroup 4764 DESCRIPTION 4765 "This group is mandatory for all systems supporting IPv6." 4767 GROUP ipAddressPrefixGroup 4768 DESCRIPTION 4769 "This group is mandatory for all systems supporting IPv6." 4771 GROUP ipv6ScopeGroup 4772 DESCRIPTION 4773 "This group is mandatory for all systems supporting IPv6." 4775 GROUP ipv6RouterAdvertGroup 4776 DESCRIPTION 4777 "This group is mandatory for all IPv6 routers." 4779 GROUP ipLastChangeGroup 4780 DESCRIPTION 4781 "This group is optional for all agents." 4783 OBJECT ipv6IpForwarding 4784 MIN-ACCESS read-only 4785 DESCRIPTION 4786 "An agent is not required to provide write access to this 4787 object" 4789 OBJECT ipv6IpDefaultHopLimit 4790 MIN-ACCESS read-only 4791 DESCRIPTION 4792 "An agent is not required to provide write access to this 4793 object" 4795 OBJECT ipv4InterfaceEnableStatus 4796 MIN-ACCESS read-only 4797 DESCRIPTION 4798 "An agent is not required to provide write access to this 4799 object" 4801 OBJECT ipv6InterfaceEnableStatus 4802 MIN-ACCESS read-only 4803 DESCRIPTION 4804 "An agent is not required to provide write access to this 4805 object" 4807 OBJECT ipv6InterfaceForwarding 4808 MIN-ACCESS read-only 4809 DESCRIPTION 4810 "An agent is not required to provide write access to this 4811 object" 4813 OBJECT ipAddressSpinLock 4814 MIN-ACCESS not-accessible 4815 DESCRIPTION 4816 "An agent is not required to provide write access to this 4817 object. However if an agent provides write access to any of 4818 the other objects in the ipAddressGroup it SHOULD provide 4819 write access to this object as well." 4821 OBJECT ipAddressIfIndex 4822 MIN-ACCESS read-only 4823 DESCRIPTION 4824 "An agent is not required to provide write or create access 4825 to this object." 4827 OBJECT ipAddressType 4828 MIN-ACCESS read-only 4829 DESCRIPTION 4830 "An agent is not required to provide write or create access 4831 to this object." 4833 OBJECT ipAddressStatus 4834 MIN-ACCESS read-only 4835 DESCRIPTION 4836 "An agent is not required to provide write or create access 4837 to this object." 4839 OBJECT ipAddressRowStatus 4840 SYNTAX RowStatus { active(1) } 4841 MIN-ACCESS read-only 4842 DESCRIPTION 4843 "An agent is not required to provide write or create access 4844 to this object." 4846 OBJECT ipAddressStorageType 4847 MIN-ACCESS read-only 4848 DESCRIPTION 4849 "An agent is not required to provide write or create access 4850 to this object. 4852 If an agent allows this object to be written or created it 4853 is not required to allow this object to be set to readOnly, 4854 permanent or nonVolatile." 4856 OBJECT ipNetToPhysicalPhysAddress 4857 MIN-ACCESS read-only 4858 DESCRIPTION 4859 "An agent is not required to provide write or create access 4860 to this object" 4862 OBJECT ipNetToPhysicalType 4863 MIN-ACCESS read-only 4864 DESCRIPTION 4865 "An agent is not required to provide write or create access 4866 to this object." 4868 OBJECT ipv6RouterAdvertSpinLock 4869 MIN-ACCESS read-only 4870 DESCRIPTION 4871 "An agent is not required to provide write access to this 4872 object. However if an agent provides write access to any of 4873 the other objects in the ipv6RouterAdvertGroup it SHOULD 4874 provide write access to this object as well." 4876 OBJECT ipv6RouterAdvertSendAdverts 4877 MIN-ACCESS read-only 4878 DESCRIPTION 4879 "An agent is not required to provide write access to this 4880 object." 4882 OBJECT ipv6RouterAdvertMaxInterval 4883 MIN-ACCESS read-only 4884 DESCRIPTION 4885 "An agent is not required to provide write access to this 4886 object." 4888 OBJECT ipv6RouterAdvertMinInterval 4889 MIN-ACCESS read-only 4890 DESCRIPTION 4891 "An agent is not required to provide write access to this 4892 object." 4894 OBJECT ipv6RouterAdvertManagedFlag 4895 MIN-ACCESS read-only 4896 DESCRIPTION 4897 "An agent is not required to provide write access to this 4898 object." 4900 OBJECT ipv6RouterAdvertOtherConfigFlag 4901 MIN-ACCESS read-only 4902 DESCRIPTION 4903 "An agent is not required to provide write access to this 4904 object." 4906 OBJECT ipv6RouterAdvertLinkMTU 4907 MIN-ACCESS read-only 4908 DESCRIPTION 4909 "An agent is not required to provide write access to this 4910 object." 4912 OBJECT ipv6RouterAdvertReachableTime 4913 MIN-ACCESS read-only 4914 DESCRIPTION 4915 "An agent is not required to provide write access to this 4916 object." 4918 OBJECT ipv6RouterAdvertRetransmitTime 4919 MIN-ACCESS read-only 4920 DESCRIPTION 4921 "An agent is not required to provide write access to this 4922 object." 4924 OBJECT ipv6RouterAdvertCurHopLimit 4925 MIN-ACCESS read-only 4926 DESCRIPTION 4927 "An agent is not required to provide write access to this 4928 object." 4930 OBJECT ipv6RouterAdvertDefaultLifetime 4931 MIN-ACCESS read-only 4932 DESCRIPTION 4933 "An agent is not required to provide write access to this 4934 object." 4936 OBJECT ipv6RouterAdvertRowStatus 4937 MIN-ACCESS read-only 4938 DESCRIPTION 4939 "An agent is not required to provide write or create access 4940 to this object." 4942 ::= { ipMIBCompliances 2 } 4944 -- units of conformance 4946 ipv4GeneralGroup OBJECT-GROUP 4947 OBJECTS { ipForwarding, ipDefaultTTL, ipReasmTimeout } 4948 STATUS current 4949 DESCRIPTION 4950 "The group of IPv4-specific objects for basic management of 4951 IPv4 entities." 4952 ::= { ipMIBGroups 3 } 4954 ipv4IfGroup OBJECT-GROUP 4955 OBJECTS { ipv4InterfaceReasmMaxSize, ipv4InterfaceEnableStatus, 4956 ipv4InterfaceRetransmitTime } 4957 STATUS current 4958 DESCRIPTION 4959 "The group of IPv4-specific objects for basic management of 4960 IPv4 interfaces." 4961 ::= { ipMIBGroups 4 } 4963 ipv6GeneralGroup2 OBJECT-GROUP 4964 OBJECTS { ipv6IpForwarding, ipv6IpDefaultHopLimit } 4965 STATUS current 4966 DESCRIPTION 4967 "The IPv6 group of objects providing for basic management of 4968 IPv6 entities." 4969 ::= { ipMIBGroups 5 } 4971 ipv6IfGroup OBJECT-GROUP 4972 OBJECTS { ipv6InterfaceReasmMaxSize, ipv6InterfaceIdentifier, 4973 ipv6InterfaceEnableStatus, ipv6InterfaceReachableTime, 4974 ipv6InterfaceRetransmitTime, ipv6InterfaceForwarding } 4975 STATUS current 4976 DESCRIPTION 4977 "The group of IPv6-specific objects for basic management of 4978 IPv6 interfaces." 4979 ::= { ipMIBGroups 6 } 4981 ipLastChangeGroup OBJECT-GROUP 4982 OBJECTS { ipv4InterfaceTableLastChange, ipv6InterfaceTableLastChange, 4983 ipIfStatsTableLastChange } 4984 STATUS current 4985 DESCRIPTION 4986 "The last change objects associated with this MIB. These 4987 objects are optional for all agents. They SHOULD be 4988 implemented on agents where it is possible to determine the 4989 proper values. Where it is not possible to determine the 4990 proper values, for example when the tables are split amongst 4991 several sub-agents using AgentX, the agent MUST NOT 4992 implement these objects to return an incorrect or static 4993 value." 4994 ::= { ipMIBGroups 7 } 4996 ipSystemStatsGroup OBJECT-GROUP 4997 OBJECTS { ipSystemStatsInReceives, ipSystemStatsInOctets, 4998 ipSystemStatsInHdrErrors, ipSystemStatsInNoRoutes, 4999 ipSystemStatsInAddrErrors, ipSystemStatsInUnknownProtos, 5000 ipSystemStatsInTruncatedPkts, ipSystemStatsInForwDatagrams, 5001 ipSystemStatsReasmReqds, ipSystemStatsReasmOKs, 5002 ipSystemStatsReasmFails, ipSystemStatsInDiscards, 5003 ipSystemStatsInDelivers, ipSystemStatsOutRequests, 5004 ipSystemStatsOutNoRoutes, ipSystemStatsOutForwDatagrams, 5005 ipSystemStatsOutDiscards, ipSystemStatsOutFragReqds, 5006 ipSystemStatsOutFragOKs, ipSystemStatsOutFragFails, 5007 ipSystemStatsOutFragCreates, ipSystemStatsOutTransmits, 5008 ipSystemStatsOutOctets, ipSystemStatsInMcastPkts, 5009 ipSystemStatsInMcastOctets, ipSystemStatsOutMcastPkts, 5010 ipSystemStatsOutMcastOctets, 5011 ipSystemStatsDiscontinuityTime, 5012 ipSystemStatsRefreshRate } 5013 STATUS current 5014 DESCRIPTION 5015 "IP system wide statistics." 5016 ::= { ipMIBGroups 8 } 5018 ipv4SystemStatsGroup OBJECT-GROUP 5019 OBJECTS { ipSystemStatsInBcastPkts, ipSystemStatsOutBcastPkts } 5020 STATUS current 5021 DESCRIPTION 5022 "IPv4 only System wide statistics." 5023 ::= { ipMIBGroups 9 } 5025 ipSystemStatsHCOctetGroup OBJECT-GROUP 5026 OBJECTS { ipSystemStatsHCInOctets, ipSystemStatsHCOutOctets, 5027 ipSystemStatsHCInMcastOctets, ipSystemStatsHCOutMcastOctets 5028 } 5029 STATUS current 5030 DESCRIPTION 5031 "IP system wide statistics for systems that may overflow the 5032 standard octet counters within 1 hour." 5033 ::= { ipMIBGroups 10 } 5035 ipSystemStatsHCPacketGroup OBJECT-GROUP 5036 OBJECTS { ipSystemStatsHCInReceives, 5037 ipSystemStatsHCInForwDatagrams, 5038 ipSystemStatsHCInDelivers, ipSystemStatsHCOutRequests, 5039 ipSystemStatsHCOutForwDatagrams, 5040 ipSystemStatsHCOutTransmits, 5041 ipSystemStatsHCInMcastPkts, ipSystemStatsHCOutMcastPkts 5042 } 5043 STATUS current 5044 DESCRIPTION 5045 "IP system wide statistics for systems that may overflow the 5046 standard packet counters within 1 hour." 5047 ::= { ipMIBGroups 11 } 5049 ipv4SystemStatsHCPacketGroup OBJECT-GROUP 5050 OBJECTS { ipSystemStatsHCInBcastPkts, ipSystemStatsHCOutBcastPkts } 5051 STATUS current 5052 DESCRIPTION 5053 "IPv4 only system wide statistics for systems that may 5054 overflow the standard packet counters within 1 hour." 5055 ::= { ipMIBGroups 12 } 5057 ipIfStatsGroup OBJECT-GROUP 5058 OBJECTS { ipIfStatsInReceives, ipIfStatsInOctets, 5059 ipIfStatsInHdrErrors, ipIfStatsInNoRoutes, 5060 ipIfStatsInAddrErrors, ipIfStatsInUnknownProtos, 5061 ipIfStatsInTruncatedPkts, ipIfStatsInForwDatagrams, 5062 ipIfStatsReasmReqds, ipIfStatsReasmOKs, 5063 ipIfStatsReasmFails, ipIfStatsInDiscards, 5064 ipIfStatsInDelivers, ipIfStatsOutRequests, 5065 ipIfStatsOutForwDatagrams, ipIfStatsOutDiscards, 5066 ipIfStatsOutFragReqds, ipIfStatsOutFragOKs, 5067 ipIfStatsOutFragFails, ipIfStatsOutFragCreates, 5068 ipIfStatsOutTransmits, ipIfStatsOutOctets, 5069 ipIfStatsInMcastPkts, ipIfStatsInMcastOctets, 5070 ipIfStatsOutMcastPkts, ipIfStatsOutMcastOctets, 5071 ipIfStatsDiscontinuityTime, ipIfStatsRefreshRate } 5072 STATUS current 5073 DESCRIPTION 5074 "IP per-interface statistics." 5075 ::= { ipMIBGroups 13 } 5077 ipv4IfStatsGroup OBJECT-GROUP 5078 OBJECTS { ipIfStatsInBcastPkts, ipIfStatsOutBcastPkts } 5079 STATUS current 5080 DESCRIPTION 5081 "IPv4 only per-interface statistics." 5082 ::= { ipMIBGroups 14 } 5084 ipIfStatsHCOctetGroup OBJECT-GROUP 5085 OBJECTS { ipIfStatsHCInOctets, ipIfStatsHCOutOctets, 5086 ipIfStatsHCInMcastOctets, ipIfStatsHCOutMcastOctets } 5087 STATUS current 5088 DESCRIPTION 5089 "IP per-interfaces statistics for systems that include 5090 interfaces that may overflow the may overflow the standard 5091 octet counters within 1 hour." 5092 ::= { ipMIBGroups 15 } 5094 ipIfStatsHCPacketGroup OBJECT-GROUP 5095 OBJECTS { ipIfStatsHCInReceives, ipIfStatsHCInForwDatagrams, 5096 ipIfStatsHCInDelivers, ipIfStatsHCOutRequests, 5097 ipIfStatsHCOutForwDatagrams, ipIfStatsHCOutTransmits, 5098 ipIfStatsHCInMcastPkts, ipIfStatsHCOutMcastPkts } 5100 STATUS current 5101 DESCRIPTION 5102 "IP per-interfaces statistics for systems that include 5103 interfaces that may overflow the standard packet counters 5104 within 1 hour." 5105 ::= { ipMIBGroups 16 } 5107 ipv4IfStatsHCPacketGroup OBJECT-GROUP 5108 OBJECTS { ipIfStatsHCInBcastPkts, ipIfStatsHCOutBcastPkts } 5109 STATUS current 5110 DESCRIPTION 5111 "IPv4 only per-interface statistics for systems that include 5112 interfaces that may overflow the standard packet counters 5113 within 1 hour." 5114 ::= { ipMIBGroups 17 } 5116 ipAddressPrefixGroup OBJECT-GROUP 5117 OBJECTS { ipAddressPrefixOrigin, 5118 ipAddressPrefixOnLinkFlag, 5119 ipAddressPrefixAutonomousFlag, 5120 ipAddressPrefixAdvPreferredLifetime, 5121 ipAddressPrefixAdvValidLifetime } 5122 STATUS current 5123 DESCRIPTION 5124 "The group of objects for providing information about address 5125 prefixes used by this node." 5126 ::= { ipMIBGroups 18 } 5128 ipAddressGroup OBJECT-GROUP 5129 OBJECTS { ipAddressSpinLock, ipAddressIfIndex, 5130 ipAddressType, ipAddressPrefix, 5131 ipAddressOrigin, ipAddressStatus, 5132 ipAddressCreated, ipAddressLastChanged, 5133 ipAddressRowStatus, ipAddressStorageType } 5134 STATUS current 5135 DESCRIPTION 5136 "The group of objects for providing information about the 5137 addresses relevant to this entity's interfaces." 5138 ::= { ipMIBGroups 19 } 5140 ipNetToPhysicalGroup OBJECT-GROUP 5141 OBJECTS { ipNetToPhysicalPhysAddress, ipNetToPhysicalLastUpdated, 5142 ipNetToPhysicalType, ipNetToPhysicalState, 5143 ipNetToPhysicalRowStatus } 5144 STATUS current 5145 DESCRIPTION 5146 "The group of objects for providing information about the 5147 mappings of network address to physical address known to 5148 this node." 5149 ::= { ipMIBGroups 20 } 5151 ipv6ScopeGroup OBJECT-GROUP 5152 OBJECTS { ipv6ScopeZoneIndexLinkLocal, ipv6ScopeZoneIndex3, 5153 ipv6ScopeZoneIndexAdminLocal, 5154 ipv6ScopeZoneIndexSiteLocal, 5155 ipv6ScopeZoneIndex6, ipv6ScopeZoneIndex7, 5156 ipv6ScopeZoneIndexOrganizationLocal, ipv6ScopeZoneIndex9, 5157 ipv6ScopeZoneIndexA, ipv6ScopeZoneIndexB, 5158 ipv6ScopeZoneIndexC, ipv6ScopeZoneIndexD } 5159 STATUS current 5160 DESCRIPTION 5161 "The group of objects for managing IPv6 scope zones." 5162 ::= { ipMIBGroups 21 } 5164 ipDefaultRouterGroup OBJECT-GROUP 5165 OBJECTS { ipDefaultRouterLifetime, ipDefaultRouterPreference } 5166 STATUS current 5167 DESCRIPTION 5168 "The group of objects for providing information about default 5169 routers known to this node." 5170 ::= { ipMIBGroups 22 } 5172 ipv6RouterAdvertGroup OBJECT-GROUP 5173 OBJECTS { ipv6RouterAdvertSpinLock, ipv6RouterAdvertSendAdverts, 5174 ipv6RouterAdvertMaxInterval, ipv6RouterAdvertMinInterval, 5175 ipv6RouterAdvertManagedFlag, 5176 ipv6RouterAdvertOtherConfigFlag, 5177 ipv6RouterAdvertLinkMTU, 5178 ipv6RouterAdvertReachableTime, 5179 ipv6RouterAdvertRetransmitTime, 5180 ipv6RouterAdvertCurHopLimit, 5181 ipv6RouterAdvertDefaultLifetime, ipv6RouterAdvertRowStatus 5182 } 5183 STATUS current 5184 DESCRIPTION 5185 "The group of objects for controlling information advertised 5186 by IPv6 routers." 5187 ::= { ipMIBGroups 23 } 5189 icmpStatsGroup OBJECT-GROUP 5190 OBJECTS {icmpStatsInMsgs, icmpStatsInErrors, 5191 icmpStatsOutMsgs, icmpStatsOutErrors, 5192 icmpMsgStatsInPkts, icmpMsgStatsOutPkts } 5193 STATUS current 5194 DESCRIPTION 5195 "The group of objects providing ICMP statistics." 5196 ::= { ipMIBGroups 24 } 5198 -- 5199 -- Deprecated objects 5200 -- 5202 ipInReceives OBJECT-TYPE 5203 SYNTAX Counter32 5204 MAX-ACCESS read-only 5205 STATUS deprecated 5206 DESCRIPTION 5207 "The total number of input datagrams received from 5208 interfaces, including those received in error. 5210 This object has been deprecated as a new IP version neutral 5211 table has been added. It is loosely replaced by 5212 ipSystemStatsInRecieves. " 5213 ::= { ip 3 } 5215 ipInHdrErrors OBJECT-TYPE 5216 SYNTAX Counter32 5217 MAX-ACCESS read-only 5218 STATUS deprecated 5219 DESCRIPTION 5220 "The number of input datagrams discarded due to errors in 5221 their IPv4 headers, including bad checksums, version number 5222 mismatch, other format errors, time-to-live exceeded, errors 5223 discovered in processing their IPv4 options, etc. 5225 This object has been deprecated as a new IP version neutral 5226 table has been added. It is loosely replaced by 5227 ipSystemStatsInHdrErrors." 5228 ::= { ip 4 } 5230 ipInAddrErrors OBJECT-TYPE 5231 SYNTAX Counter32 5232 MAX-ACCESS read-only 5233 STATUS deprecated 5234 DESCRIPTION 5235 "The number of input datagrams discarded because the IPv4 5236 address in their IPv4 header's destination field was not a 5237 valid address to be received at this entity. This count 5238 includes invalid addresses (e.g., 0.0.0.0) and addresses of 5239 unsupported Classes (e.g., Class E). For entities which are 5240 not IPv4 routers and therefore do not forward datagrams, 5241 this counter includes datagrams discarded because the 5242 destination address was not a local address. 5244 This object has been deprecated as a new IP version neutral 5245 table has been added. It is loosely replaced by 5246 ipSystemStatsInAddrErrors." 5247 ::= { ip 5 } 5249 ipForwDatagrams OBJECT-TYPE 5250 SYNTAX Counter32 5251 MAX-ACCESS read-only 5252 STATUS deprecated 5253 DESCRIPTION 5254 "The number of input datagrams for which this entity was not 5255 their final IPv4 destination, as a result of which an 5256 attempt was made to find a route to forward them to that 5257 final destination. In entities which do not act as IPv4 5258 routers, this counter will include only those packets which 5259 were Source-Routed via this entity, and the Source-Route 5260 option processing was successful. 5262 This object has been deprecated as a new IP version neutral 5263 table has been added. It is loosely replaced by 5264 ipSystemStatsInForwDatagrams. " 5265 ::= { ip 6 } 5267 ipInUnknownProtos OBJECT-TYPE 5268 SYNTAX Counter32 5269 MAX-ACCESS read-only 5270 STATUS deprecated 5271 DESCRIPTION 5272 "The number of locally-addressed datagrams received 5273 successfully but discarded because of an unknown or 5274 unsupported protocol. 5276 This object has been deprecated as a new IP version neutral 5277 table has been added. It is loosely replaced by 5278 ipSystemStatsInUnknownProtos. " 5279 ::= { ip 7 } 5281 ipInDiscards OBJECT-TYPE 5282 SYNTAX Counter32 5283 MAX-ACCESS read-only 5284 STATUS deprecated 5285 DESCRIPTION 5286 "The number of input IPv4 datagrams for which no problems 5287 were encountered to prevent their continued processing, but 5288 which were discarded (e.g., for lack of buffer space). Note 5289 that this counter does not include any datagrams discarded 5290 while awaiting re-assembly. 5292 This object has been deprecated as a new IP version neutral 5293 table has been added. It is loosely replaced by 5294 ipSystemStatsInDiscards. " 5295 ::= { ip 8 } 5297 ipInDelivers OBJECT-TYPE 5298 SYNTAX Counter32 5299 MAX-ACCESS read-only 5300 STATUS deprecated 5301 DESCRIPTION 5302 "The total number of input datagrams successfully delivered 5303 to IPv4 user-protocols (including ICMP). 5305 This object has been deprecated as a new IP version neutral 5306 table has been added. It is loosely replaced by 5307 ipSystemStatsIndelivers. " 5308 ::= { ip 9 } 5310 ipOutRequests OBJECT-TYPE 5311 SYNTAX Counter32 5312 MAX-ACCESS read-only 5313 STATUS deprecated 5314 DESCRIPTION 5315 "The total number of IPv4 datagrams which local IPv4 user 5316 protocols (including ICMP) supplied to IPv4 in requests for 5317 transmission. Note that this counter does not include any 5318 datagrams counted in ipForwDatagrams. 5320 This object has been deprecated as a new IP version neutral 5321 table has been added. It is loosely replaced by 5322 ipSystemStatsOutRequests. " 5323 ::= { ip 10 } 5325 ipOutDiscards OBJECT-TYPE 5326 SYNTAX Counter32 5327 MAX-ACCESS read-only 5328 STATUS deprecated 5329 DESCRIPTION 5330 "The number of output IPv4 datagrams for which no problem was 5331 encountered to prevent their transmission to their 5332 destination, but which were discarded (e.g., for lack of 5333 buffer space). Note that this counter would include 5334 datagrams counted in ipForwDatagrams if any such packets met 5335 this (discretionary) discard criterion. 5337 This object has been deprecated as a new IP version neutral 5338 table has been added. It is loosely replaced by 5339 ipSystemStatsOutDiscards. " 5340 ::= { ip 11 } 5342 ipOutNoRoutes OBJECT-TYPE 5343 SYNTAX Counter32 5344 MAX-ACCESS read-only 5345 STATUS deprecated 5346 DESCRIPTION 5347 "The number of IPv4 datagrams discarded because no route 5348 could be found to transmit them to their destination. Note 5349 that this counter includes any packets counted in 5350 ipForwDatagrams which meet this `no-route' criterion. Note 5351 that this includes any datagrams which a host cannot route 5352 because all of its default routers are down. 5354 This object has been deprecated as a new IP version neutral 5355 table has been added. It is loosely replaced by 5356 ipSystemStatsOutNoRoutes. " 5357 ::= { ip 12 } 5359 ipReasmReqds OBJECT-TYPE 5360 SYNTAX Counter32 5361 MAX-ACCESS read-only 5362 STATUS deprecated 5363 DESCRIPTION 5364 "The number of IPv4 fragments received which needed to be 5365 reassembled at this entity. 5367 This object has been deprecated as a new IP version neutral 5368 table has been added. It is loosely replaced by 5369 ipSystemStatsReasmReqds. " 5370 ::= { ip 14 } 5372 ipReasmOKs OBJECT-TYPE 5373 SYNTAX Counter32 5374 MAX-ACCESS read-only 5375 STATUS deprecated 5376 DESCRIPTION 5377 "The number of IPv4 datagrams successfully re-assembled. 5379 This object has been deprecated as a new IP version neutral 5380 table has been added. It is loosely replaced by 5381 ipSystemStatsReasmOKs. " 5382 ::= { ip 15 } 5384 ipReasmFails OBJECT-TYPE 5385 SYNTAX Counter32 5386 MAX-ACCESS read-only 5387 STATUS deprecated 5388 DESCRIPTION 5389 "The number of failures detected by the IPv4 re-assembly 5390 algorithm (for whatever reason: timed out, errors, etc). 5391 Note that this is not necessarily a count of discarded IPv4 5392 fragments since some algorithms (notably the algorithm in 5393 RFC 815) can lose track of the number of fragments by 5394 combining them as they are received. 5396 This object has been deprecated as a new IP version neutral 5397 table has been added. It is loosely replaced by 5398 ipSystemStatsReasmFails. " 5400 ::= { ip 16 } 5402 ipFragOKs OBJECT-TYPE 5403 SYNTAX Counter32 5404 MAX-ACCESS read-only 5405 STATUS deprecated 5406 DESCRIPTION 5407 "The number of IPv4 datagrams that have been successfully 5408 fragmented at this entity. 5410 This object has been deprecated as a new IP version neutral 5411 table has been added. It is loosely replaced by 5412 ipSystemStatsOutFragOKs. " 5413 ::= { ip 17 } 5415 ipFragFails OBJECT-TYPE 5416 SYNTAX Counter32 5417 MAX-ACCESS read-only 5418 STATUS deprecated 5419 DESCRIPTION 5420 "The number of IPv4 datagrams that have been discarded 5421 because they needed to be fragmented at this entity but 5422 could not be, e.g., because their Don't Fragment flag was 5423 set. 5425 This object has been deprecated as a new IP version neutral 5426 table has been added. It is loosely replaced by 5427 ipSystemStatsOutFragFails. " 5428 ::= { ip 18 } 5430 ipFragCreates OBJECT-TYPE 5431 SYNTAX Counter32 5432 MAX-ACCESS read-only 5433 STATUS deprecated 5434 DESCRIPTION 5435 "The number of IPv4 datagram fragments that have been 5436 generated as a result of fragmentation at this entity. 5438 This object has been deprecated as a new IP version neutral 5439 table has been added. It is loosely replaced by 5440 ipSystemStatsOutFragCreates. " 5441 ::= { ip 19 } 5443 ipRoutingDiscards OBJECT-TYPE 5444 SYNTAX Counter32 5445 MAX-ACCESS read-only 5446 STATUS deprecated 5447 DESCRIPTION 5448 "The number of routing entries which were chosen to be 5449 discarded even though they are valid. One possible reason 5450 for discarding such an entry could be to free-up buffer 5451 space for other routing entries. 5453 This object was defined in pre-IPv6 versions of the IP MIB. 5454 It was implicitly IPv4 only but the original specifications 5455 did not indicate this protocol restriction. In order to 5456 clarify the specifications this object has been deprecated 5457 and a similar, but more thoroughly clarified, object has 5458 been added to the IP-FORWARD-MIB." 5459 ::= { ip 23 } 5461 -- the deprecated IPv4 address table 5463 ipAddrTable OBJECT-TYPE 5464 SYNTAX SEQUENCE OF IpAddrEntry 5465 MAX-ACCESS not-accessible 5466 STATUS deprecated 5467 DESCRIPTION 5468 "The table of addressing information relevant to this 5469 entity's IPv4 addresses. 5471 This table has been deprecated as a new IP version neutral 5472 table has been added. It is loosely replaced by the 5473 ipAddressTable although several objects that weren't deemed 5474 useful weren't carried forward while another 5475 (ipAdEntReasmMaxSize) was moved to the ipv4InterfaceTable. 5476 " 5477 ::= { ip 20 } 5479 ipAddrEntry OBJECT-TYPE 5480 SYNTAX IpAddrEntry 5481 MAX-ACCESS not-accessible 5482 STATUS deprecated 5483 DESCRIPTION 5484 "The addressing information for one of this entity's IPv4 5485 addresses." 5486 INDEX { ipAdEntAddr } 5487 ::= { ipAddrTable 1 } 5489 IpAddrEntry ::= SEQUENCE { 5490 ipAdEntAddr IpAddress, 5491 ipAdEntIfIndex INTEGER, 5492 ipAdEntNetMask IpAddress, 5493 ipAdEntBcastAddr INTEGER, 5494 ipAdEntReasmMaxSize INTEGER 5496 } 5498 ipAdEntAddr OBJECT-TYPE 5499 SYNTAX IpAddress 5500 MAX-ACCESS read-only 5501 STATUS deprecated 5502 DESCRIPTION 5503 "The IPv4 address to which this entry's addressing 5504 information pertains." 5505 ::= { ipAddrEntry 1 } 5507 ipAdEntIfIndex OBJECT-TYPE 5508 SYNTAX INTEGER (1..2147483647) 5509 MAX-ACCESS read-only 5510 STATUS deprecated 5511 DESCRIPTION 5512 "The index value which uniquely identifies the interface to 5513 which this entry is applicable. The interface identified by 5514 a particular value of this index is the same interface as 5515 identified by the same value of the IF-MIB's ifIndex." 5516 ::= { ipAddrEntry 2 } 5518 ipAdEntNetMask OBJECT-TYPE 5519 SYNTAX IpAddress 5520 MAX-ACCESS read-only 5521 STATUS deprecated 5522 DESCRIPTION 5523 "The subnet mask associated with the IPv4 address of this 5524 entry. The value of the mask is an IPv4 address with all 5525 the network bits set to 1 and all the hosts bits set to 0." 5526 ::= { ipAddrEntry 3 } 5528 ipAdEntBcastAddr OBJECT-TYPE 5529 SYNTAX INTEGER (0..1) 5530 MAX-ACCESS read-only 5531 STATUS deprecated 5532 DESCRIPTION 5533 "The value of the least-significant bit in the IPv4 broadcast 5534 address used for sending datagrams on the (logical) 5535 interface associated with the IPv4 address of this entry. 5536 For example, when the Internet standard all-ones broadcast 5537 address is used, the value will be 1. This value applies to 5538 both the subnet and network broadcasts addresses used by the 5539 entity on this (logical) interface." 5540 ::= { ipAddrEntry 4 } 5542 ipAdEntReasmMaxSize OBJECT-TYPE 5543 SYNTAX INTEGER (0..65535) 5544 MAX-ACCESS read-only 5545 STATUS deprecated 5546 DESCRIPTION 5547 "The size of the largest IPv4 datagram which this entity can 5548 re-assemble from incoming IPv4 fragmented datagrams received 5549 on this interface." 5550 ::= { ipAddrEntry 5 } 5552 -- the deprecated IPv4 Address Translation table 5554 -- The Address Translation tables contain the IpAddress to 5555 -- "physical" address equivalences. Some interfaces do not 5556 -- use translation tables for determining address 5557 -- equivalences (e.g., DDN-X.25 has an algorithmic method); 5558 -- if all interfaces are of this type, then the Address 5559 -- Translation table is empty, i.e., has zero entries. 5561 ipNetToMediaTable OBJECT-TYPE 5562 SYNTAX SEQUENCE OF IpNetToMediaEntry 5563 MAX-ACCESS not-accessible 5564 STATUS deprecated 5565 DESCRIPTION 5566 "The IPv4 Address Translation table used for mapping from 5567 IPv4 addresses to physical addresses. 5569 This table has been deprecated as a new IP version neutral 5570 table has been added. It is loosely replaced by the 5571 ipNetToPhysicalTable. " 5572 ::= { ip 22 } 5574 ipNetToMediaEntry OBJECT-TYPE 5575 SYNTAX IpNetToMediaEntry 5576 MAX-ACCESS not-accessible 5577 STATUS deprecated 5578 DESCRIPTION 5579 "Each entry contains one IpAddress to `physical' address 5580 equivalence." 5581 INDEX { ipNetToMediaIfIndex, 5582 ipNetToMediaNetAddress } 5583 ::= { ipNetToMediaTable 1 } 5585 IpNetToMediaEntry ::= SEQUENCE { 5586 ipNetToMediaIfIndex INTEGER, 5587 ipNetToMediaPhysAddress PhysAddress, 5588 ipNetToMediaNetAddress IpAddress, 5589 ipNetToMediaType INTEGER 5590 } 5592 ipNetToMediaIfIndex OBJECT-TYPE 5593 SYNTAX INTEGER (1..2147483647) 5594 MAX-ACCESS read-create 5595 STATUS deprecated 5596 DESCRIPTION 5597 "The interface on which this entry's equivalence is 5598 effective. The interface identified by a particular value 5599 of this index is the same interface as identified by the 5600 same value of the IF-MIB's ifIndex. 5602 This object predates the rule limiting index objects to a 5603 max access value of 'not-accessible' and so continue to use 5604 a value of 'read-create'." 5605 ::= { ipNetToMediaEntry 1 } 5607 ipNetToMediaPhysAddress OBJECT-TYPE 5608 SYNTAX PhysAddress (SIZE(0..65535)) 5609 MAX-ACCESS read-create 5610 STATUS deprecated 5611 DESCRIPTION 5612 "The media-dependent `physical' address. This object should 5613 return 0 when this entry is in the 'incomplete' state. 5615 As the entries in this table are typically not persistent 5616 when this object is written the entity should not save the 5617 change to non-volatile storage. Note: a stronger 5618 requirement is not used because this object was previously 5619 defined." 5620 ::= { ipNetToMediaEntry 2 } 5622 ipNetToMediaNetAddress OBJECT-TYPE 5623 SYNTAX IpAddress 5624 MAX-ACCESS read-create 5625 STATUS deprecated 5626 DESCRIPTION 5627 "The IpAddress corresponding to the media-dependent 5628 `physical' address. 5630 This object predates the rule limiting index objects to a 5631 max access value of 'not-accessible' and so continue to use 5632 a value of 'read-create'." 5633 ::= { ipNetToMediaEntry 3 } 5635 ipNetToMediaType OBJECT-TYPE 5636 SYNTAX INTEGER { 5637 other(1), -- none of the following 5638 invalid(2), -- an invalidated mapping 5639 dynamic(3), 5640 static(4) 5641 } 5642 MAX-ACCESS read-create 5643 STATUS deprecated 5644 DESCRIPTION 5645 "The type of mapping. 5647 Setting this object to the value invalid(2) has the effect 5648 of invalidating the corresponding entry in the 5649 ipNetToMediaTable. That is, it effectively dis-associates 5650 the interface identified with said entry from the mapping 5651 identified with said entry. It is an implementation- 5652 specific matter as to whether the agent removes an 5653 invalidated entry from the table. Accordingly, management 5654 stations must be prepared to receive tabular information 5655 from agents that corresponds to entries not currently in 5656 use. Proper interpretation of such entries requires 5657 examination of the relevant ipNetToMediaType object. 5659 As the entries in this table are typically not persistent 5660 when this object is written the entity should not save the 5661 change to non-volatile storage. Note: a stronger 5662 requirement is not used because this object was previously 5663 defined." 5664 ::= { ipNetToMediaEntry 4 } 5666 -- the deprecated ICMP group 5668 icmpInMsgs OBJECT-TYPE 5669 SYNTAX Counter32 5670 MAX-ACCESS read-only 5671 STATUS deprecated 5672 DESCRIPTION 5673 "The total number of ICMP messages which the entity received. 5674 Note that this counter includes all those counted by 5675 icmpInErrors. 5677 This object has been deprecated as a new IP version neutral 5678 table has been added. It is loosely replaced by 5679 icmpStatsInMsgs. " 5680 ::= { icmp 1 } 5682 icmpInErrors OBJECT-TYPE 5683 SYNTAX Counter32 5684 MAX-ACCESS read-only 5685 STATUS deprecated 5686 DESCRIPTION 5687 "The number of ICMP messages which the entity received but 5688 determined as having ICMP-specific errors (bad ICMP 5689 checksums, bad length, etc.). 5691 This object has been deprecated as a new IP version neutral 5692 table has been added. It is loosely replaced by 5693 icmpStatsInErrors. " 5694 ::= { icmp 2 } 5696 icmpInDestUnreachs OBJECT-TYPE 5697 SYNTAX Counter32 5698 MAX-ACCESS read-only 5699 STATUS deprecated 5700 DESCRIPTION 5701 "The number of ICMP Destination Unreachable messages 5702 received. 5704 This object has been deprecated as a new IP version neutral 5705 table has been added. It is loosely replaced by a column in 5706 the icmpMsgStatsTable." 5707 ::= { icmp 3 } 5709 icmpInTimeExcds OBJECT-TYPE 5710 SYNTAX Counter32 5711 MAX-ACCESS read-only 5712 STATUS deprecated 5713 DESCRIPTION 5714 "The number of ICMP Time Exceeded messages received. 5716 This object has been deprecated as a new IP version neutral 5717 table has been added. It is loosely replaced by a column in 5718 the icmpMsgStatsTable." 5719 ::= { icmp 4 } 5721 icmpInParmProbs OBJECT-TYPE 5722 SYNTAX Counter32 5723 MAX-ACCESS read-only 5724 STATUS deprecated 5725 DESCRIPTION 5726 "The number of ICMP Parameter Problem messages received. 5728 This object has been deprecated as a new IP version neutral 5729 table has been added. It is loosely replaced by a column in 5730 the icmpMsgStatsTable." 5731 ::= { icmp 5 } 5733 icmpInSrcQuenchs OBJECT-TYPE 5734 SYNTAX Counter32 5735 MAX-ACCESS read-only 5736 STATUS deprecated 5737 DESCRIPTION 5738 "The number of ICMP Source Quench messages received. 5740 This object has been deprecated as a new IP version neutral 5741 table has been added. It is loosely replaced by a column in 5742 the icmpMsgStatsTable." 5743 ::= { icmp 6 } 5745 icmpInRedirects OBJECT-TYPE 5746 SYNTAX Counter32 5747 MAX-ACCESS read-only 5748 STATUS deprecated 5749 DESCRIPTION 5750 "The number of ICMP Redirect messages received. 5752 This object has been deprecated as a new IP version neutral 5753 table has been added. It is loosely replaced by a column in 5754 the icmpMsgStatsTable." 5755 ::= { icmp 7 } 5757 icmpInEchos OBJECT-TYPE 5758 SYNTAX Counter32 5759 MAX-ACCESS read-only 5760 STATUS deprecated 5761 DESCRIPTION 5762 "The number of ICMP Echo (request) messages received. 5764 This object has been deprecated as a new IP version neutral 5765 table has been added. It is loosely replaced by a column in 5766 the icmpMsgStatsTable." 5767 ::= { icmp 8 } 5769 icmpInEchoReps OBJECT-TYPE 5770 SYNTAX Counter32 5771 MAX-ACCESS read-only 5772 STATUS deprecated 5773 DESCRIPTION 5774 "The number of ICMP Echo Reply messages received. 5776 This object has been deprecated as a new IP version neutral 5777 table has been added. It is loosely replaced by a column in 5778 the icmpMsgStatsTable." 5779 ::= { icmp 9 } 5781 icmpInTimestamps OBJECT-TYPE 5782 SYNTAX Counter32 5783 MAX-ACCESS read-only 5784 STATUS deprecated 5785 DESCRIPTION 5786 "The number of ICMP Timestamp (request) messages received. 5788 This object has been deprecated as a new IP version neutral 5789 table has been added. It is loosely replaced by a column in 5790 the icmpMsgStatsTable." 5791 ::= { icmp 10 } 5793 icmpInTimestampReps OBJECT-TYPE 5794 SYNTAX Counter32 5795 MAX-ACCESS read-only 5796 STATUS deprecated 5797 DESCRIPTION 5798 "The number of ICMP Timestamp Reply messages received. 5800 This object has been deprecated as a new IP version neutral 5801 table has been added. It is loosely replaced by a column in 5802 the icmpMsgStatsTable." 5803 ::= { icmp 11 } 5805 icmpInAddrMasks OBJECT-TYPE 5806 SYNTAX Counter32 5807 MAX-ACCESS read-only 5808 STATUS deprecated 5809 DESCRIPTION 5810 "The number of ICMP Address Mask Request messages received. 5812 This object has been deprecated as a new IP version neutral 5813 table has been added. It is loosely replaced by a column in 5814 the icmpMsgStatsTable." 5815 ::= { icmp 12 } 5817 icmpInAddrMaskReps OBJECT-TYPE 5818 SYNTAX Counter32 5819 MAX-ACCESS read-only 5820 STATUS deprecated 5821 DESCRIPTION 5822 "The number of ICMP Address Mask Reply messages received. 5824 This object has been deprecated as a new IP version neutral 5825 table has been added. It is loosely replaced by a column in 5826 the icmpMsgStatsTable." 5827 ::= { icmp 13 } 5829 icmpOutMsgs OBJECT-TYPE 5830 SYNTAX Counter32 5831 MAX-ACCESS read-only 5832 STATUS deprecated 5833 DESCRIPTION 5834 "The total number of ICMP messages which this entity 5835 attempted to send. Note that this counter includes all 5836 those counted by icmpOutErrors. 5838 This object has been deprecated as a new IP version neutral 5839 table has been added. It is loosely replaced by 5840 icmpStatsOutMsgs." 5841 ::= { icmp 14 } 5843 icmpOutErrors OBJECT-TYPE 5844 SYNTAX Counter32 5845 MAX-ACCESS read-only 5846 STATUS deprecated 5847 DESCRIPTION 5848 "The number of ICMP messages which this entity did not send 5849 due to problems discovered within ICMP such as a lack of 5850 buffers. This value should not include errors discovered 5851 outside the ICMP layer such as the inability of IP to route 5852 the resultant datagram. In some implementations there may 5853 be no types of error which contribute to this counter's 5854 value. 5856 This object has been deprecated as a new IP version neutral 5857 table has been added. It is loosely replaced by 5858 icmpStatsOutErrors." 5859 ::= { icmp 15 } 5861 icmpOutDestUnreachs OBJECT-TYPE 5862 SYNTAX Counter32 5863 MAX-ACCESS read-only 5864 STATUS deprecated 5865 DESCRIPTION 5866 "The number of ICMP Destination Unreachable messages sent. 5868 This object has been deprecated as a new IP version neutral 5869 table has been added. It is loosely replaced by a column in 5870 the icmpMsgStatsTable." 5871 ::= { icmp 16 } 5873 icmpOutTimeExcds OBJECT-TYPE 5874 SYNTAX Counter32 5875 MAX-ACCESS read-only 5876 STATUS deprecated 5877 DESCRIPTION 5878 "The number of ICMP Time Exceeded messages sent. 5880 This object has been deprecated as a new IP version neutral 5881 table has been added. It is loosely replaced by a column in 5882 the icmpMsgStatsTable." 5883 ::= { icmp 17 } 5885 icmpOutParmProbs OBJECT-TYPE 5886 SYNTAX Counter32 5887 MAX-ACCESS read-only 5888 STATUS deprecated 5889 DESCRIPTION 5890 "The number of ICMP Parameter Problem messages sent. 5892 This object has been deprecated as a new IP version neutral 5893 table has been added. It is loosely replaced by a column in 5894 the icmpMsgStatsTable." 5895 ::= { icmp 18 } 5897 icmpOutSrcQuenchs OBJECT-TYPE 5898 SYNTAX Counter32 5899 MAX-ACCESS read-only 5900 STATUS deprecated 5901 DESCRIPTION 5902 "The number of ICMP Source Quench messages sent. 5904 This object has been deprecated as a new IP version neutral 5905 table has been added. It is loosely replaced by a column in 5906 the icmpMsgStatsTable." 5907 ::= { icmp 19 } 5909 icmpOutRedirects OBJECT-TYPE 5910 SYNTAX Counter32 5911 MAX-ACCESS read-only 5912 STATUS deprecated 5913 DESCRIPTION 5914 "The number of ICMP Redirect messages sent. For a host, this 5915 object will always be zero, since hosts do not send 5916 redirects. 5918 This object has been deprecated as a new IP version neutral 5919 table has been added. It is loosely replaced by a column in 5920 the icmpMsgStatsTable." 5921 ::= { icmp 20 } 5923 icmpOutEchos OBJECT-TYPE 5924 SYNTAX Counter32 5925 MAX-ACCESS read-only 5926 STATUS deprecated 5927 DESCRIPTION 5928 "The number of ICMP Echo (request) messages sent. 5930 This object has been deprecated as a new IP version neutral 5931 table has been added. It is loosely replaced by a column in 5932 the icmpMsgStatsTable." 5933 ::= { icmp 21 } 5935 icmpOutEchoReps OBJECT-TYPE 5936 SYNTAX Counter32 5937 MAX-ACCESS read-only 5938 STATUS deprecated 5939 DESCRIPTION 5940 "The number of ICMP Echo Reply messages sent. 5942 This object has been deprecated as a new IP version neutral 5943 table has been added. It is loosely replaced by a column in 5944 the icmpMsgStatsTable." 5945 ::= { icmp 22 } 5947 icmpOutTimestamps OBJECT-TYPE 5948 SYNTAX Counter32 5949 MAX-ACCESS read-only 5950 STATUS deprecated 5951 DESCRIPTION 5952 "The number of ICMP Timestamp (request) messages sent. 5954 This object has been deprecated as a new IP version neutral 5955 table has been added. It is loosely replaced by a column in 5956 the icmpMsgStatsTable." 5957 ::= { icmp 23 } 5959 icmpOutTimestampReps OBJECT-TYPE 5960 SYNTAX Counter32 5961 MAX-ACCESS read-only 5962 STATUS deprecated 5963 DESCRIPTION 5964 "The number of ICMP Timestamp Reply messages sent. 5966 This object has been deprecated as a new IP version neutral 5967 table has been added. It is loosely replaced by a column in 5968 the icmpMsgStatsTable." 5969 ::= { icmp 24 } 5971 icmpOutAddrMasks OBJECT-TYPE 5972 SYNTAX Counter32 5973 MAX-ACCESS read-only 5974 STATUS deprecated 5975 DESCRIPTION 5976 "The number of ICMP Address Mask Request messages sent. 5978 This object has been deprecated as a new IP version neutral 5979 table has been added. It is loosely replaced by a column in 5980 the icmpMsgStatsTable." 5981 ::= { icmp 25 } 5983 icmpOutAddrMaskReps OBJECT-TYPE 5984 SYNTAX Counter32 5985 MAX-ACCESS read-only 5986 STATUS deprecated 5987 DESCRIPTION 5988 "The number of ICMP Address Mask Reply messages sent. 5990 This object has been deprecated as a new IP version neutral 5991 table has been added. It is loosely replaced by a column in 5992 the icmpMsgStatsTable." 5993 ::= { icmp 26 } 5995 -- deprecated conformance information 5996 -- deprecated compliance statements 5998 ipMIBCompliance MODULE-COMPLIANCE 5999 STATUS deprecated 6000 DESCRIPTION 6001 "The compliance statement for systems which implement only 6002 IPv4. For version-independence, this compliance statement 6003 is deprecated in favor of ipMIBCompliance2." 6004 MODULE -- this module 6005 MANDATORY-GROUPS { ipGroup, 6006 icmpGroup } 6007 ::= { ipMIBCompliances 1 } 6009 -- deprecated units of conformance 6011 ipGroup OBJECT-GROUP 6012 OBJECTS { ipForwarding, ipDefaultTTL, ipInReceives, 6013 ipInHdrErrors, ipInAddrErrors, ipForwDatagrams, 6014 ipInUnknownProtos, ipInDiscards, ipInDelivers, 6015 ipOutRequests, ipOutDiscards, ipOutNoRoutes, 6016 ipReasmTimeout, ipReasmReqds, ipReasmOKs, 6017 ipReasmFails, ipFragOKs, ipFragFails, 6018 ipFragCreates, ipAdEntAddr, ipAdEntIfIndex, 6019 ipAdEntNetMask, ipAdEntBcastAddr, 6020 ipAdEntReasmMaxSize, 6021 ipNetToMediaIfIndex, ipNetToMediaPhysAddress, 6022 ipNetToMediaNetAddress, ipNetToMediaType, ipRoutingDiscards 6023 } 6024 STATUS deprecated 6025 DESCRIPTION 6026 "The ip group of objects providing for basic management of IP 6027 entities, exclusive of the management of IP routes. 6029 As part of the version independence this group has been 6030 deprecated. " 6031 ::= { ipMIBGroups 1 } 6033 icmpGroup OBJECT-GROUP 6034 OBJECTS { icmpInMsgs, icmpInErrors, 6035 icmpInDestUnreachs, icmpInTimeExcds, 6036 icmpInParmProbs, icmpInSrcQuenchs, 6037 icmpInRedirects, icmpInEchos, 6038 icmpInEchoReps, icmpInTimestamps, 6039 icmpInTimestampReps, icmpInAddrMasks, 6040 icmpInAddrMaskReps, icmpOutMsgs, 6041 icmpOutErrors, icmpOutDestUnreachs, 6042 icmpOutTimeExcds, icmpOutParmProbs, 6043 icmpOutSrcQuenchs, icmpOutRedirects, 6044 icmpOutEchos, icmpOutEchoReps, 6045 icmpOutTimestamps, icmpOutTimestampReps, 6046 icmpOutAddrMasks, icmpOutAddrMaskReps } 6047 STATUS deprecated 6048 DESCRIPTION 6049 "The icmp group of objects providing ICMP statistics. 6051 As part of the version independence this group has been 6052 deprecated. " 6053 ::= { ipMIBGroups 2 } 6055 END 6057 6. Previous Work 6059 This document contains objects modified from RFC 1213 [11], RFC 2011 6060 [12], RFC 2465 [13], and RFC 2466 [14]. 6062 7. References 6064 7.1. Normative 6065 [1] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 6066 and S. Waldbusser, "Structure of Management Information Version 2 6067 (SMIv2)", STD 58, RFC 2578, April 1999. 6069 [2] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 6070 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 6071 2579, April 1999. 6073 [3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 6074 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 6075 2580, April 1999. 6077 [4] Narten, T., E. Nordmark and W. Simpson, "Neighbor Discovery for IP 6078 Version 6 (IPv6)", RFC 2461, December 1998. 6080 [5] Thomson, S., T. Narten, "IPv6 Stateless Address Autoconfiguration", 6081 RFC 2462, December 1998. 6083 [6] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB", RFC 2863, 6084 June 2000. 6086 [7] Daniele, M., B. Haberman, S. Routhier, J. Schoenwaelder, "draft- 6087 ietf-ops-rfc3291bis-02.txt", RFC XXXX Month Year. 6088 -- RFC Editor 6089 -- Please update this reference as the RFC number is assigned 6090 -- 6092 [8] Draves, R. and R. Hinden, "draft-ietf-ipv6-router-selection-02.txt", 6093 June 2002. 6094 -- RFC Editor 6095 -- Please update this reference as the RFC number is assigned 6096 -- 6098 7.2. Informative 6100 [9] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 6101 Applicability Statements for Internet-Standard Management 6102 Framework", RFC 3410, December 2002. 6104 [10] D. Plummer, "An Ethernet Address Resolution Protocol", RFC0826, 6105 November 1982. 6107 [11] Rose, M. and K. McCloghrie, "Management Information Base for 6108 Network Management of TCP/IP-based internets", RFC 1213, March 6109 1991. 6111 [12] K. McCloghrie, "SNMPv2 Management Information Base for the Internet 6112 Protocol using SMIv2", RFC 2011, November 1996. 6114 [13] Haskin, D. and S. Onishi, "Management Information Base for IP 6115 Version 6: Textual Conventions and General Group", RFC 2465, 6116 December 1998. 6118 [14] Haskin, D. and S. Onishi, "Management Information Base for IP 6119 Version 6: ICMPv6 Group", RFC 2466, December 1998. 6121 [15] Narten, T. and R. Draves, "Privacy Extensions for Stateless Address 6122 Autoconfiguration in IPv6", RFC 3041, January 2001. 6124 [16] Haberman, B. and M. Wasserman, "draft-ietf- 6125 ipv6-rfc2096-update-05.txt", August 2003 6126 -- RFC Editor 6127 -- Please update this reference as the RFC numbers are assigned. 6128 -- 6130 [17] Hinden, R. and S. Deering, "draft-ietf-ipv6-addr-arch-v4-00.txt", 6131 October 9, 2003 6132 -- RFC Editor 6133 -- If the addressing architecture document preceeds this document as an 6134 -- RFC please update this reference. 6135 -- 6137 8. Security Considerations 6139 There are a number of management objects defined in this MIB module with 6140 a MAX-ACCESS clause of read-write and/or read-create. Such objects may 6141 be considered sensitive or vulnerable in some network environments. The 6142 support for SET operations in a non-secure environment without proper 6143 protection can have a negative effect on network operations. These are 6144 the tables and objects and their sensitivity/vulnerability: 6146 ipForwarding and ipv6IpForwarding - these objects allow a manager 6147 to enable or disable the routing functions on the entity. By 6148 disabling the routing functions an attacker would possibly be able 6149 to deny service to users. By enabling the routing functions an 6150 attacker could open a conduit into an area. This might result in 6151 the area providing transit for packets it shouldn't or allow the 6152 attacker access to the area bypassing security safeguards. 6154 ipDefaultTTL and ipv6IpDefaultHopLimit - these objects allow a 6155 manager to determine the diameter of the valid area for a packet. 6156 By decreasing the value of these objects an attacker could cause 6157 packets to be discarded before reaching their destinations. 6159 ipv4InterfaceEnableStatus and ipv6InterfaceEnableStatus - these 6160 objects allow a manager to enable or disable IPv4 and IPv6 on a 6161 specific interface. By enabling a protocol on an interface an 6162 attacker might be able to create an unsecured path into a node (or 6163 through it if routing is also enabled). By disabling a protocol on 6164 an interface an attacker might be able to force packets to be 6165 routed through some other interface or deny access to some or all 6166 of the network via that protocol. 6168 ipAddressTable - the objects in this table specify the addresses in 6169 use on this node. By modifying this information an attacker can 6170 cause a node to either ignore messages destined to it or accept (at 6171 least at the IP layer) messages it would otherwise ignore. The use 6172 of filtering or security associations may reduce the potential 6173 damage in the latter case. 6175 ipv6RouterAdvertTable - the objects in this table specify the 6176 information that a router should propagate in its routing 6177 advertisement messages. By modifying this information an attacker 6178 can interfere with the auto-configuration of all hosts on the link. 6179 Most modifications to this table will result in a denial of service 6180 to some or all hosts on the link. However two objects, 6181 ipv6RouterAdvertManagedFlag and ipv6RouterAdvertOtherConfigFlag, 6182 indicate if a host should acquire configuration information from 6183 some other source. By enabling these an attacker might be able to 6184 cause a host to retrieve its configuration information from a 6185 compromised source. 6187 ipNetToPhysicalPhysAddress and ipNetToPhysicalType - these objects 6188 specify information used to translate a network (IP) address into a 6189 media dependent address. By modifying these objects an attacker 6190 could disable communication with a node or divert messages from one 6191 node to another. However the attacker may be able to carry out a 6192 similar attack by simply responding to the ARP or ND requests made 6193 by the target node. 6195 Some of the readable objects in this MIB module (i.e., objects with a 6196 MAX-ACCESS other than not-accessible) may be considered sensitive or 6197 vulnerable in some network environments. It is thus important to 6198 control even GET access to these objects and possibly to even encrypt 6199 the values of these objects when sending them over the network via SNMP. 6201 These are the tables and objects and their sensitivity/vulnerability: 6203 Essentially all of the objects in this MIB could be considered 6204 sensitive as they report on the status of the IP modules within a 6205 system. However the ipSystemStatsTable, ipIfStatsTable and 6206 ipAddressTable are likely to be of most interest to an attacker. 6207 The statistics tables supply information about the quantity and 6208 type of traffic this node is processing and, especially for transit 6209 providers, may be considered sensitive. The address table provides 6210 a convenient list of all address in use by this node. Each address 6211 in isolation is unremarkable however the total list would allow an 6212 attacker to correlate otherwise unrelated traffic. For example an 6213 attacker might be able to correlate the a RFC 3041 [15] private 6214 address with known public addresses thus circumventing the 6215 intentions of RFC 3041. 6217 SNMP versions prior to SNMPv3 did not include adequate security. Even 6218 if the network itself is secure (for example by using IPSec), even then, 6219 there is no control as to who on the secure network is allowed to access 6220 and GET/SET (read/change/create/delete) the objects in this MIB module. 6222 It is RECOMMENDED that implementers consider the security features as 6223 provided by the SNMPv3 framework (see [9], section 8), including full 6224 support for the SNMPv3 cryptographic mechanisms (for authentication and 6225 privacy). 6227 Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. 6228 Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic 6229 security. It is then a customer/operator responsibility to ensure that 6230 the SNMP entity giving access to an instance of this MIB module, is 6231 properly configured to give access to the objects only to those 6232 principals (users) that have legitimate rights to indeed GET or SET 6233 (change/create/delete) them. 6235 9. Editor's Contact Information 6237 Shawn A. Routhier 6238 Wind River 6239 500 Wind River Way 6240 Alameda, CA 94501 6241 USA 6243 Email: shawn.routhier@windriver.com 6244 10. Authors 6246 This document was written by the IPv6 MIB revision design team: 6248 Bill Fenner, AT&T Labs -- Research 6249 Email: fenner@research.att.com 6251 Brian Haberman 6252 Email: brian@innovationslab.com 6254 Shawn A. Routhier, Wind River 6255 Email: shawn.routhier@windriver.com 6257 Dave Thaler, Microsoft 6258 Email: dthaler@windows.microsoft.com 6260 This document updates parts of the MIBs from several other documents. 6261 RFC2011 is the previous update to the IP MIB. RFC2465 and RFC2466 are 6262 the first versions specifying IPv6 addresses and information. 6264 RFC2011: 6265 Keith McCloghrie, Cisco Systems (Editor) 6267 RFC2465 and RFC2466: 6268 Dimitry Haskin, Bay Networks 6270 Steve Onishi, Bay Networks 6272 11. Acknowledgments 6274 Reviews and other contributions were made by: 6276 Dario Acornero, Cisco Systems 6278 Mike MacFaden, Riverstone 6280 Keith McCloghrie, Cisco Systems 6282 Juergen Schoenwalder, TU Braunschweig 6284 Margaret Wasserman, Wind River 6285 12. Intellectual Property Notice 6287 The IETF takes no position regarding the validity or scope of any 6288 intellectual property or other rights that might be claimed to pertain 6289 to the implementation or use of the technology described in this 6290 document or the extent to which any license under such rights might or 6291 might not be available; neither does it represent that it has made any 6292 effort to identify any such rights. Information on the IETF's 6293 procedures with respect to rights in standards-track and standards- 6294 related documentation can be found in BCP-11. Copies of claims of 6295 rights made available for publication and any assurances of licenses to 6296 be made available, or the result of an attempt made to obtain a general 6297 license or permission for the use of such proprietary rights by 6298 implementors or users of this specification can be obtained from the 6299 IETF Secretariat. 6301 The IETF invites any interested party to bring to its attention any 6302 copyrights, patents or patent applications, or other proprietary rights 6303 which may cover technology that may be required to practice this 6304 standard. Please address the information to the IETF Executive 6305 Director. 6307 13. Full Copyright Statement 6309 Copyright (C) The Internet Society (2004). All Rights Reserved. 6311 This document and translations of it may be copied and furnished to 6312 others, and derivative works that comment on or otherwise explain it or 6313 assist in its implementation may be prepared, copied, published and 6314 distributed, in whole or in part, without restriction of any kind, 6315 provided that the above copyright notice and this paragraph are included 6316 on all such copies and derivative works. However, this document itself 6317 may not be modified in any way, such as by removing the copyright notice 6318 or references to the Internet Society or other Internet organizations, 6319 except as needed for the purpose of developing Internet standards in 6320 which case the procedures for copyrights defined in the Internet 6321 Standards process must be followed, or as required to translate it into 6322 languages other than English. 6324 The limited permissions granted above are perpetual and will not be 6325 revoked by the Internet Society or its successors or assigns. 6327 This document and the information contained herein is provided on an "AS 6328 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 6329 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 6330 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 6331 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 6332 FITNESS FOR A PARTICULAR PURPOSE. 6334 14. RFC Editor Notes 6335 -- RFC Editor 6336 -- This section to be removed as well. 6338 This section contains notes to the RFC Editor and should be removed 6339 as the document is converted into an RFC. 6341 Most of the revision history section is to be removed. The sections to 6342 be removed include all of the specific changes to various iterations of 6343 the drafts and is indicated with a removal tag. 6345 In the module identity section of the MIB (beginning of section 5) 6346 the RFC number of this document must be added in the description field 6347 and the first revision field (replacing xxxx). 6349 In the reference section of object ipv6ScopeZoneIndexTable the reference 6350 needs to be updated to refer to the correct document if the address 6351 architecture document precedes this document as an RFC. 6353 In the references section of object ipDefaultRouterPreference the reference 6354 needs to be updated to refer to the correct document. 6356 In the references section (7) the references to 3291Bis, 2096Bis and 6357 the router selection RFC must be replaced with proper RFCs as those 6358 numbers are assigned. 6360 In the references section (7) the reference to 3513BIS should be replaced 6361 with a proper RFC if the address architecture document precedes this one 6362 as an RFC.