Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Netpath: AWS Endpoint unreachable

Ive setup Netpath to monitor AWS endpoints from several locations in our network. However from some locations im seeing endpoints as Unreachable, others work just fine. In an attempt to get the "Unreachable agents" to start working Ive tried the following:

- As a test, Ive setup an EC2 instance in AWS and allowed all traffic to and from this host.
- Im attempting to probe on several ports. Including 80 and 443. There is no difference in results.
- Local firewalls are setup to allow all traffic, including ICMP type 11. No indications in logs that traffic gets blocked.
- Netpath is showing the full path traffic takes, with the exception of the actual endpoint.
- Im currently running NCM HF1

Did anyone else encounter similar behavior? Any fixes for this issue?

Find more posts tagged with

Accepted answers

All comments

ehauser

This seems related to this issue:

https://thwack.solarwinds.com/t5/NPM-Discussions/Netpath-to-Amazon-AWS-more-hosts-and-fails/m-p/311192

Looks like no solution was ever found.

rschroeder

I've had similar challenges with cloud-based resources showing up as unavailable in Netpath.

One explanation offered to me was that the cloud provider(s) has no obligation to keep a specific resource available. It may be placed behind a load balancer that keeps services running, but individual IP addresses belonging to those original services may change or be used for other solutions or be retired.

I've seen Amazon and Microsoft cloud-based resources show 100% down/unavailable in Netpath, but still been able to use those same services. When services can move around the nation, or around the world, based on demand and availability, it appears to challenge Netpath's ability's to be flexible enough to monitor a moving target.

I'll be watching this space to see what others offer, and to read if you find a solution in the future.

Swift Packets!

Rick Schroeder