Budget Laboratory - Part 2 - IsCSI Virtual SAN With FreeNAS 8 - Fix The Exchange!

17/8/2021 Budget Laboratory: Part 2 - iSCSI Virtual SAN with FreeNAS 8 | Fix the Exchange!
The Wayback Machine - https://web.archive.org/web/20160906011150/http://www.fixtheexchange.com:80/Budge…

Search
HOME BLOGS FORUMS ABOUT CONTACT
404 Not Found

nginx/1.15.8
Home / Budget Laboratory / Budget Laboratory: Part 2 - iSCSI Virtual SAN with FreeNAS 8
Budget Laboratory: Part 2 - iSCSI Virtual SAN

with FreeNAS 8
SUBMITTED BY JOSH ON TUE, 09/06/2011 - 15:04
Storage Area Networks (SANs) are used in most Enterprise class networks, you'll also find them at a
lot of small and medium businesses. A lot of systems rely on SANs to provide high availability
features. A SAN is great to have for setting up shared storage for any type of cluster. Fiber used to
be dominant for SAN connectivity. You'd need Fiber Host Bus Adapters (HBAs) in every server you
wanted attached to your SAN, and a Fiber switch to connect everything. Then came iSCSI, which
works with much cheaper Network Interface Cards (NICs), and can use regular network switches, as well us much
cheaper copper cables. At first iSCSI wasn't as fast as Fiber, topping out at gigabit speeds, so if speed was
important, you'd stick with Fiber. Now with 10Gigabit Ethernet being readily available, you can get iSCSI SANs that
are both cost effective and high performance.
A full blown hardware SAN is still very expensive, so you're probably not going to buy one for a Lab. Luckily there
are a few ways you can create Virtual SANs for FREE! For Part 2 of my Budget Laboratory series, I'm going to show
you how to create an iSCSI Virtual SAN with FreeNAS 8 . FreeNAS is another great open source product based on
FreeBSD.
This portion of the lab build can be done at absolutely no cost, assuming you already have the required hardware.
You will need:

