Notes from the Field–vSAN SBPM Tags and VR/SRM

VSAN_AcceptedSome of my favorite posts to write and put together are for the “Notes from the Field” titles/classifications. The reason being is these posts come from my experiences with clients to help solve a business requirement or design challenge that I am sure others have been or are faced with. This time around I am working with a customer on their Business Continuity/Disaster Recovery (BC/DR) initiative. Always a fun a topic!

High Level Architecture

The customer I have been working with is already down the path of HCI and specifically with vSAN ROBO edition for some of their remote locations. When they were looking for both a primary storage uplift at their production site as well as encompassing a disaster recovery strategy, looking to vSAN was an easy choice. For the replication or “data mover” task, vSphere Replication will be leveraged tied with Site Recovery Manager (SRM) for the orchestration engine.

[Read more…]

Deploying the NetApp Edge VSA Part II

Netapp_Logo

Welcome to part II of how to deploy the NetApp Edge VSA. In part I (located HERE) we covered the deployment of the OVA template and the configuration of the Data ONTAP software. In this post I am going to cover adding your VSA(s) to NetApp’s web interface management utility, NetApp OnCommand System Manager. From there we will add the licenses you should have received from NetApp to enable additional functionality. Finally we will end with setting up an iSCSI iniator group and configuring our first LUN.

As mentioned in the first post, I am working towards setting up VMware SRM in my lab and leveraging array replication for testing. These first two posts however will walk your through getting the VSA up in running in your lab for whatever testing you would like to do with NetApp Edge VSA. Part III of this series will cover the implementation of SnapMirror for LUN replication.

For this post the assumption has been made that NetApp OnCommand System Manager has been installed somewhere on your network per the instructions provided by NetApp when you downloaded the Edge VSA.

Procedure

Step 1 – Launch NetApp OnCommand System Manager, from the initial screen on the ‘Home’ tab click the ‘Add’ button:

Pic1

Step 2 – Enter the Host name or IP Address of the VSA system and click ‘Add’ (Make sure to add both VSA’s if you plan to use SnapMirror):

Pic2

Step 3 – Select the “Primary Site” VSA and click the ‘Login’ icon in the upper left corner:

Pic3

Step 4 – Enter the ‘root’ in the ‘User Name’ field and provide the ‘Password’. Click ‘Sign In’ when ready:

Pic4

Step 5 – Once logged it is time to add the software licenses to activate Deduplication, iSCSI, and NFS (also add the license for SnapMirror and Flexclone if working with SRM). In the left hand pane expand the ‘System Tool’ section and select ‘Licenses’:

NOTE – You should have received an email from NetApp containing these keys.

Pic5

Step 6 – In the upper left corner of the right pane click the ‘Add’ icon:

Pic6

Step 7 – Type in the license key for the function you wish to activate. Click ‘Add’ when ready. Complete this step for the remaining features you wish to activate:

Pic7

Step 8 – With the license keys entered, expand the ‘Protocols’ tree and select ‘iSCSI’:

Pic8

Step 9 – In the right pane click the ‘Start’ icon to start the iSCSI service:

Pic9

Step 10  – Now to create our first LUN. Expand the ‘Storage’ tree and select ‘LUNs’:

Pic10

Step 11 – In the right pane select the ‘Initiator Groups’ tab and click the ‘Create’ icon in the upper left. Using Initiator Groups will allow us to combine multiple ESX/ESXi hosts into a group and assign that group access to the LUN’s:

Pic11

Step 12 – The ‘Create Initiator Group’ dialog will be displayed. From the ‘General’ tab provide a name for the Initiator Group and be sure to select ‘VMware’ from the ‘Operating System’ drop down:

Pic12

Step 13 – Click the ‘Initiator’ tab and click the ‘Add’ button in the lower left. Add each of the IQN’s (iSCSI Qualified Name) for your ESX/ESXi hosts. Click ‘Create’ when finished:

Pic13

Step 14 – Click the ‘LUN Management’ tab and click ‘Create’ in the upper left. The ‘Create LUN Wizard’ will be launched:

Pic14

Step 15 (Pic15) – Click ‘Next’ on the ‘Welcome to Create LUN Wizard’ dialog:

Pic15

