idnits 2.17.1 draft-ietf-frnetmib-mfrmib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 38 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 40 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1626 has weird spacing: '...for the purpo...' -- 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 9, 2000) is 8814 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) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 1604 (Obsoleted by RFC 2954) ** Obsolete normative reference: RFC 2233 (Obsoleted by RFC 2863) -- Possible downref: Non-RFC (?) normative reference: ref. 'ATMLANE' ** Obsolete normative reference: RFC 1573 (Obsoleted by RFC 2233) Summary: 21 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Definitions of Managed Objects 2 for Monitoring and Controlling the 3 UNI/NNI Multilink Frame Relay Function 5 March 9, 2000 7 draft-ietf-frnetmib-mfrmib-01 9 Prayson Pate/Bob Lynch 10 Larscom 11 pate@larscom.com 13 Kenneth Rehbehn 14 Visual Networks 15 krehbehn@visualnetworks.com 17 Status of this Memo 19 This document is an Internet-Draft and is in full conformance with 20 all provisions of Section 10 of RFC 2026. Internet-Drafts are 21 working documents of the Internet Engineering Task Force (IETF), its 22 areas, and its working groups. Note that other groups may also 23 distribute working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet- Drafts as reference 28 material or to cite them other than as ``work in progress.'' 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This memo defines a Management Information Base (MIB) for monitoring 39 and controlling a UNI/NNI Multilink Frame Relay Function as defined 40 in Frame Relay Forum FRF.16. This MIB also include conformance and 41 notification information. 43 Copyright Notice 45 Copyright (C) The Internet Society (2000). All Rights Reserved. 47 Table of Contents 49 1 The SNMP Management Framework ................................ 4 50 2 Overview ..................................................... 5 51 2.1 Multilink Frame Relay Background ........................... 5 52 2.1.1 Terminology .............................................. 5 53 2.1.2 Reference Model .......................................... 6 54 2.2 Structure of the MIB ....................................... 7 55 2.2.1 bundleMaxNumBundles ...................................... 7 56 2.2.2 bundleNextIndex .......................................... 7 57 2.2.3 bundleTable .............................................. 7 58 2.2.4 Bundle-to-ifIndex Mapping Table .......................... 7 59 2.2.5 bundleLinkTable .......................................... 8 60 2.3 Relationship With Other MIBS and Tables .................... 8 61 2.3.1 Relationship With Interface Table ........................ 8 62 2.3.1.1 Bundle Links ........................................... 8 63 2.3.1.2 Bundles ................................................ 8 64 2.3.1.3 Mapping Between ifIndex and bundleIndex ................ 9 65 2.3.1.4 ifTable Objects ........................................ 9 66 2.3.2 Relationship With Interface Stack Table .................. 9 67 2.3.3 Relationship With Frame Relay DTE MIB .................... 10 68 2.3.4 Relationship With Frame Relay Service MIB ................ 10 69 2.3.5 Example .................................................. 10 70 2.4 Creation Of Bundles and Bundle Links ....................... 12 71 2.4.1 Creation Of Bundles ...................................... 12 72 2.4.2 Creation Of Bundle Links ................................. 12 73 2.5 Notifications .............................................. 12 74 2.5.1 Bundle ................................................... 12 75 2.5.1.1 linkUp ................................................. 12 76 2.5.1.2 linkDown ............................................... 12 77 2.5.2 Bundle Link .............................................. 12 78 2.5.2.1 linkUp ................................................. 13 79 2.5.2.2 linkDown ............................................... 13 80 2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 13 81 3 Object Definitions ........................................... 14 82 4 Acknowledgments .............................................. 34 83 5 References ................................................... 35 84 6 Security Considerations ...................................... 37 85 7 Authors' Addresses ........................................... 38 86 8 Copyright Section ............................................ 38 88 1. The SNMP Management Framework 90 The SNMP Management Framework presently consists of five major 91 components: 93 o An overall architecture, described in RFC 2571 [RFC2571]. 95 o Mechanisms for describing and naming objects and events for the 96 purpose of management. The first version of this Structure of 97 Management Information (SMI) is called SMIv1 and described in 98 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 99 1215 [RFC1215]. The second version, called SMIv2, is described 100 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 101 [RFC2580]. 103 o Message protocols for transferring management information. The 104 first version of the SNMP message protocol is called SNMPv1 and 105 described in STD 15, RFC 1157 [RFC1157]. A second version of the 106 SNMP message protocol, which is not an Internet standards track 107 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 108 and RFC 1906 [RFC1906]. The third version of the message 109 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 110 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 112 o Protocol operations for accessing management information. The 113 first set of protocol operations and associated PDU formats is 114 described in STD 15, RFC 1157 [RFC1157]. A second set of 115 protocol operations and associated PDU formats is described in 116 RFC 1905 [RFC1905]. 118 o A set of fundamental applications described in RFC 2573 119 [RFC2573] and the view-based access control mechanism described 120 in RFC 2575 [RFC2575]. 122 A more detailed introduction to the current SNMP Management Framework 123 can be found in RFC 2570 [RFC2570]. 125 Managed objects are accessed via a virtual information store, termed 126 the Management Information Base or MIB. Objects in the MIB are 127 defined using the mechanisms defined in the SMI. 129 This memo specifies a MIB module that is compliant to the SMIv2. A 130 MIB conforming to the SMIv1 can be produced through the appropriate 131 translations. The resulting translated MIB must be semantically 132 equivalent, except where objects or events are omitted because no 133 translation is possible (use of Counter64). Some machine readable 134 information in SMIv2 will be converted into textual descriptions in 135 SMIv1 during the translation process. However, this loss of machine 136 readable information is not considered to change the semantics of the 137 MIB. 139 2. Overview 141 This document defines a Management Information Base (MIB) for 142 monitoring and controlling UNI/NNI Multilink Frame Relay interfaces. 143 The agreement on which this MIB is based was defined and documented 144 by the Frame Relay Forum in the Frame Relay Forum Document FRF.16 145 [FRF.16]. 147 2.1. Multilink Frame Relay Background 149 Multilink Frame Relay (MFR) for the User-to-Network Interface (UNI) 150 and the Network-to-Network Interface (NNI) provides physical 151 interface emulation for frame relay devices. The emulated physical 152 interface consists of one or more physical links, called "bundle 153 links", aggregated together into a single "bundle" of bandwidth. 154 This service provides a frame-based inverse multiplexing function, 155 sometimes referred to as an "IMUX". 157 The bundle provides the same order-preserving service as a physical 158 layer for frames sent on a data link connection. In addition, the 159 bundle provides support for all Frame Relay services based on UNI and 160 NNI standards. 162 2.1.1. Terminology 164 Physical Link -- A single physical interface that interconnects two 165 devices in a frame relay network (e.g. DS1, DS0, 166 Bearer channel, refer to FRF.14). 168 Bundle -- A grouping of one or more physical links using the 169 formats and procedures of multilink frame relay. 170 The bundle operates as a logical interface function 171 that emulates a single physical interface to the 172 Q.922 data link layer. 174 Bundle Link -- A MFR sub-component that controls operation of one 175 of the bundle's physical links. 177 2.1.2. Reference Model 179 +--------------------------+ +--------------------------+ 180 | Switching Layer -OR- | | Switching Layer -OR- | 181 | Higher-Level Applications| | Higher-Level Applications| 182 +--------------------------+ +--------------------------+ 183 | |C-Plane - Q.933| | |C-Plane - Q.933| 184 | U-Plane | (Note 1) | | U-Plane | (Note 1) | 185 | (Note 3) |---------------| | (Note 3) |---------------| 186 | |Q.922 (Note 2) | | |Q.922 (Note 2) | 187 +--------------------------+ +--------------------------+ 188 | Data Link Layer (Q.922) | | Data Link Layer (Q.922) | 189 +--------------------------+ +--------------------------+ 190 | Bundle (B) | | Bundle (B) | 191 +--------------------------+ +--------------------------+ 192 | Bundle | Bundle | Bundle | | Bundle | Bundle | Bundle | 193 | Link | Link | Link | | Link | Link | Link | 194 | (BL) | (BL) | (BL) | | (BL) | (BL) | (BL) | 195 +--------+--------+--------+ +--------+--------+--------+ 196 |Physical|Physical|Physical| |Physical|Physical|Physical| 197 | (PH) | (PH) | (PH) | ___________ | (PH) | (PH) | (PH) | 198 +----+---+----+---+----+---+ /\ \ +----+---+----+---+----+---+ 199 | | | / \ \ | | | 200 | | +---------\ \-----+ | | 201 | | / \ \ | | 202 | +--------------------\ \------------+ | 203 | _________\_______/ Bundle /_ | 204 | /\ / / \ | 205 +-------------| Bundle Link / / |------------------+ 206 \/_____________/ /____/ 207 \/__________/ 209 Figure 1: MFR Reference Diagram 211 Note 1: C-Plane operation described in Q.933 [Q.933] and FRF.4 212 [FRF.4] 214 Note 2: Multiple frame acknowledged information fransfer mode 215 described in Q.922 [Q.922] 217 Note 3: Core aspects for use with frame relay bearer service as 218 described in Q.922, Annex A [Q.922] 220 2.2. Structure of the MIB 222 The UNI/NNI MFR managed objects consist of two scalar objects and 223 three tables. 225 2.2.1. bundleMaxNumBundles 227 This scalar is used to inform the manager of the maximum number of 228 bundles supported by this device. 230 2.2.2. bundleNextIndex 232 This scalar is used to assist the manager in selecting a value for 233 bundleIndex during row creation. It can also be used to avoid race 234 conditions with multiple managers trying to create rows in the table 235 (see RFC 2494 [RFC2494] for one such alogrithm). 237 2.2.3. bundleTable 239 This table provides a means to configure and monitor bundles. It is 240 indexed by bundleIndex and contains these columns: 242 - bundleIndex Integer32 243 - bundleIfIndex InterfaceIndex 244 - bundleRowStatus RowStatus 245 - bundleNearEndName SnmpAdminString 246 - bundleFragmentation INTEGER 247 - bundleMaxFragSize Integer32 248 - bundleTimerHello INTEGER 249 - bundleTimerAck INTEGER 250 - bundleCountMaxRetry INTEGER 251 - bundleActivationClass INTEGER 252 - bundleThreshold Integer32 253 - bundleMaxDiffDelay Integer32 254 - bundleSeqNumSize INTEGER 255 - bundleLinksConfigured Integer32 256 - bundleLinksActive Integer32 257 - bundleBandwidth Integer32 258 - bundleFarEndName SnmpAdminString 259 - bundleResequencingErrors Counter32 261 2.2.4. Bundle-to-ifIndex Mapping Table 263 This table provides a means to take an ifIndex and find the 264 corresponding bundleIndex. It is indexed by ifIndex and contains 265 these columns: 267 - bundleIfIndexMapping InterfaceIndex 269 2.2.5. bundleLinkTable 271 This table provides a means to configure and monitor bundles. It is 272 indexed by ifIndex and contains these columns: 274 - bundleLinkRowStatus RowStatus 275 - bundleLinkConfigBundleIndex Integer32 276 - bundleLinkNearEndName SnmpAdminString 277 - bundleLinkState BundleLinkState 278 - bundleLinkFarEndName SnmpAdminString 279 - bundleLinkFarEndBundleName SnmpAdminString 280 - bundleLinkDelay Integer32 281 - bundleLinkFramesControlTx Counter32 282 - bundleLinkFramesControlRx Counter32 283 - bundleLinkFramesControlInvalid Counter32 284 - bundleLinkTimerExpiredCount Counter32 285 - bundleLinkLoopbackSuspected Counter32 286 - bundleLinkUnexpectedSequence Counter32 287 - bundleLinkMismatch Counter32 289 2.3. Relationship With Other MIBS and Tables 291 2.3.1. Relationship With Interface Table 293 2.3.1.1. Bundle Links 295 Each bundle link will appear as an interface in the ifTable. The 296 ifIndex that appears in the ifTable is used for indexing the bundle 297 link tables in the UNI-NNI MFR MIB. 299 2.3.1.2. Bundles 301 Each bundle will appear as an interface in the ifTable. There will 302 be corresponding bundleIndex which may be different than the ifIndex 303 of the bundle. 305 The reason is best summarized in RFC 2494 [RFC2494], which describes 306 frame relay bundle of DS0. It says: 308 This table is not indexed by ifIndex because the manager has to 309 choose the index in a createable row and the agent must be 310 allowed to select ifIndex values. 312 The rows in the ifEntry table are not creatable as they do not have 313 row status. RFC 2233 [RFC2233] suggests that the ifIndex should be 314 chosen by the agent. Here is its statement regarding row creation 315 and deletion: 317 While some interfaces, for example, most physical interfaces, 318 cannot be created via network management, other interfaces such 319 as logical interfaces sometimes can be. The ifTable contains 320 only generic information about an interface. Almost all 321 'create-able' interfaces have other, media-specific, information 322 through which configuration parameters may be supplied prior to 323 creating such an interface. Thus, the ifTable does not itself 324 support the creation or deletion of an interface (specifically, 325 it has no RowStatus column). Rather, if a particular interface 326 type supports the dynamic creation and/or deletion of an 327 interface of that type, then that media-specific MIB should 328 include an appropriate RowStatus object (see the ATM LAN- 329 Emulation Client MIB [ATMLANE] for an example of a MIB which 330 does this). Typically, when such a RowStatus object is 331 created/deleted, then the conceptual row in the ifTable 332 appears/disappears as a by-product, and an ifIndex value (chosen 333 by the agent) is stored in an appropriate object in the media- 334 specific MIB. 336 The ATM LAN-Emulation Client MIB [ATMLANE] uses different indices and 337 so does the IMA MIB. Looking at the examples we have, and the 338 statements from RFC, it seems better to have two indices. This gives 339 the SNMP agent implementor the freedom to manage their ifIndex in the 340 way they like. 342 2.3.1.3. Mapping Between ifIndex and bundleIndex 344 The bundleIfIndexMappingTable is indexed by ifIndex and provides the 345 means to map a given ifIndex into the corresponding bundleIndex. The 346 bundleIfIndexMapping object in the bundleConfigTable (indexed by 347 bundleIndex) provides the reverse mapping of a bundleIndex to the 348 corresponding ifIndex in the ifTable. 350 2.3.1.4. ifTable Objects 352 See the DESCRIPTION clauses for the bundleTable and bundleLinkTable 353 for a description of how they relate to the ifTable [RFC1573]. 355 2.3.2. Relationship With Interface Stack Table 357 The bundles and bundle links will appear in the ifStackTable defined 358 in RFC 2233 [RFC2233]. Each bundle link will appear a lower layer to 359 its owner bundle. The bundle will appear as a higher layer to the 360 bundle links and as a lower layer to a frame relay service or UNI. 362 2.3.3. Relationship With Frame Relay DTE MIB 364 The bundle will have a one-to-one correspondence with a DLCMI or UNI 365 that appear in the DTE MIB tables [RFC2115]. 367 2.3.4. Relationship With Frame Relay Service MIB 369 There is a one-to-one relationship between the MFR bundle and the 370 frame relay service logical port defined in RFC1604 [RFC1604]. There 371 is no other relationship between these MIBs. 373 2.3.5. Example 375 Figure two shows an example of how the various tables are related. 376 This example shows two bundles composed of 2 T1s each. The bundles 377 have a bundleIndex of 10 and 20 respectively. 379 +-------------------------+ 380 | Frame Relay Service | 381 +-----+-------------+-----+ 382 | | 383 +-----+------+------+-----+ 384 | MFR Bundle | MFR Bundle | 385 | 10 | 20 | 386 +--+-----+---+---+-----+--+ 387 | | | | 388 +-+-+ +-+-+ +-+-+ +-+-+ 389 |T1 | |T1 | |T1 | |T1 | 390 +---+ +---+ +-+-+ +---+ 392 Figure 2: Frame Relay Service Being Carried on 4 T1s 394 The assignment of the ifTable index values could for example be: 396 ifIndex | Description | ifType 397 --------+----------------------------+---------------------- 398 1 | FrameRelayService | frameRelayService(44) 399 2 | MFR Bundle #10 | frf16MfrBundle(163) 400 3 | MFR Bundle #20 | frf16MfrBundle(163) 401 4 | ds1 #1/MFR Bundle Link #1 | ds1(18) 402 5 | ds1 #2/MFR Bundle Link #2 | ds1(18) 403 6 | ds1 #3/MFR Bundle Link #3 | ds1(18) 404 7 | ds1 #4/MFR Bundle Link #4 | ds1(18) 406 The ifStackTable is then used to show the relationships between the 407 various interfaces. 409 HigherLayer | LowerLayer 410 ------------+----------- 411 0 | 1 412 1 | 2 413 2 | 3 414 2 | 4 415 3 | 5 416 3 | 6 417 4 | 0 418 5 | 0 419 6 | 0 420 7 | 0 422 The bundleIfIndexMappingTable shows the relationship between the 423 ifTable ifIndex and the bundleIndex: 425 ifIndex | bundleIfIndexMappingIndex 426 --------+-------------------------- 427 2 | 10 428 3 | 20 430 The bundleConfigTable shows the relationship between the bundleIndex 431 and the ifIndex: 433 bundleIndex | bundleIfIndex 434 -------------+-------------- 435 10 | 2 436 20 | 3 438 The bundleLinkConfigTable shows the relationship between the bundles 439 and bundle links: 441 bundleIndex | bundleLinkIfIndex 442 ------------+------------------ 443 10 | 4 444 10 | 5 445 20 | 6 446 20 | 7 448 2.4. Creation Of Bundles and Bundle Links 450 2.4.1. Creation Of Bundles 452 A bundle is created using the bundleConfigRowStatus RowStatus object. 453 There is no minimum set of objects required in order to create a new 454 bundle i.e. all of the parameters can assume default values. 456 2.4.2. Creation Of Bundle Links 458 A bundle link is created using the bundleLinkConfigRowStatus 459 RowStatus object. There is no minimum set of objects required in 460 order to create a new bundle link i.e. all of the parameters can 461 assume default values. 463 The bundle link is associated with a specific physical interface and 464 uses the ifIndex of the physical physical interface. The 465 bundleLinkEntry row objects may be created after or during creation 466 of the physical interface's ifEntry row objects. 468 The bundle identified in the object bundleIndex must exist at time of 469 bundle link creation. 471 2.5. Notifications 473 The linkUp and linkDown traps are defined in RFC 1573 [RFC1573]. 475 2.5.1. Bundle 477 The following SNMP traps are defined for MFR bundles. 479 2.5.1.1. linkUp 481 This trap is sent when the ifOperStatus of a bundle transitions from 482 down to up. This occurs when a sufficient number of links 483 (determined by bundleActivationClass and bundleThreshold) are in the 484 operationally up state. 486 2.5.1.2. linkDown 488 This trap is sent when the ifOperStatus of a bundle transitions from 489 up to down. This occurs when a insufficient number of links 490 (determined by bundleActivationClass and bundleThreshold) are in the 491 operationally up state. 493 2.5.2. Bundle Link 495 The following SNMP traps are defined for MFR bundle links. 497 2.5.2.1. linkUp 499 This trap is sent when a bundle link transitions into the up state. 501 2.5.2.2. linkDown 503 This trap is sent when a bundle link transitions from the up state. 505 2.5.2.3. mfrMibTrapBundleLinkMismatch 507 This trap indicates that a bundle link mismatch has been detected. 508 The following objects are reported: 510 - bundleNearEndName: configured name of near end bundle 511 - bundleFarEndName: previously reported name of far 512 end bundle 513 - bundleLinkNearEndName: configured name of near end bundle 514 - bundleLinkFarEndName: reported name of far end bundle 515 - bundleLinkFarEndBundleName: currently reported name of far 516 end bundle 518 Note that the configured items may have been configured 519 automatically. Note also that the bundleLinkMismatch counter is 520 incremented when the trap is sent. 522 3. Object Definitions 524 Managed objects are accessed via a virtual information store, termed 525 the Management Information Base or MIB. Objects in the MIB are 526 defined using the subset of Abstract Syntax Notation One (ASN.1) 527 defined in the SMI. In particular, each object type is named by an 528 OBJECT IDENTIFIER, an administratively assigned name. The object 529 type together with an object instance serves to uniquely identify a 530 specific instantiation of the object. For human convenience, we 531 often use a textual string, termed the descriptor, to refer to the 532 object type. 534 FRF16-MFR-MIB-EXP DEFINITIONS ::= BEGIN 536 IMPORTS 537 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, 538 NOTIFICATION-TYPE, experimental 539 FROM SNMPv2-SMI 540 TEXTUAL-CONVENTION, TestAndIncr, RowStatus 541 FROM SNMPv2-TC 542 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 543 FROM SNMPv2-CONF 544 SnmpAdminString 545 FROM SNMP-FRAMEWORK-MIB 546 InterfaceIndex, ifIndex 547 FROM IF-MIB; 549 mfrMib MODULE-IDENTITY 550 LAST-UPDATED "0003090000Z" 551 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" 552 CONTACT-INFO 553 "WG Charter: http://www.ietf.org/html.charters/frnetmib-charter.html 554 WG-email: frnetmib@sunroof.eng.sun.com 555 Subscribe: frnetmib-request@sunroof.eng.sun.com 556 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 558 Chair: Andy Malis 559 Lucent Technologies 560 Email: amalis@lucent.com 562 WG editor: Prayson Pate 563 Larscom 564 Email: pate@larscom.com 566 Co-author: Bob Lynch 567 Larscom 568 EMail: blynch@larscom.com 570 Co-author: Kenneth Rehbehn 571 Visual Networks 572 EMail: krehbehn@visualnetworks.com" 574 DESCRIPTION 575 "This is the MIB used to control and monitor the multilink frame 576 relay (MFR) function described in FRF.16. This was originally 577 submitted to the Frame Relay Forum as contribution FRFTC 99-151 578 and then updated as FRFTC 99-193." 580 -- --------------------------------------------------------- 581 -- --------------------------------------------------------- 582 -- Revision History 583 -- --------------------------------------------------------- 584 -- --------------------------------------------------------- 586 REVISION "0003090000Z" 587 DESCRIPTION 588 "Initial version of the FRF.16 UNI/NNI Multilink 589 Frame Relay MIB. Published as RFC [RFC-EDITOR: Enter RFC # here]." 591 REVISION "0003090000Z" 592 DESCRIPTION 593 "[RFC-EDITOR: Remove this and all following REVISION 594 statements prior to publication as an RFC] 596 Changes from draft-ietf-frnetmib-mfrmib-00.txt 597 o changed experimental number to IANA-approved 105. 598 o changed interface type for frf16MfrBundle to IANA-approved 163. 599 " 601 REVISION "9912061700Z" 602 DESCRIPTION 603 "Updates: 604 o changed name to draft-ietf-frnetmib-mfrmib-00 605 o updated text to match last MIB revisions 606 o corrected description of bundleIfIndexMappingTable 607 o added objects to show configured and current bundle links. 608 " 610 REVISION "9910212020Z" 611 DESCRIPTION 612 "Updated after comments from Michael Allen and Ken Rehben. 613 o corrected options for sequence number length 614 o changed frf16Mfr prefix to mfr 615 o created a sub-group for scalars 616 o created an entry in the bundleTable for maximum links per bundle 617 o changed indices to not-accessible 618 o changed DisplayString to SnmpAdminString 619 o updated some of the object descriptions 620 o added a -EXP to the name of the MIB 621 o added some DEFVAL and REFERENCE clauses" 623 REVISION "9910151300Z" 624 DESCRIPTION 625 "Updated after review at the October meeting in Huntsville: 626 o removed log table 627 o removed several columns from each table 628 o combined configuration, status and error tables into 629 one table each for bundles and bundle links 630 o added new objects for 631 - maximum number of bundles 632 - maximum fragment size 633 - size of sequence number 634 o added notifications 635 o added conformance information" 637 REVISION "9910011440Z" 638 DESCRIPTION 639 "Initial version submitted to the Frame Relay Forum 640 October meeting in Huntsville as FRFTC/99-151." 642 ::= { experimental 105 } 644 -- --------------------------------------------------------- 645 -- --------------------------------------------------------- 646 -- Textual Conventions 647 -- --------------------------------------------------------- 648 -- --------------------------------------------------------- 650 BundleLinkState ::= TEXTUAL-CONVENTION 651 STATUS current 652 DESCRIPTION 653 "The possible states for a bundle link, as defined in 654 Annex A of FRF.16." 655 REFERENCE "FRF.16 Annex A" 656 SYNTAX INTEGER { 657 bundleLinkStateAddSent (1), 658 bundleLinkStateAddRx (2), 659 bundleLinkStateAddAckRx (3), 660 bundleLinkStateUp (4), 661 bundleLinkStateIdlePending (5), 662 bundleLinkStateIdle (6), 663 bundleLinkStateDown (7), 664 bundleLinkStateDownIdle (8) 665 } 667 -- --------------------------------------------------------- 668 -- --------------------------------------------------------- 669 -- Object Identifers 670 -- --------------------------------------------------------- 671 -- --------------------------------------------------------- 673 mfrMibObjects OBJECT IDENTIFIER ::= { mfrMib 1 } 674 mfrMibTraps OBJECT IDENTIFIER ::= { mfrMib 2 } 675 mfrMibConformance OBJECT IDENTIFIER ::= { mfrMib 3 } 677 mfrMibScalarObjects OBJECT IDENTIFIER ::= { mfrMibObjects 1 } 678 mfrMibBundleObjects OBJECT IDENTIFIER ::= { mfrMibObjects 2 } 679 mfrMibBundleLinkObjects OBJECT IDENTIFIER ::= { mfrMibObjects 3 } 681 mfrMibTrapsPrefix OBJECT IDENTIFIER ::= { mfrMibTraps 0 } 683 mfrMibGroups OBJECT IDENTIFIER ::= { mfrMibConformance 1 } 684 mfrMibCompliances OBJECT IDENTIFIER ::= { mfrMibConformance 2 } 686 -- --------------------------------------------------------- 687 -- --------------------------------------------------------- 688 -- Scalars 689 -- --------------------------------------------------------- 690 -- --------------------------------------------------------- 692 bundleMaxNumBundles OBJECT-TYPE 693 SYNTAX Integer32 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "This object is used to inform the manager of the 698 maximum number of bundles supported by this device." 699 ::= { mfrMibScalarObjects 1 } 701 bundleNextIndex OBJECT-TYPE 702 SYNTAX TestAndIncr 703 MAX-ACCESS read-write 704 STATUS current 705 DESCRIPTION 706 "This object is used to assist the manager in 707 selecting a value for bundleIndex during row creation 708 in the bundleTable. It can also be used to avoid race 709 conditions with multiple managers trying to create 710 rows in the table (see RFC 2494 [RFC2494] for one such 711 alogrithm)." 712 REFERENCE "RFC 2494" 713 ::= { mfrMibScalarObjects 2 } 715 -- --------------------------------------------------------- 716 -- --------------------------------------------------------- 717 -- Bundle Table 718 -- --------------------------------------------------------- 719 -- --------------------------------------------------------- 721 bundleTable OBJECT-TYPE 722 SYNTAX SEQUENCE OF BundleEntry 723 MAX-ACCESS not-accessible 724 STATUS current 725 DESCRIPTION 726 "The bundle configuration and status table. There 727 is a one-to-one correspondence between a bundle 728 and an interface represented in the ifTable. 730 The following objects of the ifTable have specific 731 meaning for a MFR bundle: 732 ifAdminStatus - the bundle admin status 733 ifOperStatus - the bundle operational status 734 ifSpeed - the current bandwidth of the bundle 735 ifInUcastPkts - the number of frames received 736 on the bundle 737 ifOutUcastPkts - the number of frames transmitted 738 on the bundle 739 ifInErrors - frame (not fragment) errors 740 ifOutErrors - frame (not fragment) errors 741 " 742 ::= { mfrMibBundleObjects 3 } 744 bundleEntry OBJECT-TYPE 745 SYNTAX BundleEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "An entry in the bundle table." 750 INDEX { bundleIndex } 751 ::= { bundleTable 1 } 753 BundleEntry ::= 754 SEQUENCE { 755 bundleIndex 756 Integer32, 757 bundleIfIndex 758 InterfaceIndex, 759 bundleRowStatus 760 RowStatus, 761 bundleNearEndName 762 SnmpAdminString, 763 bundleFragmentation 764 INTEGER, 765 bundleMaxFragSize 766 Integer32, 768 bundleTimerHello 769 INTEGER, 770 bundleTimerAck 771 INTEGER, 772 bundleCountMaxRetry 773 INTEGER, 774 bundleActivationClass 775 INTEGER, 776 bundleThreshold 777 Integer32, 778 bundleMaxDiffDelay 779 Integer32, 780 bundleSeqNumSize 781 INTEGER, 782 bundleMaxBundleLinks 783 Integer32, 784 bundleLinksConfigured 785 Integer32, 786 bundleLinksActive 787 Integer32, 788 bundleBandwidth 789 Integer32, 790 bundleFarEndName 791 SnmpAdminString, 792 bundleResequencingErrors 793 Counter32 794 } 796 bundleIndex OBJECT-TYPE 797 SYNTAX Integer32 (1..2147483647) 798 MAX-ACCESS not-accessible 799 STATUS current 800 DESCRIPTION 801 "The index into the table. While this corresponds 802 to an entry in the ifTable, the value of bundleIndex 803 need not match that of the ifIndex in the ifTable. 804 A manager can use bundleNextIndex to select a unique 805 bundleIndex for creating a new row." 806 ::= { bundleEntry 1 } 808 bundleIfIndex OBJECT-TYPE 809 SYNTAX InterfaceIndex 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "The value should match an entry in the interface 814 table. The ifType should be set to frf16MfrBundle(163). 816 For example: if the value of bundleIfIndex is 10, 817 then a corresponding entry should be present in 818 the ifTable with an index of 10." 819 ::= { bundleEntry 2 } 821 bundleRowStatus OBJECT-TYPE 822 SYNTAX RowStatus 823 MAX-ACCESS read-create 824 STATUS current 825 DESCRIPTION 826 "The bundleRowStatus object allows create, change, 827 and delete operations on bundle entries." 828 REFERENCE "RFC 1903" 829 ::= { bundleEntry 3 } 831 bundleNearEndName OBJECT-TYPE 832 SYNTAX SnmpAdminString 833 MAX-ACCESS read-create 834 STATUS current 835 DESCRIPTION 836 "The configured name of the bundle." 837 REFERENCE "FRF.16 section 3.4.1" 838 ::= { bundleEntry 4 } 840 bundleFragmentation OBJECT-TYPE 841 SYNTAX INTEGER { 842 enable (1), 843 disable (2) 844 } 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "Controls whether the bundle performs/accepts 849 fragmentation and re-assembly. The possible 850 values are: 852 enable(1) - Bundle links will fragment frames 854 disable(2) - Bundle links will not fragment 855 frames." 856 DEFVAL { disable } 857 ::= { bundleEntry 5 } 859 bundleMaxFragSize OBJECT-TYPE 860 SYNTAX Integer32 (-1..8184) 861 UNITS "Octets" 862 MAX-ACCESS read-create 863 STATUS current 864 DESCRIPTION 865 "The maximum fragment size supported. Note that this 866 is only valid if bundleFragmentation is set to enable(1). 868 Zero is not a valid fragment size. 870 A bundle that does not support fragmentation must be 871 set to -1." 872 DEFVAL { -1 } 873 ::= { bundleEntry 6 } 875 bundleTimerHello OBJECT-TYPE 876 SYNTAX INTEGER (1..180) 877 UNITS "Seconds" 878 MAX-ACCESS read-create 879 STATUS current 880 DESCRIPTION 881 "The configured MFR Hello Timer value." 882 REFERENCE "FRF.16 section 4.3.8.1" 883 DEFVAL { 10 } 884 ::= { bundleEntry 7 } 886 bundleTimerAck OBJECT-TYPE 887 SYNTAX INTEGER (1..10) 888 UNITS "Seconds" 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "The configured MFR T_ACK value." 893 REFERENCE "FRF.16 section 4.3.8.2" 894 DEFVAL { 4 } 895 ::= { bundleEntry 8 } 897 bundleCountMaxRetry OBJECT-TYPE 898 SYNTAX INTEGER (1..5) 899 MAX-ACCESS read-create 900 STATUS current 901 DESCRIPTION 902 "The MFR N_MAX_RETRY value." 903 REFERENCE "FRF.16 section 4.3.8.3" 904 DEFVAL { 2 } 905 ::= { bundleEntry 9 } 907 bundleActivationClass OBJECT-TYPE 908 SYNTAX INTEGER { 909 bundleActivationClassA (1), -- at least one must link up 910 bundleActivationClassB (2), -- all links must be up 911 bundleActivationClassC (3), -- a certain number must be up 912 bundleActivationClassD (4) -- custom 913 } 914 MAX-ACCESS read-create 915 STATUS current 916 DESCRIPTION 917 "Controls the conditions under which the bundle is activated. 918 The following settings are available: 920 bundleActivationClassA(1) - at least one must link up 921 bundleActivationClassB(2) - all links must be up 922 bundleActivationClassC(3) - a certain number must be up. 923 Refer to bundleThreshold for 924 the required number. 925 bundleActivationClassD(4) - custom (implementation 926 specific)." 927 REFERENCE "FRF.16 section 4.2.2.1" 928 DEFVAL { bundleActivationClassA } 929 ::= { bundleEntry 10 } 931 bundleThreshold OBJECT-TYPE 932 SYNTAX Integer32 933 UNITS "Bundle Links" 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "Specifies the number of links that must be in operational 938 'up' state before the bundle will transition to an 939 operational up/active state. If the number of 940 operational 'up' links falls below this value, 941 then the bundle will transition to an inactive 942 state. 944 Note - this is only valid when bundleActivationClass 945 is set to bundleActivationClassC or, depending upon the 946 implementation, to bundleActivationClassD." 947 REFERENCE "FRF.16 section 4.2.2.1" 948 DEFVAL { -1 } 949 ::= { bundleEntry 11 } 951 bundleMaxDiffDelay OBJECT-TYPE 952 SYNTAX Integer32 953 UNITS "Milliseconds" 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "The maximum delay difference between the bundle 958 links." 959 DEFVAL { -1 } 960 ::= { bundleEntry 12 } 962 bundleSeqNumSize OBJECT-TYPE 963 SYNTAX INTEGER { 964 seqNumSize12bit (1), 965 seqNumSize24bit (2) 966 } 967 MAX-ACCESS read-create 968 STATUS current 969 DESCRIPTION 970 "Controls whether the standard FRF.12 12-bit 971 sequence number is used or the optional 24-bit 972 sequence number." 973 REFERENCE "FRFTC/99-194" 974 DEFVAL { seqNumSize12bit } 975 ::= { bundleEntry 13 } 977 bundleMaxBundleLinks OBJECT-TYPE 978 SYNTAX Integer32 979 UNITS "Bundle Links" 980 MAX-ACCESS read-only 981 STATUS current 982 DESCRIPTION 983 "The maximum number of bundle links supported for this bundle." 984 ::= { bundleEntry 14 } 986 bundleLinksConfigured OBJECT-TYPE 987 SYNTAX Integer32 988 UNITS "Bundle Links" 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The number of links configured for the bundle." 993 ::= { bundleEntry 15 } 995 bundleLinksActive OBJECT-TYPE 996 SYNTAX Integer32 997 UNITS "Bundle Links" 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The number of links that are active." 1002 ::= { bundleEntry 16 } 1004 bundleBandwidth OBJECT-TYPE 1005 SYNTAX Integer32 1006 UNITS "Bits/Sec" 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "The amount of available bandwidth on the bundle" 1011 ::= { bundleEntry 17 } 1013 bundleFarEndName OBJECT-TYPE 1014 SYNTAX SnmpAdminString 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "Name of the bundle received from the far end." 1019 REFERENCE "FRF.16 section 3.4.1" 1020 ::= { bundleEntry 18 } 1022 bundleResequencingErrors OBJECT-TYPE 1023 SYNTAX Counter32 1024 UNITS "Error Events" 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "A count of the number of resequncing errors. Each event 1029 may correspond to multiple lost frames. Example: 1030 Say sequence number 56, 59 and 60 is received for DLCI 100. 1031 It is decided by some means that sequence 57 and 58 is lost. 1032 This counter should then be incremented by ONE, even though 1033 two frames were lost." 1034 ::= { bundleEntry 19 } 1036 -- --------------------------------------------------------- 1037 -- --------------------------------------------------------- 1038 -- ifIndex Mapping to Bundle Index Table 1039 -- --------------------------------------------------------- 1040 -- --------------------------------------------------------- 1042 bundleIfIndexMappingTable OBJECT-TYPE 1043 SYNTAX SEQUENCE OF BundleIfIndexMappingEntry 1044 MAX-ACCESS not-accessible 1045 STATUS current 1046 DESCRIPTION 1047 "A table mapping the values of ifIndex to the 1048 bundleIndex. This is required in order to find 1049 the bundleIndex given an ifIndex. The mapping of 1050 bundleIndex to ifIndex is provided by the bundleIfIndex 1051 entry in the bundleTable." 1052 ::= { mfrMibBundleObjects 4 } 1054 bundleIfIndexMappingEntry OBJECT-TYPE 1055 SYNTAX BundleIfIndexMappingEntry 1056 MAX-ACCESS not-accessible 1057 STATUS current 1058 DESCRIPTION 1059 "Each row describes one ifIndex to bundleIndex mapping." 1060 INDEX { ifIndex } 1061 ::= { bundleIfIndexMappingTable 1 } 1063 BundleIfIndexMappingEntry ::= 1064 SEQUENCE { 1065 bundleIfIndexMappingIndex 1066 InterfaceIndex 1067 } 1069 bundleIfIndexMappingIndex OBJECT-TYPE 1070 SYNTAX InterfaceIndex 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "The bundleIndex of the given ifIndex." 1075 ::= { bundleIfIndexMappingEntry 2 } 1077 -- --------------------------------------------------------- 1078 -- --------------------------------------------------------- 1079 -- Bundle Link Table 1080 -- --------------------------------------------------------- 1081 -- --------------------------------------------------------- 1083 bundleLinkTable OBJECT-TYPE 1084 SYNTAX SEQUENCE OF BundleLinkEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "The bundle link configuration and status table. There 1089 is a one-to-one correspondence between a bundle link 1090 and a physical interface represented in the ifTable. The 1091 ifIndex of the physical interface is used to index the 1092 bundle link table, and to create rows. 1094 The following objects of the ifTable have specific 1095 meaning for a MFR bundle link: 1097 ifAdminStatus - the bundle link admin status 1098 ifOperStatus - the bundle link operational 1099 status 1100 ifSpeed - the bandwidth of the bundle 1101 link interface 1102 ifInUcastPkts - the number of frames received 1103 on the bundle link 1104 ifOutUcastPkts - the number of frames transmitted 1105 on the bundle link 1106 ifInErrors - frame and fragment errors 1107 ifOutErrors - frame and fragment errors" 1108 ::= { mfrMibBundleLinkObjects 1 } 1110 bundleLinkEntry OBJECT-TYPE 1111 SYNTAX BundleLinkEntry 1112 MAX-ACCESS not-accessible 1113 STATUS current 1114 DESCRIPTION 1115 "An entry in the bundle link table." 1116 INDEX { ifIndex } 1117 ::= { bundleLinkTable 1 } 1119 BundleLinkEntry ::= 1120 SEQUENCE { 1121 bundleLinkRowStatus 1122 RowStatus, 1123 bundleLinkConfigBundleIndex 1124 Integer32, 1125 bundleLinkNearEndName 1126 SnmpAdminString, 1127 bundleLinkState 1128 BundleLinkState, 1129 bundleLinkFarEndName 1130 SnmpAdminString, 1131 bundleLinkFarEndBundleName 1132 SnmpAdminString, 1133 bundleLinkDelay 1134 Integer32, 1135 bundleLinkFramesControlTx 1136 Counter32, 1137 bundleLinkFramesControlRx 1138 Counter32, 1139 bundleLinkFramesControlInvalid 1140 Counter32, 1141 bundleLinkTimerExpiredCount 1142 Counter32, 1143 bundleLinkLoopbackSuspected 1144 Counter32, 1145 bundleLinkUnexpectedSequence 1146 Counter32, 1147 bundleLinkMismatch 1148 Counter32 1149 } 1151 bundleLinkRowStatus OBJECT-TYPE 1152 SYNTAX RowStatus 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "The bundleLinkRowStatus object allows create, change, 1157 and delete operations on bundleLink entries. 1159 The create operation must fail if no physical interface 1160 is associated with the bundle link." 1162 ::= { bundleLinkEntry 1 } 1164 bundleLinkConfigBundleIndex OBJECT-TYPE 1165 SYNTAX Integer32 1166 MAX-ACCESS read-create 1167 STATUS current 1168 DESCRIPTION 1169 "The bundleLinkConfigBundleIndex object allows 1170 the manager to control the bundle to which the bundle 1171 link is assigned. If no value were in this field, then 1172 the bundle would remain in NOT_READY rowStatus and be 1173 unable to go to active. With an appropriate bundleIndex 1174 in this field, then we could put the bundleLink row in 1175 NOT_IN_SERVICE or ACTIVE rowStatus." 1176 ::= { bundleLinkEntry 2 } 1178 bundleLinkNearEndName OBJECT-TYPE 1179 SYNTAX SnmpAdminString 1180 MAX-ACCESS read-create 1181 STATUS current 1182 DESCRIPTION 1183 "The configured bundle link name that is sent to the far end." 1184 ::= { bundleLinkEntry 3 } 1186 bundleLinkState OBJECT-TYPE 1187 SYNTAX BundleLinkState 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "Current bundle link state as defined by the MFR protocol 1192 described in Annex A of FRF.16." 1193 REFERENCE "FRF.16 Annex A" 1194 ::= { bundleLinkEntry 4 } 1196 bundleLinkFarEndName OBJECT-TYPE 1197 SYNTAX SnmpAdminString 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "Name of bundle link received from far end." 1202 REFERENCE "FRF.16 section 3.4.2" 1203 ::= { bundleLinkEntry 5 } 1205 bundleLinkFarEndBundleName OBJECT-TYPE 1206 SYNTAX SnmpAdminString 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "Name of far end bundle for this link received from far end." 1212 REFERENCE "FRF.16 section 3.4.1" 1213 ::= { bundleLinkEntry 6 } 1215 bundleLinkDelay OBJECT-TYPE 1216 SYNTAX Integer32 1217 UNITS "Milliseconds" 1218 MAX-ACCESS read-only 1219 STATUS current 1220 DESCRIPTION 1221 "Current round-trip delay for this bundle link. The value -1 1222 is returned when an implementation does not support measurement 1223 of the bundle link delay." 1224 REFERENCE "FRF.16 section 3.4.4" 1225 ::= { bundleLinkEntry 7 } 1227 bundleLinkFramesControlTx OBJECT-TYPE 1228 SYNTAX Counter32 1229 UNITS "Frames" 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "Number of MFR control frames sent." 1234 REFERENCE "FRF.16 section 3.2" 1235 ::= { bundleLinkEntry 8 } 1237 bundleLinkFramesControlRx OBJECT-TYPE 1238 SYNTAX Counter32 1239 UNITS "Frames" 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "Number of valid MFR control frames received." 1244 REFERENCE "FRF.16 section 3.2" 1245 ::= { bundleLinkEntry 9 } 1247 bundleLinkFramesControlInvalid OBJECT-TYPE 1248 SYNTAX Counter32 1249 UNITS "Frames" 1250 MAX-ACCESS read-only 1251 STATUS current 1252 DESCRIPTION 1253 "The number of invalid MFR control frames received." 1254 REFERENCE "FRF.16 section 3.2" 1255 ::= { bundleLinkEntry 10 } 1257 bundleLinkTimerExpiredCount OBJECT-TYPE 1258 SYNTAX Counter32 1259 UNITS "Timer Expiration Events" 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "Number of times the T_HELLO or T_ACK timers expired." 1264 REFERENCE "FRF.16 section 4.3.8.1 and 4.3.8.2" 1265 ::= { bundleLinkEntry 11 } 1267 bundleLinkLoopbackSuspected OBJECT-TYPE 1268 SYNTAX Counter32 1269 UNITS "Loopback Suspected Events" 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The number of times a loopback has been suspected 1274 (based upon the use of magic numbers)." 1275 REFERENCE "FRF.16 section 4.3.7" 1276 ::= { bundleLinkEntry 12 } 1278 bundleLinkUnexpectedSequence OBJECT-TYPE 1279 SYNTAX Counter32 1280 UNITS "Frames" 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "The number of data MFR frames discarded because the sequence 1285 number of the frame for a DLCI was less than (delayed frame) 1286 or equal to (duplicate frame) the one expected for that DLCI. 1288 Example: 1289 Say frames with sequence numbers 56, 58, 59 is received for 1290 DLCI 100. While waiting for sequence number 57 another frame 1291 with sequence number 58 arrives. Frame 58 is discarded and 1292 the counter is incremented." 1293 REFERENCE "FRF.16 section 4.2.3.2" 1294 ::= { bundleLinkEntry 13 } 1296 bundleLinkMismatch OBJECT-TYPE 1297 SYNTAX Counter32 1298 UNITS "Bundle Name Mismatch Events" 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "The number of times that the unit has been notified by the 1303 remote peer that the bundle name is inconsistent with other 1304 bundle links attached to the far-end bundle." 1305 REFERENCE "FRF.16 section 4.3.2.4" 1306 ::= { bundleLinkEntry 14 } 1308 -- --------------------------------------------------------- 1309 -- --------------------------------------------------------- 1310 -- Notifications/Traps 1311 -- --------------------------------------------------------- 1312 -- --------------------------------------------------------- 1314 mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE 1315 OBJECTS { 1316 bundleNearEndName, 1317 bundleFarEndName, 1318 bundleLinkNearEndName, 1319 bundleLinkFarEndName, 1320 bundleLinkFarEndBundleName 1321 } 1322 STATUS current 1323 DESCRIPTION 1324 "This trap indicates that a bundle link mismatch has 1325 been detected. The following objects are reported: 1327 bundleNearEndName: configured name of near end bundle 1329 bundleFarEndName: previously reported name of 1330 far end bundle 1332 bundleLinkNearEndName: configured name of near end bundle 1334 bundleLinkFarEndName: reported name of far end bundle 1336 bundleLinkFarEndBundleName: currently reported name of 1337 far end bundle 1339 Note: that the configured items may have been configured 1340 automatically. 1342 Note: The bundleLinkMismatch counter is incremented when 1343 the trap is sent." 1344 REFERENCE "FRF.16 section 4.3.2.4" 1345 ::= { mfrMibTrapsPrefix 1 } 1347 -- --------------------------------------------------------- 1348 -- --------------------------------------------------------- 1349 -- Conformance/Compliance 1350 -- --------------------------------------------------------- 1351 -- --------------------------------------------------------- 1353 mfrMibCompliance MODULE-COMPLIANCE 1354 STATUS current 1355 DESCRIPTION 1356 "The compliance statement for equipment that implements 1357 the FRF16 MIB. All of the current groups are mandatory, 1358 but a number of objects may be read-only if the 1359 implementation does not allow configuration." 1360 MODULE -- this module 1361 MANDATORY-GROUPS { 1362 mfrMibBundleGroup, 1363 mfrMibBundleLinkGroup, 1364 mfrMibTrapGroup 1365 } 1367 OBJECT bundleFragmentation 1368 MIN-ACCESS read-only 1369 DESCRIPTION 1370 "Write access is not required, but the value used must be reported." 1372 OBJECT bundleMaxFragSize 1373 MIN-ACCESS read-only 1374 DESCRIPTION 1375 "Write access is not required, but the value used must be reported. 1376 A value of -1 indicates that the value is not applicable." 1378 OBJECT bundleThreshold 1379 MIN-ACCESS read-only 1380 DESCRIPTION 1381 "Write access is not required, but the value used must be reported. 1382 A value of -1 indicates that the value is not applicable." 1384 OBJECT bundleMaxDiffDelay 1385 MIN-ACCESS read-only 1386 DESCRIPTION 1387 "Write access is not required, but the value used must be reported." 1389 OBJECT bundleSeqNumSize 1390 MIN-ACCESS read-only 1391 DESCRIPTION 1392 "Write access is not required, but the value used must be reported. 1393 A value of -1 indicates that the value is not applicable." 1395 ::= { mfrMibCompliances 1 } 1397 -- --------------------------------------------------------- 1398 -- --------------------------------------------------------- 1399 -- Units of Conformance 1400 -- --------------------------------------------------------- 1401 -- --------------------------------------------------------- 1403 mfrMibBundleGroup OBJECT-GROUP 1404 OBJECTS { 1405 bundleMaxNumBundles, 1406 bundleNextIndex, 1407 bundleIfIndex, 1408 bundleRowStatus, 1409 bundleNearEndName, 1410 bundleFragmentation, 1411 bundleMaxFragSize, 1412 bundleTimerHello, 1413 bundleTimerAck, 1414 bundleCountMaxRetry, 1415 bundleActivationClass, 1416 bundleThreshold, 1417 bundleMaxDiffDelay, 1418 bundleMaxBundleLinks, 1419 bundleLinksConfigured, 1420 bundleLinksActive, 1421 bundleBandwidth, 1422 bundleSeqNumSize, 1423 bundleFarEndName, 1424 bundleResequencingErrors, 1425 bundleIfIndexMappingIndex 1426 } 1427 STATUS current 1428 DESCRIPTION 1429 "Group of objects describing bundles." 1430 ::= { mfrMibGroups 1 } 1432 mfrMibBundleLinkGroup OBJECT-GROUP 1433 OBJECTS { 1434 bundleLinkRowStatus, 1435 bundleLinkConfigBundleIndex, 1436 bundleLinkNearEndName, 1437 bundleLinkState, 1438 bundleLinkFarEndName, 1439 bundleLinkFarEndBundleName, 1440 bundleLinkDelay, 1441 bundleLinkFramesControlTx, 1442 bundleLinkFramesControlRx, 1443 bundleLinkFramesControlInvalid, 1444 bundleLinkTimerExpiredCount, 1445 bundleLinkLoopbackSuspected, 1446 bundleLinkUnexpectedSequence, 1447 bundleLinkMismatch 1448 } 1449 STATUS current 1450 DESCRIPTION 1451 "Group of objects describing bundle links." 1452 ::= { mfrMibGroups 2 } 1454 mfrMibTrapGroup NOTIFICATION-GROUP 1455 NOTIFICATIONS { 1456 mfrMibTrapBundleLinkMismatch 1457 } 1458 STATUS current 1459 DESCRIPTION 1460 "Group of objects describing notifications (traps)." 1461 ::= { mfrMibGroups 3 } 1463 END 1465 4. Acknowledgments 1467 This document was produced by the Frame Relay MFR MIB Working Group. 1469 5. References 1471 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1472 for Describing SNMP Management Frameworks", RFC 2571, April 1473 1999 1475 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1476 of Management Information for TCP/IP-based Internets", STD 1477 16, RFC 1155, May 1990 1479 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1480 16, RFC 1212, March 1991 1482 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1483 SNMP", RFC 1215, March 1991 1485 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1486 Rose, M., and S. Waldbusser, "Structure of Management 1487 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 1489 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1490 Rose, M., and S. Waldbusser, "Textual Conventions for 1491 SMIv2", STD 58, RFC 2579, April 1999 1493 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1494 Rose, M., and S. Waldbusser, "Conformance Statements for 1495 SMIv2", STD 58, RFC 2580, April 1999 1497 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1498 Network Management Protocol", STD 15, RFC 1157, May 1990. 1500 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1501 "Introduction to Community-based SNMPv2", RFC 1901, January 1502 1996. 1504 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1505 "Transport Mappings for Version 2 of the Simple Network 1506 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1508 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1509 Processing and Dispatching for the Simple Network Management 1510 Protocol (SNMP)", RFC 2572, April 1999 1512 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1513 (USM) for version 3 of the Simple Network Management 1514 Protocol (SNMPv3)", RFC 2574, April 1999 1516 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1517 "Protocol Operations for Version 2 of the Simple Network 1518 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1520 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1521 RFC 2573, April 1999 1523 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1524 Access Control Model (VACM) for the Simple Network 1525 Management Protocol (SNMP)", RFC 2575, April 1999 1527 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1528 "Introduction to Version 3 of the Internet-standard Network 1529 Management Framework", RFC 2570, April 1999 1531 [Q.922] ITU-T, Recommendation Q.922: "ISDN Data Link Layer 1532 Specification For Frame Mode Bearer Services" 1534 [Q.933] ITU-T, Recommendation Q.933: "Signalling Specification For 1535 Frame Mode Basic Call Control" 1537 [FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC 1538 Implementation Agreement" January 5, 1994. 1540 [FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay 1541 Interworking Implementation Agreement" August 20, 1999. 1543 [RFC1604] T. Brown, "Definitions of Managed Objects for Frame Relay 1544 Service" RFC 1604, Bell Communications Research, March 1994. 1545 [RFC-EDITOR: Update to current RFC that replaces RFC1604] 1547 [RFC2494] D. Fowler, "Definitions of Managed Objects for the DS0 and 1548 DS0 Bundle Interface Type" RFC 2494, Newbridge Networks, 1549 November 1997. 1551 [RFC2233] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB 1552 using SMIv2" RFC 2233, Cisco Systems, FTP Software, November 1553 1997. 1555 [ATMLANE] T. Newton, ed., "LAN Emulation Client Management 1556 Specification Version 2.0" AF-LANE-0093.000, ATM Forum, 1557 October, 1998 1559 [RFC2115] C. Brown, F. Baker, "Management Information Base for Frame 1560 Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco 1561 Systems, September 1997. 1563 [RFC1573] K. McCloghrie, F. Kastenholz, "Evolution of the Interfaces 1564 Group of MIB-II" RFC 1573, Hughes LAN Systems, FTP Software, 1565 January 1994. 1567 6. Security Considerations 1569 There are a number of management objects defined in this MIB that 1570 have a MAX-ACCESS clause of read-write and/or read-create. Such 1571 objects may be considered sensitive or vulnerable in some network 1572 environments. The support for SET operations in a non-secure 1573 environment without proper protection can have a negative effect on 1574 network operations. 1576 No managed objects in this MIB contain sensitive information. 1578 SNMPv1 by itself is not a secure environment. Even if the network 1579 itself is secure (for example by using IPSec), even then, there is no 1580 control as to who on the secure network is allowed to access and 1581 GET/SET (read/change/create/delete) the objects in this MIB. 1583 It is recommended that the implementers consider the security 1584 features as provided by the SNMPv3 framework. Specifically, the use 1585 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1586 based Access Control Model RFC 2575 [RFC2575] is recommended. 1588 It is then a customer/user responsibility to ensure that the SNMP 1589 entity giving access to an instance of this MIB, is properly 1590 configured to give access to the objects only to those principals 1591 (users) that have legitimate rights to indeed GET or SET 1592 (change/create/delete) them. 1594 7. Authors' Addresses 1596 Prayson Pate/Bob Lynch 1597 Larscom 1598 P. O. Box 14993 1599 RTP, NC, USA 27560 1601 Phone: +1 919 991-9000 1603 EMail: pate@larscom.com/blynch@larscom.com 1605 Kenneth Rehbehn 1606 Visual Networks 1607 2092 Gaither Road 1608 Rockville, MD, USA 20850 1610 Phone: +1 301 296-2325 1612 EMail: krehbehn@visualnetworks.com 1614 8. Copyright Section 1616 Copyright (C) The Internet Society (2000). All Rights Reserved. 1618 This document and translations of it may be copied and furnished to 1619 others, and derivative works that comment on or otherwise explain it 1620 or assist in its implementation may be prepared, copied, published 1621 and distributed, in whole or in part, without restriction of any 1622 kind, provided that the above copyright notice and this paragraph are 1623 included on all such copies and derivative works. However, this 1624 document itself may not be modified in any way, such as by removing 1625 the copyright notice or references to the Internet Society or other 1626 Internet organizations, except as needed for the purpose of 1627 developing Internet standards in which case the procedures for 1628 copyrights defined in the Internet Standards process must be 1629 followed, or as required to translate it into languages other than 1630 English. 1632 The limited permissions granted above are perpetual and will not be 1633 revoked by the Internet Society or its successors or assigns. 1635 This document and the information contained herein is provided on an 1636 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1637 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1638 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1639 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1640 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.