Operating System - Tru64 Unix
1748228 Members
4467 Online
108759 Solutions
New Discussion юеВ

Re: Tuning HSZ raid controllers

 
cub
Occasional Contributor

Tuning HSZ raid controllers

A consultant visited us last week and dropped us some recommendations. He advised us to tune the HSZ bus from the OS (Tru64) to increase raid performance. Can someone please advise how to set these HSZ values as below?


Tuning Suggestion: HSZ bus 0 target 1 lun 0 ( this ) has a miss set CACHE_FLUSH_TIMER ( 10 ), which may be set to 45 or more seconds.

тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 0 target 1 lun 0 has MAX_READ_CACHED_TRANSFER_SIZE set to 32; You may want to set MAX_READ_CACHED_TRANSFER_SIZE to 256 or higher depending on your application needs.

тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 0 target 1 lun 0 has MAX_WRITE_CACHED_TRANSFER_SIZE set to 32; You may want to set MAX_WRITE_CACHED_TRANSFER_SIZE to 256 or higher depending on your application needs.

тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 0 target 1 lun 0 ( other ) has a miss set CACHE_FLUSH_TIMER ( 10 ), which may be set to 45 or more seconds.
тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 1 target 0 lun 0 has MAX_READ_CACHED_TRANSFER_SIZE set to 32; You may want to set MAX_READ_CACHED_TRANSFER_SIZE to 256 or higher depending on your application needs.
тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 1 target 0 lun 0 has MAX_WRITE_CACHED_TRANSFER_SIZE set to 32; You may want to set MAX_WRITE_CACHED_TRANSFER_SIZE to 256 or higher depending on your application needs.
тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 1 target 0 lun 0 ( other ) has a miss set CACHE_FLUSH_TIMER ( 10 ), which may be set to 45 or more seconds.
тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 1 target 0 lun 0 has MAX_READ_CACHED_TRANSFER_SIZE set to 32; You may want to set MAX_READ_CACHED_TRANSFER_SIZE to 256 or higher depending on your application needs.
тАв HS* RAID Controllers
Tuning Suggestion: HSZ bus 1 target 0 lun 0 has MAX_WRITE_CACHED_TRANSFER_SIZE set to 32; You may want to set

MAX_WRITE_CACHED_TRANSFER_SIZE to 256 or higher depending on your application needs.

тАв KZPCC RAID Controllers
Operational: SWCC RAID controller drives were detected, but the steamd daemon is not running.



Many thanks,
Luke
4 REPLIES 4
Mulgund
Frequent Advisor

Re: Tuning HSZ raid controllers

Luke,
Have you installed any management software for your HSZ** controller? Like SWCC?
It should be easy to set all that you are looking for using SWCC client which installs on a windows desktop.

Infact all that you are asking for can be done thro a CLI session to the HSZ** controller also. Pl. refer to the CLI manual provided to you along with the storage you bought.

If you still need a step by step procedure, one of us will be able to help you.

Hope this helps.

-Srinivas
Han Pilmeyer
Esteemed Contributor

Re: Tuning HSZ raid controllers

Looks like those recommendations came straight out of the sys_check "warnings" section. In general we recommend to run sys_check after any changes are made to the system and in particular to look at the "warnings" sections to see if any of the recommendations made there are appropriate for your system.

You can hook up a serial line to the controller and given the above recommendations, it should be simple to find the commands to use. However, if sys_check indeed made those recommendations, you already have a connection from Tru64 UNIX to the HSZ controller.
Michael Schulte zur Sur
Honored Contributor

Re: Tuning HSZ raid controllers

Hi Luke,

depending on your os version you can do this with hszterm or hsxterm5. As Han said, serial connect to the controller is the best way. For the KZPCC controller use the Storage Works Command Console.
http://h18002.www1.hp.com/alphaserver/products/storage/kzpcc.html
It will be difficult however to get the agent for the HSZ still. What kind of HSZ do you have?

greetings,

Michael
Mark Poeschl_2
Honored Contributor

Re: Tuning HSZ raid controllers

As Han points out, those recommendations come straight from an automated tool, and more than likely have not taken into account your application environment at all. Before applying them blanket-fashion, analyzing your own I/O profile using something like VTDPY would be a good idea. VTDPY is a CLI-based utility that runs on the HSZ itself. I've seen cases where running VTDPY remotely (via hsxterm5) can hang up console access to the HSZ, so it's best to run it from the serial console port.