PXE Machines cannot contact the OSIM server on a different subnet.

Products

• CA Automation Suite for Data Centers - Configuration Automation
• CA Client Automation - Asset Management
• CA Client Automation - IT Client Manager
• CA Client Automation
• CA Client Automation - Remote Control
• CA Client Automation - Asset Intelligence
• CA Client Automation - Desktop Migration Manager
• CA Client Automation - Patch Manager
• CA Server Automation

Issue/Introduction

Description

This document describes the configuration changes required, when the PXE client, DHCP and the OSIM server are on different subnets .

Solution

Consider the following example where the DHCP, PXE Machines and the OSIM server are in different subnets/VLANs.

<Please see attached file for image>

In this example:

• The DHCP server is on VLAN 10 with a subnet of 10.1.X.X/16
• Boot Server/OSIM Server is on VLAN 20 with a subnet of 10.2.X.X/16
• PXE Machines are on VLAN 30 with a subnet of 10.3.X.X/16

The PXE clients can contact the DHCP server and initiate the DORA process. The Boot Server acts as a DHCP proxy and listens for all DHCP broadcasts.
When the boot server receives a DHCP broadcast from a PXE client, it responds to it and provides the server address that the PXE client needs to use as well as the location of the 'bootfile'. However, the routers connecting these VLAN's do not route the PXE DHCP broadcasts to the Boot Server.

To over-come this, you would need to configure 'IP Helper' (or something similar) on the routers connecting the VLANs to route the PXE DHCP broadcasts to the Boot Servers.

For Cisco routers following is the 'IP Helper' Configuration:
IP helper-address <address of the boot server>

In addition if you are using 'WinPE' boot images you will also need to forward UDP packets over port 4011 using the following command:
IP forward-protocol UDP 4011

Environment

Release:
Component: DTSVMG