idnits 2.17.1 draft-ietf-ospf-mib-05.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-19) 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 108 pages 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 322 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 13 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 693: '...database. OspfExtLsdbLimit MUST be set...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 560 has weird spacing: '... 32-bit integ...' == Line 563 has weird spacing: '... By conve...' == Line 564 has weird spacing: '... should defau...' == Line 575 has weird spacing: '... "The admin...' == Line 576 has weird spacing: '.... The value...' == (317 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 (January 1995) is 10687 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? '9' on line 3582 looks like a reference -- Missing reference section? '11' on line 3591 looks like a reference -- Missing reference section? '1' on line 3535 looks like a reference -- Missing reference section? '2' on line 3541 looks like a reference -- Missing reference section? '3' on line 3546 looks like a reference -- Missing reference section? '4' on line 3552 looks like a reference -- Missing reference section? '5' on line 3558 looks like a reference -- Missing reference section? '6' on line 3564 looks like a reference -- Missing reference section? '7' on line 3570 looks like a reference -- Missing reference section? '8' on line 3576 looks like a reference -- Missing reference section? '10' on line 3586 looks like a reference -- Missing reference section? '12' on line 3596 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 8 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft OSPF MIB January 1995 4 OSPF Version 2 Management Information Base 5 draft-ietf-ospf-mib-05.txt 7 Mon Jan 9 14:20:53 PST 1995 9 Fred Baker 11 Advanced Computer Communications 12 315 Bollay Drive 13 Santa Barbara, California 93117 15 fbaker@acc.com 17 Rob Coltun 19 RainbowBridge Communications 20 (301) 340-9416 22 rcoltun@rainbow-bridge.com 24 1. Status of this Memo 26 This document is an Internet Draft. Internet Drafts are 27 working documents of the Internet Engineering Task Force 28 (IETF), its Areas, and its Working Groups. Note that other 29 groups may also distribute working documents as Internet 30 Drafts. 32 Internet Drafts are draft documents valid for a maximum of six 33 months. Internet Drafts may be updated, replaced, or obsoleted 34 by other documents at any time. It is not appropriate to use 35 Internet Drafts as reference material or to cite them other 36 than as a "working draft" or "work in progress." 38 Please check the I-D abstract listing contained in each 39 Internet Draft directory to learn the current status of this 40 or any other Internet Draft. 42 2. Abstract 44 This memo defines a portion of the Management Information Base 45 (MIB) for use with network management protocols in TCP/IP- 46 based internets. In particular, it defines objects for 47 managing the Open Shortest Path First Routing Protocol. 49 This memo does not, in its draft form, specify a standard for 50 the Internet community. 52 3. The SNMPv2 Network Management Framework 54 The SNMPv2 Network Management Framework consists of four major 55 components. They are: 57 o RFC 1441 which defines the SMI, the mechanisms used for 58 describing and naming objects for the purpose of 59 management. 61 o RFC 1213 defines MIB-II, the core set of managed objects 62 for the Internet suite of protocols. 64 o RFC 1445 which defines the administrative and other 65 architectural aspects of the framework. 67 o RFC 1448 which defines the protocol used for network 68 access to managed objects. 70 The Framework permits new objects to be defined for the 71 purpose of experimentation and evaluation. 73 3.1. Object Definitions 75 Managed objects are accessed via a virtual information store, 76 termed the Management Information Base or MIB. Objects in the 77 MIB are defined using the subset of Abstract Syntax Notation 78 One (ASN.1) defined in the SMI. In particular, each object 79 object type is named by an OBJECT IDENTIFIER, an 80 administratively assigned name. The object type together with 81 an 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 descriptor, to refer to the 84 object type. 86 4. Overview 88 4.1. Changes from RFC 1253 90 The changes from RFC 1253 are the following: 92 (1) The textual convention PositiveInteger was changed from 93 1..'FFFFFFFF'h to 1..'7FFFFFFF'h at the request of 94 Marshall Rose. 96 (2) The textual convention TOSType was changed to reflect the 97 TOS values defined in the Router Requirements Draft, and 98 in accordance with the IP Forwarding Table MIB's values. 100 (3) The names of some objects were changed, conforming to the 101 convention that an acronym (for example, LSA) is a single 102 word ("Lsa") in most SNMP names. 104 (4) textual changes were made to make the MIB readable by 105 Dave Perkins' SMIC MIB Compiler in addition to Mosy. 106 This involved changing the case of some characters in 107 certain names and removing the DEFVAL clauses for 108 Counters. (This would appear to violate RFC 1212, which 109 explicitly states that DEFVALs are for the purpose of 110 initializing read-only objects???) 112 (5) The variables ospfAreaStatus and ospfIfStatus were added, 113 having been overlooked in the original MIB. 115 (6) The range of the variable ospfLsdbType was extended to 116 include multicastLink (Group-membership LSA) and 117 nssaExternalLink (NSSA LSA). 119 (7) The variable ospfIfMetricMetric was renamed 120 ospfIfMetricValue, and the following text was removed 121 from its description: 123 "The value FFFF is distinguished to mean 'no route via 124 this TOS'." 126 (8) The variable ospfNbmaNbrPermanence was added, with the 127 values 'dynamic' and 'permanent'; by this means, 128 dynamically learned and configured neighbors can be 129 distinguished. 131 (9) The DESCRIPTION of the variable ospfNbrIpAddr was changed 132 from 134 "The IP address of this neighbor." 136 to 138 "The IP address this neighbor is using in its IP Source 139 Address. Note that, on addressless links, this will not 140 be 0.0.0.0, but the address of another of the neighbor's 141 interfaces." 143 This is by way of clarification and does not change the 144 specification. 146 (10) The OSPF External Link State Database was added. The 147 OSPF Link State Database used to display all LSAs stored; 148 in this MIB, it displays all but the AS External LSAs. 149 This is because there are usually a large number of 150 External LSAs, and they are relicated in all non-Stub 151 Areas. 153 (11) The variable ospfAreaSummary was added to control the 154 import of summary LSAs into stub areas. If it is 155 noAreaSummary (default) the router will neither originate 156 nor propagate summary LSAs into the stub area. It will 157 rely entirely on its default route. If it is 158 sendAreaSummary, the router will both summarize and 159 propagate summary LSAs. 161 (12) The general variables ospfExtLsdbLimit and 162 ExitOverflowInterval were introduced to help handle LSDB 163 overflow. 165 (13) The use of the IP Forwarding Table is defined. 167 (14) The ospfAreaRangeTable was obsoleted and replaced with 168 the ospfAreaAggregateTable to accommodate two additional 169 indexes. The ospfAreaAggregateEntry keys now include a 170 LsdbType (which can be used to differentiate between the 171 traditional type-3 Aggregates and NSSA Aggregates) and an 172 ospfAreaAggregateMask (which will more clearly express 173 the range). 175 (15) The variable ospfAreaAggregateEffect was added. This 176 permits the network manager to hide a subnet within an 177 area. 179 (16) Normally, the border router of a stub area advertises a 180 default route as an OSPF network summary. An NSSA border 181 router will generate a type-7 LSA indicating a default 182 route, and import it into the NSSA. ospfStubMetricType 183 (ospf internal, type 1 external, or type 2 external) 184 indicates the type of the default metric advertised. 186 (17) ospfMulticastExtensions is added to the OSPF General 187 Group. This indicates the router's ability to forward IP 188 multicast (Class D) datagrams. 190 (18) ospfIfMulticastForwarding is added to the Interface 191 Group. It indicates whether, and if so, how, multicasts 192 should be forwarded on the interface. 194 (19) The MIB is converted to SNMP Version 2. Beyond simple 195 text changes and the addition of the MODULE-IDENTITY and 196 MODULE-COMPLIANCE macros, this involved trading the 197 TruthValue Textual Convention for SNMP Version 2's, which 198 has the same values, and trading the Validation Textual 199 Convention for SNMP Version 2's RowStatus. 201 (20) ospfAuthType (area authentication type) was changed to an 202 interface authentication type to match the key. It also 203 has an additional value, to indicate the use of MD5 for 204 authentication. 206 (21) ospfIfIntfType has a new value, pointToMultipoint. 208 (22) ospfIfDemand (read/write) is added, to permit control of 209 Demand OSPF features. 211 (23) ospfNbrHelloSuppressed is added, (read only). This 212 indicates whether Hellos are being suppressed to the 213 neighbor. 215 4.2. Textual Conventions 217 Several new data types are introduced as a textual convention 218 in this MIB document. These textual conventions enhance the 219 readability of the specification and can ease comparison with 220 other specifications if appropriate. It should be noted that 221 the introduction of the these textual conventions has no 222 effect on either the syntax nor the semantics of any managed 223 objects. The use of these is merely an artifact of the 224 explanatory method used. Objects defined in terms of one of 225 these methods are always encoded by means of the rules that 226 define the primitive type. Hence, no changes to the SMI or 227 the SNMP are necessary to accommodate these textual 228 conventions which are adopted merely for the convenience of 229 readers and writers in pursuit of the elusive goal of clear, 230 concise, and unambiguous MIB documents. 232 The new data types are AreaID, RouterID, TOSType, Metric, 233 BigMetric, Status, PositiveInteger, HelloRange, UpToMaxAge, 234 InterfaceIndex, and DesignatedRouterPriority. 236 4.3. Structure of MIB 238 The MIB is composed of the following sections: 239 General Variables 240 Area Data Structure 241 Area Stub Metric Table 242 Link State Database 243 Address Range Table 244 Host Table 245 Interface Table 246 Interface Metric Table 247 Virtual Interface Table 248 Neighbor Table 249 Virtual Neighbor Table 250 External Link State Database 251 Aggregate Range Table 253 There exists a separate MIB for notifications ("traps"), which 254 is entirely optional. 256 4.3.1. General Variables 258 The General Variables are about what they sound like; 259 variables which are global to the OSPF Process. 261 4.3.2. Area Data Structure and Area Stub Metric Table 263 The Area Data Structure describes the OSPF Areas that the 264 router participates in. The Area Stub Metric Table describes 265 the metrics advertised into a stub area by the default 266 router(s). 268 4.3.3. Link State Database and External Link State Database 270 The Link State Database is provided primarily to provide 271 detailed information for network debugging. 273 4.3.4. Address Table and Host Tables 275 The Address Range Table and Host Table are provided to view 276 configured Network Summary and Host Route information. 278 4.3.5. Interface and Interface Metric Tables 280 The Interface Table and the Interface Metric Table together 281 describe the various IP interfaces to OSPF. The metrics are 282 placed in separate tables in order to simplify dealing with 283 multiple types of service, and to provide flexibility in the 284 event that the IP TOS definition is changed in the future. A 285 Default Value specification is supplied for the TOS 0 286 (default) metric. 288 4.3.6. Virtual Interface Table 290 Likewise, the Virtual Interface Table describe virtual links 291 to the OSPF Process. 293 4.3.7. Neighbor and Virtual Neighbor Tables 295 The Neighbor Table and the Virtual Neighbor Table describe the 296 neighbors to the OSPF Process. 298 4.4. Conceptual Row Creation 300 For the benefit of row-creation in "conceptual" (see [9]) 301 tables, DEFVAL (Default Value) clauses are included in the 302 definitions in section 5, suggesting values which an agent 303 should use for instances of variables which need to be created 304 due to a Set-Request, but which are not specified in the Set- 305 Request. DEFVAL clauses have not been specified for some 306 objects which are read-only, implying that they are zeroed 307 upon row creation. These objects are of the SYNTAX Counter32 308 or Gauge32. 310 For those objects not having a DEFVAL clause, both management 311 stations and agents should heed the Robustness Principle of 312 the Internet (see RFC-791): 314 "be liberal in what you accept, conservative in what you 315 send" 317 That is, management stations should include as many of these 318 columnar objects as possible (e.g., all read-write objects) in 319 a Set-Request when creating a conceptual row; agents should 320 accept a Set-Request with as few of these as they need (e.g., 321 the minimum contents of a row creating SET consists of those 322 objects for which, as they cannot be intuited, no default is 323 specified.). 325 There are numerous read-write objects in this MIB, as it is 326 designed for SNMP management of the protocol, not just SNMP 327 monitoring of its state. However, in the absence of a 328 standard SNMP Security architecture, it is acceptable for 329 implementations to implement these as read-only with an 330 alternative interface for their modification. 332 4.5. Default Configuration 334 OSPF is a powerful routing protocol, equipped with features to 335 handle virtually any configuration requirement that might 336 reasonably be found within an Autonomous System. With this 337 power comes a fair degree of complexity, which the sheer 338 number of objects in the MIB will attest to. Care has 339 therefore been taken, in constructing this MIB, to define 340 default values for virtually every object, to minimize the 341 amount of parameterization required in the typical case. That 342 default configuration is as follows: 344 Given the following assumptions: 346 - IP has already been configured 348 - The ifTable has already been configured 349 - ifSpeed is estimated by the interface drivers 351 - The OSPF Process automatically discovers all IP 352 Interfaces and creates corresponding OSPF Interfaces 354 - The TOS 0 metrics are autonomously derived from ifSpeed 356 - The OSPF Process automatically creates the Areas required 357 for the Interfaces 359 The simplest configuration of an OSPF process requires that: 361 - The OSPF Process be Enabled. 363 This can be accomplished with a single SET: 364 ospfAdminStat := enabled. 366 The configured system will have the following attributes: 368 - The RouterID will be one of the IP addresses of the 369 device 371 - The device will be neither an Area Border Router nor an 372 Autonomous System Border Router. 374 - Every IP Interface, with or without an address, will be 375 an OSPF Interface. 377 - The AreaID of each interface will be 0.0.0.0, the 378 Backbone. 380 - Authentication will be disabled 382 - All Broadcast and Point to Point interfaces will be 383 operational. NBMA Interfaces require the configuration 384 of at least one neighbor. 386 - Timers on all direct interfaces will be: 387 Hello Interval: 10 seconds 388 Dead Timeout: 40 Seconds 389 Retransmission: 5 Seconds 390 Transit Delay: 1 Second 391 Poll Interval: 120 Seconds 393 - no direct links to hosts will be configured. 395 - no addresses will be summarized 397 - Metrics, being a measure of bit duration, are unambiguous 398 and intelligent. 400 - No Virtual Links will be configured. 402 5. Definitions 404 OSPF-MIB DEFINITIONS ::= BEGIN 406 IMPORTS 407 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32, 408 Integer32, IpAddress 409 FROM SNMPv2-SMI 410 TEXTUAL-CONVENTION, TruthValue, RowStatus 411 FROM SNMPv2-TC 412 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 413 mib-2 FROM RFC1213-MIB; 415 -- This MIB module uses the extended OBJECT-TYPE macro as 416 -- defined in [9]. 418 ospf MODULE-IDENTITY 419 LAST-UPDATED "9501091420Z" -- Mon Jan 9 14:20:53 PST 1995 420 ORGANIZATION "IETF OSPF Working Group" 421 CONTACT-INFO 422 " Fred Baker 423 Postal: Advanced Computer Communications 424 315 Bollay Drive 425 Santa Barbara, California 93117 426 Tel: +1 085 685 4455 427 E-Mail: fbaker@acc.com 429 Rob Coltun 430 Postal: RainbowBridge Communications 431 Tel: (301) 340-9416 432 E-Mail: rcoltun@rainbow-bridge.com" 433 DESCRIPTION 434 "The MIB module to describe the OSPF Version 2 435 Protocol" 436 ::= { mib-2 14 } 438 -- The Area ID, in OSPF, has the same format as an IP Address, 439 -- but has the function of defining a summarization point for 440 -- Link State Advertisements 442 AreaID ::= TEXTUAL-CONVENTION 443 STATUS current 444 DESCRIPTION 445 "An OSPF Area Identifier." 446 SYNTAX IpAddress 448 -- The Router ID, in OSPF, has the same format as an IP Address, 449 -- but identifies the router independent of its IP Address. 451 RouterID ::= TEXTUAL-CONVENTION 452 STATUS current 453 DESCRIPTION 454 "A OSPF Router Identifier." 455 SYNTAX IpAddress 457 -- The OSPF Metric is defined as an unsigned value in the range 459 Metric ::= TEXTUAL-CONVENTION 460 STATUS current 461 DESCRIPTION 462 "The OSPF Internal Metric." 463 SYNTAX Integer32 (0..'FFFF'h) 465 BigMetric ::= TEXTUAL-CONVENTION 466 STATUS current 467 DESCRIPTION 468 "The OSPF External Metric." 469 SYNTAX Integer32 (0..'FFFFFF'h) 471 -- Status Values 473 Status ::= TEXTUAL-CONVENTION 474 STATUS current 475 DESCRIPTION 476 "The status of an interface: 'enabled' indicates that 477 it is willing to communicate with other OSPF Routers, 478 while 'disabled' indicates that it is not." 479 SYNTAX INTEGER { enabled (1), disabled (2) } 481 -- Time Durations measured in seconds 483 PositiveInteger ::= TEXTUAL-CONVENTION 484 STATUS current 485 DESCRIPTION 486 "A positive integer. Values in excess are precluded as 487 unnecessary and prone to interoperability issues." 488 SYNTAX Integer32 (0..'7FFFFFFF'h) 490 HelloRange ::= TEXTUAL-CONVENTION 491 STATUS current 492 DESCRIPTION 493 "The range of intervals on which hello messages are 494 exchanged." 495 SYNTAX Integer32 (1..'FFFF'h) 497 UpToMaxAge ::= TEXTUAL-CONVENTION 498 STATUS current 499 DESCRIPTION 500 "The values that one might find or configure for 501 variables bounded by the maximum age of an LSA." 502 SYNTAX Integer32 (0..3600) 504 -- The range of ifIndex 506 InterfaceIndex ::= TEXTUAL-CONVENTION 507 STATUS current 508 DESCRIPTION 509 "The range of ifIndex." 510 SYNTAX Integer32 512 -- Potential Priorities for the Designated Router Election 514 DesignatedRouterPriority ::= TEXTUAL-CONVENTION 515 STATUS current 516 DESCRIPTION 517 "The values defined for the priority of a system for 518 becoming the designated router." 519 SYNTAX Integer32 (0..'FF'h) 521 TOSType ::= TEXTUAL-CONVENTION 522 STATUS current 523 DESCRIPTION 524 "Type of Service is defined as a mapping to the IP Type of 525 Service Flags as defined in the IP Forwarding Table MIB 527 +-----+-----+-----+-----+-----+-----+-----+-----+ 528 | | | | 529 | PRECEDENCE | TYPE OF SERVICE | 0 | 530 | | | | 531 +-----+-----+-----+-----+-----+-----+-----+-----+ 533 IP TOS IP TOS 534 Field Policy Field Policy 535 Contents Code Contents Code 536 0 0 0 0 ==> 0 0 0 0 1 ==> 2 537 0 0 1 0 ==> 4 0 0 1 1 ==> 6 538 0 1 0 0 ==> 8 0 1 0 1 ==> 10 539 0 1 1 0 ==> 12 0 1 1 1 ==> 14 540 1 0 0 0 ==> 16 1 0 0 1 ==> 18 541 1 0 1 0 ==> 20 1 0 1 1 ==> 22 542 1 1 0 0 ==> 24 1 1 0 1 ==> 26 543 1 1 1 0 ==> 28 1 1 1 1 ==> 30 545 The remaining values are left for future definition." 546 SYNTAX Integer32 (0..30) 548 -- OSPF General Variables 550 -- These parameters apply globally to the Router's 551 -- OSPF Process. 553 ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 } 555 ospfRouterId OBJECT-TYPE 556 SYNTAX RouterID 557 MAX-ACCESS read-write 558 STATUS current 559 DESCRIPTION 560 "A 32-bit integer uniquely identifying the 561 router in the Autonomous System. 563 By convention, to ensure uniqueness, this 564 should default to the value of one of the 565 router's IP interface addresses." 566 REFERENCE 567 "OSPF Version 2, C.1 Global parameters" 568 ::= { ospfGeneralGroup 1 } 570 ospfAdminStat OBJECT-TYPE 571 SYNTAX Status 572 MAX-ACCESS read-write 573 STATUS current 574 DESCRIPTION 575 "The administrative status of OSPF in the 576 router. The value 'enabled' denotes that the 577 OSPF Process is active on at least one inter- 578 face; 'disabled' disables it on all inter- 579 faces." 580 ::= { ospfGeneralGroup 2 } 582 ospfVersionNumber OBJECT-TYPE 583 SYNTAX INTEGER { version2 (2) } 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "The current version number of the OSPF proto- 588 col is 2." 589 REFERENCE 590 "OSPF Version 2, Title" 591 ::= { ospfGeneralGroup 3 } 593 ospfAreaBdrRtrStatus OBJECT-TYPE 594 SYNTAX TruthValue 595 MAX-ACCESS read-only 596 STATUS current 597 DESCRIPTION 598 "A flag to note whether this router is an area 599 border router." 600 REFERENCE 601 "OSPF Version 2, Section 3 Splitting the AS into 602 Areas" 603 ::= { ospfGeneralGroup 4 } 605 ospfASBdrRtrStatus OBJECT-TYPE 606 SYNTAX TruthValue 607 MAX-ACCESS read-write 608 STATUS current 609 DESCRIPTION 610 "A flag to note whether this router is config- 611 ured as an Autonomous System border router." 612 REFERENCE 613 "OSPF Version 2, Section 3.3 Classification of 614 routers" 615 ::= { ospfGeneralGroup 5 } 617 ospfExternLsaCount OBJECT-TYPE 618 SYNTAX Gauge32 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The number of external (LS type 5) link-state 623 advertisements in the link-state database." 624 REFERENCE 625 "OSPF Version 2, Appendix A.4.5 AS external link 626 advertisements" 627 ::= { ospfGeneralGroup 6 } 629 ospfExternLsaCksumSum OBJECT-TYPE 630 SYNTAX Integer32 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "The 32-bit unsigned sum of the LS checksums of 635 the external link-state advertisements con- 636 tained in the link-state database. This sum 637 can be used to determine if there has been a 638 change in a router's link state database, and 639 to compare the link-state database of two 640 routers." 641 ::= { ospfGeneralGroup 7 } 643 ospfTOSSupport OBJECT-TYPE 644 SYNTAX TruthValue 645 MAX-ACCESS read-write 646 STATUS current 647 DESCRIPTION 648 "The router's support for type-of-service rout- 649 ing." 650 REFERENCE 651 "OSPF Version 2, Appendix F.1.2 Optional TOS 652 support" 653 ::= { ospfGeneralGroup 8 } 655 ospfOriginateNewLsas OBJECT-TYPE 656 SYNTAX Counter32 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "The number of new link-state advertisements 661 that have been originated. This number is in- 662 cremented each time the router originates a new 663 LSA." 664 ::= { ospfGeneralGroup 9 } 666 ospfRxNewLsas OBJECT-TYPE 667 SYNTAX Counter32 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "The number of link-state advertisements re- 672 ceived determined to be new instantiations. 673 This number does not include newer instantia- 674 tions of self-originated link-state advertise- 675 ments." 676 ::= { ospfGeneralGroup 10 } 678 ospfExtLsdbLimit OBJECT-TYPE 679 SYNTAX Integer32 (-1..'7FFFFFFF'h) 680 MAX-ACCESS read-write 681 STATUS current 682 DESCRIPTION 683 "The maximum number of external link-state en- 684 tries that can be stored in the link-state da- 685 tabase. If the value is -1, then there is no 686 limit. 688 When the number of non-default AS-external-LSAs 689 in a router's link-state database reaches 690 ospfExtLsdbLimit, the router enters Overflow- 691 State. The router never holds more than 692 ospfExtLsdbLimit non-default AS-external-LSAs 693 in its database. OspfExtLsdbLimit MUST be set 694 identically in all routers attached to the OSPF 695 backbone and/or any regular OSPF area. (i.e., 696 OSPF stub areas and NSSAs are excluded)." 697 DEFVAL { -1 } 698 ::= { ospfGeneralGroup 11 } 700 ospfMulticastExtensions OBJECT-TYPE 701 SYNTAX Integer32 702 MAX-ACCESS read-write 703 STATUS current 704 DESCRIPTION 705 "A Bit Mask indicating whether the router is 706 forwarding IP multicast (Class D) datagrams 707 based on the algorithms defined in the Multi- 708 cast Extensions to OSPF. 710 Bit 0, if set, indicates that the router can 711 forward IP multicast datagrams in the router's 712 directly attached areas (called intra-area mul- 713 ticast routing). 715 Bit 1, if set, indicates that the router can 716 forward IP multicast datagrams between OSPF 717 areas (called inter-area multicast routing). 719 Bit 2, if set, indicates that the router can 720 forward IP multicast datagrams between Auto- 721 nomous Systems (called inter-AS multicast rout- 722 ing). 724 Only certain combinations of bit settings are 725 allowed, namely: 0 (no multicast forwarding is 726 enabled), 1 (intra-area multicasting only), 3 727 (intra-area and inter-area multicasting), 5 728 (intra-area and inter-AS multicasting) and 7 729 (multicasting everywhere). By default, no mul- 730 ticast forwarding is enabled." 731 DEFVAL { 0 } 732 ::= { ospfGeneralGroup 12 } 734 ospfExitOverflowInterval OBJECT-TYPE 735 SYNTAX PositiveInteger 736 MAX-ACCESS read-write 737 STATUS current 738 DESCRIPTION 739 "The number of seconds that, after entering 740 OverflowState, a router will attempt to leave 741 OverflowState. This allows the router to again 742 originate non-default AS-external-LSAs. When 743 set to 0, the router will not leave Overflow- 744 State until restarted." 745 DEFVAL { 0 } 746 ::= { ospfGeneralGroup 13 } 748 -- The OSPF Area Data Structure contains information 749 -- regarding the various areas. The interfaces and 750 -- virtual links are configured as part of these areas. 751 -- Area 0.0.0.0, by definition, is the Backbone Area 753 ospfAreaTable OBJECT-TYPE 754 SYNTAX SEQUENCE OF OspfAreaEntry 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "Information describing the configured parame- 759 ters and cumulative statistics of the router's 760 attached areas." 761 REFERENCE 762 "OSPF Version 2, Section 6 The Area Data Struc- 763 ture" 764 ::= { ospf 2 } 766 ospfAreaEntry OBJECT-TYPE 767 SYNTAX OspfAreaEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "Information describing the configured parame- 772 ters and cumulative statistics of one of the 773 router's attached areas." 774 INDEX { ospfAreaId } 775 ::= { ospfAreaTable 1 } 777 OspfAreaEntry ::= 778 SEQUENCE { 779 ospfAreaId 780 AreaID, 781 ospfAuthType 782 Integer32, 783 ospfImportAsExtern 784 INTEGER, 785 ospfSpfRuns 786 Counter32, 787 ospfAreaBdrRtrCount 788 Gauge32, 789 ospfAsBdrRtrCount 790 Gauge32, 792 ospfAreaLsaCount 793 Gauge32, 794 ospfAreaLsaCksumSum 795 Integer32, 796 ospfAreaSummary 797 INTEGER, 798 ospfAreaStatus 799 RowStatus 800 } 802 ospfAreaId OBJECT-TYPE 803 SYNTAX AreaID 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "A 32-bit integer uniquely identifying an area. 808 Area ID 0.0.0.0 is used for the OSPF backbone." 809 REFERENCE 810 "OSPF Version 2, Appendix C.2 Area parameters" 811 ::= { ospfAreaEntry 1 } 813 ospfAuthType OBJECT-TYPE 814 SYNTAX Integer32 815 -- none (0), 816 -- simplePassword (1) 817 -- md5 (2) 818 -- reserved for specification by IANA (> 2) 819 MAX-ACCESS read-create 820 STATUS obsolete 821 DESCRIPTION 822 "The authentication type specified for an area. 823 Additional authentication types may be assigned 824 locally on a per Area basis." 825 REFERENCE 826 "OSPF Version 2, Appendix E Authentication" 827 DEFVAL { 0 } -- no authentication, by default 828 ::= { ospfAreaEntry 2 } 830 ospfImportAsExtern OBJECT-TYPE 831 SYNTAX INTEGER { 832 importExternal (1), 833 importNoExternal (2), 834 importNssa (3) 835 } 836 MAX-ACCESS read-create 837 STATUS current 838 DESCRIPTION 839 "The area's support for importing AS external 840 link- state advertisements." 841 REFERENCE 842 "OSPF Version 2, Appendix C.2 Area parameters" 843 DEFVAL { importExternal } 844 ::= { ospfAreaEntry 3 } 846 ospfSpfRuns OBJECT-TYPE 847 SYNTAX Counter32 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION 851 "The number of times that the intra-area route 852 table has been calculated using this area's 853 link-state database. This is typically done 854 using Dijkstra's algorithm." 855 ::= { ospfAreaEntry 4 } 857 ospfAreaBdrRtrCount OBJECT-TYPE 858 SYNTAX Gauge32 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The total number of area border routers reach- 863 able within this area. This is initially zero, 864 and is calculated in each SPF Pass." 865 ::= { ospfAreaEntry 5 } 867 ospfAsBdrRtrCount OBJECT-TYPE 868 SYNTAX Gauge32 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "The total number of Autonomous System border 873 routers reachable within this area. This is 874 initially zero, and is calculated in each SPF 875 Pass." 876 ::= { ospfAreaEntry 6 } 878 ospfAreaLsaCount OBJECT-TYPE 879 SYNTAX Gauge32 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The total number of link-state advertisements 884 in this area's link-state database, excluding 885 AS External LSA's." 886 ::= { ospfAreaEntry 7 } 888 ospfAreaLsaCksumSum OBJECT-TYPE 889 SYNTAX Integer32 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "The 32-bit unsigned sum of the link-state ad- 894 vertisements' LS checksums contained in this 895 area's link-state database. This sum excludes 896 external (LS type 5) link-state advertisements. 897 The sum can be used to determine if there has 898 been a change in a router's link state data- 899 base, and to compare the link-state database of 900 two routers." 901 DEFVAL { 0 } 902 ::= { ospfAreaEntry 8 } 904 ospfAreaSummary OBJECT-TYPE 905 SYNTAX INTEGER { 906 noAreaSummary (1), 907 sendAreaSummary (2) 908 } 909 MAX-ACCESS read-create 910 STATUS current 911 DESCRIPTION 912 "The variable ospfAreaSummary controls the im- 913 port of summary LSAs into stub areas. It has 914 no effect on other areas. 916 If it is noAreaSummary, the router will neither 917 originate nor propagate summary LSAs into the 918 stub area. It will rely entirely on its de- 919 fault route. 921 If it is sendAreaSummary, the router will both 922 summarize and propagate summary LSAs." 923 DEFVAL { noAreaSummary } 924 ::= { ospfAreaEntry 9 } 926 ospfAreaStatus OBJECT-TYPE 927 SYNTAX RowStatus 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "This variable displays the status of the en- 932 try. Setting it to 'invalid' has the effect of 933 rendering it inoperative. The internal effect 934 (row removal) is implementation dependent." 935 ::= { ospfAreaEntry 10 } 937 -- OSPF Area Default Metric Table 939 -- The OSPF Area Default Metric Table describes the metrics 940 -- that a default Area Border Router will advertise into a 941 -- Stub area. 943 ospfStubAreaTable OBJECT-TYPE 944 SYNTAX SEQUENCE OF OspfStubAreaEntry 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "The set of metrics that will be advertised by 949 a default Area Border Router into a stub area." 950 REFERENCE 951 "OSPF Version 2, Appendix C.2, Area Parameters" 952 ::= { ospf 3 } 954 ospfStubAreaEntry OBJECT-TYPE 955 SYNTAX OspfStubAreaEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "The metric for a given Type of Service that 960 will be advertised by a default Area Border 961 Router into a stub area." 962 REFERENCE 963 "OSPF Version 2, Appendix C.2, Area Parameters" 964 INDEX { ospfStubAreaId, ospfStubTOS } 965 ::= { ospfStubAreaTable 1 } 967 OspfStubAreaEntry ::= 968 SEQUENCE { 969 ospfStubAreaId 970 AreaID, 971 ospfStubTOS 972 TOSType, 973 ospfStubMetric 974 BigMetric, 975 ospfStubStatus 976 RowStatus, 977 ospfStubMetricType 978 INTEGER 979 } 981 ospfStubAreaId OBJECT-TYPE 982 SYNTAX AreaID 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "The 32 bit identifier for the Stub Area. On 987 creation, this can be derived from the in- 988 stance." 989 ::= { ospfStubAreaEntry 1 } 991 ospfStubTOS OBJECT-TYPE 992 SYNTAX TOSType 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION 996 "The Type of Service associated with the 997 metric. On creation, this can be derived from 998 the instance." 999 ::= { ospfStubAreaEntry 2 } 1001 ospfStubMetric OBJECT-TYPE 1002 SYNTAX BigMetric 1003 MAX-ACCESS read-create 1004 STATUS current 1005 DESCRIPTION 1006 "The metric value applied at the indicated type 1007 of service. By default, this equals the least 1008 metric at the type of service among the inter- 1009 faces to other areas." 1010 ::= { ospfStubAreaEntry 3 } 1012 ospfStubStatus OBJECT-TYPE 1013 SYNTAX RowStatus 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "This variable displays the status of the en- 1018 try. Setting it to 'invalid' has the effect of 1019 rendering it inoperative. The internal effect 1020 (row removal) is implementation dependent." 1021 ::= { ospfStubAreaEntry 4 } 1023 ospfStubMetricType OBJECT-TYPE 1024 SYNTAX INTEGER { 1025 ospfMetric (1), -- OSPF Metric 1026 comparableCost (2), -- external type 1 1027 nonComparable (3) -- external type 2 1028 } 1029 MAX-ACCESS read-create 1030 STATUS current 1031 DESCRIPTION 1032 "This variable displays the type of metric ad- 1033 vertised as a default route." 1034 DEFVAL { ospfMetric } 1035 ::= { ospfStubAreaEntry 5 } 1037 -- OSPF Link State Database 1039 -- The Link State Database contains the Link State 1040 -- Advertisements from throughout the areas that the 1041 -- device is attached to. 1043 ospfLsdbTable OBJECT-TYPE 1044 SYNTAX SEQUENCE OF OspfLsdbEntry 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION 1048 "The OSPF Process's Link State Database." 1049 REFERENCE 1050 "OSPF Version 2, Section 12 Link State Adver- 1051 tisements" 1052 ::= { ospf 4 } 1054 ospfLsdbEntry OBJECT-TYPE 1055 SYNTAX OspfLsdbEntry 1056 MAX-ACCESS not-accessible 1057 STATUS current 1058 DESCRIPTION 1059 "A single Link State Advertisement." 1060 INDEX { ospfLsdbAreaId, ospfLsdbType, 1061 ospfLsdbLsid, ospfLsdbRouterId } 1062 ::= { ospfLsdbTable 1 } 1064 OspfLsdbEntry ::= 1065 SEQUENCE { 1066 ospfLsdbAreaId 1067 AreaID, 1068 ospfLsdbType 1069 INTEGER, 1070 ospfLsdbLsid 1071 IpAddress, 1072 ospfLsdbRouterId 1073 RouterID, 1074 ospfLsdbSequence 1075 Integer32, 1076 ospfLsdbAge 1077 Integer32, 1078 ospfLsdbChecksum 1079 Integer32, 1081 ospfLsdbAdvertisement 1082 OCTET STRING 1083 } 1085 ospfLsdbAreaId OBJECT-TYPE 1086 SYNTAX AreaID 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The 32 bit identifier of the Area from which 1091 the LSA was received." 1092 REFERENCE 1093 "OSPF Version 2, Appendix C.2 Area parameters" 1094 ::= { ospfLsdbEntry 1 } 1096 -- External Link State Advertisements are permitted 1097 -- for backward compatibility, but should be displayed in 1098 -- the ospfExtLsdbTable rather than here. 1100 ospfLsdbType OBJECT-TYPE 1101 SYNTAX INTEGER { 1102 routerLink (1), 1103 networkLink (2), 1104 summaryLink (3), 1105 asSummaryLink (4), 1106 asExternalLink (5), -- but see ospfExtLsdbTable 1107 multicastLink (6), 1108 nssaExternalLink (7) 1109 } 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "The type of the link state advertisement. 1114 Each link state type has a separate advertise- 1115 ment format." 1116 REFERENCE 1117 "OSPF Version 2, Appendix A.4.1 The Link State 1118 Advertisement header" 1119 ::= { ospfLsdbEntry 2 } 1121 ospfLsdbLsid OBJECT-TYPE 1122 SYNTAX IpAddress 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "The Link State ID is an LS Type Specific field 1127 containing either a Router ID or an IP Address; 1128 it identifies the piece of the routing domain 1129 that is being described by the advertisement." 1130 REFERENCE 1131 "OSPF Version 2, Section 12.1.4 Link State ID" 1132 ::= { ospfLsdbEntry 3 } 1134 ospfLsdbRouterId OBJECT-TYPE 1135 SYNTAX RouterID 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "The 32 bit number that uniquely identifies the 1140 originating router in the Autonomous System." 1141 REFERENCE 1142 "OSPF Version 2, Appendix C.1 Global parameters" 1143 ::= { ospfLsdbEntry 4 } 1145 -- Note that the OSPF Sequence Number is a 32 bit signed 1146 -- integer. It starts with the value '80000001'h, 1147 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1148 -- Thus, a typical sequence number will be very negative. 1150 ospfLsdbSequence OBJECT-TYPE 1151 SYNTAX Integer32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "The sequence number field is a signed 32-bit 1156 integer. It is used to detect old and dupli- 1157 cate link state advertisements. The space of 1158 sequence numbers is linearly ordered. The 1159 larger the sequence number the more recent the 1160 advertisement." 1161 REFERENCE 1162 "OSPF Version 2, Section 12.1.6 LS sequence 1163 number" 1164 ::= { ospfLsdbEntry 5 } 1166 ospfLsdbAge OBJECT-TYPE 1167 SYNTAX Integer32 -- Should be 0..MaxAge 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "This field is the age of the link state adver- 1172 tisement in seconds." 1173 REFERENCE 1174 "OSPF Version 2, Section 12.1.1 LS age" 1175 ::= { ospfLsdbEntry 6 } 1177 ospfLsdbChecksum OBJECT-TYPE 1178 SYNTAX Integer32 1179 MAX-ACCESS read-only 1180 STATUS current 1181 DESCRIPTION 1182 "This field is the checksum of the complete 1183 contents of the advertisement, excepting the 1184 age field. The age field is excepted so that 1185 an advertisement's age can be incremented 1186 without updating the checksum. The checksum 1187 used is the same that is used for ISO connec- 1188 tionless datagrams; it is commonly referred to 1189 as the Fletcher checksum." 1190 REFERENCE 1191 "OSPF Version 2, Section 12.1.7 LS checksum" 1192 ::= { ospfLsdbEntry 7 } 1194 ospfLsdbAdvertisement OBJECT-TYPE 1195 SYNTAX OCTET STRING (SIZE (1..65535)) 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "The entire Link State Advertisement, including 1200 its header." 1201 REFERENCE 1202 "OSPF Version 2, Section 12 Link State Adver- 1203 tisements" 1204 ::= { ospfLsdbEntry 8 } 1206 -- Address Range Table 1208 -- The Address Range Table acts as an adjunct to the Area 1209 -- Table; It describes those Address Range Summaries that 1210 -- are configured to be propagated from an Area to reduce 1211 -- the amount of information about it which is known beyond 1212 -- its borders. 1214 ospfAreaRangeTable OBJECT-TYPE 1215 SYNTAX SEQUENCE OF OspfAreaRangeEntry 1216 MAX-ACCESS not-accessible 1217 STATUS obsolete 1218 DESCRIPTION 1219 "A range if IP addresses specified by an IP 1220 address/IP network mask pair. For example, 1221 class B address range of X.X.X.X with a network 1222 mask of 255.255.0.0 includes all IP addresses 1223 from X.X.0.0 to X.X.255.255" 1224 REFERENCE 1225 "OSPF Version 2, Appendix C.2 Area parameters" 1226 ::= { ospf 5 } 1228 ospfAreaRangeEntry OBJECT-TYPE 1229 SYNTAX OspfAreaRangeEntry 1230 MAX-ACCESS not-accessible 1231 STATUS obsolete 1232 DESCRIPTION 1233 "A range if IP addresses specified by an IP 1234 address/IP network mask pair. For example, 1235 class B address range of X.X.X.X with a network 1236 mask of 255.255.0.0 includes all IP addresses 1237 from X.X.0.0 to X.X.255.255" 1238 REFERENCE 1239 "OSPF Version 2, Appendix C.2 Area parameters" 1240 INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet } 1241 ::= { ospfAreaRangeTable 1 } 1243 OspfAreaRangeEntry ::= 1244 SEQUENCE { 1245 ospfAreaRangeAreaId 1246 AreaID, 1247 ospfAreaRangeNet 1248 IpAddress, 1249 ospfAreaRangeMask 1250 IpAddress, 1251 ospfAreaRangeStatus 1252 RowStatus, 1253 ospfAreaRangeEffect 1254 INTEGER 1255 } 1257 ospfAreaRangeAreaId OBJECT-TYPE 1258 SYNTAX AreaID 1259 MAX-ACCESS read-only 1260 STATUS obsolete 1261 DESCRIPTION 1262 "The Area the Address Range is to be found 1263 within." 1264 REFERENCE 1265 "OSPF Version 2, Appendix C.2 Area parameters" 1266 ::= { ospfAreaRangeEntry 1 } 1268 ospfAreaRangeNet OBJECT-TYPE 1269 SYNTAX IpAddress 1270 MAX-ACCESS read-only 1271 STATUS obsolete 1272 DESCRIPTION 1273 "The IP Address of the Net or Subnet indicated 1274 by the range." 1275 REFERENCE 1276 "OSPF Version 2, Appendix C.2 Area parameters" 1277 ::= { ospfAreaRangeEntry 2 } 1279 ospfAreaRangeMask OBJECT-TYPE 1280 SYNTAX IpAddress 1281 MAX-ACCESS read-create 1282 STATUS obsolete 1283 DESCRIPTION 1284 "The Subnet Mask that pertains to the Net or 1285 Subnet." 1286 REFERENCE 1287 "OSPF Version 2, Appendix C.2 Area parameters" 1288 ::= { ospfAreaRangeEntry 3 } 1290 ospfAreaRangeStatus OBJECT-TYPE 1291 SYNTAX RowStatus 1292 MAX-ACCESS read-create 1293 STATUS obsolete 1294 DESCRIPTION 1295 "This variable displays the status of the en- 1296 try. Setting it to 'invalid' has the effect of 1297 rendering it inoperative. The internal effect 1298 (row removal) is implementation dependent." 1299 ::= { ospfAreaRangeEntry 4 } 1301 ospfAreaRangeEffect OBJECT-TYPE 1302 SYNTAX INTEGER { 1303 advertiseMatching (1), 1304 doNotAdvertiseMatching (2) 1305 } 1306 MAX-ACCESS read-create 1307 STATUS obsolete 1308 DESCRIPTION 1309 "Subnets subsumed by ranges either trigger the 1310 advertisement of the indicated summary (adver- 1311 tiseMatching), or result in the subnet's not 1312 being advertised at all outside the area." 1313 DEFVAL { advertiseMatching } 1314 ::= { ospfAreaRangeEntry 5 } 1316 -- OSPF Host Table 1318 -- The Host/Metric Table indicates what hosts are directly 1319 -- attached to the Router, and what metrics and types of 1320 -- service should be advertised for them. 1322 ospfHostTable OBJECT-TYPE 1323 SYNTAX SEQUENCE OF OspfHostEntry 1324 MAX-ACCESS not-accessible 1325 STATUS current 1326 DESCRIPTION 1327 "The list of Hosts, and their metrics, that the 1328 router will advertise as host routes." 1329 REFERENCE 1330 "OSPF Version 2, Appendix C.6 Host route param- 1331 eters" 1332 ::= { ospf 6 } 1334 ospfHostEntry OBJECT-TYPE 1335 SYNTAX OspfHostEntry 1336 MAX-ACCESS not-accessible 1337 STATUS current 1338 DESCRIPTION 1339 "A metric to be advertised, for a given type of 1340 service, when a given host is reachable." 1341 INDEX { ospfHostIpAddress, ospfHostTOS } 1342 ::= { ospfHostTable 1 } 1344 OspfHostEntry ::= 1345 SEQUENCE { 1346 ospfHostIpAddress 1347 IpAddress, 1348 ospfHostTOS 1349 TOSType, 1350 ospfHostMetric 1351 Metric, 1352 ospfHostStatus 1353 RowStatus, 1354 ospfHostAreaID 1355 AreaID 1356 } 1358 ospfHostIpAddress OBJECT-TYPE 1359 SYNTAX IpAddress 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "The IP Address of the Host." 1364 REFERENCE 1365 "OSPF Version 2, Appendix C.6 Host route parame- 1366 ters" 1367 ::= { ospfHostEntry 1 } 1369 ospfHostTOS OBJECT-TYPE 1370 SYNTAX TOSType 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The Type of Service of the route being config- 1375 ured." 1376 REFERENCE 1377 "OSPF Version 2, Appendix C.6 Host route parame- 1378 ters" 1379 ::= { ospfHostEntry 2 } 1381 ospfHostMetric OBJECT-TYPE 1382 SYNTAX Metric 1383 MAX-ACCESS read-create 1384 STATUS current 1385 DESCRIPTION 1386 "The Metric to be advertised." 1387 REFERENCE 1388 "OSPF Version 2, Appendix C.6 Host route parame- 1389 ters" 1390 ::= { ospfHostEntry 3 } 1392 ospfHostStatus OBJECT-TYPE 1393 SYNTAX RowStatus 1394 MAX-ACCESS read-create 1395 STATUS current 1396 DESCRIPTION 1397 "This variable displays the status of the en- 1398 try. Setting it to 'invalid' has the effect of 1399 rendering it inoperative. The internal effect 1400 (row removal) is implementation dependent." 1401 ::= { ospfHostEntry 4 } 1403 ospfHostAreaID OBJECT-TYPE 1404 SYNTAX AreaID 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "The Area the Host Entry is to be found within. 1409 By default, the area that a subsuming OSPF in- 1410 terface is in, or 0.0.0.0" 1411 REFERENCE 1412 "OSPF Version 2, Appendix C.2 Area parameters" 1413 ::= { ospfHostEntry 5 } 1415 -- OSPF Interface Table 1417 -- The OSPF Interface Table augments the ipAddrTable 1418 -- with OSPF specific information. 1420 ospfIfTable OBJECT-TYPE 1421 SYNTAX SEQUENCE OF OspfIfEntry 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 "The OSPF Interface Table describes the inter- 1426 faces from the viewpoint of OSPF." 1427 REFERENCE 1428 "OSPF Version 2, Appendix C.3 Router interface 1429 parameters" 1430 ::= { ospf 7 } 1432 ospfIfEntry OBJECT-TYPE 1433 SYNTAX OspfIfEntry 1434 MAX-ACCESS not-accessible 1435 STATUS current 1436 DESCRIPTION 1437 "The OSPF Interface Entry describes one inter- 1438 face from the viewpoint of OSPF." 1439 INDEX { ospfIfIpAddress, ospfAddressLessIf } 1440 ::= { ospfIfTable 1 } 1442 OspfIfEntry ::= 1443 SEQUENCE { 1444 ospfIfIpAddress 1445 IpAddress, 1446 ospfAddressLessIf 1447 Integer32, 1448 ospfIfAreaId 1449 AreaID, 1450 ospfIfType 1451 INTEGER, 1452 ospfIfAdminStat 1453 Status, 1454 ospfIfRtrPriority 1455 DesignatedRouterPriority, 1456 ospfIfTransitDelay 1457 UpToMaxAge, 1458 ospfIfRetransInterval 1459 UpToMaxAge, 1460 ospfIfHelloInterval 1461 HelloRange, 1462 ospfIfRtrDeadInterval 1463 PositiveInteger, 1464 ospfIfPollInterval 1465 PositiveInteger, 1466 ospfIfState 1467 INTEGER, 1468 ospfIfDesignatedRouter 1469 IpAddress, 1470 ospfIfBackupDesignatedRouter 1471 IpAddress, 1472 ospfIfEvents 1473 Counter32, 1474 ospfIfAuthType 1475 INTEGER, 1476 ospfIfAuthKey 1477 OCTET STRING, 1478 ospfIfStatus 1479 RowStatus, 1480 ospfIfMulticastForwarding 1481 INTEGER, 1482 ospfIfDemand 1483 TruthValue 1484 } 1486 ospfIfIpAddress OBJECT-TYPE 1487 SYNTAX IpAddress 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The IP address of this OSPF interface." 1492 ::= { ospfIfEntry 1 } 1494 ospfAddressLessIf OBJECT-TYPE 1495 SYNTAX Integer32 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "For the purpose of easing the instancing of 1500 addressed and addressless interfaces; This 1501 variable takes the value 0 on interfaces with 1502 IP Addresses, and the corresponding value of 1503 ifIndex for interfaces having no IP Address." 1504 ::= { ospfIfEntry 2 } 1506 ospfIfAreaId OBJECT-TYPE 1507 SYNTAX AreaID 1508 MAX-ACCESS read-create 1509 STATUS current 1510 DESCRIPTION 1511 "A 32-bit integer uniquely identifying the area 1512 to which the interface connects. Area ID 1513 0.0.0.0 is used for the OSPF backbone." 1514 DEFVAL { '00000000'H } -- 0.0.0.0 1515 ::= { ospfIfEntry 3 } 1517 ospfIfType OBJECT-TYPE 1518 SYNTAX INTEGER { 1519 broadcast (1), 1520 nbma (2), 1521 pointToPoint (3), 1522 pointToMultipoint (5) 1523 } 1524 MAX-ACCESS read-create 1525 STATUS current 1526 DESCRIPTION 1527 "The OSPF interface type. 1529 By way of a default, this field may be intuited 1530 from the corresponding value of ifType. Broad- 1531 cast LANs, such as Ethernet and IEEE 802.5, 1532 take the value 'broadcast', X.25 and similar 1533 technologies take the value 'nbma', and links 1534 that are definitively point to point take the 1535 value 'pointToPoint'." 1536 ::= { ospfIfEntry 4 } 1538 ospfIfAdminStat OBJECT-TYPE 1539 SYNTAX Status 1540 MAX-ACCESS read-create 1541 STATUS current 1542 DESCRIPTION 1543 "The OSPF interface's administrative status. 1544 The value formed on the interface, and the in- 1545 terface will be advertised as an internal route 1546 to some area. The value 'disabled' denotes 1547 that the interface is external to OSPF." 1548 DEFVAL { enabled } 1549 ::= { ospfIfEntry 5 } 1551 ospfIfRtrPriority OBJECT-TYPE 1552 SYNTAX DesignatedRouterPriority 1553 MAX-ACCESS read-create 1554 STATUS current 1555 DESCRIPTION 1556 "The priority of this interface. Used in 1557 multi-access networks, this field is used in 1558 the designated router election algorithm. The 1559 value 0 signifies that the router is not eligi- 1560 ble to become the designated router on this 1561 particular network. In the event of a tie in 1562 this value, routers will use their Router ID as 1563 a tie breaker." 1564 DEFVAL { 1 } 1565 ::= { ospfIfEntry 6 } 1567 ospfIfTransitDelay OBJECT-TYPE 1568 SYNTAX UpToMaxAge 1569 MAX-ACCESS read-create 1570 STATUS current 1571 DESCRIPTION 1572 "The estimated number of seconds it takes to 1573 transmit a link state update packet over this 1574 interface." 1575 DEFVAL { 1 } 1576 ::= { ospfIfEntry 7 } 1578 ospfIfRetransInterval OBJECT-TYPE 1579 SYNTAX UpToMaxAge 1580 MAX-ACCESS read-create 1581 STATUS current 1582 DESCRIPTION 1583 "The number of seconds between link-state ad- 1584 vertisement retransmissions, for adjacencies 1585 belonging to this interface. This value is 1586 also used when retransmitting database descrip- 1587 tion and link-state request packets." 1588 DEFVAL { 5 } 1589 ::= { ospfIfEntry 8 } 1591 ospfIfHelloInterval OBJECT-TYPE 1592 SYNTAX HelloRange 1593 MAX-ACCESS read-create 1594 STATUS current 1595 DESCRIPTION 1596 "The length of time, in seconds, between the 1597 Hello packets that the router sends on the in- 1598 terface. This value must be the same for all 1599 routers attached to a common network." 1600 DEFVAL { 10 } 1601 ::= { ospfIfEntry 9 } 1603 ospfIfRtrDeadInterval OBJECT-TYPE 1604 SYNTAX PositiveInteger 1605 MAX-ACCESS read-create 1606 STATUS current 1607 DESCRIPTION 1608 "The number of seconds that a router's Hello 1609 packets have not been seen before it's neigh- 1610 bors declare the router down. This should be 1611 some multiple of the Hello interval. This 1612 value must be the same for all routers attached 1613 to a common network." 1614 DEFVAL { 40 } 1615 ::= { ospfIfEntry 10 } 1617 ospfIfPollInterval OBJECT-TYPE 1618 SYNTAX PositiveInteger 1619 MAX-ACCESS read-create 1620 STATUS current 1621 DESCRIPTION 1622 "The larger time interval, in seconds, between 1623 the Hello packets sent to an inactive non- 1624 broadcast multi- access neighbor." 1625 DEFVAL { 120 } 1626 ::= { ospfIfEntry 11 } 1628 ospfIfState OBJECT-TYPE 1629 SYNTAX INTEGER { 1630 down (1), 1631 loopback (2), 1632 waiting (3), 1633 pointToPoint (4), 1634 designatedRouter (5), 1635 backupDesignatedRouter (6), 1636 otherDesignatedRouter (7) 1637 } 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION 1641 "The OSPF Interface State." 1642 DEFVAL { down } 1643 ::= { ospfIfEntry 12 } 1645 ospfIfDesignatedRouter OBJECT-TYPE 1646 SYNTAX IpAddress 1647 MAX-ACCESS read-only 1648 STATUS current 1649 DESCRIPTION 1650 "The IP Address of the Designated Router." 1651 DEFVAL { '00000000'H } -- 0.0.0.0 1652 ::= { ospfIfEntry 13 } 1654 ospfIfBackupDesignatedRouter OBJECT-TYPE 1655 SYNTAX IpAddress 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "The IP Address of the Backup Designated 1660 Router." 1661 DEFVAL { '00000000'H } -- 0.0.0.0 1662 ::= { ospfIfEntry 14 } 1664 ospfIfEvents OBJECT-TYPE 1665 SYNTAX Counter32 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "The number of times this OSPF interface has 1670 changed its state, or an error has occurred." 1671 ::= { ospfIfEntry 15 } 1673 ospfIfAuthKey OBJECT-TYPE 1674 SYNTAX OCTET STRING (SIZE (0..256)) 1675 MAX-ACCESS read-create 1676 STATUS current 1677 DESCRIPTION 1678 "The Authentication Key. If the Area's Author- 1679 ization Type is simplePassword, and the key 1680 length is shorter than 8 octets, the agent will 1681 left adjust and zero fill to 8 octets. 1683 Note that unauthenticated interfaces need no 1684 authentication key, and simple password authen- 1685 tication cannot use a key of more than 8 oc- 1686 tets. Larger keys are useful only with authen- 1687 tication mechanisms not specified in this docu- 1688 ment. 1690 When read, ospfIfAuthKey always returns an Oc- 1691 tet String of length zero." 1692 REFERENCE 1693 "OSPF Version 2, Section 9 The Interface Data 1694 Structure" 1695 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 1696 ::= { ospfIfEntry 16 } 1698 ospfIfStatus OBJECT-TYPE 1699 SYNTAX RowStatus 1700 MAX-ACCESS read-create 1701 STATUS current 1702 DESCRIPTION 1703 "This variable displays the status of the en- 1704 try. Setting it to 'invalid' has the effect of 1705 rendering it inoperative. The internal effect 1706 (row removal) is implementation dependent." 1707 ::= { ospfIfEntry 17 } 1709 ospfIfMulticastForwarding OBJECT-TYPE 1710 SYNTAX INTEGER { 1711 blocked (1), -- no multicast forwarding 1712 multicast (2), -- using multicast address 1713 unicast (3) -- to each OSPF neighbor 1714 } 1715 MAX-ACCESS read-create 1716 STATUS current 1717 DESCRIPTION 1718 "The way multicasts should forwarded on this 1719 interface; not forwarded, forwarded as data 1720 link multicasts, or forwarded as data link uni- 1721 casts. Data link multicasting is not meaning- 1722 ful on point to point and NBMA interfaces, and 1723 setting ospfMulticastForwarding to 0 effective- 1724 ly disables all multicast forwarding." 1725 DEFVAL { blocked } 1726 ::= { ospfIfEntry 18 } 1728 ospfIfDemand OBJECT-TYPE 1729 SYNTAX TruthValue 1730 MAX-ACCESS read-create 1731 STATUS current 1732 DESCRIPTION 1733 "Indicates whether Demand OSPF procedures (hel- 1734 lo supression to FULL neighbors and setting the 1735 DoNotAge flag on proogated LSAs) should be per- 1736 formed on this interface." 1737 DEFVAL { false } 1738 ::= { ospfIfEntry 19 } 1740 ospfIfAuthType OBJECT-TYPE 1741 SYNTAX INTEGER (0..255) 1742 -- none (0), 1743 -- simplePassword (1) 1744 -- md5 (2) 1745 -- reserved for specification by IANA (> 2) 1746 MAX-ACCESS read-create 1747 STATUS current 1748 DESCRIPTION 1749 "The authentication type specified for an in- 1750 terface. Additional authentication types may 1751 be assigned locally." 1752 REFERENCE 1753 "OSPF Version 2, Appendix E Authentication" 1754 DEFVAL { 0 } -- no authentication, by default 1755 ::= { ospfIfEntry 20 } 1757 -- OSPF Interface Metric Table 1759 -- The Metric Table describes the metrics to be advertised 1760 -- for a specified interface at the various types of service. 1761 -- As such, this table is an adjunct of the OSPF Interface 1762 -- Table. 1764 -- Types of service, as defined by RFC 791, have the ability 1765 -- to request low delay, high bandwidth, or reliable linkage. 1767 -- For the purposes of this specification, the measure of 1768 -- bandwidth 1770 -- Metric = 10^8 / ifSpeed 1772 -- is the default value. For multiple link interfaces, note 1773 -- that ifSpeed is the sum of the individual link speeds. 1774 -- This yields a number having the following typical values: 1776 -- Network Type/bit rate Metric 1778 -- >= 100 MBPS 1 1779 -- Ethernet/802.3 10 1780 -- E1 48 1781 -- T1 (ESF) 65 1782 -- 64 KBPS 1562 1783 -- 56 KBPS 1785 1784 -- 19.2 KBPS 5208 1785 -- 9.6 KBPS 10416 1787 -- Routes that are not specified use the default (TOS 0) metric 1789 ospfIfMetricTable OBJECT-TYPE 1790 SYNTAX SEQUENCE OF OspfIfMetricEntry 1791 MAX-ACCESS not-accessible 1792 STATUS current 1793 DESCRIPTION 1794 "The TOS metrics for a non-virtual interface 1795 identified by the interface index." 1796 REFERENCE 1797 "OSPF Version 2, Appendix C.3 Router interface 1798 parameters" 1799 ::= { ospf 8 } 1801 ospfIfMetricEntry OBJECT-TYPE 1802 SYNTAX OspfIfMetricEntry 1803 MAX-ACCESS not-accessible 1804 STATUS current 1805 DESCRIPTION 1806 "A particular TOS metric for a non-virtual in- 1807 terface identified by the interface index." 1808 REFERENCE 1809 "OSPF Version 2, Appendix C.3 Router interface 1810 parameters" 1811 INDEX { ospfIfMetricIpAddress, 1812 ospfIfMetricAddressLessIf, 1813 ospfIfMetricTOS } 1814 ::= { ospfIfMetricTable 1 } 1816 OspfIfMetricEntry ::= 1817 SEQUENCE { 1818 ospfIfMetricIpAddress 1819 IpAddress, 1820 ospfIfMetricAddressLessIf 1821 Integer32, 1822 ospfIfMetricTOS 1823 TOSType, 1824 ospfIfMetricValue 1825 Metric, 1826 ospfIfMetricStatus 1827 RowStatus 1828 } 1830 ospfIfMetricIpAddress OBJECT-TYPE 1831 SYNTAX IpAddress 1832 MAX-ACCESS read-only 1833 STATUS current 1834 DESCRIPTION 1835 "The IP address of this OSPF interface. On row 1836 creation, this can be derived from the in- 1837 stance." 1838 ::= { ospfIfMetricEntry 1 } 1840 ospfIfMetricAddressLessIf OBJECT-TYPE 1841 SYNTAX Integer32 1842 MAX-ACCESS read-only 1843 STATUS current 1844 DESCRIPTION 1845 "For the purpose of easing the instancing of 1846 addressed and addressless interfaces; This 1847 variable takes the value 0 on interfaces with 1848 IP Addresses, and the value of ifIndex for in- 1849 terfaces having no IP Address. On row crea- 1850 tion, this can be derived from the instance." 1851 ::= { ospfIfMetricEntry 2 } 1853 ospfIfMetricTOS OBJECT-TYPE 1854 SYNTAX TOSType 1855 MAX-ACCESS read-only 1856 STATUS current 1857 DESCRIPTION 1858 "The type of service metric being referenced. 1859 On row creation, this can be derived from the 1860 instance." 1861 ::= { ospfIfMetricEntry 3 } 1863 ospfIfMetricValue OBJECT-TYPE 1864 SYNTAX Metric 1865 MAX-ACCESS read-create 1866 STATUS current 1867 DESCRIPTION 1868 "The metric of using this type of service on 1869 this interface. The default value of the TOS 0 1870 Metric is 10^8 / ifSpeed." 1871 ::= { ospfIfMetricEntry 4 } 1873 ospfIfMetricStatus OBJECT-TYPE 1874 SYNTAX RowStatus 1875 MAX-ACCESS read-create 1876 STATUS current 1877 DESCRIPTION 1878 "This variable displays the status of the en- 1879 try. Setting it to 'invalid' has the effect of 1880 rendering it inoperative. The internal effect 1881 (row removal) is implementation dependent." 1882 ::= { ospfIfMetricEntry 5 } 1884 -- OSPF Virtual Interface Table 1886 -- The Virtual Interface Table describes the virtual 1887 -- links that the OSPF Process is configured to 1888 -- carry on. 1890 ospfVirtIfTable OBJECT-TYPE 1891 SYNTAX SEQUENCE OF OspfVirtIfEntry 1892 MAX-ACCESS not-accessible 1893 STATUS current 1894 DESCRIPTION 1895 "Information about this router's virtual inter- 1896 faces." 1897 REFERENCE 1898 "OSPF Version 2, Appendix C.4 Virtual link 1899 parameters" 1900 ::= { ospf 9 } 1902 ospfVirtIfEntry OBJECT-TYPE 1903 SYNTAX OspfVirtIfEntry 1904 MAX-ACCESS not-accessible 1905 STATUS current 1906 DESCRIPTION 1907 "Information about a single Virtual Interface." 1908 INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor } 1909 ::= { ospfVirtIfTable 1 } 1911 OspfVirtIfEntry ::= 1912 SEQUENCE { 1913 ospfVirtIfAreaId 1914 AreaID, 1915 ospfVirtIfNeighbor 1916 RouterID, 1917 ospfVirtIfTransitDelay 1918 UpToMaxAge, 1919 ospfVirtIfRetransInterval 1920 UpToMaxAge, 1921 ospfVirtIfHelloInterval 1922 HelloRange, 1923 ospfVirtIfRtrDeadInterval 1924 PositiveInteger, 1925 ospfVirtIfState 1926 INTEGER, 1927 ospfVirtIfEvents 1928 Counter32, 1929 ospfVirtIfAuthType 1930 INTEGER, 1931 ospfVirtIfAuthKey 1932 OCTET STRING, 1933 ospfVirtIfStatus 1934 RowStatus 1935 } 1937 ospfVirtIfAreaId OBJECT-TYPE 1938 SYNTAX AreaID 1939 MAX-ACCESS read-only 1940 STATUS current 1941 DESCRIPTION 1942 "The Transit Area that the Virtual Link 1943 traverses. By definition, this is not 0.0.0.0" 1944 ::= { ospfVirtIfEntry 1 } 1946 ospfVirtIfNeighbor OBJECT-TYPE 1947 SYNTAX RouterID 1948 MAX-ACCESS read-only 1949 STATUS current 1950 DESCRIPTION 1951 "The Router ID of the Virtual Neighbor." 1952 ::= { ospfVirtIfEntry 2 } 1954 ospfVirtIfTransitDelay OBJECT-TYPE 1955 SYNTAX UpToMaxAge 1956 MAX-ACCESS read-create 1957 STATUS current 1958 DESCRIPTION 1959 "The estimated number of seconds it takes to 1960 transmit a link- state update packet over this 1961 interface." 1962 DEFVAL { 1 } 1963 ::= { ospfVirtIfEntry 3 } 1965 ospfVirtIfRetransInterval OBJECT-TYPE 1966 SYNTAX UpToMaxAge 1967 MAX-ACCESS read-create 1968 STATUS current 1969 DESCRIPTION 1970 "The number of seconds between link-state ad- 1971 vertisement retransmissions, for adjacencies 1972 belonging to this interface. This value is 1973 also used when retransmitting database descrip- 1974 tion and link-state request packets. This 1975 value should be well over the expected round- 1976 trip time." 1977 DEFVAL { 5 } 1978 ::= { ospfVirtIfEntry 4 } 1980 ospfVirtIfHelloInterval OBJECT-TYPE 1981 SYNTAX HelloRange 1982 MAX-ACCESS read-create 1983 STATUS current 1984 DESCRIPTION 1985 "The length of time, in seconds, between the 1986 Hello packets that the router sends on the in- 1987 terface. This value must be the same for the 1988 virtual neighbor." 1989 DEFVAL { 10 } 1990 ::= { ospfVirtIfEntry 5 } 1992 ospfVirtIfRtrDeadInterval OBJECT-TYPE 1993 SYNTAX PositiveInteger 1994 MAX-ACCESS read-create 1995 STATUS current 1996 DESCRIPTION 1997 "The number of seconds that a router's Hello 1998 packets have not been seen before it's neigh- 1999 bors declare the router down. This should be 2000 some multiple of the Hello interval. This 2001 value must be the same for the virtual neigh- 2002 bor." 2003 DEFVAL { 60 } 2004 ::= { ospfVirtIfEntry 6 } 2006 ospfVirtIfState OBJECT-TYPE 2007 SYNTAX INTEGER { 2008 down (1), -- these use the same encoding 2009 pointToPoint (4) -- as the ospfIfTable 2010 } 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "OSPF virtual interface states." 2015 DEFVAL { down } 2016 ::= { ospfVirtIfEntry 7 } 2018 ospfVirtIfEvents OBJECT-TYPE 2019 SYNTAX Counter32 2020 MAX-ACCESS read-only 2021 STATUS current 2022 DESCRIPTION 2023 "The number of state changes or error events on 2024 this Virtual Link" 2025 ::= { ospfVirtIfEntry 8 } 2027 ospfVirtIfAuthKey OBJECT-TYPE 2028 SYNTAX OCTET STRING (SIZE(0..256)) 2029 MAX-ACCESS read-create 2030 STATUS current 2031 DESCRIPTION 2032 "If Authentication Type is simplePassword, the 2033 device will left adjust and zero fill to 8 oc- 2034 tets. 2036 Note that unauthenticated interfaces need no 2037 authentication key, and simple password authen- 2038 tication cannot use a key of more than 8 oc- 2039 tets. Larger keys are useful only with authen- 2040 tication mechanisms not specified in this docu- 2041 ment. 2043 When read, ospfVifAuthKey always returns a 2044 string of length zero." 2045 REFERENCE 2046 "OSPF Version 2, Section 9 The Interface Data 2047 Structure" 2048 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 2049 ::= { ospfVirtIfEntry 9 } 2051 ospfVirtIfStatus OBJECT-TYPE 2052 SYNTAX RowStatus 2053 MAX-ACCESS read-create 2054 STATUS current 2055 DESCRIPTION 2056 "This variable displays the status of the en- 2057 try. Setting it to 'invalid' has the effect of 2058 rendering it inoperative. The internal effect 2059 (row removal) is implementation dependent." 2060 ::= { ospfVirtIfEntry 10 } 2062 ospfVirtIfAuthType OBJECT-TYPE 2063 SYNTAX INTEGER (0..255) 2064 -- none (0), 2065 -- simplePassword (1) 2066 -- md5 (2) 2067 -- reserved for specification by IANA (> 2) 2068 MAX-ACCESS read-create 2069 STATUS current 2070 DESCRIPTION 2071 "The authentication type specified for a virtu- 2072 al interface. Additional authentication types 2073 may be assigned locally." 2074 REFERENCE 2075 "OSPF Version 2, Appendix E Authentication" 2076 DEFVAL { 0 } -- no authentication, by default 2077 ::= { ospfVirtIfEntry 11 } 2079 -- OSPF Neighbor Table 2081 -- The OSPF Neighbor Table describes all neighbors in 2082 -- the locality of the subject router. 2084 ospfNbrTable OBJECT-TYPE 2085 SYNTAX SEQUENCE OF OspfNbrEntry 2086 MAX-ACCESS not-accessible 2087 STATUS current 2088 DESCRIPTION 2089 "A table of non-virtual neighbor information." 2090 REFERENCE 2091 "OSPF Version 2, Section 10 The Neighbor Data 2092 Structure" 2093 ::= { ospf 10 } 2095 ospfNbrEntry OBJECT-TYPE 2096 SYNTAX OspfNbrEntry 2097 MAX-ACCESS not-accessible 2098 STATUS current 2099 DESCRIPTION 2100 "The information regarding a single neighbor." 2101 REFERENCE 2102 "OSPF Version 2, Section 10 The Neighbor Data 2103 Structure" 2104 INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex } 2105 ::= { ospfNbrTable 1 } 2107 OspfNbrEntry ::= 2108 SEQUENCE { 2109 ospfNbrIpAddr 2110 IpAddress, 2111 ospfNbrAddressLessIndex 2112 InterfaceIndex, 2113 ospfNbrRtrId 2114 RouterID, 2115 ospfNbrOptions 2116 Integer32, 2117 ospfNbrPriority 2118 DesignatedRouterPriority, 2119 ospfNbrState 2120 INTEGER, 2121 ospfNbrEvents 2122 Counter32, 2124 ospfNbrLsRetransQLen 2125 Gauge32, 2126 ospfNbmaNbrStatus 2127 RowStatus, 2128 ospfNbmaNbrPermanence 2129 INTEGER, 2130 ospfNbrHelloSuppressed 2131 TruthValue 2132 } 2134 ospfNbrIpAddr OBJECT-TYPE 2135 SYNTAX IpAddress 2136 MAX-ACCESS read-only 2137 STATUS current 2138 DESCRIPTION 2139 "The IP address this neighbor is using in its 2140 IP Source Address. Note that, on addressless 2141 links, this will not be 0.0.0.0, but the ad- 2142 dress of another of the neighbor's interfaces." 2143 ::= { ospfNbrEntry 1 } 2145 ospfNbrAddressLessIndex OBJECT-TYPE 2146 SYNTAX InterfaceIndex 2147 MAX-ACCESS read-only 2148 STATUS current 2149 DESCRIPTION 2150 "On an interface having an IP Address, zero. 2151 On addressless interfaces, the corresponding 2152 value of ifIndex in the Internet Standard MIB. 2153 On row creation, this can be derived from the 2154 instance." 2155 ::= { ospfNbrEntry 2 } 2157 ospfNbrRtrId OBJECT-TYPE 2158 SYNTAX RouterID 2159 MAX-ACCESS read-only 2160 STATUS current 2161 DESCRIPTION 2162 "A 32-bit integer (represented as a type IpAd- 2163 dress) uniquely identifying the neighboring 2164 router in the Autonomous System." 2165 DEFVAL { '00000000'H } -- 0.0.0.0 2166 ::= { ospfNbrEntry 3 } 2168 ospfNbrOptions OBJECT-TYPE 2169 SYNTAX Integer32 2170 MAX-ACCESS read-only 2171 STATUS current 2172 DESCRIPTION 2173 "A Bit Mask corresponding to the neighbor's op- 2174 tions field. 2176 Bit 0, if set, indicates that the system will 2177 operate on Type of Service metrics other than 2178 TOS 0. If zero, the neighbor will ignore all 2179 metrics except the TOS 0 metric. 2181 Bit 1, if set, indicates that the associated 2182 area accepts and operates on external informa- 2183 tion; if zero, it is a stub area. 2185 Bit 2, if set, indicates that the system is ca- 2186 pable of routing IP Multicast datagrams; i.e., 2187 that it implements the Multicast Extensions to 2188 OSPF. 2190 Bit 3, if set, indicates that the associated 2191 area is an NSSA. These areas are capable of 2192 carrying type 7 external advertisements, which 2193 are translated into type 5 external advertise- 2194 ments at NSSA borders." 2195 REFERENCE 2196 "OSPF Version 2, Section 12.1.2 Options" 2197 DEFVAL { 0 } 2198 ::= { ospfNbrEntry 4 } 2200 ospfNbrPriority OBJECT-TYPE 2201 SYNTAX DesignatedRouterPriority 2202 MAX-ACCESS read-create 2203 STATUS current 2204 DESCRIPTION 2205 "The priority of this neighbor in the designat- 2206 ed router election algorithm. The value 0 sig- 2207 nifies that the neighbor is not eligible to be- 2208 come the designated router on this particular 2209 network." 2210 DEFVAL { 1 } 2211 ::= { ospfNbrEntry 5 } 2213 ospfNbrState OBJECT-TYPE 2214 SYNTAX INTEGER { 2215 down (1), 2216 attempt (2), 2217 init (3), 2218 twoWay (4), 2219 exchangeStart (5), 2220 exchange (6), 2221 loading (7), 2222 full (8) 2223 } 2224 MAX-ACCESS read-only 2225 STATUS current 2226 DESCRIPTION 2227 "The State of the relationship with this Neigh- 2228 bor." 2229 REFERENCE 2230 "OSPF Version 2, Section 10.1 Neighbor States" 2231 DEFVAL { down } 2232 ::= { ospfNbrEntry 6 } 2234 ospfNbrEvents OBJECT-TYPE 2235 SYNTAX Counter32 2236 MAX-ACCESS read-only 2237 STATUS current 2238 DESCRIPTION 2239 "The number of times this neighbor relationship 2240 has changed state, or an error has occurred." 2241 ::= { ospfNbrEntry 7 } 2243 ospfNbrLsRetransQLen OBJECT-TYPE 2244 SYNTAX Gauge32 2245 MAX-ACCESS read-only 2246 STATUS current 2247 DESCRIPTION 2248 "The current length of the retransmission 2249 queue." 2250 ::= { ospfNbrEntry 8 } 2252 ospfNbmaNbrStatus OBJECT-TYPE 2253 SYNTAX RowStatus 2254 MAX-ACCESS read-create 2255 STATUS current 2256 DESCRIPTION 2257 "This variable displays the status of the en- 2258 try. Setting it to 'invalid' has the effect of 2259 rendering it inoperative. The internal effect 2260 (row removal) is implementation dependent." 2261 ::= { ospfNbrEntry 9 } 2263 ospfNbmaNbrPermanence OBJECT-TYPE 2264 SYNTAX INTEGER { 2265 dynamic (1), -- learned through protocol 2266 permanent (2) -- configured address 2267 } 2268 MAX-ACCESS read-only 2269 STATUS current 2270 DESCRIPTION 2271 "This variable displays the status of the en- 2272 try. 'dynamic' and 'permanent' refer to how 2273 the neighbor became known." 2274 DEFVAL { permanent } 2275 ::= { ospfNbrEntry 10 } 2277 ospfNbrHelloSuppressed OBJECT-TYPE 2278 SYNTAX TruthValue 2279 MAX-ACCESS read-only 2280 STATUS current 2281 DESCRIPTION 2282 "Indicates whether Hellos are being suppressed 2283 to the neighbor" 2284 ::= { ospfNbrEntry 11 } 2286 -- OSPF Virtual Neighbor Table 2288 -- This table describes all virtual neighbors. 2289 -- Since Virtual Links are configured in the 2290 -- virtual interface table, this table is read-only. 2292 ospfVirtNbrTable OBJECT-TYPE 2293 SYNTAX SEQUENCE OF OspfVirtNbrEntry 2294 MAX-ACCESS not-accessible 2295 STATUS current 2296 DESCRIPTION 2297 "A table of virtual neighbor information." 2298 REFERENCE 2299 "OSPF Version 2, Section 15 Virtual Links" 2300 ::= { ospf 11 } 2302 ospfVirtNbrEntry OBJECT-TYPE 2303 SYNTAX OspfVirtNbrEntry 2304 MAX-ACCESS not-accessible 2305 STATUS current 2306 DESCRIPTION 2307 "Virtual neighbor information." 2308 INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId } 2309 ::= { ospfVirtNbrTable 1 } 2311 OspfVirtNbrEntry ::= 2312 SEQUENCE { 2313 ospfVirtNbrArea 2314 AreaID, 2315 ospfVirtNbrRtrId 2316 RouterID, 2317 ospfVirtNbrIpAddr 2318 IpAddress, 2319 ospfVirtNbrOptions 2320 Integer32, 2321 ospfVirtNbrState 2322 INTEGER, 2323 ospfVirtNbrEvents 2324 Counter32, 2325 ospfVirtNbrLsRetransQLen 2326 Gauge32 2327 } 2329 ospfVirtNbrArea OBJECT-TYPE 2330 SYNTAX AreaID 2331 MAX-ACCESS read-only 2332 STATUS current 2333 DESCRIPTION 2334 "The Transit Area Identifier." 2335 ::= { ospfVirtNbrEntry 1 } 2337 ospfVirtNbrRtrId OBJECT-TYPE 2338 SYNTAX RouterID 2339 MAX-ACCESS read-only 2340 STATUS current 2341 DESCRIPTION 2342 "A 32-bit integer uniquely identifying the 2343 neighboring router in the Autonomous System." 2344 ::= { ospfVirtNbrEntry 2 } 2346 ospfVirtNbrIpAddr OBJECT-TYPE 2347 SYNTAX IpAddress 2348 MAX-ACCESS read-only 2349 STATUS current 2350 DESCRIPTION 2351 "The IP address this Virtual Neighbor is us- 2352 ing." 2353 ::= { ospfVirtNbrEntry 3 } 2355 ospfVirtNbrOptions OBJECT-TYPE 2356 SYNTAX Integer32 2357 MAX-ACCESS read-only 2358 STATUS current 2359 DESCRIPTION 2360 "A Bit Mask corresponding to the neighbor's op- 2361 tions field. 2363 Bit 1, if set, indicates that the system will 2364 operate on Type of Service metrics other than 2365 TOS 0. If zero, the neighbor will ignore all 2366 metrics except the TOS 0 metric. 2368 Bit 2, if set, indicates that the system is 2369 Network Multicast capable; ie, that it imple- 2370 ments OSPF Multicast Routing." 2371 ::= { ospfVirtNbrEntry 4 } 2373 ospfVirtNbrState OBJECT-TYPE 2374 SYNTAX INTEGER { 2375 down (1), 2376 attempt (2), 2377 init (3), 2378 twoWay (4), 2379 exchangeStart (5), 2380 exchange (6), 2381 loading (7), 2382 full (8) 2383 } 2384 MAX-ACCESS read-only 2385 STATUS current 2386 DESCRIPTION 2387 "The state of the Virtual Neighbor Relation- 2388 ship." 2389 ::= { ospfVirtNbrEntry 5 } 2391 ospfVirtNbrEvents OBJECT-TYPE 2392 SYNTAX Counter32 2393 MAX-ACCESS read-only 2394 STATUS current 2395 DESCRIPTION 2396 "The number of times this virtual link has 2397 changed its state, or an error has occurred." 2398 ::= { ospfVirtNbrEntry 6 } 2400 ospfVirtNbrLsRetransQLen OBJECT-TYPE 2401 SYNTAX Gauge32 2402 MAX-ACCESS read-only 2403 STATUS current 2404 DESCRIPTION 2405 "The current length of the retransmission 2406 queue." 2407 ::= { ospfVirtNbrEntry 7 } 2409 -- OSPF Link State Database, External 2411 -- The Link State Database contains the Link State 2412 -- Advertisements from throughout the areas that the 2413 -- device is attached to. 2415 -- This table is identical to the OSPF LSDB Table in 2416 -- format, but contains only External Link State 2417 -- Advertisements. The purpose is to allow external 2418 -- LSAs to be displayed once for the router rather 2419 -- than once in each non-stub area. 2421 ospfExtLsdbTable OBJECT-TYPE 2422 SYNTAX SEQUENCE OF OspfExtLsdbEntry 2423 MAX-ACCESS not-accessible 2424 STATUS current 2425 DESCRIPTION 2426 "The OSPF Process's Links State Database." 2427 REFERENCE 2428 "OSPF Version 2, Section 12 Link State Adver- 2429 tisements" 2430 ::= { ospf 12 } 2432 ospfExtLsdbEntry OBJECT-TYPE 2433 SYNTAX OspfExtLsdbEntry 2434 MAX-ACCESS not-accessible 2435 STATUS current 2436 DESCRIPTION 2437 "A single Link State Advertisement." 2438 INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId } 2439 ::= { ospfExtLsdbTable 1 } 2441 OspfExtLsdbEntry ::= 2442 SEQUENCE { 2443 ospfExtLsdbType 2444 INTEGER, 2445 ospfExtLsdbLsid 2446 IpAddress, 2447 ospfExtLsdbRouterId 2448 RouterID, 2449 ospfExtLsdbSequence 2450 Integer32, 2451 ospfExtLsdbAge 2452 Integer32, 2454 ospfExtLsdbChecksum 2455 Integer32, 2456 ospfExtLsdbAdvertisement 2457 OCTET STRING 2458 } 2460 ospfExtLsdbType OBJECT-TYPE 2461 SYNTAX INTEGER { 2462 asExternalLink (5) 2463 } 2464 MAX-ACCESS read-only 2465 STATUS current 2466 DESCRIPTION 2467 "The type of the link state advertisement. 2468 Each link state type has a separate advertise- 2469 ment format." 2470 REFERENCE 2471 "OSPF Version 2, Appendix A.4.1 The Link State 2472 Advertisement header" 2473 ::= { ospfExtLsdbEntry 1 } 2475 ospfExtLsdbLsid OBJECT-TYPE 2476 SYNTAX IpAddress 2477 MAX-ACCESS read-only 2478 STATUS current 2479 DESCRIPTION 2480 "The Link State ID is an LS Type Specific field 2481 containing either a Router ID or an IP Address; 2482 it identifies the piece of the routing domain 2483 that is being described by the advertisement." 2484 REFERENCE 2485 "OSPF Version 2, Section 12.1.4 Link State ID" 2486 ::= { ospfExtLsdbEntry 2 } 2488 ospfExtLsdbRouterId OBJECT-TYPE 2489 SYNTAX RouterID 2490 MAX-ACCESS read-only 2491 STATUS current 2492 DESCRIPTION 2493 "The 32 bit number that uniquely identifies the 2494 originating router in the Autonomous System." 2495 REFERENCE 2496 "OSPF Version 2, Appendix C.1 Global parameters" 2497 ::= { ospfExtLsdbEntry 3 } 2499 -- Note that the OSPF Sequence Number is a 32 bit signed 2500 -- integer. It starts with the value '80000001'h, 2501 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 2502 -- Thus, a typical sequence number will be very negative. 2504 ospfExtLsdbSequence OBJECT-TYPE 2505 SYNTAX Integer32 2506 MAX-ACCESS read-only 2507 STATUS current 2508 DESCRIPTION 2509 "The sequence number field is a signed 32-bit 2510 integer. It is used to detect old and dupli- 2511 cate link state advertisements. The space of 2512 sequence numbers is linearly ordered. The 2513 larger the sequence number the more recent the 2514 advertisement." 2515 REFERENCE 2516 "OSPF Version 2, Section 12.1.6 LS sequence 2517 number" 2518 ::= { ospfExtLsdbEntry 4 } 2520 ospfExtLsdbAge OBJECT-TYPE 2521 SYNTAX Integer32 -- Should be 0..MaxAge 2522 MAX-ACCESS read-only 2523 STATUS current 2524 DESCRIPTION 2525 "This field is the age of the link state adver- 2526 tisement in seconds." 2527 REFERENCE 2528 "OSPF Version 2, Section 12.1.1 LS age" 2529 ::= { ospfExtLsdbEntry 5 } 2531 ospfExtLsdbChecksum OBJECT-TYPE 2532 SYNTAX Integer32 2533 MAX-ACCESS read-only 2534 STATUS current 2535 DESCRIPTION 2536 "This field is the checksum of the complete 2537 contents of the advertisement, excepting the 2538 age field. The age field is excepted so that 2539 an advertisement's age can be incremented 2540 without updating the checksum. The checksum 2541 used is the same that is used for ISO connec- 2542 tionless datagrams; it is commonly referred to 2543 as the Fletcher checksum." 2544 REFERENCE 2545 "OSPF Version 2, Section 12.1.7 LS checksum" 2546 ::= { ospfExtLsdbEntry 6 } 2548 ospfExtLsdbAdvertisement OBJECT-TYPE 2549 SYNTAX OCTET STRING (SIZE(36)) 2550 MAX-ACCESS read-only 2551 STATUS current 2552 DESCRIPTION 2553 "The entire Link State Advertisement, including 2554 its header." 2555 REFERENCE 2556 "OSPF Version 2, Section 12 Link State Adver- 2557 tisements" 2558 ::= { ospfExtLsdbEntry 7 } 2560 -- OSPF Use of the CIDR Route Table 2562 ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 } 2564 -- The IP Forwarding Table defines a number of objects for use by 2565 -- the routing protocol to externalize its information. Most of 2566 -- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy, 2567 -- ipForwardNextHop, ipForwardIfIndex, ipForwardType, 2568 -- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are 2569 -- defined there. 2571 -- Those that leave some discretion are defined here. 2573 -- ipCidrRouteProto is, of course, ospf (13). 2575 -- ipCidrRouteAge is the time since the route was first calculated, 2576 -- as opposed to the time since the last SPF run. 2578 -- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing 2579 -- protocol. The following values shall be found there depending 2580 -- on the way the route was calculated. 2582 ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 } 2583 ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 } 2584 ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 } 2585 ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 } 2587 -- ipCidrRouteMetric1 is, by definition, the primary routing 2588 -- metric. Therefore, it should be the metric that route 2589 -- selection is based on. For intra-area and inter-area routes, 2590 -- it is an OSPF metric. For External Type 1 (comparable value) 2591 -- routes, it is an OSPF metric plus the External Metric. For 2592 -- external Type 2 (non-comparable value) routes, it is the 2593 -- external metric. 2595 -- ipCidrRouteMetric2 is, by definition, a secondary routing 2596 -- metric. Therefore, it should be the metric that breaks a tie 2597 -- among routes having equal metric1 values and the same 2598 -- calculation rule. For intra-area, inter-area routes, and 2599 -- External Type 1 (comparable value) routes, it is unused. For 2600 -- external Type 2 (non-comparable value) routes, it is the metric 2601 -- to the AS border router. 2603 -- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 are 2604 -- unused. 2606 -- 2607 -- The OSPF Area Aggregate Table 2608 -- 2609 -- This table replaces the OSPF Area Summary Table, being an 2610 -- extension of that for CIDR routers. 2612 ospfAreaAggregateTable OBJECT-TYPE 2613 SYNTAX SEQUENCE OF OspfAreaAggregateEntry 2614 MAX-ACCESS not-accessible 2615 STATUS current 2616 DESCRIPTION 2617 "A range of IP addresses specified by an IP 2618 address/IP network mask pair. For example, 2619 class B address range of X.X.X.X with a network 2620 mask of 255.255.0.0 includes all IP addresses 2621 from X.X.0.0 to X.X.255.255. Note that if 2622 ranges are configured such that one range sub- 2623 sumes another range (e.g., 10.0.0.0 mask 2624 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2625 most specific match is the preferred one." 2626 REFERENCE 2627 "OSPF Version 2, Appendix C.2 Area parameters" 2628 ::= { ospf 14 } 2630 ospfAreaAggregateEntry OBJECT-TYPE 2631 SYNTAX OspfAreaAggregateEntry 2632 MAX-ACCESS not-accessible 2633 STATUS current 2634 DESCRIPTION 2635 "A range of IP addresses specified by an IP 2636 address/IP network mask pair. For example, 2637 class B address range of X.X.X.X with a network 2638 mask of 255.255.0.0 includes all IP addresses 2639 from X.X.0.0 to X.X.255.255. Note that if 2640 ranges are range configured such that one range 2641 subsumes another range (e.g., 10.0.0.0 mask 2642 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2643 most specific match is the preferred one." 2644 REFERENCE 2645 "OSPF Version 2, Appendix C.2 Area parameters" 2646 INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType, 2647 ospfAreaAggregateNet, ospfAreaAggregateMask } 2648 ::= { ospfAreaAggregateTable 1 } 2650 OspfAreaAggregateEntry ::= 2651 SEQUENCE { 2652 ospfAreaAggregateAreaID 2653 AreaID, 2654 ospfAreaAggregateLsdbType 2655 INTEGER, 2656 ospfAreaAggregateNet 2657 IpAddress, 2658 ospfAreaAggregateMask 2659 IpAddress, 2660 ospfAreaAggregateStatus 2661 RowStatus, 2662 ospfAreaAggregateEffect 2663 INTEGER 2664 } 2666 ospfAreaAggregateAreaID OBJECT-TYPE 2667 SYNTAX AreaID 2668 MAX-ACCESS read-only 2669 STATUS current 2670 DESCRIPTION 2671 "The Area the Address Aggregate is to be found 2672 within." 2673 REFERENCE 2674 "OSPF Version 2, Appendix C.2 Area parameters" 2675 ::= { ospfAreaAggregateEntry 1 } 2677 ospfAreaAggregateLsdbType OBJECT-TYPE 2678 SYNTAX INTEGER { 2679 summaryLink (3), 2680 nssaExternalLink (7) 2681 } 2682 MAX-ACCESS read-only 2683 STATUS current 2684 DESCRIPTION 2685 "The type of the Address Aggregate. This field 2686 specifies the Lsdb type that this Address Ag- 2687 gregate applies to." 2688 REFERENCE 2689 "OSPF Version 2, Appendix A.4.1 The Link State 2690 Advertisement header" 2691 ::= { ospfAreaAggregateEntry 2 } 2693 ospfAreaAggregateNet OBJECT-TYPE 2694 SYNTAX IpAddress 2695 MAX-ACCESS read-only 2696 STATUS current 2697 DESCRIPTION 2698 "The IP Address of the Net or Subnet indicated 2699 by the range." 2700 REFERENCE 2701 "OSPF Version 2, Appendix C.2 Area parameters" 2702 ::= { ospfAreaAggregateEntry 3 } 2704 ospfAreaAggregateMask OBJECT-TYPE 2705 SYNTAX IpAddress 2706 MAX-ACCESS read-only 2707 STATUS current 2708 DESCRIPTION 2709 "The Subnet Mask that pertains to the Net or 2710 Subnet." 2711 REFERENCE 2712 "OSPF Version 2, Appendix C.2 Area parameters" 2713 ::= { ospfAreaAggregateEntry 4 } 2715 ospfAreaAggregateStatus OBJECT-TYPE 2716 SYNTAX RowStatus 2717 MAX-ACCESS read-create 2718 STATUS current 2719 DESCRIPTION 2720 "This variable displays the status of the en- 2721 try. Setting it to 'invalid' has the effect of 2722 rendering it inoperative. The internal effect 2723 (row removal) is implementation dependent." 2724 ::= { ospfAreaAggregateEntry 5 } 2726 ospfAreaAggregateEffect OBJECT-TYPE 2727 SYNTAX INTEGER { 2728 advertiseMatching (1), 2729 doNotAdvertiseMatching (2) 2730 } 2731 MAX-ACCESS read-create 2732 STATUS current 2733 DESCRIPTION 2734 "Subnets subsumed by ranges either trigger the 2735 advertisement of the indicated aggregate (ad- 2736 vertiseMatching), or result in the subnet's not 2737 being advertised at all outside the area." 2738 DEFVAL { advertiseMatching } 2739 ::= { ospfAreaAggregateEntry 6 } 2741 -- conformance information 2743 ospfConformance OBJECT IDENTIFIER ::= { ospf 15 } 2745 ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 } 2746 ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 } 2748 -- compliance statements 2750 ospfCompliance MODULE-COMPLIANCE 2751 STATUS current 2752 DESCRIPTION 2753 "The compliance statement " 2754 MODULE -- this module 2755 MANDATORY-GROUPS { 2756 ospfBasicGroup, 2757 ospfAreaGroup, 2758 ospfStubAreaGroup, 2759 ospfIfGroup, 2760 ospfIfMetricGroup, 2761 ospfVirtIfGroup, 2762 ospfNbrGroup, 2763 ospfVirtNbrGroup, 2764 ospfAreaAggregateGroup 2765 } 2766 ::= { ospfCompliances 1 } 2768 -- units of conformance 2770 ospfBasicGroup OBJECT-GROUP 2771 OBJECTS { 2772 ospfRouterId, 2773 ospfAdminStat, 2774 ospfVersionNumber, 2775 ospfAreaBdrRtrStatus, 2776 ospfASBdrRtrStatus, 2777 ospfExternLsaCount, 2778 ospfExternLsaCksumSum, 2779 ospfTOSSupport, 2780 ospfOriginateNewLsas, 2781 ospfRxNewLsas, 2782 ospfExtLsdbLimit, 2783 ospfMulticastExtensions, 2784 ospfExitOverflowInterval 2785 } 2786 STATUS current 2787 DESCRIPTION 2788 "These objects are required for OSPF systems." 2789 ::= { ospfGroups 1 } 2791 ospfAreaGroup OBJECT-GROUP 2792 OBJECTS { 2793 ospfAreaId, 2794 ospfImportAsExtern, 2795 ospfSpfRuns, 2796 ospfAreaBdrRtrCount, 2797 ospfAsBdrRtrCount, 2798 ospfAreaLsaCount, 2799 ospfAreaLsaCksumSum, 2800 ospfAreaSummary, 2801 ospfAreaStatus 2802 } 2803 STATUS current 2804 DESCRIPTION 2805 "These objects are required for OSPF systems 2806 supporting areas." 2807 ::= { ospfGroups 2 } 2809 ospfStubAreaGroup OBJECT-GROUP 2810 OBJECTS { 2811 ospfStubAreaId, 2812 ospfStubTOS, 2813 ospfStubMetric, 2814 ospfStubStatus, 2815 ospfStubMetricType 2816 } 2817 STATUS current 2818 DESCRIPTION 2819 "These objects are required for OSPF systems 2820 supporting stub areas." 2821 ::= { ospfGroups 3 } 2823 ospfLsdbGroup OBJECT-GROUP 2824 OBJECTS { 2825 ospfLsdbAreaId, 2826 ospfLsdbType, 2827 ospfLsdbLsid, 2828 ospfLsdbRouterId, 2829 ospfLsdbSequence, 2830 ospfLsdbAge, 2831 ospfLsdbChecksum, 2832 ospfLsdbAdvertisement 2833 } 2834 STATUS current 2835 DESCRIPTION 2836 "These objects are required for OSPF systems 2837 that display their link state database." 2838 ::= { ospfGroups 4 } 2840 ospfAreaRangeGroup OBJECT-GROUP 2841 OBJECTS { 2842 ospfAreaRangeAreaId, 2843 ospfAreaRangeNet, 2844 ospfAreaRangeMask, 2845 ospfAreaRangeStatus, 2846 ospfAreaRangeEffect 2847 } 2848 STATUS obsolete 2849 DESCRIPTION 2850 "These objects are required for non-CIDR OSPF 2851 systems that support multiple areas." 2852 ::= { ospfGroups 5 } 2854 ospfHostGroup OBJECT-GROUP 2855 OBJECTS { 2856 ospfHostIpAddress, 2857 ospfHostTOS, 2858 ospfHostMetric, 2859 ospfHostStatus, 2860 ospfHostAreaID 2861 } 2862 STATUS current 2863 DESCRIPTION 2864 "These objects are required for OSPF systems 2865 that support attached hosts." 2866 ::= { ospfGroups 6 } 2868 ospfIfGroup OBJECT-GROUP 2869 OBJECTS { 2870 ospfIfIpAddress, 2871 ospfAddressLessIf, 2872 ospfIfAreaId, 2873 ospfIfType, 2874 ospfIfAdminStat, 2875 ospfIfRtrPriority, 2876 ospfIfTransitDelay, 2877 ospfIfRetransInterval, 2878 ospfIfHelloInterval, 2879 ospfIfRtrDeadInterval, 2880 ospfIfPollInterval, 2881 ospfIfState, 2882 ospfIfDesignatedRouter, 2883 ospfIfBackupDesignatedRouter, 2884 ospfIfEvents, 2885 ospfIfAuthType, 2886 ospfIfAuthKey, 2887 ospfIfStatus, 2888 ospfIfMulticastForwarding, 2889 ospfIfDemand 2890 } 2891 STATUS current 2892 DESCRIPTION 2893 "These objects are required for OSPF systems." 2894 ::= { ospfGroups 7 } 2896 ospfIfMetricGroup OBJECT-GROUP 2897 OBJECTS { 2898 ospfIfMetricIpAddress, 2899 ospfIfMetricAddressLessIf, 2900 ospfIfMetricTOS, 2901 ospfIfMetricValue, 2902 ospfIfMetricStatus 2903 } 2904 STATUS current 2905 DESCRIPTION 2906 "These objects are required for OSPF systems." 2907 ::= { ospfGroups 8 } 2909 ospfVirtIfGroup OBJECT-GROUP 2910 OBJECTS { 2911 ospfVirtIfAreaId, 2912 ospfVirtIfNeighbor, 2913 ospfVirtIfTransitDelay, 2914 ospfVirtIfRetransInterval, 2915 ospfVirtIfHelloInterval, 2916 ospfVirtIfRtrDeadInterval, 2917 ospfVirtIfState, 2918 ospfVirtIfEvents, 2919 ospfVirtIfAuthType, 2920 ospfVirtIfAuthKey, 2921 ospfVirtIfStatus 2922 } 2923 STATUS current 2924 DESCRIPTION 2925 "These objects are required for OSPF systems." 2926 ::= { ospfGroups 9 } 2928 ospfNbrGroup OBJECT-GROUP 2929 OBJECTS { 2930 ospfNbrIpAddr, 2931 ospfNbrAddressLessIndex, 2932 ospfNbrRtrId, 2933 ospfNbrOptions, 2934 ospfNbrPriority, 2935 ospfNbrState, 2936 ospfNbrEvents, 2937 ospfNbrLsRetransQLen, 2938 ospfNbmaNbrStatus, 2939 ospfNbmaNbrPermanence, 2940 ospfNbrHelloSuppressed 2941 } 2942 STATUS current 2943 DESCRIPTION 2944 "These objects are required for OSPF systems." 2945 ::= { ospfGroups 10 } 2947 ospfVirtNbrGroup OBJECT-GROUP 2948 OBJECTS { 2949 ospfVirtNbrArea, 2950 ospfVirtNbrRtrId, 2951 ospfVirtNbrIpAddr, 2952 ospfVirtNbrOptions, 2953 ospfVirtNbrState, 2954 ospfVirtNbrEvents, 2955 ospfVirtNbrLsRetransQLen 2956 } 2957 STATUS current 2958 DESCRIPTION 2959 "These objects are required for OSPF systems." 2960 ::= { ospfGroups 11 } 2962 ospfExtLsdbGroup OBJECT-GROUP 2963 OBJECTS { 2964 ospfExtLsdbType, 2965 ospfExtLsdbLsid, 2966 ospfExtLsdbRouterId, 2967 ospfExtLsdbSequence, 2968 ospfExtLsdbAge, 2969 ospfExtLsdbChecksum, 2970 ospfExtLsdbAdvertisement 2971 } 2972 STATUS current 2973 DESCRIPTION 2974 "These objects are required for OSPF systems 2975 that display their link state database." 2976 ::= { ospfGroups 12 } 2978 ospfAreaAggregateGroup OBJECT-GROUP 2979 OBJECTS { 2980 ospfAreaAggregateAreaID, 2981 ospfAreaAggregateLsdbType, 2982 ospfAreaAggregateNet, 2983 ospfAreaAggregateMask, 2984 ospfAreaAggregateStatus, 2985 ospfAreaAggregateEffect 2986 } 2987 STATUS current 2988 DESCRIPTION 2989 "These objects are required for OSPF systems." 2990 ::= { ospfGroups 13 } 2992 END 2993 6. OSPF Traps 2995 OSPF is an event driven routing protocol, where an event can 2996 be a change in an OSPF interface's link-level status, the 2997 expiration of an OSPF timer or the reception of an OSPF 2998 protocol packet. Many of the actions that OSPF takes as a 2999 result of these events will result in a change of the routing 3000 topology. As routing topologies become large and complex it 3001 is often difficult to locate the source of a topology change 3002 or unpredicted routing path by polling a large number or 3003 routers. Another approach is to notify a network manager of 3004 potentially critical OSPF events with SNMP traps. 3006 This section defines a set of traps, objects and mechanisms to 3007 enhance the ability to manage IP internetworks which use OSPF 3008 as its IGP. It is an optional but useful extension to the 3009 OSPF MIB. 3011 6.1. Format Of Trap Definitions 3013 Section A.4.0 contains contains the trap definitions using 3015 6.2. Approach 3017 The mechanism for sending traps is straight-forward. When an 3018 exception event occurs, the application notifies the local 3019 agent who sends a trap to the appropriate SNMP management 3020 stations. The message includes the trap type and may include 3021 a list of trap specific variables. A new object is defined in 3022 section 5.2 that will allow a network manager to enable or 3023 disable particular OSPF traps. Section A.4.0 gives the trap 3024 definitions which includes the variable lists. The router ID 3025 of the originator of the trap is included in the variable list 3026 so that the network manager may easily determine the source of 3027 the trap. 3029 To limit the frequency of OSPF traps, the following additional 3030 mechanisms are suggested. 3032 6.3. Ignoring Initial Activity 3034 The majority of critical events occur when OSPF is enabled on 3035 a router, at which time the designated router is elected and 3036 neighbor adjacencies are formed. During this initial period a 3037 potential flood of traps is unnecessary since the events are 3038 expected. To avoid unnecessary traps, a router should not 3039 originate expected OSPF interface related traps until two of 3040 that interface's dead timer intervals have elapsed. The 3041 expected OSPF interface traps are ospfIfStateChange, 3042 ospfVirtIfStateChange, ospfNbrStateChange, 3043 ospfVirtNbrStateChange, ospfTxRetranmit and 3044 ospfVirtIfTxRetransmit. Additionally, ospfMaxAgeLsa and 3045 ospfOriginateLsa traps should not be originated until two dead 3046 timer intervals have elapsed where the dead timer interval 3047 used should be the dead timer with the smallest value. 3049 6.4. Throttling Traps 3051 The mechanism for throttling the traps is similar to the 3052 mechanism explained in RFC 1224 [11] section 5. The basic 3053 idea is that there is a sliding window in seconds and an upper 3054 bound on the number of traps that may be generated within this 3055 window. Unlike RFC 1224, traps are not sent to inform the 3056 network manager that the throttling mechanism has kicked in. 3058 A single window should be used to throttle all OSPF traps 3059 types except for the ospfLsdbOverflow and the 3060 ospfLsdbApproachingOverflow trap which should not be 3061 throttled. For example, if the window time is 3, the upper 3062 bound is 3 and the events that would cause trap types 1,3,5 3063 and 7 occur within a 3 second period, the type 7 trap should 3064 not be generated. 3066 Appropriate values are 7 traps with a window time of 10 3067 seconds. 3069 6.5. One Trap Per OSPF Event 3071 Several of the traps defined in section A.4.0 are generated as 3072 the result of finding an unusual condition while parsing an 3073 OSPF packet or a processing a timer event. There may be more 3074 than one unusual condition detected while handling the event. 3075 For example, a link-state update packet may contain several 3076 retransmitted link-state advertisements (LSAs), or a 3077 retransmitted database description packet may contain several 3078 database description entries. To limit the number of traps 3079 and variables, OSPF should generate at most one trap per OSPF 3080 event. Only the variables associated with the first unusual 3081 condition should be included with the trap. Similarly, if 3082 more than one type of unusual condition is encountered while 3083 parsing the packet, only the first event will generate a trap. 3085 6.6. Polling Event Counters 3087 Many of the tables in the OSPF MIB contain generalized event 3088 counters. By enabling the traps defined in this document a 3089 network manager can obtain more specific information about 3090 these events. A network manager may want to poll these event 3091 counters and enable specific OSPF traps when a particular 3092 counter starts increasing abnormally. 3094 The following table shows the relationship between the event 3095 counters defined in the OSPF MIB and the trap types defined in 3096 section A.4.0 3098 Counter32 Trap Type 3099 ----------------------- ------------------------ 3100 ospfOriginateNewLsas ospfOriginateLsa 3101 ospfIfEvents ospfIfStateChange 3102 ospfConfigError 3103 ospfIfAuthFailure 3104 ospfRxBadPacket 3105 ospfTxRetransmit 3106 ospfVirtIfEvents ospfVirtIfStateChange 3107 ospfVirtIfConfigError 3108 ospfVirtIfAuthFailure 3109 ospfVirtIfRxBadPacket 3110 ospfVirtIfTxRetransmit 3111 ospfNbrEvents ospfNbrStateChange 3112 ospfVirtNbrEvents ospfVirtNbrStateChange 3113 ospfExternLSACount ospfLsdbApproachingOverflow 3114 ospfExternLSACount ospfLsdbOverflow 3116 7. OSPF Trap Definitions 3117 OSPF-TRAP-MIB DEFINITIONS ::= BEGIN 3119 IMPORTS 3120 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress 3121 FROM SNMPv2-SMI 3122 MODULE-COMPLIANCE, OBJECT-GROUP 3123 FROM SNMPv2-CONF 3124 ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState, 3125 ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState, 3126 ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId, 3127 ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, ospfVirtNbrState, 3128 ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, ospfLsdbAreaId, 3129 ospfExtLsdbLimit, ospf 3130 FROM OSPF-MIB; 3132 ospfTrap MODULE-IDENTITY 3133 LAST-UPDATED "9402091913Z" -- Mon Jan 9 14:20:53 PST 1995 3134 ORGANIZATION "IETF OSPF Working Group" 3135 CONTACT-INFO 3136 " Fred Baker 3137 Postal: Advanced Computer Communications 3138 315 Bollay Drive 3139 Santa Barbara, California 93117 3140 Tel: +1 085 685 4455 3141 E-Mail: fbaker@acc.com 3143 Rob Coltun 3144 Postal: RainbowBridge Communications 3145 Tel: (301) 340-9416 3146 E-Mail: rcoltun@rainbow-bridge.com" 3147 DESCRIPTION 3148 "The MIB module to describe traps for the OSPF 3149 Version 2 Protocol." 3150 ::= { ospf 16 } 3152 -- Trap Support Objects 3154 -- The following are support objects for the OSPF traps. 3156 ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 } 3157 ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 } 3158 ospfSetTrap OBJECT-TYPE 3159 SYNTAX OCTET STRING (SIZE(4)) 3160 MAX-ACCESS read-write 3161 STATUS current 3162 DESCRIPTION 3163 "A four-octet string serving as a bit map for 3164 the trap events defined by the OSPF traps. This 3165 object is used to enable and disable specific 3166 OSPF traps where a 1 in the bit field 3167 represents enabled. The right-most bit (least 3168 significant) represents trap 0." 3169 ::= { ospfTrapControl 1 } 3171 ospfConfigErrorType OBJECT-TYPE 3172 SYNTAX INTEGER { 3173 badVersion (1), 3174 areaMismatch (2), 3175 unknownNbmaNbr (3), -- Router is Dr eligible 3176 unknownVirtualNbr (4), 3177 authTypeMismatch(5), 3178 authFailure (6), 3179 netMaskMismatch (7), 3180 helloIntervalMismatch (8), 3181 deadIntervalMismatch (9), 3182 optionMismatch (10) } 3183 MAX-ACCESS read-only 3184 STATUS current 3185 DESCRIPTION 3186 "Potential types of configuration conflicts. 3187 Used by the ospfConfigError and ospfConfigVir- 3188 tError traps." 3189 ::= { ospfTrapControl 2 } 3190 ospfPacketType OBJECT-TYPE 3191 SYNTAX INTEGER { 3192 hello (1), 3193 dbDescript (2), 3194 lsReq (3), 3195 lsUpdate (4), 3196 lsAck (5) } 3197 MAX-ACCESS read-only 3198 STATUS current 3199 DESCRIPTION 3200 "OSPF packet types." 3201 ::= { ospfTrapControl 3 } 3203 ospfPacketSrc OBJECT-TYPE 3204 SYNTAX IpAddress 3205 MAX-ACCESS read-only 3206 STATUS current 3207 DESCRIPTION 3208 "The IP address of an inbound packet that can- 3209 not be identified by a neighbor instance." 3210 ::= { ospfTrapControl 4 } 3212 -- Traps 3214 ospfIfStateChange NOTIFICATION-TYPE 3215 OBJECTS { 3216 ospfRouterId, -- The originator of the trap 3217 ospfIfIpAddress, 3218 ospfAddressLessIf, 3219 ospfIfState -- The new state 3220 } 3221 STATUS current 3222 DESCRIPTION 3223 "An ospfIfStateChange trap signifies that there 3224 has been a change in the state of a non-virtual 3225 OSPF interface. This trap should be generated 3226 when the interface state regresses (e.g., goes 3227 from Dr to Down) or progresses to a terminal 3228 state (i.e., Point-to-Point, DR Other, Dr, or 3229 Backup)." 3230 ::= { ospfTraps 16 } 3232 ospfVirtIfStateChange NOTIFICATION-TYPE 3233 OBJECTS { 3234 ospfRouterId, -- The originator of the trap 3235 ospfVirtIfAreaId, 3236 ospfVirtIfNeighbor, 3237 ospfVirtIfState -- The new state 3238 } 3239 STATUS current 3240 DESCRIPTION 3241 "An ospfIfStateChange trap signifies that there 3242 has been a change in the state of an OSPF vir- 3243 tual interface. 3245 This trap should be generated when the inter- 3246 face state regresses (e.g., goes from Point- 3247 to-Point to Down) or progresses to a terminal 3248 state (i.e., Point-to-Point)." 3249 ::= { ospfTraps 1 } 3250 ospfNbrStateChange NOTIFICATION-TYPE 3251 OBJECTS { 3252 ospfRouterId, -- The originator of the trap 3253 ospfNbrIpAddr, 3254 ospfNbrAddressLessIndex, 3255 ospfNbrRtrId, 3256 ospfNbrState -- The new state 3257 } 3258 STATUS current 3259 DESCRIPTION 3260 "An ospfNbrStateChange trap signifies that 3261 there has been a change in the state of a non- 3262 virtual OSPF neighbor. This trap should be 3263 generated when the neighbor state regresses 3264 (e.g., goes from Attempt or Full to 1-Way or 3265 Down) or progresses to a terminal state (e.g., 3266 2-Way or Full). When an neighbor transitions 3267 from or to Full on non-broadcast multi-access 3268 and broadcast networks, the trap should be gen- 3269 erated by the designated router. A designated 3270 router transitioning to Down will be noted by 3271 ospfIfStateChange." 3272 ::= { ospfTraps 2 } 3274 ospfVirtNbrStateChange NOTIFICATION-TYPE 3275 OBJECTS { 3276 ospfRouterId, -- The originator of the trap 3277 ospfVirtNbrArea, 3278 ospfVirtNbrRtrId, 3279 ospfVirtNbrState -- The new state 3280 } 3281 STATUS current 3282 DESCRIPTION 3283 "An ospfIfStateChange trap signifies that there 3284 has been a change in the state of an OSPF vir- 3285 tual neighbor. This trap should be generated 3286 when the neighbor state regresses (e.g., goes 3287 from Attempt or Full to 1-Way or Down) or 3288 progresses to a terminal state (e.g., Full)." 3289 ::= { ospfTraps 3 } 3290 ospfIfConfigError NOTIFICATION-TYPE 3291 OBJECTS { 3292 ospfRouterId, -- The originator of the trap 3293 ospfIfIpAddress, 3294 ospfAddressLessIf, 3295 ospfPacketSrc, -- The source IP address 3296 ospfConfigErrorType, -- Type of error 3297 ospfPacketType 3298 } 3299 STATUS current 3300 DESCRIPTION 3301 "An ospfIfConfigError trap signifies that a 3302 packet has been received on a non-virtual in- 3303 terface from a router whose configuration 3304 parameters conflict with this router's confi- 3305 guration parameters. Note that the event op- 3306 tionMismatch should cause a trap only if it 3307 prevents an adjacency from forming." 3308 ::= { ospfTraps 4 } 3310 ospfVirtIfConfigError NOTIFICATION-TYPE 3311 OBJECTS { 3312 ospfRouterId, -- The originator of the trap 3313 ospfVirtIfAreaId, 3314 ospfVirtIfNeighbor, 3315 ospfConfigErrorType, -- Type of error 3316 ospfPacketType 3317 } 3318 STATUS current 3319 DESCRIPTION 3320 "An ospfConfigError trap signifies that a pack- 3321 et has been received on a virtual interface 3322 from a router whose configuration parameters 3323 conflict with this router's configuration 3324 parameters. Note that the event optionMismatch 3325 should cause a trap only if it prevents an ad- 3326 jacency from forming." 3327 ::= { ospfTraps 5 } 3328 ospfIfAuthFailure NOTIFICATION-TYPE 3329 OBJECTS { 3330 ospfRouterId, -- The originator of the trap 3331 ospfIfIpAddress, 3332 ospfAddressLessIf, 3333 ospfPacketSrc, -- The source IP address 3334 ospfConfigErrorType, -- authTypeMismatch or authFailure 3335 ospfPacketType 3336 } 3337 STATUS current 3338 DESCRIPTION 3339 "An ospfIfAuthFailure trap signifies that a 3340 packet has been received on a non-virtual in- 3341 terface from a router whose authentication key 3342 or authentication type conflicts with this 3343 router's authentication key or authentication 3344 type." 3345 ::= { ospfTraps 6 } 3347 ospfVirtIfAuthFailure NOTIFICATION-TYPE 3348 OBJECTS { 3349 ospfRouterId, -- The originator of the trap 3350 ospfVirtIfAreaId, 3351 ospfVirtIfNeighbor, 3352 ospfConfigErrorType, -- authTypeMismatch or authFailure 3353 ospfPacketType 3354 } 3355 STATUS current 3356 DESCRIPTION 3357 "An ospfVirtIfAuthFailure trap signifies that a 3358 packet has been received on a virtual interface 3359 from a router whose authentication key or au- 3360 thentication type conflicts with this router's 3361 authentication key or authentication type." 3362 ::= { ospfTraps 7 } 3363 ospfIfRxBadPacket NOTIFICATION-TYPE 3364 OBJECTS { 3365 ospfRouterId, -- The originator of the trap 3366 ospfIfIpAddress, 3367 ospfAddressLessIf, 3368 ospfPacketSrc, -- The source IP address 3369 ospfPacketType 3370 } 3371 STATUS current 3372 DESCRIPTION 3373 "An ospfIfRxBadPacket trap signifies that an 3374 OSPF packet has been received on a non-virtual 3375 interface that cannot be parsed." 3376 ::= { ospfTraps 8 } 3378 ospfVirtIfRxBadPacket NOTIFICATION-TYPE 3379 OBJECTS { 3380 ospfRouterId, -- The originator of the trap 3381 ospfVirtIfAreaId, 3382 ospfVirtIfNeighbor, 3383 ospfPacketType 3384 } 3385 STATUS current 3386 DESCRIPTION 3387 "An ospfRxBadPacket trap signifies that an OSPF 3388 packet has been received on a virtual interface 3389 that cannot be parsed." 3390 ::= { ospfTraps 9 } 3391 ospfTxRetransmit NOTIFICATION-TYPE 3392 OBJECTS { 3393 ospfRouterId, -- The originator of the trap 3394 ospfIfIpAddress, 3395 ospfAddressLessIf, 3396 ospfNbrRtrId, -- Destination 3397 ospfPacketType, 3398 ospfLsdbType, 3399 ospfLsdbLsid, 3400 ospfLsdbRouterId 3401 } 3402 STATUS current 3403 DESCRIPTION 3404 "An ospfTxRetransmit trap signifies than an 3405 OSPF packet has been retransmitted on a non- 3406 virtual interface. All packets that may be re- 3407 transmitted are associated with an LSDB entry. 3408 The LS type, LS ID, and Router ID are used to 3409 identify the LSDB entry." 3410 ::= { ospfTraps 10 } 3412 ospfVirtIfTxRetransmit NOTIFICATION-TYPE 3413 OBJECTS { 3414 ospfRouterId, -- The originator of the trap 3415 ospfVirtIfAreaId, 3416 ospfVirtIfNeighbor, 3417 ospfPacketType, 3418 ospfLsdbType, 3419 ospfLsdbLsid, 3420 ospfLsdbRouterId 3421 } 3422 STATUS current 3423 DESCRIPTION 3424 "An ospfTxRetransmit trap signifies than an 3425 OSPF packet has been retransmitted on a virtual 3426 interface. All packets that may be retransmit- 3427 ted are associated with an LSDB entry. The LS 3428 type, LS ID, and Router ID are used to identify 3429 the LSDB entry." 3430 ::= { ospfTraps 11 } 3431 ospfOriginateLsa NOTIFICATION-TYPE 3432 OBJECTS { 3433 ospfRouterId, -- The originator of the trap 3434 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 3435 ospfLsdbType, 3436 ospfLsdbLsid, 3437 ospfLsdbRouterId 3438 } 3439 STATUS current 3440 DESCRIPTION 3441 "An ospfOriginateLsa trap signifies that a new 3442 LSA has been originated by this router. This 3443 trap should not be invoked for simple refreshes 3444 of LSAs (which happesn every 30 minutes), but 3445 instead will only be invoked when an LSA is 3446 (re)originated due to a topology change. Addi- 3447 tionally, this trap does not include LSAs that 3448 are being flushed because they have reached 3449 MaxAge." 3450 ::= { ospfTraps 12 } 3452 ospfMaxAgeLsa NOTIFICATION-TYPE 3453 OBJECTS { 3454 ospfRouterId, -- The originator of the trap 3455 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 3456 ospfLsdbType, 3457 ospfLsdbLsid, 3458 ospfLsdbRouterId 3459 } 3460 STATUS current 3461 DESCRIPTION 3462 "An ospfMaxAgeLsa trap signifies that one of 3463 the LSA in the router's link-state database has 3464 aged to MaxAge." 3465 ::= { ospfTraps 13 } 3466 ospfLsdbOverflow NOTIFICATION-TYPE 3467 OBJECTS { 3468 ospfRouterId, -- The originator of the trap 3469 ospfExtLsdbLimit 3470 } 3471 STATUS current 3472 DESCRIPTION 3473 "An ospfLsdbOverflow trap signifies that the 3474 number of LSAs in the router's link-state data- 3475 base has exceeded ospfExtLsdbLimit." 3476 ::= { ospfTraps 14 } 3478 ospfLsdbApproachingOverflow NOTIFICATION-TYPE 3479 OBJECTS { 3480 ospfRouterId, -- The originator of the trap 3481 ospfExtLsdbLimit 3482 } 3483 STATUS current 3484 DESCRIPTION 3485 "An ospfLsdbApproachingOverflow trap signifies 3486 that the number of LSAs in the router's link- 3487 state database has exceeded ninety percent of 3488 ospfExtLsdbLimit." 3489 ::= { ospfTraps 15 } 3491 -- conformance information 3493 ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 } 3495 ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 } 3496 ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 } 3498 -- compliance statements 3500 ospfTrapCompliance MODULE-COMPLIANCE 3501 STATUS current 3502 DESCRIPTION 3503 "The compliance statement " 3504 MODULE -- this module 3505 MANDATORY-GROUPS { ospfTrapControlGroup } 3507 GROUP ospfTrapControlGroup 3508 DESCRIPTION 3509 "This group is optional but recommended for all 3510 OSPF systems" 3511 ::= { ospfTrapCompliances 1 } 3513 -- units of conformance 3515 ospfTrapControlGroup OBJECT-GROUP 3516 OBJECTS { 3517 ospfSetTrap, 3518 ospfConfigErrorType, 3519 ospfPacketType, 3520 ospfPacketSrc 3521 } 3522 STATUS current 3523 DESCRIPTION 3524 "These objects are required to control traps 3525 from OSPF systems." 3526 ::= { ospfTrapGroups 1 } 3528 END 3529 8. Acknowledgements 3531 This document was produced by the OSPF Working Group. 3533 9. References 3535 [1] V. Cerf, IAB Recommendations for the Development of 3536 Internet Network Management Standards. Internet Working 3537 Group Request for Comments 1052. Network Information 3538 Center, SRI International, Menlo Park, California, 3539 (April, 1988). 3541 [2] V. Cerf, Report of the Second Ad Hoc Network Management 3542 Review Group, Internet Working Group Request for Comments 3543 1109. Network Information Center, SRI International, 3544 Menlo Park, California, (August, 1989). 3546 [3] M.T. Rose and K. McCloghrie, Structure and Identification 3547 of Management Information for TCP/IP-based internets, 3548 Internet Working Group Request for Comments 1155. 3549 Network Information Center, SRI International, Menlo 3550 Park, California, (May, 1990). 3552 [4] K. McCloghrie and M.T. Rose, Management Information Base 3553 for Network Management of TCP/IP-based internets, 3554 Internet Working Group Request for Comments 1156. 3555 Network Information Center, SRI International, Menlo 3556 Park, California, (May, 1990). 3558 [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 3559 Simple Network Management Protocol, Internet Working 3560 Group Request for Comments 1157. Network Information 3561 Center, SRI International, Menlo Park, California, (May, 3562 1990). 3564 [6] M.T. Rose (editor), Management Information Base for 3565 Network Management of TCP/IP-based internets, Internet 3566 Working Group Request for Comments 1213. Network 3567 Information Center, SRI International, Menlo Park, 3568 California, (May, 1990). 3570 [7] Information processing systems - Open Systems 3571 Interconnection - Specification of Abstract Syntax 3572 Notation One (ASN.1), International Organization for 3573 Standardization. International Standard 8824, (December, 3574 1987). 3576 [8] Information processing systems - Open Systems 3577 Interconnection - Specification of Basic Encoding Rules 3578 for Abstract Notation One (ASN.1), International 3579 Organization for Standardization. International Standard 3580 8825, (December, 1987). 3582 [9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB 3583 Definitions, Internet Draft, Internet Engineering Task 3584 Force, (September, 1990). 3586 [10] M.T. Rose (editor), A Convention for Defining Traps for 3587 use with the SNMP, Internet Working Group Request for 3588 Comments 1215. Network Information Center, SRI 3589 International, Menlo Park, California, (March, 1991). 3591 [11] L. Steinberg, Techniques for Managing Asynchronously 3592 Generated Alerts. Internet Working Group Request for 3593 Comments 1224. Network Information Center, SRI 3594 International, Menlo Park, California, (May, 1991). 3596 [12] J. Moy, Multicast Extensions to OSPF, Internet Draft, 3597 Proteon, Inc., (September, 1993). 3599 Table of Contents 3601 1 Status of this Memo ................................... 1 3602 2 Abstract .............................................. 2 3603 3 The SNMPv2 Network Management Framework ............... 3 3604 3.1 Object Definitions .................................. 3 3605 4 Overview .............................................. 3 3606 4.1 Changes from RFC 1253 ............................... 3 3607 4.2 Textual Conventions ................................. 7 3608 4.3 Structure of MIB .................................... 7 3609 4.3.1 General Variables ................................. 7 3610 4.3.2 Area Data Structure and Area Stub Metric Table .... 8 3611 4.3.3 Link State Database and External Link State Da- 3612 tabase ............................................. 8 3613 4.3.4 Address Table and Host Tables ..................... 8 3614 4.3.5 Interface and Interface Metric Tables ............. 8 3615 4.3.6 Virtual Interface Table ........................... 8 3616 4.3.7 Neighbor and Virtual Neighbor Tables .............. 8 3617 4.4 Conceptual Row Creation ............................. 8 3618 4.5 Default Configuration ............................... 9 3619 5 Definitions ........................................... 12 3620 5.1 OSPF General Variables .............................. 15 3621 5.2 OSPF Area Table ..................................... 22 3622 5.3 OSPF Area Default Metrics ........................... 27 3623 5.4 OSPF Link State Database ............................ 30 3624 5.5 OSPF Address Range Table ............................ 35 3625 5.6 OSPF Host Table ..................................... 38 3626 5.7 OSPF Interface Table ................................ 41 3627 5.8 OSPF Interface Metrics .............................. 51 3628 5.9 OSPF Virtual Interface Table ........................ 55 3629 5.10 OSPF Neighbor Table ................................ 61 3630 5.11 OSPF Virtual Neighbor Table ........................ 67 3631 5.12 OSPF External Link State Database .................. 71 3632 5.13 OSPF Route Table Use ............................... 76 3633 5.14 OSPF Area Aggregate Table .......................... 77 3634 6 OSPF Traps ............................................ 89 3635 6.1 Format Of Trap Definitions .......................... 89 3636 6.2 Approach ............................................ 89 3637 6.3 Ignoring Initial Activity ........................... 89 3638 6.4 Throttling Traps .................................... 90 3639 6.5 One Trap Per OSPF Event ............................. 90 3640 6.6 Polling Event Counters .............................. 91 3641 7 OSPF Trap Definitions ................................. 91 3642 7.1 Trap Support Objects ................................ 91 3643 7.2 Traps ............................................... 94 3644 8 Acknowledgements ...................................... 104 3645 9 References ............................................ 105