Re:
> 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
> NETCONTROL NET=LAN1;START I received this error
>
> VERSION ERROR: UPDATE NUMBERS DIFFER (NETXPORTERR 4041) and
Most likely candidate: leftover networking software from a prior release.
This has happened to a number of people, including us!
IIRC, we used ";OVERRIDE" on the NETCONTROL (?) as a temporary workaround,
and eventually purged a "MAST" file for the old software and re-streamed
jconfjob.net.
NMMAINT,6 will show you the version of all the various networking
modules/subsystems you have. Look for any line with a version below all
the rest. IIRC, 6.0 versions show up as: B0300xxx. Look for anything
less than that, or B.??.?? or B????xxxx. ... those are modules that
are probably old and causing a problem.
The rest of this note is snippets from HP3000-L:
>Could you please check for the presence of the following files:
>
>IPCINT.NET.SYS
>X25STAT.NET.SYS
>X25CHECK.NET.SYS
>X25SERVR.NET.SYS
>
>If some or all of these files are present, I would like you to rename
>them and restream JCONFJOB.NET.SYS.
--------------------------------------------------------------------------------
Subject: NETCONTROL VERSION ERROR MODULE NETXPORTERR 4044 (was HELP)
From: Mike Hornsby
Date: Monday, November 23, 1998 9:12:46 AM
Rick wrote
>Ok. I have been waiting for a callback from HP support on a problem I am
>having after updating my system to 6.0
>: BAD NETCONTROL START;NET=LAN1
>VERSION ERRORMODULE NETXPORTERR 4044
Assuming that your update went ok the first thing I would check is NMMAINT
it may tell you
what is conflicting. Probably some datacom software that was not in your new
subsys. You
can try a:
NETCONTROL START;NET=LAN1;OVERRIDE
NSCONTROL START;OVERRIDE
Be warned that HP probably won't support this but it may work until you can
get the versions fixed.
Mike Hornsby
[log in to unmask]
--------
Subject: Re: NETCONTROL VERSION ERROR MODULE NETXPORTERR 4044 (was HELP)
From: Richard Bayly
Date: Tuesday, November 24, 1998 7:00:37 AM
The products on your subsys tape might be different on your 6.0 tape to your 5.5
tape. This could cause old versions of the network services mast files to be in
net.sys. Then when you stream jconfjob and do a nscontrol start it finds the
version mismatch and aborts. The usual problem I have seen here is that NS is
not on the new versions subsys tape. If you do a listf @mast.net.sys you will
see a number of mast files, which correspond to different services, such as VT.
By renaming the appropriate mast file and restreaming jconfjob the problem is
usually solved. In my experience NSSMAST is the usual culprit. Try renaming this
and restreaming jconfjob. The following are the mast files and their associated
products:
Network Products "MAST" files
Token Ring/iX Link NSMAST, VTCMAST, VTOMAST, VTSMAST
LAN3000/XL Link NSMAST, VTCMAST, VTOMAST, VTSMAST
NS3000/XL NET Services NSMAST, VTCMAST, VTOMAST, VTSMAST, RPMMAST,
NSSMAST
ARPA Services/iX (FTP) NSMAST, VTCMAST, RPMMAST
HP FTAM 3000/iX NSMAST, VTCMAST, RPMMAST
SNA DHCF/XL VTCMAST
Cooperative Services HCSMAST
Information Access HDSPMAST
Client/Server ALLBASE HPIPMAST
Resource Sharing PDSMAST
Information Access/SQL SQLMAST
The nmmaint,6 should give you an idea into which module has the incorrect
version.
Richard Bayly
Hewlett-Packard Response Centre Australia
--------
--------------------------------------------------------------------------------
Stan Sieler [log in to unmask]
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
|