Step 16 – Provide a ‘Name’ an optional ‘Description for the LUN. Specify ‘VMware’ as the LUN ‘Type’ and choose a size and if wish to enable Thin Provisioning. Click ‘Next’ when ready:

Pic16

Step 17 – You can leave the defaults and click ‘Next’ or modify the ‘Volume Name’:

Pic17

Step 18 – Select the Initiator Group we created in Step 12 and click ‘Next’ (Optionally you can set the LUN ID):

Pic18

Step 19 – Verify the settings are correct on the ‘LUN Summary’ screen. Click ‘Next’ to continue:

Pic20

Step 20 – With the ‘Completing the Create LUN wizard’ displayed click ‘Finish’ to exit:

Pic21

And from the ‘LUN Management’ tab we can see our newly create LUN:

Pic22

**After configuring the VSA for the Primary Site repeat the above steps to configure the Secondary Site VSA.

With the LUN created and access provided to your ESX/ESXi hosts through vCenter scan and create a new Datastore from the presented NetApp Edge VSA LUN.

Next up is configuring SnapMirror replication so stay tuned!

-Jason

Deploying the NetApp Edge VSA Part I

Netapp_LogoOver the last few weeks I have been working and testing VMware Site Recovery Manager (SRM) in my home lab. In working with SRM my testing  recently has been limited to using host based replication, vSphere Replication that was introduced in SRM 5. I wanted to take the lab experience closer to something that you would see in a production environment (not that you wouldn’t see vSphere Replication in production) leveraging storage array replication and that is were the NetApp Edge VSA comes in. The NetApp VSA was introduce at VMworld 2012 and is free to anyone who is willing to signup for a NetApp account via their support website. The VM runs NetApp’s Data ONTAP software and provides features for SAN, NAS, Snapshots, and SnapMirror (replication) to mention a few as if you were working with a physical FAS array. In my SRM lab I have deployed two VSA’s, one at the “primary” site and the other at the “secondary” site. In this series of blog posts I am going to cover how I deployed the VSA’s, created a LUN, and configured SnapMirror replication. I will mention ahead of time that my experience with NetApp is limited and the steps I took were to get things working in my lab environment. If anyone see’s a potential issue or can provide additional input please leave a comment.

Once you have successfully registered for the VSA you will be able to download the OVA and OnCommand System Manager software. An email will be sent to the registered address containing the needed license keys. The resources needed to get started are listed below:

  • Register for NetApp VSA Download –> HERE
  • Data ONTAP Edge 8.1 OVA
  • OnCommand System Manager
  • NetApp Software License Keys
Lab Design
To make this work in my SRM lab I deployed two VSA’s each running on its own ESXi host. The name’s and IP’s as follows:
VSA1
  • Management Interface – vmnic0, e0a – 10.20.0.111
  • iSCSI Interface – vmnic1,e0b – 100.100.100.71
  • NFS Interface – vmnic2,eoc- 200.200.200.71
VSA2
  • Management Interface – vmnic0,e0a – 10.20.0.112
  • iSCSI Interface – vminc1,e0b – 100.100.100.72
  • NFS Interface – vmnic2,e0c – 200.200.200.72

With the administrative work done, time to deploy!

Deploying the VSA OVA

Step 1 – Browse to the download location of the VSA OVA file:

Pic1

Step 2 – Click “Next” on the details, take Note of the virtual machine hardware configuration:

  • 2 virtual CPU’s
  • 4GB RAM
  • 3 IDE Disks
  • 1 SCSI Disks
  • 4 virtual NICs

NOTE— When selecting a disk format, please select the thick provisioned (lazy zeroed) format.

Pic2

Step 3 – Accept the EULA:

Pic3

Step 4 – Name the VSA and select an inventory location:

Pic4

Step 5 – Select a host or cluster to deploy the VSA on:

Pic5

Step 6 – Select a resource pool as needed:

Pic6

Step 7 – Select a Datastore to deploy the VSA on:

Pic7

Step 8 – Select the VMDK disk format, as mentioned in Step 1 I will be using the Thick Provisioned Lazy Zeroed format:

Pic8

Step 9 – Select the virtual network:

Note – The VSA will be deployed with four virtual NICs. I placed this first interface on my “Management” network and leveraged the other interfaces for iSCSI and NFS traffic

Pic9

