Zyxel XGS1930 is randomly crashing
Freshman Member
Hi all,
I'm using 10 Zyxel XGS1930 as access switches in our network. The switches are connected per duallink LACP to the core switches. I'm using the newest Firmware V4.7
All switches crash randomly but regularly. There is hardly a week where at least one switch doesn't stop responding. The switches stop forwarding packets and they are also not reachable over their smart management interface. Also ping requests are dropped (on any ports). It is impossible for me to trace for the reason of the crash :-(
All I can do then is powering off/on the switch. Then it works again for some weeks. It is really annoying and is not what I expected of the XGS1930.
Temperature or power problems can be excluded.
Any idea what I can do? I would urgently like to avoid switching to another product.
I appended one of the used configurations. The are almost equal on all switches. Only the vlan id/names and port names differ.
All Replies
-
Hi @Aison
Based on the configuration provided, it appears that your XGS1930 switch is running firmware version V4.70(ABHT.7). We recommend upgrading to the latest firmware version, V4.70(ABHT.9), which includes important fixes and improvements.
To better understand and resolve this issue, could you please provide the following details?
- Issue Timeline: Did this problem start occurring from the initial installation, or did it begin after a firmware upgrade? Have there been any configuration changes in your network setup?
- Frequency of Crashes: How long does the system remain operational after a reboot before it crashes again?
- Technical Support File: Could you collect the tech support file from the affected switch? This file will help us analyze the logs and identify the root cause.
Kay
0 -
Hello Kay
Thanks for your fast answer. I didn't notice the change from V4.70(ABHT.7) to V4.70(ABHT.9). I upgraded now all switches to ABHT.9 and I'm going to monitor the situation.
- It started from the initial installation. The whole installation is new (installed this summer)
- Hard to say. It's not regular. Sometimes it takes just a few days, sometimes it may take weeks.
- I appended the tech support file.
0 -
Hi @Aison
From our analysis, it appears that your switch is not experiencing a crash in the conventional sense. Typically, when a crash occurs, the switch would automatically reboot itself. Instead, the issue you’re facing seems to be related to high CPU usage, which is causing the switch to stop responding.
After reviewing the logs, we observed multiple LLDP notifications on the switch. These notifications are leading to high CPU usage and may be contributing to the problem.
We recommend disabling the following features on all Zyxel switches in your network and monitoring the results:
- LLDP MED topology-change-notification
- LLDP notification
If the issue persists after making these changes, could you please:
- Collect and share the updated tech support files from the affected switches.
- Provide your network topology, including details of how the switches are connected.
This additional information will help us perform a deeper investigation.
Kay
0 -
Hello,
Thx for the answer. I disabled now all LLDP notification on all Zyxel Switches. LLDP MED was not in use anyway. But maybe there are other services like lldpd (from linux servers) sending these kind of notifications?!?
In the meantime, another switch of same model was not responding. I guess it's also related to LLDP message flooding. But on this device, I can't download the tech support files "all", since it results in a timeout on my browser?! I appended the other tech files instead.
0 -
Hi @Aison
Thank you for sharing the information and technical support files.
To assist with further troubleshooting, we would appreciate your help with the following:
- Network Topology:
- Please provide a detailed network topology. A diagram would be especially helpful.
- LLDP Feature:
- If the LLDP feature is not in use, could you disable LLDP on the switches involved?
- Tech Support Files:
- Select a switch experiencing the issue most frequently to collect technical support files.
- Collect the tech support file every three days so we can compare the differences between diagnostic information.
- If the issue occurs within this three-day period, please collect another tech support file immediately after the issue.
- For the tech support file collection process:
- Console Cable:
- If you have a 4-pin console cable, please let us know. Since the device hanging occurs randomly, we may need your help to collect debug logs when the issue arises.
Thank you for your cooperation.
Kay
0 - Network Topology:
-
Hello Kay,
Is it possible to read out the switch by console (bash/linux)? I would like to setup a cron job to read out the logs regularly. I already tried this, but that's not working :-(
sshpass -p mypass ssh admin@my-switch show tech-supportI have 4-pin console cables, but where can I connect it to the switch?
0 -
Hi @Aison
As previously mentioned, could you please confirm whether LLDP is disabled on your devices?
Additionally, the 4-pin console port is located on the side of the chassis.
When the switch is experiencing issues, kindly connect the 4-pin console cable to the switch and collect the debug logs. I’ve sent you guidance on collecting debug logs—please check your Community inbox for details.
Please also note that the
sshpasscommand is currently not supported for collecting TechSupport via SSH.Kay
0
Zyxel Employee
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 152 Nebula Ideas
- 100 Nebula Status and Incidents
- 5.8K Security
- 285 USG FLEX H Series
- 278 Security Ideas
- 1.5K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.5K Consumer Product
- 251 Service & License
- 396 News and Release
- 85 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 86 About Community
- 75 Security Highlight
