[38571] in North American Network Operators' Group
RE: Hosting Failover Question
daemon@ATHENA.MIT.EDU (Rishi Singh)
Thu Jun 7 13:05:45 2001
Message-ID: <4A0CE95CA3F8AE4198E213D807BF0D5B01183687@excnyc001.corp.tradescape.com>
From: Rishi Singh <RSingh@Tradescape.com>
To: 'James DeMong' <James.DeMong@telus.com>,
"Nanog@Merit. Edu (E-mail)" <nanog@merit.edu>
Date: Thu, 7 Jun 2001 12:56:24 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Errors-To: owner-nanog-outgoing@merit.edu
5 seconds is very good if you can attain it. I have two Nokia IP650s running
with VRRP monitored circuits. The firewalls are constantly trading vrrp
packets and firewall table sync state. The fastest failover I've gotten it
down to is about 30 seconds with complete stateful failover.
This has worked well for my applications, which are financial revenue based
trading apps. By the time the trader's screen has frozen, it takes them
about 15 seconds to bang on the keyboard, 5 seconds to get up and scream,
and 10 seconds to call someone, by the time its already failed over ;-).
-----Original Message-----
From: James DeMong [mailto:James.DeMong@telus.com]
Sent: Wednesday, June 06, 2001 12:20 PM
To: Nanog@Merit. Edu (E-mail)
Subject: Hosting Failover Question
I am looking for a Rule of Thumb on failover for hosting, mostly
tcp(webserver), some udp (audio/video streaming) stuff.
My thought is that 5 seconds to failover when a network
element(switch/router/load balancer/FW) fails is reasonable.
How many seconds is reasonable for fail over in such a situation?
Thanks in advance.
__
James DeMong
Network Design Specialist
TELUS Advanced Communications
Phone: (403) 503-3718
Email: James.DeMong@telus.com
