Kbase P50808: Is the NameServer bound to the IP/hostname address of the server within a dual NIC environment?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/11/2004 |
|
Status: Verified
GOAL:
Is the NameServer bound to the IP/hostname address of the server within a dual NIC environment?
GOAL:
How does the NameServer listen on network interfaces in a dual NIC environment?
GOAL:
Why are two different hostnames reported in the NS log file compared to the NameServer query output in a dual NIC environment?
FACT(s) (Environment):
Progress 9.x
WebSpeed 3.x
OpenEdge 10.x
FIX:
NameServer does not bind to the IP/hostname of the server whether the server has single or multiple NICs. The NameServer listens on all network interfaces so client can connect to it from either interface. When the NameServer starts it reports the string URL which is passed in the command line as the parameter -r when the AdminServer spawns of the java process for the NameServer and that is what you see in the NameServer log file:
Starting NameServer NS1 rmi://hostname2:20931/NS1 Port = 5162 Timeout = 30. (8196)
^^^^^^^^^^^^^^^^^^^^^^^^
This does not mean that the NameServer is listening on that interface.
The host name value that is reported by the "nsman -i NS1 -query" as demonstrated is taken from the java call (InetAddress.getLocalHost()).getHostName(). Because of Java's implementation, it only returns the first interface even if the NameServer listens on all the interfaces.
NameServer NS1 running on Host hostname Port 5162 Timeout 30 seconds.
In a dual NIC environment, if you specifically ask AdminServer to start on secondary interface, the NameServer log will report that fact, however, the NameServer query will still report the first interface, but this does not affect the fact that NameServer listens on all interfaces.