NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SNTP KISS IRIG
I do not understand why I am getting this KoD.
I did not recieve this KoD packet with the older firmware.
| M5300-28G-POE+ ProSafe 24-port Gigabit L2+ PoE+ with 10 Gigabit Stacking, 11.0.0.28, B1.0.0.5 |
Apr 5 08:23:18 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(463) 2770 %% SNTP: Received KoD packet from 192.168.1.1 - Kiss Code = IRIG |
| <14> Apr 5 08:22:59 4619 8FT M5300-28-1 General[emWeb]: main_login.c(216) 2769 %% HTTP Session 11 initiated for user admin connected from 192.168.0.104 |
| <14> Apr 5 08:22:59 4619 8FT M5300-28-1 CLI_WEB[emWeb]: emweb_common_custom.c(162) 2768 %% HTTP Session 11 started for user admin connected from 192.168.0.104 |
| <15> Apr 5 08:14:46 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(1900) 2767 %% SNTP: system clock synchronized on Wed Apr 5 13:14:46 2017 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (192.168.1.1). |
| <13> Apr 5 08:14:41 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(463) 2766 %% SNTP: Received KoD packet from 192.168.1.1 - Kiss Code = IRIG |
| <15> Apr 5 08:06:09 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(1900) 2765 %% SNTP: system clock synchronized on Wed Apr 5 13:06:09 2017 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (192.168.1.1). |
| <13> Apr 5 08:06:04 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(463) 2764 %% SNTP: Received KoD packet from 192.168.1.1 - Kiss Code = IRIG |
| <15> Apr 5 07:57:32 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(1900) 2763 %% SNTP: system clock synchronized on Wed Apr 5 12:57:32 2017 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (192.168.1.1). |
| <13> Apr 5 07:57:27 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(463) 2762 %% SNTP: Received KoD packet from 192.168.1.1 - Kiss Code = IRIG |
| <15> Apr 5 07:48:55 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(1900) 2761 %% SNTP: system clock synchronized on Wed Apr 5 12:48:55 2017 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (192.168.1.1). |
| <13> Apr 5 07:48:49 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(463) 2760 %% SNTP: Received KoD packet from 192.168.1.1 - Kiss Code = IRIG |
| <15> Apr 5 07:40:17 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(1900) 2759 %% SNTP: system clock synchronized on Wed Apr 5 12:40:17 2017 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (192.168.1.1). |
| <13> Apr 5 07:40:12 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(463) 2758 %% SNTP: Received KoD packet from 192.168.1.1 - Kiss Code = IRIG |
| <15> Apr 5 07:31:40 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(1900) 2757 %% SNTP: system clock synchronized on Wed Apr 5 12:31:40 2017 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (192.168.1.1). |
| <13> Apr 5 07:31:35 4619 8FT M5300-28-1 SNTP[SNTP]: sntp_client.c(463) 2756 %% SNTP: Received KoD packet from 192.168.1.1 - Kiss Code = IRIG |
7 Replies
Hi klat0n,
Kindly answer the questions below:
a. Have you tried to factory reset the M5300-28G-POE+ switch then reconfigure it from scratch?
b. What device is 192.168.1.1? Have you tried to disconnect the M5300-28G-POE+ switch from this device and check if same error will show on the logs?
c. How is everything connected? It would be best to post a diagram of your detailed network setup.
I look forward to your response.
Regards,
DaneA
NETGEAR Community Team
Regarding your question "a." This is not an option because all of the switches that are having this problem are in production.
Question "b." This is a NTP server where all of our devices get is time stamp from. I have tried rebooting and disconnecting the NTP server and the results are the same.Everything is connected by either fiber or copper in a "star" configuration. the NTP server is connected by copper on one leg of the STAR. A map should not be necessary.
Is it not possible to perform the factory reset then reconfigure from scratch during idle hours like on a weekend or after production hours in order to isolate the problem?
If ever you did the factory reset and still the same problem, kindly downgrade the firmware from v11.0.0.28 to v11.0.0.14. The firmware v11.0.0.14 addressed the issue about KoD. Be reminded to perform a factory reset after downgrading the firmware then reconfigure the switch from scratch.
You can download firmware v11.0.0.14 here.
Let us know the results.
Regards,
DaneA
NETGEAR Community Team
I am currently setting up another switch in the lab for testing out your suggestions. Although the suggestions provide are not the best solutions.
If you look back at the release notes for the firmware version you metioned , this is not the same problem that I am having.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
