PernixData has recently released the new version of his FVP product (see my post here), a software solution that accelerate workloads by using SSDs and RAM to cache reads and writes, lowering storage latency. In this blog series we will cover installation and configuration of FVP 3.0
PernixData FVP 3.0 installation – part 1
PernixData FVP 3.0 configuration – part 2
- ESXi 5.1, 5.5 or 6.0 (5.0 not supported)
- Microsoft Windows Server 2008 or 2012 for the management server with 4 vCPU and 4GB of free RAM for a production installation. It’s possible to install with less in the lab, but it will directly affect the performance, a VM with 4vCPU and 8GB RAM is recommended.
- .NET Framework 3.5.1 SP1 or later
- FVP Management Server will install Java SE 7, and Java Runtime Environment (JRE) 1.8u40. The setup program overwrites any existing installation of the JRE
- Microsoft SQL Server 2008, 2012 or 2014. SQL Express is also supported.
- A service account to run FVP services with admin access the SQL database (this can be dropped to DBO rights on the Pernix database after installation) and full administration on vCenter Server. This account will also be added to the “Log on as a Service” policy.
The PernixData Host Extension needs to be installed on all hosts in the cluster that you are activating FVP. You can install using esxcli or using VMware Update Manager. In this post I will use VUM.
To install the FVP Host Extension using the VMware Update Manager, start importing the bundle.
Attach the Baseline to a cluster or to an ESXi host
Start the Remediation and follow the wizard.
Check the compliance of all your servers.
Installing the PernixData Management Server
Run the installer and accept the license agreement
Select the “Complete” installation to install the Management server and the CLI tools. If you just want the Management Server or CLI tools you can do a custom install.
Enter the VMware vCenter Server and click Browse to select the service account (make sure to use DOMAIN\user format, a UPN such as email@example.com is not supported).
Enter the SQL server details and either select a pre-created database or enter the name of a new database.
Select the name or IP address of the management server: this is the address vSphere clients must be able to access. Configure the HTTP or HTTPS port if required
Continue through the installer pages until we get to the installation
If the VM on which you are installing FVP Management Server doesn’t meet the requirements (8GB of RAM, at least 4 vCPUs), you may receive the warning as shown in the picture. Click OK to continue.
When the installation has been completed, click Finish to exit the Wizard.
To check everything is ok go to the management console, using a supported browser, at the following url (if the default port has been used):
http://Managent Server FQDN or IP Address:60001/login