Unsolved
1 Rookie
•
10 Posts
0
413
August 9th, 2021 18:00
two MD series with dell poweredge r320 configuration in windows server 2008r2
Dear Team, This is my first time to meet with Dell MD 3200i and MD 1200 connected with two dell power edge r320 with Windows server 2008r2 installed in both power edge. I want to know what should I start with, completing OS reinstallation in one power edge. What are the settings required in Windows server for storage sharing or storage path ?


DELL-Erman O
Moderator
•
3K Posts
0
August 10th, 2021 04:00
Hello,
I believe you have installed the MDSM resource DVD https://dell.to/3xFe0mC
I found a very explanatory article about the settings you can make on the Windows 2008R2 side. Applicable to the MD3200i, this article shows it in great detail. I am quoting the following information from the link here. https://dell.to/2VEYDxd
"
Step 1
Windows 2008 R2 comes with the iSCSI initiator already installed, which is fine. Do not; I repeat, Do not (as I did during my first attempt) install the Microsoft Windows MPIO. The next screenshot shows the “Add Features Wizard”. This screenshot has been taken after finishing Step 2 (that explains why the “Multipath I/O” option has been greyed out).
Step 2
Now, you will need the Dell MD300i iSCSI software, you will need the “PowerVault MD300i Resource CD”. A recent version can be found here.
Start the installation. If you also want to install the “Modular Disk Storage Manager”, choose “Typical (Full Installation)”. If you only need the MPIO drivers, choose “Host”.
Curious to see what happened? Go to the Control Panel and open the MPIO feature, it looks like this; a number of Dell devices are now supported.
Step 3
From the Control Panel, you can start the iSCSI initiator, go to the Configuration tab and copy the Initiator Name for later use.
Step 4
Now it is time to give the Windows 2008 R2 server access to the MD3000i. Start the “Dell Modular Disk Storage Manager”, go to the Configure Tab and Add the Windows host. Specify the hostname and OS type.
In my case, there is already a Hostgroup available, to provide access to the VMware vSphere servers. Because the Windows server functions as a backup server, I added the newly created host to the same group.
Step 5
Return to the Windows server and the iSCSI initiator. Go to the Discovery tab. Click “Discover portal” and add the first of four IP addresses of the MD3000i. Repeat this step for the remaining addresses.
Step 6
Now, go to the Targets tab, the MD3000i shows up under Discovered Targets.
The status of the Discovered Target is Inactive. Click Connect, as a result the “Connect To Target” windows appear. Make sure both options are enabled.
Click the Advanced button, the “Advanced Settings” window shows up.
In the Connect Using section, under Local adapter, choose “Microsoft iSCSI initiator” and under “Initiator IP” and “Target portal IP” supply a matching combination, for instance: 192.168.100.76 (host) and 192.168.100.11 (MD3000i).
Repeat this step for the other 3 sessions.
Step 7
Return to the Targets tab. The status of the MD3000i is now Connected.
Click the “Properties” button, it will show the four sessions.
Click the “Devices” button.
In this example the MD3000i has 2 LUNS available (LUN11 and LUN12). LUN31 is for administrative purposes and does not show up because it is Disk -1 (compare with Disk 2 and Disk 3). Select the first Device (Disk 2, LUN11) and click the MPIO button.
Out-of-the-box, the “Load balance policy” is “Least Queue Depth”. Dell recommends the “Round Robin With Subset” policy. Note that two paths corresponding to the MD3000i controller that currently owns the LUN are Active; the other ones are in Standby mode.
The Details button shows the path details. You are already familiar with that.
Repeat this step for the other Devices.
"
Hope this will help!