idnits 2.17.1 draft-ietf-ospf-ospfv3-mib-02.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 62 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 63 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 295 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 459: '...base. OspfExtAreaLsdbLimit MUST be set...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 13 has weird spacing: '...in full confo...' == Line 17 has weird spacing: '...), its areas...' == Line 18 has weird spacing: '...ups may also ...' == Line 22 has weird spacing: '... months and ...' == Line 23 has weird spacing: '...iate to use ...' == (290 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 2000) is 8775 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '17' is defined on line 2514, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2521, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 2525, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 2529, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2460 (ref. '17') (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 1850 (ref. '18') (Obsoleted by RFC 4750) ** Obsolete normative reference: RFC 2740 (ref. '19') (Obsoleted by RFC 5340) ** Obsolete normative reference: RFC 2465 (ref. '20') (Obsoleted by RFC 4293, RFC 8096) Summary: 22 errors (**), 0 flaws (~~), 14 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft OSPFv3 MIB April 2000 4 Management Information Base for OSPFv3 5 7 Dan Joyal 9 Nortel Networks, Inc. 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance 14 with all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet 17 Engineering Task Force (IETF), its areas, and its working 18 groups. Note that other groups may also distribute working 19 documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other 23 documents at any time. It is inappropriate to use Internet- 24 Drafts as reference material or to cite them other than as 25 "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed 31 at http://www.ietf.org/shadow.html. 33 Abstract 35 This memo defines an experimental portion of the Management 36 Information Base (MIB) for use with network management 37 protocols in IPv6-based internets. In particular, it defines 38 objects for managing the Open Shortest Path First Routing 39 Protocol for IPv6. 41 This document specifies a MIB module in a manner that is both 42 compliant to the SNMPv2 SMI, and semantically identical to the 43 peer SNMPv1 definitions. 45 Please send comments to ospf@discuss.microsoft.com. 47 1. The SNMP Management Framework 49 The SNMP Management Framework presently consists of five major 50 components: 52 o An overall architecture, described in RFC 2571 [1]. 54 o Mechanisms for describing and naming objects and events 55 for the purpose of management. The first version of this 56 Structure of Management Information (SMI) is called SMIv1 57 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 58 [3] and RFC 1215 [4]. The second version, called SMIv2, 59 is described in STD 58, RFC 2578 [5], RFC 2579 [6] and 60 RFC 2580 [7]. 62 o Message protocols for transferring management 63 information. The first version of the SNMP message 64 protocol is called SNMPv1 and described in STD 15, RFC 65 1157 [8]. A second version of the SNMP message protocol, 66 which is not an Internet standards track protocol, is 67 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 68 [10]. The third version of the message protocol is called 69 SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 70 RFC 2574 [12]. 72 o Protocol operations for accessing management information. 73 The first set of protocol operations and associated PDU 74 formats is described in STD 15, RFC 1157 [8]. A second 75 set of protocol operations and associated PDU formats is 76 described in RFC 1905 [13]. 78 o A set of fundamental applications described in RFC 2573 79 [14] and the view-based access control mechanism 80 described in RFC 2575 [15]. 82 A more detailed introduction to the current SNMP Management 83 Framework can be found in RFC 2570 [16]. 85 Managed objects are accessed via a virtual information store, 86 termed the Management Information Base or MIB. Objects in the 87 MIB are defined using the mechanisms defined in the SMI. 89 This memo specifies a MIB module that is compliant to the 90 SMIv2. A MIB conforming to the SMIv1 can be produced through 91 the appropriate translations. The resulting translated MIB 92 must be semantically equivalent, except where objects or 93 events are omitted because no translation is possible (use of 94 Counter64). Some machine readable information in SMIv2 will be 95 converted into textual descriptions in SMIv1 during the 96 translation process. However, this loss of machine readable 97 information is not considered to change the semantics of the 98 MIB. 100 2. Differences from RFC 1850 102 (1) Textual Conventions are imported from IPV6-TC and OSPF- 103 MIB MIBs. 105 (2) The "ospf" prefix for entity names is changed to 106 "ospfv3". 108 (3) General Group object name ospfVersionNumber is changed to 109 ospfv3VersionNumber and its value is changed from 2 to 3. 111 (4) General Group object name ospfExternLsaCount is changed 112 to ospfv3AsScopeLsaCount to indicate count of all AS- 113 scoped LSAs in the database. 115 (5) General Group object name ospfExternLsaCksumSum is 116 changed to ospfv3AsScopeCksumSum to indicate checksum of 117 all AS-scoped LSAs in the database. 119 (6) Removed General Group object ospfTOSSupport. 121 (7) Removed ospfAuthType object from Area entry. 123 (8) Changed object names ospfAreaLsaCount and 124 ospfAreaLsaCksumSum to ospfv3AreaScopeLsaCount and 125 ospfv3AreaScopeLsaCksumSum. 127 (9) Removed OSPF Area Default Metric Table. 129 (10) Added object ospfv3StubMetric to Area entry as substitute 130 for Area Default Metric Table. 132 (11) Changed name of External LSDB Table to AS-Scope LSDB 133 Table. Replaced object name prefix "ospfExtLsdb" with 134 "ospfv3AsLsdb". 136 (12) Changed name of LSDB Table to Area-Scope LSDB Table. 137 Replaced object name prefix "ospfLsdb" with 138 "ospfv3AreaLsdb". 140 (13) Added ospfv3LinkLsdbTable which contains all LSAs of 141 Link-Scope. Index of ospfv3LinkLsdbTable is IPv6 142 interface index, LSA Type, Router ID and LSID. 144 (14) Re-ordered Router ID and LSID index components of LSDB 145 table entries. Since LSIDs no longer have addressing 146 semantics, GET-NEXT operations on partial OIDs are more 147 useful when the Router ID component comes before the LSID 148 component. 150 (15) Address Range Table is removed. 152 (16) Removed ospfHostTOS from Host Table entry. Object 153 ospfHostIpAddress changed to ospfv3HostIpv6Address with 154 SYNTAX changed from IpAddress to Ipv6Address. 156 (17) The MAX-ACCESS value of object ospfv3HostAreaID is 157 changed to read-create. 159 (18) Objects ospfIfIpAddress and ospfAddressLessIf removed 160 from Interface entry and as Interface Table entry index 161 components. 163 (19) Object ospfv3IfIndex added to Interface Table entry with 164 SYNTAX Ipv6IfIndex. It replaces ospfIfIpAddress and 165 ospfAddressLessIf as the Interface Table entry index. 167 (20) The SYNTAX of objects ospfIfDesignatedRouter and 168 ospfIfBackupDesignatedRouter is changed from IpAddress to 169 RouterID. 171 (21) Objects ospfIfAuthType and ospfIfAuthKey are removed from 172 Interface and Virtual Interface entries. 174 (22) Added objects ospfv3IfLinkScopeLsaCount and 175 ospfv3IfLinkLsaCksumSum to Interface entry. They maintain 176 the count of Link-Scope LSAs and the checksum of the 177 Link-Scope LSA database associated with the interface. 179 (23) Removed OSPF Interface Metric Table. Metric is now 180 accessed via object ospfv3IfMetricValue in the Interface 181 entry. 183 (24) Added object ospfv3IfInstId to Interface entry to enable 184 the setting of the interface instance value of the 185 interface. The default value is zero. 187 (25) Added object ospfv3VirtIfIndex to Virtual Interface entry 188 which is used to assign a local interface ID to the 189 virtual interface. 191 (26) Added objects ospfv3VirtIfLinkScopeLsaCount and 192 ospfv3VirtIfLinkLsaCksumSum to Virtual Interface entry. 193 They maintain the count of Link-Scope LSAs and the 194 checksum of the Link-Scope LSA database associated with 195 the virtual interface. 197 (27) Removed objects ospfNbrIpAddr and ospfNbrAddressLessIndex 198 from Neighbor entry. 200 (28) Added object ospfv3NbrIfIndex to Neighbor entry. Index 201 components ospfNbrIpAddr and ospfNbrAddressLessIndex are 202 replaced with ospfv3NbrIfIndex and ospfv3NbrRtrId. 204 (29) Added object ospfv3NbrIfId to Neighbor entry. This object 205 contains the neighbor's local interface index from the 206 neighbor's hellos advertised on the link. 208 (30) Added object ospfv3VirtNbrIfIndex to Virtual Neighbor 209 entry. This is the interface index of the virtual link 210 over which the virtual neighbor is reached. 212 (31) Changed object name ospfVirtNbrIpAddr to 213 ospfv3VirtNbrIpv6Addr and SYNTAX from IpAddress to 214 Ipv6Address. 216 (32) Added object ospfv3VirtNbrIfId to Virtual Neighbor entry. 217 This is the virtual neighbor's local virtual interface 218 index from the neighbor's hellos advertised on the 219 virtual link. 221 (33) Added object ospfv3AreaAggregateIndex to Area Aggregate 222 entry. This allows for a fixed length index for Area 223 Aggregate Table entries. 225 (34) Replaced object ospfAreaAggregateMask with 226 ospfv3AreaAggregatePrefixLen. 228 (35) Replaced object ospfAreaAggregateNet with 229 ospfv3AreaAggregatePrefix. 231 (36) Index for Area Aggregate Table entry changed from 232 ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType, 233 ospfAreaAggregateNet, ospfAreaAggregateMask to 234 ospfv3AreaAggregateAreaID, 235 ospfv3AreaAggregateAreaLsdbType, 236 ospfv3AreaAggregateIndex. 238 (37) Conformance information is changed to reflect object 239 groups removed or added. 241 (38) OSPFv3 traps are not defined. 243 3. Structure of MIB 245 The MIB is composed of the following sections: 247 General Variables 248 Area Table 249 Area-Scope Link State Database 250 Link-Scope Link State Database 251 AS-Scope Link State Database 252 Host Table 253 Interface Table 254 Virtual Interface Table 255 Neighbor Table 256 Virtual Neighbor Table 257 Aggregate Range Table 259 3.1. General Variables 261 The General Variables are global to the OSPFv3 Process. 263 3.2. Area Table 265 The Area Data Structure describes the OSPFv3 Areas that the 266 router participates in. 268 3.3. Area-Scope, Link-Scope and AS-Scope Link State 269 Database 271 The Link State Database is provided primarily to provide 272 detailed information for network debugging. 274 3.4. Host Table 276 The Host Table is provided to view configured Host Route 277 information. 279 3.5. Interface Table 281 The Interface Table describes the various IPv6 links on which 282 OSPFv3 is configured. 284 3.6. Virtual Interface Table 286 The Virtual Interface Table describes virtual OSPFv3 links. 288 3.7. Neighbor and Virtual Neighbor Tables 290 The Neighbor Table and the Virtual Neighbor Table describe the 291 neighbors to the OSPF Process. 293 3.8. Aggregate Range Table 295 The Aggregate Range Table describes prefixes which summarize 296 routing information for export outside of an Area. 298 4. Definitions 300 OSPFV3-MIB DEFINITIONS ::= BEGIN 302 IMPORTS 303 MODULE-IDENTITY, OBJECT-TYPE, experimental, 304 Counter32, Gauge32, Integer32, IpAddress 305 FROM SNMPv2-SMI 306 TruthValue, RowStatus 307 FROM SNMPv2-TC 308 MODULE-COMPLIANCE, OBJECT-GROUP 309 FROM SNMPv2-CONF 310 Ipv6IfIndex, Ipv6Address, Ipv6AddressPrefix 311 FROM IPV6-TC 312 AreaID, RouterID, Metric, BigMetric, Status, PositiveInteger, 313 HelloRange, UpToMaxAge, DesignatedRouterPriority 314 FROM OSPF-MIB 315 ; 317 ospfv3Mib MODULE-IDENTITY 318 LAST-UPDATED "9909071305Z" 319 ORGANIZATION "IETF OSPF Working Group" 320 CONTACT-INFO 321 " Dan Joyal 322 Postal: Nortel Networks 323 600 Technology Park Drive 324 Billerica, MA 01821 325 USA 326 Tel: +1-978-288-2629 327 E-Mail: djoyal@nortelnetworks.com" 328 DESCRIPTION 329 "The MIB module to describe the OSPF Version for IPv6" 330 ::= { experimental 102 } --mib-2 OID to be assigned 332 ospfv3 OBJECT IDENTIFIER ::= { ospfv3Mib 1 } 334 -- OSPFv3 General Variables 336 -- These parameters apply globally to the Router's 337 -- OSPFv3 Process. 339 ospfv3GeneralGroup OBJECT IDENTIFIER ::= { ospfv3 1 } 340 ospfv3RouterId OBJECT-TYPE 341 SYNTAX RouterID 342 MAX-ACCESS read-write 343 STATUS current 344 DESCRIPTION 345 "A 32-bit integer uniquely identifying the 346 router in the Autonomous System. 348 By convention, to ensure uniqueness, this 349 should default to the value of one of the 350 router's IPv4 interface addresses if IPv4 is 351 configured." 352 ::= { ospfv3GeneralGroup 1 } 354 ospfv3AdminStat OBJECT-TYPE 355 SYNTAX Status 356 MAX-ACCESS read-write 357 STATUS current 358 DESCRIPTION 359 "The administrative status of OSPFv3 in the 360 router. The value 'enabled' denotes that the 361 OSPFv3 Process is active on at least one inter- 362 face; 'disabled' disables it on all inter- 363 faces." 364 ::= { ospfv3GeneralGroup 2 } 366 ospfv3VersionNumber OBJECT-TYPE 367 SYNTAX INTEGER { version3 (3) } 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "The version number of OSPF for IPv6 is 3." 372 ::= { ospfv3GeneralGroup 3 } 374 ospfv3AreaBdrRtrStatus OBJECT-TYPE 375 SYNTAX TruthValue 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "A flag to note whether this router is an area 380 border router." 381 REFERENCE 382 "OSPF Version 2, Section 3 Splitting the AS into 383 Areas" 384 ::= { ospfv3GeneralGroup 4 } 386 ospfv3ASBdrRtrStatus OBJECT-TYPE 387 SYNTAX TruthValue 388 MAX-ACCESS read-write 389 STATUS current 390 DESCRIPTION 391 "A flag to note whether this router is config- 392 ured as an Autonomous System border router." 393 REFERENCE 394 "OSPF Version 2, Section 3.3 Classification of 395 routers" 396 ::= { ospfv3GeneralGroup 5 } 398 ospfv3AsScopeLsaCount OBJECT-TYPE 399 SYNTAX Gauge32 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The number of AS-Scope (e.g. AS-External) link-state 404 advertisements in the link-state database." 405 ::= { ospfv3GeneralGroup 6 } 407 ospfv3AsScopeLsaCksumSum OBJECT-TYPE 408 SYNTAX Integer32 409 MAX-ACCESS read-only 410 STATUS current 411 DESCRIPTION 412 "The 32-bit unsigned sum of the LS checksums of 413 the AS-scoped link-state advertisements con- 414 tained in the link-state database. This sum 415 can be used to determine if there has been a 416 change in a router's link state database, and 417 to compare the link-state database of two 418 routers." 419 ::= { ospfv3GeneralGroup 7 } 421 ospfv3OriginateNewLsas OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The number of new link-state advertisements 427 that have been originated. This number is in- 428 cremented each time the router originates a new 429 LSA." 430 ::= { ospfv3GeneralGroup 8 } 432 ospfv3RxNewLsas OBJECT-TYPE 433 SYNTAX Counter32 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "The number of link-state advertisements re- 438 ceived determined to be new instantiations. 439 This number does not include newer instantia- 440 tions of self-originated link-state advertise- 441 ments." 442 ::= { ospfv3GeneralGroup 9 } 444 ospfv3ExtAreaLsdbLimit OBJECT-TYPE 445 SYNTAX Integer32 (-1..'7FFFFFFF'h) 446 MAX-ACCESS read-write 447 STATUS current 448 DESCRIPTION 449 "The maximum number of non-default AS- 450 external-LSAs entries that can be stored in the 451 link-state database. If the value is -1, then 452 there is no limit. 454 When the number of non-default AS-external-LSAs 455 in a router's link-state database reaches 456 ospfv3ExtAreaLsdbLimit, the router enters Overflow- 457 State. The router never holds more than 458 ospfv3ExtAreaLsdbLimit non-default AS-external-LSAs 459 in its database. OspfExtAreaLsdbLimit MUST be set 460 identically in all routers attached to the OSPFv3 461 backbone and/or any regular OSPFv3 area. (i.e., 462 OSPFv3 stub areas and NSSAs are excluded)." 463 DEFVAL { -1 } 464 ::= { ospfv3GeneralGroup 10 } 466 ospfv3MulticastExtensions OBJECT-TYPE 467 SYNTAX Integer32 468 MAX-ACCESS read-write 469 STATUS current 470 DESCRIPTION 471 "A Bit Mask indicating whether the router is 472 forwarding IPv6 multicast datagrams 473 based on the algorithms defined in the Multi- 474 cast Extensions to OSPF. 476 Bit 0, if set, indicates that the router can 477 forward IPv6 multicast datagrams in the router's 478 directly attached areas (called intra-area mul- 479 ticast routing). 481 Bit 1, if set, indicates that the router can 482 forward IPv6 multicast datagrams between OSPFv3 483 areas (called inter-area multicast routing). 485 Bit 2, if set, indicates that the router can 486 forward IPv6 multicast datagrams between Auto- 487 nomous Systems (called inter-AS multicast rout- 488 ing). 490 Only certain combinations of bit settings are 491 allowed, namely: 0 (no multicast forwarding is 492 enabled), 1 (intra-area multicasting only), 3 493 (intra-area and inter-area multicasting), 5 494 (intra-area and inter-AS multicasting) and 7 495 (multicasting everywhere). By default, no mul- 496 ticast forwarding is enabled." 497 DEFVAL { 0 } 498 ::= { ospfv3GeneralGroup 11 } 500 ospfv3ExitOverflowInterval OBJECT-TYPE 501 SYNTAX PositiveInteger 502 MAX-ACCESS read-write 503 STATUS current 504 DESCRIPTION 505 "The number of seconds that, after entering 506 OverflowState, a router will attempt to leave 507 OverflowState. This allows the router to again 508 originate non-default AS-External-LSAs. When 509 set to 0, the router will not leave Overflow- 510 State until restarted." 511 DEFVAL { 0 } 512 ::= { ospfv3GeneralGroup 12 } 514 ospfv3DemandExtensions OBJECT-TYPE 515 SYNTAX TruthValue 516 MAX-ACCESS read-write 517 STATUS current 518 DESCRIPTION 519 "The router's support for demand routing." 520 REFERENCE 521 "OSPF Version 2, Appendix on Demand Routing" 522 ::= { ospfv3GeneralGroup 13 } 524 -- The OSPFv3 Area Data Structure contains information 525 -- regarding the various areas. The interfaces and 526 -- virtual links are configured as part of these areas. 527 -- Area 0.0.0.0, by definition, is the Backbone Area 529 ospfv3AreaTable OBJECT-TYPE 530 SYNTAX SEQUENCE OF Ospfv3AreaEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "Information describing the configured parame- 535 ters and cumulative statistics of the router's 536 attached areas." 537 REFERENCE 538 "OSPF Version 2, Section 6 The Area Data Struc- 539 ture" 540 ::= { ospfv3 2 } 542 ospfv3AreaEntry OBJECT-TYPE 543 SYNTAX Ospfv3AreaEntry 544 MAX-ACCESS not-accessible 545 STATUS current 546 DESCRIPTION 547 "Information describing the configured parame- 548 ters and cumulative statistics of one of the 549 router's attached areas." 550 INDEX { ospfv3AreaId } 551 ::= { ospfv3AreaTable 1 } 553 Ospfv3AreaEntry ::= 554 SEQUENCE { 555 ospfv3AreaId 556 AreaID, 557 ospfv3ImportAsExtern 558 INTEGER, 559 ospfv3SpfRuns 560 Counter32, 561 ospfv3AreaBdrRtrCount 562 Gauge32, 563 ospfv3AsBdrRtrCount 564 Gauge32, 565 ospfv3AreaScopeLsaCount 566 Gauge32, 567 ospfv3AreaScopeLsaCksumSum 568 Integer32, 569 ospfv3AreaSummary 570 INTEGER, 571 ospfv3AreaStatus 572 RowStatus, 573 ospfv3StubMetric 574 BigMetric 575 } 577 ospfv3AreaId OBJECT-TYPE 578 SYNTAX AreaID 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "A 32-bit integer uniquely identifying an area. 583 Area ID 0.0.0.0 is used for the OSPFv3 backbone." 584 REFERENCE 585 "OSPF Version 2, Appendix C.2 Area parameters" 586 ::= { ospfv3AreaEntry 1 } 588 ospfv3ImportAsExtern OBJECT-TYPE 589 SYNTAX INTEGER { 590 importExternal (1), -- normal area 591 importNoExternal (2), -- stub area 592 importNssa (3) -- not-so-stubby-area 593 } 594 MAX-ACCESS read-create 595 STATUS current 596 DESCRIPTION 597 "The area's support for importing AS external 598 link- state advertisements." 599 REFERENCE 600 "OSPF Version 2, Appendix C.2 Area parameters" 601 DEFVAL { importExternal } 602 ::= { ospfv3AreaEntry 2 } 604 ospfv3SpfRuns OBJECT-TYPE 605 SYNTAX Counter32 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "The number of times that the intra-area route 610 table has been calculated using this area's 611 link-state database. This is typically done 612 using Dijkstra's algorithm." 613 ::= { ospfv3AreaEntry 3 } 615 ospfv3AreaBdrRtrCount OBJECT-TYPE 616 SYNTAX Gauge32 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION 620 "The total number of area border routers reach- 621 able within this area. This is initially zero, 622 and is calculated in each SPF Pass." 623 ::= { ospfv3AreaEntry 4 } 625 ospfv3AsBdrRtrCount OBJECT-TYPE 626 SYNTAX Gauge32 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "The total number of Autonomous System border 631 routers reachable within this area. This is 632 initially zero, and is calculated in each SPF 633 Pass." 634 ::= { ospfv3AreaEntry 5 } 636 ospfv3AreaScopeLsaCount OBJECT-TYPE 637 SYNTAX Gauge32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The total number of Area-Scope link-state advertisements 642 in this area's link-state database." 643 ::= { ospfv3AreaEntry 6 } 645 ospfv3AreaScopeLsaCksumSum OBJECT-TYPE 646 SYNTAX Integer32 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION 650 "The 32-bit unsigned sum of the Area-Scope link-state 651 advertisements' LS checksums contained in this 652 area's link-state database. The sum can be used 653 to determine if there has been a change in a 654 router's link state database, and to compare the 655 link-state database of two routers." 656 DEFVAL { 0 } 657 ::= { ospfv3AreaEntry 7 } 659 ospfv3AreaSummary OBJECT-TYPE 660 SYNTAX INTEGER { 661 noAreaSummary (1), 662 sendAreaSummary (2) 663 } 664 MAX-ACCESS read-create 665 STATUS current 666 DESCRIPTION 667 "The variable ospfv3AreaSummary controls the im- 668 port of summary LSAs into stub areas. It has 669 no effect on other areas. 671 If it is noAreaSummary, the router will neither 672 originate nor propagate summary LSAs into the 673 stub area. It will rely entirely on its de- 674 fault route. 676 If it is sendAreaSummary, the router will both 677 summarize and propagate summary LSAs." 678 DEFVAL { noAreaSummary } 679 ::= { ospfv3AreaEntry 8 } 681 ospfv3AreaStatus OBJECT-TYPE 682 SYNTAX RowStatus 683 MAX-ACCESS read-create 684 STATUS current 685 DESCRIPTION 686 "This variable displays the status of the en- 687 try. Setting it to 'invalid' has the effect of 688 rendering it inoperative. The internal effect 689 (row removal) is implementation dependent." 690 ::= { ospfv3AreaEntry 9 } 692 ospfv3StubMetric OBJECT-TYPE 693 SYNTAX BigMetric 694 MAX-ACCESS read-create 695 STATUS current 696 DESCRIPTION 697 "The metric value advertised for the default route 698 into Stub and NSSA areas." 699 ::= { ospfv3AreaEntry 10 } 701 -- OSPFv3 AS-Scope Link State Database 703 -- The Link State Database contains the AS-Scope Link State 704 -- Advertisements from throughout the areas that the 705 -- device is attached to. 707 ospfv3AsLsdbTable OBJECT-TYPE 708 SYNTAX SEQUENCE OF Ospfv3AsLsdbEntry 709 MAX-ACCESS not-accessible 710 STATUS current 711 DESCRIPTION 712 "The OSPFv3 Process's AS-Scope Link State Database." 713 ::= { ospfv3 3 } 715 ospfv3AsLsdbEntry OBJECT-TYPE 716 SYNTAX Ospfv3AsLsdbEntry 717 MAX-ACCESS not-accessible 718 STATUS current 719 DESCRIPTION 720 "A single AS-Scope Link State Advertisement." 721 INDEX { ospfv3AsLsdbType, 722 ospfv3AsLsdbRouterId, 723 ospfv3AsLsdbLsid } 724 ::= { ospfv3AsLsdbTable 1 } 726 Ospfv3AsLsdbEntry ::= 727 SEQUENCE { 728 ospfv3AsLsdbType 729 INTEGER, 730 ospfv3AsLsdbRouterId 731 RouterID, 732 ospfv3AsLsdbLsid 733 IpAddress, 734 ospfv3AsLsdbSequence 735 Integer32, 736 ospfv3AsLsdbAge 737 Integer32, 738 ospfv3AsLsdbChecksum 739 Integer32, 740 ospfv3AsLsdbAdvertisement 741 OCTET STRING 742 } 744 ospfv3AsLsdbType OBJECT-TYPE 745 SYNTAX INTEGER { 746 asExternalLink (16389) -- 0x4005 747 } 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 "The type of the link state advertisement. 752 Each link state type has a separate advertise- 753 ment format. Unrecognized AS-Scope LSAs with the 754 U-bit set are also store in this database." 755 ::= { ospfv3AsLsdbEntry 1 } 757 ospfv3AsLsdbRouterId OBJECT-TYPE 758 SYNTAX RouterID 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The 32 bit number that uniquely identifies the 763 originating router in the Autonomous System." 764 REFERENCE 765 "OSPF Version 2, Appendix C.1 Global parameters" 766 ::= { ospfv3AsLsdbEntry 2 } 768 ospfv3AsLsdbLsid OBJECT-TYPE 769 SYNTAX IpAddress 770 MAX-ACCESS read-only 771 STATUS current 772 DESCRIPTION 773 "The Link State ID is an LS Type Specific field 774 containing either a Router ID or a unique identifier; 775 it identifies the piece of the routing domain 776 that is being described by the advertisement. 777 In contrast to OSPF for IPv4, the LSID has no 778 addressing semantics." 779 ::= { ospfv3AsLsdbEntry 3 } 781 -- Note that the OSPF Sequence Number is a 32 bit signed 782 -- integer. It starts with the value '80000001'h, 783 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 784 -- Thus, a typical sequence number will be very negative. 786 ospfv3AsLsdbSequence OBJECT-TYPE 787 SYNTAX Integer32 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The sequence number field is a signed 32-bit 792 integer. It is used to detect old and dupli- 793 cate link state advertisements. The space of 794 sequence numbers is linearly ordered. The 795 larger the sequence number the more recent the 796 advertisement." 797 REFERENCE 798 "OSPF Version 2, Section 12.1.6 LS sequence 799 number" 800 ::= { ospfv3AsLsdbEntry 4 } 802 ospfv3AsLsdbAge OBJECT-TYPE 803 SYNTAX Integer32 -- Should be 0..MaxAge 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "This field is the age of the link state adver- 808 tisement in seconds." 809 REFERENCE 810 "OSPF Version 2, Section 12.1.1 LS age" 811 ::= { ospfv3AsLsdbEntry 5 } 813 ospfv3AsLsdbChecksum OBJECT-TYPE 814 SYNTAX Integer32 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "This field is the checksum of the complete 819 contents of the advertisement, excepting the 820 age field. The age field is excepted so that 821 an advertisement's age can be incremented 822 without updating the checksum. The checksum 823 used is the same that is used for ISO connec- 824 tionless datagrams; it is commonly referred to 825 as the Fletcher checksum." 826 REFERENCE 827 "OSPF Version 2, Section 12.1.7 LS checksum" 828 ::= { ospfv3AsLsdbEntry 6 } 830 ospfv3AsLsdbAdvertisement OBJECT-TYPE 831 SYNTAX OCTET STRING (SIZE (1..65535)) 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "The entire Link State Advertisement, including 836 its header." 837 ::= { ospfv3AsLsdbEntry 7 } 839 -- OSPFv3 Area-Scope Link State Database 841 -- The Link State Database contains the Area-Scope Link State 842 -- Advertisements from throughout the area that the 843 -- device is attached to. 845 ospfv3AreaLsdbTable OBJECT-TYPE 846 SYNTAX SEQUENCE OF Ospfv3AreaLsdbEntry 847 MAX-ACCESS not-accessible 848 STATUS current 849 DESCRIPTION 850 "The OSPFv3 Process's Area-Scope Link State Database." 851 ::= { ospfv3 4 } 853 ospfv3AreaLsdbEntry OBJECT-TYPE 854 SYNTAX Ospfv3AreaLsdbEntry 855 MAX-ACCESS not-accessible 856 STATUS current 857 DESCRIPTION 858 "A single Area-Scope Link State Advertisement." 859 INDEX { ospfv3AreaLsdbAreaId, 860 ospfv3AreaLsdbType, 861 ospfv3AreaLsdbRouterId, 862 ospfv3AreaLsdbLsid } 863 ::= { ospfv3AreaLsdbTable 1 } 865 Ospfv3AreaLsdbEntry ::= 866 SEQUENCE { 867 ospfv3AreaLsdbAreaId 868 AreaID, 869 ospfv3AreaLsdbType 870 INTEGER, 871 ospfv3AreaLsdbRouterId 872 RouterID, 873 ospfv3AreaLsdbLsid 874 IpAddress, 875 ospfv3AreaLsdbSequence 876 Integer32, 877 ospfv3AreaLsdbAge 878 Integer32, 879 ospfv3AreaLsdbChecksum 880 Integer32, 881 ospfv3AreaLsdbAdvertisement 882 OCTET STRING 883 } 885 ospfv3AreaLsdbAreaId OBJECT-TYPE 886 SYNTAX AreaID 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "'The 32 bit identifier of the Area from which the LSA 891 was received.' 892 REFERENCE 893 'OSPF Version 2, Appendix C.2 Area parameters'" 894 ::= { ospfv3AreaLsdbEntry 1 } 896 ospfv3AreaLsdbType OBJECT-TYPE 897 SYNTAX INTEGER { 898 routerLsa (8193), -- 0x2001 899 networkLsa (8194), -- 0x2002 900 interAreaPrefixLsa (8195), -- 0x2003 901 interAreaRouterLsa (8196), -- 0x2004 902 groupMembershipLsa (8198), -- 0x2006 903 nssaExternalLsa (8199), -- 0x2007 904 intraAreaPrefixLsa (8201) -- 0x2009 905 } 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The type of the link state advertisement. 910 Each link state type has a separate advertise- 911 ment format. Unrecognized Area-Scope LSAs with 912 the U-bit set are also stored in this database." 913 ::= { ospfv3AreaLsdbEntry 2 } 915 ospfv3AreaLsdbRouterId OBJECT-TYPE 916 SYNTAX RouterID 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The 32 bit number that uniquely identifies the 921 originating router in the Autonomous System." 922 REFERENCE 923 "OSPF Version 2, Appendix C.1 Global parameters" 924 ::= { ospfv3AreaLsdbEntry 3 } 926 ospfv3AreaLsdbLsid OBJECT-TYPE 927 SYNTAX IpAddress 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "The Link State ID is an LS Type Specific field 932 containing either a Router ID or a unique identifier; 933 it identifies the piece of the routing domain 934 that is being described by the advertisement. 935 In contrast to OSPF for IPv4, the LSID has no 936 addressing semantics." 937 ::= { ospfv3AreaLsdbEntry 4 } 939 -- Note that the OSPF Sequence Number is a 32 bit signed 940 -- integer. It starts with the value '80000001'h, 941 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 942 -- Thus, a typical sequence number will be very negative. 944 ospfv3AreaLsdbSequence OBJECT-TYPE 945 SYNTAX Integer32 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "The sequence number field is a signed 32-bit 950 integer. It is used to detect old and dupli- 951 cate link state advertisements. The space of 952 sequence numbers is linearly ordered. The 953 larger the sequence number the more recent the 954 advertisement." 955 REFERENCE 956 "OSPF Version 2, Section 12.1.6 LS sequence 957 number" 958 ::= { ospfv3AreaLsdbEntry 5 } 960 ospfv3AreaLsdbAge OBJECT-TYPE 961 SYNTAX Integer32 -- Should be 0..MaxAge 962 MAX-ACCESS read-only 963 STATUS current 964 DESCRIPTION 965 "This field is the age of the link state adver- 966 tisement in seconds." 967 REFERENCE 968 "OSPF Version 2, Section 12.1.1 LS age" 969 ::= { ospfv3AreaLsdbEntry 6 } 971 ospfv3AreaLsdbChecksum OBJECT-TYPE 972 SYNTAX Integer32 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "This field is the checksum of the complete 977 contents of the advertisement, excepting the 978 age field. The age field is excepted so that 979 an advertisement's age can be incremented 980 without updating the checksum. The checksum 981 used is the same that is used for ISO connec- 982 tionless datagrams; it is commonly referred to 983 as the Fletcher checksum." 985 REFERENCE 986 "OSPF Version 2, Section 12.1.7 LS checksum" 987 ::= { ospfv3AreaLsdbEntry 7 } 989 ospfv3AreaLsdbAdvertisement OBJECT-TYPE 990 SYNTAX OCTET STRING (SIZE (1..65535)) 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "The entire Link State Advertisement, including 995 its header." 996 ::= { ospfv3AreaLsdbEntry 8 } 998 -- OSPFv3 Link-Scope Link State Database 1000 -- The Link State Database contains the Link-Scope Link State 1001 -- Advertisements from the links that the 1002 -- device is attached to. 1004 ospfv3LinkLsdbTable OBJECT-TYPE 1005 SYNTAX SEQUENCE OF Ospfv3LinkLsdbEntry 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "The OSPFv3 Process's Link-Scope Link State Database." 1010 ::= { ospfv3 5 } 1012 ospfv3LinkLsdbEntry OBJECT-TYPE 1013 SYNTAX Ospfv3LinkLsdbEntry 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "A single Link-Scope Link State Advertisement." 1018 INDEX { ospfv3LinkLsdbIfIndex, 1019 ospfv3LinkLsdbType, 1020 ospfv3LinkLsdbRouterId, 1021 ospfv3LinkLsdbLsid } 1022 ::= { ospfv3LinkLsdbTable 1 } 1024 Ospfv3LinkLsdbEntry ::= 1025 SEQUENCE { 1026 ospfv3LinkLsdbIfIndex 1027 Ipv6IfIndex, 1028 ospfv3LinkLsdbType 1029 INTEGER, 1030 ospfv3LinkLsdbRouterId 1031 RouterID, 1032 ospfv3LinkLsdbLsid 1033 IpAddress, 1034 ospfv3LinkLsdbSequence 1035 Integer32, 1036 ospfv3LinkLsdbAge 1037 Integer32, 1038 ospfv3LinkLsdbChecksum 1039 Integer32, 1040 ospfv3LinkLsdbAdvertisement 1041 OCTET STRING 1042 } 1044 ospfv3LinkLsdbIfIndex OBJECT-TYPE 1045 SYNTAX Ipv6IfIndex 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 "'The identifier of the link from which the LSA 1050 was received.' 1051 REFERENCE 1052 'OSPF Version 2, Appendix C.2 Area parameters'" 1053 ::= { ospfv3LinkLsdbEntry 1 } 1055 ospfv3LinkLsdbType OBJECT-TYPE 1056 SYNTAX INTEGER { 1057 linkLsa (8) -- 0x0008 1058 } 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "The type of the link state advertisement. 1063 Each link state type has a separate advertise- 1064 ment format. Unrecognized Link-Scope LSAs with 1065 the U-bit set are also stored in this database." 1066 ::= { ospfv3LinkLsdbEntry 2 } 1068 ospfv3LinkLsdbRouterId OBJECT-TYPE 1069 SYNTAX RouterID 1070 MAX-ACCESS read-only 1071 STATUS current 1072 DESCRIPTION 1073 "The 32 bit number that uniquely identifies the 1074 originating router in the Autonomous System." 1075 REFERENCE 1076 "OSPF Version 2, Appendix C.1 Global parameters" 1077 ::= { ospfv3LinkLsdbEntry 3 } 1079 ospfv3LinkLsdbLsid OBJECT-TYPE 1080 SYNTAX IpAddress 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The Link State ID is an LS Type Specific field 1085 containing either a Router ID or a unique identifier; 1086 it identifies the piece of the routing domain 1087 that is being described by the advertisement. 1088 In contrast to OSPF for IPv4, the LSID has no 1089 addressing semantics." 1090 ::= { ospfv3LinkLsdbEntry 4 } 1092 -- Note that the OSPF Sequence Number is a 32 bit signed 1093 -- integer. It starts with the value '80000001'h, 1094 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1095 -- Thus, a typical sequence number will be very negative. 1097 ospfv3LinkLsdbSequence OBJECT-TYPE 1098 SYNTAX Integer32 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "The sequence number field is a signed 32-bit 1103 integer. It is used to detect old and dupli- 1104 cate link state advertisements. The space of 1105 sequence numbers is linearly ordered. The 1106 larger the sequence number the more recent the 1107 advertisement." 1108 REFERENCE 1109 "OSPF Version 2, Section 12.1.6 LS sequence 1110 number" 1111 ::= { ospfv3LinkLsdbEntry 5 } 1113 ospfv3LinkLsdbAge OBJECT-TYPE 1114 SYNTAX Integer32 -- Should be 0..MaxAge 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "This field is the age of the link state adver- 1119 tisement in seconds." 1120 REFERENCE 1121 "OSPF Version 2, Section 12.1.1 LS age" 1122 ::= { ospfv3LinkLsdbEntry 6 } 1124 ospfv3LinkLsdbChecksum OBJECT-TYPE 1125 SYNTAX Integer32 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "This field is the checksum of the complete 1130 contents of the advertisement, excepting the 1131 age field. The age field is excepted so that 1132 an advertisement's age can be incremented 1133 without updating the checksum. The checksum 1134 used is the same that is used for ISO connec- 1135 tionless datagrams; it is commonly referred to 1136 as the Fletcher checksum." 1137 REFERENCE 1138 "OSPF Version 2, Section 12.1.7 LS checksum" 1139 ::= { ospfv3LinkLsdbEntry 7 } 1141 ospfv3LinkLsdbAdvertisement OBJECT-TYPE 1142 SYNTAX OCTET STRING (SIZE (1..65535)) 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "The entire Link State Advertisement, including 1147 its header." 1148 ::= { ospfv3LinkLsdbEntry 8 } 1150 -- OSPF Host Table 1152 -- The Host/Metric Table indicates what hosts are directly 1153 -- attached to the Router, and what metrics and types of 1154 -- service should be advertised for them. 1156 ospfv3HostTable OBJECT-TYPE 1157 SYNTAX SEQUENCE OF Ospfv3HostEntry 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "The list of Hosts, and their metrics, that the 1162 router will advertise as host routes." 1163 REFERENCE 1164 "OSPF Version 2, Appendix C.6 Host route param- 1165 eters" 1166 ::= { ospfv3 6 } 1168 ospfv3HostEntry OBJECT-TYPE 1169 SYNTAX Ospfv3HostEntry 1170 MAX-ACCESS not-accessible 1171 STATUS current 1172 DESCRIPTION 1173 "A metric to be advertised when a given host is reachable." 1174 INDEX { ospfv3HostIpv6Address } 1175 ::= { ospfv3HostTable 1 } 1177 Ospfv3HostEntry ::= 1178 SEQUENCE { 1179 ospfv3HostIpv6Address 1180 Ipv6Address, 1181 ospfv3HostMetric 1182 Metric, 1183 ospfv3HostStatus 1184 RowStatus, 1185 ospfv3HostAreaID 1186 AreaID 1187 } 1189 ospfv3HostIpv6Address OBJECT-TYPE 1190 SYNTAX Ipv6Address 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "The IPv6 Address of the Host. Must be a Global 1195 or Site-local address." 1196 REFERENCE 1197 "OSPF Version 2, Appendix C.6 Host route parame- 1198 ters" 1200 ::= { ospfv3HostEntry 1 } 1202 ospfv3HostMetric OBJECT-TYPE 1203 SYNTAX Metric 1204 MAX-ACCESS read-create 1205 STATUS current 1206 DESCRIPTION 1207 "The Metric to be advertised." 1208 REFERENCE 1209 "OSPF Version 2, Appendix C.6 Host route parame- 1210 ters" 1211 ::= { ospfv3HostEntry 2 } 1213 ospfv3HostStatus OBJECT-TYPE 1214 SYNTAX RowStatus 1215 MAX-ACCESS read-create 1216 STATUS current 1217 DESCRIPTION 1218 "This variable displays the status of the en- 1219 try. Setting it to 'invalid' has the effect of 1220 rendering it inoperative. The internal effect 1221 (row removal) is implementation dependent." 1222 ::= { ospfv3HostEntry 3 } 1224 ospfv3HostAreaID OBJECT-TYPE 1225 SYNTAX AreaID 1226 MAX-ACCESS read-create 1227 STATUS current 1228 DESCRIPTION 1229 "The Area the Host Entry is to be found within. 1230 By default, the area that a subsuming OSPFv3 in- 1231 terface is in, or 0.0.0.0" 1232 REFERENCE 1233 "OSPF Version 2, Appendix C.2 Area parameters" 1234 ::= { ospfv3HostEntry 4 } 1236 -- OSPFv3 Interface Table 1238 ospfv3IfTable OBJECT-TYPE 1239 SYNTAX SEQUENCE OF Ospfv3IfEntry 1240 MAX-ACCESS not-accessible 1241 STATUS current 1242 DESCRIPTION 1243 "The OSPFv3 Interface Table describes the inter- 1244 faces from the viewpoint of OSPFv3." 1245 REFERENCE 1246 "OSPF Version 2, Appendix C.3 Router interface 1247 parameters" 1248 ::= { ospfv3 7 } 1250 ospfv3IfEntry OBJECT-TYPE 1251 SYNTAX Ospfv3IfEntry 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "The OSPFv3 Interface Entry describes one inter- 1256 face from the viewpoint of OSPFv3." 1257 INDEX { ospfv3IfIndex } 1258 ::= { ospfv3IfTable 1 } 1260 Ospfv3IfEntry ::= 1261 SEQUENCE { 1262 ospfv3IfIndex 1263 Ipv6IfIndex, 1264 ospfv3IfAreaId 1265 AreaID, 1266 ospfv3IfType 1267 INTEGER, 1268 ospfv3IfAdminStat 1269 Status, 1270 ospfv3IfRtrPriority 1271 DesignatedRouterPriority, 1272 ospfv3IfTransitDelay 1273 UpToMaxAge, 1274 ospfv3IfRetransInterval 1275 UpToMaxAge, 1276 ospfv3IfHelloInterval 1277 HelloRange, 1278 ospfv3IfRtrDeadInterval 1279 PositiveInteger, 1280 ospfv3IfPollInterval 1281 PositiveInteger, 1282 ospfv3IfState 1283 INTEGER, 1284 ospfv3IfDesignatedRouter 1285 RouterID, 1287 ospfv3IfBackupDesignatedRouter 1288 RouterID, 1289 ospfv3IfEvents 1290 Counter32, 1291 ospfv3IfStatus 1292 RowStatus, 1293 ospfv3IfMulticastForwarding 1294 INTEGER, 1295 ospfv3IfDemand 1296 TruthValue, 1297 ospfv3IfMetricValue 1298 Metric, 1299 ospfv3IfLinkScopeLsaCount 1300 Gauge32, 1301 ospfv3IfLinkLsaCksumSum 1302 Integer32, 1303 ospfv3IfInstId 1304 Integer32 1305 } 1307 ospfv3IfIndex OBJECT-TYPE 1308 SYNTAX Ipv6IfIndex 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "The interface index of this OSPFv3 interface. 1313 It corresponds to the interface index of the 1314 Ipv6 interface on which OSPFv3 is configured." 1315 ::= { ospfv3IfEntry 1 } 1317 ospfv3IfAreaId OBJECT-TYPE 1318 SYNTAX AreaID 1319 MAX-ACCESS read-create 1320 STATUS current 1321 DESCRIPTION 1322 "A 32-bit integer uniquely identifying the area 1323 to which the interface connects. Area ID 1324 0.0.0.0 is used for the OSPFv3 backbone." 1325 DEFVAL { '00000000'H } -- 0.0.0.0 1326 ::= { ospfv3IfEntry 2 } 1328 ospfv3IfType OBJECT-TYPE 1329 SYNTAX INTEGER { 1330 broadcast (1), 1331 nbma (2), 1332 pointToPoint (3), 1333 pointToMultipoint (5) 1334 } 1335 MAX-ACCESS read-create 1336 STATUS current 1337 DESCRIPTION 1338 "The OSPFv3 interface type." 1339 ::= { ospfv3IfEntry 3 } 1341 ospfv3IfAdminStat OBJECT-TYPE 1342 SYNTAX Status 1343 MAX-ACCESS read-create 1344 STATUS current 1345 DESCRIPTION 1346 "The OSPFv3 interface's administrative status. 1347 The value formed on the interface, and the in- 1348 terface will be advertised as an internal route 1349 to some area. The value 'disabled' denotes 1350 that the interface is external to OSPFv3." 1351 DEFVAL { enabled } 1352 ::= { ospfv3IfEntry 4 } 1354 ospfv3IfRtrPriority OBJECT-TYPE 1355 SYNTAX DesignatedRouterPriority 1356 MAX-ACCESS read-create 1357 STATUS current 1358 DESCRIPTION 1359 "The priority of this interface. Used in 1360 multi-access networks, this field is used in 1361 the designated router election algorithm. The 1362 value 0 signifies that the router is not eligi- 1363 ble to become the designated router on this 1364 particular network. In the event of a tie in 1365 this value, routers will use their Router ID as 1366 a tie breaker." 1367 DEFVAL { 1 } 1368 ::= { ospfv3IfEntry 5 } 1370 ospfv3IfTransitDelay OBJECT-TYPE 1371 SYNTAX UpToMaxAge 1372 MAX-ACCESS read-create 1373 STATUS current 1374 DESCRIPTION 1375 "The estimated number of seconds it takes to 1376 transmit a link state update packet over this 1377 interface." 1378 DEFVAL { 1 } 1379 ::= { ospfv3IfEntry 6 } 1381 ospfv3IfRetransInterval OBJECT-TYPE 1382 SYNTAX UpToMaxAge 1383 MAX-ACCESS read-create 1384 STATUS current 1385 DESCRIPTION 1386 "The number of seconds between link-state ad- 1387 vertisement retransmissions, for adjacencies 1388 belonging to this interface. This value is 1389 also used when retransmitting database descrip- 1390 tion and link-state request packets." 1391 DEFVAL { 5 } 1392 ::= { ospfv3IfEntry 7 } 1394 ospfv3IfHelloInterval OBJECT-TYPE 1395 SYNTAX HelloRange 1396 MAX-ACCESS read-create 1397 STATUS current 1398 DESCRIPTION 1399 "The length of time, in seconds, between the 1400 Hello packets that the router sends on the in- 1401 terface. This value must be the same for all 1402 routers attached to a common network." 1403 DEFVAL { 10 } 1404 ::= { ospfv3IfEntry 8 } 1406 ospfv3IfRtrDeadInterval OBJECT-TYPE 1407 SYNTAX PositiveInteger 1408 MAX-ACCESS read-create 1409 STATUS current 1410 DESCRIPTION 1411 "The number of seconds that a router's Hello 1412 packets have not been seen before it's neigh- 1413 bors declare the router down. This should be 1414 some multiple of the Hello interval. This 1415 value must be the same for all routers attached 1416 to a common network." 1417 DEFVAL { 40 } 1418 ::= { ospfv3IfEntry 9 } 1420 ospfv3IfPollInterval OBJECT-TYPE 1421 SYNTAX PositiveInteger 1422 MAX-ACCESS read-create 1423 STATUS current 1424 DESCRIPTION 1425 "The larger time interval, in seconds, between 1426 the Hello packets sent to an inactive non- 1427 broadcast multi- access neighbor." 1428 DEFVAL { 120 } 1429 ::= { ospfv3IfEntry 10 } 1431 ospfv3IfState OBJECT-TYPE 1432 SYNTAX INTEGER { 1433 down (1), 1434 loopback (2), 1435 waiting (3), 1436 pointToPoint (4), 1437 designatedRouter (5), 1438 backupDesignatedRouter (6), 1439 otherDesignatedRouter (7) 1440 } 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "The OSPFv3 Interface State." 1445 DEFVAL { down } 1446 ::= { ospfv3IfEntry 11 } 1448 ospfv3IfDesignatedRouter OBJECT-TYPE 1449 SYNTAX RouterID 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "The Router ID of the Designated Router." 1454 DEFVAL { '00000000'H } -- 0.0.0.0 1455 ::= { ospfv3IfEntry 12 } 1457 ospfv3IfBackupDesignatedRouter OBJECT-TYPE 1458 SYNTAX RouterID 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "The Router ID of the Backup Designated 1463 Router." 1464 DEFVAL { '00000000'H } -- 0.0.0.0 1465 ::= { ospfv3IfEntry 14 } 1467 ospfv3IfEvents OBJECT-TYPE 1468 SYNTAX Counter32 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "The number of times this OSPF interface has 1473 changed its state, or an error has occurred." 1474 ::= { ospfv3IfEntry 15 } 1476 ospfv3IfStatus OBJECT-TYPE 1477 SYNTAX RowStatus 1478 MAX-ACCESS read-create 1479 STATUS current 1480 DESCRIPTION 1481 "This variable displays the status of the en- 1482 try. Setting it to 'invalid' has the effect of 1483 rendering it inoperative. The internal effect 1484 (row removal) is implementation dependent." 1485 ::= { ospfv3IfEntry 17 } 1487 ospfv3IfMulticastForwarding OBJECT-TYPE 1488 SYNTAX INTEGER { 1489 blocked (1), -- no multicast forwarding 1490 multicast (2), -- using multicast address 1491 unicast (3) -- to each OSPFv3 neighbor 1492 } 1493 MAX-ACCESS read-create 1494 STATUS current 1495 DESCRIPTION 1496 "The way multicasts should forwarded on this 1497 interface; not forwarded, forwarded as data 1498 link multicasts, or forwarded as data link uni- 1499 casts. Data link multicasting is not meaning- 1500 ful on point to point and NBMA interfaces, and 1501 setting ospfv3MulticastForwarding to 0 effective- 1502 ly disables all multicast forwarding." 1503 DEFVAL { blocked } 1504 ::= { ospfv3IfEntry 18 } 1506 ospfv3IfDemand OBJECT-TYPE 1507 SYNTAX TruthValue 1508 MAX-ACCESS read-create 1509 STATUS current 1510 DESCRIPTION 1511 "Indicates whether Demand OSPFv3 procedures (hel- 1512 lo supression to FULL neighbors and setting the 1513 DoNotAge flag on proogated LSAs) should be per- 1514 formed on this interface." 1515 DEFVAL { false } 1516 ::= { ospfv3IfEntry 19 } 1518 ospfv3IfMetricValue OBJECT-TYPE 1519 SYNTAX Metric 1520 MAX-ACCESS read-create 1521 STATUS current 1522 DESCRIPTION 1523 "The metric assigned to this interface. 1524 The default value of the Metric is 1525 10^8 / ifSpeed." 1526 ::= { ospfv3IfEntry 20 } 1528 ospfv3IfLinkScopeLsaCount OBJECT-TYPE 1529 SYNTAX Gauge32 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "The total number of Link-Scope link-state advertisements 1534 in this link's link-state database." 1535 ::= { ospfv3IfEntry 21 } 1537 ospfv3IfLinkLsaCksumSum OBJECT-TYPE 1538 SYNTAX Integer32 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "The 32-bit unsigned sum of the Link-Scope link-state 1543 advertisements' LS checksums contained in this 1544 link's link-state database. The sum can be used 1545 to determine if there has been a change in a 1546 router's link state database, and to compare the 1547 link-state database of two routers." 1548 DEFVAL { 0 } 1549 ::= { ospfv3IfEntry 22 } 1551 ospfv3IfInstId OBJECT-TYPE 1552 SYNTAX Integer32 1553 MAX-ACCESS read-create 1554 STATUS current 1555 DESCRIPTION 1556 "Enables multiple instances of OSPFv3 to be run over 1557 a single link. Each protocol instance would be assigned 1558 a separate ID. This ID has local link significance only." 1559 DEFVAL { 0 } 1560 ::= { ospfv3IfEntry 23 } 1562 -- OSPFv3 Virtual Interface Table 1564 -- The Virtual Interface Table describes the virtual 1565 -- links that the OSPFv3 Process is configured to 1566 -- carry on. 1568 ospfv3VirtIfTable OBJECT-TYPE 1569 SYNTAX SEQUENCE OF Ospfv3VirtIfEntry 1570 MAX-ACCESS not-accessible 1571 STATUS current 1572 DESCRIPTION 1573 "Information about this router's virtual inter- 1574 faces." 1575 REFERENCE 1576 "OSPF Version 2, Appendix C.4 Virtual link 1577 parameters" 1578 ::= { ospfv3 8 } 1580 ospfv3VirtIfEntry OBJECT-TYPE 1581 SYNTAX Ospfv3VirtIfEntry 1582 MAX-ACCESS not-accessible 1583 STATUS current 1584 DESCRIPTION 1585 "Information about a single Virtual Interface." 1586 INDEX { ospfv3VirtIfAreaId, ospfv3VirtIfNeighbor } 1587 ::= { ospfv3VirtIfTable 1 } 1589 Ospfv3VirtIfEntry ::= 1590 SEQUENCE { 1591 ospfv3VirtIfAreaId 1592 AreaID, 1593 ospfv3VirtIfNeighbor 1594 RouterID, 1595 ospfv3VirtIfIndex 1596 Ipv6IfIndex, 1597 ospfv3VirtIfTransitDelay 1598 UpToMaxAge, 1599 ospfv3VirtIfRetransInterval 1600 UpToMaxAge, 1601 ospfv3VirtIfHelloInterval 1602 HelloRange, 1603 ospfv3VirtIfRtrDeadInterval 1604 PositiveInteger, 1605 ospfv3VirtIfState 1606 INTEGER, 1607 ospfv3VirtIfEvents 1608 Counter32, 1609 ospfv3VirtIfStatus 1610 RowStatus, 1611 ospfv3VirtIfLinkScopeLsaCount 1612 Gauge32, 1613 ospfv3VirtIfLinkLsaCksumSum 1614 Integer32 1615 } 1617 ospfv3VirtIfAreaId OBJECT-TYPE 1618 SYNTAX AreaID 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "The Transit Area that the Virtual Link 1623 traverses. By definition, this is not 0.0.0.0" 1624 ::= { ospfv3VirtIfEntry 1 } 1626 ospfv3VirtIfNeighbor OBJECT-TYPE 1627 SYNTAX RouterID 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "The Router ID of the Virtual Neighbor." 1632 ::= { ospfv3VirtIfEntry 2 } 1634 ospfv3VirtIfIndex OBJECT-TYPE 1635 SYNTAX Ipv6IfIndex 1636 MAX-ACCESS read-create 1637 STATUS current 1638 DESCRIPTION 1639 "The interface index of this OSPFv3 virtual interface. 1640 It must be unique among all the interface indices 1641 on the router." 1642 ::= { ospfv3VirtIfEntry 3 } 1644 ospfv3VirtIfTransitDelay OBJECT-TYPE 1645 SYNTAX UpToMaxAge 1646 MAX-ACCESS read-create 1647 STATUS current 1648 DESCRIPTION 1649 "The estimated number of seconds it takes to 1650 transmit a link- state update packet over this 1651 interface." 1652 DEFVAL { 1 } 1653 ::= { ospfv3VirtIfEntry 4 } 1655 ospfv3VirtIfRetransInterval OBJECT-TYPE 1656 SYNTAX UpToMaxAge 1657 MAX-ACCESS read-create 1658 STATUS current 1659 DESCRIPTION 1660 "The number of seconds between link-state ad- 1661 vertisement retransmissions, for adjacencies 1662 belonging to this interface. This value is 1663 also used when retransmitting database descrip- 1664 tion and link-state request packets. This 1665 value should be well over the expected round- 1666 trip time." 1667 DEFVAL { 5 } 1668 ::= { ospfv3VirtIfEntry 5 } 1670 ospfv3VirtIfHelloInterval OBJECT-TYPE 1671 SYNTAX HelloRange 1672 MAX-ACCESS read-create 1673 STATUS current 1674 DESCRIPTION 1675 "The length of time, in seconds, between the 1676 Hello packets that the router sends on the in- 1677 terface. This value must be the same for the 1678 virtual neighbor." 1679 DEFVAL { 10 } 1680 ::= { ospfv3VirtIfEntry 6 } 1682 ospfv3VirtIfRtrDeadInterval OBJECT-TYPE 1683 SYNTAX PositiveInteger 1684 MAX-ACCESS read-create 1685 STATUS current 1686 DESCRIPTION 1687 "The number of seconds that a router's Hello 1688 packets have not been seen before it's neigh- 1689 bors declare the router down. This should be 1690 some multiple of the Hello interval. This 1691 value must be the same for the virtual neigh- 1692 bor." 1693 DEFVAL { 60 } 1694 ::= { ospfv3VirtIfEntry 7 } 1696 ospfv3VirtIfState OBJECT-TYPE 1697 SYNTAX INTEGER { 1698 down (1), -- these use the same encoding 1699 pointToPoint (4) -- as the ospfv3IfTable 1700 } 1701 MAX-ACCESS read-only 1702 STATUS current 1703 DESCRIPTION 1704 "OSPF virtual interface states." 1705 DEFVAL { down } 1706 ::= { ospfv3VirtIfEntry 8 } 1708 ospfv3VirtIfEvents OBJECT-TYPE 1709 SYNTAX Counter32 1710 MAX-ACCESS read-only 1711 STATUS current 1712 DESCRIPTION 1713 "The number of state changes or error events on 1714 this Virtual Link" 1715 ::= { ospfv3VirtIfEntry 9 } 1717 ospfv3VirtIfStatus OBJECT-TYPE 1718 SYNTAX RowStatus 1719 MAX-ACCESS read-create 1720 STATUS current 1721 DESCRIPTION 1722 "This variable displays the status of the en- 1723 try. Setting it to 'invalid' has the effect of 1724 rendering it inoperative. The internal effect 1725 (row removal) is implementation dependent." 1726 ::= { ospfv3VirtIfEntry 10 } 1728 ospfv3VirtIfLinkScopeLsaCount OBJECT-TYPE 1729 SYNTAX Gauge32 1730 MAX-ACCESS read-only 1731 STATUS current 1732 DESCRIPTION 1733 "The total number of Link-Scope link-state advertisements 1734 in this virtual link's link-state database." 1735 ::= { ospfv3VirtIfEntry 11 } 1737 ospfv3VirtIfLinkLsaCksumSum OBJECT-TYPE 1738 SYNTAX Integer32 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "The 32-bit unsigned sum of the Link-Scope link-state 1743 advertisements' LS checksums contained in this 1744 virtual link's link-state database. The sum can be used 1745 to determine if there has been a change in a 1746 router's link state database, and to compare the 1747 link-state database of two routers." 1748 DEFVAL { 0 } 1749 ::= { ospfv3VirtIfEntry 12 } 1751 -- OSPFv3 Neighbor Table 1752 -- The OSPFv3 Neighbor Table describes all neighbors in 1753 -- the locality of the subject router. 1755 ospfv3NbrTable OBJECT-TYPE 1756 SYNTAX SEQUENCE OF Ospfv3NbrEntry 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "A table of non-virtual neighbor information." 1761 REFERENCE 1762 "OSPF Version 2, Section 10 The Neighbor Data 1763 Structure" 1764 ::= { ospfv3 9 } 1766 ospfv3NbrEntry OBJECT-TYPE 1767 SYNTAX Ospfv3NbrEntry 1768 MAX-ACCESS not-accessible 1769 STATUS current 1770 DESCRIPTION 1771 "The information regarding a single neighbor." 1772 REFERENCE 1773 "OSPF Version 2, Section 10 The Neighbor Data 1774 Structure" 1775 INDEX { ospfv3NbrIfIndex, ospfv3NbrRtrId } 1776 ::= { ospfv3NbrTable 1 } 1778 Ospfv3NbrEntry ::= 1779 SEQUENCE { 1780 ospfv3NbrIfIndex 1781 Ipv6IfIndex, 1782 ospfv3NbrRtrId 1783 RouterID, 1784 ospfv3NbrOptions 1785 Integer32, 1786 ospfv3NbrPriority 1787 DesignatedRouterPriority, 1788 ospfv3NbrState 1789 INTEGER, 1790 ospfv3NbrEvents 1791 Counter32, 1792 ospfv3NbrLsRetransQLen 1793 Gauge32, 1794 ospfv3NbmaNbrStatus 1795 RowStatus, 1797 ospfv3NbmaNbrPermanence 1798 INTEGER, 1799 ospfv3NbrHelloSuppressed 1800 TruthValue, 1801 ospfv3NbrIfId 1802 Ipv6IfIndex 1803 } 1805 ospfv3NbrIfIndex OBJECT-TYPE 1806 SYNTAX Ipv6IfIndex 1807 MAX-ACCESS read-only 1808 STATUS current 1809 DESCRIPTION 1810 "The local link ID of the link over which the 1811 neighbor can be reached." 1812 ::= { ospfv3NbrEntry 1 } 1814 ospfv3NbrRtrId OBJECT-TYPE 1815 SYNTAX RouterID 1816 MAX-ACCESS read-only 1817 STATUS current 1818 DESCRIPTION 1819 "A 32-bit integer (represented as a type IpAd- 1820 dress) uniquely identifying the neighboring 1821 router in the Autonomous System." 1822 ::= { ospfv3NbrEntry 2 } 1824 ospfv3NbrOptions OBJECT-TYPE 1825 SYNTAX Integer32 1826 MAX-ACCESS read-only 1827 STATUS current 1828 DESCRIPTION 1829 "A Bit Mask corresponding to the neighbor's op- 1830 tions field." 1831 DEFVAL { 0 } 1832 ::= { ospfv3NbrEntry 3 } 1834 ospfv3NbrPriority OBJECT-TYPE 1835 SYNTAX DesignatedRouterPriority 1836 MAX-ACCESS read-create 1837 STATUS current 1838 DESCRIPTION 1839 "The priority of this neighbor in the designat- 1840 ed router election algorithm. The value 0 sig- 1841 nifies that the neighbor is not eligible to be- 1842 come the designated router on this particular 1843 network." 1844 DEFVAL { 1 } 1845 ::= { ospfv3NbrEntry 4 } 1847 ospfv3NbrState OBJECT-TYPE 1848 SYNTAX INTEGER { 1849 down (1), 1850 attempt (2), 1851 init (3), 1852 twoWay (4), 1853 exchangeStart (5), 1854 exchange (6), 1855 loading (7), 1856 full (8) 1857 } 1858 MAX-ACCESS read-only 1859 STATUS current 1860 DESCRIPTION 1861 "The State of the relationship with this Neigh- 1862 bor." 1863 REFERENCE 1864 "OSPF Version 2, Section 10.1 Neighbor States" 1865 DEFVAL { down } 1866 ::= { ospfv3NbrEntry 5 } 1868 ospfv3NbrEvents OBJECT-TYPE 1869 SYNTAX Counter32 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "The number of times this neighbor relationship 1874 has changed state, or an error has occurred." 1875 ::= { ospfv3NbrEntry 6 } 1877 ospfv3NbrLsRetransQLen OBJECT-TYPE 1878 SYNTAX Gauge32 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION 1882 "The current length of the retransmission 1883 queue." 1884 ::= { ospfv3NbrEntry 7 } 1886 ospfv3NbmaNbrStatus OBJECT-TYPE 1887 SYNTAX RowStatus 1888 MAX-ACCESS read-create 1889 STATUS current 1890 DESCRIPTION 1891 "This variable displays the status of the en- 1892 try. Setting it to 'invalid' has the effect of 1893 rendering it inoperative. The internal effect 1894 (row removal) is implementation dependent." 1895 ::= { ospfv3NbrEntry 8 } 1897 ospfv3NbmaNbrPermanence OBJECT-TYPE 1898 SYNTAX INTEGER { 1899 dynamic (1), -- learned through protocol 1900 permanent (2) -- configured address 1901 } 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "This variable displays the status of the en- 1906 try. 'dynamic' and 'permanent' refer to how 1907 the neighbor became known." 1908 DEFVAL { permanent } 1909 ::= { ospfv3NbrEntry 9 } 1911 ospfv3NbrHelloSuppressed OBJECT-TYPE 1912 SYNTAX TruthValue 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "Indicates whether Hellos are being suppressed 1917 to the neighbor" 1918 ::= { ospfv3NbrEntry 10 } 1920 ospfv3NbrIfId OBJECT-TYPE 1921 SYNTAX Ipv6IfIndex 1922 MAX-ACCESS read-only 1923 STATUS current 1924 DESCRIPTION 1925 "The interface ID that the neighbor advertises 1926 in its Hello Packets on this link, that is, the 1927 neighbor's local interface index." 1928 ::= { ospfv3NbrEntry 11 } 1930 -- OSPFv3 Virtual Neighbor Table 1932 -- This table describes all virtual neighbors. 1933 -- Since Virtual Links are configured in the 1934 -- virtual interface table, this table is read-only. 1936 ospfv3VirtNbrTable OBJECT-TYPE 1937 SYNTAX SEQUENCE OF Ospfv3VirtNbrEntry 1938 MAX-ACCESS not-accessible 1939 STATUS current 1940 DESCRIPTION 1941 "A table of virtual neighbor information." 1942 REFERENCE 1943 "OSPF Version 2, Section 15 Virtual Links" 1944 ::= { ospfv3 10 } 1946 ospfv3VirtNbrEntry OBJECT-TYPE 1947 SYNTAX Ospfv3VirtNbrEntry 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "Virtual neighbor information." 1953 INDEX { ospfv3VirtNbrArea, ospfv3VirtNbrRtrId } 1954 ::= { ospfv3VirtNbrTable 1 } 1956 Ospfv3VirtNbrEntry ::= 1957 SEQUENCE { 1958 ospfv3VirtNbrArea 1959 AreaID, 1960 ospfv3VirtNbrRtrId 1961 RouterID, 1962 ospfv3VirtNbrIfIndex 1963 Ipv6IfIndex, 1964 ospfv3VirtNbrIpv6Addr 1965 Ipv6Address, 1966 ospfv3VirtNbrOptions 1967 Integer32, 1968 ospfv3VirtNbrState 1969 INTEGER, 1970 ospfv3VirtNbrEvents 1971 Counter32, 1972 ospfv3VirtNbrLsRetransQLen 1973 Gauge32, 1974 ospfv3VirtNbrHelloSuppressed 1975 TruthValue, 1976 ospfv3VirtNbrIfId 1977 Ipv6IfIndex 1978 } 1980 ospfv3VirtNbrArea OBJECT-TYPE 1981 SYNTAX AreaID 1982 MAX-ACCESS read-only 1983 STATUS current 1984 DESCRIPTION 1985 "The Transit Area Identifier." 1986 ::= { ospfv3VirtNbrEntry 1 } 1988 ospfv3VirtNbrRtrId OBJECT-TYPE 1989 SYNTAX RouterID 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 "A 32-bit integer uniquely identifying the 1994 neighboring router in the Autonomous System." 1995 ::= { ospfv3VirtNbrEntry 2 } 1997 ospfv3VirtNbrIfIndex OBJECT-TYPE 1998 SYNTAX Ipv6IfIndex 1999 MAX-ACCESS read-only 2000 STATUS current 2001 DESCRIPTION 2002 "The local link ID for the virtual link over 2003 which the neighbor can be reached." 2004 ::= { ospfv3VirtNbrEntry 3 } 2006 ospfv3VirtNbrIpv6Addr OBJECT-TYPE 2007 SYNTAX Ipv6Address 2008 MAX-ACCESS read-only 2009 STATUS current 2010 DESCRIPTION 2011 "The IPv6 address used to reach this Virtual Neighbor. 2012 It must be a Site-Local or Global scope address." 2013 ::= { ospfv3VirtNbrEntry 4 } 2015 ospfv3VirtNbrOptions OBJECT-TYPE 2016 SYNTAX Integer32 2017 MAX-ACCESS read-only 2018 STATUS current 2019 DESCRIPTION 2020 "A Bit Mask corresponding to the neighbor's op- 2021 tions field." 2022 ::= { ospfv3VirtNbrEntry 5 } 2024 ospfv3VirtNbrState OBJECT-TYPE 2025 SYNTAX INTEGER { 2026 down (1), 2027 attempt (2), 2028 init (3), 2029 twoWay (4), 2030 exchangeStart (5), 2031 exchange (6), 2032 loading (7), 2033 full (8) 2034 } 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "The state of the Virtual Neighbor Relation- 2039 ship." 2040 ::= { ospfv3VirtNbrEntry 6 } 2042 ospfv3VirtNbrEvents OBJECT-TYPE 2043 SYNTAX Counter32 2044 MAX-ACCESS read-only 2045 STATUS current 2046 DESCRIPTION 2047 "The number of times this virtual link has 2048 changed its state, or an error has occurred." 2050 ::= { ospfv3VirtNbrEntry 7 } 2052 ospfv3VirtNbrLsRetransQLen OBJECT-TYPE 2053 SYNTAX Gauge32 2054 MAX-ACCESS read-only 2055 STATUS current 2056 DESCRIPTION 2057 "The current length of the retransmission 2058 queue." 2059 ::= { ospfv3VirtNbrEntry 8 } 2061 ospfv3VirtNbrHelloSuppressed OBJECT-TYPE 2062 SYNTAX TruthValue 2063 MAX-ACCESS read-only 2064 STATUS current 2065 DESCRIPTION 2066 "Indicates whether Hellos are being suppressed 2067 to the neighbor" 2068 ::= { ospfv3VirtNbrEntry 9 } 2070 ospfv3VirtNbrIfId OBJECT-TYPE 2071 SYNTAX Ipv6IfIndex 2072 MAX-ACCESS read-only 2073 STATUS current 2074 DESCRIPTION 2075 "The interface ID that the neighbor advertises 2076 in its Hello Packets on this virtual link, that is, 2077 the neighbor's local interface index." 2078 ::= { ospfv3VirtNbrEntry 10 } 2080 -- 2081 -- The OSPFv3 Area Aggregate Table 2082 -- 2084 ospfv3AreaAggregateTable OBJECT-TYPE 2085 SYNTAX SEQUENCE OF Ospfv3AreaAggregateEntry 2086 MAX-ACCESS not-accessible 2087 STATUS current 2088 DESCRIPTION 2089 "A range of IPv6 prefixes specified by a 2090 prefix/prefix length pair. Note that if 2091 ranges are configured such that one range sub- 2092 sumes another range the most specific match is 2093 the preferred one." 2094 ::= { ospfv3 11 } 2096 ospfv3AreaAggregateEntry OBJECT-TYPE 2097 SYNTAX Ospfv3AreaAggregateEntry 2098 MAX-ACCESS not-accessible 2099 STATUS current 2100 DESCRIPTION 2101 "A range of IPv6 prefixes specified by a 2102 prefix/prefix length pair. Note that if 2103 ranges are configured such that one range sub- 2104 sumes another range the most specific match is 2105 the preferred one." 2106 REFERENCE 2107 "OSPF Version 2, Appendix C.2 Area parameters" 2108 INDEX { ospfv3AreaAggregateAreaID, ospfv3AreaAggregateAreaLsdbType, 2109 ospfv3AreaAggregateIndex } 2110 ::= { ospfv3AreaAggregateTable 1 } 2112 Ospfv3AreaAggregateEntry ::= 2113 SEQUENCE { 2114 ospfv3AreaAggregateAreaID 2115 AreaID, 2116 ospfv3AreaAggregateAreaLsdbType 2117 INTEGER, 2118 ospfv3AreaAggregateIndex 2119 INTEGER, 2120 ospfv3AreaAggregatePrefix 2121 Ipv6AddressPrefix, 2122 ospfv3AreaAggregatePrefixLen 2123 INTEGER, 2124 ospfv3AreaAggregateStatus 2125 RowStatus, 2126 ospfv3AreaAggregateEffect 2127 INTEGER 2128 } 2130 ospfv3AreaAggregateAreaID OBJECT-TYPE 2131 SYNTAX AreaID 2132 MAX-ACCESS read-only 2133 STATUS current 2134 DESCRIPTION 2135 "The Area the Address Aggregate is to be found 2136 within." 2137 REFERENCE 2138 "OSPF Version 2, Appendix C.2 Area parameters" 2139 ::= { ospfv3AreaAggregateEntry 1 } 2141 ospfv3AreaAggregateAreaLsdbType OBJECT-TYPE 2142 SYNTAX INTEGER { 2143 interAreaPrefixLsa (8195), -- 0x2003 2144 nssaExternalLsa (8199) -- 0x2007 2145 } 2146 MAX-ACCESS read-only 2147 STATUS current 2148 DESCRIPTION 2149 "The type of the Address Aggregate. This field 2150 specifies the Area Lsdb type that this Address Ag- 2151 gregate applies to." 2152 REFERENCE 2153 "OSPF Version 2, Appendix A.4.1 The Link State 2154 Advertisement header" 2155 ::= { ospfv3AreaAggregateEntry 2 } 2157 ospfv3AreaAggregateIndex OBJECT-TYPE 2158 SYNTAX INTEGER (1..2147483647) 2159 MAX-ACCESS read-only 2160 STATUS current 2161 DESCRIPTION 2162 "A unique identifier for this aggregate table entry." 2163 ::= { ospfv3AreaAggregateEntry 3 } 2165 ospfv3AreaAggregatePrefix OBJECT-TYPE 2166 SYNTAX Ipv6AddressPrefix 2167 MAX-ACCESS read-create 2168 STATUS current 2169 DESCRIPTION 2170 "The IPv6 Prefix." 2171 REFERENCE 2172 "OSPF Version 2, Appendix C.2 Area parameters" 2173 ::= { ospfv3AreaAggregateEntry 4 } 2175 ospfv3AreaAggregatePrefixLen OBJECT-TYPE 2176 SYNTAX INTEGER ( 3..128 ) 2177 UNITS "bits" 2178 MAX-ACCESS read-create 2179 STATUS current 2180 DESCRIPTION 2181 "The length of the prefix (in bits). A prefix can 2182 not be shorter than 3 bits." 2183 REFERENCE 2184 "OSPF Version 2, Appendix C.2 Area parameters" 2185 ::= { ospfv3AreaAggregateEntry 5 } 2187 ospfv3AreaAggregateStatus OBJECT-TYPE 2188 SYNTAX RowStatus 2189 MAX-ACCESS read-create 2190 STATUS current 2191 DESCRIPTION 2192 "This variable displays the status of the en- 2193 try. Setting it to 'invalid' has the effect of 2194 rendering it inoperative. The internal effect 2195 (row removal) is implementation dependent." 2196 ::= { ospfv3AreaAggregateEntry 6 } 2198 ospfv3AreaAggregateEffect OBJECT-TYPE 2199 SYNTAX INTEGER { 2200 advertiseMatching (1), 2201 doNotAdvertiseMatching (2) 2202 } 2203 MAX-ACCESS read-create 2204 STATUS current 2205 DESCRIPTION 2206 "Prefixes subsumed by ranges either trigger the 2207 advertisement of the indicated aggregate (ad- 2208 vertiseMatching), or result in the prefix not 2209 being advertised at all outside the area." 2210 DEFVAL { advertiseMatching } 2211 ::= { ospfv3AreaAggregateEntry 7 } 2213 -- conformance information 2215 ospfv3Conformance OBJECT IDENTIFIER ::= { ospfv3 12 } 2216 ospfv3Groups OBJECT IDENTIFIER ::= { ospfv3Conformance 1 } 2217 ospfv3Compliances OBJECT IDENTIFIER ::= { ospfv3Conformance 2 } 2219 -- compliance statements 2221 ospfv3Compliance MODULE-COMPLIANCE 2222 STATUS current 2223 DESCRIPTION 2224 "The compliance statement " 2225 MODULE -- this module 2226 MANDATORY-GROUPS { 2227 ospfv3BasicGroup, 2228 ospfv3AreaGroup, 2229 ospfv3IfGroup, 2230 ospfv3VirtIfGroup, 2231 ospfv3NbrGroup, 2232 ospfv3VirtNbrGroup, 2233 ospfv3AreaAggregateGroup 2234 } 2235 ::= { ospfv3Compliances 1 } 2237 -- units of conformance 2239 ospfv3BasicGroup OBJECT-GROUP 2240 OBJECTS { 2241 ospfv3RouterId, 2242 ospfv3AdminStat, 2243 ospfv3VersionNumber, 2244 ospfv3AreaBdrRtrStatus, 2245 ospfv3ASBdrRtrStatus, 2246 ospfv3AsScopeLsaCount, 2247 ospfv3AsScopeLsaCksumSum, 2248 ospfv3OriginateNewLsas, 2249 ospfv3RxNewLsas, 2250 ospfv3ExtAreaLsdbLimit, 2251 ospfv3MulticastExtensions, 2252 ospfv3ExitOverflowInterval, 2253 ospfv3DemandExtensions 2254 } 2255 STATUS current 2256 DESCRIPTION 2257 "These objects are required for OSPFv3 systems." 2258 ::= { ospfv3Groups 1 } 2260 ospfv3AreaGroup OBJECT-GROUP 2261 OBJECTS { 2262 ospfv3AreaId, 2263 ospfv3ImportAsExtern, 2264 ospfv3SpfRuns, 2265 ospfv3AreaBdrRtrCount, 2266 ospfv3AsBdrRtrCount, 2267 ospfv3AreaScopeLsaCount, 2268 ospfv3AreaScopeLsaCksumSum, 2269 ospfv3AreaSummary, 2270 ospfv3AreaStatus, 2271 ospfv3StubMetric 2272 } 2273 STATUS current 2274 DESCRIPTION 2275 "These objects are required for OSPFv3 systems 2276 supporting areas." 2277 ::= { ospfv3Groups 2 } 2279 ospfv3AsLsdbGroup OBJECT-GROUP 2280 OBJECTS { 2281 ospfv3AsLsdbType, 2282 ospfv3AsLsdbRouterId, 2283 ospfv3AsLsdbLsid, 2284 ospfv3AsLsdbSequence, 2285 ospfv3AsLsdbAge, 2286 ospfv3AsLsdbChecksum, 2287 ospfv3AsLsdbAdvertisement 2288 } 2289 STATUS current 2290 DESCRIPTION 2291 "These objects are required for OSPFv3 systems 2292 that display their AS-scope link state database." 2293 ::= { ospfv3Groups 3 } 2295 ospfv3AreaLsdbGroup OBJECT-GROUP 2296 OBJECTS { 2297 ospfv3AreaLsdbAreaId, 2298 ospfv3AreaLsdbType, 2299 ospfv3AreaLsdbRouterId, 2300 ospfv3AreaLsdbLsid, 2301 ospfv3AreaLsdbSequence, 2302 ospfv3AreaLsdbAge, 2303 ospfv3AreaLsdbChecksum, 2304 ospfv3AreaLsdbAdvertisement 2305 } 2306 STATUS current 2307 DESCRIPTION 2308 "These objects are required for OSPF6 systems 2309 that display their Area-scope link state database." 2310 ::= { ospfv3Groups 4 } 2312 ospfv3LinkLsdbGroup OBJECT-GROUP 2313 OBJECTS { 2314 ospfv3LinkLsdbIfIndex, 2315 ospfv3LinkLsdbType, 2316 ospfv3LinkLsdbRouterId, 2317 ospfv3LinkLsdbLsid, 2318 ospfv3LinkLsdbSequence, 2319 ospfv3LinkLsdbAge, 2320 ospfv3LinkLsdbChecksum, 2321 ospfv3LinkLsdbAdvertisement 2322 } 2323 STATUS current 2324 DESCRIPTION 2325 "These objects are required for OSPFv3 systems 2326 that display their Link-scope link state database." 2327 ::= { ospfv3Groups 5 } 2329 ospfv3HostGroup OBJECT-GROUP 2330 OBJECTS { 2331 ospfv3HostIpv6Address, 2332 ospfv3HostMetric, 2333 ospfv3HostStatus, 2334 ospfv3HostAreaID 2335 } 2336 STATUS current 2337 DESCRIPTION 2338 "These objects are required for OSPFv3 systems 2339 that support attached hosts." 2340 ::= { ospfv3Groups 6 } 2342 ospfv3IfGroup OBJECT-GROUP 2343 OBJECTS { 2344 ospfv3IfIndex, 2345 ospfv3IfAreaId, 2346 ospfv3IfType, 2347 ospfv3IfAdminStat, 2348 ospfv3IfRtrPriority, 2349 ospfv3IfTransitDelay, 2350 ospfv3IfRetransInterval, 2351 ospfv3IfHelloInterval, 2352 ospfv3IfRtrDeadInterval, 2353 ospfv3IfPollInterval, 2354 ospfv3IfState, 2355 ospfv3IfDesignatedRouter, 2356 ospfv3IfBackupDesignatedRouter, 2357 ospfv3IfEvents, 2358 ospfv3IfStatus, 2359 ospfv3IfMulticastForwarding, 2360 ospfv3IfDemand, 2361 ospfv3IfMetricValue, 2362 ospfv3IfLinkScopeLsaCount, 2363 ospfv3IfLinkLsaCksumSum, 2364 ospfv3IfInstId 2365 } 2366 STATUS current 2367 DESCRIPTION 2368 "These interface objects are required for OSPFv3 systems." 2369 ::= { ospfv3Groups 7 } 2371 ospfv3VirtIfGroup OBJECT-GROUP 2372 OBJECTS { 2373 ospfv3VirtIfAreaId, 2374 ospfv3VirtIfNeighbor, 2375 ospfv3VirtIfIndex, 2376 ospfv3VirtIfTransitDelay, 2377 ospfv3VirtIfRetransInterval, 2378 ospfv3VirtIfHelloInterval, 2379 ospfv3VirtIfRtrDeadInterval, 2380 ospfv3VirtIfState, 2381 ospfv3VirtIfEvents, 2382 ospfv3VirtIfStatus, 2383 ospfv3VirtIfLinkScopeLsaCount, 2384 ospfv3VirtIfLinkLsaCksumSum 2385 } 2386 STATUS current 2387 DESCRIPTION 2388 "These virtual interface objects are required for OSPFv3 systems." 2390 ::= { ospfv3Groups 8 } 2392 ospfv3NbrGroup OBJECT-GROUP 2393 OBJECTS { 2394 ospfv3NbrIfIndex, 2395 ospfv3NbrRtrId, 2396 ospfv3NbrOptions, 2397 ospfv3NbrPriority, 2398 ospfv3NbrState, 2399 ospfv3NbrEvents, 2400 ospfv3NbrLsRetransQLen, 2401 ospfv3NbmaNbrStatus, 2402 ospfv3NbmaNbrPermanence, 2403 ospfv3NbrHelloSuppressed, 2404 ospfv3NbrIfId 2405 } 2406 STATUS current 2407 DESCRIPTION 2408 "These neighbor objects are required for OSPFv3 systems." 2409 ::= { ospfv3Groups 9 } 2411 ospfv3VirtNbrGroup OBJECT-GROUP 2412 OBJECTS { 2413 ospfv3VirtNbrArea, 2414 ospfv3VirtNbrRtrId, 2415 ospfv3VirtNbrIfIndex, 2416 ospfv3VirtNbrIpv6Addr, 2417 ospfv3VirtNbrOptions, 2418 ospfv3VirtNbrState, 2419 ospfv3VirtNbrEvents, 2420 ospfv3VirtNbrLsRetransQLen, 2421 ospfv3VirtNbrHelloSuppressed, 2422 ospfv3VirtNbrIfId 2423 } 2424 STATUS current 2425 DESCRIPTION 2426 "These virtual neighbor objects are required for OSPFv3 systems." 2427 ::= { ospfv3Groups 10 } 2429 ospfv3AreaAggregateGroup OBJECT-GROUP 2430 OBJECTS { 2431 ospfv3AreaAggregateAreaID, 2432 ospfv3AreaAggregateAreaLsdbType, 2433 ospfv3AreaAggregateIndex, 2434 ospfv3AreaAggregatePrefix, 2435 ospfv3AreaAggregatePrefixLen, 2436 ospfv3AreaAggregateStatus, 2437 ospfv3AreaAggregateEffect 2438 } 2439 STATUS current 2440 DESCRIPTION 2441 "These area aggregate objects are required for OSPFv3 systems." 2442 ::= { ospfv3Groups 11 } 2444 END 2445 5. Acknowledgements 2447 This document is based on the MIB for OSPF version 2 by Rob 2448 Coltun and Fred Baker [18]. 2450 6. References 2452 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An 2453 Architecture for Describing SNMP Management Frameworks", 2454 RFC 2571, April 1999 2456 [2] Rose, M., and K. McCloghrie, "Structure and 2457 Identification of Management Information for TCP/IP-based 2458 Internets", STD 16, RFC 1155, May 1990 2460 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2461 STD 16, RFC 1212, March 1991 2463 [4] M. Rose, "A Convention for Defining Traps for use with 2464 the SNMP", RFC 1215, March 1991 2466 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2467 Rose, M., and S. Waldbusser, "Structure of Management 2468 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2469 1999 2471 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2472 Rose, M., and S. Waldbusser, "Textual Conventions for 2473 SMIv2", STD 58, RFC 2579, April 1999 2475 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2476 Rose, M., and S. Waldbusser, "Conformance Statements for 2477 SMIv2", STD 58, RFC 2580, April 1999 2479 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2480 "Simple Network Management Protocol", STD 15, RFC 1157, 2481 May 1990. 2483 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2484 "Introduction to Community-based SNMPv2", RFC 1901, 2485 January 1996. 2487 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2488 "Transport Mappings for Version 2 of the Simple Network 2489 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2491 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2492 "Message Processing and Dispatching for the Simple 2493 Network Management Protocol (SNMP)", RFC 2572, April 1999 2495 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model 2496 (USM) for version 3 of the Simple Network Management 2497 Protocol (SNMPv3)", RFC 2574, April 1999 2499 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2500 "Protocol Operations for Version 2 of the Simple Network 2501 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2503 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2504 Applications", RFC 2573, April 1999 2506 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2507 Access Control Model (VACM) for the Simple Network 2508 Management Protocol (SNMP)", RFC 2575, April 1999 2510 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, 2511 "Introduction to Version 3 of the Internet-standard 2512 Network Management Framework", RFC 2570, April 1999 2514 [17] Deering, S., and R. Hinden, "Internet Protocol, Version 6 2515 (IPv6) Specification", RFC 2460, December 1998. 2517 [18] Baker, F., and Coltun, R., "OSPF Version 2 Management 2518 Information Base", RFC 1850, cisco Systems, FORE Systems, 2519 November 1995. 2521 [19] Coltun, R., Ferguson, D., Moy, J., "OSPF for IPv6", RFC 2522 2740, Siara Systems, Juniper Networks, Sycamore Networks, 2523 December 1999. 2525 [20] Haskin, D., Onishi, S., "Management Information Base for 2526 IP Version 6: Textual Conventions and General Group", RFC 2527 2465, Bay Networks, December 1998. 2529 [21] Moy, J., "OSPF Version 2", RFC 2328, Ascend 2530 Communications, Inc., April 1998. 2532 7. Security Considerations 2534 There are a number of management objects defined in this MIB 2535 that have a MAX-ACCESS clause of read-write and/or read- 2536 create. Such objects may be considered sensitive or 2537 vulnerable in some network environments. The support for SET 2538 operations in a non-secure environment without proper 2539 protection can have a negative effect on network operations. 2541 8. Author's Address 2543 Dan Joyal 2544 Nortel Networks, Inc. 2545 600 Technology Park Drive 2546 Billerica, MA 01821 2547 email: djoyal@nortelnetworks.com 2549 9. Full Copyright Statement 2551 Copyright (C) The Internet Society (1999). All Rights 2552 Reserved. 2554 This document and translations of it may be copied and 2555 furnished to others, and derivative works that comment on or 2556 otherwise explain it or assist in its implementation may be 2557 prepared, copied, published and distributed, in whole or in 2558 part, without restriction of any kind, provided that the above 2559 copyright notice and this paragraph are included on all such 2560 copies and derivative works. However, this document itself 2561 may not be modified in any way, such as by removing the 2562 copyright notice or references to the Internet Society or 2563 other Internet organizations, except as needed for the purpose 2564 of developing Internet standards in which case the procedures 2565 for copyrights defined in the Internet Standards process must 2566 be followed, or as required to translate it into languages 2567 other than English. 2569 The limited permissions granted above are perpetual and will 2570 not be revoked by the Internet Society or its successors or 2571 assigns. 2573 This document and the information contained herein is provided 2574 on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2575 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2576 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE 2577 USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 2578 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 2579 PARTICULAR PURPOSE. 2581 Acknowledgement 2583 Funding for the RFC Editor function is currently provided 2584 by the Internet Society.