Unsolved
This post is more than 5 years old
8 Posts
0
25896
Dell PowerVault MD3000i, impossible to add iSCSI target portal
Hello
I have to install a MD3000i for our storage, but I met a problem when trying to add target portal using Microsoft iSCSI initiator.
Here's my configuration:
MD3000i and Windows 2003 Server (Standard Edition) SP2
(Windows server and Module Controlers are connected to network with adress in 172.25.x.x)
MD Storage Manager was installed on this server, storage array was detected.
Server and Module controlers are directly linked via In0 ports (adress in a subnetwork 192.168.1.x and 192.168.2.x, one for each Module controler).
I installed Microsoft iSCSI Initiator, launched it and tried to add target portal...
To add target portal, I use the 192.168.1.x adress of the array and select "Local Adapter": Microsoft iSCSI Initiator, "Source IP": 192.168.1.1
Then an error occurs: "Initiator Error".
Could someone say where is my mistake ? and what is that "initiator error" ?
Firewall was down, my rights are administrator, no CHAP was configured.
FredAlc
8 Posts
0
November 12th, 2009 08:00
Yes, ping is OK for the 2 module controlers
mrokkam
154 Posts
0
November 12th, 2009 08:00
Are you able to ping the array from the server?
mrokkam
154 Posts
0
November 12th, 2009 14:00
Based on what I see, your config should work....
Can you try to repeat the process without selecting a source IP (leave it as default or 0.0.0.0)? I remember something like that helping a similar issue I had seen a while ago.
-Mohan
FredAlc
8 Posts
0
November 13th, 2009 01:00
I've tested it before (with default parameters, with/without source IP) but I try another time and problem remains.
Actually I look at the network card, maybe something wrong in it ? compatibility ? (Broadcom NetXTreme Gigabit)
Dev Mgr
4 Operator
4 Operator
•
9.3K Posts
0
November 13th, 2009 04:00
I just want to make sure I understand your setup.
Server:
LAN IP: 172.25.x.x
iSCSI IP 1: 192.168.1.x direct-connected to controller 0 in-port 0
iSCSI IP 2: 192.168.2.x direct-connected to controller 1 in-port 0
MD3000i:
Management ports: both on the 172.25.x.x subnet
Controller 0 in-port 0: 192.168.1.x
Controller 0 in-port 1: irrelevant for this as it's not used/connected
Controller 1 in-port 0: 192.168.2.x
Controller 1 in-port 1: irrelevant for this as it's not used/connected
Is this correct?
FredAlc
8 Posts
0
November 13th, 2009 05:00
Yes, this is correct.
Server:
iSCSI IP 1: 192.168.1.1 direct-connected to controller 0 in-port 0
iSCSI IP 2: 192.168.2.1 direct-connected to controller 1 in-port 0
MD3000i:
Controller 0 in-port 0: 192.168.1.2
Controller 0 in-port 1: irrelevant for this as it's not used/connected
Controller 1 in-port 0: 192.168.2.2
Controller 1 in-port 1: irrelevant for this as it's not used/connected
Pawn33
28 Posts
0
November 13th, 2009 06:00
you may try re-installing the Initiator or updating to 2.08.
here is the link.
http://www.microsoft.com/downloads/details.aspx?familyid=12cb3c1a-15d6-4585-b385-befd1319f825&displaylang=en
See if that works.
if you ping the Md, you should be getting a TTL of 64 back from the box.
FredAlc
8 Posts
0
November 13th, 2009 07:00
I've already tried to reinstall the initiator (it's already a 2.08, build 3825), without improvement :emotion-6:
For the ping:
Pinging 192.168.1.2 with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
Reply from 192.168.1.2: bytes=32 time<1ms TTL=64
(Thanks for the help :emotion-21: )
Dev Mgr
4 Operator
4 Operator
•
9.3K Posts
0
November 13th, 2009 17:00
Did you modify your server's iqn name? If so, set it back to default and try again.
FredAlc
8 Posts
0
November 16th, 2009 00:00
Yes, server's iqn name was modified (set from " :XXX" to "iqn:XXX")
I set it back to default name and, even after a server reboot, no good news: still "intiator error" displayed.
DB100000
1 Message
0
November 24th, 2009 13:00
Are you Using Cross-Over cables?
FredAlc
8 Posts
0
November 25th, 2009 02:00
Crossover cables have also been tested ... :emotion-7:
I 'll install another server soon
mrokkam
154 Posts
0
November 25th, 2009 06:00
Have you tried using the MD Configuration Utility to setup your iSCSI sessions? It is a Dell utility available on their support website... Maybe that can help...
-Mohan
FredAlc
8 Posts
0
November 25th, 2009 08:00
I also used the MD Configuration utility (version 1.4), same error: "initiator error"
I don't see what could be wrong :emotion-9:
Hardware problem could be the answer... (no proof of it, only intuition)
As soon as new server will be available, I'll test it