This document contains instructions for using vSphere to deploy a virtual Uplogix Control Center (vUCC) running LMS version 5.4 to a VMware server. Note: newer versions of VMware ESXi (v6+) no longer support all features of vSphere, but they do still work for deploying our image. You may use the newer HTML5 application to deploy the vUCC. Requirements and steps are almost identical.
Prepare to have available disk (see Requirements), two IP addresses on the same network with netmask and gateway, NTP server, and an optional DNS server. You will also need to have downloaded the vUCC OVA file (vucc5.4.ova) from the Uplogix Support Site.
|Deployment Size||Storage||Memory||CPUs (2+ GHz)|
|>1000 Local Managers||825 GB thick (SSD)||8 GB||8 cores|
|250-999 Local Managers||~650 GB thin (SAS/SSD)||8 GB||8 cores|
|100-249 Local Managers||~550 GB thin (SAS/SSD)||4 GB*||4 cores|
|1-99 Local Managers||~450 GB thin (SAS/SSD)||4 GB*||2 cores|
|Evaluation vUCC (<10 LMs)||~65 GB thin (SATA)||1 GB||1 core|
*Requires vUCC application RAM settings to be adjusted - see Adjusting Memory
Upgrades of the evaluation UCC are not supported.
Connect to your VM host and select File > Deploy OVF Template.... Although this menu item says OVF, it will let you select OVA files as well. An OVA file is just a package of the OVF file and VMDK files in the TAR format.
Select the vUCC OVA file you previously downloaded.
Depending on the version of your VMware host, you may see a similar warning window below. This is normal and will not impact the deployment of the vUCC. Click Yes to proceed.
Select a datastore with enough free space to handle your deployment (see Requirements).
Select Thin Provision or Thick Provision as appropriate to your deployment size for the disk format. If you have determined that you should use thick provisioning, you may choose lazy or eager zeroed based on your own preferences.
Map the source network to the destination network according to your needs. The default is frequently acceptable.
Ensure Power on after deployment is not selected. Click Finish to begin the deployment of the vUCC.
The progress bar is not very accurate with its time estimation. Since the vUCC has 6 VMDKs (disks) inside the OVA, you will frequently see an estimate like 5 minutes remaining, but then it will move on to the next disk and say the same estimate for remaining time. Typical deployment times vary from 25 minutes (SSD RAID 10) to 3 hours (SAS RAID 5). The deployment time is heavily dependent on the speed of the VMware host datastore and may increase when a datastore is heavily shared by other VMs. Network speed is also a factor and we recommend you use a gigabit link.
Once the deployment has completed successfully, click Close.
The following shows the default settings for the vUCC.
The following shows the default settings for the evaluation vUCC.
If you need to edit any of the deployment settings, right-click on the VM's name. Select Edit Settings... to change the number of CPU cores, memory, or network settings.
Once the settings have been configured, power on the VM. You can do this by right-clicking the VM name again or using the green “play” icon.
We recommend that you configure the vUCC for automatic startup and shutdown. Version 5.4 of the vUCC contains open source vm tools which allow VMware to do a soft shutdown of the VM. While problems usually do not occur with a hard power off, we recommend that you avoid it when possible. Hard power off can occasionally cause file system corruption.
After powering the VM on, click the Console tab. Once the vUCC has finished booting, login as user emsadmin with password password. You may miss the login prompt as information about the database writes to the console. If you see Database “UPLOGIX” warm started, hit enter once and you will be presented with the login prompt.
To configure static IP addresses for the vUCC run the following commands:
If running the VM with anything other than 8 GB of RAM, the memory settings for the vUCC application will need to be changed:
Launch a browser to the first IP address configured to verify successful installation. The default user name is administrator and the default password is password.