Anybody Had A Problem With Cisco 2960x For Poe+ Enabled IP PTZ Cameras ?

Does anyone have or had a problem powering PoE+ enabled IP PTZ cameras with Cisco 2960x ?

Some of my customers have issue powering the PTZ camera. Booting up works well but after a few minutes the connection to camera web page doesn't work. So I've checked the power drawn at the switch and found it's 15.4Watt.

But I guess the power should be flexible depending on the requirement of the camera. When the camera pan, tilt or zoom it needs more power, which will request for more watt from the switch.

But in order to resolve this issue do I have to hardcode the power per port ? The PoE power per port and overall is enough by the switch spec.

Thank you!

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

*'* ********* ** *** ****** ** ***-********* *** *** ***** of *** ******? **** * ***** ** ** *** * midspan ** **** *** *** *** *****. *** ** * midspan ***** *** ***** ** ***. **** ******* ***** *** Axis *** *** ** ***** ** * ***.

*** ******* *** *** *** ****** ****.

****** * ***!

*'* ******** ***** ** **** ***** **** *** **** **** to ******* **** *****? ** **** *******?

* *** ******* * **** *** **** *******.

***, *****! *** **** ** ****** *** ********** ** ******* the *****.

**** *****'* *** ***'* ******* **** ** ******* ** ******** negotiate ***** ****.

*** (*** ***) ** * *** ***** **** ***.* ********. It ******* ****** ******* ******* ** ***********. * ***** **** contributes ** ***** ***********.

(*** * ****** ******* ** * ***** ***** ** ******* that **** ** * *** ******, *** **** ******** ** this * ***** ****.)

**** ** ****** **** *** **** ******* *****.

**** ******* *** ***** ***********

*** **** ****** *** **** *** ** ******* ******* ***+ to ******* ********** ***** *** *********. ***.*** *** ***** ** insufficient *** ****** *********. ** ****** ********** ***** **** ***+, the ****** ********* *** ***** **** **** **** ***** ********* Protocol (****) *** ****-*** ***** ********** ******** ****** **.

**** ** *** ******* *******. **** ** **'* ******** *** the ****** **** ** *** ******* *******. ***'* ****** **'* a ***** *****. ** *** ***** ****** ****** **'* ***** logging ** ******* ******** ***** (** *** ******* *******) ** see ** **'* ******** ****** ***** ********. * ****** **** the "*** * *******" ********** ** ********* *** ** ** issue.

*'** ******* ***** *** **** *** ***** *** *** ********** between *** *** ****. ** * *** **** ** ******* the ***+ ***** ***** *** *** *** ******. ** ***** that *** ****** **** ***** **** ** ***** ****** ****** me.

******, ***** *** *** **** ******.

***,

*'* ***** ************ **** ***** ** * ***** ******.

* ******** *** ** ****** ****** ** ***** *** *********

** *** ***

**** * ******* **** ** ******* *** *********

**** ***

* **** **** **** *** ********* *** ***** *** *********

**** *******

**** ********

*** *** ****** ***** ****** ** *** **** ***** **** down ***** ****** ** *******.

******** *** *** **** * ***** ** *******?

****** *** **** ****!