Birmingham mumbai

[
 373 
]
There's quite a bit going on in this file, so I'll explain the configuration section by 
section, so you can better understand what's happening:
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 
} 
In the 
global_defs
 section, we're specifically configuring an email host to use in 
order to send out alert messages. When there's an issue and 
keepalived
 switches 
to a new primary server, it can send you an email to let you know that there was 
a problem. You'll want to change each of these values to match that of your mail 
server. If you don't have a mail server, 
keepalived
 will still function properly. You 
can remove this section if you don't have a mail server, or comment it out. However, 
it's highly recommended that you set a mail server for 
keepalived
 to use.
Let's look at the next section of code:
vrrp_instance VI_1 { 
    smtp_alert 
    interface enp0s3 
    virtual_router_id 51 
    priority 100 
 
    advert_int 5 
Here, we're assigning some configuration options regarding how our virtual IP 
assignment will function. The first thing you'll want to change here is the interface. 
In my sample 
config
, I have 
enp0s3
 as the interface name. This will need to match 
the interface on your server where you would like 
keepalived
 to be bound to. If in 
doubt, execute 
ip a
 at your shell prompt to get a list of interfaces.
virtual_router_id
 is a very special number that can be anything from 
0
 to 
255
. 
This number is used to differentiate multiple instances of 
keepalived
 running on 
the same subnet. Each member of each 
keepalived
 cluster should have the same 
virtual_router_id
, but if you're running multiple pairs or groups of servers on the 
same subnet, each group should have its own 
virtual_router_id
. I used 
51
 in my 
example, but you can use whatever number you'd like. 

---

Serving Web Content