LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Red Hat
User Name
Password
Red Hat This forum is for the discussion of Red Hat Linux.

Notices

Reply
 
Search this Thread
Old 11-29-2011, 03:15 PM   #1
lhenders326
LQ Newbie
 
Registered: Nov 2010
Posts: 3

Rep: Reputation: 0
No disk device created when iSCSI initiator logs in


I am trying to get Open-iSCSI to work on a Red Hat Enterprise Server v5.5. I can log in to the target just fine and see the sessions with teh iscsiadm -m node command. This happens across reboots of the system. What I never see is a drive device created for the iSCSI volume. There is no /dev/sde created, nothing in /dev/disk/by_path that points to an iSCSI path, no indication that a disk device was created. This happens on two Red Hat servers with different hardware. I can use the initiator in Windows 2008 R2 and create a volume with no problem on the target, but not on the Red Hat servers. I have contacted Red Hat support, but they are no help.
 
Old 12-01-2011, 04:17 PM   #2
kbp
Senior Member
 
Registered: Aug 2009
Posts: 3,758

Rep: Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643Reputation: 643
Quote:
and see the sessions with teh iscsiadm -m node command.
.. not sure how you see sessions with the node command.. try 'iscsiadm -m session'
 
Old 12-02-2011, 04:17 AM   #3
mikey99
Member
 
Registered: Nov 2008
Location: UK
Distribution: RHEL, Fedora
Posts: 68

Rep: Reputation: 12
Quote:
Originally Posted by lhenders326 View Post
I am trying to get Open-iSCSI to work on a Red Hat Enterprise Server v5.5. I can log in to the target just fine and see the sessions with teh iscsiadm -m node command. This happens across reboots of the system. What I never see is a drive device created for the iSCSI volume. There is no /dev/sde created, nothing in /dev/disk/by_path that points to an iSCSI path, no indication that a disk device was created. This happens on two Red Hat servers with different hardware. I can use the initiator in Windows 2008 R2 and create a volume with no problem on the target, but not on the Red Hat servers. I have contacted Red Hat support, but they are no help.
Assuming you are doing the following on the client to your server on 192.168.0.200 ....

Code:
# iscsiadm -m discovery -t sendtargets -p 192.168.0.200

# iscsiadm -m node -T iqn.2011-11.com.somedomain:diskname -p 192.168.0.200 -l
It is important to use the IP address, not the hostname of your server when logging in to the target.

If successful, the kernel should report the event. To see this, type

Code:
# dmesg
and check the kernel messages. It should tell you the name of the device created.

Last edited by mikey99; 12-02-2011 at 04:18 AM.
 
Old 12-05-2011, 02:11 PM   #4
lhenders326
LQ Newbie
 
Registered: Nov 2010
Posts: 3

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by kbp View Post
.. not sure how you see sessions with the node command.. try 'iscsiadm -m session'
Here is the output of the two commands:

# iscsiadm -m node
10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1
10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1

# iscsiadm -m session
tcp: [1] 10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
tcp: [2] 10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging2
tcp: [3] 10.112.100.54:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1
tcp: [4] 10.110.1.108:3260,1 iqn.1997-12.com.abernas:storage:WeeklyStaging1

They output essentially the same information. I'm starting to think that becaue teh same target shows up on two different networks that MPIO needs to be installed.
 
Old 12-05-2011, 02:14 PM   #5
lhenders326
LQ Newbie
 
Registered: Nov 2010
Posts: 3

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by mikey99 View Post
Assuming you are doing the following on the client to your server on 192.168.0.200 ....

Code:
# iscsiadm -m discovery -t sendtargets -p 192.168.0.200

# iscsiadm -m node -T iqn.2011-11.com.somedomain:diskname -p 192.168.0.200 -l
It is important to use the IP address, not the hostname of your server when logging in to the target.

If successful, the kernel should report the event. To see this, type

Code:
# dmesg
and check the kernel messages. It should tell you the name of the device created.
I have used the discovery and login commands many times already. Looking through dmesg I see where the iscsi software is intialized but no devices are created. Since the discovery finds the same target on two different IP networks does MPIO need to be installed?
 
Old 02-21-2013, 10:05 AM   #6
dudegolfin
LQ Newbie
 
Registered: Feb 2013
Posts: 2

Rep: Reputation: Disabled
Smile Resolution?

Were you able to resolve this issue? I'm facing the same issue, so if you have, I'd be interested to know about the resolution.

Thank You
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
iscsi initiator aclhkaclhk Linux - Hardware 1 12-11-2009 02:38 AM
iSCSI initiator gives problems after relogging initiator service devkpict Linux - Software 0 06-27-2008 08:24 AM
OpenSuse - iSCSI Initiator ultradj83 Linux - Networking 0 03-29-2008 06:11 AM
CentOS 4.4 iscsi-initiator IanDMac Linux - Software 0 01-01-2007 02:04 PM
iSCSI Initiator? robby2 Linux - Software 1 08-31-2004 07:41 AM


All times are GMT -5. The time now is 02:03 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration