[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

3428.0. "Vitalink Alarms Time Out" by ODIXIE::PEACOCKR () Fri Jul 24 1992 14:16

    I have been having trouble with alarms on Vitalink bridges.  The rule I
    am using checks for module state change from forwarding to *.  The
    interval is every minute (the customer is very adamant about having
    this polling interval).
    
    The problem we are having is that some of the bridges will fire the
    exception routine saying that MCC can't communicate with target.  This
    happens so much on some of the bridges that I had to change the
    exception procedure to use logging instead of mail.
    
    My concern is that there may be an instance where someone actually
    disconnects the Translan or some real condition causes a failure to
    communicate and we won't be able to tell the difference. 
    
    Is there a Vitalink or DECmcc parameter that we can adjust so the alarm 
    won't time out so much or so easily?
    
    Thanks,
    
    Rick

T.R Title User Personal
Name Date Lines

3428.1 Check 1551.* ANTIK::WESTERBERG Stefan Westerberg DS Stockholm Fri Jul 24 1992 19:51 19

T.R	Title	User	Personal Name	Date	Lines
3428.1	Check 1551.*	ANTIK::WESTERBERG	Stefan Westerberg DS Stockholm	`Fri Jul 24 1992 19:51`	19
	> Is there a Vitalink or DECmcc parameter that we can adjust so the alarm > won't time out so much or so easily? Sorry to say Rick, there isen't that much you can do about it until the next version of the Translan AM comes out on the market. If you want some history reading about this subject check entry 1551 in this conference. But the best trick to reduse the exception is to start the alarms rule with at least a 3s interval. /Stefan P.S. The error messages described in 1551 changed it's nature when upgrading to VMS 5.4-3 or 5.5 to be "Cannot Communicate with target" or "Communication with the target has been interupted".

>    Is there a Vitalink or DECmcc parameter that we can adjust so the alarm 
>    won't time out so much or so easily?
    
Sorry to say Rick, there isen't that much you can do about it until the
next version of the Translan AM comes out on the market.

If you want some history reading about this subject check entry 1551 in this
conference.

But the best trick to reduse the exception is to start the alarms rule with
at least a 3s interval.

/Stefan

P.S. 

The error messages described in 1551 changed it's nature when upgrading to
VMS 5.4-3 or 5.5 to be "Cannot Communicate with target" or "Communication with
the target has been interupted".