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

Is this the solarwinds ipsla bug?

Hello everyone. I have tested the ipsla, my topology like this:

I added ICMP Path Jitter monitoring link from R1 to R3 ( f0/0 ), I used Custom, and use one or more external nodes as a target(192.168.2.2), operations like this now

Then I shutdown R2 ( f0/0 & f1/0 ) port, but the link status displayed like this

Why Hop 1 - R2 has no packet loss? From this monitoring, how can i find which link was down?

Then I enable R2 ports (f0/0 & f1/0), and after a few minutes, I shutdown R2 ports (f0/0 & f1/0) again, this time monitoring like this

What's mean about this? Is this the ipsla bug?

Find more posts tagged with

bug

ipsla

Accepted answers

All comments

michal.hrncirik

Hi, there is a frequency set for each IPSLA operation. Did you wait at least for a next poll? If you shut down R2 then you should see operation as unavailable/down.

In case you were waiting for a next poll I'd recommend to contact SolarWinds support for that.

you may see last poll time as part of operation detail page.

FormerMember

Hi michal, thanks for your reply! My Solarwinds Poll time is 120s, I set ipsla Frequency time is 10s, and I waited long enough time, but the monitoring was still.

bob55

Hi liufisky,

could you provide us with cli command "sh ip sla sta <operation number> det" result using operation number of path jitter operation "R1 -> 192.168.2.2"?

Thanks,

Robert

FormerMember

Hi bob55, I shut R2 ports (f0/0 & f1/0), after a few minutes, I enable the ports (f0/0 & f1/0), wait a few minutes again, then the display like this:

"show ip sla monitor operational-state" display like this:

The hops was wrong?

Why?