NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
iSCSI target discovery failed
Currently running:
OS X 10.8.5
Java 7 Update 45
ATTO Xtend San 3.45
ReadyNAS PRO (OS 4.2.24)
Previously running
OS X 10.8.2
Java 7 Update 7
ATTO Xtend SAN 3.40v2
ReadyNAS PRO (OS 4.2.21)
After upgrading, I can no longer connect to my iSCSI targets and get the following pop-up error:
"Discovery failed: java.net.ProtocolException: Illegal TargetName (iqn.2010.4.nas-EA-0E-83:binaries"
Talking to ATTO Tech Support, the replied:
"The reason that you are getting this error is because the target name doesn't have two digits for the month and only has one. When we released 3.45 one of the things that we changed (to further conform to the iSCSI spec) was to require the target device to have a two digit month instead of one. Changing this should allow you to access your target again. Please keep in mind that this will need to be changed on the target itself, and we cannot help you if you run into an issue changing the name on the target device."
How do I change the target IQN? I have enabled Access Control and added the new IQN initiator, but that doesn't work. My guess is I need to actually modify the existing IQN (2010.4..)
OS X 10.8.5
Java 7 Update 45
ATTO Xtend San 3.45
ReadyNAS PRO (OS 4.2.24)
Previously running
OS X 10.8.2
Java 7 Update 7
ATTO Xtend SAN 3.40v2
ReadyNAS PRO (OS 4.2.21)
After upgrading, I can no longer connect to my iSCSI targets and get the following pop-up error:
"Discovery failed: java.net.ProtocolException: Illegal TargetName (iqn.2010.4.nas-EA-0E-83:binaries"
Talking to ATTO Tech Support, the replied:
"The reason that you are getting this error is because the target name doesn't have two digits for the month and only has one. When we released 3.45 one of the things that we changed (to further conform to the iSCSI spec) was to require the target device to have a two digit month instead of one. Changing this should allow you to access your target again. Please keep in mind that this will need to be changed on the target itself, and we cannot help you if you run into an issue changing the name on the target device."
How do I change the target IQN? I have enabled Access Control and added the new IQN initiator, but that doesn't work. My guess is I need to actually modify the existing IQN (2010.4..)
2 Replies
Replies have been turned off for this discussion
- 1) If not already installed, install Enable Root Access http://www.readynas.com/?p=4203
2) Reboot as instructed
3) Disable iSCSI support from Volumes/iSCSI
4) Using your favorite tool (ssh/nano for example), edit /etc/ietd.conf and give the target a new name
5) Enable iSCSI support again - Mangrove, thanks for the follow-up but I was already able to modify ietd.conf to get it working (same way you described). I had originally opened a ticket with Netgear Tech Support, but they were useless as they said it was not their problem.
Thanks again!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
