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

[routeorch]: Need to set drop route next hop ID to NULL #260

Closed
wants to merge 2 commits into from

Conversation

stcheng
Copy link
Contributor

@stcheng stcheng commented Jul 21, 2017

In orchagent, route's next hop packet action is set to DROP. But the previous
next hop object is still referenced by the route. This will cause the next
hop group removal failure.

Reset the drop route next hop ID to NULL to remove the reference for the
previous next hop object.

In orchagent, route's next hop packet action is set to DROP. But the previous
next hop object is still referenced by the route. This will cause the next
hop group removal failure.

Reset the drop route next hop ID to NULL to remove the reference for the
previous next hop object.
@stcheng
Copy link
Contributor Author

stcheng commented Jul 21, 2017

After the route is set back to DROP, the next hop ID is set to 0x0.

SAI_OBJECT_TYPE_ROUTE_ENTRY {"dest":"0.0.0.0/0","vr":"oid:0x3000000000002"}   
    SAI_ROUTE_ATTR_NEXT_HOP_ID   : oid:0x0                                    
    SAI_ROUTE_ATTR_PACKET_ACTION : SAI_PACKET_ACTION_DROP                     

@stcheng
Copy link
Contributor Author

stcheng commented Oct 4, 2017

deprecated since #261 is already merged.

@stcheng stcheng closed this Oct 4, 2017
@stcheng stcheng deleted the remove branch October 4, 2017 00:01
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
lukasstockner pushed a commit to genesiscloud/sonic-swss that referenced this pull request Apr 2, 2023
…t#260)

Signed-off-by: vaibhav-dahiya [email protected]

Description
Currently is_link_active API was broken because it was not using the target param in the routine to give back the correct link_status of ecah side. With this change it gives the correct result.

Motivation and Context
Required for MUX_CABLE_INFO table in streaming telemetry if the cable is disconnected or the link is down.

redis-cli -n 6 hgetall "MUX_CABLE_INFO|Ethernet16"
"
 9) "link_status_self"
10) "down"
11) "link_status_peer"
12) "up"
13) "link_status_nic"
14) "up"
How Has This Been Tested?
Tested on actual Arista7050cx3 testbed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants