13 Monitoring Service Broker

The following sections explain how you can monitor Oracle Communications Service Broker:

Introduction to Service Broker Monitoring
Understanding Service Broker Runtime MBeans
Accessing Service Broker Runtime MBeans
Runtime MBeans Reference
Service Broker Measurements
Understanding Notifications
Registering for Notifications
Identifying Key Performance Indicators
Configuring Service Broker Monitoring
Summary of Service Broker Measurements

Introduction to Service Broker Monitoring

Service Broker monitoring is based on JMX and you can monitor Service Broker using JMX Runtime MBeans. JMX Runtime MBeans are simple Java objects that provide an API to:

Poll values of Service Broker measurements, that is counters, gauges and statuses
Receive notifications when certain events occur

Runtime MBeans is a Java software API based on the standard Java Management eXtensions (JMX). The API provides a machine interface to monitor the activity of each Service Broker module.

Using JMX clients you can monitor any component (that is SSUs, IMs and SMs) in a Service Broker domain.

Understanding Service Broker Runtime MBeans

This section describes the Service Broker Runtime MBeans.

Service Broker Runtime MBeans Organization

Monitoring a Service Broker module involves polling measurements and statuses from a set of MBeans that together provide the module state. Each Service Broker module has a set of Runtime MBeans, which are organized in a hierarchy that includes:

A root MBean that lets you monitor the functionality of the module. For example, the IM-SCF root MBean provides measurement on the number of sessions that the IM-SCF handled successfully or sessions that the IM-SCF handled unsuccessfully. The root MBean also provides references to other Runtime MBeans in the hierarchy.
Other Runtime MBeans, each monitors a component or an interface of the module. For example, the IM-SCF TcapRuntimeMBean provides measurements regarding the TCAP interface.

Figure 13-1 shows an example of the Runtime MBean hierarchy for the IM-SCF CAP phase 1 Interworking Module:

Figure 13-1 Example of the IM-SCF CAP Runtime MBean Hierarchy

Each Runtime MBean provides reference to other Runtime MBeans below in the hierarchy. Therefore, a JMX client can access a Runtime MBean by either directly looking it up in the MBean Server or by browsing down through the Runtime MBean hierarchy.

Service Broker Runtime MBean Instantiation

Each module instance instantiates its own Runtime MBeans on the server where the module instance is running. If Service Broker executes a module instance on more than one server, then the module instance will create several instances of its Runtime MBeans, one on each server. The Runtime MBeans on a server, let you monitor the activity of the module instance running on that specific server.

Figure 13-2 shows an example of how IM-SCF instantiates Runtime MBeans on each of the servers on which IM-SCF is installed.

Figure 13-2 IM-SCF CAP1 Instances

Module instance Runtime MBeans are registered in the MBean server where the module instance is running. Runtime MBeans remain available in the MBean server as long as the module instance that instantiated them is running. When a module instance stops, it also destructs its Runtime MBeans.

Service Broker Runtime MBean Object Names

Runtime MBeans are registered in the MBean Server under an object name of type javax.management.ObjectName. Service Broker naming conventions encode its Runtime MBean object names as follows:

com.convergin:Type=<MBean-type-name>,Version=<version>,Location=<server-name>,Name=<module-instance-name.resource-name>,CountingMethod=<counting_method>

Table 13-1 describes the key properties that Service Broker encodes in its Runtime MBean object names.

Table 13-1 Service Broker MBean Object Name Key Properties

Property	Description
Type=<MBean-type-name>	Specifies a short name of an MBean's type without the postfix "MBean". For example, the Type parameter of LinksetRuntimeMBean is LinksetRuntime.
Location=<server-name>	Specifies a name of a Processing Server or Signaling Server on which the Runtime MBean runs.
Version=<version_number>	Specifies a version of the MBean instance. When you upgrade an MBean to a later version, this parameter enables Service Broker to keep the same name for different versions of the same MBean and use the version number to differentiate between them.
Name=<module-instance-name.resource-id>	Specifies the name of a Runtime MBean which consists of the following keys: <monitor-instance-name>: Name of the module instance that the Runtime MBean monitors <resource-name>: Resource that the Runtime MBean monitors. Possible values of this key depend on the type of an MBean.
CountingMethod=<counting_method>	Specifies how an MBean counts events. You can set <counting_method> to one of the following: CurrentInterval, when you want to get a number of times that a specific event occurred from the beginning of the time interval till the moment when you read the counter PreviousInterval, when you want to get a number of times that a specific event occurred by the end of a previous time interval CurrentGeneral, when you want to get a number of currently occurring events For more information on counting methods, see "Counters, Gauges, TPSs and Statuses".

For example:

