When searching the remote node in OEM for ORACLE9i, i got the error VNI-4044, node may be down , network may be down or slow.
But I checked that the agent service is started normal in the remote node, and the network is normal too. However, I found the node name is change automatically from 's2000d'( i typed in) to 'is-s2000d' as shown in the error message.
Try typing in the ip address as opposed to the host name when discovering the node.
Make sure your network setup is ok, do a nslookup from both the oms and the target node. If you use DNS get your network administrator to check the setup.
Make sure the agent is functioning correctly on the target node, check its status, and make sure it and nothing else are using ports 1748 and 1754 (use tnsping).
Originally posted by yanliu73 However, I found the node name is change automatically from 's2000d'( i typed in) to 'is-s2000d' as shown in the error message.
What about tnsping is-s2000d? Define this alias.
Tomaž "A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete fools" - Douglas Adams
-----------------
The problem happened just these days, it was normal before.
-------------------
Something has changed. If you are happy the agent set up has not changed, then the network set up has.
This is from metalink:
Here is what happens during the discovery process.
1. A hostname or ip address is entered from the EM Console.
2. This request is forwarded to the OMS.
3. The OMS takes that information and resolves it to an ip address (if needed).
4. Then in order to get the fully qualified hostname (which is needed
if dealing with multiple DNS domains), the OMS does a reverse NS
lookup and converts the ip address to the canonical hostname.
To simulate OMS discovery process, issue the following at a command prompt:
nslookup
The following information should be returned:
Server:
Address:
Name:
Address:
Aliases:
Next, take the ip address that was returned for the server and enter:
nslookup
The following information should be returned:
Server:
Address:
Name:
Address:
If the fully qualified name of the server is not returned, DNS needs to be
corrected so the reverse NS lookup name is correct or manually edit the
HOSTS files on each of OMS / Agent systems.
If the HOSTS file option is used, the entry should follow this format:
ie. 111.111.111.111 myhost myhost.us.oracle.com
This is with the fully qualified hostname, on port 1748, that the
Agent Gateway of the OMS contacts the Intelligent Agent to get
services information.
Hi bazza,
I tried as you told, below is the result, any further advice?
and how can I know If the HOSTS file option is used or not.
Z:\>nslookup s2000d
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1
Z:\>nslookup 192.168.0.24
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1
TCP w2000z1:3814 IS~S2000D:1748 ESTABLISHED --note the name changed
TCP w2000z1:3815 S2000B:1748 ESTABLISHED
TCP w2000z1:3816 w2000z1.Software.Arches.com:1748 ESTABLISHED
TCP w2000z1:4600 w2000z1.Software.Arches.com:4601 ESTABLISHED
TCP w2000z1:4708 S2000B:microsoft-ds ESTABLISHED
TCP w2000z1:7772 w2000z1.Software.Arches.com:1711 ESTABLISHED
.
.
.
Z:\>tnsping s2000d
TNS Ping Utility for 32-bit Windows: Version 9.2.0.1.0 - Production on 16-8ÔÂ -2
003 15:13:08
Copyright (c) 1997 Oracle Corporation. All rights reserved.
Check with your network administrator to see the IP alias mapping had been set properly. If you have had any firewall, open to accept requests to appropriate ports. Looks like a local domain issue.
Reply With Quote
Bookmarks