| draft-ietf-sigtran-m3ua-mib-04Description: Request For CommentsYou can download source copies of the file as follows:
Listed below is the contents of file draft-ietf-sigtran-m3ua-mib-04.txt. Network Working Group Antonio Roque INTERNET-DRAFT Ericsson Expires in six months August, 2002 SS7 MTP3-User Adaptation Layer (M3UA) Management Information Base using SMIv2 <draft-ietf-sigtran-m3ua-mib-04.txt> Status of This Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distributeworking 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 cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/lid-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This document is an individual submission to the IETF. Comments should be directed to the authors. Abstract The MTP3-User Adaptation Layer is a protocol for the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services of the Stream Control Transmission Protocol. Also, provision is made for protocol elements that enable a seamless operation of the MTP3- User peers in the SS7 and IP domains. This protocol would be used between a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP- resident Database. It is assumed that the SG receives SS7 signalling over a standard SS7 interface usingthe SS7 Message Transfer Part (MTP) to provide transport. This memo defines the Management Information Base (MIB) module which describes the minimum amount of objects needed to manage the implementation of the M3UA. Roque, et al [Page 1] Internet Draft M3UA MIB using SMIv2 August, 2002 Open Issues - Remove this section. - Remove Revision History - Decide under which object identifier branch of the SNMP tree, M3UA will be placed (value obtained when submitted to the IETF editor). - Update references to drafts. Table of Contents Status of This Memo.......................................1 1. Introduction..........................................3 1.1 Abbreviations........................................3 2. The SNMP Framework....................................4 3. Structure of the MIB..................................5 3.1 Management...........................................6 3.1.1 Attributes.........................................6 3.1.1.1 Protocol General Variables........................6 3.1.1.2 Protocol General Statistics.......................6 3.1.2 Tables.............................................6 3.1.2.1 Logical Application Table.........................6 3.1.2.2 Logical Application Statistics Table..............7 3.1.2.3 Signaling Process Endpoint Table..................7 3.1.2.4 Signaling Process Endpoint Statistics Table.......8 3.1.2.5 Application-Endpoint Table........................9 3.1.2.6 Routing Table....................................10 3.1.2.7 Network Appearance Table.........................10 3.1.2.8 Expanded Tables..................................11 3.1.2.8.1 Service Indicator Table........................11 3.1.2.8.2 OPC Table......................................11 3.1.2.8.3 CIC Range Table................................11 3.1.2.8.4 Point Code Table...............................12 3.1.2.8.5 Local and Remote IP Address Tables.............12 3.1.2.9 Reverse Lookup Tables............................13 3.2 Conformance.........................................14 3.2.1 Groups.............................................14 3.2.2 Compliance.........................................14 4. Definitions..........................................14 5. References...........................................54 6. Security Consideration................................56 7. Acknowledgments.......................................56 8. Authors' Addresses....................................56 9. Revision History......................................56 9.1 Changes from draft rev 03 to draft rev 04:...........57 9.2 Changes from draft rev 02 to draft rev 03:...........57 9.3 Changes from draft rev 01 to draft rev 02:...........58 9.4 Changes due to the alignment with the RFC2851 update. 58 Roque, et al [Page 2] Internet Draft M3UA MIB using SMIv2 August, 2002 1. Introduction This memo defines the Management Information Base (MIB) module which describes managed objects for implementations of the M3UA. The document starts with a brief description of the SNMP framework and continues with the MIB explanation and security consideration among others. Terms related to the SCTP architecture are explained in [1]. Other especific abbreviations are listed below. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 1.1 Abbreviations AS - Application Server ASP - Application Server Process ASPM - Application Server Process Management CIC - Circuit Identification Code DPC - Destination Point Code IPSP - IP Server Process MIB - Management Information Base M3UA - SS7 MTP3-User Adaptation Layer NA - Network Appearance NI - Network Indicator OPC - Origination Point Code PC - Point Code SCTP - Stream Control Transmision Protocol SG - Signaling Gateway SI - Service Indicator SMI - Structure of Management Information SNMP - Simple Network Management Protocol SP - Signaling Process SSN - Subsystem Number 2. The SNMP Framework The SNMP Management Framework presently consists of five major components: - An overall architecture, described in RFC 2271 [SNMPArch]. Roque, et al [Page 3] Internet Draft M3UA MIB using SMIv2 August, 2002 - Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The second version, called SMIv2, is described in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. - Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [SNMPv1]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. - Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in RFC 1157 [SNMPv1]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [SNMPv2PO]. - A set of fundamental applications described in RFC 2273 [SNMPv3App] and the view-based access control mechanism described in RFC 2575 [SNMPv3VACM]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine- readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine- readable information is not considered to change the semantics of the MIB. 3. Structure of the MIB The MIB is structured in the following way: m3uaMib / \ m3uaManagement m3uaConformance / \ / \ m3uaAttributes m3uaTables m3uaGroups m3uaCompliances / \ | Roque, et al [Page 4] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaConfig m3uaStatistics m3uaCompliance where the following sections are described : - m3uaManagement, where all the objects to manage M3UA are defined under this branch. - m3uaAttributes, where general attributes values are placed. It is divided in: - m3uaConfig, where the general M3UA configuration parameters are listed. - m3uaStatistics, where general Statistics for M3UA are listed. - m3uaTables, where specific attributes for each element that can be defined and used to manage a M3UA Based System. Every table is structured in the following way: m3uaTableName | m3uaTabAttributes / \ m3uaTabConfig m3uaTabStatistics Note: Statistics only apply to some of the tables. These tables hold data for: Logical Application, Signaling Process, Signaling Point Endpoint, Routing Keys, Network Appearances, Point Codes, Local and Remote IP Address. - m3uaConformance, for the Unit of Conformance. - m3uaGroups, M3UA MIB variables have been grouped according to their funcionality and the context they belong to. - m3uaCompliances, Minimal list of objects in the M3UA MIB module that an agent developer must implement. 3.1 Management 3.1.1 Attributes Roque, et al [Page 5] Internet Draft M3UA MIB using SMIv2 August, 2002 3.1.1.1 Protocol General Variables The first section of the MIB contains the general variables of the M3UA protocol. Maximum, minimum and initial values can be found here. 3.1.1.2 Protocol General Statistics Statistics included here relate to the whole M3UA layer. Statistics related to a specific Peer Association are defined inside its concerned table (context). 3.1.2 Tables 3.1.2.1 Logical Application Table Defines data related to a Logical Application, its state and traffic handling mode. A Logical Application is a logical entity serving an specific Routing Key. An AS or SG are Logical Applications as they are the final translation result for Routing Keys in the Routing Tables at SGPs, ASPs or IPSPs respectively. Thus they can be managed using the same object. LApps managed in a node behaving as an ASP, would represent SGs. On the contrary, LApps managed in a node that behaves as an SGP, would represent ASs. Finally, LApps managed in a node that behaves as an IPSP, would also represent ASs. m3uaAppTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppType / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppState / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppTrafficMode / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.2 Logical Application Statistics Table This table contains statistic information about each Logical Application. m3uaAppStatTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Roque, et al [Page 6] Internet Draft M3UA MIB using SMIv2 August, 2002 | m3uaAppUnreachable / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.3 Signaling Process Endpoint Table Defines data related to a Signaling Process Endpoint. A SP Endpoint identifies a peer node were a Signaling Process (SGP, ASP or IPSP) is running. The table contains the Endpoint identifier and data related to the association to that endpoint. This table is expanded with the Remote IP Address Table that identify the endpoint and with the Local IP Address Table that identify the local node for that endpoint. The table contains data related to the SCTP association to that endpoint, as its state, number of streams, and the Association ID, provided by SCTP when the association is established. m3uaSpEpTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocId / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocRemHostName / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocRemPort / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocReqOutStreams / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocOutStreams / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocIncStreams / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocState / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.4 Signaling Process Endpoint Statistics Table Defines statistics related to a Signaling Process Endpoint. The table contains statistics data related to the M3UA messaging exchanged through that association between the Signaling Processes that hold the association. m3uaSpEpStatTable Roque, et al [Page 7] Internet Draft M3UA MIB using SMIv2 August, 2002 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocId / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDataOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDataRecived / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspupOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspupAckOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspacOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspacAckOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspdnOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspdnAckOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspiaOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspiaAckOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspupIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspupAckIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspacIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspacAckIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspdnIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspdnAckIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspiaIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocAspiaAckIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocNotifyOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocErrorOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocNotifyIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocErrorIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDunaOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Roque, et al [Page 8] Internet Draft M3UA MIB using SMIv2 August, 2002 | m3uaSpEpAssocDavaOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocSconOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDupuOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDaudOut / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDunaIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDavaIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocSconIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDupuIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpAssocDaudIn / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.5 Application-Endpoint Table Defines data related to the endpoint where a Signaling Process is running, and the Logical Application IDs which the SP is serving. A Signaling Process is a process instance that uses M3UA to communicate with other signalling process. An ASP, an SGP and an IPSP are all signalling processes. As a SP can maintain different states and traffic handling modes for Every Lapp it is serving, i.e. The ASP_1 may be ASP-ACTIVE(LOAD-SHARING) for AS_1, ASP-INACTIVE for AS_2 and ASP-ACTIVE(OVER-RIDE) for AS_3. Then, one entry will be created in this table per every combination of AS Id and Endpoint Id. All the entries corresponding to the same SP running in an specific Endpoint will have a common link, the Endpoint Id. m3uaAppSpEpTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppSpEpState / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAppSpEpRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.6 Routing Table Every entry in this table contains the data that defines a Routing Key. Roque, et al [Page 9] Internet Draft M3UA MIB using SMIv2 August, 2002 As a Routing Key may be composed of any combination of basic SS7 Routing elements, if an element is not included in the routing key, a default value is assigned. This default value can continue being considered as an indexing value itself. m3uaRouting +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKDpc / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKNa / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaPeerAppId / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaPeerAppTrafficMOde / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRoutingRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.7 Network Appearance Table Defines the data specific to a Network Appearance. m3uaNaTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNA (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNaNI / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNaMtp3ProtocolType / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNaMtp3ProtocolVariant / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNaMtp3ProtocolVersion / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNaRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.8 Expanded Tables 3.1.2.8.1 Service Indicator Table This table expand information in entries in Routing Table. A Routing Key can be composed by a list of Service Indicators. m3uaSi +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKId (index) / ... | Roque, et al [Page 10] Internet Draft M3UA MIB using SMIv2 August, 2002 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKSi / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKSiRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.8.2 OPC Table This table expand information in entries in Routing Table. A Routing Key can be composed by a list of OPCs. m3uaOpc +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKOPc / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKOpcRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.8.3 CIC Range Table This table expand information in entries in Routing Table. A CIC Range can be defined for some of the OPC's which compose a Routing Key. m3uaCicRange +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKOPc (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKCicMin / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKCicMax / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaRKCicRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.8.4 Point Code Table This table expand information in entries in Network Appearance Table. A SG with several Network Appearances may be connected to different SS7 Networks and may be represented in each SS7 Network by different Point Codes. m3uaNaPcTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNA (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Roque, et al [Page 11] Internet Draft M3UA MIB using SMIv2 August, 2002 | m3uaNaPC(index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaNaPcRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.8.5 Local and Remote IP Address Tables These tables expand information for SP Endpoint Tables. When an SP Endpoint entry is created, a default free Association Id is assigned to that entry. The Local and Remote IP Address Table that will be used to establish an association towards the SGP, ASP or IPSP are stored in these tables. If the remote addresses change during association negotiation, they will be updated in the corresponding table. a) Table for local IP addressess information: This table stores information related to the local IP address/-es reserved for the association. It's indexed by the IP address. b) Table for remote IP addresses information: This table stores information related to the remote IP address/-es reserved for the association. It's indexed by the IP address. "Address" and "AddressType" use the syntax InetAddress and InetAddressType defined in the Textual Conventions for Internet Network Address [RFC2851-update]. In the general case this syntax is valid for IPv4, IPv6 and DNS but only the first two options will be valid for this MIB The IP addresses that the MIB supports are defined in the [RFC2851]: global and non-global (either with a zone index or not) IPv4 addresses, global and non-global (either with a zone index or not) IPv6 addresses. However, DNS value is not being used to identify an IP address since it is only valid during initialization (once this stage is finished, both sides only use IP addresses). To keep the name of the remote peer, an entry has been created (m3uaAssocRemHostName) in the association table. When no DNS name is provided by the remote SCTP endpoint at init time, this value will be NULL. Otherwise, the received DNS name will be stored. m3uaAssocLocalAddressTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAssocLocalAddressIPType(index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAssocLocalAddressIP (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAssocLocalAddressRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Roque, et al [Page 12] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaAssocRemAddressTable +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaSpEpId (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAssocRemAddressIPType(index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAssocRemAddressIP (index) / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | m3uaAssocRemAddressRowStatus / ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3.1.2.9 Reverse Lookup Tables There are four reverse lookup tables to help management applications to efficiently access conceptual rows in other tables. This is the way for not performing expensive tree walks through large number of associations. All of these tables are optional. The defined reversed lookup tables allow performing a lookup using the following variables: - Get Signaling Process Endpoint from Association: Obtains the LOCAL Identifier of the Endpoint that is connected through the Specified Association Id. There is only one Endpoint per Association. - Get Routing Key from Application: Obtains the LOCAL Routing Key Identifier of the Routing Key that results in the specified Logical Application Id. There is only one RK per Application. - Get Routing Key from DPC and NA: Obtains the LOCAL Routing Key Identifier of the Routing Key that contains the specified combination of DPC and NA. There is only one RK per DPC and NA combination. - Get Signaling Process Endpoints serving an Application: Obtains the LOCAL Identifiers of the Endpoints that are serving the specified Logical Application Id. There might be more than one Endpoint per Logical Application. It is not possible to either create or delete rows in these tables. 3.2 Conformance 3.2.1 Groups This section includes all the variables defined in the MIB grouped by function. 3.2.2 Compliance Requirements of the M3UA MIB to be implemented. Roque, et al [Page 13] Internet Draft M3UA MIB using SMIv2 August, 2002 4. Definitions M3UA-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, Counter64, mib-2 FROM SNMPv2-SMI -- RFC 2578 RowStatus FROM SNMPv2-TC -- RFC 2579 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 InetAddressType, InetAddress FROM INET-ADDRESS-MIB -- RFC 2851 ; m3uaMIB MODULE-IDENTITY LAST-UPDATED "200208060000Z" ORGANIZATION "IETF SIGTRAN Working Group" CONTACT-INFO " Antonio Roque Alvarez Postal: Ericsson Espana S. A. C/Ombu 3 28045 Madrid Spain Phones: +34 91 339 3523 Emails: Antonio.Roque@ericsson.com" DESCRIPTION "The MIB module for managing M3UA implementation." REVISION "200208060000Z" DESCRIPTION "MIB module developed for the SIGTRAN IETF group. Based on M3UAv11" ::= { mib-2 xxxx } -- IANA needs to choose this value -- when sent to the RFC editor -- Top-level structure of the MIB m3uaManagement OBJECT IDENTIFIER ::= { m3uaMIB 1 } m3uaConformance OBJECT IDENTIFIER ::= { m3uaMIB 2 } m3uaAttributes OBJECT IDENTIFIER ::= { m3uaManagement 1 } m3uaTables OBJECT IDENTIFIER ::= { m3uaManagement 2 } Roque, et al [Page 14] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaConfig OBJECT IDENTIFIER ::= { m3uaAttributes 1 } m3uaStatistics OBJECT IDENTIFIER ::= { m3uaAttributes 2 } m3uaLogApplication OBJECT IDENTIFIER ::= { m3uaTables 1 } m3uaLAppAttributes OBJECT IDENTIFIER ::= { m3uaLogApplication 1 } m3uaLAppConfig OBJECT IDENTIFIER ::= { m3uaLAppAttributes 1 } m3uaLAppStatistics OBJECT IDENTIFIER ::= { m3uaLAppAttributes 2 } m3uaSpEndPoint OBJECT IDENTIFIER ::= { m3uaTables 2 } m3uaSpEpAttributes OBJECT IDENTIFIER ::= { m3uaSpEndPoint 1 } m3uaSpEpConfig OBJECT IDENTIFIER ::= { m3uaSpEpAttributes 1 } m3uaSpEpStatistics OBJECT IDENTIFIER ::= { m3uaSpEpAttributes 2 } m3uaAppSpEndPoint OBJECT IDENTIFIER ::= { m3uaTables 3 } m3uaAppSpEpAttributes OBJECT IDENTIFIER ::= { m3uaAppSpEndPoint 1 } m3uaAppSpEpConfig OBJECT IDENTIFIER ::= { m3uaAppSpEpAttributes 1} m3uaRoutingTab OBJECT IDENTIFIER ::= { m3uaTables 4 } m3uaRtAttributes OBJECT IDENTIFIER ::= { m3uaRoutingTab 1 } m3uaRtConfig OBJECT IDENTIFIER ::= { m3uaRtAttributes 1 } m3uaNetworkAppearance OBJECT IDENTIFIER ::= { m3uaTables 5 } m3uaNaAttributes OBJECT IDENTIFIER ::= { m3uaNetworkAppearance 1} m3uaNaConfig OBJECT IDENTIFIER ::= { m3uaNaAttributes 1 } m3uaLookup OBJECT IDENTIFIER ::= { m3uaTables 6 } ----------------------------------------------------------------------- -- M3UA MANAGEMENT ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIGURATION ----------------------------------------------------------------------- m3uaVersion OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Identifies the current version of the M3UA." ::= { m3uaConfig 1 } m3uaProcType OBJECT-TYPE SYNTAX INTEGER { sgp(1), -- Signalling Gateway Process asp(2), -- Application Server Process ipsp(3) -- IP Server Process Roque, et al [Page 15] Internet Draft M3UA MIB using SMIv2 August, 2002 } MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates the type of the process where the M3UA layer is located." ::= { m3uaConfig 2 } m3uaLocalPort OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "Identifies the port of the M3UA service. Well-Known Port for M3UA is 2904." ::= { m3uaConfig 3 } m3uaTrValue OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Initial value of the Failover timer Tr. Recommended value is 3000 milliseconds. Tr set with value 0 disables buffering." ::= { m3uaConfig 4 } m3uaTPaudValue OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Initial value of the Periodic Audit timer TrPaud. Recommended value is 5000 milliseconds." ::= { m3uaConfig 5 } m3uaHeartBeat OBJECT-TYPE SYNTAX INTEGER { on(0), -- Heartbeat is enabled. off(1) -- Heartbeat is disabled. No BEAT msgs -- sent but BEAT messages received are -- responded. } MAX-ACCESS read-write STATUS current DESCRIPTION "Activates or deactivates the heartbeat procedure at M3UA level." Roque, et al [Page 16] Internet Draft M3UA MIB using SMIv2 August, 2002 ::= { m3uaConfig 6 } m3uaTBeatValue OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Initial value of the HeartBeat timer TBeat. Recommended value is 1000 milliseconds." ::= { m3uaConfig 7 } m3uaTAckValue OBJECT-TYPE SYNTAX Unsigned32 UNITS "milliseconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Initial value of the Retransmision timer TAck. Recommended value is 2000 milliseconds." ::= { m3uaConfig 8 } m3uaSpLshMethod OBJECT-TYPE SYNTAX INTEGER { none(0), -- Random sls(1), -- Basing on SLS cic(2), -- Basing on CIC ssn(3), -- Basing on SSN dpg(4), -- Basing on DPC other(5) -- Other method } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable indicates the method to be used when the load must be shared between several ACTIVE Signaling Processes." ::= { m3uaConfig 9 } m3uaStreamLshMethod OBJECT-TYPE SYNTAX INTEGER { none(0), -- Random sls(1), -- Basing on SLS cic(2), -- Basing on CIC ssn(3), -- Basing on SSN dpc(4), -- Basing on DPC other(5) -- Other method } MAX-ACCESS read-write STATUS current Roque, et al [Page 17] Internet Draft M3UA MIB using SMIv2 August, 2002 DESCRIPTION "This variable indicates the method to be used when the load must be shared between several streams within the same SCTP Association." ::= { m3uaConfig 10 } m3uaFailOverBuffSize OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "Size of the failover retransmision buffer. Recommended value is 64 Kbytes. Only valid if failover buffer option has been set to ON." ::= { m3uaConfig 11 } ----------------------------------------------------------------------- -- ATTRIBUTES-STATISTICS ----------------------------------------------------------------------- m3uaRoutingFailures OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times a routing operation against Routing Table fails. No final SCTP Association ID is obtained from the routing operation. That is the reason why this is a general statistic instead a per association statistic." ::= { m3uaStatistics 1 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE LOGICAL APPLICATION TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- The Logical Applications table contains information about each -- Application for which one or more routing keys can exist in the -- routing table. Log. Applications are: Signaling Gateways (SGs), -- Application Servers (ASs). m3uaAppTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaAppEntry MAX-ACCESS not-accessible Roque, et al [Page 18] Internet Draft M3UA MIB using SMIv2 August, 2002 STATUS current DESCRIPTION "A table containing Log. Application-specific information." ::= { m3uaLAppConfig 1 } m3uaAppEntry OBJECT-TYPE SYNTAX M3uaAppEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "General common variables for the Log. App." INDEX { m3uaAppId } ::= { m3uaAppTable 1 } M3uaAppEntry ::= SEQUENCE { m3uaAppId Unsigned32, m3uaAppType INTEGER, m3uaAppState INTEGER, m3uaAppTrafficMode INTEGER, m3uaAppRowStatus RowStatus } m3uaAppId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Application Identification Value." ::= { m3uaAppEntry 1 } m3uaAppType OBJECT-TYPE SYNTAX INTEGER { sg(1), as(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Logical Application Type: SG: Signaling Gateway. AS: Application Server. " ::= { m3uaAppEntry 2 } m3uaAppState OBJECT-TYPE SYNTAX INTEGER { active(1), inactive(2), down(3), pending(4) } Roque, et al [Page 19] Internet Draft M3UA MIB using SMIv2 August, 2002 MAX-ACCESS read-only STATUS current DESCRIPTION "Current Logical Application State. Based on the state of the Signaling Processes which serve it." ::= { m3uaAppEntry 3 } m3uaAppTrafficMode OBJECT-TYPE SYNTAX INTEGER { override(1), loadshare(2), broadcast(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Current Logical Application traffic handling mode." ::= { m3uaAppEntry 4 } m3uaAppRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaAppEntry 5 } ----------------------------------------------------------------------- -- ATTRIBUTES-STATISTICS ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE LOGICAL APPLICATION STATISTICS TABLE ----------------------------------------------------------------------- m3uaAppStatTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaAppStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing Log. Application statistic information." ::= { m3uaLAppStatistics 1 } m3uaAppStatEntry OBJECT-TYPE SYNTAX M3uaAppStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "General common variables for the Log. App." INDEX { m3uaAppId } -- SHARED INDEX Roque, et al [Page 20] Internet Draft M3UA MIB using SMIv2 August, 2002 ::= { m3uaAppStatTable 1 } M3uaAppStatEntry ::= SEQUENCE { m3uaAppUnreachable Counter32 } m3uaAppUnreachable OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times that the Application is unreachable through any of the Signaling Processes that are serving it." ::= { m3uaAppStatEntry 1 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE SIGNALING PROCESS ENDPOINT TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- Defines data related to a Signaling Process Endpoint. -- A SP Endpoint identifies a peer node were a SGP, ASP or IPSP are -- running. -- This table exists with any Proccess Type. -- The table contains the Endpoint Identifier and data related to the -- SCTP association to that remote endpoint. -- The Signaling Process Endpoint table contains information about -- specific data regarding the physical location of that endpoint, -- the list of remote IP addresses of that endpoint, and the list of -- local IP addresses that want to be used against that endpoint. -- This table is expanded with the Remote IP Address Table that -- identify the endpoint and with the Local IP Address Table that -- identify the local node for that endpoint. -- The table contains data related to the Association, as its state, -- number of streams, and the Association ID, provided by SCTP when -- the association is established. m3uaSpEpTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaSpEpEntry MAX-ACCESS not-accessible Roque, et al [Page 21] Internet Draft M3UA MIB using SMIv2 August, 2002 STATUS current DESCRIPTION "A table containing Signaling Process Endpoint-specific information." ::= { m3uaSpEpConfig 1 } m3uaSpEpEntry OBJECT-TYPE SYNTAX M3uaSpEpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "General common variables for the Signaling Process Endpoint." INDEX { m3uaSpEpId } ::= { m3uaSpEpTable 1 } M3uaSpEpEntry ::= SEQUENCE { m3uaSpEpId Unsigned32, m3uaSpEpAssocId Unsigned32, m3uaSpEpAssocRemHostName OCTET STRING, m3uaSpEpAssocRemPort Unsigned32, m3uaSpEpAssocReqOutStreams Unsigned32, m3uaSpEpAssocOutStreams Unsigned32, m3uaSpEpAssocIncStreams Unsigned32, m3uaSpEpAssocState INTEGER, m3uaSpEpRowStatus RowStatus } m3uaSpEpId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Signaling Process Endpoint Identification Value." ::= { m3uaSpEpEntry 1 } m3uaSpEpAssocId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Association Identification. Value identifying the association for that endpoint. This value is extracted from the SCTP association Id value returned by SCTP when the association is established to that endpoint." ::= { m3uaSpEpEntry 2 } m3uaSpEpAssocRemHostName OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..255)) Roque, et al [Page 22] Internet Draft M3UA MIB using SMIv2 August, 2002 MAX-ACCESS read-create STATUS current DESCRIPTION "Peer's DNS name. If no DNS domain name was received at init time from the peer, this entry will be meaningless, therefore it will store a NULL value. Otherwise, the remote host name received at init time will be stored." ::= { m3uaSpEpEntry 3 } m3uaSpEpAssocRemPort OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "M3UA port number to connect to remote Endpoint." ::= { m3uaSpEpEntry 4 } m3uaSpEpAssocReqOutStreams OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "If the SCTP association is initiated from the local peer, this will be the number of outgoing streams that will be requested to the remote peer at association start up." ::= { m3uaSpEpEntry 5 } m3uaSpEpAssocOutStreams OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "outgoing Streams according to the negotiation at association start up. This parameter has to be read-only by the manager." ::= { m3uaSpEpEntry 6 } m3uaSpEpAssocIncStreams OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Incoming Streams according to the negotiation at assoc. start up. This parameter has to be read-only by the manager." ::= { m3uaSpEpEntry 7 } Roque, et al [Page 23] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaSpEpAssocState OBJECT-TYPE SYNTAX INTEGER { closed(1), established(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The state of this SCTP association." ::= { m3uaSpEpEntry 8 } m3uaSpEpRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaSpEpEntry 9 } ----------------------------------------------------------------------- -- ATTRIBUTES-STATISTICS ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE SP ENDPOINT STATISTICS TABLE ----------------------------------------------------------------------- -- Defines statistics related to a Signaling Process Endpoint. -- This table exists with any Proccess Type. -- The table contains statistics data related to the M3UA messaging -- exchanged through that association between the Signaling Processes -- that hold the association. m3uaSpEpStatTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaSpEpStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing Signaling Process Endpoint-specific information." ::= { m3uaSpEpStatistics 1 } m3uaSpEpStatEntry OBJECT-TYPE SYNTAX M3uaSpEpStatEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "General common variables for the SP Endpoint." Roque, et al [Page 24] Internet Draft M3UA MIB using SMIv2 August, 2002 INDEX { m3uaSpEpId } -- shared index ::= { m3uaSpEpStatTable 1 } M3uaSpEpStatEntry ::= SEQUENCE { m3uaSpEpAssocDataOut Counter32, m3uaSpEpAssocDataIn Counter32, m3uaSpEpAssocAspupOut Counter32, m3uaSpEpAssocAspupAckOut Counter32, m3uaSpEpAssocAspacOut Counter32, m3uaSpEpAssocAspacAckOut Counter32, m3uaSpEpAssocAspdnOut Counter32, m3uaSpEpAssocAspdnAckOut Counter32, m3uaSpEpAssocAspiaOut Counter32, m3uaSpEpAssocAspiaAckOut Counter32, m3uaSpEpAssocAspupIn Counter32, m3uaSpEpAssocAspupAckIn Counter32, m3uaSpEpAssocAspacIn Counter32, m3uaSpEpAssocAspacAckIn Counter32, m3uaSpEpAssocAspdnIn Counter32, m3uaSpEpAssocAspdnAckIn Counter32, m3uaSpEpAssocAspiaIn Counter32, m3uaSpEpAssocAspiaAckIn Counter32, m3uaSpEpAssocNotifyOut Counter32, m3uaSpEpAssocErrorOut Counter32, m3uaSpEpAssocNotifyIn Counter32, m3uaSpEpAssocErrorIn Counter32, m3uaSpEpAssocDunaOut Counter32, m3uaSpEpAssocDavaOut Counter32, m3uaSpEpAssocSconOut Counter32, m3uaSpEpAssocDupuOut Counter32, m3uaSpEpAssocDaudOut Counter32, m3uaSpEpAssocDunaIn Counter32, m3uaSpEpAssocDavaIn Counter32, m3uaSpEpAssocSconIn Counter32, m3uaSpEpAssocDupuIn Counter32, m3uaSpEpAssocDaudIn Counter32 } -- Association Statistics -- DATA Statistics per Association m3uaSpEpAssocDataOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DATA messages sent through the association." ::= { m3uaSpEpStatEntry 1 } m3uaSpEpAssocDataIn OBJECT-TYPE Roque, et al [Page 25] Internet Draft M3UA MIB using SMIv2 August, 2002 SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DATA messages received through the association." ::= { m3uaSpEpStatEntry 2 } -- End of DATA Statistics per Association -- ASPM Statistics per Association m3uaSpEpAssocAspupOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPUP messages sent through the association." ::= { m3uaSpEpStatEntry 3 } m3uaSpEpAssocAspupAckOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPUP ACK messages sent through the association." ::= { m3uaSpEpStatEntry 4 } m3uaSpEpAssocAspacOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPAC messages sent through the association." ::= { m3uaSpEpStatEntry 5 } m3uaSpEpAssocAspacAckOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPAC ACK messages sent through the association." ::= { m3uaSpEpStatEntry 6 } m3uaSpEpAssocAspdnOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPDN messages sent through the association." Roque, et al [Page 26] Internet Draft M3UA MIB using SMIv2 August, 2002 ::= { m3uaSpEpStatEntry 7 } m3uaSpEpAssocAspdnAckOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPDN ACK messages sent through the association." ::= { m3uaSpEpStatEntry 8 } m3uaSpEpAssocAspiaOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPIA messages sent through the association." ::= { m3uaSpEpStatEntry 9 } m3uaSpEpAssocAspiaAckOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPIA ACK messages sent through the association." ::= { m3uaSpEpStatEntry 10 } m3uaSpEpAssocAspupIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPUP messages received through the association." ::= { m3uaSpEpStatEntry 11 } m3uaSpEpAssocAspupAckIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPUP ACK messages received through the association." ::= { m3uaSpEpStatEntry 12 } m3uaSpEpAssocAspacIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION Roque, et al [Page 27] Internet Draft M3UA MIB using SMIv2 August, 2002 "Number of ASPAC messages received through the association." ::= { m3uaSpEpStatEntry 13 } m3uaSpEpAssocAspacAckIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPAC ACK messages received through the association." ::= { m3uaSpEpStatEntry 14 } m3uaSpEpAssocAspdnIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPDN messages received through the association." ::= { m3uaSpEpStatEntry 15 } m3uaSpEpAssocAspdnAckIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPDN ACK messages received through the association." ::= { m3uaSpEpStatEntry 16 } m3uaSpEpAssocAspiaIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPIA messages received through the association." ::= { m3uaSpEpStatEntry 17 } m3uaSpEpAssocAspiaAckIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ASPIA ACK messages received through the association." ::= { m3uaSpEpStatEntry 18 } -- End of ASPM Statistics per Association Roque, et al [Page 28] Internet Draft M3UA MIB using SMIv2 August, 2002 -- MGMT Statistics per Association m3uaSpEpAssocNotifyOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of NOTIFY messages sent through the association." ::= { m3uaSpEpStatEntry 19 } m3uaSpEpAssocErrorOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ERROR messages sent through the association." ::= { m3uaSpEpStatEntry 20 } m3uaSpEpAssocNotifyIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of NOTIFY messages received through the association." ::= { m3uaSpEpStatEntry 21 } m3uaSpEpAssocErrorIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of ERROR messages received through the association." ::= { m3uaSpEpStatEntry 22 } -- End of MGMT Statistics per Association -- SSNM Statistics per Association m3uaSpEpAssocDunaOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DUNA messages sent through the association." ::= { m3uaSpEpStatEntry 23 } m3uaSpEpAssocDavaOut OBJECT-TYPE SYNTAX Counter32 Roque, et al [Page 29] Internet Draft M3UA MIB using SMIv2 August, 2002 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DAVA messages sent through the association." ::= { m3uaSpEpStatEntry 24 } m3uaSpEpAssocSconOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of SCON messages sent through the association." ::= { m3uaSpEpStatEntry 25 } m3uaSpEpAssocDupuOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DUPU messages sent through the association." ::= { m3uaSpEpStatEntry 26 } m3uaSpEpAssocDaudOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DAUD messages sent through the association." ::= { m3uaSpEpStatEntry 27 } m3uaSpEpAssocDunaIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DUNA messages received through the association." ::= { m3uaSpEpStatEntry 28 } m3uaSpEpAssocDavaIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DAVA messages received through the association." ::= { m3uaSpEpStatEntry 29 } m3uaSpEpAssocSconIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION Roque, et al [Page 30] Internet Draft M3UA MIB using SMIv2 August, 2002 "Number of SCON messages received through the association." ::= { m3uaSpEpStatEntry 30 } m3uaSpEpAssocDupuIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DUPU messages received through the association." ::= { m3uaSpEpStatEntry 31 } m3uaSpEpAssocDaudIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of DAUD messages received through the association." ::= { m3uaSpEpStatEntry 32 } -- End of SSNM Statistics per Association ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE APPLICATION-ENDPOINT TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- The Application-Endpoint table contains information about the -- Applications that the indexed Endpoint is serving and the state of -- that endpoint for that specific application. -- Although an SP is identified with an unique SCTP endpoint, there may -- be more than one SP table entry indexed by the same SP Endpoint Id. -- The reason for this is that an Endpoint can be serving several -- Applications and thus maintains different states for each of them. -- An entry will then exist in the table per every combination of -- m3uaSpEpId and m3uaAppId. m3uaAppSpEpTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaAppSpEpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing Signaling Process Endpoint-specific information." ::= { m3uaSpEpConfig 2 } Roque, et al [Page 31] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaAppSpEpEntry OBJECT-TYPE SYNTAX M3uaAppSpEpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "General common variables for the SP Endpoint." INDEX { m3uaSpEpId, -- shared index m3uaAppId } -- shared index ::= { m3uaAppSpEpTable 1 } M3uaAppSpEpEntry ::= SEQUENCE { m3uaAppSpEpState INTEGER, m3uaAppSpEpRowStatus RowStatus } m3uaAppSpEpState OBJECT-TYPE SYNTAX INTEGER { active(1), inactive(2), down(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Current state of the Endpoint for an specific Application. Based on ASPM Messages." ::= { m3uaAppSpEpEntry 1 } m3uaAppSpEpRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaAppSpEpEntry 2 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- LOCAL AND REMOTE IP ADDRESS TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- Remote Addresses Table ----------------------------------------------------------------------- Roque, et al [Page 32] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaAssocLocalAddressTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaAssocLocalAddressEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Expanded table of m3uaAssocTable based on the AssocId index. It shows several interesting data for each local address which takes part in this association." ::= { m3uaSpEpConfig 3 } m3uaAssocLocalAddressEntry OBJECT-TYPE SYNTAX M3uaAssocLocalAddressEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Local information about the available addresses." INDEX { m3uaSpEpId, -- shared index m3uaAssocLocalAddressIPType, m3uaAssocLocalAddressIP } ::= { m3uaAssocLocalAddressTable 1 } M3uaAssocLocalAddressEntry ::= SEQUENCE { m3uaAssocLocalAddressIPType InetAddressType, m3uaAssocLocalAddressIP InetAddress, m3uaAssocLocalAddressRowStatus RowStatus } m3uaAssocLocalAddressIPType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of a local IP address available for this association. unknown (0) An unknown address type. This value MUST be used to indicate an IP address different from IPv4 or IPv6. This value is used in this MIB for error conditions. ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 textual convention [RFC2851]. ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 textual convention [RFC2851]. It represents global IPv6 addresses and non-global IPv6 addresses in case where no zone index is needed. ipv4z(3): A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention Roque, et al [Page 33] Internet Draft M3UA MIB using SMIv2 August, 2002 [RFC2851]. ipv6z(4): A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention [RFC2851].ö ::= { m3uaAssocLocalAddressEntry 1 } m3uaAssocLocalAddressIP OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The value of a local IP address available for this association. An InetAddress value is always interpreted within the context of an InetAddressType value." ::= { m3uaAssocLocalAddressEntry 2 } m3uaAssocLocalAddressRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted using the RowStatus convention. A row in this table will be created per local IP address to be used in this association. The creation takes part when a new row in the m3uaAssocTable is created or when a new IPaddress is added in the local interface (if this function is allowed). A row in this table will be deleted per local IP address used in this association when the corresponding row in m3uaAssocTable is deleted or when an IP address is removed from the local interface (if this function is allowed)." ::= { m3uaAssocLocalAddressEntry 3 } ----------------------------------------------------------------------- -- Remote Addresses Table ----------------------------------------------------------------------- m3uaAssocRemAddressTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaAssocRemAddressEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Expanded table of m3uaAssocTable based on the AssocId index. It shows several interesting data for each remote peer IP address which is used in this association." Roque, et al [Page 34] Internet Draft M3UA MIB using SMIv2 August, 2002 ::= { m3uaSpEpConfig 4 } m3uaAssocRemAddressEntry OBJECT-TYPE SYNTAX M3uaAssocRemAddressEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about the remote IP address most important variables" INDEX { m3uaSpEpId, -- shared index m3uaAssocRemAddressIPType, m3uaAssocRemAddressIP } ::= { m3uaAssocRemAddressTable 1 } M3uaAssocRemAddressEntry ::= SEQUENCE { m3uaAssocRemAddressIPType InetAddressType, m3uaAssocRemAddressIP InetAddress, m3uaAssocRemAddressRowStatus RowStatus } m3uaAssocRemAddressIPType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of a local IP address available for this association. unknown (0) An unknown address type. This value MUST be used to indicate an IP address different from IPv4 or IPv6. This value is used in this MIB for error conditions. ipv4 (1): An IPv4 address as defined by the InetAddressIPv4 textual convention [RFC2851]. ipv6 (2): An IPv6 address as defined by the InetAddressIPv6 textual convention [RFC2851]. It represents global IPv6 addresses and non-global IPv6 addresses in case where no zone index is needed. ipv4z(3): A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention [RFC2851]. ipv6z(4): A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention [RFC2851].ö ::= { m3uaAssocRemAddressEntry 1 } m3uaAssocRemAddressIP OBJECT-TYPE Roque, et al [Page 35] Internet Draft M3UA MIB using SMIv2 August, 2002 SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The value of a local IP address available for this association. An InetAddress value is always interpreted within the context of an InetAddressType value." ::= { m3uaAssocRemAddressEntry 2 } m3uaAssocRemAddressRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted using the RowStatus convention. A row in this table will be created per local IP address to be used in this association. The creation takes part when a new row in the m3uaAssocTable is created or when a new IPaddress is added in the local interface (if this function is allowed). A row in this table will be deleted per local IP address Used in this association when the corresponding row in m3uaAssocTable is deleted or when an IP address is removed from the local interface (if this function is allowed)." ::= { m3uaAssocRemAddressEntry 3 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE ROUTING TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- The Routing table contains a list of routing keys which translate to -- a Logical Application ID. As stated former in this document, -- Application Servers and Signaling Gateways are Logical Applications. -- As a Routing Key may be composed of any combination of basic SS7 -- routing elements, if an element is not included in the routing key, -- a default value is assigned. This default value can continue being -- considered as an indexing value itself. m3uaRoutingTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaRoutingEntry Roque, et al [Page 36] Internet Draft M3UA MIB using SMIv2 August, 2002 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing Routing-specific information." ::= { m3uaRtConfig 1 } m3uaRoutingEntry OBJECT-TYPE SYNTAX M3uaRoutingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "General common variables for a Routing Key." INDEX { m3uaRKId } ::= { m3uaRoutingTable 1 } M3uaRoutingEntry ::= SEQUENCE { m3uaRKId Unsigned32, m3uaRKDpc Unsigned32, m3uaRKNa Unsigned32, m3uaPeerAppId Unsigned32, m3uaPeerAppTrafficMode INTEGER, m3uaRoutingRowStatus RowStatus } m3uaRKId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Local identifier for the routing key." ::= { m3uaRoutingEntry 1 } m3uaRKDpc OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Destination Point Code for that routing key. A default value will be assigned if not present in the Routing Key. Range: 0 - 16777215." ::= { m3uaRoutingEntry 2 } m3uaRKNa OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Network Appearance for that routing key. A default value will be assigned if not present in the Routing Key." ::= { m3uaRoutingEntry 3 } Roque, et al [Page 37] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaPeerAppId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Peer Application Identification Value. It can identify an Application Server or a Signaling Gateway." ::= { m3uaRoutingEntry 4 } m3uaPeerAppTrafficMode OBJECT-TYPE SYNTAX INTEGER { override(1), loadshare(2), broadcast(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "Peer Application Traffic Mode Type. Identifies the traffic mode of operation of SPs within the Peer Application." ::= { m3uaRoutingEntry 5 } m3uaRoutingRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaRoutingEntry 6 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE SI TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- This table contains a list of SIs that identify the Services covered -- by that Routing Key. This list is related to and extends information -- of every entry in Routing Table. m3uaRKSiTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaRKSiEntry MAX-ACCESS not-accessible Roque, et al [Page 38] Internet Draft M3UA MIB using SMIv2 August, 2002 STATUS current DESCRIPTION "A table containing the list of SIs that identify the services covered by that Routing Key." ::= { m3uaRtConfig 2 } m3uaRKSiEntry OBJECT-TYPE SYNTAX M3uaRKSiEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaRKId } -- shared index ::= { m3uaRKSiTable 1 } M3uaRKSiEntry ::= SEQUENCE { m3uaRKSi Unsigned32, m3uaRKSiRowStatus RowStatus } m3uaRKSi OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Service Indicator for that routing key. A default value will be assigned if not present in the Routing Key. Range: 2 - 10." ::= { m3uaRKSiEntry 1 } m3uaRKSiRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaRKSiEntry 2 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE OPC TABLE ----------------------------------------------------------------------- Roque, et al [Page 39] Internet Draft M3UA MIB using SMIv2 August, 2002 ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- This table contains a list of OPCs that identify the Originating -- Node in the SS7 Network. This list is related with and extends -- information of every entry in Routing Table. m3uaRKOpcTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaRKOpcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing the list of Point Codes that identify the Originating Node in the SS7 Network for a Routing Key." ::= { m3uaRtConfig 3 } m3uaRKOpcEntry OBJECT-TYPE SYNTAX M3uaRKOpcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaRKId } -- shared index ::= { m3uaRKOpcTable 1 } M3uaRKOpcEntry ::= SEQUENCE { m3uaRKOpc Unsigned32, m3uaRKOpcRowStatus RowStatus } m3uaRKOpc OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Origination Point Code for that routing key. A default value will be assigned if not present in the Routing Key. Range: 0 to 16777215." ::= { m3uaRKOpcEntry 1 } m3uaRKOpcRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus Roque, et al [Page 40] Internet Draft M3UA MIB using SMIv2 August, 2002 convention." ::= { m3uaRKOpcEntry 2 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE CIC RANGE TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- This table contains a CIC Range for an OPC in the Routing Key -- This list is related with and extends information -- of every entry in Routing Table. m3uaRKCicRangeTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaRKCicRangeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing the list of CIC Ranges for an OPC within the specific Routing Key." ::= { m3uaRtConfig 4 } m3uaRKCicRangeEntry OBJECT-TYPE SYNTAX M3uaRKCicRangeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaRKId, -- shared index m3uaRKOpc } ::= { m3uaRKCicRangeTable 1 } M3uaRKCicRangeEntry ::= SEQUENCE { m3uaRKCicMin Unsigned32, m3uaRKCicMax Unsigned32, m3uaRKCicRowStatus RowStatus } m3uaRKCicMin OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION Roque, et al [Page 41] Internet Draft M3UA MIB using SMIv2 August, 2002 "Minumum value of the Circuit Identification Code Range for that routing key. A default value will be assigned if not present in the Routing Key. Range: 0 to 65535." ::= { m3uaRKCicRangeEntry 1 } m3uaRKCicMax OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Maximum value of the Circuit Identification Code Range for that routing key. A default value will be assigned if not present in the Routing Key. Range: 0 to 65535." ::= { m3uaRKCicRangeEntry 2 } m3uaRKCicRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaRKCicRangeEntry 3 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE NETWORK APPEARANCE TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- The NA table contains information about the specific variables -- that apply to every Network Appearance. m3uaNaTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaNaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing Network Appearance-specific information" Roque, et al [Page 42] Internet Draft M3UA MIB using SMIv2 August, 2002 ::= { m3uaNaConfig 1 } m3uaNaEntry OBJECT-TYPE SYNTAX M3uaNaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "General common variables for a Network Appearance." INDEX { m3uaRKNa } -- shared index ::= { m3uaNaTable 1 } M3uaNaEntry ::= SEQUENCE { m3uaNaNI Unsigned32, m3uaNaMtp3ProtocolType INTEGER, m3uaNaMtp3ProtocolVariant Unsigned32, m3uaNaMtp3ProtocolVersion Unsigned32, m3uaNaRowStatus RowStatus } m3uaNaNI OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Identifies the Network Indicator of the SG Node in the SS7 Network." ::= { m3uaNaEntry 2 } m3uaNaMtp3ProtocolType OBJECT-TYPE SYNTAX INTEGER { itu(1), ansi(2), china(3), ttc(4), other(5) } MAX-ACCESS read-create STATUS current DESCRIPTION "The MTP3 protocol type for this NA." ::= { m3uaNaEntry 4 } m3uaNaMtp3ProtocolVariant OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION Roque, et al [Page 43] Internet Draft M3UA MIB using SMIv2 August, 2002 "The MTP3 protocol variant for this NA." ::= { m3uaNaEntry 5 } m3uaNaMtp3ProtocolVersion OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The MTP3 protocol version for this NA." ::= { m3uaNaEntry 6 } m3uaNaRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaNaEntry 7 } ----------------------------------------------------------------------- -- M3UA TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- THE POINT CODE TABLE ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ATTRIBUTES - CONFIG ----------------------------------------------------------------------- -- The PC table contains a list of point codes that identify the SG -- node in the SS7 Network. This list is related with and extends -- information of every NA in NA Table. -- This table expand information in entries in Network Appearance -- Table. A SG with several Network Appearances may be connected to -- different SS7 Networks and may be represented in each SS7 Network by -- different Point Codes. m3uaNaPcTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaNaPcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Roque, et al [Page 44] Internet Draft M3UA MIB using SMIv2 August, 2002 "A table containing the list of Point Codes that identify the SG Node in the SS7 Network for that Network App." ::= { m3uaNaConfig 2 } m3uaNaPcEntry OBJECT-TYPE SYNTAX M3uaNaPcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaRKNa, -- shared index m3uaNaPC } ::= { m3uaNaPcTable 1 } M3uaNaPcEntry ::= SEQUENCE { m3uaNaPC Unsigned32, m3uaNaPcRowStatus RowStatus } m3uaNaPC OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "Point Code Value. Range: 0 to 16777215." ::= { m3uaNaPcEntry 1 } m3uaNaPcRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "An object that allows entries in this table to be created and deleted by management operation using the RowStatus convention." ::= { m3uaNaPcEntry 2 } ----------------------------------------------------------------------- -- M3UA LOOKUP REVERSE TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ENDPOINT BY ASSOCIATION ----------------------------------------------------------------------- -- This table allows the obtention of the Remote Endpoint Local Id -- for an specific association. Roque, et al [Page 45] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaLookupSpEpbyAssocTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaLookupSpEpbyAssocEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing the list of remote Endpoints defined indexed by the Id of the association established to that Endpoint." ::= { m3uaLookup 1 } m3uaLookupSpEpbyAssocEntry OBJECT-TYPE SYNTAX M3uaLookupSpEpbyAssocEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaSpEpAssocId, -- shared index m3uaLookupSpEpId } -- shared index ::= { m3uaLookupSpEpbyAssocTable 1 } M3uaLookupSpEpbyAssocEntry ::= SEQUENCE { m3uaLookupSpEpId Unsigned32 } m3uaLookupSpEpId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Signaling Process Endpoint Identification Value." ::= { m3uaLookupSpEpbyAssocEntry 1 } ----------------------------------------------------------------------- -- M3UA LOOKUP REVERSE TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ROUTING KEYS BY APPLICATION ID ----------------------------------------------------------------------- -- This table allows the obtention of the Routing Keys for an specific -- Application. m3uaLookupRkbyAppTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaLookupRkbyAppEntry MAX-ACCESS not-accessible STATUS current Roque, et al [Page 46] Internet Draft M3UA MIB using SMIv2 August, 2002 DESCRIPTION "A table containing the list of Routing Keys defined for an Application." ::= { m3uaLookup 2 } m3uaLookupRkbyAppEntry OBJECT-TYPE SYNTAX M3uaLookupRkbyAppEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaPeerAppId, -- shared index m3uaLookupRKId } -- shared index ::= { m3uaLookupRkbyAppTable 1 } M3uaLookupRkbyAppEntry ::= SEQUENCE { m3uaLookupRKId Unsigned32 } m3uaLookupRKId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Routing Key Identification Value." ::= { m3uaLookupRkbyAppEntry 1 } ----------------------------------------------------------------------- -- M3UA LOOKUP REVERSE TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ROUTING KEYS BY DPC-NA ----------------------------------------------------------------------- -- This table allows the obtention of the Routing Key for an specific -- DPC-NA combination. m3uaLookupRkbyDpcNaTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaLookupRkbyDpcNaEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing the list of Routing Keys defined for an Application." ::= { m3uaLookup 3 } m3uaLookupRkbyDpcNaEntry OBJECT-TYPE SYNTAX M3uaLookupRkbyDpcNaEntry Roque, et al [Page 47] Internet Draft M3UA MIB using SMIv2 August, 2002 MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaRKDpc, -- shared index m3uaRKNa, -- shared index m3uaRKId } -- shared index ::= { m3uaLookupRkbyDpcNaTable 1 } M3uaLookupRkbyDpcNaEntry ::= SEQUENCE { m3uaLookupRKbyDpcNaId Unsigned32 } m3uaLookupRKbyDpcNaId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Routing Key Identification Value." ::= { m3uaLookupRkbyDpcNaEntry 1 } ----------------------------------------------------------------------- -- M3UA LOOKUP REVERSE TABLES ----------------------------------------------------------------------- ----------------------------------------------------------------------- -- ENDPOINTS BY APPLICATION ID ----------------------------------------------------------------------- -- This table allows the obtention of the Endpoints serving an specific -- Application. m3uaLookupSpEpbyAppTable OBJECT-TYPE SYNTAX SEQUENCE OF M3uaLookupSpEpbyAppEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing the list of Endpoints Id serving an Application." ::= { m3uaLookup 4 } m3uaLookupSpEpbyAppEntry OBJECT-TYPE SYNTAX M3uaLookupSpEpbyAppEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Point Code Entry." INDEX { m3uaAppId, -- shared index m3uaLookupSpEpbyAppId } -- shared index ::= { m3uaLookupSpEpbyAppTable 1 } Roque, et al [Page 48] Internet Draft M3UA MIB using SMIv2 August, 2002 M3uaLookupSpEpbyAppEntry ::= SEQUENCE { m3uaLookupSpEpbyAppId Unsigned32 } m3uaLookupSpEpbyAppId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Signaling Process Endpoint Identification Value." ::= { m3uaLookupSpEpbyAppEntry 1 } -- 4.1 Conformance Information m3uaGroups OBJECT IDENTIFIER ::= { m3uaConformance 1 } m3uaCompliances OBJECT IDENTIFIER ::= { m3uaConformance 2 } -- 4.1.1 Compliance Statements m3uaCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMPv3 entities which implement M3UA. The M3UA MIB specifies in this compliant implementation that Only need to support IPv4/IPv6 addresses without a zone index, unknown type and DNS names. Support for IPv4/IPv6 addresses without zone indices is not required." MODULE -- this module MANDATORY-GROUPS { m3uaAttributesGroup, m3uaLogAppAttributesTableGroup, m3uaSpEpAttributesTableGroup, m3uaAppSpEpAttributesTableGroup, m3uaRoutingAttributesTableGroup, m3uaRKSiAttributesTableGroup, m3uaRKOpcAttributesTableGroup, m3uaRKCicRangeAttribTableGroup, m3uaNaAttributesTableGroup, m3uaPcAttributesTableGroup, m3uaLocAddrAttributesTableGroup, m3uaRemAddrAttributesTableGroup } OBJECT m3uaAssocLocalAddressIPType SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2) } Roque, et al [Page 49] Internet Draft M3UA MIB using SMIv2 August, 2002 DESCRIPTION "It is only required to have IPv4 and IPv6 addresses without zone indices. Unknown values must also be supported in case the IP address has an invalid/unknown format." OBJECT m3uaAssocRemAddressIPType SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2) } DESCRIPTION "It is only required to have IPv4 and IPv6 addresses without zone indices. Unknown values must also be supported in case the IP address has an invalid/unknown format." ::= { m3uaCompliances 1 } -- 4.1.2 Units of conformance m3uaAttributesGroup OBJECT-GROUP OBJECTS { m3uaVersion, m3uaProcType, m3uaLocalPort, m3uaTrValue, m3uaTBeatValue, m3uaTAckValue, m3uaTPaudValue, m3uaHeartBeat, m3uaSpLshMethod, m3uaStreamLshMethod, m3uaFailOverBuffSize, m3uaRoutingFailures } STATUS current DESCRIPTION "The m3ua group of objects providing for management of M3UA entities. Common parameters for the protocol." ::= { m3uaGroups 1 } m3uaLogAppAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaAppId, m3uaAppType, m3uaAppState, m3uaAppTrafficMode, m3uaAppUnreachable } STATUS current DESCRIPTION "The m3ua group of objects to manage ASs/SGs and IPSs." ::= { m3uaGroups 2 } m3uaSpEpAttributesTableGroup OBJECT-GROUP Roque, et al [Page 50] Internet Draft M3UA MIB using SMIv2 August, 2002 OBJECTS { m3uaSpEpId, m3uaSpEpAssocId, m3uaSpEpAssocRemHostName, m3uaSpEpAssocRemPort, m3uaSpEpAssocReqOutStreams, m3uaSpEpAssocOutStreams, m3uaSpEpAssocIncStreams, m3uaSpEpAssocState, m3uaSpEpAssocState, m3uaSpEpAssocDataOut, m3uaSpEpAssocDataIn, m3uaSpEpAssocAspupOut, m3uaSpEpAssocAspupAckOut, m3uaSpEpAssocAspacOut, m3uaSpEpAssocAspacAckOut, m3uaSpEpAssocAspdnOut, m3uaSpEpAssocAspdnAckOut, m3uaSpEpAssocAspiaOut, m3uaSpEpAssocAspiaAckOut, m3uaSpEpAssocAspupIn, m3uaSpEpAssocAspupAckIn, m3uaSpEpAssocAspacIn, m3uaSpEpAssocAspacAckIn, m3uaSpEpAssocAspdnIn, m3uaSpEpAssocAspdnAckIn, m3uaSpEpAssocAspiaIn, m3uaSpEpAssocAspiaAckIn, m3uaSpEpAssocNotifyOut, m3uaSpEpAssocErrorOut, m3uaSpEpAssocNotifyIn, m3uaSpEpAssocErrorIn, m3uaSpEpAssocDunaOut, m3uaSpEpAssocDavaOut, m3uaSpEpAssocSconOut, m3uaSpEpAssocDupuOut, m3uaSpEpAssocDaudOut, m3uaSpEpAssocDunaIn, m3uaSpEpAssocDavaIn, m3uaSpEpAssocSconIn, m3uaSpEpAssocDupuIn, m3uaSpEpAssocDaudIn } STATUS current DESCRIPTION "The m3ua group of objects to manage SP Endpoints." ::= { m3uaGroups 3 } m3uaAppSpEpAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaAppSpEpState } Roque, et al [Page 51] Internet Draft M3UA MIB using SMIv2 August, 2002 STATUS current DESCRIPTION "The m3ua group of objects to manage Signaling Processes (SGPs, ASPs or IPSPs) for the different Applications they are serving." ::= { m3uaGroups 4 } m3uaRoutingAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaRKId, m3uaRKDpc, m3uaRKNa, m3uaPeerAppId, m3uaPeerAppTrafficMode } STATUS current DESCRIPTION "The m3ua group of objects to manage Routing Tables." ::= { m3uaGroups 5 } m3uaRKSiAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaRKSi } STATUS current DESCRIPTION "The m3ua group of objects to manage SI Table for a RKey." ::= { m3uaGroups 6 } m3uaRKOpcAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaRKOpc } STATUS current DESCRIPTION "The m3ua group of objects to manage OPC Table for a RKey." ::= { m3uaGroups 7 } m3uaRKCicRangeAttribTableGroup OBJECT-GROUP OBJECTS { m3uaRKCicMin, m3uaRKCicMax } STATUS current DESCRIPTION "The m3ua group of objects to manage CIC Table for a RKey." ::= { m3uaGroups 8 } m3uaNaAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaNaNI, m3uaNaMtp3ProtocolType, m3uaNaMtp3ProtocolVariant, m3uaNaMtp3ProtocolVersion } Roque, et al [Page 52] Internet Draft M3UA MIB using SMIv2 August, 2002 STATUS current DESCRIPTION "The m3ua group of objects to manage NA Tables." ::= { m3uaGroups 9 } m3uaPcAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaNaPC } STATUS current DESCRIPTION "The m3ua group of objects to manage PC Tables." ::= { m3uaGroups 10 } m3uaLocAddrAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaAssocLocalAddressIPType, m3uaAssocLocalAddressIP } STATUS current DESCRIPTION "The m3ua group of objects to manage Local IP Add. Tables." ::= { m3uaGroups 11 } m3uaRemAddrAttributesTableGroup OBJECT-GROUP OBJECTS { m3uaAssocRemAddressIPType, m3uaAssocRemAddressIP } STATUS current DESCRIPTION "The m3ua group of objects to manage Remote IP Add. Tables." ::= { m3uaGroups 12 } END 5. References [M3UA] G. Sidebottom, L. Ong, Guy Mousseau, K. Gradischnig, H. J. Schwarzbauer, K. Morneault, I. Rytina, M. Kalla, N. Glaude, "SS7 MTP3-User Adaptation Layer (M3UA)", Internet Draft <draft-ietf-sigtran-m3ua-11.txt>, January 2002. [MIBMPLS] Cucchiara et al. "Definnitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP)", Internet Draf <draft-ietf-mpls-ldp-mib-04.txt>, January 2000. [SecSNMP] Stallings, W., "SNMP3: A Security Enhancement for SNMP", Roque, et al [Page 53] Internet Draft M3UA MIB using SMIv2 August, 2002 IEEE Communication Surveys, Forth quarter 1998, Vol. 1 No. 1. [Cong] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1988, Stanford, California. [RFC2571] Harrington, D., Presuhn, R.,and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [RFC1906] 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. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Roque, et al [Page 54] Internet Draft M3UA MIB using SMIv2 August, 2002 Management Protocol (SNMPv2)", RFC 1905, January 1996. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, Harvard University, March 1997 [RFC2851-update] Textual Conventions for Internet Network Addresses, draft-ietf-ops-rfc2851-update-04.txt, Septemeber 20, 2001. Work in progress. [RFC2786] R. Frye,D. Levi ,S. Routhier, B. Wijnen , " Coexistence between Version 1, Version 2, and Version 3 of the Internet standard Network Management Framework ", draft-ietf-ops- rfc2851-update-06.txt, DEcember 2000. [TADRESS] Textual Conventions for Transport Addresses, draft-ietf-ops-taddress-mib-01.txt, Septemeber 20, 2001. Work in progress. 6. Security Consideration There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. It is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment. SNMPv1 by itself is not a secure environment. Even if security measures are taken (e.g., using IPSEC), there is no per-user control as to who (once an IPSEC association is established between hosts) is allowed to GET or SET the objects in this MIB It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User- Roque, et al [Page 55] Internet Draft M3UA MIB using SMIv2 August, 2002 based Security Model RFC 2574 [RFC2574] and the View-based Access Control Model RFC 2575 [RFC2575] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 7. Acknowledgments The author wish to thank Shyamal Prasad, Kurt Kite, Jennifer Jones, Srivats P., Ken Morneault and Javier Pastor for their comments. 8. Authors' Addresses Antonio Roque Tel: +34-91-339-3523 Ericsson Espana S.A. EMail: Antonio.Roque@ericsson.com Network Communication Services Omb” 3, 4th floor Madrid, 28045 Spain 9. Revision History 9.1 Changes from draft rev 03 to draft rev 04: o Integer32 is imported but not used. Removed o TEXTUAL-CONVENTION is imported but not used. Removed o mib-2 suggested as branch for mib o m3uaAppSpEpState consistently defined as INTEGER o m3uaPeerAppTrafficMode consistently defined as INTEGER o Fixed error in m3uaSpEpEntry object description text o Rework in m3uaAppType object description text 9.2 Changes from draft rev 02 to draft rev 03: o Value range of m3uaAppTrafficMode object is modified. o Object m3uaLocalPort is changed to "read-write". A comment is added with the recommended IANA port number. Roque, et al [Page 56] Internet Draft M3UA MIB using SMIv2 August, 2002 o Object m3uaFailOverBuffering is deleted. A comment in object m3uaTrValue is added: If Tr is 0 then FailOver Buffering is Off. Thus, there is no further need for this element. o Object m3uaMaxPeerApplications is deleted. o Object m3uaMaxSPperApplications is deleted. o Object m3uaAppType is added to Logical Application Table. o Replace "Sent" by "out" and "Received" by "in" in statistics. o Object m3uaSSN is deleted from Routing Table o Object m3uaNI is deleted from Routing Table o Object m3uaPeerAppTrafficMode is added to Routing Table o Index m3uaAppId in SP Endpoint Statistic Table is removed o Signaling Process Table replaced by Application-Endpoint Table o Index m3uaSpEpAssocId in SP Endpoint Table is removed o Index m3uaSpEpassocId in Local and Remote IP address table is replaced by m3uaSpEpId. o Added new Lookup Reverse Tables for: - Get EndPoint Id from Association Id. - Get Routing Key Id from Application Id. - Get Routing Key Id from DPC and NA. - Get Endpoints serving an Application. o Routing Table has been reestructured to deal with multiplicity of SIs, OPCs and CIC Ranges per Routing Key. Three new subtables are used. 9.3 Changes from draft rev 01 to draft rev 02: o Section 3.1.2.3 Signaling Process Table - Chapter re-phrased o Section 3.1.2.4 Signaling Process Endpoint Table - Last paragraph removed o Section 3.1.2.5 Signaling Process Endpoint Statistics Table m3uaAppId and m3uaSpEpId added to the table figure Corresponding changes in Definitions chapter applied. o Section 3.1.2.6 Network Appearance Table Fixed Duplicate Section No. Roque, et al [Page 57] Internet Draft M3UA MIB using SMIv2 August, 2002 m3uaNaRowStatus added to table figure. Corresponding changes in Definitions chapter applied. o Object definition of m3uaMaxStreamInbound is removed. o Object Definition of m3uaSpEpEntry Index "m3uaAppId" is replaced by m3uaSpEpAssocId. o Object Definition of m3uaSpEpStatRowStatus Definition is deleted. 9.4 Changes due to the alignment with the RFC2851 update. o Include clarification text of the IP address types supported in the M3UA MIB. Chapter 3.1.2.7.2 (Local and Remote IP address table) o Remote Primary IP address: Addition of the ipv4z an ipv6z types for non-globally IP addresses in which a scope identifier is needed. Addition of the scope of ipv6 type. All of them according to the RFC2851update-v04 o InetAddressType for local and remote IP addresses: Limit UNKNOWN type only for unknown IP address format. Remove UNKNOWN type for zero-length value in the InetAddress since it will be never zero-length due to the size restriction (0..64) Addition of the ipv4z an ipv6z types for non-globally IP addresses in which a scope identifier is needed. Addition of the scope of ipv6 type. All of them according to the RFC2851update-v04 o Conformance: Description: Specify that the M3UA MIB only need to support IPv4/IPv6 addresses without a zone index, unknown type and DNS names. Support for IPv4/IPv6 addresses without zone indices is not required. InetAddressType of local and remote IP address: Clarify the implementation is only required to support IPv4 and IPv6 address types without zone indices. Clarify also that UNKONWN type is only used in case of lcoal and remote addresses when invalid/unknown IP address format Roque, et al [Page 58] | ||||||||||||||||
Last modified: Mon, 26 Aug 2024 23:55:09 GMT Copyright © 2014 OpenSS7 Corporation All Rights Reserved. |