Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SWSS] VOQ Nexthop for remote VOQ LC should be created on inband OIF. #1823

Merged
merged 1 commit into from
Aug 5, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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