idnits 2.17.1 draft-ietf-ipv6-rfc2011-update-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 39 instances of too long lines in the document, the longest one being 7 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 188: '... makes the lastChange objects a SHOULD...' RFC 2119 keyword, line 334: '...us & ipv6InterfaceAdminStatus - SHOULD...' RFC 2119 keyword, line 342: '...s & inetNetToMediaType - SHOULD NOT be...' RFC 2119 keyword, line 1128: '... is written the entity SHOULD save the...' RFC 2119 keyword, line 1143: '... is written the entity SHOULD save the...' (20 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 3019 has weird spacing: '... used for o...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 2003) is 7528 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 5176, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 5179, 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) -- Obsolete informational reference (is this intentional?): RFC 2011 (ref. '11') (Obsoleted by RFC 4293) -- Obsolete informational reference (is this intentional?): RFC 2465 (ref. '12') (Obsoleted by RFC 4293, RFC 8096) -- Obsolete informational reference (is this intentional?): RFC 2466 (ref. '13') (Obsoleted by RFC 4293, RFC 8096) -- Obsolete informational reference (is this intentional?): RFC 3041 (ref. '14') (Obsoleted by RFC 4941) Summary: 7 errors (**), 0 flaws (~~), 5 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IPv6 MIB Revision Design Team Shawn A. Routhier, Editor 2 INTERNET-DRAFT Wind River 3 Expires: March 2004 September 2003 5 Management Information Base 6 for the Internet Protocol (IP) 7 draft-ietf-ipv6-rfc2011-update-04.txt 9 Status of this Document 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering Task 15 Force (IETF), its areas, and its working groups. Note that other groups 16 may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference material 21 or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This document is a product of the IPv6 MIB Revision Design Team. 30 Comments should be addressed to the authors, or the mailing list at 31 ipng@sunroof.eng.sun.com. 33 Copyright Notice 35 Copyright (C) The Internet Society (2003). All Rights Reserved. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) for 40 use with network management protocols in the Internet community. In 41 particular, it describes managed objects used for implementations of the 42 Internet Protocol (IP) in an IP version independent manner. This memo 43 obsoletes RFCs 2011, 2465 and 2466. 45 Table of Contents 47 1. The Internet-Standard Management Framework. . . . . . . . . . . . 2 48 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 2 49 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 50 3.1. Multi-Stack Implementations. . . . . . . . . . . . . . . . . . 10 51 3.2. Discussion of Tables and Groups. . . . . . . . . . . . . . . . 10 52 3.2.1. General Objects . . . . . . . . . . . . . . . . . . . . . . 11 53 3.2.2. Interface Tables. . . . . . . . . . . . . . . . . . . . . . 11 54 3.2.3. IP Statistics Tables. . . . . . . . . . . . . . . . . . . . 11 55 3.2.4. Internet Address Prefix Table . . . . . . . . . . . . . . . 14 56 3.2.5. Internet Address Table. . . . . . . . . . . . . . . . . . . 14 57 3.2.6. Internet Address Translation Table. . . . . . . . . . . . . 14 58 3.2.7. IPv6 Scope Zone Index . . . . . . . . . . . . . . . . . . . 15 59 3.2.8. Default Router Table. . . . . . . . . . . . . . . . . . . . 15 60 3.2.9. Router Advertisement Table. . . . . . . . . . . . . . . . . 15 61 3.2.10. ICMP Statistics Tables . . . . . . . . . . . . . . . . . . 15 62 3.2.11. Conformance and Compliance . . . . . . . . . . . . . . . . 16 63 3.2.12. Deprecated Objects . . . . . . . . . . . . . . . . . . . . 16 64 4. Updating Implementations. . . . . . . . . . . . . . . . . . . . . 16 65 4.1. Updating an implementation of the IPv4-only 66 IP-MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 67 4.2. Updating an implementation of the IPv6-MIB . . . . . . . . . . 18 68 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 69 6. Open Issues / To Do . . . . . . . . . . . . . . . . . . . . . . . 108 70 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 108 71 8. References. . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 72 8.1. Normative. . . . . . . . . . . . . . . . . . . . . . . . . . . 108 73 8.2. Informative. . . . . . . . . . . . . . . . . . . . . . . . . . 109 74 9. Security Considerations . . . . . . . . . . . . . . . . . . . . . 109 75 10. Editor's Contact Information . . . . . . . . . . . . . . . . . . 111 76 11. Authors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 77 12. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . 112 78 13. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 113 79 14. RFC Editor Notes . . . . . . . . . . . . . . . . . . . . . . . . 113 81 1. The Internet-Standard Management Framework 83 For a detailed overview of the documents that describe the current 84 Internet-Standard Management Framework, please refer to section 7 of RFC 85 3410 [8]. 87 Managed objects are accessed via a virtual information store, termed the 88 Management Information Base or MIB. MIB objects are generally accessed 89 through the Simple Network Management Protocol (SNMP). Objects in the 90 MIB are defined using the mechanisms defined in the Structure of 91 Management Information (SMI). This memo specifies a MIB module that is 92 compliant to the SMIv2, which is described in STD 58, RFC 2578 [1], STD 93 58, RFC 2579 [2] and STD 58, RFC 2580 [3]. 95 2. Revision History 97 One of the primary purposes of this revision of the IP MIB is to create 98 a single set of objects to describe and manage IP modules in an IP 99 version independent manner. Where RFCs 2465 and 2466 created a set of 100 objects independent from RFC2011 this document merges those three 101 documents into a single unified set of objects. The ipSystemStatsTable 102 and ipIfStatsTable tables are examples of updating objects to be 103 independent of IP version. Both of these tables contain counters to 104 reflect IP traffic statistics that originated in much earlier MIBs and 105 both include an IP address type in order to separate the information 106 based on IP version. 108 Another purpose of this document is to increase the manageability of a 109 node running IPv6 by adding new objects. Some of these tables, such as 110 ipDefaultRouterTable, may be useful on both IPv4 and IPv6 nodes while 111 others, such as ipv6RouterAdvertTable, are specific to a single 112 protocol. 114 The rest of this section will be removed when the draft is submitted for 115 approval as a RFC. 117 Changes from draft-ietf-ipv6-rfc2011-update-03.txt 119 September 2003 121 Deprecated the ipRoutingDiscards object and add some text to 122 describe why and that the new version specific object can be found 123 in the IP-FORWARD-MIB. 125 Modified the syntax for ipIfStatsIfIndex to be InterfaceIndex 126 instead of InterfaceIndexOrZero as we no longer need the capability 127 of using zero within the index. (The MIB originally used a zero 128 index to specify the system level statistics.) 130 Added a description clause to the ipAddressGroup object. 132 Added the ipLastChangeGroup to ipMIBComliance2 with a description 133 of optional. 135 Changed draft-ietf-ipngwg-addr-arch-v3-11.txt to RFC3513. 137 Changes from draft-ietf-ipv6-rfc2011-update-02.txt 138 June 2003 140 Removed the ipv4 and ipv6 only requirements on the 141 ipSystemStatsAFType and ipIfStatsAFType objects. Instead added a 142 pseudo compliance statement requiring only global ipv4 and ipv6 143 types for those two objects as well as inetIcmpAFType and 144 inetIcmpMsgAFType. 146 Added a pseudo compliance statement requiring only global ipv4 and 147 ipv6 types for ipAddressPrefixType. 149 Added a pseudo compliance statement requiring only global and non 150 global ipv4 and ipv6 types for ipAddressAddrType, 151 inetNetToMediaNetAddressType and ipDefaultRouterAFType 153 In response to a question about the size constraint on the various 154 InetAddress objects (0..36). I have decided to leave this as is 155 for now. The actually size will be one of 4, 8, 16 or 20 depending 156 on the type in use and the syntax could be reduced to cover those 157 sizes. However using such a small limit might require a new mib if 158 a new address type is added to the InetAddress MIB that uses a 159 larger size. 36 seems to be a reasonable compromise for allowing 160 possible growth but avoiding problems with index length 161 limitations. 163 May 2003 165 Restored ipRoutingDiscards to a current object from the deprecated 166 group per discussions with previous MIB authors. The argument to 167 move it to deprecated relied on the fact that it really belongs 168 with the routing group rather than the main IP group. However as 169 it already exists in the IP group and any router must contain the 170 IP group it is not reasonable to remove it and create a new object 171 in the routing area simply to adjust where the object is rooted in 172 the MIB tree. This object was placed in a new group 173 "ipRoutingGroup" and the group was made mandatory in order to mimic 174 the previous MIB. 176 Changed the text to use "address type" or "address types" instead 177 of "address family" or "address families" in order to avoid any 178 confusion with the term as used by IANA in the assignment of 179 address family numbers. 181 Added some text to the description of ipAddressTable to remind 182 users that link-local addresses must use the "ipv6z" type. 184 Changes from draft-ietf-ipv6-rfc2011-update-01.txt 186 February 2003 188 Added ipLastChangeGroup which makes the lastChange objects a SHOULD 189 for agents that have the proper values available. 191 Added normative references for IMPORTed mibs. 193 January 2003 195 Editorial cleanup. 197 Renamed the ipv4If entries to ipv4Interface in order to be similar 198 to the ipv6Interface entries. 200 Updated the SNMP boilerplate. 202 Updated the references to remove many SNMP specific entries and 203 split the remainder into normative and informative. 205 Updated the security considerations section. 207 Decided not to add the netmask or BcastAddr information from the 208 deprecated ipAddrTable into the new mib as there was no major 209 support for them. 211 Removed IPv6 conformance and compliance OIDs as they are no longer 212 in use. 214 Renamed ipv6Forwarding and ipv6DefaultHopLimit to ip6Forwarding and 215 ip6DefaultHopLimit and moved them from the IPv6 branch to the IP 216 branch, thus removing the last objects in the IPv6 branch. 218 Added ipv6RouterAdvertSpinLock and ipv6RouterAdvertRowStatus 220 Added ipv4IfTableLastChange, ipv6IfTableLastChange and 221 ipIfStatsTableLastChange. 223 Renumbered pretty much everything at the IP branch level in order 224 to rationalize things and fit in the new objects. 226 Changes from draft-ops-rfc2011-update-02.txt: 228 October 2002 230 Renumbered objects in groups that had objects removed from one 231 draft to another. As per SMI rules no objects that have been 232 published in an RFC have been renumbered. The affected areas are: 233 ipv6InterfaceTable, ipIfStatsTable, inetIcmpTable and 234 inetIcmpMsgTable 236 Split the ipIfStatsTable into two tables under a common OID. The 237 two tables are ipSystemStatsTable which contains system-wide 238 statistics and ipIfStatsTable which contains interface-specific 239 statistics. The same counters are available from both tables. 241 The compliance and conformance section was rebuilt. ipGroup2 was 242 renamed to ipv4GeneralGroup and ipReasmTimeout was added to it. 243 The following groups were created: ipv4IfGroup, ipv6Ifgroup, 244 ipSystemStatsGroup, ipSystemStatsHCOctetGroup, 245 ipSystemStatsHCPacketGroup, ipIfStatsGroup, ipIfStatsHCOctetGroup, 246 ipIfStatsHCPacketGroup, ipAddressPrefixGroup, ipAddressGroup, 247 ipNetToMediaGroup, ipDefaultRouterGroup, ipv6RouterAdvertGroup and 248 icmpGroup2. The compliance section allows a compliant agent to 249 provide read-only access to all of the nominally read-write 250 objects. 252 Many minor changes to deal with errors found from mib compilers. 254 Changed the indexing from inetNetToMediaEntry to use a local copy 255 of the ifIndex. 257 Import InetZoneIndex for use a a scope index. Previously this was 258 the ScopeIdentifier TC defined within this document. Also change 259 the naming convention for scopes to use index instead of 260 identifier. 262 Close several issues without changes: 264 Should we include an object or objects to express the capability of 265 an implementation with respect to items like extension headers for 266 IPv6. I have decided to not include such objects. I believe that 267 we should wait for some deployment experience to see if such 268 objects would be useful and to determine their proper granularity. 270 Are there other items that could be added to the ipv{4 6}IfTables 271 such as (for v4) directed broadcast, proxy arp, header compression, 272 broadcast address and arp cache timeout. As I receive only one 273 request for such objects I have not added them. 275 Is there a better SMI data type for the lifetime objects in the 276 ipAddressPrefixTable, ipDefaultRouterTable and 277 ipv6RouterAdvertTable. I don't think there is a better SMI data 278 type. We could generate some TCs for them (there are several 279 classes of lifetime) but I don't think that would be useful. 281 There was a note in the v6 interface table suggesting that some of 282 the objects could be removed. I think we have now removed all of 283 those objects and don't intend to remove more without comments. 285 Should the ipv6ScopeZoneIndexTable include associated objects to 286 provide a scope description similar to ipMRouteScopeNameString 287 (rfc2932)? 289 My current decision is to NOT add such an object or set of objects. 290 Should the ipv6AddressIfIdentifier be dropped? I think this 291 provides some utility in specifying the how addresses are formed 292 (at least some of them). There is also the further question of 293 moving the Ipv6AddressIfIdentifier TC somewhere else. I don't 294 think it is completely an EUI and therefore it should have a TC 295 somewhere other than the IF-MIB and here seems reasonable. 297 Any other objects from ipv6IfTable that we need? I don't think so. 299 Are there other possible sources for ipAddressPrefixOrigin? No 300 additions were suggested and no action was taken. 302 Changes from draft-ops-rfc2011-update-00.txt: 304 May 2002 306 Removed ipv6InterfaceEffectiveMtu and 307 ipv6InterfaceIdentifierLength. 309 Added text to ipAddressPrefixTable to describe its utility. 311 Added text to ipAddressTable to state that multicast addresses are 312 described in their own table(s). 314 Added ipv4IfAdminStatus and ipv6InterfaceAdminStatus. 316 Added text to ipAddressPrefixOrigin to describe that an address 317 becomes well known by assignment from IANA or the address 318 registries or by specification in a standards track RFC. 320 Added text to ipAddressOrigin to clarify the manual vs random 321 difference. 323 Added text to inetNetToMediaType to clarify the difference between 324 static and local. 326 Created textual conventions for the following IpAddressOrigin, 327 IpAddressStatus and IpAddressPrefixOrigin. 329 Added persistence information to all read-write and read-create 330 objects: 332 ipForwarding & ipDefaultTTL - should be persistent 334 ipv6Forwarding, ipv4AdminStatus & ipv6InterfaceAdminStatus - SHOULD 335 be persistent 337 ipv6InterfaceIdentifier - modified from RW to Read-only 339 ipNetToMediaPhysAddress & ipNetToMediaType - should not be 340 persistent 342 inetNetToMediaPhysAddress & inetNetToMediaType - SHOULD NOT be 343 persistent 345 Added text to specify that ifIndex objects (ipv4IfIndex, 346 ipv6InterfaceIfIndex, ipIfStatsIfIndex, ipAddressPrefixIfIndex, 347 ipAddressIfIndex and ipv6ScopeIdIfIndex) use the same indexes as 348 ifIndex. 350 Removed ifIndex and code from the descriptions of inetIcmpMsg{In 351 Out}Pkts. 353 Updated the text for the objects in the ipIfStatsTable. The new 354 text allows them to be either system wide or interface specific. 355 It also clarifies which interface should be used for some objects. 356 Finally descriptions were added to some newer objects. 358 Added ipIfStatsRefreshRate 360 Modified the author information. The main author list has been 361 moved to a section within the document and replaced on the front 362 page with the editor's name. The MIB contact information has been 363 modified. 365 Added text mentioning that ARP (RFC826) and ND (RFC2461) are the 366 two most likely ways of populating the Net to Media table. 368 Added a reference clause to inetIcmpMsgType pointing to the IANA 369 pages for ICMP and ICMPv6 parameters. 371 Added text mentioning that ipIfStatsInTooBigErrors is only valid 372 for IPv6 but that it should be instantiated for IPv4 as well. 374 Added text to the ipAddressPrefixTable and it's objects mentioning 375 that it isn't tuned for IPv4 and defaults to use for IPv4 376 addresses. 378 Added the ipAddressLastChanged object. 380 Added reference clauses to ipv6DefaultHopLimit and several objects 381 in the ipAddressPrefix table. I don't think that any other objects 382 that don't already have some text have something to reference. 384 Modified the IP statistics table. 386 ipIfStatsHCInUcastPkts became ipIfStatsHCInReceives 388 removed ipIfStatsInTooBigErrors and include those packets in 389 ipIfStatsOutFragFails 391 added ipIfStatsInForwDatagrams to count packets that we attempt to 392 forward 394 clarified the text in ipIfStatsOutForwDatagrams to make it clear 395 that "success" was related to the forwarding step and not the 396 transmission step 398 added ipIfStatsOutTransmits and ipIfStatsHCOutTransmits as counters 399 of the packets sent to the lower layers and pointed the OutOctet 400 counters to them 402 added ipIfStatsOutNoRoutes to count the number of locally generated 403 datagrams that couldn't be transmitted as no route was found 405 added ipIfStatsOutFragReqds to count the number of datagrams that 406 require fragmentation 408 Added text and a Case diagram describing the statistics table. 410 Added the ipAddressCreated object. 412 Removed ipIfStatsHCOutUcastPkts as HCOutTransmits replaces it. 414 Also re-arranged the statsTable sequence to try and group the 415 objects more rationally. 417 Added reachable and retransmit times to the ipv6InterfaceTable 419 Added Default router list. 421 Added router advertisement configuration table. 423 November 2001 424 Modified the ICMP message table to remove some indexes. The table 425 no longer tracks counters with per-interface or per-ICMP code 426 granularity. 428 12 Jul 2001 430 Changed to IPNG working group work item. 432 Removed mention of SIIT, since it's just for transition 434 Added lots of counters to ipIfStats table, and 435 ipIfStatsDiscontinuityTime 437 Changed ipAddressIfIndex and ScopeIdentifier to refer to IF-MIB 438 instead of RFC 2863 or RFC 2233 440 Removed text about agents supporting a subset of values from 441 ipv6Forwarding; this belongs in an AGENT-CAPABILITIES. 443 Un-deprecated ipReasmTimeout. XXX Do we need ipv6ReasmTimeout too? 444 I think not; RFC2460 seems to say that it's a constant 60 seconds. 446 Changes from first draft posted to v6mib mailing list: 448 23 Feb 2001 450 Added ipv4InterfaceTable 452 Added ipv6InterfaceTable 454 Added ipAddressPrefixTable and slightly reworked ipAddressTable 455 (nee inetAddressTable). 457 Deprecated ipMIBCompliance. Still need to finish updated ones. 459 Added copyright and table of contents. 461 7 Feb 2001 463 Renamed inetIfStats to ipIfStats 465 Added ipv6ScopeTable 467 Added ScopeIdentifier TC, which should be in INET-ADDRESS-MIB. 469 Added SIZE to inetAddrAddr and inetNetToMediaAddress 470 Wrote some boilerplate for multi-interface-or-system-wide counter 471 tables. 473 3. Overview 475 3.1. Multi-Stack Implementations 477 This MIB does not provide native support for implementations of multiple 478 stacks sharing the same address type. One option for supporting such 479 designs is to assign each stack within an address type to a separate 480 context. These contexts could then be selected based upon the community 481 string or context name, with the Entity MIB providing a method for 482 listing the supported contexts. 484 3.2. Discussion of Tables and Groups 486 This MIB is composed of a small number of discrete objects and a series 487 of tables meant to form the base for managing IPv4 and IPv6 entities. 489 While some of the objects are meant to be included in all entities some 490 of the objects are only conditionally mandatory. The unconditionally 491 mandatory objects are mostly counters for IP and ICMP statistics. The 492 conditionally mandatory objects fall into one of several groups: objects 493 for use in higher bandwidth situations, objects for use with IPv4, 494 objects for use with IPv6 and objects for use on IPv6 routers. In short 495 it is not expected that every entity will implement all of the objects 496 within this MIB. The reader should consult the conformance and 497 compliance section to determine which objects are appropriate for a 498 given entity. 500 3.2.1. General Objects 502 In both IPv4 and IPv6 there are only a small number of "knobs" for 503 controlling the general IP stack. Most controls will be in a more 504 specific setting, such as for controlling a router or TCP engine. 506 This MIB defines a total of three general knobs only two of which are 507 used for both IPv4 and IPv6. 509 Objects are included for both protocols to enable or disable forwarding 510 and to set limits on the lifetime of a packet (ttl or hop count). 512 The third knob, the timeout period for reassembling fragments, is only 513 defined for IPv4 as IPv6 specifies this value directly. 515 Each of group of objects is required when implementing their respective 516 protocols. 518 3.2.2. Interface Tables 520 This MIB includes a pair of tables to convey information about the IPv4 521 and IPv6 protocols that is interface specific. 523 Special note should be taken of the administrative status objects. 524 These are defined to allow each protocol to selectively enable or 525 disable interfaces. These objects can be used in conjunction with the 526 ifAdminStatus object to manipulate the interfaces as necessary. With 527 these three objects an interface may be enabled or disabled completely 528 as well as connected connected to the IPv4 stack, the IPv6 stack or both 529 stacks. Setting ifAdminStatus to "down" should not affect the protocol 530 specific status objects. 532 Each interface table is required when implementing their respective 533 protocols. 535 3.2.3. IP Statistics Tables 537 The IP statistics tables (ipSystemStatsTable and ipIfStatsTable) contain 538 objects to count the number of datagrams and octets that a given entity 539 has processed. Unlike the previous attempt this document uses a single 540 table for multiple address types. Typically the only two types of 541 interest are IPv4 and IPv6 however the table can support other types if 542 necessary. 544 The first table, ipSystemStatsTable, conveys system wide information. 545 (That is, the various counters are for all interfaces and not a specific 546 set of interfaces.) Its index is formed from a single sub-id that 547 represents the address type for which the statistics were counted. 549 The second table, ipIfStatsTable, conveys interface specific 550 information. Its index is formed from two sub-ids. The first 551 represents the address type (IPv4 and IPv6) and the interface within 552 that address type is represented by the second sub-id. 554 The two tables have a similar set of objects which are intended to count 555 the same things except for the difference in granularity. The object ID 556 "ipSystemStatsEntry.2" is reserved in order to align the object ids of 557 the counters in the first table with their counterparts in the second 558 table. 560 Two objects of note are *IfStatsDiscontinuityTime and 561 *IfStatsRefreshRate. These objects provide information about the row in 562 the table more than about the system itself. 564 The discontinuity object allows a management entity to determine if a 565 discontinuity event which would invalidate the management entities 566 understanding of the counters has occurred. The system being re- 567 initialized or the interface being cycled are possible examples of a 568 discontinuity event. 570 The refresh object allows a management entity to determine a proper 571 polling interval for the rest of the objects. 573 The following Case diagram represents the general ordering of the packet 574 counters. In order to avoid extra clutter the prefixes "ipSystemStats" 575 and "ipIfStats" have been removed from each of the counter names. 577 from from 578 interface upper 579 layers 580 V V 581 | | 582 + InReceives (1) + OutRequests 583 | | 584 | | 585 +->-+ InMcastPkts (1) | 586 | V | 587 +-<-+ | 588 | | 589 +->-+ InBcastPkts (1) | 590 | V | 591 +-<-+ | 592 | | 593 | | 594 +--> InHdrErrors +--> OutNoRoutes 595 | | 596 | | 597 +--> InTruncatedPkts | 598 | | 599 | | 600 +--> InAddrErrors | 601 | | 602 | | 603 +--> InDiscards (2) | 604 | | 605 | | 606 +--------+------->------+----->-----+----->-----+ 607 | InForwDatagrams | OutForwDatagrams | 608 | V +->-+ OutFragReqds 609 | InNoRoutes | | (packets) 610 / (local packet (3) | | 611 | IF is that of the address | +--> OutFragFails 612 | and may not be the receiving IF) | | (packets) 613 | | | 614 +->-+ ReasmReqds (fragments) +-<-+ OutFragCreates 615 | | | (fragments) 616 | | | 617 | +--> ReasmFails (fragments (4)) +->-+ OutMcastPkts (1) 618 | | | V 619 | | +-<-+ 620 +-<-+ ReasmOKs (reassembled packets) | 621 | +->-+ OutBcastPkts (1) 622 | | V 623 +--> InUnknownProtos +-<-+ 624 | | 625 | | 626 +--> InDiscards (2) +--> OutDiscards (2) 627 | | 628 | | 629 + InDelivers + OutTransmits (1) 630 | | 631 V V 632 to to 633 upper interface 634 layers 636 (1) The HC counters and octet counters are also found at these points 637 but have been left out for clarity. 639 (2) The discard counters may increment at any time in the processing 640 path. 642 (3) Local packets on the input side are counted on the interface 643 associated with their destination address, which may not be the 644 interface on which they were received. This requirement is caused by 645 the possibility of losing the original interface during processing, 646 especially re-assembly. 648 (4) Some re-assembly algorithms may lose track of the number of 649 fragments during processing and so some fragments may not be counted in 650 this object. 652 The objects in both tables are spread amongst several conformance groups 653 based on the bandwidth required to wrap the counters within an hour. 654 The base system group is mandatory for all entities. The other system 655 groups are optional depending on bandwidth. The interface specific- 656 groups are optional. 658 3.2.4. Internet Address Prefix Table 660 This table provides information about the prefixes that this entity is 661 using including their lifetimes. This table provides a convenient place 662 to which other tables that make use of prefixes, such as the 663 ipAddressTable, may point. By including this table the MIB can supply 664 the prefix information for all addresses yet minimize the amount of 665 duplication required in storing and accessing this data. This 666 arrangement also makes the relationship between addresses that have the 667 same prefix clear. 669 This table is required for IPv6 entities. 671 3.2.5. Internet Address Table 673 This table lists the IP addresses (both IPv4 and IPv6) used by this 674 entity. It also includes some basic information about how and when the 675 address was formed and last updated. This table allows a manager to 676 determine who a given entity thinks it is. 678 This table is required for all IP entities. 680 3.2.6. Internet Address Translation Table 682 This table provides a mapping between IP layer addresses and physical 683 addresses as would be formed by either ARP for IPv4 or the neighbor 684 discovery protocol for IPv6. 686 3.2.7. IPv6 Scope Zone Index 688 This table specifies the zone index to interface mapping. By examining 689 the table a manager can determine which groups of interfaces are within 690 a particular zone for a given scope. 692 The zone index information is only valid within a given entity, the 693 indexes used on one entity may not be comparable to those used on a 694 different entity. 696 This table is required for IPv6 entities. 698 3.2.8. Default Router Table 700 This table lists the default routers known to this entity. This table 701 is intended to be a simple list to display the information end nodes may 702 have been configured with or acquired through a simple system such as 703 IPv6 router advertisements. Managers attempting to view more 704 complicated routing information should examine the routing specific 705 tables from other MIBs. 707 This table is required for all entities. 709 3.2.9. Router Advertisement Table 711 This table contains the non-routing information that an IPv6 router 712 would use in constructing a router advertisement message. It does not 713 contain information about the prefixes or other routing specific 714 information that the router might advertise. The router should acquire 715 such information from either the routing tables or from some routing 716 table specific MIB. 718 This table is only required for IPv6 router entities. 720 3.2.10. ICMP Statistics Tables 722 There are two sets of statistics for ICMP. The first contains a simple 723 set of counter to track the number of ICMP messages and errors processed 724 by this entity. 726 The second supplies more detail about the ICMP messages processed by 727 this entity. Its index is formed from two sub-ids. The first 728 represents the address type (IPv4 and IPv6) and the particular message 729 type being counted is represented by the second sub-id. 731 Both of these tables are required for all entities. 733 3.2.11. Conformance and Compliance 735 This MIB contains several sets of objects. Some of these sets are 736 useful on all types of entities while others are only useful on a 737 limited subset of entities. The conformance section attempts to group 738 the objects into sets that may be discussed as units and the compliance 739 section then details which of these units are required in various 740 circumstances. 742 The circumstances used in the compliance section are implementing IPv4, 743 IPv6 or IPv6 router functions and having bandwidth less than 20MB, 744 between 20MB and 650MB or greater than 650MB. 746 3.2.12. Deprecated Objects 748 This MIB also includes a set of deprecated objects from pervious 749 iterations. They are included as part of the historical record. 751 4. Updating Implementations 753 There are several general classes of change that are required. 755 The first and most major change is that most of the previous objects 756 have different object ids and additional indexes to support the 757 possibility of different address types. The general counters for IP and 758 ICMP are examples of this. They have been moved to the 759 ipSystemStatsTable and inetIcmpMsgTable respectively. 761 The second change is the extension of all address objects to allow for 762 both IPv4 and IPv6 addresses and the addition of an address type object 763 to specify what address type is in use. 765 The third change is the addition of several new objects to the 766 replacement for a previously existing table such as inetNetToMedia. 768 The fourth change is the addition of completely new tables such as 769 ipIfStatsTable and ipDefaultRouterTable. The first is based on the 770 previous statistics groups while the second is completely new to this 771 MIB. 773 4.1. Updating an implementation of the IPv4-only IP-MIB 775 The somewhat more specific changes that are required for IPv4 follow. 776 Note well: this is not meant to be an exhaustive list and the reader 777 should examine the MIB for full details. 779 Several of the general objects (ipForwarding, ipDefaultTTL, 780 ipReasmTimeout) remain unchanged. 782 Most of the rest of the general objects were counters and have been 783 moved into the ipSystemStatsTable. The basic instrumentation should 784 remain the same though the object definitions should be checked for any 785 clarifications. If they aren't already in a structure putting the 786 counter variables in one would be useful. Several new objects have been 787 added to count additional items, instrumentation code must be added for 788 these objects. Finally the SNMP routines must be updated to handle the 789 new indexing. 791 In addition to the ipSystemStatsTable the MIB includes the 792 ipIfStatsTable. This table counts the same items as the system table 793 but does it on a per interface basis. It is optional and may be 794 ignored. If you decide to implement it you may wish to use the previous 795 instrumentation and arrange for the system statistics table to aggregate 796 the new interface level statistics. 798 The ipAddrTable has, loosely, been converted to the ipAddressTable. 799 While the general idea remains the same the ipAddressTable is 800 sufficiently different that writing new code may be easier than updating 801 old code. The primary difference is the addition of several new 802 objects. In addition the ipAdEntReasmMaxSize has been moved to another 803 table, ipv4InterfaceTable. As above the SNMP routines will need to be 804 updated to handle the new indexing. 806 The ipNetToMediaTable has been moved to the inetNetToMediaTable. These 807 tables are fairly similar and updating the old code may be 808 straightforward. As above the SNMP routines will need to be updated to 809 handle the new indexing. 811 Two new tables, ipv4InterfaceTable and ipDefaultRouterTable, are 812 required as well as several new ICMP counters. 814 Finally there are several tables that are required for IPv6 but are 815 optional for IPv4 that you may elect to implement. 817 4.2. Updating an implementation of the IPv6-MIB 819 The somewhat more specific changes that are required for IPv6 follow. 820 Note well: this is not meant to be an exhaustive list and the reader 821 should examine the MIB for full details. 823 Two of the general objects, ipv6Forwarding and ipv6DefaultHopLimit, have 824 been renamed and given new object identifiers within the ip branch but 825 are otherwise unchanged. The new names are ip6Forwarding and 826 ip6DefaultHopLimit. 828 While there is an ipv6InterfaceTable that contains some of the pieces 829 from the ipv6IfTable the two are somewhat different in concept. The 830 ipv6IfTable was meant to replicate the ifTable while the 831 ipv6InterfaceTable is meant to be an addition to the ifTable. As such 832 items that were duplicated between the ifTable and ipv6IfTable have been 833 removed and some new objects added. 835 The ipv6IfStatsTable most closely resembles the ipIfStatsTable with and 836 additional index for the address type and most of the instrumentation 837 should be re-usable. Some new objects have been added to the 838 ipIfStatsTable. As above the SNMP routines will need to be updated to 839 handle the new indexing. Finally the ipIfStatsTable is optional and may 840 be ignored. 842 The ipSystemStatsTable is effectively new, but it may be able to make 843 use of most of the instrumentation from the old ipv6IfStatsTable. As 844 with the IPv4 discussion one implementation strategy would be to count 845 the statistics for the ipIfStatsTable and aggregate them when queried 846 for this table. 848 The ipv6AddrPrefixTable is now the ipAddressPrefixTable. The new table 849 contains an extra object and the additional index required for IPv4 850 compatibility. As above the SNMP routines will need to be updated to 851 handle the new indexing. 853 The ipAddressTable is loosely based on the ipv6AddrTable but has changed 854 considerable with the addition of several new objects and the removal of 855 one of its indexes. 857 The IPv6 routing information (ipv6RouteNumber, ipv6DiscardedRoutes and 858 ipv6RouteTable) has been removed from this MIB. The replacements or 859 updates for this information is in the update to the IP Forwarding Table 860 MIB. 862 The ipv6NetToMediaTable has been converted to the inetNetToMediaTable. 863 The new table contains an extra object and the additional index required 864 for IPv4 compatibility. As above the SNMP routines will need to be 865 updated to handle the new indexing. 867 The ICMP tables have been substantially changed. The previous tables 868 required counting on a per-message and per-interface basis. The new 869 tables only require counting on a per-message per-protocol basis and 870 include an aggregate of all messages on a per-protocol basis. 872 In addition to the above several new tables have been added. Both the 873 ipv6ScopeZoneIndexTable and ipDefaultRouterTable are required on all 874 IPv6 entities. The ipv6RouterAdvertTable is only required on IPv6 875 routers. 877 5. Definitions 879 IP-MIB DEFINITIONS ::= BEGIN 881 IMPORTS 882 MODULE-IDENTITY, OBJECT-TYPE, 883 Integer32, Counter32, IpAddress, 884 mib-2, Unsigned32, Counter64 FROM SNMPv2-SMI 885 PhysAddress, TruthValue, 886 TimeStamp, RowPointer, 887 TEXTUAL-CONVENTION, TestAndIncr, 888 RowStatus FROM SNMPv2-TC 889 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 890 InetAddress, InetAddressType, 891 InetAddressPrefixLength, 892 InetZoneIndex FROM INET-ADDRESS-MIB 893 InterfaceIndex FROM IF-MIB; 895 ipMIB MODULE-IDENTITY 896 LAST-UPDATED "200309030000Z" 897 ORGANIZATION "IETF IPv6 MIB Revision Team" 898 CONTACT-INFO 899 "Editor: 900 Shawn A. Routhier 901 Wind River 902 500 Wind River Way 903 Alameda, CA 904 USA 906 Phone: +1 510 749 2095 907 EMail: " 908 DESCRIPTION 909 "The MIB module for managing IP and ICMP implementations, but 910 excluding their management of IP routes. 912 Copyright (C) The Internet Society (2003). This version of 913 this MIB module is part of RFC xxxx; see the RFC itself for 914 full legal notices." 915 REVISION "200309030000Z" 916 DESCRIPTION 917 "Update and clarify the IP version neutral revision as well 918 as add IPv6 objects for ND, default routers and router 919 advertisements." 920 REVISION "200107130000Z" 921 DESCRIPTION 922 "IP version neutral revision." 923 REVISION "9411010000Z" 924 DESCRIPTION 925 "Published separately as RFC 2011." 926 REVISION "9103310000Z" 927 DESCRIPTION 928 "The initial revision of this MIB module was part of MIB-II." 929 ::= { mib-2 48} 931 -- 932 -- The textual conventions we define and use in this MIB. 934 -- 936 IpAddressOrigin ::= TEXTUAL-CONVENTION 937 STATUS current 938 DESCRIPTION 939 "The origin of the address. 941 manual(2) indicates that the address was manually configured 942 to a specified address, e.g by user configuration. 944 wellknown(3) indicates an address constructed from a well- 945 known value, e.g. an IANA-assigned anycast address. 947 dhcp(4) indicates an address that was assigned to this 948 system by a DHCP server. 950 linklayer(5) indicates an address created by IPv6 stateless 951 auto-configuration. 953 random(6) indicates an address chosen by the system at 954 random, e.g. an IPv4 address within 169.254/16, or an RFC 955 3041 privacy address." 956 SYNTAX INTEGER { 957 other(1), 958 manual(2), 959 wellknown(3), 960 dhcp(4), 961 linklayer(5), 962 random(6) 963 } 965 IpAddressStatus ::= TEXTUAL-CONVENTION 966 STATUS current 967 DESCRIPTION 968 "The status of an address. Most of the states correspond to 969 states from the IPv6 Stateless Address Autoconfiguration 970 protocol [5]. 972 The preferred(1) state indicates that this is a valid 973 address that can appear as the destination or source address 974 of a packet. 976 The deprecated(2) state indicates that this is a valid but 977 deprecated address that should no longer be used as a source 978 address in new communications, but packets addressed to such 979 an address are processed as expected. 981 The invalid(3) state indicates that this is not valid 982 address which should not appear as the destination or source 983 address of a packet. 985 The inaccessible(4) state indicates that the address is not 986 accessible because the interface to which this address is 987 assigned is not operational. 989 The unknown(5) state indicates that the status can not be 990 determined for some reason. 992 The tentative(6) state indicates the uniqueness of the 993 address on the link is being verified. Addresses in this 994 state should not be used for general communication and 995 should only be used to determine the uniqueness of the 996 address. 998 The duplicate(7) state indicates the address has been 999 determined to be non-unique on the link and so must not be 1000 used. 1002 In the absence of other information, an IPv4 address is 1003 always preferred(1)." 1004 SYNTAX INTEGER { 1005 preferred(1), 1006 deprecated(2), 1007 invalid(3), 1008 inaccessible(4), 1009 unknown(5), 1010 tentative(6), 1011 duplicate(7) 1012 } 1014 IpAddressPrefixOrigin ::= TEXTUAL-CONVENTION 1015 STATUS current 1016 DESCRIPTION 1017 "The origin of this prefix. 1019 manual(2) indicates a prefix that was manually configured. 1021 wellknown(3) indicates a well-known prefix, e.g. 169.254/16 1022 for IPv4 auto-configuration or fe80::/10 for IPv6 link-local 1023 addresses. Well known prefixes may be assigned by IANA or 1024 the address registries or by specification in a standards 1025 track RFC. 1027 dhcp(4) indicates a prefix that was assigned by a DHCP 1028 server. 1030 routeradv(5) indicates a prefix learned from a router 1031 advertisement. 1033 Note: while IpAddressOrigin and IpAddressPrefixOrigin are 1034 similar they are not identical. The first defines how an 1035 address was created while the second defines how a prefix 1036 was found." 1037 SYNTAX INTEGER { 1038 other(1), 1039 manual(2), 1040 wellknown(3), 1041 dhcp(4), 1042 routeradv(5) 1043 } 1045 Ipv6AddressIfIdentifier ::= TEXTUAL-CONVENTION 1046 DISPLAY-HINT "2x:" 1047 STATUS current 1048 DESCRIPTION 1049 "This data type is used to model IPv6 address 1050 interface identifiers. This is a binary string 1051 of up to 8 octets in network byte-order." 1052 SYNTAX OCTET STRING (SIZE (0..8)) 1054 -- 1055 -- the IP general group 1056 -- some objects that affect all of IPv4 1057 -- 1059 ip OBJECT IDENTIFIER ::= { mib-2 4 } 1061 ipForwarding OBJECT-TYPE 1062 SYNTAX INTEGER { 1063 forwarding(1), -- acting as a router 1064 notForwarding(2) -- NOT acting as a router 1065 } 1066 MAX-ACCESS read-write 1067 STATUS current 1068 DESCRIPTION 1069 "The indication of whether this entity is acting as an IPv4 1070 router in respect to the forwarding of datagrams received 1071 by, but not addressed to, this entity. IPv4 routers forward 1072 datagrams. IPv4 hosts do not (except those source-routed 1073 via the host). 1075 When this object is written the entity should save the 1076 change to non-volatile storage and restore the object from 1077 non-volatile storage upon re-initialization of the system. 1079 Note: a stronger requirement is not used because this object 1080 was previously defined." 1081 ::= { ip 1 } 1083 ipDefaultTTL OBJECT-TYPE 1084 SYNTAX INTEGER (1..255) 1085 MAX-ACCESS read-write 1086 STATUS current 1087 DESCRIPTION 1088 "The default value inserted into the Time-To-Live field of 1089 the IPv4 header of datagrams originated at this entity, 1090 whenever a TTL value is not supplied by the transport layer 1091 protocol. 1093 When this object is written the entity should save the 1094 change to non-volatile storage and restore the object from 1095 non-volatile storage upon re-initialization of the system. 1096 Note: a stronger requirement is not used because this object 1097 was previously defined." 1098 ::= { ip 2 } 1100 ipReasmTimeout OBJECT-TYPE 1101 SYNTAX Integer32 1102 MAX-ACCESS read-only 1103 STATUS current 1104 DESCRIPTION 1105 "The maximum number of seconds which received fragments are 1106 held while they are awaiting reassembly at this entity." 1107 ::= { ip 13 } 1109 -- 1110 -- the IPv6 general group 1111 -- Some objects that affect all of IPv6 1112 -- 1114 ip6Forwarding OBJECT-TYPE 1115 SYNTAX INTEGER { 1116 forwarding(1), -- acting as a router 1117 notForwarding(2) -- NOT acting as a router 1118 } 1119 MAX-ACCESS read-write 1120 STATUS current 1121 DESCRIPTION 1122 "The indication of whether this entity is acting as an IPv6 1123 router in respect to the forwarding of datagrams received 1124 by, but not addressed to, this entity. IPv6 routers forward 1125 datagrams. IPv6 hosts do not (except those source-routed 1126 via the host). 1128 When this object is written the entity SHOULD save the 1129 change to non-volatile storage and restore the object from 1130 non-volatile storage upon re-initialization of the system." 1131 ::= { ip 25 } 1133 ip6DefaultHopLimit OBJECT-TYPE 1134 SYNTAX INTEGER (0..255) 1135 MAX-ACCESS read-write 1136 STATUS current 1137 DESCRIPTION 1138 "The default value inserted into the Hop Limit field of the 1139 IPv6 header of datagrams originated at this entity, whenever 1140 a Hop Limit value is not supplied by the transport layer 1141 protocol. 1143 When this object is written the entity SHOULD save the 1144 change to non-volatile storage and restore the object from 1145 non-volatile storage upon re-initialization of the system." 1146 REFERENCE "RFC2461 Section 6.3.2" 1147 ::= { ip 26 } 1149 -- 1150 -- IPv4 Interface Table 1151 -- 1153 ipv4IfTableLastChange OBJECT-TYPE 1154 SYNTAX TimeStamp 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The value of sysUpTime on the most recent occasion at which 1159 a row in the ipv4InterfaceTable was added or deleted or when 1160 an ipv4InterfaceReasmMaxSize or an ipv4InterfaceAdminStatus 1161 object was modified. 1163 If new objects are added to the ipv6InterfaceTable that 1164 require the ipv6InterfaceTableLastChange to be updated when 1165 they are modified they must specify that requirement in 1166 their description clause." 1167 ::= { ip 27 } 1169 ipv4InterfaceTable OBJECT-TYPE 1170 SYNTAX SEQUENCE OF Ipv4InterfaceEntry 1171 MAX-ACCESS not-accessible 1172 STATUS current 1173 DESCRIPTION 1174 "The table containing per-interface IPv4-specific 1175 information." 1177 ::= { ip 28 } 1179 ipv4InterfaceEntry OBJECT-TYPE 1180 SYNTAX Ipv4InterfaceEntry 1181 MAX-ACCESS not-accessible 1182 STATUS current 1183 DESCRIPTION 1184 "An entry containing IPv4-specific information for a specific 1185 interface." 1186 INDEX { ipv4InterfaceIfIndex } 1187 ::= { ipv4InterfaceTable 1 } 1189 Ipv4InterfaceEntry ::= SEQUENCE { 1190 ipv4InterfaceIfIndex InterfaceIndex, 1191 ipv4InterfaceReasmMaxSize Integer32, 1192 ipv4InterfaceAdminStatus INTEGER 1193 } 1195 ipv4InterfaceIfIndex OBJECT-TYPE 1196 SYNTAX InterfaceIndex 1197 MAX-ACCESS not-accessible 1198 STATUS current 1199 DESCRIPTION 1200 "The index value which uniquely identifies the interface to 1201 which this entry is applicable. The interface identified by 1202 a particular value of this index is the same interface as 1203 identified by the same value of the IF-MIB's ifIndex." 1204 ::= { ipv4InterfaceEntry 1 } 1206 ipv4InterfaceReasmMaxSize OBJECT-TYPE 1207 SYNTAX Integer32 (0..65535) 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "The size of the largest IPv4 datagram which this entity can 1212 re-assemble from incoming IPv4 fragmented datagrams received 1213 on this interface." 1214 ::= { ipv4InterfaceEntry 2 } 1216 ipv4InterfaceAdminStatus OBJECT-TYPE 1217 SYNTAX INTEGER { 1218 up(1), 1219 down(2) 1220 } 1221 MAX-ACCESS read-write 1222 STATUS current 1223 DESCRIPTION 1224 "The indication of whether IPv4 is enabled (up) or disabled 1225 (down) on this interface. This object does not affect the 1226 state of the interface itself, only its connection to an 1227 IPv4 stack. The IF-MIB should be used to control the state 1228 of the interface." 1229 ::= { ipv4InterfaceEntry 3 } 1231 -- 1232 -- v6 interface table 1233 -- 1235 ipv6IfTableLastChange OBJECT-TYPE 1236 SYNTAX TimeStamp 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "The value of sysUpTime on the most recent occasion at which 1241 a row in the ipv6InterfaceTable was added or deleted or when 1242 an ipv6InterfaceReasmMaxSize, ipv6InterfaceIdentifier, 1243 ipv6InterfacePhysicalAddress, ipv6InterfaceAdminStatus, 1244 ipv6InterfaceReachableTime or ipv6InterfaceRetransmitTime 1245 object was modified. 1247 If new objects are added to the ipv6InterfaceTable that 1248 require the ipv6InterfaceTableLastChange to be updated when 1249 they are modified they must specify that requirement in 1250 their description clause." 1251 ::= { ip 29 } 1253 ipv6InterfaceTable OBJECT-TYPE 1254 SYNTAX SEQUENCE OF Ipv6InterfaceEntry 1255 MAX-ACCESS not-accessible 1256 STATUS current 1257 DESCRIPTION 1258 "The table containing per-interface IPv6-specific 1259 information." 1260 ::= { ip 30 } 1262 ipv6InterfaceEntry OBJECT-TYPE 1263 SYNTAX Ipv6InterfaceEntry 1264 MAX-ACCESS not-accessible 1265 STATUS current 1266 DESCRIPTION 1267 "An entry containing IPv6-specific information for a given 1268 interface." 1269 INDEX { ipv6InterfaceIfIndex } 1270 ::= { ipv6InterfaceTable 1 } 1272 Ipv6InterfaceEntry ::= SEQUENCE { 1273 ipv6InterfaceIfIndex InterfaceIndex, 1274 ipv6InterfaceReasmMaxSize Unsigned32, 1275 ipv6InterfaceIdentifier Ipv6AddressIfIdentifier, 1276 ipv6InterfacePhysicalAddress PhysAddress, 1277 ipv6InterfaceAdminStatus INTEGER, 1278 ipv6InterfaceReachableTime Unsigned32, 1279 ipv6InterfaceRetransmitTime Unsigned32 1280 } 1282 ipv6InterfaceIfIndex OBJECT-TYPE 1283 SYNTAX InterfaceIndex 1284 MAX-ACCESS not-accessible 1285 STATUS current 1286 DESCRIPTION 1287 "The index value which uniquely identifies the interface to 1288 which this entry is applicable. The interface identified by 1289 a particular value of this index is the same interface as 1290 identified by the same value of the IF-MIB's ifIndex." 1291 ::= { ipv6InterfaceEntry 1 } 1293 ipv6InterfaceReasmMaxSize OBJECT-TYPE 1294 SYNTAX Unsigned32 (0..65535) 1295 UNITS "octets" 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "The size of the largest IPv6 datagram which this entity can 1300 re-assemble from incoming IPv6 fragmented datagrams received 1301 on this interface." 1302 ::= { ipv6InterfaceEntry 2 } 1304 ipv6InterfaceIdentifier OBJECT-TYPE 1305 SYNTAX Ipv6AddressIfIdentifier 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "The Interface Identifier for this interface that is (at 1310 least) unique on the link this interface is attached to. The 1311 Interface Identifier is combined with an address prefix to 1312 form an interface address. 1314 By default, the Interface Identifier is auto-configured 1315 according to the rules of the link type this interface is 1316 attached to." 1317 ::= { ipv6InterfaceEntry 3 } 1319 ipv6InterfacePhysicalAddress OBJECT-TYPE 1320 SYNTAX PhysAddress 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "The interface's physical address. For example, for an IPv6 1325 interface attached to an 802.x link, this object normally 1326 contains a MAC address. Note that in some cases this address 1327 may differ from the address of the interface's protocol sub- 1328 layer. The interface's media-specific MIB must define the 1329 bit and byte ordering and the format of the value of this 1330 object. For interfaces which do not have such an address 1331 (e.g., a serial line), this object should contain an octet 1332 string of zero length." 1333 ::= { ipv6InterfaceEntry 4 } 1335 ipv6InterfaceAdminStatus OBJECT-TYPE 1336 SYNTAX INTEGER { 1337 up(1), 1338 down(2) 1339 } 1340 MAX-ACCESS read-write 1341 STATUS current 1342 DESCRIPTION 1343 "The indication of whether IPv6 is enabled (up) or disabled 1344 (down) on this interface. This object does not affect the 1345 state of the interface itself, only its connection to an 1346 IPv6 stack. The IF-MIB should be used to control the state 1347 of the interface. 1349 When this object is written the entity SHOULD save the 1350 change to non-volatile storage and restore the object from 1351 non-volatile storage upon re-initialization of the system." 1352 ::= { ipv6InterfaceEntry 5 } 1354 ipv6InterfaceReachableTime OBJECT-TYPE 1355 SYNTAX Unsigned32 1356 UNITS "milliseconds" 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "The time a neighbor is considered reachable after receiving 1361 a reachability confirmation." 1362 REFERENCE "RFC2461, Section 6.3.2" 1363 ::= { ipv6InterfaceEntry 6 } 1365 ipv6InterfaceRetransmitTime OBJECT-TYPE 1366 SYNTAX Unsigned32 1367 UNITS "milliseconds" 1368 MAX-ACCESS read-only 1369 STATUS current 1370 DESCRIPTION 1371 "The time between retransmissions of Neighbor Solicitation 1372 messages to a neighbor when resolving the address or when 1373 probing the reachability of a neighbor." 1374 REFERENCE "RFC2461, Section 6.3.2" 1375 ::= { ipv6InterfaceEntry 7 } 1377 -- 1378 -- Per-Interface or System-Wide IP statistics. 1379 -- 1380 -- The following two tables, ipSystemStatsTable and ipIfStatsTable 1381 -- are intended to provide the same counters at different granularities. 1382 -- The ipSystemStatsTable provides system wide counters aggregating 1383 -- the traffic counters for all interfaces for a given address type. 1384 -- The ipIfStatsTable provides the same counters but for specific 1385 -- interfaces rather than as an aggregate. 1386 -- 1387 -- Note well: If a system provides both system-wide and interface-specific 1388 -- values the system-wide value may not be equal to the sum of the 1389 -- interface-specific values across all interfaces due to e.g. dynamic 1390 -- interface creation/deletion. 1392 ipTrafficStats OBJECT IDENTIFIER ::= { ip 31 } 1394 ipSystemStatsTable OBJECT-TYPE 1395 SYNTAX SEQUENCE OF IpSystemStatsEntry 1396 MAX-ACCESS not-accessible 1397 STATUS current 1398 DESCRIPTION 1399 "The table containing system wide, address type specific 1400 traffic statistics. This table and the ipIfStatsTable 1401 contain similar objects whose difference is in their 1402 granularity. Where this table contains system wide traffic 1403 statistics the ipIfStatsTable contains the same statistics 1404 but counted on a per-interface basis." 1405 ::= { ipTrafficStats 1 } 1407 ipSystemStatsEntry OBJECT-TYPE 1408 SYNTAX IpSystemStatsEntry 1409 MAX-ACCESS not-accessible 1410 STATUS current 1411 DESCRIPTION 1412 "A statistics entry containing system-wide objects for a 1413 particular address type." 1415 INDEX { ipSystemStatsAFType } 1416 ::= { ipSystemStatsTable 1 } 1418 IpSystemStatsEntry ::= SEQUENCE { 1419 ipSystemStatsAFType InetAddressType, 1420 ipSystemStatsInReceives Counter32, 1421 ipSystemStatsHCInReceives Counter64, 1422 ipSystemStatsInOctets Counter32, 1423 ipSystemStatsHCInOctets Counter64, 1424 ipSystemStatsInHdrErrors Counter32, 1425 ipSystemStatsInNoRoutes Counter32, 1426 ipSystemStatsInAddrErrors Counter32, 1427 ipSystemStatsInUnknownProtos Counter32, 1428 ipSystemStatsInTruncatedPkts Counter32, 1429 ipSystemStatsInForwDatagrams Counter32, 1430 ipSystemStatsReasmReqds Counter32, 1431 ipSystemStatsReasmOKs Counter32, 1432 ipSystemStatsReasmFails Counter32, 1433 ipSystemStatsInDiscards Counter32, 1434 ipSystemStatsInDelivers Counter32, 1435 ipSystemStatsOutRequests Counter32, 1436 ipSystemStatsOutNoRoutes Counter32, 1437 ipSystemStatsOutForwDatagrams Counter32, 1438 ipSystemStatsOutDiscards Counter32, 1439 ipSystemStatsOutFragReqds Counter32, 1440 ipSystemStatsOutFragOKs Counter32, 1441 ipSystemStatsOutFragFails Counter32, 1442 ipSystemStatsOutFragCreates Counter32, 1443 ipSystemStatsOutTransmits Counter32, 1444 ipSystemStatsHCOutTransmits Counter64, 1445 ipSystemStatsOutOctets Counter32, 1446 ipSystemStatsHCOutOctets Counter64, 1447 ipSystemStatsInMcastPkts Counter32, 1448 ipSystemStatsHCInMcastPkts Counter64, 1449 ipSystemStatsInMcastOctets Counter32, 1450 ipSystemStatsHCInMcastOctets Counter64, 1451 ipSystemStatsOutMcastPkts Counter32, 1452 ipSystemStatsHCOutMcastPkts Counter64, 1453 ipSystemStatsOutMcastOctets Counter32, 1454 ipSystemStatsHCOutMcastOctets Counter64, 1455 ipSystemStatsInBcastPkts Counter32, 1456 ipSystemStatsHCInBcastPkts Counter64, 1457 ipSystemStatsOutBcastPkts Counter32, 1458 ipSystemStatsHCOutBcastPkts Counter64, 1459 ipSystemStatsDiscontinuityTime TimeStamp, 1460 ipSystemStatsRefreshRate Unsigned32 1461 } 1463 ipSystemStatsAFType OBJECT-TYPE 1464 SYNTAX InetAddressType 1465 MAX-ACCESS not-accessible 1466 STATUS current 1467 DESCRIPTION 1468 "The address type for this row." 1469 ::= { ipSystemStatsEntry 1 } 1471 -- This object ID is reserved to allow the IDs for this table's objects 1472 -- to align with the objects in the ipIfStatsTable. 1473 -- ::= { ipSystemStatsEntry 2 } 1475 ipSystemStatsInReceives OBJECT-TYPE 1476 SYNTAX Counter32 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "The total number of input IP datagrams received, including 1481 those received in error. 1483 Discontinuities in the value of this counter can occur at 1484 re-initialization of the management system, and at other 1485 times as indicated by the value of 1486 ipSystemStatsDiscontinuityTime." 1487 ::= { ipSystemStatsEntry 3 } 1489 ipSystemStatsHCInReceives OBJECT-TYPE 1490 SYNTAX Counter64 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "The total number of input IP datagrams received, including 1495 those received in error. This object counts the same 1496 datagrams as ipSystemStatsInReceives but allows for larger 1497 values. 1499 Discontinuities in the value of this counter can occur at 1500 re-initialization of the management system, and at other 1501 times as indicated by the value of 1502 ipSystemStatsDiscontinuityTime." 1503 ::= { ipSystemStatsEntry 4 } 1505 ipSystemStatsInOctets OBJECT-TYPE 1506 SYNTAX Counter32 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "The total number of octets received in input IP datagrams, 1511 including those received in error. Octets from datagrams 1512 counted in ipSystemStatsInReceives MUST be counted here. 1514 Discontinuities in the value of this counter can occur at 1515 re-initialization of the management system, and at other 1516 times as indicated by the value of 1517 ipSystemStatsDiscontinuityTime." 1518 ::= { ipSystemStatsEntry 5 } 1520 ipSystemStatsHCInOctets OBJECT-TYPE 1521 SYNTAX Counter64 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "The total number of octets received in input IP datagrams, 1526 including those received in error. This object counts the 1527 same octets as ipSystemStatsInOctets but allows for larger 1528 values. 1530 Discontinuities in the value of this counter can occur at 1531 re-initialization of the management system, and at other 1532 times as indicated by the value of 1533 ipSystemStatsDiscontinuityTime." 1534 ::= { ipSystemStatsEntry 6 } 1536 ipSystemStatsInHdrErrors OBJECT-TYPE 1537 SYNTAX Counter32 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "The number of input IP datagrams discarded due to errors in 1542 their IP headers, including version number mismatch, other 1543 format errors, hop count exceeded, errors discovered in 1544 processing their IP options, etc. 1546 Discontinuities in the value of this counter can occur at 1547 re-initialization of the management system, and at other 1548 times as indicated by the value of 1549 ipSystemStatsDiscontinuityTime." 1550 ::= { ipSystemStatsEntry 7 } 1552 ipSystemStatsInNoRoutes OBJECT-TYPE 1553 SYNTAX Counter32 1554 MAX-ACCESS read-only 1555 STATUS current 1556 DESCRIPTION 1557 "The number of input IP datagrams discarded because no route 1558 could be found to transmit them to their destination. 1560 Discontinuities in the value of this counter can occur at 1561 re-initialization of the management system, and at other 1562 times as indicated by the value of 1563 ipSystemStatsDiscontinuityTime." 1564 ::= { ipSystemStatsEntry 8 } 1566 ipSystemStatsInAddrErrors OBJECT-TYPE 1567 SYNTAX Counter32 1568 MAX-ACCESS read-only 1569 STATUS current 1570 DESCRIPTION 1571 "The number of input IP datagrams discarded because the IP 1572 address in their IP header's destination field was not a 1573 valid address to be received at this entity. This count 1574 includes invalid addresses (e.g., ::0) and unsupported 1575 addresses (e.g., addresses with unallocated prefixes). For 1576 entities which are not IP routers and therefore do not 1577 forward datagrams, this counter includes datagrams discarded 1578 because the destination address was not a local address. 1580 Discontinuities in the value of this counter can occur at 1581 re-initialization of the management system, and at other 1582 times as indicated by the value of 1583 ipSystemStatsDiscontinuityTime." 1584 ::= { ipSystemStatsEntry 9 } 1586 ipSystemStatsInUnknownProtos OBJECT-TYPE 1587 SYNTAX Counter32 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "The number of locally-addressed IP datagrams received 1592 successfully but discarded because of an unknown or 1593 unsupported protocol. 1595 When tracking interface statistics the counter of the 1596 interface to which these datagrams were addressed is 1597 incremented. This interface might not be the same as the 1598 input interface for some of the datagrams. 1600 Discontinuities in the value of this counter can occur at 1601 re-initialization of the management system, and at other 1602 times as indicated by the value of 1603 ipSystemStatsDiscontinuityTime." 1604 ::= { ipSystemStatsEntry 10 } 1606 ipSystemStatsInTruncatedPkts OBJECT-TYPE 1607 SYNTAX Counter32 1608 MAX-ACCESS read-only 1609 STATUS current 1610 DESCRIPTION 1611 "The number of input IP datagrams discarded because datagram 1612 frame didn't carry enough data. 1614 Discontinuities in the value of this counter can occur at 1615 re-initialization of the management system, and at other 1616 times as indicated by the value of 1617 ipSystemStatsDiscontinuityTime." 1618 ::= { ipSystemStatsEntry 11 } 1620 ipSystemStatsInForwDatagrams OBJECT-TYPE 1621 SYNTAX Counter32 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "The number of input datagrams for which this entity was not 1626 their final IP destination and for which this entity 1627 attempted to find a route to forward them to that final 1628 destination. In entities which do not act as IP routers, 1629 this counter will include only those datagrams which were 1630 Source-Routed via this entity, and the Source-Route 1631 processing was successful. 1633 When tracking interface statistics the counter of the 1634 incoming interface is incremented for each datagram. 1636 Discontinuities in the value of this counter can occur at 1637 re-initialization of the management system, and at other 1638 times as indicated by the value of 1639 ipSystemStatsDiscontinuityTime." 1640 ::= { ipSystemStatsEntry 12 } 1642 ipSystemStatsReasmReqds OBJECT-TYPE 1643 SYNTAX Counter32 1644 MAX-ACCESS read-only 1645 STATUS current 1646 DESCRIPTION 1647 "The number of IP fragments received which needed to be 1648 reassembled at this interface. 1650 When tracking interface statistics the counter of the 1651 interface to which these fragments were addressed is 1652 incremented. This interface might not be the same as the 1653 input interface for some of the fragments. 1655 Discontinuities in the value of this counter can occur at 1656 re-initialization of the management system, and at other 1657 times as indicated by the value of 1658 ipSystemStatsDiscontinuityTime." 1659 ::= { ipSystemStatsEntry 13 } 1661 ipSystemStatsReasmOKs OBJECT-TYPE 1662 SYNTAX Counter32 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "The number of IP datagrams successfully reassembled. 1668 When tracking interface statistics the counter of the 1669 interface to which these datagrams were addressed is 1670 incremented. This interface might not be the same as the 1671 input interface for some of the datagrams. 1673 Discontinuities in the value of this counter can occur at 1674 re-initialization of the management system, and at other 1675 times as indicated by the value of 1676 ipSystemStatsDiscontinuityTime." 1677 ::= { ipSystemStatsEntry 14 } 1679 ipSystemStatsReasmFails OBJECT-TYPE 1680 SYNTAX Counter32 1681 MAX-ACCESS read-only 1682 STATUS current 1683 DESCRIPTION 1684 "The number of failures detected by the IP re-assembly 1685 algorithm (for whatever reason: timed out, errors, etc.). 1686 Note that this is not necessarily a count of discarded IP 1687 fragments since some algorithms (notably the algorithm in 1688 RFC 815) can lose track of the number of fragments by 1689 combining them as they are received. 1691 When tracking interface statistics the counter of the 1692 interface to which these fragments were addressed is 1693 incremented. This interface might not be the same as the 1694 input interface for some of the fragments. 1696 Discontinuities in the value of this counter can occur at 1697 re-initialization of the management system, and at other 1698 times as indicated by the value of 1699 ipSystemStatsDiscontinuityTime." 1700 ::= { ipSystemStatsEntry 15 } 1702 ipSystemStatsInDiscards OBJECT-TYPE 1703 SYNTAX Counter32 1704 MAX-ACCESS read-only 1705 STATUS current 1706 DESCRIPTION 1707 "The number of input IP datagrams for which no problems were 1708 encountered to prevent their continued processing, but which 1709 were discarded (e.g., for lack of buffer space). Note that 1710 this counter does not include any datagrams discarded while 1711 awaiting re-assembly. 1713 Discontinuities in the value of this counter can occur at 1714 re-initialization of the management system, and at other 1715 times as indicated by the value of 1716 ipSystemStatsDiscontinuityTime." 1717 ::= { ipSystemStatsEntry 16 } 1719 ipSystemStatsInDelivers OBJECT-TYPE 1720 SYNTAX Counter32 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 "The total number of datagrams successfully delivered to IP 1725 user-protocols (including ICMP). 1727 When tracking interface statistics the counter of the 1728 interface to which these datagrams were addressed is 1729 incremented. This interface might not be the same as the 1730 input interface for some of the datagrams. 1732 Discontinuities in the value of this counter can occur at 1733 re-initialization of the management system, and at other 1734 times as indicated by the value of 1735 ipSystemStatsDiscontinuityTime." 1736 ::= { ipSystemStatsEntry 17 } 1738 ipSystemStatsOutRequests OBJECT-TYPE 1739 SYNTAX Counter32 1740 MAX-ACCESS read-only 1741 STATUS current 1742 DESCRIPTION 1743 "The total number of IP datagrams which local IP user- 1744 protocols (including ICMP) supplied to IP in requests for 1745 transmission. Note that this counter does not include any 1746 datagrams counted in ipSystemStatsOutForwDatagrams. 1748 Discontinuities in the value of this counter can occur at 1749 re-initialization of the management system, and at other 1750 times as indicated by the value of 1751 ipSystemStatsDiscontinuityTime." 1753 ::= { ipSystemStatsEntry 18 } 1755 ipSystemStatsOutNoRoutes OBJECT-TYPE 1756 SYNTAX Counter32 1757 MAX-ACCESS read-only 1758 STATUS current 1759 DESCRIPTION 1760 "The number of local generated IP datagrams discarded because 1761 no route could be found to transmit them to their 1762 destination. 1764 As no route can be found for these datagrams the interface 1765 specific instances are not meaningful for this object. 1767 Discontinuities in the value of this counter can occur at 1768 re-initialization of the management system, and at other 1769 times as indicated by the value of 1770 ipSystemStatsDiscontinuityTime." 1771 ::= { ipSystemStatsEntry 19 } 1773 ipSystemStatsOutForwDatagrams OBJECT-TYPE 1774 SYNTAX Counter32 1775 MAX-ACCESS read-only 1776 STATUS current 1777 DESCRIPTION 1778 "The number of datagrams which this entity received and for 1779 which it was successful in finding a path to their final 1780 destination. In entities which do not act as IP routers, 1781 this counter will include only those datagrams which were 1782 Source-Routed via this entity, and the Source-Route 1783 processing was successful. 1785 When tracking interface statistics the counter of the 1786 outgoing interface is incremented for a successfully 1787 forwarded datagram. 1789 Discontinuities in the value of this counter can occur at 1790 re-initialization of the management system, and at other 1791 times as indicated by the value of 1792 ipSystemStatsDiscontinuityTime." 1793 ::= { ipSystemStatsEntry 20 } 1795 ipSystemStatsOutDiscards OBJECT-TYPE 1796 SYNTAX Counter32 1797 MAX-ACCESS read-only 1798 STATUS current 1799 DESCRIPTION 1800 "The number of output IP datagrams for which no problem was 1801 encountered to prevent their transmission to their 1802 destination, but which were discarded (e.g., for lack of 1803 buffer space). Note that this counter would include 1804 datagrams counted in ipSystemStatsOutForwDatagrams if any 1805 such datagrams met this (discretionary) discard criterion. 1807 Discontinuities in the value of this counter can occur at 1808 re-initialization of the management system, and at other 1809 times as indicated by the value of 1810 ipSystemStatsDiscontinuityTime." 1811 ::= { ipSystemStatsEntry 21 } 1813 ipSystemStatsOutFragReqds OBJECT-TYPE 1814 SYNTAX Counter32 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "The number of IP datagrams that would require fragmentation 1819 in order to be transmitted. 1821 When tracking interface statistics the counter of the 1822 outgoing interface is incremented for a successfully 1823 fragmented datagram. 1825 Discontinuities in the value of this counter can occur at 1826 re-initialization of the management system, and at other 1827 times as indicated by the value of 1828 ipSystemStatsDiscontinuityTime." 1829 ::= { ipSystemStatsEntry 22 } 1831 ipSystemStatsOutFragOKs OBJECT-TYPE 1832 SYNTAX Counter32 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "The number of IP datagrams that have been successfully 1837 fragmented. 1839 When tracking interface statistics the counter of the 1840 outgoing interface is incremented for a successfully 1841 fragmented datagram. 1843 Discontinuities in the value of this counter can occur at 1844 re-initialization of the management system, and at other 1845 times as indicated by the value of 1846 ipSystemStatsDiscontinuityTime." 1847 ::= { ipSystemStatsEntry 23 } 1849 ipSystemStatsOutFragFails OBJECT-TYPE 1850 SYNTAX Counter32 1851 MAX-ACCESS read-only 1852 STATUS current 1853 DESCRIPTION 1854 "The number of IP datagrams that have been discarded because 1855 they needed to be fragmented but could not be. This 1856 includes IPv4 packets that have the DF bit set and IPv6 1857 packets that are being forwarded and exceed the outgoing 1858 link MTU. 1860 When tracking interface statistics the counter of the 1861 outgoing interface is incremented for an unsuccessfully 1862 fragmented datagram. 1864 Discontinuities in the value of this counter can occur at 1865 re-initialization of the management system, and at other 1866 times as indicated by the value of 1867 ipSystemStatsDiscontinuityTime." 1868 ::= { ipSystemStatsEntry 24 } 1870 ipSystemStatsOutFragCreates OBJECT-TYPE 1871 SYNTAX Counter32 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "The number of output datagram fragments that have been 1876 generated as a result of IP fragmentation. 1878 When tracking interface statistics the counter of the 1879 outgoing interface is incremented for a successfully 1880 fragmented datagram. 1882 Discontinuities in the value of this counter can occur at 1883 re-initialization of the management system, and at other 1884 times as indicated by the value of 1885 ipSystemStatsDiscontinuityTime." 1886 ::= { ipSystemStatsEntry 25 } 1888 ipSystemStatsOutTransmits OBJECT-TYPE 1889 SYNTAX Counter32 1890 MAX-ACCESS read-only 1891 STATUS current 1892 DESCRIPTION 1893 "The total number of IP datagrams that this entity supplied 1894 to the lower layers for transmission. This includes 1895 datagrams generated local and those forwarded by this 1896 entity. 1898 Discontinuities in the value of this counter can occur at 1899 re-initialization of the management system, and at other 1900 times as indicated by the value of 1901 ipSystemStatsDiscontinuityTime." 1902 ::= { ipSystemStatsEntry 26 } 1904 ipSystemStatsHCOutTransmits OBJECT-TYPE 1905 SYNTAX Counter64 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "The total number of IP datagrams that this entity supplied 1910 to the lower layers for transmission. This object counts 1911 the same datagrams as ipSystemStatsOutTransmits but allows 1912 for larger values. 1914 Discontinuities in the value of this counter can occur at 1915 re-initialization of the management system, and at other 1916 times as indicated by the value of 1917 ipSystemStatsDiscontinuityTime." 1918 ::= { ipSystemStatsEntry 27 } 1920 ipSystemStatsOutOctets OBJECT-TYPE 1921 SYNTAX Counter32 1922 MAX-ACCESS read-only 1923 STATUS current 1924 DESCRIPTION 1925 "The total number of octets in IP datagrams delivered to the 1926 lower layers for transmission. Octets from datagrams 1927 counted in ipSystemStatsOutTransmits MUST be counted here. 1929 Discontinuities in the value of this counter can occur at 1930 re-initialization of the management system, and at other 1931 times as indicated by the value of 1932 ipSystemStatsDiscontinuityTime." 1933 ::= { ipSystemStatsEntry 28 } 1935 ipSystemStatsHCOutOctets OBJECT-TYPE 1936 SYNTAX Counter64 1937 MAX-ACCESS read-only 1938 STATUS current 1939 DESCRIPTION 1940 "The total number of octets in IP datagrams delivered to the 1941 lower layers for transmission. This objects counts the same 1942 octets as ipSystemStatsOutOctets but allows for larger 1943 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 29 } 1951 ipSystemStatsInMcastPkts OBJECT-TYPE 1952 SYNTAX Counter32 1953 MAX-ACCESS read-only 1954 STATUS current 1955 DESCRIPTION 1956 "The number of IP multicast datagrams received. 1958 Discontinuities in the value of this counter can occur at 1959 re-initialization of the management system, and at other 1960 times as indicated by the value of 1961 ipSystemStatsDiscontinuityTime." 1962 ::= { ipSystemStatsEntry 30 } 1964 ipSystemStatsHCInMcastPkts OBJECT-TYPE 1965 SYNTAX Counter64 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "The number of IP multicast datagrams received. This object 1970 counts the same datagrams as ipSystemStatsInMcastPkts but 1971 allows for larger values. 1973 Discontinuities in the value of this counter can occur at 1974 re-initialization of the management system, and at other 1975 times as indicated by the value of 1976 ipSystemStatsDiscontinuityTime." 1977 ::= { ipSystemStatsEntry 31 } 1979 ipSystemStatsInMcastOctets OBJECT-TYPE 1980 SYNTAX Counter32 1981 MAX-ACCESS read-only 1982 STATUS current 1983 DESCRIPTION 1984 "The total number of octets received in IP multicast 1985 datagrams. Octets from datagrams counted in 1986 ipSystemStatsOutMcastPkts MUST be counted here. 1988 Discontinuities in the value of this counter can occur at 1989 re-initialization of the management system, and at other 1990 times as indicated by the value of 1991 ipSystemStatsDiscontinuityTime." 1992 ::= { ipSystemStatsEntry 32 } 1994 ipSystemStatsHCInMcastOctets OBJECT-TYPE 1995 SYNTAX Counter64 1996 MAX-ACCESS read-only 1997 STATUS current 1998 DESCRIPTION 1999 "The total number of octets received in IP multicast 2000 datagrams. This object counts the same octets as 2001 ipSystemStatsInMcastOctets but allows for larger values. 2003 Discontinuities in the value of this counter can occur at 2004 re-initialization of the management system, and at other 2005 times as indicated by the value of 2006 ipSystemStatsDiscontinuityTime." 2007 ::= { ipSystemStatsEntry 33 } 2009 ipSystemStatsOutMcastPkts OBJECT-TYPE 2010 SYNTAX Counter32 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "The number of IP multicast datagrams transmitted. 2016 Discontinuities in the value of this counter can occur at 2017 re-initialization of the management system, and at other 2018 times as indicated by the value of 2019 ipSystemStatsDiscontinuityTime." 2020 ::= { ipSystemStatsEntry 34 } 2022 ipSystemStatsHCOutMcastPkts OBJECT-TYPE 2023 SYNTAX Counter64 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "The number of IP multicast datagrams transmitted. This 2028 object counts the same datagrams as 2029 ipSystemStatsOutMcastPkts but allows for larger values. 2031 Discontinuities in the value of this counter can occur at 2032 re-initialization of the management system, and at other 2033 times as indicated by the value of 2034 ipSystemStatsDiscontinuityTime." 2035 ::= { ipSystemStatsEntry 35 } 2037 ipSystemStatsOutMcastOctets OBJECT-TYPE 2038 SYNTAX Counter32 2039 MAX-ACCESS read-only 2040 STATUS current 2041 DESCRIPTION 2042 "The total number of octets transmitted in IP multicast 2043 datagrams. Octets from datagrams counted in 2044 ipSystemStatsInMcastPkts MUST be counted here. 2046 Discontinuities in the value of this counter can occur at 2047 re-initialization of the management system, and at other 2048 times as indicated by the value of 2049 ipSystemStatsDiscontinuityTime." 2050 ::= { ipSystemStatsEntry 36 } 2052 ipSystemStatsHCOutMcastOctets OBJECT-TYPE 2053 SYNTAX Counter64 2054 MAX-ACCESS read-only 2055 STATUS current 2056 DESCRIPTION 2057 "The total number of octets received in IP multicast 2058 datagrams. This object counts the same octets as 2059 ipSystemStatsOutMcastOctets but allows for larger values. 2061 Discontinuities in the value of this counter can occur at 2062 re-initialization of the management system, and at other 2063 times as indicated by the value of 2064 ipSystemStatsDiscontinuityTime." 2065 ::= { ipSystemStatsEntry 37 } 2067 ipSystemStatsInBcastPkts OBJECT-TYPE 2068 SYNTAX Counter32 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "The number of IP broadcast datagrams received. 2074 Discontinuities in the value of this counter can occur at 2075 re-initialization of the management system, and at other 2076 times as indicated by the value of 2077 ipSystemStatsDiscontinuityTime." 2078 ::= { ipSystemStatsEntry 38 } 2080 ipSystemStatsHCInBcastPkts OBJECT-TYPE 2081 SYNTAX Counter64 2082 MAX-ACCESS read-only 2083 STATUS current 2084 DESCRIPTION 2085 "The number of IP broadcast datagrams received. This object 2086 counts the same datagrams as ipSystemStatsInBcastPkts but 2087 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 39 } 2095 ipSystemStatsOutBcastPkts OBJECT-TYPE 2096 SYNTAX Counter32 2097 MAX-ACCESS read-only 2098 STATUS current 2099 DESCRIPTION 2100 "The number of IP broadcast datagrams transmitted. 2102 Discontinuities in the value of this counter can occur at 2103 re-initialization of the management system, and at other 2104 times as indicated by the value of 2105 ipSystemStatsDiscontinuityTime." 2106 ::= { ipSystemStatsEntry 40 } 2108 ipSystemStatsHCOutBcastPkts OBJECT-TYPE 2109 SYNTAX Counter64 2110 MAX-ACCESS read-only 2111 STATUS current 2112 DESCRIPTION 2113 "The number of IP broadcast datagrams transmitted. This 2114 object counts the same datagrams as 2115 ipSystemStatsOutBcastPkts but allows for larger values. 2117 Discontinuities in the value of this counter can occur at 2118 re-initialization of the management system, and at other 2119 times as indicated by the value of 2120 ipSystemStatsDiscontinuityTime." 2121 ::= { ipSystemStatsEntry 41 } 2123 ipSystemStatsDiscontinuityTime OBJECT-TYPE 2124 SYNTAX TimeStamp 2125 MAX-ACCESS read-only 2126 STATUS current 2127 DESCRIPTION 2128 "The value of sysUpTime on the most recent occasion at which 2129 any one or more of this entry's counters suffered a 2130 discontinuity. 2132 If no such discontinuities have occurred since the last re- 2133 initialization of the local management subsystem, then this 2134 object contains a zero value." 2135 ::= { ipSystemStatsEntry 42 } 2137 ipSystemStatsRefreshRate OBJECT-TYPE 2138 SYNTAX Unsigned32 2139 UNITS "milli-seconds" 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "The minimum reasonable polling interval for this entry. 2144 This object provides an indication of the minimum amount of 2145 time required to update the counters in this entry." 2146 ::= { ipSystemStatsEntry 43 } 2148 ipIfStatsTableLastChange OBJECT-TYPE 2149 SYNTAX TimeStamp 2150 MAX-ACCESS read-only 2151 STATUS current 2152 DESCRIPTION 2153 "The value of sysUpTime on the most recent occasion at which 2154 a row in the ipIfStatsTable was added or deleted. 2156 If new objects are added to the ipIfStatsTable that require 2157 the ipIfStatsTableLastChange to be updated when they are 2158 modified they must specify that requirement in their 2159 description clause." 2160 ::= { ipTrafficStats 2 } 2162 ipIfStatsTable OBJECT-TYPE 2163 SYNTAX SEQUENCE OF IpIfStatsEntry 2164 MAX-ACCESS not-accessible 2165 STATUS current 2166 DESCRIPTION 2167 "The table containing per-interface traffic statistics. This 2168 table and the ipSystemStatsTable contain similar objects 2169 whose difference is in their granularity. Where this table 2170 contains per-interface statistics the ipSystemStatsTable 2171 contains the same statistics but counted on a system wide 2172 basis." 2173 ::= { ipTrafficStats 3 } 2175 ipIfStatsEntry OBJECT-TYPE 2176 SYNTAX IpIfStatsEntry 2177 MAX-ACCESS not-accessible 2178 STATUS current 2179 DESCRIPTION 2180 "An interface statistics entry containing objects for a 2181 particular interface and address type." 2182 INDEX { ipIfStatsAFType, ipIfStatsIfIndex } 2183 ::= { ipIfStatsTable 1 } 2185 IpIfStatsEntry ::= SEQUENCE { 2186 ipIfStatsAFType InetAddressType, 2187 ipIfStatsIfIndex InterfaceIndex, 2188 ipIfStatsInReceives Counter32, 2189 ipIfStatsHCInReceives Counter64, 2190 ipIfStatsInOctets Counter32, 2191 ipIfStatsHCInOctets Counter64, 2192 ipIfStatsInHdrErrors Counter32, 2193 ipIfStatsInNoRoutes Counter32, 2194 ipIfStatsInAddrErrors Counter32, 2195 ipIfStatsInUnknownProtos Counter32, 2196 ipIfStatsInTruncatedPkts Counter32, 2197 ipIfStatsInForwDatagrams Counter32, 2198 ipIfStatsReasmReqds Counter32, 2199 ipIfStatsReasmOKs Counter32, 2200 ipIfStatsReasmFails Counter32, 2201 ipIfStatsInDiscards Counter32, 2202 ipIfStatsInDelivers Counter32, 2203 ipIfStatsOutRequests Counter32, 2204 ipIfStatsOutNoRoutes Counter32, 2205 ipIfStatsOutForwDatagrams Counter32, 2206 ipIfStatsOutDiscards Counter32, 2207 ipIfStatsOutFragReqds Counter32, 2208 ipIfStatsOutFragOKs Counter32, 2209 ipIfStatsOutFragFails Counter32, 2210 ipIfStatsOutFragCreates Counter32, 2211 ipIfStatsOutTransmits Counter32, 2212 ipIfStatsHCOutTransmits Counter64, 2213 ipIfStatsOutOctets Counter32, 2214 ipIfStatsHCOutOctets Counter64, 2215 ipIfStatsInMcastPkts Counter32, 2216 ipIfStatsHCInMcastPkts Counter64, 2217 ipIfStatsInMcastOctets Counter32, 2218 ipIfStatsHCInMcastOctets Counter64, 2219 ipIfStatsOutMcastPkts Counter32, 2220 ipIfStatsHCOutMcastPkts Counter64, 2221 ipIfStatsOutMcastOctets Counter32, 2222 ipIfStatsHCOutMcastOctets Counter64, 2223 ipIfStatsInBcastPkts Counter32, 2224 ipIfStatsHCInBcastPkts Counter64, 2225 ipIfStatsOutBcastPkts Counter32, 2226 ipIfStatsHCOutBcastPkts Counter64, 2227 ipIfStatsDiscontinuityTime TimeStamp, 2228 ipIfStatsRefreshRate Unsigned32 2229 } 2231 ipIfStatsAFType OBJECT-TYPE 2232 SYNTAX InetAddressType 2233 MAX-ACCESS not-accessible 2234 STATUS current 2235 DESCRIPTION 2236 "The address type for this row." 2237 ::= { ipIfStatsEntry 1 } 2239 ipIfStatsIfIndex OBJECT-TYPE 2240 SYNTAX InterfaceIndex 2241 MAX-ACCESS not-accessible 2242 STATUS current 2243 DESCRIPTION 2244 "The index value which uniquely identifies the interface to 2245 which this entry is applicable. The interface identified by 2246 a particular value of this index is the same interface as 2247 identified by the same value of the IF-MIB's ifIndex." 2248 ::= { ipIfStatsEntry 2 } 2250 ipIfStatsInReceives OBJECT-TYPE 2251 SYNTAX Counter32 2252 MAX-ACCESS read-only 2253 STATUS current 2254 DESCRIPTION 2255 "The total number of input IP datagrams received, including 2256 those received in error. 2258 Discontinuities in the value of this counter can occur at 2259 re-initialization of the management system, and at other 2260 times as indicated by the value of 2261 ipIfStatsDiscontinuityTime." 2262 ::= { ipIfStatsEntry 3 } 2264 ipIfStatsHCInReceives OBJECT-TYPE 2265 SYNTAX Counter64 2266 MAX-ACCESS read-only 2267 STATUS current 2268 DESCRIPTION 2269 "The total number of input IP datagrams received, including 2270 those received in error. This object counts the same 2271 datagrams as ipIfStatsInReceives but allows for larger 2272 values. 2274 Discontinuities in the value of this counter can occur at 2275 re-initialization of the management system, and at other 2276 times as indicated by the value of 2277 ipIfStatsDiscontinuityTime." 2278 ::= { ipIfStatsEntry 4 } 2280 ipIfStatsInOctets OBJECT-TYPE 2281 SYNTAX Counter32 2282 MAX-ACCESS read-only 2283 STATUS current 2284 DESCRIPTION 2285 "The total number of octets received in input IP datagrams, 2286 including those received in error. Octets from datagrams 2287 counted in ipIfStatsInReceives MUST be counted here. 2289 Discontinuities in the value of this counter can occur at 2290 re-initialization of the management system, and at other 2291 times as indicated by the value of 2292 ipIfStatsDiscontinuityTime." 2293 ::= { ipIfStatsEntry 5 } 2295 ipIfStatsHCInOctets OBJECT-TYPE 2296 SYNTAX Counter64 2297 MAX-ACCESS read-only 2298 STATUS current 2299 DESCRIPTION 2300 "The total number of octets received in input IP datagrams, 2301 including those received in error. This object counts the 2302 same octets as ipIfStatsInOctets but allows for larger 2303 values. 2305 Discontinuities in the value of this counter can occur at 2306 re-initialization of the management system, and at other 2307 times as indicated by the value of 2308 ipIfStatsDiscontinuityTime." 2309 ::= { ipIfStatsEntry 6 } 2311 ipIfStatsInHdrErrors OBJECT-TYPE 2312 SYNTAX Counter32 2313 MAX-ACCESS read-only 2314 STATUS current 2315 DESCRIPTION 2316 "The number of input IP datagrams discarded due to errors in 2317 their IP headers, including version number mismatch, other 2318 format errors, hop count exceeded, errors discovered in 2319 processing their IP options, etc. 2321 Discontinuities in the value of this counter can occur at 2322 re-initialization of the management system, and at other 2323 times as indicated by the value of 2324 ipIfStatsDiscontinuityTime." 2325 ::= { ipIfStatsEntry 7 } 2327 ipIfStatsInNoRoutes OBJECT-TYPE 2328 SYNTAX Counter32 2329 MAX-ACCESS read-only 2330 STATUS current 2331 DESCRIPTION 2332 "The number of input IP datagrams discarded because no route 2333 could be found to transmit them to their destination. 2335 Discontinuities in the value of this counter can occur at 2336 re-initialization of the management system, and at other 2337 times as indicated by the value of 2338 ipIfStatsDiscontinuityTime." 2339 ::= { ipIfStatsEntry 8 } 2341 ipIfStatsInAddrErrors OBJECT-TYPE 2342 SYNTAX Counter32 2343 MAX-ACCESS read-only 2344 STATUS current 2345 DESCRIPTION 2346 "The number of input IP datagrams discarded because the IP 2347 address in their IP header's destination field was not a 2348 valid address to be received at this entity. This count 2349 includes invalid addresses (e.g., ::0) and unsupported 2350 addresses (e.g., addresses with unallocated prefixes). For 2351 entities which are not IP routers and therefore do not 2352 forward datagrams, this counter includes datagrams discarded 2353 because the destination address was not a local address. 2355 Discontinuities in the value of this counter can occur at 2356 re-initialization of the management system, and at other 2357 times as indicated by the value of 2358 ipIfStatsDiscontinuityTime." 2359 ::= { ipIfStatsEntry 9 } 2361 ipIfStatsInUnknownProtos OBJECT-TYPE 2362 SYNTAX Counter32 2363 MAX-ACCESS read-only 2364 STATUS current 2365 DESCRIPTION 2366 "The number of locally-addressed IP datagrams received 2367 successfully but discarded because of an unknown or 2368 unsupported protocol. 2370 When tracking interface statistics the counter of the 2371 interface to which these datagrams were addressed is 2372 incremented. This interface might not be the same as the 2373 input interface for some of the datagrams. 2375 Discontinuities in the value of this counter can occur at 2376 re-initialization of the management system, and at other 2377 times as indicated by the value of 2378 ipIfStatsDiscontinuityTime." 2379 ::= { ipIfStatsEntry 10 } 2381 ipIfStatsInTruncatedPkts OBJECT-TYPE 2382 SYNTAX Counter32 2383 MAX-ACCESS read-only 2384 STATUS current 2385 DESCRIPTION 2386 "The number of input IP datagrams discarded because datagram 2387 frame didn't carry enough data. 2389 Discontinuities in the value of this counter can occur at 2390 re-initialization of the management system, and at other 2391 times as indicated by the value of 2392 ipIfStatsDiscontinuityTime." 2393 ::= { ipIfStatsEntry 11 } 2395 ipIfStatsInForwDatagrams OBJECT-TYPE 2396 SYNTAX Counter32 2397 MAX-ACCESS read-only 2398 STATUS current 2399 DESCRIPTION 2400 "The number of input datagrams for which this entity was not 2401 their final IP destination and for which this entity 2402 attempted to find a route to forward them to that final 2403 destination. In entities which do not act as IP routers, 2404 this counter will include only those datagrams which were 2405 Source-Routed via this entity, and the Source-Route 2406 processing was successful. 2408 When tracking interface statistics the counter of the 2409 incoming interface is incremented for each datagram. 2411 Discontinuities in the value of this counter can occur at 2412 re-initialization of the management system, and at other 2413 times as indicated by the value of 2414 ipIfStatsDiscontinuityTime." 2415 ::= { ipIfStatsEntry 12 } 2417 ipIfStatsReasmReqds OBJECT-TYPE 2418 SYNTAX Counter32 2419 MAX-ACCESS read-only 2420 STATUS current 2421 DESCRIPTION 2422 "The number of IP fragments received which needed to be 2423 reassembled at this interface. 2425 When tracking interface statistics the counter of the 2426 interface to which these fragments were addressed is 2427 incremented. This interface might not be the same as the 2428 input interface for some of the fragments. 2430 Discontinuities in the value of this counter can occur at 2431 re-initialization of the management system, and at other 2432 times as indicated by the value of 2433 ipIfStatsDiscontinuityTime." 2434 ::= { ipIfStatsEntry 13 } 2436 ipIfStatsReasmOKs OBJECT-TYPE 2437 SYNTAX Counter32 2438 MAX-ACCESS read-only 2439 STATUS current 2440 DESCRIPTION 2441 "The number of IP datagrams successfully reassembled. 2443 When tracking interface statistics the counter of the 2444 interface to which these datagrams were addressed is 2445 incremented. This interface might not be the same as the 2446 input interface for some of the datagrams. 2448 Discontinuities in the value of this counter can occur at 2449 re-initialization of the management system, and at other 2450 times as indicated by the value of 2451 ipIfStatsDiscontinuityTime." 2452 ::= { ipIfStatsEntry 14 } 2454 ipIfStatsReasmFails OBJECT-TYPE 2455 SYNTAX Counter32 2456 MAX-ACCESS read-only 2457 STATUS current 2458 DESCRIPTION 2459 "The number of failures detected by the IP re-assembly 2460 algorithm (for whatever reason: timed out, errors, etc.). 2461 Note that this is not necessarily a count of discarded IP 2462 fragments since some algorithms (notably the algorithm in 2463 RFC 815) can lose track of the number of fragments by 2464 combining them as they are received. 2466 When tracking interface statistics the counter of the 2467 interface to which these fragments were addressed is 2468 incremented. This interface might not be the same as the 2469 input interface for some of the fragments. 2471 Discontinuities in the value of this counter can occur at 2472 re-initialization of the management system, and at other 2473 times as indicated by the value of 2474 ipIfStatsDiscontinuityTime." 2475 ::= { ipIfStatsEntry 15 } 2477 ipIfStatsInDiscards OBJECT-TYPE 2478 SYNTAX Counter32 2479 MAX-ACCESS read-only 2480 STATUS current 2481 DESCRIPTION 2482 "The number of input IP datagrams for which no problems were 2483 encountered to prevent their continued processing, but which 2484 were discarded (e.g., for lack of buffer space). Note that 2485 this counter does not include any datagrams discarded while 2486 awaiting re-assembly. 2488 Discontinuities in the value of this counter can occur at 2489 re-initialization of the management system, and at other 2490 times as indicated by the value of 2491 ipIfStatsDiscontinuityTime." 2492 ::= { ipIfStatsEntry 16 } 2494 ipIfStatsInDelivers OBJECT-TYPE 2495 SYNTAX Counter32 2496 MAX-ACCESS read-only 2497 STATUS current 2498 DESCRIPTION 2499 "The total number of datagrams successfully delivered to IP 2500 user-protocols (including ICMP). 2502 When tracking interface statistics the counter of the 2503 interface to which these datagrams were addressed is 2504 incremented. This interface might not be the same as the 2505 input interface for some of the datagrams. 2507 Discontinuities in the value of this counter can occur at 2508 re-initialization of the management system, and at other 2509 times as indicated by the value of 2510 ipIfStatsDiscontinuityTime." 2511 ::= { ipIfStatsEntry 17 } 2513 ipIfStatsOutRequests OBJECT-TYPE 2514 SYNTAX Counter32 2515 MAX-ACCESS read-only 2516 STATUS current 2517 DESCRIPTION 2518 "The total number of IP datagrams which local IP user- 2519 protocols (including ICMP) supplied to IP in requests for 2520 transmission. Note that this counter does not include any 2521 datagrams counted in ipIfStatsOutForwDatagrams. 2523 Discontinuities in the value of this counter can occur at 2524 re-initialization of the management system, and at other 2525 times as indicated by the value of 2526 ipIfStatsDiscontinuityTime." 2527 ::= { ipIfStatsEntry 18 } 2529 ipIfStatsOutNoRoutes OBJECT-TYPE 2530 SYNTAX Counter32 2531 MAX-ACCESS read-only 2532 STATUS current 2533 DESCRIPTION 2534 "The number of local generated IP datagrams discarded because 2535 no route could be found to transmit them to their 2536 destination. 2538 As no route can be found for these datagrams the interface 2539 specific instances are not meaningful for this object. 2541 Discontinuities in the value of this counter can occur at 2542 re-initialization of the management system, and at other 2543 times as indicated by the value of 2544 ipIfStatsDiscontinuityTime." 2545 ::= { ipIfStatsEntry 19 } 2547 ipIfStatsOutForwDatagrams OBJECT-TYPE 2548 SYNTAX Counter32 2549 MAX-ACCESS read-only 2550 STATUS current 2551 DESCRIPTION 2552 "The number of datagrams which this entity received and for 2553 which it was successful in finding a path to their final 2554 destination. In entities which do not act as IP routers, 2555 this counter will include only those datagrams which were 2556 Source-Routed via this entity, and the Source-Route 2557 processing was successful. 2559 When tracking interface statistics the counter of the 2560 outgoing interface is incremented for a successfully 2561 forwarded datagram. 2563 Discontinuities in the value of this counter can occur at 2564 re-initialization of the management system, and at other 2565 times as indicated by the value of 2566 ipIfStatsDiscontinuityTime." 2567 ::= { ipIfStatsEntry 20 } 2569 ipIfStatsOutDiscards OBJECT-TYPE 2570 SYNTAX Counter32 2571 MAX-ACCESS read-only 2572 STATUS current 2573 DESCRIPTION 2574 "The number of output IP datagrams for which no problem was 2575 encountered to prevent their transmission to their 2576 destination, but which were discarded (e.g., for lack of 2577 buffer space). Note that this counter would include 2578 datagrams counted in ipIfStatsOutForwDatagrams if any such 2579 datagrams met this (discretionary) discard criterion. 2581 Discontinuities in the value of this counter can occur at 2582 re-initialization of the management system, and at other 2583 times as indicated by the value of 2584 ipIfStatsDiscontinuityTime." 2585 ::= { ipIfStatsEntry 21 } 2587 ipIfStatsOutFragReqds OBJECT-TYPE 2588 SYNTAX Counter32 2589 MAX-ACCESS read-only 2590 STATUS current 2591 DESCRIPTION 2592 "The number of IP datagrams that would require fragmentation 2593 in order to be transmitted. 2595 When tracking interface statistics the counter of the 2596 outgoing interface is incremented for a successfully 2597 fragmented datagram. 2599 Discontinuities in the value of this counter can occur at 2600 re-initialization of the management system, and at other 2601 times as indicated by the value of 2602 ipIfStatsDiscontinuityTime." 2603 ::= { ipIfStatsEntry 22 } 2605 ipIfStatsOutFragOKs OBJECT-TYPE 2606 SYNTAX Counter32 2607 MAX-ACCESS read-only 2608 STATUS current 2609 DESCRIPTION 2610 "The number of IP datagrams that have been successfully 2611 fragmented. 2613 When tracking interface statistics the counter of the 2614 outgoing interface is incremented for a successfully 2615 fragmented datagram. 2617 Discontinuities in the value of this counter can occur at 2618 re-initialization of the management system, and at other 2619 times as indicated by the value of 2620 ipIfStatsDiscontinuityTime." 2621 ::= { ipIfStatsEntry 23 } 2623 ipIfStatsOutFragFails OBJECT-TYPE 2624 SYNTAX Counter32 2625 MAX-ACCESS read-only 2626 STATUS current 2627 DESCRIPTION 2628 "The number of IP datagrams that have been discarded because 2629 they needed to be fragmented but could not be. This 2630 includes IPv4 packets that have the DF bit set and IPv6 2631 packets that are being forwarded and exceed the outgoing 2632 link MTU. 2634 When tracking interface statistics the counter of the 2635 outgoing interface is incremented for an unsuccessfully 2636 fragmented datagram. 2638 Discontinuities in the value of this counter can occur at 2639 re-initialization of the management system, and at other 2640 times as indicated by the value of 2641 ipIfStatsDiscontinuityTime." 2642 ::= { ipIfStatsEntry 24 } 2644 ipIfStatsOutFragCreates OBJECT-TYPE 2645 SYNTAX Counter32 2646 MAX-ACCESS read-only 2647 STATUS current 2648 DESCRIPTION 2649 "The number of output datagram fragments that have been 2650 generated as a result of IP fragmentation. 2652 When tracking interface statistics the counter of the 2653 outgoing interface is incremented for a successfully 2654 fragmented datagram. 2656 Discontinuities in the value of this counter can occur at 2657 re-initialization of the management system, and at other 2658 times as indicated by the value of 2659 ipIfStatsDiscontinuityTime." 2660 ::= { ipIfStatsEntry 25 } 2662 ipIfStatsOutTransmits OBJECT-TYPE 2663 SYNTAX Counter32 2664 MAX-ACCESS read-only 2665 STATUS current 2666 DESCRIPTION 2667 "The total number of IP datagrams that this entity supplied 2668 to the lower layers for transmission. This includes 2669 datagrams generated local and those forwarded by this 2670 entity. 2672 Discontinuities in the value of this counter can occur at 2673 re-initialization of the management system, and at other 2674 times as indicated by the value of 2675 ipIfStatsDiscontinuityTime." 2676 ::= { ipIfStatsEntry 26 } 2678 ipIfStatsHCOutTransmits OBJECT-TYPE 2679 SYNTAX Counter64 2680 MAX-ACCESS read-only 2681 STATUS current 2682 DESCRIPTION 2683 "The total number of IP datagrams that this entity supplied 2684 to the lower layers for transmission. This object counts 2685 the same datagrams as ipIfStatsOutTransmits but allows for 2686 larger values. 2688 Discontinuities in the value of this counter can occur at 2689 re-initialization of the management system, and at other 2690 times as indicated by the value of 2691 ipIfStatsDiscontinuityTime." 2692 ::= { ipIfStatsEntry 27 } 2694 ipIfStatsOutOctets OBJECT-TYPE 2695 SYNTAX Counter32 2696 MAX-ACCESS read-only 2697 STATUS current 2698 DESCRIPTION 2699 "The total number of octets in IP datagrams delivered to the 2700 lower layers for transmission. Octets from datagrams 2701 counted in ipIfStatsOutTransmits MUST be counted here. 2703 Discontinuities in the value of this counter can occur at 2704 re-initialization of the management system, and at other 2705 times as indicated by the value of 2706 ipIfStatsDiscontinuityTime." 2707 ::= { ipIfStatsEntry 28 } 2709 ipIfStatsHCOutOctets OBJECT-TYPE 2710 SYNTAX Counter64 2711 MAX-ACCESS read-only 2712 STATUS current 2713 DESCRIPTION 2714 "The total number of octets in IP datagrams delivered to the 2715 lower layers for transmission. This objects counts the same 2716 octets as ipIfStatsOutOctets but allows for larger values. 2718 Discontinuities in the value of this counter can occur at 2719 re-initialization of the management system, and at other 2720 times as indicated by the value of 2721 ipIfStatsDiscontinuityTime." 2722 ::= { ipIfStatsEntry 29 } 2724 ipIfStatsInMcastPkts OBJECT-TYPE 2725 SYNTAX Counter32 2726 MAX-ACCESS read-only 2727 STATUS current 2728 DESCRIPTION 2729 "The number of IP multicast datagrams received. 2731 Discontinuities in the value of this counter can occur at 2732 re-initialization of the management system, and at other 2733 times as indicated by the value of 2734 ipIfStatsDiscontinuityTime." 2735 ::= { ipIfStatsEntry 30 } 2737 ipIfStatsHCInMcastPkts OBJECT-TYPE 2738 SYNTAX Counter64 2739 MAX-ACCESS read-only 2740 STATUS current 2741 DESCRIPTION 2742 "The number of IP multicast datagrams received. This object 2743 counts the same datagrams as ipIfStatsInMcastPkts but allows 2744 for larger values. 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 31 } 2752 ipIfStatsInMcastOctets OBJECT-TYPE 2753 SYNTAX Counter32 2754 MAX-ACCESS read-only 2755 STATUS current 2756 DESCRIPTION 2757 "The total number of octets received in IP multicast 2758 datagrams. Octets from datagrams counted in 2759 ipIfStatsOutMcastPkts MUST be counted here. 2761 Discontinuities in the value of this counter can occur at 2762 re-initialization of the management system, and at other 2763 times as indicated by the value of 2764 ipIfStatsDiscontinuityTime." 2765 ::= { ipIfStatsEntry 32 } 2767 ipIfStatsHCInMcastOctets OBJECT-TYPE 2768 SYNTAX Counter64 2769 MAX-ACCESS read-only 2770 STATUS current 2771 DESCRIPTION 2772 "The total number of octets received in IP multicast 2773 datagrams. This object counts the same octets as 2774 ipIfStatsInMcastOctets but allows for larger values. 2776 Discontinuities in the value of this counter can occur at 2777 re-initialization of the management system, and at other 2778 times as indicated by the value of 2779 ipIfStatsDiscontinuityTime." 2780 ::= { ipIfStatsEntry 33 } 2782 ipIfStatsOutMcastPkts OBJECT-TYPE 2783 SYNTAX Counter32 2784 MAX-ACCESS read-only 2785 STATUS current 2786 DESCRIPTION 2787 "The number of IP multicast datagrams transmitted. 2789 Discontinuities in the value of this counter can occur at 2790 re-initialization of the management system, and at other 2791 times as indicated by the value of 2792 ipIfStatsDiscontinuityTime." 2793 ::= { ipIfStatsEntry 34 } 2795 ipIfStatsHCOutMcastPkts OBJECT-TYPE 2796 SYNTAX Counter64 2797 MAX-ACCESS read-only 2798 STATUS current 2799 DESCRIPTION 2800 "The number of IP multicast datagrams transmitted. This 2801 object counts the same datagrams as ipIfStatsOutMcastPkts 2802 but allows for larger values. 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 35 } 2810 ipIfStatsOutMcastOctets OBJECT-TYPE 2811 SYNTAX Counter32 2812 MAX-ACCESS read-only 2813 STATUS current 2814 DESCRIPTION 2815 "The total number of octets transmitted in IP multicast 2816 datagrams. Octets from datagrams counted in 2817 ipIfStatsInMcastPkts MUST be counted here. 2819 Discontinuities in the value of this counter can occur at 2820 re-initialization of the management system, and at other 2821 times as indicated by the value of 2822 ipIfStatsDiscontinuityTime." 2823 ::= { ipIfStatsEntry 36 } 2825 ipIfStatsHCOutMcastOctets OBJECT-TYPE 2826 SYNTAX Counter64 2827 MAX-ACCESS read-only 2828 STATUS current 2829 DESCRIPTION 2830 "The total number of octets received in IP multicast 2831 datagrams. This object counts the same octets as 2832 ipIfStatsOutMcastOctets but allows for larger values. 2834 Discontinuities in the value of this counter can occur at 2835 re-initialization of the management system, and at other 2836 times as indicated by the value of 2837 ipIfStatsDiscontinuityTime." 2838 ::= { ipIfStatsEntry 37 } 2840 ipIfStatsInBcastPkts OBJECT-TYPE 2841 SYNTAX Counter32 2842 MAX-ACCESS read-only 2843 STATUS current 2844 DESCRIPTION 2845 "The number of IP broadcast datagrams received. 2847 Discontinuities in the value of this counter can occur at 2848 re-initialization of the management system, and at other 2849 times as indicated by the value of 2850 ipIfStatsDiscontinuityTime." 2851 ::= { ipIfStatsEntry 38 } 2853 ipIfStatsHCInBcastPkts OBJECT-TYPE 2854 SYNTAX Counter64 2855 MAX-ACCESS read-only 2856 STATUS current 2857 DESCRIPTION 2858 "The number of IP broadcast datagrams received. This object 2859 counts the same datagrams as ipIfStatsInBcastPkts but allows 2860 for larger values. 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 39 } 2868 ipIfStatsOutBcastPkts OBJECT-TYPE 2869 SYNTAX Counter32 2870 MAX-ACCESS read-only 2871 STATUS current 2872 DESCRIPTION 2873 "The number of IP broadcast datagrams transmitted. 2875 Discontinuities in the value of this counter can occur at 2876 re-initialization of the management system, and at other 2877 times as indicated by the value of 2878 ipIfStatsDiscontinuityTime." 2879 ::= { ipIfStatsEntry 40 } 2881 ipIfStatsHCOutBcastPkts OBJECT-TYPE 2882 SYNTAX Counter64 2883 MAX-ACCESS read-only 2884 STATUS current 2885 DESCRIPTION 2886 "The number of IP broadcast datagrams transmitted. This 2887 object counts the same datagrams as ipIfStatsOutBcastPkts 2888 but allows for larger values. 2890 Discontinuities in the value of this counter can occur at 2891 re-initialization of the management system, and at other 2892 times as indicated by the value of 2893 ipIfStatsDiscontinuityTime." 2894 ::= { ipIfStatsEntry 41 } 2896 ipIfStatsDiscontinuityTime OBJECT-TYPE 2897 SYNTAX TimeStamp 2898 MAX-ACCESS read-only 2899 STATUS current 2900 DESCRIPTION 2901 "The value of sysUpTime on the most recent occasion at which 2902 any one or more of this entry's counters suffered a 2903 discontinuity. 2905 If no such discontinuities have occurred since the last re- 2906 initialization of the local management subsystem, then this 2907 object contains a zero value." 2908 ::= { ipIfStatsEntry 42 } 2910 ipIfStatsRefreshRate OBJECT-TYPE 2911 SYNTAX Unsigned32 2912 UNITS "milli-seconds" 2913 MAX-ACCESS read-only 2914 STATUS current 2915 DESCRIPTION 2916 "The minimum reasonable polling interval for this entry. 2917 This object provides an indication of the minimum amount of 2918 time required to update the counters in this entry." 2919 ::= { ipIfStatsEntry 43 } 2921 -- 2922 -- Internet Address Prefix table 2923 -- 2925 ipAddressPrefixTable OBJECT-TYPE 2926 SYNTAX SEQUENCE OF IpAddressPrefixEntry 2927 MAX-ACCESS not-accessible 2928 STATUS current 2929 DESCRIPTION 2930 "This table allows the user to determine the source of an IP 2931 address or set of IP addresses and allows other tables to 2932 share the information via pointer rather than by copying. 2934 For example when the node configures both a unicast and 2935 anycast address for a prefix the ipAddressPrefix objects for 2936 those addresses will point to a single row in this table. 2938 This table primarily provides support for IPv6 prefixes and 2939 several of the objects are less meaningful for IPv4. The 2940 table continues to allow IPv4 addresses to allow future 2941 flexibility. In order to promote a common configuration 2942 this document includes suggestions for default values for 2943 IPv4 prefixes. Each of these values may be overridden if an 2944 object is meaningful to the node." 2945 ::= { ip 32 } 2947 ipAddressPrefixEntry OBJECT-TYPE 2948 SYNTAX IpAddressPrefixEntry 2949 MAX-ACCESS not-accessible 2950 STATUS current 2951 DESCRIPTION 2952 "inet prefix entry" 2953 INDEX { ipAddressPrefixIfIndex, ipAddressPrefixType, 2954 ipAddressPrefixPrefix, ipAddressPrefixLength } 2955 ::= { ipAddressPrefixTable 1 } 2957 IpAddressPrefixEntry ::= SEQUENCE { 2958 ipAddressPrefixIfIndex InterfaceIndex, 2959 ipAddressPrefixType InetAddressType, 2960 ipAddressPrefixPrefix InetAddress, 2961 ipAddressPrefixLength InetAddressPrefixLength, 2962 ipAddressPrefixOrigin IpAddressPrefixOrigin, 2963 ipAddressPrefixOnLinkFlag TruthValue, 2964 ipAddressPrefixAutonomousFlag TruthValue, 2965 ipAddressPrefixAdvPreferredLifetime Unsigned32, 2966 ipAddressPrefixAdvValidLifetime Unsigned32 2967 } 2969 ipAddressPrefixIfIndex OBJECT-TYPE 2970 SYNTAX InterfaceIndex 2971 MAX-ACCESS not-accessible 2972 STATUS current 2973 DESCRIPTION 2974 "The index value which uniquely identifies the interface on 2975 which this prefix is configured. The interface identified 2976 by a particular value of this index is the same interface as 2977 identified by the same value of the IF-MIB's ifIndex." 2978 ::= { ipAddressPrefixEntry 1 } 2980 ipAddressPrefixType OBJECT-TYPE 2981 SYNTAX InetAddressType 2982 MAX-ACCESS not-accessible 2983 STATUS current 2984 DESCRIPTION 2985 "The address type of ipAddressPrefix." 2986 ::= { ipAddressPrefixEntry 2 } 2988 ipAddressPrefixPrefix OBJECT-TYPE 2989 SYNTAX InetAddress (SIZE(0..36)) 2990 MAX-ACCESS not-accessible 2991 STATUS current 2992 DESCRIPTION 2993 "The address prefix. Bits after ipAddressPrefixLength must 2994 be zero." 2995 ::= { ipAddressPrefixEntry 3 } 2997 ipAddressPrefixLength OBJECT-TYPE 2998 SYNTAX InetAddressPrefixLength 2999 MAX-ACCESS not-accessible 3000 STATUS current 3001 DESCRIPTION 3002 "The prefix length associated with this prefix." 3003 ::= { ipAddressPrefixEntry 4 } 3005 ipAddressPrefixOrigin OBJECT-TYPE 3006 SYNTAX IpAddressPrefixOrigin 3007 MAX-ACCESS read-only 3008 STATUS current 3009 DESCRIPTION 3010 "The origin of this prefix." 3011 ::= { ipAddressPrefixEntry 5 } 3013 ipAddressPrefixOnLinkFlag OBJECT-TYPE 3014 SYNTAX TruthValue 3015 MAX-ACCESS read-only 3016 STATUS current 3017 DESCRIPTION 3018 "This object has the value 'true(1)', if this prefix can be 3019 used for on-link determination and the value 'false(2)' 3020 otherwise. 3022 The default for IPv4 prefixes is 'true(1)'." 3023 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and RFC2462" 3024 ::= { ipAddressPrefixEntry 6 } 3026 ipAddressPrefixAutonomousFlag OBJECT-TYPE 3027 SYNTAX TruthValue 3028 MAX-ACCESS read-only 3029 STATUS current 3030 DESCRIPTION 3031 "Autonomous address configuration flag. When true(1), 3032 indicates that this prefix can be used for autonomous 3033 address configuration (i.e. can be used to form a local 3034 interface address). If false(2), it is not used to auto- 3035 configure a local interface address. 3037 The default for IPv4 prefixes is 'false(2)'." 3038 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and RFC2462" 3039 ::= { ipAddressPrefixEntry 7 } 3041 ipAddressPrefixAdvPreferredLifetime OBJECT-TYPE 3042 SYNTAX Unsigned32 3043 UNITS "seconds" 3044 MAX-ACCESS read-only 3045 STATUS current 3046 DESCRIPTION 3047 "The length of time in seconds that this prefix will remain 3048 preferred, i.e. time until deprecation. A value of 3049 4,294,967,295 represents infinity. 3051 The address generated from a deprecated prefix should no 3052 longer be used as a source address in new communications, 3053 but packets received on such an interface are processed as 3054 expected. 3056 The default for IPv4 prefixes is 4,294,967,295 (infinity)." 3057 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and RFC2462" 3058 ::= { ipAddressPrefixEntry 8 } 3060 ipAddressPrefixAdvValidLifetime OBJECT-TYPE 3061 SYNTAX Unsigned32 3062 UNITS "seconds" 3063 MAX-ACCESS read-only 3064 STATUS current 3065 DESCRIPTION 3066 "The length of time, in seconds, that this prefix will remain 3067 valid, i.e. time until invalidation. A value of 3068 4,294,967,295 represents infinity. 3070 The address generated from an invalidated prefix should not 3071 appear as the destination or source address of a packet. 3073 The default for IPv4 prefixes is 4,294,967,295 (infinity)." 3074 REFERENCE "For IPv6 RFC2461, especially sections 2 and 4.6.2 and RFC2462" 3075 ::= { ipAddressPrefixEntry 9 } 3077 -- 3078 -- Internet Address Table 3079 -- 3081 ipAddressTable OBJECT-TYPE 3082 SYNTAX SEQUENCE OF IpAddressEntry 3083 MAX-ACCESS not-accessible 3084 STATUS current 3085 DESCRIPTION 3086 "This table contains addressing information relevant to the 3087 entity's interfaces. 3089 This table does not contain multicast address information. 3090 Tables for such information should be contained in multicast 3091 specific MIBs such as RFC3019. 3093 Note well: When including IPv6 link-local addresses in this 3094 table the entry must use an InetAddressType of 'ipv6z' in 3095 order to differentiate between the possible interfaces." 3096 ::= { ip 33 } 3098 ipAddressEntry OBJECT-TYPE 3099 SYNTAX IpAddressEntry 3100 MAX-ACCESS not-accessible 3101 STATUS current 3102 DESCRIPTION 3103 "inet addr entry" 3104 INDEX { ipAddressAddrType, ipAddressAddr } 3105 ::= { ipAddressTable 1 } 3107 IpAddressEntry ::= SEQUENCE { 3108 ipAddressAddrType InetAddressType, 3109 ipAddressAddr InetAddress, 3110 ipAddressIfIndex InterfaceIndex, 3111 ipAddressType INTEGER, 3112 ipAddressPrefix RowPointer, 3113 ipAddressOrigin IpAddressOrigin, 3114 ipAddressStatus IpAddressStatus, 3115 ipAddressCreated TimeStamp, 3116 ipAddressLastChanged TimeStamp 3117 } 3119 ipAddressAddrType OBJECT-TYPE 3120 SYNTAX InetAddressType 3121 MAX-ACCESS not-accessible 3122 STATUS current 3123 DESCRIPTION 3124 "The address type of ipAddressAddr." 3125 ::= { ipAddressEntry 1 } 3127 ipAddressAddr OBJECT-TYPE 3128 SYNTAX InetAddress (SIZE(0..36)) 3129 MAX-ACCESS not-accessible 3130 STATUS current 3131 DESCRIPTION 3132 "The IP address to which this entry's addressing information 3133 pertains." 3134 ::= { ipAddressEntry 2 } 3136 ipAddressIfIndex OBJECT-TYPE 3137 SYNTAX InterfaceIndex 3138 MAX-ACCESS read-only 3139 STATUS current 3140 DESCRIPTION 3141 "The index value which uniquely identifies the interface to 3142 which this entry is applicable. The interface identified by 3143 a particular value of this index is the same interface as 3144 identified by the same value of the IF-MIB's ifIndex." 3145 ::= { ipAddressEntry 3 } 3147 ipAddressType OBJECT-TYPE 3148 SYNTAX INTEGER { 3149 unicast(1), 3150 anycast(2), 3151 broadcast(3) 3152 } 3153 MAX-ACCESS read-only 3154 STATUS current 3155 DESCRIPTION 3156 "The type of address. broadcast(3) is not a valid value for 3157 IPv6 addresses (RFC3513). " 3158 ::= { ipAddressEntry 4 } 3160 ipAddressPrefix OBJECT-TYPE 3161 SYNTAX RowPointer 3162 MAX-ACCESS read-only 3163 STATUS current 3164 DESCRIPTION 3165 "A pointer to the row in the prefix table to which this 3166 address belongs. May be { 0 0 } if there is no such row." 3167 ::= { ipAddressEntry 5 } 3169 ipAddressOrigin OBJECT-TYPE 3170 SYNTAX IpAddressOrigin 3171 MAX-ACCESS read-only 3172 STATUS current 3173 DESCRIPTION 3174 "The origin of the address." 3175 ::= { ipAddressEntry 6 } 3177 ipAddressStatus OBJECT-TYPE 3178 SYNTAX IpAddressStatus 3179 MAX-ACCESS read-only 3180 STATUS current 3181 DESCRIPTION 3182 "The status of the address, describing if the address can be 3183 used for communication. 3185 In the absence of other information, an IPv4 address is 3186 always preferred(1)." 3187 ::= { ipAddressEntry 7 } 3189 ipAddressCreated OBJECT-TYPE 3190 SYNTAX TimeStamp 3191 MAX-ACCESS read-only 3192 STATUS current 3193 DESCRIPTION 3194 "The value of sysUpTime at the time this entry was created. 3195 If this entry was created prior to the last re- 3196 initialization of the local network management subsystem, 3197 then this object contains a zero value." 3198 ::= { ipAddressEntry 8 } 3200 ipAddressLastChanged OBJECT-TYPE 3201 SYNTAX TimeStamp 3202 MAX-ACCESS read-only 3203 STATUS current 3204 DESCRIPTION 3205 "The value of sysUpTime at the time this entry was last 3206 updated. If this entry was updated prior to the last re- 3207 initialization of the local network management subsystem, 3208 then this object contains a zero value." 3209 ::= { ipAddressEntry 9 } 3211 -- 3212 -- the Internet Address Translation table 3213 -- 3215 inetNetToMediaTable OBJECT-TYPE 3216 SYNTAX SEQUENCE OF InetNetToMediaEntry 3217 MAX-ACCESS not-accessible 3218 STATUS current 3219 DESCRIPTION 3220 "The IP Address Translation table used for mapping from IP 3221 addresses to physical addresses. 3223 The Address Translation tables contain the IP address to 3224 'physical' address equivalences. Some interfaces do not use 3225 translation tables for determining address equivalences 3226 (e.g., DDN-X.25 has an algorithmic method); if all 3227 interfaces are of this type, then the Address Translation 3228 table is empty, i.e., has zero entries. 3230 While many protocols may be used to populate this table, ARP 3231 [9] and Neighbor Discovery [4] are the most likely options." 3232 ::= { ip 34 } 3234 inetNetToMediaEntry OBJECT-TYPE 3235 SYNTAX InetNetToMediaEntry 3236 MAX-ACCESS not-accessible 3237 STATUS current 3238 DESCRIPTION 3239 "Each entry contains one IP address to `physical' address 3240 equivalence." 3241 INDEX { inetNetToMediaIfIndex, 3242 inetNetToMediaNetAddressType, 3243 inetNetToMediaNetAddress } 3244 ::= { inetNetToMediaTable 1 } 3246 InetNetToMediaEntry ::= SEQUENCE { 3247 inetNetToMediaIfIndex InterfaceIndex, 3248 inetNetToMediaNetAddressType InetAddressType, 3249 inetNetToMediaNetAddress InetAddress, 3250 inetNetToMediaPhysAddress PhysAddress, 3251 inetNetToMediaLastUpdated TimeStamp, 3252 inetNetToMediaType INTEGER, 3253 inetNetToMediaState INTEGER 3254 } 3256 inetNetToMediaIfIndex OBJECT-TYPE 3257 SYNTAX InterfaceIndex 3258 MAX-ACCESS not-accessible 3259 STATUS current 3260 DESCRIPTION 3261 "The index value which uniquely identifies the interface to 3262 which this entry is applicable. The interface identified by 3263 a particular value of this index is the same interface as 3264 identified by the same value of the IF-MIB's ifIndex." 3265 ::= { inetNetToMediaEntry 1 } 3267 inetNetToMediaNetAddressType OBJECT-TYPE 3268 SYNTAX InetAddressType 3269 MAX-ACCESS not-accessible 3270 STATUS current 3271 DESCRIPTION 3272 "The type of inetNetToMediaNetAddress." 3273 ::= { inetNetToMediaEntry 2 } 3275 inetNetToMediaNetAddress OBJECT-TYPE 3276 SYNTAX InetAddress (SIZE(0..36)) 3277 MAX-ACCESS not-accessible 3278 STATUS current 3279 DESCRIPTION 3280 "The IP Address corresponding to the media-dependent 3281 `physical' address." 3282 ::= { inetNetToMediaEntry 3 } 3284 inetNetToMediaPhysAddress OBJECT-TYPE 3285 SYNTAX PhysAddress 3286 MAX-ACCESS read-create 3287 STATUS current 3288 DESCRIPTION 3289 "The media-dependent `physical' address. 3291 As the entries in this table are typically not persistent 3292 when this object is written the entity SHOULD NOT save the 3293 change to non-volatile storage." 3294 ::= { inetNetToMediaEntry 4 } 3296 inetNetToMediaLastUpdated OBJECT-TYPE 3297 SYNTAX TimeStamp 3298 MAX-ACCESS read-only 3299 STATUS current 3300 DESCRIPTION 3301 "The value of sysUpTime at the time this entry was last 3302 updated. If this entry was updated prior to the last re- 3303 initialization of the local network management subsystem, 3304 then this object contains a zero value." 3305 ::= { inetNetToMediaEntry 5 } 3307 inetNetToMediaType OBJECT-TYPE 3308 SYNTAX INTEGER { 3309 other(1), -- none of the following 3310 invalid(2), -- an invalidated mapping 3311 dynamic(3), 3312 static(4), 3313 local(5) -- local interface 3314 } 3315 MAX-ACCESS read-create 3316 STATUS current 3317 DESCRIPTION 3318 "The type of mapping. 3320 Setting this object to the value invalid(2) has the effect 3321 of invalidating the corresponding entry in the 3322 inetNetToMediaTable. That is, it effectively dis-associates 3323 the interface identified with said entry from the mapping 3324 identified with said entry. It is an implementation- 3325 specific matter as to whether the agent removes an 3326 invalidated entry from the table. Accordingly, management 3327 stations must be prepared to receive tabular information 3328 from agents that corresponds to entries not currently in 3329 use. Proper interpretation of such entries requires 3330 examination of the relevant inetNetToMediaType object. 3332 The 'dynamic(3)' type indicates that the IP address to 3333 physical addresses mapping has been dynamically resolved 3334 using e.g. IPv4 ARP or the IPv6 Neighbor Discovery protocol. 3336 The 'static(4)' type indicates that the mapping has been 3337 statically configured. Both of these refer to entries that 3338 provide mappings for other entities addresses. 3340 The 'local(5)' type indicates that the mapping is provided 3341 for an entity's own interface address. 3343 As the entries in this table are typically not persistent 3344 when this object is written the entity SHOULD NOT save the 3345 change to non-volatile storage." 3346 ::= { inetNetToMediaEntry 6 } 3348 inetNetToMediaState OBJECT-TYPE 3349 SYNTAX INTEGER { 3350 reachable(1), -- confirmed reachability 3352 stale(2), -- unconfirmed reachability 3354 delay(3), -- waiting for reachability 3355 -- confirmation before entering 3356 -- the probe state 3358 probe(4), -- actively probing 3360 invalid(5), -- an invalidated mapping 3362 unknown(6), -- state can not be determined 3363 -- for some reason. 3365 incomplete(7) -- address resolution is being performed. 3366 } 3367 MAX-ACCESS read-only 3368 STATUS current 3369 DESCRIPTION 3370 "The Neighbor Unreachability Detection [4] state for the 3371 interface when the address mapping in this entry is used. 3372 If Neighbor Unreachability Detection is not in use (e.g. for 3373 IPv4), this object is always unknown(6)." 3374 REFERENCE "RFC2461" 3375 ::= { inetNetToMediaEntry 7 } 3377 -- 3378 -- The IPv6 Scope Zone Index Table. 3379 -- 3381 ipv6ScopeZoneIndexTable OBJECT-TYPE 3382 SYNTAX SEQUENCE OF Ipv6ScopeZoneIndexEntry 3383 MAX-ACCESS not-accessible 3384 STATUS current 3385 DESCRIPTION 3386 "The table used to describe IPv6 unicast and multicast scope 3387 zones." 3388 ::= { ip 35 } 3390 ipv6ScopeZoneIndexEntry OBJECT-TYPE 3391 SYNTAX Ipv6ScopeZoneIndexEntry 3392 MAX-ACCESS not-accessible 3393 STATUS current 3394 DESCRIPTION 3395 "Each entry contains the list of scope identifiers on a given 3396 interface." 3397 INDEX { ipv6ScopeZoneIndexIfIndex } 3398 ::= { ipv6ScopeZoneIndexTable 1 } 3400 Ipv6ScopeZoneIndexEntry ::= SEQUENCE { 3401 ipv6ScopeZoneIndexIfIndex InterfaceIndex, 3402 ipv6ScopeZoneIndexLinkLocal InetZoneIndex, 3403 ipv6ScopeZoneIndexSubnetLocal InetZoneIndex, 3404 ipv6ScopeZoneIndexAdminLocal InetZoneIndex, 3405 ipv6ScopeZoneIndexSiteLocal InetZoneIndex, 3406 ipv6ScopeZoneIndex6 InetZoneIndex, 3407 ipv6ScopeZoneIndex7 InetZoneIndex, 3408 ipv6ScopeZoneIndexOrganizationLocal InetZoneIndex, 3409 ipv6ScopeZoneIndex9 InetZoneIndex, 3410 ipv6ScopeZoneIndexA InetZoneIndex, 3411 ipv6ScopeZoneIndexB InetZoneIndex, 3412 ipv6ScopeZoneIndexC InetZoneIndex, 3413 ipv6ScopeZoneIndexD InetZoneIndex 3414 } 3416 ipv6ScopeZoneIndexIfIndex OBJECT-TYPE 3417 SYNTAX InterfaceIndex 3418 MAX-ACCESS not-accessible 3419 STATUS current 3420 DESCRIPTION 3421 "The index value which uniquely identifies the interface to 3422 which this these scopes belong. The interface identified by 3423 a particular value of this index is the same interface as 3424 identified by the same value of the IF-MIB's ifIndex." 3425 ::= { ipv6ScopeZoneIndexEntry 1 } 3427 ipv6ScopeZoneIndexLinkLocal OBJECT-TYPE 3428 SYNTAX InetZoneIndex 3429 MAX-ACCESS read-only 3430 STATUS current 3431 DESCRIPTION 3432 "The zone index for the link-local scope on this interface." 3433 ::= { ipv6ScopeZoneIndexEntry 2 } 3435 ipv6ScopeZoneIndexSubnetLocal OBJECT-TYPE 3436 SYNTAX InetZoneIndex 3437 MAX-ACCESS read-only 3438 STATUS current 3439 DESCRIPTION 3440 "The zone index for the subnet-local scope on this 3441 interface." 3442 ::= { ipv6ScopeZoneIndexEntry 3 } 3444 ipv6ScopeZoneIndexAdminLocal OBJECT-TYPE 3445 SYNTAX InetZoneIndex 3446 MAX-ACCESS read-only 3447 STATUS current 3448 DESCRIPTION 3449 "The zone index for the admin-local scope on this interface." 3450 ::= { ipv6ScopeZoneIndexEntry 4 } 3452 ipv6ScopeZoneIndexSiteLocal OBJECT-TYPE 3453 SYNTAX InetZoneIndex 3454 MAX-ACCESS read-only 3455 STATUS current 3456 DESCRIPTION 3457 "The zone index for the site-local scope on this interface." 3458 ::= { ipv6ScopeZoneIndexEntry 5 } 3460 ipv6ScopeZoneIndex6 OBJECT-TYPE 3461 SYNTAX InetZoneIndex 3462 MAX-ACCESS read-only 3463 STATUS current 3464 DESCRIPTION 3465 "The zone index for scope 6 on this interface." 3466 ::= { ipv6ScopeZoneIndexEntry 6 } 3468 ipv6ScopeZoneIndex7 OBJECT-TYPE 3469 SYNTAX InetZoneIndex 3470 MAX-ACCESS read-only 3471 STATUS current 3472 DESCRIPTION 3473 "The zone index for scope 7 on this interface." 3474 ::= { ipv6ScopeZoneIndexEntry 7 } 3476 ipv6ScopeZoneIndexOrganizationLocal OBJECT-TYPE 3477 SYNTAX InetZoneIndex 3478 MAX-ACCESS read-only 3479 STATUS current 3480 DESCRIPTION 3481 "The zone index for the organization-local scope on this 3482 interface." 3483 ::= { ipv6ScopeZoneIndexEntry 8 } 3485 ipv6ScopeZoneIndex9 OBJECT-TYPE 3486 SYNTAX InetZoneIndex 3487 MAX-ACCESS read-only 3488 STATUS current 3489 DESCRIPTION 3490 "The zone index for scope 9 on this interface." 3491 ::= { ipv6ScopeZoneIndexEntry 9 } 3493 ipv6ScopeZoneIndexA OBJECT-TYPE 3494 SYNTAX InetZoneIndex 3495 MAX-ACCESS read-only 3496 STATUS current 3497 DESCRIPTION 3498 "The zone index for scope A on this interface." 3499 ::= { ipv6ScopeZoneIndexEntry 10 } 3501 ipv6ScopeZoneIndexB OBJECT-TYPE 3502 SYNTAX InetZoneIndex 3503 MAX-ACCESS read-only 3504 STATUS current 3505 DESCRIPTION 3506 "The zone index for scope B on this interface." 3507 ::= { ipv6ScopeZoneIndexEntry 11 } 3509 ipv6ScopeZoneIndexC OBJECT-TYPE 3510 SYNTAX InetZoneIndex 3511 MAX-ACCESS read-only 3512 STATUS current 3513 DESCRIPTION 3514 "The zone index for scope C on this interface." 3515 ::= { ipv6ScopeZoneIndexEntry 12 } 3517 ipv6ScopeZoneIndexD OBJECT-TYPE 3518 SYNTAX InetZoneIndex 3519 MAX-ACCESS read-only 3520 STATUS current 3521 DESCRIPTION 3522 "The zone index for scope D on this interface." 3523 ::= { ipv6ScopeZoneIndexEntry 13 } 3525 -- 3526 -- The Default Router Table 3527 -- This table simply lists the default routers, for more information 3528 -- about routing tables see the routing MIBs 3529 -- 3531 ipDefaultRouterTable OBJECT-TYPE 3532 SYNTAX SEQUENCE OF IpDefaultRouterEntry 3533 MAX-ACCESS not-accessible 3534 STATUS current 3535 DESCRIPTION 3536 "The table used to describe the default routers known to this 3537 entity." 3538 ::= { ip 36 } 3540 ipDefaultRouterEntry OBJECT-TYPE 3541 SYNTAX IpDefaultRouterEntry 3542 MAX-ACCESS not-accessible 3543 STATUS current 3544 DESCRIPTION 3545 "Each entry contains information about a default router known 3546 to this entity." 3547 INDEX {ipDefaultRouterAFType, ipDefaultRouterAddress} 3548 ::= { ipDefaultRouterTable 1 } 3550 IpDefaultRouterEntry ::= SEQUENCE { 3551 ipDefaultRouterAFType InetAddressType, 3552 ipDefaultRouterAddress InetAddress, 3553 ipDefaultRouterIfIndex InterfaceIndex, 3554 ipDefaultRouterLifetime Unsigned32, 3555 ipDefaultRouterPreference INTEGER 3556 } 3558 ipDefaultRouterAFType OBJECT-TYPE 3559 SYNTAX InetAddressType 3560 MAX-ACCESS not-accessible 3561 STATUS current 3562 DESCRIPTION 3563 "The address type for this row." 3564 ::= { ipDefaultRouterEntry 1 } 3566 ipDefaultRouterAddress OBJECT-TYPE 3567 SYNTAX InetAddress (SIZE(0..36)) 3568 MAX-ACCESS not-accessible 3569 STATUS current 3570 DESCRIPTION 3571 "The IP address of the default router represented by this 3572 row." 3574 ::= { ipDefaultRouterEntry 2 } 3576 ipDefaultRouterIfIndex OBJECT-TYPE 3577 SYNTAX InterfaceIndex 3578 MAX-ACCESS read-only 3579 STATUS current 3580 DESCRIPTION 3581 "The index value which uniquely identifies the interface by 3582 which the router can be reached. The interface identified 3583 by a particular value of this index is the same interface as 3584 identified by the same value of the IF-MIB's ifIndex." 3585 ::= { ipDefaultRouterEntry 3 } 3587 ipDefaultRouterLifetime OBJECT-TYPE 3588 SYNTAX Unsigned32 (0..65535) 3589 UNITS "seconds" 3590 MAX-ACCESS read-only 3591 STATUS current 3592 DESCRIPTION 3593 "The length of time, in seconds, that this router will remain 3594 useful as a default router. A value of zero indicates that 3595 it is no longer useful as a default router. It is left to 3596 the implementor of the MIB as to whether a router with a 3597 lifetime of zero is removed from the list. 3599 For IPv6 this value should be extracted from the router 3600 advertisement messages. " 3601 REFERENCE "For IPv6 RFC2462 sections 4.2 and 6.3.4" 3602 ::= { ipDefaultRouterEntry 4 } 3604 ipDefaultRouterPreference OBJECT-TYPE 3605 SYNTAX INTEGER { 3606 medium (0), 3607 high (1), 3608 reserved (2), 3609 low (3) 3610 } 3611 MAX-ACCESS read-only 3612 STATUS current 3613 DESCRIPTION 3614 "An indication of preference given to this router as a 3615 default router. Treating the value as a 2 bit signed 3616 integer allows for simple arithmetic comparisons. 3618 For IPv4 routers or IPv6 routers that are not using the 3619 updated router advertisement format this object is set to 3620 medium (0)." 3621 REFERENCE "draft-ietf-ipv6-router-selection-02.txt, section 2.1" 3622 ::= { ipDefaultRouterEntry 5 } 3624 -- 3625 -- Configuration information for constructing router advertisements 3626 -- 3628 ipv6RouterAdvertSpinLock OBJECT-TYPE 3629 SYNTAX TestAndIncr 3630 MAX-ACCESS read-write 3631 STATUS current 3632 DESCRIPTION 3633 "An advisory lock used to allow cooperating SNMP managers to 3634 coordinate their use of the set operation in creating or 3635 modifying rows within this table. 3637 In order to use this lock to coordinate the use of set 3638 operations managers should first retrieve 3639 ipv6RouterAdvertSpinLock. They should then determine the 3640 appropriate row to create or modify. Finally they should 3641 issue the appropriate set command including the retrieved 3642 value of ipv6RouterAdvertSpinLock. If another manager has 3643 altered the table in the meantime, then the value of 3644 ipv6RouterAdvertSpinLock will have changed and the creation 3645 will fail as it will be specifying an incorrect value for 3646 ipv6RouterAdvertSpinLock. " 3647 ::= { ip 37 } 3649 ipv6RouterAdvertTable OBJECT-TYPE 3650 SYNTAX SEQUENCE OF Ipv6RouterAdvertEntry 3651 MAX-ACCESS not-accessible 3652 STATUS current 3653 DESCRIPTION 3654 "The table containing information used to construct router 3655 advertisements." 3656 ::= { ip 38 } 3658 ipv6RouterAdvertEntry OBJECT-TYPE 3659 SYNTAX Ipv6RouterAdvertEntry 3660 MAX-ACCESS not-accessible 3661 STATUS current 3662 DESCRIPTION 3663 "An entry containing information used to construct router 3664 advertisements. 3666 Information in this table is persistent and when this object 3667 is written the entity SHOULD save the change to non-volatile 3668 storage." 3670 INDEX { ipv6RouterAdvertIfIndex } 3671 ::= { ipv6RouterAdvertTable 1 } 3673 Ipv6RouterAdvertEntry ::= SEQUENCE { 3674 ipv6RouterAdvertIfIndex InterfaceIndex, 3675 ipv6RouterAdvertSendAdverts TruthValue, 3676 ipv6RouterAdvertMaxInterval Unsigned32, 3677 ipv6RouterAdvertMinInterval Unsigned32, 3678 ipv6RouterAdvertManagedFlag TruthValue, 3679 ipv6RouterAdvertOtherConfigFlag TruthValue, 3680 ipv6RouterAdvertLinkMTU Unsigned32, 3681 ipv6RouterAdvertReachableTime Unsigned32, 3682 ipv6RouterAdvertRetransmitTime Unsigned32, 3683 ipv6RouterAdvertCurHopLimit Unsigned32, 3684 ipv6RouterAdvertDefaultLifetime Unsigned32, 3685 ipv6RouterAdvertRowStatus RowStatus 3686 } 3688 ipv6RouterAdvertIfIndex OBJECT-TYPE 3689 SYNTAX InterfaceIndex 3690 MAX-ACCESS not-accessible 3691 STATUS current 3692 DESCRIPTION 3693 "The index value which uniquely identifies the interface on 3694 which router advertisements constructed with this 3695 information will be transmitted. The interface identified 3696 by a particular value of this index is the same interface as 3697 identified by the same value of the IF-MIB's ifIndex." 3698 ::= { ipv6RouterAdvertEntry 1 } 3700 ipv6RouterAdvertSendAdverts OBJECT-TYPE 3701 SYNTAX TruthValue 3702 MAX-ACCESS read-create 3703 STATUS current 3704 DESCRIPTION 3705 "A flag indicating whether or not the router sends periodic 3706 router advertisements and responds to router solicitations 3707 on this interface." 3708 REFERENCE "RFC2461 Section 6.2.1" 3709 DEFVAL { false } 3710 ::= { ipv6RouterAdvertEntry 2 } 3712 ipv6RouterAdvertMaxInterval OBJECT-TYPE 3713 SYNTAX Unsigned32 (4..1800) 3714 UNITS "seconds" 3715 MAX-ACCESS read-create 3716 STATUS current 3717 DESCRIPTION 3718 "The maximum time allowed between sending unsolicited router 3719 advertisements from this interface." 3720 REFERENCE "RFC2461 Section 6.2.1" 3721 DEFVAL { 600 } 3722 ::= { ipv6RouterAdvertEntry 3 } 3724 ipv6RouterAdvertMinInterval OBJECT-TYPE 3725 SYNTAX Unsigned32 (3..1350) 3726 UNITS "seconds" 3727 MAX-ACCESS read-create 3728 STATUS current 3729 DESCRIPTION 3730 "The minimum time allowed between sending unsolicited router 3731 advertisements from this interface. 3733 The default is 0.33 * ipv6RouterAdvertMaxInterval." 3734 REFERENCE "RFC2461 Section 6.2.1" 3735 ::= { ipv6RouterAdvertEntry 4 } 3737 ipv6RouterAdvertManagedFlag OBJECT-TYPE 3738 SYNTAX TruthValue 3739 MAX-ACCESS read-create 3740 STATUS current 3741 DESCRIPTION 3742 "The true/false value to be placed into the 'managed address 3743 configuration' flag field in router advertisements sent from 3744 this interface." 3745 REFERENCE "RFC2461 Section 6.2.1" 3746 DEFVAL { false } 3747 ::= { ipv6RouterAdvertEntry 5 } 3749 ipv6RouterAdvertOtherConfigFlag OBJECT-TYPE 3750 SYNTAX TruthValue 3751 MAX-ACCESS read-create 3752 STATUS current 3753 DESCRIPTION 3754 "The true/false value to be placed int the 'other stateful 3755 configuration' flag field in router advertisements sent from 3756 this interface." 3757 REFERENCE "RFC2461 Section 6.2.1" 3758 DEFVAL { false } 3759 ::= { ipv6RouterAdvertEntry 6 } 3761 ipv6RouterAdvertLinkMTU OBJECT-TYPE 3762 SYNTAX Unsigned32 3763 MAX-ACCESS read-create 3764 STATUS current 3765 DESCRIPTION 3766 "The value to be placed in MTU options sent by the router on 3767 this interface. 3769 A value of zero indicates that no MTU options are sent." 3770 REFERENCE "RFC2461 Section 6.2.1" 3771 DEFVAL { 0 } 3772 ::= { ipv6RouterAdvertEntry 7 } 3774 ipv6RouterAdvertReachableTime OBJECT-TYPE 3775 SYNTAX Unsigned32 (0..3600000) 3776 UNITS "milliseconds" 3777 MAX-ACCESS read-create 3778 STATUS current 3779 DESCRIPTION 3780 "The value to be placed in the reachable time field in router 3781 advertisement messages sent from this interface. 3783 A value of zero in the router advertisement indicates that 3784 the advertisement isn't specifying a value for reachable 3785 time." 3786 REFERENCE "RFC2461 Section 6.2.1" 3787 DEFVAL { 0 } 3788 ::= { ipv6RouterAdvertEntry 8 } 3790 ipv6RouterAdvertRetransmitTime OBJECT-TYPE 3791 SYNTAX Unsigned32 3792 UNITS "milliseconds" 3793 MAX-ACCESS read-create 3794 STATUS current 3795 DESCRIPTION 3796 "The value to be placed in the retransmit timer field in 3797 router advertisements sent from this interface. 3799 A value of zero in the router advertisement indicates that 3800 the advertisement isn't specifying a value for retrans 3801 time." 3802 REFERENCE "RFC2461 Section 6.2.1" 3803 DEFVAL { 0 } 3804 ::= { ipv6RouterAdvertEntry 9 } 3806 ipv6RouterAdvertCurHopLimit OBJECT-TYPE 3807 SYNTAX Unsigned32 (0..255) 3808 MAX-ACCESS read-create 3809 STATUS current 3810 DESCRIPTION 3811 "The default value to be placed in the current hop limit 3812 field in router advertisements sent from this interface. 3813 The value should be set to the current diameter of the 3814 Internet. 3816 A value of zero in the router advertisement indicates that 3817 the advertisement isn't specifying a value for curHopLimit. 3819 The default should be set to the value specified in the 3820 'Assigned Numbers' RFC that was in effect at the time of 3821 implementation." 3822 REFERENCE "RFC2461 Section 6.2.1" 3823 ::= { ipv6RouterAdvertEntry 10 } 3825 ipv6RouterAdvertDefaultLifetime OBJECT-TYPE 3826 SYNTAX Unsigned32 (0..65535) 3827 UNITS "seconds" 3828 MAX-ACCESS read-create 3829 STATUS current 3830 DESCRIPTION 3831 "The value to be placed in the router lifetime field of 3832 router advertisements sent from this interface. This value 3833 MUST be either 0 or between ipv6RouterAdvertMaxInterval and 3834 9000 seconds. 3836 A value of zero indicates that the router is not to be used 3837 as a default router. 3839 The default is 3 * ipv6RouterAdvertMaxInterval." 3840 REFERENCE "RFC2461 Section 6.2.1" 3841 ::= { ipv6RouterAdvertEntry 11 } 3843 ipv6RouterAdvertRowStatus OBJECT-TYPE 3844 SYNTAX RowStatus 3845 MAX-ACCESS read-create 3846 STATUS current 3847 DESCRIPTION 3848 "The status of this conceptual row. 3850 The RowStatus TC requires that this DESCRIPTION clause 3851 states under which circumstances other objects in this row 3852 can be modified. The value of this object has no effect on 3853 whether other objects in this conceptual row can be 3854 modified." 3855 ::= { ipv6RouterAdvertEntry 12 } 3857 -- 3858 -- ICMP section 3859 -- 3861 icmp OBJECT IDENTIFIER ::= { mib-2 5 } 3863 -- 3864 -- ICMP non-message-specific counters 3865 -- 3867 inetIcmpTable OBJECT-TYPE 3868 SYNTAX SEQUENCE OF InetIcmpEntry 3869 MAX-ACCESS not-accessible 3870 STATUS current 3871 DESCRIPTION 3872 "The table of generic system-wide ICMP counters." 3873 ::= { icmp 27 } 3875 inetIcmpEntry OBJECT-TYPE 3876 SYNTAX InetIcmpEntry 3877 MAX-ACCESS not-accessible 3878 STATUS current 3879 DESCRIPTION 3880 "A conceptual row in the inetIcmpTable." 3881 INDEX { inetIcmpAFType } 3882 ::= { inetIcmpTable 1 } 3884 InetIcmpEntry ::= SEQUENCE { 3885 inetIcmpAFType InetAddressType, 3886 inetIcmpInMsgs Counter32, 3887 inetIcmpInErrors Counter32, 3888 inetIcmpOutMsgs Counter32, 3889 inetIcmpOutErrors Counter32 3890 } 3892 inetIcmpAFType OBJECT-TYPE 3893 SYNTAX InetAddressType 3894 MAX-ACCESS not-accessible 3895 STATUS current 3896 DESCRIPTION 3897 "The IP address type of the statistics." 3898 ::= { inetIcmpEntry 1 } 3900 inetIcmpInMsgs OBJECT-TYPE 3901 SYNTAX Counter32 3902 MAX-ACCESS read-only 3903 STATUS current 3904 DESCRIPTION 3905 "The total number of ICMP messages which the entity received. 3906 Note that this counter includes all those counted by 3907 inetIcmpInErrors." 3908 ::= { inetIcmpEntry 2 } 3910 inetIcmpInErrors OBJECT-TYPE 3911 SYNTAX Counter32 3912 MAX-ACCESS read-only 3913 STATUS current 3914 DESCRIPTION 3915 "The number of ICMP messages which the entity received but 3916 determined as having ICMP-specific errors (bad ICMP 3917 checksums, bad length, etc.)." 3918 ::= { inetIcmpEntry 3 } 3920 inetIcmpOutMsgs OBJECT-TYPE 3921 SYNTAX Counter32 3922 MAX-ACCESS read-only 3923 STATUS current 3924 DESCRIPTION 3925 "The total number of ICMP messages which the entity received. 3926 Note that this counter includes all those counted by 3927 inetIcmpOutErrors." 3928 ::= { inetIcmpEntry 4 } 3930 inetIcmpOutErrors OBJECT-TYPE 3931 SYNTAX Counter32 3932 MAX-ACCESS read-only 3933 STATUS current 3934 DESCRIPTION 3935 "The number of ICMP messages which this entity did not send 3936 due to problems discovered within ICMP such as a lack of 3937 buffers. This value should not include errors discovered 3938 outside the ICMP layer such as the inability of IP to route 3939 the resultant datagram. In some implementations there may 3940 be no types of error which contribute to this counter's 3941 value." 3942 ::= { inetIcmpEntry 5 } 3944 -- 3945 -- per-AF, per-message type ICMP counters 3946 -- 3948 inetIcmpMsgTable OBJECT-TYPE 3949 SYNTAX SEQUENCE OF InetIcmpMsgEntry 3950 MAX-ACCESS not-accessible 3951 STATUS current 3952 DESCRIPTION 3953 "The table of system-wide per-AF per-message type ICMP 3954 counters." 3955 ::= { icmp 28 } 3957 inetIcmpMsgEntry OBJECT-TYPE 3958 SYNTAX InetIcmpMsgEntry 3959 MAX-ACCESS not-accessible 3960 STATUS current 3961 DESCRIPTION 3962 "A conceptual row in the inetIcmpMsgTable. 3964 The system should track each ICMP type value, even if that 3965 ICMP type is not supported by the system." 3966 INDEX { inetIcmpMsgAFType, inetIcmpMsgType } 3967 ::= { inetIcmpMsgTable 1 } 3969 InetIcmpMsgEntry ::= SEQUENCE { 3970 inetIcmpMsgAFType InetAddressType, 3971 inetIcmpMsgType Integer32, 3972 inetIcmpMsgInPkts Counter32, 3973 inetIcmpMsgOutPkts Counter32 3974 } 3976 inetIcmpMsgAFType OBJECT-TYPE 3977 SYNTAX InetAddressType 3978 MAX-ACCESS not-accessible 3979 STATUS current 3980 DESCRIPTION 3981 "The IP address type of the statistics." 3982 ::= { inetIcmpMsgEntry 1 } 3984 inetIcmpMsgType OBJECT-TYPE 3985 SYNTAX Integer32 (0..255) 3986 MAX-ACCESS not-accessible 3987 STATUS current 3988 DESCRIPTION 3989 "The ICMP type field of the message type being counted by 3990 this row. 3992 Note that ICMP message types are scoped by the address type 3993 in use." 3994 REFERENCE "http://www.iana.org/assignments/icmp-parameters and 3995 http://www.iana.org/assignments/icmpv6-parameters" 3996 ::= { inetIcmpMsgEntry 2 } 3998 inetIcmpMsgInPkts OBJECT-TYPE 3999 SYNTAX Counter32 4000 MAX-ACCESS read-only 4001 STATUS current 4002 DESCRIPTION 4003 "The number of input packets for this AF and type." 4004 ::= { inetIcmpMsgEntry 3 } 4006 inetIcmpMsgOutPkts OBJECT-TYPE 4007 SYNTAX Counter32 4008 MAX-ACCESS read-only 4009 STATUS current 4010 DESCRIPTION 4011 "The number of output packets for this AF and type." 4012 ::= { inetIcmpMsgEntry 4 } 4014 -- 4015 -- conformance information 4016 -- 4018 ipMIBConformance OBJECT IDENTIFIER ::= { ipMIB 2 } 4020 ipMIBCompliances OBJECT IDENTIFIER ::= { ipMIBConformance 1 } 4021 ipMIBGroups OBJECT IDENTIFIER ::= { ipMIBConformance 2 } 4023 -- compliance statements 4024 ipMIBCompliance2 MODULE-COMPLIANCE 4025 STATUS current 4026 DESCRIPTION 4027 "The compliance statement for systems which implement IP - either 4028 IPv4 or IPv6. 4030 There are a number of INDEX objects that cannot be represented in 4031 the form of OBJECT clauses in SMIv2, but for which we have the 4032 following compliance requirements, expressed in OBJECT clause form 4033 in this description clause: 4035 -- OBJECT ipSystemStatsAFType 4036 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 4037 -- DESCRIPTION 4038 -- This MIB requires support for only global IPv4 and IPv6 4039 -- address types. 4040 -- 4041 -- OBJECT ipIfStatsAFType 4042 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 4043 -- DESCRIPTION 4044 -- This MIB requires support for only global IPv4 and IPv6 4045 -- address types. 4047 -- 4048 -- OBJECT inetIcmpAFType 4049 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 4050 -- DESCRIPTION 4051 -- This MIB requires support for only global IPv4 and IPv6 4052 -- address types. 4053 -- 4054 -- OBJECT inetIcmpMsgAFType 4055 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 4056 -- DESCRIPTION 4057 -- This MIB requires support for only global IPv4 and IPv6 4058 -- address types. 4059 -- 4060 -- OBJECT ipAddressPrefixType 4061 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 4062 -- DESCRIPTION 4063 -- This MIB requires support for only global IPv4 and IPv6 4064 -- address types. 4065 -- 4066 -- OBJECT ipAddressAddrType 4067 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), 4068 -- ipv4z(3), ipv6z(4)} 4069 -- DESCRIPTION 4070 -- This MIB requires support for only global and non-global 4071 -- IPv4 and IPv6 address types. 4072 -- 4073 -- OBJECT inetNetToMediaNetAddressType 4074 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), 4075 -- ipv4z(3), ipv6z(4)} 4076 -- DESCRIPTION 4077 -- This MIB requires support for only global and non-global 4078 -- IPv4 and IPv6 address types. 4079 -- 4080 -- OBJECT ipDefaultRouterAFType 4081 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), 4082 -- ipv4z(3), ipv6z(4)} 4083 -- DESCRIPTION 4084 -- This MIB requires support for only global and non-global 4085 -- IPv4 and IPv6 address types. 4086 " 4088 MODULE -- this module 4090 MANDATORY-GROUPS { ipSystemStatsGroup, ipAddressGroup, 4091 ipNetToMediaGroup, ipDefaultRouterGroup, 4092 icmpGroup2 } 4094 GROUP ipSystemStatsHCOctetGroup 4095 DESCRIPTION 4096 "This group is mandatory for systems that have an aggregate 4097 bandwidth greater than 20MB." 4099 GROUP ipSystemStatsHCPacketGroup 4100 DESCRIPTION 4101 "This group is mandatory for systems that have an aggregate 4102 bandwidth greater than 650MB." 4104 GROUP ipIfStatsGroup 4105 DESCRIPTION 4106 "This group is optional for all systems." 4108 GROUP ipIfStatsHCOctetGroup 4109 DESCRIPTION 4110 "This group is mandatory for systems that include the 4111 ipIfStatsGroup and include links with bandwidths greater 4112 than 20MB." 4114 GROUP ipIfStatsHCPacketGroup 4115 DESCRIPTION 4116 "This group is mandatory for systems that include the 4117 ipIfStatsGroup and include links with bandwidths greater 4118 than 650MB." 4120 GROUP ipv4GeneralGroup 4121 DESCRIPTION 4122 "This group is mandatory for all systems supporting IPv4." 4124 GROUP ipv4IfGroup 4125 DESCRIPTION 4126 "This group is mandatory for all systems supporting IPv4." 4128 GROUP ipv6GeneralGroup2 4129 DESCRIPTION 4130 "This group is mandatory for all systems supporting IPv6." 4132 GROUP ipv6IfGroup 4133 DESCRIPTION 4134 "This group is mandatory for all systems supporting IPv6." 4136 GROUP ipAddressPrefixGroup 4137 DESCRIPTION 4138 "This group is mandatory for all systems supporting IPv6." 4140 GROUP ipv6ScopeGroup 4141 DESCRIPTION 4142 "This group is mandatory for all systems supporting IPv6." 4144 GROUP ipv6RouterAdvertGroup 4145 DESCRIPTION 4146 "This group is mandatory for all IPv6 routers." 4148 GROUP ipLastChangeGroup 4149 DESCRIPTION 4150 "This group is optional for all agents." 4152 OBJECT ip6Forwarding 4153 MIN-ACCESS read-only 4154 DESCRIPTION 4155 "An agent is not required to provide write access to this 4156 object" 4158 OBJECT ip6DefaultHopLimit 4159 MIN-ACCESS read-only 4160 DESCRIPTION 4161 "An agent is not required to provide write access to this 4162 object" 4164 OBJECT ipv4InterfaceAdminStatus 4165 MIN-ACCESS read-only 4166 DESCRIPTION 4167 "An agent is not required to provide write access to this 4168 object" 4170 OBJECT ipv6InterfaceAdminStatus 4171 MIN-ACCESS read-only 4172 DESCRIPTION 4173 "An agent is not required to provide write access to this 4174 object" 4176 OBJECT inetNetToMediaPhysAddress 4177 MIN-ACCESS read-only 4178 DESCRIPTION 4179 "An agent is not required to provide write or create access 4180 to this object" 4182 OBJECT inetNetToMediaType 4183 MIN-ACCESS read-only 4184 DESCRIPTION 4185 "An agent is not required to provide write or create access 4186 to this object" 4188 OBJECT ipv6RouterAdvertSpinLock 4189 MIN-ACCESS read-only 4190 DESCRIPTION 4191 "An agent is not required to provide write access to this 4192 object. However if an agent provides write access to any of 4193 the other objects in the ipv6RouterAdvertGroup it SHOULD 4194 provide write access to this object as well." 4196 OBJECT ipv6RouterAdvertSendAdverts 4197 MIN-ACCESS read-only 4198 DESCRIPTION 4199 "An agent is not required to provide write access to this 4200 object" 4202 OBJECT ipv6RouterAdvertMaxInterval 4203 MIN-ACCESS read-only 4204 DESCRIPTION 4205 "An agent is not required to provide write access to this 4206 object" 4208 OBJECT ipv6RouterAdvertMinInterval 4209 MIN-ACCESS read-only 4210 DESCRIPTION 4211 "An agent is not required to provide write access to this 4212 object" 4214 OBJECT ipv6RouterAdvertManagedFlag 4215 MIN-ACCESS read-only 4216 DESCRIPTION 4217 "An agent is not required to provide write access to this 4218 object" 4220 OBJECT ipv6RouterAdvertOtherConfigFlag 4221 MIN-ACCESS read-only 4222 DESCRIPTION 4223 "An agent is not required to provide write access to this 4224 object" 4226 OBJECT ipv6RouterAdvertLinkMTU 4227 MIN-ACCESS read-only 4228 DESCRIPTION 4229 "An agent is not required to provide write access to this 4230 object" 4232 OBJECT ipv6RouterAdvertReachableTime 4233 MIN-ACCESS read-only 4234 DESCRIPTION 4235 "An agent is not required to provide write access to this 4236 object" 4238 OBJECT ipv6RouterAdvertRetransmitTime 4239 MIN-ACCESS read-only 4240 DESCRIPTION 4241 "An agent is not required to provide write access to this 4242 object" 4244 OBJECT ipv6RouterAdvertCurHopLimit 4245 MIN-ACCESS read-only 4246 DESCRIPTION 4247 "An agent is not required to provide write access to this 4248 object" 4250 OBJECT ipv6RouterAdvertDefaultLifetime 4251 MIN-ACCESS read-only 4252 DESCRIPTION 4253 "An agent is not required to provide write access to this 4254 object" 4256 OBJECT ipv6RouterAdvertRowStatus 4257 MIN-ACCESS read-only 4258 DESCRIPTION 4259 "An agent is not required to provide write or create access 4260 to this object" 4262 ::= { ipMIBCompliances 2 } 4264 -- units of conformance 4266 ipv4GeneralGroup OBJECT-GROUP 4267 OBJECTS { ipForwarding, ipDefaultTTL, ipReasmTimeout } 4268 STATUS current 4269 DESCRIPTION 4270 "The group of IPv4-specific objects for basic management of 4271 IPv4 entities." 4272 ::= { ipMIBGroups 3 } 4274 ipv4IfGroup OBJECT-GROUP 4275 OBJECTS { ipv4InterfaceReasmMaxSize, ipv4InterfaceAdminStatus } 4276 STATUS current 4277 DESCRIPTION 4278 "The group of IPv4-specific objects for basic management of 4279 IPv4 interfaces." 4280 ::= { ipMIBGroups 4 } 4282 ipv6GeneralGroup2 OBJECT-GROUP 4283 OBJECTS { ip6Forwarding, ip6DefaultHopLimit } 4284 STATUS current 4285 DESCRIPTION 4286 "The IPv6 group of objects providing for basic management of 4287 IPv6 entities." 4288 ::= { ipMIBGroups 5 } 4290 ipv6IfGroup OBJECT-GROUP 4291 OBJECTS { ipv6InterfaceReasmMaxSize, ipv6InterfaceIdentifier, 4292 ipv6InterfacePhysicalAddress, ipv6InterfaceAdminStatus, 4293 ipv6InterfaceReachableTime, ipv6InterfaceRetransmitTime } 4294 STATUS current 4295 DESCRIPTION 4296 "The group of IPv6-specific objects for basic management of 4297 IPv6 interfaces." 4298 ::= { ipMIBGroups 6 } 4300 ipLastChangeGroup OBJECT-GROUP 4301 OBJECTS { ipv4IfTableLastChange, ipv6IfTableLastChange, 4302 ipIfStatsTableLastChange } 4303 STATUS current 4304 DESCRIPTION 4305 "The last change objects associated with this MIB. These 4306 objects are optional for all agents. They SHOULD be 4307 implemented on agents where it is possible to determine the 4308 proper values. Where it is not possible to determine the 4309 proper values, for example when the tables are split amongst 4310 several sub-agents using AgentX, the agent MUST NOT 4311 implement these objects to return an incorrect or static 4312 value." 4313 ::= { ipMIBGroups 7 } 4315 ipSystemStatsGroup OBJECT-GROUP 4316 OBJECTS { ipSystemStatsInReceives, ipSystemStatsInOctets, 4317 ipSystemStatsInHdrErrors, ipSystemStatsInNoRoutes, 4318 ipSystemStatsInAddrErrors, ipSystemStatsInUnknownProtos, 4319 ipSystemStatsInTruncatedPkts, ipSystemStatsInForwDatagrams, 4320 ipSystemStatsReasmReqds, ipSystemStatsReasmOKs, 4321 ipSystemStatsReasmFails, ipSystemStatsInDiscards, 4322 ipSystemStatsInDelivers, ipSystemStatsOutRequests, 4323 ipSystemStatsOutNoRoutes, ipSystemStatsOutForwDatagrams, 4324 ipSystemStatsOutDiscards, ipSystemStatsOutFragReqds, 4325 ipSystemStatsOutFragOKs, ipSystemStatsOutFragFails, 4326 ipSystemStatsOutFragCreates, ipSystemStatsOutTransmits, 4327 ipSystemStatsOutOctets, ipSystemStatsInMcastPkts, 4328 ipSystemStatsInMcastOctets, ipSystemStatsOutMcastPkts, 4329 ipSystemStatsOutMcastOctets, ipSystemStatsInBcastPkts, 4330 ipSystemStatsOutBcastPkts, ipSystemStatsDiscontinuityTime, 4331 ipSystemStatsRefreshRate } 4332 STATUS current 4333 DESCRIPTION 4334 "IP system wide statistics." 4336 ::= { ipMIBGroups 8 } 4338 ipSystemStatsHCOctetGroup OBJECT-GROUP 4339 OBJECTS { ipSystemStatsHCInOctets, ipSystemStatsHCOutOctets, 4340 ipSystemStatsHCInMcastOctets, ipSystemStatsHCOutMcastOctets } 4341 STATUS current 4342 DESCRIPTION 4343 "IP system wide statistics for systems that may overflow the 4344 standard octet counters within 1 hour." 4345 ::= { ipMIBGroups 9 } 4347 ipSystemStatsHCPacketGroup OBJECT-GROUP 4348 OBJECTS { ipSystemStatsHCInReceives, ipSystemStatsHCOutTransmits, 4349 ipSystemStatsHCInMcastPkts, ipSystemStatsHCOutMcastPkts, 4350 ipSystemStatsHCInBcastPkts, ipSystemStatsHCOutBcastPkts } 4351 STATUS current 4352 DESCRIPTION 4353 "IP system wide statistics for systems that may overflow the 4354 standard packet counters within 1 hour." 4355 ::= { ipMIBGroups 10 } 4357 ipIfStatsGroup OBJECT-GROUP 4358 OBJECTS { ipIfStatsInReceives, ipIfStatsInOctets, 4359 ipIfStatsInHdrErrors, ipIfStatsInNoRoutes, 4360 ipIfStatsInAddrErrors, ipIfStatsInUnknownProtos, 4361 ipIfStatsInTruncatedPkts, ipIfStatsInForwDatagrams, 4362 ipIfStatsReasmReqds, ipIfStatsReasmOKs, 4363 ipIfStatsReasmFails, ipIfStatsInDiscards, 4364 ipIfStatsInDelivers, ipIfStatsOutRequests, 4365 ipIfStatsOutNoRoutes, ipIfStatsOutForwDatagrams, 4366 ipIfStatsOutDiscards, ipIfStatsOutFragReqds, 4367 ipIfStatsOutFragOKs, ipIfStatsOutFragFails, 4368 ipIfStatsOutFragCreates, ipIfStatsOutTransmits, 4369 ipIfStatsOutOctets, ipIfStatsInMcastPkts, 4370 ipIfStatsInMcastOctets, ipIfStatsOutMcastPkts, 4371 ipIfStatsOutMcastOctets, ipIfStatsInBcastPkts, 4372 ipIfStatsOutBcastPkts, ipIfStatsDiscontinuityTime, 4373 ipIfStatsRefreshRate } 4374 STATUS current 4375 DESCRIPTION 4376 "IP per-interface statistics." 4377 ::= { ipMIBGroups 11 } 4379 ipIfStatsHCOctetGroup OBJECT-GROUP 4380 OBJECTS { ipIfStatsHCInOctets, ipIfStatsHCOutOctets, 4381 ipIfStatsHCInMcastOctets, ipIfStatsHCOutMcastOctets } 4382 STATUS current 4383 DESCRIPTION 4384 "IP per-interfaces statistics for systems that include 4385 interfaces that may overflow the may overflow the standard 4386 octet counters within 1 hour." 4387 ::= { ipMIBGroups 12 } 4389 ipIfStatsHCPacketGroup OBJECT-GROUP 4390 OBJECTS { ipIfStatsHCInReceives, ipIfStatsHCOutTransmits, 4391 ipIfStatsHCInMcastPkts, ipIfStatsHCOutMcastPkts, 4392 ipIfStatsHCInBcastPkts, ipIfStatsHCOutBcastPkts } 4393 STATUS current 4394 DESCRIPTION 4395 "IP per-interfaces statistics for systems that includes 4396 interfaces that may overflow the standard packet counters 4397 within 1 hour." 4398 ::= { ipMIBGroups 13 } 4400 ipAddressPrefixGroup OBJECT-GROUP 4401 OBJECTS { ipAddressPrefixOrigin, 4402 ipAddressPrefixOnLinkFlag, 4403 ipAddressPrefixAutonomousFlag, 4404 ipAddressPrefixAdvPreferredLifetime, 4405 ipAddressPrefixAdvValidLifetime } 4406 STATUS current 4407 DESCRIPTION 4408 "The group of objects for providing information about address 4409 prefixes used by this node." 4410 ::= { ipMIBGroups 14 } 4412 ipAddressGroup OBJECT-GROUP 4413 OBJECTS { ipAddressIfIndex, ipAddressType, 4414 ipAddressPrefix, ipAddressOrigin, 4415 ipAddressStatus, ipAddressCreated, 4416 ipAddressLastChanged } 4417 STATUS current 4418 DESCRIPTION 4419 "The group of objects for providing information about the 4420 addresses relevant to this entity's interfaces." 4421 ::= { ipMIBGroups 15 } 4423 ipNetToMediaGroup OBJECT-GROUP 4424 OBJECTS { inetNetToMediaPhysAddress, inetNetToMediaLastUpdated, 4425 inetNetToMediaType, inetNetToMediaState } 4426 STATUS current 4427 DESCRIPTION 4428 "The group of objects for providing information about the 4429 mappings of network address to physical address known to 4430 this node." 4431 ::= { ipMIBGroups 16 } 4433 ipv6ScopeGroup OBJECT-GROUP 4434 OBJECTS { ipv6ScopeZoneIndexLinkLocal, ipv6ScopeZoneIndexSubnetLocal, 4435 ipv6ScopeZoneIndexAdminLocal, ipv6ScopeZoneIndexSiteLocal, 4436 ipv6ScopeZoneIndex6, ipv6ScopeZoneIndex7, 4437 ipv6ScopeZoneIndexOrganizationLocal, ipv6ScopeZoneIndex9, 4438 ipv6ScopeZoneIndexA, ipv6ScopeZoneIndexB, 4439 ipv6ScopeZoneIndexC, ipv6ScopeZoneIndexD } 4440 STATUS current 4441 DESCRIPTION 4442 "The group of objects for managing IPv6 scope zones." 4443 ::= { ipMIBGroups 17 } 4445 ipDefaultRouterGroup OBJECT-GROUP 4446 OBJECTS { ipDefaultRouterIfIndex, ipDefaultRouterLifetime, 4447 ipDefaultRouterPreference } 4448 STATUS current 4449 DESCRIPTION 4450 "The group of objects for providing information about default 4451 routers known to this node." 4452 ::= { ipMIBGroups 18 } 4454 ipv6RouterAdvertGroup OBJECT-GROUP 4455 OBJECTS { ipv6RouterAdvertSpinLock, ipv6RouterAdvertSendAdverts, 4456 ipv6RouterAdvertMaxInterval, ipv6RouterAdvertMinInterval, 4457 ipv6RouterAdvertManagedFlag, ipv6RouterAdvertOtherConfigFlag, 4458 ipv6RouterAdvertLinkMTU, ipv6RouterAdvertReachableTime, 4459 ipv6RouterAdvertRetransmitTime, ipv6RouterAdvertCurHopLimit, 4460 ipv6RouterAdvertDefaultLifetime, ipv6RouterAdvertRowStatus 4461 } 4462 STATUS current 4463 DESCRIPTION 4464 "The group of objects for controlling information advertised 4465 by IPv6 routers." 4466 ::= { ipMIBGroups 19 } 4468 icmpGroup2 OBJECT-GROUP 4469 OBJECTS {inetIcmpInMsgs, inetIcmpInErrors, inetIcmpOutMsgs, 4470 inetIcmpOutErrors, inetIcmpMsgInPkts, inetIcmpMsgOutPkts } 4471 STATUS current 4472 DESCRIPTION 4473 "The group of objects providing ICMP statistics." 4474 ::= { ipMIBGroups 20 } 4476 -- 4477 -- Deprecated objects 4478 -- 4480 ipInReceives OBJECT-TYPE 4481 SYNTAX Counter32 4482 MAX-ACCESS read-only 4483 STATUS deprecated 4484 DESCRIPTION 4485 "The total number of input datagrams received from 4486 interfaces, including those received in error." 4487 ::= { ip 3 } 4489 ipInHdrErrors OBJECT-TYPE 4490 SYNTAX Counter32 4491 MAX-ACCESS read-only 4492 STATUS deprecated 4493 DESCRIPTION 4494 "The number of input datagrams discarded due to errors in 4495 their IPv4 headers, including bad checksums, version number 4496 mismatch, other format errors, time-to-live exceeded, errors 4497 discovered in processing their IPv4 options, etc." 4498 ::= { ip 4 } 4500 ipInAddrErrors OBJECT-TYPE 4501 SYNTAX Counter32 4502 MAX-ACCESS read-only 4503 STATUS deprecated 4504 DESCRIPTION 4505 "The number of input datagrams discarded because the IPv4 4506 address in their IPv4 header's destination field was not a 4507 valid address to be received at this entity. This count 4508 includes invalid addresses (e.g., 0.0.0.0) and addresses of 4509 unsupported Classes (e.g., Class E). For entities which are 4510 not IPv4 routers and therefore do not forward datagrams, 4511 this counter includes datagrams discarded because the 4512 destination address was not a local address." 4513 ::= { ip 5 } 4515 ipForwDatagrams OBJECT-TYPE 4516 SYNTAX Counter32 4517 MAX-ACCESS read-only 4518 STATUS deprecated 4519 DESCRIPTION 4520 "The number of input datagrams for which this entity was not 4521 their final IPv4 destination, as a result of which an 4522 attempt was made to find a route to forward them to that 4523 final destination. In entities which do not act as IPv4 4524 routers, this counter will include only those packets which 4525 were Source-Routed via this entity, and the Source-Route 4526 option processing was successful." 4527 ::= { ip 6 } 4529 ipInUnknownProtos OBJECT-TYPE 4530 SYNTAX Counter32 4531 MAX-ACCESS read-only 4532 STATUS deprecated 4533 DESCRIPTION 4534 "The number of locally-addressed datagrams received 4535 successfully but discarded because of an unknown or 4536 unsupported protocol." 4537 ::= { ip 7 } 4539 ipInDiscards OBJECT-TYPE 4540 SYNTAX Counter32 4541 MAX-ACCESS read-only 4542 STATUS deprecated 4543 DESCRIPTION 4544 "The number of input IPv4 datagrams for which no problems 4545 were encountered to prevent their continued processing, but 4546 which were discarded (e.g., for lack of buffer space). Note 4547 that this counter does not include any datagrams discarded 4548 while awaiting re-assembly." 4549 ::= { ip 8 } 4551 ipInDelivers OBJECT-TYPE 4552 SYNTAX Counter32 4553 MAX-ACCESS read-only 4554 STATUS deprecated 4555 DESCRIPTION 4556 "The total number of input datagrams successfully delivered 4557 to IPv4 user-protocols (including ICMP)." 4558 ::= { ip 9 } 4560 ipOutRequests OBJECT-TYPE 4561 SYNTAX Counter32 4562 MAX-ACCESS read-only 4563 STATUS deprecated 4564 DESCRIPTION 4565 "The total number of IPv4 datagrams which local IPv4 user 4566 protocols (including ICMP) supplied to IPv4 in requests for 4567 transmission. Note that this counter does not include any 4568 datagrams counted in ipForwDatagrams." 4569 ::= { ip 10 } 4571 ipOutDiscards OBJECT-TYPE 4572 SYNTAX Counter32 4573 MAX-ACCESS read-only 4574 STATUS deprecated 4575 DESCRIPTION 4576 "The number of output IPv4 datagrams for which no problem was 4577 encountered to prevent their transmission to their 4578 destination, but which were discarded (e.g., for lack of 4579 buffer space). Note that this counter would include 4580 datagrams counted in ipForwDatagrams if any such packets met 4581 this (discretionary) discard criterion." 4582 ::= { ip 11 } 4584 ipOutNoRoutes OBJECT-TYPE 4585 SYNTAX Counter32 4586 MAX-ACCESS read-only 4587 STATUS deprecated 4588 DESCRIPTION 4589 "The number of IPv4 datagrams discarded because no route 4590 could be found to transmit them to their destination. Note 4591 that this counter includes any packets counted in 4592 ipForwDatagrams which meet this `no-route' criterion. Note 4593 that this includes any datagrams which a host cannot route 4594 because all of its default routers are down." 4595 ::= { ip 12 } 4597 ipReasmReqds OBJECT-TYPE 4598 SYNTAX Counter32 4599 MAX-ACCESS read-only 4600 STATUS deprecated 4601 DESCRIPTION 4602 "The number of IPv4 fragments received which needed to be 4603 reassembled at this entity." 4604 ::= { ip 14 } 4606 ipReasmOKs OBJECT-TYPE 4607 SYNTAX Counter32 4608 MAX-ACCESS read-only 4609 STATUS deprecated 4610 DESCRIPTION 4611 "The number of IPv4 datagrams successfully re-assembled." 4612 ::= { ip 15 } 4614 ipReasmFails OBJECT-TYPE 4615 SYNTAX Counter32 4616 MAX-ACCESS read-only 4617 STATUS deprecated 4618 DESCRIPTION 4619 "The number of failures detected by the IPv4 re-assembly 4620 algorithm (for whatever reason: timed out, errors, etc). 4621 Note that this is not necessarily a count of discarded IPv4 4622 fragments since some algorithms (notably the algorithm in 4623 RFC 815) can lose track of the number of fragments by 4624 combining them as they are received." 4626 ::= { ip 16 } 4628 ipFragOKs OBJECT-TYPE 4629 SYNTAX Counter32 4630 MAX-ACCESS read-only 4631 STATUS deprecated 4632 DESCRIPTION 4633 "The number of IPv4 datagrams that have been successfully 4634 fragmented at this entity." 4635 ::= { ip 17 } 4637 ipFragFails OBJECT-TYPE 4638 SYNTAX Counter32 4639 MAX-ACCESS read-only 4640 STATUS deprecated 4641 DESCRIPTION 4642 "The number of IPv4 datagrams that have been discarded 4643 because they needed to be fragmented at this entity but 4644 could not be, e.g., because their Don't Fragment flag was 4645 set." 4646 ::= { ip 18 } 4648 ipFragCreates OBJECT-TYPE 4649 SYNTAX Counter32 4650 MAX-ACCESS read-only 4651 STATUS deprecated 4652 DESCRIPTION 4653 "The number of IPv4 datagram fragments that have been 4654 generated as a result of fragmentation at this entity." 4655 ::= { ip 19 } 4657 ipRoutingDiscards OBJECT-TYPE 4658 SYNTAX Counter32 4659 MAX-ACCESS read-only 4660 STATUS deprecated 4661 DESCRIPTION 4662 "The number of routing entries which were chosen to be 4663 discarded even though they are valid. One possible reason 4664 for discarding such an entry could be to free-up buffer 4665 space for other routing entries. 4667 This object was defined in pre-IPv6 versions of the IP MIB. 4668 It was implicitly IPv4 only but the original specifications 4669 did not indicate this protocol restriction. In order to 4670 clarify the specifications this object has been deprecated 4671 and a similar, but more thourghly clarified, object has been 4672 added to the IP-FORWARD-MIB." 4673 ::= { ip 23 } 4675 -- the deprecated IPv4 address table 4677 ipAddrTable OBJECT-TYPE 4678 SYNTAX SEQUENCE OF IpAddrEntry 4679 MAX-ACCESS not-accessible 4680 STATUS deprecated 4681 DESCRIPTION 4682 "The table of addressing information relevant to this 4683 entity's IPv4 addresses." 4684 ::= { ip 20 } 4686 ipAddrEntry OBJECT-TYPE 4687 SYNTAX IpAddrEntry 4688 MAX-ACCESS not-accessible 4689 STATUS deprecated 4690 DESCRIPTION 4691 "The addressing information for one of this entity's IPv4 4692 addresses." 4693 INDEX { ipAdEntAddr } 4694 ::= { ipAddrTable 1 } 4696 IpAddrEntry ::= SEQUENCE { 4697 ipAdEntAddr IpAddress, 4698 ipAdEntIfIndex INTEGER, 4699 ipAdEntNetMask IpAddress, 4700 ipAdEntBcastAddr INTEGER, 4701 ipAdEntReasmMaxSize INTEGER 4702 } 4704 ipAdEntAddr OBJECT-TYPE 4705 SYNTAX IpAddress 4706 MAX-ACCESS read-only 4707 STATUS deprecated 4708 DESCRIPTION 4709 "The IPv4 address to which this entry's addressing 4710 information pertains." 4711 ::= { ipAddrEntry 1 } 4713 ipAdEntIfIndex OBJECT-TYPE 4714 SYNTAX INTEGER (1..2147483647) 4715 MAX-ACCESS read-only 4716 STATUS deprecated 4717 DESCRIPTION 4718 "The index value which uniquely identifies the interface to 4719 which this entry is applicable. The interface identified by 4720 a particular value of this index is the same interface as 4721 identified by the same value of the IF-MIB's ifIndex." 4723 ::= { ipAddrEntry 2 } 4725 ipAdEntNetMask OBJECT-TYPE 4726 SYNTAX IpAddress 4727 MAX-ACCESS read-only 4728 STATUS deprecated 4729 DESCRIPTION 4730 "The subnet mask associated with the IPv4 address of this 4731 entry. The value of the mask is an IPv4 address with all 4732 the network bits set to 1 and all the hosts bits set to 0." 4733 ::= { ipAddrEntry 3 } 4735 ipAdEntBcastAddr OBJECT-TYPE 4736 SYNTAX INTEGER (0..1) 4737 MAX-ACCESS read-only 4738 STATUS deprecated 4739 DESCRIPTION 4740 "The value of the least-significant bit in the IPv4 broadcast 4741 address used for sending datagrams on the (logical) 4742 interface associated with the IPv4 address of this entry. 4743 For example, when the Internet standard all-ones broadcast 4744 address is used, the value will be 1. This value applies to 4745 both the subnet and network broadcasts addresses used by the 4746 entity on this (logical) interface." 4747 ::= { ipAddrEntry 4 } 4749 ipAdEntReasmMaxSize OBJECT-TYPE 4750 SYNTAX INTEGER (0..65535) 4751 MAX-ACCESS read-only 4752 STATUS deprecated 4753 DESCRIPTION 4754 "The size of the largest IPv4 datagram which this entity can 4755 re-assemble from incoming IPv4 fragmented datagrams received 4756 on this interface." 4757 ::= { ipAddrEntry 5 } 4759 -- the deprecated IPv4 Address Translation table 4761 -- The Address Translation tables contain the IpAddress to 4762 -- "physical" address equivalences. Some interfaces do not 4763 -- use translation tables for determining address 4764 -- equivalences (e.g., DDN-X.25 has an algorithmic method); 4765 -- if all interfaces are of this type, then the Address 4766 -- Translation table is empty, i.e., has zero entries. 4768 ipNetToMediaTable OBJECT-TYPE 4769 SYNTAX SEQUENCE OF IpNetToMediaEntry 4770 MAX-ACCESS not-accessible 4771 STATUS deprecated 4772 DESCRIPTION 4773 "The IPv4 Address Translation table used for mapping from 4774 IPv4 addresses to physical addresses." 4775 ::= { ip 22 } 4777 ipNetToMediaEntry OBJECT-TYPE 4778 SYNTAX IpNetToMediaEntry 4779 MAX-ACCESS not-accessible 4780 STATUS deprecated 4781 DESCRIPTION 4782 "Each entry contains one IpAddress to `physical' address 4783 equivalence." 4784 INDEX { ipNetToMediaIfIndex, 4785 ipNetToMediaNetAddress } 4786 ::= { ipNetToMediaTable 1 } 4788 IpNetToMediaEntry ::= SEQUENCE { 4789 ipNetToMediaIfIndex INTEGER, 4790 ipNetToMediaPhysAddress PhysAddress, 4791 ipNetToMediaNetAddress IpAddress, 4792 ipNetToMediaType INTEGER 4793 } 4795 ipNetToMediaIfIndex OBJECT-TYPE 4796 SYNTAX INTEGER (1..2147483647) 4797 MAX-ACCESS read-create 4798 STATUS deprecated 4799 DESCRIPTION 4800 "The interface on which this entry's equivalence is 4801 effective. The interface identified by a particular value 4802 of this index is the same interface as identified by the 4803 same value of the IF-MIB's ifIndex." 4804 ::= { ipNetToMediaEntry 1 } 4806 ipNetToMediaPhysAddress OBJECT-TYPE 4807 SYNTAX PhysAddress 4808 MAX-ACCESS read-create 4809 STATUS deprecated 4810 DESCRIPTION 4811 "The media-dependent `physical' address. This object should 4812 return 0 when this entry is in the 'incomplete' state. 4814 As the entries in this table are typically not persistent 4815 when this object is written the entity should not save the 4816 change to non-volatile storage. Note: a stronger 4817 requirement is not used because this object was previously 4818 defined." 4819 ::= { ipNetToMediaEntry 2 } 4821 ipNetToMediaNetAddress OBJECT-TYPE 4822 SYNTAX IpAddress 4823 MAX-ACCESS read-create 4824 STATUS deprecated 4825 DESCRIPTION 4826 "The IpAddress corresponding to the media-dependent 4827 `physical' address." 4828 ::= { ipNetToMediaEntry 3 } 4830 ipNetToMediaType OBJECT-TYPE 4831 SYNTAX INTEGER { 4832 other(1), -- none of the following 4833 invalid(2), -- an invalidated mapping 4834 dynamic(3), 4835 static(4) 4836 } 4837 MAX-ACCESS read-create 4838 STATUS deprecated 4839 DESCRIPTION 4840 "The type of mapping. 4842 Setting this object to the value invalid(2) has the effect 4843 of invalidating the corresponding entry in the 4844 ipNetToMediaTable. That is, it effectively dis-associates 4845 the interface identified with said entry from the mapping 4846 identified with said entry. It is an implementation- 4847 specific matter as to whether the agent removes an 4848 invalidated entry from the table. Accordingly, management 4849 stations must be prepared to receive tabular information 4850 from agents that corresponds to entries not currently in 4851 use. Proper interpretation of such entries requires 4852 examination of the relevant ipNetToMediaType object. 4854 As the entries in this table are typically not persistent 4855 when this object is written the entity should not save the 4856 change to non-volatile storage. Note: a stronger 4857 requirement is not used because this object was previously 4858 defined." 4859 ::= { ipNetToMediaEntry 4 } 4861 -- the deprecated ICMP group 4863 icmpInMsgs OBJECT-TYPE 4864 SYNTAX Counter32 4865 MAX-ACCESS read-only 4866 STATUS deprecated 4867 DESCRIPTION 4868 "The total number of ICMP messages which the entity received. 4869 Note that this counter includes all those counted by 4870 icmpInErrors." 4871 ::= { icmp 1 } 4873 icmpInErrors OBJECT-TYPE 4874 SYNTAX Counter32 4875 MAX-ACCESS read-only 4876 STATUS deprecated 4877 DESCRIPTION 4878 "The number of ICMP messages which the entity received but 4879 determined as having ICMP-specific errors (bad ICMP 4880 checksums, bad length, etc.)." 4881 ::= { icmp 2 } 4883 icmpInDestUnreachs OBJECT-TYPE 4884 SYNTAX Counter32 4885 MAX-ACCESS read-only 4886 STATUS deprecated 4887 DESCRIPTION 4888 "The number of ICMP Destination Unreachable messages 4889 received." 4890 ::= { icmp 3 } 4892 icmpInTimeExcds OBJECT-TYPE 4893 SYNTAX Counter32 4894 MAX-ACCESS read-only 4895 STATUS deprecated 4896 DESCRIPTION 4897 "The number of ICMP Time Exceeded messages received." 4898 ::= { icmp 4 } 4900 icmpInParmProbs OBJECT-TYPE 4901 SYNTAX Counter32 4902 MAX-ACCESS read-only 4903 STATUS deprecated 4904 DESCRIPTION 4905 "The number of ICMP Parameter Problem messages received." 4906 ::= { icmp 5 } 4908 icmpInSrcQuenchs OBJECT-TYPE 4909 SYNTAX Counter32 4910 MAX-ACCESS read-only 4911 STATUS deprecated 4912 DESCRIPTION 4913 "The number of ICMP Source Quench messages received." 4914 ::= { icmp 6 } 4916 icmpInRedirects OBJECT-TYPE 4917 SYNTAX Counter32 4918 MAX-ACCESS read-only 4919 STATUS deprecated 4920 DESCRIPTION 4921 "The number of ICMP Redirect messages received." 4922 ::= { icmp 7 } 4924 icmpInEchos OBJECT-TYPE 4925 SYNTAX Counter32 4926 MAX-ACCESS read-only 4927 STATUS deprecated 4928 DESCRIPTION 4929 "The number of ICMP Echo (request) messages received." 4930 ::= { icmp 8 } 4932 icmpInEchoReps OBJECT-TYPE 4933 SYNTAX Counter32 4934 MAX-ACCESS read-only 4935 STATUS deprecated 4936 DESCRIPTION 4937 "The number of ICMP Echo Reply messages received." 4938 ::= { icmp 9 } 4940 icmpInTimestamps OBJECT-TYPE 4941 SYNTAX Counter32 4942 MAX-ACCESS read-only 4943 STATUS deprecated 4944 DESCRIPTION 4945 "The number of ICMP Timestamp (request) messages received." 4946 ::= { icmp 10 } 4948 icmpInTimestampReps OBJECT-TYPE 4949 SYNTAX Counter32 4950 MAX-ACCESS read-only 4951 STATUS deprecated 4952 DESCRIPTION 4953 "The number of ICMP Timestamp Reply messages received." 4954 ::= { icmp 11 } 4956 icmpInAddrMasks OBJECT-TYPE 4957 SYNTAX Counter32 4958 MAX-ACCESS read-only 4959 STATUS deprecated 4960 DESCRIPTION 4961 "The number of ICMP Address Mask Request messages received." 4962 ::= { icmp 12 } 4964 icmpInAddrMaskReps OBJECT-TYPE 4965 SYNTAX Counter32 4966 MAX-ACCESS read-only 4967 STATUS deprecated 4968 DESCRIPTION 4969 "The number of ICMP Address Mask Reply messages received." 4970 ::= { icmp 13 } 4972 icmpOutMsgs OBJECT-TYPE 4973 SYNTAX Counter32 4974 MAX-ACCESS read-only 4975 STATUS deprecated 4976 DESCRIPTION 4977 "The total number of ICMP messages which this entity 4978 attempted to send. Note that this counter includes all 4979 those counted by icmpOutErrors." 4980 ::= { icmp 14 } 4982 icmpOutErrors OBJECT-TYPE 4983 SYNTAX Counter32 4984 MAX-ACCESS read-only 4985 STATUS deprecated 4986 DESCRIPTION 4987 "The number of ICMP messages which this entity did not send 4988 due to problems discovered within ICMP such as a lack of 4989 buffers. This value should not include errors discovered 4990 outside the ICMP layer such as the inability of IP to route 4991 the resultant datagram. In some implementations there may 4992 be no types of error which contribute to this counter's 4993 value." 4994 ::= { icmp 15 } 4996 icmpOutDestUnreachs OBJECT-TYPE 4997 SYNTAX Counter32 4998 MAX-ACCESS read-only 4999 STATUS deprecated 5000 DESCRIPTION 5001 "The number of ICMP Destination Unreachable messages sent." 5002 ::= { icmp 16 } 5004 icmpOutTimeExcds OBJECT-TYPE 5005 SYNTAX Counter32 5006 MAX-ACCESS read-only 5007 STATUS deprecated 5008 DESCRIPTION 5009 "The number of ICMP Time Exceeded messages sent." 5010 ::= { icmp 17 } 5012 icmpOutParmProbs OBJECT-TYPE 5013 SYNTAX Counter32 5014 MAX-ACCESS read-only 5015 STATUS deprecated 5016 DESCRIPTION 5017 "The number of ICMP Parameter Problem messages sent." 5018 ::= { icmp 18 } 5020 icmpOutSrcQuenchs OBJECT-TYPE 5021 SYNTAX Counter32 5022 MAX-ACCESS read-only 5023 STATUS deprecated 5024 DESCRIPTION 5025 "The number of ICMP Source Quench messages sent." 5026 ::= { icmp 19 } 5028 icmpOutRedirects OBJECT-TYPE 5029 SYNTAX Counter32 5030 MAX-ACCESS read-only 5031 STATUS deprecated 5032 DESCRIPTION 5033 "The number of ICMP Redirect messages sent. For a host, this 5034 object will always be zero, since hosts do not send 5035 redirects." 5036 ::= { icmp 20 } 5038 icmpOutEchos OBJECT-TYPE 5039 SYNTAX Counter32 5040 MAX-ACCESS read-only 5041 STATUS deprecated 5042 DESCRIPTION 5043 "The number of ICMP Echo (request) messages sent." 5044 ::= { icmp 21 } 5046 icmpOutEchoReps OBJECT-TYPE 5047 SYNTAX Counter32 5048 MAX-ACCESS read-only 5049 STATUS deprecated 5050 DESCRIPTION 5051 "The number of ICMP Echo Reply messages sent." 5052 ::= { icmp 22 } 5054 icmpOutTimestamps OBJECT-TYPE 5055 SYNTAX Counter32 5056 MAX-ACCESS read-only 5057 STATUS deprecated 5058 DESCRIPTION 5059 "The number of ICMP Timestamp (request) messages sent." 5060 ::= { icmp 23 } 5062 icmpOutTimestampReps OBJECT-TYPE 5063 SYNTAX Counter32 5064 MAX-ACCESS read-only 5065 STATUS deprecated 5066 DESCRIPTION 5067 "The number of ICMP Timestamp Reply messages sent." 5068 ::= { icmp 24 } 5070 icmpOutAddrMasks OBJECT-TYPE 5071 SYNTAX Counter32 5072 MAX-ACCESS read-only 5073 STATUS deprecated 5074 DESCRIPTION 5075 "The number of ICMP Address Mask Request messages sent." 5076 ::= { icmp 25 } 5078 icmpOutAddrMaskReps OBJECT-TYPE 5079 SYNTAX Counter32 5080 MAX-ACCESS read-only 5081 STATUS deprecated 5082 DESCRIPTION 5083 "The number of ICMP Address Mask Reply messages sent." 5084 ::= { icmp 26 } 5086 -- deprecated conformance information 5087 -- deprecated compliance statements 5089 ipMIBCompliance MODULE-COMPLIANCE 5090 STATUS deprecated 5091 DESCRIPTION 5092 "The compliance statement for systems which implement only 5093 IPv4. For version-independence, this compliance statement 5094 is deprecated in favor of ipMIBCompliance2." 5095 MODULE -- this module 5096 MANDATORY-GROUPS { ipGroup, 5097 icmpGroup } 5098 ::= { ipMIBCompliances 1 } 5100 -- deprecated units of conformance 5101 ipGroup OBJECT-GROUP 5102 OBJECTS { ipForwarding, ipDefaultTTL, ipInReceives, 5103 ipInHdrErrors, ipInAddrErrors, ipForwDatagrams, 5104 ipInUnknownProtos, ipInDiscards, ipInDelivers, 5105 ipOutRequests, ipOutDiscards, ipOutNoRoutes, 5106 ipReasmTimeout, ipReasmReqds, ipReasmOKs, 5107 ipReasmFails, ipFragOKs, ipFragFails, 5108 ipFragCreates, ipAdEntAddr, ipAdEntIfIndex, 5109 ipAdEntNetMask, ipAdEntBcastAddr, ipAdEntReasmMaxSize, 5110 ipNetToMediaIfIndex, ipNetToMediaPhysAddress, 5111 ipNetToMediaNetAddress, ipNetToMediaType, ipRoutingDiscards } 5112 STATUS deprecated 5113 DESCRIPTION 5114 "The ip group of objects providing for basic management of IP 5115 entities, exclusive of the management of IP routes." 5116 ::= { ipMIBGroups 1 } 5118 icmpGroup OBJECT-GROUP 5119 OBJECTS { icmpInMsgs, icmpInErrors, 5120 icmpInDestUnreachs, icmpInTimeExcds, 5121 icmpInParmProbs, icmpInSrcQuenchs, 5122 icmpInRedirects, icmpInEchos, 5123 icmpInEchoReps, icmpInTimestamps, 5124 icmpInTimestampReps, icmpInAddrMasks, 5125 icmpInAddrMaskReps, icmpOutMsgs, 5126 icmpOutErrors, icmpOutDestUnreachs, 5127 icmpOutTimeExcds, icmpOutParmProbs, 5128 icmpOutSrcQuenchs, icmpOutRedirects, 5129 icmpOutEchos, icmpOutEchoReps, 5130 icmpOutTimestamps, icmpOutTimestampReps, 5131 icmpOutAddrMasks, icmpOutAddrMaskReps } 5132 STATUS deprecated 5133 DESCRIPTION 5134 "The icmp group of objects providing ICMP statistics." 5135 ::= { ipMIBGroups 2 } 5137 END 5139 6. Open Issues / To Do 5141 The MIB has been passed through a MIB checker (smilint and smicng) but 5142 will need another pass to ensure no errors crept in during editing. 5144 I have now added some lastChange objects to the ipv4 and ipv6 interface 5145 tables and the ipifstats table. Currently I have added these object to 5146 an optional conformance group, but made them a SHOULD for agents with 5147 the proper information. 5149 7. Acknowledgments 5151 This document contains objects modified from RFC 1213 [10], RFC 2011 5152 [11], RFC 2465 [12], and RFC 2466 [13]. 5154 8. References 5156 8.1. Normative 5158 [1] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 5159 and S. Waldbusser, "Structure of Management Information Version 2 5160 (SMIv2)", STD 58, RFC 2578, April 1999. 5162 [2] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 5163 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 5164 2579, April 1999. 5166 [3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 5167 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 5168 2580, April 1999. 5170 [4] Narten, T., E. Nordmark and W. Simpson, "Neighbor Discovery for IP 5171 Version 6 (IPv6)", RFC 2461, December 1998. 5173 [5] Thomson, S., T. Narten, "IPv6 Stateless Address Autoconfiguration", 5174 RFC 2462, December 1998. 5176 [6] McCloghrie, K., F. Kastenholz, "The Interfaces Group MIB", RFC 2863, 5177 June 2000. 5179 [7] Daniele, M., B. Haberman, S. Routhier, J. Schoenwaelder, "draft- 5180 ietf-ops-rfc3291bis-00.txt", RFC XXXX Month Year. (Placeholder for 5181 updated version including InetZoneIndex) 5183 8.2. Informative 5185 [8] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 5186 Applicability Statements for Internet-Standard Management 5187 Framework", RFC 3410, December 2002. 5189 [9] D. Plummer, "An Ethernet Address Resolution Protocol", RFC0826, 5190 November 1982. 5192 [10] Rose, M. and K. McCloghrie, "Management Information Base for 5193 Network Management of TCP/IP-based internets", RFC 1213, March 5194 1991. 5196 [11] K. McCloghrie, "SNMPv2 Management Information Base for the Internet 5197 Protocol using SMIv2", RFC 2011, November 1996. 5199 [12] Haskin, D. and S. Onishi, "Management Information Base for IP 5200 Version 6: Textual Conventions and General Group", RFC 2465, 5201 December 1998. 5203 [13] Haskin, D. and S. Onishi, "Management Information Base for IP 5204 Version 6: ICMPv6 Group", RFC 2466, December 1998. 5206 [14] Narten, T. and R. Draves, "Privacy Extensions for Stateless Address 5207 Autoconfiguration in IPv6", RFC 3041, January 2001. 5209 9. Security Considerations 5211 There are a number of management objects defined in this MIB module with 5212 a MAX-ACCESS clause of read-write and/or read-create. Such objects may 5213 be considered sensitive or vulnerable in some network environments. The 5214 support for SET operations in a non-secure environment without proper 5215 protection can have a negative effect on network operations. These are 5216 the tables and objects and their sensitivity/vulnerability: 5218 ipForwarding and ip6Forwarding - these objects allow a manager to 5219 enable or disable the routing functions on the entity. By 5220 disabling the routing functions an attacker would possibly be able 5221 to deny service to users. By enabling the routing functions an 5222 attacker could open open an conduit into an area. This might 5223 result in the area providing transit for packets it shouldn't or 5224 allow the attacker access to the area bypassing security 5225 safeguards. 5227 ipDefaultTTL and ip6DefaultHopLimit - these objects allow a manager 5228 to determine the diameter of the valid area for a packet. By 5229 decreasing the value of these objects an attacker could cause 5230 packets to be discarded before reaching their destinations. 5232 ipv4InterfaceAdminStatus and ipv6InterfaceAdminStatus - these 5233 objects allow a manager to enable or disable IPv4 and IPv6 on a 5234 specific interface. By enabling a protocol on an interface an 5235 attacker might be able to create an unsecured path into a node (or 5236 through it if routing is also enabled). By disabling a protocol on 5237 an interface an attacker might be able to force packets to be 5238 routed through some other interface or deny access to some or all 5239 of the network via that protocol. 5241 ipv6RouterAdvertTable - the objects in this table specify the 5242 information that a router should propagate in its routing 5243 advertisement messages. By modifying this information an attacker 5244 can interfere with the auto-configuration of all hosts on the link. 5245 Most modifications to this table will result in a denial of service 5246 to some or all hosts on the link. However two objects, 5247 ipv6RouterAdvertManagedFlag and ipv6RouterAdvertOtherConfigFlag, 5248 indicate if a host should acquire configuration information from 5249 some other source. By enabling these an attacker might be able to 5250 cause a host to retrieve its configuration information from a 5251 compromised source. 5253 inetNetToMediaPhysAddress and inetNetToMediaType - these objects 5254 specify information used to translate a network (IP) address into a 5255 media dependent address. By modifying these objects an attacker 5256 could disable communication with a node or divert messages from one 5257 node to another. However the attacker may be able to carry out a 5258 similar attack by simply responding to the ARP or ND requests made 5259 by the target node. 5261 Some of the readable objects in this MIB module (i.e., objects with a 5262 MAX-ACCESS other than not-accessible) may be considered sensitive or 5263 vulnerable in some network environments. It is thus important to 5264 control even GET access to these objects and possibly to even encrypt 5265 the values of these objects when sending them over the network via SNMP. 5266 These are the tables and objects and their sensitivity/vulnerability: 5268 Essentially all of the objects in this MIB could be considered 5269 sensitive as they report on the status of the IP modules within a 5270 system. However the ipSystemStatsTable, ipIfStatsTable and 5271 ipAddressTable are likely to be of most interest to an attacker. 5272 The statistics tables supply information about the quantity and 5273 type of traffic this node is processing and, especially for transit 5274 providers, may be considered sensitive. The address table provides 5275 a convenient list of all address in use by this node. Each address 5276 in isolation is unremarkable however the total list would allow an 5277 attacker to correlate otherwise unrelated traffic. For example an 5278 attacker might be able to correlate the a RFC 3041 [14] private 5279 address with known public addresses thus circumventing the 5280 intentions of RFC 3041. 5282 SNMP versions prior to SNMPv3 did not include adequate security. Even 5283 if the network itself is secure (for example by using IPSec), even then, 5284 there is no control as to who on the secure network is allowed to access 5285 and GET/SET (read/change/create/delete) the objects in this MIB module. 5287 It is RECOMMENDED that implementers consider the security features as 5288 provided by the SNMPv3 framework (see [8], section 8), including full 5289 support for the SNMPv3 cryptographic mechanisms (for authentication and 5290 privacy). 5292 Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. 5293 Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic 5294 security. It is then a customer/operator responsibility to ensure that 5295 the SNMP entity giving access to an instance of this MIB module, is 5296 properly configured to give access to the objects only to those 5297 principals (users) that have legitimate rights to indeed GET or SET 5298 (change/create/delete) them. 5300 10. Editor's Contact Information 5302 Shawn A. Routhier 5303 Wind River 5304 500 Wind River Way 5305 Alameda, CA 94501 5306 USA 5308 Email: sar@epilogue.com 5310 11. Authors 5311 This document was written by the IPv6 MIB revision design team: 5313 Bill Fenner, AT&T Labs -- Research 5314 Email: fenner@research.att.com 5316 Brian Haberman 5317 Email: bkhabs@nc.rr.com 5319 Shawn A. Routhier, Wind River 5320 Email: sar@epilogue.com 5322 Dave Thaler, Microsoft 5323 Email: dthaler@windows.microsoft 5325 This document updates parts of the MIBs from several other documents. 5326 RFC2011 is the previous update to the IP MIB. RFC2465 and RFC2466 are 5327 the first versions specifying IPv6 addresses and information. 5329 RFC2011: 5330 Keith McCloghrie, Cisco Systems (Editor) 5332 RFC2465 and RFC2466: 5333 Dimitry Haskin, Bay Networks 5335 Steve Onishi, Bay Networks 5337 12. Acknowledgments 5339 Reviews and other contributions were made by: 5341 Dario Acornero, Cisco Systems 5343 Mike MacFaden, Riverstone 5345 Keith McCloghrie, Cisco Systems 5347 Juergen Schoenwalder, TU Braunschweig 5349 Margaret Wasserman, Wind River 5351 13. Full Copyright Statement 5353 Copyright (C) The Internet Society (2003). All Rights Reserved. 5355 This document and translations of it may be copied and furnished to 5356 others, and derivative works that comment on or otherwise explain it or 5357 assist in its implementation may be prepared, copied, published and 5358 distributed, in whole or in part, without restriction of any kind, 5359 provided that the above copyright notice and this paragraph are included 5360 on all such copies and derivative works. However, this document itself 5361 may not be modified in any way, such as by removing the copyright notice 5362 or references to the Internet Society or other Internet organizations, 5363 except as needed for the purpose of developing Internet standards in 5364 which case the procedures for copyrights defined in the Internet 5365 Standards process must be followed, or as required to translate it into 5366 languages other than English. 5368 The limited permissions granted above are perpetual and will not be 5369 revoked by the Internet Society or its successors or assigns. 5371 This document and the information contained herein is provided on an "AS 5372 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 5373 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 5374 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 5375 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 5376 FITNESS FOR A PARTICULAR PURPOSE. 5378 14. RFC Editor Notes This section contains notes to the RFC Editor and 5379 should be removed as the document is converted into an RFC. 5381 In the module identity section of the MIB (beginning of section 5) the 5382 RFC number of this document must be added in the description field 5383 (replacing xxxx). 5385 In the references section (8.1) the reference to the ID for rfc3291bis 5386 must be replaced with a proper RFC (not yet issued as I write this.)