Operating System - HP-UX
1753328 Members
4802 Online
108792 Solutions
New Discussion юеВ

Re: Ignite problem, "unknown host".

 
SOLVED
Go to solution
Leif Halvarsson_2
Honored Contributor

Ignite problem, "unknown host".

Hi,
If i try to make a network archive, running make_net_recovery from the client I get the following error.

make_net_recovery -s c997
ERROR: c997 is an unknown host

The client is installed from the Ignite server (c997).

I get the same error if I run from the Ignite GUI on the Ignite server.

Both the client and the Ignite server is of course up and running and communication in both direction (ping) is OK.

I have used the same Ignite server for about 6 months and used it for a large number of ignite backup without any problem.

What could be the reason ?


4 REPLIES 4
Mourad Derriche
Occasional Advisor

Re: Ignite problem, "unknown host".

Can you ping the host 'c997' without specifying the FQDN?
Read between the lines...
Mark Grant
Honored Contributor

Re: Ignite problem, "unknown host".

I would expect a different error message but is there any NFS issue between the two machines at the moment?
Never preceed any demonstration with anything more predictive than "watch this"
Steve Steel
Honored Contributor
Solution

Re: Ignite problem, "unknown host".

Hi

This is dns

make_net_recovery known issues as documented in Ignite Release Note:

* When the client machine is on a different network domain than the Ignite-UX
server, the recovery GUI may have difficulty finding the client. This problem
can be remedied by making sure that both the client and server have DNS search
strings for both of the domains.


Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
Leif Halvarsson_2
Honored Contributor

Re: Ignite problem, "unknown host".

Hi,
It was a DNS problem. The DNS domain had been set for the client but not for the Ignite server. After configuring DNS for the Ignite server everything seems to work. I should have suspected this at once as the same problem is rather common in Data Protector.

Thank you !