How does cluster virtual behave differently with and without FFO?

Situation #1. "cluster virtual ffo off"

 

AN1(master) sends VRRP packets on a routine schedule, and

AN2(backup) doesn't send VRRP packets.

 

Unplugged AN1.

 

AN1(backup) doesn't send VRRP packets, and

AN2(master) sends VRRP packets on a routine schedule.

 

Plugged AN1 again.

 

AN1(master) sends VRRP packets on a routine schedule, and

AN2(backup) doesn't send VRRP packets.

 

Situation #2. "cluster virtual ffo on"

When FFO is enabled, APV knows that the other node is unplugged, so it will not send out advertisement. When plugging AN1 back into the network, the link is detected, AN2 will start sending out the advertisement. At this that time it will negotiate and set the role status.

AN1(master) sends VRRP packets on a routine schedule, and

AN2(backup) doesn't send VRRP packets.

 

Unplugged AN1.

 

AN1(backup) doesn't send VRRP packets, and

AN2(master) sends VRRP packets only once.

 

Plugged AN1 again.

 

AN1(master) sends VRRP packets on a routine schedule, and

AN2(backup) doesn't send VRRP packets.

___________________________________________________________

Advertisement packets:

AN1(master) sends VRRP packets on a routine schedule, and

AN2(backup) doesn't send VRRP packets.

07:59:51.889147 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
07:59:56.939083 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
07:59:56.939091 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:00:01.979693 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:00:01.979701 10.7.15.40 > 224.0.0.18:  ip-proto-112 20

08:00:07.019637 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:00:07.019645 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:00:11.068921 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:00:11.068926 10.7.15.40 > 224.0.0.18:  ip-proto-112 20

 

Unplugged AN1.

 

AN1(backup) doesn't send VRRP packets, and

AN2(master) sends VRRP packets only once.
08:00:15.213893 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:00:15.213904 10.7.15.45 > 224.0.0.18:  ip-proto-112 20

 

Plugged AN1 again.

AN2 (master) starts sending out VRRP packets until AN1 link is completely up.

08:02:38.688628 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:38.688643 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:43.738687 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:43.738702 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:48.798793 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:48.798806 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:53.868853 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:53.868867 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:58.918926 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:02:58.918942 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:03.989000 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:03.989014 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:09.029082 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:09.029095 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:14.069218 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:14.069230 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:19.119235 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:19.119250 10.7.15.45 > 224.0.0.18:  ip-proto-112 20

 

AN1 link is fully established and start negotiating role status.
08:03:23.172750 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:03:23.172759 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:03:23.174573 10.7.15.45 > 224.0.0.18:  ip-proto-112 20
08:03:23.174585 10.7.15.45 > 224.0.0.18:  ip-proto-112 20

 

AN1(master) sends VRRP packets on a routine schedule, and

AN2(backup) doesn't send VRRP packets.
08:03:28.231359 10.7.15.40 > 224.0.0.18:  ip-proto-112 20
08:03:28.231366 10.7.15.40 > 224.0.0.18:  ip-proto-112 20