Operating System - HP-UX
1832542 Members
6162 Online
110043 Solutions
New Discussion

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

 
SOLVED
Go to solution
John Goetz
Advisor

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

ERROR: No response from Ignite-UX Server: "ignite".
5 REPLIES 5
Sanjay_6
Honored Contributor
Solution

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

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
John Goetz
Advisor

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

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

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

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
Steven E. Protter
Exalted Contributor

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

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
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Michael Roberts_3
Honored Contributor

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

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

etouq ot hguone revelc ton m'i