Re: [c-nsp] IP SLA tracking, static routes and OSPF announcements

Ok, got it, that works unfortunately the data has rolled so if I’ll keep it up my sleeve to do this if it happens again… Scott H Login, LLC > On Apr 22, 2018, at 7:57 PM, Khan Muddassir wrote: > > Hi Scott, > the command looks to be "sho ip ospf statis", I wrongly typed

Re: [c-nsp] IP SLA tracking, static routes and OSPF announcements

Hey, > We have a very strong policy to *NEVER* point a route towards just an > supposedly-connected IP address, always use an interface along with it. To reword the statement, do not enable route recursion unless you know you need it. In IOS(-X[ER]) recursion is always on, in JunOS you need

Re: [c-nsp] IP SLA tracking, static routes and OSPF announcements

Muddasir; Unfortunately I do not, the statistics command does not seem to exist; sh ip ospf database statistics ^ % Invalid input detected at '^' marker. sh ip ospf database ? adv-routerAdvertising Router link states asbr-summary ASBR

Re: [c-nsp] IP SLA tracking, static routes and OSPF announcements

Hi, On Fri, Apr 20, 2018 at 09:52:32AM -0500, Scott Harvanek wrote: > ip route x.x.x.x 255.255.255.224 track 5 > ip route x.x.x.x 255.255.255.248 track 5 As a side note, and it might not be relevant to this at all. We have a very strong policy to *NEVER* point a route towards just an

[c-nsp] IP SLA tracking, static routes and OSPF announcements

I’ve encountered an odd routing issue and I’m hoping it’s a simple configuration issue and not a Bug, looking for input on this please :) Equipment: Cisco 6500E series w/ SUP720 MSFC3/PFC3 Software: 15.1(2)SY10, RELEASE SOFTWARE (fc4) ADV IP Services Scenario; We have a pair of the above

Re: [c-nsp] IP-SLA on 7600 - 12.2(33)SRE3

Bill, it works just fine as this is a platform independent feature, just make sure not to overload the cpu... Arie On Tue, Apr 26, 2016, 16:32 Bill Buhlman wrote: > Any one using IP-SLA on a 7600 running 12.2(33)SRE3? I have a customer > wanting to use it for a backup

[c-nsp] IP-SLA on 7600 - 12.2(33)SRE3

Any one using IP-SLA on a 7600 running 12.2(33)SRE3? I have a customer wanting to use it for a backup circuit. Have not configured it before... Thanks, Bill Bill Buhlman Network Engineer Contra Costa County Office of Education 77 Santa Barbara Road Pleasant Hill, CA 94523 925-942-5362 -

[c-nsp] IP SLA - all zero's for latency one-way measurements

Anyone know why I would be seeing zero's for latency ? It just seems to come and go. sometimes I see all zero's and other times I see numbers that seem realistic. I would expect some latency. actually about 7 milliseconds of round trip latency is expected.. But zero latency seems weird to me.

Re: [c-nsp] IP SLA - all zero's for latency one-way measurements

Check your clock sync. On Thu, Aug 27, 2015 at 6:53 AM, Aaron aar...@gvtc.com wrote: Anyone know why I would be seeing zero's for latency ? It just seems to come and go. sometimes I see all zero's and other times I see numbers that seem realistic. I would expect some latency. actually about

Re: [c-nsp] IP SLA?

Dan Brisson dbris...@gmail.com writes: I'm waiting to hear what the customer has for hardware/software, although in that this is a Co-lo environment, it would be nice to have a standard method for dual-connecting customers at Layer 3 when the next one requests it. That's what scares me

Re: [c-nsp] IP SLA?

On 3/29/15 12:46 AM, Mark Tinka wrote: On 29/Mar/15 05:12, Dan Brisson wrote: Labbing this up, OSPF makes the default route advertisement much easier: router ospf 160 network 192.168.10.1 0.0.0.3 area 0 default-information originate always Downsides of OSPF vs. EIGRP in this scenario?

Re: [c-nsp] IP SLA?

