Product documentation
Citrix Provisioning
Current Release 2402 LTSR 2311 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR 7.15
View PDF

Booting through a router

September 8, 2020
Contributed by: 
E

You can boot target devices through a network router. This allows the Provisioning Server to exist on a different subnet from the target device. Since conditions vary from customer to customer, adjustments may be needed for different network configurations.

The configuration shown in the diagram below separates the Provisioning Server from the target device by using a Windows 2000 Server platform acting as a router.

Network router boot

Configuring for DHCP

In this configuration, a DHCP server must be active on the local subnet (197.100.x.x) of the target device. In the configuration example above, the DHCP service is running on the same machine acting as a router between the two subnets, though it is not mandatory that the DHCP service actually runs on the router itself. This DHCP server provides the IP address and the PXE boot information to the target device.

Configure the DHCP service to provide valid IP addresses to any target device booting on the local subnet (197.100.x.x).

In order to provide the PXE boot information to the target device, configure the following options in your DHCP server :

  1. DISABLE Option 60 (Class ID).
  2. Enable Option 66 (Boot Server Host Name) – Enter the IP address of the TFTP Server. In this configuration, the value is 10.64.0.10.
  3. Enable option 67 (Boot file name) – Enter the name of the boot file. For a standard configuration, the filename is ARDBP32.bin.

Configuring the Provisioning Services for PXE

Using the Console, configure the bootstrap settings to use the Gateway and Subnet mask fields. These fields should reflect the gateway and subnet to be used by the target device. In this case, they are 197.100.x.x for the gateway, and 255.255.255.0 for the netmask.

Verify the TFTP service is running on the Provisioning Server.

The PXE Service on the Provisioning Server in the above configuration is not necessary since options 66 & 67 in the router’s DHCP service provide the same information to the target device. You can stop the PXE Service on the Provisioning Server if you have no target devices on the Provisioning Server subnet needing its functionality. The same is true for any DHCP service running on the Provisioning Server itself.

Running PXE and DHCP on the Same Computer

If PXE and DHCP are running on the same Provisioning Server, an option tag must be added to the DHCP configuration. This tag indicates to the target devices (using PXE) that the DHCP server is also the PXE boot server. Verify that option tag 60 is added to your DHCP scope. Provisioning Services setup automatically adds this tag to your scope provided that the Microsoft DHCP server is installed and configured before installing Provisioning Services. The Configuration Wizard sets-up the Tellurian DHCP Server configuration file if you use the wizard to configure Provisioning Services.

The following is an example Tellurian DHCP Server configuration file which contains the option 60 tag.

pre codeblock max-lease-time 120; default-lease-time 120; option dhcp-class-identifier "PXEClient"; subnet 192.168.4.0 netmask 255.255.255.0 { option routers 192.168.123.1; range 192.168.4.100 192.168.4.120; }. <!--NeedCopy-->

Booting through a router
September 8, 2020
Contributed by: 
E
September 8, 2020
Contributed by: 
E

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.