Solaris Operating Environment
This section contains general issues, known bugs, patches, and notes about the Solaris 7 11/99 release on the Sun Enterprise 10000 server.
General Issues
Upgrades from Solaris 2.3 or Solaris 2.4 to Solaris 7 11/99 are not supported.
Note -
Before beginning the fresh install or upgrade procedures for the Solaris operating environment on the Sun Enterprise 10000 server, you must install the SSP patches described in the Sun Enterprise 10000 SSP Installation Guide and Release Notes, unless you have upgraded the SSP operating environment to SSP 3.1.1 or SSP 3.2.
Solaris 7 11/99 and Boot-Disk Partition Sizes
If you are upgrading the operating environment from Solaris 2.6 to Solaris 7 11/99 and if 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.
Solaris 7 11/99 and Driver Variables
For Solaris 7 11/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 pln:pln_enable_detach_suspend=1
SunFDDI
SunFDDI(TM) is not supported on the Sun Enterprise 10000 server.
SunATM 4.0 Update 1
SunATM(TM) 4.0 Update 1 is not supported on the Sun Enterprise 10000 server.
Known Bugs
This section contains the bugs known to exist in the Solaris 7 11/99 release.
4231845 - Cannot Detach System Board if the in.rarpd Daemon is Running and /rplboot Exists
For Solaris 7 11/99 Beta, the qec and qe drivers are not compatible with DR or AP 2.2.
Workaround: None
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
Documentation Errata
This section contains errors in the documentation that pertains to the Solaris operating environment on the Sun Enterprise 10000 server.
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
- © 2010, Oracle Corporation and/or its affiliates