Hi, On Sun, Mar 29, 2015 at 06:46:40AM +0200, Mark Tinka wrote: Downsides of OSPF vs. EIGRP in this scenario? I just think it's a terrible idea running an IGP with a customer. I mean, I see the benefit from a link failure detection point of view, but an IGP is still an IGP - and that I

Re: [c-nsp] IP SLA?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/Mar/15 10:44, Gert Doering wrote: EIGRP can be filtered just as well as BGP, and has much nicer convergence properties. I have no experience with EIGRP, so I won't even try :-)... OSPF would theoretically be unviable (all link-state

Re: [c-nsp] IP SLA?

On 29/Mar/15 14:46, Dan Brisson wrote: I'm waiting to hear what the customer has for hardware/software, although in that this is a Co-lo environment, it would be nice to have a standard method for dual-connecting customers at Layer 3 when the next one requests it. That's what scares me

Re: [c-nsp] IP SLA?

Hi, On Sun, Mar 29, 2015 at 10:34:53PM +0200, Mark Tinka wrote: Not being negative, just saying that while an IGP can solve the failure detection issue faster than BGP can, it opens up other issues you really need to evaluate. It will be difficult for you to appreciate these issues until you

Re: [c-nsp] IP SLA?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/Mar/15 22:45, Gert Doering wrote: On the other hand, while you are still all picking on me for suggesting an IGP - don't forget the havoc that you can do with BGP, like, not having proper incoming filters and not ensuring that prefixes

Re: [c-nsp] IP SLA?

Hello, On 3/24/15 8:48 AM, Gert Doering wrote: Hi, On Tue, Mar 24, 2015 at 08:27:59AM -0400, Dan Brisson wrote: I'm curious what folks do in the situation where you have redundant links to your customers. I'm speaking primarily in co-lo environments where you offer redundant Internet

Re: [c-nsp] IP SLA?

Hello, On 3/24/15 8:48 AM, Gert Doering wrote: Hi, On Tue, Mar 24, 2015 at 08:27:59AM -0400, Dan Brisson wrote: I'm curious what folks do in the situation where you have redundant links to your customers. I'm speaking primarily in co-lo environments where you offer redundant Internet

Re: [c-nsp] IP SLA?

On 29/Mar/15 05:12, Dan Brisson wrote: Labbing this up, OSPF makes the default route advertisement much easier: router ospf 160 network 192.168.10.1 0.0.0.3 area 0 default-information originate always Downsides of OSPF vs. EIGRP in this scenario? I just think it's a terrible idea

Re: [c-nsp] IP SLA?

+1 for using a routing protocol. BGP with a private AS is a decent fit here. On Mar 24, 2015, at 8:48 AM, Gert Doering g...@greenie.muc.de wrote: Hi, On Tue, Mar 24, 2015 at 08:27:59AM -0400, Dan Brisson wrote: I'm curious what folks do in the situation where you have redundant links to

Re: [c-nsp] IP SLA?