com.convergin:Type=MessageByOpRuntime,Version=1.0.0,Location=sb_01, Name=imscfcap4_instance.CAP.InitialDP,CountingMethod=CurrentInterval

Accessing Service Broker Runtime MBeans

Runtime MBeans are located and registered in the MBean Server of Processing Servers and Signaling Servers, where the Service Broker module instances are running.

Remote JMX clients (clients running in a different JVM than the Processing Server or Signaling), can use the javax.management.remote APIs to access any Service Broker MBean server. When accessed from a remote client, a Service Broker MBean Server returns its javax.management.MBeanServerConnection interface, which enables clients to access MBeans.

To monitor a module instance running on a Processing Server or a Signaling Server, a JMX client has to:

Connect to the MBean Server on the server. This is where the Runtime MBeans are registered.
Lookup the Runtime MBeans in the MBean Server.
Use the Runtime MBean interfaces to query counter and status values, and to receive notifications.

Runtime MBeans Reference

The Service Broker Runtime MBeans are described in details in JavaDoc. See Oracle Communications Service Broker Runtime MBeans Javadoc.

Service Broker Measurements

This section describe various aspects of Service Broker measurements.

Counters, Gauges, TPSs and Statuses

Service Broker Runtime MBeans provide the following types of attributes:

Counters

Counters store the number of times a particular event has occurred in the last time interval. For example, a counter can provide the number of messages received in the last 15 minutes interval. The time interval is configurable for each module instance depending on your specific needs. Whenever a time interval ends, Service Broker zeroes a counter.

Figure 13-3 shows how a counter increases and zeroes periodically in the end of each time interval.

Figure 13-3 Typical Counter Graph

Graph showing number of received messages in 15 minutes

Names of counter attributes have the count prefix.

Service Broker provides the following types of counters::

Current interval counters

This type of counters provides a number of times that a specific event occurred from the beginning of the time interval till the moment when you read the counter. You can check how much time elapsed since the beginning of the current time interval using WcsUptimeMBean.

To make a counter to act as a current interval counter, create an instance of an MBean and set the CountingMethod property of the MBean object name to CurrentInterval.
Previous interval counters

This type of counters provides a number of times that a specific event occurred by the end of a previous time interval.

To make a counter to act as a previous interval counter, create an instance of an MBean and set the CountingMethod property of the MBean object name to PreviousInterval.

Figure 13-4 shows an example of a current interval counter compared to a previous interval counter.

Figure 13-4 Current Interval Counter

Graph showing current intervals readings.

Note:

You need to access different instances of an MBean for each type of counter. The two MBean instances differ by the CountingMethod property of their object name. The value of the CountingMethod of one instance is CurrentInterval and of the second instance is PreviousInterval.

TPSs

TPSs are special counters whose time interval is non-configurable and preset to a very short duration of 15 seconds. There are only a few TPS counters. All of them have been identified as the most important Service Broker counters, which are critical to monitor Service Broker performance.

Names of TPS attributes have the count prefix. However, as opposed to regular counter attributes, TPS counters are available in MBean instances whose CountingMethod property is set to ShortInterval.

Gauges

Gauges store a number measured at a given moment. For example, the number of currently active sessions.

Figure 13-5 shows how a gauge's value changes over time.

Figure 13-5 Typical Gauge Graph

Names of gauge attributes have the gauge prefix. Gauge attributes are available in MBean instances whose CountingMethod property equals CurrentGeneral.

Statuses

Statuses are attributes that indicate a state of a resource. For example, a status can provide information about a current state of an SS7 point code.

Module-Level Measurements and Tier-Level Measurements

Runtime MBeans can provide measurements described in "Service Broker Measurements" on the following levels:

Module

When a Service Broker module loads, Service Broker creates runtime MBeans for this module. Counters and gauges of runtime MBeans provide information about the module for which the MBeans were created. For example, when IM-SCF CAP1 loads, Service Broker creates runtime MBeans for monitoring the TCAP and CAP interfaces of the module. These MBeans contains counters and gauges that gather information about sessions and operations handled by IM-SCF CAP1.
Tier

To provide measurements on how an entire tier functions, Service Broker provides the runtime MBean that contains counters and gauges for gathering information related to the tier rather than to individual modules. For example, SystemCountersRuntimeMBean provides a counter that indicates the number of sessions opened in the last period in the Processing Tier.

Understanding Notifications

Service Broker notifications are based on Service Broker counters, gauges, TPSs and status attributes as described in "Service Broker Measurements". You can specify criteria for each Runtime MBean attribute (that is counter, gauge, TPS or status) that cause Service Broker to invoke a notification when each criteria is met.

In general, the notification mechanism involves the following steps:

An attribute value changes and reaches a criteria that was specified
The Runtime MBean invokes a notification.
The attribute value changes again and the criteria is not met any longer.
The Runtime MBean clears the previously sent notification by invoking a cease notification.

