之前配置好的keepalive，在後來測試過程中發現關閉keepalive重新啓動時日誌會報以下錯誤：
Jul 1 14:47:13 frontend1 Keepalived_vrrp[112938]: bogus VRRP packet received on ens160 !!!
Jul 1 14:47:13 frontend1 Keepalived_vrrp[112938]: VRRP_Instance(VI_1) Dropping received VRRP packet...
Jul 1 14:47:14 frontend1 Keepalived_vrrp[112938]: (VI_1): ip address associated with VRID 51 not present in MASTER advert : 10.12.50.198
Jul 1 14:47:14 frontend1 Keepalived_vrrp[112938]: bogus VRRP packet received on ens160 !!!
Jul 1 14:47:14 frontend1 Keepalived_vrrp[112938]: VRRP_Instance(VI_1) Dropping received VRRP packet...
Jul 1 14:47:15 frontend1 Keepalived_vrrp[112938]: (VI_1): ip address associated with VRID 51 not present in MASTER advert : 10.12.50.198
Jul 1 14:47:15 frontend1 Keepalived_vrrp[112938]: bogus VRRP packet received on ens160 !!!
Jul 1 14:47:15 frontend1 Keepalived_vrrp[112938]: VRRP_Instance(VI_1) Dropping received VRRP packet...
Jul 1 14:47:16 frontend1 Keepalived_vrrp[112938]: (VI_1): ip address associated with VRID 51 not present in MASTER advert : 10.12.50.198
查閱資料折騰了一番後，可能是keepalive master的virtual_router_id和局域網內的其它的keepalive master的virtual_router_id有衝突，修改 /etc/keepalived/keepalived.conf 配置文件裏的 virtual_router_id 51 爲其它數值後，啓動keepalive後日志不再報錯。
需要注意的是，從節點的keepalive的virtual_router_id是需要和主節點的virtual_router_id 保持一致的，不然的話，兩個keepalive節點貌似都是以master的身份工作，不過測試了下，這樣兩個主的keeplive貌似也是能起到 虛擬ip 高可用的作用，只不過兩個keeplive單獨起作用而已，虛擬ip會路由帶後啓動的keeplive 的節點上。
以上是自己的測試結果，如有不對歡迎留言。