Frequently Asked Questions

1. How do I Switch to a Static IP System if I Don't Have Access to the System's Desktop?

The following steps can be used to configure a wired network interface to have a static IP address.

Run the following series of commands:

# svcadm disable network/physical:nwam
# svcadm enable network/physical:default
# echo <IP_addr> > /etc/hostname.<ifname>
# echo <hostname> > /etc/nodename

Run the following command:
```
# vi /etc/hosts
```
And, append this line to the file:
```
<IP_addr> <hostname> <hostname>.local loghost
```
Then, edit the entries for the loopback addresses, so that these entries contain only 'localhost' as the alias. In other words, edit the line for the '::1' entry to show the following:
```
::1 localhost
```
And, edit the line for the 127.0.0.1 entry to show the following:
```
127.0.0.1 localhost
```
Run the following command:
```
# vi /etc/netmasks
```
And, append this line to the file:
```
<network> <netmask>
```

Run the following commands:

# ifconfig <ifname> plumb
# ifconfig <ifname> <IP_addr> netmask <netmask> up

If you use DNS to resolve hostnames, perform these additional steps:
1. Configure the file, /etc/resolv.conf(4), to work with the DNS servers for your network. You may need to consult your network administrator for this information.
  An example of the /etc/resolv.conf file may look like this:
```
domain mycompany.com
       nameserver 192.168.1.118
       nameserver 192.168.2.220 
```
2. Run the following command:
```
# cp /etc/nsswitch.dns /etc/nsswitch.conf
```
Configure a default route:
If your network does not have a discoverable default router, you need to set a static default route on your system. You may need to consult your network administrator for this information.
To set up a static default route, add your network's default router IP address to the /etc/defaultrouter(4) file as shown in the following commands:
```
# echo <default_route_IP_addr> >> /etc/defaultrouter
# route add default <default_route_IP_addr>
```

2. Does my SPARC Client Support WAN boot?

The automated installer requires WAN boot support for SPARC clients. You can check whether your client open boot prompt supports WAN boot by checking whether network-boot-arguments is a valid variable that can be set in the eeprom. If the variable network-boot-arguments is displayed, or if it returns the output network-boot-arguments: data not available, the open boot prompt supports WAN boot installations.

# eeprom | grep network-boot-arguments
network-boot-arguments: data not available

If there is no output to the above command, then WAN Boot is not supported.

3. Where do I find the AI ISO Image that I Need?

Download an AI ISO image for x86 clients or for SPARC clients from http://www.opensolaris.com/get/. The automated installer will use this AI ISO image to install the OpenSolaris OS to your client systems.

Store the AI ISO image on your local file system. For example, store the image at /export/aiimages/osol-0906-ai-x86.iso.

4. How do I Modify the Manifest File to Point to Repository of my Choice?

You can modify the following default repository information in the manifest file:

<ai_pkg_repo_default_authority>
     <main url="http://pkg.opensolaris.org" authname="opensolaris.org"/>
</ai_pkg_repo_default_authority>

If your IPS repository is pkg.mycompany.com and the authorization is mycompany.com, change pkg.opensolaris.org to pkg.mycompany.com and opensolaris.org to mycompany.com.

<ai_pkg_repo_default_authority>
     <main url="http://pkg.mycompany.com" authname="mycompany.com"/>
</ai_pkg_repo_default_authority>

5. How do I Install a Particular OpenSolaris Development Build?

Development builds of the OpenSolaris operating system are available in-between releases. See http://www.opensolaris.org/os/downloads/.

The build number or release of the AI ISO image that you specify in the installadm create-service command with the -s option must be the same build number or release of the OpenSolaris operating system that you specify in the AI manifest.

Check the build number or release for the AI ISO image when you download the image.

In the AI manifest, if you want to install a specific version of the OpenSolaris OS, you can specify the version in the package entire. The IPS repositories include the full FMRI for each version of a package. Use the FMRI string to specify a specific version of the package, entire, in the AI manifest.

The following example specifies that OpenSolaris build 111 be installed to the client.

