upgrade vms 7.3-2 to 8.3 problems

[Volker Halle]

Roger,

there must be some LAN protocol, which changes the MAC address to the 'OLD' DECnet MAC address.

What does MC NCP LIS EXE CHAR report ?

Look at all the LAN protocols with:

$ ANAL/SYS
SDA> SHOW LAN

Consider to put an EXIT at the beginning of SYSTARTUP_VMS.COM and see whether you're then running with the hardware address as the current MAC address. Then look thorugh your startup and start individual products until the MAC addresses changes...

Volker.

[Volker Halle]

Roger,

find out your current SCSSYSTEMID via:

$ MC SYSGEN
SYSGEN> SHOW SCSSYSTEMID
SYSGEN> EXIT

SYSGEN> WRITE CURRENT changes the modification date of ALPHAVMSSYS.PAR !

How did you run AUTOGEN ? Did you look into SYS$SYSTEM:AGEN$PARAMS.REPORT for any errors ?

Volker.

[robert70]

with sysgen
show scssytemid is showing
65534
so yes definitely still holding the wrong value as should be 65533

[Volker Halle]

Roger,

then again: HOW are you running AUTOGEN ? Leave the SYSTARTUP_VMS.COM checking until we've figured out, why AUTOGEN does not work the way you think...

Volker.

[robert70]

OK

I ran autogen by doing

$ set def sys$update
$ @autogen

this didnt ask me any other questions
just eventually returned me to the $ prompt

I have subsequently used
$ MCR SYSGEN
set scssystemid 65533
write current

and the nrebooted which has changed the mac address to AA-00-04-00-FE-FF

But I agree with you that there is something not write with the AUTOGEN phase?
I notice that a file created called setparams.dat still contains the old scssystemid 65534!

[robert70]

The AGEN$PARAMS.REPORT has a line near the top which says................

*** No Changes will be done by AUTOGEN **
The values given in this report are what autogen would have set the parameters to.

why is this not doing doing changes live.

[Volker Halle]

Roger,

you need to run:

$ @SYS$UPDATE:AUTOGEN GETDATA SETPARAMS

Then everything should be fine !

Volker.

[robert70]

aha
thanks
I'll try that

[Volker Halle · Accepted solution]

Roger,

just running @SYS$UPDATE:AUTOGEN without ANY parameters just runs the GENPARAMS phase and does NOT write the system parameters, which would be done in the SETPARAMS phase.

Now everything should have been explained and you're ready to re-connect the network cable.

Volker.

[robert70]

Volker,

You are a STAR!
Superb everything looks like its working now
UPGRADE back on network
no problems so far!

Thanks you very much indeed

Regards
Roger

[Volker Halle]

Roger,

one possible culprit for changing the MAC address to the DECnet MAC address - even if NOT running DECnet itself - may be LAT.

When LAT creates a LINK on a LAN adapter, LATCP will - by default - use an implied CREATE LINK/DECNET and change the MAC address to the value specified in SCSSYSTEMID.

Volker.

[robert70]

SOUNDS LIKE IT COULD BE WHAT WAS HAPPENING HERE.

We are going to upgrade our LIVE box at some point so we may encounter the same type of problems.

We will see.
Thanks

[John-Wu_1]

Hi robert70:
I am now planning to upgrade my system OVMS 7.3-2 to V8.3 on Alpha server, could you kindly help to confirm the update kits(UPDATE-1200 ):
is it "SYS FAcility Patch Kit for OpenVMS Alpha V7.3-2 VMS732_SYS-V1200 " or "UPDATE Consolidated Patch Kit for OpenVMS Alpha V8.3 VMS83A_UPDATE-V1200 "

Thank you very much in advance!

[robert70]

its the 2nd one that I used for my upgrade
cheers
robert