MENU
An administrator has created a volume and needs to attach it to a windows host a via iSCSI. The data Services IP has been configured in the MS iSCSI Initiator, but no target are visible.
What is most likely the cause this issue?
29 comments · newest first
JO
Josphine
10 months ago
Seems odd that no targets show up at all...
LE
Lenny
11 months ago
Wait, are you sure CHAP needs to be set up on the client?
AL
Alesia
11 months ago
Definitely check the IQN authorization too!
JA
Jaime
11 months ago
I think it's more likely the CHAP password is wrong.
DE
Desirae
11 months ago
Probably the host's IP isn't authorized.
LI
Linwood
11 months ago
I’m a bit confused about the CHAP settings. Wasn't there something about needing to configure it on both ends? That might point to option C.
TA
Tamala
12 months ago
I’m not entirely sure, but I feel like the host's IQN could be the problem. That makes me lean towards option D.
AR
Ariel
12 months ago
I think I saw a practice question where CHAP authentication was mentioned. Maybe it’s option B or C?
HU
Huey
1 year ago
I remember something about IP authorization being a common issue with iSCSI setups. Could it be option A?
ON
Onita
1 year ago
I feel pretty confident about this one. The most likely cause is that the host's IQN isn't authorized to access the volume. That's probably the issue we need to address.
SH
Shanda
1 year ago
I'm a bit confused on this one. Is it possible the host's IP address isn't authorized to access the volume? That could be the problem, right?
SH
Shelton
1 year ago
Ah, I think I know what's going on here. The CHAP authentication hasn't been set up on the client side, so the target isn't visible. That's gotta be it.
MA
Maile
1 year ago
Okay, let's see. The data Services IP has been configured, so that's not the issue. I'm guessing it's probably either the CHAP password or the host's IQN authorization.
LA
Laticia
1 year ago
Hmm, this seems like a tricky one. I'll need to think through the possible causes carefully.
CU
Curt
2 years ago
Hmm, I'm not sure about that. Maybe the CHAP password is incorrect. You know what they say, 'Passwords are like underwear, change them often and don't share them with strangers.'
TR
Trina
2 years ago
B) The CHAP password configured on the client is incorrect.
MA
Mauricio
2 years ago
A) The host' s IP address is not authorized to access the volume.
BO
Bo
2 years ago
I agree with Louvenia. The IQN is the unique identifier for the host, and if it's not authorized, the targets won't be visible. That's definitely the issue here.
AL
Allene
2 years ago
D) The host's IQN is not authorized to access the volume.
TA
Tamra
2 years ago
C) The CHAP Authentication has not been configured on the client.
ON
Ona
2 years ago
B) The CHAP password configured on the client is incorrect.
FE
Felton
2 years ago
A) The host's IP address is not authorized to access the volume.
JA
Jacquline
2 years ago
I'm not sure, but I think option A could also be a possibility if the host's IP address is not authorized to access the volume.
LO
Louvenia
2 years ago
The most likely cause is option D. The host's IQN is not authorized to access the volume. Without the correct IQN authorization, the target won't be visible on the host.
JA
Janessa
2 years ago
C) The CHAP Authentication has not been configured on the client.
MA
Markus
2 years ago
B) The CHAP password configured on the client is incorrect.
PH
Phung
2 years ago
A) The host's IP address is not authorized to access the volume.
AR
Aretha
2 years ago
I agree with Della, option D makes sense because the target won't be visible if the host's IQN is not authorized.
DE
Della
2 years ago
I think the most likely cause is option D, the host's IQN is not authorized.