VMWare Workstation OR VMWare Player*
FreeNAS 8**
300 GB of free space
https://web.archive.org/web/20160906011150/http://www.fixtheexchange.com/Budget-Laboratory-Part2-iSCSI-Virtual-SAN-with-FreeNAS-8 1/47
*If you followed Part 1 of this series, you should already have VMWare Workstation, which has a free trial, and you
will need to use it. VMWare Player is completely free, you should be able to setup your Virtual SAN using it if you so
choose, however I'm using VMWare Workstation for the creation of this article.
**I'm using the 64-bit version for this article.
Step 1: Create a Virtual Machine for your Virtual SAN
If you haven't already, open VMWare Workstation.
From the "Home" screen, click the "New Virtual Machine" button, or hit "CTRL+N".
Select "Custom (advanced)" and click "Next".
Accept the defaults and click "Next".
Select "Installer disc image file (iso):", browse to the location where you saved your FreeNAS .iso at, then click
"Next".
Select "Other", then select "FreeBSD 64-Bit" from the drop down list, then click "Next"
Give your VM a name, then click "Next".
Accept the defaults for the CPU and click "Next".
Accept the defaults for RAM and click "Next".
UPDATE: The recommended minimum RAM for FreeNAS 8 is 512MB, so you should probably change your RAM to
512MB here. However, I have been running it with 256MB without issues. You can always increase the RAM on your
VM later.
We'll be changing the Network settings later, so this page doesn't matter, click "Next".
Accept the defaults for I/O Controller types, and click "Next".
Select "Create a new virtual disk", then click "Next".
Select "SCSI", then click "Next".
Accept the defaults of 8 GB and "Store virtual disk as a single file", then click Next.
Accept the default and click "Next".
Make sure "Power on this virtual machine after creation" is NOT checked, and click "Finish".
BEFORE powering on the Virtual Machine, we need to edit the hardware settings. Click the "Edit virtual machine
settings" link on your FreeNAS Virtual SAN Virtual Machine, or hit "CTRL+D".
If you followed Part 1 of this series, you'll need to select "Network Adapter", then select "Custom: Specific virtual
network", and choose the VMNet that is bridged to the LAN side of your network. For me this is VMNet3. Otherwise
you can just choose "Bridged: Connected directly to the physical network".
After that we need to add another "Hard Disk", click the "Add..." button.
Select "Hard Disk" and click "Next".
Select "Create a new virtual disk" and click "Next".
Select "SCSI" and click "Next".
Set the "Maximum disk size (GB):" to 300, select "Store virtual disk as a single file", and click "Next".
Note: Originally I used ten 30GB drives to sort of mimic a physical disk array. Since the virtual drives are all stored
on the same physical drive, there's no real benefit to doing it that way. So in the interest of keeping things simple,
a single 300GB drive works fine. If you were going to setup a Virtual SAN for any sort of production use, you'd want
to give the VM direct access to several physical drives.
Accept the default and click "Next".
Click "OK" on the Virtual Machine Settings page.
Your Virtual Machine is now ready to power on.
Step 2: Install FreeNAS.
Power on the Virtual Machine.
Hit 1 to start the install.
Select the 8 GB drive as the destination, then hit "Enter".
Hit "Y" to continue.
The installation completes, hit "Enter" to continue.
Hit 3 to Reboot.
When FreeNAS boots, hit 1 to configure the network, then 1 to select the interface, n, then y, give the interface a
name, enter a static IP. Hit "n" for "Configure IPv6".
Step 3: Configure FreeNAS through the web interface.
Open a web browser and browse to the IP you assigned to your FreeNAS Virtual Machine in Step 2.
You'll see a flashing "Alert" in the upper right corner letting you know that you need to set a password, so lets take
care of that first. Expand "My Account".
Click the "Change Password" link, set and confirm a password, then click "Change Admin Password".
Next we need to create a volume. Click the "Storage" icon at the top of the page.
Give the volume a name, I named my "SAN1". Check the disk, and select "ZFS" as the "Filesystem type" then click
"Add Volume".
Note: If you used multiple drives, you'd have a few more options here. Depending on the number of drives
selected, different RAID types would become available. With ZFS you'd see RAID-Z and RAID-Z2. For more
information on RAID-Z, check out Jeff Bonwick's blog post over at Oracle . Jeff Bonwick is the inventor of RAID-Z.
For more information on RAID-Z2, check out Adam Leventhal's blog post over at Oracle .
Next we need to create a ZFS Volume, click on the "Create ZFS Volume" button from the Storage page.
I named this volume "ESXi" since we will be using it for an iSCSI LUN to be attached to ESXi in a later lesson. We'll
make the size 150GB by putting "150G" as the size. The rest of of the space will be used in later lessons. Click
"Add ZFS Volume" when you are done.
Note: ZFS is a file system with a lot of cool features that started in Solaris. Solaris, like the FreeBSD that FreeNAS is
based on, is a flavor of Unix. For more information on ZFS, check out the ZFS page at opensolaris.org .
Next we need to turn the iSCSI service on.
Click the "Services" button at the top of the page, then click the switch next to "iSCSI" to turn the service on.
Now lets configure iSCSI. We'll start by setting up Authentication, so we can have a little security for our Virtual
SAN.
Expand "ISCSI" click "Target Global Configuration" then click "Authentication", then click "Add iSCSI User"
I used "vsan" as my User, you can call it whatever you want, just remember what it is. Set and confirm a "Secret",
you can leave the bottom 3 fields blank, and click "OK".
Next we need to create a Portal.
Select "Portals", then click "Add Portal"
Here we can just accept the default and click OK. This means it will listen on port 3260 on all IPs for this portal.
Next we need to create a device extent.
Click "Device Extents" then "Add Extent"
Give the Extent a name, I named mine "ESXi", because we'll be assigning this LUN to ESXi in a later lesson. Select
"SAN1/ESXI (150G)" (or whatever you named your ZFS volume earlier) from the drop down for "Disk device" then
click "OK".
Now we'll setup the Target Global Configuration.
Click "Target Global Configuration", change the base name if desired (I just changed example.org to
fixtheexchange.com for mine), select "CHAP" from the drop down for the "Discovery Auth Method", and "1" as the
"Discovery Auth Group". Everything else can be kept as-is. Click "Save".
The last thing we need to do is add a target.
Click "Targets" then "Add Target".
Give your target a name, and an alias. Again, I used ESXi here because that is what this LUN will be used for later
on.
Select "Disk" from the drop down for "Type".
Select "1" from the drop down for "Portal Group ID".
Select "1" from the drop down for "Initiator Group ID".
Select "1" from the drop down for "Authentication Group number".
Click "OK".
The last thing we need to do is add the Extent to the Target.
Click "Associated Targets."
Click "Add Extent to Target".
Select the Target you created earlier in the "Target" drop down.
Select the Extent you created earlier in the "Extent" drop down.
Click "OK".
That's it! Your Virtual SAN has been configured. We now have an iSCSI LUN that we will use with ESXi in a later
lesson. In Part 3 of the "Budget Laboratory" series, we'll be installing VMware ESXi 4.1 inside of VMware Workstation
7.
Tags:
SAN
FreeNAS
FreeBSD
VMWare
‹ Budget Laboratory: Part 1 - Multi-WAN Load up Budget Laboratory: Part 3 - VMWare ESXi 4.1
Balancing with pfSense on VMWare Workstation on VMWare Workstation 7 ›
Log in or register to post comments
Comments 4
SUBMITTED BY JOSH ON WED, 09/07/2011 - 08:51
Article updated.
I added a few notes with more information to this article, so if you've already read it, it's
worth another read. I also fixed some of the screen shots that had mysteriously disappeared.
SUBMITTED BY MULTIPLEXOR (NOT VERIFIED) ON MON, 09/12/2011 - 16:23
fiber vs. fibre
You may have associated with the wrong spelling in your article. Try Fibre ;)
SUBMITTED BY JOSH ON MON, 09/12/2011 - 20:09
Both spellings are correct.
Both are correct. "Fiber" is the preferred spelling in American English. "Fibre" is more
commonly used in other English speaking countries.
SUBMITTED BY SARRATHBABU ON FRI, 02/24/2012 - 21:59
Hi Guys,
Hi Guys,
am useing in my laptop FreeNAS 8.0.3RELEASEp1. I have created one 20 GB volume and created 10 disk each
1GB capacity and able to access all the 10 disk through iSCSI protocal in my sun solaris10 servers.
My requirement is first 5 disk useing for sun1 server and another 5 disk useing for another sun2 server but
here able able to see all 10 disk in both the servers. how we can share required disk only for remote
solaris/linux servers.
Thanks in advance.
Regards
Sarathbbau
—
Thanks
Sarathbabu
User login
Username *
Password *
Create new account
Request new password
Log in
Series
Budget Laboratory
Budget Laboratory: Part 1 - Multi-WAN Load Balancing with pfSense on VMWare Workstation
Budget Laboratory: Part 2 - iSCSI Virtual SAN with FreeNAS 8
Budget Laboratory: Part 3 - VMWare ESXi 4.1 on VMWare Workstation 7
Budget Laboratory: Part 4 - Connecting VMWare ESXi 4.1 to an iSCSI SAN through vSphere
Budget Laboratory: Part 5 - Creating an OS Template VM in ESXi 4.1
Learn I.T.
Topics
Active Directory (2)
April Fools (2)
BlackBerry (0)
Citrix (1)
Exchange 2003 (1)
Exchange 2007 (6)
Exchange 2010 (18)
Exchange 2013 (15)
Exchange 2016 (2)
Firewall (2)
FreeBSD (3)
FreeNAS (4)
Ignite (1)
News (2)
PowerShell (6)
SAN (2)
Scripting (4)
Security (2)
Server 2003 (1)
Server 2008 R2 (1)
VMWare (10)
Windows 8 (7)
Windows Server 2012 (1)
Windows Server 8 Beta (3)
pfSense (2)
Tweets by
404 Not
Found
nginx/1.15.8
Disclaimer
As of 3/26/2012, I (Josh) am a Microsoft employee. This blog and the fixtheexchange.com domain name are my own personal property, this
is NOT an official Microsoft site, and is NOT affiliated with Microsoft or any of its subsidiaries or partners in any way. All posts on this site are
my own personal opinion(s) and do not reflect the opinion(s) of my employer(s) past or present. Comments are the personal opinion(s) of
those who leave them. Any advice, or use of scripts, found on this site should be done at your own risk. My employer (Microsoft) and I, are
NOT responsible for your use of any content linked to, or found on, this site.
Connect with us:

