This can cause VM performance issues and disk slowness.
Path redundancy to storage device naa.################################ degraded. Path vmhba#:C#:T#:L# is down. Affected datastores: Datastore1.Lost access to volume ########-########-####-############# (Datastore1) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
WARNING: ScsiDeviceIO: 1513: Device naa.################################ performance has deteriorated. I/O latency increased from average value of #### microseconds to ##### microseconds.
Cmd 0x# (0x#####, #####) to dev "naa.################################" on path "vmhba#:C#:T#:L#" Failed: H:0x5 D:0x0 P:0x0 Aborted at driver layer.
Cmd (0x#) 0x#, cmdId.initiator=0x######## CmdSN 0x#### from world ####### to dev "naa.################################" failed H:0x8 D:0x0 P:0x0 Cancelled from driver layer
/var/run/log/vobd.log you may see the following error:
Uplink: vmnic# is down. Affected dvPort: ##/50 24 e2 d9 41 e2 48 58-## ## ## ## ## ## ## ##. 3 uplinks up. Failed criteria: ###
Since the DAVG is high, we are getting in-flight aborts, and driver aborts we know that the latency is coming from either the network or storage driver/firmware, the fabric/ network, or the array itself.
Check these and if you cannot find the source of the latency on your own then you need to contact your network and storage vendor to have them investigate the latency.