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

Jim mckinneyj at saic.com
Wed May 8 07:40:51 EDT 2019


On Friday, May 3, 2019 at 4:36:22 PM UTC-4, Michael Moroney wrote:
> Carlos Murillo <ce.murillosanchez at gmail.com> writes:
> 
> >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.
> 
> Why do you think this high interrupt stack time is cluster-specific and not just
> network-specific? If it's hardware (likely because of the age of everything)
> you'll see high interrupt stack time when doing TCP/IP or any networking. Anyway, 
> Hoff's suggestions will disable clustering.

How stable is the network where you're connecting to? Do adjacent systems experience any issues when this one gets busy? In days long past I've observed instances where misconfigured routers (asymmetric routing?), duplicate IP address, etc... have resulted in what amounts to a broadcast storm that overwhelm the slower VAX NICs and is locally observed as the system living on the interrupt stack.




More information about the Info-vax mailing list