View Single Post
  #2  
Old 5th April 2007, 11:28
manurro manurro is offline
Junior Member
 
Join Date: Apr 2007
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

OK, it was an IPTABLES issue, I should have checked that before

For those who may have same issue, adding that to iptables config file fixed my problem:
Loadb1
Code:
-A RH-Firewall-1-INPUT -p ip -m comment -m state -s bbb.bbb.bbb.bbb --state NEW -j ACCEPT --comment Hearbeat
-A RH-Firewall-1-INPUT -p ip -m comment -m state -s xxx.xxx.xxx.xxx --state NEW -j ACCEPT --comment Hearbeat
Loadb2
Code:
-A RH-Firewall-1-INPUT -p ip -m comment -m state -s aaa.aaa.aaa.aaa --state NEW -j ACCEPT --comment Hearbeat
-A RH-Firewall-1-INPUT -p ip -m comment -m state -s xxx.xxx.xxx.xxx --state NEW -j ACCEPT --comment Hearbeat
(aaa.aaa.aaa.aaa is loadb1's IP, bbb.bbb.bbb.bbb loadb2's IP and xxx.xxx.xxx.xxx is the virtual IP)

Regards!
Reply With Quote