Book a demo
Zynty / Documentation / Device & inventory management
Device & inventory management · 6 min read · troubleshooting

Troubleshoot a device showing Unreachable

A step-by-step path for diagnosing the most common reason a device won't report data.

What you'll need

  • Network access to test connectivity from the collector's segment
1

Confirm what Zynty tried

Open the device and check the specific failure reason shown, timeout, connection refused, and authentication failed each point to a different fix.

Zynty application screenshot
1
2

Rule out basic connectivity

From the collector (not your laptop, routing can differ), confirm the device answers ICMP and that the monitoring port is open.

ping 10.20.9.1
nc -vz -u 10.20.9.1 161   # SNMP
nc -vz 10.20.9.1 22       # SSH
3

Check for a changed credential

A common cause is a community string or password rotated on the device but not updated in Zynty. Re-enter the credential on the device's Protocols tab.

4

Check for an ACL or firewall change

If connectivity and credentials both check out, confirm nothing changed in an intermediate firewall or the device's own management-plane ACL, this is especially common right after a config push or change window.

← Previous
Organize devices into sites and groups

Related guides

Import devices in bulk via CSV

Onboard hundreds of devices at once instead of adding them one at a time.

importcsvbulk

Auto-discover devices on a subnet

Scan an IP range and add what responds, faster than hunting down every device manually.

discoveryscan

Organize devices into sites and groups

Structure your inventory so dashboards, alert routing and reports reflect how your network is actually organized.

organizationsitesgroups