idnits 2.17.1 draft-ietf-ospf-ospfv3-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 60 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 61 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 264 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 17 instances of too long lines in the document, the longest one being 10 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 433: '...base. OspfExtAreaLsdbLimit MUST be set...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 10 has weird spacing: '...in full confo...' == Line 14 has weird spacing: '...), its areas...' == Line 15 has weird spacing: '...ups may also ...' == Line 19 has weird spacing: '... months and ...' == Line 20 has weird spacing: '...iate to use ...' == (259 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '2' is defined on line 2432, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 2452, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 2455, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 2462, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 2466, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 2470, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '4') ** Obsolete normative reference: RFC 1905 (ref. '5') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1573 (ref. '6') (Obsoleted by RFC 2233) ** Obsolete normative reference: RFC 2460 (ref. '7') (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 1850 (ref. '8') (Obsoleted by RFC 4750) == Outdated reference: A later version (-08) exists of draft-ietf-ospf-ospfv6-06 ** Obsolete normative reference: RFC 2465 (ref. '10') (Obsoleted by RFC 4293, RFC 8096) Summary: 15 errors (**), 0 flaws (~~), 16 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Management Information Base for OSPFv3 2 4 Dan Joyal 6 Nortel Networks, Inc. 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance 11 with all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet 14 Engineering Task Force (IETF), its areas, and its working 15 groups. Note that other groups may also distribute working 16 documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six 19 months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet- 21 Drafts as reference material or to cite them other than as 22 "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed 28 at http://www.ietf.org/shadow.html. 30 Abstract 32 This memo defines an experimental portion of the Management 33 Information Base (MIB) for use with network management 34 protocols in IPv6-based internets. In particular, it defines 35 objects for managing the Open Shortest Path First Routing 36 Protocol for IPv6. 38 This document specifies a MIB module in a manner that is both 39 compliant to the SNMPv2 SMI, and semantically identical to the 40 peer SNMPv1 definitions. 42 Please send comments to ospf@discuss.microsoft.com. 44 1. The SNMPv2 Network Management Framework 46 The SNMPv2 Network Management Framework presently consists of 47 three major components. They are: 49 o the SMI, described in RFC 1902 [1] - the mechanisms used 50 for describing and naming objects for the purpose of 51 management. 53 o the MIB-II, described in RFC 1213/STD 17 [3] - the core 54 set of managed objects for the Internet suite of 55 protocols. 57 o RFC 1157 [4] and RFC 1905 [5] which define two versions 58 of the protocol used for network access to managed 59 objects. 61 The Framework permits new objects to be defined for the 62 purpose of experimentation and evaluation. 64 1.1. Object Definitions 66 Managed objects are accessed via a virtual information store, 67 termed the Management Information Base or MIB. Objects in the 68 MIB are defined using the subset of Abstract Syntax Notation 69 One (ASN.1) defined in the SMI. In particular, each object 70 object type is named by an OBJECT IDENTIFIER, an 71 administratively assigned name. The object type together with 72 an object instance serves to uniquely identify a specific 73 instantiation of the object. For human convenience, we often 74 use a textual string, termed the descriptor, to refer to the 75 object type. 77 2. Differences from RFC 1850 79 (1) Textual Conventions are imported from IPV6-TC and OSPF- 80 MIB MIBs. 82 (2) The "ospf" prefix for entity names is changed to 83 "ospfv3". 85 (3) General Group object name ospfVersionNumber is changed to 86 ospfv3VersionNumber and its value is changed from 2 to 3. 88 (4) General Group object name ospfExternLsaCount is changed 89 to ospfv3AsScopeLsaCount to indicate count of all AS- 90 scoped LSAs in the database. 92 (5) General Group object name ospfExternLsaCksumSum is 93 changed to ospfv3AsScopeCksumSum to indicate checksum of 94 all AS-scoped LSAs in the database. 96 (6) Removed General Group object ospfTOSSupport. 98 (7) Removed ospfAuthType object from Area entry. 100 (8) Changed object names ospfAreaLsaCount and 101 ospfAreaLsaCksumSum to ospfv3AreaScopeLsaCount and 102 ospfv3AreaScopeLsaCksumSum. 104 (9) Removed OSPF Area Default Metric Table. 106 (10) Added object ospfv3StubMetric to Area entry as substitute 107 for Area Default Metric Table. 109 (11) Changed name of External LSDB Table to AS-Scope LSDB 110 Table. Replaced object name prefix "ospfExtLsdb" with 111 "ospfv3AsLsdb". 113 (12) Changed name of LSDB Table to Area-Scope LSDB Table. 114 Replaced object name prefix "ospfLsdb" with 115 "ospfv3AreaLsdb". 117 (13) Added ospfv3LinkLsdbTable which contains all LSAs of 118 Link-Scope. Index of ospfv3LinkLsdbTable is IPv6 119 interface index, LSA Type, Router ID and LSID. 121 (14) Re-ordered Router ID and LSID index components of LSDB 122 table entries. Since LSIDs no longer have addressing 123 semantics, GET-NEXT operations on partial OIDs are more 124 useful when the Router ID component comes before the LSID 125 component. 127 (15) Address Range Table is removed. 129 (16) Removed ospfHostTOS from Host Table entry. Object 130 ospfHostIpAddress changed to ospfv3HostIpv6Address with 131 SYNTAX changed from IpAddress to Ipv6Address. 133 (17) Objects ospfIfIpAddress and ospfAddressLessIf removed 134 from Interface entry and as Interface Table entry index 135 components. 137 (18) Object ospfv3IfIndex added to Interface Table entry with 138 SYNTAX Ipv6IfIndex. It replaces ospfIfIpAddress and 139 ospfAddressLessIf as the Interface Table entry index. 141 (19) The SYNTAX of objects ospfIfDesignatedRouter and 142 ospfIfBackupDesignatedRouter is changed from IpAddress to 143 RouterID. 145 (20) Objects ospfIfAuthType and ospfIfAuthKey are removed from 146 Interface and Virtual Interface entries. 148 (21) Added objects ospfv3IfLinkScopeLsaCount and 149 ospfv3IfLinkLsaCksumSum to Interface entry. They maintain 150 the count of Link-Scope LSAs and the checksum of the 151 Link-Scope LSA database associated with the interface. 153 (22) Removed OSPF Interface Metric Table. Metric is now 154 accessed via object ospfv3IfMetricValue in the Interface 155 entry. 157 (23) Added object ospfv3IfInstId to Interface entry to enable 158 the setting of the interface instance value of the 159 interface. The default value is zero. 161 (24) Added object ospfv3VirtIfIndex to Virtual Interface entry 162 which is used to assign a local interface ID to the 163 virtual interface. 165 (25) Added objects ospfv3VirtIfLinkScopeLsaCount and 166 ospfv3VirtIfLinkLsaCksumSum to Virtual Interface entry. 167 They maintain the count of Link-Scope LSAs and the 168 checksum of the Link-Scope LSA database associated with 169 the virtual interface. 171 (26) Removed objects ospfNbrIpAddr and ospfNbrAddressLessIndex 172 from Neighbor entry. 174 (27) Added object ospfv3NbrIfIndex to Neighbor entry. Index 175 components ospfNbrIpAddr and ospfNbrAddressLessIndex are 176 replaced with ospfv3NbrIfIndex and ospfv3NbrRtrId. 178 (28) Added object ospfv3NbrIfId to Neighbor entry. This object 179 contains the neighbor's local interface index from the 180 neighbor's hellos advertised on the link. 182 (29) Added object ospfv3VirtNbrIfIndex to Virtual Neighbor 183 entry. This is the interface index of the virtual link 184 over which the virtual neighbor is reached. 186 (30) Changed object name ospfVirtNbrIpAddr to 187 ospfv3VirtNbrIpv6Addr and SYNTAX from IpAddress to 188 Ipv6Address. 190 (31) Added object ospfv3VirtNbrIfId to Virtual Neighbor entry. 191 This is the virtual neighbor's local virtual interface 192 index from the neighbor's hellos advertised on the 193 virtual link. 195 (32) Added object ospfv3AreaAggregateIndex to Area Aggregate 196 entry. This allows for a fixed length index for Area 197 Aggregate Table entries. 199 (33) Replaced object ospfAreaAggregateMask with 200 ospfv3AreaAggregatePrefixLen. 202 (34) Replaced object ospfAreaAggregateNet with 203 ospfv3AreaAggregatePrefix. 205 (35) Index for Area Aggregate Table entry changed from 206 ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType, 207 ospfAreaAggregateNet, ospfAreaAggregateMask to 208 ospfv3AreaAggregateAreaID, 209 ospfv3AreaAggregateAreaLsdbType, 210 ospfv3AreaAggregateIndex. 212 (36) Conformance information is changed to reflect object 213 groups removed or added. 215 (37) OSPFv3 traps are not defined. 217 3. Structure of MIB 219 The MIB is composed of the following sections: 221 General Variables 222 Area Table 223 Area-Scope Link State Database 224 Link-Scope Link State Database 225 AS-Scope Link State Database 226 Host Table 227 Interface Table 228 Virtual Interface Table 229 Neighbor Table 230 Virtual Neighbor Table 231 Aggregate Range Table 233 3.1. General Variables 235 The General Variables are global to the OSPFv3 Process. 237 3.2. Area Table 239 The Area Data Structure describes the OSPFv3 Areas that the 240 router participates in. 242 3.3. Area-Scope, Link-Scope and AS-Scope Link State 243 Database 245 The Link State Database is provided primarily to provide 246 detailed information for network debugging. 248 3.4. Host Table 250 The Host Table is provided to view configured Host Route 251 information. 253 3.5. Interface Table 255 The Interface Table describes the various IPv6 links on which 256 OSPFv3 is configured. 258 3.6. Virtual Interface Table 260 The Virtual Interface Table describes virtual OSPFv3 links. 262 3.7. Neighbor and Virtual Neighbor Tables 264 The Neighbor Table and the Virtual Neighbor Table describe the 265 neighbors to the OSPF Process. 267 3.8. Aggregate Range Table 269 The Aggregate Range Table describes prefixes which summarize 270 routing information for export outside of an Area. 272 4. Definitions 274 OSPFV3-MIB DEFINITIONS ::= BEGIN 276 IMPORTS 277 MODULE-IDENTITY, OBJECT-TYPE, experimental 278 Counter32, Gauge32, Integer32, Unsigned32 279 FROM SNMPv2-SMI 280 TEXTUAL-CONVENTION, TruthValue, RowStatus 281 FROM SNMPv2-TC 282 MODULE-COMPLIANCE, OBJECT-GROUP 283 FROM SNMPv2-CONF 284 Ipv6IfIndex, Ipv6Address, Ipv6AddressPrefix, 285 FROM IPV6-TC 286 AreaID, RouterID, Metric, BigMetric, Status, PositiveInteger, 287 HelloRange, UpToMaxAge, DesignatedRouterPriority 288 FROM OSPF-MIB 289 ; 291 ospfv3Mib OBJECT IDENTIFIER ::= { experimental --to be assigned-- } 293 ospfv3 MODULE-IDENTITY 294 LAST-UPDATED "9907082155Z" 295 ORGANIZATION "IETF OSPF Working Group" 296 CONTACT-INFO 297 " Dan Joyal 298 Postal: Nortel Networks 299 600 Technology Park Drive 300 Billerica, MA 01821 301 USA 302 Tel: +1-978-288-2629 303 E-Mail: djoyal@nortelnetworks.com" 304 DESCRIPTION 305 "The MIB module to describe the OSPF Version for IPv6" 306 ::= { ospfv3Mib 1 } 308 -- OSPFv3 General Variables 310 -- These parameters apply globally to the Router's 311 -- OSPFv3 Process. 313 ospfv3GeneralGroup OBJECT IDENTIFIER ::= { ospfv3 1 } 314 ospfv3RouterId OBJECT-TYPE 315 SYNTAX RouterID 316 MAX-ACCESS read-write 317 STATUS current 318 DESCRIPTION 319 "A 32-bit integer uniquely identifying the 320 router in the Autonomous System. 322 By convention, to ensure uniqueness, this 323 should default to the value of one of the 324 router's IPv4 interface addresses if IPv4 is 325 configured." 326 ::= { ospfv3GeneralGroup 1 } 328 ospfv3AdminStat OBJECT-TYPE 329 SYNTAX Status 330 MAX-ACCESS read-write 331 STATUS current 332 DESCRIPTION 333 "The administrative status of OSPFv3 in the 334 router. The value 'enabled' denotes that the 335 OSPFv3 Process is active on at least one inter- 336 face; 'disabled' disables it on all inter- 337 faces." 338 ::= { ospfv3GeneralGroup 2 } 340 ospfv3VersionNumber OBJECT-TYPE 341 SYNTAX INTEGER { version3 (3) } 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The version number of OSPF for IPv6 is 3." 346 ::= { ospfv3GeneralGroup 3 } 348 ospfv3AreaBdrRtrStatus OBJECT-TYPE 349 SYNTAX TruthValue 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "A flag to note whether this router is an area 354 border router." 355 REFERENCE 356 "OSPF Version 2, Section 3 Splitting the AS into 357 Areas" 358 ::= { ospfv3GeneralGroup 4 } 360 ospfv3ASBdrRtrStatus OBJECT-TYPE 361 SYNTAX TruthValue 362 MAX-ACCESS read-write 363 STATUS current 364 DESCRIPTION 365 "A flag to note whether this router is config- 366 ured as an Autonomous System border router." 367 REFERENCE 368 "OSPF Version 2, Section 3.3 Classification of 369 routers" 370 ::= { ospfv3GeneralGroup 5 } 372 ospfv3AsScopeLsaCount OBJECT-TYPE 373 SYNTAX Gauge32 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The number of AS-Scope (e.g. AS-External) link-state 378 advertisements in the link-state database." 379 ::= { ospfv3GeneralGroup 6 } 381 ospfv3AsScopeLsaCksumSum OBJECT-TYPE 382 SYNTAX Integer32 383 MAX-ACCESS read-only 384 STATUS current 385 DESCRIPTION 386 "The 32-bit unsigned sum of the LS checksums of 387 the AS-scoped link-state advertisements con- 388 tained in the link-state database. This sum 389 can be used to determine if there has been a 390 change in a router's link state database, and 391 to compare the link-state database of two 392 routers." 393 ::= { ospfv3GeneralGroup 7 } 395 ospfv3OriginateNewLsas OBJECT-TYPE 396 SYNTAX Counter32 397 MAX-ACCESS read-only 398 STATUS current 399 DESCRIPTION 400 "The number of new link-state advertisements 401 that have been originated. This number is in- 402 cremented each time the router originates a new 403 LSA." 404 ::= { ospfv3GeneralGroup 8 } 406 ospfv3RxNewLsas OBJECT-TYPE 407 SYNTAX Counter32 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The number of link-state advertisements re- 412 ceived determined to be new instantiations. 413 This number does not include newer instantia- 414 tions of self-originated link-state advertise- 415 ments." 416 ::= { ospfv3GeneralGroup 9 } 418 ospfv3ExtAreaLsdbLimit OBJECT-TYPE 419 SYNTAX Integer32 (-1..'7FFFFFFF'h) 420 MAX-ACCESS read-write 421 STATUS current 422 DESCRIPTION 423 "The maximum number of non-default AS- 424 external-LSAs entries that can be stored in the 425 link-state database. If the value is -1, then 426 there is no limit. 428 When the number of non-default AS-external-LSAs 429 in a router's link-state database reaches 430 ospfv3ExtAreaLsdbLimit, the router enters Overflow- 431 State. The router never holds more than 432 ospfv3ExtAreaLsdbLimit non-default AS-external-LSAs 433 in its database. OspfExtAreaLsdbLimit MUST be set 434 identically in all routers attached to the OSPFv3 435 backbone and/or any regular OSPFv3 area. (i.e., 436 OSPFv3 stub areas and NSSAs are excluded)." 437 DEFVAL { -1 } 438 ::= { ospfv3GeneralGroup 10 } 440 ospfv3MulticastExtensions OBJECT-TYPE 441 SYNTAX Integer32 442 MAX-ACCESS read-write 443 STATUS current 444 DESCRIPTION 445 "A Bit Mask indicating whether the router is 446 forwarding IPv6 multicast datagrams 447 based on the algorithms defined in the Multi- 448 cast Extensions to OSPF. 450 Bit 0, if set, indicates that the router can 451 forward IPv6 multicast datagrams in the router's 452 directly attached areas (called intra-area mul- 453 ticast routing). 455 Bit 1, if set, indicates that the router can 456 forward IPv6 multicast datagrams between OSPFv3 457 areas (called inter-area multicast routing). 459 Bit 2, if set, indicates that the router can 460 forward IPv6 multicast datagrams between Auto- 461 nomous Systems (called inter-AS multicast rout- 462 ing). 464 Only certain combinations of bit settings are 465 allowed, namely: 0 (no multicast forwarding is 466 enabled), 1 (intra-area multicasting only), 3 467 (intra-area and inter-area multicasting), 5 468 (intra-area and inter-AS multicasting) and 7 469 (multicasting everywhere). By default, no mul- 470 ticast forwarding is enabled." 471 DEFVAL { 0 } 472 ::= { ospfv3GeneralGroup 11 } 474 ospfv3ExitOverflowInterval OBJECT-TYPE 475 SYNTAX PositiveInteger 476 MAX-ACCESS read-write 477 STATUS current 478 DESCRIPTION 479 "The number of seconds that, after entering 480 OverflowState, a router will attempt to leave 481 OverflowState. This allows the router to again 482 originate non-default AS-External-LSAs. When 483 set to 0, the router will not leave Overflow- 484 State until restarted." 485 DEFVAL { 0 } 486 ::= { ospfv3GeneralGroup 12 } 488 ospfv3DemandExtensions OBJECT-TYPE 489 SYNTAX TruthValue 490 MAX-ACCESS read-write 491 STATUS current 492 DESCRIPTION 493 "The router's support for demand routing." 494 REFERENCE 495 "OSPF Version 2, Appendix on Demand Routing" 496 ::= { ospfv3GeneralGroup 13 } 498 -- The OSPFv3 Area Data Structure contains information 499 -- regarding the various areas. The interfaces and 500 -- virtual links are configured as part of these areas. 501 -- Area 0.0.0.0, by definition, is the Backbone Area 503 ospfv3AreaTable OBJECT-TYPE 504 SYNTAX SEQUENCE OF OspfAreaEntry 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "Information describing the configured parame- 509 ters and cumulative statistics of the router's 510 attached areas." 511 REFERENCE 512 "OSPF Version 2, Section 6 The Area Data Struc- 513 ture" 514 ::= { ospfv3 2 } 516 ospfv3AreaEntry OBJECT-TYPE 517 SYNTAX OspfAreaEntry 518 MAX-ACCESS not-accessible 519 STATUS current 520 DESCRIPTION 521 "Information describing the configured parame- 522 ters and cumulative statistics of one of the 523 router's attached areas." 524 INDEX { ospfv3AreaId } 525 ::= { ospfv3AreaTable 1 } 527 Ospfv3AreaEntry ::= 528 SEQUENCE { 529 ospfv3AreaId 530 AreaID, 531 ospfv3ImportAsExtern 532 INTEGER, 533 ospfv3SpfRuns 534 Counter32, 535 ospfv3AreaBdrRtrCount 536 Gauge32, 537 ospfv3AsBdrRtrCount 538 Gauge32, 539 ospfv3AreaScopeLsaCount 540 Gauge32, 541 ospfv3AreaScopeLsaCksumSum 542 Integer32, 543 ospfv3AreaSummary 544 INTEGER, 545 ospfv3AreaStatus 546 RowStatus, 547 ospfv3StubMetric, 548 BigMetric 549 } 551 ospfv3AreaId OBJECT-TYPE 552 SYNTAX AreaID 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "A 32-bit integer uniquely identifying an area. 557 Area ID 0.0.0.0 is used for the OSPFv3 backbone." 558 REFERENCE 559 "OSPF Version 2, Appendix C.2 Area parameters" 560 ::= { ospfv3AreaEntry 1 } 562 ospfv3ImportAsExtern OBJECT-TYPE 563 SYNTAX INTEGER { 564 importExternal (1), -- normal area 565 importNoExternal (2), -- stub area 566 importNssa (3) -- not-so-stubby-area 567 } 568 MAX-ACCESS read-create 569 STATUS current 570 DESCRIPTION 571 "The area's support for importing AS external 572 link- state advertisements." 573 REFERENCE 574 "OSPF Version 2, Appendix C.2 Area parameters" 575 DEFVAL { importExternal } 576 ::= { ospfv3AreaEntry 2 } 578 ospfv3SpfRuns OBJECT-TYPE 579 SYNTAX Counter32 580 MAX-ACCESS read-only 581 STATUS current 582 DESCRIPTION 583 "The number of times that the intra-area route 584 table has been calculated using this area's 585 link-state database. This is typically done 586 using Dijkstra's algorithm." 587 ::= { ospfv3AreaEntry 3 } 589 ospfv3AreaBdrRtrCount OBJECT-TYPE 590 SYNTAX Gauge32 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The total number of area border routers reach- 595 able within this area. This is initially zero, 596 and is calculated in each SPF Pass." 597 ::= { ospfv3AreaEntry 4 } 599 ospfv3AsBdrRtrCount OBJECT-TYPE 600 SYNTAX Gauge32 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "The total number of Autonomous System border 605 routers reachable within this area. This is 606 initially zero, and is calculated in each SPF 607 Pass." 608 ::= { ospfv3AreaEntry 5 } 610 ospfv3AreaScopeLsaCount OBJECT-TYPE 611 SYNTAX Gauge32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The total number of Area-Scope link-state advertisements 616 in this area's link-state database." 617 ::= { ospfv3AreaEntry 6 } 619 ospfv3AreaScopeLsaCksumSum OBJECT-TYPE 620 SYNTAX Integer32 621 MAX-ACCESS read-only 622 STATUS current 623 DESCRIPTION 624 "The 32-bit unsigned sum of the Area-Scope link-state 625 advertisements' LS checksums contained in this 626 area's link-state database. The sum can be used 627 to determine if there has been a change in a 628 router's link state database, and to compare the 629 link-state database of two routers." 630 DEFVAL { 0 } 631 ::= { ospfv3AreaEntry 7 } 633 ospfv3AreaSummary OBJECT-TYPE 634 SYNTAX INTEGER { 635 noAreaSummary (1), 636 sendAreaSummary (2) 637 } 638 MAX-ACCESS read-create 639 STATUS current 640 DESCRIPTION 641 "The variable ospfv3AreaSummary controls the im- 642 port of summary LSAs into stub areas. It has 643 no effect on other areas. 645 If it is noAreaSummary, the router will neither 646 originate nor propagate summary LSAs into the 647 stub area. It will rely entirely on its de- 648 fault route. 650 If it is sendAreaSummary, the router will both 651 summarize and propagate summary LSAs." 652 DEFVAL { noAreaSummary } 653 ::= { ospfv3AreaEntry 8 } 655 ospfv3AreaStatus OBJECT-TYPE 656 SYNTAX RowStatus 657 MAX-ACCESS read-create 658 STATUS current 659 DESCRIPTION 660 "This variable displays the status of the en- 661 try. Setting it to 'invalid' has the effect of 662 rendering it inoperative. The internal effect 663 (row removal) is implementation dependent." 664 ::= { ospfv3AreaEntry 9 } 666 ospfv3StubMetric OBJECT-TYPE 667 SYNTAX BigMetric 668 MAX-ACCESS read-create 669 STATUS current 670 DESCRIPTION 671 "The metric value advertised for the default route 672 into Stub areas." 673 ::= { ospfv3AreaEntry 10 } 675 -- OSPFv3 AS-Scope Link State Database 677 -- The Link State Database contains the AS-Scope Link State 678 -- Advertisements from throughout the areas that the 679 -- device is attached to. 681 ospfv3AsLsdbTable OBJECT-TYPE 682 SYNTAX SEQUENCE OF OspfAsLsdbEntry 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "The OSPFv3 Process's AS-Scope Link State Database." 687 ::= { ospfv3 3 } 689 ospfv3AsLsdbEntry OBJECT-TYPE 690 SYNTAX OspfAsLsdbEntry 691 MAX-ACCESS not-accessible 692 STATUS current 693 DESCRIPTION 694 "A single AS-Scope Link State Advertisement." 695 INDEX { ospfv3AsLsdbType, 696 ospfv3AsLsdbRouterId, 697 ospfv3AsLsdbLsid } 698 ::= { ospfv3AsLsdbTable 1 } 700 Ospfv3AsLsdbEntry ::= 701 SEQUENCE { 702 ospfv3AsLsdbType 703 INTEGER, 704 ospfv3AsLsdbRouterId 705 RouterID, 706 ospfv3AsLsdbLsid 707 IpAddress, 708 ospfv3AsLsdbSequence 709 Integer32, 710 ospfv3AsLsdbAge 711 Integer32, 712 ospfv3AsLsdbChecksum 713 Integer32, 714 ospfv3AsLsdbAdvertisement 715 OCTET STRING 716 } 718 ospfv3AsLsdbType OBJECT-TYPE 719 SYNTAX INTEGER { 720 asExternalLink (16389) -- 0x4005 721 } 722 MAX-ACCESS read-only 723 STATUS current 724 DESCRIPTION 725 "The type of the link state advertisement. 726 Each link state type has a separate advertise- 727 ment format. Unrecognized AS-Scope LSAs with the 728 U-bit set are also store in this database." 729 ::= { ospfv3AsLsdbEntry 1 } 731 ospfv3AsLsdbRouterId OBJECT-TYPE 732 SYNTAX RouterID 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The 32 bit number that uniquely identifies the 737 originating router in the Autonomous System." 738 REFERENCE 739 "OSPF Version 2, Appendix C.1 Global parameters" 740 ::= { ospfv3AsLsdbEntry 2 } 742 ospfv3AsLsdbLsid OBJECT-TYPE 743 SYNTAX IpAddress 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The Link State ID is an LS Type Specific field 748 containing either a Router ID or a unique identifier; 749 it identifies the piece of the routing domain 750 that is being described by the advertisement. 751 In contrast to OSPF for IPv4, the LSID has no 752 addressing semantics." 753 ::= { ospfv3AsLsdbEntry 3 } 755 -- Note that the OSPF Sequence Number is a 32 bit signed 756 -- integer. It starts with the value '80000001'h, 757 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 758 -- Thus, a typical sequence number will be very negative. 760 ospfv3AsLsdbSequence OBJECT-TYPE 761 SYNTAX Integer32 762 MAX-ACCESS read-only 763 STATUS current 764 DESCRIPTION 765 "The sequence number field is a signed 32-bit 766 integer. It is used to detect old and dupli- 767 cate link state advertisements. The space of 768 sequence numbers is linearly ordered. The 769 larger the sequence number the more recent the 770 advertisement." 771 REFERENCE 772 "OSPF Version 2, Section 12.1.6 LS sequence 773 number" 774 ::= { ospfv3AsLsdbEntry 4 } 776 ospfv3AsLsdbAge OBJECT-TYPE 777 SYNTAX Integer32 -- Should be 0..MaxAge 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "This field is the age of the link state adver- 782 tisement in seconds." 783 REFERENCE 784 "OSPF Version 2, Section 12.1.1 LS age" 785 ::= { ospfv3AsLsdbEntry 5 } 787 ospfv3AsLsdbChecksum OBJECT-TYPE 788 SYNTAX Integer32 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 "This field is the checksum of the complete 793 contents of the advertisement, excepting the 794 age field. The age field is excepted so that 795 an advertisement's age can be incremented 796 without updating the checksum. The checksum 797 used is the same that is used for ISO connec- 798 tionless datagrams; it is commonly referred to 799 as the Fletcher checksum." 800 REFERENCE 801 "OSPF Version 2, Section 12.1.7 LS checksum" 802 ::= { ospfv3AsLsdbEntry 6 } 804 ospfv3AsLsdbAdvertisement OBJECT-TYPE 805 SYNTAX OCTET STRING (SIZE (1..65535)) 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "The entire Link State Advertisement, including 810 its header." 811 ::= { ospfv3AsLsdbEntry 7 } 813 -- OSPFv3 Area-Scope Link State Database 815 -- The Link State Database contains the Area-Scope Link State 816 -- Advertisements from throughout the area that the 817 -- device is attached to. 819 ospfv3AreaLsdbTable OBJECT-TYPE 820 SYNTAX SEQUENCE OF Ospfv3AreaLsdbEntry 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 "The OSPFv3 Process's Area-Scope Link State Database." 825 ::= { ospfv3 4 } 827 ospfv3AreaLsdbEntry OBJECT-TYPE 828 SYNTAX Ospfv3AreaLsdbEntry 829 MAX-ACCESS not-accessible 830 STATUS current 831 DESCRIPTION 832 "A single Area-Scope Link State Advertisement." 833 INDEX { ospfv3AreaLsdbAreaId, 834 ospfv3AreaLsdbType, 835 ospfv3AreaLsdbRouterId, 836 ospfv3AreaLsdbLsid } 837 ::= { ospfv3AreaLsdbTable 1 } 839 Ospfv3AreaLsdbEntry ::= 840 SEQUENCE { 841 ospfv3AreaLsdbAreaId 842 AreaID, 843 ospfv3AreaLsdbType 844 INTEGER, 845 ospfv3AreaLsdbRouterId 846 RouterID, 847 ospfv3AreaLsdbLsid 848 IpAddress, 849 ospfv3AreaLsdbSequence 850 Integer32, 851 ospfv3AreaLsdbAge 852 Integer32, 853 ospfv3AreaLsdbChecksum 854 Integer32, 855 ospfv3AreaLsdbAdvertisement 856 OCTET STRING 857 } 859 ospfv3AreaLsdbAreaId OBJECT-TYPE 860 SYNTAX AreaID 861 ACCESS read-only 862 STATUS mandatory 863 DESCRIPTION 864 "'The 32 bit identifier of the Area from which the LSA 865 was received.' 866 REFERENCE 867 'OSPF Version 2, Appendix C.2 Area parameters'" 868 ::= { ospfv3AreaLsdbEntry 1 } 870 ospfv3AreaLsdbType OBJECT-TYPE 871 SYNTAX INTEGER { 872 routerLsa (8193) -- 0x2001 873 networkLsa (8194) -- 0x2002 874 interAreaPrefixLsa (8195) -- 0x2003 875 interAreaRouterLsa (8196) -- 0x2004 876 groupMembershipLsa (8198) -- 0x2006 877 nssaExternalLsa (8199) -- 0x2007 878 intraAreaPrefixLsa (8201) -- 0x2009 879 } 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The type of the link state advertisement. 884 Each link state type has a separate advertise- 885 ment format. Unrecognized Area-Scope LSAs with 886 the U-bit set are also stored in this database." 887 ::= { ospfv3AreaLsdbEntry 1 } 889 ospfv3AreaLsdbRouterId OBJECT-TYPE 890 SYNTAX RouterID 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "The 32 bit number that uniquely identifies the 895 originating router in the Autonomous System." 896 REFERENCE 897 "OSPF Version 2, Appendix C.1 Global parameters" 898 ::= { ospfv3AreaLsdbEntry 2 } 900 ospfv3AreaLsdbLsid OBJECT-TYPE 901 SYNTAX IpAddress 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "The Link State ID is an LS Type Specific field 906 containing either a Router ID or a unique identifier; 907 it identifies the piece of the routing domain 908 that is being described by the advertisement. 909 In contrast to OSPF for IPv4, the LSID has no 910 addressing semantics." 911 ::= { ospfv3AreaLsdbEntry 3 } 913 -- Note that the OSPF Sequence Number is a 32 bit signed 914 -- integer. It starts with the value '80000001'h, 915 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 916 -- Thus, a typical sequence number will be very negative. 918 ospfv3AreaLsdbSequence OBJECT-TYPE 919 SYNTAX Integer32 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "The sequence number field is a signed 32-bit 924 integer. It is used to detect old and dupli- 925 cate link state advertisements. The space of 926 sequence numbers is linearly ordered. The 927 larger the sequence number the more recent the 928 advertisement." 929 REFERENCE 930 "OSPF Version 2, Section 12.1.6 LS sequence 931 number" 932 ::= { ospfv3AreaLsdbEntry 4 } 934 ospfv3AreaLsdbAge OBJECT-TYPE 935 SYNTAX Integer32 -- Should be 0..MaxAge 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "This field is the age of the link state adver- 940 tisement in seconds." 941 REFERENCE 942 "OSPF Version 2, Section 12.1.1 LS age" 943 ::= { ospfv3AreaLsdbEntry 5 } 945 ospfv3AreaLsdbChecksum OBJECT-TYPE 946 SYNTAX Integer32 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "This field is the checksum of the complete 951 contents of the advertisement, excepting the 952 age field. The age field is excepted so that 953 an advertisement's age can be incremented 954 without updating the checksum. The checksum 955 used is the same that is used for ISO connec- 956 tionless datagrams; it is commonly referred to 957 as the Fletcher checksum." 959 REFERENCE 960 "OSPF Version 2, Section 12.1.7 LS checksum" 961 ::= { ospfv3AreaLsdbEntry 6 } 963 ospfv3AreaLsdbAdvertisement OBJECT-TYPE 964 SYNTAX OCTET STRING (SIZE (1..65535)) 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "The entire Link State Advertisement, including 969 its header." 970 ::= { ospfv3AreaLsdbEntry 7 } 972 -- OSPFv3 Link-Scope Link State Database 974 -- The Link State Database contains the Link-Scope Link State 975 -- Advertisements from the links that the 976 -- device is attached to. 978 ospfv3LinkLsdbTable OBJECT-TYPE 979 SYNTAX SEQUENCE OF Ospfv3LinkLsdbEntry 980 MAX-ACCESS not-accessible 981 STATUS current 982 DESCRIPTION 983 "The OSPFv3 Process's Link-Scope Link State Database." 984 ::= { ospfv3 5 } 986 ospfv3LinkLsdbEntry OBJECT-TYPE 987 SYNTAX Ospfv3LinkLsdbEntry 988 MAX-ACCESS not-accessible 989 STATUS current 990 DESCRIPTION 991 "A single Link-Scope Link State Advertisement." 992 INDEX { ospfv3LinkLsdbIfindex, 993 ospfv3LinkLsdbType, 994 ospfv3LinkLsdbRouterId, 995 ospfv3LinkLsdbLsid } 996 ::= { ospfv3LinkLsdbTable 1 } 998 Ospfv3LinkLsdbEntry ::= 999 SEQUENCE { 1000 ospfv3LinkLsdbIfIndex 1001 Ipv6IfIndex, 1002 ospfv3LinkLsdbType 1003 INTEGER, 1004 ospfv3LinkLsdbRouterId 1005 RouterID, 1006 ospfv3LinkLsdbLsid 1007 IpAddress, 1008 ospfv3LinkLsdbSequence 1009 Integer32, 1010 ospfv3LinkLsdbAge 1011 Integer32, 1012 ospfv3LinkLsdbChecksum 1013 Integer32, 1014 ospfv3LinkLsdbAdvertisement 1015 OCTET STRING 1016 } 1018 ospfv3LinkLsdbIfindex OBJECT-TYPE 1019 SYNTAX Ipv6IfIndex 1020 ACCESS read-only 1021 STATUS mandatory 1022 DESCRIPTION 1023 "'The identifier of the link from which the LSA 1024 was received.' 1025 REFERENCE 1026 'OSPF Version 2, Appendix C.2 Area parameters'" 1027 ::= { ospfv3LinkLsdbEntry 1 } 1029 ospfv3LinkLsdbType OBJECT-TYPE 1030 SYNTAX INTEGER { 1031 linkLsa (8) -- 0x0008 1032 } 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "The type of the link state advertisement. 1037 Each link state type has a separate advertise- 1038 ment format. Unrecognized Link-Scope LSAs with 1039 the U-bit set are also stored in this database." 1040 ::= { ospfv3LinkLsdbEntry 2 } 1042 ospfv3LinkLsdbRouterId OBJECT-TYPE 1043 SYNTAX RouterID 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "The 32 bit number that uniquely identifies the 1048 originating router in the Autonomous System." 1049 REFERENCE 1050 "OSPF Version 2, Appendix C.1 Global parameters" 1051 ::= { ospfv3LinkLsdbEntry 3 } 1053 ospfv3LinkLsdbLsid OBJECT-TYPE 1054 SYNTAX IpAddress 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "The Link State ID is an LS Type Specific field 1059 containing either a Router ID or a unique identifier; 1060 it identifies the piece of the routing domain 1061 that is being described by the advertisement. 1062 In contrast to OSPF for IPv4, the LSID has no 1063 addressing semantics." 1064 ::= { ospfv3LinkLsdbEntry 4 } 1066 -- Note that the OSPF Sequence Number is a 32 bit signed 1067 -- integer. It starts with the value '80000001'h, 1068 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1069 -- Thus, a typical sequence number will be very negative. 1071 ospfv3LinkLsdbSequence OBJECT-TYPE 1072 SYNTAX Integer32 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "The sequence number field is a signed 32-bit 1077 integer. It is used to detect old and dupli- 1078 cate link state advertisements. The space of 1079 sequence numbers is linearly ordered. The 1080 larger the sequence number the more recent the 1081 advertisement." 1082 REFERENCE 1083 "OSPF Version 2, Section 12.1.6 LS sequence 1084 number" 1085 ::= { ospfv3LinkLsdbEntry 5 } 1087 ospfv3LinkLsdbAge OBJECT-TYPE 1088 SYNTAX Integer32 -- Should be 0..MaxAge 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "This field is the age of the link state adver- 1093 tisement in seconds." 1094 REFERENCE 1095 "OSPF Version 2, Section 12.1.1 LS age" 1096 ::= { ospfv3LinkLsdbEntry 6 } 1098 ospfv3LinkLsdbChecksum OBJECT-TYPE 1099 SYNTAX Integer32 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "This field is the checksum of the complete 1104 contents of the advertisement, excepting the 1105 age field. The age field is excepted so that 1106 an advertisement's age can be incremented 1107 without updating the checksum. The checksum 1108 used is the same that is used for ISO connec- 1109 tionless datagrams; it is commonly referred to 1110 as the Fletcher checksum." 1111 REFERENCE 1112 "OSPF Version 2, Section 12.1.7 LS checksum" 1113 ::= { ospfv3LinkLsdbEntry 7 } 1115 ospfv3LinkLsdbAdvertisement OBJECT-TYPE 1116 SYNTAX OCTET STRING (SIZE (1..65535)) 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "The entire Link State Advertisement, including 1121 its header." 1122 ::= { ospfv3LinkLsdbEntry 8 } 1124 -- OSPF Host Table 1126 -- The Host/Metric Table indicates what hosts are directly 1127 -- attached to the Router, and what metrics and types of 1128 -- service should be advertised for them. 1130 ospfv3HostTable OBJECT-TYPE 1131 SYNTAX SEQUENCE OF OspfHostEntry 1132 MAX-ACCESS not-accessible 1133 STATUS current 1134 DESCRIPTION 1135 "The list of Hosts, and their metrics, that the 1136 router will advertise as host routes." 1137 REFERENCE 1138 "OSPF Version 2, Appendix C.6 Host route param- 1139 eters" 1140 ::= { ospfv3 6 } 1142 ospfv3HostEntry OBJECT-TYPE 1143 SYNTAX Ospfv3HostEntry 1144 MAX-ACCESS not-accessible 1145 STATUS current 1146 DESCRIPTION 1147 "A metric to be advertised when a given host is reachable." 1148 INDEX { ospfv3HostIpv6Address } 1149 ::= { ospfv3HostTable 1 } 1151 Ospfv3HostEntry ::= 1152 SEQUENCE { 1153 ospfv3HostIpv6Address 1154 Ipv6Address, 1155 ospfv3HostMetric 1156 Metric, 1157 ospfv3HostStatus 1158 RowStatus, 1159 ospfv3HostAreaID 1160 AreaID 1161 } 1163 ospfv3HostIpv6Address OBJECT-TYPE 1164 SYNTAX Ipv6Address 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "The IPv6 Address of the Host. Must be a Global 1169 or Site-local address." 1170 REFERENCE 1171 "OSPF Version 2, Appendix C.6 Host route parame- 1172 ters" 1174 ::= { ospfv3HostEntry 1 } 1176 ospfv3HostMetric OBJECT-TYPE 1177 SYNTAX Metric 1178 MAX-ACCESS read-create 1179 STATUS current 1180 DESCRIPTION 1181 "The Metric to be advertised." 1182 REFERENCE 1183 "OSPF Version 2, Appendix C.6 Host route parame- 1184 ters" 1185 ::= { ospfv3HostEntry 2 } 1187 ospfv3HostStatus OBJECT-TYPE 1188 SYNTAX RowStatus 1189 MAX-ACCESS read-create 1190 STATUS current 1191 DESCRIPTION 1192 "This variable displays the status of the en- 1193 try. Setting it to 'invalid' has the effect of 1194 rendering it inoperative. The internal effect 1195 (row removal) is implementation dependent." 1196 ::= { ospfv3HostEntry 3 } 1198 ospfv3HostAreaID OBJECT-TYPE 1199 SYNTAX AreaID 1200 MAX-ACCESS read-only 1201 STATUS current 1202 DESCRIPTION 1203 "The Area the Host Entry is to be found within. 1204 By default, the area that a subsuming OSPFv3 in- 1205 terface is in, or 0.0.0.0" 1206 REFERENCE 1207 "OSPF Version 2, Appendix C.2 Area parameters" 1208 ::= { ospfv3HostEntry 4 } 1210 -- OSPFv3 Interface Table 1212 ospfv3IfTable OBJECT-TYPE 1213 SYNTAX SEQUENCE OF Ospfv3IfEntry 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "The OSPFv3 Interface Table describes the inter- 1218 faces from the viewpoint of OSPFv3." 1219 REFERENCE 1220 "OSPF Version 2, Appendix C.3 Router interface 1221 parameters" 1222 ::= { ospfv3 7 } 1224 ospfv3IfEntry OBJECT-TYPE 1225 SYNTAX Ospfv3IfEntry 1226 MAX-ACCESS not-accessible 1227 STATUS current 1228 DESCRIPTION 1229 "The OSPFv3 Interface Entry describes one inter- 1230 face from the viewpoint of OSPFv3." 1231 INDEX { ospfv3IfIndex } 1232 ::= { ospfv3IfTable 1 } 1234 Ospfv3IfEntry ::= 1235 SEQUENCE { 1236 ospfv3IfIndex 1237 Ipv6IfIndex, 1238 ospfv3IfAreaId 1239 AreaID, 1240 ospfv3IfType 1241 INTEGER, 1242 ospfv3IfAdminStat 1243 Status, 1244 ospfv3IfRtrPriority 1245 DesignatedRouterPriority, 1246 ospfv3IfTransitDelay 1247 UpToMaxAge, 1248 ospfv3IfRetransInterval 1249 UpToMaxAge, 1250 ospfv3IfHelloInterval 1251 HelloRange, 1252 ospfv3IfRtrDeadInterval 1253 PositiveInteger, 1254 ospfv3IfPollInterval 1255 PositiveInteger, 1256 ospfv3IfState 1257 INTEGER, 1258 ospfv3IfDesignatedRouter 1259 RouterID, 1261 ospfv3IfBackupDesignatedRouter 1262 RouterID, 1263 ospfv3IfEvents 1264 Counter32, 1265 ospfv3IfStatus 1266 RowStatus, 1267 ospfv3IfMulticastForwarding 1268 INTEGER, 1269 ospfv3IfDemand 1270 TruthValue, 1271 ospfv3IfMetricValue 1272 Metric, 1273 ospfv3IfLinkScopeLsaCount 1274 Gauge32, 1275 ospfv3IfLinkLsaCksumSum 1276 Integer32, 1277 ospfv3IfInstId 1278 Integer32 1279 } 1281 ospfv3IfIndex OBJECT-TYPE 1282 SYNTAX Ipv6IfIndex 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "The interface index of this OSPFv3 interface. 1287 It corresponds to the interface index of the 1288 Ipv6 interface on which OSPFv3 is configured." 1289 ::= { ospfv3IfEntry 1 } 1291 ospfv3IfAreaId OBJECT-TYPE 1292 SYNTAX AreaID 1293 MAX-ACCESS read-create 1294 STATUS current 1295 DESCRIPTION 1296 "A 32-bit integer uniquely identifying the area 1297 to which the interface connects. Area ID 1298 0.0.0.0 is used for the OSPFv3 backbone." 1299 DEFVAL { '00000000'H } -- 0.0.0.0 1300 ::= { ospfv3IfEntry 2 } 1302 ospfv3IfType OBJECT-TYPE 1303 SYNTAX INTEGER { 1304 broadcast (1), 1305 nbma (2), 1306 pointToPoint (3), 1307 pointToMultipoint (5) 1308 } 1309 MAX-ACCESS read-create 1310 STATUS current 1311 DESCRIPTION 1312 "The OSPFv3 interface type." 1313 ::= { ospfv3IfEntry 3 } 1315 ospfv3IfAdminStat OBJECT-TYPE 1316 SYNTAX Status 1317 MAX-ACCESS read-create 1318 STATUS current 1319 DESCRIPTION 1320 "The OSPFv3 interface's administrative status. 1321 The value formed on the interface, and the in- 1322 terface will be advertised as an internal route 1323 to some area. The value 'disabled' denotes 1324 that the interface is external to OSPFv3." 1325 DEFVAL { enabled } 1326 ::= { ospfv3IfEntry 4 } 1328 ospfv3IfRtrPriority OBJECT-TYPE 1329 SYNTAX DesignatedRouterPriority 1330 MAX-ACCESS read-create 1331 STATUS current 1332 DESCRIPTION 1333 "The priority of this interface. Used in 1334 multi-access networks, this field is used in 1335 the designated router election algorithm. The 1336 value 0 signifies that the router is not eligi- 1337 ble to become the designated router on this 1338 particular network. In the event of a tie in 1339 this value, routers will use their Router ID as 1340 a tie breaker." 1341 DEFVAL { 1 } 1342 ::= { ospfv3IfEntry 5 } 1344 ospfv3IfTransitDelay OBJECT-TYPE 1345 SYNTAX UpToMaxAge 1346 MAX-ACCESS read-create 1347 STATUS current 1348 DESCRIPTION 1349 "The estimated number of seconds it takes to 1350 transmit a link state update packet over this 1351 interface." 1352 DEFVAL { 1 } 1353 ::= { ospfv3IfEntry 6 } 1355 ospfv3IfRetransInterval OBJECT-TYPE 1356 SYNTAX UpToMaxAge 1357 MAX-ACCESS read-create 1358 STATUS current 1359 DESCRIPTION 1360 "The number of seconds between link-state ad- 1361 vertisement retransmissions, for adjacencies 1362 belonging to this interface. This value is 1363 also used when retransmitting database descrip- 1364 tion and link-state request packets." 1365 DEFVAL { 5 } 1366 ::= { ospfv3IfEntry 7 } 1368 ospfv3IfHelloInterval OBJECT-TYPE 1369 SYNTAX HelloRange 1370 MAX-ACCESS read-create 1371 STATUS current 1372 DESCRIPTION 1373 "The length of time, in seconds, between the 1374 Hello packets that the router sends on the in- 1375 terface. This value must be the same for all 1376 routers attached to a common network." 1377 DEFVAL { 10 } 1378 ::= { ospfv3IfEntry 8 } 1380 ospfv3IfRtrDeadInterval OBJECT-TYPE 1381 SYNTAX PositiveInteger 1382 MAX-ACCESS read-create 1383 STATUS current 1384 DESCRIPTION 1385 "The number of seconds that a router's Hello 1386 packets have not been seen before it's neigh- 1387 bors declare the router down. This should be 1388 some multiple of the Hello interval. This 1389 value must be the same for all routers attached 1390 to a common network." 1391 DEFVAL { 40 } 1392 ::= { ospfv3IfEntry 9 } 1394 ospfv3IfPollInterval OBJECT-TYPE 1395 SYNTAX PositiveInteger 1396 MAX-ACCESS read-create 1397 STATUS current 1398 DESCRIPTION 1399 "The larger time interval, in seconds, between 1400 the Hello packets sent to an inactive non- 1401 broadcast multi- access neighbor." 1402 DEFVAL { 120 } 1403 ::= { ospfv3IfEntry 10 } 1405 ospfv3IfState OBJECT-TYPE 1406 SYNTAX INTEGER { 1407 down (1), 1408 loopback (2), 1409 waiting (3), 1410 pointToPoint (4), 1411 designatedRouter (5), 1412 backupDesignatedRouter (6), 1413 otherDesignatedRouter (7) 1414 } 1415 MAX-ACCESS read-only 1416 STATUS current 1417 DESCRIPTION 1418 "The OSPFv3 Interface State." 1419 DEFVAL { down } 1420 ::= { ospfv3IfEntry 11 } 1422 ospfv3IfDesignatedRouter OBJECT-TYPE 1423 SYNTAX RouterID 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "The Router ID of the Designated Router." 1428 DEFVAL { '00000000'H } -- 0.0.0.0 1429 ::= { ospfv3IfEntry 12 } 1431 ospfv3IfBackupDesignatedRouter OBJECT-TYPE 1432 SYNTAX RouterID 1433 MAX-ACCESS read-only 1434 STATUS current 1435 DESCRIPTION 1436 "The Router ID of the Backup Designated 1437 Router." 1438 DEFVAL { '00000000'H } -- 0.0.0.0 1439 ::= { ospfv3IfEntry 14 } 1441 ospfv3IfEvents OBJECT-TYPE 1442 SYNTAX Counter32 1443 MAX-ACCESS read-only 1444 STATUS current 1445 DESCRIPTION 1446 "The number of times this OSPF interface has 1447 changed its state, or an error has occurred." 1448 ::= { ospfv3IfEntry 15 } 1450 ospfv3IfStatus OBJECT-TYPE 1451 SYNTAX RowStatus 1452 MAX-ACCESS read-create 1453 STATUS current 1454 DESCRIPTION 1455 "This variable displays the status of the en- 1456 try. Setting it to 'invalid' has the effect of 1457 rendering it inoperative. The internal effect 1458 (row removal) is implementation dependent." 1459 ::= { ospfv3IfEntry 17 } 1461 ospfv3IfMulticastForwarding OBJECT-TYPE 1462 SYNTAX INTEGER { 1463 blocked (1), -- no multicast forwarding 1464 multicast (2), -- using multicast address 1465 unicast (3) -- to each OSPFv3 neighbor 1466 } 1467 MAX-ACCESS read-create 1468 STATUS current 1469 DESCRIPTION 1470 "The way multicasts should forwarded on this 1471 interface; not forwarded, forwarded as data 1472 link multicasts, or forwarded as data link uni- 1473 casts. Data link multicasting is not meaning- 1474 ful on point to point and NBMA interfaces, and 1475 setting ospfv3MulticastForwarding to 0 effective- 1476 ly disables all multicast forwarding." 1477 DEFVAL { blocked } 1478 ::= { ospfv3IfEntry 18 } 1480 ospfv3IfDemand OBJECT-TYPE 1481 SYNTAX TruthValue 1482 MAX-ACCESS read-create 1483 STATUS current 1484 DESCRIPTION 1485 "Indicates whether Demand OSPFv3 procedures (hel- 1486 lo supression to FULL neighbors and setting the 1487 DoNotAge flag on proogated LSAs) should be per- 1488 formed on this interface." 1489 DEFVAL { false } 1490 ::= { ospfv3IfEntry 19 } 1492 ospfv3IfMetricValue OBJECT-TYPE 1493 SYNTAX Metric 1494 MAX-ACCESS read-create 1495 STATUS current 1496 DESCRIPTION 1497 "The metric assigned to this interface. 1498 The default value of the Metric is 1499 10^8 / ifSpeed." 1500 ::= { ospfv3IfEntry 20 } 1502 ospfv3IfLinkScopeLsaCount OBJECT-TYPE 1503 SYNTAX Gauge32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "The total number of Link-Scope link-state advertisements 1508 in this link's link-state database." 1509 ::= { ospfv3IfEntry 21 } 1511 ospfv3IfLinkLsaCksumSum OBJECT-TYPE 1512 SYNTAX Integer32 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "The 32-bit unsigned sum of the Link-Scope link-state 1517 advertisements' LS checksums contained in this 1518 link's link-state database. The sum can be used 1519 to determine if there has been a change in a 1520 router's link state database, and to compare the 1521 link-state database of two routers." 1522 DEFVAL { 0 } 1523 ::= { ospfv3IfEntry 22 } 1525 ospfv3IfInstId OBJECT-TYPE 1526 SYNTAX Integer32 1527 MAX-ACCESS read-create 1528 STATUS current 1529 DESCRIPTION 1530 "Enables multiple instances of OSPFv3 to be run over 1531 a single link. Each protocol instance would be assigned 1532 a separate ID. This ID has local link significance only." 1533 DEFVAL { 0 } 1534 ::= { ospfv3IfEntry 23 } 1536 -- OSPFv3 Virtual Interface Table 1538 -- The Virtual Interface Table describes the virtual 1539 -- links that the OSPFv3 Process is configured to 1540 -- carry on. 1542 ospfv3VirtIfTable OBJECT-TYPE 1543 SYNTAX SEQUENCE OF Ospfv3VirtIfEntry 1544 MAX-ACCESS not-accessible 1545 STATUS current 1546 DESCRIPTION 1547 "Information about this router's virtual inter- 1548 faces." 1549 REFERENCE 1550 "OSPF Version 2, Appendix C.4 Virtual link 1551 parameters" 1552 ::= { ospfv3 8 } 1554 ospfv3VirtIfEntry OBJECT-TYPE 1555 SYNTAX Ospfv3VirtIfEntry 1556 MAX-ACCESS not-accessible 1557 STATUS current 1558 DESCRIPTION 1559 "Information about a single Virtual Interface." 1560 INDEX { ospfv3VirtIfAreaId, ospfv3VirtIfNeighbor } 1561 ::= { ospfv3VirtIfTable 1 } 1563 Ospfv3VirtIfEntry ::= 1564 SEQUENCE { 1565 ospfv3VirtIfAreaId 1566 AreaID, 1567 ospfv3VirtIfNeighbor 1568 RouterID, 1569 ospfv3VirtIfIndex 1570 Ipv6IfIndex, 1571 ospfv3VirtIfTransitDelay 1572 UpToMaxAge, 1573 ospfv3VirtIfRetransInterval 1574 UpToMaxAge, 1575 ospfv3VirtIfHelloInterval 1576 HelloRange, 1577 ospfv3VirtIfRtrDeadInterval 1578 PositiveInteger, 1579 ospfv3VirtIfState 1580 INTEGER, 1581 ospfv3VirtIfEvents 1582 Counter32, 1583 ospfv3VirtIfStatus 1584 RowStatus, 1585 ospfv3VirtIfLinkScopeLsaCount 1586 Gauge32, 1587 ospfv3VirtIfLinkLsaCksumSum 1588 Integer32 1589 } 1591 ospfv3VirtIfAreaId OBJECT-TYPE 1592 SYNTAX AreaID 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "The Transit Area that the Virtual Link 1597 traverses. By definition, this is not 0.0.0.0" 1598 ::= { ospfv3VirtIfEntry 1 } 1600 ospfv3VirtIfNeighbor OBJECT-TYPE 1601 SYNTAX RouterID 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "The Router ID of the Virtual Neighbor." 1606 ::= { ospfv3VirtIfEntry 2 } 1608 ospfv3VirtIfIndex OBJECT-TYPE 1609 SYNTAX Ipv6IfIndex 1610 MAX-ACCESS read-create 1611 STATUS current 1612 DESCRIPTION 1613 "The interface index of this OSPFv3 virtual interface. 1614 It must be unique among all the interface indices 1615 on the router." 1616 ::= { ospfv3IfEntry 3 } 1618 ospfv3VirtIfTransitDelay OBJECT-TYPE 1619 SYNTAX UpToMaxAge 1620 MAX-ACCESS read-create 1621 STATUS current 1622 DESCRIPTION 1623 "The estimated number of seconds it takes to 1624 transmit a link- state update packet over this 1625 interface." 1626 DEFVAL { 1 } 1627 ::= { ospfv3VirtIfEntry 4 } 1629 ospfv3VirtIfRetransInterval OBJECT-TYPE 1630 SYNTAX UpToMaxAge 1631 MAX-ACCESS read-create 1632 STATUS current 1633 DESCRIPTION 1634 "The number of seconds between link-state ad- 1635 vertisement retransmissions, for adjacencies 1636 belonging to this interface. This value is 1637 also used when retransmitting database descrip- 1638 tion and link-state request packets. This 1639 value should be well over the expected round- 1640 trip time." 1641 DEFVAL { 5 } 1642 ::= { ospfv3VirtIfEntry 5 } 1644 ospfv3VirtIfHelloInterval OBJECT-TYPE 1645 SYNTAX HelloRange 1646 MAX-ACCESS read-create 1647 STATUS current 1648 DESCRIPTION 1649 "The length of time, in seconds, between the 1650 Hello packets that the router sends on the in- 1651 terface. This value must be the same for the 1652 virtual neighbor." 1653 DEFVAL { 10 } 1654 ::= { ospfv3VirtIfEntry 6 } 1656 ospfv3VirtIfRtrDeadInterval OBJECT-TYPE 1657 SYNTAX PositiveInteger 1658 MAX-ACCESS read-create 1659 STATUS current 1660 DESCRIPTION 1661 "The number of seconds that a router's Hello 1662 packets have not been seen before it's neigh- 1663 bors declare the router down. This should be 1664 some multiple of the Hello interval. This 1665 value must be the same for the virtual neigh- 1666 bor." 1667 DEFVAL { 60 } 1668 ::= { ospfv3VirtIfEntry 7 } 1670 ospfv3VirtIfState OBJECT-TYPE 1671 SYNTAX INTEGER { 1672 down (1), -- these use the same encoding 1673 pointToPoint (4) -- as the ospfv3IfTable 1674 } 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "OSPF virtual interface states." 1679 DEFVAL { down } 1680 ::= { ospfv3VirtIfEntry 8 } 1682 ospfv3VirtIfEvents OBJECT-TYPE 1683 SYNTAX Counter32 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "The number of state changes or error events on 1688 this Virtual Link" 1689 ::= { ospfv3VirtIfEntry 9 } 1691 ospfv3VirtIfStatus OBJECT-TYPE 1692 SYNTAX RowStatus 1693 MAX-ACCESS read-create 1694 STATUS current 1695 DESCRIPTION 1696 "This variable displays the status of the en- 1697 try. Setting it to 'invalid' has the effect of 1698 rendering it inoperative. The internal effect 1699 (row removal) is implementation dependent." 1700 ::= { ospfv3VirtIfEntry 10 } 1702 ospfv3VirtIfLinkScopeLsaCount OBJECT-TYPE 1703 SYNTAX Gauge32 1704 MAX-ACCESS read-only 1705 STATUS current 1706 DESCRIPTION 1707 "The total number of Link-Scope link-state advertisements 1708 in this virtual link's link-state database." 1709 ::= { ospfv3IfEntry 11 } 1711 ospfv3VirtIfLinkLsaCksumSum OBJECT-TYPE 1712 SYNTAX Integer32 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "The 32-bit unsigned sum of the Link-Scope link-state 1717 advertisements' LS checksums contained in this 1718 virtual link's link-state database. The sum can be used 1719 to determine if there has been a change in a 1720 router's link state database, and to compare the 1721 link-state database of two routers." 1722 DEFVAL { 0 } 1723 ::= { ospfv3IfEntry 12 } 1725 -- OSPFv3 Neighbor Table 1726 -- The OSPFv3 Neighbor Table describes all neighbors in 1727 -- the locality of the subject router. 1729 ospfv3NbrTable OBJECT-TYPE 1730 SYNTAX SEQUENCE OF Ospfv3NbrEntry 1731 MAX-ACCESS not-accessible 1732 STATUS current 1733 DESCRIPTION 1734 "A table of non-virtual neighbor information." 1735 REFERENCE 1736 "OSPF Version 2, Section 10 The Neighbor Data 1737 Structure" 1738 ::= { ospfv3 9 } 1740 ospfv3NbrEntry OBJECT-TYPE 1741 SYNTAX Ospfv3NbrEntry 1742 MAX-ACCESS not-accessible 1743 STATUS current 1744 DESCRIPTION 1745 "The information regarding a single neighbor." 1746 REFERENCE 1747 "OSPF Version 2, Section 10 The Neighbor Data 1748 Structure" 1749 INDEX { ospfv3NbrIfIndex, ospfv3NbrRtrId } 1750 ::= { ospfv3NbrTable 1 } 1752 Ospfv3NbrEntry ::= 1753 SEQUENCE { 1754 ospfv3NbrIfIndex 1755 Ipv6IfIndex, 1756 ospfv3NbrRtrId 1757 RouterID, 1758 ospfv3NbrOptions 1759 Integer32, 1760 ospfv3NbrPriority 1761 DesignatedRouterPriority, 1762 ospfv3NbrState 1763 INTEGER, 1764 ospfv3NbrEvents 1765 Counter32, 1766 ospfv3NbrLsRetransQLen 1767 Gauge32, 1768 ospfv3NbmaNbrStatus 1769 RowStatus, 1771 ospfv3NbmaNbrPermanence 1772 INTEGER, 1773 ospfv3NbrHelloSuppressed 1774 TruthValue, 1775 ospfv3NbrIfId 1776 Ipv6IfIndex 1777 } 1779 ospfv3NbrIfIndex OBJECT-TYPE 1780 SYNTAX Ipv6IfIndex 1781 MAX-ACCESS read-only 1782 STATUS current 1783 DESCRIPTION 1784 "The local link ID of the link over which the 1785 neighbor can be reached." 1786 ::= { ospfv3NbrEntry 1 } 1788 ospfv3NbrRtrId OBJECT-TYPE 1789 SYNTAX RouterID 1790 MAX-ACCESS read-only 1791 STATUS current 1792 DESCRIPTION 1793 "A 32-bit integer (represented as a type IpAd- 1794 dress) uniquely identifying the neighboring 1795 router in the Autonomous System." 1796 DEFVAL { '00000000'H } -- 0.0.0.0 1797 ::= { ospfv3NbrEntry 2 } 1799 ospfv3NbrOptions OBJECT-TYPE 1800 SYNTAX Integer32 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "A Bit Mask corresponding to the neighbor's op- 1805 tions field. 1806 DEFVAL { 0 } 1807 ::= { ospfv3NbrEntry 3 } 1809 ospfv3NbrPriority OBJECT-TYPE 1810 SYNTAX DesignatedRouterPriority 1811 MAX-ACCESS read-create 1812 STATUS current 1813 DESCRIPTION 1814 "The priority of this neighbor in the designat- 1815 ed router election algorithm. The value 0 sig- 1816 nifies that the neighbor is not eligible to be- 1817 come the designated router on this particular 1818 network." 1819 DEFVAL { 1 } 1820 ::= { ospfv3NbrEntry 4 } 1822 ospfv3NbrState OBJECT-TYPE 1823 SYNTAX INTEGER { 1824 down (1), 1825 attempt (2), 1826 init (3), 1827 twoWay (4), 1828 exchangeStart (5), 1829 exchange (6), 1830 loading (7), 1831 full (8) 1832 } 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "The State of the relationship with this Neigh- 1837 bor." 1838 REFERENCE 1839 "OSPF Version 2, Section 10.1 Neighbor States" 1840 DEFVAL { down } 1841 ::= { ospfv3NbrEntry 5 } 1843 ospfv3NbrEvents OBJECT-TYPE 1844 SYNTAX Counter32 1845 MAX-ACCESS read-only 1846 STATUS current 1847 DESCRIPTION 1848 "The number of times this neighbor relationship 1849 has changed state, or an error has occurred." 1850 ::= { ospfv3NbrEntry 6 } 1852 ospfv3NbrLsRetransQLen OBJECT-TYPE 1853 SYNTAX Gauge32 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION 1857 "The current length of the retransmission 1858 queue." 1859 ::= { ospfv3NbrEntry 7 } 1861 ospfv3NbmaNbrStatus OBJECT-TYPE 1862 SYNTAX RowStatus 1863 MAX-ACCESS read-create 1864 STATUS current 1865 DESCRIPTION 1866 "This variable displays the status of the en- 1867 try. Setting it to 'invalid' has the effect of 1868 rendering it inoperative. The internal effect 1869 (row removal) is implementation dependent." 1870 ::= { ospfv3NbrEntry 8 } 1872 ospfv3NbmaNbrPermanence OBJECT-TYPE 1873 SYNTAX INTEGER { 1874 dynamic (1), -- learned through protocol 1875 permanent (2) -- configured address 1876 } 1877 MAX-ACCESS read-only 1878 STATUS current 1879 DESCRIPTION 1880 "This variable displays the status of the en- 1881 try. 'dynamic' and 'permanent' refer to how 1882 the neighbor became known." 1883 DEFVAL { permanent } 1884 ::= { ospfv3NbrEntry 9 } 1886 ospfv3NbrHelloSuppressed OBJECT-TYPE 1887 SYNTAX TruthValue 1888 MAX-ACCESS read-only 1889 STATUS current 1890 DESCRIPTION 1891 "Indicates whether Hellos are being suppressed 1892 to the neighbor" 1893 ::= { ospfv3NbrEntry 10 } 1895 ospfv3NbrIfId OBJECT-TYPE 1896 SYNTAX Ipv6IfIndex 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "The interface ID that the neighbor advertises 1901 in its Hello Packets on this link, that is, the 1902 neighbor's local interface index." 1903 ::= { ospfv3NbrEntry 11 } 1905 -- OSPFv3 Virtual Neighbor Table 1907 -- This table describes all virtual neighbors. 1908 -- Since Virtual Links are configured in the 1909 -- virtual interface table, this table is read-only. 1911 ospfv3VirtNbrTable OBJECT-TYPE 1912 SYNTAX SEQUENCE OF Ospfv3VirtNbrEntry 1913 MAX-ACCESS not-accessible 1914 STATUS current 1915 DESCRIPTION 1916 "A table of virtual neighbor information." 1917 REFERENCE 1918 "OSPF Version 2, Section 15 Virtual Links" 1919 ::= { ospfv3 10 } 1921 ospfv3VirtNbrEntry OBJECT-TYPE 1922 SYNTAX Ospfv3VirtNbrEntry 1924 MAX-ACCESS not-accessible 1925 STATUS current 1926 DESCRIPTION 1927 "Virtual neighbor information." 1928 INDEX { ospfv3VirtNbrArea, ospfv3VirtNbrRtrId } 1929 ::= { ospfv3VirtNbrTable 1 } 1931 Ospfv3VirtNbrEntry ::= 1932 SEQUENCE { 1933 ospfv3VirtNbrArea 1934 AreaID, 1935 ospfv3VirtNbrRtrId 1936 RouterID, 1937 ospfv3VirtNbrIfIndex 1938 Ipv6IfIndex, 1940 ospfv3VirtNbrIpv6Addr 1941 Ipv6Address, 1942 ospfv3VirtNbrOptions 1943 Integer32, 1944 ospfv3VirtNbrState 1945 INTEGER, 1946 ospfv3VirtNbrEvents 1947 Counter32, 1948 ospfv3VirtNbrLsRetransQLen 1949 Gauge32, 1950 ospfv3VirtNbrHelloSuppressed 1951 TruthValue, 1952 ospfv3VirtNbrIfId 1953 Ipv6IfIndex 1954 } 1956 ospfv3VirtNbrArea OBJECT-TYPE 1957 SYNTAX AreaID 1958 MAX-ACCESS read-only 1959 STATUS current 1960 DESCRIPTION 1961 "The Transit Area Identifier." 1962 ::= { ospfv3VirtNbrEntry 1 } 1964 ospfv3VirtNbrRtrId OBJECT-TYPE 1965 SYNTAX RouterID 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 "A 32-bit integer uniquely identifying the 1970 neighboring router in the Autonomous System." 1971 ::= { ospfv3VirtNbrEntry 2 } 1973 ospfv3VirtNbrIfIndex OBJECT-TYPE 1974 SYNTAX Ipv6IfIndex 1975 MAX-ACCESS read-only 1976 STATUS current 1977 DESCRIPTION 1978 "The local link ID for the virtual link over 1979 which the neighbor can be reached." 1980 ::= { ospfv3NbrEntry 3 } 1982 ospfv3VirtNbrIpv6Addr OBJECT-TYPE 1983 SYNTAX Ipv6Address 1984 MAX-ACCESS read-only 1985 STATUS current 1986 DESCRIPTION 1987 "The IPv6 address used to reach this Virtual Neighbor. 1988 It must be a Site-Local or Global scope address." 1989 ::= { ospfv3VirtNbrEntry 4 } 1991 ospfv3VirtNbrOptions OBJECT-TYPE 1992 SYNTAX Integer32 1993 MAX-ACCESS read-only 1994 STATUS current 1995 DESCRIPTION 1996 "A Bit Mask corresponding to the neighbor's op- 1997 tions field. 1998 ::= { ospfv3VirtNbrEntry 5 } 2000 ospfv3VirtNbrState OBJECT-TYPE 2001 SYNTAX INTEGER { 2002 down (1), 2003 attempt (2), 2004 init (3), 2005 twoWay (4), 2006 exchangeStart (5), 2007 exchange (6), 2008 loading (7), 2009 full (8) 2010 } 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "The state of the Virtual Neighbor Relation- 2015 ship." 2016 ::= { ospfv3VirtNbrEntry 6 } 2018 ospfv3VirtNbrEvents OBJECT-TYPE 2019 SYNTAX Counter32 2020 MAX-ACCESS read-only 2021 STATUS current 2022 DESCRIPTION 2023 "The number of times this virtual link has 2024 changed its state, or an error has occurred." 2025 ::= { ospfv3VirtNbrEntry 7 } 2027 ospfv3VirtNbrLsRetransQLen OBJECT-TYPE 2028 SYNTAX Gauge32 2029 MAX-ACCESS read-only 2030 STATUS current 2031 DESCRIPTION 2032 "The current length of the retransmission 2033 queue." 2034 ::= { ospfv3VirtNbrEntry 8 } 2036 ospfv3VirtNbrHelloSuppressed OBJECT-TYPE 2037 SYNTAX TruthValue 2038 MAX-ACCESS read-only 2039 STATUS current 2040 DESCRIPTION 2041 "Indicates whether Hellos are being suppressed 2042 to the neighbor" 2043 ::= { ospfv3VirtNbrEntry 9 } 2045 ospfv3VirtNbrIfId OBJECT-TYPE 2046 SYNTAX Ipv6IfIndex 2047 MAX-ACCESS read-only 2048 STATUS current 2049 DESCRIPTION 2050 "The interface ID that the neighbor advertises 2051 in its Hello Packets on this virtual link, that is, 2052 the neighbor's local interface index." 2053 ::= { ospfv3VirtNbrEntry 10 } 2055 -- 2056 -- The OSPFv3 Area Aggregate Table 2057 -- 2059 ospfv3AreaAggregateTable OBJECT-TYPE 2060 SYNTAX SEQUENCE OF Ospfv3AreaAggregateEntry 2061 MAX-ACCESS not-accessible 2062 STATUS current 2063 DESCRIPTION 2064 "A range of IPv6 prefixes specified by a 2065 prefix/prefix length pair. Note that if 2066 ranges are configured such that one range sub- 2067 sumes another range the most specific match is 2068 the preferred one." 2069 ::= { ospfv3 11 } 2071 ospfv3AreaAggregateEntry OBJECT-TYPE 2072 SYNTAX Ospfv3AreaAggregateEntry 2073 MAX-ACCESS not-accessible 2074 STATUS current 2075 DESCRIPTION 2076 "A range of IPv6 prefixes specified by a 2077 prefix/prefix length pair. Note that if 2078 ranges are configured such that one range sub- 2079 sumes another range the most specific match is 2080 the preferred one." 2081 REFERENCE 2082 "OSPF Version 2, Appendix C.2 Area parameters" 2083 INDEX { ospfv3AreaAggregateAreaID, ospfv3AreaAggregateAreaLsdbType, 2084 ospfv3AreaAggregateIndex } 2085 ::= { ospfv3AreaAggregateTable 1 } 2087 Ospfv3AreaAggregateEntry ::= 2088 SEQUENCE { 2089 ospfv3AreaAggregateAreaID 2090 AreaID, 2091 ospfv3AreaAggregateAreaLsdbType 2092 INTEGER, 2093 ospfv3AreaAggregateIndex 2094 INTEGER, 2095 ospfv3AreaAggregatePrefix 2096 Ipv6AddressPrefix, 2097 ospfv3AreaAggregatePrefixLen 2098 INTEGER, 2099 ospfv3AreaAggregateStatus 2100 RowStatus, 2101 ospfv3AreaAggregateEffect 2102 INTEGER 2103 } 2105 ospfv3AreaAggregateAreaID OBJECT-TYPE 2106 SYNTAX AreaID 2107 MAX-ACCESS read-only 2108 STATUS current 2109 DESCRIPTION 2110 "The Area the Address Aggregate is to be found 2111 within." 2112 REFERENCE 2113 "OSPF Version 2, Appendix C.2 Area parameters" 2114 ::= { ospfv3AreaAggregateEntry 1 } 2116 ospfv3AreaAggregateAreaLsdbType OBJECT-TYPE 2117 SYNTAX INTEGER { 2118 interAreaPrefixLsa (8195), -- 0x2003 2119 nssaExternalLsa (8199) -- 0x2007 2120 } 2121 MAX-ACCESS read-only 2122 STATUS current 2123 DESCRIPTION 2124 "The type of the Address Aggregate. This field 2125 specifies the Area Lsdb type that this Address Ag- 2126 gregate applies to." 2127 REFERENCE 2128 "OSPF Version 2, Appendix A.4.1 The Link State 2129 Advertisement header" 2130 ::= { ospfv3AreaAggregateEntry 2 } 2132 ospfv3AreaAggregateIndex OBJECT-TYPE 2133 SYNTAX INTEGER (1..2147483647) 2134 MAX-ACCESS read-only 2135 STATUS current 2136 DESCRIPTION 2137 "A unique identifier for this aggregate table entry." 2138 ::= { ospfv3AreaAggregateEntry 3 } 2140 ospfv3AreaAggregatePrefix OBJECT-TYPE 2141 SYNTAX Ipv6AddressPrefix 2142 MAX-ACCESS read-create 2143 STATUS current 2144 DESCRIPTION 2145 "The IPv6 Prefix." 2146 REFERENCE 2147 "OSPF Version 2, Appendix C.2 Area parameters" 2148 ::= { ospfv3AreaAggregateEntry 4 } 2150 ospfv3AreaAggregatePrefixLen OBJECT-TYPE 2151 SYNTAX INTEGER ( 3..128 ) 2152 UNITS "bits" 2153 MAX-ACCESS read-create 2154 STATUS current 2155 DESCRIPTION 2156 "The length of the prefix (in bits). A prefix can 2157 not be shorter than 3 bits." 2158 REFERENCE 2159 "OSPF Version 2, Appendix C.2 Area parameters" 2160 ::= { ospfv3AreaAggregateEntry 5 } 2162 ospfv3AreaAggregateStatus OBJECT-TYPE 2163 SYNTAX RowStatus 2164 MAX-ACCESS read-create 2165 STATUS current 2166 DESCRIPTION 2167 "This variable displays the status of the en- 2168 try. Setting it to 'invalid' has the effect of 2169 rendering it inoperative. The internal effect 2170 (row removal) is implementation dependent." 2171 ::= { ospfv3AreaAggregateEntry 6 } 2173 ospfv3AreaAggregateEffect OBJECT-TYPE 2174 SYNTAX INTEGER { 2175 advertiseMatching (1), 2176 doNotAdvertiseMatching (2) 2177 } 2178 MAX-ACCESS read-create 2179 STATUS current 2180 DESCRIPTION 2181 "Prefixes subsumed by ranges either trigger the 2182 advertisement of the indicated aggregate (ad- 2183 vertiseMatching), or result in the prefix not 2184 being advertised at all outside the area." 2185 DEFVAL { advertiseMatching } 2186 ::= { ospfv3AreaAggregateEntry 7 } 2188 -- conformance information 2190 ospfv3Conformance OBJECT IDENTIFIER ::= { ospfv3 12 } 2191 ospfv3Groups OBJECT IDENTIFIER ::= { ospfv3Conformance 1 } 2192 ospfv3Compliances OBJECT IDENTIFIER ::= { ospfv3Conformance 2 } 2194 -- compliance statements 2196 ospfv3Compliance MODULE-COMPLIANCE 2197 STATUS current 2198 DESCRIPTION 2199 "The compliance statement " 2200 MODULE -- this module 2201 MANDATORY-GROUPS { 2202 ospfv3BasicGroup, 2203 ospfv3AreaGroup, 2204 ospfv3IfGroup, 2205 ospfv3VirtIfGroup, 2206 ospfv3NbrGroup, 2207 ospfv3VirtNbrGroup, 2208 ospfv3AreaAggregateGroup 2209 } 2210 ::= { ospfv3Compliances 1 } 2212 -- units of conformance 2214 ospfv3BasicGroup OBJECT-GROUP 2215 OBJECTS { 2216 ospfv3RouterId, 2217 ospfv3AdminStat, 2218 ospfv3VersionNumber, 2219 ospfv3AreaBdrRtrStatus, 2220 ospfv3ASBdrRtrStatus, 2221 ospfv3AsScopeLsaCount, 2222 ospfv3AsScopeLsaCksumSum, 2223 ospfv3OriginateNewLsas, 2224 ospfv3RxNewLsas, 2225 ospfv3ExtAreaLsdbLimit, 2226 ospfv3MulticastExtensions, 2227 ospfv3ExitOverflowInterval, 2228 ospfv3DemandExtensions 2229 } 2230 STATUS current 2231 DESCRIPTION 2232 "These objects are required for OSPFv3 systems." 2233 ::= { ospfv3Groups 1 } 2235 ospfv3AreaGroup OBJECT-GROUP 2236 OBJECTS { 2237 ospfv3AreaId, 2238 ospfv3ImportAsExtern, 2239 ospfv3SpfRuns, 2240 ospfv3AreaBdrRtrCount, 2241 ospfv3AsBdrRtrCount, 2242 ospfv3AreaScopeLsaCount, 2243 ospfv3AreaScopeLsaCksumSum, 2244 ospfv3AreaSummary, 2245 ospfv3AreaStatus, 2246 ospfv3StubMetric 2247 } 2248 STATUS current 2249 DESCRIPTION 2250 "These objects are required for OSPFv3 systems 2251 supporting areas." 2252 ::= { ospfv3Groups 2 } 2254 ospfv3AsLsdbGroup OBJECT-GROUP 2255 OBJECTS { 2256 ospfv3AsLsdbType, 2257 ospfv3AsLsdbRouterId, 2258 ospfv3AsLsdbLsid, 2259 ospfv3AsLsdbSequence, 2260 ospfv3AsLsdbAge, 2261 ospfv3AsLsdbChecksum, 2262 ospfv3AsLsdbAdvertisement 2263 } 2264 STATUS current 2265 DESCRIPTION 2266 "These objects are required for OSPFv3 systems 2267 that display their AS-scope link state database." 2268 ::= { ospfv3Groups 3 } 2270 ospfv3AreaLsdbGroup OBJECT-GROUP 2271 OBJECTS { 2272 ospfv3AreaLsdbAreaId, 2273 ospfv3AreaLsdbType, 2274 ospfv3AreaLsdbRouterId, 2275 ospfv3AreaLsdbLsid, 2276 ospfv3AreaLsdbSequence, 2277 ospfv3AreaLsdbAge, 2278 ospfv3AreaLsdbChecksum, 2279 ospfv3AreaLsdbAdvertisement 2280 } 2281 STATUS current 2282 DESCRIPTION 2283 "These objects are required for OSPF6 systems 2284 that display their Area-scope link state database." 2285 ::= { ospfv3Groups 4 } 2287 ospfv3LinkLsdbGroup OBJECT-GROUP 2288 OBJECTS { 2289 ospfv3LinkLsdbIfIndex, 2290 ospfv3LinkLsdbType, 2291 ospfv3LinkLsdbRouterId, 2292 ospfv3LinkLsdbLsid, 2293 ospfv3LinkLsdbSequence, 2294 ospfv3LinkLsdbAge, 2295 ospfv3LinkLsdbChecksum, 2296 ospfv3LinkLsdbAdvertisement 2297 } 2298 STATUS current 2299 DESCRIPTION 2300 "These objects are required for OSPFv3 systems 2301 that display their Link-scope link state database." 2302 ::= { ospfv3Groups 5 } 2304 ospfv3HostGroup OBJECT-GROUP 2305 OBJECTS { 2306 ospfv3HostIpv6Address, 2307 ospfv3HostMetric, 2308 ospfv3HostStatus, 2309 ospfv3HostAreaID 2310 } 2311 STATUS current 2312 DESCRIPTION 2313 "These objects are required for OSPFv3 systems 2314 that support attached hosts." 2315 ::= { ospfv3Groups 6 } 2317 ospfv3IfGroup OBJECT-GROUP 2318 OBJECTS { 2319 ospfv3IfIndex, 2320 ospfv3IfAreaId, 2321 ospfv3IfType, 2322 ospfv3IfAdminStat, 2323 ospfv3IfRtrPriority, 2324 ospfv3IfTransitDelay, 2325 ospfv3IfRetransInterval, 2326 ospfv3IfHelloInterval, 2327 ospfv3IfRtrDeadInterval, 2328 ospfv3IfPollInterval, 2329 ospfv3IfState, 2330 ospfv3IfDesignatedRouter, 2331 ospfv3IfBackupDesignatedRouter, 2332 ospfv3IfEvents, 2333 ospfv3IfStatus, 2334 ospfv3IfMulticastForwarding, 2335 ospfv3IfDemand, 2336 ospfv3IfMetricValue, 2337 ospfv3IfLinkScopeLsaCount, 2338 ospfv3IfLinkLsaCksumSum, 2339 ospfv3IfInstId 2340 } 2341 STATUS current 2342 DESCRIPTION 2343 "These interface objects are required for OSPFv3 systems." 2344 ::= { ospfv3Groups 7 } 2346 ospfv3VirtIfGroup OBJECT-GROUP 2347 OBJECTS { 2348 ospfv3VirtIfAreaId, 2349 ospfv3VirtIfNeighbor, 2350 ospfv3VirtIfIndex, 2351 ospfv3VirtIfTransitDelay, 2352 ospfv3VirtIfRetransInterval, 2353 ospfv3VirtIfHelloInterval, 2354 ospfv3VirtIfRtrDeadInterval, 2355 ospfv3VirtIfState, 2356 ospfv3VirtIfEvents, 2357 ospfv3VirtIfStatus, 2358 ospfv3VirtIfLinkScopeLsaCount, 2359 ospfv3VirtIfLinkLsaCksumSum 2360 } 2361 STATUS current 2362 DESCRIPTION 2363 "These virtual interface objects are required for OSPFv3 systems." 2365 ::= { ospfv3Groups 8 } 2367 ospfv3NbrGroup OBJECT-GROUP 2368 OBJECTS { 2369 ospfv3NbrIfIndex, 2370 ospfv3NbrRtrId, 2371 ospfv3NbrOptions, 2372 ospfv3NbrPriority, 2373 ospfv3NbrState, 2374 ospfv3NbrEvents, 2375 ospfv3NbrLsRetransQLen, 2376 ospfv3NbmaNbrStatus, 2377 ospfv3NbmaNbrPermanence, 2378 ospfv3NbrHelloSuppressed, 2379 ospfv3NbrIfId 2380 } 2381 STATUS current 2382 DESCRIPTION 2383 "These neighbor objects are required for OSPFv3 systems." 2384 ::= { ospfv3Groups 9 } 2386 ospfv3VirtNbrGroup OBJECT-GROUP 2387 OBJECTS { 2388 ospfv3VirtNbrArea, 2389 ospfv3VirtNbrRtrId, 2390 ospfv3VirtNbrIfIndex, 2391 ospfv3VirtNbrIpv6Addr, 2392 ospfv3VirtNbrOptions, 2393 ospfv3VirtNbrState, 2394 ospfv3VirtNbrEvents, 2395 ospfv3VirtNbrLsRetransQLen, 2396 ospfv3VirtNbrHelloSuppressed, 2397 ospfv3VirtNbrIfId 2398 } 2399 STATUS current 2400 DESCRIPTION 2401 "These virtual neighbor objects are required for OSPFv3 systems." 2402 ::= { ospfv3Groups 10 } 2404 ospfv3AreaAggregateGroup OBJECT-GROUP 2405 OBJECTS { 2406 ospfv3AreaAggregateAreaID, 2407 ospfv3AreaAggregateAreaLsdbType, 2408 ospfv3AreaAggregateIndex, 2409 ospfv3AreaAggregatePrefix, 2410 ospfv3AreaAggregatePrefixLen, 2411 ospfv3AreaAggregateStatus, 2412 ospfv3AreaAggregateEffect 2413 } 2414 STATUS current 2415 DESCRIPTION 2416 "These area aggregate objects are required for OSPFv3 systems." 2417 ::= { ospfv3Groups 11 } 2419 END 2420 5. Acknowledgements 2422 This document is based on the MIB for OSPF version 2 by Rob 2423 Coltun and Fred Baker [8]. 2425 6. References 2427 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 2428 and S. Waldbusser, "Structure of Management Information 2429 for Version 2 of the Simple Network Management Protocol 2430 (SNMPv2)", RFC 1902, January 1996. 2432 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 2433 and S. Waldbusser, "Textual Conventions for Version 2 of 2434 the Simple Network Management Protocol (SNMPv2)", RFC 2435 1903, January 1996. 2437 [3] McCloghrie, K., and M. Rose, Editors, "Management 2438 Information Base for Network Management of TCP/IP-based 2439 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 2440 Performance Systems International, March 1991. 2442 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A 2443 Simple Network Management Protocol (SNMP)", STD 15, RFC 2444 1157, SNMP Research, Performance Systems International, 2445 MIT Lab for Computer Science, May 1990. 2447 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. 2448 and S. Waldbusser, "Protocol Operations for Version 2 of 2449 the Simple Network Management Protocol (SNMPv2)", RFC 2450 1905, January 1996. 2452 [6] McCloghrie, K. and F. Kastenholz, "Evolution of the 2453 Interfaces Group of MIB-II" , RFC 1573, January 1994. 2455 [7] Deering, S., and R. Hinden, "Internet Protocol, Version 6 2456 (IPv6) Specification", RFC 2460, December 1998. 2458 [8] Baker, F., and Coltun, R., "OSPF Version 2 Management 2459 Information Base", RFC 1850, cisco Systems, FORE Systems, 2460 November 1995. 2462 [9] Coltun, R., Ferguson, D., Moy, J., Internet Draft draft- 2463 ietf-ospf-ospfv6-06.txt, Siara Systems, Juniper Networks, 2464 Sycamore Networks, June 1999. 2466 [10] Haskin, D., Onishi, S., "Management Information Base for 2467 IP Version 6: Textual Conventions and General Group", RFC 2468 2465, Bay Networks, December 1998. 2470 [11] Moy, J., "OSPF Version 2", RFC 2328, Ascend 2471 Communications, Inc., April 1998. 2473 7. Security Considerations 2475 Security issues are not discussed in this memo. 2477 8. Authors' Address 2479 Dan Joyal 2480 Nortel Networks, Inc. 2481 600 Technology Park Drive 2482 Billerica, MA 01821 2483 email: djoyal@nortelnetworks.com