Basically it looks like you are having some connectivity issues between your host and the array(s). Whether it is the cause of the server crashing, it's really hard to tell without checking the cluster/application logs - but it's worth investigating, all right.
The problem here is that any of the components on the way (host, HBA, switch, SP port, array itself) can be failing, so we'll need to check all of them to find the root cause - I am afraid that due to the amount of logs that need to be checked (EMCreports, switch logs, array SP collects), the only proper way of doing it will be through a Service Request - please open one with PowerPath/Windows support and we'll take care of this.
Not sure if you still are looking for some assistance. Regarding the dead paths or degraded devices, looking at the screenshots, it appears that your configuration is as follows:
4 paths to CLARiiON
8 paths to VNX
The reason why Disk 3 and 5 show degraded is because there is a single path that is dead from . When a device is in degraded mode it simply means that at least 1 path is dead thus not optimal. PP automatically uses the remaining paths for IO until the path some back alive.
Now, focusing on each device, Disk 3 is coming from CLARiiON and looks to have 3 paths via port4 (c4t0d3, c4t1d3, and c4t2d3), but one is dead (c4t0d3). Comparing with the other CLARiiON LUNs, none of them show any path using target 0 (t0), it is either target 1 or 2. For Disk 5, it is coming from VNX and looks to have 5 paths via port4 (c4t0d1, c4t2d1, c4t3d1, c4t4d1, and c4t5d1) with one path (c4t2d1) dead. Comparing with the other VNX LUNs, none of them show any paths via target 2 (t2), they are only using target 0, 3, 4, and 5. That tells me those are ghost/invalid paths. Please check for the presence of POWERMT.CUSTOM (xml and/or lck extension) either inside EMC\PowerPath\ (5.7.x and up) or EMC\PowerCommon\ (5.5.x and below). If found, rename/delete this file and reboot the host. It is not recommended to use this file unless there are specific configurations the host needs/uses.
Regarding the crashes, it would be difficult to truly diagnose what might be happening, but the fact that there are a lot of path dead events may suggest a connectivity problem.
Hopefully this helps, if so, please make sure to mark it as answered.
pawelw1
306 Posts
2
July 14th, 2016 00:00
Hi Will,
Basically it looks like you are having some connectivity issues between your host and the array(s). Whether it is the cause of the server crashing, it's really hard to tell without checking the cluster/application logs - but it's worth investigating, all right.
The problem here is that any of the components on the way (host, HBA, switch, SP port, array itself) can be failing, so we'll need to check all of them to find the root cause - I am afraid that due to the amount of logs that need to be checked (EMCreports, switch logs, array SP collects), the only proper way of doing it will be through a Service Request - please open one with PowerPath/Windows support and we'll take care of this.
Thank you,
Pawel
andress1
27 Posts
2
August 2nd, 2016 09:00
Hello Will,
Not sure if you still are looking for some assistance. Regarding the dead paths or degraded devices, looking at the screenshots, it appears that your configuration is as follows:
4 paths to CLARiiON
8 paths to VNX
The reason why Disk 3 and 5 show degraded is because there is a single path that is dead from . When a device is in degraded mode it simply means that at least 1 path is dead thus not optimal. PP automatically uses the remaining paths for IO until the path some back alive.
Now, focusing on each device, Disk 3 is coming from CLARiiON and looks to have 3 paths via port4 (c4t0d3, c4t1d3, and c4t2d3), but one is dead (c4t0d3). Comparing with the other CLARiiON LUNs, none of them show any path using target 0 (t0), it is either target 1 or 2. For Disk 5, it is coming from VNX and looks to have 5 paths via port4 (c4t0d1, c4t2d1, c4t3d1, c4t4d1, and c4t5d1) with one path (c4t2d1) dead. Comparing with the other VNX LUNs, none of them show any paths via target 2 (t2), they are only using target 0, 3, 4, and 5. That tells me those are ghost/invalid paths. Please check for the presence of POWERMT.CUSTOM (xml and/or lck extension) either inside EMC\PowerPath\ (5.7.x and up) or EMC\PowerCommon\ (5.5.x and below). If found, rename/delete this file and reboot the host. It is not recommended to use this file unless there are specific configurations the host needs/uses.
Regarding the crashes, it would be difficult to truly diagnose what might be happening, but the fact that there are a lot of path dead events may suggest a connectivity problem.
Hopefully this helps, if so, please make sure to mark it as answered.
Thanks,
Andres