Solved

Connect iSCSI to Server 2008 R2 IBM DS3300

Posted on 2010-11-16
7
3,453 Views
Last Modified: 2012-05-10
I have a VMware machine, Server 2003 that is set up iSCSI to our IBM DS3300 storage with 2 controllers.  It was setup by consultants who put the system in place, so I don't really know how or what they set up, so I'm looking for as close to step-by-step instructions as possible: Simply, we are decomissioning the Server 2003 machine (was never active), and want to install new Server 2008R2, and connect to the SCSI drives as setup in Server 2003, to make it our new File Server. The IBM Storage Manager 2 was used to set up the hosts and drive mappings.

Do I just copy the settings to the new 2008 Server?  I don't have any space to create a new virtual machine and keep both the 2003 and 2008 server images, so I need to get all the settings from 2003, wipe it, and install new 2008 build.

The current settings are as follows:
In the DS3300 Setup- Configured Host NTFSFILE with iSCSI Initiataor Name iqn.1991.05.com.micrsoft:ntfsfile and Host type as Windows 2000/Server 2003/Server 2008 Non-Clustered (supports DMP) thats 750GB. (Let me know if you need any other settings from the Storage Manager)

On the Server we have:
2 Network Connections:
1 - VMware Accelerated AMD PCNet Adapter 172.16.100.60/24 - Labeled as ISCSI A
2 - VMware Accelerated AMD PCNet Adapter #2 172.16.101.60/24 - labeled as ISCSI B

Data drive properties in My Computer on server:
Hardware Info:
IBM 1726-3xx FAStT Mutli-Path Disk Device Bus 0, Target id, LUN 0
IBM 1726-3xx FAStT SCSI  Disk Device Number 0, Target Id 0, LUN 0
IBM Universal X Port SCSI Disk device Number 0, Target Id 0, LUN 31
VMware Virtual disk SCSI Disk Device. Bus 0, Targetid 0, LUN 0

Microsoft iSCSI Initiator Properties 2 connections
iqn.1992-01.com.lsi:1535.600a0b8000490cc70000000048c4de99
Initiator Name: iqn.1991-05.com.microsoft:ntfsfiler.company.net

Disk Managment Info:
IBM 1726-3xx FAStT Multi-Path Disk Device
Location: Port 2,2 Bus 0, Target ID 0, LUN 0

Microsoft iSCSI Initiator Properties:
Initiator Node Name: iqn.1991-05.com.microsoft:ntfsfiler.company.net
Discovery - Target Portals 172.16.100.100 Port 3260 and 172.16.101.100 Port 3260
Targets: one listed as iqn.1992-01.com.lsi:1525.600..
1 persistent target, same as above.

Ok, so now that I've given all possible information I can think of, just need to know how to best proceed in setting this identical connection up on the Server 2008R2, as well as anything that needs to be disconnected or removed on 2003 when decommissioning this server.  I'm not not really concerned with data loss on this drive, as there is nothing to important on here, I just would like the 2008R2 server to be connected to this 750GB drive.

Thank you in advance!
0
Comment
Question by:fireguy1125
  • 4
  • 3
7 Comments
 
LVL 77

Accepted Solution

by:
arnold earned 500 total points
ID: 34152737
There is nothing that needs to be done on the win2k3 given by your statement that the two will not be active at the same time.

The only thing to consider/confirm is that the iscsi targets are not used to boot the system i.e. c:\ is not an ISCSI provided drive.
Check the configuration on the IBM storage to see whether these targets are limited to the windows 2003 VM local IPs i.e. 172.16.100.60 and 172.16.101.60
It they are, you would need to make sure that the new windows 2008 has those IPs or alter the configuration on the storage array to allow access to these targets from different IPs.

Once you create the new windows 2008, you would use the ISCSI initiator and add the two IPs for the iscsi provider 172.16.100.100:3260 and 172.16.101.100/24 for multipath access.
one that is done, you should see the available targets that the storage has. Connect to it and you will have access to the data.

