idnits 2.17.1 draft-ietf-ospf-mib-update-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 54 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. ** 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 660: '...database. OspfExtLsdbLimit MUST be set...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 126 has weird spacing: '...objects and ...' == Line 127 has weird spacing: '... for the p...' == Line 138 has weird spacing: '...andards track...' == Line 544 has weird spacing: '...isables it on...' == Line 602 has weird spacing: '... the exter...' == (49 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 (November 2000) is 8563 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: '12' is mentioned on line 142, but not defined -- Looks like a reference, but probably isn't: 'RFC-1704' on line 2157 -- Looks like a reference, but probably isn't: 'RFC 2178' on line 4434 -- Looks like a reference, but probably isn't: 'RFC2574' on line 4731 -- Looks like a reference, but probably isn't: 'RFC2575' on line 4732 == Unused Reference: '21' is defined on line 4409, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 4392, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 4396, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 4403, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 4406, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 4413, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 4418, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 4426, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2460 (ref. '17') (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 1850 (ref. '18') (Obsoleted by RFC 4750) ** Downref: Normative reference to an Unknown state RFC: RFC 1052 (ref. '19') ** Downref: Normative reference to an Unknown state RFC: RFC 1109 (ref. '20') -- Possible downref: Non-RFC (?) normative reference: ref. '22' -- Possible downref: Non-RFC (?) normative reference: ref. '23' ** Downref: Normative reference to an Experimental RFC: RFC 1224 (ref. '24') ** Downref: Normative reference to an Historic RFC: RFC 1584 (ref. '25') Summary: 23 errors (**), 0 flaws (~~), 19 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group S. Giacalone 2 INTERNET-DRAFT Predictive Systems 3 Expiration Date: May 2001 D. Joyal 4 Filename:draft-ietf-ospf-mib-update-05.txt Quantum Bridge 5 Communications 6 Rob Coltun 7 Redback Networks 8 Fred Baker 9 Cisco Systems 10 November 2000 12 OSPF Version 2 Management Information Base 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its areas, 17 and its working groups. Note that other groups may also distribute 18 working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Abstract 33 This memo defines a portion of the Management Information Base (MIB) 34 for use with network management protocols in TCP/IP-based internets. 35 In particular, it defines objects for managing the Open Shortest Path 36 First Routing Protocol. 38 This memo is intended to update and possibly obsolete RFC 1850, 39 however, it is designed to be backwards compatible. The functional 40 differences between this memo and RFC 1850 are explained in Appendix 41 B. 43 Please send comments to ospf@discuss.microsoft.com. 45 Copyright Notice 47 Copyright (C) The Internet Society (1999). All Rights Reserved. 49 Table of Contents 51 The SNMPv2 Network Management Framework 52 Object Definitions 53 1 Overview ..............................................3 54 1.1 The SNMPv2 Network Management Framework .............3 55 1.2 The SMI, and Object definitions .....................3 56 1.3 Object Identification ...............................4 57 1.4 Textual Conventions .................................4 58 1.5 Conceptual Row Creation .............................4 59 1.6 Default Configuration ...............................5 60 2 Structure of this MIB .................................6 61 2.1 The Purposes of the sections in this MIB ............6 62 2.1.1 General Variables .................................6 63 2.1.2 Area Data Structure and Area Stub Metric Table ....7 64 2.1.3 Link State Database and External Link State 65 Database ..........................................7 66 2.1.4 Address Table and Host Tables .....................7 67 2.1.5 Interface and Interface Metric Tables .............7 68 2.1.6 Virtual Interface Table ...........................7 69 2.1.7 Neighbor and Virtual Neighbor Tables ..............7 70 2.1.8 Local Link State Database Table and Virtual 71 Local Link State Database Table ...................7 72 3 OSPF-MIB Definitions ..................................7 73 3.1 OSPF General Variables ..............................11 74 3.2 OSPF Area Table .....................................16 75 3.3 OSPF Area Default Metrics ...........................20 76 3.4 OSPF Link State Database ............................22 77 3.5 OSPF Address Range Table ............................26 78 3.6 OSPF Host Table .....................................28 79 3.7 OSPF Interface Table ................................30 80 3.8 OSPF Interface Metric Table .........................37 81 3.9 OSPF Virtual Interface Table ........................40 82 3.10 OSPF Neighbor Table ................................44 83 3.11 OSPF Virtual Neighbor Table ........................48 84 3.12 OSPF External Link State Database ..................51 85 3.13 OSPF Route Table Use ...............................54 86 3.14 OSPF Area Aggregate Table ..........................55 87 3.15 OSPF Local LSDB Table...............................58 88 3.16 OSPF Virtual Local LSDB Table.......................61 89 3.17 Conformance Information ............................65 90 4 OSPF Trap overview ....................................74 91 4.1 Introduction.........................................74 92 4.2 Approach.............................................74 93 4.3 Ignoring Initial Activity ...........................74 94 4.4 Throttling Traps ....................................75 95 4.5 One Trap Per OSPF Event .............................75 96 4.6 Polling Event Counters ..............................75 97 5 OSPF Trap Definitions .................................76 98 5.1 Trap Support Objects ................................77 99 5.2 Traps ...............................................78 100 5.3 Conformance Information .............................84 101 6 Acknowledgements ......................................85 102 7 References ............................................86 103 A TOS Support ...........................................88 104 B Changes from RFC 1850 .................................88 105 B.1 RFC 1583 Compatibility ..............................88 106 B.2 OSPF Traffic Engineering Support ....................88 107 B.3 OSPF NSSA Enhancement Support .......................88 108 B.4 Opaque LSA Support ..................................89 109 B.5 OSPF Compliances.....................................90 110 B.6 OSPF Authentication and Security.....................91 111 B.7 OSPF Trap MIB .......................................92 112 B.8 Miscellaneous .......................................92 113 C Security Considerations ...............................93 114 D Authors' Addresses ....................................94 115 E Full Copyright Statement ..............................95 117 1 Overview 119 1.1 The SNMPv2 Network Management Framework 121 This document describes aspects of the SNMPv2 Network Management 122 Framework, which consists of a number of components. They are: 124 - An overall architecture, described in RFC 2571 [1]. 126 - Mechanisms for describing and naming objects and events 127 for the purpose of management. The first version of this 128 Structure of Management Information (SMI) is called SMIv1 129 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 130 [3] and RFC 1215 [4]. The second version, called SMIv2, 131 is described in STD 58, RFC 2578 [5], RFC 2579 [6] and 132 RFC 2580 [7]. 134 - Message protocols for transferring management 135 information. The first version of the SNMP message 136 protocol is called SNMPv1 and described in STD 15, RFC 137 1157 [8]. A second version of the SNMP message protocol, 138 which is not an Internet standards track protocol, is 139 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 140 [10]. The third version of the message protocol is called 141 SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 142 RFC 2574 [12]. 144 - Protocol operations for accessing management information. 145 The first set of protocol operations and associated PDU 146 formats is described in STD 15, RFC 1157 [8]. A second 147 set of protocol operations and associated PDU formats is 148 described in RFC 1905 [13]. 150 - A set of fundamental applications described in RFC 2573 151 [14] and the view-based access control mechanism 152 described in RFC 2575 [15]. 154 1.2 The SMI, and Object Definitions 156 Managed objects are accessed via a virtual information store, termed 157 the Management Information Base or MIB. Objects in the MIB are 158 defined using the subset of Abstract Syntax Notation One (ASN.1) 159 defined in the SMI. 161 This memo specifies a MIB module that is compliant to the 162 SMIv2. A MIB conforming to the SMIv1 can be produced through 163 the appropriate translations. 165 1.3 Object Identification 167 Objects in the SMI are defined by types, and are named by an 168 OBJECT IDENTIFIER, which is an administratively assigned name. 169 The object type together with an object instance serves to 170 uniquely identify a specific instantiation of the object. For 171 human convenience, we often use a textual string, termed 172 the descriptor, to refer to the object type. 174 1.4 Textual Conventions 176 Several data types in this MIB document are termed textual 177 conventions. Textual conventions enhance the readability 178 of the specification and can ease comparison with other 179 specifications if appropriate. It should be noted that 180 textual conventions have no effect on either the syntax nor 181 the semantics of any managed objects. Objects defined in 182 terms of one of these methods are always encoded by means 183 of the rules that define the primitive type. Textual 184 conventions are used for the convenience of readers and 185 writers in pursuit of the goal of clear, concise, and 186 unambiguous MIB documents. 188 1.5 Conceptual Row Creation 190 For the benefit of row-creation in "conceptual" tables, 191 DEFVAL (Default Value) clauses are included in the definitions in 192 section 3, suggesting values which an agent should use for instances 193 of variables which need to be created due to a Set-Request, but which 194 are not specified in the Set-Request. DEFVAL clauses have not been 195 specified for some objects which are read-only, implying that they 196 are zeroed upon row creation. These objects are of the SYNTAX 197 Counter32 or Gauge32. 199 For those objects not having a DEFVAL clause, both management 200 stations and agents should heed the Robustness Principle of the 201 Internet (see RFC-791): 203 "be liberal in what you accept, conservative in what you send" 204 Therefor, management stations should include as many of these 205 columnar objects as possible (e.g., all read-write objects) in a Set- 206 Request when creating a conceptual row. Agents should accept a Set- 207 Request with as few of these columnar objects as they need (e.g., the 208 minimum contents of a "row-creating" SET consists of those objects 209 for which, as they cannot be intuited, no default is specified.). 211 1.6 Default Configuration 213 OSPF is a powerful routing protocol, equipped with features to handle 214 virtually any configuration requirement that might reasonably be 215 found within an Autonomous System. With this power comes a fair 216 degree of complexity, which the sheer number of objects in the MIB 217 will attest to. Care has therefore been taken, in constructing this 218 MIB, to define default values for virtually every object, to minimize 219 the amount of parameterization required in the typical case. That 220 default configuration is as follows: 222 Given the following assumptions: 224 - IP has already been configured 226 - The ifTable has already been configured 228 - ifSpeed is estimated by the interface drivers 230 - The OSPF Process automatically discovers all IP 231 Interfaces and creates corresponding OSPF Interfaces 233 - The OSPF Process automatically creates the Areas required 234 for the Interfaces 236 The simplest configuration of an OSPF process requires that: 238 - The OSPF Process be Enabled. 240 This can be accomplished with a single SET: 242 ospfAdminStat := enabled. 244 The configured system will have the following attributes: 246 - The RouterID will be one of the IP addresses of the 247 device 249 - The device will be neither an Area Border Router nor an 250 Autonomous System Border Router. 252 - Every IP Interface, with or without an address, will be 253 an OSPF Interface. 255 - The AreaID of each interface will be 0.0.0.0, the 256 Backbone. 258 - Authentication will be disabled 260 - All Broadcast and Point to Point interfaces will be 261 operational. NBMA Interfaces require the configuration 262 of at least one neighbor. 264 - Timers on all direct interfaces will be: 266 Hello Interval: 10 seconds 267 Dead Timeout: 40 Seconds 268 Retransmission: 5 Seconds 269 Transit Delay: 1 Second 270 Poll Interval: 120 Seconds 272 - No direct links to hosts will be configured. 274 - No addresses will be summarized 276 - Metrics, being a measure of bit duration, are unambiguous 277 and intelligent. 279 - No Virtual Links will be configured. 281 2 Structure of this MIB 283 This MIB is composed of the following sections: 285 General Variables 286 Area Data Structure 287 Area Stub Metric Table 288 Link State Database 289 Address Range Table 290 Host Table 291 Interface Table 292 Interface Metric Table 293 Virtual Interface Table 294 Neighbor Table 295 Virtual Neighbor Table 296 External Link State Database 297 Aggregate Range Table 298 Local Link State Database 300 There exists a separate MIB for notifications ("traps"), which is 301 entirely optional. 303 2.1 The Purposes of the sections in this MIB 304 2.1.1 General Variables 306 The General Variables describe (as it may seem from the name) 307 variables which are global to the OSPF Process. 309 2.1.2 Area Data Structure and Area Stub Metric Table 311 The Area Data Structure describes all of the OSPF Areas that the 312 router participates in. The Area Table includes data for NSSA 313 translation. 315 The Area Stub Metric Table describes the metrics advertised into 316 a stub area by the default router(s). 318 2.1.3 Link State Database and External Link State Database 320 The Link State Database is provided primarily to provide detailed 321 information for network debugging. 323 2.1.4 Address Table and Host Tables 325 The Address Range Table and Host Table are provided to view 326 configured Network Summary and Host Route information. 328 2.1.5 Interface and Interface Metric Tables 330 The Table and the Interface Metric Table together describe 331 the various IP interfaces to OSPF. The metrics are placed in 332 separate tables in order to simplify dealing with multiple types of 333 service. The Interface table includes Link-Local (Opaque Type-9) LSA 334 statistics. 336 2.1.6 Virtual Interface Table 338 The Virtual Interface Table describes virtual links to the 339 OSPF Process, similarly to the (non-Virtual)Interface Tables. This 340 table includes Link-Local (Opaque Type-9) LSA statistics. 342 2.1.7 Neighbor and Virtual Neighbor Tables 344 The Neighbor Table and the Virtual Neighbor Table describe the 345 neighbors to the OSPF Process. 347 2.1.8 Local Link State Database Table and Virtual 348 Local Link State Database Table 350 The Local Link State Database Table and Virtual Local Link State 351 Database Table are identical to the OSPF LSDB Table in 352 format, but contain only Link-Local (Opaque Type-9) Link State 353 Advertisements for non-virtual and virtual links. 355 OSPF-MIB DEFINITIONS ::= BEGIN 357 IMPORTS 358 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32, 359 Integer32, IpAddress, mib-2 360 FROM SNMPv2-SMI 361 TEXTUAL-CONVENTION, TruthValue, RowStatus 362 FROM SNMPv2-TC 363 MODULE-COMPLIANCE, OBJECT-GROUP 364 FROM SNMPv2-CONF 365 InterfaceIndexOrZero 366 FROM IF-MIB; 368 ospf MODULE-IDENTITY 369 LAST-UPDATED "200011201015Z" -- Mon Nov 20 10:15:00 GMT 2000 370 ORGANIZATION "IETF OSPF Working Group" 371 CONTACT-INFO 372 " Spencer Giacalone 373 Postal: Predictive Systems 374 25a Vreeland Road 375 Florham Park, NJ 07932 376 Tel: +1 (973) 301-5695 377 E-Mail: spencer.giacalone@predictive.com 379 Dan Joyal 380 Postal: Quantum Bridge Communications 381 1 High Street 382 North Andover, MA 01845 383 Tel: +1 (978) 688-9100 384 E-Mail: djoyal@quantumbridge.com" 385 DESCRIPTION 386 "The MIB module to describe the OSPF Version 2 387 Protocol. Note that some objects in this MIB 388 module may pose a significant security risk. 389 Refer to the Security Considerations section 390 in the document defining this MIB module for more 391 information" 392 REVISION "200011201015Z" -- Mon Nov 20 10:15:00 GMT 2000 393 DESCRIPTION 394 "Updated for latest changes to OSPF Version 2" 395 REVISION "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995 396 DESCRIPTION 397 "The initial SMIv2 revision of this MIB module, published in 398 RFC1850." 399 ::= { mib-2 14 } 401 -- Note the Area ID, in OSPF, has the same format as an IP Address, 402 -- but has the function of defining a summarization point for 403 -- Link State Advertisements 404 AreaID ::= TEXTUAL-CONVENTION 405 STATUS current 406 DESCRIPTION 407 "An OSPF Area Identifier." 408 SYNTAX IpAddress 410 -- Note: The Router ID, in OSPF, has the same format as an IP 411 -- Address, but identifies the router independent of its IP Address. 413 RouterID ::= TEXTUAL-CONVENTION 414 STATUS current 415 DESCRIPTION 416 "A OSPF Router Identifier." 417 SYNTAX IpAddress 419 -- Note the OSPF Metric is defined as an unsigned value in the range 421 Metric ::= TEXTUAL-CONVENTION 422 STATUS current 423 DESCRIPTION 424 "The OSPF Internal Metric." 425 SYNTAX Integer32 (0..'FFFF'h) 427 BigMetric ::= TEXTUAL-CONVENTION 428 STATUS current 429 DESCRIPTION 430 "The OSPF External Metric." 431 SYNTAX Integer32 (0..'FFFFFF'h) 433 -- Status Values 435 Status ::= TEXTUAL-CONVENTION 436 STATUS current 437 DESCRIPTION 438 "An indication of the operability of an OSPF 439 function or feature. For example, The status 440 of an interface: 'enabled' indicates that 441 it is willing to communicate with other OSPF Routers, 442 while 'disabled' indicates that it is not." 443 SYNTAX INTEGER { enabled (1), disabled (2) } 445 -- Note that the following Time Durations are measured in seconds 447 PositiveInteger ::= TEXTUAL-CONVENTION 448 STATUS current 449 DESCRIPTION 450 "A positive integer. Values in excess are precluded as 451 unnecessary and prone to interoperability issues." 452 SYNTAX Integer32 (0..'7FFFFFFF'h) 454 HelloRange ::= TEXTUAL-CONVENTION 455 STATUS current 456 DESCRIPTION 457 "The range of intervals on which hello messages are 458 exchanged." 459 SYNTAX Integer32 (1..'FFFF'h) 461 UpToMaxAge ::= TEXTUAL-CONVENTION 462 STATUS current 463 DESCRIPTION 464 "The values that one might find or configure for 465 variables bounded by the maximum age of an LSA." 466 SYNTAX Integer32 (0..3600) 468 -- The range of ifIndex 470 InterfaceIndex ::= TEXTUAL-CONVENTION 471 STATUS obsolete 472 DESCRIPTION 473 "The range of ifIndex. This statement 474 no longer used and is included for backwards- 475 compatibility " 476 SYNTAX Integer32 478 -- Potential Priorities for the Designated Router Election 480 DesignatedRouterPriority ::= TEXTUAL-CONVENTION 481 STATUS current 482 DESCRIPTION 483 "The values defined for the priority of a system for 484 becoming the designated router." 485 SYNTAX Integer32 (0..'FF'h) 487 TOSType ::= TEXTUAL-CONVENTION 488 STATUS current 489 DESCRIPTION 490 "Type of Service is defined as a mapping to the IP Type of 491 Service Flags as defined in the IP Forwarding Table MIB 493 +-----+-----+-----+-----+-----+-----+-----+-----+ 494 | | | | 495 | PRECEDENCE | TYPE OF SERVICE | 0 | 496 | | | | 497 +-----+-----+-----+-----+-----+-----+-----+-----+ 499 IP TOS IP TOS 500 Field Policy Field Policy 502 Contents Code Contents Code 503 0 0 0 0 ==> 0 0 0 0 1 ==> 2 504 0 0 1 0 ==> 4 0 0 1 1 ==> 6 505 0 1 0 0 ==> 8 0 1 0 1 ==> 10 506 0 1 1 0 ==> 12 0 1 1 1 ==> 14 507 1 0 0 0 ==> 16 1 0 0 1 ==> 18 508 1 0 1 0 ==> 20 1 0 1 1 ==> 22 509 1 1 0 0 ==> 24 1 1 0 1 ==> 26 510 1 1 1 0 ==> 28 1 1 1 1 ==> 30 512 The remaining values are left for future definition." 513 SYNTAX Integer32 (0..30) 515 -- OSPF General Variables 517 -- Note: These parameters apply globally to the Router's 518 -- OSPF Process. 520 ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 } 522 ospfRouterId OBJECT-TYPE 523 SYNTAX RouterID 524 MAX-ACCESS read-write 525 STATUS current 526 DESCRIPTION 527 "A 32-bit integer uniquely identifying the 528 router in the Autonomous System. 529 By convention, to ensure uniqueness, this 530 should default to the value of one of the 531 router's IP interface addresses." 532 REFERENCE 533 "OSPF Version 2, C.1 Global parameters" 534 ::= { ospfGeneralGroup 1 } 536 ospfAdminStat OBJECT-TYPE 537 SYNTAX Status 538 MAX-ACCESS read-write 539 STATUS current 540 DESCRIPTION 541 "The administrative status of OSPF in the 542 router. The value 'enabled' denotes that the 543 OSPF Process is active on at least one inter- 544 face; 'disabled' disables it on all inter- 545 faces." 546 ::= { ospfGeneralGroup 2 } 548 ospfVersionNumber OBJECT-TYPE 549 SYNTAX INTEGER { version2 (2) } 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The current version number of the OSPF proto- 554 col is 2." 556 REFERENCE 557 "OSPF Version 2, Title" 558 ::= { ospfGeneralGroup 3 } 560 ospfAreaBdrRtrStatus OBJECT-TYPE 561 SYNTAX TruthValue 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "A flag to note whether this router is an area 566 border router." 567 REFERENCE 568 "OSPF Version 2, Section 3 Splitting the AS into 569 Areas" 570 ::= { ospfGeneralGroup 4 } 572 ospfASBdrRtrStatus OBJECT-TYPE 573 SYNTAX TruthValue 574 MAX-ACCESS read-write 575 STATUS current 576 DESCRIPTION 577 "A flag to note whether this router is config- 578 ured as an Autonomous System border router." 579 REFERENCE 580 "OSPF Version 2, Section 3.3 Classification of 581 routers" 582 ::= { ospfGeneralGroup 5 } 584 ospfExternLsaCount OBJECT-TYPE 585 SYNTAX Gauge32 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The number of external (LS type 5) link-state 590 advertisements in the link-state database." 591 REFERENCE 592 "OSPF Version 2, Appendix A.4.5 AS external link 593 advertisements" 594 ::= { ospfGeneralGroup 6 } 596 ospfExternLsaCksumSum OBJECT-TYPE 597 SYNTAX Integer32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "The 32-bit unsigned sum of the LS checksums of 602 the external link-state advertisements con- 603 tained in the link-state database. This sum 604 can be used to determine if there has been a 605 change in a router's link state database, and 606 to compare the link-state database of two 607 routers." 608 ::= { ospfGeneralGroup 7 } 610 ospfTOSSupport OBJECT-TYPE 611 SYNTAX TruthValue 612 MAX-ACCESS read-write 613 STATUS current 614 DESCRIPTION 615 "The router's support for type-of-service rout- 616 ing." 617 REFERENCE 618 "OSPF Version 2, Appendix F.1.2 Optional TOS 619 support" 620 ::= { ospfGeneralGroup 8 } 622 ospfOriginateNewLsas OBJECT-TYPE 623 SYNTAX Counter32 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The number of new link-state advertisements 628 that have been originated. This number is in- 629 cremented each time the router originates a new 630 LSA." 631 ::= { ospfGeneralGroup 9 } 633 ospfRxNewLsas OBJECT-TYPE 634 SYNTAX Counter32 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "The number of link-state advertisements re- 639 ceived determined to be new instantiations. 640 This number does not include newer instantia- 641 tions of self-originated link-state advertise- 642 ments." 643 ::= { ospfGeneralGroup 10 } 645 ospfExtLsdbLimit OBJECT-TYPE 646 SYNTAX Integer32 (-1..'7FFFFFFF'h) 647 MAX-ACCESS read-write 648 STATUS current 649 DESCRIPTION 650 "The maximum number of non-default AS- 651 external-LSAs entries that can be stored in the 652 link-state database. If the value is -1, then 653 there is no limit. 655 When the number of non-default AS-external-LSAs 656 in a router's link-state database reaches 657 ospfExtLsdbLimit, the router enters Overflow- 658 State. The router never holds more than 659 ospfExtLsdbLimit non-default AS-external-LSAs 660 in its database. OspfExtLsdbLimit MUST be set 661 identically in all routers attached to the OSPF 662 backbone and/or any regular OSPF area. (i.e., 663 OSPF stub areas and NSSAs are excluded)." 664 DEFVAL { -1 } 665 ::= { ospfGeneralGroup 11 } 667 ospfMulticastExtensions OBJECT-TYPE 668 SYNTAX Integer32 669 MAX-ACCESS read-write 670 STATUS current 671 DESCRIPTION 672 "A Bit Mask indicating whether the router is 673 forwarding IP multicast (Class D) datagrams 674 based on the algorithms defined in the Multi- 675 cast Extensions to OSPF. 677 Bit 0, if set, indicates that the router can 678 forward IP multicast datagrams in the router's 679 directly attached areas (called intra-area mul- 680 ticast routing). 682 Bit 1, if set, indicates that the router can 683 forward IP multicast datagrams between OSPF 684 areas (called inter-area multicast routing). 686 Bit 2, if set, indicates that the router can 687 forward IP multicast datagrams between Auto- 688 nomous Systems (called inter-AS multicast rout- 689 ing). 691 Only certain combinations of bit settings are 692 allowed, namely: 0 (no multicast forwarding is 693 enabled), 1 (intra-area multicasting only), 3 694 (intra-area and inter-area multicasting), 5 695 (intra-area and inter-AS multicasting) and 7 696 (multicasting everywhere). By default, no mul- 697 ticast forwarding is enabled." 698 DEFVAL { 0 } 699 ::= { ospfGeneralGroup 12 } 701 ospfExitOverflowInterval OBJECT-TYPE 702 SYNTAX PositiveInteger 703 MAX-ACCESS read-write 704 STATUS current 705 DESCRIPTION 706 "The number of seconds that, after entering 707 OverflowState, a router will attempt to leave 708 OverflowState. This allows the router to again 709 originate non-default AS-external-LSAs. When 710 set to 0, the router will not leave Overflow- 711 State until restarted." 712 DEFVAL { 0 } 713 ::= { ospfGeneralGroup 13 } 715 ospfDemandExtensions OBJECT-TYPE 716 SYNTAX TruthValue 717 MAX-ACCESS read-write 718 STATUS current 719 DESCRIPTION 720 "The router's support for demand routing." 721 REFERENCE 722 "Extending OSPF to Support Demand Circuits" 723 ::= { ospfGeneralGroup 14 } 725 ospfRFC1583Compatibility OBJECT-TYPE 726 SYNTAX TruthValue 727 MAX-ACCESS read-write 728 STATUS current 729 DESCRIPTION 730 "Indicates metrics used to choose among multiple AS- 731 external-LSAs. When RFC1583Compatibility is set to 732 enabled, only cost will be used when choosing among 733 multiple AS-external-LSAs advertising the same 734 destination. When RFC1583Compatibility is set to 735 disabled, preference will be driven first by type of 736 path using cost only to break ties." 737 REFERENCE 738 "OSPF Version 2, Section 16.4.1 External path preferences" 739 ::= { ospfGeneralGroup 15 } 741 ospfOpaqueLsaSupport OBJECT-TYPE 742 SYNTAX TruthValue 743 MAX-ACCESS read-write 744 STATUS current 745 DESCRIPTION 746 "The router's support for Opaque LSA types." 747 REFERENCE 748 "The OSPF Opaque LSA Option" 749 ::= { ospfGeneralGroup 16 } 751 ospfTrafficEngineeringSupport OBJECT-TYPE 752 SYNTAX TruthValue 753 MAX-ACCESS read-write 754 STATUS current 755 DESCRIPTION 756 "The router's support for OSPF traffic engineering." 757 ::= { ospfGeneralGroup 17 } 759 -- OSPF Area Data Structure 760 -- The OSPF Area Data Structure contains information 761 -- regarding the various areas. The interfaces and 762 -- virtual links are configured as part of these areas. 763 -- Area 0.0.0.0, by definition, is the Backbone Area 765 ospfAreaTable OBJECT-TYPE 766 SYNTAX SEQUENCE OF OspfAreaEntry 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "Information describing the configured parame- 771 ters and cumulative statistics of the router's 772 attached areas." 773 REFERENCE 774 "OSPF Version 2, Section 6 The Area Data Struc- 775 ture" 776 ::= { ospf 2 } 778 ospfAreaEntry OBJECT-TYPE 779 SYNTAX OspfAreaEntry 780 MAX-ACCESS not-accessible 781 STATUS current 782 DESCRIPTION 783 "Information describing the configured parame- 784 ters and cumulative statistics of one of the 785 router's attached areas." 786 INDEX { ospfAreaId } 787 ::= { ospfAreaTable 1 } 789 OspfAreaEntry ::= 790 SEQUENCE { 791 ospfAreaId 792 AreaID, 793 ospfAuthType 794 Integer32, 795 ospfImportAsExtern 796 INTEGER, 797 ospfSpfRuns 798 Counter32, 799 ospfAreaBdrRtrCount 800 Gauge32, 801 ospfAsBdrRtrCount 802 Gauge32, 803 ospfAreaLsaCount 804 Gauge32, 805 ospfAreaLsaCksumSum 806 Integer32, 807 ospfAreaSummary 808 INTEGER, 809 ospfAreaStatus 810 RowStatus, 811 ospfAreaNssaTranslatorRole 812 INTEGER, 813 ospfAreaNssaTranslatorState 814 INTEGER, 815 ospfAreaNssaTranslatorStabilityInterval 816 PositiveInteger, 817 ospfAreaNssaTranslatorEvents 818 Counter32 819 } 821 ospfAreaId OBJECT-TYPE 822 SYNTAX AreaID 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "A 32-bit integer uniquely identifying an area. 827 Area ID 0.0.0.0 is used for the OSPF backbone." 828 REFERENCE 829 "OSPF Version 2, Appendix C.2 Area parameters" 830 ::= { ospfAreaEntry 1 } 832 ospfAuthType OBJECT-TYPE 833 SYNTAX Integer32 834 -- none (0), 835 -- simplePassword (1) 836 -- md5 (2) 837 -- reserved for specification by IANA (> 2) 838 MAX-ACCESS read-create 839 STATUS obsolete 840 DESCRIPTION 841 "The authentication type specified for an area. 842 Additional authentication types may be assigned 843 locally on a per Area basis." 844 REFERENCE 845 "OSPF Version 2, Appendix D Authentication" 846 DEFVAL { 0 } -- no authentication, by default 847 ::= { ospfAreaEntry 2 } 849 ospfImportAsExtern OBJECT-TYPE 850 SYNTAX INTEGER { 851 importExternal (1), 852 importNoExternal (2), 853 importNssa (3) 854 } 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "Indicates whether an area is a Stub area, NSSA, or standard 859 area. Type-5 AS-External LSAs and Type-11 Opaque LSAs are 860 not imported into Stub Areas or NSSAs. NSSAs import AS- 861 External data as Type-7 LSAs" 862 REFERENCE 863 "OSPF Version 2, Appendix C.2 Area parameters" 864 DEFVAL { importExternal } 865 ::= { ospfAreaEntry 3 } 867 ospfSpfRuns OBJECT-TYPE 868 SYNTAX Counter32 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "The number of times that the intra-area route 873 table has been calculated using this area's 874 link-state database. This is typically done 875 using Dijkstra's algorithm." 876 ::= { ospfAreaEntry 4 } 878 ospfAreaBdrRtrCount OBJECT-TYPE 879 SYNTAX Gauge32 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The total number of area border routers reach- 884 able within this area. This is initially zero, 885 and is calculated in each SPF Pass." 886 ::= { ospfAreaEntry 5 } 888 ospfAsBdrRtrCount OBJECT-TYPE 889 SYNTAX Gauge32 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "The total number of Autonomous System border 894 routers reachable within this area. This is 895 initially zero, and is calculated in each SPF 896 Pass." 897 ::= { ospfAreaEntry 6 } 899 ospfAreaLsaCount OBJECT-TYPE 900 SYNTAX Gauge32 901 MAX-ACCESS read-only 902 STATUS current 903 DESCRIPTION 904 "The total number of link-state advertisements 905 in this area's link-state database, excluding 906 AS External LSA's." 907 ::= { ospfAreaEntry 7 } 909 ospfAreaLsaCksumSum OBJECT-TYPE 910 SYNTAX Integer32 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "The 32-bit unsigned sum of the link-state ad- 915 vertisements' LS checksums contained in this 916 area's link-state database. This sum excludes 917 external (LS type 5) link-state advertisements. 918 The sum can be used to determine if there has 919 been a change in a router's link state data- 920 base, and to compare the link-state database of 921 two routers." 922 DEFVAL { 0 } 923 ::= { ospfAreaEntry 8 } 925 ospfAreaSummary OBJECT-TYPE 926 SYNTAX INTEGER { 927 noAreaSummary (1), 928 sendAreaSummary (2) 929 } 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "The variable ospfAreaSummary controls the im- 934 port of summary LSAs into stub and NSSA areas. 935 It has no effect on other areas. 937 If it is noAreaSummary, the router will neither 938 originate nor propagate summary LSAs into the 939 stub or NSSA area. It will rely entirely on its 940 default route. 942 If it is sendAreaSummary, the router will both 943 summarize and propagate summary LSAs." 944 DEFVAL { noAreaSummary } 945 ::= { ospfAreaEntry 9 } 947 ospfAreaStatus OBJECT-TYPE 948 SYNTAX RowStatus 949 MAX-ACCESS read-create 950 STATUS current 951 DESCRIPTION 952 "This object permits management of the table by 953 facilitating actions such as row creation, 954 construction and destruction." 955 ::= { ospfAreaEntry 10 } 957 ospfAreaNssaTranslatorRole OBJECT-TYPE 958 SYNTAX INTEGER { always (1), candidate (2) } 959 MAX-ACCESS read-create 960 STATUS current 961 DESCRIPTION 962 "Indicates an NSSA Border router's ability to 963 perform NSSA translation of type-7 LSAs into 964 type-5 LSAs." 965 DEFVAL { candidate } 966 ::= { ospfAreaEntry 11 } 968 ospfAreaNssaTranslatorState OBJECT-TYPE 969 SYNTAX INTEGER { enabled (1), 970 elected (2), 971 disabled (3) 972 } 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "Indicates if and how an NSSA Border router is 977 performing NSSA translation of type-7 LSAs into type-5 978 LSAs. When this object set to enabled, the NSSA Border 979 router's OspfAreaNssaExtTranslatorRole has been set to 980 always. When this object is set to elected, a candidate 981 NSSA Border router is Translating type-7 LSAs into type-5. 982 When this object is set to disabled, a candidate NSSA 983 Border router is NOT translating type-7 LSAs into type-5." 984 ::= { ospfAreaEntry 12 } 986 ospfAreaNssaTranslatorStabilityInterval OBJECT-TYPE 987 SYNTAX PositiveInteger 988 MAX-ACCESS read-create 989 STATUS current 990 DESCRIPTION 991 "The number of seconds after an elected translator 992 determines its services are no longer required, that 993 it should continue to perform its translation duties." 994 DEFVAL { 40 } 995 ::= { ospfAreaEntry 13 } 997 ospfAreaNssaTranslatorEvents OBJECT-TYPE 998 SYNTAX Counter32 999 MAX-ACCESS read-only 1000 STATUS current 1001 DESCRIPTION 1002 "Indicates the number of Translator State changes 1003 that have occurred since the last boot-up." 1004 ::= { ospfAreaEntry 14 } 1006 -- OSPF Area Default Metric Table 1008 -- The OSPF Area Default Metric Table describes the metrics 1009 -- that a default Area Border Router will advertise into a 1010 -- Stub area. 1012 ospfStubAreaTable OBJECT-TYPE 1013 SYNTAX SEQUENCE OF OspfStubAreaEntry 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "The set of metrics that will be advertised by 1018 a default Area Border Router into a stub area." 1019 REFERENCE 1020 "OSPF Version 2, Appendix C.2, Area Parameters" 1021 ::= { ospf 3 } 1023 ospfStubAreaEntry OBJECT-TYPE 1024 SYNTAX OspfStubAreaEntry 1025 MAX-ACCESS not-accessible 1026 STATUS current 1027 DESCRIPTION 1028 "The metric for a given Type of Service that 1029 will be advertised by a default Area Border 1030 Router into a stub area." 1031 REFERENCE 1032 "OSPF Version 2, Appendix C.2, Area Parameters" 1033 INDEX { ospfStubAreaId, ospfStubTOS } 1034 ::= { ospfStubAreaTable 1 } 1036 OspfStubAreaEntry ::= 1037 SEQUENCE { 1038 ospfStubAreaId 1039 AreaID, 1040 ospfStubTOS 1041 TOSType, 1042 ospfStubMetric 1043 BigMetric, 1044 ospfStubStatus 1045 RowStatus, 1046 ospfStubMetricType 1047 INTEGER 1048 } 1050 ospfStubAreaId OBJECT-TYPE 1051 SYNTAX AreaID 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "The 32 bit identifier for the Stub Area. On 1056 creation, this can be derived from the in- 1057 stance." 1058 ::= { ospfStubAreaEntry 1 } 1060 ospfStubTOS OBJECT-TYPE 1061 SYNTAX TOSType 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "The Type of Service associated with the 1066 metric. On creation, this can be derived from 1067 the instance." 1068 ::= { ospfStubAreaEntry 2 } 1070 ospfStubMetric OBJECT-TYPE 1071 SYNTAX BigMetric 1072 MAX-ACCESS read-create 1073 STATUS current 1074 DESCRIPTION 1075 "The metric value applied at the indicated type 1076 of service. By default, this equals the least 1077 metric at the type of service among the inter- 1078 faces to other areas." 1079 ::= { ospfStubAreaEntry 3 } 1081 ospfStubStatus OBJECT-TYPE 1082 SYNTAX RowStatus 1083 MAX-ACCESS read-create 1084 STATUS current 1085 DESCRIPTION 1086 "This object permits management of the table by 1087 facilitating actions such as row creation, 1088 construction and destruction." 1089 ::= { ospfStubAreaEntry 4 } 1091 ospfStubMetricType OBJECT-TYPE 1092 SYNTAX INTEGER { 1093 ospfMetric (1), -- OSPF Metric 1094 comparableCost (2), -- external type 1 1095 nonComparable (3) -- external type 2 1096 } 1097 MAX-ACCESS read-create 1098 STATUS current 1099 DESCRIPTION 1100 "This variable displays the type of metric ad- 1101 vertised as a default route." 1102 DEFVAL { ospfMetric } 1103 ::= { ospfStubAreaEntry 5 } 1105 -- OSPF Link State Database 1107 -- The Link State Database contains the Link State 1108 -- Advertisements from throughout the areas that the 1109 -- device is attached to. 1111 ospfLsdbTable OBJECT-TYPE 1112 SYNTAX SEQUENCE OF OspfLsdbEntry 1113 MAX-ACCESS not-accessible 1114 STATUS current 1115 DESCRIPTION 1116 "The OSPF Process's Link State Database." 1117 REFERENCE 1118 "OSPF Version 2, Section 12 Link State Adver- 1119 tisements" 1120 ::= { ospf 4 } 1122 ospfLsdbEntry OBJECT-TYPE 1123 SYNTAX OspfLsdbEntry 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION 1127 "A single Link State Advertisement." 1128 INDEX { ospfLsdbAreaId, ospfLsdbType, 1129 ospfLsdbLsid, ospfLsdbRouterId } 1130 ::= { ospfLsdbTable 1 } 1132 OspfLsdbEntry ::= 1133 SEQUENCE { 1134 ospfLsdbAreaId 1135 AreaID, 1136 ospfLsdbType 1137 INTEGER, 1138 ospfLsdbLsid 1139 IpAddress, 1140 ospfLsdbRouterId 1141 RouterID, 1142 ospfLsdbSequence 1143 Integer32, 1144 ospfLsdbAge 1145 Integer32, 1146 ospfLsdbChecksum 1147 Integer32, 1148 ospfLsdbAdvertisement 1149 OCTET STRING 1150 } 1152 ospfLsdbAreaId OBJECT-TYPE 1153 SYNTAX AreaID 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "The 32 bit identifier of the Area from which 1158 the LSA was received." 1159 REFERENCE 1160 "OSPF Version 2, Appendix C.2 Area parameters" 1161 ::= { ospfLsdbEntry 1 } 1163 -- Note: External Link State Advertisements are permitted 1164 -- for backward compatibility, but should be displayed in 1165 -- the ospfExtLsdbTable rather than here. 1167 ospfLsdbType OBJECT-TYPE 1168 SYNTAX INTEGER { 1169 routerLink (1), 1170 networkLink (2), 1171 summaryLink (3), 1172 asSummaryLink (4), 1173 asExternalLink (5), -- but see ospfExtLsdbTable 1174 multicastLink (6), 1175 nssaExternalLink (7), 1176 areaOpaqueLink (10) 1177 } 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "The type of the link state advertisement. 1182 Each link state type has a separate advertise- 1183 ment format." 1184 REFERENCE 1185 "OSPF Version 2, Appendix A.4.1 The Link State 1186 Advertisement header" 1187 ::= { ospfLsdbEntry 2 } 1189 ospfLsdbLsid OBJECT-TYPE 1190 SYNTAX IpAddress 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "The Link State ID is an LS Type Specific field 1195 containing either a Router ID or an IP Address; 1196 it identifies the piece of the routing domain 1197 that is being described by the advertisement." 1198 REFERENCE 1199 "OSPF Version 2, Section 12.1.4 Link State ID" 1200 ::= { ospfLsdbEntry 3 } 1202 ospfLsdbRouterId OBJECT-TYPE 1203 SYNTAX RouterID 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "The 32 bit number that uniquely identifies the 1208 originating router in the Autonomous System." 1209 REFERENCE 1210 "OSPF Version 2, Appendix C.1 Global parameters" 1211 ::= { ospfLsdbEntry 4 } 1213 -- Note that the OSPF Sequence Number is a 32 bit signed 1214 -- integer. It starts with the value '80000001'h, 1215 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1216 -- Thus, a typical sequence number will be very negative. 1218 ospfLsdbSequence OBJECT-TYPE 1219 SYNTAX Integer32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "The sequence number field is a signed 32-bit 1224 integer. It is used to detect old and dupli- 1225 cate link state advertisements. The space of 1226 sequence numbers is linearly ordered. The 1227 larger the sequence number the more recent the 1228 advertisement." 1229 REFERENCE 1230 "OSPF Version 2, Section 12.1.6 LS sequence 1231 number" 1232 ::= { ospfLsdbEntry 5 } 1234 ospfLsdbAge OBJECT-TYPE 1235 SYNTAX Integer32 -- Should be 0..MaxAge, except when 1236 -- doNotAge bit is set 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "This field is the age of the link state adver- 1241 tisement in seconds." 1242 REFERENCE 1243 "OSPF Version 2, Section 12.1.1 LS age" 1244 ::= { ospfLsdbEntry 6 } 1246 ospfLsdbChecksum OBJECT-TYPE 1247 SYNTAX Integer32 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "This field is the checksum of the complete 1252 contents of the advertisement, excepting the 1253 age field. The age field is excepted so that 1254 an advertisement's age can be incremented 1255 without updating the checksum. The checksum 1256 used is the same that is used for ISO connec- 1257 tionless datagrams; it is commonly referred to 1258 as the Fletcher checksum." 1259 REFERENCE 1260 "OSPF Version 2, Section 12.1.7 LS checksum" 1261 ::= { ospfLsdbEntry 7 } 1263 ospfLsdbAdvertisement OBJECT-TYPE 1264 SYNTAX OCTET STRING (SIZE (1..65535)) 1265 MAX-ACCESS read-only 1266 STATUS current 1267 DESCRIPTION 1268 "The entire Link State Advertisement, including 1269 its header." 1270 REFERENCE 1271 "OSPF Version 2, Section 12 Link State Adver- 1272 tisements" 1273 ::= { ospfLsdbEntry 8 } 1275 -- Address Range Table 1277 -- The Address Range Table acts as an adjunct to the Area 1278 -- Table; It describes those Address Range Summaries that 1279 -- are configured to be propagated from an Area to reduce 1280 -- the amount of information about it which is known beyond 1281 -- its borders. 1283 ospfAreaRangeTable OBJECT-TYPE 1284 SYNTAX SEQUENCE OF OspfAreaRangeEntry 1285 MAX-ACCESS not-accessible 1286 STATUS obsolete 1287 DESCRIPTION 1288 "A range if IP addresses specified by an IP 1289 address/IP network mask pair. For example, 1290 class B address range of X.X.X.X with a network 1291 mask of 255.255.0.0 includes all IP addresses 1292 from X.X.0.0 to X.X.255.255" 1293 REFERENCE 1294 "OSPF Version 2, Appendix C.2 Area parameters" 1295 ::= { ospf 5 } 1297 ospfAreaRangeEntry OBJECT-TYPE 1298 SYNTAX OspfAreaRangeEntry 1299 MAX-ACCESS not-accessible 1300 STATUS obsolete 1301 DESCRIPTION 1302 "A range if IP addresses specified by an IP 1303 address/IP network mask pair. For example, 1304 class B address range of X.X.X.X with a network 1305 mask of 255.255.0.0 includes all IP addresses 1306 from X.X.0.0 to X.X.255.255" 1307 REFERENCE 1308 "OSPF Version 2, Appendix C.2 Area parameters" 1309 INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet } 1310 ::= { ospfAreaRangeTable 1 } 1312 OspfAreaRangeEntry ::= 1313 SEQUENCE { 1314 ospfAreaRangeAreaId 1315 AreaID, 1316 ospfAreaRangeNet 1317 IpAddress, 1318 ospfAreaRangeMask 1319 IpAddress, 1320 ospfAreaRangeStatus 1321 RowStatus, 1322 ospfAreaRangeEffect 1323 INTEGER 1324 } 1326 ospfAreaRangeAreaId OBJECT-TYPE 1327 SYNTAX AreaID 1328 MAX-ACCESS read-only 1329 STATUS obsolete 1330 DESCRIPTION 1331 "The Area the Address Range is to be found 1332 within." 1333 REFERENCE 1334 "OSPF Version 2, Appendix C.2 Area parameters" 1335 ::= { ospfAreaRangeEntry 1 } 1337 ospfAreaRangeNet OBJECT-TYPE 1338 SYNTAX IpAddress 1339 MAX-ACCESS read-only 1340 STATUS obsolete 1341 DESCRIPTION 1342 "The IP Address of the Net or Subnet indicated 1343 by the range." 1344 REFERENCE 1345 "OSPF Version 2, Appendix C.2 Area parameters" 1346 ::= { ospfAreaRangeEntry 2 } 1348 ospfAreaRangeMask OBJECT-TYPE 1349 SYNTAX IpAddress 1350 MAX-ACCESS read-create 1351 STATUS obsolete 1352 DESCRIPTION 1353 "The Subnet Mask that pertains to the Net or 1354 Subnet." 1355 REFERENCE 1356 "OSPF Version 2, Appendix C.2 Area parameters" 1357 ::= { ospfAreaRangeEntry 3 } 1359 ospfAreaRangeStatus OBJECT-TYPE 1360 SYNTAX RowStatus 1361 MAX-ACCESS read-create 1362 STATUS obsolete 1363 DESCRIPTION 1364 "This object permits management of the table by 1365 facilitating actions such as row creation, 1366 construction and destruction." 1367 ::= { ospfAreaRangeEntry 4 } 1369 ospfAreaRangeEffect OBJECT-TYPE 1370 SYNTAX INTEGER { 1371 advertiseMatching (1), 1372 doNotAdvertiseMatching (2) 1373 } 1374 MAX-ACCESS read-create 1375 STATUS obsolete 1376 DESCRIPTION 1377 "Subnets subsumed by ranges either trigger the 1378 advertisement of the indicated summary (adver- 1379 tiseMatching), or result in the subnet's not 1380 being advertised at all outside the area." 1381 DEFVAL { advertiseMatching } 1382 ::= { ospfAreaRangeEntry 5 } 1384 -- OSPF Host Table 1386 -- The Host/Metric Table indicates what hosts are directly 1387 -- attached to the Router, what metrics and types of 1388 -- service should be advertised for them and what Areas they 1389 -- are found within. 1391 ospfHostTable OBJECT-TYPE 1392 SYNTAX SEQUENCE OF OspfHostEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "The list of Hosts, and their metrics, that the 1397 router will advertise as host routes." 1398 REFERENCE 1399 "OSPF Version 2, Appendix C.7 Host route param- 1400 eters" 1401 ::= { ospf 6 } 1403 ospfHostEntry OBJECT-TYPE 1404 SYNTAX OspfHostEntry 1405 MAX-ACCESS not-accessible 1406 STATUS current 1407 DESCRIPTION 1408 "A metric to be advertised, for a given type of 1409 service, when a given host is reachable." 1410 INDEX { ospfHostIpAddress, ospfHostTOS } 1411 ::= { ospfHostTable 1 } 1413 OspfHostEntry ::= 1414 SEQUENCE { 1415 ospfHostIpAddress 1416 IpAddress, 1417 ospfHostTOS 1418 TOSType, 1419 ospfHostMetric 1420 Metric, 1421 ospfHostStatus 1422 RowStatus, 1423 ospfHostAreaID 1424 AreaID 1425 } 1427 ospfHostIpAddress OBJECT-TYPE 1428 SYNTAX IpAddress 1429 MAX-ACCESS read-only 1430 STATUS current 1431 DESCRIPTION 1432 "The IP Address of the Host." 1433 REFERENCE 1434 "OSPF Version 2, Appendix C.7 Host route parame- 1435 ters" 1436 ::= { ospfHostEntry 1 } 1438 ospfHostTOS OBJECT-TYPE 1439 SYNTAX TOSType 1440 MAX-ACCESS read-only 1441 STATUS current 1442 DESCRIPTION 1443 "The Type of Service of the route being config- 1444 ured." 1445 REFERENCE 1446 "OSPF Version 2, Appendix C.7 Host route parame- 1447 ters" 1448 ::= { ospfHostEntry 2 } 1450 ospfHostMetric OBJECT-TYPE 1451 SYNTAX Metric 1452 MAX-ACCESS read-create 1453 STATUS current 1454 DESCRIPTION 1455 "The Metric to be advertised." 1456 REFERENCE 1457 "OSPF Version 2, Appendix C.7 Host route parame- 1458 ters" 1459 ::= { ospfHostEntry 3 } 1461 ospfHostStatus OBJECT-TYPE 1462 SYNTAX RowStatus 1463 MAX-ACCESS read-create 1464 STATUS current 1465 DESCRIPTION 1466 "This object permits management of the table by 1467 facilitating actions such as row creation, 1468 construction and destruction." 1470 ::= { ospfHostEntry 4 } 1472 ospfHostAreaID OBJECT-TYPE 1473 SYNTAX AreaID 1474 MAX-ACCESS read-create 1475 STATUS current 1476 DESCRIPTION 1477 "The Area the Host Entry is to be found within." 1478 REFERENCE 1479 "OSPF Version 2, Appendix C.7 Host parameters" 1480 ::= { ospfHostEntry 5 } 1482 -- OSPF Interface Table 1484 -- The OSPF Interface Table augments the ipAddrTable 1485 -- with OSPF specific information. 1487 ospfIfTable OBJECT-TYPE 1488 SYNTAX SEQUENCE OF OspfIfEntry 1489 MAX-ACCESS not-accessible 1490 STATUS current 1491 DESCRIPTION 1492 "The OSPF Interface Table describes the inter- 1493 faces from the viewpoint of OSPF." 1494 REFERENCE 1495 "OSPF Version 2, Appendix C.3 Router interface 1496 parameters" 1497 ::= { ospf 7 } 1499 ospfIfEntry OBJECT-TYPE 1500 SYNTAX OspfIfEntry 1501 MAX-ACCESS not-accessible 1502 STATUS current 1503 DESCRIPTION 1504 "The OSPF Interface Entry describes one inter- 1505 face from the viewpoint of OSPF." 1506 INDEX { ospfIfIpAddress, ospfAddressLessIf } 1507 ::= { ospfIfTable 1 } 1509 OspfIfEntry ::= 1510 SEQUENCE { 1511 ospfIfIpAddress 1512 IpAddress, 1513 ospfAddressLessIf 1514 InterfaceIndexOrZero, 1515 ospfIfAreaId 1516 AreaID, 1517 ospfIfType 1518 INTEGER, 1519 ospfIfAdminStat 1520 Status, 1521 ospfIfRtrPriority 1522 DesignatedRouterPriority, 1523 ospfIfTransitDelay 1524 UpToMaxAge, 1525 ospfIfRetransInterval 1526 UpToMaxAge, 1527 ospfIfHelloInterval 1528 HelloRange, 1529 ospfIfRtrDeadInterval 1530 PositiveInteger, 1531 ospfIfPollInterval 1532 PositiveInteger, 1533 ospfIfState 1534 INTEGER, 1535 ospfIfDesignatedRouter 1536 IpAddress, 1537 ospfIfBackupDesignatedRouter 1538 IpAddress, 1539 ospfIfEvents 1540 Counter32, 1541 ospfIfAuthKey 1542 OCTET STRING, 1543 ospfIfStatus 1544 RowStatus, 1545 ospfIfMulticastForwarding 1546 INTEGER, 1547 ospfIfDemand 1548 TruthValue, 1549 ospfIfAuthType 1550 INTEGER, 1551 ospfIfLsaCount 1552 Gauge32, 1553 ospfIfLsaCksumSum 1554 Integer32 1556 } 1558 ospfIfIpAddress OBJECT-TYPE 1559 SYNTAX IpAddress 1560 MAX-ACCESS read-only 1561 STATUS current 1562 DESCRIPTION 1563 "The IP address of this OSPF interface." 1564 ::= { ospfIfEntry 1 } 1566 ospfAddressLessIf OBJECT-TYPE 1567 SYNTAX InterfaceIndexOrZero 1568 MAX-ACCESS read-only 1569 STATUS current 1570 DESCRIPTION 1571 "For the purpose of easing the instancing of 1572 addressed and address less interfaces; This 1573 variable takes the value 0 on interfaces with 1574 IP Addresses, and the corresponding value of 1575 ifIndex for interfaces having no IP Address." 1576 ::= { ospfIfEntry 2 } 1578 ospfIfAreaId OBJECT-TYPE 1579 SYNTAX AreaID 1580 MAX-ACCESS read-create 1581 STATUS current 1582 DESCRIPTION 1583 "A 32-bit integer uniquely identifying the area 1584 to which the interface connects. Area ID 1585 0.0.0.0 is used for the OSPF backbone." 1586 DEFVAL { '00000000'H } -- 0.0.0.0 1587 ::= { ospfIfEntry 3 } 1589 ospfIfType OBJECT-TYPE 1590 SYNTAX INTEGER { 1591 broadcast (1), 1592 nbma (2), 1593 pointToPoint (3), 1594 pointToMultipoint (5) 1595 } 1596 MAX-ACCESS read-create 1597 STATUS current 1598 DESCRIPTION 1599 "The OSPF interface type. 1600 By way of a default, this field may be intuited 1601 from the corresponding value of ifType. Broad- 1602 cast LANs, such as Ethernet and IEEE 802.5, 1603 take the value 'broadcast', X.25 and similar 1604 technologies take the value 'nbma', and links 1605 that are definitively point to point take the 1606 value 'pointToPoint'." 1607 ::= { ospfIfEntry 4 } 1609 ospfIfAdminStat OBJECT-TYPE 1610 SYNTAX Status 1611 MAX-ACCESS read-create 1612 STATUS current 1613 DESCRIPTION 1614 "The OSPF interface's administrative status. 1615 The value formed on the interface, and the in- 1616 terface will be advertised as an internal route 1617 to some area. The value 'disabled' denotes 1618 that the interface is external to OSPF." 1619 DEFVAL { enabled } 1620 ::= { ospfIfEntry 5 } 1622 ospfIfRtrPriority OBJECT-TYPE 1623 SYNTAX DesignatedRouterPriority 1624 MAX-ACCESS read-create 1625 STATUS current 1626 DESCRIPTION 1627 "The priority of this interface. Used in 1628 multi-access networks, this field is used in 1629 the designated router election algorithm. The 1630 value 0 signifies that the router is not eligi- 1631 ble to become the designated router on this 1632 particular network. In the event of a tie in 1633 this value, routers will use their Router ID as 1634 a tie breaker." 1635 DEFVAL { 1 } 1636 ::= { ospfIfEntry 6 } 1638 ospfIfTransitDelay OBJECT-TYPE 1639 SYNTAX UpToMaxAge 1640 MAX-ACCESS read-create 1641 STATUS current 1642 DESCRIPTION 1643 "The estimated number of seconds it takes to 1644 transmit a link state update packet over this 1645 interface." 1646 DEFVAL { 1 } 1647 ::= { ospfIfEntry 7 } 1649 ospfIfRetransInterval OBJECT-TYPE 1650 SYNTAX UpToMaxAge 1651 MAX-ACCESS read-create 1652 STATUS current 1653 DESCRIPTION 1654 "The number of seconds between link-state ad- 1655 vertisement retransmissions, for adjacencies 1656 belonging to this interface. This value is 1657 also used when retransmitting database descrip- 1658 tion and link-state request packets." 1659 DEFVAL { 5 } 1660 ::= { ospfIfEntry 8 } 1662 ospfIfHelloInterval OBJECT-TYPE 1663 SYNTAX HelloRange 1664 MAX-ACCESS read-create 1665 STATUS current 1666 DESCRIPTION 1667 "The length of time, in seconds, between the 1668 Hello packets that the router sends on the in- 1669 terface. This value must be the same for all 1670 routers attached to a common network." 1671 DEFVAL { 10 } 1672 ::= { ospfIfEntry 9 } 1674 ospfIfRtrDeadInterval OBJECT-TYPE 1675 SYNTAX PositiveInteger 1676 MAX-ACCESS read-create 1677 STATUS current 1678 DESCRIPTION 1679 "The number of seconds that a router's Hello 1680 packets have not been seen before it's neigh- 1681 bors declare the router down. This should be 1682 some multiple of the Hello interval. This 1683 value must be the same for all routers attached 1684 to a common network." 1685 DEFVAL { 40 } 1686 ::= { ospfIfEntry 10 } 1688 ospfIfPollInterval OBJECT-TYPE 1689 SYNTAX PositiveInteger 1690 MAX-ACCESS read-create 1691 STATUS current 1692 DESCRIPTION 1693 "The larger time interval, in seconds, between 1694 the Hello packets sent to an inactive non- 1695 broadcast multi- access neighbor." 1696 DEFVAL { 120 } 1697 ::= { ospfIfEntry 11 } 1699 ospfIfState OBJECT-TYPE 1700 SYNTAX INTEGER { 1701 down (1), 1702 loopback (2), 1703 waiting (3), 1704 pointToPoint (4), 1705 designatedRouter (5), 1706 backupDesignatedRouter (6), 1707 otherDesignatedRouter (7) 1708 } 1709 MAX-ACCESS read-only 1710 STATUS current 1711 DESCRIPTION 1712 "The OSPF Interface State." 1713 DEFVAL { down } 1714 ::= { ospfIfEntry 12 } 1716 ospfIfDesignatedRouter OBJECT-TYPE 1717 SYNTAX IpAddress 1718 MAX-ACCESS read-only 1719 STATUS current 1720 DESCRIPTION 1721 "The IP Address of the Designated Router." 1722 DEFVAL { '00000000'H } -- 0.0.0.0 1723 ::= { ospfIfEntry 13 } 1725 ospfIfBackupDesignatedRouter OBJECT-TYPE 1726 SYNTAX IpAddress 1727 MAX-ACCESS read-only 1728 STATUS current 1729 DESCRIPTION 1730 "The IP Address of the Backup Designated 1731 Router." 1732 DEFVAL { '00000000'H } -- 0.0.0.0 1733 ::= { ospfIfEntry 14 } 1735 ospfIfEvents OBJECT-TYPE 1736 SYNTAX Counter32 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "The number of times this OSPF interface has 1741 changed its state, or an error has occurred." 1742 ::= { ospfIfEntry 15 } 1744 ospfIfAuthKey OBJECT-TYPE 1745 SYNTAX OCTET STRING (SIZE (0..256)) 1746 MAX-ACCESS read-create 1747 STATUS current 1748 DESCRIPTION 1749 "The cleartext password used as an OSPF 1750 Authentication key when simplePassword security 1751 is enabled. This object does not access any OSPF 1752 Cryptogaphic (e.g. MD5) Authentication Key under 1753 any circumstance. 1755 If the key length is shorter than 8 octets, the 1756 agent will left adjust and zero fill to 8 octets. 1758 Unauthenticated interfaces need no authentication 1759 key, and simple password authentication cannot use 1760 a key of more than 8 octets. 1762 Note that the use of simplePassword authentication 1763 is NOT recommended when there is concern regarding 1764 attack upon the OSPF system. SimplePassword 1765 authentication is only sufficient to protect against 1766 accidental misconfigurations because it re-uses 1767 cleartext passwords. [RFC-1704] 1769 When read, ospfIfAuthKey always returns an Octet 1770 String of length zero." 1771 REFERENCE 1772 "OSPF Version 2, Section 9 The Interface Data 1773 Structure" 1774 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 1775 ::= { ospfIfEntry 16 } 1777 ospfIfStatus OBJECT-TYPE 1778 SYNTAX RowStatus 1779 MAX-ACCESS read-create 1780 STATUS current 1781 DESCRIPTION 1782 "This object permits management of the table by 1783 facilitating actions such as row creation, 1784 construction and destruction." 1785 ::= { ospfIfEntry 17 } 1787 ospfIfMulticastForwarding OBJECT-TYPE 1788 SYNTAX INTEGER { 1789 blocked (1), -- no multicast forwarding 1790 multicast (2), -- using multicast address 1791 unicast (3) -- to each OSPF neighbor 1792 } 1793 MAX-ACCESS read-create 1794 STATUS current 1795 DESCRIPTION 1796 "The way multicasts should forwarded on this 1797 interface; not forwarded, forwarded as data 1798 link multicasts, or forwarded as data link uni- 1799 casts. Data link multicasting is not meaning- 1800 ful on point to point and NBMA interfaces, and 1801 setting ospfMulticastForwarding to 0 effective- 1802 ly disables all multicast forwarding." 1803 DEFVAL { blocked } 1804 ::= { ospfIfEntry 18 } 1806 ospfIfDemand OBJECT-TYPE 1807 SYNTAX TruthValue 1808 MAX-ACCESS read-create 1809 STATUS current 1810 DESCRIPTION 1811 "Indicates whether Demand OSPF procedures (hel- 1812 lo suppression to FULL neighbors and setting the 1813 DoNotAge flag on propagated LSAs) should be per- 1814 formed on this interface." 1815 DEFVAL { false } 1816 ::= { ospfIfEntry 19 } 1818 ospfIfAuthType OBJECT-TYPE 1819 SYNTAX INTEGER (0..255) 1820 -- none (0), 1821 -- simplePassword (1) 1822 -- md5 (2) 1823 -- reserved for specification by IANA (> 2) 1824 MAX-ACCESS read-create 1825 STATUS current 1826 DESCRIPTION 1827 "The authentication type specified for an in- 1828 terface. Additional authentication types may 1829 be assigned locally. 1831 Note that this object can be used to engage 1832 in significant attacks against an OSPF router." 1833 REFERENCE 1834 "OSPF Version 2, Appendix D Authentication" 1835 DEFVAL { 0 } -- no authentication, by default 1836 ::= { ospfIfEntry 20 } 1838 ospfIfLsaCount OBJECT-TYPE 1839 SYNTAX Gauge32 1840 MAX-ACCESS read-only 1841 STATUS current 1842 DESCRIPTION 1843 "The total number of link-local link state advertisements 1844 in this interface's link-local link state database." 1845 ::= { ospfIfEntry 21 } 1847 ospfIfLsaCksumSum OBJECT-TYPE 1848 SYNTAX Integer32 1849 MAX-ACCESS read-only 1850 STATUS current 1851 DESCRIPTION 1852 "The 32-bit unsigned sum of the link-state ad- 1853 vertisements' LS checksums contained in this 1854 interface's link-local link state database. 1855 The sum can be used to determine if there has 1856 been a change in the interface's link state data- 1857 base, and to compare the interface link-state database of 1858 routers attached to the same subnet." 1859 ::= { ospfIfEntry 22 } 1861 -- OSPF Interface Metric Table 1863 -- The Metric Table describes the metrics to be advertised 1864 -- for a specified interface at the various types of service. 1865 -- As such, this table is an adjunct of the OSPF Interface 1866 -- Table. 1868 -- Types of service, as defined by RFC 791, have the ability 1869 -- to request low delay, high bandwidth, or reliable linkage. 1871 -- For the purposes of this specification, the measure of 1872 -- bandwidth: 1874 -- Metric = 10^8 / ifSpeed 1875 -- is the default value. For multiple link interfaces, note 1876 -- that ifSpeed is the sum of the individual link speeds. 1877 -- This yields a number having the following typical values: 1879 -- Network Type/bit rate Metric 1881 -- >= 100 MBPS 1 1882 -- Ethernet/802.3 10 1883 -- E1 48 1884 -- T1 (ESF) 65 1885 -- 64 KBPS 1562 1886 -- 56 KBPS 1785 1887 -- 19.2 KBPS 5208 1888 -- 9.6 KBPS 10416 1890 -- Routes that are not specified use the default (TOS 0) metric 1892 ospfIfMetricTable OBJECT-TYPE 1893 SYNTAX SEQUENCE OF OspfIfMetricEntry 1894 MAX-ACCESS not-accessible 1895 STATUS current 1896 DESCRIPTION 1897 "The TOS metrics for a non-virtual interface 1898 identified by the interface index." 1899 REFERENCE 1900 "OSPF Version 2, Appendix C.3 Router interface 1901 parameters" 1902 ::= { ospf 8 } 1904 ospfIfMetricEntry OBJECT-TYPE 1905 SYNTAX OspfIfMetricEntry 1906 MAX-ACCESS not-accessible 1907 STATUS current 1908 DESCRIPTION 1909 "A particular TOS metric for a non-virtual in- 1910 terface identified by the interface index." 1911 REFERENCE 1912 "OSPF Version 2, Appendix C.3 Router interface 1913 parameters" 1914 INDEX { ospfIfMetricIpAddress, 1915 ospfIfMetricAddressLessIf, 1916 ospfIfMetricTOS } 1917 ::= { ospfIfMetricTable 1 } 1919 OspfIfMetricEntry ::= 1920 SEQUENCE { 1921 ospfIfMetricIpAddress 1922 IpAddress, 1923 ospfIfMetricAddressLessIf 1924 InterfaceIndexOrZero, 1925 ospfIfMetricTOS 1926 TOSType, 1927 ospfIfMetricValue 1928 Metric, 1929 ospfIfMetricStatus 1930 RowStatus 1931 } 1933 ospfIfMetricIpAddress OBJECT-TYPE 1934 SYNTAX IpAddress 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "The IP address of this OSPF interface. On row 1939 creation, this can be derived from the in- 1940 stance." 1941 ::= { ospfIfMetricEntry 1 } 1943 ospfIfMetricAddressLessIf OBJECT-TYPE 1944 SYNTAX InterfaceIndexOrZero 1945 MAX-ACCESS read-only 1946 STATUS current 1947 DESCRIPTION 1948 "For the purpose of easing the instancing of 1949 addressed and addressless interfaces; This 1950 variable takes the value 0 on interfaces with 1951 IP Addresses, and the value of ifIndex for in- 1952 terfaces having no IP Address. On row crea- 1953 tion, this can be derived from the instance." 1954 ::= { ospfIfMetricEntry 2 } 1956 ospfIfMetricTOS OBJECT-TYPE 1957 SYNTAX TOSType 1958 MAX-ACCESS read-only 1959 STATUS current 1960 DESCRIPTION 1961 "The type of service metric being referenced. 1962 On row creation, this can be derived from the 1963 instance." 1964 ::= { ospfIfMetricEntry 3 } 1966 ospfIfMetricValue OBJECT-TYPE 1967 SYNTAX Metric 1968 MAX-ACCESS read-create 1969 STATUS current 1970 DESCRIPTION 1971 "The metric of using this type of service on 1972 this interface. The default value of the TOS 0 1973 Metric is 10^8 / ifSpeed." 1974 ::= { ospfIfMetricEntry 4 } 1976 ospfIfMetricStatus OBJECT-TYPE 1977 SYNTAX RowStatus 1978 MAX-ACCESS read-create 1979 STATUS current 1980 DESCRIPTION 1981 "This object permits management of the table by 1982 facilitating actions such as row creation, 1983 construction and destruction." 1984 ::= { ospfIfMetricEntry 5 } 1986 -- OSPF Virtual Interface Table 1988 -- The Virtual Interface Table describes the virtual 1989 -- links that the OSPF Process is configured to 1990 -- carry on. 1992 ospfVirtIfTable OBJECT-TYPE 1993 SYNTAX SEQUENCE OF OspfVirtIfEntry 1994 MAX-ACCESS not-accessible 1995 STATUS current 1996 DESCRIPTION 1997 "Information about this router's virtual inter- 1998 faces." 1999 REFERENCE 2000 "OSPF Version 2, Appendix C.4 Virtual link 2001 parameters" 2002 ::= { ospf 9 } 2004 ospfVirtIfEntry OBJECT-TYPE 2005 SYNTAX OspfVirtIfEntry 2006 MAX-ACCESS not-accessible 2007 STATUS current 2008 DESCRIPTION 2009 "Information about a single Virtual Interface." 2010 INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor } 2011 ::= { ospfVirtIfTable 1 } 2013 OspfVirtIfEntry ::= 2014 SEQUENCE { 2015 ospfVirtIfAreaId 2016 AreaID, 2017 ospfVirtIfNeighbor 2018 RouterID, 2019 ospfVirtIfTransitDelay 2020 UpToMaxAge, 2021 ospfVirtIfRetransInterval 2022 UpToMaxAge, 2023 ospfVirtIfHelloInterval 2024 HelloRange, 2025 ospfVirtIfRtrDeadInterval 2026 PositiveInteger, 2028 ospfVirtIfState 2029 INTEGER, 2030 ospfVirtIfEvents 2031 Counter32, 2032 ospfVirtIfAuthType 2033 INTEGER, 2034 ospfVirtIfAuthKey 2035 OCTET STRING, 2036 ospfVirtIfStatus 2037 RowStatus, 2038 ospfVirtIfLsaCount 2039 Gauge32, 2040 ospfVirtIfLsaCksumSum 2041 Integer32 2042 } 2044 ospfVirtIfAreaId OBJECT-TYPE 2045 SYNTAX AreaID 2046 MAX-ACCESS read-only 2047 STATUS current 2048 DESCRIPTION 2049 "The Transit Area that the Virtual Link 2050 traverses. By definition, this is not 0.0.0.0" 2051 ::= { ospfVirtIfEntry 1 } 2053 ospfVirtIfNeighbor OBJECT-TYPE 2054 SYNTAX RouterID 2055 MAX-ACCESS read-only 2056 STATUS current 2057 DESCRIPTION 2058 "The Router ID of the Virtual Neighbor." 2059 ::= { ospfVirtIfEntry 2 } 2061 ospfVirtIfTransitDelay OBJECT-TYPE 2062 SYNTAX UpToMaxAge 2063 MAX-ACCESS read-create 2064 STATUS current 2065 DESCRIPTION 2066 "The estimated number of seconds it takes to 2067 transmit a link-state update packet over this 2068 interface." 2069 DEFVAL { 1 } 2070 ::= { ospfVirtIfEntry 3 } 2072 ospfVirtIfRetransInterval OBJECT-TYPE 2073 SYNTAX UpToMaxAge 2074 MAX-ACCESS read-create 2075 STATUS current 2076 DESCRIPTION 2077 "The number of seconds between link-state ad- 2078 vertisement retransmissions, for adjacencies 2079 belonging to this interface. This value is 2080 also used when retransmitting database descrip- 2081 tion and link-state request packets. This 2082 value should be well over the expected round- 2083 trip time." 2084 DEFVAL { 5 } 2085 ::= { ospfVirtIfEntry 4 } 2087 ospfVirtIfHelloInterval OBJECT-TYPE 2088 SYNTAX HelloRange 2089 MAX-ACCESS read-create 2090 STATUS current 2091 DESCRIPTION 2092 "The length of time, in seconds, between the 2093 Hello packets that the router sends on the in- 2094 terface. This value must be the same for the 2095 virtual neighbor." 2096 DEFVAL { 10 } 2097 ::= { ospfVirtIfEntry 5 } 2099 ospfVirtIfRtrDeadInterval OBJECT-TYPE 2100 SYNTAX PositiveInteger 2101 MAX-ACCESS read-create 2102 STATUS current 2103 DESCRIPTION 2104 "The number of seconds that a router's Hello 2105 packets have not been seen before it's neigh- 2106 bors declare the router down. This should be 2107 some multiple of the Hello interval. This 2108 value must be the same for the virtual neigh- 2109 bor." 2110 DEFVAL { 60 } 2111 ::= { ospfVirtIfEntry 6 } 2113 ospfVirtIfState OBJECT-TYPE 2114 SYNTAX INTEGER { 2115 down (1), -- these use the same encoding 2116 pointToPoint (4) -- as the ospfIfTable 2117 } 2118 MAX-ACCESS read-only 2119 STATUS current 2120 DESCRIPTION 2121 "OSPF virtual interface states." 2122 DEFVAL { down } 2123 ::= { ospfVirtIfEntry 7 } 2125 ospfVirtIfEvents OBJECT-TYPE 2126 SYNTAX Counter32 2127 MAX-ACCESS read-only 2128 STATUS current 2129 DESCRIPTION 2130 "The number of state changes or error events on 2131 this Virtual Link" 2132 ::= { ospfVirtIfEntry 8 } 2134 ospfVirtIfAuthKey OBJECT-TYPE 2135 SYNTAX OCTET STRING (SIZE(0..256)) 2136 MAX-ACCESS read-create 2137 STATUS current 2138 DESCRIPTION 2139 "The cleartext password used as an OSPF 2140 Authentication key when simplePassword security 2141 is enabled. This object does not access any OSPF 2142 Cryptogaphic (e.g. MD5) Authentication Key under 2143 any circumstance. 2145 If the key length is shorter than 8 octets, the 2146 agent will left adjust and zero fill to 8 octets. 2148 Unauthenticated interfaces need no authentication 2149 key, and simple password authentication cannot use 2150 a key of more than 8 octets. 2152 Note that the use of simplePassword authentication 2153 is NOT recommended when there is concern regarding 2154 attack upon the OSPF system. SimplePassword 2155 authentication is only sufficient to protect against 2156 accidental misconfigurations because it re-uses 2157 cleartext passwords. [RFC-1704] 2159 When read, ospfIfAuthKey always returns an Octet 2160 String of length zero." 2161 REFERENCE 2162 "OSPF Version 2, Section 9 The Interface Data 2163 Structure" 2164 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 2165 ::= { ospfVirtIfEntry 9 } 2167 ospfVirtIfStatus OBJECT-TYPE 2168 SYNTAX RowStatus 2169 MAX-ACCESS read-create 2170 STATUS current 2171 DESCRIPTION 2172 "This object permits management of the table by 2173 facilitating actions such as row creation, 2174 construction and destruction." 2175 ::= { ospfVirtIfEntry 10 } 2177 ospfVirtIfAuthType OBJECT-TYPE 2178 SYNTAX INTEGER (0..255) 2179 -- none (0), 2180 -- simplePassword (1) 2181 -- md5 (2) 2182 -- reserved for specification by IANA (> 2) 2183 MAX-ACCESS read-create 2184 STATUS current 2185 DESCRIPTION 2186 "The authentication type specified for a virtu- 2187 al interface. Additional authentication types 2188 may be assigned locally. 2190 Note that this object can be used to engage 2191 in significant attacks against an OSPF router." 2192 REFERENCE 2193 "OSPF Version 2, Appendix E Authentication" 2194 DEFVAL { 0 } -- no authentication, by default 2195 ::= { ospfVirtIfEntry 11 } 2197 ospfVirtIfLsaCount OBJECT-TYPE 2198 SYNTAX Gauge32 2199 MAX-ACCESS read-only 2200 STATUS current 2201 DESCRIPTION 2202 "The total number of link-local link state advertisements 2203 in this virtual interface's link-local link state database." 2204 ::= { ospfVirtIfEntry 12 } 2206 ospfVirtIfLsaCksumSum OBJECT-TYPE 2207 SYNTAX Integer32 2208 MAX-ACCESS read-only 2209 STATUS current 2210 DESCRIPTION 2211 "The 32-bit unsigned sum of the link-state ad- 2212 vertisements' LS checksums contained in this 2213 virtual interface's link-local link state database. 2214 The sum can be used to determine if there has 2215 been a change in the virtual interface's link state data- 2216 base, and to compare the virtual interface link-state 2217 database of the virtual neighbors." 2218 ::= { ospfVirtIfEntry 13 } 2220 -- OSPF Neighbor Table 2222 -- The OSPF Neighbor Table describes all neighbors in 2223 -- the locality of the subject router. 2225 ospfNbrTable OBJECT-TYPE 2226 SYNTAX SEQUENCE OF OspfNbrEntry 2227 MAX-ACCESS not-accessible 2228 STATUS current 2229 DESCRIPTION 2230 "A table of non-virtual neighbor information." 2232 REFERENCE 2233 "OSPF Version 2, Section 10 The Neighbor Data 2234 Structure" 2235 ::= { ospf 10 } 2237 ospfNbrEntry OBJECT-TYPE 2238 SYNTAX OspfNbrEntry 2239 MAX-ACCESS not-accessible 2240 STATUS current 2241 DESCRIPTION 2242 "The information regarding a single neighbor." 2243 REFERENCE 2244 "OSPF Version 2, Section 10 The Neighbor Data 2245 Structure" 2246 INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex } 2247 ::= { ospfNbrTable 1 } 2249 OspfNbrEntry ::= 2250 SEQUENCE { 2251 ospfNbrIpAddr 2252 IpAddress, 2253 ospfNbrAddressLessIndex 2254 InterfaceIndexOrZero, 2255 ospfNbrRtrId 2256 RouterID, 2257 ospfNbrOptions 2258 Integer32, 2259 ospfNbrPriority 2260 DesignatedRouterPriority, 2261 ospfNbrState 2262 INTEGER, 2263 ospfNbrEvents 2264 Counter32, 2265 ospfNbrLsRetransQLen 2266 Gauge32, 2267 ospfNbmaNbrStatus 2268 RowStatus, 2269 ospfNbmaNbrPermanence 2270 INTEGER, 2271 ospfNbrHelloSuppressed 2272 TruthValue 2273 } 2275 ospfNbrIpAddr OBJECT-TYPE 2276 SYNTAX IpAddress 2277 MAX-ACCESS read-only 2278 STATUS current 2279 DESCRIPTION 2280 "The IP address this neighbor is using in its 2281 IP Source Address. Note that, on addressless 2282 links, this will not be 0.0.0.0, but the ad- 2283 dress of another of the neighbor's interfaces." 2284 ::= { ospfNbrEntry 1 } 2286 ospfNbrAddressLessIndex OBJECT-TYPE 2287 SYNTAX InterfaceIndexOrZero 2288 MAX-ACCESS read-only 2289 STATUS current 2290 DESCRIPTION 2291 "On an interface having an IP Address, zero. 2292 On addressless interfaces, the corresponding 2293 value of ifIndex in the Internet Standard MIB. 2294 On row creation, this can be derived from the 2295 instance." 2296 ::= { ospfNbrEntry 2 } 2298 ospfNbrRtrId OBJECT-TYPE 2299 SYNTAX RouterID 2300 MAX-ACCESS read-only 2301 STATUS current 2302 DESCRIPTION 2303 "A 32-bit integer (represented as a type IpAd- 2304 dress) uniquely identifying the neighboring 2305 router in the Autonomous System." 2306 DEFVAL { '00000000'H } -- 0.0.0.0 2307 ::= { ospfNbrEntry 3 } 2309 ospfNbrOptions OBJECT-TYPE 2310 SYNTAX Integer32 2311 MAX-ACCESS read-only 2312 STATUS current 2313 DESCRIPTION 2314 "A Bit Mask corresponding to the neighbor's op- 2315 tions field. 2317 Bit 0, if set, indicates that the system will 2318 operate on Type of Service metrics other than 2319 TOS 0. If zero, the neighbor will ignore all 2320 metrics except the TOS 0 metric. 2322 Bit 1, if set, indicates that the associated 2323 area accepts and operates on external informa- 2324 tion; if zero, it is a stub area. 2326 Bit 2, if set, indicates that the system is ca- 2327 pable of routing IP Multicast datagrams; i.e., 2328 that it implements the Multicast Extensions to 2329 OSPF. 2331 Bit 3, if set, indicates that the associated 2332 area is an NSSA. These areas are capable of 2333 carrying type 7 external advertisements, which 2334 are translated into type 5 external advertise- 2335 ments at NSSA borders." 2336 REFERENCE 2337 "OSPF Version 2, Section 12.1.2 Options" 2338 DEFVAL { 0 } 2339 ::= { ospfNbrEntry 4 } 2341 ospfNbrPriority OBJECT-TYPE 2342 SYNTAX DesignatedRouterPriority 2343 MAX-ACCESS read-create 2344 STATUS current 2345 DESCRIPTION 2346 "The priority of this neighbor in the designat- 2347 ed router election algorithm. The value 0 sig- 2348 nifies that the neighbor is not eligible to be- 2349 come the designated router on this particular 2350 network." 2351 DEFVAL { 1 } 2352 ::= { ospfNbrEntry 5 } 2354 ospfNbrState OBJECT-TYPE 2355 SYNTAX INTEGER { 2356 down (1), 2357 attempt (2), 2358 init (3), 2359 twoWay (4), 2360 exchangeStart (5), 2361 exchange (6), 2362 loading (7), 2363 full (8) 2364 } 2365 MAX-ACCESS read-only 2366 STATUS current 2367 DESCRIPTION 2368 "The State of the relationship with this Neigh- 2369 bor." 2370 REFERENCE 2371 "OSPF Version 2, Section 10.1 Neighbor States" 2372 DEFVAL { down } 2373 ::= { ospfNbrEntry 6 } 2375 ospfNbrEvents OBJECT-TYPE 2376 SYNTAX Counter32 2377 MAX-ACCESS read-only 2378 STATUS current 2379 DESCRIPTION 2380 "The number of times this neighbor relationship 2381 has changed state, or an error has occurred." 2382 ::= { ospfNbrEntry 7 } 2384 ospfNbrLsRetransQLen OBJECT-TYPE 2385 SYNTAX Gauge32 2386 MAX-ACCESS read-only 2387 STATUS current 2388 DESCRIPTION 2389 "The current length of the retransmission 2390 queue." 2391 ::= { ospfNbrEntry 8 } 2393 ospfNbmaNbrStatus OBJECT-TYPE 2394 SYNTAX RowStatus 2395 MAX-ACCESS read-create 2396 STATUS current 2397 DESCRIPTION 2398 "This object permits management of the table by 2399 facilitating actions such as row creation, 2400 construction and destruction." 2401 ::= { ospfNbrEntry 9 } 2403 ospfNbmaNbrPermanence OBJECT-TYPE 2404 SYNTAX INTEGER { 2405 dynamic (1), -- learned through protocol 2406 permanent (2) -- configured address 2407 } 2408 MAX-ACCESS read-only 2409 STATUS current 2410 DESCRIPTION 2411 "This variable displays the status of the en- 2412 try. 'dynamic' and 'permanent' refer to how 2413 the neighbor became known." 2414 DEFVAL { permanent } 2415 ::= { ospfNbrEntry 10 } 2417 ospfNbrHelloSuppressed OBJECT-TYPE 2418 SYNTAX TruthValue 2419 MAX-ACCESS read-only 2420 STATUS current 2421 DESCRIPTION 2422 "Indicates whether Hellos are being suppressed 2423 to the neighbor" 2424 ::= { ospfNbrEntry 11 } 2426 -- OSPF Virtual Neighbor Table 2428 -- This table describes all virtual neighbors. 2429 -- Since Virtual Links are configured in the 2430 -- virtual interface table, this table is read-only. 2432 ospfVirtNbrTable OBJECT-TYPE 2433 SYNTAX SEQUENCE OF OspfVirtNbrEntry 2434 MAX-ACCESS not-accessible 2435 STATUS current 2436 DESCRIPTION 2437 "A table of virtual neighbor information." 2438 REFERENCE 2439 "OSPF Version 2, Section 15 Virtual Links" 2440 ::= { ospf 11 } 2442 ospfVirtNbrEntry OBJECT-TYPE 2443 SYNTAX OspfVirtNbrEntry 2444 MAX-ACCESS not-accessible 2445 STATUS current 2446 DESCRIPTION 2447 "Virtual neighbor information." 2448 INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId } 2449 ::= { ospfVirtNbrTable 1 } 2451 OspfVirtNbrEntry ::= 2452 SEQUENCE { 2453 ospfVirtNbrArea 2454 AreaID, 2455 ospfVirtNbrRtrId 2456 RouterID, 2457 ospfVirtNbrIpAddr 2458 IpAddress, 2459 ospfVirtNbrOptions 2460 Integer32, 2461 ospfVirtNbrState 2462 INTEGER, 2463 ospfVirtNbrEvents 2464 Counter32, 2465 ospfVirtNbrLsRetransQLen 2466 Gauge32, 2467 ospfVirtNbrHelloSuppressed 2468 TruthValue 2469 } 2471 ospfVirtNbrArea OBJECT-TYPE 2472 SYNTAX AreaID 2473 MAX-ACCESS read-only 2474 STATUS current 2475 DESCRIPTION 2476 "The Transit Area Identifier." 2477 ::= { ospfVirtNbrEntry 1 } 2479 ospfVirtNbrRtrId OBJECT-TYPE 2480 SYNTAX RouterID 2481 MAX-ACCESS read-only 2482 STATUS current 2483 DESCRIPTION 2484 "A 32-bit integer uniquely identifying the 2485 neighboring router in the Autonomous System." 2487 ::= { ospfVirtNbrEntry 2 } 2489 ospfVirtNbrIpAddr OBJECT-TYPE 2490 SYNTAX IpAddress 2491 MAX-ACCESS read-only 2492 STATUS current 2493 DESCRIPTION 2494 "The IP address this Virtual Neighbor is us- 2495 ing." 2496 ::= { ospfVirtNbrEntry 3 } 2498 ospfVirtNbrOptions OBJECT-TYPE 2499 SYNTAX Integer32 2500 MAX-ACCESS read-only 2501 STATUS current 2502 DESCRIPTION 2503 "A Bit Mask corresponding to the neighbor's op- 2504 tions field. 2506 Bit 1, if set, indicates that the system will 2507 operate on Type of Service metrics other than 2508 TOS 0. If zero, the neighbor will ignore all 2509 metrics except the TOS 0 metric. 2511 Bit 2, if set, indicates that the system is 2512 Network Multicast capable; ie, that it imple- 2513 ments OSPF Multicast Routing." 2514 ::= { ospfVirtNbrEntry 4 } 2516 ospfVirtNbrState OBJECT-TYPE 2517 SYNTAX INTEGER { 2518 down (1), 2519 attempt (2), 2520 init (3), 2521 twoWay (4), 2522 exchangeStart (5), 2523 exchange (6), 2524 loading (7), 2525 full (8) 2526 } 2527 MAX-ACCESS read-only 2528 STATUS current 2529 DESCRIPTION 2530 "The state of the Virtual Neighbor Relation- 2531 ship." 2532 ::= { ospfVirtNbrEntry 5 } 2534 ospfVirtNbrEvents OBJECT-TYPE 2535 SYNTAX Counter32 2536 MAX-ACCESS read-only 2537 STATUS current 2538 DESCRIPTION 2539 "The number of times this virtual link has 2540 changed its state, or an error has occurred." 2541 ::= { ospfVirtNbrEntry 6 } 2543 ospfVirtNbrLsRetransQLen OBJECT-TYPE 2544 SYNTAX Gauge32 2545 MAX-ACCESS read-only 2546 STATUS current 2547 DESCRIPTION 2548 "The current length of the retransmission 2549 queue." 2550 ::= { ospfVirtNbrEntry 7 } 2552 ospfVirtNbrHelloSuppressed OBJECT-TYPE 2553 SYNTAX TruthValue 2554 MAX-ACCESS read-only 2555 STATUS current 2556 DESCRIPTION 2557 "Indicates whether Hellos are being suppressed 2558 to the neighbor" 2559 ::= { ospfVirtNbrEntry 8 } 2561 -- OSPF Link State Database, External 2563 -- The Link State Database contains the Link State 2564 -- Advertisements from throughout the areas that the 2565 -- device is attached to. 2567 -- This table is identical to the OSPF LSDB Table in 2568 -- format, but contains only Link State Advertisements with 2569 -- global flooding scope. The purpose is to allow external 2570 -- LSAs to be displayed once for the router rather 2571 -- than once in each non-stub area. 2573 ospfExtLsdbTable OBJECT-TYPE 2574 SYNTAX SEQUENCE OF OspfExtLsdbEntry 2575 MAX-ACCESS not-accessible 2576 STATUS current 2577 DESCRIPTION 2578 "The OSPF Process's Links State Database." 2579 REFERENCE 2580 "OSPF Version 2, Section 12 Link State Adver- 2581 tisements" 2582 ::= { ospf 12 } 2584 ospfExtLsdbEntry OBJECT-TYPE 2585 SYNTAX OspfExtLsdbEntry 2586 MAX-ACCESS not-accessible 2587 STATUS current 2588 DESCRIPTION 2589 "A single Link State Advertisement." 2590 INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId } 2591 ::= { ospfExtLsdbTable 1 } 2593 OspfExtLsdbEntry ::= 2594 SEQUENCE { 2595 ospfExtLsdbType 2596 INTEGER, 2597 ospfExtLsdbLsid 2598 IpAddress, 2599 ospfExtLsdbRouterId 2600 RouterID, 2601 ospfExtLsdbSequence 2602 Integer32, 2603 ospfExtLsdbAge 2604 Integer32, 2605 ospfExtLsdbChecksum 2606 Integer32, 2607 ospfExtLsdbAdvertisement 2608 OCTET STRING 2609 } 2611 ospfExtLsdbType OBJECT-TYPE 2612 SYNTAX INTEGER { 2613 asExternalLink (5), 2614 asOpaqueLink (11) 2615 } 2616 MAX-ACCESS read-only 2617 STATUS current 2618 DESCRIPTION 2619 "The type of the link state advertisement. 2620 Each link state type has a separate advertise- 2621 ment format." 2622 REFERENCE 2623 "OSPF Version 2, Appendix A.4.1 The Link State 2624 Advertisement header" 2625 ::= { ospfExtLsdbEntry 1 } 2627 ospfExtLsdbLsid OBJECT-TYPE 2628 SYNTAX IpAddress 2629 MAX-ACCESS read-only 2630 STATUS current 2631 DESCRIPTION 2632 "The Link State ID is an LS Type Specific field 2633 containing either a Router ID or an IP Address; 2634 it identifies the piece of the routing domain 2635 that is being described by the advertisement." 2636 REFERENCE 2637 "OSPF Version 2, Section 12.1.4 Link State ID" 2638 ::= { ospfExtLsdbEntry 2 } 2640 ospfExtLsdbRouterId OBJECT-TYPE 2641 SYNTAX RouterID 2642 MAX-ACCESS read-only 2643 STATUS current 2644 DESCRIPTION 2645 "The 32 bit number that uniquely identifies the 2646 originating router in the Autonomous System." 2647 REFERENCE 2648 "OSPF Version 2, Appendix C.1 Global parameters" 2649 ::= { ospfExtLsdbEntry 3 } 2651 -- Note that the OSPF Sequence Number is a 32 bit signed 2652 -- integer. It starts with the value '80000001'h, 2653 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 2654 -- Thus, a typical sequence number will be very negative. 2656 ospfExtLsdbSequence OBJECT-TYPE 2657 SYNTAX Integer32 2658 MAX-ACCESS read-only 2659 STATUS current 2660 DESCRIPTION 2661 "The sequence number field is a signed 32-bit 2662 integer. It is used to detect old and dupli- 2663 cate link state advertisements. The space of 2664 sequence numbers is linearly ordered. The 2665 larger the sequence number the more recent the 2666 advertisement." 2667 REFERENCE 2668 "OSPF Version 2, Section 12.1.6 LS sequence 2669 number" 2670 ::= { ospfExtLsdbEntry 4 } 2672 ospfExtLsdbAge OBJECT-TYPE 2673 SYNTAX Integer32 -- Should be 0..MaxAge, except when 2674 -- doNotAge bit is set 2675 MAX-ACCESS read-only 2676 STATUS current 2677 DESCRIPTION 2678 "This field is the age of the link state adver- 2679 tisement in seconds." 2680 REFERENCE 2681 "OSPF Version 2, Section 12.1.1 LS age" 2682 ::= { ospfExtLsdbEntry 5 } 2684 ospfExtLsdbChecksum OBJECT-TYPE 2685 SYNTAX Integer32 2686 MAX-ACCESS read-only 2687 STATUS current 2688 DESCRIPTION 2689 "This field is the checksum of the complete 2690 contents of the advertisement, excepting the 2691 age field. The age field is excepted so that 2692 an advertisement's age can be incremented 2693 without updating the checksum. The checksum 2694 used is the same that is used for ISO connec- 2695 tionless datagrams; it is commonly referred to 2696 as the Fletcher checksum." 2697 REFERENCE 2698 "OSPF Version 2, Section 12.1.7 LS checksum" 2699 ::= { ospfExtLsdbEntry 6 } 2701 ospfExtLsdbAdvertisement OBJECT-TYPE 2702 SYNTAX OCTET STRING (SIZE(36)) 2703 MAX-ACCESS read-only 2704 STATUS current 2705 DESCRIPTION 2706 "The entire Link State Advertisement, including 2707 its header." 2708 REFERENCE 2709 "OSPF Version 2, Section 12 Link State Adver- 2710 tisements" 2711 ::= { ospfExtLsdbEntry 7 } 2713 -- OSPF Use of the CIDR Route Table 2715 ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 } 2717 -- The IP Forwarding Table defines a number of objects for use by 2718 -- the routing protocol to externalize its information. Most of 2719 -- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy, 2720 -- ipForwardNextHop, ipForwardIfIndex, ipForwardType, 2721 -- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are 2722 -- defined there. 2724 -- Those that leave some discretion are defined here. 2726 -- ipCidrRouteProto is, of course, ospf (13). 2728 -- ipCidrRouteAge is the time since the route was first calculated, 2729 -- as opposed to the time since the last SPF run. 2731 -- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing 2732 -- protocol. The following values shall be found there depending 2733 -- on the way the route was calculated. 2735 ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 } 2736 ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 } 2737 ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 } 2738 ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 } 2740 -- ipCidrRouteMetric1 is, by definition, the primary routing 2741 -- metric. Therefore, it should be the metric that route 2742 -- selection is based on. For intra-area and inter-area routes, 2743 -- it is an OSPF metric. For External Type 1 (comparable value) 2744 -- routes, it is an OSPF metric plus the External Metric. For 2745 -- external Type 2 (non-comparable value) routes, it is the 2746 -- external metric. 2748 -- ipCidrRouteMetric2 is, by definition, a secondary routing 2749 -- metric. Therefore, it should be the metric that breaks a tie 2750 -- among routes having equal metric1 values and the same 2751 -- calculation rule. For intra-area, inter-area routes, and 2752 -- External Type 1 (comparable value) routes, it is unused. For 2753 -- external Type 2 (non-comparable value) routes, it is the metric 2754 -- to the AS border router. 2756 -- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 2757 -- are unused. 2759 -- The OSPF Area Aggregate Table 2760 -- 2761 -- This table replaces the OSPF Area Summary Table, being an 2762 -- extension of that for CIDR routers. 2764 ospfAreaAggregateTable OBJECT-TYPE 2765 SYNTAX SEQUENCE OF OspfAreaAggregateEntry 2766 MAX-ACCESS not-accessible 2767 STATUS current 2768 DESCRIPTION 2769 "A range of IP addresses specified by an IP 2770 address/IP network mask pair. For example, 2771 class B address range of X.X.X.X with a network 2772 mask of 255.255.0.0 includes all IP addresses 2773 from X.X.0.0 to X.X.255.255. Note that if 2774 ranges are configured such that one range sub- 2775 sumes another range (e.g., 10.0.0.0 mask 2776 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2777 most specific match is the preferred one." 2778 REFERENCE 2779 "OSPF Version 2, Appendix C.2 Area parameters" 2780 ::= { ospf 14 } 2782 ospfAreaAggregateEntry OBJECT-TYPE 2783 SYNTAX OspfAreaAggregateEntry 2784 MAX-ACCESS not-accessible 2785 STATUS current 2786 DESCRIPTION 2787 "A range of IP addresses specified by an IP 2788 address/IP network mask pair. For example, 2789 class B address range of X.X.X.X with a network 2790 mask of 255.255.0.0 includes all IP addresses 2791 from X.X.0.0 to X.X.255.255. Note that if 2792 ranges are range configured such that one range 2793 subsumes another range (e.g., 10.0.0.0 mask 2794 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2795 most specific match is the preferred one." 2796 REFERENCE 2797 "OSPF Version 2, Appendix C.2 Area parameters" 2798 INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType, 2799 ospfAreaAggregateNet, ospfAreaAggregateMask } 2800 ::= { ospfAreaAggregateTable 1 } 2802 OspfAreaAggregateEntry ::= 2803 SEQUENCE { 2804 ospfAreaAggregateAreaID 2805 AreaID, 2806 ospfAreaAggregateLsdbType 2807 INTEGER, 2808 ospfAreaAggregateNet 2809 IpAddress, 2810 ospfAreaAggregateMask 2811 IpAddress, 2812 ospfAreaAggregateStatus 2813 RowStatus, 2814 ospfAreaAggregateEffect 2815 INTEGER 2816 } 2818 ospfAreaAggregateAreaID OBJECT-TYPE 2819 SYNTAX AreaID 2820 MAX-ACCESS read-only 2821 STATUS current 2822 DESCRIPTION 2823 "The Area the Address Aggregate is to be found 2824 within." 2825 REFERENCE 2826 "OSPF Version 2, Appendix C.2 Area parameters" 2827 ::= { ospfAreaAggregateEntry 1 } 2829 ospfAreaAggregateLsdbType OBJECT-TYPE 2830 SYNTAX INTEGER { 2831 summaryLink (3), 2832 nssaExternalLink (7) 2833 } 2834 MAX-ACCESS read-only 2835 STATUS current 2836 DESCRIPTION 2837 "The type of the Address Aggregate. This field 2838 specifies the Lsdb type that this Address Ag- 2839 gregate applies to." 2840 REFERENCE 2841 "OSPF Version 2, Appendix A.4.1 The Link State 2842 Advertisement header" 2843 ::= { ospfAreaAggregateEntry 2 } 2845 ospfAreaAggregateNet OBJECT-TYPE 2846 SYNTAX IpAddress 2847 MAX-ACCESS read-only 2848 STATUS current 2849 DESCRIPTION 2850 "The IP Address of the Net or Subnet indicated 2851 by the range." 2852 REFERENCE 2853 "OSPF Version 2, Appendix C.2 Area parameters" 2854 ::= { ospfAreaAggregateEntry 3 } 2856 ospfAreaAggregateMask OBJECT-TYPE 2857 SYNTAX IpAddress 2858 MAX-ACCESS read-only 2859 STATUS current 2860 DESCRIPTION 2861 "The Subnet Mask that pertains to the Net or 2862 Subnet." 2863 REFERENCE 2864 "OSPF Version 2, Appendix C.2 Area parameters" 2865 ::= { ospfAreaAggregateEntry 4 } 2867 ospfAreaAggregateStatus OBJECT-TYPE 2868 SYNTAX RowStatus 2869 MAX-ACCESS read-create 2870 STATUS current 2871 DESCRIPTION 2872 "This object permits management of the table by 2873 facilitating actions such as row creation, 2874 construction and destruction." 2875 ::= { ospfAreaAggregateEntry 5 } 2877 ospfAreaAggregateEffect OBJECT-TYPE 2878 SYNTAX INTEGER { 2879 advertiseMatching (1), 2880 doNotAdvertiseMatching (2) 2881 } 2882 MAX-ACCESS read-create 2883 STATUS current 2884 DESCRIPTION 2885 "Subnets subsumed by ranges either trigger the 2886 advertisement of the indicated aggregate (ad- 2887 vertiseMatching), or result in the subnet's not 2888 being advertised at all outside the area." 2889 DEFVAL { advertiseMatching } 2890 ::= { ospfAreaAggregateEntry 6 } 2892 -- OSPF Link State Database, Link-Local for non-virtual links 2894 -- This table is identical to the OSPF LSDB Table in 2895 -- format, but contains only Link-Local Link State 2896 -- Advertisements for non-virtual links. The purpose is 2897 -- to allow Link-Local LSAs to be displayed for each 2898 -- non-virtual interface. This table is implemented to 2899 -- support type-9 LSAs which are defined in 2900 -- "The OSPF Opaque LSA Option". 2902 ospfLocalLsdbTable OBJECT-TYPE 2903 SYNTAX SEQUENCE OF OspfLocalLsdbEntry 2904 MAX-ACCESS not-accessible 2905 STATUS current 2906 DESCRIPTION 2907 "The OSPF Process's Link-Local Link State Database 2908 for non-virtual links." 2909 REFERENCE 2910 "OSPF Version 2, Section 12 Link State Adver- 2911 tisements and The OSPF Opaque LSA Option" 2912 ::= { ospf 17 } 2914 ospfLocalLsdbEntry OBJECT-TYPE 2915 SYNTAX OspfLocalLsdbEntry 2916 MAX-ACCESS not-accessible 2917 STATUS current 2918 DESCRIPTION 2919 "A single Link State Advertisement." 2920 INDEX { ospfLocalLsdbIpAddress, ospfLocalLsdbAddressLessIf, 2921 ospfLocalLsdbType, ospfLocalLsdbLsid, ospfLocalLsdbRouterId 2922 } 2923 ::= { ospfLocalLsdbTable 1 } 2925 OspfLocalLsdbEntry ::= 2926 SEQUENCE { 2927 ospfLocalLsdbIpAddress 2928 IpAddress, 2929 ospfLocalLsdbAddressLessIf 2930 InterfaceIndexOrZero, 2931 ospfLocalLsdbType 2932 INTEGER, 2933 ospfLocalLsdbLsid 2934 IpAddress, 2935 ospfLocalLsdbRouterId 2936 RouterID, 2937 ospfLocalLsdbSequence 2938 Integer32, 2939 ospfLocalLsdbAge 2940 Integer32, 2941 ospfLocalLsdbChecksum 2942 Integer32, 2944 ospfLocalLsdbAdvertisement 2945 OCTET STRING 2946 } 2948 ospfLocalLsdbIpAddress OBJECT-TYPE 2949 SYNTAX IpAddress 2950 MAX-ACCESS read-only 2951 STATUS current 2952 DESCRIPTION 2953 "The IP Address of the interface from 2954 which the LSA was received if the interface is 2955 numbered." 2956 REFERENCE 2957 "OSPF Version 2, Appendix C.3 Interface parameters" 2958 ::= { ospfLocalLsdbEntry 1 } 2960 ospfLocalLsdbAddressLessIf OBJECT-TYPE 2961 SYNTAX InterfaceIndexOrZero 2962 MAX-ACCESS read-only 2963 STATUS current 2964 DESCRIPTION 2965 "The Interface Index of the interface from 2966 which the LSA was received if the interface is 2967 unnumbered." 2968 REFERENCE 2969 "OSPF Version 2, Appendix C.3 Interface parameters" 2970 ::= { ospfLocalLsdbEntry 2 } 2972 ospfLocalLsdbType OBJECT-TYPE 2973 SYNTAX INTEGER { localOpaqueLink (9) } 2974 MAX-ACCESS read-only 2975 STATUS current 2976 DESCRIPTION 2977 "The type of the link state advertisement. 2978 Each link state type has a separate advertise- 2979 ment format." 2980 REFERENCE 2981 "OSPF Version 2, Appendix A.4.1 The Link State 2982 Advertisement header and " 2983 ::= { ospfLocalLsdbEntry 3 } 2985 ospfLocalLsdbLsid OBJECT-TYPE 2986 SYNTAX IpAddress 2987 MAX-ACCESS read-only 2988 STATUS current 2989 DESCRIPTION 2990 "The Link State ID is an LS Type Specific field 2991 containing a 32 bit identifier in IP address format; 2992 it identifies the piece of the routing domain 2993 that is being described by the advertisement." 2994 REFERENCE 2995 "OSPF Version 2, Section 12.1.4 Link State ID" 2996 ::= { ospfLocalLsdbEntry 4 } 2998 ospfLocalLsdbRouterId OBJECT-TYPE 2999 SYNTAX RouterID 3000 MAX-ACCESS read-only 3001 STATUS current 3002 DESCRIPTION 3003 "The 32 bit number that uniquely identifies the 3004 originating router in the Autonomous System." 3005 REFERENCE 3006 "OSPF Version 2, Appendix C.1 Global parameters" 3007 ::= { ospfLocalLsdbEntry 5 } 3009 -- Note that the OSPF Sequence Number is a 32 bit signed 3010 -- integer. It starts with the value '80000001'h, 3011 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 3012 -- Thus, a typical sequence number will be very negative. 3014 ospfLocalLsdbSequence OBJECT-TYPE 3015 SYNTAX Integer32 3016 MAX-ACCESS read-only 3017 STATUS current 3018 DESCRIPTION 3019 "The sequence number field is a signed 32-bit 3020 integer. It is used to detect old and dupli- 3021 cate link state advertisements. The space of 3022 sequence numbers is linearly ordered. The 3023 larger the sequence number the more recent the 3024 advertisement." 3025 REFERENCE 3026 "OSPF Version 2, Section 12.1.6 LS sequence 3027 number" 3028 ::= { ospfLocalLsdbEntry 6 } 3030 ospfLocalLsdbAge OBJECT-TYPE 3031 SYNTAX Integer32 -- Should be 0..MaxAge, except when 3032 -- doNotAge bit is set 3033 MAX-ACCESS read-only 3034 STATUS current 3035 DESCRIPTION 3036 "This field is the age of the link state adver- 3037 tisement in seconds." 3038 REFERENCE 3039 "OSPF Version 2, Section 12.1.1 LS age" 3040 ::= { ospfLocalLsdbEntry 7 } 3042 ospfLocalLsdbChecksum OBJECT-TYPE 3043 SYNTAX Integer32 3044 MAX-ACCESS read-only 3045 STATUS current 3046 DESCRIPTION 3047 "This field is the checksum of the complete 3048 contents of the advertisement, excepting the 3049 age field. The age field is excepted so that 3050 an advertisement's age can be incremented 3051 without updating the checksum. The checksum 3052 used is the same that is used for ISO connec- 3053 tionless datagrams; it is commonly referred to 3054 as the Fletcher checksum." 3055 REFERENCE 3056 "OSPF Version 2, Section 12.1.7 LS checksum" 3057 ::= { ospfLocalLsdbEntry 8 } 3059 ospfLocalLsdbAdvertisement OBJECT-TYPE 3060 SYNTAX OCTET STRING (SIZE (1..65535)) 3061 MAX-ACCESS read-only 3062 STATUS current 3063 DESCRIPTION 3064 "The entire Link State Advertisement, including 3065 its header." 3066 REFERENCE 3067 "OSPF Version 2, Section 12 Link State Adver- 3068 tisements" 3069 ::= { ospfLocalLsdbEntry 9 } 3071 -- OSPF Link State Database, Link-Local for virtual Links 3073 -- This table is identical to the OSPF LSDB Table in 3074 -- format, but contains only Link-Local Link State 3075 -- Advertisements for virtual links. The purpose is to 3076 -- allow Link-Local LSAs to be displayed for each virtual 3077 -- interface. This table is implemented to support type-9 LSAs 3078 -- which are defined in "The OSPF Opaque LSA Option". 3080 ospfVirtLocalLsdbTable OBJECT-TYPE 3081 SYNTAX SEQUENCE OF OspfVirtLocalLsdbEntry 3082 MAX-ACCESS not-accessible 3083 STATUS current 3084 DESCRIPTION 3085 "The OSPF Process's Link-Local Link State Database 3086 for virtual links." 3087 REFERENCE 3088 "OSPF Version 2, Section 12 Link State Adver- 3089 tisements and The OSPF Opaque LSA Option" 3090 ::= { ospf 18 } 3092 ospfVirtLocalLsdbEntry OBJECT-TYPE 3093 SYNTAX OspfVirtLocalLsdbEntry 3094 MAX-ACCESS not-accessible 3095 STATUS current 3096 DESCRIPTION 3097 "A single Link State Advertisement." 3098 INDEX { ospfVirtLocalLsdbTransitArea, 3099 ospfVirtLocalLsdbNeighbor, 3100 ospfVirtLocalLsdbType, 3101 ospfVirtLocalLsdbLsid, 3102 ospfVirtLocalLsdbRouterId 3103 } 3104 ::= { ospfVirtLocalLsdbTable 1 } 3106 OspfVirtLocalLsdbEntry ::= 3107 SEQUENCE { 3108 ospfVirtLocalLsdbTransitArea 3109 AreaID, 3110 ospfVirtLocalLsdbNeighbor 3111 RouterID, 3112 ospfVirtLocalLsdbType 3113 INTEGER, 3114 ospfVirtLocalLsdbLsid 3115 IpAddress, 3116 ospfVirtLocalLsdbRouterId 3117 RouterID, 3118 ospfVirtLocalLsdbSequence 3119 Integer32, 3120 ospfVirtLocalLsdbAge 3121 Integer32, 3122 ospfVirtLocalLsdbChecksum 3123 Integer32, 3124 ospfVirtLocalLsdbAdvertisement 3125 OCTET STRING 3126 } 3128 ospfVirtLocalLsdbTransitArea OBJECT-TYPE 3129 SYNTAX AreaID 3130 MAX-ACCESS read-only 3131 STATUS current 3132 DESCRIPTION 3133 "The Transit Area that the Virtual Link 3134 traverses. By definition, this is not 0.0.0.0" 3135 REFERENCE 3136 "OSPF Version 2, Appendix C.3 Interface parameters" 3137 ::= { ospfVirtLocalLsdbEntry 1 } 3139 ospfVirtLocalLsdbNeighbor OBJECT-TYPE 3140 SYNTAX RouterID 3141 MAX-ACCESS read-only 3142 STATUS current 3143 DESCRIPTION 3144 "The Router ID of the Virtual Neighbor." 3145 REFERENCE 3146 "OSPF Version 2, Appendix C.3 Interface parameters" 3148 ::= { ospfVirtLocalLsdbEntry 2 } 3150 ospfVirtLocalLsdbType OBJECT-TYPE 3151 SYNTAX INTEGER { localOpaqueLink (9) } 3152 MAX-ACCESS read-only 3153 STATUS current 3154 DESCRIPTION 3155 "The type of the link state advertisement. 3156 Each link state type has a separate advertise- 3157 ment format." 3158 REFERENCE 3159 "OSPF Version 2, Appendix A.4.1 The Link State 3160 Advertisement header and " 3161 ::= { ospfVirtLocalLsdbEntry 3 } 3163 ospfVirtLocalLsdbLsid OBJECT-TYPE 3164 SYNTAX IpAddress 3165 MAX-ACCESS read-only 3166 STATUS current 3167 DESCRIPTION 3168 "The Link State ID is an LS Type Specific field 3169 containing a 32 bit identifier in IP address format; 3170 it identifies the piece of the routing domain 3171 that is being described by the advertisement." 3172 REFERENCE 3173 "OSPF Version 2, Section 12.1.4 Link State ID" 3174 ::= { ospfVirtLocalLsdbEntry 4 } 3176 ospfVirtLocalLsdbRouterId OBJECT-TYPE 3177 SYNTAX RouterID 3178 MAX-ACCESS read-only 3179 STATUS current 3180 DESCRIPTION 3181 "The 32 bit number that uniquely identifies the 3182 originating router in the Autonomous System." 3183 REFERENCE 3184 "OSPF Version 2, Appendix C.1 Global parameters" 3185 ::= { ospfVirtLocalLsdbEntry 5 } 3187 -- Note that the OSPF Sequence Number is a 32 bit signed 3188 -- integer. It starts with the value '80000001'h, 3189 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 3190 -- Thus, a typical sequence number will be very negative. 3192 ospfVirtLocalLsdbSequence OBJECT-TYPE 3193 SYNTAX Integer32 3194 MAX-ACCESS read-only 3195 STATUS current 3196 DESCRIPTION 3197 "The sequence number field is a signed 32-bit 3198 integer. It is used to detect old and dupli- 3199 cate link state advertisements. The space of 3200 sequence numbers is linearly ordered. The 3201 larger the sequence number the more recent the 3202 advertisement." 3203 REFERENCE 3204 "OSPF Version 2, Section 12.1.6 LS sequence 3205 number" 3206 ::= { ospfVirtLocalLsdbEntry 6 } 3208 ospfVirtLocalLsdbAge OBJECT-TYPE 3209 SYNTAX Integer32 -- Should be 0..MaxAge, except when 3210 -- doNotAge bit is set 3211 MAX-ACCESS read-only 3212 STATUS current 3213 DESCRIPTION 3214 "This field is the age of the link state adver- 3215 tisement in seconds." 3216 REFERENCE 3217 "OSPF Version 2, Section 12.1.1 LS age" 3218 ::= { ospfVirtLocalLsdbEntry 7 } 3220 ospfVirtLocalLsdbChecksum OBJECT-TYPE 3221 SYNTAX Integer32 3222 MAX-ACCESS read-only 3223 STATUS current 3224 DESCRIPTION 3225 "This field is the checksum of the complete 3226 contents of the advertisement, excepting the 3227 age field. The age field is excepted so that 3228 an advertisement's age can be incremented 3229 without updating the checksum. The checksum 3230 used is the same that is used for ISO connec- 3231 tionless datagrams; it is commonly referred to 3232 as the Fletcher checksum." 3233 REFERENCE 3234 "OSPF Version 2, Section 12.1.7 LS checksum" 3235 ::= { ospfVirtLocalLsdbEntry 8 } 3237 ospfVirtLocalLsdbAdvertisement OBJECT-TYPE 3238 SYNTAX OCTET STRING (SIZE (1..65535)) 3239 MAX-ACCESS read-only 3240 STATUS current 3241 DESCRIPTION 3242 "The entire Link State Advertisement, including 3243 its header." 3244 REFERENCE 3245 "OSPF Version 2, Section 12 Link State Adver- 3246 tisements" 3247 ::= { ospfVirtLocalLsdbEntry 9 } 3249 -- conformance information 3251 ospfConformance OBJECT IDENTIFIER ::= { ospf 15 } 3253 ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 } 3254 ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 } 3256 -- compliance statements 3258 -- This compliance statement is deprecated and replaced 3259 -- by ospfCompliance2 3261 ospfCompliance MODULE-COMPLIANCE 3262 STATUS deprecated 3263 DESCRIPTION 3264 "The compliance statement." 3265 MODULE -- this module 3266 MANDATORY-GROUPS { 3267 ospfBasicGroup, 3268 ospfAreaGroup, 3269 ospfStubAreaGroup, 3270 ospfIfGroup, 3271 ospfIfMetricGroup, 3272 ospfVirtIfGroup, 3273 ospfNbrGroup, 3274 ospfVirtNbrGroup, 3275 ospfAreaAggregateGroup 3276 } 3277 ::= { ospfCompliances 1 } 3279 ospfCompliance2 MODULE-COMPLIANCE 3280 STATUS current 3281 DESCRIPTION 3282 "The compliance statement." 3283 MODULE -- this module 3284 MANDATORY-GROUPS { 3285 ospfBasicGroup2, 3286 ospfAreaGroup2, 3287 ospfStubAreaGroup, 3288 ospfIfGroup2, 3289 ospfIfMetricGroup, 3290 ospfVirtIfGroup2, 3291 ospfNbrGroup, 3292 ospfVirtNbrGroup, 3293 ospfAreaAggregateGroup 3294 } 3295 GROUP ospfHostGroup 3296 DESCRIPTION 3297 "This group is mandatory for OSPF systems that support 3298 attached hosts." 3299 GROUP ospfLsdbGroup 3300 DESCRIPTION 3301 "This group is mandatory for OSPF systems that display 3302 their per-area link state database." 3303 GROUP ospfExtLsdbGroup 3304 DESCRIPTION 3305 "This group is mandatory for OSPF systems that display 3306 their AS link state database." 3307 GROUP ospfLocalLsdbGroup 3308 DESCRIPTION 3309 "This group is mandatory for OSPF systems that display 3310 their per-link link state database for non-virtual 3311 links." 3312 GROUP ospfVirtLocalLsdbGroup 3313 DESCRIPTION 3314 "This group is mandatory for OSPF systems that display 3315 their per-link link state database for virtual links." 3316 ::= { ospfCompliances 2 } 3318 -- units of conformance 3320 -- This object group is deprecated and replaced by ospfBasicGroup2 3322 ospfBasicGroup OBJECT-GROUP 3323 OBJECTS { 3324 ospfRouterId, 3325 ospfAdminStat, 3326 ospfVersionNumber, 3327 ospfAreaBdrRtrStatus, 3328 ospfASBdrRtrStatus, 3329 ospfExternLsaCount, 3330 ospfExternLsaCksumSum, 3331 ospfTOSSupport, 3332 ospfOriginateNewLsas, 3333 ospfRxNewLsas, 3334 ospfExtLsdbLimit, 3335 ospfMulticastExtensions, 3336 ospfExitOverflowInterval, 3337 ospfDemandExtensions 3338 } 3339 STATUS deprecated 3340 DESCRIPTION 3341 "These objects are required for OSPF systems." 3342 ::= { ospfGroups 1 } 3344 -- This object group is deprecated and replaced by ospfAreaGroup2 3346 ospfAreaGroup OBJECT-GROUP 3347 OBJECTS { 3348 ospfAreaId, 3349 ospfImportAsExtern, 3350 ospfSpfRuns, 3351 ospfAreaBdrRtrCount, 3352 ospfAsBdrRtrCount, 3353 ospfAreaLsaCount, 3354 ospfAreaLsaCksumSum, 3355 ospfAreaSummary, 3356 ospfAreaStatus 3357 } 3358 STATUS deprecated 3359 DESCRIPTION 3360 "These objects are required for OSPF systems 3361 supporting areas. This statement is included 3362 for backwards-compatibility. The ospfAreaGroup2 3363 statement is recommended" 3364 ::= { ospfGroups 2 } 3366 ospfStubAreaGroup OBJECT-GROUP 3367 OBJECTS { 3368 ospfStubAreaId, 3369 ospfStubTOS, 3370 ospfStubMetric, 3371 ospfStubStatus, 3372 ospfStubMetricType 3373 } 3374 STATUS current 3375 DESCRIPTION 3376 "These objects are required for OSPF systems 3377 supporting stub areas." 3378 ::= { ospfGroups 3 } 3380 ospfLsdbGroup OBJECT-GROUP 3381 OBJECTS { 3382 ospfLsdbAreaId, 3383 ospfLsdbType, 3384 ospfLsdbLsid, 3385 ospfLsdbRouterId, 3386 ospfLsdbSequence, 3387 ospfLsdbAge, 3388 ospfLsdbChecksum, 3389 ospfLsdbAdvertisement 3390 } 3391 STATUS current 3392 DESCRIPTION 3393 "These objects are required for OSPF systems 3394 that display their link state database." 3395 ::= { ospfGroups 4 } 3397 ospfAreaRangeGroup OBJECT-GROUP 3398 OBJECTS { 3399 ospfAreaRangeAreaId, 3400 ospfAreaRangeNet, 3401 ospfAreaRangeMask, 3402 ospfAreaRangeStatus, 3403 ospfAreaRangeEffect 3404 } 3405 STATUS obsolete 3406 DESCRIPTION 3407 "These objects are required for non-CIDR OSPF 3408 systems that support multiple areas." 3409 ::= { ospfGroups 5 } 3411 ospfHostGroup OBJECT-GROUP 3412 OBJECTS { 3413 ospfHostIpAddress, 3414 ospfHostTOS, 3415 ospfHostMetric, 3416 ospfHostStatus, 3417 ospfHostAreaID 3418 } 3419 STATUS current 3420 DESCRIPTION 3421 "These objects are required for OSPF systems 3422 that support attached hosts." 3423 ::= { ospfGroups 6 } 3425 -- This object group is deprecated and replaced by ospfIfGroup2 3427 ospfIfGroup OBJECT-GROUP 3428 OBJECTS { 3429 ospfIfIpAddress, 3430 ospfAddressLessIf, 3431 ospfIfAreaId, 3432 ospfIfType, 3433 ospfIfAdminStat, 3434 ospfIfRtrPriority, 3435 ospfIfTransitDelay, 3436 ospfIfRetransInterval, 3437 ospfIfHelloInterval, 3438 ospfIfRtrDeadInterval, 3439 ospfIfPollInterval, 3440 ospfIfState, 3441 ospfIfDesignatedRouter, 3442 ospfIfBackupDesignatedRouter, 3443 ospfIfEvents, 3444 ospfIfAuthType, 3445 ospfIfAuthKey, 3446 ospfIfStatus, 3447 ospfIfMulticastForwarding, 3448 ospfIfDemand 3449 } 3450 STATUS deprecated 3451 DESCRIPTION 3452 "These objects are required for OSPF systems." 3453 ::= { ospfGroups 7 } 3455 ospfIfMetricGroup OBJECT-GROUP 3456 OBJECTS { 3457 ospfIfMetricIpAddress, 3458 ospfIfMetricAddressLessIf, 3459 ospfIfMetricTOS, 3460 ospfIfMetricValue, 3461 ospfIfMetricStatus 3462 } 3463 STATUS current 3464 DESCRIPTION 3465 "These objects are required for OSPF systems." 3466 ::= { ospfGroups 8 } 3468 -- This object group is deprecated and replaced by ospfVirtIfGroup2 3470 ospfVirtIfGroup OBJECT-GROUP 3471 OBJECTS { 3472 ospfVirtIfAreaId, 3473 ospfVirtIfNeighbor, 3474 ospfVirtIfTransitDelay, 3475 ospfVirtIfRetransInterval, 3476 ospfVirtIfHelloInterval, 3477 ospfVirtIfRtrDeadInterval, 3478 ospfVirtIfState, 3479 ospfVirtIfEvents, 3480 ospfVirtIfAuthType, 3481 ospfVirtIfAuthKey, 3482 ospfVirtIfStatus 3483 } 3484 STATUS deprecated 3485 DESCRIPTION 3486 "These objects are required for OSPF systems." 3487 ::= { ospfGroups 9 } 3489 ospfNbrGroup OBJECT-GROUP 3490 OBJECTS { 3491 ospfNbrIpAddr, 3492 ospfNbrAddressLessIndex, 3493 ospfNbrRtrId, 3494 ospfNbrOptions, 3495 ospfNbrPriority, 3496 ospfNbrState, 3497 ospfNbrEvents, 3498 ospfNbrLsRetransQLen, 3499 ospfNbmaNbrStatus, 3500 ospfNbmaNbrPermanence, 3501 ospfNbrHelloSuppressed 3502 } 3504 STATUS current 3505 DESCRIPTION 3506 "These objects are required for OSPF systems." 3507 ::= { ospfGroups 10 } 3509 ospfVirtNbrGroup OBJECT-GROUP 3510 OBJECTS { 3511 ospfVirtNbrArea, 3512 ospfVirtNbrRtrId, 3513 ospfVirtNbrIpAddr, 3514 ospfVirtNbrOptions, 3515 ospfVirtNbrState, 3516 ospfVirtNbrEvents, 3517 ospfVirtNbrLsRetransQLen, 3518 ospfVirtNbrHelloSuppressed 3519 } 3520 STATUS current 3521 DESCRIPTION 3522 "These objects are required for OSPF systems." 3523 ::= { ospfGroups 11 } 3525 ospfExtLsdbGroup OBJECT-GROUP 3526 OBJECTS { 3527 ospfExtLsdbType, 3528 ospfExtLsdbLsid, 3529 ospfExtLsdbRouterId, 3530 ospfExtLsdbSequence, 3531 ospfExtLsdbAge, 3532 ospfExtLsdbChecksum, 3533 ospfExtLsdbAdvertisement 3534 } 3535 STATUS current 3536 DESCRIPTION 3537 "These objects are required for OSPF systems 3538 that display their link state database." 3539 ::= { ospfGroups 12 } 3541 ospfAreaAggregateGroup OBJECT-GROUP 3542 OBJECTS { 3543 ospfAreaAggregateAreaID, 3544 ospfAreaAggregateLsdbType, 3545 ospfAreaAggregateNet, 3546 ospfAreaAggregateMask, 3547 ospfAreaAggregateStatus, 3548 ospfAreaAggregateEffect 3549 } 3550 STATUS current 3551 DESCRIPTION 3552 "These objects are required for OSPF systems." 3553 ::= { ospfGroups 13 } 3555 ospfLocalLsdbGroup OBJECT-GROUP 3556 OBJECTS { 3557 ospfLocalLsdbIpAddress, 3558 ospfLocalLsdbAddressLessIf, 3559 ospfLocalLsdbType, 3560 ospfLocalLsdbLsid, 3561 ospfLocalLsdbRouterId, 3562 ospfLocalLsdbSequence, 3563 ospfLocalLsdbAge, 3564 ospfLocalLsdbChecksum, 3565 ospfLocalLsdbAdvertisement 3566 } 3567 STATUS current 3568 DESCRIPTION 3569 "These objects are required for OSPF systems 3570 that display their Link-Local link state databases 3571 for non-virtual links." 3572 ::= { ospfGroups 14 } 3574 ospfVirtLocalLsdbGroup OBJECT-GROUP 3575 OBJECTS { 3576 ospfVirtLocalLsdbTransitArea, 3577 ospfVirtLocalLsdbNeighbor, 3578 ospfVirtLocalLsdbType, 3579 ospfVirtLocalLsdbLsid, 3580 ospfVirtLocalLsdbRouterId, 3581 ospfVirtLocalLsdbSequence, 3582 ospfVirtLocalLsdbAge, 3583 ospfVirtLocalLsdbChecksum, 3584 ospfVirtLocalLsdbAdvertisement 3585 } 3586 STATUS current 3587 DESCRIPTION 3588 "These objects are required for OSPF systems 3589 that display their Link-Local link state databases 3590 for virtual links." 3591 ::= { ospfGroups 15 } 3593 ospfBasicGroup2 OBJECT-GROUP 3594 OBJECTS { 3595 ospfRouterId, 3596 ospfAdminStat, 3597 ospfVersionNumber, 3598 ospfAreaBdrRtrStatus, 3599 ospfASBdrRtrStatus, 3600 ospfExternLsaCount, 3601 ospfExternLsaCksumSum, 3602 ospfTOSSupport, 3603 ospfOriginateNewLsas, 3604 ospfRxNewLsas, 3605 ospfExtLsdbLimit, 3606 ospfMulticastExtensions, 3607 ospfExitOverflowInterval, 3608 ospfDemandExtensions, 3609 ospfRFC1583Compatibility, 3610 ospfOpaqueLsaSupport, 3611 ospfTrafficEngineeringSupport 3612 } 3613 STATUS current 3614 DESCRIPTION 3615 "These objects are required for OSPF systems." 3616 ::= { ospfGroups 16 } 3618 ospfAreaGroup2 OBJECT-GROUP 3619 OBJECTS { 3620 ospfAreaId, 3621 ospfImportAsExtern, 3622 ospfSpfRuns, 3623 ospfAreaBdrRtrCount, 3624 ospfAsBdrRtrCount, 3625 ospfAreaLsaCount, 3626 ospfAreaLsaCksumSum, 3627 ospfAreaSummary, 3628 ospfAreaStatus, 3629 ospfAreaNssaTranslatorRole, 3630 ospfAreaNssaTranslatorState, 3631 ospfAreaNssaTranslatorStabilityInterval, 3632 ospfAreaNssaTranslatorEvents 3633 } 3634 STATUS current 3635 DESCRIPTION 3636 "These objects are required for OSPF systems 3637 supporting areas. This statement is recommended 3638 for use. " 3639 ::= { ospfGroups 17 } 3641 ospfIfGroup2 OBJECT-GROUP 3642 OBJECTS { 3643 ospfIfIpAddress, 3644 ospfAddressLessIf, 3645 ospfIfAreaId, 3646 ospfIfType, 3647 ospfIfAdminStat, 3648 ospfIfRtrPriority, 3649 ospfIfTransitDelay, 3650 ospfIfRetransInterval, 3651 ospfIfHelloInterval, 3652 ospfIfRtrDeadInterval, 3653 ospfIfPollInterval, 3654 ospfIfState, 3655 ospfIfDesignatedRouter, 3656 ospfIfBackupDesignatedRouter, 3657 ospfIfEvents, 3658 ospfIfAuthType, 3659 ospfIfAuthKey, 3660 ospfIfStatus, 3661 ospfIfMulticastForwarding, 3662 ospfIfDemand, 3663 ospfIfLsaCount, 3664 ospfIfLsaCksumSum 3665 } 3666 STATUS current 3667 DESCRIPTION 3668 "These objects are required for OSPF systems." 3669 ::= { ospfGroups 18 } 3671 ospfVirtIfGroup2 OBJECT-GROUP 3672 OBJECTS { 3673 ospfVirtIfAreaId, 3674 ospfVirtIfNeighbor, 3675 ospfVirtIfTransitDelay, 3676 ospfVirtIfRetransInterval, 3677 ospfVirtIfHelloInterval, 3678 ospfVirtIfRtrDeadInterval, 3679 ospfVirtIfState, 3680 ospfVirtIfEvents, 3681 ospfVirtIfAuthType, 3682 ospfVirtIfAuthKey, 3683 ospfVirtIfStatus, 3684 ospfVirtIfLsaCount, 3685 ospfVirtIfLsaCksumSum 3686 } 3687 STATUS current 3688 DESCRIPTION 3689 "These objects are required for OSPF systems." 3690 ::= { ospfGroups 19 } 3692 -- This object group is included for SMI conformance. It is not a 3693 -- mandatory group for compliance with this MIB 3695 ospfObsoleteGroup OBJECT-GROUP 3696 OBJECTS { 3697 ospfAuthType 3698 } 3699 STATUS obsolete 3700 DESCRIPTION 3701 "These objects are obsolete and are no longer required for 3702 OSPF systems. They are placed into this group for SMI 3703 conformance" 3704 ::= { ospfGroups 20 } 3706 END 3707 4 OSPF Trap Overview 3709 4.1 Introduction 3711 OSPF is an event driven routing protocol, where an event can be a 3712 change in an OSPF interface's link-level status, the expiration of an 3713 OSPF timer or the reception of an OSPF protocol packet. Many of the 3714 actions that OSPF takes as a result of these events will result in a 3715 change of the routing topology. 3717 As routing topologies become large and complex it is often difficult 3718 to locate the source of a topology change or unpredicted routing path 3719 by polling a large number or routers. Because of the difficulty of 3720 polling a large number of devices, a more prudent approach is for 3721 devices to notify a network manager of potentially critical OSPF 3722 events using SNMP traps. 3724 This section defines a set of traps, objects and mechanisms to 3725 enhance the ability to manage IP internetworks which use OSPF as its 3726 IGP. It is an optional but very useful extension to the OSPF MIB. 3728 4.2 Approach 3730 The mechanism for sending traps is straight-forward. When an 3731 exception event occurs, the application notifies the local agent who 3732 sends a trap to the appropriate SNMP management stations. The 3733 message includes the trap type and may include a list of trap 3734 specific variables. Section 5 gives the trap 3735 definitions which includes the variable lists. The router ID 3736 of the originator of the trap is included in the variable list 3737 so that the network manager may easily determine the source of the 3738 trap. 3740 To limit the frequency of OSPF traps, the following additional 3741 mechanisms are suggested. 3743 4.3 Ignoring Initial Activity 3745 The majority of critical events occur when OSPF is enabled on a 3746 router, at which time the designated router is elected and neighbor 3747 adjacencies are formed. During this initial period a potential 3748 flood of traps is unnecessary since the events are expected. To avoid 3749 unnecessary traps, a router should not originate expected OSPF 3750 interface related traps until two of that interface's dead timer 3751 intervals have elapsed. The expected OSPF interface traps are 3752 ospfIfStateChange, ospfVirtIfStateChange, ospfNbrStateChange, 3753 ospfVirtNbrStateChange, ospfTxRetranmit and ospfVirtIfTxRetransmit. 3754 Additionally, ospfMaxAgeLsa and ospfOriginateLsa traps should not be 3755 originated until two dead timer intervals have elapsed where the dead 3756 timer interval used should be the dead timer with the smallest value. 3758 4.4 Throttling Traps 3760 The mechanism for throttling the traps is similar to the mechanism 3761 explained in RFC 1224 [24]. The basic premise of the throttling 3762 mechanism is that of a sliding window, defined in seconds and an 3763 upper bound on the number of traps that may be generated within this 3764 window. Note that unlike RFC 1224, traps are not sent to inform the 3765 network manager that the throttling mechanism has kicked in. 3767 A single window should be used to throttle all OSPF traps types 3768 except for the ospfLsdbOverflow and the ospfLsdbApproachingOverflow 3769 trap which should not be throttled. For example, with a window time 3770 of 3, an upper bound of 3, and events to cause trap types 1,3,5 and 7 3771 (4 traps within a 3 second period), the type 7 (the 4th) trap should 3772 not be generated. 3774 Appropriate values are 7 traps with a window time of 10 seconds. 3776 4.5 One Trap Per OSPF Event 3778 Several of the traps defined in section 5 are 3779 generated as the result of finding an unusual condition while 3780 parsing an OSPF packet or a processing a timer event. There 3781 may be more than one unusual condition detected while handling 3782 the event. For example, a link-state update packet may contain 3783 several retransmitted link-state advertisements (LSAs), or a 3784 retransmitted database description packet may contain several 3785 database description entries. To limit the number of traps and 3786 variables, OSPF should generate at most one trap per OSPF event. 3787 Only the variables associated with the first unusual condition 3788 should be included with the trap. Similarly, if more than 3789 one type of unusual condition is encountered while parsing the 3790 packet, only the first event will generate a trap. 3792 4.6 Polling Event Counters 3794 Many of the tables in the OSPF MIB contain generalized event 3795 counters. By enabling the traps defined in this document a network 3796 manager can obtain more specific information about these events. A 3797 network manager may want to poll these event counters and enable 3798 specific OSPF traps when a particular counter starts increasing 3799 abnormally. 3801 The following table shows the relationship between the event counters 3802 defined in the OSPF MIB and the trap types defined in section x. 3804 Counter32 Trap Type 3805 ----------------------- ------------------------ 3806 ospfOriginateNewLsas ospfOriginateLsa 3807 ospfIfEvents ospfIfStateChange 3808 ospfConfigError 3809 ospfIfAuthFailure 3810 ospfRxBadPacket 3811 ospfTxRetransmit 3812 ospfVirtIfEvents ospfVirtIfStateChange 3813 ospfVirtIfConfigError 3814 ospfVirtIfAuthFailure 3815 ospfVirtIfRxBadPacket 3816 ospfVirtIfTxRetransmit 3817 ospfNbrEvents ospfNbrStateChange 3818 ospfVirtNbrEvents ospfVirtNbrStateChange 3819 ospfExternLSACount ospfLsdbApproachingOverflow 3820 ospfExternLSACount ospfLsdbOverflow 3822 OSPF-TRAP-MIB DEFINITIONS ::= BEGIN 3824 IMPORTS 3825 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress 3826 FROM SNMPv2-SMI 3827 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 3828 FROM SNMPv2-CONF 3829 ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState, 3830 ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState, 3831 ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId, 3832 ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, 3833 ospfVirtNbrState, ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, 3834 ospfLsdbAreaId, ospfExtLsdbLimit, ospf, ospfAreaId, 3835 ospfAreaNssaTranslatorState 3836 FROM OSPF-MIB; 3838 ospfTrap MODULE-IDENTITY 3839 LAST-UPDATED "200010201225Z" -- Fri Oct 20 12:25:50 GMT 3840 -- 2000 3841 ORGANIZATION "IETF OSPF Working Group" 3842 CONTACT-INFO 3843 " Spencer Giacalone 3844 Postal: Predictive Systems 3845 25a Vreeland Road 3846 Florham Park, NJ 07932 3847 Tel: +1 (973) 301-5695 3848 E-Mail: spencer.giacalone@predictive.com 3850 Dan Joyal 3851 Postal: Quantum Bridge Communications 3852 1 High Street 3853 North Andover, MA 01845 3854 Tel: +1 (978) 688-9100 3855 E-Mail: djoyal@quantumbridge.com" 3856 DESCRIPTION 3857 "The MIB module to describe traps for the OSPF 3858 Version 2 Protocol." 3859 REVISION "200011201015Z" -- Mon Nov 20 10:15:00 GMT 2000 3860 DESCRIPTION 3861 "Updated for latest version of OSPFv2" 3862 REVISION "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995 3863 DESCRIPTION 3864 "The initial SMIv2 revision of this MIB module, published 3865 in RFC1850." 3866 ::= { ospf 16 } 3868 -- Trap Support Objects 3870 -- The following are support objects for the OSPF traps. 3872 ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 } 3873 ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 } 3875 ospfSetTrap OBJECT-TYPE 3876 SYNTAX OCTET STRING (SIZE(4)) 3877 MAX-ACCESS read-write 3878 STATUS current 3879 DESCRIPTION 3880 "A four-octet string serving as a bit map for 3881 the trap events defined by the OSPF traps. This 3882 object is used to enable and disable specific 3883 OSPF traps where a 1 in the bit field 3884 represents enabled. The right-most bit (least 3885 significant) represents trap 0." 3886 ::= { ospfTrapControl 1 } 3888 ospfConfigErrorType OBJECT-TYPE 3889 SYNTAX INTEGER { 3890 badVersion (1), 3891 areaMismatch (2), 3892 unknownNbmaNbr (3), -- Router is DR eligible 3893 unknownVirtualNbr (4), 3894 authTypeMismatch(5), 3895 authFailure (6), 3896 netMaskMismatch (7), 3897 helloIntervalMismatch (8), 3898 deadIntervalMismatch (9), 3899 optionMismatch (10), 3900 mtuMismatch (11), 3901 noError (12) } 3902 MAX-ACCESS read-only 3903 STATUS current 3904 DESCRIPTION 3905 "Potential types of configuration conflicts. 3906 Used by the ospfConfigError and ospfConfigVir- 3907 tError traps. When the last value of a trap 3908 using this object is needed, but no traps of 3909 that type have been sent, this value pertaining 3910 to this object should be returned as noError" 3911 ::= { ospfTrapControl 2 } 3913 ospfPacketType OBJECT-TYPE 3914 SYNTAX INTEGER { 3915 hello (1), 3916 dbDescript (2), 3917 lsReq (3), 3918 lsUpdate (4), 3919 lsAck (5), 3920 nullPacket (6) } 3921 MAX-ACCESS read-only 3922 STATUS current 3923 DESCRIPTION 3924 "OSPF packet types. When the last value of a trap 3925 using this object is needed, but no traps of 3926 that type have been sent, this value pertaining 3927 to this object should be returned as nullPacket" 3928 ::= { ospfTrapControl 3 } 3930 ospfPacketSrc OBJECT-TYPE 3931 SYNTAX IpAddress 3932 MAX-ACCESS read-only 3933 STATUS current 3934 DESCRIPTION 3935 "The IP address of an inbound packet that can- 3936 not be identified by a neighbor instance. When 3937 the last value of a trap using this object is 3938 needed, but no traps of that type have been sent, 3939 this value pertaining to this object should 3940 be returned as 0.0.0.0" 3941 ::= { ospfTrapControl 4 } 3943 -- Traps 3945 ospfVirtIfStateChange NOTIFICATION-TYPE 3946 OBJECTS { ospfRouterId, -- The originator of the trap 3947 ospfVirtIfAreaId, 3948 ospfVirtIfNeighbor, 3949 ospfVirtIfState -- The new state 3950 } 3951 STATUS current 3952 DESCRIPTION 3953 "An ospfIfStateChange trap signifies that there 3954 has been a change in the state of an OSPF vir- 3955 tual interface. 3957 This trap should be generated when the inter- 3958 face state regresses (e.g., goes from Point- 3959 to-Point to Down) or progresses to a terminal 3960 state (i.e., Point-to-Point)." 3961 ::= { ospfTraps 1 } 3963 ospfNbrStateChange NOTIFICATION-TYPE 3964 OBJECTS { ospfRouterId, -- The originator of the trap 3965 ospfNbrIpAddr, 3966 ospfNbrAddressLessIndex, 3967 ospfNbrRtrId, 3968 ospfNbrState -- The new state 3969 } 3970 STATUS current 3971 DESCRIPTION 3972 "An ospfNbrStateChange trap signifies that 3973 there has been a change in the state of a non- 3974 virtual OSPF neighbor. This trap should be 3975 generated when the neighbor state regresses 3976 (e.g., goes from Attempt or Full to 1-Way or 3977 Down) or progresses to a terminal state (e.g., 3978 2-Way or Full). When an neighbor transitions 3979 from or to Full on non-broadcast multi-access 3980 and broadcast networks, the trap should be gen- 3981 erated by the designated router. A designated 3982 router transitioning to Down will be noted by 3983 ospfIfStateChange." 3984 ::= { ospfTraps 2 } 3986 ospfVirtNbrStateChange NOTIFICATION-TYPE 3987 OBJECTS { ospfRouterId, -- The originator of the trap 3988 ospfVirtNbrArea, 3989 ospfVirtNbrRtrId, 3990 ospfVirtNbrState -- The new state 3991 } 3992 STATUS current 3993 DESCRIPTION 3994 "An ospfIfStateChange trap signifies that there 3995 has been a change in the state of an OSPF vir- 3996 tual neighbor. This trap should be generated 3997 when the neighbor state regresses (e.g., goes 3998 from Attempt or Full to 1-Way or Down) or 3999 progresses to a terminal state (e.g., Full)." 4000 ::= { ospfTraps 3 } 4002 ospfIfConfigError NOTIFICATION-TYPE 4003 OBJECTS { ospfRouterId, -- The originator of the trap 4004 ospfIfIpAddress, 4005 ospfAddressLessIf, 4006 ospfPacketSrc, -- The source IP address 4007 ospfConfigErrorType, -- Type of error 4008 ospfPacketType 4009 } 4010 STATUS current 4011 DESCRIPTION 4012 "An ospfIfConfigError trap signifies that a 4013 packet has been received on a non-virtual in- 4014 terface from a router whose configuration 4015 parameters conflict with this router's confi- 4016 guration parameters. Note that the event op- 4017 tionMismatch should cause a trap only if it 4018 prevents an adjacency from forming." 4019 ::= { ospfTraps 4 } 4021 ospfVirtIfConfigError NOTIFICATION-TYPE 4022 OBJECTS { ospfRouterId, -- The originator of the trap 4023 ospfVirtIfAreaId, 4024 ospfVirtIfNeighbor, 4025 ospfConfigErrorType, -- Type of error 4026 ospfPacketType 4027 } 4028 STATUS current 4029 DESCRIPTION 4030 "An ospfConfigError trap signifies that a pack- 4031 et has been received on a virtual interface 4032 from a router whose configuration parameters 4033 conflict with this router's configuration 4034 parameters. Note that the event optionMismatch 4035 should cause a trap only if it prevents an ad- 4036 jacency from forming." 4037 ::= { ospfTraps 5 } 4039 ospfIfAuthFailure NOTIFICATION-TYPE 4040 OBJECTS { ospfRouterId, -- The originator of the trap 4041 ospfIfIpAddress, 4042 ospfAddressLessIf, 4043 ospfPacketSrc, -- The source IP address 4044 ospfConfigErrorType, -- authTypeMismatch or 4045 -- authFailure 4046 ospfPacketType 4047 } 4048 STATUS current 4049 DESCRIPTION 4050 "An ospfIfAuthFailure trap signifies that a 4051 packet has been received on a non-virtual in- 4052 terface from a router whose authentication key 4053 or authentication type conflicts with this 4054 router's authentication key or authentication 4055 type." 4056 ::= { ospfTraps 6 } 4058 ospfVirtIfAuthFailure NOTIFICATION-TYPE 4059 OBJECTS { ospfRouterId, -- The originator of the trap 4060 ospfVirtIfAreaId, 4061 ospfVirtIfNeighbor, 4062 ospfConfigErrorType, -- authTypeMismatch or 4063 -- authFailure 4064 ospfPacketType 4065 } 4066 STATUS current 4067 DESCRIPTION 4068 "An ospfVirtIfAuthFailure trap signifies that a 4069 packet has been received on a virtual interface 4070 from a router whose authentication key or au- 4071 thentication type conflicts with this router's 4072 authentication key or authentication type." 4073 ::= { ospfTraps 7 } 4075 ospfIfRxBadPacket NOTIFICATION-TYPE 4076 OBJECTS { ospfRouterId, -- The originator of the trap 4077 ospfIfIpAddress, 4078 ospfAddressLessIf, 4079 ospfPacketSrc, -- The source IP address 4080 ospfPacketType 4081 } 4082 STATUS current 4083 DESCRIPTION 4084 "An ospfIfRxBadPacket trap signifies that an 4085 OSPF packet has been received on a non-virtual 4086 interface that cannot be parsed." 4087 ::= { ospfTraps 8 } 4089 ospfVirtIfRxBadPacket NOTIFICATION-TYPE 4090 OBJECTS { ospfRouterId, -- The originator of the trap 4091 ospfVirtIfAreaId, 4092 ospfVirtIfNeighbor, 4093 ospfPacketType 4094 } 4095 STATUS current 4096 DESCRIPTION 4097 "An ospfRxBadPacket trap signifies that an OSPF 4098 packet has been received on a virtual interface 4099 that cannot be parsed." 4100 ::= { ospfTraps 9 } 4102 ospfTxRetransmit NOTIFICATION-TYPE 4103 OBJECTS { ospfRouterId, -- The originator of the trap 4104 ospfIfIpAddress, 4105 ospfAddressLessIf, 4106 ospfNbrRtrId, -- Destination 4107 ospfPacketType, 4108 ospfLsdbType, 4109 ospfLsdbLsid, 4110 ospfLsdbRouterId 4111 } 4112 STATUS current 4113 DESCRIPTION 4114 "An ospfTxRetransmit trap signifies than an 4115 OSPF packet has been retransmitted on a non- 4116 virtual interface. All packets that may be re- 4117 transmitted are associated with an LSDB entry. 4118 The LS type, LS ID, and Router ID are used to 4119 identify the LSDB entry." 4120 ::= { ospfTraps 10 } 4122 ospfVirtIfTxRetransmit NOTIFICATION-TYPE 4123 OBJECTS { ospfRouterId, -- The originator of the trap 4124 ospfVirtIfAreaId, 4125 ospfVirtIfNeighbor, 4126 ospfPacketType, 4127 ospfLsdbType, 4128 ospfLsdbLsid, 4129 ospfLsdbRouterId 4130 } 4131 STATUS current 4132 DESCRIPTION 4133 "An ospfTxRetransmit trap signifies than an 4134 OSPF packet has been retransmitted on a virtual 4135 interface. All packets that may be retransmit- 4136 ted are associated with an LSDB entry. The LS 4137 type, LS ID, and Router ID are used to identify 4138 the LSDB entry." 4139 ::= { ospfTraps 11 } 4141 ospfOriginateLsa NOTIFICATION-TYPE 4142 OBJECTS { ospfRouterId, -- The originator of the trap 4143 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 4144 ospfLsdbType, 4145 ospfLsdbLsid, 4146 ospfLsdbRouterId 4147 } 4148 STATUS current 4149 DESCRIPTION 4150 "An ospfOriginateLsa trap signifies that a new 4151 LSA has been originated by this router. This 4152 trap should not be invoked for simple refreshes 4153 of LSAs (which happens every 30 minutes), but 4154 instead will only be invoked when an LSA is 4155 (re)originated due to a topology change. Addi- 4156 tionally, this trap does not include LSAs that 4157 are being flushed because they have reached 4158 MaxAge." 4159 ::= { ospfTraps 12 } 4161 ospfMaxAgeLsa NOTIFICATION-TYPE 4162 OBJECTS { ospfRouterId, -- The originator of the trap 4163 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 4164 ospfLsdbType, 4165 ospfLsdbLsid, 4166 ospfLsdbRouterId 4167 } 4168 STATUS current 4169 DESCRIPTION 4170 "An ospfMaxAgeLsa trap signifies that one of 4171 the LSA in the router's link-state database has 4172 aged to MaxAge." 4173 ::= { ospfTraps 13 } 4175 ospfLsdbOverflow NOTIFICATION-TYPE 4176 OBJECTS { ospfRouterId, -- The originator of the trap 4177 ospfExtLsdbLimit 4178 } 4179 STATUS current 4180 DESCRIPTION 4181 "An ospfLsdbOverflow trap signifies that the 4182 number of LSAs in the router's link-state data- 4183 base has exceeded ospfExtLsdbLimit." 4184 ::= { ospfTraps 14 } 4186 ospfLsdbApproachingOverflow NOTIFICATION-TYPE 4187 OBJECTS { ospfRouterId, -- The originator of the trap 4188 ospfExtLsdbLimit 4189 } 4190 STATUS current 4191 DESCRIPTION 4192 "An ospfLsdbApproachingOverflow trap signifies 4193 that the number of LSAs in the router's link- 4194 state database has exceeded ninety percent of 4195 ospfExtLsdbLimit." 4196 ::= { ospfTraps 15 } 4198 ospfIfStateChange NOTIFICATION-TYPE 4199 OBJECTS { ospfRouterId, -- The originator of the trap 4200 ospfIfIpAddress, 4201 ospfAddressLessIf, 4202 ospfIfState -- The new state 4203 } 4204 STATUS current 4205 DESCRIPTION 4206 "An ospfIfStateChange trap signifies that there 4207 has been a change in the state of a non-virtual 4208 OSPF interface. This trap should be generated 4209 when the interface state regresses (e.g., goes 4210 from Dr to Down) or progresses to a terminal 4211 state (i.e., Point-to-Point, DR Other, Dr, or 4212 Backup)." 4213 ::= { ospfTraps 16 } 4215 ospfNssaTranslatorStatusChange NOTIFICATION-TYPE 4216 OBJECTS { ospfRouterId, -- The originator of the trap 4217 ospfAreaId, 4218 ospfAreaNssaTranslatorState -- The current translation 4219 -- status 4220 } 4221 STATUS current 4222 DESCRIPTION 4223 "An ospfNssaTranslatorStatusChange trap indicates that there 4224 has been a change in the router's ability to translate OSPF 4225 type-7 LSAs into OSPF type-5 LSAs. This trap should be 4226 generated when the Translator Status transitions from or to 4227 any defined status on a per area basis." 4228 ::= { ospfTraps 17 } 4230 -- conformance information 4232 ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 } 4234 ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 } 4235 ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 } 4237 -- compliance statements 4239 ospfTrapCompliance MODULE-COMPLIANCE 4240 STATUS obsolete 4241 DESCRIPTION 4242 "The compliance statement " 4243 MODULE -- this module 4244 MANDATORY-GROUPS { ospfTrapControlGroup } 4246 GROUP ospfTrapControlGroup 4247 DESCRIPTION 4248 "This group is optional but recommended for all 4249 OSPF systems" 4250 ::= { ospfTrapCompliances 1 } 4252 ospfTrapCompliance2 MODULE-COMPLIANCE 4253 STATUS current 4254 DESCRIPTION 4255 "The compliance statement" 4256 MODULE -- this module 4257 MANDATORY-GROUPS { ospfTrapControlGroup, ospfTrapEventGroup } 4258 OBJECT ospfConfigErrorType 4259 MIN-ACCESS accessible-for-notify 4260 DESCRIPTION 4261 "This object is only required to be supplied within 4262 notifications." 4263 OBJECT ospfPacketType 4264 MIN-ACCESS accessible-for-notify 4265 DESCRIPTION 4266 "This object is only required to be supplied within 4267 notifications." 4268 OBJECT ospfPacketSrc 4269 MIN-ACCESS accessible-for-notify 4270 DESCRIPTION 4271 "This object is only required to be supplied within 4272 notifications." 4273 ::= { ospfTrapCompliances 2 } 4275 -- units of conformance 4277 ospfTrapControlGroup OBJECT-GROUP 4278 OBJECTS { ospfSetTrap, 4279 ospfConfigErrorType, 4280 ospfPacketType, 4281 ospfPacketSrc 4282 } 4283 STATUS current 4284 DESCRIPTION 4285 "These objects are required to control traps 4286 from OSPF systems." 4287 ::= { ospfTrapGroups 1 } 4289 ospfTrapEventGroup NOTIFICATION-GROUP 4290 NOTIFICATIONS { 4291 ospfVirtIfStateChange, 4292 ospfNbrStateChange, 4293 ospfVirtNbrStateChange, 4294 ospfIfConfigError, 4295 ospfVirtIfConfigError, 4296 ospfIfAuthFailure, 4297 ospfVirtIfAuthFailure, 4298 ospfIfRxBadPacket, 4299 ospfVirtIfRxBadPacket, 4300 ospfTxRetransmit, 4301 ospfVirtIfTxRetransmit, 4302 ospfOriginateLsa, 4303 ospfMaxAgeLsa, 4304 ospfLsdbOverflow, 4305 ospfLsdbApproachingOverflow, 4306 ospfIfStateChange, 4307 ospfNssaTranslatorStatusChange 4308 } 4309 STATUS current 4310 DESCRIPTION 4311 "A grouping of OSPF Trap Events, as specified 4312 in NOTIFICATION-TYPE constructs." 4313 ::= { ospfTrapGroups 2 } 4315 END 4316 6 Acknowledgements 4318 This document was produced by the OSPF Working Group, and is 4319 based on the MIB for OSPF version 2 by Rob Coltun and Fred 4320 Baker [18]. 4322 The Authors acknowledge the following individuals: 4324 - John Moy, Sycamore Networks 4326 - Rob Coltun, RedBack Networks 4328 -Randall Atkinson, Extreme Networks 4330 -David T Perkins, SNMPinfo 4332 -Ken Shipman, Unisphere Networks 4334 7 References 4336 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An 4337 Architecture for Describing SNMP Management Frameworks", 4338 RFC 2571, April 1999 4339 [2] Rose, M., and K. McCloghrie, "Structure and 4340 Identification of Management Information for TCP/IP-based 4341 Internets", STD 16, RFC 1155, May 1990 4343 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 4344 STD 16, RFC 1212, March 1991 4346 [4] M. Rose, "A Convention for Defining Traps for use with 4347 the SNMP", RFC 1215, March 1991 4349 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4350 Rose, M., and S. Waldbusser, "Structure of Management 4351 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 4352 1999 4354 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4355 Rose, M., and S. Waldbusser, "Textual Conventions for 4356 SMIv2", STD 58, RFC 2579, April 1999 4358 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4359 Rose, M., and S. Waldbusser, "Conformance Statements for 4360 SMIv2", STD 58, RFC 2580, April 1999 4362 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 4363 "Simple Network Management Protocol", STD 15, RFC 1157, 4364 May 1990. 4366 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4367 "Introduction to Community-based SNMPv2", RFC 1901, 4368 January 1996. 4370 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4371 "Transport Mappings for Version 2 of the Simple Network 4372 Management Protocol (SNMPv2)", RFC 1906, January 1996. 4374 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, 4375 "Message Processing and Dispatching for the Simple 4376 Network Management Protocol (SNMP)", RFC 2572, April 1999 4378 [21] Moy, J., "OSPF Version 2", RFC 2328, Ascend 4379 Communications, Inc., April 1998. 4381 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4382 "Protocol Operations for Version 2 of the Simple Network 4383 Management Protocol (SNMPv2)", RFC 1905, January 1996. 4385 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 4386 Applications", RFC 2573, April 1999 4388 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 4389 Access Control Model (VACM) for the Simple Network 4390 Management Protocol (SNMP)", RFC 2575, April 1999 4392 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, 4393 "Introduction to Version 3 of the Internet-standard 4394 Network Management Framework", RFC 2570, April 1999 4396 [17] Deering, S., and R. Hinden, "Internet Protocol, Version 6 4397 (IPv6) Specification", RFC 2460, December 1998. 4399 [18] Baker, F., and Coltun, R., "OSPF Version 2 Management 4400 Information Base", RFC 1850, Cisco Systems, FORE Systems, 4401 November 1995. 4403 [19] Cerf, V., "IAB Recommendations for the Development of Internet 4404 Network Management Standards", RFC 1052, NRI, April 1988. 4406 [20] Cerf, V., "Report of the Second Ad Hoc Network Management Review 4407 Group", RFC 1109, NRI, August 1989. 4409 [21] Rose M., Editor, "Management Information Base for Network 4410 Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, 4411 Performance Systems International, March 1991. 4413 [22] Information processing systems - Open Systems Interconnection - 4414 Specification of Abstract Syntax Notation One (ASN.1), 4415 International Organization for Standardization, International 4416 Standard 8824, December 1987. 4418 [23] Information processing systems - Open Systems Interconnection - 4419 Specification of Basic Encoding Rules for Abstract Notation One 4420 (ASN.1), International Organization for Standardization, 4421 International Standard 8825, December 1987. 4423 [24] Steinberg, L., "Techniques for Managing Asynchronously Generated 4424 Alerts", RFC 1224, IBM Corporation, May 1991. 4426 [25] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, 4427 Inc., September 1993. 4429 A TOS Support 4431 For backward compatibility with previous versions of the OSPF 4432 MIB specification, TOS-specific information has been retained 4433 in this document, though the TOS routing option has been 4434 deleted from OSPF [RFC 2178]. 4436 B Changes from RFC 1850 4438 This section documents the differences between this memo and RFC 4439 1850. 4441 B.1 RFC 1583 Compatibility 4443 Added object ospfRFC1583Compatibility to ospfGeneralGroup 4444 to indicate support with "RFC 1583 Compatibility" This object 4445 has DEFVAL of "enabled". 4447 B.2 OSPF Traffic Engineering Support 4449 Added object ospfTrafficEngineeringSuport to ospfGeneralGroup 4450 to indicate support of OSPF traffic engineering. 4452 B.3 OSPF NSSA Enhancement Support 4454 Added new objects to OspfAreaTable including: 4456 -ospfAreaNssaTranslatorRole to indicate the configured 4457 NSSA translation role. 4459 -ospfAreaNssaTranslatorState to indicate the current 4460 NSSA translation role. 4462 -ospfAreaNssaTranslatorStabilityInterval to 4463 indicate time to continue to perform at current 4464 translation status. 4466 -ospfAreaNssaTranslatorEvents to indicate the number of 4467 times OSPF Translation State has changed. 4469 Added new object ospfNssaTranslatorStatusChange 4470 to ospfTraps in OSPF-TRAP-MIB DEFINITIONS. 4472 Added ospfAreaId to IMPORTS in OSPF-TRAP-MIB DEFINITIONS to support 4473 ospfNssaTranslatorStatusChange. 4475 Added ospfAreaExtNssaTranslatorStatus to IMPORTS in OSPF-TRAP-MIB 4476 DEFINITIONS to support ospfNssaTranslatorStatusChange. 4478 Modified the DESCRIPTION clause of the ospfAreaSummary object in 4479 the ospfAreaTable to indicate support for NSSA. 4481 Modified the DESCRIPTION clause of the ospfImportAsExtern object in 4482 the ospfAreaTable for clarity. 4484 B.4 Opaque LSA Support 4486 Added object ospfOpaqueLsaSupport to ospfGeneralGroup 4487 to indicate support of OSPF Opaque LSAs. 4489 Created ospfLocalLsdbTable, for Link-local (type-9) LSA support. 4490 This table is indexed by: 4492 -ospflocalLsdbIpAddress 4494 -ospfLocalLsdbAddressLessIf 4496 -ospfLocalLsdbType 4498 -ospfLocalLsdbLsid 4500 -ospfLocalLsdbRouterId 4502 ospfLocalLsdbTable contains the following (columnar) objects: 4504 -ospfLocalLsdbSequence, to indicate LSA instance 4506 -ospfLocalLsdbAge 4508 -ospfLocalLsdbChecksum 4510 -ospfLocalLsdbAdvertisement, containing the entire LSA 4512 Created ospfVirLocalLsdbTable, for Link-local (type-9) LSA support 4513 on virtual links. This table is indexed by: 4515 -ospfVirtLocalLsdbTransitArea 4517 -ospfVirtLocalLsdbNeighbor, to indicate the router ID of the 4518 virtual neighbor 4520 -ospfVirLocalLsdbType 4522 -ospfVirLocalLsdbLsid 4524 -ospfVirLocalLsdbRouterId 4526 ospfVirLocalLsdbTable contains the following (columnar) objects: 4528 -ospfVirLocalLsdbSequence, to indicate LSA instance 4530 -ospfVirLocalLsdbAge 4532 -ospfVirLocalLsdbChecksum 4534 -ospfVirLocalLsdbAdvertisement, containing the entire LSA 4536 Added objects to ospfIfTable to support Link-local (type-9) LSAs, 4537 including: 4539 -ospfIfLsaCount 4541 -ospfIfLsaCksumSum, to indicate the sum of the type-9 link- 4542 state advertisement checksums on this interface 4544 Added objects to ospfVirIfTable, to support Link-local (type-9) LSAs 4545 on virtual links, including: 4547 -ospfVirIfLsaCount 4549 -ospfVirIfLsaCksumSum, to indicate the sum of the type-9 link- 4550 state advertisement checksums on this link. 4552 To support area scope (type-10) LSAs, the enumeration 4553 areaOpaqueLink (10) was added to ospfLsdbType in the ospfLsdbTable. 4555 To support AS scope (type-11) LSAs, the enumeration 4556 asOpaqueLink (11) was added to ospfExtLsdbType in the 4557 ospfExtLsdbTable. 4559 B.5 OSPF Compliances 4561 Compliance statements were depreciated as needed due to the fact that 4562 many new items have been added to the MIB. These statements include: 4564 -ospfCompliance 4566 New compliance statements were added as needed to replace deprecated 4567 statements. These Statements include: 4569 -ospfCompliance2 4571 Conformance groups were depreciated as needed due to the fact that 4572 many new items have been added to the MIB. These groups include: 4574 -ospfBasicGroup 4576 -ospfAreaGroup 4578 -ospfIfGroup 4580 -ospfVirtIfGroup 4582 New conformance groups were added as needed to replace deprecated 4583 groups. These groups include: 4585 -ospfBasicGroup2 4587 -ospfAreaGroup2 4589 -ospfIfGroup2 4591 -ospfVirtIfGroup2 4593 Added completely new conformance groups as needed, including: 4595 -ospfLocalLsdbGroup, which specifies support for link local (type- 4596 9) LSAs. 4598 -ospfVirtLocalLsdbGroup, which specifies support for link local 4599 (type-9) LSAs on virtual links. 4601 -ospfObsoleteGroup, for obsolete objects and SMI compatibility. 4603 B.6 OSPF Authentication and Security 4604 As there has been significant concern in the community regarding 4605 cascading security vulnerabilities, the following changes have been 4606 incorporated: 4608 -Modified the DESCRIPTION clause of ospfIfAuthKey due to 4609 security concerns, and to increase clarity 4611 -Modified the DESCRIPTION clause of ospfVirtIfAuthKey due to 4612 security concerns, and to increase clarity 4614 -Modified the DESCRIPTION clause of ospfIfAuthType due to 4615 security concerns, and to increase clarity 4617 -Modified the DESCRIPTION clause of ospfVirtIfType due to 4618 security concerns, and to increase clarity 4620 -Modified the OSPF MIB MODULE DESCRIPTION due to security 4621 concerns and to include a reference to the security 4622 considerations section in this document that will transcend 4623 compilation 4625 -Modified the security considerations section to provide 4626 detail 4628 B.7 OSPF Trap MIB 4630 Added ospfTrapEventGroup. 4632 Added importation of NOTIFICATION-GROUP. 4634 Changed the STATUS of the ospfTrapCompliance 4635 MODULE-COMPLIANCE construct to obsolete. 4637 Added ospfTrapCompliance2 MODULE-COMPLIANCE construct 4638 which replaces ospfTrapCompliance. OspfTrapCompliance 4639 includes an updated MANDATORY-GROUPS clause and new 4640 MIN-ACCESS specifications. 4642 Added mtuMismatch enumeration to ospfConfigErrorType 4643 object in ospfTrapControl to imply MTU mismatch trap generation. 4644 in ospfIfConfigError. 4646 Added noError enumeration to ospfConfigErrorType 4647 object for situations when traps are requested, but none 4648 have been sent. Updated the DESCRIPTION clause accordingly. 4650 Added nullPacket enumeration to ospfPacketType object 4651 for situations when traps are requested, but none 4652 have been sent. Updated the DESCRIPTION clause accordingly. 4654 Updated the DESCRIPTION clause of ospfPacketSrc for 4655 situations when traps are requested, but none have been sent.. 4657 B.8 Miscellaneous 4659 Various sections, have been moved and or modified for clarity. 4660 Most of these changes are semantic in nature, and include, 4661 but are not limited to: 4663 -The OSPF Overview section's format was revised. Unneeded 4664 information was removed. Removed information includes OSPF TOS 4665 default values. 4667 -The Trap Overview section's format and working were revised. 4668 Unneeded information was removed. 4670 -Modified the DESCRIPTION clause of "Status" "TEXTUAL-CONVENTION" 4671 for clarity 4673 -The updates section was moved from the Overview to an appendix 4675 -Updated "REFERENCE" clauses in all objects, as needed 4677 -Modified the SEQUENCE of the OspfIfTable to reflect the true 4678 order of the objects in the Table 4680 -Modified the DESCRIPTION clause of all row management objects 4681 for clarity 4683 Changed the MAX-ACCESS clause of ospfHostStatus to "read-create" 4685 Added importation of InterfaceIndexOrZero from IF-MIB. This TEXTUAL- 4686 CONVENTION will replace the InterfaceIndex TEXTUAL-CONVENTION. 4688 Changed the SYNTAX clause of ospfNbrAddressLessIndex to use the 4689 semantically identical InterfaceIndexOrZero TEXTUAL-CONVENTION, as 4690 permitted by the SMI. 4692 Changed the STATUS clause of the TEXTUAL-CONVENTION InterfaceIndex 4693 to obsolete and modified the DESCRIPTION accordingly. 4695 Changed the SYNTAX clause of ospfAddressLessIf to use the 4696 semantically identical InterfaceIndexOrZero TEXTUAL-CONVENTION, as 4697 permitted by the SMI. 4699 Changed the SYNTAX clause of ospfIfMetricAddressLessIf to use the 4700 semantically identical InterfaceIndexOrZero TEXTUAL-CONVENTION, as 4701 permitted by the SMI. 4703 Changed importation of mib-2 from RFC1213-MIB to SNMPv2-SMI 4705 C Security Considerations 4707 There are a number of management objects defined in this MIB that 4708 have a MAX-ACCESS clause of read-write and/or read-create. Such 4709 objects may be considered sensitive or vulnerable in some network 4710 environments. The support for SET operations in a non-secure 4711 environment without proper protection can have a negative effect on 4712 network operations. 4714 It is recommended that attention be specifically given to 4715 implementing the MAX-ACCESS clause in a number of objects, including 4716 ospfIfAuthKey, ospfIfAuthType, ospfVirtIfAuthKey, and 4717 ospfVirtIfAuthType in scenarios that DO NOT use SNMPv3 strong 4718 security (i.e. authentication and encryption). Extreme caution must 4719 be used to minimize the risk of cascading security vulnerabilities 4720 when SNMPv3 strong security is not used. When SNMPv3 strong security 4721 is not used, these objects should have access of read-only, not read- 4722 create. 4724 SNMPv1 by itself is not a secure environment. Even if the network 4725 itself is secure (for example by using IPSec), even then, there is no 4726 control as to who on the secure network is allowed to access and 4727 GET/SET (read/change/create/delete) the objects in this MIB. 4729 It is recommended that the implementers consider the security 4730 features as provided by the SNMPv3 framework. Specifically, the use 4731 of the User-based Security Model RFC 2574 [RFC2574] and the View- 4732 based Access Control Model RFC 2575 [RFC2575] is recommended. 4734 It is then a customer/user responsibility to ensure that the SNMP 4735 entity giving access to an instance of this MIB, is properly 4736 configured to give access to the objects only to those principals 4737 (users) that have legitimate rights to indeed GET or SET 4738 (change/create/delete) them. 4740 D Authors' Addresses 4742 Spencer Giacalone 4743 Predictive Systems, Inc. 4744 145 Hudson Street 4745 New York, NY 10013 4747 Phone: +1 (973) 301-5695 4748 EMail: spencer.giacalone@predictive.com 4750 Dan Joyal 4751 Quantum Bridge Communications, Inc. 4752 1 High Street 4753 North Andover, MA 01821 4755 Phone: +1 (978) 688-9100 4756 EMail: djoyal@quantumbridge.com 4758 Rob Coltun 4759 Redback Networks, Inc. 4760 300 Furguson Drive 4761 Mountain View, CA 94043 4763 Phone: +1 (650) 390-9030 4764 EMail: rcoltun@siara.com 4766 Fred Baker 4767 Cisco Systems, Inc. 4768 519 Lado Drive 4769 Santa Barbara, CA 93111 4771 Phone: +1 (805) 681-0115 4772 EMail: fred@cisco.com 4774 E Full Copyright Statement 4776 Copyright (C) The Internet Society (2000). All Rights Reserved. 4777 This document and translations of it may be copied and furnished to 4778 others, and derivative works that comment on or otherwise explain it 4779 or assist in its implementation may be prepared, copied, published 4780 and distributed, in whole or in part, without restriction of any 4781 kind, provided that the above copyright notice and this paragraph are 4782 included on all such copies and derivative works. However, this 4783 document itself may not be modified in any way, such as by removing 4784 the copyright notice or references to the Internet Society or other 4785 Internet organizations, except as needed for the purpose of 4786 developing Internet standards in which case the procedures for 4787 copyrights defined in the Internet Standards process must be 4788 followed, or as required to translate it into languages other than 4789 English. 4791 The limited permissions granted above are perpetual and will not be 4792 revoked by the Internet Society or its successors or assigns. 4794 This document and the information contained herein is provided on an 4795 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4796 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4797 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4798 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 4799 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.