2
The device automatically sets the power usage of the device by using CDP power negotiation or by the
IEEE classification and LLPD power negotiation.
If you do not manually configure the cutoff-power value, the device automatically determines it by using CDP
power negotiation or the device IEEE classification and LLDP power negotiation. If CDP or LLDP are not
enabled, the default value of 30 W is applied. However without CDP or LLDP, the device does not allow
devices to consume more than 15.4 W of power because values from 15400 to 30000 mW are only allocated
based on CDP or LLDP requests. If a powered device consumes more than 15.4 W without CDP or LLDP
negotiation, the device might be in violation of the maximum current
Imax
limitation and might experience
an
Icut
fault for drawing more current than the maximum. The port remains in the fault state for a time before
attempting to power on again. If the port continuously draws more than 15.4 W, the cycle repeats.
When a powered device connected to a PoE+ port restarts and sends a CDP or LLDP packet with a power
TLV, the device locks to the power-negotiation protocol of that first packet and does not respond to power
requests from the other protocol. For example, if the device is locked to CDP, it does not provide power to
devices that send LLDP requests. If CDP is disabled after the device has locked on it, the device does not
respond to LLDP power requests and can no longer power on any accessories. In this case, you should restart
the powered device.
If power policing is enabled, the device polices power usage by comparing the real-time power consumption
to the maximum power allocated on the PoE port. If the device uses more than the maximum power allocation
(or
cutoff power
) on the port, the device either turns power off to the port, or the device generates a syslog
message and updates the LEDs (the port LEDs are blinking amber) while still providing power to the device.
•
To configure the device to turn off power to the port and put the port in the error-disabled state, use the
power inline police
interface configuration command.
•
To configure the device to generate a syslog message while still providing power to the device, use the
power inline police action log
command.
If you do not enter the
action log
keywords, the default action is to shut down the port, turn off power to it,
and put the port in the PoE error-disabled state. To configure the PoE port to automatically recover from the
error-disabled state, use the
errdisable detect cause inline-power
global configuration command to enable
error-disabled detection for the PoE cause and the
errdisable recovery cause inline-power interval interval
global configuration command to enable the recovery timer for the PoE error-disabled cause.
If policing is disabled, no action occurs when the powered device consumes more than the maximum
power allocation on the port, which could adversely affect the device.
Caution
You can verify your settings by entering the
show power inline police
privileged EXEC command.
Examples
This example shows how to enable policing of the power consumption and configuring the device to generate
a syslog message on the PoE port on a device:
Device(config)#
interface gigabitethernet1/0/2
Device(config-if)#
power inline police action log
Command Reference, Cisco IOS XE Everest 16.5.1a (Catalyst 3650 Switches)
64
power inline police
Summary of Contents for Catalyst 3650 Series
Page 2: ... 2017 Cisco Systems Inc All rights reserved ...
Page 37: ...P A R T I Campus Fabric Campus Fabric page 13 ...
Page 38: ......
Page 51: ...P A R T II Interface and Hardware Components Interface and Hardware Commands page 27 ...
Page 52: ......
Page 165: ...P A R T III IP IP page 141 ...
Page 166: ......
Page 235: ...P A R T IV IP Multicast Routing IP Multicast Routing page 211 ...
Page 236: ......
Page 303: ...P A R T V IPv6 IPv6 page 279 ...
Page 304: ......
Page 307: ...P A R T VI Layer 2 3 Layer 2 3 page 283 ...
Page 308: ......
Page 399: ...P A R T VII Multiprotocol Label Switching MPLS MPLS page 375 Multicast VPN page 385 ...
Page 400: ......
Page 429: ...P A R T VIII Network Management Flexible NetFlow page 405 Network Management page 479 ...
Page 430: ......
Page 595: ...P A R T IX Programmability Programmability page 571 ...
Page 596: ......
Page 624: ...Command Reference Cisco IOS XE Everest 16 5 1a Catalyst 3650 Switches 598 ping6 ...
Page 625: ...P A R T X QoS Auto QoS page 601 QoS page 641 ...
Page 626: ......
Page 666: ...Command Reference Cisco IOS XE Everest 16 5 1a Catalyst 3650 Switches 640 show auto qos ...
Page 706: ...Command Reference Cisco IOS XE Everest 16 5 1a Catalyst 3650 Switches 680 trust device ...
Page 707: ...P A R T XI Routing Bidirectional Forwarding Detection page 683 ...
Page 708: ......
Page 725: ...P A R T XII Security Security page 701 ...
Page 726: ......
Page 875: ...P A R T XIII Stack Manager and High Availability Stack Manager and High Availability page 851 ...
Page 876: ......
Page 912: ......
Page 1027: ...P A R T XV VLAN VLAN page 1003 ...
Page 1028: ......
Page 1100: ...Command Reference Cisco IOS XE Everest 16 5 1a Catalyst 3650 Switches 1074 vtp primary ...
Page 1102: ...Command Reference Cisco IOS XE Everest 16 5 1a Catalyst 3650 Switches 1076 Notices ...
Page 1108: ...Command Reference Cisco IOS XE Everest 16 5 1a Catalyst 3650 Switches IN 6 Index ...