[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

3223.0. "filtering alarms to other domains" by SEDSWS::MALLOY () Mon Jun 22 1992 07:55

		FILTERING ALARMS
               =====================


I have a network  containing 25 Nodes (phaseIV and Phasev)
These nodes are L2 area Routers and have several Wide area
links.
These  nodes are divided into 6 domains.  

Notification is set for LATEST ALARMS.Which give a good feeling for
whats going on.

The main problem is when I lost 2 WAN links in the same domain.
The upper domain changes red (critical) .
IF one link comes back online then the upper domain changes green (clear).

But I still have circuit down.

I have create other domains  now for  phaseIV nodes , phasev and
links. Each of these new domains contain the other 6 domains as
sub-domains.
 I am trying filter the alarms to these new domains.

PhaseIV <-------------  critical alarm for phaseIV nodes
PhaseV  <-------------  critical alarm for phaseV nodes
Link    <-------------  critical alarm for circuits 



 I hope these three domains will remain red until the customer clears
them.


I have spent many hours trying solve this and have achieved very little.
I can stop all alarms but I can not filter ALARMS  


questions
=========

	1) Should this be possible.
	2) Has someone got the correct syntax


	I am going back to  site  on  23-jun-1992 to continue 
playing with alarm filtering. I shall bring back copies of the
notification requests.


		Gary

         
T.RTitleUserPersonal
Name
DateLines
3223.1T1.2.7 bugTOOK::CALLANDERMCC = My Constant CompanionMon Jun 22 1992 16:273
this sounds like a bug we hd in T1.2.7, if that is not what
you are running please let me know. Otherwise, this problem 
should have already been corrected at this time.