This post is more than 5 years old

1 Rookie

 • 

31 Posts

4282

December 29th, 2014 09:00

lun response time (ms) very high

We have a new VNX 5600 installed last week.  I setup a single tiered RAID 5 pool for a VMware ESXi cluster.  I've zoned the ESXi servers, setup Host groups, and added the initiators to the host group.  The ESXi servers are seeing the storage appropriately with the appropriate amount of paths.  I allocated some LUNs to the host groups.  We configure the Virtual Machine Swapfile Location option on our ESXi servers to move the vm swapfile to a datastore LUN instead of them being located with the virtual machine.  We've created about 60 virtual machines in this cluster and the swapfiles for the virtual machines reside on the datastore LUN that has been configured.  None of the virtual machines are in production and they aren't doing anything right now other than just running.  VNX Monitoring and Reporting indicates that the response time for this LUN is very poor.  4 to 5 times an hour the response time will spike well over 20 ms (in the range of several hundred ms to 100 seconds).  I look in vCenter at performance metrics for virtual machines and the datastores and I see no latency issues for the datastore.  It's barely doing anything at all as far as read / writes.  In VNX Monitoring and Reporting there the iops is almost nothing.  Max iops reached 6 this morning and most the time it is a zero.  All the other metrics in VNX Monitoring and Reporting for the LUN in question are almost nothing also (queue length max .5, utilization is 0%, bandwidth is .0175, etc).

We have several other clusters configured the same way and the response time for the datastore LUN isn't having any issues so I'm wondering where the issue is?  Any thoughts?

1 Rookie

 • 

104 Posts

December 31st, 2014 01:00

hi,

have a look at this, it might explain your situation.. we have seen it too:

https://support.emc.com/kb/91353

sk

9 Legend

 • 

20.4K Posts

December 29th, 2014 10:00

if you see next to no iops then you can safely disregard those big response times. I see the same issue in my M&R as well as Unisphere Analyzer. I think it was glen that explain that it had something to do with how the response time was being calcualated.

1 Rookie

 • 

31 Posts

January 2nd, 2015 10:00

Thanks for the response.  That article appears to be applicable.  I opened a case with EMC while waiting for a response to my initial question and they pointed me towards this also - https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000001BNb

No Events found!

Top