[Veritas-ha] Veritas 1.1.2 Install and scsi-initiator-id
Espen Martinsen
Espen.Martinsen at mnemonic.no
Mon Dec 11 00:03:17 CST 2000
Hi,
I think it's bothe easyier and safer to do this in the
eeprom, and I do it on both machines.
Why? The point here is that none of the machines should have
the same scsi-inititator at any time.
If you use a *.conf file, it would have scsi-initiator=7 until it
resets during readind it's conf-file.
If at that moment the other machine also uses 7, it will get a
scsi-reset, and i.e VxVM will mark the disks as offline. (If you are
unlucky)
SO, what I do is this:
machine 1: sets scsi-initiator to: "2" on both shared JBOD's:
machine1:
{e} ok show-devs
/counter-timer at 7,3c00
/sbus at 7,0
/counter-timer at 6,3c00
/fhc at 6,f8800000
/sbus at 6,0
/counter-timer at 3,3c00
/sbus at 3,0
/counter-timer at 2,3c00
/fhc at 2,f8800000
/sbus at 2,0
/SUNW,UltraSPARC-II at f,0
/SUNW,UltraSPARC-II at e,0
/fhc at e,f8800000
/central at 1f,0
/virtual-memory
/memory at 0,0
/aliases
/options
/openprom
/chosen
/packages
/sbus at 7,0/SUNW,qfe at 0,8c30000
/sbus at 7,0/SUNW,qfe at 0,8c20000
/sbus at 7,0/SUNW,qfe at 0,8c10000
/sbus at 7,0/SUNW,qfe at 0,8c00000
/sbus at 7,0/SUNW,fas at 3,8800000
/sbus at 7,0/SUNW,hme at 3,8c00000
/sbus at 7,0/SUNW,fas at 3,8800000/st
/sbus at 7,0/SUNW,fas at 3,8800000/sd
/fhc at 6,f8800000/sbus-speed at 0,500000
/fhc at 6,f8800000/eeprom at 0,300000
/fhc at 6,f8800000/flashprom at 0,0
/fhc at 6,f8800000/environment at 0,400000
/fhc at 6,f8800000/ac at 0,1000000
/sbus at 6,0/QLGC,isp at 2,10000 -> this one
/sbus at 6,0/SUNW,socal at d,10000
/sbus at 6,0/QLGC,isp at 2,10000/st
/sbus at 6,0/QLGC,isp at 2,10000/sd
/sbus at 6,0/SUNW,socal at d,10000/sf at 1,0
/sbus at 6,0/SUNW,socal at d,10000/sf at 0,0
/sbus at 6,0/SUNW,socal at d,10000/sf at 1,0/ssd
/sbus at 6,0/SUNW,socal at d,10000/sf at 0,0/ssd
/sbus at 3,0/SUNW,qfe at 0,8c30000
/sbus at 3,0/SUNW,qfe at 0,8c20000
/sbus at 3,0/SUNW,qfe at 0,8c10000
/sbus at 3,0/SUNW,hme at 3,8c00000
/sbus at 3,0/SUNW,fas at 3,8800000/st
/sbus at 3,0/SUNW,fas at 3,8800000/sd
/fhc at 2,f8800000/sbus-speed at 0,500000
/fhc at 2,f8800000/eeprom at 0,300000
/fhc at 2,f8800000/flashprom at 0,0
/fhc at 2,f8800000/environment at 0,400000
/fhc at 2,f8800000/ac at 0,1000000
/sbus at 2,0/QLGC,isp at 2,10000 -> and this one
/sbus at 2,0/SUNW,socal at d,10000
/sbus at 2,0/QLGC,isp at 2,10000/st
/sbus at 2,0/QLGC,isp at 2,10000/sd
/sbus at 2,0/SUNW,socal at d,10000/sf at 1,0
/sbus at 2,0/SUNW,socal at d,10000/sf at 0,0
/sbus at 2,0/SUNW,socal at d,10000/sf at 1,0/ssd
/sbus at 2,0/SUNW,socal at d,10000/sf at 0,0/ssd
/fhc at e,f8800000/flashprom at 0,0
/fhc at e,f8800000/sram at 0,200000
/fhc at e,f8800000/environment at 0,400000
/fhc at e,f8800000/simm-status at 0,600000
/fhc at e,f8800000/ac at 0,1000000
/central at 1f,0/fhc at 0,f8800000
/central at 1f,0/fhc at 0,f8800000/clock-board at 0,900000
/central at 1f,0/fhc at 0,f8800000/zs at 0,904000
/central at 1f,0/fhc at 0,f8800000/zs at 0,902000
/central at 1f,0/fhc at 0,f8800000/eeprom at 0,908000
/openprom/client-services
/packages/disk-label
/packages/obp-tftp
/packages/deblocker
/packages/terminal-emulator
{e} ok
{e} ok nvedit
0: probe-all
1: cd /sbus at 2,0/QLGC,isp at 2,10000
2: 2 encode-int " scsi-initiator-id" property
3: device-end
4: cd /sbus at 6,0/QLGC,isp at 2,10000
5: 2 encode-int " scsi-initiator-id" property
6: device-end
7: install-console
8: banner
9:
10:
{e} ok
{e} ok nvstore
{e} ok
setenv use-nvramrc? true
{e} ok
machine 2: sets scsi-initiator to: "3" on both shared JBOD's:
nvedit
{e} ok show-disks
a) /sbus at 7,0/SUNW,fas at 3,8800000/sd
b) /sbus at 6,0/QLGC,isp at 2,10000/sd <- here's #1
c) /sbus at 6,0/SUNW,socal at d,10000/sf at 1,0/ssd
d) /sbus at 6,0/SUNW,socal at d,10000/sf at 0,0/ssd
e) /sbus at 3,0/SUNW,fas at 3,8800000/sd
f) /sbus at 2,0/QLGC,isp at 2,10000/sd <- and here's #2
g) /sbus at 2,0/SUNW,socal at d,10000/sf at 1,0/ssd
h) /sbus at 2,0/SUNW,socal at d,10000/sf at 0,0/ssd
q) NO SELECTION
Enter Selection, q to quit: q
{e} ok nvedit
0: devalias disk /sbus at 2,0/SUNW,socal at d,10000/sf at 0,0/ssd at 0,0
1: probe-all
2: cd /sbus at 2,0/QLGC,isp at 2,10000
3: 3 encode-int " scsi-initiator-id" property
4: device-end
5: cd /sbus at 6,0/QLGC,isp at 2,10000
6: 3 encode-int " scsi-initiator-id" property
7: device-end
8: install-console
9: banner
10:
{e} ok nvstore
{e} ok setenv use-nvramrc? true
use-nvramrc? = true
{e} ok
Done on both!
> I am installing Veritas VCS 1.1.2 and in the install manual under
> Configuring the Network and Storage, there is a section on Modify
> the configuration file of the shared SCSI driver on each system.
>
> It ask to identify the three-letter name and device parent for the
> shared SCSI controller with the following command:
>
> # ls -l shared_disk_partition
> when i do this I get the following:
>
> lrwxrwxrwx 1 root root 57 Dec 6 14:00 /dev/dsk/c1t0d0s7 ->
> ../../devices/pci at 1f,0/pci at 1/pci at 1/SUNW,isptwo at 4/sd at 0,0:h
>
> This identifies the parent as /pci at 1f,0 and and the driver as isptwo.
> In the install manual it has you do a prtconf -v to get the register
> property values for the shared SCSI controller, and show have a display
> that look like the following:
>
> Output resembles:
> QLGC,isp, instance #0
> ...
> Register Specifications: Bus Type=0x0, Address=0x10000, Size=1c2
> ...
>
> My output looks like the following:
>
> virtual-memory (driver not attached)
> pci, instance #0
> Register Specifications:
> Bus Type=0x1fe, Address=0x0, Size=0x10000
> Bus Type=0x1fe, Address=0x1000000, Size=0x100
> Range Specifications:
> Ch: 00,00000000 Pa: 00,000001fe, Sz: 1000000
> Ch: 00,01000000 Pa: 1000000,00000000, Sz: 0
> Ch: 1fe,02000000 Pa: 00,01000000, Sz: 2000000
> Ch: 00,00000000 Pa: 1ff,00000000, Sz: 1
> Ch: 00,03000000 Pa: 00,00000000, Sz: 1ff
> Interrupt Specifications:
> Interrupt Priority=0xe (ipl 14), vector=0x7f0 (2032)
> Interrupt Priority=0xe (ipl 14), vector=0x7ee (2030)
> Interrupt Priority=0xe (ipl 14), vector=0x7ef (2031)
> Interrupt Priority=0xe (ipl 14), vector=0x7e5 (2021)
> pci, instance #0
> Driver properties:
> name <device_type> length <4>
> value <0x70636900>.
> Hardware properties:
> name <latency-timer> length <4>
> value <0x00000040>.
> name <cache-line-size> length <4>
> value <0x00000010>.
>
> This is the only place that has the Register Specification. Further
> down the output i have the following:
>
> SUNW,isptwo, instance #0
> Driver properties:
> name <target1-wide> length <0> -- <no value>.
> name <target1-TQ> length <0> -- <no value>.
> name <target1-sync-speed> length <4>
> value <0x0000a2c2>.
> name <target0-wide> length <0> -- <no value>.
> name <target0-TQ> length <0> -- <no value>.
> name <target0-sync-speed> length <4>
> value <0x0000a2c2>.
> name <scsi-options> length <4>
> value <0x00001ff8>.
> name <scsi-watchdog-tick> length <4>
> value <0x0000000a>.
> name <scsi-tag-age-limit> length <4>
> value <0x00000002>.
> name <scsi-reset-delay> length <4>
> value <0x00000bb8>.
> Hardware properties:
> name <cache-line-size> length <4>
> value <0x00000010>.
> name <interrupts> length <4>
> value <0x00000001>.
> name <device-id> length <4>
> value <0x00001020>.
> name <vendor-id> length <4>
> value <0x00001077>.
> name <reg> length <80>
>
>
> As per the manual you are then to Modify /kernel/drv/driver_name.conf
> on each system to set the SCSI ID for the system to use on the shared bus.
> (Create this file if it does not exist.)
>
> The format for this file is as follows:
>
> name= driver_name parent= parent_name
> reg=register_property_values
> scsi-initiator-id=scsi_id;
>
>
> I have created the following files with no luck. I have only used one
> at a time during the boot -r sequence.
>
> /kernel/drv/isptwo.conf <----- Using the output from above
> name="isptwo" parent="/pci at 1f,0"
> reg=0x1fe,0x1000000,100
> scsi-initiator-id=5;
>
> This did nothing
>
> I then create /kernel/drv/isp.conf <---- Using from what is in the drv dir.
> name="isp" parent="/pci at 1f,0"
> reg=0x1fe,0x1000000,100
> scsi-initiator-id=5;
>
>
> This gives me a warning:
>
> WARNING: cannot merge prototype from isp.conf.
>
> I have tried using the information from both line under Register
> Specifications: with no luck.
>
>
> The manual stateds that after the boot -r I should see something like
>
> isp0: initiator SCSI ID now 5.
>
> Am I doing something wrong, missing something or is the manual wrong?
>
> I know how to set the scsi-initiator-id from the ok prom and get the
> system to come up with the output as above:
> isp0: initiator SCSI ID now 5.
>
> I wanted to be able to do the proccedure from the manual.
>
> I have the following Software and hardware:
>
> Enterprise 10 server with 4 9.1GB disk drive that will be shared between
> the systems in the cluster. Software is Solaris 8 11/99.
>
> Thanks for any help on this, I will send more information if needed.
>
> /mdb
>
>
>
>
>
> _______________________________________________
> Veritas-ha maillist - Veritas-ha at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha
Mvh
--------------------------------------------------------------
Espen Martinsen Email : esm at mnemonic.no
Mnemonic AS, Waldemar Thranesgt. 77 Phone : +47 2299 9710/00
N-0175 Oslo, NORWAY Fax : +47 2299 9701
--------------------------------------------------------------
(PADI AOW 87191) http://www.pogostick.net/~esm
More information about the Veritas-ha
mailing list