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

Add a check if OID exists before setting Host Tx Ready Signal Enable #3232

Merged
merged 1 commit into from
Jul 22, 2024

Conversation

noaOrMlnx
Copy link
Collaborator

What I did
I added a query before setting host tx ready - must check that Oid exists before setting attribute to SAI.

Why I did it

When we do dynamic port breakout to a Fw-control port, portsorch receives a notification that something was deleted in TRANSCEIVER_INFO table from State DB, and tries to set HOST_TX_READY_SIGNAL_ENABLE attribute to false for the deleted OID.
The issue is the Oid is already deleted and we receive an error from SAI.

How I verified it
Run DPB on the switch
Details if related

@noaOrMlnx
Copy link
Collaborator Author

@prgeor
can you please review this host_tx_ready fix?

@prgeor
Copy link
Contributor

prgeor commented Jul 11, 2024

@noaOrMlnx Why OA is acting upon deleted ports?

prsunny pushed a commit that referenced this pull request Jul 12, 2024
This is a cherry-pick of #3232

What I did
I added a query before setting host tx ready - must check that Oid exists before setting attribute to SAI.
@prsunny
Copy link
Collaborator

prsunny commented Jul 12, 2024

@prgeor , can you please approve?

@noaOrMlnx
Copy link
Collaborator Author

@prgeor OA is acting upon port deletion, if a module was plugged out, and its entry was deleted from TRANSCEIVER_INFO table is State DB, so it could set HostTxReady enable to false.
In DPB case, the port OID is deleted, and we can't set any attribute to SAI.

}

SWSS_LOG_NOTICE("Could not set SAI_PORT_ATTR_HOST_TX_SIGNAL_ENABLE - OID does not exist 0x%" PRIx64, port.m_port_id);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@noaOrMlnx can we print the port name in the notice message?

@liat-grozovik liat-grozovik merged commit 2367bca into sonic-net:master Jul 22, 2024
16 of 17 checks passed
@bingwang-ms
Copy link
Contributor

Please fix the conflict to 202311 branch.

mssonicbld pushed a commit to mssonicbld/sonic-swss that referenced this pull request Jul 25, 2024
…onic-net#3232)

- What I did
I added a query before setting host tx ready - must check that Oid exists before setting attribute to SAI.

- Why I did it
When we do dynamic port breakout to a Fw-control port, portsorch receives a notification that something was deleted in TRANSCEIVER_INFO table from State DB, and tries to set HOST_TX_READY_SIGNAL_ENABLE attribute to false for the deleted OID.
The issue is the Oid is already deleted and we receive an error from SAI.

- How I verified it
Run DPB on the switch
@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202405: #3243

mssonicbld pushed a commit that referenced this pull request Jul 25, 2024
…3232)

- What I did
I added a query before setting host tx ready - must check that Oid exists before setting attribute to SAI.

- Why I did it
When we do dynamic port breakout to a Fw-control port, portsorch receives a notification that something was deleted in TRANSCEIVER_INFO table from State DB, and tries to set HOST_TX_READY_SIGNAL_ENABLE attribute to false for the deleted OID.
The issue is the Oid is already deleted and we receive an error from SAI.

- How I verified it
Run DPB on the switch
@yxieca
Copy link
Contributor

yxieca commented Aug 28, 2024

@noaOrMlnx can you help creating separate PR for 202311 branch? Thanks!

@noaOrMlnx
Copy link
Collaborator Author

@yxieca
Hi, PR for 202311 was already created and merged - #3233
Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants