ARP response on request interface for service instance
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 ARP request is received from service VM
Vrouter needs to send ARP response on the incoming interface
rather bridging the ARP reply packet, as FDB route points
to arbitrarly any of the service VM encap L2 nexthop.
After preparing the ARP 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/16604 github. org/Juniper/ contrail- vrouter/ commit/ c8a6f77cc82d190 aea1900a05bff2a b9ba061a7f
Committed: http://
Submitter: Zuul
Branch: master
commit c8a6f77cc82d190 aea1900a05bff2a b9ba061a7f
Author: Divakar <email address hidden>
Date: Thu Jun 11 09:23:26 2015 -0700
ARP response on request interface for service instance
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 ARP request is received from service VM
Vrouter needs to send ARP response on the incoming interface
rather bridging the ARP reply packet, as FDB route points
to arbitrarly any of the service VM encap L2 nexthop.
After preparing the ARP 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: Id90228b432e2d8 6360a7b77d332b7 cdb701cf144
closes-bug: #1461882