C H A P T E R  6

Sun Enterprise 10000 Release Notes

This chapter contains the release notes for the following features on the Sun Enterprise 10000 server: Dynamic Reconfiguration (DR), InterDomain Networks (IDNs), and the Solaris operating environment on Sun Enterprise 10000 domains.

Dynamic Reconfiguration Issues

DR Model 3.0

You must use DR model 3.0 on Sun Enterprise 10000 domains that run the Solaris 9 12/03 operating environment or later. DR model 3.0 refers to DR functionality that uses the following commands on the SSP to perform domain DR operations:

In addition, you can run the cfgadm(1M) command on domains to obtain board status information. Note that DR model 3.0 also interfaces with the Reconfiguration Coordination Manager (RCM) to coordinate the DR operations with other applications running on a domain.

Note - DR model 3.0 is the only DR model supported for the Solaris 9 4/04 release. For details on DR model 3.0, refer to the Sun Enterprise 10000 Dynamic Reconfiguration User Guide.

General Issues

This section contains general issues that involve DR on the Sun Enterprise 10000 server. You should read this section before you attempt to install or configure DR.

DR and Bound User Processes

For Solaris 9 4/04, DR no longer automatically unbinds user processes from CPUs that are being detached. You are now required to perform this operation before initiating a detach sequence. The drain operation fails if CPUs are found with bound processes.

Enabling DR 3.0 Requires an Extra Step in Certain Situations (Bug ID 4507010)

If you upgrade or perform a fresh install of the Solaris operating environment on a domain before you upgrade the SSP to SSP 3.5, the domain will not be properly configured for DR 3.0.

Workaround: Run the following command as superuser on the domain, after the SSP has been upgraded to SSP 3.5. This workaround is not necessary until DR 3.0 is enabled on the domain.

# devfsadm -i ngdr

InterDomain Networks (IDN)

General Issues

For a domain to become part of an IDN, all boards in that domain that have active memory must have at least one active CPU.

Solaris Operating Environment

This section contains general issues, known bugs, patches, and notes about the Solaris 9 4/04 operating environment on the Sun Enterprise 10000 server.

General Issues

Dynamic reconfiguration (DR) and InterDomain Networks are supported in the Solaris 9 4/04 release.

Note - Before you begin the fresh installation or upgrade of the Solaris 9 4/04 operating environment on a Sun Enterprise 10000 domain, you must install SSP 3.5 on your System Service Processor. SSP 3.5 supports the Solaris 9 4/04 operating environment on Sun Enterprise 10000 domains.

Note - Do not use the Solaris 9 4/04 Installation CD to install or upgrade the Solaris operating environment on Sun Enterprise 10000 domains. Begin installation from the Solaris 9 4/04 Software 1 of 2 CD. You can follow the installation procedures described in the Sun Enterprise 10000 SSP 3.5 Installation Guide and Release Notes, if you substitute the Solaris 9 4/04 Software CDs for the Solaris 8 10/01 CDs.

Solaris 9 4/04 and Boot Disk Partition Sizes

If you are upgrading the operating environment from Solaris 2.6 to Solaris 9 4/04 and you used the partition layout suggested in the SMCC Hardware Platform Guide Solaris 2.6, the partitions might 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 might calculate a partition layout that is not acceptable for some systems. For instance, DSR might select partitions that appear to DSR as unused (non-UFS partitions that might contain raw data or other types of file systems). If DSR selects a used partition, data loss might 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 might need to manually repartition the boot device, or you might have to perform a fresh installation.

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.

Note - If local-mac-address? is set to true, it might 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

procedure icon  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