Document fins/I0577-1
FIN #: I0577-1
SYNOPSIS: Solstice DiskSuite (SDS) is now supported on Ultra 5 and Ultra 10
systems.
DATE: MAY/05/00
KEYWORDS: Solstice DiskSuite (SDS) is now supported on Ultra 5 and Ultra 10
systems.
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: Solstice DiskSuite (SDS) is now supported on Ultra 5 and
Ultra 10 systems.
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: Solstice DiskSuite on Ultra 10 & 5 systems
PRODUCT CATEGORY: Storage / SW Admin
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
---------------
- A21 - Ultra 5 -
- A22 - Ultra 10 -
X-Options Affected
------------------
X5227A - - OPT INT 4.3GB DRIVE FOR U10 -
X5236A - - OPT INT 9GB DRIVE FOR U5/U10 -
X6170A - - OPT INT CD-ROM FOR U5/U10 -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
- - -
REFERENCES:
BugId: 4120188, 4212490, 4205336
PatchId: 
107121 - For Solaris 7
106407 - For Solaris 2.6
106197 - For Solaris 2.5.1
DOC: 805-7115-10 - Ultra 5/10 CD-ROM and Hard Disk Drive Installation Guide
805-5960-10 - Solstice DiskSuite 4.2 Installation and Product Notes
805-5962-10 - Solstice DiskSuite 4.2 Reference Guide
805-5961-10 - Solstice DiskSuite 4.2 User's Guide
URL: FAQ's for SDS on IDE -
http://storage.central.sun.com/projects/disksuite/info/faq.html#eide
IDE FAQ -
http://dtsw.eng.sun.com/dtio-iohelp/ide.html
Web site for comparison of SDS and veritas at -
http://ie.corp/~hellier/comp/diskmgt/
PROBLEM DESCRIPTION:
The Ultra 5/Ultra 10 workstations use IDE as the primary interface for
mass storage. The purpose for this FIN is to make sure to provide all
the necessary information to configure Ultra 5/Ultra 10 systems in IDE
disk mirroring configurations.
There are limitations in the driver and in the IDE interface to
configure Ultra 10/Ultra 5 in a mirroring configuration. Hence, using
Solstice DiskSuite and VxVM software for the purpose of IDE disk
mirroring on Ultra 5/Ultra 10 has been a problem.
IDE protocol limitations mean that mirroring is only recommended when
the disk drive is attached to a different channel than itsmirror. Thus,
it is not recommended to attach the disk and the mirrored disk on the
same channel.
Recommended Hardware configuration:
-----------------------------------
IDE subsystem has two channels designated as Primary and Secondary
which work independently of each other. On the Ultra 5/Ultra 10
Motherboard, there are two separate connectors for each channel. Each
channel can support two devices. One of these can be selected as
Master device (device 0) and the other as Slave device (Device 1). The
selection of Master and Slave is done through jumper settings next to
the power connector on the device.
The Hardware configuration which should be used when using Ultra 10
in a mirrored configuration is;
Primary Channel - One disk selected as Master.
Secondary Channel - One disk selected as Master.
If it is desired to connect a CDROM device, it should be connected as
a slave on the secondary channel.
Two IDE cables would be required for this configuration. Each connected
to the connector on the Motherboard at one end and to a Disk drive
(jumper as Master) at the other end.
Note - For connecting a second disk on Ultra 5, the X-option part
number is X5236A.
Software Constraints:
---------------------
Solstice DiskSuite 4.1 has a recommendation of having a minimum of
three metadevice state databases to maintain a quorum. It is further
recommended that the state database be maintained on different disks.
Thus, requiring three IDE disks on the system.
The recommendation for a IDE subsystem is to mirror disks across the
channel. As a result only, two IDE disks are possible hence only
two metadevice state databases.
This limitation has a known impact - Solstice DiskSuite will function
with only two disks and two state database replicas. However, should
one disk fail, there would not be a quorum. There's no problem with the
system will arise until the system goes down. Once the system is down,
it will not boot multi-user without system administration intervention.
If the quorum is not met on boot, for example; due to a drive failure,
the system will come up single user. The problem will be reported when
the machine is rebooted and the output messages will be similar to the
following;
ok boot
...
Hostname: demo
metainit: demo: stale databases
Insufficient metadevice database replicas located.
Use metadb to delete databases which are broken.
Ignore any "Read-only file system" error messages.
Reboot the system when finished to reload the metadevice
database. After reboot, repair any broken database
replicas which were deleted.
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance):<root-password>
Entering System Maintenance Mode.
IDE Disk Driver (DAD) and the IDE HBA (UATA) driver were modified and
made more robust for the mirroring support on U5/U10.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| X | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
Enterprise Customers and authorized Field Service Representatives may
avoid the above mentioned problem by following the recommendation as
shown below;
The driver patch needs to be installed on the system before using the
mirroring features of Solstice DiskSuites (SDS).
The required patch numbers are;
#1. Solaris 7 - Patch Number: 107121 or greater.
#2. Solaris 2.6 - Patch Number: 106407 or greater.
#3. Solaris 2.5.1 - Patch Number: 106197 or greater.
In case the above problem is encountered then the following procedure
may be used as a workaround;
The recovery procedure for this can be obtained from -
Appendix C of the DiskSuite 4.2 Reference Manual or Appendix
C of the DiskSuite 4.1 Administration Guide or from the following
web site -
http://sunsolve.Corp.Sun.COM/int-cgi/doc2html?intinfodoc/18280+9139927042741
#2. At the OBP level, the alias for cdrom device is
/pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f. This is hardcoded with the
assumption that the CDROM device is connected as the Master device on
secondary channel. In the mirroring configuration, this is not be true
(CDROM will be a Slave on Primary or Secondary channel) so this alias
would be rendered inaccurate. As a result, the following command would
not work - ok> boot cdrom
The alias for cdrom needs to be changed (using command nvalias) to;
A) If the CDROM device is Slave on primary channel
ok nvalias cdrom /pci@1f,0/pci@1,1/ide@3/cdrom@1,0:f
B) if CDROM drive is Slave on secondary channel
ok nvalias cdrom /pci@1f,0/pci@1,1/ide@3/cdrom@3,0:f
Note : The change to alias is required if the user wants to use the
command "boot cdrom" which is the usual case. Booting from the
cdrom will work if the complete pathname of the device node is
given along with the boot i.e. The following command works and
system will boot from CD even when if the alias has not been
updated. ok boot /pci@1f,0/pci@1,1/ide@3/cdrom@3,0:f.
COMMENTS:
--------------------------------------------------------------------------
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "Enterprise Services Documenta-
tion" and click on "FIN & FCO attachments", then choose the
appropriate
folder, FIN or FCO. This will display supporting directories/files for
FINs or FCOs.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.