Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Nodes in Unknown or Down status

Nodes in Unknown or Down status


This article describes the issue when a node appears to have a status of Unknown or Down despite being able to ping the device.


SAM version 6.1 or later.



This issue occurs when the node is using SNMP instead of ICMP to poll the status of the system and SNMP is not working correctly.



Scenario 1:

  1. Go to Settings > Manage Nodes.
  2. Select the node that shows an Unknown or Down status, and click List Resources. 
  3. Under Status & Response Time, select "ICMP" and click Submit.  If ICMP was already selected, select "SNMP" and then click Submit. Then go back to List Resources, select "ICMP", and click Submit.

Note: If these steps did not resolve the issue, try deleting and then recreating the node in question. 

  4. check the windows firewall for "file and print sharing, (echo-request - ICMPv4)" verify this is enabled.


Scenario 2:

In some cases you may see the devices (especially network) showing incorrect nodes status as down even though you can ping them from Orion Server. And the Orion Server also reports 100% packet loss on these nodes.


This is due to ACL's on the intermediary firewall between the devices being monitored OR the Device itself blocking traffic from IP / network that is hosting the Orion Server.


Remove the Orion Server IP from ACL block list on the firewalls between the Orion Server and managed network nodes. And wait for next poll from Orion or Poll them manually.


Last modified