- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: VSA error EID_LATENCY_STATUS_EXCESSIVE E000601...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-21-2010 02:38 PM
тАО12-21-2010 02:38 PM
VSA error EID_LATENCY_STATUS_EXCESSIVE E00060100
Everything appears to be fine, but when I try to run a physical to virtual conversion with the destination volume on the VSA, a error is logged about 10 minutes into the file copy process. At the same time, the destination virtual machine locks up and the process fails.
The error is.
Message: The storage system 'ausvsa1.xxxxx.local', in cluster 'AUS1', latency = 65.013, which exceeds 60.000.
EID_LATENCY_STATUS_EXCESSIVE E00060100
This is followed by two more events:
The system CPU utilization (100%) status is 'Saturated'.
The storage system 'ausvsa1.xxxxx.local', in cluster 'AUS1', latency status is 'Normal'.
The ESXi server has plenty of CPU and memory headroom and the VSA is configured for 2000hz of CPU as required in the VSA Install and Configuration Guide.
The very same p2v job runs successfully to the local disc of the ESXi server. Anyone know what this error means?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2010 03:37 PM
тАО12-22-2010 03:37 PM
Re: VSA error EID_LATENCY_STATUS_EXCESSIVE E00060100
Is the uplink to your core switch a non-blocking port? I've seen oversubcription cause latency issues.
Regards,
Scott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2010 08:04 PM
тАО12-22-2010 08:04 PM
Re: VSA error EID_LATENCY_STATUS_EXCESSIVE E00060100
It is good to know that this is a network issue, I wasn't sure what latency it was talking about (network, disc, who knows).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-31-2010 06:27 PM
тАО12-31-2010 06:27 PM
Re: VSA error EID_LATENCY_STATUS_EXCESSIVE E00060100
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-03-2011 11:10 AM
тАО01-03-2011 11:10 AM
Re: VSA error EID_LATENCY_STATUS_EXCESSIVE E00060100
We converted all of our VSAs to use RDMs instead of VMFS-based VMDKs and haven't seen the problem since. :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2011 09:46 AM
тАО01-11-2011 09:46 AM
Re: VSA error EID_LATENCY_STATUS_EXCESSIVE E00060100
I installed a new ESXi server 4.1 build 320137 on a HP DL365 G5 and put a version 9.0.00.3561 VSA on there. I created a 1.95TB VMDK and attached it to SCSI 1:0 on the VSA.
I created a 500GB thin volume on the VSA and presented it to the ESXi host via an internal only vSwitch.
I created a VM on the new VSA volume and whilst Windows 2008 R2 was installing the CMC logged the latency > 60ms error a few times and eventually the VSA declared the volume inoperable and the VM hung completely.
I was watching the disk latency values and the VSA lun was reporting latencies of 45 seconds+ whilst the physical lun that the VMDK was sat on was reporting maximum latencies of 20ms (average <5ms).
I have now deployed a VSA running 8.5 and the issue has vanished.