Joseph Mack wrote:
"Carlos J. Ramos" wrote:
No, unfortunately request to LVS services from the machine outside the
gateway does not work under any condition.
OK summary now: LVS is accessible from the gateway. The LVS is not accessible
from the remote machine. When you bring down the LVS by clearing the ipvsadm
table, and bring up a service on port 80 on the director, you can access
the service on director:80 from the remote node. You don't have any filter rules
on the gateway.
I don't have any ideas I'm sorry. I think you'll have to brute force this
one with tcpdump and see where the packets get hung up. Watch for icmp replies
saying something is not accessible or tcp packets that don't get replies.
Joe
Hi. Now, it seems to be solved by using static routes to hosts instead
of using static routes to networks.
There is also another important note.
Directors uses MQSeries from IBM, the starting squence in haresources
was mqseries masq.lvs (script for NAT), it looks that the 1 minute
needed by mqseries to get up was confusing(!?) masq.lvs or ldirectord.
We have just change the order to get up mqseries and masq.lvs, rising up
first masq.lvs and finally mqseries.
With this two changes now seems it perfectly works.
Thanks a lot.
Carlos
--
--------------------------------------------------------
Carlos J. Ramos Genasys II Spain, S.A.U.
Administrador de Sistemas Ventura de la Vega 5
Tel:+34-91-3649100 ext 170 28014 Madrid
Fax:+34-91-3649119
Spain
Email: cjramos@xxxxxxxxxx
--------------------------------------------------------
|