test

Solaris 7 8/99 Release Notes Supplement for Sun Hardware

Chapter 4 Sun Enterprise 10000 Release Notes

Sun Enterprise 10000

This section contains general issues, known bugs, patches, and notes about the Solaris 7 8/99 release on the Sun Enterprise(TM) 10000.

General Issues

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.

Note -

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.

Solaris 7 8/99 and Boot-Disk Partition Sizes

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.

Solaris 7 8/99 and Driver Variables

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

Operating Mode

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.

Solaris 7 8/99 and the SSP

Note -

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.

Note -

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.

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

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 5/99 release of DR.

4231845 - Cannot Detach System Board if the in.rarpd Daemon is Running and /rplboot Exists

For Solaris 7 8/99, 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 - 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

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

    ok setenv local-mac-address? false

AP on the Sun Enterprise 10000 Server

Alternate Pathing (AP) 2.2 is the first release of AP that is supported on Sun Enterprise 10000 domains running the Solaris 7 8/99 operating environment.

Note -

AP 2.2 is the first AP release to support Solaris 7 8/99.

AP enables you to define and control alternate physical paths to peripheral devices, adding increased availability and a level of fault recovery to your server. If a physical path to a device becomes unavailable, an alternate path can be used. For more information, see the Sun Enterprise Server Alternate Pathing 2.2 User's Guide in the Solaris 7 8/99 on Sun Hardware Collection AnswerBook.

Note -

At the time of this printing, AP 2.2 Beta is not compatible with any version of Sun Enterprise Volume Manager(TM) (SEVM).

Installation Issues

If you are upgrading from Solaris 2.5.1 or 2.6 to Solaris 7 8/99 and have AP 2.0 or 2.1 and Solstice(TM) DiskSuite(TM) 4.0 or 4.1 (SDS) on your system, you must upgrade to AP 2.2 and SDS 4.2. This section contains an overview of the entire process, which requires you to use several sections from different publications. You should ensure that you have the following publications before you start the upgrade:

Caution - Caution -

You must follow the sequence given here to successfully complete the upgrade.

In general, you will perform the following tasks:

Specifically, you must perform the following tasks:

  1. Read "Performing an Upgrade of AP" in "Alternate Pathing 2.2 on the Sun Enterprise 10000" in the Solaris 7 8/99 Sun Hardware Platform Guide.

  2. Commit any uncommitted AP metadevices (see Step 1 in "To Upgrade AP" in "Alternate Pathing 2.2 on the Sun Enterprise 10000" in the Solaris 7 8/99 Sun Hardware Platform Guide).

  3. Deconfigure SDS (see steps 1 through 8 in "How to Convert to DiskSuite 4.2 on SPARC Systems Running DiskSuite 4.0 or 4.1" in the Solstice DiskSuite 4.2 Installation and Product Notes).

    Caution - Caution -

    Do not install Solaris 7 8/99 at this time.

  4. Perform steps 3 through 5 in "To Upgrade AP" in "Alternate Pathing 2.2 on the Sun Enterprise 10000" in the Solaris 7 8/99 Sun Hardware Platform Guide).

    Note -

    For this beta release, you must remove the SUNWapap package as part of Step 3a in "To Upgrade AP" in the Solaris 7 8/99 Sun Hardware Platform Guide.

  5. Upgrade to Solaris 7 8/99 (see Step 6 in "To Upgrade AP" in "Alternate Pathing 2.2 on the Sun Enterprise 10000" in the Solaris 7 8/99 Sun Hardware Platform Guide).

  6. Follow steps 6 through 9 in "To Upgrade AP" in "Alternate Pathing 2.2 on the Sun Enterprise 10000" in the Solaris 7 8/99 Sun Hardware Platform Guide).

  7. Install SDS 4.2, then restore it (see Step 10 in "To Upgrade AP" in "Alternate Pathing 2.2 on the Sun Enterprise 10000" in the Solaris 7 8/99 Sun Hardware Platform Guide and steps 10 through 16 in "How to Convert to DiskSuite 4.2 on SPARC Systems Running DiskSuite 4.0 or 4.1" in Chapter 1 of the Solstice DiskSuite 4.2 Installation and Product Notes).

General Issues

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

Supported Devices

