Specifying filtering operations for resychronization

During resynchronization, the probe can perform various filtering operations, the details of which are defined in the filter file specified by the ResyncFilterFile property.

Simple filters

Simple filters use the following syntax:

<v11:filter> 
<v11:attributeNameList> 
<v13:attributeName>POSSIBLE_VALUE</v13:attributeName> 
</v11:attributeNameList> 
</v11:filter>

Where attributeName is one of the event attributes listed in the table below, and POSSIBLE_VALUE is one of the values listed for that attribute.

The following example code shows how to use the filter file to select for resynchronization all those events that have a perceivedSeverity of MINOR:

<v11:filter> 
<v11:perceivedSeverityList> 
<v13:perceivedSeverity>MINOR</v13:perceivedSeverity> 
</v11:perceivedSeverityList> 
</v11:filter>

More complex filters

Complex filters use the following syntax:

<v11:filter>
  <v11:source>AlarmSourceType</v11:source>
    <v11:scope>
      <v12:name>
        <v12:rdn>
          <v12:type></v12:type>
          <v12:value></v12:value>
        </v12:rdn>
      </v12:name>
    </v11:scope>

  <v11:attributeNameList>
      <v13:attributeName>POSSIBLE_VALUE</v13:attributeName>
      <v13:attributeName>POSSIBLE_VALUE</v13:attributeName>
  </v11:attributeNameList>

  <v11:probableCauseList>
    <v14:prc extension="?" qualifier="?">
      <v14:ru>false</v14:ru>
      <v14:contra>false</v14:contra>
      <v14:probableCause>PROBABLE_CAUSE</v14:probableCause>
    </v14:prc>
  </v11:probableCauseList>

  <v11:acknowledgeIndication>ACKNOWLEDGEMENT_STATUS</v11:acknowledgeIndication>
</v11:filter>

The following example code shows how to use the filter file to select for resynchronization only those alarms generated by MTOSI server, that have a perceivedSeverity of either WARNING, or MINOR, and whose probable cause is transmission failure.

<v11:filter>
  <v11:source>INTERNAL</v11:source>
    <v11:scope>
      <v12:name>
        <v12:rdn>
          <v12:type>MD</v12:type>
          <v12:value><Object Name of Network Element></v12:value>
        </v12:rdn>
      </v12:name>
    </v11:scope>

  <v11:perceivedSeverityList>
         <v13:perceivedSeverity>WARNING</v13:perceivedSeverity>
         <v13:perceivedSeverity>MINOR</v13:perceivedSeverity>
  </v11:perceivedSeverityList>


  <v11:probableCauseList>
    <v14:prc extension="?" qualifier="?">
      <v14:ru>false</v14:ru>
      <v14:contra>false</v14:contra>
      <v14:probableCause>TX_FAIL</v14:probableCause>
    </v14:prc>
  </v11:probableCauseList>


<v11:acknowledgeIndication>?</v11:AI_EVENT_UNACKNOWLEDGED>

</v11:filter>

Attribute names and their corresponding values

The following table shows all the attributes that you can use within filter files, and their corresponding possible values.
Table 1. Filter attributes and associated values
Attribute name Possible values

AcknowledgeIndicationType

  • ACKNOWLEDGED
  • UNACKNOWLEDGED
  • NOT_APPLICABLE

AssignedSeverityEnumType

  • INDETERMINATE
  • CRITICAL
  • MAJOR
  • MINOR
  • WARNING
  • NOT_ALARMED
  • FREE_CHOICE

EquipmentProtectionGroupTypeEnumType

  • MINOR_EXT
  • M_FOR_N
  • M:N
  • EPG_1_PLUS_1
  • EPG_INBD_1_PLUS_1
  • EPG_1_FOR_N
  • BPS

EquipmentSwitchReasonEnumType

  • MINOR_EXT
  • VENDOR_EXT
  • NOT_APPLICABLE
  • FAILURE
  • MANUAL

G_774_3_APSfunctionEnumType

  • MINOR_EXT
  • VENDOR_EXT
  • G.783
  • Legacy

PerceivedSeverity

  • INDETERMINATE
  • CRITICAL
  • MAJOR
  • MINOR
  • WARNING
  • CLEARED

