1200
C
93: P
E C
HAPTER
O
Troubleshooting PoE
ONFIGURATION
[Sysname-GigabitEthernet1/0/1] poe enable
[Sysname-GigabitEthernet1/0/1] quit
[Sysname] interface GigabitEthernet 1/0/2
[Sysname-GigabitEthernet1/0/2] poe enable
[Sysname-GigabitEthernet1/0/2] quit
[Sysname] interface GigabitEthernet 1/0/11
[Sysname-GigabitEthernet1/0/11] poe enable
[Sysname-GigabitEthernet1/0/11] quit
[Sysname] interface GigabitEthernet 1/0/12
[Sysname-GigabitEthernet1/0/12] poe enable
[Sysname-GigabitEthernet1/0/12] quit
# Set the power priority level of GigabitEthernet 1/0/2 to critical.
<Sysname> system-view
[Sysname] interface GigabitEthernet 1/0/2
[Sysname-GigabitEthernet1/0/2] poe priority critical
[Sysname-GigabitEthernet1/0/2] quit
# Set the maximum power of GigabitEthernet 1/0/11 to 9,000 milliwatts.
[Sysname] interface GigabitEthernet 1/0/11
[Sysname-GigabitEthernet1/0/11] poe max-power 9000
[Sysname-GigabitEthernet1/0/11] quit
After the configuration takes effect, the IP phone and AR device are powered and
can work normally.
Symptom 1: Setting of the priority of a PoE interface to critical fails.
Analysis:
The guaranteed remaining power of the PSE is lower than the maximum power
■
of the PoE interface.
The priority of the PoE interface is already set.
■
Solution:
In the first case, you can solve the problem by reducing the maximum power of
■
the PoE interface when the guaranteed remaining power of the PSE cannot be
modified.
In the second case, you should first remove the priority already configured.
■
Symptom 2: Applying a PoE configuration file to a PoE interface fails.
Analysis:
Some configurations in the PoE configuration file are already configured.
■
Some configurations in the PoE configuration file do not meet the
■
configuration requirements of the PoE interface.
Another PoE configuration file is already applied to the PoE interface.
■
Solution: