When an A3x00 and the supporting RM6 software is installed. The default 
Solaris LUN support is updated in the OS from 1 to 8 LUNs. Therefore during 
a boot operation or reconfiguation boot operation, Solaris has to scan 8 LUNs on 
each target before scanning the next target. The default targets of the Raid 
Controllers are 4 and 5.

As part of the Raid Manager 6 installation, a modification will have been made 
to the /kernel/drv/sd.conf file.  It will include a Raid Manager section 
for Targets 1-15 and LUNs 1-7 as shown below:

	# BEGIN RAID Manager additional LUN entries
	# DO NOT EDIT from BEGIN above to END below...
	name="sd" class="scsi"
	target=0 lun=1;

	name="sd" class="scsi"
	target=0 lun=2;

	name="sd" class="scsi"
	target=0 lun=3;

	name="sd" class="scsi"
	target=0 lun=4;

	name="sd" class="scsi"
	target=0 lun=5;

	name="sd" class="scsi"
	target=0 lun=6;

	name="sd" class="scsi"
	target=0 lun=7;
	.
	.
	.
	(Middle portion ommitted for reading)
	.
        .
        .
        name="sd" class="scsi"
	target=15 lun=1;
 
	name="sd" class="scsi"
	target=15 lun=2;
 
	name="sd" class="scsi"
	target=15 lun=3;
 
	name="sd" class="scsi"
	target=15 lun=4;
 
	name="sd" class="scsi"
	target=15 lun=5;
 
	name="sd" class="scsi"
	target=15 lun=6;
 
	name="sd" class="scsi"
	target=15 lun=7;
	# END RAID Manager additional lun entries

There are two problems with this:

1. During the booting process of the node, the sd driver will timeout  
   for every non-existent LUN.  If multiple A3x00's or A1000's are attached,
   it can take at least an hour to complete reboot cycle time for supporting
   the first 8 LUNs.  If 16-32 LUNs have to be supported on the A3x00 or 
   the A1000, the reboot cycle time will take even longer to complete.
  
2. During the process of bringing a StorEdge A3500 or A3000 controller
   back online, it will run a drvconfig.  If the sd.conf file contains 
   extra (unused) targets and LUNs, the process for rescanning the 
   device tree for extra (unused) targets and LUNs may even take longer 
   to complete a reboot on an Enterprise 10000 system.

This boot delay problem can be avoided with A3X00 and A1000 by completing 
the procedures below:

This step-by-step procedure should result in an improvement in the reboot 
time, as well as an in improvement in changing the Raid Controller from 
an "offline" state to an "online" state.  The main purpose for this procedure  
is to make sure that the drvconfig doesn't have  to negotiate with non-existent
LUNs.

Note: A3x00 Raid Controllers are Targets 4 and 5 by default setting.

1. From the command prompt, type the following:
	   
   # /etc/raid/bin/lad

   c1t5d0s0 1T92401270 LUNS: 0 1 2 
   c2t5d0s0 1T92401348 LUNS: 0 1 2 
   c3t4d3s0 1T92600542 LUNS: 3 4 5 
   c4t5d0s0 1T92400129 LUNS: 0 1 2 
   c7t4d3s0 1T92401081 LUNS: 3 4 5 
   c8t4d3s0 1T92401082 LUNS: 3 4 5

   Every Raid Controller in these configurations are set to target t4 
   (eg c3[t4]d3s0) or target t5 (c1[t5]d0s0) from the /etc/raid/bin/lad
   output.  These are the target entries that need to be retained in 
   the /kernel/drv/sd.conf file.  These target numbers may vary between
   different configurations.

2. From the command editor, edit the /kernel/drv/sd.conf

   In the "RAID Manager" section, delete ALL targets
   except 4 and 5 which the A3x00's Raid Controllers must use.

3. The new sd.conf for the "RAID Manager" section should look
   like this after the modification:

        # BEGIN RAID Manager additional LUN entries
        # DO NOT EDIT from BEGIN above to END below...
        
        name="sd" class="scsi"
        target=4 lun=1;

        name="sd" class="scsi"
        target=4 lun=2;

        name="sd" class="scsi"
        target=4 lun=3;

        name="sd" class="scsi"
        target=4 lun=4;

        name="sd" class="scsi"
        target=4 lun=5;

        name="sd" class="scsi"
        target=4 lun=6;

        name="sd" class="scsi"
	target=4 lun=7;

        name="sd" class="scsi"
        target=5 lun=1;

        name="sd" class="scsi"
        target=5 lun=2;

        name="sd" class="scsi"
        target=5 lun=3;

        name="sd" class="scsi"
        target=5 lun=4;

        name="sd" class="scsi"
        target=5 lun=5;

        name="sd" class="scsi"
        target=5 lun=6;

        name="sd" class="scsi"
        target=5 lun=7;	
	# END RAID Manager additional LUN entries
	
Note: Targets 4 and 5 LUN 0 are not shown because they have   
      already been defined in the sd.conf near the top.

4. The booting cycle time should be reduced when performing the reboot 
   after saving the file.  A reconfiguration reboot is not necessary  
   on the A3x00(s) or A1000(s).

NOTE: The configuration is not set at targets 4 and 5 by default on 
      every A1000(s), it is necessary to make sure that these entries go 
      into the "RAID Manager" section of sd.conf.  Otherwise after 
      rebooting, the RM6 SW will not see your A1000 Raid Module.
      This procedure may affect third party multi-LUN devices. If the 
      systems have third party multi-LUN devices, verify their target ID 
      setting and make sure you do not disable them with this procedure.

This SRDB has been produced to allow customers access to the
details provided via  

FIN #: I0551-1

systems with large StorEdge A3000, A3500 or A1000 configs.

It has been reproduced in this form with the direct permission of the
FIN author and sponser (who is the NWS Sonoma SW PM).