Document fins/I0511-2
FIN #: I0511-2
SYNOPSIS: Enabling DMP under Volume Manager 2.5/2.6 with RDAC and
RSM2000/A3x00/A3500FC may cause private regions to be lost.
DATE: Sep/18/00
KEYWORDS: Enabling DMP under Volume Manager 2.5/2.6 with RDAC and
RSM2000/A3x00/A3500FC may cause private regions to be lost.
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: Enabling DMP under Volume Manager 2.5/2.6 with RDAC and
RSM2000/A3x00/A3500FC may cause private regions to be lost.
This FIN is not applicable to VxVM 3.0.2 or higher.
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: VM DMP interferes with RSM2000/A3x00/A3500FC RDAC
PRODUCT CATEGORY: Storage / SW Admin
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- ANYSYS - System Platform Independent -
X-Options Affected
------------------
X6530A - - RSM Array 2000 in Exp. Cabn.15x4.2Gb/5400 -
X6531A - - RSM Array 2000 in Exp. Cabn.35x4.2Gb/5400 -
X6532A - - RSM Array 2000 in Exp. Cabn.15x4.2Gb/7200 -
X6533A - - RSM Array 2000 in Exp. Cabn.35x4.2Gb/7200 -
X6534A - - RSM Array 2000 in Exp. Cabn.15x9.1Gb/7200 -
X6535A - - RSM Array 2000 in Exp. Cabn.35x9.1Gb/7200 -
6534A A3000 - A3000 15*9.1GB/7200 FWSCSI -
6535A - - A3000 35*9.1GB/7200 FWSCSI -
SG-ARY351A-180G A3500 - A3500 1 CONT MOD./5 TRAYS/18GB -
SG-ARY353A-360G - - A3500 2 CONT/7 TRAYS/18GB -
SG-ARY360A-90G - - A3500 1 CONT/5 TRAYS/9GB(10K) -
SG-ARY362A-180G - - A3500 2 CONT/7 TRAYS/9GB(10K) -
SG-ARY366A-72G - - A3500 1 CONT/2 TRAYS/9GB(10K) -
SG-ARY366A-72GR5 - - A3500 1 CONT/2 TRAYS/9GB(10K) -
SG-ARY370A-91G - - 91-GB A3500 (1x5x9-GB) -
SG-ARY372A-182G - - 182-GB A3500 (2x7x9-GB) -
SG-ARY374A-273G - - 273-GB A3500 w/(3x15x9-GB) -
SG-ARY380A-182G - - 182-GB A3500 (1x5x18-GB) -
SG-ARY382A-364G - - 364-GB A3500 (2x7x18-GB) -
SG-ARY384A-546G - - 546-GB A3500 (3x15x18-GB) -
SG-XARY351A-180G - - A3500 1 CONT MOD/5 TRAYS/18GB -
SG-XARY353A-1008G - - A3500 2 CONT/7 TRAYS/18GB -
SG-XARY353A-360G - - A3500 2 CONT/7 TRAYS/18GB -
SG-XARY355A-2160G - - A3500 3 CONT/15 TRAYS/18GB -
SG-XARY360A-545G - - 545-GB A3500 (1X5X9-GB) -
SG-XARY360A-90G - - A3500 1 CONT/5 TRAYS/9GB(10K) -
SG-XARY362A-180G - - A3500 2 CONT/7 TRAYS/9GB(10K) -
SG-XARY362A-763G - - A3500 2 CONT/7 TRAYS/9GB(10K) -
SG-XARY364A-1635G - - A3500 3 CONT/15 TRAYS/9GB(10K) -
SG-XARY366A-72G - - A3500 1 CONT/2 TRAYS/9GB(10K) -
SG-XARY380A-1092G - - 1092-GB A3500 (1x5x18-GB) -
X6538A - - X-OPT,A3500FC CONTROLLER -
6538A - - FCTY, CONTROLLER, A3500FC -
UG-A3K-A3500FC - - ASSY,UPGRADE,A3500FC/TABASCO -
UG-A3500-A3500FC - - ASSY,UPGRADE,A3500FC/DILBERT -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
EVM-2.5-B SEVM 2.5 Base Pack (Media and Doc.) -
805-1603-10 Sun Enterprise VM 2.5 User's Guide -
805-1604-10 Sun Enterprise VM 2.5 Installation Guide -
805-1605-10 Sun Enterprise VM 2.5 Release Notes -
805-1607-10 Sun Enterprise VM 2.5 System Admin Guide -
804-5967-10 Sun Enterprise VM 2.5 (CD Insert) -
805-5708-10 Sun Enterprise VM 2.6 Release Notes -
804-6316-10 Sun StorEdge Volume Manager 2.6 (CD Insert) -
805-5707-10 Volume Manager 2.6 Installation Guide -
805-5706-10 Volume Manager 2.6 Sysadmin Guide -
704-6316-10 Sun StorEdge Volume Manager 2.6 -
- Veritas Volume Manager 2.5 -
- Veritas Volume Manager 2.6 -
REFERENCES:
BugId: 4180291, 4109037, 4237490
ESC: 520517
PROBLEM DESCRIPTION:
There have been several reported cases where systems with an attached
RSM2000/A3x00/A3500FC with Volume Manager on top of RM6 LUNs have
experienced the corruption of the Volume Manager configurations. The
purpose of this FIN update is to notify that VxVM 3.0.2 and A1000s are
not affected.
Upon further investigation, the cause has been found to be an
incompatibility between Dynamic MultiPathing (DMP) and Redundant Disk
Array Controller (RDAC), the "failover" software used exclusively by
the RSM2000/A3x00/A3500FC and the ability to disable DMP for certain
devices and enable it for others.
This problem occurs at boot time when DMP builds it's in-kernel
mapping of disk access names to disk media names. This mapping is
being done at the same time RDAC is establishing it's control and
management of the dual paths to the RSM2000/A3x00/A3500FC.
DMP initially sees both physical paths to the RSM2000/A3x00/A3500FC and
adds them to this mapping. The RDAC module then notices a device name
change usually caused by some hardware configuration change such as
swapped or failed controller) and invalidates the paths already seen by
DMP.
This causes an error message such as the following to be seen at bootup
for each RM6 LUN as described below:
Warning: /sbus@7,0/QLGC,isp@2,10000/sd@5,0 i/o to invalid geometry
Volume Manager disables the configuration copy on that device because
it no longer deems it to be valid. If all configuration copies are
disabled (there is one on every LUN), the disk group does not get
imported upon system boot, and the following message results:
vxvm: Error: cannot auto-import group.
DiskGroup has no valid configuration copies
As a result, the diskgroup is lost forever. The system continues to
boot, however, and once logged in, the 'root' user can list the Volume
Manager disks using 'vxdisk list' to see that the affected LUNs are
marked as "altused". For example:
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced - - error
c0t0d1s2 sliced disk01 rootdg online
c0t0d2s2 sliced disk02 rootdg online
c0t2d0s2 sliced disk03 rootdg online
c0t2d1s2 sliced - - error
c0t2d2s2 sliced - - error
c3t5d0s2 sliced - - online altused
c3t5d1s2 sliced - - online altused
c3t5d2s2 sliced - - online altused
There are normally (2) configuration copies on a disk. If the first
one gets corrupted, the "altused" flag is set and the second one is
used instead. In this case, the flag is set, but when Volume Manager
goes to use the second one, it realizes too late that it, too, must be
disabled for the same reason as the first. Hence, the 'altused' flag
is misleading, because the alternate configuration copy is not really
being used at all.
Update for FIN I0511-2;
-----------------------
In this -2, the following has been updated to FINI0511-1;
1) Taken out A1000 and add RSM2000 and A3500FC on the following
sections:
. SYNOPSIS
. PRODUCT REFERENCE
. PROBLEM DESCRIPTION
. CORRECTIVE ACTION
2) Removed the A1000 X-option parts and added RSM2000 and A3500FC
X-option parts on the X-OPTIONS AFFECTED section.
3) Add Note statement "The problems have been fixed in Veritas Volume
Manager 3.0.2 and later releases and it is not necessary to apply
this FIN if running VxVM 3.0.2 or later." on the COMMENT section.
4) Add BugId# 4180291 in the REFERENCE section.
5) Following changes have been made on the PART NUMBERS AFFECTED
section;
. Removed EVM-2.4-B: SEVM 2.4 Base Pack (Media and Doc.).
. Add Veritas Volume Manager and 2.5 Veritas Volume Manager 2.6
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| X | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
In response to the above mentioned problem due to an interaction with
Volume Manager DMP interfering with RSM2000/A3x00/A3500FC RDAC, The
following recommendation is provided to resolve the problem:
In Volume Manager 3.0.2 or later, the DMP code has been fixed such
that DMP is not used on disks identified as controlled by RDAC and,
therefore, no corrective action is required.
For those customers unwilling or unable to upgrade their Volume
Manager software, it is recommended that they disable DMP on systems
with RDAC (that is, all systems with an attached RSM2000/A3x00/A3500FC)
as described below:
This document explains how to disable the DMP module of Volume Manager
(DMP stands for Dynamic MultiPathing). This procedure should NOT be
performed on systems running the following 2 patches (as these versions
of the patches contained a bug which prevents DMP from being disabled):
SEVM 2.5: 
105463
SEVM 2.6: 106606
* Make sure the latest versions of these Volume Manager patches are
installed before attempting this procedure (as they contain the fix
which allows DMP to be disabled).
1. Remove the vxdmp driver.
rm /kernel/drv/vxdmp
* If running a 64 bit version of Solaris you will need to
remove the vxdmp driver from the sparcv9 directory as well:
rm /kernel/drv/sparcv9/vxdmp
2. Edit /etc/system and remove the vxdmp forceload statement.
vi /etc/system
forceload: drv/vxdmp
3. Remove the DMP device directories.
rm -rf /dev/vx/dmp
rm -rf /dev/vx/rdmp
4. Create symbolic links to dmp and rdmp.
ln -s /dev/dsk /dev/vx/dmp
ln -s /dev/rdsk /dev/vx/rdmp
5. Reboot System.
COMMENTS:
NOTE: The problems have been fixed in Veritas Volume Manager 3.0.2
and later releases and it is not necessary to apply this FIN
if running VxVM 3.0.2 or later.
--------------------------------------------------------------------------
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.