Skip to content

Commit

Permalink
VOQ: Nexthop for remote VOQ LC should be created on inband OIF. (#1823)
Browse files Browse the repository at this point in the history
VOQ nexthop for remote neighbors should be created on local inband port only for the kernel purpose. SAI should use actual RIF of the remote system port interface. #1686 seems to be break this condition and this change address it.
  • Loading branch information
minionatwork authored and judyjoseph committed Aug 18, 2021
1 parent 834c5c8 commit c5e90ab
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions orchagent/neighorch.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ bool NeighOrch::addNextHop(const NextHopKey &nh)
}

NextHopKey nexthop(nh);
if (m_intfsOrch->isRemoteSystemPortIntf(nexthop.alias))
if (m_intfsOrch->isRemoteSystemPortIntf(nh.alias))
{
//For remote system ports kernel nexthops are always on inband. Change the key
Port inbp;
Expand All @@ -202,7 +202,7 @@ bool NeighOrch::addNextHop(const NextHopKey &nh)
}

assert(!hasNextHop(nexthop));
sai_object_id_t rif_id = m_intfsOrch->getRouterIntfsId(nexthop.alias);
sai_object_id_t rif_id = m_intfsOrch->getRouterIntfsId(nh.alias);

vector<sai_attribute_t> next_hop_attrs;

Expand Down

0 comments on commit c5e90ab

Please sign in to comment.