Conference azur::mcc

4059.0. "Ressources for TSAM/ALARM" by CCEI0::RAOULT () Tue Nov 10 1992 05:53

	Hello,

	Having installed DECMCC BMS 1.2 on a customer site,I have to manage 
	about 150 node4 entities on their WAN and 100 terminal servers through
	TSAM(tsm was installed).	

	Due to the lack of memory (24 mbytes soon 48 ),I choose to survey the 
	events detected by the DEMSA router on each LAN/area (set up as 
	remote host event sink).

	With the notification services and the targetting I was able to 
	manipulate correctly all the events,keeping only several alarms for 
	critical aspects and performance purpose.
	
	Then I managed the reachabilty of my Terminal servers (split in 5 
	domains/partitions)with one rule/targetting per domain as follow:

$mana/enter
use ver
CREATE domain .A RULE A_ALL_SERVERS                      -
  EXPRESSION        = (TERMINAL_SERVER * -
			 SECONDS SINCE ZEROED < 200 , AT EVERY 00:03:00 )                               ,- 
  ALARM FIRED PROCEDURE	= MCC_COMMON:MCC_ALARMS_MAIL_ALARM.COM      	,-
  ALARM EXCEPTION PROCEDURE = MCC_COMMON:MCC_ALARMS_MAIL_EXCEPTION.COM 	,-
  CATEGORY          	= ""                          	,-
  DESCRIPTION       	=""      	,-
  BATCH QUEUE           = "ALARMS"                                 	,-
  ALARM FIRED PARAMETER	= "DECMCC"                              	,-
  SEVERITY	= critical	                                        ,-
  AUTO ENABLE	= yes
!
!
Assign Target DOMAIN A -
    Event Source = Domain LOCAL_NS:.A Rule A_ALL_SERVERS, -
    Event Name = "OSI Rule Fired", -
    Managed Object = "TERMINAL_SERVER #1", -
    Target Entity = "TERMINAL_SERVER #1"
!
exit
	
	Questions: 

	Is there a way to easily translate the ethernet address sent during
	a request load (Decnet event 0.3) to the terminal server name(occurs
	rule on event  + procedure + targetting ...),to avoid this polling
	and have a real time detection?

	If not,which kind of mechanism is used when I poll with on rule about
	20 T servers? 20 mop remote console at the same time?

	Thanks in advance.
	Best regards.
							Fabrice.	

Fabrice-

I can't answer your question about translating ethernet address in to
terminal server name.  Although if your code runs at DCL, you might
construct an FCL command which would query for the name or lat name using
the ethernet address like so:


MCC> show term 08-00-2B-26-AA-9B name

Terminal_Server 08-00-2B-26-AA-9B
AT 10-NOV-1992 19:56:53 Identifiers

                                   Name = LOCAL_NS:.ts.kayak

- or -

MCC> show term 08-00-2B-26-AA-9B lat node name

Terminal_Server 08-00-2B-26-AA-9B LAT
AT 10-NOV-1992 19:56:28 Characteristics

                              Node Name = "KAYAK"

Of course terminal server must be up and responding to get the second
attribute, so the first would be better in this situation.


You appear to be doing what I recommend to folks checking on reachability.
One things to keep in mind, which your rules seem to be OK with: TSAM can
not check on terminal servers in parallel, (I wish it could! its on my
wish list!)  Your last sentence indicated that you thought it might do that.
TSAM would check each of the 20 terminal servers in order, not going on to
the next one until the response from the previous comes back.  This bottle
neck is in TSAM, and can not gotten around by breaking alarms up or more
domains etc.

You must make sure the TSAM has enough time to get through all of the alarm
rules in the "AT EVERY" time you have alotted.

-Dave