[Info-vax] 3par ssh connection

[Kerry Main]

> -----Original Message-----
> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Simon Clubley
> via Info-vax
> Sent: May 20, 2019 1:17 PM
> To: info-vax at rbnsn.com
> Cc: Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP>
> Subject: Re: [Info-vax] 3par ssh connection
> 
> On 2019-05-20, Kerry Main <kemain.nospam at gmail.com> wrote:
> >
> > While I do not have a 3par san in my lab (I wish!), but I have been
> > using SSH via the new VSI TCPIP stack (based on Multinet) and Multinet
> > v55 (easy to flip back and forth btw) with no issues connecting
> > between Windows
> > (Putty) and latest versions of OpenVMS AXP and I64 systems with no
> problems.
> >
> 
> Hello Kerry,
> 
> From the above, it sounds like you are using VMS as the server, not the
> client. The problems are in both directions, but they really start when
you are
> using VMS to make outgoing connections to non-VMS systems, as opposed
> to when you are accepting incoming connections to your VMS systems.
> 
> Simon.
> 

Agree, but lets not forget that the native TCPIP stack in OpenVMS is likely
7-10 years behind the TCPIP technology that comes with current versions of
Multinet.  The new VSI TCPIP stack is a huge leap forward in capability to
meet todays standards. 

Having stated this, like any product, one should first verify if the latest
patches in Multinet have been applied.

Reference: (see SSH patches released July, 2018)
<http://www.process.com/support/recommended_patches.html>


Regards,

Kerry Main
Kerry dot main at starkgaming dot com