Guys,
I actually found a solution to this. After much googling I was able to
come up with this:
vrrp_instance VI_1 {
interface eth1
state MASTER
virtual_router_id 51
priority 101 # 101 on master, 100 on backup
*dont_track_primary*
vrrp_unicast_bind 10.40.116.30 # Internal IP
Em 29-09-2015 15:03, Gordon Messmer escreveu:
On 09/29/2015 09:14 AM, Tim Dunphy wrote:
And if I do an ifconfig command I see no evidence of an eth1 existing.
"ifconfig -a" will show you all of your interfaces.
Maybe there is a confusion here. Sounds like Tim thought keepalived
would create
On 09/29/2015 09:14 AM, Tim Dunphy wrote:
And if I do an ifconfig command I see no evidence of an eth1 existing.
"ifconfig -a" will show you all of your interfaces.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/ce
Tim Dunphy wrote:
> Hey guys,
>
> I'm trying to install keepalived 1.2.19 on a centos 6.5 machine. I did an
> install from source.
>
> And when I start keepalived this is what I'm seeing in the logs. It's
> reporting that the VRRP_Instance(VI_1) Now in FAULT state.
Two stupid questions:
1. Why
Hey guys,
I'm trying to install keepalived 1.2.19 on a centos 6.5 machine. I did an
install from source.
And when I start keepalived this is what I'm seeing in the logs. It's
reporting that the VRRP_Instance(VI_1) Now in FAULT state.
Here's more of that log entry:
Sep 29 12:06:58 USECLSNDMNRDB
5 matches
Mail list logo