Filters

This section describes the filters that help retrieve matching elements.

The probe retrieves elements by using a filter that associates an ObjectServer field with its expected value. Filters take the following format:

<attribute_name> <attribute_comparison_operator> <attribute_value>

The following table lists the valid operators and attribute values for the available ObjectServer fields:

Table 1. Valid operators and attribute values
Name of the attribute	Valid operators	Valid attribute values
`alarmType`	`==`	`COMMUNICATIONS_ALARM` `ENVIRONMENTAL_ALARM` `EQUIPMENT_ALARM` `PROCESSING_ERROR_ALARM` `QUALITY_OF_SERVICE_ALARM`
`managedObjectClass`	`==`	The filtering of elements sent from the device can only be configured in Nokia-Siemens NetAct. For details of the syntax required for filtering object classes, refer to your CORBA documentation or contact your system administrator. Note: An attribute value of `0` retrieves any matching alarms from both the 3GPP interface and the Nokia-Siemens NetAct system.
`perceivedSeverity`	`==` `<` `<=` `>` `>=`	`CRITICAL` `MAJOR` `MINOR` `WARNING` `CLEARED`

Valid filters

The following filters are examples of valid filters:

(managedObjectClass == SubNetwork) OR (managedObjectClass == ManagedElement) OR (managedObjectClass == ManagedFunction) AND (NOT alarmType == PROCESSING_ERROR_ALARM)
(alarmType == ENVIRONMENTAL_ALARM) OR (perceivedSeverity <= MINOR)
(alarmType == ENVIRONMENTAL_ALARM) OR (NOT perceivedSeverity == WARNING)

The following filters are examples of invalid filters that will not work:

(perceivedSeverity == WARNING) OR (managedObjectInstance == SubNetwork=Nokia-1)
(alarmType == ENVIRONMENTAL_ALARM) AND (probableCause < 1000)
(alarmType < ENVIRONMENTAL_ALARM)