Troubleshooting Tip: Validating PoE issues on a FortiSwitch connecting with PoE devices

[riteshpv]

Description	This article outlines the steps to follow when a PoE device fails to power up after being connected for the first time to a FortiSwitch.
Scope	All FortiSwitch PoE models.
Solution	There are two different PoE models in FortiSwitch: one is the half PoE model (e.g., FS108EP), and the other is the full PoE model (e.g., FS108EF). Note that the FortiSwitch port to which the PoE device is connected should have PoE capability. Verify this by using the following command: get switch poe inline Unit Power Budget: 240.00W Unit Guard Band: 19.00W Unit Power Consumption: 22.60W Unit Poe Power Mode : Priority Based. Interface Status State Max-Power(W) Power-consumption(W) Priority Class Error ------------------------------------------------------------------------------------------------------ port1 Enabled Delivering Power 16.2 2.20 Low 1 port2 Enabled Delivering Power 16.2 2.10 Low 1 port3 Enabled Delivering Power 16.2 2.10 Low 1 port4 Enabled Delivering Power 16.2 2.10 Low 1 port5 Enabled Delivering Power 16.2 2.10 Low 1 port6 Enabled Delivering Power 16.2 2.20 Low 1 port7 Enabled Delivering Power 16.2 2.10 Low 1 port8 Enabled Searching 0.00 0.00 Low 0 port9 Enabled Searching 0.00 0.00 Low 0 port10 Enabled Searching 0.00 0.00 Low 0 port11 Enabled Searching 0.00 0.00 Low 0 port12 Enabled Searching 0.00 0.00 Low 0 Considering the PoE device was connected to port13 then with above command, it can be determined that PoE is not available on that port. Additionally, verify from the config on the FortiSwitch that the port has PoE enabled: show full-configuration switch physical-port port1   config switch physical-port edit "port1" set cdp-status disable   set description '' set dmi-status global set energy-efficient-ethernet disable set flapguard disabled set flow-control disable set fortilink-p2p disable set l2-learning enabled set lldp-profile "default-auto-isl" set lldp-status tx-rx set loopback disable set max-frame-size 9216 set poe-disconnection-type DC set poe-port-mode IEEE802_3AT set poe-port-priority low-priority set poe-pre-standard-detection disable set poe-status enable  <- Poe status enabled on the port. set speed auto set status up set storm-control-mode global next end Note: Replace port1 with the port number connected to the PoE device facing issues. If the PoE device is connected to PoE ports, verify that the device is drawing power by using the following command: get switch poe inline Interface Status State Max-Power(W) Power-consumption(W) Priority Class Error ------------------------------------------------------------------------------------------------------ port1 Enabled Delivering Power 16.2 2.20 Low 1 As seen above, the power provided by FortiSwitch on the port is 802.3af (nearly 15W) and the power consumption is 2.20 (drawing power). If the PoE device is not powering up, then verify if the PoE device requires 802.3at (nearly 30W) power. config switch physical-port edit "port1" set poe-port-mode IEEE802_3AT    <- Default is 802.3af. next end If the PoE device is not powering up, check for any errors related to PoE. Refer to the 'Related articles' section at the end of this article for further guidance. If no errors are present, verify the PoE device power requirement. Document the PoE device model number, available datasheet, and, if applicable, the software version of PoE device. Verify whether the PoE device works with any alternative power sources such as an external DC power supply, a PoE injector, or another PoE switch. If the device functions with any of these, document the model number of the power source, any available datasheet, and, if applicable, the software version of the other switch. If possible, test with a different PoE device model. Document the newly tested PoE device powers up or not, including its datasheet, model number, and OS version.  Test the PoE device on different FortiSwitch ports. For example, if PoE is available from FortiSwitch port 1 to port 20, conduct tests on port 1, port 5, port 10, port 15, and port 20. If certain ports are unavailable, test on the available ones. This will help determine if the issue is specific to any particular FortiSwitch port. If issues are still observed, open a TAC case and collect the following logs with a PoE device connected to FortiSwitch, and also provide the documented info and observation as discussed above. show full-configuration diagnose debug crashlog read diagnose debug report get switch poe inline diagnose switch poe status port1 Note: Replace port1 with the port number of the connected PoE device facing the issue. Advisory: Do not connect any power source to a FortiSwitch port that induces power. For example, if there are two FortiSwitch devices with PoE enabled on port 1, do not connect port 1 of these devices to each other with PoE enabled. Make sure to disable PoE on these ports before connecting them. config switch physical-port edit "port1" set poe-status disable next end If the PoE devices do not require it, do not activate the 'poe-pre-standard-detect' feature. If this setting cannot be located in the FortiSwitch port, check in switch global mode. Note: This feature is disabled by default show full-configuration switch physical-port port<no> show full switch global Related articles: Troubleshooting Tip: Power Fault: Error Type 28 (Port is off: Non-802.3af powered device) Technical Tip: POE fault 4 - Port is yet undefined Technical Tip: 'Power Fault: Error Type 36 (Port is off: Voltage injection into the port)' on FortiS... Troubleshooting Tip: Diagnosing a PoE fault on a FortiSwitch