Hi,
During NAT, on the collocated server, we added the return address in the
route table, (As described in lbguide.pdf for Linux OS, we have redhat adv.
server v2.1)
And found that ND is not responding to the arp queries(in this case from the
gateway for the return address added in the route table.)

Is this a known bug in dispatcher on Linux env with nat-with-collocation?
We are using dispatcher component from WebSphere V5.

Regards,
rdr

[ Post a follow-up to this message ]

Are the arp queries not working or just pings?  ND should respond to arp
queries for return addressess (assuming those return addresses are on
the active HA -- or on a non-HA setup).  But pings will not get a
response.  You can ping the return address, kill it after a second, then
check your local arp table to see if you got an entry.

Jeff

[ Post a follow-up to this message ]

Hi,
Its not in the case of ping for return address. ND is not responding to arp
queries for return addresses on a non-HA setup. (In case of HA, it is
working fine on the primary dispatcher, but the above problem is seen when
the backup dispatcher is active.)


Regards,
Roopa.

"JLee" <leeja@NOSPAMus.ibm.com> wrote in message
news:3EBBF0A8.1080409@NOSPAMus.ibm.com...
quote:

> Are the arp queries not working or just pings?  ND should respond to arp
> queries for return addressess (assuming those return addresses are on
> the active HA -- or on a non-HA setup).  But pings will not get a
> response.  You can ping the return address, kill it after a second, then
> check your local arp table to see if you got an entry.
>
> Jeff
>

[ Post a follow-up to this message ]

Roopa,

I would contact IBM Support for this. I believe they found the problem
with the arp queries in a non-HA setup, but I've not heard of problems
when the standby takes over for a cluster/return address.

Jeff

[ Post a follow-up to this message ]