HTTP/1.1 200 OK Date: Tue, 09 Apr 2002 00:56:52 GMT Server: Apache/1.3.20 (Unix) Last-Modified: Fri, 24 Mar 1995 23:00:00 GMT ETag: "2e9d9c-20cd2-2f734ef0" Accept-Ranges: bytes Content-Length: 134354 Connection: close Content-Type: text/plain Definitions of Supplemental Managed Objects for ATM Management March 1995 Faye Ly (editor) BayNetworks Communications, Inc. faye@Baynetworks.COM Michael Noto (editor) Bell Communications Research noto@cc.bellcore.com Andrew Smith (editor) BayNetworks Communications, Inc. asmith@Baynetworks.COM Kaj Tesink (editor) Bell Communications Research kaj@cc.bellcore.com 1. 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 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 a "work in progress". draft Supplemental ATM Management Objects March 1995 2. 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 objects used for managing ATM-based interfaces, devices, networks and services in addition to those defined in the ATM MIB [1], to provide additional support for the management of: - ATM Switched Virtual Connections (SVCs) - ATM Permanent Virtual Connections (PVCs) This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. This memo does not specify a standard for the Internet community. 3. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework consists of four major components. They are: 0 RFC 1442 [2] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. 0 STD 17, RFC 1213 [3] defines MIB-II, the core set of managed objects for the Internet suite of protocols. 0 RFC 1445 [4] which defines the administrative and other architectural aspects of the framework. 0 RFC 1448 [5] which defines the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Expires XX [Page 2] draft Supplemental ATM Management Objects March 1995 4. 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 also refer to the object type. 5. Overview The purpose of this memo is to provide additional capabilities, not found in the ATM MIB [1], which are needed to manage ATM interfaces. This memo addresses the following areas: - ATM Switch/Network/Host Support - ATM Switch/Network Support - ATM Host Support 5.1. Background In addition to the MIB module defined in this memo, other MIB modules are necessary to manage ATM interfaces, links and cross-connects. Examples include MIB II for general system and interface management (RFC 1213 and RFC 1573), the DS3 or SONET MIBs for management of SONET and DS3 physical interfaces, and, as appropriate, MIB modules for applications that make use of ATM, such as SMDS [15] and LAN Emulation [14]. These MIB modules are outside the scope of this specification. This MIB module also requires the use of the ATM MIB module defined in [1]. ATM Endpoint applications such as ATM LAN Emulation or Classical IP-over-ATM Clients and Servers use ATM to establish SVC/PVC connections for exchanging control and data information. The agents of these ATM applications must provide Expires XX [Page 3] draft Supplemental ATM Management Objects March 1995 the network manager with information on the SVC/PVCs in use and which applications are using them. The information can be made generic so as to apply to all ATM applications. This memo proposes extensions to the ATM MIB [1] in order to support this. The current specification of this supplemental ATM MIB is based on SNMPv2. 5.2. Supported Functions The managed ATM objects are arranged into the following groups: - ATM Switch/Network/Host Support: (1) ATM Switch/Network/Host Group (2) ATM Switch/Network/Host SVC Group - ATM Switch/Network Support: (3) ATM Switch/Network Group (4) ATM Switch/Network SVC Group - ATM Host Support: (5) ATM Host Group (6) ATM Host SVC Group 5.2.1. ATM Switch/Network/Host Support 5.2.1.1. ATM Switch/Network/Host Group 5.2.1.1.1. ATM VCL Statistics Table The atmVclStatTable is an extension to the atmVclTable. It contains counters such as the cells received and cells transmitted per SVC or PVC. These counters are defined as 32 bit integers. The implementation of this table is optional. 5.2.1.2. ATM Switch/Network/Host SVC Group 5.2.1.2.1. ATM Interface SVC Configuration Table This group contains information on the configuration of local ATM interfaces on an ATM device required to support SVCs in addition to those defined in the atmInterfaceConfTable of the ATM MIB [1] and those defined in RFC1573 [6]. Expires XX [Page 4] draft Supplemental ATM Management Objects March 1995 Two important aspects of a local ATM interface that supports SVCs are the peak bandwidth assigned to the signalling virtual channel and signalling type used. The signalling virtual channel is a point-to-point, bidirectional symmetric, virtual channel connection. The range of peak bandwidth values is 173 cells/sec to 3979 cells/sec, in steps of 173 cells/sec, with a default value of 173 cells/sec. Using the ATM MIB [1] the signalling virtual channel bandwidth is assigned by creating a row in the ATM Traffic Descriptor Table which defines a Peak Cell Rate (PCR) which represents the signalling channel bandwidth. Then using an entry in the atmVclTable [1], identify this row in the ATM Traffic Descriptor Table as the traffic descriptor for the signalling channel bandwidth. The signalling type defines the type of signalling supported at the local ATM interface (e.g., Q.2931 signalling). The defined signalling types supported by this MIB include: Q.2931 [11], ATM Forum's UNI 3.1 [10], and ATM Forum's P-NNI [12]. This group contains a set of timers that do not have universal default values. The following timers are supported by either Q.2931 [11], ATM Forum UNI 3.1 [10], or both: T302 Overlap Sending Timer: Applicable to both Hosts and Network Switches. This timer starts when a SETUP ACKNOWLEDGE message is sent. The normal cause for stopping is when sending a complete indication, or network alert or connect request received. At first expiry clear if call information determined to be definitely incomplete; else send a CALL PROCEEDING. The range of this timer is defined in Q.2931 as 10-15 seconds. T302 is a Mandatory timer only if Q.2931 Section 6.5 "Overlap Sending and Receiving" is implemented. Note: The ATM Forum UNI 3.1 [10] does not support this timer. T310 Outgoing Call Proceeding Timer: Applicable to both Hosts and Network Switches. This timer starts when a CALL PROCEEDING message is received. The normal cause for stopping is when an ALERT, CONNECT, or RELEASE message is received. At first expiry a RELEASE message is sent. The range of this timer from 10 to 120 seconds. T310 is a Mandatory timer. Q.2931 recommends a default value of 30-120 seconds and the ATM Forums UNI 3.1 Specification recommends a default value Expires XX [Page 5] draft Supplemental ATM Management Objects March 1995 of 10 seconds. Therefore, the range is between 10-120 seconds. T317 Restart Timer: Applicable to both Hosts and Network Switches. This timer starts when a RESTART message is received. The normal cause for stopping this timer is when there is an internal clearing of call references. At first expiry there is a maintenance notification. T317 is a Mandatory timer. The range of this timer is less than the value of Timer T316 (i.e., less than 2 minutes). In addition to above timers, several other timers which are used by hosts and network switches are defined by either Q.2931, ATM Forum UNI 3.1, or both of them. However, these timers have not been defined as managed objects since recommended default values can be used. The timers not defined in this MIB fit into one of the following categories: 1) If the Timer is only supported by the ATM Forum UNI 3.1, then use the ATM Forum UNI 3.1 Recommended default value for the timer. 2) If the Timer is only supported by Q.2931, then use the Q.2931 Recommended default value for the timer. 3) If the Timer is supported by ATM Forum UNI 3.1 and Q.2931, then use the common default value for the timer. The following timers are not included in this MIB: T301, T303, T304, T306, T308, T309, T313, T316, T322, T398, T399. 5.2.1.2.2. SSCOP Table This group contains information on the ATM SSCOP signalling layer and must be supported by signalling entities. 5.2.1.2.3. Unsupported Service Failures Table This group contains information on the setup failures that occur when setting up an ATM SVC. Maintaining counters for each individual signalling cause codes would result in a large number of counters. Instead, this memo uses an approach that lumps events into three categories. Three counters are used Expires XX [Page 6] draft Supplemental ATM Management Objects March 1995 to monitor connection failures occurring due to: 1) unavailable route, 2) unavailable switch or network resources, or 3) the called party. The counters are defined as follows: 1. Route Unavailable Counter This counter maintains the number of calls cleared because there was no route unavailable to the destination. 2. Resources Unavailable Counter This counter maintains the number of cleared calls due to switch or network resources being unavailable. 3. Called Party Counter This counter maintains the number of cleared calls caused by the called party (e.g., called party rejects the call). 5.2.1.2.4. ATM Signalling Layer Protocol Errors Table This group contains information on the Protocol Errors that occur at the signalling layer when establishing an ATM SVC. 5.2.1.2.5. UNI Signalling Sub-layer Statistics Table Configuration is needed per signalling entity in order to manage attributes of all SVCs set up by that entity. Signalling entities are not always bound one to one to ATM UNIs which is not always the case: a more flexible indexing mechanism would be to multiple signalling entities on a single UNI or vice versa - using ifIndex and VPI would provide sufficient flexibility here. Statistics per VCL are needed in order to find out the usage of VCL resources by ATM applications. Additionally, to monitor the usage and health of an UNI signalling entity, some counters are needed per UNI signalling entity. Two new objects are added to count the number of connections established. One for incoming SVCs and one for outgoing SVCs. Expires XX [Page 7] draft Supplemental ATM Management Objects March 1995 5.2.2. ATM Switch/Network Support 5.2.2.1. ATM Switch/Network Group 5.2.2.1.1. ATM Interface Administrative Address Table This group is only supported by switches or networks for interfaces that have multiple associated addresses. This group contains an ATM Interface Administrative Address Table (atmIfAdminAddrTable) which list up to 16 valid addresses for calls to and from a given interface. One of these numbers shall be specified as the "default" number. With screening, the Calling Party Number Information Element received in the SETUP message is checked by the switch or network to verify that it is one of the allowable addresses listed in the atmIfAdminAddrTable. 5.2.2.2. ATM Switch/Network SVC Group 5.2.2.2.1. ATM UNI SVC Subscription Features Table This group must be supported by switches or networks supporting SVCs. The following subscription features for a UNI that supports ATM SVCs are contained in this group: 1) Calling party number delivery feature This parameter indicates whether the calling party number is delivered by the switch or network to the called address. (The calling party number is always delivered by the switch or network to the terminating switch, and this feature determines whether the number is delivered to the called party.) The default value is 'disabled' which indicates that the feature is not active. 2) Calling party number screening feature This parameter indicates whether screening of a calling party number is supported by the switch or network. If supported, the switch or network checks the calling party number received in the SETUP or ADD PARTY message to verify that it is one of the allowable calling party numbers. (This list of allowable calling party numbers is located in the atmIfAdminAddrTable with up to 16 valid addresses per UNI. One of these numbers shall be specified as the "default" number.) Expires XX [Page 8] draft Supplemental ATM Management Objects March 1995 If the received calling party number fails screening, the switch or network will replace the calling party number received in the SETUP or ADD PARTY message with the default number for the interface before forwarding this to the called party. This will result in a completed call, but the delivered calling party number will not be the number indicated by the calling party. Failed screening number events are monitored by the atmSubscrFeaturClgPtyFailScrCnts. The default value for this feature is 'enabled' which indicates that the screening is active. 3) Calling party subaddress transfer feature This parameter indicates whether the switch or network accepts, transfers, and delivers the Calling Party Subaddress Information Element received in the appropriate signalling message. The default value is 'disabled' which indicates that the feature is not active. 4) Called party subaddress transfer feature This parameter indicates whether the switch or network accepts, transfers, and delivers the Called Party Subaddress Information Element received in the appropriate signalling message. The default value is 'disabled' which indicates that the feature is not active. 5) High layer information transfer feature This parameter indicates whether the switch or network accepts, transfers, and delivers the Broadband High Layer Information Element received in the appropriate signalling message. The default value is 'disabled' which indicates that the feature is not active. 6) Low layer information transfer feature This parameter indicates whether the switch or network accepts, transfers, and delivers Broadband Low Layer Information Element received in the appropriate signalling message. The default value is 'disabled' which indicates that the feature is not active. 7) Low layer information selection feature Expires XX [Page 9] draft Supplemental ATM Management Objects March 1995 This parameter indicates whether the switch or network accepts, transfers, and delivers up to three instances of the Broadband Low Layer Information Element for low layer information selection received in the appropriate signalling message. The default value is 'disabled' which indicates that the feature is not active. This parameter may be supplied only if the Low layer information transfer feature has a value of 'enabled'. 8) AAL parameter information transfer feature This parameter indicates whether the switch or network accepts, transfers, and delivers the ATM Adaptation Layer Parameters Information Element received in the appropriate signalling message. The default value is 'disabled' which indicates that the feature is not active. 9) Preferred Carrier Presubscription This parameter identifies the carrier to which intercarrier calls originated from this interface are routed when transit network selection information is not provided by the calling party. 5.2.3. ATM Host Support 5.2.3.1. ATM Host Group 5.2.3.1.1. VCL Extension Table There can be two types of VCLs, Permanent VC or Switched VC used by ATM applications. The ATM MIB [1] provides general connection management (atmVclTable). This memo provides an extension to the atmVclTable which supports both SVC/PVC monitoring and PVC configuration capabilities. This table contains information needed for configuring PVCs and monitoring SVC/PVCs. It is an extension to the atmVclTable defined in the ATM MIB [1]. The object Remote ATM address and Local ATM address describe the two endpoint addresses of a VCL. Local ATM address represents the ATM endpoint at the end of the VCL represented by this agent. Remote ATM address represents the ATM application at the other end. Expires XX [Page 10] draft Supplemental ATM Management Objects March 1995 The object Connection Type is the type of the VCL, it is either a PVC, an incoming SVC or a outgoing SVC. When creating an SVC, the agent can represent the VCL's attributes by selecting entries from two tables: the ATM Traffic Descriptor Parameter Table defined in the ATM MIB [1] and the ATM Signalling Descriptor Parameter Table defined in this memo. For SVCs, the Signalling Descriptor index is used to point to an entry in the ATM Signalling Descriptor Parameter Table. 5.2.3.1.2. ATM Addresses to VCC Mapping Table Some ATM applications (e.g. LAN Emulation) use ATM endpoint addresses even over PVCs. In order to trace SVC/PVCs between such ATM applications, it is important to be able to monitor VCLs (both SVCs and PVCs) indexed by their endpoint ATM addresses. The atmVclAddrTable contains all VCCs currently active and is indexed by the remote ATM address. It is used in conjunction with the atmVclTable and the atmVclExtTable. Each entry in this table identifies an entry in the atmVclTable/atmVclExtTable. 5.2.3.2. ATM Host SVC Group 5.2.3.2.1. Signalling Parameter Descriptor Table This table extends the ATM VCL table of the ATM MIB [1] to include all other necessary signalling information as specified in both ATM Forum UNI Specifications [9] and [10]. A user can create an entry with all signalling parameters and later use that entry to specify the signalling characteristics of SVCs. Signalling attributes can be grouped into following categories: 1) ATM Adaptation Layer Parameters Information in this group are captured in the ATM Signalling Descriptor Parameter Table defined in this memo. Please refer to section 5.4.5.5 of [9] and [10]. 2) Broadband Bearer Capability Expires XX [Page 11] draft Supplemental ATM Management Objects March 1995 Information in this group are captured by the ATM Signalling Descriptor Parameter Table defined in this memo. Please refer to section 5.4.5.7 of [9] and [10]. 3) Broadband High Layer Information Information in this group are captured by the ATM Signalling Descriptor Parameter Table defined in this memo. Please refer to section 5.4.5.8 of [9] and [10]. 4) Broadband Low Layer Information Information in this group are captured by the ATM Signalling Descriptor Parameter Table defined in this memo. Please refer to section 5.4.5.9 of [9] and [10]. 6. Valid Address Sets / Default Address A given ATM UNI interface may have an Address, "ifPhysAddress", to identify the interface. In addition, a given ATM UNI interface may have several other valid addresses which can be used to originate and receive calls. The valid addresses that are used to receive calls are listed in the "ifRcvAddrTable" defined in RFC1573 [6]. ATM interfaces of switches and networks do not use the ifRcvAddrTable. Valid addresses to be used by a switch or network are listed in the ATM Interface Administrative Address Table. The ATM Interface Administrative Address Table is not supported by hosts. 7. Configuration of VPLs, VCLs, and Cross-Connects The ATM Managed Objects needed to support the configuration of VPLs, VCLs, and Cross-Connects are defined in the ATM MIB [1]. 8. Definitions ATM2-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, experimental, Counter32, Integer32, IpAddress Expires XX [Page 12] draft Supplemental ATM Management Objects March 1995 FROM SNMPv2-SMI TEXTUAL-CONVENTION, DisplayString, TimeStamp, RowStatus FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF atmMIBObjects, IfIndex, atmVclEntry, atmVclVpi, atmVclVci FROM ATM-MIB ifIndex FROM RFC1213-MIB; atm2MIB MODULE-IDENTITY LAST-UPDATED "9503231200Z" ORGANIZATION "TBD" CONTACT-INFO " Faye Ly Postal: Bay Networks Inc. 4401 Great America Parkway Santa Clara, CA 95052 US Tel: +1 408 764 1702 Fax: +1 408 988 5525 E-Mail: faye@Baynetworks.COM Michael Noto Postal: Bell Communications Research 331 Newman Springs Road Red Bank, NJ 07701 US Tel: +1 908 758 5104 Fax: +1 908 758 4177 E-mail: noto@cc.bellcore.com Andrew Smith Postal: Bay Networks Inc. 4401 Great America Parkway Santa Clara, CA 95052 US Tel: +1 408 764 1574 Fax: +1 408 988 5525 E-Mail: asmith@Baynetworks.COM Kaj Tesink Postal: Bell Communications Research Expires XX [Page 13] draft Supplemental ATM Management Objects March 1995 331 Newman Springs Road Red Bank, NJ 07701 US Tel: +1 908 758 5254 Fax: +1 908 758 4177 E-mail: kaj@cc.bellcore.com" DESCRIPTION "This MIB Module is a supplement to the ATM-MIB [1]. This MIB provides supplemental information from both a switch/network perspective and an ATM application prospective." ::= { experimental XX } atm2MIBObjects OBJECT IDENTIFIER ::= {atm2MIB 1} -- In case this module is put on the standards track -- replace the following: -- "atm2MIB MODULE-IDENTITY ::= {experimental XX}" with -- "atm2MIB MODULE-IDENTITY ::= {atmMIBObjects 13}" -- and include atmMIBObjects in the IMPORT clause. -- This ATM2-MIB Module consists of the following groups: -- ATM Switch/Network/Host Support: -- (1) ATM Switch/Network/Host Group -- (2) ATM Switch/Network/Host SVC Group -- ATM Switch/Network Support: -- (3) ATM Switch/Network Group -- (4) ATM Switch/Network SVC Group -- ATM Host Support: -- (5) ATM Host Group -- (6) ATM Host SVC Group -- Textual Conventions -- AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The value of this object identifies a row in the atmSigDescrParamTable. " SYNTAX Integer32 Expires XX [Page 14] draft Supplemental ATM Management Objects March 1995 AtmAddress ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The ATM address used by the network entity." SYNTAX OCTET STRING (SIZE(0|20)) Expires XX [Page 15] draft Supplemental ATM Management Objects March 1995 -- **************************************************** -- (1) ATM Switch/Network/Host Group -- This group contains information for a Switch/Network/Host -- that implements ATM interfaces. This group contains -- the following table: -- 1. ATM VCC Statistics Table atmSwtchNetHostGroup OBJECT IDENTIFIER ::= { atm2MIBObjects 1} -- 1. ATM VCC Statistics Table atmVclStatTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmVclStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains all statistic counters per VCC. It is used to monitor the usage of the VCC by cells coming in and going out. This table is an extension to the atmVclTable." ::= { atmSwtchNetHostGroup 1 } atmVclStatEntry OBJECT-TYPE SYNTAX AtmVclStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table represents a VCC. " INDEX { ifIndex, atmVclVpi, atmVclVci } ::= { atmVclStatTable 1 } AtmVclStatEntry ::= SEQUENCE { atmVclStatCellIns Counter32, atmVclStatCellOuts Counter32 } atmVclStatCellIns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current Expires XX [Page 16] draft Supplemental ATM Management Objects March 1995 DESCRIPTION "The value of this object is the number of cells received by this VCC since it is established." ::= { atmVclStatEntry 1 } atmVclStatCellOuts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is the number of cells transmitted from this VCC since it is established." ::= { atmVclStatEntry 2 } Expires XX [Page 17] draft Supplemental ATM Management Objects March 1995 -- **************************************************** -- (2) ATM Switch/Network/Host SVC Group -- This group contains information for a Switch/Network/Host -- that implements ATM interfaces supporting Switched -- Virtual Connections (SVCs). -- This group contains the following tables -- 1. ATM Interface SVC Configuration Table -- 2. ATM SSCOP Table -- 3. ATM Unsupported Service Table -- 4. ATM Signalling Layer Error Table -- 5. ATM Signalling Layer Statistics Table atmSwtchNetHostSVCGroup OBJECT IDENTIFIER::= { atm2MIBObjects 2} -- 1. ATM Interface SVC Configuration Table -- This table provides configuration for ATM -- Switched Virtual Connections (SVCs). atmInterfaceSVCConfTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmInterfaceSVCConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM local interface configuration parameters, one entry per ATM interface port." ::= { atmSwtchNetHostSVCGroup 1 } atmInterfaceSVCConfEntry OBJECT-TYPE SYNTAX AtmInterfaceSVCConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This list contains signalling configuration parameters and state variables." INDEX { ifIndex, atmInterfaceSVCSigVpi, atmInterfaceSVCSigVci } ::= { atmInterfaceSVCConfTable 1} AtmInterfaceSVCConfEntry ::= SEQUENCE { atmInterfaceSVCSigVpi INTEGER, atmInterfaceSVCSigVci INTEGER, atmInterfaceSVCSigType INTEGER, Expires XX [Page 18] draft Supplemental ATM Management Objects March 1995 atmInterfaceSVCTimerT302 INTEGER, atmInterfaceSVCTimerT310 INTEGER, atmInterfaceSVCTimerT317 INTEGER } atmInterfaceSVCSigVpi OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VPI value used by this signalling entity." DEFVAL { 0 } ::= { atmInterfaceSVCConfEntry 1} atmInterfaceSVCSigVci OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS not-accessible STATUS current DESCRIPTION "The VCI value used by this signalling entity." DEFVAL { 5 } ::= { atmInterfaceSVCConfEntry 2} atmInterfaceSVCSigType OBJECT-TYPE SYNTAX INTEGER { other(1), qDOT2931(2), uni3DOT0(3),uni3DOT1(4), pnni(5) } MAX-ACCESS read-write STATUS current DESCRIPTION "This parameter identifies the type of signalling that will be used for the identified interface. Q.2931: This is the signalling type defined in ITU-T Recommendation Q.2931, Broadband Integrated Service Digital Network (B-ISDN) Digital Service Signalling System No.2 (DSS2) User-Network Interface (UNI) Layer 3 Specification for Basic Call/Connection Control (September 1994) [11]. -- Update this reference when the May 1995 -- version is accepted Expires XX [Page 19] draft Supplemental ATM Management Objects March 1995 UNI 3.0: This is the signalling type defined in ATM Forum, ATM User-Network Interface, Version 3.0 (UNI 3.0) Specification, Part I (1994) [9]. UNI 3.1: This is the signalling type defined in ATM Forum, ATM User-Network Interface, Version 3.1 (UNI 3.1) Specification, Part I (November 1994) [10]. P-NNI : This is the signalling type defined for a Private Network-to-Network Interface in ATM Forum 94-0471R4, P-NNI Draft Specification, P-NNI SWG (November 1994) [12]. -- Update this reference when the draft matures" ::= { atmInterfaceSVCConfEntry 3} atmInterfaceSVCTimerT302 OBJECT-TYPE SYNTAX INTEGER (10..15) UNITS "Seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Applicable to both Hosts and Switches. This timer starts when a SETUP ACKNOWLEDGE message is sent. The normal cause for stopping is when sending a complete indication, or network alert or connect request received. At first expiry clear if call information determined to be definitely incomplete; else send a CALL PROCEEDING. The range of this timer is defined in Q.2931 as 10-15 seconds. T302 is a Mandatory timer only if Q.2931 Section 6.5 'Overlap Sending and Receiving' is implemented. Note: The ATM Forum UNI 3.1 does not support this timer." ::= { atmInterfaceSVCConfEntry 4} atmInterfaceSVCTimerT310 OBJECT-TYPE Expires XX [Page 20] draft Supplemental ATM Management Objects March 1995 SYNTAX INTEGER (10..120) UNITS "Seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Applicable to both Hosts and Switches. This timer starts when a CALL PROCEEDING message is received. The normal cause for stopping is when an ALERTing, CONNECT, or RELEASE message is received. At first expiry a RELEASE message is sent. The range of this timer from 10-120 seconds since Q.2931 recommends a default value of 10 seconds for Networks and 30-120 seconds for Users, while the ATM Forum's UNI 3.1 Specification recommends a default value of 10 seconds for both Networks and Users. T310 is a Mandatory timer. Note: The ALERTing message is only defined in Q.2931. The ATM Forum UNI 3.1 Specification does not support this message." ::= { atmInterfaceSVCConfEntry 5} atmInterfaceSVCTimerT317 OBJECT-TYPE SYNTAX INTEGER (0..119) UNITS "Seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Applicable to both Hosts and Switches. This timer starts when a RESTART message is received. The normal cause for stopping this timer is when there is an internal clearing of call references. At first expiry there is a maintenance notification. The range of this timer is less than the value of Timer T316 (i.e., less than 2 minutes). T317 is a Mandatory timer. " ::= { atmInterfaceSVCConfEntry 6} -- 2. ATM SSCOP Table -- This table contains objects that provide information -- on the SSCOP (Service Specific Connection -- Oriented Protocol). atmSSCOPTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmSSCOPEntry MAX-ACCESS not-accessible Expires XX [Page 21] draft Supplemental ATM Management Objects March 1995 STATUS current DESCRIPTION "This table contains SSCOP parameters, one entry per ATM interface port." ::= { atmSwtchNetHostSVCGroup 2} atmSSCOPEntry OBJECT-TYPE SYNTAX AtmSSCOPEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This list contains SSCOP parameters ." INDEX { ifIndex } ::= { atmSSCOPTable 1} AtmSSCOPEntry ::= SEQUENCE { atmSSCOPConMontrCounts Counter32, atmSSCOPErrdPduCounts Counter32 } atmSSCOPConMontrCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "SSCOP Connection Monitoring Counter. This counter counts the sum of the following errors: 1) SSCOP Connection Disconnect Counter The abnormal occurrence of this event is characterized by the expiry of Timer_NO_RESPONSE. (This event is communicated to the layer management with MAA-ERROR code P. See Q.2110 [13].) 2) SSCOP Connection Initiation Failure This condition indicates the inability to establish an SSCOP connection. This event occurs whenever the number of expiries of the connection control timer (Timer_CC) exceeds the MaxCC or upon receipt of a connection reject message BGREJ PDU. (This event is communicated to layer management with MAA-ERROR code O. See Q.2110.) Expires XX [Page 22] draft Supplemental ATM Management Objects March 1995 3) SSCOP Connection Re-Establ/Resynch This event occurs upon receipt of a BGN PDU or RESYNC PDU." ::= { atmSSCOPEntry 1} atmSSCOPErrdPduCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "SSCOP Errored PDUs Counter. This counter counts the sum of the following errors: 1) Invalid PDUs. These are defined in SSCOP and consist of PDUs with incorrect length (MAA-ERROR code U), undefined PDU type code or not 32-bit aligned. 2) PDUs that result in MAA error codes and are discarded See Errors A-M and Q-T defined in Q.2110 [13]." ::= { atmSSCOPEntry 2} -- 3. ATM Unsupported Service Table -- This table contains counters which -- monitor Unsupported Service Requests. atmUnsuptServTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmUnsuptServEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains unsupported service requests, one entry per ATM interface port." ::= { atmSwtchNetHostSVCGroup 3 } atmUnsuptServEntry OBJECT-TYPE SYNTAX AtmUnsuptServEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This list contains three counters of unsupported service requests." INDEX { ifIndex } Expires XX [Page 23] draft Supplemental ATM Management Objects March 1995 ::= { atmUnsuptServTable 1} AtmUnsuptServEntry ::= SEQUENCE { atmUnsuptServRouteUnavails Counter32, atmUnsuptServResrcUnavails Counter32, atmUnsuptServCldPrtyCounts Counter32 } atmUnsuptServRouteUnavails OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Route Unavailable Counter. This counter counts the sum of the following errors: Cause Value Meaning 1 unallocated (unassigned) number 2 no route to specified transit network 3 no route to destination 88 incompatible destination" ::= { atmUnsuptServEntry 1} atmUnsuptServResrcUnavails OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Resource Unavailability Counter. This counter counts the sum of the following errors: Cause Value Meaning 27 destination out of order 35 requested VPCI/VCI not available 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available 58 bearer capability not presently available 63 Service or option not available, unspecified Expires XX [Page 24] draft Supplemental ATM Management Objects March 1995 92 too many pending add party requests" ::= { atmUnsuptServEntry 2} atmUnsuptServCldPrtyCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Called Party Responsible For Unsuccessful Call Counter. This counter counts the sum of the following errors: Cause Value Meaning 17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line id restriction (CLIR) 31 normal, unspecified Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure" ::= { atmUnsuptServEntry 3} -- 4. ATM Signalling Layer Protocol Error Table -- This table contains objects that provide information on -- ATM signalling layer protocol errors atmSigLyrErrTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmSigLyrErrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table monitors protocol errors at the signalling layer." ::= { atmSwtchNetHostSVCGroup 4 } atmSigLyrErrEntry OBJECT-TYPE SYNTAX AtmSigLyrErrEntry MAX-ACCESS not-accessible STATUS current Expires XX [Page 25] draft Supplemental ATM Management Objects March 1995 DESCRIPTION "An entry in atmSigLyrErrTable." INDEX { ifIndex } ::= { atmSigLyrErrTable 1} AtmSigLyrErrEntry ::= SEQUENCE { atmSigLyrErrIncrtMesgCounts Counter32, atmSigLyrErrTimerExprCounts Counter32, atmSigLyrErrRestartCounts Counter32 } atmSigLyrErrIncrtMesgCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Incorrect Messages Counter. The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, DROP PARTY, and STATUS messages transmitted or received, that contain any of the Cause values listed below. - Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: 1. Message with invalid protocol discriminator 2. Message with errors in the call reference I.E. - Bits 5-8 of the first octet not equal to '0000' - Bits 1-4 of the first octet indicating a length other than 3 octets - RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress - SETUP message received with call reference flag incorrectly set to 1 - SETUP message received with a call reference for a call that is already active or in progress. Expires XX [Page 26] draft Supplemental ATM Management Objects March 1995 3. Message too short The following cause values are monitored by this counter: Cause Value Meaning 10 VPCI/VCI unacceptable 28 invalid number format (address incomplete) 43 access information discarded 57 bearer capability not authorized 65 bearer capability not implemented 73 unsupported combination of traffic parameters 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 91 invalid transit network selection 93 AAL parameters cannot be supported 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted." ::= { atmSigLyrErrEntry 1} atmSigLyrErrTimerExprCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Timer Expiries Counter. The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The Expires XX [Page 27] draft Supplemental ATM Management Objects March 1995 conditions for incrementing this counter are: - Expiry of any network timer - Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, 'recovery on timer expiry'. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted." ::= { atmSigLyrErrEntry 2} atmSigLyrErrRestartCounts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Restart Activity Counter. The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when receiving or transmitting a RESTART message. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted." ::= { atmSigLyrErrEntry 3} -- 5. ATM Signalling Sub-layer Statistics Table -- This table provides objects to manage the number of -- incoming and outgoing VCLs per signalling entity. atmIfSigStatTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmIfSigStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains all VCL connection counts for all signalling layer this agent manages." ::= { atmSwtchNetHostSVCGroup 5 } Expires XX [Page 28] draft Supplemental ATM Management Objects March 1995 atmIfSigStatEntry OBJECT-TYPE SYNTAX AtmIfSigStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table represents a signalling entity. Each entry contains information such as the number of calls established." INDEX { ifIndex, atmInterfaceSVCSigVpi, atmInterfaceSVCSigVci } ::= { atmIfSigStatTable 1 } AtmIfSigStatEntry ::= SEQUENCE { atmIfSigInEstablished Counter32, atmIfSigOutEstablished Counter32 } atmIfSigInEstablished OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of VCLs established at this signalling entity. The value of this object is the incoming connections." ::= { atmIfSigStatEntry 1 } atmIfSigOutEstablished OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of VCLs established at this signalling entity. The value of this object is the outgoing connections." ::= { atmIfSigStatEntry 2 } Expires XX [Page 29] draft Supplemental ATM Management Objects March 1995 -- **************************************************** -- (3) ATM Switch/Network Group -- This group contains information for a Switch/Network -- that implements ATM interfaces. This group contains -- the following table: -- 1. ATM Interface Administrative Address Table atmSwtchNetGroup OBJECT IDENTIFIER::= { atm2MIBObjects 3} -- 1. ATM Interface Administrative Address Table -- This table contains a list of the valid calling party -- addresses for a UNI in the case of both PVCs and SVCs. -- For PVCs, if addresses are not used then an entry in -- this table is not necessary. This list is to be used with -- the calling party number screening feature. atmIfAdminAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmIfAdminAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains an address list on a per interface basis. This table only applies to switches or networks and only for interfaces that have more than one address assigned." ::= { atmSwtchNetGroup 1 } atmIfAdminAddrEntry OBJECT-TYPE SYNTAX AtmIfAdminAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the atmIfAdminAddrTable." INDEX { ifIndex, atmIfAdminAddrAddress } ::= { atmIfAdminAddrTable 1} AtmIfAdminAddrEntry ::= SEQUENCE { atmIfAdminAddrAddress OCTET STRING, atmIfAdminAddrRowStatus RowStatus } atmIfAdminAddrAddress OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..255)) Expires XX [Page 30] draft Supplemental ATM Management Objects March 1995 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A valid address for a given switch or network interface." ::= { atmIfAdminAddrEntry 1} atmIfAdminAddrRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used to create and delete rows in the atmIfAdminAddrTable." ::= { atmIfAdminAddrEntry 2} Expires XX [Page 31] draft Supplemental ATM Management Objects March 1995 -- **************************************************** -- (4) ATM Switch/Network SVC Group -- This group contains information for a Switch/Network -- that implements ATM interfaces supporting Switched -- Virtual Connections (SVCs). This group contains -- the following table: -- 1. ATM Subscription Feature Table atmSwtchNetSVCGroup OBJECT IDENTIFIER::= { atm2MIBObjects 4} -- 1. ATM Subscription Feature Table -- This table contains objects used to manage -- ATM Subscription Features. atmSubscrFeaturTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmSubscrFeaturEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains ATM local interface subscription feature parameters, one entry per ATM interface port." ::= { atmSwtchNetSVCGroup 1 } atmSubscrFeaturEntry OBJECT-TYPE SYNTAX AtmSubscrFeaturEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This list contains ATM subscription feature parameters." INDEX { ifIndex } ::= { atmSubscrFeaturTable 1} AtmSubscrFeaturEntry ::= SEQUENCE { atmSubscrFeaturClgPtyNumDel INTEGER, atmSubscrFeaturClgPtyNumScr INTEGER, atmSubscrFeaturClgPtyFailScrCnts Counter32, atmSubscrFeaturClgPtySubAddrTrans INTEGER, atmSubscrFeaturCldPtySubAddrTrans INTEGER, atmSubscrFeaturHiLyrInfoTrans INTEGER, atmSubscrFeaturLoLyrInfoTrans INTEGER, Expires XX [Page 32] draft Supplemental ATM Management Objects March 1995 atmSubscrFeaturLoLyrInfoSel INTEGER, atmSubscrFeaturAALInfoTrans INTEGER, atmSubscrFeaturPrefCarrier OCTET STRING } atmSubscrFeaturClgPtyNumDel OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This parameter indicates whether the Calling Party Number Information Element is forwarded to the called party address. The value of this parameter can be: - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not turned on (i.e., not subscribed to)." DEFVAL { disabled } ::= { atmSubscrFeaturEntry 1} atmSubscrFeaturClgPtyNumScr OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This parameter indicates whether screening of a calling party number received in a SETUP or ADD PARTY message is enabled on the switch or network. With screening, the switch or network checks the Calling Party Number Information Element in the received SETUP or ADD PARTY message to verify that it is one of the valid addresses listed in the atmInterfaceAdminAddress defined in the ATM MIB [1] or the atmIfAdminAddrTable. If the check fails the switch or network will replace the calling party number with the default number for the interface (atmInterfaceAdminAddress) before forwarding this to the called party. This will result in a completed call, but the delivered calling party number will not be the number desired by the calling party. The value of this parameter can be: - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not Expires XX [Page 33] draft Supplemental ATM Management Objects March 1995 turned on (i.e., not subscribed to)." DEFVAL { enabled } ::= { atmSubscrFeaturEntry 2} atmSubscrFeaturClgPtyFailScrCnts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-write STATUS current DESCRIPTION "This is a counter to keep track of the calling party numbers that fail screening. If the calling party number screening feature is enabled (i.e., if atmSubscrFeaturClgPtyNumScr = enabled(1)), and the Calling Party Number Information Element includes a calling party number in the SETUP or ADD PARTY signalling messages, the switch or network checks its list to validate the received calling party number. If the calling party number is not one of the allowable numbers, the switch or network substitutes the default number for the calling party number that failed screening and increments the counter." ::= { atmSubscrFeaturEntry 3} atmSubscrFeaturClgPtySubAddrTrans OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The calling party subaddress transfer feature. This parameter indicates whether to accept and transfer the Calling Party Subaddress Information Element from the calling party to the called party. Calling party subaddress information shall only be forwarded to the called party if the calling party number delivery feature is enabled (i.e., atmSubscrFeaturClgPtyNumDel = 'enabled(1)'. The value of this parameter can be: - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not turned on (i.e., not subscribed to)." DEFVAL { disabled } ::= { atmSubscrFeaturEntry 4} atmSubscrFeaturCldPtySubAddrTrans OBJECT-TYPE Expires XX [Page 34] draft Supplemental ATM Management Objects March 1995 SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The called party subaddress transfer feature. This parameter indicates whether to accept, transfer, and deliver the Called Party Subaddress Information Element from the calling party to the called party. The value of this parameter can be: - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not turned on (i.e., not subscribed to)." DEFVAL { disabled } ::= { atmSubscrFeaturEntry 5} atmSubscrFeaturHiLyrInfoTrans OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The high layer information transfer feature. This parameter indicates whether to accept, transfer, and deliver the Broadband High Layer Information Element from the calling party to the called party. The value of this parameter can be: - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not turned on (i.e., not subscribed to)." DEFVAL { disabled } ::= { atmSubscrFeaturEntry 6} atmSubscrFeaturLoLyrInfoTrans OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The low layer information transfer feature. This parameter indicates whether to accept, transfer, and deliver the Broadband Low Layer Information Element from the calling party to the called party. The value of this parameter can be: Expires XX [Page 35] draft Supplemental ATM Management Objects March 1995 - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not turned on (i.e., not subscribed to)." DEFVAL { disabled } ::= { atmSubscrFeaturEntry 7} atmSubscrFeaturLoLyrInfoSel OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The low layer information selection feature. This parameter indicates whether to accept, transfer, and deliver up to three instances of the Broadband Low Layer Information Element for low layer information selection from the calling party to the called party. This feature may be supplied only if atmSubscrFeaturLoLyrInfoTrans = 'enabled(1)'. The value of this parameter can be: - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not turned on (i.e., not subscribed to)." DEFVAL { disabled } ::= { atmSubscrFeaturEntry 8} atmSubscrFeaturAALInfoTrans OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The AAL parameter information transfer feature. This parameter indicates whether to accept, transfer, and deliver the ATM Adaptation Layer Parameters Information Element from the calling party to the called party. The value of this parameter can be: - enabled(1) The feature is supported and turned on (i.e., subscribed to) - disabled(2) The feature is not supported or not turned on (i.e., not subscribed to)." DEFVAL { disabled } Expires XX [Page 36] draft Supplemental ATM Management Objects March 1995 ::= { atmSubscrFeaturEntry 9} atmSubscrFeaturPrefCarrier OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS current DESCRIPTION "This parameter identifies the carrier to which intercarrier calls originated from this interface are routed when transit network selection information is not provided by the calling party. If a Carrier Identification Code (CIC) is used the parameter shall contain the CIC. For three-digit CICs, the first octet shall be '0' and the CIC is contained in the three following octets. If the preferred carrier feature is not supported the value is a zero-length string." ::= { atmSubscrFeaturEntry 10} Expires XX [Page 37] draft Supplemental ATM Management Objects March 1995 -- **************************************************** -- (5) ATM Host Group -- This group contains information for a Host -- that implements ATM interfaces. The following -- two tables are included in this group: -- 1. ATM VCL Extension Table -- 2. ATM Addresses to VPI/VCI Mapping Table atmHostGroup OBJECT IDENTIFIER::= {atm2MIBObjects 5} -- 1. ATM VCL Extension Table atmVclExtTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmVclExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table is an extension to the atmVclTable. It provides additional information necessary for VCLs management. Additional information included in this table are remote and local ATM addresses, the requested signalling interface number and the type of the VCL." ::= { atmHostGroup 1 } atmVclExtEntry OBJECT-TYPE SYNTAX AtmVclExtEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table represents an extension to the atmVclTable. Objects atmVclConnType and atmVclSigDescrIndex are required during a creation of an entry in the atmVclTable." AUGMENTS { atmVclEntry } ::= { atmVclExtTable 1 } AtmVclExtEntry ::= SEQUENCE { atmVclRemoteAtmAddr AtmAddress, atmVclLocalAtmAddr AtmAddress, atmVclConnType Expires XX [Page 38] draft Supplemental ATM Management Objects March 1995 INTEGER, atmVclSigDescrIndex AtmSigDescrParamIndex } atmVclRemoteAtmAddr OBJECT-TYPE SYNTAX AtmAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The ATM address on the remote end of the VCL. When not specified, the value of this object is a zero length string. For SVCs, agent supplies the value of this object at creation time. For PVCs, manager can supply the value of this object during or after the PVC creation. Manager can modify the value of this object for PVC entries only." ::= { atmVclExtEntry 1 } atmVclLocalAtmAddr OBJECT-TYPE SYNTAX AtmAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The ATM address on the local end of the VCL. When not specified, the value of this object is a zero length string. For SVCs, agent supplies the value of this object at creation time. For PVCs, manager can supply the value of this object during or after the PVC creation. Manager can modify the value of this object for PVC entries only." DEFVAL { ''H } ::= { atmVclExtEntry 2 } atmVclConnType OBJECT-TYPE SYNTAX INTEGER { pvc(1), -- Permanent VC svcIncoming(2), -- Switched VC, incoming svcOutgoing(3) -- Switched VC, outgoing } MAX-ACCESS read-create STATUS current DESCRIPTION "The type of the VCL. It is either Permanent VC, Switched VC incoming or Switched VC outgoing. This Expires XX [Page 39] draft Supplemental ATM Management Objects March 1995 object cannot be modified once created." ::= { atmVclExtEntry 3 } atmVclSigDescrIndex OBJECT-TYPE SYNTAX AtmSigDescrParamIndex MAX-ACCESS read-create STATUS current DESCRIPTION "The value of this object identifies the row in the ATM Signalling Descriptor Table which applies to this VCL." ::= { atmVclExtEntry 4 } -- 2. ATM Addresses to VPI/VCI Mapping Table -- This table provides an alternative way to access -- a row in the atmVclTable of the ATM MIB [1] by -- using the remote address as an index, instead of -- the ifIndex atmVclAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmVclAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides an alternative way to retrieve the atmVclTable. This table can be used to retrieve the indexing to the atmVclTable by the Remote ATM address." ::= { atmHostGroup 2 } atmVclAddrEntry OBJECT-TYPE SYNTAX AtmVclAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table represents an entry in the atmVclTable by it's Remote ATM address. Entries in this table are read only. They show up when entries are created in the atmVclTable. The ifIndex used in the INDEX clause refers to the ATM interface number (ifIndex in the atmInterfaceTable) this VCL pertains to." INDEX { atmVclRemoteAtmAddr, atmVclAddrIndex } ::= { atmVclAddrTable 1 } Expires XX [Page 40] draft Supplemental ATM Management Objects March 1995 AtmVclAddrEntry ::= SEQUENCE { atmVclAddrIndex Integer32, atmVclAddrAtmIfIndex IfIndex, atmVclAddrVpi INTEGER, atmVclAddrVci INTEGER } atmVclAddrIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object is a number assigned by agent to uniquely identifies a single entry under a certain Remote ATM Address. That is, there can be multiple VCLs to a single Remote ATM address on a given ATM interface, the value of this object uniquely identifies each of them." ::= { atmVclAddrEntry 1 } atmVclAddrAtmIfIndex OBJECT-TYPE SYNTAX IfIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The interface index of the ATM interface where this VCL pertains to. This object with atmVclAddrVpi and atmVclAddrVci serve as an index to the atmVclTable." ::= { atmVclAddrEntry 2 } atmVclAddrVpi OBJECT-TYPE SYNTAX INTEGER (0..4095) MAX-ACCESS read-only STATUS current DESCRIPTION "The VPI value of the VCL. This object with atmVclAddrAtmIfIndex and atmVclAddrVci serve as an index to the atmVclTable." ::= { atmVclAddrEntry 3 } Expires XX [Page 41] draft Supplemental ATM Management Objects March 1995 atmVclAddrVci OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The VCI value of the VCL. This object with atmVclAddrAtmIfIndex and atmVclAddrVpi serve as an index to the atmVclTable." ::= { atmVclAddrEntry 4 } Expires XX [Page 42] draft Supplemental ATM Management Objects March 1995 -- **************************************************** -- (6) ATM Host SVC Group -- This group contains information for a Host -- that implements ATM interfaces supporting Switched -- Virtual Connections (SVCs). This group includes the -- following table: -- 1. ATM Signalling Descriptor Parameter Table atmHostSVCGroup OBJECT IDENTIFIER::= {atm2MIBObjects 6} -- 1. ATM Signalling Descriptor Parameter Table -- This table contains object to provides signalling -- capabilities of VCLs. atmSigDescrParamTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmSigDescrParamEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table contains signalling capabilities of VCLs except the Traffic Descriptor. Traffic descriptors are described in the atmTrafficDescrParamTable." REFERENCE "ATM User-Network Interface Specification, Version 3.0, Section 5.4.5 Variable Length Information Elements." ::= { atmHostSVCGroup 1 } atmSigDescrParamEntry OBJECT-TYPE SYNTAX AtmSigDescrParamEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table represents a set of signalling capabilities that can be applied to a VCL. Objects atmSigDescrParamRowStatus is required during creation." INDEX { atmSigDescrParamIndex } ::= { atmSigDescrParamTable 1 } AtmSigDescrParamEntry ::= SEQUENCE { atmSigDescrParamIndex Expires XX [Page 43] draft Supplemental ATM Management Objects March 1995 AtmSigDescrParamIndex, atmSigDescrParamAalType INTEGER, atmSigDescrParamAalMode INTEGER, atmSigDescrParamAalSscsType INTEGER, atmSigDescrParamBhliType INTEGER, atmSigDescrParamBhliInfo OCTET STRING, atmSigDescrParamBbcClass INTEGER, atmSigDescrParamBbcTraffic INTEGER, atmSigDescrParamBbcTiming INTEGER, atmSigDescrParamBbcClipping INTEGER, atmSigDescrParamBbcConnConf INTEGER, atmSigDescrParamBlliLayer2 INTEGER, atmSigDescrParamBlliLayer3 INTEGER, atmSigDescrParamBlliPktSize INTEGER, atmSigDescrParamBlliSnapId INTEGER, atmSigDescrParamBlliOuiPid OCTET STRING, atmSigDescrParamRowStatus RowStatus } atmSigDescrParamIndex OBJECT-TYPE SYNTAX AtmSigDescrParamIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of this object is used by the atmVclExtTable to identify a row in this table." ::= { atmSigDescrParamEntry 1 } atmSigDescrParamAalType OBJECT-TYPE Expires XX [Page 44] draft Supplemental ATM Management Objects March 1995 SYNTAX INTEGER { other(1), -- not defined aal1(2), -- AAL type 1 aal34(3), -- AAL type 3/4 aal5(4), -- AAL type 5 userDefined(5) -- User-Defined AAL } MAX-ACCESS read-create STATUS current DESCRIPTION "The AAL type. The value of this object is set to other(1) when not defined." DEFVAL { other } ::= { atmSigDescrParamEntry 2 } atmSigDescrParamAalMode OBJECT-TYPE SYNTAX INTEGER { other(1), -- not defined msg(2), -- Message mode stream(3) -- Streaming mode } MAX-ACCESS read-create STATUS current DESCRIPTION "The AAL mode. The value of this object is other(1) when atmSigDescrParamAalType is aal1(2). Values msg(2) and stream(3) are only applicable when atmSigDescrParamAalType is set to aal34(3) or aal5(4). This object is applicable to UNI 3.0 only." DEFVAL { other } ::= { atmSigDescrParamEntry 3 } atmSigDescrParamAalSscsType OBJECT-TYPE SYNTAX INTEGER { other(1), -- other, or not used assured(2), -- Data SSCS based on SSCOP -- assured operation nonassured(3), -- Data SSCS based on SSCOP -- non-assured operation frameRelay(4) -- frame relay SSCS } MAX-ACCESS read-create STATUS current DESCRIPTION Expires XX [Page 45] draft Supplemental ATM Management Objects March 1995 "The SSCS type used by this entry." DEFVAL { other } ::= { atmSigDescrParamEntry 4 } atmSigDescrParamBhliType OBJECT-TYPE SYNTAX INTEGER { other(1), -- not defined iso(2), -- ISO user(3), -- User specific hiProfile(4), -- Higher layer profile -- this enum applicable to -- UNI 3.0 only vendorSpecific(5) -- Vender specific application -- identifier } MAX-ACCESS read-create STATUS current DESCRIPTION "The Broadband high layer type." DEFVAL { other } ::= { atmSigDescrParamEntry 5 } atmSigDescrParamBhliInfo OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..7)) MAX-ACCESS read-create STATUS current DESCRIPTION "The Broadband high layer information. When atmSigDescrParamBhliType is set to iso(2), the value of this object is a zero length string. When atmSigDescrParamBhliType is set to hiProfile(4), the value of this object is a length of 4 octet string containing user to user profile identifier. When atmSigDescrParamBhliType is set to vendorSpecific(4), the value of this object is a length of 7 octet string. The most significant 3 octets consist of a globally- administered OUI, the least significant 4 octets are the vender administered application OUI." DEFVAL { ''H } ::= { atmSigDescrParamEntry 6 } atmSigDescrParamBbcClass OBJECT-TYPE SYNTAX INTEGER { other(1), -- not defined or unspecified Expires XX [Page 46] draft Supplemental ATM Management Objects March 1995 bcoba(2), -- BCOB-A bcobc(3), -- BCOB-C bcobx(4) -- BCOB-X } MAX-ACCESS read-only STATUS current DESCRIPTION "The Broadband bearer capability class." ::= { atmSigDescrParamEntry 7 } atmSigDescrParamBbcTraffic OBJECT-TYPE SYNTAX INTEGER { other(1), -- not defined noIndication(2), -- No indication cbr(3), -- Constant bit rate vbr(4) -- Variable bit rate } MAX-ACCESS read-only STATUS current DESCRIPTION "The Broadband bearer capability traffic type." ::= { atmSigDescrParamEntry 8 } atmSigDescrParamBbcTiming OBJECT-TYPE SYNTAX INTEGER { other(1), -- not specified noIndication(2), -- No Indication required(3), -- end-to-end timing required notReq(4) -- end-to-end timing not -- required } MAX-ACCESS read-only STATUS current DESCRIPTION "The Broadband bearer capability timing requirements." ::= { atmSigDescrParamEntry 9 } atmSigDescrParamBbcClipping OBJECT-TYPE SYNTAX INTEGER { other(1), -- not specified true(2), -- not susceptible to -- clipping false(3) -- susceptible to clipping } Expires XX [Page 47] draft Supplemental ATM Management Objects March 1995 MAX-ACCESS read-only STATUS current DESCRIPTION "The Broadband bearer capability susceptibility to clipping parameter." ::= { atmSigDescrParamEntry 10 } atmSigDescrParamBbcConnConf OBJECT-TYPE SYNTAX INTEGER { ptp(1), -- point-to-point ptmp(2) -- point-to-multipoint } MAX-ACCESS read-only STATUS current DESCRIPTION "The Broadband bearer capability user plane connection configuration parameter." ::= { atmSigDescrParamEntry 11 } atmSigDescrParamBlliLayer2 OBJECT-TYPE SYNTAX INTEGER { other(1), -- not specified iso1745(2), -- Basic mode ISO 1745 q921(3), -- CCITT Recommendation Q.921 x25linklayer(4), -- CCITT Recommendation X.25 -- Link Layer x25multilink(5), -- CCITT Recommendation X.25 -- Multilink lapb(6), -- Extended LAPB; for half -- duplex operation hdlcArm(7), -- HDLC ARM (ISO 4335) hdlcNrm(8), -- HDLC NRM (ISO 4335) hdlcAbm(9), -- HDLC ABM (ISO 4335) iso88022(10), -- LAN logical link control -- (ISO 8802/2) x75slp(11), -- CCITT Recommendation X.75, -- single link -- procedure (SLP) q922(12), -- CCITT Recommendation Q.922 userDef(13), -- User specified iso7776(14) -- ISO 7776 DTE-DTE operation } MAX-ACCESS read-create STATUS current DESCRIPTION Expires XX [Page 48] draft Supplemental ATM Management Objects March 1995 "The Broadband low layer information, protocol type of layer 2. The value of this object is other(1) if layer 2 protocol is not used." DEFVAL { other } ::= { atmSigDescrParamEntry 12 } atmSigDescrParamBlliLayer3 OBJECT-TYPE SYNTAX INTEGER { other(1), -- not specified x25pkt(2), -- CCITT Recommendation X.25 -- packet layer isoiec8208(3), -- ISO/IEC 8208 (X.25 packet -- level protocol for data -- terminal equipment) x223iso8878(4), -- X.223/ISO 8878 isoiec8473(5), -- ISO/IEC 8473 OSI -- connectionless -- mode protocol t70(6), -- CCITT Recommendation T.70 -- minimum -- network layer tr9577(7), -- ISO/IEC TR 9577 Protocol -- Identification in the -- network layer userDef(8) -- user specified } MAX-ACCESS read-create STATUS current DESCRIPTION "The Broadband low layer information, protocol type of layer 3. The value of this object is other(1) if layer 3 protocol is not used." DEFVAL { other } ::= { atmSigDescrParamEntry 13 } atmSigDescrParamBlliPktSize OBJECT-TYPE SYNTAX INTEGER { other(1), -- not used s16(2), -- 16 octets s32(3), -- 32 octets s64(4), -- 64 octets s128(5), -- 128 octets s256(6), -- 256 octets s512(7), -- 512 octets s1024(8), -- 1028 octets Expires XX [Page 49] draft Supplemental ATM Management Objects March 1995 s2048(9), -- 2048 octets s4096(10) -- 4096 octets } MAX-ACCESS read-create STATUS current DESCRIPTION "The default packet size defined in B-LLI." DEFVAL { other } ::= { atmSigDescrParamEntry 14 } atmSigDescrParamBlliSnapId OBJECT-TYPE SYNTAX INTEGER { other(1), -- not used true(2), -- SNAP ID is 1 false(3) -- SNAP ID is 0 } MAX-ACCESS read-create STATUS current DESCRIPTION "The SNAP ID used for Broadband low layer protocol layer 3. The value of this object is other(1) if atmSigDescrParamBlliLayer3 is set to other(1)." DEFVAL { other } ::= { atmSigDescrParamEntry 15 } atmSigDescrParamBlliOuiPid OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..5)) MAX-ACCESS read-create STATUS current DESCRIPTION "The OUT/PID encoding for Broadband low layer protocol layer 3. The value of this object is a zero length string if atmSigDescrParamBlliLayer3 is set to none(1). When used, it is always 5 octets with the most significant octet as the OUI Octet 1 and the least significant octet as the PID Octet 2." DEFVAL { ''H } ::= { atmSigDescrParamEntry 16 } atmSigDescrParamRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION Expires XX [Page 50] draft Supplemental ATM Management Objects March 1995 "This object is used to create and delete rows in the atmSigDescrParamTable. Writable values are: -'createAndWait' which allows manager to create an entry first and fill in the parameters later. -'active' which allows manager to set the entry to be available to users. -'destroy' which allows manager to delete an entry from this table. Readable values are: -'createAndWait' which means the entry is created but not available to be used. -'active' means it is active and ready to be used by agent or manager." ::= { atmSigDescrParamEntry 17 } Expires XX [Page 51] draft Supplemental ATM Management Objects March 1995 -- **************************************************** -- (7) ATM VP Interface Configuration Group -- This group contains information for interfaces -- supporting the ILMI-over-VPC scenario. -- This group includes the following table: -- 1. ATM VP Interface Configuration Table atmVPIfConfGroup OBJECT IDENTIFIER::= {atm2MIBObjects 7} -- 1. ATM VP Interface Configuration Table -- This table contains objects to provide the ILMI -- and neighbor information for the ILMI-over-VPC -- scenario. atmVPInterfaceConfTable OBJECT-TYPE SYNTAX SEQUENCE OF atmVPInterfaceConfEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The ILMI and neighbor information for the ILMI- over-VPC scenario." ::= { atmVPIfConfGroup 1 } atmVPInterfaceConfEntry OBJECT-TYPE SYNTAX AtmVPInterfaceConfEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "An entry with ILMI and Neighbor information." AUGMENTS { atmVplEntry } ::= { atmVPInterfaceConfEntryTable 1 } AtmVPInterfaceConfEntry ::= SEQUENCE { atmVplIlmiVci INTEGER, atmVplInterfaceMyNeighborIpAddress IpAddress, atmVplInterfaceMyNeighborIfName DisplayString } atmVplIlmiVci OBJECT-TYPE SYNTAX INTEGER Expires XX [Page 52] draft Supplemental ATM Management Objects March 1995 ACCESS read-write STATUS mandatory DESCRIPTION "The VCI value of the VPC supporting the ILMI at this VPL interface. If the value is zero then the ILMI is not supported at this VPL interface." DEFVAL { 0 } ::= { AtmVPInterfaceConfEntry 1 } atmVplInterfaceMyNeighborIpAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-write STATUS mandatory DESCRIPTION "The IP address of the neighbor system connected to the far end of this VPL interface, to which a Network Management Station can send SNMP messages, as IP datagrams sent to UDP port 161, in order to access network management information concerning the operation of that system. Note that the value of this object may be obtained in different ways, e.g., by manual configuration, or through ILMI interaction with the neighbor system." ::= { AtmVPInterfaceConfEntry 2 } atmVplInterfaceMyNeighborIfName OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "The textual name of the interface on the neighbor system on the far end of this VPL interface, and to which this interface connects. If the neighbor system is manageable through SNMP and supports the object ifName, the value of this object must be identical with that of ifName for the ifEntry of the lowest level physical interface for this port. If this interface does not have a textual name, the value of this object is a zero length string. Note that the value of this object may be obtained in different ways, e.g., by manual configuration, or through ILMI interaction with the neighbor system." ::= { AtmVPInterfaceConfEntry 3 } Expires XX [Page 53] draft Supplemental ATM Management Objects March 1995 -- ************************************************ -- Conformance Information atm2MIBConformance OBJECT IDENTIFIER ::= {atm2MIB 2} atm2MIBGroups OBJECT IDENTIFIER ::= {atm2MIBConformance 1} atm2MIBCompliances OBJECT IDENTIFIER ::= {atm2MIBConformance 2} -- Compliance Statements atm2MIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which represent ATM interfaces. The compliance statements are used to determine if a particular group or object applies to hosts, networks/switches, or both." MODULE -- this module MANDATORY-GROUPS { atmSwtchNetHostGroup } -- Objects in the ATM Switch/Network/Host Group OBJECT atmVclConnType MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs and PVCs for ATM." -- The ATM Switch/Network/Host SVC Group GROUP atmSwtchNetHostSVCGroup DESCRIPTION "This group is mandatory for a Switch/Network/Host that implements ATM interfaces supporting Switched Virtual Connections (SVCs)." Expires XX [Page 54] draft Supplemental ATM Management Objects March 1995 OBJECT atmInterfaceSVCSigType MIN-ACCESS read-only DESCRIPTION "Write access is not required" OBJECT atmInterfaceSVCTimerT302 MIN-ACCESS read-only DESCRIPTION "Only required for systems that implement Q.2931 Section 6.5 'Overlap Sending and Receiving'." OBJECT atmInterfaceSVCTimerT310 MIN-ACCESS read-only DESCRIPTION "Write access is not required" OBJECT atmInterfaceSVCTimerT317 MIN-ACCESS read-only DESCRIPTION "Write access is not required" -- The ATM Switch/Network Group GROUP atmSwtchNetGroup DESCRIPTION "This group is mandatory for a Switch/Network that implements ATM interfaces." OBJECT atmIfAdminAddrRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required, and only one of the six enumerated values for the RowStatus textual convention need be supported, specifically: active(1)." -- The ATM Switch/Network SVC Group GROUP atmSwtchNetSVCGroup DESCRIPTION Expires XX [Page 55] draft Supplemental ATM Management Objects March 1995 "This group is mandatory for a Switch/Network that implements ATM interfaces supporting Switched Virtual Connections (SVCs)." OBJECT atmSubscrFeaturClgPtyNumDel MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Calling Party Number Delivery feature." OBJECT atmSubscrFeaturClgPtyNumScr MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Calling Party Number Screening feature." OBJECT atmSubscrFeaturClgPtyFailScrCnts MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Calling Party Number Screening feature." OBJECT atmSubscrFeaturClgPtySubAddrTrans MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Calling Party Subaddress Transfer feature." OBJECT atmSubscrFeaturCldPtySubAddrTrans MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Called Party Subaddress Transfer feature." OBJECT atmSubscrFeaturHiLyrInfoTrans MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the High Layer Information Transfer feature." OBJECT atmSubscrFeaturLoLyrInfoTrans MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Low Layer Information Transfer feature." Expires XX [Page 56] draft Supplemental ATM Management Objects March 1995 OBJECT atmSubscrFeaturLoLyrInfoSel MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Low Layer Information Selection feature." OBJECT atmSubscrFeaturAALInfoTrans MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the AAL Parameter Information Transfer feature." OBJECT atmSubscrFeaturPrefCarrier MIN-ACCESS read-only DESCRIPTION "Only required for a switch/network that supports the Preferred Carrier feature." -- The ATM Host Group GROUP atmHostGroup DESCRIPTION "This group is mandatory for a Host that implements ATM interfaces." OBJECT atmVclRemoteAtmAddr MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs and PVCs for ATM." OBJECT atmVclLocalAtmAddr MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs and PVCs for ATM." -- The ATM Host SVC Group GROUP atmHostSVCGroup DESCRIPTION Expires XX [Page 57] draft Supplemental ATM Management Objects March 1995 "This group is mandatory for a Host that implements ATM interfaces supporting Switched Virtual Connections (SVCs)." OBJECT atmVclSigDescrIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs and PVCs for ATM." OBJECT atmSigDescrParamAalType MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamAalMode MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamAalSscsType MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamBhliType MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamBhliInfo MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamBlliLayer2 MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." Expires XX [Page 58] draft Supplemental ATM Management Objects March 1995 OBJECT atmSigDescrParamBlliLayer3 MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamBlliPktSize MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamBlliSnapId MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamBlliOuiPid MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for hosts that support SVCs." OBJECT atmSigDescrParamRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required, and only one of the six enumerated values for the RowStatus textual convention need be supported, specifically: active(1). This object is required only for hosts that support SVCs." -- The ATM VP Interface Configuration Group GROUP atmVPIfConfGroup DESCRIPTION "This group is mandatory for interfaces that support ILMI and neighbor information for the ILMI-over-VPC scenario." OBJECT atmVplIlmiVci MIN-ACCESS read-only Expires XX [Page 59] draft Supplemental ATM Management Objects March 1995 DESCRIPTION "Write access is not required. This object is required for interfaces that support ILMI and neighbor information for the ILMI-over-VPC scenario." OBJECT atmVplInterfaceMyNeighborIpAddress MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for interfaces that support ILMI and neighbor information for the ILMI-over-VPC scenario." OBJECT atmVplInterfaceMyNeighborIfName MIN-ACCESS read-only DESCRIPTION "Write access is not required. This object is required for interfaces that support ILMI and neighbor information for the ILMI-over-VPC scenario." -- ********************************************** -- Units of Conformance atmSwtchNetHostGroup OBJECT-GROUP OBJECTS { atmVclConnType, atmVclStatCellIns, atmVclStatCellOuts} STATUS current DESCRIPTION "A collection of objects providing information for a Switch/Network/Host that implements ATM interfaces." ::= { atm2MIBGroups 1 } atmSwtchNetHostSVCGroup OBJECT-GROUP OBJECTS { atmInterfaceSVCSigType, Expires XX [Page 60] draft Supplemental ATM Management Objects March 1995 atmInterfaceSVCTimerT302, atmInterfaceSVCTimerT310, atmInterfaceSVCTimerT317, atmSSCOPConMontrCounts, atmSSCOPErrdPduCounts, atmUnsuptServRouteUnavails, atmUnsuptServResrcUnavails, atmUnsuptServCldPrtyCounts, atmSigLyrErrIncrtMesgCounts, atmSigLyrErrTimerExprCounts, atmSigLyrErrRestartCounts, atmIfSigInEstablished, atmIfSigOutEstablished} STATUS current DESCRIPTION "A collection of objects providing information for a Switch/Network/Host that implements ATM interfaces supporting Switched Virtual Connections (SVCs)." ::= { atm2MIBGroups 2 } atmSwtchNetGroup OBJECT-GROUP OBJECTS { atmIfAdminAddrAddress, atmIfAdminAddrRowStatus} STATUS current DESCRIPTION "A collection of objects providing information for a Switch/Network that implements ATM interfaces." ::= { atm2MIBGroups 3 } atmSwtchNetSVCGroup OBJECT-GROUP OBJECTS { atmSubscrFeaturClgPtyNumDel, atmSubscrFeaturClgPtyNumScr, atmSubscrFeaturClgPtyFailScrCnts, atmSubscrFeaturClgPtySubAddrTrans, atmSubscrFeaturCldPtySubAddrTrans, atmSubscrFeaturHiLyrInfoTrans, atmSubscrFeaturLoLyrInfoTrans, atmSubscrFeaturLoLyrInfoSel, Expires XX [Page 61] draft Supplemental ATM Management Objects March 1995 atmSubscrFeaturAALInfoTrans, atmSubscrFeaturPrefCarrier} STATUS current DESCRIPTION "A collection of objects providing information for a Switch/Network that implements ATM interfaces supporting Switched Virtual Connections (SVCs)." ::= { atm2MIBGroups 4 } atmHostGroup OBJECT-GROUP OBJECTS { atmVclRemoteAtmAddr, atmVclLocalAtmAddr, atmVclAddrIndex, atmVclAddrAtmIfIndex, atmVclAddrVpi, atmVclAddrVci} STATUS current DESCRIPTION "A collection of objects providing information for a Host that implements ATM interfaces." ::= { atm2MIBGroups 5 } atmHostSVCGroup OBJECT-GROUP OBJECTS { atmVclSigDescrIndex, atmSigDescrParamAalType, atmSigDescrParamAalMode, atmSigDescrParamAalSscsType, atmSigDescrParamBhliType, atmSigDescrParamBhliInfo, atmSigDescrParamBbcClass, atmSigDescrParamBbcTraffic, atmSigDescrParamBbcTiming, atmSigDescrParamBbcClipping, atmSigDescrParamBbcConnConf, atmSigDescrParamBlliLayer2, atmSigDescrParamBlliLayer3, atmSigDescrParamBlliPktSize, atmSigDescrParamBlliSnapId, atmSigDescrParamBlliOuiPid, Expires XX [Page 62] draft Supplemental ATM Management Objects March 1995 atmSigDescrParamRowStatus} STATUS current DESCRIPTION "A collection of objects providing information for a Host that implements ATM interfaces supporting Switched Virtual Connections (SVCs)." ::= { atm2MIBGroups 6 } atmVPIfConfGroup OBJECT-GROUP OBJECTS { atmVplIlmiVci, atmVplInterfaceMyNeighborIpAddress, atmVplInterfaceMyNeighborIfName} STATUS current DESCRIPTION "A collection of objects providing information for interfaces that support ILMI and neighbor information for the ILMI-over-VPC scenario." ::= { atm2MIBGroups 7 } END Expires XX [Page 63] draft Supplemental ATM Management Objects March 1995 9. Acknowledgments Expires XX [Page 64] draft Supplemental ATM Management Objects March 1995 10. References [1] Ahmed, M., Tesink, K., "Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2", RFC 1695, Bell Communications Research, August 1994. [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. [3] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [4] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes LAN Systems, April 1993. [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. [6] McCloghrie, K. and F. Kastenholz, "Evolution of the Interfaces Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, January 1994. [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for SNMPv2", RFC1443, SNMP Research,Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. [8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for SNMPv2", RFC1444, SNMP Research,Inc., Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon University, April 1993. [9] ATM Forum, "ATM User-Network Interface, Version 3.0 (UNI 3.0) Specification, Part I", 1994. Expires XX [Page 65] draft Supplemental ATM Management Objects March 1995 [10] ATM Forum, "ATM User-Network Interface, Version 3.1 (UNI 3.1) Specification, Part I", November 1994. [11] ITU-T Recommendation Q.2931, "Broadband Integrated Service Digital Network (B-ISDN) Digital Service Signalling System No.2 (DSS2) User-Network Interface (UNI) Layer 3 Specification for Basic Call/Connection Control", September 1994. [12] ATM Forum 94-0471R4, "P-NNI Draft Specification, P-NNI SWG", November 1994. [13] ITU-T Draft Recommendation Q.2110, "Broadband Integrated Service Digital Network (B-ISDN) - ATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP) Specification", 1994. [14] Newton, T., "Baseline Text For LAN Emulation Client Management", ATM Forum Contribution 94-0737R1, Digital Equipment Corporation, January 1995. [15] Brown, T., Tesink, K., "Definitions of Managed Objects for SMDS Interfaces using SMIv2", RFC 1694, Bell Communications Research, August 1994. Expires XX [Page 66] draft Supplemental ATM Management Objects March 1995 11. Security Considerations Security issues are not discussed in this memo. 12. Authors' Addresses Faye Ly BayNetworks Communications, Inc. 4401 Great America Pkwy Santa Clara, CA 95052 Phone: (408) 764-1702 EMail: faye@Baynetworks.COM Michael Noto Bell Communications Research Room 1E-348 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 Phone: (908) 758-5104 EMail: noto@cc.bellcore.com Andrew Smith BayNetworks Communications, Inc. 4401 Great America Pkwy Santa Clara, CA 95052 Phone: (408) 764-1574 EMail: asmith@Baynetworks.COM Kaj Tesink Bell Communications Research Room 1A-427 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 Phone: (908) 758-5254 EMail: kaj@cc.bellcore.com Expires XX [Page 67] draft Supplemental ATM Management Objects March 1995 Table of Contents 1 Status of this Memo ................................... 1 2 Introduction .......................................... 2 3 The SNMPv2 Network Management Framework ............... 2 4 Object Definitions .................................... 3 5 Overview .............................................. 3 5.1 Background .......................................... 3 5.2 Supported Functions ................................. 4 5.2.1 ATM Switch/Network/Host Support ................... 4 5.2.1.1 ATM Switch/Network/Host Group ................... 4 5.2.1.1.1 ATM VCL Statistics Table ...................... 4 5.2.1.2 ATM Switch/Network/Host SVC Group ............... 4 5.2.1.2.1 ATM Interface SVC Configuration Table ......... 4 5.2.1.2.2 SSCOP Table ................................... 6 5.2.1.2.3 Unsupported Service Failures Table ............ 6 5.2.1.2.4 ATM Signalling Layer Protocol Errors Table .... 7 5.2.1.2.5 UNI Signalling Sub-layer Statistics Table ..... 7 5.2.2 ATM Switch/Network Support ........................ 8 5.2.2.1 ATM Switch/Network Group ........................ 8 5.2.2.1.1 ATM Interface Administrative Address Table .... 8 5.2.2.2 ATM Switch/Network SVC Group .................... 8 5.2.2.2.1 ATM UNI SVC Subscription Features Table ....... 8 5.2.3 ATM Host Support .................................. 10 5.2.3.1 ATM Host Group .................................. 10 5.2.3.1.1 VCL Extension Table ........................... 10 5.2.3.1.2 ATM Addresses to VCC Mapping Table ............ 11 5.2.3.2 ATM Host SVC Group .............................. 11 5.2.3.2.1 Signalling Parameter Descriptor Table ......... 11 6 Valid Address Sets / Default Address .................. 12 7 Configuration of VPLs, VCLs, and Cross-Connects ....... 12 8 Definitions ........................................... 12 9 Acknowledgments ....................................... 64 10 References ........................................... 65 11 Security Considerations .............................. 67 12 Authors' Addresses ................................... 67 Expires XX [Page 68]