[Info-vax] Opa0 in TIMOUT state

[abrsvc]

On Wednesday, July 7, 2021 at 2:27:57 PM UTC-4, Jan-Erik Söderholm wrote:
> Den 2021-07-07 kl. 20:02, skrev abrsvc: 
> > On Wednesday, July 7, 2021 at 1:52:07 PM UTC-4, Volker Halle wrote: 
> >> Dan, 
> >> 
> >> could this be related (you didn't specify type of system and/or OpenVMS version) ? 
> >> 
> >> https://community.hpe.com/t5/Operating-System-OpenVMS/OPA0/td-p/4049992#.YOXpGDNxfcs 
> >> 
> >> Volker. 
> > 
> > I should have known better, but the configuration is as follows: 
> > 
> > VAX 4000 model 108. OpenVMS version 7.3 
> > 
> > The error count appears to increase when any reply/all is performed or any operator message is sent to OPA0. 
> > 
> > This is in a virtual environment where OPA0 us channelled to a socket connection. Unknown details about that connection. 
> > 
> > Dan 
> >
> Has the socket simply lost it's connection? 
> Is it something remotely that connects to this socket? 
> 
> I would expect a lost socket connection to look like 
> an LA120 that is out of paper... 
> 
> > Unknown details about that connection... 
> 
> Probably the key words here.

I would have expected the opa0 port to be in an Xoff state if the socket connection were severed rather than just a timeout state.  Am I correct in this?

The terminal state was as expected except for the timeout state.