cancel
Showing results for 
Search instead for 
Did you mean: 

Model 20

SOLVED
Go to solution
David Gwin_1
Advisor

Model 20

I have an old K220 800 system with a disk array Model 20 (A3232A) that I have recently reassembled the hardware (it had been out of service for about 5 years) and, then after the system was up and running, I upgraded the OS to 10.20 (I know how old the system is but it is all that I have). I have applied the OS patch PHCO_23261 (and a few other patches). The problem that I am having is that it takes an exceptionally long time to read and write (including moving and deleting) to the disk array. I believe that all of kernel parameters tuned correctly. Can anyone out there dust off your memory cells and tell me why the disk array access would be so slow? Also, the SCSI cable from the system goes to the disk array SCSI-B and then terminated. There is also a SCSI-A but there is nothing plugged into it. Should the system connect to the disk array SCSI-A and then a SCSI jumper cable to SCSI-B and then terminate???

Thank you
David
1 REPLY
Thomas J. Harrold
Trusted Contributor
Solution

Re: Model 20

Sounds like you have a NIKE (aka clariion) array. It has been a while....

There are two controller (A and B) on a model 20. When you bind a lun, you assign it to one of the two controllers. It is possible that the LUNs were bound to Controller A. You can move the cable to SCSI-A, and do a full ioscan (#ioscan -funC disk) to see if new devices are created. (then #insf to actually build the device files)

NIKE arrays, if configured properly, will allow LUNs to be "failed over" (autotresspass is the term they use) to the other controller.

Best bet is to connect a dumb terminal, or a laptop running a terminal emulator to the NIKE, and see how the array was configured.

There are some tweaks that can be made to the cache settings, etc.

Usually when I saw poor performance, it was due to SCSI errors. Check the output of the dmesg command to see if you are receiving SCSI lbolt errors. These result from a bad terminator, or bad cable, and sometimes from a bad host SCSI card.

Hope this helps. If you get the terminal connected to the NIKE, let me know. I can probably dig up some documentation....

-tjh
I learn something new everyday. (usually because I break something new everyday)