[Info-vax] How to convert a cluster-seeking vax into a networked stand-alone machine

[Carlos Murillo]

On Friday, May 3, 2019 at 4:32:09 PM UTC-5, Simon Clubley wrote:
> On 2019-05-02, Carlos Murillo  wrote:
> > Hello everyone;
> >
> > I've got a vaxstation 4k/60 running OpenVMS 7.2 that apparently has network-induced problems.  The cpu spends 80% + of the time in interrupt stack mode, which goes to zero if the AUI transceiver is disconnected.  Trying to isolate the problem, I've disabled MOP serving, MSCP serving, pretty much all server processes.  But of course, it still want it to do TCPIP.  How can I configure it so that nothing cluster-related is involved in its sysgen-related settings? Basically a TCPIP-speaking stand-alone workstation.
> >
> > carlos.
> >
> 
> Given the VMS version, are you running TCP/IP Services version 5.0
> (and exactly that version) ?
> 
> If you are, are you using telnet to connect to your system ?
> 
> If you are using telnet, have you set the terminal type on your
> terminal emulator to one that is recognised by VMS ?
> 
> TCP/IP Services V5.0 had a bug in it which meant that continuous
> network traffic was seen when using telnet if the telnet client
> didn't use a recognised terminal type.
> 
> If your site security policies allow it, and _ONLY_ if they allow it,
> use Wireshark or similar to monitor the traffic. If you are seeing
> heavy traffic on port 23, then this may be the problem.
> 
> Simon.

Thanks Stephen, Michael, Robert and Simon.  I had already disconnected the AUI transceiver and the interrupt stack usage went to zero, so I did know that the issue is related to the network components. I don't have an AUI loopback, but I suppose I can wire one up. 
 I've been trying to turn off one network component at a time.  Clustering was an obvious one, especially since I am not really using the system in clustered mode (my only other physical vax is a vaxstation 2000 running 5.5-2).  I do use telnet to connect to it, but I also have a serial terminal as a console. The interrupt load is present even when there is no open telnet session.  I'll check the version of TCP/iP services when I'm back home; I think it was  5.0 indeed.

carlos.