3 Apprentice

 • 

423 Posts

November 27th, 2013 01:00

Marie,

i'm not sure if you are in SPA for SMAS or Unisphere, but in either you should be able to drill down into the DA's that are showing busy in the diagnostic view and sort the physical disks by activity.  When you find the busy disks you should then be able to double click and drill into to find out the busy volumes, TDAT or Regular device. This should hopefully get you on the right path to finding your culprit.

1.3K Posts

November 27th, 2013 06:00

The subject of this thread talks about high latency, then goes off to DA utilization.  The two may have nothing to do with one another.   Is it read or write latency you are concerned about?

What code are you running?  in 5876.229 you may see high DA % busy, but much of that could be background activity.

1.3K Posts

November 27th, 2013 08:00

FAST VP movement, IVTOC, Clone copy, rebuild, etc. 

19 Posts

November 27th, 2013 08:00

I'm in Unisphere. I'm able to drill into the disk then device. This helps. Still amazed there's not a more elegant method in Unisphere. I thought I recalled SMAS SPA being easier to locate a hot dev. The other method I've heard is to add *all STD devs to a Device Group but that's too tedious in this case. Would be multiple groups, etc. This abaility to drill through the disk to dev helps. Thanks!

19 Posts

November 27th, 2013 08:00

5876.229.145.  What type of specific activities would be on your list of Background Activities?

No Events found!

Top