First, thanks for releasing this script, it has enabled me to provide some insight for our virtualization team without me needing to understand too much about Vmware at this stage. However, there is the problem because now I have implemented it successfully, it is showing sdd errors on many of the ESXi hypervisors it is looking at. The virtualization team are asking me what does this error actually mean, this ESXi host for instance has 30 disks, 16 are flagged green and 14 are flagged red, but they claim no issues exist with the disks :-
HBA Redundancy OK. 2 HBA found.
green All disks on prefered paths.
red At least one disk has no active paths!
yellow Some paths are dead. (28/84)
-------------============== Disk Details ==============-------------
Path Paths Paths FC HBA Names
Disks Status Dead Active vmhba2 vmhba3
green naa.60000970000292604094533030424430 Fully redundant 0 4 2 2
green naa.60000970000292600444533030303944 Fully redundant 0 2 1 1
red naa.60000970000292600444533030303732 No active paths 2 0 1 1
< not all lines reproduced, there are 27 other similar >
-------------============== WWN Details ==============-------------
The odd thing is that on 2 of the hosts where the sdd test is red, they have found genuine disk errors.
Any insight appreciated.
Thanks
--
Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In most cases when this comes up it's a matter of bad HBAs, bad
fibrechannel adapters in switches or bad cables or the link.
In rare cases it's been bad setup or config but in all cases the test shows
the truth and there are only 28 out of supposed 84 paths that are working
This could be because disks aren't used but haven't been completely removed
from all HBAs.
In the text you sent the ESC says the link to the disk is dead, this means
he finds a config that points to each HBA but the HBA probably doesn't find
them, probably the disk isn't allocated to this ESX anymore from your disk
management system.
I've had these discussions many times with my colleges, but so far the
script doesn't lie..
First, thanks for releasing this script, it has enabled me to provide some
insight for our virtualization team without me needing to understand too
much about Vmware at this stage. However, there is the problem because now
I have implemented it successfully, it is showing sdd errors on many of the
ESXi hypervisors it is looking at. The virtualization team are asking me
what does this error actually mean, this ESXi host for instance has 30
disks, 16 are flagged green and 14 are flagged red, but they claim no
issues exist with the disks :-
HBA Redundancy OK. 2 HBA found.
green All disks on prefered paths.
red At least one disk has no active paths!
yellow Some paths are dead. (28/84)
-------------============== Disk Details ==============-------------
Path Paths Paths FC HBA Names
Disks Status Dead Active vmhba2 vmhba3
green naa.60000970000292604094533030424430 Fully redundant 0 4 2 2
green naa.60000970000292600444533030303944 Fully redundant 0 2 1 1
red naa.60000970000292600444533030303732 No active paths 2 0 1 1
< not all lines reproduced, there are 27 other similar >
-------------============== WWN Details ==============-------------
The odd thing is that on 2 of the hosts where the sdd test is red, they
have found genuine disk errors.
Hi,
Many thanks for the quick response. At least everyone has the data now, so my work is done. Others may have sleepless nights for a while of course.....
--
Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
First, thanks for releasing this script, it has enabled me to provide some insight for our virtualization team without me needing to understand too much about Vmware at this stage. However, there is the problem because now I have implemented it successfully, it is showing sdd errors on many of the ESXi hypervisors it is looking at. The virtualization team are asking me what does this error actually mean, this ESXi host for instance has 30 disks, 16 are flagged green and 14 are flagged red, but they claim no issues exist with the disks :-
HBA Redundancy OK. 2 HBA found.
green All disks on prefered paths.
red At least one disk has no active paths!
yellow Some paths are dead. (28/84)
-------------============== Disk Details ==============-------------
Path Paths Paths FC HBA Names
Disks Status Dead Active vmhba2 vmhba3
green naa.60000970000292604094533030424430 Fully redundant 0 4 2 2
green naa.60000970000292600444533030303944 Fully redundant 0 2 1 1
red naa.60000970000292600444533030303732 No active paths 2 0 1 1
< not all lines reproduced, there are 27 other similar >
-------------============== WWN Details ==============-------------
The odd thing is that on 2 of the hosts where the sdd test is red, they have found genuine disk errors.
Any insight appreciated.
Thanks
--
Andy
Hi Andy
In most cases when this comes up it's a matter of bad HBAs, bad
fibrechannel adapters in switches or bad cables or the link.
In rare cases it's been bad setup or config but in all cases the test shows
the truth and there are only 28 out of supposed 84 paths that are working
This could be because disks aren't used but haven't been completely removed
from all HBAs.
In the text you sent the ESC says the link to the disk is dead, this means
he finds a config that points to each HBA but the HBA probably doesn't find
them, probably the disk isn't allocated to this ESX anymore from your disk
management system.
I've had these discussions many times with my colleges, but so far the
script doesn't lie..
good luck
Gudmo
On Mon, Feb 16, 2015 at 10:26 AM, Andy Smith shadymint@users.sf.net wrote:
Hi,
Many thanks for the quick response. At least everyone has the data now, so my work is done. Others may have sleepless nights for a while of course.....
--
Andy