Hi, On Tue, Mar 24, 2015 at 12:53:36PM +, Scott Granados wrote: +1 for using a routing protocol. BGP with a private AS is a decent fit here. The main reason we like EIGRP here is less config, and faster failover, as compared to BGP :-) (BGP+BFD wins, of course, but I've yet to see a

[c-nsp] IP SLA?

I'm curious what folks do in the situation where you have redundant links to your customers. I'm speaking primarily in co-lo environments where you offer redundant Internet connectivity to co-lo customers. So for example, you give a customer 2 ethernet handoffs from two separate Layer 2

Re: [c-nsp] IP SLA?

On 24/Mar/15 14:48, Gert Doering wrote: You could use static+BFD, but I bet that half of the available gear will not support that... Or if it does, could be spotty for IPv6. This is one of the issues I have on the ME3600X. Mark. ___ cisco-nsp

Re: [c-nsp] IP SLA?

On 24/Mar/15 14:27, Dan Brisson wrote: I'm curious what folks do in the situation where you have redundant links to your customers. I'm speaking primarily in co-lo environments where you offer redundant Internet connectivity to co-lo customers. So for example, you give a customer 2

Re: [c-nsp] IP SLA?

On 3/24/15 8:30 AM, Jared Mauch wrote: On Mar 24, 2015, at 8:27 AM, Dan Brissondbris...@gmail.com wrote: I'm curious what folks do in the situation where you have redundant links to your customers. I'm speaking primarily in co-lo environments where you offer redundant Internet connectivity

Re: [c-nsp] IP SLA?

Hi, On Tue, Mar 24, 2015 at 08:27:59AM -0400, Dan Brisson wrote: I'm curious what folks do in the situation where you have redundant links to your customers. I'm speaking primarily in co-lo environments where you offer redundant Internet connectivity to co-lo customers. So for example,

Re: [c-nsp] IP SLA?

On 24/Mar/15 14:51, Dan Brisson wrote: It also occurs to me that this really isn't any different than a customer buying 2 connections from their premises to the same ISP. Or is it? It isn't, except in such cases, BGP is the best way to go. Mark.

Re: [c-nsp] IP SLA?

On Mar 24, 2015, at 8:27 AM, Dan Brisson dbris...@gmail.com wrote: I'm curious what folks do in the situation where you have redundant links to your customers. I'm speaking primarily in co-lo environments where you offer redundant Internet connectivity to co-lo customers. So for

[c-nsp] IP SLA FTP doesn't finish the download?

Ok, The situations is this... Router 3825 running 12.4(24)T5 advipsrv., with several VRFs. Each vrf is connected to a different modem, configured in a different service. The router has configured several IP SLAs... icmp, http, and off course ftp. All those probes are being monitored over SNMP to

[c-nsp] IP SLA issue

Hi All, I have a very simple configuration I am having problem with. track 2 rtr 1 reachability ! ip sla 1 icmp-echo 10.1.18.49 source-ip 10.0.254.30 timeout 500 frequency 3 ip sla schedule 1 life forever start-time now ! ip route 0.0.0.0 0.0.0.0 10.0.254.25 50 track 2 ip route 0.0.0.0 0.0.0.0

Re: [c-nsp] IP SLA issue

On 12/5/12 9:10 PM, Ali Sumsam wrote: Hi All, I have a very simple configuration I am having problem with. track 2 rtr 1 reachability ! ip sla 1 icmp-echo 10.1.18.49 source-ip 10.0.254.30 timeout 500 frequency 3 ip sla schedule 1 life forever start-time now ! ip route 0.0.0.0

Re: [c-nsp] IP SLA

Saku Ytti wrote: I have been looking at IP SLA and was wondering whether there are any appliances around which emulate Ciscos IP SLA so that you can use it as a responder, or even better, the transmitter end? Have you found any? I'd be very interested in commercial solution also.

Re: [c-nsp] IP SLA

On (2012-11-19 09:48 +0100), Christophe Fillot wrote: I've written a small responder that handles TCP connect, UDP echo and UDP jitter operations (for IPv4/IPv6), but unfortunately I don't know if I can publish it for the reasons you gave below. The protocol is easy to decode anyway.

Re: [c-nsp] IP SLA

Saku Ytti wrote: http://tools.ietf.org/html/draft-cisco-sla-protocol-04 http://www.juniper.net/us/en/local/pdf/app-notes/3500145-en.pdf I wonder if those implicitly mean that you are allowed to build responder or not. The Cisco draft is not really what we're seeing in real-life (real-life

Re: [c-nsp] IP SLA

On (2012-11-19 11:08 +0100), Christophe Fillot wrote: About the packet handling, since I only support TCP/UDP probes, I use the classic socket API. It is not using AF_PACKET to support some strange probes, it only supports UDP jitter for Cisco. It is using AF_PACKET so it can see full header

Re: [c-nsp] IP SLA

On Mon, Nov 12, 2012 at 7:09 PM, Saku Ytti s...@ytti.fi wrote: On (2011-10-19 18:01 +0200), Andrew Miehs wrote: I have been looking at IP SLA and was wondering whether there are any appliances around which emulate Ciscos IP SLA so that you can use it as a responder, or even better, the

Re: [c-nsp] IP SLA

On (2011-10-19 18:01 +0200), Andrew Miehs wrote: I have been looking at IP SLA and was wondering whether there are any appliances around which emulate Ciscos IP SLA so that you can use it as a responder, or even better, the transmitter end? Have you found any? I'd be very interested in

Re: [c-nsp] IP SLA configuration

On Fri, 2012-05-25 at 17:45 -0500, Michael Malitsky wrote: I am trying to configure IP SLA to track a static route. 2821 router, IOS 15.1.4(M)4, IP Base license. You need the Enterprise Base license for that platform. We were surprised by this too when we started rolling out a dozen of these

Re: [c-nsp] IP SLA configuration

You need an additional license for that feature On May 25, 2012 7:18 PM, Michael Malitsky malit...@netabn.com wrote: I know I shouldn't be trying anything new at the end of Friday before a long weekend, but... I am trying to configure IP SLA to track a static route. 2821 router, IOS

Re: [c-nsp] IP SLA configuration

Yeah, Data license. Regards, Alexander Lim On May 26, 2012, at 7:19 AM, chris tknch...@gmail.com wrote: You need an additional license for that feature On May 25, 2012 7:18 PM, Michael Malitsky malit...@netabn.com wrote: I know I shouldn't be trying anything new at the end of Friday

[c-nsp] IP SLA eigrp

Hi, Is it possible to make down ip eigrp routing protocol when ip sla icmp jitter detect, let say, 200ms or 10% packet loss to other host in network. Grzegorz Zapalski ___ cisco-nsp mailing list cisco-nsp@puck.nether.net

Re: [c-nsp] IP SLA eigrp

On 16/11/2011 15:22, Grzegorz Zapalski wrote: Is it possible to make down ip eigrp routing protocol when ip sla icmp jitter detect, let say, 200ms or 10% packet loss to other host in network. Would Performance Routing do what you're looking for?

Re: [c-nsp] IP SLA

FYI - Last I checked Brix system can provision (via snmp) ipsla tests to ipsla enabled Cisco routers, but can not emulate it on their own hardware verifiers Dave On 10/20/2011 05:03 AM, Tony Tauber wrote: At a previous employer, we used Brix Networks which was acquired by EXFO and is

[c-nsp] IP SLA

Hi all, I have been looking at IP SLA and was wondering whether there are any appliances around which emulate Ciscos IP SLA so that you can use it as a responder, or even better, the transmitter end? If not, does anyone have any alternative device/ software recommendations? Thanks Andrew

Re: [c-nsp] IP SLA

On Wed, 2011-10-19 at 18:01 +0200, Andrew Miehs wrote: I have been looking at IP SLA and was wondering whether there are any appliances around which emulate Ciscos IP SLA so that you can use it as a responder, or even better, the transmitter end? There's this company Cisco that produces some

Re: [c-nsp] IP SLA

On Apr 1, 2010, at 12:33 AM, Mohammad Khalil wrote: how can i draw IP sla results ? I use the Solarwinds IP SLA manager. http://www.solarwinds.com/products/ip-sla-monitoring/info.aspx ___ cisco-nsp mailing list cisco-nsp@puck.nether.net

Re: [c-nsp] IP SLA

At a previous employer, we used Brix Networks which was acquired by EXFO and is presented here: http://www.exfo.com/en/Products/ProductList.aspx?Id=261 That was many years ago and I didn't work with it directly, but that is the intended use of the product. Tony On Wed, Oct 19, 2011 at 12:01

Re: [c-nsp] IP SLA

On Oct 19, 2011, at 3:05 PM, Steve Rubin wrote: On Apr 1, 2010, at 12:33 AM, Mohammad Khalil wrote: how can i draw IP sla results ? I use the Solarwinds IP SLA manager. http://www.solarwinds.com/products/ip-sla-monitoring/info.aspx Oops, sorry for the old reply. The new thread

Re: [c-nsp] IP SLA on redundant backhauls

Subject: [c-nsp] IP SLA on redundant backhauls Hi, I have the following scenario ISP --- link A -- CE link B - I have a lot of voice traffic on this backhaul.. The problem is that when a circuit has problems in terms of (errors incrementing) but circuit doesnt go down

[c-nsp] IP SLA on redundant backhauls

Hi, I have the following scenario ISP --- link A -- CE link B - I have a lot of voice traffic on this backhaul.. The problem is that when a circuit has problems in terms of (errors incrementing) but circuit doesnt go down at all, ospf is stable but voice is not reliable

Re: [c-nsp] IP SLA source pings on PIX/ASA ?

To anybody reading this, this is an open bug/feature request with Cisco TAC. On Thu, Apr 14, 2011 at 7:24 AM, Rama Darbha rdar...@gmail.com wrote: Eshan, This is a tricky design, as you know we can't ping to or from the far side interface of the PIX/ASA. Here is a guide that talks about

Re: [c-nsp] IP SLA source pings on PIX/ASA ?

Eshan, Do you have the bugID? Regards, Rama On Tue, Apr 19, 2011 at 2:43 AM, Eshan Bhide eshanbh...@gmail.com wrote: To anybody reading this, this is an open bug/feature request with Cisco TAC. On Thu, Apr 14, 2011 at 7:24 AM, Rama Darbha rdar...@gmail.com wrote: Eshan, This is a tricky

[c-nsp] IP SLA source pings on PIX/ASA ?

I tried asking this question elsewhere but wasn't able to get a satisfactory response, thought I should try here! We have site to site mesh ipsec tunnels that terminate on different PIXes. A requirement for clients using these tunnels is to monitor the downtime on a particular tunnel - using a

Re: [c-nsp] IP SLA Scalability

On Thu, Oct 21, 2010 at 4:52 PM, Mikael Abrahamsson swm...@swm.pp.sewrote: On Thu, 21 Oct 2010, Ben Steele wrote: Has anyone ran a rather large amount of SLA probes from a router who can comment on the cpu performance characteristics on how it scaled for your particular platform? You

Re: [c-nsp] IP SLA Scalability

If you're doing this in an MPLS VPN scenario, you might want to make sure you test your code so it has timestamping for arrival time for packets even if they are labeled. I ran into this on a 7301 5 years ago, took 14 months for that TAC case to complete with the answer that timestamping

[c-nsp] IP SLA Scalability

Hi, Has anyone ran a rather large amount of SLA probes from a router who can comment on the cpu performance characteristics on how it scaled for your particular platform? Specifically looking to see if its feasible to expect a router to be able to go upwards of 500+ simultaneous monitors(looking

Re: [c-nsp] IP SLA Scalability

On Thu, 21 Oct 2010, Ben Steele wrote: Has anyone ran a rather large amount of SLA probes from a router who can comment on the cpu performance characteristics on how it scaled for your particular platform? You should really contact your account team to get a comment from them. I've spoken to

Re: [c-nsp] IP SLA measurement against USA

On Jul 15, 2010, at 6:02 AM, LM wrote: Hi, I want to control the SLA gave by our internet provider against USA and Europe. The issue is that I would like to configure SLA code in our border routers to have some visibility of it. So, is there anyone in the mailing list who can give me a

Re: [c-nsp] IP SLA measurement against USA

Thanks for your answer, I will take a look to it. El 21/07/10 14:11, Anton Kapela escribió: On Jul 15, 2010, at 6:02 AM, LM wrote: Hi, I want to control the SLA gave by our internet provider against USA and Europe. The issue is that I would like to configure SLA code in our border

[c-nsp] IP SLA measurement against USA

Hi, I want to control the SLA gave by our internet provider against USA and Europe. The issue is that I would like to configure SLA code in our border routers to have some visibility of it. So, is there anyone in the mailing list who can give me a fixed points -IPs- to verify this?, I don't

[c-nsp] IP SLA

how can i draw IP sla results ? _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969

Re: [c-nsp] IP SLA

2010/4/1 Mohammad Khalil eng_m...@hotmail.com how can i draw IP sla results ? I use CACTI and IP SLA templates to draw ICMP Echo RTT and VoIP jitter. Works pretty well. http://gregsowell.com/?p=1333 http://forums.cacti.net/about19542.html http://forums.cacti.net/about4136.html --

Re: [c-nsp] IP SLA

You can draw O/P using SMNP OIDs with MRTG. Message: 8 Date: Thu, 1 Apr 2010 09:43:02 +0200 From: Aleksandar aleksandar.topuzo...@gmail.com To: Mohammad Khalil eng_m...@hotmail.com Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] IP SLA Message-ID

[c-nsp] IP SLA

Dears we have a customer which uses IPLC (L2 Connection through our network) anyway the link passes through multiple provider i want to be able to measure the delay through my network (we uses xconnect to transport the customer traffic) and there is no IP adressing in between any ideas guys ?

Re: [c-nsp] IP SLA

If it's possible/supported, use CFM (802.1ag) ethernet SLAs. -- Tassos Mohammad Khalil wrote on 23/03/2010 11:20: Dears we have a customer which uses IPLC (L2 Connection through our network) anyway the link passes through multiple provider i want to be able to measure the delay through my

[c-nsp] ip sla echo vrf with df-bit set?

I'm trying to setup a mechanism for ensuring end-to-end MTU in our L3 MPLS VPN network. I'd like to use ip sla tracking to do so and I have setup a monitor: ip sla monitor 99 type echo protocol ipIcmpEcho x.x.x.x request-data-size 1500 vrf XYZ Unfortunately, I cannot find any way to set the

Re: [c-nsp] ip sla echo vrf with df-bit set?

Hi, * Christopher Hunt dharmach...@gmail.com wrote: Unfortunately, I cannot find any way to set the DF bit using ip sla monitor. Anyone know if it's available anywhere or coming soon? Can anyone else think of another strategy? I'm currently running 12.4(22)T on a series of 7200VXRs. Look

Re: [c-nsp] ip sla echo vrf with df-bit set?

[mailto:dharmach...@gmail.com] Sent: Thursday, January 28, 2010 12:05 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] ip sla echo vrf with df-bit set? I'm trying to setup a mechanism for ensuring end-to-end MTU in our L3 MPLS VPN network. I'd like to use ip sla tracking to do so and I have

