Do not store OriginVn attribute in Locally originated multicast route
Currently, OriginVn value is determined by looking at the virtual_network_index
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.
Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.
Reviewed: https:/ /review. opencontrail. org/32679 github. com/Juniper/ contrail- controller/ commit/ 0c456c401dbc8c6 eac7b00e85898b0 c77bb42319
Committed: http://
Submitter: Zuul (<email address hidden>)
Branch: master
commit 0c456c401dbc8c6 eac7b00e85898b0 c77bb42319
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jun 8 13:44:18 2017 -0700
Do not store OriginVn attribute in Locally originated multicast route
Currently, OriginVn value is determined by looking at the virtual_ network_ index
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.
Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.
Change-Id: I55c894f044b0b3 bce537b9ace94cd 836bfef0fa5
Closes-Bug: #1696853