[c-nsp] A few very Quick IP SLA questions

[Drew Weaver]

Does that Syntax work on 6500s (SXI3) it doesn't seem to in my case?

thanks,
-Drew


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Ziv Leyes
Sent: Sunday, July 18, 2010 4:32 AM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] A few very Quick IP SLA questions

Wouldn't the source issue be solved if you use
  type echo protocol ipicmpEcho x.x.25.97 source-interface Giga0/1
instead of source-ip?


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Drew Weaver
Sent: Friday, July 16, 2010 6:15 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] A few very Quick IP SLA questions

Hi all, happy Friday.

A few questions regarding configuring IP SLA.

I've configured two IP SLA probes as such:

ip sla 1
 icmp-echo x.x.25.97 source-ip x.x.25.98
 frequency 10
ip sla schedule 1 life forever start-time now

ip sla 2
 icmp-echo x.x.25.101 source-ip x.x.25.102
 frequency 10
ip sla schedule 2 life forever start-time now

1) If I want this probe to run forever, is it best to configure it as a recurring probe or have the lifetime be 'forever'?
2) If the router has multiple paths to the destination does specifying the source-address mean that 100% of the time it will use the Interface that the indicated source address is assigned to?
3) When using the 'track command' (for example: track 100 ip sla 1 reachability | state) What is the functional difference between reachability and state? Wouldn't they be the same thing?

Also the main reason for implementing this is because we had an instance where a interface didn't go down, but no traffic would pass through it (routing protocols failed, etc) and we have our default routes setup as such:

ip route 0.0.0.0 0.0.0.0 Vlan4091 x.x.25.97
ip route 0.0.0.0 0.0.0.0 Vlan4092 x.x.25.101

So return traffic was still being sent down the 'dead but up/up' interface which caused obvious heartache.

Would using a track on each of these routes (combined with aforementioned IP SLA probes) be a good way to prevent this from occurring in the future?

I basically want to ensure that both the interface is up and that traffic can pass from this router to its gateway before the route will be used.

Sorry this is so long, hopefully it makes at least some sense.

I thought about using BFD, but it seems like they have removed support for BFD on VLANs in recent code.

Thanks,
-Drew

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************




 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************




_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/