This article mentions a scenario where after an upgrade or a reboot, the device prints incomplete serial number for the third party optics. Another QFX5100 running the same version and of the same model shows the SN correctly for the same optic without any issues.
The <show chassis hardware> shows incomplete output.
CLI output:
lab@qfx>show chassis hardware
Routing Engine 0 BUILTIN BUILTIN QFX Routing Engine
FPC 0 REV 28 650-056265 VXXXXXXXXX6 QFX5100-24Q-2P
CPU BUILTIN BUILTIN FPC CPU
PIC 0 BUILTIN BUILTIN 24x 40G-QSFP
Xcvr 1 NON-JNPR 47xxx UNKNOWN <<<< incomplete SN under cli output
In the chassisd logs, it would print a bogus SN which is only visible corruption seen in the logs.
lab@qfx> show log chassisd | match "Pno=NON-JNPR"
Feb 13 07:32:59 pic_copy_port_info:Got SFP Rev=, Pno=NON-JNPR, Sno=\x178\x0w\x0xx\x03\xxx
In PFE shell:
TFXPC0(qfx vty)# show qsfp 1 identifier
Identifier: QSFP+
Vendor SN: 47xxxxxxxx1 <<< Complete SN displayed in PFE output
Juniper PN: NON-JNPR
The issue seems to be with the register value which stores serial number information on the device getting corrupted which is causing the issue. The chassisd seems to be reading some values however it is not able to interpret the serial number correctly and hence this is not recorded as intended in the CLI output.
Please try the below and see if the issue gets resolved.
1. Soft reseat the SFP from PFE shell and check if the issue is resolved.
request pfe execute target fpc0 command "set cmqfx xcvr remove pic 0 port 1"
request pfe execute target fpc0 command "set cmqfx xcvr insert pic 0 port 1"
2. Physically reseat the SFP and check if the value is recorded correctly?
3. If the issue persists, please try restarting chassisd process in a maintenance window.
restart chassis-control gracefully
4. If the issue persists, please try to perform a power drain and check if this helps.
5. If the issue persists post power drain, then RMA the device.
2024-02-16 : Initial Publication2024-07-29 - Visibility modified