idnits 2.17.1 draft-ietf-ospf-ospfv3-mib-15.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 23, 2009) is 5392 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: 'RFC3414' is defined on line 4439, but no explicit reference was found in the text == Unused Reference: 'RFC3415' is defined on line 4443, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2460 (Obsoleted by RFC 8200) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group D. Joyal (Editor) 3 Internet Draft Nortel 4 Intended status: Standards Track V. Manral (Editor) 5 Expires: December 25, 2009 IP Infusion 6 June 23, 2009 8 Management Information Base for OSPFv3 9 draft-ietf-ospf-ospfv3-mib-15.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with 14 the provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on December 25, 2009. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents in effect on the date of 41 publication of this document (http://trustee.ietf.org/license- 42 info). Please review these documents carefully, as they describe 43 your rights and restrictions with respect to this document. 45 This document may contain material from IETF Documents or IETF 46 Contributions published or made publicly available before November 47 10, 2008. The person(s) controlling the copyright in some of this 48 material may not have granted the IETF Trust the right to allow 49 modifications of such material outside the IETF Standards Process. 50 Without obtaining an adequate license from the person(s) controlling 51 the copyright in such materials, this document may not be modified 52 outside the IETF Standards Process, and derivative works of it may 53 not be created outside the IETF Standards Process, except to format 54 it for publication as an RFC or to translate it into languages other 55 than English. 57 Abstract 59 This memo defines a portion of the Management Information Base (MIB) 60 for use with network management protocols in IPv6-based internets. 61 In particular, it defines objects for managing the Open Shortest Path 62 First (OSPF) Routing Protocol for IPv6, otherwise known as OSPF 63 version 3 (OSPFv3). 65 Please send comments to ospf@ietf.org. 67 Table of Contents 69 1. The Internet-Standard Management Framework.....................3 70 2. Overview.......................................................3 71 2.1. IPv6 Interfaces..............................................3 72 2.2. Addressing Semantics.........................................3 73 2.3. Authentication...............................................4 74 2.4. Type of Service..............................................4 75 2.5. Flooding Scope...............................................4 76 2.6. Virtual Links................................................4 77 2.7. Neighbors....................................................4 78 2.8. OSPFv3 Counters..............................................4 79 2.9. Multiple OSPFv3 Instances....................................5 80 2.10. Notifications ..............................................5 81 2.11. Conventions.................................................5 82 3. OSPFv3 Notification Overview...................................5 83 3.1. Introduction.................................................5 84 3.2. Ignoring Initial Activity....................................5 85 3.3. Throttling Notifications.....................................6 86 3.4. One Notification Per OSPFv3 Event............................6 87 3.5. Polling Event Counters.......................................6 88 4. Structure of the OSPFv3 MIB....................................7 89 4.1. General Variables............................................7 90 4.2. Area Table...................................................7 91 4.3. Area-Scope, Link-Scope and AS-Scope Link State Database......7 92 4.4. Host Table...................................................7 93 4.5. Interface Table..............................................7 94 4.6. Virtual Interface Table......................................7 95 4.7. Neighbor, Configured Neighbor and Virtual Neighbor Tables....7 96 4.8. Area Aggregate Table.........................................7 97 4.9. Notifications................................................8 98 5. Definitions....................................................8 99 6. Security Considerations.......................................74 100 7. IANA Considerations...........................................74 101 8. Acknowledgements..............................................75 102 9. Normative References..........................................75 103 10. Informative References.......................................76 104 11. Contributors' Addresses......................................76 105 12. Authors' Addresses...........................................76 107 1. The Internet-Standard Management Framework 109 For a detailed overview of the documents that describe the current 110 Internet-Standard Management Framework, please refer to section 7 of 111 RFC 3410 [RFC3410]. 113 Managed objects are accessed via a virtual information store, termed 114 the Management Information Base or MIB. MIB objects are generally 115 accessed through the Simple Network Management Protocol (SNMP). 116 Objects in the MIB are defined using the mechanisms defined in the 117 Structure of Management Information (SMI). This memo specifies a MIB 118 module that is compliant to the SMIv2, which is described in STD 58, 119 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 120 [RFC2580] 122 2. Overview 124 This memo defines a portion of the Management Information Base (MIB) 125 for managing the Open Shortest Path First Routing Protocol for IPv6 126 [RFC5340], otherwise known as OSPF version 3 (OSPFv3). Though the 127 fundamental mechanisms of OSPF version 2 (OSPFv2) [RFC2328] remain 128 unchanged in OSPFv3, some changes were necessary due to differences 129 in IP address size and in protocol semantics between IPv4 and IPv6. 130 In many cases, where the protocol operations have not changed from 131 OSPFv2, the specification for OSPFv3 does not restate the details, 132 but instead refers to the relevant sections in the OSPFv2 133 specification. This MIB follows along the same lines and includes 134 Reference clauses referring to the OSPFv2 specification when 135 applicable. 137 2.1. IPv6 Interfaces 139 IPv6 interfaces attach to links [RFC2460]. A link is roughly defined 140 as the layer below IPv6 (e.g. Ethernet, IPv4 Tunnel). One or more 141 IPv6 prefixes can be associated with an IPv6 interface. IPv6 142 interfaces and the prefixes associated with those interfaces can be 143 configured via the IP-MIB [RFC4293]. IPv6 interfaces are configured 144 in the IPv6 Interface Table and IPv6 prefixes are configured in the 145 Internet Address Prefix Table. An IPv6 interface is identified by a 146 unique index value. IPv6 Address Prefix Table entries associated with 147 an IPv6 interface reference the interface's index. 149 Whereas an interface identifier in OSPFv2 is a local IPv4 address or 150 MIB-2 interface index, an OSPFv3 interface identifier is an IPv6 151 interface index. For example, the index value of an OSPFv3 Interface 152 Table entry is the IPv6 interface index of the IPv6 interface over 153 which OSPFv3 is configured to operate. 155 2.2. Addressing Semantics 157 Router ID, Area ID and Link State ID remain at the OSPFv2 size of 32 158 bits. To ensure uniqueness, a router running both IPv4 and IPv6 159 concurrently can continue to use a local IPv4 host address, 160 represented as an unsigned 32-bit value, as the OSPFv3 Router ID. 161 Otherwise, the Router ID must be selected using another method (e.g. 162 administratively assigned). 164 Router ID, Area ID and Link State ID do not have addressing semantics 165 in OSPFv3, so their syntax is changed to Unsigned32. The Router ID 166 index component comes before the Link State ID index component in the 167 OSPFv3 MIB because the lack of addressing semantics in Link State IDs 168 make them less unique identifiers than the Router ID. It is more 169 useful to do partial OID lookups extending to the Router ID rather 170 than the Link State ID. 172 2.3. Authentication 174 In OSPFv3, authentication has been removed from the protocol itself. 175 MIB objects related to authentication are not carried forward from 176 the OSPFv2 MIB. 178 2.4. Type of Service 180 OSPFv2 MIB objects related to Type of Service (ToS) are not carried 181 forward to the OSPFv3 MIB. 183 2.5. Flooding Scope 185 Flooding scope for LSAs has been generalized and is now explicitly 186 encoded in the LSA's LS type field. The action to take upon receipt 187 of unknown LSA types is also encoded in the LS type field [RFC5340]. 188 The OSPFv3 MIB defines three Link State Database tables, one each 189 for Area-scope LSAs, Link-scope LSAs and AS-scope LSAs. 191 2.6. Virtual Links 193 Since addressing semantics have been removed from router-LSAs in 194 OSPFv3, Virtual Links now need to be assigned an interface ID for 195 advertisement in Hello packets and in router-LSAs. A read-only 196 object has been added to the Virtual Interface Table entry to view 197 the assigned interface ID. 199 2.7. Neighbors 201 The OSPFv3 Neighbor Table is a read-only table that contains 202 information learned from Hellos received from neighbors, including 203 configured neighbors. The OSPFv3 Configured Neighbor Table contains 204 entries for manually configured neighbors for use on NBMA and 205 Point-to-Multipoint interface types. 207 2.8. OSPFv3 Counters 209 This MIB defines several counters, namely: 211 - ospfv3OriginateNewLsas, ospfv3RxNewLsas in the 212 ospfv3GeneralGroup 213 - ospfv3AreaSpfRuns, ospfv3AreaNssaTranslatorEvents in the 214 ospfv3AreaTable 215 - ospfv3IfEvents in the ospfv3IfTable 216 - ospfv3VirtIfEvents in the ospfv3VirtIfTable 217 - ospfv3NbrEvents in the ospfv3NbrTable 218 - ospfv3VirtNbrEvents in the ospfv3VirtNbrTable 220 As a best practice, a management entity, when reading these counters, 221 should use the discontinuity object, ospfv3DiscontinuityTime, to 222 determine if an event that would invalidate the management entity 223 understanding of the counters has occurred. A restart of the OSPFv3 224 routing process is a possible example of a discontinuity event. 226 2.9. Multiple OSPFv3 Instances 228 SNMPv3 supports "Contexts" that can be used to implement MIB views on 229 multiple OSPFv3 instances on the same system. See [RFC3411] or its 230 successors for details. 232 2.10. Notifications 234 Notifications define a set of notifications, objects, and mechanisms 235 to enhance the ability to manage IP internetworks that use OSPFv3 as 236 their Interior Gateway Protocol (IGP). 238 2.11 Conventions 240 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 241 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 242 "OPTIONAL" in this document are to be interpreted as described in 243 RFC 2119 [RFC2119]. 245 3. OSPFv3 Notification Overview 247 3.1. Introduction 249 OSPFv3 is an event-driven routing protocol, where an event can be 250 a change in an OSPFv3 interface's link-level status, the 251 expiration of an OSPFv3 timer, or the reception of an OSPFv3 252 protocol packet. Many of the actions that OSPFv3 takes as a result 253 of these events will result in a change of the routing topology. 255 As routing topologies become large and complex, it is often 256 difficult to locate the source of a topology change or 257 unpredicted routing path by polling a large number or routers. 258 Because of the difficulty of polling a large number of devices, 259 a more prudent approach is for devices to notify a network manager 260 of potentially critical OSPF events using SNMP notifications. 262 3.2 Ignoring Initial Activity 264 The majority of critical events occur when OSPFv3 is enabled on a 265 router, at which time the designated router is elected and 266 neighbor adjacencies are formed. During this initial period, a 267 potential flood of notifications is unnecessary since the 268 events are expected. To avoid unnecessary notifications, a 269 router should not originate expected OSPFv3 interface-related 270 notifications until two of that interface's dead timer intervals 271 have elapsed. The expected OSPFv3 interface notifications are 272 ospfv3IfStateChange, ospfv3VirtIfStateChange, 273 ospfv3NbrStateChange, and ospfv3VirtNbrStateChange. 275 3.3 Throttling Notifications 277 The mechanism for throttling the notifications is similar to 278 the mechanism explained in RFC 1224 [RFC1224]. The basic premise 279 of the throttling mechanism is that of a sliding window, defined 280 in seconds and an upper bound on the number of notifications that 281 may be generated within this window. Note that unlike RFC 1224, 282 notifications are not sent to inform the network manager that the 283 throttling mechanism has kicked in. 285 A single window should be used to throttle all OSPFv3 286 notifications types except for the ospfv3LsdbOverflow and the 287 ospfv3LsdbApproachingOverflow notifications, which should not be 288 throttled. For example, with a window time of 3, an upper bound 289 of 3, and events to cause notifications 1, 2, 3, and 4 (4 290 notifications within a 3-second period), the 4th notification 291 should not be generated. 293 Appropriate values are 7 notifications with a window time of 294 10 seconds. 296 3.4 One Notification Per OSPFv3 Event 298 Several of the notifications defined in this MIB are generated as 299 the result of finding an unusual condition while parsing an OSPFv3 300 packet or a processing a timer event. There may be more than one 301 unusual condition detected while handling the event. For example, 302 a link state update packet may contain several retransmitted link 303 state advertisements (LSAs), or a retransmitted database 304 description packet may contain several database description 305 entries. To limit the number of notifications and variables, 306 OSPFv3 should generate at most one notification per OSPFv3 event. 307 Only the variables associated with the first unusual 308 condition should be included with the notification. Similarly, if 309 more than one type of unusual condition is encountered while 310 parsing the packet, only the first event will generate a 311 notification. 313 3.5 Polling Event Counters 315 Many of the tables in the OSPFv3 MIB contain generalized event 316 counters. By enabling the notifications defined in this document, 317 a network manager can obtain more specific information about these 318 events. A network manager may want to poll these event counters 319 and enable OSPFv3 notifications when a particular counter starts 320 increasing abnormally. 322 4. Structure of the OSPFv3 MIB 324 The MIB is composed of the following sections: 326 General Variables 327 Area Table 328 Area-Scope Link State Database 329 Link-Scope Link State Databases (non-virtual and virtual) 330 AS-Scope Link State Database 331 Host Table 332 Interface Table 333 Virtual Interface Table 334 Neighbor Table 335 Configured Neighbor Table 336 Virtual Neighbor Table 337 Area Aggregate Table 338 Notifications 340 4.1. General Variables 342 The General Variables are global to the OSPFv3 Process. 344 4.2. Area Table 346 The Area Data Structure describes the OSPFv3 Areas that the 347 router participates in. 349 4.3. Area-Scope, Link-Scope and AS-Scope Link State Database 351 The Link State Databases are provided primarily to provide 352 detailed information for network debugging. There are separate 353 tables for Link-Scope LSAs received over non-virtual and virtual 354 interfaces. 356 4.4. Host Table 358 The Host Table is provided to view configured Host Route 359 information. 361 4.5. Interface Table 363 The Interface Table describes the various IPv6 links on which 364 OSPFv3 is configured. 366 4.6. Virtual Interface Table 368 The Virtual Interface Table describes virtual OSPFv3 links. 370 4.7. Neighbor, Configured Neighbor and Virtual Neighbor Tables 371 The Neighbor Table, the Configured Neighbor Table and the Virtual 372 Neighbor Table describe the neighbors to the OSPFv3 Process. 374 4.8. Area Aggregate Table 376 The Area Aggregate Table describes prefixes, which summarize 377 routing information for export outside of an Area. 379 4.9 Notifications 381 Notifications are defined for OSPFv3 events. Several objects are 382 defined specifically as variables to be used with notifications. 384 5. Definitions 386 OSPFV3-MIB DEFINITIONS ::= BEGIN 388 IMPORTS 389 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, 390 Counter32, Gauge32, Integer32, Unsigned32 391 FROM SNMPv2-SMI 392 TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeStamp 393 FROM SNMPv2-TC 394 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 395 FROM SNMPv2-CONF 396 InterfaceIndex 397 FROM IF-MIB 398 InetAddressType, InetAddress, InetAddressPrefixLength, 399 InetAddressIPv6 400 FROM INET-ADDRESS-MIB 401 Metric, BigMetric, Status, 402 HelloRange, DesignatedRouterPriority 403 FROM OSPF-MIB; 405 ospfv3MIB MODULE-IDENTITY 406 LAST-UPDATED "200906231200Z" 407 ORGANIZATION "IETF OSPF Working Group" 408 CONTACT-INFO 409 "WG E-Mail: ospf@ietf.org 410 WG Chairs: Acee Lindem 411 acee@redback.com 413 Abhay Roy 414 akr@cisco.com 416 Editors: Dan Joyal 417 Nortel 418 600 Technology Park Drive 419 Billerica, MA 01821, USA 420 djoyal@nortel.com 421 Vishwas Manral 422 IP Infusion 423 Bangalore 424 India 425 vishwas@ipinfusion.com" 427 DESCRIPTION 428 "The MIB module for OSPF version 3. 430 Copyright (C) The IETF Trust (2009). 431 This version of this MIB module is part of 432 RFC xxxx; see the RFC itself for full legal 433 notices." 435 REVISION "200906231200Z" 436 DESCRIPTION -- RFC Editor assigns RFC xxxx 437 "Initial version, published as RFC xxxx" 438 -- RFC Ed.: replace xxxx with actual RFC number & remove this note 440 ::= { mib-2 YYY } 441 -- RFC Ed.: replace YYY with IANA-assigned number & remove this note 443 -- Textual conventions 445 Ospfv3UpToRefreshIntervalTC ::= TEXTUAL-CONVENTION 446 DISPLAY-HINT "d" 447 STATUS current 448 DESCRIPTION 449 "The values one might be able to configure for 450 variables bounded by the Refresh Interval" 451 REFERENCE 452 "OSPF Version 2, Section B. Architectural Constants" 453 SYNTAX Unsigned32 (1..1800) 455 Ospfv3DeadIntervalRangeTC ::= TEXTUAL-CONVENTION 456 DISPLAY-HINT "d" 457 STATUS current 458 DESCRIPTION 459 "The range, in seconds, of dead interval value." 460 REFERENCE 461 "OSPF Version 3, Section C.3 Router interface 462 parameters" 463 SYNTAX Unsigned32 (1..'FFFF'h) 465 Ospfv3RouterIdTC ::= TEXTUAL-CONVENTION 466 DISPLAY-HINT "d" 467 STATUS current 468 DESCRIPTION 469 "A 32-bit, unsigned integer uniquely identifying the 470 router in the Autonomous System. To ensure 471 uniqueness, this may default to the value of one of 472 the router's IPv4 host addresses if IPv4 is 473 configured on the router." 475 REFERENCE 476 "OSPF Version 3, Section C.1 Global parameters" 477 SYNTAX Unsigned32 (1..'FFFFFFFF'h) 479 Ospfv3LsIdTC ::= TEXTUAL-CONVENTION 480 DISPLAY-HINT "d" 481 STATUS current 482 DESCRIPTION 483 "A unique 32-bit identifier of the piece of the 484 routing domain that is being described by a Link 485 State advertisement. In contrast to OSPFv2, the 486 LSID has no addressing semantics." 487 REFERENCE 488 "OSPF Version 2, Section 2.1.4 Link State ID" 489 SYNTAX Unsigned32 (1..'FFFFFFFF'h) 491 Ospfv3AreaIdTC ::= TEXTUAL-CONVENTION 492 DISPLAY-HINT "d" 493 STATUS current 494 DESCRIPTION 495 "An OSPFv3 Area Identifier. A value of zero 496 identifies the backbone area." 497 REFERENCE 498 "OSPF Version 3, Section C.3 Router interface 499 parameters" 500 SYNTAX Unsigned32 (0..'FFFFFFFF'h) 502 Ospfv3IfInstIdTC ::= TEXTUAL-CONVENTION 503 DISPLAY-HINT "d" 504 STATUS current 505 DESCRIPTION 506 "An OSPFv3 interface instance ID" 507 REFERENCE 508 "OSPF Version 3, Section C.3 Router interface 509 parameters" 510 SYNTAX Unsigned32 (0..255) 512 Ospfv3LsaSequenceTC ::= TEXTUAL-CONVENTION 513 DISPLAY-HINT "d" 514 STATUS current 515 DESCRIPTION 516 "The sequence number field is a signed 32-bit 517 integer. It is used to detect old and duplicate 518 link state advertisements. The space of 519 sequence numbers is linearly ordered. The 520 larger the sequence number the more recent the 521 advertisement." 522 REFERENCE 523 "OSPF Version 2, Section 12.1.6, LS sequence 524 number." 525 SYNTAX Integer32 527 Ospfv3LsaAgeTC ::= TEXTUAL-CONVENTION 528 DISPLAY-HINT "d" 529 STATUS current 530 DESCRIPTION 531 "The age of the link state advertisement in 532 seconds. The high order bit of the LS age 533 field is considered the DoNotAge bit for 534 support of on-demand circuits." 535 REFERENCE 536 "OSPF Version 2, Section 12.1.1, LS age and 537 Extending OSPF to Support Demand Circuits, 538 Section 2.2, The LS age field." 539 SYNTAX Unsigned32 (0..3600 | 32768..36368) 541 -- Top-level structure of MIB 542 ospfv3Notifications OBJECT IDENTIFIER ::= { ospfv3MIB 0 } 543 ospfv3Objects OBJECT IDENTIFIER ::= { ospfv3MIB 1 } 544 ospfv3Conformance OBJECT IDENTIFIER ::= { ospfv3MIB 2 } 546 -- OSPFv3 General Variables 548 -- These parameters apply globally to the Router's 549 -- OSPFv3 Process. 551 ospfv3GeneralGroup OBJECT IDENTIFIER ::= { ospfv3Objects 1 } 553 ospfv3RouterId OBJECT-TYPE 554 SYNTAX Ospfv3RouterIdTC 555 MAX-ACCESS read-write 556 STATUS current 557 DESCRIPTION 558 "A 32-bit unsigned integer uniquely identifying 559 the router in the Autonomous System. To ensure 560 uniqueness, this may default to the 32-bit 561 unsigned integer representation of one of 562 the router's IPv4 interface addresses (if IPv4 563 is configured on the router). 565 This object is persistent and when written the 566 entity SHOULD save the change to non-volatile 567 storage." 568 REFERENCE 569 "OSPF Version 3, Section C.1 Global parameters" 570 ::= { ospfv3GeneralGroup 1 } 572 ospfv3AdminStatus OBJECT-TYPE 573 SYNTAX Status 574 MAX-ACCESS read-write 575 STATUS current 576 DESCRIPTION 577 "The administrative status of OSPFv3 in the 578 router. The value 'enabled' denotes that the 579 OSPFv3 Process is active on at least one 580 interface; 'disabled' disables it on all 581 interfaces. 583 This object is persistent and when written the 584 entity SHOULD save the change to non-volatile 585 storage." 586 ::= { ospfv3GeneralGroup 2 } 588 ospfv3VersionNumber OBJECT-TYPE 589 SYNTAX INTEGER { version3 (3) } 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "The version number of OSPF for IPv6 is 3." 594 ::= { ospfv3GeneralGroup 3 } 596 ospfv3AreaBdrRtrStatus OBJECT-TYPE 597 SYNTAX TruthValue 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "A flag to denote whether this router is an area 602 border router. The value of this object is true(1) 603 when the router is an area border router." 604 REFERENCE 605 "OSPF Version 2, Section 3 Splitting the AS into 606 Areas" 607 ::= { ospfv3GeneralGroup 4 } 609 ospfv3ASBdrRtrStatus OBJECT-TYPE 610 SYNTAX TruthValue 611 MAX-ACCESS read-write 612 STATUS current 613 DESCRIPTION 614 "A flag to note whether this router is 615 configured as an Autonomous System border router. 617 This object is persistent and when written the 618 entity SHOULD save the change to non-volatile 619 storage." 620 REFERENCE 621 "OSPF Version 2, Section 3.3 Classification of 622 routers" 623 ::= { ospfv3GeneralGroup 5 } 625 ospfv3AsScopeLsaCount OBJECT-TYPE 626 SYNTAX Gauge32 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "The number of AS-Scope (e.g. AS-External) link state 631 advertisements in the link state database." 632 ::= { ospfv3GeneralGroup 6 } 634 ospfv3AsScopeLsaCksumSum OBJECT-TYPE 635 SYNTAX Unsigned32 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The 32-bit unsigned sum of the LS checksums of 640 the AS-scoped link state advertisements 641 contained in the link state database. This sum 642 can be used to determine if there has been a 643 change in a router's link state database or 644 to compare the link state database of two 645 routers." 646 ::= { ospfv3GeneralGroup 7 } 648 ospfv3OriginateNewLsas OBJECT-TYPE 649 SYNTAX Counter32 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "The number of new link-state advertisements 654 that have been originated. This number is 655 incremented each time the router originates a new 656 LSA. 658 Discontinuities in the value of this counter 659 can occur at re-initialization of the management 660 system and at other times as indicated by the 661 value of ospfv3DiscontinuityTime." 662 ::= { ospfv3GeneralGroup 8 } 664 ospfv3RxNewLsas OBJECT-TYPE 665 SYNTAX Counter32 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The number of link state advertisements 670 received determined to be new instantiations. 671 This number does not include newer 672 instantiations of self-originated link state 673 advertisements. 675 Discontinuities in the value of this counter 676 can occur at re-initialization of the management 677 system and at other times as indicated by the 678 value of ospfv3DiscontinuityTime." 679 ::= { ospfv3GeneralGroup 9 } 681 ospfv3ExtLsaCount OBJECT-TYPE 682 SYNTAX Gauge32 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "The number of External(LS type 0x4005) in the 687 link state database" 688 ::= { ospfv3GeneralGroup 10 } 690 ospfv3ExtAreaLsdbLimit OBJECT-TYPE 691 SYNTAX Integer32 (-1..'7FFFFFFF'h) 692 MAX-ACCESS read-write 693 STATUS current 694 DESCRIPTION 695 "The maximum number of non-default 696 AS-external-LSAs entries that can be stored in the 697 link state database. If the value is -1, then 698 there is no limit. 700 When the number of non-default AS-external-LSAs 701 in a router's link-state database reaches 702 ospfv3ExtAreaLsdbLimit, the router enters Overflow 703 state. The router never holds more than 704 ospfv3ExtAreaLsdbLimit non-default AS-external-LSAs 705 in its database. ospfv3ExtAreaLsdbLimit MUST be set 706 identically in all routers attached to the OSPFv3 707 backbone and/or any regular OSPFv3 area. (i.e., 708 OSPFv3 stub areas and NSSAs are excluded). 710 This object is persistent and when written the 711 entity SHOULD save the change to non-volatile 712 storage." 713 ::= { ospfv3GeneralGroup 11 } 715 ospfv3ExitOverflowInterval OBJECT-TYPE 716 SYNTAX Unsigned32 717 UNITS "seconds" 718 MAX-ACCESS read-write 719 STATUS current 720 DESCRIPTION 721 "The number of seconds that, after entering 722 Overflow State, a router will attempt to leave 723 Overflow State. This allows the router to again 724 originate non-default, AS-External-LSAs. When 725 set to 0, the router will not leave Overflow 726 State until restarted. 728 This object is persistent and when written the 729 entity SHOULD save the change to non-volatile 730 storage." 731 ::= { ospfv3GeneralGroup 12 } 733 ospfv3DemandExtensions OBJECT-TYPE 734 SYNTAX TruthValue 735 MAX-ACCESS read-write 736 STATUS current 737 DESCRIPTION 738 "The router's support for demand circuits. 739 The value of this object is true(1) when 740 demand circuits are supported. 742 This object is persistent and when written the 743 entity SHOULD save the change to non-volatile 744 storage." 745 REFERENCE 746 "OSPF Version 2, Appendix on Demand Circuits" 747 ::= { ospfv3GeneralGroup 13 } 749 ospfv3ReferenceBandwidth OBJECT-TYPE 750 SYNTAX Unsigned32 751 UNITS "kilobits per second" 752 MAX-ACCESS read-write 753 STATUS current 754 DESCRIPTION 755 "Reference bandwidth in kilobits per second for 756 calculating default interface metrics. The 757 default value is 100,000 KBPS (100 MBPS) 759 This object is persistent and when written the 760 entity SHOULD save the change to non-volatile 761 storage." 762 REFERENCE 763 "OSPF Version 2, Section C.3 Router interface 764 parameters" 765 DEFVAL { 100000 } 766 ::= { ospfv3GeneralGroup 14 } 768 ospfv3RestartSupport OBJECT-TYPE 769 SYNTAX INTEGER { none (1), 770 plannedOnly (2), 771 plannedAndUnplanned (3) 772 } 773 MAX-ACCESS read-write 774 STATUS current 775 DESCRIPTION 776 "The router's support for OSPF Graceful restart. 777 Options include: no restart support, only planned 778 restarts or both planned and unplanned restarts. 780 This object is persistent and when written the 781 entity SHOULD save the change to non-volatile 782 storage." 783 REFERENCE "Graceful OSPF Restart, Appendix B.1 Global 784 Parameters" 785 ::= { ospfv3GeneralGroup 15 } 787 ospfv3RestartInterval OBJECT-TYPE 788 SYNTAX Ospfv3UpToRefreshIntervalTC 789 UNITS "seconds" 790 MAX-ACCESS read-write 791 STATUS current 792 DESCRIPTION 793 "Configured OSPF Graceful restart timeout interval. 795 This object is persistent and when written the 796 entity SHOULD save the change to non-volatile 797 storage." 798 REFERENCE "Graceful OSPF Restart, Appendix B.1 Global 799 Parameters (Minimum subset)" 800 DEFVAL { 120 } 801 ::= { ospfv3GeneralGroup 16 } 803 ospfv3RestartStrictLsaChecking OBJECT-TYPE 804 SYNTAX TruthValue 805 MAX-ACCESS read-write 806 STATUS current 807 DESCRIPTION 808 "Indicates if strict LSA checking is enabled for 809 graceful restart. A value of true(1) indicates that 810 strict LSA checking is enabled. 812 This object is persistent and when written 813 the entity SHOULD save the change to non-volatile 814 storage." 815 REFERENCE "Graceful OSPF Restart, Appendix B.2 Global 816 Parameters (Optional)" 817 DEFVAL { true } 818 ::= { ospfv3GeneralGroup 17 } 820 ospfv3RestartStatus OBJECT-TYPE 821 SYNTAX INTEGER { notRestarting (1), 822 plannedRestart (2), 823 unplannedRestart (3) 824 } 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The current status of OSPF Graceful restart capability." 829 ::= { ospfv3GeneralGroup 18 } 831 ospfv3RestartAge OBJECT-TYPE 832 SYNTAX Ospfv3UpToRefreshIntervalTC 833 UNITS "seconds" 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "Remaining time in current OSPF Graceful restart 838 interval." 839 ::= { ospfv3GeneralGroup 19 } 841 ospfv3RestartExitReason OBJECT-TYPE 842 SYNTAX INTEGER { none (1), 843 inProgress (2), 844 completed (3), 845 timedOut (4), 846 topologyChanged (5) 847 } 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION 851 "Describes the outcome of the last attempt at a 852 Graceful restart. 854 none:............no restart has yet been attempted. 855 inProgress:......a restart attempt is currently underway. 856 completed:.......the last restart completed successfully. 857 timedOut:........the last restart timed out. 858 topologyChanged:.the last restart was aborted due to 859 a topology change." 860 ::= { ospfv3GeneralGroup 20 } 862 ospfv3NotificationEnable OBJECT-TYPE 863 SYNTAX TruthValue 864 MAX-ACCESS read-write 865 STATUS current 866 DESCRIPTION 867 "This object provides a coarse level of control 868 over the generation of OSPFv3 notifications. 869 Fine grain control can be accomplished by utilizing 870 the objects defined in RFC 3413 [RFC3413] 871 specifically, those described in section 6. 873 If this object is set to true(1), then it enables 874 the generation of OSPFv3 notifications. If it is 875 set to false(2), these notifications are not 876 generated. 878 This object is persistent and when written the 879 entity SHOULD save the change to non-volatile 880 storage." 881 ::= { ospfv3GeneralGroup 21 } 883 ospfv3StubRouterSupport OBJECT-TYPE 884 SYNTAX TruthValue 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "The router's support for stub router functionality. An 889 object value of true(1) indicates that stub router 890 functionality is supported." 891 REFERENCE 892 "OSPF Stub Router Advertisement" 893 ::= { ospfv3GeneralGroup 22 } 895 ospfv3StubRouterAdvertisement OBJECT-TYPE 896 SYNTAX INTEGER { 897 doNotAdvertise (1), 898 advertise(2) 899 } 900 MAX-ACCESS read-write 901 STATUS current 902 DESCRIPTION 903 "This object controls the advertisement of 904 stub LSAs by the router. The value 905 doNotAdvertise(1) will result in the advertisement 906 of standard LSAs and is the default value. 908 This object is persistent and when written 909 the entity SHOULD save the change to non-volatile 910 storage." 911 REFERENCE 912 "OSPF Stub Router Advertisement, Section 2. Proposed 913 Solution" 914 DEFVAL { doNotAdvertise } 915 ::= { ospfv3GeneralGroup 23 } 917 ospfv3DiscontinuityTime OBJECT-TYPE 918 SYNTAX TimeStamp 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "The value of sysUpTime on the most recent occasion 923 at which any one of this MIB's counters suffered 924 a discontinuity. 926 If no such discontinuities have occurred since the last 927 reinitialization of the local management subsystem, 928 then this object contains a zero value." 929 ::= { ospfv3GeneralGroup 24 } 931 ospfv3RestartTime OBJECT-TYPE 932 SYNTAX TimeStamp 933 MAX-ACCESS read-only 934 STATUS current 935 DESCRIPTION 936 "The value of sysUpTime on the most recent occasion 937 at which the ospfv3RestartExitReason was updated." 938 ::= { ospfv3GeneralGroup 25 } 940 -- The OSPFv3 Area Data Structure contains information 941 -- regarding the various areas. The interfaces and 942 -- virtual links are configured as part of these areas. 943 -- Area 0, by definition, is the Backbone Area 945 ospfv3AreaTable OBJECT-TYPE 946 SYNTAX SEQUENCE OF Ospfv3AreaEntry 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 "Information describing the configured 951 parameters and cumulative statistics of the router's 952 attached areas. The interfaces and 953 virtual links are configured as part of these areas. 954 Area 0, by definition, is the Backbone Area." 955 REFERENCE 956 "OSPF Version 2, Section 6, The Area Data 957 Structure" 958 ::= { ospfv3Objects 2 } 960 ospfv3AreaEntry OBJECT-TYPE 961 SYNTAX Ospfv3AreaEntry 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "Information describing the configured 966 parameters and cumulative statistics of one of the 967 router's attached areas. 969 The information in this table is persistent 970 and when written the entity SHOULD save the 971 change to non-volatile storage." 972 INDEX { ospfv3AreaId } 973 ::= { ospfv3AreaTable 1 } 975 Ospfv3AreaEntry ::= SEQUENCE { 976 ospfv3AreaId 977 Ospfv3AreaIdTC, 978 ospfv3AreaImportAsExtern 979 INTEGER, 980 ospfv3AreaSpfRuns 981 Counter32, 982 ospfv3AreaBdrRtrCount 983 Gauge32, 984 ospfv3AreaAsBdrRtrCount 985 Gauge32, 986 ospfv3AreaScopeLsaCount 987 Gauge32, 988 ospfv3AreaScopeLsaCksumSum 989 Unsigned32, 990 ospfv3AreaSummary 991 INTEGER, 992 ospfv3AreaRowStatus 993 RowStatus, 994 ospfv3AreaStubMetric 995 BigMetric, 996 ospfv3AreaNssaTranslatorRole 997 INTEGER, 998 ospfv3AreaNssaTranslatorState 999 INTEGER, 1000 ospfv3AreaNssaTranslatorStabInterval 1001 Unsigned32, 1003 ospfv3AreaNssaTranslatorEvents 1004 Counter32, 1005 ospfv3AreaStubMetricType 1006 INTEGER, 1007 ospfv3AreaTEEnabled 1008 TruthValue 1009 } 1011 ospfv3AreaId OBJECT-TYPE 1012 SYNTAX Ospfv3AreaIdTC 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "A 32-bit unsigned integer uniquely identifying an area. 1017 Area ID 0 is used for the OSPFv3 backbone." 1018 REFERENCE 1019 "OSPF Version 2, Appendix C.2 Area parameters" 1020 ::= { ospfv3AreaEntry 1 } 1022 ospfv3AreaImportAsExtern OBJECT-TYPE 1023 SYNTAX INTEGER { 1024 importExternal(1), -- normal area 1025 importNoExternal(2), -- stub area 1026 importNssa(3) -- not-so-stubby-area 1027 } 1028 MAX-ACCESS read-create 1029 STATUS current 1030 DESCRIPTION 1031 "Indicates whether an area is a Stub area, NSSA, or 1032 standard area. AS-scope LSAs are not imported into Stub 1033 Areas or NSSAs. NSSAs import AS-External data as NSSA 1034 LSAs which have Area-scope." 1035 REFERENCE 1036 "OSPF Version 2, Appendix C.2 Area parameters" 1037 DEFVAL { importExternal } 1038 ::= { ospfv3AreaEntry 2 } 1040 ospfv3AreaSpfRuns OBJECT-TYPE 1041 SYNTAX Counter32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "The number of times that the intra-area route 1046 table has been calculated using this area's 1047 link state database. This is typically done 1048 using Dijkstra's algorithm. 1050 Discontinuities in the value of this counter 1051 can occur at re-initialization of the management 1052 system and at other times as indicated by the 1053 value of ospfv3DiscontinuityTime." 1054 ::= { ospfv3AreaEntry 3 } 1056 ospfv3AreaBdrRtrCount OBJECT-TYPE 1057 SYNTAX Gauge32 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "The total number of area border routers 1062 reachable within this area. This is initially zero, 1063 and is calculated in each Shortest Path First(SPF) 1064 pass." 1065 DEFVAL { 0 } 1066 ::= { ospfv3AreaEntry 4 } 1068 ospfv3AreaAsBdrRtrCount OBJECT-TYPE 1069 SYNTAX Gauge32 1070 MAX-ACCESS read-only 1071 STATUS current 1072 DESCRIPTION 1073 "The total number of Autonomous System border 1074 routers reachable within this area. This is 1075 initially zero, and is calculated in each SPF 1076 pass." 1077 DEFVAL { 0 } 1078 ::= { ospfv3AreaEntry 5 } 1080 ospfv3AreaScopeLsaCount OBJECT-TYPE 1081 SYNTAX Gauge32 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "The total number of Area-Scope link state 1086 advertisements in this area's link state 1087 database." 1088 DEFVAL { 0 } 1089 ::= { ospfv3AreaEntry 6 } 1091 ospfv3AreaScopeLsaCksumSum OBJECT-TYPE 1092 SYNTAX Unsigned32 1093 MAX-ACCESS read-only 1094 STATUS current 1095 DESCRIPTION 1096 "The 32-bit unsigned sum of the Area-Scope link state 1097 advertisements' LS checksums contained in this 1098 area's link state database. The sum can be used 1099 to determine if there has been a change in a 1100 router's link state database or to compare the 1101 link-state database of two routers." 1102 ::= { ospfv3AreaEntry 7 } 1104 ospfv3AreaSummary OBJECT-TYPE 1105 SYNTAX INTEGER { 1106 noAreaSummary(1), 1107 sendAreaSummary(2) 1108 } 1110 MAX-ACCESS read-create 1111 STATUS current 1112 DESCRIPTION 1113 "The variable ospfv3AreaSummary controls the 1114 import of Inter-Area LSAs into stub and 1115 NSSA areas. It has no effect on other areas. 1117 If it is noAreaSummary, the router will neither 1118 originate nor propagate Inter-Area LSAs into the 1119 stub or NSSA area. It will only advertise a 1120 default route. 1122 If it is sendAreaSummary, the router will both 1123 summarize and propagate Inter-Area LSAs." 1124 DEFVAL { sendAreaSummary } 1125 ::= { ospfv3AreaEntry 8 } 1127 ospfv3AreaRowStatus OBJECT-TYPE 1128 SYNTAX RowStatus 1129 MAX-ACCESS read-create 1130 STATUS current 1131 DESCRIPTION 1132 "This object permits management of the table by 1133 facilitating actions such as row creation, 1134 construction and destruction. 1136 The value of this object has no effect on 1137 whether other objects in this conceptual row can be 1138 modified." 1139 ::= { ospfv3AreaEntry 9 } 1141 ospfv3AreaStubMetric OBJECT-TYPE 1142 SYNTAX BigMetric 1143 MAX-ACCESS read-create 1144 STATUS current 1145 DESCRIPTION 1146 "The metric value advertised for the default route 1147 into Stub and NSSA areas. By default, this equals the 1148 least metric among the interfaces to other areas." 1149 ::= { ospfv3AreaEntry 10 } 1151 ospfv3AreaNssaTranslatorRole OBJECT-TYPE 1152 SYNTAX INTEGER { always(1), candidate(2) } 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "Indicates an NSSA Border router's policy for 1157 perform NSSA translation of NSSA-LSAs into 1158 AS-External-LSAs." 1159 DEFVAL { candidate } 1160 ::= { ospfv3AreaEntry 11 } 1162 ospfv3AreaNssaTranslatorState OBJECT-TYPE 1163 SYNTAX INTEGER { 1164 enabled(1), 1165 elected(2), 1166 disabled(3) 1167 } 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "Indicates if and how an NSSA Border router is 1172 performing NSSA translation of NSSA-LSAs into 1173 AS-External-LSAs. When this object is set to enabled, 1174 the NSSA Border router's ospfv3AreaNssaTranslatorRole 1175 has been set to always. When this object is set to 1176 elected, a candidate NSSA Border router is translating 1177 NSSA-LSAs into AS-External-LSAs. When this object is 1178 set to disabled, a candidate NSSA Border router is NOT 1179 translating NSSA-LSAs into AS-External-LSAs." 1180 ::= { ospfv3AreaEntry 12 } 1182 ospfv3AreaNssaTranslatorStabInterval OBJECT-TYPE 1183 SYNTAX Unsigned32 1184 UNITS "seconds" 1185 MAX-ACCESS read-create 1186 STATUS current 1187 DESCRIPTION 1188 "The stability interval defined as the number of 1189 seconds after an elected translator determines its 1190 services are no longer required that it should 1191 continue to perform its translation duties." 1192 DEFVAL { 40 } 1193 ::= { ospfv3AreaEntry 13 } 1195 ospfv3AreaNssaTranslatorEvents OBJECT-TYPE 1196 SYNTAX Counter32 1197 MAX-ACCESS read-only 1198 STATUS current 1199 DESCRIPTION 1200 "Indicates the number of Translator State changes 1201 that have occurred since the last start-up of the 1202 OSPFv3 routing process. 1204 Discontinuities in the value of this counter 1205 can occur at re-initialization of the management 1206 system and at other times as indicated by the 1207 value of ospfv3DiscontinuityTime." 1208 ::= { ospfv3AreaEntry 14 } 1210 ospfv3AreaStubMetricType OBJECT-TYPE 1211 SYNTAX INTEGER { 1212 ospfv3Metric (1), -- OSPF Metric 1213 comparableCost (2), -- external type 1 1214 nonComparable (3) -- external type 2 1215 } 1217 MAX-ACCESS read-create 1218 STATUS current 1219 DESCRIPTION 1220 "This variable assigns the type of metric 1221 advertised as a default route." 1222 DEFVAL { ospfv3Metric } 1223 ::= { ospfv3AreaEntry 15 } 1225 ospfv3AreaTEEnabled OBJECT-TYPE 1226 SYNTAX TruthValue 1227 MAX-ACCESS read-create 1228 STATUS current 1229 DESCRIPTION 1230 "Indicates whether or not traffic engineering 1231 is enabled in the area. The object is set 1232 to the value true(1) to enable traffic engineering. 1233 Traffic engineering is disabled by default." 1234 DEFVAL { false } 1235 ::= { ospfv3AreaEntry 16 } 1237 -- OSPFv3 AS-Scope Link State Database 1239 ospfv3AsLsdbTable OBJECT-TYPE 1240 SYNTAX SEQUENCE OF Ospfv3AsLsdbEntry 1241 MAX-ACCESS not-accessible 1242 STATUS current 1243 DESCRIPTION 1244 "The OSPFv3 Process's AS-Scope Link State Database 1245 (LSDB). The LSDB contains the AS-Scope Link State 1246 Advertisements from throughout the areas that the 1247 device is attached to." 1248 ::= { ospfv3Objects 3 } 1250 ospfv3AsLsdbEntry OBJECT-TYPE 1251 SYNTAX Ospfv3AsLsdbEntry 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "A single AS-Scope Link State Advertisement." 1256 INDEX { ospfv3AsLsdbType, 1257 ospfv3AsLsdbRouterId, 1258 ospfv3AsLsdbLsid } 1259 ::= { ospfv3AsLsdbTable 1 } 1261 Ospfv3AsLsdbEntry ::= SEQUENCE { 1262 ospfv3AsLsdbType 1263 Unsigned32, 1264 ospfv3AsLsdbRouterId 1265 Ospfv3RouterIdTC, 1266 ospfv3AsLsdbLsid 1267 Ospfv3LsIdTC, 1269 ospfv3AsLsdbSequence 1270 Ospfv3LsaSequenceTC, 1271 ospfv3AsLsdbAge 1272 Ospfv3LsaAgeTC, 1273 ospfv3AsLsdbChecksum 1274 Integer32, 1275 ospfv3AsLsdbAdvertisement 1276 OCTET STRING, 1277 ospfv3AsLsdbTypeKnown 1278 TruthValue 1279 } 1281 ospfv3AsLsdbType OBJECT-TYPE 1282 SYNTAX Unsigned32(0..'FFFFFFFF'h) 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "The type of the link state advertisement. 1287 Each link state type has a separate 1288 advertisement format. AS-Scope LSAs not recognized 1289 by the router may be stored in the database." 1290 ::= { ospfv3AsLsdbEntry 1 } 1292 ospfv3AsLsdbRouterId OBJECT-TYPE 1293 SYNTAX Ospfv3RouterIdTC 1294 MAX-ACCESS not-accessible 1295 STATUS current 1296 DESCRIPTION 1297 "The 32 bit number that uniquely identifies the 1298 originating router in the Autonomous System." 1299 REFERENCE 1300 "OSPF Version 2, Appendix C.1 Global parameters" 1301 ::= { ospfv3AsLsdbEntry 2 } 1303 ospfv3AsLsdbLsid OBJECT-TYPE 1304 SYNTAX Ospfv3LsIdTC 1305 MAX-ACCESS not-accessible 1306 STATUS current 1307 DESCRIPTION 1308 "The Link State ID is an LS Type Specific field 1309 containing a unique identifier; 1310 it identifies the piece of the routing domain 1311 that is being described by the advertisement. 1312 In contrast to OSPFv2, the LSID has no 1313 addressing semantics." 1314 ::= { ospfv3AsLsdbEntry 3 } 1316 -- Note that the OSPF Sequence Number is a 32 bit signed 1317 -- integer. It starts with the value '80000001'h, 1318 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1319 -- Thus, a typical sequence number will be very negative. 1321 ospfv3AsLsdbSequence OBJECT-TYPE 1322 SYNTAX Ospfv3LsaSequenceTC 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "The sequence number field is a signed 32-bit 1327 integer. It is used to detect old and duplicate 1328 link state advertisements. The space of 1329 sequence numbers is linearly ordered. The 1330 larger the sequence number the more recent the 1331 advertisement." 1332 REFERENCE 1333 "OSPF Version 2, Section 12.1.6 LS sequence 1334 number" 1335 ::= { ospfv3AsLsdbEntry 4 } 1337 ospfv3AsLsdbAge OBJECT-TYPE 1338 SYNTAX Ospfv3LsaAgeTC 1339 UNITS "seconds" 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "This field is the age of the link state 1344 advertisement in seconds. The high order bit 1345 of the LS age field is considered the DoNotAge 1346 bit for support of on-demand circuits." 1347 REFERENCE 1348 "OSPF Version 2, Section 12.1.1, LS age and 1349 Extending OSPF to Support Demand Circuits, 1350 Section 2.2, The LS age field." 1351 ::= { ospfv3AsLsdbEntry 5 } 1353 ospfv3AsLsdbChecksum OBJECT-TYPE 1354 SYNTAX Integer32 1355 MAX-ACCESS read-only 1356 STATUS current 1357 DESCRIPTION 1358 "This field is the checksum of the complete 1359 contents of the advertisement, excepting the 1360 age field. The age field is excepted so that 1361 an advertisement's age can be incremented 1362 without updating the checksum. The checksum 1363 used is the same that is used for ISO 1364 connectionless datagrams; it is commonly 1365 referred to as the Fletcher checksum." 1366 REFERENCE 1367 "OSPF Version 2, Section 12.1.7 LS checksum" 1368 ::= { ospfv3AsLsdbEntry 6 } 1370 ospfv3AsLsdbAdvertisement OBJECT-TYPE 1371 SYNTAX OCTET STRING (SIZE (1..65535)) 1372 MAX-ACCESS read-only 1373 STATUS current 1374 DESCRIPTION 1375 "The entire Link State Advertisement, including 1376 its header." 1377 ::= { ospfv3AsLsdbEntry 7 } 1379 ospfv3AsLsdbTypeKnown OBJECT-TYPE 1380 SYNTAX TruthValue 1381 MAX-ACCESS read-only 1382 STATUS current 1383 DESCRIPTION 1384 "The value true(1) indicates that the LSA type 1385 is recognized by this Router." 1386 ::= { ospfv3AsLsdbEntry 8 } 1388 -- OSPFv3 Area-Scope Link State Database 1390 ospfv3AreaLsdbTable OBJECT-TYPE 1391 SYNTAX SEQUENCE OF Ospfv3AreaLsdbEntry 1392 MAX-ACCESS not-accessible 1393 STATUS current 1394 DESCRIPTION 1395 "The OSPFv3 Process's Area-Scope LSDB. 1396 The LSDB contains the Area-Scope Link State 1397 Advertisements from throughout the area that the 1398 device is attached to." 1399 ::= { ospfv3Objects 4 } 1401 ospfv3AreaLsdbEntry OBJECT-TYPE 1402 SYNTAX Ospfv3AreaLsdbEntry 1403 MAX-ACCESS not-accessible 1404 STATUS current 1405 DESCRIPTION 1406 "A single Area-Scope Link State Advertisement." 1407 INDEX { ospfv3AreaLsdbAreaId, 1408 ospfv3AreaLsdbType, 1409 ospfv3AreaLsdbRouterId, 1410 ospfv3AreaLsdbLsid } 1411 ::= { ospfv3AreaLsdbTable 1 } 1413 Ospfv3AreaLsdbEntry ::= SEQUENCE { 1414 ospfv3AreaLsdbAreaId 1415 Ospfv3AreaIdTC, 1416 ospfv3AreaLsdbType 1417 Unsigned32, 1418 ospfv3AreaLsdbRouterId 1419 Ospfv3RouterIdTC, 1420 ospfv3AreaLsdbLsid 1421 Ospfv3LsIdTC, 1422 ospfv3AreaLsdbSequence 1423 Ospfv3LsaSequenceTC, 1424 ospfv3AreaLsdbAge 1425 Ospfv3LsaAgeTC, 1427 ospfv3AreaLsdbChecksum 1428 Integer32, 1429 ospfv3AreaLsdbAdvertisement 1430 OCTET STRING, 1431 ospfv3AreaLsdbTypeKnown 1432 TruthValue 1433 } 1435 ospfv3AreaLsdbAreaId OBJECT-TYPE 1436 SYNTAX Ospfv3AreaIdTC 1437 MAX-ACCESS not-accessible 1438 STATUS current 1439 DESCRIPTION 1440 "The 32-bit identifier of the Area from which the 1441 LSA was received." 1442 REFERENCE 1443 "OSPF Version 2, Appendix C.2 Area parameters" 1444 ::= { ospfv3AreaLsdbEntry 1 } 1446 ospfv3AreaLsdbType OBJECT-TYPE 1447 SYNTAX Unsigned32(0..'FFFFFFFF'h) 1448 MAX-ACCESS not-accessible 1449 STATUS current 1450 DESCRIPTION 1451 "The type of the link state advertisement. 1452 Each link state type has a separate 1453 advertisement format. Area-Scope LSAs unrecognized 1454 by the router are also stored in this database." 1455 ::= { ospfv3AreaLsdbEntry 2 } 1457 ospfv3AreaLsdbRouterId OBJECT-TYPE 1458 SYNTAX Ospfv3RouterIdTC 1459 MAX-ACCESS not-accessible 1460 STATUS current 1461 DESCRIPTION 1462 "The 32-bit number that uniquely identifies the 1463 originating router in the Autonomous System." 1464 REFERENCE 1465 "OSPF Version 2, Appendix C.1 Global parameters" 1466 ::= { ospfv3AreaLsdbEntry 3 } 1468 ospfv3AreaLsdbLsid OBJECT-TYPE 1469 SYNTAX Ospfv3LsIdTC 1470 MAX-ACCESS not-accessible 1471 STATUS current 1472 DESCRIPTION 1473 "The Link State ID is an LS Type Specific field 1474 containing a unique identifier; 1475 it identifies the piece of the routing domain 1476 that is being described by the advertisement. 1477 In contrast to OSPFv2, the LSID has no 1478 addressing semantics." 1479 ::= { ospfv3AreaLsdbEntry 4 } 1481 -- Note that the OSPF Sequence Number is a 32 bit signed 1482 -- integer. It starts with the value '80000001'h, 1483 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1484 -- Thus, a typical sequence number will be very negative. 1486 ospfv3AreaLsdbSequence OBJECT-TYPE 1487 SYNTAX Ospfv3LsaSequenceTC 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The sequence number field is a signed 32-bit 1492 integer. It is used to detect old and 1493 duplicate link state advertisements. The space 1494 of sequence numbers is linearly ordered. The 1495 larger the sequence number the more recent the 1496 advertisement." 1497 REFERENCE 1498 "OSPF Version 2, Section 12.1.6 LS sequence 1499 number" 1500 ::= { ospfv3AreaLsdbEntry 5 } 1502 ospfv3AreaLsdbAge OBJECT-TYPE 1503 SYNTAX Ospfv3LsaAgeTC 1504 UNITS "seconds" 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "This field is the age of the link state 1509 advertisement in seconds. The high order bit 1510 of the LS age field is considered the DoNotAge 1511 bit for support of on-demand circuits." 1512 REFERENCE 1513 "OSPF Version 2, Section 12.1.1, LS age and 1514 Extending OSPF to Support Demand Circuits, 1515 Section 2.2, The LS age field." 1516 ::= { ospfv3AreaLsdbEntry 6 } 1518 ospfv3AreaLsdbChecksum OBJECT-TYPE 1519 SYNTAX Integer32 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "This field is the checksum of the complete 1524 contents of the advertisement, excepting the 1525 age field. The age field is excepted so that 1526 an advertisement's age can be incremented 1527 without updating the checksum. The checksum 1528 used is the same that is used for ISO 1529 connectionless datagrams; it is commonly 1530 referred to as the Fletcher checksum." 1531 REFERENCE 1532 "OSPF Version 2, Section 12.1.7 LS checksum" 1534 ::= { ospfv3AreaLsdbEntry 7 } 1536 ospfv3AreaLsdbAdvertisement OBJECT-TYPE 1537 SYNTAX OCTET STRING (SIZE (1..65535)) 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "The entire Link State Advertisement, including 1542 its header." 1543 ::= { ospfv3AreaLsdbEntry 8 } 1545 ospfv3AreaLsdbTypeKnown OBJECT-TYPE 1546 SYNTAX TruthValue 1547 MAX-ACCESS read-only 1548 STATUS current 1549 DESCRIPTION 1550 "The value true(1) indicates that the LSA type is 1551 recognized by this Router." 1552 ::= { ospfv3AreaLsdbEntry 9 } 1554 -- OSPFv3 Link-Scope Link State Database, for non-virtual interfaces 1556 ospfv3LinkLsdbTable OBJECT-TYPE 1557 SYNTAX SEQUENCE OF Ospfv3LinkLsdbEntry 1558 MAX-ACCESS not-accessible 1559 STATUS current 1560 DESCRIPTION 1561 "The OSPFv3 Process's Link-Scope LSDB for non-virtual 1562 interfaces. The LSDB contains the Link-Scope Link 1563 State Advertisements from the interfaces that the 1564 device is attached to." 1565 ::= { ospfv3Objects 5 } 1567 ospfv3LinkLsdbEntry OBJECT-TYPE 1568 SYNTAX Ospfv3LinkLsdbEntry 1569 MAX-ACCESS not-accessible 1570 STATUS current 1571 DESCRIPTION 1572 "A single Link-Scope Link State Advertisement." 1573 INDEX { ospfv3LinkLsdbIfIndex, 1574 ospfv3LinkLsdbIfInstId, 1575 ospfv3LinkLsdbType, 1576 ospfv3LinkLsdbRouterId, 1577 ospfv3LinkLsdbLsid } 1578 ::= { ospfv3LinkLsdbTable 1 } 1580 Ospfv3LinkLsdbEntry ::= SEQUENCE { 1581 ospfv3LinkLsdbIfIndex 1582 InterfaceIndex, 1583 ospfv3LinkLsdbIfInstId 1584 Ospfv3IfInstIdTC, 1586 ospfv3LinkLsdbType 1587 Unsigned32, 1588 ospfv3LinkLsdbRouterId 1589 Ospfv3RouterIdTC, 1590 ospfv3LinkLsdbLsid 1591 Ospfv3LsIdTC, 1592 ospfv3LinkLsdbSequence 1593 Ospfv3LsaSequenceTC, 1594 ospfv3LinkLsdbAge 1595 Ospfv3LsaAgeTC, 1596 ospfv3LinkLsdbChecksum 1597 Integer32, 1598 ospfv3LinkLsdbAdvertisement 1599 OCTET STRING, 1600 ospfv3LinkLsdbTypeKnown 1601 TruthValue 1602 } 1604 ospfv3LinkLsdbIfIndex OBJECT-TYPE 1605 SYNTAX InterfaceIndex 1606 MAX-ACCESS not-accessible 1607 STATUS current 1608 DESCRIPTION 1609 "The identifier of the link from which the LSA 1610 was received." 1611 ::= { ospfv3LinkLsdbEntry 1 } 1613 ospfv3LinkLsdbIfInstId OBJECT-TYPE 1614 SYNTAX Ospfv3IfInstIdTC 1615 MAX-ACCESS not-accessible 1616 STATUS current 1617 DESCRIPTION 1618 "The identifier of the interface instance from 1619 which the LSA was received." 1620 ::= { ospfv3LinkLsdbEntry 2 } 1622 ospfv3LinkLsdbType OBJECT-TYPE 1623 SYNTAX Unsigned32(0..'FFFFFFFF'h) 1624 MAX-ACCESS not-accessible 1625 STATUS current 1626 DESCRIPTION 1627 "The type of the link state advertisement. 1628 Each link state type has a separate 1629 advertisement format. Link-Scope LSAs unrecognized 1630 by the router are also stored in this database." 1631 ::= { ospfv3LinkLsdbEntry 3 } 1633 ospfv3LinkLsdbRouterId OBJECT-TYPE 1634 SYNTAX Ospfv3RouterIdTC 1635 MAX-ACCESS not-accessible 1636 STATUS current 1637 DESCRIPTION 1638 "The 32 bit number that uniquely identifies the 1639 originating router in the Autonomous System." 1640 REFERENCE 1641 "OSPF Version 2, Appendix C.1 Global parameters" 1642 ::= { ospfv3LinkLsdbEntry 4 } 1644 ospfv3LinkLsdbLsid OBJECT-TYPE 1645 SYNTAX Ospfv3LsIdTC 1646 MAX-ACCESS not-accessible 1647 STATUS current 1648 DESCRIPTION 1649 "The Link State ID is an LS Type Specific field 1650 containing a unique identifier; 1651 it identifies the piece of the routing domain 1652 that is being described by the advertisement. 1653 In contrast to OSPFv2, the LSID has no 1654 addressing semantics. However, in OSPFv3 1655 the Link State ID always contains the flooding 1656 scope of the LSA." 1657 ::= { ospfv3LinkLsdbEntry 5 } 1659 -- Note that the OSPF Sequence Number is a 32 bit signed 1660 -- integer. It starts with the value '80000001'h, 1661 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1662 -- Thus, a typical sequence number will be very negative. 1664 ospfv3LinkLsdbSequence OBJECT-TYPE 1665 SYNTAX Ospfv3LsaSequenceTC 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "The sequence number field is a signed 32-bit 1670 integer. It is used to detect old and duplicate 1671 link state advertisements. The space of 1672 sequence numbers is linearly ordered. The 1673 larger the sequence number the more recent the 1674 advertisement." 1675 REFERENCE 1676 "OSPF Version 2, Section 12.1.6 LS sequence 1677 number" 1678 ::= { ospfv3LinkLsdbEntry 6 } 1680 ospfv3LinkLsdbAge OBJECT-TYPE 1681 SYNTAX Ospfv3LsaAgeTC 1682 UNITS "seconds" 1683 MAX-ACCESS read-only 1684 STATUS current 1685 DESCRIPTION 1686 "This field is the age of the link state 1687 advertisement in seconds. The high order bit 1688 of the LS age field is considered the DoNotAge 1689 bit for support of on-demand circuits." 1690 REFERENCE 1691 "OSPF Version 2, Section 12.1.1, LS age and 1692 Extending OSPF to Support Demand Circuits, 1693 Section 2.2, The LS age field." 1694 ::= { ospfv3LinkLsdbEntry 7 } 1696 ospfv3LinkLsdbChecksum OBJECT-TYPE 1697 SYNTAX Integer32 1698 MAX-ACCESS read-only 1699 STATUS current 1700 DESCRIPTION 1701 "This field is the checksum of the complete 1702 contents of the advertisement, excepting the 1703 age field. The age field is excepted so that 1704 an advertisement's age can be incremented 1705 without updating the checksum. The checksum 1706 used is the same that is used for ISO 1707 connectionless datagrams; it is commonly 1708 referred to as the Fletcher checksum." 1709 REFERENCE 1710 "OSPF Version 2, Section 12.1.7 LS checksum" 1711 ::= { ospfv3LinkLsdbEntry 8 } 1713 ospfv3LinkLsdbAdvertisement OBJECT-TYPE 1714 SYNTAX OCTET STRING (SIZE (1..65535)) 1715 MAX-ACCESS read-only 1716 STATUS current 1717 DESCRIPTION 1718 "The entire Link State Advertisement, including 1719 its header." 1720 ::= { ospfv3LinkLsdbEntry 9 } 1722 ospfv3LinkLsdbTypeKnown OBJECT-TYPE 1723 SYNTAX TruthValue 1724 MAX-ACCESS read-only 1725 STATUS current 1726 DESCRIPTION 1727 "The value true(1) indicates that the LSA type is 1728 recognized by this Router." 1729 ::= { ospfv3LinkLsdbEntry 10 } 1731 -- OSPF Host Table 1733 ospfv3HostTable OBJECT-TYPE 1734 SYNTAX SEQUENCE OF Ospfv3HostEntry 1735 MAX-ACCESS not-accessible 1736 STATUS current 1737 DESCRIPTION 1738 "The Host/Metric Table indicates what hosts are 1739 directly attached to the router and their 1740 corresponding metrics." 1741 REFERENCE 1742 "OSPF Version 2, Appendix C.6 Host route 1743 parameters" 1745 ::= { ospfv3Objects 6 } 1747 ospfv3HostEntry OBJECT-TYPE 1748 SYNTAX Ospfv3HostEntry 1749 MAX-ACCESS not-accessible 1750 STATUS current 1751 DESCRIPTION 1752 "A metric to be advertised when a given host is 1753 reachable. 1755 The information in this table is persistent and 1756 when written the entity SHOULD save the change 1757 to non-volatile storage." 1758 INDEX { ospfv3HostAddressType, 1759 ospfv3HostAddress } 1760 ::= { ospfv3HostTable 1 } 1762 Ospfv3HostEntry ::= SEQUENCE { 1763 ospfv3HostAddressType 1764 InetAddressType, 1765 ospfv3HostAddress 1766 InetAddress, 1767 ospfv3HostMetric 1768 Metric, 1769 ospfv3HostRowStatus 1770 RowStatus, 1771 ospfv3HostAreaID 1772 Ospfv3AreaIdTC 1773 } 1775 ospfv3HostAddressType OBJECT-TYPE 1776 SYNTAX InetAddressType 1777 MAX-ACCESS not-accessible 1778 STATUS current 1779 DESCRIPTION 1780 "The address type of ospfv3HostAddress. Only IPv6 1781 global address type expected." 1782 REFERENCE 1783 "OSPF Version 2, Appendix C.6 Host route 1784 parameters" 1785 ::= { ospfv3HostEntry 1 } 1787 ospfv3HostAddress OBJECT-TYPE 1788 SYNTAX InetAddress 1789 MAX-ACCESS not-accessible 1790 STATUS current 1791 DESCRIPTION 1792 "The IPv6 Address of the Host. Must be an 1793 IPv6 global address." 1794 REFERENCE 1795 "OSPF Version 2, Appendix C.6 Host route 1796 parameters" 1798 ::= { ospfv3HostEntry 2 } 1800 ospfv3HostMetric OBJECT-TYPE 1801 SYNTAX Metric 1802 MAX-ACCESS read-create 1803 STATUS current 1804 DESCRIPTION 1805 "The Metric to be advertised." 1806 REFERENCE 1807 "OSPF Version 2, Appendix C.6 Host route 1808 parameters" 1809 ::= { ospfv3HostEntry 3 } 1811 ospfv3HostRowStatus OBJECT-TYPE 1812 SYNTAX RowStatus 1813 MAX-ACCESS read-create 1814 STATUS current 1815 DESCRIPTION 1816 "This object permits management of the table by 1817 facilitating actions such as row creation, 1818 construction and destruction. 1820 The value of this object has no effect on 1821 whether other objects in this conceptual row can be 1822 modified." 1823 ::= { ospfv3HostEntry 4 } 1825 ospfv3HostAreaID OBJECT-TYPE 1826 SYNTAX Ospfv3AreaIdTC 1827 MAX-ACCESS read-create 1828 STATUS current 1829 DESCRIPTION 1830 "The Area the Host Entry is to be found within. 1831 By default, the area for the subsuming OSPFv3 1832 interface or Area 0 if there is no subsuming 1833 interface." 1834 REFERENCE 1835 "OSPF Version 2, Appendix C.2 Area parameters" 1836 ::= { ospfv3HostEntry 5 } 1838 -- OSPFv3 Interface Table 1840 ospfv3IfTable OBJECT-TYPE 1841 SYNTAX SEQUENCE OF Ospfv3IfEntry 1842 MAX-ACCESS not-accessible 1843 STATUS current 1844 DESCRIPTION 1845 "The OSPFv3 Interface Table describes the 1846 interfaces from the viewpoint of OSPFv3." 1847 REFERENCE 1848 "OSPF for IPv6, Appendix C.3 Router interface 1849 parameters" 1851 ::= { ospfv3Objects 7 } 1853 ospfv3IfEntry OBJECT-TYPE 1854 SYNTAX Ospfv3IfEntry 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "The OSPFv3 Interface Entry describes one 1859 interface from the viewpoint of OSPFv3. 1861 The information in this table is persistent 1862 and when written the entity SHOULD save the 1863 change to non-volatile storage." 1864 INDEX { ospfv3IfIndex, 1865 ospfv3IfInstId } 1866 ::= { ospfv3IfTable 1 } 1868 Ospfv3IfEntry ::= SEQUENCE { 1869 ospfv3IfIndex 1870 InterfaceIndex, 1871 ospfv3IfInstId 1872 Ospfv3IfInstIdTC, 1873 ospfv3IfAreaId 1874 Ospfv3AreaIdTC, 1875 ospfv3IfType 1876 INTEGER, 1877 ospfv3IfAdminStatus 1878 Status, 1879 ospfv3IfRtrPriority 1880 DesignatedRouterPriority, 1881 ospfv3IfTransitDelay 1882 Ospfv3UpToRefreshIntervalTC, 1883 ospfv3IfRetransInterval 1884 Ospfv3UpToRefreshIntervalTC, 1885 ospfv3IfHelloInterval 1886 HelloRange, 1887 ospfv3IfRtrDeadInterval 1888 Ospfv3DeadIntervalRangeTC, 1889 ospfv3IfPollInterval 1890 Unsigned32, 1891 ospfv3IfState 1892 INTEGER, 1893 ospfv3IfDesignatedRouter 1894 Ospfv3RouterIdTC, 1895 ospfv3IfBackupDesignatedRouter 1896 Ospfv3RouterIdTC, 1897 ospfv3IfEvents 1898 Counter32, 1899 ospfv3IfRowStatus 1900 RowStatus, 1901 ospfv3IfDemand 1902 TruthValue, 1904 ospfv3IfMetricValue 1905 Metric, 1906 ospfv3IfLinkScopeLsaCount 1907 Gauge32, 1908 ospfv3IfLinkLsaCksumSum 1909 Unsigned32, 1910 ospfv3IfDemandNbrProbe 1911 TruthValue, 1912 ospfv3IfDemandNbrProbeRetransLimit 1913 Unsigned32, 1914 ospfv3IfDemandNbrProbeInterval 1915 Unsigned32, 1916 ospfv3IfTEDisabled 1917 TruthValue, 1918 ospfv3IfLinkLSASuppression 1919 TruthValue 1920 } 1922 ospfv3IfIndex OBJECT-TYPE 1923 SYNTAX InterfaceIndex 1924 MAX-ACCESS not-accessible 1925 STATUS current 1926 DESCRIPTION 1927 "The interface index of this OSPFv3 interface. 1928 It corresponds to the interface index of the 1929 IPv6 interface on which OSPFv3 is configured." 1930 ::= { ospfv3IfEntry 1 } 1932 ospfv3IfInstId OBJECT-TYPE 1933 SYNTAX Ospfv3IfInstIdTC 1934 MAX-ACCESS not-accessible 1935 STATUS current 1936 DESCRIPTION 1937 "Enables multiple interface instances of OSPFv3 1938 to be run over a single link. Each interface 1939 instance would be assigned a separate ID. This ID 1940 has local link significance only." 1941 ::= { ospfv3IfEntry 2 } 1943 ospfv3IfAreaId OBJECT-TYPE 1944 SYNTAX Ospfv3AreaIdTC 1945 MAX-ACCESS read-create 1946 STATUS current 1947 DESCRIPTION 1948 "A 32-bit integer uniquely identifying the area 1949 to which the interface connects. Area ID 1950 0 is used for the OSPFv3 backbone." 1951 DEFVAL { 0 } 1952 ::= { ospfv3IfEntry 3 } 1954 ospfv3IfType OBJECT-TYPE 1955 SYNTAX INTEGER { 1956 broadcast(1), 1957 nbma(2), 1958 pointToPoint(3), 1959 pointToMultipoint(5) 1960 } 1961 MAX-ACCESS read-create 1962 STATUS current 1963 DESCRIPTION 1964 "The OSPFv3 interface type." 1965 ::= { ospfv3IfEntry 4 } 1967 ospfv3IfAdminStatus OBJECT-TYPE 1968 SYNTAX Status 1969 MAX-ACCESS read-create 1970 STATUS current 1971 DESCRIPTION 1972 "The OSPFv3 interface's administrative status. 1973 The value formed on the interface, and the 1974 interface will be advertised as an internal route 1975 to some area. The value 'disabled' denotes 1976 that the interface is external to OSPFv3. 1978 Note that a value of 'disabled' for the object 1979 ospfv3AdminStatus will override a value of 1980 'enabled' for the interface." 1981 DEFVAL { enabled } 1982 ::= { ospfv3IfEntry 5 } 1984 ospfv3IfRtrPriority OBJECT-TYPE 1985 SYNTAX DesignatedRouterPriority 1986 MAX-ACCESS read-create 1987 STATUS current 1988 DESCRIPTION 1989 "The priority of this interface. Used in 1990 multi-access networks, this field is used in 1991 the designated router election algorithm. The 1992 value 0 signifies that the router is not 1993 eligible to become the designated router on this 1994 particular network. In the event of a tie in 1995 this value, routers will use their Router ID as 1996 a tie breaker." 1997 DEFVAL { 1 } 1998 ::= { ospfv3IfEntry 6 } 2000 ospfv3IfTransitDelay OBJECT-TYPE 2001 SYNTAX Ospfv3UpToRefreshIntervalTC 2002 UNITS "seconds" 2003 MAX-ACCESS read-create 2004 STATUS current 2005 DESCRIPTION 2006 "The estimated number of seconds it takes to transmit 2007 a Link State Update packet over this interface. LSAs 2008 contained in the update packet must have their age 2009 incremented by this amount before transmission. This 2010 value should take into account the transmission and 2011 propagation delays of the interface." 2012 REFERENCE 2013 "OSPF for IPv6, Appendix C.3 Router interface 2014 parameters." 2015 DEFVAL { 1 } 2016 ::= { ospfv3IfEntry 7 } 2018 ospfv3IfRetransInterval OBJECT-TYPE 2019 SYNTAX Ospfv3UpToRefreshIntervalTC 2020 UNITS "seconds" 2021 MAX-ACCESS read-create 2022 STATUS current 2023 DESCRIPTION 2024 "The number of seconds between link state 2025 advertisement retransmissions for adjacencies 2026 belonging to this interface. This value is 2027 also used when retransmitting database 2028 description and link state request packets." 2029 DEFVAL { 5 } 2030 ::= { ospfv3IfEntry 8 } 2032 ospfv3IfHelloInterval OBJECT-TYPE 2033 SYNTAX HelloRange 2034 UNITS "seconds" 2035 MAX-ACCESS read-create 2036 STATUS current 2037 DESCRIPTION 2038 "The length of time, in seconds, between the 2039 Hello packets that the router sends on the 2040 interface. This value must be the same for all 2041 routers attached to a common network." 2042 DEFVAL { 10 } 2043 ::= { ospfv3IfEntry 9 } 2045 ospfv3IfRtrDeadInterval OBJECT-TYPE 2046 SYNTAX Ospfv3DeadIntervalRangeTC 2047 UNITS "seconds" 2048 MAX-ACCESS read-create 2049 STATUS current 2050 DESCRIPTION 2051 "The number of seconds that a router's Hello 2052 packets have not been seen before its 2053 neighbors declare the router down on the interface. 2054 This should be some multiple of the Hello interval. 2055 This value must be the same for all routers attached 2056 to a common network." 2057 DEFVAL { 40 } 2058 ::= { ospfv3IfEntry 10 } 2060 ospfv3IfPollInterval OBJECT-TYPE 2061 SYNTAX Unsigned32 2062 UNITS "seconds" 2063 MAX-ACCESS read-create 2064 STATUS current 2065 DESCRIPTION 2066 "The larger time interval, in seconds, between 2067 the Hello packets sent to an inactive, 2068 non-broadcast, multi-access neighbor." 2069 DEFVAL { 120 } 2070 ::= { ospfv3IfEntry 11 } 2072 ospfv3IfState OBJECT-TYPE 2073 SYNTAX INTEGER { 2074 down(1), 2075 loopback(2), 2076 waiting(3), 2077 pointToPoint(4), 2078 designatedRouter(5), 2079 backupDesignatedRouter(6), 2080 otherDesignatedRouter(7), 2081 standby(8) 2082 } 2083 MAX-ACCESS read-only 2084 STATUS current 2085 DESCRIPTION 2086 "The OSPFv3 Interface State. An interface may be 2087 in standby state if there are multiple interfaces 2088 on the link and another interface is active. The 2089 interface may be in down state if the underlying 2090 IPv6 interface is down or if the admin status is 2091 'disabled' either globally or for the interface." 2092 ::= { ospfv3IfEntry 12 } 2094 ospfv3IfDesignatedRouter OBJECT-TYPE 2095 SYNTAX Ospfv3RouterIdTC 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 "The Router ID of the Designated Router." 2100 ::= { ospfv3IfEntry 13 } 2102 ospfv3IfBackupDesignatedRouter OBJECT-TYPE 2103 SYNTAX Ospfv3RouterIdTC 2104 MAX-ACCESS read-only 2105 STATUS current 2106 DESCRIPTION 2107 "The Router ID of the Backup Designated 2108 Router." 2109 ::= { ospfv3IfEntry 14 } 2111 ospfv3IfEvents OBJECT-TYPE 2112 SYNTAX Counter32 2113 MAX-ACCESS read-only 2114 STATUS current 2115 DESCRIPTION 2116 "The number of times this OSPFv3 interface has 2117 changed its state or an error has occurred. 2119 Discontinuities in the value of this counter 2120 can occur at re-initialization of the management 2121 system and at other times as indicated by the 2122 value of ospfv3DiscontinuityTime." 2123 ::= { ospfv3IfEntry 15 } 2125 ospfv3IfRowStatus OBJECT-TYPE 2126 SYNTAX RowStatus 2127 MAX-ACCESS read-create 2128 STATUS current 2129 DESCRIPTION 2130 "This object permits management of the table by 2131 facilitating actions such as row creation, 2132 construction and destruction. 2134 The value of this object has no effect on 2135 whether other objects in this conceptual row can be 2136 modified." 2137 ::= { ospfv3IfEntry 16 } 2139 ospfv3IfDemand OBJECT-TYPE 2140 SYNTAX TruthValue 2141 MAX-ACCESS read-create 2142 STATUS current 2143 DESCRIPTION 2144 "Indicates whether Demand OSPFv3 procedures 2145 (hello suppression to FULL neighbors and 2146 setting the DoNotAge flag on propagated LSAs) 2147 should be performed on this interface." 2148 DEFVAL { false } 2149 ::= { ospfv3IfEntry 17 } 2151 ospfv3IfMetricValue OBJECT-TYPE 2152 SYNTAX Metric 2153 MAX-ACCESS read-create 2154 STATUS current 2155 DESCRIPTION 2156 "The metric assigned to this interface. 2157 The default value of the Metric is 2158 Reference Bandwidth / ifSpeed. The value 2159 of the reference bandwidth can be set 2160 in the ospfv3ReferenceBandwidth object." 2161 ::= { ospfv3IfEntry 18 } 2163 ospfv3IfLinkScopeLsaCount OBJECT-TYPE 2164 SYNTAX Gauge32 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "The total number of Link-Scope link state 2169 advertisements in this link's link state 2170 database." 2171 ::= { ospfv3IfEntry 19 } 2173 ospfv3IfLinkLsaCksumSum OBJECT-TYPE 2174 SYNTAX Unsigned32 2175 MAX-ACCESS read-only 2176 STATUS current 2177 DESCRIPTION 2178 "The 32-bit unsigned sum of the Link-Scope link state 2179 advertisements' LS checksums contained in this 2180 link's link state database. The sum can be used 2181 to determine if there has been a change in a 2182 router's link state database or to compare the 2183 link state database of two routers." 2184 ::= { ospfv3IfEntry 20 } 2186 ospfv3IfDemandNbrProbe OBJECT-TYPE 2187 SYNTAX TruthValue 2188 MAX-ACCESS read-create 2189 STATUS current 2190 DESCRIPTION 2191 "Indicates whether or not neighbor probing is 2192 enabled to determine whether or not the neighbor 2193 is inactive. Neighbor probing is disabled by 2194 default." 2195 DEFVAL { false } 2196 ::= { ospfv3IfEntry 21 } 2198 ospfv3IfDemandNbrProbeRetransLimit OBJECT-TYPE 2199 SYNTAX Unsigned32 2200 MAX-ACCESS read-create 2201 STATUS current 2202 DESCRIPTION 2203 "The number of consecutive LSA retransmissions before 2204 the neighbor is deemed inactive and the neighbor 2205 adjacency is brought down." 2206 DEFVAL { 10 } 2207 ::= { ospfv3IfEntry 22} 2209 ospfv3IfDemandNbrProbeInterval OBJECT-TYPE 2210 SYNTAX Unsigned32 2211 UNITS "seconds" 2212 MAX-ACCESS read-create 2213 STATUS current 2214 DESCRIPTION 2215 "Defines how often the neighbor will be probed." 2216 DEFVAL { 120 } 2217 ::= { ospfv3IfEntry 23 } 2219 ospfv3IfTEDisabled OBJECT-TYPE 2220 SYNTAX TruthValue 2221 MAX-ACCESS read-create 2222 STATUS current 2223 DESCRIPTION 2224 "Indicates whether or not traffic engineering 2225 is disabled on the interface when traffic 2226 engineering is enabled in the area where the 2227 interface is attached. The object is set 2228 to the value true(1) to disable traffic engineering 2229 on the interface. Traffic engineering is enabled 2230 by default on the interface when traffic engineering 2231 is enabled in the area where the interface is 2232 attached." 2233 DEFVAL { false } 2234 ::= { ospfv3IfEntry 24 } 2236 ospfv3IfLinkLSASuppression OBJECT-TYPE 2237 SYNTAX TruthValue 2238 MAX-ACCESS read-create 2239 STATUS current 2240 DESCRIPTION 2241 "Specifies whether or not Link LSA origination needs 2242 to be suppressed for non-Broadcast or NBMA. The object 2243 is set to value true (1) to suppress the origination." 2244 REFERENCE 2245 "OSPF Version 3, Appendix C.3." 2246 DEFVAL { false } 2247 ::= { ospfv3IfEntry 25 } 2249 -- OSPFv3 Virtual Interface Table 2251 ospfv3VirtIfTable OBJECT-TYPE 2252 SYNTAX SEQUENCE OF Ospfv3VirtIfEntry 2253 MAX-ACCESS not-accessible 2254 STATUS current 2255 DESCRIPTION 2256 "Information about this router's virtual 2257 interfaces that the OSPFv3 Process is configured 2258 to carry on." 2259 REFERENCE 2260 "OSPF Version 3, Appendix C.4 Virtual link 2261 parameters" 2262 ::= { ospfv3Objects 8 } 2264 ospfv3VirtIfEntry OBJECT-TYPE 2265 SYNTAX Ospfv3VirtIfEntry 2266 MAX-ACCESS not-accessible 2267 STATUS current 2268 DESCRIPTION 2269 "Information about a single Virtual Interface. 2271 The information in this table is persistent 2272 and when written the entity SHOULD save the 2273 change to non-volatile storage." 2274 INDEX { ospfv3VirtIfAreaId, 2275 ospfv3VirtIfNeighbor } 2276 ::= { ospfv3VirtIfTable 1 } 2278 Ospfv3VirtIfEntry ::= SEQUENCE { 2279 ospfv3VirtIfAreaId 2280 Ospfv3AreaIdTC, 2281 ospfv3VirtIfNeighbor 2282 Ospfv3RouterIdTC, 2283 ospfv3VirtIfIndex 2284 InterfaceIndex, 2285 ospfv3VirtIfInstId 2286 Ospfv3IfInstIdTC, 2287 ospfv3VirtIfTransitDelay 2288 Ospfv3UpToRefreshIntervalTC, 2289 ospfv3VirtIfRetransInterval 2290 Ospfv3UpToRefreshIntervalTC, 2291 ospfv3VirtIfHelloInterval 2292 HelloRange, 2293 ospfv3VirtIfRtrDeadInterval 2294 Ospfv3DeadIntervalRangeTC, 2295 ospfv3VirtIfState 2296 INTEGER, 2297 ospfv3VirtIfEvents 2298 Counter32, 2299 ospfv3VirtIfRowStatus 2300 RowStatus, 2301 ospfv3VirtIfLinkScopeLsaCount 2302 Gauge32, 2303 ospfv3VirtIfLinkLsaCksumSum 2304 Unsigned32 2305 } 2307 ospfv3VirtIfAreaId OBJECT-TYPE 2308 SYNTAX Ospfv3AreaIdTC 2309 MAX-ACCESS not-accessible 2310 STATUS current 2311 DESCRIPTION 2312 "The Transit Area that the Virtual Link 2313 traverses. By definition, this is not 2314 Area 0." 2315 ::= { ospfv3VirtIfEntry 1 } 2317 ospfv3VirtIfNeighbor OBJECT-TYPE 2318 SYNTAX Ospfv3RouterIdTC 2319 MAX-ACCESS not-accessible 2320 STATUS current 2321 DESCRIPTION 2322 "The Router ID of the Virtual Neighbor." 2323 ::= { ospfv3VirtIfEntry 2 } 2325 ospfv3VirtIfIndex OBJECT-TYPE 2326 SYNTAX InterfaceIndex 2327 MAX-ACCESS read-only 2328 STATUS current 2329 DESCRIPTION 2330 "The local interface index assigned by the 2331 OSPFv3 process to this OSPFv3 virtual interface. 2332 It is advertised in Hello's sent over the virtual 2333 link and in the router's router-LSAs." 2334 ::= { ospfv3VirtIfEntry 3 } 2336 ospfv3VirtIfInstId OBJECT-TYPE 2337 SYNTAX Ospfv3IfInstIdTC 2338 MAX-ACCESS read-only 2339 STATUS current 2340 DESCRIPTION 2341 "The local interface instance ID assigned by the 2342 OSPFv3 process to this OSPFv3 virtual interface." 2343 ::= { ospfv3VirtIfEntry 4 } 2345 ospfv3VirtIfTransitDelay OBJECT-TYPE 2346 SYNTAX Ospfv3UpToRefreshIntervalTC 2347 UNITS "seconds" 2348 MAX-ACCESS read-create 2349 STATUS current 2350 DESCRIPTION 2351 "The estimated number of seconds it takes to 2352 transmit a link state update packet over this 2353 interface." 2354 DEFVAL { 1 } 2355 ::= { ospfv3VirtIfEntry 5 } 2357 ospfv3VirtIfRetransInterval OBJECT-TYPE 2358 SYNTAX Ospfv3UpToRefreshIntervalTC 2359 UNITS "seconds" 2360 MAX-ACCESS read-create 2361 STATUS current 2362 DESCRIPTION 2363 "The number of seconds between link state 2364 advertisement retransmissions for adjacencies 2365 belonging to this interface. This value is 2366 also used when retransmitting database 2367 description and link state request packets. This 2368 value should be well over the expected 2369 round-trip time." 2370 DEFVAL { 5 } 2371 ::= { ospfv3VirtIfEntry 6 } 2373 ospfv3VirtIfHelloInterval OBJECT-TYPE 2374 SYNTAX HelloRange 2375 UNITS "seconds" 2376 MAX-ACCESS read-create 2377 STATUS current 2378 DESCRIPTION 2379 "The length of time, in seconds, between the 2380 Hello packets that the router sends on the 2381 interface. This value must be the same for the 2382 virtual neighbor." 2383 DEFVAL { 10 } 2384 ::= { ospfv3VirtIfEntry 7 } 2386 ospfv3VirtIfRtrDeadInterval OBJECT-TYPE 2387 SYNTAX Ospfv3DeadIntervalRangeTC 2388 UNITS "seconds" 2389 MAX-ACCESS read-create 2390 STATUS current 2391 DESCRIPTION 2392 "The number of seconds that a router's Hello 2393 packets have not been seen before its 2394 neighbors declare the router down. This should 2395 be some multiple of the Hello interval. This 2396 value must be the same for the virtual 2397 neighbor." 2398 DEFVAL { 60 } 2399 ::= { ospfv3VirtIfEntry 8 } 2401 ospfv3VirtIfState OBJECT-TYPE 2402 SYNTAX INTEGER { 2403 down(1), 2404 pointToPoint(4) 2405 } 2406 MAX-ACCESS read-only 2407 STATUS current 2408 DESCRIPTION 2409 "OSPF virtual interface states. The same encoding 2410 as the ospfV3IfTable is used." 2411 ::= { ospfv3VirtIfEntry 9 } 2413 ospfv3VirtIfEvents OBJECT-TYPE 2414 SYNTAX Counter32 2415 MAX-ACCESS read-only 2416 STATUS current 2417 DESCRIPTION 2418 "The number of state changes or error events on 2419 this Virtual Link. 2421 Discontinuities in the value of this counter 2422 can occur at re-initialization of the management 2423 system and at other times as indicated by the 2424 value of ospfv3DiscontinuityTime." 2425 ::= { ospfv3VirtIfEntry 10 } 2427 ospfv3VirtIfRowStatus OBJECT-TYPE 2428 SYNTAX RowStatus 2429 MAX-ACCESS read-create 2430 STATUS current 2431 DESCRIPTION 2432 "This object permits management of the table by 2433 facilitating actions such as row creation, 2434 construction and destruction. 2436 The value of this object has no effect on 2437 whether other objects in this conceptual row can be 2438 modified." 2439 ::= { ospfv3VirtIfEntry 11 } 2441 ospfv3VirtIfLinkScopeLsaCount OBJECT-TYPE 2442 SYNTAX Gauge32 2443 MAX-ACCESS read-only 2444 STATUS current 2445 DESCRIPTION 2446 "The total number of Link-Scope link state 2447 advertisements in this virtual link's link state 2448 database." 2449 ::= { ospfv3VirtIfEntry 12 } 2451 ospfv3VirtIfLinkLsaCksumSum OBJECT-TYPE 2452 SYNTAX Unsigned32 2453 MAX-ACCESS read-only 2454 STATUS current 2455 DESCRIPTION 2456 "The 32-bit unsigned sum of the Link-Scope link-state 2457 advertisements' LS checksums contained in this 2458 virtual link's link-state database. The sum can be used 2459 to determine if there has been a change in a 2460 router's link state database or to compare the 2461 link state database of two routers." 2462 ::= { ospfv3VirtIfEntry 13 } 2464 -- OSPFv3 Neighbor Table 2466 ospfv3NbrTable OBJECT-TYPE 2467 SYNTAX SEQUENCE OF Ospfv3NbrEntry 2468 MAX-ACCESS not-accessible 2469 STATUS current 2470 DESCRIPTION 2471 "A table describing all neighbors in the 2472 locality of the OSPFv3 router." 2473 REFERENCE 2474 "OSPF Version 2, Section 10 The Neighbor Data 2475 Structure" 2476 ::= { ospfv3Objects 9 } 2478 ospfv3NbrEntry OBJECT-TYPE 2479 SYNTAX Ospfv3NbrEntry 2480 MAX-ACCESS not-accessible 2481 STATUS current 2482 DESCRIPTION 2483 "The information regarding a single neighbor." 2484 REFERENCE 2485 "OSPF Version 2, Section 10 The Neighbor Data 2486 Structure" 2487 INDEX { ospfv3NbrIfIndex, 2488 ospfv3NbrIfInstId, 2489 ospfv3NbrRtrId } 2490 ::= { ospfv3NbrTable 1 } 2492 Ospfv3NbrEntry ::= SEQUENCE { 2493 ospfv3NbrIfIndex 2494 InterfaceIndex, 2495 ospfv3NbrIfInstId 2496 Ospfv3IfInstIdTC, 2497 ospfv3NbrRtrId 2498 Ospfv3RouterIdTC, 2499 ospfv3NbrAddressType 2500 InetAddressType, 2501 ospfv3NbrAddress 2502 InetAddress, 2503 ospfv3NbrOptions 2504 Integer32, 2505 ospfv3NbrPriority 2506 DesignatedRouterPriority, 2507 ospfv3NbrState 2508 INTEGER, 2509 ospfv3NbrEvents 2510 Counter32, 2511 ospfv3NbrLsRetransQLen 2512 Gauge32, 2513 ospfv3NbrHelloSuppressed 2514 TruthValue, 2515 ospfv3NbrIfId 2516 InterfaceIndex, 2517 ospfv3NbrRestartHelperStatus 2518 INTEGER, 2519 ospfv3NbrRestartHelperAge 2520 Ospfv3UpToRefreshIntervalTC, 2521 ospfv3NbrRestartHelperExitReason 2522 INTEGER 2523 } 2525 ospfv3NbrIfIndex OBJECT-TYPE 2526 SYNTAX InterfaceIndex 2527 MAX-ACCESS not-accessible 2528 STATUS current 2529 DESCRIPTION 2530 "The local link ID of the link over which the 2531 neighbor can be reached." 2532 ::= { ospfv3NbrEntry 1 } 2534 ospfv3NbrIfInstId OBJECT-TYPE 2535 SYNTAX Ospfv3IfInstIdTC 2536 MAX-ACCESS not-accessible 2537 STATUS current 2538 DESCRIPTION 2539 "Interface instance over which the neighbor 2540 can be reached. This ID has local link 2541 significance only." 2542 ::= { ospfv3NbrEntry 2 } 2544 ospfv3NbrRtrId OBJECT-TYPE 2545 SYNTAX Ospfv3RouterIdTC 2546 MAX-ACCESS not-accessible 2547 STATUS current 2548 DESCRIPTION 2549 "A 32-bit unsigned integer uniquely identifying the 2550 Neighboring router in the Autonomous System." 2551 ::= { ospfv3NbrEntry 3 } 2553 ospfv3NbrAddressType OBJECT-TYPE 2554 SYNTAX InetAddressType 2555 MAX-ACCESS read-only 2556 STATUS current 2557 DESCRIPTION 2558 "The address type of ospfv3NbrAddress. Only IPv6 2559 addresses without zone index are expected." 2560 ::= { ospfv3NbrEntry 4 } 2562 ospfv3NbrAddress OBJECT-TYPE 2563 SYNTAX InetAddress 2564 MAX-ACCESS read-only 2565 STATUS current 2566 DESCRIPTION 2567 "The IPv6 address of the neighbor associated with 2568 the local link." 2569 ::= { ospfv3NbrEntry 5 } 2571 ospfv3NbrOptions OBJECT-TYPE 2572 SYNTAX Integer32 2573 MAX-ACCESS read-only 2574 STATUS current 2575 DESCRIPTION 2576 "A Bit Mask corresponding to the neighbor's 2577 options field." 2578 REFERENCE 2579 "OSPF Version 3, Appendix A.2 the Options field" 2580 ::= { ospfv3NbrEntry 6 } 2582 ospfv3NbrPriority OBJECT-TYPE 2583 SYNTAX DesignatedRouterPriority 2584 MAX-ACCESS read-only 2585 STATUS current 2586 DESCRIPTION 2587 "The priority of this neighbor in the designated 2588 router election algorithm. The value 0 signifies 2589 that the neighbor is not eligible to become the 2590 designated router on this particular network." 2591 ::= { ospfv3NbrEntry 7 } 2593 ospfv3NbrState OBJECT-TYPE 2594 SYNTAX INTEGER { 2595 down(1), 2596 attempt(2), 2597 init(3), 2598 twoWay(4), 2599 exchangeStart(5), 2600 exchange(6), 2601 loading(7), 2602 full(8) 2603 } 2604 MAX-ACCESS read-only 2605 STATUS current 2606 DESCRIPTION 2607 "The State of the relationship with this 2608 Neighbor." 2609 REFERENCE 2610 "OSPF Version 2, Section 10.1 Neighbor States" 2611 ::= { ospfv3NbrEntry 8 } 2613 ospfv3NbrEvents OBJECT-TYPE 2614 SYNTAX Counter32 2615 MAX-ACCESS read-only 2616 STATUS current 2617 DESCRIPTION 2618 "The number of times this neighbor relationship 2619 has changed state or an error has occurred. 2621 Discontinuities in the value of this counter 2622 can occur at re-initialization of the management 2623 system and at other times as indicated by the 2624 value of ospfv3DiscontinuityTime." 2625 ::= { ospfv3NbrEntry 9 } 2627 ospfv3NbrLsRetransQLen OBJECT-TYPE 2628 SYNTAX Gauge32 2629 MAX-ACCESS read-only 2630 STATUS current 2631 DESCRIPTION 2632 "The current length of the retransmission 2633 queue." 2634 ::= { ospfv3NbrEntry 10 } 2636 ospfv3NbrHelloSuppressed OBJECT-TYPE 2637 SYNTAX TruthValue 2638 MAX-ACCESS read-only 2639 STATUS current 2640 DESCRIPTION 2641 "Indicates whether Hellos are being suppressed 2642 to the neighbor" 2643 ::= { ospfv3NbrEntry 11 } 2645 ospfv3NbrIfId OBJECT-TYPE 2646 SYNTAX InterfaceIndex 2647 MAX-ACCESS read-only 2648 STATUS current 2649 DESCRIPTION 2650 "The interface ID that the neighbor advertises 2651 in its Hello Packets on this link, that is, the 2652 neighbor's local interface index." 2653 ::= { ospfv3NbrEntry 12 } 2655 ospfv3NbrRestartHelperStatus OBJECT-TYPE 2656 SYNTAX INTEGER { notHelping (1), 2657 helping (2) 2658 } 2659 MAX-ACCESS read-only 2660 STATUS current 2661 DESCRIPTION 2662 "Indicates whether the router is acting 2663 as a Graceful restart helper for the neighbor." 2664 ::= { ospfv3NbrEntry 13 } 2666 ospfv3NbrRestartHelperAge OBJECT-TYPE 2667 SYNTAX Ospfv3UpToRefreshIntervalTC 2668 UNITS "seconds" 2669 MAX-ACCESS read-only 2670 STATUS current 2671 DESCRIPTION 2672 "Remaining time in current OSPF Graceful restart 2673 interval, if the router is acting as a restart 2674 helper for the neighbor." 2675 ::= { ospfv3NbrEntry 14 } 2677 ospfv3NbrRestartHelperExitReason OBJECT-TYPE 2678 SYNTAX INTEGER { none (1), 2679 inProgress (2), 2680 completed (3), 2681 timedOut (4), 2682 topologyChanged (5) 2683 } 2684 MAX-ACCESS read-only 2685 STATUS current 2686 DESCRIPTION 2687 "Describes the outcome of the last attempt at acting 2688 as a Graceful restart helper for the neighbor. 2690 none:............no restart has yet been attempted. 2691 inProgress:......a restart attempt is currently underway. 2692 completed:.......the last restart completed successfully. 2693 timedOut:........the last restart timed out. 2694 topologyChanged:.the last restart was aborted due to 2695 a topology change." 2696 ::= { ospfv3NbrEntry 15 } 2698 -- OSPFv3 Configured Neighbor Table 2700 ospfv3CfgNbrTable OBJECT-TYPE 2701 SYNTAX SEQUENCE OF Ospfv3CfgNbrEntry 2702 MAX-ACCESS not-accessible 2703 STATUS current 2704 DESCRIPTION 2705 "A table describing all configured neighbors. 2707 The configured neighbors table just gives 2708 OSPFv3 information for sending OSPFv3 packets 2709 to potential neighbors and is typically used 2710 on nbma and point-to-multipoint networks. 2711 Once a hello is received from a neighbor in 2712 the configured neighbor table, an entry for 2713 that neighbor is created in the neighbor table 2714 and adjacency state is maintained there. 2715 Neighbors on multi-access or point-to-point 2716 networks can use multicast addressing, so only 2717 neighbor table entries are created for them." 2718 REFERENCE 2719 "OSPF Version 2, Section 10 The Neighbor Data 2720 Structure" 2721 ::= { ospfv3Objects 10 } 2723 ospfv3CfgNbrEntry OBJECT-TYPE 2724 SYNTAX Ospfv3CfgNbrEntry 2725 MAX-ACCESS not-accessible 2726 STATUS current 2727 DESCRIPTION 2728 "The information regarding a single configured 2729 neighbor. 2731 The information in this table is persistent 2732 and when written the entity SHOULD save the 2733 change to non-volatile storage." 2734 REFERENCE 2735 "OSPF Version 2, Section 10 The Neighbor Data 2736 Structure" 2737 INDEX { ospfv3CfgNbrIfIndex, 2738 ospfv3CfgNbrIfInstId, 2739 ospfv3CfgNbrAddressType, 2740 ospfv3CfgNbrAddress } 2741 ::= { ospfv3CfgNbrTable 1 } 2743 Ospfv3CfgNbrEntry ::= SEQUENCE { 2744 ospfv3CfgNbrIfIndex 2745 InterfaceIndex, 2746 ospfv3CfgNbrIfInstId 2747 Ospfv3IfInstIdTC, 2748 ospfv3CfgNbrAddressType 2749 InetAddressType, 2750 ospfv3CfgNbrAddress 2751 InetAddress, 2752 ospfv3CfgNbrPriority 2753 DesignatedRouterPriority, 2754 ospfv3CfgNbrRowStatus 2755 RowStatus 2756 } 2758 ospfv3CfgNbrIfIndex OBJECT-TYPE 2759 SYNTAX InterfaceIndex 2760 MAX-ACCESS not-accessible 2761 STATUS current 2762 DESCRIPTION 2763 "The local link ID of the link over which the 2764 neighbor can be reached." 2765 ::= { ospfv3CfgNbrEntry 1 } 2767 ospfv3CfgNbrIfInstId OBJECT-TYPE 2768 SYNTAX Ospfv3IfInstIdTC 2769 MAX-ACCESS not-accessible 2770 STATUS current 2771 DESCRIPTION 2772 "Interface instance over which the neighbor 2773 can be reached. This ID has local link 2774 significance only." 2775 ::= { ospfv3CfgNbrEntry 2 } 2777 ospfv3CfgNbrAddressType OBJECT-TYPE 2778 SYNTAX InetAddressType 2779 MAX-ACCESS not-accessible 2780 STATUS current 2781 DESCRIPTION 2782 "The address type of ospfv3NbrAddress. Only IPv6 2783 addresses without zone index are expected." 2784 ::= { ospfv3CfgNbrEntry 3 } 2786 ospfv3CfgNbrAddress OBJECT-TYPE 2787 SYNTAX InetAddress 2788 MAX-ACCESS not-accessible 2789 STATUS current 2790 DESCRIPTION 2791 "The IPv6 address of the neighbor associated with 2792 the local link." 2793 ::= { ospfv3CfgNbrEntry 4 } 2795 ospfv3CfgNbrPriority OBJECT-TYPE 2796 SYNTAX DesignatedRouterPriority 2797 MAX-ACCESS read-create 2798 STATUS current 2799 DESCRIPTION 2800 "The priority of this neighbor in the designated 2801 router election algorithm. The value 0 signifies 2802 that the neighbor is not eligible to become the 2803 designated router on this particular network." 2804 DEFVAL { 1 } 2805 ::= { ospfv3CfgNbrEntry 5 } 2807 ospfv3CfgNbrRowStatus OBJECT-TYPE 2808 SYNTAX RowStatus 2809 MAX-ACCESS read-create 2810 STATUS current 2811 DESCRIPTION 2812 "This object permits management of the table by 2813 facilitating actions such as row creation, 2814 construction and destruction. 2816 The value of this object has no effect on 2817 whether other objects in this conceptual row can be 2818 modified." 2819 ::= { ospfv3CfgNbrEntry 6 } 2821 -- OSPFv3 Virtual Neighbor Table 2823 ospfv3VirtNbrTable OBJECT-TYPE 2824 SYNTAX SEQUENCE OF Ospfv3VirtNbrEntry 2825 MAX-ACCESS not-accessible 2826 STATUS current 2827 DESCRIPTION 2828 "A table describing all virtual neighbors." 2829 REFERENCE 2830 "OSPF Version 2, Section 15 Virtual Links" 2831 ::= { ospfv3Objects 11 } 2833 ospfv3VirtNbrEntry OBJECT-TYPE 2834 SYNTAX Ospfv3VirtNbrEntry 2835 MAX-ACCESS not-accessible 2836 STATUS current 2837 DESCRIPTION 2838 "Virtual neighbor information." 2839 INDEX { ospfv3VirtNbrArea, 2840 ospfv3VirtNbrRtrId } 2841 ::= { ospfv3VirtNbrTable 1 } 2843 Ospfv3VirtNbrEntry ::= SEQUENCE { 2844 ospfv3VirtNbrArea 2845 Ospfv3AreaIdTC, 2846 ospfv3VirtNbrRtrId 2847 Ospfv3RouterIdTC, 2848 ospfv3VirtNbrIfIndex 2849 InterfaceIndex, 2850 ospfv3VirtNbrIfInstId 2851 Ospfv3IfInstIdTC, 2852 ospfv3VirtNbrAddressType 2853 InetAddressType, 2854 ospfv3VirtNbrAddress 2855 InetAddress, 2856 ospfv3VirtNbrOptions 2857 Integer32, 2858 ospfv3VirtNbrState 2859 INTEGER, 2860 ospfv3VirtNbrEvents 2861 Counter32, 2862 ospfv3VirtNbrLsRetransQLen 2863 Gauge32, 2864 ospfv3VirtNbrHelloSuppressed 2865 TruthValue, 2866 ospfv3VirtNbrIfId 2867 InterfaceIndex, 2868 ospfv3VirtNbrRestartHelperStatus 2869 INTEGER, 2870 ospfv3VirtNbrRestartHelperAge 2871 Ospfv3UpToRefreshIntervalTC, 2872 ospfv3VirtNbrRestartHelperExitReason 2873 INTEGER 2874 } 2876 ospfv3VirtNbrArea OBJECT-TYPE 2877 SYNTAX Ospfv3AreaIdTC 2878 MAX-ACCESS not-accessible 2879 STATUS current 2880 DESCRIPTION 2881 "The Transit Area Identifier." 2882 ::= { ospfv3VirtNbrEntry 1 } 2884 ospfv3VirtNbrRtrId OBJECT-TYPE 2885 SYNTAX Ospfv3RouterIdTC 2886 MAX-ACCESS not-accessible 2887 STATUS current 2888 DESCRIPTION 2889 "A 32-bit integer uniquely identifying the 2890 neighboring router in the Autonomous System." 2891 ::= { ospfv3VirtNbrEntry 2 } 2893 ospfv3VirtNbrIfIndex OBJECT-TYPE 2894 SYNTAX InterfaceIndex 2895 MAX-ACCESS read-only 2896 STATUS current 2897 DESCRIPTION 2898 "The local interface ID for the virtual link over 2899 which the neighbor can be reached." 2900 ::= { ospfv3VirtNbrEntry 3 } 2902 ospfv3VirtNbrIfInstId OBJECT-TYPE 2903 SYNTAX Ospfv3IfInstIdTC 2904 MAX-ACCESS read-only 2905 STATUS current 2906 DESCRIPTION 2907 "The interface instance for the virtual link over 2908 which the neighbor can be reached." 2909 ::= { ospfv3VirtNbrEntry 4 } 2911 ospfv3VirtNbrAddressType OBJECT-TYPE 2912 SYNTAX InetAddressType 2913 MAX-ACCESS read-only 2914 STATUS current 2915 DESCRIPTION 2916 "The address type of ospfv3VirtNbrAddress. Only IPv6 2917 addresses without zone index are expected." 2918 ::= { ospfv3VirtNbrEntry 5 } 2920 ospfv3VirtNbrAddress OBJECT-TYPE 2921 SYNTAX InetAddress 2922 MAX-ACCESS read-only 2923 STATUS current 2924 DESCRIPTION 2925 "The IPv6 address advertised by this Virtual Neighbor. 2926 It must be a Global scope address." 2927 ::= { ospfv3VirtNbrEntry 6 } 2929 ospfv3VirtNbrOptions OBJECT-TYPE 2930 SYNTAX Integer32 2931 MAX-ACCESS read-only 2932 STATUS current 2933 DESCRIPTION 2934 "A Bit Mask corresponding to the neighbor's options 2935 field." 2936 REFERENCE 2937 "OSPF Version 3, Appendix A.2 the Options field" 2938 ::= { ospfv3VirtNbrEntry 7 } 2940 ospfv3VirtNbrState OBJECT-TYPE 2941 SYNTAX INTEGER { 2942 down(1), 2943 attempt(2), 2944 init(3), 2945 twoWay(4), 2946 exchangeStart(5), 2947 exchange(6), 2948 loading(7), 2949 full(8) 2950 } 2951 MAX-ACCESS read-only 2952 STATUS current 2953 DESCRIPTION 2954 "The state of the Virtual Neighbor Relationship." 2955 ::= { ospfv3VirtNbrEntry 8 } 2957 ospfv3VirtNbrEvents OBJECT-TYPE 2958 SYNTAX Counter32 2959 MAX-ACCESS read-only 2960 STATUS current 2961 DESCRIPTION 2962 "The number of times this virtual link has 2963 changed its state or an error has occurred. 2965 Discontinuities in the value of this counter 2966 can occur at re-initialization of the management 2967 system and at other times as indicated by the 2968 value of ospfv3DiscontinuityTime." 2969 ::= { ospfv3VirtNbrEntry 9 } 2971 ospfv3VirtNbrLsRetransQLen OBJECT-TYPE 2972 SYNTAX Gauge32 2973 MAX-ACCESS read-only 2974 STATUS current 2975 DESCRIPTION 2976 "The current length of the retransmission 2977 queue." 2978 ::= { ospfv3VirtNbrEntry 10 } 2980 ospfv3VirtNbrHelloSuppressed OBJECT-TYPE 2981 SYNTAX TruthValue 2982 MAX-ACCESS read-only 2983 STATUS current 2984 DESCRIPTION 2985 "Indicates whether Hellos are being suppressed 2986 to the neighbor" 2987 ::= { ospfv3VirtNbrEntry 11 } 2989 ospfv3VirtNbrIfId OBJECT-TYPE 2990 SYNTAX InterfaceIndex 2991 MAX-ACCESS read-only 2992 STATUS current 2993 DESCRIPTION 2994 "The interface ID that the neighbor advertises 2995 in its Hello Packets on this virtual link, that is, 2996 the neighbor's local interface ID." 2997 ::= { ospfv3VirtNbrEntry 12 } 2999 ospfv3VirtNbrRestartHelperStatus OBJECT-TYPE 3000 SYNTAX INTEGER { notHelping (1), 3001 helping (2) 3002 } 3003 MAX-ACCESS read-only 3004 STATUS current 3005 DESCRIPTION 3006 "Indicates whether the router is acting 3007 as a Graceful restart helper for the neighbor." 3008 ::= { ospfv3VirtNbrEntry 13 } 3010 ospfv3VirtNbrRestartHelperAge OBJECT-TYPE 3011 SYNTAX Ospfv3UpToRefreshIntervalTC 3012 UNITS "seconds" 3013 MAX-ACCESS read-only 3014 STATUS current 3015 DESCRIPTION 3016 "Remaining time in current OSPF Graceful restart 3017 interval, if the router is acting as a restart 3018 helper for the neighbor." 3019 ::= { ospfv3VirtNbrEntry 14 } 3021 ospfv3VirtNbrRestartHelperExitReason OBJECT-TYPE 3022 SYNTAX INTEGER { none (1), 3023 inProgress (2), 3024 completed (3), 3025 timedOut (4), 3026 topologyChanged (5) 3027 } 3028 MAX-ACCESS read-only 3029 STATUS current 3030 DESCRIPTION 3031 "Describes the outcome of the last attempt at acting 3032 as a Graceful restart helper for the neighbor. 3034 none:............no restart has yet been attempted. 3035 inProgress:......a restart attempt is currently underway. 3036 completed:.......the last restart completed successfully. 3037 timedOut:........the last restart timed out. 3038 topologyChanged:.the last restart was aborted due to 3039 a topology change." 3040 ::= { ospfv3VirtNbrEntry 15 } 3042 -- 3043 -- The OSPFv3 Area Aggregate Table 3044 -- 3046 ospfv3AreaAggregateTable OBJECT-TYPE 3047 SYNTAX SEQUENCE OF Ospfv3AreaAggregateEntry 3048 MAX-ACCESS not-accessible 3049 STATUS current 3050 DESCRIPTION 3051 "The Area Aggregate Table acts as an adjunct 3052 to the Area Table. It describes those address 3053 aggregates that are configured to be propagated 3054 from an area. Its purpose is to reduce the amount 3055 of information that is known beyond an Area's 3056 borders. 3058 A range of IPv6 prefixes specified by a 3059 prefix/prefix length pair. Note that if 3060 ranges are configured such that one range 3061 subsumes another range the most specific 3062 match is the preferred one." 3063 ::= { ospfv3Objects 12 } 3065 ospfv3AreaAggregateEntry OBJECT-TYPE 3066 SYNTAX Ospfv3AreaAggregateEntry 3067 MAX-ACCESS not-accessible 3068 STATUS current 3069 DESCRIPTION 3070 "A single area aggregate entry. 3072 Information in this table is persistent and 3073 when this object is written the entity SHOULD 3074 save the change to non-volatile storage." 3075 REFERENCE 3076 "OSPF Version 2, Appendix C.2 Area parameters" 3077 INDEX { ospfv3AreaAggregateAreaID, 3078 ospfv3AreaAggregateAreaLsdbType, 3079 ospfv3AreaAggregatePrefixType, 3080 ospfv3AreaAggregatePrefix, 3081 ospfv3AreaAggregatePrefixLength } 3082 ::= { ospfv3AreaAggregateTable 1 } 3084 Ospfv3AreaAggregateEntry ::= SEQUENCE { 3085 ospfv3AreaAggregateAreaID 3086 Ospfv3AreaIdTC, 3087 ospfv3AreaAggregateAreaLsdbType 3088 INTEGER, 3089 ospfv3AreaAggregatePrefixType 3090 InetAddressType, 3091 ospfv3AreaAggregatePrefix 3092 InetAddress, 3093 ospfv3AreaAggregatePrefixLength 3094 InetAddressPrefixLength, 3095 ospfv3AreaAggregateRowStatus 3096 RowStatus, 3097 ospfv3AreaAggregateEffect 3098 INTEGER, 3099 ospfv3AreaAggregateRouteTag 3100 Unsigned32 3101 } 3103 ospfv3AreaAggregateAreaID OBJECT-TYPE 3104 SYNTAX Ospfv3AreaIdTC 3105 MAX-ACCESS not-accessible 3106 STATUS current 3107 DESCRIPTION 3108 "The Area the Address Aggregate is to be found 3109 within." 3110 REFERENCE 3111 "OSPF Version 2, Appendix C.2 Area parameters" 3112 ::= { ospfv3AreaAggregateEntry 1 } 3114 ospfv3AreaAggregateAreaLsdbType OBJECT-TYPE 3115 SYNTAX INTEGER { 3116 interAreaPrefixLsa(8195), -- 0x2003 3117 nssaExternalLsa(8199) -- 0x2007 3118 } 3119 MAX-ACCESS not-accessible 3120 STATUS current 3121 DESCRIPTION 3122 "The type of the Address Aggregate. This field 3123 specifies the Area Lsdb type that this Address 3124 Aggregate applies to." 3125 REFERENCE 3126 "OSPF Version 2, Appendix A.4.1 The Link State 3127 Advertisement header" 3128 ::= { ospfv3AreaAggregateEntry 2 } 3130 ospfv3AreaAggregatePrefixType OBJECT-TYPE 3131 SYNTAX InetAddressType 3132 MAX-ACCESS not-accessible 3133 STATUS current 3134 DESCRIPTION 3135 "The prefix type of ospfv3AreaAggregatePrefix. Only 3136 IPv6 addresses are expected." 3137 ::= { ospfv3AreaAggregateEntry 3 } 3139 ospfv3AreaAggregatePrefix OBJECT-TYPE 3140 SYNTAX InetAddress (SIZE (0..16)) 3141 MAX-ACCESS not-accessible 3142 STATUS current 3143 DESCRIPTION 3144 "The IPv6 Prefix." 3145 REFERENCE 3146 "OSPF Version 2, Appendix C.2 Area parameters" 3147 ::= { ospfv3AreaAggregateEntry 4 } 3149 ospfv3AreaAggregatePrefixLength OBJECT-TYPE 3150 SYNTAX InetAddressPrefixLength (3..128) 3151 UNITS "bits" 3152 MAX-ACCESS not-accessible 3153 STATUS current 3154 DESCRIPTION 3155 "The length of the prefix (in bits). A prefix can 3156 not be shorter than 3 bits." 3157 REFERENCE 3158 "OSPF Version 2, Appendix C.2 Area parameters" 3159 ::= { ospfv3AreaAggregateEntry 5 } 3161 ospfv3AreaAggregateRowStatus OBJECT-TYPE 3162 SYNTAX RowStatus 3163 MAX-ACCESS read-create 3164 STATUS current 3165 DESCRIPTION 3166 "This object permits management of the table by 3167 facilitating actions such as row creation, 3168 construction and destruction. 3170 The value of this object has no effect on 3171 whether other objects in this conceptual row can be 3172 modified." 3173 ::= { ospfv3AreaAggregateEntry 6 } 3175 ospfv3AreaAggregateEffect OBJECT-TYPE 3176 SYNTAX INTEGER { 3177 advertiseMatching(1), 3178 doNotAdvertiseMatching(2) 3179 } 3180 MAX-ACCESS read-create 3181 STATUS current 3182 DESCRIPTION 3183 "Prefixes subsumed by ranges either trigger the 3184 advertisement of the indicated aggregate 3185 (advertiseMatching) or will result in the prefix not 3186 being advertised at all outside the area." 3187 DEFVAL { advertiseMatching } 3188 ::= { ospfv3AreaAggregateEntry 7 } 3190 ospfv3AreaAggregateRouteTag OBJECT-TYPE 3191 SYNTAX Unsigned32 3192 MAX-ACCESS read-create 3193 STATUS current 3194 DESCRIPTION 3195 "This tag is advertised only in the summarized 3196 As-External LSA when summarizing from NSSA-LSAs to 3197 AS-External-LSAs." 3198 DEFVAL { 0 } 3199 ::= { ospfv3AreaAggregateEntry 8 } 3201 -- OSPFv3 Link-Scope Link State Database, for virtual interfaces 3203 ospfv3VirtLinkLsdbTable OBJECT-TYPE 3204 SYNTAX SEQUENCE OF Ospfv3VirtLinkLsdbEntry 3205 MAX-ACCESS not-accessible 3206 STATUS current 3207 DESCRIPTION 3208 "The OSPFv3 Process's Link-Scope LSDB for virtual 3209 interfaces. The LSDB contains the Link-Scope Link 3210 State Advertisements from virtual interfaces." 3211 ::= { ospfv3Objects 13 } 3213 ospfv3VirtLinkLsdbEntry OBJECT-TYPE 3214 SYNTAX Ospfv3VirtLinkLsdbEntry 3215 MAX-ACCESS not-accessible 3216 STATUS current 3217 DESCRIPTION 3218 "A single Link-Scope Link State Advertisement 3219 for a virtual interface." 3220 INDEX { ospfv3VirtLinkLsdbIfAreaId, 3221 ospfv3VirtLinkLsdbIfNeighbor, 3222 ospfv3VirtLinkLsdbType, 3223 ospfv3VirtLinkLsdbRouterId, 3224 ospfv3VirtLinkLsdbLsid } 3225 ::= { ospfv3VirtLinkLsdbTable 1 } 3227 Ospfv3VirtLinkLsdbEntry ::= SEQUENCE { 3228 ospfv3VirtLinkLsdbIfAreaId 3229 Ospfv3AreaIdTC, 3230 ospfv3VirtLinkLsdbIfNeighbor 3231 Ospfv3RouterIdTC, 3232 ospfv3VirtLinkLsdbType 3233 Unsigned32, 3234 ospfv3VirtLinkLsdbRouterId 3235 Ospfv3RouterIdTC, 3236 ospfv3VirtLinkLsdbLsid 3237 Ospfv3LsIdTC, 3238 ospfv3VirtLinkLsdbSequence 3239 Ospfv3LsaSequenceTC, 3240 ospfv3VirtLinkLsdbAge 3241 Ospfv3LsaAgeTC, 3242 ospfv3VirtLinkLsdbChecksum 3243 Integer32, 3244 ospfv3VirtLinkLsdbAdvertisement 3245 OCTET STRING, 3246 ospfv3VirtLinkLsdbTypeKnown 3247 TruthValue 3248 } 3250 ospfv3VirtLinkLsdbIfAreaId OBJECT-TYPE 3251 SYNTAX Ospfv3AreaIdTC 3252 MAX-ACCESS not-accessible 3253 STATUS current 3254 DESCRIPTION 3255 "The Transit Area that the Virtual Link 3256 traverses. By definition, this is not 3257 Area 0." 3258 ::= { ospfv3VirtLinkLsdbEntry 1 } 3260 ospfv3VirtLinkLsdbIfNeighbor OBJECT-TYPE 3261 SYNTAX Ospfv3RouterIdTC 3262 MAX-ACCESS not-accessible 3263 STATUS current 3264 DESCRIPTION 3265 "The Router ID of the Virtual Neighbor." 3266 ::= { ospfv3VirtLinkLsdbEntry 2 } 3268 ospfv3VirtLinkLsdbType OBJECT-TYPE 3269 SYNTAX Unsigned32(0..'FFFFFFFF'h) 3270 MAX-ACCESS not-accessible 3271 STATUS current 3272 DESCRIPTION 3273 "The type of the link state advertisement. 3274 Each link state type has a separate 3275 advertisement format. Link-Scope LSAs unrecognized 3276 by the router are also stored in this database." 3277 ::= { ospfv3VirtLinkLsdbEntry 3 } 3279 ospfv3VirtLinkLsdbRouterId OBJECT-TYPE 3280 SYNTAX Ospfv3RouterIdTC 3281 MAX-ACCESS not-accessible 3282 STATUS current 3283 DESCRIPTION 3284 "The 32 bit number that uniquely identifies the 3285 originating router in the Autonomous System." 3286 REFERENCE 3287 "OSPF Version 2, Appendix C.1 Global parameters" 3288 ::= { ospfv3VirtLinkLsdbEntry 4 } 3290 ospfv3VirtLinkLsdbLsid OBJECT-TYPE 3291 SYNTAX Ospfv3LsIdTC 3292 MAX-ACCESS not-accessible 3293 STATUS current 3294 DESCRIPTION 3295 "The Link State ID is an LS Type Specific field 3296 containing a unique identifier; 3297 it identifies the piece of the routing domain 3298 that is being described by the advertisement. 3299 In contrast to OSPFv2, the LSID has no 3300 addressing semantics." 3301 ::= { ospfv3VirtLinkLsdbEntry 5 } 3303 -- Note that the OSPF Sequence Number is a 32 bit signed 3304 -- integer. It starts with the value '80000001'h, 3305 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 3306 -- Thus, a typical sequence number will be very negative. 3308 ospfv3VirtLinkLsdbSequence OBJECT-TYPE 3309 SYNTAX Ospfv3LsaSequenceTC 3310 MAX-ACCESS read-only 3311 STATUS current 3312 DESCRIPTION 3313 "The sequence number field is a signed 32-bit 3314 integer. It is used to detect old and duplicate 3315 link state advertisements. The space of 3316 sequence numbers is linearly ordered. The 3317 larger the sequence number the more recent the 3318 advertisement." 3319 REFERENCE 3320 "OSPF Version 2, Section 12.1.6 LS sequence 3321 number" 3322 ::= { ospfv3VirtLinkLsdbEntry 6 } 3324 ospfv3VirtLinkLsdbAge OBJECT-TYPE 3325 SYNTAX Ospfv3LsaAgeTC 3326 UNITS "seconds" 3327 MAX-ACCESS read-only 3328 STATUS current 3329 DESCRIPTION 3330 "This field is the age of the link state 3331 advertisement in seconds. The high order bit 3332 of the LS age field is considered the DoNotAge 3333 bit for support of on-demand circuits." 3334 REFERENCE 3335 "OSPF Version 2, Section 12.1.1, LS age and 3336 Extending OSPF to Support Demand Circuits, 3337 Section 2.2, The LS age field." 3338 ::= { ospfv3VirtLinkLsdbEntry 7 } 3340 ospfv3VirtLinkLsdbChecksum OBJECT-TYPE 3341 SYNTAX Integer32 3342 MAX-ACCESS read-only 3343 STATUS current 3344 DESCRIPTION 3345 "This field is the checksum of the complete 3346 contents of the advertisement, excepting the 3347 age field. The age field is excepted so that 3348 an advertisement's age can be incremented 3349 without updating the checksum. The checksum 3350 used is the same that is used for ISO 3351 connectionless datagrams; it is commonly 3352 referred to as the Fletcher checksum." 3353 REFERENCE 3354 "OSPF Version 2, Section 12.1.7 LS checksum" 3355 ::= { ospfv3VirtLinkLsdbEntry 8 } 3357 ospfv3VirtLinkLsdbAdvertisement OBJECT-TYPE 3358 SYNTAX OCTET STRING (SIZE (1..65535)) 3359 MAX-ACCESS read-only 3360 STATUS current 3361 DESCRIPTION 3362 "The entire Link State Advertisement, including 3363 its header." 3364 ::= { ospfv3VirtLinkLsdbEntry 9 } 3366 ospfv3VirtLinkLsdbTypeKnown OBJECT-TYPE 3367 SYNTAX TruthValue 3368 MAX-ACCESS read-only 3369 STATUS current 3370 DESCRIPTION 3371 "The value true(1) indicates that the LSA type is 3372 recognized by this Router." 3373 ::= { ospfv3VirtLinkLsdbEntry 10 } 3375 -- The Ospfv3 Notification Table 3377 -- The Ospfv3 Notification Table records fields that are 3378 -- required for notifications 3379 ospfv3NotificationEntry OBJECT IDENTIFIER 3380 ::= { ospfv3Objects 14 } 3382 ospfv3ConfigErrorType OBJECT-TYPE 3383 SYNTAX INTEGER { 3384 badVersion (1), 3385 areaMismatch (2), 3386 unknownNbmaNbr (3), -- Router is DR eligible 3387 unknownVirtualNbr (4), 3388 helloIntervalMismatch (5), 3389 deadIntervalMismatch (6), 3390 optionMismatch (7), 3391 mtuMismatch (8), 3392 duplicateRouterId (9), 3393 noError (10) } 3394 MAX-ACCESS accessible-for-notify 3395 STATUS current 3396 DESCRIPTION 3397 "Potential types of configuration conflicts. 3398 Used by the ospfv3ConfigError and 3399 ospfv3ConfigVirtError notifications." 3400 ::= { ospfv3NotificationEntry 1 } 3402 ospfv3PacketType OBJECT-TYPE 3403 SYNTAX INTEGER { 3404 hello (1), 3405 dbDescript (2), 3406 lsReq (3), 3407 lsUpdate (4), 3408 lsAck (5), 3409 nullPacket (6) } 3410 MAX-ACCESS accessible-for-notify 3411 STATUS current 3412 DESCRIPTION 3413 "OSPFv3 packet types." 3414 ::= { ospfv3NotificationEntry 2 } 3416 ospfv3PacketSrc OBJECT-TYPE 3417 SYNTAX InetAddressIPv6 3418 MAX-ACCESS accessible-for-notify 3419 STATUS current 3420 DESCRIPTION 3421 "The IPv6 address of an inbound packet that cannot 3422 be identified by a neighbor instance. 3424 Only IPv6 addresses without zone index are expected." 3425 ::= { ospfv3NotificationEntry 3 } 3427 -- Notification definitions 3429 -- The notifications need to throttled so as to not overwhelm the 3430 -- management agent, in case of rapid changes to the OSPFv3 module. 3432 ospfv3VirtIfStateChange NOTIFICATION-TYPE 3433 OBJECTS { ospfv3RouterId, -- The originator of the notification 3434 ospfv3VirtIfState -- The new state 3435 } 3436 STATUS current 3437 DESCRIPTION 3438 "An ospfv3VirtIfStateChange notification signifies that 3439 there has been a change in the state of an OSPFv3 virtual 3440 interface. 3442 This notification should be generated when the interface 3443 state regresses (e.g., goes from Point-to-Point to Down) 3444 or progresses to a terminal state (i.e., Point-to-Point)." 3445 ::= { ospfv3Notifications 1 } 3447 ospfv3NbrStateChange NOTIFICATION-TYPE 3448 OBJECTS { ospfv3RouterId, -- The originator of the notification 3449 ospfv3NbrState -- The new state 3450 } 3451 STATUS current 3452 DESCRIPTION 3453 "An ospfv3NbrStateChange notification signifies that 3454 there has been a change in the state of a 3455 non-virtual OSPFv3 neighbor. This notification should be 3456 generated when the neighbor state regresses 3457 (e.g., goes from Attempt or Full to 1-Way or 3458 Down) or progresses to a terminal state (e.g., 3459 2-Way or Full). When an neighbor transitions 3460 from or to Full on non-broadcast multi-access 3461 and broadcast networks, the notification should be 3462 generated by the designated router. A designated 3463 router transitioning to Down will be noted by 3464 ospfIfStateChange." 3465 ::= { ospfv3Notifications 2 } 3467 ospfv3VirtNbrStateChange NOTIFICATION-TYPE 3468 OBJECTS { ospfv3RouterId, -- The originator of the notification 3469 ospfv3VirtNbrState -- The new state 3470 } 3471 STATUS current 3472 DESCRIPTION 3473 "An ospfv3VirtNbrStateChange notification signifies 3474 that there has been a change in the state of an OSPFv3 3475 virtual neighbor. This notification should be generated 3476 when the neighbor state regresses (e.g., goes 3477 from Attempt or Full to 1-Way or Down) or 3478 progresses to a terminal state (e.g., Full)." 3479 ::= { ospfv3Notifications 3 } 3481 ospfv3IfConfigError NOTIFICATION-TYPE 3482 OBJECTS { ospfv3RouterId, -- The originator of the notification 3483 ospfv3IfState, -- State of the interface 3484 ospfv3PacketSrc, -- IPv6 address of source 3485 ospfv3ConfigErrorType, -- Type of error 3486 ospfv3PacketType -- Type of packet 3487 } 3488 STATUS current 3489 DESCRIPTION 3490 "An ospfv3IfConfigError notification signifies that a 3491 packet has been received on a non-virtual 3492 interface from a router whose configuration 3493 parameters conflict with this router's 3494 configuration parameters. Note that the event 3495 optionMismatch should cause a notification only if it 3496 prevents an adjacency from forming." 3497 ::= { ospfv3Notifications 4 } 3499 ospfv3VirtIfConfigError NOTIFICATION-TYPE 3500 OBJECTS { ospfv3RouterId, -- The originator of the notification 3501 ospfv3VirtIfState, -- State of the interface 3502 ospfv3ConfigErrorType, -- Type of error 3503 ospfv3PacketType 3504 } 3505 STATUS current 3506 DESCRIPTION 3507 "An ospfv3VirtIfConfigError notification signifies that a 3508 packet has been received on a virtual interface 3509 from a router whose configuration parameters 3510 conflict with this router's configuration 3511 parameters. Note that the event optionMismatch 3512 should cause a notification only if it prevents an 3513 adjacency from forming." 3514 ::= { ospfv3Notifications 5 } 3516 ospfv3IfRxBadPacket NOTIFICATION-TYPE 3517 OBJECTS { ospfv3RouterId, -- The originator of the notification 3518 ospfv3IfState, -- State of the interface 3519 ospfv3PacketSrc, -- The source IPv6 address 3520 ospfv3PacketType -- Type of packet 3521 } 3522 STATUS current 3523 DESCRIPTION 3524 "An ospfv3IfRxBadPacket notification signifies that an 3525 OSPFv3 packet that cannot be parsed has been received on a 3526 non-virtual interface." 3527 ::= { ospfv3Notifications 6 } 3529 ospfv3VirtIfRxBadPacket NOTIFICATION-TYPE 3530 OBJECTS { ospfv3RouterId, -- The originator of the notification 3531 ospfv3VirtIfState, -- State of the interface 3532 ospfv3PacketType -- Type of packet 3533 } 3534 STATUS current 3535 DESCRIPTION 3536 "An ospfv3VirtIfRxBadPacket notification signifies 3537 that an OSPFv3 packet that cannot be parsed has been 3538 received on a virtual interface." 3539 ::= { ospfv3Notifications 7 } 3541 ospfv3LsdbOverflow NOTIFICATION-TYPE 3542 OBJECTS { ospfv3RouterId, -- The originator of the notification 3543 ospfv3ExtAreaLsdbLimit -- Limit on External LSAs 3544 } 3545 STATUS current 3546 DESCRIPTION 3547 "An ospfv3LsdbOverflow notification signifies that the 3548 number of LSAs in the router's link-state 3549 database has exceeded ospfv3ExtAreaLsdbLimit." 3550 ::= { ospfv3Notifications 8 } 3552 ospfv3LsdbApproachingOverflow NOTIFICATION-TYPE 3553 OBJECTS { ospfv3RouterId, -- The originator of the notification 3554 ospfv3ExtAreaLsdbLimit 3555 } 3556 STATUS current 3557 DESCRIPTION 3558 "An ospfv3LsdbApproachingOverflow notification signifies 3559 that the number of LSAs in the router's 3560 link-state database has exceeded ninety percent of 3561 ospfv3ExtAreaLsdbLimit." 3562 ::= { ospfv3Notifications 9 } 3564 ospfv3IfStateChange NOTIFICATION-TYPE 3565 OBJECTS { ospfv3RouterId, -- The originator of the notification 3566 ospfv3IfState -- The new state 3567 } 3568 STATUS current 3569 DESCRIPTION 3570 "An ospfv3IfStateChange notification signifies that there 3571 has been a change in the state of a non-virtual 3572 OSPFv3 interface. This notification should be generated 3573 when the interface state regresses (e.g., goes 3574 from DR to Down) or progresses to a terminal 3575 state (i.e., Point-to-Point, DR Other, DR, or 3576 Backup)." 3577 ::= { ospfv3Notifications 10 } 3579 ospfv3NssaTranslatorStatusChange NOTIFICATION-TYPE 3580 OBJECTS { ospfv3RouterId, -- The originator of the notification 3581 ospfv3AreaNssaTranslatorState -- new state 3582 } 3583 STATUS current 3584 DESCRIPTION 3585 "An ospfv3NssaTranslatorStatusChange notification 3586 indicates that there has been a change in the router's 3587 ability to translate OSPFv3 NSSA LSAs into OSPFv3 External 3588 LSAs. This notification should be generated when the 3589 Translator Status transitions from or to any defined 3590 status on a per area basis." 3591 ::= { ospfv3Notifications 11 } 3593 ospfv3RestartStatusChange NOTIFICATION-TYPE 3594 OBJECTS { ospfv3RouterId, -- The originator of the notification 3595 ospfv3RestartStatus, -- new status 3596 ospfv3RestartInterval, 3597 ospfv3RestartExitReason 3598 } 3599 STATUS current 3600 DESCRIPTION 3601 "An ospfv3RestartStatusChange notification signifies that 3602 there has been a change in the graceful restart 3603 state for the router. This notification should be 3604 generated when the router restart status 3605 changes." 3606 ::= { ospfv3Notifications 12 } 3608 ospfv3NbrRestartHelperStatusChange NOTIFICATION-TYPE 3609 OBJECTS { ospfv3RouterId, -- The originator of the notification 3610 ospfv3NbrRestartHelperStatus, -- new status 3611 ospfv3NbrRestartHelperAge, 3612 ospfv3NbrRestartHelperExitReason 3613 } 3614 STATUS current 3615 DESCRIPTION 3616 "An ospfv3NbrRestartHelperStatusChange notification 3617 signifies that there has been a change in the 3618 graceful restart helper state for the neighbor. 3619 This notification should be generated when the 3620 neighbor restart helper status transitions for a neighbor." 3621 ::= { ospfv3Notifications 13 } 3623 ospfv3VirtNbrRestartHelperStatusChange NOTIFICATION-TYPE 3624 OBJECTS { ospfv3RouterId, -- The originator of the notification 3625 ospfv3VirtNbrRestartHelperStatus, -- new status 3626 ospfv3VirtNbrRestartHelperAge, 3627 ospfv3VirtNbrRestartHelperExitReason 3628 } 3629 STATUS current 3630 DESCRIPTION 3631 "An ospfv3VirtNbrRestartHelperStatusChange 3632 notification signifies that there has been a 3633 change in the graceful restart helper state for 3634 the virtual neighbor. This notification should be 3635 generated when the virtual neighbor restart helper status 3636 transitions for a virtual neighbor." 3637 ::= { ospfv3Notifications 14 } 3639 -- conformance information 3641 ospfv3Groups OBJECT IDENTIFIER ::= { ospfv3Conformance 1 } 3642 ospfv3Compliances OBJECT IDENTIFIER ::= { ospfv3Conformance 2 } 3644 -- compliance statements 3646 ospfv3FullCompliance MODULE-COMPLIANCE 3647 STATUS current 3648 DESCRIPTION "The compliance statement" 3649 MODULE -- this module 3650 MANDATORY-GROUPS { 3651 ospfv3BasicGroup, 3652 ospfv3AreaGroup, 3653 ospfv3IfGroup, 3654 ospfv3VirtIfGroup, 3655 ospfv3NbrGroup, 3656 ospfv3CfgNbrGroup, 3657 ospfv3VirtNbrGroup, 3658 ospfv3AreaAggregateGroup 3659 } 3661 GROUP ospfv3AsLsdbGroup 3662 DESCRIPTION 3663 "This group is required for OSPFv3 systems that 3664 display their AS-scope link state database." 3666 GROUP ospfv3AreaLsdbGroup 3667 DESCRIPTION 3668 "This group is required for OSPFv3 systems that 3669 display their Area-scope link state database." 3671 GROUP ospfv3LinkLsdbGroup 3672 DESCRIPTION 3673 "This group is required for OSPFv3 systems that 3674 display their Link-scope link state database 3675 for non-virtual interfaces." 3677 GROUP ospfv3VirtLinkLsdbGroup 3678 DESCRIPTION 3679 "This group is required for OSPFv3 systems that 3680 display their Link-scope link state database 3681 for virtual interfaces." 3683 GROUP ospfv3HostGroup 3684 DESCRIPTION 3685 "This group is required for OSPFv3 systems that 3686 support attached hosts." 3688 GROUP ospfv3NotificationObjectGroup 3689 DESCRIPTION 3690 "This group is required for OSPFv3 systems that 3691 support OSPFv3 notifications." 3693 GROUP ospfv3NotificationGroup 3694 DESCRIPTION 3695 "This group is required for OSPFv3 systems that 3696 support OSPFv3 notifications." 3698 OBJECT ospfv3NbrAddressType 3699 SYNTAX InetAddressType { ipv6(2) } 3700 DESCRIPTION 3701 "An implementation is only required to support IPv6 3702 address without zone index." 3704 OBJECT ospfv3NbrAddress 3705 SYNTAX InetAddress (SIZE (16)) 3706 DESCRIPTION 3707 "An implementation is only required to support IPv6 3708 address without zone index." 3710 OBJECT ospfv3VirtNbrAddressType 3711 SYNTAX InetAddressType { ipv6(2) } 3712 DESCRIPTION 3713 "An implementation is only required to support IPv6 3714 address without zone index." 3716 OBJECT ospfv3VirtNbrAddress 3717 SYNTAX InetAddress (SIZE (16)) 3718 DESCRIPTION 3719 "An implementation is only required to support IPv6 3720 address without zone index." 3722 ::= { ospfv3Compliances 1 } 3724 ospfv3ReadOnlyCompliance MODULE-COMPLIANCE 3725 STATUS current 3726 DESCRIPTION 3727 "When this MIB is implemented without support for 3728 read-create (i.e., in read-only mode), the 3729 implementation can claim read-only compliance. Such 3730 a device can then be monitored, but cannot be 3731 configured with this MIB." 3733 MODULE -- this module 3734 MANDATORY-GROUPS { 3735 ospfv3BasicGroup, 3736 ospfv3AreaGroup, 3737 ospfv3IfGroup, 3738 ospfv3VirtIfGroup, 3739 ospfv3NbrGroup, 3740 ospfv3CfgNbrGroup, 3741 ospfv3VirtNbrGroup, 3742 ospfv3AreaAggregateGroup 3743 } 3745 GROUP ospfv3AsLsdbGroup 3746 DESCRIPTION 3747 "This group is required for OSPFv3 systems that 3748 display their AS-scope link state database." 3750 GROUP ospfv3AreaLsdbGroup 3751 DESCRIPTION 3752 "This group is required for OSPFv3 systems that 3753 display their Area-scope link state database." 3755 GROUP ospfv3LinkLsdbGroup 3756 DESCRIPTION 3757 "This group is required for OSPFv3 systems that 3758 display their Link-scope link state database 3759 for non-virtual interfaces." 3761 GROUP ospfv3VirtLinkLsdbGroup 3762 DESCRIPTION 3763 "This group is required for OSPFv3 systems that 3764 display their Link-scope link state database 3765 for virtual interfaces." 3767 GROUP ospfv3HostGroup 3768 DESCRIPTION 3769 "This group is required for OSPFv3 systems that 3770 support attached hosts." 3772 GROUP ospfv3NotificationObjectGroup 3773 DESCRIPTION 3774 "This group is required for OSPFv3 systems that 3775 support OSPFv3 notifications." 3777 GROUP ospfv3NotificationGroup 3778 DESCRIPTION 3779 "This group is required for OSPFv3 systems that 3780 support OSPFv3 notifications." 3782 OBJECT ospfv3RouterId 3783 MIN-ACCESS read-only 3784 DESCRIPTION 3785 "Write access is not required." 3787 OBJECT ospfv3AdminStatus 3788 MIN-ACCESS read-only 3789 DESCRIPTION 3790 "Write access is not required." 3792 OBJECT ospfv3ExtAreaLsdbLimit 3793 MIN-ACCESS read-only 3794 DESCRIPTION 3795 "Write access is not required." 3797 OBJECT ospfv3ExitOverflowInterval 3798 MIN-ACCESS read-only 3799 DESCRIPTION 3800 "Write access is not required." 3802 OBJECT ospfv3DemandExtensions 3803 MIN-ACCESS read-only 3804 DESCRIPTION 3805 "Write access is not required." 3807 OBJECT ospfv3ReferenceBandwidth 3808 MIN-ACCESS read-only 3809 DESCRIPTION 3810 "Write access is not required." 3812 OBJECT ospfv3RestartSupport 3813 MIN-ACCESS read-only 3814 DESCRIPTION 3815 "Write access is not required." 3817 OBJECT ospfv3RestartInterval 3818 MIN-ACCESS read-only 3819 DESCRIPTION 3820 "Write access is not required." 3822 OBJECT ospfv3RestartStrictLsaChecking 3823 MIN-ACCESS read-only 3824 DESCRIPTION 3825 "Write access is not required." 3827 OBJECT ospfv3NotificationEnable 3828 MIN-ACCESS read-only 3829 DESCRIPTION 3830 "Write access is not required." 3832 OBJECT ospfv3StubRouterAdvertisement 3833 MIN-ACCESS read-only 3834 DESCRIPTION 3835 "Write access is not required." 3837 OBJECT ospfv3AreaImportAsExtern 3838 MIN-ACCESS read-only 3839 DESCRIPTION 3840 "Write access is not required." 3842 OBJECT ospfv3AreaSummary 3843 MIN-ACCESS read-only 3844 DESCRIPTION 3845 "Write access is not required." 3847 OBJECT ospfv3AreaRowStatus 3848 MIN-ACCESS read-only 3849 DESCRIPTION 3850 "Write access is not required." 3852 OBJECT ospfv3AreaStubMetric 3853 MIN-ACCESS read-only 3854 DESCRIPTION 3855 "Write access is not required." 3857 OBJECT ospfv3AreaNssaTranslatorRole 3858 MIN-ACCESS read-only 3859 DESCRIPTION 3860 "Write access is not required." 3862 OBJECT ospfv3AreaNssaTranslatorStabInterval 3863 MIN-ACCESS read-only 3864 DESCRIPTION 3865 "Write access is not required." 3867 OBJECT ospfv3AreaStubMetricType 3868 MIN-ACCESS read-only 3869 DESCRIPTION 3870 "Write access is not required." 3872 OBJECT ospfv3AreaTEEnabled 3873 MIN-ACCESS read-only 3874 DESCRIPTION 3875 "Write access is not required." 3877 OBJECT ospfv3HostMetric 3878 MIN-ACCESS read-only 3879 DESCRIPTION 3880 "Write access is not required." 3882 OBJECT ospfv3HostRowStatus 3883 MIN-ACCESS read-only 3884 DESCRIPTION 3885 "Write access is not required." 3887 OBJECT ospfv3HostAreaID 3888 MIN-ACCESS read-only 3889 DESCRIPTION 3890 "Write access is not required." 3892 OBJECT ospfv3IfAreaId 3893 MIN-ACCESS read-only 3894 DESCRIPTION 3895 "Write access is not required." 3897 OBJECT ospfv3IfType 3898 MIN-ACCESS read-only 3899 DESCRIPTION 3900 "Write access is not required." 3902 OBJECT ospfv3IfAdminStatus 3903 MIN-ACCESS read-only 3904 DESCRIPTION 3905 "Write access is not required." 3907 OBJECT ospfv3IfRtrPriority 3908 MIN-ACCESS read-only 3909 DESCRIPTION 3910 "Write access is not required." 3912 OBJECT ospfv3IfTransitDelay 3913 MIN-ACCESS read-only 3914 DESCRIPTION 3915 "Write access is not required." 3917 OBJECT ospfv3IfRetransInterval 3918 MIN-ACCESS read-only 3919 DESCRIPTION 3920 "Write access is not required." 3922 OBJECT ospfv3IfHelloInterval 3923 MIN-ACCESS read-only 3924 DESCRIPTION 3925 "Write access is not required." 3927 OBJECT ospfv3IfRtrDeadInterval 3928 MIN-ACCESS read-only 3929 DESCRIPTION 3930 "Write access is not required." 3932 OBJECT ospfv3IfPollInterval 3933 MIN-ACCESS read-only 3934 DESCRIPTION 3935 "Write access is not required." 3937 OBJECT ospfv3IfRowStatus 3938 MIN-ACCESS read-only 3939 DESCRIPTION 3940 "Write access is not required." 3942 OBJECT ospfv3IfDemand 3943 MIN-ACCESS read-only 3944 DESCRIPTION 3945 "Write access is not required." 3947 OBJECT ospfv3IfMetricValue 3948 MIN-ACCESS read-only 3949 DESCRIPTION 3950 "Write access is not required." 3952 OBJECT ospfv3IfDemandNbrProbe 3953 MIN-ACCESS read-only 3954 DESCRIPTION 3955 "Write access is not required." 3957 OBJECT ospfv3IfDemandNbrProbeRetransLimit 3958 MIN-ACCESS read-only 3959 DESCRIPTION 3960 "Write access is not required." 3962 OBJECT ospfv3IfDemandNbrProbeInterval 3963 MIN-ACCESS read-only 3964 DESCRIPTION 3965 "Write access is not required." 3967 OBJECT ospfv3IfTEDisabled 3968 MIN-ACCESS read-only 3969 DESCRIPTION 3970 "Write access is not required." 3972 OBJECT ospfv3IfLinkLSASuppression 3973 MIN-ACCESS read-only 3974 DESCRIPTION 3975 "Write access is not required." 3977 OBJECT ospfv3VirtIfTransitDelay 3978 MIN-ACCESS read-only 3979 DESCRIPTION 3980 "Write access is not required." 3982 OBJECT ospfv3VirtIfRetransInterval 3983 MIN-ACCESS read-only 3984 DESCRIPTION 3985 "Write access is not required." 3987 OBJECT ospfv3VirtIfHelloInterval 3988 MIN-ACCESS read-only 3989 DESCRIPTION 3990 "Write access is not required." 3992 OBJECT ospfv3VirtIfRtrDeadInterval 3993 MIN-ACCESS read-only 3994 DESCRIPTION 3995 "Write access is not required." 3997 OBJECT ospfv3VirtIfRowStatus 3998 MIN-ACCESS read-only 3999 DESCRIPTION 4000 "Write access is not required." 4002 OBJECT ospfv3CfgNbrPriority 4003 MIN-ACCESS read-only 4004 DESCRIPTION 4005 "Write access is not required." 4007 OBJECT ospfv3CfgNbrRowStatus 4008 MIN-ACCESS read-only 4009 DESCRIPTION 4010 "Write access is not required." 4012 OBJECT ospfv3AreaAggregateRowStatus 4013 MIN-ACCESS read-only 4014 DESCRIPTION 4015 "Write access is not required." 4017 OBJECT ospfv3AreaAggregateEffect 4018 MIN-ACCESS read-only 4019 DESCRIPTION 4020 "Write access is not required." 4022 OBJECT ospfv3AreaAggregateRouteTag 4023 MIN-ACCESS read-only 4024 DESCRIPTION 4025 "Write access is not required." 4027 ::= { ospfv3Compliances 2 } 4029 -- units of conformance 4031 ospfv3BasicGroup OBJECT-GROUP 4032 OBJECTS { 4033 ospfv3RouterId, 4034 ospfv3AdminStatus, 4035 ospfv3VersionNumber, 4036 ospfv3AreaBdrRtrStatus, 4037 ospfv3ASBdrRtrStatus, 4038 ospfv3AsScopeLsaCount, 4039 ospfv3AsScopeLsaCksumSum, 4040 ospfv3OriginateNewLsas, 4041 ospfv3RxNewLsas, 4042 ospfv3ExtLsaCount, 4043 ospfv3ExtAreaLsdbLimit, 4044 ospfv3ExitOverflowInterval, 4045 ospfv3DemandExtensions, 4046 ospfv3ReferenceBandwidth, 4047 ospfv3RestartSupport, 4048 ospfv3RestartInterval, 4049 ospfv3RestartStrictLsaChecking, 4050 ospfv3RestartStatus, 4051 ospfv3RestartAge, 4052 ospfv3RestartExitReason, 4053 ospfv3NotificationEnable, 4054 ospfv3StubRouterSupport, 4055 ospfv3StubRouterAdvertisement, 4056 ospfv3DiscontinuityTime, 4057 ospfv3RestartTime 4058 } 4059 STATUS current 4060 DESCRIPTION 4061 "These objects are used for managing/monitoring 4062 OSPFv3 global parameters." 4063 ::= { ospfv3Groups 1 } 4065 ospfv3AreaGroup OBJECT-GROUP 4066 OBJECTS { 4067 ospfv3AreaImportAsExtern, 4068 ospfv3AreaSpfRuns, 4069 ospfv3AreaBdrRtrCount, 4070 ospfv3AreaAsBdrRtrCount, 4071 ospfv3AreaScopeLsaCount, 4072 ospfv3AreaScopeLsaCksumSum, 4073 ospfv3AreaSummary, 4074 ospfv3AreaRowStatus, 4075 ospfv3AreaStubMetric, 4076 ospfv3AreaNssaTranslatorRole, 4077 ospfv3AreaNssaTranslatorState, 4078 ospfv3AreaNssaTranslatorStabInterval, 4079 ospfv3AreaNssaTranslatorEvents, 4080 ospfv3AreaStubMetricType, 4081 ospfv3AreaTEEnabled 4082 } 4083 STATUS current 4084 DESCRIPTION 4085 "These objects are used for OSPFv3 systems 4086 supporting areas." 4087 ::= { ospfv3Groups 2 } 4089 ospfv3AsLsdbGroup OBJECT-GROUP 4090 OBJECTS { 4091 ospfv3AsLsdbSequence, 4092 ospfv3AsLsdbAge, 4093 ospfv3AsLsdbChecksum, 4094 ospfv3AsLsdbAdvertisement, 4095 ospfv3AsLsdbTypeKnown 4096 } 4097 STATUS current 4098 DESCRIPTION 4099 "These objects are used for OSPFv3 systems 4100 that display their AS-scope link state database." 4101 ::= { ospfv3Groups 3 } 4103 ospfv3AreaLsdbGroup OBJECT-GROUP 4104 OBJECTS { 4105 ospfv3AreaLsdbSequence, 4106 ospfv3AreaLsdbAge, 4107 ospfv3AreaLsdbChecksum, 4108 ospfv3AreaLsdbAdvertisement, 4109 ospfv3AreaLsdbTypeKnown 4110 } 4111 STATUS current 4112 DESCRIPTION 4113 "These objects are used for OSPFv3 systems 4114 that display their Area-scope link state database." 4115 ::= { ospfv3Groups 4 } 4117 ospfv3LinkLsdbGroup OBJECT-GROUP 4118 OBJECTS { 4119 ospfv3LinkLsdbSequence, 4120 ospfv3LinkLsdbAge, 4121 ospfv3LinkLsdbChecksum, 4122 ospfv3LinkLsdbAdvertisement, 4123 ospfv3LinkLsdbTypeKnown 4124 } 4125 STATUS current 4126 DESCRIPTION 4127 "These objects are used for OSPFv3 systems 4128 that display their Link-scope link state database 4129 for non-virtual interfaces." 4130 ::= { ospfv3Groups 5 } 4132 ospfv3HostGroup OBJECT-GROUP 4133 OBJECTS { 4134 ospfv3HostMetric, 4135 ospfv3HostRowStatus, 4136 ospfv3HostAreaID 4137 } 4138 STATUS current 4139 DESCRIPTION 4140 "These objects are used for OSPFv3 systems 4141 that support attached hosts." 4142 ::= { ospfv3Groups 6 } 4144 ospfv3IfGroup OBJECT-GROUP 4145 OBJECTS { 4146 ospfv3IfAreaId, 4147 ospfv3IfType, 4148 ospfv3IfAdminStatus, 4149 ospfv3IfRtrPriority, 4150 ospfv3IfTransitDelay, 4151 ospfv3IfRetransInterval, 4152 ospfv3IfHelloInterval, 4153 ospfv3IfRtrDeadInterval, 4154 ospfv3IfPollInterval, 4155 ospfv3IfState, 4156 ospfv3IfDesignatedRouter, 4157 ospfv3IfBackupDesignatedRouter, 4158 ospfv3IfEvents, 4159 ospfv3IfRowStatus, 4160 ospfv3IfDemand, 4161 ospfv3IfMetricValue, 4162 ospfv3IfLinkScopeLsaCount, 4163 ospfv3IfLinkLsaCksumSum, 4164 ospfv3IfDemandNbrProbe, 4165 ospfv3IfDemandNbrProbeRetransLimit, 4166 ospfv3IfDemandNbrProbeInterval, 4167 ospfv3IfTEDisabled, 4168 ospfv3IfLinkLSASuppression 4169 } 4170 STATUS current 4171 DESCRIPTION 4172 "These interface objects used for 4173 managing/monitoring OSPFv3 interfaces." 4174 ::= { ospfv3Groups 7 } 4176 ospfv3VirtIfGroup OBJECT-GROUP 4177 OBJECTS { 4178 ospfv3VirtIfIndex, 4179 ospfv3VirtIfInstId, 4180 ospfv3VirtIfTransitDelay, 4181 ospfv3VirtIfRetransInterval, 4182 ospfv3VirtIfHelloInterval, 4183 ospfv3VirtIfRtrDeadInterval, 4184 ospfv3VirtIfState, 4185 ospfv3VirtIfEvents, 4186 ospfv3VirtIfRowStatus, 4187 ospfv3VirtIfLinkScopeLsaCount, 4188 ospfv3VirtIfLinkLsaCksumSum 4189 } 4190 STATUS current 4191 DESCRIPTION 4192 "These virtual interface objects are used for 4193 managing/monitoring OSPFv3 virtual interfaces." 4194 ::= { ospfv3Groups 8 } 4196 ospfv3NbrGroup OBJECT-GROUP 4197 OBJECTS { 4198 ospfv3NbrAddressType, 4199 ospfv3NbrAddress, 4200 ospfv3NbrOptions, 4201 ospfv3NbrPriority, 4202 ospfv3NbrState, 4203 ospfv3NbrEvents, 4204 ospfv3NbrLsRetransQLen, 4205 ospfv3NbrHelloSuppressed, 4206 ospfv3NbrIfId, 4207 ospfv3NbrRestartHelperStatus, 4208 ospfv3NbrRestartHelperAge, 4209 ospfv3NbrRestartHelperExitReason 4210 } 4211 STATUS current 4212 DESCRIPTION 4213 "These neighbor objects are used for 4214 managing/monitoring OSPFv3 neighbors." 4215 ::= { ospfv3Groups 9 } 4217 ospfv3CfgNbrGroup OBJECT-GROUP 4218 OBJECTS { 4219 ospfv3CfgNbrPriority, 4220 ospfv3CfgNbrRowStatus 4221 } 4222 STATUS current 4223 DESCRIPTION 4224 "These configured neighbor objects are used for 4225 managing/monitoring OSPFv3 configured neighbors." 4226 ::= { ospfv3Groups 10 } 4228 ospfv3VirtNbrGroup OBJECT-GROUP 4229 OBJECTS { 4230 ospfv3VirtNbrIfIndex, 4231 ospfv3VirtNbrIfInstId, 4232 ospfv3VirtNbrAddressType, 4233 ospfv3VirtNbrAddress, 4234 ospfv3VirtNbrOptions, 4235 ospfv3VirtNbrState, 4236 ospfv3VirtNbrEvents, 4237 ospfv3VirtNbrLsRetransQLen, 4238 ospfv3VirtNbrHelloSuppressed, 4239 ospfv3VirtNbrIfId, 4240 ospfv3VirtNbrRestartHelperStatus, 4241 ospfv3VirtNbrRestartHelperAge, 4242 ospfv3VirtNbrRestartHelperExitReason 4243 } 4244 STATUS current 4245 DESCRIPTION 4246 "These virtual neighbor objects are used for 4247 managing/monitoring OSPFv3 virtual neighbors." 4248 ::= { ospfv3Groups 11 } 4250 ospfv3AreaAggregateGroup OBJECT-GROUP 4251 OBJECTS { 4252 ospfv3AreaAggregateRowStatus, 4253 ospfv3AreaAggregateEffect, 4254 ospfv3AreaAggregateRouteTag 4255 } 4256 STATUS current 4257 DESCRIPTION 4258 "These area aggregate objects used required for 4259 aggregating OSPFv3 prefixes for summarization 4260 across areas." 4261 ::= { ospfv3Groups 12 } 4263 ospfv3VirtLinkLsdbGroup OBJECT-GROUP 4264 OBJECTS { 4265 ospfv3VirtLinkLsdbSequence, 4266 ospfv3VirtLinkLsdbAge, 4267 ospfv3VirtLinkLsdbChecksum, 4268 ospfv3VirtLinkLsdbAdvertisement, 4269 ospfv3VirtLinkLsdbTypeKnown 4270 } 4271 STATUS current 4272 DESCRIPTION 4273 "These objects are used for OSPFv3 systems 4274 that display their Link-scope link state database 4275 for virtual interfaces." 4276 ::= { ospfv3Groups 13 } 4278 ospfv3NotificationObjectGroup OBJECT-GROUP 4279 OBJECTS { 4280 ospfv3ConfigErrorType, 4281 ospfv3PacketType, 4282 ospfv3PacketSrc 4283 } 4284 STATUS current 4285 DESCRIPTION 4286 "These objects are used to record notification 4287 parameters" 4288 ::= { ospfv3Groups 14 } 4290 ospfv3NotificationGroup NOTIFICATION-GROUP 4291 NOTIFICATIONS { 4292 ospfv3VirtIfStateChange, 4293 ospfv3NbrStateChange, 4294 ospfv3VirtNbrStateChange, 4295 ospfv3IfConfigError, 4296 ospfv3VirtIfConfigError, 4297 ospfv3IfRxBadPacket, 4298 ospfv3VirtIfRxBadPacket, 4299 ospfv3LsdbOverflow, 4300 ospfv3LsdbApproachingOverflow, 4301 ospfv3IfStateChange, 4302 ospfv3NssaTranslatorStatusChange, 4303 ospfv3RestartStatusChange, 4304 ospfv3NbrRestartHelperStatusChange, 4305 ospfv3VirtNbrRestartHelperStatusChange 4306 } 4307 STATUS current 4308 DESCRIPTION 4309 "This group is used for OSPFv3 notifications" 4310 ::= { ospfv3Groups 15 } 4312 END 4314 6. Security Considerations 4316 There are a number of management objects defined in this MIB module 4317 with a MAX-ACCESS clause of read-write and/or read-create. Such 4318 objects may be considered sensitive or vulnerable in some network 4319 environments. The support for SET operations in a non-secure 4320 environment without proper protection can have a negative effect on 4321 network operations. Improper manipulation of the objects represented 4322 by this MIB may result in disruption of network connectivity by 4323 administratively disabling the entire OSPFv3 entity or individual 4324 interfaces, by deleting configured neighbors, by reducing the limit 4325 on External LSAs, by changing ASBR status, by manipulating route 4326 aggregation, by manipulating interface and route metrics, by changing 4327 hello interval or dead interval, or by changing interface type. 4328 Remote monitoring can be defeated by disabling of SNMP notifications. 4329 Performance can be impacted by increasing the limit on External LSAs 4330 or changing DR/BDR priority. 4332 Some of the readable objects in this MIB module (i.e., objects with a 4333 MAX-ACCESS other than not-accessible) may be considered sensitive or 4334 vulnerable in some network environments. It is thus important to 4335 control even GET and/or NOTIFY access to these objects and possibly 4336 to even encrypt the values of these objects when sending them over 4337 the network via SNMP. Unauthorized access to readable objects in this 4338 MIB allows the discovery of the network topology and operating 4339 parameters which can be used to target further attacks on the network 4340 or to gain a competitive business advantage. 4342 SNMP versions prior to SNMPv3 did not include adequate security. 4343 Even if the network itself is secure (for example by using IPsec), 4344 even then, there is no control as to who on the secure network is 4345 allowed to access and GET/SET (read/change/create/delete) the objects 4346 in this MIB module. 4348 It is RECOMMENDED that implementers consider the security features as 4349 provided by the SNMPv3 framework (see [RFC3410], section 8), 4350 including full support for the SNMPv3 cryptographic mechanisms (for 4351 authentication and privacy). 4353 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4354 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4355 enable cryptographic security. It is then a customer/operator 4356 responsibility to ensure that the SNMP entity giving access to an 4357 instance of this MIB module is properly configured to give access to 4358 the objects only to those principals (users) that have legitimate 4359 rights to indeed GET or SET (change/create/delete) them. 4361 7. IANA Considerations 4363 The MIB module in this document uses the following IANA-assigned 4364 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 4366 Descriptor OBJECT IDENTIFIER value 4367 ---------- ----------------------- 4369 ospfv3MIB { mib-2 YYY } 4371 [Editor's Note (to be removed prior to publication): the IANA is 4372 requested to assign a value for "YYY" under the 'mib-2' subtree and 4373 to record the assignment in the SMI Numbers registry. When the 4374 assignment has been made, the RFC Editor is asked to replace "YYY" 4375 (here and in the MIB module) with the assigned value and to remove 4376 this note.] 4378 8. Acknowledgements 4380 This document is based on the MIB for OSPF version 2 [RFC4750]. The 4381 editors would like to thank Toshiaki Takada, Ramachandran 4382 Radhakrishnan, Harikrishna Golapalli Mahesh Kurapati, Acee Lindem, 4383 Keith McCloghrie, Manish Gupta, Nic Neate, Vanitha N., Vivek Dubey, 4384 Ramana Koppula, Boris Benenson and Hong Zhang for their constructive 4385 comments. Special thanks to Joan Cucchiara for her thorough review as 4386 the MIB Doctor. 4388 9. Normative References 4390 [RFC2328] Moy, J., "OSPF Version 2", RFC 2328, April 1998. 4392 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4393 Rose, M. and S. Waldbusser, "Structure of Management 4394 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 4395 1999. 4397 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4398 Rose, M. and S. Waldbusser, "Textual Conventions for 4399 SMIv2", STD 58, RFC 2579, April 1999. 4401 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4402 Rose, M. and S. Waldbusser, "Conformance Statements for 4403 SMIv2", STD 58, RFC 2580, April 1999. 4405 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 4406 for IPv6", RFC5340, July 2008 4408 [RFC4293] Routhier, S. Ed., "Management Information Base for 4409 The Internet Protocol (IP)", RFC 4293, April 2006. 4411 [RFC4750] Joyal, D., Galecki, P. and Giacalone, S., "OSPF Version 2 4412 Management Information Base", RFC 4750, December 2006. 4414 10. Informative References 4416 [RFC1224] Steinberg, L., "Techniques for Managing Asynchronously 4417 Generated Alerts", RFC 1224, May 1991. 4419 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 4420 Requirement Levels", BCP 14, RFC 2119, March 1997. 4422 [RFC2460] Deering, S., and R. Hinden, "Internet Protocol, Version 6 4423 (IPv6) Specification", RFC 2460, December 1998. 4425 [RFC3410] Case, J., Mundy, R., Partain, D., Stewart, B., 4426 "Introduction and Applicability Statements for 4427 Internet-Standard Management Framework", RFC 3410, 4428 December 2002. 4430 [RFC3411] Harrington, D., Presuhn, R., Wijnen, B., 4431 "An Architecture for Describing Simple Network Management 4432 Protocol (SNMP) Management Frameworks", RFC 3411, 4433 December 2002. 4435 [RFC3413] Levi, D., Meyer, P., Stewart, B., 4436 "Simple Network Management Protocol (SNMP) Applications", 4437 RFC 3413, December 2002. 4439 [RFC3414] Blumenthal, U., Wijnen, B., "User-based Security Model 4440 (USM) for version 3 of the Simple Network Management 4441 Protocol (SNMPv3)", RFC 3414, December 2002. 4443 [RFC3415] Wijnen, B., Presuhn, R., McCloghrie, K., 4444 "View-based Access Control Model (VACM) for the 4445 Simple Network Management Protocol (SNMP)", RFC 3415, 4446 December 2002. 4448 11. Contributors' Addresses 4450 Jacek Kwiatkowski 4451 Intel Technology Poland 4452 ul. Slowackiego 173 4453 80-298 Gdansk, Poland 4454 Email: jacek.kwiatkowski@intel.com 4456 Sebastian Zwolinski 4457 Intel Technology Poland 4458 ul. Slowackiego 173 4459 80-298 Gdansk, Poland 4460 Email: sebastian.zwolinski@intel.com 4462 12. Editors' Addresses 4464 Dan Joyal 4465 Nortel 4466 600 Technology Park Drive 4467 Billerica, MA 01821 4468 Email: djoyal@nortel.com 4470 Vishwas Manral 4471 IP Infusion 4472 Bangalore 4473 India 4474 Email: vishwas@ipinfusion.com