Hello again Mike / open-iscsi community, Any clue as to what might be missing for me? Is there a way to update by editing a file as opposed to typing in the commands? It seems so close to being figured out but I'm stumped!
Thanks again Jeff On Fri, Jan 4, 2013 at 4:37 PM, Jeff Bye <jeff...@gogoluckey.com> wrote: > 2.0-871 is what I'm running > > Jeff > > > On Fri, Jan 4, 2013 at 4:17 PM, Jeff Bye <jeff...@gogoluckey.com> wrote: > >> I tried all of the commands and none of them worked for me: >> >> *deadlineserver@deadlineserver ~ $ iscsiadm -m discoverydb -t st -p >> 10.10.0.1:3260 -o delete* >> iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t >> type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ >> -n name ] [ -v value ] >> iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L >> all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname >> -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n >> name ] [ -v value ] ] >> iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r >> sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -v >> value ] ] >> iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I >> ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] >> iscsiadm -m fw [ -l ] >> iscsiadm -m host [ -P printlevel ] [ -H hostno ] >> iscsiadm -k priority >> >> >> *I checked man iscsiadm and found:* >> -m, --mode op >> specify the mode. op must be one of discovery, node, fw, >> host iface or session. >> >> If no other options are specified: for discovery and >> node, all of their respective records >> are displayed; for session, all active sessions and >> connections are displayed; for fw, all >> boot firmware values are displayed; for host, all iSCSI >> hosts are displayed; and for iface, >> all ifaces setup in /etc/iscsi/ifaces are displayed. >> >> Am I running the wrong version perhaps? >> >> Jeff >> >> >> >> On Thu, Jan 3, 2013 at 7:05 PM, Mike Christie <micha...@cs.wisc.edu>wrote: >> >>> The iscsid.conf values are the defaults one used to setup the >>> port/node/target db. If you clear the iscsid.conf values, you would >>> still need to update the db ones for it to take effect on existing >>> targets you have already setup. >>> >>> For the discovery values you can either delete the old discovery record: >>> >>> iscsiadm -m discoverydb -t st -p ip -o delete >>> >>> When you run the discovery command next, then it will use the >>> iscsid.conf settings to create the discovery record. >>> >>> or if your tools does not support that command you can clear the chap >>> settings >>> >>> iscsiadm -m discoverydb -t st -p ip -o update -n >>> discovery.sendtargets.auth.username -v "" >>> iscsiadm -m discoverydb -t st -p ip -o update -n >>> discovery.sendtargets.auth.password -v "" >>> iscsiadm -m discoverydb -t st -p ip -o update -n >>> discovery.sendtargets.auth.authmethod -v none >>> >>> >>> On 01/03/2013 01:46 PM, Jeff Bye wrote: >>> > Hey! I've been out of town for a couple of weeks. Hope you had a >>> > chance to take some time off as well :) >>> > >>> > It seems that the username and password I had initially set up is still >>> > being used, however in iscsid.conf CHAP is set to "none" and any other >>> > information has been commented. Does this only affect the target side? >>> > >>> > Jeff >>> > >>> > When I had it running on a windows machine (a temporary setup) we kept >>> > it open and >>> > On Fri, Dec 21, 2012 at 1:32 AM, Mike Christie <micha...@cs.wisc.edu >>> > <mailto:micha...@cs.wisc.edu>> wrote: >>> > >>> > On 12/20/2012 06:54 PM, GGL wrote: >>> > > deadlineserver@deadlineserver / $ sudo iscsiadm -m discovery -t >>> > > sendtargets -p 10.10.0.1 >>> > > iscsiadm: Login authentication failed with target >>> > >>> > Yeah, this is a CHAP failure. Is it turned off on the target too? >>> > >>> > Could you run >>> > >>> > sudo iscsiadm -m discovery -t sendtargets -p 10.10.0.1 -d 8 >>> > >>> > and send all the output? >>> > >>> > Also while running this command run: >>> > >>> > tcpdump -w iscsi.discovery.out -i your_eth_device >>> > >>> > and then send that iscsi.discovery.out file. It will show us what >>> the >>> > target is sending on the wire too. >>> > >>> > >>> > Both of those files will have passwords in them if you have CHAP >>> > settings still being used, so send me them in private or edit out >>> the >>> > values if you do not want them on the open. >>> > >>> > >>> > >>> > >>> > -- >>> > Jeff Bye >>> > Graphics Coordinator >>> > Liberty Post >>> > 12910 Culver Blvd. Suite G >>> > Los Angeles, CA 90066 >>> > (310) 314-3900 x247 >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "open-iscsi" group. >>> > To post to this group, send email to open-iscsi@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > open-iscsi+unsubscr...@googlegroups.com. >>> > For more options, visit this group at >>> > http://groups.google.com/group/open-iscsi?hl=en. >>> >>> >> >> >> -- >> Jeff Bye >> Graphics Coordinator >> Liberty Post >> 12910 Culver Blvd. Suite G >> Los Angeles, CA 90066 >> (310) 314-3900 x247 >> > > > > -- > Jeff Bye > Graphics Coordinator > Liberty Post > 12910 Culver Blvd. Suite G > Los Angeles, CA 90066 > (310) 314-3900 x247 > -- Jeff Bye Graphics Coordinator Liberty Post 12910 Culver Blvd. Suite G Los Angeles, CA 90066 (310) 314-3900 x247 -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