<ai_manifest name="ai_packages">
     <ai_install_packages>
         <pkg name="[email protected]"/>
         <pkg name="SUNWcsd"/>
         <pkg name="SUNWcs"/>
         <pkg name="babel_install"/>
         <pkg name="openoffice"/>
         <pkg name="SUNWTcl"/>
     </ai_install_packages>
     <ai_uninstall_packages>
         <pkg name="babel_install"/>
         <pkg name="slim_install"/>
     </ai_uninstall_packages>
</ai_manifest>

6. How do I Locate the Default AI Manifest for an Install Service?

The default AI manifest for each install service is called default.xml. This file is located at /var/ai/<port>/AI_data, where <port> is the port number of the install service. You can use the following procedure to locate this file.

Find the name of the install service that has the default manifest that you want to modify.
The name of the install service is the name that you provided in the installadm create-service command when you created the install service. If you didn't provide an install service name, the installadm create-service assigned a service name for your service.
You can view a the list of enabled install services on your subnet by using the following command:
```
# /usr/sbin/installadm list
```
Find the port number where this install service is running. You can get your port number using the following command, where <svc_name> is the service name.
```
# svccfg svc:/system/install/server:default listprop AI<svc_name>
```
For example, if the service name is 0906sparc, you can run the following command to get the properties of the 0906sparc:
```
# svccfg svc:/system/install/server:default listprop AI0906sparc
```
Extract the port number from the value, txt_record.

Note - Do not modify the default AI manifest file. You can, however, copy this file and create a new default manifest for an install ervice. For instructions, see How to Replace the Default AI Manifest.

7. How Can I Cleanup a Failed Service?

If installadm create-service fails to create an install service, use the following procedures to clean up.

Run installadm delete-service to remove the failed install service:
```
# installadm delete-service [-x] svcname
```
If that command fails with the following message:
```
The specified service does not exist: <svcname>
```
Try the following procedure:
1. Check if the automated installer webserver had been started for the service.
  First, search for the port number used for the webserver by finding the dns-sd process associated with webserver. An example of how to do this search by using the ps(1) command, and the resulting output, is as follows:
```
# ps -ef | grep dns-sd | grep " svc2 " \
root 11216 1 0 Apr 15 pts/2 0:00 \
/usr/bin/dns-sd -R svc2 _OSInstall._tcp local \
46502 aiwebserver=192.168.2.1
```
2. Kill this process, as in this example:
```
# kill -9 11216
```
  The example output shows that the webserver for the serivce, svc2, is being served off of port 46502.
3. Now search for the webserver process that's associated with this port number, and kill that process. See the following example:
```
# ps -ef | grep installadm/webserver | grep 46502 \
root 11026 1 1 Apr 15 pts/2 71:35 \
/usr/bin/python2.4 \
/usr/lib/installadm/webserver -p 46502 /var/ai/46502
# kill -9 11026
```
4. Now, remove the data directory for the install service, which also has that port number found above, 4652, it its path:
```
# rm -rf /var/ai/46502
```
If you want to delete the target image path directory that was specified for the failed install service, remove the <targetdir> that you use in the installadm create-service command:
```
# rm -rf targetdir
```

As a further step, see 8. How do I Cleanup DHCP Configurations for a SPARC Install Service?

8. How do I Cleanup DHCP Configurations for a SPARC Install Service?

When you run the installadm create-service command with the -i and -c options, the DHCP server is configured . To cleanup the DHCP configurations for a failed or deleted SPARC install service, log into the DHCP Manager and manually remove the DHCP macros for the install service. And, remove any IP addresses that were configured when you created the install service.

For more information, see the dhcpmgr(1M) man page.

9. How do I Run Automated Installations in Debug Verbose Mode?

You can run the installer in verbose debug mode, in order to capture more information about the installation in the install_log file.

When you use the installadm create-service command to create an install service, or you use the installadm create-client command to set up a custom client, these commands populate the install configuration file. For x86 systems, this file is the GRUB menu.lst file. For SPARC systems, this file is the install.conf file. In order to enable debug mode, you need to set the install_debug option to enable in this install configuration file, as per the following instructions.

