[dhcwg] Defining failover scenario
"Drew Baron" <drewba@microsoft.com> Mon, 08 October 2001 23:56 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04288; Mon, 8 Oct 2001 19:56:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21823; Mon, 8 Oct 2001 19:55:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21803 for <dhcwg@optimus.ietf.org>; Mon, 8 Oct 2001 19:55:35 -0400 (EDT)
Received: from inet-vrs-04.redmond.corp.microsoft.com (mail4.microsoft.com [131.107.3.122]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA04279 for <dhcwg@ietf.org>; Mon, 8 Oct 2001 19:55:33 -0400 (EDT)
Received: from 157.54.1.52 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 08 Oct 2001 16:55:06 -0700
Received: from red-msg-12.redmond.corp.microsoft.com ([157.54.2.26]) by inet-imc-06.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 8 Oct 2001 16:55:05 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5739.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------InterScan_NT_MIME_Boundary"
Date: Mon, 08 Oct 2001 16:55:05 -0700
Message-ID: <905568611548FF439A27CB4F41D273E9CAD17C@red-msg-12.redmond.corp.microsoft.com>
Thread-Topic: Defining failover scenario
Thread-Index: AcFQVKY/nVPp8FogTgC02r3GEEMYnA==
From: Drew Baron <drewba@microsoft.com>
To: dhcwg@ietf.org
X-OriginalArrivalTime: 08 Oct 2001 23:55:05.0698 (UTC) FILETIME=[A7469420:01C15054]
Subject: [dhcwg] Defining failover scenario
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
The failover draft <draft-ietf-dhc-failover-09.txt> lists the following as a challenging scenario: 3.4.2. Network partition where DHCP servers can't communicate but each can talk to clients: "First, due to a network failure, the primary and secondary servers cannot communicate. As well, some of the DHCP clients must be able to com- municate with the primary server, and some of the clients must now only be able to communicate with the secondary server." The phrase 'some of the clients' is tripping me up. I'm struggling to envision the scenario needed to end up in this state. Can anyone provide a concrete example of an environment that this could occur in? How do I end up with clients that are on the same segment that cannot reach both servers? Thanks, -Drew Baron
- [dhcwg] Defining failover scenario Drew Baron
- RE: [dhcwg] Defining failover scenario Bernie Volz (EUD)
- Re: [dhcwg] Defining failover scenario Ted Lemon