Re: tools and techniques to pinpoint and respond to loss on a path

2013-07-16 Thread Michael DeMan
What I have done in the past, and this presumes you have a /29 or bigger on the peering session to your upstreams is to check with the direct upstream provider at each and get approval to put a linux box diagnostics server on the peering side of each BGP upstream connection you have - default-ro

Re: tools and techniques to pinpoint and respond to loss on a path

2013-07-16 Thread Pete Lumbis
IP SLA + EEM on the 4900. You can have the 4900 run pings/latency tests and then run commands and pipe them to flash when the issue happens. -Pete On Mon, Jul 15, 2013 at 5:18 PM, Andy Litzinger < andy.litzin...@theplatform.com> wrote: > Hi, > > Does anyone have any recommendations on how to pi

RE: tools and techniques to pinpoint and respond to loss on a path

2013-07-16 Thread Andy Litzinger
> From: Blake Dunlap [mailto:iki...@gmail.com] > While any provider will attempt to fix peer / upstream issues as they can, any > SLA you would have is between two points on their private network, not > from point A to point Z that they have no control over across multiple peers > and the public in

RE: tools and techniques to pinpoint and respond to loss on a path

2013-07-16 Thread James Sink
Have you looked into Cisco's OER? -James -Original Message- From: Andy Litzinger [mailto:andy.litzin...@theplatform.com] Sent: Monday, July 15, 2013 2:19 PM To: nanog@nanog.org Subject: tools and techniques to pinpoint and respond to loss on a path Hi, Does anyone hav

Re: tools and techniques to pinpoint and respond to loss on a path

2013-07-15 Thread Blake Dunlap
Personally I would never expect simple routed connectivity across the public internet to be such a high level of reliability, without at least diverse path tunnels running route protocols internally. While any provider will attempt to fix peer / upstream issues as they can, any SLA you would have

Re: tools and techniques to pinpoint and respond to loss on a path

2013-07-15 Thread Jared Mauch
On Jul 15, 2013, at 5:18 PM, Andy Litzinger wrote: > I'd like to be able to collect enough relevant data to pinpoint the trouble > spot as much as possible so I can take it to the ISPs and request a solution. > The blackouts are so quick that it's impossible to log in and get a trace- > he

tools and techniques to pinpoint and respond to loss on a path

2013-07-15 Thread Andy Litzinger
Hi, Does anyone have any recommendations on how to pinpoint and react to packet loss across the internet? preferably in an automated fashion. For detection I'm currently looking at trying smoketrace to run from inside my network, but I'd love to be able to run traceroutes from my edge routers