This post is more than 5 years old
22 Posts
0
46757
January 7th, 2010 10:00
AX4-5i Newbie Question, Adding Second Nic
Hello-
I have a window 2003R2 server connecting via an iSCSI software initiator into an AX4-5i with four target IPs. (spa0,a1,b0,b1) I am using MS MPIO 2.08 with Powerpath 5.3. All four paths are connecting fine and showing active. I am trying configure a second nic, configured on a separate subnet, to connect from the 2003R2 host into the AX4-5i, but I am having issues. When I open the iSCSI Initiator Properties page and go to Targets I see four connected paths. I am highlighting one of the paths, selecting log on, checking 'automatically restore this path' and 'enable multipathing', then selecting advanced. In the advanced page for local adapter I am choosing Microsoft iSCSI initiator. For source IP I am choosing my new nic's IP address. Under target portal I only have one option, which is the IP I listed originally under the discovery tab. When I select OK I get the error "The target does not have enough resources to process the given request." I have tried manually typing a different IP address under the target portal but it won't let me. Can someone help me to understand what I am doing wrong?
Thank you in advance.
Erik
Dev Mgr
4 Operator
•
9.3K Posts
1
January 7th, 2010 20:00
Just to make sure I understand your setup right now (as in; before adding in a 2nd NIC):
- you are using a single NIC with a single IP address
- you are connecting (logged in) to all 4 ports on the array
- therefor all 4 of those ports are on the same subnet
Now you want to add a 2nd NIC (good move! (add failover and loadbalancing)) on a separate subnet (also a good move, but mostly if you also put it on a separate physical switch (vLAN'd or just fully dedicated switch (isolated/disconnected from the rest of your network), you need to pick 2 of the iSCSI ports and change their IP to the new subnet as well. Before doing this, go into the iSCSI initiator, highlight the first port that you'll be changing the IP on, go to details, checkbox the connection and log off. Now do the same for the other connection that you'll change the IP on.
Now change the IP addresses on those 2 iSCSI ports in Navisphere Express.
You should be left with:
- SPA0 on the old subnet
- SPA1 on the new (2nd) subnet
- SPB0 on the old subnet
- SPB1 on the new (2nd) subnet
Make sure the cables go to the correct switches.
Test you setup with a simple ping to all 4 iSCSI IP addresses.
Go into the iSCSI initiator, pick the target tab and hit refresh (need to make sure the iSCSI initiator re-polls the ports to 'notice' the change in target IP addresses).
Now you pick one of the inactive connections, click logon, check the reconnect-on-reboot checkbox (don't need the multipathing checkbox from what I understand as you're only connecting once to each physical port and Powerpath 'merges' the 4 connections into 1 'disk-instance'), leave "advanced" alone, and click ok to see if it logs on.
Personally I prefer to just let the server utility do my iSCSI logons (after the networking has been figured out and tested (with pings).
Dev Mgr
4 Operator
•
9.3K Posts
1
January 8th, 2010 10:00
Go to the persistent bindings/favorite targets tab (name depends on which OS and iSCSI initiator). You'll probably see 6 (or a multiple of 6) entries here I would think. These 'extras' are leftovers from the old connections.
If you can afford another 5 minute downtime (iSCSI disconnect), I'd recommend:
- log off from all iSCSI targets
- remove all persistent bindings/favorite targets
- reconnect the 4 iSCSI targets
If the issue then still persists I'd take it 1 step further:
- log off from all iSCSI targets
- remove all persistent bindings/favorite targets
- remove all the entries on the discovery tab
- reboot the server
- re-add 1 iSCSI IP address under the discovery tab (the iSCSI protocol allows the array to provide all possible targets when the iSCSI initiator queries just that 1 IP/port)
- reconnect the 4 iSCSI targets
Dev Mgr
4 Operator
•
9.3K Posts
1
January 11th, 2010 14:00
In there it should only list the host with 1 IP. This should be the management (LAN) IP of the server, not the iSCSI IP(s). The hostname and IP in that section are purely to help recognize which server is using with virtual disk (it's easier to recognize than having to learn to read the whole iqn name of the server).
elarso
22 Posts
0
January 8th, 2010 09:00
Thank you for the response. I followed your instructions and everything went according to plan. I can trespass the assigned lun to both sp's with no errors and ping the four sp IP addresses fine. I have one follow up question. When I launch the iSCSI shortcut and go to the targets tab and select the two targets that I changed over to the second IP address and hit details I now see two targets listed under Identifiers. When I highlight one of them it states connected, when I highlight the other one it states reconnecting. I can manually log off the reconnecting one but it reappears on reboot. Things appear to be working okay, but it makes me nervous. Any thoughts?
elarso
22 Posts
0
January 11th, 2010 11:00
Client working perfectly. On the Navisphere side should I see the host listed separately for each different IP I have assigned to it or should it only show up once with both IPs under the single listing? Right now when I go to the Hosts tab, in Navisphere, the host is listed twice, but it has a 'U' next to the reference with the new IP address I assigned. When I go to storage groups to my storage group to my host I only see the host listed once with the original IP referenced. Can you clarify how the host should show up in Navisphere when it has two separate IP's assigned to it? Once with both IP's referenced or twice with each unique IP address.
Thanks again,
spgsit
185 Posts
0
January 4th, 2012 13:00
I know it is rather old post, but I inherited AX4-5i & it gives me headache only
With ESX 4/5 it works fine using MRU
But with Win 2008 R2 & MS iSCSI (using dual Interl Pro/1000 MT adapter) initiator on two subnets I get mostly:
- Connection to the target was lost. The initiator will attempt to retry the connection.
- Target failed to respond in time to a Task Management request.
- Target sent an invalid iSCSI PDU. Dump data contains the entire iSCSI header.
- Initiator sent a task management command to reset the target. The target name is given in the dump data.
- The initiator could not send an iSCSI PDU. Error status is given in the dump data.
- Target failed to respond in time for a login request.
If I connect to a single target & have the targets on this very SP it works fine.
Any attempt at multipathing |& the hell breaks lose
Using 2 isolated separate PowerConnect 5424
Also tried Broadcom BCM5708C iSCSI HBA, and also PowerPath, which was no different ("dancing paths" etc)
Anybody has any ideas?
Thanks
Seb
DELL-Sam L
Moderator
•
7.6K Posts
0
January 4th, 2012 15:00
Hello Seb,
Based on the information that you provided what would need to be done is to look at the SP collects from the AX 4-5i as well as get logs from both Power connect switches and ESX to see where the problem is occurring at. Based on all that it might be best to contact tech support to assist &ensure that the setup is correct and that everything will run smoothly.
Here is a link to the install guide for the AX 4-5i that can help make sure that your setup is correct with their best practices. www.emc.com/.../dell-ax45-install.htm
Let us know if you have any other questions
spgsit
185 Posts
0
January 5th, 2012 00:00
As I said, ESX works fine (hence the setup is right), it is only Win Server 2008 R2 that does not work correctly
Seb
DELL-Sam L
Moderator
•
7.6K Posts
0
January 5th, 2012 11:00
Seb,
Sorry I misread your question. What you can do if you haven’t already is to change the binding order of the nic’s so that the iSCSI will log in before windows starts so that once windows comes up your connections are seen & connected. To change the binding order you need to go to the network connection select the local area connection hit the alt key and it will bring up another menu where you choose advance Advanced settingselect the iSCSI connection & move it to the top if not already done.
Let us know how it goes.
spgsit
185 Posts
0
January 5th, 2012 12:00
But it is not the bind order, it is the whole "experience"
With ESX it works rock solid, with W2K8R2 & two NICs, subnets, M$ iSCSI initiator (Powerpath or not) is just wonky.
I use one volume for ISO storage.
With single connection to SP A0 (virtual disk is accessed via SP A) it is almost OK (I can almost use this volume - some lockups happen, any exe can not be executed - APPCRASH)
But with more connections (to SP A1, SP B0, SP B1) is all goes heywire (volumes not recognized, Disk Management will completely lockup etc). To a point of hard reset required
Seb
Dev Mgr
4 Operator
•
9.3K Posts
0
January 6th, 2012 06:00
Which version of PowerPath did you install?
spgsit
185 Posts
0
January 6th, 2012 12:00
EMCPower.X64.signed.5.5.P01.b358
Seb
DELL-Sam L
Moderator
•
7.6K Posts
0
January 6th, 2012 13:00
Seb,
That version of powerpath that you are currently using states the following: “PowerPath 5.5 P01 for Windows is a patch package recommended to PowerPath Migration Enabler and Encryption customers only.” If you are using that then you have the correct version. If not then EMC states that it is best to use the following version: PowerPath 5.5 SP1 is a full-package installation service pack. Here is a link to EMC site & you can see the difference in the 2 versions that they state. https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/appmanager/km/secureDesktop?_nfpb=true&_pageLabel=servicesDownloadsTemplatePg&internalId=0b01406680021d87&_irrt=true
Let us know how it goes
spgsit
185 Posts
0
January 6th, 2012 14:00
The content you are trying to access is unavailable. This content may have expired, the link may be incorrect or you may not be entitled to access it with your account.
DELL-Sam L
Moderator
•
7.6K Posts
0
January 6th, 2012 14:00
Seb,
If you have access to EMC powerlink then you need to login and then access the link.
Let us know how it goes