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

Include target hostname for each Hop in Current and Historical Traceroute resources

On the ICMP Path Echo Operations view, Current and Historical Traceroute resources, include the target hostname for each Hop. I have trouble keeping ip addresses in my head and hate having to take additional steps to figure out what the Hop device name is.

For example, Hop 1 - 10.10.10.1 <targethostname> 1.0ms

Find more posts tagged with

Accepted answers

All comments

tom.rybka

Unfortunately, no dynamic reverse DNS resolution is implemented in IPSLA Manager. However, IP addresses that represent nodes in Orion are displayed as node names instead. If there is a specific IP address of your interest, you may consider adding it as a node (it may be even unmanaged) so it displays its name instead of the IP address.

fcaron

Rgward,

Is this an acceptable solution? Are your intermediate nodes/hops managed (or at least known) by NPM Core?

FormerMember

Unfortunately, no dynamic reverse DNS resolution is implemented in IPSLA Manager. However, IP addresses that represent nodes in Orion are displayed as node names instead. If there is a specific IP address of your interest, you may consider adding it as a node (it may be even unmanaged) so it displays its name instead of the IP address.

Is this an acceptable solution? Are your intermediate nodes/hops managed (or at least known) by NPM Core?

Francois/Tom, No, this is not acceptable solution. All our immediate nodes/hops are managed by NPM. With ICMP Path Ping, the interface addresses are reported per hop, not the node's managed ip address which is typically the node loopback address. All our core node interfaces are in DNS. So, if I understand Tom's response, I need to revise my feature request to add dynamic reverse DNS resolution to the Current and Historical Traceroute resources.

fcaron

Created requirement (74876).

Good input, thank you.