idnits 2.17.1 draft-ietf-ospf-mib-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** 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 an Authors' Addresses Section. ** There are 205 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 8 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 486 has weird spacing: '... 32-bit integ...' == Line 489 has weird spacing: '... By conve...' == Line 490 has weird spacing: '... should defau...' == Line 501 has weird spacing: '... "The admin...' == Line 502 has weird spacing: '.... The value...' == (200 more instances...) == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (November 1992) is 11484 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) -- Missing reference section? '7' on line 2425 looks like a reference -- Missing reference section? '3' on line 2401 looks like a reference -- Missing reference section? '8' on line 2431 looks like a reference -- Missing reference section? '13' on line 107 looks like a reference -- Missing reference section? '9' on line 2437 looks like a reference -- Missing reference section? '1' on line 2390 looks like a reference -- Missing reference section? '2' on line 2396 looks like a reference -- Missing reference section? '4' on line 2407 looks like a reference -- Missing reference section? '5' on line 2413 looks like a reference -- Missing reference section? '6' on line 2419 looks like a reference -- Missing reference section? '10' on line 2441 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 8 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft OSPF MIB November 1992 4 OSPF Version 2 Management Information Base 6 Tue Nov 3 11:27:41 PST 1992 8 Fred Baker 10 Advanced Computer Communications 11 315 Bollay Drive 12 Santa Barbara, California 93117 14 fbaker@acc.com 16 Rob Coltun 18 Consultant 19 (301) 340-9416 21 rcoltun@ni.umd.edu 23 1. Status of this Memo 25 This document is an Internet Draft. Internet Drafts are 26 working documents of the Internet Engineering Task Force 27 (IETF), its Areas, and its Working Groups. Note that other 28 groups may also distribute working documents as Internet 29 Drafts. 31 Internet Drafts are draft documents valid for a maximum of six 32 months. Internet Drafts may be updated, replaced, or obsoleted 33 by other documents at any time. It is not appropriate to use 34 Internet Drafts as reference material or to cite them other 35 than as a "working draft" or "work in progress." 37 Please check the I-D abstract listing contained in each 38 Internet Draft directory to learn the current status of this 39 or any other Internet Draft. 41 2. Abstract 43 This memo defines a portion of the Management Information Base 44 (MIB) for use with network management protocols in TCP/IP- 45 based internets. In particular, it defines objects for 46 managing the Open Shortest Path First Routing Protocol. 48 This memo does not, in its draft form, specify a standard for 49 the Internet community. 51 3. The Network Management Framework 53 The Internet-standard Network Management Framework consists of 54 three components. They are: 56 RFC 1155 which defines the SMI, the mechanisms used for 57 describing and naming objects for the purpose of management. 58 RFC 1212 defines a more concise description mechanism, which 59 is wholly consistent with the SMI. 61 RFC 1156 which defines MIB-I, the core set of managed objects 62 for the Internet suite of protocols. RFC 1213 defines MIB-II, 63 an evolution of MIB-I based on implementation experience and 64 new operational requirements. 66 RFC 1157 which defines the SNMP, the protocol used for network 67 access to managed objects. 69 The Framework permits new objects to be defined for the 70 purpose of experimentation and evaluation. 72 4. Objects 74 Managed objects are accessed via a virtual information store, 75 termed the Management Information Base or MIB. Objects in the 76 MIB are defined using the subset of Abstract Syntax Notation 77 One (ASN.1) [7] defined in the SMI. In particular, each 78 object has a name, a syntax, and an encoding. The name is an 79 object identifier, an administratively assigned name, which 80 specifies an object type. The object type together with an 81 object instance serves to uniquely identify a specific 82 instantiation of the object. For human convenience, we often 83 use a textual string, termed the OBJECT DESCRIPTOR, to also 84 refer to the object type. 86 The syntax of an object type defines the abstract data 87 structure corresponding to that object type. The ASN.1 88 language is used for this purpose. However, the SMI [3] 89 purposely restricts the ASN.1 constructs which may be used. 90 These restrictions are explicitly made for simplicity. 92 The encoding of an object type is simply how that object type 93 is represented using the object type's syntax. Implicitly 94 tied to the notion of an object type's syntax and encoding is 95 how the object type is represented when being transmitted on 96 the network. 98 The SMI specifies the use of the basic encoding rules of ASN.1 99 [8], subject to the additional requirements imposed by the 100 SNMP. 102 4.1. Format of Definitions 104 Section 6 contains contains the specification of all object 105 types contained in this MIB module. The object types are 106 defined using the conventions defined in the SMI, as amended 107 by the extensions specified in RFC1212 [13]. 109 4.2. Changes from RFC 1253 111 The changes from RFC 1253 are the following: 113 (1) The textual convention PositiveInteger was changed from 114 1..'FFFFFFFF'h to 1..'7FFFFFFF'h at the request of 115 Marshall Rose. 117 (2) The textual convention TOSType was changed to reflect the 118 TOS values defined in the Router Requirements Draft, and 119 in accordance with the IP Forwarding Table MIB's values. 121 (3) The names of some objects were changed, conforming to the 122 convention that an acronym (for example, LSA) is a single 123 word ("Lsa") in most SNMP names. 125 (4) textual changes were made to make the MIB readable by 126 Dave Perkins' SMIC MIB Compiler in addition to Mosy. 127 This involved changing the case of some characters in 128 certain names and removing the DEFVAL clauses for 129 Counters. (This would appear to violate RFC 1212, which 130 explicitly states that DEFVALs are for the purpose of 131 initializing read-only objects???) 133 (5) The variables ospfAreaStatus and ospfIfStatus were added, 134 having been overlooked in the original MIB. 136 (6) The range of the variable ospfLsdbType was extended to 137 include multicastLink (Multicast LSA) and 138 nssaExternalLink (NSSA LSA). 140 (7) The variable ospfIfMetricMetric was renamed 141 ospfIfMetricValue, and the following text was removed 142 from its description: 144 "The value FFFF is distinguished to mean 'no route via 145 this TOS'." 147 (8) The range of the variable ospfNBMANbrStatus was extended 148 from by this means, dynamically learned and configured 149 neighbors can be distinguished. 151 (9) The DESCRIPTION of the variable ospfNbrIpAddr was changed 152 from 154 "The IP address of this neighbor." 156 to 158 "The IP address this neighbor is using in its IP Source 159 Address. Note that, on addressless links, this will not 160 be 0.0.0.0, but the address of another of the neighbor's 161 interfaces." 162 This is by way of clarification and does not change the 163 specification. 165 (10) The OSPF External Link State Database was added. The 166 OSPF Link State Database used to display all LSAs stored; 167 in this MIB, it displays all but the AS External LSAs. 168 This is because there are usually a large number of 169 External LSAs, and they are relicated in all non-Stub 170 Areas. 172 (11) The variable ospfAreaSummary was added to control the 173 import of summary LSAs into stub areas. If it is 174 noAreaSummary (default) the router will neither originate 175 nor propagate summary LSAs into the stub area. It will 176 rely entirely on its default route. If it is 177 sendAreaSummary, the router will both summarize and 178 propagate summary LSAs. 180 (12) The general variable ospfExtLsdbLimit was introduced to 181 help handle LSDB overflow. 183 (13) The use of the IP Forwarding Table is defined. 185 (14) The range of the variable ospfAreaRangeStatus was 186 extended to include the concepts advertiseMatching, 187 invalid (delete), and doNotAdvertiseMatching. This 188 permits the network manager to hide a subnet within an 189 area. 191 (15) Normally, the border router of a stub area advertises a 192 default route as an OSPF network summary. An NSSA border 193 router will generate a type-5 LSA indicating a default 194 route, and import it into the NSSA. ospfStubMetricType 195 (ospf internal, type 1 external, or type 2 external) 196 indicates the type of the default metric advertised. 198 (16) ospfMulticastForwarding is added to the OSPF General 199 Group. This indicates the router's ability to forward IP 200 multicast (class D) datagrams. 202 (17) ospfIfMulticastForwarding in the Interface Group. It 203 indicates whether, and if so, how, multicasts should be 204 forwarded on the interface. 206 5. Overview 208 5.1. Textual Conventions 210 Several new data types are introduced as a textual convention 211 in this MIB document. These textual conventions enhance the 212 readability of the specification and can ease comparison with 213 other specifications if appropriate. It should be noted that 214 the introduction of the these textual conventions has no 215 effect on either the syntax nor the semantics of any managed 216 objects. The use of these is merely an artifact of the 217 explanatory method used. Objects defined in terms of one of 218 these methods are always encoded by means of the rules that 219 define the primitive type. Hence, no changes to the SMI or 220 the SNMP are necessary to accommodate these textual 221 conventions which are adopted merely for the convenience of 222 readers and writers in pursuit of the elusive goal of clear, 223 concise, and unambiguous MIB documents. 225 The new data types are AreaID, RouterID, TOSType, Metric, 226 BigMetric, TruthValue, Status, Validation, PositiveInteger, 227 HelloRange, UpToMaxAge, InterfaceIndex, and 228 DesignatedRouterPriority. 230 5.2. Structure of MIB 232 The MIB is composed of the following sections: 233 General Variables 234 Area Data Structure 235 Area Stub Metric Table 236 Link State Database 237 Address Range Table 238 Host Table 239 Interface Table 240 Interface Metric Table 241 Virtual Interface Table 242 Neighbor Table 243 Virtual Neighbor Table 244 External Link State Database 246 5.2.1. General Variables 248 The General Variables are about what they sound like; 249 variables which are global to the OSPF Process. 251 5.2.2. Area Data Structure and Area Stub Metric Table 253 The Area Data Structure describes the OSPF Areas that the 254 router participates in. The Area Stub Metric Table describes 255 the metrics advertised into a stub area by the default 256 router(s). 258 5.2.3. Link State Database and External Link State Database 260 The Link State Database is provided primarily to provide 261 detailed information for network debugging. 263 5.2.4. Address Table and Host Tables 265 The Address Range Table and Host Table are provided to view 266 configured Network Summary and Host Route information. 268 5.2.5. Interface and Interface Metric Tables 270 The Interface Table and the Interface Metric Table together 271 describe the various IP interfaces to OSPF. The metrics are 272 placed in separate tables in order to simplify dealing with 273 multiple types of service, and to provide flexibility in the 274 event that the IP TOS definition is changed in the future. A 275 Default Value specification is supplied for the TOS 0 276 (default) metric. 278 5.2.6. Virtual Interface Table 280 Likewise, the Virtual Interface Table describe virtual links 281 to the OSPF Process. 283 5.2.7. Neighbor and Virtual Neighbor Tables 285 The Neighbor Table and the Virtual Neighbor Table describe the 286 neighbors to the OSPF Process. 288 5.3. Conceptual Row Creation 290 For the benefit of row-creation in "conceptual" (see [9]) 291 tables, DEFVAL (Default Value) clauses are included in the 292 definitions in section 5, suggesting values which an agent 293 should use for instances of variables which need to be created 294 due to a Set-Request, but which are not specified in the Set- 295 Request. DEFVAL clauses have not been specified for some 296 objects which are read-only, implying that they are zeroed 297 upon row creation. These objects are of the SYNTAX Counter or 298 Gauge. 300 For those objects not having a DEFVAL clause, both management 301 stations and agents should heed the Robustness Principle of 302 the Internet (see RFC-791): 304 "be liberal in what you accept, conservative in what you 305 send" 307 That is, management stations should include as many of these 308 columnar objects as possible (e.g., all read-write objects) in 309 a Set-Request when creating a conceptual row; agents should 310 accept a Set-Request with as few of these as they need (e.g., 311 the minimum contents of a row creating SET consists of those 312 objects for which, as they cannot be intuited, no default is 313 specified.). 315 There are numerous read-write objects in this MIB, as it is 316 designed for SNMP management of the protocol, not just SNMP 317 monitoring of its state. However, in the absence of a 318 standard SNMP Security architecture, it is acceptable for 319 implementations to implement these as read-only with an 320 alternative interface for their modification. 322 5.4. Default Configuration 324 OSPF is a powerful routing protocol, equipped with features to 325 handle virtually any configuration requirement that might 326 reasonably be found within an Autonomous System. With this 327 power comes a fair degree of complexity, which the sheer 328 number of objects in the MIB will attest to. Care has 329 therefore been taken, in constructing this MIB, to define 330 default values for virtually every object, to minimize the 331 amount of parameterization required in the typical case. That 332 default configuration is as follows: 334 Given the following assumptions: 336 - IP has already been configured 338 - The ifTable has already been configured 339 - ifSpeed is estimated by the interface drivers 341 - The OSPF Process automatically discovers all IP 342 Interfaces and creates corresponding OSPF Interfaces 344 - The TOS 0 metrics are autonomously derived from ifSpeed 346 - The OSPF Process automatically creates the Areas required 347 for the Interfaces 349 The simplest configuration of an OSPF process requires that: 351 - The OSPF Process be Enabled. 353 This can be accomplished with a single SET: 354 ospfAdminStat := enabled. 356 The configured system will have the following attributes: 358 - The RouterID will be one of the IP addresses of the 359 device 361 - The device will be neither an Area Border Router nor an 362 Autonomous System Border Router. 364 - Every IP Interface, with or without an address, will be 365 an OSPF Interface. 367 - The AreaID of each interface will be 0.0.0.0, the 368 Backbone. 370 - Authentication will be disabled 372 - All Broadcast and Point to Point interfaces will be 373 operational. NBMA Interfaces require the configuration 374 of at least one neighbor. 376 - Timers on all direct interfaces will be: 377 Hello Interval: 10 seconds 378 Dead Timeout: 40 Seconds 379 Retransmission: 5 Seconds 380 Transit Delay: 1 Second 381 Poll Interval: 120 Seconds 383 - no direct links to hosts will be configured. 385 - no addresses will be summarized 387 - Metrics, being a measure of bit duration, are unambiguous 388 and intelligent. 390 - No Virtual Links will be configured. 392 6. Definitions 394 RFC1253-MIB DEFINITIONS ::= BEGIN 396 IMPORTS 397 Counter, Gauge, IpAddress 398 FROM RFC1155-SMI 399 mib-2 400 FROM RFC1213-MIB 401 OBJECT-TYPE 402 FROM RFC-1212; 404 -- This MIB module uses the extended OBJECT-TYPE macro as 405 -- defined in [9]. 407 ospf OBJECT IDENTIFIER ::= { mib-2 14 } 409 -- The Area ID, in OSPF, has the same format as an IP Address, 410 -- but has the function of defining a summarization point for 411 -- Link State Advertisements 413 AreaID ::= IpAddress 415 -- The Router ID, in OSPF, has the same format as an IP Address, 416 -- but identifies the router independent of its IP Address. 418 RouterID ::= IpAddress 420 -- The OSPF Metric is defined as an unsigned value in the range 422 Metric ::= INTEGER (1..'FFFF'h) 423 BigMetric ::= INTEGER (1..'FFFFFF'h) 425 -- Boolean Values 427 TruthValue ::= INTEGER { true (1), false (2) } 429 -- Status Values 431 Status ::= INTEGER { enabled (1), disabled (2) } 433 -- Row Creation/Deletion Values 435 Validation ::= INTEGER { valid (1), invalid (2) } 436 -- Time Durations measured in seconds 438 PositiveInteger ::= INTEGER (1..'7FFFFFFF'h) 439 HelloRange ::= INTEGER (1..'FFFF'h) 440 UpToMaxAge ::= INTEGER (1..3600) 442 -- The range of ifIndex, i.e. (1..ifNumber) 444 InterfaceIndex ::= INTEGER 446 -- Potential Priorities for the Designated Router Election 448 DesignatedRouterPriority ::= INTEGER (0..'FF'h) 450 -- Type of Service is defined as a mapping to the IP Type of 451 -- Service Flags as defined in the IP Forwarding Table MIB 453 -- +-----+-----+-----+-----+-----+-----+-----+-----+ 454 -- | | | | 455 -- | PRECEDENCE | TYPE OF SERVICE | 0 | 456 -- | | | | 457 -- +-----+-----+-----+-----+-----+-----+-----+-----+ 459 -- IP TOS IP TOS 460 -- Field Policy Field Policy 461 -- Contents Code Contents Code 462 -- 0 0 0 0 ==> 0 0 0 0 1 ==> 2 463 -- 0 0 1 0 ==> 4 0 0 1 1 ==> 6 464 -- 0 1 0 0 ==> 8 0 1 0 1 ==> 10 465 -- 0 1 1 0 ==> 12 0 1 1 1 ==> 14 466 -- 1 0 0 0 ==> 16 1 0 0 1 ==> 18 467 -- 1 0 1 0 ==> 20 1 0 1 1 ==> 22 468 -- 1 1 0 0 ==> 24 1 1 0 1 ==> 26 469 -- 1 1 1 0 ==> 28 1 1 1 1 ==> 30 471 -- The remaining values are left for future definition. 473 TOSType ::= INTEGER (0..31) 474 -- OSPF General Variables 476 -- These parameters apply globally to the Router's 477 -- OSPF Process. 479 ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 } 481 ospfRouterId OBJECT-TYPE 482 SYNTAX RouterID 483 ACCESS read-write 484 STATUS mandatory 485 DESCRIPTION 486 "A 32-bit integer uniquely identifying the 487 router in the Autonomous System. 489 By convention, to ensure uniqueness, this 490 should default to the value of one of the 491 router's IP interface addresses." 492 REFERENCE 493 "OSPF Version 2, C.1 Global parameters" 494 ::= { ospfGeneralGroup 1 } 496 ospfAdminStat OBJECT-TYPE 497 SYNTAX Status 498 ACCESS read-write 499 STATUS mandatory 500 DESCRIPTION 501 "The administrative status of OSPF in the 502 router. The value 'enabled' denotes that the 503 OSPF Process is active on at least one inter- 504 face; 'disabled' disables it on all inter- 505 faces." 506 ::= { ospfGeneralGroup 2 } 508 ospfVersionNumber OBJECT-TYPE 509 SYNTAX INTEGER { version2 (2) } 510 ACCESS read-only 511 STATUS mandatory 512 DESCRIPTION 513 "The current version number of the OSPF proto- 514 col is 2." 515 REFERENCE 516 "OSPF Version 2, Title" 517 ::= { ospfGeneralGroup 3 } 519 ospfAreaBdrRtrStatus OBJECT-TYPE 520 SYNTAX TruthValue 521 ACCESS read-only 522 STATUS mandatory 523 DESCRIPTION 524 "A flag to note whether this router is an area 525 border router." 526 REFERENCE 527 "OSPF Version 2, Section 3 Splitting the AS into 528 Areas" 529 ::= { ospfGeneralGroup 4 } 531 ospfASBdrRtrStatus OBJECT-TYPE 532 SYNTAX TruthValue 533 ACCESS read-write 534 STATUS mandatory 535 DESCRIPTION 536 "A flag to note whether this router is config- 537 ured as an Autonomous System border router." 538 REFERENCE 539 "OSPF Version 2, Section 3.3 Classification of 540 routers" 541 ::= { ospfGeneralGroup 5 } 543 ospfExternLsaCount OBJECT-TYPE 544 SYNTAX Gauge 545 ACCESS read-only 546 STATUS mandatory 547 DESCRIPTION 548 "The number of external (LS type 5) link-state 549 advertisements in the link-state database." 550 REFERENCE 551 "OSPF Version 2, Appendix A.4.5 AS external link 552 advertisements" 553 ::= { ospfGeneralGroup 6 } 555 ospfExternLsaCksumSum OBJECT-TYPE 556 SYNTAX INTEGER 557 ACCESS read-only 558 STATUS mandatory 559 DESCRIPTION 560 "The 32-bit unsigned sum of the LS checksums of 561 the external link-state advertisements con- 562 tained in the link-state database. This sum 563 can be used to determine if there has been a 564 change in a router's link state database, and 565 to compare the link-state database of two 566 routers." 567 ::= { ospfGeneralGroup 7 } 569 ospfTOSSupport OBJECT-TYPE 570 SYNTAX TruthValue 571 ACCESS read-write 572 STATUS mandatory 573 DESCRIPTION 574 "The router's support for type-of-service rout- 575 ing." 576 REFERENCE 577 "OSPF Version 2, Appendix F.1.2 Optional TOS 578 support" 579 ::= { ospfGeneralGroup 8 } 581 ospfOriginateNewLsas OBJECT-TYPE 582 SYNTAX Counter 583 ACCESS read-only 584 STATUS mandatory 585 DESCRIPTION 586 "The number of new link-state advertisements 587 that have been originated. This number is in- 588 cremented each time the router originates a new 589 LSA." 590 ::= { ospfGeneralGroup 9 } 592 ospfRxNewLsas OBJECT-TYPE 593 SYNTAX Counter 594 ACCESS read-only 595 STATUS mandatory 596 DESCRIPTION 597 "The number of link-state advertisements re- 598 ceived determined to be new instantiations. 599 This number does not include newer instantia- 600 tions of self-originated link-state advertise- 601 ments." 602 ::= { ospfGeneralGroup 10 } 604 ospfExtLsdbLimit OBJECT-TYPE 605 SYNTAX INTEGER (-1..'7FFFFFFF'h) 606 ACCESS read-write 607 STATUS mandatory 608 DESCRIPTION 609 "The maximum number of external link-state en- 610 tries that can be stored in the link-state da- 611 tabase. If the value is -1, then there is no 612 limit." 613 DEFVAL { -1 } 614 ::= { ospfGeneralGroup 11 } 616 ospfMulticastForwarding OBJECT-TYPE 617 SYNTAX INTEGER 618 -- 0 no multicast forwarding 619 -- 1 intra-area multicast forwarding 620 -- 2 inter-area multicast forwarding 621 -- 3 inter-area and intra-area multicast forwarding 622 -- 4 inter-AS multicast forwarding 623 -- 5 inter-AS and intra-Area multicast forwarding 624 -- 6 inter-AS and inter-Area multicast forwarding 625 -- 7 multicast forwarding anywhere 626 ACCESS read-write 627 STATUS mandatory 628 DESCRIPTION 629 "A bit mask indicating the limits on Network 630 Layer multicast (Class D) forwarding. It is 631 represented as a sum of the following: 632 if intra-Area forwarding is permitted, 1; else 0 633 if inter-Area forwarding is permitted, 2; else 0 634 if inter-AS forwarding is permitted, 4; else 0 635 By default, no multicast forwarding is enabled." 636 DEFVAL { 0 } 637 ::= { ospfGeneralGroup 12 } 639 -- The OSPF Area Data Structure contains information 640 -- regarding the various areas. The interfaces and 641 -- virtual links are configured as part of these areas. 642 -- Area 0.0.0.0, by definition, is the Backbone Area 644 ospfAreaTable OBJECT-TYPE 645 SYNTAX SEQUENCE OF OspfAreaEntry 646 ACCESS not-accessible 647 STATUS mandatory 648 DESCRIPTION 649 "Information describing the configured parame- 650 ters and cumulative statistics of the router's 651 attached areas." 652 REFERENCE 653 "OSPF Version 2, Section 6 The Area Data Struc- 654 ture" 655 ::= { ospf 2 } 657 ospfAreaEntry OBJECT-TYPE 658 SYNTAX OspfAreaEntry 659 ACCESS not-accessible 660 STATUS mandatory 661 DESCRIPTION 662 "Information describing the configured parame- 663 ters and cumulative statistics of one of the 664 router's attached areas." 665 INDEX { ospfAreaId } 666 ::= { ospfAreaTable 1 } 668 OspfAreaEntry ::= 669 SEQUENCE { 670 ospfAreaId 671 AreaID, 672 ospfAuthType 673 INTEGER, 674 ospfImportAsExtern 675 INTEGER, 676 ospfSpfRuns 677 Counter, 678 ospfAreaBdrRtrCount 679 Gauge, 680 ospfAsBdrRtrCount 681 Gauge, 683 ospfAreaLsaCount 684 Gauge, 685 ospfAreaLsaCksumSum 686 INTEGER, 687 ospfAreaSummary 688 INTEGER, 689 ospfAreaStatus 690 Validation 691 } 693 ospfAreaId OBJECT-TYPE 694 SYNTAX AreaID 695 ACCESS read-write 696 STATUS mandatory 697 DESCRIPTION 698 "A 32-bit integer uniquely identifying an area. 699 Area ID 0.0.0.0 is used for the OSPF backbone." 700 REFERENCE 701 "OSPF Version 2, Appendix C.2 Area parameters" 702 ::= { ospfAreaEntry 1 } 704 ospfAuthType OBJECT-TYPE 705 SYNTAX INTEGER 706 -- none (0), 707 -- simplePassword (1) 708 -- reserved for specification by IANA (> 1) 709 ACCESS read-write 710 STATUS mandatory 711 DESCRIPTION 712 "The authentication type specified for an area. 713 Additional authentication types may be assigned 714 locally on a per Area basis." 715 REFERENCE 716 "OSPF Version 2, Appendix E Authentication" 717 DEFVAL { 0 } -- no authentication, by default 718 ::= { ospfAreaEntry 2 } 720 ospfImportAsExtern OBJECT-TYPE 721 SYNTAX INTEGER { 722 importExternal (1), 723 importNoExternal (2), 724 importNssa (3) 725 } 726 ACCESS read-write 727 STATUS mandatory 728 DESCRIPTION 729 "The area's support for importing AS external 730 link- state advertisements." 731 REFERENCE 732 "OSPF Version 2, Appendix C.2 Area parameters" 733 DEFVAL { importExternal } 734 ::= { ospfAreaEntry 3 } 736 ospfSpfRuns OBJECT-TYPE 737 SYNTAX Counter 738 ACCESS read-only 739 STATUS mandatory 740 DESCRIPTION 741 "The number of times that the intra-area route 742 table has been calculated using this area's 743 link-state database. This is typically done 744 using Dijkstra's algorithm." 745 ::= { ospfAreaEntry 4 } 747 ospfAreaBdrRtrCount OBJECT-TYPE 748 SYNTAX Gauge 749 ACCESS read-only 750 STATUS mandatory 751 DESCRIPTION 752 "The total number of area border routers reach- 753 able within this area. This is initially zero, 754 and is calculated in each SPF Pass." 755 ::= { ospfAreaEntry 5 } 757 ospfAsBdrRtrCount OBJECT-TYPE 758 SYNTAX Gauge 759 ACCESS read-only 760 STATUS mandatory 761 DESCRIPTION 762 "The total number of Autonomous System border 763 routers reachable within this area. This is 764 initially zero, and is calculated in each SPF 765 Pass." 766 ::= { ospfAreaEntry 6 } 768 ospfAreaLsaCount OBJECT-TYPE 769 SYNTAX Gauge 770 ACCESS read-only 771 STATUS mandatory 772 DESCRIPTION 773 "The total number of link-state advertisements 774 in this area's link-state database, excluding 775 AS External LSA's." 776 ::= { ospfAreaEntry 7 } 778 ospfAreaLsaCksumSum OBJECT-TYPE 779 SYNTAX INTEGER 780 ACCESS read-only 781 STATUS mandatory 782 DESCRIPTION 783 "The 32-bit unsigned sum of the link-state ad- 784 vertisements' LS checksums contained in this 785 area's link-state database. This sum excludes 786 external (LS type 5) link-state advertisements. 787 The sum can be used to determine if there has 788 been a change in a router's link state data- 789 base, and to compare the link-state database of 790 two routers." 791 DEFVAL { 0 } 792 ::= { ospfAreaEntry 8 } 794 ospfAreaSummary OBJECT-TYPE 795 SYNTAX INTEGER { 796 noAreaSummary (1), 797 sendAreaSummary (2) 798 } 799 ACCESS read-only 800 STATUS mandatory 801 DESCRIPTION 802 "The variable ospfAreaSummary controls the im- 803 port of summary LSAs into stub areas. It has 804 no effect on other areas. 806 If it is noAreaSummary, the router will neither 807 originate nor propagate summary LSAs into the 808 stub area. It will rely entirely on its de- 809 fault route. 811 If it is sendAreaSummary, the router will both 812 summarize and propagate summary LSAs." 813 DEFVAL { noAreaSummary } 814 ::= { ospfAreaEntry 9 } 816 ospfAreaStatus OBJECT-TYPE 817 SYNTAX Validation 818 ACCESS read-write 819 STATUS mandatory 820 DESCRIPTION 821 "This variable displays the status of the en- 822 try. Setting it to 'invalid' has the effect of 823 rendering it inoperative. The internal effect 824 (row removal) is implementation dependent." 825 DEFVAL { valid } 826 ::= { ospfAreaEntry 10 } 828 -- OSPF Area Default Metric Table 830 -- The OSPF Area Default Metric Table describes the metrics 831 -- that a default Area Border Router will advertise into a 832 -- Stub area. 834 ospfStubAreaTable OBJECT-TYPE 835 SYNTAX SEQUENCE OF OspfStubAreaEntry 836 ACCESS not-accessible 837 STATUS mandatory 838 DESCRIPTION 839 "The set of metrics that will be advertised by 840 a default Area Border Router into a stub area." 841 REFERENCE 842 "OSPF Version 2, Appendix C.2, Area Parameters" 843 ::= { ospf 3 } 845 ospfStubAreaEntry OBJECT-TYPE 846 SYNTAX OspfStubAreaEntry 847 ACCESS not-accessible 848 STATUS mandatory 849 DESCRIPTION 850 "The metric for a given Type of Service that 851 will be advertised by a default Area Border 852 Router into a stub area." 853 REFERENCE 854 "OSPF Version 2, Appendix C.2, Area Parameters" 855 INDEX { ospfStubAreaID, ospfStubTOS } 856 ::= { ospfStubAreaTable 1 } 858 OspfStubAreaEntry ::= 859 SEQUENCE { 860 ospfStubAreaID 861 AreaID, 862 ospfStubTOS 863 TOSType, 864 ospfStubMetric 865 BigMetric, 866 ospfStubStatus 867 Validation, 868 ospfStubMetricType 869 INTEGER 870 } 871 ospfStubAreaID OBJECT-TYPE 872 SYNTAX AreaID 873 ACCESS read-write 874 STATUS mandatory 875 DESCRIPTION 876 "The 32 bit identifier for the Stub Area. On 877 creation, this can be derived from the in- 878 stance." 879 ::= { ospfStubAreaEntry 1 } 881 ospfStubTOS OBJECT-TYPE 882 SYNTAX TOSType 883 ACCESS read-write 884 STATUS mandatory 885 DESCRIPTION 886 "The Type of Service associated with the 887 metric. On creation, this can be derived from 888 the instance." 889 ::= { ospfStubAreaEntry 2 } 891 ospfStubMetric OBJECT-TYPE 892 SYNTAX BigMetric 893 ACCESS read-write 894 STATUS mandatory 895 DESCRIPTION 896 "The metric value applied at the indicated type 897 of service. By default, this equals the least 898 metric at the type of service among the inter- 899 faces to other areas." 900 ::= { ospfStubAreaEntry 3 } 902 ospfStubStatus OBJECT-TYPE 903 SYNTAX Validation 904 ACCESS read-write 905 STATUS mandatory 906 DESCRIPTION 907 "This variable displays the status of the en- 908 try. Setting it to 'invalid' has the effect of 909 rendering it inoperative. The internal effect 910 (row removal) is implementation dependent." 911 DEFVAL { valid } 912 ::= { ospfStubAreaEntry 4 } 914 ospfStubMetricType OBJECT-TYPE 915 SYNTAX INTEGER { 916 ospfMetric (1), -- OSPF Metric 917 comparableCost (2), -- external type 1 918 nonComparable (3) -- external type 2 919 } 920 ACCESS read-write 921 STATUS mandatory 922 DESCRIPTION 923 "This variable displays the type of metric ad- 924 vertised as a default route." 925 DEFVAL { ospfMetric } 926 ::= { ospfStubAreaEntry 5 } 928 -- OSPF Link State Database 930 -- The Link State Database contains the Link State 931 -- Advertisements from throughout the areas that the 932 -- device is attached to. 934 ospfLsdbTable OBJECT-TYPE 935 SYNTAX SEQUENCE OF OspfLsdbEntry 936 ACCESS not-accessible 937 STATUS mandatory 938 DESCRIPTION 939 "The OSPF Process's Link State Database." 940 REFERENCE 941 "OSPF Version 2, Section 12 Link State Adver- 942 tisements" 943 ::= { ospf 4 } 945 ospfLsdbEntry OBJECT-TYPE 946 SYNTAX OspfLsdbEntry 947 ACCESS not-accessible 948 STATUS mandatory 949 DESCRIPTION 950 "A single Link State Advertisement." 951 INDEX { ospfLsdbAreaId, ospfLsdbType, 952 ospfLsdbLsid, ospfLsdbRouterId } 953 ::= { ospfLsdbTable 1 } 955 OspfLsdbEntry ::= 956 SEQUENCE { 957 ospfLsdbAreaId 958 AreaID, 959 ospfLsdbType 960 INTEGER, 961 ospfLsdbLsid 962 IpAddress, 963 ospfLsdbRouterId 964 RouterID, 965 ospfLsdbSequence 966 INTEGER, 967 ospfLsdbAge 968 INTEGER, 969 ospfLsdbChecksum 970 INTEGER, 972 ospfLsdbAdvertisement 973 OCTET STRING 974 } 976 ospfLsdbAreaId OBJECT-TYPE 977 SYNTAX AreaID 978 ACCESS read-only 979 STATUS mandatory 980 DESCRIPTION 981 "The 32 bit identifier of the Area from which 982 the LSA was received." 983 REFERENCE 984 "OSPF Version 2, Appendix C.2 Area parameters" 985 ::= { ospfLsdbEntry 1 } 987 -- External Link State Advertisements are permitted 988 -- for backward compatibility, but should be displayed in 989 -- the ospfExtLsdbTable rather than here. 991 ospfLsdbType OBJECT-TYPE 992 SYNTAX INTEGER { 993 routerLink (1), 994 networkLink (2), 995 summaryLink (3), 996 asSummaryLink (4), 997 asExternalLink (5), -- but see ospfExtLsdbTable 998 multicastLink (6), 999 nssaExternalLink (7) 1000 } 1001 ACCESS read-only 1002 STATUS mandatory 1003 DESCRIPTION 1004 "The type of the link state advertisement. 1005 Each link state type has a separate advertise- 1006 ment format." 1007 REFERENCE 1008 "OSPF Version 2, Appendix A.4.1 The Link State 1009 Advertisement header" 1010 ::= { ospfLsdbEntry 2 } 1012 ospfLsdbLsid OBJECT-TYPE 1013 SYNTAX IpAddress 1014 ACCESS read-only 1015 STATUS mandatory 1016 DESCRIPTION 1017 "The Link State ID is an LS Type Specific field 1018 containing either a Router ID or an IP Address; 1019 it identifies the piece of the routing domain 1020 that is being described by the advertisement." 1021 REFERENCE 1022 "OSPF Version 2, Section 12.1.4 Link State ID" 1023 ::= { ospfLsdbEntry 3 } 1025 ospfLsdbRouterId OBJECT-TYPE 1026 SYNTAX RouterID 1027 ACCESS read-only 1028 STATUS mandatory 1029 DESCRIPTION 1030 "The 32 bit number that uniquely identifies the 1031 originating router in the Autonomous System." 1032 REFERENCE 1033 "OSPF Version 2, Appendix C.1 Global parameters" 1034 ::= { ospfLsdbEntry 4 } 1036 -- Note that the OSPF Sequence Number is a 32 bit signed 1037 -- integer. It starts with the value '80000001'h, 1038 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1039 -- Thus, a typical sequence number will be very negative. 1041 ospfLsdbSequence OBJECT-TYPE 1042 SYNTAX INTEGER 1043 ACCESS read-only 1044 STATUS mandatory 1045 DESCRIPTION 1046 "The sequence number field is a signed 32-bit 1047 integer. It is used to detect old and dupli- 1048 cate link state advertisements. The space of 1049 sequence numbers is linearly ordered. The 1050 larger the sequence number the more recent the 1051 advertisement." 1052 REFERENCE 1053 "OSPF Version 2, Section 12.1.6 LS sequence 1054 number" 1055 ::= { ospfLsdbEntry 5 } 1057 ospfLsdbAge OBJECT-TYPE 1058 SYNTAX INTEGER -- Should be 0..MaxAge 1059 ACCESS read-only 1060 STATUS mandatory 1061 DESCRIPTION 1062 "This field is the age of the link state adver- 1063 tisement in seconds." 1064 REFERENCE 1065 "OSPF Version 2, Section 12.1.1 LS age" 1066 ::= { ospfLsdbEntry 6 } 1068 ospfLsdbChecksum OBJECT-TYPE 1069 SYNTAX INTEGER 1070 ACCESS read-only 1071 STATUS mandatory 1072 DESCRIPTION 1073 "This field is the checksum of the complete 1074 contents of the advertisement, excepting the 1075 age field. The age field is excepted so that 1076 an advertisement's age can be incremented 1077 without updating the checksum. The checksum 1078 used is the same that is used for ISO connec- 1079 tionless datagrams; it is commonly referred to 1080 as the Fletcher checksum." 1081 REFERENCE 1082 "OSPF Version 2, Section 12.1.7 LS checksum" 1083 ::= { ospfLsdbEntry 7 } 1085 ospfLsdbAdvertisement OBJECT-TYPE 1086 SYNTAX OCTET STRING 1087 ACCESS read-only 1088 STATUS mandatory 1089 DESCRIPTION 1090 "The entire Link State Advertisement, including 1091 its header." 1092 REFERENCE 1093 "OSPF Version 2, Section 12 Link State Adver- 1094 tisements" 1095 ::= { ospfLsdbEntry 8 } 1097 -- Address Range Table 1099 -- The Address Range Table acts as an adjunct to the Area 1100 -- Table; It describes those Address Range Summaries that 1101 -- are configured to be propagated from an Area to reduce 1102 -- the amount of information about it which is known beyond 1103 -- its borders. 1105 ospfAreaRangeTable OBJECT-TYPE 1106 SYNTAX SEQUENCE OF OspfAreaRangeEntry 1107 ACCESS not-accessible 1108 STATUS mandatory 1109 DESCRIPTION 1110 "A range if IP addresses specified by an IP 1111 address/IP network mask pair. For example, 1112 class B address range of X.X.X.X with a network 1113 mask of 255.255.0.0 includes all IP addresses 1114 from X.X.0.0 to X.X.255.255" 1115 REFERENCE 1116 "OSPF Version 2, Appendix C.2 Area parameters" 1117 ::= { ospf 5 } 1119 ospfAreaRangeEntry OBJECT-TYPE 1120 SYNTAX OspfAreaRangeEntry 1121 ACCESS not-accessible 1122 STATUS mandatory 1123 DESCRIPTION 1124 "A range if IP addresses specified by an IP 1125 address/IP network mask pair. For example, 1126 class B address range of X.X.X.X with a network 1127 mask of 255.255.0.0 includes all IP addresses 1128 from X.X.0.0 to X.X.255.255" 1129 REFERENCE 1130 "OSPF Version 2, Appendix C.2 Area parameters" 1131 INDEX { ospfAreaRangeAreaID, ospfAreaRangeNet } 1132 ::= { ospfAreaRangeTable 1 } 1134 OspfAreaRangeEntry ::= 1135 SEQUENCE { 1136 ospfAreaRangeAreaID 1137 AreaID, 1138 ospfAreaRangeNet 1139 IpAddress, 1141 ospfAreaRangeMask 1142 IpAddress, 1143 ospfAreaRangeStatus 1144 INTEGER 1145 } 1147 ospfAreaRangeAreaID OBJECT-TYPE 1148 SYNTAX AreaID 1149 ACCESS read-write 1150 STATUS mandatory 1151 DESCRIPTION 1152 "The Area the Address Range is to be found 1153 within." 1154 REFERENCE 1155 "OSPF Version 2, Appendix C.2 Area parameters" 1156 ::= { ospfAreaRangeEntry 1 } 1158 ospfAreaRangeNet OBJECT-TYPE 1159 SYNTAX IpAddress 1160 ACCESS read-write 1161 STATUS mandatory 1162 DESCRIPTION 1163 "The IP Address of the Net or Subnet indicated 1164 by the range." 1165 REFERENCE 1166 "OSPF Version 2, Appendix C.2 Area parameters" 1167 ::= { ospfAreaRangeEntry 2 } 1169 ospfAreaRangeMask OBJECT-TYPE 1170 SYNTAX IpAddress 1171 ACCESS read-write 1172 STATUS mandatory 1173 DESCRIPTION 1174 "The Subnet Mask that pertains to the Net or 1175 Subnet." 1176 REFERENCE 1177 "OSPF Version 2, Appendix C.2 Area parameters" 1178 ::= { ospfAreaRangeEntry 3 } 1180 ospfAreaRangeStatus OBJECT-TYPE 1181 SYNTAX INTEGER { 1182 advertiseMatching (1), 1183 invalid (2), 1184 doNotAdvertiseMatching (3) 1185 } 1186 ACCESS read-write 1187 STATUS mandatory 1188 DESCRIPTION 1189 "This variable displays the status of the en- 1190 try. Setting it to 'invalid' has the effect of 1191 rendering it inoperative. The internal effect 1192 (row removal) is implementation dependent. 1194 Subnets subsumed by ranges either trigger the 1195 advertisement of the indicated summary (adver- 1196 tiseMatching), or result in the subnet's not 1197 being advertised at all outside the area." 1198 DEFVAL { advertiseMatching } 1199 ::= { ospfAreaRangeEntry 4 } 1201 -- OSPF Host Table 1203 -- The Host/Metric Table indicates what hosts are directly 1204 -- attached to the Router, and what metrics and types of 1205 -- service should be advertised for them. 1207 ospfHostTable OBJECT-TYPE 1208 SYNTAX SEQUENCE OF OspfHostEntry 1209 ACCESS not-accessible 1210 STATUS mandatory 1211 DESCRIPTION 1212 "The list of Hosts, and their metrics, that the 1213 router will advertise as host routes." 1214 REFERENCE 1215 "OSPF Version 2, Appendix C.6 Host route param- 1216 eters" 1217 ::= { ospf 6 } 1219 ospfHostEntry OBJECT-TYPE 1220 SYNTAX OspfHostEntry 1221 ACCESS not-accessible 1222 STATUS mandatory 1223 DESCRIPTION 1224 "A metric to be advertised, for a given type of 1225 service, when a given host is reachable." 1226 INDEX { ospfHostIpAddress, ospfHostTOS } 1227 ::= { ospfHostTable 1 } 1229 OspfHostEntry ::= 1230 SEQUENCE { 1231 ospfHostIpAddress 1232 IpAddress, 1233 ospfHostTOS 1234 TOSType, 1235 ospfHostMetric 1236 Metric, 1237 ospfHostStatus 1238 Validation 1239 } 1240 ospfHostIpAddress OBJECT-TYPE 1241 SYNTAX IpAddress 1242 ACCESS read-write 1243 STATUS mandatory 1244 DESCRIPTION 1245 "The IP Address of the Host." 1246 REFERENCE 1247 "OSPF Version 2, Appendix C.6 Host route parame- 1248 ters" 1249 ::= { ospfHostEntry 1 } 1251 ospfHostTOS OBJECT-TYPE 1252 SYNTAX TOSType 1253 ACCESS read-write 1254 STATUS mandatory 1255 DESCRIPTION 1256 "The Type of Service of the route being config- 1257 ured." 1258 REFERENCE 1259 "OSPF Version 2, Appendix C.6 Host route parame- 1260 ters" 1261 ::= { ospfHostEntry 2 } 1263 ospfHostMetric OBJECT-TYPE 1264 SYNTAX Metric 1265 ACCESS read-write 1266 STATUS mandatory 1267 DESCRIPTION 1268 "The Metric to be advertised." 1269 REFERENCE 1270 "OSPF Version 2, Appendix C.6 Host route parame- 1271 ters" 1272 ::= { ospfHostEntry 3 } 1274 ospfHostStatus OBJECT-TYPE 1275 SYNTAX Validation 1276 ACCESS read-write 1277 STATUS mandatory 1278 DESCRIPTION 1279 "This variable displays the status of the en- 1280 try. Setting it to 'invalid' has the effect of 1281 rendering it inoperative. The internal effect 1282 (row removal) is implementation dependent." 1283 DEFVAL { valid } 1284 ::= { ospfHostEntry 4 } 1286 -- OSPF Interface Table 1288 -- The OSPF Interface Table augments the ipAddrTable 1289 -- with OSPF specific information. 1291 ospfIfTable OBJECT-TYPE 1292 SYNTAX SEQUENCE OF OspfIfEntry 1293 ACCESS not-accessible 1294 STATUS mandatory 1295 DESCRIPTION 1296 "The OSPF Interface Table describes the inter- 1297 faces from the viewpoint of OSPF." 1298 REFERENCE 1299 "OSPF Version 2, Appendix C.3 Router interface 1300 parameters" 1301 ::= { ospf 7 } 1303 ospfIfEntry OBJECT-TYPE 1304 SYNTAX OspfIfEntry 1305 ACCESS not-accessible 1306 STATUS mandatory 1307 DESCRIPTION 1308 "The OSPF Interface Entry describes one inter- 1309 face from the viewpoint of OSPF." 1310 INDEX { ospfIfIpAddress, ospfAddressLessIf } 1311 ::= { ospfIfTable 1 } 1313 OspfIfEntry ::= 1314 SEQUENCE { 1315 ospfIfIpAddress 1316 IpAddress, 1317 ospfAddressLessIf 1318 INTEGER, 1319 ospfIfAreaId 1320 AreaID, 1321 ospfIfType 1322 INTEGER, 1323 ospfIfAdminStat 1324 Status, 1325 ospfIfRtrPriority 1326 DesignatedRouterPriority, 1327 ospfIfTransitDelay 1328 UpToMaxAge, 1330 ospfIfRetransInterval 1331 UpToMaxAge, 1332 ospfIfHelloInterval 1333 HelloRange, 1334 ospfIfRtrDeadInterval 1335 PositiveInteger, 1336 ospfIfPollInterval 1337 PositiveInteger, 1338 ospfIfState 1339 INTEGER, 1340 ospfIfDesignatedRouter 1341 IpAddress, 1342 ospfIfBackupDesignatedRouter 1343 IpAddress, 1344 ospfIfEvents 1345 Counter, 1346 ospfIfAuthKey 1347 OCTET STRING, 1348 ospfIfStatus 1349 Validation, 1350 ospfIfMulticastForwarding 1351 INTEGER 1352 } 1354 ospfIfIpAddress OBJECT-TYPE 1355 SYNTAX IpAddress 1356 ACCESS read-write 1357 STATUS mandatory 1358 DESCRIPTION 1359 "The IP address of this OSPF interface." 1360 ::= { ospfIfEntry 1 } 1362 ospfAddressLessIf OBJECT-TYPE 1363 SYNTAX INTEGER 1364 ACCESS read-write 1365 STATUS mandatory 1366 DESCRIPTION 1367 "For the purpose of easing the instancing of 1368 addressed and addressless interfaces; This 1369 variable takes the value 0 on interfaces with 1370 IP Addresses, and the corresponding value of 1371 ifIndex for interfaces having no IP Address." 1372 ::= { ospfIfEntry 2 } 1374 ospfIfAreaId OBJECT-TYPE 1375 SYNTAX AreaID 1376 ACCESS read-write 1377 STATUS mandatory 1378 DESCRIPTION 1379 "A 32-bit integer uniquely identifying the area 1380 to which the interface connects. Area ID 1381 0.0.0.0 is used for the OSPF backbone." 1382 DEFVAL { '00000000'H } -- 0.0.0.0 1383 ::= { ospfIfEntry 3 } 1385 ospfIfType OBJECT-TYPE 1386 SYNTAX INTEGER { 1387 broadcast (1), 1388 nbma (2), 1389 pointToPoint (3) 1390 } 1391 ACCESS read-write 1392 STATUS mandatory 1393 DESCRIPTION 1394 "The OSPF interface type. 1396 By way of a default, this field may be intuited 1397 from the corresponding value of ifType. Broad- 1398 cast LANs, such as Ethernet and IEEE 802.5, 1399 take the value 'broadcast', X.25 and similar 1400 technologies take the value 'nbma', and links 1401 that are definitively point to point take the 1402 value 'pointToPoint'." 1403 ::= { ospfIfEntry 4 } 1405 ospfIfAdminStat OBJECT-TYPE 1406 SYNTAX Status 1407 ACCESS read-write 1408 STATUS mandatory 1409 DESCRIPTION 1410 "The OSPF interface's administrative status. 1411 The value formed on the interface, and the in- 1412 terface will be advertised as an internal route 1413 to some area. The value 'disabled' denotes 1414 that the interface is external to OSPF." 1415 DEFVAL { enabled } 1416 ::= { ospfIfEntry 5 } 1418 ospfIfRtrPriority OBJECT-TYPE 1419 SYNTAX DesignatedRouterPriority 1420 ACCESS read-write 1421 STATUS mandatory 1422 DESCRIPTION 1423 "The priority of this interface. Used in 1424 multi-access networks, this field is used in 1425 the designated router election algorithm. The 1426 value 0 signifies that the router is not eligi- 1427 ble to become the designated router on this 1428 particular network. In the event of a tie in 1429 this value, routers will use their Router ID as 1430 a tie breaker." 1431 DEFVAL { 1 } 1432 ::= { ospfIfEntry 6 } 1434 ospfIfTransitDelay OBJECT-TYPE 1435 SYNTAX UpToMaxAge 1436 ACCESS read-write 1437 STATUS mandatory 1438 DESCRIPTION 1439 "The estimated number of seconds it takes to 1440 transmit a link state update packet over this 1441 interface." 1442 DEFVAL { 1 } 1443 ::= { ospfIfEntry 7 } 1445 ospfIfRetransInterval OBJECT-TYPE 1446 SYNTAX UpToMaxAge 1447 ACCESS read-write 1448 STATUS mandatory 1449 DESCRIPTION 1450 "The number of seconds between link-state ad- 1451 vertisement retransmissions, for adjacencies 1452 belonging to this interface. This value is 1453 also used when retransmitting database descrip- 1454 tion and link-state request packets." 1455 DEFVAL { 5 } 1456 ::= { ospfIfEntry 8 } 1458 ospfIfHelloInterval OBJECT-TYPE 1459 SYNTAX HelloRange 1460 ACCESS read-write 1461 STATUS mandatory 1462 DESCRIPTION 1463 "The length of time, in seconds, between the 1464 Hello packets that the router sends on the in- 1465 terface. This value must be the same for all 1466 routers attached to a common network." 1467 DEFVAL { 10 } 1468 ::= { ospfIfEntry 9 } 1470 ospfIfRtrDeadInterval OBJECT-TYPE 1471 SYNTAX PositiveInteger 1472 ACCESS read-write 1473 STATUS mandatory 1474 DESCRIPTION 1475 "The number of seconds that a router's Hello 1476 packets have not been seen before it's neigh- 1477 bors declare the router down. This should be 1478 some multiple of the Hello interval. This 1479 value must be the same for all routers attached 1480 to a common network." 1481 DEFVAL { 40 } 1482 ::= { ospfIfEntry 10 } 1484 ospfIfPollInterval OBJECT-TYPE 1485 SYNTAX PositiveInteger 1486 ACCESS read-write 1487 STATUS mandatory 1488 DESCRIPTION 1489 "The larger time interval, in seconds, between 1490 the Hello packets sent to an inactive non- 1491 broadcast multi- access neighbor." 1492 DEFVAL { 120 } 1493 ::= { ospfIfEntry 11 } 1495 ospfIfState OBJECT-TYPE 1496 SYNTAX INTEGER { 1497 down (1), 1498 loopback (2), 1499 waiting (3), 1500 pointToPoint (4), 1501 designatedRouter (5), 1502 backupDesignatedRouter (6), 1503 otherDesignatedRouter (7) 1504 } 1505 ACCESS read-only 1506 STATUS mandatory 1507 DESCRIPTION 1508 "The OSPF Interface State." 1509 DEFVAL { down } 1510 ::= { ospfIfEntry 12 } 1512 ospfIfDesignatedRouter OBJECT-TYPE 1513 SYNTAX IpAddress 1514 ACCESS read-only 1515 STATUS mandatory 1516 DESCRIPTION 1517 "The IP Address of the Designated Router." 1518 DEFVAL { '00000000'H } -- 0.0.0.0 1519 ::= { ospfIfEntry 13 } 1521 ospfIfBackupDesignatedRouter OBJECT-TYPE 1522 SYNTAX IpAddress 1523 ACCESS read-only 1524 STATUS mandatory 1525 DESCRIPTION 1526 "The IP Address of the Backup Designated 1527 Router." 1528 DEFVAL { '00000000'H } -- 0.0.0.0 1529 ::= { ospfIfEntry 14 } 1531 ospfIfEvents OBJECT-TYPE 1532 SYNTAX Counter 1533 ACCESS read-only 1534 STATUS mandatory 1535 DESCRIPTION 1536 "The number of times this OSPF interface has 1537 changed its state, or an error has occurred." 1538 ::= { ospfIfEntry 15 } 1540 ospfIfAuthKey OBJECT-TYPE 1541 SYNTAX OCTET STRING 1542 ACCESS read-write 1543 STATUS mandatory 1544 DESCRIPTION 1545 "The Authentication Key. If the Area's Author- 1546 ization Type is simplePassword, and the key 1547 length is shorter than 8 octets, the agent will 1548 left adjust and zero fill to 8 octets. 1550 When read, ospfIfAuthKey always returns an Oc- 1551 tet String of length zero." 1552 REFERENCE 1553 "OSPF Version 2, Section 9 The Interface Data 1554 Structure" 1555 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 1556 ::= { ospfIfEntry 16 } 1558 ospfIfStatus OBJECT-TYPE 1559 SYNTAX Validation 1560 ACCESS read-write 1561 STATUS mandatory 1562 DESCRIPTION 1563 "This variable displays the status of the en- 1564 try. Setting it to 'invalid' has the effect of 1565 rendering it inoperative. The internal effect 1566 (row removal) is implementation dependent." 1567 DEFVAL { valid } 1568 ::= { ospfIfEntry 17 } 1570 ospfIfMulticastForwarding OBJECT-TYPE 1571 SYNTAX INTEGER { 1572 disabled (1), -- no multicast forwarding 1573 multicast (2), -- using multicast address 1574 unicast (3) -- to each OSPF neighbor 1575 } 1576 ACCESS read-write 1577 STATUS mandatory 1578 DESCRIPTION 1579 "The way multicasts should forwarded on this 1580 interface; not forwarded, forwarded as data 1581 link multicasts, or forwarded as data link uni- 1582 casts. Data link multicasting is not meaningul 1583 on point to point and NBMA interfaces, and set- 1584 ting ospfMulticastForwarding to 0 effectively 1585 disables all multicast forwarding." 1586 DEFVAL { disabled } 1587 ::= { ospfIfEntry 18 } 1589 -- OSPF Interface Metric Table 1591 -- The Metric Table describes the metrics to be advertised 1592 -- for a specified interface at the various types of service. 1593 -- As such, this table is an adjunct of the OSPF Interface 1594 -- Table. 1596 -- Types of service, as defined by RFC 791, have the ability 1597 -- to request low delay, high bandwidth, or reliable linkage. 1599 -- For the purposes of this specification, the measure of 1600 -- bandwidth 1602 -- Metric = 10^8 / ifSpeed 1604 -- is the default value. For multiple link interfaces, note 1605 -- that ifSpeed is the sum of the individual link speeds. 1606 -- This yields a number having the following typical values: 1608 -- Network Type/bit rate Metric 1610 -- >= 100 MBPS 1 1611 -- Ethernet/802.3 10 1612 -- E1 48 1613 -- T1 (ESF) 65 1614 -- 64 KBPS 1562 1615 -- 56 KBPS 1785 1616 -- 19.2 KBPS 5208 1617 -- 9.6 KBPS 10416 1619 -- Routes that are not specified use the default (TOS 0) metric 1621 ospfIfMetricTable OBJECT-TYPE 1622 SYNTAX SEQUENCE OF OspfIfMetricEntry 1623 ACCESS not-accessible 1624 STATUS mandatory 1625 DESCRIPTION 1626 "The TOS metrics for a non-virtual interface 1627 identified by the interface index." 1628 REFERENCE 1629 "OSPF Version 2, Appendix C.3 Router interface 1630 parameters" 1631 ::= { ospf 8 } 1633 ospfIfMetricEntry OBJECT-TYPE 1634 SYNTAX OspfIfMetricEntry 1635 ACCESS not-accessible 1636 STATUS mandatory 1637 DESCRIPTION 1638 "A particular TOS metric for a non-virtual in- 1639 terface identified by the interface index." 1640 REFERENCE 1641 "OSPF Version 2, Appendix C.3 Router interface 1642 parameters" 1643 INDEX { ospfIfMetricIpAddress, 1644 ospfIfMetricAddressLessIf, 1645 ospfIfMetricTOS } 1646 ::= { ospfIfMetricTable 1 } 1648 OspfIfMetricEntry ::= 1649 SEQUENCE { 1650 ospfIfMetricIpAddress 1651 IpAddress, 1652 ospfIfMetricAddressLessIf 1653 INTEGER, 1654 ospfIfMetricTOS 1655 TOSType, 1656 ospfIfMetricValue 1657 Metric, 1658 ospfIfMetricStatus 1659 Validation 1660 } 1662 ospfIfMetricIpAddress OBJECT-TYPE 1663 SYNTAX IpAddress 1664 ACCESS read-write 1665 STATUS mandatory 1666 DESCRIPTION 1667 "The IP address of this OSPF interface. On row 1668 creation, this can be derived from the in- 1669 stance." 1670 ::= { ospfIfMetricEntry 1 } 1672 ospfIfMetricAddressLessIf OBJECT-TYPE 1673 SYNTAX INTEGER 1674 ACCESS read-write 1675 STATUS mandatory 1676 DESCRIPTION 1677 "For the purpose of easing the instancing of 1678 addressed and addressless interfaces; This 1679 variable takes the value 0 on interfaces with 1680 IP Addresses, and the value of ifIndex for in- 1681 terfaces having no IP Address. On row crea- 1682 tion, this can be derived from the instance." 1683 ::= { ospfIfMetricEntry 2 } 1685 ospfIfMetricTOS OBJECT-TYPE 1686 SYNTAX TOSType 1687 ACCESS read-write 1688 STATUS mandatory 1689 DESCRIPTION 1690 "The type of service metric being referenced. 1691 On row creation, this can be derived from the 1692 instance." 1693 ::= { ospfIfMetricEntry 3 } 1695 ospfIfMetricValue OBJECT-TYPE 1696 SYNTAX Metric 1697 ACCESS read-write 1698 STATUS mandatory 1699 DESCRIPTION 1700 "The metric of using this type of service on 1701 this interface. The default value of the TOS 0 1702 Metric is 10^8 / ifSpeed." 1703 ::= { ospfIfMetricEntry 4 } 1705 ospfIfMetricStatus OBJECT-TYPE 1706 SYNTAX Validation 1707 ACCESS read-write 1708 STATUS mandatory 1709 DESCRIPTION 1710 "This variable displays the status of the en- 1711 try. Setting it to 'invalid' has the effect of 1712 rendering it inoperative. The internal effect 1713 (row removal) is implementation dependent." 1714 DEFVAL { valid } 1715 ::= { ospfIfMetricEntry 5 } 1717 -- OSPF Virtual Interface Table 1719 -- The Virtual Interface Table describes the virtual 1720 -- links that the OSPF Process is configured to 1721 -- carry on. 1723 ospfVirtIfTable OBJECT-TYPE 1724 SYNTAX SEQUENCE OF OspfVirtIfEntry 1725 ACCESS not-accessible 1726 STATUS mandatory 1727 DESCRIPTION 1728 "Information about this router's virtual inter- 1729 faces." 1730 REFERENCE 1731 "OSPF Version 2, Appendix C.4 Virtual link 1732 parameters" 1733 ::= { ospf 9 } 1735 ospfVirtIfEntry OBJECT-TYPE 1736 SYNTAX OspfVirtIfEntry 1737 ACCESS not-accessible 1738 STATUS mandatory 1739 DESCRIPTION 1740 "Information about a single Virtual Interface." 1741 INDEX { ospfVirtIfAreaID, ospfVirtIfNeighbor } 1742 ::= { ospfVirtIfTable 1 } 1744 OspfVirtIfEntry ::= 1745 SEQUENCE { 1746 ospfVirtIfAreaID 1747 AreaID, 1748 ospfVirtIfNeighbor 1749 RouterID, 1750 ospfVirtIfTransitDelay 1751 UpToMaxAge, 1752 ospfVirtIfRetransInterval 1753 UpToMaxAge, 1754 ospfVirtIfHelloInterval 1755 HelloRange, 1756 ospfVirtIfRtrDeadInterval 1757 PositiveInteger, 1758 ospfVirtIfState 1759 INTEGER, 1760 ospfVirtIfEvents 1761 Counter, 1762 ospfVirtIfAuthKey 1763 OCTET STRING, 1764 ospfVirtIfStatus 1765 Validation 1766 } 1768 ospfVirtIfAreaID OBJECT-TYPE 1769 SYNTAX AreaID 1770 ACCESS read-write 1771 STATUS mandatory 1772 DESCRIPTION 1773 "The Transit Area that the Virtual Link 1774 traverses. By definition, this is not 0.0.0.0" 1775 ::= { ospfVirtIfEntry 1 } 1777 ospfVirtIfNeighbor OBJECT-TYPE 1778 SYNTAX RouterID 1779 ACCESS read-write 1780 STATUS mandatory 1781 DESCRIPTION 1782 "The Router ID of the Virtual Neighbor." 1783 ::= { ospfVirtIfEntry 2 } 1785 ospfVirtIfTransitDelay OBJECT-TYPE 1786 SYNTAX UpToMaxAge 1787 ACCESS read-write 1788 STATUS mandatory 1789 DESCRIPTION 1790 "The estimated number of seconds it takes to 1791 transmit a link- state update packet over this 1792 interface." 1793 DEFVAL { 1 } 1794 ::= { ospfVirtIfEntry 3 } 1796 ospfVirtIfRetransInterval OBJECT-TYPE 1797 SYNTAX UpToMaxAge 1798 ACCESS read-write 1799 STATUS mandatory 1800 DESCRIPTION 1801 "The number of seconds between link-state ad- 1802 vertisement retransmissions, for adjacencies 1803 belonging to this interface. This value is 1804 also used when retransmitting database descrip- 1805 tion and link-state request packets. This 1806 value should be well over the expected round- 1807 trip time." 1808 DEFVAL { 5 } 1809 ::= { ospfVirtIfEntry 4 } 1811 ospfVirtIfHelloInterval OBJECT-TYPE 1812 SYNTAX HelloRange 1813 ACCESS read-write 1814 STATUS mandatory 1815 DESCRIPTION 1816 "The length of time, in seconds, between the 1817 Hello packets that the router sends on the in- 1818 terface. This value must be the same for the 1819 virtual neighbor." 1820 DEFVAL { 10 } 1821 ::= { ospfVirtIfEntry 5 } 1823 ospfVirtIfRtrDeadInterval OBJECT-TYPE 1824 SYNTAX PositiveInteger 1825 ACCESS read-write 1826 STATUS mandatory 1827 DESCRIPTION 1828 "The number of seconds that a router's Hello 1829 packets have not been seen before it's neigh- 1830 bors declare the router down. This should be 1831 some multiple of the Hello interval. This 1832 value must be the same for the virtual neigh- 1833 bor." 1834 DEFVAL { 60 } 1835 ::= { ospfVirtIfEntry 6 } 1837 ospfVirtIfState OBJECT-TYPE 1838 SYNTAX INTEGER { 1839 down (1), -- these use the same encoding 1840 pointToPoint (4) -- as the ospfIfTable 1841 } 1842 ACCESS read-only 1843 STATUS mandatory 1844 DESCRIPTION 1845 "OSPF virtual interface states." 1846 DEFVAL { down } 1847 ::= { ospfVirtIfEntry 7 } 1849 ospfVirtIfEvents OBJECT-TYPE 1850 SYNTAX Counter 1851 ACCESS read-only 1852 STATUS mandatory 1853 DESCRIPTION 1854 "The number of state changes or error events on 1855 this Virtual Link" 1856 ::= { ospfVirtIfEntry 8 } 1858 ospfVirtIfAuthKey OBJECT-TYPE 1859 SYNTAX OCTET STRING 1860 ACCESS read-write 1861 STATUS mandatory 1862 DESCRIPTION 1863 "If Authentication Type is simplePassword, the 1864 device will left adjust and zero fill to 8 oc- 1865 tets. 1867 When read, ospfVifAuthKey always returns a 1868 string of length zero." 1869 REFERENCE 1870 "OSPF Version 2, Section 9 The Interface Data 1871 Structure" 1872 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 1873 ::= { ospfVirtIfEntry 9 } 1875 ospfVirtIfStatus OBJECT-TYPE 1876 SYNTAX Validation 1877 ACCESS read-write 1878 STATUS mandatory 1879 DESCRIPTION 1880 "This variable displays the status of the en- 1881 try. Setting it to 'invalid' has the effect of 1882 rendering it inoperative. The internal effect 1883 (row removal) is implementation dependent." 1884 DEFVAL { valid } 1885 ::= { ospfVirtIfEntry 10 } 1887 -- OSPF Neighbor Table 1889 -- The OSPF Neighbor Table describes all neighbors in 1890 -- the locality of the subject router. 1892 ospfNbrTable OBJECT-TYPE 1893 SYNTAX SEQUENCE OF OspfNbrEntry 1894 ACCESS not-accessible 1895 STATUS mandatory 1896 DESCRIPTION 1897 "A table of non-virtual neighbor information." 1898 REFERENCE 1899 "OSPF Version 2, Section 10 The Neighbor Data 1900 Structure" 1901 ::= { ospf 10 } 1903 ospfNbrEntry OBJECT-TYPE 1904 SYNTAX OspfNbrEntry 1905 ACCESS not-accessible 1906 STATUS mandatory 1907 DESCRIPTION 1908 "The information regarding a single neighbor." 1909 REFERENCE 1910 "OSPF Version 2, Section 10 The Neighbor Data 1911 Structure" 1912 INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex } 1913 ::= { ospfNbrTable 1 } 1915 OspfNbrEntry ::= 1916 SEQUENCE { 1917 ospfNbrIpAddr 1918 IpAddress, 1919 ospfNbrAddressLessIndex 1920 InterfaceIndex, 1921 ospfNbrRtrId 1922 RouterID, 1923 ospfNbrOptions 1924 INTEGER, 1925 ospfNbrPriority 1926 DesignatedRouterPriority, 1927 ospfNbrState 1928 INTEGER, 1930 ospfNbrEvents 1931 Counter, 1932 ospfNbrLSRetransQLen 1933 Gauge, 1934 ospfNbmaNbrStatus 1935 INTEGER 1936 } 1938 ospfNbrIpAddr OBJECT-TYPE 1939 SYNTAX IpAddress 1940 ACCESS read-write 1941 STATUS mandatory 1942 DESCRIPTION 1943 "The IP address this neighbor is using in its 1944 IP Source Address. Note that, on addressless 1945 links, this will not be 0.0.0.0, but the ad- 1946 dress of another of the neighbor's interfaces." 1947 ::= { ospfNbrEntry 1 } 1949 ospfNbrAddressLessIndex OBJECT-TYPE 1950 SYNTAX InterfaceIndex 1951 ACCESS read-write 1952 STATUS mandatory 1953 DESCRIPTION 1954 "On an interface having an IP Address, zero. 1955 On addressless interfaces, the corresponding 1956 value of ifIndex in the Internet Standard MIB. 1957 On row creation, this can be derived from the 1958 instance." 1959 ::= { ospfNbrEntry 2 } 1961 ospfNbrRtrId OBJECT-TYPE 1962 SYNTAX RouterID 1963 ACCESS read-only 1964 STATUS mandatory 1965 DESCRIPTION 1966 "A 32-bit integer (represented as a type IpAd- 1967 dress) uniquely identifying the neighboring 1968 router in the Autonomous System." 1969 DEFVAL { '00000000'H } -- 0.0.0.0 1970 ::= { ospfNbrEntry 3 } 1972 ospfNbrOptions OBJECT-TYPE 1973 SYNTAX INTEGER 1974 ACCESS read-only 1975 STATUS mandatory 1976 DESCRIPTION 1977 "A Bit Mask corresponding to the neighbor's op- 1978 tions field. 1980 Bit 0, if set, indicates that the area accepts 1981 and operates on external information; if zero, 1982 it is a stub area. 1984 Bit 1, if set, indicates that the system will 1985 operate on Type of Service metrics other than 1986 TOS 0. If zero, the neighbor will ignore all 1987 metrics except the TOS 0 metric. 1989 Bit 2, if set, indicates that the system is 1990 Network Multicast capable; ie, that it imple- 1991 ments OSPF Multicast Routing." 1992 REFERENCE 1993 "OSPF Version 2, Section 12.1.2 Options" 1994 DEFVAL { 0 } 1995 ::= { ospfNbrEntry 4 } 1997 ospfNbrPriority OBJECT-TYPE 1998 SYNTAX DesignatedRouterPriority 1999 ACCESS read-write 2000 STATUS mandatory 2001 DESCRIPTION 2002 "The priority of this neighbor in the designat- 2003 ed router election algorithm. The value 0 sig- 2004 nifies that the neighbor is not eligible to be- 2005 come the designated router on this particular 2006 network." 2007 DEFVAL { 1 } 2008 ::= { ospfNbrEntry 5 } 2010 ospfNbrState OBJECT-TYPE 2011 SYNTAX INTEGER { 2012 down (1), 2013 attempt (2), 2014 init (3), 2015 twoWay (4), 2016 exchangeStart (5), 2017 exchange (6), 2018 loading (7), 2019 full (8) 2020 } 2021 ACCESS read-only 2022 STATUS mandatory 2023 DESCRIPTION 2024 "The State of the relationship with this Neigh- 2025 bor." 2026 REFERENCE 2027 "OSPF Version 2, Section 10.1 Neighbor States" 2028 DEFVAL { down } 2029 ::= { ospfNbrEntry 6 } 2031 ospfNbrEvents OBJECT-TYPE 2032 SYNTAX Counter 2033 ACCESS read-only 2034 STATUS mandatory 2035 DESCRIPTION 2036 "The number of times this neighbor relationship 2037 has changed state, or an error has occurred." 2038 ::= { ospfNbrEntry 7 } 2040 ospfNbrLSRetransQLen OBJECT-TYPE 2041 SYNTAX Gauge 2042 ACCESS read-only 2043 STATUS mandatory 2044 DESCRIPTION 2045 "The current length of the retransmission 2046 queue." 2047 ::= { ospfNbrEntry 8 } 2049 ospfNbmaNbrStatus OBJECT-TYPE 2050 SYNTAX INTEGER { 2051 dynamic (1), -- learned through protocol 2052 invalid (2), -- set to delete 2053 permanent (3) -- configured address 2054 } 2055 ACCESS read-write 2056 STATUS mandatory 2057 DESCRIPTION 2058 "This variable displays the status of the en- 2059 try. Setting it to 'invalid' has the effect of 2060 rendering it inoperative. The internal effect 2061 (row removal) is implementation dependent." 2062 DEFVAL { permanent } 2063 ::= { ospfNbrEntry 9 } 2065 -- OSPF Virtual Neighbor Table 2067 -- This table describes all virtual neighbors. 2068 -- Since Virtual Links are configured in the 2069 -- virtual interface table, this table is read-only. 2071 ospfVirtNbrTable OBJECT-TYPE 2072 SYNTAX SEQUENCE OF OspfVirtNbrEntry 2073 ACCESS not-accessible 2074 STATUS mandatory 2075 DESCRIPTION 2076 "A table of virtual neighbor information." 2077 REFERENCE 2078 "OSPF Version 2, Section 15 Virtual Links" 2079 ::= { ospf 11 } 2081 ospfVirtNbrEntry OBJECT-TYPE 2082 SYNTAX OspfVirtNbrEntry 2083 ACCESS not-accessible 2084 STATUS mandatory 2085 DESCRIPTION 2086 "Virtual neighbor information." 2087 INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId } 2088 ::= { ospfVirtNbrTable 1 } 2090 OspfVirtNbrEntry ::= 2091 SEQUENCE { 2092 ospfVirtNbrArea 2093 AreaID, 2094 ospfVirtNbrRtrId 2095 RouterID, 2096 ospfVirtNbrIpAddr 2097 IpAddress, 2098 ospfVirtNbrOptions 2099 INTEGER, 2100 ospfVirtNbrState 2101 INTEGER, 2102 ospfVirtNbrEvents 2103 Counter, 2104 ospfVirtNbrLSRetransQLen 2105 Gauge 2106 } 2107 ospfVirtNbrArea OBJECT-TYPE 2108 SYNTAX AreaID 2109 ACCESS read-only 2110 STATUS mandatory 2111 DESCRIPTION 2112 "The Transit Area Identifier." 2113 ::= { ospfVirtNbrEntry 1 } 2115 ospfVirtNbrRtrId OBJECT-TYPE 2116 SYNTAX RouterID 2117 ACCESS read-only 2118 STATUS mandatory 2119 DESCRIPTION 2120 "A 32-bit integer uniquely identifying the 2121 neighboring router in the Autonomous System." 2122 ::= { ospfVirtNbrEntry 2 } 2124 ospfVirtNbrIpAddr OBJECT-TYPE 2125 SYNTAX IpAddress 2126 ACCESS read-only 2127 STATUS mandatory 2128 DESCRIPTION 2129 "The IP address this Virtual Neighbor is us- 2130 ing." 2131 ::= { ospfVirtNbrEntry 3 } 2133 ospfVirtNbrOptions OBJECT-TYPE 2134 SYNTAX INTEGER 2135 ACCESS read-only 2136 STATUS mandatory 2137 DESCRIPTION 2138 "A Bit Mask corresponding to the neighbor's op- 2139 tions field. 2141 Bit 1, if set, indicates that the system will 2142 operate on Type of Service metrics other than 2143 TOS 0. If zero, the neighbor will ignore all 2144 metrics except the TOS 0 metric. 2146 Bit 2, if set, indicates that the system is 2147 Network Multicast capable; ie, that it imple- 2148 ments OSPF Multicast Routing." 2149 ::= { ospfVirtNbrEntry 4 } 2151 ospfVirtNbrState OBJECT-TYPE 2152 SYNTAX INTEGER { 2153 down (1), 2154 attempt (2), 2155 init (3), 2156 twoWay (4), 2157 exchangeStart (5), 2158 exchange (6), 2159 loading (7), 2160 full (8) 2161 } 2162 ACCESS read-only 2163 STATUS mandatory 2164 DESCRIPTION 2165 "The state of the Virtual Neighbor Relation- 2166 ship." 2167 ::= { ospfVirtNbrEntry 5 } 2169 ospfVirtNbrEvents OBJECT-TYPE 2170 SYNTAX Counter 2171 ACCESS read-only 2172 STATUS mandatory 2173 DESCRIPTION 2174 "The number of times this virtual link has 2175 changed its state, or an error has occurred." 2176 ::= { ospfVirtNbrEntry 6 } 2178 ospfVirtNbrLSRetransQLen OBJECT-TYPE 2179 SYNTAX Gauge 2180 ACCESS read-only 2181 STATUS mandatory 2182 DESCRIPTION 2183 "The current length of the retransmission 2184 queue." 2185 ::= { ospfVirtNbrEntry 7 } 2187 -- OSPF Link State Database, External 2189 -- The Link State Database contains the Link State 2190 -- Advertisements from throughout the areas that the 2191 -- device is attached to. 2193 -- This table is identical to the OSPF LSDB Table in 2194 -- format, but contains only External Link State 2195 -- Advertisements. The purpose is to allow external 2196 -- LSAs to be displayed once for the router rather 2197 -- than once in each non-stub area. 2199 ospfExtLsdbTable OBJECT-TYPE 2200 SYNTAX SEQUENCE OF OspfExtLsdbEntry 2201 ACCESS not-accessible 2202 STATUS mandatory 2203 DESCRIPTION 2204 "The OSPF Process's Links State Database." 2205 REFERENCE 2206 "OSPF Version 2, Section 12 Link State Adver- 2207 tisements" 2208 ::= { ospf 12 } 2210 ospfExtLsdbEntry OBJECT-TYPE 2211 SYNTAX OspfExtLsdbEntry 2212 ACCESS not-accessible 2213 STATUS mandatory 2214 DESCRIPTION 2215 "A single Link State Advertisement." 2216 INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId } 2217 ::= { ospfExtLsdbTable 1 } 2219 OspfExtLsdbEntry ::= 2220 SEQUENCE { 2221 ospfExtLsdbType 2222 INTEGER, 2223 ospfExtLsdbLsid 2224 IpAddress, 2225 ospfExtLsdbRouterId 2226 RouterID, 2227 ospfExtLsdbSequence 2228 INTEGER, 2229 ospfExtLsdbAge 2230 INTEGER, 2231 ospfExtLsdbChecksum 2232 INTEGER, 2233 ospfExtLsdbAdvertisement 2234 OCTET STRING 2235 } 2237 ospfExtLsdbType OBJECT-TYPE 2238 SYNTAX INTEGER { 2239 asExternalLink (5) 2240 } 2241 ACCESS read-only 2242 STATUS mandatory 2243 DESCRIPTION 2244 "The type of the link state advertisement. 2245 Each link state type has a separate advertise- 2246 ment format." 2247 REFERENCE 2248 "OSPF Version 2, Appendix A.4.1 The Link State 2249 Advertisement header" 2250 ::= { ospfExtLsdbEntry 1 } 2252 ospfExtLsdbLsid OBJECT-TYPE 2253 SYNTAX IpAddress 2254 ACCESS read-only 2255 STATUS mandatory 2256 DESCRIPTION 2257 "The Link State ID is an LS Type Specific field 2258 containing either a Router ID or an IP Address; 2259 it identifies the piece of the routing domain 2260 that is being described by the advertisement." 2261 REFERENCE 2262 "OSPF Version 2, Section 12.1.4 Link State ID" 2263 ::= { ospfExtLsdbEntry 2 } 2265 ospfExtLsdbRouterId OBJECT-TYPE 2266 SYNTAX RouterID 2267 ACCESS read-only 2268 STATUS mandatory 2269 DESCRIPTION 2270 "The 32 bit number that uniquely identifies the 2271 originating router in the Autonomous System." 2272 REFERENCE 2273 "OSPF Version 2, Appendix C.1 Global parameters" 2274 ::= { ospfExtLsdbEntry 3 } 2276 -- Note that the OSPF Sequence Number is a 32 bit signed 2277 -- integer. It starts with the value '80000001'h, 2278 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 2279 -- Thus, a typical sequence number will be very negative. 2281 ospfExtLsdbSequence OBJECT-TYPE 2282 SYNTAX INTEGER 2283 ACCESS read-only 2284 STATUS mandatory 2285 DESCRIPTION 2286 "The sequence number field is a signed 32-bit 2287 integer. It is used to detect old and dupli- 2288 cate link state advertisements. The space of 2289 sequence numbers is linearly ordered. The 2290 larger the sequence number the more recent the 2291 advertisement." 2292 REFERENCE 2293 "OSPF Version 2, Section 12.1.6 LS sequence 2294 number" 2295 ::= { ospfExtLsdbEntry 4 } 2297 ospfExtLsdbAge OBJECT-TYPE 2298 SYNTAX INTEGER -- Should be 0..MaxAge 2299 ACCESS read-only 2300 STATUS mandatory 2301 DESCRIPTION 2302 "This field is the age of the link state adver- 2303 tisement in seconds." 2304 REFERENCE 2305 "OSPF Version 2, Section 12.1.1 LS age" 2306 ::= { ospfExtLsdbEntry 5 } 2308 ospfExtLsdbChecksum OBJECT-TYPE 2309 SYNTAX INTEGER 2310 ACCESS read-only 2311 STATUS mandatory 2312 DESCRIPTION 2313 "This field is the checksum of the complete 2314 contents of the advertisement, excepting the 2315 age field. The age field is excepted so that 2316 an advertisement's age can be incremented 2317 without updating the checksum. The checksum 2318 used is the same that is used for ISO connec- 2319 tionless datagrams; it is commonly referred to 2320 as the Fletcher checksum." 2321 REFERENCE 2322 "OSPF Version 2, Section 12.1.7 LS checksum" 2323 ::= { ospfExtLsdbEntry 6 } 2325 ospfExtLsdbAdvertisement OBJECT-TYPE 2326 SYNTAX OCTET STRING 2327 ACCESS read-only 2328 STATUS mandatory 2329 DESCRIPTION 2330 "The entire Link State Advertisement, including 2331 its header." 2332 REFERENCE 2333 "OSPF Version 2, Section 12 Link State Adver- 2334 tisements" 2335 ::= { ospfExtLsdbEntry 7 } 2337 -- OSPF Use of the IP Forwarding Table 2339 ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 } 2341 -- The IP Forwarding Table defines a number of objects for use by 2342 -- the routing protocol to externalize its information. Most of 2343 -- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy, 2344 -- ipForwardNextHop, ipForwardIfIndex, ipForwardType, 2345 -- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are 2346 -- defined there. 2348 -- Those that leave some discretion are defined here. 2350 -- ipForwardProto is, of course, ospf (13). 2352 -- ipForwardAge is the time since the route was first calculated, 2353 -- as opposed to the time since the last SPF run. 2355 -- ipForwardInfo is an OBJECT IDENTIFIER for use by the routing 2356 -- protocol. The following values shall be found there depending 2357 -- on the way the route was calculated. 2359 ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 } 2360 ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 } 2361 ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 } 2362 ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 } 2364 -- ipForwardMetric1 is, by definition, the primary routing 2365 -- metric. Therefore, it should be the metric that route 2366 -- selection is based on. For intra-area and inter-area routes, 2367 -- it is an OSPF metric. For External Type 1 (comparable value) 2368 -- routes, it is an OSPF metric plus the External Metric. For 2369 -- external Type 2 (non-comparable value) routes, it is the 2370 -- external metric. 2372 -- ipForwardMetric2 is, by definition, a secondary routing 2373 -- metric. Therefore, it should be the metric that breaks a tie 2374 -- among routes having equal metric1 values and the same 2375 -- calculation rule. For intra-area, inter-area routes, and 2376 -- External Type 1 (comparable value) routes, it is unused. For 2377 -- external Type 2 (non-comparable value) routes, it is the metric 2378 -- to the AS border router. 2380 -- ipForwardMetric3, ipForwardMetric4, and ipForwardMetric5 are 2381 -- unused. 2383 END 2384 7. Acknowledgements 2386 This document was produced by the OSPF Working Group. 2388 8. References 2390 [1] V. Cerf, IAB Recommendations for the Development of 2391 Internet Network Management Standards. Internet Working 2392 Group Request for Comments 1052. Network Information 2393 Center, SRI International, Menlo Park, California, 2394 (April, 1988). 2396 [2] V. Cerf, Report of the Second Ad Hoc Network Management 2397 Review Group, Internet Working Group Request for Comments 2398 1109. Network Information Center, SRI International, 2399 Menlo Park, California, (August, 1989). 2401 [3] M.T. Rose and K. McCloghrie, Structure and Identification 2402 of Management Information for TCP/IP-based internets, 2403 Internet Working Group Request for Comments 1155. 2404 Network Information Center, SRI International, Menlo 2405 Park, California, (May, 1990). 2407 [4] K. McCloghrie and M.T. Rose, Management Information Base 2408 for Network Management of TCP/IP-based internets, 2409 Internet Working Group Request for Comments 1156. 2410 Network Information Center, SRI International, Menlo 2411 Park, California, (May, 1990). 2413 [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 2414 Simple Network Management Protocol, Internet Working 2415 Group Request for Comments 1157. Network Information 2416 Center, SRI International, Menlo Park, California, (May, 2417 1990). 2419 [6] M.T. Rose (editor), Management Information Base for 2420 Network Management of TCP/IP-based internets, Internet 2421 Working Group Request for Comments 1213. Network 2422 Information Center, SRI International, Menlo Park, 2423 California, (May, 1990). 2425 [7] Information processing systems - Open Systems 2426 Interconnection - Specification of Abstract Syntax 2427 Notation One (ASN.1), International Organization for 2428 Standardization. International Standard 8824, (December, 2429 1987). 2431 [8] Information processing systems - Open Systems 2432 Interconnection - Specification of Basic Encoding Rules 2433 for Abstract Notation One (ASN.1), International 2434 Organization for Standardization. International Standard 2435 8825, (December, 1987). 2437 [9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB 2438 Definitions, Internet Draft, Internet Engineering Task 2439 Force, (September, 1990). 2441 [10] M.T. Rose (editor), A Convention for Defining Traps for 2442 use with the SNMP, Internet Draft, Internet Engineering 2443 Task Force, (September, 1990). 2445 Table of Contents 2447 1 Status of this Memo ................................... 1 2448 2 Abstract .............................................. 2 2449 3 The Network Management Framework ...................... 3 2450 4 Objects ............................................... 4 2451 4.1 Format of Definitions ............................... 4 2452 4.2 Changes from RFC 1253 ............................... 4 2453 5 Overview .............................................. 7 2454 5.1 Textual Conventions ................................. 7 2455 5.2 Structure of MIB .................................... 7 2456 5.2.1 General Variables ................................. 7 2457 5.2.2 Area Data Structure and Area Stub Metric Table .... 8 2458 5.2.3 Link State Database and External Link State Da- 2459 tabase ............................................. 8 2460 5.2.4 Address Table and Host Tables ..................... 8 2461 5.2.5 Interface and Interface Metric Tables ............. 8 2462 5.2.6 Virtual Interface Table ........................... 8 2463 5.2.7 Neighbor and Virtual Neighbor Tables .............. 8 2464 5.3 Conceptual Row Creation ............................. 8 2465 5.4 Default Configuration ............................... 9 2466 6 Definitions ........................................... 12 2467 6.1 OSPF General Variables .............................. 13 2468 6.2 OSPF Area Table ..................................... 18 2469 6.3 OSPF Area Default Metrics ........................... 23 2470 6.4 OSPF Link State Database ............................ 26 2471 6.5 OSPF Address Range Table ............................ 31 2472 6.6 OSPF Host Table ..................................... 34 2473 6.7 OSPF Interface Table ................................ 37 2474 6.8 OSPF Interface Metrics .............................. 45 2475 6.9 OSPF Virtual Interface Table ........................ 49 2476 6.10 OSPF Neighbor Table ................................ 54 2477 6.11 OSPF Virtual Neighbor Table ........................ 59 2478 6.12 OSPF External Link State Database .................. 63 2479 6.13 OSPF Route Table Use ............................... 68 2480 7 Acknowledgements ...................................... 70 2481 8 References ............................................ 70