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