Re: Only one misc_check possible (several configured per VIP)
Bernd <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
Am 2016-07-15 13:13, schrieb Bernd:
> Hi,
Hi again,
I verified that this behaviour is still continuing running 1.2.23.
Best,
Bernd
> I've got a weird experience here (snippet from config):
>
> virtual_server 12.34.56.78 80 {
> delay_loop 20
> lb_algo wlc
> lb_kind NAT
> nat_mask 255.255.255.0
> persistence_timeout 0
> protocol TCP
> alpha
>
> real_server 10.0.0.100 80 {
> weight 1
> MISC_CHECK {
> misc_path "/root/bin/check_hosts.sh 10.0.0.100"
> misc_timeout 5
> }
> }
> }
>
> real_server 10.0.0.101 80 {
> weight 1
> MISC_CHECK {
> misc_path "/root/bin/check_hosts.sh 10.0.0.101"
> misc_timeout 5
> }
> }
> }
>
> real_server 10.0.0.102 80 {
> weight 1
> MISC_CHECK {
> misc_path "/root/bin/check_hosts.sh 10.0.0.102"
> misc_timeout 5
> }
> }
> }
> }
>
> However, only the first appearance is being used (10.0.0.100); if I
> comment out .100, it works for .101, but not for .102. If I comment out
> .101, it works for .102...
>
> I verified this using tcpdump - no packet going to the second or third
> rs configured.
>
> Any idea what could cause this? Tried 1.2.13 from CentOS base repo as
> well as a self-built 1.2.19
>
> Best regards,
>
> Bernd
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev