11 Monitoring Online Mediation Controller

This chapter describes how to monitor Oracle Communications Online Mediation Controller.

About Monitoring Online Mediation Controller

You can monitor how Online Mediation Controller operates by receiving the following information:

• Statistics on messages and sessions that Interworking Modules (IMs) and the Orchestration Engine (OE) handle. See "Monitoring the Processing Domain" for more information.

• Status of the network entities with which Signaling Server Units (SSUs) communicate. See "Monitoring the Signaling Domain" for more information.

• Availability of the Diameter and RADIUS ports. See "Checking Availability of the Diameter and RADIUS Ports" for more information.

Monitoring the Processing Domain

A deployment of Online Mediation Controller might involve the following components:

• OE

• In online charging solutions:

  • IM-OCF, which communicates with an online charging system

  • R-IM-OCF, which communicates with the network

• In offline charging solutions:

  • IM-OFCF PCP, which communicates with an offline charging system

  • R-IM-OFCF, which communicates with the network

Using runtime MBeans, you can gather statistics on sessions and messages that these IMs send and receive through their interfaces:

• Base Diameter. See "Monitoring the Base Diameter Interface" for more information.

• Diameter Ro (online charging). See "Monitoring the Interfaces in Online Charging Solutions" for more information.

• Diameter Rf (offline charging). See "Monitoring the Interfaces in Offline Charging Solutions" for more information.

Monitoring the Base Diameter Interface

Both online charging and offline charging IMs provide the base Diameter interface. Using DiameterRuntimeMBean, you can get statistics on messages that the IM sent and received through this interface.

Online Mediation Controller creates a separate instance of DiameterRuntimeMBean for each instance of IM-OCF, R-IM-OCF, IM-OFCF, and R-IM-OFCF.

The object name of this MBean is com.convergin:Type=DiameterRuntime,Version=MBean_Version,Location=<server-name>,Name=IM_Instance_Name.Diameter.

Table 11-1 describes the counters that DiameterRuntimeMBean provides.

Table 11-1 DiameterRuntimeMBean Counters

To Get Total Number of...	Use...
Sent and received answers	getAnsCount()
Sent and received requests	getRequestCount()

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Monitoring the Interfaces in Online Charging Solutions

In an online charging solution, IM-OCF and R-IM-OCF provide the Diameter Ro interface. You can get the following statistics on messages that the IM sent and received through this interface:

• Counters of Diameter Ro charging requests and charging answers. See "Getting Statistics on Charging Requests and Charging Answers" for more information.

• Gauge for Diameter Ro sessions. See "Getting Statistics on Currently Active Sessions" for more information.

Getting Statistics on Charging Requests and Charging Answers

Using RoRuntimeMBean, you can get counters of charging requests and charging answers that IM-OCF or R-IM-OCF sent and received.

Online Mediation Controller creates a separate instance of RoRuntimeMBean for each instance of IM-OCF and R-IM-OCF.

The object name of this MBean is com.convergin:Type=RoRuntime,Version=MBean_Version,Location=<server-name>,Name=IM_Instance_Name.Ro.

Table 11-2 describes the counters that RoRuntimeMBean provides.

Table 11-2 RoRuntimeMBean Counters

To Get Total Number of...	Use...
Session Charging with Unit Reservation (SCUR) and Event Charging with Unit Reservation (ECUR) sessions that the IM handled	getChargingWithUnitReservationSessionCount()
Immediate Event Charging (IEC) sessions that the IM handled	getIecSessionCount()
Sent and received Credit-Control-Requests (CCRs)	getCcrCount()
CCRs sent and received with the Media-Initiator-Flag AVP set to CalledParty	getCcrCalledInitiatorCount()
CCRs sent and received with the Media-Initiator-Flag AVP set to CallingParty	getCcrCallingInitiatorCount()
CCRs sent and received with the Media-Initiator-Flag AVP set to Unknown	getCcrUnknownInitiatorCount()
Sent and received Credit Control Answers (CCAs)	getCcaCount()
Sent and received CCAs with a successful result	getSuccessCcaCount()
Sent and received CCAs with an error result	getErrorCcaCount()
Sent and received Initial requests	getInitialRequestCount()
Sent and received Update CCRs	getUpdateRequestCount()
Sent and received Terminate CCRs	getTerminateRequestCount()
Sent and received Event CCRs	getImmediateRequestCount()
Successfully completed sessions	getCompleteSessionCount()
Error sessions	getErrorSessionCount()
Blocked sessions, that is the number of sessions terminated with the result code 4012	getBlockedSessionCount()
Redirected sessions, that is the number of CCAs with the Final-Unit-Action AVP set to Redirect.	getRedirectedSessionCount()

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on Currently Active Sessions