Re: [c-nsp] ip sla question

On Mon, 2009-10-19 at 15:33 -0700, Alex Wa wrote: Why do we need to specify dst-port as in ip sla 1 udp-jitter dest-ip DEST-PORT even when the ip sla responder doen't have one particular port where it listens to? If you only enable ip sla responder the query device uses control

[c-nsp] ip sla question

Hi guys,   Why do we need to specify dst-port as in   ip sla 1 udp-jitter dest-ip DEST-PORT   even when the ip sla responder doen't have one particular port where it listens to?   thanks in advance to everyone alejandro w. ___ cisco-nsp

Re: [c-nsp] IP SLA / EEM Scripting

. [mailto:pshule...@gmail.com] Sent: Friday, 21 August 2009 12:52 PM To: Aaron Riemer Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] IP SLA / EEM Scripting A perl script with Net:Ping, and Net:Telnet might be easier, especially if you have a server dedicated to device management. Both are fairly

Re: [c-nsp] IP SLA / EEM Scripting

. Ivan http://www.ioshints.info/about http://blog.ioshints.info/ -Original Message- From: Aaron Riemer [mailto:arie...@wesenergy.com.au] Sent: Friday, August 21, 2009 3:27 AM To: cisco-nsp@puck.nether.net Subject: [c-nsp] IP SLA / EEM Scripting Hey Guys, I am hoping to use

[c-nsp] IP SLA / EEM Scripting

Hey Guys, I am hoping to use a combination of IP SLA and EEM to run a script when a certain event occurs. For example we have a cellular router that sometimes requires a reset. We have a backup link so I would like to automate this reset process. What I would like to do is to monitor the

Re: [c-nsp] IP SLA / EEM Scripting

A perl script with Net:Ping, and Net:Telnet might be easier, especially if you have a server dedicated to device management. Both are fairly trivial modules with many examples on line. Have cron run the script every 5(whatever) min. If ping fails, part of the scripts logic is to telnet and

[c-nsp] IP Sla

hi all i configured the following on my router ip sla 200 icmp-echo 4.2.2.2 threshold 50 frequency 5 ip sla schedule 200 life forever start-time now event manager applet FILE event snmp oid 1.3.6.1.4.1.9.9.42.1.2.9.1.7.200 get-type exact entry-op eq entry-val 1 exit-op eq exit-val 2

Re: [c-nsp] IP Sla

: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Mohammad Khalil Sent: Tuesday, July 28, 2009 11:49 To: cisco-nsp@puck.nether.net Subject: [c-nsp] IP Sla hi all i configured the following on my router ip sla 200 icmp-echo 4.2.2.2 threshold 50

Re: [c-nsp] IP SLA accuracy

