BNS Platform Hardware
 

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

In this Document

Symptoms

Cause

Solution

Created from <SR 3-12760175791>

Applies to:

Symptoms

Move the Rule function is not working under DSR GUI path Main Menu: Diameter -> Mediation -> Rule Sets -> RuleName

Cause

It looks like one of the below two reasons are hitting due to which Move the Rule Column is not working :

1. When the Filter function or clicking a Condition column heading is used to sort the columns, the Move the rule columns are not displayed. The Restore Order button can be clicked to return the list to its original order.
2. If all of the conditions in the rule support Fast Search, then the Move the rule columns are not displayed.

Solution

The Diameter > Mediation > Rule Sets > {name} page displays the following columns  Move the rule

A Move the rule column appears at the left and at the right of the rules list when there are rules that are allowed to be moved up or down in the list to change the order of rule execution.
Up and Down buttons in the Move the rule columns can be used to move a rule up one position in the list or down one position in the list each time the button is clicked. Up and Down buttons appear in the Move the rule columns for a rule or rule group when the order of the rules is allowed to be changed, with the following restrictions:
• When the Filter function or clicking a Condition column heading is used to sort the columns, the Move the rule columns are not displayed. The Restore Order button can be clicked to return the list to its original order.
• If all of the conditions in the rule support Fast Search, then the Move the rule columns are not displayed.

If there is at least one condition that does not support Fast Search, then the Up and Down buttons are displayed according to the following rules:
• All of the rules that support Fast Search always appear in the list before any rules that do not support Fast Search.
• The rows that have exactly the same data in the conditions that support Fast Search form a group. Rows can be moved only within their group; the Up and Down buttons are enabled and disabled accordingly.

Above corresponds to the "all of the conditions in the rule support Fast Search".How to identify cases of "the rule support Fast Search" and "the rule not support Fast Search" ?

Let me share the details with you on Fast Search :

Fast Search
The Fast Search option is used to cause Mediation to use fast database lookups. If Fast Search is not used, the values of each condition are checked one-by-one until the first match is found. The Fast Search option appears as the first element for each condition that is defined in the Conditions section for a Rule Template. The Fast Search option is not editable; it serves only to indicate whether
Fast Search will or will not be used for the condition:
All of the conditions with the Fast Search option enabled must precede any conditions without Fast Search enabled in the Rule Set list. If any conditions without Fast Search enabled precede conditions with Fast Search enabled, a database lookup could fall back to slow search because of the order of the conditions.
The value of the Fast Search option is determined by the Operator and the Right value that are selected for the condition. The Fast Search value is either the “Yes” (check mark) sign or the “No”(red circle with a red line through it) sign.
• Fast Search is supported only by the “equals”, “begins with (longest match)”, “begins with”, “is within”, “exists”, “does not exist”, “is true”, “is false” Operators.
• If a “no” sign is displayed for the Fast Search option, then the Operator “=^^” (begins with – longest match) is disabled (cannot be selected) in the Operator drop down list for the condition.
• Regardless of the Operator, the Fast Search option is supported if the Right value is a Fixed value (a data value was entered in the Rule Template, and the value cannot be changed in the Rule Set).
• Regardless of the Operator, the Fast Search option is not supported if the “xl-value” Right value type is selected without a Fixed value.
The “Yes” sign is displayed for the Fast Search option if:
• One of the Operators “==” (equals), “=^^” (begins with-longest match), “=^ (begins with)”, “is within”, “exists”, “does not exist”, “is true, “is false” is selected and the Right value type is not “xl-value”.
• The Default value is Fixed regardless of the selected Operator and Right value type; and either the condition is the first one in the Condition Set, or all the conditions above it also have a “Yes” sign for the Fast Search option.
In any other case, the “No” sign is displayed.
When the selected Operator, the order of the conditions, or the Right value type changes, then every Fast Search “Yes” and “No” value has to be reevaluated and redrawn, and the Case-sensitive check box is either enabled or disabled accordingly.
If a “Yes” sign has to be changed to “No” under the Fast Search heading as a result of the reevaluation, and the related Operator “=^^” (begins with-longest match) was selected, a dialog box is displayed to confirm disabling of Fast Search:
Case-sensitive lookup depends on the Fast Search option; the check box is unchecked and disabled if Fast Search is also disabled. The Case-sensitive check box is enabled only for the Octet-String and UTF8String Right value types.

In a Simple Note, You can go to Active OAM GUI at this path : Main Menu: Diameter -> Mediation -> Rule Templates , then Select any Rule Set name and then Edit the rule set to check if fast search is enabled or not..

This solution has no attachment