[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

785.0. "TSM: CCR-E-NORESOURCE once agian" by UTOPIE::BRAUN_R () Thu Apr 03 1997 16:26

(cross-posted in TSM and DECNET-OSI_FOR_VMS)

Hi all,

our customer has a strange problem:

2 identical nodes in a cluster:  OVMS 6.2, DNSOSI6.3, ECO5,   TSM2.1

9 DECserver700-08.

From one node all DECservers can be used with TSM USE SERVER ...
From the other node, a single DECserver (always the same) can
not be used, the famous error message is:

    %CCR-E-NORESOURCE , insufficient Resources
    %TSM-E-CONNECT , connection to terminal server failed 

This is not a sporadic problem (quota,..), it's a constant problem.
All other DECservers have no problem.
From the TSM-database, all DECservers seem to have identical setup,
MAC-address o.k,...

There are no MOP clients for these DECservers.
 
I'll provide a CTF-Trace of the MOP-circuit (but have to wait for customer's
authorization to log in again).
 

Any help will be highly appreciated.

Thanks,
Ralph




 



T.RTitleUserPersonal
Name
DateLines
785.1try some of these ideas!CSC32::D_SHAVEYFri Apr 04 1997 16:5215
    Ralph,
    
    	What does an:
    
    $set host/mop etc.     get from this other system. 
    
    On the terminal server:
    
    local>show server status
    
    check the cpu and memory on the bottom left to see how high they are
    too. If the terminal server has an IP address, can you telnet to it?
    
    Darrell Shavey
    csc32::d_shavey
785.2MOP restart!UTOPIE::BRAUN_RTue Apr 08 1997 11:4828
    Hi,
    
    problem was in MOP, MOP-restart solved the problem.
    Should be some hangup due to fast reconnect or similar.
    
    
    I have sent TSM ECO 5 to the customer:
    (Rel. Notes)
      .
      .
      .
    5.2  Reconnect Delay Under DECnet/OSI
    
    A delay of 2 seconds has been added when reconnecting to the
    same server that was previously connected in the TSM
    session under DECnet/OSI. This allows sufficient time for the
    NET$MOP process to disconnect its MOP connection after TSM
    disconnects.
    In previous versions, users would recieve CCR or circuit error
    messages when attempting to do two USE SERVER commands in a row
    to the same server, or when disconnecting and immediately re-
    connecting, especially when doing these commands from a command
    file.
    
    
    Regards,
    Ralph