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 front panel led support and transceiver monitor for inventec d7054 and d7032 #1660

Closed
wants to merge 1 commit into from

Conversation

klhaung
Copy link
Contributor

@klhaung klhaung commented Apr 30, 2018

[device]: Modify SFPUtil for inventec-d7032
[device]: Add front panel led support for Inventec-d7032
[platform]: Add transceiver monitor daemon for Inventec-d7032 and Inventec-d7054

- What I did

  • Add front panel led support for inventec-d7032
  • Add transceiver monitor daemon for Inventec-d7032 and Inventec-d7054
  • Bugfix in sfputil.py used for inventec-d7032

- How I did it

  • Add two pythons scripts which is spawned by debian init script for monitoring port status
  • Add led initialization file for Inventec d7032

- How to verify it

  • Build image, install on device platform to and make sure it is worked properly

- Description for the changelog

Add front panel led support and transceiver monitor for invnetec d7054 and d7032

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

[device]: Add front panel led support for Inventec-d7032
[platform]: Add transceiver monitor daemon for Inventec-d7032 and Inventec-d7054
@klhaung
Copy link
Contributor Author

klhaung commented May 2, 2018

From the console output of jenkin build, the error messages are

slave.mk:381: recipe for target 'target/docker-dhcp-relay.gz' failed
make: *** [target/docker-dhcp-relay.gz] Error 1
Makefile:81: recipe for target 'target/sonic-broadcom.bin' failed
make: *** [target/sonic-broadcom.bin] Error 2

It looks to me that it is not due to our fix. Please advice how to resolve it for merging the fix into SONiC.

Thanks

@klhaung
Copy link
Contributor Author

klhaung commented May 2, 2018

The issue is fixed in this PR, #1659. Close this one and create new one for merging.

@klhaung klhaung closed this May 2, 2018
@klhaung klhaung reopened this May 2, 2018
@klhaung
Copy link
Contributor Author

klhaung commented May 4, 2018

Close this pull request because of the file permission of added python scripts.

@klhaung klhaung closed this May 4, 2018
lguohan pushed a commit that referenced this pull request Jun 21, 2021
Update sonic-utilities submodule. This include the following commits:

285960d [config]: Update environment file during config reload (#1673)
3f0ecd5 [config] Remove "reset failed" print lines from config reload (#1654) 
a1c8751 Make the soft-reboot available in the SONiC image on master (#1681)
45e7b71 [Mellanox] Add all results from saisdkdump to the techsupport on Mellanox switches (#1660)
carl-nokia pushed a commit to carl-nokia/sonic-buildimage that referenced this pull request Aug 7, 2021
Update sonic-utilities submodule. This include the following commits:

285960d [config]: Update environment file during config reload (sonic-net#1673)
3f0ecd5 [config] Remove "reset failed" print lines from config reload (sonic-net#1654) 
a1c8751 Make the soft-reboot available in the SONiC image on master (sonic-net#1681)
45e7b71 [Mellanox] Add all results from saisdkdump to the techsupport on Mellanox switches (sonic-net#1660)
theasianpianist pushed a commit to theasianpianist/sonic-buildimage that referenced this pull request Feb 5, 2022
Fix issue - sonic-net#4009

When a member port is added to port-channel, create a unique LACP key.
When adding a member port to port-channel set the LACP key to a unique number.
The number is extracted from the port-channel name and will be the number at the end of the port-channel name with an additional digit at the beginning in order to make sure that this number will be unique in the system.

Why I did it
If LACP key is not set, then the peer will not be able to distinguish the ports which are connected to different port-channels, as it will receive the LACP key as 0 for all the ports from different port-channels.

How I verified it
I configure a SONiC switch to have two port-channels and on a second switch, I created one port-channel for both links between the switches.
On the second switch only one of the ports comes up in the PO and the other one stayed down.
taras-keryk pushed a commit to taras-keryk/sonic-buildimage that referenced this pull request Apr 28, 2022
…anox switches (sonic-net#1660)

- What I did
Enhance the way techsupport collects dumps provided by SAI and do not keep them in the filesystem once the techsupport is created.

- How I did it
Create a temporary directory once techsupport script is executed, gather all files SAI dumps created, add them to the tech support and remove the temporary directory and files.
Remove direct call to FW trace collection as it is done now by SAI dump

- How to verify it
Run techsupport, verify newly created files are part of it including mlxtrace which is no longer called directly by the techsupport script.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant