test

Solaris 7 11/99 Release Notes Supplement for Sun Hardware

AP on Sun Enterprise Servers

This section contains the release notes for Alternate Pathing (AP) 2.2 on all Sun Enterprise servers, except the Sun Enterprise 10000. See "AP on the Sun Enterprise 10000" for information about the Enterprise 10000 server.

Note -

AP 2.2 is the first release of AP that supports Solaris 7 11/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 AP User's Guide in the Solaris 7 11/99 on Sun Hardware Collection AnswerBook2(TM).

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.6 to Solaris 7 11/99 and have AP 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 the Solaris 7 11/99 Sun Hardware Platform Guide.

  2. Commit any uncommitted AP metadevices (see Step 1 in "To Upgrade AP" in the Solaris 7 11/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 11/99 at this time.

  4. Remove the current AP configuration (see Step 3 in "To Upgrade AP" in the Solaris 7 11/99 Sun Hardware Platform Guide).

  5. Upgrade to Solaris 7 11/99 (see Step 4 in "To Upgrade AP" in the Solaris 7 11/99 Sun Hardware Platform Guide).

  6. Upgrade to AP 2.2 (see Step 5 in "To Upgrade AP" in the Solaris 7 11/99 Sun Hardware Platform Guide).

  7. Install SDS 4.2, then restore it (see Step 6 in "To Upgrade AP" in the Solaris 7 11/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 Sun Enterprise servers. 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 devices are supported in which releases:

Table 5-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 11/99 

N/A 

N/A 

ge,hme, le, nf, qe, qfe

SunFDDI and GigabitEthernet Devices

AP 2.2 validation tests were performed on SunFDDI (revision 6.0) and GigabitEthernet (revision 2.0). If you install either of these devices, 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 these devices. 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 lists includes the possible combinations of AP and Solaris software you can install on a Sun Enterprise server.

Known Bugs

The following bugs are no known bugs in this version of AP 2.2.

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 - AP GigabitEthernet stress test hands.

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.

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