[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::tsm

Title:Terminal Server Manager
Notice:For TSM Kit location see note 2.0
Moderator:MRLAT::RASPUZZI
Created:Wed Nov 05 1986
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:789
Total number of notes:2904

787.0. "test server x error" by CSC32::MAULUCCI () Tue Apr 22 1997 10:28

    I'm working an issue where a customer is running V2.1 TSM on a
    Vaxstation 4000 model 90. The system is not in a cluster, and is not
    running DECelms. 
    
    	When the customer does a "TSM>test server x" he gets a display
    similar to this one:
    
    ATVIC1: tsm test server *
    %TSM-E-NO_SERVICE_CKTS, No usable service circuits, server ATDT0C
    %TSM-E-NO_SERVICE_CKTS, No usable service circuits, server ATDT0D
    %TSM-E-NO_SERVICE_CKTS, No usable service circuits, server ATDT0E
    %TSM-E-NO_SERVICE_CKTS, No usable service circuits, server ATDT0J
    %TSM-E-NO_SERVICE_CKTS, No usable service circuits, server ATDT0K
    %TSM-W-TIMEOUT, No response from server T0101, partition PFSERVERS
    
    ATVIC1: tsm test server *
    %TSM-E-NO_SERVICE_CKTS, No usable service circuits, server ATDT07
    %TSM-E-NO_SERVICE_CKTS, No usable service circuits, server ATDT0H
    %TSM-W-TIMEOUT, No response from server T0101, partition PFSERVERS
    
    
    
    Different servers are listed each time. The service circuit is
    correctly defined as isa-0. A "connect node" from NCP or a "use server"
    from TSM always works. 
    
    I am having the customer check system for multiple tsm$configure.dat
    files. He is also going to upgrade to 2.1-05. 
    
    Any ideas ?
T.RTitleUserPersonal
Name		DateLines