Solaris 10 7/07 HW Release Notes

Before You Begin

This section contains critical installation issues that you need to be aware of before installing or upgrading to Solaris 10 OS. These issues might have an impact that would prevent installation or upgrades from completing successfully. If bugs in this section apply to your system, you might need to perform the recommended workarounds before you install or upgrade.

Installation Change for the Solaris Companion DVD

When you are installing the Solaris OS, the Companion DVD is not available to be installed with the Solaris installation program. Use the pkgadd(1M) command to install the Solaris Companion DVD. For detailed installation instructions, see the README file on the Companion DVD.

Correct Solaris Data Encryption Supplement Required for Use of Longer Key Lengths on Solaris 10 Updates

When you install the Solaris 10 7/07 HW release and you wish to access longer key lengths for use with data encryption, you must use the Solaris Data Encryption Supplement packages that corresponds to Solaris 10. The supplement is delivered in the SUNWcry and SUNWcryr packages that are available for download from:

http://www.sun.com/download/

To bring these packages up to the same patch level as your current update, you will have to install the appropriate patch:

Patch ID 118562-05 or a later revision for SPARC based systems
Patch ID 118563-04 or a later revision for x86 based systems

To determine your current patch level, use showrev -p.

Additional Procedures Required When Installing Patches for Solaris 10 7/07 HW Release

The following patches are applied to resolve problems that were reported in CR 6277164 and CR 6214222:

Patch ID 119366-05 for SPARC based systems
Patch ID 119367-05 for x86 based systems

The sections that follow provide further steps that you must perform to completely resolve the reported problems.

Resolving Issues With the GNOME Display Manager (6277164)

Note –

Perform this procedure before you use the GNOME Display Manager (GDM) as your login program, or if you have already enabled GDM as your login program. Otherwise, you can skip this procedure.

When applying the patch, load new values into the GDM configuration files. Then restart the GDM application.

To load the new values into the configuration file, choose one of the following options.
- Copy the /etc/X11/gdm/factory-gdm.conf file to the /etc/X11/gdm/gdm.conf file.
  
  Perform this step if you have not made any modifications to the gdm.conf file. Then you can start the GDM application.
- Manually merge the differences in the factory-gdm.conf file into the gdm.conf file.
  
  Perform this step if you have modified the gdm.conf file and want to retain your modifications.
  
  When merging files, copy the values for the following commands from the factory-gdm.conf file to the gdm.conf file. These commands enable you to obtain the best OS performance.
  - RebootCommand
  - HaltCommand
  - SuspendCommand
  - DefaultPath
  - RootPath
  - GraphicalTheme
To restart GDM, perform the following steps:
1. Become superuser.
2. Issue the following command:
  # svcadm disable application/gdm2-login
3. In the console that is now displayed, press Return to display a command prompt.
4. To restart GDM, issue the following command:
  # svcadm enable application/gdm2-login

Sun Fire V250 Server Installation

The SUNWCXall software metacluster must be installed on a Sun Fire V250 Server.

NFS Version 4 Introduces New Prompt at First System Boot

Solaris 10 OS uses NFS Version 4 (NFSv4) as the default distributed file system mechanism. In NFSv4, file user and group attributes are exchanged as strings of the form “user@domain” and “group@domain,” respectively.

The domain portion of the string should be common between client and server. This information is automatically derived from the system's name service domain name. However, in certain cases, the derived domain might not match between client and server. This mismatch might typically occur in environments where either of the following circumstances is true:

The DNS TXT record is not used.
Multiple administrative domain boundaries are crossed.

If domain information between client and server does not match, NFSv4-accessed files might appear to be owned by “nobody.”

To ensure proper configuration, on the first system boot the system now prompts you for a domain to use for NFSv4. Answer “no” to this prompt if one of the following configurations describes your deployment:

Your deployment utilizes the DNS TXT record to configure the NFSv4 domain.
Your deployment has a single (flat) administrative domain.

Custom JumpStart and Advanced Installations

Environments that use the Custom JumpStart^TM method to perform unattended system installations require minimal tuning to suppress the first boot prompts.

A sample script, set_nfs4_domain, is provided in the Solaris 10 distribution media and is located in the ${CDrom_mnt_pt}/Solaris_10/Misc/jumpstart_sample directory. A copy of this script should be modified to set the NFS4_DOMAIN variable to site-specific needs and be called from within JumpStart's finish script. The target system's NFSv4 domain is therefore preconfigured as part of the JumpStart finish phase, and thus suppresses any first boot prompts.

