host - A500 is connected DS2300 full bus Mode with error

Jung.S.H — Thu, 21 Oct 2004 09:12:54 GMT

host - A500 and DS2300 full bus Mode error

HBA - BCC HBA - BCC
A500 has two SCSI card ( Ultra 160 ) - scsi id is 7
Each SCSI port on a BCC is connected to a host HBA in the same host.
STM log is OK

Split Bus Mode is no error but full bus Mode is error.

** log ***************************************************************
sometimes /dev/rscsi/c4t15d0 is NO_HW and sometimes /dev/rscsi/c4t15d0 is CLAIMED
#ioscan -fnCctl
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 0/0/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ctl 2 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 3 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
ctl 4 0/4/0/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ctl 6 0/4/0/0.15.0 sctl NO_HW DEVICE HP A6491A
/dev/rscsi/c4t15d0
ctl 5 0/6/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c5t7d0
ctl 7 0/6/2/0.15.0 sctl CLAIMED DEVICE HP A6491A
/dev/rscsi/c5t15d0
*** Dmesg ***************************************************************
lsp: 0x0000000044023b80
bp->b_dev: cb05f202
scb->io_id: 500014e
lsp: 0x0000000000000000
DSAtbl->host_iocb_index: 1
DSAtbl->host_iocb_addr: a5800
scb->cdb: 12 00 00 00 24 00 scratch_lsp: 0x0000000000000000
c8xx_iocb [fffffffffa7deb00]:
01005840 ff007f00 000a1040 770f0000
00000005 000a5820 00000006 000a5828

