ONTAP Simulator: Getting Started Quick - NetApp · ONTAP Simulator: Getting Started Quick A guide...

ONTAP Simulator:Getting Started QuickA guide to the minimum steps to get a NetApp ONTAP 9 simulator running on a typical Windows or macOS system.

Version 1.0

© 2016 NetApp, Inc. All rights reserved. --- NETAPP CONFIDENTIAL ---1

§ Overview of the ONTAP Simulator§ Download and Install VMware Player§ Download and Install ONTAP Simulator§ ONTAP First Boot and Cluster Setup § Immediate First Steps for your Cluster§ Polishing Steps for your Cluster§ Additional Resources and Issues§ macOS Installation, Setup and Hints

Table of contentsONTAP Simulator: Getting Started Quick


Overview of the ONTAP Simulator


§ Has been available and in use for over a decade, since at least ONTAP 6

§ Previously required a Linux host and a lot of CLI setup, skills, and paid-for virtualization products (like: VMware Workstation, Parallels, Fusion, etc)

§ As of ONTAP 8.0 it is a much simpler package (.ova) which can be quickly opened and booted on many types of systems and VM Player is free

§ What is it? § When you download a version of the simulator, boot it and run it, you are not running code that is

“similar and simulated” ONTAP, “it is” in fact that version of ONTAP (features, bugs and all)§ The difference is that on the underneath side of the simulator, instead of having the low-level drivers

for hardware items like NVRAM, flash-card, SAS adapters, shelves and disks, those things are substituted with drivers for local disk files on your system.

ONTAP Simulator: History and What is it? Available to customers, partners and NetApp personnel


ONTAP Simulator: Software DiagramSoftware running on your system


…

e0a e0b e0c e0dex: 192.168.x.10

28 1GB disks; Initially with: 14 owned by Node-01 with a 3-disk aggr0 aggregate

Cluster InterconnectVMnet8network

VM Player or Fusion

Your Windows or macOS system

Optional

DNS Server

192.168.x.2

VMnet8 Adapter192.168.x.1

ssh, cli, putty System Manager PowerShellWith ToolkitMount an

NFS Export

Map aiSCSI LUN

Map aCIFS Share

ONTAP Simulator

§ Good at:§ New system setup – not hardware specific things like SP setup or ADP, but just like a real system it

needs network, aggregate, SVM, protocol and miscellaneous setup § Ongoing management – Creating and modifying Aggregates, Storage Virtual Machines,

Volumes, Policies, Snapshots, Qtrees, Quotas, Exports, Shares, LUNs, QoS, events, statistics, networking, security, and SnapMirror/Vault

§ Not so good at:§ Things to do with: service-processor, installation, failover, doing upgrades, MetroCluster

ONTAP Simulator: Good and bad use casesThings the simulator will be good at … and not so good


§ To keep this process relevant, simple, repeatable, and to work on the broadest range of hardware (laptops w/8GB of memory) we are focusing on:§ Clustered Data ONTAP§ ONTAP Version 9§ Single Node cluster

§ However, all of the following are available and possible:§ 7-Mode mode Data ONTAP going back to 7.3 and up through 8.2§ 2-node Clusters (8.2 and 8.3 are still available for download) § Notes:

§ Two node clusters require twice the memory footprint, as such, it’s probably more valuable from a learning and experimentation perspective to create two single-node clusters if you have the memory

§ Going back to 7.3 means running the 7.3 simulator on a Linux system (Linux on VM Player for example)

ONTAP Simulator: Disclaimers for this ‘Getting Started Quick’ GuideSimulator is available in many flavors and configurations


§ Hardware:§ 64-bit x86 CPU with 1.3GHz§ Two processor cores § 8GB Memory § Free Disk Space (for one simulator)

§ ~10 GB to get started § Up to ~30 GB after months of normal use

§ Virtualization Technology CPU Feature

§ Access to the Internet:§ VMware – to download VM Player§ NetApp – to download ONTAP

Laptop or System RequirementsAssumption is this matches many of the configurations out there


§ If valuable, and you have the disk space, you could have a number ONTAP simulator VMs (9.0, 8.3.2, etc) under the control of VM Player but run them one at a time. Since someday, you may run a system with more memory, think of each VM as an instance of ONTAP that may run at the same time … so use unique names and IP addresses for each instance

§ While you may start out with a single-node cluster, allocate IP addresses with the idea you may upgrade it to a two node at somepoint in the future. Reserve addresses for the second node even if you won’t use them right now

§ In cDOT you always have management sorts of LIFs (cluster, node, intercluster) and data LIFs owned by SVMs. You have 254 addresses to play with in your VM Player subnet so allocate ranges in an easy to remember fashion. For example, a scheme might be something like below. (where ‘x’ is your VM Player or Fusion generated subnet 3rd octet number):

ONTAP Simulator: Network address planningConsider each simulator instance something you may copy, restore later or even share


§ First Cluster (10s, 20s)§ Mgmt LIF addrs: 192.168.x.10 -> 19

§ Cluster mgmt: 192.168.x.10§ Node1 mgmt: 192.168.x.11

§ Node1 intercluster: 192.168.x.12§ Node2 mgmt: 192.168.x.13

§ Node2 intercluster: 192.168.168.x.14§ Data LIF addrs: 192168.x.20 -> 29

§ Second Cluster (30s, 40s)§ Mgmt LIF addrs: 192.168.x.30 -> 39


