Disk Enclosures
1753325 Members
4961 Online
108792 Solutions
New Discussion юеВ

Problems with DS2300 and HA

 
Essent Unix Beheer
Occasional Contributor

Problems with DS2300 and HA

Hi,

I'm trying to set up a HA-cluster with 2 DS2300 en 2 rp3440 machines.
The array's have tobe full bus.
But when I try to configure a disk I get errors on both servers.

The errors are:
Oct 26 14:28:32 puthkd10 vmunix: SCSI: Resetting SCSI -- lbolt: 1461135, bus: 6 path: 0/4/1/1
Oct 26 14:28:32 puthkd10 vmunix: SCSI: Reset detected -- lbolt: 1461135, bus: 6 path: 0/4/1/1
Oct 26 14:28:38 puthkd10 vmunix: SCSI: isrEscape Controller at 0/4/1/1.
Oct 26 14:28:38 puthkd10 vmunix: SCSI: lsp is NULL on phase mismatch -- lbolt: 1461700, bus: 6
Oct 26 14:28:38 puthkd10 vmunix: lbp->state: 30008
Oct 26 14:28:38 puthkd10 vmunix: lbp->offset: ffffffff

For the other server:
Oct 26 14:33:26 puthkd11 vmunix: SCSI: Reset detected -- path: 0/4/1/1
Oct 26 14:33:26 puthkd11 vmunix: SCSI: -- lbolt: 1297641, bus: 6
Oct 26 14:33:26 puthkd11 vmunix: lbp->state: 30008
Oct 26 14:33:26 puthkd11 vmunix: lbp->offset: ffffffff

Here are some ioscans from both servers.
PUTHKD10
DISKS:
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 5 0/3/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 6 0/3/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
disk 7 0/4/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 8 0/4/1/1.1.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c6t1d0 /dev/rdsk/c6t1d0

CONTROLERS
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
ctl 0 0/0/2/0.0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 0/0/2/0.1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ctl 2 0/1/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 3 0/1/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
ctl 4 0/3/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ctl 7 0/3/1/0.15.0 sctl CLAIMED DEVICE HP A6491A
/dev/rscsi/c4t15d0
ctl 5 0/4/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c5t7d0
ctl 6 0/4/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0
ctl 8 0/4/1/1.15.0 sctl CLAIMED DEVICE HP A6491A

EXT BUS DEVICES
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
ext_bus 0 0/0/2/0.0 side CLAIMED INTERFACE IDE
ext_bus 1 0/0/2/0.1 side CLAIMED INTERFACE IDE
ext_bus 2 0/1/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
ext_bus 3 0/1/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
ext_bus 4 0/3/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6828-60101
ext_bus 5 0/4/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6829-60101
ext_bus 6 0/4/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6829-60101


PUTHKD11
DISKS:
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 3 0/3/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 5 0/3/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
disk 4 0/4/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 6 0/4/1/1.1.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c6t1d0 /dev/rdsk/c6t1d0

CONTOLERS:
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
ctl 0 0/0/2/0.0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 0/0/2/0.1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ctl 2 0/1/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 3 0/1/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
ctl 4 0/3/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ctl 7 0/3/1/0.15.0 sctl CLAIMED DEVICE HP A6491A
/dev/rscsi/c4t15d0
ctl 5 0/4/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c5t7d0
ctl 6 0/4/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0
ctl 8 0/4/1/1.15.0 sctl CLAIMED DEVICE HP A6491A

EXT BUS DEVICES:
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
ext_bus 0 0/0/2/0.0 side CLAIMED INTERFACE IDE
ext_bus 1 0/0/2/0.1 side CLAIMED INTERFACE IDE
ext_bus 2 0/1/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
ext_bus 3 0/1/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD
ext_bus 4 0/3/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6828-60101
ext_bus 5 0/4/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6829-60101
ext_bus 6 0/4/1/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6829-60101


What am I doing wrong.
Or what am I overlooking.
Could someone pls help out.

Regards,

Pim van der Meer.
3 REPLIES 3
Uwe Zessin
Honored Contributor

Re: Problems with DS2300 and HA

Sounds like you are working with shared SCSI busses...

Did you remember to configure the adapters of your servers to have different SCSI IDs on the same bus?
.
Zygmunt Krawczyk
Honored Contributor

Re: Problems with DS2300 and HA

Hi,

the connection topology should look like at the page 32 in:
http://h200001.www2.hp.com/bc/docs/support/SupportManual/lpg29283/lpg29283.pdf

and the target ID on SCSI controllers on one rp3440 should be set to 6

Regards,
Zygmunt
Essent Unix Beheer
Occasional Contributor

Re: Problems with DS2300 and HA

Thanx.

Changing the SCSI-id did it.

kind regards.

Pim