The following devices are supported by the AP software on Sun Enterprise servers:

The following table lists which network devices are supported in which releases:

Table 4-1 Supported Network Devices

 

AP 2.0 

AP 2.1 

AP 2.2 

Solaris 2.5.1 

hme, le, nf, bf, hi, qe, qfe

N/A 

N/A 

Solaris 2.6 (5/98) 

N/A 

ge, hme, le, nf, qe, qfe, vge

N/A 

Solaris 7 8/99 

N/A 

N/A 

ge,hme, le, nf, qe, qfe

SunFDDI Devices

AP 2.2 validation tests were performed on SunFDDI (revision 6.0). If you install this device, you must use the revision level that was tested, unless a higher revision level exists. In addition, you must install all of the available patches for this device. Refer to http://www.sunsolve.sun.com for more information about the patches.

Sun StorEdge A3000

The Sun StorEdge A3000 supports failover capabilities that are similar to those provided by AP. Because of this, AP does not support the Sun StorEdge A3000. See that product's documentation for more information about its failover support.

Sun StorEdge A5000

AP supports the Sun StorEdge A5000 for this release.

Sun StorEdge A7000

AP 2.2 does not support the Sun StorEdge A7000 for this release.

Software Compatibility

The following figures show the possible combinations of SSP, AP, and Solaris software you can install on a Sun Enterprise server. Note that the Sun Enterprise 10000 can have any combination of domains with the operating environment and software listed on the right of the figures. The version of the Solaris operating environment on the SSP and the version on the domain do not need to match.

Note -

In the following figures, "base only" means no AP and no DR, unless otherwise noted. Mainly, "base only" refers to a domain that has only the Solaris operating environment installed. In addition, some of the scenarios below are possible only if you install a patch, or a set of patches, on the SSP or on the domain. For more information about what patch, or patches, refer to the patch descriptions at http://sunsolve.sun.com.

Figure 4-1 SSP 3.0, AP 2.0, and Solaris 2.5.1 on the Sun Enterprise 10000

Graphic

Figure 4-2 SSP 3.1, AP 2.1, Solaris 2.5.1, Solaris 2.6 3/98, Solaris 2.6 5/98, and Solaris 7 on the Sun Enterprise 10000

Graphic

Figure 4-3 SSP 3.1, AP 2.2, AP 2.1, Solaris 2.5.1, Solaris 2.6 3/98, Solaris 2.6 5/98, Solaris 7, Solaris 7 3/99, Solaris 7 5/99, and Solaris 7 8/99 on the Sun Enterprise 10000 server

Graphic

Known Bugs

There are no known bugs in this release of AP.

Fixed Bugs

This section contains the synopses and Sun BugID number of the more important bugs that have been fixed since the AP 2.1 release (Solaris 2.6 5/98). This list does not include all of the fixed bugs.

4126743 - AP disk autofailover hangs on simultaneous multi-pathgroup failures (this bug was fixed by BugID 4136249).

4126897 - Domain panics when there are no AP database and metadevice entry in /etc/vfstab.

4136249 - I/O's to SEVM RAID volumes hang after AP autofailover.

4141438 - mhme interface hangs under heavy use of network.

4143514 - FDDI with AP hangs with heavy use of network.

4147674 - AP causes ifconfig to hang on a mutex.

4153152 - apconfig works as an ordinary user.

4161396 - AP 2.x needs capability to work with GEM.

4163270 - netstat of network ap network meta interface shows no tallies.

4166620 - snoop of AP meta network interface stops snooping after switch.

4170818 - If you run the $<callouts nadb macro, or fm2's "callout ts" command, you see thousands of qenable timeouts in the timeshare callout table.

4180055 - Accessing an AP'd metadisk with a failed active alternate panics.

4180702 - Messages from swap.c are not internationalized.

4183581 - apboot disk causes coredump when disk is the same as the current boot disk.

4185154 - GigabitEnthernet stress test hangs.

4188418 - It is possible for a hard disk error to go undetected by Veritas [SEVM].

4195441 - AP2.0 ap_daemon doesn't communicate with AP2.2.

4226867 - ap_reboot_host fails for photon in mixed AP versions.

4228731 - Non-existent network interfaces not marked as detached after reboot.