Internet Draft FR/ATM Service Interworking MIB February 1999 Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function February 20, 1999 draft-ieft-frnetmib-atmiwf-01.txt Kenneth Rehbehn Visual Networks krehbehn@visualnetworks.com Orly Nicklass RAD Data Communications, Ltd. Orly_n@rad.co.il George Mouradian AT&T Labs gvm@att.com Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 material 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-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Expires August 1999 [Page 1] Internet Draft FR/ATM Service Interworking MIB February 1999 Abstract This memo defines a Management Information Base (MIB) for monitoring and controlling a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Expires August 1999 [Page 2] Internet Draft FR/ATM Service Interworking MIB February 1999 Table of Contents 1 The SNMPv2 Network Management Framework ...................... 4 2 Object Definitions ........................................... 5 3 Overview ..................................................... 6 3.1 Frame Relay/ATM Service Interworking ....................... 6 4 Object Definitions ........................................... 7 4.1 The FR/ATM PVC Service IWF Connection Group ................ 9 4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 15 5 Frame Relay/ATM PVC Service Interworking TRAP ................ 21 6 Conformance Information ...................................... 22 6.1 Compliance Statement For Equipment ......................... 22 6.2 Compliance Statement For Service (CNM Interface) ........... 24 6.3 Units of Conformance ....................................... 26 6.3.1 Basic FR/ATM IWF PVC Connection Group .................... 26 6.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 26 6.3.3 Notification Group ....................................... 27 7 Acknowledgments .............................................. 28 8 References ................................................... 29 9 Security Considerations ...................................... 30 10 Authors' Addresses .......................................... 30 11 Copyright Section ........................................... 31 Expires August 1999 [Page 3] Internet Draft FR/ATM Service Interworking MIB February 1999 1. The SNMPv2 Network Management Framework The SNMP Network Management Framework presently consists of three major components. They are: o the SMI, described in RFC 1902 [1] - the mechanisms used for describing and naming objects for the purpose of management. o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects for the Internet suite of protocols. o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for accessing managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Expires August 1999 [Page 4] Internet Draft FR/ATM Service Interworking MIB February 1999 2. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. Expires August 1999 [Page 5] Internet Draft FR/ATM Service Interworking MIB February 1999 3. Overview This document defines a Management Information Base (MIB) for monitoring and controlling a service interworking function (IWF) for Permanent Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer Mode (ATM) technologies. The agreements on which this MIB is based were reached jointly by the Frame Relay Forum and the ATM Forum and are documented in the Frame Relay Forum Document FRF.8 [9]. In the future, the MIB defined in this document may be used or extended for service interworking using Switched Virtual Connections. 3.1. Frame Relay/ATM Service Interworking Service interworking applies when a Frame Relay service user interworks with an ATM service user, the ATM service user performs no frame relaying service-specific functions, and the frame relay service user performs no ATM service-specific functions. The optional translation of particular higher layer protocols to satisfy the requirements of end-systems may also be implemented. Consult FRF.8 [9] for more details. Expires August 1999 [Page 6] Internet Draft FR/ATM Service Interworking MIB February 1999 4. Object Definitions FR-ATM-PVC-SERVICE-INTERWORKING-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, transmission, Integer32, BITS, Counter32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, TimeStamp FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF AtmVpIdentifier, AtmVcIdentifier FROM ATM-TC-MIB InterfaceIndex FROM IF-MIB; frAtmIwfMIB MODULE-IDENTITY LAST-UPDATED "9902200000Z" ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" CONTACT-INFO "Kenneth Rehbehn Postal: Visual Networks 2092 Gaither Road Rockville, MD USA 20850 Tel: +1 301 296 2325 Fax: +1 301 296 2302 E-mail: krehbehn@visualnetworks.com Orly Nicklass Postal: RAD Data Communications Ltd. 12 Hanechoshet St. Tel Aviv 69710 Israel Tel: +972 (3) 6459588 Fax: +972 (3) 6472675 E-mail: orly@radmail.rad.co.il George Mouradian Postal: AT&T Labs, Room 1G-325 101 Crawfords Corner Road Holmdel, NJ 07733-3030 Tel: +1 908 949 7671 Email: gvm@att.com" Expires August 1999 [Page 7] Internet Draft FR/ATM Service Interworking MIB February 1999 DESCRIPTION "The MIB module for monitoring and controlling the Frame Relay/ATM PVC Service Interworking Function." ::= { transmission xxx } -- -- Object Identifiers -- frAtmIwfMIBObjects OBJECT IDENTIFIER ::= { frAtmIwfMIB 1 } frAtmIwfTraps OBJECT IDENTIFIER ::= { frAtmIwfMIB 2 } frAtmIwfTrapsPrefix OBJECT IDENTIFIER ::= { frAtmIwfTraps 0 } frAtmIwfConformance OBJECT IDENTIFIER ::= { frAtmIwfMIB 3 } frAtmIwfGroups OBJECT IDENTIFIER ::= { frAtmIwfConformance 1 } frAtmIwfCompliances OBJECT IDENTIFIER ::= { frAtmIwfConformance 2 } -- -- Textual Conventions -- Dlci ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is a DLCI for a PVC segment end-point." SYNTAX Integer32 Expires August 1999 [Page 8] Internet Draft FR/ATM Service Interworking MIB February 1999 -- -- The FR/ATM PVC Service IWF Group -- -- The Frame Relay/ATM PVC Service Interworking Function -- Connection Table contains all connections utilizing -- the interworking function. -- frAtmIwfConnIndexNext OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an appropriate value to be used for frAtmIwfConnIndex when creating entries in the frAtmIwfConnectionTable. The value 0 indicates that no unassigned entries are available. To obtain the frAtmIwfConnIndexNext value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index." ::= { frAtmIwfMIBObjects 1 } frAtmIwfConnectionTable OBJECT-TYPE SYNTAX SEQUENCE OF FrAtmIwfConnectionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table in which each row represents a Frame Relay/ATM interworking connection." ::= { frAtmIwfMIBObjects 2 } frAtmIwfConnectionEntry OBJECT-TYPE SYNTAX FrAtmIwfConnectionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The FrAtmIwfConnectionEntry provides an entry for an interworking connection between a Frame Relay PVC and one or more ATM PVCs. A single Frame Relay PVC connected to a single ATM PVC is refered to as a `point-to-point' connection and is represented by a single row in the FR/ATM IWF Expires August 1999 [Page 9] Internet Draft FR/ATM Service Interworking MIB February 1999 Connection Table. The case of a single Frame Relay PVC connected to multiple ATM PVCs is refered to as a `point-to-multipoint' connection and is represented by multiple rows in the FR/ATM IWF Connection Table. The object frAtmIwfConnIndex uniquely identifies each point-to-point or point-to-multipoint connection. The manager obtains the frAtmIwfConnIndex value for by reading the frAtmIwfConnIndexNext object. After a frAtmIwfConnIndex is assigned for the connection, the manager creates one or more rows in the Cross Connect Table; one for each cross- connection between the frame relay PVC and an ATM PVC. In the case of `point-to-multipoint' connections, all rows are indexed by the same frAtmIwfConnIndex value and MUST refer to the same frame relay PVC. An entry can be created only when the Frame Relay PVC and at least one ATM PVC exist. A row can be established by one-step set-request with all required parameter values and frAtmIwfConnRowStatus set to createAndGo(4). The Agent should perform all error checking as needed. A pair of cross-connected PVCs, as identified by a particular value of the indexes, is released by setting frAtmIwfConnRowStatus to destroy(6). The Agent may release all associated resources. The manager may remove the related PVCs thereafter." INDEX { frAtmIwfConnIndex, frAtmIwfConnAtmPort, frAtmIwfConnVpi, frAtmIwfConnVci, frAtmIwfConnFrPort, frAtmIwfConnDlci } ::= { frAtmIwfConnectionTable 1 } FrAtmIwfConnectionEntry ::= SEQUENCE { frAtmIwfConnIndex Integer32, frAtmIwfConnAtmPort InterfaceIndex, Expires August 1999 [Page 10] Internet Draft FR/ATM Service Interworking MIB February 1999 frAtmIwfConnVpi AtmVpIdentifier, frAtmIwfConnVci AtmVcIdentifier, frAtmIwfConnFrPort InterfaceIndex, frAtmIwfConnDlci Dlci, frAtmIwfConnRowStatus RowStatus, frAtmIwfConnAdminStatus INTEGER, frAtmIwfConnAtm2FrOperStatus INTEGER, frAtmIwfConnAtm2FrLastChange TimeStamp, frAtmIwfConnFr2AtmOperStatus INTEGER, frAtmIwfConnFr2AtmLastChange TimeStamp, frAtmIwfConnUnrecognizedPayloadHeaders Counter32, frAtmIwfConnectionDescriptor Integer32 } frAtmIwfConnIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index to identify this interworking connection." ::= { frAtmIwfConnectionEntry 1 } frAtmIwfConnAtmPort OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index in the ifTable that identifies the ATM port for this interworking connection." ::= { frAtmIwfConnectionEntry 2 } frAtmIwfConnVpi OBJECT-TYPE SYNTAX AtmVpIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VPI of the ATM PVC end point for this interworking connection." ::= { frAtmIwfConnectionEntry 3 } frAtmIwfConnVci OBJECT-TYPE SYNTAX AtmVcIdentifier MAX-ACCESS not-accessible STATUS current Expires August 1999 [Page 11] Internet Draft FR/ATM Service Interworking MIB February 1999 DESCRIPTION "The VCI of the ATM PVC end point for this interworking connection." ::= { frAtmIwfConnectionEntry 4 } frAtmIwfConnFrPort OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index in the ifTable that identifies the Frame Relay port for this interworking connection." ::= { frAtmIwfConnectionEntry 5 } frAtmIwfConnDlci OBJECT-TYPE SYNTAX Dlci MAX-ACCESS not-accessible STATUS current DESCRIPTION "The DLCI that identifies the Frame Relay PVC end point for this interworking connection." ::= { frAtmIwfConnectionEntry 6 } frAtmIwfConnRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this table row. This entry is used to create, change or delete a cross-connect. This object can not be set to active(6) unless the frAtmIwfConnAdminStatus exist in this row. To turn on a cross-connect, the frAtmIwfConnAdminStatus is set to up(1)." ::= { frAtmIwfConnectionEntry 7 } frAtmIwfConnAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired operational state for this interworking connection." Expires August 1999 [Page 12] Internet Draft FR/ATM Service Interworking MIB February 1999 ::= { frAtmIwfConnectionEntry 8 } frAtmIwfConnAtm2FrOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current operational state of this interworking connection in the direction from ATM to FR end." ::= { frAtmIwfConnectionEntry 9 } frAtmIwfConnAtm2FrLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this interworking connection entered its current operational state in the ATM to FR direction. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value." ::= { frAtmIwfConnectionEntry 10 } frAtmIwfConnFr2AtmOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current operational state of this interworking connection in the direction from FR to ATM end." ::= { frAtmIwfConnectionEntry 11 } frAtmIwfConnFr2AtmLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this interworking connection entered its current operational state in the FR to ATM direction. If the current state was entered prior to the last Expires August 1999 [Page 13] Internet Draft FR/ATM Service Interworking MIB February 1999 re-initialization of the local network management subsystem, then this object contains a zero value." ::= { frAtmIwfConnectionEntry 12 } frAtmIwfConnUnrecognizedPayloadHeaders OBJECT-TYPE SYNTAX Counter32 UNITS "Frames" MAX-ACCESS read-only STATUS current DESCRIPTION "This attribute counts the number of frames discarded by the IWF because, while operating in Translation Mode, the IWF is unable to decode the incoming frame payload header according to the mapping rules. (i.e., payload header not recognized by the IWF). When operating in Transparent Mode, the IWF must return noSuchInstance." REFERENCE "FRF.8 [9], Section 5.3.1" ::= { frAtmIwfConnectionEntry 13 } frAtmIwfConnectionDescriptor OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value represents a pointer to the relevant descriptor in the IWF descriptor table." ::= { frAtmIwfConnectionEntry 14 } Expires August 1999 [Page 14] Internet Draft FR/ATM Service Interworking MIB February 1999 -- -- The FR/ATM PVC Service IWF Connection Descriptor Group -- -- The Frame Relay/ATM PVC Service Interworking Function -- Connection Descriptor table. A descriptor provides the -- attributes for a type of interworked connection. -- frAtmIwfConnectionDescriptorIndexNext OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an appropriate value to be used for frAtmIwfConnectionDescriptorIndex when creating entries in the frAtmIwfConnectionDescriptorTable. The value 0 indicates that no unassigned entries are available. To obtain the frAtmIwfConnectionDescriptorIndexNext value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index." ::= { frAtmIwfMIBObjects 3 } frAtmIwfConnectionDescriptorTable OBJECT-TYPE SYNTAX SEQUENCE OF FrAtmIwfConnectionDescriptorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table in which each row represents a descriptor for one type of Frame Relay/ATM interworking connection. A descriptor may be assigned to zero or more FR/ATM PVC service IWF connections." ::= { frAtmIwfMIBObjects 4 } frAtmIwfConnectionDescriptorEntry OBJECT-TYPE SYNTAX FrAtmIwfConnectionDescriptorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry for a descriptor in an interworking connection between a Frame Relay PVC and an ATM Expires August 1999 [Page 15] Internet Draft FR/ATM Service Interworking MIB February 1999 PVC." INDEX { frAtmIwfConnectionDescriptorIndex } ::= { frAtmIwfConnectionDescriptorTable 1 } FrAtmIwfConnectionDescriptorEntry ::= SEQUENCE { frAtmIwfConnectionDescriptorIndex Integer32, frAtmIwfConnDeToClpMappingMode INTEGER, frAtmIwfConnClpToDeMappingMode INTEGER, frAtmIwfConnCongestionMappingMode INTEGER, frAtmIwfConnEncapsulationMappingMode INTEGER, frAtmIwfConnEncapsulationMappings BITS, frAtmIwfConnFragAndReassEnabled INTEGER, frAtmIwfConnArpTranslationEnabled INTEGER } frAtmIwfConnectionDescriptorIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value to identify a descriptor in the table " ::= { frAtmIwfConnectionDescriptorEntry 1 } frAtmIwfConnDeToClpMappingMode OBJECT-TYPE SYNTAX INTEGER { mode1(1), mode2Const0(2), mode2Const1(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object describes which mode of translation is in use for loss priority mapping in the Frame Relay to ATM direction. mode1 = the DE field in the Q.922 core frame shall be mapped to the ATM CLP filed of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame. Expires August 1999 [Page 16] Internet Draft FR/ATM Service Interworking MIB February 1999 mode2Contst0 = the ATM CLP filed of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame shall be set to constant 0. mode2Contst1 = the ATM CLP filed of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame shall be set to constant 1." REFERENCE "FRF.8 [9], Section 4.2.1" DEFVAL { mode1 } ::= { frAtmIwfConnectionDescriptorEntry 2 } frAtmIwfConnClpToDeMappingMode OBJECT-TYPE SYNTAX INTEGER { mode1(1), mode2Const0(2), mode2Const1(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object describes which mode of translation is in use for loss priority mapping in the ATM to Frame Relay direction. mode1 = if one or more cells in a frame has its CLP field set, the DE field of the Q.922 core frame should be set. mode2Const0 = the DE field of the Q.922 core frame should be set to constant 0. mode2Const1 = the DE field of the Q.922 core frame should be set to constant 1." REFERENCE "FRF.8 [9], Section 4.2.2" DEFVAL { mode1 } ::= { frAtmIwfConnectionDescriptorEntry 3 } frAtmIwfConnCongestionMappingMode OBJECT-TYPE Expires August 1999 [Page 17] Internet Draft FR/ATM Service Interworking MIB February 1999 SYNTAX INTEGER { mode1(1), mode2(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object describes which mode of translation is in use for forward congestion indication mapping in the Frame Relay to ATM direction. mode1 = The FECN field in the Q.922 core frame shall be mapped to the ATM EFCI field of every cell generated by the segmentation process of the AAL5 PDU containing the information of that frame. mode2 = The FECN field in the Q.922 core frame shall not be mapped to the ATM EFCI field of cells generated by the segmentation process of the AAL5 PDU containing the information of that frame. The EFCI field is always set to 'congestion not experienced'. In both of the modes above, if there is congestion in the forward direction in the ATM layer within the IWF, then the IWF can set the EFCI field to 'congestion experienced'." REFERENCE "FRF.8 [9], Section 4.3.1.1" DEFVAL { mode1 } ::= { frAtmIwfConnectionDescriptorEntry 4 } frAtmIwfConnEncapsulationMappingMode OBJECT-TYPE SYNTAX INTEGER { transparentMode(1), translationMode(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object indicates whether the mapping of upper layer protocol encapsulation is enabled on this interworking connection. Expires August 1999 [Page 18] Internet Draft FR/ATM Service Interworking MIB February 1999 transparentMode = Forward the encapsulations unaltered. translationMode = Perform mapping between the two encapsulations due to the incompatibilities of the two methods." REFERENCE "FRF.8 [9], Section 5.3" DEFVAL { transparentMode } ::= { frAtmIwfConnectionDescriptorEntry 5 } frAtmIwfConnEncapsulationMappings OBJECT-TYPE SYNTAX BITS { none (0), -- Transparent mode operation bridgedPdus(1), -- PID: 0x00-01,-07,-02 or -08 bridged802dot6(2), -- PID: 0x00-0B bPdus(3), -- PID: 0x00-0E or -0F routedIp(4), -- NLPID: OxCC routedOsi(5), -- NLPID: Ox81, 0x82 or 0x83 otherRouted(6), -- x25Iso8202(7), -- q933q2931(8) } MAX-ACCESS read-write STATUS current DESCRIPTION "If upper layer protocol encapsulation mapping is enabled on this interworking connection, then this attribute enumerates which of the encapsulation mappings are supported." REFERENCE "FRF.8 [9], Section 5.3.1" DEFVAL { { none } } ::= { frAtmIwfConnectionDescriptorEntry 6 } frAtmIwfConnFragAndReassEnabled OBJECT-TYPE SYNTAX INTEGER { enabled(1), notEnabled(2)} MAX-ACCESS read-write STATUS current DESCRIPTION "The attribute indicates whether fragmentation and reassembly is enabled for this connection." REFERENCE "FRF.8 [9], Section 5.3.1.4" DEFVAL { notEnabled } ::= { frAtmIwfConnectionDescriptorEntry 7 } Expires August 1999 [Page 19] Internet Draft FR/ATM Service Interworking MIB February 1999 frAtmIwfConnArpTranslationEnabled OBJECT-TYPE SYNTAX INTEGER { enabled(1), notEnabled(2)} MAX-ACCESS read-write STATUS current DESCRIPTION "The attribute indicates whether ARP translation is enabled for this connection." REFERENCE "FRF.8 [9], Section 5.4" DEFVAL { notEnabled } ::= { frAtmIwfConnectionDescriptorEntry 8 } Expires August 1999 [Page 20] Internet Draft FR/ATM Service Interworking MIB February 1999 -- -- Frame Relay/ATM PVC Service Interworking TRAP -- frAtmIwfConnStatusChange NOTIFICATION-TYPE OBJECTS { frAtmIwfConnIndex, frAtmIwfConnAtmPort, frAtmIwfConnVpi, frAtmIwfConnVci, frAtmIwfConnFrPort, frAtmIwfConnDlci, frAtmIwfConnAdminStatus, frAtmIwfConnAtm2FrOperStatus, frAtmIwfConnFr2AtmOperStatus } STATUS current DESCRIPTION "An indication that the status of this interworking connection has changed." ::= { frAtmIwfTrapsPrefix 1 } Expires August 1999 [Page 21] Internet Draft FR/ATM Service Interworking MIB February 1999 -- -- Conformance Information -- -- -- Compliance Statement For Equipment -- frAtmIwfEquipmentCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for equipment that implements the FR/ATM Interworking MIB." MODULE -- this module MANDATORY-GROUPS { frAtmIwfBasicGroup, frAtmIwfConnectionDescriptorGroup, frAtmIwfNotificationsGroup } OBJECT frAtmIwfConnDeToClpMappingMode SYNTAX INTEGER { mode1(1) } DESCRIPTION "Only support for Mode 1 is required." OBJECT frAtmIwfConnClpToDeMappingMode SYNTAX INTEGER { mode1(1) } DESCRIPTION "Only support for Mode 1 is required." OBJECT frAtmIwfConnCongestionMappingMode SYNTAX INTEGER { mode1(1) } DESCRIPTION "Only support for Mode 1 is required." OBJECT frAtmIwfConnEncapsulationMappingMode SYNTAX INTEGER { transparentMode(1) } DESCRIPTION "Support for Translation Mode is not required." OBJECT frAtmIwfConnEncapsulationMappings SYNTAX BITS { none(0) } DESCRIPTION "The IWF may provide one, some or none of the encapsulation translations defined in section 5.3.1 of FRF.8 [9]." Expires August 1999 [Page 22] Internet Draft FR/ATM Service Interworking MIB February 1999 OBJECT frAtmIwfConnFragAndReassEnabled SYNTAX INTEGER { notEnabled(2) } DESCRIPTION "Only support for Mode 1 is required." OBJECT frAtmIwfConnArpTranslationEnabled SYNTAX INTEGER { notEnabled(2) } DESCRIPTION "Support for ARP Translation is not required." ::= { frAtmIwfCompliances 1 } Expires August 1999 [Page 23] Internet Draft FR/ATM Service Interworking MIB February 1999 -- -- Compliance Statement For Service (CNM Interface) -- frAtmIwfServiceCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for a CNM interface that implements the FR/ATM Interworking MIB." MODULE -- this module MANDATORY-GROUPS { frAtmIwfBasicGroup, frAtmIwfConnectionDescriptorGroup, frAtmIwfNotificationsGroup } -- -- Exceptions for each object type implemented for a -- CNM view of the FR/ATM Interworking MIB -- OBJECT frAtmIwfConnAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frAtmIwfConnDeToClpMappingMode SYNTAX INTEGER { mode1(1) } MIN-ACCESS read-only DESCRIPTION "Support for Mode 1 is required. Other modes are optional. Write access is not required." OBJECT frAtmIwfConnClpToDeMappingMode SYNTAX INTEGER { mode1(1) } MIN-ACCESS read-only DESCRIPTION "Support for Mode 1 is required. Other modes are optional. Write access is not required." OBJECT frAtmIwfConnCongestionMappingMode SYNTAX INTEGER { mode1(1) } MIN-ACCESS read-only DESCRIPTION "Support for Mode 1 is required. Other modes are optional. Write access is not required." Expires August 1999 [Page 24] Internet Draft FR/ATM Service Interworking MIB February 1999 OBJECT frAtmIwfConnEncapsulationMappingMode SYNTAX INTEGER { transparentMode(1) } MIN-ACCESS read-only DESCRIPTION "Support for Transparent Mode is required. Translation Mode is optional. Write access is not required." OBJECT frAtmIwfConnEncapsulationMappings SYNTAX BITS { none(0) } MIN-ACCESS read-only DESCRIPTION "The IWF may provide one, some or none of the encapsulation translations defined in section 5.3.1 of FRF.8 [9]. Write access is not required." OBJECT frAtmIwfConnFragAndReassEnabled SYNTAX INTEGER { notEnabled(2) } MIN-ACCESS read-only DESCRIPTION "Support for Fragmentation and Reassembly is not required. Write access is not required." OBJECT frAtmIwfConnArpTranslationEnabled SYNTAX INTEGER { notEnabled(2) } MIN-ACCESS read-only DESCRIPTION "Support for ARP Translation is not required. Write access is not required." OBJECT frAtmIwfConnRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { frAtmIwfCompliances 2 } Expires August 1999 [Page 25] Internet Draft FR/ATM Service Interworking MIB February 1999 -- -- Units of Conformance -- -- -- Basic FR/ATM IWF PVC Connection Group -- frAtmIwfBasicGroup OBJECT-GROUP OBJECTS { frAtmIwfConnIndexNext, frAtmIwfConnAdminStatus, frAtmIwfConnAtm2FrOperStatus, frAtmIwfConnAtm2FrLastChange, frAtmIwfConnFr2AtmOperStatus, frAtmIwfConnFr2AtmLastChange, frAtmIwfConnUnrecognizedPayloadHeaders, frAtmIwfConnectionDescriptor, frAtmIwfConnRowStatus } STATUS current DESCRIPTION "The collection of basic objects for configuration and control of FR/ATM interworking connections." ::= { frAtmIwfGroups 1 } -- -- FR/ATM IWF PVC Connection Descriptor Group -- frAtmIwfConnectionDescriptorGroup OBJECT-GROUP OBJECTS { frAtmIwfConnectionDescriptorIndexNext, frAtmIwfConnDeToClpMappingMode, frAtmIwfConnClpToDeMappingMode, frAtmIwfConnCongestionMappingMode, frAtmIwfConnEncapsulationMappingMode, frAtmIwfConnEncapsulationMappings, frAtmIwfConnUnrecognizedPayloadHeaders, frAtmIwfConnFragAndReassEnabled, frAtmIwfConnArpTranslationEnabled } STATUS current DESCRIPTION "The collection of basic objects for specification of FR/ATM interworking connection descriptors." ::= { frAtmIwfGroups 2 } Expires August 1999 [Page 26] Internet Draft FR/ATM Service Interworking MIB February 1999 -- -- Notfication Group -- frAtmIwfNotificationsGroup NOTIFICATION-GROUP NOTIFICATIONS { frAtmIwfConnStatusChange } STATUS current DESCRIPTION "The notification for FR/ATM interworking status change." ::= { frAtmIwfGroups 3 } END Expires August 1999 [Page 27] Internet Draft FR/ATM Service Interworking MIB February 1999 7. Acknowledgments This document was produced by the Frame Relay Service MIB Working Group. Expires August 1999 [Page 28] Internet Draft FR/ATM Service Interworking MIB February 1999 8. References [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991. [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, May 1990. [4] SNMPv2 Working Group, 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. [5] SNMPv2 Working Group, 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. [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1907, January 1996. [7] Information processing systems - Open Systems Interconnection, "Specification of Abstract Syntax Notation One (ASN.1)", International Organization for Standardization, International Standard 8824, December 1987. [8] Information processing systems - Open Systems Interconnection, "Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)", International Organization for Standardization, International Standard 8825, December 1987. [9] Frame Relay/ATM PVC Service Interworking Implementation Agreement, Frame Relay Forum, Document Number FRF.8, April 14, 1995. [10] Network Working Group, Noto, Spiegel, and Tesink, "Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999. Expires August 1999 [Page 29] Internet Draft FR/ATM Service Interworking MIB February 1999 9. Security Considerations This MIB adds no security issues that are not raised by SNMP itself. As a Network Management Protocol, SNMP is capable of changing the configuration of a system, of denial of service attacks through requiring the agent to respond to its messages, and displaying values of system counters and configuration settings in the clear where an adversary might read them. This, however, is not in itself a threat: this is the function of the protocol, but could be misused. Such misuse can be avoided or minimized through SNMP Security. 10. Authors' Addresses Kenneth Rehbehn Visual Networks 2092 Gaither Road Rockville, MD, USA 20850 Phone: +1 301 296-2325 EMail: krehbehn@visualnetworks.com Orly Nicklass RAD Data Communications, Ltd. 12 Hanechoshet St. Tel Aviv 69710 Israel Phone: +972 (3) 6459588 E-mail: orly@radmail.rad.co.il George Mouradian AT&T Labs, Room 1G-325 101 Crawfords Corner Road Holmdel, NJ USA 07733 Phone: +1 908 949 7671 EMail: gvm@att.com Expires August 1999 [Page 30] Internet Draft FR/ATM Service Interworking MIB February 1999 11. Copyright Section Copyright (C) The Internet Society (1999). 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 August 1999 [Page 31]