Follow these steps to perform unattended installations:

Create a copy of the set_nfs4_domain script in the same directory as your JumpStart's finish.sh scripts.
Edit the script and set the NFS4_DOMAIN variable to your specific needs.
Edit your finish.sh script and append a call to set_nfs4_domain.
Perform the JumpStart installations as usual.

For further details, refer to the sysidconfig(1M), sysidtool(1M), nfsmapid(1M), and nfs(4) man pages. See also the System Administration Guide: Network Services.

Default Size of `/var` File System Inadequate for Extra Value Products

The default size of the /var file system might be insufficient for the Extra Value products in the following situations:

If you install any of the Extra Value products that are provided on the Solaris 10 DVD or CDs
If the /var file system is located on a separate slice

You must manually specify a larger slice size for the /var file system.

Note –

If the /var file system is not on a separate slice or partition, this problem does not occur.

Workaround: Choose one of the following workarounds.

If you are using the Solaris installation program GUI, follow these steps.
1. Begin the installation.
2. From Select Type of Install, select Custom Install.
  
  The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.
3. From Lay Out File Systems, select Modify.
  
  The disk layout screen is displayed.
4. Type /var in the File System column for a specific slice, then click Apply.
  
  The installation program suggests a default size for the /var file system.
5. Edit the Size column entry for the /var file system to twice the disk space size.
  
  For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.
6. Complete the installation.
If you are using the Solaris installation program's text installer, follow these steps.
1. Begin the installation.
2. From Select Type of Install, select Custom Install.
  
  The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.
3. From Lay Out File Systems, select Auto Layout.
  
  The disk layout screen is displayed.
4. Type /var in the File System column for a specific slice.
  
  The installation program suggests a default size for the /var file system.
5. Press F4_Customize to customize the size of the /var file system.
6. Edit the Size column entry for the /var file system to twice the disk space size.
  
  For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.
7. Complete the installation.
If you are using the custom JumpStart program, use the filesys profile keyword to set the size of the /var file system. The following example sets the size of the /var file system on slice 5 to 256 Mbytes.
filesys c0t0d0s5 256 /var

SPARC: Older Firmware Might Need Boot Flash PROM Update

On SPARC based systems, Solaris 10 OS runs in 64–bit mode only. Some Sun4U^TM systems might need to be updated to a higher level of OpenBoot^TM firmware in the flash PROM to run the OS in 64-bit mode. The following systems might require a flash PROM update:

Ultra^TM 2
Ultra 450 and Sun Enterprise^TM 450
Sun Enterprise 3000, 4000, 5000, and 6000 systems

The following table lists the UltraSPARC systems and the minimum firmware versions that are required to run the 64–bit Solaris 10 OS. System type is the equivalent of the output of the uname -i command. You can determine which firmware version you are running by using the prtconf -V command.

Table 2–1 Minimum Firmware Versions Required to Run 64–Bit Solaris Software on UltraSPARC Systems


System Type From `uname -i`	Minimum Firmware Version From `prtconf -V`
SUNW,Ultra-2	3.11.2
SUNW,Ultra-4	3.7.107
SUNW,Ultra-Enterprise	3.2.16

Note –

If a system is not listed in the previous table, the system does not need a flash PROM update.

See any edition of the Solaris 8 Sun Hardware Platform Guide at http://docs.sun.com for instructions to perform a flash PROM update.

Solaris Management Console 2.1 Software Is Not Compatible With Solaris Management Console 1.0, 1.0.1, or 1.0.2 Software

Solaris Management Console 2.1 software is not compatible with Solaris Management Console 1.0, 1.0.1, or 1.0.2 software. If you are upgrading to the Solaris 10 release, and you have Solaris Management Console 1.0, 1.0.1, or 1.0.2 software installed, you must first uninstall the Solaris Management Console software before you upgrade. Solaris Management Console software might exist on your system if you installed the SEAS 2.0 overbox, the SEAS 3.0 overbox, or the Solaris 8 Admin Pack.

Workaround: Choose one of the following workarounds:

Before you upgrade, use the /usr/bin/prodreg command to perform a full uninstall of Solaris Management Console software.

