Sun Storage D1000 Array
 
Solaris Cluster
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
 

A confict can exists between SCSI initiator IDs'.
This article addresses this problem.
The following shows the output of a format command and SCSI error
messages in a faulty configuration:
# format
Searching for disks...done
....
2. c3t0d0 <drive not available: formatting>
/pci@8,700000/scsi@2/sd@0,0
3. c3t1d0 <drive not available: formatting>
/pci@8,700000/scsi@2/sd@1,0
# more /var/adm/messages
Jul 16 10:36:01 deneir scsi: [ID 107833 kern.warning] WARNING:
/pci@8,700000/scsi@2 (glm2):
Jul 16 10:36:01 deneir  got SCSI bus reset
Jul 16 10:36:01 deneir genunix: [ID 611667 kern.info] NOTICE: glm2: got
SCSI bus reset
Jul 16 10:36:05 deneir genunix: [ID 405830 kern.warning] WARNING: Device
sd31 failed to power up.
Jul 16 10:37:54 deneir  unexpected SCSI interrupt while idle
Jul 16 10:51:13 deneir scsi: [ID 107833 kern.warning] WARNING:
/pci@8,700000/scsi@2,1/sd@8,0 (sd52):
Jul 16 10:51:13 deneir scsi: [ID 107833 kern.warning] WARNING:
/pci@8,700000/scsi@2/sd@1,0 (sd31):

(Note: to share the Sun StorEdge D1000 disks with two hosts, the only disk
management supported by Sun is under Sun[TM] Cluster control)
This problem is produced because the scsi-initiator-id variable is set to 7
on both nodes.
To fix the problem we need to change the scsi-initiator-id to 6 on one of
the nodes.
The procedure below explains how to do this:
1.- Edit the nvramrc script to change the scsi-initiator-id for the host
adapters on the first node.
The following examples sets the scsi-initiator-id to 6 for SBUS and PCI based machines respectively. The OpenBoot PROM Monitor prints the line numbers (0:, 1:, and so on).
(Note: Insert exactly one space after the first double quote and before
scsi-initiator-id)
SBUS-example:
{0} ok nvedit
0: probe-all
1: cd /sbus@1f,0/QLGC,isp@3,10000
2: 6 encode-int " scsi-initiator-id" property
3: device-end
4: cd /sbus@1f,0/
5: 6 encode-int " scsi-initiator-id" property
6: device-end
7: install-console
8: banner [Control C]
{0} ok
PCI-example:
{0} ok  nvedit
0:  probe-all install-console banner
1:  cd /pci@6,4000/scsi@3
2:  6 " scsi-initiator-id" integer-property
3:  device-end
4:  cd /pci@6,4000/scsi@2,1
5:  6 " scsi-initiator-id" integer-property
6:  device-end
7:  banner [Control C]
{0} ok
2.- Store the changes.
The changes you make through the nvedit command are recorded on a temporary
copy of the nvramrc script. You can continue to edit this copy without
risk. After you complete your edits, save the changes. If you are not sure
about the changes, discard them.
2.1- To store the changes, at the ok prompt, type:
{0} ok nvstore
{0} ok
2.2 - To discard the changes, type:
{0} ok nvquit
{0} ok
Verify the contents of the nvramrc script you created in Step 7, as shown
in the following example.
If the contents of the nvramrc script are incorrect, use the nvedit command
to make corrections.
{0} ok printenv nvramrc
nvramrc =             probe-all
cd /sbus@1f,0/QLGC,isp@3,10000
6 encode-int " scsi-initiator-id" property
device-end
cd /sbus@1f,0/
6 encode-int " scsi-initiator-id" property
device-end
install-console
banner
{0} ok
After nvramrc had been reviewed, you have to instruct the OpenBoot PROM
(OBP) Monitor to use the nvramrc script, as shown in the following example.
{0} ok setenv use-nvramrc? true
use-nvramrc? = true
{0} ok
At this step, we are ready to boot the dual hosted Sun StorEdge D1000 .

This solution has no attachment