Make_net_recovery version mismatch

[Laszlo Csizmadia]

The Ignite-UX server and cliens must have the same version of Ignite? I have the following problem:
gelegen1# make_net_recovery -s geleopv1
...
ERROR: The versions of the tools required for system recovery on "gelegen1"
are different from the versions on the server system "geleopv1". To
ensure that versions are compatible, install the required toolset from
the server geleopv1, using the command: /usr/sbin/swinstall -x
mount_all_filesystems=false -s
geleopv1:/var/opt/ignite/depots/recovery_cmds "*"

======= 03/11/03 11:47:13 MET make_net_recovery completed unsuccessfully
gelegen1# swlist | grep Ignite
B5725AA B.3.6.82 HP-UX Installation Utilities
(Ignite-UX)
Ignite-UX-11-00 B.3.6.82 HP-UX Installation Utilities for

Installing 11.00 Systems
geleopv1:/var/opt/ignite# swlist | grep Ignite
B5725AA_APZ A.3.7.95 HP-UX Installation Utilities
(Ignite-UX - S800 - 10.20)
Ignite-UX-10-20 A.3.7.95 HP-UX Installation Utilities for

Which filestes need to be installed to have the requested files in geleopv1:/var/opt/ignite/depots/recovery_cmds?
This directory contains nothing now.
Thanks in advance...

[John Poff]

Hi,

The client and server need to have the same version of Ignite. We've run into the problem here before with new systems we've loaded. The new system will have a different version than our Ignite server and the server will complain. Just swremove the Ignite from the client and let the server install what it needs and you should be in business.

JP

[Alex Glennie]

But if that still fails note the following you can check versions on both systems using :

an swlist -l fileset Ignite-UX

Ignite just calls the tool /opt/ignite/lbin/check_version to do the version
check. If this fails
for ANY reason the above error will appear so it may not necessarily be the obvious answer

To down track the problem execute as
user root
on the client:

/opt/ignite/lbin/check_version -vr -s

The real problem should now become obvious. Ussually it's a tftp issue.

Some hints on tftp problems:
- Check entry in /etc/inetd.conf on server. It should look like:
tftp dgram udp wait root /usr/lbin/tftpd tftpd
/opt/ignite /var/opt/ignite
If you need to change it, don't forget to call "inetd -c".
- Check for bad/unnessary entries for tftp in /var/adm/inetd.sec.

Some tftp debuging tricks:
- Enable inetd's connection logging (inetd -l) and watch /var/adm/syslog.log
during tests.
- Login on server and do:
# cd /tmp
# tftp localhost
tftp> get /opt/ignite/Version
Received 10 bytes in 0.1 seconds
tftp> quit
- Login on client and do the same as abive - but use the server's name instead
of localhost.

[melvyn burnard]

As John says, they have to be the same versions. We had htis issue when we set up one major Ignite srever for all our systems, and it now works well, as we just update hte srever with hte latest Ignite, and it pushes this out to hte client when a backup is requested.
Works like a treat.

[John Bolene]

Yes, they both have to agree.

I have 3 servers for this purpose, a 10.20, an 11.0, and an 11i.

These support all my current HP configurations.

I am almost completed with the 10.20 upgrade to 11 and will have this server to use for the next version of 11i.

[Laszlo Csizmadia]

Thanks.
> Just swremove the Ignite from the client and let the server install what it needs and you should be in business.

And how 'let the server install' the requested filesets to the client? You mean somehow swinstall or other tool?

[John Poff]

When you do a make_net_recovery of your client from the server, the server will check for the presence of the Ignite software on the client to see if it exists and if it is the correct version. If it doesn't find the Ignite software on the client, the server will install it for you.

JP