Internet-Draft FR/ATM Service Interworking MIB November 1996 Managed Objects for Monitoring and Controlling the Frame Relay/ATM Service Interworking Function draft-ietf-frnetmib-atmiwf-00.txt 25 November 1996 George Mouradian AT&T Labs gvm@att.com Status of this Memo This document is an Internet-Draft. 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.'' To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 1. Introduction This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to monitor and control the Frame Relay/ATM PVC Service Interworking Function described in [9]. This MIB may be implemented in equipment that performs the interworking function, and may also be used by service providers at a Customer Network Management (CNM) interface when the interworking function is performed within the service network. Expires April 1997 [Page 1] Internet-Draft FR/ATM Service Interworking MIB November 1996 2. The SNMP Network Management Framework The SNMP Network Management Framework presently consists of three major components. They are: the SMI, described in RFC 1902 [1] - the mechanisms used for describing and naming objects for the purpose of management. the MIB-II, STD 17, RFC 1231 [2] - the core set of managed objects for the Internet suite of protocols. 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. 2.1. 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. 3. Overview This document defines a Management Information Base (MIB) for monitoring and controling 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 Realy 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 Expires April 1997 [Page 2] Internet-Draft FR/ATM Service Interworking MIB November 1996 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. 4. Definitions FR-ATM-PVC-SERVICE-INTERWORKING-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, TimeTicks experimental, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF AtmVpIdentifier, AtmVcIdentifier, AtmAddr FROM ATM-TC-MIB InterfaceIndex, ifIndex FROM IF-MIB; frAtmIwfMIB MODULE-IDENTITY LAST-UPDATED "9611242000Z" ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group" CONTACT-INFO "George Mouradian AT&T Labs, Room 1G-325 101 Crawfords Corner Road Holmdel, NJ 07733-3030 Phone: +1 908 949 7671 Email: gvm@att.com DESCRIPTION "The MIB module for monitoring and controlling the Frame Relay/ATM PVC Service Interworking Function." ::= { experimental xxx } -- Object Identifiers frAtmIwfMIBObjects OBJECT IDENTIFIER ::= { frAtmIwfMIB 1 } -- Textual Conventions Expires April 1997 [Page 3] Internet-Draft FR/ATM Service Interworking MIB November 1996 Dlci ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is a DLCI for a PVC segment end-point." SYNTAX Integer32 FrAddress ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is a Q.931 Frame Relay address." SYNTAX Integer32 -- ???? What is the right syntax -- for FR addresses? -- The Frame Relay/ATM PVC Service Interworking Connection Table 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 1 } frAtmIwfConnectionEntry OBJECT-TYPE SYNTAX FrAtmIwfConnectionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry for an interworking connection between a Frame Relay PVC and an ATM PVC." INDEX { frAtmIwfFrPort, frAtmIwfDlci, frAtmIwfAtmPort, frAtmIwfVpi, frAtmIwfVci } ::= { frAtmIwfConnectionTable 1 } FrAtmIwfConnectionEntry ::= SEQUENCE { frAtmIwfConnFrPort InterfaceIndex, frAtmIwfConnDlci Dlci, frAtmIwfConnAtmPort InterfaceIndex, frAtmIwfConnVpi AtmVpIdentifier, frAtmIwfConnVci AtmVcIdentifier, frAtmIwfConnAdminStatus INTEGER, frAtmIwfConnOperStatus INTEGER, frAtmIwfConnLastChange TimeTicks, frAtmIwfConnDeToClpMappingMode INTEGER, frAtmIwfConnClpToDeMappingMode INTEGER, Expires April 1997 [Page 4] Internet-Draft FR/ATM Service Interworking MIB November 1996 frAtmIwfConnCongestionMappingMode INTEGER, frAtmIwfConnEncapsulationMappingMode INTEGER, frAtmIwfConnEncapsulationMappings BITS, frAtmIwfConnUnrecognizedPayloadHeaders Counter32, frAtmIwfConnFragAndReassEnabled INTEGER, frAtmIwfConnArpTranslationEnabled INTEGER, frAtmIwfConnFrAddress FrAddr, frAtmIwfConnAtmAddress AtmAddr, frAtmIwfConnRowStatus RowStatus } 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 xxx } 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 xxx } 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 xxx } 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 xxx } frAtmIwfConnVci OBJECT-TYPE Expires April 1997 [Page 5] Internet-Draft FR/ATM Service Interworking MIB November 1996 SYNTAX AtmVcIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VCI of the ATM PVC end point for this interworking connection." ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnAdminStatus OBJECT-TYPE SYNTAX Integer { up(1), down(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired operational state for this interworking connection." ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnOperStatus OBJECT-TYPE SYNTAX Integer { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current operational state of this interworking connection." ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnLastChange OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this interworking connection entered its current operational state. 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 xxx } frAtmIwfConnDeToClpMappingMode OBJECT-TYPE SYNTAX Integer { mode1(1), mode2(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object describes which mode of translation is in use for loss priority mapping in the Frame Relay to ATM direction." REFERENCE Expires April 1997 [Page 6] Internet-Draft FR/ATM Service Interworking MIB November 1996 "Section 4.2.1 of FRF.8 [9]." DEFVAL { mode1 } ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnClpToDeMappingMode OBJECT-TYPE SYNTAX Integer { mode1(1), mode2(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object describes which mode of translation is in use for loss priority mapping in the ATM to Frame Relay direction." REFERENCE "Section 4.2.2 of FRF.8 [9]." DEFVAL { mode1 } ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnCongestionMappingMode OBJECT-TYPE SYNTAX Integer { mode1(1), mode2(2) } MAX-ACCESS read-create 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." REFERENCE "Section 4.3.1.1 of FRF.8 [9]." DEFVAL { mode1 } ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnEncapsulationMappingMode OBJECT-TYPE SYNTAX Integer { transparentMode(1), translationMode(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates whether the mapping of upper layer protocol encapsulation is enabled on this interworking connection as defined in section 5.3 of FRF.8 [9]." DEFVAL { transparentMode } ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnEncapsulationMappings OBJECT-TYPE SYNTAX BITS { bridgedPdus(0) -- PID: 0x00-01, 0x00-07, 0x00-02 or 0x00-08 bridged802.6(1) -- PID: 0x00-0B bPdus(2) -- PID: 0x00-0E or 0x00-0F routedIp(3) -- NLPID: OxCC Expires April 1997 [Page 7] Internet-Draft FR/ATM Service Interworking MIB November 1996 routedOsi(4) -- NLPID: Ox81, 0x82 or 0x83 otherRouted(5) -- x25Iso8202(6) -- q933q2931(7) } MAX-ACCESS read-create STATUS current DESCRIPTION "If upper layer protocol encapsulation mapping is enabled on this interworking connection, then this attribute enumerates which of the encapsulation mappings defined in section 5.3.1 of FRF.8 [9] are supported." DEFVAL { } -- ??????? ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnUnrecognizedPayloadHeaders OBJECT-TYPE SYNTAX Counter32 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 defined in section 5.3.1 of FRF.8 [9] (i.e., payload header not recognized by the IWF)." ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnFragAndReassEnabled OBJECT-TYPE SYNTAX Integer { enabled(1), notEnabled(2)} MAX-ACCESS read-create STATUS current DESCRIPTION "The attribute indicates whether fragmentation and reassembly is enabled for this connection as described in section 5.3.1.4 of FRF.8 [9]." DEFVAL { notEnabled } ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnArpTranslationEnabled OBJECT-TYPE SYNTAX Integer { enabled(1), notEnabled(2)} MAX-ACCESS read-create STATUS current DESCRIPTION "The attribute indicates whether ARP translation is enabled for this connection as described in section 5.4 of FRF.8 [9]." DEFVAL { notEnabled } ::= { frAtmIwfConnectionEntry xxx } Expires April 1997 [Page 8] Internet-Draft FR/ATM Service Interworking MIB November 1996 frAtmIwfConnFrAddress OBJECT-TYPE SYNTAX FrAddr MAX-ACCESS read-create STATUS current DESCRIPTION "The Frame Relay Q.933 address, in E.164 format, if known, of the Frame Relay Service User end point." DEFVAL { ?????????? } ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnAtmAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS read-create STATUS current DESCRIPTION "The ATM Q.2931 address/subaddress tuple, in E.164 or NSAP format, if known, of the ATM Service User end point." DEFVAL { ?????????? } ::= { frAtmIwfConnectionEntry xxx } frAtmIwfConnRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row." ::= { frAtmIwfConnectionEntry xxx } -- notifications frAtmIwfNotifications OBJECT IDENTIFIER ::= { frAtmIwfMIB 2 } frAtmIwfNotifyPrefix OBJECT IDENTIFIER ::= { frAtmIwfNotifications 0 } frAtmIwfConnStatusChange NOTIFICATION-TYPE OBJECTS { frAtmIwfConnFrPort, frAtmIwfConnDlci, frAtmIwfConnAtmPort, frAtmIwfConnVpi, frAtmIwfConnVci, frAtmIwfConnAdminStatus, frAtmIwfConnOperStatus } STATUS current DESCRIPTION "An indication that the status of this interworking connection has changed." ::= { frAtmIwfNotifyPrefix 1 } Expires April 1997 [Page 9] Internet-Draft FR/ATM Service Interworking MIB November 1996 -- conformance information frAtmIwfConformance OBJECT IDENTIFIER ::= { frAtmIwfMIB 3 } frAtmIwfGroups OBJECT IDENTIFIER ::= { frAtmIwfConformance 1 } frAtmIwfCompliances OBJECT IDENTIFIER ::= { frAtmIwfConformance 2 } frAtmIwfEquipmentCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for equipment that implements the FR/ATM Interworking MIB." MODULE -- this module MANDATORY-GROUPS { frAtmIwfBasicGroup, 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 { } -- ??????????? DESCRIPTION "The IWF may provide one, some or none of the encapsulation translations defined in section 5.3.1 of FRF.8 [9]." 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 April 1997 [Page 10] Internet-Draft FR/ATM Service Interworking MIB November 1996 frAtmIwfEquipmentCompliance 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, frAtmIwfNotificationsGroup } OBJECT frAtmIwfConnAdminStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT frAtmIwfConnDeToClpMappingMode SYNTAX INTEGER { mode1(1) } MIN-ACCESS read-only DESCRIPTION "Only support for Mode 1 is required. Write access is not required." OBJECT frAtmIwfConnClpToDeMappingMode SYNTAX INTEGER { mode1(1) } MIN-ACCESS read-only DESCRIPTION "Only support for Mode 1 is required. Write access is not required." OBJECT frAtmIwfConnCongestionMappingMode SYNTAX INTEGER { mode1(1) } MIN-ACCESS read-only DESCRIPTION "Only support for Mode 1 is required. Write access is not required." OBJECT frAtmIwfConnEncapsulationMappingMode SYNTAX INTEGER { transparentMode(1) } MIN-ACCESS read-only DESCRIPTION "Support for Translation Mode is not required. Write access is not required." OBJECT frAtmIwfConnEncapsulationMappings SYNTAX BITS { } -- ??????????? 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 Expires April 1997 [Page 11] Internet-Draft FR/ATM Service Interworking MIB November 1996 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 } -- units of conformance frAtmIwfBasicGroup OBJECT-GROUP OBJECTS { frAtmIwfConnFrPort, frAtmIwfConnDlci, frAtmIwfConnAtmPort, frAtmIwfConnVpi, frAtmIwfConnVci, frAtmIwfConnAdminStatus, frAtmIwfConnOperStatus, frAtmIwfConnLastChange, frAtmIwfConnDeToClpMappingMode, frAtmIwfConnClpToDeMappingMode, frAtmIwfConnCongestionMappingMode, frAtmIwfConnEncapsulationMappingMode, frAtmIwfConnEncapsulationMappings, frAtmIwfConnUnrecognizedPayloadHeaders, frAtmIwfConnFragAndReassEnabled, frAtmIwfConnArpTranslationEnabled, frAtmIwfConnFrAddress, frAtmIwfConnAtmAddress, frAtmIwfConnRowStatus } STATUS current DESCRIPTION "A collection of objects for configuration and control of FR/ATM interworking connections." ::= { frAtmIwfGroups 1 } frAtmIwfNotificationsGroup NOTIFICATIONS-GROUP Expires April 1997 [Page 12] Internet-Draft FR/ATM Service Interworking MIB November 1996 OBJECTS { frAtmIwfConnStatusChange } STATUS current DESCRIPTION "The notification for FR/ATM interworking status change." ::= { frAtmIwfGroups 2 } END 5. Acknowledgements 6. 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, Internation 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, Internation Standard 8825, December 1987. [9] Frame Relay/ATM PVC Service Interworking Implementation Agreement, Frame Relay Forum, Document Number FRF.8, April 14, 1995. Expires April 1997 [Page 13] Internet-Draft FR/ATM Service Interworking MIB November 1996 7. Security Considerations Security issues are not discussed in this memo. 8. Author's Address 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 Table of Contents: 1 Introduction................................................. 1 2 The SNMP Network Management Framework........................ 2 2.1 Object Definitions......................................... 2 3 Overview..................................................... 2 3.1 Frame Relay/ATM Service Interworking....................... 2 4 Definitions.................................................. 3 5 Acknowledgements............................................. 13 6 References................................................... 13 7 Security Considerations...................................... 14 8 Author's Address............................................. 14 Expires April 1997 [Page 14]