[Info-vax] DECnet Phase IV broken after VSI update

[cao...@pitbulluk.org]

On Friday, October 29, 2021 at 7:59:37 PM UTC+1, Rich Jordan wrote:
> On Friday, October 29, 2021 at 1:02:18 PM UTC-5, Volker Halle wrote: 
> > Rich, 
> > 
> > so you're saying: DECnet IV works after a fresh install of VSI VMS V8.4-2L1, but doesn't after an upgrade from HP VMS V8.4 ? 
> > 
> > Any DECnet OPCOM messages ? 
> > $ MC NCP SHOW KNO LINE COUNT 
> > $ MC NCP SHOW KNO CIRC COUNT 
> > DECnet license active ? 
> > TCPIP started AFTER DECnet ? 
> > 
> > Volker.
> Volker 
> License is active as part of VMS FOE pak; DECnet is in end-node state. 
> TCPIP was not started during this boot; it was manually started in one previous to test, and it is after DECnet startup in the startup procedures. 
> I DO need to test it again to make sure I'm not reporting a false positive about its status but I'm swamped, later today or next week to confirm that. 
> 
> The line count is all clear except 
> 
> Line = EIA-0 
> ... 
> 4103 Send failure, including: 
> Carrier check failed 
> 
> 
> The circuit count is clear except 
> 
> Circuit = EIA-0 
> 31 Circuit Down 
> 
> Note that I had the circuit turned off to stop all the operator messages, and it restarted the count when I re-enabled it to post this. Its up to 55 now. 
> 
> I tried a different switch and cable also, no difference, and again both old and new switch worked fine when booted from old HP VMS or the fresh install of VSI VMS. 
> 
> 
> I'll follow up with a TCPIP startup and test as soon as I can; everyone decided to have their peecees do diaper dumps today. 
> 
> I am not currently connected to the iLO but the iLO _is_ connected to the same switch as the server data link (only one server NIC has been connected at a time).

I've recently upgraded to VSI V8.4-2L3 on an RX4640 from L2 without any DECnet IV issues over ethernet circuits, except for issues with LAT. I solved that problem
by using separate interfaces for DECnet, TCP-IP and LAT.

Keith