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