[Info-vax] PEA0 error

[Mark Berryman]

On 9/10/21 7:04 AM, David Jones wrote:
> On Thursday, September 9, 2021 at 8:36:55 PM UTC-4, Mark Berryman wrote:
>> $ show dev/full eia0
>>
>> Device EIA0:, device type i8254x, is online, network device, error
>> logging is
>> enabled, device is a template only.
>>
>> Error count 0 Operations completed
>> 0
>> Owner process "" Owner UIC
>> [SYSTEM]
>> Owner process ID 00000000 Dev Prot
>> S:RWPL,O:RWPL,G,W
>> Reference count 0 Default buffer size
>> 512
>> Current preferred CPU Id 1 Fastpath
>> 1
>> Current Interrupt CPU Id 1
>>
>> Operating characteristics: Link up, Full duplex, Autonegotiation.
>>
>> Speed (Mbits/sec) 1000 Adapteri82545 VMware (Gigabit
>> Ethernet)
> 
> I gave up trusting autonegotiation to reliably get it right. A mismatch between
> full and half duplex which let the device interchange enough packets to see
> the other nodes but the virtual circuits would be unstable.

The first autonegotiation standard in '95 that came with FastEthernet 
had interoperability issues, causing many folks to cease to trust it.

However, the 802.3ab Gigabit Ethernet standard in '99 made 
autonegotiation mandatory for Gigabit connections, and it continues to 
be for higher speeds, since there are now more features than just speed 
and duplex to be negotiated (flow control being a significant one).  The 
interoperability issues were addressed and, above 1G, half-duplex no 
longer exists.

> 
>> $ mcr lancp
>> $ LANCP> show dev/char eia0
>>
> 
> What does show dev/counter say with regard to errors (collisions and carrier
> check failures)?
> 

There are no errors on the Ethernet interface.  I should have noted 
that, when the node is configured as a standalone node, both DECnet and 
IP run just fine over this interface.

Mark Berryman