4 Monitoring Policy Controller Using Runtime MBeans

This chapter explains how to monitor Oracle Communications Service Broker Policy Controller (Policy Controller) using runtime MBeans.

About Monitoring Policy Controller

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

• Statistics on messages and sessions that Policy Controller handles. 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.

Monitoring the Processing Domain

Policy Controller generates and collects a set of statistics for each processing managed server. You can use the statistics to monitor subscriber traffic. The statistics are derived from a variety of counters and gauges collected by MBean attributes. These statistics are available for you to view using a JConsole or another third-party JMX-compliant monitoring tool.

By default:

• Policy Controller MBean statistics counters and gauges are active.

• Statistics notification is enabled.

• The counters are reset to zero every 900 seconds.

• Monitoring notifications are sampled every 30 seconds to check whether the threshold has been crossed.

Each unified domain contains one set of statistics MBeans. In dual processing and signaling domains the statistics MBeans reside on the processing managed servers.

Monitoring the Policy Controller Interfaces

Using PcrfMBean, you can get counters of messages that Policy Controller sends and receives through the Gx and Rx interfaces.

The object name of this MBean is oracle:Class=oracle.axia.api.platform.runtimembean.RuntimeStandardMBean,Type=PcrfCounter,Version=MBean_Version,Location=Managed_Server_Name,Name=pcrf,CountingMethod=Counting_Method

The following sections describe the counters and gauges that you can use to get statistics on messages that Policy Controller sends and receives through each of these interfaces.

Getting Statistics on the Gx Interface

Table 4-1 describes the counters and the gauge that PcrfMBean provides for the Gx interface.

Table 4-1 PcrfMBean Counters and Gauge for the Gx Interface

To Get Total Number of…	Use…
Successfully completed sessions	GxSuccessfullyCompletedSessions
Failed sessions	GxFailedSessions
CCAs sent with the Result-Code AVP less than 3000	GxCcaInitialSentSuccess
CCA-Initial messages sent with the Result-Code AVP equals to, or is greater than 3000	GxCcaInitialSentFailure
CCA-Update messages sent with the Result-Code AVP less than 3000	GxCcaUpdateSentSuccess
CCA-Update messages sent with the Result-Code AVP equals to, or is greater than 3000	GxCcaUpdateSentFailure
CCA-Terminate messages sent with the Result-Code AVP less than 3000	GxCcaTerminateSentSuccess
CCA-Terminate messages sent with the Result-Code AVP equals to, or is greater than 3000	GxCcaTerminateSentFailure
Incremented each time a Gx session timer (Tcc) fires.	GxTimedOutSessionsTcc
Incremented each time a Gx session closing timer (Tsc) fires.	GxTimedOutSessionsTsc
CCR-Initial message received	GxCcrInitialReceived
CCR-Update messages received	GxCcrUpdateReceived
CCR-Terminate messages received	GxCcrTerminateReceived
RAR messages sent	GxRarSent
RAA messages received with the Result-Code AVP less than 3000	GxRaaReceivedSuccess
RAA messages received with the Result-Code AVP equals to, or is greater than 3000	GxRaaReceivedFailure
CCR-Initial messages received and rejected due to overload	GxThrottledSessions
Currently active sessions (gauge)	GxActiveSession

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 Rx Interface

Table 4-2 describes the counters and the gauge that PcrfMBean provides for the Rx interface.

Table 4-2 PcrfMBean Counters and Gauge for the Rx Interface

To Get Total Number of…	Use...
Initial AAR messages received and rejected due to overload	RxThrottledSessions
STA messages received with the Result-Code AVP less than 3000	RxSuccessfullyCompletedSessions
AAA or ASA messages sent with the Result-Code AVP equal to, or greater than 3000	RxFailedSessions
Timed Out Sessions (Tcc) messages received	RxTimedOutSessions
Initial AAR messages received	RxAarInitialReceived
Initial AAA messages sent with the Result-Code AVP less than 3000	RxAaaInitialSentSuccess
Initial AAA messages sent with the Result-Code AVP equals to, or greater than 3000	RxAaaInitialSentFailure
Subsequent AAA messages sent with the Result-Code AVP less than 3000	RxAaaSubsequentSentSuccess
Subsequent AAA messages sent with the Result-Code AVP equals to, or greater than 3000	RxAaaSubsequentSentFailure
ASR messages sent	RxAsrSent
ASA messages received with the Result-Code AVP less than 3000	RxAsaReceivedSuccess
RAA messages received with the Result-Code AVP equals to, or greater than 3000	RxAsaReceivedFailure
STR messages received	RxStrReceived
STA messages sent with the Result-Code AVP less than 3000	RxStaSentSuccess
STA messages sent with the Result-Code AVP equals to, or greater than 3000	RxStaSentFailure
Incremented each time an Rx session timer (Tcc) fires.	RxTimedOutSessionsTcc
Incremented each time an Rx session closing timer (Tsc) fires.	RxTimedOutSessionsTsc
Subsequent AAR messages received	RxAarSubsequentReceived
STR messages received	RxStrReceived
ASR messages sent	RxAsrSent
Currently active sessions	RxActiveSession

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

Policy Controller might require 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.

• SMPP SSU. See "Checking the Status of SMPP 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 4-3 describes the attributes that NetworkEntityRuntimeMBean provides.

Table 4-3 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 4-4 describes the attribute that PcpPaStatisticsMBean provides.

Table 4-4 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 4-5 describes the attributes that NetworkEntityRuntimeMBean provides.

Table 4-5 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 the Status of SMPP Network Entities

Using SmppAdapterMBean, you can get the status of all SMPP connections. Table 4-6 describes the attribute that SmppAdapterMBean provides.

Table 4-6 SmppAdapterMBean Status Attribute

Attribute	Description
getlistSmscConnectionStatus[]	Specifies the status of all SMSC connections. Possible values: 0 - Inactive 1 - Active

Using NetworkEntityRuntimeMBean, you can get the status of the network entity. Table 4-7 describes the attributes that NetworkEntityRuntimeMBean provides.

Table 4-7 NetworkEntityRuntimeMBean Status Attributes

Attribute	Description
getValue()	Specifies 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. Possible values: 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.