Troubleshooting tip. FortiADC shows errors 'PSU temperature hits threshold' and 'PSU Device FAN is bad'

[JHelio]

Description	This article discusses the errors with PSU voltage.
Scope	FortiADC-400F v7.0.0.
Solution	At FortiADC, logs can be found PSU logs errors as below: date=2024-09-26 time=01:06:08 log_id=0003000242 type=event subtype=system pri=information vd=root msg_id=72697 submod=none user=none ui=none action=none status=success logdesc=Temperature msg=Temperature of PSU 2 back to normal date=2024-09-26 time=01:06:04 log_id=0003000241 type=event subtype=system pri=critical vd=root msg_id=72696 submod=none user=none ui=none action=none status=success logdesc=Temperature msg=PSU 2 temperature 4688.00 C hits threshold date=2024-09-25 time=13:16:05 log_id=0003000243 type=event subtype=system pri=error vd=root msg_id=72115 submod=none user=none ui=none action=none status=success logdesc=Velocity of FAN msg=PSU 1 Device FAN is bad date=2024-09-21 time=01:28:34 log_id=0003000243 type=event subtype=system pri=error vd=root msg_id=62730 submod=none user=none ui=none action=none status=success logdesc=Velocity of FAN msg=PSU 2 Device FAN is bad The command below can be executed to get more details: execute hwmon It is identified that some PSU models for FortiADC can generate such errors. Remove the PSU from the FortiADC fan slot (which is hot-swappable) and look for the P/N number: If the PSU P/N end with FTN without '-R2', RMA the PSU: If the PSU P/N ends with FTN-R2, it is the new version and should work normally.