idnits 2.17.1 draft-ietf-frnetmib-mfrmib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** 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 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1630 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 (October 2000) is 8593 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2223' is mentioned on line 508, but not defined ** Obsolete undefined reference: RFC 2223 (Obsoleted by RFC 7322) ** 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 (ref. 'RFC2863') (Obsoleted by RFC 2863) -- Possible downref: Non-RFC (?) normative reference: ref. 'ATMLANE' -- Possible downref: Non-RFC (?) normative reference: ref. 'ATMIMA' Summary: 19 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft MIB For FRF.16 UNI/NNI MFR October 2000 4 Definitions of Managed Objects 5 for Monitoring and Controlling the 6 UNI/NNI Multilink Frame Relay Function 8 October 6, 2000 10 draft-ietf-frnetmib-mfrmib-04 12 Prayson Pate 13 Overture Networks 14 prayson.pate@overturenetworks.com 16 Bob Lynch 17 Larscom Incorporated 18 blynch@larscom.com 20 Kenneth Rehbehn 21 Megisto Systems, Inc. 22 krehbehn@megisto.com 24 Status of this Memo 26 This document is an Internet-Draft and is in full conformance with 27 all provisions of Section 10 of RFC 2026. Internet-Drafts are 28 working documents of the Internet Engineering Task Force (IETF), its 29 areas, and its working groups. Note that other groups may also 30 distribute working documents as Internet-Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet- Drafts as reference 35 material or to cite them other than as ``work in progress.'' 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 Abstract 45 This memo defines a Management Information Base (MIB) for monitoring 46 and controlling a UNI/NNI Multilink Frame Relay Function as defined 47 in Frame Relay Forum FRF.16. This MIB also include conformance and 48 notification information. 50 Copyright Notice 52 Copyright (C) The Internet Society (2000). All Rights Reserved. 54 Table of Contents 56 1 The SNMP Management Framework ................................ 4 57 2 Overview ..................................................... 5 58 2.1 Multilink Frame Relay Background ........................... 5 59 2.1.1 Terminology .............................................. 5 60 2.1.2 Reference Model .......................................... 6 61 2.2 Structure of the MIB ....................................... 7 62 2.2.1 mfrBundleMaxNumBundles ................................... 7 63 2.2.2 mfrBundleNextIndex ....................................... 7 64 2.2.3 mfrBundleTable ........................................... 7 65 2.2.4 Bundle-to-ifIndex Mapping Table .......................... 7 66 2.2.5 mfrBundleLinkTable ....................................... 8 67 2.3 Relationship With Other MIBS and Tables .................... 8 68 2.3.1 Relationship With Interface Table ........................ 8 69 2.3.1.1 Bundle Links ........................................... 8 70 2.3.1.2 Bundles ................................................ 8 71 2.3.1.3 Mapping Between ifIndex and mfrBundleIndex ............. 9 72 2.3.1.4 ifTable Objects ........................................ 9 73 2.3.2 Relationship With Interface Stack Table .................. 10 74 2.3.3 Relationship With Frame Relay DTE MIB .................... 10 75 2.3.4 Relationship With Frame Relay Service MIB ................ 10 76 2.3.5 Example .................................................. 11 77 2.4 Creation Of Bundles and Bundle Links ....................... 12 78 2.4.1 Creation Of Bundles ...................................... 12 79 2.4.2 Creation Of Bundle Links ................................. 12 80 2.5 Notifications .............................................. 13 81 2.5.1 Bundle ................................................... 13 82 2.5.1.1 linkUp ................................................. 13 83 2.5.1.2 linkDown ............................................... 13 84 2.5.2 Bundle Link .............................................. 13 85 2.5.2.1 linkUp ................................................. 13 86 2.5.2.2 linkDown ............................................... 13 87 2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 14 88 3 Object Definitions ........................................... 15 89 4 Acknowledgments .............................................. 34 90 5 References ................................................... 35 91 6 Security Considerations ...................................... 37 92 7 Authors' Addresses ........................................... 38 93 8 Full Copyright Section ....................................... 39 95 1. The SNMP Management Framework 97 The SNMP Management Framework presently consists of five major 98 components: 100 o An overall architecture, described in RFC 2571 [RFC2571]. 102 o Mechanisms for describing and naming objects and events for the 103 purpose of management. The first version of this Structure of 104 Management Information (SMI) is called SMIv1 and described in 105 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 106 1215 [RFC1215]. The second version, called SMIv2, is described 107 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 108 [RFC2580]. 110 o Message protocols for transferring management information. The 111 first version of the SNMP message protocol is called SNMPv1 and 112 described in STD 15, RFC 1157 [RFC1157]. A second version of the 113 SNMP message protocol, which is not an Internet standards track 114 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 115 and RFC 1906 [RFC1906]. The third version of the message 116 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 117 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 119 o Protocol operations for accessing management information. The 120 first set of protocol operations and associated PDU formats is 121 described in STD 15, RFC 1157 [RFC1157]. A second set of 122 protocol operations and associated PDU formats is described in 123 RFC 1905 [RFC1905]. 125 o A set of fundamental applications described in RFC 2573 126 [RFC2573] and the view-based access control mechanism described 127 in RFC 2575 [RFC2575]. 129 A more detailed introduction to the current SNMP Management Framework 130 can be found in RFC 2570 [RFC2570]. 132 Managed objects are accessed via a virtual information store, termed 133 the Management Information Base or MIB. Objects in the MIB are 134 defined using the mechanisms defined in the SMI. 136 This memo specifies a MIB module that is compliant to the SMIv2. A 137 MIB conforming to the SMIv1 can be produced through the appropriate 138 translations. The resulting translated MIB must be semantically 139 equivalent, except where objects or events are omitted because no 140 translation is possible (use of Counter64). Some machine readable 141 information in SMIv2 will be converted into textual descriptions in 142 SMIv1 during the translation process. However, this loss of machine 143 readable information is not considered to change the semantics of the 144 MIB. 146 2. Overview 148 This document defines a Management Information Base (MIB) for 149 monitoring and controlling the UNI/NNI Multilink Frame Relay 150 function. The agreement on which this MIB is based was defined and 151 documented by the Frame Relay Forum in the Frame Relay Forum Document 152 FRF.16 [FRF.16]. 154 2.1. Multilink Frame Relay Background 156 Multilink Frame Relay (MFR) for the User-to-Network Interface (UNI) 157 and the Network-to-Network Interface (NNI) provides physical 158 interface emulation for frame relay devices. The emulated physical 159 interface consists of one or more physical links, called "bundle 160 links", aggregated together into a single "bundle" of bandwidth. 161 This service provides a frame-based inverse multiplexing function, 162 sometimes referred to as an "IMUX". 164 The bundle provides the same order-preserving service as a physical 165 layer for frames sent on a data link connection. In addition, the 166 bundle provides support for all Frame Relay services based on UNI and 167 NNI standards. 169 2.1.1. Terminology 171 Physical Link -- A single physical interface that interconnects two 172 devices in a frame relay network (e.g. DS1, DS0, 173 Bearer channel, refer to FRF.14). 175 Bundle -- A grouping of one or more physical links using the 176 formats and procedures of multilink frame relay. 177 The bundle operates as a logical interface function 178 that emulates a single physical interface to the 179 Q.922 data link layer. 181 Bundle Link -- A MFR sub-component that controls operation of one 182 of the bundle's physical links. 184 2.1.2. Reference Model 186 +--------------------------+ +--------------------------+ 187 | Switching Layer -OR- | | Switching Layer -OR- | 188 | Higher-Level Applications| | Higher-Level Applications| 189 +--------------------------+ +--------------------------+ 190 | |C-Plane - Q.933| | |C-Plane - Q.933| 191 | U-Plane | (Note 1) | | U-Plane | (Note 1) | 192 | (Note 3) |---------------| | (Note 3) |---------------| 193 | |Q.922 (Note 2) | | |Q.922 (Note 2) | 194 +--------------------------+ +--------------------------+ 195 | Data Link Layer (Q.922) | | Data Link Layer (Q.922) | 196 +--------------------------+ +--------------------------+ 197 | Bundle (B) | | Bundle (B) | 198 +--------------------------+ +--------------------------+ 199 | Bundle | Bundle | Bundle | | Bundle | Bundle | Bundle | 200 | Link | Link | Link | | Link | Link | Link | 201 | (BL) | (BL) | (BL) | | (BL) | (BL) | (BL) | 202 +--------+--------+--------+ +--------+--------+--------+ 203 |Physical|Physical|Physical| |Physical|Physical|Physical| 204 | (PH) | (PH) | (PH) | __________ | (PH) | (PH) | (PH) | 205 +----+---+----+---+----+---+ /\ \ +----+---+----+---+----+---+ 206 | | | / \ \ | | | 207 | | +--------\ \-----+ | | 208 | | / \ \ | | 209 | +-------------------\ \------------+ | 210 | _________\_______/ Bundle /_ | 211 | /\ / / \ | 212 +------------| Bundle Link / / |------------------+ 213 \/_____________/ /____/ 214 \/__________/ 216 Figure 1: MFR Reference Diagram 218 Note 1: C-Plane operation as described in Q.933 [Q.933] and FRF.4 219 [FRF.4] 221 Note 2: Multiple frame acknowledged information fransfer mode as 222 described in Q.922 [Q.922] 224 Note 3: Core aspects for use with frame relay bearer service as 225 described in Q.922, Annex A [Q.922] 227 2.2. Structure of the MIB 229 The UNI/NNI MFR managed objects consist of two scalar objects and 230 three tables. 232 2.2.1. mfrBundleMaxNumBundles 234 This scalar is used to inform the manager of the maximum number of 235 bundles supported by this device. 237 2.2.2. mfrBundleNextIndex 239 This scalar is used to assist the manager in selecting a value for 240 mfrBundleIndex during row creation. It can also be used to avoid 241 race conditions with multiple managers trying to create rows in the 242 table (see RFC 2494 [RFC2494] for one such alogrithm). 244 2.2.3. mfrBundleTable 246 This table provides a means to configure and monitor bundles. It is 247 indexed by mfrBundleIndex and contains these columns: 249 - mfrBundleIndex Integer32 250 - mfrBundleIfIndex InterfaceIndex 251 - mfrBundleRowStatus RowStatus 252 - mfrBundleNearEndName SnmpAdminString 253 - mfrBundleFragmentation INTEGER 254 - mfrBundleMaxFragSize Integer32 255 - mfrBundleTimerHello INTEGER 256 - mfrBundleTimerAck INTEGER 257 - mfrBundleCountMaxRetry INTEGER 258 - mfrBundleActivationClass INTEGER 259 - mfrBundleThreshold Integer32 260 - mfrBundleMaxDiffDelay Integer32 261 - mfrBundleSeqNumSize INTEGER 262 - mfrBundleLinksConfigured Integer32 263 - mfrBundleLinksActive Integer32 264 - mfrBundleBandwidth Integer32 265 - mfrBundleFarEndName SnmpAdminString 266 - mfrBundleResequencingErrors Counter32 268 2.2.4. Bundle-to-ifIndex Mapping Table 270 This table provides a means to take an ifIndex and find the 271 corresponding mfrBundleIndex. It is indexed by ifIndex and contains 272 these columns: 274 - mfrBundleIfIndexMapping Integer32 276 2.2.5. mfrBundleLinkTable 278 This table provides a means to configure and monitor bundle links. 279 It is indexed by ifIndex and contains these columns: 281 - mfrBundleLinkRowStatus RowStatus 282 - mfrBundleLinkConfigBundleIndex Integer32 283 - mfrBundleLinkNearEndName SnmpAdminString 284 - mfrBundleLinkState MfrBundleLinkState 285 - mfrBundleLinkFarEndName SnmpAdminString 286 - mfrBundleLinkFarEndBundleName SnmpAdminString 287 - mfrBundleLinkDelay Integer32 288 - mfrBundleLinkFramesControlTx Counter32 289 - mfrBundleLinkFramesControlRx Counter32 290 - mfrBundleLinkFramesControlInvalid Counter32 291 - mfrBundleLinkTimerExpiredCount Counter32 292 - mfrBundleLinkLoopbackSuspected Counter32 293 - mfrBundleLinkUnexpectedSequence Counter32 294 - mfrBundleLinkMismatch Counter32 296 2.3. Relationship With Other MIBS and Tables 298 2.3.1. Relationship With Interface Table 300 2.3.1.1. Bundle Links 302 Each bundle link will appear as an interface in the ifTable. The 303 ifIndex that appears in the ifTable is used for indexing the bundle 304 link tables in the UNI-NNI MFR MIB. 306 2.3.1.2. Bundles 308 Each bundle will appear as an interface in the ifTable. There will 309 be corresponding mfrBundleIndex which may be different than the 310 ifIndex of the bundle. 312 The reason is best summarized in RFC 2494 [RFC2494], which describes 313 frame relay bundle of DS0. It says: 315 This table is not indexed by ifIndex because the manager has to 316 choose the index in a createable row and the agent must be 317 allowed to select ifIndex values. 319 The rows in the ifEntry table are not creatable as they do not have 320 row status. RFC 2863 [RFC2863] suggests that the ifIndex should be 321 chosen by the agent. Here is its statement regarding row creation 322 and deletion: 324 While some interfaces, for example, most physical interfaces, 325 cannot be created via network management, other interfaces such 326 as logical interfaces sometimes can be. The ifTable contains 327 only generic information about an interface. Almost all 328 'create-able' interfaces have other, media-specific, information 329 through which configuration parameters may be supplied prior to 330 creating such an interface. Thus, the ifTable does not itself 331 support the creation or deletion of an interface (specifically, 332 it has no RowStatus column). Rather, if a particular interface 333 type supports the dynamic creation and/or deletion of an 334 interface of that type, then that media-specific MIB should 335 include an appropriate RowStatus object (see the ATM LAN- 336 Emulation Client MIB [ATMLANE] for an example of a MIB which 337 does this). Typically, when such a RowStatus object is 338 created/deleted, then the conceptual row in the ifTable 339 appears/disappears as a by-product, and an ifIndex value (chosen 340 by the agent) is stored in an appropriate object in the media- 341 specific MIB. 343 The ATM LAN-Emulation Client MIB [ATMLANE] uses different indices and 344 so does the IMA MIB [ATMIMA]. Looking at the examples we have, and 345 the statements from RFC, it seems better to have two indices. This 346 gives the SNMP agent implementor the freedom to manage their ifIndex 347 in the way they like. 349 2.3.1.3. Mapping Between ifIndex and mfrBundleIndex 351 The mfrBundleIfIndexMappingTable is indexed by ifIndex and provides 352 the means to map a given ifIndex into the corresponding 353 mfrBundleIndex. The mfrBundleIfIndexMapping object in the 354 mfrBundleTable (indexed by mfrBundleIndex) provides the reverse 355 mapping of a mfrBundleIndex to the corresponding ifIndex in the 356 ifTable. 358 2.3.1.4. ifTable Objects 360 The bundle configuration and status table. There is a one-to-one 361 correspondence between a bundle and an interface represented in the 362 ifTable. 364 The following objects of the ifTable have specific meaning for an MFR 365 bundle: 367 ifAdminStatus - the bundle admin status 368 ifOperStatus - the bundle operational status 369 ifSpeed - the current bandwidth of the bundle 370 ifInUcastPkts - the number of frames received on the bundle 371 ifOutUcastPkts - the number of frames transmitted on the bundle 372 ifInErrors - frame (not fragment) errors 373 ifOutErrors - frame (not fragment) errors 375 The following objects of the ifTable have specific meaning for an MFR 376 bundle link: 378 ifAdminStatus - the bundle link admin status 379 ifOperStatus - the bundle link operational status 380 ifSpeed - the bandwidth of the bundle link interface 381 ifInUcastPkts - the number of frames received on the bundle link 382 ifOutUcastPkts - the number of frames transmitted on the bundle 383 link 384 ifInErrors - frame and fragment errors 385 ifOutErrors - frame and fragment errors 387 2.3.2. Relationship With Interface Stack Table 389 The bundles and bundle links will appear in the ifStackTable defined 390 in RFC 2863 [RFC2863]. Each bundle link will appear a lower layer to 391 its owner bundle. The bundle will appear as a higher layer to the 392 bundle links and as a lower layer to a frame relay service or UNI. 394 2.3.3. Relationship With Frame Relay DTE MIB 396 The bundle will have a one-to-one correspondence with a DLCMI or UNI 397 that appear in the DTE MIB tables [RFC2115]. 399 2.3.4. Relationship With Frame Relay Service MIB 401 There is a one-to-one relationship between the MFR bundle and the 402 frame relay service logical port defined in RFC1604 [RFC1604]. 404 2.3.5. Example 406 Figure two shows an example of how the various tables are related. 407 This example shows two bundles composed of 2 T1s each. The bundles 408 have a mfrBundleIndex of 10 and 20 respectively. 410 +-------------------------+ 411 | Frame Relay Service | 412 +-----+-------------+-----+ 413 | | 414 +-----+------+------+-----+ 415 | MFR Bundle | MFR Bundle | 416 | 10 | 20 | 417 +--+-----+---+---+-----+--+ 418 | | | | 419 +-+-+ +-+-+ +-+-+ +-+-+ 420 |T1 | |T1 | |T1 | |T1 | 421 +---+ +---+ +-+-+ +---+ 423 Figure 2: Frame Relay Service Being Carried on 4 T1s 425 The assignment of the ifTable index values could for example be: 427 ifIndex | Description | ifType 428 --------+----------------------------+---------------------- 429 1 | FrameRelayService | frameRelayService(44) 430 2 | MFR Bundle #10 | frf16MfrBundle(163) 431 3 | MFR Bundle #20 | frf16MfrBundle(163) 432 4 | ds1 #1/MFR Bundle Link #1 | ds1(18) 433 5 | ds1 #2/MFR Bundle Link #2 | ds1(18) 434 6 | ds1 #3/MFR Bundle Link #3 | ds1(18) 435 7 | ds1 #4/MFR Bundle Link #4 | ds1(18) 437 The ifStackTable is then used to show the relationships between the 438 various interfaces. 440 HigherLayer | LowerLayer 441 ------------+----------- 442 0 | 1 443 1 | 2 444 1 | 3 445 2 | 4 446 2 | 5 447 3 | 6 448 3 | 7 449 4 | 0 450 5 | 0 451 6 | 0 452 7 | 0 454 The mfrBundleIfIndexMappingTable shows the relationship between the 455 ifTable ifIndex and the mfrBundleIndex: 457 ifIndex | mfrBundleIfIndexMappingIndex 458 --------+----------------------------- 459 2 | 10 460 3 | 20 462 The mfrBundleTable shows the relationship between the mfrBundleIndex 463 and the ifIndex: 465 mfrBundleIndex | mfrBundleIfIndex 466 ---------------+----------------- 467 10 | 2 468 20 | 3 470 The mfrBundleLinkTable shows the relationship between the bundles and 471 bundle links: 473 mfrBundleIndex | mfrBundleLinkIfIndex 474 ---------------+--------------------- 475 10 | 4 476 10 | 5 477 20 | 6 478 20 | 7 480 2.4. Creation Of Bundles and Bundle Links 482 2.4.1. Creation Of Bundles 484 A new bundle is created by setting a createAndGo(4) value in the 485 mfrBundleRowStatus RowStatus object. Optionally, an agent could also 486 support setting a value of createAndWait(5) followed by a set to the 487 value active(1). 489 When a bundle is created, the agent must create a new interface in 490 the ifTable. The ifIndex for this new interface is used for the 491 value of mfrBundleIfIndex. 493 2.4.2. Creation Of Bundle Links 495 A new bundle link is created by setting a createAndGo(4) value in the 496 mfrBundleLinkRowStatus RowStatus object. 498 The bundle link is associated with a specific physical interface and 499 uses the ifIndex of the physical interface. The mfrBundleLinkEntry 500 row objects may be created after or during creation of the physical 501 interface's ifEntry row objects. 503 The bundle identified in the object mfrBundleIndex must exist at time 504 of bundle link creation. 506 2.5. Notifications 508 The linkUp and linkDown traps are defined in RFC 2223 [RFC2223]. 510 2.5.1. Bundle 512 The following SNMP traps are defined for MFR bundles. 514 2.5.1.1. linkUp 516 This trap is sent when the ifOperStatus of a bundle transitions from 517 down to up. This occurs when a sufficient number of links 518 (determined by mfrBundleActivationClass and mfrBundleThreshold) are 519 in the operationally up state. 521 2.5.1.2. linkDown 523 This trap is sent when the ifOperStatus of a bundle transitions from 524 up to down. This occurs when a insufficient number of links 525 (determined by mfrBundleActivationClass and mfrBundleThreshold) are 526 in the operationally up state. 528 2.5.2. Bundle Link 530 The following SNMP traps are defined for MFR bundle links. 532 2.5.2.1. linkUp 534 This trap is sent when a mfrBundleLinkState object transitions to the 535 value mfrBundleLinkStateUp. 537 2.5.2.2. linkDown 539 This trap is sent when a mfrBundleLinkState object transitions from 540 the value mfrBundleLinkStateUp. 542 2.5.2.3. mfrMibTrapBundleLinkMismatch 544 This trap indicates that a bundle link mismatch has been detected. 545 The following objects are reported: 547 - mfrBundleNearEndName: configured name of near end bundle 548 - mfrBundleFarEndName: previously reported name of far 549 end bundle 550 - mfrBundleLinkNearEndName: configured name of near end bundle 551 - mfrBundleLinkFarEndName: reported name of far end bundle 552 - mfrBundleLinkFarEndBundleName: currently reported name of far 553 end bundle 555 Note that the configured items may have been configured 556 automatically. Note also that the mfrBundleLinkMismatch counter is 557 incremented when the trap is sent. 559 3. Object Definitions 561 Managed objects are accessed via a virtual information store, termed 562 the Management Information Base or MIB. Objects in the MIB are 563 defined using the subset of Abstract Syntax Notation One (ASN.1) 564 defined in the SMI. In particular, each object type is named by an 565 OBJECT IDENTIFIER, an administratively assigned name. The object 566 type together with an object instance serves to uniquely identify a 567 specific instantiation of the object. For human convenience, we 568 often use a textual string, termed the descriptor, to refer to the 569 object type. 571 FR-MFR-MIB DEFINITIONS ::= BEGIN 573 IMPORTS 574 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, 575 NOTIFICATION-TYPE, transmission 576 FROM SNMPv2-SMI 577 TEXTUAL-CONVENTION, TestAndIncr, RowStatus 578 FROM SNMPv2-TC 579 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 580 FROM SNMPv2-CONF 581 SnmpAdminString 582 FROM SNMP-FRAMEWORK-MIB 583 InterfaceIndex, ifIndex 584 FROM IF-MIB; 586 mfrMib MODULE-IDENTITY 587 LAST-UPDATED "200010020000Z" 588 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) 589 Working Group" 590 CONTACT-INFO 591 "WG Charter: 592 http://www.ietf.org/html.charters/frnetmib-charter.html 593 WG-email: frnetmib@sunroof.eng.sun.com 594 Subscribe: frnetmib-request@sunroof.eng.sun.com 595 Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib 597 Chair: Andy Malis 598 Vivace Networks 599 Email: Andy.Malis@vivacenetworks.com 601 WG editor: Prayson Pate 602 Overture Networks 603 Email: prayson.pate@overturenetworks.com 605 Co-author: Bob Lynch 606 Larscom Incorporated 607 EMail: blynch@larscom.com 608 Co-author: Kenneth Rehbehn 609 Megisto Systems, Inc. 610 EMail: krehbehn@megisto.com" 612 DESCRIPTION 613 "This is the MIB used to control and monitor the multilink 614 frame relay (MFR) function described in FRF.16." 616 -- --------------------------------------------------------- 617 -- --------------------------------------------------------- 618 -- Revision History 619 -- --------------------------------------------------------- 620 -- --------------------------------------------------------- 622 REVISION "200010020000Z" 623 DESCRIPTION 624 "Published as RFC [RFC-EDITOR: Enter RFC # here]." 626 ::= { transmission xx } -- xx to be assigned by IANA 628 -- --------------------------------------------------------- 629 -- --------------------------------------------------------- 630 -- Textual Conventions 631 -- --------------------------------------------------------- 632 -- --------------------------------------------------------- 634 MfrBundleLinkState ::= TEXTUAL-CONVENTION 635 STATUS current 636 DESCRIPTION 637 "The possible states for a bundle link, as defined in 638 Annex A of FRF.16." 639 REFERENCE "FRF.16 Annex A" 640 SYNTAX INTEGER { 641 mfrBundleLinkStateAddSent (1), 642 mfrBundleLinkStateAddRx (2), 643 mfrBundleLinkStateAddAckRx (3), 644 mfrBundleLinkStateUp (4), 645 mfrBundleLinkStateIdlePending (5), 646 mfrBundleLinkStateIdle (6), 647 mfrBundleLinkStateDown (7), 648 mfrBundleLinkStateDownIdle (8) 649 } 651 -- --------------------------------------------------------- 652 -- --------------------------------------------------------- 653 -- Object Identifers 654 -- --------------------------------------------------------- 655 -- --------------------------------------------------------- 656 mfrMibScalarObjects OBJECT IDENTIFIER ::= { mfrMib 1 } 657 mfrMibBundleObjects OBJECT IDENTIFIER ::= { mfrMib 2 } 658 mfrMibBundleLinkObjects OBJECT IDENTIFIER ::= { mfrMib 3 } 659 mfrMibTraps OBJECT IDENTIFIER ::= { mfrMib 4 } 660 mfrMibConformance OBJECT IDENTIFIER ::= { mfrMib 5 } 662 mfrMibTrapsPrefix OBJECT IDENTIFIER ::= { mfrMibTraps 0 } 664 mfrMibGroups OBJECT IDENTIFIER ::= { mfrMibConformance 1 } 665 mfrMibCompliances OBJECT IDENTIFIER ::= { mfrMibConformance 2 } 667 -- --------------------------------------------------------- 668 -- --------------------------------------------------------- 669 -- Scalars 670 -- --------------------------------------------------------- 671 -- --------------------------------------------------------- 673 mfrBundleMaxNumBundles OBJECT-TYPE 674 SYNTAX Integer32 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "This object is used to inform the manager of the 679 maximum number of bundles supported by this device." 680 ::= { mfrMibScalarObjects 1 } 682 mfrBundleNextIndex OBJECT-TYPE 683 SYNTAX TestAndIncr 684 MAX-ACCESS read-write 685 STATUS current 686 DESCRIPTION 687 "This object is used to assist the manager in 688 selecting a value for mfrBundleIndex during row creation 689 in the mfrBundleTable. It can also be used to avoid race 690 conditions with multiple managers trying to create 691 rows in the table (see RFC 2494 [RFC2494] for one such 692 alogrithm)." 693 REFERENCE "RFC 2494" 694 ::= { mfrMibScalarObjects 2 } 696 -- --------------------------------------------------------- 697 -- --------------------------------------------------------- 698 -- Bundle Table 699 -- --------------------------------------------------------- 700 -- --------------------------------------------------------- 702 mfrBundleTable OBJECT-TYPE 703 SYNTAX SEQUENCE OF MfrBundleEntry 704 MAX-ACCESS not-accessible 705 STATUS current 706 DESCRIPTION 707 "The bundle configuration and status table. There 708 is a one-to-one correspondence between a bundle 709 and an interface represented in the ifTable. 711 The following objects of the ifTable have specific 712 meaning for an MFR bundle: 713 ifAdminStatus - the bundle admin status 714 ifOperStatus - the bundle operational status 715 ifSpeed - the current bandwidth of the bundle 716 ifInUcastPkts - the number of frames received 717 on the bundle 718 ifOutUcastPkts - the number of frames transmitted 719 on the bundle 720 ifInErrors - frame (not fragment) errors 721 ifOutErrors - frame (not fragment) errors 722 " 723 ::= { mfrMibBundleObjects 3 } 725 mfrBundleEntry OBJECT-TYPE 726 SYNTAX MfrBundleEntry 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "An entry in the bundle table." 731 INDEX { mfrBundleIndex } 732 ::= { mfrBundleTable 1 } 734 MfrBundleEntry ::= 735 SEQUENCE { 736 mfrBundleIndex 737 Integer32, 738 mfrBundleIfIndex 739 InterfaceIndex, 740 mfrBundleRowStatus 741 RowStatus, 742 mfrBundleNearEndName 743 SnmpAdminString, 744 mfrBundleFragmentation 745 INTEGER, 746 mfrBundleMaxFragSize 747 Integer32, 748 mfrBundleTimerHello 749 INTEGER, 750 mfrBundleTimerAck 751 INTEGER, 752 mfrBundleCountMaxRetry 753 INTEGER, 755 mfrBundleActivationClass 756 INTEGER, 757 mfrBundleThreshold 758 Integer32, 759 mfrBundleMaxDiffDelay 760 Integer32, 761 mfrBundleSeqNumSize 762 INTEGER, 763 mfrBundleMaxBundleLinks 764 Integer32, 765 mfrBundleLinksConfigured 766 Integer32, 767 mfrBundleLinksActive 768 Integer32, 769 mfrBundleBandwidth 770 Integer32, 771 mfrBundleFarEndName 772 SnmpAdminString, 773 mfrBundleResequencingErrors 774 Counter32 775 } 777 mfrBundleIndex OBJECT-TYPE 778 SYNTAX Integer32 (1..2147483647) 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "The index into the table. While this corresponds 783 to an entry in the ifTable, the value of mfrBundleIndex 784 need not match that of the ifIndex in the ifTable. 785 A manager can use mfrBundleNextIndex to select a unique 786 mfrBundleIndex for creating a new row." 787 ::= { mfrBundleEntry 1 } 789 mfrBundleIfIndex OBJECT-TYPE 790 SYNTAX InterfaceIndex 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "The value must match an entry in the interface 795 table whose ifType must be set to frf16MfrBundle(163). 797 For example: if the value of mfrBundleIfIndex is 10, 798 then a corresponding entry should be present in 799 the ifTable with an index of 10 and an ifType of 163." 800 ::= { mfrBundleEntry 2 } 802 mfrBundleRowStatus OBJECT-TYPE 803 SYNTAX RowStatus 804 MAX-ACCESS read-create 805 STATUS current 806 DESCRIPTION 807 "The mfrBundleRowStatus object allows create, change, 808 and delete operations on bundle entries." 809 REFERENCE "RFC 1903" 810 ::= { mfrBundleEntry 3 } 812 mfrBundleNearEndName OBJECT-TYPE 813 SYNTAX SnmpAdminString 814 MAX-ACCESS read-create 815 STATUS current 816 DESCRIPTION 817 "The configured name of the bundle." 818 REFERENCE "FRF.16 section 3.4.1" 819 ::= { mfrBundleEntry 4 } 821 mfrBundleFragmentation OBJECT-TYPE 822 SYNTAX INTEGER { 823 enable (1), 824 disable (2) 825 } 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "Controls whether the bundle performs/accepts 830 fragmentation and re-assembly. The possible 831 values are: 833 enable(1) - Bundle links will fragment frames 835 disable(2) - Bundle links will not fragment 836 frames." 837 DEFVAL { disable } 838 ::= { mfrBundleEntry 5 } 840 mfrBundleMaxFragSize OBJECT-TYPE 841 SYNTAX Integer32 (-1..8184) 842 UNITS "Octets" 843 MAX-ACCESS read-create 844 STATUS current 845 DESCRIPTION 846 "The maximum fragment size supported. Note that this 847 is only valid if mfrBundleFragmentation is set to enable(1). 849 Zero is not a valid fragment size. 851 A bundle that does not support fragmentation must return 852 this object with a value of -1." 854 DEFVAL { -1 } 855 ::= { mfrBundleEntry 6 } 857 mfrBundleTimerHello OBJECT-TYPE 858 SYNTAX INTEGER (1..180) 859 UNITS "Seconds" 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "The configured MFR Hello Timer value." 864 REFERENCE "FRF.16 section 4.3.8.1" 865 DEFVAL { 10 } 866 ::= { mfrBundleEntry 7 } 868 mfrBundleTimerAck OBJECT-TYPE 869 SYNTAX INTEGER (1..10) 870 UNITS "Seconds" 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "The configured MFR T_ACK value." 875 REFERENCE "FRF.16 section 4.3.8.2" 876 DEFVAL { 4 } 877 ::= { mfrBundleEntry 8 } 879 mfrBundleCountMaxRetry OBJECT-TYPE 880 SYNTAX INTEGER (1..5) 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "The MFR N_MAX_RETRY value." 885 REFERENCE "FRF.16 section 4.3.8.3" 886 DEFVAL { 2 } 887 ::= { mfrBundleEntry 9 } 889 mfrBundleActivationClass OBJECT-TYPE 890 SYNTAX INTEGER { 891 mfrBundleActivationClassA (1), 892 mfrBundleActivationClassB (2), 893 mfrBundleActivationClassC (3), 894 mfrBundleActivationClassD (4) 895 } 896 MAX-ACCESS read-create 897 STATUS current 898 DESCRIPTION 899 "Controls the conditions under which the bundle is activated. 900 The following settings are available: 902 mfrBundleActivationClassA(1) - at least one must link up 903 mfrBundleActivationClassB(2) - all links must be up 904 mfrBundleActivationClassC(3) - a certain number must be 905 up. Refer to 906 mfrBundleThreshold for 907 the required number. 908 mfrBundleActivationClassD(4) - custom (implementation 909 specific)." 910 REFERENCE "FRF.16 section 4.2.2.1" 911 DEFVAL { mfrBundleActivationClassA } 912 ::= { mfrBundleEntry 10 } 914 mfrBundleThreshold OBJECT-TYPE 915 SYNTAX Integer32 (-1..2147483647) 916 UNITS "Bundle Links" 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "Specifies the number of links that must be in operational 921 'up' state before the bundle will transition to an 922 operational up/active state. If the number of 923 operational 'up' links falls below this value, 924 then the bundle will transition to an inactive 925 state. 927 Note - this is only valid when mfrBundleActivationClass 928 is set to mfrBundleActivationClassC or, depending upon the 929 implementation, to mfrBundleActivationClassD. A bundle that 930 is not set to one of these must return this object with a 931 value of -1." 932 REFERENCE "FRF.16 section 4.2.2.1" 933 DEFVAL { -1 } 934 ::= { mfrBundleEntry 11 } 936 mfrBundleMaxDiffDelay OBJECT-TYPE 937 SYNTAX Integer32 (-1..2147483647) 938 UNITS "Milliseconds" 939 MAX-ACCESS read-create 940 STATUS current 941 DESCRIPTION 942 "The maximum delay difference between the bundle 943 links. 945 A value of -1 indicates that this object does not contain 946 a valid value" 947 DEFVAL { -1 } 948 ::= { mfrBundleEntry 12 } 950 mfrBundleSeqNumSize OBJECT-TYPE 951 SYNTAX INTEGER { 952 seqNumSize12bit (1), 953 seqNumSize24bit (2) 954 } 955 MAX-ACCESS read-create 956 STATUS current 957 DESCRIPTION 958 "Controls whether the standard FRF.12 12-bit 959 sequence number is used or the optional 24-bit 960 sequence number." 961 REFERENCE "FRFTC/99-194" 962 DEFVAL { seqNumSize12bit } 963 ::= { mfrBundleEntry 13 } 965 mfrBundleMaxBundleLinks OBJECT-TYPE 966 SYNTAX Integer32 (1..2147483647) 967 UNITS "Bundle Links" 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The maximum number of bundle links supported for 972 this bundle." 973 ::= { mfrBundleEntry 14 } 975 mfrBundleLinksConfigured OBJECT-TYPE 976 SYNTAX Integer32 (1..2147483647) 977 UNITS "Bundle Links" 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "The number of links configured for the bundle." 982 ::= { mfrBundleEntry 15 } 984 mfrBundleLinksActive OBJECT-TYPE 985 SYNTAX Integer32 (-1..2147483647) 986 UNITS "Bundle Links" 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "The number of links that are active." 991 ::= { mfrBundleEntry 16 } 993 mfrBundleBandwidth OBJECT-TYPE 994 SYNTAX Integer32 995 UNITS "Bits/Sec" 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "The amount of available bandwidth on the bundle" 1000 ::= { mfrBundleEntry 17 } 1002 mfrBundleFarEndName OBJECT-TYPE 1003 SYNTAX SnmpAdminString 1004 MAX-ACCESS read-only 1005 STATUS current 1006 DESCRIPTION 1007 "Name of the bundle received from the far end." 1008 REFERENCE "FRF.16 section 3.4.1" 1009 ::= { mfrBundleEntry 18 } 1011 mfrBundleResequencingErrors OBJECT-TYPE 1012 SYNTAX Counter32 1013 UNITS "Error Events" 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "A count of the number of resequncing errors. Each event 1018 may correspond to multiple lost frames. Example: 1019 Say sequence number 56, 59 and 60 is received for DLCI 100. 1020 It is decided by some means that sequence 57 and 58 is lost. 1021 This counter should then be incremented by ONE, even though 1022 two frames were lost." 1023 ::= { mfrBundleEntry 19 } 1025 -- --------------------------------------------------------- 1026 -- --------------------------------------------------------- 1027 -- ifIndex Mapping to Bundle Index Table 1028 -- --------------------------------------------------------- 1029 -- --------------------------------------------------------- 1031 mfrBundleIfIndexMappingTable OBJECT-TYPE 1032 SYNTAX SEQUENCE OF MfrBundleIfIndexMappingEntry 1033 MAX-ACCESS not-accessible 1034 STATUS current 1035 DESCRIPTION 1036 "A table mapping the values of ifIndex to the 1037 mfrBundleIndex. This is required in order to find 1038 the mfrBundleIndex given an ifIndex. The mapping of 1039 mfrBundleIndex to ifIndex is provided by the 1040 mfrBundleIfIndex entry in the mfrBundleTable." 1041 ::= { mfrMibBundleObjects 4 } 1043 mfrBundleIfIndexMappingEntry OBJECT-TYPE 1044 SYNTAX MfrBundleIfIndexMappingEntry 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION 1048 "Each row describes one ifIndex to mfrBundleIndex mapping." 1049 INDEX { ifIndex } 1050 ::= { mfrBundleIfIndexMappingTable 1 } 1052 MfrBundleIfIndexMappingEntry ::= 1053 SEQUENCE { 1054 mfrBundleIfIndexMappingIndex 1055 Integer32 1056 } 1058 mfrBundleIfIndexMappingIndex OBJECT-TYPE 1059 SYNTAX Integer32 (1..2147483647) 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "The mfrBundleIndex of the given ifIndex." 1064 ::= { mfrBundleIfIndexMappingEntry 2 } 1066 -- --------------------------------------------------------- 1067 -- --------------------------------------------------------- 1068 -- Bundle Link Table 1069 -- --------------------------------------------------------- 1070 -- --------------------------------------------------------- 1072 mfrBundleLinkTable OBJECT-TYPE 1073 SYNTAX SEQUENCE OF MfrBundleLinkEntry 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "The bundle link configuration and status table. There 1078 is a one-to-one correspondence between a bundle link 1079 and a physical interface represented in the ifTable. The 1080 ifIndex of the physical interface is used to index the 1081 bundle link table, and to create rows. 1083 The following objects of the ifTable have specific 1084 meaning for an MFR bundle link: 1086 ifAdminStatus - the bundle link admin status 1087 ifOperStatus - the bundle link operational 1088 status 1089 ifSpeed - the bandwidth of the bundle 1090 link interface 1091 ifInUcastPkts - the number of frames received 1092 on the bundle link 1093 ifOutUcastPkts - the number of frames transmitted 1094 on the bundle link 1095 ifInErrors - frame and fragment errors 1096 ifOutErrors - frame and fragment errors" 1097 ::= { mfrMibBundleLinkObjects 1 } 1099 mfrBundleLinkEntry OBJECT-TYPE 1100 SYNTAX MfrBundleLinkEntry 1101 MAX-ACCESS not-accessible 1102 STATUS current 1103 DESCRIPTION 1104 "An entry in the bundle link table." 1105 INDEX { ifIndex } 1106 ::= { mfrBundleLinkTable 1 } 1108 MfrBundleLinkEntry ::= 1109 SEQUENCE { 1110 mfrBundleLinkRowStatus 1111 RowStatus, 1112 mfrBundleLinkConfigBundleIndex 1113 Integer32, 1114 mfrBundleLinkNearEndName 1115 SnmpAdminString, 1116 mfrBundleLinkState 1117 MfrBundleLinkState, 1118 mfrBundleLinkFarEndName 1119 SnmpAdminString, 1120 mfrBundleLinkFarEndBundleName 1121 SnmpAdminString, 1122 mfrBundleLinkDelay 1123 Integer32, 1124 mfrBundleLinkFramesControlTx 1125 Counter32, 1126 mfrBundleLinkFramesControlRx 1127 Counter32, 1128 mfrBundleLinkFramesControlInvalid 1129 Counter32, 1130 mfrBundleLinkTimerExpiredCount 1131 Counter32, 1132 mfrBundleLinkLoopbackSuspected 1133 Counter32, 1134 mfrBundleLinkUnexpectedSequence 1135 Counter32, 1136 mfrBundleLinkMismatch 1137 Counter32 1138 } 1140 mfrBundleLinkRowStatus OBJECT-TYPE 1141 SYNTAX RowStatus 1142 MAX-ACCESS read-create 1143 STATUS current 1144 DESCRIPTION 1145 "The mfrBundleLinkRowStatus object allows create, change, 1146 and delete operations on mfrBundleLink entries. 1148 The create operation must fail if no physical interface 1149 is associated with the bundle link." 1151 ::= { mfrBundleLinkEntry 1 } 1153 mfrBundleLinkConfigBundleIndex OBJECT-TYPE 1154 SYNTAX Integer32 (1..2147483647) 1155 MAX-ACCESS read-create 1156 STATUS current 1157 DESCRIPTION 1158 "The mfrBundleLinkConfigBundleIndex object allows 1159 the manager to control the bundle to which the bundle 1160 link is assigned. If no value were in this field, then 1161 the bundle would remain in NOT_READY rowStatus and be 1162 unable to go to active. With an appropriate mfrBundleIndex 1163 in this field, then we could put the mfrBundleLink row in 1164 NOT_IN_SERVICE or ACTIVE rowStatus." 1165 ::= { mfrBundleLinkEntry 2 } 1167 mfrBundleLinkNearEndName OBJECT-TYPE 1168 SYNTAX SnmpAdminString 1169 MAX-ACCESS read-create 1170 STATUS current 1171 DESCRIPTION 1172 "The configured bundle link name that is sent to the far end." 1173 ::= { mfrBundleLinkEntry 3 } 1175 mfrBundleLinkState OBJECT-TYPE 1176 SYNTAX MfrBundleLinkState 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "Current bundle link state as defined by the MFR protocol 1181 described in Annex A of FRF.16." 1182 REFERENCE "FRF.16 Annex A" 1183 ::= { mfrBundleLinkEntry 4 } 1185 mfrBundleLinkFarEndName OBJECT-TYPE 1186 SYNTAX SnmpAdminString 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "Name of bundle link received from far end." 1191 REFERENCE "FRF.16 section 3.4.2" 1192 ::= { mfrBundleLinkEntry 5 } 1194 mfrBundleLinkFarEndBundleName OBJECT-TYPE 1195 SYNTAX SnmpAdminString 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "Name of far end bundle for this link received from far end." 1201 REFERENCE "FRF.16 section 3.4.1" 1202 ::= { mfrBundleLinkEntry 6 } 1204 mfrBundleLinkDelay OBJECT-TYPE 1205 SYNTAX Integer32 (-1..2147483647) 1206 UNITS "Milliseconds" 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "Current round-trip delay for this bundle link. The 1211 value -1 is returned when an implementation does not 1212 support measurement of the bundle link delay." 1213 REFERENCE "FRF.16 section 3.4.4" 1214 ::= { mfrBundleLinkEntry 7 } 1216 mfrBundleLinkFramesControlTx OBJECT-TYPE 1217 SYNTAX Counter32 1218 UNITS "Frames" 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "Number of MFR control frames sent." 1223 REFERENCE "FRF.16 section 3.2" 1224 ::= { mfrBundleLinkEntry 8 } 1226 mfrBundleLinkFramesControlRx OBJECT-TYPE 1227 SYNTAX Counter32 1228 UNITS "Frames" 1229 MAX-ACCESS read-only 1230 STATUS current 1231 DESCRIPTION 1232 "Number of valid MFR control frames received." 1233 REFERENCE "FRF.16 section 3.2" 1234 ::= { mfrBundleLinkEntry 9 } 1236 mfrBundleLinkFramesControlInvalid OBJECT-TYPE 1237 SYNTAX Counter32 1238 UNITS "Frames" 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "The number of invalid MFR control frames received." 1243 REFERENCE "FRF.16 section 3.2" 1244 ::= { mfrBundleLinkEntry 10 } 1246 mfrBundleLinkTimerExpiredCount OBJECT-TYPE 1247 SYNTAX Counter32 1248 UNITS "Timer Expiration Events" 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "Number of times the T_HELLO or T_ACK timers expired." 1253 REFERENCE "FRF.16 section 4.3.8.1 and 4.3.8.2" 1254 ::= { mfrBundleLinkEntry 11 } 1256 mfrBundleLinkLoopbackSuspected OBJECT-TYPE 1257 SYNTAX Counter32 1258 UNITS "Loopback Suspected Events" 1259 MAX-ACCESS read-only 1260 STATUS current 1261 DESCRIPTION 1262 "The number of times a loopback has been suspected 1263 (based upon the use of magic numbers)." 1264 REFERENCE "FRF.16 section 4.3.7" 1265 ::= { mfrBundleLinkEntry 12 } 1267 mfrBundleLinkUnexpectedSequence OBJECT-TYPE 1268 SYNTAX Counter32 1269 UNITS "Frames" 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The number of data MFR frames discarded because the sequence 1274 number of the frame for a DLCI was less than (delayed frame) 1275 or equal to (duplicate frame) the one expected for that DLCI. 1277 Example: 1278 Say frames with sequence numbers 56, 58, 59 is received for 1279 DLCI 100. While waiting for sequence number 57 another frame 1280 with sequence number 58 arrives. Frame 58 is discarded and 1281 the counter is incremented." 1282 REFERENCE "FRF.16 section 4.2.3.2" 1283 ::= { mfrBundleLinkEntry 13 } 1285 mfrBundleLinkMismatch OBJECT-TYPE 1286 SYNTAX Counter32 1287 UNITS "Bundle Name Mismatch Events" 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The number of times that the unit has been notified by the 1292 remote peer that the bundle name is inconsistent with other 1293 bundle links attached to the far-end bundle." 1294 REFERENCE "FRF.16 section 4.3.2.4" 1295 ::= { mfrBundleLinkEntry 14 } 1297 -- --------------------------------------------------------- 1298 -- --------------------------------------------------------- 1299 -- Notifications/Traps 1300 -- --------------------------------------------------------- 1301 -- --------------------------------------------------------- 1303 mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE 1304 OBJECTS { 1305 mfrBundleNearEndName, 1306 mfrBundleFarEndName, 1307 mfrBundleLinkNearEndName, 1308 mfrBundleLinkFarEndName, 1309 mfrBundleLinkFarEndBundleName 1310 } 1311 STATUS current 1312 DESCRIPTION 1313 "This trap indicates that a bundle link mismatch has 1314 been detected. The following objects are reported: 1316 mfrBundleNearEndName: configured name of near end bundle 1318 mfrBundleFarEndName: previously reported name of 1319 far end bundle 1321 mfrBundleLinkNearEndName: configured name of near end bundle 1323 mfrBundleLinkFarEndName: reported name of far end bundle 1325 mfrBundleLinkFarEndBundleName: currently reported name of 1326 far end bundle 1328 Note: that the configured items may have been configured 1329 automatically. 1331 Note: The mfrBundleLinkMismatch counter is incremented when 1332 the trap is sent." 1333 REFERENCE "FRF.16 section 4.3.2.4" 1334 ::= { mfrMibTrapsPrefix 1 } 1336 -- --------------------------------------------------------- 1337 -- --------------------------------------------------------- 1338 -- Conformance/Compliance 1339 -- --------------------------------------------------------- 1340 -- --------------------------------------------------------- 1342 mfrMibCompliance MODULE-COMPLIANCE 1343 STATUS current 1344 DESCRIPTION 1345 "The compliance statement for equipment that implements 1346 the FRF16 MIB. All of the current groups are mandatory, 1347 but a number of objects may be read-only if the 1348 implementation does not allow configuration." 1349 MODULE -- this module 1350 MANDATORY-GROUPS { 1351 mfrMibBundleGroup, 1352 mfrMibBundleLinkGroup, 1353 mfrMibTrapGroup 1354 } 1356 OBJECT mfrBundleFragmentation 1357 MIN-ACCESS read-only 1358 DESCRIPTION 1359 "Write access is not required, but the value used must be 1360 reported." 1362 OBJECT mfrBundleMaxFragSize 1363 MIN-ACCESS read-only 1364 DESCRIPTION 1365 "Write access is not required, but the value used must be 1366 reported. 1367 A value of -1 indicates that the value is not applicable." 1369 OBJECT mfrBundleThreshold 1370 MIN-ACCESS read-only 1371 DESCRIPTION 1372 "Write access is not required, but the value used must be 1373 reported. 1374 A value of -1 indicates that the value is not applicable." 1376 OBJECT mfrBundleMaxDiffDelay 1377 MIN-ACCESS read-only 1378 DESCRIPTION 1379 "Write access is not required, but the value used must be 1380 reported." 1382 OBJECT mfrBundleSeqNumSize 1383 MIN-ACCESS read-only 1384 DESCRIPTION 1385 "Write access is not required, but the value used must be 1386 reported. 1387 A value of -1 indicates that the value is not applicable." 1389 ::= { mfrMibCompliances 1 } 1391 -- --------------------------------------------------------- 1392 -- --------------------------------------------------------- 1393 -- Units of Conformance 1394 -- --------------------------------------------------------- 1395 -- --------------------------------------------------------- 1396 mfrMibBundleGroup OBJECT-GROUP 1397 OBJECTS { 1398 mfrBundleMaxNumBundles, 1399 mfrBundleNextIndex, 1400 mfrBundleIfIndex, 1401 mfrBundleRowStatus, 1402 mfrBundleNearEndName, 1403 mfrBundleFragmentation, 1404 mfrBundleMaxFragSize, 1405 mfrBundleTimerHello, 1406 mfrBundleTimerAck, 1407 mfrBundleCountMaxRetry, 1408 mfrBundleActivationClass, 1409 mfrBundleThreshold, 1410 mfrBundleMaxDiffDelay, 1411 mfrBundleMaxBundleLinks, 1412 mfrBundleLinksConfigured, 1413 mfrBundleLinksActive, 1414 mfrBundleBandwidth, 1415 mfrBundleSeqNumSize, 1416 mfrBundleFarEndName, 1417 mfrBundleResequencingErrors, 1418 mfrBundleIfIndexMappingIndex 1419 } 1420 STATUS current 1421 DESCRIPTION 1422 "Group of objects describing bundles." 1423 ::= { mfrMibGroups 1 } 1425 mfrMibBundleLinkGroup OBJECT-GROUP 1426 OBJECTS { 1427 mfrBundleLinkRowStatus, 1428 mfrBundleLinkConfigBundleIndex, 1429 mfrBundleLinkNearEndName, 1430 mfrBundleLinkState, 1431 mfrBundleLinkFarEndName, 1432 mfrBundleLinkFarEndBundleName, 1433 mfrBundleLinkDelay, 1434 mfrBundleLinkFramesControlTx, 1435 mfrBundleLinkFramesControlRx, 1436 mfrBundleLinkFramesControlInvalid, 1437 mfrBundleLinkTimerExpiredCount, 1438 mfrBundleLinkLoopbackSuspected, 1439 mfrBundleLinkUnexpectedSequence, 1440 mfrBundleLinkMismatch 1441 } 1442 STATUS current 1443 DESCRIPTION 1444 "Group of objects describing bundle links." 1446 ::= { mfrMibGroups 2 } 1448 mfrMibTrapGroup NOTIFICATION-GROUP 1449 NOTIFICATIONS { 1450 mfrMibTrapBundleLinkMismatch 1451 } 1452 STATUS current 1453 DESCRIPTION 1454 "Group of objects describing notifications (traps)." 1455 ::= { mfrMibGroups 3 } 1457 END 1459 4. Acknowledgments 1461 This document was produced by the Frame Relay Service MIB (frnetmib) 1462 Working Group in conjunction with the Frame Relay Forum. 1464 5. References 1466 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1467 for Describing SNMP Management Frameworks", RFC 2571, April 1468 1999 1470 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1471 of Management Information for TCP/IP-based Internets", STD 1472 16, RFC 1155, May 1990 1474 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1475 16, RFC 1212, March 1991 1477 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1478 SNMP", RFC 1215, March 1991 1480 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1481 Rose, M., and S. Waldbusser, "Structure of Management 1482 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 1484 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1485 Rose, M., and S. Waldbusser, "Textual Conventions for 1486 SMIv2", STD 58, RFC 2579, April 1999 1488 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1489 Rose, M., and S. Waldbusser, "Conformance Statements for 1490 SMIv2", STD 58, RFC 2580, April 1999 1492 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1493 Network Management Protocol", STD 15, RFC 1157, May 1990. 1495 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1496 "Introduction to Community-based SNMPv2", RFC 1901, January 1497 1996. 1499 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1500 "Transport Mappings for Version 2 of the Simple Network 1501 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1503 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1504 Processing and Dispatching for the Simple Network Management 1505 Protocol (SNMP)", RFC 2572, April 1999 1507 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1508 (USM) for version 3 of the Simple Network Management 1509 Protocol (SNMPv3)", RFC 2574, April 1999 1511 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1512 "Protocol Operations for Version 2 of the Simple Network 1513 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1515 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1516 RFC 2573, April 1999 1518 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1519 Access Control Model (VACM) for the Simple Network 1520 Management Protocol (SNMP)", RFC 2575, April 1999 1522 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1523 "Introduction to Version 3 of the Internet-standard Network 1524 Management Framework", RFC 2570, April 1999 1526 [Q.922] ITU-T, Recommendation Q.922: "ISDN Data Link Layer 1527 Specification For Frame Mode Bearer Services" 1529 [Q.933] ITU-T, Recommendation Q.933: "Signalling Specification For 1530 Frame Mode Basic Call Control" 1532 [FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC 1533 Implementation Agreement" January 5, 1994. 1535 [FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay 1536 Interworking Implementation Agreement" August 20, 1999. 1538 [RFC1604] T. Brown, "Definitions of Managed Objects for Frame Relay 1539 Service" RFC 1604, Bell Communications Research, March 1994. 1540 [RFC-EDITOR: Update to current RFC that replaces RFC1604] 1542 [RFC2494] D. Fowler, "Definitions of Managed Objects for the DS0 and 1543 DS0 Bundle Interface Type" RFC 2494, Newbridge Networks, 1544 November 1997. 1546 [RFC2863] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB 1547 using SMIv2" RFC 2233, Cisco Systems, FTP Software, June 1548 2000. 1550 [ATMLANE] T. Newton, ed., "LAN Emulation Client Management 1551 Specification Version 2.0" AF-LANE-0093.000, ATM Forum, 1552 October, 1998 1554 [ATMIMA] R. Vallee, ed., "Inverse Multiplexing for ATM Specification 1555 Version 1.1" (Appendix A) AF-PHY-0086.001, ATM Forum, March, 1556 1999 1558 [RFC2115] C. Brown, F. Baker, "Management Information Base for Frame 1559 Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco 1560 Systems, September 1997. 1562 6. Security Considerations 1564 There are a number of management objects defined in this MIB that 1565 have a MAX-ACCESS clause of read-write and/or read-create. Such 1566 objects may be considered sensitive or vulnerable in some network 1567 environments. The support for SET operations in a non-secure 1568 environment without proper protection can have a negative effect on 1569 network operations. 1571 No managed objects in this MIB contain sensitive information. 1573 SNMPv1 by itself is not a secure environment. Even if the network 1574 itself is secure (for example by using IPSec), even then, there is no 1575 control as to who on the secure network is allowed to access and 1576 GET/SET (read/change/create/delete) the objects in this MIB. 1578 It is recommended that the implementers consider the security 1579 features as provided by the SNMPv3 framework. Specifically, the use 1580 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1581 based Access Control Model RFC 2575 [RFC2575] is recommended. 1583 It is then a customer/user responsibility to ensure that the SNMP 1584 entity giving access to an instance of this MIB, is properly 1585 configured to give access to the objects only to those principals 1586 (users) that have legitimate rights to indeed GET or SET 1587 (change/create/delete) them. 1589 7. Authors' Addresses 1591 Prayson Pate 1592 Overture Networks 1593 P. O. Box 14864 1594 RTP, NC, USA 27709 1596 Phone: +1 919 558 2200 1598 EMail: prayson.pate@overturenetworks.com 1600 Bob Lynch 1601 Larscom Incorporated 1602 P. O. Box 14993 1603 RTP, NC, USA 27560 1605 Phone: +1 919 991-9062 1607 EMail: blynch@larscom.com 1609 Kenneth Rehbehn 1610 Megisto Systems, Inc. 1611 20251 Century Boulevard 1612 Germantown, MD, USA 20874 1614 Phone: +1 301 529-4427 1616 EMail: krehbehn@megisto.com 1618 8. Full Copyright Section 1620 Copyright (C) The Internet Society (2000). All Rights Reserved. 1622 This document and translations of it may be copied and furnished to 1623 others, and derivative works that comment on or otherwise explain it 1624 or assist in its implementation may be prepared, copied, published 1625 and distributed, in whole or in part, without restriction of any 1626 kind, provided that the above copyright notice and this paragraph are 1627 included on all such copies and derivative works. However, this 1628 document itself may not be modified in any way, such as by removing 1629 the copyright notice or references to the Internet Society or other 1630 Internet organizations, except as needed for the purpose of 1631 developing Internet standards in which case the procedures for 1632 copyrights defined in the Internet Standards process must be 1633 followed, or as required to translate it into languages other than 1634 English. 1636 The limited permissions granted above are perpetual and will not be 1637 revoked by the Internet Society or its successors or assigns. 1639 This document and the information contained herein is provided on an 1640 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1641 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1642 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1643 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1644 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.