Notifications are triggered by the Runtime MBean whose attribute is being monitored.

"Specifying Notification Criteria for Counters and TPSs" and "Specifying Notification Criteria for Gauges" explain how thresholds define reporting and clearance of a notification for counters and gauges.

Specifying Notification Criteria for Counters and TPSs

Counters store the number of times a particular event has occurred in the last time interval. For example, a counter can measure the number of InitialDP operations received in the last 15 minutes. See "Counters".

Table 13-2 explains how reaching an upper threshold or a lower threshold causes reporting and clearing of a notification.

Table 13-2 Reporting and Clearing Notifications for Counters

Threshold	Notification Sent When...	Notification Cleared When...
Upper	The counter crosses the upper threshold.	The counter does not reach the upper threshold by the end of the last time interval
Lower	The counter does not cross the lower threshold by the end of the last time interval	The counter crosses up the lower threshold by the end of the last time interval

Specifying Notification Criteria for Gauges

Gauges are MBean attributes that provide a measurement at a given moment. For example, a gauge can contain a number of currently active sessions. See "Gauges".

Table 13-3 explains how reaching an upper threshold or a lower threshold causes reporting and clearing of a notification.

Table 13-3 Reporting and Clearing Notifications for Gauges

Threshold	Notification Sent When...	Notification Cleared When...
Upper	The increasing gauge crosses the upper threshold.	The decreasing gauge crosses the threshold ceased value.
Lower	The decreasing gauge crosses the lower threshold.	The increasing gauge crosses the threshold ceased value.

Specifying Notification Criteria for Statuses

Statuses are MBean attributes that indicate a state of a module. Service Broker triggers a notification when the value of an attribute changes to a certain value.

For example, SsuRemotePointCodeRuntimeMBean has the Status attribute that indicates availability of a point code. To monitor this attribute, you can define that Service Broker triggers a notification when the value of the Status attribute changes and indicates that the remote point becomes unavailable.

Table 13-4 explains how entering a specified state and exiting a state causes reporting and clearing of a notification.

Table 13-4 Reporting and Clearing Notifications for Statuses

Notification Sent When...	Notification Cleared When...
A monitored attribute changes to a specified state	A monitored attribute changes again to a state other than a specified state.

Notification Structure

The Service Broker notification mechanism is based on javax.management.Notification and javax.management.AttributeChangeNotification Java classes.

These Java classes contain the following fields:

Source

The ObjectName of a Runtime MBean that sent the notification
Sequence number

This number allows individual notifications to be identified by a receiver
Message

Provides detailed textual description of a notification

Type

The type conveys the semantics of the notification in the following format: <rmb>.<attr>.<class>, where:

<rmb> defines a type of the runtime MBean that triggers a notification
<attr> defines an attribute of a runtime MBean whose change triggers the notification

<class> defines a type of the change that triggers the notification. Table 13-5 describes notification classes that can be defined in the Type field.

Table 13-5 Notification Class Values

Class	Description
High	A runtime MBean counter or gauge crosses an upper threshold
Low	A runtime MBean counter or gauge crosses a lower threshold
Attribute.changed	A value of a runtime MBean attribute changed
Ceased	A previous notification is cleared

Time

This specifies the time when the event which triggered the notification, occurred
UserData

This specifies additional data that the runtime MBean that triggers the notification wants to communicate.

The UserData field can contain any data that a runtime MBean which sends a notification, wants to communicate to a receiver. This field contains tag-value pairs separated by the semicolon.

The following tags are allowed:
- OriginNotificationSeqNum, which is used by a clearing notification to enable matching with the original notification that was cleared. In the clearing notification, this tag is set to the sequence number of the cleared notification. For more information, see "Receiving Notification Clearing".
- LowThreshold, which is set to the crossed value of the lower threshold when the notification class set to ""low" is triggered
- HighThreshold, which is set to the crossed value of the upper threshold when the notification class is set to "high" is triggered
- Match, which is set to the matched value when the notification class set to "match" is triggered
- Differs, which is set to the value with which an attribute value was compared when the notification class set to "differs" is triggered

Receiving Notification Clearing

A runtime MBean clears a notification when criteria described in "Specifying Notification Criteria for Counters and TPSs" and "Specifying Notification Criteria for Gauges" are met.

To enable a notification receiver to recognize which original notification needs to be cleared, a runtime MBean uses the following methods:

The OriginNotificationSeqNum tag in the UserData field of a clearing notification contains the sequence number of the original notification to be cleared.
The Source field of the clearing notification contains the same value as the Source field of the original notification to be cleared.
Clearing notifications contain the "ceased" postfix in the Type field. For example: Type=ImscfCapRuntimeMBean.SessionGauge.ceased.

