HP3000-L Archives

August 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Fri, 18 Aug 2000 09:47:36 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (89 lines)
Steve,

IIUC, you took a 5.5 system and did an Update with a 6.0 CSLT.  This brought
the core operating system files up to 6.0, but the remaining supporting
files are still 5.5 versions. Specifically, you want to :RESTORE @.NET.SYS
from a backup that corresponds to the CSLT to get the correct version of
those files.

You are in somewhat of a sticky situation because there are also other files
in the SYS account that probably should be restored, i. e. newer versions of
programs and directory permissions for HFS files under 6.0.

While restoring the NET group to 6.0 revisions will fix your immediate
problem, the safest (and probably only supported method) of fixing this is
to re-update to 6.0 from HP tapes. This will take care of the remaining
operating system files that are out of date, and any post-processing jobs
that typically run during an update.

If your test system should look identical to the production system (other
than IP address of course) then you may get away with this:

START NORECOVERY NOSYSSTART   to bring the system up "vanilla" with no extra
processes running.

Using a 6.0 backup tape that matches the 6.0 OS version,

:RESTORE *t;@[log in to unmask]@.CONFIG.SYS,@[log in to unmask],/[a-z]@/;show;olddate;directory

You should make a copy of your NMCONFIG file before this :RESTORE command so
that you can put it back later. Otherwise you will lose the network
configuration because it will be overlaid by the production copy.

Again, this method is only if the test system should be identical in every
way.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio


----- Original Message -----
From: "Ritenour, Steven" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, August 17, 2000 14:33 PM
Subject: 6.0 Upgrade Problem!


> Hello All,
>    I have been planning to upgrade our e3000 for a while now.  I have
upgraded
> our test e3000 from 5.5 pp7 to 6.0 pp2 and selected reactive patches.  All
went
> rather well in this adventure, actually been running 6.0 on the box since
April.
> Well these last 2 day I have been involved in a Disaster Recovery Test and
after
> I successfully build our production box and had the user check it out I
thought
> I take advantage of the machine and actually update the server to 6.0 form
the
> CSLT prior to leaving the site.  Well after doing the UPDATE and booting
the
> system up I got the following errors when I attempted to start the Network
> Software, I believe this was discussed a few weeks back but got no hits in
the
> archives.  Can anyone offer help in resolving this problem.
>
> When I entered:
>
> NETCONTROL NET=LAN1;START         I received this error
>
> VERSION ERROR: UPDATE NUMBERS DIFFER (NETXPORTERR 4041)      and
>
> Encountered one of more errors while processing command (CIERR 4436)
>
> And when I entered
>
> NSCONTROL START
>
> Network services software versions do not match (CIERR 5077)
> NSCONTROL Command error (CIERR 5400)
>
> I Still have the DRP machine for a few more hours so any help offered
would be
> greatly appreciated.
>
> Steve Ritenour

ATOM RSS1 RSS2