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

Conference help::decnet-osi_for_vms

Title:DECnet/OSI for OpenVMS
Moderator:TUXEDO::FONSECA
Created:Thu Feb 21 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3990
Total number of notes:19027

3917.0. "TSM: CCR-E-NORESOURCE once again" by UTOPIE::BRAUN_R () Thu Apr 03 1997 13:23

(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
3917.1Need some more information...DAVIDF::FOXDavid B. Fox -- DTN 285-2091Fri Apr 04 1997 10:327
I've been running TSM fine on my DECnet Plus system for quite some time.  What
version of VMS (Alpha or VAX?), DECnet, and TSM are you running?

In my case, I'm running OpenVMS VAX V6.2, DECnet PLUS V6.3-ECO06, and TSM
V2.1-05.  I don't have any performance issues.

	David
3917.2Sounds like TSMBULEAN::TAYLORFri Apr 04 1997 17:0510
    
    Hi,
    
    This sounds like a TSM problem that should have been
    fixed back in October.
    
    Cheers,
    
    Pat
    
3917.3Thanks! It was MOP!UTOPIE::BRAUN_RTue Apr 08 1997 08:5327
        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