NTP server change causes switch disconnection issue
NTP server change causes switch disconnection issue
After changing the NTP server in the controller, all of the network SG2008 switches are now displaying DISCONNECTED in the Devices list. In the site's topology map they are also showing as being not connected. This can't be true as all network clients are working OK.
In my network there are 2 core switches with 2 switches downstream from one of the core switches. Oddly, the EAPs connected to the downstream switches are still showing as CONNECTED and everything is working as expected.
I'm not sure how to fix this issue without downing the network completely and rebooting everything. Suggestions ??
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @PHTP
What do you use on your side? Can you give us more details?
1. the NTP server config;
2. Only switches are affected?
PHTP wrote
@Vincent-TP
We do not use Google TimeServer and have the same problem.
- Copy Link
- Report Inappropriate Content
@Vincent-TP
I find some interesting Infos.
When we change the time server, it doesn't take long before only a certain type of switch fails.
All other switches continue to run without any problems.
All affected switches also have the same firmware:
Model SX3008F v1.20
Firmware version 1.20.14 Build 20251226 Rel.60828
- Copy Link
- Report Inappropriate Content
Hi @PHTP
Thanks for that info. We are working on it.
When we change the time server, it doesn't take long before only a certain type of switch fails.
>>>Can you please let us know what NTP server did you change to? We will test it locally.
PHTP wrote
@Vincent-TP
I find some interesting Infos.When we change the time server, it doesn't take long before only a certain type of switch fails.
All other switches continue to run without any problems.All affected switches also have the same firmware:
Model SX3008F v1.20
Firmware version 1.20.14 Build 20251226 Rel.60828
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 310
Replies: 13
Voters 0
No one has voted for it yet.
