Technical Tip: FortiSwitch Power Fault: Error Type 60 (Port is off: Calculated power > power limit)

Take the below example of Power Budget 370 with already 14xFortiAPs connected  : 

Unit Power Budget: 370.00W
Unit Guard Band: 19.00W
Unit Power Consumption: 152.00W
Unit Temperature: 60.00 Centigrade
Unit Poe Power Mode : Priority Based.

1. If there are 14xFortiAP (or any other PD device ) already up and connected.
   
   
2. All 14xPD devices are up with lldp negotiation power of 25 Watts.

get switch lldp neighbors-detail

Power requested: 25.0W <--
Power allocated: 25.0W <--
LLDP-MED, Extended Power-via-MDI:
Power type: PD
Power source: PSE
Power priority: critical
Power value: 25.0W

3. Since 14xFortiAPs or PD devices are already up (14x25W = 350 Watts) and reserved 350 Watts, when a 15th FortiAP or any PD device is trying to come up, it is hitting a unit power budget of 370 Watts.

    

4. That is why the error is seen as 'Power Fault: Error Type 60 (Port is off: Calculated power > power limit)'.

    

Note: Even though the actual power consumption of the FortiAPs is around 10 to 11 watts, 25 Watts for each FAP is already reserved.

If more FortiAP or any PD devices are to be added  there are a few suggestions below : 

1. Remove lldp profile default from ports where no PD are connected.
   
   
2. Remove med-tlv 'power-management' from lldp profile default/

Example:

lldp profile default has the below config : 

    set med-tlvs inventory-management network-policy location-identification power-management <--

config switch lldp profile
(profile) # edit defaul
(default) # set med-tlvs inventory-management network-policy location-identificatio
(default) # end

3. Alternatively, another lldp profile can be created without med-tlv 'power-management', and it can be assigned to ports where FortiAPs or any PDs are connected.