Chapter 4 Documentation Issues

This chapter describes known documentation problems. For documentation issues identified too late to be included in these release notes, refer to the Solaris 9 4/04 Release Notes at http://docs.sun.com/db/doc/817-3804.

The following documentation issues have been added to this chapter since the Solaris 9 4/04 Beta Release Notes was published on http://docs.sun.com.

• Document Affected: Solaris 9 4/04 Installation Guide

• Document Affected: Sunscreen 3.2 Configuration Examples Manual

• Document Affected: LDAP Naming Services Setup and Administration in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)

• Document Affected: Administering DHCP (Task) in System Administration Guide: IP Services

Document Affected: Solaris 9 4/04 Installation Guide

Descriptions of naming conventions for creating RAID-1 volumes with the custom JumpStart^TM installation method in the Solaris 9 4/04 Installation Guide are inadequate. If RAID-1 volumes are named incorrectly, the RAID-1 volume might not be created during the installation.

When you use the custom JumpStart installation method to create RAID-1 volumes (mirrors) and RAID-0 volumes (submirrors), you can let the software detect and assign volume names to mirrors, or you can assign the names in the profile. If you let the software detect the names, the software assigns the first volume number that is available. If you assign names in the profile, assign mirror names ending in zero so that the installation can use the names ending in 1 and 2 for submirrors. If you assign numbers incorrectly, the mirror might not be created. For example, if you specify a mirror name with a number that ends in 1 or 2 (d1 or d2), the JumpStart program fails to create the mirror if the mirror name is a duplicate of a submirror's name

In the following profile example, the mirror is assigned the first volume numbers that are available. If the next available mirror ending in zero is d10, then the names d11 and d12 are assigned to the submirrors.

filesys                 mirror c0t0d0s1  /

In the following profile example, the mirror number is assigned in the profile as d30. The submirror names are assigned by the software based on the mirror number and the first available submirrors. In this example, the submirrors are named d31 and d32.

filesys                 mirror:d30 c0t1d0s0 c0t0d0s0  /

Document Affected: Sunscreen 3.2 Configuration Examples Manual

In the chapter, “Using High Availability (HA)”, sections 1b and 4b, on pages 72 and 73, should read as follows:

• Section 1b:

  If it does not already exist, configure the HA heartbeat interface.

  For bos-screen1 in this example, use the following command:

  # echo "10.0.4.1" > /etc/hostname.hme3

• Section 4b:

  If it does not already exist, configure the HA heartbeat interface.

  For bos-screen2 in this example, use the following command:

  # echo "10.0.4.2" > /etc/hostname.hme3

Document Affected: LDAP Naming Services Setup and Administration in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP)

References to the use of the ldapclient command options in the “LDAP Naming Services Setup and Administration” section of the System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) are incorrect. For all Solaris 9 releases, the command syntax should be changed to the following:

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

Document Affected: Administering DHCP (Task) in System Administration Guide: IP Services

The section, “Creating DHCP Options and Macros for Solaris Installation Parameters”, should include the following information regarding DHCP Vendor Options Size Limitations:

Note that the sum total of the values assigned to all the options in a macro must not exceed 255 bytes, including the option codes and length information. This limit is dictated by the DHCP protocol.

Generally, you should pass the minimum amount of vendor information needed. You should use short path names in options that require path names. If you create symbolic links to long paths, you can pass the shorter link names.

Document Affected: Using the CIM Object Manager in Solaris WBEM Developer's Guide

Several patches require that the CIM Object Manager be started manually, after the patches have been applied. The following is a list of those patches:

To restart the CIM Object Manager, follow these steps:

# /etc/init.d/init.wbem stop

# /etc/init.d/init.wbem start

For more information about stopping and restarting the CIM Object Manager, see “Stopping and Restarting the CIM Object Manager,” in the Solaris WBEM Developer's Guide.