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

tcp IPSLA fails - test on systems works fine

probably missing something simple, but...
trying to implement some sort of tcp test across our WAN ckts from head end router to remote (across frame).
set up tcp to port 22 from loopback to loopback in IPSLA.
made sure both loopbacks were managed.
This fails in IPSLA, but if i telnet to port 22 from the head end router sourcing from loopback to remote loopback it works fine....

any thoughts/suggestions?

Find more posts tagged with

Accepted answers

njoylif

got it...had to enable responder on remote (target)...only going one way...
#>ip sla monitor responder

thanks

All comments

tom.rybka

njoylif,

There is a thread related to your question, it may be caused by firewall rules which don't allow communication on port 1967 which is IPSLA uses for controlling signals and messages. Please take a look at:

Are you trying to create an automatic operation for this in IP SLA Manager?

njoylif

thanks for the response. My IPSLA/NPM is behind a firewall, but the IPSLA TCP test is from router to router connected to eachother by frame (with no ACLs in place on the frame interfaces). The SLA gets configured on the router no problem through NPM IPSLA website. does that make sense? Do I still need to open 1967 (I assume if it configures the router, its good, but... )
I read the linked and will test, but also want to verify from this angle.

thanks again.

njoylif

got it...had to enable responder on remote (target)...only going one way...
#>ip sla monitor responder

thanks

njoylif

I would have expected IPSLA to go out and configure this...no?
I thought you could configure the whole thing through NPM/IPSLA.

thanks