Registering for Notifications

You can register for notifications using any JMX client. If you want to receive notifications from several MBeans, you need to register for each MBean separately.

The following explains how to register for notifications using JConsole:

Start JConsole.
Click the MBeans tab. The tree view of MBeans is displayed.
On the tree view pane, select the MBean for which you want to register.
Under the selected MBean, select Notifications. The Notification Buffer is displayed on the main pane.
Click Subscribe.

The registration created. When an event occurs, the notification is displayed in the Notification Buffer. You can clear the Notification Buffer at any time by clicking Clear.

Identifying Key Performance Indicators

Key performance indicators are measurements (counters, gauges, TPSs and statuses) that you monitor in order to asses the state and performance of your system.

Depending on your system and the modules installed in your system, you have to identify the measurements that will best serve the evaluation of your system. For the summary of available Service Broker measurements see "Summary of Service Broker Measurements".

Use the Administration Console to configure the Monitoring tab of each module instance in your system. Define notifications that Service Broker will invoke, based on key performance indicators that you selected.

Set your NMS to monitor key performance indicators by either periodically polling the values of these measurements or register to notifications that you specified.

Configuring Service Broker Monitoring

For detailed description on how you can configure the monitoring functionality in the module and tier level, see Configuring Service Broker Monitoring in Oracle Communications Service Broker Configuration Guide.

Summary of Service Broker Measurements

This section summarizes measurements that you can take to monitor activity of Service Broker and individual Service Broker's modules.

Monitoring Common Interfaces

The following sections provide reference information on attributes of Runtime MBeans that enable you to monitor interfaces which are common for IMs.

Monitoring the TCAP Interface

Table 13-6 describes attributes that enable you to monitor the TCAP interface.

Table 13-6 TCAP Interface Monitoring Attributes

Attribute	Description	Type	MBean
AppInitiatedTransCount	Returns the number of currently opened applications that initiated TCAP Transactions	Counter	TcapRuntimeMBean
DestroyTransactionCount	Returns the number of TCAP transactions that have been closed on the module in the last measurement period	Counter	TcapRuntimeMBean
NetworkInitiatedTrans Count	Returns the number of currently opened TCAP transactions initiated by the network	Counter	TcapRuntimeMBean
TransactionCount	Returns the total number of TCAP transactions that a module handled in the last measurement period	Counter	TcapRuntimeMBean
AbnormalDialogueCount	Returns the number of P-ABORT messages received from the network with the Reason header set to 'No Common Dialogue Portion	Counter	TcapPAbortCountRuntimeMBean
BadlyFormattedTransactionPortionCount		Counter	TcapPAbortCountRuntimeMBean
IncorrectTransactionPortionCount	Returns the number of TC-P-ABORT messages that a module received received from a network with the Reason header set to 'Incorrect Transaction Portion' in the last measurement period	Counter	TcapPAbortCountRuntimeMBean
NoCommonDialoguePortionCount	Returns the number of the number of TC-P-ABORT messages that a module received from a network with the Reason header set to 'No Common Dialogue Portion' in the last measurement period	Counter	TcapPAbortCountRuntimeMBean
ResourceLimitationCount	Returns the number of TC-P-ABORT messages that a module received received from a network with the Reason header set to 'Resource Limitation' in the last measurement period	Counter	TcapPAbortCountRuntimeMBean
UnrecognizedMessageTypeCount	Returns the number of TC-P-ABORT messages that a module received from a network with the Reason header set to 'Unrecognized Message Type' in the last measurement period	Counter	TcapPAbortCountRuntimeMBean
UnrecognizedTransactionIDCount	Returns the number of TC-P-ABORT messages that a module received received from a network with the Reason header set to 'Unrecognized Transaction ID' in the last measurement period	Counter	TcapPAbortCountRuntimeMBean
ReceiveFailedCount	Returns the number of messages that a module received but failed to process successfully in the last measurement period	Counter	TcapMessageCount RuntimeMBean
ReceiveSuccessCount	Returns the number of messages that a module received and processed successfully in the last measurement period	Counter	TcapMessageCount RuntimeMBean
SentFailedCount	Returns the number of messages that a module failed to send to the SS7 network in the last measurement period	Counter	TcapMessageCount RuntimeMBean
SentSuccessCount	Returns the number of messages that a module successfully sent to the SS7 network in the last measurement period.	Counter	TcapMessageCount RuntimeMBean
ComponentInvokeTimer Expiry Count	Returns the Invoke component timer expiry count	Counter	TcapComponentRuntimeMBean
ComponentRejectTimer ExpiryCount	Returns the Reject component timer expiry count	Counter	TcapComponentRuntimeMBean
ReceivedErrorCount	Returns the number of TCAP Error components that a module received from the network in the last measurement period	Counter	TcapComponentRuntimeMBean
ReceivedInvokeCount	Returns the number of TCAP Invoke components that a module received from the network in the last measurement period	Counter	TcapComponentRuntimeMBean
ReceivedResultLCount	Returns the number of TCAP ResultL components that a module received from the network in the last measurement period	Counter	TcapComponentRuntimeMBean
ReceivedResultNLCount	Returns the number of TCAP ResultNL components that a module received from the network in the last measurement period	Counter	TcapComponentRuntimeMBean
ReceivedTimerResetCount	Returns the number of received TCAP TimerReset components that a module received from the network in the last measurement period	Counter	TcapComponentRuntimeMBean
ReceivedUCancelCount	Returns the number of TCAP UCancel components that a module received from the network in the last measurement period	Counter	TcapComponentRuntimeMBean
ReceivedURejectCount	Returns the number of U-REJECT components that a module received from the network in the last measurement period	Counter	TcapComponentRuntimeMBean
SentErrorCount	Returns the number of TCAP Error components that a module sent to the network in the last measurement period	Counter	TcapComponentRuntimeMBean
SentInvokeCount	Returns the number of TCAP Invoke components that a module sent to the network in the last measurement period	Counter	TcapComponentRuntimeMBean
SentLRejectCount	Returns the number of TCAP LReject components that a module sent to the network in the last measurement period	Counter	TcapComponentRuntimeMBean
SentResultNLCount	Returns the number of TCAP ResultNL components that a module sent to the network in the last measurement period	Counter	TcapComponentRuntimeMBean
SentRRejectCount	Returns the number of TCAP RReject components that a module sent to the network in the last measurement period	Counter	TcapComponentRuntimeMBean

