Initiator Error 02/00

Tutorials/Articles Search HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Software iscsid: discovery login to 192.168.130.101 rejected: initiator error (02/0b) User Name Remember Me? Password Linux - Software This forum is for Software issues. Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 03-24-2010, 02:40 PM #1 AlucardZero Senior Member Registered: May 2006 Location: USA Distribution: Debian Posts: 4,795 Rep: iscsid: discovery

Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly Access Gateway)Profile ManagementProof of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products XenServer XenServer Product Family Storage Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. http://www.linuxquestions.org/questions/linux-software-2/iscsid-discovery-login-to-192-168-130-101-rejected-initiator-error-02-0b-797615/ iSCSI connections to non-existent volume Started by Peter Hinds , 23 June 2011 - 09:44 PM Login to Reply 9 replies to this topic Best Answer Tim van der Zeeuw , 25 April 2012 - 10:00 AM You can kill the session, so you don't have to reboot the host.Find the target with the command:iscsiadm -m http://discussions.citrix.com/topic/289486-iscsi-connections-to-non-existent-volume/ session -P 1Kill the session:iscsiadm -m session -r SESSIONID -u --> SESSIONID is the SID of the session reference to the targetexample: iscsiadm -m session -r 9 -uRegards Go to the full post

Peter Hinds Members #1 Peter Hinds 68 posts Posted 23 June 2011 - 09:44 PM Hi,XenServer is attempting to connect to a non existent volume on the EqualLogic SAN which does not exist. The volume is created by the PHDVirtual backup agent however the backup process fails (not all the time though) and I start receive repeated notifications from the EqualLogic array that a connection attempt failed. The daemon log shows this:Jun 17 02:14:02 xxxxxx iscsid: conn 0 login rejected: initiator error - target not found (02/03)The Kern.log shows this:un 17 02:13:24 xxxxx kernel: connection823:0: detected conn error (1020)Jun 17 02:13:26 xxxxx kernel: connection623:0: detected conn error (1020)Jun 17 02:13:51 xxxxx last message repeated 8 timesJun 17 02:13:53 xxxxx kernel: scsi833 : iSCSI Initiator over TCP/IPJun 17 02:13:53 xxxxx kernel:

NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphere™ > vSphere Upgrade & Install > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 8 Replies Latest reply: Jun 5, 2009 4:04 https://communities.vmware.com/thread/213921?start=0&tstart=0 PM by ArsonSmith ESX 3.5 Patch manager upgrade lost iSCSI targets ArsonSmith https://bugzilla.redhat.com/show_bug.cgi?id=537787 Jun 5, 2009 8:47 AM Using Update Manager I had recently updated an ESX 3.5 server to the latest patch level.I lost all my iSCSI targets, My iSCSI device (Dell MD3000i) no longer sees the initiator from this patched host.I've checked the firewall, removed and reconfigured the iSCSI initiator error initiator and still don't see it showing up. What else do I need to look at to troubleshoot this further? Thanks in advance EDIT:This update included these two patches:http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008327http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010129 697Views Tags: none (add) This content has been marked as final. Show 8 replies 1. Re: ESX 3.5 Patch manager upgrade lost iSCSI targets ArsonSmith Jun 5, 2009 initiator error 02/00 10:27 AM (in response to ArsonSmith) Seeing this in /var/log/messagesJun 5 10:18:22 srv48 vmkiscsid[3642]: Connected to Discovery Address x.x.x.28 Jun 5 10:18:22 srv48 vmkiscsid[3642]: discovery login to x.x.x.28 rejected: initiator error (02/00), non-retryable, giving up Jun 5 10:18:22 srv48 vmkiscsid[3643]: Connected to Discovery Address x.x.x.29 Jun 5 10:18:22 srv48 vmkiscsid[3643]: discovery login to x.x.x.29 rejected: initiator error (02/00), non-retryable, giving up Jun 5 10:18:22 srv48 vmkiscsid[3644]: Connected to Discovery Address x.x.x.30 Jun 5 10:18:22 srv48 vmkiscsid[3644]: discovery login to x.x.x.30 rejected: initiator error (02/00), non-retryable, giving up Jun 5 10:18:23 srv48 vmkiscsid[3645]: Connected to Discovery Address x.x.x.31 Jun 5 10:18:23 srv48 vmkiscsid[3645]: discovery login to x.x.x.31 rejected: initiator error (02/00), non-retryable, giving up Like Show 0 Likes (0) Actions 2. Re: ESX 3.5 Patch manager upgrade lost iSCSI targets AndreTheGiant Jun 5, 2009 10:50 AM (in response to ArsonSmith) Have you tried (from your ESX box) to do a ping and a vmkping to your target IPs?Are you using a CHAP password?On MD3000i you see the host connected? Andre**if you found this or any other answer usefu

Log In [x] | Forgot Password Login: [x] Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug537787 - On Super Micro servers : iscsiadm discovery initiator error (02/02), non-retryable, giving up [NEEDINFO] Summary: On Super Micro servers : iscsiadm discovery initiator error (02/02), non-retr... Status: CLOSED WONTFIX Aliases: None Product: Red Hat Enterprise Linux 5 Classification: Red Hat Component: iscsi-initiator-utils (Show other bugs) Sub Component: --- Version: 5.6 Hardware: x86_64 Linux Priority low Severity urgent TargetMilestone: rc TargetRelease: --- Assigned To: Chris Leech QA Contact: Red Hat Kernel QE team Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2009-11-16 06:14 EST by Srinivasan Ramani Modified: 2014-06-02 09:02 EDT (History) CC List: 3 users (show) coughlan mchristi sramani See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2014-06-02 09:02:56 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Flags: pm-rhel: needinfo? (sramani) Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Srinivasan Ramani 2009-11-16 06:14:31 EST Description of problem: Open-iscsi Initiator is unable to discover target . Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run command : iscsiadm -m discovery -t sendtargets -p 192.168.100.41 -d 8 2. Using a Hardware iSCSI Target from Pillar. The ip address 192.168.100.41 is location of iscsi portal. Actual results: Initiator Error , discovery fails. iscsiadm -m discovery -t sendtargets -p 192.168.100.41 -d 8 iscsiadm: Max file limits 1024 1024 iscsiadm: updating defaults from '/etc/iscsi/iscsid.conf' iscsiadm: updated 'discovery.sendtargets.iscsi.MaxRecvDataSegmentLength', '32768' => '32768' iscsiadm: updated 'node.session.timeo.replacement_timeout', '120' => '120' iscsiadm: updated 'node.conn[0].timeo.login_timeout', '30' => '15' iscsiadm: updated 'node.conn[0].timeo.logout_timeout', '15' => '15' iscsiadm: updated 'node.conn[0].timeo.noop_out_interval', '5' => '5' iscsiadm: updated 'node.conn[0].timeo.noop_out_timeout', '5' => '5' iscsiadm: updated 'node.session.err_timeo.abort_timeout', '15' => '15' iscsiadm: updated 'node.session.err_timeo.lu_reset_timeout', '30' => '20' iscsiadm: updated 'node.session.initial_login_retry_max', '4' => '64' iscsiadm: updated 'node.