idnits 2.17.1 draft-ietf-frnetmib-mfrmib-02.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 41 instances of too long lines in the document, the longest one being 9 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 1634 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 (April 4, 2000) is 8787 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 April 4, 2000 7 draft-ietf-frnetmib-mfrmib-02.txt 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 Integer32 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 1 | 3 414 2 | 4 415 2 | 5 416 3 | 6 417 3 | 7 418 4 | 0 419 5 | 0 420 6 | 0 421 7 | 0 423 The bundleIfIndexMappingTable shows the relationship between the 424 ifTable ifIndex and the bundleIndex: 426 ifIndex | bundleIfIndexMappingIndex 427 --------+-------------------------- 428 2 | 10 429 3 | 20 431 The bundleConfigTable shows the relationship between the bundleIndex 432 and the ifIndex: 434 bundleIndex | bundleIfIndex 435 -------------+-------------- 436 10 | 2 437 20 | 3 439 The bundleLinkConfigTable shows the relationship between the bundles 440 and bundle links: 442 bundleIndex | bundleLinkIfIndex 443 ------------+------------------ 444 10 | 4 445 10 | 5 446 20 | 6 447 20 | 7 449 2.4. Creation Of Bundles and Bundle Links 451 2.4.1. Creation Of Bundles 453 A bundle is created using the bundleConfigRowStatus RowStatus object. 454 There is no minimum set of objects required in order to create a new 455 bundle i.e. all of the parameters can assume default values. 457 2.4.2. Creation Of Bundle Links 459 A bundle link is created using the bundleLinkConfigRowStatus 460 RowStatus object. There is no minimum set of objects required in 461 order to create a new bundle link i.e. all of the parameters can 462 assume default values. 464 The bundle link is associated with a specific physical interface and 465 uses the ifIndex of the physical physical interface. The 466 bundleLinkEntry row objects may be created after or during creation 467 of the physical interface's ifEntry row objects. 469 The bundle identified in the object bundleIndex must exist at time of 470 bundle link creation. 472 2.5. Notifications 474 The linkUp and linkDown traps are defined in RFC 1573 [RFC1573]. 476 2.5.1. Bundle 478 The following SNMP traps are defined for MFR bundles. 480 2.5.1.1. linkUp 482 This trap is sent when the ifOperStatus of a bundle transitions from 483 down to up. This occurs when a sufficient number of links 484 (determined by bundleActivationClass and bundleThreshold) are in the 485 operationally up state. 487 2.5.1.2. linkDown 489 This trap is sent when the ifOperStatus of a bundle transitions from 490 up to down. This occurs when a insufficient number of links 491 (determined by bundleActivationClass and bundleThreshold) are in the 492 operationally up state. 494 2.5.2. Bundle Link 496 The following SNMP traps are defined for MFR bundle links. 498 2.5.2.1. linkUp 500 This trap is sent when a bundle link transitions into the up state. 502 2.5.2.2. linkDown 504 This trap is sent when a bundle link transitions from the up state. 506 2.5.2.3. mfrMibTrapBundleLinkMismatch 508 This trap indicates that a bundle link mismatch has been detected. 509 The following objects are reported: 511 - bundleNearEndName: configured name of near end bundle 512 - bundleFarEndName: previously reported name of far 513 end bundle 514 - bundleLinkNearEndName: configured name of near end bundle 515 - bundleLinkFarEndName: reported name of far end bundle 516 - bundleLinkFarEndBundleName: currently reported name of far 517 end bundle 519 Note that the configured items may have been configured 520 automatically. Note also that the bundleLinkMismatch counter is 521 incremented when the trap is sent. 523 3. Object Definitions 525 Managed objects are accessed via a virtual information store, termed 526 the Management Information Base or MIB. Objects in the MIB are 527 defined using the subset of Abstract Syntax Notation One (ASN.1) 528 defined in the SMI. In particular, each object type is named by an 529 OBJECT IDENTIFIER, an administratively assigned name. The object 530 type together with an object instance serves to uniquely identify a 531 specific instantiation of the object. For human convenience, we 532 often use a textual string, termed the descriptor, to refer to the 533 object type. 535 FRF16-MFR-MIB-EXP DEFINITIONS ::= BEGIN 537 IMPORTS 538 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, 539 NOTIFICATION-TYPE, experimental 540 FROM SNMPv2-SMI 541 TEXTUAL-CONVENTION, TestAndIncr, RowStatus 542 FROM SNMPv2-TC 543 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 544 FROM SNMPv2-CONF 545 SnmpAdminString 546 FROM SNMP-FRAMEWORK-MIB 547 InterfaceIndex, ifIndex 548 FROM IF-MIB; 550 mfrMib MODULE-IDENTITY 551 LAST-UPDATED "0003090000Z" 552 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" 553 CONTACT-INFO 554 "WG Charter: http://www.ietf.org/html.charters/frnetmib-charter.html 555 WG-email: frnetmib@sunroof.eng.sun.com 556 Subscribe: frnetmib-request@sunroof.eng.sun.com 557 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 559 Chair: Andy Malis 560 Lucent Technologies 561 Email: amalis@lucent.com 563 WG editor: Prayson Pate 564 Larscom 565 Email: pate@larscom.com 567 Co-author: Bob Lynch 568 Larscom 569 EMail: blynch@larscom.com 571 Co-author: Kenneth Rehbehn 572 Visual Networks 573 EMail: krehbehn@visualnetworks.com" 575 DESCRIPTION 576 "This is the MIB used to control and monitor the multilink frame 577 relay (MFR) function described in FRF.16. This was originally 578 submitted to the Frame Relay Forum as contribution FRFTC 99-151 579 and then updated as FRFTC 99-193." 581 -- --------------------------------------------------------- 582 -- --------------------------------------------------------- 583 -- Revision History 584 -- --------------------------------------------------------- 585 -- --------------------------------------------------------- 587 REVISION "0003090000Z" 588 DESCRIPTION 589 "Initial version of the FRF.16 UNI/NNI Multilink 590 Frame Relay MIB. Published as RFC [RFC-EDITOR: Enter RFC # here]." 592 REVISION "0004040000Z" 593 DESCRIPTION 594 "[RFC-EDITOR: Remove this and all following REVISION 595 statements prior to publication as an RFC] 597 Changes from draft-ietf-frnetmib-mfrmib-01.txt from IETF-47: 598 o Fixed display of sample ifStackTable 599 o Changed bundleIfIndexMappingIndex from InterfaceIndex to Integer32 600 " 602 REVISION "0003090000Z" 603 DESCRIPTION 604 "Changes from draft-ietf-frnetmib-mfrmib-00.txt 605 o changed experimental number to IANA-approved 105. 606 o changed interface type for frf16MfrBundle to IANA-approved 163. 607 " 609 REVISION "9912061700Z" 610 DESCRIPTION 611 "Updates: 612 o changed name to draft-ietf-frnetmib-mfrmib-00 613 o updated text to match last MIB revisions 614 o corrected description of bundleIfIndexMappingTable 615 o added objects to show configured and current bundle links. 616 " 618 REVISION "9910212020Z" 619 DESCRIPTION 620 "Updated after comments from Michael Allen and Ken Rehben. 621 o corrected options for sequence number length 622 o changed frf16Mfr prefix to mfr 623 o created a sub-group for scalars 624 o created an entry in the bundleTable for maximum links per bundle 625 o changed indices to not-accessible 626 o changed DisplayString to SnmpAdminString 627 o updated some of the object descriptions 628 o added a -EXP to the name of the MIB 629 o added some DEFVAL and REFERENCE clauses" 631 REVISION "9910151300Z" 632 DESCRIPTION 633 "Updated after review at the October meeting in Huntsville: 634 o removed log table 635 o removed several columns from each table 636 o combined configuration, status and error tables into 637 one table each for bundles and bundle links 638 o added new objects for 639 - maximum number of bundles 640 - maximum fragment size 641 - size of sequence number 642 o added notifications 643 o added conformance information" 645 REVISION "9910011440Z" 646 DESCRIPTION 647 "Initial version submitted to the Frame Relay Forum 648 October meeting in Huntsville as FRFTC/99-151." 650 ::= { experimental 105 } 652 -- --------------------------------------------------------- 653 -- --------------------------------------------------------- 654 -- Textual Conventions 655 -- --------------------------------------------------------- 656 -- --------------------------------------------------------- 658 BundleLinkState ::= TEXTUAL-CONVENTION 659 STATUS current 660 DESCRIPTION 661 "The possible states for a bundle link, as defined in 662 Annex A of FRF.16." 663 REFERENCE "FRF.16 Annex A" 664 SYNTAX INTEGER { 665 bundleLinkStateAddSent (1), 666 bundleLinkStateAddRx (2), 667 bundleLinkStateAddAckRx (3), 668 bundleLinkStateUp (4), 669 bundleLinkStateIdlePending (5), 670 bundleLinkStateIdle (6), 671 bundleLinkStateDown (7), 672 bundleLinkStateDownIdle (8) 673 } 675 -- --------------------------------------------------------- 676 -- --------------------------------------------------------- 677 -- Object Identifers 678 -- --------------------------------------------------------- 679 -- --------------------------------------------------------- 681 mfrMibObjects OBJECT IDENTIFIER ::= { mfrMib 1 } 682 mfrMibTraps OBJECT IDENTIFIER ::= { mfrMib 2 } 683 mfrMibConformance OBJECT IDENTIFIER ::= { mfrMib 3 } 685 mfrMibScalarObjects OBJECT IDENTIFIER ::= { mfrMibObjects 1 } 686 mfrMibBundleObjects OBJECT IDENTIFIER ::= { mfrMibObjects 2 } 687 mfrMibBundleLinkObjects OBJECT IDENTIFIER ::= { mfrMibObjects 3 } 689 mfrMibTrapsPrefix OBJECT IDENTIFIER ::= { mfrMibTraps 0 } 691 mfrMibGroups OBJECT IDENTIFIER ::= { mfrMibConformance 1 } 692 mfrMibCompliances OBJECT IDENTIFIER ::= { mfrMibConformance 2 } 694 -- --------------------------------------------------------- 695 -- --------------------------------------------------------- 696 -- Scalars 697 -- --------------------------------------------------------- 698 -- --------------------------------------------------------- 700 bundleMaxNumBundles OBJECT-TYPE 701 SYNTAX Integer32 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "This object is used to inform the manager of the 706 maximum number of bundles supported by this device." 707 ::= { mfrMibScalarObjects 1 } 709 bundleNextIndex OBJECT-TYPE 710 SYNTAX TestAndIncr 711 MAX-ACCESS read-write 712 STATUS current 713 DESCRIPTION 714 "This object is used to assist the manager in 715 selecting a value for bundleIndex during row creation 716 in the bundleTable. It can also be used to avoid race 717 conditions with multiple managers trying to create 718 rows in the table (see RFC 2494 [RFC2494] for one such 719 alogrithm)." 720 REFERENCE "RFC 2494" 721 ::= { mfrMibScalarObjects 2 } 723 -- --------------------------------------------------------- 724 -- --------------------------------------------------------- 725 -- Bundle Table 726 -- --------------------------------------------------------- 727 -- --------------------------------------------------------- 729 bundleTable OBJECT-TYPE 730 SYNTAX SEQUENCE OF BundleEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "The bundle configuration and status table. There 735 is a one-to-one correspondence between a bundle 736 and an interface represented in the ifTable. 738 The following objects of the ifTable have specific 739 meaning for a MFR bundle: 740 ifAdminStatus - the bundle admin status 741 ifOperStatus - the bundle operational status 742 ifSpeed - the current bandwidth of the bundle 743 ifInUcastPkts - the number of frames received 744 on the bundle 745 ifOutUcastPkts - the number of frames transmitted 746 on the bundle 747 ifInErrors - frame (not fragment) errors 748 ifOutErrors - frame (not fragment) errors 749 " 750 ::= { mfrMibBundleObjects 3 } 752 bundleEntry OBJECT-TYPE 753 SYNTAX BundleEntry 754 MAX-ACCESS not-accessible 755 STATUS current 756 DESCRIPTION 757 "An entry in the bundle table." 758 INDEX { bundleIndex } 759 ::= { bundleTable 1 } 761 BundleEntry ::= 762 SEQUENCE { 763 bundleIndex 764 Integer32, 765 bundleIfIndex 766 InterfaceIndex, 768 bundleRowStatus 769 RowStatus, 770 bundleNearEndName 771 SnmpAdminString, 772 bundleFragmentation 773 INTEGER, 774 bundleMaxFragSize 775 Integer32, 776 bundleTimerHello 777 INTEGER, 778 bundleTimerAck 779 INTEGER, 780 bundleCountMaxRetry 781 INTEGER, 782 bundleActivationClass 783 INTEGER, 784 bundleThreshold 785 Integer32, 786 bundleMaxDiffDelay 787 Integer32, 788 bundleSeqNumSize 789 INTEGER, 790 bundleMaxBundleLinks 791 Integer32, 792 bundleLinksConfigured 793 Integer32, 794 bundleLinksActive 795 Integer32, 796 bundleBandwidth 797 Integer32, 798 bundleFarEndName 799 SnmpAdminString, 800 bundleResequencingErrors 801 Counter32 802 } 804 bundleIndex OBJECT-TYPE 805 SYNTAX Integer32 (1..2147483647) 806 MAX-ACCESS not-accessible 807 STATUS current 808 DESCRIPTION 809 "The index into the table. While this corresponds 810 to an entry in the ifTable, the value of bundleIndex 811 need not match that of the ifIndex in the ifTable. 812 A manager can use bundleNextIndex to select a unique 813 bundleIndex for creating a new row." 814 ::= { bundleEntry 1 } 816 bundleIfIndex OBJECT-TYPE 817 SYNTAX InterfaceIndex 818 MAX-ACCESS read-only 819 STATUS current 820 DESCRIPTION 821 "The value should match an entry in the interface 822 table. The ifType should be set to frf16MfrBundle(163). 824 For example: if the value of bundleIfIndex is 10, 825 then a corresponding entry should be present in 826 the ifTable with an index of 10." 827 ::= { bundleEntry 2 } 829 bundleRowStatus OBJECT-TYPE 830 SYNTAX RowStatus 831 MAX-ACCESS read-create 832 STATUS current 833 DESCRIPTION 834 "The bundleRowStatus object allows create, change, 835 and delete operations on bundle entries." 836 REFERENCE "RFC 1903" 837 ::= { bundleEntry 3 } 839 bundleNearEndName OBJECT-TYPE 840 SYNTAX SnmpAdminString 841 MAX-ACCESS read-create 842 STATUS current 843 DESCRIPTION 844 "The configured name of the bundle." 845 REFERENCE "FRF.16 section 3.4.1" 846 ::= { bundleEntry 4 } 848 bundleFragmentation OBJECT-TYPE 849 SYNTAX INTEGER { 850 enable (1), 851 disable (2) 852 } 853 MAX-ACCESS read-create 854 STATUS current 855 DESCRIPTION 856 "Controls whether the bundle performs/accepts 857 fragmentation and re-assembly. The possible 858 values are: 860 enable(1) - Bundle links will fragment frames 862 disable(2) - Bundle links will not fragment 863 frames." 864 DEFVAL { disable } 865 ::= { bundleEntry 5 } 867 bundleMaxFragSize OBJECT-TYPE 868 SYNTAX Integer32 (-1..8184) 869 UNITS "Octets" 870 MAX-ACCESS read-create 871 STATUS current 872 DESCRIPTION 873 "The maximum fragment size supported. Note that this 874 is only valid if bundleFragmentation is set to enable(1). 876 Zero is not a valid fragment size. 878 A bundle that does not support fragmentation must be 879 set to -1." 880 DEFVAL { -1 } 881 ::= { bundleEntry 6 } 883 bundleTimerHello OBJECT-TYPE 884 SYNTAX INTEGER (1..180) 885 UNITS "Seconds" 886 MAX-ACCESS read-create 887 STATUS current 888 DESCRIPTION 889 "The configured MFR Hello Timer value." 890 REFERENCE "FRF.16 section 4.3.8.1" 891 DEFVAL { 10 } 892 ::= { bundleEntry 7 } 894 bundleTimerAck OBJECT-TYPE 895 SYNTAX INTEGER (1..10) 896 UNITS "Seconds" 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "The configured MFR T_ACK value." 901 REFERENCE "FRF.16 section 4.3.8.2" 902 DEFVAL { 4 } 903 ::= { bundleEntry 8 } 905 bundleCountMaxRetry OBJECT-TYPE 906 SYNTAX INTEGER (1..5) 907 MAX-ACCESS read-create 908 STATUS current 909 DESCRIPTION 910 "The MFR N_MAX_RETRY value." 911 REFERENCE "FRF.16 section 4.3.8.3" 912 DEFVAL { 2 } 913 ::= { bundleEntry 9 } 915 bundleActivationClass OBJECT-TYPE 916 SYNTAX INTEGER { 917 bundleActivationClassA (1), -- at least one must link up 918 bundleActivationClassB (2), -- all links must be up 919 bundleActivationClassC (3), -- a certain number must be up 920 bundleActivationClassD (4) -- custom 921 } 922 MAX-ACCESS read-create 923 STATUS current 924 DESCRIPTION 925 "Controls the conditions under which the bundle is activated. 926 The following settings are available: 928 bundleActivationClassA(1) - at least one must link up 929 bundleActivationClassB(2) - all links must be up 930 bundleActivationClassC(3) - a certain number must be up. 931 Refer to bundleThreshold for 932 the required number. 933 bundleActivationClassD(4) - custom (implementation 934 specific)." 935 REFERENCE "FRF.16 section 4.2.2.1" 936 DEFVAL { bundleActivationClassA } 937 ::= { bundleEntry 10 } 939 bundleThreshold OBJECT-TYPE 940 SYNTAX Integer32 941 UNITS "Bundle Links" 942 MAX-ACCESS read-create 943 STATUS current 944 DESCRIPTION 945 "Specifies the number of links that must be in operational 946 'up' state before the bundle will transition to an 947 operational up/active state. If the number of 948 operational 'up' links falls below this value, 949 then the bundle will transition to an inactive 950 state. 952 Note - this is only valid when bundleActivationClass 953 is set to bundleActivationClassC or, depending upon the 954 implementation, to bundleActivationClassD." 955 REFERENCE "FRF.16 section 4.2.2.1" 956 DEFVAL { -1 } 957 ::= { bundleEntry 11 } 959 bundleMaxDiffDelay OBJECT-TYPE 960 SYNTAX Integer32 961 UNITS "Milliseconds" 962 MAX-ACCESS read-create 963 STATUS current 964 DESCRIPTION 965 "The maximum delay difference between the bundle 966 links." 967 DEFVAL { -1 } 968 ::= { bundleEntry 12 } 970 bundleSeqNumSize OBJECT-TYPE 971 SYNTAX INTEGER { 972 seqNumSize12bit (1), 973 seqNumSize24bit (2) 974 } 975 MAX-ACCESS read-create 976 STATUS current 977 DESCRIPTION 978 "Controls whether the standard FRF.12 12-bit 979 sequence number is used or the optional 24-bit 980 sequence number." 981 REFERENCE "FRFTC/99-194" 982 DEFVAL { seqNumSize12bit } 983 ::= { bundleEntry 13 } 985 bundleMaxBundleLinks OBJECT-TYPE 986 SYNTAX Integer32 987 UNITS "Bundle Links" 988 MAX-ACCESS read-only 989 STATUS current 990 DESCRIPTION 991 "The maximum number of bundle links supported for this bundle." 992 ::= { bundleEntry 14 } 994 bundleLinksConfigured OBJECT-TYPE 995 SYNTAX Integer32 996 UNITS "Bundle Links" 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The number of links configured for the bundle." 1001 ::= { bundleEntry 15 } 1003 bundleLinksActive OBJECT-TYPE 1004 SYNTAX Integer32 1005 UNITS "Bundle Links" 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The number of links that are active." 1010 ::= { bundleEntry 16 } 1012 bundleBandwidth OBJECT-TYPE 1013 SYNTAX Integer32 1014 UNITS "Bits/Sec" 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "The amount of available bandwidth on the bundle" 1019 ::= { bundleEntry 17 } 1021 bundleFarEndName OBJECT-TYPE 1022 SYNTAX SnmpAdminString 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "Name of the bundle received from the far end." 1027 REFERENCE "FRF.16 section 3.4.1" 1028 ::= { bundleEntry 18 } 1030 bundleResequencingErrors OBJECT-TYPE 1031 SYNTAX Counter32 1032 UNITS "Error Events" 1033 MAX-ACCESS read-only 1034 STATUS current 1035 DESCRIPTION 1036 "A count of the number of resequncing errors. Each event 1037 may correspond to multiple lost frames. Example: 1038 Say sequence number 56, 59 and 60 is received for DLCI 100. 1039 It is decided by some means that sequence 57 and 58 is lost. 1040 This counter should then be incremented by ONE, even though 1041 two frames were lost." 1042 ::= { bundleEntry 19 } 1044 -- --------------------------------------------------------- 1045 -- --------------------------------------------------------- 1046 -- ifIndex Mapping to Bundle Index Table 1047 -- --------------------------------------------------------- 1048 -- --------------------------------------------------------- 1050 bundleIfIndexMappingTable OBJECT-TYPE 1051 SYNTAX SEQUENCE OF BundleIfIndexMappingEntry 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "A table mapping the values of ifIndex to the 1056 bundleIndex. This is required in order to find 1057 the bundleIndex given an ifIndex. The mapping of 1058 bundleIndex to ifIndex is provided by the bundleIfIndex 1059 entry in the bundleTable." 1060 ::= { mfrMibBundleObjects 4 } 1062 bundleIfIndexMappingEntry OBJECT-TYPE 1063 SYNTAX BundleIfIndexMappingEntry 1064 MAX-ACCESS not-accessible 1065 STATUS current 1066 DESCRIPTION 1067 "Each row describes one ifIndex to bundleIndex mapping." 1068 INDEX { ifIndex } 1069 ::= { bundleIfIndexMappingTable 1 } 1071 BundleIfIndexMappingEntry ::= 1072 SEQUENCE { 1073 bundleIfIndexMappingIndex 1074 Integer32 1075 } 1077 bundleIfIndexMappingIndex OBJECT-TYPE 1078 SYNTAX Integer32 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "The bundleIndex of the given ifIndex." 1083 ::= { bundleIfIndexMappingEntry 2 } 1085 -- --------------------------------------------------------- 1086 -- --------------------------------------------------------- 1087 -- Bundle Link Table 1088 -- --------------------------------------------------------- 1089 -- --------------------------------------------------------- 1091 bundleLinkTable OBJECT-TYPE 1092 SYNTAX SEQUENCE OF BundleLinkEntry 1093 MAX-ACCESS not-accessible 1094 STATUS current 1095 DESCRIPTION 1096 "The bundle link configuration and status table. There 1097 is a one-to-one correspondence between a bundle link 1098 and a physical interface represented in the ifTable. The 1099 ifIndex of the physical interface is used to index the 1100 bundle link table, and to create rows. 1102 The following objects of the ifTable have specific 1103 meaning for a MFR bundle link: 1105 ifAdminStatus - the bundle link admin status 1106 ifOperStatus - the bundle link operational 1107 status 1108 ifSpeed - the bandwidth of the bundle 1109 link interface 1110 ifInUcastPkts - the number of frames received 1111 on the bundle link 1113 ifOutUcastPkts - the number of frames transmitted 1114 on the bundle link 1115 ifInErrors - frame and fragment errors 1116 ifOutErrors - frame and fragment errors" 1117 ::= { mfrMibBundleLinkObjects 1 } 1119 bundleLinkEntry OBJECT-TYPE 1120 SYNTAX BundleLinkEntry 1121 MAX-ACCESS not-accessible 1122 STATUS current 1123 DESCRIPTION 1124 "An entry in the bundle link table." 1125 INDEX { ifIndex } 1126 ::= { bundleLinkTable 1 } 1128 BundleLinkEntry ::= 1129 SEQUENCE { 1130 bundleLinkRowStatus 1131 RowStatus, 1132 bundleLinkConfigBundleIndex 1133 Integer32, 1134 bundleLinkNearEndName 1135 SnmpAdminString, 1136 bundleLinkState 1137 BundleLinkState, 1138 bundleLinkFarEndName 1139 SnmpAdminString, 1140 bundleLinkFarEndBundleName 1141 SnmpAdminString, 1142 bundleLinkDelay 1143 Integer32, 1144 bundleLinkFramesControlTx 1145 Counter32, 1146 bundleLinkFramesControlRx 1147 Counter32, 1148 bundleLinkFramesControlInvalid 1149 Counter32, 1150 bundleLinkTimerExpiredCount 1151 Counter32, 1152 bundleLinkLoopbackSuspected 1153 Counter32, 1154 bundleLinkUnexpectedSequence 1155 Counter32, 1156 bundleLinkMismatch 1157 Counter32 1158 } 1160 bundleLinkRowStatus OBJECT-TYPE 1161 SYNTAX RowStatus 1162 MAX-ACCESS read-create 1163 STATUS current 1164 DESCRIPTION 1165 "The bundleLinkRowStatus object allows create, change, 1166 and delete operations on bundleLink entries. 1168 The create operation must fail if no physical interface 1169 is associated with the bundle link." 1170 ::= { bundleLinkEntry 1 } 1172 bundleLinkConfigBundleIndex OBJECT-TYPE 1173 SYNTAX Integer32 1174 MAX-ACCESS read-create 1175 STATUS current 1176 DESCRIPTION 1177 "The bundleLinkConfigBundleIndex object allows 1178 the manager to control the bundle to which the bundle 1179 link is assigned. If no value were in this field, then 1180 the bundle would remain in NOT_READY rowStatus and be 1181 unable to go to active. With an appropriate bundleIndex 1182 in this field, then we could put the bundleLink row in 1183 NOT_IN_SERVICE or ACTIVE rowStatus." 1184 ::= { bundleLinkEntry 2 } 1186 bundleLinkNearEndName OBJECT-TYPE 1187 SYNTAX SnmpAdminString 1188 MAX-ACCESS read-create 1189 STATUS current 1190 DESCRIPTION 1191 "The configured bundle link name that is sent to the far end." 1192 ::= { bundleLinkEntry 3 } 1194 bundleLinkState OBJECT-TYPE 1195 SYNTAX BundleLinkState 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "Current bundle link state as defined by the MFR protocol 1200 described in Annex A of FRF.16." 1201 REFERENCE "FRF.16 Annex A" 1202 ::= { bundleLinkEntry 4 } 1204 bundleLinkFarEndName OBJECT-TYPE 1205 SYNTAX SnmpAdminString 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "Name of bundle link received from far end." 1210 REFERENCE "FRF.16 section 3.4.2" 1211 ::= { bundleLinkEntry 5 } 1213 bundleLinkFarEndBundleName OBJECT-TYPE 1214 SYNTAX SnmpAdminString 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "Name of far end bundle for this link received from far end." 1219 REFERENCE "FRF.16 section 3.4.1" 1220 ::= { bundleLinkEntry 6 } 1222 bundleLinkDelay OBJECT-TYPE 1223 SYNTAX Integer32 1224 UNITS "Milliseconds" 1225 MAX-ACCESS read-only 1226 STATUS current 1227 DESCRIPTION 1228 "Current round-trip delay for this bundle link. The value -1 1229 is returned when an implementation does not support measurement 1230 of the bundle link delay." 1231 REFERENCE "FRF.16 section 3.4.4" 1232 ::= { bundleLinkEntry 7 } 1234 bundleLinkFramesControlTx OBJECT-TYPE 1235 SYNTAX Counter32 1236 UNITS "Frames" 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "Number of MFR control frames sent." 1241 REFERENCE "FRF.16 section 3.2" 1242 ::= { bundleLinkEntry 8 } 1244 bundleLinkFramesControlRx OBJECT-TYPE 1245 SYNTAX Counter32 1246 UNITS "Frames" 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "Number of valid MFR control frames received." 1251 REFERENCE "FRF.16 section 3.2" 1252 ::= { bundleLinkEntry 9 } 1254 bundleLinkFramesControlInvalid OBJECT-TYPE 1255 SYNTAX Counter32 1256 UNITS "Frames" 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "The number of invalid MFR control frames received." 1261 REFERENCE "FRF.16 section 3.2" 1262 ::= { bundleLinkEntry 10 } 1264 bundleLinkTimerExpiredCount OBJECT-TYPE 1265 SYNTAX Counter32 1266 UNITS "Timer Expiration Events" 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "Number of times the T_HELLO or T_ACK timers expired." 1271 REFERENCE "FRF.16 section 4.3.8.1 and 4.3.8.2" 1272 ::= { bundleLinkEntry 11 } 1274 bundleLinkLoopbackSuspected OBJECT-TYPE 1275 SYNTAX Counter32 1276 UNITS "Loopback Suspected Events" 1277 MAX-ACCESS read-only 1278 STATUS current 1279 DESCRIPTION 1280 "The number of times a loopback has been suspected 1281 (based upon the use of magic numbers)." 1282 REFERENCE "FRF.16 section 4.3.7" 1283 ::= { bundleLinkEntry 12 } 1285 bundleLinkUnexpectedSequence OBJECT-TYPE 1286 SYNTAX Counter32 1287 UNITS "Frames" 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The number of data MFR frames discarded because the sequence 1292 number of the frame for a DLCI was less than (delayed frame) 1293 or equal to (duplicate frame) the one expected for that DLCI. 1295 Example: 1296 Say frames with sequence numbers 56, 58, 59 is received for 1297 DLCI 100. While waiting for sequence number 57 another frame 1298 with sequence number 58 arrives. Frame 58 is discarded and 1299 the counter is incremented." 1300 REFERENCE "FRF.16 section 4.2.3.2" 1301 ::= { bundleLinkEntry 13 } 1303 bundleLinkMismatch OBJECT-TYPE 1304 SYNTAX Counter32 1305 UNITS "Bundle Name Mismatch Events" 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "The number of times that the unit has been notified by the 1310 remote peer that the bundle name is inconsistent with other 1311 bundle links attached to the far-end bundle." 1312 REFERENCE "FRF.16 section 4.3.2.4" 1313 ::= { bundleLinkEntry 14 } 1315 -- --------------------------------------------------------- 1316 -- --------------------------------------------------------- 1317 -- Notifications/Traps 1318 -- --------------------------------------------------------- 1319 -- --------------------------------------------------------- 1321 mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE 1322 OBJECTS { 1323 bundleNearEndName, 1324 bundleFarEndName, 1325 bundleLinkNearEndName, 1326 bundleLinkFarEndName, 1327 bundleLinkFarEndBundleName 1328 } 1329 STATUS current 1330 DESCRIPTION 1331 "This trap indicates that a bundle link mismatch has 1332 been detected. The following objects are reported: 1334 bundleNearEndName: configured name of near end bundle 1336 bundleFarEndName: previously reported name of 1337 far end bundle 1339 bundleLinkNearEndName: configured name of near end bundle 1341 bundleLinkFarEndName: reported name of far end bundle 1343 bundleLinkFarEndBundleName: currently reported name of 1344 far end bundle 1346 Note: that the configured items may have been configured 1347 automatically. 1349 Note: The bundleLinkMismatch counter is incremented when 1350 the trap is sent." 1351 REFERENCE "FRF.16 section 4.3.2.4" 1352 ::= { mfrMibTrapsPrefix 1 } 1354 -- --------------------------------------------------------- 1355 -- --------------------------------------------------------- 1356 -- Conformance/Compliance 1357 -- --------------------------------------------------------- 1358 -- --------------------------------------------------------- 1360 mfrMibCompliance MODULE-COMPLIANCE 1361 STATUS current 1362 DESCRIPTION 1363 "The compliance statement for equipment that implements 1364 the FRF16 MIB. All of the current groups are mandatory, 1365 but a number of objects may be read-only if the 1366 implementation does not allow configuration." 1367 MODULE -- this module 1368 MANDATORY-GROUPS { 1369 mfrMibBundleGroup, 1370 mfrMibBundleLinkGroup, 1371 mfrMibTrapGroup 1372 } 1374 OBJECT bundleFragmentation 1375 MIN-ACCESS read-only 1376 DESCRIPTION 1377 "Write access is not required, but the value used must be reported." 1379 OBJECT bundleMaxFragSize 1380 MIN-ACCESS read-only 1381 DESCRIPTION 1382 "Write access is not required, but the value used must be reported. 1383 A value of -1 indicates that the value is not applicable." 1385 OBJECT bundleThreshold 1386 MIN-ACCESS read-only 1387 DESCRIPTION 1388 "Write access is not required, but the value used must be reported. 1389 A value of -1 indicates that the value is not applicable." 1391 OBJECT bundleMaxDiffDelay 1392 MIN-ACCESS read-only 1393 DESCRIPTION 1394 "Write access is not required, but the value used must be reported." 1396 OBJECT bundleSeqNumSize 1397 MIN-ACCESS read-only 1398 DESCRIPTION 1399 "Write access is not required, but the value used must be reported. 1400 A value of -1 indicates that the value is not applicable." 1402 ::= { mfrMibCompliances 1 } 1404 -- --------------------------------------------------------- 1405 -- --------------------------------------------------------- 1406 -- Units of Conformance 1407 -- --------------------------------------------------------- 1408 -- --------------------------------------------------------- 1410 mfrMibBundleGroup OBJECT-GROUP 1411 OBJECTS { 1412 bundleMaxNumBundles, 1413 bundleNextIndex, 1414 bundleIfIndex, 1415 bundleRowStatus, 1416 bundleNearEndName, 1417 bundleFragmentation, 1418 bundleMaxFragSize, 1419 bundleTimerHello, 1420 bundleTimerAck, 1421 bundleCountMaxRetry, 1422 bundleActivationClass, 1423 bundleThreshold, 1424 bundleMaxDiffDelay, 1425 bundleMaxBundleLinks, 1426 bundleLinksConfigured, 1427 bundleLinksActive, 1428 bundleBandwidth, 1429 bundleSeqNumSize, 1430 bundleFarEndName, 1431 bundleResequencingErrors, 1432 bundleIfIndexMappingIndex 1433 } 1434 STATUS current 1435 DESCRIPTION 1436 "Group of objects describing bundles." 1437 ::= { mfrMibGroups 1 } 1439 mfrMibBundleLinkGroup OBJECT-GROUP 1440 OBJECTS { 1441 bundleLinkRowStatus, 1442 bundleLinkConfigBundleIndex, 1443 bundleLinkNearEndName, 1444 bundleLinkState, 1445 bundleLinkFarEndName, 1446 bundleLinkFarEndBundleName, 1447 bundleLinkDelay, 1448 bundleLinkFramesControlTx, 1449 bundleLinkFramesControlRx, 1450 bundleLinkFramesControlInvalid, 1451 bundleLinkTimerExpiredCount, 1452 bundleLinkLoopbackSuspected, 1453 bundleLinkUnexpectedSequence, 1454 bundleLinkMismatch 1455 } 1457 STATUS current 1458 DESCRIPTION 1459 "Group of objects describing bundle links." 1460 ::= { mfrMibGroups 2 } 1462 mfrMibTrapGroup NOTIFICATION-GROUP 1463 NOTIFICATIONS { 1464 mfrMibTrapBundleLinkMismatch 1465 } 1466 STATUS current 1467 DESCRIPTION 1468 "Group of objects describing notifications (traps)." 1469 ::= { mfrMibGroups 3 } 1471 END 1473 4. Acknowledgments 1475 This document was produced by the Frame Relay MFR MIB Working Group. 1477 5. References 1479 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1480 for Describing SNMP Management Frameworks", RFC 2571, April 1481 1999 1483 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1484 of Management Information for TCP/IP-based Internets", STD 1485 16, RFC 1155, May 1990 1487 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1488 16, RFC 1212, March 1991 1490 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1491 SNMP", RFC 1215, March 1991 1493 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1494 Rose, M., and S. Waldbusser, "Structure of Management 1495 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 1497 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1498 Rose, M., and S. Waldbusser, "Textual Conventions for 1499 SMIv2", STD 58, RFC 2579, April 1999 1501 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1502 Rose, M., and S. Waldbusser, "Conformance Statements for 1503 SMIv2", STD 58, RFC 2580, April 1999 1505 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1506 Network Management Protocol", STD 15, RFC 1157, May 1990. 1508 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1509 "Introduction to Community-based SNMPv2", RFC 1901, January 1510 1996. 1512 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1513 "Transport Mappings for Version 2 of the Simple Network 1514 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1516 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1517 Processing and Dispatching for the Simple Network Management 1518 Protocol (SNMP)", RFC 2572, April 1999 1520 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1521 (USM) for version 3 of the Simple Network Management 1522 Protocol (SNMPv3)", RFC 2574, April 1999 1524 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1525 "Protocol Operations for Version 2 of the Simple Network 1526 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1528 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1529 RFC 2573, April 1999 1531 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1532 Access Control Model (VACM) for the Simple Network 1533 Management Protocol (SNMP)", RFC 2575, April 1999 1535 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1536 "Introduction to Version 3 of the Internet-standard Network 1537 Management Framework", RFC 2570, April 1999 1539 [Q.922] ITU-T, Recommendation Q.922: "ISDN Data Link Layer 1540 Specification For Frame Mode Bearer Services" 1542 [Q.933] ITU-T, Recommendation Q.933: "Signalling Specification For 1543 Frame Mode Basic Call Control" 1545 [FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC 1546 Implementation Agreement" January 5, 1994. 1548 [FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay 1549 Interworking Implementation Agreement" August 20, 1999. 1551 [RFC1604] T. Brown, "Definitions of Managed Objects for Frame Relay 1552 Service" RFC 1604, Bell Communications Research, March 1994. 1553 [RFC-EDITOR: Update to current RFC that replaces RFC1604] 1555 [RFC2494] D. Fowler, "Definitions of Managed Objects for the DS0 and 1556 DS0 Bundle Interface Type" RFC 2494, Newbridge Networks, 1557 November 1997. 1559 [RFC2233] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB 1560 using SMIv2" RFC 2233, Cisco Systems, FTP Software, November 1561 1997. 1563 [ATMLANE] T. Newton, ed., "LAN Emulation Client Management 1564 Specification Version 2.0" AF-LANE-0093.000, ATM Forum, 1565 October, 1998 1567 [RFC2115] C. Brown, F. Baker, "Management Information Base for Frame 1568 Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco 1569 Systems, September 1997. 1571 [RFC1573] K. McCloghrie, F. Kastenholz, "Evolution of the Interfaces 1572 Group of MIB-II" RFC 1573, Hughes LAN Systems, FTP Software, 1573 January 1994. 1575 6. Security Considerations 1577 There are a number of management objects defined in this MIB that 1578 have a MAX-ACCESS clause of read-write and/or read-create. Such 1579 objects may be considered sensitive or vulnerable in some network 1580 environments. The support for SET operations in a non-secure 1581 environment without proper protection can have a negative effect on 1582 network operations. 1584 No managed objects in this MIB contain sensitive information. 1586 SNMPv1 by itself is not a secure environment. Even if the network 1587 itself is secure (for example by using IPSec), even then, there is no 1588 control as to who on the secure network is allowed to access and 1589 GET/SET (read/change/create/delete) the objects in this MIB. 1591 It is recommended that the implementers consider the security 1592 features as provided by the SNMPv3 framework. Specifically, the use 1593 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1594 based Access Control Model RFC 2575 [RFC2575] is recommended. 1596 It is then a customer/user responsibility to ensure that the SNMP 1597 entity giving access to an instance of this MIB, is properly 1598 configured to give access to the objects only to those principals 1599 (users) that have legitimate rights to indeed GET or SET 1600 (change/create/delete) them. 1602 7. Authors' Addresses 1604 Prayson Pate/Bob Lynch 1605 Larscom 1606 P. O. Box 14993 1607 RTP, NC, USA 27560 1609 Phone: +1 919 991-9000 1611 EMail: pate@larscom.com/blynch@larscom.com 1613 Kenneth Rehbehn 1614 Visual Networks 1615 2092 Gaither Road 1616 Rockville, MD, USA 20850 1618 Phone: +1 301 296-2325 1620 EMail: krehbehn@visualnetworks.com 1622 8. Copyright Section 1624 Copyright (C) The Internet Society (2000). All Rights Reserved. 1626 This document and translations of it may be copied and furnished to 1627 others, and derivative works that comment on or otherwise explain it 1628 or assist in its implementation may be prepared, copied, published 1629 and distributed, in whole or in part, without restriction of any 1630 kind, provided that the above copyright notice and this paragraph are 1631 included on all such copies and derivative works. However, this 1632 document itself may not be modified in any way, such as by removing 1633 the copyright notice or references to the Internet Society or other 1634 Internet organizations, except as needed for the purpose of 1635 developing Internet standards in which case the procedures for 1636 copyrights defined in the Internet Standards process must be 1637 followed, or as required to translate it into languages other than 1638 English. 1640 The limited permissions granted above are perpetual and will not be 1641 revoked by the Internet Society or its successors or assigns. 1643 This document and the information contained herein is provided on an 1644 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1645 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1646 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1647 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1648 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.