Unityvsa Installation and Theory of Operation. Copyright ©2016 EMC

Welcome to UnityVSA Installation and Theory of Operation.

Copyright ©2016 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. The trademarks, logos, and service marks (collectively "Trademarks") appearing in this publication are the property of EMC Corporation and other parties. Nothing contained in this publication should be construed as granting any license or right to use any Trademark without the prior written permission of the party that owns the Trademark.

EMC, EMC², the EMC logo, AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Aveksa, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect, ClaimPack, ClaimsEditor, Claralert ,cLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration Intelligence, Configuresoft, Connectrix, Constellation Computing, CoprHD, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD Boost, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences, Documentum, DR Anywhere, DSSD, ECS, elnput, E-Lab, Elastic Cloud

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 1 Storage, EmailXaminer, EmailXtender , EMC Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, Isilon, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Mozy, Multi-Band Deduplication,Navisphere, Netstorage, NetWitness, NetWorker, EMC OnCourse, OnRack, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere, ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, Silver Trail, EMC Snap, SnapImage, SnapSure, SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data Consistency, Vblock, VCE. Velocity, Viewlets, ViPR, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, VSAM I/O PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation ‹#› This course covers an overview of the release of the UnityVSA Software Defined Storage solution, and the specific features and functions it supports. Details about the licensing and support model are presented. Procedures for deploying the UnityVSA OVA file in an ESXi environment, performing the initialization and initial UnityVSA setup, creating a NAS Server, creating UNIX and Windows File Systems and Shares, and creating iSCSI Block Storage are all discussed and demonstrated.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 2 This course is segmented into six distinct topics. First is a product overview. The following five topics provide demonstrations for deployment and initialization, initial setup and storage provisioning.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 3 This module focuses on the rationale for the release of UnityVSA, its benefits, the system configuration and the specific features and functions it supports. The module also describes the product offerings and licensing model, and explains the system limits based on the license with larger capacity.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 4 Unity Virtualized Storage Appliance (VSA) is a software defined storage platform running on general purpose hardware. UnityVSA is deployed on a VMware ESXi hypervisor.

The UnityVSA can coexist with and provide storage to applications running on the same server hardware. Multiple VSA instances can be deployed on a single server.

The UnityVSA is a Unified Array, providing both Block (iSCSI), File (NFS & SMB/CIFS), and VVols in one integrated platform. A consistent look and feel across the Unity platform is made possible using HTML5 Unisphere. A consistent Unity feature set and data services such as Unified Snapshots and Replication are available with the UnityVSA.

UnityVSA is a low cost deployment solution, ideal for testing application features and functionalities and training new storage administrators. The solution is also a suitable software defined storage solution for Remote Office/Branch Office (ROBO) deployments when the amount of employees does not justify the use of a dedicated storage array.

Service providers can benefit from the deployment of multiple VSAs for multiple clients, offering multi-tenancy storage instances.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 5 The virtualized Unity models are the replacement for the VNXe1600 systems. The Unity storage software stack, running on a purpose built hardware, is virtualized and encapsulated into an OVA file which can be deployed in an ESXi host.

Reliable block storage is provided to the UnityVSA via a RAID card associated with the hypervisor and host hardware (Direct Attached Storage) or via an external RAID protected Storage array (EMC arrays or 3rd party storage arrays).

RAID protection is provided at the physical level – UnityVSA adds no RAID protection on top of the virtual disks. Storage is provisioned to the UnityVSA via Fibre Channel/iSCSI (block) or NFS (File).

VMware vSphere datastores are built from file systems (NFS) or LUNs (VMFS) provisioned by the backend.

vDisks for the UnityVSA are created from the provisioned ESXi datastores.

UnityVSA storage pools can then be provisioned from the vDisks. And Unity storage resources (Block, File and VMware datastores) can be provisioned to hosts using the storage pools. UnityVSA provisions Block storage to hosts only using the iSCSI protocol.

The Community Edition is intended for non-production environments such as test, development, and training. In the Community Edition all the UnityVSA features are available, it is completely free and there is no expiration date associated with it. The capacity limit is 4TB. The support is based on a EMC monitored Community forum where users can access, post questions and participate in discussions.

