idnits 2.17.1 draft-ietf-ospf-mib-update-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 54 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 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 (May 2000) is 8740 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 4350 -- Looks like a reference, but probably isn't: 'RFC2574' on line 4569 -- Looks like a reference, but probably isn't: 'RFC2575' on line 4570 == Unused Reference: '21' is defined on line 4325, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 4308, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 4312, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 4319, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 4322, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 4329, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 4334, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 4342, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2460 (ref. '17') (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 1850 (ref. '18') (Obsoleted by RFC 4750) ** Downref: Normative reference to an Unknown state RFC: RFC 1052 (ref. '19') ** Downref: Normative reference to an Unknown state RFC: RFC 1109 (ref. '20') -- Possible downref: Non-RFC (?) normative reference: ref. '22' -- Possible downref: Non-RFC (?) normative reference: ref. '23' ** Downref: Normative reference to an Experimental RFC: RFC 1224 (ref. '24') ** Downref: Normative reference to an Historic RFC: RFC 1584 (ref. '25') Summary: 23 errors (**), 0 flaws (~~), 19 warnings (==), 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: November 2000 D. Joyal 4 Filename:draft-ietf-ospf-mib-update-01.txt Nortel Networks 5 Rob Coltun 6 Redback Networks 7 Fred Baker 8 Cisco Systems 9 May 2000 11 OSPF Version 2 Management Information Base 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, 16 and its working groups. Note that other groups may also distribute 17 working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Abstract 32 This memo defines a portion of the Management Information Base (MIB) 33 for use with network management protocols in TCP/IP-based internets. 34 In particular, it defines objects for managing the Open Shortest Path 35 First Routing Protocol. 37 This memo is intended to update and possibly obsolete RFC 1850, 38 however, it is designed to be backwards compatible. The functional 39 differences between this memo and RFC 1850 are explained in Appendix 40 B. 42 Please send comments to ospf@discuss.microsoft.com. 44 Copyright Notice 46 Copyright (C) The Internet Society (1999). All Rights Reserved. 48 Table of Contents 50 The SNMPv2 Network Management Framework 51 Object Definitions 52 1 Overview ..............................................3 53 1.1 The SNMPv2 Network Management Framework .............3 54 1.2 The SMI, and Object definitions .....................3 55 1.3 Object Identification ...............................4 56 1.4 Textual Conventions .................................4 57 1.5 Conceptual Row Creation .............................4 58 1.6 Default Configuration ...............................5 59 2 Structure of this MIB .................................6 60 2.1 The Purposes of the sections in this MIB ............6 61 2.1.1 General Variables .................................6 62 2.1.2 Area Data Structure and Area Stub Metric Table ....7 63 2.1.3 Link State Database and External Link State 64 Database ..........................................7 65 2.1.4 Address Table and Host Tables .....................7 66 2.1.5 Interface and Interface Metric Tables .............7 67 2.1.6 Virtual Interface Table ...........................7 68 2.1.7 Neighbor and Virtual Neighbor Tables ..............7 69 2.1.8 Local Link State Database Table and Virtual 70 Local Link State Database Table ...................7 71 3 OSPF-MIB Definitions ..................................7 72 3.1 OSPF General Variables ..............................11 73 3.2 OSPF Area Table .....................................16 74 3.3 OSPF Area Default Metrics ...........................21 75 3.4 OSPF Link State Database ............................23 76 3.5 OSPF Address Range Table ............................26 77 3.6 OSPF Host Table .....................................28 78 3.7 OSPF Interface Table ................................30 79 3.8 OSPF Interface Metric Table .........................37 80 3.9 OSPF Virtual Interface Table ........................40 81 3.10 OSPF Neighbor Table ................................44 82 3.11 OSPF Virtual Neighbor Table ........................48 83 3.12 OSPF External Link State Database ..................51 84 3.13 OSPF Route Table Use ...............................54 85 3.14 OSPF Area Aggregate Table ..........................55 86 3.15 OSPF Local LSDB Table...............................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 .................................76 97 5.1 Trap Support Objects ................................76 98 5.2 Traps ...............................................78 99 5.3 Conformance Information .............................83 100 6 Acknowledgements ......................................84 101 7 References ............................................84 102 A TOS Support ...........................................86 103 B Changes from RFC 1850 .................................86 104 B.1 RFC 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 Compliance .....................................89 110 B.7 Miscellaneous .......................................90 111 C Security Considerations ...............................90 112 D Authors' Addresses ....................................91 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 "0005011225Z" -- Mon May 01 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 "0005011225Z" -- Mon May 01 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 ospfIfAuthKey 1556 OCTET STRING, 1557 ospfIfStatus 1558 RowStatus, 1559 ospfIfMulticastForwarding 1560 INTEGER, 1561 ospfIfDemand 1562 TruthValue, 1563 ospfIfAuthType 1564 INTEGER, 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 ospfIfAuthKey OBJECT-TYPE 1760 SYNTAX OCTET STRING (SIZE (0..256)) 1761 MAX-ACCESS read-create 1762 STATUS current 1763 DESCRIPTION 1764 "This object refers to the OSPF clear-text 1765 password (e.g. the simplePassword Authentication Key). 1766 It does not refer to any OSPF cryptographic password 1767 or key. The OSPF cryptographic key is not accessible 1768 via this MIB. 1770 When the interface's Authentication Type is 1771 simplePassword, and the key length is shorter than 1772 8 octets, the agent will left adjust and zero fill 1773 to 8 octets. 1775 Note that unauthenticated interfaces need no 1776 authentication key, and simple password authen- 1777 tication cannot use a key of more than 8 oc- 1778 tets. Larger keys are useful only with authen- 1779 tication mechanisms not specified in this docu- 1780 ment. 1782 When read, ospfIfAuthKey always returns an Oc- 1783 tet String of length zero." 1784 REFERENCE 1785 "OSPF Version 2, Section 9 The Interface Data 1786 Structure" 1787 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 1788 ::= { ospfIfEntry 16 } 1790 ospfIfStatus OBJECT-TYPE 1791 SYNTAX RowStatus 1792 MAX-ACCESS read-create 1793 STATUS current 1794 DESCRIPTION 1795 "This variable displays the status of the en- 1796 try. Setting it to 'invalid' has the effect of 1797 rendering it inoperative. The internal effect 1798 (row removal) is implementation dependent." 1799 ::= { ospfIfEntry 17 } 1801 ospfIfMulticastForwarding OBJECT-TYPE 1802 SYNTAX INTEGER { 1803 blocked (1), -- no multicast forwarding 1804 multicast (2), -- using multicast address 1805 unicast (3) -- to each OSPF neighbor 1806 } 1807 MAX-ACCESS read-create 1808 STATUS current 1809 DESCRIPTION 1810 "The way multicasts should forwarded on this 1811 interface; not forwarded, forwarded as data 1812 link multicasts, or forwarded as data link uni- 1813 casts. Data link multicasting is not meaning- 1814 ful on point to point and NBMA interfaces, and 1815 setting ospfMulticastForwarding to 0 effective- 1816 ly disables all multicast forwarding." 1817 DEFVAL { blocked } 1818 ::= { ospfIfEntry 18 } 1820 ospfIfDemand OBJECT-TYPE 1821 SYNTAX TruthValue 1822 MAX-ACCESS read-create 1823 STATUS current 1824 DESCRIPTION 1825 "Indicates whether Demand OSPF procedures (hel- 1826 lo suppression to FULL neighbors and setting the 1827 DoNotAge flag on propagated LSAs) should be per- 1828 formed on this interface." 1829 DEFVAL { false } 1830 ::= { ospfIfEntry 19 } 1832 ospfIfAuthType OBJECT-TYPE 1833 SYNTAX INTEGER (0..255) 1834 -- none (0), 1835 -- simplePassword (1) 1836 -- md5 (2) 1837 -- reserved for specification by IANA (> 2) 1838 MAX-ACCESS read-create 1839 STATUS current 1840 DESCRIPTION 1841 "The authentication type specified for an in- 1842 terface. Additional authentication types may 1843 be assigned locally." 1844 REFERENCE 1845 "OSPF Version 2, Appendix D Authentication" 1846 DEFVAL { 0 } -- no authentication, by default 1847 ::= { ospfIfEntry 20 } 1849 ospfIfLsaCount OBJECT-TYPE 1850 SYNTAX Gauge32 1851 MAX-ACCESS read-only 1852 STATUS current 1853 DESCRIPTION 1854 "The total number of link-local link state advertisements 1855 in this interface's link-local link state database." 1856 ::= { ospfIfEntry 21 } 1858 ospfIfLsaCksumSum OBJECT-TYPE 1859 SYNTAX Integer32 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "The 32-bit unsigned sum of the link-state ad- 1864 vertisements' LS checksums contained in this 1865 interface's link-local link state database. 1866 The sum can be used to determine if there has 1867 been a change in the interface's link state data- 1868 base, and to compare the interface link-state database of 1869 routers attached to the same subnet." 1870 ::= { ospfIfEntry 22 } 1872 -- OSPF Interface Metric Table 1874 -- The Metric Table describes the metrics to be advertised 1875 -- for a specified interface at the various types of service. 1876 -- As such, this table is an adjunct of the OSPF Interface 1877 -- Table. 1879 -- Types of service, as defined by RFC 791, have the ability 1880 -- to request low delay, high bandwidth, or reliable linkage. 1882 -- For the purposes of this specification, the measure of 1883 -- bandwidth: 1885 -- Metric = 10^8 / ifSpeed 1887 -- is the default value. For multiple link interfaces, note 1888 -- that ifSpeed is the sum of the individual link speeds. 1889 -- This yields a number having the following typical values: 1891 -- Network Type/bit rate Metric 1893 -- >= 100 MBPS 1 1894 -- Ethernet/802.3 10 1895 -- E1 48 1896 -- T1 (ESF) 65 1897 -- 64 KBPS 1562 1898 -- 56 KBPS 1785 1899 -- 19.2 KBPS 5208 1900 -- 9.6 KBPS 10416 1902 -- Routes that are not specified use the default (TOS 0) metric 1904 ospfIfMetricTable OBJECT-TYPE 1905 SYNTAX SEQUENCE OF OspfIfMetricEntry 1906 MAX-ACCESS not-accessible 1907 STATUS current 1908 DESCRIPTION 1909 "The TOS metrics for a non-virtual interface 1910 identified by the interface index." 1911 REFERENCE 1912 "OSPF Version 2, Appendix C.3 Router interface 1913 parameters" 1914 ::= { ospf 8 } 1916 ospfIfMetricEntry OBJECT-TYPE 1917 SYNTAX OspfIfMetricEntry 1918 MAX-ACCESS not-accessible 1919 STATUS current 1920 DESCRIPTION 1921 "A particular TOS metric for a non-virtual in- 1922 terface identified by the interface index." 1923 REFERENCE 1924 "OSPF Version 2, Appendix C.3 Router interface 1925 parameters" 1926 INDEX { ospfIfMetricIpAddress, 1927 ospfIfMetricAddressLessIf, 1928 ospfIfMetricTOS } 1929 ::= { ospfIfMetricTable 1 } 1931 OspfIfMetricEntry ::= 1932 SEQUENCE { 1933 ospfIfMetricIpAddress 1934 IpAddress, 1935 ospfIfMetricAddressLessIf 1936 Integer32, 1937 ospfIfMetricTOS 1938 TOSType, 1939 ospfIfMetricValue 1940 Metric, 1941 ospfIfMetricStatus 1942 RowStatus 1943 } 1945 ospfIfMetricIpAddress OBJECT-TYPE 1946 SYNTAX IpAddress 1947 MAX-ACCESS read-only 1948 STATUS current 1949 DESCRIPTION 1950 "The IP address of this OSPF interface. On row 1951 creation, this can be derived from the in- 1952 stance." 1953 ::= { ospfIfMetricEntry 1 } 1955 ospfIfMetricAddressLessIf OBJECT-TYPE 1956 SYNTAX Integer32 1957 MAX-ACCESS read-only 1958 STATUS current 1959 DESCRIPTION 1960 "For the purpose of easing the instancing of 1961 addressed and addressless interfaces; This 1962 variable takes the value 0 on interfaces with 1963 IP Addresses, and the value of ifIndex for in- 1964 terfaces having no IP Address. On row crea- 1965 tion, this can be derived from the instance." 1966 ::= { ospfIfMetricEntry 2 } 1968 ospfIfMetricTOS OBJECT-TYPE 1969 SYNTAX TOSType 1970 MAX-ACCESS read-only 1971 STATUS current 1972 DESCRIPTION 1973 "The type of service metric being referenced. 1974 On row creation, this can be derived from the 1975 instance." 1976 ::= { ospfIfMetricEntry 3 } 1978 ospfIfMetricValue OBJECT-TYPE 1979 SYNTAX Metric 1980 MAX-ACCESS read-create 1981 STATUS current 1982 DESCRIPTION 1983 "The metric of using this type of service on 1984 this interface. The default value of the TOS 0 1985 Metric is 10^8 / ifSpeed." 1986 ::= { ospfIfMetricEntry 4 } 1988 ospfIfMetricStatus OBJECT-TYPE 1989 SYNTAX RowStatus 1990 MAX-ACCESS read-create 1991 STATUS current 1992 DESCRIPTION 1993 "This variable displays the status of the en- 1994 try. Setting it to 'invalid' has the effect of 1995 rendering it inoperative. The internal effect 1996 (row removal) is implementation dependent." 1997 ::= { ospfIfMetricEntry 5 } 1999 -- OSPF Virtual Interface Table 2001 -- The Virtual Interface Table describes the virtual 2002 -- links that the OSPF Process is configured to 2003 -- carry on. 2005 ospfVirtIfTable OBJECT-TYPE 2006 SYNTAX SEQUENCE OF OspfVirtIfEntry 2007 MAX-ACCESS not-accessible 2008 STATUS current 2009 DESCRIPTION 2010 "Information about this router's virtual inter- 2011 faces." 2012 REFERENCE 2013 "OSPF Version 2, Appendix C.4 Virtual link 2014 parameters" 2015 ::= { ospf 9 } 2017 ospfVirtIfEntry OBJECT-TYPE 2018 SYNTAX OspfVirtIfEntry 2019 MAX-ACCESS not-accessible 2020 STATUS current 2021 DESCRIPTION 2022 "Information about a single Virtual Interface." 2023 INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor } 2024 ::= { ospfVirtIfTable 1 } 2026 OspfVirtIfEntry ::= 2027 SEQUENCE { 2028 ospfVirtIfAreaId 2029 AreaID, 2030 ospfVirtIfNeighbor 2031 RouterID, 2033 ospfVirtIfTransitDelay 2034 UpToMaxAge, 2035 ospfVirtIfRetransInterval 2036 UpToMaxAge, 2037 ospfVirtIfHelloInterval 2038 HelloRange, 2039 ospfVirtIfRtrDeadInterval 2040 PositiveInteger, 2041 ospfVirtIfState 2042 INTEGER, 2043 ospfVirtIfEvents 2044 Counter32, 2045 ospfVirtIfAuthType 2046 INTEGER, 2047 ospfVirtIfAuthKey 2048 OCTET STRING, 2049 ospfVirtIfStatus 2050 rowStatus 2051 ospfVirtIfLsaCount 2052 Gauge32, 2053 ospfVirtIfLsaCksumSum 2054 Integer32 2055 } 2057 ospfVirtIfAreaId OBJECT-TYPE 2058 SYNTAX AreaID 2059 MAX-ACCESS read-only 2060 STATUS current 2061 DESCRIPTION 2062 "The Transit Area that the Virtual Link 2063 traverses. By definition, this is not 0.0.0.0" 2064 ::= { ospfVirtIfEntry 1 } 2066 ospfVirtIfNeighbor OBJECT-TYPE 2067 SYNTAX RouterID 2068 MAX-ACCESS read-only 2069 STATUS current 2070 DESCRIPTION 2071 "The Router ID of the Virtual Neighbor." 2072 ::= { ospfVirtIfEntry 2 } 2074 ospfVirtIfTransitDelay OBJECT-TYPE 2075 SYNTAX UpToMaxAge 2076 MAX-ACCESS read-create 2077 STATUS current 2078 DESCRIPTION 2079 "The estimated number of seconds it takes to 2080 transmit a link-state update packet over this 2081 interface." 2082 DEFVAL { 1 } 2083 ::= { ospfVirtIfEntry 3 } 2085 ospfVirtIfRetransInterval OBJECT-TYPE 2086 SYNTAX UpToMaxAge 2087 MAX-ACCESS read-create 2088 STATUS current 2089 DESCRIPTION 2090 "The number of seconds between link-state ad- 2091 vertisement retransmissions, for adjacencies 2092 belonging to this interface. This value is 2093 also used when retransmitting database descrip- 2094 tion and link-state request packets. This 2095 value should be well over the expected round- 2096 trip time." 2097 DEFVAL { 5 } 2098 ::= { ospfVirtIfEntry 4 } 2100 ospfVirtIfHelloInterval OBJECT-TYPE 2101 SYNTAX HelloRange 2102 MAX-ACCESS read-create 2103 STATUS current 2104 DESCRIPTION 2105 "The length of time, in seconds, between the 2106 Hello packets that the router sends on the in- 2107 terface. This value must be the same for the 2108 virtual neighbor." 2109 DEFVAL { 10 } 2110 ::= { ospfVirtIfEntry 5 } 2112 ospfVirtIfRtrDeadInterval OBJECT-TYPE 2113 SYNTAX PositiveInteger 2114 MAX-ACCESS read-create 2115 STATUS current 2116 DESCRIPTION 2117 "The number of seconds that a router's Hello 2118 packets have not been seen before it's neigh- 2119 bors declare the router down. This should be 2120 some multiple of the Hello interval. This 2121 value must be the same for the virtual neigh- 2122 bor." 2123 DEFVAL { 60 } 2124 ::= { ospfVirtIfEntry 6 } 2126 ospfVirtIfState OBJECT-TYPE 2127 SYNTAX INTEGER { 2128 down (1), -- these use the same encoding 2129 pointToPoint (4) -- as the ospfIfTable 2130 } 2131 MAX-ACCESS read-only 2132 STATUS current 2133 DESCRIPTION 2134 "OSPF virtual interface states." 2136 DEFVAL { down } 2137 ::= { ospfVirtIfEntry 7 } 2139 ospfVirtIfEvents OBJECT-TYPE 2140 SYNTAX Counter32 2141 MAX-ACCESS read-only 2142 STATUS current 2143 DESCRIPTION 2144 "The number of state changes or error events on 2145 this Virtual Link" 2146 ::= { ospfVirtIfEntry 8 } 2148 ospfVirtIfAuthKey OBJECT-TYPE 2149 SYNTAX OCTET STRING (SIZE(0..256)) 2150 MAX-ACCESS read-create 2151 STATUS current 2152 DESCRIPTION 2153 "If Authentication Type is simplePassword, the 2154 device will left adjust and zero fill to 8 oc- 2155 tets. 2157 Note that unauthenticated interfaces need no 2158 authentication key, and simple password authen- 2159 tication cannot use a key of more than 8 oc- 2160 tets. Larger keys are useful only with authen- 2161 tication mechanisms not specified in this docu- 2162 ment. 2164 When read, ospfVifAuthKey always returns a 2165 string of length zero." 2166 REFERENCE 2167 "OSPF Version 2, Section 9 The Interface Data 2168 Structure" 2169 DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0 2170 ::= { ospfVirtIfEntry 9 } 2172 ospfVirtIfStatus OBJECT-TYPE 2173 SYNTAX RowStatus 2174 MAX-ACCESS read-create 2175 STATUS current 2176 DESCRIPTION 2177 "This variable displays the status of the en- 2178 try. Setting it to 'invalid' has the effect of 2179 rendering it inoperative. The internal effect 2180 (row removal) is implementation dependent." 2181 ::= { ospfVirtIfEntry 10 } 2183 ospfVirtIfAuthType OBJECT-TYPE 2184 SYNTAX INTEGER (0..255) 2185 -- none (0), 2186 -- simplePassword (1) 2187 -- md5 (2) 2188 -- reserved for specification by IANA (> 2) 2189 MAX-ACCESS read-create 2190 STATUS current 2191 DESCRIPTION 2192 "The authentication type specified for a virtu- 2193 al interface. Additional authentication types 2194 may be assigned locally." 2195 REFERENCE 2196 "OSPF Version 2, Appendix E Authentication" 2197 DEFVAL { 0 } -- no authentication, by default 2198 ::= { ospfVirtIfEntry 11 } 2200 ospfVirtIfLsaCount OBJECT-TYPE 2201 SYNTAX Gauge32 2202 MAX-ACCESS read-only 2203 STATUS current 2204 DESCRIPTION 2205 "The total number of link-local link state advertisements 2206 in this virtual interface's link-local link state database." 2207 ::= { ospfVirtIfEntry 12 } 2209 ospfVirtIfLsaCksumSum OBJECT-TYPE 2210 SYNTAX Integer32 2211 MAX-ACCESS read-only 2212 STATUS current 2213 DESCRIPTION 2214 "The 32-bit unsigned sum of the link-state ad- 2215 vertisements' LS checksums contained in this 2216 virtual interface's link-local link state database. 2217 The sum can be used to determine if there has 2218 been a change in the virtual interface's link state data- 2219 base, and to compare the virtual interface link-state 2220 database of the virtual neighbors." 2221 ::= { ospfVirtIfEntry 13 } 2223 -- OSPF Neighbor Table 2225 -- The OSPF Neighbor Table describes all neighbors in 2226 -- the locality of the subject router. 2228 ospfNbrTable OBJECT-TYPE 2229 SYNTAX SEQUENCE OF OspfNbrEntry 2230 MAX-ACCESS not-accessible 2231 STATUS current 2232 DESCRIPTION 2233 "A table of non-virtual neighbor information." 2234 REFERENCE 2235 "OSPF Version 2, Section 10 The Neighbor Data 2236 Structure" 2238 ::= { ospf 10 } 2240 ospfNbrEntry OBJECT-TYPE 2241 SYNTAX OspfNbrEntry 2242 MAX-ACCESS not-accessible 2243 STATUS current 2244 DESCRIPTION 2245 "The information regarding a single neighbor." 2246 REFERENCE 2247 "OSPF Version 2, Section 10 The Neighbor Data 2248 Structure" 2249 INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex } 2250 ::= { ospfNbrTable 1 } 2252 OspfNbrEntry ::= 2253 SEQUENCE { 2254 ospfNbrIpAddr 2255 IpAddress, 2256 ospfNbrAddressLessIndex 2257 InterfaceIndex, 2258 ospfNbrRtrId 2259 RouterID, 2260 ospfNbrOptions 2261 Integer32, 2262 ospfNbrPriority 2263 DesignatedRouterPriority, 2264 ospfNbrState 2265 INTEGER, 2266 ospfNbrEvents 2267 Counter32, 2268 ospfNbrLsRetransQLen 2269 Gauge32, 2270 ospfNbmaNbrStatus 2271 RowStatus, 2272 ospfNbmaNbrPermanence 2273 INTEGER, 2274 ospfNbrHelloSuppressed 2275 TruthValue 2276 } 2278 ospfNbrIpAddr OBJECT-TYPE 2279 SYNTAX IpAddress 2280 MAX-ACCESS read-only 2281 STATUS current 2282 DESCRIPTION 2283 "The IP address this neighbor is using in its 2284 IP Source Address. Note that, on addressless 2285 links, this will not be 0.0.0.0, but the ad- 2286 dress of another of the neighbor's interfaces." 2287 ::= { ospfNbrEntry 1 } 2289 ospfNbrAddressLessIndex OBJECT-TYPE 2290 SYNTAX InterfaceIndex 2291 MAX-ACCESS read-only 2292 STATUS current 2293 DESCRIPTION 2294 "On an interface having an IP Address, zero. 2295 On addressless interfaces, the corresponding 2296 value of ifIndex in the Internet Standard MIB. 2297 On row creation, this can be derived from the 2298 instance." 2299 ::= { ospfNbrEntry 2 } 2301 ospfNbrRtrId OBJECT-TYPE 2302 SYNTAX RouterID 2303 MAX-ACCESS read-only 2304 STATUS current 2305 DESCRIPTION 2306 "A 32-bit integer (represented as a type IpAd- 2307 dress) uniquely identifying the neighboring 2308 router in the Autonomous System." 2309 DEFVAL { '00000000'H } -- 0.0.0.0 2310 ::= { ospfNbrEntry 3 } 2312 ospfNbrOptions OBJECT-TYPE 2313 SYNTAX Integer32 2314 MAX-ACCESS read-only 2315 STATUS current 2316 DESCRIPTION 2317 "A Bit Mask corresponding to the neighbor's op- 2318 tions field. 2320 Bit 0, if set, indicates that the system will 2321 operate on Type of Service metrics other than 2322 TOS 0. If zero, the neighbor will ignore all 2323 metrics except the TOS 0 metric. 2325 Bit 1, if set, indicates that the associated 2326 area accepts and operates on external informa- 2327 tion; if zero, it is a stub area. 2329 Bit 2, if set, indicates that the system is ca- 2330 pable of routing IP Multicast datagrams; i.e., 2331 that it implements the Multicast Extensions to 2332 OSPF. 2334 Bit 3, if set, indicates that the associated 2335 area is an NSSA. These areas are capable of 2336 carrying type 7 external advertisements, which 2337 are translated into type 5 external advertise- 2338 ments at NSSA borders." 2339 REFERENCE 2340 "OSPF Version 2, Section 12.1.2 Options" 2341 DEFVAL { 0 } 2342 ::= { ospfNbrEntry 4 } 2344 ospfNbrPriority OBJECT-TYPE 2345 SYNTAX DesignatedRouterPriority 2346 MAX-ACCESS read-create 2347 STATUS current 2348 DESCRIPTION 2349 "The priority of this neighbor in the designat- 2350 ed router election algorithm. The value 0 sig- 2351 nifies that the neighbor is not eligible to be- 2352 come the designated router on this particular 2353 network." 2354 DEFVAL { 1 } 2355 ::= { ospfNbrEntry 5 } 2357 ospfNbrState OBJECT-TYPE 2358 SYNTAX INTEGER { 2359 down (1), 2360 attempt (2), 2361 init (3), 2362 twoWay (4), 2363 exchangeStart (5), 2364 exchange (6), 2365 loading (7), 2366 full (8) 2367 } 2368 MAX-ACCESS read-only 2369 STATUS current 2370 DESCRIPTION 2371 "The State of the relationship with this Neigh- 2372 bor." 2373 REFERENCE 2374 "OSPF Version 2, Section 10.1 Neighbor States" 2375 DEFVAL { down } 2376 ::= { ospfNbrEntry 6 } 2378 ospfNbrEvents OBJECT-TYPE 2379 SYNTAX Counter32 2380 MAX-ACCESS read-only 2381 STATUS current 2382 DESCRIPTION 2383 "The number of times this neighbor relationship 2384 has changed state, or an error has occurred." 2385 ::= { ospfNbrEntry 7 } 2387 ospfNbrLsRetransQLen OBJECT-TYPE 2388 SYNTAX Gauge32 2389 MAX-ACCESS read-only 2390 STATUS current 2391 DESCRIPTION 2392 "The current length of the retransmission 2393 queue." 2394 ::= { ospfNbrEntry 8 } 2396 ospfNbmaNbrStatus OBJECT-TYPE 2397 SYNTAX RowStatus 2398 MAX-ACCESS read-create 2399 STATUS current 2400 DESCRIPTION 2401 "This variable displays the status of the en- 2402 try. Setting it to 'invalid' has the effect of 2403 rendering it inoperative. The internal effect 2404 (row removal) is implementation dependent." 2405 ::= { ospfNbrEntry 9 } 2407 ospfNbmaNbrPermanence OBJECT-TYPE 2408 SYNTAX INTEGER { 2409 dynamic (1), -- learned through protocol 2410 permanent (2) -- configured address 2411 } 2412 MAX-ACCESS read-only 2413 STATUS current 2414 DESCRIPTION 2415 "This variable displays the status of the en- 2416 try. 'dynamic' and 'permanent' refer to how 2417 the neighbor became known." 2418 DEFVAL { permanent } 2419 ::= { ospfNbrEntry 10 } 2421 ospfNbrHelloSuppressed OBJECT-TYPE 2422 SYNTAX TruthValue 2423 MAX-ACCESS read-only 2424 STATUS current 2425 DESCRIPTION 2426 "Indicates whether Hellos are being suppressed 2427 to the neighbor" 2428 ::= { ospfNbrEntry 11 } 2430 -- OSPF Virtual Neighbor Table 2432 -- This table describes all virtual neighbors. 2433 -- Since Virtual Links are configured in the 2434 -- virtual interface table, this table is read-only. 2436 ospfVirtNbrTable OBJECT-TYPE 2437 SYNTAX SEQUENCE OF OspfVirtNbrEntry 2438 MAX-ACCESS not-accessible 2439 STATUS current 2440 DESCRIPTION 2441 "A table of virtual neighbor information." 2442 REFERENCE 2443 "OSPF Version 2, Section 15 Virtual Links" 2444 ::= { ospf 11 } 2446 ospfVirtNbrEntry OBJECT-TYPE 2447 SYNTAX OspfVirtNbrEntry 2448 MAX-ACCESS not-accessible 2449 STATUS current 2450 DESCRIPTION 2451 "Virtual neighbor information." 2452 INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId } 2453 ::= { ospfVirtNbrTable 1 } 2455 OspfVirtNbrEntry ::= 2456 SEQUENCE { 2457 ospfVirtNbrArea 2458 AreaID, 2459 ospfVirtNbrRtrId 2460 RouterID, 2461 ospfVirtNbrIpAddr 2462 IpAddress, 2463 ospfVirtNbrOptions 2464 Integer32, 2465 ospfVirtNbrState 2466 INTEGER, 2467 ospfVirtNbrEvents 2468 Counter32, 2469 ospfVirtNbrLsRetransQLen 2470 Gauge32, 2471 ospfVirtNbrHelloSuppressed 2472 TruthValue 2473 } 2475 ospfVirtNbrArea OBJECT-TYPE 2476 SYNTAX AreaID 2477 MAX-ACCESS read-only 2478 STATUS current 2479 DESCRIPTION 2480 "The Transit Area Identifier." 2481 ::= { ospfVirtNbrEntry 1 } 2483 ospfVirtNbrRtrId OBJECT-TYPE 2484 SYNTAX RouterID 2485 MAX-ACCESS read-only 2486 STATUS current 2487 DESCRIPTION 2488 "A 32-bit integer uniquely identifying the 2489 neighboring router in the Autonomous System." 2490 ::= { ospfVirtNbrEntry 2 } 2492 ospfVirtNbrIpAddr OBJECT-TYPE 2493 SYNTAX IpAddress 2494 MAX-ACCESS read-only 2495 STATUS current 2496 DESCRIPTION 2497 "The IP address this Virtual Neighbor is us- 2498 ing." 2499 ::= { ospfVirtNbrEntry 3 } 2501 ospfVirtNbrOptions OBJECT-TYPE 2502 SYNTAX Integer32 2503 MAX-ACCESS read-only 2504 STATUS current 2505 DESCRIPTION 2506 "A Bit Mask corresponding to the neighbor's op- 2507 tions field. 2509 Bit 1, if set, indicates that the system will 2510 operate on Type of Service metrics other than 2511 TOS 0. If zero, the neighbor will ignore all 2512 metrics except the TOS 0 metric. 2514 Bit 2, if set, indicates that the system is 2515 Network Multicast capable; ie, that it imple- 2516 ments OSPF Multicast Routing." 2517 ::= { ospfVirtNbrEntry 4 } 2519 ospfVirtNbrState OBJECT-TYPE 2520 SYNTAX INTEGER { 2521 down (1), 2522 attempt (2), 2523 init (3), 2524 twoWay (4), 2525 exchangeStart (5), 2526 exchange (6), 2527 loading (7), 2528 full (8) 2529 } 2530 MAX-ACCESS read-only 2531 STATUS current 2532 DESCRIPTION 2533 "The state of the Virtual Neighbor Relation- 2534 ship." 2535 ::= { ospfVirtNbrEntry 5 } 2537 ospfVirtNbrEvents OBJECT-TYPE 2538 SYNTAX Counter32 2539 MAX-ACCESS read-only 2540 STATUS current 2541 DESCRIPTION 2542 "The number of times this virtual link has 2543 changed its state, or an error has occurred." 2544 ::= { ospfVirtNbrEntry 6 } 2546 ospfVirtNbrLsRetransQLen OBJECT-TYPE 2547 SYNTAX Gauge32 2548 MAX-ACCESS read-only 2549 STATUS current 2550 DESCRIPTION 2551 "The current length of the retransmission 2552 queue." 2553 ::= { ospfVirtNbrEntry 7 } 2555 ospfVirtNbrHelloSuppressed OBJECT-TYPE 2556 SYNTAX TruthValue 2557 MAX-ACCESS read-only 2558 STATUS current 2559 DESCRIPTION 2560 "Indicates whether Hellos are being suppressed 2561 to the neighbor" 2562 ::= { ospfVirtNbrEntry 8 } 2564 -- OSPF Link State Database, External 2566 -- The Link State Database contains the Link State 2567 -- Advertisements from throughout the areas that the 2568 -- device is attached to. 2570 -- This table is identical to the OSPF LSDB Table in 2571 -- format, but contains only Link State Advertisements with 2572 -- global flooding scope. The purpose is to allow external 2573 -- LSAs to be displayed once for the router rather 2574 -- than once in each non-stub area. 2576 ospfExtLsdbTable OBJECT-TYPE 2577 SYNTAX SEQUENCE OF OspfExtLsdbEntry 2578 MAX-ACCESS not-accessible 2579 STATUS current 2580 DESCRIPTION 2581 "The OSPF Process's Links State Database." 2582 REFERENCE 2583 "OSPF Version 2, Section 12 Link State Adver- 2584 tisements" 2585 ::= { ospf 12 } 2587 ospfExtLsdbEntry OBJECT-TYPE 2588 SYNTAX OspfExtLsdbEntry 2589 MAX-ACCESS not-accessible 2590 STATUS current 2591 DESCRIPTION 2592 "A single Link State Advertisement." 2594 INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId } 2595 ::= { ospfExtLsdbTable 1 } 2597 OspfExtLsdbEntry ::= 2598 SEQUENCE { 2599 ospfExtLsdbType 2600 INTEGER, 2601 ospfExtLsdbLsid 2602 IpAddress, 2603 ospfExtLsdbRouterId 2604 RouterID, 2605 ospfExtLsdbSequence 2606 Integer32, 2607 ospfExtLsdbAge 2608 Integer32, 2609 ospfExtLsdbChecksum 2610 Integer32, 2611 ospfExtLsdbAdvertisement 2612 OCTET STRING 2613 } 2615 ospfExtLsdbType OBJECT-TYPE 2616 SYNTAX INTEGER { 2617 asExternalLink (5), 2618 asOpaqueLink (11) 2619 } 2620 MAX-ACCESS read-only 2621 STATUS current 2622 DESCRIPTION 2623 "The type of the link state advertisement. 2624 Each link state type has a separate advertise- 2625 ment format." 2626 REFERENCE 2627 "OSPF Version 2, Appendix A.4.1 The Link State 2628 Advertisement header" 2629 ::= { ospfExtLsdbEntry 1 } 2631 ospfExtLsdbLsid OBJECT-TYPE 2632 SYNTAX IpAddress 2633 MAX-ACCESS read-only 2634 STATUS current 2635 DESCRIPTION 2636 "The Link State ID is an LS Type Specific field 2637 containing either a Router ID or an IP Address; 2638 it identifies the piece of the routing domain 2639 that is being described by the advertisement." 2640 REFERENCE 2641 "OSPF Version 2, Section 12.1.4 Link State ID" 2642 ::= { ospfExtLsdbEntry 2 } 2644 ospfExtLsdbRouterId OBJECT-TYPE 2645 SYNTAX RouterID 2646 MAX-ACCESS read-only 2647 STATUS current 2648 DESCRIPTION 2649 "The 32 bit number that uniquely identifies the 2650 originating router in the Autonomous System." 2651 REFERENCE 2652 "OSPF Version 2, Appendix C.1 Global parameters" 2653 ::= { ospfExtLsdbEntry 3 } 2655 -- Note that the OSPF Sequence Number is a 32 bit signed 2656 -- integer. It starts with the value '80000001'h, 2657 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 2658 -- Thus, a typical sequence number will be very negative. 2660 ospfExtLsdbSequence OBJECT-TYPE 2661 SYNTAX Integer32 2662 MAX-ACCESS read-only 2663 STATUS current 2664 DESCRIPTION 2665 "The sequence number field is a signed 32-bit 2666 integer. It is used to detect old and dupli- 2667 cate link state advertisements. The space of 2668 sequence numbers is linearly ordered. The 2669 larger the sequence number the more recent the 2670 advertisement." 2671 REFERENCE 2672 "OSPF Version 2, Section 12.1.6 LS sequence 2673 number" 2674 ::= { ospfExtLsdbEntry 4 } 2676 ospfExtLsdbAge OBJECT-TYPE 2677 SYNTAX Integer32 -- Should be 0..MaxAge, except when 2678 -- doNotAge bit is set 2679 MAX-ACCESS read-only 2680 STATUS current 2681 DESCRIPTION 2682 "This field is the age of the link state adver- 2683 tisement in seconds." 2684 REFERENCE 2685 "OSPF Version 2, Section 12.1.1 LS age" 2686 ::= { ospfExtLsdbEntry 5 } 2688 ospfExtLsdbChecksum OBJECT-TYPE 2689 SYNTAX Integer32 2690 MAX-ACCESS read-only 2691 STATUS current 2692 DESCRIPTION 2693 "This field is the checksum of the complete 2694 contents of the advertisement, excepting the 2695 age field. The age field is excepted so that 2696 an advertisement's age can be incremented 2697 without updating the checksum. The checksum 2698 used is the same that is used for ISO connec- 2699 tionless datagrams; it is commonly referred to 2700 as the Fletcher checksum." 2701 REFERENCE 2702 "OSPF Version 2, Section 12.1.7 LS checksum" 2703 ::= { ospfExtLsdbEntry 6 } 2705 ospfExtLsdbAdvertisement OBJECT-TYPE 2706 SYNTAX OCTET STRING (SIZE(36)) 2707 MAX-ACCESS read-only 2708 STATUS current 2709 DESCRIPTION 2710 "The entire Link State Advertisement, including 2711 its header." 2712 REFERENCE 2713 "OSPF Version 2, Section 12 Link State Adver- 2714 tisements" 2715 ::= { ospfExtLsdbEntry 7 } 2717 -- OSPF Use of the CIDR Route Table 2719 ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 } 2721 -- The IP Forwarding Table defines a number of objects for use by 2722 -- the routing protocol to externalize its information. Most of 2723 -- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy, 2724 -- ipForwardNextHop, ipForwardIfIndex, ipForwardType, 2725 -- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are 2726 -- defined there. 2728 -- Those that leave some discretion are defined here. 2730 -- ipCidrRouteProto is, of course, ospf (13). 2732 -- ipCidrRouteAge is the time since the route was first calculated, 2733 -- as opposed to the time since the last SPF run. 2735 -- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing 2736 -- protocol. The following values shall be found there depending 2737 -- on the way the route was calculated. 2739 ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 } 2740 ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 } 2741 ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 } 2742 ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 } 2744 -- ipCidrRouteMetric1 is, by definition, the primary routing 2745 -- metric. Therefore, it should be the metric that route 2746 -- selection is based on. For intra-area and inter-area routes, 2747 -- it is an OSPF metric. For External Type 1 (comparable value) 2748 -- routes, it is an OSPF metric plus the External Metric. For 2749 -- external Type 2 (non-comparable value) routes, it is the 2750 -- external metric. 2752 -- ipCidrRouteMetric2 is, by definition, a secondary routing 2753 -- metric. Therefore, it should be the metric that breaks a tie 2754 -- among routes having equal metric1 values and the same 2755 -- calculation rule. For intra-area, inter-area routes, and 2756 -- External Type 1 (comparable value) routes, it is unused. For 2757 -- external Type 2 (non-comparable value) routes, it is the metric 2758 -- to the AS border router. 2760 -- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 2761 -- are unused. 2763 -- The OSPF Area Aggregate Table 2764 -- 2765 -- This table replaces the OSPF Area Summary Table, being an 2766 -- extension of that for CIDR routers. 2768 ospfAreaAggregateTable OBJECT-TYPE 2769 SYNTAX SEQUENCE OF OspfAreaAggregateEntry 2770 MAX-ACCESS not-accessible 2771 STATUS current 2772 DESCRIPTION 2773 "A range of IP addresses specified by an IP 2774 address/IP network mask pair. For example, 2775 class B address range of X.X.X.X with a network 2776 mask of 255.255.0.0 includes all IP addresses 2777 from X.X.0.0 to X.X.255.255. Note that if 2778 ranges are configured such that one range sub- 2779 sumes another range (e.g., 10.0.0.0 mask 2780 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2781 most specific match is the preferred one." 2782 REFERENCE 2783 "OSPF Version 2, Appendix C.2 Area parameters" 2784 ::= { ospf 14 } 2786 ospfAreaAggregateEntry OBJECT-TYPE 2787 SYNTAX OspfAreaAggregateEntry 2788 MAX-ACCESS not-accessible 2789 STATUS current 2790 DESCRIPTION 2791 "A range of IP addresses specified by an IP 2792 address/IP network mask pair. For example, 2793 class B address range of X.X.X.X with a network 2794 mask of 255.255.0.0 includes all IP addresses 2795 from X.X.0.0 to X.X.255.255. Note that if 2796 ranges are range configured such that one range 2797 subsumes another range (e.g., 10.0.0.0 mask 2798 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 2799 most specific match is the preferred one." 2800 REFERENCE 2801 "OSPF Version 2, Appendix C.2 Area parameters" 2802 INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType, 2803 ospfAreaAggregateNet, ospfAreaAggregateMask } 2804 ::= { ospfAreaAggregateTable 1 } 2806 OspfAreaAggregateEntry ::= 2807 SEQUENCE { 2808 ospfAreaAggregateAreaID 2809 AreaID, 2810 ospfAreaAggregateLsdbType 2811 INTEGER, 2812 ospfAreaAggregateNet 2813 IpAddress, 2814 ospfAreaAggregateMask 2815 IpAddress, 2816 ospfAreaAggregateStatus 2817 RowStatus, 2818 ospfAreaAggregateEffect 2819 INTEGER 2820 } 2822 ospfAreaAggregateAreaID OBJECT-TYPE 2823 SYNTAX AreaID 2824 MAX-ACCESS read-only 2825 STATUS current 2826 DESCRIPTION 2827 "The Area the Address Aggregate is to be found 2828 within." 2829 REFERENCE 2830 "OSPF Version 2, Appendix C.2 Area parameters" 2831 ::= { ospfAreaAggregateEntry 1 } 2833 ospfAreaAggregateLsdbType OBJECT-TYPE 2834 SYNTAX INTEGER { 2835 summaryLink (3), 2836 nssaExternalLink (7) 2837 } 2838 MAX-ACCESS read-only 2839 STATUS current 2840 DESCRIPTION 2841 "The type of the Address Aggregate. This field 2842 specifies the Lsdb type that this Address Ag- 2843 gregate applies to." 2844 REFERENCE 2845 "OSPF Version 2, Appendix A.4.1 The Link State 2846 Advertisement header" 2847 ::= { ospfAreaAggregateEntry 2 } 2849 ospfAreaAggregateNet OBJECT-TYPE 2850 SYNTAX IpAddress 2851 MAX-ACCESS read-only 2852 STATUS current 2853 DESCRIPTION 2854 "The IP Address of the Net or Subnet indicated 2855 by the range." 2856 REFERENCE 2857 "OSPF Version 2, Appendix C.2 Area parameters" 2858 ::= { ospfAreaAggregateEntry 3 } 2860 ospfAreaAggregateMask OBJECT-TYPE 2861 SYNTAX IpAddress 2862 MAX-ACCESS read-only 2863 STATUS current 2864 DESCRIPTION 2865 "The Subnet Mask that pertains to the Net or 2866 Subnet." 2867 REFERENCE 2868 "OSPF Version 2, Appendix C.2 Area parameters" 2869 ::= { ospfAreaAggregateEntry 4 } 2871 ospfAreaAggregateStatus OBJECT-TYPE 2872 SYNTAX RowStatus 2873 MAX-ACCESS read-create 2874 STATUS current 2875 DESCRIPTION 2876 "This variable displays the status of the en- 2877 try. Setting it to 'invalid' has the effect of 2878 rendering it inoperative. The internal effect 2879 (row removal) is implementation dependent." 2880 ::= { ospfAreaAggregateEntry 5 } 2882 ospfAreaAggregateEffect OBJECT-TYPE 2883 SYNTAX INTEGER { 2884 advertiseMatching (1), 2885 doNotAdvertiseMatching (2) 2886 } 2887 MAX-ACCESS read-create 2888 STATUS current 2889 DESCRIPTION 2890 "Subnets subsumed by ranges either trigger the 2891 advertisement of the indicated aggregate (ad- 2892 vertiseMatching), or result in the subnet's not 2893 being advertised at all outside the area." 2894 DEFVAL { advertiseMatching } 2895 ::= { ospfAreaAggregateEntry 6 } 2897 -- OSPF Link State Database, Link-Local for non-virtual links 2898 -- This table is identical to the OSPF LSDB Table in 2899 -- format, but contains only Link-Local Link State 2900 -- Advertisements for non-virtual links. The purpose is 2901 -- to allow Link-Local LSAs to be displayed for each 2902 -- non-virtual interface. This table is implemented to 2903 -- support type-9 LSAs which are defined in 2904 -- "The OSPF Opaque LSA Option". 2906 ospfLocalLsdbTable OBJECT-TYPE 2907 SYNTAX SEQUENCE OF OspfLocalLsdbEntry 2908 MAX-ACCESS not-accessible 2909 STATUS current 2910 DESCRIPTION 2911 "The OSPF Process's Link-Local Link State Database 2912 for non-virtual links." 2913 REFERENCE 2914 "OSPF Version 2, Section 12 Link State Adver- 2915 tisements and The OSPF Opaque LSA Option" 2916 ::= { ospf 15 } 2918 ospfLocalLsdbEntry OBJECT-TYPE 2919 SYNTAX OspfLocalLsdbEntry 2920 MAX-ACCESS not-accessible 2921 STATUS current 2922 DESCRIPTION 2923 "A single Link State Advertisement." 2924 INDEX { ospfLocalLsdbIpAddress, ospfLocalLsdbAddressLessIf, 2925 ospfLocalLsdbType, ospfLocalLsdbLsid, ospfLocalLsdbRouterId 2926 } 2927 ::= { ospfLocalLsdbTable 1 } 2929 OspfLocalLsdbEntry ::= 2930 SEQUENCE { 2931 ospfLocalLsdbIpAddress 2932 IpAddress, 2933 ospfLocalLsdbAddressLessIf 2934 Integer32, 2935 ospfLocalLsdbType 2936 INTEGER, 2937 ospfLocalLsdbLsid 2938 IpAddress, 2939 ospfLocalLsdbRouterId 2940 RouterID, 2941 ospfLocalLsdbSequence 2942 Integer32, 2943 ospfLocalLsdbAge 2944 Integer32, 2945 ospfLocalLsdbChecksum 2946 Integer32, 2947 ospfLocalLsdbAdvertisement 2948 OCTET STRING 2949 } 2951 ospfLocalLsdbIpAddress OBJECT-TYPE 2952 SYNTAX IpAddress 2953 MAX-ACCESS read-only 2954 STATUS current 2955 DESCRIPTION 2956 "The IP Address of the interface from 2957 which the LSA was received if the interface is 2958 numbered." 2959 REFERENCE 2960 "OSPF Version 2, Appendix C.3 Interface parameters" 2961 ::= { ospfLocalLsdbEntry 1 } 2963 ospfLocalLsdbAddressLessIf OBJECT-TYPE 2964 SYNTAX Integer32 2965 MAX-ACCESS read-only 2966 STATUS current 2967 DESCRIPTION 2968 "The Interface Index of the interface from 2969 which the LSA was received if the interface is 2970 unnumbered." 2971 REFERENCE 2972 "OSPF Version 2, Appendix C.3 Interface parameters" 2973 ::= { ospfLocalLsdbEntry 2 } 2975 ospfLocalLsdbType OBJECT-TYPE 2976 SYNTAX INTEGER { localOpaqueLink (9) } 2977 MAX-ACCESS read-only 2978 STATUS current 2979 DESCRIPTION 2980 "The type of the link state advertisement. 2981 Each link state type has a separate advertise- 2982 ment format." 2983 REFERENCE 2984 "OSPF Version 2, Appendix A.4.1 The Link State 2985 Advertisement header and " 2986 ::= { ospfLocalLsdbEntry 3 } 2988 ospfLocalLsdbLsid OBJECT-TYPE 2989 SYNTAX IpAddress 2990 MAX-ACCESS read-only 2991 STATUS current 2992 DESCRIPTION 2993 "The Link State ID is an LS Type Specific field 2994 containing a 32 bit identifier in IP address format; 2995 it identifies the piece of the routing domain 2996 that is being described by the advertisement." 2997 REFERENCE 2998 "OSPF Version 2, Section 12.1.4 Link State ID" 3000 ::= { ospfLocalLsdbEntry 4 } 3002 ospfLocalLsdbRouterId OBJECT-TYPE 3003 SYNTAX RouterID 3004 MAX-ACCESS read-only 3005 STATUS current 3006 DESCRIPTION 3007 "The 32 bit number that uniquely identifies the 3008 originating router in the Autonomous System." 3009 REFERENCE 3010 "OSPF Version 2, Appendix C.1 Global parameters" 3011 ::= { ospfLocalLsdbEntry 5 } 3013 -- Note that the OSPF Sequence Number is a 32 bit signed 3014 -- integer. It starts with the value '80000001'h, 3015 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 3016 -- Thus, a typical sequence number will be very negative. 3018 ospfLocalLsdbSequence OBJECT-TYPE 3019 SYNTAX Integer32 3020 MAX-ACCESS read-only 3021 STATUS current 3022 DESCRIPTION 3023 "The sequence number field is a signed 32-bit 3024 integer. It is used to detect old and dupli- 3025 cate link state advertisements. The space of 3026 sequence numbers is linearly ordered. The 3027 larger the sequence number the more recent the 3028 advertisement." 3029 REFERENCE 3030 "OSPF Version 2, Section 12.1.6 LS sequence 3031 number" 3032 ::= { ospfLocalLsdbEntry 6 } 3034 ospfLocalLsdbAge OBJECT-TYPE 3035 SYNTAX Integer32 -- Should be 0..MaxAge, except when 3036 -- doNotAge bit is set 3037 MAX-ACCESS read-only 3038 STATUS current 3039 DESCRIPTION 3040 "This field is the age of the link state adver- 3041 tisement in seconds." 3042 REFERENCE 3043 "OSPF Version 2, Section 12.1.1 LS age" 3044 ::= { ospfLocalLsdbEntry 7 } 3046 ospfLocalLsdbChecksum OBJECT-TYPE 3047 SYNTAX Integer32 3048 MAX-ACCESS read-only 3049 STATUS current 3050 DESCRIPTION 3051 "This field is the checksum of the complete 3052 contents of the advertisement, excepting the 3053 age field. The age field is excepted so that 3054 an advertisement's age can be incremented 3055 without updating the checksum. The checksum 3056 used is the same that is used for ISO connec- 3057 tionless datagrams; it is commonly referred to 3058 as the Fletcher checksum." 3059 REFERENCE 3060 "OSPF Version 2, Section 12.1.7 LS checksum" 3061 ::= { ospfLocalLsdbEntry 8 } 3063 ospfLocalLsdbAdvertisement OBJECT-TYPE 3064 SYNTAX OCTET STRING (SIZE (1..65535)) 3065 MAX-ACCESS read-only 3066 STATUS current 3067 DESCRIPTION 3068 "The entire Link State Advertisement, including 3069 its header." 3070 REFERENCE 3071 "OSPF Version 2, Section 12 Link State Adver- 3072 tisements" 3073 ::= { ospfLocalLsdbEntry 9 } 3075 -- OSPF Link State Database, Link-Local for virtual Links 3077 -- This table is identical to the OSPF LSDB Table in 3078 -- format, but contains only Link-Local Link State 3079 -- Advertisements for virtual links. The purpose is to 3080 -- allow Link-Local LSAs to be displayed for each virtual 3081 -- interface. This table is implemented to support type-9 LSAs 3082 -- which are defined in "The OSPF Opaque LSA Option". 3084 ospfVirtLocalLsdbTable OBJECT-TYPE 3085 SYNTAX SEQUENCE OF OspfVirtLocalLsdbEntry 3086 MAX-ACCESS not-accessible 3087 STATUS current 3088 DESCRIPTION 3089 "The OSPF Process's Link-Local Link State Database 3090 for virtual links." 3091 REFERENCE 3092 "OSPF Version 2, Section 12 Link State Adver- 3093 tisements and The OSPF Opaque LSA Option" 3094 ::= { ospf 16 } 3096 ospfVirtLocalLsdbEntry OBJECT-TYPE 3097 SYNTAX OspfVirtLocalLsdbEntry 3098 MAX-ACCESS not-accessible 3099 STATUS current 3100 DESCRIPTION 3101 "A single Link State Advertisement." 3102 INDEX { ospfVirtLocalLsdbTransitArea, 3103 ospfVirtLocalLsdbNeighbor, 3104 ospfVirtLocalLsdbType, 3105 ospfVirtLocalLsdbLsid, 3106 ospfVirtLocalLsdbRouterId 3107 } 3108 ::= { ospfVirtLocalLsdbTable 1 } 3110 OspfVirtLocalLsdbEntry ::= 3111 SEQUENCE { 3112 ospfVirtLocalLsdbTransitArea 3113 AreaID, 3114 ospfVirtLocalLsdbNeighbor 3115 RouterID, 3116 ospfVirtLocalLsdbType 3117 INTEGER, 3118 ospfVirtLocalLsdbLsid 3119 IpAddress, 3120 ospfVirtLocalLsdbRouterId 3121 RouterID, 3122 ospfVirtLocalLsdbSequence 3123 Integer32, 3124 ospfVirtLocalLsdbAge 3125 Integer32, 3126 ospfVirtLocalLsdbChecksum 3127 Integer32, 3128 ospfVirtLocalLsdbAdvertisement 3129 OCTET STRING 3130 } 3132 ospfVirtLocalLsdbTransitArea OBJECT-TYPE 3133 SYNTAX AreaID 3134 MAX-ACCESS read-only 3135 STATUS current 3136 DESCRIPTION 3137 "The Transit Area that the Virtual Link 3138 traverses. By definition, this is not 0.0.0.0" 3139 REFERENCE 3140 "OSPF Version 2, Appendix C.3 Interface parameters" 3141 ::= { ospfVirtLocalLsdbEntry 1 } 3143 ospfVirtLocalLsdbNeighbor OBJECT-TYPE 3144 SYNTAX RouterID 3145 MAX-ACCESS read-only 3146 STATUS current 3147 DESCRIPTION 3148 "The Router ID of the Virtual Neighbor." 3149 REFERENCE 3150 "OSPF Version 2, Appendix C.3 Interface parameters" 3151 ::= { ospfVirtLocalLsdbEntry 2 } 3153 ospfVirtLocalLsdbType OBJECT-TYPE 3154 SYNTAX INTEGER { localOpaqueLink (9) } 3155 MAX-ACCESS read-only 3156 STATUS current 3157 DESCRIPTION 3158 "The type of the link state advertisement. 3159 Each link state type has a separate advertise- 3160 ment format." 3161 REFERENCE 3162 "OSPF Version 2, Appendix A.4.1 The Link State 3163 Advertisement header and " 3164 ::= { ospfVirtLocalLsdbEntry 3 } 3166 ospfVirtLocalLsdbLsid OBJECT-TYPE 3167 SYNTAX IpAddress 3168 MAX-ACCESS read-only 3169 STATUS current 3170 DESCRIPTION 3171 "The Link State ID is an LS Type Specific field 3172 containing a 32 bit identifier in IP address format; 3173 it identifies the piece of the routing domain 3174 that is being described by the advertisement." 3175 REFERENCE 3176 "OSPF Version 2, Section 12.1.4 Link State ID" 3177 ::= { ospfVirtLocalLsdbEntry 4 } 3179 ospfVirtLocalLsdbRouterId OBJECT-TYPE 3180 SYNTAX RouterID 3181 MAX-ACCESS read-only 3182 STATUS current 3183 DESCRIPTION 3184 "The 32 bit number that uniquely identifies the 3185 originating router in the Autonomous System." 3186 REFERENCE 3187 "OSPF Version 2, Appendix C.1 Global parameters" 3188 ::= { ospfVirtLocalLsdbEntry 5 } 3190 -- Note that the OSPF Sequence Number is a 32 bit signed 3191 -- integer. It starts with the value '80000001'h, 3192 -- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h 3193 -- Thus, a typical sequence number will be very negative. 3195 ospfVirtLocalLsdbSequence OBJECT-TYPE 3196 SYNTAX Integer32 3197 MAX-ACCESS read-only 3198 STATUS current 3199 DESCRIPTION 3200 "The sequence number field is a signed 32-bit 3201 integer. It is used to detect old and dupli- 3202 cate link state advertisements. The space of 3203 sequence numbers is linearly ordered. The 3204 larger the sequence number the more recent the 3205 advertisement." 3206 REFERENCE 3207 "OSPF Version 2, Section 12.1.6 LS sequence 3208 number" 3209 ::= { ospfVirtLocalLsdbEntry 6 } 3211 ospfVirtLocalLsdbAge OBJECT-TYPE 3212 SYNTAX Integer32 -- Should be 0..MaxAge, except when 3213 -- doNotAge bit is set 3214 MAX-ACCESS read-only 3215 STATUS current 3216 DESCRIPTION 3217 "This field is the age of the link state adver- 3218 tisement in seconds." 3219 REFERENCE 3220 "OSPF Version 2, Section 12.1.1 LS age" 3221 ::= { ospfVirtLocalLsdbEntry 7 } 3223 ospfVirtLocalLsdbChecksum OBJECT-TYPE 3224 SYNTAX Integer32 3225 MAX-ACCESS read-only 3226 STATUS current 3227 DESCRIPTION 3228 "This field is the checksum of the complete 3229 contents of the advertisement, excepting the 3230 age field. The age field is excepted so that 3231 an advertisement's age can be incremented 3232 without updating the checksum. The checksum 3233 used is the same that is used for ISO connec- 3234 tionless datagrams; it is commonly referred to 3235 as the Fletcher checksum." 3236 REFERENCE 3237 "OSPF Version 2, Section 12.1.7 LS checksum" 3238 ::= { ospfVirtLocalLsdbEntry 8 } 3240 ospfVirtLocalLsdbAdvertisement OBJECT-TYPE 3241 SYNTAX OCTET STRING (SIZE (1..65535)) 3242 MAX-ACCESS read-only 3243 STATUS current 3244 DESCRIPTION 3245 "The entire Link State Advertisement, including 3246 its header." 3247 REFERENCE 3248 "OSPF Version 2, Section 12 Link State Adver- 3249 tisements" 3250 ::= { ospfVirtLocalLsdbEntry 9 } 3252 -- conformance information 3253 ospfConformance OBJECT IDENTIFIER ::= { ospf 20 } 3255 ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 } 3256 ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 } 3258 -- compliance statements 3260 -- This compliance statement is deprecated and replaced 3261 -- by ospfCompliance2 3263 ospfCompliance MODULE-COMPLIANCE 3264 STATUS deprecated 3265 DESCRIPTION 3266 "The compliance statement." 3267 MODULE -- this module 3268 MANDATORY-GROUPS { 3269 ospfBasicGroup, 3270 ospfAreaGroup, 3271 ospfStubAreaGroup, 3272 ospfIfGroup, 3273 ospfIfMetricGroup, 3274 ospfVirtIfGroup, 3275 ospfNbrGroup, 3276 ospfVirtNbrGroup, 3277 ospfAreaAggregateGroup 3278 } 3279 ::= { ospfCompliances 1 } 3281 ospfCompliance2 MODULE-COMPLIANCE 3282 STATUS current 3283 DESCRIPTION 3284 "The compliance statement." 3285 MODULE -- this module 3286 MANDATORY-GROUPS { 3287 ospfBasicGroup2, 3288 ospfAreaGroup2, 3289 ospfStubAreaGroup, 3290 ospfIfGroup2, 3291 ospfIfMetricGroup, 3292 ospfVirtIfGroup2, 3293 ospfNbrGroup, 3294 ospfVirtNbrGroup, 3295 ospfAreaAggregateGroup 3296 } 3297 GROUP ospfHostGroup 3298 DESCRIPTION 3299 "This group is mandatory for OSPF systems that support 3300 attached hosts." 3301 GROUP ospfLsdbGroup 3302 DESCRIPTION 3303 "This group is mandatory for OSPF systems that display 3304 their per-area link state database." 3305 GROUP ospfExtLsdbGroup 3306 DESCRIPTION 3307 "This group is mandatory for OSPF systems that display 3308 their AS link state database." 3309 GROUP ospfLocalLsdbGroup 3310 DESCRIPTION 3311 "This group is mandatory for OSPF systems that display 3312 their per-link link state database for non-virtual 3313 links." 3314 GROUP ospfVirtLocalLsdbGroup 3315 DESCRIPTION 3316 "This group is mandatory for OSPF systems that display 3317 their per-link link state database for virtual links." 3318 ::= { ospfCompliances 2 } 3320 -- units of conformance 3322 -- This object group is deprecated and replaced by ospfBasicGroup2 3324 ospfBasicGroup OBJECT-GROUP 3325 OBJECTS { 3326 ospfRouterId, 3327 ospfAdminStat, 3328 ospfVersionNumber, 3329 ospfAreaBdrRtrStatus, 3330 ospfASBdrRtrStatus, 3331 ospfExternLsaCount, 3332 ospfExternLsaCksumSum, 3333 ospfTOSSupport, 3334 ospfOriginateNewLsas, 3335 ospfRxNewLsas, 3336 ospfExtLsdbLimit, 3337 ospfMulticastExtensions, 3338 ospfExitOverflowInterval, 3339 ospfDemandExtensions 3340 } 3341 STATUS deprecated 3342 DESCRIPTION 3343 "These objects are required for OSPF systems." 3344 ::= { ospfGroups 1 } 3346 -- This object group is deprecated and replaced by ospfAreaGroup2 3348 ospfAreaGroup OBJECT-GROUP 3349 OBJECTS { 3350 ospfAreaId, 3351 ospfImportAsExtern, 3352 ospfSpfRuns, 3353 ospfAreaBdrRtrCount, 3354 ospfAsBdrRtrCount, 3355 ospfAreaLsaCount, 3356 ospfAreaLsaCksumSum, 3357 ospfAreaSummary, 3358 ospfAreaStatus 3359 } 3360 STATUS current 3361 DESCRIPTION 3362 "These objects are required for OSPF systems 3363 supporting areas. This statement is included 3364 for backwards-compatibility. The ospfAreaGroup2 3365 statement is recommended" 3366 ::= { ospfGroups 2 } 3368 ospfStubAreaGroup OBJECT-GROUP 3369 OBJECTS { 3370 ospfStubAreaId, 3371 ospfStubTOS, 3372 ospfStubMetric, 3373 ospfStubStatus, 3374 ospfStubMetricType 3375 } 3376 STATUS current 3377 DESCRIPTION 3378 "These objects are required for OSPF systems 3379 supporting stub areas." 3380 ::= { ospfGroups 3 } 3382 ospfLsdbGroup OBJECT-GROUP 3383 OBJECTS { 3384 ospfLsdbAreaId, 3385 ospfLsdbType, 3386 ospfLsdbLsid, 3387 ospfLsdbRouterId, 3388 ospfLsdbSequence, 3389 ospfLsdbAge, 3390 ospfLsdbChecksum, 3391 ospfLsdbAdvertisement 3392 } 3393 STATUS current 3394 DESCRIPTION 3395 "These objects are required for OSPF systems 3396 that display their link state database." 3397 ::= { ospfGroups 4 } 3399 ospfAreaRangeGroup OBJECT-GROUP 3400 OBJECTS { 3401 ospfAreaRangeAreaId, 3402 ospfAreaRangeNet, 3403 ospfAreaRangeMask, 3404 ospfAreaRangeStatus, 3405 ospfAreaRangeEffect 3406 } 3407 STATUS obsolete 3408 DESCRIPTION 3409 "These objects are required for non-CIDR OSPF 3410 systems that support multiple areas." 3411 ::= { ospfGroups 5 } 3413 ospfHostGroup OBJECT-GROUP 3414 OBJECTS { 3415 ospfHostIpAddress, 3416 ospfHostTOS, 3417 ospfHostMetric, 3418 ospfHostStatus, 3419 ospfHostAreaID 3420 } 3421 STATUS current 3422 DESCRIPTION 3423 "These objects are required for OSPF systems 3424 that support attached hosts." 3425 ::= { ospfGroups 6 } 3427 -- This object group is deprecated and replaced by ospfIfGroup2 3429 ospfIfGroup OBJECT-GROUP 3430 OBJECTS { 3431 ospfIfIpAddress, 3432 ospfAddressLessIf, 3433 ospfIfAreaId, 3434 ospfIfType, 3435 ospfIfAdminStat, 3436 ospfIfRtrPriority, 3437 ospfIfTransitDelay, 3438 ospfIfRetransInterval, 3439 ospfIfHelloInterval, 3440 ospfIfRtrDeadInterval, 3441 ospfIfPollInterval, 3442 ospfIfState, 3443 ospfIfDesignatedRouter, 3444 ospfIfBackupDesignatedRouter, 3445 ospfIfEvents, 3446 ospfIfAuthType, 3447 ospfIfAuthKey, 3448 ospfIfStatus, 3449 ospfIfMulticastForwarding, 3450 ospfIfDemand 3451 } 3452 STATUS deprecated 3453 DESCRIPTION 3454 "These objects are required for OSPF systems." 3456 ::= { ospfGroups 7 } 3458 ospfIfMetricGroup OBJECT-GROUP 3459 OBJECTS { 3460 ospfIfMetricIpAddress, 3461 ospfIfMetricAddressLessIf, 3462 ospfIfMetricTOS, 3463 ospfIfMetricValue, 3464 ospfIfMetricStatus 3465 } 3466 STATUS current 3467 DESCRIPTION 3468 "These objects are required for OSPF systems." 3469 ::= { ospfGroups 8 } 3471 -- This object group is deprecated and replaced by ospfVirtIfGroup2 3473 ospfVirtIfGroup OBJECT-GROUP 3474 OBJECTS { 3475 ospfVirtIfAreaId, 3476 ospfVirtIfNeighbor, 3477 ospfVirtIfTransitDelay, 3478 ospfVirtIfRetransInterval, 3479 ospfVirtIfHelloInterval, 3480 ospfVirtIfRtrDeadInterval, 3481 ospfVirtIfState, 3482 ospfVirtIfEvents, 3483 ospfVirtIfAuthType, 3484 ospfVirtIfAuthKey, 3485 ospfVirtIfStatus 3486 } 3487 STATUS deprecated 3488 DESCRIPTION 3489 "These objects are required for OSPF systems." 3490 ::= { ospfGroups 9 } 3492 ospfNbrGroup OBJECT-GROUP 3493 OBJECTS { 3494 ospfNbrIpAddr, 3495 ospfNbrAddressLessIndex, 3496 ospfNbrRtrId, 3497 ospfNbrOptions, 3498 ospfNbrPriority, 3499 ospfNbrState, 3500 ospfNbrEvents, 3501 ospfNbrLsRetransQLen, 3502 ospfNbmaNbrStatus, 3503 ospfNbmaNbrPermanence, 3504 ospfNbrHelloSuppressed 3505 } 3506 STATUS current 3507 DESCRIPTION 3508 "These objects are required for OSPF systems." 3509 ::= { ospfGroups 10 } 3511 ospfVirtNbrGroup OBJECT-GROUP 3512 OBJECTS { 3513 ospfVirtNbrArea, 3514 ospfVirtNbrRtrId, 3515 ospfVirtNbrIpAddr, 3516 ospfVirtNbrOptions, 3517 ospfVirtNbrState, 3518 ospfVirtNbrEvents, 3519 ospfVirtNbrLsRetransQLen, 3520 ospfVirtNbrHelloSuppressed 3521 } 3522 STATUS current 3523 DESCRIPTION 3524 "These objects are required for OSPF systems." 3525 ::= { ospfGroups 11 } 3527 ospfExtLsdbGroup OBJECT-GROUP 3528 OBJECTS { 3529 ospfExtLsdbType, 3530 ospfExtLsdbLsid, 3531 ospfExtLsdbRouterId, 3532 ospfExtLsdbSequence, 3533 ospfExtLsdbAge, 3534 ospfExtLsdbChecksum, 3535 ospfExtLsdbAdvertisement 3536 } 3537 STATUS current 3538 DESCRIPTION 3539 "These objects are required for OSPF systems 3540 that display their link state database." 3541 ::= { ospfGroups 12 } 3543 ospfAreaAggregateGroup OBJECT-GROUP 3544 OBJECTS { 3545 ospfAreaAggregateAreaID, 3546 ospfAreaAggregateLsdbType, 3547 ospfAreaAggregateNet, 3548 ospfAreaAggregateMask, 3549 ospfAreaAggregateStatus, 3550 ospfAreaAggregateEffect 3551 } 3552 STATUS current 3553 DESCRIPTION 3554 "These objects are required for OSPF systems." 3555 ::= { ospfGroups 13 } 3557 ospfLocalLsdbGroup OBJECT-GROUP 3558 OBJECTS { 3559 ospfLocalLsdbIpAddress, 3560 ospfLocalLsdbAddressLessIf, 3561 ospfLocalLsdbType, 3562 ospfLocalLsdbLsid, 3563 ospfLocalLsdbRouterId, 3564 ospfLocalLsdbSequence, 3565 ospfLocalLsdbAge, 3566 ospfLocalLsdbChecksum, 3567 ospfLocalLsdbAdvertisement 3568 } 3569 STATUS current 3570 DESCRIPTION 3571 "These objects are required for OSPF systems 3572 that display their Link-Local link state databases 3573 for non-virtual links." 3574 ::= { ospfGroups 14 } 3576 ospfVirtLocalLsdbGroup OBJECT-GROUP 3577 OBJECTS { 3578 ospfVirtLocalLsdbTransitArea, 3579 ospfVirtLocalLsdbNeighbor, 3580 ospfVirtLocalLsdbType, 3581 ospfVirtLocalLsdbLsid, 3582 ospfVirtLocalLsdbRouterId, 3583 ospfVirtLocalLsdbSequence, 3584 ospfVirtLocalLsdbAge, 3585 ospfVirtLocalLsdbChecksum, 3586 ospfVirtLocalLsdbAdvertisement 3587 } 3588 STATUS current 3589 DESCRIPTION 3590 "These objects are required for OSPF systems 3591 that display their Link-Local link state databases 3592 for virtual links." 3593 ::= { ospfGroups 15 } 3595 ospfBasicGroup2 OBJECT-GROUP 3596 OBJECTS { 3597 ospfRouterId, 3598 ospfAdminStat, 3599 ospfVersionNumber, 3600 ospfAreaBdrRtrStatus, 3601 ospfASBdrRtrStatus, 3602 ospfExternLsaCount, 3603 ospfExternLsaCksumSum, 3604 ospfTOSSupport, 3605 ospfOriginateNewLsas, 3606 ospfRxNewLsas, 3607 ospfExtLsdbLimit, 3608 ospfMulticastExtensions, 3609 ospfExitOverflowInterval, 3610 ospfDemandExtensions, 3611 ospfRFC1583Compatibility, 3612 ospfOpaqueLsaSupport, 3613 ospfTrafficEngineeringSupport, 3614 ospfAsOpaqueLsdbLimit 3615 } 3616 STATUS current 3617 DESCRIPTION 3618 "These objects are required for OSPF systems." 3619 ::= { ospfGroups 16 } 3621 ospfAreaGroup2 OBJECT-GROUP 3622 OBJECTS { 3623 ospfAreaId, 3624 ospfImportAsExtern, 3625 ospfSpfRuns, 3626 ospfAreaBdrRtrCount, 3627 ospfAsBdrRtrCount, 3628 ospfAreaLsaCount, 3629 ospfAreaLsaCksumSum, 3630 ospfAreaSummary, 3631 ospfAreaStatus, 3632 ospfAreaNssaTranslatorRole, 3633 ospfAreaNssaTranslatorState, 3634 ospfAreaNssaTranslatorStabilityInterval, 3635 ospfAreaNssaTranslatorEvents 3636 } 3637 STATUS current 3638 DESCRIPTION 3639 "These objects are required for OSPF systems 3640 supporting areas. This statement is recommended 3641 for use. " 3642 ::= { ospfGroups 17 } 3644 ospfIfGroup2 OBJECT-GROUP 3645 OBJECTS { 3646 ospfIfIpAddress, 3647 ospfAddressLessIf, 3648 ospfIfAreaId, 3649 ospfIfType, 3650 ospfIfAdminStat, 3651 ospfIfRtrPriority, 3652 ospfIfTransitDelay, 3653 ospfIfRetransInterval, 3654 ospfIfHelloInterval, 3655 ospfIfRtrDeadInterval, 3656 ospfIfPollInterval, 3657 ospfIfState, 3658 ospfIfDesignatedRouter, 3659 ospfIfBackupDesignatedRouter, 3660 ospfIfEvents, 3661 ospfIfAuthType, 3662 ospfIfAuthKey, 3663 ospfIfStatus, 3664 ospfIfMulticastForwarding, 3665 ospfIfDemand, 3666 ospfIfLsaCount, 3667 ospfIfLsaCksumSum 3668 } 3669 STATUS current 3670 DESCRIPTION 3671 "These objects are required for OSPF systems." 3672 ::= { ospfGroups 18 } 3674 ospfVirtIfGroup2 OBJECT-GROUP 3675 OBJECTS { 3676 ospfVirtIfAreaId, 3677 ospfVirtIfNeighbor, 3678 ospfVirtIfTransitDelay, 3679 ospfVirtIfRetransInterval, 3680 ospfVirtIfHelloInterval, 3681 ospfVirtIfRtrDeadInterval, 3682 ospfVirtIfState, 3683 ospfVirtIfEvents, 3684 ospfVirtIfAuthType, 3685 ospfVirtIfAuthKey, 3686 ospfVirtIfStatus, 3687 ospfVirtIfLsaCount, 3688 ospfVirtIfLsaCksumSum 3689 } 3690 STATUS current 3691 DESCRIPTION 3692 "These objects are required for OSPF systems." 3693 ::= { ospfGroups 19 } 3695 END 3697 4 OSPF Trap Overview 3699 4.1 Introduction 3701 OSPF is an event driven routing protocol, where an event can be a 3702 change in an OSPF interface's link-level status, the expiration of an 3703 OSPF timer or the reception of an OSPF protocol packet. Many of the 3704 actions that OSPF takes as a result of these events will result in a 3705 change of the routing topology. 3707 As routing topologies become large and complex it is often difficult 3708 to locate the source of a topology change or unpredicted routing path 3709 by polling a large number or routers. Because of the difficulty of 3710 polling a large number of devices, a more prudent approach is for 3711 devices to notify a network manager of potentially critical OSPF 3712 events using SNMP traps. 3714 This section defines a set of traps, objects and mechanisms to 3715 enhance the ability to manage IP internetworks which use OSPF as its 3716 IGP. It is an optional but very useful extension to the OSPF MIB. 3718 4.2 Approach 3720 The mechanism for sending traps is straight-forward. When an 3721 exception event occurs, the application notifies the local agent who 3722 sends a trap to the appropriate SNMP management stations. The 3723 message includes the trap type and may include a list of trap 3724 specific variables. Section 5 gives the trap 3725 definitions which includes the variable lists. The router ID 3726 of the originator of the trap is included in the variable list 3727 so that the network manager may easily determine the source of the 3728 trap. 3730 To limit the frequency of OSPF traps, the following additional 3731 mechanisms are suggested. 3733 4.3 Ignoring Initial Activity 3735 The majority of critical events occur when OSPF is enabled on a 3736 router, at which time the designated router is elected and neighbor 3737 adjacencies are formed. During this initial period a potential 3738 flood of traps is unnecessary since the events are expected. To avoid 3739 unnecessary traps, a router should not originate expected OSPF 3740 interface related traps until two of that interface's dead timer 3741 intervals have elapsed. The expected OSPF interface traps are 3742 ospfIfStateChange, ospfVirtIfStateChange, ospfNbrStateChange, 3743 ospfVirtNbrStateChange, ospfTxRetranmit and ospfVirtIfTxRetransmit. 3744 Additionally, ospfMaxAgeLsa and ospfOriginateLsa traps should not be 3745 originated until two dead timer intervals have elapsed where the dead 3746 timer interval used should be the dead timer with the smallest value. 3748 4.4 Throttling Traps 3750 The mechanism for throttling the traps is similar to the mechanism 3751 explained in RFC 1224 [24]. The basic premise of the throttling 3752 mechanism is that of a sliding window, defined in seconds and an 3753 upper bound on the number of traps that may be generated within this 3754 window. Note that unlike RFC 1224, traps are not sent to inform the 3755 network manager that the throttling mechanism has kicked in. 3757 A single window should be used to throttle all OSPF traps types 3758 except for the ospfLsdbOverflow and the ospfLsdbApproachingOverflow 3759 trap which should not be throttled. For example, with a window time 3760 of 3, an upper bound of 3, and events to cause trap types 1,3,5 and 7 3761 (4 traps within a 3 second period), the type 7 (the 4th) trap should 3762 not be generated. 3764 Appropriate values are 7 traps with a window time of 10 seconds. 3766 4.5 One Trap Per OSPF Event 3768 Several of the traps defined in section 5 are 3769 generated as the result of finding an unusual condition while 3770 parsing an OSPF packet or a processing a timer event. There 3771 may be more than one unusual condition detected while handling 3772 the event. For example, a link-state update packet may contain 3773 several retransmitted link-state advertisements (LSAs), or a 3774 retransmitted database description packet may contain several 3775 database description entries. To limit the number of traps and 3776 variables, OSPF should generate at most one trap per OSPF event. 3777 Only the variables associated with the first unusual condition 3778 should be included with the trap. Similarly, if more than 3779 one type of unusual condition is encountered while parsing the 3780 packet, only the first event will generate a trap. 3782 4.6 Polling Event Counters 3784 Many of the tables in the OSPF MIB contain generalized event 3785 counters. By enabling the traps defined in this document a network 3786 manager can obtain more specific information about these events. A 3787 network manager may want to poll these event counters and enable 3788 specific OSPF traps when a particular counter starts increasing 3789 abnormally. 3791 The following table shows the relationship between the event counters 3792 defined in the OSPF MIB and the trap types defined in section x. 3794 Counter32 Trap Type 3795 ----------------------- ------------------------ 3796 ospfOriginateNewLsas ospfOriginateLsa 3797 ospfIfEvents ospfIfStateChange 3798 ospfConfigError 3799 ospfIfAuthFailure 3800 ospfRxBadPacket 3801 ospfTxRetransmit 3802 ospfVirtIfEvents ospfVirtIfStateChange 3803 ospfVirtIfConfigError 3804 ospfVirtIfAuthFailure 3805 ospfVirtIfRxBadPacket 3806 ospfVirtIfTxRetransmit 3807 ospfNbrEvents ospfNbrStateChange 3808 ospfVirtNbrEvents ospfVirtNbrStateChange 3809 ospfExternLSACount ospfLsdbApproachingOverflow 3810 ospfExternLSACount ospfLsdbOverflow 3812 OSPF-TRAP-MIB DEFINITIONS ::= BEGIN 3814 IMPORTS 3815 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress 3816 FROM SNMPv2-SMI 3817 MODULE-COMPLIANCE, OBJECT-GROUP 3818 FROM SNMPv2-CONF 3819 ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState, 3820 ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState, 3821 ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId, 3822 ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, 3823 ospfVirtNbrState, ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, 3824 ospfLsdbAreaId, ospfExtLsdbLimit, ospf, ospfAreaId, 3825 ospfAreaExtNssaTranslatorStatus 3826 FROM OSPF-MIB; 3828 ospfTrap MODULE-IDENTITY 3829 LAST-UPDATED "0005011225Z" -- Mon May 01 12:25:50 GMT 2000 3830 ORGANIZATION "IETF OSPF Working Group" 3831 CONTACT-INFO 3832 " Spencer Giacalone 3833 Postal: Predictive Systems 3834 145 Hudson Street 3835 New York, New York 10013 3836 Tel: +1 (973) 301-5695 3837 E-Mail: spencer.giacalone@predictive.com 3839 Dan Joyal 3840 Postal: Nortel Networks 3841 600 Technology Park Drive 3842 Billerica, MA 01821 3843 Tel: +1 (978) 288-2629 3844 E-Mail: djoyal@nortelnetworks.com" 3845 DESCRIPTION 3846 "The MIB module to describe traps for the OSPF 3847 Version 2 Protocol." 3848 REVISION "0005011225Z" -- Mon May 01 12:25:50 GMT 2000 3849 DESCRIPTION 3850 "Updated for latest version of OSPFv2" 3851 ::= { ospf 21 } 3853 -- Trap Support Objects 3855 -- The following are support objects for the OSPF traps. 3857 ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 } 3858 ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 } 3860 ospfSetTrap OBJECT-TYPE 3861 SYNTAX OCTET STRING (SIZE(4)) 3862 MAX-ACCESS read-write 3863 STATUS current 3864 DESCRIPTION 3865 "A four-octet string serving as a bit map for 3866 the trap events defined by the OSPF traps. This 3867 object is used to enable and disable specific 3868 OSPF traps where a 1 in the bit field 3869 represents enabled. The right-most bit (least 3870 significant) represents trap 0." 3871 ::= { ospfTrapControl 1 } 3873 ospfConfigErrorType OBJECT-TYPE 3874 SYNTAX INTEGER { 3875 badVersion (1), 3876 areaMismatch (2), 3877 unknownNbmaNbr (3), -- Router is Dr eligible 3878 unknownVirtualNbr (4), 3879 authTypeMismatch(5), 3880 authFailure (6), 3881 netMaskMismatch (7), 3882 helloIntervalMismatch (8), 3883 deadIntervalMismatch (9), 3884 optionMismatch (10), 3885 mtuMismatch (11) } 3886 MAX-ACCESS read-only 3887 STATUS current 3888 DESCRIPTION 3889 "Potential types of configuration conflicts. 3890 Used by the ospfConfigError and ospfConfigVir- 3891 tError traps." 3892 ::= { ospfTrapControl 2 } 3894 ospfPacketType OBJECT-TYPE 3895 SYNTAX INTEGER { 3896 hello (1), 3897 dbDescript (2), 3898 lsReq (3), 3899 lsUpdate (4), 3900 lsAck (5) } 3901 MAX-ACCESS read-only 3902 STATUS current 3903 DESCRIPTION 3904 "OSPF packet types." 3905 ::= { ospfTrapControl 3 } 3907 ospfPacketSrc OBJECT-TYPE 3908 SYNTAX IpAddress 3909 MAX-ACCESS read-only 3910 STATUS current 3911 DESCRIPTION 3912 "The IP address of an inbound packet that can- 3913 not be identified by a neighbor instance." 3914 ::= { ospfTrapControl 4 } 3916 -- Traps 3918 ospfVirtIfStateChange NOTIFICATION-TYPE 3919 OBJECTS { ospfRouterId, -- The originator of the trap 3920 ospfVirtIfAreaId, 3921 ospfVirtIfNeighbor, 3922 ospfVirtIfState -- The new state 3923 } 3924 STATUS current 3925 DESCRIPTION 3926 "An ospfIfStateChange trap signifies that there 3927 has been a change in the state of an OSPF vir- 3928 tual interface. 3930 This trap should be generated when the inter- 3931 face state regresses (e.g., goes from Point- 3932 to-Point to Down) or progresses to a terminal 3933 state (i.e., Point-to-Point)." 3934 ::= { ospfTraps 1 } 3936 ospfNbrStateChange NOTIFICATION-TYPE 3937 OBJECTS { ospfRouterId, -- The originator of the trap 3938 ospfNbrIpAddr, 3939 ospfNbrAddressLessIndex, 3940 ospfNbrRtrId, 3941 ospfNbrState -- The new state 3942 } 3943 STATUS current 3944 DESCRIPTION 3945 "An ospfNbrStateChange trap signifies that 3946 there has been a change in the state of a non- 3947 virtual OSPF neighbor. This trap should be 3948 generated when the neighbor state regresses 3949 (e.g., goes from Attempt or Full to 1-Way or 3950 Down) or progresses to a terminal state (e.g., 3951 2-Way or Full). When an neighbor transitions 3952 from or to Full on non-broadcast multi-access 3953 and broadcast networks, the trap should be gen- 3954 erated by the designated router. A designated 3955 router transitioning to Down will be noted by 3956 ospfIfStateChange." 3957 ::= { ospfTraps 2 } 3959 ospfVirtNbrStateChange NOTIFICATION-TYPE 3960 OBJECTS { ospfRouterId, -- The originator of the trap 3961 ospfVirtNbrArea, 3962 ospfVirtNbrRtrId, 3963 ospfVirtNbrState -- The new state 3964 } 3965 STATUS current 3966 DESCRIPTION 3967 "An ospfIfStateChange trap signifies that there 3968 has been a change in the state of an OSPF vir- 3969 tual neighbor. This trap should be generated 3970 when the neighbor state regresses (e.g., goes 3971 from Attempt or Full to 1-Way or Down) or 3972 progresses to a terminal state (e.g., Full)." 3973 ::= { ospfTraps 3 } 3975 ospfIfConfigError NOTIFICATION-TYPE 3976 OBJECTS { ospfRouterId, -- The originator of the trap 3977 ospfIfIpAddress, 3978 ospfAddressLessIf, 3979 ospfPacketSrc, -- The source IP address 3980 ospfConfigErrorType, -- Type of error 3981 ospfPacketType 3982 } 3983 STATUS current 3984 DESCRIPTION 3985 "An ospfIfConfigError trap signifies that a 3986 packet has been received on a non-virtual in- 3987 terface from a router whose configuration 3988 parameters conflict with this router's confi- 3989 guration parameters. Note that the event op- 3990 tionMismatch should cause a trap only if it 3991 prevents an adjacency from forming." 3992 ::= { ospfTraps 4 } 3994 ospfVirtIfConfigError NOTIFICATION-TYPE 3995 OBJECTS { ospfRouterId, -- The originator of the trap 3996 ospfVirtIfAreaId, 3997 ospfVirtIfNeighbor, 3998 ospfConfigErrorType, -- Type of error 3999 ospfPacketType 4000 } 4001 STATUS current 4002 DESCRIPTION 4003 "An ospfConfigError trap signifies that a pack- 4004 et has been received on a virtual interface 4005 from a router whose configuration parameters 4006 conflict with this router's configuration 4007 parameters. Note that the event optionMismatch 4008 should cause a trap only if it prevents an ad- 4009 jacency from forming." 4010 ::= { ospfTraps 5 } 4012 ospfIfAuthFailure NOTIFICATION-TYPE 4013 OBJECTS { ospfRouterId, -- The originator of the trap 4014 ospfIfIpAddress, 4015 ospfAddressLessIf, 4016 ospfPacketSrc, -- The source IP address 4017 ospfConfigErrorType, -- authTypeMismatch or 4018 -- authFailure 4019 ospfPacketType 4020 } 4021 STATUS current 4022 DESCRIPTION 4023 "An ospfIfAuthFailure trap signifies that a 4024 packet has been received on a non-virtual in- 4025 terface from a router whose authentication key 4026 or authentication type conflicts with this 4027 router's authentication key or authentication 4028 type." 4029 ::= { ospfTraps 6 } 4031 ospfVirtIfAuthFailure NOTIFICATION-TYPE 4032 OBJECTS { ospfRouterId, -- The originator of the trap 4033 ospfVirtIfAreaId, 4034 ospfVirtIfNeighbor, 4035 ospfConfigErrorType, -- authTypeMismatch or 4036 -- authFailure 4037 ospfPacketType 4038 } 4039 STATUS current 4040 DESCRIPTION 4041 "An ospfVirtIfAuthFailure trap signifies that a 4042 packet has been received on a virtual interface 4043 from a router whose authentication key or au- 4044 thentication type conflicts with this router's 4045 authentication key or authentication type." 4046 ::= { ospfTraps 7 } 4048 ospfIfRxBadPacket NOTIFICATION-TYPE 4049 OBJECTS { ospfRouterId, -- The originator of the trap 4050 ospfIfIpAddress, 4051 ospfAddressLessIf, 4052 ospfPacketSrc, -- The source IP address 4053 ospfPacketType 4054 } 4055 STATUS current 4056 DESCRIPTION 4057 "An ospfIfRxBadPacket trap signifies that an 4058 OSPF packet has been received on a non-virtual 4059 interface that cannot be parsed." 4060 ::= { ospfTraps 8 } 4062 ospfVirtIfRxBadPacket NOTIFICATION-TYPE 4063 OBJECTS { ospfRouterId, -- The originator of the trap 4064 ospfVirtIfAreaId, 4065 ospfVirtIfNeighbor, 4066 ospfPacketType 4067 } 4068 STATUS current 4069 DESCRIPTION 4070 "An ospfRxBadPacket trap signifies that an OSPF 4071 packet has been received on a virtual interface 4072 that cannot be parsed." 4073 ::= { ospfTraps 9 } 4075 ospfTxRetransmit NOTIFICATION-TYPE 4076 OBJECTS { ospfRouterId, -- The originator of the trap 4077 ospfIfIpAddress, 4078 ospfAddressLessIf, 4079 ospfNbrRtrId, -- Destination 4080 ospfPacketType, 4081 ospfLsdbType, 4082 ospfLsdbLsid, 4083 ospfLsdbRouterId 4084 } 4085 STATUS current 4086 DESCRIPTION 4087 "An ospfTxRetransmit trap signifies than an 4088 OSPF packet has been retransmitted on a non- 4089 virtual interface. All packets that may be re- 4090 transmitted are associated with an LSDB entry. 4091 The LS type, LS ID, and Router ID are used to 4092 identify the LSDB entry." 4093 ::= { ospfTraps 10 } 4095 ospfVirtIfTxRetransmit NOTIFICATION-TYPE 4096 OBJECTS { ospfRouterId, -- The originator of the trap 4097 ospfVirtIfAreaId, 4098 ospfVirtIfNeighbor, 4099 ospfPacketType, 4100 ospfLsdbType, 4101 ospfLsdbLsid, 4102 ospfLsdbRouterId 4103 } 4104 STATUS current 4105 DESCRIPTION 4106 "An ospfTxRetransmit trap signifies than an 4107 OSPF packet has been retransmitted on a virtual 4108 interface. All packets that may be retransmit- 4109 ted are associated with an LSDB entry. The LS 4110 type, LS ID, and Router ID are used to identify 4111 the LSDB entry." 4112 ::= { ospfTraps 11 } 4114 ospfOriginateLsa NOTIFICATION-TYPE 4115 OBJECTS { ospfRouterId, -- The originator of the trap 4116 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 4117 ospfLsdbType, 4118 ospfLsdbLsid, 4119 ospfLsdbRouterId 4120 } 4121 STATUS current 4122 DESCRIPTION 4123 "An ospfOriginateLsa trap signifies that a new 4124 LSA has been originated by this router. This 4125 trap should not be invoked for simple refreshes 4126 of LSAs (which happens every 30 minutes), but 4127 instead will only be invoked when an LSA is 4128 (re)originated due to a topology change. Addi- 4129 tionally, this trap does not include LSAs that 4130 are being flushed because they have reached 4131 MaxAge." 4132 ::= { ospfTraps 12 } 4134 ospfMaxAgeLsa NOTIFICATION-TYPE 4135 OBJECTS { ospfRouterId, -- The originator of the trap 4136 ospfLsdbAreaId, -- 0.0.0.0 for AS Externals 4137 ospfLsdbType, 4138 ospfLsdbLsid, 4139 ospfLsdbRouterId 4140 } 4141 STATUS current 4142 DESCRIPTION 4143 "An ospfMaxAgeLsa trap signifies that one of 4144 the LSA in the router's link-state database has 4145 aged to MaxAge." 4146 ::= { ospfTraps 13 } 4148 ospfLsdbOverflow NOTIFICATION-TYPE 4149 OBJECTS { ospfRouterId, -- The originator of the trap 4150 ospfExtLsdbLimit 4151 } 4152 STATUS current 4153 DESCRIPTION 4154 "An ospfLsdbOverflow trap signifies that the 4155 number of LSAs in the router's link-state data- 4156 base has exceeded ospfExtLsdbLimit." 4157 ::= { ospfTraps 14 } 4159 ospfLsdbApproachingOverflow NOTIFICATION-TYPE 4160 OBJECTS { ospfRouterId, -- The originator of the trap 4161 ospfExtLsdbLimit 4162 } 4163 STATUS current 4164 DESCRIPTION 4165 "An ospfLsdbApproachingOverflow trap signifies 4166 that the number of LSAs in the router's link- 4167 state database has exceeded ninety percent of 4168 ospfExtLsdbLimit." 4169 ::= { ospfTraps 15 } 4171 ospfIfStateChange NOTIFICATION-TYPE 4172 OBJECTS { ospfRouterId, -- The originator of the trap 4173 ospfIfIpAddress, 4174 ospfAddressLessIf, 4175 ospfIfState -- The new state 4176 } 4177 STATUS current 4178 DESCRIPTION 4179 "An ospfIfStateChange trap signifies that there 4180 has been a change in the state of a non-virtual 4181 OSPF interface. This trap should be generated 4182 when the interface state regresses (e.g., goes 4183 from Dr to Down) or progresses to a terminal 4184 state (i.e., Point-to-Point, DR Other, Dr, or 4185 Backup)." 4186 ::= { ospfTraps 16 } 4188 ospfNssaTranslatorStatusChange NOTIFICATION-TYPE 4189 OBJECTS { ospfRouterId, -- The originator of the trap 4190 ospfAreaId, 4191 ospfAreaNssaTranslatorState -- The current translation 4192 -- status 4193 } 4194 STATUS current 4195 DESCRIPTION 4196 "An ospfNssaTranslatorStatusChange trap indicates that there 4197 has been a change in the router's ability to translate OSPF 4198 type-7 LSAs into OSPF type-5 LSAs. This trap should be 4199 generated when the Translator Status transitions from or to 4200 any defined status on a per area basis." 4201 ::= { ospfTraps 17 } 4203 -- conformance information 4205 ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 } 4207 ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 } 4208 ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 } 4210 -- compliance statements 4212 ospfTrapCompliance MODULE-COMPLIANCE 4213 STATUS current 4214 DESCRIPTION 4215 "The compliance statement " 4216 MODULE -- this module 4217 MANDATORY-GROUPS { ospfTrapControlGroup } 4218 ::= { ospfTrapCompliances 1 } 4220 -- units of conformance 4222 ospfTrapControlGroup OBJECT-GROUP 4223 OBJECTS { ospfSetTrap, 4224 ospfConfigErrorType, 4225 ospfPacketType, 4226 ospfPacketSrc 4227 } 4228 STATUS current 4229 DESCRIPTION 4230 "These objects are required to control traps 4231 from OSPF systems." 4232 ::= { ospfTrapGroups 1 } 4234 END 4236 6 Acknowledgements 4238 This document was produced by the OSPF Working Group, and is 4239 based on the MIB for OSPF version 2 by Rob Coltun and Fred 4240 Baker [18]. 4242 The Authors acknowledge the following individuals: 4244 - John Moy, Sycamore Networks 4246 - Rob Cultun, RedBack Networks 4248 - Pat Murphy, USGS 4250 7 References 4252 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An 4253 Architecture for Describing SNMP Management Frameworks", 4254 RFC 2571, April 1999 4255 [2] Rose, M., and K. McCloghrie, "Structure and 4256 Identification of Management Information for TCP/IP-based 4257 Internets", STD 16, RFC 1155, May 1990 4259 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 4260 STD 16, RFC 1212, March 1991 4262 [4] M. Rose, "A Convention for Defining Traps for use with 4263 the SNMP", RFC 1215, March 1991 4265 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4266 Rose, M., and S. Waldbusser, "Structure of Management 4267 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 4268 1999 4270 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4271 Rose, M., and S. Waldbusser, "Textual Conventions for 4272 SMIv2", STD 58, RFC 2579, April 1999 4274 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4275 Rose, M., and S. Waldbusser, "Conformance Statements for 4276 SMIv2", STD 58, RFC 2580, April 1999 4278 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 4279 "Simple Network Management Protocol", STD 15, RFC 1157, 4280 May 1990. 4282 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4283 "Introduction to Community-based SNMPv2", RFC 1901, 4284 January 1996. 4286 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4287 "Transport Mappings for Version 2 of the Simple Network 4288 Management Protocol (SNMPv2)", RFC 1906, January 1996. 4290 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, 4291 "Message Processing and Dispatching for the Simple 4292 Network Management Protocol (SNMP)", RFC 2572, April 1999 4294 [21] Moy, J., "OSPF Version 2", RFC 2328, Ascend 4295 Communications, Inc., April 1998. 4297 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4298 "Protocol Operations for Version 2 of the Simple Network 4299 Management Protocol (SNMPv2)", RFC 1905, January 1996. 4301 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 4302 Applications", RFC 2573, April 1999 4304 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 4305 Access Control Model (VACM) for the Simple Network 4306 Management Protocol (SNMP)", RFC 2575, April 1999 4308 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, 4309 "Introduction to Version 3 of the Internet-standard 4310 Network Management Framework", RFC 2570, April 1999 4312 [17] Deering, S., and R. Hinden, "Internet Protocol, Version 6 4313 (IPv6) Specification", RFC 2460, December 1998. 4315 [18] Baker, F., and Coltun, R., "OSPF Version 2 Management 4316 Information Base", RFC 1850, Cisco Systems, FORE Systems, 4317 November 1995. 4319 [19] Cerf, V., "IAB Recommendations for the Development of Internet 4320 Network Management Standards", RFC 1052, NRI, April 1988. 4322 [20] Cerf, V., "Report of the Second Ad Hoc Network Management Review 4323 Group", RFC 1109, NRI, August 1989. 4325 [21] Rose M., Editor, "Management Information Base for Network 4326 Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, 4327 Performance Systems International, March 1991. 4329 [22] Information processing systems - Open Systems Interconnection - 4330 Specification of Abstract Syntax Notation One (ASN.1), 4331 International Organization for Standardization, International 4332 Standard 8824, December 1987. 4334 [23] Information processing systems - Open Systems Interconnection - 4335 Specification of Basic Encoding Rules for Abstract Notation One 4336 (ASN.1), International Organization for Standardization, 4337 International Standard 8825, December 1987. 4339 [24] Steinberg, L., "Techniques for Managing Asynchronously Generated 4340 Alerts", RFC 1224, IBM Corporation, May 1991. 4342 [25] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, 4343 Inc., September 1993. 4345 A TOS Support 4347 For backward compatibility with previous versions of the OSPF 4348 MIB specification, TOS-specific information has been retained 4349 in this document, though the TOS routing option has been 4350 deleted from OSPF [RFC 2178]. 4352 B Changes from RFC 1850 4354 This section documents the differences between this memo and RFC 4355 1850. 4357 B.1 RFC 1583 Compatibility 4359 Added object ospfRFC1583Compatibility to ospfGeneralGroup 4360 to indicate support with "RFC 1583 Compatibility" This object 4361 has DEFVAL of "enabled". 4363 B.2 OSPF Traffic Engineering Support 4365 Added object ospfTrafficEngineeringSuport to ospfGeneralGroup 4366 to indicate support of OSPF traffic engineering. 4368 B.3 OSPF NSSA Enhancement Support 4369 Added new objects to OspfAreaTable including: 4371 -ospfAreaNssaTranslatorRole to indicate the configured 4372 NSSA translation role. 4374 -ospfAreaNssaTranslatorState to indicate the current 4375 NSSA translation role. 4377 -ospfAreaNssaTranslatorStabilityInterval to 4378 indicate time to continue to perform at current 4379 translation status. 4381 -ospfAreaNssaTranslatorEvents to indicate the number of 4382 times OSPF Translation Status has changed. 4384 Added new object ospfNssaTranslatorStatusChange 4385 to ospfTraps in OSPF-TRAP-MIB DEFINITIONS. 4387 Added ospfAreaId to IMPORTS in OSPF-TRAP-MIB DEFINITIONS to support 4388 ospfNssaTranslatorStatusChange. 4390 Added ospfAreaExtNssaTranslatorStatus to IMPORTS in OSPF-TRAP-MIB 4391 DEFINITIONS to support ospfNssaTranslatorStatusChange. 4393 Modified the DESCRIPTION clause of the ospfAreaSummary object in 4394 the ospfAreaTable to indicate support for NSSA. 4396 Modified the DESCRIPTION clause of the ospfImportAsExtern object in 4397 the ospfAreaTable for clarity. 4399 B.4 OSPF MTU Mismatch Support 4401 Added mtuMismatch enumeration to ospfConfigErrorType 4402 object in ospfTrapControl to imply MTU mismatch trap generation. 4403 in ospfIfConfigError. 4405 B.5 Opaque LSA Support 4407 Added object ospfOpaqueLsaSupport to ospfGeneralGroup 4408 to indicate support of OSPF Opaque LSAs. 4410 Added object ospfAsOpaqueLsdbLimit to ospfGeneralGroup 4411 to indicate a limit of Type-11 LSAs in the LSDB before overflow . 4413 Created ospfLocalLsdbTable, for Link-local (type-9) LSA support. 4414 This table is indexed by: 4416 -ospflocalLsdbIpAddress 4418 -ospfLocalLsdbAddressLessIf 4419 -ospfLocalLsdbType 4421 -ospfLocalLsdbLsid 4423 -ospfLocalLsdbRouterId 4425 ospfLocalLsdbTable contains the following (columnar) objects: 4427 -ospfLocalLsdbSequence, to indicate LSA instance 4429 -ospfLocalLsdbAge 4431 -ospfLocalLsdbChecksum 4433 -ospfLocalLsdbAdvertisement, containing the entire LSA 4435 Created ospfVirLocalLsdbTable, for Link-local (type-9) LSA support 4436 on virtual links. This table is indexed by: 4438 -ospfVirtLocalLsdbTransitArea 4440 -ospfVirtLocalLsdbNeighbor, to indicate the router ID of the 4441 virtual neighbor 4443 -ospfVirLocalLsdbType 4445 -ospfVirLocalLsdbLsid 4447 -ospfVirLocalLsdbRouterId 4449 ospfVirLocalLsdbTable contains the following (columnar) objects: 4451 -ospfVirLocalLsdbSequence, to indicate LSA instance 4453 -ospfVirLocalLsdbAge 4455 -ospfVirLocalLsdbChecksum 4457 -ospfVirLocalLsdbAdvertisement, containing the entire LSA 4459 Added objects to ospfIfTable to support Link-local (type-9) LSAs, 4460 including: 4462 -ospfIfLsaCount 4464 -ospfIfLsaCksumSum, to indicate the sum of the type-9 link- 4465 state advertisement checksums on this interface 4467 Added objects to ospfVirIfTable, to support Link-local (type-9) LSAs 4468 on virtual links, including: 4470 -ospfVirIfLsaCount 4472 -ospfVirIfLsaCksumSum, to indicate the sum of the type-9 link- 4473 state advertisement checksums on this link. 4475 To support area scope (type-10) LSAs, the enumeration 4476 areaOpaqueLink (10) was added to ospfLsdbType in the ospfLsdbTable. 4478 To support AS scope (type-11) LSAs, the enumeration 4479 asOpaqueLink (11) was added to ospfExtLsdbType in the 4480 ospfExtLsdbTable. 4482 B.6 OSPF Compliances 4484 Compliance statements were depreciated as needed due to the fact that 4485 many new items have been added to the MIB. These statements include: 4487 -ospfCompliance 4489 New compliance statements were added as needed to replace deprecated 4490 statements. These Statements include: 4492 -ospfCompliance2 4494 Conformance groups were depreciated as needed due to the fact that 4495 many new items have been added to the MIB. These groups include: 4497 -ospfBasicGroup 4499 -ospfAreaGroup 4501 -ospfIfGroup 4503 -ospfVirtIfGroup 4505 New conformance groups were added as needed to replace deprecated 4506 groups. These groups include: 4508 -ospfBasicGroup2 4510 -ospfAreaGroup2 4512 -ospfIfGroup2 4514 -ospfVirtIfGroup2 4516 Added completely new conformance groups as needed, including: 4518 -ospfLocalLsdbGroup, which specifies support for link local (type- 4519 9) LSAs. 4521 -ospfVirtLocalLsdbGroup, which specifies support for link local 4522 (type-9) LSAs on virtual links. 4524 B.7 Miscellaneous 4526 Various sections, have been moved and or modified for clarity. 4527 Most of these changes are semantic in nature, and include, 4528 but are not limited to: 4530 -The OSPF Overview section's format was revised. Unneeded 4531 information was removed. Removed information includes OSPF TOS 4532 default values. 4534 -The Trap Overview section's format and working were revised. 4535 Unneeded information was removed. 4537 -Modified the DESCRIPTION clause of "Status" "TEXTUAL-CONVENTION" 4538 for clarity 4540 -The updates section was moved from the Overview to an appendix 4542 -Updated "REFERENCE" clauses in all objects, as needed 4544 -Modified the SEQUENCE of the OspfIfTable to reflect the true 4545 order of the objects in the Table 4547 -Modified the DESCRIPTION clause of ospfIfAuthKey due to security 4548 concerns, and to increase clarity 4550 Changed the "MAX-ACCESS" clause of 4551 "ospfHostStatus" in "ospfHostTable" to "read-create" 4553 C Security Considerations 4555 There are a number of management objects defined in this MIB that 4556 have a MAX-ACCESS clause of read-write and/or read-create. Such 4557 objects may be considered sensitive or vulnerable in some network 4558 environments. The support for SET operations in a non-secure 4559 environment without proper protection can have a negative effect on 4560 network operations. 4562 SNMPv1 by itself is not a secure environment. Even if the network 4563 itself is secure (for example by using IPSec), even then, there is no 4564 control as to who on the secure network is allowed to access and 4565 GET/SET (read/change/create/delete) the objects in this MIB. 4567 It is recommended that the implementers consider the security 4568 features as provided by the SNMPv3 framework. Specifically, the use 4569 of the User-based Security Model RFC 2574 [RFC2574] and the View- 4570 based Access Control Model RFC 2575 [RFC2575] is recommended. 4572 It is then a customer/user responsibility to ensure that the SNMP 4573 entity giving access to an instance of this MIB, is properly 4574 configured to give access to the objects only to those principals 4575 (users) that have legitimate rights to indeed GET or SET 4576 (change/create/delete) them. 4578 D Authors' Addresses 4580 Spencer Giacalone 4581 Predictive Systems, Inc. 4582 145 Hudson Street 4583 New York, NY 10013 4585 Phone: +1 (973) 301-5695 4586 EMail: spencer.giacalone@predictive.com 4588 Dan Joyal 4589 Nortel Networks, Inc. 4590 600 Technology Park Drive 4591 Billerica, MA 01821 4593 Phone: +1 (978) 288-2629 4594 EMail: djoyal@nortelnetworks.com 4596 Rob Coltun 4597 Redback Networks, Inc. 4598 300 Furguson Drive 4599 Mountain View, CA 94043 4601 Phone: +1 (650) 390-9030 4602 EMail: rcoltun@siara.com 4604 Fred Baker 4605 Cisco Systems, Inc. 4606 519 Lado Drive 4607 Santa Barbara, CA 93111 4609 Phone: +1 (805) 681-0115 4610 EMail: fred@cisco.com 4612 E Full Copyright Statement 4614 Copyright (C) The Internet Society (2000). All Rights Reserved. 4615 This document and translations of it may be copied and furnished to 4616 others, and derivative works that comment on or otherwise explain it 4617 or assist in its implementation may be prepared, copied, published 4618 and distributed, in whole or in part, without restriction of any 4619 kind, provided that the above copyright notice and this paragraph are 4620 included on all such copies and derivative works. However, this 4621 document itself may not be modified in any way, such as by removing 4622 the copyright notice or references to the Internet Society or other 4623 Internet organizations, except as needed for the purpose of 4624 developing Internet standards in which case the procedures for 4625 copyrights defined in the Internet Standards process must be 4626 followed, or as required to translate it into languages other than 4627 English. 4629 The limited permissions granted above are perpetual and will not be 4630 revoked by the Internet Society or its successors or assigns. 4632 This document and the information contained herein is provided on an 4633 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4634 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4635 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4636 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 4637 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.