Conference marvin::x25psi

3743.0. "EMERGENCY problem with MAIL hung when using X25-MAIL" by ULYSSE::DIVINE (Denis DIVIN� @VBO (7)828-5450 (Valbonne-FRANCE)) Wed Apr 02 1997 15:35

Hello,

I'm currently facing a strange and EMERGENCY problem.

Until last friday, I was sending mail over X25 from my production system (NONOS)
using another system (VALPUB) on the same LAN to 3 customers (in New-York, 
London and Singapore).
It was working fine.Please find the topology of my LAN

  |-------------------------|
    |                |
 -------         --------
| NONOS |       | VALPUB |----------> connection to X25/X29 world --> NY,LO,SI
|       |       |        |            
 -------         --------
VAX4000-200     MicroVAXII
VMS V5.5-2      VMS V5.3-1
PSI V4.3        PSI V4.2
DECnet IV       DECnet OSI


This past Saturday, I replace my VAX4000-200 by a VAX4000-700.
The system disk is a copy of the old one which has been upgraded to VMS V5.5-2H
(to have the drivers for the VAX4000-700)
Since then almost everytime, the process hang when sending mail from NONOS.
It's working fine when sending mail from VALPUB directly.

I can received X25 mail from the customers, or connect over X29 to the remote
systems without problem.

Yesterday, I applied the CSCPAT_0527016 (V4.3 Fix Kit) and rebooted my system,
but I still have the same problem.

I'm not the only one having a system which use VALPUB as gateway on the LAN,
and it seems that it's working fine for the other folk (even in PSI V4.3)

I saw in this notes conference that it exists a PSI V4.3A.
I saw as well in this notes conference a lot of problem with MAIL hang,
when sending big file, but in my case I'm sending file less than 50 blocks.

My next questions are :

1] Could it be that my problem is due to the fact that my Ethernet interface
   on the new system is too FAST ?
   Is there any parameter to increase/decrease on one of the 2 systems ?

2] Is VAX PSI V4.3A will fix my problem ?
   If so, there can I get/request this update kit ?

3] If VAX PSI V4.3A will not fix the problem , will it work if I down-grade 
   to PSI V4.2 ?

4] I wanted to use poor man routing to send mail using VALPUB
   but everytime I have the following error message

     MAIL>send
     TO : VALPUB::PSI%dte_number
     %MAIL-E-LOGLINK, error creating network link to node LOCSC
     -SYSTEM-F-IVDEVNAM, invalid device name

   On VALPUB, I have the following OPCOM message

%%%%%%%%%%%  OPCOM   2-APR-1997 10:50:21.66  %%%%%%%%%%%
Message from user DECNET on VALPUB
DECnet event 7.10, call failure
From node 51.92 (VALPUB),  2-APR-1997 10:50:19.20
Module X25-PROTOCOL, Direction = Outgoing, Call failure = Insufficient resources
Remote DTE = 023535239

   How can I get it running ,at least as a workaround ?
 
In summary, it use to work last week and now I facing an EMERGENCY problem
as I'm using X25 MAIL for a call handling system with these 3 external customers

Let me know if you need further details and if needed how can I escalate this
problem to get it fix asap.

Thank's for any help/support.
   
Regards,

/Denis D. (ECCC/EBS Technical Support)

    Your diagram shows VALPUB running DECnet/OSI and P.S.I. V4.2, if this
    it true then this is a unsupported configuration and I am surprised
    that it works at all.  DECnet/OSI includes the all X.25 functionality
    of P.S.I. therefore there is no separate P.S.I. kit for DECnet/OSI.

    If VALPUB is really a DECnet Phase IV system with P.S.I. V4.2 then you
    probably need to upgrade P.S.I. V4.3 + fix kit.  I vaguely remember a
    problem where things broke on the connector system when working with
    fast access systems.

    Finally P.S.I. V4.2 and V4.3 are both unsupported and you should really
    look at upgrading both these systems to DECnet/OSI.

    Andrew.