- Release 15.5SY Supervisor Engine 6T Software Configuration Guide
- Preface
- Product Overview
- Command-Line Interfaces
- Smart Port Macros
- Virtual Switching Systems (VSS)
- Enhanced Fast Software Upgrade (eFSU)
- Fast Software Upgrades
- Stateful Switchover (SSO)
- Non-Stop Forwarding (NSF)
- RPR Supervisor Engine Redundancy
- Interface Configuration
- UniDirectional Link Detection (UDLD)
- Instant Access
- EnergyWise
- Power Management
- Environmental Monitoring
- Online Diagnostics
- Onboard Failure Logging (OBFL)
- Switch Fabric Functionality
- Cisco IP Phone Support
- Power over Ethernet
- Layer 2 LAN Port Configuration
- Flex Links
- EtherChannels
- IEEE 802.1ak MVRP and MRP
- VLAN Trunking Protocol (VTP)
- VLANs
- Private VLANs (PVLANs)
- Private Hosts
- IEEE 802.1Q Tunneling
- Layer 2 Protocol Tunneling
- Spanning Tree Protocols (STP, MST)
- Optional STP Features
- IP Unicast Layer 3 Switching
- Policy Based Routing (PBR)
- Layer 3 Interface Configuration
- Unidirectional Ethernet (UDE) and unidirectional link routing (UDLR)
- Multiprotocol Label Switching (MPLS)
- MPLS VPN Support
- Ethernet over MPLS (EoMPLS)
- Virtual Private LAN Services (VPLS)
- L2VPN Advanced VPLS (A-VPLS)
- Ethernet Virtual Connections (EVC)
- Layer 2 over Multipoint GRE (L2omGRE)
- Campus Fabric
- IPv4 Multicast Layer 3 Features
- IPv4 Multicast IGMP Snooping
- IPv4 PIM Snooping
- IPv4 Multicast VLAN Registration (MVR)
- IPv4 IGMP Filtering
- IPv4 Router Guard
- IPv4 Multicast VPN Support
- IPv6 Multicast Layer 3 Features
- IPv6 MLD Snooping
- NetFlow Hardware Support
- System Event Archive (SEA)
- Backplane Platform Monitoring
- Local SPAN, RSPAN, and ERSPAN
- SNMP IfIndex Persistence
- Top-N Reports
- Layer 2 Traceroute Utility
- Mini Protocol Analyzer
- PFC QoS Guidelines and Restrictions
- PFC QoS Overview
- PFC QoS Classification, Marking, and Policing
- PFC QoS Policy Based Queueing
- PFC QoS Global and Interface Options
- AutoQoS
- MPLS QoS
- PFC QoS Statistics Data Export
- Cisco IOS ACL Support
- Cisco TrustSec (CTS)
- AutoSecure
- MAC Address-Based Traffic Blocking
- Port ACLs (PACLs)
- VLAN ACLs (VACLs)
- Policy-Based Forwarding (PBF)
- Denial of Service (DoS) Protection
- Control Plane Policing (CoPP)
- Dynamic Host Configuration Protocol (DHCP) Snooping
- Configuring IGMP Proxy
- IP Source Guard
- Dynamic ARP Inspection (DAI)
- Traffic Storm Control
- Unknown Unicast and Multicast Flood Control
- IEEE 802.1X Port-Based Authentication
- Configuring Web-Based Authentication
- Port Security
- Lawful Intercept
- Online Diagnostic Tests
Power over Ethernet (PoE) Support
Note ● For information about switching modules that support PoE, see the Release Notes for Cisco IOS Release 15.2SY publication at this URL:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.1SY/release_notes.html
- For complete syntax and usage information for the commands used in this chapter, see these publications:
http://www.cisco.com/en/US/products/ps11846/prod_command_reference_list.html
http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Participate in the Technical Documentation Ideas forum
Prerequisites for PoE
Restrictions for PoE
Information About PoE
- Device Roles
- PoE Overview
- CPD-Based PoE Management
- Inline Power IEEE Power Classification Override
- LLDP Inline Power Negotiation for PoE+ (IEEE 802.3at)
Device Roles
- Power sourcing equipment (PSE)—A device that provides power through a twisted-pair Ethernet connection. The switch, through switching modules equipped with Power over Ethernet (PoE) daughtercards, functions in the PSE role.
- Powered device (PD)—A device powered by a PSE (for example, IP phones, IP cameras, and wireless access points).
Note Not all PoE-capable devices are powered from the switch. There are two sources of local power for PoE-capable devices:
- A power supply connected to the device.
- A power supply through a patch panel over the Ethernet connection to the device.
When a locally powered PoE-capable device is present on a switching module port, the switching module itself cannot detect its presence. If the device supports CDP, the supervisor engine can discover a locally powered PoE-capable device through CDP messaging with the device. If a locally powered PoE-capable device loses local power, the switching module can discover and supply power to the IP phone if the inline power mode is set to auto.
PoE Overview
Cisco PoE daughtercards support one or more PoE implementation:
– Supported only with the PoE daughtercard on the WS-X6148E-GE-45AT switching module.
– These features are supported for IEEE 802.3at-compliant class 4 PDs:
• Class 4: 30.00 W at the PSE (12.95 W to 25.50 W at the PD).
• Optionally, LLDP Inline Power Negotiation for PoE+.
– With releases earlier than Release 15.1(1)SY, maximum 16.8 W at the PSE (ePoE for 45 ports maximum).
– Supported with the WS-F6K-48-AF PoE daughtercard and the PoE daughtercard on the WS-X6148E-GE-45AT switching module.
– The IEEE 802.3af PoE standard defines a method to sense a PD and to immediately classify the power requirement of the PD into these per port power ranges at the PSE:
• Class 0: Up to 15.4 W (0.44–12.95 W at the PD; default classification)
• Class 1: Up to 4 W (0.44–3.84 W at the PD)
• Class 2: Up to 7 W (3.84–6.49 W at the PD)
• Class 3: Up to 15.4 W (6.49–12.95 W at the PD)
With a PoE daughtercard installed, a switching module can automatically detect and provision a PoE-capable device that adheres to a PoE implementation supported by the PoE daughtercard. The switching module can supply power to devices supporting other PoE implementations only through manual configuration.
Only a PD connected directly to the switch port can be powered from the switch. If a second PD is daisy-chained from the PD that is connected to the switch port, the second PD cannot be powered by the switch.
Each PD requires power to be allocated from the chassis power budget. Because each PD can have unique power requirements, more devices can be supported if the system’s power management software can intelligently allocate the necessary power on a per-port basis.
You can configure ports to allocate power at a level based on the following:
CPD-Based PoE Management
When a switching module port detects an unpowered PD, the default-allocated power is provided to the port. When the correct amount of power is determined through CDP messaging with the PD, the supervisor engine reduces or increases the allocated power, up to the hardware limit of the installed PoE daughtercard.
Inline Power IEEE Power Classification Override
The IEEE 802.3af standard contains no provision for adjustment of the power allocation. 802.3af-compliant PDs that support CDP can use CDP to override the IEEE 802.3af power classification.
The WS-F6K-48-AF PoE daughtercard or the PoE daughtercard on the WS-X6148E-GE-45AT switching module support these inline power IEEE 802.3af power classification override features:
- Power use measurement—The ability to accurately measure the power provided by the port to the powered device.
- Power policing—The ability to monitor power usage on a port.
With power measurement and policing, you can safely override the IEEE 802.3af power classification of a device that requires a power level at the lower end of its IEEE power classification range.
PoE monitoring and policing compares the power consumption on ports with the administrative maximum value (either a configured maximum value or the port’s default value). If the power consumption on a monitored port exceeds the administrative maximum value, the following actions occur:
LLDP Inline Power Negotiation for PoE+ (IEEE 802.3at)
The PoE daughtercard on the WS-X6148E-GE-45AT switching module supports IEEE 802.3at -compliant LLDP PoE power negotiation, which supports additional negotiation that can reduce power usage.
- The LLDP TLV used is DTE Power-via-MDI TLV.
- When a PD that performs power negotiation using multiple protocols (CDP and LLDP 802.3at) is connected to a switch, the switch locks to the first protocol packet (CDP or LLDP) that contains the power negotiation TLV. If you need to use any single protocol for power negotiation each time, you must administratively disable the other power negotiation protocols on the switch interface.
- See this publication for other the Link Layer Discovery Protocol (LLDP) configuration procedures:
http://www.cisco.com/en/US/docs/ios/cether/configuration/guide/ce_lldp-med.html
How to Configure PoE Support
- Displaying PoE Status
- Configuring Per-Port PoE Support
- Configuring PoE Power Priority
- Configuring PoE Monitoring and Policing
- Disabling LLDP Power Negotiation (IEEE 802.3at)
Displaying PoE Status
This example shows how to display the PoE status on switch:
Configuring Per-Port PoE Support
To configure per-port PoE support, perform this task:
When configuring inline power support with the power inline command, note the following information:
- To configure auto-detection of a PD and PoE auto-allocation, enter the auto keyword.
- To configure auto-detection of a PD but reserve a fixed PoE allocation, enter the static keyword.
- To specify the maximum power to allocate to a port, enter either the auto or static keyword followed by the max keyword and the power level in milliwatts.
- When the auto keyword is entered and CDP is enabled on the port, a PD that supports CDP can negotiate a different power level.
- To disable auto-detection of a PD, enter the never keyword.
- With a WS-F6K-GE48-AF, WS-F6K-48-AF, or the PoE daughtercard on the WS-X6148E-GE-45AT switching module:
– The configurable range of maximum power using the max keyword is 4000 to 16800 milliwatts. If no maximum power level is configured, the default maximum power is 15400 milliwatts.
Note To support a large number of inline-powered ports using power levels above 15400 milliwatts on an inline power card, we recommend using the static keyword so that the power budget is deterministic.
– When the auto keyword is entered and CDP is enabled on the port, an inline-powered device that supports CDP can negotiate a power level up to 16800 milliwatts unless a lower maximum power level is configured.
This example shows how to disable inline power on GigabitEthernet port 2/10:
This example shows how to enable inline power on GigabitEthernet port 2/10:
This example shows how to verify the inline power configuration on GigabitEthernet port 2/10:
Configuring PoE Power Priority
You can configure how the switch responds if a power shortage occurs by setting the priority of ports providing PoE. The priority determines the order in which PoE is removed from ports if a power shortage occurs: low-priority, then high-priority, with power maintained for critical-priority ports as long as possible. These sections describe how to configure PoE power priority:
Setting the PoE Power Priority Global Enable State
To disable PoE power priority globally, perform this task:
|
|
|
---|---|---|
This example shows how to disable PoE power priority globally:
The column heading of any show power inline command displays the PoE power priority global state (“disabled” in this example):
Configuring PoE Port Power Priority
To configure PoE port power priority, perform this task:
This example shows how to configure the PoE port power priority of GigabitEthernet port 2/10 as high:
This example shows how to verify the PoE port power priority configuration of GigabitEthernet port 2/10:
Configuring PoE Monitoring and Policing
With the WS-F6K-48-AF PoE daughtercard or the PoE daughtercard on the WS-X6148E-GE-45AT switching module, to configure PoE monitoring and policing, perform this task:
|
|
|
---|---|---|
Router# show power inline { type slot/port | module slot }[ detail ] |
This example shows how to enable monitoring and policing on GigabitEthernet port 1/9:
These examples shows how to verify the power monitoring and policing configuration on GigabitEthernet port 2/10:
Disabling LLDP Power Negotiation (IEEE 802.3at)
With the WS-X6148E-GE-45AT switching module, LLDP power negotiation is enabled by default. To disable LLDP power negotiation, perform this task:
|
|
---|---|
|
This example shows how to display the LLDP power negotiation configuration on interface GigabitEthernet 3/1 when LLDP power negotiation is enabled:
This example shows how to disable LLDP power negotiation on interface GigabitEthernet 2/10:
http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Participate in the Technical Documentation Ideas forum