xs1930-12hp becomes inaccessible after a few days uptime

rfs666
rfs666 Posts: 3
First Comment

Local managed switch (Nebula disabled). No special features enabled. One subnet/port configured. Web-interface via direct connected computer.

After a few days, the switche's IP address is no longer ping able and also the login page does not load.

Tried to access from different switch ports - same result.

Firmware 4.80(ABQF.3)C0 on primary. Older firmware which came from factory on backup.

Needs power cycle to be come accessible again.

What could be the issue?


All Replies

  • Zyxel_Kay
    Zyxel_Kay Posts: 552  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer

    Hi @rfs666

    To better assist you, could you kindly provide the following details?

    1. Could you please specify the devices connected to the switch?
    2. Based on your description, it seems you're unable to access the switch interface. Can you confirm if the traffic is being forwarded as usual during this time?
    3. What was the status of the switch LEDs when the issue occurred? Specifically, could you describe the status of the Port LEDs?
    4. How frequently does this issue occur?

    Kay

  • rfs666
    rfs666 Posts: 3
    First Comment

    Hello Kay, thanks for looking into it.

    1. Windows computers + server + uplink to other switch (having various IOT clients connected)
    2. The traffic is still forwarded, however one client did not get its IP renewed, after the client's lease was expired
    3. Nothing unusual about the LEDs. Looked like normal operation with normal blinking on the connected ports.
    4. looks like 4 days period:

    24 2022-01-01T00:00:23Z AL system: System has reset without management command
    25 2024-03-18T14:53:08+01:00 DE interface: Port 5 - Leviathan link up 100M/F
    113 2024-03-14T21:49:46+01:00 NO system: Gets the time and date from a time server successfully
    114 2022-01-01T00:00:35+01:00 DE interface: Port 10 - WAN link up 1G/F

    After last reboot today, I disabled IPv6 (was DHCP). After the first lock up, I did put static port address on IPv4 (was also DHCP before, but seems this was not the reason).

  • Zyxel_Kay
    Zyxel_Kay Posts: 552  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer
    edited March 21

    Hi @rfs666

    Thank you for providing additional details.

    Based on the information shared, it seems there might be a DHCP-related issue. To further troubleshoot this, we kindly ask for your cooperation in the following steps:

    1. Could you please utilize the ZON utility to scan your network? If the switch obtains an IP address, it's possible there's an IP conflict within your network. Please provide the results of the scan.
    2. If the switch doesn't acquire an IP address, it suggests a potential DHCP server issue. Could you please check the lease time and pool size settings of your DHCP server?
    3. Additionally, you may consider setting a Static IP for the switch XS1930-12HP using the ZON utility to see if the issue persists.

    For more guidance on using the ZON utility, you can refer to this article:

    Kay

  • cbeckstein
    cbeckstein Posts: 17  Freshman Member
    10 Comments

    Just an idea:

    Did you experiment with the "Auto Power Down" settings for the ports of the switch?

    I mean, does the problem persist if you disable "Auto Power Down" for all its ports?

  • rfs666
    rfs666 Posts: 3
    First Comment

    OK, the switch is now up for 7 days since last reboot, seems problem solved. Although it had already a fixed IPv4 address, seems the DHCP client for IPv6 was causing the issue. After removing all IPv6 settings from the configuration, it's stable now.