Birmingham mumbai

[
 372 
]
Next, we'll need to install 
keepalived
. Simply run the following command on both of 
your servers:
sudo apt install keepalived 
If you check the status of the 
keepalived
 daemon, you'll see that it attempted to start 
as soon as it was installed, and then immediately failed. If you check the status of 
keepalived
 with the 
systemctl
 command, you'll see an error similar to the following:
Condition: start condition failed 
Since we haven't actually configured 
keepalived
, it's fine for it to have failed. After 
all, we haven't given it anything to check, nor have we assigned our floating IP. 
By default, there is no sample configuration file created once you've installed the 
package; we'll have to create that on our own. Configuration for 
keepalived
 is stored 
in 
/etc/keepalived
, which at this point should just be an empty directory on your 
system. If, for some reason, this directory doesn't exist, create it:
sudo mkdir /etc/keepalived
Let's open a text editor on our primary server and edit the 
/etc/keepalived/
keepalived.conf
 file, which should be empty. Insert the following code into the file. 
There
 are some changes you'll need to make in order for this configuration to work 
in your environment. As we continue, I'll explain what the code is doing and what 
you'll need to change. Keep your text editor open after you paste the code, and keep 
reading for some tips on how to ensure that this 
config
 file will work for you:
global_defs { 
    notification_email { 
    [e-mail] 
    } 
    notification_email_from [e-mail] 
    smtp_server 192.168.1.150 
    smtp_connect_timeout 30 
    router_id mycompany_web_prod 
} 
vrrp_instance VI_1 { 
    smtp_alert 
    interface enp0s3 
    virtual_router_id 51 
    priority 100 
     advert_int 5 
    virtual_ipaddress { 
    192.168.1.200 
    } 
} 

---

Chapter 14