GARP packets from VM are trapped and not flooded

[Hari Prasad Killi]

When AAP is configured, the GARP packets from VM are trapped to agent (enables agent to determine active VM in active-backup config). In this case, the GARP packets from the VM are not flooded. vrouter should also flood the GARP packets.

[Daisuke Nakajima (dnakajima)]

Let me correct above;
GARP is not flooded when we don’t’ have AAP. However GARP is flooded when we have AAP.
So, vRouter should flood GARP both cases (with/without AAP).

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/14883
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/14883
Committed: http://github.org/Juniper/contrail-vrouter/commit/c2e31f8357075e32ae2b0acfb51daecb4054ba04
Submitter: Zuul
Branch: R2.20

commit c2e31f8357075e32ae2b0acfb51daecb4054ba04
Author: Divakar <email address hidden>
Date: Thu Nov 5 11:20:56 2015 +0530

Mirroring the GARP packes rather trapping

When the Agent puts the Trap flag in L3 route it expects the Garp
packets to be trapped to it. As of now, the packet is only getting
Trapped and not getting flooded when this flag is seen. As such, Garp
packet always need to be flooded irrespective of the Trap flag.

To fix this, when the Trap flag is seen in the L3 route, a copuy of Garp
packet is given to VM and original copy is flooded as well.

Change-Id: I586385e157cd221bfa21d879b7601ebfa00cd5c8
closes-bug: #1511237

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/16107
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/16107
Committed: http://github.org/Juniper/contrail-vrouter/commit/1aa44695cbc3d74f8b41204c2087555e7e454feb
Submitter: Zuul
Branch: master

commit 1aa44695cbc3d74f8b41204c2087555e7e454feb
Author: Divakar <email address hidden>
Date: Thu Nov 5 11:20:56 2015 +0530

Mirroring the GARP packes rather trapping

When the Agent puts the Trap flag in L3 route it expects the Garp
packets to be trapped to it. As of now, the packet is only getting
Trapped and not getting flooded when this flag is seen. As such, Garp
packet always need to be flooded irrespective of the Trap flag.

To fix this, when the Trap flag is seen in the L3 route, a copuy of Garp
packet is given to VM and original copy is flooded as well.

Change-Id: I586385e157cd221bfa21d879b7601ebfa00cd5c8
closes-bug: #1511237