§ Node1 intercluster: 192.168.x.32§ Node2 mgmt: 192.168.x.33

§ Node2 intercluster: 192.168.168.x.34§ Data LIF addrs: 192.168.x.40 -> 49

§ Third Cluster (50s, 60s)§ Mgmt LIF addrs: 192.168.x.50 -> 59


§ Node1 Intercluster: 192.168.x.52§ Node2 mgmt: 192.168.x.53

§ Node2 Intercluster: 192.168.168.x.54§ Data LIF addrs: 192.168.x.60 -> 69

Download and Install VMware Player


Also known as: VMware Workstation Player, Workstation Player, VM Player or VMplayer

DownloadVM Player from VMware.comGo to Login -> My VMware -> and Register if you do not already have an account


1

2

Download VM Player from VMware.com (continued)Find All Downloads -> look for VMware Workstation Player -> then View Download Components


1

2

Download VM Player from VMware.com (continued)On the VMware Workstation Player page -> select Download for Windows 64-bit -> then Save, then Run


1

2

3

Install the VMware Workstation VM PlayerAllow the installer to make changes to your device; follow the Setup Wizard instructions by hitting [Next]


1

2

Install the VMware Workstation VM Player (continued)Setup Wizard questions are fairly straight forward. Likely to require a reboot at the end


Notes on Setup Wizard options:

• It will ask if you have a license, ignore that for now. Later you’ll just register your email address

• Screen shots show options selected. I suggest the Enhanced Keyboard Drive but not certain it’s required.

• It will ask you to click [Yes] to restart at the end

VM Player Final Steps: Determine the subnet it generatedVM Player creates a virtual subnet within your system which ONTAP will use. Use ipconfig to look that up


1Once VM Player is installed it creates two virtual adapters on your system called VMnet1 and VMnet8. VM Player generates random IP subnets for these adapters. We will be using the VMnet8 subnet.

Open a CMD or PowerShell window and type ipconfig. Look through the adapters and find the VMnet8 adapter.

Write down to record that subnet as it will become the subnet your cluster lives in. In this example it has generated and is using the 192.168.23.0 subnet with a class-c mask (255.255.255.0).

The address 192.168.23.1 is your laptop’s IP address into that subnet. Later, we will be placing ONTAP cluster and node management LIFs into that same subnet.

23

NOTE: Be aware this guide mixes examples of the VMnet8 on different subnets (192.168.23.0 above, 17.0 later on, etc)

§ This could have been the FIRST step but leaving until here since it may already be on

§ This feature goes by several names: Intel VT-x, Virtualization Technology (VTx), amd-v

§ It may already be enabled on your system. It appears Windows 8.x and 10 already require and have VT-x enabled so enabling this may only be an issue for Windows 7 users.

§ Make sure it is Enabled, Save Settings and continue booting up

§ OR … if you think it’s enabled, just go ahead and install VM Player and ONTAP Simulator and keep an eye out for any VT-x related errors when attempting to start the ONTAP VM

§ The following slide shows some example BIOS screenshots showing the setting. It seems to be found under Security, Power, or Advanced menus depending on manufacturer

§ VMware has this KB article with more details: http://kb.vmware.com/kb/1003944

VM Player Final Steps: Enabling Virtualization Technology VT-x must be enabled before VM Player and Simulator can operate properly


VM Player Final Steps: Enabling Virtualization Technology (continued) VT-x Must be enabled before VM Player can operate properly – some example BIOS screenshots


Download and InstallONTAP Simulator


Downloading ONTAP 9 Simulator to your SystemGo to NetApp Support Site, login using Customer, NetApp, or Partner Credentials


Downloading ONTAP 9 Simulator to your SystemUse Downloads dropdown -> Product Evaluation -> Data ONTAP Simulator


1

2

Downloading ONTAP 9 Simulator to your SystemOn the Simulate ONTAP page -> select Simulator 8.x and 9.x – next page Accept T&C and click Continue


1

23

Downloading ONTAP 9 Simulator to your SystemDownload the 4 files identified for ONTAP 9.0 to a folder on your system (Downloads, or maybe a folder within)


Downloading ONTAP 9 Simulator to your SystemNow you should have those four files on your system somewhere


Launch VM Player and select Open a Virtual MachineBrowse to where you downloaded the ova file and select and open it


12

3

You will be asked to give it a name and store it somewhereGive it a name meaningful to you and situation. \Documents\Virtual Machines is a good default, click [Import]


1

23

NOTE: This name will become the name of the Virtual Machine (VM) to VM Player. It can be different than the actual ONTAP cluster or node name but it might help to keep them the same. So adding -01 to your planned cluster name would indicate this is the first, and maybe only, node in the ONTAP cluster.

Your ONTAP node is ready to Powered On (aka: Play)You can Play or Edit the virtual machine, click Edit virtual machine settings just to look at some things


Don’t change anything for now!

Just click [Cancel]

ONTAP First Boot and Cluster Setup


Click Play and you’ll begin to see ONTAP BootingThis is similar to powering on a FAS controller for the first time


NOTES: You are likely to see two things occur on this first boot:

• A window may appear asking you to download and install VMware Tools … ignore it by clicking [Remind me later]

• Remember: always say no or decline if and when VM Player suggests downloading or installing VMware Tools

