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

monitor secondary IP without creating another node instance

is there a way to monitor a secondary IP without creating another node instance?

scenerio......

we have a couple sites with redundant routers, each with their own circuit. we also use sdwan which evaluates the 2 paths to the site and sends traffic over whichever path is better.

last week we had an issue with one of the circuits where it was dropping outbound traffic. our node monitoring did not pick this up since the routers are managed by an internal loopback and the polling of the effected device went over the good sdwan link. our interface error detection didn't pick it up either because there were no incrementing errors, just dropped packets. this would have been discovered if we were also performing ping tests to the public IPs

i'm looking for a way we can icmp monitor the public IPs on these routers in addition to the loopback management IP.

Find more posts tagged with

Accepted answers

brscott

The ideal is one template and just change the "script arguments" field after you assign it.

Not sure why it didn't work with $args[0], try replacing that top line with these two lines and make sure you are setting the script arcuments to an ip address or hostname when you are testing it.

param ( $IP )
$AvgTime = Test-Connection $IP -Count 3 -ErrorAction SilentlyContinue | Measure-Object -Property ResponseTime -Average

All comments

Kuroneko

We use snmp on the loopback and additional icmp nodes for the circuit IP. Only way to get latency and packet loss statistics for each IP.

chad.every

I've used the NetPath feature in NPM for this type of scenario. The 'node' is simply wherever you install the NetPath agent but you can source multiple paths from that agent. My scenario was more inside my network going outbound and I had to create rules to force certain netpath destinations to always travel over a certain circuit. Then there are some netpath alerts can can be created.

brscott

If you have SAM, then you can add an application monitor with a powershell component. The script could be something like:

$AvgTime = Test-Connection $args[0] -Count 3 -ea 0 | measure-Object -Property ResponseTime -Average
$AvgTime
if ( $AvgTime.Count -gt 0 ) {
"Statistic.responsetimems: $($AvgTime.Average)"
} else {
"Statistic.responsetimems: NaN"
}

The argument would be the IP address you want to ping.

brscott

I pulled that out of one of our monitors, and now that I look at it, I don't think it will alert the way they expected it to... but you get the idea. I think I am going to rewrite that.

brscott

There! Now you can set thresholds on response time and response count. And just like that... some of monitors went red... I guess I better inform those responsible for their monitors of what I just did.

$AvgTime = Test-Connection $args[0] -Count 3 -ErrorAction SilentlyContinue | Measure-Object -Property ResponseTime -Average

Write-Host "Statistic.ResponseCount: $($AvgTime.Count)"
Write-Host "Message.ResponseCount: $($AvgTime.Count) ICMP responses received"

if ( $AvgTime.Count -gt 0 ) {
Write-Host "Statistic.ResponseTimeMs: $($AvgTime.Average)"
Write-Host "Message.ResponseTimeMs: $($AvgTime.Average)ms average response time"
} else {
Write-Host "Statistic.ResponseTimeMs: "
Write-Host "Message.ResponseTimeMs: ERROR No responses received"
}

bgoulet

hahaha!

i assume the powershell script runs on the SW engine, not the monitored node? the nodes in this case are cisco routers.

i have some coding experience but none with PS so i'm having a bit of difficulty understanding how this works. is it good to go as-is or do i need to tweek some thresholds?

i've also never worked with SAM. is there a good instructional guide on working with SAM/PSscripts? how to create, how to gather and report on data, etc.