Lab Overview: NetApp Introduction Lab for Data … LAB ON DEMAND (LOD) Lab Overview: NetApp Introduction Lab for Data ONTAP 8.2 7-Mode June 2015 | SL10230 Lab Overview v1.1 2 Lab Overview:

NETAPP LAB ON DEMAND (LOD)

Lab Overview: NetApp Introduction Lab for Data ONTAP 8.2 7-Mode June 2015 | SL10230 Lab Overview v1.1

Lab Overview: Intro Lab for Data ONTAP 8.2 7-Mode v1.1 2

INTRODUCTION

This document provides basic information required to use the Introduction Lab for Data ONTAP 8.2 7-Mode lab in Lab on Demand. Unlike most Lab on Demand labs, there is no formal lab guide for this lab, and there are no plans to create such a guide since 7-Mode support is no longer present in Data ONTAP 8.3 and later versions. Instead, this document provides a brief overview of the lab’s components and credentials, details of an in-lab script you can run to automatically configure some lab components, and a suggestions of how to demo a few select 7-Mode features.

Since there is no formal lab guide for this lab, the lab user must have suff icient Data ONTAP 7-Mode knowledge to independently configure and operate the lab's components.

Figure 1) NetApp Introduction Lab environment layout.

All of the servers and storage controllers presented in this lab are virtual devices, and the networks that interconnect them are exclusive to just your lab session. The virtual storage controllers (vsims) offer nearly all the same functionality as do physical storage controllers, but at a reduced performance profile.

Lab Overview Document: NetApp Introduction Lab for Data ONTAP 8.2 7-Mode v1.0 3

SOFTWARE COMPONENTS

The lab includes the following software components.

Data ONTAP 8.2.3P3

Windows 2012R2

Windows 2008R2

Red Hat Enterprise Linux 6.5

NetApp OnCommand System Manager 3.1.2

NetApp Windows Unified Host Utilities 7.0

NetApp ONTAP DSM for Windows MPIO 4.1P1

NetApp Linux Unified Host Utilities 7.0

The Host Utility kits, System Manager, and DSM for Windows MPIO are all pre-installed.

SnapDrive for Windows 7.1.1 and SnapDrive for UNIX 5.2.2 are available in the lab but not installed. All prerequisites are pre-installed, and the SnapDrive installation packages can be found under C:\LOD\software on JUMPHOST and under /root/LOD on rhel1 and rhel2.

SCRIPTING TOOLS

For users interested in scripting, the following scripting tools are available in this lab.

ActivePerl 5.16.3 (x64)

ActiveTcl 8.6.1

PowerShell 3.0

Windows PowerShell Integrated Scripting Environment (ISE)

NetApp Manageability SDK 5.3

Data ONTAP PowerShell Toolkit v3.2.1

To utilize the Data ONTAP PowerShell Toolkit, launch PowerShell (32 or 64 bit) on JUMPHOST

and issue the following commands:

Import-Module DataONTAP

Show-NaHelp

The NetApp Manageability 5.3 SDK is installed on JUMPHOST under C:\netapp-manageability-

sdk-5.3.The SDK documentation is included as a part of the SDK.


LAB SYSTEMS SUMMARY

The following table lists the various hosts available in the lab along with their access credentials.

Hostname IP Address(es) Username Password

JUMPHOST 192.168.0.5 Demo\Administrator Netapp1!

rhel1 192.168.0.61 root Netapp1!

rhel2 192.168.0.62 root Netapp1!

WIN2K8R2 192.168.0.31 Demo\Administrator Netapp1!

DC1 192.168.0.253 Demo\Administrator Netapp1!

fas01 192.168.0.101 root Netapp1!

fas02 192.168.0.151 root Netapp1!

KEY FEATURES TO DEMONSTRATE

This is a sandbox lab, meaning that it is purposely minimally configured lab so you can customize it to meet your own specific needs. However, if you take advantage of the provided in-lab automation, then the resulting lab instance will be configured in a manner to facilitate demonstrating the following NetApp features:

CIFS and NFS file shares

iSCSI LUNs

qtrees

Deduplication

Basic SnapMirror and SnapVault

High Availability (HA) failover


LAB AUTOMATION/SETUP

Lab users can optionally run the Lab_Prep.bat script found in the scripts folder on the desktop of JUMPHOST to create the volumes, CIFS shares, and NFS exports shown in the following table.