• Secondly, you may also notice the traditional boot up count down (9,8,7,6,…) giving you 10 seconds to hit a key to get the loader prompt.

• It may get to 1, then seem to hang and not boot. This is a quirk and it will eventually continue.

• However, you can click into the console window and hit [Enter] to speed it up, or wait a bit longer

Another important aspect of VM Player to UnderstandHow to direct your cursor, or user input control, between the VM console and your greater Windows system


NOTE: In the early stages, this can be confusing. If you’ve clicked into the console window and you’d like to do something else (like google something or look at local files) you need to press Ctrl+Alt to free your user input focus from the VM console.

If your cursor seems to be missing, it is probably just assigned into the console window. Just press Ctrl+Alt at the same time and then wiggle your mouse. It will be back to your Windows system.

But be prepared to click back into the VM console because soon you will need to press Ctrl-C to get the ONTAP Boot Menu to zero disks.

Click into the VM console window and be ready to type Ctrl-CPress it a few times to be sure and look for the “Boot Menu will be available” message


NOTE-1: At this point, the simulator is like a regular ONTAP 9 system shipped from the factory except it’s disks were not zeroed. So we do that as the first step. It will warn you and ask if you are sure. Answer yes to both questions. Expect about 5-10 minutes to zero. If your laptop uses a flash drive, faster yet.

NOTE-2: If you miss the chance to enter Ctrl-C at the right time, let it go and it will reboot once, maybe twice. Once you get it, choose option 4

NOTE-3: If you get the lower yellow 3-choice menu about VMware Tools as seen here, click [Never Remind Me] … because you DO NOT want to install VMware Tools on your ONTAP simulator

NOTE: Pick up here

For those following the macOS instructions at the end of this slide deck, this is where you should pick up and continue with the rest of the ONTAP Simulator Setup.

As usual, you’ll be asked if you are sure (twice)System reboots with “Wipe filer procedure requested” and expect series of dots indicating disk zeroing progress


After disk zeroing completes, you’ll reboot into Cluster SetupThis is where things begin to look and act exactly like an actual install and setup. Suggested answers follow.


Some suggested Cluster Setup answersFor your first cluster, we’re recommending a single-node cluster


§ Create new or join an existing cluster? create

§ Do you intend … single node cluster? yes

§ Cluster administrator’s password? netapp123 (or your favorite secret password)

§ Enter the cluster name? hq-stor (or whatever you choose to name your cluster)

§ Enter the cluster base license key: SMKQROWJNQYQSDAAAAAAAAAAAAAA

§ Additional license key []? [Enter] we’ll do that later From the file: Cmode_license_9.0.txtCluster Base License (Serial Number 1-80-000008)================================================

You use the cluster base license when setting up the first simulator in a cluster. (NOTE: spaces every 3-characters added for readabilty)

Cluster Base license = SMK QRO WJN QYQ SDA AAA AAA AAA AAA A

NOTES:

• It is tricky to cut and paste from Windows into the VM Player console. As such, the cluster base license key is shown to the right in 3-char chunks to made it easier to read and enter. You can enter it in lower case if helpful.

