idnits 2.17.1 draft-ietf-ospf-mib-update-00.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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 92 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 54 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 648: '...database. OspfExtLsdbLimit MUST be set...' RFC 2119 keyword, line 761: '...ase. OspfAsOpaqueLsdbLimit MUST be set...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 124 has weird spacing: '...objects and ...' == Line 125 has weird spacing: '... for the p...' == Line 136 has weird spacing: '...andards track...' == Line 532 has weird spacing: '...isables it on...' == Line 589 has weird spacing: '... the exter...' == (49 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 2000) is 8777 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 140, but not defined -- Looks like a reference, but probably isn't: 'RFC 2178' on line 4343 -- Looks like a reference, but probably isn't: 'RFC2574' on line 4559 -- Looks like a reference, but probably isn't: 'RFC2575' on line 4560 == Unused Reference: '21' is defined on line 4318, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 4301, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 4305, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 4312, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 4315, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 4322, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 4327, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 4335, 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 (~~), 20 warnings (==), 7 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: October 2000 D. Joyal 4 Filename:draft-ietf-ospf-mib-update-00.txt Nortel Networks 5 Rob Coltun 6 Redback Networks 7 Fred Baker 8 Cisco Systems 9 April 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 1580 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...............................57 87 3.16 OSPF Virtual Local LSDB Table.......................61 88 3.17 Conformance Information ............................64 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 .................................75 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 1859 Compatibility ..............................86 105 B.2 OSPF Traffic Engineering Support ....................86 106 B.3 OSPF NSSA Enhancement Support .......................86 107 B.4 OSPF MTU Mismatch Support ...........................87 108 B.5 Opaque LSA Support ..................................87 109 B.6 OSPF Compliances ....................................89 110 B.7 Miscellaneous .......................................89 111 C Security Considerations ...............................90 112 D Authors' Addresses ....................................90 113 E Full Copyright Statement ..............................91 115 1 Overview 117 1.1 The SNMPv2 Network Management Framework 119 This document describes aspects of the SNMPv2 Network Management 120 Framework, which consists of a number of components. They are: 122 - An overall architecture, described in RFC 2571 [1]. 124 - Mechanisms for describing and naming objects and events 125 for the purpose of management. The first version of this 126 Structure of Management Information (SMI) is called SMIv1 127 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 128 [3] and RFC 1215 [4]. The second version, called SMIv2, 129 is described in STD 58, RFC 2578 [5], RFC 2579 [6] and 130 RFC 2580 [7]. 132 - Message protocols for transferring management 133 information. The first version of the SNMP message 134 protocol is called SNMPv1 and described in STD 15, RFC 135 1157 [8]. A second version of the SNMP message protocol, 136 which is not an Internet standards track protocol, is 137 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 138 [10]. The third version of the message protocol is called 139 SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 140 RFC 2574 [12]. 142 - Protocol operations for accessing management information. 143 The first set of protocol operations and associated PDU 144 formats is described in STD 15, RFC 1157 [8]. A second 145 set of protocol operations and associated PDU formats is 146 described in RFC 1905 [13]. 148 - A set of fundamental applications described in RFC 2573 149 [14] and the view-based access control mechanism 150 described in RFC 2575 [15]. 152 1.2 The SMI, and Object Definitions 153 Managed objects are accessed via a virtual information store, termed 154 the Management Information Base or MIB. Objects in the MIB are 155 defined using the subset of Abstract Syntax Notation One (ASN.1) 156 defined in the SMI. 158 This memo specifies a MIB module that is compliant to the 159 SMIv2. A MIB conforming to the SMIv1 can be produced through 160 the appropriate translations. 162 1.3 Object Identification 164 Objects in the SMI are defined by types, and are named by an 165 OBJECT IDENTIFIER, which is an administratively assigned name. 166 The object type together with an object instance serves to 167 uniquely identify a specific instantiation of the object. For 168 human convenience, we often use a textual string, termed 169 the descriptor, to refer to the object type. 171 1.4 Textual Conventions 173 Several data types in this MIB document are termed textual 174 conventions. Textual conventions enhance the readability 175 of the specification and can ease comparison with other 176 specifications if appropriate. It should be noted that 177 textual conventions have no effect on either the syntax nor 178 the semantics of any managed objects. Objects defined in 179 terms of one of these methods are always encoded by means 180 of the rules that define the primitive type. Textual 181 conventions are used for the convenience of readers and 182 writers in pursuit of the goal of clear, concise, and 183 unambiguous MIB documents. 185 1.5 Conceptual Row Creation 187 For the benefit of row-creation in "conceptual" tables, 188 DEFVAL (Default Value) clauses are included in the definitions in 189 section 3, suggesting values which an agent should use for instances 190 of variables which need to be created due to a Set-Request, but which 191 are not specified in the Set-Request. DEFVAL clauses have not been 192 specified for some objects which are read-only, implying that they 193 are zeroed upon row creation. These objects are of the SYNTAX 194 Counter32 or Gauge32. 196 For those objects not having a DEFVAL clause, both management 197 stations and agents should heed the Robustness Principle of the 198 Internet (see RFC-791): 200 "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 305 The General Variables describe (as it may seem from the name) 306 variables which are global to the OSPF Process. 308 2.1.2 Area Data Structure and Area Stub Metric Table 310 The Area Data Structure describes all of the OSPF Areas that the 311 router participates in. The Area Table includes data for NSSA 312 translation. 314 The Area Stub Metric Table describes the metrics advertised into 315 a stub area by the default router(s). 317 2.1.3 Link State Database and External Link State Database 319 The Link State Database is provided primarily to provide detailed 320 information for network debugging. 322 2.1.4 Address Table and Host Tables 324 The Address Range Table and Host Table are provided to view 325 configured Network Summary and Host Route information. 327 2.1.5 Interface and Interface Metric Tables 329 The Table and the Interface Metric Table together describe 330 the various IP interfaces to OSPF. The metrics are placed in 331 separate tables in order to simplify dealing with multiple types of 332 service. The Interface table includes Link-Local (Opaque Type-9) LSA 333 statistics. 335 2.1.6 Virtual Interface Table 337 The Virtual Interface Table describes virtual links to the 338 OSPF Process, similarly to the (non-Virtual)Interface Tables. This 339 table includes Link-Local (Opaque Type-9) LSA statistics. 341 2.1.7 Neighbor and Virtual Neighbor Tables 343 The Neighbor Table and the Virtual Neighbor Table describe the 344 neighbors to the OSPF Process. 346 2.1.8 Local Link State Database Table and Virtual 347 Local Link State Database Table 349 The Local Link State Database Table and Virtual Local Link State 350 Database Table are identical to the OSPF LSDB Table in 351 format, but contain only Link-Local (Opaque Type-9) Link State 352 Advertisements for non-virtual and virtual links. 354 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 "0004021225Z" -- Sun Apr 02 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" 386 REVISION "0004021225Z" -- Sun Apr 02 12:25:50 GMT 2000 387 DESCRIPTION 388 "Updated for latest changes to OSPF Version 2" 389 ::= { mib-2 14 } 391 -- Note the Area ID, in OSPF, has the same format as an IP Address, 392 -- but has the function of defining a summarization point for 393 -- Link State Advertisements 395 AreaID ::= TEXTUAL-CONVENTION 396 STATUS current 397 DESCRIPTION 398 "An OSPF Area Identifier." 399 SYNTAX IpAddress 401 -- Note: The Router ID, in OSPF, has the same format as an IP 402 -- Address, but identifies the router independent of its IP Address. 404 RouterID ::= TEXTUAL-CONVENTION 405 STATUS current 406 DESCRIPTION 407 "A OSPF Router Identifier." 408 SYNTAX IpAddress 410 -- Note the OSPF Metric is defined as an unsigned value in the range 412 Metric ::= TEXTUAL-CONVENTION 413 STATUS current 414 DESCRIPTION 415 "The OSPF Internal Metric." 416 SYNTAX Integer32 (0..'FFFF'h) 418 BigMetric ::= TEXTUAL-CONVENTION 419 STATUS current 420 DESCRIPTION 421 "The OSPF External Metric." 422 SYNTAX Integer32 (0..'FFFFFF'h) 424 -- Status Values 426 Status ::= TEXTUAL-CONVENTION 427 STATUS current 428 DESCRIPTION 429 "An indication of the operability of an OSPF 430 function or feature. For example, The status 431 of an interface: 'enabled' indicates that 432 it is willing to communicate with other OSPF Routers, 433 while 'disabled' indicates that it is not." 434 SYNTAX INTEGER { enabled (1), disabled (2) } 436 -- Note that the following Time Durations are measured in seconds 438 PositiveInteger ::= TEXTUAL-CONVENTION 439 STATUS current 440 DESCRIPTION 441 "A positive integer. Values in excess are precluded as 442 unnecessary and prone to interoperability issues." 443 SYNTAX Integer32 (0..'7FFFFFFF'h) 445 HelloRange ::= TEXTUAL-CONVENTION 446 STATUS current 447 DESCRIPTION 448 "The range of intervals on which hello messages are 449 exchanged." 450 SYNTAX Integer32 (1..'FFFF'h) 452 UpToMaxAge ::= TEXTUAL-CONVENTION 453 STATUS current 454 DESCRIPTION 455 "The values that one might find or configure for 456 variables bounded by the maximum age of an LSA." 457 SYNTAX Integer32 (0..3600) 459 -- The range of ifIndex 461 InterfaceIndex ::= TEXTUAL-CONVENTION 462 STATUS current 463 DESCRIPTION 464 "The range of ifIndex." 465 SYNTAX Integer32 467 -- Potential Priorities for the Designated Router Election 469 DesignatedRouterPriority ::= TEXTUAL-CONVENTION 470 STATUS current 471 DESCRIPTION 472 "The values defined for the priority of a system for 473 becoming the designated router." 474 SYNTAX Integer32 (0..'FF'h) 476 TOSType ::= TEXTUAL-CONVENTION 477 STATUS current 478 DESCRIPTION 479 "Type of Service is defined as a mapping to the IP Type of 480 Service Flags as defined in the IP Forwarding Table MIB 482 +-----+-----+-----+-----+-----+-----+-----+-----+ 483 | | | | 484 | PRECEDENCE | TYPE OF SERVICE | 0 | 485 | | | | 486 +-----+-----+-----+-----+-----+-----+-----+-----+ 488 IP TOS IP TOS 489 Field Policy Field Policy 491 Contents Code Contents Code 492 0 0 0 0 ==> 0 0 0 0 1 ==> 2 493 0 0 1 0 ==> 4 0 0 1 1 ==> 6 494 0 1 0 0 ==> 8 0 1 0 1 ==> 10 495 0 1 1 0 ==> 12 0 1 1 1 ==> 14 496 1 0 0 0 ==> 16 1 0 0 1 ==> 18 497 1 0 1 0 ==> 20 1 0 1 1 ==> 22 498 1 1 0 0 ==> 24 1 1 0 1 ==> 26 499 1 1 1 0 ==> 28 1 1 1 1 ==> 30 501 The remaining values are left for future definition." 502 SYNTAX Integer32 (0..30) 504 -- OSPF General Variables 505 -- Note: These parameters apply globally to the Router's 506 -- OSPF Process. 508 ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 } 510 ospfRouterId OBJECT-TYPE 511 SYNTAX RouterID 512 MAX-ACCESS read-write 513 STATUS current 514 DESCRIPTION 515 "A 32-bit integer uniquely identifying the 516 router in the Autonomous System. 517 By convention, to ensure uniqueness, this 518 should default to the value of one of the 519 router's IP interface addresses." 520 REFERENCE 521 "OSPF Version 2, C.1 Global parameters" 522 ::= { ospfGeneralGroup 1 } 524 ospfAdminStat OBJECT-TYPE 525 SYNTAX Status 526 MAX-ACCESS read-write 527 STATUS current 528 DESCRIPTION 529 "The administrative status of OSPF in the 530 router. The value 'enabled' denotes that the 531 OSPF Process is active on at least one inter- 532 face; 'disabled' disables it on all inter- 533 faces." 534 ::= { ospfGeneralGroup 2 } 536 ospfVersionNumber OBJECT-TYPE 537 SYNTAX INTEGER { version2 (2) } 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The current version number of the OSPF proto- 542 col is 2." 543 REFERENCE 544 "OSPF Version 2, Title" 545 ::= { ospfGeneralGroup 3 } 547 ospfAreaBdrRtrStatus OBJECT-TYPE 548 SYNTAX TruthValue 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "A flag to note whether this router is an area 553 border router." 554 REFERENCE 555 "OSPF Version 2, Section 3 Splitting the AS into 556 Areas" 557 ::= { ospfGeneralGroup 4 } 559 ospfASBdrRtrStatus OBJECT-TYPE 560 SYNTAX TruthValue 561 MAX-ACCESS read-write 562 STATUS current 563 DESCRIPTION 564 "A flag to note whether this router is config- 565 ured as an Autonomous System border router." 566 REFERENCE 567 "OSPF Version 2, Section 3.3 Classification of 568 routers" 569 ::= { ospfGeneralGroup 5 } 571 ospfExternLsaCount OBJECT-TYPE 572 SYNTAX Gauge32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The number of external (LS type 5) link-state 577 advertisements in the link-state database." 578 REFERENCE 579 "OSPF Version 2, Appendix A.4.5 AS external link 580 advertisements" 581 ::= { ospfGeneralGroup 6 } 583 ospfExternLsaCksumSum OBJECT-TYPE 584 SYNTAX Integer32 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "The 32-bit unsigned sum of the LS checksums of 589 the external link-state advertisements con- 590 tained in the link-state database. This sum 591 can be used to determine if there has been a 592 change in a router's link state database, and 593 to compare the link-state database of two 594 routers." 595 ::= { ospfGeneralGroup 7 } 597 ospfTOSSupport OBJECT-TYPE 598 SYNTAX TruthValue 599 MAX-ACCESS read-write 600 STATUS current 601 DESCRIPTION 602 "The router's support for type-of-service rout- 603 ing." 604 REFERENCE 605 "OSPF Version 2, Appendix F.1.2 Optional TOS 606 support" 608 ::= { ospfGeneralGroup 8 } 610 ospfOriginateNewLsas OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The number of new link-state advertisements 616 that have been originated. This number is in- 617 cremented each time the router originates a new 618 LSA." 619 ::= { ospfGeneralGroup 9 } 621 ospfRxNewLsas OBJECT-TYPE 622 SYNTAX Counter32 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The number of link-state advertisements re- 627 ceived determined to be new instantiations. 628 This number does not include newer instantia- 629 tions of self-originated link-state advertise- 630 ments." 631 ::= { ospfGeneralGroup 10 } 633 ospfExtLsdbLimit OBJECT-TYPE 634 SYNTAX Integer32 (-1..'7FFFFFFF'h) 635 MAX-ACCESS read-write 636 STATUS current 637 DESCRIPTION 638 "The maximum number of non-default AS- 639 external-LSAs entries that can be stored in the 640 link-state database. If the value is -1, then 641 there is no limit. 643 When the number of non-default AS-external-LSAs 644 in a router's link-state database reaches 645 ospfExtLsdbLimit, the router enters Overflow- 646 State. The router never holds more than 647 ospfExtLsdbLimit non-default AS-external-LSAs 648 in its database. OspfExtLsdbLimit MUST be set 649 identically in all routers attached to the OSPF 650 backbone and/or any regular OSPF area. (i.e., 651 OSPF stub areas and NSSAs are excluded)." 652 DEFVAL { -1 } 653 ::= { ospfGeneralGroup 11 } 655 ospfMulticastExtensions OBJECT-TYPE 656 SYNTAX Integer32 657 MAX-ACCESS read-write 658 STATUS current 659 DESCRIPTION 660 "A Bit Mask indicating whether the router is 661 forwarding IP multicast (Class D) datagrams 662 based on the algorithms defined in the Multi- 663 cast Extensions to OSPF. 665 Bit 0, if set, indicates that the router can 666 forward IP multicast datagrams in the router's 667 directly attached areas (called intra-area mul- 668 ticast routing). 670 Bit 1, if set, indicates that the router can 671 forward IP multicast datagrams between OSPF 672 areas (called inter-area multicast routing). 674 Bit 2, if set, indicates that the router can 675 forward IP multicast datagrams between Auto- 676 nomous Systems (called inter-AS multicast rout- 677 ing). 679 Only certain combinations of bit settings are 680 allowed, namely: 0 (no multicast forwarding is 681 enabled), 1 (intra-area multicasting only), 3 682 (intra-area and inter-area multicasting), 5 683 (intra-area and inter-AS multicasting) and 7 684 (multicasting everywhere). By default, no mul- 685 ticast forwarding is enabled." 686 DEFVAL { 0 } 687 ::= { ospfGeneralGroup 12 } 689 ospfExitOverflowInterval OBJECT-TYPE 690 SYNTAX PositiveInteger 691 MAX-ACCESS read-write 692 STATUS current 693 DESCRIPTION 694 "The number of seconds that, after entering 695 OverflowState, a router will attempt to leave 696 OverflowState. This allows the router to again 697 originate non-default AS-external-LSAs. When 698 set to 0, the router will not leave Overflow- 699 State until restarted." 700 DEFVAL { 0 } 701 ::= { ospfGeneralGroup 13 } 703 ospfDemandExtensions OBJECT-TYPE 704 SYNTAX TruthValue 705 MAX-ACCESS read-write 706 STATUS current 707 DESCRIPTION 708 "The router's support for demand routing." 709 REFERENCE 710 "Extending OSPF to Support Demand Circuits" 711 ::= { ospfGeneralGroup 14 } 713 ospfRFC1583Compatibility OBJECT-TYPE 714 SYNTAX TruthValue 715 MAX-ACCESS read-write 716 STATUS current 717 DESCRIPTION 718 "Indicates metrics used to choose among multiple AS- 719 external-LSAs. When RFC1583Compatibility is set to 720 enabled, only cost will be used when choosing among 721 multiple AS-external-LSAs advertising the same 722 destination. When RFC1583Compatibility is set to 723 disabled, preference will be driven first by type of 724 path using cost only to break ties." 725 REFERENCE 726 "OSPF Version 2, Section 16.4.1 External path preferences" 727 ::= { ospfGeneralGroup 15 } 729 ospfOpaqueLsaSupport OBJECT-TYPE 730 SYNTAX TruthValue 731 MAX-ACCESS read-write 732 STATUS current 733 DESCRIPTION 734 "The router's support for Opaque LSA types." 735 REFERENCE 736 "The OSPF Opaque LSA Option" 737 ::= { ospfGeneralGroup 16 } 739 ospfTrafficEngineeringSupport OBJECT-TYPE 740 SYNTAX TruthValue 741 MAX-ACCESS read-write 742 STATUS current 743 DESCRIPTION 744 "The router's support for OSPF traffic engineering." 745 ::= { ospfGeneralGroup 17 } 747 ospfAsOpaqueLsdbLimit OBJECT-TYPE 748 SYNTAX Integer32 (-1..'7FFFFFFF'h) 749 MAX-ACCESS read-write 750 STATUS current 751 DESCRIPTION 752 "The maximum number of type-11 Opaque LSA 753 entries that can be stored in the link-state database. 754 If the value is -1, then there is no limit. 756 When the number of type-11 Opaque LSAs 757 in a router's link-state database reaches 758 ospfAsOpaqueLsdbLimit, the router enters Overflow- 759 State. The router never holds more than 760 ospfAsOpaqueLsdbLimit type-11 Opaque LSAs 761 in its database. OspfAsOpaqueLsdbLimit MUST be set 762 identically in all routers in the OSPF domain." 763 DEFVAL { -1 } 764 ::= { ospfGeneralGroup 18 } 766 -- OSPF Area Data Structure 768 -- The OSPF Area Data Structure contains information 769 -- regarding the various areas. The interfaces and 770 -- virtual links are configured as part of these areas. 771 -- Area 0.0.0.0, by definition, is the Backbone Area 773 ospfAreaTable OBJECT-TYPE 774 SYNTAX SEQUENCE OF OspfAreaEntry 775 MAX-ACCESS not-accessible 776 STATUS current 777 DESCRIPTION 778 "Information describing the configured parame- 779 ters and cumulative statistics of the router's 780 attached areas." 781 REFERENCE 782 "OSPF Version 2, Section 6 The Area Data Struc- 783 ture" 784 ::= { ospf 2 } 786 ospfAreaEntry OBJECT-TYPE 787 SYNTAX OspfAreaEntry 788 MAX-ACCESS not-accessible 789 STATUS current 790 DESCRIPTION 791 "Information describing the configured parame- 792 ters and cumulative statistics of one of the 793 router's attached areas." 794 INDEX { ospfAreaId } 795 ::= { ospfAreaTable 1 } 797 OspfAreaEntry ::= 798 SEQUENCE { 799 ospfAreaId 800 AreaID, 801 ospfAuthType 802 Integer32, 803 ospfImportAsExtern 804 INTEGER, 805 ospfSpfRuns 806 Counter32, 807 ospfAreaBdrRtrCount 808 Gauge32, 809 ospfAsBdrRtrCount 810 Gauge32, 812 ospfAreaLsaCount 813 Gauge32, 814 ospfAreaLsaCksumSum 815 Integer32, 816 ospfAreaSummary 817 INTEGER, 818 ospfAreaStatus 819 RowStatus 820 ospfAreaNssaTranslatorRole 821 INTEGER, 822 ospfAreaNssaTranslatorState 823 INTEGER, 824 ospfAreaNssaTranslatorStabilityInterval 825 PositiveInteger, 826 ospfAreaNssaTranslatorEvents 827 Counter32 828 } 830 ospfAreaId OBJECT-TYPE 831 SYNTAX AreaID 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "A 32-bit integer uniquely identifying an area. 836 Area ID 0.0.0.0 is used for the OSPF backbone." 837 REFERENCE 838 "OSPF Version 2, Appendix C.2 Area parameters" 839 ::= { ospfAreaEntry 1 } 841 ospfAuthType OBJECT-TYPE 842 SYNTAX Integer32 843 -- none (0), 844 -- simplePassword (1) 845 -- md5 (2) 846 -- reserved for specification by IANA (> 2) 847 MAX-ACCESS read-create 848 STATUS obsolete 849 DESCRIPTION 850 "The authentication type specified for an area. 851 Additional authentication types may be assigned 852 locally on a per Area basis." 853 REFERENCE 854 "OSPF Version 2, Appendix D Authentication" 855 DEFVAL { 0 } -- no authentication, by default 856 ::= { ospfAreaEntry 2 } 858 ospfImportAsExtern OBJECT-TYPE 859 SYNTAX INTEGER { 860 importExternal (1), 861 importNoExternal (2), 862 importNssa (3) 863 } 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "Indicates whether an area is a Stub area, NSSA, or standard 868 area. Type-5 AS-External LSAs and Type-11 Opaque LSAs are 869 not imported into Stub Areas or NSSAs. NSSAs import AS- 870 External data as Type-7 LSAs" 871 REFERENCE 872 "OSPF Version 2, Appendix C.2 Area parameters" 873 DEFVAL { importExternal } 874 ::= { ospfAreaEntry 3 } 876 ospfSpfRuns OBJECT-TYPE 877 SYNTAX Counter32 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The number of times that the intra-area route 882 table has been calculated using this area's 883 link-state database. This is typically done 884 using Dijkstra's algorithm." 885 ::= { ospfAreaEntry 4 } 887 ospfAreaBdrRtrCount OBJECT-TYPE 888 SYNTAX Gauge32 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION 892 "The total number of area border routers reach- 893 able within this area. This is initially zero, 894 and is calculated in each SPF Pass." 895 ::= { ospfAreaEntry 5 } 897 ospfAsBdrRtrCount OBJECT-TYPE 898 SYNTAX Gauge32 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "The total number of Autonomous System border 903 routers reachable within this area. This is 904 initially zero, and is calculated in each SPF 905 Pass." 906 ::= { ospfAreaEntry 6 } 908 ospfAreaLsaCount OBJECT-TYPE 909 SYNTAX Gauge32 910 MAX-ACCESS read-only 911 STATUS current 912 DESCRIPTION 913 "The total number of link-state advertisements 914 in this area's link-state database, excluding 915 AS External LSA's." 916 ::= { ospfAreaEntry 7 } 918 ospfAreaLsaCksumSum OBJECT-TYPE 919 SYNTAX Integer32 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "The 32-bit unsigned sum of the link-state ad- 924 vertisements' LS checksums contained in this 925 area's link-state database. This sum excludes 926 external (LS type 5) link-state advertisements. 927 The sum can be used to determine if there has 928 been a change in a router's link state data- 929 base, and to compare the link-state database of 930 two routers." 931 DEFVAL { 0 } 932 ::= { ospfAreaEntry 8 } 934 ospfAreaSummary OBJECT-TYPE 935 SYNTAX INTEGER { 936 noAreaSummary (1), 937 sendAreaSummary (2) 938 } 939 MAX-ACCESS read-create 940 STATUS current 941 DESCRIPTION 942 "The variable ospfAreaSummary controls the im- 943 port of summary LSAs into stub and NSSA areas. 944 It has no effect on other areas. 946 If it is noAreaSummary, the router will neither 947 originate nor propagate summary LSAs into the 948 stub or NSSA area. It will rely entirely on its 949 default route. 951 If it is sendAreaSummary, the router will both 952 summarize and propagate summary LSAs." 953 DEFVAL { noAreaSummary } 954 ::= { ospfAreaEntry 9 } 956 ospfAreaStatus OBJECT-TYPE 957 SYNTAX RowStatus 958 MAX-ACCESS read-create 959 STATUS current 960 DESCRIPTION 961 "This variable displays the status of the en- 962 try. Setting it to 'invalid' has the effect of 963 rendering it inoperative. The internal effect 964 (row removal) is implementation dependent." 966 ::= { ospfAreaEntry 10 } 968 ospfAreaNssaTranslatorRole OBJECT-TYPE 969 SYNTAX INTEGER { always (1), candidate (2) } 970 MAX-ACCESS read-create 971 STATUS current 972 DESCRIPTION 973 "Indicates an NSSA Border router's ability to 974 perform NSSA translation of type-7 LSAs into 975 type-5 LSAs." 976 DEFVAL { candidate } 977 ::= { ospfAreaEntry 11 } 979 ospfAreaNssaTranslatorState OBJECT-TYPE 980 SYNTAX INTEGER { enabled (1), 981 elected (2), 982 disabled (3) 983 } 984 MAX-ACCESS read-only 985 STATUS current 986 DESCRIPTION 987 "Indicates if and how an NSSA Border router is 988 performing NSSA translation of type-7 LSAs into type-5 989 LSAs. When this object set to enabled, the NSSA Border 990 router's OspfAreaNssaExtTranslatorRole has been set to 991 always. When this object is set to elected, a candidate 992 NSSA Border router is Translating type-7 LSAs into type-5. 993 When this object is set to disabled, a candidate NSSA 994 Border router is NOT translating type-7 LSAs into type-5." 995 ::= { ospfAreaEntry 12 } 997 ospfAreaNssaTranslatorStabilityInterval OBJECT-TYPE 998 SYNTAX PositiveInteger 999 MAX-ACCESS read-write 1000 STATUS current 1001 DESCRIPTION 1002 "The number of seconds after an elected translator 1003 determines its services are no longer required, that 1004 it should continue to perform its translation duties." 1005 DEFVAL { 40 } 1006 ::= { ospfAreaEntry 13 } 1008 ospfAreaNssaTranslatorEvents OBJECT-TYPE 1009 SYNTAX Counter32 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "Indicates the number of Translator State changes 1014 that have occurred since the last boot-up." 1015 ::= { ospfAreaEntry 14 } 1017 -- OSPF Area Default Metric Table 1019 -- The OSPF Area Default Metric Table describes the metrics 1020 -- that a default Area Border Router will advertise into a 1021 -- Stub area. 1023 ospfStubAreaTable OBJECT-TYPE 1024 SYNTAX SEQUENCE OF OspfStubAreaEntry 1025 MAX-ACCESS not-accessible 1026 STATUS current 1027 DESCRIPTION 1028 "The set of metrics that will be advertised by 1029 a default Area Border Router into a stub area." 1030 REFERENCE 1031 "OSPF Version 2, Appendix C.2, Area Parameters" 1032 ::= { ospf 3 } 1034 ospfStubAreaEntry OBJECT-TYPE 1035 SYNTAX OspfStubAreaEntry 1036 MAX-ACCESS not-accessible 1037 STATUS current 1038 DESCRIPTION 1039 "The metric for a given Type of Service that 1040 will be advertised by a default Area Border 1041 Router into a stub area." 1042 REFERENCE 1043 "OSPF Version 2, Appendix C.2, Area Parameters" 1044 INDEX { ospfStubAreaId, ospfStubTOS } 1045 ::= { ospfStubAreaTable 1 } 1047 OspfStubAreaEntry ::= 1048 SEQUENCE { 1049 ospfStubAreaId 1050 AreaID, 1051 ospfStubTOS 1052 TOSType, 1053 ospfStubMetric 1054 BigMetric, 1055 ospfStubStatus 1056 RowStatus, 1057 ospfStubMetricType 1058 INTEGER 1059 } 1061 ospfStubAreaId OBJECT-TYPE 1062 SYNTAX AreaID 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION 1066 "The 32 bit identifier for the Stub Area. On 1067 creation, this can be derived from the in- 1068 stance." 1069 ::= { ospfStubAreaEntry 1 } 1071 ospfStubTOS OBJECT-TYPE 1072 SYNTAX TOSType 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "The Type of Service associated with the 1077 metric. On creation, this can be derived from 1078 the instance." 1079 ::= { ospfStubAreaEntry 2 } 1081 ospfStubMetric OBJECT-TYPE 1082 SYNTAX BigMetric 1083 MAX-ACCESS read-create 1084 STATUS current 1085 DESCRIPTION 1086 "The metric value applied at the indicated type 1087 of service. By default, this equals the least 1088 metric at the type of service among the inter- 1089 faces to other areas." 1090 ::= { ospfStubAreaEntry 3 } 1092 ospfStubStatus OBJECT-TYPE 1093 SYNTAX RowStatus 1094 MAX-ACCESS read-create 1095 STATUS current 1096 DESCRIPTION 1097 "This variable displays the status of the en- 1098 try. Setting it to 'invalid' has the effect of 1099 rendering it inoperative. The internal effect 1100 (row removal) is implementation dependent." 1101 ::= { ospfStubAreaEntry 4 } 1103 ospfStubMetricType OBJECT-TYPE 1104 SYNTAX INTEGER { 1105 ospfMetric (1), -- OSPF Metric 1106 comparableCost (2), -- external type 1 1107 nonComparable (3) -- external type 2 1108 } 1109 MAX-ACCESS read-create 1110 STATUS current 1111 DESCRIPTION 1112 "This variable displays the type of metric ad- 1113 vertised as a default route." 1114 DEFVAL { ospfMetric } 1115 ::= { ospfStubAreaEntry 5 } 1117 -- OSPF Link State Database 1119 -- The Link State Database contains the Link State 1120 -- Advertisements from throughout the areas that the 1121 -- device is attached to. 1123 ospfLsdbTable OBJECT-TYPE 1124 SYNTAX SEQUENCE OF OspfLsdbEntry 1125 MAX-ACCESS not-accessible 1126 STATUS current 1127 DESCRIPTION 1128 "The OSPF Process's Link State Database." 1129 REFERENCE 1130 "OSPF Version 2, Section 12 Link State Adver- 1131 tisements" 1132 ::= { ospf 4 } 1134 ospfLsdbEntry OBJECT-TYPE 1135 SYNTAX OspfLsdbEntry 1136 MAX-ACCESS not-accessible 1137 STATUS current 1138 DESCRIPTION 1139 "A single Link State Advertisement." 1140 INDEX { ospfLsdbAreaId, ospfLsdbType, 1141 ospfLsdbLsid, ospfLsdbRouterId } 1142 ::= { ospfLsdbTable 1 } 1144 OspfLsdbEntry ::= 1145 SEQUENCE { 1146 ospfLsdbAreaId 1147 AreaID, 1148 ospfLsdbType 1149 INTEGER, 1150 ospfLsdbLsid 1151 IpAddress, 1152 ospfLsdbRouterId 1153 RouterID, 1154 ospfLsdbSequence 1155 Integer32, 1156 ospfLsdbAge 1157 Integer32, 1158 ospfLsdbChecksum 1159 Integer32, 1160 ospfLsdbAdvertisement 1161 OCTET STRING 1162 } 1164 ospfLsdbAreaId OBJECT-TYPE 1165 SYNTAX AreaID 1166 MAX-ACCESS read-only 1167 STATUS current 1168 DESCRIPTION 1169 "The 32 bit identifier of the Area from which 1170 the LSA was received." 1171 REFERENCE 1172 "OSPF Version 2, Appendix C.2 Area parameters" 1173 ::= { ospfLsdbEntry 1 } 1175 -- Note: External Link State Advertisements are permitted 1176 -- for backward compatibility, but should be displayed in 1177 -- the ospfExtLsdbTable rather than here. 1179 ospfLsdbType OBJECT-TYPE 1180 SYNTAX INTEGER { 1181 routerLink (1), 1182 networkLink (2), 1183 summaryLink (3), 1184 asSummaryLink (4), 1185 asExternalLink (5), -- but see ospfExtLsdbTable 1186 multicastLink (6), 1187 nssaExternalLink (7), 1188 areaOpaqueLink (10) 1189 } 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "The type of the link state advertisement. 1194 Each link state type has a separate advertise- 1195 ment format." 1196 REFERENCE 1197 "OSPF Version 2, Appendix A.4.1 The Link State 1198 Advertisement header" 1199 ::= { ospfLsdbEntry 2 } 1201 ospfLsdbLsid OBJECT-TYPE 1202 SYNTAX IpAddress 1203 MAX-ACCESS read-only 1204 STATUS current 1205 DESCRIPTION 1206 "The Link State ID is an LS Type Specific field 1207 containing either a Router ID or an IP Address; 1208 it identifies the piece of the routing domain 1209 that is being described by the advertisement." 1210 REFERENCE 1211 "OSPF Version 2, Section 12.1.4 Link State ID" 1212 ::= { ospfLsdbEntry 3 } 1214 ospfLsdbRouterId OBJECT-TYPE 1215 SYNTAX RouterID 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "The 32 bit number that uniquely identifies the 1220 originating router in the Autonomous System." 1221 REFERENCE 1222 "OSPF Version 2, Appendix C.1 Global parameters" 1223 ::= { ospfLsdbEntry 4 } 1225 -- Note that the OSPF Sequence Number is a 32 bit signed 1226 -- integer. It starts with the value '80000001'h, 1227 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 1228 -- Thus, a typical sequence number will be very negative. 1230 ospfLsdbSequence OBJECT-TYPE 1231 SYNTAX Integer32 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "The sequence number field is a signed 32-bit 1236 integer. It is used to detect old and dupli- 1237 cate link state advertisements. The space of 1238 sequence numbers is linearly ordered. The 1239 larger the sequence number the more recent the 1240 advertisement." 1241 REFERENCE 1242 "OSPF Version 2, Section 12.1.6 LS sequence 1243 number" 1244 ::= { ospfLsdbEntry 5 } 1246 ospfLsdbAge OBJECT-TYPE 1247 SYNTAX Integer32 -- Should be 0..MaxAge, except when 1248 -- doNotAge bit is set 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "This field is the age of the link state adver- 1253 tisement in seconds." 1254 REFERENCE 1255 "OSPF Version 2, Section 12.1.1 LS age" 1256 ::= { ospfLsdbEntry 6 } 1258 ospfLsdbChecksum OBJECT-TYPE 1259 SYNTAX Integer32 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "This field is the checksum of the complete 1264 contents of the advertisement, excepting the 1265 age field. The age field is excepted so that 1266 an advertisement's age can be incremented 1267 without updating the checksum. The checksum 1268 used is the same that is used for ISO connec- 1269 tionless datagrams; it is commonly referred to 1270 as the Fletcher checksum." 1271 REFERENCE 1272 "OSPF Version 2, Section 12.1.7 LS checksum" 1273 ::= { ospfLsdbEntry 7 } 1275 ospfLsdbAdvertisement OBJECT-TYPE 1276 SYNTAX OCTET STRING (SIZE (1..65535)) 1277 MAX-ACCESS read-only 1278 STATUS current 1279 DESCRIPTION 1280 "The entire Link State Advertisement, including 1281 its header." 1282 REFERENCE 1283 "OSPF Version 2, Section 12 Link State Adver- 1284 tisements" 1285 ::= { ospfLsdbEntry 8 } 1287 -- Address Range Table 1289 -- The Address Range Table acts as an adjunct to the Area 1290 -- Table; It describes those Address Range Summaries that 1291 -- are configured to be propagated from an Area to reduce 1292 -- the amount of information about it which is known beyond 1293 -- its borders. 1295 ospfAreaRangeTable OBJECT-TYPE 1296 SYNTAX SEQUENCE OF OspfAreaRangeEntry 1297 MAX-ACCESS not-accessible 1298 STATUS obsolete 1299 DESCRIPTION 1300 "A range if IP addresses specified by an IP 1301 address/IP network mask pair. For example, 1302 class B address range of X.X.X.X with a network 1303 mask of 255.255.0.0 includes all IP addresses 1304 from X.X.0.0 to X.X.255.255" 1305 REFERENCE 1306 "OSPF Version 2, Appendix C.2 Area parameters" 1307 ::= { ospf 5 } 1309 ospfAreaRangeEntry OBJECT-TYPE 1310 SYNTAX OspfAreaRangeEntry 1311 MAX-ACCESS not-accessible 1312 STATUS obsolete 1313 DESCRIPTION 1314 "A range if IP addresses specified by an IP 1315 address/IP network mask pair. For example, 1316 class B address range of X.X.X.X with a network 1317 mask of 255.255.0.0 includes all IP addresses 1318 from X.X.0.0 to X.X.255.255" 1319 REFERENCE 1320 "OSPF Version 2, Appendix C.2 Area parameters" 1321 INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet } 1322 ::= { ospfAreaRangeTable 1 } 1324 OspfAreaRangeEntry ::= 1325 SEQUENCE { 1326 ospfAreaRangeAreaId 1327 AreaID, 1328 ospfAreaRangeNet 1329 IpAddress, 1330 ospfAreaRangeMask 1331 IpAddress, 1332 ospfAreaRangeStatus 1333 RowStatus, 1334 ospfAreaRangeEffect 1335 INTEGER 1336 } 1338 ospfAreaRangeAreaId OBJECT-TYPE 1339 SYNTAX AreaID 1340 MAX-ACCESS read-only 1341 STATUS obsolete 1342 DESCRIPTION 1343 "The Area the Address Range is to be found 1344 within." 1345 REFERENCE 1346 "OSPF Version 2, Appendix C.2 Area parameters" 1347 ::= { ospfAreaRangeEntry 1 } 1349 ospfAreaRangeNet OBJECT-TYPE 1350 SYNTAX IpAddress 1351 MAX-ACCESS read-only 1352 STATUS obsolete 1353 DESCRIPTION 1354 "The IP Address of the Net or Subnet indicated 1355 by the range." 1356 REFERENCE 1357 "OSPF Version 2, Appendix C.2 Area parameters" 1358 ::= { ospfAreaRangeEntry 2 } 1360 ospfAreaRangeMask OBJECT-TYPE 1361 SYNTAX IpAddress 1362 MAX-ACCESS read-create 1363 STATUS obsolete 1364 DESCRIPTION 1365 "The Subnet Mask that pertains to the Net or 1366 Subnet." 1367 REFERENCE 1368 "OSPF Version 2, Appendix C.2 Area parameters" 1369 ::= { ospfAreaRangeEntry 3 } 1371 ospfAreaRangeStatus OBJECT-TYPE 1372 SYNTAX RowStatus 1373 MAX-ACCESS read-create 1374 STATUS obsolete 1375 DESCRIPTION 1376 "This variable displays the status of the en- 1377 try. Setting it to 'invalid' has the effect of 1378 rendering it inoperative. The internal effect 1379 (row removal) is implementation dependent." 1380 ::= { ospfAreaRangeEntry 4 } 1382 ospfAreaRangeEffect OBJECT-TYPE 1383 SYNTAX INTEGER { 1384 advertiseMatching (1), 1385 doNotAdvertiseMatching (2) 1386 } 1387 MAX-ACCESS read-create 1388 STATUS obsolete 1389 DESCRIPTION 1390 "Subnets subsumed by ranges either trigger the 1391 advertisement of the indicated summary (adver- 1392 tiseMatching), or result in the subnet's not 1393 being advertised at all outside the area." 1394 DEFVAL { advertiseMatching } 1395 ::= { ospfAreaRangeEntry 5 } 1397 -- OSPF Host Table 1399 -- The Host/Metric Table indicates what hosts are directly 1400 -- attached to the Router, what metrics and types of 1401 -- service should be advertised for them and what Areas they 1402 -- are found within. 1404 ospfHostTable OBJECT-TYPE 1405 SYNTAX SEQUENCE OF OspfHostEntry 1406 MAX-ACCESS not-accessible 1407 STATUS current 1408 DESCRIPTION 1409 "The list of Hosts, and their metrics, that the 1410 router will advertise as host routes." 1411 REFERENCE 1412 "OSPF Version 2, Appendix C.7 Host route param- 1413 eters" 1414 ::= { ospf 6 } 1416 ospfHostEntry OBJECT-TYPE 1417 SYNTAX OspfHostEntry 1418 MAX-ACCESS not-accessible 1419 STATUS current 1420 DESCRIPTION 1421 "A metric to be advertised, for a given type of 1422 service, when a given host is reachable." 1423 INDEX { ospfHostIpAddress, ospfHostTOS } 1424 ::= { ospfHostTable 1 } 1426 OspfHostEntry ::= 1427 SEQUENCE { 1428 ospfHostIpAddress 1429 IpAddress, 1430 ospfHostTOS 1431 TOSType, 1432 ospfHostMetric 1433 Metric, 1434 ospfHostStatus 1435 RowStatus, 1436 ospfHostAreaID 1437 AreaID 1438 } 1440 ospfHostIpAddress OBJECT-TYPE 1441 SYNTAX IpAddress 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "The IP Address of the Host." 1446 REFERENCE 1447 "OSPF Version 2, Appendix C.7 Host route parame- 1448 ters" 1449 ::= { ospfHostEntry 1 } 1451 ospfHostTOS OBJECT-TYPE 1452 SYNTAX TOSType 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "The Type of Service of the route being config- 1457 ured." 1458 REFERENCE 1459 "OSPF Version 2, Appendix C.7 Host route parame- 1460 ters" 1461 ::= { ospfHostEntry 2 } 1463 ospfHostMetric OBJECT-TYPE 1464 SYNTAX Metric 1465 MAX-ACCESS read-create 1466 STATUS current 1467 DESCRIPTION 1468 "The Metric to be advertised." 1469 REFERENCE 1470 "OSPF Version 2, Appendix C.7 Host route parame- 1471 ters" 1473 := { ospfHostEntry 3 } 1475 ospfHostStatus OBJECT-TYPE 1476 SYNTAX RowStatus 1477 MAX-ACCESS read-create 1478 STATUS current 1479 DESCRIPTION 1480 "This variable displays the status of the en- 1481 try. Setting it to 'invalid' has the effect of 1482 rendering it inoperative. The internal effect 1483 (row removal) is implementation dependent." 1484 ::= { ospfHostEntry 4 } 1486 ospfHostAreaID OBJECT-TYPE 1487 SYNTAX AreaID 1488 MAX-ACCESS read-create 1489 STATUS current 1490 DESCRIPTION 1491 "The Area the Host Entry is to be found within." 1492 REFERENCE 1493 "OSPF Version 2, Appendix C.7 Host parameters" 1494 ::= { ospfHostEntry 5 } 1496 -- OSPF Interface Table 1498 -- The OSPF Interface Table augments the ipAddrTable 1499 -- with OSPF specific information. 1501 ospfIfTable OBJECT-TYPE 1502 SYNTAX SEQUENCE OF OspfIfEntry 1503 MAX-ACCESS not-accessible 1504 STATUS current 1505 DESCRIPTION 1506 "The OSPF Interface Table describes the inter- 1507 faces from the viewpoint of OSPF." 1508 REFERENCE 1509 "OSPF Version 2, Appendix C.3 Router interface 1510 parameters" 1511 ::= { ospf 7 } 1513 ospfIfEntry OBJECT-TYPE 1514 SYNTAX OspfIfEntry 1515 MAX-ACCESS not-accessible 1516 STATUS current 1517 DESCRIPTION 1518 "The OSPF Interface Entry describes one inter- 1519 face from the viewpoint of OSPF." 1520 INDEX { ospfIfIpAddress, ospfAddressLessIf } 1521 ::= { ospfIfTable 1 } 1523 OspfIfEntry ::= 1524 SEQUENCE { 1525 ospfIfIpAddress 1526 IpAddress, 1527 ospfAddressLessIf 1528 Integer32, 1529 ospfIfAreaId 1530 AreaID, 1531 ospfIfType 1532 INTEGER, 1533 ospfIfAdminStat 1534 Status, 1535 ospfIfRtrPriority 1536 DesignatedRouterPriority, 1537 ospfIfTransitDelay 1538 UpToMaxAge, 1539 ospfIfRetransInterval 1540 UpToMaxAge, 1541 ospfIfHelloInterval 1542 HelloRange, 1543 ospfIfRtrDeadInterval 1544 PositiveInteger, 1545 ospfIfPollInterval 1546 PositiveInteger, 1547 ospfIfState 1548 INTEGER, 1549 ospfIfDesignatedRouter 1550 IpAddress, 1551 ospfIfBackupDesignatedRouter 1552 IpAddress, 1553 ospfIfEvents 1554 Counter32, 1555 ospfIfAuthType 1556 INTEGER, 1557 ospfIfAuthKey 1558 OCTET STRING, 1559 ospfIfStatus 1560 RowStatus, 1561 ospfIfMulticastForwarding 1562 INTEGER, 1563 ospfIfDemand 1564 TruthValue 1565 ospfIfLsaCount 1566 Gauge32, 1567 ospfIfLsaCksumSum 1568 Integer32 1570 } 1572 ospfIfIpAddress OBJECT-TYPE 1573 SYNTAX IpAddress 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "The IP address of this OSPF interface." 1578 ::= { ospfIfEntry 1 } 1580 ospfAddressLessIf OBJECT-TYPE 1581 SYNTAX Integer32 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "For the purpose of easing the instancing of 1586 addressed and address less interfaces; This 1587 variable takes the value 0 on interfaces with 1588 IP Addresses, and the corresponding value of 1589 ifIndex for interfaces having no IP Address." 1590 ::= { ospfIfEntry 2 } 1592 ospfIfAreaId OBJECT-TYPE 1593 SYNTAX AreaID 1594 MAX-ACCESS read-create 1595 STATUS current 1596 DESCRIPTION 1597 "A 32-bit integer uniquely identifying the area 1598 to which the interface connects. Area ID 1599 0.0.0.0 is used for the OSPF backbone." 1600 DEFVAL { '00000000'H } -- 0.0.0.0 1601 ::= { ospfIfEntry 3 } 1603 ospfIfType OBJECT-TYPE 1604 SYNTAX INTEGER { 1605 broadcast (1), 1606 nbma (2), 1607 pointToPoint (3), 1608 pointToMultipoint (5) 1609 } 1610 MAX-ACCESS read-create 1611 STATUS current 1612 DESCRIPTION 1613 "The OSPF interface type. 1614 By way of a default, this field may be intuited 1615 from the corresponding value of ifType. Broad- 1616 cast LANs, such as Ethernet and IEEE 802.5, 1617 take the value 'broadcast', X.25 and similar 1618 technologies take the value 'nbma', and links 1619 that are definitively point to point take the 1620 value 'pointToPoint'." 1621 ::= { ospfIfEntry 4 } 1623 ospfIfAdminStat OBJECT-TYPE 1624 SYNTAX Status 1625 MAX-ACCESS read-create 1626 STATUS current 1627 DESCRIPTION 1628 "The OSPF interface's administrative status. 1629 The value formed on the interface, and the in- 1630 terface will be advertised as an internal route 1631 to some area. The value 'disabled' denotes 1632 that the interface is external to OSPF." 1633 DEFVAL { enabled } 1634 ::= { ospfIfEntry 5 } 1636 ospfIfRtrPriority OBJECT-TYPE 1637 SYNTAX DesignatedRouterPriority 1638 MAX-ACCESS read-create 1639 STATUS current 1640 DESCRIPTION 1641 "The priority of this interface. Used in 1642 multi-access networks, this field is used in 1643 the designated router election algorithm. The 1644 value 0 signifies that the router is not eligi- 1645 ble to become the designated router on this 1646 particular network. In the event of a tie in 1647 this value, routers will use their Router ID as 1648 a tie breaker." 1649 DEFVAL { 1 } 1650 ::= { ospfIfEntry 6 } 1652 ospfIfTransitDelay OBJECT-TYPE 1653 SYNTAX UpToMaxAge 1654 MAX-ACCESS read-create 1655 STATUS current 1656 DESCRIPTION 1657 "The estimated number of seconds it takes to 1658 transmit a link state update packet over this 1659 interface." 1660 DEFVAL { 1 } 1661 ::= { ospfIfEntry 7 } 1663 ospfIfRetransInterval OBJECT-TYPE 1664 SYNTAX UpToMaxAge 1665 MAX-ACCESS read-create 1666 STATUS current 1667 DESCRIPTION 1668 "The number of seconds between link-state ad- 1669 vertisement retransmissions, for adjacencies 1670 belonging to this interface. This value is 1671 also used when retransmitting database descrip- 1672 tion and link-state request packets." 1673 DEFVAL { 5 } 1674 ::= { ospfIfEntry 8 } 1676 ospfIfHelloInterval OBJECT-TYPE 1677 SYNTAX HelloRange 1678 MAX-ACCESS read-create 1679 STATUS current 1680 DESCRIPTION 1681 "The length of time, in seconds, between the 1682 Hello packets that the router sends on the in- 1683 terface. This value must be the same for all 1684 routers attached to a common network." 1685 DEFVAL { 10 } 1686 ::= { ospfIfEntry 9 } 1688 ospfIfRtrDeadInterval OBJECT-TYPE 1689 SYNTAX PositiveInteger 1690 MAX-ACCESS read-create 1691 STATUS current 1692 DESCRIPTION 1693 "The number of seconds that a router's Hello 1694 packets have not been seen before it's neigh- 1695 bors declare the router down. This should be 1696 some multiple of the Hello interval. This 1697 value must be the same for all routers attached 1698 to a common network." 1699 DEFVAL { 40 } 1700 ::= { ospfIfEntry 10 } 1702 ospfIfPollInterval OBJECT-TYPE 1703 SYNTAX PositiveInteger 1704 MAX-ACCESS read-create 1705 STATUS current 1706 DESCRIPTION 1707 "The larger time interval, in seconds, between 1708 the Hello packets sent to an inactive non- 1709 broadcast multi- access neighbor." 1710 DEFVAL { 120 } 1711 ::= { ospfIfEntry 11 } 1713 ospfIfState OBJECT-TYPE 1714 SYNTAX INTEGER { 1715 down (1), 1716 loopback (2), 1717 waiting (3), 1718 pointToPoint (4), 1719 designatedRouter (5), 1720 backupDesignatedRouter (6), 1721 otherDesignatedRouter (7) 1722 } 1723 MAX-ACCESS read-only 1724 STATUS current 1725 DESCRIPTION 1726 "The OSPF Interface State." 1728 DEFVAL { down } 1729 ::= { ospfIfEntry 12 } 1731 ospfIfDesignatedRouter OBJECT-TYPE 1732 SYNTAX IpAddress 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "The IP Address of the Designated Router." 1737 DEFVAL { '00000000'H } -- 0.0.0.0 1738 ::= { ospfIfEntry 13 } 1740 ospfIfBackupDesignatedRouter OBJECT-TYPE 1741 SYNTAX IpAddress 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "The IP Address of the Backup Designated 1746 Router." 1747 DEFVAL { '00000000'H } -- 0.0.0.0 1748 ::= { ospfIfEntry 14 } 1750 ospfIfEvents OBJECT-TYPE 1751 SYNTAX Counter32 1752 MAX-ACCESS read-only 1753 STATUS current 1754 DESCRIPTION 1755 "The number of times this OSPF interface has 1756 changed its state, or an error has occurred." 1757 ::= { ospfIfEntry 15 } 1759 ospfIfAuthType OBJECT-TYPE 1760 SYNTAX INTEGER (0..255) 1761 -- none (0), 1762 -- simplePassword (1) 1763 -- md5 (2) 1764 -- reserved for specification by IANA (> 2) 1765 MAX-ACCESS read-create 1766 STATUS current 1767 DESCRIPTION 1768 "The authentication type specified for an in- 1769 terface. Additional authentication types may 1770 be assigned locally." 1771 REFERENCE 1772 "OSPF Version 2, Appendix D Authentication" 1773 DEFVAL { 0 } -- no authentication, by default 1774 ::= { ospfIfEntry 16 } 1776 ospfIfAuthKey OBJECT-TYPE 1777 SYNTAX OCTET STRING (SIZE (0..256)) 1778 MAX-ACCESS read-create 1779 STATUS current 1780 DESCRIPTION 1781 "The Authentication Key. If the Area's Author- 1782 ization Type is simplePassword, and the key 1783 length is shorter than 8 octets, the agent will 1784 left adjust and zero fill to 8 octets. 1786 Note that unauthenticated interfaces need no 1787 authentication key, and simple password authen- 1788 tication cannot use a key of more than 8 oc- 1789 tets. Larger keys are useful only with authen- 1790 tication mechanisms not specified in this docu- 1791 ment. 1793 When read, ospfIfAuthKey always returns an Oc- 1794 tet String of length zero." 1795 REFERENCE 1796 "OSPF Version 2, Section 9 The Interface Data 1797 Structure" 1798 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 1799 ::= { ospfIfEntry 17 } 1801 ospfIfStatus OBJECT-TYPE 1802 SYNTAX RowStatus 1803 MAX-ACCESS read-create 1804 STATUS current 1805 DESCRIPTION 1806 "This variable displays the status of the en- 1807 try. Setting it to 'invalid' has the effect of 1808 rendering it inoperative. The internal effect 1809 (row removal) is implementation dependent." 1810 ::= { ospfIfEntry 18 } 1812 ospfIfMulticastForwarding OBJECT-TYPE 1813 SYNTAX INTEGER { 1814 blocked (1), -- no multicast forwarding 1815 multicast (2), -- using multicast address 1816 unicast (3) -- to each OSPF neighbor 1817 } 1818 MAX-ACCESS read-create 1819 STATUS current 1820 DESCRIPTION 1821 "The way multicasts should forwarded on this 1822 interface; not forwarded, forwarded as data 1823 link multicasts, or forwarded as data link uni- 1824 casts. Data link multicasting is not meaning- 1825 ful on point to point and NBMA interfaces, and 1826 setting ospfMulticastForwarding to 0 effective- 1827 ly disables all multicast forwarding." 1828 DEFVAL { blocked } 1829 ::= { ospfIfEntry 19 } 1831 ospfIfDemand OBJECT-TYPE 1832 SYNTAX TruthValue 1833 MAX-ACCESS read-create 1834 STATUS current 1835 DESCRIPTION 1836 "Indicates whether Demand OSPF procedures (hel- 1837 lo suppression to FULL neighbors and setting the 1838 DoNotAge flag on propagated LSAs) should be per- 1839 formed on this interface." 1840 DEFVAL { false } 1841 ::= { ospfIfEntry 20 } 1843 ospfIfLsaCount OBJECT-TYPE 1844 SYNTAX Gauge32 1845 MAX-ACCESS read-only 1846 STATUS current 1847 DESCRIPTION 1848 "The total number of link-local link state advertisements 1849 in this interface's link-local link state database." 1850 ::= { ospfIfEntry 21 } 1852 ospfIfLsaCksumSum OBJECT-TYPE 1853 SYNTAX Integer32 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION 1857 "The 32-bit unsigned sum of the link-state ad- 1858 vertisements' LS checksums contained in this 1859 interface's link-local link state database. 1860 The sum can be used to determine if there has 1861 been a change in the interface's link state data- 1862 base, and to compare the interface link-state database of 1863 routers attached to the same subnet." 1864 ::= { ospfIfEntry 22 } 1866 -- OSPF Interface Metric Table 1868 -- The Metric Table describes the metrics to be advertised 1869 -- for a specified interface at the various types of service. 1870 -- As such, this table is an adjunct of the OSPF Interface 1871 -- Table. 1873 -- Types of service, as defined by RFC 791, have the ability 1874 -- to request low delay, high bandwidth, or reliable linkage. 1876 -- For the purposes of this specification, the measure of 1877 -- bandwidth: 1879 -- Metric = 10^8 / ifSpeed 1880 -- is the default value. For multiple link interfaces, note 1881 -- 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, 1931 ospfIfMetricTOS 1932 TOSType, 1933 ospfIfMetricValue 1934 Metric, 1935 ospfIfMetricStatus 1936 RowStatus 1937 } 1939 ospfIfMetricIpAddress OBJECT-TYPE 1940 SYNTAX IpAddress 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "The IP address of this OSPF interface. On row 1945 creation, this can be derived from the in- 1946 stance." 1947 ::= { ospfIfMetricEntry 1 } 1949 ospfIfMetricAddressLessIf OBJECT-TYPE 1950 SYNTAX Integer32 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "For the purpose of easing the instancing of 1955 addressed and addressless interfaces; This 1956 variable takes the value 0 on interfaces with 1957 IP Addresses, and the value of ifIndex for in- 1958 terfaces having no IP Address. On row crea- 1959 tion, this can be derived from the instance." 1960 ::= { ospfIfMetricEntry 2 } 1962 ospfIfMetricTOS OBJECT-TYPE 1963 SYNTAX TOSType 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The type of service metric being referenced. 1968 On row creation, this can be derived from the 1969 instance." 1970 ::= { ospfIfMetricEntry 3 } 1972 ospfIfMetricValue OBJECT-TYPE 1973 SYNTAX Metric 1974 MAX-ACCESS read-create 1975 STATUS current 1976 DESCRIPTION 1977 "The metric of using this type of service on 1978 this interface. The default value of the TOS 0 1979 Metric is 10^8 / ifSpeed." 1980 ::= { ospfIfMetricEntry 4 } 1982 ospfIfMetricStatus OBJECT-TYPE 1983 SYNTAX RowStatus 1984 MAX-ACCESS read-create 1985 STATUS current 1986 DESCRIPTION 1987 "This variable displays the status of the en- 1988 try. Setting it to 'invalid' has the effect of 1989 rendering it inoperative. The internal effect 1990 (row removal) is implementation dependent." 1991 ::= { ospfIfMetricEntry 5 } 1993 -- OSPF Virtual Interface Table 1995 -- The Virtual Interface Table describes the virtual 1996 -- links that the OSPF Process is configured to 1997 -- carry on. 1999 ospfVirtIfTable OBJECT-TYPE 2000 SYNTAX SEQUENCE OF OspfVirtIfEntry 2001 MAX-ACCESS not-accessible 2002 STATUS current 2003 DESCRIPTION 2004 "Information about this router's virtual inter- 2005 faces." 2006 REFERENCE 2007 "OSPF Version 2, Appendix C.4 Virtual link 2008 parameters" 2009 ::= { ospf 9 } 2011 ospfVirtIfEntry OBJECT-TYPE 2012 SYNTAX OspfVirtIfEntry 2013 MAX-ACCESS not-accessible 2014 STATUS current 2015 DESCRIPTION 2016 "Information about a single Virtual Interface." 2017 INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor } 2018 ::= { ospfVirtIfTable 1 } 2020 OspfVirtIfEntry ::= 2021 SEQUENCE { 2022 ospfVirtIfAreaId 2023 AreaID, 2024 ospfVirtIfNeighbor 2025 RouterID, 2026 ospfVirtIfTransitDelay 2027 UpToMaxAge, 2028 ospfVirtIfRetransInterval 2029 UpToMaxAge, 2030 ospfVirtIfHelloInterval 2031 HelloRange, 2033 ospfVirtIfRtrDeadInterval 2034 PositiveInteger, 2035 ospfVirtIfState 2036 INTEGER, 2037 ospfVirtIfEvents 2038 Counter32, 2039 ospfVirtIfAuthType 2040 INTEGER, 2041 ospfVirtIfAuthKey 2042 OCTET STRING, 2043 ospfVirtIfStatus 2044 rowStatus 2045 ospfVirtIfLsaCount 2046 Gauge32, 2047 ospfVirtIfLsaCksumSum 2048 Integer32 2049 } 2051 ospfVirtIfAreaId OBJECT-TYPE 2052 SYNTAX AreaID 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "The Transit Area that the Virtual Link 2057 traverses. By definition, this is not 0.0.0.0" 2058 ::= { ospfVirtIfEntry 1 } 2060 ospfVirtIfNeighbor OBJECT-TYPE 2061 SYNTAX RouterID 2062 MAX-ACCESS read-only 2063 STATUS current 2064 DESCRIPTION 2065 "The Router ID of the Virtual Neighbor." 2066 ::= { ospfVirtIfEntry 2 } 2068 ospfVirtIfTransitDelay OBJECT-TYPE 2069 SYNTAX UpToMaxAge 2070 MAX-ACCESS read-create 2071 STATUS current 2072 DESCRIPTION 2073 "The estimated number of seconds it takes to 2074 transmit a link-state update packet over this 2075 interface." 2076 DEFVAL { 1 } 2077 ::= { ospfVirtIfEntry 3 } 2079 ospfVirtIfRetransInterval OBJECT-TYPE 2080 SYNTAX UpToMaxAge 2081 MAX-ACCESS read-create 2082 STATUS current 2083 DESCRIPTION 2084 "The number of seconds between link-state ad- 2085 vertisement retransmissions, for adjacencies 2086 belonging to this interface. This value is 2087 also used when retransmitting database descrip- 2088 tion and link-state request packets. This 2089 value should be well over the expected round- 2090 trip time." 2091 DEFVAL { 5 } 2092 ::= { ospfVirtIfEntry 4 } 2094 ospfVirtIfHelloInterval OBJECT-TYPE 2095 SYNTAX HelloRange 2096 MAX-ACCESS read-create 2097 STATUS current 2098 DESCRIPTION 2099 "The length of time, in seconds, between the 2100 Hello packets that the router sends on the in- 2101 terface. This value must be the same for the 2102 virtual neighbor." 2103 DEFVAL { 10 } 2104 ::= { ospfVirtIfEntry 5 } 2106 ospfVirtIfRtrDeadInterval OBJECT-TYPE 2107 SYNTAX PositiveInteger 2108 MAX-ACCESS read-create 2109 STATUS current 2110 DESCRIPTION 2111 "The number of seconds that a router's Hello 2112 packets have not been seen before it's neigh- 2113 bors declare the router down. This should be 2114 some multiple of the Hello interval. This 2115 value must be the same for the virtual neigh- 2116 bor." 2117 DEFVAL { 60 } 2118 ::= { ospfVirtIfEntry 6 } 2120 ospfVirtIfState OBJECT-TYPE 2121 SYNTAX INTEGER { 2122 down (1), -- these use the same encoding 2123 pointToPoint (4) -- as the ospfIfTable 2124 } 2125 MAX-ACCESS read-only 2126 STATUS current 2127 DESCRIPTION 2128 "OSPF virtual interface states." 2129 DEFVAL { down } 2130 ::= { ospfVirtIfEntry 7 } 2132 ospfVirtIfEvents OBJECT-TYPE 2133 SYNTAX Counter32 2134 MAX-ACCESS read-only 2135 STATUS current 2136 DESCRIPTION 2137 "The number of state changes or error events on 2138 this Virtual Link" 2139 ::= { ospfVirtIfEntry 8 } 2141 ospfVirtIfAuthKey OBJECT-TYPE 2142 SYNTAX OCTET STRING (SIZE(0..256)) 2143 MAX-ACCESS read-create 2144 STATUS current 2145 DESCRIPTION 2146 "If Authentication Type is simplePassword, the 2147 device will left adjust and zero fill to 8 oc- 2148 tets. 2150 Note that unauthenticated interfaces need no 2151 authentication key, and simple password authen- 2152 tication cannot use a key of more than 8 oc- 2153 tets. Larger keys are useful only with authen- 2154 tication mechanisms not specified in this docu- 2155 ment. 2157 When read, ospfVifAuthKey always returns a 2158 string of length zero." 2159 REFERENCE 2160 "OSPF Version 2, Section 9 The Interface Data 2161 Structure" 2162 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 2163 ::= { ospfVirtIfEntry 9 } 2165 ospfVirtIfStatus OBJECT-TYPE 2166 SYNTAX RowStatus 2167 MAX-ACCESS read-create 2168 STATUS current 2169 DESCRIPTION 2170 "This variable displays the status of the en- 2171 try. Setting it to 'invalid' has the effect of 2172 rendering it inoperative. The internal effect 2173 (row removal) is implementation dependent." 2174 ::= { ospfVirtIfEntry 10 } 2176 ospfVirtIfAuthType OBJECT-TYPE 2177 SYNTAX INTEGER (0..255) 2178 -- none (0), 2179 -- simplePassword (1) 2180 -- md5 (2) 2181 -- reserved for specification by IANA (> 2) 2182 MAX-ACCESS read-create 2183 STATUS current 2184 DESCRIPTION 2185 "The authentication type specified for a virtu- 2186 al interface. Additional authentication types 2187 may be assigned locally." 2188 REFERENCE 2189 "OSPF Version 2, Appendix E Authentication" 2190 DEFVAL { 0 } -- no authentication, by default 2191 ::= { ospfVirtIfEntry 11 } 2193 ospfVirtIfLsaCount OBJECT-TYPE 2194 SYNTAX Gauge32 2195 MAX-ACCESS read-only 2196 STATUS current 2197 DESCRIPTION 2198 "The total number of link-local link state advertisements 2199 in this virtual interface's link-local link state database." 2200 ::= { ospfVirtIfEntry 12 } 2202 ospfVirtIfLsaCksumSum OBJECT-TYPE 2203 SYNTAX Integer32 2204 MAX-ACCESS read-only 2205 STATUS current 2206 DESCRIPTION 2207 "The 32-bit unsigned sum of the link-state ad- 2208 vertisements' LS checksums contained in this 2209 virtual interface's link-local link state database. 2210 The sum can be used to determine if there has 2211 been a change in the virtual interface's link state data- 2212 base, and to compare the virtual interface link-state 2213 database of the virtual neighbors." 2214 ::= { ospfVirtIfEntry 13 } 2216 -- OSPF Neighbor Table 2218 -- The OSPF Neighbor Table describes all neighbors in 2219 -- the locality of the subject router. 2221 ospfNbrTable OBJECT-TYPE 2222 SYNTAX SEQUENCE OF OspfNbrEntry 2223 MAX-ACCESS not-accessible 2224 STATUS current 2225 DESCRIPTION 2226 "A table of non-virtual neighbor information." 2227 REFERENCE 2228 "OSPF Version 2, Section 10 The Neighbor Data 2229 Structure" 2230 ::= { ospf 10 } 2232 ospfNbrEntry OBJECT-TYPE 2233 SYNTAX OspfNbrEntry 2234 MAX-ACCESS not-accessible 2235 STATUS current 2236 DESCRIPTION 2237 "The information regarding a single neighbor." 2238 REFERENCE 2239 "OSPF Version 2, Section 10 The Neighbor Data 2240 Structure" 2241 INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex } 2242 ::= { ospfNbrTable 1 } 2244 OspfNbrEntry ::= 2245 SEQUENCE { 2246 ospfNbrIpAddr 2247 IpAddress, 2248 ospfNbrAddressLessIndex 2249 InterfaceIndex, 2250 ospfNbrRtrId 2251 RouterID, 2252 ospfNbrOptions 2253 Integer32, 2254 ospfNbrPriority 2255 DesignatedRouterPriority, 2256 ospfNbrState 2257 INTEGER, 2258 ospfNbrEvents 2259 Counter32, 2260 ospfNbrLsRetransQLen 2261 Gauge32, 2262 ospfNbmaNbrStatus 2263 RowStatus, 2264 ospfNbmaNbrPermanence 2265 INTEGER, 2266 ospfNbrHelloSuppressed 2267 TruthValue 2268 } 2270 ospfNbrIpAddr OBJECT-TYPE 2271 SYNTAX IpAddress 2272 MAX-ACCESS read-only 2273 STATUS current 2274 DESCRIPTION 2275 "The IP address this neighbor is using in its 2276 IP Source Address. Note that, on addressless 2277 links, this will not be 0.0.0.0, but the ad- 2278 dress of another of the neighbor's interfaces." 2279 ::= { ospfNbrEntry 1 } 2281 ospfNbrAddressLessIndex OBJECT-TYPE 2282 SYNTAX InterfaceIndex 2283 MAX-ACCESS read-only 2284 STATUS current 2285 DESCRIPTION 2286 "On an interface having an IP Address, zero. 2288 On addressless interfaces, the corresponding 2289 value of ifIndex in the Internet Standard MIB. 2290 On row creation, this can be derived from the 2291 instance." 2292 ::= { ospfNbrEntry 2 } 2294 ospfNbrRtrId OBJECT-TYPE 2295 SYNTAX RouterID 2296 MAX-ACCESS read-only 2297 STATUS current 2298 DESCRIPTION 2299 "A 32-bit integer (represented as a type IpAd- 2300 dress) uniquely identifying the neighboring 2301 router in the Autonomous System." 2302 DEFVAL { '00000000'H } -- 0.0.0.0 2303 ::= { ospfNbrEntry 3 } 2305 ospfNbrOptions OBJECT-TYPE 2306 SYNTAX Integer32 2307 MAX-ACCESS read-only 2308 STATUS current 2309 DESCRIPTION 2310 "A Bit Mask corresponding to the neighbor's op- 2311 tions field. 2313 Bit 0, if set, indicates that the system will 2314 operate on Type of Service metrics other than 2315 TOS 0. If zero, the neighbor will ignore all 2316 metrics except the TOS 0 metric. 2318 Bit 1, if set, indicates that the associated 2319 area accepts and operates on external informa- 2320 tion; if zero, it is a stub area. 2322 Bit 2, if set, indicates that the system is ca- 2323 pable of routing IP Multicast datagrams; i.e., 2324 that it implements the Multicast Extensions to 2325 OSPF. 2327 Bit 3, if set, indicates that the associated 2328 area is an NSSA. These areas are capable of 2329 carrying type 7 external advertisements, which 2330 are translated into type 5 external advertise- 2331 ments at NSSA borders." 2332 REFERENCE 2333 "OSPF Version 2, Section 12.1.2 Options" 2334 DEFVAL { 0 } 2335 ::= { ospfNbrEntry 4 } 2337 ospfNbrPriority OBJECT-TYPE 2338 SYNTAX DesignatedRouterPriority 2339 MAX-ACCESS read-create 2340 STATUS current 2341 DESCRIPTION 2342 "The priority of this neighbor in the designat- 2343 ed router election algorithm. The value 0 sig- 2344 nifies that the neighbor is not eligible to be- 2345 come the designated router on this particular 2346 network." 2347 DEFVAL { 1 } 2348 ::= { ospfNbrEntry 5 } 2350 ospfNbrState OBJECT-TYPE 2351 SYNTAX INTEGER { 2352 down (1), 2353 attempt (2), 2354 init (3), 2355 twoWay (4), 2356 exchangeStart (5), 2357 exchange (6), 2358 loading (7), 2359 full (8) 2360 } 2361 MAX-ACCESS read-only 2362 STATUS current 2363 DESCRIPTION 2364 "The State of the relationship with this Neigh- 2365 bor." 2366 REFERENCE 2367 "OSPF Version 2, Section 10.1 Neighbor States" 2368 DEFVAL { down } 2369 ::= { ospfNbrEntry 6 } 2371 ospfNbrEvents OBJECT-TYPE 2372 SYNTAX Counter32 2373 MAX-ACCESS read-only 2374 STATUS current 2375 DESCRIPTION 2376 "The number of times this neighbor relationship 2377 has changed state, or an error has occurred." 2378 ::= { ospfNbrEntry 7 } 2380 ospfNbrLsRetransQLen OBJECT-TYPE 2381 SYNTAX Gauge32 2382 MAX-ACCESS read-only 2383 STATUS current 2384 DESCRIPTION 2385 "The current length of the retransmission 2386 queue." 2387 ::= { ospfNbrEntry 8 } 2389 ospfNbmaNbrStatus OBJECT-TYPE 2390 SYNTAX RowStatus 2391 MAX-ACCESS read-create 2392 STATUS current 2393 DESCRIPTION 2394 "This variable displays the status of the en- 2395 try. Setting it to 'invalid' has the effect of 2396 rendering it inoperative. The internal effect 2397 (row removal) is implementation dependent." 2398 ::= { ospfNbrEntry 9 } 2400 ospfNbmaNbrPermanence OBJECT-TYPE 2401 SYNTAX INTEGER { 2402 dynamic (1), -- learned through protocol 2403 permanent (2) -- configured address 2404 } 2405 MAX-ACCESS read-only 2406 STATUS current 2407 DESCRIPTION 2408 "This variable displays the status of the en- 2409 try. 'dynamic' and 'permanent' refer to how 2410 the neighbor became known." 2411 DEFVAL { permanent } 2412 ::= { ospfNbrEntry 10 } 2414 ospfNbrHelloSuppressed OBJECT-TYPE 2415 SYNTAX TruthValue 2416 MAX-ACCESS read-only 2417 STATUS current 2418 DESCRIPTION 2419 "Indicates whether Hellos are being suppressed 2420 to the neighbor" 2421 ::= { ospfNbrEntry 11 } 2423 -- OSPF Virtual Neighbor Table 2425 -- This table describes all virtual neighbors. 2426 -- Since Virtual Links are configured in the 2427 -- virtual interface table, this table is read-only. 2429 ospfVirtNbrTable OBJECT-TYPE 2430 SYNTAX SEQUENCE OF OspfVirtNbrEntry 2431 MAX-ACCESS not-accessible 2432 STATUS current 2433 DESCRIPTION 2434 "A table of virtual neighbor information." 2435 REFERENCE 2436 "OSPF Version 2, Section 15 Virtual Links" 2437 ::= { ospf 11 } 2439 ospfVirtNbrEntry OBJECT-TYPE 2440 SYNTAX OspfVirtNbrEntry 2441 MAX-ACCESS not-accessible 2442 STATUS current 2443 DESCRIPTION 2444 "Virtual neighbor information." 2445 INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId } 2446 ::= { ospfVirtNbrTable 1 } 2448 OspfVirtNbrEntry ::= 2449 SEQUENCE { 2450 ospfVirtNbrArea 2451 AreaID, 2452 ospfVirtNbrRtrId 2453 RouterID, 2454 ospfVirtNbrIpAddr 2455 IpAddress, 2456 ospfVirtNbrOptions 2457 Integer32, 2458 ospfVirtNbrState 2459 INTEGER, 2460 ospfVirtNbrEvents 2461 Counter32, 2462 ospfVirtNbrLsRetransQLen 2463 Gauge32, 2464 ospfVirtNbrHelloSuppressed 2465 TruthValue 2466 } 2468 ospfVirtNbrArea OBJECT-TYPE 2469 SYNTAX AreaID 2470 MAX-ACCESS read-only 2471 STATUS current 2472 DESCRIPTION 2473 "The Transit Area Identifier." 2474 ::= { ospfVirtNbrEntry 1 } 2476 ospfVirtNbrRtrId OBJECT-TYPE 2477 SYNTAX RouterID 2478 MAX-ACCESS read-only 2479 STATUS current 2480 DESCRIPTION 2481 "A 32-bit integer uniquely identifying the 2482 neighboring router in the Autonomous System." 2483 ::= { ospfVirtNbrEntry 2 } 2485 ospfVirtNbrIpAddr OBJECT-TYPE 2486 SYNTAX IpAddress 2487 MAX-ACCESS read-only 2488 STATUS current 2489 DESCRIPTION 2490 "The IP address this Virtual Neighbor is us- 2491 ing." 2492 ::= { ospfVirtNbrEntry 3 } 2494 ospfVirtNbrOptions OBJECT-TYPE 2495 SYNTAX Integer32 2496 MAX-ACCESS read-only 2497 STATUS current 2498 DESCRIPTION 2499 "A Bit Mask corresponding to the neighbor's op- 2500 tions field. 2502 Bit 1, if set, indicates that the system will 2503 operate on Type of Service metrics other than 2504 TOS 0. If zero, the neighbor will ignore all 2505 metrics except the TOS 0 metric. 2507 Bit 2, if set, indicates that the system is 2508 Network Multicast capable; ie, that it imple- 2509 ments OSPF Multicast Routing." 2510 ::= { ospfVirtNbrEntry 4 } 2512 ospfVirtNbrState OBJECT-TYPE 2513 SYNTAX INTEGER { 2514 down (1), 2515 attempt (2), 2516 init (3), 2517 twoWay (4), 2518 exchangeStart (5), 2519 exchange (6), 2520 loading (7), 2521 full (8) 2522 } 2523 MAX-ACCESS read-only 2524 STATUS current 2525 DESCRIPTION 2526 "The state of the Virtual Neighbor Relation- 2527 ship." 2528 ::= { ospfVirtNbrEntry 5 } 2530 ospfVirtNbrEvents OBJECT-TYPE 2531 SYNTAX Counter32 2532 MAX-ACCESS read-only 2533 STATUS current 2534 DESCRIPTION 2535 "The number of times this virtual link has 2536 changed its state, or an error has occurred." 2537 ::= { ospfVirtNbrEntry 6 } 2539 ospfVirtNbrLsRetransQLen OBJECT-TYPE 2540 SYNTAX Gauge32 2541 MAX-ACCESS read-only 2542 STATUS current 2543 DESCRIPTION 2544 "The current length of the retransmission 2545 queue." 2546 ::= { ospfVirtNbrEntry 7 } 2548 ospfVirtNbrHelloSuppressed OBJECT-TYPE 2549 SYNTAX TruthValue 2550 MAX-ACCESS read-only 2551 STATUS current 2552 DESCRIPTION 2553 "Indicates whether Hellos are being suppressed 2554 to the neighbor" 2555 ::= { ospfVirtNbrEntry 8 } 2557 -- OSPF Link State Database, External 2559 -- The Link State Database contains the Link State 2560 -- Advertisements from throughout the areas that the 2561 -- device is attached to. 2563 -- This table is identical to the OSPF LSDB Table in 2564 -- format, but contains only Link State Advertisements with 2565 -- global flooding scope. The purpose is to allow external 2566 -- LSAs to be displayed once for the router rather 2567 -- than once in each non-stub area. 2569 ospfExtLsdbTable OBJECT-TYPE 2570 SYNTAX SEQUENCE OF OspfExtLsdbEntry 2571 MAX-ACCESS not-accessible 2572 STATUS current 2573 DESCRIPTION 2574 "The OSPF Process's Links State Database." 2575 REFERENCE 2576 "OSPF Version 2, Section 12 Link State Adver- 2577 tisements" 2578 ::= { ospf 12 } 2580 ospfExtLsdbEntry OBJECT-TYPE 2581 SYNTAX OspfExtLsdbEntry 2582 MAX-ACCESS not-accessible 2583 STATUS current 2584 DESCRIPTION 2585 "A single Link State Advertisement." 2586 INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId } 2587 ::= { ospfExtLsdbTable 1 } 2589 OspfExtLsdbEntry ::= 2590 SEQUENCE { 2591 ospfExtLsdbType 2592 INTEGER, 2593 ospfExtLsdbLsid 2594 IpAddress, 2595 ospfExtLsdbRouterId 2596 RouterID, 2597 ospfExtLsdbSequence 2598 Integer32, 2599 ospfExtLsdbAge 2600 Integer32, 2601 ospfExtLsdbChecksum 2602 Integer32, 2603 ospfExtLsdbAdvertisement 2604 OCTET STRING 2605 } 2607 ospfExtLsdbType OBJECT-TYPE 2608 SYNTAX INTEGER { 2609 asExternalLink (5), 2610 asOpaqueLink (11) 2611 } 2612 MAX-ACCESS read-only 2613 STATUS current 2614 DESCRIPTION 2615 "The type of the link state advertisement. 2616 Each link state type has a separate advertise- 2617 ment format." 2618 REFERENCE 2619 "OSPF Version 2, Appendix A.4.1 The Link State 2620 Advertisement header" 2621 ::= { ospfExtLsdbEntry 1 } 2623 ospfExtLsdbLsid OBJECT-TYPE 2624 SYNTAX IpAddress 2625 MAX-ACCESS read-only 2626 STATUS current 2627 DESCRIPTION 2628 "The Link State ID is an LS Type Specific field 2629 containing either a Router ID or an IP Address; 2630 it identifies the piece of the routing domain 2631 that is being described by the advertisement." 2632 REFERENCE 2633 "OSPF Version 2, Section 12.1.4 Link State ID" 2634 ::= { ospfExtLsdbEntry 2 } 2636 ospfExtLsdbRouterId OBJECT-TYPE 2637 SYNTAX RouterID 2638 MAX-ACCESS read-only 2639 STATUS current 2640 DESCRIPTION 2641 "The 32 bit number that uniquely identifies the 2642 originating router in the Autonomous System." 2644 REFERENCE 2645 "OSPF Version 2, Appendix C.1 Global parameters" 2646 ::= { ospfExtLsdbEntry 3 } 2648 -- Note that the OSPF Sequence Number is a 32 bit signed 2649 -- integer. It starts with the value '80000001'h, 2650 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 2651 -- Thus, a typical sequence number will be very negative. 2653 ospfExtLsdbSequence OBJECT-TYPE 2654 SYNTAX Integer32 2655 MAX-ACCESS read-only 2656 STATUS current 2657 DESCRIPTION 2658 "The sequence number field is a signed 32-bit 2659 integer. It is used to detect old and dupli- 2660 cate link state advertisements. The space of 2661 sequence numbers is linearly ordered. The 2662 larger the sequence number the more recent the 2663 advertisement." 2664 REFERENCE 2665 "OSPF Version 2, Section 12.1.6 LS sequence 2666 number" 2667 ::= { ospfExtLsdbEntry 4 } 2669 ospfExtLsdbAge OBJECT-TYPE 2670 SYNTAX Integer32 -- Should be 0..MaxAge, except when 2671 -- doNotAge bit is set 2672 MAX-ACCESS read-only 2673 STATUS current 2674 DESCRIPTION 2675 "This field is the age of the link state adver- 2676 tisement in seconds." 2677 REFERENCE 2678 "OSPF Version 2, Section 12.1.1 LS age" 2679 ::= { ospfExtLsdbEntry 5 } 2681 ospfExtLsdbChecksum OBJECT-TYPE 2682 SYNTAX Integer32 2683 MAX-ACCESS read-only 2684 STATUS current 2685 DESCRIPTION 2686 "This field is the checksum of the complete 2687 contents of the advertisement, excepting the 2688 age field. The age field is excepted so that 2689 an advertisement's age can be incremented 2690 without updating the checksum. The checksum 2691 used is the same that is used for ISO connec- 2692 tionless datagrams; it is commonly referred to 2693 as the Fletcher checksum." 2694 REFERENCE 2695 "OSPF Version 2, Section 12.1.7 LS checksum" 2696 ::= { ospfExtLsdbEntry 6 } 2698 ospfExtLsdbAdvertisement OBJECT-TYPE 2699 SYNTAX OCTET STRING (SIZE(36)) 2700 MAX-ACCESS read-only 2701 STATUS current 2702 DESCRIPTION 2703 "The entire Link State Advertisement, including 2704 its header." 2705 REFERENCE 2706 "OSPF Version 2, Section 12 Link State Adver- 2707 tisements" 2708 ::= { ospfExtLsdbEntry 7 } 2710 -- OSPF Use of the CIDR Route Table 2712 ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 } 2714 -- The IP Forwarding Table defines a number of objects for use by 2715 -- the routing protocol to externalize its information. Most of 2716 -- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy, 2717 -- ipForwardNextHop, ipForwardIfIndex, ipForwardType, 2718 -- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are 2719 -- defined there. 2721 -- Those that leave some discretion are defined here. 2723 -- ipCidrRouteProto is, of course, ospf (13). 2725 -- ipCidrRouteAge is the time since the route was first calculated, 2726 -- as opposed to the time since the last SPF run. 2728 -- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing 2729 -- protocol. The following values shall be found there depending 2730 -- on the way the route was calculated. 2732 ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 } 2733 ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 } 2734 ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 } 2735 ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 } 2737 -- ipCidrRouteMetric1 is, by definition, the primary routing 2738 -- metric. Therefore, it should be the metric that route 2739 -- selection is based on. For intra-area and inter-area routes, 2740 -- it is an OSPF metric. For External Type 1 (comparable value) 2741 -- routes, it is an OSPF metric plus the External Metric. For 2742 -- external Type 2 (non-comparable value) routes, it is the 2743 -- external metric. 2745 -- ipCidrRouteMetric2 is, by definition, a secondary routing 2746 -- metric. Therefore, it should be the metric that breaks a tie 2747 -- among routes having equal metric1 values and the same 2748 -- calculation rule. For intra-area, inter-area routes, and 2749 -- External Type 1 (comparable value) routes, it is unused. For 2750 -- external Type 2 (non-comparable value) routes, it is the metric 2751 -- to the AS border router. 2753 -- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 2754 -- are unused. 2756 -- The OSPF Area Aggregate Table 2757 -- 2758 -- This table replaces the OSPF Area Summary Table, being an 2759 -- extension of that for CIDR routers. 2761 ospfAreaAggregateTable OBJECT-TYPE 2762 SYNTAX SEQUENCE OF OspfAreaAggregateEntry 2763 MAX-ACCESS not-accessible 2764 STATUS current 2765 DESCRIPTION 2766 "A range of IP addresses specified by an IP 2767 address/IP network mask pair. For example, 2768 class B address range of X.X.X.X with a network 2769 mask of 255.255.0.0 includes all IP addresses 2770 from X.X.0.0 to X.X.255.255. Note that if 2771 ranges are configured such that one range sub- 2772 sumes another range (e.g., 10.0.0.0 mask 2773 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2774 most specific match is the preferred one." 2775 REFERENCE 2776 "OSPF Version 2, Appendix C.2 Area parameters" 2777 ::= { ospf 14 } 2779 ospfAreaAggregateEntry OBJECT-TYPE 2780 SYNTAX OspfAreaAggregateEntry 2781 MAX-ACCESS not-accessible 2782 STATUS current 2783 DESCRIPTION 2784 "A range of IP addresses specified by an IP 2785 address/IP network mask pair. For example, 2786 class B address range of X.X.X.X with a network 2787 mask of 255.255.0.0 includes all IP addresses 2788 from X.X.0.0 to X.X.255.255. Note that if 2789 ranges are range configured such that one range 2790 subsumes another range (e.g., 10.0.0.0 mask 2791 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2792 most specific match is the preferred one." 2793 REFERENCE 2794 "OSPF Version 2, Appendix C.2 Area parameters" 2795 INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType, 2796 ospfAreaAggregateNet, ospfAreaAggregateMask } 2797 ::= { ospfAreaAggregateTable 1 } 2799 OspfAreaAggregateEntry ::= 2800 SEQUENCE { 2801 ospfAreaAggregateAreaID 2802 AreaID, 2803 ospfAreaAggregateLsdbType 2804 INTEGER, 2805 ospfAreaAggregateNet 2806 IpAddress, 2807 ospfAreaAggregateMask 2808 IpAddress, 2809 ospfAreaAggregateStatus 2810 RowStatus, 2811 ospfAreaAggregateEffect 2812 INTEGER 2813 } 2815 ospfAreaAggregateAreaID OBJECT-TYPE 2816 SYNTAX AreaID 2817 MAX-ACCESS read-only 2818 STATUS current 2819 DESCRIPTION 2820 "The Area the Address Aggregate is to be found 2821 within." 2822 REFERENCE 2823 "OSPF Version 2, Appendix C.2 Area parameters" 2824 ::= { ospfAreaAggregateEntry 1 } 2826 ospfAreaAggregateLsdbType OBJECT-TYPE 2827 SYNTAX INTEGER { 2828 summaryLink (3), 2829 nssaExternalLink (7) 2830 } 2831 MAX-ACCESS read-only 2832 STATUS current 2833 DESCRIPTION 2834 "The type of the Address Aggregate. This field 2835 specifies the Lsdb type that this Address Ag- 2836 gregate applies to." 2837 REFERENCE 2838 "OSPF Version 2, Appendix A.4.1 The Link State 2839 Advertisement header" 2840 ::= { ospfAreaAggregateEntry 2 } 2842 ospfAreaAggregateNet OBJECT-TYPE 2843 SYNTAX IpAddress 2844 MAX-ACCESS read-only 2845 STATUS current 2846 DESCRIPTION 2847 "The IP Address of the Net or Subnet indicated 2848 by the range." 2849 REFERENCE 2850 "OSPF Version 2, Appendix C.2 Area parameters" 2851 ::= { ospfAreaAggregateEntry 3 } 2853 ospfAreaAggregateMask OBJECT-TYPE 2854 SYNTAX IpAddress 2855 MAX-ACCESS read-only 2856 STATUS current 2857 DESCRIPTION 2858 "The Subnet Mask that pertains to the Net or 2859 Subnet." 2860 REFERENCE 2861 "OSPF Version 2, Appendix C.2 Area parameters" 2862 ::= { ospfAreaAggregateEntry 4 } 2864 ospfAreaAggregateStatus OBJECT-TYPE 2865 SYNTAX RowStatus 2866 MAX-ACCESS read-create 2867 STATUS current 2868 DESCRIPTION 2869 "This variable displays the status of the en- 2870 try. Setting it to 'invalid' has the effect of 2871 rendering it inoperative. The internal effect 2872 (row removal) is implementation dependent." 2873 ::= { ospfAreaAggregateEntry 5 } 2875 ospfAreaAggregateEffect OBJECT-TYPE 2876 SYNTAX INTEGER { 2877 advertiseMatching (1), 2878 doNotAdvertiseMatching (2) 2879 } 2880 MAX-ACCESS read-create 2881 STATUS current 2882 DESCRIPTION 2883 "Subnets subsumed by ranges either trigger the 2884 advertisement of the indicated aggregate (ad- 2885 vertiseMatching), or result in the subnet's not 2886 being advertised at all outside the area." 2887 DEFVAL { advertiseMatching } 2888 ::= { ospfAreaAggregateEntry 6 } 2890 -- OSPF Link State Database, Link-Local for non-virtual links 2892 -- This table is identical to the OSPF LSDB Table in 2893 -- format, but contains only Link-Local Link State 2894 -- Advertisements for non-virtual links. The purpose is 2895 -- to allow Link-Local LSAs to be displayed for each 2896 -- non-virtual interface. This table is implemented to 2897 -- support type-9 LSAs which are defined in 2898 -- "The OSPF Opaque LSA Option". 2900 ospfLocalLsdbTable OBJECT-TYPE 2901 SYNTAX SEQUENCE OF OspfLocalLsdbEntry 2902 MAX-ACCESS not-accessible 2903 STATUS current 2904 DESCRIPTION 2905 "The OSPF Process's Link-Local Link State Database 2906 for non-virtual links." 2907 REFERENCE 2908 "OSPF Version 2, Section 12 Link State Adver- 2909 tisements and The OSPF Opaque LSA Option" 2910 ::= { ospf 15 } 2912 ospfLocalLsdbEntry OBJECT-TYPE 2913 SYNTAX OspfLocalLsdbEntry 2914 MAX-ACCESS not-accessible 2915 STATUS current 2916 DESCRIPTION 2917 "A single Link State Advertisement." 2918 INDEX { ospfLocalLsdbIpAddress, ospfLocalLsdbAddressLessIf, 2919 ospfLocalLsdbType, ospfLocalLsdbLsid, ospfLocalLsdbRouterId 2920 } 2921 ::= { ospfLocalLsdbTable 1 } 2923 OspfLocalLsdbEntry ::= 2924 SEQUENCE { 2925 ospfLocalLsdbIpAddress 2926 IpAddress, 2927 ospfLocalLsdbAddressLessIf 2928 Integer32, 2929 ospfLocalLsdbType 2930 INTEGER, 2931 ospfLocalLsdbLsid 2932 IpAddress, 2933 ospfLocalLsdbRouterId 2934 RouterID, 2935 ospfLocalLsdbSequence 2936 Integer32, 2937 ospfLocalLsdbAge 2938 Integer32, 2939 ospfLocalLsdbChecksum 2940 Integer32, 2941 ospfLocalLsdbAdvertisement 2942 OCTET STRING 2943 } 2945 ospfLocalLsdbIpAddress OBJECT-TYPE 2946 SYNTAX IpAddress 2947 MAX-ACCESS read-only 2948 STATUS current 2949 DESCRIPTION 2950 "The IP Address of the interface from 2951 which the LSA was received if the interface is 2952 numbered." 2953 REFERENCE 2954 "OSPF Version 2, Appendix C.3 Interface parameters" 2955 ::= { ospfLocalLsdbEntry 1 } 2957 ospfLocalLsdbAddressLessIf OBJECT-TYPE 2958 SYNTAX Integer32 2959 MAX-ACCESS read-only 2960 STATUS current 2961 DESCRIPTION 2962 "The Interface Index of the interface from 2963 which the LSA was received if the interface is 2964 unnumbered." 2965 REFERENCE 2966 "OSPF Version 2, Appendix C.3 Interface parameters" 2967 ::= { ospfLocalLsdbEntry 2 } 2969 ospfLocalLsdbType OBJECT-TYPE 2970 SYNTAX INTEGER { localOpaqueLink (9) } 2971 MAX-ACCESS read-only 2972 STATUS current 2973 DESCRIPTION 2974 "The type of the link state advertisement. 2975 Each link state type has a separate advertise- 2976 ment format." 2977 REFERENCE 2978 "OSPF Version 2, Appendix A.4.1 The Link State 2979 Advertisement header and " 2980 ::= { ospfLocalLsdbEntry 3 } 2982 ospfLocalLsdbLsid OBJECT-TYPE 2983 SYNTAX IpAddress 2984 MAX-ACCESS read-only 2985 STATUS current 2986 DESCRIPTION 2987 "The Link State ID is an LS Type Specific field 2988 containing a 32 bit identifier in IP address format; 2989 it identifies the piece of the routing domain 2990 that is being described by the advertisement." 2991 REFERENCE 2992 "OSPF Version 2, Section 12.1.4 Link State ID" 2993 ::= { ospfLocalLsdbEntry 4 } 2995 ospfLocalLsdbRouterId OBJECT-TYPE 2996 SYNTAX RouterID 2997 MAX-ACCESS read-only 2998 STATUS current 2999 DESCRIPTION 3000 "The 32 bit number that uniquely identifies the 3001 originating router in the Autonomous System." 3002 REFERENCE 3003 "OSPF Version 2, Appendix C.1 Global parameters" 3004 ::= { ospfLocalLsdbEntry 5 } 3006 -- Note that the OSPF Sequence Number is a 32 bit signed 3007 -- integer. It starts with the value '80000001'h, 3008 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 3009 -- Thus, a typical sequence number will be very negative. 3011 ospfLocalLsdbSequence OBJECT-TYPE 3012 SYNTAX Integer32 3013 MAX-ACCESS read-only 3014 STATUS current 3015 DESCRIPTION 3016 "The sequence number field is a signed 32-bit 3017 integer. It is used to detect old and dupli- 3018 cate link state advertisements. The space of 3019 sequence numbers is linearly ordered. The 3020 larger the sequence number the more recent the 3021 advertisement." 3022 REFERENCE 3023 "OSPF Version 2, Section 12.1.6 LS sequence 3024 number" 3025 ::= { ospfLocalLsdbEntry 6 } 3027 ospfLocalLsdbAge OBJECT-TYPE 3028 SYNTAX Integer32 -- Should be 0..MaxAge, except when 3029 -- doNotAge bit is set 3030 MAX-ACCESS read-only 3031 STATUS current 3032 DESCRIPTION 3033 "This field is the age of the link state adver- 3034 tisement in seconds." 3035 REFERENCE 3036 "OSPF Version 2, Section 12.1.1 LS age" 3037 ::= { ospfLocalLsdbEntry 7 } 3039 ospfLocalLsdbChecksum OBJECT-TYPE 3040 SYNTAX Integer32 3041 MAX-ACCESS read-only 3042 STATUS current 3043 DESCRIPTION 3044 "This field is the checksum of the complete 3045 contents of the advertisement, excepting the 3046 age field. The age field is excepted so that 3047 an advertisement's age can be incremented 3048 without updating the checksum. The checksum 3049 used is the same that is used for ISO connec- 3050 tionless datagrams; it is commonly referred to 3051 as the Fletcher checksum." 3052 REFERENCE 3053 "OSPF Version 2, Section 12.1.7 LS checksum" 3054 ::= { ospfLocalLsdbEntry 8 } 3056 ospfLocalLsdbAdvertisement OBJECT-TYPE 3057 SYNTAX OCTET STRING (SIZE (1..65535)) 3058 MAX-ACCESS read-only 3059 STATUS current 3060 DESCRIPTION 3061 "The entire Link State Advertisement, including 3062 its header." 3063 REFERENCE 3064 "OSPF Version 2, Section 12 Link State Adver- 3065 tisements" 3066 ::= { ospfLocalLsdbEntry 9 } 3068 -- OSPF Link State Database, Link-Local for virtual Links 3070 -- This table is identical to the OSPF LSDB Table in 3071 -- format, but contains only Link-Local Link State 3072 -- Advertisements for virtual links. The purpose is to 3073 -- allow Link-Local LSAs to be displayed for each virtual 3074 -- interface. This table is implemented to support type-9 LSAs 3075 -- which are defined in "The OSPF Opaque LSA Option". 3077 ospfVirtLocalLsdbTable OBJECT-TYPE 3078 SYNTAX SEQUENCE OF OspfVirtLocalLsdbEntry 3079 MAX-ACCESS not-accessible 3080 STATUS current 3081 DESCRIPTION 3082 "The OSPF Process's Link-Local Link State Database 3083 for virtual links." 3084 REFERENCE 3085 "OSPF Version 2, Section 12 Link State Adver- 3086 tisements and The OSPF Opaque LSA Option" 3087 ::= { ospf 16 } 3089 ospfVirtLocalLsdbEntry OBJECT-TYPE 3090 SYNTAX OspfVirtLocalLsdbEntry 3091 MAX-ACCESS not-accessible 3092 STATUS current 3093 DESCRIPTION 3094 "A single Link State Advertisement." 3095 INDEX { ospfVirtLocalLsdbTransitArea, 3096 ospfVirtLocalLsdbNeighbor, 3097 ospfVirtLocalLsdbType, 3098 ospfVirtLocalLsdbLsid, 3099 ospfVirtLocalLsdbRouterId 3100 } 3101 ::= { ospfVirtLocalLsdbTable 1 } 3103 OspfVirtLocalLsdbEntry ::= 3104 SEQUENCE { 3105 ospfVirtLocalLsdbTransitArea 3106 AreaID, 3107 ospfVirtLocalLsdbNeighbor 3108 RouterID, 3109 ospfVirtLocalLsdbType 3110 INTEGER, 3111 ospfVirtLocalLsdbLsid 3112 IpAddress, 3113 ospfVirtLocalLsdbRouterId 3114 RouterID, 3115 ospfVirtLocalLsdbSequence 3116 Integer32, 3117 ospfVirtLocalLsdbAge 3118 Integer32, 3119 ospfVirtLocalLsdbChecksum 3120 Integer32, 3121 ospfVirtLocalLsdbAdvertisement 3122 OCTET STRING 3123 } 3125 ospfVirtLocalLsdbTransitArea OBJECT-TYPE 3126 SYNTAX AreaID 3127 MAX-ACCESS read-only 3128 STATUS current 3129 DESCRIPTION 3130 "The Transit Area that the Virtual Link 3131 traverses. By definition, this is not 0.0.0.0" 3132 REFERENCE 3133 "OSPF Version 2, Appendix C.3 Interface parameters" 3134 ::= { ospfVirtLocalLsdbEntry 1 } 3136 ospfVirtLocalLsdbNeighbor OBJECT-TYPE 3137 SYNTAX RouterID 3138 MAX-ACCESS read-only 3139 STATUS current 3140 DESCRIPTION 3141 "The Router ID of the Virtual Neighbor." 3142 REFERENCE 3143 "OSPF Version 2, Appendix C.3 Interface parameters" 3144 ::= { ospfVirtLocalLsdbEntry 2 } 3146 ospfVirtLocalLsdbType OBJECT-TYPE 3147 SYNTAX INTEGER { localOpaqueLink (9) } 3148 MAX-ACCESS read-only 3149 STATUS current 3150 DESCRIPTION 3151 "The type of the link state advertisement. 3152 Each link state type has a separate advertise- 3153 ment format." 3154 REFERENCE 3155 "OSPF Version 2, Appendix A.4.1 The Link State 3156 Advertisement header and " 3157 ::= { ospfVirtLocalLsdbEntry 3 } 3159 ospfVirtLocalLsdbLsid OBJECT-TYPE 3160 SYNTAX IpAddress 3161 MAX-ACCESS read-only 3162 STATUS current 3163 DESCRIPTION 3164 "The Link State ID is an LS Type Specific field 3165 containing a 32 bit identifier in IP address format; 3166 it identifies the piece of the routing domain 3167 that is being described by the advertisement." 3168 REFERENCE 3169 "OSPF Version 2, Section 12.1.4 Link State ID" 3170 ::= { ospfVirtLocalLsdbEntry 4 } 3172 ospfVirtLocalLsdbRouterId OBJECT-TYPE 3173 SYNTAX RouterID 3174 MAX-ACCESS read-only 3175 STATUS current 3176 DESCRIPTION 3177 "The 32 bit number that uniquely identifies the 3178 originating router in the Autonomous System." 3179 REFERENCE 3180 "OSPF Version 2, Appendix C.1 Global parameters" 3181 ::= { ospfVirtLocalLsdbEntry 5 } 3183 -- Note that the OSPF Sequence Number is a 32 bit signed 3184 -- integer. It starts with the value '80000001'h, 3185 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 3186 -- Thus, a typical sequence number will be very negative. 3188 ospfVirtLocalLsdbSequence OBJECT-TYPE 3189 SYNTAX Integer32 3190 MAX-ACCESS read-only 3191 STATUS current 3192 DESCRIPTION 3193 "The sequence number field is a signed 32-bit 3194 integer. It is used to detect old and dupli- 3195 cate link state advertisements. The space of 3196 sequence numbers is linearly ordered. The 3197 larger the sequence number the more recent the 3198 advertisement." 3199 REFERENCE 3200 "OSPF Version 2, Section 12.1.6 LS sequence 3201 number" 3203 ::= { ospfVirtLocalLsdbEntry 6 } 3205 ospfVirtLocalLsdbAge OBJECT-TYPE 3206 SYNTAX Integer32 -- Should be 0..MaxAge, except when 3207 -- doNotAge bit is set 3208 MAX-ACCESS read-only 3209 STATUS current 3210 DESCRIPTION 3211 "This field is the age of the link state adver- 3212 tisement in seconds." 3213 REFERENCE 3214 "OSPF Version 2, Section 12.1.1 LS age" 3215 ::= { ospfVirtLocalLsdbEntry 7 } 3217 ospfVirtLocalLsdbChecksum OBJECT-TYPE 3218 SYNTAX Integer32 3219 MAX-ACCESS read-only 3220 STATUS current 3221 DESCRIPTION 3222 "This field is the checksum of the complete 3223 contents of the advertisement, excepting the 3224 age field. The age field is excepted so that 3225 an advertisement's age can be incremented 3226 without updating the checksum. The checksum 3227 used is the same that is used for ISO connec- 3228 tionless datagrams; it is commonly referred to 3229 as the Fletcher checksum." 3230 REFERENCE 3231 "OSPF Version 2, Section 12.1.7 LS checksum" 3232 ::= { ospfVirtLocalLsdbEntry 8 } 3234 ospfVirtLocalLsdbAdvertisement OBJECT-TYPE 3235 SYNTAX OCTET STRING (SIZE (1..65535)) 3236 MAX-ACCESS read-only 3237 STATUS current 3238 DESCRIPTION 3239 "The entire Link State Advertisement, including 3240 its header." 3241 REFERENCE 3242 "OSPF Version 2, Section 12 Link State Adver- 3243 tisements" 3244 ::= { ospfVirtLocalLsdbEntry 9 } 3246 -- conformance information 3248 ospfConformance OBJECT IDENTIFIER ::= { ospf 20 } 3250 ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 } 3251 ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 } 3252 -- compliance statements 3254 -- This compliance statement is deprecated and replaced 3255 -- by ospfCompliance2 3257 ospfCompliance MODULE-COMPLIANCE 3258 STATUS deprecated 3259 DESCRIPTION 3260 "The compliance statement." 3261 MODULE -- this module 3262 MANDATORY-GROUPS { 3263 ospfBasicGroup, 3264 ospfAreaGroup, 3265 ospfStubAreaGroup, 3266 ospfIfGroup, 3267 ospfIfMetricGroup, 3268 ospfVirtIfGroup, 3269 ospfNbrGroup, 3270 ospfVirtNbrGroup, 3271 ospfAreaAggregateGroup 3272 } 3273 ::= { ospfCompliances 1 } 3275 ospfCompliance2 MODULE-COMPLIANCE 3276 STATUS current 3277 DESCRIPTION 3278 "The compliance statement." 3279 MODULE -- this module 3280 MANDATORY-GROUPS { 3281 ospfBasicGroup2, 3282 ospfAreaGroup2, 3283 ospfStubAreaGroup, 3284 ospfIfGroup2, 3285 ospfIfMetricGroup, 3286 ospfVirtIfGroup2, 3287 ospfNbrGroup, 3288 ospfVirtNbrGroup, 3289 ospfAreaAggregateGroup 3290 } 3291 GROUP ospfHostGroup 3292 DESCRIPTION 3293 "This group is mandatory for OSPF systems that support 3294 attached hosts." 3295 GROUP ospfLsdbGroup 3296 DESCRIPTION 3297 "This group is mandatory for OSPF systems that display 3298 their per-area link state database." 3299 GROUP ospfExtLsdbGroup 3300 DESCRIPTION 3301 "This group is mandatory for OSPF systems that display 3302 their AS link state database." 3304 GROUP ospfLocalLsdbGroup 3305 DESCRIPTION 3306 "This group is mandatory for OSPF systems that display 3307 their per-link link state database for non-virtual 3308 links." 3309 GROUP ospfVirtLocalLsdbGroup 3310 DESCRIPTION 3311 "This group is mandatory for OSPF systems that display 3312 their per-link link state database for virtual links." 3313 ::= { ospfCompliances 2 } 3315 -- units of conformance 3317 -- This object group is deprecated and replaced by ospfBasicGroup2 3319 ospfBasicGroup OBJECT-GROUP 3320 OBJECTS { 3321 ospfRouterId, 3322 ospfAdminStat, 3323 ospfVersionNumber, 3324 ospfAreaBdrRtrStatus, 3325 ospfASBdrRtrStatus, 3326 ospfExternLsaCount, 3327 ospfExternLsaCksumSum, 3328 ospfTOSSupport, 3329 ospfOriginateNewLsas, 3330 ospfRxNewLsas, 3331 ospfExtLsdbLimit, 3332 ospfMulticastExtensions, 3333 ospfExitOverflowInterval, 3334 ospfDemandExtensions 3335 } 3336 STATUS deprecated 3337 DESCRIPTION 3338 "These objects are required for OSPF systems." 3339 ::= { ospfGroups 1 } 3341 -- This object group is deprecated and replaced by ospfAreaGroup2 3343 ospfAreaGroup OBJECT-GROUP 3344 OBJECTS { 3345 ospfAreaId, 3346 ospfImportAsExtern, 3347 ospfSpfRuns, 3348 ospfAreaBdrRtrCount, 3349 ospfAsBdrRtrCount, 3350 ospfAreaLsaCount, 3351 ospfAreaLsaCksumSum, 3352 ospfAreaSummary, 3353 ospfAreaStatus 3354 } 3355 STATUS current 3356 DESCRIPTION 3357 "These objects are required for OSPF systems 3358 supporting areas. This statement is included 3359 for backwards-compatibility. The ospfAreaGroup2 3360 statement is recommended" 3361 ::= { ospfGroups 2 } 3363 ospfStubAreaGroup OBJECT-GROUP 3364 OBJECTS { 3365 ospfStubAreaId, 3366 ospfStubTOS, 3367 ospfStubMetric, 3368 ospfStubStatus, 3369 ospfStubMetricType 3370 } 3371 STATUS current 3372 DESCRIPTION 3373 "These objects are required for OSPF systems 3374 supporting stub areas." 3375 ::= { ospfGroups 3 } 3377 ospfLsdbGroup OBJECT-GROUP 3378 OBJECTS { 3379 ospfLsdbAreaId, 3380 ospfLsdbType, 3381 ospfLsdbLsid, 3382 ospfLsdbRouterId, 3383 ospfLsdbSequence, 3384 ospfLsdbAge, 3385 ospfLsdbChecksum, 3386 ospfLsdbAdvertisement 3387 } 3388 STATUS current 3389 DESCRIPTION 3390 "These objects are required for OSPF systems 3391 that display their link state database." 3392 ::= { ospfGroups 4 } 3394 ospfAreaRangeGroup OBJECT-GROUP 3395 OBJECTS { 3396 ospfAreaRangeAreaId, 3397 ospfAreaRangeNet, 3398 ospfAreaRangeMask, 3399 ospfAreaRangeStatus, 3400 ospfAreaRangeEffect 3401 } 3402 STATUS obsolete 3403 DESCRIPTION 3404 "These objects are required for non-CIDR OSPF 3405 systems that support multiple areas." 3406 ::= { ospfGroups 5 } 3408 ospfHostGroup OBJECT-GROUP 3409 OBJECTS { 3410 ospfHostIpAddress, 3411 ospfHostTOS, 3412 ospfHostMetric, 3413 ospfHostStatus, 3414 ospfHostAreaID 3415 } 3416 STATUS current 3417 DESCRIPTION 3418 "These objects are required for OSPF systems 3419 that support attached hosts." 3420 ::= { ospfGroups 6 } 3422 -- This object group is deprecated and replaced by ospfIfGroup2 3424 ospfIfGroup OBJECT-GROUP 3425 OBJECTS { 3426 ospfIfIpAddress, 3427 ospfAddressLessIf, 3428 ospfIfAreaId, 3429 ospfIfType, 3430 ospfIfAdminStat, 3431 ospfIfRtrPriority, 3432 ospfIfTransitDelay, 3433 ospfIfRetransInterval, 3434 ospfIfHelloInterval, 3435 ospfIfRtrDeadInterval, 3436 ospfIfPollInterval, 3437 ospfIfState, 3438 ospfIfDesignatedRouter, 3439 ospfIfBackupDesignatedRouter, 3440 ospfIfEvents, 3441 ospfIfAuthType, 3442 ospfIfAuthKey, 3443 ospfIfStatus, 3444 ospfIfMulticastForwarding, 3445 ospfIfDemand 3446 } 3447 STATUS deprecated 3448 DESCRIPTION 3449 "These objects are required for OSPF systems." 3450 ::= { ospfGroups 7 } 3452 ospfIfMetricGroup OBJECT-GROUP 3453 OBJECTS { 3454 ospfIfMetricIpAddress, 3455 ospfIfMetricAddressLessIf, 3456 ospfIfMetricTOS, 3457 ospfIfMetricValue, 3458 ospfIfMetricStatus 3459 } 3460 STATUS current 3461 DESCRIPTION 3462 "These objects are required for OSPF systems." 3463 ::= { ospfGroups 8 } 3465 -- This object group is deprecated and replaced by ospfVirtIfGroup2 3467 ospfVirtIfGroup OBJECT-GROUP 3468 OBJECTS { 3469 ospfVirtIfAreaId, 3470 ospfVirtIfNeighbor, 3471 ospfVirtIfTransitDelay, 3472 ospfVirtIfRetransInterval, 3473 ospfVirtIfHelloInterval, 3474 ospfVirtIfRtrDeadInterval, 3475 ospfVirtIfState, 3476 ospfVirtIfEvents, 3477 ospfVirtIfAuthType, 3478 ospfVirtIfAuthKey, 3479 ospfVirtIfStatus 3480 } 3481 STATUS deprecated 3482 DESCRIPTION 3483 "These objects are required for OSPF systems." 3484 ::= { ospfGroups 9 } 3486 ospfNbrGroup OBJECT-GROUP 3487 OBJECTS { 3488 ospfNbrIpAddr, 3489 ospfNbrAddressLessIndex, 3490 ospfNbrRtrId, 3491 ospfNbrOptions, 3492 ospfNbrPriority, 3493 ospfNbrState, 3494 ospfNbrEvents, 3495 ospfNbrLsRetransQLen, 3496 ospfNbmaNbrStatus, 3497 ospfNbmaNbrPermanence, 3498 ospfNbrHelloSuppressed 3499 } 3500 STATUS current 3501 DESCRIPTION 3502 "These objects are required for OSPF systems." 3503 ::= { ospfGroups 10 } 3505 ospfVirtNbrGroup OBJECT-GROUP 3506 OBJECTS { 3507 ospfVirtNbrArea, 3508 ospfVirtNbrRtrId, 3509 ospfVirtNbrIpAddr, 3510 ospfVirtNbrOptions, 3511 ospfVirtNbrState, 3512 ospfVirtNbrEvents, 3513 ospfVirtNbrLsRetransQLen, 3514 ospfVirtNbrHelloSuppressed 3515 } 3516 STATUS current 3517 DESCRIPTION 3518 "These objects are required for OSPF systems." 3519 ::= { ospfGroups 11 } 3521 ospfExtLsdbGroup OBJECT-GROUP 3522 OBJECTS { 3523 ospfExtLsdbType, 3524 ospfExtLsdbLsid, 3525 ospfExtLsdbRouterId, 3526 ospfExtLsdbSequence, 3527 ospfExtLsdbAge, 3528 ospfExtLsdbChecksum, 3529 ospfExtLsdbAdvertisement 3530 } 3531 STATUS current 3532 DESCRIPTION 3533 "These objects are required for OSPF systems 3534 that display their link state database." 3535 ::= { ospfGroups 12 } 3537 ospfAreaAggregateGroup OBJECT-GROUP 3538 OBJECTS { 3539 ospfAreaAggregateAreaID, 3540 ospfAreaAggregateLsdbType, 3541 ospfAreaAggregateNet, 3542 ospfAreaAggregateMask, 3543 ospfAreaAggregateStatus, 3544 ospfAreaAggregateEffect 3545 } 3546 STATUS current 3547 DESCRIPTION 3548 "These objects are required for OSPF systems." 3549 ::= { ospfGroups 13 } 3551 ospfLocalLsdbGroup OBJECT-GROUP 3552 OBJECTS { 3553 ospfLocalLsdbIpAddress, 3554 ospfLocalLsdbAddressLessIf, 3555 ospfLocalLsdbType, 3556 ospfLocalLsdbLsid, 3557 ospfLocalLsdbRouterId, 3558 ospfLocalLsdbSequence, 3559 ospfLocalLsdbAge, 3560 ospfLocalLsdbChecksum, 3561 ospfLocalLsdbAdvertisement 3562 } 3563 STATUS current 3564 DESCRIPTION 3565 "These objects are required for OSPF systems 3566 that display their Link-Local link state databases 3567 for non-virtual links." 3568 ::= { ospfGroups 14 } 3570 ospfVirtLocalLsdbGroup OBJECT-GROUP 3571 OBJECTS { 3572 ospfVirtLocalLsdbTransitArea, 3573 ospfVirtLocalLsdbNeighbor, 3574 ospfVirtLocalLsdbType, 3575 ospfVirtLocalLsdbLsid, 3576 ospfVirtLocalLsdbRouterId, 3577 ospfVirtLocalLsdbSequence, 3578 ospfVirtLocalLsdbAge, 3579 ospfVirtLocalLsdbChecksum, 3580 ospfVirtLocalLsdbAdvertisement 3581 } 3582 STATUS current 3583 DESCRIPTION 3584 "These objects are required for OSPF systems 3585 that display their Link-Local link state databases 3586 for virtual links." 3587 ::= { ospfGroups 15 } 3589 ospfBasicGroup2 OBJECT-GROUP 3590 OBJECTS { 3591 ospfRouterId, 3592 ospfAdminStat, 3593 ospfVersionNumber, 3594 ospfAreaBdrRtrStatus, 3595 ospfASBdrRtrStatus, 3596 ospfExternLsaCount, 3597 ospfExternLsaCksumSum, 3598 ospfTOSSupport, 3599 ospfOriginateNewLsas, 3600 ospfRxNewLsas, 3601 ospfExtLsdbLimit, 3602 ospfMulticastExtensions, 3603 ospfExitOverflowInterval, 3604 ospfDemandExtensions, 3605 ospfRFC1583Compatibility, 3606 ospfOpaqueLsaSupport, 3607 ospfTrafficEngineeringSupport, 3608 ospfAsOpaqueLsdbLimit 3609 } 3610 STATUS current 3611 DESCRIPTION 3612 "These objects are required for OSPF systems." 3613 ::= { ospfGroups 16 } 3615 ospfAreaGroup2 OBJECT-GROUP 3616 OBJECTS { 3617 ospfAreaId, 3618 ospfImportAsExtern, 3619 ospfSpfRuns, 3620 ospfAreaBdrRtrCount, 3621 ospfAsBdrRtrCount, 3622 ospfAreaLsaCount, 3623 ospfAreaLsaCksumSum, 3624 ospfAreaSummary, 3625 ospfAreaStatus, 3626 ospfAreaNssaTranslatorRole, 3627 ospfAreaNssaTranslatorState, 3628 ospfAreaNssaTranslatorStabilityInterval, 3629 ospfAreaNssaTranslatorEvents 3630 } 3631 STATUS current 3632 DESCRIPTION 3633 "These objects are required for OSPF systems 3634 supporting areas. This statement is recommended 3635 for use. " 3636 ::= { ospfGroups 17 } 3638 ospfIfGroup2 OBJECT-GROUP 3639 OBJECTS { 3640 ospfIfIpAddress, 3641 ospfAddressLessIf, 3642 ospfIfAreaId, 3643 ospfIfType, 3644 ospfIfAdminStat, 3645 ospfIfRtrPriority, 3646 ospfIfTransitDelay, 3647 ospfIfRetransInterval, 3648 ospfIfHelloInterval, 3649 ospfIfRtrDeadInterval, 3650 ospfIfPollInterval, 3651 ospfIfState, 3652 ospfIfDesignatedRouter, 3653 ospfIfBackupDesignatedRouter, 3654 ospfIfEvents, 3655 ospfIfAuthType, 3656 ospfIfAuthKey, 3657 ospfIfStatus, 3658 ospfIfMulticastForwarding, 3659 ospfIfDemand, 3660 ospfIfLsaCount, 3661 ospfIfLsaCksumSum 3662 } 3663 STATUS current 3664 DESCRIPTION 3665 "These objects are required for OSPF systems." 3666 ::= { ospfGroups 18 } 3668 ospfVirtIfGroup2 OBJECT-GROUP 3669 OBJECTS { 3670 ospfVirtIfAreaId, 3671 ospfVirtIfNeighbor, 3672 ospfVirtIfTransitDelay, 3673 ospfVirtIfRetransInterval, 3674 ospfVirtIfHelloInterval, 3675 ospfVirtIfRtrDeadInterval, 3676 ospfVirtIfState, 3677 ospfVirtIfEvents, 3678 ospfVirtIfAuthType, 3679 ospfVirtIfAuthKey, 3680 ospfVirtIfStatus, 3681 ospfVirtIfLsaCount, 3682 ospfVirtIfLsaCksumSum 3683 } 3684 STATUS current 3685 DESCRIPTION 3686 "These objects are required for OSPF systems." 3687 ::= { ospfGroups 19 } 3689 END 3691 4 OSPF Trap Overview 3693 4.1 Introduction 3695 OSPF is an event driven routing protocol, where an event can be a 3696 change in an OSPF interface's link-level status, the expiration of an 3697 OSPF timer or the reception of an OSPF protocol packet. Many of the 3698 actions that OSPF takes as a result of these events will result in a 3699 change of the routing topology. 3701 As routing topologies become large and complex it is often difficult 3702 to locate the source of a topology change or unpredicted routing path 3703 by polling a large number or routers. Because of the difficulty of 3704 polling a large number of devices, a more prudent approach is for 3705 devices to notify a network manager of potentially critical OSPF 3706 events using SNMP traps. 3708 This section defines a set of traps, objects and mechanisms to 3709 enhance the ability to manage IP internetworks which use OSPF as its 3710 IGP. It is an optional but very useful extension to the OSPF MIB. 3712 4.2 Approach 3714 The mechanism for sending traps is straight-forward. When an 3715 exception event occurs, the application notifies the local agent who 3716 sends a trap to the appropriate SNMP management stations. The 3717 message includes the trap type and may include a list of trap 3718 specific variables. Section 5 gives the trap 3719 definitions which includes the variable lists. The router ID 3720 of the originator of the trap is included in the variable list 3721 so that the network manager may easily determine the source of the 3722 trap. 3724 To limit the frequency of OSPF traps, the following additional 3725 mechanisms are suggested. 3727 4.3 Ignoring Initial Activity 3729 The majority of critical events occur when OSPF is enabled on a 3730 router, at which time the designated router is elected and neighbor 3731 adjacencies are formed. During this initial period a potential 3732 flood of traps is unnecessary since the events are expected. To avoid 3733 unnecessary traps, a router should not originate expected OSPF 3734 interface related traps until two of that interface's dead timer 3735 intervals have elapsed. The expected OSPF interface traps are 3736 ospfIfStateChange, ospfVirtIfStateChange, ospfNbrStateChange, 3737 ospfVirtNbrStateChange, ospfTxRetranmit and ospfVirtIfTxRetransmit. 3738 Additionally, ospfMaxAgeLsa and ospfOriginateLsa traps should not be 3739 originated until two dead timer intervals have elapsed where the dead 3740 timer interval used should be the dead timer with the smallest value. 3742 4.4 Throttling Traps 3744 The mechanism for throttling the traps is similar to the mechanism 3745 explained in RFC 1224 [24]. The basic premise of the throttling 3746 mechanism is that of a sliding window, defined in seconds and an 3747 upper bound on the number of traps that may be generated within this 3748 window. Note that unlike RFC 1224, traps are not sent to inform the 3749 network manager that the throttling mechanism has kicked in. 3751 A single window should be used to throttle all OSPF traps types 3752 except for the ospfLsdbOverflow and the ospfLsdbApproachingOverflow 3753 trap which should not be throttled. For example, with a window time 3754 of 3, an upper bound of 3, and events to cause trap types 1,3,5 and 7 3755 (4 traps within a 3 second period), the type 7 (the 4th) trap should 3756 not be generated. 3758 Appropriate values are 7 traps with a window time of 10 seconds. 3760 4.5 One Trap Per OSPF Event 3761 Several of the traps defined in section 5 are 3762 generated as the result of finding an unusual condition while 3763 parsing an OSPF packet or a processing a timer event. There 3764 may be more than one unusual condition detected while handling 3765 the event. For example, a link-state update packet may contain 3766 several retransmitted link-state advertisements (LSAs), or a 3767 retransmitted database description packet may contain several 3768 database description entries. To limit the number of traps and 3769 variables, OSPF should generate at most one trap per OSPF event. 3770 Only the variables associated with the first unusual condition 3771 should be included with the trap. Similarly, if more than 3772 one type of unusual condition is encountered while parsing the 3773 packet, only the first event will generate a trap. 3775 4.6 Polling Event Counters 3777 Many of the tables in the OSPF MIB contain generalized event 3778 counters. By enabling the traps defined in this document a network 3779 manager can obtain more specific information about these events. A 3780 network manager may want to poll these event counters and enable 3781 specific OSPF traps when a particular counter starts increasing 3782 abnormally. 3784 The following table shows the relationship between the event counters 3785 defined in the OSPF MIB and the trap types defined in section x. 3787 Counter32 Trap Type 3788 ----------------------- ------------------------ 3789 ospfOriginateNewLsas ospfOriginateLsa 3790 ospfIfEvents ospfIfStateChange 3791 ospfConfigError 3792 ospfIfAuthFailure 3793 ospfRxBadPacket 3794 ospfTxRetransmit 3795 ospfVirtIfEvents ospfVirtIfStateChange 3796 ospfVirtIfConfigError 3797 ospfVirtIfAuthFailure 3798 ospfVirtIfRxBadPacket 3799 ospfVirtIfTxRetransmit 3800 ospfNbrEvents ospfNbrStateChange 3801 ospfVirtNbrEvents ospfVirtNbrStateChange 3802 ospfExternLSACount ospfLsdbApproachingOverflow 3803 ospfExternLSACount ospfLsdbOverflow 3805 OSPF-TRAP-MIB DEFINITIONS ::= BEGIN 3807 IMPORTS 3808 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress 3809 FROM SNMPv2-SMI 3811 MODULE-COMPLIANCE, OBJECT-GROUP 3812 FROM SNMPv2-CONF 3813 ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState, 3814 ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState, 3815 ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId, 3816 ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, 3817 ospfVirtNbrState, ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, 3818 ospfLsdbAreaId, ospfExtLsdbLimit, ospf, ospfAreaId, 3819 ospfAreaExtNssaTranslatorStatus 3820 FROM OSPF-MIB; 3822 ospfTrap MODULE-IDENTITY 3823 LAST-UPDATED "0004021225Z" -- Sun Apr 02 12:25:50 GMT 2000 3824 ORGANIZATION "IETF OSPF Working Group" 3825 CONTACT-INFO 3826 " Spencer Giacalone 3827 Postal: Predictive Systems 3828 145 Hudson Street 3829 New York, New York 10013 3830 Tel: +1 (973) 301-5695 3831 E-Mail: spencer.giacalone@predictive.com 3833 Dan Joyal 3834 Postal: Nortel Networks 3835 600 Technology Park Drive 3836 Billerica, MA 01821 3837 Tel: +1 (978) 288-2629 3838 E-Mail: djoyal@nortelnetworks.com" 3839 DESCRIPTION 3840 "The MIB module to describe traps for the OSPF 3841 Version 2 Protocol." 3842 REVISION "0004021225Z" -- Sun Apr 02 12:25:50 GMT 2000 3843 DESCRIPTION 3844 "Updated for latest version of OSPFv2" 3845 ::= { ospf 21 } 3847 -- Trap Support Objects 3849 -- The following are support objects for the OSPF traps. 3851 ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 } 3852 ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 } 3854 ospfSetTrap OBJECT-TYPE 3855 SYNTAX OCTET STRING (SIZE(4)) 3856 MAX-ACCESS read-write 3857 STATUS current 3858 DESCRIPTION 3859 "A four-octet string serving as a bit map for 3860 the trap events defined by the OSPF traps. This 3861 object is used to enable and disable specific 3862 OSPF traps where a 1 in the bit field 3863 represents enabled. The right-most bit (least 3864 significant) represents trap 0." 3865 ::= { ospfTrapControl 1 } 3867 ospfConfigErrorType OBJECT-TYPE 3868 SYNTAX INTEGER { 3869 badVersion (1), 3870 areaMismatch (2), 3871 unknownNbmaNbr (3), -- Router is Dr eligible 3872 unknownVirtualNbr (4), 3873 authTypeMismatch(5), 3874 authFailure (6), 3875 netMaskMismatch (7), 3876 helloIntervalMismatch (8), 3877 deadIntervalMismatch (9), 3878 optionMismatch (10), 3879 mtuMismatch (11) } 3880 MAX-ACCESS read-only 3881 STATUS current 3882 DESCRIPTION 3883 "Potential types of configuration conflicts. 3884 Used by the ospfConfigError and ospfConfigVir- 3885 tError traps." 3886 ::= { ospfTrapControl 2 } 3888 ospfPacketType OBJECT-TYPE 3889 SYNTAX INTEGER { 3890 hello (1), 3891 dbDescript (2), 3892 lsReq (3), 3893 lsUpdate (4), 3894 lsAck (5) } 3895 MAX-ACCESS read-only 3896 STATUS current 3897 DESCRIPTION 3898 "OSPF packet types." 3899 ::= { ospfTrapControl 3 } 3901 ospfPacketSrc OBJECT-TYPE 3902 SYNTAX IpAddress 3903 MAX-ACCESS read-only 3904 STATUS current 3905 DESCRIPTION 3906 "The IP address of an inbound packet that can- 3907 not be identified by a neighbor instance." 3908 ::= { ospfTrapControl 4 } 3910 -- Traps 3911 ospfVirtIfStateChange NOTIFICATION-TYPE 3912 OBJECTS { ospfRouterId, -- The originator of the trap 3913 ospfVirtIfAreaId, 3914 ospfVirtIfNeighbor, 3915 ospfVirtIfState -- The new state 3916 } 3917 STATUS current 3918 DESCRIPTION 3919 "An ospfIfStateChange trap signifies that there 3920 has been a change in the state of an OSPF vir- 3921 tual interface. 3923 This trap should be generated when the inter- 3924 face state regresses (e.g., goes from Point- 3925 to-Point to Down) or progresses to a terminal 3926 state (i.e., Point-to-Point)." 3927 ::= { ospfTraps 1 } 3929 ospfNbrStateChange NOTIFICATION-TYPE 3930 OBJECTS { ospfRouterId, -- The originator of the trap 3931 ospfNbrIpAddr, 3932 ospfNbrAddressLessIndex, 3933 ospfNbrRtrId, 3934 ospfNbrState -- The new state 3935 } 3936 STATUS current 3937 DESCRIPTION 3938 "An ospfNbrStateChange trap signifies that 3939 there has been a change in the state of a non- 3940 virtual OSPF neighbor. This trap should be 3941 generated when the neighbor state regresses 3942 (e.g., goes from Attempt or Full to 1-Way or 3943 Down) or progresses to a terminal state (e.g., 3944 2-Way or Full). When an neighbor transitions 3945 from or to Full on non-broadcast multi-access 3946 and broadcast networks, the trap should be gen- 3947 erated by the designated router. A designated 3948 router transitioning to Down will be noted by 3949 ospfIfStateChange." 3950 ::= { ospfTraps 2 } 3952 ospfVirtNbrStateChange NOTIFICATION-TYPE 3953 OBJECTS { ospfRouterId, -- The originator of the trap 3954 ospfVirtNbrArea, 3955 ospfVirtNbrRtrId, 3956 ospfVirtNbrState -- The new state 3957 } 3958 STATUS current 3959 DESCRIPTION 3960 "An ospfIfStateChange trap signifies that there 3961 has been a change in the state of an OSPF vir- 3962 tual neighbor. This trap should be generated 3963 when the neighbor state regresses (e.g., goes 3964 from Attempt or Full to 1-Way or Down) or 3965 progresses to a terminal state (e.g., Full)." 3966 ::= { ospfTraps 3 } 3968 ospfIfConfigError NOTIFICATION-TYPE 3969 OBJECTS { ospfRouterId, -- The originator of the trap 3970 ospfIfIpAddress, 3971 ospfAddressLessIf, 3972 ospfPacketSrc, -- The source IP address 3973 ospfConfigErrorType, -- Type of error 3974 ospfPacketType 3975 } 3976 STATUS current 3977 DESCRIPTION 3978 "An ospfIfConfigError trap signifies that a 3979 packet has been received on a non-virtual in- 3980 terface from a router whose configuration 3981 parameters conflict with this router's confi- 3982 guration parameters. Note that the event op- 3983 tionMismatch should cause a trap only if it 3984 prevents an adjacency from forming." 3985 ::= { ospfTraps 4 } 3987 ospfVirtIfConfigError NOTIFICATION-TYPE 3988 OBJECTS { ospfRouterId, -- The originator of the trap 3989 ospfVirtIfAreaId, 3990 ospfVirtIfNeighbor, 3991 ospfConfigErrorType, -- Type of error 3992 ospfPacketType 3993 } 3994 STATUS current 3995 DESCRIPTION 3996 "An ospfConfigError trap signifies that a pack- 3997 et has been received on a virtual interface 3998 from a router whose configuration parameters 3999 conflict with this router's configuration 4000 parameters. Note that the event optionMismatch 4001 should cause a trap only if it prevents an ad- 4002 jacency from forming." 4003 ::= { ospfTraps 5 } 4005 ospfIfAuthFailure NOTIFICATION-TYPE 4006 OBJECTS { ospfRouterId, -- The originator of the trap 4007 ospfIfIpAddress, 4008 ospfAddressLessIf, 4009 ospfPacketSrc, -- The source IP address 4010 ospfConfigErrorType, -- authTypeMismatch or 4011 -- authFailure 4012 ospfPacketType 4013 } 4014 STATUS current 4015 DESCRIPTION 4016 "An ospfIfAuthFailure trap signifies that a 4017 packet has been received on a non-virtual in- 4018 terface from a router whose authentication key 4019 or authentication type conflicts with this 4020 router's authentication key or authentication 4021 type." 4022 ::= { ospfTraps 6 } 4024 ospfVirtIfAuthFailure NOTIFICATION-TYPE 4025 OBJECTS { ospfRouterId, -- The originator of the trap 4026 ospfVirtIfAreaId, 4027 ospfVirtIfNeighbor, 4028 ospfConfigErrorType, -- authTypeMismatch or 4029 -- authFailure 4030 ospfPacketType 4031 } 4032 STATUS current 4033 DESCRIPTION 4034 "An ospfVirtIfAuthFailure trap signifies that a 4035 packet has been received on a virtual interface 4036 from a router whose authentication key or au- 4037 thentication type conflicts with this router's 4038 authentication key or authentication type." 4039 ::= { ospfTraps 7 } 4041 ospfIfRxBadPacket NOTIFICATION-TYPE 4042 OBJECTS { ospfRouterId, -- The originator of the trap 4043 ospfIfIpAddress, 4044 ospfAddressLessIf, 4045 ospfPacketSrc, -- The source IP address 4046 ospfPacketType 4047 } 4048 STATUS current 4049 DESCRIPTION 4050 "An ospfIfRxBadPacket trap signifies that an 4051 OSPF packet has been received on a non-virtual 4052 interface that cannot be parsed." 4053 ::= { ospfTraps 8 } 4055 ospfVirtIfRxBadPacket NOTIFICATION-TYPE 4056 OBJECTS { ospfRouterId, -- The originator of the trap 4057 ospfVirtIfAreaId, 4058 ospfVirtIfNeighbor, 4059 ospfPacketType 4060 } 4061 STATUS current 4062 DESCRIPTION 4063 "An ospfRxBadPacket trap signifies that an OSPF 4064 packet has been received on a virtual interface 4065 that cannot be parsed." 4066 ::= { ospfTraps 9 } 4068 ospfTxRetransmit NOTIFICATION-TYPE 4069 OBJECTS { ospfRouterId, -- The originator of the trap 4070 ospfIfIpAddress, 4071 ospfAddressLessIf, 4072 ospfNbrRtrId, -- Destination 4073 ospfPacketType, 4074 ospfLsdbType, 4075 ospfLsdbLsid, 4076 ospfLsdbRouterId 4077 } 4078 STATUS current 4079 DESCRIPTION 4080 "An ospfTxRetransmit trap signifies than an 4081 OSPF packet has been retransmitted on a non- 4082 virtual interface. All packets that may be re- 4083 transmitted are associated with an LSDB entry. 4084 The LS type, LS ID, and Router ID are used to 4085 identify the LSDB entry." 4086 ::= { ospfTraps 10 } 4088 ospfVirtIfTxRetransmit NOTIFICATION-TYPE 4089 OBJECTS { ospfRouterId, -- The originator of the trap 4090 ospfVirtIfAreaId, 4091 ospfVirtIfNeighbor, 4092 ospfPacketType, 4093 ospfLsdbType, 4094 ospfLsdbLsid, 4095 ospfLsdbRouterId 4096 } 4097 STATUS current 4098 DESCRIPTION 4099 "An ospfTxRetransmit trap signifies than an 4100 OSPF packet has been retransmitted on a virtual 4101 interface. All packets that may be retransmit- 4102 ted are associated with an LSDB entry. The LS 4103 type, LS ID, and Router ID are used to identify 4104 the LSDB entry." 4105 ::= { ospfTraps 11 } 4107 ospfOriginateLsa NOTIFICATION-TYPE 4108 OBJECTS { ospfRouterId, -- The originator of the trap 4109 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 4110 ospfLsdbType, 4111 ospfLsdbLsid, 4112 ospfLsdbRouterId 4113 } 4114 STATUS current 4115 DESCRIPTION 4116 "An ospfOriginateLsa trap signifies that a new 4117 LSA has been originated by this router. This 4118 trap should not be invoked for simple refreshes 4119 of LSAs (which happens every 30 minutes), but 4120 instead will only be invoked when an LSA is 4121 (re)originated due to a topology change. Addi- 4122 tionally, this trap does not include LSAs that 4123 are being flushed because they have reached 4124 MaxAge." 4125 ::= { ospfTraps 12 } 4127 ospfMaxAgeLsa NOTIFICATION-TYPE 4128 OBJECTS { ospfRouterId, -- The originator of the trap 4129 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 4130 ospfLsdbType, 4131 ospfLsdbLsid, 4132 ospfLsdbRouterId 4133 } 4134 STATUS current 4135 DESCRIPTION 4136 "An ospfMaxAgeLsa trap signifies that one of 4137 the LSA in the router's link-state database has 4138 aged to MaxAge." 4139 ::= { ospfTraps 13 } 4141 ospfLsdbOverflow NOTIFICATION-TYPE 4142 OBJECTS { ospfRouterId, -- The originator of the trap 4143 ospfExtLsdbLimit 4144 } 4145 STATUS current 4146 DESCRIPTION 4147 "An ospfLsdbOverflow trap signifies that the 4148 number of LSAs in the router's link-state data- 4149 base has exceeded ospfExtLsdbLimit." 4150 ::= { ospfTraps 14 } 4152 ospfLsdbApproachingOverflow NOTIFICATION-TYPE 4153 OBJECTS { ospfRouterId, -- The originator of the trap 4154 ospfExtLsdbLimit 4155 } 4156 STATUS current 4157 DESCRIPTION 4158 "An ospfLsdbApproachingOverflow trap signifies 4159 that the number of LSAs in the router's link- 4160 state database has exceeded ninety percent of 4161 ospfExtLsdbLimit." 4162 ::= { ospfTraps 15 } 4164 ospfIfStateChange NOTIFICATION-TYPE 4165 OBJECTS { ospfRouterId, -- The originator of the trap 4166 ospfIfIpAddress, 4167 ospfAddressLessIf, 4168 ospfIfState -- The new state 4169 } 4170 STATUS current 4171 DESCRIPTION 4172 "An ospfIfStateChange trap signifies that there 4173 has been a change in the state of a non-virtual 4174 OSPF interface. This trap should be generated 4175 when the interface state regresses (e.g., goes 4176 from Dr to Down) or progresses to a terminal 4177 state (i.e., Point-to-Point, DR Other, Dr, or 4178 Backup)." 4179 ::= { ospfTraps 16 } 4181 ospfNssaTranslatorStatusChange NOTIFICATION-TYPE 4182 OBJECTS { ospfRouterId, -- The originator of the trap 4183 ospfAreaId, 4184 ospfAreaNssaTranslatorState -- The current translation 4185 -- status 4186 } 4187 STATUS current 4188 DESCRIPTION 4189 "An ospfNssaTranslatorStatusChange trap indicates that there 4190 has been a change in the router's ability to translate OSPF 4191 type-7 LSAs into OSPF type-5 LSAs. This trap should be 4192 generated when the Translator Status transitions from or to 4193 any defined status on a per area basis." 4194 ::= { ospfTraps 17 } 4196 -- conformance information 4198 ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 } 4200 ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 } 4201 ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 } 4203 -- compliance statements 4205 ospfTrapCompliance MODULE-COMPLIANCE 4206 STATUS current 4207 DESCRIPTION 4208 "The compliance statement " 4209 MODULE -- this module 4210 MANDATORY-GROUPS { ospfTrapControlGroup } 4211 ::= { ospfTrapCompliances 1 } 4213 -- units of conformance 4215 ospfTrapControlGroup OBJECT-GROUP 4216 OBJECTS { ospfSetTrap, 4217 ospfConfigErrorType, 4218 ospfPacketType, 4219 ospfPacketSrc 4220 } 4221 STATUS current 4222 DESCRIPTION 4223 "These objects are required to control traps 4224 from OSPF systems." 4225 ::= { ospfTrapGroups 1 } 4227 END 4229 6 Acknowledgements 4231 This document was produced by the OSPF Working Group, and is 4232 based on the MIB for OSPF version 2 by Rob Coltun and Fred 4233 Baker [18]. 4235 The Authors acknowledge the following individuals: 4237 - John Moy, Sycamore Networks 4239 - Rob Cultun, RedBack Networks 4241 - Pat Murphy, USGS 4243 7 References 4245 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An 4246 Architecture for Describing SNMP Management Frameworks", 4247 RFC 2571, April 1999 4248 [2] Rose, M., and K. McCloghrie, "Structure and 4249 Identification of Management Information for TCP/IP-based 4250 Internets", STD 16, RFC 1155, May 1990 4252 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 4253 STD 16, RFC 1212, March 1991 4255 [4] M. Rose, "A Convention for Defining Traps for use with 4256 the SNMP", RFC 1215, March 1991 4258 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4259 Rose, M., and S. Waldbusser, "Structure of Management 4260 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 4261 1999 4263 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4264 Rose, M., and S. Waldbusser, "Textual Conventions for 4265 SMIv2", STD 58, RFC 2579, April 1999 4267 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4268 Rose, M., and S. Waldbusser, "Conformance Statements for 4269 SMIv2", STD 58, RFC 2580, April 1999 4271 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 4272 "Simple Network Management Protocol", STD 15, RFC 1157, 4273 May 1990. 4275 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4276 "Introduction to Community-based SNMPv2", RFC 1901, 4277 January 1996. 4279 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4280 "Transport Mappings for Version 2 of the Simple Network 4281 Management Protocol (SNMPv2)", RFC 1906, January 1996. 4283 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, 4284 "Message Processing and Dispatching for the Simple 4285 Network Management Protocol (SNMP)", RFC 2572, April 1999 4287 [21] Moy, J., "OSPF Version 2", RFC 2328, Ascend 4288 Communications, Inc., April 1998. 4290 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4291 "Protocol Operations for Version 2 of the Simple Network 4292 Management Protocol (SNMPv2)", RFC 1905, January 1996. 4294 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 4295 Applications", RFC 2573, April 1999 4297 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 4298 Access Control Model (VACM) for the Simple Network 4299 Management Protocol (SNMP)", RFC 2575, April 1999 4301 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, 4302 "Introduction to Version 3 of the Internet-standard 4303 Network Management Framework", RFC 2570, April 1999 4305 [17] Deering, S., and R. Hinden, "Internet Protocol, Version 6 4306 (IPv6) Specification", RFC 2460, December 1998. 4308 [18] Baker, F., and Coltun, R., "OSPF Version 2 Management 4309 Information Base", RFC 1850, Cisco Systems, FORE Systems, 4310 November 1995. 4312 [19] Cerf, V., "IAB Recommendations for the Development of Internet 4313 Network Management Standards", RFC 1052, NRI, April 1988. 4315 [20] Cerf, V., "Report of the Second Ad Hoc Network Management Review 4316 Group", RFC 1109, NRI, August 1989. 4318 [21] Rose M., Editor, "Management Information Base for Network 4319 Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, 4320 Performance Systems International, March 1991. 4322 [22] Information processing systems - Open Systems Interconnection - 4323 Specification of Abstract Syntax Notation One (ASN.1), 4324 International Organization for Standardization, International 4325 Standard 8824, December 1987. 4327 [23] Information processing systems - Open Systems Interconnection - 4328 Specification of Basic Encoding Rules for Abstract Notation One 4329 (ASN.1), International Organization for Standardization, 4330 International Standard 8825, December 1987. 4332 [24] Steinberg, L., "Techniques for Managing Asynchronously Generated 4333 Alerts", RFC 1224, IBM Corporation, May 1991. 4335 [25] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, 4336 Inc., September 1993. 4338 A TOS Support 4340 For backward compatibility with previous versions of the OSPF 4341 MIB specification, TOS-specific information has been retained 4342 in this document, though the TOS routing option has been 4343 deleted from OSPF [RFC 2178]. 4345 B Changes from RFC 1850 4347 This section documents the differences between this memo and RFC 4348 1850. 4350 B.1 RFC 1583 Compatibility 4352 Added object ospfRFC1583Compatibility to ospfGeneralGroup 4353 to indicate support with "RFC 1583 Compatibility" This object 4354 has DEFVAL of "enabled". 4356 B.2 OSPF Traffic Engineering Support 4358 Added object ospfTrafficEngineeringSuport to ospfGeneralGroup 4359 to indicate support of OSPF traffic engineering. 4361 B.3 OSPF NSSA Enhancement Support 4363 Added new objects to OspfAreaTable including: 4365 -ospfAreaNssaTranslatorRole to indicate the configured 4366 NSSA translation role. 4368 -ospfAreaNssaTranslatorState to indicate the current 4369 NSSA translation role. 4371 -ospfAreaNssaTranslatorStabilityInterval to 4372 indicate time to continue to perform at current 4373 translation status. 4375 -ospfAreaNssaTranslatorEvents to indicate the number of 4376 times OSPF Translation Status has changed. 4378 Added new object ospfNssaTranslatorStatusChange 4379 to ospfTraps in OSPF-TRAP-MIB DEFINITIONS. 4381 Added ospfAreaId to IMPORTS in OSPF-TRAP-MIB DEFINITIONS to support 4382 ospfNssaTranslatorStatusChange. 4384 Added ospfAreaExtNssaTranslatorStatus to IMPORTS in OSPF-TRAP-MIB 4385 DEFINITIONS to support ospfNssaTranslatorStatusChange. 4387 Modified the DESCRIPTION clause of the ospfAreaSummary object in 4388 the ospfAreaTable to indicate support for NSSA. 4390 Modified the DESCRIPTION clause of the ospfImportAsExtern object in 4391 the ospfAreaTable for clarity. 4393 B.4 OSPF MTU Mismatch Support 4395 Added mtuMismatch enumeration to ospfConfigErrorType 4396 object in ospfTrapControl to imply MTU mismatch trap generation. 4397 in ospfIfConfigError. 4399 B.5 Opaque LSA Support 4401 Added object ospfOpaqueLsaSupport to ospfGeneralGroup 4402 to indicate support of OSPF Opaque LSAs. 4404 Added object ospfAsOpaqueLsdbLimit to ospfGeneralGroup 4405 to indicate a limit of Type-11 LSAs in the LSDB before overflow . 4407 Created ospfLocalLsdbTable, for Link-local (type-9) LSA support. 4408 This table is indexed by: 4410 -ospflocalLsdbIpAddress 4412 -ospfLocalLsdbAddressLessIf 4414 -ospfLocalLsdbType 4416 -ospfLocalLsdbLsid 4418 -ospfLocalLsdbRouterId 4420 ospfLocalLsdbTable contains the following (columnar) objects: 4422 -ospfLocalLsdbSequence, to indicate LSA instance 4424 -ospfLocalLsdbAge 4426 -ospfLocalLsdbChecksum 4428 -ospfLocalLsdbAdvertisement, containing the entire LSA 4430 Created ospfVirLocalLsdbTable, for Link-local (type-9) LSA support 4431 on virtual links. This table is indexed by: 4433 -ospfVirtLocalLsdbTransitArea 4435 -ospfVirtLocalLsdbNeighbor, to indicate the router ID of the 4436 virtual neighbor 4438 -ospfVirLocalLsdbType 4440 -ospfVirLocalLsdbLsid 4442 -ospfVirLocalLsdbRouterId 4444 ospfVirLocalLsdbTable contains the following (columnar) objects: 4446 -ospfVirLocalLsdbSequence, to indicate LSA instance 4448 -ospfVirLocalLsdbAge 4450 -ospfVirLocalLsdbChecksum 4452 -ospfVirLocalLsdbAdvertisement, containing the entire LSA 4454 Added objects to ospfIfTable to support Link-local (type-9) LSAs, 4455 including: 4457 -ospfIfLsaCount 4459 -ospfIfLsaCksumSum, to indicate the sum of the type-9 link- 4460 state advertisement checksums on this interface 4462 Added objects to ospfVirIfTable, to support Link-local (type-9) LSAs 4463 on virtual links, including: 4465 -ospfVirIfLsaCount 4467 -ospfVirIfLsaCksumSum, to indicate the sum of the type-9 link- 4468 state advertisement checksums on this link. 4470 To support area scope (type-10) LSAs, the enumeration 4471 areaOpaqueLink (10) was added to ospfLsdbType in the ospfLsdbTable. 4473 To support AS scope (type-11) LSAs, the enumeration 4474 asOpaqueLink (11) was added to ospfExtLsdbType in the 4475 ospfExtLsdbTable. 4477 B.6 OSPF Compliances 4479 Compliance statements were depreciated as needed due to the fact that 4480 many new items have been added to the MIB. These statements include: 4482 -ospfCompliance 4484 New compliance statements were added as needed to replace deprecated 4485 statements. These Statements include: 4487 -ospfCompliance 4489 Conformance groups were depreciated as needed due to the fact that 4490 many new items have been added to the MIB. These groups include: 4492 -ospfBasicGroup 4494 -ospfAreaGroup 4496 -ospfIfGroup 4498 -ospfVirtIfGroup 4500 New conformance groups were added as needed to replace deprecated 4501 groups. These groups include: 4503 -ospfBasicGroup2 4505 -ospfAreaGroup2 4507 -ospfIfGroup2 4509 -ospfVirtIfGroup2 4511 Added completely new conformance groups as needed, including: 4513 -ospfLocalLsdbGroup, which specifies support for link local (type- 4514 9) LSAs. 4516 -ospfVirtLocalLsdbGroup, which specifies support for link local 4517 (type-9) LSAs on virtual links. 4519 B.7 Miscellaneous 4521 Various sections, have been moved and or modified for clarity. 4523 Most of these changes are semantic in nature, and include, 4524 but are not limited to: 4526 -The OSPF Overview section's format was revised. Unneeded 4527 information was removed. Removed information includes OSPF TOS 4528 default values. 4530 -The Trap Overview section's format and working were revised. 4531 Unneeded information was removed. 4533 -Modified description clause of "Status" "TEXTUAL-CONVENTION" for 4534 clarity 4536 -The updates section was moved from the Overview to an appendix 4538 -Updating "REFERENCE" clauses in all objects, as needed 4540 Changed the "MAX-ACCESS" clause of 4541 "ospfHostStatus" in "ospfHostTable" to "read-create" 4543 C Security Considerations 4545 There are a number of management objects defined in this MIB that 4546 have a MAX-ACCESS clause of read-write and/or read-create. Such 4547 objects may be considered sensitive or vulnerable in some network 4548 environments. The support for SET operations in a non-secure 4549 environment without proper protection can have a negative effect on 4550 network operations. 4552 SNMPv1 by itself is not a secure environment. Even if the network 4553 itself is secure (for example by using IPSec), even then, there is no 4554 control as to who on the secure network is allowed to access and 4555 GET/SET (read/change/create/delete) the objects in this MIB. 4557 It is recommended that the implementers consider the security 4558 features as provided by the SNMPv3 framework. Specifically, the use 4559 of the User-based Security Model RFC 2574 [RFC2574] and the View- 4560 based Access Control Model RFC 2575 [RFC2575] is recommended. 4562 It is then a customer/user responsibility to ensure that the SNMP 4563 entity giving access to an instance of this MIB, is properly 4564 configured to give access to the objects only to those principals 4565 (users) that have legitimate rights to indeed GET or SET 4566 (change/create/delete) them. 4568 D Authors' Addresses 4570 Spencer Giacalone 4571 Predictive Systems, Inc. 4572 145 Hudson Street 4573 New York, NY 10013 4574 Phone: +1 (973) 301-5695 4575 EMail: spencer.giacalone@predictive.com 4577 Dan Joyal 4578 Nortel Networks, Inc. 4579 600 Technology Park Drive 4580 Billerica, MA 01821 4582 Phone: +1 (978) 288-2629 4583 EMail: djoyal@nortelnetworks.com 4585 Rob Coltun 4586 Redback Networks, Inc. 4587 300 Furguson Drive 4588 Mountain View, CA 94043 4590 Phone: +1 (650) 390-9030 4591 EMail: rcoltun@siara.com 4593 Fred Baker 4594 Cisco Systems, Inc. 4595 519 Lado Drive 4596 Santa Barbara, CA 93111 4598 Phone: +1 (805) 681-0115 4599 EMail: fred@cisco.com 4601 E Full Copyright Statement 4603 Copyright (C) The Internet Society (2000). All Rights Reserved. 4604 This document and translations of it may be copied and furnished to 4605 others, and derivative works that comment on or otherwise explain it 4606 or assist in its implementation may be prepared, copied, published 4607 and distributed, in whole or in part, without restriction of any 4608 kind, provided that the above copyright notice and this paragraph are 4609 included on all such copies and derivative works. However, this 4610 document itself may not be modified in any way, such as by removing 4611 the copyright notice or references to the Internet Society or other 4612 Internet organizations, except as needed for the purpose of 4613 developing Internet standards in which case the procedures for 4614 copyrights defined in the Internet Standards process must be 4615 followed, or as required to translate it into languages other than 4616 English. 4618 The limited permissions granted above are perpetual and will not be 4619 revoked by the Internet Society or its successors or assigns. 4621 This document and the information contained herein is provided on an 4622 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4623 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4624 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4625 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 4626 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.