Lack of logs for switches errors

GiuseppeR

Hello everyone,

I went online on Nebula and I saw this error:

For this reason I visited the specific page Nebula suggested me to look at:

I saw no details to understand the reason why the switch went on error.

So I changed from "Range" mode to "Before" mode for logs details:

Anyway no logs.

So how could I try troubleshooting in this scenario?

Zyxel_Judy

Hi @GiuseppeR ,

In this case, it is correct that there are no relevant logs in the Change log, as it only shows configuration changes made manually.

Zyxel_Judy

Hi @GiuseppeR ,

To better support you, please enable Zyxel support.

Additionally, please provide us with the name of your Nebula organization/site here or via the private message by clinking to my account > Message.

GiuseppeR

Hello @Zyxel_Judy

PM sent with details and with screenshots.

See you soon, have a nice day 😎

Zyxel_Judy

Hi @GiuseppeR ,

After reviewing your site, this is a known issue where connectivity changes (offline events) may lead to a problem when triggering the auto-configuration recovery feature, causing the device to lock. We plan to resolve this feature in the near future. Please follow our Switch News & Release to know about the fixes, enhancements and new feature:

News and Release - Zyxel Community

For a workaround solution now, please deactivate the auto-configuration recovery feature.

GiuseppeR

Hello @Zyxel_Judy

I read it. So the lack of logs is correct, because there are no relevant logs to show but just a problem in the firmware?

Zyxel_Judy

Hi @GiuseppeR ,

In this case, it is correct that there are no relevant logs in the Change log, as it only shows configuration changes made manually.