POE Configuration
27 min
\<font color="#1d50a2">show interface poe\</font> \[command] show interface poe \[purpose] display interface poe information \[view] system view \[use cases] sonic# show interface poe \<font color="#1d50a2">show interface poe diagnose\</font> \[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 diagnose pse device information field value \ version 0x4a02 status ok expected poe device found (zone1) event temperature 48 c temperature alarm 110 c reset count 0 initialized true pse wrong port map interface current id expect id \ \<font color="#1d50a2">show interface poe pd alive check status\</font> \[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 | + + + + + + + + \<font color="#1d50a2">show interface poe status comment\</font> \[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 comment status code comment \ 0x3d port power up was denied due to (pd class report power > user predefined power value) note power denied counter will advance 0x3c calculated power > power limit 0x22 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/mode 0x20 power management function shuts down port due to lack of power port is shut down or remains off 0x26 port fails due to system voltage supply through other port check other port for status 0x24 this error is linked with mask 0x1f enable 0x24 port fails due to voltage being applied to the port from external source 0x25 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 activated 0x34 short condition was detected for example, cable crystal head may have short circuit 0x37 the device returns an unknown port status for the software currently not used 0x36 the die temperature is above safe operating value 0x1c non standard pd connected 0x1b interim state during line detection status changes after detection process is completed 0x41 port was not turned on due to hardware power limit (pd class power > hardware class limit) for example, poh pd over m device port 0x43 illegal class 0x45 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 crashed 0x46 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 crashed 0x47 port is at force power error, according to the ieee test mode error the port was forced power and host crash occurred 0x48 during crash, a recovery port delivering power was disconnected due to udl 0x49 during crash, a recovery port delivering power was disconnected due to pg event 0x08 hardware pin disables all ports 0x06 mains voltage is higher than the maximum voltage limit 0x07 mains voltage is lower than the minimum voltage limit 0x84 non ieee pd was detected using 4p matrix in bt mode and power as 4 pair 0x85 802 3bt sspd was detected using 4p matrix and operate as 2p, if requested class <= 4 0x86 802 3bt sspd was detected using 4p matrix and operate as 4p, if requested class > 4 0x87 802 3bt dspd was detected using 4p matrix and operate as 2p due to 4 pair candidate validation in two cycles 0x80 non ieee pd was detected using 2p matrix in the bt mode 0x81 802 3bt compliant pd was detected using 2p matrix 0x82 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 pair 0x1f 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 2p 0x89 802 3bt dspd was detected using 4p matrix and operate as 4p 0x1a user command set port to off 0x4a during crash, a recovery port delivering power was disconnected due to ovl 0x4b during crash, a recovery port delivering power was disconnected due to sc 0xa8 port is not connected 0x12 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 port 0x91 port matrix 4p and delivers power on both pair sets due to the force power command 0x90 port matrix 2p and delivers power due to the force power command 0xa7 this error is reported only in 4 pair port when invalid connection check signature was detected in such a case, detection fail counter is incremented 0xa0 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 used \<font color="#1d50a2">poe enable\</font> \[command] poe enable no poe enable \[purpose] enable poe power supply function of the interface \[view] interface view \[use cases] sonic(config)# interface ethernet 1 sonic(config if 1)# poe enable \<font color="#1d50a2">poe delay\</font> \[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 1 sonic(config if 1)# poe delay 300 \<font color="#1d50a2">poe max power\</font> \[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 60w \<font color="#1d50a2">poe priority {low|high|critical}\</font> \[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 4 sonic(config if 4)# poe priority high \<font color="#1d50a2">time range time\</font> \[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 01 \<font color="#1d50a2">time range date\</font> \[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 day \<font color="#1d50a2">poe power off time range\</font> \[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 48 sonic(config if 48)# poe power off time range test warning this operation may power off some pd continue? \\\[y/n] y \<font color="#1d50a2">poe legacy detect enable\</font> \[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 1 sonic(config if 1)# poe legacy detect disable \<font color="#1d50a2">poe reinitialize\</font> \[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 reinitialize \<font color="#1d50a2">poe pd alive check enable\</font> \[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 1 sonic(config if 1)# poe pd alive check enable \<font color="#1d50a2">poe pd alive check ip\</font> \[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 1 sonic(config if 1)# poe pd alive check ip 192 168 0 1 \<font color="#1d50a2">poe pd alive check delay\</font> \[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 1 sonic(config if 1)# poe pd alive check delay 60 \<font color="#1d50a2">poe pd alive check interval\</font> \[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 1 sonic(config if 1)# poe pd alive check interval 30 \<font color="#1d50a2">poe pd alive check err threshold\</font> \[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 1 sonic(config if 1)# poe pd alive check err threshold 10 \<font color="#1d50a2">poe pd alive check action {reboot|alarm}\</font> \[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 1 sonic(config if 1)# poe pd alive check action reboot \<font color="#1d50a2">poe pd alive check reboot interval\</font> \[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 1 sonic(config if 1)# poe pd alive check reboot interval 100
