VoIP Issue/Errors

See Error messages on a VoIP Host below.  These were gotten by going into vSphere Client >  Clicking on the IP Address of the host > Going to the Event Tab.  Question:  How to determine if this is an issue with the chasis' internal storage or an external SAN?

Device naa.600605b003825740162fe7352adc9915 performance has deteriorated. I/O latency increased from average value of 21912 microseconds to 2150722 microseconds.

Lost access to volume 4e9d45e6-ce6d3808-cd05-001018a3a4a2 (datastore1) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.

Successfully restored access to volume 4e9d45e6-ce6d3808-cd05-001018a3a4a2 (datastore1) following connectivity issues.
Member_2_7965974Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bryant SchaperCommented:
Are you seeing issues other than the error, I know the first error generally can be ignored unless you are seeing problems, how are the links that connect to to the iscsi looking?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization ConsultantCommented:
The I/O Latency issues are normal, and just a warning.

However, losing access to a volume/datastore is more serious.

Is this local storage or shared storage ?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Commented:
I am going to go on a assumption here that you left the datastore name the default of "datastore1" when the host was setup if this was the case this may be from your local storage. Are your VM's running on a SAN or local storage?

The following KB will show you how to identify disk in VMware: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014953
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Voice Over IP

From novice to tech pro — start learning today.