but a number of objects may be read-only if the
implementation does not allow configuration."
MODULE -- this module
MANDATORY-GROUPS {
mfrMibBundleGroup,
mfrMibBundleLinkGroup,
mfrMibTrapGroup
}
OBJECT mfrBundleFragmentation
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, but the value used must be
reported."
OBJECT mfrBundleMaxFragSize
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, but the value used must be
reported.
A value of -1 indicates that the value is not applicable."
OBJECT mfrBundleThreshold
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, but the value used must be
reported.
A value of -1 indicates that the value is not applicable."
OBJECT mfrBundleMaxDiffDelay
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, but the value used must be
reported."
OBJECT mfrBundleSeqNumSize
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, but the value used must be
reported.
A value of -1 indicates that the value is not applicable."
::= { mfrMibCompliances 1 }
-- ---------------------------------------------------------
-- ---------------------------------------------------------
-- Units of Conformance
-- ---------------------------------------------------------
-- ---------------------------------------------------------
mfrMibBundleGroup OBJECT-GROUP
OBJECTS {
mfrBundleMaxNumBundles,
mfrBundleNextIndex,
mfrBundleIfIndex,
mfrBundleRowStatus,
mfrBundleNearEndName,
mfrBundleFragmentation,
mfrBundleMaxFragSize,
mfrBundleTimerHello,
mfrBundleTimerAck,
mfrBundleCountMaxRetry,
mfrBundleActivationClass,
mfrBundleThreshold,
mfrBundleMaxDiffDelay,
mfrBundleMaxBundleLinks,
mfrBundleLinksConfigured,
mfrBundleLinksActive,
mfrBundleBandwidth,
mfrBundleSeqNumSize,
mfrBundleFarEndName,
mfrBundleResequencingErrors,
mfrBundleIfIndexMappingIndex
}
STATUS current
DESCRIPTION
"Group of objects describing bundles."
::= { mfrMibGroups 1 }
mfrMibBundleLinkGroup OBJECT-GROUP
OBJECTS {
mfrBundleLinkRowStatus,
mfrBundleLinkConfigBundleIndex,
mfrBundleLinkNearEndName,
mfrBundleLinkState,
mfrBundleLinkFarEndName,
mfrBundleLinkFarEndBundleName,
mfrBundleLinkDelay,
mfrBundleLinkFramesControlTx,
mfrBundleLinkFramesControlRx,
mfrBundleLinkFramesControlInvalid,
mfrBundleLinkTimerExpiredCount,
mfrBundleLinkLoopbackSuspected,
mfrBundleLinkUnexpectedSequence,
mfrBundleLinkMismatch
}
STATUS current
DESCRIPTION
"Group of objects describing bundle links."
::= { mfrMibGroups 2 }
mfrMibTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mfrMibTrapBundleLinkMismatch
}
STATUS current
DESCRIPTION
"Group of objects describing notifications (traps)."
::= { mfrMibGroups 3 }
END
4. Acknowledgments
This document was produced by the Frame Relay Service MIB (frnetmib)
Working Group in conjunction with the Frame Relay Forum.
5. References
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC2571, April
1999.
[RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD
16, RFC1155, May 1990.
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD
16, RFC1212, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC1157, May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC1901, January
1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network
Management Protocol (SNMP)", RFC2572, April 1999.
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC1905, January 1996.
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
RFC2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC2570, April 1999.
[Q.922] ITU-T, Recommendation Q.922: "ISDN Data Link Layer
Specification For Frame Mode Bearer Services"
[Q.933] ITU-T, Recommendation Q.933: "Signalling Specification For
Frame Mode Basic Call Control"
[FRF.4] R. Cherukuri (ed), FRF.4: "Frame Relay User-to-Network SVC
Implementation Agreement" January 5, 1994.
[FRF.16] M. Sheehan (ed), FRF.16: "UNI/NNI Multilink Frame Relay
Interworking Implementation Agreement" August 20, 1999.
[RFC1604] Rehbehn, K. and D. Fowler, "Definitions of Managed Objects
for Frame Relay Service", RFC2954, October 2000.
[RFC2494] Fowler, D., "Definitions of Managed Objects for the DS0 and
DS0 Bundle Interface Type", RFC2494, November 1997.
[RFC2863] McCloghrie, D. and F. Kastenholz, "The Interfaces Group MIB
using SMIv2", RFC2233, June 2000.
[ATMLANE] T. Newton, ed., "LAN Emulation Client Management
Specification Version 2.0" AF-LANE-0093.000, ATM Forum,
October, 1998
[ATMIMA] R. Vallee, ed., "Inverse Multiplexing for ATM Specification
Version 1.1" (Appendix A) AF-PHY-0086.001, ATM Forum,
March, 1999
[RFC2115] Brown, C. and F. Baker, "Management Information Base for
Frame Relay DTEs Using SMIv2", RFC2115, September 1997.
6. Security Considerations
There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
No managed objects in this MIB contain sensitive information.
SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC2574 [RFC2574] and the View-
based Access Control Model RFC2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
7. Authors' Addresses
Prayson Pate
Overture Networks
P. O. Box 14864
RTP, NC, USA 27709
Phone: +1 919 558 2200
EMail: prayson.pate@overturenetworks.com
Bob Lynch
Overture Networks
P. O. Box 14864
RTP, NC, USA 27709
Phone: +1 919 558-2200
EMail: bob.lynch@overturenetworks.com
Kenneth Rehbehn
Megisto Systems, Inc.
20251 Century Boulevard
Germantown, MD, USA 20874
Phone: +1 301 529-4427
EMail: krehbehn@megisto.com
8. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFCEditor function is currently provided by the
Internet Society.