If you did not uninstall Solaris Management Console 1.0, 1.0.1, or 1.0.2 software before you upgraded to the Solaris 10 release, you must first remove all Solaris Management Console 1.0, 1.0.1, or 1.0.2 packages. Use the pkgrm command for package removal instead of the prodreg command. Carefully follow the order of package removal. Complete the following steps:

Become superuser.
Type the following command:
# pkginfo | grep “Solaris Management Console“
If the description does not start with “Solaris Management Console 2.1,” the package names in the output identify a Solaris Management Console 1.0 package.
Use the pkgrm command to remove all instances of Solaris Management Console 1.0 packages in the following order:

Note –
Do not remove any package that has “Solaris Management Console 2.1” in its description. For example, SUNWmc.2 might indicate Solaris Management Console 2.1 software.

If the pkginfo output displays multiple versions of Solaris Management Console 1.0 packages, use the pkgrm command to remove both packages. Remove the original package. Then, remove the package that has been appended with a number. For example, if the SUNWmcman and SUNWmcman.2 packages appear in the pkginfo output, first remove the SUNWmcman package and then remove the SUNWmcman.2 package. Do not use the prodreg command.
# pkgrm SUNWmcman # pkgrm SUNWmcapp # pkgrm SUNWmcsvr# pkgrm SUNWmcsvu # pkgrm SUNWmc # pkgrm SUNWmcc # pkgrm SUNWmcsws
In a terminal window, type the following command:
# rm -rf /var/sadm/pkg/SUNWmcapp

The Solaris Management Console 2.1 software should now function properly. For future maintenance, or if the Solaris Management Console 2.1 software does not function properly, remove the Solaris Management Console 2.1 software. Reinstall the software by completing the following steps:

Use the pkgrm command to remove all Solaris Management Console 2.1 packages and dependent packages in the following order:

Note –

If your installation has multiple instances of Solaris Management Console 2.1 packages, such as SUNWmc and SUNWmc.2, first remove SUNWmc, and then SUNWmc.2 . Do not use the prodreg command.

# pkgrm SUNWpmgr 
# pkgrm SUNWrmui 
# pkgrm SUNWlvmg 
# pkgrm SUNWlvma 
# pkgrm SUNWlvmr 
# pkgrm SUNWdclnt 
# pkgrm SUNWmga 
# pkgrm SUNWmgapp 
# pkgrm SUNWmcdev 
# pkgrm SUNWmcex 
# pkgrm SUNWwbmc 
# pkgrm SUNWmc 
# pkgrm SUNWmcc 
# pkgrm SUNWmccom

Insert the Solaris 10 Software - 4 CD into your CD-ROM drive. Type the following in a terminal window:

# 
# cd /cdrom/cdrom0/Solaris_10/Product
# pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev \
  SUNWmgapp SUNWmga SUNWdclnt SUNWlvmr SUNWlvma SUNWlvmg SUNWpmgr \
  SUNWrmui

All previous Solaris Management Console versions are removed. The Solaris Management Console 2.1 software is now functional.

Cannot Create a Solaris Flash Archive When Solaris Zones Are Installed (6246943)

Starting with the current Solaris release, a Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not currently compatible with the Solaris containers (zones) feature.

Do not use the flar create command to create a Solaris Flash archive in these instances:

In any non-global zone
In the global zone if there are any non-global zones installed

If you create a Solaris Flash archive in such an instance, the resulting archive might not install properly when the archive is deployed.

Workaround: None.

Before You Begin

Installation Change for the Solaris Companion DVD

Correct Solaris Data Encryption Supplement Required for Use of Longer Key Lengths on Solaris 10 Updates

Additional Procedures Required When Installing Patches for Solaris 10 7/07 HW Release

Resolving Issues With the GNOME Display Manager (6277164)

Sun Fire V250 Server Installation

NFS Version 4 Introduces New Prompt at First System Boot

Custom JumpStart and Advanced Installations

Default Size of /var File System Inadequate for Extra Value Products

SPARC: Older Firmware Might Need Boot Flash PROM Update

Solaris Management Console 2.1 Software Is Not Compatible With Solaris Management Console 1.0, 1.0.1, or 1.0.2 Software

Cannot Create a Solaris Flash Archive When Solaris Zones Are Installed (6246943)

Default Size of `/var` File System Inadequate for Extra Value Products