lbolt_at_timeout: 0, lbolt_at_start: 0
lsp->state: 5
Pre-DSP script dump [fffffffffa7de330]:
80840000 00000760 745c0200 00000000
888c0000 fffffd50 88880000 fffffcb0
c8xx_iocb [fffffffffb7deb00]:
0100d840 ff007f10 000a9040 770f0000
00000005 000ad820 00000006 000ad828
Script dump [fffffffffa7de350]:
48000000 00000000 7c5cf000 00000000
7c360000 00000000 745c3000 00000000
Pre-DSP script dump [fffffffffb7de218]:
74358000 00000000 80840000 00000658
f1640004 00000008 7a5c0100 00000000
NCR chip register dump for: 0x400200a
Script dump [fffffffffb7de238]:
1e000000 00000010 878b0000 000002a8
1a000000 00000018 e27c0004 000a8700
00: NCR chip register dump for: 0x400200a
SCNTL3: 77 00: SCNTL2: 00 SCNTL3: 77 SCNTL1: 00 SCNTL2: 80 SCNTL0: ca
SCNTL1: 00 04: SCNTL0: da
GPREG: 0b 04: SDID: 00 GPREG: 0b SXFER: 00 SDID: 0f SCID: 47
SXFER: 00 08: SCID: 47
SBCL: 00 08: SSID: 00 SBCL: 00 SOCL: 00 SSID: 00 SFBR: 00
SOCL: 00 0c: SFBR: 00
SSTAT2: 02 0c: SSTAT1: 00 SSTAT2: 02 SSTAT0: 00 SSTAT1: 08 DSTAT: 80
SSTAT0: 00 10: DSA: fa7deb00
DSTAT: 00
14: 10: DSA: fb7deb00
MBOX1: 00 14: MBOX0: 00 MBOX1: 00 ISTAT1: 00 MBOX0: 00 ISTAT: 20
ISTAT1: 00 1c: TEMP: 00000000
ISTAT: 00
24: DCMDDBC: 00000000
1c: TEMP: 00000000
28: DNAD: 00000000
24: DCMDDBC: 1e000000
2c: DSP: fa7de358
28: DNAD: 000ad828
30: DSPS: 00000000
2c: DSP: fb7de240
34: SCRATCHA: ff000000
30: DSPS: 000ad820
38: 34: SCRATCHA: ff077f10
DCNTL: a1 38: DWT: 00 DCNTL: a1 DIEN: 7f DWT: 00 DMODE: 4c
DIEN: 7f 3c: ADDER: fa7de358
DMODE: 4c
40: 3c: ADDER: fb88ba60
SIST1: 00 40: SIST0: 00 SIST1: 00 SIEN1: 97 SIST0: 00 SIEN0: 8f
SIEN1: 97 44: SIEN0: 8f
GPCNTL: 2f 44: MACNTL: 00 GPCNTL: 2f SWIDE: 00 MACNTL: 00 SLPAR: 00
SWIDE: 00 48: SLPAR: 00
RESPID1: 00 48: RESPID0: 80 RESPID1: 00 STIME1: 00 RESPID0: 80 STIME0
: fc
STIME1: 00 4c: STIME0: fc
STEST3: 80 4c: STEST2: 00 STEST3: 80 STEST1: 0c STEST2: 00 STEST0: 07
STEST1: 0c 50: STEST0: 07
RESV50: 00 50: RESV51: c0 RESV50: 00 SIDL1: 00 RESV51: c0 SIDL0: c2
SIDL1: 00 54: SIDL0: c0
CCNTL1: 01 54: CCNTL0: 01 CCNTL1: 01 SODL1: 00 CCNTL0: 01 SODL0: 00
SODL1: 00 58: SODL0: 00
RESV58: 00 58: RESV59: 00 RESV58: 00 SBDL1: 00 RESV59: 00 SBDL0: 00
SBDL1: 00 5c: SCRATCHB: 00000000
SBDL0: 00
60: SCRATCHC: c0ffffff
5c: SCRATCHB: 000f0001
64: SCRATCHD: 00000000
60: SCRATCHC: c0ffffff
68: SCRATCHE: fa7dec00
64: SCRATCHD: 000a9040
6c: SCRATCHF: 000a0000
68: SCRATCHE: fb7dec00
70: SCRATCHG: ff010301
6c: SCRATCHF: 000a8000
74: SCRATCHH: 000a5600
70: SCRATCHG: 770f0000
78: SCRATCHI: ff017700
74: SCRATCHH: 000ad600
7c: SCRATCHJ: 00000000
78: SCRATCHI: ff017700
bc: SCNTL4: 00
7c: SCRATCHJ: 0100d840
PCI configuration register dump:
bc: SCNTL4: 00
Command: 0157
PCI configuration register dump:
Latency Timer: ff
Command: 0157
Cache Line Size: 10
Latency Timer: ff
Cache Line Size: 10
SCSI: Ultra160 Controller at 0/4/0/0: Error: The domain validation test for target 15 determined tha
t communication may not be possible to this target. Verify the hardware configuration.
SCSI: Ultra160 Controller at 0/6/2/0: Error: The domain validation test for target 15 determined tha
t communication may not be possible to this target. Verify the hardware configuration.
scsi_probe: when probing target 15, lun 1 (dev=cb04f100): couldn't probe lun 0 (no longer responding
?)

I have to Full Bus Mode setting and alternate path setting.
how to configration full bus mode ?

Re: host - A500 is connected DS2300 full bus Mode with error

Zygmunt Krawczyk — Fri, 22 Oct 2004 05:01:16 GMT

Hi,

if you want to connect the ds2300 to dual SCSI controller of the same host, you must set up the ds2300 to split bus mode.

Regards,
Zygmunt

Re: host - A500 is connected DS2300 full bus Mode with error

Zygmunt Krawczyk — Fri, 22 Oct 2004 05:04:35 GMT

Hi,

read the doc:
"hp StorageWorks disk system 2300
user's guide"

http://h200006.www2.hp.com/bc/docs/support/SupportManual/lpg29283/lpg29283.pdf

Regards,
Zygmunt

Re: host - A500 is connected DS2300 full bus Mode with error

Luk Vandenbussche — Fri, 22 Oct 2004 06:05:47 GMT

You have to put it in split bus mode or change the scsi id off on card.
You must change the scsi id to a not used id.

Change your scsi id in SERvice mode at the startup screen

topic Re: host - A500 is connected DS2300 full bus Mode with error in Disk

host - A500 is connected DS2300 full bus Mode with error

Re: host - A500 is connected DS2300 full bus Mode with error

Re: host - A500 is connected DS2300 full bus Mode with error

Re: host - A500 is connected DS2300 full bus Mode with error