@guyd2 

The last poster has provided a log that clearly indicates the product is at fault. 

I am not sure why you correlate yours to his. If you are facing the same thing, you can contact the support for a replacement. 

Otherwise, your PoE problem is not related to any posts you have linked. 

Controller keeps all the settings.
As long as you don't reset the controller or lose the backup from/on the controller.

The description is more like the thing I stressed before on other similar cases with the PoE problems. It's the cable issue. 

  @Clive_A 

First, thank for your quick answer.

Regarding other post, perhaps he posted logs which I didn't fully read, but it seemed as I said, same mode and same problem.

Since my last post of logging of thousands of problems, I disabled all logs to try and select what log causes this over logging ( and I still don't understand if this is an error).

So, to be sure that it is not same failure as the other poster, please let me know what logs to put in here.

2nd, I rolled back firmware upgrade that was done same day. Less than a day with nothing of that matter.

I would like to know that I don'at have any hardware issue.

Guy

  @guyd2 

guyd2 wrote

  @Clive_A 

 

First, thank for your quick answer.

Regarding other post, perhaps he posted logs which I didn't fully read, but it seemed as I said, same mode and same problem.

 

Since my last post of logging of thousands of problems, I disabled all logs to try and select what log causes this over logging ( and I still don't understand if this is an error).

 

So, to be sure that it is not same failure as the other poster, please let me know what logs to put in here.

2nd, I rolled back firmware upgrade that was done same day. Less than a day with nothing of that matter.

 

I would like to know that I don'at have any hardware issue.

Guy

 

 

That error in that post, was from the CLI. I don't think you face the same issue as his. 

That was a reading from the bootup phase and the system fails because of a fatal error in the hardware.

You have booted the device properly and you did not look for the errors from the CLI or console port. So, you don't read the same stuff as him. I think this hardware issue should be ruled out. 

Unless you tell me that you see the exact error in the bootup phase from the console connection. 

I would tell you this is a problem with your cable. Believe it or not. This is the only thing that matters in the PoE. I know the users from the community get CAT7 or 8, shielded and outdoor-rated cables or whatsoever expensive and high-quality cable, but these don't matter. 

PoE is sensitive to the shielding and length. Other aspects play roles, but they don't count and weigh much compared to the length. 

Common Questions About 802.3 PoE

  @guyd2 

guyd2 wrote

  @Clive_A 

 

Ok- I put aside comparison for other post.

Regarding your guess:

1. All infrastructure cables in my house (newly built) was installed CAT7 cables and keystones. All ports were checked using a ping device that verifies shielding contact to plug.

2. Since ALL POE devices were disconnected at once without turning back on, suddenly, twice a day, after a year of never-happend-this-issue, and there is a I must say, it is not right (on top of UPTIME of each device showing months of constant uptime).

3. After downgrade to previous Switch firmware, it never happened again.

 

 

Guy

 

So you can conclude this down to the firmware upgrade? 

I am seeing nothing regarding the firmware upgrade or version. I don't have any comments or suggestions if you say so. 

If you believe this is a hardware issue, you can contact the support team for RMA. But my diagnosis does not indicate this is a firmware or hardware issue unless more tests are done. 

I don't trust any of the so-called "premium" cables, CAT7, 8, 9, or 10. I would only trust a 3ft CAT5e UTP and test the PoE. The higher the CAT, the less it means for a home setup. High CAT is usually used for the patch panel over short distances. It does not mean it would outperform any CAT5e or CAT6. 

  @Clive_A 

I'm a professional, but this phoenomena happen twice after upgrade- once after re-powering the switch (ALL POE were off), and seconds 6 hours after power off and on. Never happend before and never happened after downgrade.

what do you suggest regarding cables? and on what basis you are sure that all cables are mis-preform?

All passed "Cable test" succesfully (APs are cabled connected). 

All passed post installation tests.

All worked flawless for a year.

If this is not raising any flag for firmware....? it there any additinal data to share ?

Thank's for your assistance.

Guy

  @guyd2 

guyd2 wrote

  @Clive_A 

 

I'm a professional, but this phoenomena happen twice after upgrade- once after re-powering the switch (ALL POE were off), and seconds 6 hours after power off and on. Never happend before and never happened after downgrade.

 

what do you suggest regarding cables? and on what basis you are sure that all cables are mis-preform?

All passed "Cable test" succesfully (APs are cabled connected). 

All passed post installation tests.

All worked flawless for a year.

 

If this is not raising any flag for firmware....? it there any additinal data to share ?

 

Thank's for your assistance.

Guy

Device info is needed if this requires further investigation.

You can take a look at the device info before you send it. The time has to include the period when your PoE experiences a problem.