Module 6: Creating an LUN

In this module, I will demonstrate how to setup an iSCSI LUN on the Storage system and I will map it with Window system as a drive.

iSCSI is a protocol to simplify SCSI-based storage that transferring data over ubiquitous network structures, for instance, LAN or VPN. A logical hard drive is locally mapped to a machine by using the iSCSI target and It provides an illusion that that mapped drive will able to managed by a local operating system. The local is called initiator and the server, that provide service is called initiator target.

Logical unit number (LUN):  LUN is a unique identifier of an individual or collection of physical or virtual storage devices that execute input/output (I/O) commands with a host machine by SCSI protocol.  An iSCSI LUN can be mapped to one or multiple iSCSI Targets to provide iSCSI storage services

The tasks  for the module 6:

  • license and start the iSCSI service
  • Configure iSCSI on Windows server 2008 R2
  • Use NetApp system manager to Create an LUN
  • Access LUNs from windows server 2008 R2
  • NondistrUPtively Move a volume that contains an LUN

Steps for the task: license and start the iSCSI service 

You must enable the iSCSI license by entering the iSCSI license key before you use the iSCSI target service, and you need turning on the iSCSI option from the target Storage system.

Step1: Go to the CLI interface, to check your iSCSI Service license key is enable or not! As you can see,  I already enabled iSCSI license key. If you don’t have the license key. You can visit my “Module 4: Getting Started with Basic Network Administration” to get a license key.

1.jpg

Step2: To enable the iSCSI license key,  Go to the Configuration -> System Tools -> Licences. Then click add. You will get a wizard that allows you to add license key. 2.jpg

Step3: Now you need to check that iSCSI service is started or not! If it has not started yet, you need to enable it. Go to the NetApp System Manager, click Protocols > iSCSI3.jpg

Step4: My iSCSI has not started yet. Now I will show how to start the iSCSI service. Go to the CLI console of your system storage and write the following code to start the iSCSI. Your iSCSI protocol will enable automatically after executing “Start” command.

options licensed_feature.iscsi.enable [to check the status of iscsi feature is enable or not!]

options licensed_feature.iscsi.enable [ help you to enable your iscsi feature]

iscsi start [By this command, iscsi service will be started]

4.jpg5.jpg

Steps for the task: Configure iSCSI on Windows server 2008 R2 

To access LUNs when you are using iSCSI, you must add an entry for the storage system using the iSCSI Initiator.

In this task, I will configure Windows Server 2008 to be an iSCSI initiator. One entry has to be needed for each storage system in the configuration regardless how many interfaces that are enabled for iSCSI traffic.

An active/active or HA pair storage system configuration requires two entries, one for each storage system node in the configuration.

Step1: Go to the DC Server and Start Microsoft iSCSI Initiator service from components service.  First, you need to go “Server manager”, Click “Component Services” from Tools or you can search “Component Services” from your startup. 6.jpg

Select “Startup type” automatic that ensure you that the service will be run automatic whenever you start the windows and use the service without any interrupt.If you get any problem to initiate you iSCSI map drive, check this status first for troubleshooting. 7.jpg

8.jpg

Now click “Start” for starting the “Microsoft iSCSI Initiator Service“. The iSCSI service starts every time Windows is started.9.jpg

Step 2: Now you need to iSCSI initiator Property. To find out this option, go to the Start button and, in the “Search programs and files textbox,” enter iSCSI initiator.10.jpg11.jpg

Step3: Now you need to check configuration tab from iSCSI Initiator Properties. You will get initiator name like: iqn.1991-05.com.microsoft:win2k8-01.pod01-vdc.momataj.local [The name must be unique and it will start “iqn” and last part is your machine name and domain ID]12

Step4:  Next you will configure the iSCSI service to see the e0a target portal group for your assigned storage system. Now click “Discovery tab” -> “Discover Portal”.Then you will see “Discover Target Portal” dialogue box appears. 13.jpg14.jpg

Enter the IP address of e0a on Controller1/Vsim IP of your assigned storage system, leave the port as 3260, and click the Advanced button.The Advanced Settings dialogue box appears:15.jpg16.jpg

