Document fins/I0589-1
FIN #: I0589-1
SYNOPSIS: glm.conf file must be modified to support more than 8 LUNs on any
PCI-SCSI connected A1000/A3x00 using any version of RM 6.
DATE: Jun/20/00
KEYWORDS: glm.conf file must be modified to support more than 8 LUNs on any
PCI-SCSI connected A1000/A3x00 using any version of RM 6.
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: glm.conf file must be modified to support more than 8 LUNs on
any PCI-SCSI connected A1000/A3x00 using any version of RM 6.
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: Any RM 6 version
PRODUCT CATEGORY: Storage / SW Admin
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- ANYSYS - - -
X-Options Affected
------------------
- RSM2000 ALL RSM Array 2000 -
- A3000 ALL StorEdge A3000 -
- A3500 ALL StorEdge A3500 -
- A1000 ALL StorEdge A1000 -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
- - -
(SCSI Devices)
Type Vendor Model Serial Number(Min) Serial Number(Max) Firmware
---- ------ ------- ------------------ ------------------ --------
HBA GLM X6541A - - -
REFERENCES:
BugId: 4095155, 4187678, 4325025
PatchId: 
105580 or higher, 106925
MANUAL: 805-7556-10 Sun StorEdge RAID Manager 6.22 Installation Guide
805-7558-10 Sun StorEdge RAID Manager 6.22 Release Notes
805-4058-11 Sun StorEdge RAID Manager 6.1.1 Installation Guide
805-3656-11 Sun StorEdge RAID Manager 6.1.1 Release Notes
PROBLEM DESCRIPTION:
Attempting to support for more than 8 LUNs on a system using the
PCI UltraSCSI differential dual channel host adapter connected to an
A3x00/A1000 array can cause loss of access to the data on those arrays.
Attempting to access that data will produce an error message "Unable
to scan module". The Raid Manager 6 GUI will not report anything.
This occurs on any version of Solaris 2.6 and above running any version
of RM 6 in which the PCI UltraSCSI host adapter is attached to either
an A3x00 or A1000 array. It is brought on by editing rmparams for
System_MaxLunsPerController=N where N is greater than 8, and then
running add16lun.sh or using genscsiconf. Actually attempting to
create a 9th LUN using RM6 or raidutil will cause the loss of access
which can be restored.
The cause of this problem is the lack of driver knowledge needed from
glm.conf file. Note that if the 9th LUN is actually created, then a
boot -r is not sufficient to remove it and restore communication. The
serial port must be used to remove the 9th LUN.
Furthermore, there is a difference in the glm.conf file needed on
Solaris 7 and Solaris 8 compared to Solaris 2.6. One MUST edit the
glm.conf file when upgrading from Solaris 2.6.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| X | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives and Enterprise Customers to
prevent the above problem can be avoided by properly enabling more than
8 LUN support when using the glm host adapter as described next.
In this example, 16 will be used for the number of LUNs supported.
Note that 16 is the maximum supported with RM 6.1.1. 32 can be
supported with RM 6.22.
1) On Solaris 2.6: Install glm driver patch 105580 or higher
On Solaris 7: Install glm driver patch 106925 or higher
On Solaris 8: No patch is needed
2) Install the other patches for RM6 as defined in Early Notifier 20029.
3) Edit /usr/lib/osa/rmparams as described in the RM 6 Release Notes:
System_MaxLunsPerController=16
It is recommended you make a backup copy of the rmparams file first.
Note: Step 3 is not necessary if you are using the add16/32lun.sh
script(s) on the RM6.22 CD.
4) On Solaris 2.6 edit /kernel/drv/glm.conf file, if it exists, or create
a new one with:
device-type-scsi-options-list =
"Symbios StorEDGE A1000", "lsi-scsi-options",
"Symbios StorEDGE A3000", "lsi-scsi-options",
"SYMBIOS RSM Array 2000", "lsi-scsi-options";
lsi-scsi-options = 0x107f8;
On Solaris 7 and 8 edit /kernel/drv/glm.conf file, if it exists, or
create a new one with:
device-type-scsi-options-list =
"Symbios StorEDGE A1000", "lsi-scsi-options",
"Symbios StorEDGE A3000", "lsi-scsi-options",
"SYMBIOS RSM Array 2000", "lsi-scsi-options";
lsi-scsi-options = 0x407f8;
It is recommended you make a backup copy of the glm.conf file before
editing it.
5) Run add16lun.sh.
As a side note, don't use the add16lun.sh on the RM 6.1.1 CD or
you will lose access to all data on any A1000's attached.
Add16lun.sh is fixed in the RM 6.1.1update1 and 6.1.1update2
releases. These shell scripts are in the /Tools directory on the
CD.
Also note that add32lun.sh is available for RM 6.22 only.
6) Do a reconfiguration reboot, ie boot -r.
7) Now you can create new LUNs above 8.
COMMENTS:
When system is upgraded from Solaris 2.6 to Solaris 7 or 8, then the
last line of the glm.conf must be edited as described in step 4) above.
In particular, the lsi-scsi-options must be changed to 0x407f8.
--------------------------------------------------------------------------
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.