How to Capture Data When Subscriber Data Management HLR Is Experiencing Overloading Conditions

Asset ID:	1-71-2184854.1
Update Date:	2016-09-21
Keywords:

Solution Type Technical Instruction Sure

Solution 2184854.1 : How to Capture Data When Subscriber Data Management HLR Is Experiencing Overloading Conditions

Applies to:

Oracle Communications Subscriber Data Management (SDM) - Version SDM 7.0.22 to SDM 9.1.3 [Release SDM 7.0 to SDM 9.0]
Tekelec

Goal

This document provides the steps required to determine "if" there is an overload condition present, as well as "why" an overload condition is present

Solution

For SDM HLR All Releases.

If you encounter an issue where SDM HLR is generating alarms for HLR Overload Control (Alarm ID's 9039 & 9040), make sure the following actions are done.

1) Determine if there has been any network maintenance at the time of the event? If so provide information to Support.

2) Gather screenshots of the Active and Historical Alarms.

3) Ping across the network to see if there is latency present.

4) Check NTP to make sure the NTP is synchronizing.

5) Capture the Bluelogs.

a) # bluelogs.sh -z /export/TAC/bluelogs/

6) Gather any core files

a) # ls -ltr /blue/var/debug/

b) # gencore /blue/bin/<process>

5) Run and capture the following commands for Legacy SDM to analyze (as root).

a) # top

b) # free -m

c) # vmstat

d) # iostat -n

e) # mpstat

Attach data to SR that was opened for Oracle Analysis.

Attachments

This solution has no attachment