-
Notifications
You must be signed in to change notification settings - Fork 612
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/Nvidia SN2700 - show platform failure #2771
Comments
admin@sonic:~$ sudo generate_dump The dump file itself is 43MB and too large to upload directly. What is the preferred file repo service to utilize? |
Description: When attempting to pull system details on a Mellanox/Nvidia SN2700 utilizing the "show platform" commands the results are either outright errors or display incorrect information. This appears to be due to device files not existing within the sonic-mgmt docker.
Branches: Master, 202211 with builds on April 2nd, 2023j.
Steps to reproduce the issue
Describe the results you received
### admin@sonic:~$ show platform summary
Platform: x86_64-mlnx_msn2700-r0
HwSKU: Mellanox-SN2700
ASIC: mellanox
ASIC Count: 1
Serial Number: N/A
Model Number: N/A
Hardware Revision: N/A
### admin@sonic:~$ show platform fan
Fan Not detected
### admin@sonic:~$ show platform firmware
Traceback (most recent call last):
File "/usr/local/bin/fwutil", line 5, in
from fwutil.main import cli
File "/usr/local/lib/python3.9/dist-packages/fwutil/init.py", line 3, in
from . import main
File "/usr/local/lib/python3.9/dist-packages/fwutil/main.py", line 40, in
pdp = PlatformDataProvider()
File "/usr/local/lib/python3.9/dist-packages/fwutil/lib.py", line 162, in init
self.chassis_component_map = self.__get_chassis_component_map()
File "/usr/local/lib/python3.9/dist-packages/fwutil/lib.py", line 168, in __get_chassis_component_map
chassis_name = self.__chassis.get_name()
File "/usr/local/lib/python3.9/dist-packages/sonic_platform/chassis.py", line 524, in get_name
self.initialize_eeprom()
File "/usr/local/lib/python3.9/dist-packages/sonic_platform/chassis.py", line 504, in initialize_eeprom
self._eeprom = Eeprom()
File "/usr/local/lib/python3.9/dist-packages/sonic_platform/eeprom.py", line 61, in init
raise RuntimeError("No syseeprom symlink found")
RuntimeError: No syseeprom symlink found
admin@sonic:~$ show platform psustatus
Error: Failed to get the number of PSUs
Error: Failed to get PSU status
Error: failed to get PSU status from state DB
### admin@sonic:~$ show platform ssdhealth
Error response from daemon: Container 94fb7159e219359e9d24424559ac1b225c488d60adca5f71ad28085ca09d9348 is not running
Device Model : StorFly VSF302XC016G-MLX1
Health : N/A
Temperature : 100C
### admin@sonic:~$ show platform syseeprom
Failed to read system EEPROM info from DB
### admin@sonic:~$ show platform temperature
Thermal Not detected
Describe the results you expected
The expected results is for the show platform commands to function properly without crashing, error messages or erroneous results.
Additional information you deem important (e.g. issue happens only occasionally)
This issue occurs every time due to the source of the issue. It appears the issue is the result of the following symlink target files not existing within the sonic-mgmt docker
admin@sonic:~$ ls -l /var/run/hw-management/eeprom
total 0
lrwxrwxrwx 1 root root 71 Apr 2 19:41 cpu_info -> /sys/devices/platform/mlxplat/i2c_mlxcpld.1/i2c-1/i2c-16/16-0051/eeprom
lrwxrwxrwx 1 root root 71 Apr 2 19:40 fan1_info -> /sys/devices/platform/mlxplat/i2c_mlxcpld.1/i2c-1/i2c-11/11-0050/eeprom
lrwxrwxrwx 1 root root 71 Apr 2 19:40 fan2_info -> /sys/devices/platform/mlxplat/i2c_mlxcpld.1/i2c-1/i2c-12/12-0050/eeprom
lrwxrwxrwx 1 root root 71 Apr 2 19:40 fan3_info -> /sys/devices/platform/mlxplat/i2c_mlxcpld.1/i2c-1/i2c-13/13-0050/eeprom
lrwxrwxrwx 1 root root 71 Apr 2 19:41 fan4_info -> /sys/devices/platform/mlxplat/i2c_mlxcpld.1/i2c-1/i2c-14/14-0050/eeprom
lrwxrwxrwx 1 root root 69 Apr 2 19:41 vpd_info -> /sys/devices/platform/mlxplat/i2c_mlxcpld.1/i2c-1/i2c-8/8-0051/eeprom
Output of
show version
The text was updated successfully, but these errors were encountered: