Hi every one, my name is Anoop Mishra and I am Microsoft Trainer and CCI (Citrix Certified Instructor). You have been read previously my blog “How to Enable Offline file in Windows Server 2012” and most like by you. Now I wrote my blog “How to create iSCSI Storage”. I hope you will like this.
iSCSI Target Role first time include by Microsoft in Windows Server 2012 Operating System. This is a sub role of “File Server and Storage Service Role” With the help of this role we can create ISCSI LUN (Logical Unit Number) and can provide to other Node on there IP Address. ISCSI LUN use in Fail Over Clustering.
iSCSI is a protocol that use to access to remote,small computer system interface (SCSI)-based storage devices over a TCP/IP network. Iscsi carries standard SCSI commands over IP networks to facilitate data transfers over intranets, It use to manage storage over long distances. We can use iSCSI to transmit data over LAN or WAN, ISCSI uses TCP/IP port 3260.
TCP/IP Network:- We can use standard LAN Card and standard network switches to connect the servers to the storage device. To provide sufficient performance, the network should provide speeds of at least 1 gigabit per second (Gbps), and should provide multiple NIC path to the iSCSI target.
iSCSI Targets:- This is another method of gaining access to storage. iSCSI targets present or advertise storage, similar to controllers for hard Disk drives of locally attached storage. However, this storage is accessed over a network, instead of locally. Many storage vendors implement hardware-level iSCSI targets as part of their storage device’s hardware. Windows Server 2012 provides the iSCSI target server— which is effectively a driver for the iSCSI protocol—as a role service.
iSCSI initiators:- The iSCSI target displays storage to the iSCSI initiator (also known as the client), which acts as a local disk controller for the remote disks. All versions of Windows Server beginning with Windows Server 2008 include the iSCSI initiator, and can connect to iSCSI targets.
iSCSI Qualified Name (IQN):- IQNs are globally unique identifiers that are used to address initiators and targets on an iSCSI network.
For this Lab we will use 4 wiindows server 2012 Virtual Machine on
Hyper-V Server. All machine should be in Domain/Client environment. I used Domain Name as Microsoft.local
1. Server name is DC and this server act as a Domain Controller and I have installed ADDS (Active Directory Domain Service) Role and DNS (Domain Name Service) Role. This Sever IP Address is 192.168.100.1 Subnet Mask is 255.255.255.0, Preferred DNS IP is 192.168.100.1.
2. Server Name is Node1 this server is a member of Microsoft.local and this server will be use to access ISCSI DISK from ISCSI Target Server through ISCSI Initiator software. IP Address 192.168.100.2, Subnet Mask 255.255.255.0, DNS IP 192.168.100.1. This server we will use in Fail over clustering in future.
3. Server Name is Node2 this server is a member of Microsoft.local and this server will be use to access ISCSI DISK from ISCSI Target Server through ISCSI Initiator software. IP Address 192.168.100.3, Subnet Mask 255.255.255.0, DNS IP 192.168.100.1. This server we will use in Fail over clustering in future.
4. Server Name is Node3 this server is a member of Microsoft.local and this server will be use as Storage and on this Server will install ISCSI Target Role . On this Server We will install 30 GB SCSI Hard disk which will be use from ISCSI Target to create VHD which will be use to Node1.Microsoft.local and Node2.Microsoft.local. IP Address of Node3 will be 192.168.100.4, Subnet Mask 255.255.255.0, DNS IP 192.168.100.1.
Now We Start the Lab.
I have already installed Hyper-v feature on Windows 8 Enterprise Edition. Open Hyper-v now and all machine properly joined in Domain/Client environment. My Domain name is Microsoft.local. Now open Node3. Which will be act as a Storage Server.
Now Select node3 and goto settings->iSCSI Controller->Hard Drive->Add->New->Select VHDX->Select Name Field Type “iSCSI Storage Disk” and Select Hyper-v storage location for save the Disk.->Create a new blank virtual Hard Disk (Disk space 30 GB).
Select dynamically expending
Type Name and Desired Location to save the Disk
Type Disk Space 30 GB Select Next
Select finish now you can check your new hard disk have attached on Node3 V.M
Now Open Node3 and Log in from Domain admin account and run diskmgmt.MSC command and format this disk.
On Run type DISKMGMT.MSC Command
Now configure the disk as Online, Initialize Disk, Select MBR and Right Click on Disk and Select New Simple volume and Format in NTFS file system.
Now Disk has been formatted and ready to work
Now open Server manager on Node 3 server and Select Add Role and Feature.
Select File and Storage Services-> Click iSCSI Target Service – Click Next
Now Role have installed Click Close
Open Server Manager -> Select File and Storage Services
Click on To create on iSCSI virtual disk. Start the New iSCSI Virtual Disk Wizard
Select 30 GB DISK and Click Next
Type Disk 1 and Click Next
Type 10 GB Disk Space and Select Fixed Size and Click Next Button
Select New iSCSI target and click Next Button
Type Target1 and Click Next Button
Click on Add
Select enter a value for the selected type ->Select IQN IP Address
In IQN type Node 1 Ip Address 192.168.100.2 click OK Button
In IQN type Node 2 Ip Address 192.168.100.3 click OK Button
Select Create Button Now you will see Disk 1 have created
For create 2nd Disk Select Task and Right Click here Select New iSCSI Virtual disk
Type 10 GB Disk space and select Fixed Disk now Click Next
Select Existing iSCSI Target and Click Next
Disk 2 has been created now Select Close
Now we switched on Node1.Microsoft.local server
On Start Menu, Type iSCSI initiator and Enter Button Press
Press Yes Button
Select Discovery Tab and Select Discovery Portal
Type IP Address of Storage Server (192.168.100.4) and Press OK Button
Select Target Button and Press Connect Button you will see IQN Id will be Active now press OK
Open RUN Menu and Type Diskmgmt.msc Command
In Disk Management Console you are looking 2 Hard Disk has been attached and each disk size is 10 GB.
Now both disk format in NTFS file system Disk 1 will be Name Quorum and Drive letter (Q) and Disk 2 will be Name Resource and Drive letter (R)
Now Switched to Node2.Microsoft.local Server and Same Task Perform
Now Select Change Drive Letter of Disk 1 (Q) and Disk 2 Drive Letter (R)
Now your both (NODE1 and NODE2 ) Servers are ready to work for High Availability. Now you can install Fail over Clustering feature and proceed next.