idnits 2.17.1 draft-ietf-ospf-cidr-route-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == 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 an Abstract 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 246 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 123 has weird spacing: '...current ipFor...' == Line 149 has weird spacing: '...oute to a pa...' == Line 200 has weird spacing: '... entry with ...' == Line 206 has weird spacing: '...icit or other...' == Line 207 has weird spacing: '...nstance of t...' == (241 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 (March 1995) is 10634 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: '1' is defined on line 1818, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 1824, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 1829, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1835, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 1840, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 1843, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1849, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '2') ** Obsolete normative reference: RFC 1448 (ref. '3') (Obsoleted by RFC 1905) ** Obsolete normative reference: RFC 1443 (ref. '6') (Obsoleted by RFC 1903) ** Obsolete normative reference: RFC 1354 (ref. '7') (Obsoleted by RFC 2096) Summary: 17 errors (**), 0 flaws (~~), 14 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 DRAFT IP Forwarding Table MIB March 1995 4 IP Forwarding Table MIB 6 Fri Mar 17 12:32:57 PST 1995 7 draft-ietf-ospf-cidr-route-mib-04.txt 9 Fred Baker 10 Cisco Systems 11 fred@cisco.com 13 Status of this Memo 15 This document is an Internet Draft. Internet Drafts are 16 working documents of the Internet Engineering Task Force 17 (IETF), its Areas, and its Working Groups. Note that other 18 groups may also distribute working documents as Internet 19 Drafts. 21 Internet Drafts are valid for a maximum of six months and may 22 be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet Drafts as reference 24 material or to cite them other than as a "work in progress". 26 1. Introduction 28 This memo defines an update to RFC 1354, "IP Forwarding Table 29 MIB", for Classless Inter-Domain Routing (CIDR). That 30 document was developed by the Router Requirements Working 31 Group as an update to RFC 1213's ipRouteTable, with the 32 display of multiple routes as a primary objective. The 33 significant difference between this MIB and RFC 1354 is the 34 recognition (explicitly discussed but by consensus left to 35 future work) that CIDR routes may have the same network number 36 but different network masks. 38 2. The SNMPv2 Network Management Framework 40 The SNMPv2 Network Management Framework consists of four major 41 components. They are: 43 o RFC 1441 which defines the SMI, the mechanisms used for 44 describing and naming objects for the purpose of 45 management. 47 o RFC 1213 defines MIB-II, the core set of managed objects 48 for the Internet suite of protocols. 50 o RFC 1445 which defines the administrative and other 51 architectural aspects of the framework. 53 o RFC 1448 which defines the protocol used for network 54 access to managed objects. 56 The Framework permits new objects to be defined for the 57 purpose of experimentation and evaluation. 59 2.1. Object Definitions 61 Managed objects are accessed via a virtual information store, 62 termed the Management Information Base or MIB. Objects in the 63 MIB are defined using the subset of Abstract Syntax Notation 64 One (ASN.1) defined in the SMI. In particular, each object 65 object type is named by an OBJECT IDENTIFIER, an 66 administratively assigned name. The object type together with 67 an object instance serves to uniquely identify a specific 68 instantiation of the object. For human convenience, we often 69 use a textual string, termed the descriptor, to refer to the 70 object type. 72 3. Overview 74 The MIB consists of two tables and two global objects. 76 (1) The object ipForwardNumber indicates the number of 77 current routes. This is primarily to avoid having to 78 read the table in order to determine this number. 80 (2) The ipForwardTable updates the RFC 1213 ipRouteTable to 81 display multipath IP Routes. This is in turn obsoleted 82 by the ipCidrRouteTable. 84 (3) The ipCidrRouteTable updates the RFC 1213 ipRouteTable to 85 display multipath IP Routes having the same network 86 number but differing network masks. 88 4. Definitions 90 IP-FORWARD-MIB DEFINITIONS ::= BEGIN 92 IMPORTS 93 MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Integer32, Gauge32 94 FROM SNMPv2-SMI 95 RowStatus 96 FROM SNMPv2-TC 97 ip 98 FROM RFC1213-MIB 99 MODULE-COMPLIANCE, OBJECT-GROUP 100 FROM SNMPv2-CONF; 102 ipForward MODULE-IDENTITY 103 LAST-UPDATED "9503171232Z" -- Fri Mar 17 12:32:57 PST 1995 104 ORGANIZATION "IETF OSPF Working Group" 105 CONTACT-INFO 106 " Fred Baker 107 Postal: Cisco Systems 108 519 Lado Drive 109 Santa Barbara, California 93111 111 Phone: +1 805 681 0115 112 Email: fred@cisco.com 113 " 114 DESCRIPTION 115 "The MIB module for the display of CIDR multipath IP Routes." 116 ::= { ip 24 } 118 ipForwardNumber OBJECT-TYPE 119 SYNTAX Gauge32 120 MAX-ACCESS read-only 121 STATUS obsolete 122 DESCRIPTION 123 "The number of current ipForwardTable entries 124 that are not invalid." 125 ::= { ipForward 1 } 127 -- IP Forwarding Table 129 -- The IP Forwarding Table obsoletes and replaces the ipRoute 130 -- Table current in MIB-I and MIB-II. It adds knowledge of 131 -- the autonomous system of the next hop, multiple next hop 132 -- support, and policy routing support. 134 ipForwardTable OBJECT-TYPE 135 SYNTAX SEQUENCE OF IpForwardEntry 136 MAX-ACCESS not-accessible 137 STATUS obsolete 138 DESCRIPTION 139 "This entity's IP Routing table." 140 REFERENCE 141 "RFC 1213 Section 6.6, The IP Group" 142 ::= { ipForward 2 } 144 ipForwardEntry OBJECT-TYPE 145 SYNTAX IpForwardEntry 146 MAX-ACCESS not-accessible 147 STATUS obsolete 148 DESCRIPTION 149 "A particular route to a particular destina- 150 tion, under a particular policy." 151 INDEX { 152 ipForwardDest, 153 ipForwardProto, 154 ipForwardPolicy, 155 ipForwardNextHop 156 } 157 ::= { ipForwardTable 1 } 159 IpForwardEntry ::= 160 SEQUENCE { 161 ipForwardDest 162 IpAddress, 163 ipForwardMask 164 IpAddress, 165 ipForwardPolicy 166 Integer32, 167 ipForwardNextHop 168 IpAddress, 169 ipForwardIfIndex 170 Integer32, 171 ipForwardType 172 INTEGER, 173 ipForwardProto 174 INTEGER, 175 ipForwardAge 176 Integer32, 177 ipForwardInfo 178 OBJECT IDENTIFIER, 180 ipForwardNextHopAS 181 Integer32, 182 ipForwardMetric1 183 Integer32, 184 ipForwardMetric2 185 Integer32, 186 ipForwardMetric3 187 Integer32, 188 ipForwardMetric4 189 Integer32, 190 ipForwardMetric5 191 Integer32 192 } 194 ipForwardDest OBJECT-TYPE 195 SYNTAX IpAddress 196 MAX-ACCESS read-only 197 STATUS obsolete 198 DESCRIPTION 199 "The destination IP address of this route. An 200 entry with a value of 0.0.0.0 is considered a 201 default route. 203 This object may not take a Multicast (Class D) 204 address value. 206 Any assignment (implicit or otherwise) of an 207 instance of this object to a value x must be 208 rejected if the bitwise logical-AND of x with 209 the value of the corresponding instance of the 210 ipForwardMask object is not equal to x." 211 ::= { ipForwardEntry 1 } 213 ipForwardMask OBJECT-TYPE 214 SYNTAX IpAddress 215 MAX-ACCESS read-create 216 STATUS obsolete 217 DESCRIPTION 218 "Indicate the mask to be logical-ANDed with the 219 destination address before being compared to 220 the value in the ipForwardDest field. For 221 those systems that do not support arbitrary 222 subnet masks, an agent constructs the value of 223 the ipForwardMask by reference to the IP Ad- 224 dress Class. 226 Any assignment (implicit or otherwise) of an 227 instance of this object to a value x must be 228 rejected if the bitwise logical-AND of x with 229 the value of the corresponding instance of the 230 ipForwardDest object is not equal to ipForward- 231 Dest." 232 DEFVAL { '00000000'h } -- 0.0.0.0 233 ::= { ipForwardEntry 2 } 235 -- The following convention is included for specification 236 -- of TOS Field contents. At this time, the Host Requirements 237 -- and the Router Requirements documents disagree on the width 238 -- of the TOS field. This mapping describes the Router 239 -- Requirements mapping, and leaves room to widen the TOS field 240 -- without impact to fielded systems. 242 ipForwardPolicy OBJECT-TYPE 243 SYNTAX Integer32 244 MAX-ACCESS read-only 245 STATUS obsolete 246 DESCRIPTION 247 "The general set of conditions that would cause 248 the selection of one multipath route (set of 249 next hops for a given destination) is referred 250 to as 'policy'. 252 Unless the mechanism indicated by ipForwardPro- 253 to specifies otherwise, the policy specifier is 254 the IP TOS Field. The encoding of IP TOS is as 255 specified by the following convention. Zero 256 indicates the default path if no more specific 257 policy applies. 259 +-----+-----+-----+-----+-----+-----+-----+-----+ 260 | | | | 261 | PRECEDENCE | TYPE OF SERVICE | 0 | 262 | | | | 263 +-----+-----+-----+-----+-----+-----+-----+-----+ 265 IP TOS IP TOS 266 Field Policy Field Policy 267 Contents Code Contents Code 268 0 0 0 0 ==> 0 0 0 0 1 ==> 2 269 0 0 1 0 ==> 4 0 0 1 1 ==> 6 270 0 1 0 0 ==> 8 0 1 0 1 ==> 10 271 0 1 1 0 ==> 12 0 1 1 1 ==> 14 272 1 0 0 0 ==> 16 1 0 0 1 ==> 18 273 1 0 1 0 ==> 20 1 0 1 1 ==> 22 274 1 1 0 0 ==> 24 1 1 0 1 ==> 26 275 1 1 1 0 ==> 28 1 1 1 1 ==> 30 277 Protocols defining 'policy' otherwise must ei- 278 ther define a set of values which are valid for 279 this object or must implement an integer- 280 instanced policy table for which this object's 281 value acts as an index." 282 ::= { ipForwardEntry 3 } 284 ipForwardNextHop OBJECT-TYPE 285 SYNTAX IpAddress 286 MAX-ACCESS read-only 287 STATUS obsolete 288 DESCRIPTION 289 "On remote routes, the address of the next sys- 290 tem en route; Otherwise, 0.0.0.0." 291 ::= { ipForwardEntry 4 } 293 ipForwardIfIndex OBJECT-TYPE 294 SYNTAX Integer32 295 MAX-ACCESS read-create 296 STATUS obsolete 297 DESCRIPTION 298 "The ifIndex value which identifies the local 299 interface through which the next hop of this 300 route should be reached." 301 DEFVAL { 0 } 302 ::= { ipForwardEntry 5 } 304 ipForwardType OBJECT-TYPE 305 SYNTAX INTEGER { 306 other (1), -- not specified by this MIB 307 invalid (2), -- logically deleted 308 local (3), -- local interface 309 remote (4) -- remote destination 310 } 311 MAX-ACCESS read-create 312 STATUS obsolete 313 DESCRIPTION 314 "The type of route. Note that local(3) refers 315 to a route for which the next hop is the final 316 destination; remote(4) refers to a route for 317 which the next hop is not the final destina- 318 tion. 320 Setting this object to the value invalid(2) has 321 the effect of invalidating the corresponding 322 entry in the ipForwardTable object. That is, 323 it effectively disassociates the destination 324 identified with said entry from the route iden- 325 tified with said entry. It is an 326 implementation-specific matter as to whether 327 the agent removes an invalidated entry from the 328 table. Accordingly, management stations must 329 be prepared to receive tabular information from 330 agents that corresponds to entries not current- 331 ly in use. Proper interpretation of such en- 332 tries requires examination of the relevant ip- 333 ForwardType object." 334 DEFVAL { invalid } 335 ::= { ipForwardEntry 6 } 337 ipForwardProto OBJECT-TYPE 338 SYNTAX INTEGER { 339 other (1), -- not specified 340 local (2), -- local interface 341 netmgmt (3), -- static route 342 icmp (4), -- result of ICMP Redirect 344 -- the following are all dynamic 345 -- routing protocols 346 egp (5), -- Exterior Gateway Protocol 347 ggp (6), -- Gateway-Gateway Protocol 348 hello (7), -- FuzzBall HelloSpeak 349 rip (8), -- Berkeley RIP or RIP-II 350 is_is (9), -- Dual IS-IS 351 es_is (10), -- ISO 9542 352 ciscoIgrp (11), -- Cisco IGRP 353 bbnSpfIgp (12), -- BBN SPF IGP 354 ospf (13), -- Open Shortest Path First 355 bgp (14), -- Border Gateway Protocol 356 idpr (15) -- InterDomain Policy Routing 357 } 358 MAX-ACCESS read-only 359 STATUS obsolete 360 DESCRIPTION 361 "The routing mechanism via which this route was 362 learned. Inclusion of values for gateway rout- 363 ing protocols is not intended to imply that 364 hosts should support those protocols." 365 ::= { ipForwardEntry 7 } 367 ipForwardAge OBJECT-TYPE 368 SYNTAX Integer32 369 MAX-ACCESS read-only 370 STATUS obsolete 371 DESCRIPTION 372 "The number of seconds since this route was 373 last updated or otherwise determined to be 374 correct. Note that no semantics of `too old' 375 can be implied except through knowledge of the 376 routing protocol by which the route was 377 learned." 378 DEFVAL { 0 } 379 ::= { ipForwardEntry 8 } 381 ipForwardInfo OBJECT-TYPE 382 SYNTAX OBJECT IDENTIFIER 383 MAX-ACCESS read-create 384 STATUS obsolete 385 DESCRIPTION 386 "A reference to MIB definitions specific to the 387 particular routing protocol which is responsi- 388 ble for this route, as determined by the value 389 specified in the route's ipForwardProto value. 390 If this information is not present, its value 391 should be set to the OBJECT IDENTIFIER { 0 0 }, 392 which is a syntactically valid object identif- 393 ier, and any implementation conforming to ASN.1 394 and the Basic Encoding Rules must be able to 395 generate and recognize this value." 396 ::= { ipForwardEntry 9 } 398 ipForwardNextHopAS OBJECT-TYPE 399 SYNTAX Integer32 400 MAX-ACCESS read-create 401 STATUS obsolete 402 DESCRIPTION 403 "The Autonomous System Number of the Next Hop. 404 When this is unknown or not relevant to the 405 protocol indicated by ipForwardProto, zero." 407 DEFVAL { 0 } 408 ::= { ipForwardEntry 10 } 410 ipForwardMetric1 OBJECT-TYPE 411 SYNTAX Integer32 412 MAX-ACCESS read-create 413 STATUS obsolete 414 DESCRIPTION 415 "The primary routing metric for this route. 416 The semantics of this metric are determined by 417 the routing-protocol specified in the route's 418 ipForwardProto value. If this metric is not 419 used, its value should be set to -1." 420 DEFVAL { -1 } 421 ::= { ipForwardEntry 11 } 423 ipForwardMetric2 OBJECT-TYPE 424 SYNTAX Integer32 425 MAX-ACCESS read-create 426 STATUS obsolete 427 DESCRIPTION 428 "An alternate routing metric for this route. 429 The semantics of this metric are determined by 430 the routing-protocol specified in the route's 431 ipForwardProto value. If this metric is not 432 used, its value should be set to -1." 433 DEFVAL { -1 } 434 ::= { ipForwardEntry 12 } 436 ipForwardMetric3 OBJECT-TYPE 437 SYNTAX Integer32 438 MAX-ACCESS read-create 439 STATUS obsolete 440 DESCRIPTION 441 "An alternate routing metric for this route. 442 The semantics of this metric are determined by 443 the routing-protocol specified in the route's 444 ipForwardProto value. If this metric is not 445 used, its value should be set to -1." 446 DEFVAL { -1 } 447 ::= { ipForwardEntry 13 } 449 ipForwardMetric4 OBJECT-TYPE 450 SYNTAX Integer32 451 MAX-ACCESS read-create 452 STATUS obsolete 453 DESCRIPTION 454 "An alternate routing metric for this route. 455 The semantics of this metric are determined by 456 the routing-protocol specified in the route's 457 ipForwardProto value. If this metric is not 458 used, its value should be set to -1." 459 DEFVAL { -1 } 460 ::= { ipForwardEntry 14 } 462 ipForwardMetric5 OBJECT-TYPE 463 SYNTAX Integer32 464 MAX-ACCESS read-create 465 STATUS obsolete 466 DESCRIPTION 467 "An alternate routing metric for this route. 468 The semantics of this metric are determined by 469 the routing-protocol specified in the route's 470 ipForwardProto value. If this metric is not 471 used, its value should be set to -1." 472 DEFVAL { -1 } 473 ::= { ipForwardEntry 15 } 475 ipCidrRouteNumber OBJECT-TYPE 476 SYNTAX Gauge32 477 MAX-ACCESS read-only 478 STATUS current 479 DESCRIPTION 480 "The number of current ipCidrRouteTable entries 481 that are not invalid." 482 ::= { ipForward 3 } 484 -- IP CIDR Route Table 486 -- The IP CIDR Route Table obsoletes and replaces the ipRoute 487 -- Table current in MIB-I and MIB-II and the IP Forwarding Table. 488 -- It adds knowledge of the autonomous system of the next hop, 489 -- multiple next hops, and policy routing, and Classless 490 -- Inter-Domain Routing. 492 ipCidrRouteTable OBJECT-TYPE 493 SYNTAX SEQUENCE OF IpCidrRouteEntry 494 MAX-ACCESS not-accessible 495 STATUS current 496 DESCRIPTION 497 "This entity's IP Routing table." 498 REFERENCE 499 "RFC 1213 Section 6.6, The IP Group" 500 ::= { ipForward 4 } 502 ipCidrRouteEntry OBJECT-TYPE 503 SYNTAX IpCidrRouteEntry 504 MAX-ACCESS not-accessible 505 STATUS current 506 DESCRIPTION 507 "A particular route to a particular destina- 508 tion, under a particular policy." 509 INDEX { 510 ipCidrRouteDest, 511 ipCidrRouteMask, 512 ipCidrRouteTos, 513 ipCidrRouteNextHop 514 } 515 ::= { ipCidrRouteTable 1 } 517 IpCidrRouteEntry ::= 518 SEQUENCE { 519 ipCidrRouteDest 520 IpAddress, 521 ipCidrRouteMask 522 IpAddress, 523 ipCidrRouteTos 524 Integer32, 525 ipCidrRouteNextHop 526 IpAddress, 527 ipCidrRouteIfIndex 528 Integer32, 529 ipCidrRouteType 530 INTEGER, 531 ipCidrRouteProto 532 INTEGER, 533 ipCidrRouteAge 534 Integer32, 535 ipCidrRouteInfo 536 OBJECT IDENTIFIER, 537 ipCidrRouteNextHopAS 538 Integer32, 539 ipCidrRouteMetric1 540 Integer32, 541 ipCidrRouteMetric2 542 Integer32, 543 ipCidrRouteMetric3 544 Integer32, 545 ipCidrRouteMetric4 546 Integer32, 547 ipCidrRouteMetric5 548 Integer32, 549 ipCidrRouteStatus 550 RowStatus 551 } 553 ipCidrRouteDest OBJECT-TYPE 554 SYNTAX IpAddress 555 MAX-ACCESS read-only 556 STATUS current 557 DESCRIPTION 558 "The destination IP address of this route. 560 This object may not take a Multicast (Class D) 561 address value. 563 Any assignment (implicit or otherwise) of an 564 instance of this object to a value x must be 565 rejected if the bitwise logical-AND of x with 566 the value of the corresponding instance of the 567 ipCidrRouteMask object is not equal to x." 568 ::= { ipCidrRouteEntry 1 } 570 ipCidrRouteMask OBJECT-TYPE 571 SYNTAX IpAddress 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "Indicate the mask to be logical-ANDed with the 576 destination address before being compared to 577 the value in the ipCidrRouteDest field. For 578 those systems that do not support arbitrary 579 subnet masks, an agent constructs the value of 580 the ipCidrRouteMask by reference to the IP Ad- 581 dress Class. 583 Any assignment (implicit or otherwise) of an 584 instance of this object to a value x must be 585 rejected if the bitwise logical-AND of x with 586 the value of the corresponding instance of the 587 ipCidrRouteDest object is not equal to ipCidrRoute- 588 Dest." 589 ::= { ipCidrRouteEntry 2 } 591 -- The following convention is included for specification 592 -- of TOS Field contents. At this time, the Host Requirements 593 -- and the Router Requirements documents disagree on the width 594 -- of the TOS field. This mapping describes the Router 595 -- Requirements mapping, and leaves room to widen the TOS field 596 -- without impact to fielded systems. 598 ipCidrRouteTos OBJECT-TYPE 599 SYNTAX Integer32 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "The policy specifier is the IP TOS Field. The encoding 604 of IP TOS is as specified by the following convention. 605 Zero indicates the default path if no more specific 606 policy applies. 608 +-----+-----+-----+-----+-----+-----+-----+-----+ 609 | | | | 610 | PRECEDENCE | TYPE OF SERVICE | 0 | 611 | | | | 612 +-----+-----+-----+-----+-----+-----+-----+-----+ 614 IP TOS IP TOS 615 Field Policy Field Policy 616 Contents Code Contents Code 617 0 0 0 0 ==> 0 0 0 0 1 ==> 2 618 0 0 1 0 ==> 4 0 0 1 1 ==> 6 619 0 1 0 0 ==> 8 0 1 0 1 ==> 10 620 0 1 1 0 ==> 12 0 1 1 1 ==> 14 621 1 0 0 0 ==> 16 1 0 0 1 ==> 18 622 1 0 1 0 ==> 20 1 0 1 1 ==> 22 623 1 1 0 0 ==> 24 1 1 0 1 ==> 26 624 1 1 1 0 ==> 28 1 1 1 1 ==> 30" 625 ::= { ipCidrRouteEntry 3 } 627 ipCidrRouteNextHop OBJECT-TYPE 628 SYNTAX IpAddress 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "On remote routes, the address of the next sys- 633 tem en route; Otherwise, 0.0.0.0." 634 ::= { ipCidrRouteEntry 4 } 636 ipCidrRouteIfIndex OBJECT-TYPE 637 SYNTAX Integer32 638 MAX-ACCESS read-create 639 STATUS current 640 DESCRIPTION 641 "The ifIndex value which identifies the local 642 interface through which the next hop of this 643 route should be reached." 644 DEFVAL { 0 } 645 ::= { ipCidrRouteEntry 5 } 647 ipCidrRouteType OBJECT-TYPE 648 SYNTAX INTEGER { 649 other (1), -- not specified by this MIB 650 local (2), -- local interface 651 remote (3), -- remote destination 652 reject (4) -- route which discards traffic 653 } 654 MAX-ACCESS read-create 655 STATUS current 656 DESCRIPTION 657 "The type of route. Note that local(3) refers 658 to a route for which the next hop is the final 659 destination; remote(4) refers to a route for 660 which the next hop is not the final destina- 661 tion. 663 Routes which do not result in traffic forwarding or 664 rejection should not be displayed even if the 665 implementation keeps them stored internally. 667 reject refers to a route which, if matched, discards 668 the message as unreachable. This is used in some 669 protocols as a means of correctly aggregating routes." 670 ::= { ipCidrRouteEntry 6 } 672 ipCidrRouteProto OBJECT-TYPE 673 SYNTAX INTEGER { 674 other (1), -- not specified 675 local (2), -- local interface 676 netmgmt (3), -- static route 677 icmp (4), -- result of ICMP Redirect 679 -- the following are all dynamic 680 -- routing protocols 681 egp (5), -- Exterior Gateway Protocol 682 ggp (6), -- Gateway-Gateway Protocol 683 hello (7), -- FuzzBall HelloSpeak 684 rip (8), -- Berkeley RIP or RIP-II 685 is_is (9), -- Dual IS-IS 686 es_is (10), -- ISO 9542 687 ciscoIgrp (11), -- Cisco IGRP 688 bbnSpfIgp (12), -- BBN SPF IGP 689 ospf (13), -- Open Shortest Path First 690 bgp (14), -- Border Gateway Protocol 691 idpr (15) -- InterDomain Policy Routing 692 } 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "The routing mechanism via which this route was 697 learned. Inclusion of values for gateway rout- 698 ing protocols is not intended to imply that 699 hosts should support those protocols." 701 ::= { ipCidrRouteEntry 7 } 703 ipCidrRouteAge OBJECT-TYPE 704 SYNTAX Integer32 705 MAX-ACCESS read-only 706 STATUS current 707 DESCRIPTION 708 "The number of seconds since this route was 709 last updated or otherwise determined to be 710 correct. Note that no semantics of `too old' 711 can be implied except through knowledge of the 712 routing protocol by which the route was 713 learned." 714 DEFVAL { 0 } 715 ::= { ipCidrRouteEntry 8 } 717 ipCidrRouteInfo OBJECT-TYPE 718 SYNTAX OBJECT IDENTIFIER 719 MAX-ACCESS read-create 720 STATUS current 721 DESCRIPTION 722 "A reference to MIB definitions specific to the 723 particular routing protocol which is responsi- 724 ble for this route, as determined by the value 725 specified in the route's ipCidrRouteProto value. 726 If this information is not present, its value 727 should be set to the OBJECT IDENTIFIER { 0 0 }, 728 which is a syntactically valid object identif- 729 ier, and any implementation conforming to ASN.1 730 and the Basic Encoding Rules must be able to 731 generate and recognize this value." 732 ::= { ipCidrRouteEntry 9 } 734 ipCidrRouteNextHopAS OBJECT-TYPE 735 SYNTAX Integer32 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "The Autonomous System Number of the Next Hop. 740 When this is unknown or not relevant to the 741 protocol indicated by ipCidrRouteProto, zero." 742 DEFVAL { 0 } 743 ::= { ipCidrRouteEntry 10 } 745 ipCidrRouteMetric1 OBJECT-TYPE 746 SYNTAX Integer32 747 MAX-ACCESS read-create 748 STATUS current 749 DESCRIPTION 750 "The primary routing metric for this route. 751 The semantics of this metric are determined by 752 the routing-protocol specified in the route's 753 ipCidrRouteProto value. If this metric is not 754 used, its value should be set to -1." 755 DEFVAL { -1 } 756 ::= { ipCidrRouteEntry 11 } 758 ipCidrRouteMetric2 OBJECT-TYPE 759 SYNTAX Integer32 760 MAX-ACCESS read-create 761 STATUS current 762 DESCRIPTION 763 "An alternate routing metric for this route. 764 The semantics of this metric are determined by 765 the routing-protocol specified in the route's 766 ipCidrRouteProto value. If this metric is not 767 used, its value should be set to -1." 768 DEFVAL { -1 } 769 ::= { ipCidrRouteEntry 12 } 771 ipCidrRouteMetric3 OBJECT-TYPE 772 SYNTAX Integer32 773 MAX-ACCESS read-create 774 STATUS current 775 DESCRIPTION 776 "An alternate routing metric for this route. 777 The semantics of this metric are determined by 778 the routing-protocol specified in the route's 779 ipCidrRouteProto value. If this metric is not 780 used, its value should be set to -1." 781 DEFVAL { -1 } 782 ::= { ipCidrRouteEntry 13 } 784 ipCidrRouteMetric4 OBJECT-TYPE 785 SYNTAX Integer32 786 MAX-ACCESS read-create 787 STATUS current 788 DESCRIPTION 789 "An alternate routing metric for this route. 790 The semantics of this metric are determined by 791 the routing-protocol specified in the route's 792 ipCidrRouteProto value. If this metric is not 793 used, its value should be set to -1." 794 DEFVAL { -1 } 795 ::= { ipCidrRouteEntry 14 } 797 ipCidrRouteMetric5 OBJECT-TYPE 798 SYNTAX Integer32 799 MAX-ACCESS read-create 800 STATUS current 801 DESCRIPTION 802 "An alternate routing metric for this route. 803 The semantics of this metric are determined by 804 the routing-protocol specified in the route's 805 ipCidrRouteProto value. If this metric is not 806 used, its value should be set to -1." 807 DEFVAL { -1 } 808 ::= { ipCidrRouteEntry 15 } 810 ipCidrRouteStatus OBJECT-TYPE 811 SYNTAX RowStatus 812 MAX-ACCESS read-create 813 STATUS current 814 DESCRIPTION 815 "The row status variable, used according to 816 row installation and removal conventions." 817 ::= { ipCidrRouteEntry 16 } 819 -- conformance information 821 ipForwardConformance OBJECT IDENTIFIER ::= { ipForward 5 } 823 ipForwardGroups OBJECT IDENTIFIER ::= { ipForwardConformance 1 } 824 ipForwardCompliances OBJECT IDENTIFIER ::= { ipForwardConformance 2 } 826 -- compliance statements 828 ipForwardCompliance MODULE-COMPLIANCE 829 STATUS current 830 DESCRIPTION 831 "The compliance statement for SNMPv2 entities 832 which implement the ipForward MIB." 834 MODULE -- this module 835 MANDATORY-GROUPS { ipForwardCidrRouteGroup } 837 ::= { ipForwardCompliances 1 } 839 -- units of conformance 841 ipForwardMultiPathGroup OBJECT-GROUP 842 OBJECTS { ipForwardNumber, 843 ipForwardDest, ipForwardMask, ipForwardPolicy, 844 ipForwardNextHop, ipForwardIfIndex, ipForwardType, 845 ipForwardProto, ipForwardAge, ipForwardInfo, 846 ipForwardNextHopAS, 847 ipForwardMetric1, ipForwardMetric2, ipForwardMetric3, 848 ipForwardMetric4, ipForwardMetric5 849 } 850 STATUS obsolete 851 DESCRIPTION 852 "IP Multipath Route Table." 853 ::= { ipForwardGroups 2 } 855 ipForwardCidrRouteGroup OBJECT-GROUP 856 OBJECTS { ipCidrRouteNumber, 857 ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, 858 ipCidrRouteNextHop, ipCidrRouteIfIndex, ipCidrRouteType, 859 ipCidrRouteProto, ipCidrRouteAge, ipCidrRouteInfo, 860 ipCidrRouteNextHopAS, ipCidrRouteMetric1, 861 ipCidrRouteMetric2, ipCidrRouteMetric3, 862 ipCidrRouteMetric4, ipCidrRouteMetric5, ipCidrRouteStatus 863 } 864 STATUS current 865 DESCRIPTION 866 "The CIDR Route Table." 867 ::= { ipForwardGroups 3 } 869 END 870 5. Acknowledgements 872 This work was originally performed by the Router Requirements 873 Working Group at the request of the OSPF Working Group. This 874 update was performed under the auspices of the OSPF Working 875 Group. John Moy of Proteon Incorporated is the chair. 877 6. References 879 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 880 "Structure of Management Information for version 2 of the 881 Simple Network Management Protocol (SNMPv2)", RFC 1442, 882 SNMP Research, Inc., Hughes LAN Systems, Dover Beach 883 Consulting, Inc., Carnegie Mellon University, April 1993. 885 [2] Galvin, J., and K. McCloghrie, "Administrative Model for 886 version 2 of the Simple Network Management Protocol 887 (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes 888 LAN Systems, April 1993. 890 [3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 891 "Protocol Operations for version 2 of the Simple Network 892 Management Protocol (SNMPv2)", RFC 1448, SNMP Research, 893 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., 894 Carnegie Mellon University, April 1993. 896 [4] McCloghrie, K., and M. Rose, "Management Information Base 897 for Network Management of TCP/IP-based internets - MIB- 898 II", STD 17, RFC 1213, Hughes LAN Systems, Performance 899 Systems International, March 1991. 901 [5] Postel, J., "Internet Protocol", STD 5, RFC 791, 902 USC/Information Sciences Institute, September 1981. 904 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 905 "Textual Conventions for version 2 of the Simple Network 906 Management Protocol (SNMPv2)", RFC 1443, SNMP Research, 907 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., 908 Carnegie Mellon University, April 1993. 910 [7] Fred Baker, "IP Forwarding Table MIB", Request for 911 Comments 1354, (July 1992). 913 7. Security Considerations 915 Security is an objective not in this MIB view. 917 8. Author's Address 919 Fred Baker 920 Cisco Systems 921 519 Lado Drive 922 Santa Barbara, California 93111 924 Phone: +1 805 681 0115 925 Email: fred@cisco.com 927 Table of Contents 929 1 Introduction .......................................... 2 930 2 The SNMPv2 Network Management Framework ............... 3 931 2.1 Object Definitions .................................. 3 932 3 Overview .............................................. 4 933 4 Definitions ........................................... 5 934 5 Acknowledgements ...................................... 24 935 6 References ............................................ 25 936 7 Security Considerations ............................... 26 937 8 Author's Address ...................................... 26 939 IP Forwarding Table MIB 941 Fri Mar 17 12:32:57 PST 1995 942 draft-ietf-ospf-cidr-route-mib-04.txt 944 Fred Baker 945 Cisco Systems 946 fred@cisco.com 948 Status of this Memo 950 This document is an Internet Draft. Internet Drafts are 951 working documents of the Internet Engineering Task Force 952 (IETF), its Areas, and its Working Groups. Note that other 953 groups may also distribute working documents as Internet 954 Drafts. 956 Internet Drafts are valid for a maximum of six months and may 957 be updated, replaced, or obsoleted by other documents at any 958 time. It is inappropriate to use Internet Drafts as reference 959 material or to cite them other than as a "work in progress". 961 9. Introduction 963 This memo defines an update to RFC 1354, "IP Forwarding Table 964 MIB", for Classless Inter-Domain Routing (CIDR). That 965 document was developed by the Router Requirements Working 966 Group as an update to RFC 1213's ipRouteTable, with the 967 display of multiple routes as a primary objective. The 968 significant difference between this MIB and RFC 1354 is the 969 recognition (explicitly discussed but by consensus left to 970 future work) that CIDR routes may have the same network number 971 but different network masks. 973 10. The SNMPv2 Network Management Framework 975 The SNMPv2 Network Management Framework consists of four major 976 components. They are: 978 o RFC 1441 which defines the SMI, the mechanisms used for 979 describing and naming objects for the purpose of 980 management. 982 o RFC 1213 defines MIB-II, the core set of managed objects 983 for the Internet suite of protocols. 985 o RFC 1445 which defines the administrative and other 986 architectural aspects of the framework. 988 o RFC 1448 which defines the protocol used for network 989 access to managed objects. 991 The Framework permits new objects to be defined for the 992 purpose of experimentation and evaluation. 994 10.1. Object Definitions 996 Managed objects are accessed via a virtual information store, 997 termed the Management Information Base or MIB. Objects in the 998 MIB are defined using the subset of Abstract Syntax Notation 999 One (ASN.1) defined in the SMI. In particular, each object 1000 object type is named by an OBJECT IDENTIFIER, an 1001 administratively assigned name. The object type together with 1002 an object instance serves to uniquely identify a specific 1003 instantiation of the object. For human convenience, we often 1004 use a textual string, termed the descriptor, to refer to the 1005 object type. 1007 11. Overview 1009 The MIB consists of two tables and two global objects. 1011 (1) The object ipForwardNumber indicates the number of 1012 current routes. This is primarily to avoid having to 1013 read the table in order to determine this number. 1015 (2) The ipForwardTable updates the RFC 1213 ipRouteTable to 1016 display multipath IP Routes. This is in turn obsoleted 1017 by the ipCidrRouteTable. 1019 (3) The ipCidrRouteTable updates the RFC 1213 ipRouteTable to 1020 display multipath IP Routes having the same network 1021 number but differing network masks. 1023 12. Definitions 1025 IP-FORWARD-MIB DEFINITIONS ::= BEGIN 1027 IMPORTS 1028 MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Integer32, Gauge32 1029 FROM SNMPv2-SMI 1030 RowStatus 1031 FROM SNMPv2-TC 1032 ip 1033 FROM RFC1213-MIB 1034 MODULE-COMPLIANCE, OBJECT-GROUP 1035 FROM SNMPv2-CONF; 1037 ipForward MODULE-IDENTITY 1038 LAST-UPDATED "9402220000Z" -- Fri Mar 17 12:32:57 PST 1995 1039 ORGANIZATION "IETF OSPF Working Group" 1040 CONTACT-INFO 1041 " Fred Baker 1042 Postal: Cisco Systems 1043 519 Lado Drive 1044 Santa Barbara, California 93111 1046 Phone: +1 805 681 0115 1047 Email: fred@cisco.com 1048 " 1049 DESCRIPTION 1050 "The MIB module for the display of CIDR multipath IP Routes." 1051 ::= { ip 24 } 1053 ipForwardNumber OBJECT-TYPE 1054 SYNTAX Gauge32 1055 MAX-ACCESS read-only 1056 STATUS obsolete 1057 DESCRIPTION 1058 "The number of current ipForwardTable entries 1059 that are not invalid." 1060 ::= { ipForward 1 } 1062 -- IP Forwarding Table 1064 -- The IP Forwarding Table obsoletes and replaces the ipRoute 1065 -- Table current in MIB-I and MIB-II. It adds knowledge of 1066 -- the autonomous system of the next hop, multiple next hop 1067 -- support, and policy routing support. 1069 ipForwardTable OBJECT-TYPE 1070 SYNTAX SEQUENCE OF IpForwardEntry 1071 MAX-ACCESS not-accessible 1072 STATUS obsolete 1073 DESCRIPTION 1074 "This entity's IP Routing table." 1075 REFERENCE 1076 "RFC 1213 Section 6.6, The IP Group" 1077 ::= { ipForward 2 } 1079 ipForwardEntry OBJECT-TYPE 1080 SYNTAX IpForwardEntry 1081 MAX-ACCESS not-accessible 1082 STATUS obsolete 1083 DESCRIPTION 1084 "A particular route to a particular destina- 1085 tion, under a particular policy." 1086 INDEX { 1087 ipForwardDest, 1088 ipForwardProto, 1089 ipForwardPolicy, 1090 ipForwardNextHop 1091 } 1092 ::= { ipForwardTable 1 } 1094 IpForwardEntry ::= 1095 SEQUENCE { 1096 ipForwardDest 1097 IpAddress, 1098 ipForwardMask 1099 IpAddress, 1100 ipForwardPolicy 1101 Integer32, 1102 ipForwardNextHop 1103 IpAddress, 1104 ipForwardIfIndex 1105 Integer32, 1106 ipForwardType 1107 INTEGER, 1108 ipForwardProto 1109 INTEGER, 1110 ipForwardAge 1111 Integer32, 1112 ipForwardInfo 1113 OBJECT IDENTIFIER, 1115 ipForwardNextHopAS 1116 Integer32, 1117 ipForwardMetric1 1118 Integer32, 1119 ipForwardMetric2 1120 Integer32, 1121 ipForwardMetric3 1122 Integer32, 1123 ipForwardMetric4 1124 Integer32, 1125 ipForwardMetric5 1126 Integer32 1127 } 1129 ipForwardDest OBJECT-TYPE 1130 SYNTAX IpAddress 1131 MAX-ACCESS read-only 1132 STATUS obsolete 1133 DESCRIPTION 1134 "The destination IP address of this route. An 1135 entry with a value of 0.0.0.0 is considered a 1136 default route. 1138 This object may not take a Multicast (Class D) 1139 address value. 1141 Any assignment (implicit or otherwise) of an 1142 instance of this object to a value x must be 1143 rejected if the bitwise logical-AND of x with 1144 the value of the corresponding instance of the 1145 ipForwardMask object is not equal to x." 1146 ::= { ipForwardEntry 1 } 1148 ipForwardMask OBJECT-TYPE 1149 SYNTAX IpAddress 1150 MAX-ACCESS read-create 1151 STATUS obsolete 1152 DESCRIPTION 1153 "Indicate the mask to be logical-ANDed with the 1154 destination address before being compared to 1155 the value in the ipForwardDest field. For 1156 those systems that do not support arbitrary 1157 subnet masks, an agent constructs the value of 1158 the ipForwardMask by reference to the IP Ad- 1159 dress Class. 1161 Any assignment (implicit or otherwise) of an 1162 instance of this object to a value x must be 1163 rejected if the bitwise logical-AND of x with 1164 the value of the corresponding instance of the 1165 ipForwardDest object is not equal to ipForward- 1166 Dest." 1167 DEFVAL { '00000000'h } -- 0.0.0.0 1168 ::= { ipForwardEntry 2 } 1170 -- The following convention is included for specification 1171 -- of TOS Field contents. At this time, the Host Requirements 1172 -- and the Router Requirements documents disagree on the width 1173 -- of the TOS field. This mapping describes the Router 1174 -- Requirements mapping, and leaves room to widen the TOS field 1175 -- without impact to fielded systems. 1177 ipForwardPolicy OBJECT-TYPE 1178 SYNTAX Integer32 1179 MAX-ACCESS read-only 1180 STATUS obsolete 1181 DESCRIPTION 1182 "The general set of conditions that would cause 1183 the selection of one multipath route (set of 1184 next hops for a given destination) is referred 1185 to as 'policy'. 1187 Unless the mechanism indicated by ipForwardPro- 1188 to specifies otherwise, the policy specifier is 1189 the IP TOS Field. The encoding of IP TOS is as 1190 specified by the following convention. Zero 1191 indicates the default path if no more specific 1192 policy applies. 1194 +-----+-----+-----+-----+-----+-----+-----+-----+ 1195 | | | | 1196 | PRECEDENCE | TYPE OF SERVICE | 0 | 1197 | | | | 1198 +-----+-----+-----+-----+-----+-----+-----+-----+ 1200 IP TOS IP TOS 1201 Field Policy Field Policy 1202 Contents Code Contents Code 1203 0 0 0 0 ==> 0 0 0 0 1 ==> 2 1204 0 0 1 0 ==> 4 0 0 1 1 ==> 6 1205 0 1 0 0 ==> 8 0 1 0 1 ==> 10 1206 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1207 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1208 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1209 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1210 1 1 1 0 ==> 28 1 1 1 1 ==> 30 1212 Protocols defining 'policy' otherwise must ei- 1213 ther define a set of values which are valid for 1214 this object or must implement an integer- 1215 instanced policy table for which this object's 1216 value acts as an index." 1217 ::= { ipForwardEntry 3 } 1219 ipForwardNextHop OBJECT-TYPE 1220 SYNTAX IpAddress 1221 MAX-ACCESS read-only 1222 STATUS obsolete 1223 DESCRIPTION 1224 "On remote routes, the address of the next sys- 1225 tem en route; Otherwise, 0.0.0.0." 1226 ::= { ipForwardEntry 4 } 1228 ipForwardIfIndex OBJECT-TYPE 1229 SYNTAX Integer32 1230 MAX-ACCESS read-create 1231 STATUS obsolete 1232 DESCRIPTION 1233 "The ifIndex value which identifies the local 1234 interface through which the next hop of this 1235 route should be reached." 1236 DEFVAL { 0 } 1237 ::= { ipForwardEntry 5 } 1239 ipForwardType OBJECT-TYPE 1240 SYNTAX INTEGER { 1241 other (1), -- not specified by this MIB 1242 invalid (2), -- logically deleted 1243 local (3), -- local interface 1244 remote (4) -- remote destination 1245 } 1246 MAX-ACCESS read-create 1247 STATUS obsolete 1248 DESCRIPTION 1249 "The type of route. Note that local(3) refers 1250 to a route for which the next hop is the final 1251 destination; remote(4) refers to a route for 1252 which the next hop is not the final destina- 1253 tion. 1255 Setting this object to the value invalid(2) has 1256 the effect of invalidating the corresponding 1257 entry in the ipForwardTable object. That is, 1258 it effectively disassociates the destination 1259 identified with said entry from the route iden- 1260 tified with said entry. It is an 1261 implementation-specific matter as to whether 1262 the agent removes an invalidated entry from the 1263 table. Accordingly, management stations must 1264 be prepared to receive tabular information from 1265 agents that corresponds to entries not current- 1266 ly in use. Proper interpretation of such en- 1267 tries requires examination of the relevant ip- 1268 ForwardType object." 1269 DEFVAL { invalid } 1270 ::= { ipForwardEntry 6 } 1272 ipForwardProto OBJECT-TYPE 1273 SYNTAX INTEGER { 1274 other (1), -- not specified 1275 local (2), -- local interface 1276 netmgmt (3), -- static route 1277 icmp (4), -- result of ICMP Redirect 1279 -- the following are all dynamic 1280 -- routing protocols 1281 egp (5), -- Exterior Gateway Protocol 1282 ggp (6), -- Gateway-Gateway Protocol 1283 hello (7), -- FuzzBall HelloSpeak 1284 rip (8), -- Berkeley RIP or RIP-II 1285 is_is (9), -- Dual IS-IS 1286 es_is (10), -- ISO 9542 1287 ciscoIgrp (11), -- Cisco IGRP 1288 bbnSpfIgp (12), -- BBN SPF IGP 1289 ospf (13), -- Open Shortest Path First 1290 bgp (14), -- Border Gateway Protocol 1291 idpr (15) -- InterDomain Policy Routing 1292 } 1293 MAX-ACCESS read-only 1294 STATUS obsolete 1295 DESCRIPTION 1296 "The routing mechanism via which this route was 1297 learned. Inclusion of values for gateway rout- 1298 ing protocols is not intended to imply that 1299 hosts should support those protocols." 1300 ::= { ipForwardEntry 7 } 1302 ipForwardAge OBJECT-TYPE 1303 SYNTAX Integer32 1304 MAX-ACCESS read-only 1305 STATUS obsolete 1306 DESCRIPTION 1307 "The number of seconds since this route was 1308 last updated or otherwise determined to be 1309 correct. Note that no semantics of `too old' 1310 can be implied except through knowledge of the 1311 routing protocol by which the route was 1312 learned." 1313 DEFVAL { 0 } 1314 ::= { ipForwardEntry 8 } 1316 ipForwardInfo OBJECT-TYPE 1317 SYNTAX OBJECT IDENTIFIER 1318 MAX-ACCESS read-create 1319 STATUS obsolete 1320 DESCRIPTION 1321 "A reference to MIB definitions specific to the 1322 particular routing protocol which is responsi- 1323 ble for this route, as determined by the value 1324 specified in the route's ipForwardProto value. 1325 If this information is not present, its value 1326 should be set to the OBJECT IDENTIFIER { 0 0 }, 1327 which is a syntactically valid object identif- 1328 ier, and any implementation conforming to ASN.1 1329 and the Basic Encoding Rules must be able to 1330 generate and recognize this value." 1331 ::= { ipForwardEntry 9 } 1333 ipForwardNextHopAS OBJECT-TYPE 1334 SYNTAX Integer32 1335 MAX-ACCESS read-create 1336 STATUS obsolete 1337 DESCRIPTION 1338 "The Autonomous System Number of the Next Hop. 1339 When this is unknown or not relevant to the 1340 protocol indicated by ipForwardProto, zero." 1342 DEFVAL { 0 } 1343 ::= { ipForwardEntry 10 } 1345 ipForwardMetric1 OBJECT-TYPE 1346 SYNTAX Integer32 1347 MAX-ACCESS read-create 1348 STATUS obsolete 1349 DESCRIPTION 1350 "The primary routing metric for this route. 1351 The semantics of this metric are determined by 1352 the routing-protocol specified in the route's 1353 ipForwardProto value. If this metric is not 1354 used, its value should be set to -1." 1355 DEFVAL { -1 } 1356 ::= { ipForwardEntry 11 } 1358 ipForwardMetric2 OBJECT-TYPE 1359 SYNTAX Integer32 1360 MAX-ACCESS read-create 1361 STATUS obsolete 1362 DESCRIPTION 1363 "An alternate routing metric for this route. 1364 The semantics of this metric are determined by 1365 the routing-protocol specified in the route's 1366 ipForwardProto value. If this metric is not 1367 used, its value should be set to -1." 1368 DEFVAL { -1 } 1369 ::= { ipForwardEntry 12 } 1371 ipForwardMetric3 OBJECT-TYPE 1372 SYNTAX Integer32 1373 MAX-ACCESS read-create 1374 STATUS obsolete 1375 DESCRIPTION 1376 "An alternate routing metric for this route. 1377 The semantics of this metric are determined by 1378 the routing-protocol specified in the route's 1379 ipForwardProto value. If this metric is not 1380 used, its value should be set to -1." 1381 DEFVAL { -1 } 1382 ::= { ipForwardEntry 13 } 1384 ipForwardMetric4 OBJECT-TYPE 1385 SYNTAX Integer32 1386 MAX-ACCESS read-create 1387 STATUS obsolete 1388 DESCRIPTION 1389 "An alternate routing metric for this route. 1390 The semantics of this metric are determined by 1391 the routing-protocol specified in the route's 1392 ipForwardProto value. If this metric is not 1393 used, its value should be set to -1." 1394 DEFVAL { -1 } 1395 ::= { ipForwardEntry 14 } 1397 ipForwardMetric5 OBJECT-TYPE 1398 SYNTAX Integer32 1399 MAX-ACCESS read-create 1400 STATUS obsolete 1401 DESCRIPTION 1402 "An alternate routing metric for this route. 1403 The semantics of this metric are determined by 1404 the routing-protocol specified in the route's 1405 ipForwardProto value. If this metric is not 1406 used, its value should be set to -1." 1407 DEFVAL { -1 } 1408 ::= { ipForwardEntry 15 } 1410 ipCidrRouteNumber OBJECT-TYPE 1411 SYNTAX Gauge32 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The number of current ipCidrRouteTable entries 1416 that are not invalid." 1417 ::= { ipForward 3 } 1419 -- IP CIDR Route Table 1421 -- The IP CIDR Route Table obsoletes and replaces the ipRoute 1422 -- Table current in MIB-I and MIB-II and the IP Forwarding Table. 1423 -- It adds knowledge of the autonomous system of the next hop, 1424 -- multiple next hops, and policy routing, and Classless 1425 -- Inter-Domain Routing. 1427 ipCidrRouteTable OBJECT-TYPE 1428 SYNTAX SEQUENCE OF IpCidrRouteEntry 1429 MAX-ACCESS not-accessible 1430 STATUS current 1431 DESCRIPTION 1432 "This entity's IP Routing table." 1433 REFERENCE 1434 "RFC 1213 Section 6.6, The IP Group" 1435 ::= { ipForward 4 } 1437 ipCidrRouteEntry OBJECT-TYPE 1438 SYNTAX IpCidrRouteEntry 1439 MAX-ACCESS not-accessible 1440 STATUS current 1441 DESCRIPTION 1442 "A particular route to a particular destina- 1443 tion, under a particular policy." 1444 INDEX { 1445 ipCidrRouteDest, 1446 ipCidrRouteMask, 1447 ipCidrRouteTos, 1448 ipCidrRouteNextHop 1449 } 1450 ::= { ipCidrRouteTable 1 } 1452 IpCidrRouteEntry ::= 1453 SEQUENCE { 1454 ipCidrRouteDest 1455 IpAddress, 1456 ipCidrRouteMask 1457 IpAddress, 1458 ipCidrRouteTos 1459 Integer32, 1460 ipCidrRouteNextHop 1461 IpAddress, 1462 ipCidrRouteIfIndex 1463 Integer32, 1464 ipCidrRouteType 1465 INTEGER, 1466 ipCidrRouteProto 1467 INTEGER, 1468 ipCidrRouteAge 1469 Integer32, 1470 ipCidrRouteInfo 1471 OBJECT IDENTIFIER, 1472 ipCidrRouteNextHopAS 1473 Integer32, 1474 ipCidrRouteMetric1 1475 Integer32, 1476 ipCidrRouteMetric2 1477 Integer32, 1478 ipCidrRouteMetric3 1479 Integer32, 1480 ipCidrRouteMetric4 1481 Integer32, 1482 ipCidrRouteMetric5 1483 Integer32, 1484 ipCidrRouteStatus 1485 RowStatus 1486 } 1488 ipCidrRouteDest OBJECT-TYPE 1489 SYNTAX IpAddress 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "The destination IP address of this route. 1495 This object may not take a Multicast (Class D) 1496 address value. 1498 Any assignment (implicit or otherwise) of an 1499 instance of this object to a value x must be 1500 rejected if the bitwise logical-AND of x with 1501 the value of the corresponding instance of the 1502 ipCidrRouteMask object is not equal to x." 1503 ::= { ipCidrRouteEntry 1 } 1505 ipCidrRouteMask OBJECT-TYPE 1506 SYNTAX IpAddress 1507 MAX-ACCESS read-only 1508 STATUS current 1509 DESCRIPTION 1510 "Indicate the mask to be logical-ANDed with the 1511 destination address before being compared to 1512 the value in the ipCidrRouteDest field. For 1513 those systems that do not support arbitrary 1514 subnet masks, an agent constructs the value of 1515 the ipCidrRouteMask by reference to the IP Ad- 1516 dress Class. 1518 Any assignment (implicit or otherwise) of an 1519 instance of this object to a value x must be 1520 rejected if the bitwise logical-AND of x with 1521 the value of the corresponding instance of the 1522 ipCidrRouteDest object is not equal to ipCidrRoute- 1523 Dest." 1524 ::= { ipCidrRouteEntry 2 } 1526 -- The following convention is included for specification 1527 -- of TOS Field contents. At this time, the Host Requirements 1528 -- and the Router Requirements documents disagree on the width 1529 -- of the TOS field. This mapping describes the Router 1530 -- Requirements mapping, and leaves room to widen the TOS field 1531 -- without impact to fielded systems. 1533 ipCidrRouteTos OBJECT-TYPE 1534 SYNTAX Integer32 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "The policy specifier is the IP TOS Field. The encoding 1539 of IP TOS is as specified by the following convention. 1540 Zero indicates the default path if no more specific 1541 policy applies. 1543 +-----+-----+-----+-----+-----+-----+-----+-----+ 1544 | | | | 1545 | PRECEDENCE | TYPE OF SERVICE | 0 | 1546 | | | | 1547 +-----+-----+-----+-----+-----+-----+-----+-----+ 1549 IP TOS IP TOS 1550 Field Policy Field Policy 1551 Contents Code Contents Code 1552 0 0 0 0 ==> 0 0 0 0 1 ==> 2 1553 0 0 1 0 ==> 4 0 0 1 1 ==> 6 1554 0 1 0 0 ==> 8 0 1 0 1 ==> 10 1555 0 1 1 0 ==> 12 0 1 1 1 ==> 14 1556 1 0 0 0 ==> 16 1 0 0 1 ==> 18 1557 1 0 1 0 ==> 20 1 0 1 1 ==> 22 1558 1 1 0 0 ==> 24 1 1 0 1 ==> 26 1559 1 1 1 0 ==> 28 1 1 1 1 ==> 30" 1560 ::= { ipCidrRouteEntry 3 } 1562 ipCidrRouteNextHop OBJECT-TYPE 1563 SYNTAX IpAddress 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1567 "On remote routes, the address of the next sys- 1568 tem en route; Otherwise, 0.0.0.0." 1569 ::= { ipCidrRouteEntry 4 } 1571 ipCidrRouteIfIndex OBJECT-TYPE 1572 SYNTAX Integer32 1573 MAX-ACCESS read-create 1574 STATUS current 1575 DESCRIPTION 1576 "The ifIndex value which identifies the local 1577 interface through which the next hop of this 1578 route should be reached." 1579 DEFVAL { 0 } 1580 ::= { ipCidrRouteEntry 5 } 1582 ipCidrRouteType OBJECT-TYPE 1583 SYNTAX INTEGER { 1584 other (1), -- not specified by this MIB 1585 local (2), -- local interface 1586 remote (3), -- remote destination 1587 reject (4) -- route which discards traffic 1588 } 1589 MAX-ACCESS read-create 1590 STATUS current 1591 DESCRIPTION 1592 "The type of route. Note that local(3) refers 1593 to a route for which the next hop is the final 1594 destination; remote(4) refers to a route for 1595 which the next hop is not the final destina- 1596 tion. 1598 Routes which do not result in traffic forwarding or 1599 rejection should not be displayed even if the 1600 implementation keeps them stored internally. 1602 reject refers to a route which, if matched, discards 1603 the message as unreachable. This is used in some 1604 protocols as a means of correctly aggregating routes." 1605 ::= { ipCidrRouteEntry 6 } 1607 ipCidrRouteProto OBJECT-TYPE 1608 SYNTAX INTEGER { 1609 other (1), -- not specified 1610 local (2), -- local interface 1611 netmgmt (3), -- static route 1612 icmp (4), -- result of ICMP Redirect 1614 -- the following are all dynamic 1615 -- routing protocols 1616 egp (5), -- Exterior Gateway Protocol 1617 ggp (6), -- Gateway-Gateway Protocol 1618 hello (7), -- FuzzBall HelloSpeak 1619 rip (8), -- Berkeley RIP or RIP-II 1620 is_is (9), -- Dual IS-IS 1621 es_is (10), -- ISO 9542 1622 ciscoIgrp (11), -- Cisco IGRP 1623 bbnSpfIgp (12), -- BBN SPF IGP 1624 ospf (13), -- Open Shortest Path First 1625 bgp (14), -- Border Gateway Protocol 1626 idpr (15) -- InterDomain Policy Routing 1627 } 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "The routing mechanism via which this route was 1632 learned. Inclusion of values for gateway rout- 1633 ing protocols is not intended to imply that 1634 hosts should support those protocols." 1636 ::= { ipCidrRouteEntry 7 } 1638 ipCidrRouteAge OBJECT-TYPE 1639 SYNTAX Integer32 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "The number of seconds since this route was 1644 last updated or otherwise determined to be 1645 correct. Note that no semantics of `too old' 1646 can be implied except through knowledge of the 1647 routing protocol by which the route was 1648 learned." 1649 DEFVAL { 0 } 1650 ::= { ipCidrRouteEntry 8 } 1652 ipCidrRouteInfo OBJECT-TYPE 1653 SYNTAX OBJECT IDENTIFIER 1654 MAX-ACCESS read-create 1655 STATUS current 1656 DESCRIPTION 1657 "A reference to MIB definitions specific to the 1658 particular routing protocol which is responsi- 1659 ble for this route, as determined by the value 1660 specified in the route's ipCidrRouteProto value. 1661 If this information is not present, its value 1662 should be set to the OBJECT IDENTIFIER { 0 0 }, 1663 which is a syntactically valid object identif- 1664 ier, and any implementation conforming to ASN.1 1665 and the Basic Encoding Rules must be able to 1666 generate and recognize this value." 1667 ::= { ipCidrRouteEntry 9 } 1669 ipCidrRouteNextHopAS OBJECT-TYPE 1670 SYNTAX Integer32 1671 MAX-ACCESS read-create 1672 STATUS current 1673 DESCRIPTION 1674 "The Autonomous System Number of the Next Hop. 1675 When this is unknown or not relevant to the 1676 protocol indicated by ipCidrRouteProto, zero." 1677 DEFVAL { 0 } 1678 ::= { ipCidrRouteEntry 10 } 1680 ipCidrRouteMetric1 OBJECT-TYPE 1681 SYNTAX Integer32 1682 MAX-ACCESS read-create 1683 STATUS current 1684 DESCRIPTION 1685 "The primary routing metric for this route. 1686 The semantics of this metric are determined by 1687 the routing-protocol specified in the route's 1688 ipCidrRouteProto value. If this metric is not 1689 used, its value should be set to -1." 1690 DEFVAL { -1 } 1691 ::= { ipCidrRouteEntry 11 } 1693 ipCidrRouteMetric2 OBJECT-TYPE 1694 SYNTAX Integer32 1695 MAX-ACCESS read-create 1696 STATUS current 1697 DESCRIPTION 1698 "An alternate routing metric for this route. 1699 The semantics of this metric are determined by 1700 the routing-protocol specified in the route's 1701 ipCidrRouteProto value. If this metric is not 1702 used, its value should be set to -1." 1703 DEFVAL { -1 } 1704 ::= { ipCidrRouteEntry 12 } 1706 ipCidrRouteMetric3 OBJECT-TYPE 1707 SYNTAX Integer32 1708 MAX-ACCESS read-create 1709 STATUS current 1710 DESCRIPTION 1711 "An alternate routing metric for this route. 1712 The semantics of this metric are determined by 1713 the routing-protocol specified in the route's 1714 ipCidrRouteProto value. If this metric is not 1715 used, its value should be set to -1." 1716 DEFVAL { -1 } 1717 ::= { ipCidrRouteEntry 13 } 1719 ipCidrRouteMetric4 OBJECT-TYPE 1720 SYNTAX Integer32 1721 MAX-ACCESS read-create 1722 STATUS current 1723 DESCRIPTION 1724 "An alternate routing metric for this route. 1725 The semantics of this metric are determined by 1726 the routing-protocol specified in the route's 1727 ipCidrRouteProto value. If this metric is not 1728 used, its value should be set to -1." 1729 DEFVAL { -1 } 1730 ::= { ipCidrRouteEntry 14 } 1732 ipCidrRouteMetric5 OBJECT-TYPE 1733 SYNTAX Integer32 1734 MAX-ACCESS read-create 1735 STATUS current 1736 DESCRIPTION 1737 "An alternate routing metric for this route. 1738 The semantics of this metric are determined by 1739 the routing-protocol specified in the route's 1740 ipCidrRouteProto value. If this metric is not 1741 used, its value should be set to -1." 1742 DEFVAL { -1 } 1743 ::= { ipCidrRouteEntry 15 } 1745 ipCidrRouteStatus OBJECT-TYPE 1746 SYNTAX RowStatus 1747 MAX-ACCESS read-create 1748 STATUS current 1749 DESCRIPTION 1750 "The row status variable, used according to 1751 row installation and removal conventions." 1752 ::= { ipCidrRouteEntry 16 } 1754 -- conformance information 1756 ipForwardConformance OBJECT IDENTIFIER ::= { ipForward 5 } 1758 ipForwardGroups OBJECT IDENTIFIER ::= { ipForwardConformance 1 } 1759 ipForwardCompliances OBJECT IDENTIFIER ::= { ipForwardConformance 2 } 1761 -- compliance statements 1763 ipForwardCompliance MODULE-COMPLIANCE 1764 STATUS current 1765 DESCRIPTION 1766 "The compliance statement for SNMPv2 entities 1767 which implement the ipForward MIB." 1769 MODULE -- this module 1770 MANDATORY-GROUPS { ipForwardCidrRouteGroup } 1772 GROUP ipForwardCidrRouteGroup 1773 DESCRIPTION 1774 "The ipForwardCidrRouteGroup group is current only for those 1775 SNMPv2 entities which implement CIDR Routing." 1776 ::= { ipForwardCompliances 1 } 1778 -- units of conformance 1780 ipForwardMultiPathGroup OBJECT-GROUP 1781 OBJECTS { ipForwardNumber, 1782 ipForwardDest, ipForwardMask, ipForwardPolicy, 1783 ipForwardNextHop, ipForwardIfIndex, ipForwardType, 1784 ipForwardProto, ipForwardAge, ipForwardInfo, 1785 ipForwardNextHopAS, 1786 ipForwardMetric1, ipForwardMetric2, ipForwardMetric3, 1787 ipForwardMetric4, ipForwardMetric5 1788 } 1789 STATUS obsolete 1790 DESCRIPTION 1791 "IP Multipath Route Table." 1792 ::= { ipForwardGroups 2 } 1794 ipForwardCidrRouteGroup OBJECT-GROUP 1795 OBJECTS { ipCidrRouteNumber, 1796 ipCidrRouteDest, ipCidrRouteMask, ipCidrRouteTos, 1797 ipCidrRouteNextHop, ipCidrRouteIfIndex, ipCidrRouteType, 1798 ipCidrRouteProto, ipCidrRouteAge, ipCidrRouteInfo, 1799 ipCidrRouteNextHopAS, ipCidrRouteMetric1, 1800 ipCidrRouteMetric2, ipCidrRouteMetric3, 1801 ipCidrRouteMetric4, ipCidrRouteMetric5, ipCidrRouteStatus 1802 } 1803 STATUS current 1804 DESCRIPTION 1805 "The CIDR Route Table." 1806 ::= { ipForwardGroups 3 } 1808 END 1809 13. Acknowledgements 1811 This work was originally performed by the Router Requirements 1812 Working Group at the request of the OSPF Working Group. This 1813 update was performed under the auspices of the OSPF Working 1814 Group. John Moy of Proteon Incorporated is the chair. 1816 14. References 1818 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1819 "Structure of Management Information for version 2 of the 1820 Simple Network Management Protocol (SNMPv2)", RFC 1442, 1821 SNMP Research, Inc., Hughes LAN Systems, Dover Beach 1822 Consulting, Inc., Carnegie Mellon University, April 1993. 1824 [2] Galvin, J., and K. McCloghrie, "Administrative Model for 1825 version 2 of the Simple Network Management Protocol 1826 (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes 1827 LAN Systems, April 1993. 1829 [3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1830 "Protocol Operations for version 2 of the Simple Network 1831 Management Protocol (SNMPv2)", RFC 1448, SNMP Research, 1832 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., 1833 Carnegie Mellon University, April 1993. 1835 [4] McCloghrie, K., and M. Rose, "Management Information Base 1836 for Network Management of TCP/IP-based internets - MIB- 1837 II", STD 17, RFC 1213, Hughes LAN Systems, Performance 1838 Systems International, March 1991. 1840 [5] Postel, J., "Internet Protocol", STD 5, RFC 791, 1841 USC/Information Sciences Institute, September 1981. 1843 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1844 "Textual Conventions for version 2 of the Simple Network 1845 Management Protocol (SNMPv2)", RFC 1443, SNMP Research, 1846 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., 1847 Carnegie Mellon University, April 1993. 1849 [7] Fred Baker, "IP Forwarding Table MIB", Request for 1850 Comments 1354, (July 1992). 1852 15. Security Considerations 1854 Security is an objective not in this MIB view. 1856 16. Author's Address 1858 Fred Baker 1859 Cisco Systems 1860 519 Lado Drive 1861 Santa Barbara, California 93111 1863 Phone: +1 805 681 0115 1864 Email: fred@cisco.com 1866 Table of Contents 1868 9 Introduction .......................................... 28 1869 10 The SNMPv2 Network Management Framework .............. 29 1870 10.1 Object Definitions ................................. 29 1871 11 Overview ............................................. 30 1872 12 Definitions .......................................... 31 1873 13 Acknowledgements ..................................... 50 1874 14 References ........................................... 51 1875 15 Security Considerations .............................. 52 1876 16 Author's Address ..................................... 52