1. When both Master/primay and Backup become master
One of the reason for both VRRP instances become master is
A. There is no reachability (connection issue) between the two. When there is no reachability both instances send VRRP packets and assume master as themselves.
B. The auth type protocol mismatch in VRRP instances in keepalived.conf
When there is auth_type mismatch between the two then both VRRP instances does not understand VRRP packets themselves and both become master.
2. When VRRP instance become fault
If keepavlied service stop on the instance.
One of the reason for both VRRP instances become master is
A. There is no reachability (connection issue) between the two. When there is no reachability both instances send VRRP packets and assume master as themselves.
B. The auth type protocol mismatch in VRRP instances in keepalived.conf
When there is auth_type mismatch between the two then both VRRP instances does not understand VRRP packets themselves and both become master.
2. When VRRP instance become fault
If keepavlied service stop on the instance.
No comments:
Post a Comment