On Jun 23, 2009, at 12:24 PM, Mikael Abrahamsson wrote: Short answer is no. My experience is that measurements normally varies by several milliseconds, and sometimes much more than that. Correct, it's in the ms range. ---

Re: [c-nsp] IP SLA accuracy

Microseconds level precision is possible with the precision keyword. http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_02.html#wp1064123 -Ozgur --- On Mon, 22/6/09, Jeff Bacon ba...@walleyesoftware.com wrote: From: Jeff Bacon ba...@walleyesoftware.com Subject: [c-nsp] IP SLA

Re: [c-nsp] IP SLA accuracy

On Tue, 23 Jun 2009, Ozgur Guler wrote: Microseconds level precision is possible with the precision keyword. http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_02.html#wp1064123 Setting the reporting to microseconds instead of milliseconds doesn't improve the measurement

[c-nsp] IP SLA accuracy

How accurate is the new(ish) IP SLA measurement system? For local metro links with RT times in the 300-500usec range, can it monitor for variations of 100-200usec in some reasonable fashion? (Yes it can vary that much just dependent on queueing, load, etc. I am just curious what people's

Re: [c-nsp] IP SLA accuracy

On Mon, 22 Jun 2009, Jeff Bacon wrote: How accurate is the new(ish) IP SLA measurement system? For local metro links with RT times in the 300-500usec range, can it monitor for variations of 100-200usec in some reasonable fashion? Short answer is no. My experience is that measurements

[c-nsp] IP Sla + Track does not trigger EEM applet

Hi, i set up a configuration to reset an IPSEC Tunnel : track 1 ip sla 1 reachability delay down 60 up 30 ip sla 1 icmp-echo 1.1.1.1 source-interface Loopback13 ip sla schedule 1 life forever start-time now event manager applet Reset_IPsec_Tunnel event none action 1.0 cli command ena

Re: [c-nsp] IP Sla + Track does not trigger EEM applet

try debug event manager all Dave. anton.schweit...@o2.com wrote: Hi, i set up a configuration to reset an IPSEC Tunnel : track 1 ip sla 1 reachability delay down 60 up 30 ip sla 1 icmp-echo 1.1.1.1 source-interface Loopback13 ip sla schedule 1 life forever start-time now

[c-nsp] IP SLA logging....

Hi, Does anyone know how I can generate as syslog message (either locally or sent to a syslog server) as opposed to a trap? I have the following configuration, running 124-16a Enterprise Base on 3725 router. ! ! logging buffered 16384 debugging ! ip sla monitor logging traps ip sla monitor 2

Re: [c-nsp] IP Sla Configuration

know if you need further info. Arie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Letkeman Sent: Wednesday, November 26, 2008 02:02 AM To: cisco_nsp Subject: [c-nsp] IP Sla Configuration Hello, I have 5 different route's on our 2821 router and I'm

Re: [c-nsp] IP SLA and dyn routes

, 2008 06:12 AM To: Dean Smith Cc: 'cisco-nsp' Subject: Re: [c-nsp] IP SLA and dyn routes I honestly haven't spent enough time with it yet to know all the details but maybe check PfR (aka: OER) to see if can help you out. Rodney On Mon, Aug 25, 2008 at 09:53:41PM +0100, Dean Smith wrote: Sounds

[c-nsp] IP SLA and dyn routes

Hi all, i´m having problem with my SP(run MPLS/BGP) where the the time to converge networks is so high (10 minutes) and they say that are working and will be fix in 3 months aprox. I want anything to do convergence faster for me. I read about IP SLA, but do not find doc related IP SLA x dynamic

Re: [c-nsp] IP SLA and dyn routes

-nsp] IP SLA and dyn routes Hi all, i´m having problem with my SP(run MPLS/BGP) where the the time to converge networks is so high (10 minutes) and they say that are working and will be fix in 3 months aprox. I want anything to do convergence faster for me. I read about IP SLA, but do not find doc