Some suggested Cluster Setup answers (continued)This is where the VM Player subnet assigned for the VMnet8 adapter comes into play (replace 23 with your #)


§ Enter the cluster management interface port [e0a]: e0c (could be a,b, or d, but c is more typical)§ Enter the cluster management interface IP address: 192.168.23.10§ Enter the cluster management interface netmask: 255.255.255.0§ Enter the cluster management interface default gateway: 192.168.23.2

§ Enter the DNS domain names: acme.com§ Enter the name server IP addresses: 192.168.23.1

§ Where is is the controller located: In my laptop

§ Enter the node management interface port []: e0c (use same as cluster_mgmt)§ Enter the node management interface interface IP address: 192.168.23.11§ Enter the node management interface netmask: 255.255.255.0§ Enter the node management interface default gateway: 192.168.23.2

§ Enter the system config backup destination … (press enter to skip): [Enter]§ Pause message for autosupport information is displayed: [Enter]

Your cluster is created and ready for accessYou can access it via the VM Player console, ssh, or System Manager (and eventually NFS, CIFS, iSCSI)


NOTE-1: You probably want to avoid using the VM Player console for routine access and experimenting for a number of reasons:

- You can’t resize it in any useful way- There are no scroll bars and no way to look at previous output- The continual hassle of having to type Ctrl-Atl to get out of it

NOTE-2: Come back to the VM Player console if you have networking problems and cannot access the cluster for some reason. Using the console is equivalent of being connected to the node’s serial port.

Using Putty and/or System ManagerUsing the Cluster Management IP Address, connect via ssh or https (Chrome may work when IE, Edge won’t)


Immediate First Steps for your Cluster


Steps you should do now before proceeding and before you forget

Immediate First Steps for your ClusterThese items are best practices for keeping a simulator in good health and easy to access


§ Perform networking tests to confirm connectivity

§ Expand your root aggregate and root volume

§ Put your cluster addresses in your host’s /etc/hosts file

§ Enter licenses for the simulator

§ Miscellaneous useful setup

§ Learn to suspend and resume your cluster

Perform networking tests to confirm your cluster accessYour host Windows system should be able to ping your cluster’s cluster and node mgmt addresses


Common Problems

1. LIF has migrated away from e0c to e0a which, by default, is meant for cluster interconnect:Solution: net int revert *

2. The subnet in use by VM Player is not what you think it is:Solution: compare ’net int show’ and ‘ipconfig’ for VMnet8

3. VM Player needs Network Adpater 3 and 4 (aka: e0c, e0d) set to Custom -> Specific Virtual network -> VMnet8 (NAT)Solution: see next slide

NOTE: Be aware this guide mixes examples of the VMnet8 on different subnets (192.168.80.0 here, 23.0 and 17.0 earlier, etc)

Perform networking tests (Possible solution for #3 on prior slide)Your host Windows system should be able to ping your cluster’s cluster and node mgmt addresses


1

Forcing VMnet8 virtual network

• Use VM Player’s dropdown, select Manage -> Virtual Machine Settings

• Click on adapter 3 (then 4) and select (o) Custom: Specific virtual network

• Scroll through the list and select VMnet8 (NAT)

• Until both 3 and 4 look as shown

• Click [OK] and then go back and re-run your ping tests

• If still problems, check for the problem #1 and #2 solutions on prior slides)

2

Expand your root aggregate and root volumeIt starts at 3 disks, add 2 more to make a total of 5 disks (this is a simulator specific recommendation)


1

2

Expand your root aggregate and root volume (continued)Now expand your root volume (vol0) to take advantages of the new space


1

Expand your root aggregate and root volume (continued)In addition, turn off vol0 snapshots except one nightly (a recommendation)


1

2

Put your cluster in your local system’s hosts fileThis will let you refer to it by name(s) rather than IP addresses


For Windows 10 (Win7 similar)

• Press the Windows key

• Type Notepad in the search field

• In the search results, right-click Notepad and select Run as administrator !!!

• From Notepad, open the following file: c:\Windows\System32\Drivers\etc\hosts

• NOTE: To see the hosts file above you will need to set the file browser dialogue box to look at All Files (*.*) not just Text Documents (*.txt) files

• Make the necessary changes to the file (see next slide)

• Click File > Save to save your changes.1

2Right-Click Notepad

and select Run as Administrator

3

Put your cluster in your local system’s hosts file (continued)This will let you refer to it by name(s) rather than IP addresses


What should you add?

• Cluster Mgmt address

• Node mgmt address

• While we’re here, add some SVM or Vserveraddresses, even though we haven’t created them in ONTAP yet.

• After you close and save, open a cmd or PowerShell window and confirm you can now ping the cluster and node by these names

Enter licenses into your simulatorCopy and paste the below text into a terminal emulator session (ie; putty) at the ::> prompt


license add YVUCRRRRYVHXCFABGAAAAAAAAAAA # CIFSlicense add WKQGSRRRYVHXCFABGAAAAAAAAAAA # FCPlicense add SOHOURRRYVHXCFABGAAAAAAAAAAA # FlexClonelicense add YBSOYRRRYVHXCFABGAAAAAAAAAAA # Insight_Balancelicense add KQSRRRRRYVHXCFABGAAAAAAAAAAA # iSCSIlicense add MBXNQRRRYVHXCFABGAAAAAAAAAAA # NFSlicense add QDDSVRRRYVHXCFABGAAAAAAAAAAA # SnapLocklicense add MHUZXRRRYVHXCFABGAAAAAAAAAAA # SnapLock_Enterpriselicense add CYAHWRRRYVHXCFABGAAAAAAAAAAA # SnapManagerlicense add GUJZTRRRYVHXCFABGAAAAAAAAAAA # SnapMirrorlicense add OSYVWRRRYVHXCFABGAAAAAAAAAAA # SnapProtectlicense add UZLKTRRRYVHXCFABGAAAAAAAAAAA # SnapRestorelicense add EJFDVRRRYVHXCFABGAAAAAAAAAAA # SnapVault

NOTES:

• These are the actual simulator licenses for the VM Player flavor of the ONTAP 9 (GA) simulator

• If you are in the future and installing a future version of ONTAP, be sure to check and use the licenses that come with that simulator as they may change.

Enter licenses into your simulator (continued)Or copy and paste the below text into the System Manager Add Licenses window


YVUCRRRRYVHXCFABGAAAAAAAAAAA,WKQGSRRRYVHXCFABGAAAAAAAAAAA,SOHOURRRYVHXCFABGAAAAAAAAAAA,YBSOYRRRYVHXCFABGAAAAAAAAAAA,KQSRRRRRYVHXCFABGAAAAAAAAAAA,MBXNQRRRYVHXCFABGAAAAAAAAAAA,QDDSVRRRYVHXCFABGAAAAAAAAAAA,MHUZXRRRYVHXCFABGAAAAAAAAAAA,CYAHWRRRYVHXCFABGAAAAAAAAAAA,GUJZTRRRYVHXCFABGAAAAAAAAAAA,OSYVWRRRYVHXCFABGAAAAAAAAAAA,UZLKTRRRYVHXCFABGAAAAAAAAAAA,EJFDVRRRYVHXCFABGAAAAAAAAAAA

NOTES:

• These are the actual simulator licenses for the VM Player flavor of the ONTAP 9 (GA) simulator which you can cut/paste into System Manager

• If you are in the future and installing a future version, be sure to check and use the licenses that come with that simulator. They may change

Enter licenses into your simulator (continued)System Manager in ONTAP 9 has a top-level Quick Link for entering licenses


1

2

Miscellaneous setup stepsCLI Timeout, Timezone, and Date-time


NOTES:

• Setting the timeout to zero disables the automatic logout of ssh cli session which can be annoying

• Set the timezone to your local timezone to avoid confusion

• Set the date and time.

• As you continue to use your simulator, keep an occasional eye on the date and time.

• If you suspend and resume the simulator you may find it is behind and you’ll need to set the date and time again.

• You can tell ONTAP to access an external NTP server which may or may no work well for you.

These Cluster Shell commands:::> timeout modify –timeout 0

::> timezone US/Central

::> date 201611101044

This eliminates some alerts that might be reported

::> set advanced::> net options switchless-cluster modify –enabled true::> set admin

Learn to suspend and resume your ClusterSuspend Guest is preferred to Shut Down Guest, Resume and Power On are the same thing


NOTES:

• When you want to put the simulator away completely use the Suspend Guest option and then close the VM Player application

• If you just close the VM Player app it will ask if your want to Suspend or shutdown. Suspend is the default so just hit enter and the simulator suspends and VM Player exists

• The next time you launch VM Player, highlight your simulater and click Play (which for a suspended VM performs a quick resume)

• Check ONTAP’s date/time after a suspend/resume operation

Polishing Steps for your Cluster


Steps you can perform now or later to finish polishing your simulator environment

Create data aggregatesPlanning thoughts and ideas


§ Keep one spare drive (even though I’ve never seen a simulator drive fail in 10 years)

§ Unless you’ve decided to go the 2-node cluster route (not covered in these slides), do a disk assign –all to bring the 14 unassigned drives into your <node>-01 configuration for a total of 28 drives. This leaves 27 drives (minus the 1 spare)

§ Assuming you’ve grown your aggr0 to 5-drives (recommended, see early step) that leaves you 22 drives for data aggregates.

§ I recommend creating at least two data aggregates for training purposes (volume move, simulate multiple drive types such as SAS, SATA, SSD)

§ You might want to leave enough spares drives that you can be ready to do aggregate creation experiments. Also, these are your aggregates so also pretty easy to delete.

§ A possible scenario (pick your own naming convention):§ Aggregate name: hq_n01_sas01 with 8 drives§ Aggregate name: hq_n01_sata01 with 8 drives§ Aggregate name: hq_n01_ssd01 with 6 drives

Take ownership of all disks Viewing the current ownership and then disk assign -all


NOTES:

• Notice that the Disk Type reports as FCAL. We are in pretend land here so it doesn’t really matter but keep this in mind.

• Notice that there are 28 disks and only 14 of them are assigned to <node>-01.

• Notice that aggregate aggr0 only has 3 drives at this point. As described in the earlier ‘Immediate First Steps’ section it is still recommended to make this 5, these screen shots were just taken before that occurred.

Take ownership of all disks (continued) Assign ownership of unassigned disks to <node>-01 and confirm with another disk show


NOTES:

• Notice that aggregate aggr0 only has 3 drives at this point. As described in the earlier ‘Immediate First Steps’ section it is still recommended to make this 5, these screen shots were just taken before that occurred.

Create data aggregates (continued)Example showing creating an aggregate with System Manager


NOTES:

• Notice that the only choice in the Disk Type dropdown is FCAL. Again, this is pretend land and we are making believe this is an aggregate of 8 SAS drives simply by the name convention

• If you are really motivated to maximize space available to provision volumes into, you might decide to pick RAID4. However, there could be (are) NetApp software tools and products that will not allow placing volumes into non RAID_DP aggregates, so be aware.

Create data aggregates (continued)Here are a set of commands to create three aggregates if you prefer CLI for this


Example Cluster Shell Aggregate Create Commands:

aggregate create hq_n01_sas01 -raidtype raid_dp -maxraidsize 14 -diskcount 8aggregate create hq_n01_sata01 -raidtype raid_dp -maxraidsize 14 -diskcount 8aggregate create hq_n01_ssd01 -raidtype raid_dp -maxraidsize 14 -diskcount 6

Create data aggregates (continued)Simulator with 3 data aggregates and aggr0 renamed to aggr0_hq_n01


Create your first SVM – Some planning considerationsYou can now create data Storage Virtual Machines mixing CIFS, NFS and iSCSI


§ If you are on a Windows system:§ CIFS is the easy protocol to access your cluster § NFS for Windows is available but it may not be built into your version and flavor of Windows§ iSCSI for Windows is either built in or available to add (using the iSCSI Initiator Control Panel)

§ If you are on a macOS system:§ Both CIFS and NFS clients are built in, iSCSI Initiators are available

§ In either case, you probably do not have an Active Directory server in your control, hence:§ You must setup and use CIFS in what is called Workgroup mode (as opposed to AD mode)§ ONTAP 9 supports workgroup mode, but the System Manager SVM Setup Wizard presumes AD mode§ Hence:

§ You can not use System Manager’s GUI to create an SVM for CIFS in Workgroup mode (in ONTAP 9.0)§ The following slide provides the ClusterShell template commands to create an SVM with Workgroup CIFS

Create your first SVM (for Workgroup CIFS)Use these commands as a template to create a Workgroup CIFS SVM


Using ClusterShell via ssh (putty, etc) to create the SVM, LIF, etc:

cluster::> vserver create -vserver hq-vs0 -aggregate hq_n01_sas01 -rootvolume hqvs0_root -rootvolume-security-style ntfs -language en_US.UTF-8

cluster::> network interface create -vserver hq-vs0 -lif hq-vs0_lif1 -role data –data -protocol cifs-home-node hq-stor-01 -home-port e0c -address 192.168.17.20 -netmask 255.255.255.0

cluster::> vserver cifs create -vserver hq-vs0 -cifs-server hq-vs0 -workgroup wg

cluster::> volume create -vserver hq-vs0 -volume myvol -aggregate hq_n01_sas01 -size 1gb -junction-path /myvol

cluster::> cifs share create -vserver hq-vs0 -share-name myshare -path /myvol

cluster::> local-user create -vserver hq-vs0 -user-name johnsmith

NOTES:1) You probably need to edit the items in red to match your environment2) This guide mixes examples of the VMnet8 on different subnets (192.168.23.0, 17.0, .80.0, etc.)