The Professional edition is recommended for production use. The Professional Edition has all features available with a subscription valid for one year. The edition comes in three flavors of supported storage capacity: 10, 25, and 50 TB. The Professional edition comes with EMC Enhanced support, including the configuration of ESRS/ConnectEMC, and available phone assistance to troubleshoot and fix failures with the virtual system,

There are capacity upgrades available for the Professional subscription licenses. These only extend the capacity but not the subscription period. • 10 TB to 25 TB upgrade path license • 10 TB to 50 TB upgrade path license • 25 TB to 50 TB upgrade path license

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 7 1 Any paid licenses can be installed non-disruptively. Limits will scale accordingly with the installed license (up to the supported maximums). The licenses have a minimum code requirement – a newer license cannot be installed on an older version of code.

For the virtual systems, the license keys are based on the system’s UUID (Universally Unique Identifier). These keys, which are included in the License (.lic) files can be obtained through the ‘Get License Online’ link in the Unisphere Licenses page of the Initial Configuration wizard or License Management page in the Settings window. The user must provide the virtual system UUID to the Electronic Licensing Management System (ELMS) and the license authorization code (LAC) ID to download the license file locally.

The license file must then be transferred to a computer with access to the virtual Unity system. By clicking on the Install License link, the user can upload the license file from the local machine to the storage system after accepting the license agreement.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 8 The following will be a typical scenario for your UnityVSA. The customer purchases a license which will be valid for 12 months. Four weeks before expiration, they see license expiration alerts in Unisphere. These are repeated periodically – 3 weeks before, then 2 weeks, then 7 days before, then 6, 5, 4, 3, 2, 1 days before the expiration date. There is also a ‘Get License’ link in the GUI that directs customers to Software Licensing Central where they can renew their license. Once the license expires, users can continue to use the UnityVSA but not provision anything new until they renew their license.

Please note that support is bundled in with the VSA paid licenses. So if a paid license expires, the customer’s support contract tied to the license expires too. They can never have the software without support or just support with an expired software license. From a diagnosis standpoint, the support contract is your best gauge. The license expiration date is also stored in ELMS.

Customers must buy a license for equal or larger capacity.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 9 This chart shows the Unity features that are supported by the Unity VSA. Note that some of the features that rely on specific physical hardware are not supported by the UnityVSA.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 11 This module covered the rationale for the release of UnityVSA, its benefits, the system configuration and the specific features and functions it supports. The module also described the product offerings and licensing model, and explained the system limits based on the license with larger capacity.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 12 This module focuses on the deployment of a UnityVSA system in a VMware vSphere ESXi hypervisor. The module also describes the initialization process for the deployed virtualized system using installation tools and utilities. The module explains how to add virtual disks to the UnityVSA for data storage.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 13 Hardware specifications for the UnityVSA deployment start with a 64 bit, dual or quad core CPU from the x86 Intel family running at 2GHz or faster. The Xeon E5 Series or later processor is recommended. The minimum version of VMware hypervisor version running on the server must be 5.5.

Memory is set at a minimum of 16 GB for ESXi 5.5 or 18 GB for ESXi 6.0.

The number of network interfaces is four 1GbE or four 10GbE.

The RAID Controller must support at least one of the following RAID Levels: 1, 5, 6, and 10 with a 6Gbps Back End connectivity and a maximum of 32 physical disks. Minimum Cache size of 512MB or higher is recommended. The host interface will be PCIe2.0. A backup battery, and S.M.A.R.T. support are required.

Several different servers from Lenovo, Cisco, IBM and Dell are suitable to host the UnityVSA.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 14 Here are the specifications for the UnityVSA system. The appliance is deployed with a single SP with 2 virtual CPUs with 2GHz or faster clock speed. The System has a 12GB memory and uses 4 data ports for I/O. These ports are vmxnet3 vNICs emulating 10GbE.

The supported protocols are iSCSI (Block) and NFS or SMB (File).

Some features will not be configurable via Unisphere. Features like FAST Cache, Quick Start pool provisioning, Fibre Channel, Link Aggregation, MCC Write Caching, MCR, physical array hardware (fans, batteries, hardware-based encryption, etc.) are not applicable.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 15 The UnityVSA OVA deployment is straightforward. A VMWare ESXi 5.5 or later environment is required. Standard tools in the vSphere web client are used for the deployment. Right click on the server chosen for the Unity deployment and select ‘Deploy OVF Template’ (an OVA file is synonymous with OVF template).

It is a good idea to check that the ESXi server used for OVA deployment has access to the client server running Unisphere and access to the client server to perform I/O operations from the UnityVSA.

From the vSphere Web Client Deploy OVF Template wizard, locate the OVA file on the local machine and follow the next steps to deploy the virtual appliance.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 16 When deploying the Virtual Unity system OVA file in vSphere Web Client, it is possible to configure the IPv4 and/or IPv6 address for the management interface from the Customize template page of the Deploy OVF Template Wizard. If no configuration is done on this page, the virtual system will try to get a dynamic IP address from a DHCP server when it is powered on. If the network includes a DHCP server and a DNS server, then an IP address can be assigned automatically to the management interface.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 17 The deployment creates a UnityVSA that is ready to power on when the deployment finishes. The UnityVSA self initialization continues for at least another 30 minutes or more.

Please note that the UnityVSA MUST be powered on prior to making any edits to the UnityVSA virtual machine settings.

Changes to the physical configuration of a UnityVSA VM such as adding or removing network interfaces or modifying the cache size are not supported. The only accepted modifications of the physical configuration of a UnityVSA VM is the addition of virtual disks to store user data.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 18 To verify that the UnityVSA Initialization is complete, log in to the UnityVSA console as ‘service’ and run the svc_diag command. The command should return a clean output with no failures as shown in the example.

The initialization is now complete and you can move on to creating vDisks for the UnityVSA.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 19 The svc_initial_config command is used to configure an IPv4 and/or IPv6 address for the management interface of an unconfigured Unity system. This is an alternative method for configuring the management interface in case it was not customized during the OVA template deployment and if the UnityVSA hass not been assigned a dynamic IP address from a DHCP server in the same network.

Besides the network parameters for the management interface, the command also configures the system with a given friendly name.

From the vSphere client, the implementer must open the Console for the deployed virtual Unity system and login with the service account (default credentials are service/service). Then using the syntax shown in the slide run the svc_initial_config command to assign an IP address to the management interface.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 20 The Unity Connection Utility can also be used to configure an IPv4 and/or IPv6 address for the management interface of an unconfigured Unity system. This is an alternative method for configuring the management interface in case it was not customized during the OVA template deployment and if the UnityVSA is not been assigned a dynamic IP address from a DHCP server in the same network.

The Unity Connection Utility software is available for download from the EMC Online Product Support page. It must be installed on a Windows host in the same subnet as the UnityVSA.

The installer package includes the 32 bit JAVA Platform Standard Edition 1.8 Update 60 (Java 8 is embedded with Connection Utility).

When executing the utility the Auto-discover method must be selected from the Welcome page. The Discover engine will search the network for unconfigured systems and list them. The UnityVSA system can be identified by its serial number. The user must select it in order to continue with the configuration.

In the Configure Network Information page select the option to use a static IPv4 and/or IPv6 address. Then enter the information recorded in the Connection Utility section of the Configuration Worksheet to assign the static IP address for the management interface.

Review the information and then click Configure to apply the settings to the UnityVSA management interface. The Deploy page will display the status of the configuration process, which can take up to 10 minutes. Once the process is done a blue check mark is displayed and the Finish and Start Unisphere buttons are enabled. Click Finish to close the wizard.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 21 The InitCLI.exe tool is available for download from the EMC Online Product Support page. The tool must be run from a Windows host in the same subnet as the UnityVSA.

The discover parameter will search the network for available systems to be configured and will list the information about the system including its serial number (ID) shown in the first box . The output qualifier specified the output format as NVP (Name Value Pair) or CSV (Comma Separated Value).

The discovered UnityVSA system can then be configured by using the configure parameter and specifying the serial number of the system, and the IP address, subnet mask, gateway and a friendly name.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 22 When the UnityVSA is deployed, three virtual disks (vmdks) are automatically created for the VM’s system data. These are the virtual disks identified as 1 to 3. These disks should not be modified or deleted.

After the initialization completes, at least one virtual disk must be added for user data. More vDisks can be added when additional storage for user data is needed. Up to a maximum of 16 user vDisks are supported.

From Hosts and Clusters, expand the ESXi server where the UnityVSA was deployed, right click on the UnityVSA and select ‘Edit Settings’ from the pull down menu.

From the bottom of the Virtual Hardware tab, use the ‘New Device’ menu to select ‘New Hard Disk’. Enter the appropriate settings to the screen

If more than 12 user vdisks are added, another SCSI controller will be automatically added to accommodate the additional disks.

Ensure the SCSI controller type is "paravirtual". Other types are not supported and can cause boot problems and unrecognizable disks. vSphere can be used to view and change the controller type if needed.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 23 The maximum size supported for the New Hard Disk depends on the installed license and the free capacity of the underlying provisioned storage (in the example the maximum capacity of the used datastore is 2.10 TB). changes depending on the license installed. Be sure to select the ‘Thick provision eager zeroed’ radio button under the ‘Disk Provisioning’ parameters. ‘Thick provision eager zeroed’ is recommended for best performance.

To add more disks select New Hard Disk from the New Device drop-down list and click Add.

To finalized the Edit Settings and reconfigure the virtual machine click the OK button.

The new disks will be added to the virtual appliance.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 24 This video demo shows how to deploy a UnityVSA system and initialize it by running the svc_initial_config command from the vSphere Console to the SPA and by running the Connection Utility from a Windows host.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 25 This video demo shows how to add virtual disks to the UnityVSA to provide data storage for the client hosts.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 26 This module covered the deployment of a UnityVSA system in a VMware vSphere ESXi hypervisor. The module also described the initialization process for the deployed virtualized system using installation tools and utilities. The module explained how to add virtual disks to the UnityVSA for user storage.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 28 After initializing the UnityVSA system, the user can open an internet browser session to the system management port and log into Unisphere with the default credentials (admin/Password123#) to configure the system.

During the deployment, a new IP address was assigned to the UnityVSA Storage Processor Management Interface.

After deployment, the management IP address can be found in vSphere Web Client in the UnityVSA VM Summary tab, under the "DNS Name" field.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 29 Unisphere will launch the Initial Configuration wizard to walk the user through the initial setup of Unisphere and prepare the system for use. After the initial setup is concluded the wizard can be launched at any time from the settings window.

The wizard sequence is displayed here and will be demonstrated in a video.

The first time the wizard is launched the Copyright page will display the End User License Agreement (EULA) and require that the user check the radio button to accept it in order to continue to the next step. The next step requires the user to change the admin and service user passwords from their default values (service password can be set to have the same password as the admin user). The Unisphere licenses page allow the user to obtain the Unisphere license file online and upload to the system.

The next pages allow the configuration of DNS and system time synchronization support. A pool can be also configured for provisioning file or block storage. This pool is also a requirement for creating a NAS server (optional). Other optional settings involve configuring alert notifications via emails or SNMP traps, and iSCSI interfaces for block storage.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 30 One of the steps of the Initial Configuration wizard is the installation of the product license file for the purchased subscription. Installing the license is not an optional step and cannot be skipped. This step will unlock the features that are enabled by the license subscription. As mentioned before the license key for the UnityVSA system is based on the system’s UUID (Universally Unique Identifier). These keys which are included in the License (.lic) files can be obtained through the Get License Online link in the window.

The user must provide the virtual system UUID and the license authorization code (LAC) ID to download the license file locally. Then upload the license by selecting the Install License option. This option will upload the file to the storage system and activate the license. This file must be local to a computer that has network access to the UnityVSA system.

It is possible to verify the licenses that were activated by clicking on the View License link.

Once a license is installed observe that additional features that are enabled by the license subscription such as ESRS are also presented on the wizard for configuration.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 31 The virtual disks created just after the UnityVSA deployment will be used to create the storage pools. At least one pool must be created prior to creating storage resources or NAS servers.

The first time the Create a Pool wizard is launched you must specify pool tiering information (Capacity, Performance or Extreme Performance). This information is not discovered by the UnityVSA OE. Therefore you must manually associate tiers with each virtual disk. You can create multiple pools and assign each pool a different tier, or create a multi-tiered pool.

The Storage Pool can later be expanded by selecting any of the unused virtual disks.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 32 One of the steps of the Initial Configuration wizard is the creation of the iSCSI interfaces to allow the provision of block storage to hosts. By clicking on the “add sign” link the Add iSCSI Network interface window will open and allow the configuration of a SPA port as an iSCSI target.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 33 A NAS Server can also be created from the wizard to allow the provision of file storage to hosts. By clicking on the “add sign” link the Create a NAS Server window will open and allow the configuration of an interface on the SPA to share file systems via SMB/NFS protocols.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 34 This video demo shows the initial setup of the UnityVSA with the Initial Configuration wizard in Unisphere. The demonstration will walk through the configuration steps required to setup a new UnityVSA deployment, create a Storage Pool from virtual disks and create a NAS Server.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 35 This module covered the Initial Setup of the UnityVSA system using the Initial Configuration wizard in the Unisphere interface.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 37 To create LUNs select the Block page under the Storage Section in Unisphere. The LUNs page will be displayed with a list of existing LUNs with its size and percentage of allocated capacity. You can then launch the Create a LUN wizard by clicking on the “ add sign” link. Then follow the wizard steps: • Provide the name and description for the LUN • Select the storage pool to use. • If the selected pool is tiered then it is possible to choose the tiering policy. • Define the LUN size. • Provide access to the SAN host using a previously configured host configuration (with a defined connectivity protocol). • Define the access level of the SAN host to the LUN. • Optionally configure local and remote protection for the LUN, and the Host I/O limits. • Review the LUN to be created on the Summary page then click Finish

The results of the process will be displayed.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 38 To create Consistency Groups select the Block page under the Storage Section in Unisphere. Then select the Consistency Groups page from the top menu. The Consistency Groups page will be displayed with a list of existing CGs with its size and percentage of allocated capacity. You can then launch the Create a Consistency Group wizard by clicking on the “add sign” link. Then follow the wizard steps: • Provide the name and description for the Consistency Group • Click on the “add sign” link to open the Configure LUNs window. • Define the number of LUNs and a name. The name of the LUNs will be the combination of the name and a sequence of numbers. • Select the storage pool to use and define the size of the LUNs. • If the selected pool is tiered then it is possible to choose the tiering policy. • Host I/O limits can also be defined before saving the configuration. • Provide access to the SAN hosts using host configurations previously created (with a defined connectivity protocol). • Define the access level of the SAN host to the LUN. • Review the LUN to be created on the Summary page then click Finish

The results of the process will be displayed.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 39 This video demo shows how to provision block storage to hosts. This demonstration will walk through the configuration steps to create an optional LUN Group and one or more LUNs for iSCSI connected block storage.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 40 To create a storage resource that will be connected by a host via the NFS (Linux/UNIX) or SMB/CIFS (Windows) protocols, you must create a file system with a share.

From Unisphere, select the File option under the Storage section. The File Systems page shows a list of existing file systems with its size, allocated capacity, and the NAS Server and pools they are associated with.

Click on the “add” link to launch the Create a File System wizard. The steps of the wizard include: • Configure the Protocols the file system will support • Select the NAS Server to associate with the file system • Enter a name and optional description for the file system • Select the storage pool to create from and the size of the file system • Define if thin provisioning must be used to create the file system • Optionally select a tiering policy • Provide a name for the share • For Windows Shares it is possible to configure additional SMB settings • For Linux/UNIX Shares it is possible to associate it with a host profile and set the access level: read-only, read/write, and read/write, allow root. • Optionally configure local and remote data protection • Review the File system to be created then click Finish

The results of the process will be displayed.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 41 This video demo shows how to provision file storage to hosts. This demonstration will walk through the configuration steps to create UNIX and Windows file systems as well as NFS and SMB shares.

Copyright 2016 EMC Corporation. All rights reserved. UnityVSA Installation and Theory of Operation 43 This course covered an overview of the release of the UnityVSA Software Defined Storage solution, and the specific features and functions it supports. Details about the licensing and support model were also presented. Procedures for deploying the UnityVSA OVA file in an ESXi environment, performing the initialization and initial UnityVSA setup, creating a NAS Server, creating UNIX and Windows File Systems and Shares, and creating iSCSI Block Storage were discussed and demonstrated.

This concludes the training.