In in-network service instance case, when service scaling
is more than one, all the instances are going to have the
same mac address and IP address. Inet route points to
ECMP composite nexthop but FDB route does not point to ECMP
nexthop. So when neighbour request is received from service VM
Vrouter needs to send response on the incoming interface
rather bridging the reply packet, as FDB route points
to arbitrarly any of the service VM encap L2 nexthop.
After preparing the reply packet,bridge lookup is done
and outgoing interface is compared against ingress interface.
If they are not same, reply packet is transmitted on
ingress interface.
Reviewed: https:/ /review. opencontrail. org/24973 github. org/Juniper/ contrail- vrouter/ commit/ e894f7e028afd0a 879d52f4f68a7da f1c56dedf6
Committed: http://
Submitter: Zuul
Branch: R3.0
commit e894f7e028afd0a 879d52f4f68a7da f1c56dedf6
Author: Divakar D <email address hidden>
Date: Sat Oct 8 19:25:38 2016 +0530
Transmit V6 Neighbour advertisement on the receiving interface
This fix is IPV6 equivalent of /review. opencontrail. org/#/c/ 11506/.
https:/
In in-network service instance case, when service scaling
is more than one, all the instances are going to have the
same mac address and IP address. Inet route points to
ECMP composite nexthop but FDB route does not point to ECMP
nexthop. So when neighbour request is received from service VM
Vrouter needs to send response on the incoming interface
rather bridging the reply packet, as FDB route points
to arbitrarly any of the service VM encap L2 nexthop.
After preparing the reply packet,bridge lookup is done
and outgoing interface is compared against ingress interface.
If they are not same, reply packet is transmitted on
ingress interface.
Change-Id: Ib0113227019d7a 452541129843813 a647d388b36
closes-bug: #1461882