Step 10 – Provide the following configuration information for the VSA:

  • Host Name
  • IP Address
  • Netmask
  • Gateway
  • Administrative Password
  • Disk Size (Note – You will need to scroll the window down to see this option)

Pic10

Step 11 – Confirm the information is correct and click Finish to being the deployment

Pic11

Pic12

Pic13

***Optional***

Step 12 – After deploying the VSA do not power it on just yet. The VSA is configured with 4 vNics and to resemble a sort of production network I chose to use the 1st interface for management, interface 2 for my iSCSI traffic, and interface 3 for NFS exports. On interface 4 I cleared the check box for “Connect at Power On” as I did not plan on using it:

Pic14

Step 13 – From within your vCenter inventory power on the VSA:

Pic15

step 14 – For the advanced configuration fire up your SSH client of choice (I am using Putty) and connect to the DNS/IP address of the VSA. Login with the ‘root’ user account and the password you specified during the OVF deployment

Pic16

Step 15 – To configure the VSA type ‘setup’ and press ‘Enter’. Instead of screen grabbing every setting, below are the configuration options that are presented and the values I used:

Are you sure you want to continue? [yes] <Press Enter>
Please enter the new hostname [VSA1]: <Press Enter>
Do yu want to enable IPv6: [n]: <Press Enter>
Do you want to configure interface groups? [n]: <Press Enter>
Please enter the IP address for Network Interface e0a [10.20.0.111]: <Press Enter>
Please enter the netmask for Network Interface e0a [255.255.255.0]: <Press Enter>
Please enter media type for e0a {100tx-fd, tp-fd, 100tx, tp, auto (10/100/1000)} [auto]: <Press Enter>
Please enter flow control for e0a {none, receive, send, full} [full]: <Press Enter>
Do you want e0a to support jumbo frames? [n]: <Press Enter>
Please enter the IP address for Network Interface e0b []:<YOUR iSCSI NETWORK IP HERE>
Please enter the netmask for Network Interface e0b [255.0.0.0]:<YOUR iSCSI NETMASK HERE>
Please enter media type for e0b {100tx-fd, tp-fd, 100tx, tp, auto (10/100/1000)} [auto] <Press Enter>
Please enter flow control for e0b {none, receive, send, full} [full]: <Press Enter>
Do you want e0b to support jumbo frames? [n] <Press Enter>
Please enter the IP address for Network Interface e0c []: <YOUR NFS NETWORK IP HERE>
Please enter the netmask for Network Interface e0c [255.0.0.0]: <YOUR NFS NETMASK HERE>
Please enter media type for e0c {100tx-fd, tp-fd, 100tx, tp, auto (10/100/1000)} [auto]: <Press Enter>
Please enter flow control for e0c {none, receive, send, full} [full]: <Press Enter>
Do you want e0c to support jumbo frames? [n]: <Press Enter>
Please enter the IP address for Network Interface e0d []: <Press Enter>
Would you like to continue setup through the web interface? [n]: <Press Enter>
Please enter the name or IP address of the IPv4 default gateway [10.20.0.1]: <YOUR GATEWAY>
Please enter the name or IP address of the administration host: <Press Enter>
Please enter timezone [GMT]: <I am in Pacific time zone, so I entered ‘US/Pacific>
Where is the filer located? []: <ENTER YOUR LOCATION>
Enter the root directory for HTTP files [/vol/vol0/home/http]: <Press Enter>
Do you want to run DNS resolver? [n]: YES
Please enter DNS domain name []:<YOUR DOMAIN HERE>
Please enter the IP address for first nameserver []: <YOUR DNS SERVER HERE>
Do you want another nameserver? [n]: YES <If you have a second DNS server, NO if not>
Please enter the IP address for alternate nameserver []: <YOUR DNS SERVER HERE>
Do you want another nameserver? [n]: <YES or NO Depending on your environment>
Do you want to run NIS client? [n]: <Press Enter>
Message about NetApp Support: <Press Enter>
Do you want to configure the Shelf Alternate Control Path Management interface for SAS shelves [n]: <Press Enter>

Once completed type ‘Reboot’ at the prompt and press ‘Enter’ to continue.

Remember to deploy your second VSA!

After the VSA’s have been rebooted the configuration of the units will continue via NetApp’s OnCommand System Manager interface, stay tuned!

-Jason