Possible Causes for Distribution and Deployment Failure

OS deployments might fail or fail to complete if any of the following conditions occur:

• The target RSC technology server was not powered off before discovery was run. RSC servers must remain powered off until discovery is complete and discovery has been confirmed by using the show server command. See Discovery of RSC Servers.

• Partitions are not modified to suit a Sun Fire V40z or SPARC V440 server. See To Modify the Default Solaris OS Profile for a Sun Fire V40z or a SPARC V440 Server in Sun N1 System Manager 1.3 Operating System Provisioning Guide.

• Scripts are not modified to install the driver needed to recognize the Ethernet interface on a Sun Fire V20z server. See To Modify a Solaris 9 OS Profile for a Sun Fire V20z Server With a K2.0 Motherboard in Sun N1 System Manager 1.3 Operating System Provisioning Guide.

• DHCP is not correctly configured. See Solaris Deployment Job Times Out or Stops.

• OS profile installs only the Solaris Core System Support distribution group. See Solaris OS Profile Installation Fails.

• The target server cannot access DHCP information or mount distribution directories. See Invalid Management Server Netmask.

• The management server cannot access files during a Load OS operation. See Restarting NFS to Resolve Boot Failed Errors.

• The Linux deployment stops. See Linux Deployment Stops.

• The Red Hat deployment fails. See Red Hat Linux OS Profile Creation Fails.

Use the following graphic as a guide to troubleshooting best practices. The graphic describes steps to take when you initiate provisioning operations. Taking these steps will help you troubleshoot deployments with greater efficiency.