Hi,
We would like to generate port link state alarms for wich the severity depends on an extra parameter that is updated on the fly by an automation script.
The parameter used in the condition has the following values: Mon-Wa, Mon-Mi, Mon-Ma, Mon-C.
In the example we describe here the parameter has the value Mon-C, which should create a critical alarm for a port that has a link status not equal to 'Up'.
Each condition maps on the corresponding severity.
This seems to work fine during several actions (update 'Port Monitored' param via automation/manual, restart element, ...).
Only if we update/apply the alarm template the severity of the alarm falls back to 'Warning' and is set to 'Critical' after a couple of seconds.
The question is how this conditional monitoring should work with multiple lines?
Hi Tom,
Looking at your screenshots, I could see that you are applying the same filter (in this case the wildcard '*') for the column parameter 'Port State' (I can see 4 extra rows created in your alarm template).
We normally created multiple rows in the alarm template to define different filters per instance. For Example, I would like that my Interface 'Gi0' has critical alarm on 'Operational State' if the value is equal to 'Critical', but for other interfaces I would like to set a different severity (e.g. Warning). For this case I would define my alarm template as follows:
Extra rows added in an alarm template are applied by DataMiner from top to bottom. The first filter that matches the index will be used to apply the severity. Since you are using the wildcard '*' for the first row, this means that all the rows on the table will use the first row to set the severity.
Keep in mind that the main purpose of the alarm conditional monitoring in alarm templates is to enable/disable the monitoring (not to update alarm severities). I believe for this case you could use correlation rules. For example, you can create a correlation rule that will update the severity of the alarm depending of the value of the extra parameter:
More information about how to use script conditions can be found in DataMiner Help.
In this example, I created a correlated alarm that will assign a different severity to the alarm that triggered initially the correlation rule (when the value of another column is equal to '60'):
Keep in mind that in this case the correlation rule will be triggered when there is an alarm on the monitored parameter (not when there is an update on the extra parameter). In case you would like to trigger the correlation rule based on the value of the extra parameter, then the alarm filter should be updated to take into account the value of the extra parameter.
Hope it helps.