Budget Laboratory - Part 2 - IsCSI Virtual SAN With FreeNAS 8 - Fix The Exchange!

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Budget Laboratory - Part 2 - IsCSI Virtual SAN With FreeNAS 8 - Fix The Exchange!

Uploaded by

Copyright:

Available Formats

17/8/2021 Budget Laboratory: Part 2 - iSCSI Virtual SAN with FreeNAS 8 | Fix the Exchange!

The Wayback Machine - https://web.archive.org/web/20160906011150/http://www.fixtheexchange.com:80/Budge…

HOME BLOGS FORUMS ABOUT CONTACT

404 Not Found

Budget Laboratory: Part 2 - iSCSI Virtual SAN

You will need:

**I'm using the 64-bit version for this article.

Step 1: Create a Virtual Machine for your Virtual SAN

If you haven't already, open VMWare Workstation.

Select "Custom (advanced)" and click "Next".

Accept the defaults and click "Next".

Give your VM a name, then click "Next".

Accept the defaults for the CPU and click "Next".

Accept the defaults for RAM and click "Next".

Select "Create a new virtual disk", then click "Next".

Select "SCSI", then click "Next".

Accept the default and click "Next".

Select "Hard Disk" and click "Next".

Select "Create a new virtual disk" and click "Next".

Select "SCSI" and click "Next".

