Скачать или смотреть How to Create an iSCSI Initiator Group on Your NetApp Filer Using the CLI

How to Create an iSCSI Initiator Group on Your NetApp Filer Using the CLI

Use this quick tip to learn how to create an iSCSI Initiator group for your NetApp filer using the Command-Line Interface (CLI).

For more information about NetApp equipment, visit http://www.reliant-technology.com/pro... or call 1.877.227.0828 to speak with a NetApp storage specialist.


Video Transcript:

Hello. Welcome to Reliant Technology. This short video will explain how to create an iGroup for iSCSI, so let's begin. If we look at the NetApp OnCommand System Manager, we have a LUN that we have created with an _i. We will actually create an iGroup that will actually map to this LUN. As you can see there is ... We will create one called reliant ig_i. We created an _f for fiber channel in the previous video.

So we will start out by typing iGroup. Create. We're going to use a -I, for iSCSI. Then we're going to use a lowercase t for type. In this instance, we are going to use VMware. There are other types that you can use, such as AIX, Linux, or Windows, but in this instance, we are using VMware. We are then going to specify the name for this iGroup. We will actually create an iGroup called reliant ig_i for iSCSI and then we are going to specify the iSCSI IQN identifier. Going to go ahead and paste it in here so I don't have to type it all out. Now we are ready to create our iGroup, so we will hit enter.

If we go back to the OnCommand System Manager and do a refresh, you will see that now an iGroup named reliant ig_i has been created and it is type iSCSI with operating system VMware. We will then go back and do an edit and you will see that the IQN that we specified is part of this iGroup. So now we will actually go back to the CLI and we will actually add a second IQN identifier to this iGroup.

So we start off by typing iGroup and then add and then we're going to use a -f, now this -f disables checking for conflicts on the cluster partner so we're definitely going to use a -f here. Then we are going to specify the iGroup name that we just created. Then we're going to add a second identifier, which I'm going to paste in here, and then we're going to hit enter. Now, if we go back to here and we do a refresh on the system manager and go to edit, we will actually see now we have 2 IQN initiators in this iGroup.

So now the last step is we're going to map this iGroup to a LUN that we have specified as reliant_lun_i. So, if we go back to the CLI, we will actually now type in lun, map, we'll type in a lowercase f again so that it'll not do a conflict test on the cluster partner, then we will actually specify the full path to the lun. This includes the volume that the LUN resides in, in this case it's reliant_volume, and then we will specify the LUN name, which is lun_i and then we will specify which iGroup we want to map to this LUN. In this case it's the one that we just created, which is reliant ig_i. We will go ahead and hit enter and you can see that it was mapped to this LUN.

So now we will go back to LUN management, we will click edit and we will go to the initiator group and we can actually see that reliant_i is now mapped with this check box and for the LUN id it actually used the next available, in this case it was 0 so now we have presented the IQN's of the VMware server to this lun, so now that VMware can connect to this LUN.

Thank you for watching it.

RESOURCES & LINKS:
____________________________________________
Reliant Technology - https://www.Reliant-Technology.com
Linkedin:   / reliant-technology  
Facebook:   / relianttechnology  
Twitter:   / goreliant  

#Reliant #CreateaniSCSI #NetAppFiler