POE Configuration
show interface poe
Section titled “show interface poe”[Command]
show interface poe
[Purpose]
Display interface POE information
[View]
System view
[Use Cases]
sonic# show interface poeshow interface poe diagnose
Section titled “show interface poe diagnose”[Command]
show interface poe diagnose
[Purpose]
Display interface POE initialization information
[View]
System view
[Usage Scenario]
This command displays information including POE hardware version, POE status, current POE temperature, alarm temperature, and the number of internal POE resets.
[Notes]
If the command results in a “device busy” message, it is normal. This indicates that the system is currently retrieving POE power information. Simply reissue the command to get the results.
[Use Cases]
sonic# show interface poe diagnosePSE device information:field value----------------- ------------------------------------version 0x4a02status OK Expected PoE device Found (Zone1)eventtemperature 48 Ctemperature-alarm 110 Creset-count 0initialized TruePSE wrong port map:Interface Current Id Expect Id----------- ------------ -----------show interface poe pd alive-check status
Section titled “show interface poe pd alive-check status”[Command]
show interface poe pd alive-check status
[Purpose]
Display the PoE PD Alive Check configuration and status information for the interface.
[View]
System view
[Usage Scenario]
This command can display the configuration information for PoE PD Alive Check and its real-time status monitoring results.
[Notes]
When the interface’s PoE feature is disabled, both the last_ping_time and alive status will display as N/A.
[Use Cases]
sonic# show interface poe pd alive-check status----------------------------------------------------------------------config for delay/interval/err_threshold/action/reboot_interval+-------------+--------+------------------+-------------+---------------------+---------+----------+| Interface | mode | config | pd-ip | last_ping_time | alive | err_count |+=============+========+==================+=============+=====================+=========+===========+| Ethernet2 | enable | 60/15/3/alarm/30 | 192.168.0.1 | 2025-09-13 16:22:16 | True | 2 |+-------------+--------+------------------+-------------+---------------------+---------+----------+show interface poe status comment
Section titled “show interface poe status comment”[Command] show interface poe status comment
[Purpose] Show the meaning of interface PoE status codes
[View] System View
[Use Cases]
sonic# show interface poe status commentStatus Code Comment------------- ------------------------------------------------------------------------------------------------------------------------------------------------0x3d Port power-up was denied due to (PD class report power > user predefined power value). Note: Power denied counter will advance0x3c Calculated power > power limit0x22 Port configuration was changed or port mode was changed, causing the port to turn off. This status is momentary (2s delay). After the delay, the port status is updated according to the new configuration/mode0x20 Power Management function shuts down port due to lack of power. Port is shut down or remains off0x26 Port fails due to system voltage supply through other port. Check other port for status 0x24. This error is linked with mask 0x1F enable0x24 Port fails due to voltage being applied to the port from external source0x25 Fail due to out-of-range capacitor value or Fail due to detected short value (when mask 0x04 is set)0x35 Port temperature protection mechanism was activated0x34 Short condition was detected. For example, cable crystal head may have short circuit0x37 The device returns an unknown port status for the software currently not used0x36 The die temperature is above safe operating value0x1c Non-Standard PD connected0x1b Interim state during line detection. Status changes after detection process is completed0x41 Port was not turned on due to hardware power limit (PD class power > Hardware class limit) For example, PoH PD over M device port0x43 Illegal class0x45 Port is off -- after the Host crash, the port is off and waits for the Host command to proceed with new detection cycles. The port was delivering power before the Host crash but was configured to be forced-shut when Host crashed0x46 Port is off -- after the Host crash, the port is off and waits for the Host command to proceed with the new detection cycles. The port was enabled and not delivering power before the Host crash and was configured to be forced-shut when Host crashed0x47 Port is at force power error, according to the IEEE test mode error. The port was forced power and Host crash occurred0x48 During crash, a recovery port delivering power was disconnected due to UDL0x49 During crash, a recovery port delivering power was disconnected due to PG event0x08 Hardware pin disables all ports0x06 Mains voltage is higher than the maximum voltage limit0x07 Mains voltage is lower than the minimum voltage limit0x84 Non-IEEE PD was detected using 4P matrix in BT mode and power as 4-pair0x85 802.3BT-SSPD was detected using 4P matrix and operate as 2P, if requested class <= 40x86 802.3BT-SSPD was detected using 4P matrix and operate as 4P, if requested class > 40x87 802.3BT-DSPD was detected using 4P matrix and operate as 2P due to 4-pair candidate validation in two cycles0x80 Non-IEEE PD was detected using 2P matrix in the BT mode0x81 802.3BT-compliant PD was detected using 2P matrix0x82 Signature failure on Alt-B, allowing power only on Alt-A(Non-IEEE or Legacy PD)0x83 Non-IEEE PD was detected using 4P matrix in BT mode and power as 2-pair0x1f Overload state according to 802.3AF/AT (current is above Icut(about 1A for each 2P)) or (PM3 != 0 and (PD class report > user predefined power value))0x1e Underload state according to 802.3AF/AT (current is below Imin(about 10mA))0x88 802.3BT-DSPD was detected using 4P matrix and operate as 2P0x89 802.3BT-DSPD was detected using 4P matrix and operate as 4P0x1a User command set port to off0x4a During crash, a recovery port delivering power was disconnected due to OVL0x4b During crash, a recovery port delivering power was disconnected due to SC0xa8 Port is not connected0x12 Port does not respond. Hardware fault, system initialization, or PoE controller lost communication with PoE port device allocated for this port. (part of the Refresh function).0x11 Port is not mapped to physical port, port is in unknown state, or PoE controller fails to communicate with PoE port device allocated for this port0x91 Port matrix 4P and delivers power on both pair sets due to the Force Power command0x90 Port matrix 2P and delivers power due to the Force Power command0xa7 This error is reported only in 4-pair port when invalid connection check signature was detected. In such a case, detection fail counter is incremented0xa0 The Force Power was set, one of the port pair sets stop delivering power, from at least one reason out of various reasons(system related, device related, port related, or Pair set related)0x0c Fewer ports are available than the maximum number of ports that the Controller can support. Unavailable ports are considered off. Currently not usedpoe enable
Section titled “poe enable”[Command]
poe enable
no poe enable
[Purpose]
Enable POE power supply function of the interface
[View]
Interface view
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe enablepoe delay
Section titled “poe delay”[Command]
poe-delay time
no poe-delay
[Purpose]
Configure the delayed start time of the interface POE function
[Parameter]
| Parameter | Description |
|---|---|
| time | Range of values: 0-3600 |
[View]
Interface view
[Usage Scenario]
This command is used to delay the activation of Power over Ethernet (PoE) power supply on an interface based on actual usage requirements. When the uplink link state stabilizes, and the protocols are running correctly, PoE power is supplied to the connected PoE devices. This delay mechanism is useful for ensuring that PoE devices receive power only when the network is stable and ready to support them.
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe delay 300poe max-power
Section titled “poe max-power”[Command]
poe max-power power
no poe max-power
[Purpose] Configure the maximum output power of the device
[Parameter]
| Parameter | Description |
|---|---|
| power | 60w/30w/15w/30w-at.The unit is: w |
[View]
System configuration view
[Notes]
By default, the maximum output power of a device is the power actually provided by the device. Therefore, the configured maximum output power must be lower than or equal to the total power of PoE power modules.
[Use Cases]
sonic(config)# poe max-power 60wpoe priority {low|high|critical}
Section titled “poe priority {low|high|critical}”[Command]
poe priority {low|high|critical}
[Purpose]
Configure the power priority of a PoE interface
[Parameter]
| Parameter | Description |
|---|---|
| critical | Indicates the highest priority |
| high | Indicates the second highest priority |
| low | Indicates the lowest priority |
[View]
System configuration view
[Notes]
When the output power of a device is insufficient, the device in automatic power management mode provides power for the interfaces of the higher power supply priorities first and cuts off power of the interfaces of the lower power supply priorities. PoE switches provide power to PDs connected to the interfaces in the sequence in which PDs are connected to them. By default, the power supply priority of an interface is low.
[Use Cases]
sonic(config)# interface ethernet 4sonic(config-if-4)# poe priority hightime-range time
Section titled “time-range time”[Command]
time-range name from date_stop to date_start
no time-range
[Purpose]
Configure PoE power-off time range
[Parameter]
| Parameter | Description |
|---|---|
| name | Specifies the name of a time range |
| date_stop | Specify the stop time of a time range, the format is hh:mm YY-MM-DD |
| date_start | Specify the start time of a time range, the format is hh:mm YY-MM-DD |
[View]
System configuration view
[Use Cases]
sonic(config)# time-range test from 12:00 2022-01-01 to 16:00 2023-01-01time-range date
Section titled “time-range date”[Command]
time-range name time_stop to time_start
no time-range
[Purpose]
Configure PoE power-off date range
[Parameter]
| Parameter | Description |
|---|---|
| name | Specifies the name of a time range |
| time_stop | Specify the stop time of a time range, the format is hh:mm |
| time_start | Specify the start time of a time range, the format is hh:mm |
[View]
System configuration view
[Use Cases]
sonic(config)# time-range test 00:00 to 23:59 off-daypoe power-off time-range
Section titled “poe power-off time-range”[Command]
poe power-off time-range name
no poe power-off time-range
[Purpose]
Configure PoE power-off time range effective on an interface
[View]
Interface view
[Use Cases]
sonic(config)# interface ethernet 48sonic(config-if-48)# poe power-off time-range testWarning: This operation may power off some PD. Continue? **\[Y/N]**: ypoe legacy-detect enable
Section titled “poe legacy-detect enable”[Command]
poe legacy-detect enable
poe legacy-detect disable
[Purpose]
Enable device power supply compatibility detection for PD devices.
[View]
interface view
[Usage Scenario]
Enable compatibility detection for PD devices, allowing the device to detect PD devices that do not comply with the 802.3af or 802.3at standards and supply power to these PD devices. If the compatibility check for PD devices is not enabled, the device will not recognize non-standard PD devices and will be unable to supply power to them.
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe legacy-detect disablepoe reinitialize
Section titled “poe reinitialize”[Command]
poe reinitialize
[Purpose]
Initialize POE feature
[View]
System configuration view
[Usage Scenario]
If the device has not been initialized for POE at the factory, this command can be used for manual initialization. After executing this command, a device reboot is not required, but all POE functionalities will be automatically disabled. Once initialization is complete, POE will be enabled again
[Use Cases]
sonic(config)# poe reinitializepoe pd alive-check enable
Section titled “poe pd alive-check enable”[Command]
poe pd alive-check enable
no poe pd alive-check enable
[Purpose]
Enable the PoE PD Alive Check detection function on the interface.
[View]
Interface view
[Usage Scenario]
It detects the status of the peer device by pinging the configured IP address. If the number of consecutive failed detection attempts exceeds the set threshold, it will generate a Warning alarm in the logs and execute the configured action.
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe pd alive-check enablepoe pd alive-check ip
Section titled “poe pd alive-check ip”[Command]
poe pd alive-check ip ip_address
no poe pd alive-check ip
[Purpose]
Configure the IP address for PoE PD Alive Check detection.
[View]
Interface view
[Parameter]
| Parameter | Description |
|---|---|
| ip_address | support IPv4 address and IPv6 address |
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe pd alive-check ip 192.168.0.1poe pd alive-check delay
Section titled “poe pd alive-check delay”[Command]
poe pd alive-check delay time
no poe pd alive-check delay
[Purpose]
Configure the delay time for PoE state restart after a PoE detection abnormality.
[View]
Interface view
[Parameter]
| Parameter | Description |
|---|---|
| time | The detection delay after a PoE restart;Unit: seconds;Range: 5-600 |
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe pd alive-check delay 60poe pd alive-check interval
Section titled “poe pd alive-check interval”[Command]
poe pd alive-check interval time
no poe pd alive-check interval
[Purpose]
Configure the detection interval for PoE PD Alive Check.
[View]
Interface view
[Parameter]
| Parameter | Description |
|---|---|
| time | The detection interval for PoE PD Alive Check,;Unit: seconds; Range: 10-300 |
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe pd alive-check interval 30poe pd alive-check err-threshold
Section titled “poe pd alive-check err-threshold”[Command]
poe pd alive-check err-threshold number
no poe pd alive-check err-threshold
[Purpose]
Configure the threshold for the number of PoE PD Alive Check detection errors.
[View]
Interface view
[Parameter]
| Parameter | Description |
|---|---|
| number | The threshold for the number of PoE PD Alive Check detection errors; Unit: seconds; Range: 1-10. |
[Usage Scenario]
When the number of times the device detects that the IP is unreachable is greater than or equal to the configured error-count threshold, the configured action will be triggered and a Warning alarm log will be generated.
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe pd alive-check err-threshold 10poe pd alive-check action {reboot|alarm}
Section titled “poe pd alive-check action {reboot|alarm}”[Command]
poe pd alive-check action {reboot|alarm}
no poe pd alive-check action
[Purpose]
Configure the action to be taken after a PoE PD Alive Check detection abnormality.
[View]
Interface view
[Parameter]
| Parameter | Description |
|---|---|
| reboot | When an anomaly is triggered, only a Warning alarm log is generated. |
| alarm | When an anomaly is triggered, both a Warning alarm log is generated and the interface’s PoE function is restarted.this action is default. |
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe pd alive-check action rebootpoe pd alive-check reboot-interval
Section titled “poe pd alive-check reboot-interval”[Command]
poe pd alive-check reboot-interval time
no poe pd alive-check reboot-interval
[Purpose]
Configure the interval between the PoE shutdown and the subsequent PoE restart on the interface after a PoE PD Alive Check anomaly is triggered.
[View]
Interface view
[Parameter]
| Parameter | Description |
|---|---|
| time | The interval between the PoE shutdown and restart on the interface after a PoE PD Alive Check anomaly is triggered; Unit: seconds; Range: 1-180. |
[Use Cases]
sonic(config)# interface ethernet 1sonic(config-if-1)# poe pd alive-check reboot-interval 100