17.jpg

Step 5: Click the Targets tab for verifying your target setup and notice that it shows one discovered target

18.jpg

Step 6: Click the Properties button from targets tab.You can see no current Session avaiable first time.19.jpg

Step7: To discover the list of the portal, Click the Portal Groups tab.

20.jpg

Step8: On the Targets tab, ensure that the storage system’s iSCSI Qualified Name (IQN) is highlighted, and click the Connect button for establishing a connection between the initiator and target iSCSI.

21.jpg22.jpg

Step 9: From the “Connect to Target” wizard, click setting: Ensure that “Add this connection to the list of Favourite Targets” is selected. and then Select “Enable multi-path”. Now click “Advanced”23.jpg

Step 10: In the Advanced setting dialogue box, Local adapter: Microsoft iSCSI Initiator, “Initiator IP” (the host that will act as an initiator or the computer you’ll mad drive)  and “Target portal IP” (That server you configured iSCSI LUN), and select the first interface on “Windows Server 2008 machine”.24.jpg

Click OK to return to the Connect To Target dialog box.The status of the target is now Connected. That means your initiator and target server connection has been configured to attach the drive.

25.jpg

Step 11: Now again click Properties. The Properties dialog box appears.  You can see “the connect session target portal group tag: 1000”, It indicates that your first target network is connected to generate the session.26.jpg

Step 12: Now you see the targeted assigned storage system appears on the favourite tab if you click ” Favourite Targets” because you accepted the default settings and made this a favourite target during “Advanced setting” configuration in step 9.27.jpg

Steps for the task: Use NetApp system manager to Create an LUN 

In this task, I will create a volume and LUNs: LUN1 and LUN2 by using NetApp System Manager and attach the LUN to an iSCSI initiator group (igroup).

Step1:  You need to copy the initiator name from your initiator host,  In my case, Windows 2012 R2 system, click iSCSI Initiator > Configuration for initiator name.

Step2: Open Controller1/Dataontap (vSIM) and click Storage > LUNs in NetApp System Manager, . You need to click the Create button. The Create LUN Wizard appears.28.jpg

Step3: On the General Properties page, enter these values:
a. In the Name text box, enter lun1.
b. In the Description text box, enter LUN for iSCSI exercise.
c. In the Size area, enter 50 GB [size of your LUN, that you want to create, try to keep it bigger]
d. From the Type drop-down list, select Windows. Note:: this is my setup, you can change it depend on your environment.29.jpg

Step4: Select Create a new flexible volume in, On the LUN Container page. Then click Next. Note: If you already created a volume for your LUN, you can choose “Select an existing volume or qtree for this LUN”

30.jpg

Step5: Now you are on the Initiator Mapping page, click the Add Initiator Group button.
You will see “Create Initiator Group” dialog box.

In the Name field, enter the initiator name of the Windows 2012 system you copied in Step 1.  Then Click the Initiators tab and click Add.In the Name field, re-enter the initiator name, and click Ok. click Create.31.jpg

32.jpg

Step6: Select the newly created initiator group and click Next33.jpg

34.jpg

Review the LUN Summary page and click Next to create the LUN 36.jpg

Step 7: Click Finish to complete the wizard. On the LUN Management tab, examine the features of lun1.

37.jpg

Step8: Now create the second LUN: lun2 by following the step 2 to step

38.jpg

Steps for the task: Access LUNs from windows server 2012 R2

In this task, I will attach LUN: lun1 and Lun2 with my initiator host: Windows Server 2008 R2 machine as drive

Step1: Click the Server Manager icon on your assigned remote Windows Server 2008 R2 machine, Expand the Storage node from the tree pane. Disk Management is visible.

39.jpg

Step2: If the two new LUNs that you created in the NetApp System Manager in your Storage System are not visible from the console tree, Select “File and Storage Service” -> right-click Disk Management and select Rescan Disks. After a short time, you will see the two LUN appears. Note: Sometimes you will not see them visible because of some configuration error, firewall connection problem.40.jpg

43

