idnits 2.17.1 draft-ietf-ospf-mt-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. == There are 4 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 1317: '... It is RECOMMENDED that implementors...' RFC 2119 keyword, line 1323: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 606 has weird spacing: '...ertised by a...' == Line 749 has weird spacing: '... By defau...' == Line 803 has weird spacing: '... Router inter...' == Line 1079 has weird spacing: '...ecifies the ...' -- 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 (December 15, 2009) is 5246 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) == Unused Reference: 'RFC2629' is defined on line 1282, but no explicit reference was found in the text == Unused Reference: 'RFC4915' is defined on line 1290, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1850 (Obsoleted by RFC 4750) ** Obsolete normative reference: RFC 2629 (Obsoleted by RFC 7749) Summary: 5 errors (**), 0 flaws (~~), 9 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group N. Rawat 3 Internet-Draft R. Shrivastava 4 Intended status: Standards Track Cisco Systems 5 Expires: June 18, 2010 D. Kushi 6 F5 7 December 15, 2009 9 OSPF Version 2 MIB for Multi-Topology (MT) Routing 10 draft-ietf-ospf-mt-mib-04 12 Abstract 14 This memo defines an extension to the Open Shortest Path First 15 version 2 Management Information Base (OSPFv2 MIB) for use with 16 network management protocols in the Internet community. In 17 particular it describes objects and lists considerations for the 18 management of OSPF Multi-Topology routing. 20 Status of This Memo 22 This Internet-Draft is submitted to IETF in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 This Internet-Draft will expire on June 18, 2010. 43 Copyright Notice 45 Copyright (c) 2009 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1.1. Change Log . . . . . . . . . . . . . . . . . . . . . . . . 3 62 1.1.1. Initial version . . . . . . . . . . . . . . . . . . . 3 63 1.1.2. August 2007 version . . . . . . . . . . . . . . . . . 3 64 1.1.3. April 2008 version . . . . . . . . . . . . . . . . . . 3 65 1.1.4. November 2008 version . . . . . . . . . . . . . . . . 3 66 1.1.5. December 2009 version . . . . . . . . . . . . . . . . 3 67 2. The Internet-Standard Management Framework . . . . . . . . . . 4 68 3. Short Overview of Multi-topology routing. . . . . . . . . . . 4 69 4. Relationship to Other MIBs . . . . . . . . . . . . . . . . . . 5 70 5. MIB Overview . . . . . . . . . . . . . . . . . . . . . . . . . 5 71 5.1. Conformance Groups . . . . . . . . . . . . . . . . . . . . 5 72 5.1.1. The ospfMtGeneralGroup . . . . . . . . . . . . . . . . 5 73 5.1.2. The ospfMtConfigurationGroup . . . . . . . . . . . . . 5 74 5.1.3. The ospfMtAreaGroup . . . . . . . . . . . . . . . . . 5 75 5.1.4. The ospfMtAreaTopoGroup . . . . . . . . . . . . . . . 5 76 5.1.5. The ospfMtStubAreaGroup . . . . . . . . . . . . . . . 5 77 5.1.6. The ospfMtHostGroup . . . . . . . . . . . . . . . . . 6 78 5.1.7. The ospfMtIfMetricGroup . . . . . . . . . . . . . . . 6 79 5.1.8. The ospfMtVirtIfMetricGroup . . . . . . . . . . . . . 6 80 5.1.9. The ospfMtAreaAggregateGroup . . . . . . . . . . . . . 6 81 5.2. The OSPFv2-MT-MIB Module . . . . . . . . . . . . . . . . . 6 82 5.2.1. Mib Module . . . . . . . . . . . . . . . . . . . . . . 6 83 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27 84 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 85 7.1. Normative References . . . . . . . . . . . . . . . . . . . 27 86 7.2. Informative References . . . . . . . . . . . . . . . . . . 27 87 Appendix A. IANA Considerations . . . . . . . . . . . . . . . . . 28 88 Appendix B. Security Considerations . . . . . . . . . . . . . . . 28 90 1. Introduction 92 This memo defines an extension to the Open Shortest Path First 93 version 2 Management Information Base (OSPFv2 MIB) for use with 94 network management protocols in the Internet community. In 95 particular it describes objects and lists considerations for the 96 management of OSPFv2 Multi-Topology routing. 98 1.1. Change Log 100 This section to be deleted when the document becomes approved. 102 1.1.1. Initial version 104 The initial version was submitted to the OSPF working group as a 105 working group document on January 12, 2007. 107 1.1.2. August 2007 version 109 The following changes were made for the version submitted to the IETF 110 as draft-ietf-ospf-mt-mib-01.txt: 112 Revised issue date. 114 Changed references to internet draft draft-ietf-ospf-mt-07 to 115 references to RFC4915. 117 1.1.3. April 2008 version 119 The following changes were made for the version submitted to the IETF 120 as draft-ietf-ospf-mt-mib-02.txt: 122 Revised issue date. 124 1.1.4. November 2008 version 126 The following changes were made for the version submitted to the IETF 127 as draft-ietf-ospf-mt-mib-03.txt: 129 Revised issue date. 131 1.1.5. December 2009 version 133 The following changes were made for the version submitted to the IETF 134 as draft-ietf-ospf-mt-mib-04.txt: 136 Revised issue date. 138 Updated author information. 140 2. The Internet-Standard Management Framework 142 For a detailed overview of the documents that describe the current 143 Internet-Standard Management Framework, please refer to section 7 of 144 RFC 3410 [RFC3410]. 146 Managed objects are accessed via a virtual information store, termed 147 the Management Information Base or MIB. MIB objects are generally 148 accessed through the Simple Network Management Protocol (SNMP). 149 Objects in the MIB are defined using the mechanisms defined in the 150 Structure of Management Information (SMI). This memo specifies a MIB 151 module that is compliant to the SMIv2, which is described in STD 58, 152 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 153 [RFC2580]. 155 3. Short Overview of Multi-topology routing. 157 The multi-topology extensions to OSPFv2 are changes to the base 158 version 2 specification enabling the construction of multiple routing 159 topologies through a network of routing nodes participating in the 160 protocol (through the use of these extensions). Multi-topology 161 routing (MT routing) is most useful in conjunction with class-based 162 packet forwarding. An individual routing topology may be associated 163 with a packet classifier; packets belonging to some defined class are 164 routed according to its associated routing topology. 166 Fundamentally, MT routing engenders a routing node with the ability 167 to automatically construct orthogonal routing topologies that provide 168 a node with the means to forward distinct IP packets having identical 169 destination IP addresses to different nexthop routers. A routing 170 node may, through packet inspection, associate a packet to a class; a 171 class may be associated with a distinct topology. For example, a 172 packet classifier may be defined that associates TCP traffic with 173 topology A and UDP traffic with topology B. It may be the case, for 174 example, that at any single instant of time, an IP packet bearing a 175 TCP payload destined for IP address Y is routed out interface I1 176 whereas an IP packet bearing a UDP payload destined for IP address Y 177 is routed out interface I2. This because I1 leads to the nexthop 178 router for topology A and I2 leads to the nexthop router for B; the 179 exemplified nexthop routers being distinct. 181 MT routing is essentially a reincarnation of TOS-based routing, the 182 principal difference being that packet classification decisions are 183 decoupled from the routing protocol itself -- any criteria may be 184 used to associate a packet with a topology, not simply the policy 185 implied by the encoded TOS byte definitions. 187 4. Relationship to Other MIBs 189 The OSPFv2 MIB [RFC1850][RFC4750] defines basic information for the 190 management of OSPFv2. 192 This MIB extends [RFC1850][RFC4750] to enable the management of MT 193 capable routing nodes. This MIB module introduces a scalar used to 194 determine a routing node's Multi-topology routing capabilities and a 195 set of tables that are used instead of, or in addition to, their 196 named equivalents contained within [RFC1850][RFC4750], in order to 197 manage Multi-topology routing. 199 It is envisaged that the value of the scalar 'ospfMtSupport', or the 200 absence of an instance of this object in a router's MIB, will be used 201 by applications to discover MT-capable routing nodes and hence used 202 to select an appropriate set of objects from within this MIB and 203 those contained within [RFC1850][RFC4750] to manage the device. 205 5. MIB Overview 207 This document defines the OSPFv2-MT-MIB module. 209 5.1. Conformance Groups 211 5.1.1. The ospfMtGeneralGroup 213 This group contains one object used to support the discovery of MT- 214 capable routers. 216 5.1.2. The ospfMtConfigurationGroup 218 This group contains objects used to associate a name with a multi- 219 topology identifier (MTID). 221 5.1.3. The ospfMtAreaGroup 223 This group contains an object used to configure an area-specific, 224 multi-topology routing specific parameter. 226 5.1.4. The ospfMtAreaTopoGroup 228 This group contains objects used to collect statistics and configure 229 parameters applicable to a topology within an area. 231 5.1.5. The ospfMtStubAreaGroup 233 This group contains objects used to configure metrics for topologies 234 advertised by a default Area Border Router into a stub area. 236 5.1.6. The ospfMtHostGroup 238 This group contains objects used to configure metrics for topologies 239 associated with attached hosts. 241 5.1.7. The ospfMtIfMetricGroup 243 This group contains objects used to configure metrics for topologies 244 configured on interfaces. 246 5.1.8. The ospfMtVirtIfMetricGroup 248 This group contains objects used to configure metrics for topologies 249 configured on virtual interfaces. 251 5.1.9. The ospfMtAreaAggregateGroup 253 This group contains objects used to configure address aggregation for 254 topologies. 256 5.2. The OSPFv2-MT-MIB Module 258 5.2.1. Mib Module 260 OSPFv2-MT-MIB DEFINITIONS ::= BEGIN 262 IMPORTS 263 MODULE-IDENTITY, OBJECT-TYPE, 264 mib-2, 265 Integer32, 266 Counter32, 267 IpAddress FROM SNMPv2-SMI -- [RFC2578] 268 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 269 TEXTUAL-CONVENTION, 270 RowStatus, 271 TruthValue FROM SNMPv2-TC -- [RFC2579] 272 InterfaceIndexOrZero FROM IF-MIB -- [RFC2863] 273 AreaID, 274 ospfAreaEntry, 275 RouterID, 276 Metric, 277 BigMetric FROM OSPF-MIB; -- [RFC1850] 278 [RFC4750] 280 ospfMtMIB MODULE-IDENTITY 281 LAST-UPDATED "200912100000Z" 282 ORGANIZATION "IETF OSPF Working Group" 283 CONTACT-INFO 284 "WG E-Mail: ospf@peach.ease.lsoft.com 286 WG Chairs: acee@redback.com 287 akr@cisco.com 289 Namita Rawat 290 Cisco Systems 291 510 McCarthy Blvd. 292 Milpitas, CA 95035 USA 294 Rashmi Shrivastava 295 Cisco Systems 296 510 McCarthy Blvd. 297 Milpitas, CA 95035 USA 299 David M. Kushi 300 F5 301 401 Elliot Avenue W. 302 Seattle, WA 303 " 305 DESCRIPTION 306 "The MIB module for the management of OSPF Version 2 307 Multi-topology routing. This MIB module is used in 308 conjunction with the OSFPv2 MIB module to support 309 the Multi-topology extensions. 311 Copyright (C) The IETF Trust (2009). 312 This version of this MIB module is part of 313 RFC XXXX; see the RFC itself for full legal 314 notices." 315 REVISION "200912100000Z" 316 DESCRIPTION 317 "Initial version of this MIB." 318 ::= { mib-2 nnn } -- to be determined later 320 ospfMtMIBObjects OBJECT IDENTIFIER ::= { ospfMtMIB 1 } 321 ospfMtMIBConformance OBJECT IDENTIFIER ::= { ospfMtMIB 2 } 322 ospfMtMIBNotifications OBJECT IDENTIFIER ::= { ospfMtMIB 0 } 323 ospfMtGeneral OBJECT IDENTIFIER ::= { ospfMtMIBObjects 1 } 324 ospfMtConfiguration OBJECT IDENTIFIER ::= { ospfMtMIBObjects 2 } 325 ospfMt OBJECT IDENTIFIER ::= { ospfMtMIBObjects 3 } 327 -- Textual Conventions 329 TopologyID ::= TEXTUAL-CONVENTION 330 DISPLAY-HINT "d-0" 331 STATUS current 332 DESCRIPTION 333 "A topology identifier. 335 Section 3.7 of RFC 4915 defines the mapping 336 of the topology id space." 337 REFERENCE 338 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 339 SYNTAX Integer32 (0..127) 341 -- 342 -- The objects used to manage OSPF MT 343 -- 345 ospfMtSupport OBJECT-TYPE 346 SYNTAX TruthValue 347 MAX-ACCESS read-only 348 STATUS current 349 DESCRIPTION 350 "This entity's support for Multi-topology routing. 351 When this object has a value of 'true' this entity 352 supports multi-topology routing. When the value is 353 'false' or when this object doesn't exist, this 354 entity doesn't support MT routing. This object is 355 instantiated by the agent during the managed system's 356 initialization." 357 ::= { ospfMtGeneral 1 } 359 -- OSPF MT Topology Information 361 -- A table containing a list of topologies configured on the 362 -- ospf router and each topology's name. 364 ospfMtTable OBJECT-TYPE 365 SYNTAX SEQUENCE OF OspfMtEntry 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "A table mapping a configured topology id to a name." 370 REFERENCE 371 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 372 ::= { ospfMtConfiguration 1 } 374 ospfMtEntry OBJECT-TYPE 375 SYNTAX OspfMtEntry 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "Information describing one of the topologies 380 on the router. 382 The managed system creates a row for the 383 device's default topology. This row cannot 384 be destroyed by a management station." 385 REFERENCE 386 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 387 INDEX { ospfMtTopoId } 388 ::= { ospfMtTable 1 } 390 OspfMtEntry ::= SEQUENCE { 391 ospfMtTopoId TopologyID, 392 ospfMtTopoName OCTET STRING, 393 ospfMtTopoStatus RowStatus 394 } 396 ospfMtTopoId OBJECT-TYPE 397 SYNTAX TopologyID 398 MAX-ACCESS not-accessible 399 STATUS current 400 DESCRIPTION 401 "The ID for a topology." 402 REFERENCE 403 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 404 ::= { ospfMtEntry 1 } 406 ospfMtTopoName OBJECT-TYPE 407 SYNTAX OCTET STRING (SIZE(0..255)) 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The name of the topology." 412 REFERENCE 413 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 414 ::= { ospfMtEntry 2 } 416 ospfMtTopoStatus OBJECT-TYPE 417 SYNTAX RowStatus 418 MAX-ACCESS read-create 419 STATUS current 420 DESCRIPTION 421 "This object permits management of the table by 422 facilitating actions such as row creation, 423 construction and destruction. The value of 424 this object has no effect on whether other 425 objects in this conceptual row can be modified." 426 ::= { ospfMtEntry 3 } 428 -- Multi Topology OSPF Area Table 430 -- The OSPF MT Area Data Structure contains information 431 -- regarding the various areas. The interfaces and 432 -- virtual links are configured as part of these areas. 433 -- Area 0.0.0.0, by definition, is the Backbone Area. A 434 -- new object is added to the data structure to indicate 435 -- area's MT Routing Exclusion capability. 437 ospfMtAreaTable OBJECT-TYPE 438 SYNTAX SEQUENCE OF OspfMtAreaEntry 439 MAX-ACCESS not-accessible 440 STATUS current 441 DESCRIPTION 442 "Information describing area parameters supporting 443 Multi-topology routing. 445 The entries in this table augment the entries contained 446 within the ospfAreaTable; an augmenting entry is created 447 by the managed system when the value of ospfMtSupport is 448 'true'." 449 REFERENCE 450 "OSPF Version 2, Section 6 The Area Data Structure 451 and RFC 4915, Multi-Topology (MT) Routing in OSPF" 452 ::= { ospfMt 1 } 454 ospfMtAreaEntry OBJECT-TYPE 455 SYNTAX OspfMtAreaEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "Information describing the configured parameters 460 and cumulative statistics of one of the router's 461 attached areas." 462 AUGMENTS { ospfAreaEntry } 463 ::= { ospfMtAreaTable 1 } 465 OspfMtAreaEntry ::= SEQUENCE { 466 ospfMtAreaExclusion TruthValue 467 } 469 ospfMtAreaExclusion OBJECT-TYPE 470 SYNTAX TruthValue 471 MAX-ACCESS read-only 472 STATUS current 473 DESCRIPTION 474 "Describes the area's MT default exclusion 475 capability." 477 REFERENCE 478 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 479 ::= { ospfMtAreaEntry 1 } 481 -- Multi Topology OSPF Area Topology Table 482 -- This table gives topology specific information for the area. 484 ospfMtAreaTopoTable OBJECT-TYPE 485 SYNTAX SEQUENCE OF OspfMtAreaTopoEntry 486 MAX-ACCESS not-accessible 487 STATUS current 488 DESCRIPTION 489 "Information describing the configured parameters 490 and cumulative statistics of the router's topologies 491 in an area." 492 REFERENCE 493 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 494 ::= { ospfMt 2 } 496 ospfMtAreaTopoEntry OBJECT-TYPE 497 SYNTAX OspfMtAreaTopoEntry 498 MAX-ACCESS not-accessible 499 STATUS current 500 DESCRIPTION 501 "Information describing the configured parameters 502 and cumulative statistics of a topology in an area." 503 INDEX { ospfMtAreaTopoId, ospfMtAreaId } 504 ::= { ospfMtAreaTopoTable 1 } 506 OspfMtAreaTopoEntry ::= SEQUENCE { 507 ospfMtAreaTopoId TopologyID, 508 ospfMtAreaId AreaID, 509 ospfMtSpfRuns Counter32, 510 ospfMtAreaSummary INTEGER, 511 ospfMtAreaTopoStatus RowStatus 512 } 514 ospfMtAreaTopoId OBJECT-TYPE 515 SYNTAX TopologyID 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 "The ID for a topology; this can 520 be derived from the OSPF instance." 521 REFERENCE 522 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 523 ::= { ospfMtAreaTopoEntry 1 } 525 ospfMtAreaId OBJECT-TYPE 526 SYNTAX AreaID 527 MAX-ACCESS not-accessible 528 STATUS current 529 DESCRIPTION 530 "The 32 bit identifier for the Area. On creation, 531 this can be derived from the OSPF instance." 532 ::= { ospfMtAreaTopoEntry 2 } 534 ospfMtSpfRuns OBJECT-TYPE 535 SYNTAX Counter32 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "The number of times the SPF is run for a 540 given topology." 541 REFERENCE 542 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 543 ::= { ospfMtAreaTopoEntry 3 } 545 ospfMtAreaSummary OBJECT-TYPE 546 SYNTAX INTEGER { 547 noAreaSummary (1), 548 sendAreaSummary (2) 549 } 550 MAX-ACCESS read-create 551 STATUS current 552 DESCRIPTION 553 "This object controls the importation of summary LSAs 554 into stub areas. It has no effect on other areas. 556 If its value is 'noAreaSummary', the router will 557 neither originate nor propagate summary LSAs into 558 the stub area. It will rely entirely on its default 559 route. 561 If its value is 'sendAreaSummary', the router will 562 both summarize and propagate summary LSAs." 563 DEFVAL { noAreaSummary } 564 ::= { ospfMtAreaTopoEntry 4 } 566 ospfMtAreaTopoStatus OBJECT-TYPE 567 SYNTAX RowStatus 568 MAX-ACCESS read-create 569 STATUS current 570 DESCRIPTION 571 "This object permits management of the table by 572 facilitating actions such as row creation, 573 construction and destruction. 575 The value of this object has no effect on 576 whether other objects in this conceptual row can be 577 modified." 578 ::= { ospfMtAreaTopoEntry 5 } 580 -- OSPF MT Area Default Metric Table 582 -- The OSPF MT Area Default Metric Table describes the metrics 583 -- that a default Area Border Router advertises into a 584 -- Stub area for a particular topology. The ABR may advertise 585 -- different metrics for different topologies. 587 ospfMtStubAreaTable OBJECT-TYPE 588 SYNTAX SEQUENCE OF OspfMtStubAreaEntry 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "The set of metrics that will be advertised 593 for a specific topology by a default Area 594 Border Router into a stub area." 595 REFERENCE 596 "OSPF Version 2, Appendix C.2, Area Parameters, 597 and RFC 4915, Multi-Topology (MT) Routing in OSPF" 598 ::= { ospfMt 3 } 600 ospfMtStubAreaEntry OBJECT-TYPE 601 SYNTAX OspfMtStubAreaEntry 602 MAX-ACCESS not-accessible 603 STATUS current 604 DESCRIPTION 605 "The metric for a specific topology that will be 606 advertised by a default Area Border Router 607 into a stub area." 608 REFERENCE 609 "OSPF Version 2, Appendix C.2, Area Parameters 610 and RFC 4915, Multi-Topology (MT) Routing in OSPF" 611 INDEX { ospfMtStubAreaTopoId, ospfMtStubAreaId } 612 ::= { ospfMtStubAreaTable 1 } 614 OspfMtStubAreaEntry ::= SEQUENCE { 615 ospfMtStubAreaTopoId TopologyID, 616 ospfMtStubAreaId AreaID, 617 ospfMtStubMetric BigMetric, 618 ospfMtStubMetricType INTEGER, 619 ospfMtStubStatus RowStatus 620 } 621 ospfMtStubAreaTopoId OBJECT-TYPE 622 SYNTAX TopologyID 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "The ID for a topology; this can be derived 627 from the OSPF instance." 628 REFERENCE 629 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 630 ::= { ospfMtStubAreaEntry 1 } 632 ospfMtStubAreaId OBJECT-TYPE 633 SYNTAX AreaID 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "The 32 bit identifier for the Stub Area; this 638 can be derived from the OSPF instance." 639 ::= { ospfMtStubAreaEntry 2 } 641 ospfMtStubMetric OBJECT-TYPE 642 SYNTAX BigMetric 643 MAX-ACCESS read-create 644 STATUS current 645 DESCRIPTION 646 "The metric value associated with a topology." 647 ::= { ospfMtStubAreaEntry 3 } 649 ospfMtStubMetricType OBJECT-TYPE 650 SYNTAX INTEGER { 651 ospfMtMetric (1), -- OSPF Metric 652 comparableCost (2), -- external type 1 653 nonComparable (3) -- external type 2 654 } 655 MAX-ACCESS read-create 656 STATUS current 657 DESCRIPTION 658 "This object contains the type of metric advertised 659 as a default route." 660 DEFVAL { ospfMtMetric } 661 ::= { ospfMtStubAreaEntry 4 } 663 ospfMtStubStatus OBJECT-TYPE 664 SYNTAX RowStatus 665 MAX-ACCESS read-create 666 STATUS current 667 DESCRIPTION 668 "This object permits management of the table by 669 facilitating actions such as row creation, 670 construction and destruction. 672 The value of this object has no effect on 673 whether other objects in this conceptual row can be 674 modified." 675 ::= { ospfMtStubAreaEntry 5 } 677 -- OSPF MT Host Table 679 -- The Host/Metric Table is used to indicate which hosts are 680 -- directly attached to the managed router, and the set of metrics 681 -- that should be advertised for them. 682 -- 683 ospfMtHostTable OBJECT-TYPE 684 SYNTAX SEQUENCE OF OspfMtHostEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "The list of hosts and their associated metrics 689 that the router will advertise as host routes." 690 REFERENCE 691 "OSPF Version 2, Appendix C.6 Host route parameters 692 and RFC 4915, Multi-Topology (MT) Routing in OSPF" 693 ::= { ospfMt 4 } 695 ospfMtHostEntry OBJECT-TYPE 696 SYNTAX OspfMtHostEntry 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "A metric to be advertised, for a specific topology, 701 when a given host is reachable." 702 INDEX { ospfMtHostTopoId, ospfMtHostIpAddress } 703 ::= { ospfMtHostTable 1 } 705 OspfMtHostEntry ::= SEQUENCE { 706 ospfMtHostTopoId TopologyID, 707 ospfMtHostIpAddress IpAddress, 708 ospfMtHostMetric Metric, 709 ospfMtHostAreaID AreaID, 710 ospfMtHostStatus RowStatus 711 } 713 ospfMtHostTopoId OBJECT-TYPE 714 SYNTAX TopologyID 715 MAX-ACCESS not-accessible 716 STATUS current 717 DESCRIPTION 718 "The ID for a topology." 719 REFERENCE 720 "RFC 4915, Multi-Topology (MT) Routing in OSPF" 721 ::= { ospfMtHostEntry 1 } 723 ospfMtHostIpAddress OBJECT-TYPE 724 SYNTAX IpAddress 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "The IP Address of the Host." 729 REFERENCE 730 "OSPF Version 2, Appendix C.6 Host route parameters." 731 ::= { ospfMtHostEntry 2 } 733 ospfMtHostMetric OBJECT-TYPE 734 SYNTAX Metric 735 MAX-ACCESS read-create 736 STATUS current 737 DESCRIPTION 738 "The Metric to be advertised." 739 REFERENCE 740 "OSPF Version 2, Appendix C.6 Host route parameters." 741 ::= { ospfMtHostEntry 3 } 743 ospfMtHostAreaID OBJECT-TYPE 744 SYNTAX AreaID 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "The Area in which the Host Entry is to be found. 749 By default, the area that a subsuming OSPF in- 750 terface is in, or 0.0.0.0." 751 REFERENCE 752 "OSPF Version 2, Appendix C.2 Area parameters." 753 ::= { ospfMtHostEntry 4 } 755 ospfMtHostStatus OBJECT-TYPE 756 SYNTAX RowStatus 757 MAX-ACCESS read-create 758 STATUS current 759 DESCRIPTION 760 "This object permits management of the table by 761 facilitating actions such as row creation, 762 construction and destruction. 764 The value of this object has no effect on 765 whether other objects in this conceptual row can be 766 modified." 767 ::= { ospfMtHostEntry 5 } 769 -- OSPF MT Interface Metric Table 771 -- The Metric Table describes the metrics to be advertised 772 -- for a specified interface for the configured topologies. 773 -- As such, this table is an adjunct of the OSPF Interface 774 -- Table. 776 -- For the purposes of this specification, the measure of 777 -- bandwidth 779 -- Metric = 10^8 / ifSpeed 781 -- is the default value. For multiple link interfaces, note 782 -- that ifSpeed is the sum of the individual link speeds. 783 -- This yields a number having the following typical values: 785 -- Network Type/bit rate Metric 787 -- >= 100 MBPS 1 788 -- Ethernet/802.3 10 789 -- E1 48 790 -- T1 (ESF) 65 791 -- 64 KBPS 1562 792 -- 56 KBPS 1785 793 -- 19.2 KBPS 5208 794 -- 9.6 KBPS 10416 795 ospfMtIfMetricTable OBJECT-TYPE 796 SYNTAX SEQUENCE OF OspfMtIfMetricEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "The topology specific metrics for a non-virtual 801 interface identified by the interface index." 802 REFERENCE 803 "OSPF Version 2, Appendix C.3 Router interface 804 parameters and RFC 4915, Multi-Topology (MT) Routing 805 in OSPF" 806 ::= { ospfMt 5 } 808 ospfMtIfMetricEntry OBJECT-TYPE 809 SYNTAX OspfMtIfMetricEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 813 "A particular topology specific metric for 814 a non-virtual interface identified by the 815 interface index." 816 REFERENCE 817 "OSPF Version 2, Appendix C.3 Router interface 818 parameters." 819 INDEX { ospfMtIfMetricTopoId, 820 ospfMtIfMetricIpAddress, 821 ospfMtIfMetricAddressLessIf } 822 ::= { ospfMtIfMetricTable 1 } 824 OspfMtIfMetricEntry ::= SEQUENCE { 825 ospfMtIfMetricTopoId TopologyID, 826 ospfMtIfMetricIpAddress IpAddress, 827 ospfMtIfMetricAddressLessIf InterfaceIndexOrZero, 828 ospfMtIfMetricValue Metric, 829 ospfMtIfMetricTopoStatus RowStatus 830 } 832 ospfMtIfMetricTopoId OBJECT-TYPE 833 SYNTAX TopologyID 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "The topology specific metric being referenced. 838 On row creation, this can be derived from the 839 OSPF instance." 840 ::= { ospfMtIfMetricEntry 1 } 842 ospfMtIfMetricIpAddress OBJECT-TYPE 843 SYNTAX IpAddress 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "The IP address of this OSPF interface. On 848 row creation, this can be derived from the 849 OSPF instance." 850 ::= { ospfMtIfMetricEntry 2 } 852 ospfMtIfMetricAddressLessIf OBJECT-TYPE 853 SYNTAX InterfaceIndexOrZero 854 MAX-ACCESS not-accessible 855 STATUS current 856 DESCRIPTION 857 "For the purpose of easing the instancing of 858 addressed and addressless interfaces, this 859 object takes the value 0 on interfaces having 860 IP Addresses, and the value of ifIndex for 861 interfaces having no IP Address. On row 862 creation, this can be derived from the 863 OSPF instance." 864 ::= { ospfMtIfMetricEntry 3 } 866 ospfMtIfMetricValue OBJECT-TYPE 867 SYNTAX Metric 868 MAX-ACCESS read-create 869 STATUS current 870 DESCRIPTION 871 "The metric associated with this topology." 872 ::= { ospfMtIfMetricEntry 4 } 874 ospfMtIfMetricTopoStatus OBJECT-TYPE 875 SYNTAX RowStatus 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "This object permits management of the table by 880 facilitating actions such as row creation, 881 construction and destruction. 883 The value of this object has no effect on 884 whether other objects in this conceptual row can be 885 modified." 886 ::= { ospfMtIfMetricEntry 5 } 888 -- OSPF MT Virtual Interface Metric Table 890 -- The Virtual Interface Metric Table describes the metrics to be 891 -- advertised for a specific virtual interface under a specific 892 -- topology. As such, this table is an adjunct of the OSPF Virtual 893 -- Interface Table. 895 ospfMtVirtIfMetricTable OBJECT-TYPE 896 SYNTAX SEQUENCE OF OspfMtVirtIfMetricEntry 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "The topology specific metrics for a virtual 901 interface." 902 REFERENCE 903 "OSPF Version 2, Appendix C.3 Router interface 904 parameters and RFC 4915, Multi-Topology (MT) Routing 905 in OSPF" 906 ::= { ospfMt 6 } 908 ospfMtVirtIfMetricEntry OBJECT-TYPE 909 SYNTAX OspfMtVirtIfMetricEntry 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "A particular topology specific metric for 914 a virtual interface." 915 REFERENCE 916 "OSPF Version 2, Appendix C.3 Router interface 917 parameters." 918 INDEX { ospfMtVirtIfMetricTopoId, 919 ospfMtVirtIfMetricArea, 920 ospfMtVirtIfMetricNbrRtrId, 921 ospfMtVirtIfMetricNbrIpAddress } 922 ::= { ospfMtVirtIfMetricTable 1 } 924 OspfMtVirtIfMetricEntry ::= SEQUENCE { 925 ospfMtVirtIfMetricTopoId TopologyID, 926 ospfMtVirtIfMetricArea AreaID, 927 ospfMtVirtIfMetricNbrRtrId RouterID, 928 ospfMtVirtIfMetricNbrIpAddress IpAddress, 929 ospfMtVirtIfMetricValue Metric, 930 ospfMtVirtIfMetricTopoStatus RowStatus 931 } 933 ospfMtVirtIfMetricTopoId OBJECT-TYPE 934 SYNTAX TopologyID 935 MAX-ACCESS not-accessible 936 STATUS current 937 DESCRIPTION 938 "The topology specific metric being referenced. 939 On row creation, this can be derived from the 940 OSPF instance." 941 ::= { ospfMtVirtIfMetricEntry 1 } 943 ospfMtVirtIfMetricArea OBJECT-TYPE 944 SYNTAX AreaID 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "A 32 bit identifier for Area ID." 949 ::= { ospfMtVirtIfMetricEntry 2 } 951 ospfMtVirtIfMetricNbrRtrId OBJECT-TYPE 952 SYNTAX RouterID 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "A 32 bit identifier for Router ID." 958 ::= { ospfMtVirtIfMetricEntry 3 } 960 ospfMtVirtIfMetricNbrIpAddress OBJECT-TYPE 961 SYNTAX IpAddress 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "A 32 bit identifier identifying virtual neighbor 966 end point IP address." 967 ::= { ospfMtVirtIfMetricEntry 4 } 969 ospfMtVirtIfMetricValue OBJECT-TYPE 970 SYNTAX Metric 971 MAX-ACCESS read-create 972 STATUS current 973 DESCRIPTION 974 "The metric associated with the topology." 975 ::= { ospfMtVirtIfMetricEntry 5 } 977 ospfMtVirtIfMetricTopoStatus OBJECT-TYPE 978 SYNTAX RowStatus 979 MAX-ACCESS read-create 980 STATUS current 981 DESCRIPTION 982 "This object permits management of the table by 983 facilitating actions such as row creation, 984 construction and destruction. 986 The value of this object has no effect on 987 whether other objects in this conceptual row can be 988 modified." 989 ::= { ospfMtVirtIfMetricEntry 6 } 991 -- The OSPF MT Area Aggregate Table 992 -- When the value of ospfMtSupport is 'true' this table is 993 -- used instead of the ospfAreaAggregate table defined 994 -- in RFC 1850 and RFC 4750. It is used to support aggregation 995 -- across multiple topologies. 997 ospfMtAreaAggregateTable OBJECT-TYPE 998 SYNTAX SEQUENCE OF OspfMtAreaAggregateEntry 999 MAX-ACCESS not-accessible 1000 STATUS current 1001 DESCRIPTION 1002 "A range of IP addresses specified by an IP 1003 address/IP network mask pair. For example, 1004 class B address range of X.X.X.X with a network 1005 mask of 255.255.0.0 includes all IP addresses 1006 from X.X.0.0 to X.X.255.255. Note that if 1007 ranges are configured such that one range 1008 subsumes another range (e.g., 10.0.0.0 mask 1009 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 1010 most specific match is the preferred one." 1011 REFERENCE 1012 "OSPF Version 2, Appendix C.2 Area parameters. 1013 and RFC 4915, Multi-Topology (MT) Routing in OSPF" 1014 ::= { ospfMt 7 } 1016 ospfMtAreaAggregateEntry OBJECT-TYPE 1017 SYNTAX OspfMtAreaAggregateEntry 1018 MAX-ACCESS not-accessible 1019 STATUS current 1020 DESCRIPTION 1021 "A range of IP addresses specified by an IP 1022 address/IP network mask pair. For example, 1023 class B address range of X.X.X.X with a network 1024 mask of 255.255.0.0 includes all IP addresses 1025 from X.X.0.0 to X.X.255.255. Note that if 1026 ranges are range configured such that one range 1027 subsumes another range (e.g., 10.0.0.0 mask 1028 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the 1029 most specific match is the preferred one." 1030 REFERENCE 1031 "OSPF Version 2, Appendix C.2 Area parameters." 1032 INDEX { ospfMtAreaAggregateTopoId, 1033 ospfMtAreaAggregateAreaID, 1034 ospfMtAreaAggregateLsdbType, 1035 ospfMtAreaAggregateNet, 1036 ospfMtAreaAggregateMask } 1037 ::= { ospfMtAreaAggregateTable 1 } 1039 OspfMtAreaAggregateEntry ::= SEQUENCE { 1040 ospfMtAreaAggregateTopoId TopologyID, 1041 ospfMtAreaAggregateAreaID AreaID, 1042 ospfMtAreaAggregateLsdbType INTEGER, 1043 ospfMtAreaAggregateNet IpAddress, 1044 ospfMtAreaAggregateMask IpAddress, 1045 ospfMtAreaAggregateEffect INTEGER, 1046 ospfMtAreaAggregateStatus RowStatus 1047 } 1049 ospfMtAreaAggregateTopoId OBJECT-TYPE 1050 SYNTAX TopologyID 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "The ID for a topology." 1055 REFERENCE 1056 "RFC 4915, Multi Topology (MT) Routing in OSPF" 1057 ::= { ospfMtAreaAggregateEntry 1 } 1059 ospfMtAreaAggregateAreaID OBJECT-TYPE 1060 SYNTAX AreaID 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "The Area in which the Address Aggregate is to 1065 be found." 1066 REFERENCE 1067 "OSPF Version 2, Appendix C.2 Area parameters." 1068 ::= { ospfMtAreaAggregateEntry 2 } 1070 ospfMtAreaAggregateLsdbType OBJECT-TYPE 1071 SYNTAX INTEGER { 1072 summaryLink (3), 1073 nssaExternalLink (7) 1074 } 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "The type of the Address Aggregate. This field 1079 specifies the Lsdb type that this Address 1080 Aggregate applies to." 1081 REFERENCE 1082 "OSPF Version 2, Appendix A.4.1 The Link State 1083 Advertisement header." 1084 ::= { ospfMtAreaAggregateEntry 3 } 1086 ospfMtAreaAggregateNet OBJECT-TYPE 1087 SYNTAX IpAddress 1088 MAX-ACCESS not-accessible 1089 STATUS current 1090 DESCRIPTION 1091 "The IP Address of the Net or Subnet indicated 1092 by the range." 1093 REFERENCE 1094 "OSPF Version 2, Appendix C.2 Area parameters." 1095 ::= { ospfMtAreaAggregateEntry 4 } 1097 ospfMtAreaAggregateMask OBJECT-TYPE 1098 SYNTAX IpAddress 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "The Subnet Mask that pertains to the Net or 1103 Subnet." 1104 REFERENCE 1105 "OSPF Version 2, Appendix C.2 Area parameters." 1106 ::= { ospfMtAreaAggregateEntry 5 } 1108 ospfMtAreaAggregateEffect OBJECT-TYPE 1109 SYNTAX INTEGER { 1110 advertiseMatching (1), 1111 doNotAdvertiseMatching (2) 1112 } 1113 MAX-ACCESS read-create 1114 STATUS current 1115 DESCRIPTION 1116 "Subnets subsumed by ranges either trigger the 1117 advertisement of the indicated aggregate 1118 (advertiseMatching), or result in the subnet's 1119 not being advertised at all outside the area." 1120 DEFVAL { advertiseMatching } 1121 ::= { ospfMtAreaAggregateEntry 6 } 1123 ospfMtAreaAggregateStatus OBJECT-TYPE 1124 SYNTAX RowStatus 1125 MAX-ACCESS read-create 1126 STATUS current 1127 DESCRIPTION 1128 "This object permits management of the table by 1129 facilitating actions such as row creation, 1130 construction and destruction. 1132 The value of this object has no effect on 1133 whether other objects in this conceptual row can be 1134 modified." 1135 ::= { ospfMtAreaAggregateEntry 7 } 1137 -- Conformance 1138 ospfMtMIBCompliances OBJECT IDENTIFIER ::= { ospfMtMIBConformance 1 } 1139 ospfMtMIBGroups OBJECT IDENTIFIER ::= { ospfMtMIBConformance 2 } 1141 ospfMIBCompliance MODULE-COMPLIANCE 1142 STATUS current 1143 DESCRIPTION 1144 "The compliance statement for entities which support 1145 OSPFv2 Multi-topology routing." 1146 MODULE MANDATORY-GROUPS { ospfMtAreaGroup, 1147 ospfMtAreaTopoGroup, 1148 ospfMtStubAreaGroup, 1149 ospfMtHostGroup, 1150 ospfMtIfMetricGroup, 1151 ospfMtVirtIfMetricGroup, 1152 ospfMtAreaAggregateGroup } 1154 GROUP ospfMtGeneralGroup 1155 DESCRIPTION 1156 "All systems supporting discovery of OSPFv2 1157 capabilities should support this group." 1159 GROUP ospfMtConfigurationGroup 1160 DESCRIPTION 1161 "Only systems that reference topologies by name 1162 instead of number need to support this group." 1163 ::= { ospfMtMIBCompliances 1 } 1165 -- Units of Conformance 1167 ospfMtGeneralGroup OBJECT-GROUP 1168 OBJECTS { ospfMtSupport } 1169 STATUS current 1170 DESCRIPTION 1171 "A collection of objects used to manage OSPF 1172 entities supporting Multi-topology routing." 1173 ::= { ospfMtMIBGroups 1 } 1175 ospfMtConfigurationGroup OBJECT-GROUP 1176 OBJECTS { ospfMtTopoName, 1177 ospfMtTopoStatus } 1178 STATUS current 1179 DESCRIPTION 1180 "A collection of objects used to manage OSPF 1181 entities supporting Multi-topology routing." 1182 ::= { ospfMtMIBGroups 2 } 1184 ospfMtAreaGroup OBJECT-GROUP 1185 OBJECTS { ospfMtAreaExclusion } 1186 STATUS current 1187 DESCRIPTION 1188 "A collection of objects used to manage OSPF 1189 entities supporting Multi-topology routing and 1190 areas." 1191 ::= { ospfMtMIBGroups 3 } 1193 ospfMtAreaTopoGroup OBJECT-GROUP 1194 OBJECTS { ospfMtSpfRuns, 1195 ospfMtAreaSummary, 1196 ospfMtAreaTopoStatus } 1197 STATUS current 1198 DESCRIPTION 1199 "A collection of objects used to manage OSPF 1200 entities supporting Multi-topology routing." 1201 ::= { ospfMtMIBGroups 4 } 1203 ospfMtStubAreaGroup OBJECT-GROUP 1204 OBJECTS { ospfMtStubMetric, 1205 ospfMtStubMetricType, 1206 ospfMtStubStatus } 1207 STATUS current 1208 DESCRIPTION 1209 "A collection of objects used to manage OSPF 1210 entities supporting Multi-topology routing." 1211 ::= { ospfMtMIBGroups 5 } 1213 ospfMtHostGroup OBJECT-GROUP 1214 OBJECTS { ospfMtHostMetric, 1215 ospfMtHostAreaID, 1216 ospfMtHostStatus } 1217 STATUS current 1218 DESCRIPTION 1219 "A collection of objects used to manage OSPF 1220 entities supporting Multi-topology routing." 1221 ::= { ospfMtMIBGroups 6 } 1223 ospfMtIfMetricGroup OBJECT-GROUP 1224 OBJECTS { ospfMtIfMetricValue, 1225 ospfMtIfMetricTopoStatus } 1226 STATUS current 1227 DESCRIPTION 1228 "A collection of objects used to manage OSPF 1229 entities supporting Multi-topology routing." 1230 ::= { ospfMtMIBGroups 7 } 1232 ospfMtVirtIfMetricGroup OBJECT-GROUP 1233 OBJECTS { ospfMtVirtIfMetricValue, 1234 ospfMtVirtIfMetricTopoStatus } 1235 STATUS current 1236 DESCRIPTION 1237 "A collection of objects used to manage OSPF 1238 entities supporting Multi-topology routing." 1239 ::= { ospfMtMIBGroups 8 } 1241 ospfMtAreaAggregateGroup OBJECT-GROUP 1242 OBJECTS { ospfMtAreaAggregateEffect, 1243 ospfMtAreaAggregateStatus 1244 } 1245 STATUS current 1246 DESCRIPTION 1247 "A collection of objects used to manage OSPF 1248 entities supporting Multi-topology routing." 1249 ::= { ospfMtMIBGroups 9 } 1251 END 1253 6. Acknowledgements 1255 The authors wish to thank Bill Fenner, Tom Henderson, Acee Lindem, 1256 Peter Psenak and Rajiv Raghunarayan for their helpful comments and 1257 careful review of this document. 1259 7. References 1261 7.1. Normative References 1263 [RFC1850] Baker, F. and R. Coltun, "OSPF Version 2 Management 1264 Information Base", RFC 1850, November 1995. 1266 [RFC4750] Joyal, D., Galecki, P., Giacalone, S., Coltun, R., and F. 1267 Baker, "OSPF Version 2 Management Information Base", 1268 RFC 4750, December 2006. 1270 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1271 Schoenwaelder, Ed., "Structure of Management Information 1272 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1274 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1275 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1276 STD 58, RFC 2579, April 1999. 1278 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1279 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1280 April 1999. 1282 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 1283 June 1999. 1285 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1286 MIB", RFC 2863, June 2000. 1288 7.2. Informative References 1290 [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. 1291 Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", 1292 RFC 4915, June 2007. 1294 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1295 "Introduction and Applicability Statements for Internet- 1296 Standard Management Framework", RFC 3410, December 2002. 1298 Appendix A. IANA Considerations 1300 IANA is requested to make a MIB OID assignment for the OSPFv2-MT-MIB 1301 module under the appropriate subtree. 1303 Appendix B. Security Considerations 1305 There are many management objects defined in these MIB modules with a 1306 MAX-ACCESS clause of read-write and/or read-create. Such objects may 1307 be considered sensitive or vulnerable in some network environments. 1308 The support for SET operations in a non-secure environment without 1309 proper protection can have a negative effect on network operations. 1311 SNMP versions prior to SNMPv3 did not include adequate security. 1312 Even if the network itself is secure (for example by using IPSec), 1313 even then, there is no control as to who on the secure network is 1314 allowed to access and GET/SET (read/change/create/delete) the objects 1315 in this MIB module. 1317 It is RECOMMENDED that implementors consider the security features as 1318 provided by the SNMPv3 framework (see [RFC3410], section 8), 1319 including full support for the SNMPv3 cryptographic mechanisms (for 1320 authentication and privacy). 1322 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1323 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1324 enable cryptographic security. It is then a customer/operator 1325 responsibility to ensure that the SNMP entity giving access to an 1326 instance of this MIB module is properly configured to give access to 1327 the objects only to those principals (users) that have legitimate 1328 rights to indeed GET or SET (change/create/delete) them. 1330 Authors' Addresses 1332 Namita Rawat 1333 Cisco Systems 1334 510 McCarthy Blvd. 1335 Milpitas, CA 1336 USA 1338 EMail: nrawat@cisco.com 1339 Rashmi Shrivastava 1340 Cisco Systems 1341 510 McCarthy Blvd. 1342 Milpitas, CA 1343 USA 1345 EMail: rashi@cisco.com 1347 David M. Kushi 1348 F5 1349 2460 North First Street 1350 San Jose, CA 1351 USA 1353 EMail: d.kushi@f5.com