It is desired to connect 2 nodes to a single disk-pack for the purpose of shared storage
or clustering. However, there will be a conflict of device IDs because both machines' 
scsi-initiator-id is defaulted to 7. How can this scsi-initiator-id be changed to another
number without affecting other devices ?

There are basically 2 ways to change the scsi-initiator-id.

1) Simply go to the OpenBoot prompt (ok prompt) of one of the machines and 
change the scsi-initiator-id accordingly.
 
#### Steps to take:
ok setenv scsi-initiator-id 6
ok reset-all

NOTE:
Since the CD-ROM's scsi-initiator-id is 6 as well, it will be disabled for that
machine. The setenv variable will change ALL adapters on the system, thus
making 
the CD-ROM drive useless on the built in SCSI adapter.
This may be a probable solution if one does not require the use of that 
CD-ROM. The other machine with initiator-id remaining at 7, can still make use 
of its CD-ROM.


2) This is a better solution because it only changes the initiator-id on the 
adapters that need to be changed. The CD-ROM remains functional after the
change.

Go to the OpenBoot prompt and follow the steps accordingly:

### These steps to find out relavant adapters' paths:
ok set NVRAM auto-boot? false
ok reset-all
ok probe-scsi-all

### These steps to edit the nvramrc script, to run 
### at bootup, to change the scsi-initiator-id:
ok nvedit
   0 probe-all
   1 cd /sbus@1f,0/SUNW,fas@2,8800000
   2 6 encode-int " scsi-initiator-id" property
   3 device-end
   4 cd /sbus@1f,0/SUNW,fas@0,8800000
   5 6 encode-int " scsi-initiator-id" property
   6 device-end
   7 install-console
   8 banner
   <CTRL-C>
ok nvstore
ok setenv use-nvramrc? true
ok reset-all

NOTE:
At step 1 and 4, the paths were taken from "ok probe-scsi-all".
At step 2 and 5, there is a white space between the first (") and scsi.
Remember also to save the nvramrc script by executing "nvstore"
and set to use nvramrc script at bootup by executing "setenv use-nvramrc? true"