Step3: You will see your two LUNs are offline status and partition “Unknown”. Select lun1, right-click Disk #, and select Online to bring lun1 online. Then again, Select lun2, right-click Disk # and select Online to bring lun2 online45.jpg46.jpg

Step4: Now you need to initiate your lUNs as the master boot record (MBR) partition Disk. Right-click Disk # on lun1 and select Initialize Disk. The Initialize Disk dialog box appears, with information for both disks (one for lun1 and the other for lun2).47.jpg48.jpg49.jpg

Step5: Verify that the master boot record (MBR) partition style is selected for both LUNs (because you created both LUNs with this partition style), and then click OK

50.jpg

Step6: Right-click the new unallocated disk for lun1 and select “New Simple Volume” from the menu. You will get: The New Simple Volume” Wizard
NOTE: In this task, you provision the LUN with the New Simple Volume Wizard, However,  you can also use the Provisioning Storage Wizard from the Share and Storage Management tool to provision the LUN.51.jpg

52.jpg

Step7: On the Specify Volume Size page, choose the maximum possible LUN size and click Next.54.jpg

Step8: Now you need to assign your lun1 an available Drive Letter, such as E, and click Next.55.jpg

Step9: Select Format the LUN with the following settings, from the File system drop-down list, select NTFS, and then click Next.56.jpg

57.jpg

58.jpg

59.jpg

Step10: Now repeat the same steps for the lun2 to attach as a drive. Now I am showing the configuration from “Computer Manager”. Note: In the previus lun1 configuration, I did from server manager. You can do this configuration from “computer Management” as well.

60.jpg

60.jpg

62

63.jpg

64.jpg

****Navigate to the drive letter of the LUN and write a test file to the LUN to verify that it is working correctly.

Steps for the task: NondistrUPtively Move a volume that contains an LUN

In this task, move a volume containing LUN2 to a new aggregate and then move it back.

Step 1: Remove the LUN2 export from the /etc/exports file and unload its export from memory:

exportfs -z /vol/lun2

65.jpg

Step 2: Open the mapped drive for LUN2, and start a copy of several files. After you start the operation, do not disrupt access to the LUN while the LUN’s volume is being moved to a new aggregate.

Step3: Move LUN2’s volume, originally on aggr2, to aggr1:

> vol move start lun2_vol aggr1

NOTE: The nondisruptive volume move requires similar aggregates on both source and
destination (32-bit to 32-bit or 64-bit to 64-bit only).67.jpg

vol move status lun2 –v [Verify the status of the move operation]

Step4:  After the move is complete, verify that you can continue to access LUN2 on your Windows server.

68.jpg

Step  5: Now again move the volume that contains LUN1 back to aggr2 but this time does a manual by the following command.

vol move start lun2 aggr2 –m [-m means you are moving the lun to aggr manully]

Step 6: The mapped drive for LUN2 on your Windows server and begin a copy of several files. Perform the move. After complete moving, verify that you can continue to access LUN2 on your Windows

vol move cutover /vol/lun2

What is thin provisioning? 

Thin provisioning is the act of using virtualization technology for optimising storage utilisation to provide storage on-demand-allocation and over-subscription capability.

iSCSI Target Mapping: Map the iSCSI LUN to one or more iSCSI Targets.

Problem: If you get you LUN is not visible in the disk management, you can follow my solution.

Solution:

1. Check your component services: Microsoft iSCSI Initiator service is starting or not. If it is not – click start and from property select it “automatic”. If it is running, then restart it again.

2. Check your firewall. turn off your public firewall from server manager.69.jpg

3. Disconnect your initiator connection and connect it again. 70.jpg

4. Check your iSCSI service is running or not! in your storage system in the NETAPP manager system. 71.jpg

5. Click Edit to check your target node name is correct or not! match it with your windows server initiator name.72.jpg

6. After verifying all the steps, Go to again “Disk Management”. Rescan disk again. I hope you will get visible your LUNs on the disk management screen.

Basic NetApp Configuration and Administration modules are complete here! Now the time to move VMwere VSphere. 

Thank you 🙂 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s