performance issue

ECC defaults values for these numbers, which are below. These numbers are generic starting points, and often aren't the numbers for your environment.

Critical 8000+
Warning 4000-6000
Minor 0-4000

If performance in your environment is acceptable, what I would suggest you do, is use performance manager to collect a months worth of data. Then figure out average values for these numbers. That will give you a baseline of performance in your environment, and then use those numbers to alert on if you want.

Aside from the standard alerting values, performance manager collects a ton of statistics. What I like to do is define a whole bunch of new vital signs, not just the 15 default ones.

I break performance into a few categories. Then in each category, I look at several things:

Front end:
-Dir-Fibre>iops
-Dir-Fibre>% until
-Dir-Port>throughput in Kbytes per sec
-Dir-Port>% util
-Dir-Fibre>system write pending events
-Dir-Fibre>device write pending events

Cache/system:
System>total iops
System>% hit
System>% write
System>% read hit
System>Kbytes read per sec
System>Kbytes written per sec
Device>system bus Kbytes per sec
Dir-Fibre> % hit
Dir-Fibre>% write
Dir-Fibre>% read hit
Dir-Fibre>slot collisions per sec
Dir-Port>average io size in Kbytes
-System>system max wp limit
-System>number write pending tracks
-Dir-Fibre>system write pending events
-Dir-Fibre>device write pending events
-Device>max write pending threshold
-Device>write pending count

Back end:
-Dir-DA>iops
-Dir-DA>% util
-Disk>SCSI commands per sec
-Disk>% util
-Device>iops
-Device>HA Kbytes transferred per sec
-Device>DA Kbytes transferred per sec
-Dir-DA>prefetched tracks per sec
-Dir-DA>tracks not used per sec
-Device>prefetched tracks per sec
-Device>% read hit

Then I report on the states most critical and important to me. Bottom line is what numbers are good performance for you, are what you need to alert on.

Now that I¿ve finished my rant on performance, I¿ve got work to do