Monitoring the IN INterface

Table 13-7 describes attributes that enable you to monitor the IN interface.

Table 13-7 IN INterface Monitoring Attributes

Attribute	Description	Type	MBean
NetworkInitiatedDialog Count	Returns the number of non-module-initiated dialogs that a module handled in the last measurement period	Counter	DialogRuntimeMBean
NetworkInitiatedDialog Gauge	Returns the number of currently opened dialogs initiated by the network	Counter	NOT IMPLEMENTED
ServiceInitiatedDialog Count	Returns the number of dialogs that a module initiated and handled in the last measurement period	Counter	DialogRuntimeMBean
ServiceInitiatedDialog Gauge	Returns the number of currently opened dialogs initiated by a service	Counter	NOT IMPLEMENTED
RcvCount	Returns the number of messages that a module received from the network in the last measurement period	Counter	MessageRuntimeMBean
SndCount	Returns the number of messages that a module sent to the network in the last measurement period	Counter	MessageRuntimeMBean

Monitoring the Diameter Interface

Table 13-8 describes attributes that enable you to monitor the Diameter interface

Table 13-8 Diameter Monitoring Attributes

Attribute	Description	Type	MBean
CcaCount	Returns the total number of CCAs that a module sent and received	Counter	RoRuntimeMBean
CcrCalledInitiatorCount	Returns the number of Credit-Control-Requests (CCRs) received with the Media-Initiator-Flag AVP set to CalledParty	Counter	RoRuntimeMBean
CcrCallingInitiatorCount	Returns the number of Credit-Control-Requests (CCRs) received with the Media-Initiator-Flag AVP set to CallingParty	Counter	RoRuntimeMBean
CcrCount	Returns the total number of Credit-Control-Requests (CCRs) that a module sent and received in the last measurement period	Counter	RoRuntimeMBean
CcrUnknownInitiator Count	Returns the number of Credit-Control-Requests (CCRs) received with the Media-Initiator-Flag AVP set to Unknown	Counter	RoRuntimeMBean
EcurSessionCount	Returns the number of Event Charging with Unit Reservation (ECUR) sessions that a module handled in the last measurement period	Counter	RoRuntimeMBean
ErrorCcaCount	Returns the total number of CCAs with an error result that a module sent and received	Counter	RoRuntimeMBean
IecSessionCount	Returns the number of Immediate Event Charging (IEC) sessions that a module handled in the last measurement period	Counter	RoRuntimeMBean
ScurInitialCcrCount	Returns the number of Initial Credit Control Requests (CCRs) that a module sent and received in the last measurement period	Counter	RoRuntimeMBean
ScurSessionCount	Returns the number of Session Charging with Unit Reservation (SCUR) sessions that a module handled in the last measurement period	Counter	RoRuntimeMBean
ScurTerminateCcrCount	Returns the number of Terminate Credit Control Requests (CCRs) that a module sent and received in the last measurement period	Counter	RoRuntimeMBean
ScurUpdateCcrCount	Returns the number of Update Credit Control Requests (CCRs) that a module sent and received in the last measurement period	Counter	RoRuntimeMBean
SuccessCcaCount	Returns the total number of CCAs with a successful result that a module sent and received	Counter	RoRuntimeMBean
AnsCount	Returns the number of Diameter answers that a module sent and received	Counter	DiameterRuntimeMBean
RequestCount	Returns the number of Diameter requests that a module sent and received	Counter	DiameterRuntimeMBean

