draft-ietf-sigtran-m3ua-mib-04.txt   draft-ietf-sigtran-m3ua-mib-05.txt 
Network Working Group Antonio Roque Network Working Group Antonio Roque
INTERNET-DRAFT Ericsson INTERNET-DRAFT Antonio Canete
Javier Pastor-Balbas
Ericsson
Expires in six months August, 2002 Expires in six months June, 2003
SS7 MTP3-User Adaptation Layer (M3UA) SS7 MTP3-User Adaptation Layer (M3UA)
Management Information Base using SMIv2 Management Information Base using SMIv2
<draft-ietf-sigtran-m3ua-mib-04.txt> <draft-ietf-sigtran-m3ua-mib-05.txt>
Status of This Memo Status of This Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. Internet-Drafts are working provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distributeworking its working groups. Note that other groups may also distributeworking
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and Internet-Drafts are draft documents valid for a maximum of six months and
skipping to change at page 1, line 42 skipping to change at page 1, line 44
directed to the authors. directed to the authors.
Abstract Abstract
The MTP3-User Adaptation Layer is a protocol for the transport of any SS7 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 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the
services of the Stream Control Transmission Protocol. Also, provision is services of the Stream Control Transmission Protocol. Also, provision is
made for protocol elements that enable a seamless operation of the MTP3- 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 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- a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or IP-
resident Database. It is assumed that the SG receives SS7 signalling over resident Database. It is assumed that the SG receives SS7 signaling over
a standard SS7 interface usingthe SS7 Message Transfer Part (MTP) to a standard SS7 interface usingthe SS7 Message Transfer Part (MTP) to
provide transport. provide transport.
This memo defines the Management Information Base (MIB) module which This memo defines the Management Information Base (MIB) module which
describes the minimum amount of objects needed to manage the describes the minimum amount of objects needed to manage the
implementation of the M3UA. implementation of the M3UA.
Open Issues Open Issues
- Remove this section. - Remove this section.
- Remove Revision History - Remove Revision History
- Decide under which object identifier branch of the SNMP tree, M3UA will - Decide under which object identifier branch of the SNMP tree, M3UA will
be placed (value obtained when submitted to the IETF editor). be placed (value obtained when submitted to the IETF editor).
- Update references to drafts. - Update references to drafts.
- Check Security Considerations section
Table of Contents Table of Contents
Status of This Memo.......................................1 1. Introduction...........................................4
1. Introduction..........................................3 1.1 Abbreviations.........................................4
1.1 Abbreviations........................................3 2. The Internet-Standard Management Framework..............4
2. The SNMP Framework....................................4 3. Structure of the MIB...................................5
3. Structure of the MIB..................................5 3.1 Management............................................6
3.1 Management...........................................6 3.1.1 Attributes..........................................6
3.1.1 Attributes.........................................6 3.1.1.1 Protocol General Variables.........................6
3.1.1.1 Protocol General Variables........................6 3.1.1.2 Protocol General Statistics........................6
3.1.1.2 Protocol General Statistics.......................6 3.1.2 ASPTables...........................................6
3.1.2 Tables.............................................6 3.1.2.1 Destination Table..................................7
3.1.2.1 Logical Application Table.........................6 3.1.2.2 Signaling Gateway Process Table....................8
3.1.2.2 Logical Application Statistics Table..............7 3.1.2.3 Association Table..................................8
3.1.2.3 Signaling Process Endpoint Table..................7 3.1.2.4 Routing Context Table..............................9
3.1.2.4 Signaling Process Endpoint Statistics Table.......8 3.1.2.5 ASP Statistics Table..............................10
3.1.2.5 Application-Endpoint Table........................9 3.1.3 SGP/IPSP Tables....................................11
3.1.2.6 Routing Table....................................10 3.1.3.1 Routing Table.....................................11
3.1.2.7 Network Appearance Table.........................10 3.1.3.2 Application Server(AS) Table......................12
3.1.2.8 Expanded Tables..................................11 3.1.3.3 Application Server Process Table..................13
3.1.2.8.1 Service Indicator Table........................11 3.1.3.4 Application Server Process Association Table......14
3.1.2.8.2 OPC Table......................................11 3.1.3.5 SGP / IPSP Statistics Table.......................14
3.1.2.8.3 CIC Range Table................................11 3.1.4 Generic Tables.....................................16
3.1.2.8.4 Point Code Table...............................12 3.1.4.1 Network Appearance Table..........................16
3.1.2.8.5 Local and Remote IP Address Tables.............12 3.1.4.2 Generic Statistics Table..........................16
3.1.2.9 Reverse Lookup Tables............................13 3.2 Conformance..........................................17
3.2 Conformance.........................................14 3.2.1 Groups..............................................18
3.2.1 Groups.............................................14 3.2.2 Compliance..........................................18
3.2.2 Compliance.........................................14 4. Definitions...........................................18
4. Definitions..........................................14 5.1 Normative References..................................58
5. References...........................................54 5.2 Informative References................................59
6. Security Consideration................................56 6. Security Considerations................................60
7. Acknowledgments.......................................56 7. Acknowledgements.......................................60
8. Authors' Addresses....................................56 8. Authors' Addresses.....................................60
9. Revision History......................................56 9. Revision History.......................................61
9.1 Changes from draft rev 03 to draft rev 04:...........57 9.1 Changes from draft rev 04 to draft rev 05:............61
9.2 Changes from draft rev 02 to draft rev 03:...........57 9.2 Changes from draft rev 03 to draft rev 04:............61
9.3 Changes from draft rev 01 to draft rev 02:...........58 9.3 Changes from draft rev 02 to draft rev 03:............62
9.4 Changes due to the alignment with the RFC2851 update. 58 9.4 Changes from draft rev 01 to draft rev 02:............63
9.5 Changes due to the alignment with the RFC2851 update..63
1. Introduction 1. Introduction
This memo defines the Management Information Base (MIB) module which This memo defines the Management Information Base (MIB) module which
describes managed objects for implementations of the M3UA. describes managed objects for implementations of the M3UA.
The document starts with a brief description of the SNMP framework and The document starts with a brief description of the SNMP framework and
continues with the MIB explanation and security consideration among continues with the MIB explanation and security consideration among
others. others.
Terms related to the SCTP architecture are explained in [1]. Other Terms related to the SCTP architecture are explained in [1]. Other
skipping to change at page 3, line 32 skipping to change at page 4, line 32
AS - Application Server AS - Application Server
ASP - Application Server Process ASP - Application Server Process
ASPM - Application Server Process Management ASPM - Application Server Process Management
CIC - Circuit Identification Code CIC - Circuit Identification Code
DPC - Destination Point Code DPC - Destination Point Code
IPSP - IP Server Process IPSP - IP Server Process
MIB - Management Information Base MIB - Management Information Base
M3UA - SS7 MTP3-User Adaptation Layer M3UA - SS7 MTP3-User Adaptation Layer
NA - Network Appearance NA - Network Appearance
NI - Network Indicator NI - Network Indicator
OPC - Origination Point Code OPC - Originating Point Code
PC - Point Code PC - Point Code
SCTP - Stream Control Transmision Protocol SCTP - Stream Control Transmission Protocol
SG - Signaling Gateway SG - Signaling Gateway
SGP - Signaling Gateway Process
SI - Service Indicator SI - Service Indicator
SMI - Structure of Management Information SMI - Structure of Management Information
SNMP - Simple Network Management Protocol SNMP - Simple Network Management Protocol
SP - Signaling Process SP - Signaling Process
SSN - Subsystem Number SSN - Sub-System Number
2. The SNMP Framework
The SNMP Management Framework presently consists of five major
components:
- An overall architecture, described in RFC 2271 [SNMPArch].
- 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 2. The Internet-Standard Management Framework
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 For a detailed overview of the documents that describe the current
the view-based access control mechanism described in RFC 2575 Internet-Standard Management Framework, please refer to section 7 of
[SNMPv3VACM]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined using the Management Information Base or MIB. MIB objects are generally
the mechanisms defined in the SMI. This memo specifies a MIB module that accessed through the Simple Network Management Protocol (SNMP).
is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced Objects in the MIB are defined using the mechanisms defined in the
through the appropriate translations. The resulting translated MIB must Structure of Management Information (SMI). This memo specifies a MIB
be semantically equivalent, except where objects or events are omitted module that is compliant to the SMIv2, which is described in STD 58,
because no translation is possible (use of Counter64). Some machine- RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
readable information in SMIv2 will be converted into textual descriptions [RFC2580].
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 3. Structure of the MIB
The MIB is structured in the following way: The MIB is structured in the following way:
m3uaMib MIB-2 {1 3 6 1 2 1}
/ \ |
m3uaManagement m3uaConformance +--(xxxx)m3uaMib
/ \ / \ |
m3uaAttributes m3uaTables m3uaGroups m3uaCompliances +--(1) m3uaManagement
/ \ | | |
m3uaConfig m3uaStatistics m3uaCompliance | +--(1) m3uaAttributes
| | |
| | +--(1) m3uaConfig
| | |
| | +--(2) m3uaStatistics
| |
| |
| +--(2) m3uaTables
|
|
+--(2) m3uaConformance
|
+--(1) m3uaGroups
|
+--(2) m3uaCompliances
|
+--(1) m3uaAspCompliance
|
+--(2) m3uaSgpIpspCompliance
where the following sections are described : 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 o m3uaManagement, where all the objects to manage M3UA are defined
parameters are listed. under this branch.
- m3uaStatistics, where general Statistics for M3UA are listed. - 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 - m3uaTables: where specific attributes for each element that can be
defined and used to manage a M3UA Based System. Every table is defined and used to manage a M3UA Based System. Every table is
structured in the following way: structured in the following way:
m3uaTableName m3uaScopeTablename
| |
m3uaTabAttributes
/ \ / \
m3uaTabConfig m3uaTabStatistics m3uaScopeCfg m3uaScopeStat
Note: Statistics only apply to some of the tables.
These tables hold data for: These tables hold data for:
Logical Application, - Asp: Tables that are implemented in ASP Agents,
Signaling Process, - SgpIpsp: Tables that are implemented in both SGP and IPSP Agents,
Signaling Point Endpoint, - Gen: Tables implemented in all ASP, SGP and IPSP Agents
Routing Keys,
Network Appearances,
Point Codes,
Local and Remote IP Address.
- m3uaConformance, for the Unit of Conformance. o m3uaConformance, for the Unit of Conformance.
- m3uaGroups, M3UA MIB variables have been grouped according to their - m3uaGroups: M3UA MIB variables have been grouped according to
funcionality and the context they belong to. their funcionality and the context they belong to.
- m3uaCompliances, Minimal list of objects in the M3UA - m3uaCompliances: minimal list of objects in the M3UA MIB module
MIB module that an agent developer must implement. that an agent developer must implement.
3.1 Management 3.1 Management
3.1.1 Attributes 3.1.1 Attributes
3.1.1.1 Protocol General Variables 3.1.1.1 Protocol General Variables
The first section of the MIB contains the general variables of the M3UA The first section of the MIB contains the general variables of the
protocol. Maximum, minimum and initial values can be found here. M3UA protocol. Maximum, minimum and initial values can be found here.
3.1.1.2 Protocol General Statistics 3.1.1.2 Protocol General Statistics
Statistics included here relate to the whole M3UA layer. Statistics Statistics included here relate to the whole M3UA layer. Statistics
related to a specific Peer Association are defined inside its concerned per association are defined inside specific association tables.
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. 3.1.2 ASP Tables
m3uaAppStatTable All the tables included within this branch, are tables to be located
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ in the ASP node. These tables will show remote (SGP) or local (ASP)
| m3uaAppId (index) / ... | nodes parameters.
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAppUnreachable / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.3 Signaling Process Endpoint Table The tables have been divided into Configuration Tables (Cfg) and
Statistic Tables (Stat).
Defines data related to a Signaling Process Endpoint. 3.1.2.1 Destination Table
A SP Endpoint identifies a peer node were a Signaling Process (SGP, ASP The destination table is composed of all the parameters needed to find
or IPSP) is running. the right SG to reach the SS7 destination. The addressing parameters
that are needed are: Network Appearance (NA) that univocally reference
the network where the message is sent, and Destination Point Code
(DPC), which is the final address in the SS7 domain.
The table contains the Endpoint identifier and data related to the Each final destination within the SS7 domain can be reached through
association to that endpoint. one or more Signaling Gateways (SGs). The state of the destination may
be different for each SG and AS pairs.
This table is expanded with the Remote IP Address Table that identify the The result of this table would be the final destination state. An SS7
endpoint and with the Local IP Address Table that identify the local node node may be available, unavailable, congested, restricted or unknown.
for that endpoint. There may be certain cases where its state is unknown, e.g. after
initialization.
The table contains data related to the SCTP association to that endpoint, mib-2 {1 3 6 1 2 1}
as its state, number of streams, and the Association ID, provided by SCTP +--(xxxx) m3uaMib
when the association is established. |
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
: +--(1) m3uaAsp
: |
+--(1) m3uaAspCfg
| |
: +--(1) m3uaAspDestTable
: | |
: +--(1) m3uaAspDestNa (index)
: |
+--(2) m3uaAspDestDpc (index)
|
+--(3) m3uaAspDestSgId (index)
|
+--(4) m3uaAspDestAsId (index)
|
+--(5) m3uaAspDestState
3.1.2.2 Signaling Gateway Process Table
m3uaSpEpTable This table compiles the SGPs that serve a SG. An SGP may be only
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ activated for certain ASes.
| m3uaSpEpId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocId / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocRemHostName / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocRemPort / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocReqOutStreams / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocOutStreams / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocIncStreams / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocState / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.4 Signaling Process Endpoint Statistics Table The result of the table is the status of the AS through a specific
SGP.
Defines statistics related to a Signaling Process Endpoint. mib-2 {1 3 6 1 2 1}
+--(xxxx) m3uaMib
|
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
: +--(1) m3uaAsp
: : |
: +--(1) m3uaAspCfg
| |
: :
: +--(2) m3uaAspSgpTable
| |
: +--(1) m3uaAspSgpAsId (index)
: |
+--(2) m3uaAspSgpSgId (index)
|
+--(3) m3uaAspSgpId (index)
|
+--(4) m3uaAspSgpState
The table contains statistics data related to the M3UA messaging 3.1.2.3 Association Table
exchanged through that association between the Signaling Processes that
hold the association.
m3uaSpEpStatTable From an ASP point of view, an SGP can be reached using the association
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ established to it. This table allows to know the identification for
| m3uaSpEpId (index) / ... | the association to a concrete SGP as well as the SCTP streams
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ constraints imposed by M3UA to the lower layer.
| m3uaSpEpAssocId / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDataOut / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDataRecived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.5 Application-Endpoint Table mib-2 {1 3 6 1 2 1}
+--(xxxx) m3uaMib
|
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
: +--(1) m3uaAsp
: |
+--(1) m3uaAspCfg
| |
: :
: +--(3) m3uaAspAssocTable
| |
: +--(1) m3uaAspAssocSgpId (index)
: |
+--(2) m3uaAspAssocId
|
+--(3) m3uaAspAssocMinOutStreams
|
+--(4) m3uaAspAssocMaxInStreams
Defines data related to the endpoint where a Signaling Process is 3.1.2.4 Routing Context Table
running, and the Logical Application IDs which the SP is serving.
A Signaling Process is a process instance that uses M3UA to communicate The Routing Context (RC)is an optional parameter as per RFC3332. When
with other signalling process. An ASP, an SGP and an IPSP are all this parameter is used by an M3UA implementation, this table will show
signalling processes. the values that it takes.
As a SP can maintain different states and traffic handling modes for RC scope is per SGP where each AS has an associated RC value.
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 mib-2 {1 3 6 1 2 1}
Endpoint will have a common link, the Endpoint Id. +--(xxxx) m3uaMib
|
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
: +--(1) m3uaAsp
: : |
: +--(1) m3uaAspCfg
| |
: :
: +--(3) m3uaAspRcTable
| |
: +--(1) m3uaAspRcSgpId (index)
: |
+--(2) m3uaAspRcAsId (index)
|
+--(3) m3uaAspRcValue
m3uaAppSpEpTable 3.1.2.5 ASP Statistics Table
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAppId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAppSpEpState / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAppSpEpRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.6 Routing Table It defines statistics specific to an Application Server Process.
Every entry in this table contains the data that defines a Routing Key. Statistics applicable to SGP, ASP and IPSP are covered in the generic
statistics table.
As a Routing Key may be composed of any combination of basic SS7 Routing mib-2 {1 3 6 1 2 1}
elements, if an element is not included in the routing key, a default +--(xxxx) m3uaMib
value is assigned. This default value can continue being considered as an |
indexing value itself. +--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
: +--(1) m3uaAsp
: : |
: :
+--(2) m3uaAspStat
| |
: |
: +--(1) m3uaAspStatTable
| |
: +--(1) m3uaAspStatAssocId (index)
: |
+--(2) m3uaAspStatAspupOut
|
+--(3) m3uaAspStatAspacOut
|
+--(4) m3uaAspStatAspdnOut
|
+--(5) m3uaAspStatAspiaOut
|
+--(6) m3uaAspStatAspupAckIn
|
+--(7) m3uaAspStatAspacAckIn
|
+--(8) m3uaAspStatAspdnAckIn
|
+--(9) m3uaAspStatAspiaAckIn
|
+--(10) m3uaAspStatNotifyIn
|
+--(11) m3uaAspStatDaudOut
|
+--(12) m3uaAspStatDunaIn
|
+--(13) m3uaAspStatDavaIn
|
+--(14) m3uaAspStatDupuIn
m3uaRouting 3.1.3 SGP/IPSP Tables
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaRKId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaRKDpc / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaRKNa / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaPeerAppId / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaPeerAppTrafficMOde / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaRoutingRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.7 Network Appearance Table All the tables included within this branch are tables to be located in
the SGP or IPSP node. These tables will show remote (ASP/IPSP) node
parameters.
Defines the data specific to a Network Appearance. The tables have been divided into Configuration Tables (Cfg) and
Statistics Tables (Stat).
m3uaNaTable 3.1.3.1 Routing Table
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNA (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaNI / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaMtp3ProtocolType / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaMtp3ProtocolVariant / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaMtp3ProtocolVersion / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.8 Expanded Tables The Routing table contains a list of routing keys, which translate to
an Application Server ID and a corresponding Routing Context.
3.1.2.8.1 Service Indicator Table 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.
This table expand information in entries in Routing Table. mib-2 {1 3 6 1 2 1}
A Routing Key can be composed by a list of Service Indicators. +--(xxxx) m3uaMib
|
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
| :
| :
| |
: +--(2) m3uaSgpIpsp
: |
+--(1) m3uaSgpIpspCfg
| |
: +--(1) m3uaSgpIpspRtgTable
: | |
: +--(1) m3uaSgpIpspRtgNa (index)
: |
+--(2) m3uaSgpIpspRtgDpc (index)
|
+--(3) m3uaSgpIpspRtgSi (index)
|
+--(4) m3uaSgpIpspRtgOpc (index)
|
+--(5) m3uaSgpIpspRtgAsId
|
+--(6) m3uaSgpIpspRtgRc
m3uaSi 3.1.3.2 Application Server(AS) Table
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaRKId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaRKSi / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaRKSiRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.8.2 OPC Table The Application Server table contains information on the state and
traffic mode of each Application for which one or more routing keys
can exist in the Signalling Gateway or IPSP routing table.
This table expand information in entries in Routing Table. mib-2 {1 3 6 1 2 1}
A Routing Key can be composed by a list of OPCs. +--(xxxx) m3uaMib
|
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
| :
| :
| |
: +--(2) m3uaSgpIpsp
: |
+--(1) m3uaSgpIpspCfg
| |
: :
m3uaOpc : +--(2) m3uaSgpIpspAsTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| m3uaRKId (index) / ... | : +--(1) m3uaSgpIpspAsId (index)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : |
| m3uaRKOPc / ... | +--(2) m3uaSgpIpspAsState
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| m3uaRKOpcRowStatus / ... | +--(3) m3uaSgpIpspAsTmt
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.8.3 CIC Range Table 3.1.3.3 Application Server Process (ASP) Table
This table expand information in entries in Routing Table. This table shows the State of the Application Server Process or IPSP
A CIC Range can be defined for some of the OPC's which compose a Routing for each Application Server, and the role of the ASP in the AS traffic
Key. distribution, according to each AS traffic mode.
m3uaCicRange mib-2 {1 3 6 1 2 1}
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +--(xxxx) m3uaMib
| m3uaRKId (index) / ... | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +--(1) m3uaManagement
| m3uaRKOPc (index) / ... | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | :
| m3uaRKCicMin / ... | | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| m3uaRKCicMax / ... | | +--(2) m3uaTables
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| m3uaRKCicRowStatus / ... | | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | :
| |
: +--(2) m3uaSgpIpsp
: |
+--(1) m3uaSgpIpspCfg
| |
: :
: +--(3) m3uaSgpIpspAspTable
| |
: +--(1) m3uaSgpIpspAspAsId (index)
: |
+--(2) m3uaSgpIpspAspId (index)
|
+--(3) m3uaSgpIpspAspState
|
+--(4) m3uaSgpIpspAspRole
3.1.3.4 Application Server Process (ASP) Association Table
3.1.2.8.4 Point Code Table It defines data related to the SCTP Association for an Application
Server Process or IPSP.
This table expand information in entries in Network Appearance Table. Further Association data can be obtained from the SCTP MIB.
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 mib-2 {1 3 6 1 2 1}
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +--(xxxx) m3uaMib
| m3uaNA (index) / ... | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +--(1) m3uaManagement
| m3uaNaPC(index) / ... | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | :
| m3uaNaPcRowStatus / ... | | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |
| +--(2) m3uaTables
| |
| :
| :
| |
: +--(2) m3uaSgpIpsp
: |
+--(1) m3uaSgpIpspCfg
| |
: :
: +--(4) m3uaSgpIpspAssocTable
| |
: +--(1) m3uaSgpIpspAssocAspId (index)
: |
+--(2) m3uaSgpIpspAssocId
|
+--(3) m3uaSgpIpspAssocReqOutStreams
3.1.2.8.5 Local and Remote IP Address Tables 3.1.3.5 SGP / IPSP Statistics Table
These tables expand information for SP Endpoint Tables. When an SP It defines statistics specific to a Signaling Gateway Process or IP
Endpoint entry is created, a default free Association Id is assigned to Signaling Process.
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: Statistics applicable to SGP, ASP and IPSP are covered in the generic
This table stores information related to the local IP address/-es statistics table.
reserved for the association. It's indexed by the IP address.
b) Table for remote IP addresses information: For the IPSP, the ASP Statistics table also applies.
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 The table contains statistics data related to the M3UA messages
InetAddressType defined in the Textual Conventions for Internet Network exchanged through each association at the SGP or IPSP.
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]: mib-2 {1 3 6 1 2 1}
global and non-global (either with a zone index or not) IPv4 addresses, +--(xxxx) m3uaMib
global and non-global (either with a zone index or not) IPv6 addresses. |
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
| :
| :
| |
: +--(2) m3uaSgpIpsp
: : |
: :
+--(2) m3uaSgpIpspStat
| |
: |
: +--(1) m3uaSgpIpspStatTable
| |
: +--(1) m3uaSgpIpspStatAssocId (index)
: |
+--(2) m3uaSgpIpspStatAspupAckOut
|
+--(3) m3uaSgpIpspStatAspacAckOut
|
+--(4) m3uaSgpIpspStatAspdnAckOut
|
+--(5) m3uaSgpIpspStatAspiaAckOut
|
+--(6) m3uaSgpIpspStatAspupIn
|
+--(7) m3uaSgpIpspStatAspacIn
|
+--(8) m3uaSgpIpspStatAspdnIn
|
+--(9) m3uaSgpIpspStatAspiaIn
|
+--(10) m3uaSgpIpspStatNotifyOut
|
+--(11) m3uaSgpIpspStatDunaOut
|
+--(12) m3uaSgpIpspStatDavaOut
|
+--(13) m3uaSgpIpspStatDupuOut
|
+--(14) m3uaSgpIpspStatDaudIn
However, DNS value is not being used to identify an IP address since it 3.1.4 Generic Tables
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 3.1.4.1 Network Appearance Table
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocLocalAddressIPType(index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocLocalAddressIP (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocLocalAddressRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
m3uaAssocRemAddressTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocRemAddressIPType(index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocRemAddressIP (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocRemAddressRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.9 Reverse Lookup Tables It defines the data specific to a Network Appearance.
There are four reverse lookup tables to help management applications to mib-2 {1 3 6 1 2 1}
efficiently access conceptual rows in other tables. This is the way for +--(xxxx) m3uaMib
not performing expensive tree walks through large number of associations. |
All of these tables are optional. +--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
: :
: :
+--(3) m3uaGen
|
+--(1) m3uaGenCfg
| |
: +--(1) m3uaGenNaTable
| |
: +--(1) m3uaGenNaValue (index)
: |
+--(2) m3uaGenNaNi
|
+--(3) m3uaGenNaMtp3ProtType
|
+--(4) m3uaGenNaMtp3ProtVariant
|
+--(5) m3uaGenNaMtp3ProtVersion
The defined reversed lookup tables allow performing a lookup using the 3.1.4.2 Generic Statistics Table
following variables: Defines statistics common to Application Server Processes, Signaling
Gateway Processes and IP Signaling Processes.
- Get Signaling Process Endpoint from Association: Obtains the LOCAL The table contains statistics data related to the M3UA messages
Identifier of the Endpoint that is connected through the Specified exchanged through each association at the Signaling Process.
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. mib-2 {1 3 6 1 2 1}
+--(xxxx) m3uaMib
|
+--(1) m3uaManagement
| |
| :
| :
| |
| +--(2) m3uaTables
| |
: :
: :
|
+--(3) m3uaGen
|
:
:
|
+--(2) m3uaGenStat
| |
: +--(1) m3uaGenStatTable
| |
: +--(1) m3uaGenStatAssocId (index)
: |
+--(2) m3uaGenStatAssocDataOut
|
+--(3) m3uaGenStatAssocDataIn
|
+--(4) m3uaGenStatAssocErrorOut
|
+--(5) m3uaGenStatAssocErrorIn
|
+--(6) m3uaGenStatAssocSconOut
|
+--(7) m3uaGenStatAssocSconIn
3.2 Conformance 3.2 Conformance
3.2.1 Groups 3.2.1 Groups
This section includes all the variables defined in the MIB grouped by This section includes all the variables defined in the MIB grouped by
function. function.
3.2.2 Compliance 3.2.2 Compliance
Requirements of the M3UA MIB to be implemented. Requirements of the M3UA MIB to be implemented.
4. Definitions 4. Definitions
skipping to change at page 14, line 10 skipping to change at page 18, line 18
3.2.2 Compliance 3.2.2 Compliance
Requirements of the M3UA MIB to be implemented. Requirements of the M3UA MIB to be implemented.
4. Definitions 4. Definitions
M3UA-MIB DEFINITIONS ::= BEGIN M3UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Counter32, Counter64, mib-2
Counter32, Counter64, mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
RowStatus
TruthValue
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB -- RFC 2851
; ;
m3uaMIB MODULE-IDENTITY m3uaMIB MODULE-IDENTITY
LAST-UPDATED "200208060000Z" LAST-UPDATED "200306050000Z" -- 5th June 2003
ORGANIZATION "IETF SIGTRAN Working Group" ORGANIZATION "IETF SIGTRAN Working Group"
CONTACT-INFO CONTACT-INFO
" Antonio Roque Alvarez "
WG EMail: sigtran@ietf.org
Postal: Ericsson Espana S. A. Web Page:
C/Ombu 3 http://www.ietf.org/html.charters/sigtran-charter.html
28045 Madrid
Spain
Phones: +34 91 339 3523 Chair: Lyndon Ong
Ciena Corporation
0480 Ridgeview Drive
Cupertino, CA 95014
USA
Tel:
Email: lyong@ciena.com
Emails: Antonio.Roque@ericsson.com" Editors: Antonio Roque-Alvarez
R&D Department
Ericsson Espana S. A.
Via de los Poblados, 13
28033 Madrid
Spain
Tel: +34 91 339 3523
Email: Antonio.Roque@ericsson.com
Antonio Canete-Martinez
R&D Department
Ericsson Espana S. A.
Via de los Poblados, 13
28033 Madrid
Spain
Tel: +34 91 339 2460
Email: Antonio.Canete@ericsson.com
Jose-Javier Pastor-Balbas
R&D Department
Ericsson Espana S. A.
Via de los Poblados, 13
28033 Madrid
Spain
Tel: +34 91 339 1397
Email: J.Javier.Pastor@ericsson.com
"
DESCRIPTION DESCRIPTION
"The MIB module for managing M3UA implementation." "The MIB module for managing M3UA implementations.
REVISION "200208060000Z"
DESCRIPTION Copyright (C) The Internet Society (2003). This version of this
"MIB module developed for the SIGTRAN IETF group. MIB module is part of RFC YYYY; see the RFC itself for full
Based on M3UAv11" legal notices. "
::= { mib-2 xxxx } -- IANA needs to choose this value
-- when sent to the RFC editor REVISION "200306050000Z" -- 5th June 2003
DESCRIPTION " Initial version, published as RFC YYYY"
-- RFC Editor: to assign YYYY
::= { mib-2 xxxx }
-- IANA: to assign xxxx
-- RFC Editor: to change xxxx into the value assigned by IANA
-- Top-level structure of the MIB -- Top-level structure of the MIB
m3uaManagement OBJECT IDENTIFIER ::= { m3uaMIB 1 } m3uaManagement OBJECT IDENTIFIER ::= { m3uaMIB 1 }
m3uaConformance OBJECT IDENTIFIER ::= { m3uaMIB 2 } m3uaConformance OBJECT IDENTIFIER ::= { m3uaMIB 2 }
m3uaAttributes OBJECT IDENTIFIER ::= { m3uaManagement 1 } m3uaAttributes OBJECT IDENTIFIER ::= { m3uaManagement 1 }
m3uaTables OBJECT IDENTIFIER ::= { m3uaManagement 2 }
m3uaConfig OBJECT IDENTIFIER ::= { m3uaAttributes 1 } m3uaConfig OBJECT IDENTIFIER ::= { m3uaAttributes 1 }
m3uaStatistics OBJECT IDENTIFIER ::= { m3uaAttributes 2 } m3uaStatistics OBJECT IDENTIFIER ::= { m3uaAttributes 2 }
m3uaLogApplication OBJECT IDENTIFIER ::= { m3uaTables 1 } m3uaTables OBJECT IDENTIFIER ::= { m3uaManagement 2 }
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 } m3uaAsp OBJECT IDENTIFIER ::= { m3uaTables 1 }
m3uaAppSpEpAttributes OBJECT IDENTIFIER ::= { m3uaAppSpEndPoint 1 } m3uaAspCfg OBJECT IDENTIFIER ::= { m3uaAsp 1 }
m3uaAppSpEpConfig OBJECT IDENTIFIER ::= { m3uaAppSpEpAttributes 1} -- m3uaAspDestTable OBJECT IDENTIFIER ::= { m3uaAspCfg 1 }
-- m3uaAspSgpTable OBJECT IDENTIFIER ::= { m3uaAspCfg 2 }
-- m3uaAspAssocTable OBJECT IDENTIFIER ::= { m3uaAspCfg 3 }
-- m3uaAspRcTable OBJECT IDENTIFIER ::= { m3uaAspCfg 4 }
m3uaAspStat OBJECT IDENTIFIER ::= { m3uaAsp 2 }
-- m3uaAspStatTable OBJECT IDENTIFIER ::= { m3uaAspStat 1 }
m3uaRoutingTab OBJECT IDENTIFIER ::= { m3uaTables 4 } m3uaSgpIpsp OBJECT IDENTIFIER ::= { m3uaTables 2 }
m3uaRtAttributes OBJECT IDENTIFIER ::= { m3uaRoutingTab 1 } m3uaSgpIpspCfg OBJECT IDENTIFIER ::= { m3uaSgpIpsp 1 }
m3uaRtConfig OBJECT IDENTIFIER ::= { m3uaRtAttributes 1 } -- m3uaSgpIpspRtgTable OBJECT IDENTIFIER ::= { m3uaSgpIpspCfg 1 }
-- m3uaSgpIpspAsTable OBJECT IDENTIFIER ::= { m3uaSgpIpspCfg 2 }
-- m3uaSgpIpspAspTable OBJECT IDENTIFIER ::= { m3uaSgpIpspCfg 3 }
-- m3uaSgpIpspAssocTable OBJECT IDENTIFIER ::= {m3uaSgpIpspCfg 4}
m3uaSgpIpspStat OBJECT IDENTIFIER ::= { m3uaSgpIpsp 2 }
-- m3uaSgIpspStatTable OBJECT IDENTIFIER ::= { m3uaSgpIpspStat 1 }
m3uaNetworkAppearance OBJECT IDENTIFIER ::= { m3uaTables 5 } m3uaGen OBJECT IDENTIFIER ::= { m3uaTables 3 }
m3uaNaAttributes OBJECT IDENTIFIER ::= { m3uaNetworkAppearance 1} m3uaGenCfg OBJECT IDENTIFIER ::= { m3uaGen 1 }
m3uaNaConfig OBJECT IDENTIFIER ::= { m3uaNaAttributes 1 } -- m3uaGenNaTable OBJECT IDENTIFIER ::= { m3uaGenCfg 1 }
m3uaLookup OBJECT IDENTIFIER ::= { m3uaTables 6 } m3uaGenStat OBJECT IDENTIFIER ::= { m3uaGen 2 }
-- m3uaGenStatTable OBJECT IDENTIFIER ::= { m3uaGenStat 1 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA MANAGEMENT -- M3UA MANAGEMENT
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIGURATION -- ATTRIBUTES - CONFIGURATION
----------------------------------------------------------------------- -----------------------------------------------------------------------
m3uaVersion OBJECT-TYPE m3uaVersion OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
skipping to change at page 15, line 44 skipping to change at page 21, line 8
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIGURATION -- ATTRIBUTES - CONFIGURATION
----------------------------------------------------------------------- -----------------------------------------------------------------------
m3uaVersion OBJECT-TYPE m3uaVersion OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the current version of the M3UA." "Identifies the current version of the M3UA."
::= { m3uaConfig 1 } ::= { m3uaConfig 1 }
m3uaProcType OBJECT-TYPE m3uaProcType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
sgp(1), -- Signalling Gateway Process sgp(1), -- Signaling Gateway Process
asp(2), -- Application Server Process asp(2), -- Application Server Process
ipsp(3) -- IP Server Process ipsp(3) -- IP Server Process
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the type of the process where the "This variable indicates the type of the process where the
M3UA layer is located." M3UA layer is located."
::= { m3uaConfig 2 } ::= { m3uaConfig 2 }
m3uaLocalPort OBJECT-TYPE m3uaLocalPort OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the port of the M3UA service. "Identifies the port of the M3UA service. Well-known Port for
Well-Known Port for M3UA is 2904." M3UA is 2905."
DEFVAL {2905} -- well-known port assigned by IANA to M3UA
::= { m3uaConfig 3 } ::= { m3uaConfig 3 }
m3uaTrValue OBJECT-TYPE m3uaTrInitValue OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Initial value of the Failover timer Tr. Recommended "Initial value of the Failover timer Tr. Tr set with value 0
value is 3000 milliseconds. Tr set with value 0 disables disables buffering."
buffering." DEFVAL {3000} -- 3000 milliseconds itÆs the recommended value
::= { m3uaConfig 4 } ::= { m3uaConfig 4 }
m3uaTPaudValue OBJECT-TYPE m3uaTPAudInitValue OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Initial value of the Periodic Audit timer TrPaud. "Initial value of the Periodic Audit timer TPAud."
Recommended value is 5000 milliseconds." DEFVAL {5000} -- 5000 milliseconds itÆs the recommended value
::= { m3uaConfig 5 } ::= { m3uaConfig 5 }
m3uaHeartBeat OBJECT-TYPE m3uaHeartBeat OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TruthValue
on(0), -- Heartbeat is enabled. MAX-ACCESS read-only
off(1) -- Heartbeat is disabled. No BEAT msgs
-- sent but BEAT messages received are
-- responded.
}
MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Activates or deactivates the heartbeat procedure at M3UA "Activates or deactivates the heartbeat procedure at M3UA
level." level.
When the object is set to 'true' (1), the heartbeat procedure
is enabled.
When the object is set to 'false' (2), Heartbeat is disabled.
No BEAT messages are sent but the BEAT messages received are
responded."
::= { m3uaConfig 6 } ::= { m3uaConfig 6 }
m3uaTBeatValue OBJECT-TYPE m3uaTBeatInitValue OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Initial value of the HeartBeat timer TBeat. Recommended "Initial value of the HeartBeat timer TBeat."
value is 1000 milliseconds." DEFVAL {1000} -- 1000 milliseconds is the recommended value
::= { m3uaConfig 7 } ::= { m3uaConfig 7 }
m3uaTAckValue OBJECT-TYPE m3uaTAckInitValue OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Initial value of the Retransmision timer TAck. Recommended "Initial value of the Retransmission timer TAck."
value is 2000 milliseconds." DEFVAL {2000} -- 2000 milliseconds is the recommended value
::= { m3uaConfig 8 } ::= { m3uaConfig 8 }
m3uaSpLshMethod OBJECT-TYPE m3uaSpLshMethod OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), -- Random other(1), -- Other method not listed below
sls(1), -- Basing on SLS sls(2), -- Basing on SLS
cic(2), -- Basing on CIC cic(3), -- Basing on CIC
ssn(3), -- Basing on SSN ssn(4) -- Basing on SSN
dpg(4), -- Basing on DPC
other(5) -- Other method
} }
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the method to be used when the "This variable indicates the method to be used when the
load must be shared between several ACTIVE Signaling load must be shared between several ACTIVE Signaling
Processes." Processes."
::= { m3uaConfig 9 } ::= { m3uaConfig 9 }
m3uaStreamLshMethod OBJECT-TYPE m3uaStreamLshMethod OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), -- Random other(1), -- Other method not listed below
sls(1), -- Basing on SLS sls(2), -- Basing on SLS
cic(2), -- Basing on CIC cic(2), -- Basing on CIC
ssn(3), -- Basing on SSN ssn(2) -- Basing on SSN
dpc(4), -- Basing on DPC
other(5) -- Other method
} }
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the method to be used when the "This variable indicates the method to be used when the
load must be shared between several streams within the same load must be shared between several streams within the same
SCTP Association." SCTP Association."
::= { m3uaConfig 10 } ::= { m3uaConfig 10 }
m3uaFailOverBuffSize OBJECT-TYPE m3uaFailOverBuffSize OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write UNITS "bytes"
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Size of the failover retransmision buffer. Recommended "Size of the failover retransmission buffer. Recommended
value is 64 Kbytes. Only valid if failover buffer value is 64 Kbytes. Only valid if failover buffer
option has been set to ON." option has been set to ON."
DEFVAL {65535} -- Recommended value is 64 Kbytes
::= { m3uaConfig 11 } ::= { m3uaConfig 11 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES-STATISTICS -- ATTRIBUTES-STATISTICS
----------------------------------------------------------------------- -----------------------------------------------------------------------
m3uaRoutingFailures OBJECT-TYPE m3uaRoutingFailures OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 18, line 33 skipping to change at page 24, line 15
m3uaRoutingFailures OBJECT-TYPE m3uaRoutingFailures OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times a routing operation against Routing "The number of times a routing operation against Routing
Table fails. No final SCTP Association ID is obtained from Table fails. No final SCTP Association ID is obtained from
the routing operation. That is the reason why this is a the routing operation. That is the reason why this is a
general statistic instead a per association statistic." general statistic instead a per association statistic."
::= { m3uaStatistics 1 } ::= { m3uaStatistics 1 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE LOGICAL APPLICATION TABLE -- ASP TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG -- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- DESTINATION TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- The Logical Applications table contains information about each -- The Destination Table contains information about each destination
-- Application for which one or more routing keys can exist in the -- that can be reached from the ASP where it is located.
-- routing table. Log. Applications are: Signaling Gateways (SGs),
-- Application Servers (ASs).
m3uaAppTable OBJECT-TYPE m3uaAspDestTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAppEntry SYNTAX SEQUENCE OF M3uaAspDestEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing Log. Application-specific information." "A table containing per SS7 destination information. The
::= { m3uaLAppConfig 1 } state of destinations through each SG can be fetched per AS."
m3uaAppEntry OBJECT-TYPE ::= { m3uaAspCfg 1 }
SYNTAX M3uaAppEntry
m3uaAspDestEntry OBJECT-TYPE
SYNTAX M3uaAspDestEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General common variables for the Log. App." "Destination parameters and relation with SGs and ASes."
INDEX { m3uaAppId } INDEX { m3uaAspDestNa, m3uaAspDestDpc, m3uaAspDestSgId,
::= { m3uaAppTable 1 } m3uaAspDestAsId }
M3uaAppEntry ::= SEQUENCE { ::= { m3uaAspDestTable 1 }
m3uaAppId Unsigned32,
m3uaAppType INTEGER, M3uaAspDestEntry ::= SEQUENCE {
m3uaAppState INTEGER, m3uaAspDestNa Unsigned32,
m3uaAppTrafficMode INTEGER, m3uaAspDestDpc Unsigned32,
m3uaAppRowStatus RowStatus m3uaAspDestSgId Unsigned32,
m3uaAspDestAsId Unsigned32,
m3uaAspDestState INTEGER
} }
m3uaAppId OBJECT-TYPE m3uaAspDestNa OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Application Identification Value." "Network Appearance. When this parameter is not used, Network
::= { m3uaAppEntry 1 } Indicator parameter, as included in the MTP3 message, will be
filled in."
m3uaAppType OBJECT-TYPE ::= { m3uaAspDestEntry 1 }
SYNTAX INTEGER {
sg(1), m3uaAspDestDpc OBJECT-TYPE
as(2) SYNTAX Unsigned32
} MAX-ACCESS not-accessible
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Logical Application Type: "Destination Point Code located in the SS7 network. It is the
SG: Signaling Gateway. final destination for the message generated in the ASP which
AS: Application Server. should reach the SS7 node traversing a Signaling Gateway."
"
::= { m3uaAppEntry 2 }
m3uaAppState OBJECT-TYPE ::= { m3uaAspDestEntry 2 }
SYNTAX INTEGER {
active(1), m3uaAspDestSgId OBJECT-TYPE
inactive(2), SYNTAX Unsigned32
down(3), MAX-ACCESS not-accessible
pending(4)
}
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current Logical Application State. Based on the state "Signaling Gateway (SG) Identifier. It represents an SG that
of the Signaling Processes which serve it." is in the way to the final DPC located in the SS7 network."
::= { m3uaAppEntry 3 }
m3uaAppTrafficMode OBJECT-TYPE ::= { m3uaAspDestEntry 3 }
m3uaAspDestAsId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Application Server (AS) Identifier. It represents an AS that
is being served by the ASP. A specific destination address
could be reachable or not from the ASP, depending on each AS
this ASP is serving to."
::= { m3uaAspDestEntry 4 }
m3uaAspDestState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
override(1), unknown (1),
loadshare(2), available(2),
broadcast(3) unavailable(3),
congested(4),
restricted(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Current Logical Application traffic handling mode." "Destination reachability status. It is the status of the
::= { m3uaAppEntry 4 } Signaling Point that is the final destination of a message
within the SS7 network when the message travels through the
Signaling Gateway (SG) identified by the m3uaAspDestSgId
object."
m3uaAppRowStatus OBJECT-TYPE ::= { m3uaAspDestEntry 5 }
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 -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE LOGICAL APPLICATION STATISTICS TABLE -- ASP TABLES
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- SIGNALING GATEWAY PROCESS TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
m3uaAppStatTable OBJECT-TYPE -- The SGP Table contains information about the SGPs per SG that can be
SYNTAX SEQUENCE OF M3uaAppStatEntry -- reached from this ASP. It shows the state of each AS at each remote
-- SGP.
m3uaAspSgpTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAspSgpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing Log. Application statistic information." "A table containing SGP status information for each SG that
::= { m3uaLAppStatistics 1 } is communicating with an AS served by this ASP."
m3uaAppStatEntry OBJECT-TYPE ::= { m3uaAspCfg 2 }
SYNTAX M3uaAppStatEntry
m3uaAspSgpEntry OBJECT-TYPE
SYNTAX M3uaAspSgpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General common variables for the Log. App." " SGP related parameters. There are SGPs available depending
INDEX { m3uaAppId } -- SHARED INDEX on the AS the ASP is serving and the SG it wants to send the
::= { m3uaAppStatTable 1 } messages. It may be one or more SGP for each AS-SG pair."
INDEX { m3uaAspSgpAsId, m3uaAspSgpSgId, m3uaAspSgpId }
M3uaAppStatEntry ::= SEQUENCE { ::= { m3uaAspSgpTable 1 }
m3uaAppUnreachable Counter32 }
m3uaAppUnreachable OBJECT-TYPE M3uaAspSgpEntry ::= SEQUENCE {
SYNTAX Counter32 m3uaAspSgpAsId Unsigned32,
m3uaAspSgpSgId Unsigned32,
m3uaAspSgpId Unsigned32,
m3uaAspSgpState INTEGER
}
m3uaAspSgpAsId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Application Server (AS) Identifier. It represents an AS that
is being served by the ASP."
::= { m3uaAspSgpEntry 1 }
m3uaAspSgpSgId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Signaling Gateway (SG) Identifier. It represents an SG
composed of the SGPs identified by m3uaAspSgpId."
::= { m3uaAspSgpEntry 2 }
m3uaAspSgpId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Signaling Gateway Process (SGP) Identifier. It represents an
SGP that is serving the Signaling Gateway (SG) identified by
the m3uaAspSgpSgId object."
::= { m3uaAspSgpEntry 3 }
m3uaAspSgpState OBJECT-TYPE
SYNTAX INTEGER {
unknown (1),
active(2),
inactive(3),
down(4)
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of times that the Application is unreachable "AS state through each SGP in the SG."
through any of the Signaling Processes that are serving
it." ::= { m3uaAspSgpEntry 4 }
::= { m3uaAppStatEntry 1 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE SIGNALING PROCESS ENDPOINT TABLE -- ASP TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG -- CONFIG
----------------------------------------------------------------------- -----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ASSOCIATION TABLE
-----------------------------------------------------------------------
-- The Association Table contains information about the association
-- towards each SGP that can be reached from this ASP when serving to any
-- of its ASes. Limits of the streams that are data for the lower layer
-- (SCTP) are also included.
-- Defines data related to a Signaling Process Endpoint. m3uaAspAssocTable OBJECT-TYPE
-- A SP Endpoint identifies a peer node were a SGP, ASP or IPSP are SYNTAX SEQUENCE OF M3uaAspAssocEntry
-- 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 MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing Signaling Process Endpoint-specific "A table containing SCTP association information information
information." for each SGP that is communicating with this ASP."
::= { m3uaSpEpConfig 1 }
m3uaSpEpEntry OBJECT-TYPE ::= { m3uaAspCfg 3 }
SYNTAX M3uaSpEpEntry
m3uaAspAssocEntry OBJECT-TYPE
SYNTAX M3uaAspAssocEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General common variables for the Signaling Process " SCTP related parameters. There will be one association to
Endpoint." each of the SGPs that this ASP has to talk to."
INDEX { m3uaSpEpId } INDEX { m3uaAspAssocSgpId }
::= { m3uaSpEpTable 1 }
M3uaSpEpEntry ::= SEQUENCE { ::= { m3uaAspAssocTable 1 }
m3uaSpEpId Unsigned32,
m3uaSpEpAssocId Unsigned32,
m3uaSpEpAssocRemHostName OCTET STRING,
m3uaSpEpAssocRemPort Unsigned32,
m3uaSpEpAssocReqOutStreams Unsigned32,
m3uaSpEpAssocOutStreams Unsigned32,
m3uaSpEpAssocIncStreams Unsigned32,
m3uaSpEpAssocState INTEGER,
m3uaSpEpRowStatus RowStatus
M3uaAspAssocEntry ::= SEQUENCE {
m3uaAspAssocSgpId Unsigned32,
m3uaAspAssocId Unsigned32,
m3uaAspAssocMinOutStreams Unsigned32,
m3uaAspAssocMaxInStreams Unsigned32
} }
m3uaSpEpId OBJECT-TYPE m3uaAspAssocSgpId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signaling Process Endpoint Identification Value." "Signaling Gateway Process (SGP) Identifier. It represents an
::= { m3uaSpEpEntry 1 } SGP."
m3uaSpEpAssocId OBJECT-TYPE ::= { m3uaAspAssocEntry 1 }
m3uaAspAssocId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Association Identification. Value identifying the "Association Identification. It is the value that identifies
association for that endpoint. This value is extracted from the association that is established between this ASP and the
the SCTP association Id value returned by SCTP when the SGP represented by m3uaAspAssocSgpId. This value is extracted
association is established to that endpoint." from the SCTP association Id value returned by SCTP when the
::= { m3uaSpEpEntry 2 } association is established to that endpoint. It is the link
to get the transport values from the SCTP MIB."
m3uaSpEpAssocRemHostName OBJECT-TYPE ::= { m3uaAspAssocEntry 2 }
SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-create m3uaAspAssocMinOutStreams OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Peer's DNS name. "If the SCTP association is initiated from this ASP,
If no DNS domain name was received at init time from the this will be the minimum number of outgoing streams that is
peer, this entry will be meaningless, therefore it will requested to the remote peer at association start up."
store a NULL value.
Otherwise, the remote host name received at init time will
be stored."
::= { m3uaSpEpEntry 3 }
m3uaSpEpAssocRemPort OBJECT-TYPE ::= { m3uaAspAssocEntry 3 }
m3uaAspAssocMaxInStreams OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"M3UA port number to connect to remote Endpoint." "It is the maximum number of input streams that this
::= { m3uaSpEpEntry 4 } application can support. It is used during the Association
establishment phase."
m3uaSpEpAssocReqOutStreams OBJECT-TYPE ::= { m3uaAspAssocEntry 4 }
SYNTAX Unsigned32
MAX-ACCESS read-create -----------------------------------------------------------------------
-- M3UA TABLES
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ASP TABLES
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ROUTING CONTEXT TABLE
-----------------------------------------------------------------------
-- The Routing Context (RC) Table contains information about the
-- association towards each SGP that can be reached from this ASP when
-- serving to any of its ASes.
m3uaAspRcTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAspAssocEntry
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the SCTP association is initiated from the local peer, "A table containing the Routing Context (RC) values for each
this will be the number of outgoing streams that will be SGP-AS relationship. As indicated in the M3UA RFC, the RC
requested to the remote peer at association start up." values are SGP scoped."
::= { m3uaSpEpEntry 5 }
m3uaSpEpAssocOutStreams OBJECT-TYPE ::= { m3uaAspCfg 4 }
SYNTAX Unsigned32
MAX-ACCESS read-only m3uaAspRcEntry OBJECT-TYPE
SYNTAX M3uaAspRcEntry
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"outgoing Streams according to the negotiation at " RC value for each AS as assigned by the SGP."
association start up. This parameter has to be read-only by INDEX { m3uaAspRcSgpId, m3uaAspRcAsId }
the manager."
::= { m3uaSpEpEntry 6 } ::= { m3uaAspRcTable 1 }
m3uaSpEpAssocIncStreams OBJECT-TYPE M3uaAspRcEntry ::= SEQUENCE {
m3uaAspRcSgpId Unsigned32,
m3uaAspRcAsId Unsigned32,
m3uaAspRcValue Unsigned32
}
m3uaAspRcSgpId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Incoming Streams according to the negotiation at assoc. "Signaling Gateway Process (SGP) Identifier. It represents an
start up. This parameter has to be read-only by the SGP that communicates with this ASP."
manager."
::= { m3uaSpEpEntry 7 } ::= { m3uaAspRcEntry 1 }
m3uaSpEpAssocState OBJECT-TYPE
SYNTAX INTEGER { m3uaAspRcAsId OBJECT-TYPE
closed(1), SYNTAX Unsigned32
established(2) MAX-ACCESS not-accessible
}
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of this SCTP association." "Application Server (AS) Identifier. It represents an AS that
::= { m3uaSpEpEntry 8 } is being served by the ASP."
m3uaSpEpRowStatus OBJECT-TYPE ::= { m3uaAspRcEntry 2 }
SYNTAX RowStatus
MAX-ACCESS read-create m3uaAspRcValue OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "This is the value for the Routing Context that is share
and deleted by management operation using the RowStatus between the SGP identified by communicatinm3uaAspRcSgpId
convention." object and this ASP when serving to AS identified by the
::= { m3uaSpEpEntry 9 } m3uaAspRcAsId object."
::= { m3uaAspRcEntry 3 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES-STATISTICS -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE SP ENDPOINT STATISTICS TABLE -- ASP TABLES
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- STATISTICS
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ASP STATISTICS TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- Defines statistics related to a Signaling Process Endpoint. -- It defines statistics specific to an Application Server Process.
-- Statistics applicable to SGP, ASP and IPSP are covered in the generic
-- This table exists with any Proccess Type. -- statistics table.
-- The table contains statistics data related to the M3UA messaging -- The table contains statistics data related to the M3UA messages
-- exchanged through that association between the Signaling Processes -- exchanged through each association at the ASP.
-- that hold the association.
m3uaSpEpStatTable OBJECT-TYPE m3uaAspStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaSpEpStatEntry SYNTAX SEQUENCE OF M3uaAspStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing Signaling Process Endpoint-specific "A table containing per association statistics."
information." ::= { m3uaAspStat 1 }
::= { m3uaSpEpStatistics 1 }
m3uaSpEpStatEntry OBJECT-TYPE m3uaAspStatEntry OBJECT-TYPE
SYNTAX M3uaSpEpStatEntry SYNTAX M3uaAspStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General common variables for the SP Endpoint." "It counts all the messages received and sent through a
INDEX { m3uaSpEpId } -- shared index specific association."
::= { m3uaSpEpStatTable 1 } INDEX { m3uaAspStatAssocId }
M3uaSpEpStatEntry ::= SEQUENCE { ::= { m3uaAspStatTable 1 }
m3uaSpEpAssocDataOut Counter32,
m3uaSpEpAssocDataIn Counter32, M3uaAspStatEntry ::= SEQUENCE {
m3uaSpEpAssocAspupOut Counter32, m3uaAspStatAssocId Unsigned32,
m3uaSpEpAssocAspupAckOut Counter32, m3uaAspStatAspupOut Counter32,
m3uaSpEpAssocAspacOut Counter32, m3uaAspStatAspacOut Counter32,
m3uaSpEpAssocAspacAckOut Counter32, m3uaAspStatAspdnOut Counter32,
m3uaSpEpAssocAspdnOut Counter32, m3uaAspStatAspiaOut Counter32,
m3uaSpEpAssocAspdnAckOut Counter32, m3uaAspStatAspupAckIn Counter32,
m3uaSpEpAssocAspiaOut Counter32, m3uaAspStatAspacAckIn Counter32,
m3uaSpEpAssocAspiaAckOut Counter32, m3uaAspStatAspdnAckIn Counter32,
m3uaSpEpAssocAspupIn Counter32, m3uaAspStatAspiaAckIn Counter32,
m3uaSpEpAssocAspupAckIn Counter32, m3uaAspStatNotifyIn Counter32,
m3uaSpEpAssocAspacIn Counter32, m3uaAspStatDaudOut Counter32,
m3uaSpEpAssocAspacAckIn Counter32, m3uaAspStatDunaIn Counter32,
m3uaSpEpAssocAspdnIn Counter32, m3uaAspStatDavaIn Counter32,
m3uaSpEpAssocAspdnAckIn Counter32, m3uaAspStatDupuIn 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 -- Association Statistics
-- DATA Statistics per Association -- ASPM 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 m3uaAspStatAssocId OBJECT-TYPE
SYNTAX Counter32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of DATA messages received through the association." "Association Identification. It is the value that identifies
::= { m3uaSpEpStatEntry 2 } the association that is established between this ASP and the
SGP represented by m3uaAspAssocSgpId. This value is extracted
-- End of DATA Statistics per Association from the SCTP association Id value returned by SCTP when the
association is established to that endpoint. It is the link
-- ASPM Statistics per Association to get the transport values from the SCTP MIB."
m3uaSpEpAssocAspupOut OBJECT-TYPE ::= { m3uaAspStatEntry 1 }
m3uaAspStatAspupOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPUP messages sent through the association." "Number of ASPUP messages sent through the association."
::= { m3uaSpEpStatEntry 3 }
m3uaSpEpAssocAspupAckOut OBJECT-TYPE ::= { m3uaAspStatEntry 2 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPUP ACK messages sent through the
association."
::= { m3uaSpEpStatEntry 4 }
m3uaSpEpAssocAspacOut OBJECT-TYPE m3uaAspStatAspacOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPAC messages sent through the association." "Number of ASPAC messages sent through the association."
::= { m3uaSpEpStatEntry 5 }
m3uaSpEpAssocAspacAckOut OBJECT-TYPE ::= { m3uaAspStatEntry 3 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPAC ACK messages sent through the
association."
::= { m3uaSpEpStatEntry 6 }
m3uaSpEpAssocAspdnOut OBJECT-TYPE m3uaAspStatAspdnOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPDN messages sent through the association." "Number of ASPDN messages sent through the association."
::= { m3uaSpEpStatEntry 7 }
m3uaSpEpAssocAspdnAckOut OBJECT-TYPE ::= { m3uaAspStatEntry 4 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPDN ACK messages sent through the
association."
::= { m3uaSpEpStatEntry 8 }
m3uaSpEpAssocAspiaOut OBJECT-TYPE m3uaAspStatAspiaOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPIA messages sent through the association." "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 ::= { m3uaAspStatEntry 5 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPUP messages received through the
association."
::= { m3uaSpEpStatEntry 11 }
m3uaSpEpAssocAspupAckIn OBJECT-TYPE m3uaAspStatAspupAckIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPUP ACK messages received through the "Number of ASPUP ACK messages received through the
association." association."
::= { m3uaSpEpStatEntry 12 }
m3uaSpEpAssocAspacIn OBJECT-TYPE ::= { m3uaAspStatEntry 6 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPAC messages received through the
association."
::= { m3uaSpEpStatEntry 13 }
m3uaSpEpAssocAspacAckIn OBJECT-TYPE m3uaAspStatAspacAckIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPAC ACK messages received through the "Number of ASPAC ACK messages received through the
association." association."
::= { m3uaSpEpStatEntry 14 }
m3uaSpEpAssocAspdnIn OBJECT-TYPE ::= { m3uaAspStatEntry 7 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPDN messages received through the
association."
::= { m3uaSpEpStatEntry 15 }
m3uaSpEpAssocAspdnAckIn OBJECT-TYPE m3uaAspStatAspdnAckIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPDN ACK messages received through the "Number of ASPDN ACK messages received through the
association." association."
::= { m3uaSpEpStatEntry 16 }
m3uaSpEpAssocAspiaIn OBJECT-TYPE ::= { m3uaAspStatEntry 8 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPIA messages received through the
association."
::= { m3uaSpEpStatEntry 17 }
m3uaSpEpAssocAspiaAckIn OBJECT-TYPE m3uaAspStatAspiaAckIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of ASPIA ACK messages received through the "Number of ASPIA ACK messages received through the
association." association."
::= { m3uaSpEpStatEntry 18 }
-- End of ASPM Statistics per Association ::= { m3uaAspStatEntry 9 }
-- MGMT Statistics per Association
m3uaSpEpAssocNotifyOut OBJECT-TYPE -- End of ASPM Statistics per Association
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of NOTIFY messages sent through the association."
::= { m3uaSpEpStatEntry 19 }
m3uaSpEpAssocErrorOut OBJECT-TYPE -- MGMT Statistics per Association
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ERROR messages sent through the association."
::= { m3uaSpEpStatEntry 20 }
m3uaSpEpAssocNotifyIn OBJECT-TYPE m3uaAspStatNotifyIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of NOTIFY messages received through the "Number of NOTIFY messages received through the
association." association."
::= { m3uaSpEpStatEntry 21 }
m3uaSpEpAssocErrorIn OBJECT-TYPE ::= { m3uaAspStatEntry 10 }
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 -- End of MGMT Statistics per Association
-- SSNM Statistics per Association -- SSNM Statistics per Association
m3uaAspStatDaudOut OBJECT-TYPE
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
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 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of DAUD messages sent through the association." "Number of DAUD messages sent through the association."
::= { m3uaSpEpStatEntry 27 }
m3uaSpEpAssocDunaIn OBJECT-TYPE ::= { m3uaAspStatEntry 11 }
m3uaAspStatDunaIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of DUNA messages received through the association." "Number of DUNA messages received through the association."
::= { m3uaSpEpStatEntry 28 }
m3uaSpEpAssocDavaIn OBJECT-TYPE ::= { m3uaAspStatEntry 12 }
m3uaAspStatDavaIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of DAVA messages received through the association." "Number of DAVA messages received through the association."
::= { m3uaSpEpStatEntry 29 }
m3uaSpEpAssocSconIn OBJECT-TYPE ::= { m3uaAspStatEntry 13 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of SCON messages received through the association."
::= { m3uaSpEpStatEntry 30 }
m3uaSpEpAssocDupuIn OBJECT-TYPE m3uaAspStatDupuIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of DUPU messages received through the association." "Number of DUPU messages received through the association."
::= { m3uaSpEpStatEntry 31 }
m3uaSpEpAssocDaudIn OBJECT-TYPE ::= { m3uaAspStatEntry 14 }
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 -- End of SSNM Statistics per Association
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE APPLICATION-ENDPOINT TABLE -- TABLES AT SGP/IPSP
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG -- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ROUTING TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- The Application-Endpoint table contains information about the -- The Routing table contains a list of routing keys, which translate to
-- Applications that the indexed Endpoint is serving and the state of -- an Application Server ID and a corresponding Routing Context.
-- that endpoint for that specific application.
-- Although an SP is identified with an unique SCTP endpoint, there may -- As a Routing Key may be composed of any combination of basic SS7
-- be more than one SP table entry indexed by the same SP Endpoint Id. -- routing elements, if an element is not included in the routing key,
-- The reason for this is that an Endpoint can be serving several -- a default value is assigned. This default value can continue being
-- Applications and thus maintains different states for each of them. -- considered as an indexing value itself.
-- An entry will then exist in the table per every combination of
-- m3uaSpEpId and m3uaAppId.
m3uaAppSpEpTable OBJECT-TYPE m3uaSgpIpspRtgTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAppSpEpEntry SYNTAX SEQUENCE OF M3uaSgpIpspRtgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Signaling Process Endpoint-specific
information."
::= { m3uaSpEpConfig 2 }
m3uaAppSpEpEntry OBJECT-TYPE
SYNTAX M3uaAppSpEpEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General common variables for the SP Endpoint." "A table containing Routing-specific information."
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 ::= { m3uaSgpIpspCfg 1 }
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 }
----------------------------------------------------------------------- m3uaSgpIpspRtgEntry OBJECT-TYPE
-- M3UA TABLES SYNTAX M3uaSgpIpspRtgEntry
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- LOCAL AND REMOTE IP ADDRESS TABLES
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- Remote Addresses Table
-----------------------------------------------------------------------
m3uaAssocLocalAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAssocLocalAddressEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Expanded table of m3uaAssocTable based on the AssocId "General common variables for a Routing Key."
index. INDEX { m3uaSgpIpspRtgNa,
It shows several interesting data for each local m3uaSgpIpspRtgDpc,
address which takes part in this association." m3uaSgpIpspRtgSi,
::= { m3uaSpEpConfig 3 } m3uaSgpIpspRtgOpc }
m3uaAssocLocalAddressEntry OBJECT-TYPE ::= { m3uaSgpIpspRtgTable 1 }
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 { M3uaSgpIpspRtgEntry ::= SEQUENCE {
m3uaAssocLocalAddressIPType InetAddressType, m3uaSgpIpspRtgNa Unsigned32,
m3uaAssocLocalAddressIP InetAddress, m3uaSgpIpspRtgDpc Unsigned32,
m3uaAssocLocalAddressRowStatus RowStatus m3uaSgpIpspRtgSi Unsigned32,
m3uaSgpIpspRtgOpc Unsigned32,
m3uaSgpIpspRtgAsId Unsigned32,
m3uaSgpIpspRtgRc Unsigned32
} }
m3uaAssocLocalAddressIPType OBJECT-TYPE m3uaSgpIpspRtgNa OBJECT-TYPE
SYNTAX InetAddressType SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of a local IP address available for this "Network Appearance for that routing key. A default value
association. will be assigned if not present in the Routing Key."
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].ö
::= { m3uaAssocLocalAddressEntry 1 }
m3uaAssocLocalAddressIP OBJECT-TYPE ::= { m3uaSgpIpspRtgEntry 1 }
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 m3uaSgpIpspRtgDpc OBJECT-TYPE
SYNTAX RowStatus SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "Destination Point Code for that routing key. A default
and deleted using the RowStatus convention. value will be assigned if not present in the Routing Key.
A row in this table will be created per local IP address to Range: 0 - 16777215."
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 }
----------------------------------------------------------------------- ::= { m3uaSgpIpspRtgEntry 2 }
-- Remote Addresses Table
-----------------------------------------------------------------------
m3uaAssocRemAddressTable OBJECT-TYPE m3uaSgpIpspRtgSi OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAssocRemAddressEntry SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Expanded table of m3uaAssocTable based on the AssocId "Service Indicator for that routing key. A default value
index. will be assigned if not present in the Routing Key.
It shows several interesting data for each remote peer IP Range: 2 - 10."
address which is used in this association."
::= { m3uaSpEpConfig 4 }
m3uaAssocRemAddressEntry OBJECT-TYPE ::= { m3uaSgpIpspRtgEntry 3 }
SYNTAX M3uaAssocRemAddressEntry
m3uaSgpIpspRtgOpc OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about the remote IP address most important "Originating Point Code for that routing key. A default
variables" value will be assigned if not present in the Routing Key.
INDEX { m3uaSpEpId, -- shared index Range: 0 to 16777215."
m3uaAssocRemAddressIPType,
m3uaAssocRemAddressIP }
::= { m3uaAssocRemAddressTable 1 }
M3uaAssocRemAddressEntry ::= SEQUENCE { ::= { m3uaSgpIpspRtgEntry 4 }
m3uaAssocRemAddressIPType InetAddressType,
m3uaAssocRemAddressIP InetAddress,
m3uaAssocRemAddressRowStatus RowStatus
}
m3uaAssocRemAddressIPType OBJECT-TYPE m3uaSgpIpspRtgAsId OBJECT-TYPE
SYNTAX InetAddressType SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of a local IP address available for this "Application Server Identification Value."
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 } ::= { m3uaSgpIpspRtgEntry 5 }
m3uaAssocRemAddressIP OBJECT-TYPE m3uaSgpIpspRtgRc OBJECT-TYPE
SYNTAX InetAddress SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of a local IP address available for this "Routing Context for that routing key."
association. An InetAddress value is always interpreted
within the context of an InetAddressType value."
::= { m3uaAssocRemAddressEntry 2 }
m3uaAssocRemAddressRowStatus OBJECT-TYPE ::= { m3uaSgpIpspRtgEntry 6 }
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 -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE ROUTING TABLE -- TABLES AT SGP/IPSP
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG -- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- APPLICATION SERVER (AS) TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- The Routing table contains a list of routing keys which translate to -- The Application Server table contains information on the state and
-- a Logical Application ID. As stated former in this document, -- traffic mode of each Application for which one or more routing keys
-- Application Servers and Signaling Gateways are Logical Applications. -- can exist in the Signalling Gateway or IPSP routing table.
-- 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 m3uaSgpIpspAsTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaRoutingEntry SYNTAX SEQUENCE OF M3uaSgpIpspAsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing Routing-specific information." "A table containing Application Server-specific information."
::= { m3uaRtConfig 1 }
m3uaRoutingEntry OBJECT-TYPE ::= { m3uaSgpIpspCfg 2 }
SYNTAX M3uaRoutingEntry
m3uaSgpIpspAsEntry OBJECT-TYPE
SYNTAX M3uaSgpIpspAsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General common variables for a Routing Key." "General common variables for the Application Server"
INDEX { m3uaRKId } INDEX { m3uaSgpIpspAsId }
::= { m3uaRoutingTable 1 } ::= { m3uaSgpIpspAsTable 1 }
M3uaRoutingEntry ::= SEQUENCE { M3uaSgpIpspAsEntry ::= SEQUENCE {
m3uaRKId Unsigned32, m3uaSgpIpspAsId Unsigned32,
m3uaRKDpc Unsigned32, m3uaSgpIpspAsState INTEGER,
m3uaRKNa Unsigned32, m3uaSgpIpspAsTmt INTEGER
m3uaPeerAppId Unsigned32,
m3uaPeerAppTrafficMode INTEGER,
m3uaRoutingRowStatus RowStatus
} }
m3uaRKId OBJECT-TYPE m3uaSgpIpspAsId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Local identifier for the routing key." "Application Server Identification Value."
::= { m3uaRoutingEntry 1 }
m3uaRKDpc OBJECT-TYPE ::= { m3uaSgpIpspAsEntry 1 }
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 m3uaSgpIpspAsState OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX INTEGER {
MAX-ACCESS read-create active(1),
STATUS current inactive(2),
DESCRIPTION down(3),
"Network Appearance for that routing key. A default value pending(4)
will be assigned if not present in the Routing Key." }
::= { m3uaRoutingEntry 3 } MAX-ACCESS read-only
m3uaPeerAppId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Peer Application Identification Value. It can identify "Current Application Server State. Based on the state
an Application Server or a Signaling Gateway." of the Application Server Processes which serve it."
::= { m3uaRoutingEntry 4 }
m3uaPeerAppTrafficMode OBJECT-TYPE ::= { m3uaSgpIpspAsEntry 2 }
m3uaSgpIpspAsTmt OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
override(1), override(1),
loadshare(2), loadshare(2),
broadcast(3) broadcast(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-only
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 STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "Current Application Server Traffic Mode Type."
and deleted by management operation using the RowStatus ::= { m3uaSgpIpspAsEntry 3 }
convention."
::= { m3uaRoutingEntry 6 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE SI TABLE -- TABLES AT SGP/IPSP
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG -- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- APPLICATION SERVER PROCESS TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- This table contains a list of SIs that identify the Services covered -- This table shows the State of the Application Server Process or IPSP
-- by that Routing Key. This list is related to and extends information -- for each Application Server, and the role of the ASP in the AS traffic
-- of every entry in Routing Table. -- distribution, according to each AS traffic mode.
m3uaRKSiTable OBJECT-TYPE m3uaSgpIpspAspTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaRKSiEntry SYNTAX SEQUENCE OF M3uaSgpIpspAspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of SIs that identify the "A table containing Application Server Process-specific
services covered by that Routing Key." information."
::= { m3uaRtConfig 2 }
m3uaRKSiEntry OBJECT-TYPE ::= { m3uaSgpIpspCfg 3 }
SYNTAX M3uaRKSiEntry
m3uaSgpIpspAspEntry OBJECT-TYPE
SYNTAX M3uaSgpIpspAspEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "General common variables for the Application Server
INDEX { m3uaRKId } -- shared index Process."
::= { m3uaRKSiTable 1 } INDEX { m3uaSgpIpspAspAsId,
m3uaSgpIpspAspId }
M3uaRKSiEntry ::= SEQUENCE { ::= { m3uaSgpIpspAspTable 1 }
m3uaRKSi Unsigned32,
m3uaRKSiRowStatus RowStatus M3uaSgpIpspAspEntry ::= SEQUENCE {
m3uaSgpIpspAspAsId Unsigned32,
m3uaSgpIpspAspId Unsigned32,
m3uaSgpIpspAspState INTEGER,
m3uaSgpIpspAspRole INTEGER
} }
m3uaSgpIpspAspAsId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Application Server Identification Value."
m3uaRKSi OBJECT-TYPE ::= { m3uaSgpIpspAspEntry 1 }
m3uaSgpIpspAspId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Service Indicator for that routing key. A default value " Application Server Process Identification Value."
will be assigned if not present in the Routing Key.
Range: 2 - 10."
::= { m3uaRKSiEntry 1 }
m3uaRKSiRowStatus OBJECT-TYPE ::= { m3uaSgpIpspAspEntry 2 }
SYNTAX RowStatus
MAX-ACCESS read-create m3uaSgpIpspAspState OBJECT-TYPE
SYNTAX INTEGER {
aspDown(1),
aspUp(2),
aspActive(3)
}
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "The state of this Application Server Process for a
and deleted by management operation using the RowStatus given AS."
convention."
::= { m3uaRKSiEntry 2 } ::= { m3uaSgpIpspAspEntry 3 }
m3uaSgpIpspAspRole OBJECT-TYPE
SYNTAX INTEGER {
primary(1),
backup(2),
loadsharing(3),
broadcast (4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The role of this Application Server Process within the
traffic mode for each AS."
::= { m3uaSgpIpspAspEntry 4 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE OPC TABLE -- TABLES AT SGP/IPSP
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG -- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- APPLICATION SERVER PROCESS (ASP) ASSOCIATION TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- This table contains a list of OPCs that identify the Originating -- Defines data related to the SCTP Association for an Application Server
-- Node in the SS7 Network. This list is related with and extends -- Process or IPSP.
-- information of every entry in Routing Table. -- Further Association data can be obtained from the SCTP MIB.
m3uaRKOpcTable OBJECT-TYPE m3uaSgpIpspAssocTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaRKOpcEntry SYNTAX SEQUENCE OF M3uaSgpIpspAssocEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of Point Codes that identify "A table containing ASP/IPSP Association-specific
the Originating Node in the SS7 Network for a Routing information."
Key."
::= { m3uaRtConfig 3 }
m3uaRKOpcEntry OBJECT-TYPE ::= { m3uaSgpIpspCfg 4 }
SYNTAX M3uaRKOpcEntry
m3uaSgpIpspAssocEntry OBJECT-TYPE
SYNTAX M3uaSgpIpspAssocEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "General common variables for the Association for an
INDEX { m3uaRKId } -- shared index ASP."
::= { m3uaRKOpcTable 1 } INDEX { m3uaSgpIpspAssocAspId }
M3uaRKOpcEntry ::= SEQUENCE { ::= { m3uaSgpIpspAssocTable 1 }
m3uaRKOpc Unsigned32,
m3uaRKOpcRowStatus RowStatus
}
m3uaRKOpc OBJECT-TYPE M3uaSgpIpspAssocEntry ::= SEQUENCE {
m3uaSgpIpspAssocAspId Unsigned32,
m3uaSgpIpspAssocId Unsigned32,
m3uaSgpIpspAssocMinOutStreams Unsigned32,
m3uaSgpIpspAssocMaxInStreams Unsigned32
}
m3uaSgpIpspAssocAspId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Origination Point Code for that routing key. A default " Application Server Process Identification Value."
value will be assigned if not present in the Routing Key.
Range: 0 to 16777215."
::= { m3uaRKOpcEntry 1 }
m3uaRKOpcRowStatus OBJECT-TYPE ::= { m3uaSgpIpspAssocEntry 1 }
SYNTAX RowStatus
MAX-ACCESS read-create m3uaSgpIpspAssocId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "Association Identification. Value identifying the
and deleted by management operation using the RowStatus association for that ASP. This value is extracted from
convention." the SCTP association Id value returned by SCTP when the
association is established to that endpoint."
::= { m3uaRKOpcEntry 2 } ::= { m3uaSgpIpspAssocEntry 2 }
m3uaSgpIpspAssocMinOutStreams OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the SCTP association is initiated from this ASP,
this will be the minimum number of outgoing streams that is
requested to the remote peer at association start up."
::= { m3uaSgpIpspAssocEntry 3 }
m3uaSgpIpspAssocMaxInStreams OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"It is the maximum number of input streams that this
application can support. It is used during the Association
establishment phase."
::= { m3uaSgpIpspAssocEntry 4 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- THE CIC RANGE TABLE -- TABLES AT SGP/IPSP
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG -- STATISTICS
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- SGP / IPSP STATISTICS TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- This table contains a CIC Range for an OPC in the Routing Key -- It defines statistics specific to a Signaling Gateway Process or IP
-- This list is related with and extends information -- Signaling Process.
-- of every entry in Routing Table.
m3uaRKCicRangeTable OBJECT-TYPE -- Statistics applicable to SGP, ASP and IPSP are covered in the generic
SYNTAX SEQUENCE OF M3uaRKCicRangeEntry -- statistics table.
-- For the IPSP, the ASP Statistics table also applies.
-- The table contains statistics data related to the M3UA messages
-- exchanged through each association at the SGP or IPSP.
m3uaSgpIpspStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaSgpIpspStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of CIC Ranges for an OPC "A table containing per association statistics."
within the specific Routing Key."
::= { m3uaRtConfig 4 } ::= { m3uaSgpIpspStat 1 }
m3uaRKCicRangeEntry OBJECT-TYPE m3uaSgpIpspStatEntry OBJECT-TYPE
SYNTAX M3uaRKCicRangeEntry SYNTAX M3uaSgpIpspStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "It counts all the messages received and sent through a
INDEX { m3uaRKId, -- shared index specific association."
m3uaRKOpc } INDEX { m3uaSgpIpspStatAssocId }
::= { m3uaRKCicRangeTable 1 }
M3uaRKCicRangeEntry ::= SEQUENCE { ::= { m3uaSgpIpspStatTable 1 }
m3uaRKCicMin Unsigned32,
m3uaRKCicMax Unsigned32, M3uaSgpIpspStatEntry ::= SEQUENCE {
m3uaRKCicRowStatus RowStatus m3uaSgpIpspStatAssocId Unsigned32,
m3uaSgpIpspStatAspupAckOut Counter32,
m3uaSgpIpspStatAspacAckOut Counter32,
m3uaSgpIpspStatAspdnAckOut Counter32,
m3uaSgpIpspStatAspiaAckOut Counter32,
m3uaSgpIpspStatAspupIn Counter32,
m3uaSgpIpspStatAspacIn Counter32,
m3uaSgpIpspStatAspdnIn Counter32,
m3uaSgpIpspStatAspiaIn Counter32,
m3uaSgpIpspStatNotifyOut Counter32,
m3uaSgpIpspStatDunaOut Counter32,
m3uaSgpIpspStatDavaOut Counter32,
m3uaSgpIpspStatDupuOut Counter32,
m3uaSgpIpspStatDaudIn Counter32
} }
m3uaRKCicMin OBJECT-TYPE -- Association Statistics
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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 -- ASPM Statistics per Association
m3uaSgpIpspStatAssocId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum value of the Circuit Identification Code "Association Identification. It is the value that identifies
Range for that routing key. A default value will the association that is established between this SGP or IPSP
be assigned if not present in the Routing Key. and the remote ASP or IPSP. This value is extracted from the
Range: 0 to 65535." SCTP association Id value returned by SCTP when the
::= { m3uaRKCicRangeEntry 2 } association is established to that endpoint. It is the link
to get the transport values from the SCTP MIB."
m3uaRKCicRowStatus OBJECT-TYPE ::= { m3uaSgpIpspStatEntry 1 }
SYNTAX RowStatus
MAX-ACCESS read-create m3uaSgpIpspStatAspupAckOut OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "Number of ASPUP ACK messages sent through the association."
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 ::= { m3uaSgpIpspStatEntry 2 }
-- that apply to every Network Appearance.
m3uaNaTable OBJECT-TYPE m3uaSgpIpspStatAspacAckOut OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaNaEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing Network Appearance-specific information" "Number of ASPAC ACK messages sent through the association."
::= { m3uaNaConfig 1 } ::= { m3uaSgpIpspStatEntry 3 }
m3uaNaEntry OBJECT-TYPE m3uaSgpIpspStatAspdnAckOut OBJECT-TYPE
SYNTAX M3uaNaEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"General common variables for a Network Appearance." "Number of ASPDN ACK messages sent through the association."
INDEX { m3uaRKNa } -- shared index
::= { m3uaNaTable 1 }
M3uaNaEntry ::= SEQUENCE { ::= { m3uaSgpIpspStatEntry 4 }
m3uaNaNI Unsigned32,
m3uaNaMtp3ProtocolType INTEGER,
m3uaNaMtp3ProtocolVariant Unsigned32,
m3uaNaMtp3ProtocolVersion Unsigned32,
m3uaNaRowStatus RowStatus
}
m3uaNaNI OBJECT-TYPE m3uaSgpIpspStatAspiaAckOut OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the Network Indicator of the SG Node in the "Number of ASPIA ACK messages sent through the association."
SS7 Network."
::= { m3uaNaEntry 2 } ::= { m3uaSgpIpspStatEntry 5 }
m3uaNaMtp3ProtocolType OBJECT-TYPE m3uaSgpIpspStatAspupIn OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Counter32
itu(1), MAX-ACCESS read-only
ansi(2),
china(3),
ttc(4),
other(5)
}
MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MTP3 protocol type for this NA." "Number of ASPUP messages received through the association."
::= { m3uaNaEntry 4 } ::= { m3uaSgpIpspStatEntry 6 }
m3uaNaMtp3ProtocolVariant OBJECT-TYPE m3uaSgpIpspStatAspacIn OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MTP3 protocol variant for this NA." "Number of ASPAC messages received through the association."
::= { m3uaNaEntry 5 } ::= { m3uaSgpIpspStatEntry 7 }
m3uaNaMtp3ProtocolVersion OBJECT-TYPE m3uaSgpIpspStatAspdnIn OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The MTP3 protocol version for this NA." "Number of ASPDN messages received through the association."
::= { m3uaNaEntry 6 }
m3uaNaRowStatus OBJECT-TYPE ::= { m3uaSgpIpspStatEntry 8 }
SYNTAX RowStatus m3uaSgpIpspStatAspiaIn OBJECT-TYPE
MAX-ACCESS read-create SYNTAX Counter32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "Number of ASPIA messages received through the association."
and deleted by management operation using the RowStatus
convention."
::= { m3uaNaEntry 7 } ::= { m3uaSgpIpspStatEntry 9 }
----------------------------------------------------------------------- -- End of ASPM Statistics per Association
-- M3UA TABLES
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- THE POINT CODE TABLE
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ATTRIBUTES - CONFIG
-----------------------------------------------------------------------
-- The PC table contains a list of point codes that identify the SG -- MGMT Statistics per Association
-- 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 m3uaSgpIpspStatNotifyOut OBJECT-TYPE
-- Table. A SG with several Network Appearances may be connected to SYNTAX Counter32
-- different SS7 Networks and may be represented in each SS7 Network by MAX-ACCESS read-only
-- different Point Codes. STATUS current
DESCRIPTION
"Number of NOTIFY messages sent through the association."
::= { m3uaSgpIpspStatEntry 10 }
m3uaNaPcTable OBJECT-TYPE -- End of MGMT Statistics per Association
SYNTAX SEQUENCE OF M3uaNaPcEntry
MAX-ACCESS not-accessible -- SSNM Statistics per Association
m3uaSgpIpspStatDunaOut OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of Point Codes that identify "Number of DUNA messages sent through the association."
the SG Node in the SS7 Network for that Network App." ::= { m3uaSgpIpspStatEntry 11 }
::= { m3uaNaConfig 2 }
m3uaNaPcEntry OBJECT-TYPE m3uaSgpIpspStatDavaOut OBJECT-TYPE
SYNTAX M3uaNaPcEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "Number of DAVA messages sent through the association."
INDEX { m3uaRKNa, -- shared index
m3uaNaPC }
::= { m3uaNaPcTable 1 }
M3uaNaPcEntry ::= SEQUENCE { ::= { m3uaSgpIpspStatEntry 12 }
m3uaNaPC Unsigned32,
m3uaNaPcRowStatus RowStatus
}
m3uaNaPC OBJECT-TYPE m3uaSgpIpspStatDupuOut OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Value. Range: 0 to 16777215." "Number of DUPU messages sent through the association."
::= { m3uaSgpIpspStatEntry 13 }
::= { m3uaNaPcEntry 1 }
m3uaNaPcRowStatus OBJECT-TYPE m3uaSgpIpspStatDaudIn OBJECT-TYPE
SYNTAX RowStatus SYNTAX Counter32
MAX-ACCESS read-create MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An object that allows entries in this table to be created "Number of DAUD messages received through the association."
and deleted by management operation using the RowStatus ::= { m3uaSgpIpspStatEntry 14 }
convention."
::= { m3uaNaPcEntry 2 } -- End of SSNM Statistics per Association
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA LOOKUP REVERSE TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ENDPOINT BY ASSOCIATION -- GENERIC
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- CONFIG
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- NETWORK APPEARANCE TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- This table allows the obtention of the Remote Endpoint Local Id m3uaGenNaTable OBJECT-TYPE
-- for an specific association. SYNTAX SEQUENCE OF M3uaGenNaEntry
m3uaLookupSpEpbyAssocTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaLookupSpEpbyAssocEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of remote Endpoints defined "A table containing Network Appearance-specific information"
indexed by the Id of the association established to that ::= { m3uaGenCfg 1 }
Endpoint."
::= { m3uaLookup 1 } m3uaGenNaEntry OBJECT-TYPE
SYNTAX M3uaGenNaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for a Network Appearance."
INDEX { m3uaGenNaValue }
::= { m3uaGenNaTable 1 }
M3uaGenNaEntry ::= SEQUENCE {
m3uaGenNaValue Unsigned32,
m3uaGenNaNi Unsigned32,
m3uaGenNaMtp3ProtType INTEGER,
m3uaGenNaMtp3ProtVariant Unsigned32,
m3uaGenNaMtp3ProtVersion Unsigned32
}
m3uaLookupSpEpbyAssocEntry OBJECT-TYPE m3uaGenNaValue OBJECT-TYPE
SYNTAX M3uaLookupSpEpbyAssocEntry SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "Network Appearance Value."
INDEX { m3uaSpEpAssocId, -- shared index
m3uaLookupSpEpId } -- shared index
::= { m3uaLookupSpEpbyAssocTable 1 }
M3uaLookupSpEpbyAssocEntry ::= SEQUENCE { ::= { m3uaGenNaEntry 2 }
m3uaLookupSpEpId Unsigned32
}
m3uaLookupSpEpId OBJECT-TYPE m3uaGenNaNi OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signaling Process Endpoint Identification Value." "Identifies the Network Indicator of the SG Node in the
::= { m3uaLookupSpEpbyAssocEntry 1 } SS7 Network."
-----------------------------------------------------------------------
-- M3UA LOOKUP REVERSE TABLES
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- ROUTING KEYS BY APPLICATION ID
-----------------------------------------------------------------------
-- This table allows the obtention of the Routing Keys for an specific ::= { m3uaGenNaEntry 3 }
-- Application.
m3uaLookupRkbyAppTable OBJECT-TYPE m3uaGenNaMtp3ProtType OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaLookupRkbyAppEntry SYNTAX INTEGER {
MAX-ACCESS not-accessible itu(1),
ansi(2),
china(3),
ttc(4),
other(5)
}
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of Routing Keys defined "The MTP3 protocol type for this NA."
for an Application."
::= { m3uaLookup 2 } ::= { m3uaGenNaEntry 4 }
m3uaLookupRkbyAppEntry OBJECT-TYPE m3uaGenNaMtp3ProtVariant OBJECT-TYPE
SYNTAX M3uaLookupRkbyAppEntry SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "The MTP3 protocol variant for this NA."
INDEX { m3uaPeerAppId, -- shared index
m3uaLookupRKId } -- shared index
::= { m3uaLookupRkbyAppTable 1 }
M3uaLookupRkbyAppEntry ::= SEQUENCE { ::= { m3uaGenNaEntry 5 }
m3uaLookupRKId Unsigned32
}
m3uaLookupRKId OBJECT-TYPE m3uaGenNaMtp3ProtVersion OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Routing Key Identification Value." "The MTP3 protocol version for this NA."
::= { m3uaLookupRkbyAppEntry 1 }
::= { m3uaGenNaEntry 6 }
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- M3UA LOOKUP REVERSE TABLES -- M3UA TABLES
----------------------------------------------------------------------- -----------------------------------------------------------------------
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- ROUTING KEYS BY DPC-NA -- GENERIC
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- STATISTICS
-----------------------------------------------------------------------
-----------------------------------------------------------------------
-- GENERIC STATISTICS TABLE
----------------------------------------------------------------------- -----------------------------------------------------------------------
-- This table allows the obtention of the Routing Key for an specific -- Defines statistics common to Application Server Processes,
-- DPC-NA combination. -- Signaling Gateway Processes and IP Signaling Processes.
m3uaLookupRkbyDpcNaTable OBJECT-TYPE -- The table contains statistics data related to the M3UA messages
SYNTAX SEQUENCE OF M3uaLookupRkbyDpcNaEntry -- exchanged through each association at the Signaling Process.
m3uaGenStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaGenStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of Routing Keys defined "A table containing per association statistics."
for an Application." ::= { m3uaGenStat 1 }
m3uaGenStatEntry OBJECT-TYPE
::= { m3uaLookup 3 } SYNTAX M3uaGenStatEntry
m3uaLookupRkbyDpcNaEntry OBJECT-TYPE
SYNTAX M3uaLookupRkbyDpcNaEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "It counts all the messages received and sent through a
INDEX { m3uaRKDpc, -- shared index specific association."
m3uaRKNa, -- shared index INDEX { m3uaGenStatAssocId }
m3uaRKId } -- shared index ::= { m3uaGenStatTable 1 }
::= { m3uaLookupRkbyDpcNaTable 1 }
M3uaLookupRkbyDpcNaEntry ::= SEQUENCE { M3uaGenStatEntry ::= SEQUENCE {
m3uaLookupRKbyDpcNaId Unsigned32 m3uaGenStatAssocId Unsigned32,
m3uaGenStatDataOut Counter32,
m3uaGenStatDataIn Counter32,
m3uaGenStatErrorOut Counter32,
m3uaGenStatErrorIn Counter32,
m3uaGenStatSconOut Counter32,
m3uaGenStatSconIn Counter32
} }
m3uaLookupRKbyDpcNaId OBJECT-TYPE -- Association Statistics
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 -- DATA Statistics per Association
-- Application.
m3uaLookupSpEpbyAppTable OBJECT-TYPE m3uaGenStatAssocId OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaLookupSpEpbyAppEntry SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing the list of Endpoints Id serving "Association Identification. It is the value that identifies
an Application." the association that is established between an ASP and an SGP
or between 2 IPSPs. This value is extracted from the SCTP
::= { m3uaLookup 4 } association Id value returned by SCTP when the association is
established to that endpoint. It is the link to get the
transport values from the SCTP MIB."
::= { m3uaGenStatEntry 1 }
m3uaLookupSpEpbyAppEntry OBJECT-TYPE m3uaGenStatDataOut OBJECT-TYPE
SYNTAX M3uaLookupSpEpbyAppEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Point Code Entry." "Number of DATA messages sent through the association."
INDEX { m3uaAppId, -- shared index ::= { m3uaGenStatEntry 2 }
m3uaLookupSpEpbyAppId } -- shared index
::= { m3uaLookupSpEpbyAppTable 1 }
M3uaLookupSpEpbyAppEntry ::= SEQUENCE {
m3uaLookupSpEpbyAppId Unsigned32
}
m3uaLookupSpEpbyAppId OBJECT-TYPE m3uaGenStatDataIn OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signaling Process Endpoint Identification Value." "Number of DATA messages received through the association."
::= { m3uaLookupSpEpbyAppEntry 1 } ::= { m3uaGenStatEntry 3 }
-- 4.1 Conformance Information -- End of DATA Statistics per Association
m3uaGroups OBJECT IDENTIFIER ::= { m3uaConformance 1 } -- MGMT Statistics per Association
m3uaCompliances OBJECT IDENTIFIER ::= { m3uaConformance 2 }
-- 4.1.1 Compliance Statements m3uaGenStatErrorOut OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ERROR messages sent through the association."
::= { m3uaGenStatEntry 4 }
m3uaCompliance MODULE-COMPLIANCE m3uaGenStatErrorIn OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMPv3 entities which "Number of ERROR messages received through the association."
implement M3UA. ::= { m3uaGenStatEntry 5 }
The M3UA MIB specifies in this compliant implementation that -- End of MGMT Statistics per Association
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 -- SSNM Statistics per Association
MANDATORY-GROUPS { m3uaAttributesGroup,
m3uaLogAppAttributesTableGroup,
m3uaSpEpAttributesTableGroup,
m3uaAppSpEpAttributesTableGroup,
m3uaRoutingAttributesTableGroup,
m3uaRKSiAttributesTableGroup,
m3uaRKOpcAttributesTableGroup,
m3uaRKCicRangeAttribTableGroup,
m3uaNaAttributesTableGroup,
m3uaPcAttributesTableGroup,
m3uaLocAddrAttributesTableGroup,
m3uaRemAddrAttributesTableGroup
}
OBJECT m3uaAssocLocalAddressIPType m3uaGenStatSconOut OBJECT-TYPE
SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2) } SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION DESCRIPTION
"It is only required to have IPv4 and IPv6 addresses "Number of SCON messages sent through the association."
without zone indices. Unknown values must also be ::= { m3uaGenStatEntry 6 }
supported in case the IP address has an invalid/unknown
format."
OBJECT m3uaAssocRemAddressIPType m3uaGenStatSconIn OBJECT-TYPE
SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2) } SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION DESCRIPTION
"It is only required to have IPv4 and IPv6 addresses "Number of SCON messages received through the association."
without zone indices. Unknown values must also be ::= { m3uaGenStatEntry 7 }
supported in case the IP address has an invalid/unknown
format."
::= { m3uaCompliances 1 } -- End of SSNM Statistics per Association
-- 4.1 Conformance Information
-- 4.1.2 Units of conformance m3uaCompliances OBJECT IDENTIFIER ::= { m3uaConformance 1 }
m3uaGroups OBJECT IDENTIFIER ::= { m3uaConformance 2 }
-- 4.1.1 Units of conformance
m3uaAttributesGroup OBJECT-GROUP m3uaAttributesGroup OBJECT-GROUP
OBJECTS { m3uaVersion, OBJECTS { m3uaVersion,
m3uaProcType, m3uaProcType,
m3uaLocalPort, m3uaLocalPort,
m3uaTrValue, m3uaTrValue,
m3uaTBeatValue, m3uaTBeatValue,
m3uaTAckValue, m3uaTAckValue,
m3uaTPaudValue, m3uaTPaudValue,
m3uaHeartBeat, m3uaHeartBeat,
skipping to change at page 50, line 40 skipping to change at page 54, line 29
m3uaHeartBeat, m3uaHeartBeat,
m3uaSpLshMethod, m3uaSpLshMethod,
m3uaStreamLshMethod, m3uaStreamLshMethod,
m3uaFailOverBuffSize, m3uaFailOverBuffSize,
m3uaRoutingFailures m3uaRoutingFailures
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects providing for management of M3UA "The m3ua group of objects providing for management of M3UA
entities. Common parameters for the protocol." entities. Common parameters for the protocol."
::= { m3uaGroups 1 } ::= { m3uaGroups 1 }
m3uaLogAppAttributesTableGroup OBJECT-GROUP m3uaAspCfgGroup OBJECT-GROUP
OBJECTS { m3uaAppId,
m3uaAppType, OBJECTS { m3uaAspDestState,
m3uaAppState, m3uaAspSgpState,
m3uaAppTrafficMode, m3uaAspAssocId,
m3uaAppUnreachable m3uaAspAssocMinOutStreams,
m3uaAspAssocMaxInStreams,
m3uaAspRcValue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage ASs/SGs and IPSs." "The m3ua group of objects to describe configuration values
at the Application Server Process (ASP)."
::= { m3uaGroups 2 } ::= { m3uaGroups 2 }
m3uaSpEpAttributesTableGroup OBJECT-GROUP m3uaAspStatsGroup OBJECT-GROUP
OBJECTS { m3uaSpEpId, OBJECTS { m3uaAspStatAspupOut,
m3uaSpEpAssocId, m3uaAspStatAspacOut,
m3uaSpEpAssocRemHostName, m3uaAspStatAspdnOut,
m3uaSpEpAssocRemPort, m3uaAspStatAspiaOut,
m3uaSpEpAssocReqOutStreams, m3uaAspStatAspupAckIn,
m3uaSpEpAssocOutStreams, m3uaAspStatAspacAckIn,
m3uaSpEpAssocIncStreams, m3uaAspStatAspdnAckIn,
m3uaSpEpAssocState, m3uaAspStatAspiaAckIn,
m3uaSpEpAssocState, m3uaAspStatNotifyIn,
m3uaSpEpAssocDataOut, m3uaAspStatDaudOut,
m3uaSpEpAssocDataIn, m3uaAspStatDunaIn,
m3uaSpEpAssocAspupOut, m3uaAspStatDavaIn,
m3uaSpEpAssocAspupAckOut, m3uaAspStatDupuIn
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 STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage SP Endpoints." "The m3ua group of objects to count how the number of
messages received/send by an ASP. Most of these messages
applies to the M3UA client process and would also apply to an
IPSP acting as a client."
::= { m3uaGroups 3 } ::= { m3uaGroups 3 }
m3uaAppSpEpAttributesTableGroup OBJECT-GROUP m3uaSgpIpspCfgGroup OBJECT-GROUP
OBJECTS { m3uaAppSpEpState OBJECTS { m3uaSgpIpspRtgAsId,
m3uaSgpIpspRtgRc,
m3uaSgpIpspAsState,
m3uaSgpIpspAsTrafficMode,
m3uaSgpIpspAspState,
m3uaSgpIpspAspRole,
m3uaSgpIpspAssocId,
m3uaSgpIpspAssocMinOutStreams,
m3uaSgpIpspAssocMaxInStreams
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage Signaling Processes "The m3ua group of objects to describe configuration values
(SGPs, ASPs or IPSPs) for the different Applications at either the Signaling Gateway Process (SGP) or the IP
they are serving." Server Process (IPSP)."
::= { m3uaGroups 4 }
m3uaRoutingAttributesTableGroup OBJECT-GROUP ::= { m3uaGroups 4 }
OBJECTS { m3uaRKId, m3uaSgpIpspStatsGroup OBJECT-GROUP
m3uaRKDpc, OBJECTS { m3uaSgpIpspStatAspupAckOut,
m3uaRKNa, m3uaSgpIpspStatAspacAckOut,
m3uaPeerAppId, m3uaSgpIpspStatAspdnAckOut,
m3uaPeerAppTrafficMode m3uaSgpIpspStatAspiaAckOut,
m3uaSgpIpspStatAspupIn,
m3uaSgpIpspStatAspacIn,
m3uaSgpIpspStatAspdnIn,
m3uaSgpIpspStatAspiaIn,
m3uaSgpIpspStatNotifyOut,
m3uaSgpIpspStatDunaOut,
m3uaSgpIpspStatDavaOut,
m3uaSgpIpspStatDupuOut,
m3uaSgpIpspStatDaudIn
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage Routing Tables." "The m3ua group of objects to count how the number of
messages received/send by a Signaling Process or IPSP."
::= { m3uaGroups 5 } ::= { m3uaGroups 5 }
m3uaRKSiAttributesTableGroup OBJECT-GROUP m3uaGenCfgGroup OBJECT-GROUP
OBJECTS { m3uaRKSi } OBJECTS { m3uaGenNaNi,
m3uaGenNaMtp3ProtType,
m3uaGenNaMtp3ProtVariant,
m3uaGenNaMtp3ProtVersion
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage SI Table for a RKey." "The m3ua group of objects to describe the Network Appearance
(NA) value."
::= { m3uaGroups 6 } ::= { m3uaGroups 6 }
m3uaRKOpcAttributesTableGroup OBJECT-GROUP m3uaGenStatsGroup OBJECT-GROUP
OBJECTS { m3uaRKOpc } OBJECTS { m3uaGenStatDataOut,
m3uaGenStatDataIn,
m3uaGenStatErrorOut,
m3uaGenStatErrorIn,
m3uaGenStatSconOut,
m3uaGenStatSconIn
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage OPC Table for a RKey." "The m3ua group of objects to count how the number of
messages received/send by a Signaling Process. This objects
are implemented in all kind of signaling processes: ASPs,
SGPs and IPSPs."
::= { m3uaGroups 7 } ::= { m3uaGroups 7 }
m3uaRKCicRangeAttribTableGroup OBJECT-GROUP -- 4.1.2 Compliance Statements
OBJECTS { m3uaRKCicMin,
m3uaRKCicMax }
STATUS current
DESCRIPTION
"The m3ua group of objects to manage CIC Table for a RKey."
::= { m3uaGroups 8 }
m3uaNaAttributesTableGroup OBJECT-GROUP m3uaAspCompliance MODULE-COMPLIANCE
OBJECTS { m3uaNaNI,
m3uaNaMtp3ProtocolType,
m3uaNaMtp3ProtocolVariant,
m3uaNaMtp3ProtocolVersion
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage NA Tables." "The compliance statement for Application Server Processes (ASP)
::= { m3uaGroups 9 } that implement this MIB in order to be managed using SNMP
protocol."
m3uaPcAttributesTableGroup OBJECT-GROUP MODULE -- this module
OBJECTS { m3uaNaPC MANDATORY-GROUPS { m3uaAttributesGroup,
m3uaAspCfgGroup,
m3uaGenCfgGroup,
m3uaAspStatsGroup,
m3uaGenStatsGroup
} }
::= { m3uaCompliances 1 }
m3uaSgpCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage PC Tables." "The compliance statement for Signaling Gateway Processes (SGP)
::= { m3uaGroups 10 } that implement this MIB in order to be managed using SNMP
protocol."
m3uaLocAddrAttributesTableGroup OBJECT-GROUP MODULE -- this module
OBJECTS { m3uaAssocLocalAddressIPType, MANDATORY-GROUPS { m3uaAttributesGroup,
m3uaAssocLocalAddressIP m3uaSgpIpspCfgGroup,
m3uaGenCfgGroup,
m3uaSgpIpspStatsGroup,
m3uaGenStatsGroup
} }
::= { m3uaCompliances 2 }
m3uaIpspCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The m3ua group of objects to manage Local IP Add. Tables." "The compliance statement IP Server Processes (IPSP) that
::= { m3uaGroups 11 } implement this MIB in order to be managed using SNMP protocol."
m3uaRemAddrAttributesTableGroup OBJECT-GROUP MODULE -- this module
OBJECTS { m3uaAssocRemAddressIPType, MANDATORY-GROUPS { m3uaAttributesGroup,
m3uaAssocRemAddressIP m3uaSgpIpspCfgGroup,
m3uaGenCfgGroup,
m3uaAspStatsGroup,
m3uaSgpIpspStatsGroup,
m3uaGenStatsGroup
} }
STATUS current
DESCRIPTION ::= { m3uaCompliances 3 }
"The m3ua group of objects to manage Remote IP Add.
Tables."
::= { m3uaGroups 12 }
END END
5. References 5. References
[M3UA] G. Sidebottom, L. Ong, Guy Mousseau, K. Gradischnig, H. J. 5.1 Normative References
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",
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 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
16, RFC 1212, March 1991. 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the [RFC1215] M. Rose, "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991. SNMP", RFC 1215, March 1991.
[RFC2571]Harrington, D., Presuhn, R.,and B. Wijnen, "An architecture
for Describing SNMP Management Frameworks", RFC 2571, April
1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2",
SMIv2", STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2",
SMIv2", STD 58, RFC 2580, April 1999. 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, [RFC2960] R. Stewart, Q. Xie, K. Morneault, C. Sharp, H. J.
"Message Processing and Dispatching for the Simple Network Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V.
Management Protocol (SNMP)", RFC 2572, April 1999. Paxson, "Stream Control Transmission Protocol", October 2000.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC3291] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder,
(USM) for version 3 of the Simple Network Management "Textual Conventions for Internet Network Addresses", May 2002.
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC3332] G. Sidebottom, K.Morneault, J. Pastor-Balbas, "SS7 MTP3-User
"Protocol Operations for Version 2 of the Simple Network Adaptation Layer (M3UA)", Mar 2002.
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 5.2 Informative References
RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC1213] Rose, M. and K. McCloghrie, "Management Information Base for
Access Control Model (VACM) for the Simple Network Network Management of TCP/IP-based internets", RFC 1213,March
Management Protocol (SNMP)", RFC 2575, April 1999. 1991.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2012] K. McCloghrie, "SNMPv2 Management Information Base for the
"Introduction to Version 3 of the Internet-standard Network Transmission Control Protocol using SMIv2", RFC 2012, November
Management Framework", RFC 2570, April 1999. 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Harvard University, Requirement Levels", BCP 14, RFC 2119, Harvard University,
March 1997 March 1997
[RFC2851-update] Textual Conventions for Internet Network Addresses, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
draft-ietf-ops-rfc2851-update-04.txt, Septemeber 20, 2001. "Introduction and Applicability Statements for Internet-Standard
Work in progress. Management Framework", RFC 3410, December 2002.
[RFC2786] R. Frye,D. Levi ,S. Routhier, B. Wijnen , " Coexistence [VANJ] Jacobson, V., "Congestion Avoidance and Control", SIGCOMM 1988,
between Version 1, Version 2, and Version 3 of the Internet Stanford, California.
standard Network Management Framework ", draft-ietf-ops-
rfc2851-update-06.txt, DEcember 2000.
[TADRESS] Textual Conventions for Transport Addresses, [IPv6ARCH] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe,
draft-ietf-ops-taddress-mib-01.txt, Septemeber 20, 2001. A. and B. Zill, "IPv6 Scoped Address Architecture", draft-ietf-
Work in progress. ipngwg-scoping-arch-04.txt, December 2002. Work in progress.
6. Security Consideration [TCPMIB] Bill Fenner, Keith McCloghrie, Rajiv Raghunarayan, Juergen
Schoenwalder, "Management Information Base for the Transmission
Control Protocol (TCP) ", draft-ietf-ipv6-rfc2012-update-01.txt
, November 2002. Work in progress.
There are a number of management objects defined in this MIB that have a [UDPMIB] Bill Fenner, "Management Information Base for User Datagram
MAX-ACCESS clause of read-write and/or read-create. Such objects may be Protocol (UDP), draft-ietf-ipv6-rfc2013-update-00.txt, June
considered sensitive or vulnerable in some network environments. The 2002. Work in progress.
support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. [MIBGUIDE] Heard, "Guidelines for MIB Authors and Reviewers", draft-
ietf-ops-mib-review-guidelines-00.txt, February 2003. Work in
progress
6. Security Considerations
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 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 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 over the network via SNMP. Not all versions of SNMP provide features
such a secure environment. for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if security measures SNMPv1 by itself is not a secure environment. Even if security
are taken (e.g., using IPSEC), there is no per-user control as to who measures are taken (e.g., using IPSEC), there is no per-user control
(once an IPSEC association is established between hosts) is allowed to as to who (once an IPSEC association is established between hosts) is
GET or SET the objects in this MIB allowed to GET or SET the objects in this MIB
It is recommended that the implementers consider the security features as It is recommended that the implementers consider the security features
provided by the SNMPv3 framework. Specifically, the use of the User- as provided by the SNMPv3 framework. Specifically, the use of the
based Security Model RFC 2574 [RFC2574] and the View-based Access Control User-based Security Model RFC 2574 [RFC2574] and the View-based Access
Model RFC 2575 [RFC2575] is recommended. Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity It is then a customer/user responsibility to ensure that the SNMP
giving access to an instance of this MIB, is properly configured to give entity giving access to an instance of this MIB, is properly
access to the objects only to those principals (users) that have configured to give access to the objects only to those principals
legitimate rights to indeed GET or SET (change/create/delete) them. (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them.
7. Acknowledgments 7. Acknowledgements
The author wish to thank Shyamal Prasad, Kurt Kite, Jennifer Jones, The authors wish to thank Shyamal Prasad, Kurt Kite, Jennifer Jones,
Srivats P., Ken Morneault and Javier Pastor for their comments. Srivats P., Ken Morneault and Tolga Asveren for their comments.
8. Authors' Addresses 8. Authors' Addresses
Antonio Roque Tel: +34-91-339-3523 Antonio Roque Tel: +34-91-339-3523
Ericsson Espana S.A. EMail: Antonio.Roque@ericsson.com Ericsson Espana S.A. EMail: Antonio.Roque@ericsson.com
Network Communication Services Via de los Poblados 13, 4th floor
Omb” 3, 4th floor Madrid, 28033
Madrid, 28045 Spain
Antonio Canete Tel: +34-91-339-2460
Ericsson Espana S.A. EMail: Antonio.Canete@ericsson.com
Via de los Poblados 13, 4th floor
Madrid, 28033
Spain
Jose-Javier Pastor-Balbas Tel: +34-91-339-1397
Ericsson Espana S.A. EMail: J.Javier.Pastor@ericsson.com
Via de los Poblados 13, 4th floor
Madrid, 28033
Spain Spain
9. Revision History 9. Revision History
9.1 Changes from draft rev 03 to draft rev 04: 9.1 Changes from draft rev 04 to draft rev 05:
o Integer32 is imported but not used. Removed o Changed objects from having writing permission to read-only
o General MIBs boiler plate updated.
o Tables divided per node type: ASPs, SGP/IPSP and General Tables
(with general values and statistic, valid per every node type)
o Updated contact information
o Removed CIC and SSN from the RK
o Security Considerations updated
o Copyright Statement included
9.2 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 TEXTUAL-CONVENTION is imported but not used. Removed
o mib-2 suggested as branch for mib o mib-2 suggested as branch for mib
o m3uaAppSpEpState consistently defined as INTEGER o m3uaAppSpEpState consistently defined as INTEGER
o m3uaPeerAppTrafficMode consistently defined as INTEGER o m3uaPeerAppTrafficMode consistently defined as INTEGER
o Fixed error in m3uaSpEpEntry object description text o Fixed error in m3uaSpEpEntry object description text
o Rework in m3uaAppType object description text o Rework in m3uaAppType object description text
9.2 Changes from draft rev 02 to draft rev 03: 9.3 Changes from draft rev 02 to draft rev 03:
o Value range of m3uaAppTrafficMode object is modified. o Value range of m3uaAppTrafficMode object is modified.
o Object m3uaLocalPort is changed to "read-write". A comment o Object m3uaLocalPort is changed to "read-write". A comment
is added with the recommended IANA port number. is added with the recommended IANA port number.
o Object m3uaFailOverBuffering is deleted. A comment in object o Object m3uaFailOverBuffering is deleted. A comment in object
m3uaTrValue is added: If Tr is 0 then FailOver Buffering is Off. m3uaTrValue is added: If Tr is 0 then FailOver Buffering is Off.
Thus, there is no further need for this element. Thus, there is no further need for this element.
skipping to change at page 57, line 33 skipping to change at page 63, line 4
o Index m3uaAppId in SP Endpoint Statistic Table is removed o Index m3uaAppId in SP Endpoint Statistic Table is removed
o Signaling Process Table replaced by Application-Endpoint Table o Signaling Process Table replaced by Application-Endpoint Table
o Index m3uaSpEpAssocId in SP Endpoint Table is removed o Index m3uaSpEpAssocId in SP Endpoint Table is removed
o Index m3uaSpEpassocId in Local and Remote IP address table is o Index m3uaSpEpassocId in Local and Remote IP address table is
replaced by m3uaSpEpId. replaced by m3uaSpEpId.
o Added new Lookup Reverse Tables for: o Added new Lookup Reverse Tables for:
- Get EndPoint Id from Association Id. - Get EndPoint Id from Association Id.
- Get Routing Key Id from Application Id. - Get Routing Key Id from Application Id.
- Get Routing Key Id from DPC and NA. - Get Routing Key Id from DPC and NA.
- Get Endpoints serving an Application. - Get Endpoints serving an Application.
o Routing Table has been reestructured to deal with multiplicity o Routing Table has been reestructured to deal with multiplicity
of SIs, OPCs and CIC Ranges per Routing Key. of SIs, OPCs and CIC Ranges per Routing Key.
Three new subtables are used. Three new subtables are used.
9.3 Changes from draft rev 01 to draft rev 02: 9.4 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.3 Signaling Process Table - Chapter re-phrased
o Section 3.1.2.4 Signaling Process Endpoint Table - Last paragraph o Section 3.1.2.4 Signaling Process Endpoint Table - Last paragraph
removed removed
o Section 3.1.2.5 Signaling Process Endpoint Statistics Table o Section 3.1.2.5 Signaling Process Endpoint Statistics Table
m3uaAppId and m3uaSpEpId added to the table figure m3uaAppId and m3uaSpEpId added to the table figure
Corresponding changes in Definitions chapter applied. Corresponding changes in Definitions chapter applied.
skipping to change at page 58, line 16 skipping to change at page 63, line 38
Corresponding changes in Definitions chapter applied. Corresponding changes in Definitions chapter applied.
o Object definition of m3uaMaxStreamInbound is removed. o Object definition of m3uaMaxStreamInbound is removed.
o Object Definition of m3uaSpEpEntry o Object Definition of m3uaSpEpEntry
Index "m3uaAppId" is replaced by m3uaSpEpAssocId. Index "m3uaAppId" is replaced by m3uaSpEpAssocId.
o Object Definition of m3uaSpEpStatRowStatus o Object Definition of m3uaSpEpStatRowStatus
Definition is deleted. Definition is deleted.
9.4 Changes due to the alignment with the RFC2851 update. 9.5 Changes due to the alignment with the RFC2851 update.
o Include clarification text of the IP address types supported in the 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) 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 o Remote Primary IP address: Addition of the ipv4z an ipv6z types for
non-globally IP addresses in which a scope identifier is needed. non-globally IP addresses in which a scope identifier is needed.
Addition of the scope of ipv6 type. All of them according to the Addition of the scope of ipv6 type. All of them according to the
RFC2851update-v04 RFC2851update-v04
o InetAddressType for local and remote IP addresses: o InetAddressType for local and remote IP addresses:
Limit UNKNOWN type only for unknown IP address format. Remove UNKNOWN Limit UNKNOWN type only for unknown IP address format. Remove UNKNOWN
type for zero-length value in the InetAddress since it will be never type for zero-length value in the InetAddress since it will be never
zero-length due to the size restriction (0..64) zero-length due to the size restriction (0..64)
Addition of the ipv4z an ipv6z types for non-globally IP addresses in 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. which a scope identifier is needed. Addition of the scope of ipv6
type.
All of them according to the RFC2851update-v04 All of them according to the RFC2851update-v04
o Conformance: o Conformance:
Description: Specify that the M3UA MIB only need to support IPv4/IPv6 Description: Specify that the M3UA MIB only need to support IPv4/IPv6
addresses without a zone index, unknown type and DNS names. Support for addresses without a zone index, unknown type and DNS names. Support
for
IPv4/IPv6 addresses without zone indices is not required. IPv4/IPv6 addresses without zone indices is not required.
InetAddressType of local and remote IP address: Clarify the InetAddressType of local and remote IP address: Clarify the
implementation is only required to support IPv4 and IPv6 address types implementation is only required to support IPv4 and IPv6 address types
without zone indices. Clarify also that UNKONWN type is only used in without zone indices. Clarify also that UNKONWN type is only used in
case of lcoal and remote addresses when invalid/unknown IP address case of lcoal and remote addresses when invalid/unknown IP address
format format
Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/