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

[Dave Froble]

On 11/4/2021 7:07 PM, Rich Jordan wrote:
> On Monday, November 1, 2021 at 1:40:00 PM UTC-5, Volker Halle wrote:
>> Rich,
>>
>> thanks for testing and sharing your notes. So it really looks like an upgrade vs. install issue. And it affects the LAN interface, irrelevant of the protocol used.
>>
>> Is the 'link LED' lit on the physical LAN interface ?
>>
>> SHOW DEV/FULL EIA0 shows 'no link' - right ?
>>
>> Please test with the system parameter file from the freshly installed system disk.
>>
>> Volker.
>
> Replacing the parameter file on the upgraded system with the one from the clean VSI install did not make a difference WRT the network; it did cause some complaints because DECwindows could not start, but everything else did after I updated SCSNODE and SCSSYSTEMID in the copied file to match the upgraded system's name and ID.
>
> I tried a second NIC port for the hell of it, but none of them come up.  Counters show the same errors as before.
>
> I'm contacting the customer's VSI rep to find out how we can put in a support request; hopefully that side of things has been taken care of.
>
> Rich
>

I don't know if this is your problem.  It was my problem.

By default, DECnet Phase IV installation and configuration will enable DECnet protocol on all available interfaces on the system.  Once configured, the system administrator would want to go into NCP and purge all lines and circuits that are not needed from the database.

     > $ MCR NCL PURGE CIRCUIT EWA-1 ALL
     > $ MCR NCL PURGE LINE EWA-1 ALL

Then use STARTNET to start DECnet.

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486