Betty Crocker 16 LUN CookBook OS requirements: Solaris 2.6 RM6 requirments: 6.1 and above Patch requirements: 105181-xx => 2.6 kernel update patch 105600-xx => 2.6 isp patch for 32 LUN support 105797-xx => 2.6 sd patch xx -> is latest revision of patch Note: If you have Solaris 2.6 5/98, then you have the isp already in there for 32 LUN support. Go to the following location and get the 16 LUN script: http://sunsolve2.Sun.COM/fcs/A1000_A3000/ Steps to be performed: 1. Edit the /usr/lib/osa/rmparams file and adjust the following variable to 16 => System_MaxLunsPerController 2. Go to the /usr/lib/osa/bin directory and run the following script that was installed from the patch you downloaded from sunsolve2. #./add16lun.sh 3. reconfig reboot now run RM6, and your all set for 16 LUN support!!!!! Note: you can certainly use the 16 LUN script from the tools directory on the RM6 cd. The ONLY problem is that if you have a A1000(s) and that unit is targeted anything past 7, you will have the same problem as with the A3000 and folks trying to get > 8 LUNs on there.......if that is the case, you WILL most likely have to wipe the A1000(s) clean and LOSE all access to data on there. To do that, you can perform the following steps to reset the A1000 configuration: 1. Kill RM6 2. power down host and A1000 3. remove battery from A1000 and reinstall the battery after about a minute. 4. REMOVE all drives except the one from the far left.... 5. power up the host, then power up the A1000... what this will do is create a default Raid 0 LUN 0 One final note, PCI systems is still currently limited to 8 LUNs with the devices mentioned above. Observation: When you go to 16 LUN support, let's say you have a 5 drive Raid 5 and your gonna put 15 LUNs on there. You will notice that from LUN 7 and above, after each LUN goes into "optimal" state, you will notice that there is NO disk activity. Even though the RM6 GUI is still showing the remaining LUNs formatting. Within about a minute, the drive activity will come back to life and keep on going. Not sure why this is happening, drive timing or something is my guess, this pattern will continue till the last LUN is created.