[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

2900.0. "TS_AM T1.0.7 Problem" by FILTON::EVANS_M () Thu Apr 30 1992 15:42

    MCC		T1.2.7
    TS_AM	T1.0.7
    VMS		A5.5
    
    I am running a field test of network management services (NMS) at a
    site in Bristol. I am suffering a problem with the terminal server
    access module T1.0.7.
    
    New installation of the terminal server access module. Installation was
    clean. I am having problems registering all types of terminal servers and 
    are receiving a partial registration and the following error messages.
    
    MCC>Register terminal_server dsv230 address = 08-00-2b-16-05-05, type ds300
    
    Error returned	DNA4 problem encountered updating DECnet database
    			error 347
    
    When registering using the iconic map, and including the DECnet address
    in the details screen the same error is returned. 
    
    If the DECnet address is not included in the details screen a different 
    error message is returned :-
    
    Error returned	Communication with target has been interrupted.
    
    After this partial registration the termial server cannot be used
    because all operations receive the same message above.
    
    
    The DNS back translation .MCC_TERMINAL_SERVER_BACKTRANSLATION is set up
    ok and other access modules can register Bridges,Node4,s etc.
    
    The servers are acessable using TSM from the MCC platform.
    
    Please can someone point me in the right direction.  
    
    
    Thanks
    
    
    Mat Evans
T.RTitleUserPersonal
Name
DateLines
2900.1QuestionsTOOK::FONSECAI heard it through the Grapevine...Fri May 01 1992 18:2313
Mat-

I'm equally baffled by your problems.  From your example, I can not
see why you would be getting a DNA4 error.  TSAM does not go out to the
DNA4 AM unless you provide a DECnet address.

If you had previously attempted to register this with a DECnet address,
and did it again without, then there might be reason.  Since you are familiar
with TSM, I'm wondering if you used the TSM to TSAM database convert utility?

Also, did you have proper privs to access the DECnet database?

-Dave
2900.2The SolutionFILTON::EVANS_MThu May 07 1992 08:448
    Dave,
    
    Thanks for your reply. The solution was as simple as the access to the
    Decnet account. The TS_AM is now performing perfectly.
    
    Cheers
    
    Mat Evans