Monitoring the SIP Interface

Table 13-9 describes attributes that enable you to monitor the SIP interface

Table 13-9 SIP Interface Monitoring Attributes

Attribute	Description	Type	MBean
SessionCount	Returns the total number of SIP sessions handled in the last measurement period	Counter	SipRuntimeMBean
SessionGauge	Returns the number of SIP sessions that a module is currently handling	Gauge	NOT IMPLEMENTED
RcvCount	Returns the total number of SIP requests that a module received from the network	Counter	SipRequestRuntime MBean SipRequestByMethod RuntimeMBean SipResponseByRequest MethodRuntimeMBean
SndCount	Returns the total number of SIP requests that a module sent to the network	Counter	SipRequestRuntime MBean SipRequestByMethod RuntimeMBean SipResponseByRequest MethodRuntimeMBean

Monitoring Service Broker's Modules

The following sections provide reference information on attributes of Runtime MBeans that enable you to monitor Service Broker's individual modules.

Monitoring the Processing Tier

Table 13-10 describes attributes that enable you to monitor the Service Broker Processing Tier.

Table 13-10 Processing Titer Monitoring Attributes

Attribute	Description	Type	MBean
InitialRequestCount	Specifies the number of sessions opened in the Processing Server in the last measurement period	Counter	SystemCountersRuntimeMBean
SessionGauge	Specifies the number of currently opened sessions in the Processing Server	Gauge	SystemGaugeRuntime MBean

Monitoring SS7 SSU

Table 13-11 describes attributes that enable you to monitor SS7 SSU.

Table 13-11 SS7 SSU Monitoring Attributes

Attribute	Description	Type	MBean
Status	Specifies the point code status. Possible values: 1 - Inaccessible 2 - Congested 3 - Accessible	Status	SsuLocalPointCode RuntimeMBean
InService	Returns a subsystem status	Status	SsuLocalSubSystem RuntimeMBean
Status	Specifies a point code status. Possible values for TDM: 1 - Remote SCCP is available 2 - Remote SCCP is unavailable, reason unknown 3 - Remote SCCP is unequipped 4 - Remote SCCP is inaccessible 5 - Remote SCCP is congested Possible values for SIGTRAN: 0 - Remote SCCP is accessible 1 - Remote SCCP is inaccessible	Status	SsuRemotePointCode RuntimeMBean

Attribute

Description

Type

MBean

Status

Specifies the point code status. Possible values:

1 - Inaccessible
2 - Congested
3 - Accessible

Status

SsuLocalPointCode RuntimeMBean

InService

Returns a subsystem status

Status

SsuLocalSubSystem RuntimeMBean

Status

Specifies a point code status. Possible values for TDM:

1 - Remote SCCP is available
2 - Remote SCCP is unavailable, reason unknown
3 - Remote SCCP is unequipped
4 - Remote SCCP is inaccessible
5 - Remote SCCP is congested

Possible values for SIGTRAN:

0 - Remote SCCP is accessible
1 - Remote SCCP is inaccessible

Status

SsuRemotePointCode RuntimeMBean

Monitoring SIP SSU

Table 13-12 describes attributes that enable you to monitor the SIP SSU.

Table 13-12 SIP SSU Monitoring Attributes

Attribute	Description	Type	MBean
Status	Specifies the status of a SIP network entity. Possible values: Active Inactive	Status	NetworkEntityRuntime MBean

Attribute

Description

Type

MBean

Status

Specifies the status of a SIP network entity. Possible values:

Active
Inactive

Status

NetworkEntityRuntime MBean

Monitoring the Orchestration Engine

Table 13-13 describes attributes that enable you to monitor the OE.

Table 13-13 Orchestration Engine Monitoring Attributes

Attribute	Description	Type	MBean
SessionCount	Returns the total number of sessions that the OE handled in the last measurement period	Counter	OeRuntimeMBean
SessionGauge	Returns the number of SIP sessions that the OE is currently handling	Gauge	NOT IMPLEMENTED
SuccessfulApplication TriggeringCount	Returns the number of successful application triggering that the OE performed in the last measurement period	Counter	OeRuntimeMBean
UnsuccessfulApplication TriggeringCount	Returns the number of unsuccessful application triggering that the OE attempted to perform in the last measurement period	Counter	OeRuntimeMBean
ExecutionCount	Returns the number of times that the OE triggered the specific OLP in the last measurement period	Counter	OlpRuntimeMBean
SuccessfulQueryCount	Returns the number of successful queries that an OPR executed in the last measurement period	Counter	OprRuntimeMBean
UnsuccessfulQueryCount	Returns the number of unsuccessful queries that an OPR attempted to execute in the last measurement period	Counter	OprRuntimeMBean

