Beiträge von surya

Thanks for the clarification.

Other than setting up firewalls at operating system level, is there any other approach? The web service has firewall operations. Do they work with the KVM VPS/RS?

How do I access the VCP GUI described in this wiki?

https://www.netcup-wiki.de/wiki/Firewall_des_netcup_VCP

I do not see this in either the customercontrolpanel or servercontrolpanel sites for either VPS or root server.

Hello michaeleifel

I solved (I think!) the problem slightly differently and it seems to do the job. keepalived will always only ever nominate one of the servers as the MASTER. I check if the node is the MASTER and invoke the web service for rerouting the floating IP to the MASTER.

#!/bin/bash
CURL_BODY='...'

ENDSTATE=$3

case $ENDSTATE in
    "MASTER") CURL_OUTPUT=$(curl -s -H "Content-Type: text/xml; charset=utf-8" -H "SOAPAction:" -d "$CURL_BODY" -X POST "https://www.servercontrolpanel.de:443/SCP/WSEndUser")
        echo "$CURL_OUTPUT"
        exit 0
        ;;
esac

Hello michaeleifel

Thanks a lot for the explanation and the script. That is brilliant.

I did some testing with a simple notify script to invoke the routing web service and am able to simulate the loop condition. Will try to implement your script.

Hello michaeleifel , Thanks very much for your reply.

I am trying to do something very similar to your setup. I am trying to do a failover for the kubernetes control plane. I was initially trying with the cloud vlan interface and when it didn't work I tried with the dummy interface as per the link you mentioned.

I fixed the issue after looking at your configuration. I switched the failover IP to use eth0 and added unicast_src_ip and unicast_peer for the secondary interfaces and it worked!

I was testing the failover IP routing using web service and it works as expected when I shutdown the master node. However, when the master node comes back, the virtual IP switches to the master node but the failover IP doesn't get rerouted because I used the notify_fault script.

notify_fault "/etc/keepalived/failover.sh"

I am looking into your script from here: https://forum.netcup.de/administration…nen/#post154940

I am setting up a three node cluster with failover IP, cloud vlan and keepalived on ubuntu 20.04. I tried various options for configuring keepalived. The virtual IP address gets assigned but is not reachable from another node within the cluster.

/etc/netplan/keepalived.yaml

network:
   version: 2
   bridges:
       ens01:
           dhcp4: no
           dhcp6: no
           accept-ra: no

/etc/keepalived/keepalived.conf

vrrp_script chk_haproxy {
        script "killall -0 haproxy"
        interval 2
        rise 2
}

vrrp_instance VI_1 {
        interface ens192
        state BACKUP
        priority 100
        advert_int 1

        virtual_router_id 50
        unicast_src_ip 192.168.60.48
        unicast_peer {
                192.168.60.49
        }

        virtual_ipaddress {
                192.168.60.50/24 dev ens01
        }

        track_script {
                chk_haproxy
        }
}

I tried creating the network interface using systemd-networkd:

[NetDev]
Name=ens01
Kind=dummy

I tried with use_vmac, strict_mode off and few other settings but I am unable to ping the virtual IP address from another machine. There are no firewalls and the nodes are able to talk to each other using the cloud vlan network configuration. Do I need to do any additional routing settings?