For x86 systems, the menu.lst configuration file is created in the /tftpboot/ directory with one of the following filename formats:
- If you used the installadm create-service -n <service_name> command, the filename is menu.lst.<service_name>.
- If you used the installadm create-client -e <mac> command, the filename is menu.lst.01<mac>.
In this file, the options are provided as kernel parameters, such as the following:
```
kernel$ ... -B install_media=...,livessh=enable,install_debug=enable
```
Since the install_debug option in the above example is set to enable, the installer will run in verbose debug mode.
For SPARC systems, the install.conf file is populated in the ai_image_dest directory when an install service is created by using an installadm create-service command, such as the following:
```
# installadm create-service [-n svc_name] [-s ai_iso_image] ai_image_dest
```
In the install.conf file, the options are defined as name-value pairs, such as the following:
```
$ cat <ai_image_dest>/install.conf
...
install_debug=enable
...
```
Since the install_debug option in the above example is set to enable, the installer will run in verbose debug mode.

10. How do I Enable Remote Access to an AI Client by Using `ssh`?

You can enable network access to an automated install client by using ssh. You can use this access to remotely observe an installation process.

Enable this access by setting the option, livessh, to enable in the installation configuration file. When this access is enabled, you can log in to the AI client by using the username and password, “jack/jack”.

For x86 systems, the menu.lst configuration file is created in the /tftpboot/ directory with one of the following filename formats:
- If you used the installadm create-service -n <service_name> command, the filename is menu.lst.<service_name>.
- If you used the installadm create-client -e <mac> command, the filename is menu.lst.01<mac>.
In this file, the options are provided as kernel parameters, such as the following:
```
kernel$ ... -B install_media=...,livessh=enable,install_debug=enable
```
The livessh option is this excerpt is set to enable.
For SPARC systems, the install.conf file is populated in the ai_image_dest directory when an install service is created by using an installadm create-service command such as the following:
```
# installadm create-service [-n <service_name>] [-s <ai_iso_image>] <ai_image_dest>
```
In the install.conf file, the options are defined as name-value pairs, such as:
```
$ cat <ai_image_dest>/install.conf
...
livessh=enable
...
```
The livessh option is this excerpt is set to enable.

11. How do I Boot the Install Environment Without Starting an Installation?

You can boot to single-user mode using -s as an option to the kernel. Use the following instructions:

Caution - Make sure to use the -s option so that an installation will not begin.

Specify the -s option as follows:
- For a SPARC system, use the following command:
```
OK boot net:dhcp -s
```
- For an x86 system, edit the GRUB menu and add the -s option to the kernel line.
Login as root and run the following command:
```
svcadm disable auto-installer
```

12. How do I Generate Encrypted Passwords?

One method of generating encrypted passwords for the OpenSolaris OS is to create a user of the intended name and password on the OpenSolaris OS, copy the password from the /etc/shadow file between the 1st and 2nd colons of the user's record, and add that information into the 'userpass' or 'rootpass' values in the SC manifest.

See How to Create Custom SC Manifest Files.

13. Is the Automated Installer Backwards Compatible?

No, the OpenSolaris 2009.06 automated installer is not backward compatible with ISO images or automated installer tools from earlier OpenSolaris releases. Use OpenSolaris 2009.06 automated installer tools and procedures with the OpenSolaris 2009.06 operating system and 2009.06 ISO images only.

14. How is the default target disk selected?

You can use the <ai_target_device> tag to specify a particular target disk on which to install the OpenSolaris OS. See Defining an Install Target. If you do not specify a target disk, the automated installer chooses a default target for installing the OpenSolaris OS.

The default target disk is selected as follows:

The installer gets the recommended size for installing the OpenSolaris OS from the AI libraries. Currently, the recommended size is 12 GB.
The installer searches for available disks on the client.

Note - The installer selects only the following types of disks:
- For SPARC clients, the installer searches for disks with a VTOC label.
- For x86 clients, the installer searches for Solaris partitions.
When the first disk is found, the installer checks the size of that disk.
- If the size is greater than or equal to the recommended size, the installer selects the disk and returns to the installation procedure.
- If the size is less than the recommended size, the installer goes to the next disk to check the size.
If there is no match, the automated installation fails.