You don't actually say what leads you to believe that the disk
subsystems are the problem other than you are now using an XIV. I
would have expected 3 internal disks to be a poor performer anyway
which leads me to believe that the system may not previously have been
heavy on IO for this disk configuration (if it is correct) to be OK. I
realise this is just supposition but...
A quick but crude way to check whether the disks are an issue is to
use the WRKDSKSTS to see how busy the disks are. Issue the command
then refresh the display after a few minutes - if you are up around
30%/40% or more on all disks all the time then this may be the
bottleneck.
Alternatively you may want to look at your CPU and memory/subsystem
configurations to be sure the problem is indeed with the XIV. You can
use WRKSYSSTS to see if the CPU is maxed out or you have heavy
faulting in any of your memory pools - are these configured the same
as the previous machine ?
Operations navigator offers some basic monitoring tools you can use to
try and determine whether the problem might lie so you may want to try
and use these to monitor what's happening with your system. This can
be used to measure the IO and percent busy on your disks over a longer
period and in a more graphical format than the WRKDSKSSTS mentioned
above.
Before you go looking at the XIV you want to be sure that disk is
indeed the issue - apologies if you have already done this, I just get
the impression from your email that you may not have.
On Tue, Jul 3, 2012 at 7:12 PM, Mauricio Kanter <mkanter@xxxxxxxxxxxxxx> wrote:
Thank you all for your questions:
The LUN sizes are 34GB and there are about 30 of them. In the past I think we had 3 internal disks totaling 450 GB.
My XIV storage manager mentioned me he thinks the stripe size is a VIOS definition (not an XIV one) ... Is there an easy way I can check it? I do not know the machine (VIOS was configured by an external provider).
Mauri.
midrange.com
