Internet-Draft Carthic, S. HCL Technologies (Cisco ODC) Expires: January 14, 2003 July 15, 2002 Definitions of Managed Objects for PPP Multilink Bundles draft-carthic-mpbundle-mib-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [16]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference materials or to cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Drafts can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on January 14, 2003. Abstract PPP Multilink Protocol provides a means to aggregate multiple physical links, providing a "bundle", with greater bandwidth than any of the constituent members. This memo defines SMIv2 Management Information Base(MIB) for management of PPP Multilink Bundles. Table of Contents 1. The SNMP Management Framework ...........................2 2. PPP Multilink Protocol Overview .........................3 2.1 Terminology .............................................4 3. Structure of the MIB ....................................4 3.1 MP Bundle Objects .......................................4 3.1.1 mpBundleNextIndex .......................................4 3.1.2 mpBundleTable ...........................................4 3.2 MP Bundle Link Objects ..................................4 Expires: January 14, 2003 [Page 1] Internet-Draft MP-BUNDLE-MIB July 2002 3.2.1 mpBundleLinkTable .......................................4 3.3 Mapping Objects .........................................5 3.3.1 mpBundleIfIndexMappingTable .............................5 4. Relationship with IF-MIB ................................5 4.1 Usage of ifTable ........................................5 4.1.1 Bundles .................................................5 4.1.2 Bundle Links ............................................6 4.2 Usage of ifStackTable ...................................6 5. Definitions .............................................7 Acknowlegements ........................................18 References .............................................18 Author's Address .......................................20 Full Copyright Statement ...............................20 1. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578[RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. Expires: January 14, 2003 [Page 2] Internet-Draft MP-BUNDLE-MIB July 2002 A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 2. PPP Multilink Protocol Overview PPP Multilink Protocol provides a means to aggregate multiple physical links between a fixed pair of systems, providing a virtual link (bundle) with a greater bandwidth than any of the consitutent links. The bundle preserves the order of packets, transmitted over the member links, by use of sequence numbers. _____ _____ / \ / \ | NL1 | | NL2 | \_____/ \_____/ | | +------+ +-------+ _|_____| / \ | MLCP | <--------o Link Layer Demultiplexing \________/ | | <----------------o Virtual Link _____ | _____ / \ | / \ | LCP |-----+-------| LCP | \_____/ \_____/ | | | | o o {Physical Link 1} {Physical Link 2} Expires: January 14, 2003 [Page 3] Internet-Draft MP-BUNDLE-MIB July 2002 2.1 Terminology Physical Link - A physical interface that interconnects two systems. Bundle - An aggregate of one or more physical links using the formats and procedures of PPP Multilink Protocol. The bundles operates as a virtual PPP link-layer entity. 3. Structure of MIB 3.1 MP Bundle Objects 3.1.1 mpBundleNextIndex This scalar is used to assist the manager applications to select a mpBundleIndex during row creation in mpBundleTable. It can be used to avoid race conditions when multiple manager applications try to creates rows in the table. 3.1.2 mpBundleTable This table provides a means to configure MP bundles. It is indexed by mpBundleIndex and contains the following columns: o mpBundleIndex Integer32 o mpBundleIfIndex InterfaceIndex o mpBundleRowStatus RowStatus o mpBundleSeqNumSize INTEGER o mpBundleMRRU Integer32 o mpBundleEndpointIDClass INTEGER o mpBundleEndpointID OCTET STRING o mpBundleFragmentation INTEGER o mpBundleMaxFragmentSize Integer32 o mpBundleLinksMin Integer32 o mpBundleLinksMax Integer32 o mpBundleLinksConfigured Integer32 o mpBundleLinksActive Integer32 o mpBundleTxSeqNum Integer32 o mpBundleRxSeqNum Integer32 o mpBundleFragmentLoss Counter32 o mpBundleFragmentDiscards Counter32 3.2 MP Bundle Link Objects 3.2.1 mpBundleLinkTable This table provides a means to associate links with bundles. It is Expires: January 14, 2003 [Page 4] Internet-Draft MP-BUNDLE-MIB July 2002 indexed by mpBundleLinkIfIndex and contains the following columns: o mpBundleLinkIfIndex InterfaceIndex o mpBundleLinkBundleIndex Integer32 o mpBundleLinkRowStatus RowStatus o mpBundleLinkDiffDelay Integer32 o mpBundleLinkState MpLinkState 3.3 Mapping Objects 3.3.1 mpBundleIfIndexMappingTable The mpBundleIfIndex object provides mpBundleIndex to ifIndex mapping for a bundle. This table provides ifIndex to mpBundleIndex (reverse) mapping for a bundle. The table is indexed by ifIndex and consists of the following column: o mpBundleIfIndexMapping Integer32 4. Relationship with IF-MIB 4.1 Usage of ifTable 4.1.1 Bundles For each multilink PPP bundle, a ifEntry is created with ifType value of pppMultilinkBundle(108) and there will be a corresponding entry in the mpBundleTable. mpBundleIndex may be different from the ifIndex. mpBundleIfIndex will provide mpBundleIndex-to-ifIndex mapping and mpBundleIfIndexMapping will provide ifIndex-to-mpBundleIndex mapping. mpBundleTable is not indexed by ifIndex as otherwise, the manager will have to choose a ifIndex for row creation. The manager will choose mpBundleIndex and the agent will choose the corresponding ifIndex. The following objects of ifTable will have specific meaning for a bundle: o ifAdminStatus - the admin status of the bundle o ifOperStatus - the operational status of the bundle o ifType - pppMultilinkBundle(108) o ifSpeed - the available bandwidth of the bundle o ifMtu - the MTU of the bundle o ifInUCastPkts - the number of frames recevied on the bundle o ifOutUCastPkts - the number of frames transmitted on the bundle o ifInErrors - the number of inbound frames with errors Expires: January 14, 2003 [Page 5] Internet-Draft MP-BUNDLE-MIB July 2002 o ifOutErrors - the number of outbound frames with errors 4.1.2 Bundle Links Each bundle link will appear as an interface in ifTable and the corresponding ifIndex will be used as mpBundleIfIndex. The following objects of ifTable will have specific meaning for a bundle link: o ifInUCastPkts - the number of frames received on the link o ifOutUCastPkts - the number of frames transmitted on the link o ifInErrors - the number of inbound frame and fragment errors o ifOutErrors - the number of outbound frame and fragment errors 4.2 Usage of ifStackTable Each bundle link will appear as lower layer to its bundle interface. The bundle interface will appear as a higher layer to the bundle links. The use of ifStackTable to show the relationship of MP bundle and its member links is illustrated with an example. Example given below is for illustration purpose only. Example: Two DS1 leased lines are aggregated to form a PPP multilink bundle. _____________________________ | | | Multilink Bundle Interface | | pppMultilinkBundle(108) | |_____________________________| | | _____|______ _____|_____ | | | | | Link Layer | | Link Layer| | ppp (23) | | ppp (23) | |____________| |___________| | | ____|_____ ____|_____ | | | | | ds1(18) | | ds1(18) | |__________| |__________| Expires: January 14, 2003 [Page 6] Internet-Draft MP-BUNDLE-MIB July 2002 The assignment of ifIndex values could for example be: ifIndex ifDescr ifType ------------------------------------------ 1 T1 0/0 ds1(18) 2 T1 0/1 ds1(18) 3 Serial 0/0:0 ppp(23) 4 Serial 0/1:0 ppp(23) 5 Multilink1 pppMultilinkBundle(108) The corresponding ifStackTable will be: ifStackHigherLayer ifStackLowerLayer ------------------------------------------ 0 5 1 0 2 0 3 1 4 2 5 3 5 4 5. Definitions MP-BUNDLE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32, mib-2 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC InterfaceIndex, ifIndex FROM IF-MIB; mpBundleMIB MODULE-IDENTITY LAST-UPDATED "200207040000Z" ORGANIZATION "HCL Technologies Ltd (Cisco ODC)" CONTACT-INFO " Carthic Sundararaj Email: csundara@cisco.com Expires: January 14, 2003 [Page 7] Internet-Draft MP-BUNDLE-MIB July 2002 " DESCRIPTION "The MIB to manage PPP Multilink Bundles." REVISION "200207040000Z" DESCRIPTION "Initial version of the MP-BUNDLE-MIB." ::= { mib-2 xx } -- to be assigned by RFC Editor mpBundleObjects OBJECT IDENTIFIER ::= { mpBundleMIB 1 } MpLinkState ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "State of PPP multilink bundle link." SYNTAX INTEGER { active(1), inactive(2) } -- -- PPP Multilink Bundle Objects -- mpBundleNextIndex OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains the next appropriate value to be used for mpBundleIndex when creating entries in mpBundleTable. A manager must first retrieve the value of this object. The agent should modify the value of this object to reflect the next unassigned index after each retrieval by the manager. If the number of unassigned entries is exhausted, this object will take a value of 0." ::= { mpBundleObjects 1 } mpBundleTable OBJECT-TYPE SYNTAX SEQUENCE OF MpBundleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides the management information applicable to a PPP Multilink Bundle. It provides a means to create new PPP Multilink bundles and existing bundles can be removed." ::= { mpBundleObjects 2 } Expires: January 14, 2003 [Page 8] Internet-Draft MP-BUNDLE-MIB July 2002 mpBundleEntry OBJECT-TYPE SYNTAX MpBundleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in mpBundleTable." INDEX { mpBundleIndex } ::= { mpBundleTable 1 } MpBundleEntry ::= SEQUENCE { mpBundleIndex Integer32, mpBundleIfIndex InterfaceIndex, mpBundleRowStatus RowStatus, mpBundleMRRU Integer32, mpBundleSeqNumSize INTEGER, mpBundleEndpointIDClass INTEGER, mpBundleEndpointID OCTET STRING, mpBundleFragmentation INTEGER, mpBundleMaxFragmentSize Integer32, mpBundleLinksMin Integer32, mpBundleLinksMax Integer32, mpBundleLinksConfigured Integer32, mpBundleLinksActive Integer32, mpBundleTxSeqNum Integer32, mpBundleRxSeqNum Integer32, mpBundleFragmentLoss Counter32, mpBundleFragmentDiscards Counter32 } mpBundleIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index identifying this entry in mpBundleTable." ::= { mpBundleEntry 1 } mpBundleIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The 'ifIndex' corresponding to this bundle." ::= { mpBundleEntry 2 } Expires: January 14, 2003 [Page 9] Internet-Draft MP-BUNDLE-MIB July 2002 mpBundleRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row." ::= { mpBundleEntry 3 } mpBundleMRRU OBJECT-TYPE SYNTAX Integer32 (0..2147483647) UNITS "Octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The Maximum Received Reconstructed Unit for this bundle. It specifies the maximum number of octets in the Information fields of reassembled packets." REFERENCE "RFC 1990, Section 5.1.1" ::= { mpBundleEntry 4 } mpBundleSeqNumSize OBJECT-TYPE SYNTAX INTEGER { shortSeqNum(1), longSeqNum(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The sequence number format to be used when packets are fragmented. shortSeqNum - 12 bit sequence number format longSeqNum - 24 bit sequence number format " REFERENCE "RFC 1990, Section 5.1.2" DEFVAL { longSeqNum } ::= { mpBundleEntry 5 } Expires: January 14, 2003 [Page 10] Internet-Draft MP-BUNDLE-MIB July 2002 mpBundleEndpointIDClass OBJECT-TYPE SYNTAX INTEGER { nullClass(1), localAddress(2), ipAddress(3), ieee802dot1GlobalMACAddress(4), pppMagicNumberBlock(5), psnDirectoryNumber(6) } MAX-ACCESS read-create STATUS current DESCRIPTION "The Class of Endpoint Discriminator/Identifier address space used for this bundle." REFERENCE "RFC 1990, Section 5.1.3" DEFVAL { nullClass } ::= { mpBundleEntry 6 } mpBundleEndpointID OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..20)) MAX-ACCESS read-create STATUS current DESCRIPTION "The Endpoint Discriminator/Identifier used for this bundle." REFERENCE "RFC 1990, Section 5.1.3" ::= { mpBundleEntry 7 } mpBundleFragmentation OBJECT-TYPE SYNTAX INTEGER { enable(1), disable(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The object providing control to enable or disable fragmentation." DEFVAL { disable } ::= { mpBundleEntry 8 } Expires: January 14, 2003 [Page 11] Internet-Draft MP-BUNDLE-MIB July 2002 mpBundleMaxFragmentSize OBJECT-TYPE SYNTAX Integer32 (-1..2147483647) UNITS "Octets" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum fragment size for this bundle. This object is valid only when fragmentation is enabled on the bundle. The object must return a value of -1 if fragmentation is disabled. A value of 0 is not valid fragment size." DEFVAL { -1 } ::= { mpBundleEntry 9 } mpBundleLinksMin OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum number of member links required to be active for this bundle to be active." ::= { mpBundleEntry 10 } mpBundleLinksMax OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of links that can be configured as members of this bundle." ::= { mpBundleEntry 11 } mpBundleLinksConfigured OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of links configured as members of this bundle." ::= { mpBundleEntry 12 } mpBundleLinksActive OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of member links that are currently active." ::= { mpBundleEntry 13 } Expires: January 14, 2003 [Page 12] Internet-Draft MP-BUNDLE-MIB July 2002 mpBundleTxSeqNum OBJECT-TYPE SYNTAX Integer32 (0..16777215) MAX-ACCESS read-only STATUS current DESCRIPTION "The sequence number of the last transmitted fragment." ::= { mpBundleEntry 14 } mpBundleRxSeqNum OBJECT-TYPE SYNTAX Integer32 (0..16777215) MAX-ACCESS read-only STATUS current DESCRIPTION "The sequence number of the last received fragment." ::= { mpBundleEntry 15 } mpBundleFragmentLoss OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of lost fragments for this bundle. Fragments may be lost due to corruption of individual packets or link failure." REFERENCE "RFC 1990, Section 4.1" ::= { mpBundleEntry 16 } mpBundleFragmentDiscards OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of fragments that were discarded on this bundle. Fragments are discarded if a fragmented multilink PPP packet could not be reassembled." REFERENCE "RFC 1990, Section 4.1" ::= { mpBundleEntry 17 } Expires: January 14, 2003 [Page 13] Internet-Draft MP-BUNDLE-MIB July 2002 -- -- PPP Multilink Bundle Link Objects -- mpBundleLinkTable OBJECT-TYPE SYNTAX SEQUENCE OF MpBundleLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides means to configure member links to a bundle." ::= { mpBundleObjects 3 } mpBundleLinkEntry OBJECT-TYPE SYNTAX MpBundleLinkEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in mpBundleLinkTable." INDEX { mpBundleLinkIfIndex } ::= { mpBundleLinkTable 1 } MpBundleLinkEntry ::= SEQUENCE { mpBundleLinkIfIndex InterfaceIndex, mpBundleLinkBundleIndex Integer32, mpBundleLinkRowStatus RowStatus, mpBundleLinkDiffDelay Integer32, mpBundleLinkState MpLinkState } mpBundleLinkIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The 'ifIndex' corresponding to this link." ::= { mpBundleLinkEntry 1 } mpBundleLinkBundleIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-create STATUS current DESCRIPTION "The mpBundleIndex of the bundle of which this link a member." ::= { mpBundleLinkEntry 2 } Expires: January 14, 2003 [Page 14] Internet-Draft MP-BUNDLE-MIB July 2002 mpBundleLinkRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row." ::= { mpBundleLinkEntry 3 } mpBundleLinkDiffDelay OBJECT-TYPE SYNTAX Integer32 (0..2147483647) UNITS "milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object provides the delay for this link relative to the link with the longest delay. The value will be 0 for the link with the longest delay." REFERENCE "RFC 1990, Section 4.2" ::= { mpBundleLinkEntry 4 } mpBundleLinkState OBJECT-TYPE SYNTAX MpLinkState MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the multilink state of the link." ::= { mpBundleLinkEntry 5 } -- -- Mapping Objects -- mpBundleIfIndexMappingTable OBJECT-TYPE SYNTAX SEQUENCE OF MpBundleIfIndexMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table mapping the 'ifIndex' values of 'mpBundleIfIndex' values to its corresponding 'mpBundleIndex' values." ::= { mpBundleObjects 4 } mpBundleIfIndexMappingEntry OBJECT-TYPE SYNTAX MpBundleIfIndexMappingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in mpBundleIfIndexMappingTable." Expires: January 14, 2003 [Page 15] Internet-Draft MP-BUNDLE-MIB July 2002 INDEX { ifIndex } ::= { mpBundleIfIndexMappingTable 1 } MpBundleIfIndexMappingEntry ::= SEQUENCE { mpBundleIfIndexMapping Integer32 } mpBundleIfIndexMapping OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The 'mpBundleIndex' value corresponding to the 'ifIndex' value of this row." ::= { mpBundleIfIndexMappingEntry 1 } -- Conformance Information mpBundleMIBConformance OBJECT IDENTIFIER ::= { mpBundleMIB 2 } mpBundleMIBCompliances OBJECT IDENTIFIER ::= { mpBundleMIBConformance 1 } mpBundleMIBGroups OBJECT IDENTIFIER ::= { mpBundleMIBConformance 2 } -- Compliance Statements mpBundleMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities which implement MP-BUNDLE-MIB." MODULE -- this module MANDATORY-GROUPS { mpBundleGroup, mpBundleLinkGroup } OBJECT mpBundleSeqNumSize MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mpBundleMRRU MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mpBundleEndpointIDClass Expires: January 14, 2003 [Page 16] Internet-Draft MP-BUNDLE-MIB July 2002 MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mpBundleEndpointID MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mpBundleFragmentation MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mpBundleMaxFragmentSize MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mpBundleLinksMin MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mpBundleLinkDiffDelay MIN-ACCESS not-accessible DESCRIPTION "This is an optional attribute." ::= { mpBundleMIBCompliances 1 } -- Units of Conformance mpBundleGroup OBJECT-GROUP OBJECTS { mpBundleIfIndex, mpBundleRowStatus, mpBundleSeqNumSize, mpBundleMRRU, mpBundleEndpointIDClass, mpBundleEndpointID, mpBundleFragmentation, mpBundleMaxFragmentSize, mpBundleLinksMin, mpBundleLinksMax, mpBundleLinksConfigured, mpBundleLinksActive, mpBundleTxSeqNum, mpBundleRxSeqNum, Expires: January 14, 2003 [Page 17] Internet-Draft MP-BUNDLE-MIB July 2002 mpBundleFragmentLoss, mpBundleFragmentDiscards, mpBundleIfIndexMapping } STATUS current DESCRIPTION "Objects in mpBundleTable and mpBundleIfIndexMappingTable." ::= { mpBundleMIBGroups 1 } mpBundleLinkGroup OBJECT-GROUP OBJECTS { mpBundleLinkBundleIndex, mpBundleLinkRowStatus, mpBundleLinkDiffDelay, mpBundleLinkState } STATUS current DESCRIPTION "Object in mpBundleLinkTable." ::= { mpBundleMIBGroups 2 } END Acknowledgements Funding for the RFC Editor function is currently provided by the Internet Society. References [1] Wijnen, B., Harrington, D. and R. Presuhn, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Expires: January 14, 2003 [Page 18] Internet-Draft MP-BUNDLE-MIB July 2002 Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [16] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [17] K. Sklower, B. Lloyd, G. McGregor, D. Carr, T. Coradetti, "The PPP Multilink Protocol (MP)", RFC 1990, August 1996. Expires: January 14, 2003 [Page 19] Internet-Draft MP-BUNDLE-MIB July 2002 Author's Address Carthic Sundararaj HCL Technologies Ltd 158 N.S.K Salai, Vadapalani Chennai 600 026 INDIA Phone: +91 44 3750171 Email: csundara@cisco.com Full Copyright Statement Copyright (C) The Internet Society (2002). 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. Expires: January 14, 2003 [Page 20]