How ICMP polling works? Node is down (not pinging as well)but still status is up

I suspect you are not seeing a change because the node is in maintenance mode.

Suspend collecting data or mute alerts for nodes in maintenance - SolarWinds Worldwide, LLC. Help and Support

Well, it appears that alerts are muted, because the system has been set into maintenance mode. That's why you don't get alerts. Not sure why it shows as being up though...?

Have you checked that the device doesn't ping from your Orion server directly rather than your own desktop/laptop? It could be an ACL issue.

Failing that you could set the device as UnManaged and then Manage it again (This should result in an Unknown Status which then turns to Down)

Two things come to mind:

1. Is the response time actually being polled via ICMP or is it SNMP?
   How Orion calculates the polling response time using SNMP and ICMP - SolarWinds Worldwide, LLC. Help and Support
2. If the node is actually down, then it seems like something else might be going on there. Duplicate IP assignment? Hostname resolves to another IP? Some routing shenanigans?

I would try pinging by the hostname and see if it resolves. Maybe it's returning a different IP address and that's why.

I checked in my QA environment and it doesn't seem like muting the alerts alone would be enough to cause it, I still see the status of the node change. I would check those two things as they seem the most likely, otherwise there might be something else going on in your environment.

No, Today, I kept on the mute state. the concern is when the node is not pinging then why it's showing up?

Check to see if your blocking icmp on your firewall. The node can still show as "Up" if you are monitoring via SNMP not ICMP. BTW, you forgot to scrub one of the IP addresses in your screen shots.

Hello Jroupviere,

Its polling via ICMP. So, there is no such option to check the resource to check the response time. little bit surprised if the node is down (not pinging)  it should show in upstate in SolarWinds. I did nslookup there is duplication.

1. I am assuming something else must have screwed up here, this looks to me like a issue with SolarWinds, this probably happened because it could not update the status value of node on its DB and DB is still holding the value 'UP' which was the old status value (before you set mute alerts on it I guess the node was UP and the DB is still holding the same value).

2. For the remaining folks - this node is being polled via ICMP, hence we can rule out option one where SNMP is used for Node status.

3. Could you do me a favor, just login into node page and check the PING report and availability of the node (since you are only using mute alerts option SolarWinds should still be pinging this device, is it doing that ? This is what i would need to look into, at first place - if the report inside Node page is showing 100% ping loss and if availability of node is 0, then try to unmanage and re-manage the node, check if the status of node falls back in place and gives the correct status)

4. The issue could be more serious than what you are suspecting, check for other nodes like these in your environment, if the issue is similar then raise a case with SolarWinds immediately (there could be several reasons as to why such things happen, issue with JobEngine, issue on DB, connectivity issues with the DB - i mean solarwinds is not talking to its own DB due to dropped connections etc)

Hope it helps

what sort of duplication ? Do you see 2 host-names for the same IP ?

Hi Tony,

I have checked port is open on the firewall.