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