NOTES:

• The local-user create command prompts you for a password to create for this new user and that password must meet more requirements than normal.

• For example, If you’re trying to use netapp123, use Netapp123

Access your first SVM (for Workgroup CIFS)Then to access the share, in a PowerShell or cmd window


NOTES:

• You can certainly use the Windows File Explorer for your version of Windows but there are lots of differences between Windows 7, 8, and 10 and different environments

• This syntax should work across all versions of Windows and setups

• Type: net use To see all mapped shares

• Type: net use /? For help on the exact syntax breakdown of the command

\\server\share Server\user (* prompts for pswd) Keep aroundDrive Letter(* auto selects)

Create your first SVM (Workgroup CIFS) (continued)CLI View of interfaces and vservers after setting up Workgroup CIFS SVM


Create your first SVM (Workgroup CIFS) (continued)System Manager view of SVM and volume after setting up Workgroup CIFS SVM


Additional Resources and Issues


This section includes:• Links to other resources and documentation• Common issues you may encounter and resolutions

Resources

§ VMware Workstation Player (referred to within this guide as VM Player)§ Enabling VT technology on your laptop – http://kb.vmware.com/kb/1003944§ Download – http://downloads.vmware.com (scroll down to VMware Workstation Player)§ Documentation – http://pubs.vmware.com/player-12-windows/index.jsp§ Support - https://www.vmware.com/support/player.html

