For the packets from VM to an ECMP destination we are forcing the
packets to be L3 routed. When ARP request comes for that VM from one of
the ECMP sources, though we have the stiching for VM's IP we give
Vhost's MAC to route the packets as packets need to be routed in this
direction as well. This functioanlity is added with the fix for the bug
1472796.
But the fix for the above bug should not handle the ARP request coming
from BMS (in TSN) as TSN is never a gateway for BMS. Such ARP request
should be flooded. So the fix is to not force the L3 if ARP request is
from BMS.
Reviewed: https:/ /review. opencontrail. org/16374 github. org/Juniper/ contrail- vrouter/ commit/ c5098ddeb28bf0d b2e0cc43a4cb59c 390d882ae1
Committed: http://
Submitter: Zuul
Branch: master
commit c5098ddeb28bf0d b2e0cc43a4cb59c 390d882ae1
Author: Divakar <email address hidden>
Date: Wed Aug 26 17:39:11 2015 +0530
No source IP lookup for ARP requests from BMS
For the packets from VM to an ECMP destination we are forcing the
packets to be L3 routed. When ARP request comes for that VM from one of
the ECMP sources, though we have the stiching for VM's IP we give
Vhost's MAC to route the packets as packets need to be routed in this
direction as well. This functioanlity is added with the fix for the bug
1472796.
But the fix for the above bug should not handle the ARP request coming
from BMS (in TSN) as TSN is never a gateway for BMS. Such ARP request
should be flooded. So the fix is to not force the L3 if ARP request is
from BMS.
Change-Id: Ib2626f27a89d34 cd98b04e6084aac 12ca8eb4ac9
closes-bug: #1485804