New and Changed Information
The following table provides an overview of the significant changes up to the current release. The table does not provide an exhaustive list of all changes or of the new features up to this release.
Cisco APIC Release |
Feature |
Description |
---|---|---|
5.1(1) |
Decouple Power over Ethernet from VLANs and EPGs. |
VLAN and EPG configurations are optional in the PoE policy. |
4.2(1) |
Cisco APIC and Power over Ethernet. |
This guide is first released. |
About Power Over Ethernet (PoE)
Power over Ethernet (PoE) provides the ability for the switch infrastructure to supply power over a copper Ethernet cable to an endpoint device. It enables scalable and manageable power delivery and simplifies deployments of devices such IP telephones, wireless access points, security cameras, and so on.
Power Sourcing Equipment (PSE) detects the presence of a Powered Device (PD), negotiates power requirements, and delivers power. PoE works on the same network cable that carries network traffic data. The Nexus 9000 platform switches act as the PSE devices to supply power to any device which may require it.
Power Over Ethernet Port States
Any switch port that has Power over Ethernet (PoE) enabled on it will have one of the following PoE states:
-
On
– PoE is enabled on the port,Supplied Power
is taken from the power supply andDelivered Power
is provided to the powered device (PD). -
Pwr-deny
– PoE is enabled on the port but the power cannot be supplied due to user configuration restriction or insufficient power capacity of the Power Sourcing Equipment (PSE). -
Faulty
– The port has experienced a fault condition. A faulty PoE port state may resolve on its own or it may require user intervention to correct the issue.In case of recoverable errors, the PoE daemon on the switch may be able to recover and reapply power based on configuration, class of the device, and installed power capacity. User intervention, such as changing admin status of the port, changing PoE-related interface configuration, and/or PD insertion and removal (OIR) can bring the port out of error state in case of recoverable errors.
In case of non-recoverable errors, the PoE daemon on the switch will turn off power to the port.
-
Off
– PoE is disabled on the port. The port will function as a typical data port.
Power Over Ethernet Limitations
The Power Over Ethernet (PoE) feature has the following limitations:
-
PoE is supported only on the N9K-C9348GC-FXP, N9K-C9358GY-FXP, and N9K-C93108TC-FX3P switches.
-
PoE is supported in 802.3af and 802.3at modes only.
-
The maximum power output per port is 30W.
Configuring Power Over Ethernet
The Power over Ethernet (PoE) feature is not enabled by default. You must enable PoE by creating a PoE Node policy. Until PoE is configured, the switch ports do not supply power and function as any typical Ethernet ports. If the device at the other end of the link is already powered-up via alternate power source, the port will operate like a typical Ethernet port. If a PoE device is connected to the port, the device will not receive power until PoE is enabled on that switch port. Once PoE is configured, all PoE ports will supply inline power.
You can create a PoE Node Policy in one of three ways:
-
Using the Cisco APIC GUI, as described in Configuring PoE Using the Cisco APIC GUI
-
Using the NX-OS style CLI, as described in Configuring PoE Using the NX-OS-Style CLI
-
Using the REST API, as described in Configuring PoE Using the REST API
Configuring PoE Using the Cisco APIC GUI
You can use the Cisco APIC GUI to configure the Power over Ethernet (PoE) settings.
Procedure
Step 1 |
Log in to your Cisco APIC. |
Step 2 |
Create PoE node policy. |
Step 3 |
Create a PoE interface policy. |
Step 4 |
Configure port policy group with PoE interface policy. |
Step 5 |
Configure leaf interface profile with port policy group. |
Step 6 |
Configure switch policy group with PoE node policy. |
Step 7 |
Configure leaf switch profile with switch policy group. |
Configuring PoE Using the NX-OS-Style CLI
You can use the NX-OS-style CLI to configure the Power over Ethernet (PoE) settings.
![]() Note |
The CLI configuration is different when you enable or disable the PoE feature at the port level for integration with the Cisco Application Centric Infrastructure (ACI) policy framework. No explicit switchport voice-vlan CLI configuration is supported on a per port basis. Instead, you must configure the PoE VLAN and EPG on ports on which you want the configuration for VoIP phones to receive voice-VLAN over LLDP. |
Procedure
Step 1 |
Enter configuration mode. Example:
|
||
Step 2 |
Create a policy group. Example:
|
||
Step 3 |
Configure port-level PoE policy in the policy group. Example:
|
||
Step 4 |
Configure power and EPG settings. Example:
|
||
Step 5 |
Configure the leaf switch interface profile. Example:
|
||
Step 6 |
Configure the policy group for the leaf switch interface profile. Example:
|
||
Step 7 |
Specify ports for the interface group. Example:
|
||
Step 8 |
Apply the policy on your interface group. Example:
|
||
Step 9 |
Configure the leaf switch profile. Example:
|
||
Step 10 |
Configure the leaf switch policy group and specify leaf switch nodes for the group. Example:
|
||
Step 11 |
Apply the interface policy on the leaf switch profile. Example:
|
Configuring PoE Using the REST API
You can use the REST API to configure the Power over Ethernet (PoE) settings.
Procedure
Step 1 |
Create the PoE node policy. Example:
|
Step 2 |
Create the PoE Interface Policy. You must set the adminSt object property to Example:The following example XML code configures the PoE policy with the voice VLAN and EPG:
Example:The following example XML code configures the PoE policy without the voice VLAN and EPG:
|
Step 3 |
Associate the PoE policy. Example:
|
Power Over Ethernet Switch Configuration Information
The following outputs provide sample PoE configuration on the switches..
Current PoE configuration on all ports
ifav9-leaf37# show power inline
Module Available Used Remaining
(Watts) (Watts) (Watts)
------ --------- ------ ---------
1 1250.0 575.2 674.8
Interface Admin Oper Supplied Delivered Device IEEE Max
(Watts) (Watts) Class
--------- ----- ---- -------- --------- ------ ----- ---
Eth1/1 auto on 7.3 6.4 Cisco IP Phone 8945 2 7.0
Eth1/2 auto on 29.7 26.1 IEEE PD 4 27.0
Eth1/3 auto on 19.1 16.8 IEEE PD 4 25.0
Eth1/4 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/5 auto on 34.1 30.0 IEEE PD 4 30.0
Eth1/6 auto on 17.5 15.4 IEEE PD 3 20.0
Eth1/7 auto on 22.7 20.0 IEEE PD 4 20.0
Eth1/8 auto on 17.5 15.4 IEEE PD 3 20.0
Eth1/10 auto on 8.0 7.0 iPECS LIP-9008; 0.0 2 20.0
Eth1/12 auto on 22.7 20.0 IEEE PD 4 20.0
Eth1/13 auto on 4.1 3.6 IEEE PD 1 4.0
Eth1/14 auto on 28.2 24.8 IEEE PD 4 30.0
Eth1/15 auto on 22.7 20.0 IEEE PD 4 20.0
Eth1/16 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/17 auto on 17.5 15.4 IEEE PD 3 20.0
Eth1/18 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/19 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/20 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/21 auto on 17.5 15.4 IEEE PD 3 20.0
Eth1/22 auto on 8.0 7.0 IEEE PD 2 20.0
Eth1/23 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/24 auto on 17.5 15.4 IEEE PD 3 20.0
Eth1/25 auto on 13.6 12.0 Cisco IP Phone 7975 3 20.0
Eth1/26 auto on 34.1 30.0 IEEE PD 4 30.0
Eth1/27 auto on 17.5 15.4 IEEE PD 3 20.0
Eth1/32 auto on 29.7 26.1 IEEE PD 4 28.0
Eth1/34 auto power-deny 0.0 0.0 NA NA 28.0
Eth1/37 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/45 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/46 auto on 10.1 8.9 IEEE PD 4 20.0
Eth1/47 auto on 19.1 16.8 IEEE PD 4 20.0
Eth1/49 auto fault 0.0 0.0 n/a n/a 4.0
Current PoE power consumption on all ports
ifav9-leaf37# show power inline consumption
Interface Consumption Admin
Configured Consumption (Watts)
---------- ----------- -------------------
Eth1/1 Yes 4.0
Eth1/2 Yes 4.0
Eth1/3 Yes 4.0
Eth1/4 Yes 4.0
Eth1/5 Yes 4.0
Eth1/6 Yes 4.0
Eth1/7 Yes 4.0
Eth1/8 Yes 4.0
Eth1/10 Yes 4.0
Eth1/12 Yes 4.0
Eth1/13 Yes 4.0
Eth1/14 Yes 4.0
Eth1/15 Yes 4.0
Eth1/16 Yes 4.0
Eth1/17 Yes 4.0
Eth1/18 Yes 4.0
Eth1/19 Yes 4.0
Eth1/20 Yes 4.0
Eth1/21 Yes 4.0
Eth1/22 Yes 4.0
Eth1/23 Yes 4.0
Eth1/24 Yes 4.0
Eth1/25 Yes 4.0
Eth1/26 Yes 4.0
Eth1/27 Yes 4.0
Eth1/32 Yes 4.0
Eth1/34 Yes 4.0
Eth1/37 Yes 4.0
Eth1/45 Yes 4.0
Eth1/46 Yes 4.0
Eth1/47 Yes 4.0
Eth1/49 Yes 4.0
Current PoE configuration on a single port
ifav9-leaf37# show power inline ethernet 1/1
Interface Admin Oper Supplied Delivered Device IEEE Max
(Watts) (Watts) Class
--------- ----- ---- -------- --------- ------ ----- ---
Eth1/1 auto on 7.3 6.4 Cisco IP Phone 8945 2 7.0
Interface AdminPowerMax AdminConsumption
(Watts) (Watts)
--------- ------------- ----------------
Eth1/1 7.0 7.0
PoE Port policing actions
ifav9-leaf37# show power inline police
Interface Admin Oper Admin Oper Cutoff Oper
State State Police Police Power Power
--------- ----- ----- ------ ------ ------ -----
Eth1/1 auto on none n/a 6.4 5.1
Eth1/2 auto on none n/a 26.1 16.3
Eth1/3 auto on none n/a 16.8 10.5
Eth1/4 auto on none n/a 16.8 7.7
Eth1/5 auto on none n/a 30.0 8.5
Eth1/6 auto on none n/a 15.4 5.4
Eth1/7 auto on none n/a 20.0 9.5
Eth1/8 auto on none n/a 15.4 5.5
Eth1/10 auto on none n/a 7.0 2.1
Eth1/12 auto on none n/a 20.0 13.1
Eth1/13 auto on none n/a 3.6 2.3
Eth1/14 auto on none n/a 24.8 8.4
Eth1/15 auto on none n/a 20.0 8.4
Eth1/16 auto on none n/a 16.8 7.7
Eth1/17 auto on none n/a 15.4 14.5
Eth1/18 auto on none n/a 16.8 10.4
Eth1/19 auto on none n/a 16.8 10.1
Eth1/20 auto on none n/a 16.8 8.3
Eth1/21 auto on none n/a 15.4 11.5
Eth1/22 auto on none n/a 7.0 4.4
Eth1/23 auto on none n/a 16.8 7.3
Eth1/24 auto on none n/a 15.4 11.1
Eth1/25 auto on none n/a 12.0 8.9
Eth1/26 auto on none n/a 30.0 16.8
Eth1/27 auto on none n/a 15.4 5.6
Eth1/32 auto on none n/a 26.1 15.7
Eth1/34 auto power-deny none n/a 0.0 0.0
Eth1/37 auto on none n/a 16.8 10.2
Eth1/45 auto on none n/a 16.8 10.4
Eth1/46 auto on none n/a 8.9 4.7
Eth1/47 auto on none n/a 16.8 7.2
Eth1/49 auto fault none n/a 0.0 0.0
PoE port priority
ifav9-leaf37# show power inline priority
Interface Admin Oper Priority
State State
--------- ----- ----- -----
Eth1/1 auto on low
Eth1/2 auto on high
Eth1/3 auto on low
Eth1/4 auto on low
Eth1/5 auto on low
Eth1/6 auto on low
Eth1/7 auto on low
Eth1/8 auto on low
Eth1/10 auto on low
Eth1/12 auto on low
Eth1/13 auto on low
Eth1/14 auto on low
Eth1/15 auto on low
Eth1/16 auto on low
Eth1/17 auto on low
Eth1/18 auto on low
Eth1/19 auto on low
Eth1/20 auto on low
Eth1/21 auto on low
Eth1/22 auto on low
Eth1/23 auto on low
Eth1/24 auto on low
Eth1/25 auto on low
Eth1/26 auto on low
Eth1/27 auto on low
Eth1/32 auto on low
Eth1/34 auto power-deny low
Eth1/37 auto on low
Eth1/45 auto on low
Eth1/46 auto on low
Eth1/47 auto on low
Eth1/49 auto fault low
PoE configuration event history of a port
ifav9-leaf37# vsh -c "show system internal poe event-history interface ethernet 1/1"
>>>>FSM: <Ethernet1/1> has 4 logged transitions<<<<<
1) FSM:<Ethernet1/1> Transition at 991000 usecs after Tue Oct 16 13:50:22 2018
Previous state: [PORT_ST_POE_SHUT]
Triggered event: [POE_PORT_EV_START_DETECTION]
Next state: [PORT_ST_POE_DETECTING]
2) FSM:<Ethernet1/1> Transition at 712319 usecs after Tue Oct 16 13:50:23 2018
Previous state: [PORT_ST_POE_DETECTING]
Triggered event: [POE_PORT_EV_IEEE_PD_DETECTED]
Next state: [PORT_ST_POE_DETECTED]
3) FSM:<Ethernet1/1> Transition at 927598 usecs after Tue Oct 16 13:50:23 2018
Previous state: [PORT_ST_POE_DETECTED]
Triggered event: [POE_PORT_EV_POWER_GOOD]
Next state: [PORT_ST_POE_POWER_GOOD]
4) FSM:<Ethernet1/1> Transition at 767401 usecs after Tue Oct 16 13:52:13 2018
Previous state: [PORT_ST_POE_POWER_GOOD]
Triggered event: [POE_PORT_EV_POWER_ADJUST]
Next state: [FSM_ST_NO_CHANGE]
Curr state: [PORT_ST_POE_POWER_GOOD]
ifav9-leaf37# vsh -c "show system internal poe info ethernet 1/1"
Interface name : Eth1/1
Interface mode : auto
Interface Priority : low
Interface description : Cisco IP Phone 8945
Policer action : none (policer is off)
Max power : 7.0
Default power : 4.0
PS supplied power : 7.3
PD Base power : 7.0
Port delivered power : 6.4
Port consumption pwr : 5.1
Max drawn power : 5.9
Policer measured pwr : 0.0
PD Class : IEEE 2
PD Discovery mode : IEEE
PD Detection status : Delivering
Num violations : 0
PoE object information of a port
ifav9-leaf37# moquery -c poeIf -d "sys/poe/inst/if-[eth1/1]"
Total Objects shown: 1
# poe.If
id : eth1/1
absentCounter : 0
adminSt : enabled
childAction :
consumption : 4000
cutoffPower : 7955
deliveredPower : 6400
descr :
devClass : IEEE PD - Class 2
devName : Cisco IP Phone 8945
dn : sys/poe/inst/if-[eth1/1]
invalidSignatureCounter : 0
lcOwn : local
max : 7000
modTs : 2018-10-16T13:50:21.421-07:00
mode : auto
monPolDn : uni/infra/moninfra-default
name : node37_1_1
operSt : on
overloadCounter : 0
poeEpg : uni/tn-t0/ap-AP1/epg-EPG37_1_1
poeVoiceVlan : vlan-401
policeAct : none
policeSt : na
policingPower : 7000
portConsumption : 5074
portPriority : 0
powerDeniedCounter : 0
prioHigh : no
rn : if-[eth1/1]
shortCounter : 0
status :
suppliedPower : 7273
used : 7955
ifav9-leaf37# moquery -c poeModule -d "sys/poe/inst/if-[eth1/1]/mac-30:30:3A:30:30:3A-[vlan-401]"
Total Objects shown: 1
# poe.Module
mac : 30:30:3A:30:30:3A
vlan : vlan-401
childAction :
dn : sys/poe/inst/if-[eth1/1]/mac-30:30:3A:30:30:3A-[vlan-401]
epg : uni/tn-t0/ap-AP1/epg-EPG37_1_1
id : eth1/1
modTs : never
rn : mac-30:30:3A:30:30:3A-[vlan-401]
status :
vlanType : access
List of faults on the switch
ifav9-leaf37# faults
Severity : warning
Fault Code : F3342
Cause : feature-poe-config-fail-unrecoverable
Acknowledged : no
Last Transition : 2018-10-16T13:52:47.335-07:00
Dn : sys/poe/inst/if-[eth1/49]/fault-F3342
Severity : warning
Fault Code : F3342
Cause : feature-poe-config-fail-unrecoverable
Acknowledged : no
Last Transition : 2018-10-16T16:23:00.738-07:00
Dn : sys/poe/inst/if-[eth1/34]/fault-F3342
Severity : warning
Fault Code : F3341
Cause : feature-poe-config-fail-recoverable
Acknowledged : no
Last Transition : 2018-10-16T16:23:00.733-07:00
Dn : sys/poe/inst/if-[eth1/34]/fault-F3341
Total : 3