idnits 2.17.1 draft-haskin-onishi-ipv6-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-27) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 67 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 4 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 15 has weird spacing: '... This docum...' == Line 16 has weird spacing: '...working docum...' == Line 17 has weird spacing: '...working group...' == Line 18 has weird spacing: '... groups may ...' == Line 22 has weird spacing: '...-Drafts may ...' == (62 more instances...) -- 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 (October 1996) is 10056 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: '2' is defined on line 3075, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 3098, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '4') ** Obsolete normative reference: RFC 1905 (ref. '5') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1573 (ref. '6') (Obsoleted by RFC 2233) ** Obsolete normative reference: RFC 1883 (ref. '7') (Obsoleted by RFC 2460) -- Possible downref: Non-RFC (?) normative reference: ref. '8' Summary: 16 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet-Draft IPv6 MIB October 1996 3 Management Information Base for IP Version 6 4 6 Wed Oct 9 14:39:52 EDT 1996 8 Dimitry Haskin 9 Steve Onishi 11 Bay Networks, Inc. 13 Status of this Memo 15 This document is an Internet-Draft. Internet-Drafts are 16 working documents of the Internet Engineering Task Force 17 (IETF), its areas, and its working groups. Note that other 18 groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months. Internet-Drafts may be updated, replaced, or 23 obsoleted by other documents at any time. It is not 24 appropriate to use Internet-Drafts as reference material or to 25 cite them other than as a ``working draft'' or ``work in 26 progress.'' 28 To learn the current status of any Internet-Draft, please 29 check the ``1id-abstracts.txt'' listing contained in the 30 Internet-Drafts Shadow Directories on ftp.is.co.za (Africa), 31 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 32 ds.internic.net (US East Coast), or ftp.isi.edu (US West 33 Coast). 35 Abstract 37 This paper is intended to serve as a framework for definition 38 of IPv6 MIB objects. 40 This memo defines an experimental portion of the Management 41 Information Base (MIB) for use with network management 42 protocols in the IPv6-based internets. 44 This document specifies a MIB module in a manner that is both 45 compliant to the SNMPv2 SMI, and semantically identical to the 46 peer SNMPv1 definitions. 48 Table of Contents 50 1. The SNMPv2 Network Management Framework ............. 3 51 1.1 Object Definitions ................................ 3 52 2. Overview ............................................ 4 53 3. IPv6 Address Representation ......................... 5 54 4. Definition of Textual Conventions ................... 7 55 5. IPv6 MIB Definitions ................................ 9 56 5.1. The IPv6 General Group ............................ 9 57 5.2. The ICMPv6 Group .................................. 44 58 5.3. The UDP Group ..................................... 61 59 5.4. The TCP Group ..................................... 65 60 6. Acknowledgements .................................... 74 61 7. References .......................................... 74 62 8. Security Considerations ............................. 75 63 9. Authors' Addresses................................... 75 65 1. The SNMPv2 Network Management Framework 67 The SNMPv2 Network Management Framework presently consists of 68 three major components. They are: 70 o the SMI, described in RFC 1902 [1] - the mechanisms used 71 for describing and naming objects for the purpose of 72 management. 74 o the MIB-II, described in RFC 1213/STD 17 [3] - the core 75 set of managed objects for the Internet suite of 76 protocols. 78 o RFC 1157 [4] and RFC 1905 [5] which define two versions 79 of the protocol used for network access to managed 80 objects. 82 The Framework permits new objects to be defined for the 83 purpose of experimentation and evaluation. 85 1.1. Object Definitions 87 Managed objects are accessed via a virtual information store, 88 termed the Management Information Base or MIB. Objects in the 89 MIB are defined using the subset of Abstract Syntax Notation 90 One (ASN.1) defined in the SMI. In particular, each object 91 object type is named by an OBJECT IDENTIFIER, an 92 administratively assigned name. The object type together with 93 an object instance serves to uniquely identify a specific 94 instantiation of the object. For human convenience, we often 95 use a textual string, termed the descriptor, to refer to the 96 object type. 98 2. Overview 100 The objects in this MIB are arranged into the following 101 groups: 103 - IPv6 General 104 - ICMPv6 105 - UDP 106 - TCP 108 These groups are the basic unit of conformance: if the 109 semantics of a group is applicable to an implementation, then 110 it must implement all objects in that group. For example, an 111 implementation must implement the TCP group if and only if it 112 implements the TCP over IPv6 protocol. At minimum, 113 implementations must implement IPv6 General and ICMPv6 groups. 115 The IPv6 General group consists of 6 tables: 117 - ipv6IfTable 119 The IPv6 Interfaces table contains information on the 120 entity's IPv6 interfaces. 122 - ipv6IfStatsTable 124 This table contains information on the traffic 125 statistics of the entity's IPv6 interfaces. 127 - ipv6AddrPrefixTable 129 The IPv6 Address Prefix table contains information on 130 Address Prefixes that are associated with the entity's 131 IPv6 interfaces. 133 - ipv6AddrTable 135 This table contains the addressing information relevant 136 to the entity's IPv6 interfaces. 138 - ipv6RouteTable 140 The IPv6 routing table contains an entry for each valid 141 IPv6 unicast route that can be used for packet 142 forwarding determination. 144 - ipv6NetToMediaEntryTable 146 The IPv6 address translation table contain the IPv6 147 Address to `physical' address equivalences. 149 The ICMPv6 group consists of 1 table: 151 - ipv6IfIcmpTable 153 This table contains information on the ICMPv6 154 statistics of the entity's IPv6 interfaces. 156 The UDP group consists of 1 table: 158 - ipv6UdpTable 160 This table contains information on the entity's UDP 161 end-points on which a local application is currently 162 accepting datagrams. 164 The TCP group consists of 1 table: 166 - ipv6TcpConnTable 168 This table contains information about the entity's 169 existing TCP connections. 171 In addition to the object definitions, this document defines a 172 number of textual convention to represent object types that 173 are specific to IPv6. 175 3. IPv6 Address Representation 177 The IPv6 MIB defined in this memo uses an OCTET STRING of 178 length 16 to represent 128-bit IPv6 address in network byte- 179 order. This approach allows to implement IPv6 MIB without 180 requiring any changes to the SNMPv2 SMI and compliant SNMP 181 implementations. A drawback of this approach is that, if an 182 IPv6 address is used for the object instance identification, 183 16 sub-identifiers are used to form the instance-identifier. 185 An alternative approach would be to introduce a new object 186 type that represents an IPv6 address as a string of four 32- 187 bit unsigned integers. Only 4 sub-identifiers would be used 188 to form the instance-identifier from an IPv6 address. The 189 disadvantage of this solution is that it would require changes 190 to the SMI and SNMPv2 implementations to support IPv6 MIB. 192 4. Definition of Textual Conventions 194 IPV6-TC DEFINITIONS ::= BEGIN 196 IMPORTS 197 Integer32 FROM SNMPv2-SMI 198 TEXTUAL-CONVENTION FROM SNMPv2-TC; 200 -- IPv6 MIB sub-tree. 201 -- It is not the best but a convenient temporary place 202 -- for this identifier. 203 ipv6 OBJECT IDENTIFIER ::= {experimental XX} 205 -- definition of textual conventions 206 Ipv6Address ::= TEXTUAL-CONVENTION 207 DISPLAY-HINT "2x:" 208 STATUS current 209 DESCRIPTION 210 "This data type is used to model IPv6 addresses. 211 This is a binary string of 16 octets in network 212 byte-order." 213 SYNTAX OCTET STRING (SIZE (16)) 215 Ipv6AddressPrefix ::= TEXTUAL-CONVENTION 216 DISPLAY-HINT "2x:" 217 STATUS current 218 DESCRIPTION 219 "This data type is used to model IPv6 address 220 prefixes. This is a binary string of up to 16 221 octets in network byte-order." 222 SYNTAX OCTET STRING (SIZE (0..16)) 224 Ipv6AddressToken ::= TEXTUAL-CONVENTION 225 DISPLAY-HINT "2x:" 226 STATUS current 227 DESCRIPTION 228 "This data type is used to model IPv6 address 229 tokens. This is a binary string of up to 6 230 octets in network byte-order." 231 SYNTAX OCTET STRING (SIZE (0..6)) 233 Ipv6IfIndex ::= TEXTUAL-CONVENTION 234 DISPLAY-HINT "d" 235 STATUS current 236 DESCRIPTION 237 "A unique value, greater than zero, for each 238 interface or interface sub-layer in the managed 239 system. It is recommended that values are assigned 240 contiguously starting from 1. The value for each 241 interface sub-layer must remain constant at least 242 from one re-initialization of the entity's network 243 management system to the next re-initialization." 244 SYNTAX Integer32 (1..2147483647) 246 END 248 5. IPv6 MIB Definitions 250 5.1. The IPv6 General Group 252 IPV6-MIB DEFINITIONS ::= BEGIN 254 IMPORTS 255 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 256 Counter32, Integer32, Unsigned32 FROM SNMPv2-SMI 257 DisplayString, PhysAddress, TruthValue, TimeStamp, 258 VariablePointer, RowPointer FROM SNMPv2-TC 259 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 260 Ipv6IfIndex, Ipv6Address, Ipv6AddressPrefix, 261 ipv6, Ipv6AddressToken FROM IPV6-TC; 263 ipv6MIB MODULE-IDENTITY 264 LAST-UPDATED "9610042155Z" 265 ORGANIZATION "IETF IPv6 MIB Working Group" 266 CONTACT-INFO 267 " Dimitry Haskin 269 Postal: Bay Networks, Inc. 270 2 Federal St. 271 Billerica, MA 01821 272 US 274 Tel: +1-508-916-8124 275 E-mail: dhaskin@baynetworks.com 277 Steve Onishi 279 Postal: Bay Networks, Inc. 280 3 Federal Street 281 Billerica, MA 01821 282 US 284 Tel: +1-508-916-3816 285 E-mail: sonishi@baynetworks.com" 286 DESCRIPTION 287 "The MIB module for entities implementing the IPv6 288 protocol." 289 ::= { ipv6 1 } 291 -- the IPv6 general group 293 ipv6MIBObjects OBJECT IDENTIFIER ::= { ipv6MIB 1 } 295 ipv6Forwarding OBJECT-TYPE 296 SYNTAX INTEGER { 297 forwarding(1), -- acting as a router 299 -- NOT acting as 300 notForwarding(2) -- a router 301 } 302 MAX-ACCESS read-write 303 STATUS current 304 DESCRIPTION 305 "The indication of whether this entity is acting 306 as an IPv6 router in respect to the forwarding of 307 datagrams received by, but not addressed to, this 308 entity. IPv6 routers forward datagrams. IPv6 309 hosts do not (except those source-routed via the 310 host). 312 Note that for some managed nodes, this object may 313 take on only a subset of the values possible. 314 Accordingly, it is appropriate for an agent to 315 return a `badValue' response if a management 316 station attempts to change this object to an 317 inappropriate value." 318 ::= { ipv6MIBObjects 1 } 320 ipv6DefaultHopLimit OBJECT-TYPE 321 SYNTAX INTEGER(0..255) 322 MAX-ACCESS read-write 323 STATUS current 324 DESCRIPTION 325 "The default value inserted into the Hop Limit 326 field of the IPv6 header of datagrams originated at 327 this entity, whenever a Hop Limit value is not 328 supplied by the transport layer protocol." 329 DEFVAL { 60 } 330 ::= { ipv6MIBObjects 2 } 332 ipv6InReceives OBJECT-TYPE 333 SYNTAX Counter32 334 MAX-ACCESS read-only 335 STATUS current 336 DESCRIPTION 337 "The total number of input datagrams received from 338 interfaces, including those received in error." 339 ::= { ipv6MIBObjects 3 } 341 ipv6InHdrErrors OBJECT-TYPE 342 SYNTAX Counter32 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The total number of input datagrams discarded due 347 to errors in their IPv6 headers, including version 348 number mismatch, other format errors, hop count 349 exceeded, errors discovered in processing their 350 IPv6 options, etc." 351 ::= { ipv6MIBObjects 4 } 353 ipv6TooBigErrors OBJECT-TYPE 354 SYNTAX Counter32 355 MAX-ACCESS read-only 356 STATUS current 357 DESCRIPTION 358 "The total number of datagrams that could not be 359 forwarded because their size exceeded the Path MTU" 360 ::= { ipv6MIBObjects 5 } 362 ipv6InAddrErrors OBJECT-TYPE 363 SYNTAX Counter32 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "The total number of input datagrams discarded 368 because the IPv6 address in their IPv6 header's 369 destination field was not a valid address to be 370 received at this entity. This count includes 371 invalid addresses (e.g., ::0) and unsupported 372 addresses (e.g., addresses with unallocated 373 prefixes). For entities which are not IPv6 routers 374 and therefore do not forward datagrams, this 375 counter includes datagrams discarded because the 376 destination address was not a local address." 377 ::= { ipv6MIBObjects 6 } 379 ipv6TruncatedPkts OBJECT-TYPE 380 SYNTAX Counter32 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 384 "The total number of input datagrams discarded 385 because datagram frame didn't carry enough data" 386 ::= { ipv6MIBObjects 7 } 388 ipv6ForwDatagrams OBJECT-TYPE 389 SYNTAX Counter32 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The total number of input datagrams for which this 394 entity was not their final IPv6 destination, as a 395 result of which an attempt was made to find a 396 route to forward them to that final destination. 397 In entities which do not act as IPv6 routers, this 398 counter will include only those packets which were 399 Source-Routed via this entity, and the Source- 400 Route option processing was successful." 401 ::= { ipv6MIBObjects 8 } 403 ipv6InUnknownProtos OBJECT-TYPE 404 SYNTAX Counter32 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The total number of locally-addressed datagrams 409 received successfully but discarded because of an 410 unknown or unsupported protocol." 411 ::= { ipv6MIBObjects 9 } 413 ipv6InDiscards OBJECT-TYPE 414 SYNTAX Counter32 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "The total number of input IPv6 datagrams for which 419 no problems were encountered to prevent their 420 continued processing, but which were discarded 421 (e.g., for lack of buffer space). Note that this 422 counter does not include any datagrams discarded 423 while awaiting re-assembly." 424 ::= { ipv6MIBObjects 10 } 426 ipv6InDelivers OBJECT-TYPE 427 SYNTAX Counter32 428 MAX-ACCESS read-only 429 STATUS current 430 DESCRIPTION 431 "The total number of input datagrams successfully 432 delivered to IPv6 user-protocols (including 433 ICMPv6)." 434 ::= { ipv6MIBObjects 11 } 436 ipv6OutRequests OBJECT-TYPE 437 SYNTAX Counter32 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "The total number of IPv6 datagrams which local IPv6 442 user-protocols (including ICMPv6) supplied to IPv6 443 requests for transmission. Note that this counter 444 in does not include any datagrams counted in 445 ipv6ForwDatagrams." 446 ::= { ipv6MIBObjects 12 } 448 ipv6OutDiscards OBJECT-TYPE 449 SYNTAX Counter32 450 MAX-ACCESS read-only 451 STATUS current 452 DESCRIPTION 453 "The total number of output IPv6 datagrams for 454 which no problem was encountered to prevent their 455 transmission to their destination, but which were 456 discarded (e.g., for lack of buffer space). Note 457 that this counter would include datagrams counted 458 in ipv6ForwDatagrams if any such packets met this 459 discretionary) discard criterion." 460 ::= { ipv6MIBObjects 13 } 462 ipv6OutNoRoutes OBJECT-TYPE 463 SYNTAX Counter32 464 MAX-ACCESS read-only 465 STATUS current 466 DESCRIPTION 467 "The number of IPv6 datagrams discarded because 468 no route could be found to transmit them to their 469 destination. Note that this counter includes any 470 packets counted in ipv6ForwDatagrams which 471 meet this `no-route' criterion. Note that this 472 includes any datagrams which a host cannot route 473 because all of its default routers are down." 474 ::= { ipv6MIBObjects 14 } 476 ipv6ReasmTimeout OBJECT-TYPE 477 SYNTAX Unsigned32 478 UNITS "seconds" 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The maximum number of seconds which received 483 fragments are held while they are awaiting 484 reassembly at this entity." 485 ::= { ipv6MIBObjects 15 } 487 ipv6ReasmReqds OBJECT-TYPE 488 SYNTAX Counter32 489 MAX-ACCESS read-only 490 STATUS current 491 DESCRIPTION 492 "The number of IPv6 fragments received which needed 493 to be reassembled at this entity." 494 ::= { ipv6MIBObjects 16 } 496 ipv6ReasmOKs OBJECT-TYPE 497 SYNTAX Counter32 498 MAX-ACCESS read-only 499 STATUS current 500 DESCRIPTION 501 "The number of IPv6 datagrams successfully 502 reassembled." 503 ::= { ipv6MIBObjects 17 } 505 ipv6ReasmFails OBJECT-TYPE 506 SYNTAX Counter32 507 MAX-ACCESS read-only 508 STATUS current 509 DESCRIPTION 510 "The number of failures detected by the IPv6 re- 511 assembly algorithm (for whatever reason: timed 512 out, errors, etc). Note that this is not 513 necessarily a count of discarded IPv6 fragments 514 since some algorithms can lose track of the number 515 of fragments by combining them as they are 516 received." 517 ::= { ipv6MIBObjects 18 } 519 ipv6FragOKs OBJECT-TYPE 520 SYNTAX Counter32 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The number of IPv6 datagrams that have been 525 successfully fragmented at this entity." 526 ::= { ipv6MIBObjects 19 } 528 ipv6FragFails OBJECT-TYPE 529 SYNTAX Counter32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "The number of IPv6 datagrams that have been 534 discarded because they needed to be fragmented 535 at this entity but could not be." 536 ::= { ipv6MIBObjects 20 } 538 ipv6FragCreates OBJECT-TYPE 539 SYNTAX Counter32 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "The total number of IPv6 datagram fragments that 544 have been generated as a result of fragmentation 545 at this entity." 546 ::= { ipv6MIBObjects 21 } 548 ipv6InMcastPkts OBJECT-TYPE 549 SYNTAX Counter32 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The total number of multicast packets received 554 by this entity" 555 ::= { ipv6MIBObjects 22 } 557 ipv6OutMcastPkts OBJECT-TYPE 558 SYNTAX Counter32 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "The total number of multicast packets transmitted 563 by this entity" 564 ::= { ipv6MIBObjects 23 } 566 ipv6Interfaces OBJECT-TYPE 567 SYNTAX Unsigned32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The number of IPv6 interfaces (regardless of 572 their current state) present on this system." 573 ::= { ipv6MIBObjects 24 } 575 ipv6IfTableLastChange OBJECT-TYPE 576 SYNTAX TimeStamp 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "The value of sysUpTime at the time of the last 581 insertion or removal of an entry in the 582 ipv6IfTable. If the number of entries has been 583 unchanged since the last re-initialization of 584 the local network management subsystem, then this 585 object contains a zero value." 586 ::= { ipv6MIBObjects 25 } 588 -- the IPv6 Interfaces table 590 ipv6IfTable OBJECT-TYPE 591 SYNTAX SEQUENCE OF Ipv6IfEntry 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "The IPv6 Interfaces table contains information 596 on the entity's internetwork-layer interfaces. 597 An IPv6 interface constitutes a logical network 598 layer attachment to the layer immediately below 599 IPv6 including internet layer 'tunnels', such as 600 tunnels over IPv4 or IPv6 itself." 601 ::= { ipv6MIBObjects 26 } 603 ipv6IfEntry OBJECT-TYPE 604 SYNTAX Ipv6IfEntry 605 MAX-ACCESS not-accessible 606 STATUS current 607 DESCRIPTION 608 "An interface entry containing objects 609 about a particular IPv6 interface." 610 INDEX { ipv6IfIndex } 611 ::= { ipv6IfTable 1 } 613 Ipv6IfEntry ::= SEQUENCE { 614 ipv6IfIndex Ipv6IfIndex, 615 ipv6IfDescr DisplayString, 616 ipv6IfLowerLayer VariablePointer, 617 ipv6IfEffectiveMtu Unsigned32, 618 ipv6IfReasmMaxSize Unsigned32, 619 ipv6IfToken Ipv6AddressToken, 620 ipv6IfTokenLength INTEGER, 621 ipv6IfPhysicalAddress PhysAddress, 622 ipv6IfAdminStatus INTEGER, 623 ipv6IfOperStatus INTEGER, 624 ipv6IfLastChange TimeStamp 625 } 627 ipv6IfIndex OBJECT-TYPE 628 SYNTAX Ipv6IfIndex 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "A unique non-zero value identifying 633 the particular IPv6 interface." 634 ::= { ipv6IfEntry 1 } 636 ipv6IfDescr OBJECT-TYPE 637 SYNTAX DisplayString 638 MAX-ACCESS read-write 639 STATUS current 640 DESCRIPTION 641 "A textual string containing information about the 642 interface. This string may be set by the network 643 management system." 644 ::= { ipv6IfEntry 2 } 646 ipv6IfLowerLayer OBJECT-TYPE 647 SYNTAX VariablePointer 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "This object identifies the protocol layer over 652 which this network interface operates. If this 653 network interface operates over the data-link 654 layer, then the value of this object refers to an 655 instance of ifIndex [6]. If this network interface 656 operates over an IPv4 interface, the value of this 657 object refers to an instance of ipAdEntAddr [3]. 658 If this network interface operates over another 659 IPv6 interface, the value of this object refers to 660 an instance of ipv6IfIndex. If this network 661 interface is not currently operating over an active 662 protocol layer, then the value of this object 663 should be set to the OBJECT ID { 0 0 }." 664 ::= { ipv6IfEntry 3 } 666 ipv6IfEffectiveMtu OBJECT-TYPE 667 SYNTAX Unsigned32 668 UNITS "octets" 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "The size of the largest IPv6 packet which can be 673 sent/received on the interface, specified in 674 octets." 675 ::= { ipv6IfEntry 4 } 677 ipv6IfReasmMaxSize OBJECT-TYPE 678 SYNTAX Unsigned32 (0..65535) 679 UNITS "octets" 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "The size of the largest IPv6 datagram which this 684 entity can re-assemble from incoming IPv6 fragmented 685 datagrams received on this interface." 686 ::= { ipv6IfEntry 5 } 688 ipv6IfToken OBJECT-TYPE 689 SYNTAX Ipv6AddressToken 690 MAX-ACCESS read-write 691 STATUS current 692 DESCRIPTION 693 "The address token for this interface that is 694 (at least) unique on the link this interface is 695 attached to. The address token is combined with 696 an address prefix to form an interface address. 698 By default, the interface token is autoconfigured 699 according to the rules of the link type this 700 interface is attached to." 701 ::= { ipv6IfEntry 6 } 703 ipv6IfTokenLength OBJECT-TYPE 704 SYNTAX INTEGER (0..64) 705 UNITS "bits" 706 MAX-ACCESS read-write 707 STATUS current 708 DESCRIPTION 709 "The length of the address token in bits." 710 ::= { ipv6IfEntry 7 } 712 ipv6IfPhysicalAddress OBJECT-TYPE 713 SYNTAX PhysAddress 714 MAX-ACCESS read-only 715 STATUS current 716 DESCRIPTION 717 "The interface's physical address. For example, for 718 an IPv6 interface attached to an 802.x link, this 719 object normally contains a MAC address. Note that 720 in some cases this address may differ from the 721 address of the interface's protocol sub-layer. The 722 interface's media-specific MIB must define the bit 723 and byte ordering and the format of the value of 724 this object. For interfaces which do not have such 725 an address (e.g., a serial line), this object should 726 contain an octet string of zero length." 727 ::= { ipv6IfEntry 8 } 729 ipv6IfAdminStatus OBJECT-TYPE 730 SYNTAX INTEGER { 731 up(1), -- ready to pass packets 732 down(2) 733 } 734 MAX-ACCESS read-write 735 STATUS current 736 DESCRIPTION 737 "The desired state of the interface. When a managed 738 system initializes, all IPv6 interfaces start with 739 ipv6IfAdminStatus in the down(2) state. As a result 740 of either explicit management action or per 741 configuration information retained by the managed 742 system, ipv6IfAdminStatus is then changed to 743 the up(1) state (or remains in the down(2) state)." 744 ::= { ipv6IfEntry 9 } 746 ipv6IfOperStatus OBJECT-TYPE 747 SYNTAX INTEGER { 748 up(1), -- ready to pass packets 750 down(2), 752 tokenless(3), -- no interface token 754 -- status can not be determined 755 unknown(4), -- for some reason 757 notPresent(5) -- some component is missing 758 } 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The current operational state of the interface. 763 The tokenless(3) state indicates that no valid 764 address token is assigned to the interface. This 765 state usually indicates that the link-local interface 766 address failed Duplicate Address Detection. If 767 ipv6IfAdminStatus is down(2) then ipv6IfOperStatus 768 should be down(2). If ipv6IfAdminStatus is changed 769 to up(1) then ipv6IfOperStatus should change to up(1) 770 if the interface is ready to transmit and receive 771 network traffic; it should remain in the down(2) or 772 tokenless(3) state if and only if there is a fault 773 that prevents it from going to the up(1) state; it 774 should remain in the notPresent(5) state if 775 the interface has missing (typically, lower layer) 776 components." 777 ::= { ipv6IfEntry 10 } 779 ipv6IfLastChange OBJECT-TYPE 780 SYNTAX TimeStamp 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The value of sysUpTime at the time the interface 785 entered its current operational state. If the 786 current state was entered prior to the last 787 re-initialization of the local network management 788 subsystem, then this object contains a zero 789 value." 790 ::= { ipv6IfEntry 11 } 792 -- IPv6 Interface Statistics table 794 ipv6IfStatsTable OBJECT-TYPE 795 SYNTAX SEQUENCE OF Ipv6IfStatsEntry 796 MAX-ACCESS not-accessible 797 STATUS current 798 DESCRIPTION 799 "IPv6 interface traffic statistics" 800 ::= { ipv6MIBObjects 27 } 802 ipv6IfStatsEntry OBJECT-TYPE 803 SYNTAX Ipv6IfStatsEntry 804 MAX-ACCESS not-accessible 805 STATUS current 806 DESCRIPTION 807 "An interface statistics entry containing objects 808 at a particular IPv6 interface." 809 AUGMENTS { ipv6IfEntry } 810 ::= { ipv6IfStatsTable 1 } 812 Ipv6IfStatsEntry ::= SEQUENCE { 813 ipv6IfStatsInReceives 814 Counter32, 815 ipv6IfStatsInHdrErrors 816 Counter32, 817 ipv6IfStatsTooBigErrors 818 Counter32, 819 ipv6IfStatsInAddrErrors 820 Counter32, 821 ipv6IfStatsForwDatagrams 822 Counter32, 823 ipv6IfStatsInUnknownProtos 824 Counter32, 825 ipv6IfStatsInDiscards 826 Counter32, 827 ipv6IfStatsInDelivers 828 Counter32, 830 ipv6IfStatsOutRequests 831 Counter32, 832 ipv6IfStatsOutDiscards 833 Counter32, 834 ipv6IfStatsOutNoRoutes 835 Counter32, 836 ipv6IfStatsReasmReqds 837 Counter32, 838 ipv6IfStatsReasmOKs 839 Counter32, 840 ipv6IfStatsReasmFails 841 Counter32, 842 ipv6IfStatsFragOKs 843 Counter32, 844 ipv6IfStatsFragFails 845 Counter32, 846 ipv6IfStatsFragCreates 847 Counter32, 848 ipv6IfStatsInMcastPkts 849 Counter32, 850 ipv6IfStatsOutMcastPkts 851 Counter32, 852 ipv6IfStatsInTruncatedPkts 853 Counter32 854 } 856 ipv6IfStatsInReceives OBJECT-TYPE 857 SYNTAX Counter32 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "The total number of input datagrams received from 862 interfaces, including those received in error." 863 ::= { ipv6IfStatsEntry 1 } 865 ipv6IfStatsInHdrErrors OBJECT-TYPE 866 SYNTAX Counter32 867 MAX-ACCESS read-only 868 STATUS current 869 DESCRIPTION 870 "The number of input datagrams discarded due to 871 errors in their IPv6 headers, including version 872 number mismatch, other format errors, hop count 873 exceeded, errors discovered in processing their 874 IPv6 options, etc." 876 ::= { ipv6IfStatsEntry 2 } 878 ipv6IfStatsTooBigErrors OBJECT-TYPE 879 SYNTAX Counter32 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The number of datagrams that could not be forwarded 884 because their size exceeded the Path MTU" 885 ::= { ipv6IfStatsEntry 3 } 887 ipv6IfStatsInAddrErrors OBJECT-TYPE 888 SYNTAX Counter32 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION 892 "The number of input datagrams discarded because 893 the IPv6 address in their IPv6 header's destination 894 field was not a valid address to be received at 895 this entity. This count includes invalid 896 addresses (e.g., ::0) and unsupported addresses 897 (e.g., addresses with unallocated prefixes). For 898 entities which are not IPv6 routers and therefore 899 do not forward datagrams, this counter includes 900 datagrams discarded because the destination address 901 was not a local address." 902 ::= { ipv6IfStatsEntry 4 } 904 ipv6IfStatsForwDatagrams OBJECT-TYPE 905 SYNTAX Counter32 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The number of input datagrams for which this 910 entity was not their final IPv6 destination, as a 911 result of which an attempt was made to find a 912 route to forward them to that final destination. 913 In entities which do not act as IPv6 routers, this 914 counter will include only those packets which were 915 Source-Routed via this entity, and the Source- 916 Route option processing was successful." 917 ::= { ipv6IfStatsEntry 5 } 919 ipv6IfStatsInUnknownProtos OBJECT-TYPE 920 SYNTAX Counter32 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "The number of locally-addressed datagrams 925 received successfully but discarded because of an 926 unknown or unsupported protocol." 927 ::= { ipv6IfStatsEntry 6 } 929 ipv6IfStatsInDiscards OBJECT-TYPE 930 SYNTAX Counter32 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "The number of input IPv6 datagrams for which no 935 problems were encountered to prevent their 936 continued processing, but which were discarded 937 (e.g., for lack of buffer space). Note that this 938 counter does not include any datagrams discarded 939 while awaiting re-assembly." 940 ::= { ipv6IfStatsEntry 7 } 942 ipv6IfStatsInDelivers OBJECT-TYPE 943 SYNTAX Counter32 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "The total number of input datagrams successfully 948 delivered to IPv6 user-protocols (including ICMP)." 949 ::= { ipv6IfStatsEntry 8 } 951 ipv6IfStatsOutRequests OBJECT-TYPE 952 SYNTAX Counter32 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "The total number of IPv6 datagrams which local IPv6 957 user-protocols (including ICMP) supplied to IPv6 in 958 requests for transmission. Note that this counter 959 does not include any datagrams counted in 960 ipv6IfStatsForwDatagrams." 961 ::= { ipv6IfStatsEntry 9 } 963 ipv6IfStatsOutDiscards OBJECT-TYPE 964 SYNTAX Counter32 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "The number of output IPv6 datagrams for which no 969 problem was encountered to prevent their 970 transmission to their destination, but which were 971 discarded (e.g., for lack of buffer space). Note 972 that this counter would include datagrams counted 973 in ipv6IfStatsForwDatagrams if any such packets 974 met this (discretionary) discard criterion." 975 ::= { ipv6IfStatsEntry 10 } 977 ipv6IfStatsOutNoRoutes OBJECT-TYPE 978 SYNTAX Counter32 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The number of IPv6 datagrams discarded because no 983 route could be found to transmit them to their 984 destination. Note that this counter includes any 985 packets counted in ipv6IfStatsForwDatagrams which 986 meet this `no-route' criterion. Note that this 987 includes any datagarms which a host cannot route 988 because all of its default routers are down." 989 ::= { ipv6IfStatsEntry 11 } 991 ipv6IfStatsReasmReqds OBJECT-TYPE 992 SYNTAX Counter32 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION 996 "The number of IPv6 fragments received which needed 997 to be reassembled at this entity." 998 ::= { ipv6IfStatsEntry 12 } 1000 ipv6IfStatsReasmOKs OBJECT-TYPE 1001 SYNTAX Counter32 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "The number of IPv6 datagrams successfully 1006 reassembled." 1007 ::= { ipv6IfStatsEntry 13 } 1009 ipv6IfStatsReasmFails OBJECT-TYPE 1010 SYNTAX Counter32 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "The number of failures detected by the IPv6 re- 1015 assembly algorithm (for whatever reason: timed 1016 out, errors, etc). Note that this is not 1017 necessarily a count of discarded IPv6 fragments 1018 since some algorithms (notably the algorithm in 1019 RFC 815) can lose track of the number of fragments 1020 by combining them as they are received." 1021 ::= { ipv6IfStatsEntry 14 } 1023 ipv6IfStatsFragOKs OBJECT-TYPE 1024 SYNTAX Counter32 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The number of IPv6 datagrams that have been 1029 successfully fragmented at this entity." 1030 ::= { ipv6IfStatsEntry 15 } 1032 ipv6IfStatsFragFails OBJECT-TYPE 1033 SYNTAX Counter32 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The number of IPv6 datagrams that have been 1038 discarded because they needed to be fragmented 1039 at this entity but could not be." 1040 ::= { ipv6IfStatsEntry 16 } 1042 ipv6IfStatsFragCreates OBJECT-TYPE 1043 SYNTAX Counter32 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "The number of IPv6 datagram fragments that have 1048 been generated as a result of fragmentation at 1049 this entity." 1050 ::= { ipv6IfStatsEntry 17 } 1052 ipv6IfStatsInMcastPkts OBJECT-TYPE 1053 SYNTAX Counter32 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "The number of multicast packets received 1058 by the interface" 1059 ::= { ipv6IfStatsEntry 18 } 1061 ipv6IfStatsOutMcastPkts OBJECT-TYPE 1062 SYNTAX Counter32 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION 1066 "The number of multicast packets transmitted 1067 by the interface" 1068 ::= { ipv6IfStatsEntry 19 } 1070 ipv6IfStatsInTruncatedPkts OBJECT-TYPE 1071 SYNTAX Counter32 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "The number of input datagrams discarded because 1076 datagram frame didn't carry enough data" 1077 ::= { ipv6IfStatsEntry 20 } 1079 -- Address Prefix table 1081 -- The IPv6 Address Prefix table contains information on 1082 -- the entity's IPv6 Address Prefixes that are associated 1083 -- with IPv6 interfaces. 1085 ipv6AddrPrefixTable OBJECT-TYPE 1086 SYNTAX SEQUENCE OF Ipv6AddrPrefixEntry 1087 MAX-ACCESS not-accessible 1088 STATUS current 1089 DESCRIPTION 1090 "The list of IPv6 address prefixes of 1091 IPv6 interfaces." 1092 ::= { ipv6MIBObjects 28 } 1094 ipv6AddrPrefixEntry OBJECT-TYPE 1095 SYNTAX Ipv6AddrPrefixEntry 1096 MAX-ACCESS not-accessible 1097 STATUS current 1098 DESCRIPTION 1099 "An interface entry containing objects of 1100 a particular IPv6 address prefix." 1101 INDEX { ipv6IfIndex, 1102 ipv6AddrPrefix, 1103 ipv6AddrPrefixLength } 1104 ::= { ipv6AddrPrefixTable 1 } 1106 Ipv6AddrPrefixEntry ::= SEQUENCE { 1107 ipv6AddrPrefix Ipv6AddressPrefix, 1108 ipv6AddrPrefixLength INTEGER (3..128), 1109 ipv6AddrPrefixOnLinkFlag TruthValue, 1110 ipv6AddrPrefixAutonomousFlag TruthValue, 1111 ipv6AddrPrefixAdvPreferredLifetime Unsigned32, 1112 ipv6AddrPrefixAdvValidLifetime Unsigned32 1113 } 1115 ipv6AddrPrefix OBJECT-TYPE 1116 SYNTAX Ipv6AddressPrefix 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "The prefix associated with the this interface." 1121 ::= { ipv6AddrPrefixEntry 1 } 1123 ipv6AddrPrefixLength OBJECT-TYPE 1124 SYNTAX INTEGER (3..128) 1125 UNITS "bits" 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "The length of the prefix (in bits). A prefix can 1130 not be shorter than 3 bits." 1131 ::= { ipv6AddrPrefixEntry 2 } 1133 ipv6AddrPrefixOnLinkFlag OBJECT-TYPE 1134 SYNTAX TruthValue 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "This object has the value 'true(1)', if that this 1139 prefix can be used for on-link determination and 1140 the value 'false(2)' otherwise." 1141 ::= { ipv6AddrPrefixEntry 3 } 1143 ipv6AddrPrefixAutonomousFlag OBJECT-TYPE 1144 SYNTAX TruthValue 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "Autonomous address configuration flag. When 1149 true(1), indicates that this prefix can be used 1150 for autonomous address configuration (i.e. can 1151 be used to form a local interface address). 1152 If false(2), it is not used to autoconfigure 1153 a local interface address." 1154 ::= { ipv6AddrPrefixEntry 4 } 1156 ipv6AddrPrefixAdvPreferredLifetime OBJECT-TYPE 1157 SYNTAX Unsigned32 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "It is the length of time in seconds that this 1162 prefix will remain preferred, i.e. time until 1163 deprecation. A value of 4,294,967,295 represents 1164 infinity. 1166 The address generated from a deprecated prefix 1167 should no longer be used as a source address in 1168 new communications, but packets received on such 1169 an interface are processed as expected." 1170 ::= { ipv6AddrPrefixEntry 5 } 1172 ipv6AddrPrefixAdvValidLifetime OBJECT-TYPE 1173 SYNTAX Unsigned32 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "It is the length of time in seconds that this 1178 prefix will remain valid, i.e. time until 1179 invalidation. A value of 4,294,967,295 represents 1180 infinity. 1182 The address generated from an invalidated prefix 1183 should not appear as the destination or source 1184 address of a packet." 1185 ::= { ipv6AddrPrefixEntry 6 } 1187 -- the IPv6 Address table 1188 -- The IPv6 address table contains this node's IPv6 1189 -- addressing information. 1191 ipv6AddrTable OBJECT-TYPE 1192 SYNTAX SEQUENCE OF Ipv6AddrEntry 1193 MAX-ACCESS not-accessible 1194 STATUS current 1195 DESCRIPTION 1196 "The table of addressing information relevant to 1197 this node's interface addresses." 1198 ::= { ipv6MIBObjects 29 } 1200 ipv6AddrEntry OBJECT-TYPE 1201 SYNTAX Ipv6AddrEntry 1202 MAX-ACCESS not-accessible 1203 STATUS current 1204 DESCRIPTION 1205 "The addressing information for one of this 1206 node's interface addresses." 1207 INDEX { ipv6IfIndex, ipv6AddrAddress } 1208 ::= { ipv6AddrTable 1 } 1210 Ipv6AddrEntry ::= 1211 SEQUENCE { 1212 ipv6AddrAddress Ipv6Address, 1213 ipv6AddrPfxLength INTEGER, 1214 ipv6AddrType INTEGER, 1215 ipv6AddrStatus INTEGER 1216 } 1218 ipv6AddrAddress OBJECT-TYPE 1219 SYNTAX Ipv6Address 1220 MAX-ACCESS not-accessible 1221 STATUS current 1222 DESCRIPTION 1223 "The IPv6 address to which this entry's addressing 1224 information pertains." 1225 ::= { ipv6AddrEntry 1 } 1227 ipv6AddrPfxLength OBJECT-TYPE 1228 SYNTAX INTEGER(0..128) 1229 UNITS "bits" 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "The length of the prefix (in bits) associated with 1234 the IPv6 address of this entry." 1235 ::= { ipv6AddrEntry 2 } 1237 ipv6AddrType OBJECT-TYPE 1238 SYNTAX INTEGER { 1239 -- address has been form 1240 -- using stateless 1241 stateless(1), -- autoconfiguration 1243 -- address has been acquired 1244 -- by stateful means 1245 -- (e.g. DHCPv6, manual 1246 stateful(2), -- configuration) 1248 -- type can not be determined 1249 unknown(3) -- for some reason. 1250 } 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "The type of address. Note that 'stateless(1)' 1255 refers to an address that was statelessly 1256 autoconfigured; 'stateful(2)' refers to a address 1257 which was acquired by via a stateful protocol 1258 (e.g. DHCPv6, manual configuration)." 1259 ::= { ipv6AddrEntry 3 } 1261 ipv6AddrStatus OBJECT-TYPE 1262 SYNTAX INTEGER { 1263 preferred(1), 1265 deprecated(2), 1267 invalid(3), 1269 inaccessible(4), 1271 unknown(5) -- status can not be determined 1272 -- for some reason. 1273 } 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "Address status. The preferred(1) state indicates 1278 that this is a valid address that can appear as 1279 the destination or source address of a packet. 1280 The deprecated(2) this is a valid but deprecated 1281 address that should no longer be used as a source 1282 address in new communications, but packets addressed 1283 to such an address are processed as expected. The 1284 invalid(3) state indicates that this is not valid 1285 address which should not appear as the destination 1286 or source address of a packet. The inaccessible(4) 1287 state indicates the address is not accessible because 1288 the interface to which this address is assigned is 1289 not operational." 1290 ::= { ipv6AddrEntry 4 } 1292 -- IPv6 Routing objects 1294 ipv6InstalledRoutes OBJECT-TYPE 1295 SYNTAX Counter32 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "The number of current ipv6RouteTable entries 1300 that are not invalid." 1301 ::= { ipv6MIBObjects 30 } 1303 ipv6DiscardedRoutes OBJECT-TYPE 1304 SYNTAX Counter32 1305 MAX-ACCESS read-only 1306 STATUS current 1307 DESCRIPTION 1308 "The number of routing entries which were chosen 1309 to be discarded even though they are valid. One 1310 possible reason for discarding such an entry could 1311 be to free-up buffer space for other routing 1312 entries." 1313 ::= { ipv6MIBObjects 31 } 1315 -- IPv6 Routing table 1317 -- The IPv6 routing table contains an entry for each 1318 -- valid IPv6 unicast route that can be used for 1319 -- packet forwarding determination. 1321 ipv6RouteTable OBJECT-TYPE 1322 SYNTAX SEQUENCE OF Ipv6RouteEntry 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "IPv6 Routing table" 1327 ::= { ipv6MIBObjects 32 } 1329 ipv6RouteEntry OBJECT-TYPE 1330 SYNTAX Ipv6RouteEntry 1331 MAX-ACCESS not-accessible 1332 STATUS current 1333 DESCRIPTION 1334 "A routing entry" 1335 INDEX { ipv6RouteDest, 1336 ipv6RoutePfxLength, 1337 ipv6RouteIfIndex, 1338 ipv6RouteIndex } 1339 ::= { ipv6RouteTable 1 } 1341 Ipv6RouteEntry ::= SEQUENCE { 1342 ipv6RouteDest Ipv6Address, 1343 ipv6RoutePfxLength INTEGER, 1344 ipv6RouteIfIndex Ipv6IfIndex, 1345 ipv6RouteIndex Integer32, 1346 ipv6RouteNextHop Ipv6Address, 1347 ipv6RouteType INTEGER, 1348 ipv6RouteProtocol INTEGER, 1349 ipv6RoutePolicy Unsigned32, 1350 ipv6RouteAge Unsigned32, 1351 ipv6RouteNextHopRDI OCTET STRING, 1352 ipv6RouteMetric Unsigned32, 1353 ipv6RouteWeight Unsigned32, 1354 ipv6RouteInfo RowPointer, 1355 ipv6RouteValid TruthValue 1356 } 1358 ipv6RouteDest OBJECT-TYPE 1359 SYNTAX Ipv6Address 1360 MAX-ACCESS not-accessible 1361 STATUS current 1362 DESCRIPTION 1363 "The destination IPv6 address of this route. 1364 This object may not take a Multicast address 1365 value." 1367 ::= { ipv6RouteEntry 1 } 1369 ipv6RoutePfxLength OBJECT-TYPE 1370 SYNTAX INTEGER(0..128) 1371 UNITS "bits" 1372 MAX-ACCESS not-accessible 1373 STATUS current 1374 DESCRIPTION 1375 "Indicates the prefix length of the destination 1376 address." 1377 ::= { ipv6RouteEntry 2 } 1379 ipv6RouteIfIndex OBJECT-TYPE 1380 SYNTAX Ipv6IfIndex 1381 MAX-ACCESS not-accessible 1382 STATUS current 1383 DESCRIPTION 1384 "The index value which uniquely identifies the local 1385 interface through which the next hop of this 1386 route should be reached. The interface identified 1387 by a particular value of this index is the same 1388 interface as identified by the same value of 1389 ipv6IfIndex." 1390 ::= { ipv6RouteEntry 3 } 1392 ipv6RouteIndex OBJECT-TYPE 1393 SYNTAX Integer32 1394 MAX-ACCESS not-accessible 1395 STATUS current 1396 DESCRIPTION 1397 "The value which uniquely identifies the route 1398 among the routes to the same network layer 1399 destination. The way this value is chosen is 1400 implementation specific but it must be unique for 1401 ipv6RouteDest/ipv6RoutePfxLength/ipv6RouteIfIndex 1402 tuple and remain constant for the life of the route." 1403 ::= { ipv6RouteEntry 4 } 1405 ipv6RouteNextHop OBJECT-TYPE 1406 SYNTAX Ipv6Address 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "On remote routes, the address of the next system 1411 en route; Otherwise, ::0" 1413 ::= { ipv6RouteEntry 5 } 1415 ipv6RouteType OBJECT-TYPE 1416 SYNTAX INTEGER { 1417 other(1), -- none of the following 1419 invalid(2), -- an invalidated route 1421 -- route to directly 1422 direct(3), -- connected (sub-)network 1424 -- route to a non-local 1425 indirect(4), -- destination 1427 -- an route indicating that 1428 -- packets to destinations 1429 -- matching this route are 1430 discard(5) -- to be discarded 1431 } 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "The type of route. Note that 'direct(3)' refers 1436 to a route for which the next hop is the final 1437 destination; 'indirect(4)' refers to a route for 1438 which the next hop is not the final 1439 destination; 'discard(5)' refers to a route 1440 indicating that packets to destinations matching 1441 this route are to be discarded (sometimes called 1442 black-hole route)." 1443 ::= { ipv6RouteEntry 6 } 1445 ipv6RouteProtocol OBJECT-TYPE 1446 SYNTAX INTEGER { 1447 other(1), -- none of the following 1449 -- non-protocol information, 1450 -- e.g., manually configured 1451 local(2), -- entries 1453 netmgmt(3), -- static route 1455 -- obtained via Neighbor 1456 -- Discovery protocol, 1457 ndisc(4), -- e.g., Redirect 1458 -- the following are all 1459 -- dynamic routing protocols 1460 rip(5), -- RIPng 1461 ospf(6), -- Open Shortest Path First 1462 idrp(7) -- InterDomain Routing Protocol 1463 } 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "The routing mechanism via which this route was 1468 learned." 1469 ::= { ipv6RouteEntry 7 } 1471 ipv6RoutePolicy OBJECT-TYPE 1472 SYNTAX Unsigned32 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "The general set of conditions that would cause the 1477 selection of one multipath route (set of next hops 1478 for a given destination) is referred to as 'policy'. 1479 Unless the mechanism indicated by ipv6RouteProtocol 1480 specified otherwise, the policy specifier is the 1481 Priority field of the IPv6 packet header. The 1482 encoding of IPv6 Priority is specified by 1483 the following convention: 1485 0 - uncharacterized traffic 1486 1 - 'filler' traffic (e.g., netnews) 1487 2 - unattended data transfer (e.g., email) 1488 3 - reserved 1489 4 - attended bulk transfer (e.g., FTP, NFS) 1490 5 - reserved 1491 6 - interactive traffic (e.g., telnet, X) 1492 7 - internet control traffic (e.g., routing 1493 protocols, SNMP) 1495 Protocols defining 'policy' otherwise must either 1496 define a set of values which are valid for 1497 this object or must implement an integer- 1498 instanced policy table for which this object's 1499 value acts as an index." 1500 ::= { ipv6RouteEntry 8 } 1502 ipv6RouteAge OBJECT-TYPE 1503 SYNTAX Unsigned32 1504 UNITS "seconds" 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "The number of seconds since this route was last 1509 updated or otherwise determined to be correct. 1510 Note that no semantics of `too old' can be implied 1511 except through knowledge of the routing protocol 1512 by which the route was learned." 1513 ::= { ipv6RouteEntry 9 } 1515 ipv6RouteNextHopRDI OBJECT-TYPE 1516 SYNTAX OCTET STRING (SIZE (0 | 16)) 1517 MAX-ACCESS read-only 1518 STATUS current 1519 DESCRIPTION 1520 "The Routing Domain ID of the Next Hop. 1521 When this is unknown or not relevant to the 1522 protocol indicated by ipv6RouteProtocol, it is 1523 an octet string of zero size." 1524 ::= { ipv6RouteEntry 10 } 1526 ipv6RouteMetric OBJECT-TYPE 1527 SYNTAX Unsigned32 1528 MAX-ACCESS read-only 1529 STATUS current 1530 DESCRIPTION 1531 "The routing metric for this route. The 1532 semantics of this metric are determined by the 1533 routing protocol specified in the route's 1534 ipv6RouteProtocol value. When this is unknown 1535 or not relevant to the protocol indicated by 1536 ipv6RouteProtocol, the object value should be 1537 set to its maximum value (4,294,967,295)." 1538 ::= { ipv6RouteEntry 11 } 1540 ipv6RouteWeight OBJECT-TYPE 1541 SYNTAX Unsigned32 1542 MAX-ACCESS read-only 1543 STATUS current 1544 DESCRIPTION 1545 "The system internal weight value for this route. 1546 The semantics of this value are determined by 1547 the implementation specific rules. Generally, 1548 within routes with the same ipv6RoutePolicy value, 1549 the lower the weight value the more preferred is 1550 the route." 1551 ::= { ipv6RouteEntry 12 } 1553 ipv6RouteInfo OBJECT-TYPE 1554 SYNTAX RowPointer 1555 MAX-ACCESS read-only 1556 STATUS current 1557 DESCRIPTION 1558 "A reference to MIB definitions specific to the 1559 particular routing protocol which is responsible 1560 for this route, as determined by the value 1561 specified in the route's ipv6RouteProto value. 1562 If this information is not present, its value 1563 should be set to the OBJECT ID { 0 0 }, 1564 which is a syntactically valid object identifier, 1565 and any implementation conforming to ASN.1 1566 and the Basic Encoding Rules must be able to 1567 generate and recognize this value." 1568 ::= { ipv6RouteEntry 13 } 1570 ipv6RouteValid OBJECT-TYPE 1571 SYNTAX TruthValue 1572 MAX-ACCESS read-write 1573 STATUS current 1574 DESCRIPTION 1575 "Setting this object to the value 'false(2)' has 1576 the effect of invalidating the corresponding entry 1577 in the ipv6RouteTable object. That is, it 1578 effectively disassociates the destination 1579 identified with said entry from the route 1580 identified with said entry. It is an 1581 implementation-specific matter as to whether the 1582 agent removes an invalidated entry from the table. 1583 Accordingly, management stations must be prepared 1584 to receive tabular information from agents that 1585 corresponds to entries not currently in use. 1586 Proper interpretation of such entries requires 1587 examination of the relevant ipv6RouteInvalid 1588 object." 1589 DEFVAL { true } 1590 ::= { ipv6RouteEntry 14 } 1592 -- IPv6 Address Translation table 1594 -- The IPv6 address translation table contain the 1595 -- Ipv6Address to `physical' address equivalences. 1596 -- Some interfaces do not use translation tables 1597 -- for determining address equivalences; if all 1598 -- interfaces are of this type, then the Address 1599 -- Translation table is empty, i.e., has zero 1600 -- entries. 1602 ipv6NetToMediaEntryTable OBJECT-TYPE 1603 SYNTAX SEQUENCE OF Ipv6NetToMediaEntry 1604 MAX-ACCESS not-accessible 1605 STATUS current 1606 DESCRIPTION 1607 "The IPv6 Address Translation table used for 1608 mapping from IPv6 addresses to physical addresses." 1609 ::= { ipv6MIBObjects 33 } 1611 ipv6NetToMediaEntry OBJECT-TYPE 1612 SYNTAX Ipv6NetToMediaEntry 1613 MAX-ACCESS not-accessible 1614 STATUS current 1615 DESCRIPTION 1616 "Each entry contains one IPv6 address to `physical' 1617 address equivalence." 1618 INDEX { ipv6IfIndex, 1619 ipv6NetToMediaNetAddress } 1620 ::= { ipv6NetToMediaEntryTable 1 } 1622 Ipv6NetToMediaEntry ::= SEQUENCE { 1623 ipv6NetToMediaNetAddress 1624 Ipv6Address, 1625 ipv6NetToMediaPhysAddress 1626 PhysAddress, 1627 ipv6NetToMediaType 1628 INTEGER, 1629 ipv6NetToMediaValid 1630 TruthValue 1631 } 1633 ipv6NetToMediaNetAddress OBJECT-TYPE 1634 SYNTAX Ipv6Address 1635 MAX-ACCESS not-accessible 1636 STATUS current 1637 DESCRIPTION 1638 "The IPv6 Address corresponding to 1639 the media-dependent `physical' address." 1640 ::= { ipv6NetToMediaEntry 1 } 1642 ipv6NetToMediaPhysAddress OBJECT-TYPE 1643 SYNTAX PhysAddress 1644 MAX-ACCESS read-only 1645 STATUS current 1646 DESCRIPTION 1647 "The media-dependent `physical' address." 1648 ::= { ipv6NetToMediaEntry 2 } 1650 ipv6NetToMediaType OBJECT-TYPE 1651 SYNTAX INTEGER { 1652 other(1), -- none of the following 1653 dynamic(2), -- dynamically resolved 1654 static(3) -- statically configured 1655 } 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "The type of mapping." 1660 ::= { ipv6NetToMediaEntry 3 } 1662 ipv6NetToMediaValid OBJECT-TYPE 1663 SYNTAX TruthValue 1664 MAX-ACCESS read-write 1665 STATUS current 1666 DESCRIPTION 1667 "Setting this object to the value 'false(2)' has 1668 the effect of invalidating the corresponding entry 1669 in the ipv6NetToMediaTable. That is, it effectively 1670 disassociates the interface identified with said 1671 entry from the mapping identified with said entry. 1672 It is an implementation-specific matter as to 1673 whether the agent removes an invalidated entry 1674 from the table. Accordingly, management stations 1675 must be prepared to receive tabular information 1676 from agents that corresponds to entries not 1677 currently in use. Proper interpretation of such 1678 entries requires examination of the relevant 1679 ipv6NetToMediaInvalid object." 1680 DEFVAL { true } 1681 ::= { ipv6NetToMediaEntry 4 } 1683 -- definition of IPv6-related traps. 1685 ipv6Traps OBJECT IDENTIFIER ::= { ipv6MIB 2 } 1687 ipv6IfStateChange NOTIFICATION-TYPE 1688 OBJECTS { 1689 ipv6IfDescr, 1690 ipv6IfOperStatus -- the new state of the If. 1691 } 1692 STATUS current 1693 DESCRIPTION 1694 "An ipv6IfStateChange trap signifies that there 1695 has been a change in the state of an ipv6 interface. 1696 This trap should be generated when the interface's 1697 operational status transitions to or from 1698 the down(2) state." 1699 ::= { ipv6Traps 1 } 1701 -- conformance information 1703 ipv6Conformance OBJECT IDENTIFIER ::= { ipv6MIB 3 } 1705 ipv6Compliances OBJECT IDENTIFIER ::= { ipv6Conformance 1 } 1706 ipv6Groups OBJECT IDENTIFIER ::= { ipv6Conformance 2 } 1708 -- compliance statements 1710 ipMIBCompliance MODULE-COMPLIANCE 1711 STATUS current 1712 DESCRIPTION 1713 "The compliance statement for SNMPv2 entities which 1714 implement ipv6 MIB." 1715 MODULE -- this module 1716 MANDATORY-GROUPS { ipv6GeneralGroup } 1717 ::= { ipv6Compliances 1 } 1719 ipv6GeneralGroup OBJECT-GROUP 1720 OBJECTS { ipv6Forwarding, 1721 ipv6DefaultHopLimit, 1722 ipv6InReceives, 1723 ipv6InHdrErrors, 1724 ipv6TooBigErrors, 1725 ipv6InAddrErrors, 1726 ipv6TruncatedPkts, 1727 ipv6ForwDatagrams, 1728 ipv6InUnknownProtos, 1729 ipv6InDiscards, 1730 ipv6InDelivers, 1731 ipv6OutRequests, 1732 ipv6OutDiscards, 1733 ipv6OutNoRoutes, 1734 ipv6ReasmTimeout, 1735 ipv6ReasmReqds, 1736 ipv6ReasmOKs, 1737 ipv6ReasmFails, 1738 ipv6FragOKs, 1739 ipv6FragFails, 1740 ipv6FragCreates, 1741 ipv6InMcastPkts, 1742 ipv6OutMcastPkts, 1743 ipv6Interfaces, 1744 ipv6IfTableLastChange, 1745 ipv6IfDescr, 1746 ipv6IfLowerLayer, 1747 ipv6IfEffectiveMtu, 1748 ipv6IfReasmMaxSize, 1749 ipv6IfToken, 1750 ipv6IfTokenLength, 1751 ipv6IfPhysicalAddress, 1752 ipv6IfAdminStatus, 1753 ipv6IfOperStatus, 1754 ipv6IfLastChange, 1755 ipv6IfStatsInReceives, 1756 ipv6IfStatsInHdrErrors, 1757 ipv6IfStatsTooBigErrors, 1758 ipv6IfStatsInAddrErrors, 1759 ipv6IfStatsForwDatagrams, 1760 ipv6IfStatsInUnknownProtos, 1761 ipv6IfStatsInDiscards, 1762 ipv6IfStatsInDelivers, 1763 ipv6IfStatsOutRequests, 1764 ipv6IfStatsOutDiscards, 1765 ipv6IfStatsOutNoRoutes, 1766 ipv6IfStatsReasmReqds, 1767 ipv6IfStatsReasmOKs, 1768 ipv6IfStatsReasmFails, 1769 ipv6IfStatsFragOKs, 1770 ipv6IfStatsFragFails, 1771 ipv6IfStatsFragCreates, 1772 ipv6IfStatsInMcastPkts, 1773 ipv6IfStatsOutMcastPkts, 1774 ipv6IfStatsInTruncatedPkts, 1775 ipv6AddrPrefixOnLinkFlag, 1776 ipv6AddrPrefixAutonomousFlag, 1777 ipv6AddrPrefixAdvPreferredLifetime, 1778 ipv6AddrPrefixAdvValidLifetime, 1779 ipv6AddrPfxLength, 1780 ipv6AddrType, 1781 ipv6AddrStatus, 1782 ipv6InstalledRoutes, 1783 ipv6DiscardedRoutes, 1784 ipv6RouteNextHop, 1785 ipv6RouteType, 1786 ipv6RouteProtocol, 1787 ipv6RoutePolicy, 1788 ipv6RouteAge, 1789 ipv6RouteNextHopRDI, 1790 ipv6RouteMetric, 1791 ipv6RouteWeight, 1792 ipv6RouteInfo, 1793 ipv6RouteValid, 1794 ipv6NetToMediaPhysAddress, 1795 ipv6NetToMediaType, 1796 ipv6NetToMediaValid } 1797 STATUS current 1798 DESCRIPTION 1799 "The IPv6 group of objects providing for basic 1800 management of IPv6 entities" 1801 ::= { ipv6Groups 1 } 1803 END 1805 5.2. The ICMPv6 Group 1807 IPV6-ICMP-MIB DEFINITIONS ::= BEGIN 1809 IMPORTS 1810 MODULE-IDENTITY, OBJECT-TYPE, 1811 Counter32 FROM SNMPv2-SMI 1812 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 1813 ipv6 FROM IPV6-TC 1814 ipv6IfEntry FROM IPV6-MIB; 1816 ipv6IcmpMIB MODULE-IDENTITY 1817 LAST-UPDATED "9610042155Z" 1818 ORGANIZATION "IETF IPv6 MIB Working Group" 1819 CONTACT-INFO 1820 " Dimitry Haskin 1822 Postal: Bay Networks, Inc. 1823 2 Federal St. 1824 Billerica, MA 01821 1825 US 1827 Tel: +1-508-916-8124 1828 E-mail: dhaskin@baynetworks.com 1830 Steve Onishi 1832 Postal: Bay Networks, Inc. 1833 3 Federal Street 1834 Billerica, MA 01821 1835 US 1837 Tel: +1-508-916-3816 1838 E-mail: sonishi@baynetworks.com" 1839 DESCRIPTION 1840 "The MIB module for entities implementing 1841 the ICMPv6." 1842 ::= { ipv6 2 } 1844 -- the ICMPv6 group 1846 ipv6IcmpMIBObjects OBJECT IDENTIFIER ::= { ipv6IcmpMIB 1 } 1847 ipv6IcmpInMsgs OBJECT-TYPE 1848 SYNTAX Counter32 1849 MAX-ACCESS read-only 1850 STATUS current 1851 DESCRIPTION 1852 "The total number of ICMP messages which 1853 the entity received. Note that this counter 1854 includes all those counted by ipv6IcmpInErrors." 1855 ::= { ipv6IcmpMIBObjects 1 } 1857 ipv6IcmpInErrors OBJECT-TYPE 1858 SYNTAX Counter32 1859 MAX-ACCESS read-only 1860 STATUS current 1861 DESCRIPTION 1862 "The number of ICMP messages which the entity 1863 received but determined as having ICMP-specific 1864 errors (bad ICMP checksums, bad length, etc.)." 1865 ::= { ipv6IcmpMIBObjects 2 } 1867 ipv6IcmpInDestUnreachs OBJECT-TYPE 1868 SYNTAX Counter32 1869 MAX-ACCESS read-only 1870 STATUS current 1871 DESCRIPTION 1872 "The number of ICMP Destination Unreachable 1873 messages received." 1874 ::= { ipv6IcmpMIBObjects 3 } 1876 ipv6IcmpInTimeExcds OBJECT-TYPE 1877 SYNTAX Counter32 1878 MAX-ACCESS read-only 1879 STATUS current 1880 DESCRIPTION 1881 "The number of ICMP Time Exceeded messages 1882 received." 1883 ::= { ipv6IcmpMIBObjects 4 } 1885 ipv6IcmpInParmProbs OBJECT-TYPE 1886 SYNTAX Counter32 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "The number of ICMP Parameter Problem messages 1891 received." 1893 ::= { ipv6IcmpMIBObjects 5 } 1895 ipv6IcmpInPktTooBigs OBJECT-TYPE 1896 SYNTAX Counter32 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "The number of ICMP Packet Too Big messages 1901 received." 1902 ::= { ipv6IcmpMIBObjects 6 } 1904 ipv6IcmpInEchos OBJECT-TYPE 1905 SYNTAX Counter32 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "The number of ICMP Echo (request) messages 1910 received." 1911 ::= { ipv6IcmpMIBObjects 7 } 1913 ipv6IcmpInEchoReps OBJECT-TYPE 1914 SYNTAX Counter32 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "The number of ICMP Echo Reply messages received." 1919 ::= { ipv6IcmpMIBObjects 8 } 1921 ipv6IcmpInRouterSolicits OBJECT-TYPE 1922 SYNTAX Counter32 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "The number of ICMP Router Solicit messages 1927 received." 1928 ::= { ipv6IcmpMIBObjects 9 } 1930 ipv6IcmpInRouterAdvertisements OBJECT-TYPE 1931 SYNTAX Counter32 1932 MAX-ACCESS read-only 1933 STATUS current 1934 DESCRIPTION 1935 "The number of ICMP Router Advertisement messages 1936 received." 1937 ::= { ipv6IcmpMIBObjects 10 } 1939 ipv6IcmpInNeighborSolicits OBJECT-TYPE 1940 SYNTAX Counter32 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "The number of ICMP Neighbor Solicit messages 1945 received." 1946 ::= { ipv6IcmpMIBObjects 11 } 1948 ipv6IcmpInNeighborAdvertisements OBJECT-TYPE 1949 SYNTAX Counter32 1950 MAX-ACCESS read-only 1951 STATUS current 1952 DESCRIPTION 1953 "The number of ICMP Neighbor Advertisement 1954 messages received." 1955 ::= { ipv6IcmpMIBObjects 12 } 1957 ipv6IcmpInRedirects OBJECT-TYPE 1958 SYNTAX Counter32 1959 MAX-ACCESS read-only 1960 STATUS current 1961 DESCRIPTION 1962 "The number of Redirect messages received." 1963 ::= { ipv6IcmpMIBObjects 13 } 1965 ipv6IcmpInAdminProhib OBJECT-TYPE 1966 SYNTAX Counter32 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "Number of ICMP destination unreachable/communication 1971 administratively prohibited messages received." 1972 ::= { ipv6IcmpMIBObjects 14 } 1974 ipv6IcmpOutMsgs OBJECT-TYPE 1975 SYNTAX Counter32 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "The total number of ICMP messages which this 1980 entity attempted to send. Note that this counter 1981 includes all those counted by icmpOutErrors." 1982 ::= { ipv6IcmpMIBObjects 15 } 1984 ipv6IcmpOutErrors OBJECT-TYPE 1985 SYNTAX Counter32 1986 MAX-ACCESS read-only 1987 STATUS current 1988 DESCRIPTION 1989 "The number of ICMP messages which this entity did 1990 not send due to problems discovered within ICMP 1991 such as a lack of buffers. This value should not 1992 include errors discovered outside the ICMP layer 1993 such as the inability of IPv6 to route the resultant 1994 datagram. In some implementations there may be no 1995 types of error which contribute to this counter's 1996 value." 1997 ::= { ipv6IcmpMIBObjects 16 } 1999 ipv6IcmpOutDestUnreachs OBJECT-TYPE 2000 SYNTAX Counter32 2001 MAX-ACCESS read-only 2002 STATUS current 2003 DESCRIPTION 2004 "The number of ICMP Destination Unreachable 2005 messages sent." 2006 ::= { ipv6IcmpMIBObjects 17 } 2008 ipv6IcmpOutTimeExcds OBJECT-TYPE 2009 SYNTAX Counter32 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "The number of ICMP Time Exceeded messages sent." 2014 ::= { ipv6IcmpMIBObjects 18 } 2016 ipv6IcmpOutParmProbs OBJECT-TYPE 2017 SYNTAX Counter32 2018 MAX-ACCESS read-only 2019 STATUS current 2020 DESCRIPTION 2021 "The number of ICMP Parameter Problem messages 2022 sent." 2023 ::= { ipv6IcmpMIBObjects 19 } 2025 ipv6IcmpOutPktTooBigs OBJECT-TYPE 2026 SYNTAX Counter32 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "The number of ICMP Packet Too Big messages sent." 2031 ::= { ipv6IcmpMIBObjects 20 } 2033 ipv6IcmpOutEchos OBJECT-TYPE 2034 SYNTAX Counter32 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "The number of ICMP Echo (request) messages sent." 2039 ::= { ipv6IcmpMIBObjects 21 } 2041 ipv6IcmpOutEchoReps OBJECT-TYPE 2042 SYNTAX Counter32 2043 MAX-ACCESS read-only 2044 STATUS current 2045 DESCRIPTION 2046 "The number of ICMP Echo Reply messages sent." 2047 ::= { ipv6IcmpMIBObjects 22 } 2049 ipv6IcmpOutRouterSolicits OBJECT-TYPE 2050 SYNTAX Counter32 2051 MAX-ACCESS read-only 2052 STATUS current 2053 DESCRIPTION 2054 "The number of ICMP Router Solicitation messages 2055 sent." 2056 ::= { ipv6IcmpMIBObjects 23 } 2058 ipv6IcmpOutRouterAdvertisements OBJECT-TYPE 2059 SYNTAX Counter32 2060 MAX-ACCESS read-only 2061 STATUS current 2062 DESCRIPTION 2063 "The number of ICMP Router Advertisement messages 2064 received." 2065 ::= { ipv6IcmpMIBObjects 24 } 2067 ipv6IcmpOutNeighborSolicits OBJECT-TYPE 2068 SYNTAX Counter32 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "The number of ICMP Neighbor Solicitation 2073 messages sent." 2075 ::= { ipv6IcmpMIBObjects 25 } 2077 ipv6IcmpOutNeighborAdvertisements OBJECT-TYPE 2078 SYNTAX Counter32 2079 MAX-ACCESS read-only 2080 STATUS current 2081 DESCRIPTION 2082 "The number of ICMP Neighbor Advertisement 2083 messages 2084 received." 2085 ::= { ipv6IcmpMIBObjects 26 } 2087 ipv6IcmpOutRedirects OBJECT-TYPE 2088 SYNTAX Counter32 2089 MAX-ACCESS read-only 2090 STATUS current 2091 DESCRIPTION 2092 "The number of Redirect messages sent. For 2093 a host, this object will always be zero, 2094 since hosts do not send redirects." 2095 ::= { ipv6IcmpMIBObjects 27 } 2097 ipv6IcmpOutAdminProhib OBJECT-TYPE 2098 SYNTAX Counter32 2099 MAX-ACCESS read-only 2100 STATUS current 2101 DESCRIPTION 2102 "Number of ICMP destination unreachable/ 2103 communication administratively prohibited 2104 messages sent." 2105 ::= { ipv6IcmpMIBObjects 28 } 2107 -- Per-interface ICMPv6 statistics table 2109 ipv6IfIcmpTable OBJECT-TYPE 2110 SYNTAX SEQUENCE OF Ipv6IfIcmpEntry 2111 MAX-ACCESS not-accessible 2112 STATUS current 2113 DESCRIPTION 2114 "IPv6 ICMP statistics" 2115 ::= { ipv6IcmpMIBObjects 29 } 2117 ipv6IfIcmpEntry OBJECT-TYPE 2118 SYNTAX Ipv6IfIcmpEntry 2119 MAX-ACCESS not-accessible 2120 STATUS current 2121 DESCRIPTION 2122 "An ICMPv6 statistics entry containing 2123 objects at a particular IPv6 interface." 2124 AUGMENTS { ipv6IfEntry } 2125 ::= { ipv6IfIcmpTable 1 } 2127 Ipv6IfIcmpEntry ::= SEQUENCE { 2128 ipv6IfIcmpInMsgs 2129 Counter32 , 2130 ipv6IfIcmpInErrors 2131 Counter32 , 2132 ipv6IfIcmpInDestUnreachs 2133 Counter32 , 2134 ipv6IfIcmpInTimeExcds 2135 Counter32 , 2136 ipv6IfIcmpInParmProbs 2137 Counter32 , 2138 ipv6IfIcmpInPktTooBigs 2139 Counter32 , 2140 ipv6IfIcmpInEchos 2141 Counter32 , 2142 ipv6IfIcmpInEchoReps 2143 Counter32 , 2144 ipv6IfIcmpInRouterSolicits 2145 Counter32 , 2146 ipv6IfIcmpInRouterAdvertisements 2147 Counter32 , 2148 ipv6IfIcmpInNeighborSolicits 2149 Counter32 , 2150 ipv6IfIcmpInNeighborAdvertisements 2151 Counter32 , 2152 ipv6IfIcmpInRedirects 2153 Counter32 , 2154 ipv6IfIcmpOutMsgs 2155 Counter32 , 2156 ipv6IfIcmpOutErrors 2157 Counter32 , 2158 ipv6IfIcmpOutDestUnreachs 2159 Counter32 , 2160 ipv6IfIcmpOutTimeExcds 2161 Counter32 , 2162 ipv6IfIcmpOutParmProbs 2163 Counter32 , 2164 ipv6IfIcmpOutPktTooBigs 2165 Counter32 , 2166 ipv6IfIcmpOutEchos 2167 Counter32 , 2168 ipv6IfIcmpOutEchoReps 2169 Counter32 , 2170 ipv6IfIcmpOutRouterSolicits 2171 Counter32 , 2172 ipv6IfIcmpOutRouterAdvertisements 2173 Counter32 , 2174 ipv6IfIcmpOutNeighborSolicits 2175 Counter32 , 2176 ipv6IfIcmpOutNeighborAdvertisements 2177 Counter32 , 2178 ipv6IfIcmpOutRedirects 2179 Counter32 , 2180 ipv6IfIcmpInAdminProhib 2181 Counter32 , 2182 ipv6IfIcmpOutAdminProhib 2183 Counter32 2184 } 2186 ipv6IfIcmpInMsgs OBJECT-TYPE 2187 SYNTAX Counter32 2188 MAX-ACCESS read-only 2189 STATUS current 2190 DESCRIPTION 2191 "The total number of ICMP messages which includes 2192 all those counted by ipv6IfIcmpInErrors." 2193 ::= { ipv6IfIcmpEntry 1 } 2195 ipv6IfIcmpInErrors OBJECT-TYPE 2196 SYNTAX Counter32 2197 MAX-ACCESS read-only 2198 STATUS current 2199 DESCRIPTION 2200 "The number of ICMP messages which the entity 2201 received but determined as having ICMP-specific 2202 errors (bad ICMP checksums, bad length, etc.)." 2203 ::= { ipv6IfIcmpEntry 2 } 2205 ipv6IfIcmpInDestUnreachs OBJECT-TYPE 2206 SYNTAX Counter32 2207 MAX-ACCESS read-only 2208 STATUS current 2209 DESCRIPTION 2210 "The number of ICMP Destination Unreachable 2211 messages received." 2212 ::= { ipv6IfIcmpEntry 3 } 2214 ipv6IfIcmpInTimeExcds OBJECT-TYPE 2215 SYNTAX Counter32 2216 MAX-ACCESS read-only 2217 STATUS current 2218 DESCRIPTION 2219 "The number of ICMP Time Exceeded messages 2220 received." 2221 ::= { ipv6IfIcmpEntry 4 } 2223 ipv6IfIcmpInParmProbs OBJECT-TYPE 2224 SYNTAX Counter32 2225 MAX-ACCESS read-only 2226 STATUS current 2227 DESCRIPTION 2228 "The number of ICMP Parameter Problem messages 2229 received." 2230 ::= { ipv6IfIcmpEntry 5 } 2232 ipv6IfIcmpInPktTooBigs OBJECT-TYPE 2233 SYNTAX Counter32 2234 MAX-ACCESS read-only 2235 STATUS current 2236 DESCRIPTION 2237 "The number of ICMP Packet Too Big messages 2238 received." 2239 ::= { ipv6IfIcmpEntry 6 } 2241 ipv6IfIcmpInEchos OBJECT-TYPE 2242 SYNTAX Counter32 2243 MAX-ACCESS read-only 2244 STATUS current 2245 DESCRIPTION 2246 "The number of ICMP Echo (request) messages 2247 received." 2248 ::= { ipv6IfIcmpEntry 7 } 2250 ipv6IfIcmpInEchoReps OBJECT-TYPE 2251 SYNTAX Counter32 2252 MAX-ACCESS read-only 2253 STATUS current 2254 DESCRIPTION 2255 "The number of ICMP Echo Reply messages received." 2256 ::= { ipv6IfIcmpEntry 8 } 2258 ipv6IfIcmpInRouterSolicits OBJECT-TYPE 2259 SYNTAX Counter32 2260 MAX-ACCESS read-only 2261 STATUS current 2262 DESCRIPTION 2263 "The number of ICMP Router Solicit messages 2264 received." 2265 ::= { ipv6IfIcmpEntry 9 } 2267 ipv6IfIcmpInRouterAdvertisements OBJECT-TYPE 2268 SYNTAX Counter32 2269 MAX-ACCESS read-only 2270 STATUS current 2271 DESCRIPTION 2272 "The number of ICMP Router Advertisement messages 2273 received." 2274 ::= { ipv6IfIcmpEntry 10 } 2276 ipv6IfIcmpInNeighborSolicits OBJECT-TYPE 2277 SYNTAX Counter32 2278 MAX-ACCESS read-only 2279 STATUS current 2280 DESCRIPTION 2281 "The number of ICMP Neighbor Solicit messages 2282 received." 2283 ::= { ipv6IfIcmpEntry 11 } 2285 ipv6IfIcmpInNeighborAdvertisements OBJECT-TYPE 2286 SYNTAX Counter32 2287 MAX-ACCESS read-only 2288 STATUS current 2289 DESCRIPTION 2290 "The number of ICMP Neighbor Advertisement 2291 messages received." 2292 ::= { ipv6IfIcmpEntry 12 } 2294 ipv6IfIcmpInRedirects OBJECT-TYPE 2295 SYNTAX Counter32 2296 MAX-ACCESS read-only 2297 STATUS current 2298 DESCRIPTION 2299 "The number of Redirect messages received." 2301 ::= { ipv6IfIcmpEntry 13 } 2303 ipv6IfIcmpInAdminProhib OBJECT-TYPE 2304 SYNTAX Counter32 2305 MAX-ACCESS read-only 2306 STATUS current 2307 DESCRIPTION 2308 "Number of ICMP dest unreachable/communication 2309 administratively prohibited messages received." 2310 ::= { ipv6IfIcmpEntry 14 } 2312 ipv6IfIcmpOutMsgs OBJECT-TYPE 2313 SYNTAX Counter32 2314 MAX-ACCESS read-only 2315 STATUS current 2316 DESCRIPTION 2317 "The total number of ICMP messages which this 2318 entity attempted to send. Note that this counter 2319 includes all those counted by icmpOutErrors." 2320 ::= { ipv6IfIcmpEntry 15 } 2322 ipv6IfIcmpOutErrors OBJECT-TYPE 2323 SYNTAX Counter32 2324 MAX-ACCESS read-only 2325 STATUS current 2326 DESCRIPTION 2327 "The number of ICMP messages which this entity did 2328 not send due to problems discovered within ICMP 2329 such as a lack of buffers. This value should not 2330 include errors discovered outside the ICMP layer 2331 such as the inability of IPv6 to route the resultant 2332 datagram. In some implementations there may be no 2333 types of error which contribute to this counter's 2334 value." 2335 ::= { ipv6IfIcmpEntry 16 } 2337 ipv6IfIcmpOutDestUnreachs OBJECT-TYPE 2338 SYNTAX Counter32 2339 MAX-ACCESS read-only 2340 STATUS current 2341 DESCRIPTION 2342 "The number of ICMP Destination Unreachable 2343 messages sent." 2344 ::= { ipv6IfIcmpEntry 17 } 2346 ipv6IfIcmpOutTimeExcds OBJECT-TYPE 2347 SYNTAX Counter32 2348 MAX-ACCESS read-only 2349 STATUS current 2350 DESCRIPTION 2351 "The number of ICMP Time Exceeded messages sent." 2352 ::= { ipv6IfIcmpEntry 18 } 2354 ipv6IfIcmpOutParmProbs OBJECT-TYPE 2355 SYNTAX Counter32 2356 MAX-ACCESS read-only 2357 STATUS current 2358 DESCRIPTION 2359 "The number of ICMP Parameter Problem messages 2360 sent." 2361 ::= { ipv6IfIcmpEntry 19 } 2363 ipv6IfIcmpOutPktTooBigs OBJECT-TYPE 2364 SYNTAX Counter32 2365 MAX-ACCESS read-only 2366 STATUS current 2367 DESCRIPTION 2368 "The number of ICMP Packet Too Big messages sent." 2369 ::= { ipv6IfIcmpEntry 20 } 2371 ipv6IfIcmpOutEchos OBJECT-TYPE 2372 SYNTAX Counter32 2373 MAX-ACCESS read-only 2374 STATUS current 2375 DESCRIPTION 2376 "The number of ICMP Echo (request) messages sent." 2377 ::= { ipv6IfIcmpEntry 21 } 2379 ipv6IfIcmpOutEchoReps OBJECT-TYPE 2380 SYNTAX Counter32 2381 MAX-ACCESS read-only 2382 STATUS current 2383 DESCRIPTION 2384 "The number of ICMP Echo Reply messages sent." 2385 ::= { ipv6IfIcmpEntry 22 } 2387 ipv6IfIcmpOutRouterSolicits OBJECT-TYPE 2388 SYNTAX Counter32 2389 MAX-ACCESS read-only 2390 STATUS current 2391 DESCRIPTION 2392 "The number of ICMP Router Solicitation messages 2393 sent." 2394 ::= { ipv6IfIcmpEntry 23 } 2396 ipv6IfIcmpOutRouterAdvertisements OBJECT-TYPE 2397 SYNTAX Counter32 2398 MAX-ACCESS read-only 2399 STATUS current 2400 DESCRIPTION 2401 "The number of ICMP Router Advertisement messages 2402 received." 2403 ::= { ipv6IfIcmpEntry 24 } 2405 ipv6IfIcmpOutNeighborSolicits OBJECT-TYPE 2406 SYNTAX Counter32 2407 MAX-ACCESS read-only 2408 STATUS current 2409 DESCRIPTION 2410 "The number of ICMP Neighbor Solicitation 2411 messages sent." 2412 ::= { ipv6IfIcmpEntry 25 } 2414 ipv6IfIcmpOutNeighborAdvertisements OBJECT-TYPE 2415 SYNTAX Counter32 2416 MAX-ACCESS read-only 2417 STATUS current 2418 DESCRIPTION 2419 "The number of ICMP Neighbor Advertisement 2420 messages 2421 received." 2422 ::= { ipv6IfIcmpEntry 26 } 2424 ipv6IfIcmpOutRedirects OBJECT-TYPE 2425 SYNTAX Counter32 2426 MAX-ACCESS read-only 2427 STATUS current 2428 DESCRIPTION 2429 "The number of Redirect messages sent. For 2430 a host, this object will always be zero, 2431 since hosts do not send redirects." 2432 ::= { ipv6IfIcmpEntry 27 } 2434 ipv6IfIcmpOutAdminProhib OBJECT-TYPE 2435 SYNTAX Counter32 2436 MAX-ACCESS read-only 2437 STATUS current 2438 DESCRIPTION 2439 "Number of ICMP dest unreachable/communication 2440 administratively prohibited messages sent." 2441 ::= { ipv6IfIcmpEntry 28 } 2443 -- conformance information 2445 ipv6IcmpConformance OBJECT IDENTIFIER ::= { ipv6IcmpMIB 2 } 2447 ipv6IcmpCompliances 2448 OBJECT IDENTIFIER ::= { ipv6IcmpConformance 1 } 2449 ipv6IcmpGroups 2450 OBJECT IDENTIFIER ::= { ipv6IcmpConformance 2 } 2452 -- compliance statements 2454 ipv6IcmpCompliance MODULE-COMPLIANCE 2455 STATUS current 2456 DESCRIPTION 2457 "The compliance statement for SNMPv2 entities which 2458 implement ICMPv6." 2459 MODULE -- this module 2460 MANDATORY-GROUPS { ipv6IcmpGroup } 2461 ::= { ipv6IcmpCompliances 1 } 2463 ipv6IcmpGroup OBJECT-GROUP 2464 OBJECTS { 2465 ipv6IcmpInMsgs, 2466 ipv6IcmpInErrors, 2467 ipv6IcmpInDestUnreachs, 2468 ipv6IcmpInTimeExcds, 2469 ipv6IcmpInParmProbs , 2470 ipv6IcmpInEchoReps , 2471 ipv6IcmpInRouterSolicits, 2472 ipv6IcmpInRouterAdvertisements, 2473 ipv6IcmpInNeighborSolicits, 2474 ipv6IcmpInNeighborAdvertisements, 2475 ipv6IcmpInRedirects, 2476 ipv6IcmpInPktTooBigs, 2477 ipv6IcmpInEchos, 2478 ipv6IcmpOutMsgs, 2479 ipv6IcmpOutErrors, 2480 ipv6IcmpOutDestUnreachs, 2481 ipv6IcmpOutTimeExcds, 2482 ipv6IcmpOutParmProbs, 2483 ipv6IcmpOutPktTooBigs , 2484 ipv6IcmpOutEchos, 2485 ipv6IcmpOutEchoReps, 2486 ipv6IcmpOutRouterSolicits, 2487 ipv6IcmpOutRouterAdvertisements, 2488 ipv6IcmpOutNeighborSolicits, 2489 ipv6IcmpOutNeighborAdvertisements, 2490 ipv6IcmpOutRedirects, 2491 ipv6IcmpInAdminProhib, 2492 ipv6IcmpOutAdminProhib, 2493 ipv6IfIcmpInMsgs, 2494 ipv6IfIcmpInErrors, 2495 ipv6IfIcmpInDestUnreachs, 2496 ipv6IfIcmpInTimeExcds, 2497 ipv6IfIcmpInParmProbs , 2498 ipv6IfIcmpInEchoReps , 2499 ipv6IfIcmpInRouterSolicits, 2500 ipv6IfIcmpInRouterAdvertisements, 2501 ipv6IfIcmpInNeighborSolicits, 2502 ipv6IfIcmpInNeighborAdvertisements, 2503 ipv6IfIcmpInRedirects, 2504 ipv6IfIcmpOutMsgs, 2505 ipv6IfIcmpOutErrors, 2506 ipv6IfIcmpOutDestUnreachs, 2507 ipv6IfIcmpOutTimeExcds, 2508 ipv6IfIcmpOutParmProbs, 2509 ipv6IfIcmpOutPktTooBigs , 2510 ipv6IfIcmpOutEchos, 2511 ipv6IfIcmpOutEchoReps, 2512 ipv6IfIcmpOutRouterSolicits, 2513 ipv6IfIcmpOutRouterAdvertisements, 2514 ipv6IfIcmpOutNeighborSolicits, 2515 ipv6IfIcmpOutNeighborAdvertisements, 2516 ipv6IfIcmpOutRedirects, 2517 ipv6IfIcmpInAdminProhib, 2518 ipv6IfIcmpOutAdminProhib, 2519 ipv6IfIcmpInPktTooBigs, 2520 ipv6IfIcmpInEchos 2521 } 2522 STATUS current 2523 DESCRIPTION 2524 "The ICMPv6 group of objects providing information 2525 specific to ICMPv6." 2526 ::= { ipv6IcmpGroups 1 } 2528 END 2530 5.3. The UDP Group 2532 IPV6-UDP-MIB DEFINITIONS ::= BEGIN 2534 IMPORTS 2535 MODULE-IDENTITY, OBJECT-TYPE, 2536 Counter32, Unsigned32 FROM SNMPv2-SMI 2537 ipv6, Ipv6Address FROM IPV6-TC 2538 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 2539 ipv6IfIndex FROM IPV6-MIB; 2541 ipv6UdpMIB MODULE-IDENTITY 2542 LAST-UPDATED "9610042155Z" 2543 ORGANIZATION "IETF IPv6 MIB Working Group" 2544 CONTACT-INFO 2545 " Dimitry Haskin 2546 Postal: Bay Networks, Inc. 2547 2 Federal St. 2548 Billerica, MA 01821 2549 US 2551 Tel: +1-508-916-8124 2552 E-mail: dhaskin@baynetworks.com 2554 Steve Onishi 2555 Postal: Bay Networks, Inc. 2556 3 Federal Street 2557 Billerica, MA 01821 2558 US 2560 Tel: +1-508-916-3816 2561 E-mail: sonishi@baynetworks.com" 2562 DESCRIPTION 2563 "The MIB module for entities implementing UDP 2564 over IPv6." 2565 ::= { ipv6 3} 2567 -- the UDP group 2569 ipv6UdpMIBObjects OBJECT IDENTIFIER ::= { ipv6UdpMIB 1 } 2570 ipv6UdpInDatagrams OBJECT-TYPE 2571 SYNTAX Counter32 2572 MAX-ACCESS read-only 2573 STATUS current 2574 DESCRIPTION 2575 "The total number of UDP datagrams delivered to 2576 UDP users." 2577 ::= { ipv6UdpMIBObjects 1 } 2579 ipv6UdpNoPorts OBJECT-TYPE 2580 SYNTAX Counter32 2581 MAX-ACCESS read-only 2582 STATUS current 2583 DESCRIPTION 2584 "The total number of received UDP datagrams 2585 for which there was no application at 2586 the destination port." 2587 ::= { ipv6UdpMIBObjects 2 } 2589 ipv6UdpInErrors OBJECT-TYPE 2590 SYNTAX Counter32 2591 MAX-ACCESS read-only 2592 STATUS current 2593 DESCRIPTION 2594 "The number of received UDP datagrams that 2595 could not be delivered for reasons other 2596 than the lack of an application at 2597 the destination port." 2598 ::= { ipv6UdpMIBObjects 3 } 2600 ipv6UdpOutDatagrams OBJECT-TYPE 2601 SYNTAX Counter32 2602 MAX-ACCESS read-only 2603 STATUS current 2604 DESCRIPTION 2605 "The total number of UDP datagrams sent 2606 from this entity." 2607 ::= { ipv6UdpMIBObjects 4 } 2609 ipv6UdpTable OBJECT-TYPE 2610 SYNTAX SEQUENCE OF Ipv6UdpEntry 2611 MAX-ACCESS not-accessible 2612 STATUS current 2613 DESCRIPTION 2614 "The UDP listener table contains information 2615 about this entity's UDP end-points on which 2616 a local application is currently accepting 2617 datagrams." 2618 ::= { ipv6UdpMIBObjects 5 } 2620 ipv6UdpEntry OBJECT-TYPE 2621 SYNTAX Ipv6UdpEntry 2622 MAX-ACCESS not-accessible 2623 STATUS current 2624 DESCRIPTION 2625 "Information about a particular current UDP 2626 listener." 2627 INDEX { ipv6IfIndex, 2628 ipv6UdpLocalAddress, 2629 ipv6UdpLocalPort } 2630 ::= { ipv6UdpTable 1 } 2632 Ipv6UdpEntry ::= SEQUENCE { 2633 ipv6UdpLocalAddress Ipv6Address, 2634 ipv6UdpLocalPort Unsigned32 2635 } 2637 ipv6UdpLocalAddress OBJECT-TYPE 2638 SYNTAX Ipv6Address 2639 MAX-ACCESS not-accessible 2640 STATUS current 2641 DESCRIPTION 2642 "The local IPv6 address for this UDP listener. 2643 In the case of a UDP listener which is willing 2644 to accept datagrams for any IPv6 address 2645 associated with the interface, the value ::0 2646 is used." 2647 ::= { ipv6UdpEntry 2 } 2649 ipv6UdpLocalPort OBJECT-TYPE 2650 SYNTAX Unsigned32 2651 MAX-ACCESS read-only 2652 STATUS current 2653 DESCRIPTION 2654 "The local port number for this UDP listener." 2655 ::= { ipv6UdpEntry 3 } 2657 -- conformance information 2658 ipv6UdpConformance OBJECT IDENTIFIER ::= { ipv6UdpMIB 2 } 2660 ipv6UdpCompliances OBJECT IDENTIFIER ::= { ipv6UdpConformance 1 } 2661 ipv6UdpGroups OBJECT IDENTIFIER ::= { ipv6UdpConformance 2 } 2663 -- compliance statements 2665 ipv6UdpCompliance MODULE-COMPLIANCE 2666 STATUS current 2667 DESCRIPTION 2668 "The compliance statement for SNMPv2 entities which 2669 implement UDP over IPv6." 2670 MODULE -- this module 2671 GROUP ipv6UdpGroup 2672 DESCRIPTION 2673 "This group is mandatory for all entities 2674 which implement UDP over IPv6." 2675 ::= { ipv6UdpCompliances 1 } 2677 ipv6UdpGroup OBJECT-GROUP 2678 OBJECTS { 2679 ipv6UdpInDatagrams, 2680 ipv6UdpNoPorts, 2681 ipv6UdpInErrors, 2682 ipv6UdpOutDatagrams, 2683 ipv6UdpLocalPort 2684 } 2685 STATUS current 2686 DESCRIPTION 2687 "The UDP group of objects providing information 2688 specific to UDP over IPv6." 2689 ::= { ipv6UdpGroups 1 } 2691 END 2693 5.4. The TCP Group 2695 IPV6-TCP-MIB DEFINITIONS ::= BEGIN 2697 IMPORTS 2698 MODULE-IDENTITY, OBJECT-TYPE, 2699 Unsigned32, Gauge32, Counter32, 2700 Integer32 FROM SNMPv2-SMI 2701 ipv6, Ipv6Address FROM IPV6-TC 2702 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 2703 ipv6IfIndex FROM IPV6-MIB; 2705 ipv6TcpMIB MODULE-IDENTITY 2706 LAST-UPDATED "9610042155Z" 2707 ORGANIZATION "IETF IPv6 MIB Working Group" 2708 CONTACT-INFO 2709 " Dimitry Haskin 2710 Postal: Bay Networks, Inc. 2711 2 Federal St. 2712 Billerica, MA 01821 2713 US 2715 Tel: +1-508-916-8124 2716 E-mail: dhaskin@baynetworks.com 2718 Steve Onishi 2719 Postal: Bay Networks, Inc. 2720 3 Federal Street 2721 Billerica, MA 01821 2722 US 2724 Tel: +1-508-916-3816 2725 E-mail: sonishi@baynetworks.com" 2726 DESCRIPTION 2727 "The MIB module for entities implementing TCP 2728 over IPv6." 2729 ::= { ipv6 4} 2731 -- the TCPv6 group 2733 ipv6TcpMIBObjects OBJECT IDENTIFIER ::= { ipv6TcpMIB 1 } 2734 -- Note that instances of object types that represent 2735 -- information about a particular TCP connection are 2736 -- transient; they persist only as long as the connection 2737 -- in question. 2739 ipv6TcpRtoAlgorithm OBJECT-TYPE 2740 SYNTAX INTEGER { 2741 other(1), -- none of the following 2743 constant(2), -- a constant rto 2744 rsre(3), -- MIL-STD-1778, Appendix B 2745 vanj(4) -- Van Jacobson's algorithm [8] 2746 } 2747 MAX-ACCESS read-only 2748 STATUS current 2749 DESCRIPTION 2750 "The algorithm used to determine the timeout value 2751 used for retransmitting unacknowledged octets." 2752 ::= { ipv6TcpMIBObjects 1 } 2754 ipv6TcpRtoMin OBJECT-TYPE 2755 SYNTAX Unsigned32 2756 UNITS "milliseconds" 2757 MAX-ACCESS read-only 2758 STATUS current 2759 DESCRIPTION 2760 "The minimum value permitted by a TCP 2761 implementation for the retransmission timeout, 2762 measured in milliseconds. More refined semantics 2763 for objects of this type depend upon the algorithm 2764 used to determine the retransmission timeout. In 2765 particular, when the timeout algorithm is rsre(3), 2766 an object of this type has the semantics of the 2767 LBOUND quantity described in RFC 793." 2768 ::= { ipv6TcpMIBObjects 2 } 2770 ipv6TcpRtoMax OBJECT-TYPE 2771 SYNTAX Unsigned32 2772 UNITS "milliseconds" 2773 MAX-ACCESS read-only 2774 STATUS current 2775 DESCRIPTION 2776 "The maximum value permitted by a TCP 2777 implementation for the retransmission timeout, 2778 measured in milliseconds. More refined semantics 2779 for objects of this type depend upon the algorithm 2780 used to determine the retransmission timeout. In 2781 particular, when the timeout algorithm is rsre(3), 2782 an object of this type has the semantics of the 2783 UBOUND quantity described in RFC 793." 2784 ::= { ipv6TcpMIBObjects 3 } 2786 ipv6TcpMaxConn OBJECT-TYPE 2787 SYNTAX Integer32 2788 MAX-ACCESS read-only 2789 STATUS current 2790 DESCRIPTION 2791 "The limit on the total number of TCP connections 2792 the entity can support. In entities where the 2793 maximum number of connections is dynamic, this 2794 object should contain the value -1." 2795 ::= { ipv6TcpMIBObjects 4 } 2797 ipv6TcpActiveOpens OBJECT-TYPE 2798 SYNTAX Counter32 2799 MAX-ACCESS read-only 2800 STATUS current 2801 DESCRIPTION 2802 "The number of times TCP connections have made a 2803 direct transition to the SYN-SENT state from the 2804 CLOSED state." 2805 ::= { ipv6TcpMIBObjects 5 } 2807 ipv6TcpPassiveOpens OBJECT-TYPE 2808 SYNTAX Counter32 2809 MAX-ACCESS read-only 2810 STATUS current 2811 DESCRIPTION 2812 "The number of times TCP connections have made a 2813 direct transition to the SYN-RCVD state from the 2814 LISTEN state." 2815 ::= { ipv6TcpMIBObjects 6 } 2817 ipv6TcpAttemptFails OBJECT-TYPE 2818 SYNTAX Counter32 2819 MAX-ACCESS read-only 2820 STATUS current 2821 DESCRIPTION 2822 "The number of times TCP connections have made a 2823 direct transition to the CLOSED state from either 2824 the SYN-SENT state or the SYN-RCVD state, plus the 2825 number of times TCP connections have made a direct 2826 transition to the LISTEN state from the SYN-RCVD 2827 state." 2828 ::= { ipv6TcpMIBObjects 7 } 2830 ipv6TcpEstabResets OBJECT-TYPE 2831 SYNTAX Counter32 2832 MAX-ACCESS read-only 2833 STATUS current 2834 DESCRIPTION 2835 "The number of times TCP connections have made a 2836 direct transition to the CLOSED state from either 2837 the ESTABLISHED state or the CLOSE-WAIT state." 2838 ::= { ipv6TcpMIBObjects 8 } 2840 ipv6TcpCurrEstab OBJECT-TYPE 2841 SYNTAX Gauge32 2842 MAX-ACCESS read-only 2843 STATUS current 2844 DESCRIPTION 2845 "The number of TCP connections for which the 2846 current state is either ESTABLISHED or CLOSE- 2847 WAIT." 2848 ::= { ipv6TcpMIBObjects 9 } 2850 ipv6TcpInSegs OBJECT-TYPE 2851 SYNTAX Counter32 2852 MAX-ACCESS read-only 2853 STATUS current 2854 DESCRIPTION 2855 "The total number of segments received, including 2856 those received in error. This count includes 2857 segments received on currently established 2858 connections." 2859 ::= { ipv6TcpMIBObjects 10 } 2861 ipv6TcpOutSegs OBJECT-TYPE 2862 SYNTAX Counter32 2863 MAX-ACCESS read-only 2864 STATUS current 2865 DESCRIPTION 2866 "The total number of segments sent, including 2867 those on current connections but excluding those 2868 containing only retransmitted octets." 2870 ::= { ipv6TcpMIBObjects 11 } 2872 ipv6TcpRetransSegs OBJECT-TYPE 2873 SYNTAX Counter32 2874 MAX-ACCESS read-only 2875 STATUS current 2876 DESCRIPTION 2877 "The total number of segments retransmitted - that 2878 is, the number of TCP segments transmitted 2879 containing one or more previously transmitted 2880 octets." 2881 ::= { ipv6TcpMIBObjects 12 } 2883 ipv6TcpInErrs OBJECT-TYPE 2884 SYNTAX Counter32 2885 MAX-ACCESS read-only 2886 STATUS current 2887 DESCRIPTION 2888 "The total number of segments received in error 2889 (e.g., bad TCP checksums)." 2890 ::= { ipv6TcpMIBObjects 13 } 2892 ipv6TcpOutRsts OBJECT-TYPE 2893 SYNTAX Counter32 2894 MAX-ACCESS read-only 2895 STATUS current 2896 DESCRIPTION 2897 "The number of TCP segments sent containing the 2898 RST flag." 2899 ::= { ipv6TcpMIBObjects 14 } 2901 -- the TCPv6 Connection table 2903 -- The TCPv6 connection table contains information 2904 -- about this entity's existing TCPv6 connections. 2906 ipv6TcpConnTable OBJECT-TYPE 2907 SYNTAX SEQUENCE OF Ipv6TcpConnEntry 2908 MAX-ACCESS not-accessible 2909 STATUS current 2910 DESCRIPTION 2911 "A table containing TCP connection-specific 2912 information." 2913 ::= { ipv6TcpMIBObjects 15 } 2915 ipv6TcpConnEntry OBJECT-TYPE 2916 SYNTAX Ipv6TcpConnEntry 2917 MAX-ACCESS not-accessible 2918 STATUS current 2919 DESCRIPTION 2920 "Information about a particular current TCP 2921 connection. An object of this type is transient, 2922 in that it ceases to exist when (or soon after) 2923 the connection makes the transition to the CLOSED 2924 state." 2925 INDEX { ipv6IfIndex, 2926 ipv6TcpConnLocalAddress, 2927 ipv6TcpConnLocalPort, 2928 ipv6TcpConnRemAddress, 2929 ipv6TcpConnRemPort } 2930 ::= { ipv6TcpConnTable 1 } 2932 Ipv6TcpConnEntry ::= 2933 SEQUENCE { 2934 ipv6TcpConnLocalAddress Ipv6Address, 2935 ipv6TcpConnLocalPort INTEGER (0..65535), 2936 ipv6TcpConnRemAddress Ipv6Address, 2937 ipv6TcpConnRemPort INTEGER (0..65535), 2938 ipv6TcpConnState INTEGER 2939 } 2941 ipv6TcpConnLocalAddress OBJECT-TYPE 2942 SYNTAX Ipv6Address 2943 MAX-ACCESS not-accessible 2944 STATUS current 2945 DESCRIPTION 2946 "The local IPv6 address for this TCP connection. In 2947 the case of a connection in the listen state which 2948 is willing to accept connections for any IPv6 2949 address associated with the interface, the value 2950 ::0 is used." 2951 ::= { ipv6TcpConnEntry 1 } 2953 ipv6TcpConnLocalPort OBJECT-TYPE 2954 SYNTAX INTEGER (0..65535) 2955 MAX-ACCESS not-accessible 2956 STATUS current 2957 DESCRIPTION 2958 "The local port number for this TCP connection." 2959 ::= { ipv6TcpConnEntry 2 } 2961 ipv6TcpConnRemAddress OBJECT-TYPE 2962 SYNTAX Ipv6Address 2963 MAX-ACCESS not-accessible 2964 STATUS current 2965 DESCRIPTION 2966 "The remote IPv6 address for this TCP connection." 2967 ::= { ipv6TcpConnEntry 3 } 2969 ipv6TcpConnRemPort OBJECT-TYPE 2970 SYNTAX INTEGER (0..65535) 2971 MAX-ACCESS not-accessible 2972 STATUS current 2973 DESCRIPTION 2974 "The remote port number for this TCP connection." 2975 ::= { ipv6TcpConnEntry 4 } 2977 ipv6TcpConnState OBJECT-TYPE 2978 SYNTAX INTEGER { 2979 closed(1), 2980 listen(2), 2981 synSent(3), 2982 synReceived(4), 2983 established(5), 2984 finWait1(6), 2985 finWait2(7), 2986 closeWait(8), 2987 lastAck(9), 2988 closing(10), 2989 timeWait(11), 2990 deleteTCB(12) 2991 } 2992 MAX-ACCESS read-write 2993 STATUS current 2994 DESCRIPTION 2995 "The state of this TCP connection. 2997 The only value which may be set by a management 2998 station is deleteTCB(12). Accordingly, it is 2999 appropriate for an agent to return a `badValue' 3000 response if a management station attempts to set 3001 this object to any other value. 3003 If a management station sets this object to the 3004 value deleteTCB(12), then this has the effect of 3005 deleting the TCB (as defined in RFC 793) of the 3006 corresponding connection on the managed node, 3007 resulting in immediate termination of the 3008 connection. 3010 As an implementation-specific option, a RST 3011 segment may be sent from the managed node to the 3012 other TCP endpoint (note however that RST segments 3013 are not sent reliably)." 3014 ::= { ipv6TcpConnEntry 5 } 3016 -- conformance information 3018 ipv6TcpConformance OBJECT IDENTIFIER ::= { ipv6TcpMIB 2 } 3020 ipv6TcpCompliances OBJECT IDENTIFIER ::= { ipv6TcpConformance 1 } 3021 ipv6TcpGroups OBJECT IDENTIFIER ::= { ipv6TcpConformance 2 } 3023 -- compliance statements 3025 ipv6TcpCompliance MODULE-COMPLIANCE 3026 STATUS current 3027 DESCRIPTION 3028 "The compliance statement for SNMPv2 entities which 3029 implement TCP over IPv6." 3030 MODULE -- this module 3031 GROUP ipv6TcpGroup 3032 DESCRIPTION 3033 "This group is mandatory for all entities 3034 which implement TCP over IPv6." 3035 ::= { ipv6TcpCompliances 1 } 3037 ipv6TcpGroup OBJECT-GROUP 3038 OBJECTS { 3039 ipv6TcpRtoAlgorithm, 3040 ipv6TcpRtoMin, 3041 ipv6TcpRtoMax, 3042 ipv6TcpMaxConn, 3043 ipv6TcpActiveOpens, 3044 ipv6TcpPassiveOpens, 3045 ipv6TcpAttemptFails, 3046 ipv6TcpEstabResets, 3047 ipv6TcpCurrEstab, 3048 ipv6TcpInSegs, 3049 ipv6TcpOutSegs, 3050 ipv6TcpRetransSegs, 3051 ipv6TcpInErrs, 3052 ipv6TcpOutRsts, 3053 ipv6TcpConnState 3054 } 3055 STATUS current 3056 DESCRIPTION 3057 "The TCP group of objects providing information 3058 specific to TCP over IPv6." 3059 ::= { ipv6TcpGroups 1 } 3061 END 3063 6. Acknowledgements 3065 This document borrows from MIB works produced by IETF for 3066 IPv4-based internets. 3068 7. References 3070 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 3071 and S. Waldbusser, "Structure of Management Information 3072 for Version 2 of the Simple Network Management Protocol 3073 (SNMPv2)", RFC 1902, January 1996. 3075 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 3076 and S. Waldbusser, "Textual Conventions for Version 2 of 3077 the Simple Network Management Protocol (SNMPv2)", RFC 3078 1903, January 1996. 3080 [3] McCloghrie, K., and M. Rose, Editors, "Management 3081 Information Base for Network Management of TCP/IP-based 3082 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 3083 Performance Systems International, March 1991. 3085 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A 3086 Simple Network Management Protocol (SNMP)", STD 15, RFC 3087 1157, SNMP Research, Performance Systems International, 3088 MIT Lab for Computer Science, May 1990. 3090 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. 3091 and S. Waldbusser, "Protocol Operations for Version 2 of 3092 the Simple Network Management Protocol (SNMPv2)", RFC 3093 1905, January 1996. 3095 [6] McCloghrie, K. and F. Kastenholz, "Evolution of the 3096 Interfaces Group of MIB-II" , RFC 1573, January 1994. 3098 [7] Deering, S., and R. Hinden, "Internet Protocol, Version 6 3099 (IPv6) Specification", RFC 1883, December 1995. 3101 [8] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 3102 1988, Stanford, California. 3104 8. Security Considerations 3106 Security issues are not discussed in this memo. 3108 9. Authors' Address 3110 Dimitry Haskin 3111 Bay Networks, Inc. 3112 2 Federal Street 3113 Billerica, MA 01821 3114 email: dhaskin@baynetworks.com 3116 Steve Onishi 3117 Bay Networks, Inc. 3118 3 Federal Street 3119 Billerica, MA 01821 3120 email: sonishi@baynetworks.com