Contrail 2.21-14: DHCP Packets are not trapped from vrouter to agent

[Deepak Jeyaraman]

Build:
root@ccra-06:~# contrail-version
Package Version Build-ID | Repo | Package Name
-------------------------------------- ------------------------------ ----------------------------------
contrail-analytics 2.21.1-14 14
contrail-config 2.21.1-14 14
contrail-config-openstack 2.21.1-14 14

issue:

Total 20 instances:
10 - Ubuntu
10 - vSRX2.0

There are some vSRX2.0 (4 out of 10) which dont have DHCP IPs for fxp0 (management)

But when this is initiated manually, we are able to get them.

Screenshot attached (totally 4 png - showing the failure as well as manually done, it works)

[Deepak Jeyaraman (jdeepak)]

FYI, there is no error in schema.err - this issue is not related to schema errors

[OpenContrail Admin (ci-admin-f)]

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

[OpenContrail Admin (ci-admin-f)]

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

[OpenContrail Admin (ci-admin-f)]

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

commit ede19c383bce2b542f26aeadc342a1e33eada154
Author: Divakar <email address hidden>
Date: Wed Dec 16 08:15:16 2015 -0800

Trapping DHCP packets in the ingress processing of Tap interface

Right the DHCP packets are processed in L2 multicast nexthop as DHCP
request packet is a multicast packet. In a scaled setup, this leads to
issues, as Agent receives the config late and VRF correspodning to VMI,
L2 broadcast route and multicast nexthop also does not get added. This
leads to DHCP request packet getting dropped.

As "D" flag is set on VMI by Agent when nova-compute plugs the
interface, the DHCP packet can be trapped to Agent without even the
configuration. Agent in this case can provide the short lease to VM.

So as a fix, the DHCP processing both in V4 and V6 are moved from L2
multicast nexthop to Vm ingress processing.

Change-Id: Ibf7e6a6b7c1201ff8c487ad561a9245831b81b51
closes-bug: #1525028

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/15850
Committed: http://github.org/Juniper/contrail-vrouter/commit/fdeb3c5bf6ba12f23b1c16eded5eeee24d90a25a
Submitter: Zuul
Branch: R2.21.x

commit fdeb3c5bf6ba12f23b1c16eded5eeee24d90a25a
Author: Divakar <email address hidden>
Date: Wed Dec 16 15:01:05 2015 +0530

Trapping DHCP packets in the ingress processing of Tap interface

Right the DHCP packets are processed in L2 multicast nexthop as DHCP
request packet is a multicast packet. In a scaled setup, this leads to
issues, as Agent receives the config late and VRF correspodning to VMI,
L2 broadcast route and multicast nexthop also does not get added. This
leads to DHCP request packet getting dropped.

As "D" flag is set on VMI by Agent when nova-compute plugs the
interface, the DHCP packet can be trapped to Agent without even the
configuration. Agent in this case can provide the short lease to VM.

So as a fix, the DHCP processing both in V4 and V6 are moved from L2
multicast nexthop to Vm ingress processing.

Change-Id: I2a01aa282b6662ea1ef5832770cc92da931ee833
closes-bug: #1525028

[OpenContrail Admin (ci-admin-f)]

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

[OpenContrail Admin (ci-admin-f)]

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

commit f7979367790ac566bf5460651d112eb947b8e4b1
Author: Divakar <email address hidden>
Date: Wed Dec 16 08:15:16 2015 -0800

Trapping DHCP packets in the ingress processing of Tap interface

Right the DHCP packets are processed in L2 multicast nexthop as DHCP
request packet is a multicast packet. In a scaled setup, this leads to
issues, as Agent receives the config late and VRF correspodning to VMI,
L2 broadcast route and multicast nexthop also does not get added. This
leads to DHCP request packet getting dropped.

As "D" flag is set on VMI by Agent when nova-compute plugs the
interface, the DHCP packet can be trapped to Agent without even the
configuration. Agent in this case can provide the short lease to VM.

So as a fix, the DHCP processing both in V4 and V6 are moved from L2
multicast nexthop to Vm ingress processing.

Change-Id: Ibf7e6a6b7c1201ff8c487ad561a9245831b81b51
closes-bug: #1525028