§ NetApp ONTAP Simulator§ Download – http://mysupport.netapp.com/NOW/cgi-bin/simulator§ Documentation – same as above§ Support - http://community.netapp.com/t5/Simulator-Discussions/bd-p/simulator-discussions§ PowerShell Toolkit: http://mysupport.netapp.com/tools/info/ECMLP2310788I.html?productID=6192


§ Watch the console (VM Player window) and wait until you see the login: prompt. If you already see that, open a cmd or PowerShell window and try to ping both:§ Cluster mgmt LIF IP address§ Node mgmt LIF IP address

§ If you can ping the node mgmt LIF but not the cluster mgmt LIF, the most likely cause is the cluster is still synchronizing the cluster ring database and taking longer than expected.

§ Confirm this by ssh’ing into the node mgmt LIF and do a net int show command. If the only LIF you see is the node mgmt LIF, this is the issue.

§ Monitor the process with these commands: net int show , cluster show , stat system show (if high cpu% it’s still sync’ing) and/or set advanced;cluster ring show

§ On a slow system this has been seen to take over 20 minutes. This is one reason it’s better to Suspend and Resume your cluster.

§ While sometimes a reboot cannot be avoided, the only time you must halt your cluster is when you need to adjust VM Player options or when you want to save, copy or share the VM in \Documents\Virtual Machines

ISSUE: I rebooted my cluster node and still can’t access itCluster reboot time can be longer than expected


§ Halt the simulator

