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

[Mellanox] Re-initialize SFP object when detecting a new SFP insertion #5695

Merged
merged 1 commit into from
Oct 23, 2020

Conversation

Junchao-Mellanox
Copy link
Collaborator

@Junchao-Mellanox Junchao-Mellanox commented Oct 22, 2020

- Why I did it

SFP object will be initialized to a certain type even if no SFP present. A case could be:

  1. A SFP object is initialized to QSFP type by default when there is no SFP present
  2. User insert a SFP with an adapter to this QSFP port
  3. The SFP object fail to read EEPROM because it still treats itself as QSFP.

This PR fixes this issue.

- How I did it

When detecting a new SFP insertion, read its SFP type and DOM capability from EEPROM again.

- How to verify it

Manual test

- Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

@jleveque
Copy link
Contributor

Retest vsimage please

@Junchao-Mellanox
Copy link
Collaborator Author

retest broadcom please

@jleveque jleveque merged commit 15c59e1 into sonic-net:master Oct 23, 2020
abdosi pushed a commit that referenced this pull request Oct 30, 2020
#5695)

When detecting a new SFP insertion, read its SFP type and DOM capability from EEPROM again.

SFP object will be initialized to a certain type even if no SFP present. A case could be:

1. A SFP object is initialized to QSFP type by default when there is no SFP present
2. User insert a SFP with an adapter to this QSFP port
3. The SFP object fail to read EEPROM because it still treats itself as QSFP.

This PR fixes this issue.
@Junchao-Mellanox Junchao-Mellanox deleted the fix_insert_sfp branch November 18, 2020 01:06
santhosh-kt pushed a commit to santhosh-kt/sonic-buildimage that referenced this pull request Feb 25, 2021
sonic-net#5695)

When detecting a new SFP insertion, read its SFP type and DOM capability from EEPROM again.

SFP object will be initialized to a certain type even if no SFP present. A case could be:

1. A SFP object is initialized to QSFP type by default when there is no SFP present
2. User insert a SFP with an adapter to this QSFP port
3. The SFP object fail to read EEPROM because it still treats itself as QSFP.

This PR fixes this issue.
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.

4 participants