Using RoGaugeRuntimeMBean, you can get the gauge of sessions that IM-OCF or IM-OCF is currently handling.

Online Mediation Controller creates a separate instance of RoGaugeRuntimeMBean for each instance of IM-OCF and R-IM-OCF.

The object name of this MBean is com.convergin:Type=RoGaugeRuntime,Version=MBean_Version,Location=<server-name>,Name=IM_Instance_Name.Ro.

Table 11-3 describes the gauge that RoGaugeRuntimeMBean provides.

Table 11-3 RoGaugeRuntimeMBean Gauge

To Get Total Number of...	Use...
Currently active sessions	getActiveSessionsGauge()

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Monitoring the Interfaces in Offline Charging Solutions

In an offline charging solution, IM-OFCF PCP and R-IM-OFCF RADIUS provide the Rf interface.

You can get the following statistics on messages that the IM sent and received through this interface:

• Counters of Diameter Rf accounting requests and accounting answers. See "Getting Statistics on Accounting Requests and Accounting Answers" for more information.

• Gauge for Diameter Rf sessions. See "Getting Statistics on Currently Active Sessions" for more information.

Getting Statistics on Accounting Requests and Accounting Answers

Using RfRuntimeMBean, you can get statistics on accounting requests and accounting answers that IM-OFCF PCP or R-IM-OFCF RADIUS sent and received.

Online Mediation Controller creates a separate instance of RfRuntimeMBean for each instance of IM-OFCF PCP and R-IM-OFCF PCP.

The object name of this MBean is com.convergin:Type=RfRuntime,Version=MBean_Version,Location=<server-name>,Name=IM_Instance_Name.Rf.

Table 11-4 describes the counters that RfRuntimeMBean provides.

Table 11-4 RfRuntimeMBean Counters

To Get Total Number of...	Use...
Sessions handled by the IM	getSessionCount()
Sent and received Accounting Requests (ACR)	getAcrCount()
ACRs sent and received with the Accounting-Record-Type AVP set to START-RECORD	getStartAcrCount()
ACRs sent and received with the Accounting-Record-Type AVP set to INTERIM_RECORD	getInterimAcrCount()
ACRs sent and received with the Accounting-Record-Type AVP set to STOP_RECORD	getStopAcrCount()
ACRs sent and received with the Accounting-Record-Type AVP set to EVENT_RECORD	getEventAcrCount()
Sent and received Accounting Answers (ACAs)	getAcaCount()
ACAs sent and received with the Result-Code AVP < 3000 (success)	getAcaSuccessCount()
ACAs sent and received with the Result-Code AVP >= 3000 (failure)	getAcaErrorCount()
Successfully completed sessions	getCompleteSessionCount()
Error sessions	getErrorSessionCount()

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on Currently Active Sessions

Using RfGaugeRuntimeMBean, you can get the gauge of sessions that IM-OFCF or R-IM-OFCF is currently handling.

Online Mediation Controller creates a separate instance of RfGaugeRuntimeMBean for each instance of IM-OFCF PCP and R-IM-OFCF PCP.

The object name of this MBean is com.convergin:Type=RfgaugeRuntime,Version=MBean_Version,Location=<server-name>,Name=IM_Instance_Name.Rf.

Table 11-5 describes the gauge that RfGaugeRuntimeMBean provides.

Table 11-5 RfGaugeRuntimeMBean

To Get Total Number of...	Use...
Currently active sessions	getActiveSessionsGauge()

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on the Orchestration Engine

Using OeRuntimeMBean, you can get the counters of sessions and application triggers.

