|
Issue: PoE power fault errors occur on FortiSwitch-148F-FPOE v7.0.4 build0071 using PoE Firmware Version:2.2.3.
User-Impact: PoE powered devices (PDs) such as IP Phones or Access Points connecting to FortiSwitch-PoE ports do not power on.
Summary:
FortiSwitch shows the following PoE power fault errors in the below command outputs:
# get switch poe inline
# diagnose switch poe status <Port_ID>
Power Fault: Error Type 38 (Port is off: Discharged load)
Power Fault: Error Type 36 (Port is off: Voltage injection into the port)
Cause: When the FortiSwitch-PoE port is connected to a PSE (Power Sourcing Equipment) such as a 3rd party PoE FortiSwitch, the 3rd party PoE FortiSwitch may inject power into the FortiSwitch port. This causes the PoE errors 'Discharged load' and 'Voltage injection into the port', which may harm the device.
Fix:
1. 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 PDs like the Cisco 794x phone which was released decades ago. If the user doesn't have these old PDs, pre-standard detection should be kept disabled by default.
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. With FortiSwitchOS 7.0.4, '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
FortiSwitch CLI (For Standalone FortiSwitch units):
# config switch global
# show full
# set poe-pre-standard-detect disable
# end
2. Disable PoE status on the 3rd party PoE Switch or FortiSwitch that's plugged/connected into FortiSwitch port:
FortiGate CLI (For Managed FortiSwitch units):
# config switch-controller managed-switch
# edit <FortiSwitch_serial_number>
# config ports
# edit <port_name>
# set poe-status disable
# end
# end
FortiSwitch CLI (For Standalone FortiSwitch units):
# config switch physical-port
# edit <port
# set poe-status disable
# end
3. Power-cycle the affected FortiSwitch using the below command if the PoE error does not go away:
# execute reboot
Note: To avoid loss of configuration settings, download a backup of the FortiSwitch configuration before attempting a reboot.
See Page 77 of FortiSwitch 6.4.5 - Managed by FortiOS 6.4 for more information:
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/8f3df6f8-7879-11eb-9995-00505...
4. If error 36 and error 38 are gone after reboot, the issue is fixed.
5. If error 36 and error 38 are still present, log a ticket with Fortinet Support with the affected FortiSwitch Serial Number.
6. If this PoE error is occurring between two adjacent/interconnected FortiSwitch units, attach the following outputs from both the FortiSwitch units to the ticket for further analysis:
# get hardware status
# get switch poe inline
# diagnose switch poe status <Port_ID>
# show full-configuration switch interface
# show full-configuration system interface
# show full
# diag debug report
Reference KB: How to detect PoE fault on the FortiSwitch
https://community.fortinet.com/t5/FortiSwitch/Technical-Tip-How-to-detect-PoE-fault-on-the-FortiSwit...
|