Re: [c-nsp] IP SLA and dyn routes

to decide which one is up/working etc Dean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Everton Diniz Sent: 25 August 2008 21:13 To: cisco-nsp Subject: [c-nsp] IP SLA and dyn routes Hi all, i?m having problem with my SP(run MPLS/BGP

[c-nsp] IP SLA RTT question...

Hi, I don't remember seeing IP SLA-related questions on the list before so I hope this is not off-topic. I setup the following: R1R2R3 R1 configured as IP SLA source/responder to R3. R3 configured as IP SLA source/responder to R1. R2 configured just to route traffic. R1

Re: [c-nsp] IP SLA RTT question...

Try making the destination port of the jitter probe different from the UDP probe. Years ago when I first started using rtr the two probe types would interfere with each other. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net

[c-nsp] IP SLA - dns operation: Error code=4

Hello, I'm testing various aspects of IP SLA, and have been trying to set up an HTTP get url operation - unsuccessfully. My configuration is as follows: ip sla monitor 300 type http operation get url http://www.example.com name-server name-server cache disable threshold 5000 frequency 300 ip

Re: [c-nsp] IP SLA - dns operation: Error code=4

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Giles Coochey Sent: 05 February 2008 10:07 To: cisco-nsp@puck.nether.net Subject: [c-nsp] IP SLA - dns operation: Error code=4 Hello, I'm testing various aspects of IP SLA, and have been trying to set up an HTTP

Re: [c-nsp] IP SLA - dns operation: Error code=4

Giles Coochey wrote on Tuesday, February 05, 2008 11:07 AM: Hello, I'm testing various aspects of IP SLA, and have been trying to set up an HTTP get url operation - unsuccessfully. My configuration is as follows: ip sla monitor 300 type http operation get url http://www.example.com

Re: [c-nsp] IP SLA - dns operation: Error code=4

I had one similar where the source IPs being used from CLI and SLA were different. The CLI source was correctly set to a mgmt loopback which did have access to DNS the internet. The SLA monitor was using a source that didn't - fixed by specifying the source for the SLA probe. That

Re: [c-nsp] ip sla monitor/traceroute source

Hi Rolf, Ok, will give it a try and report back. I'm pretty sure you'll be correct. Now I remember that the ip route statements originally also pointed to a interface, and my systems weren't happy. When I changed it to a next hop/ip it worked perfectly. Thanks,

Re: [c-nsp] ip sla monitor/traceroute source

Hi, Yes, your correct, I did use the same destination. The article first talks about just the next hop, which should go out the interface where that IP's bound to not causing an issue. There was an example in the article about doing I think something similar. Instead of next

Re: [c-nsp] ip sla monitor/traceroute source

Hi Tuc, If it was a PtP interface - such as Serial / Frame or other, then you can safely use the interface as the Destination, however when on a multiaccess medium (such as ethernet), it is more correct to use the 'Next-Hop' address of the device. (even if there is only a crossover cable