Host: 10.28.10.123
Standby: 10.28.10.108
VIP: 10.28.10.251
With keepalived yum installed, configured, start keepalived, but in the case of machine can't ping the VIP, closed on a host of keepalived, separate starting keepalived machine, also can't on the host ping VIP, to show just a little
Iptables has been closed, selinux is set to the permissive
IP a are as follows:
[root @ localhost keepalived] # IP a
1: lo: & lt; The LOOPBACK, UP, LOWER_UP & gt; Mtu 65536 qdisc noqueue state UNKNOWN
The link/loopback 00:00:00:00:00:00 BRD 00:00:00:00:00:00
Inet 127.0.0.1/8 scope host lo
Valid_lft forever preferred_lft forever
Inet6: : 1/128 scope host
Valid_lft forever preferred_lft forever
2: ens3: & lt; BROADCAST and MULTICAST, the UP, LOWER_UP & gt; Mtu 1500 qdisc pfifo_fast state UP qlen 1000
The link/Mr 06:3 a: 94:00:00:54 BRD ff: ff: ff: ff: ff: ff
Inet 10.28.10.123/24 BRD 10.28.10.255 scope global ens3
Valid_lft forever preferred_lft forever
Inet 10.28.10.251/24 scope global secondary ens3
Valid_lft forever preferred_lft forever
Inet6 fe80: : 43 a: 94 ff: fe00:54/64 scope link
Valid_lft forever preferred_lft forever

Keepalived. Conf configuration is as follows:
! The Configuration File for keepalived

Global_defs {
Router_id LVS_DEVEL
}

Vrrp_instance VI_1 {
State MASTER # stand-by for BACKUP
Interface ens3
Virtual_router_id 51
Priority # 100 for machine of 99
Advert_int 1
The authentication {
The auth_type PASS
Auth_pass 1111
}
Virtual_ipaddress {
10.28.10.251
}
}

CodePudding user response:

Refer to some of the online solutions, failed to resolve, strives for the great god show just a little,,,

CodePudding user response:

Stand-by have binding VIP

CodePudding user response:

Will, Lord for launch, will their binding VIP
Doubt is the problem of VRRP, but I don't know how to solve

CodePudding user response:

Close the iptables selinux
Restart the network service
Whether see nginx keepalived start
The standby interface is ens3
Main preparation machine whether ping each other

CodePudding user response:

reference 4 floor fan63182830 response:

closed iptables selinux
Restart the network service
Whether see nginx keepalived start
The standby interface is ens3
Whether the main standby each other ping

Thanks,
Restart the network service failed when

[root @ localhost keepalived] # systemctl restart network. The service
The Job for the network. The service failed. See 'systemctl status network. The service' and 'journalctl - xn' for the details.
[root @ localhost keepalived] # systemctl status. Network service
Network. The service - LSB: "bringing up/down networking
The Loaded: the Loaded (/etc/rc. D/init. D/network)
Active: failed (Result: exit - code) since Thu 04:54:37 2015-10-22 EDT. Line 7 s
Process: 6857 ExecStart=/etc/rc. D/init. D/network start (code=exited, status=1/FAILURE)

Oct 22 04:54:37 localhost. Localdomain network [6857] : RTNETLINK answers: File exists
Oct 22 04:54:37 localhost. Localdomain network [6857] : RTNETLINK answers: File exists
Oct 22 04:54:37 localhost. Localdomain network [6857] : RTNETLINK answers: File exists
Oct 22 04:54:37 localhost. Localdomain network [6857] : RTNETLINK answers: File exists
Oct 22 04:54:37 localhost. Localdomain network [6857] : RTNETLINK answers: File exists
Oct 22 04:54:37 localhost. Localdomain network [6857] : RTNETLINK answers: File exists
Oct 22 04:54:37 localhost. Localdomain network [6857] : RTNETLINK answers: File exists
Oct 22 04:54:37 localhost. Localdomain systemd [1] : network. Service: control the process exited, code=exited the status=1
Oct 22 04:54:37 localhost. Localdomain systemd [1] : Failed to start the LSB: "bringing up/down networking.
Oct 22 04:54:37 localhost. Localdomain systemd [1] : the Unit network. The service rose failed state.

CodePudding user response:

Standby interface is indeed ens3, main machine can ping each other

CodePudding user response:

router_id

CodePudding user response:

What do you mean?

CodePudding user response:

Router_id LVS_DEVEL name change is not the same

CodePudding user response:

Changed or not

CodePudding user response:

The standby IP a look

CodePudding user response:

Ok, this is for the situation of the machine starting keepalived
IP/root @ localhost ~ # a
1: lo: & lt; The LOOPBACK, UP, LOWER_UP & gt; Mtu 65536 qdisc noqueue state UNKNOWN
The link/loopback 00:00:00:00:00:00 BRD 00:00:00:00:00:00
Inet 127.0.0.1/8 scope host lo
Valid_lft forever preferred_lft forever
Inet6: : 1/128 scope host
Valid_lft forever preferred_lft forever
2: ens3: & lt; BROADCAST and MULTICAST, the UP, LOWER_UP & gt; Mtu 1500 qdisc pfifo_fast state UP qlen 1000
The link/Mr 06:9 9: e4:00:00:45 BRD ff: ff: ff: ff: ff: ff
Inet 10.28.10.108/24 BRD 10.28.10.255 scope global ens3
Valid_lft forever preferred_lft forever
Inet 10.28.10.251/24 scope global secondary ens3
Valid_lft forever preferred_lft forever
Inet6 fe80: : 499: e4ff: fe00:45/64 scope link
Valid_lft forever preferred_lft forever

I now test launched the host only keepalived, although there is a VIP, but other machine can't the VIPnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull