Vous êtes sur la page 1sur 17

Basic NetApp Configuration and Administration Lab1

Equipment Diagram

Exercise environment includes several virtual machines (VMs): one


Windows 2012 Server, one Data ONTAP cluster, and one Linux server. Only the
hardware of the Data ONTAP cluster virtual machine (VM) is simulated; The Data
ONTAP software is authentic.

EXERCISE 1: GETTING TO KNOW YOUR EQUIPMENT KIT


Objectives:Task 1:- Ensure connectivity to a Data ONTAP cluster

Above screen shows the both the cluster are accessible and in healthy state.

Task 2 :- Synchronize the date and time between a Windows domain and
a Data ONTAP cluster

Above image shows the time of both the windows server and clusters are in sync with
US/Pacific time zone

Task 3 :- Ensure that required licenses are installed

Above image shows the license of cluster 1 and the package included in the license.

Task 4:- Add DNS host records for a Data ONTAP cluster and other hosts
to a Windows DNS Manager

Above image shows the DNS entries are added for both cluster1 and UNIX server and
both server and cluster is pinging from windows server.

EXERCISE 2: WORKING WITH DATA ONTAP ADMINISTRATIVE INTERFACES


Objectives:Task 1:- List basic commands for managing a Data ONTAP cluster from
the CLI
There is a huge list of commands which can be used in CLI to manage ONTAP cluster. I
have listed few of them discussed in the lab training.
Version

Displays the version and mode of the ONTAP

Is similar to the help command where it displays the list of available


commands.

Quit the list of commands and return to the CLI prompt

man

Display the index of Data ONTAP manual pages

Network

Display the network command and sub commands

Clusters

Manage clusters

Up

Go up one directory

Storage

Manage storage ,disks, aggregates and failover

Task 2 :- Add a two-node Data ONTAP cluster to be managed by


OnCommand System Manager

Above image shows cluster one is added to the On Command System manager. And
the cluster is functional and the status is up.

Task 3:- Use OnCommand System Manager to configure the SNMP public
community name for a Data ONTAP cluster

Above image shows the SNMP protocol is enabled and the community name public is
added to configuration.

EXERCISE 3: HARDWARE BASICS AND MANAGING PHYSICAL COMPONENTS


Objectives:Task 1 :- Use OnCommand System Manager to display hardware
components
By navigating to Storage on the Nodes section on the Left pane on the command
manager we can check the volumes and disk layout on any cluster. Images below show
the different section of aggregate tab.

Task 2 :- Use CLI commands to display hardware components


To display the hardware components on a cluster on CLI first we have make sure
we are in the navigated to proper cluster and storage command is used to manage to
components.
Command used below for example is storage > disk show

EXERCISE 4: CREATING AND MANAGING AGGREGATES


Objectives:Task 1 :- Use OnCommand System Manager to create an aggregate for a
Data ONTAP cluster

Using create aggregate wizard Aggr1 has been created using the on command
manager.

Task 2 :- Use the command-line interface (CLI) to create an aggregate for a


Data ONTAP cluster

Using the command Storage aggregate Create aggregate aggr2 has been created .

Task 3 :- Delete an aggregate and initialize disks


Now another aggregate by the name aggr_test has been created. Before deleting
the aggregate must be taken offline using the command Storage aggregate offline.
Once it is offline Storage aggregate delete command is used to delete the aggregate.

Once the aggregate is deleted initialize the disk using the command Storage
disk zerospares.

EXERCISE 5: SETTING UP A STORAGE VIRTUAL MACHINE


Objectives:Task 1 :- Use the System Manager Vserver Setup wizard to create an SVM
(called a Vserver by the UI)

Vserver svm1 has been created using the setup wizared. And above image shows the
Vserver being listed on the cluster1.

Task 2 :- Use the Vserver Setup wizard to configure CIFS and NFS settings
and create a logical interface (LIF) for CIFS and NFS data

Vserver has been configured to accept bot nfs and cifs data.

Task 3 :- Use the Vserver Setup wizard to configure a data LIF for the
iSCSI protocol

iSCSI has been configured using above data.

Task 4:- Use the Vserver Setup wizard to configure the SVM administrator

Vserver administrator has been configured.

Task 5 :- Add DNS host records for the SVM management LIF, CIFS data
LIF, and NFS data LIF

Both SVM1 and SVM1_data vservers have been added to the windows DNS manager

EXERCISE 6: CREATING AND MANAGING VOLUMES ON AN SVM


Objectives:Task 1 :- Delegate volume creation to the SVM administrator (vsadmin)

Volume creation has been delegated to SVM administrator.

Task 2 :- Create volumes on the SVM

Volumes Project_y, Project_z, Teams are created.

Task 3 :- Organize the SVM namespace

SVM namespace has been organized in to sub volumes as shown in the image above.

EXERCISE 7: SHARING VOLUMES WITH WINDOWS CLIENTS


Objectives:Task 1 :- Create a CIFS share for a volume at the root of the namespace

Vol1 CIFS share has been created.

Task 2 :- Change the default access control settings


As shown in the image above access have been granted to Learn\Administrator/

Task 3 :- Map a disk to a shared volume and view other volumes that are in
the junction path

Shared Volume has been mounted on the windows server as a network drive.

Task 4 :- Create a CIFS share with share-specific permissions for a volume


in a junction path

Provided specific permission for the individual folder .As show abouve wire access to
the folder Project_y is restricted.

EXERCISE 8: EXPORTING VOLUMES TO UNIX AND LINUX CLIENTS


Objectives:Task 1 :- Confirm that the NFS protocol is allowed on a storage virtual
machine(SVM)

Verified NFS protocol is enabled for the volumes.

Task 2 :- Confirm that the data LIF enables the use of the NFS protocol

Verified LIF allows the nfs protocol.

Task 3 :- Configure multiprotocol access for Windows and UNIX users

Windows to UNIX and Unix to windows protocols have been configured successfully.

Task 4:- Create export policies

Export policies have been created.

Task 5 :- Assign an export policy to a volume

Policy has been assigned to the volume and it is accessible in a Unix server.