Cristi, If you look in the Topology Tab or the Navigation panel at the models for which you've changed the values, I'll bet they're all showing green. Getting an alarm is different from the contactability of a device. Way back in 4.1 (IIRC), Cabletron changed the functionality of pingables to allow them to go into an initial state (blue) if their Value When Red was set to '0'. This allowed the modeling of end-user PCs and other pingable devices for which Red "Lost Contact" alarms were not desired.
Changing the value_when_xxx doesn't affect the alarm process functionality, except for this one instance where it tells Spectrum that if it's a Pingable, and it's Value_when_red is set to '7', then generate a Lost Contact alarm if it can no longer be pinged. -----Original Message----- From: Cristi Mitrana [mailto:[email protected]] Sent: Thursday, July 09, 2009 12:08 AM To: spectrum Subject: Re: [spectrum] Pingable model re-initializing instead of sending traps. 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] --------------------------------------------------------------------------------------------------------- This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. --------------------------------------------------------------------------------------------------------- --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
