I have seen an IPSLA HTTP track run on the peering router that executes EEM
script to shutdown neighbor or physical interface when IPSLA starts
receiving timeouts and track is down. Only thing I don't like about this
approach is the logic and state becomes somewhat reliant on the site being
tracked. We used google.com because we would know pretty quick if that site
went down ;)
Marc Edwards
CCIE #38259
On Thu, Jun 27, 2013 at 6:05 AM, gaston brait <gbrait_at_hotmail.com> wrote:
> I work for a company with 2 datacenter connected via a dark fiber and they
> have an IBGP peership between them.Both datacenter have EBGP peers to 2
> different carriers. Carrier A is the preferred one.The problem is that we
> have
> had several incidents where carrier A has problems on their cloud, but the
> BGP
> peer with us never goes down and we continue to recieve prefix from
> them.When
> this happens we lose all internet connectivity and we need to manually
> switch
> to carrier B.Is there any way to automate this process? Maybe track an
> internet route and if it is unreachable bring the peer down?
> Thanks,
> Regards,
> Gaston
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Jun 27 2013 - 06:36:14 ART
This archive was generated by hypermail 2.2.0 : Mon Jul 01 2013 - 06:58:42 ART