Description

A newly commissioned QFX5220 reports "Optics HW error" alarms on multiple ports immediately after boot. The affected optics remain in the init_fail state, and "show interfaces diagnostics" optics reports 0 V module voltage.

This behavior indicates a hardware-level issue with optics power delivery rather than a software or transceiver compatibility issue.

Symptoms

During initial commissioning, multiple front-panel ports report optics hardware errors.

++ Command outputs from the switch:

user@QFX5220> show system alarms no-forwarding

0 alarms currently active

user@QFX5220> show system firmware

Part            Type             Tag Current              Available            Status

                                      version              version

RE 0            BIOS ROM         0  33.01                33.01                OK

RE 0            TMC FPGA         1  7.1.20               7.1.20               OK

RE 0            RE FPGA          2  0.1.6                0.1.6                OK

RE 0            SSD Primary      3  SBR12005             SBR12050             OK

RE 0            SSD Secondary    4  SBR12005             SBR12050             OK

RE 0            Power CPLD       5  1.32                 1.32                 OK

RE 0            Optics CPLD      6  0.1.8                0.1.8                OK

RE 0            Fan CPLD         7  0xA2                 0.0                  OK

RE 0            BCM TH3 Flash    8  2.5                  2.10                 OK

 

user@QFX5220> show chassis alarms

6 alarms currently active

Alarm time Class Description

2025-10-03 10:30:24 XXXX Minor port-0/0/0: Optics HW error

2025-10-03 10:30:24 XXXX Minor port-0/0/1: Optics HW error

2025-10-03 10:30:24 XXXX Minor port-0/0/2: Optics HW error

2025-10-03 10:30:24 XXXX Minor port-0/0/3: Optics HW error

2025-10-03 10:30:24 XXXX Minor port-0/0/4: Optics HW error

2025-10-03 10:30:24 XXXX Minor port-0/0/5: Optics HW error

 

user@QFX5220:pfe> show picd optics fpc_slot 0 pic_slot 0 port 0 cmd list

PICD optics list

Name         State    LOS_LOL_Status             OtherAlarms  StateMachine  ErrCtr

 xcvr-0/0/0   PRESENT  RxLOS,TxLOS,RxLOL,TxLOL,   PRESENT      init_fail     0

 xcvr-0/0/1   PRESENT  RxLOS,TxLOS,RxLOL,TxLOL,   PRESENT      init_fail     0

 xcvr-0/0/2   PRESENT  RxLOS,TxLOS,RxLOL,TxLOL,   PRESENT      init_fail     0

 xcvr-0/0/3   PRESENT  RxLOS,TxLOS,RxLOL,TxLOL,   PRESENT      init_fail     0

 xcvr-0/0/4   PRESENT  RxLOS,TxLOS,RxLOL,TxLOL,   PRESENT      init_fail     0

 xcvr-0/0/5   PRESENT  RxLOS,TxLOS,RxLOL,TxLOL,   PRESENT      init_fail     0

 xcvr-0/0/6   ABSENT

 xcvr-0/0/7   ABSENT

 

  • Before customer power cycled the unit, we noticed that the optics are not getting voltage from the system.

 

user@QFX5220> show interfaces diagnostics optics et-0/0/1:0

Physical interface: et-0/0/1:0

   Module temperature                       : 0 degrees C / 32 degrees F

   Module voltage                           : 0 V

 

The optics are detected as present but are not receiving operating voltage from the system. As a result, the transceivers fail initialization and generate "Optics HW error" alarms.

Since the module voltage is reported as 0 V, this points to a hardware-related problem in the chassis power delivery path rather than a software issue.

Without additional power-related diagnostics, it is not possible to determine whether the failure originates from:

Power input
Power supply (PSU)
Internal chassis power distribution

Solution

If this issue is encountered, collect the following information before rebooting or power cycling the device:

  • show chassis alarms
  • show chassis power
  • show system firmware
  • show interfaces diagnostics optics <interface>
  • On PFE : show picd optics fpc_slot 0 pic_slot 0 port 0 cmd list
     

If optics on multiple ports simultaneously report 0 V module voltage and remain in the init_fail state,consider hardware replacement of the Chassis/PSU

Modification History

2026-05-14 : Article Created