idnits 2.17.1 draft-ietf-frnetmib-mfrmib-00.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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 37 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 37 instances of too long lines in the document, the longest one being 7 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 1572 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 (December 1999) is 8897 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: 20 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft MIB For FRF.16 UNI/NNI MFR December 1999 3 Definitions of Managed Objects 4 for Monitoring and Controlling the 5 UNI/NNI Multilink Frame Relay Function 7 December 6, 1999 9 draft-ietf-frnetmib-mfrmib-00.txt 11 Prayson Pate/Bob Lynch 12 Larscom 13 pate@larscom.com 15 Kenneth Rehbehn 16 Visual Networks 17 krehbehn@visualnetworks.com 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC 2026. Internet-Drafts are 23 working documents of the Internet Engineering Task Force (IETF), its 24 areas, and its working groups. Note that other groups may also 25 distribute working documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet- Drafts as reference 30 material or to cite them other than as ``work in progress.'' 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 Abstract 40 This memo defines a Management Information Base (MIB) for monitoring 41 and controlling a UNI/NNI Multilink Frame Relay Function as defined 42 in Frame Relay Forum FRF.16. This MIB also include conformance and 43 notification information. 45 Copyright Notice 47 Copyright (C) The Internet Society (1999). All Rights Reserved. 49 Table of Contents 51 1 The SNMP Management Framework ................................ 4 52 2 Overview ..................................................... 5 53 2.1 Multilink Frame Relay Background ........................... 5 54 2.1.1 Terminology .............................................. 5 55 2.1.2 Reference Model .......................................... 6 56 2.2 Structure of the MIB ....................................... 7 57 2.2.1 bundleMaxNumBundles ...................................... 7 58 2.2.2 bundleNextIndex .......................................... 7 59 2.2.3 bundleTable .............................................. 7 60 2.2.4 Bundle-to-ifIndex Mapping Table .......................... 7 61 2.2.5 bundleLinkTable .......................................... 8 62 2.3 Relationship With Other MIBS and Tables .................... 8 63 2.3.1 Relationship With Interface Table ........................ 9 64 2.3.1.1 Bundle Links ........................................... 9 65 2.3.1.2 Bundles ................................................ 9 66 2.3.1.3 Mapping Between ifIndex and bundleIndex ................ 10 67 2.3.1.4 ifTable Objects ........................................ 10 68 2.3.2 Relationship With Interface Stack Table .................. 10 69 2.3.3 Relationship With Frame Relay DTE MIB .................... 11 70 2.3.4 Relationship With Frame Relay Service MIB ................ 11 71 2.3.5 Example .................................................. 11 72 2.4 Creation Of Bundles and Bundle Links ....................... 13 73 2.4.1 Creation Of Bundles ...................................... 13 74 2.4.2 Creation Of Bundle Links ................................. 13 75 2.5 Notifications .............................................. 13 76 2.5.1 Bundle ................................................... 13 77 2.5.1.1 linkUp ................................................. 13 78 2.5.1.2 linkDown ............................................... 13 79 2.5.2 Bundle Link .............................................. 13 80 2.5.2.1 linkUp ................................................. 13 81 2.5.2.2 linkDown ............................................... 14 82 2.5.2.3 mfrMibTrapBundleLinkMismatch ........................... 14 83 3 Object Definitions ........................................... 15 84 4 Acknowledgments .............................................. 33 85 5 References ................................................... 34 86 6 Security Considerations ...................................... 36 87 7 Authors' Addresses ........................................... 37 88 8 Copyright Section ............................................ 37 90 1. The SNMP Management Framework 92 The SNMP Management Framework presently consists of five major 93 components: 95 o An overall architecture, described in RFC 2571 [RFC2571]. 97 o Mechanisms for describing and naming objects and events for the 98 purpose of management. The first version of this Structure of 99 Management Information (SMI) is called SMIv1 and described in 100 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 101 1215 [RFC1215]. The second version, called SMIv2, is described 102 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 103 [RFC2580]. 105 o Message protocols for transferring management information. The 106 first version of the SNMP message protocol is called SNMPv1 and 107 described in STD 15, RFC 1157 [RFC1157]. A second version of the 108 SNMP message protocol, which is not an Internet standards track 109 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 110 and RFC 1906 [RFC1906]. The third version of the message 111 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 112 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 114 o Protocol operations for accessing management information. The 115 first set of protocol operations and associated PDU formats is 116 described in STD 15, RFC 1157 [RFC1157]. A second set of 117 protocol operations and associated PDU formats is described in 118 RFC 1905 [RFC1905]. 120 o A set of fundamental applications described in RFC 2573 121 [RFC2573] and the view-based access control mechanism described 122 in RFC 2575 [RFC2575]. 124 A more detailed introduction to the current SNMP Management Framework 125 can be found in RFC 2570 [RFC2570]. 127 Managed objects are accessed via a virtual information store, termed 128 the Management Information Base or MIB. Objects in the MIB are 129 defined using the mechanisms defined in the SMI. 131 This memo specifies a MIB module that is compliant to the SMIv2. A 132 MIB conforming to the SMIv1 can be produced through the appropriate 133 translations. The resulting translated MIB must be semantically 134 equivalent, except where objects or events are omitted because no 135 translation is possible (use of Counter64). Some machine readable 136 information in SMIv2 will be converted into textual descriptions in 137 SMIv1 during the translation process. However, this loss of machine 138 readable information is not considered to change the semantics of the 139 MIB. 141 2. Overview 143 This document defines a Management Information Base (MIB) for 144 monitoring and controlling a UNI/NNI Multilink Frame Relay function. 145 The agreement on which this MIB is based was defined and documented 146 by the Frame Relay Forum in the Frame Relay Forum Document FRF.16 147 [FRF.16]. 149 2.1. Multilink Frame Relay Background 151 Multilink Frame Relay (MFR) for the User-to-Network Interface (UNI) 152 and the Network-to-Network Interface (NNI) provides physical 153 interface emulation for frame relay devices. The emulated physical 154 interface consists of one or more physical links, called "bundle 155 links", aggregated together into a single "bundle" of bandwidth. 156 This service provides a frame-based inverse multiplexing function, 157 sometimes referred to as an "IMUX". 159 The bundle provides the same order-preserving service as a physical 160 layer for frames sent on a data link connection. In addition, the 161 bundle provides support for all Frame Relay services based on UNI and 162 NNI standards. 164 2.1.1. Terminology 166 Physical Link -- A single physical interface that interconnects two 167 devices in a frame relay network (e.g. DS1, DS0, 168 Bearer channel, refer to FRF.14). 170 Bundle -- A grouping of one or more physical links using the 171 formats and procedures of multilink frame relay. 172 The bundle operates as a logical interface function 173 that emulates a single physical interface to the 174 Q.922 data link layer. 176 Bundle Link -- A MFR sub-component that controls operation of one 177 of the bundle's physical links. 179 2.1.2. Reference Model 181 +--------------------------+ +--------------------------+ 182 | Switching Layer -OR- | | Switching Layer -OR- | 183 | Higher-Level Applications| | Higher-Level Applications| 184 +--------------------------+ +--------------------------+ 185 | |C-Plane - Q.933| | |C-Plane - Q.933| 186 | U-Plane | (Note 1) | | U-Plane | (Note 1) | 187 | (Note 3) |---------------| | (Note 3) |---------------| 188 | |Q.922 (Note 2) | | |Q.922 (Note 2) | 189 +--------------------------+ +--------------------------+ 190 | Data Link Layer (Q.922) | | Data Link Layer (Q.922) | 191 +--------------------------+ +--------------------------+ 192 | Bundle (B) | | Bundle (B) | 193 +--------------------------+ +--------------------------+ 194 | Bundle | Bundle | Bundle | | Bundle | Bundle | Bundle | 195 | Link | Link | Link | | Link | Link | Link | 196 | (BL) | (BL) | (BL) | | (BL) | (BL) | (BL) | 197 +--------+--------+--------+ +--------+--------+--------+ 198 |Physical|Physical|Physical| |Physical|Physical|Physical| 199 | (PH) | (PH) | (PH) | ___________ | (PH) | (PH) | (PH) | 200 +----+---+----+---+----+---+ /\ \ +----+---+----+---+----+---+ 201 | | | / \ \ | | | 202 | | +---------\ \-----+ | | 203 | | / \ \ | | 204 | +--------------------\ \------------+ | 205 | _________\_______/ Bundle /_ | 206 | /\ / / \ | 207 +-------------| Bundle Link / / |------------------+ 208 \/_____________/ /____/ 209 \/__________/ 211 Figure 1: MFR Reference Diagram 213 Note 1: C-Plane operation described in Q.933 [Q.933] and FRF.4 214 [FRF.4] 216 Note 2: Multiple frame acknowledged information fransfer mode 217 described in Q.922 [Q.922] 219 Note 3: Core aspects for use with frame relay bearer service as 220 described in Q.922, Annex A [Q.922] 222 2.2. Structure of the MIB 224 The UNI/NNI MFR managed objects consist of three tables and two 225 scalars. 227 2.2.1. bundleMaxNumBundles 229 This scalar is used to inform the manager of the maximum number of 230 bundles supported by this device. 232 2.2.2. bundleNextIndex 234 This scalar is used to assist the manager in selecting a value for 235 bundleIndex during row creation. It can also be used to avoid race 236 conditions with multiple managers trying to create rows in the table 237 (see RFC 2494 [RFC2494] for one such alogrithm). 239 2.2.3. bundleTable 241 This table provides a means to configure and monitor bundles. It is 242 indexed by bundleIndex and contains these columns: 244 - bundleIndex Integer32 245 - bundleIfIndex InterfaceIndex 246 - bundleRowStatus RowStatus 247 - bundleNearEndName SnmpAdminString 248 - bundleFragmentation INTEGER 249 - bundleMaxFragSize Integer32 250 - bundleTimerHello INTEGER 251 - bundleTimerAck INTEGER 252 - bundleCountMaxRetry INTEGER 253 - bundleActivationClass INTEGER 254 - bundleThreshold Integer32 255 - bundleMaxDiffDelay Integer32 256 - bundleSeqNumSize INTEGER 257 - bundleLinksConfigured Integer32 258 - bundleLinksActive Integer32 259 - bundleBandwidth Integer32 260 - bundleFarEndName SnmpAdminString 261 - bundleResequencingErrors Counter32 263 2.2.4. Bundle-to-ifIndex Mapping Table 265 This table provides a means to take an ifIndex and find the 266 corresponding bundleIndex. It is indexed by ifIndex and contains 267 these columns: 269 - bundleIfIndexMapping InterfaceIndex 271 2.2.5. bundleLinkTable 273 This table provides a means to configure and monitor bundles. It is 274 indexed by ifIndex and contains these columns: 276 - bundleLinkRowStatus RowStatus 277 - bundleLinkConfigBundleIndex Integer32 278 - bundleLinkNearEndName SnmpAdminString 279 - bundleLinkState BundleLinkState 280 - bundleLinkFarEndName SnmpAdminString 281 - bundleLinkFarEndBundleName SnmpAdminString 282 - bundleLinkDelay Integer32 283 - bundleLinkFramesControlTx Counter32 284 - bundleLinkFramesControlRx Counter32 285 - bundleLinkFramesControlInvalid Counter32 286 - bundleLinkTimerExpiredCount Counter32 287 - bundleLinkLoopbackSuspected Counter32 288 - bundleLinkUnexpectedSequence Counter32 289 - bundleLinkMismatch Counter32 291 2.3. Relationship With Other MIBS and Tables 293 Figure 2 (adapted from RFC 1604 [RFC1604]) shows the relationship of 294 this MIB with other MIBs. 295 ____________________________________________________ 296 | | | | | 297 | | | SIP | RFC1490 | 298 | | X.25 MIB | Relay | (no applic.| 299 | | for IW/Encap.| MIB | MIB) | 300 | | | | | 301 | MIB II |-----------------------------------| 302 | | | 303 | ifTable | Frame Relay Service MIB | 304 | ifXTable |___________________________________| 305 | ifStackTable | | 306 | | FRF.16 MFR MIB | 307 | |___________________________________| 308 | | | | 309 | | Physical Layer MIBs | ATM MIB | 310 | | e.g., DS1/E1 MIB, |---------| 311 | | RS232-like MIB | Phy. | 312 | | | Layer | 313 | | | MIB | 314 |______________|_________________________|_________| 316 Figure 2: Relationship With Other MIBs 318 2.3.1. Relationship With Interface Table 320 2.3.1.1. Bundle Links 322 Each bundle link will appear as an interface in the ifTable. The 323 ifIndex that appears in the ifTable is used for indexing the bundle 324 link tables in the UNI-NNI MFR MIB. 326 2.3.1.2. Bundles 328 Each bundle will appear as an interface in the ifTable. There will 329 be corresponding bundleIndex which may be different than the ifIndex 330 of the bundle. 332 The reason is best summarized in RFC 2494 [RFC2494], which describes 333 frame relay bundle of DS0. It says: 335 This table is not indexed by ifIndex because the manager has to 336 choose the index in a createable row and the agent must be 337 allowed to select ifIndex values. 339 The rows in the ifEntry table are not creatable as they do not have 340 row status. RFC 2233 [RFC2233] suggests that the ifIndex should be 341 chosen by the agent. Here is its statement regarding row creation 342 and deletion: 344 While some interfaces, for example, most physical interfaces, 345 cannot be created via network management, other interfaces such 346 as logical interfaces sometimes can be. The ifTable contains 347 only generic information about an interface. Almost all 348 'create-able' interfaces have other, media-specific, information 349 through which configuration parameters may be supplied prior to 350 creating such an interface. Thus, the ifTable does not itself 351 support the creation or deletion of an interface (specifically, 352 it has no RowStatus column). Rather, if a particular interface 353 type supports the dynamic creation and/or deletion of an 354 interface of that type, then that media-specific MIB should 355 include an appropriate RowStatus object (see the ATM LAN- 356 Emulation Client MIB [ATMLANE] for an example of a MIB which 357 does this). Typically, when such a RowStatus object is 358 created/deleted, then the conceptual row in the ifTable 359 appears/disappears as a by-product, and an ifIndex value (chosen 360 by the agent) is stored in an appropriate object in the media- 361 specific MIB. 363 The ATM LAN-Emulation Client MIB [ATMLANE] uses different indices and 364 so does the IMA MIB. Looking at the examples we have, and the 365 statements from RFC, it seems better to have two indices. This gives 366 the SNMP agent implementor the freedom to manage their ifIndex in the 367 way they like. 369 2.3.1.3. Mapping Between ifIndex and bundleIndex 371 The bundleIfIndexMappingTable is indexed by ifIndex and provides the 372 means to map a given ifIndex into the corresponding bundleIndex. The 373 bundleIfIndexMapping object in the bundleConfigTable (indexed by 374 bundleIndex) provides the reverse mapping of a bundleIndex to the 375 corresponding ifIndex in the ifTable. 377 2.3.1.4. ifTable Objects 379 The table below summarizes the objects in the ifTable [RFC1573] and 380 how they relate to bundles and bundle links. 382 ifTable Column | Bundle Use | Bundle Link Use 383 ------------------+--------------------+--------------------- 384 ifIndex |no special meaning |no special meaning 385 ifDescr |no special meaning |no special meaning 386 ifType |TBD |TBD 387 ifMtu |no special meaning |no special meaning 388 ifSpeed |sum of bundle speeds|no special meaning 389 ifPhysAddress |no special meaning |no special meaning 390 ifAdminStatus |control of bundle |control of bundle link 391 ifOperStatus |status of bundle |status of bundle link 392 ifLastChange |no special meaning |no special meaning 393 ifInOctets |no special meaning |no special meaning 394 ifInUcastPkts |count of frames |count of fragments 395 ifInNUcastPkts |deprecated |deprecated 396 ifInDiscards |no special meaning |no special meaning 397 ifInErrors |no special meaning |no special meaning 398 ifInUnknownProtos |no special meaning |no special meaning 399 ifOutOctets |no special meaning |no special meaning 400 ifOutUcastPkts |no special meaning |no special meaning 401 ifOutNUcastPkts |deprecated |deprecated 402 ifOutDiscards |no special meaning |no special meaning 403 ifOutErrors |no special meaning |no special meaning 404 ifOutQLen |deprecated |deprecated 405 ifSpecific |deprecated |deprecated 407 2.3.2. Relationship With Interface Stack Table 409 The bundles and bundle links will appear in the ifStackTable defined 410 in RFC 2233 [RFC2233]. Each bundle link will appear a lower layer to 411 its owner bundle. The bundle will appear as a higher layer to the 412 bundle links and as a lower layer to a frame relay service or UNI. 414 2.3.3. Relationship With Frame Relay DTE MIB 416 The bundle will have a one-to-one correspondence with a DLCMI or UNI 417 that appear in the DTE MIB tables [RFC2115]. 419 2.3.4. Relationship With Frame Relay Service MIB 421 There is a one-to-one relationship between the MFR bundle and the 422 frame relay service defined in RFC1604 [RFC1604]. There is no other 423 relationship between these MIBs. 425 2.3.5. Example 427 Figure three shows an example of how the various tables are related. 428 This example shows two bundles composed of 2 T1s each. The bundles 429 have a bundleIndex of 10 and 20 respectively. 431 +-------------------------+ 432 | Frame Relay Service | 433 +-----+-------------+-----+ 434 | | 435 +-----+------+------+-----+ 436 | MFR Bundle | MFR Bundle | 437 | 10 | 20 | 438 +--+-----+---+---+-----+--+ 439 | | | | 440 +-+-+ +-+-+ +-+-+ +-+-+ 441 |T1 | |T1 | |T1 | |T1 | 442 +---+ +---+ +-+-+ +---+ 444 Figure 3: Frame Relay Service Being Carried on 4 T1s 446 The assignment of the ifTable index values could for example be: 448 ifIndex | Description 449 --------+---------------------------------------- 450 1 | FrameRelayService (type 44) 451 2 | MFR Bundle #10 (type TBD) 452 3 | MFR Bundle #20 (type TBD) 453 4 | ds1 #1/MFR Bundle Link #1 (type 18) 454 5 | ds1 #2/MFR Bundle Link #2 (type 18) 455 6 | ds1 #3/MFR Bundle Link #3 (type 18) 456 7 | ds1 #4/MFR Bundle Link #4 (type 18) 458 The ifStackTable is then used to show the relationships between the 459 various interfaces. 461 HigherLayer | LowerLayer 462 ------------+----------- 463 0 | 1 464 1 | 2 465 2 | 3 466 2 | 4 467 3 | 5 468 3 | 6 469 4 | 0 470 5 | 0 471 6 | 0 472 7 | 0 474 The bundleIfIndexMappingTable shows the relationship between the 475 ifTable ifIndex and the bundleIndex: 477 ifIndex | bundleIfIndexMappingIndex 478 --------+-------------------------- 479 2 | 10 480 3 | 20 482 The bundleConfigTable shows the relationship between the bundleIndex 483 and the ifIndex: 485 bundleIndex | bundleIfIndex 486 -------------+-------------- 487 10 | 2 488 20 | 3 490 The bundleLinkConfigTable shows the relationship between the bundles 491 and bundle links: 493 bundleIndex | bundleLinkIfIndex 494 ------------+------------------ 495 10 | 4 496 10 | 5 497 20 | 6 498 20 | 7 500 2.4. Creation Of Bundles and Bundle Links 502 2.4.1. Creation Of Bundles 504 A bundle is created using the bundleConfigRowStatus RowStatus object. 505 There is no minimum set of objects required in order to create a new 506 bundle i.e. all of the parameters can assume default values. 508 2.4.2. Creation Of Bundle Links 510 A bundle link is created using the bundleLinkConfigRowStatus 511 RowStatus object. It must be created as a part of an existing 512 bundle. There is no minimum set of objects required in order to 513 create a new bundle link i.e. all of the parameters can assume 514 default values. The only requirement is that the owner bundle 515 (specified by bundleIndex) be in existence. 517 2.5. Notifications 519 The linkUp and linkDown traps are defined in RFC 1573 [RFC1573]. 521 2.5.1. Bundle 523 The following SNMP traps are defined for MFR bundles. 525 2.5.1.1. linkUp 527 This trap is sent when the ifOperStatus of a bundle transitions from 528 down to up. This occurs when a sufficient number of links 529 (determined by bundleActivationClass and bundleThreshold) are in the 530 operationally up state. 532 2.5.1.2. linkDown 534 This trap is sent when the ifOperStatus of a bundle transitions from 535 up to down. This occurs when a insufficient number of links 536 (determined by bundleActivationClass and bundleThreshold) are in the 537 operationally up state. 539 2.5.2. Bundle Link 541 The following SNMP traps are defined for MFR bundle links. 543 2.5.2.1. linkUp 545 This trap is sent when a bundle link transitions into the up state. 547 2.5.2.2. linkDown 549 This trap is sent when a bundle link transitions from the up state. 551 2.5.2.3. mfrMibTrapBundleLinkMismatch 553 This trap indicates that a bundle link mismatch has been detected. 554 The following objects are reported: 556 - bundleNearEndName: configured name of near end bundle 557 - bundleFarEndName: previously reported name of far 558 end bundle 559 - bundleLinkNearEndName: configured name of near end bundle 560 - bundleLinkFarEndName: reported name of far end bundle 561 - bundleLinkFarEndBundleName: currently reported name of far 562 end bundle 564 Note that the configured items may have been configured 565 automatically. Note also that the bundleLinkMismatch counter is 566 incremented when the trap is sent. 568 3. Object Definitions 570 Managed objects are accessed via a virtual information store, termed 571 the Management Information Base or MIB. Objects in the MIB are 572 defined using the subset of Abstract Syntax Notation One (ASN.1) 573 defined in the SMI. In particular, each object type is named by an 574 OBJECT IDENTIFIER, an administratively assigned name. The object 575 type together with an object instance serves to uniquely identify a 576 specific instantiation of the object. For human convenience, we 577 often use a textual string, termed the descriptor, to refer to the 578 object type. 580 FRF16-MFR-MIB-EXP DEFINITIONS ::= BEGIN 582 IMPORTS 583 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, 584 NOTIFICATION-TYPE, experimental 585 FROM SNMPv2-SMI 586 TEXTUAL-CONVENTION, TestAndIncr, RowStatus 587 FROM SNMPv2-TC 588 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 589 FROM SNMPv2-CONF 590 SnmpAdminString 591 FROM SNMP-FRAMEWORK-MIB 592 InterfaceIndex, ifIndex 593 FROM IF-MIB; 595 mfrMib MODULE-IDENTITY 596 LAST-UPDATED "9910191300Z" 597 ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" 598 CONTACT-INFO 599 "Prayson Pate/Bob Lynch 600 Postal: Larscom 601 P. O. Box 14993 602 RTP, NC, USA 27560 603 Phone: +1 919 991-9000 604 EMail: pate@larscom.com/blynch@larscom.com 606 Kenneth Rehbehn 607 Postal: Visual Networks 608 2092 Gaither Road 609 Rockville, MD USA 20850 610 Tel: +1 301 296 2325 611 Fax: +1 301 296 2302 612 E-mail: krehbehn@visualnetworks.com" 614 DESCRIPTION 615 "This is the MIB used to control and monitor the multilink frame 616 relay (MFR) function described in FRF.16. This was originally 617 submitted to the Frame Relay Forum as contribution FRFTC 99-151 618 and then updated as FRFTC 99-193." 620 -- --------------------------------------------------------- 621 -- --------------------------------------------------------- 622 -- Revision History 623 -- --------------------------------------------------------- 624 -- --------------------------------------------------------- 626 REVISION "9910011440Z" 627 DESCRIPTION 628 "Initial version submitted to the Frame Relay Forum 629 October meeting in Huntsville as FRFTC/99-151." 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 "9910212020Z" 646 DESCRIPTION 647 "Updated after comments from Michael Allen and Ken Rehben. 648 o corrected options for sequence number length 649 o changed frf16Mfr prefix to mfr 650 o created a sub-group for scalars 651 o created an entry in the bundleTable for maximum links per bundle 652 o changed indices to not-accessible 653 o changed DisplayString to SnmpAdminString 654 o updated some of the object descriptions 655 o added a -EXP to the name of the MIB 656 o added some DEFVAL and REFERENCE clauses" 658 REVISION "9912061700Z" 659 DESCRIPTION 660 "Updates: 661 o changed name to draft-ietf-frnetmib-mfrmib-00 662 o updated text to match last MIB revisions 663 o corrected description of bundleIfIndexMappingTable 664 o added objects to show configured and current bundle links. 665 " 667 ::= { experimental 555 } 669 -- --------------------------------------------------------- 670 -- --------------------------------------------------------- 671 -- Textual Conventions 672 -- --------------------------------------------------------- 673 -- --------------------------------------------------------- 675 BundleLinkState ::= TEXTUAL-CONVENTION 676 STATUS current 677 DESCRIPTION 678 "The possible states for a bundle link, as defined in 679 Annex A of FRF.16." 680 REFERENCE "FRF.16 Annex A" 681 SYNTAX INTEGER { 682 bundleLinkStateAddSent (1), 683 bundleLinkStateAddRx (2), 684 bundleLinkStateAddAckRx (3), 685 bundleLinkStateUp (4), 686 bundleLinkStateIdlePending (5), 687 bundleLinkStateIdle (6), 688 bundleLinkStateDown (7), 689 bundleLinkStateDownIdle (8) 690 } 692 -- --------------------------------------------------------- 693 -- --------------------------------------------------------- 694 -- Object Identifers 695 -- --------------------------------------------------------- 696 -- --------------------------------------------------------- 698 mfrMibObjects OBJECT IDENTIFIER ::= { mfrMib 1 } 699 mfrMibTraps OBJECT IDENTIFIER ::= { mfrMib 2 } 700 mfrMibConformance OBJECT IDENTIFIER ::= { mfrMib 3 } 702 mfrMibScalarObjects OBJECT IDENTIFIER ::= { mfrMibObjects 1 } 703 mfrMibBundleObjects OBJECT IDENTIFIER ::= { mfrMibObjects 2 } 704 mfrMibBundleLinkObjects OBJECT IDENTIFIER ::= { mfrMibObjects 3 } 706 mfrMibTrapsPrefix OBJECT IDENTIFIER ::= { mfrMibTraps 0 } 708 mfrMibGroups OBJECT IDENTIFIER ::= { mfrMibConformance 1 } 709 mfrMibCompliances OBJECT IDENTIFIER ::= { mfrMibConformance 2 } 711 -- --------------------------------------------------------- 712 -- --------------------------------------------------------- 713 -- Scalars 714 -- --------------------------------------------------------- 715 -- --------------------------------------------------------- 716 bundleMaxNumBundles OBJECT-TYPE 717 SYNTAX Integer32 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "This object is used to inform the manager of the 722 maximum number of bundles supported by this device." 723 ::= { mfrMibScalarObjects 1 } 725 bundleNextIndex OBJECT-TYPE 726 SYNTAX TestAndIncr 727 MAX-ACCESS read-write 728 STATUS current 729 DESCRIPTION 730 "This object is used to assist the manager in 731 selecting a value for bundleIndex during row creation 732 in the bundleTable. It can also be used to avoid race 733 conditions with multiple managers trying to create 734 rows in the table (see RFC 2494 [RFC2494] for one such 735 alogrithm)." 736 REFERENCE "RFC 2494" 737 ::= { mfrMibScalarObjects 2 } 739 -- --------------------------------------------------------- 740 -- --------------------------------------------------------- 741 -- Bundle Table 742 -- --------------------------------------------------------- 743 -- --------------------------------------------------------- 745 bundleTable OBJECT-TYPE 746 SYNTAX SEQUENCE OF BundleEntry 747 MAX-ACCESS not-accessible 748 STATUS current 749 DESCRIPTION 750 "The bundle configuration and status table. There 751 is a one-to-one correspondence between a bundle 752 and an interface represented in the ifTable. 753 The manager can use the following entries in the ifTable: 754 ifAdminStatus - the bundle admin status 755 ifOperStatus - the bundle operational status 756 ifSpeed - the current bandwidth of the bundle 757 ifInErrors - packet (not fragment) errors 758 etc." 759 ::= { mfrMibBundleObjects 3 } 761 bundleEntry OBJECT-TYPE 762 SYNTAX BundleEntry 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "An entry in the bundle table." 767 INDEX { bundleIndex } 768 ::= { bundleTable 1 } 770 BundleEntry ::= 771 SEQUENCE { 772 bundleIndex 773 Integer32, 774 bundleIfIndex 775 InterfaceIndex, 776 bundleRowStatus 777 RowStatus, 778 bundleNearEndName 779 SnmpAdminString, 780 bundleFragmentation 781 INTEGER, 782 bundleMaxFragSize 783 Integer32, 784 bundleTimerHello 785 INTEGER, 786 bundleTimerAck 787 INTEGER, 788 bundleCountMaxRetry 789 INTEGER, 790 bundleActivationClass 791 INTEGER, 792 bundleThreshold 793 Integer32, 794 bundleMaxDiffDelay 795 Integer32, 796 bundleSeqNumSize 797 INTEGER, 798 bundleMaxBundleLinks 799 Integer32, 800 bundleLinksConfigured 801 Integer32, 802 bundleLinksActive 803 Integer32, 804 bundleBandwidth 805 Integer32, 806 bundleFarEndName 807 SnmpAdminString, 808 bundleResequencingErrors 809 Counter32 810 } 812 bundleIndex OBJECT-TYPE 813 SYNTAX Integer32 (1..2147483647) 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "The index into the table. While this corresponds 818 to an entry in the ifTable, the value of bundleIndex 819 need not match that of the ifIndex in the ifTable. 820 A manager can use bundleNextIndex to select a unique 821 bundleIndex for creating a new row." 822 ::= { bundleEntry 1 } 824 bundleIfIndex OBJECT-TYPE 825 SYNTAX InterfaceIndex 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "The value should match an entry in the interface 830 table. The ifType should be set to frame-relay. 831 For example: if the value of bundleIfIndex is 10, 832 then a corresponding entry should be present in 833 the ifTable with an index of 10." 834 ::= { bundleEntry 2 } 836 bundleRowStatus OBJECT-TYPE 837 SYNTAX RowStatus 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 841 "The bundleRowStatus object allows create, change, 842 and delete operations on bundle entries." 843 REFERENCE "RFC 1903" 844 ::= { bundleEntry 3 } 846 bundleNearEndName OBJECT-TYPE 847 SYNTAX SnmpAdminString (SIZE (0..50)) 848 MAX-ACCESS read-create 849 STATUS current 850 DESCRIPTION 851 "The configured name of the bundle." 852 REFERENCE "FRF.16 section 3.4.1" 853 ::= { bundleEntry 4 } 855 bundleFragmentation OBJECT-TYPE 856 SYNTAX INTEGER { 857 enable (1), 858 disable (2) 859 } 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "Controls whether the bundle performs/accepts 864 fragmentation and re-assembly." 865 DEFVAL { disable } 866 ::= { bundleEntry 5 } 868 bundleMaxFragSize OBJECT-TYPE 869 SYNTAX Integer32 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). 875 Otherwise, it should be reported as -1." 876 DEFVAL { -1 } 877 ::= { bundleEntry 6 } 879 bundleTimerHello OBJECT-TYPE 880 SYNTAX INTEGER (1..180) 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "The configured MFR Hello Timer value (in seconds). 885 The default value is 10." 886 REFERENCE "FRF.16 section 4.3.8.1" 887 DEFVAL { 10 } 888 ::= { bundleEntry 7 } 890 bundleTimerAck OBJECT-TYPE 891 SYNTAX INTEGER (1..10) 892 MAX-ACCESS read-create 893 STATUS current 894 DESCRIPTION 895 "The configured MFR T_ACK value (in seconds). 896 The default value is 4." 897 REFERENCE "FRF.16 section 4.3.8.2" 898 DEFVAL { 4 } 899 ::= { bundleEntry 8 } 901 bundleCountMaxRetry OBJECT-TYPE 902 SYNTAX INTEGER (1..5) 903 MAX-ACCESS read-create 904 STATUS current 905 DESCRIPTION 906 "The MFR N_MAX_RETRY value. 907 The default value is 2." 908 REFERENCE "FRF.16 section 4.3.8.3" 909 DEFVAL { 2 } 910 ::= { bundleEntry 9 } 912 bundleActivationClass OBJECT-TYPE 913 SYNTAX INTEGER { 914 bundleActivationClassA (1), -- at least one must link up 915 bundleActivationClassB (2), -- all links must be up 916 bundleActivationClassC (3), -- a certain number must be up 917 bundleActivationClassD (4) -- custom 918 } 919 MAX-ACCESS read-create 920 STATUS current 921 DESCRIPTION 922 "Controls the conditions under which the bundle is activated." 923 REFERENCE "FRF.16 section 4.2.2.1" 924 DEFVAL { bundleActivationClassA } 925 ::= { bundleEntry 10 } 927 bundleThreshold OBJECT-TYPE 928 SYNTAX Integer32 929 MAX-ACCESS read-create 930 STATUS current 931 DESCRIPTION 932 "Specifies the number of links that must be in operational 933 'up' state before the bundle will transition to an 934 operational up/active state. If the number of 935 operational 'up' links falls below this value, 936 then the bundle will transition to an inactive 937 state. 938 Note - this is only valid when bundleActivationClass 939 is set to bundleActivationClassC or to bundleActivationClassD." 940 REFERENCE "FRF.16 section 4.2.2.1" 941 DEFVAL { -1 } 942 ::= { bundleEntry 11 } 944 bundleMaxDiffDelay OBJECT-TYPE 945 SYNTAX Integer32 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "The maximum delay difference between the bundle 950 links. The unit of measure is milliseconds." 951 DEFVAL { -1 } 952 ::= { bundleEntry 12 } 954 bundleSeqNumSize OBJECT-TYPE 955 SYNTAX INTEGER { 956 seqNumSize12bit (1), 957 seqNumSize24bit (2) 958 } 959 MAX-ACCESS read-create 960 STATUS current 961 DESCRIPTION 962 "Controls whether the standard FRF.12 12-bit 963 sequence number is used or the optional 24-bit 964 sequence number." 965 REFERENCE "FRFTC/99-194" 966 DEFVAL { seqNumSize12bit } 967 ::= { bundleEntry 13 } 969 bundleMaxBundleLinks OBJECT-TYPE 970 SYNTAX Integer32 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "The maximum number of bundle links supported for this bundle." 975 ::= { bundleEntry 14 } 977 bundleLinksConfigured OBJECT-TYPE 978 SYNTAX Integer32 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The number of links configured for the bundle." 983 ::= { bundleEntry 15 } 985 bundleLinksActive OBJECT-TYPE 986 SYNTAX Integer32 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "The number of links that are active." 991 ::= { bundleEntry 16 } 993 bundleBandwidth OBJECT-TYPE 994 SYNTAX Integer32 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION 998 "The amount of available bandwidth in bits/sec." 999 ::= { bundleEntry 17 } 1001 bundleFarEndName OBJECT-TYPE 1002 SYNTAX SnmpAdminString (SIZE (0..50)) 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "Name of the bundle received from the far end." 1007 REFERENCE "FRF.16 section 3.4.1" 1008 ::= { bundleEntry 18 } 1010 bundleResequencingErrors OBJECT-TYPE 1011 SYNTAX Counter32 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "A count of the number of resequncing errors. Each event 1016 may correspond to multiple lost frames. Example: 1017 Say sequence number 56, 59 and 60 is received for DLCI 100. 1018 It is decided by some means that sequence 57 and 58 is lost. 1019 This counter should then be incremented by ONE, even though 1020 two frames were lost." 1021 ::= { bundleEntry 19 } 1023 -- --------------------------------------------------------- 1024 -- --------------------------------------------------------- 1025 -- ifIndex Mapping to Bundle Index Table 1026 -- --------------------------------------------------------- 1027 -- --------------------------------------------------------- 1029 bundleIfIndexMappingTable OBJECT-TYPE 1030 SYNTAX SEQUENCE OF BundleIfIndexMappingEntry 1031 MAX-ACCESS not-accessible 1032 STATUS current 1033 DESCRIPTION 1034 "A table mapping the values of ifIndex to the 1035 bundleIndex. This is required in order to find 1036 the bundleIndex given an ifIndex. The mapping of 1037 bundleIndex to ifIndex is provided by the bundleIfIndex 1038 entry in the bundleTable." 1039 ::= { mfrMibBundleObjects 4 } 1041 bundleIfIndexMappingEntry OBJECT-TYPE 1042 SYNTAX BundleIfIndexMappingEntry 1043 MAX-ACCESS not-accessible 1044 STATUS current 1045 DESCRIPTION 1046 "Each row describes one ifIndex to bundleIndex mapping." 1047 INDEX { ifIndex } 1048 ::= { bundleIfIndexMappingTable 1 } 1050 BundleIfIndexMappingEntry ::= 1051 SEQUENCE { 1052 bundleIfIndexMappingIndex 1053 InterfaceIndex 1054 } 1056 bundleIfIndexMappingIndex OBJECT-TYPE 1057 SYNTAX InterfaceIndex 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "The bundleIndex of the given ifIndex." 1062 ::= { bundleIfIndexMappingEntry 2 } 1064 -- --------------------------------------------------------- 1065 -- --------------------------------------------------------- 1066 -- Bundle Link Table 1067 -- --------------------------------------------------------- 1068 -- --------------------------------------------------------- 1070 bundleLinkTable OBJECT-TYPE 1071 SYNTAX SEQUENCE OF BundleLinkEntry 1072 MAX-ACCESS not-accessible 1073 STATUS current 1074 DESCRIPTION 1075 "The bundle link configuration and status table. There 1076 is a one-to-one correspondence between a bundle link 1077 and a physical interface represented in the ifTable. The 1078 ifIndex of the physical interface is used to index the 1079 bundle link table, and to create rows. 1081 The manager can use the following entries in the ifTable: 1082 ifAdminStatus - the bundle link admin status 1083 ifOperStatus - the bundle link operationl status 1084 ifSpeed - the bandwidth of the bundle link 1085 ifInErrors - frame/fragment errors 1086 etc." 1087 ::= { mfrMibBundleLinkObjects 1 } 1089 bundleLinkEntry OBJECT-TYPE 1090 SYNTAX BundleLinkEntry 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "An entry in the bundle link table." 1095 INDEX { ifIndex } 1096 ::= { bundleLinkTable 1 } 1098 BundleLinkEntry ::= 1099 SEQUENCE { 1100 bundleLinkRowStatus 1101 RowStatus, 1102 bundleLinkConfigBundleIndex 1103 Integer32, 1104 bundleLinkNearEndName 1105 SnmpAdminString, 1106 bundleLinkState 1107 BundleLinkState, 1109 bundleLinkFarEndName 1110 SnmpAdminString, 1111 bundleLinkFarEndBundleName 1112 SnmpAdminString, 1113 bundleLinkDelay 1114 Integer32, 1115 bundleLinkFramesControlTx 1116 Counter32, 1117 bundleLinkFramesControlRx 1118 Counter32, 1119 bundleLinkFramesControlInvalid 1120 Counter32, 1121 bundleLinkTimerExpiredCount 1122 Counter32, 1123 bundleLinkLoopbackSuspected 1124 Counter32, 1125 bundleLinkUnexpectedSequence 1126 Counter32, 1127 bundleLinkMismatch 1128 Counter32 1129 } 1131 bundleLinkRowStatus OBJECT-TYPE 1132 SYNTAX RowStatus 1133 MAX-ACCESS read-create 1134 STATUS current 1135 DESCRIPTION 1136 "The bundleLinkRowStatus object allows create, change, 1137 and delete operations on bundleLink entries." 1138 ::= { bundleLinkEntry 1 } 1140 bundleLinkConfigBundleIndex OBJECT-TYPE 1141 SYNTAX Integer32 1142 MAX-ACCESS read-create 1143 STATUS current 1144 DESCRIPTION 1145 "The bundleLinkConfigBundleIndex object allows 1146 the manager to control the bundle to which the bundle 1147 link is assigned. If no value were in this field, then 1148 the bundle would remain in NOT_READY rowStatus and be 1149 unable to go to active. With an appropriate bundleIndex 1150 in this field, then we could put the bundleLink row in 1151 NOT_IN_SERVICE or ACTIVE rowStatus." 1152 ::= { bundleLinkEntry 2 } 1154 bundleLinkNearEndName OBJECT-TYPE 1155 SYNTAX SnmpAdminString (SIZE (0..50)) 1156 MAX-ACCESS read-create 1157 STATUS current 1158 DESCRIPTION 1159 "The configured bundle link name that is sent to the far end." 1160 ::= { bundleLinkEntry 3 } 1162 bundleLinkState OBJECT-TYPE 1163 SYNTAX BundleLinkState 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "Current bundle link state as defined by the MFR protocol 1168 described in Annex A of FRF.16." 1169 REFERENCE "FRF.16 Annex A" 1170 ::= { bundleLinkEntry 4 } 1172 bundleLinkFarEndName OBJECT-TYPE 1173 SYNTAX SnmpAdminString (SIZE (0..50)) 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "Name of bundle link received from far end." 1178 REFERENCE "FRF.16 section 3.4.2" 1179 ::= { bundleLinkEntry 5 } 1181 bundleLinkFarEndBundleName OBJECT-TYPE 1182 SYNTAX SnmpAdminString (SIZE (0..50)) 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "Name of far end bundle for this link received from far end." 1187 REFERENCE "FRF.16 section 3.4.1" 1188 ::= { bundleLinkEntry 6 } 1190 bundleLinkDelay OBJECT-TYPE 1191 SYNTAX Integer32 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "Current round-trip delay for this bundle link." 1196 REFERENCE "FRF.16 section 3.4.4" 1197 ::= { bundleLinkEntry 7 } 1199 bundleLinkFramesControlTx OBJECT-TYPE 1200 SYNTAX Counter32 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "Number of MFR control frames sent." 1205 ::= { bundleLinkEntry 8 } 1207 bundleLinkFramesControlRx OBJECT-TYPE 1208 SYNTAX Counter32 1209 MAX-ACCESS read-only 1210 STATUS current 1211 DESCRIPTION 1212 "Number of valid MFR control frames received." 1213 ::= { bundleLinkEntry 9 } 1215 bundleLinkFramesControlInvalid OBJECT-TYPE 1216 SYNTAX Counter32 1217 MAX-ACCESS read-only 1218 STATUS current 1219 DESCRIPTION 1220 "The number of invalid MFR control frames received." 1221 ::= { bundleLinkEntry 10 } 1223 bundleLinkTimerExpiredCount OBJECT-TYPE 1224 SYNTAX Counter32 1225 MAX-ACCESS read-only 1226 STATUS current 1227 DESCRIPTION 1228 "Number of times the T_HELLO or T_ACK timers expired." 1229 ::= { bundleLinkEntry 11 } 1231 bundleLinkLoopbackSuspected OBJECT-TYPE 1232 SYNTAX Counter32 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "The number of times a loopback has been suspected 1237 (based upon the use of magic numbers)." 1238 REFERENCE "FRF.16 section 4.3.7" 1239 ::= { bundleLinkEntry 12 } 1241 bundleLinkUnexpectedSequence OBJECT-TYPE 1242 SYNTAX Counter32 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "The number of data MFR frames discarded because the sequence 1247 number of the frame for a DLCI was less than (delayed frame) 1248 or equal to (duplicate frame) the one expected for that DLCI. 1250 Example: 1251 Say frames with sequence numbers 56, 58, 59 is received for 1252 DLCI 100. While waiting for sequence number 57 another frame 1253 with sequence number 58 arrives. Frame 58 is discarded and 1254 the counter is incremented." 1255 REFERENCE "FRF.16 section 4.2.3.2" 1256 ::= { bundleLinkEntry 13 } 1258 bundleLinkMismatch OBJECT-TYPE 1259 SYNTAX Counter32 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 "The number of times that the unit has detected a mismatch between 1264 the near end and far end bundles." 1265 REFERENCE "FRF.16 section 4.3.2.4" 1266 ::= { bundleLinkEntry 14 } 1268 -- --------------------------------------------------------- 1269 -- --------------------------------------------------------- 1270 -- Notifications/Traps 1271 -- --------------------------------------------------------- 1272 -- --------------------------------------------------------- 1274 mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE 1275 OBJECTS { 1276 bundleNearEndName, 1277 bundleFarEndName, 1278 bundleLinkNearEndName, 1279 bundleLinkFarEndName, 1280 bundleLinkFarEndBundleName 1281 } 1282 STATUS current 1283 DESCRIPTION 1284 "This trap indicates that a bundle link mismatch has 1285 been detected. The following objects are reported: 1286 - bundleNearEndName: configured name of near end bundle 1287 - bundleFarEndName: previously reported name of far end bundle 1288 - bundleLinkNearEndName: configured name of near end bundle 1289 - bundleLinkFarEndName: reported name of far end bundle 1290 - bundleLinkFarEndBundleName: currently reported name of 1291 far end bundle 1292 Note: that the configured items may have been configured 1293 automatically. 1294 Note: The bundleLinkMismatch counter is incremented when 1295 the trap is sent." 1296 REFERENCE "FRF.16 section 4.3.2.4" 1297 ::= { mfrMibTrapsPrefix 1 } 1299 -- --------------------------------------------------------- 1300 -- --------------------------------------------------------- 1301 -- Conformance/Compliance 1302 -- --------------------------------------------------------- 1303 -- --------------------------------------------------------- 1304 mfrMibCompliance MODULE-COMPLIANCE 1305 STATUS current 1306 DESCRIPTION 1307 "The compliance statement for equipment that implements 1308 the FRF16 MIB. All of the current groups are mandatory, 1309 but a number of objects may be read-only if the 1310 implementation does not allow configuration." 1311 MODULE -- this module 1312 MANDATORY-GROUPS { 1313 mfrMibBundleGroup, 1314 mfrMibBundleLinkGroup, 1315 mfrMibTrapGroup 1316 } 1318 OBJECT bundleFragmentation 1319 MIN-ACCESS read-only 1320 DESCRIPTION 1321 "Write access is not required, but the value used must be reported." 1323 OBJECT bundleMaxFragSize 1324 MIN-ACCESS read-only 1325 DESCRIPTION 1326 "Write access is not required, but the value used must be reported. 1327 A value of -1 indicates that the value is not applicable." 1329 OBJECT bundleThreshold 1330 MIN-ACCESS read-only 1331 DESCRIPTION 1332 "Write access is not required, but the value used must be reported. 1333 A value of -1 indicates that the value is not applicable." 1335 OBJECT bundleMaxDiffDelay 1336 MIN-ACCESS read-only 1337 DESCRIPTION 1338 "Write access is not required, but the value used must be reported." 1340 OBJECT bundleSeqNumSize 1341 MIN-ACCESS read-only 1342 DESCRIPTION 1343 "Write access is not required, but the value used must be reported. 1344 A value of -1 indicates that the value is not applicable." 1346 ::= { mfrMibCompliances 1 } 1348 -- --------------------------------------------------------- 1349 -- --------------------------------------------------------- 1350 -- Units of Conformance 1351 -- --------------------------------------------------------- 1352 -- --------------------------------------------------------- 1353 mfrMibBundleGroup OBJECT-GROUP 1354 OBJECTS { 1355 bundleMaxNumBundles, 1356 bundleIfIndex, 1357 bundleRowStatus, 1358 bundleNearEndName, 1359 bundleFragmentation, 1360 bundleMaxFragSize, 1361 bundleTimerHello, 1362 bundleTimerAck, 1363 bundleCountMaxRetry, 1364 bundleActivationClass, 1365 bundleThreshold, 1366 bundleMaxDiffDelay, 1367 bundleMaxBundleLinks, 1368 bundleSeqNumSize, 1369 bundleFarEndName, 1370 bundleResequencingErrors, 1371 bundleIfIndexMappingIndex, 1372 bundleNextIndex 1373 } 1374 STATUS current 1375 DESCRIPTION 1376 "Group of objects describing bundles." 1377 ::= { mfrMibGroups 1 } 1379 mfrMibBundleLinkGroup OBJECT-GROUP 1380 OBJECTS { 1381 bundleLinkRowStatus, 1382 bundleLinkConfigBundleIndex, 1383 bundleLinkNearEndName, 1384 bundleLinkState, 1385 bundleLinkFarEndName, 1386 bundleLinkFarEndBundleName, 1387 bundleLinkDelay, 1388 bundleLinkFramesControlTx, 1389 bundleLinkFramesControlRx, 1390 bundleLinkFramesControlInvalid, 1391 bundleLinkTimerExpiredCount, 1392 bundleLinkLoopbackSuspected, 1393 bundleLinkUnexpectedSequence, 1394 bundleLinkMismatch 1395 } 1396 STATUS current 1397 DESCRIPTION 1398 "Group of objects describing bundle links." 1399 ::= { mfrMibGroups 2 } 1401 mfrMibTrapGroup NOTIFICATION-GROUP 1402 NOTIFICATIONS { 1403 mfrMibTrapBundleLinkMismatch 1404 } 1405 STATUS current 1406 DESCRIPTION 1407 "Group of objects describing notifications (traps)." 1408 ::= { mfrMibGroups 3 } 1410 END 1412 4. Acknowledgments 1414 This document was produced by the Frame Relay MFR MIB Working Group. 1416 5. References 1418 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1419 for Describing SNMP Management Frameworks", RFC 2571, April 1420 1999 1422 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1423 of Management Information for TCP/IP-based Internets", STD 1424 16, RFC 1155, May 1990 1426 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1427 16, RFC 1212, March 1991 1429 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1430 SNMP", RFC 1215, March 1991 1432 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1433 Rose, M., and S. Waldbusser, "Structure of Management 1434 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 1436 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1437 Rose, M., and S. Waldbusser, "Textual Conventions for 1438 SMIv2", STD 58, RFC 2579, April 1999 1440 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1441 Rose, M., and S. Waldbusser, "Conformance Statements for 1442 SMIv2", STD 58, RFC 2580, April 1999 1444 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1445 Network Management Protocol", STD 15, RFC 1157, May 1990. 1447 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1448 "Introduction to Community-based SNMPv2", RFC 1901, January 1449 1996. 1451 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1452 "Transport Mappings for Version 2 of the Simple Network 1453 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1455 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1456 Processing and Dispatching for the Simple Network Management 1457 Protocol (SNMP)", RFC 2572, April 1999 1459 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1460 (USM) for version 3 of the Simple Network Management 1461 Protocol (SNMPv3)", RFC 2574, April 1999 1463 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1464 "Protocol Operations for Version 2 of the Simple Network 1465 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1467 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1468 RFC 2573, April 1999 1470 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1471 Access Control Model (VACM) for the Simple Network 1472 Management Protocol (SNMP)", RFC 2575, April 1999 1474 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1475 "Introduction to Version 3 of the Internet-standard Network 1476 Management Framework", RFC 2570, April 1999 1478 [Q.922] ITU-T, Recommendation Q.922: "ISDN Data Link Layer 1479 Specification For Frame Mode Bearer Services" 1481 [Q.933] ITU-T, Recommendation Q.933: "Signalling Specification For 1482 Frame Mode Basic Call Control" 1484 [FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC 1485 Implementation Agreement" January 5, 1994. 1487 [FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay 1488 Interworking Implementation Agreement" August 20, 1999. 1490 [RFC1604] T. Brown, "Definitions of Managed Objects for Frame Relay 1491 Service" RFC 1604, Bell Communications Research, March 1994. 1493 [RFC2494] D. Fowler, "Definitions of Managed Objects for the DS0 and 1494 DS0 Bundle Interface Type" RFC 2494, Newbridge Networks, 1495 November 1997. 1497 [RFC2233] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB 1498 using SMIv2" RFC 2233, Cisco Systems, FTP Software, November 1499 1997. 1501 [ATMLANE] T. Newton, ed., "LAN Emulation Client Management 1502 Specification Version 2.0" AF-LANE-0093.000, ATM Forum, 1503 October, 1998 1505 [RFC2115] C. Brown, F. Baker, "Management Information Base for Frame 1506 Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco 1507 Systems, September 1997. 1509 [RFC1573] K. McCloghrie, F. Kastenholz, "Evolution of the Interfaces 1510 Group of MIB-II" RFC 1573, Hughes LAN Systems, FTP Software, 1511 January 1994. 1513 6. Security Considerations 1515 There are a number of management objects defined in this MIB that 1516 have a MAX-ACCESS clause of read-write and/or read-create. Such 1517 objects may be considered sensitive or vulnerable in some network 1518 environments. The support for SET operations in a non-secure 1519 environment without proper protection can have a negative effect on 1520 network operations. 1522 No managed objects in this MIB contain sensitive information. 1524 SNMPv1 by itself is not a secure environment. Even if the network 1525 itself is secure (for example by using IPSec), even then, there is no 1526 control as to who on the secure network is allowed to access and 1527 GET/SET (read/change/create/delete) the objects in this MIB. 1529 It is recommended that the implementers consider the security 1530 features as provided by the SNMPv3 framework. Specifically, the use 1531 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1532 based Access Control Model RFC 2575 [RFC2575] is recommended. 1534 It is then a customer/user responsibility to ensure that the SNMP 1535 entity giving access to an instance of this MIB, is properly 1536 configured to give access to the objects only to those principals 1537 (users) that have legitimate rights to indeed GET or SET 1538 (change/create/delete) them. 1540 7. Authors' Addresses 1542 Prayson Pate/Bob Lynch 1543 Larscom 1544 P. O. Box 14993 1545 RTP, NC, USA 27560 1547 Phone: +1 919 991-9000 1549 EMail: pate@larscom.com/blynch@larscom.com 1551 Kenneth Rehbehn 1552 Visual Networks 1553 2092 Gaither Road 1554 Rockville, MD, USA 20850 1556 Phone: +1 301 296-2325 1558 EMail: krehbehn@visualnetworks.com 1560 8. Copyright Section 1562 Copyright (C) The Internet Society (1999). All Rights Reserved. 1564 This document and translations of it may be copied and furnished to 1565 others, and derivative works that comment on or otherwise explain it 1566 or assist in its implementation may be prepared, copied, published 1567 and distributed, in whole or in part, without restriction of any 1568 kind, provided that the above copyright notice and this paragraph are 1569 included on all such copies and derivative works. However, this 1570 document itself may not be modified in any way, such as by removing 1571 the copyright notice or references to the Internet Society or other 1572 Internet organizations, except as needed for the purpose of 1573 developing Internet standards in which case the procedures for 1574 copyrights defined in the Internet Standards process must be 1575 followed, or as required to translate it into languages other than 1576 English. 1578 The limited permissions granted above are perpetual and will not be 1579 revoked by the Internet Society or its successors or assigns. 1581 This document and the information contained herein is provided on an 1582 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1583 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1584 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1585 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1586 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.