Note that the NFS Mount Points listed below are preconfigured in autofs on the systems named rhel1 and rhel2 so that once the script finishes you can automatically access those directories from those Linux hosts.

The Lab_Prep.bat script also creates SnapMirror and SnapVault relationships between fas01 and fas02 for these volumes, as listed in the SnapMirror/SnapVault Relationship Source column, and initiates the baseline transfers

Controller Volume CIFS Share NFS Mount Point 1

SnapMirror/ SnapVault Relationship Source

fas01 /vol/vol1 \\fas01\vol1 /net/fas01/vol/vol1

fas01 /vol/vol2 \\fas01\vol2 /net/fas01/vol/vol2

fas02 /vol/snapmirror_vol1 \\fas02\snapmirror_vol1 /net/fas02/vol/snapmirror_vol1 fas01:/vol/vol1

fas02 /vol/snapvault_vol1 \\fas02\snapvault_vol1 /net/fas02//vol/snapvault_vol1 fas01:/vol/vol1

To prepare for the demo, login to JUMPHOST and launch the Lab_Prep.bat batch file found in the scripts folder on the desktop. The script will take 3-4 minutes to run, and performs the following actions:

Creates the NetApp volumes on fas01 and fas02. Pre-populates sample data to the vol1 and vol2 volumes on fas01. Note that the sample

data is the same for both volumes. Deduplicates vol1 on fas01. Note that vol2 does not get deduped by the script so that

you can easily show a “before” and “after” comparison, and to also give you the opportunity to demonstrate an actual dedup operation in front of the customer.

Establishes SnapMirror and SnapVault relationships between fas01 vol1 and fas02 snapmirror_vol1 and snapvault_vol1.

1 On the hosts rhel1 & rhel2 these mountpoints are pre-configured in autofs, so you can just cd to the

directories without any manually mounting the NFS volumes yourself. Note that due to the way autofs works these mounts points may only become visible in the directory structure after you cd or ls the specified path.


Once you've run this script you can easily demonstrate a live deduplication operation by using the following procedure.

1. Mount the \\fas01\vol1 and \\fas01\vol2 shares on JUMPHOST and examine the contents; note that both volumes contain exactly the same files. Vol1 was deduped by the Lab_Prep.bat script, but vol2 was not.

2. Use ssh to log into fas01 and run the following command to display the space saved on both vol1 and vol2 through deduplication, remembering that vol1 has already be deduplicated while vol2 has not. fas01> df -s

3. Configure deduplication on the volume vol2. fas01> sis on /vol/vol2

4. Start the deduplication operation of vol2, which will process all existing data on the volume. fas01> sis start –s /vol/vol2

5. Show the progress of the running deduplication operation. Note that since vol2 only contains a small set of files, the deduplication operations will complete quickly, so you'll need to move fast if you want to catch it in operation.

fas01> sis status

High Availability

Version 1.1 of the lab now includes High Availability (HA) for the storage controllers, meaning that you can perform HA takeover and giveback operations on fas01 and fas02.

When the lab starts, controller failover may be disabled as the simulator is unable to preserve that setting during lab provisioning. If you run the Lab_Prep.bat script then that script will enable cluster failover for you, otherwise you will need to manually check the failover status and enable it yourself. Use the following command to check the failover status:

fas01> cf status

If failover is disabled then the preceding command will report "Controller failover disabled". In that case you can enabled failover by using the command:

fas01> cf enable

Once failover is enabled, you can initiate an HA takeover of fas02 by fas01 by issuing the command:

fas01> cf takeover

The takeover process will take a couple of minutes, during which progress messages will intemittently output to the terminal window, and during which fas02 will go through a reboot cycle and then wait during bootup for giveback. After that you can initate a giveback operation. fas01 (takeover)> cf giveback


KNOWN ISSUES

If you have a PuTTY session open to either fas01 or fas02 at the time you run the Lab_Prep.bat script then the script will fail. The workaround is to close that PuTTY session before you run the script. The script can only be run once in a given lab session so if you experience a script failure the most expedient course of action is to book a new copy of the lab.

Documents

Lab Overview: NetApp Introduction Lab for Data … LAB ON DEMAND (LOD) Lab Overview: NetApp Introduction Lab for Data ONTAP 8.2 7-Mode June 2015 | SL10230 Lab Overview v1.1 2 Lab Overview: