North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: IP failover/migration question.

  • From: Andrew Warfield
  • Date: Sun Jun 11 23:56:40 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=HMBcT7OlTDrQm0kMcbQSn5auL6aLf3EXVeyNxizdAuM0r8tkMy7HjwG7UZuiD43c8KJemJPuFLVMHTaDd4OEjfPOF8LRfnPNZx7OMZZMbj1P1K/LHHdoQ9UxQhQEuZ+tkS3nG4tTUHetfnz9K8grwMknB/mYupbHxq5cGml9JAE=

I think there is some cisco magic you could do with 'dial backup'... you
may even be able to rig this up with an ibgp session (even if that goes
out over the external provider) to swing the routes.

NOTE: this could make your site oscillate if there are connectivity issues
between the sites, it could get messy FAST, and it could be hard to
troubleshoot. Basically look before you leap :)

This link may b e of assistance:
This link asks me for a login...

to get greed into it.. are you sure you want to be 'stuck' with a single
carrier? :) What if the carrier dies wouldn't you want redundant carrier
links as well?
I'd love a multi-ISP solution.  I just assumed that anything involving
more than a single upstream AS across the two links would leave me
having to consider BGP convergence instead of just IGP reconfig.  I
didn't presume that that would likely be something that happened in
seconds.  If there's a fast approach to be had here, I'd love to hear