Monitoring IM-SCF

You can monitor the following interfaces of IM-SCF:

CAP
INAP CS-1
WIN
AIN
TCAP

Table 13-14 describes attributes that enable you to monitor the CAP, INAP CS-1, WIN, and AIN interfaces of IM-SCF. For more information on monitoring the TCAP interface, see "Monitoring the TCAP Interface".

Table 13-14 IM-SCF Monitoring Attributes

Attribute	Description	Type	MBean
FullControlCount	Returns the number of fully controlled sessions that IM-SCF handled in the last measurement period. Full control means that IM-SCF handled the session during the session setup and continues to handle this session after the session is established.	Counter	ImscfCapRuntimeMBean ImscfWinRuntimeMBean ImscfInapCs1Runtime MBean ImscfAinRuntimeMBean
InitialControlCount	Returns the number of non-fully controlled sessions. Non-full control means that IM-SCF handled the session only during the session setup.	Counter	ImscfCapRuntimeMBean ImscfWinRuntimeMBean ImscfInapCs1Runtime MBean ImscfAinRuntimeMBean
SessionCount	Returns the total number of sessions that IM-SCF handled in last measurement period	Counter	ImscfCapRuntimeMBean ImscfWinRuntimeMBean ImscfInapCs1Runtime MBean ImscfAinRuntimeMBean
SessionGauge	Returns the total number of sessions that IM-SCF is currently handling	Counter	NOT IMPLEMENTED
RcvCount	Returns the number of messages that IM-SCF received from the network in the last measurement period.	Counter	MessageByOpRuntime MBean InitialDpByEventType RuntimeMBean ErbByEventTypeRuntimeMBean InitialDpByServiceKey RuntimeMBean InitialDpSmsByService KeyRuntimeMBean
SndCount	Returns the number of messages that IM-SCF sent to the network in the last measurement period.	Counter	MessageByOpRuntime MBean InitialDpByEventType RuntimeMBean ErbByEventTypeRuntimeMBean InitialDpByServiceKey RuntimeMBean InitialDpSmsByService KeyRuntimeMBean

Monitoring IM-SSF

You can monitor the following interfaces of IM-SSF:

CAP
INAP CS-1
WIN
AIN
TCAP

Table 13-15 describes attributes that enable you to monitor the CAP, INAP CS-1, WIN, and AIN interfaces of IM-SSF. For more information on monitoring the TCAP interface, see "Monitoring the TCAP Interface".

Table 13-15 IM-SSF Monitoring Attributes

Attribute	Description	Type	MBean
FullControlCount	Returns the number of fully controlled sessions that IM-SSF handled in the last measurement period. Full control means that IM-SSF handled the session during the session setup and continues to handle this session after the session is established.	Counter	ImssfCapRuntimeMBean ImssfWinRuntimeMBean ImssfInapCs1Runtime MBean ImssfAinRuntimeMBean
InitialControlCount	Returns the number of non-fully controlled sessions. Non-full control means that IM-SSF handled the session during the session setup only.	Counter	ImssfCapRuntimeMBean ImssfWinRuntimeMBean ImssfInapCs1Runtime MBean ImssfAinRuntimeMBean
SessionCount	Returns the total number of sessions that IM-SSF handled in last measurement period	Counter	ImssfCapRuntimeMBean ImssfWinRuntimeMBean ImssfInapCs1Runtime MBean ImssfAinRuntimeMBean
SessionGauge	Returns the total number of sessions that IM-SSF CAP is currently handling	Gauge	NOT IMPLEMENTED
UserInteractionCount	Returns the number of sessions that included interaction with a media resource	Counter	ImssfCapRuntimeMBean
TssfExpiryCount	Returns the number of times that Tssf expired	Counter	ImssfCapRuntimeMBean
OSideSessionCount	Returns the number of sessions that triggered a service on the O-side	Counter	ImssfCapRuntimeMBean
TSideSessionCount	Returns the number of sessions that triggered a service on the T-side	Counter	ImssfCapRuntimeMBean
RcvCount	Returns the number of messages that IM-SSF received from the network in the last measurement period.	Counter	MessageByOpRuntimeMBean InitialDpByEventType RuntimeMBean ErbByEventTypeRuntimeMBean InitialDpByServiceKey RuntimeMBean InitialDpSmsByService KeyRuntimeMBean
SndCount	Specifies the number of messages that IM-SSF sent to the network in the last measurement period.	Counter	MessageByOpRuntime MBean InitialDpByEventType RuntimeMBean ErbByEventTypeRuntimeMBean InitialDpByServiceKey RuntimeMBean InitialDpSmsByService KeyRuntimeMBean

