Re: Failover solution using BGP

2008-12-31 Thread Florian Weimer
* Naveen Nathan: Of the several solutions presented the two that seem to be simple to implement and guarantee traffic were conditional route advertisements or using more specific routes. One thing you need to consider is what happens if your AS is split. In this case, traffic will probably

Re: Failover solution using BGP

2008-12-31 Thread Roland Dobbins
On Dec 31, 2008, at 11:59 AM, Naveen Nathan wrote: Also they didn't want to subnet the space for the failover location, so it's all or nothing style routing. Have they considered doing GSLB via DNS rather than playing routing games? Seems as if it might answer better, be less complex,

RE: Failover solution using BGP

2008-12-31 Thread Bryant Valencia
If an IBGP link is possible then you could automate this with the proper attributes. Date: Wed, 31 Dec 2008 00:08:32 + From: nav...@calpop.com To: nanog@nanog.org Subject: Failover solution using BGP Hi, I would appreciate insight and experience for the following situation. I have a

Re: Failover solution using BGP

2008-12-31 Thread Florian Weimer
* Roland Dobbins: Have they considered doing GSLB via DNS rather than playing routing games? Seems as if it might answer better, be less complex, et. al. I suspect they want to solve the split brain problem, which would explain the strong, non-negotiable requirement of traffic flow to only

Re: Failover solution using BGP

2008-12-31 Thread Roland Dobbins
On Dec 31, 2008, at 11:36 PM, Florian Weimer wrote: DNS tweaks won't help with that (and to be honest, BGP doesn't address it, either). After all, there ought to be an internal line of communication as well as the external one, and the availability probes can be set up with logic such

Re: Failover solution using BGP

2008-12-31 Thread Doug Schaapveld
On Tue, Dec 30, 2008 at 6:13 PM, Chris Ely c...@internap.com wrote: Conditional advertisements might be what you're looking for: http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a0080094309.shtml I did something just like this recently. Apologies if this is

Leap second tonight

2008-12-31 Thread Kevin Day
Just a reminder that there's a leap second tonight. Last time I watched for what happened on 01/01/2006, there was a little bit of chaos: http://markmail.org/message/cpoj3jw5onzhhjkr?q=%22kevin+day%22+leap+second+reminder+nanogpage=1refer=cnkxb3iv7sls5axu I've been told that some of the

Re: Leap second tonight

2008-12-31 Thread Peter Lothberg
INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS) SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE SERVICE DE LA ROTATION TERRESTRE OBSERVATOIRE DE PARIS 61, Av. de l'Observatoire 75014 PARIS (France) Tel.

Re: Leap second tonight

2008-12-31 Thread Jasper Bryant-Greene
Since leap seconds apply to UTC, won't the leap second be in about 22 minutes? -jasper On 1/01/2009, at 11:41 AM, Kevin Day wrote: Just a reminder that there's a leap second tonight. Last time I watched for what happened on 01/01/2006, there was a little bit of chaos:

Re: Leap second tonight

2008-12-31 Thread Majdi S. Abbas
On Wed, Dec 31, 2008 at 04:41:39PM -0600, Kevin Day wrote: I've been told that some of the causes of these problems are fixed on any reasonably recent ntp distribution, but just in case, you might wanna keep an eye out if you're seeing any weirdness. The worst damage I'd heard from

Re: Leap second tonight

2008-12-31 Thread Kevin Oberman
From: Kevin Day toa...@dragondata.com Date: Wed, 31 Dec 2008 16:41:39 -0600 Just a reminder that there's a leap second tonight. Last time I watched for what happened on 01/01/2006, there was a little bit of chaos:

Re: Leap second tonight

2008-12-31 Thread Peter Lothberg
bash-2.05b# date Thu Jan 1 00:59:58 CET 2009 bash-2.05b# date Thu Jan 1 00:59:59 CET 2009 bash-2.05b# date Thu Jan 1 00:59:60 CET 2009 bash-2.05b# date Thu Jan 1 01:00:00 CET 2009 bash-2.05b# date Thu Jan 1 01:00:01 CET 2009 bash-2.05b# -P

Re: Leap second tonight

2008-12-31 Thread Michael Hallgren

Re: Leap second tonight

2008-12-31 Thread Wil Schultz
At which point my Solaris 10 v490's reboot in unison, lovely. Anyone else see anything interesting? -wil On Dec 31, 2008, at 4:01 PM, Peter Lothberg wrote: bash-2.05b# date Thu Jan 1 00:59:58 CET 2009 bash-2.05b# date Thu Jan 1 00:59:59 CET 2009 bash-2.05b# date Thu Jan 1 00:59:60 CET

Re: Leap second tonight

2008-12-31 Thread Jon Meek
My Solaris 10 boxes are all happy (and did not reboot). I monitor NTP on a number of devices, including one router. The router was off by one second for a while, but is OK after an hour. Everything else was fine immediately. In 2005, our CDMA clock got the leap second between 15:08 and 15:38 EST

RE: Leap second tonight

2008-12-31 Thread Matthew Huff
It looks like clepsydra hasn't been updated: address ref clock st when poll reach delay offsetdisp -~192.5.41.40 .USNO.1 194 1024 37741.15.1938.2 -~130.207.244.240 .GPS. 168 1024 37723.1 11.09 1.3 ~127.127.7.1

Re: Leap second tonight

2008-12-31 Thread Steven M. Bellovin
On Wed, 31 Dec 2008 16:53:57 -0800 Wil Schultz wschu...@bsdboy.com wrote: At which point my Solaris 10 v490's reboot in unison, lovely. Solaris? Or ZuneOS? (See http://www.nytimes.com/2009/01/01/technology/personaltech/01zune.html) --Steve Bellovin,