Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

IP SLA Reachability is always up?

Hello, im trying to get IP SLA to work on a test environment, this is my current configuration.

IP_SLA.jpg

Now if I issue a shut on any port on R1 even if i disconnect the cable, the

sh track 1 command always shows "reachability is up" if I try to ping 10.1.5.1 the ping fails.

the track 1 static route is always up.

If i replace the ASA1 for another router the SLA works, I tested this on a Real ASA with 8.2.2(16), I didnt not issue any routes as its a Production ASA, but I configured the IP SLA without a route and even sending the host down the sh track 1 command always shows "reachability is up"

Does anyone know what i might be doing wrong?

Many Thanks

4 REPLIES
New Member

Re: IP SLA Reachability is always up?

please share the configuration and the destination you are tracking, will be more helpul with any rough diagram.

Sent from Cisco Technical Support iPhone App

Regards Waqas Younas CCIEx2 #27815 (Routing and Switching) (Service Provider) Contact for Online Training
New Member

Re: IP SLA Reachability is always up?

Hi, the whole configuration is on the diagram.

This is a test environment, therefore the only configuration R1 R2 and R3 have is interface IP addresses and EIGRP advertising network 10.1.4.0 and 10.1.3.0, and R4 advertising 10.1.5.0.

The Asa has the 2 interfaces configures and the IP SLA which is written on the diagram.

The destination of the track is 10.1.5.1 as in the configuration on the Diagram.

New Member

Re: IP SLA Reachability is always up?

I forgot to mention on the diagram configuration for the ASA i have sla monitor schedule 1 life forever start-time now

New Member

Re: IP SLA Reachability is always up?

Everything is working now, the problem was that after everything was setup, a reload on the firewall did the trick.

Thanks

169
Views
0
Helpful
4
Replies