Oracle Communications Diameter Signaling Router (DSR)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
 

In this Document

Goal

Solution

References

Created from <SR 3-12940754621>

Applies to:

Goal

This document explains how raising EventId 19901 alarms can be cleared or avoided when provisioning Egress Throttle Group entries in Diameter Signaling Router Release 7.0.x

Solution

In this case the appearance of EventId 19901 is due to Bug 21299124 "ETG: Minor DB validation Alarm when Rate Limiting is not configured."

Background:
When a new Egress Throttle Group [ETG] is created (Insert), table entries for BOTH 'Rate Limiting' and 'Pending Transaction Limiting' parameters are created. If the one of the checkboxes for 'Egress Throttlings' [ETG type] option is unchecked (for example 'Rate Limiting' is unchecked), the parameter values for the associated ETG type are set to defaults and the capability is Disabled for that unchecked type.
The root of this Bug is that when 'Rate Limiting' ETG type option is not checked, one of the fields in a software table is not properly set to its default value but instead set to '0.' Even though Rate Limiting will not be used, this value does not match the enforced default and the audit detects it and raises 19901.

Resolution:
This Bug is resolved in DSR 7.1 and later software releases.  Oracle recommends upgrading to this release or later to capture the permanent fix.

Temporary Workaround:
Create ETG entries that have BOTH Rate Limiting and Pending Transaction Limiting options, then Enable only the Pending Transaction Limiting capability.

1. First, delete the 'bad' ETGs that are already present
2. On each DA-MP, manually clear the alarm by logging in to each server as admusr and executing 'alarm.put -e 19901 -s 5'
3. Next add back each Egress Throttle Group but with both 'Rate Limiting' and 'Pending Transaction Limiting' Egress Throttlings checked. Set any mandatory parameters.
4. In the Active SOAM under Main Menu: Diameter -> Maintenance -> Egress Throttle Groups screen, use only the 'Enable Pending Transaction Limiting' button to enable this capability on selected (highlighted) Egress Throttle Group entries as desired. Simply choose not to use 'Rate Limiting' even though it is available

Alternative Workaround:
You may consider another workaround but be advised that (1) it manipulates table entries which has some risk, (2) it requires each DA-MP to be restarted, thus drops all connections and (3) it will have to be done EVERY TIME a new ETG entry is added. However, any entry for which this workaround is executed will remain corrected over restarts and reboots [i.e. 19901 will not come back over reboot]. Also this method will not allow a user to enable 'Rate Limiting' as the GUI will provide an error for any attempt.

Workaround #2: Correct errant table value on the active SOAM, restart EVERY DA-MP to clear 19901 alarm AND correct ETG Operational Status.
-----------

1. Identify the ETG ID# from the 19901 alarm. Example:
   TIMESTAMP: 2016-06-30 14:07:09.397 UTC
   NETWORK_ELEMENT: NO_MYLAB
   SERVER: mylab-mp-1
   SEQ_NUM: 12710025
   EVENT_NUMBER: 19901
   SEVERITY: MAJOR
   PROCESS: dsr
   TYPE: STK
   INSTANCE:
   NAME: CFG-DB Validation Error
   DESCRIPTION: A minor database validation error was detected on the MP server during an update. MP internal database is now out of sync with the configuration database. Subsequent database operations on the MP are ALLOWED.
   ERR_INFO:
   GN_INFO/WRN
   ConfigError<PreUpdateError> in file DrlData.C at line 8583:
   Failed in setting the rate limiting onset/abatement threshold parameters
   for aggregated metric for etgId: 11 <<<======== ETG ID ==================
   ^^ [23116:DbRecordHandler.C:779]
    
2. Log into the active SOAM as admuser
3. Print full table content so we are sure of all entry values before making any changes:
   [admusr@active-SOAM ~]$ iqt -E DpiEgressThrottleGrp
    
4. Using the ETG ID from step 1, change the 'bad' value to its default of 250 using the following command
   [admusr@active-SOAM ~]$ iset -frateConvergenceTime=250 DpiEgressThrottleGrp where "id=<ETG ID>"
    
5. Here's an example; in lab the errant ETG ID was 11 as shown in the 19901 event above:
   [admusr@mylab-soam-b ~]$ iset -frateConvergenceTime=250 DpiEgressThrottleGrp where "id=11"
   === changed 1 records ===
   [admusr@mylab-soam-b ~]$
    
6. Print full table again to verify rateConvergenceTime was changed to 250:
   [admusr@active-SOAM ~]$ iqt -E DpiEgressThrottleGrp
    
7. To clear the 19901 alarm and repair the 'UNK' Operational States shown in the SOAM GUI Main Menu: Diameter -> Maintenance -> Egress Throttle Groups, perform the following:
   1. Log into the ACTIVE SOAM GUI
   2. Navigate to the Main Menu: Status & Manage -> Server screen
   3. Select (highlight) a DA-MP with the 19901 alarm
   4. Select 'Restart' at the bottom of the screen.
   5. When DA-MP recovers, repeat this step on the next DA-MP until all have been restarted

This will clear the 19901 alarms, repair the database, and will not allow a user to enable 'Rate Limiting' if they attempt to do so on the Main Menu: Diameter -> Maintenance -> Egress Throttle Groups screen.

You may choose either Workaround method to resolve this problem. Your decision should be based on what is best for you and your operators.

References

This solution has no attachment