Operating System - HP-UX
1753816 Members
8421 Online
108805 Solutions
New Discussion юеВ

make_net_recovery and error

 
SOLVED
Go to solution
Stefan Preusse
New Member

make_net_recovery and error

I want to use make_net_recovery.
I have setup the ignite server, the nfs exports have been made.

The software "Ignite-UX tape and network recovery tool subset" (version B.2.3.205) was installed via ignite-userinterface.

So far, so good. But when I try to create an archive with make_net_recovery, I get the following error-message:

ERROR: The versions of the tools required for network system recovery on
"ap025f" are different from the versions on the server system
"frsux201". To ensure that versions are compatible, install the
required toolset from the server frsux201, using the command:
/usr/sbin/swinstall -x mount_all_filesystems=false -s
frsux201:/var/opt/ignite/depots/recovery_cmds "*"

I have reinstalled the software on the client, but I get still the same error.

Any idea, what is causing this error?

4 REPLIES 4
CHRIS ANORUO
Honored Contributor

Re: make_net_recovery and error

Did you update /etc/bootptab? Okay reboot the system and try it out again
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
Cheryl Griffin
Honored Contributor
Solution

Re: make_net_recovery and error

Stefan,

Ignite has some rather generic error messages, this is one of them.

Try the following to uncover the real error:
# /opt/ignite/lbin/check_version -vr -s {Ignite_Server_Name_Here}

Next, check that tftp is enabled in /etc/inetd.conf and for any tftp entries in /var/adm/inetd.sec. If you make any changes here, be sure to inetd -c to restart the inet daemon.

Best Wishes,
Cheryl
"Downtime is a Crime."
Cheryl Griffin
Honored Contributor

Re: make_net_recovery and error

Stefan,
For clarity:

The check_version command would be run on the client.

The inetd.conf and .sec are examined on the server.
"Downtime is a Crime."
Stefan Preusse
New Member

Re: make_net_recovery and error

Hallo Cheryl,

thanks for your tip.
this has solved my problem, there was a problem with the tftp-configuration and inetd.sec

Regards
Stefan