§ Reduce the VMs RAM (VM Player -> Manage -> Virtual machine Settings -> Change to 3072

§ Power on the simulator, stopping at the VLOADER> (i.e; press space bar at count down)

§ At the VLOADER prompt:VLOADER> setenv bootarg.init.low_mem 512VLOADER> setenv bootarg.vnvram.size 64VLOADER> setenv nvram_discard trueVLOADER> boot_ontap

§ ONTAP should boot up normally

§ cluster::> run local –command sysconfig # should confirm memory setting

ISSUE: Want to reduce simulator memory from 5GB to 3GB If you would like more breathing room or want to try bring up two clusters, you might want this


§ You have to have enabled the diag account on the cluster (see Tech Note elsewhere)

§ At Cluster Shell prompt:

cluster::> set diagnosticcluster::*> systemshelllogin: diagPassword: <whatever password you set on diag account>node% cd /mroot/etc/log/mlognode% rm *.log.* # this removes just older archive log filesnode% exitcluster::*> set admin

cluster::> vol show vol0 # to see if space reclaimed. If not, delete existing snapshotscluster::> run localnode-01> snap delete vol0 nightly.0node-01> snap list vol0 # there should be none now, delete others if more existnode-01> exit

cluster::> vol show vol0 # should see space reclaimed (thou sometimes it takes a few minutes)

ISSUE: If your root volume fills up over timeIf even after you increase aggr0 and vol0 size you still fill up the root volume


ISSUE: Root volume can become inconsistent


If you see this message on console or upon logging in

§ Halt the node (cluster ::> halt) and wait until fully down

§ Press any key to begin the boot up process

§ As it begins booting, hit any key other than Enter, ex: Space bar, to stop at VLOADER prompt. Enter:VLOADER> unsetenv bootarg.init.boot_recoveryVLOADER> boot_ontap

§ System will boot up but will take awhile to fully rebuild and recover

ISSUE: VMware Tools Warnings bother but want date/time sync’ed


Certain Hypervisors (VM Player) continually suggest installing VMware Tools

§ Halt the node (::> halt) and wait until fully down

§ Press any key to begin the boot up process

§ As it begins booting, hit any key other than Enter, for example: hitthe space bar, to stop at VLOADER prompt. Enter:

VLOADER> setenv bootarg.vm.run_vmtools false VLOADER> boot_ontap

§ System will boot up normally

§ Running this way, the ONTAP guest will no longer even attempt to sync it’s time with the host. As such, you may want to have ONTAP sync with an external Network Time Protocol (NTP) server.

§ This command will establish pool.ntp.org as a time server for your simulator

cluster::> cluster time-service ntp server create pool.ntp.org

§ After a few minutes you should see (using the date command) that the date/time sync up correctly

§ There is a default ONTAP System Configuration Backup process that can slow down the simulator. Take these steps to reduce when these occur and how many copies are retained.

§ At Cluster Shell prompt:

cluster::> set advancedcluster::*> job schedule cron modify 8hour -hour 18 -minute 15 # Once at 6:15pm (up to you)

Warning: Schedule in use by 0 volume Snapshot policy entries, 0 SnapMirror entries, 0 antivirus on-demand entries, 0 SIS policy entries, and 1 configuration backup settings. This change will affect the schedule of all referenced entities. Continue with modify? {y|n}: y

cluster::*> system configuration backup setting modify -numbackups1 1 # 1st (8hour) to 1 copycluster::*> system configuration backup setting modify -numbackups2 1 # 2nd (daily) to 1 copycluster::*> system configuration backup setting modify -numbackups3 1 # 3rd (weekly) to 1 copy

cluster::*> set admincluster::>

ISSUE: Simulator performance is poor during certain periodsCan occur at midnight, 1am, 10am, etc (based on 8hour, hourly and weekly job schedule cron settings)


macOS Installation, Setup and Hints


This section contains:• macOS Installation and Setup (the steps which are different)• macOS and Fusion Hints

ONTAP Simulator: macOS Setup Overview

§ The key process differences are:

§ You will download and install the VMware Fusion application Instead of VMware Workstation Player (VM Player)

§ You will use Fusion to Import and Start Up the ONTAP SimulatorVersus VM Player functions to Open and Play the same simulator

§ Fusion is a paid-for tool versus VM Player which is a free toolDownloading gives you a 30-day free trial. Regular license is ~$79

§ This section will cover the early process differences and then end by directing the reader back to a common point in the VM Player ONTAP process to continue on


macOS VMware Fusion Prerequisites

§ System Requirements § Any 64-bit capable Intel® Mac® (Compatible with Core 2 Duo, Xeon, i3, i5, i7 processors or better)§ Minimum 4GB of RAM (though with ONTAP 9 you’ll need a 8GB system)§ 750MB free disk space for VMware Fusion and at least 5GB for each virtual machine

§ Host Operating Systems§ Mac OS X 10.9 Mavericks§ Mac OS X 10.10 Yosemite§ Mac OS X 10.11 El Capitan§ macOS 10.12 Sierra


Download Fusion from VMware.comFind All Downloads -> look for VMware Fusion -> then click the Try choice


1

2

Download Fusion from VMware.com (continued)


NOTES:

• You’ll be presented with the choice of regular or Pro.

• The same thing gets downloaded in either case so pick either.

• Later, if you purchase a license, the regular should be enough but review the comparison online.

• The download usually goes into your Downloads folder

After downloading, Install Fusion


NOTES: Your desktop may be configured differently, but the basic install steps are:

1. When you select a download (regular or Pro) you’ll get the .dmgdisk image file (shown here on the desktop but likely in your Downloads folder)

2. Double-click the .dmg file to open which shows the contents of the VMware Fusion disk

3. Double-click the VMware Fusion disk which shows the icon for the VMware Fusion.app

4. Click on and drag the .app to your Mac’s Applications folder

5. On the desktop pictured, the Applications folder is in the dock so it can be dragged to that dock icon

2 34

5

Start Fusion


NOTES:

• Verify that you have the administrator password for you Mac

• In the Applications folder, double-click VMware Fusion

• The Virtual Machine Library windows appears.

• If it doesn’t appear, select from top of screen menu Windows -> Virtual Machine Library (or Shift-Command-L)

• (Optional) To Save Fusion in the Dock, right-click the Fusion icon in the dock and select Options -> Keep in Dock

Adding ONTAP Simulator to Fusion


NOTES:

• Following the steps beginning on page 18 of Simulate ONTA9.0 Installation and Setup Guide (.pdf)

• From the Fusion menu bar click File -> Import

• In the Choose an Existing Virtual Machine window click [Choose File…]

• Then browse to and choose the .ova file downloaded previously

• Click [Continue]

1

2

3

4

Adding ONTAP Simulator to Fusion (continued)


NOTES:

• Fusion will present a window allowing you to name to VM you are creating and select a folder to create it in

• For the VM name, select something that matches your planned cluster name with an added -01 to represent that this is the first (and maybe only) node of the cluster( lb-stor-01 shown here )

• You can leave the folder as Virtual Machines which is a new folder in your Mac user Documents folder( a good default to leave it at )

• Click [Save]

1

2

3



NOTES:

• The VM is now created.

• You can optionally look at [Customize Settings] but do not change anything at this point.

• Click [Finish]



NOTES:

• Your Virtual Machine Library should now look something like this.

• Before you Start Up the virtual machine there is one more step: to determine what subnet number Fusion has generated for the VMnet8 subnet inside your Mac.

• This is similar to the Windows VM Player setup (see prior slides) where we used ipconfig to determine the subnet. Here we’ll use ifconfig as shown on next slide

Determining the VMnet8 Subnet


NOTES: to obtain the VMnet8 subnet

• Open a Terminal Window

• Type ifconfig vmnet8

• Write down to record the IP address after inet which is your Mac’s IP address in the new VMnet8 subnet which Fusion created.So in the case shown, the VMnet8 subnet is 192.168.126.0 and 192.168.126.1 is your Mac’s IP address in that subnet

• The mask is 255.255.255.0 (the equivalent to the hex 0xffffff00 shown above)

NOTES: to open a terminal window

• Method #1:• Press F4• Click Other folder icon• Click the Terminal app icon

• Method #2:• Click the icon in upper

right of the top menu bar• Type terminal and hit enter

Click Startup and you’ll begin to see ONTAP Booting


This is similar to powering on a FAS controller for the first time NOTES:

• Back on your Virtual Machine Library window, with your ONTAP simulator VM highlighted, click the arrow or Start Up icon.

• A new console window will open and begin showing the simulator booting up

1


Another important aspect of Fusion to UnderstandHow to direct your cursor, or user input control, between the Fusion console and your Mac

NOTE: In the early stages, this can be confusing. If you’ve clicked into the console window and you’d like to do something else (such as to google something or look at local files) you need to press Ctrl+Command to free your user input focus from the Fusion console.

If your cursor seems to be missing, it is probably just assigned into the console window. Just press Ctrl+Command at the same time and then wiggle your mouse. It will be back to your Windows system.

But be prepared to click back into the VM console because soon you will need to press Ctrl-C to get the ONTAP Boot Menu to zero disks.


Click into the VM console window and be ready to type Ctrl-CPress it a few times to be sure and look for the “Boot Menu will be available” message

NOTE-1: If you miss the chance to enter Ctrl-C at the right time, let it go and it will reboot once, maybe twice. Once you get it, choose option 4

NOTE-2: At this point, the simulator is like a regular ONTAP 9 system shipped from the factory except it’s disks were not zeroed. So we do that as the first step. It will warn you and ask if you are sure. Answer yes to both. Expect approximately 5-10 minutes to zero. If your laptop uses a flash drive, faster yet.

NOTE-3: From this point forward, these macOS setup directions merge back into the prior steps for Windows and VM Player. Continue back at approximately slide 32 or look for the ‘Pick up here’ NOTE and the Apple logo.

HINT: Make Suspending the Simulator the default


To avoid ONTAP shutdown and reboots, change Preferences NOTES:

• In Fusion menus, select VMware Fusion and Preferences …

• In the General tab, the first option controls what happens when you close a VM console window.

• Select Suspend the virtual Machine

• The [_] Confirm before closing choice is up to you

• On an HDD based Mac, the suspend and restore times might be 60 to 90 seconds

• On an SSD based Mac, the suspend and restore times might be 10 to 20 seconds

HINT: Looking at or changing a VM Settings


While halted and down, you can edit a VMs Settings NOTES:

• If you click Settings you’ll get the VM Settings window.

• Processors & Memory let you control the amount of memory provided to the VM.

• Network Adapter 1,2,3,4 are e0a e0b, e0c, e0d respectively

• If you edit a Network Adapter, you should normally select ‘Private to my Mac’ as ‘configured to use’ which is the VMnet8 local subnet.

HINT: ssh is built into macOS


You can open a Terminal windows and ssh directly into the cluster

NOTES: to open a Terminal window

• Method #1:• Press F4• Click Other folder icon• Click the Terminal app icon

• Method #2:• Click the icon in upper

right of the top menu bar• Type terminal and hit enter

HINT: To edit the /etc/hosts on your macOS system


Using terminal windows and vi editor is shown below

NOTES:

• If you have a Unix background and prefer the vi editor, enter:

sudo vi /etc/hosts

• Don’t use vi if you are now experienced with it. Type <esc>q! to get out without making any edits.

• Another editor that is a little easier to pickup is nano, enter:sudo nano /etc/hosts

• After editing, display new file with:sudo cat /etc/hosts

HINT: Mounting a CIFS share on macOS


Use the Finder menu Go -> Connect to Server ...NOTES: Fill out Server Address

• smb:// indicates CIFS

• hq-vs0\johnsmithis server-name\user-name

• @separates user and share

• hq-vs0/myshareis server-name/share-name

• After clicking Connect it prompts for password

• HINT: Once you get ‘myshare’ on the desktop, right-click it and Make Alias so that you can quickly access later

1

2 3

ONTAP Simulator: Getting Started Quick - NetApp · ONTAP Simulator: Getting Started Quick A guide...

Documents

Transcript of ONTAP Simulator: Getting Started Quick - NetApp · ONTAP Simulator: Getting Started Quick A guide...