Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

SOLVED
Go to solution
R Cardwell
Advisor

Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Hi,

I though I would give this forum a try especially after the amount of help I got from the ITO section. I am currently building a service guarded L-class cluster using 2 L-Class servers and a single DS2300 (which I know doesn't give fully redundancy, but it was decided by management it provided sufficient failover for our needs).

Now what I have done is configured the DS2300 in full mode mode (and SES) and using dual port SCSI adapters (A5150A cards, which I believe support multi-initiator buses) connected one server to one BCC (and terminated the 2nd connector on the BCC) and the other server to the 2nd BCC (and likewise terminated the second SCSI connector), now this seems to work for a little while, then the syslog starts filling up with these messages, and ioscan/disk access starts to hang for long periods of time:

Apr 14 14:48
...
STAT: 80, DSPS: 99fbe5c1
lsp: 0000000000000000
lbp->owner: 0000000000000000
scratch_lsp: 0000000000000000
Pre-DSP script dump [ffffffff99fbe348]:
60000008 00000000 60000040 00000000
0f000000 99fbe5c1 98080000 00000007
Script dump [ffffffff99fbe368]:
0f000001 99fbe5c1 80840000 fffffea8
7c027f00 00000000 60000040 00000000
SCSI: Resetting SCSI -- lbolt: 33955752, bus: 5
SCSI: Reset detected -- lbolt: 33955752, bus: 5
SCSI: Reset detected -- lbolt: 33955757, bus: 5
SCSI: Reset detected -- lbolt: 33956254, bus: 5
SCSI: lsp is NULL on phase mismatch -- lbolt: 33993319, bus: 5
lbp->state: 4060
lbp->offset: ffffffff
lbp->uPhysScript: 99fbe000
From most recent interrupt:
ISTAT: 0a, SIST0: 90, SIST1: 00, DSTAT: 80, DSPS: 99fbe5c1
lsp: 0000000000000000
lbp->owner: 0000000000000000
scratch_lsp: 0000000000000000
Pre-DSP script dump [ffffffff99fbe348]:
60000008 00000000 60000040 00000000
0f000000 99fbe5c1 98080000 00000007
Script dump [ffffffff99fbe368]:
0f000001 99fbe5c1 80840000 fffffea8
7c027f00 00000000 60000040 00000000
SCSI: Resetting SCSI -- lbolt: 33993419, bus: 5
SCSI: Reset detected -- lbolt: 33993419, bus: 5
SCSI: Reset detected -- lbolt: 33993919, bus: 5
lbp->state: 4060
lbp->offset: ffffffff
lbp->uPhysScript: 99fbe000
From most recent interrupt:
ISTAT: 02, SIST0: 02, SIST1: 00, DSTAT: 80, DSPS: 99fbe028
lsp: 0000000000000000
lbp->owner: 0000000000000000
scratch_lsp: 0000000000000000
Pre-DSP script dump [ffffffff99fbe0e0]:
e0340004 00000000 e0100004 00000000
48000000 00000000 78350000 00000000
Script dump [ffffffff99fbe100]:
50000000 99fbe028 80000000 0000000b
0f000001 99fbe5c0 60000040 00000000
SCSI: lsp is NULL on phase mismatch -- lbolt: 33994421, bus: 5
lbp->state: 4060

+ lots more.

Now I am assuming that these errors are due to multiple initiators on a single shared bus, the whole channel is getting reset all as they fight for control, is this right? if so how should I connect up the two servers to a single disk array so they can access a shared volume group?

Any help that can be provided would be much appreciated.


Rich Cardwell.
7 REPLIES
Michael Steele_2
Honored Contributor
Solution

Re: Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Bus 5 can be identified with:

ioscan -fknC ext_bus

It should be target number 5.

Check your SCSI terminations.

Also check your disk firmware levels with diskinfo and pv timeouts:

diskinfo -v /dev/rdsk/cXtYdZ
pvchange -v /dev/dsk/cXtYdZ

To change timeouts.

pvchange -t 180 /dev/dsk/cXtYdZ

Peruse this document and take special note of figure 4-1 and pages 68 to 72.

http://docs.hp.com/hpux/pdf/B3936-90024.pdf

Also refer to LOGTOOL and verify in ioscan that all is unique. In LOGTOOL look for HW errors:

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY.

Note the first and last dates of transactions and calculate the difference. If the difference is short, like 4 hours, then this is important to note. Now read down the report of hardware addresses and observe the integer numbers in parenthesis. Anything over 150 in this 4 hour period should be called into HP for replacement.
Support Fatherhood - Stop Family Law
Eugeny Brychkov
Honored Contributor

Re: Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Rich,
you're absolutely correct. As soon as DS2300 in full bus config, both BCCs are forming one logical bus (not physical, but logical). This means that all devices connected to both BCCs should have different SCSI Ids. In your case, when you're connecting dual ported HBA to the same bus, they (ports) have same SCSI Id=7. So you need to change SCSI Id of one of them. To do it stop machine booting in PDC, and use 'SCSI' command to change SCSI Id.
Good luck!
Eugeny
R Cardwell
Advisor

Re: Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Hi Michael,

Thanks for the response, yes Bus 5 is the SCSI adaptor connected to the DS2300, on the other node Bus 4 is being reset, as that is the other adaptor connected to the DS2300. So that makes sense as I see it.

As for the documentation, Is there anyway to reset the initiator ID on the SCSI cards (its a A5150A I think) so that it appears as 7 on one card and 6 on the other? (as mentioned in the table in the docs) I know you could do this with the HBA in D-Class's via dip-switches, however there doesn't appear to be anyway to adjust this on the newer cards.

I will try and find some new terminators to see if that helps.

Rich Cardwell.

All the disks appear to have HP05 firmware.

ie disk info o/p:
/riccsu -> diskinfo -v /dev/rdsk/c4t0d0
SCSI describe of /dev/rdsk/c4t0d0:
vendor: HP 36.4G
product id: ATLAS10K3_36_SCA
type: direct access
size: 35566480 Kbytes
bytes per sector: 512
rev level: HP05
blocks per disk: 71132960
ISO version: 0
ECMA version: 0
ANSI version: 2
removable media: no
response format: 2
(Additional inquiry bytes: (32)55 (33)4d (34)47 (35)56 (36)4b (37)36 (38)46 (
39)20 (40)20 (41)20 (42)20 (43)51 (44)55 (45)41 (46)4e (47)54 (48)55 (49)4d (50)
20 (51)c (52)0 (53)0 (54)0 (55)0 (56)0 (57)0 (58)0 (59)0 (60)0 (61)0 (62)0 (63)0
(64)0 (65)0 (66)0 (67)0 (68)0 (69)0 (70)0 (71)0 (72)0 (73)0 (74)0 (75)0 (76)0 (
77)0 (78)0 (79)0 (80)0 (81)0 (82)0 (83)0 (84)0 (85)0 (86)0 (87)0 (88)0 (89)0 (90
)0 )
Michael Steele_2
Honored Contributor

Re: Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Found a typo:

pvchange -v /dev/dsk/cXtYdZ

...should be

pvdisplay
Support Fatherhood - Stop Family Law
Vincent Abad
Advisor

Re: Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Hi Richard,

Follow this procedure to change the SCSI initiator of a host:

1. If the machine has already been booted, you may get the H/W path of the initiator
before rebooting. Go directly to step 2 otherwise and refer to [1].
1.1. ioscan
1.2. Note the two paths of ext_bus of SCSI cards to shared disks
1.3. shutdown -r 0
2. Interrupt the boot of the machine
2.1. As soon as the message ???Press any key within 10 seconds to stop boot??? is
displayed, press a key.
3. Go into ???Information menu??? and get the path of SCSI cards:
3.1. IN
3.2. IO
3.3. Note the path associated to type: ???SCSI bus cntlr???. Several path correspond to
SCSI card for shared disk. Refer to [1] to know which are concerned in
your configuration.
4. Go into ???Main menu??? then ???Service Menu???:
4.1. SER
5. For each card linked to the shared disk, configure initiator with command:
5.1. scsi init 6 (or 14) where = 0/4/0/0 for instance
6. Check your new configuration
6.1. scsi
7. You may then boot your machine

I'll hope it help you,

--Vincent
R Cardwell
Advisor

Re: Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Yep that fixed it, when I initially booted up I checked the scsi command but couldn't see the HBA's so I assumed you couldn't changed the id's.

So I have now set one to 6 and one to 7 and everything appears to be working.

The only little oddity left now, is when I do an I/O scan on each system I can see only one initaitor on the bus with the drives, where I expected to see both.

Thanks for all you help with this.

Rich Cardwell
Vincent Farrugia
Honored Contributor

Re: Problems connecting 2 L-Class to a Single DS2300 (SCSI Lbolt errors)

Hello,

You can't see both the simple reason that the other initiator is on the other server. Ioscan only scand hardware from the local server.

HTH,
Vince
Tape Drives RULE!!!