can´t connect ISCSI SAN IBM storwize v7000

Hi,

I have configured an IBM storwize v7000 SAN, i have configured a 19 TB volume, and created an ISCSI host. I have connected to my windows 2008R2 ISCSI initiator with no problem, as this link shows.

http://www.windowsnetworking.com/articles-tutorials/windows-server-2008/Connect-Windows-Server-2008-Windows-Vista-iSCSI-Server.html

When i try to initialize this disk in the disk management console it doesn´t initialize the disk. In the system events shows this event.

 The description for Event ID 129 from source iScsiPrt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
The message has no description.

This message is logged when the Vista initiator or the Windows Server 2008 initiator sends an iSCSI Task Management command to the target device, and the device (\Device\ScsiPort0) does not respond within the time-out period.

Does anyone know why this happend.

Thanks
Camel0tAsked:
Who is Participating?
 
Camel0tConnect With a Mentor Author Commented:
I finally have configured the SAN as fiberchannel, thanks everyone for your assistance.
0
 
Paul SolovyovskyConnect With a Mentor Senior IT AdvisorCommented:
not fully familar with the new line of HP products (3par) but iscsi should be fairly easy.

1.  Do you have a separate VLAN/subnet for your iscsi traffic?
2.  On the SAN have you added the IP of the initiator (the machine connecting to the LUN) to the target IP (the ip that's advertising the LUN).
0
 
Camel0tAuthor Commented:
Yes, i´ve got a different subnet to my ISCSI traffic and i have configured the IP of the initiator.
I can ping and connect to my ISCSI device, but it doesn´t initialize when i try to connect it to the server in the disk management console.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Paul SolovyovskySenior IT AdvisorCommented:
Have you added the IQN (initiator) to the target?
0
 
Camel0tAuthor Commented:
Yes, and it appears as connected in the "targets" tab of the windows 2008r2 initiator, but it doesn´t initialize as local disk in the server.
0
 
Paul SolovyovskySenior IT AdvisorCommented:
make sure that the permissons on the san are read/write, I have seen this when it's only read permissions to the LUN, otherwise you can call HP and work with their support, they're pretty good at resolving issues like this
0
 
Camel0tAuthor Commented:
I solved my problem by configuring it in a different way.
0
 
cdjcCommented:
I'm afraid that it's not as simple as reading an OpenFiler HOWTO Blog post and applying part of the steps for Windows :(

Luckily, IBM has a very thorough Redbooks site.  So, for future use, in case anyone finds this question looking for an iSCSI answer, please refer to the following sections in the "Implementing the IBM Storwize V7000 V6.3" Redbook, found here: http://www.redbooks.ibm.com/abstracts/sg247938.html

Section 4.2.2 - Windows 2008 R2: Preparing for iSCSI.  (There are registry modifications that need to be made here as well.)

Section 4.3.2 - Creating iSCSI Hosts.
0
All Courses

From novice to tech pro — start learning today.