"power-over-ethernet allocate-by usage" is by default on in switches but it seems to not giving full power (need to be 30W peak, not 25.5W rms!) to PD.
"...allocate-by class" has same effect: with same orange poe-led blink PTZ dies and start another power sequence.
Is there any deeper way to debug poe problems other than making oscilloscope insertion point to cable and see what's going on there?
------------------------------
Jori Luoto
------------------------------
Original Message:
Sent: May 11, 2021 03:16 AM
From: Yash NN
Subject: poe-allocate-by value missing from CX...
Yes, AOS-CX switches support allocated-by Usage and Class as per standard.
switch(config)# interface 1/1/1
power-over-ethernet allocate-by usage
switch(config-if)# power-over-ethernet allocate-by usage
power-over-ethernet allocate-by class
switch(config-if)# power-over-ethernet allocate-by class
Will get on debug poe steps.
Good day!
------------------------------
Yash NN
Original Message:
Sent: May 07, 2021 07:28 AM
From: Jori Luoto
Subject: poe-allocate-by value missing from CX...
Hi,
I hope this question does not appear as double (it seems like previous mailing has been stucked somewhere)
So I have problem with poe allocation while using bad behaving AV-equipments (like pro level NDI cameras and poe-powered monitor speakers).
ArubaOS had nice workaround in interface level configuration: "poe-allocate-by value" and "poe-value 30". Those two config lines gave switch instruction to reserve and distribute 30W of power to PD's without need from them to ask such power amount...
AOS-CX (v10.07) running on 6100 switch seems to lack such command which can be used to do "maximum at-power allocation" to ports so I'm bit trouble at this moment because cameras are rebooting them selves about always somebody tries to turn camera head (I think it's camera head turning motors which are doing small overload or so..)
I have tried to grab max power information by using "show power-over-ethernet" when turning camera head but max. value has been something like 18.9W which is way less than at-max value of 25.5W.
Today I picked out next few lines from "show logging" where last line is event when camera died and started power cycle:2021-05-07T08:38:15.037819+00:00 6100 poe-hald[2207]: Event|7902|LOG_INFO|AMM|1/1|Powered device power delivery on interface 1/1/1
2021-05-07T08:38:15.032812+00:00 6100 poe-protod[2192]: Event|7901|LOG_INFO|AMM|1/1|Detected powered device on interface 1/1/1. Type:2, Class:4
2021-05-07T08:38:13.987445+00:00 6100 intfd[451]: Event|404|LOG_INFO|AMM|1/1|Link status for interface 1/1/1 is down
2021-05-07T08:38:13.517107+00:00 6100 poe-hald[2207]: Event|7904|LOG_WARN|AMM|1/1|Powered device fault on interface 1/1/1. Fault type Current/Power Cutoff (Icut)
What I had tried already is to disable lldp (rxtx) from port level, disabled lldp from switch level, added "power-over-ethernet pre-std-detect
" etc. but noting has efectively helped to this problem.
How can I debug poe problems more deeply to see whyt this is happening and is there another way to fix this than buy additional poe-injector to do it's work??
------------------------------
Jori Luoto
AV IT specialist
Audico Systems oy
------------------------------