[SunHELP] D1000/Multiple Hosts/Initiator IDs

Mon Mar 11 12:01:25 CST 2002

The attacked file may help.  I don't remember the SunDoc number, but here
the contents of the doc are in the attachment.

Dennis Lund

-----Original Message-----
From: Josh Greenberg [mailto:mustard_greens at yahoo.com]
Sent: Monday, March 11, 2002 11:41 AM
To: sunhelp at sunhelp.org
Subject: [SunHELP] D1000/Multiple Hosts/Initiator IDs

Hey folks,

After spending too enough hours to make my eyes burn
at suns site and various mailing lists, im gonna suck
it up and post.

I have a U1 creator and a U2 running SOlaris 8. I have
added a UWDIS card to both hosts that are connected to
one D1000 that is bridged for HA purposes.  However, I
cant find any info on changing the scsi-initiator-id
for the second host's UWDIS card. I am pretty sure
that the tweak has to go into /kernel/drv/isp.conf or
something, but finding how to do it has me stuck.  

This stems from getting frequent scsi bus resets when
both hosts are powered on, or system hangs when the
second host has had its initiator id changed in prom
(im guessing that is because the proom setting applies
to the internal scsi bus, and it cant find the boot
disks anymore).  

Can someone *please* help.  My head hurts from
searching for an answer at this point.  EIther a clear
how-to or a pointer to the appropriate documentation
would be great.  If I am not on the right track, the
appropriate correction would be appreciated.

Thanks, Josh

=====
"Come the millennium, month 12, in the home of greatest power, The village
idiot will come forth to be acclaimed the leader." 
--Nostradamus
Try FREE Yahoo! Mail - the world's greatest free email!
http://mail.yahoo.com/
_______________________________________________
SunHELP maillist  -  SunHELP at sunhelp.org
http://www.sunhelp.org/mailman/listinfo/sunhelp

<html>
<body>
<font size="3" face="Times New Roman"><span style="mso-fareast-font-family: Times New Roman; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
<span style="font-size:10.0pt;font-family:Times New Roman;
mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:
EN-US;mso-bidi-language:AR-SA"></span><font face="Times New Roman" size="3"><span style="mso-fareast-font-family:Times New Roman; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.</span></font></p>
</body>
</html>
Setting the scsi-initiator-id on PCI Systems (E250/E450)....

(26 March 2001)

Shared storage in clusters uses the Multi-Initiator capability of the SCSI
specification. PCI systems use PCI host adapter cards for the SCSI interface.
Otherwise, the operation is the same as in SBus systems. The scsi-initiator-id
must be changed because you cannot have two controllers (or SCSI devices) with
the same SCSI ID on the same SCSI chain. This is true for all shared storage.

However, the scsi-initiator-id of controllers that link private storage should
be returned to 7 or it will conflict with the SCSI ID 6 of the CD-ROM. Also,
for 6-slot MultiPacks you must change the SCSI IDs to the 9-14 range. Use the
switch on the back of the MultiPack to change this.

The normal documented procedure for setting up dual-hosted MultiPacks is to
set the scsi-initiator-id for one node to 6 and then reset specific SCSI
adaptors (ones that are not attached to the dual-hosted disks) to 7. The
scsi-initiator-id for the other node attached to the disk must be left at the
default setting (7). This approach may be somewhat error-prone because you can
get SCSI errors if you do not reset ALL of the adaptors that are NOT attached
to the dual-hosted disks to 7.

A method that works well is to leave the scsi-initiator-id for both nodes to
7. Then, set the scsi-initiator-id for ONLY the adaptors that are connected to
the dual-hosted disk to 6 on one of the nodes (normally the second node). Do
NOT change jumper settings on any SCSI device (CD-ROM). Do NOT change the
scsi-initiator-id to 8 because it will cause a conflict with some other
storage devices (D1000).

Only change the scsi-initiator-id on one node in the chain of the dual-hosted
SCSI device. At the ok (OBP) prompt, use the probe-scsi-all command to
identify the controllers connected to the shared storage and those connected
to private storage. You may have to first do a reset-all before the
probe-scsi-all command will work. Depending on your configuration, there are
two methods of doing this.

Method 1
Note: Use Method 1 if your system is a Sun Enterprise 450.

If more controllers are connected to private storage than controllers
connected to shared storage, more scsi-initiator-id 7s than scsi-initiator-id
6s, or more private storage controllers than shared storage controllers:

Note: Steps 1 through 5 should be done on one of the nodes attached to the
disk. Step 6 needs to be done on both nodes (assuming you are not using Ultra
SCSI):

1. Edit or create the nvramrc to set the scsi-initiator-id to 6 for these
devices. From the OBP enter:

ok nvedit
ok probe-all install-console banner
ok cd /pci at 6,4000/scsi at 3
ok 6 " scsi-initiator-id" integer-property
ok device-end
ok cd /pci at 6,4000/scsi at 2,1
ok 6 " scsi-initiator-id" integer-property
ok device-end

2. Do a ctrl-c, and store the nvramrc:

ok nvstore

3. Evaluate the nvramrc:

ok nvramrc evaluate

4. Set the system to use the nvramrc:

ok setenv use-nvramrc? true

5. Do a reset:

ok reset-all

6. Edit the /etc/system file (on both nodes) and add the following line to set
fast/wide SCSI (disable Ultra SCSI):

set scsi_options=0x3f8

7. Boot both systems and verify that you can see the multi-hosted disks from
both nodes.

Method 2
If the system is not an Enterprise 450, and there are more controllers
connected to shared storage than controllers connected to private storage,
more scsi-inititator-id 6s than scsi-initiator-id 7s, or more shared storage
controllers than private storage controllers, then:

1. Set the global scsi-initator-id to 6:

ok setenv scsi-initiator-id 6
scsi-initiator-id = 6

2. Edit or create the nvramrc script and set the scsi-initiator-id of the
controllers connected to private storage to 7. The line number (0:, 1:, and so
on) are printed by the OBP, for example:

Caution - Insert EXACTLY one space after the double quote and before
scsi-initiator-id.

nvedit
0: probe-all
1: cd /sbus at 70,0/SUNW,fas at 1,8800000
2: 7 encode-int " scsi-initiator-id" property
3: device-end
4: cd /sbus at 70,0/QLGC,isp at 0,10000
5: 7 encode-int " scsi-initiator-id" property
6: device-end
7: cd /sbus at 50,0/SUNW,fas at 1,8800000
8: 7 encode-int " scsi-initiator-id" property
9: device-end
10: install-console
11: banner [Control C]
ok

In this example, you have set three controller scsi-initiator-ids to 7. Your
script may be different because you will be resetting controllers that were
listed by the probe-scsi-all command.

3. Store or discard the changes.

ok nvstrore
ok

ok nvquit [This will discard the changes]
ok

4. Enter the nvedit command to create and store an nvramrc script.

ok set use-nvramrc? = true
ok reset-all

5. Connect the shared storage devices and then enter:

ok boot -r