Naiman, Eugen wrote:
This is interesting (changing "Value When Red" to 7 in order to get alarms). I
thought that this value (7, 1, or 3) is used only to calculate the container rollup value
and it doesn't have an impact on alarms.
Just a couple days ago I've been bothered because some devices on our
network are modelled, I'm interested in receiving all alarms from them but I
want to see only the criticals displayed. Still, major alarms and minor alarms
on these devices had an impact on container roll-up value.
Way too many containers displayed these roll-up triangles so I went to these devices and set up the
value for "Value When Orange" and "Value When Yellow" to 0; result, all
roll-ups disappeared.
According to the solution presented in this email (my opinion though) I
shouldn't receive any minor or major alarms once I set up the corresponding
attribute to 0 but, that's not the case - I have checked and I continue to have
all these alarms and to have new ones generated since then.
What can be the explanation then?
There are different attributes for 'value when xxx' (which is the
rollup value) and for the 'xxx threshold', maybe setting the former will
impact the latter.
My way to deal with pingables was to set up a watch on them and the watch
triggers an alarm once it is violated.
You could use a Policy and setup the desired attributes on the models
once you figure out how to configure the 2 attributes to work as you want.
hth,
--
Cristi Mitrana
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]
