Configuring Listen Address for a machine / node manager

Question

Hi,
If I give the localhost as value for the Listen Address for the machine (and this the Node Manager), I can start/stop any managed server belonging to the domain
and related machine.
When I change this address to the value of the IP address I get from "ping hostname" (that is to be found in /etc/hosts), or the corresponding host name found in /etc/hosts,
I get the following Warning from the Console:
- For server <managed server>, the Node Manager associated with machine MyMachine02 is not reachable.
- All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
Can someone explain me how can a machine and the node manager be configured with another value than localhost for the Listen Address?
Is there maybe a configuration that must be done at physical server level?
Having this functionality will be a necessity for a cluster.
Thanks by advance for sharing your experience.

Answer 1

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers