| draft-sigtran-m3ua-mib-00 Description: Request For Comments
You can download source copies of the file as follows:
Listed below is the contents of file draft-sigtran-m3ua-mib-00.txt.
Network Working Group Antonio Roque
INTERNET-DRAFT Ericsson
expires in six months December 21,2000
SS7 MTP3-User Adaptation Layer (M3UA)
Management Information Base using SMIv2
<draft-sigtran-m3ua-mib-00.txt>
Status of This Memo
This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC 2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts
as reference material or cite them other than as "work in
progress".
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/lid-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
The MTP3-User Adaptation Layer is a protocol for the transport of
any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP
using the services of the Stream Control Transmission Protocol. Also,
provision is made for protocol elements that enable a seamless
operation of the MTP3-User peers in the SS7 and IP domains. This
protocol would be used between a Signalling Gateway (SG) and a Media
Gateway Controller (MGC) or IP-resident Database. It is assumed that
the SG receives SS7 signalling over a standard SS7 interface using the
SS7 Message Transfer Part (MTP) to provide transport.
This memo defines the Management Information Base (MIB) module which
describes the minimum amount of objects needed to manage the implementation
of the SCTP.
Open Issues
- Remove this section.
- Remove Revision History
- Decide under which object identifier branch of the SNMP tree, M3UA
will be placed (value obtained when submitted to the IETF editor).
- Update references to drafts.
Table of Contents
1. Introduction ................................................
1.1 Abbreviations ..............................................
2. The SNMP framework ..........................................
3. Structure of the MIB ........................................
3.1 Protocol General Variables .................................
3.2 Protocol General Statistics ................................
3.3 M3UA Tables ................................................
4. Definitions .................................................
4.1 Conformance Information ....................................
4.1.1 Compliance Statements ....................................
4.1.2 Units of Conformance .....................................
5. References ..................................................
6. Security Considerations .....................................
7. Acknowledgements ............................................
8. Authors' Addresses ..........................................
9. Revision History ............................................
1. Introduction
This memo defines the Management Information Base (MIB) module which
describes managed objects for implementations of the SCTP.
The document starts with a brief description of the SNMP framework and
continues with the MIB explanation and security consideration among
others.
Terms related to the SCTP architecture are explained in [1]. Other
especific abbreviations are listed below.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
1.1 Abbreviations
AS - Application Server
ASP - Application Server Process
ASPM - Application Server Process Management
CIC - Circuit Identification Code
DPC - Destination Point Code
IPSP - IP Server Process
MIB - Management Information Base
M3UA - SS7 MTP3-User Adaptation Layer
NA - Network Appearance
NI - Network Indicator
OPC - Origination Point Code
PC - Point Code
SCTP - Stream Control Transmision Protocol
SG - Signaling Gateway
SI - Service Indicator
SMI - Structure of Management Information
SNMP - Simple Network Management Protocol
SP - Signaling Process
SSN - Subsystem Number
2. The SNMP Framework
The SNMP Management Framework presently consists of five major
components:
- An overall architecture, described in RFC 2271 [SNMPArch].
- Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215
[SNMPv1Traps]. The second version, called SMIv2, is described
in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904
[SNMPv2Conf].
- Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1
and described in RFC 1157 [SNMPv1]. A second version of the
SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM].
- Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in RFC 1157 [SNMPv1]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[SNMPv2PO].
- A set of fundamental applications described in RFC 2273
[SNMPv3App] and the view-based access control mechanism
described in RFC 2575 [SNMPv3VACM].
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the MIB
are defined using the mechanisms defined in the SMI. This memo
specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions
in SMIv1 during the translation process. However, this loss of
machine-readable information is not considered to change the
semantics of the MIB.
3. Structure of the MIB
The MIB is structured in the following way:
m3uaMib
/ \
m3uaObjects m3uaConformance
/ \ / \
m3uaScalars m3uaTables m3uaGroups m3uaCompliances
|
m3uaCompliance
where the following sections are described :
- m3uaObjects, where all the M3UA objects are defined under
this branch.
-m3uaScalars, where scalars values are placed. It is
divided in:
- General variables, where the main M3UA
variables are listed.
- General Statistics for M3UA.
- m3uaTables, to hold data from each Application Server,
Application Server Process, Signaling Gateway, Signaling
Gateway Process, Signaling Point Endpoint and Routing Table
together with the main statistics per SP Endpoint.
Local and Remote IP Address tables are included
into the general Endpoint table to allow multiples
IP addresses in order to support the multihome feature.
- m3uaConformance, for the Unit of Conformance.
- m3uaGroups, M3UA MIB variables have been grouped according
to their funcionality and the context they belong to (general
variables, variables/statistics per AS, variables per ASP,
variables per SG, variables per SGP, variables per local IP
address and variables/statistics per remote IP address).
- m3uaCompliances, Minimal list of objects in the M3UA MIB module
that an agent developer must implement.
3.1 Objects
3.1.1 Scalars
3.1.1.1 Protocol General Variables
The first section of the MIB contains the general variables of the
M3UA protocol. Maximum, minimum and initial values can be found here.
3.1.1.2 Protocol General Statistics
Statistics included here are related to the whole M3UA layer. Statistics
related to a specific Peer Association are defined inside its
concerned table (context).
3.1.2 Tables
3.1.2.1 Application Server Table
Defines data related to an Application Server, its state and traffic
handling mode.
m3uaAsTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAsId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAsTrafficMode / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAsState / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAsRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.2 Application Server Process Table
Defines data related to an Application Server Process, its state and traffic
handling mode, and the Association ID of the association established to that
ASP.
Note that an ASP can maintain different states and traffic handling modes for
every AS 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 ASP table
will be created per every combination of AS and Association ID.
Several ASP will correspond to one SP Endpoint. They will be linked by the
Association Id.
m3uaAspTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAsId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAspAssocId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAspState / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.3 Signaling Gateway Table
Defines data related to a Signaling Gateway, its state and traffic
handling mode.
m3uaSgTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgTrafficMode / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgState / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.4 Signaling Gateway Process Table
Defines data related to a Signaling Gateway Process, its state and the
Association ID that identifies that SGP.
An unique SGP corresponds to an unique SP Endpoint and SG ID. They will be
linked by the Association Id.
m3uaSgpTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgpAssocId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgpState / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSgpRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.5 Routing Table
Every entry in this table contains the data that defines a Routing Key.
As a Routing Key may be composed of any combination of basic SS7 routing
elements, if an element is not included in the routing key, a default value
is assigned. This default value can continue being considered as an indexing
value itself.
m3uaRouting
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNA (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNI (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSI (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaOPC (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaDPC (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSSN (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaCICmin (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaCICmax (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaPeerAppId / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.6 Network Appearance Table
Defines the data specific to a Network Appearance.
m3uaNaTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNA (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaNI / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaMtp3ProtocolType / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaMtp3ProtocolVariant / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaMtp3ProtocolVersion / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.7 Signaling Process Endpoint Table
Defines data related to a Signaling Process Endpoint.
A SP Endpoint identifies a peer node were a SGP, ASP or IPSP are running.
The table contains the Endpoint identifier and data related to the association
to that endpoint.
This table is expanded with the Remote IP Address Table that
identify the endpoint and with the Local IP Address Table that identify the
local node for that endpoint.
The table contains data related to the Association, as its state, number of
streams, and the Association ID, provided by SCTP when the association is
established.
The main table also contains statistics data related to the M3UA messaging
exchanged through that association between the Signaling Processes that
hold the association.
m3uaSpEpTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocRemHostName / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocRemPort / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocReqOutStreams / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocOutStreams / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocIncStreams / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocState / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDataSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDataRecived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspupSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspupAckSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspacSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspacAckSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspdnSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspdnAckSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspiaSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspiaAckSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspupReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspupAckReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspacReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspacAckReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspdnReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspdnAckReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspiaReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocAspiaAckReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocNotifySent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocErrorSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocNotifyReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocErrorReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDunaSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDavaSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocSconSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDupuSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDaudSent / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDunaReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDavaReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocSconReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDupuReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpAssocDaudReceived / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaSpEpRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.8 Expanded Tables
3.1.2.8.1 Point Code Table
This table expand information in entries in Network Appearance Table.
A SG with several Network Appearances may be connected to different
SS7 Networks and may be represented in each SS7 Network by different
Point Codes.
m3uaNaPcTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNA (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaPC(index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaNaPcRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1.2.8.2 Local and Remote IP Address Tables
These tables expand information for SP Endpoint Tables. When an
SP Endpoint entry is created, a default free Association Id is assigned to
that entry. The Local and Remote IP Address Table that will be used to
establish an association towards the SGP or ASPEP provided are stored in
these tables. When the SCTP Association is established, the Association Id
will be replaced by the one obtained from SCTP.
If the remote addresses change during association negotiation, they will be
updated in the corresponding table.
a) Table for local IP addressess information:
This table stores information related to the local IP
address/-es reserved for the association. It's indexed by
the IP address.
b) Table for remote IP addresses information:
This table stores information related to the remote IP
address/-es reserved for the association. It's indexed by
the IP addresses.
Note that the IP address indexing the tables is valid for IPv4, IPv6 and
DNS [RFC2851]. Therefore, IP address is defined by the Internet address
type and the value of the IP address, according to the Textual Conventions
for Internet Network Address.
However, DNS value is not being used to identify an IP address since it is
only valid during initialization (once this stage is finished, both sides only
use IP addresses). To keep the name of the remote peer, an entry has been
created (m3uaAssocRemHostName) in the association table. When no DNS name is
provided by the remote SCTP endpoint at init time, this value will be
NULL. Otherwise, the received DNS name will be stored.
m3uaAssocLocalAddressTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocLocalAddressIPType(index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocLocalAddressIP (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocLocalAddressRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
m3uaAssocRemAddressTable
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocId (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocRemAddressIPType(index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocRemAddressIP (index) / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| m3uaAssocRemAddressRowStatus / ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Every entry is explained when defining the MIB.
3.2 Conformance
3.2.1 Groups
This section includes all the variables defined in the MIB grouped by
function(variables and statistics) and context (M3UA general parameters,
AS, ASP, SG and SGP context, local IP address context or remote IP address context).
Therefore following groups were created:
- General variables for the M3UA layer
- General statistics for the M3UA layer
- Variables for AS, ASP, SG and SGP, and variables per
local and remote IP address
- Statistics per remote SP endpoint
3.2.2 Compliance
Requirements of the M3UA MIB to be implemented.
4. Definitions
M3UA-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32,
Counter32, Counter64, mib-2
FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION, RowStatus
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC 2580
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB -- RFC 2851
;
m3uaMIB MODULE-IDENTITY
LAST-UPDATED "200101050000Z"
ORGANIZATION "IETF SIGTRAN Working Group"
CONTACT-INFO
" Antonio Roque Alvarez
Postal: Ericsson Espana S. A.
C/Retama 7
28045 Madrid
Spain
Phones: +34 91 339 3523
Emails: Antonio.Roque@ericsson.com"
DESCRIPTION
"The MIB module for managing M3UA implementation."
REVISION "200101050000Z"
DESCRIPTION
"MIB module developed for the SIGTRAN IETF group. Based on M3UAv4"
::= { xxxx } -- IANA needs to choose this value
-- when sent to the RFC editor
-- Top-level structure of the MIB
m3uaObjects OBJECT IDENTIFIER ::= { m3uaMIB 1 }
m3uaConformance OBJECT IDENTIFIER ::= { m3uaMIB 2 }
m3uaScalars OBJECT IDENTIFIER ::= { m3uaObjects 1 }
m3uaTables OBJECT IDENTIFIER ::= { m3uaObjects 2 }
-- PROTOCOL GENERAL VARIABLES
-- **************************
m3uaVersion OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Identifies the current version of the M3UA."
::= { m3uaScalars 1 }
m3uaProcType OBJECT-TYPE
SYNTAX INTEGER {
sgp(1), -- Signalling Gateway Process
asp(2), -- Application Server Process
ipsp(3) -- IP Server Process
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable indicates the type of the process where the
M3UA layer is located."
::= { m3uaScalars 2 }
m3uaLocalPort OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Identifies the port of the M3UA service."
::= { m3uaScalars 3 }
m3uaTrValue OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Initial value of the Failover timer Tr. Recommended
value is 3000 milliseconds."
::= { m3uaScalars 4 }
m3uaTPaudValue OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Initial value of the Periodic Audit timer TrPaud Recommended
value is 5000 milliseconds."
::= { m3uaScalars 5 }
m3uaHeartBeat OBJECT-TYPE
SYNTAX INTEGER {
on(0), -- Heartbeat is enabled.
off(1) -- Heartbeat is disabled. No BEAT messages
-- sent but BEAT messages received are
-- responded.
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Activates or deactivates the heartbeat procedure at M3UA level."
::= { m3uaScalars 6 }
m3uaTBeatValue OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Initial value of the HeartBeat timer TBeat. Recommended
value is 1000 milliseconds."
::= { m3uaScalars 7 }
m3uaTAckValue OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Initial value of the Retransmision timer TAck. Recommended
value is 2000 milliseconds."
::= { m3uaScalars 8 }
m3uaSpLshMethod OBJECT-TYPE
SYNTAX INTEGER {
none(0), -- Random
sls(1), -- Basing on SLS
cic(2), -- Basing on CIC
ssn(3), -- Basing on SSN
dpg(4), -- Basing on DPC
other(5) -- Other method
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the method to be used when the load
must be shared between several ACTIVE Signaling Processes."
::= { m3uaScalars 9 }
m3uaStreamLshMethod OBJECT-TYPE
SYNTAX INTEGER {
none(0), -- Random
sls(1), -- Basing on SLS
cic(2), -- Basing on CIC
ssn(3), -- Basing on SSN
dpc(4), -- Basing on DPC
other(5) -- Other method
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the method to be used when the load
must be shared between several streams within the same
SCTP Association."
::= { m3uaScalars 10 }
m3uaMaxStreamInbound OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Maximum number of incoming streams allowed when accepting
a SCTP Association from a remote peer. Recommended value is 10."
::= { m3uaScalars 11 }
m3uaFailOverBuffering OBJECT-TYPE
SYNTAX INTEGER {
on(0), -- Messages are buffered during FailOver
off(1) -- No buffering. Messages are discarded
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Activates or deactivates the buffering of messages during
failover."
::= { m3uaScalars 12 }
m3uaFailOverBuffSize OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Size of the failover retransmision buffer. Recommended value is
64 Kbytes. Only valid if failover buffer option has been set to
ON."
::= { m3uaScalars 13 }
m3uaMaxPeerApplications OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Maximum number of remote applications ( ASs or SGs )."
::= { m3uaScalars 14 }
m3uaMaxSPperApplications OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Maximum number of Signaling Processes ( ASPs, IPSPs or SGPs )
per remote application ( AS or SG)."
::= { m3uaScalars 15 }
-- PROTOCOL GENERAL STATISTICS
m3uaRoutingFailures OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times a routing operation against Routing Table
fails. No final SCTP Association ID is obtained from the routing
operation. That is the reason why this is a general statistic
instead a per association statistic."
::= { m3uaScalars 16 }
-- M3UA TABLES
-- ***********
-- The Application Server Table
-- ****************************
-- The Application Server table contains information about each
-- Application Server for which one or more routing keys can exist in the
-- routing table.
-- This table exist when the Proccess Type is SGP or IPSP.
m3uaAsTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Application Server-specific information."
::= { m3uaTables 1 }
m3uaAsEntry OBJECT-TYPE
SYNTAX M3uaAsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for the AS."
INDEX { m3uaAsId }
::= { m3uaAsTable 1 }
M3uaAsEntry ::= SEQUENCE {
m3uaAsId Unsigned32,
m3uaAsState INTEGER,
m3uaAsTrafficMode INTEGER,
m3uaAsRowStatus RowStatus
}
m3uaAsId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Application Server Identification Value."
::= { m3uaAsEntry 1 }
m3uaAsState OBJECT-TYPE
SYNTAX INTEGER {
active(1),
inactive(2),
down(3),
pending(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current Application Server State. Based on the state
of the ASPs which serve it."
::= { m3uaAsEntry 2 }
m3uaAsTrafficMode OBJECT-TYPE
SYNTAX INTEGER {
loadshare(1),
override(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current Application Server traffic handling mode."
::= { m3uaAsEntry 3 }
m3uaAsRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted by management operation using the RowStatus convention."
::= { m3uaAsEntry 4 }
-- The Application Server Process Table
-- ************************************
-- The Application Server Process table contains information about each
-- ASP that is serving an specific AS trough a specific SCTP Association.
-- This table exists when the Proccess Type is SGP or IPSP.
-- Although an ASP is identified with an unique SCTP endpoint, there may
-- be more than one ASP table entry indexed by the same SCTP Association Id.
-- The reason for this is that an ASP may maintain different states for
-- the different ASs that it is serving. An ASP entry will then exist in the
-- table per every combination of m3uaAspAssocId and m3uaAsId.
-- When an ASP Active message is sent from the remote ASP Endpoint including
-- the Routing Contexts that identify the ASs that the ASP is serving, one
-- entry is created in this table per every RC received with the message.
-- Entries in this table cannot be added, deleted or modified via
-- management.
m3uaAspTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaAspEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Application Server Process-specific
information."
::= { m3uaTables 2 }
m3uaAspEntry OBJECT-TYPE
SYNTAX M3uaAspEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for the ASP."
INDEX { m3uaAsId, -- shared index
m3uaAspAssocId }
::= { m3uaAspTable 1 }
M3uaAspEntry ::= SEQUENCE {
m3uaAspAssocId Unsigned32,
m3uaAspState INTEGER
}
m3uaAspAssocId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Association Identification. Value identifying the association
of the endpoint corresponding to the ASP. This value is extracted
from the SCTP association through which the ASP Active message has
been received."
::= { m3uaAspEntry 1 }
m3uaAspState OBJECT-TYPE
SYNTAX INTEGER {
active(1),
standby(2),
inactive(3),
down(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current Application Server Process State. Based on
ASPM Messages."
::= { m3uaAspEntry 2 }
-- The Signaling Gateway Table
-- ****************************
-- The Signaling Gateway table contains information about each
-- Signaling Gateway for which one or more routing keys can exist in the
-- routing table.
-- This table exists when the Proccess Type is ASP.
m3uaSgTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaSgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Signaling Gateway-specific information."
::= { m3uaTables 3 }
m3uaSgEntry OBJECT-TYPE
SYNTAX M3uaSgEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for the SG."
INDEX { m3uaSgId }
::= { m3uaSgTable 1 }
M3uaSgEntry ::= SEQUENCE {
m3uaSgId Unsigned32,
m3uaSgState INTEGER,
m3uaSgTrafficMode INTEGER,
m3uaSgRowStatus RowStatus
}
m3uaSgId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Signaling Gateway Identification Value. Assigned by
management."
::= { m3uaSgEntry 1 }
m3uaSgState OBJECT-TYPE
SYNTAX INTEGER {
active(1),
down(2),
pending(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current Signaling Gateway State. Based on the state
of the SGPs which serve it."
::= { m3uaSgEntry 2 }
m3uaSgTrafficMode OBJECT-TYPE
SYNTAX INTEGER {
loadshare(1),
override(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current Signaling Gateway traffic handling mode."
::= { m3uaSgEntry 3 }
m3uaSgRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted by management operation using the RowStatus convention."
::= { m3uaSgEntry 4 }
-- The Signaling Gateway Process Table
-- ***********************************
-- The Signaling Gateway Process table contains information about each
-- SGP that is serving an specific SG trough a specific SCTP Association.
-- A SGP is identified with an unique SCTP endpoint.
-- This table exists when the Proccess Type is ASP.
m3uaSgpTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaSgpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Signaling Gateway Process-specific
information."
::= { m3uaTables 4 }
m3uaSgpEntry OBJECT-TYPE
SYNTAX M3uaSgpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for the ASP."
INDEX { m3uaSgId, -- shared index
m3uaSgpAssocId }
::= { m3uaSgpTable 1 }
M3uaSgpEntry ::= SEQUENCE {
m3uaSgpState INTEGER,
m3uaSgpAssocId Unsigned32,
m3uaSgpRowStatus RowStatus
}
m3uaSgpState OBJECT-TYPE
SYNTAX INTEGER {
active(1),
down(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Current Signaling Gateway Process State. Based on
ASPM Messages."
::= { m3uaSgpEntry 1 }
m3uaSgpAssocId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Association Identification. Value identifying the association
to that endpoint. This value is extracted from the SCTP
association through which the ASP has connected the SGP."
::= { m3uaSgpEntry 2 }
m3uaSgpRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted by management operation using the RowStatus convention."
::= { m3uaSgpEntry 3 }
-- The Routing Table
-- *****************
-- The Routing table contains a list of routing keys which translate to
-- Application Servers or Signaling Gateways.
-- This table exists with any Proccess Type.
-- An Index Computation mechanism could be considered instead of current
-- multi-index mechanism.
m3uaRoutingTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaRoutingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Routing-specific information."
::= { m3uaTables 5 }
m3uaRoutingEntry OBJECT-TYPE
SYNTAX M3uaRoutingEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for a Routing Key."
INDEX { m3uaNA,
m3uaNI,
m3uaSI,
m3uaOPC,
m3uaDPC,
m3uaSSN,
m3uaCICmin,
m3uaCICmax }
::= { m3uaRoutingTable 1 }
M3uaRoutingEntry ::= SEQUENCE {
m3uaNA Unsigned32,
m3uaNI Unsigned32,
m3uaSI Unsigned32,
m3uaOPC Unsigned32,
m3uaDPC Unsigned32,
m3uaSSN Unsigned32,
m3uaCICmin Unsigned32,
m3uaCICmax Unsigned32,
m3uaPeerAppId Unsigned32,
m3uaRoutingRowStatus RowStatus
}
m3uaNA OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Network Appearance for that routing key. A default value
will be assigned if not present in the Routing Key."
::= { m3uaRoutingEntry 1 }
m3uaNI OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Network Indicator for that routing key. A default value
will be assigned if not present in the Routing Key."
::= { m3uaRoutingEntry 2 }
m3uaSI OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Service Indicator for that routing key. A default value
will be assigned if not present in the Routing Key."
::= { m3uaRoutingEntry 3 }
m3uaOPC OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Origination Point Code for that routing key. A default value
will be assigned if not present in the Routing Key."
::= { m3uaRoutingEntry 4 }
m3uaDPC OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Destination Point Code for that routing key. A default value
will be assigned if not present in the Routing Key."
::= { m3uaRoutingEntry 5 }
m3uaSSN OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Subsystem Number for that routing key. A default value
will be assigned if not present in the Routing Key."
::= { m3uaRoutingEntry 6 }
m3uaCICmin OBJECT-TYPE
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."
::= { m3uaRoutingEntry 7 }
m3uaCICmax OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Maximum value of the Circuit Identification Code
Range for that routing key. A default value will
be assigned if not present in the Routing Key."
::= { m3uaRoutingEntry 8 }
m3uaPeerAppId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Peer Application Identification Value. It can identify
an Application Server or a Signaling Gateway."
::= { m3uaRoutingEntry 9 }
m3uaRoutingRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted by management operation using the RowStatus convention."
::= { m3uaRoutingEntry 10 }
-- The Network Appearance table
-- ****************************
-- The NA table contains information about the specific variables
-- that apply to every Network Appearance.
-- This table can exists (not neccessarily) with any Proccess Type.
m3uaNaTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaNaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Network Appearance-specific information."
::= { m3uaTables 6 }
m3uaNaEntry OBJECT-TYPE
SYNTAX M3uaNaEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for a Network Appearance."
INDEX { m3uaNA } -- shared index
::= { m3uaNaTable 1 }
M3uaNaEntry ::= SEQUENCE {
m3uaNaNI Unsigned32,
m3uaNaMtp3ProtocolType INTEGER,
m3uaNaMtp3ProtocolVariant Unsigned32,
m3uaNaMtp3ProtocolVersion Unsigned32,
m3uaNaRowStatus RowStatus
}
m3uaNaNI OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Identifies the Network Indicator of the SG Node in the
SS7 Network."
::= { m3uaNaEntry 2 }
m3uaNaMtp3ProtocolType OBJECT-TYPE
SYNTAX INTEGER {
itu(1),
ansi(2),
china(3),
ntt(4),
other(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The MTP3 protocol type for this NA."
::= { m3uaNaEntry 4 }
m3uaNaMtp3ProtocolVariant OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The MTP3 protocol variant for this NA."
::= { m3uaNaEntry 5 }
m3uaNaMtp3ProtocolVersion OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The MTP3 protocol version for this NA."
::= { m3uaNaEntry 6 }
m3uaNaRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted by management operation using the RowStatus convention."
::= { m3uaNaEntry 7 }
-- The Point Code table
-- ****************************
-- The PC table contains a list of point codes that identify the SG node
-- in the SS7 Network. This list is related with and extends information of
-- every NA in NA Table.
-- This table can exists (not neccessarily) with any Proccess Type.
m3uaNaPcTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaNaPcEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing the list of Point Codes that identify
the SG Node in the SS7 Network for that Network App."
::= { m3uaTables 7 }
m3uaNaPcEntry OBJECT-TYPE
SYNTAX M3uaNaPcEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Point Code Entry."
INDEX { m3uaNA, -- shared index
m3uaNaPC }
::= { m3uaNaPcTable 1 }
M3uaNaPcEntry ::= SEQUENCE {
m3uaNaPC Unsigned32,
m3uaNaPcRowStatus RowStatus
}
m3uaNaPC OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Point Code Value."
::= { m3uaNaPcEntry 1 }
m3uaNaPcRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted by management operation using the RowStatus convention."
::= { m3uaNaPcEntry 2 }
-- The SP Endpoint Table
-- **********************
-- Defines data related to a Signaling Process Endpoint.
-- A SP Endpoint identifies a peer node were a SGP, ASP or IPSP are running.
-- This table exists with any Proccess Type.
-- The table contains the Endpoint Identifier and data related to the
-- SCTP association to that remote endpoint.
-- The Signaling Process Endpoint table contains information about
-- specific data regarding the physical location of that endpoint,
-- the list of remote IP addresses of that endpoint, and the list of local
-- IP addresses that want to be used against that endpoint.
-- 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.
-- The main table also contains statistics data related to the M3UA messaging
-- exchanged through that association between the Signaling Processes that
-- hold the association.
m3uaSpEpTable OBJECT-TYPE
SYNTAX SEQUENCE OF M3uaSpEpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing Signaling Process Endpoint-specific
information."
::= { m3uaTables 8 }
m3uaSpEpEntry OBJECT-TYPE
SYNTAX M3uaSpEpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"General common variables for the ASP."
INDEX { m3uaAsId, -- shared index
m3uaSpEpId }
::= { m3uaSpEpTable 1 }
M3uaSpEpEntry ::= SEQUENCE {
m3uaSpEpId Unsigned32,
m3uaSpEpAssocId Unsigned32,
m3uaSpEpAssocRemHostName OCTET STRING,
m3uaSpEpAssocRemPort Unsigned32,
m3uaSpEpAssocReqOutStreams Unsigned32,
m3uaSpEpAssocOutStreams Unsigned32,
m3uaSpEpAssocIncStreams Unsigned32,
m3uaSpEpAssocState INTEGER,
m3uaSpEpAssocDataSent Counter64,
m3uaSpEpAssocDataReceived Counter64,
m3uaSpEpAssocAspupSent Counter64,
m3uaSpEpAssocAspupAckSent Counter64,
m3uaSpEpAssocAspacSent Counter64,
m3uaSpEpAssocAspacAckSent Counter64,
m3uaSpEpAssocAspdnSent Counter64,
m3uaSpEpAssocAspdnAckSent Counter64,
m3uaSpEpAssocAspiaSent Counter64,
m3uaSpEpAssocAspiaAckSent Counter64,
m3uaSpEpAssocAspupReceived Counter64,
m3uaSpEpAssocAspupAckReceived Counter64,
m3uaSpEpAssocAspacReceived Counter64,
m3uaSpEpAssocAspacAckReceived Counter64,
m3uaSpEpAssocAspdnReceived Counter64,
m3uaSpEpAssocAspdnAckReceived Counter64,
m3uaSpEpAssocAspiaReceived Counter64,
m3uaSpEpAssocAspiaAckReceived Counter64,
m3uaSpEpAssocNotifySent Counter64,
m3uaSpEpAssocErrorSent Counter64,
m3uaSpEpAssocNotifyReceived Counter64,
m3uaSpEpAssocErrorReceived Counter64,
m3uaSpEpAssocDunaSent Counter64,
m3uaSpEpAssocDavaSent Counter64,
m3uaSpEpAssocSconSent Counter64,
m3uaSpEpAssocDupuSent Counter64,
m3uaSpEpAssocDaudSent Counter64,
m3uaSpEpAssocDunaReceived Counter64,
m3uaSpEpAssocDavaReceived Counter64,
m3uaSpEpAssocSconReceived Counter64,
m3uaSpEpAssocDupuReceived Counter64,
m3uaSpEpAssocDaudReceived Counter64,
m3uaSpEpRowStatus RowStatus
}
m3uaSpEpId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Signaling Process Endpoint Identification Value."
::= { m3uaSpEpEntry 1 }
m3uaSpEpAssocId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Association Identification. Value identifying the association
for that endpoint. This value is extracted from the SCTP
association Id value returned by SCTP when the association is
established to that endpoint."
::= { m3uaSpEpEntry 2 }
m3uaSpEpAssocRemHostName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Peer's DNS name.
If no DNS domain name was received at init time from the peer,
this entry will be meaningless, therefore it will store a NULL
value.
Otherwise, the remote host name received at init time will be
stored."
::= { m3uaSpEpEntry 3 }
m3uaSpEpAssocRemPort OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"M3UA port number to connect to remote Endpoint."
::= { m3uaSpEpEntry 4 }
m3uaSpEpAssocReqOutStreams OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the SCTP association is initiated from the local peer,
this will be the number of outgoing streams that will be
requested to the remote peer at association start up."
::= { m3uaSpEpEntry 5 }
m3uaSpEpAssocOutStreams OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"outgoing Streams according to the negotiation at association
start up. This parameter has to be read-only by the manager."
::= { m3uaSpEpEntry 6 }
m3uaSpEpAssocIncStreams OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Incoming Streams according to the negotiation at association
start up. This parameter has to be read-only by the manager."
::= { m3uaSpEpEntry 7 }
m3uaSpEpAssocState OBJECT-TYPE
SYNTAX INTEGER {
closed(1),
established(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The state of this SCTP association."
::= { m3uaSpEpEntry 8 }
-- Association Statistics
-- DATA Statistics per Association
m3uaSpEpAssocDataSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DATA messages sent through the association."
::= { m3uaSpEpEntry 9 }
m3uaSpEpAssocDataReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DATA messages received through the association."
::= { m3uaSpEpEntry 10 }
-- End of DATA Statistics per Association
-- MGMT Statistics per Association
m3uaSpEpAssocAspupSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPUP messages sent through the association."
::= { m3uaSpEpEntry 11 }
m3uaSpEpAssocAspupAckSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPUP ACK messages sent through the association."
::= { m3uaSpEpEntry 12 }
m3uaSpEpAssocAspacSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPAC messages sent through the association."
::= { m3uaSpEpEntry 13 }
m3uaSpEpAssocAspacAckSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPAC ACK messages sent through the association."
::= { m3uaSpEpEntry 14 }
m3uaSpEpAssocAspdnSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPDN messages sent through the association."
::= { m3uaSpEpEntry 15 }
m3uaSpEpAssocAspdnAckSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPDN ACK messages sent through the association."
::= { m3uaSpEpEntry 16 }
m3uaSpEpAssocAspiaSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPIA messages sent through the association."
::= { m3uaSpEpEntry 17 }
m3uaSpEpAssocAspiaAckSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPIA ACK messages sent through the association."
::= { m3uaSpEpEntry 18 }
m3uaSpEpAssocAspupReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPUP messages received through the association."
::= { m3uaSpEpEntry 19 }
m3uaSpEpAssocAspupAckReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPUP ACK messages received through the association."
::= { m3uaSpEpEntry 20 }
m3uaSpEpAssocAspacReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPAC messages received through the association."
::= { m3uaSpEpEntry 21 }
m3uaSpEpAssocAspacAckReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPAC ACK messages received through the association."
::= { m3uaSpEpEntry 22 }
m3uaSpEpAssocAspdnReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPDN messages received through the association."
::= { m3uaSpEpEntry 23 }
m3uaSpEpAssocAspdnAckReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPDN ACK messages received through the association."
::= { m3uaSpEpEntry 24 }
m3uaSpEpAssocAspiaReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPIA messages received through the association."
::= { m3uaSpEpEntry 25 }
m3uaSpEpAssocAspiaAckReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ASPIA ACK messages received through the association."
::= { m3uaSpEpEntry 26 }
-- End of ASPM Statistics per Association
-- MGMT Statistics per Association
m3uaSpEpAssocNotifySent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of NOTIFY messages sent through the association."
::= { m3uaSpEpEntry 27 }
m3uaSpEpAssocErrorSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ERROR messages sent through the association."
::= { m3uaSpEpEntry 28 }
m3uaSpEpAssocNotifyReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of NOTIFY messages Received through the association."
::= { m3uaSpEpEntry 29 }
m3uaSpEpAssocErrorReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of ERROR messages Received through the association."
::= { m3uaSpEpEntry 30 }
-- End of MGMT Statistics per Association
-- SSNM Statistics per Association
m3uaSpEpAssocDunaSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DUNA messages sent through the association."
::= { m3uaSpEpEntry 31 }
m3uaSpEpAssocDavaSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DAVA messages sent through the association."
::= { m3uaSpEpEntry 32 }
m3uaSpEpAssocSconSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of SCON messages sent through the association."
::= { m3uaSpEpEntry 33 }
m3uaSpEpAssocDupuSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DUPU messages sent through the association."
::= { m3uaSpEpEntry 34 }
m3uaSpEpAssocDaudSent OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DAUD messages sent through the association."
::= { m3uaSpEpEntry 35 }
m3uaSpEpAssocDunaReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DUNA messages received through the association."
::= { m3uaSpEpEntry 36 }
m3uaSpEpAssocDavaReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DAVA messages received through the association."
::= { m3uaSpEpEntry 37 }
m3uaSpEpAssocSconReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of SCON messages received through the association."
::= { m3uaSpEpEntry 38 }
m3uaSpEpAssocDupuReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DUPU messages received through the association."
::= { m3uaSpEpEntry 39 }
m3uaSpEpAssocDaudReceived OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of DAUD messages received through the association."
::= { m3uaSpEpEntry 40 }
-- End of SSNM Statistics per Association
m3uaSpEpRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted by management operation using the RowStatus convention."
::= { m3uaSpEpEntry 41 }
-- Expanded tables: Including Multihome feature
-- Local Address table
-- *******************
-- This table exists with any Proccess Type.
m3uaAssocLocalAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF SctpAssocLocalAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Expanded table of m3uaAssocTable based on the AssocId index.
It shows several interesting data for each local
address which takes part in this association."
::= { m3uaTables 9 }
m3uaAssocLocalAddressEntry OBJECT-TYPE
SYNTAX SctpAssocLocalAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Local information about the available addresses."
INDEX { m3uaSpEpAssocId, -- shared index
m3uaAssocLocalAddressIPType,
m3uaAssocLocalAddressIP }
::= { m3uaAssocLocalAddressTable 1 }
SctpAssocLocalAddressEntry ::= SEQUENCE {
m3uaAssocLocalAddressIPType InetAddressType,
m3uaAssocLocalAddressIP InetAddress,
m3uaAssocLocalAddressRowStatus RowStatus
}
m3uaAssocLocalAddressIPType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of a local IP address available for this association.
unknown (0) An unknown address type. This value MUST
be used if the value of the corresponding
InetAddress object is a zero-length string.
It may also be used to indicate an IP address
which is not one of the formats defined below.
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]."
::= { m3uaAssocLocalAddressEntry 1 }
m3uaAssocLocalAddressIP OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of a local IP address available for this association.
An InetAddress value is always interpreted within the
context of an InetAddressType value.
If SCTP are using DNS names, the mapping to IP address/-es
will be done at reception of INIT or INIT_ACK messages."
::= { m3uaAssocLocalAddressEntry 2 }
m3uaAssocLocalAddressRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted using the RowStatus convention.
A row in this table will be created per local IP address to be
used in this association. The creation takes part when
a new row in the m3uaAssocTable is created or when a new IP
address is added in the local interface (if this function
is allowed).
A row in this table will be deleted per local IP address used
in this association when the corresponding row in m3uaAssocTable
is deleted or when an IP address is removed from the local
interface (if this function is allowed).."
::= { m3uaAssocLocalAddressEntry 3 }
-- Remote Addresses TABLE
-- **********************
-- This table exists with any Proccess Type.
m3uaAssocRemAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF SctpAssocRemAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Expanded table of m3uaAssocTable based on the AssocId index
It shows several interesting data for each remote peer IP
address which is used in this association."
::= { m3uaTables 10 }
m3uaAssocRemAddressEntry OBJECT-TYPE
SYNTAX SctpAssocRemAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about the remote IP address most important variables"
INDEX { m3uaSpEpAssocId, -- shared index
m3uaAssocRemAddressIPType,
m3uaAssocRemAddressIP }
::= { m3uaAssocRemAddressTable 1 }
SctpAssocRemAddressEntry ::= SEQUENCE {
m3uaAssocRemAddressIPType InetAddressType,
m3uaAssocRemAddressIP InetAddress,
m3uaAssocRemAddressRowStatus RowStatus
}
m3uaAssocRemAddressIPType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of a remote IP address available for this association.
unknown (0) An unknown address type. This value MUST
be used if the value of the corresponding
InetAddress object is a zero-length string.
It may also be used to indicate an IP address
which is not one of the formats defined below.
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]."
::= { m3uaAssocRemAddressEntry 1 }
m3uaAssocRemAddressIP OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of a remote IP address available for this association.
An InetAddress value is always interpreted within the
context of an InetAddressType value."
::= { m3uaAssocRemAddressEntry 2 }
m3uaAssocRemAddressRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An object that allows entries in this table to be created and
deleted using the RowStatus convention.
A row in this table will be created per remote IP address to be
used in this association. The creation takes part when
a new row in the m3uaAssocTable is created.
A row in this table will be deleted per remote IP address used
in this association when the corresponding row in m3uaAssocTable
is deleted."
::= { m3uaAssocRemAddressEntry 3 }
-- 4.1 Conformance Information
m3uaGroups OBJECT IDENTIFIER ::= { m3uaConformance 1 }
m3uaCompliances OBJECT IDENTIFIER ::= { m3uaConformance 2 }
-- 4.1.1 Compliance Statements
m3uaCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement M3UA."
MODULE -- this module
MANDATORY-GROUPS { m3uaGeneralVariablesGroup,
m3uaAsTablesVariablesGroup,
m3uaAspTablesVariablesGroup,
m3uaSpEpTablesVariablesGroup,
m3uaSgTablesVariablesGroup,
m3uaSgpTablesVariablesGroup,
m3uaRoutingTablesVariablesGroup,
m3uaNaTablesVariablesGroup,
m3uaPcTablesVariablesGroup,
m3uaSpEpVariablesGroup,
m3uaLocAddrTablesVariablesGroup,
m3uaRemAddrTablesVariablesGroup
}
GROUP m3uaStateStatGroup
DESCRIPTION
"The m3ua group of objects to control state changes in the M3UA
protocol."
OBJECT m3uaAssocLocalAddressIPType
SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION
"It is only required to have IPv4 and IPv6 addresses to be
stored since the use of the host names is limited to first
stage, when the association is being established."
OBJECT m3uaAssocLocalAddressIP
SYNTAX InetAddress (SIZE(4|16))
DESCRIPTION
"It is only required to support IPv4 and unique IPv6
addresses."
OBJECT m3uaAssocRemAddressIPType
SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION
"It is only required to have IPv4 and IPv6 addresses to be
stored since the use of the host names is limited to first
stage, when the association is being established."
OBJECT m3uaAssocRemAddressIP
SYNTAX InetAddress (SIZE(4|16))
DESCRIPTION
"It is only required to support IPv4 and unique IPv6
addresses."
::= { m3uaCompliances 1 }
-- 4.1.2 Units of conformance
m3uaGeneralVariablesGroup OBJECT-GROUP
OBJECTS { m3uaProcType, m3uaLocalPort, m3uaTrValue, m3uaTBeatValue,
m3uaTAckValue, m3uaTPaudValue, m3uaSpLshMethod, m3uaStreamLshMethod,
m3uaMaxStreamInbound, m3uaFailOverBuffering, m3uaFailOverBuffSize,
m3uaMaxPeerApplications, m3uaMaxSPperApplications, m3uaHeartBeat,
m3uaVersion
}
STATUS current
DESCRIPTION
"The m3ua group of objects providing for management of M3UA
entities. Common parameters for the protocol."
::= { m3uaGroups 1 }
m3uaStateStatGroup OBJECT-GROUP
OBJECTS { m3uaRoutingFailures
}
STATUS current
DESCRIPTION
"The m3ua group of objects to control state changes in the M3UA
protocol."
::= { m3uaGroups 2 }
m3uaAsTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaAsId, m3uaAsState, m3uaAsTrafficMode,
m3uaAsRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage ASs."
::= { m3uaGroups 3 }
m3uaAspTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaAspAssocId,
m3uaAspState
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage ASPs."
::= { m3uaGroups 4 }
m3uaSpEpTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaSpEpId, m3uaSpEpAssocId,
m3uaSpEpRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage SP Endpoints."
::= { m3uaGroups 5 }
m3uaSgTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaSgId, m3uaSgState, m3uaSgTrafficMode,
m3uaSgRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage SGs."
::= { m3uaGroups 6 }
m3uaSgpTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaSgpState, m3uaSgpAssocId,
m3uaSgpRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage SGPs."
::= { m3uaGroups 7 }
m3uaRoutingTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaNA, m3uaNI, m3uaSI, m3uaOPC,
m3uaDPC, m3uaSSN, m3uaCICmin,
m3uaCICmax, m3uaPeerAppId, m3uaRoutingRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage Routing Tables."
::= { m3uaGroups 8 }
m3uaNaTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaNA, m3uaNaNI, m3uaNaMtp3ProtocolType,
m3uaNaMtp3ProtocolVariant, m3uaNaMtp3ProtocolVersion,
m3uaNaRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage NA Tables."
::= { m3uaGroups 9 }
m3uaPcTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaNaPC,
m3uaNaPcRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage PC Tables."
::= { m3uaGroups 10 }
m3uaSpEpVariablesGroup OBJECT-GROUP
OBJECTS { m3uaSpEpAssocId, m3uaSpEpAssocState, m3uaSpEpAssocRemPort,
m3uaSpEpAssocReqOutStreams, m3uaSpEpAssocOutStreams,
m3uaSpEpAssocIncStreams, m3uaSpEpAssocRemHostName,
m3uaSpEpAssocDataSent, m3uaSpEpAssocDataReceived,
m3uaSpEpAssocAspupSent, m3uaSpEpAssocAspupAckSent,
m3uaSpEpAssocAspacSent, m3uaSpEpAssocAspacAckSent,
m3uaSpEpAssocAspdnSent, m3uaSpEpAssocAspdnAckSent,
m3uaSpEpAssocAspiaSent, m3uaSpEpAssocAspiaAckSent,
m3uaSpEpAssocAspupReceived, m3uaSpEpAssocAspupAckReceived,
m3uaSpEpAssocAspacReceived, m3uaSpEpAssocAspacAckReceived,
m3uaSpEpAssocAspdnReceived, m3uaSpEpAssocAspdnAckReceived,
m3uaSpEpAssocAspiaReceived, m3uaSpEpAssocAspiaAckReceived,
m3uaSpEpAssocNotifySent, m3uaSpEpAssocErrorSent,
m3uaSpEpAssocNotifyReceived, m3uaSpEpAssocErrorReceived,
m3uaSpEpAssocDunaSent, m3uaSpEpAssocDavaSent,
m3uaSpEpAssocSconSent, m3uaSpEpAssocDupuSent,
m3uaSpEpAssocDaudSent, m3uaSpEpAssocDunaReceived,
m3uaSpEpAssocDavaReceived, m3uaSpEpAssocSconReceived,
m3uaSpEpAssocDupuReceived, m3uaSpEpAssocDaudReceived,
m3uaSpEpRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage Assoc. Tables."
::= { m3uaGroups 11 }
m3uaLocAddrTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaAssocLocalAddressIPType, m3uaAssocLocalAddressIP,
m3uaAssocLocalAddressRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage Local IP Address Tables."
::= { m3uaGroups 12 }
m3uaRemAddrTablesVariablesGroup OBJECT-GROUP
OBJECTS { m3uaAssocRemAddressIPType, m3uaAssocRemAddressIP,
m3uaAssocRemAddressRowStatus
}
STATUS current
DESCRIPTION
"The m3ua group of objects to manage Remote IP Address Tables."
::= { m3uaGroups 13 }
END
5. References
[M3UA] G. Sidebottom, L. Ong, Guy Mousseau, K. Gradischnig, H. J.
Schwarzbauer, K. Morneault, I. Rytina, M. Kalla, N. Glaude,
"SS7 MTP3-User Adaptation Layer (M3UA)",
Internet Draft <draft-ietf-sigtran-m3ua-04.txt>,
September 2000.
[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
16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
[RFC2851] Textual Conventions for Internet Network Addresses ,
RFC 2851, June 2000.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, Harvard University, March 1997
6. Security Consideration
There are a number of management objects defined in this MIB that have
a MAX-ACCESS clause of read-write and/or read-create. Such objects may
be considered sensitive or vulnerable in some network environments. The
support for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations.
It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if security measures
are taken (e.g., using IPSEC), there is no per-user control as to who
(once an IPSEC association is established between hosts) is allowed to
GET or SET the objects in this MIB
It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the
User-based Security Model RFC 2574 [RFC2574] and the View-based Access
Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them.
7. Acknowledgments
The author wish to thank Shyamal Prasad, Kurt Kite and Jennifer Jones for
their comments.
8. Authors' Addresses
Antonio Roque Tel: +34-91-339-3523
Ericsson Espana S.A. EMail: Antonio.Roque@ericsson.com
Network Communication Services
Retama 7, 5th floor
Madrid, 28045
Spain
9. Revision History
Changes from pre-draft rev 00 to sigtran-draft rev 00:
- Timer TRtmsn renamed as TAck.
- Added a new object to enable or disable heartbeat.
- New stream inbound/outbound objects added in general variables.
- Timer TPaud ( Periodic audit timer ) added to general variables.
- Counter32 replaced for Counter64 in RoutingFailures object type.
- State "PENDING" added to m3uaAsState object.
- Traffic handling mode removed from ASP table.
- Comments Text in NA Table modified: NA is relevant for ASP, IPSP and SGP.
- Editorial changes.
|
Documentation