The object name of this MBean is com.convergin:Type=OeRuntime,Version=MBean_Version,Location=Server_Name,Name=IM_instance_name.Oe

Table 11-6 describes the counters that OeRuntimeMBean provides.

Table 11-6 OeRuntimeMBean Counters

To Get Total Number of...	Use...
Sessions that the OE handled	getSessionCount()
Successful application triggering that the OE performed	getSuccessfulApplicationTriggeringCount()
Unsuccessful application triggering that the OE attempted to perform	getUnsuccessfulApplicationTriggeringCount()
2xx and 3xx responses that the OE received	getSuccessfulUAServerTriggeringCounter()

Using OlpRuntimeMBean, you can get the counter of triggering a specific Orchestration Login Processor (OLP).

The object name of this MBean is com.convergin:Type=OlpRuntime,Version=MBean_Version,Location=Server_Name,Name=IM_Instance_Name.Olp.Olp_Name

Table 11-7 describes the counter that OlpRuntimeMBean provides.

Table 11-7 OlpRuntimeMBean Counter

To Get Total Number of...	Use...
Times that the OE triggered the specific OLP	getExecutionCount()

Using OprRuntimeMBean, you can get the counter of queries that the Orchestration Logic Processor (OLP) executed.

The object name of this MBean is com.convergin:Type=OprRuntime,Version=MBean_Version,Location=Server_Name,Name=IM_Instance_Name.Opr.Opr_Name

Table 11-8 describes the counters that OprRuntimeMBean provides.

Table 11-8 OprRuntimeMBean Counters

To Get Total Number of...	Use...
Successful queries that an OPR executed	getSuccessfulQueryCount()
Unsuccessful queries that an OPR attempted to execute	getUnsuccessfulQueryCount()

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Monitoring the Signaling Domain

A deployment of Online Mediation Controller might involve the following SSUs:

• Diameter SSU. See "Checking the Status of Diameter Network Entities" for more information.

• PCP SSU. See "Checking the Status of PCP Network Entities" for more information.

• WS SSU. See "Checking the Status of Web Service Network Entities" for more information.

Using runtime MBeans, you can check whether the network entity with which the SSU communicates is active.

Checking the Status of Diameter Network Entities

Using NetworkEntityRuntimeMBean, you can get the status of the Diameter network entity. Table 11-9 describes the attributes that NetworkEntityRuntimeMBean provides.

Table 11-9 NetworkEntityRuntimeMBean Attributes

Attribute	Description
getValue()	The attribute contains the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.
getStatus()	Specifies a network entity status: 0 - Network entity is unavailable 1 - Network entity is available 2 - Status of the network entity is unknown

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Checking the Status of PCP Network Entities

Using PcpPaStatisticsMBean, you can get the status of the BRM application. Table 11-10 describes the attribute that PcpPaStatisticsMBean provides.

Table 11-10 PCP SSU Monitoring Attribute

Attribute	Description
getPcpPaStatus()	Specifies the status of the BRM applicatikon. Possible values: 0 - Inactive 1 - Active

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Checking the Status of Web Service Network Entities

Using NetworkEntityRuntimeMBean, you can get the status of the Web Services entity. Table 11-11 describes the attributes that NetworkEntityRuntimeMBean provides.

Table 11-11 NetworkEntityRuntimeMBean

Attribute	Description
getValue()	The attribute contains the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.
getStatus()	Specifies a network entity status: 0 - Network entity is unavailable 1 - Network entity is available 2 - Status of the network entity is unknown

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Checking Availability of the Diameter and RADIUS Ports

To ensure a stable communication between entities in a Diameter or RADIUS network and Online Mediation Controller, you can check whether the Diameter and RADIUS ports of Online Mediation Controller are up. This check is known as healthcheck.

To perform a healthcheck for a Diameter or RADIUS port:

• Configure the Load Balancer to send to Online Mediation Controller a TCP open request.

  If you check availability of the Diameter port, then after the connection is established, you can receive more detailed information, such as a Result-Code AVP on the status of the port, by sending a Capabilities-Exchange-Request (CER) and analyzing the received Capabilities-Exchange-Answer (CEA).