Solaris Operating Environment

This section contains general issues, known bugs, patches, and notes about the Solaris 8 2/02 operating environment on the Sun Enterprise 10000 server.

General Issues

Alternate Pathing (AP), dynamic reconfiguration (DR), and InterDomain Networks are supported in the Solaris 8 2/02 release.

If you intend to use DR model 3.0 on a Sun Enterprise 10000 domain, you must install SSP 3.5 on your System Service Processor before you begin the fresh install or upgrade of the Solaris 8 2/02 operating environment on that domain. SSP 3.5 supports the Solaris 8 2/02 operating environment on Sun Enterprise 10000 domains.

Do not use the Solaris 8 2/02 Installation CD to install or upgrade the Solaris operating environment on Sun Enterprise 10000 domains. Begin installation from the Solaris 8 2/02 Software 1 of 2 CD, as explained in the SSP 3.5 Installation Guide and Release Notes.

Solaris 8 2/02 and Boot-Disk Partition Sizes

If you are upgrading the operating environment from Solaris 2.6 to Solaris 8 2/02 and you used the partition layout suggested in the SMCC Hardware Platform Guide Solaris 2.6, the partitions may not be large enough for the upgrade. For instance, the /usr partition must be at least 653 megabytes. If /usr is smaller than the size needed to perform the upgrade, suninstall uses the Dynamic Space Reallocation (DSR) mode to reallocate the space of the disk partitions.

DSR may calculate a partition layout which is not acceptable for some systems. For instance, DSR may select partitions that appear to DSR as being unused (non-UFS partitions which may contain raw data or other types of file systems). If DSR selects a used partition, data loss may occur. Therefore, you must know the current status of the partitions DSR wants to use before you allow DSR to continue with the reallocation of the disk partitions.

After DSR presents an acceptable layout and you choose to proceed with the reallocation, DSR adjusts the affected file systems, and the upgrade continues. However, if you cannot constrain the layout so that it is acceptable for your needs, then you may need to manually repartition the boot device, or you may have to perform a fresh install.

OpenBoot PROM Variables

Before you perform the boot net command from the OpenBoot PROM prompt (ok), you must verify that the local-mac-address? variable is set to false, which is the factory default. If the variable is set to true, you must ensure that this value is an appropriate local configuration.

If local-mac-address? is set to true, it may prevent the domain from successfully booting over the network.

In a netcon(1M) window, you can use the following command at the OpenBoot PROM prompt to display the values of the OpenBoot PROM variables:

ok printenv

To Set the local-mac-address? Variable

1. If the variable is set to true, use the setenv command to set it to false.

   ok setenv local-mac-address? false