Accept the default and click "Next".

Click "OK" on the Virtual Machine Settings page.

Your Virtual Machine is now ready to power on.

Step 2: Install FreeNAS.

Power on the Virtual Machine.

Hit 1 to start the install.

Select the 8 GB drive as the destination, then hit "Enter".

Hit "Y" to continue.

The installation completes, hit "Enter" to continue.

Step 3: Configure FreeNAS through the web interface.

Next we need to turn the iSCSI service on.

Next we need to create a Portal.

Select "Portals", then click "Add Portal"

Next we need to create a device extent.

Click "Device Extents" then "Add Extent"

Now we'll setup the Target Global Configuration.

The last thing we need to do is add a target.

Click "Targets" then "Add Target".

Select "Disk" from the drop down for "Type".

The last thing we need to do is add the Extent to the Target.

Click "Associated Targets."

Click "Add Extent to Target".

Log in or register to post comments

SUBMITTED BY JOSH ON WED, 09/07/2011 - 08:51

Log in or register to post comments

SUBMITTED BY MULTIPLEXOR (NOT VERIFIED) ON MON, 09/12/2011 - 16:23

fiber vs. fibre

Log in or register to post comments

SUBMITTED BY JOSH ON MON, 09/12/2011 - 20:09

Both spellings are correct.

Log in or register to post comments

SUBMITTED BY SARRATHBABU ON FRI, 02/24/2012 - 21:59

Log in or register to post comments

Create new account

Request new password

Budget Laboratory: Part 2 - iSCSI Virtual SAN with FreeNAS 8

Budget Laboratory: Part 3 - VMWare ESXi 4.1 on VMWare Workstation 7

Budget Laboratory: Part 5 - Creating an OS Template VM in ESXi 4.1

Active Directory (2)

April Fools (2)

Exchange 2003 (1)

Exchange 2007 (6)