[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

2689.0. "Number of alarms...? " by MEHR::MEHR () Fri Apr 03 1992 22:56

Questions:
----------


	. What is the total number of alarms that can be set on DECmcc?
          (This question might have been asked before, but my search did 
    	   not find any!)
    
	. I understood that it depends on the environment.	  
          But some guidelines are needed as to what DECmcc can and can 
	  not do.
	
	  For example, our customer has a VAX4000, with 64 Meg memory, and 
	  wants to set up 500 alarms, with 2 minutes polling intervals!

	. If "500 polls, every 2 minutes"  is not acceptable,   (speaking of 
	  DECmcc limitation only - not worrying about traffic on the network!)  
	  what is  acceptable?



Details:
--------

	We have a large Digital customer who has purchased DECmcc to
	manage their network of 70% LAT traffic. They have about 500 
	terminals servers. 

	They have purchased DECmcc to become more pro-active, and their 
	main concern is reachability. They want to increase their internal 
	customer satisfaction by getting to the problem before their 
	customers calls them, as they get dropped by LAT.
	
	Beside  the amount of traffic generated on the network being an 
	issue when creating so many alarms, we need some data as to what 
	DECmcc can and can not do. And some guidelines on resources it takes.
	
	And in general,  when service turn around time is critical, what is 
	the  proper way of checking for reachability of a large number of 
	devices such as Terminal Servers, Ethernet Stations or SNMP devices?
      
    

Thanks,
Mahnaz
T.RTitleUserPersonal
Name
DateLines
2689.1Alarms in v1.2 supports Global WildcardsMOLAR::ROBERTSKeith Roberts - DECmcc Toolkit TeamSat Apr 04 1992 01:0425
    Mahnaz,
    
    I cannot say for sure how many rules you can run for v1.2, but I would
    guess that 100 to 150 would be the limit for your VAX4000.
    
    But, if you are planning on running rules which are all the same except
    for the entity which needs to be polled -- DECmcc v1.2 Alarms supports
    global wildcards.
    
    You can write a single rule which will poll all of the specified entity
    class in a specific domain, that is:
    
            (node4 * maximum address > 50, at every 00:30:00)
    
    This rule, created in a specific domain, will poll each node4 entity in
    the domain .. repeating every 30 minutes.
    
    Be aware however, the entities are polled serially - one after the
    other, and not in parallel.  So this type of rule would need a
    reasonable polling interval like 30 minutes because in a domain with a
    lot of entities it may take a while to communicate to every entity.
    
    Hope this helps.
    
    /keith
2689.2ThanksMEHR::MEHRTue Apr 07 1992 19:504
    
    Thanks,
    
    Mahnaz
2689.3Alarms in v1.2 doesn't support Global WildcardsNEXUS6::BERNECICHFri Apr 10 1992 14:4051
Hi,
I've installed mcc ft 1.2.15 on my vs3100/76 vms 5-4.2. 32mb.

I try to  write a single rule which will poll all of the specified
in a domain entity but the creation fail.

$ Manage/Enter
DECmcc (X1.2.15)

CREATE MCC 0 ALARMS RULE Rech_state_on -
EXPRESSION         = (NODE4 * state = on , AT EVERY 00:10:00) ,-
PROCEDURE          = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM     ,-
EXCEPTION HANDLER  = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY           = " Node Reachable  "                    ,-
DESCRIPTION        = "  Node Reachable   "                   ,-
PARAMETER          = " NODE_ALARMS.LOG    "                        ,-
PERCEIVED SEVERITY = warning                                ,-
IN DOMAIN          = milan

MCC 0 ALARMS RULE Rech_state_on
AT 10-APR-1992 16:29:07
                        
Valid entity specification not found in alarm expression.


-- But for one entity


$ Manage/Enter
DECmcc (X1.2.15)

CREATE MCC 0 ALARMS RULE Rech_state_on -
EXPRESSION         = (NODE4 nebbia state = on , AT EVERY 00:10:00) ,-
PROCEDURE          = MCC_COMMON:MCC_ALARMS_LOG_ALARM.COM     ,-
EXCEPTION HANDLER  = MCC_COMMON:MCC_ALARMS_LOG_EXCEPTION.COM ,-
CATEGORY           = " Node Reachable  "                    ,-
DESCRIPTION        = "  Node Reachable   "                   ,-
PARAMETER          = " NODE_ALARMS.LOG    "                        ,-
PERCEIVED SEVERITY = warning                                ,-
IN DOMAIN          = milan

MCC 0 ALARMS RULE Rech_state_on
                              
AT 10-APR-1992 16:33:42

Entity created successfully.



Many Thanks
Enrico
2689.4TOOK::MINTZErik Mintz, DECmcc Development, dtn 226-5033Fri Apr 10 1992 15:475
You are trying what we call a "Global entity wildcard".
That is not supported in X1.2.15, but will be supported in EFT Update.

-- Erik

2689.5NEXUS6::BERNECICHFri Apr 10 1992 16:005
Re -1

Thank you Erik for quick reply

Enrico