> The target node, 'Phalen' already KNOWS what it's DNS name > and IP address > are.
For *one* interface, agreed. It looks to me like WAS is looking at all the interfaces, and not getting info for some of them. I'm assuming that both machines are connected to the same hipersocket LAN -- am I way off? > There is NO way that WebSphere on 'Calhoun' can learn about > what the IP > address of the hipersocket on Phalen is. Phalen, in the > process of being > federated HAS to tell the process on Calhoun about itself, > including the IP > address of the ethernet interface it is using. It reports the wrong > information, and of course, the sanity check in the process running on > Calhoun fails. I guess I'm thinking that it may actually *be* using the HSI interface if it got the interface info during the query, and thus is barfing on not having the host info. If the HSI interfaces are in the same subnet and the other interfaces are not, the IP code may legitmately be preferring the shorter (same subnet vs different subnet) route. > Why are you not asking whether or not this interface is > correct. Correct is a relative term here. By metric (if the HSI interfaces are on the same subnet), it's picking the "best" route, regardless of naming. > This of course, only becomes an issue if you 1) define the > hipersocket interface before installing WebSphere and 2) > whether or not you > made the changes to chandev.conf so that the entry that > corresponds to hsi1 > is after the entry for eth0. Could be. I'm setting up a test now to see what happens. The messages still tell me that somehow it's using another interface than you think it is, and it can't get the info for the interface it is actually using. What happens if you put a name for the HSI interface into /etc/hosts? ---------------------------------------------------------------------- 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
