NCDA Study Part 2.1 – Data ONTAP: Configuration

When you first boot up a NetApp array, you’ll need to go through the initial setup to configure the basics for Data ONTAP.   I covered the process of basic configuration back when I discussed building the Data ONTAP Simulator VMs.  So this first section will look very familiar.

We’re going to perform the following labs in both the CLI and System Manager where the capabilities to do in both exist.

  • Initial Setup of the controller
  • License the products

Initial Setup – CLI

The initial configuration of Data ONTAP prepares the device for remote connectivity and allows you to SSH into the device once the configuration is completed.  From that point, more in depth configuration needs to take place to prepare the device for service.  This part of the setup process is only able to be performed from the CLI of the device.  This is typically done using the cable provided by NetApp on the physical appliance or by using a blue Cisco roll-over cable if you don’t have the NetApp cable.  The cable is plugged into the serial IOIO port on the back of the first controller.  You can use any terminal emulator at that point pointed to the COM port on a laptop with the settings 9600baud 8N1.  Because I’m doing this in VMware, it’s easier because you just use the console window of the virtual machine.

  • Boot device
  • When prompted to access the Boot menu press CTRL+C
  • Press 4 to Zeroize and clean drives
  • Confirm with y
  • Confirm with y
  • System will reboot

Allow the wipe and disk assign process to take place.  When the system finishes zeroizing the disks and assigning ownership, it will then move into configuration mode.

  • Enter the hostname of the simulator (I named mine ONTAP1/2)
  • Take default on IPv6 of no
  • Take default on interface groups of no
  • Enter the IP address of the e0a interface of 192.168.175.10
  • Enter the Subnet Mask of 255.255.255.0
  • Take default on media type of auto
  • Take default on flow control of full
  • Take default on jumbo frames of no
  • Enter the IP address of the e0b interface of 192.168.175.11
  • Enter the Subnet Mask of 255.255.255.0
  • Take default on media type of auto
  • Take default on flow control of full
  • Take default on jumbo frames of no
  • Don’t enter an IP for e0c
  • Don’t enter an IP for e0d
  • Take the default on web interface setup of no
  • Enter the IP address of the default gateway of 192.168.175.51(our router’s IP address)
  • Don’t enter the IP address for an administrative host
  • Enter the hours of the timezone from GMT of -6 (Chicago)
  • Enter the name of where the filer is located of Chicago
  • Take the default for root directory of /vol/vol0/home/http
  • Take the default of DNS resolver of no
  • Take the default of NIS client of no
  • Press Enter
  • Take the default for ACP of no
  • Allow VM to finish configuration

Once this initial setup is complete, you can now login to the device via SSH.  From this point you can run the sysconfig command to get some basic information about the device.  If you’re device is an HA pair, you’ll need to configure the other controller using the same methods above using different IP addressing.

intial_config_step1

Licensing – CLI

The next step is to license the device.  This can be done using either the OnCommand System Manager or through the CLI.  It’s much faster to do it via the CLI as with System Manager, you have to add them one at a time.  Since we’re using the Data ONTAP Simulator, it comes with free licenses for use with this VM.  I typically put them into Notepad++ so they’re easier to add all of them at once.

7-mode Licenses
—————
License Key Purpose
a_sis MTVVGAF Deduplication (Advanced Single-Instance Storage)
cifs DZDACHD CIFS protocol
compression CEVIVFK Compression
disk_sanitization PZKEAZL Disk sanitization
http NAZOMKC HTTP protocol
fcp BKHEXNB Works but does not provide much functionality
flex_cache_nfs ADIPPVM FlexCache license
flex_clone ANLEAZL FlexClone license
iscsi BSLRLTG iSCSI protocol
nearstore_option ELNRLTG NearStore personality
nfs BQOEAZL NFS protocol
operations_manager CYLGWWF Operations manager
protection_manager CGUKRDE Protection manager
provisioning_manager UYNXFJJ Provisioning manager
smdomino RKBAFSN SnapManager for Domino*
smsql HNGEAZL SnapManager for SQL Server*
snaplock ZOJPPVM SnapLock WORM Compliance edition
snaplock_enterprise PTZZESN SnapLock WORM Enterprise edition
snapmanagerexchange BCJEAZL SnapManager for Exchange*
snapmanager_hyperv COIRLTG SnapManager for Hyper-V
snapmanager_oracle QZJTKCL SnapManager for Oracle
snapmanager_sap WICPMKC SnapManager for SAP
snapmanager_sharepoint UPDCBQH SnapManager for SharePoint
snapmirror DFVXFJJ SnapMirror between simulators
snapmirror_sync XJQIVFK Synchronous SnapMirror between simulators
snaprestore DNDCBQH SnapRestore
snapvalidator JQAACHD Oracle SnapValidator license
sv_linux_pri ZYICXLC Open Systems SnapVault from Linux clients*
sv_ontap_pri PVOIVFK SnapVault “primary” (source filer)
sv_ontap_sec PDXMQMI SnapVault “secondary” (destination filer)
sv_unix_pri RQAYBFE Open Systems SnapVault from UNIX clients*
sv_windows_pri ZOPRKAM Open Systems SnapVault from Windows clients*
syncmirror_local RIQTKCL SyncMirror (think RAID 4+1)
vfiler NQBYFJJ Multiple virtual Filers
vld JGFRLTG

The command to add all of these in is license add <license>.  So we end up with this as the script:

 license add MTVVGAF
 license add DZDACHD
 license add CEVIVFK
 license add PZKEAZL
 license add NAZOMKC
 license add BKHEXNB
 license add ADIPPVM
 license add ANLEAZL
 license add BSLRLTG
 license add ELNRLTG
 license add BQOEAZL
 license add CYLGWWF
 license add CGUKRDE
 license add UYNXFJJ
 license add RKBAFSN
 license add HNGEAZL
 license add ZOJPPVM
 license add PTZZESN
 license add BCJEAZL
 license add COIRLTG
 license add QZJTKCL
 license add WICPMKC
 license add UPDCBQH
 license add DFVXFJJ
 license add XJQIVFK
 license add DNDCBQH
 license add JQAACHD
 license add ZYICXLC
 license add PVOIVFK
 license add PDXMQMI
 license add RQAYBFE
 license add ZOPRKAM
 license add RIQTKCL
 license add NQBYFJJ
 license add JGFRLTG

From the CLI, paste in the commands and press enter.  This is what you will see:

cli_license_step1

Some of the licenses will already be part of the Simulator and some will not.  Some might even require a reboot of the controller to facilitate the activation.

Licensing – OnCommand System Manager

To perform this same task from OnCommand System Manager, you’ll need to open it up and connect to the controller.  System Manager requires Java Runtime 32bit and Adobe Flash Player to be installed before you can install the application.  The installation for System Manager is straightforward, take the default settings.

When you launch the System Manager application, you’ll need to add a controller:

  • Click the Add button once the console opens and input the IP address of the controller as well as the root user and login password, and click Add

osm_step1

  • Allow the controller to be found and added and then double click the newly added controller to connect to it

osm_step2

  • Expand the controller name, Configuration, System Tools and Licenses.  I’m going to add the CIFS license to the device by clicking on Add and then pasting in the license code from above.

osm_step3

Once the license is added, you’ll see it in the list of licenses.  All licenses have to be added one at a time via System Manager.  This makes it a very lengthy process adding all the licenses from above.  It’s much simpler to add them via the CLI and they can be bulk imported very quickly.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s