| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi there, Lets talk current severity for alarms. When looking at the status of an OCCURS rule the current severity was always 'critical' (even if it never fired). Is current severity supported for OCCURS (and change_of) rules or might this be a bug??? Functionally the current severity attribute is a great idea, but how far will it be taken concerning usefullness? For instance, if I have alarms in batch running will I be able to get the 'current severity' of these rules?? If you got by the last question lets take another step. If I have a rule which incorporates wildcards will the current severity now have multiple instances corresponding to the entity instances being wildcarded?? One more step if we dare!! When bringing up a new map will MCC look at the current severity of all alarms enabled (all processes) and update the map??? The problem to be solved here is network mngmt using OCCURS rules only. OCCURS rules have the advantage of being fast with little overhead but if you weren't looking (ie. the map isn't up off hours) when the event happened you don't get a current status of the network when the map is brought up. Polling rules have the advantage of always providing an update function built in. The problem here is the customer must create and support at least a single poll alarm to get a fresh look at the network. Keeping up with MCC changes can be quite a task for each config change and it would be nice if MCC could help with a function similar to this without having to maintain polling alarms as a sanity check on "current network status". kind regards, brad...
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2258.1 | notification not using current severity attr | TOOK::CALLANDER | MCC = My Constant Companion | Tue Feb 18 1992 10:43 | 9 |
Brad, you ask alot of good questions. I know I don't have the answers
right now. Let me see what I can find out for you.
The gist of it is, right now the notification services aren't looking
at the current severity argument at all when a map is brought up,
thought it is a great idea.
jill
| |||||