can't set the parameter AdminPowerMax higher that 7000 mW.

Unanswered Question
Jan 16th, 2008

can't set the parameter AdminPowerMax higher that 7000 mW.

Look at systemdump:

SGDFPSAcc2#sh power inline fastEthernet 4/13

Available:1400(w) Used:315(w) Remaining:1085(w)

Interface Admin Oper Power(Watts) Device Class

From PS To Device

--------- ------ ---------- ---------- ---------- ------------------- -----

Fa4/13 static off 7.0 7.0 n/a n/a

Interface AdminPowerMax AdminConsumption

(Watts) (Watts)

---------- --------------- --------------------

Fa4/13 7.0 7.0

SGDFPSAcc2#conf t

Enter configuration commands, one per line. End with CNTL/Z.

SGDFPSAcc2(config)#fast

SGDFPSAcc2(config)#in

SGDFPSAcc2(config)#interface fas

SGDFPSAcc2(config)#interface fastEthernet 4/13

SGDFPSAcc2(config-if)#pow

SGDFPSAcc2(config-if)#power in

SGDFPSAcc2(config-if)#power inline ?

auto Automatically detect and power inline devices

consumption Configure the inline device consumption

never Never apply inline power

static High priority inline power interface

SGDFPSAcc2(config-if)#power inline au

SGDFPSAcc2(config-if)#power inline auto m

SGDFPSAcc2(config-if)#power inline auto max ?

<4000-7000> milli-watts

The parameter :

SGDFPSAcc2#sh power inline consumption default

Default PD consumption : 15400 mW

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
aghaznavi Tue, 01/22/2008 - 12:54

If you set a small value for the power allocation, all connected inline power devices initially are powered up, but after you receive the CDP messages, the system learns that devices consume more power and deny power to some of the ports. If you set a small value, it can also result in the overdraw of power for some time with unanticipated results, such as hardware failures and unexpected resets. 7000 milliwatts (mW) is the maximum power supported for these modules.

Actions

This Discussion