Monitoring IM-ASF

Table 13-16 describes attributes that enable you to monitor IM-ASF.

Table 13-16 IM-ASF Monitoring Attributes

Attribute	Description	Type	MBean
SessionCount	Returns the number of sessions that IM-ASF SIP handled	Counter	ImasfSipRuntimeMBean

Monitoring R-IM-ASF

Table 13-17 describes attributes that enable you to monitor R-IM-ASF.

Table 13-17 R-IM-ASF Monitoring Attributes

Attribute	Description	Type	MBean
SessionCount	Returns the number of sessions that R-IM-ASF SIP handled	Counter	RimasfSipRuntimeMBean

Monitoring IM-OCF

You can monitor the following:

Root ImocfRuntimeMBean
Diameter interface

Table 13-18 describes attributes that enable you to monitor the root ImocfRuntimeMBean. For more information on monitoring the Diameter interface, see "Monitoring the Diameter Interface".

Table 13-18 IM-OCF Monitoring Attributes

Attribute	Description	Type	MBean
SessionCount	Returns the number of sessions that IM-OCF handled	Counter	ImocfRuntimeMBean
SessionGauge	Returns the number of sessions that IM-OCF is currently handling	Gauge	NOT IMPLEMENTED
AbandonSessionCount	Returns the number of session establishing attempts that were abandoned by a user during setup in the last measurement period	Counter	ImocfRuntimeMBean
AverageCallDuration	Returns the average call duration in the im-ocf	Counter	NOT IMPLEMENTED
ErrorSessionCount	Returns the number of attempt session establishment that failed during setup in the last measurement period	Counter	NOT IMPLEMENTED
ServiceNotApproved SessionCount	Returns the number of attempt session establishment that were not approved by the service (no credit) in the last measurement period	Counter	NOT IMPLEMENTED
UserTerminatedSession Count	Returns the number of established sessions that were terminated by one of the users in the last measurement period	Counter	ImocfRuntimeMBean
ServiceTerminatedSession Count	Returns the number of established sessions that were terminated by the service in the last measurement period	Counter	ImocfRuntimeMBean

Monitoring R-IM-OCF

You can monitor the following:

Root ImocfRuntimeMBean
Diameter interface

Table 13-19 describes attributes that enable you to monitor the root RimocfRuntimeMBean. For more information on monitoring the Diameter interface, see "Monitoring the Diameter Interface".

Table 13-19 R-IM-OCF Monitoring Attributes

Attribute	Description	Type	MBean
SessionCount	Returns the number of sessions that R-IM-OCF handled in the last measurement period	Counter	RimocfRuntimeMBean
SessionGauge	Returns the number of sessions that R-IM-OCF is currently handling	Gauge	RimocfRuntimeMBean
AbandonSessionCount	Returns the number of session establishing attempts that were abandoned by a user during setup in the last measurement period	Counter	RimocfRuntimeMBean
UserTerminatedSession Count	Returns the number of established sessions that were terminated by one of the users in the last measurement period	Counter	RimocfRuntimeMBean
ServiceTerminatedSession Count	Returns the number of established sessions that were terminated by the service in the last measurement period	Counter	RimocfRuntimeMBean

Monitoring IM-PSX

You can monitor the following interfaces of IM-PSX:

MAP (for GSM networks) or ANSI-MAP (for CDMA networks)
TCAP

Table 13-20 describes attributes that enable you to monitor the MAP interface. For more information on monitoring the TCAP interface, see "Monitoring the TCAP Interface".

Table 13-20 IM-PSX Monitoring Attributes

Attribute	Description	Type	MBean
NetworkInitiatedDialog Count	Returns the number of non-module-initiated dialogs that the module handled in the last measurement period	Counter	DialogRuntimeMBean
ServiceInitiatedDialog Count	Returns the number of dialogs that a module initiated and handled in the last measurement period	Counter	DialogRuntimeMBean
RcvCount	Returns the number of messages that a module received from the network in the last measurement period	Counter	MessageRuntimeMBean
SndCount	Returns the number of messages that a module sent to the network in the last measurement period	Counter	MessageRuntimeMBean MessageByOpRuntimeMBean

Monitoring SM-PME

Table 13-21 describes attributes that enable you to monitor the IN interface

Table 13-21 SM-PME Monitoring Attributes

Attribute	Description	Type	MBean
successfulMappingCount	Specifies the number of successful mapping executed	Counter	PmeRuntimeMBean
failMappingCount	Specifies the number of failed mapping	Counter	PmeRuntimeMBean