Conference azur::mcc

  Andrew,

  Can you post the Rule you are creating ?

  /keith

    Forget it!  
    
    DECmcc does not support an FDDI interface on the host system.   The 
    USE DEFAULT QUALIFIER VIA PORT works for shows but not for the alarms fm.

    
    
     
    

    I thought VIA PORT got supported in ALARMS FM.
    
    Can anyone verify this?
    
    					Chris

    
          
    I tried the USE DEF QUAL VIA PORT prior to enabling an alarm and
    it worked fine.  But, I don't have an FDDI adapter.
    
    I should have tried this before I entered my note but I didn't see any 
    mention of the fix in the release notes so...         
    
    

    I have a customer who wants to set up DECmcc V1.3 in the following
    configuration to monitor two separate LAN segments:
    
    
    0----------+----------0  LAN1
               |
               |SVA-0
               |
            --------
            | MCC0 |
            --------
               |
               |SVA-1
               |
    0----------+----------0  LAN2
    
    
    They would like to be able to create alarm rules using the "VIA PORT"
    qualifier.  The would also like to receive SNMP traps from nodes on
    both LANs.  Using two IP addresses is allowable.  They would also like
    to receive DECnet events over both lines.
    
    
    How much of this is possible with DECmcc V1.3 and VMS ?
    
    -dan

re .4

>    I tried the USE DEF QUAL VIA PORT prior to enabling an alarm and
>   it worked fine.  But, I don't have an FDDI adapter.

	
	I am still unable to make bridge alarms work over FDDI interface
	even USE DEF QUAL VIA PORT prior to enabling an alarm .
	Other alarms , such as decnet and snmp alarms are working over 
	FDDI, only BRIDGE alarms arn't working. 
	DECmCC is V1.2 . I wonder if V1.3 would make a difference.

	A typical alarm looks like this :

	create domain elizabeth_st_building rule -
	ho_bridge_620_siteb_bridge_line_2_framing_errors -
	expression = (change_of(bridge ho_bridge_620_siteb line 2 -
	framing errors , *,*), at every 00:02:00), -
	alarm fired proc = hec_net:mcc_alarms_mail_alarm.com , -
	alarm exception proc = hec_net:mcc_alarms_mail_exception.com , -
	category = "Cable framing errors" , -
	description = "HO cable A framing errors ", -
	Batch queue = "alarm$batch" , -
	alarm fired parameter = "mcc_mail" ,-
	auto enable= no,-
	severity = warning

	
	A show bridge command can be forced via the FDDI interface with
	the VIA port qualifier. But how does one make the bridge alarms 
	take the FDDI path ?? Anyone done this before ?
	
	This is actually a customer problem. I need to let him know if
	it is meant to work ! who can I talk to to get a definitive answer ?


Andrew

RE: 4783.6

>   A show bridge command can be forced via the FDDI interface with
>   the VIA port qualifier. But how does one make the bridge alarms 
>   take the FDDI path ?? Anyone done this before ?

  I took a look at the "Alarms and Notification Services Use" book
  (first the v1.3 version, then v1.2) and found a page labelled:

	"Specifying Routing Information for Alarm Rules"

  (page 4-18 in v1.3 book, I was using BOOKREADER for the v1.2 book).

  It says that for FCL, VIA PORT is passed on the ENABLE command.

  Example given is:

	ENABLE DOMAIN MYDOMAIN RULE CHICAGO_HUB, VIA PORT BNA-0

  For a DEMFA on OpenVMS, replace "BNA-0" with something like "MFA0:". 

  (Yipes! The example device given, "BNA-0", won't work for STATION,
   CONC, or BRIDGE entities since the hardware designation, "ETA0:",
   is what's needed).

  Hope this helps (and works!).

						Chris

    Thanks for the info, Chris.  It looks as though I will be able to do
    everything I requested in (.5).  
    
    As a result, we are in a perfect position to be able to sell more
    DECmcc.  
    
    ;-)  Dan

    
    RE .7
    
    Chris, Thanks for the pointer. Bridge alarms now works over FDDI
    interface.
    
    Andrew.