[AusNOG] Checking peering

Tue Sep 9 18:47:02 EST 2014

It certainly does, good to know and thanks!

Cheers,
Matt
On 09/09/2014 6:38 PM, "Pawel Rybczyk" <nogs at border6.com> wrote:

> Hi Matt,
>
> I'm happy to answer this question for you. The Border 6 NSI solution
> performs constantly active probing via all of configured transits. Each
> probe is routed via the transits with "some pretty sneaky PBR/static
> routing". The probe configuration ensures that when it is sent via
> transit A it will come back via transit A, too. This allows us to know
> exactly what transit actually works fine, and what transit is currently
> misbehaving, without relying on any statistical traffic sampling. Once a
> transit has been flagged as 'bad', we can optionally execute an
> automatic action on the router to shut down the misbehaving transit.
>
> I hope this answers your question.
>
> Cheers,
> Pawel
>
>
> On 09/09/2014 09:43 AM, Matt Ayre wrote:
> > May I ask, how is a blackhole on the internet typically detected by such
> an
> > appliance?
> >
> > It would seem a pretty difficult task in an active/active ISP environment
> > where a fair amount of traffic is asymmetric (ie both upstreams will
> appear
> > impacted just based on traffic levels without some pretty sneaky
> PBR/static
> > routing and geo based KPI monitoring)
> >
> > Cheers,
> > Matt
> >
> > On 9 September 2014 17:09, Pawel Rybczyk <nogs at border6.com> wrote:
> >
> >> Hi Andrew,
> >>
> >> I hope this won't look like I'm invading this thread with commercial
> >> information :) I felt it relevant, though.
> >> My name is Paweł and I'm from the Border 6 company. My colleague,
> >> Mateusz, already mentioned our BGP optimization product earlier in this
> >> thread. I'd only like to add a short note about inbound traffic control,
> >> since you are wondering about it - our NSI solution is already
> >> supporting inbound optimization when needed. We are able to do automatic
> >> AS prepending for cost control and traffic balancing purpose. We can
> >> also automatically shut down the BGP session of a transit in case of
> >> detected blackout. The latter is quite important, since without it you
> >> might have one of your transits malfunctioning (BGP up, but traffic
> >> dropped), causing a general outage on your whole BGP platform, because
> >> your prefixes would still be announced via the faulty link.
> >> Do not hesitate to contact me off-list for more details (or see the
> >> earlier message from Mateusz with a link to our brochure).
> >>
> >> best regards,
> >> Pawel
> >>
> >>
> >> On 09/09/2014 01:51 AM, Andrew Cox wrote:
> >>> I got onto these guys for a chat after seeing some of the info here.
> >>>
> >>> The one thing I missed on this initially is that the Noction system is
> >> only
> >>> capable of controlling the outbound traffic from your network
> >> (controlling
> >>> next-hop for external prefixes) and while it seems quite capable of
> doing
> >>> this, as yet there is no ability to control prefix advertisements to
> your
> >>> upstream transit providers (but they tell me something might be
> available
> >>> end of year).
> >>>
> >>> - Andrew
> >>>
> >>> On 28 August 2014 17:44, Andrew Jones <aj at jonesy.com.au> wrote:
> >>>
> >>>> I can't get away from their ads, they follow me all over the Internet!
> >>>> But yes, I'd be interested in hearing anyone's experiences with it as
> >> well.
> >>>> Andrew
> >>>>
> >>>>
> >>>> On 28.08.2014 17:38, Ross Cheetham wrote:
> >>>>
> >>>>> Hey Luke,
> >>>>>
> >>>>> Be very interested to see how you find this tool. Was talking with
> >>>>> these guys when they were still beta, but never got a chance to have
> a
> >>>>> trial / play.
> >>>>>
> >>>>> Cheers,
> >>>>> Ross
> >>>>>
> >>>>> On 28 August 2014 12:25, Luke Iggleden <luke+ausnog at sisgroup.com.au>
> >>>>> wrote:
> >>>>>
> >>>>>  I was pointed to this a couple of weeks ago. going to give it a
> trial.
> >>>>>>
> >>>>>> http://www.noction.com/ [2]
> >>>>>>
> >>>>>>
> >>>>>> On 28/08/2014 12:14 pm, Richard Ham AusNOG wrote:
> >>>>>>
> >>>>>>  Hi Alex,
> >>>>>>>
> >>>>>>> I haven't got any new or unheard-of solutions here so will be
> >> watching
> >>>>>>> replies too - I use smokeping to alert, however have been trying to
> >>>>>>> figure
> >>>>>>> out how to use conditional advertisements on Ciscos to withdraw
> >> routes
> >>>>>>> to
> >>>>>>> peers that are not behaving. I've run into obstacles since I don't
> >>>>>>> receive
> >>>>>>> global tables from most of my peers and I've messed around with
> using
> >>>>>>> scripts initiated by smokeping to withdraw and re-insert BGP
> >>>>>>> advertisement
> >>>>>>> based on packet loss, however that's purely experimental and I've
> >> since
> >>>>>>> junked the attempt as a bad/error-prone idea.
> >>>>>>>
> >>>>>>> With Regards,
> >>>>>>>
> >>>>>>> Richard
> >>>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of
> >> Alex
> >>>>>>> Samad - Yieldbroker
> >>>>>>> Sent: Thursday, 28 August 2014 12:05 PM
> >>>>>>> To: ausnog at lists.ausnog.net
> >>>>>>> Subject: [AusNOG] Checking peering
> >>>>>>>
> >>>>>>> Hi
> >>>>>>>
> >>>>>>> So after the issue with Vocus recently, I wonder how do people test
> >>>>>>> weather
> >>>>>>> a peer is good or bad.
> >>>>>>>
> >>>>>>> I have had a few issues where my link to a peer is okay, BGP is
> okay,
> >>>>>>> but
> >>>>>>> because of issues downstream my end to end connectivity was down.
> >>>>>>>
> >>>>>>> So now I am looking at how I can monitor this.
> >>>>>>>
> >>>>>>> My basic tool set is ping availability and times
> >>>>>>> Also there is customer feed back
> >>>>>>> And application feedback
> >>>>>>> And msg from ISP (hazard notice etc)
> >>>>>>>
> >>>>>>> I know cisco has some sort of monitoring and bgp tuning that it can
> >> do.
> >>>>>>> But
> >>>>>>> I don't have cisco devices.
> >>>>>>>
> >>>>>>> So what are other people doing/using?
> >>>>>>>
> >>>>>>> Alex
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> AusNOG mailing list
> >>>>>>> AusNOG at lists.ausnog.net
> >>>>>>> http://lists.ausnog.net/mailman/listinfo/ausnog [1]
> >>>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> AusNOG mailing list
> >>>>>> AusNOG at lists.ausnog.net
> >>>>>> http://lists.ausnog.net/mailman/listinfo/ausnog [1]
> >>>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Ross Cheetham / System Operations Manager
> >>>>>
> >>>>> / ross at crucial.com.au
> >>>>>
> >>>>> Crucial Cloud Hosting Office: 1300 884 839
> >>>>>
> >>>>> Suite 1, Level 3, 104-106 Commonwealth St, Surry Hills NSW 2010
> >>>>>
> >>>>> http://www.crucial.com.au [3]
> >>>>>
> >>>>>  [3]
> >>>>>
> >>>>> This e-mail message may contain confidential or legally privileged
> >>>>> information and is intended only for the use of the intended
> >>>>> recipient(s). Any unauthorized disclosure, dissemination,
> >>>>> distribution, copying or the taking of any action in reliance on the
> >>>>> information herein is prohibited. E-mails are not secure and cannot
> be
> >>>>> guaranteed to be error free as they can be intercepted, amended, or
> >>>>> contain viruses. Anyone who communicates with us by e-mail is deemed
> >>>>> to have accepted these risks. Company Name is not responsible for
> >>>>> errors or omissions in this message and denies any responsibility for
> >>>>> any damage arising from the use of e-mail. Any opinion and other
> >>>>> statement contained in this message and any attachment are solely
> >>>>> those of the author and do not necessarily represent those of the
> >>>>> company.
> >>>>>
> >>>>> Links:
> >>>>> ------
> >>>>> [1] http://lists.ausnog.net/mailman/listinfo/ausnog
> >>>>> [2] http://www.noction.com/
> >>>>> [3] http://www.crucial.com.au/
> >>>>>
> >>>>> _______________________________________________
> >>>>> AusNOG mailing list
> >>>>> AusNOG at lists.ausnog.net
> >>>>> http://lists.ausnog.net/mailman/listinfo/ausnog
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> AusNOG mailing list
> >>>> AusNOG at lists.ausnog.net
> >>>> http://lists.ausnog.net/mailman/listinfo/ausnog
> >>>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> AusNOG mailing list
> >>> AusNOG at lists.ausnog.net
> >>> http://lists.ausnog.net/mailman/listinfo/ausnog
> >>>
> >> _______________________________________________
> >> AusNOG mailing list
> >> AusNOG at lists.ausnog.net
> >> http://lists.ausnog.net/mailman/listinfo/ausnog
> >>
> >
> >
> >
> > _______________________________________________
> > AusNOG mailing list
> > AusNOG at lists.ausnog.net
> > http://lists.ausnog.net/mailman/listinfo/ausnog
> >
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20140909/b2df2513/attachment.html>