1. Mediation User Guide
  2. Diameter Mediation
  3. Rule Templates
  4. Impact of Adding Rule Templates
  5. Assessing a Rule Template for Safe Use

2.2.1.1 Assessing a Rule Template for Safe Use

Follow this procedure to assess if it is safe to use a mediation template. Perform this procedure first during low traffic periods, and then repeat it during both moderate and peak load periods. Running this procedure does not impact the performance of the system.

  1. Use SSH to access the DA-MP where the rule template is activated.
  2. Activate the template and assign rules to the template.

    Note:

    Do not assign the template to a trigger point at this time. Assigning the template to a trigger point impacts the performance of the system.
  3. Run the top command to show the CPU usage of the DrlRequestTask DrlAnswerTask processes: 
    top -H -p `pidof dsr`

    Figure 2-2 Top Command Example Output

      PID USER   PR  NI  VIRT  RES  SHR S  %CPU  %MEM     TIME+  COMMAND                                                                                                 
31841 root   10 -10 6521m 3.2g 279m S  13.7  13.7   89:36.28 DrlRequestTask                                                                                          
31837 root   10 -10 6521m 3.2g 279m S  13.0  13.7   89:40.01 DrlRequestTask                                                                                          
31839 root   10 -10 6521m 3.2g 279m S  13.0  13.7   89:35.54 DrlRequestTask                                                                                          
31835 root   10 -10 6521m 3.2g 279m R  12.7  13.7   89:46.33 DrlRequestTask                                                                                          
31847 root   10 -10 6521m 3.2g 279m S   6.3  13.7   40:55.98 DrlAnswerTask                                                                                           
31845 root   10 -10 6521m 3.2g 279m R   6.0  13.7   41:00.14 DrlAnswerTask                                                                                           
31849 root   10 -10 6521m 3.2g 279m S   6.0  13.7   40:57.99 DrlAnswerTask                                                                                           
31803 root   10 -10 6521m 3.2g 279m S   3.0  13.7   22:49.83 CslRx

    Note:

    The top command continues to run showing real time updates to CPU usage until it is explicitly terminated
  4. Monitor the "%CPU" usage of the respective threads.
    1. If the template is assigned to a Request Trigger point, monitor the "%CPU" value associated with the DrlRequestTask process.
    2. If the template is assigned to a Answer Trigger point, monitor the "%CPU" value associated with the DrlAnswerTask process.
  5. Assign the template to the appropriate trigger point
  6. Continue to monitor the "%CPU" usage of the respective threads as performed in 4

    In a geo-redundant setup (where traffic from the mate site can double in case of the mate site failure), operators can add templates or rules as long as the "%CPU" value on any of the DrlRequestTask or DrlAnswerTask processes does not exceed 40%.

    When deployed in a non-geo-redundant setup, operators can add templates or rules as long as the "%CPU" value on any of the DrlRequestTask or DrlAnswerTask processes does not exceed 80%.