ProtectionGroupTypeEnumType

  • MINOR_EXT
  • PGT_MSP_1_PLUS_1
  • PGT_MSP_1_FOR_N
  • PGT_2_FIBER_BLSR
  • PGT_4_FIBER_BLSR
  • PGT_1VN
  • PGT_1P1
  • PGT_UNKNOWN

ProtectionTypeEnumType

  • MINOR_EXT
  • VENDOR_EXT
  • MSP_APS
  • PGT_MSP_1_PLUS_1
  • PGT_MSP_1_FOR_N
  • PGT_2_FIBER_BLSR
  • PGT_4_FIBER_BLSR
  • PT_SNCP
  • PT_UNKNOWN

ServiceAffectingType

  • UNKNOWN
  • SERVICE_AFFECTING
  • NON_SERVICE_AFFECTING

SwitchReasonType

  • NOT_APPLICABLE
  • RESTORED
  • SIGNAL_FAIL
  • SIGNAL_MISMATCH
  • SIGNAL_DEGRADE
  • AUTOMATIC_SWITCH
  • MANUAL

ReversionModeType

  • UNKNOWN
  • NON_REVERTIVE
  • REVERTIVE

The following table shows a list of attributes that you can use within complex filter files, and their corresponding possible values.

Table 2. Complex filter attributes and associated values
Name Type Description Example

source

AlarmSourceType

Use this attribute to filter alarms based on alarm source type. The attribute can be set to one of the following values:

INTERNAL: The probe filters internal alarms from target system based on alarm source type.

NOT_APPLICABLE or omitted: The probe does not filter alarm based on alarm source type.

Note: When query internal alarm from a specific target system, source parameter should set to INTERNAL.
<v11:source>INTERNAL</v11:source>

scope

NamingAttribute ListType

Use this attribute to filter the alarms based on specific managed elements. If no managed element is specified, alarms from all managed elements are selected.
Note: The specified value must be the MTOSI object name of a network element.

When an network element name is specified, it indicates the equipment from which alarms are queried.

<v11:scope>
  <v12:name>
    <v12:rdn>
     <v12:type>MD</v12:type>
<v12:value>
<Object Name of Network Element>
</v12:value> </v12:rdn> </v12:name> </v11:scope> For Example: <v11:scope> <v12:name> <v12:rdn> <v12:type>MD</v12:type> <v12:value>
<Object Name of Network Element>
</v12:value> </v12:rdn> </v12:name> </v11:scope>For Example:

perceived SeverityList

PerceivedSeverity ListType

Use this attribute to filter the alarms based on a specified level of severity. This can be set to one of the following values:

  • CRITICAL
  • MAJOR
  • MINOR
  • WARNING
<v11:perceivedSeverityList>
<v13:perceivedSeverity>WARNING
<v13:perceivedSeverity>    
<v13:perceivedSeverity>MINOR<v1
3:perceivedSeverity> 
</v11:perceivedSeverityList>

probableCause List

ProbableCause List Type

Use this attribute to filter the alarms based on a list of probable causes. If no probable causes are specified, all alarms will be selected for resynchronization.

Note: You can specify any of the standard MTOSI probable cause descriptions. For details, see the TM Forum MTOSI web site.
<v11:probableCauseList>
 <v14:prc>       
 <v14:ru>false</v14:ru>

<v14:contra>false</v14:contra

<v14:probableCause>TX_FAIL</v14:
probableCause></
   v14:prc>
</v11:probableCauseList>

ru

ProbableCause List Type

The following sub-attribute is defined for each probable cause:

ru: The Remote Unit (RU) parameter is used to indicate the location of the network resource associated with the alarm probable cause:

false: The alarm is associated with a local network resource.

true: The alarm is associated with a remote network resource.

 

contra

ProbableCause List Type

The following sub-attribute is defined for each probable cause:

contra: This parameter is used to distinguish the direction of the signal related alarm:

false: The alarm is detected on the signal related to the sink atomic function.

true: The alarm is detected on the signal related to the source atomic function.

 

acknowledge Indication

Acknowledge IndicationType

Use this attribute to filter the alarms based on the acknowledgement status. The attribute can be set to one of the following values:

AI_EVENT_ ACKNOWLEDGED: Acknowledged.

AI_EVENT_ UNACKNOWLEDGED: Unacknowledged.

NOT_APPLICABLE: unknown.

<v11:acknowledgeIndication>AI_
EVENT_UNACKNOWLEDGED</v11:
acknowledgeIndication>