about

install-unity-falcon.ps1 deploys a DELL|EMC Unity VSA on VMware Workstation.
it is a fully automated process.
the process changed from a pre-falocn release, as the ova deployment has some changes. to iplement theese changes, som teaks have to be made by the installer:

  • unity needs to run pvscsi devices
  • only system disks are allowed at system boot time
  • uuid has changed from a SP uuid to a system UUID ( randomly changed with every deployment ), so a license file can not be re-used as the first byte changes with every deployment of the same machine: image

the changes requires a Change in the deployment process to invoke at least one shutdown - reconfig and a injection of the lic_file from a "drop-in" directory ( only if you want to autoconfigure luns, iscsi and fileservices )

Import

to start a unity deployment, we have to initially Import the ova. simply run 

.\install-unity-falcon.ps1 -ovf C:\Downloads\UnityVSA-4.1.0.9058043.ova

where you have to replace the ovf with your downloaded Version

Deploy

there are multiple options to deploy unity.

  • base deployment ( no license required, all config done vi web ui)
.\install-unity-falcon.ps1 -Masterpath C:\Users\KarstenBottlabbuildr\Master.labbuildr -Mastername UnityVSA-4.1.1* -configure -Defaults
  • a full flavored unity including join to an active directory can be done with: 
.\install-unity-falcon.ps1 -Masterpath C:\Users\KarstenBottlabbuildr\Master.labbuildr -Mastername UnityVSA-4.1.1* -configure -Defaults -lic_dir C:\labbuildr2017\ -Protocols cifs,
iscsi,nfs -Disks 6 -iscsi_hosts all

used switches

  • lic_dir drop-in directory fo the licence we have to download once we get the system uuid upon first reboot
  • Masterpath directory where the master was deployed from the ova
  • Mastername name of the master to be picked
  • configure do a base configuration
  • Protocols if lic_dir is present, the provided protocols are deployed

the workflow starts with the deployment and first boot of the unity System. the first boot may take up to 10 minutes ( a lot of checks, key generation and image copies are taking place )

image of step1 imaging on console: image

image of powershell output on step1 image

once the system imaging is done and the system Management os has booted, the runtime Services are configured. this is a 27 step process you may also watch the 27 steps in the VM´s console:
image ip-addresses will be configured once step 27 is reached.

once the first deployment Phase reached System ready, the System uuid is presented and the System reboots. Copy the UUID and paste it in https://www.emc.com/auth/elmeval.htm to get your license.

image image

download the license and copy the file into the drop-in Directory specified with -lic_dir

image

The System will do a second boot now and start the configuration of the System:

image

if you have not already presented a license file, the installer will wait for you and check the drop-in dir until the file is present. note: do not rename the file upon save or copy, as the installer watches for the uuid in the Name.

once the license file is found, the System customization starts with the selected protocols:

image

if cifs needs to be configured, a second reboot might be required for the NTP adjustment

image

final views

These samples are an example representing the full config done by labbuildr image

image

image