Solaris 7 5/99 Release Notes Supplement for Sun Hardware

Sun Enterprise 10000 Server

This chapter contains general issues, known bugs, patches, and notes about the Solaris 7 5/99 release on the Sun^TM Enterprise^TM 10000 server.

General Issues

Alternate Pathing (AP) 2.2 and Dynamic Reconfiguration (DR) are supported in the Solaris 7 release. Inter-Domain Networks (IDNs) are not supported. Upgrades from the Solaris 2.3 or Solaris 2.4 operating environments to the Solaris 7 operating environment are not supported.

Note -

Before beginning the fresh install or upgrade procedures, you must install the SSP patches described in "Solaris 7 and the SSP".

The Solaris 7 Operating Environment and Boot-Disk Partition Sizes

If you are upgrading the operating environment from the Solaris 2.6 operating environment to the Solaris 7 operating environment 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 to succeed. 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 will adjust the affected file systems, and the upgrade will continue. 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.

Operating Mode

On the Sun Enterprise 10000, you can check whether a domain is running in 32-bit or in 64-bit mode by using the following command:

domain_name# isainfo -k
sparcv9

The returned value, sparcv9, indicates that the domain is running the 64-bit operating mode; otherwise, the domain is running in 32-bit mode.

You can also use another command, isalist, to check the operating mode; however, the return value, sparcv9+vis, differs from the return value of the isainfo --k command. The values are synonymous. They both indicate that the domain is running in 64-bit mode.

Solaris 7 and the SSP

SSP 3.1 is the first SSP release to support Solaris 7. If you are installing Solaris 7 on a domain or upgrading a domain's current Solaris operating environment, you must have SSP 3.1 installed on the SSP. SSP 3.0 does not support Solaris 7 on a domain. In addition, before you perform the fresh install or upgrade of the Solaris 7 software on an Sun Enterprise 10000 domain, the SSP must have Patch-ID 105684-04. This patch is on your Sun Computer Systems Supplements CD.

Note -

If the CD contains the latest version the patch, indicated by a higher-numbered suffix, use that patch instead of the patch number indicated in this section.

Patch-ID 105684-04

Description: OBP/download_helper needs to support 2.7

BugIDs fixed with this patch: 4078459 4083870 4084325 4097230 4102171 4118746 4137422 4146592

Patch-ID 106281-01

Description: SSP 3.1 sys_id -m doesn't work in year 2000 or after (Y2K bug)

BugIDs fixed with this patch: 4105569

Patch-ID 106282-01

Description: SSP 3.1 Hostview suppresses trap messages after 1999

BugIDs fixed with this patch: 4108443

Documentation Errata

This section contains errors in the documentation that pertains to the Solaris operating environment on the Sun Enterprise 10000 server.

Fresh Install Procedure

In the "Solaris 7 5/99 on the Sun Enterprise 10000 Server" chapter of the Sun Hardware Platform Guide Solaris 7 5/99, the Fresh Install procedure points the reader to the "Setting up the SSP as a Boot Server" section if the domain in question already exists. The procedure should, however, point the reader to the "Updating the OpenBoot PROM" section.

The Fresh Install procedure is not intended to be used for installations in which the domain already has an eeprom.image file associated with it on the SSP. Note that if you have removed the domain by using the domain_remove(1M) command, you will need to perform all of the procedures in the Fresh Install section to recreate the eeprom.image. If the eeprom.image already exists, refer to the "Performing an Upgrade" section.

OBP Variables

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

Caution -

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 OBP prompt to display the values of the OBP variables:

ok printenv

To Set the `local-mac-address?` Variable

If the variable is set to true, use the setenv command to set it to false.
```
ok setenv local-mac-address? false
```

Solaris Version Names

The version name for the Solaris operating environment changed in Sun publications with the release of Solaris 7 5/99; however, the version name in the code did not change. Thus, you should use 2.7 wherever the procedures call out for the version number of the operating system. For instance, in the "Creating a New Domain" procedure in the Fresh Install section, you should use 2.7 for the version name, as in the following example:

ssp# domain_create -d domain_name -b board_numbers -o 2.7 -p platform_name

Known Bugs

There are no Sun Enterprise 10000-specific bugs known to exist in the Solaris 7 5/99 release.

Fixed Bugs

This section lists important bugs that have been fixed. Minor bugs are not included. Each entry includes a 7-digit BugID assigned by Sun to aid in bug-tracking and a one-line description of the bug.

4110199 - /etc/init.d/cvc Implementation, Packaging Inconsistent