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

[Carlos Murillo]

On Tuesday, May 7, 2019 at 7:10:29 PM UTC-5, Carlos Murillo wrote:
> 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.
> > 
> > -- 
> > Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
> > Microsoft: Bringing you 1980s technology to a 21st century world
> 
> Hi Simon;  I finally had time to sit at the machine.  I am running TCP/IP Services V5.0-9.  Indeed, if I login at the serial console with no telnet sessions open, the cpu is mostly idle.  As soon as I try to telnet into it (even before authenticating the user), the interrupt stack mode usage goes through the roof. Once in the telnet session I tried
> 
> $ set terminal /device=vt100
> 
> but that did not change anything.
> 
>  So what is the solution? Can I just grab a higher-numbered version of TCP/IP Services and install it? Or is there a workaround?
> 
> Carlos.

Duh!  I found it: just set TERM=vt100 in the shell _before_ invoking telnet.

carlos.