Win. PE v. 3. 0 and Microsoft i. SCSI Initiator. You may also be interested in my Power. Shell Script to Build a Custom Win. PE v. 3. 0 ISO posting. We have one Guest OS, which is a. The Windows Assessment and Deployment Toolkit (ADK) is compatible with Windows Server 2012, Windows 8, Windows 7, Windows Server 2008, and Vista. The easiest way to connect to you iSCSI storage LUNs from Windows Server 2008 is by using the iSCSI initiator GUI. With the GUI you can easily make a connection. We explain how to configure and use an iSCSI target on a NAS server with Windows' built. C: \Windows\System. Mount. Location\Windows\System. Windows\System. 32\iscsicli. Windows\System. 32\iscsicpl. Windows\System. 32\iscsicpl. Windows\System. 32\iscsidsc. Windows\System. 32\iscsied. Windows\System. 32\iscsiexe. Windows\System. 32\iscsilog. Windows\System. 32\iscsium. Windows\System. 32\iscsiwmi. Windows\System. 32\Drivers\msiscsi. Windows\System. 32\en- us\iscsicli. Step 1: Set up your target and communications infrastructure. Before you install the iSCSI initiator on any of your servers or workstations, you must have something. Windows\System. 32\en- us\iscsicpl. Windows\System. 32\en- us\iscsicpl. Windows\System. 32\en- us\iscsidsc. Windows\System. 32\en- us\iscsiexe. Windows\System. 32\en- us\iscsilog. Using Regedit load the Win. PE registry hives directly under HKEY. Install, configure, and use Microsoft's i. SCSI initiator? This blog post is also available as a Tech. Republic download in PDF form. Internet Small Computer System Interface (i. SCSI) has taken the storage world by storm. No longer is shared storage a niche enjoyed by only large, wealthy corporations. Internet SCSI is leveling the playing field by making shared storage available at a reasonable cost to anyone. By leveraging the ubiquitous Ethernet networks prevalent in most organizations, IT staff training costs for i. SCSI are very low and result in quick, seamless deployments. Further, operating system vendors are making it easier than ever to get into the i. SCSI game by making i. SCSI initiator software freely available. By using an i. SCSI initiator, target- based volumes can be mounted on a server as if they were local volumes and are managed as such. A gigabit Ethernet network infrastructure — i. SCSI requires an IP- based Ethernet network for its transport between systems with initiators (servers) and targets (storage arrays). In this How do I.. This can be one of the enterprise class arrays, such as those available from Left. Hand, Equal. Logic, Dell, or EMC or, if you're on a tighter budget and want to build your own array, a target running i. SCSI target software, such as Star. Wind. For more information about building a SAN on the cheap, take a look at: I recommend that, whenever possible, you use either a physically separate infrastructure or separate IP network/VLAN for your i. SCSI traffic. By doing so, you simplify troubleshooting and configuration later on. Setting up and configuring your target is beyond the scope of this article. Step 2: Configure your local i. SCSI network adapter. One best practice is to assign either a dedicated gigabit Ethernet NIC or TCP offload adapter (To. E adapter) in each server to handle i. SCSI traffic — in other words, don't share your user- facing network connection for storage traffic. If you've created a separate physical network or VLAN for storage traffic, assign this adapter an IP address that works on the storage network. By placing storage traffic on its own network that is routed separately from the main network, you increase the overall security of your storage infrastructure and simplify the overall configuration. Step 3: Download Microsoft's i. SCSI initiator — if necessary. Depending on the operating system you're using, you may need to download Microsoft's i. SCSI initiator software. If you're planning to connect to an i. SCSI target from a Windows XP or Windows Server 2. Microsoft's i. SCSI initiator download page and obtain the software. If you're connecting from a Windows Vista or Windows Server 2. Microsoft's i. SCSI initiator is included with these operating systems, so you can safely skip this step. Make sure to download the initiator that is designed for your operating system. Microsoft provides builds for both 3. Windows. In the 6. Itanium- based processors. Step 4: Install the i. SCSI initiator. If you're running an operating system on which the i. SCSI initiator software is not installed, execute the file you downloaded and follow the installation instructions (Figure A). The installer will ask you to decide which components you would like to install. See Step 6 for more information about how MPIO can be of benefit. If you have a target that supports Microsoft's MPIO (check with your manufacturer), you should enable this option. Otherwise, if your target supports MPIO through the use of a proprietary device- specific module (DSM), obtain that DSM from your array manufacturer and follow the manufacturer's installation recommendations. Step 5: Connect to the i. SCSI array. Now that you have the initiator software installed, you need to tell it where to look for mountable volumes. Start the initiator configuration by going to the Control Panel and choosing the i. SCSI Initiator option. From the initiator, choose the Discovery tab, shown in Figure B. This will open the Add Target Portal dialog box, shown in Figure C. The default communication port for i. SCSI traffic is 3. Unless you have changed your port, leave this as is. If you have configured CHAP security or are using IPSec for communication between your client and the array, click on the Advanced button and make necessary configuration changes. The Advanced Settings dialog box is shown in Figure D. Note that, at this point, you're not connecting to an actual volume, but only to the array in general. To see the list of available targets on the array you selected, choose the Targets tab, shown in Figure F. A window pops up (Figure G) with the target name and two options from which you can choose. If you want your server to connect to this volume automatically when your system boots, make sure you choose the Automatically Restore This Connection When The System Boots check box. Unless you have a good reason otherwise, you should always select this check box. If you do not, you can't make the i. SCSI target persistent after a reboot and will need to manually reconnect it. To enable high availability and to boost performance, choose the Enable Multi- path check box. Make sure to understand that multi- pathing (MPIO) requires multiple network adapters dedicated to the i. SCSI task, and for maximum availability, you should also have a fully meshed gigabit Ethernet architecture for your storage traffic. Again, if you are using CHAP or IPSec for communication with a target, click the Advanced button to bring up the Advanced Settings dialog box you saw in Figure D. The target status in the imitator window should change to Connected. If you selected the Automatically Restore This Connection When The System Boots check box as explained in the previous step, you can now add the target to the i. SCSI service's binding list. By doing so, you make sure that Windows does not consider the i. SCSI service fully started until connections are restored to all volumes on the binding list. This is important if you have data on an i. SCSI target that other services depend on. For example, if you create a share on your server and that shared data resides on an i. SCSI target, the Server service that handles the share depends on the i. SCSI service's complete availability to bring up the shares. Note: With older versions of the i. SCSI initiators, creating this kind of dependency structure required you to reconfigure individual service dependencies — a process that could get complicated. With the i. SCSI Initiator version 2, Microsoft has fixed this issue, but you still need to bind the targets. This will bind all available i. SCSI targets (that can be bound) to the i. SCSI startup process. If you want to choose individual targets to bind, click the Add button. However, you will need to know the target's drive letter or mount point. At this point in these instructions, we haven't gotten quite that far. Take a look at this: Open Computer Management (Start . Choose the Disk Management option. If the volume you are using is still blank — that is, newly created on your i. SCSI target and does not contain data — Windows will pop up the Disk Initialization wizard, as shown in Figure J. This disk is a small target I created on my i. SCSI host. An i. SCSI- based volume follows the same rules as any other Windows volume. You can create this volume as basic or dynamic (although dynamic is not recommended for i. SCSI) or even as GPT (GUID partition table) volumes, which support volumes in excess of 2. TB. Just as is the case with any Windows volume, you need to initialize the new drive, create a partition, and format the new volume. Take note in Figure J that Windows truly sees this disk as just another typical volume. There is nothing on the Disk Management screen to indicate that Windows is treating this volume any differently because it is stored on an i. SCSI array. Summary. Once you get past the mental adjustment that has to take place when you start using shared storage, you'll probably find that i.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |