Node down vs Node is unreachable by ICMP
-
-
Hi Egert,
I had the same issue with Nodes Unreachable by ICMP. Victor and I determined that the ICMP poll was ignoring the server setting for PollCountForStatusChange (mine is set to 5 and it alarmed on one missed ping). I believe they are working on fixing this. Until that happens, I just disabled the Event Processing Policy.
Cheers,
Donovan. -
-
Can I ask if this is still an issue please, our system will report in this order for example for most devices on a regular basis?
09:41:32 - SYS_ICMP_UNREACHABLE
09:41:32 - SYS_NODE_MAJOR
09:42:34 - SYS_ICMP_OK
09:42:34 - SYS_NODE_NORMAL -
Hi, Does anyone know please??
-
Hi,
problem with ICMP polls ignoring "poll count for status change" was fixed. Do you have poll count set to more than 1 and still get regular ICMP unreachable?
Best regards,
Victor -
Hi Victor,
Sorry I didn't see you had commented.
I've upped my poll count from the default of 1 to 2 but i'm still getting these messages?
See below
-
Can you try to set debug level to 7 for tag poll.icmp, and when problem repeats, send me extract from the server log filtered by object name?
Best regards,
Victor -
Hi Victor,
Please see below for one client, went unreachable, major at 09:58:23, back to normal 10:00:42
Thanks
Nick2023.05.31 09:56:11.912 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:56:11.912 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 09:57:16.994 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:57:18.292 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=2 RTT=0
2023.05.31 09:58:22.612 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:58:23.800 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=2 RTT=0
2023.05.31 09:59:33.326 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 09:59:33.326 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=2
2023.05.31 10:00:42.308 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:00:42.308 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 10:01:52.415 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:01:52.415 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=1
2023.05.31 10:02:57.539 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:02:57.539 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 10:04:02.641 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:04:02.641 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
2023.05.31 10:05:07.675 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: calling IcmpPing(192.168.1.85,3,1500,46)
2023.05.31 10:05:07.675 *D* [poll.icmp ] Node::icmpPollAddress(GARDENW10-1 [14138], PRI, 192.168.1.85):: ping status=0 RTT=0
-
According to log server got two timeouts - at 09:57:18 and 09:58:23 (status=2 means timeout). Next ping was successful again. Do you think there was a possibility of network issues at that time that could cause loss of ICMP packets? Also, if you change poll count to 3 or 4, will it fix the situation?
Best regards,
Victor -
Hi Victor,
Thanks for the reply, I'm unsure on network issues, it's small, around 50 switches.
Will increases the poll count to 3 and see.
Thanks
Nick
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login