The only issue you will have is if the current windows 2003 is the only domain controller and the security settings within this ISCSI drive are domain based versus member server base.  In this type of a scenario, you would need to assert your rights via advanced take ownership of files using the server/domain administrator account.
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 34159304
Ok, wiped the 2003 server, built the 2008R2 server, have 3 Network Adapters configured in the Virtual Machine Properties, with identical Network labels/connections as in the previous 2003 server settings.  However, when I boot the VM, and look at the network adapters, the 3 are listed, but all 3 are showing  being the same driver, the Intel PRO/1000MT.

Server 2003 was showing one being the Intel, and the others being the Broadcom card that is used for the iscsi connection.  I don't see where this can be changed, but I know that's not the way it was setup previously.  once physical adapter on the Host is used for network only, the other physical adapter is used for the iscsi san.  However the server is showing that the intel is used by both the network AND iSCSI.
0
 
LVL 77

Expert Comment

by:arnold
ID: 34160374
It does not matter what the driver or the type of the VM network adapter is as long as it works and gets an IP that you need to access the IPs of the IBM storage.
You can change the network adapters in the VM configuration.

Are you using the VM network adapters as NAT or as Bridge to Host adapter such that it can get an IP on each of the physical LANs?
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 1

Author Comment

by:fireguy1125
ID: 34164695
Not sure, which mode, here are screenshots how can I tell?
 network adapters networking
0
 
LVL 77

Expert Comment

by:arnold
ID: 34166842
What is the HOSTS LAN segment?

LAN <=> Host  <=> VM NAT LAN

You  seem to have defined the VM NAT LAN to use the same IPs as the Physical LAN.

You need to define the VM as a bridge to the HOSTS network interfaces.
LAN <=> Host <=> bridge <=> VM network interfaces
This way when the VM network interface gets an IP it will be on the physical LAN.
             
The 2008 VM server should actually have two interfaces label the same way:
1 - VMware Accelerated AMD PCNet Adapter 172.16.100.60/24 - Labeled as ISCSI A
2 - VMware Accelerated AMD PCNet Adapter #2 172.16.101.60/24 - labeled as ISCSI  
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 34167385
The hosts segment is 192.168.0.0/16

I don't see the VMware Accelerated AMD PCNet Adapter as an option anywhere.

Where do I define the VM as a bridge?  When I go to the Virtual Machine properties, the only 2 adapter type options I have are E1000 and Enhanced vmxnet. With the choice of 3 network connections:
VM Network
Virtual Machine Network ISCSI A
Virtual Machine Network ISCSI B

See screen shot.
addnetworkadapt.jpg
0
 
LVL 1

Author Comment

by:fireguy1125
ID: 34167552
Ok, I  changed the interface settings of the 2nd and 3rd interface within Server2k8, ran through the iSCSI initiator, and it detected and established the drive, and seems to be working fine.

Also, reading into it on vmware performance tuning best practices it said the following:

The default virtual network adapter emulated inside 32-bit guests is the AMD
PCnet32 device configured with VMware's vlance driver (e1000 for 64-bit guests).
However, vmxnet provides much better performance than vlance and should be
used for optimal performance.
The vmxnet driver implements an idealized network interface that passes through
network traffic from the virtual machine to the physical cards with minimal
overhead. To use the vmxnet network adapter, install the vmxnet driver (available
in VMware Tools) on your virtual machines.
Note that the network speeds reported by the guest networking driver on the
virtual machine do not necessarily reflect the actual capacity of the underlying
physical network interface card. For example, the vlance guest driver on a virtual
machine reports a speed of 10Mbps, even if the physical card on the server is
100Mbps or 1Gbps, because the AMD PCnet cards that ESX Server emulates are
10Mbps, by definition. However, ESX Server is not limited to 10Mbps and transfers
network packets as fast as the resources on the physical server machines allow.

So it appears the e1000 is for 64bit OSes, and the AMD was for 32bit, which explains everything, and I just looked through the settings of other Vms and see this is the case.  So it seems to be fine now, thank you so much for your persistence!
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question