|
This command is available only via FortiGate and not directly on FortiSwitch.
The command set poe-capable 1 enables PoE functionality (PoE config) on a particular FortiSwitch or FortiSwitch port managed by FortiGate.
This setting is not available for manual configuration changes as it is automatically enabled based on the FortiSwitch’s capability.
Example:
Consider a FortiSwitch S248EF, which has 52 ports, with 1 to 48 of which support PoE.
When this FortiSwitch is registered with the FortiGate, ports 1 to 48 will have the default 'poe-capable' value set to 1, while ports 49 to 52 will have 'poe-capable' set to 0.
To verify the configuration, run the following command:
config switch-controller managed-switch
edit "FSW-serial-no" <--- Replace with the FortiSwitch serial number or name depending on the configuration/version.
config ports
edit port1
show full <-- This will display the full configuration of port1.
If poe-capable is set to 1, additional PoE settings will be available in the configuration. If poe-capable is set to 0, other PoE-related configurations will not be present.
Example PoE settings when poe-capable is set to 1:
set poe-status enable
set poe-pre-standard-detection disable
set poe-capable 1
set poe-port-mode ieee802-3at
set poe-port-priority low-priority
If an attempt is made to manually change the poe-capable setting, the following error will occur:
set poe-capable 0
this operation is not permitted.
Command fail. Return code -9999
However, it is possible to change the value using the unset command. For example, to unset poe-capable on port1:
config switch-controller managed-switch
edit "FSW-serial-no"
config ports
edit port1
unset poe-capable
next
end
With this configuration, the poe-capable value will change from 1 to 0. However, this does not mean the port is incapable of providing power. The PoE configuration will no longer be available from the FortiGate, but PoE functionality will still exist on the FortiSwitch itself, and connected devices will continue to receive power.
This change will revert if the FortiSwitch reboots.
If it is necessary to disable the PoE on the FortiSwitch port from FortiGate then refer to config enable/disable poe.
flcfgd Debug Output:
The following output is collected with flcfgd debug that demonstrates, once the switch (hostname test_name) reboots, PoE capabilities are re-synced, with ports 1 to 48 set to poe_capable=yes, and ports 49 to 52 set to poe_capable=(null).
273s:643ms:417us flcfg_process_switch_offline_event[435]:got offline event for vfid 0 switch test_name
273s:643ms:515us flcfg_process_switch_online_event[409]:got online event for vfid 0 switch test_name
273s:643ms:534us flcfg_process_switch_online_event[417]:online configuration is scheduled for switch test_name
273s:651ms:351us flcfg_trigger_lldp_nbr_sync[228]:trigger lldp nbr sync on sw test_name
273s:656ms:415us flcfg_remove_msw_sync_errors[1143]:No file /tmp/switch-controller/error-log/test_name to remove.
0: config vdom
0: edit root
0: config system dns-database
0: edit "fortiswitch"
0: config dns-entry
0: edit 0
0: set hostname "test_name"
0: set ip 1.1.1.5
0: end
0: end
0: end
273s:663ms:520us flcfg_update_physical_port_poe_type[839]:Processing data for sw test_name vfid 0
[show_walker_construct:85] open('/tmp/system.conf.5573.5YlSeD) to save config of 'root'
write config file success, prepare to save '/tmp/system.conf.5573.5YlSeD' to '/data/./config/sys_vd_root+root.conf.gz' on flash
flash: block_sz=1024, free_blocks=131207
[__create_file_new_version:312] the new version config file '/data/./config/sys_vd_root+root.conf.gz.v000079559' is created
[symlink_config_file:379] a new version of '/data/./config/sys_vd_root+root.conf.gz' is created: /data/./config/sys_vd_root+root.conf.gz.v000079559
[symlink_config_file:423] the old version '/data/./config/sys_vd_root+root.conf.gz.v000079558' is deleted
[symlink_config_file:425] '/data/./config/sys_vd_root+root.conf.gz' has been symlink'ed to the new version '/data/./config/sys_vd_root+root.conf.gz.v000079559'. The old version '/data/./config/sys_vd_root+root.
conf.gz.v000079558' has been deleted
zip config file /data/./config/sys_vd_root+root.conf.gz success!
275s:252ms:227us __flcfg_parse_port_data[791]:port=port1 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:279us __flcfg_parse_port_data[791]:port=port2 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:295us __flcfg_parse_port_data[791]:port=port3 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:312us __flcfg_parse_port_data[791]:port=port4 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:327us __flcfg_parse_port_data[791]:port=port5 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:342us __flcfg_parse_port_data[791]:port=port6 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:357us __flcfg_parse_port_data[791]:port=port7 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:373us __flcfg_parse_port_data[791]:port=port8 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:388us __flcfg_parse_port_data[791]:port=port9 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:403us __flcfg_parse_port_data[791]:port=port10 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:418us __flcfg_parse_port_data[791]:port=port11 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:434us __flcfg_parse_port_data[791]:port=port12 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:449us __flcfg_parse_port_data[791]:port=port13 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:464us __flcfg_parse_port_data[791]:port=port14 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:479us __flcfg_parse_port_data[791]:port=port15 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:494us __flcfg_parse_port_data[791]:port=port16 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:510us __flcfg_parse_port_data[791]:port=port17 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:525us __flcfg_parse_port_data[791]:port=port18 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:540us __flcfg_parse_port_data[791]:port=port19 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:555us __flcfg_parse_port_data[791]:port=port20 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:570us __flcfg_parse_port_data[791]:port=port21 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:585us __flcfg_parse_port_data[791]:port=port22 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:600us __flcfg_parse_port_data[791]:port=port23 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:615us __flcfg_parse_port_data[791]:port=port24 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:630us __flcfg_parse_port_data[791]:port=port25 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:646us __flcfg_parse_port_data[791]:port=port26 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:661us __flcfg_parse_port_data[791]:port=port27 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:676us __flcfg_parse_port_data[791]:port=port28 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:692us __flcfg_parse_port_data[791]:port=port29 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:707us __flcfg_parse_port_data[791]:port=port30 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:722us __flcfg_parse_port_data[791]:port=port31 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:737us __flcfg_parse_port_data[791]:port=port32 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:752us __flcfg_parse_port_data[791]:port=port33 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:767us __flcfg_parse_port_data[791]:port=port34 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:798us __flcfg_parse_port_data[791]:port=port35 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:813us __flcfg_parse_port_data[791]:port=port36 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:828us __flcfg_parse_port_data[791]:port=port37 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:843us __flcfg_parse_port_data[791]:port=port38 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:860us __flcfg_parse_port_data[791]:port=port39 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:875us __flcfg_parse_port_data[791]:port=port40 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:889us __flcfg_parse_port_data[791]:port=port41 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:904us __flcfg_parse_port_data[791]:port=port42 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:919us __flcfg_parse_port_data[791]:port=port43 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:933us __flcfg_parse_port_data[791]:port=port44 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:948us __flcfg_parse_port_data[791]:port=port45 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:963us __flcfg_parse_port_data[791]:port=port46 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:977us __flcfg_parse_port_data[791]:port=port47 type=RJ45 poe_capable=yes group=PoE+
275s:252ms:992us __flcfg_parse_port_data[791]:port=port48 type=RJ45 poe_capable=yes group=PoE+
275s:253ms:7us __flcfg_parse_port_data[791]:port=port49 type=SFP poe_capable=(null) group=SFP
275s:253ms:22us __flcfg_parse_port_data[791]:port=port50 type=SFP poe_capable=(null) group=SFP
275s:253ms:36us __flcfg_parse_port_data[791]:port=port51 type=SFP poe_capable=(null) group=SFP
275s:253ms:51us __flcfg_parse_port_data[791]:port=port52 type=SFP poe_capable=(null) group=SFP
|
