On an A3x00 or A1000 configured with LUN numbers greater than 7, LUNS
whose numbers are greater than 7 show up using a different hardware
path that that of LUNS 0 through 7.

This different hardware path will show up in /dev/rdsk, /dev/dsk, as
well as in 'format.'  For an example, see the following snippet from
the output of the 'format' utility:

   8. c3t4d4 <Symbios-StorEDGEA3000-0205 cyl 17192 alt 2 hd 64 sec 64>
      /pseudo/rdnexus@8/rdriver@4,4
   9. c3t4d5 <Symbios-StorEDGEA3000-0205 cyl 17192 alt 2 hd 64 sec 64>
      /pseudo/rdnexus@8/rdriver@4,5
  10. c3t4d6 <Symbios-StorEDGEA3000-0205 cyl 17192 alt 2 hd 64 sec 64>
      /pseudo/rdnexus@8/rdriver@4,6
  11. c3t4d7 <Symbios-StorEDGEA3000-0205 cyl 17192 alt 2 hd 64 sec 64>
      /pseudo/rdnexus@8/rdriver@4,7
  12. c3t4d8 <Symbios-StorEDGEA3000-0205 cyl 17192 alt 2 hd 64 sec 64>
      /sbus@2,0/QLGC,isp@2,10000/sd@4,8
  13. c3t4d9 <Symbios-StorEDGEA3000-0205 cyl 17192 alt 2 hd 64 sec 64>
      /sbus@2,0/QLGC,isp@2,10000/sd@4,9

Notice how LUNs 8 and 9 show a path without the 'rdnexus' and 'rdriver'
paths.      

This problem is usually due to the fact that the '/etc/osa/rmparams'
file has the parameter "System_MaxLunsPerController" set to 8.
 
To fix the problem, set the value of this parameter to the correct
value (typically 16 or 32) and perform a reconfiguration reboot on the
system.
 
 
This problem may manifest itself after any of the following scenarios: 
 
1.  Adding or removing patches or packages that reference the
    /etc/osa/rmparams file.  This might have the effect of setting the
    values in this file back to their defaults.
 
2.  Upgrading the 'rm6' software and forgetting to make this change to
    the rmparams file.
 
3.  Performing the procedure to allow 16 or 32 LUN support, but leaving
    out the step of editing this parameter in this file.