On May 3, 2007, at 7:35 AM, Joni Moyer wrote:
Hello everyone,
Is this normal behavior when a server has 2 IP addresses to switch
attributes? Or does this cause a delay? And if this is an issue, is
there a way to resolve this so that it doesn't occur?
Joni -
It's a harmless message, but certainly clutter.
How to deal with it depends upon the nature of the duality and how the
sessions are being initiated. Some approaches:
You can often keep this informational message from appearing by the
TCPServeraddress in your client options file causing client-initiated
sessions to initiate through a consistent IP-address adapter; and for
server-initiated schedules, fill in the node HLAddress spec. If for
some reason the client network name can DNS-resolve to multiple IP
addresses (as in the case of virtual IPs), code an IP address for the
client's network location, to uniquely identify it, rather than using a
network name.
Maybe someone out there has further experience with it, and can lend
more?
Richard Sims http://people.bu.edu/rbs/