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

Failure by the the firewall ipsla hops monitoring

Hello everyone, i have tested the Solarwinds IPSLA, this was my topology:

I have added the ICMP Path Jitter from R1(enable ipsla) to R3(f0/0) used Solarwinds IPSLA, then the hop monitoring was right, from R1 to R2, and R2 to R3(f0/0), was 2 hops.

But when i tested in my production environment, between R1 and R2 has a Cisco ASA Firewall, the topology like this:

The hops was chang to 1? I guess the ASA Firewall has restriction, but i don't know what should I do configuration?

Find more posts tagged with

asa

ipsla

cisco

Accepted answers

FormerMember

Hi all, I tested the same topology using PIX, the same result, so I can basically confirmed the firewall itself was not supported the IPSLA path detection.

All comments

bob55

Hi liufisky,

is traceroute working from R1 to R3?

Regards,

Robert

FormerMember

Hi bob55, traceroute can reach R2 (f0/0).

FormerMember

After testing, i found this situation was caused by the firewall, maybe the IOS version, maybe the firewall itself was not supported the IPSLA path detection.

michal.hrncirik

hi liufisky,

thanks for sharing your findings with our community.

Michal

FormerMember

Hi Michal, I am pleased to share with everyone my experience feelings

FormerMember

Hi all, I tested the same topology using PIX, the same result, so I can basically confirmed the firewall itself was not supported the IPSLA path detection.