I thought I would share with you all an experience you may want to be aware of with WebSphere, hipersockets and the Federation process:
We are building our production linux environment. One of the requirements of that was to have a two node cluster available should demand require it be brought online. In the process of building that WebSphere cluster we experienced a strange problem: ADMU0012I: Creating Node Agent configuration for node: phalen ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU0036E: The Deployment Manager cannot lookup by name host phalen.co.hennepin.mn.us at address 192.168.252.15 The add node operation failed. Check the server logs for details. The address that got returned was the hipersocket interface addess, not eth0! We couldn't figure it out, so we just removed the hipersocket interface. The federation went fine..... However I found the following..... I added the hipersocket interface to /etc/chandev.conf on this particular system by hand because yast doesn't appear to do that. In doing so, I put it ahead of the ethernet interface. This changes the order in which it appears in /proc/qeth. The hipersocket address in that situation gets top billing. It appears that WebSphere in the Federation process, interrogates the node being brought in and gets some information from that system. Specifically, it appears to return the first interface defined in either /etc/chandev.conf, or more likely, /proc/qeth, as the ethernet interface to use to talk to that node. The IP address is returned to the node on the system that is doing the federation, and of course the lookup by hostname isn't going to resolve to the IP address of the hipersocket. It's non-routeable and not defined to our DNS. I bring this up, because there are possible mult-OSA configurations out there, and that the first ethernet device defined may NOT be the one you want websphere to be using to talk to the world. I now return you to you regularly scheduled mailing list discussion. -James. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
