Alternate Pathing (AP) 2.2 and Dynamic Reconfiguration (DR) are supported in the Solaris 7 8/99 release. Inter-Domain Networks (IDN) is not supported. Upgrades from Solaris 2.3 or Solaris 2.4 to Solaris 7 8/99 are not supported.
Before beginning the fresh install or upgrade procedures, you must install the SSP patches described in "Solaris 7 8/99 and the SSP", unless you have upgraded the SSP operating environment to SSP 3.1.1.
If you are upgrading the operating environment from Solaris 2.6 to Solaris 7 8/99 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 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.
For Solaris 7 8/99, you must enable the soc and pln drivers in /etc/system before you attempt to detach a system board that hosts these drivers. Use the following syntax to enable the drivers:
set pln:pln_enable_detach_suspend=1 set soc:soc_enable_detach_suspend=1
On the Sun Enterprise 10000, you can check whether a domain is running in 32-bit or 64-bit mode by using the following command:
domain_name# isainfo -k sparcv9
The returned value, sparcv9, indicates that the domain is running in 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.
For additional information on SSP bugs and patches, see "System Service Processor".
SSP 3.1 is the first SSP release to support Solaris 7 8/99. If you are installing Solaris 7 8/99 on a domain or upgrading the existing Solaris operating environment on a domain, you must have SSP 3.1 or SSP 3.1.1 installed on the SSP. SSP 3.0 does not support Solaris 7 8/99. In addition, before you perform the Solaris 7 8/99 upgrade on a Sun Enterprise 10000 domain, the SSP must have Patch-ID 105684-04 installed, unless you have upgraded the SSP operating environment to SSP 3.1.1. The following patches are available at http://www.sunsolve.com.
If the SunSolve site contains versions of the patch that are higher than the version numbers listed in this section, use those patches instead of the patch numbers indicated in this section.
Description: OBP/download_helper needs to support 2.7
BugIDs fixed with this patch: 4078459 4083870 4084325 4097230 4102171 4118746 4137422 4146592
Description: SSP 3.1 sys_id -m doesn't work in year 2000 or after (Y2K bug)
BugIDs fixed with this patch: 4105569
Description: SSP 3.1 Hostview suppresses trap messages after 1999
BugIDs fixed with this patch: 4108443
SunFDDI(TM) is not supported on the Sun Enterprise 10000 server.
SunATM(TM) 4.0 Update 1 is not supported on the Sun Enterprise 10000 server.