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

NetPath not seeing my L3 switch

I'm new to NetPath and just trying it out. I started with a simple service probe between my Orion host and a core switch on our remote network across the WAN. While NetPath did fill in most of the blanks, the one that has me scratching my head is the LOCAL core switch, the second hop in this picture. This is a node that is monitored by NPM, has full SNMP stats on it, and is the L3 router for my local network... but NetPath says it cannot communicate with it and there is "no response." What is misconfigured on this core switch that would prevent NetPath from communicating with it, even though it sees it as a (valid) hop in the path?

Find more posts tagged with

Accepted answers

All comments

ken_cohen

The only reason I can think of is if the protocol you have NetPath using is blocked at the switch, possibly by an ACL.

rschroeder

Is it possible NetPath has discovered that node by a different IP address than it is known by NPM? For example, if you've got NPM & NCM managing it via a loopback0 at 192.168.20.20, but the actual hop to/from it discovered by NetPath is 10.10.20.20, would that explain why NetPath isn't aware of its details?

Similarly, if there are any rules or restrictions regarding what devices can learn that device's information, or from what interfaces the information can be learned, could they be affecting NetPath's discovery of the node's details?

How about CDP and LLDP--are they enabled / allowed on the links NetPath discovers?

And are all of NetPath's required TCP ports allowed to talk to the L3 node?

foonly

The TCP packets are obviously making it through. The crafted packets rely on the ICMP response from the device when TTL is exceeded.

Check the ICMP settings for the L3 interface on your core to make sure that all ICMP types are allowed.

alvaro.culebras

When you use netpath to a switch or router what port do you use generally?

I am new with netpath and I´m having the same problem as pufferdude and I don´t know if coul be the port.

rschroeder

Please review this document and ensure the stated ports are opened / allowed for access.

Port requirements for all SolarWinds products - SolarWinds Worldwide, LLC. Help and Support

Swift packets!

Rick Schroeder

rschroeder

You'd only point at a port to which the switch or router listens. For example, you could point at TCP port 22 since you use it for SSH to manage the switch or router via CLI. Or perhaps you'd point at TCP port 179 if you're tracking BGP hops. Use whatever port your target device allows.

ACL's on the switch or router may need to be adjusted to allow your SolarWinds NetPath poller's source address, if you lock traffic down so securely that traffic from your NetPath poller would be dropped without an appropriate ACL allowing it.