Legacy Policy Filters in Spectrum
Article ID: 367634
Updated On:
Products
Issue/Introduction
In the Spectrum application, there are existing legacy policy filters, such as "Policy-Search Modeled_Link_noalarm," which are used for filtering network interfaces based on certain criteria. The current filter is structured as follows:
The goal is to enhance this filter by adding an additional condition using the <or> operator.
The new requirement is to filter interfaces where either "0x11f7e" contains "NOALARM" and "0x12a79" is not equal to "0," or where "0x11564" (Notes) contains "NOALARM."
Environment
DX Netops Spectrum all releases
Resolution
To enhance the filtering capabilities of the "Policy-Search Modeled_Link_NoAlarm" policy criteria in the Spectrum application, customer proposed the following XML configuration:
This XML snippet defines a policy search criteria named "Policy-Search Modeled_Link_NoAlarm." Within this criteria, there are two conditions nested under an <or> logical operator, indicating that either condition can be met for the criteria to be satisfied.
The first condition, <attr-match match-type="contains" id="0x11f7e" value="NOALARM" />, checks if the attribute with ID "0x11f7e" contains the value "NOALARM." Similarly, the second condition <attr-match match-type="contains" id="0x11564" value="NOALARM" /> checks if the attribute with ID "0x11564" contains the value "NOALARM."
Both of these conditions are enclosed within the <or> element, meaning that if either of these conditions is met, the policy search criteria will be satisfied.
Additionally, outside of the <or> block, there is another condition <attr-match match-type="not-equal-to" id="0x12a79" value="0" />, which checks if the attribute with ID "0x12a79" is not equal to the value "0."
This condition is independent of the <or> block and must be satisfied along with at least one of the conditions inside the <or> block for the overall policy search criteria to be met.
Feedback
