An administrator sees the following error in the log files:
Which two events could be the source of the error message? (Choose two.)
A.
vCenter Server failure
B.
VXLAN failure
C.
Disk array failure
D.
Network failure
E.
ESXi host failure
Explanation:
https://communities.vmware.com/thread/265187
C, D – OK
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2136081
0
0
https://kb.vmware.com/kb/1009557
1
0
CD
0
0
CD
0
0
I dont agree. It should be C and E. Normally a san-lun volume should be accessed by FC, why networking can be an issue? It could be a problem on the disk array or in the HBA in the host. Could someone explain why C is an option?
1
0
Sorry, I meant, explain why “D” is an option?
0
0
Hi Mario,
I believe CD are correct.
C – We all agree C is correct;
D- SAN can also be related to iSCSI, in which case the network aspect is valid. What’s more, the “N” in SAN stands for Network, so even FC needs a network to operate (excluding DAS, of course). It’s not the same as Ethernet network but it still is type a network.
E – If the ESXi host fails, it won’t complain that a specific volume is down, but instead the whole system would be down. If the option had mentioned a system component failure (like a HBA, for example) than E could potentially be considered)
6
0
I was also thinking about C and E answers..
Networking issue should not be involved with SAN. More certainly an error on the ESXi HBA
Why would you choose “D” instead ?
0
2
Thanks for your reply SPFC
0
0
I guess it could be an iSCSI SAN, that would use networking. I can’t see a host failure giving this message as it’s a SAN and not local storage.
0
0
you can refer to these error logs from hostd.log file form within an esxi host and not from vcenter server unless otherwise specified in the question. Hence answer is C and D
0
0
The Question is 1:1 in the KB 🙂
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009557
Example
If an ESX host has mounted a volume san-lun-100 from device naa.60060160b4111600826120bae2e3dd11:1 and loses connectivity (due to a cable pull, disk array failure, and so on) to the device for a period exceeding 16 seconds, the following error message appears:
Lost access to volume 496befed-1c79c817-6beb-001ec9b60619 (san-lun-100) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
(due to a cable pull, disk array failure, and so on)
3
0
Follow up question for “themike”.
What do you suppose “cable pull” means? A network cable was pulled in the case of an iSCSI SAN array, or a fiber channel/SAS cable was pulled in the case of a FB SAN or direct attached SAS storage?
What do you mean by the “The Question is 1:1?
Regards,
Adam Tyler
0
0
If you read the link provided by “themike” al the way down, it says that it concerns firbrechannel, making C-E the logical answer.
0
0
The KB says:
“Connect to the ESX host’s service console.
Run these commands: ”
If the host is down it would be complicated.
0
0
ive done a lot of thinking and research about this and i believe the answer is C and D
if the esxi host had a failure and went down, youd have a lot more problems then just a lun issue.
the question clearly states that access to a lun has been lost… nothing else has happened.
0
0
As I put in the same question of the other exam, I have had the exam today in Spain with a score of 500/500. Specifically in this question I’ve selected C & D: Disk Failure and Network Failure since it made little more sense for me.
https://www.briefmenow.org/vmware/which-two-events-could-be-the-source-of-the-error-message-3/#comment-272091
1
0
Clearly C and D.
Technically, ‘E’ could be a choice here since it doesn’t have to be a fatal failure like PSOD (ESX purple screen of death) or O/S disk crash or disk controller failure, but rather some hardware component failure (e.g. non-O/S disk supporting a local datastore) or misconfiguration.
However, the error message in the log file has a reference to SAN – storage area Network so it’s not about something local to the ESX host.
So it must be either network related (D) or storage (C).
0
0