Re: DHCP, boot server race?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jay Tanner (jt_at_nowhere.net)
Date: 12/30/04 

Date: Thu, 30 Dec 2004 17:16:28 -0500

KM,
Thanks for answering and I'm sorry for not being clear enough.

All system elements are Compact PCI (cPCI) and are plugins in a PICMG
2.16 chassis. This simply means everything is a blade and all blades
are networked via paths that are integral to the chassis backplane. In
this context,
XPe blade server -> a general purpose blade computer on which we will
execute a dedicated function operating under XP Embedded.
boot server -> a similar blade as described above but running a disk
based OS, e.g. XP-Pro or Win Server 2003 and running the RBS packaged
with XP Embedded. This is the same device as "a boot server on a blade"
and it has a static IP.
switch/DHCP server -> a PICNG 2.16 ethernet switch. Such switches
typically include a DHCP server that can assign slot specific IP
addresses. For example, it can be desirable to have a mapping of IP
address to chassis slot number for physical identification of failed blades.

We are using PXE and we do have DHCP as supported by the "switch/DHCP
server" element. The question is whether this device, particularly the
DHCP service, can engage in a race with the RBS if both are booted in
parallel such that a race outcome might be that clients can get IP
addresses but not be served boot images under PXE.

KM wrote:

> Jay,
>
> Before going into analysis of your message could you clarify a few terms you used?
>
> "XPe blade server"?
> "boot server"? (RBS?)
> "a boot server resident on a blade"?
>
> That could be my poor English but I could not interpret your message properly.
>
> If your XPe devices leverage PXe to boot the image, you will need DHCP (or at least BOOTP) server running on the network.
> But you probably knew this as you would have had to set up RBS/DHCP environment for booting the clients.
>

Relevant Pages

  • Re: DHCP, boot server race?
    ... It works rather as Proxy DHCP in the PXE boot scenario. ... The client initial DHCP request has to be responded by DHCP and Proxy DHCP (replies with boot server IP). ... I am not sure how PXe can work if one of the parts is not there. ... This simply means everything is a blade and all blades> are networked via paths that are integral to the chassis backplane. ...
    (microsoft.public.windowsxp.embedded)
  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: SBS 2003 Misconfigured?
    ... DHCP shows up on the server as running. ... The netgear has a setting for the Internet IP which is set to the ... Which, based on the configuration you gave, is part of the problem. ...
    (microsoft.public.windows.server.sbs)
  • RE: DHCP
    ... SBS stops leasing out IP addresses. ... to DHCP. ... Administrative tools ' Server Management. ... go into the ISA console to create and apply a Firewall access rule with the ...
    (microsoft.public.windows.server.sbs)
  • Re: Application Hang
    ... Do not run 2 DHCP servers together, that will create conflicts for the client. ... Under DNS management console is the server listed under Forward lookup zone, if yes with how many entries and which ones? ... I hope this is what you were looking for by way of scope options: ...
    (microsoft.public.windows.server.networking)