topic Re: Getting error message when Adding New Client for Recovery in Ignite. in Operating System - HP-UX

Getting error message when Adding New Client for Recovery in Ignite.

John Goetz — Mon, 22 Nov 2004 11:08:37 GMT

ERROR: No response from Ignite-UX Server: "ignite".

Re: Getting error message when Adding New Client for Recovery in Ignite.

Sanjay_6 — Mon, 22 Nov 2004 11:14:53 GMT

Hi John,

Check and make sure, you are able to resolve the hostname and ip address of the client from the ignite server using nslookup. do the same on the client to make sure, you are able to resolve the ignite server hostname and ip address.

Hope this helps.

Regds

Re: Getting error message when Adding New Client for Recovery in Ignite.

John Goetz — Mon, 22 Nov 2004 11:18:57 GMT

nslookup on both the Ignite and client servers are able to resolve the hostname and IP address

Re: Getting error message when Adding New Client for Recovery in Ignite.

Sanjay_6 — Mon, 22 Nov 2004 11:25:33 GMT

Hi john,

Do you have nfs configured and running on ignite server and tftp enabled,

http://www.software.hp.com/products/IUX/docs/sysadm.html#Chapter-1

Hope this helps.

regds

Re: Getting error message when Adding New Client for Recovery in Ignite.

Steven E. Protter — Mon, 22 Nov 2004 11:30:46 GMT

You can try adding the client from the Ignite server.

I'd check and see if the inetd daemon is running on the server and that there isn't a /var/adm/inetd.sec entry that blocks access to the Ignite client you desire to add.

SEP

Re: Getting error message when Adding New Client for Recovery in Ignite.

Michael Roberts_3 — Mon, 22 Nov 2004 11:33:18 GMT

When adding a new client Ignite copies some commands over to the client. These commands are then run to setup the per client directory on the server, and to check that there is NFS and tftp connectivity between the client and server.

On the client make sure that you can:

tftp igniteServer << eot
get /opt/ignite/Version
quit
eot

and
mount igniteServer:/var/opt/ignite/clients /var/tmp/mnt

If either of these fail then you need to correct it before you can successfully ignite.

For tftp setup /etc/inetd.conf:
tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite

run inetd -c

for NFS setup /etc/exports:
/var/opt/ignite/clients -anon=2

exportfs -av