This section describes the known OS provisioning (deployment) issues.
OS deployments of Red Hat or SUSE Linux might time out or stop due to a known issue with the spanning tree setting on a network switch.
Workaround: Disable spanning tree on the switch or the switch ports used for the management server and the target servers provisioning network connections.
OS deployment of Red Hat Linux 3.0 Update 2 might stop and enter interactive mode due to a time out issue.
Workaround: Use Update 3 or later.
When using the Load OS wizard in the browser interface, the Exclude Server field does not work when you enter servers to be excluded from being provisioned. This feature is not available from the browser interface.
Workaround: Use the load server command from the command line interface.
The Load OS Wizard does not make it clear why the user has to enter the hostname and configuration twice.
The user is prompted for the hostname in two of the wizard steps:
The first prompt is for the hostname used during the installation process
The second prompt for hostname value that is to be used when the installation is complete
These values might or might not be the same.
Solaris 10 does not install the dhcpd daemon in /usr/sbin/ as did earlier versions of Solaris, but instead Solaris 10 installs the dhcpd daemon in /usr/local/sbin/. As a result, if the machine is rebooted or you kill the dhcpd daemon, the dhcpd daemon cannot be restarted.
Workaround: Every time the Solaris management server is rebooted or shutdown, you must enter the following command on the management server after it boots:
/opt/SUNWscs/sbin/s_dhcp_config.pl -e -I interface |