Hello,

I can not ping dispatcher machine from itself for cluster address. I can
ping cluster address from any other machines from my local net, but not from
itself.
Load balancing working properly for all others machines also.
Why?
Is my network setting for dispatcher wrong?

Thanks,
N Baranov

[ Post a follow-up to this message ]

Nikolay,

It depends on the operating system that ND is running on.  AIX should
work, Solaris with 'ifconfig' aliased addresses should, Linux won't and
Windows won't.  ND hooks into each of the kernels and IP stacks
differently (depending on the OS and what's allowed) so certain things
act differently.

Jeff

[ Post a follow-up to this message ]

Thanks for reply, Jeff

Probably, I don't understand  something, but how HTTP advisor can work on
cluster address on my Win2k ND box (using MAC-forwarding method) if this
address can not be pinged?

I see (via Network monitor) IP packets sending from my local IP address to
cluster address during working HTTP advisor, but nothing to go in reverse
direction. Advisor's conclusion is server box failed.

Thanks for any comments,
N Baranov

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

> Nikolay,
>
> It depends on the operating system that ND is running on.  AIX should
> work, Solaris with 'ifconfig' aliased addresses should, Linux won't and
> Windows won't.  ND hooks into each of the kernels and IP stacks
> differently (depending on the OS and what's allowed) so certain things
> act differently.
>
> Jeff
>

[ Post a follow-up to this message ]

I should have clarified that the answers I gave on pings only apply to
pings coming from the ND box itself.  So the Windows box running ND
can't ping the cluster, but other boxes on the subnet can.

Advisors do not need to ping the cluster address however.  The Java
advisor thread works with the executor to make sure the connection
request goes to the correct server -- the only ping is against the
server address itself. If the advisor can't ping the server, then it
won't send the protocol request (since we know the server isn't
responding to network traffic).  But nothing in the advisor code ever
pings the cluster IP.

Jeff

[ Post a follow-up to this message ]

Thanks for explanation, Jeff

I found the reason of HTTP advisor failing. The problem was in Cloud WAN
simulator installed. Its driver prevent to proper work of advisor (don't
know, how). But one interesting thing appear - I can ping my ND box from
itself on cluster address now 

N Baranov


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

> I should have clarified that the answers I gave on pings only apply to
> pings coming from the ND box itself.  So the Windows box running ND
> can't ping the cluster, but other boxes on the subnet can.
>
> Advisors do not need to ping the cluster address however.  The Java
> advisor thread works with the executor to make sure the connection
> request goes to the correct server -- the only ping is against the
> server address itself. If the advisor can't ping the server, then it
> won't send the protocol request (since we know the server isn't
> responding to network traffic).  But nothing in the advisor code ever
> pings the cluster IP.
>
> Jeff
>

[ Post a follow-up to this message ]