0330 - System SCCP TPS Threshold Exceeded

This message indicates EAGLE has exceeded its TPS (Transactions Per Second) message transport rate threshold. For every 30 seconds EAGLE is above the threshold, an ATH (Application Trouble Handler) reports the minimum, maximum and average TPS value seen during the past 30-second period.

Example

RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0330 ** SCCP SYSTEM      System SCCP TPS Threshold exceeded

Alarm Level: Major

Recovery

1. Use rept-stat-sccp to determine the status of the SCCP subsystem.
   This command also identifies which SCCP cards are OOS-MT. For example, enter:
   rept-stat-sccp
   Example of the output:

   eaglestp 00-10-24 20:38:58 EST EAGLE 35.0.0
       SCCP SUBSYSTEM REPORT IS-NR          Ovflw-1       -----
       SCCP Cards Configured= 4 Cards       IS-NR= 4
       System TCP Alarm Threshold =  80% Total capacity 
       System Peak SCCP Load =  3000 TPS
       System Total SCCP Capacity =  5000 TPS
       CARD   VERSION     PST        SST         AST      MSU USAGE   CPU USAGE 
       -------------------------------------------------------------------------
       1212   021-001-000 IS-NR      ACTIVE      ALMINH       47%         32%
       -------------------------------------------------------------------------
       SCCP Service Average MSU Capacity = 47%     Average CPU Capacity = 32%
       
       Command Completed.

   Use the command rept-stat-sccp:mode=perf to retrieve the maximum and average values, if desired.
2. The user may clear this alarm by raising the threshold limit to a value greater than the maximum value.
   In this case, the alarm stops immediately. You should use the rtrv-th-alm command to list the threshold rate, and you may use the chg-th-alm command to change the threshold value.
3. The user should evaluate this new traffic level and determine whether additional SCCP cards are required to maintain the TPS level the system is processing.
4. Use the rept-stat-card command to display the card status and maintenance activity states.
   Examine the report for any cards that may be OOS-MT.
5. Use the init-card command to initialize any cards(s) that are OOS-MT.
   This causes the card(s) to reload the MTP data as well as GTT data tables.
6. Again using the rept-stat-sccp command, verify the card(s) have returned to service.
   If any card(s) have failed to return to IS-NR, reseat the card(s).
7. If any card(s) remain OOS-MT, replace the card(s).
   Refer to the Maintenance Manual for card removal/replacement procedures.