Solaris OS Deployment Job Times Out or Stops

If you attempt to load a Solaris OS profile and the OS Deploy job times out or stops, check the output in the job details to ensure that the target server completed a PXE boot. For example:

PXE-M0F: Exiting Broadcom PXE ROM.
      Broadcom UNDI PXE-2.1 v7.5.14
     Copyright (C) 2000-2004 Broadcom Corporation
     Copyright (C) 1997-2000 Intel Corporation
     All rights reserved.      
CLIENT MAC ADDR: 00 09 3D 00 A5 FC  GUID: 68D3BE2E 6D5D 11D8 BA9A 0060B0B36963
     DHCP.

If the PXE boot fails, the /etc/dhcpd.conf file on the management server might have erroneous network interface connection entries, which can occur if incorrect information is specified during the N1 System Manager configuration process.

The best diagnostic tool is to open a console window on the target machine and then run the deployment. See Connecting to the Serial Console for a Managed Server in Sun N1 System Manager 1.3 Discovery and Administration Guide.

If you suspect that the /etc/dhcpd.conf file was configured incorrectly, perform the following steps to modify the configuration.

1. Log in to the management server as root (su - root).

2. Inspect the dhcpd.conf file for errors.

3. If errors exist that need to be corrected, stop N1 System Manager and rerun the configuration process as described in Configuring the N1 System Manager in Sun N1 System Manager 1.3 Installation and Configuration Guide. Ensure that you specify the correct management server Ethernet port for the N1 System Manager management network and provisioning network.

4. When the configuration process has completed and N1 System Manager has restarted, load the OS profile on the target server.