Description
This article describes various ways to detect a PoE fault on a FortiSwitch.
Scope
FortiSwitch-424D-POE v6.2.0 build0200.
Solution
1) Verify if the FortiSwitch Model and switchport supports PoE. Certain FortiSwitch models may only partially support PoE or not support PoE at all.
Check the FortiSwitch model datasheet for PoE support information.
2) Consider whether this a new unit or if, prior to this issue, FortiSwitch PoE has worked as expected.
3) Consider whether, prior to this issue, there was any change made on the FortiSwitch or if there was a power-outage that affected it.
4) Try resetting PoE on the FortiSwitch with the following command, then test PoE again:
# execute switch-controller poe-reset
5) Try the below test on the FortiSwitch during a maintenance window and check the PoE status after:
Unplug all cables, gracefully shutdown the FortiSwitch and wait for 15-30 minutes, then power on the device with only a console cable and PSU cord plugged in. Use the following command to execute a graceful shutdown:
# execute shutdown
6) Try factory-resetting the Switch once:
# execute factoryreset
Note: To avoid loss of configuration settings, download a backup of the FortiSwitch configuration before attempting a factory reset.
7) Check if the FortiSwitch port shows a Power Status fault:
# get switch poe inline
# diagnose switch poe status port11
Port(11) Power:0.00W, Power-Status code: 5(Fault)
Power-Up Mode: Normal Mode
Power Fault: Error Type 6 (Startup Failure)
Remote Power Device Type: IEEE802.3AF PD
Power Class: 0
Defined Max Power: 16.2W, Priority: Low.
Voltage: 0.00V
Current: 0mA
Temperature: 53.75 Centigrade
8) Check if the FortiSwitch hardware status shows an invalid PoE firmware version 0.0.0.0:
# get hardware status
Poe Firmware Version: 0.0.0.0
9) Check if running execute log display in FortiSwitch shows PoE warnings as shown below:
1969-12-31 16:02:07 log_id=0101002010 type=event subtype=poe pri=warning vd=root action="poe-debug" user="poed" status="None" msg=" doFailDetail:/bin/poed: time out
1969-12-31 16:02:07 log_id=0101002010 type=event subtype=poe pri=warning vd=root action="poe-debug" user="poed" status="None" msg=" doFailDetail:/bin/poed: time out
10) Consider upgrading the affected FortiSwitch to the latest firmware in the v6.2.x or 6.4.x stream. After, check if the issue persists.
11) Disable "poe-pre-standard-detection" if it's not in-use.
The purpose of "poe-pre-standard-detection" (also called legacy detection or capacitor detection) is to support old PD like the Cisco 794x phone which was released decades ago. If the user doesn't have any of these old PD, keep pre-standard detection disabled (the default option).
There was a bug in FortiSwitchOS 7.0.3 GA where "poe-pre-standard-detection" is always enabled.
The issue is fixed in FortiSwitchOS 7.0.4 GA. From FortiSwitchOS 7.0.4 and up, "poe-pre-standard-detection" is disabled by default.
FortiGate CLI (for Managed FortiSwitch units):
# config switch-controller managed-switch
# edit <FortiSwitch_serial_number>
# set poe-pre-standard-detection disable
# next
# end
FSW CLI (For Standalone FortiSwitch units):
# config switch global
# show full
# set poe-pre-standard-detect disable
# end
See page 10 of FortiSwitch 6.4.5 - Managed by FortiOS 6.4: https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/8f3df6f8-7879-11eb-9995-005056...
12) If the issue persists, log a ticket with Fortinet Support and attach the following logs from the affected FortiSwitch:
# get switch poe inline
# diagnose switch poe status
# get hardware status
# diagnose sys fan status
# diag sys pcb temp
# diagnose sys psu status
# show full
# diag debug report
Reference:
