[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

5125.0. "Need Input on Managing Vitalink" by TRIGG::TRIGG::CLAYTON (Merlin Clayton DTN 445-7217) Fri May 28 1993 10:49

Does anyone have any pratical experience working with the Vitalink AM with
V1.3 of MCC?

In a few weeks I'm going to be delivering a conculting engagement for EMS v2.3
and one of the tasks will be to install and configure the Vitalink AM.

I'm interested in any war stories - good or bad - relative to VBAM.  

I'm also interested in any tips on how to use the AM for effective
management of the Translans - e.g., alarm rules, attributes to define alarms
for, launched appls for console interface, etc.

Any input will be greatly appreciated.

Thanks.

Merlin

T.RTitleUserPersonal
Name
DateLines
5125.1No problem so farMQOSWS::F_MONETTEMontreal Sales SupportTue Jun 01 1993 14:2922
I did install it on V1.3 without any problems. You need to
check the software version of the specific bridges:

	Translan 320	20.2.2 (minimum)
	Translan 335	10.4.2 (minimum)
	Translan 350	10.4.2 (minimun)
	Translan III	6.10.2 (minimum)


I did also define some alarms rules on port module state
attributes without any problems (it works well). it almost
like a Lanbridge 200.

Didn't try any lauched appls but IT DIDN'T WORK WITH THE
POLYCENTER ALARMS MANAGER. As soon as you want to define
alarms rule on port #, the application just crashed.

It works fine using the IMPM or FCL.

Regards,

Francois
5125.2Port requires unsupported datatype in almmgrGOSTE::CALLANDERTue Jun 01 1993 15:1313
    The port problem with the alarm manager is known. The Port entity
    requires support of an UNSIGNED8 (1 byte) datatype that the
    publically available version of the alarm manager doesn't support.
    
    I have made an updated copy of the alarm manager available to a
    number of sites utilizing MCC to manage Translan bridges. If
    this is something you require please let me know. If you can
    wait for port support, the field test version of the alarm manager
    product (no longer prototype) should be available in a few
    weeks.
    
    jill
    
5125.3VBAM works hereZUR01::SCHNEIDERRThu Jun 03 1993 03:0021
Merlin,

We use the VBAM, too. I had to test it out for a customer who was not quite 
shure to use the VBAM or the new SNMP features from the VITALINK.

With the VBAM all I tested runned well. The problem is (earlier discussed) that 
the TRANSLANmgmnt-protocoll doesn't return all the parameter you can see and 
modify on the Translans console-port. So you can't do everything from remote.

If you wan't to use SNMP there is the same story. The whole SNMP agent is only 
implemented in the Translan 350. The Translan III supports only a subset of the 
SNMP features. The SNMP agent on the Translans has a problem, it crashes from 
time to time. This means the bridge itself works, but you can't access it via 
SNMP. The second problem is that the Translan doesn't answer properly to ARP 
requests. So you have to do a permanent ARP entry on your machine, to register 
the Translans.

At the moment I would recomend to use the VBAM.


Roland
5125.4New Version Of Alarm Manager?ANGLIN::CLAYTONMerlin Clayton DTN 445-7217Tue Jun 08 1993 14:4619
    
>>    I have made an updated copy of the alarm manager available to a
>>    number of sites utilizing MCC to manage Translan bridges. If
>>    this is something you require please let me know. If you can
>>    wait for port support, the field test version of the alarm manager
>>    product (no longer prototype) should be available in a few
>>    weeks.
    
jill,

Could you make this copy of the alarm manager available for my customer
since he wants to manage Translan bridges and use the alarm manager?

Thanks.

Merlin