Subscriber Activity Log

Asset ID:	1-71-2240498.1
Update Date:	2017-03-16
Keywords:

Solution Type Technical Instruction Sure

Solution 2240498.1 : Subscriber Activity Log

Applies to:

Oracle Communications Policy Management - Version POLICY 11.5.0 and later
Tekelec

Goal

To provide the customer, PSE and TSC a real time tool to debug real/test user issues in real time.
Reduce time to resolution

Solution

The Subscriber Activity Log provides insight into the system at a fine grained level that will be useful for both support purposes and for customers interested in subscriber specific tracking.
Subscriber activity will include diameter protocol level messaging, user profile retrieval, and policy engine execution.

The CMP system can perform real-time tracing of Gx, Rx, SOAP, TCP provisioning, and Sh protocol messages for a subscriber from multiple MPE devices. Together this information allows a user to monitor a particular subscriber request(s) through the entire system.

This document contains the steps to configure the Subscriber Activity log, a demo scenario and some limitations of this feature.

Configuration:

From the "System Wide Reports" section of the navigation pane, select "Subscriber Activity Log". The "Subscriber Activity Log" page opens.

On the "Configuration" tab:
- Click "Modify"
  - Set “Trace Enable” to TRUE
  - Set “Severity” to INFO or DEBUG¹
  - Activity Type :
    - Protocol : True (default)
    - Policy : True (default)

Subscriber Identity Log - Configuraiton 1

¹The main difference in traces when collected with Debug vs INFO is , you see extra hex dump and line by line evaluation of all policies. In Info mode you will only see the policy which is executed and not evaluated and ignored.

Click "Add" on the "Subscriber Identifier List":
- Identifier types – IMSI/E.164/NAI/IP/Session-ID
Click "Save"

Subscriber Identity Log - Configuraiton 2

On the "Log Backup" tab:
- Click "Modify" and update the following fields according to your needs:
  - First Running Time
  - Run Interval (Hours)
  - Max Keep (Days)
  - Folder Max Size (MB)

The following snapshot represents the Default Settings for the "Log Backup" session:

Default Settings for Log backup

Where the new log is saved:

Output for log location

The following snapshot represents the Custom Settings for the "Log Backup" session:

Custom Settings for Log backup

Demo scenario:

Here some examples of the policy and DIAMCLI commands used to test the Subscriber Identity log. You can review several snapshots obtained during the execution of the DIAMCLI commands at the end of the document in the section "Snapshots"

Policy:

Where the request is creating a new session

And where the subscriber profile data is available

gran total volume to 100 percent used to gaurav_rollover

install Gaurav_test PCC rule(s) for session

accept message

DIAMCLI commands:

connect -address=10.148.230.122 -remoteidentity=tkhandekar-mpe-115.oracle.com -set app1.name=gx -identity=diamcli -realm=oracle.com
ccr gx -request=initial -framedip=172.25.0.30 -sgsnip=200.79.17.27 -sgsnmccmnc=334020 -ratt=utran -ipcantype=0 -user164=518555121212340 -userimsi=311303123456789 -operation=1 -calledstationid=apn1.com -bearerid=102 -supportedfeatures=REL9
ccr gx -request=update -set umi1.used.total=<usage> -set events="33" -sessionid=<Session id>
ccr gx -request=terminate -sessionid=<Session id>

Limitations:

Maximum subscribers that can be configured (enabled + disabled trace) : 60
Maximum subscribers that can have trace enabled : 20
If the system goes into load shedding , feature is disabled automatically
Rx AAR message is not traced automatically based on original E164/IMSI/Session ID identifiers. (Bug# 21843046)

Snapshots

Attachments

This solution has no attachment