Strange log message. Is this an error?

Hi @Zyxel_Judy

Now… I have two different PoE log errors logged in this thread. 

First log error:
“Port Detection Status is Searching”
“Port Detection Status is Delivering Power”

Result of first log error:
The two actual ports did not flap down and up again
Attached units did not reboot
Attached units did not drop traffic

Second log error 30 days later:
“PoE power usage exceeds 95% threshold, remaining power is 0.0W”
“PoE power usage is less than 95% threshold, remaining power is 324.6W”
(ONE second between these messages)

Result of second log error:
No PoE powered devices got problems or was powered down
Attached unit did not reboot
Attached unit did not drop traffic

This second PoE error has been seen before in march by two other persons. You offered a RMA for that person at that time, but he rejected it with the argument “Given that you couldn't replicate the problem and therefore have no fix, a replacement may suffer from the same issue.” (I did chat with one of the two that have seen this log with high PoE usage in the forum chat). To note is that he has not seen this message again.

As it is simply impossible during these circumstances that the power draw would go from my std approx 49W to momentarily over 95% of the switch max 375W which would be an increase of more than 7 times normal power usage, it must be either a hardware issue or a software bug. But… As no problem at all was seen with power or actual traffic on the switch ports, well, that could lead to not suspect hardware, but software/firmware!

As this switch model has been around for a while and this log message has be up in the forum before with at least two different persons except me, I do wonder why you do not go through the firmware code and look at what in the code that actually triggers this log message. Just to offer an RMA when you have no clue if the same log message will/can appear again in the new replaced hardware, well, that bothers me… Just a response with “we are unable to replicate that problem” and offer an RMA, that bothers me. 

I do very much appreciate that you took the time to look into the switch, but I am not satisfied with that you take it so easily.

I will in this case not go on with an RMA as I have not had any real issues except the log messages that you cannot explain. But if I will see any more of this log messages I will probably try to move away from this switch and replace it with something else. I.e send it back to where I bought it. It is simply too much for me with two different PoE log errors directly after moving to this Zyxel switch that you cannot explain and take so easily.

B t w… My switch has Hardware Version: V1.19. Do you have any newer hardware revision?

Do you have any on-site fix/replace if paying for it?
How long will the RMA take?
How will my existing CLI license be added to the new device?
Is it possible to have another switch in advance? I can pay for en extra switch and get a refund when you receive the RMA unit.

PS
I asked above…." I do wonder why you do not go through the firmware code and look at what in the code that actually triggers this log message.". Again… what in the firmware code will cause these log messages? Line voltage fluctuation? Is it possible for you to reveal what and how the triggers in firmware causes these log messages?
* “Port Detection Status is Searching”
* “Port Detection Status is Delivering Power”
* “PoE power usage exceeds 95% threshold, remaining power is 0.0W”

Hi @Zyxel_Judy

I now have logged an RMA according to your recommendation. While waiting I have seen the

“Port Detection Status is Searching”
"Port Detection Status is Delivering Power"

again on port 6 and 7. And as before, the ports did NOT loose power. Still worked as it should with power and data. So I am actually not in a real hurry with the RMA as "these are just log messages"…

On port 6 - Cisco SLM2008 switch
Supports the IEEE 802.3af Power-over-Ethernet (PoE) PD

On port 7 - Axis M3026-VE camera
Power Power over Ethernet IEEE 802.3af/802.3at Type 1 Class 2
max 4.5 W, typical 3.4 W

Now… My devices on port 6-7 are older devices (An Axis camera and a PoE powered 8-port Cisco switch), but had no PoE problems whatsoever with the old switch. And I have actually not had any problems with this Zyxel switch either... Only the log messages mentioned above that *may* / *could* be false messages. The PoE powered port 1-4 have top notch Aruba 505 and 535 AP:s and have not had this log message.

This Zyxel has more advanced PoE settings than the old switch. Could it be the case that there is something triggered within PoE negotiation ( I do not know the PoE std though). The strange thing though is that it happens within the same second on both ports, which could probably tell it is not a PoE negotiation thing or end device issue. But even so, I have now set "force-802.1at" on port 7 but not on port 6. So I will see if it happens again on both ports or just one of them as they now have different PoE config settings. But I doubt… as the ports log this almost synchronously.

Regarding the logs:
“PoE power usage exceeds 95% threshold, remaining power is 0.0W”
“PoE power usage is less than 95% threshold, remaining power is 324.6W”

that have happened ONCE within the switch 40 day uptime and restored within the same second… And as before with the other messages, the ports did NOT loose power. Still worked as it should with power and data.

It must be a hardware or firmware issue. It is simply not possible for the six connected devices to draw this amount of power. Even if a short circuit should occur on o port it still has a max power draw on that port… Max worst case power for all six devices according to its devices specs are 5+4.5+13.5+4x26.4=128.6W. But According to the switch it mostly draw 45-48W in total during std usage.

My background in the business tells me it is a rather high probability that a new switch eventually could suffer the same issues. But that we will see when the switch is replaced…. And whatever happens after the replacement, it will add extra pieces to this investigation.

Hi

I think that would ve very clear already as I uploaded info about my purchase (with purchase date on from nov 2024 it) when I did the RMA. Despite that, this is what I got. So with this in mind, what do think I should do?

And.. Now I am sitting here with my old original unit from nov 2024 plus the heavily used one I got on the RMA. So whatever happens, I have to send the one I just got directly in return with the packaging slip I got with it. So starting a new RMA again when the first one haasn't got in return could be messy. So I would need someone at Zyxel to handle it all. Not different persons… To add to that is my CLI license that has been moved to the unit that just arrived that I will send in return. This will cause me a lot of head ace.