PernixData FVP® 3.

5 and
PernixData Architect™ 1.1
Installation Guide (New
Installations)
Version 1
Table of Contents
About This Guide ....................................................................................................................... 7
Intended Audience ..................................................................................................................... 7
Contacting PernixData ............................................................................................................... 7
Support .................................................................................................................................. 7
Feedback ............................................................................................................................... 7
Product Description ................................................................................................................... 7
Trademarks and Legal Information ............................................................................................ 8
Terminology ............................................................................................................................... 8
Introduction ................................................................................................................................ 9
What Are FVP and Architect?................................................................................................. 9
New in the 3.5 Release .........................................................................................................10
FVP and Architect Components ............................................................................................11
Installing FVP and Architect Overview ......................................................................................11
Verify Installation Prerequisites .................................................................................................13
General Installation Prerequisites ..........................................................................................13
Verify Host Extension Module Installation Prerequisites ........................................................14
Verify Windows-Based Management Server Installation Prerequisites ..................................16
Verify Management Server Appliance Installation Prerequisites ............................................23
Installing the Host Extension Module ........................................................................................26
Installing the Management Server and Management CLI Tools ................................................30
Windows-Based Management Server Installation .................................................................30
vCenter Server Logon: vCenter is in the Same Domain as Management Server ................................ 37
vCenter Server Logon: vCenter is in a Different Domain Than Management Server ......................... 38
Verify the Account .............................................................................................................................. 40
Management Server Virtual Appliance Installation (Deployment and Configuration) .............47
Deploying the Management Server Appliance ................................................................................... 49
Configuring the Management Server Appliance................................................................................. 61
Accessing the Management Server Appliance Configuration Pages After Initial Configuration ........ 69
Additional Options After Initial Management Server Appliance Configuration ................................. 70
Enabling and Disabling SSH Access ..................................................................................................... 72
Read-Only Database Access from Remote Computers ....................................................................... 75
Root Password Access ......................................................................................................................... 76
Password Recovery (Lost Password) ................................................................................................... 77

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 2 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Appendix A: Hardware and Software Prerequisites for FVP ......................................................78
ESXi Host Configuration Requirements and Recommendations ...........................................78
Windows-Based Management Server Configuration .............................................................79
Requirements and Compatibility ............................................................................................79
Firewall Settings ....................................................................................................................81
Supported Hardware .............................................................................................................82
Supported Software...............................................................................................................83
Configuration Maximums .......................................................................................................84
Path Selection Policies (FVP)................................................................................................84
Appendix B: Configure the Web Browser for the Management Console ...................................85
Microsoft Internet Explorer (10.0 or Later) .............................................................................86
Google Chrome .....................................................................................................................87
Mozilla Firefox .......................................................................................................................88
Appendix C: How to Access the Management Console ............................................................89
Log On Using a Web Browser ...............................................................................................89
Log On Using a vSphere Web Client .....................................................................................91
Appendix D: Connecting the Management Server Appliance to an Existing Microsoft SQL
Server Database.......................................................................................................................95
Appendix E: Related Documentation ........................................................................................98
PernixData Guides ................................................................................................................98
Selected PernixData Support and KB Documentation ...........................................................99
Selected Third-Party Documentation ...................................................................................100

List of Figures
Figure 1: Verify the ESXi Version............................................................................................14
Figure 2: Check for Previous Versions of the Host Extension Module .....................................15
Figure 3: Verify Memory and vCPU Allocation ........................................................................18
Figure 4: Verify the Windows Server Version ..........................................................................19
Figure 5: Verify the .NET Framework Version .........................................................................20
Figure 6: Verify TCP/IP is Enabled .........................................................................................21
Figure 7: Configure Secure Shell Access................................................................................27
Figure 8: Start Secure Shell Access .......................................................................................27
Figure 9: Insufficient Resources Warning ...............................................................................31
Figure 10: Extracting the Setup File ........................................................................................32
Figure 11: The Welcome Page ...............................................................................................32

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 3 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 12: License Agreement Page .......................................................................................33
Figure 13: Destination Folder Screen......................................................................................33
Figure 14: Change Current Destination Folder Dialog Box......................................................34
Figure 15: Setup Type Screen ................................................................................................35
Figure 16: Custom Setup Options ...........................................................................................35
Figure 17: Custom Setup Installation Location ........................................................................36
Figure 18: vCenter Server Logon Information (vCenter Server in Same Domain as
Management Server) ..............................................................................................................37
Figure 19: Remote vCenter Server Logon Information (vCenter Server on Different Computer
than Management Server) ......................................................................................................39
Figure 20: Server Properties Dialog Box .................................................................................40
Figure 21: Database Server Screen (Example 1) ....................................................................41
Figure 22: Database Server Screen (Example 2) ....................................................................41
Figure 23: The Network Port Settings Page ............................................................................43
Figure 24: Licensing Screen ...................................................................................................45
Figure 25: Ready to Install Screen ..........................................................................................45
Figure 26: Installing the Management Server..........................................................................46
Figure 27: The Installation Complete Page .............................................................................46
Figure 28: Error Message Seen If the VI Client Is Connected Directly to ESXi Hosts..............48
Figure 29: Select the vCenter Cluster .....................................................................................49
Figure 30: OVF Template Deployment....................................................................................49
Figure 31: The Source Dialog Box ..........................................................................................50
Figure 32: The PernixData Management Server OVA File ......................................................50
Figure 33: OVA File Source Location ......................................................................................51
Figure 34: The OVF Template Details Screen ........................................................................51
Figure 35: The Name and Location Screen ............................................................................52
Figure 36: The Deployment Configuration Screen ..................................................................53
Figure 37: Specify a Host........................................................................................................54
Figure 38: The Storage Screen ...............................................................................................55
Figure 39: The Disk Format Screen ........................................................................................56
Figure 40: The Networking Properties Screen ........................................................................57
Figure 41: Management Server VM Does Not Power On If Network Properties Are Not
Specified.................................................................................................................................58
Figure 42: The Edit Settings… Option.....................................................................................58
Figure 43: Setting Networking Properties Using the VI Client Edit Settings… Option ..............59
Figure 44: Power On the Management Server VM..................................................................59
Figure 45: Start the Deployment .............................................................................................60

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 4 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 46: Deployment Progress Bar ......................................................................................61
Figure 47: Successful Deployment .........................................................................................61
Figure 48: The Recent Tasks Area of the vSphere Client .......................................................61
Figure 49: Point the Browser to the Static IP Address of the Management Server Appliance .62
Figure 50: The Your Connection is Not Private Screen ...........................................................62
Figure 51: The Your Connection is Not Private Screen Advanced Options .............................63
Figure 52: The End User License Agreement (EULA).............................................................63
Figure 53: The PernixData Management Appliance Configuration Login Screen ....................64
Figure 54: The PernixData Management Server Appliance Configuration Screen ..................65
Figure 55: The Network Settings Screen ................................................................................65
Figure 56: Proxy Settings (Network Settings Screen) .............................................................66
Figure 57: The Time Screen ...................................................................................................67
Figure 58: The Appliance Credentials Screen .........................................................................67
Figure 59: The Configuration Complete Screen ......................................................................68
Figure 60: The Management Console Login Screen ...............................................................69
Figure 61: The Global Settings Tab Appliance Configuration Page.........................................70
Figure 62: The Services Screen..............................................................................................71
Figure 63: Selecting a Service Activates the Appropriate Options...........................................71
Figure 64: The Management Console Screen in the Appliance Configuration.........................72
Figure 65: The Access Screen ................................................................................................72
Figure 66: Enable SSH Access (Management Server Appliance) ...........................................73
Figure 67: SSH Changes Saved Confirmation ........................................................................73
Figure 68: Opening TCP Port 5432 to Enable Remote Read-Only Access .............................75
Figure 69: Using Remote Read-Only Access to Connect to the Management Server
Appliance ................................................................................................................................76
Figure 70: The Management Server Appliance Configuration Page Login ..............................77
Figure 71: Configuring Cookies in Internet Explorer ................................................................86
Figure 72: Allow Cookies in Chrome .......................................................................................87
Figure 73: Configuring Cookies in Firefox ...............................................................................88
Figure 74: Management Console Logon Screen .....................................................................90
Figure 75: The PernixData Dashboard....................................................................................91
Figure 76: The vSphere Web Client Logon Screen .................................................................91
Figure 77: Accessing the PernixData Management Console in the vSphere Web Client ........92
Figure 78: Security Exception Dialog Box ...............................................................................92
Figure 79: The PernixData Home Page ..................................................................................93
Figure 80: The FVP Dashboard in the vSphere Web Client ....................................................94

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 5 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
List of Tables
Table 1: PernixData FVP Terminology ..................................................................................... 8
Table 2: Minimum Dedicated Resource Requirements for the PernixData Management
Server VM ..............................................................................................................................17
Table 3: Minimum Dedicated Resource Requirements for the PernixData Management
Server Appliance ....................................................................................................................25
Table 4: Deployment Sizes and Required Resources .............................................................53
Table 5: FVP Firewall Settings ................................................................................................81
Table 6: FVP Supported Hardware .........................................................................................82
Table 7: FVP Supported Software ..........................................................................................83
Table 8: FVP Path Selection Policies ......................................................................................84

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 6 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
About This Guide
Version 1, June 8, 2016.

The PernixData FVP® 3.5 and PernixData ArchitectTM 1.1 Installation Guide provides instructions for
installing PernixData FVP and PernixData Architect software, including the new Management Server
Appliance. This guide provides instructions only for new installations of FVP 3.5 and Architect 1.1. Please
refer to the PernixData FVP 3.5 and Architect 1.1 Upgrade Guide to upgrade from a previous version.

Intended Audience
This guide is intended for anyone who wants to install the PernixData FVP 3.5 and PernixData Architect
1.1 software. The information in this guide is written for experienced system administrators who are
familiar with VMware vSphere®.

Contacting PernixData
Support
Technical Support: visit the PernixData Support site at http://support.pernixdata.com (requires login).
Compatibility information: refer to the PernixData Support Matrix on the PernixData Support website.
Feedback
For feedback on PernixData products, send email to [email protected].
If you have questions, comments, or concerns about PernixData FVP documentation, email
[email protected].

Product Description
PernixData FVP is the world’s first, and only, enterprise-class, server-side storage intelligence platform
that is embedded in the hypervisor to provide reliable I/O performance enhancements to unmodified
virtual machines (VMs) on existing primary storage. PernixData FVP virtualizes server-side flash and
server RAM across all hosts, and connects the high-speed server-side resources into existing VM I/O
paths, to transparently reduce the IOPS burden on a storage system. Leverage PernixData’s FVP with
your existing primary storage deployments and manage them within the context of your familiar
hypervisor management tools.
PernixData Architect is the world’s first, and only enterprise-class, server-side storage intelligence
platform that is embedded in the hypervisor to provide real-time analytics (descriptive, predictive, and
prescriptive) for optimal storage and VM design. PernixData Architect is a proactive, strategic data
center management tool that continually generates new data based on dynamic VM and infrastructure
conditions. PernixData Architect is hardware-agnostic, so its single-pane-of-glass view across all data
centers can gather and analyze data from all hardware on VMware’s Hardware Compatibility List (HCL).
If you would like to know more about PernixData products, please see the frequently-asked questions
(FAQ) at http://www.pernixdata.com/products/faq.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 7 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Trademarks and Legal Information
Copyright © 2016 PernixData, Inc. All rights reserved. This product is protected by U.S. and international
copyright and intellectual property laws. For open source legal notices and trademarking information,
see the Legal Notices, Trademarks, Open Source Licenses Appendix in the latest version of the
PernixData FVP User Guide.
PernixData, FVP, the stylized X, and Flash Cluster are registered trademarks, and Architect is a trademark
of PernixData, Inc. in the United States and/or other jurisdictions. All other brands, products, marks and
names mentioned herein may be trademarks or service marks of, and are used to identify, products or
services of their respective owners.
VMware is a registered trademark of VMware, Inc. in the United States and other jurisdictions.
Microsoft is a registered trademark of Microsoft Corporation in the United States and other countries.
All other marks and names mentioned herein may be trademarks of their respective companies.

Terminology
Before installing the latest version of PernixData FVP or PernixData Architect, familiarize yourself with
the terms listed in Table 1.
Table 1: PernixData FVP Terminology

Term Definition

Flash Device A server-side PCIe or SSD storage device. Flash devices are also
referred to as flash storage.

FVP Cluster A cluster-wide pool of flash devices and/or server RAM created by
PernixData FVP. Virtual machines running on host computers
within a cluster can use this resource pool to dramatically
accelerate input/output operations.

PernixData Host Extension Module The PernixData component you install on an ESXi host computer.
To take advantage of the FVP acceleration resources, virtual
machines must be running on an ESXi host that has the Host
Extension Module installed.

PernixData Management Console The PernixData component that serves as a standalone UI for FVP
management and administration. You can also perform FVP
management tasks using the FVP module for Windows PowerShell.

PernixData Management Server The PernixData component that runs alongside VMware vCenter
and coordinates ESXi hosts and the PernixData Management
Console. When you issue a command in the Management Console
(or by using Windows PowerShell), the Management Server carries
out the command.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 8 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Introduction

This Installation Guide describes how to perform a new installation of PernixData FVP® 3.5 and
PernixData Architect TM 1.1 software and its components. This document does not apply to software
upgrades. In addition to fresh installation, the appendixes of this document describe:
● Hardware and software requirements
● Accessing the PernixData Management Console
● Related PernixData documentation (Upgrade Guide, Uninstallation Guide, Release Notes, etc.)
This section covers:
● What are FVP and Architect?
● New in the 3.5 Release
● Components of FVP and Architect

What Are FVP and Architect?

PernixData FVP and Architect is the latest version of PernixData FVP and Architect, software products
that dramatically increase performance in a VMware environment by allowing virtual machines to use
flash devices and server RAM to “accelerate” reads and writes. For example, when a VM issues a read
request, FVP can retrieve the data from a local acceleration resource (flash or RAM), a process that is
not only faster than retrieving the data from a datastore, but also reduces the amount of data traveling
across your network. Similarly, when a VM needs to write data, FVP can quickly write the data to a local
acceleration resource and receive acknowledgment that the operation was completed. As storage
resources allow, FVP copies the written data from the acceleration resource to the backend datastore.
PernixData Architect is a platform for data center design, deployment, operation, and optimization in a
VMware environment. Architect provides visibility across all data center elements (VMs, server-side
memory, datastores) by performing real-time, end-to-end analytics. Architect regularly generates data
based on dynamic virtual machine and infrastructure conditions, correlated with third-party data from
VMware vCenter, and provides design recommendations to optimize performance.
Architect is a data-driven, strategic, proactive operational tool that enables you to catch design issues
before they impact your data center, maximize application performance, and minimize the need for
troubleshooting. Instead of reacting to issues as with traditional management tools, Architect gives you
predictive and prescriptive analytics that enable you to act on recommendations to optimize the data
center before trouble occurs.
Architect and FVP work together to provide an integrated platform for real-time data center resource
and performance analysis and recommendations (Architect), and a way to execute the
recommendations (FVP).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 9 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
New in the 3.5 Release

This version of FVP and Architect software introduces a new way to install and configure the PernixData
Management Server. Prior to this release, the Management Server was available only as a Microsoft
Windows based server. This release introduces the PernixData Management Server Appliance, a
dedicated, self-contained virtual machine. You can install either version of the Management Server.
If you want to migrate from an existing Windows-based Management Server to the Management Server
Appliance and preserve your existing configuration and history database, you can connect the
Management Server Appliance to the existing Microsoft SQL Server Database, as described in Appendix
D: Connecting the Management Server Appliance to an Existing Microsoft SQL Server Database.

NOTE

You can uninstall the Windows-based Management Server and

then install the Management Server Appliance and avoid using the
SQL Server Database.
However, uninstalling the Management Server software loses the
configuration, so if you uninstall the Windows-based Management
Server, and then install the Management Server Appliance, you
need to reconfigure the FVP Clusters, acceleration resources,
VMs, and datastores. All reports and logs are also lost.
Connecting the Management Server Appliance to the existing SQL
Server Database preserves the configuration, reports, and logs.

The Management Server Appliance offers several advantages over the Windows-based Management
Server:
• Built-in, embedded database, so you don’t have to configure an SQL server.
• Easy customization of resources based on deployment size.
• Easier installation with fewer prerequisites.
• No need for Windows Server licenses or .NET Framework 3.5.1.
The Management Server Appliance does not include an option to install only the Management CLI Tools
instead of the full Management Server. (You might want to install just the Management CLI Tools for
managing FVP and Architect from a remote computer.) If you want to install the Management CLI Tools
on a management computer, download the Windows Management Server Installer and use the Custom
Installation option to install the Management CLI Tools on the management computer.
In addition to the Management Server Appliance, version 3.5 introduces:
• Support for accelerating VMs that use raw device mapping (RDM) disks.
• A new search box for FVP Clusters.
• More granular reporting on read and write operations.
For more information on these new features, refer to the FVP 3.5 and Architect 1.1 User Guide.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 10 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
FVP and Architect Components

Installation consists of the following three components:

● Host Extension Module. Software that enables virtual machines on a host to take advantage of
FVP’s acceleration capabilities. This software should be installed on each of your ESXi hosts.
● Management Server software. Software that coordinates the Host Extension Module and the
Management Console.
You can install the Management Server in either of two ways:
● Windows-based: The Management Server must be installed on a computer running
Windows Server 2008 or later (64-bit edition only). You can install the Management
Server in a virtual machine, so you don’t have to dedicate a physical server to FVP. We
strongly recommend that you install the Management Server in its own dedicated VM.
However, providing that you dedicate enough resources (RAM and vCPUs) to the
Management Server and to the other applications, you can install it in the same VM as
other applications.
● Self-contained virtual appliance: Install the Management Server Appliance using a
VMware OVA package, using the vSphere Client. Windows Server and an SQL database
do not need to be licensed and installed.
● Management Console. User interface, and primary management tool, for FVP and Architect. A
browser-based utility, the Management Console replaces the vSphere plugin that served as the
principal management tool in versions of FVP prior to FVP 3.0. With FVP 3.0 or later, you do not
need to install and configure the vSphere plugin.
This document explains how to install and configure each of these components. Appendix C: How to
Access the Management Console shows you how to log on to the Management Console. For version
compatibility information, see the PernixData Support Matrix on the PernixData Support website
(requires login).

Installing FVP and Architect Overview

The InstallShield Wizard installs the Windows-based version of PernixData FVP and PernixData Architect
Management Server, and the vSphere Client installs the PernixData Management Server Appliance.

NOTE

Deploying the Management Server Appliance VM is supported

only if the VI Client is connected to the vCenter Server. The VI
Client cannot be connected directly to individual ESX hosts or the
deployment fails. If you attempt to deploy the Management Server
to an ESX host, an error message is generated.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 11 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Both FVP and Architect are installed in one package. You cannot install or uninstall FVP and Architect
separately. You can license and activate each product separately. If you have a paid license, enter the
license key you received after you put in your purchase order when you activate the product.
You can also activate a 30-day trial of FVP or Architect. Before you start a 30-day trial, we strongly
recommend that you identify the resources (datastores, hosts, etc.) you want to use before you begin
the trial. We recommend this so that when you start the trial, you can spend the full 30 days trying out
the product, rather than spending time identifying resources and setting up your environment after the
trial period has started.
Including preparing for installation by verifying the installation prerequisites, installing FVP and Architect
is a three-step process:
1. Verify the installation prerequisites. Performing these steps before you upgrade the software
prepares your systems for the software installation and make the process go smoothly.

NOTE

If PernixData software is already installed, do not use the process

documented in this installation guide. Instead, use the upgrade
process described in the PernixData FVP 3.5 Upgrade Guide, or
first uninstall the current software as described in the PernixData
FVP and Architect Uninstallation Guide.

2. Install the Host Extension Module on all of the ESXi hosts.

3. Install the Management Server. There are two ways to install the Management Server: you can
install it as Windows executable (Windows-Based Management Server Installation), or as a
virtual appliance (Management Server Virtual Appliance Installation (Deployment and
Configuration)). Installing the Management Server as a Windows executable requires a
computer running Windows Server 2008 or Windows Server 2012.
In addition, your web browser must allow the use of cookies, as described in Appendix B: Configure the
Web Browser for the Management Console.
This document describes each of these procedures step-by-step.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 12 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 NOTE

In FVP 3.0 and later releases, you manage PernixData software

using the browser-based Management Console. Optionally, you
can still install the PernixData vSphere VI Client plugin or the
PernixData vSphere Web Client plugin. However, you can access
only a limited amount of basic information in these clients, and you
cannot configure the software in them.
If you access the Management Server using one of the plugins,
when you log in, you see a link to the PernixData Management
Console. Click the link to open the Management Console in a
standalone browser window. In the Management Console, you can
access all of the FVP and Architect information, and configure the
software. Most management activities require using the
Management Console.

Verify Installation Prerequisites

Before you install the software, verify the prerequisites and requirements in this section. Appendix A
provides a comprehensive list of hardware and software compatibility, requirements, and
recommendations. This section covers common prerequisites to verify for software installation,
organized in four subsections:
● General installation prerequisites
● PernixData Host Extension Module installation prerequisites
● Verify Windows-Based Management Server Installation Prerequisites
● Verify Management Server Appliance Installation Prerequisites
To prevent surprises and make installation go smoothly, we recommend that you perform all
prerequisites for installation before you begin the actual installation procedure.

General Installation Prerequisites

General installation prerequisites apply to the entire installation process, rather than to one phase of
installation. These requirements apply to installing the PernixData Management Server either as a
Windows executable or as a virtual appliance.
1. Verify that all your hosts are running ESXi 5.1, 5.5, or 6.0.

NOTE

FVP 3.5 and Architect 1.1 do not support ESXi 5.0.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 13 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 In the vSphere Client, verify the version of ESXi installed on a host by first selecting the host
from the vCenter inventory. Then, on the Summary tab, scroll down until you find the entry for
Image Profile. If you cannot read the value for the Image Profile property, hover the mouse
pointer over the value (Figure 1); the complete value is displayed in a tooltip.
Figure 1: Verify the ESXi Version

2. FVP hosts must be part of a vCenter cluster. FVP does not support use on standalone ESXi hosts
that are not members of a vSphere Cluster.
3. Before you install the software, VMware vCenter must be up and running.
4. PernixData software supports only ESXi hypervisors.
5. Verify that your web browser:
• Allows the use of cookies as part of its authentication mechanism. Appendix B shows
you how to set Microsoft Internet Explorer, Google Chrome, and Mozilla Firefox to allow
using cookies.
• Allows JavaScript and transport layer security (TLS).
• Allows popups. Disable the popup blocker to open the Management Console from inside
the vSphere Web Client.

Verify Host Extension Module Installation Prerequisites

Host Extension Module installation prerequisites apply to the first part of the installation procedure,
which is installing the Host Extension Module on all of the ESXi hosts. (To use the FVP fault-tolerant
Write Back acceleration feature, the Host Extension Module needs to be installed on all hosts because
you can use Write Back mode only on hosts that run the Host Extension Module. In addition, datastores
used with FVP must be on hosts that run the Host Extension Module.)
Regardless of the method you choose to install the PernixData Management Server (Windows
executable or virtual appliance), Host Extension Module installation is the same.
Verify that all flash devices and all applicable drivers and software are already installed on your hosts.
Do not install the Host Extension Module until the host storage, drivers, and software are ready.
1. Verify that the flash devices on the hosts do not contain partitions. FVP does not support
partitioned flash devices. FVP requires exclusive access to each flash device allocated to FVP.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 14 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Server-side flash memory cannot be used partly by FVP and partly by another application. See
VMware KB 1036609 for instructions on deleting partitions from a flash device.
2. This document is intended for new installations only. To verify that the host does not have a
previous version of the Host Extension Module installed, run the following command (the
PernixData installer does not overwrite the Host Extension Module, so no older version of the
Host Extension Module can reside on the hosts before installation):
esxcli software vib list | grep –i pernix
If the command returns no data, there is no previous version of the Host Extension Module
installed, so you can skip the rest of this step. However, if you see output with a vendor entry
for PernixData similar to Figure 2, a previous version of the Host Extension Module is installed.
Figure 2: Check for Previous Versions of the Host Extension Module

Uninstall the previous version by running the following command:

cp /opt/pernixdata/bin/prnxuninstall.sh /tmp/ &&
/tmp/prnxuninstall.sh
This command copies and runs the script prnxuninstall.sh, a script that removes all instances of
the Host Extension Module.
Uninstalling the Host Extension Module is critical: the Host Extension Module cannot overwrite
any prior instance of the Host Extension Module. If you try to overwrite an existing instance of
the Host Extension Module, the command fails with the following error message:
[InstallationError]
Error in running rm /tardisks/pernixco.v00:
Return code: 1
Output: rm: can't remove '/tardisks/pernixco.v00': Device or
resource busy
It is not safe to continue. Please reboot the host immediately to
discard the unfinished update.
Please refer to the log file for more details.
Despite the error message, it is safe to continue, and you do not need to reboot the host.
Instead, use prnxuninstall.sh to uninstall the older version of the Host Extension Module, then
try again to install the new Host Extension Module.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 15 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Verify Windows-Based Management Server Installation Prerequisites

NOTE

Verify these prerequisites only if you choose to use the Windows-

based Management Server. If you plan to deploy the Management
Server Virtual Appliance, skip ahead to Verify Management Server
Appliance Installation Prerequisites.

Windows-based Management Server installation prerequisites apply to the second part of the
installation procedure, which is installing the Management Server software on the appropriate server or
in the appropriate VM (if you are not installing the Management Server Appliance).
Verify that you have a vCenter account you can use to run the PernixData Management Server service
and access the PernixData Management Server database. To make both installation and management as
easy as possible, we strongly recommend that you use the same account to:
● Install the FVP and Architect PernixData Management Server
● Run the Management Server service
● Log on to SQL Server
Although you can use multiple accounts for these tasks, that might complicate installation and
maintenance of FVP. The Management Server account can be either an Active Directory account or a
local computer account, and must:
● Have local administrator rights on the computer on which you install the Management Server.
This must include the right to log on locally.
● Have appropriate privileges for vCenter.
● Have database owner (DBO) permissions to the SQL Server database FVP will use.
● Be able to run the FVP Management Server service.
1. As a best practice, the Management Server is usually installed in a VM instead of on a physical
server (this enables moving the Management Server application easily if the physical host server
needs maintenance and makes management easier). If you install the Management Server on a
physical server, maintenance on the physical server can cause an interruption of service.
If you install the Management Server on a physical server, ensure that the Management Server
has been allocated at least 8 GB of free RAM.
If you install the Management Server in a VM, verify that you allocate enough dedicated
resources to the Management Server VM to support your vSphere environment, as shown in
Table 2. By dedicated resources, we mean that if other applications run in the same VM, the
minimum resource requirements shown in Table 2 are in addition to the resources allocated to

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 16 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 any other application running in the VM. The recommended minimum amount of resources to
dedicate to the Management Server depends on the size of your vSphere environment.
Table 2: Minimum Dedicated Resource Requirements for the PernixData Management Server VM

vSphere Environment Minimum Dedicated VM RAM vCPUs

Tiny (1-5 hosts or 1-50 VMs) 4 GB 2

Small (6-100 hosts or 51-1000 VMs) 8 GB 4

Medium (101-400 hosts or 1001-4000 VMs) 12 GB 8

Large (more than 400 hosts or 4000 VMs) 16 GB 16

NOTE

We recommend that you run the Management Server in a

dedicated VM. If you decide to run the Management Server in the
same VM as the SQL database, add at least 1 GB to the VM RAM
requirements (and more memory is always better).

We recommend that you install the Management Server in its own dedicated virtual machine.
Because of resource requirements and consumption, we recommend that you do not install the
Management Server in the same virtual machine as vCenter.
In the vSphere Client, verify the resources allocated to a virtual machine by right-clicking the VM
in the vSphere inventory, and then clicking Edit Settings. In the Virtual Machine Properties
dialog box, on the Hardware tab, verify the values for Memory and CPUs (Figure 3).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 17 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 3: Verify Memory and vCPU Allocation

If you need to modify these values, power off the VM and then click Edit Settings to bring back
up the Virtual Machine Properties dialog box. You cannot change memory and CPU allocations
while a VM is powered on.

2. Verify that the server on which you install the Management Server is running a 64-bit version of
Windows Server 2008 or Windows Server 2012.
To verify that your version of Windows Server meets the PernixData software requirements,
click Start, right-click Computer, and then click Properties. The resulting dialog box (Figure 4)
shows the operating system version and the operating system type (32-bit or 64-bit).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 18 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 4: Verify the Windows Server Version

3. Verify that the server on which you install the Management Server is running .NET Framework
3.51 Service Pack 1 or later.
To verify that the required version of the .NET Framework is installed, click the Server Manager
icon in the Windows Server toolbar, or type ServerManager.msc in the Run dialog box.
In Server Manager, click Features, and then look for the entry for the .NET Framework. The
listed version must be 3.5.1 or later (Figure 5).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 19 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 5: Verify the .NET Framework Version

4. Verify that Microsoft SQL Server 2008, Microsoft SQL Server 2012, or Microsoft SQL Server 2014
(any edition) is already installed, and that TCP/IP is enabled.

NOTE

Note the location of the SQL server instance where you will install
the Management Server. If you want to specify a non-default TCP
for the SQL Server, see PernixData KB article 1216 on the
PernixData Support website (requires login).

The PernixData Management Server requires Microsoft SQL Server 2008, 2012, or 2014. If you
do not have an existing instance of SQL Server that can host the PernixData Management Server
database, to save money, PernixData recommends installing Microsoft® SQL Server® Express
2012. (You can download a free copy of SQL Server Express here.) To perform a default
installation of SQL Server Express, run the following command from the directory where the
installer executable is located (this example installs SQL Server using the instance name
PRNX_SQLEXP):

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 20 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Setup.exe /ACTION=install /IACCEPTSQLSERVERLICENSETERMS
/SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /HIDECONSOLE /QS
/FEATURES=SQL /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS"
/NPENABLED="1" /TCPENABLED="1" /INSTANCENAME=PRNX_SQLEXP
You can find more information on the command-line installation of SQL Server (including
information about the individual command-line switches) here.
To verify that TCP/IP has been enabled, start the Sql Server Configuration Manager. When the
Configuration Manager appears, expand SQL Server Network Configuration, and then click the
Protocols heading for the SQL Server instance where you will install the FVP management
database. In the right pane of the Configuration Manager, verify that TCP/IP is set to Enabled
(Figure 6).
Figure 6: Verify TCP/IP is Enabled

If TCP/IP is not enabled, right-click TCP/IP and click Enable.

NOTE

You must enable the SQL Server TCP/IP protocol even if the
database is installed locally. Without TCP/IP enabled, the
Management Server might not be able to connect to and
communicate with the database.

You can find additional details on enabling TCP/IP using the SQL Server Configuration Manager
here. If you are using SQL Server Express and do not have a copy of the Configuration Manager
you can download a copy of the SQL Server Express Management Studio from the Microsoft
Download Center.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 21 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 If you are using an SQL Named Instance, make sure that the SQL Browser Service is enabled and
running. More information about the Browser Service is available here.

5. Configure SQL Server to use Windows authentication.

If you configure SQL Server to use Windows authentication and if you also follow our
recommendation to use the same account for Management Server installation, running the
Management Server service, and logging on to SQL Server, then you can leave the Windows
authentication credentials of the user who is installing (or who will install) the PernixData
software selected.
If your instance of SQL Server does not use Windows authentication or if you want to use a
different account to log on to SQL Server, select SQL Server Authentication, and then type in
the login and password information.

NOTE

If you use SQL Server authentication instead of Windows

authentication, you must use an SQL Server account that already
exists, because the PernixData setup program cannot create it for
you.
The authentication account you use must have sysadmin
privileges.

6. Note the location of your vCenter Server. The PernixData Installation Wizard needs to log onto
the vCenter Server to complete the setup.

NOTE

If you have multiple vCenters, you need to install a separate

instance of PernixData Management Server for each vCenter.

7. Prevent the database transaction log file from growing too large and using too much disk space
either by configuring the database to use simple recovery mode or by scheduling the database
for regular full backups.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 22 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Verify Management Server Appliance Installation Prerequisites

NOTE

Verify these prerequisites only if you choose to use the virtual

appliance based Management Server. If you plan to deploy the
Windows-based Management Server, see the prerequisites in
Verify Windows-Based Management Server Installation
Prerequisites.

The prerequisites for installing the Management Server Appliance are fewer and easier than the
prerequisites for installing the Windows-based Management Server. These prerequisites apply to the
second part of the installation procedure, which is installing the Management Server Appliance (if you
are not installing the Windows-based Management Server).
1. Verify that you have a vCenter account to connect to the vCenter Server. This account must
have administrator access to the root of vCenter.
2. Verify that the VI Client is connected only to the vCenter Server. If the VI Client is connected
directly to an ESXi host, the deployment fails and generates an error message.
3. If a previous version of the Windows-based Management Server is installed, you must uninstall
it before you install the Management Server Appliance (see the PernixData FVP and Architect
Uninstallation Guide).

NOTE

Uninstalling the Management Server software loses the

configuration, so if you uninstall the Windows-based Management
Server, and then install the Management Server Appliance, you
need to reconfigure the FVP Clusters, acceleration resources,
VMs, and datastores. All reports and logs are also lost.

4. During installation and configuration, the installer asks for settings that you should have handy
before you begin configuring the Management Server Appliance:
• The location (IP address or DNS name) of your vCenter Server. The installer needs to log
onto the vCenter Server to complete the setup.

NOTE

If you have multiple vCenters, you need to install a separate

instance of the PernixData Management Server for each vCenter.
If the vCenters are in Linked Mode, then you need to launch the
Management Console using the vCenter Web Client.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 23 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • Static IP Address to assign to the Management Server Appliance. A static IP address is
required to run the Management Server service. You cannot use a dynamic IP address (for
example, do not use an address assigned by a DHCP server). Be sure to obtain a static IP
address for the Management Server Appliance before you begin the installation.
• Subnet mask
• Default gateway address
• DNS server name and IP address

NOTE

Be sure to add an entry to your DNS server to map the DNS entry
for the hostname to the IP address. This enables you to specify
the name instead of the IP address because the DNS server will
be able to resolve the hostname.

• Proxy server settings to enable PernixPlus (IP address and port, and the username and
password if authentication is required). If the machine on which you deploy the
Management Server Appliance is behind a proxy server and does not have a direct
connection to the Internet, then you need to specify the proxy server settings to support
online licensing.

NOTE

PernixPlus collects anonymous, relevant deployment data to

identify potential problems before they happen, and to decrease
the time it takes to solve issues.

5. A feature of the Management Server Appliance is that you select your deployment size during
configuration. The deployment size determines the amount of resources dedicated exclusively
to FVP that are required to support the deployment. The Management Server automatically
assigns the required resources to the deployment if the resources are available. However, the
Management Server Appliance cannot ensure that the required resources exist on the physical
host. If there are not enough host resources to support the deployment, then when you start
the Management Server Appliance VM, a message pops up to let you know the deployment
requires more resources.
Ensure that the resources required for the size of your deployment are available on the physical
host. Table 3 shows the resources required for different deployment sizes.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 24 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Table 3: Minimum Dedicated Resource Requirements for the PernixData Management Server Appliance

Minimum Dedicated Disk Size

vSphere Environment vCPUs
VM RAM (Thick)*

Tiny (1-5 hosts or 1-50 VMs) 4 GB 2 100GB

Small (6-100 hosts or 51-1000 VMs) 8 GB 4 100GB

Medium (101-400 hosts or 1001-4000 VMs) 12 GB 8 100GB

Large (more than 400 hosts or 4000 VMs) 16 GB 16 100GB

* You can configure the disk size as “thin” so that the disk size starts out small and grows only as
needed.
If you select the wrong vSphere environment size during Management Server Appliance VM
configuration, or if you want to change the resource allocation for the VM, you can change the
allocated amount of RAM and number of vCPUs manually using your vSphere Client.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 25 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Installing the Host Extension Module
Before you install the software, VMware vCenter must be up and running. Installing the Host Extension
Module is the same regardless of whether you install the Windows-based Management Server or the
Management Server Appliance.
We recommend that all of your ESXi hosts run the same version of the Host Extension Module. As with
previous versions of FVP, we strongly recommend that you install the Host Extension Module on all the
hosts in an FVP Cluster to help ensure that you can use and gain the greatest benefit from all of the
features and capabilities of the software. (To use the FVP fault-tolerant Write Back acceleration feature,
the Host Extension Module must be installed on all hosts. In addition, datastores used with FVP must be
on hosts that run the Host Extension Module.)
For example, to create an FVP Cluster within a vCenter cluster named San Jose, install the Host
Extension Module on each host in the San Jose cluster.
If you did not perform the following steps from the Verify Host Extension Module Installation
Prerequisites section, then before you begin the Host Extension Module installation procedure, follow
the steps in the prerequisites verification section to ensure that:
● Flash devices and all applicable drivers and software are installed on your hosts.
● Flash devices do not contain partitions. FVP does not support partitioned flash devices.
● No earlier version of the Host Extension Module resides on your hosts. Because the installation
program does not overwrite previous versions of the Host Extension Module software, no
previous version can reside on a host. This procedure in this document is for new installs only.
You can install the PernixData Host Extension Module in one of two ways:
• Using VMware Update Manager (VUM)
• Using esxcli
You can install the Host Extension Module using VMware Update Manager (VUM), providing that you
have the appropriate offline bundle. If you do not use VUM to upgrade the Host Extension Module, then
follow the steps in this section to install the software using esxcli. If you are unfamiliar with using VUM
and you have access to the PernixData support portal (requires login), the PernixData Knowledge Base
article Host Extension Installation and Upgrade Using VMware Update Manager (VUM) here describes
how to install the Host Extension Module using VUM. The PernixData Knowledge Base video (requires
login) also shows how to install the Host Extension Module using VUM here.
This section describes the process of installing the Host Extension Module using esxcli.
Install the Host Extension Module by completing the following procedure on each VMware host:
1. Use the Direct Console UI or the vSphere Client to enable the ESXi Shell or SSH access for host
CLI configuration.
In the vSphere Client, enable shell access by selecting the host, clicking the Configuration tab,
and then clicking Security Profile. In the Security Profile pane, click the Properties link next to
Services to display the Service Properties dialog box (Figure 7).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 26 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 7: Configure Secure Shell Access

In the Services Properties dialog box, select ESXi Shell and then click Options. In the ESXi Shell
(TSM) Options dialog box (Figure 8) select a Startup Policy, click Start, and then click OK. (Be
sure you click Start: otherwise the service is configured but not enabled.)
Figure 8: Start Secure Shell Access

Use the same process to configure and enable the SSH (secure shell) service.
For more information, see VMware KB 2004746.
2. Copy the PernixData host extension file for your version of ESXi to a shared location accessible
to all the hosts in the vSphere Cluster, or to each host in the FVP Cluster. The .ZIP file includes
the vSphere version number in the file name. For example, the host extension file for vSphere
5.5 has a file name similar to the following:

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 27 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 PernixData-host-extension-vSphere5.5.0_3.5.0.0-xxxxx.zip

You can copy the host extension file to each host using a command such as scp (secure copy).
Alternatively, you can place the .ZIP file on a datastore that all the hosts can access.
3. Use the ESXi Shell or another secure shell utility (such as PuTTY) to log on to the host as a root
user.
4. Put the host into Maintenance Mode from the VI Client or from the web Client by right-clicking
on the host, and then selecting Enter Maintenance Mode.

You can put the host into Maintenance mode from the esxcli using the command esxcli
system maintenanceMode set –e true. However, this is not recommended because
if VMs are running on the host, the CLI command fails, so to put the host in Maintenance Mode
from the CLI, you have to first power off, suspend, or migrate the running hosts.

If a host is not in Maintenance Mode, you cannot install the Host Extension Module. Instead,
installation fails with the error message:

Cannot uninstall PernixData VIB outside of host maintenance mode

Please put the host in maintenance mode first

Verify if a host is in Maintenance Mode by running the following command:

esxcli system maintenanceMode get

If this command returns the result Enabled, then the host is already in Maintenance Mode. If
the command returns the result Disabled, then the host is not in Maintenance Mode. (Disabled
means that Maintenance Mode is disabled and is not running.)

5. Use the following esxcli command to install the PernixData Host Extension Module. Be sure to
replace <.ZIP file name with full path> with the full path to your host extension .ZIP file:
esxcli software vib install -d <.ZIP-file-name-with-full-path>
For example, if you copy the host extension file to the /tmp directory on the host, use a
command similar to the following:
esxcli software vib install-d /tmp/PernixData-host-extension-
vSphere5.5.0_3.5.0.0-XXXXX.zip
In the preceding command, vib is short for vSphere Installation Bundle, and refers to a host
extension file. vSphere vibs are .ZIP archives that contain setup files, an XML descriptor file, and
an electronic signature file.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 28 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 6. Backup the ESXi configuration settings device using the following command:
/sbin/auto-backup.sh

IMPORTANT

If you accidentally install the wrong Host Extension Module (for

example, if you inadvertently install the Host Extension Module for
PernixData FVP 2.5), then you must remove the incorrect Host
Extension Module before you can install the correct version. As
mentioned previously, you can remove the PernixData Host
Extension Module from a computer by running the prnxuninstall.sh
script:

cp /opt/pernixdata/bin/prnxuninstall.sh /tmp/ &&

/tmp/prnxuninstall.sh

7. Run the following command to remove the host from maintenance mode:
esxcli system maintenanceMode set -e false
8. Terminate your existing shell session, and repeat the procedure for each remaining host.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 29 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Installing the Management Server and Management CLI Tools
Before you install the software, VMware vCenter must be up and running. You can install the PernixData
Management Server in two ways:
• As a Windows-based program.
• As a virtual appliance.

Windows-Based Management Server Installation

Windows-based Management Server installation is similar to installing previous versions of FVP. Default
installation includes the Management Server and the Windows PowerShell Management CLI Tools. You
can also choose a custom installation. Custom installation is useful for installing just the Management
CLI Tools on a laptop computer to use Windows PowerShell to manage FVP and Architect.
If you did not perform the following steps from the Verify Windows-Based Management Server
Installation Prerequisites section, then before you begin the Management Server installation procedure,
follow the steps in the prerequisites verification section to ensure that:
● The Management Server VM has been allocated enough exclusively dedicated RAM and vCPU
resources, as shown in Table 2.
● If you install the Management Server in a VM, we recommend that you install it in a VM that is
dedicated to the Management Server. Because of resource requirements, we recommend that
you do not install the Management Server in the same VM as vCenter. Although we recommend
a dedicated VM for the Management Server, if you install the Management Server in the same
VM as the SQL Server instance it uses, we recommend that you add at least more 1 GB of RAM
to the VM.
● The server on which you install the Management Server is running a 64-bit version of Windows
Server 2008 or Windows Server 2012.
● The server on which you install the Management Server is running .NET Framework 3.51 Service
Pack 1 or later.
● Microsoft SQL Server 2008, Microsoft SQL Server 2012, or Microsoft SQL Server 2014 (any
version) is already installed, and that TCP/IP is enabled.
● SQL Server uses Windows authentication.
If you install the Management Server on a server that does not allocate sufficient resources to the
Management Server, the Management Server warns you that you need to allocate more resources after
you complete the installation (Figure 9).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 30 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 9: Insufficient Resources Warning

From completing the steps in the Verify Windows-Based Management Server Installation Prerequisites
section, you should know:
● The location of your vCenter Server. The Installation Wizard needs to log on to vCenter to
complete the setup. If you have multiple vCenters, you need to install a separate instance of the
Management Server for each vCenter.
● The location of the SQL Server instance on which you will install the Management Server
database. To make both installation and management easier it is recommended that the
database be installed on the same server as the Management Server itself.

To install the Management Server, complete the following procedure:

1. Double-click the installation file. The installation file name is similar to PernixData FVP
Management Server - 3.5.XXXXX.0.exe, depending on the build number. Make sure that the file
name includes the version number 3.5, for example:
PernixData FVP Management Server – 3.5.XXXXX.0.exe
After you double-click the installation file, click Run to run the installation program, and then
wait for the Installation Wizard to extract the setup file (Figure 10).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 31 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 10: Extracting the Setup File

2. When the Installation Wizard Welcome page appears (Figure 11), click Next.
Figure 11: The Welcome Page

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 32 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 3. On the License Agreement page (Figure 12), read the license agreement, select I accept the
terms in the license agreement, and then click Next. You must accept the license agreement to
continue.
Figure 12: License Agreement Page

4. On the Destination Folder screen (Figure 13), click Next to install the Management Server in the
default folder (C:\Program Files\PernixData\Management Server). If you’d prefer to install the
Management Server in a different folder, click Change.
Figure 13: Destination Folder Screen

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 33 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 If you choose to install the Management Server in a different folder, use the Change Current
Destination Folder dialog box (Figure 14) to select the folder, and then click OK. When setup
returns you to the Destination Folder page, click Next.
Figure 14: Change Current Destination Folder Dialog Box

5. To install both the Management Server and the Management command-line interface (CLI) tools
(including the PernixData Windows PowerShell module), on the Setup Type page (Figure 15),
select Complete setup, and then click Next. We strongly recommend that you install the
Management CLI Tools along with the Management Server. Use Custom setup to install just the
management tools on a management computer (for example, an administrator’s laptop
computer).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 34 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 15: Setup Type Screen

Custom setup (Figure 16) provides three options.

Figure 16: Custom Setup Options

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 35 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 You can install:
• Just the management tools. You can install just the Management CLI Tools on an
administrator’s computer to manage PernixData applications from a computer that does
not have the Management Server installed. This is the reason you might use custom
installation. To run the PernixData PowerShell commands, you must install the
Management CLI Tools, which includes the PernixData PowerShell module, on the
computer.
• Just the Management Server. This is not recommended because there is no reason not
to install the Management CLI Tools with the Management Server.
• Both the Management Server and the Management CLI Tools. This is equivalent to doing
a Complete setup.
If you perform a custom setup, make sure you select This feature, and all sub-features, will be
installed on local hard drive when choosing the items to install, as shown in Figure 17.
Figure 17: Custom Setup Installation Location

6. On the VMware vCenter Server Logon Information screen, specify the name of your vCenter
Server, and the account name and password for the Management Server service.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 36 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 In the VMware vCenter Server field, specify the location of the vCenter Server.

NOTE

Because of resource requirements and consumption, we strongly

recommend that you do not install the vCenter Server and the
Management Server in the same VM. If you install the vCenter
Server and Management Server in the same VM, allocate enough
dedicated resources to the Management Server (see Table 2).

The vCenter Server can be in the same domain as the PernixData Management Server or in a
different domain than the Management Server. If the vCenter Server is in a different domain, to
run the Management Server using a local account from a remote vCenter Server, check the Run
PernixData Management Server Service as “Local System” checkbox.
This step shows you how to configure the vCenter Server when it is in the same domain as the
Management Server, and shows you how to configure the vCenter Server when it is in a
different domain than the Management Server. This step also shows you how to verify the
account the Management Server service runs under, if necessary.

vCenter Server Logon: vCenter is in the Same Domain as Management Server

If you install the Management Server in the same domain as the vCenter Server, enter the fully
qualified domain name or IP address in the VMware vCenter Server field (Figure 18).
Figure 18: vCenter Server Logon Information (vCenter Server in Same Domain as Management Server)

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 37 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 In the Account name box, enter the name of the domain user under whom the Management
Server will run. In the Account Password box, enter the password for that account.
When the vCenter Server and the Management Server are in the same domain, you can enter
the Account name in one of following formats:
• username@domain (for example, administrator@mydomain).
• domain_name\user_name (for example, pernixdata\fvpadmin).
• If the vCenter Server uses a custom SSL port (not the default port 443), then you can
use the format server:port-number (for example, SRVR:21443).
The account must have Administrator permissions on the computer on which the Management
Server is installed. The specified account must also be able to log on to SQL Server with
sysadmin privileges. As part of setup, the account is also granted the right to log on as a service
to the Management Server computer.

NOTE

For easier and more convenient operation, we reiterate the

recommendation to run the Management Server service using the
same account used to run the Management Server service and to
log on to the SQL Server database.

To finish configuring the vCenter Server when the vCenter Server and the Management Server
are in the same domain and continue the installation, click Next. (Do not select the Run
PernixData Management Server Service as “Local System” checkbox.)

vCenter Server Logon: vCenter is in a Different Domain Than Management Server

If you install the Management Server in a different domain than the vCenter Server, enter the
fully qualified domain name of the server (for example, vcenter.pernixdata.com) or the
IP address in the VMware vCenter Server field (Figure 19).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 38 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 19: Remote vCenter Server Logon Information (vCenter Server on Different Computer than Management Server)

In the Account name box, enter the name of the domain user under whom the Management
Server will run. In the Account Password box, enter the password for that account.
When the vCenter Server and the Management Server are in the same domain, you can enter
the Account name in one of following formats:
• username@domain (for example, administrator@mydomain).
• domain_name\user_name (for example, pernixdata\fvpadmin).
• If the vCenter Server uses a custom SSL port (not the default port 443), then you can
use the format server:port-number (for example, SRVR:21443).
The account has Administrator permissions on the computer on which the Management Server
is installed. The specified account must also be able to log on to SQL Server with sysadmin
privileges. As part of setup, the account is also granted the right to log on as a service to the
Management Server computer.

NOTE

For easier and more convenient operation, we reiterate the

recommendation to run the Management Server service using the
same account used to run the Management Server service and to
log on to the SQL Server database.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 39 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Click the Run PernixData Management Server Service as “Local System” checkbox to select
connecting to the remote vCenter Server using the specified account credentials. Click Next to
continue setting up the connection to the remote vCenter Server.

Verify the Account

If you need to verify the account that the Management Server service is running under, right-
click PernixData Management Server in the Services snap-in, and then view the information on
the Log On tab of the Server Properties dialog box (Figure 20). The account must be able to
access (connect to) the SQL Server. For example, if the db_Owner is set to
domain\Administrator, but the Management Server service runs as .\Administrator, then the
Management Server cannot access the database, so the service stops. In Figure 20, the
db_Owner is set to .\Administrator, so the account can connect to the SQL Server.
Figure 20: Server Properties Dialog Box

After you configure the vCenter Server on the VMware vCenter Server Logon Information page,
click Next to continue the installation.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 40 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 7. In the Database Server screen (Figure 21 and Figure 22), specify the SQL Server database server
and the SQL Server database that the Management Server will use. Specify the user name and
password used to connect the Management Server with the database server.
Figure 21: Database Server Screen (Example 1)

Or:
Figure 22: Database Server Screen (Example 2)

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 41 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • Enter the name of the SQL Server computer in the Database server that you are installing
to box to specify the database server. For example:
san-jose-sql-1

NOTE

You can also select a database server from the dropdown list, or
select a server by clicking the Browse button.

If the computer runs multiple instances of SQL Server, then specify the instance name as
well, using the syntax server\instance:
san-jose-sql-1\sql2012
If you install the Management Server and SQL Server on the same computer, then you can
specify the computer name using the following syntax:
(localhost)
If you install the Management Server and SQL Server on the same computer, and if you need
to include an instance name, then specify the instance after a backslash, for example:
(localhost)\sql2012
• The default Database Name is prnx. Optionally, you can enter a customized name (for
example, FVPdatabase) in the Database Name box.

NOTE

The Database Name can include only alphanumeric characters

and underscores. Underscores are the only special characters
allowed in the Database Name.

• The Connect using radio buttons and fields specify the method of connecting to the
database server.
At the beginning of Verify Windows-Based Management Server Installation Prerequisites,
we recommended that you use the same account to install Management Server, run the
Management Server service, and to log on to SQL Server. In Step 5 on page 22, we
recommended that you configure SQL Server to use Windows authentication to make
installation and management as easy as possible.
If you followed these recommendations, then leave the Windows authentication
credentials of current user radio button selected, and click Next to continue the installation.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 42 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 If your instance of SQL Server does not use Windows authentication, or if you want to use a
different account to log on to SQL Server, select the Server authentication using the Login
ID and password below radio button. This activates the grayed-out Login ID and Account
Password fields. Enter the account name and password.

NOTE

As documented in Step 5 on page 22, the SQL Server account

must already exist because the installation program cannot
create it for you, and the account must have sysadmin
privileges.

Click Next to continue the installation.

8. In the Management Server Network Port Settings screen (Figure 23), configure how the
network identifies the Management Server by specifying the Management Server computer
name (for example, san-jose-fvp-1) or IP address, and the HTTP and HTTPS ports to use.
Figure 23: The Network Port Settings Page

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 43 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • In the Name or IP Address field, use the drop down list to identify the Management Server
by its computer name or by its IP address. Unless your network has experienced name
resolution problems, we recommend that you use the name instead of the IP address
because the name is descriptive, and therefore easier to identify.

NOTE

The choice of identifying the Management Server by name or IP

address does not affect how you access the Management
Console. For example, if you use the computer name, you can
access the Management Console using a URL such as:
http://san-jose-fvp-1.pernixdata.com:60001/login
If you use the computer name as the network identifier, you can
still use the IP address to access the Management Console:
http://192.168.1.100:60001/login

• Specify the HTTP port in the HTTP Port field and specify the HTTPS port in the HTTPS Port
field. By default, the HTTP port is port 60001 and the HTTPS port is port 60002. We
recommend that you use the default values unless you cannot open those ports in your
environment.
Although using different ports does not cause issues, changing the port values can
complicate FVP management slightly because you might need to add the port parameter for
some operations. For example, if you use the default port number values, and you use
Windows PowerShell, you can connect to your FVP deployment using a command similar to:
Connect-PrnxServer -UserName "administrator" -Password "p@ssw0rd"

However, if you change the port number values, many Windows PowerShell commands
require you to specify the port number in addition to the other values, for example:
Connect-PrnxServer -UserName "administrator" -Password "p@ssw0rd" –
Port 60004

Another reason to use the default values is that they are easy for administrators to
remember. For example, you have to specify the HTTP port when you connect to the
Management Console:
http://san-jose-fvp-1.pernixdata.com:60001/login
In addition, PernixData documentation uses 60001 as the HTTP port number, so referring to
the documentation is another easy way to find the default port number that is not available
if you use a different port number.
Click Next to continue the installation.

9. Install the Management Server. On the PernixData FVP Licensing screen (Figure 24), click Next.
Then on the Ready to Install the Program page (Figure 25), click Install.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 44 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 24: Licensing Screen

Figure 25: Ready to Install Screen

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 45 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 10. The Installing PernixData Management Server screen tracks the progress of the installation
(Figure 26). Installation usually takes approximately five minutes or less.
Figure 26: Installing the Management Server

11. When setup completes, click Finish on the InstallShield Wizard Completed page (Figure 27) to
close the Installation Wizard.
Figure 27: The Installation Complete Page

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 46 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 If your web browser is configured to allow cookies as part of the authentication mechanism,
allow JavaScript and TLS, and allow popups, as described in General Installation Prerequisites,
you can now log on to the Management Console.
If you have not configured your browser to allow cookies as part of the authentication process,
Appendix B shows you how to do that for Microsoft Internet Explorer, Google Chrome, and
Mozilla Firefox.

Management Server Virtual Appliance Installation (Deployment and

Configuration)

The Management Server Appliance is comprised of two components:

1. Management Server Service (handles communication with vCenter, internal database, etc.).
2. Management Server Console (provides a graphical interface for administrator interaction).
The installation process includes deploying the Management Server Appliance VM, and then configuring
the Management Server service for use.
If you want to install the Windows PowerShell Management CLI Tools, you need to use the Windows-
based installer to run a custom installation (see Step 5 on page 22). You can deploy the Management
Server Appliance as your main management system and use the Windows-based installer to install just
the CLI Tools on a management computer.
This procedure is for new installations only. You cannot migrate from an existing Windows-based
Management Server installation to the Management Server Appliance at this time. If you want to use
the Management Server Appliance and a Windows-based version of the Management Server is already
installed, you must uninstall the Windows-based Management Server before you install the
Management Server Appliance. (For uninstallation instructions, see the PernixData FVP and Architect
Uninstallation Guide.)

NOTE

Uninstalling the Management Server software loses the

configuration, so if you uninstall the Windows-based Management
Server, and then install the Management Server Appliance, you
need to reconfigure the FVP Clusters, acceleration resources,
VMs, and datastores. All reports and logs are also lost.

If you did not perform the following steps from the Verify Management Server Appliance Installation
Prerequisites section, then before you begin the Management Server Appliance installation procedure,
follow the steps in the prerequisites verification section to ensure that:
● The VI Client is connected only to the vCenter Server. If the VI Client is connected directly to an
ESXi host, the deployment fails and generates an error message (Figure 28).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 47 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 28: Error Message Seen If the VI Client Is Connected Directly to ESXi Hosts

● The physical host on which you install the Management Server Appliance has sufficient RAM and
vCPU resources to meet the resource requirements for the Management Server Appliance, as
shown in Table 3. These resources are in addition to resources required for other VMs on the
host.

● You have made a DNS Server entry to map the hostname to the static IP address you will assign
to the Management Server Appliance.
● You know the required network settings (location of your vCenter Server, IP addresses, etc.) and
have obtained a static IP address for the Management Server Appliance. A static IP address is
required to run the Management Server service. You cannot use a dynamic IP address (for
example, do not use an address assigned by a DHCP server). If you have multiple vCenters, you
need to install a separate instance of the Management Server Appliance for each vCenter.
If you install the Management Server Appliance on a server that does not have sufficient resources to
support the deployment, when you attempt to start the Management Server Appliance, it warns you
that you need to allocate more resources before you can use FVP.

NOTE

If you have multiple vCenters, you need to install a separate

instance of the PernixData Management Server for each vCenter.
If the vCenters are in Linked Mode, then you need to launch the
Management Server Console using the vCenter Web Client.

You can deploy the Management Server Appliance using the vSphere Client or using the vSphere Web
Client (refer to VMware documentation for how to install applications using the vSphere Web Client).
The Management Server Appliance installation section covers:
• Deploying the Management Server Appliance Using the vSphere Client
• Configuring the Management Server Appliance
• Accessing the Management Server Appliance Configuration Pages After Initial Configuration

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 48 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • Additional Options After Initial Management Server Appliance Configuration
• Enabling and Disabling SSH Access
• Root Password Access
• Password Recovery (Lost Password)

Deploying the Management Server Appliance

To deploy and configure the Management Server Appliance using the vSphere Client, complete the
following procedure:
1. Start the vSphere Client and connect to the vCenter Server.
2. Select the vCenter Cluster on which you want to install the Management Server Appliance
(Figure 29).
Figure 29: Select the vCenter Cluster

3. Click File and select Deploy OVF Template… to specify the source location of the OVF template
(Figure 30).
Figure 30: OVF Template Deployment

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 49 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 4. The Source dialog box appears (Figure 31). Click Browse… to navigate to the PernixData
Management Server Appliance OVA file.
Figure 31: The Source Dialog Box

5. Select the PernixData Management Server OVA file (the filename is similar to the highlighted
filename in Figure 32), then click Open.
Figure 32: The PernixData Management Server OVA File

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 50 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 6. The selected OVA file appears in the Source dialog box (Figure 33). Click Next to continue.
Figure 33: OVA File Source Location

7. The OVF Template Details screen appears (Figure 34).

Figure 34: The OVF Template Details Screen

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 51 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 The screen includes the following information:
• Product—The name of the PernixData products.
• Version—The version number of the PernixData Management Server Appliance.
• Vendor—The vendor name (PernixData).
• Publisher—The publisher name (PernixData).
• Download size—The size of the file.
• Size on disk—The disk space required for thin and thick provisioning.
• Description—What the selected OVF template does. The IP address referred to is the static
IP address you will configure in Step 13 of this procedure.
Click Next to continue.

8. The Name and Location screen appears. In the Name field, enter a unique name for the
Management Server Appliance. For example, pernix-ms-app-04, as shown in Figure 35. After
you name the Management Server Appliance, click Next.
Figure 35: The Name and Location Screen

9. The Deployment Configuration screen appears (Figure 36). Select the approximate size of your
deployment using the Configuration drop-down menu.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 52 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 36: The Deployment Configuration Screen

The Configuration drop-down menu provides four deployment size choices, and the amount of
resources required to support each deployment size. Table 4 shows the deployment sizes and
the resource requirements for each deployment size.
Table 4: Deployment Sizes and Required Resources

Minimum Dedicated Disk Size

Deployment Size vCPUs
VM RAM (Thick)*

Tiny (1-5 hosts or 1-50 VMs) 4 GB 2 100GB

Small (6-100 hosts or 51-1000 VMs) 8 GB 4 100GB

Medium (101-400 hosts or 1001-4000 VMs) 12 GB 8 100GB

Large (more than 400 hosts or 4000 VMs) 16 GB 16 100GB

* You can configure the disk size as “thin” so that the disk size starts small and grows as needed.
If you select the wrong vSphere environment size, or if you want to change the resource
allocation for the VM later, you can change the allocated amount of RAM and number of vCPUs
manually.
If you did not ensure that the required amount of resources are available for the Management
Server Appliance as part of the installation planning (see Verify Management Server Appliance
Installation Prerequisites), check to ensure that the required resources for your deployment size
are available.
The installation program automatically assigns the required resources to the Management
Server Appliance. However, the installation program cannot check to ensure that the required
resources are actually available. If the required resources are not available, then when you start
the Management Server Appliance VM, a message appears to notify you that there are
insufficient resources to run the appliance. To fix the issue, add resources to the Management
Server Appliance.
After you specify the deployment size, click Next to continue.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 53 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 10. The Specify a Specific Host screen appears. Select the vCenter Cluster host on which you want
to deploy the Management Server Appliance template. Figure 37 shows the host with the IP
address 10.20.12.51 selected. Click Next to continue.
Figure 37: Specify a Host

11. If more than one datastore is associated with the selected host, then the Storage screen
appears so that you can choose a destination storage device for the Management Server
Appliance VM files (Figure 38: The Storage Screen). If only one datastore is associated with the
selected host, then that datastore is used as the destination storage device, this step is skipped,
and the Disk Format screen shown in Step 12 appears.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 54 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 38: The Storage Screen

Because no storage profiles are configured, there are no choices in the VM Storage Profile field.
Select a datastore and then click Next to continue.

12. The Disk Format screen appears. The screen shows the datastore selected for the OVF template
deployment, and the space available on the datastore in Gigabytes. Click the appropriate radio
button to select whether you want to thick provision or thin provision the client:
• Thick Provision Lazy Zeroed—All of the disk space (100GB) is allocated and reserved, but not
wiped clean (so each block must be zeroed before performing the new write), when the disk
space is created. Other VMs cannot use the disk space, even when it is not in use.
• Thick Provision Eager Zeroed—All of the disk space (100GB) is allocated and wiped clean
(zeroed) when the disk space is created. Other VMs cannot use the disk space, even when it
is not in use.
• Thin Provision—Uses the lowest amount of disk space. Other VMs can use the unused disk
space.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 55 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 When you use thick provisioning, all of the configured disk space is used on the array, even if the
space is not in use. When you use thin provisioning, in the beginning, a relatively small amount
of disk space is used on the array, and more space is allocated as needed. Figure 39 shows Thin
Provision selected. Click Next to continue.
Figure 39: The Disk Format Screen

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 56 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 13. The Networking Properties screen appears (Figure 40).
Figure 40: The Networking Properties Screen

In the IP Address field of the IP Settings section, enter the static IP address that you obtained
from your administrator before you began the install process. You cannot use a dynamic IP
address; you must use a static IP address. Enter the subnet mask and default gateway IP address
in the appropriate fields.
In the DNS section, enter the IP address of a DNS server to use for the Management Server
Appliance. After you enter all of the values in the Network Properties screen, click Next to
continue. Skip the rest of this step and go to Step 14.
If you do not provide all of the values requested on this screen, then the Management Server
Appliance cannot power on. If you want to fill in the Networking Property values after
deployment, you can continue the deployment, but instead of the successful deployment
message at the end of the process (see Step 16), you see the dialog shown in Figure 41.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 57 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 41: Management Server VM Does Not Power On If Network Properties Are Not Specified

Click Close to continue. You can power on the Management Server Appliance by providing the
required values after deployment. In the vCenter Client, right-click on the Management Server
Appliance and select Edit Settings… (Figure 42).
Figure 42: The Edit Settings… Option

The Virtual Machines Properties screen appears . Click the Options tab (circled in Figure 43),
then select Properties to reveal the Networking Properties screen.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 58 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 43: Setting Networking Properties Using the VI Client Edit Settings… Option

Enter the required values in the appropriate fields, then click OK. When the network properties
are configured (you can check the status in the Recent Tasks area), right-click the Management
Server VM (pernix-ms-app-04 in Figure 44), click Power, then select Power On.
Figure 44: Power On the Management Server VM

After the Management Server Appliance powers on (check Recent Tasks), you can configure the
appliance (see Configuring the Management Server Appliance).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 59 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 14. The Ready to Complete screen appears. Click the Power on after deployment checkbox to
power on the Management Server Appliance VM after deployment. (If you do not select the
checkbox, you will have to power up the VM anyway to configure it.) The screen also includes
information about the deployment size setting (Figure 39). Click Finish to finish the installation
and begin the deployment.
Figure 45: Start the Deployment

15. The deployment begins. A popup screen shows the progress of the deployment and the
approximate time remaining (Figure 46).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 60 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 46: Deployment Progress Bar

16. If you do not check the Close this dialog when completed checkbox in the previous step, a pop-
up box confirms successful deployment (Figure 47).
Figure 47: Successful Deployment

If you closed the dialog box, you can check the deployment on the Recent Tasks area of the
vSphere Client (Figure 48).
Figure 48: The Recent Tasks Area of the vSphere Client

This step completes deploying the Management Server Appliance. Continue and complete the
installation by configuring the Management Server Appliance.

Configuring the Management Server Appliance

1. After you deploy the Management Server Appliance, open a browser window and point the
browser to the static IP address you obtained for the Management Server Appliance (Figure 49)
so that you can configure the appliance.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 61 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 49: Point the Browser to the Static IP Address of the Management Server Appliance

2. The Your connection is not private screen appears (Figure 50). This screen appears because the
software uses a default self-signed certificate. Do not be concerned about this. If you want to,
you can deploy an SSL certificate to the Management Server Appliance by following the
instructions in PernixData KB article 1076. Click Advanced to reveal the advanced portion of the
screen.
Figure 50: The Your Connection is Not Private Screen

The Advanced portion of the screen (Figure 51) allows you to continue by clicking the Proceed
to <URL> (unsafe) link (in Figure 51, the URL is 10.20.98.204). In spite of the warning
message, it is safe to proceed.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 62 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 51: The Your Connection is Not Private Screen Advanced Options

3. The end user license agreement (EULA) appears (Figure 52). Click the I Accept radio button and
then click Next to accept the EULA and continue.
Figure 52: The End User License Agreement (EULA)

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 63 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 4. The PernixData login screen appears (Figure 53). Enter the credentials (user name and
password) you received from PernixData to log in to the Management Server Appliance and
configure it.
The user name is pernixdata (all lower-case letters) and is not configurable and cannot be
changed. However, the initial password (pernixdataappliance, all lower-case letters) is
temporary. You must change the password during initial Management Server Appliance
configuration. After you enter the user name and the temporary password, click Login to log
into the Management Server Appliance configuration pages.
Figure 53: The PernixData Management Appliance Configuration Login Screen

5. The PernixData Management Server Appliance Configuration screen appears (Figure 54).
Appliance configuration is a four-step process that begins with vCenter Server configuration,
then proceeds to configuring the network settings, time, and your Management Server
Appliance credentials. You can also navigate among the four screens by clicking the desired
option in the menu on the left side of the screen.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 64 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 54: The PernixData Management Server Appliance Configuration Screen

In the vCenter Server field, enter the IP address of the vCenter Server that the Management
Server Appliance will work with. Enter administrator-level vCenter credentials in the Username
and Password fields. Click Next to continue to the Network Settings screen.

6. The Network Settings screen appears. The values you entered in Step 13 on page 57 when you
deployed the OVA file appear in the appropriate fields (Figure 55).
Figure 55: The Network Settings Screen

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 65 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 In the DNS section, you can enter a hostname (not required, but recommended for easier
identification) and the IP address of at least one DNS server. Clicking the question mark (?) icon
provides additional information about the Hostname field:
This field is optional and specifies the hostname for the appliance. In addition to
standard networking purposes, this field is used when registering plugins with the
vSphere clients, so ensure any hostname entered is routable to them. An FQDN is
preferred, but a simple name can also work as long as vSphere clients can connect to it.
This field can be left empty, in which case the IP address will be used for vSphere plugin
registration.
If you want to specify more than one DNS server, click the plus sign (+) to open another DNS
server IP address field.

NOTE

Be sure to add an entry to your DNS server to map the DNS entry
for the hostname to the IP address. This enables you to specify
the name instead of the IP address because the DNS server will
be able to resolve the hostname.

If you use a proxy server to connect to the Internet, click the Enable checkbox in the Proxy
section to enable Internet access for PernixPlus and to support online licensing. If you do not
use a proxy server to connect to the Internet, click Next to continue. When you click the Enable
checkbox, the rest of the Proxy settings are revealed (Figure 56).
Figure 56: Proxy Settings (Network Settings Screen)

Enter the proxy server IP address in the Proxy Server field, and the port number in the Port
field. The Management Server Appliance checks to ensure that the DNS server address is valid. If
the address is not valid, the message Invalid DNS Server Address appears next to the
Discard button.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 66 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 If your proxy server requires authentication, click the Authentication Required checkbox, then
enter the username and password credentials.
Click Save to save the proxy settings and continue to the next screen.

7. The Time screen appears (Figure 57). Use the drop-down menu in the Time Zone field to select
your time zone. Optionally, enter the NTP server in the NTP Server field. Click Next to continue.
Figure 57: The Time Screen

8. The Appliance Credentials screen appears (Figure 58). For security, you must reset your
Management Server Appliance password before you can access the Management Console and
begin using your PernixData software. We recommend that you set a strong password to
prevent unauthorized access.
Figure 58: The Appliance Credentials Screen

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 67 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 The Appliance Credentials fields are:
• Username—The default username pernixdata appears automatically in the Username
field. You cannot change the default username.
• Current Password—Enter the current password. Because this is the first time you are
configuring the Management Server Appliance, the current password is the default
password you received from PernixData (pernixdataappliance). There are no restrictions on
the characters you can use to specify the password.

NOTE

This procedure is for new installations. However, if you previously

installed a version of the Management Server Appliance, the
pernixdata username might be associated with the password
configured during the previous installation.

• New Password—Enter your new password.

• Confirm—Re-enter your new password. The string in the New Password field must match
the string in the Confirm field before you can continue.
Click Finish to finish the installation.

9. The Configuration Complete Screen appears (Figure 59).

Figure 59: The Configuration Complete Screen

Click Stay Here to remain on the configuration pages for the Management Server Appliance, or
click Go to PernixData Management Console to go to the PernixData Hub and begin using your
PernixData software.
This step completes configuring the Management Server Appliance.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 68 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Accessing the Management Server Appliance Configuration Pages After Initial
Configuration

After you finish configuring the Management Server Appliance, when you go to the PernixData
Management Console (either by clicking the Go to PernixData Management Console button after initial
configuration, or by pointing a browser at the static IP address of the Management Server Appliance—
see Appendix C: How to Access the Management Console for details), you must log in to the
Management Console (Figure 60). This login screen is different than the login screen for the
Management Server Appliance configuration pages. Use your vCenter Credentials (not the Management
Server configuration credentials) to log in to the Management Console.
Figure 60: The Management Console Login Screen

After you log in to the PernixData Management Console, you can return to the Management Server
Appliance configuration pages from the Management Console at any time.
1. From the Global Settings tab on the PernixData Hub, select Appliance Configuration from the
menu on the left side of the page (Figure 61).
Click the link shown in the Appliance Configuration URL field that includes the static IP address
of the Management Server Appliance to go to the configuration pages.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 69 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 61: The Global Settings Tab Appliance Configuration Page

NOTE

If you entered the hostname instead of an IP address for the

Management Appliance Configuration URL, the URL appears as
the hostname.

2. Unless you are already logged in to the PernixData appliance configuration pages, or you just
finished initial configuration and chose to Stay Here instead of Go to PernixData Management
Console, the appliance login screen appears. This is the same login screen that appears when
you initially configure the appliance (Figure 53). Enter the Management Server Appliance User
name and Password credentials.
Remember that these are not the same credentials you use to access the Management Console.
(You use your vCenter Server credentials to log in to the Management Console.) The user name
for appliance configuration is always pernixdata, and the password is the password you
configured in Step 8 on page 67 during appliance configuration.

Additional Options After Initial Management Server Appliance Configuration

After you log in to the Management Server Appliance Configuration pages (or stay on the configuration
pages after initial configuration), there are three additional options in the menu on the left side of the
screen (Figure 62). The three new options are the Services screen, the Management Console screen,
and the Software Update screen.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 70 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 62: The Services Screen

The Services screen shows the current status of the services that the Management Server Appliance
uses. In Figure 62), the Start, Stop, and Restart options are grayed out. Click anywhere in a row to select
(highlight) a service and activate the appropriate options. For example, if you select a currently running
service, then only the Stop and Restart options become active, because the service is already started
(Figure 63). If you select a service that has stopped, only the Start and Restart buttons become active.
Figure 63: Selecting a Service Activates the Appropriate Options

The Software Update screen enables you to upgrade the Management Server Appliance easily. You
need to download an appropriate upgrade bundle from PernixData Support before you can upgrade the
software. See the latest version of the PernixData FVP and Architect Upgrade Guide for the upgrade
procedure.
When you are ready to go to the PernixData Management Console, click the Management Console link
(Figure 64).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 71 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 64: The Management Console Screen in the Appliance Configuration

Click the URL in the PernixData Management Console URL field to go to the Management Console. If
you are not already logged in to the Management Console, use your vCenter Server credentials to access
the Management Console.

Enabling and Disabling SSH Access

By default, SSH access is disabled. From the Access screen on the PernixData Management Server
Appliance Configuration pages, you can enable and disable SSH access (Figure 65), as well as change
password used to access the Configuration pages.
Figure 65: The Access Screen

Click the Enable SSH Access check box (Figure 66), and then click the Save button to enable SSH access.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 72 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 66: Enable SSH Access (Management Server Appliance)

A dialog box confirms that the changes were saved (Figure 67).
Figure 67: SSH Changes Saved Confirmation

Click OK. The Enable SSH Access check box remains checked to show that SSH access is enabled. To
disable SSH access, click the Enable SSH Access check box to clear the check mark, and then click Save.
The Changes Saved dialog box appears again, and after you click OK, the Enable SSH Access check box is
unchecked, and SSH access is disabled.
In case of an upgrade failure, you can enable SSH access to the Management Server Appliance from a
command line editor, for example, from the vSphere Client Console. Be careful to make only the edits
listed in this procedure. Uncommenting and/or editing incorrect lines in the configuration can lead to
unpredictable behavior.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 73 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
To enable SSH from a command line editor:
1. From the console, log in to the Management Server Appliance, using the IP address of the
appliance and the login credentials for the Management Server Configuration pages (configured
in Step 8 on page 67, not the vCenter credentials used to log into the PernixData Management
Console.
2. At the prompt, run the command to open the SSH configuration (sshd_config). For example,
in a VI editor, the command is:
sudo vi /etc/ssh/sshd_config

3. The SSH configuration appears. Use the keypad to scroll through the configuration and find the
following two password authentication lines:
PasswordAuthentication no
#PasswordAuthentication yes

4. Edit the configuration. Add a “#” sign in front of the “PasswordAuthentication no” entry to
comment it out, and delete the “#” sign in front of the “#PasswordAuthentication yes”
entry to enable the command. The result looks like this:
#PasswordAuthentication no
PasswordAuthentication yes

5. Save the configuration. For example, in a VI editor, press ESC to enable entering commands,
type a colon (“:”) followed by “wq” (for write and quit), and then press Enter; the following
example command writes (saves) the configuration and quits editing the SSH configuration in a
VI editor:
[pernixdata@pernix-ms-app-04 ~]$ :wq

6. At the prompt, run the command to open the cloud configuration file (cloud.cfg). For
example, in a VI editor, the command is:
sudo vi /etc/cloud/cloud.cfg

7. Use the keypad to scroll through the configuration and find the line:
ssh_pwauth: 0

8. Change value in the line “ssh_pwauth: 0” from 0 to 1, so that it reads:

ssh_pwauth: 1

9. Save the configuration.

10. Restart the SSH service to make the changes take effect:
sudo service sshd restart
11. You can now SSH into the Management Server.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 74 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Read-Only Database Access from Remote Computers

PernixData provides a read-only user login for access to the Management Server Appliance database
from remote computers:
• Database User Login—prnx_readonly
• Database Password—readonly
The default database login and database password cannot be changed. You enable remote read-only
database access on the Management Server Appliance from a command-line editor; for example, from
the vSphere Client Console:
1. From the console, log in to the Management Server Appliance, using the IP address of the
appliance and the login credentials for the Management Server Configuration pages (configured
in Step 8 on page 67, not the vCenter credentials used to log into the PernixData Management
Console.
2. At the prompt, run the following commands to open TCP port 5432 (this is the port that the
Management Server Appliance Postgres database uses) and save the configuration:
$ sudo iptables --insert INPUT --protocol --destination-port 5432 --
match state --state NEW --jump ACCEPT
$ sudo service iptables save

The console screen looks similar to Figure 68, which shows that the new firewall rule has been
saved:
Figure 68: Opening TCP Port 5432 to Enable Remote Read-Only Access

Opening the TCP port permits remote users to access the PernixData Management Server
Appliance database.
3. You can now connect to the Management Server Appliance database from the remote
computer. For example, Figure 69 shows connecting using pgAdmin III:

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 75 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 69: Using Remote Read-Only Access to Connect to the Management Server Appliance

The Name is the name you choose to use to store the settings.
The Host is the IP address of the Management Server Appliance.
The Port is 5432, the port that the Postgres database uses.
The Maintenance DB is the PernixData database (prnx).
The Username is always prnx_readonly.
The Password (not shown) is always readonly.

Root Password Access

If you lose your “pernixdata” user password, you can access FVP and Architect Management Server
Appliance configuration page using the root password. (Your vCenter credentials still log you in to the
Management Console.) The default root username and password are:
• Username—root
• Password—ApP!i@nce2016

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 76 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
You cannot change the login name. To log in to the Management Server Appliance configuration page,
point your browser to the Management Server URL and append /config to the URL. For example, if the
Management Server URL is 10.20.98.204, point your browser to:
https://10.20.98.204/config
The browser takes you to the Management Server Appliance configuration page login screen. Enter the
root user credentials (Figure 70).
Figure 70: The Management Server Appliance Configuration Page Login

Click Login to log in to the configuration pages.

PernixData recommends that you change the root password to help prevent unauthorized access. After
logging in, click Appliance Credentials to go to the password change page. Changing the root password is
the same procedure as changing the pernixdata user password. See Step 8 on page 67 for how to change
the password.

Password Recovery (Lost Password)

If you lose your password for the “pernixdata” user and you need to reconfigure it, contact PernixData
support at http://support.pernixdata.com.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 77 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Appendix A: Hardware and Software Prerequisites for FVP
Before you begin installing FVP and Architect, make sure that your VMware environment meets the
prerequisites in this appendix. Some prerequisites apply only to the Windows-based Management
Server and do not apply to the Management Server Appliance.

ESXi Host Configuration Requirements and Recommendations

• FVP requires exclusive access to each flash device allocated to FVP. Server-side flash cannot be
used partly by FVP and partly by another application. In servers where drive bays are limited
(such as blade servers), PernixData recommends populating all the drive bays with solid state
drive (SSD) flash devices, and booting either from the SAN/PXE or from a USB/SD Card. This
approach requires a persistent scratch location for storing temporary data such as logs,
diagnostic information, and the system swap file. See VMware KB 1033696 for instructions on
setting up this type of configuration.

NOTE

FVP does not require the types and capacities of flash devices
installed on your hosts to be identical. You can mix and match
flash devices of different sizes and from different vendors as
needed.

• For optimal performance with FVP, SSD flash devices should be accessed without using a RAID
configuration. Whenever possible you should configure your disk controllers to operate in JBOD
or Pass Through modes. This refers to a setup where multiple drives are configured either as
independent drives or as a single logical volume that does not use RAID.
• If JBOD or Pass Through modes are not available, create single-drive RAID-0 logical volumes, and
disable read-ahead optimization and controller cache on those volumes. RAID-0 (also known as
a striped volume) offers increased disk performance, but does not provide data redundancy. In
this case, FVP provides data redundancy for you.

NOTE

For detailed configuration settings for common server controller

platforms, see the list of Technical Reference guides in the
Documents and Download section of the PernixData Customer
and Partner portal.

• You must remove existing partitions from your flash devices before you add those devices to an
FVP Cluster. See VMware KB 1036609 for instructions on deleting partitions from a flash device.
• Install the Host Extension Module on all hosts in a cluster on which you intend to use fault
tolerant Write Back acceleration. You can use Write Back mode only on hosts that are running

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 78 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 the Host Extension Module, because Distributed Resource Scheduler (DRS) or high availability
(HA) might migrate a virtual machine to another host. For this reason, make sure that each host
in the cluster is running the Host Extension Module.
• Set up datastores used with FVP on hosts that are running the Host Extension Module. Reserve
the datastores exclusively for use by FVP. If you set up a datastore on a host that is not running
the Host Extension Module, or if a host accesses a datastore that is not running the Host
Extension Module, then FVP cannot accelerate write operations involving the datastore. The
result is that all VMs run in Write Through mode, and no VMs run in Write Back mode.
Write Back mode is not allowed in any deployment in which a host that is not running the Host
Extension Module accesses one of the datastores. In this scenario, that none of the virtual
machines in the FVP cluster can use Write Back mode. If a non-FVP host accesses even one
datastore, VMs that use that datastore cannot operate in Write Back mode.

Windows-Based Management Server Configuration

• In Microsoft Active Directory environments, we strongly recommended that you run the
Management Server service using a domain account that:
o Runs the FVP Management Server service.
o Has full administrator permissions to vCenter.
o Has database owner (DBO) permissions to the SQL Server database used by FVP.
• To prevent the database transaction log file from growing too large and using too much disk
space, either configure the database to use simple recovery mode or schedule the database for
regular full backups.

Requirements and Compatibility

• In order to install FVP, your environment must meet the following minimum requirements
(some requirements apply only to the Windows-based Management Server, as marked):
• One VMware vCenter® 5.1, 5.5, or 6.0 Server or one VMware vCenter Server Appliance 5.1, 5.5,
or 6.0 managed ESXi cluster with the following:
o One or more ESXi 5.1, 5.5, or 6.0 hosts containing one or more ESXi-compatible PCIe or
SSD based flash devices.

NOTE

FVP does not support stand-alone ESXi hosts: FVP hosts must be
part of a vCenter cluster.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 79 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • One or more FC, FCoE, iSCSI, or NFS-based storage devices containing one or more virtual
machines. Direct-attached storage and other local datastores are also supported.
• One Microsoft® Windows Server 2008 or Windows Server 2012 64-bit instance to run the
PernixData Management Server service. (Windows-based Management Server only.)
• The PernixData Management Server service:
o Installs Oracle Java SE 8.
o Installs Java Runtime Environment (JRE) 1.8u91.

NOTE

The setup program overwrites any existing JRE installation.

o Accesses the Management Server database (see below). Installing the FVP software
does not alter the contents of any existing databases.
o The Management Server requires minimum dedicated RAM and vCPU resources as
shown in Table 2. The PernixData Knowledge Base article Tuning Management Server
for Optimal UI Performance here (requires login) provides more detailed information
about resource requirements.
o The Management Server requires the host server to run .NET Framework 3.51 Service
Pack 1 or later. (Windows-based Management Server only.)
• Any version of Microsoft® SQL Server® 2008, Microsoft® SQL Server® 2012 or Microsoft® SQL
Server® 2014 (required to host the Management Server database). If you do not have a SQL
Server database, you can download the free Microsoft® SQL Server® 2012 Express database. To
make management easier, we recommend that you install this database on the same computer
as the Management Server. (Windows-based Management Server only.)
● VMware vCenter must be up and running before you can install FVP or Architect, because as
part of the installation process, FVP and Architect must log on to vCenter. Note that your
vCenter does not need to include any clusters, hosts, or virtual machines in order to install FVP
or Architect. However, these items must be added to the vCenter before you can configure and
use FVP or Architect.
FVP and Architect can also use the vCenter Server Virtual Appliance (a Linux-based implementation of
VMware vCenter).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 80 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Firewall Settings

To ensure network access among all the components within a PernixData deployment, ensure that the
ports shown in Table 5 are open for all firewalls in the vCenter network.
Table 5: FVP Firewall Settings

Source Destination Port(s)

Management Server ESXi hosts TCP 751

ESXi Host(s) ESXi hosts TCP 750, 751

Management Server vCenter TCP 443

Management Console and Windows Management Server TCP 60001, 60002

PowerShell

Management Server (vSphere Linked Management Server (vSphere TCP 60002

Mode) Linked Mode)

NOTE

If you changed the Management Server network port settings in

Step 8 on page 43, ensure that those ports are open.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 81 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Supported Hardware

PernixData software supports the hardware listed in Table 6. In general, the hardware requirements are
the same as the hardware requirements for ESXi 5.1, 5.5, or 6.0.
Table 6: FVP Supported Hardware

Server Description

ESXi host server Any server listed in the VMware Compatibility Guide for ESXi 5.1, 5.5, or
6.0. For example:
• Cisco UCS series
• Dell PowerEdge series
• HP DL and BL series
• IBM xSeries platforms

Flash Devices Any flash device listed in the VMware Compatibility Guide for ESXi 5.1, 5.5,
or 6.0. Examples include (but are not limited to):
• Cisco, Dell, HP, IBM OEM SSDs
• Intel DC S3700 Series SSD
• PCIe and NVMe SSDs or cards

Storage Adapters Any:

• 4 Gbps or higher Fibre Channel (FC) adapter
• 1 Gbps or higher iSCSI adapter
• 10 Gbps or higher converged network adapter (CNA) listed in the
VMware Compatibility Guide for ESXi 5.1, 5.5, or 6.0.

Network Adapters Any 1 Gbps or higher network adapter listed in the VMware Compatibility
Guide for ESXi 5.1, 5.5, or 6.0.

Storage Protocols (for Supported storage protocols include:

backend datastores)
• FC
• Fibre Channel over Ethernet (FCoE)
• iSCSI
• NFS
• Local datastores

Storage Systems Any storage system listed in the VMware Compatibility Guide for ESXi 5.1,
5.5, or 6.0. PernixData software supports datastores that are managed by
the VMware Native Multipathing Plugin (NMP).

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 82 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Supported Software

You can use PernixData software with the software listed in Table 7. Only ESXi hypervisors are
supported. If you use the Windows-based Management Server, you must install the Management Server
on a computer running a supported version of Microsoft Windows, and the Management Server
database must be a supported version of Microsoft SQL Server. Microsoft Windows and a Microsoft SQL
Server are not required if you use the Management Server Appliance.
Table 7: FVP Supported Software

Software Description

Hypervisors Any of the following versions of VMware ESXi:

• ESXi 5.1
• ESXi 5.5
• ESXi 6.0

VMFS versions Any of the following versions of the Virtual Machine File System (VMFS):
• VMFS-3
• VMFS-5

Management The FVP Management Server can be installed on a computer running any of
Server (Windows- the following operating systems:
based
• Microsoft Windows Server 2008 64-bit
Management
• Microsoft Windows Server 2008 R2 64-bit
Server only)
• Microsoft Windows Server 2012 64-bit
• Microsoft Windows Server 2012 SP2 64-bit
• Microsoft Windows Server 2012 R2 64-bit

Management Any of the following editions of Microsoft SQL Server:

Server Database
• Microsoft® SQL Server® 2008 (All Editions)
(Windows-based
• Microsoft® SQL Server® 2012 (All Editions)
Management
• Microsoft® SQL Server® 2014 (All Editions)
Server only)

Guest Operating Any guest operating system listed in the VMware Compatibility Guide for
Systems ESXi 5.1, 5.5, or 6.0.

Browsers A See Appendix B: Configure the Web Browser for the Management
Console for browser support and recommendations.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 83 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Configuration Maximums

PernixData software supports the same set of maximums supported by your version of VMware
vSphere®. For example, vSphere 5.5 imposes maximum settings such as 64 virtual CPUs per virtual
machine and 2,048 virtual disks per host. For example, in a vSphere 5.5 environment, PernixData
software supports a maximum of 64 virtual CPUs per virtual machine and a maximum of 2,048 virtual
disks per host. Likewise, if you are running vSphere 5.5.you can have no more than:
• 1000 hosts in a single vCenter
• 500 hosts in a single datacenter
• 32 hosts in a single vCenter cluster
• 512 virtual machines on a single host
For the latest configuration maximums for vSphere 6.0, see the VMware KB article on ESXi/ESX
configuration maximums here.

Path Selection Policies (FVP)

When you install FVP, the software attempts to “claim” any datastores associated with hosts on which
you install the Host Extension Module. For example, if Host A accesses Datastores 1, 2, and 3, FVP
attempts to claim each of those three datastores as its own. If the datastore is compatible with FVP (the
datastore is managed with VMware’s Native Multipathing Plugin), then FVP claims the datastore and
replaces the path selection policy assigned to that datastore. FVP replaces the VMware PSP with the FVP
equivalent, as shown in Table 8.
Table 8: FVP Path Selection Policies

VMware Default PSP FVP Replacement PSP

VMR_PSP_FIXED PRNX_PSP_FIXED
VMR_PSP_MRU PRNX_PSP_MRU
VMR_PSP_RR PRNX_PSP_RR

FVP needs to claim the available datastores for acceleration to operate correctly. Claiming all of the
datastores enables FVP to manage all I/O requests for the datastores.

NOTE

VMs that belong to an FVP cluster can still use datastores that
FVP is not able to claim. However, those VMs cannot take full
advantage of FVP acceleration capabilities. For example, VMs that
save data to an unsupported storage array (including arrays
managed by EMC PowerPath) cannot use Write Back mode to
speed up write operations, and cannot take advantage of FVP
failover mechanisms such as fault domains.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 84 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Appendix B: Configure the Web Browser for the Management Console
In the FVP 3.0 release and subsequent releases, PernixData replaced the vSphere plugin used in previous
versions of the software with a new, browser-based, standalone Management Console. Either before or
after you install the Management Server, configure your web browser to work with the PernixData
Management Console.
Configuring your web browser for the Management Console includes:
• Allowing the use of cookies as part of the authentication mechanism.
• Allowing JavaScript and transport layer security (TLS).
• Allowing popups.

NOTE

Some browser plugins and extensions might interfere with the

Management Console. If you experience unusual or inconsistent
behavior when running the Management Console, disable all of
the web browser plugins and extensions. After that, if the
Management Console works as expected, re-enable the plugins
and extensions one at a time and see how each affects the
Management Console, until you discover the plugin or extension
that interferes with the Management Console.

PernixData software uses cookies as part of its authentication mechanism. If your web browser does not
allow the use of cookies, then you cannot log on to FVP or Architect. (Or, depending on your browser,
you might be able to log on, but the Management Console displays no data.) Before you log on to the
Management Console, carry out the appropriate procedure for your web browser to verify that your
logon session can be authenticated:
• Microsoft Internet Explorer
• Google Chrome
• Mozilla Firefox

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 85 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Microsoft Internet Explorer (10.0 or Later)

Click the Tools drop-down menu, and then click Internet Options. In the Internet Options dialog box, on
the Privacy tab, make sure that the privacy setting is set to Medium High (Figure 71).
Figure 71: Configuring Cookies in Internet Explorer

NOTE

Microsoft Internet Explorer versions prior to 10.0 are not

supported.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 86 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Google Chrome

Click the Customize and Control Google Chrome icon (upper right corner of the page). Click Settings. On
the Settings page, scroll down and select Show advanced settings….
Under Privacy, click Content Settings. In the Content Settings dialog box, make sure that Allow local
data to be set (recommended) is selected. (This option is under the Cookies heading, as shown in Figure
72.)

NOTE

We recommend that you use the latest version of Google Chrome

with PernixData software.

Figure 72: Allow Cookies in Chrome

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 87 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Mozilla Firefox

Click the settings menu (the three bars in the upper right-hand corner of the browser window). Click
Options. In the Options dialog box, on the Privacy tab, select the History dropdown and select Use
custom settings for history. Make sure the Accept cookies checkbox is selected, and verify that Always
is selected from the Accept third-party cookies dropdown list (Figure 73).

NOTE

We recommend that you use the latest version of Mozilla Firefox

with PernixData software.

Figure 73: Configuring Cookies in Firefox

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 88 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Appendix C: How to Access the Management Console
The PernixData Management Console is a standalone, HTML5-based management tool that you can
access using a web browser or a vSphere Web Client. You can access the Management Console with any
supported web browser (see Appendix B: Configure the Web Browser for the Management Console),
from any computer that has either:
1. Access to the server on which you installed the Management Server. You can install the
Management Server using the Windows-based installer or the Management Server Appliance (a
dedicated, self-contained VM) installer.
2. The CLI Management Tools installed (see Step 5 on page 22). You do not need the CLI
Management Tools to access the Management Console using the Management Server
Appliance. The CLI Management Tools can only be installed using the Windows-based installer.
You cannot install the CLI Management Tools on a computer using the Management Server
Appliance installer. The CLI Management Tools enable you to manage FVP from a remote
computer using PowerShell cmdlets.
You can either install the CLI Management Tools remotely in case you need scripting, or you can
trigger remote calls to the Management Server by running a remote PowerShell script. When
you use the Management Server Appliance, you can use the CLI Management Tools remotely
from any Windows-based computer that runs Windows 2008 R2 or higher.
Whether you log on to the Management Console using a web browser, a vSphere Web Client, or a
vSphere Client, and whether you install the Management Server using the Windows-based installer or
the Appliance-based installer, you use the same PernixData Management Console.
If you access the Management Console using the vSphere Web Client or the vSphere Client, you only see
basic FVP information, but you can start the Management Console from the client with the benefit of
using a single sign-on (SSO). Accessing the Management Console using a web browser is slightly faster
and easier than using the vSphere Web Client. However, if you need to view and access vCenter
information along with FVP information, then accessing the Management Console using the vSphere
client might be the right choice.
There are two ways to log on to the Management Console:
• Log On Using a Web Browser
• Log On Using a vSphere Web Client

Log On Using a Web Browser

1. Start your web browser. If you previously configured a DNS entry for the Management Server,
you can use the fully qualified domain name (FQDN) to access the Management Console, for
example:
https://FVP.pernixdata.com:60002/login
In the preceding URL:

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 89 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • FVP.pernixdata.com represents the FQDN of the computer on which the Management
Server is installed. Alternatively, you can use the IP address of that computer. For example,
if the computer IP address is 192.168.1.1:
https://192.168.1.1:60002/login
• 60002 represents the HTTPS port for the Management Server. However, when you install
the Windows-based Management Server, you can specify a different port. If you use a
different port (for example, port 60009), then specify that port number in your URL. For
example:
https://fvp.pernixdata.com:60009/login

NOTE

Log on using the HTTPS protocol, not the HTTP protocol.

Alternatively, if you are using the Management Server Appliance, you can use the IP address of
the Management Server for access, for example:
https://192.168.1.1
2. After you enter the URL in your web browser, the PernixData Management Console logon
screen appears (Figure 74).
Figure 74: Management Console Logon Screen

If you start the Management Console from your vSphere Client or vSphere Web Client, you are
automatically logged on using SSO. PernixData software relies on vCenter for security and
authentication. Therefore, to log on to FVP or Architect, you need to enter the
domain\username and the password of a user who has the appropriate vCenter permissions.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 90 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 For more information on vCenter permissions, see the Role-Based Access Control section of the
User Guide. Enter a user name and password in the appropriate boxes, and then click Login.
After authentication, the PernixData Dashboard appears (Figure 75).
Figure 75: The PernixData Dashboard

Log On Using a vSphere Web Client

1. Use a web browser to log on to your vSphere Web Client, using a URL similar to:
https://vcenter.pernixdata.com:9443/vsphere-client/

NOTE

Logging on to vCenter uses the HTTPS protocol, not the HTTP

protocol.

2. Log on to the vSphere Web Client (Figure 76) using your vCenter credentials.
Figure 76: The vSphere Web Client Logon Screen

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 91 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 3. Click the PernixData link in the left pane of the Web Client (Figure 77).
Figure 77: Accessing the PernixData Management Console in the vSphere Web Client

4. PernixData software includes a self-signed certificate used for authentication purposes. If you
use the PernixData certificate and do not install a custom CA-signed certificate, you need to add
a security exception to access PernixData software using the vSphere Web Client. The first time
you access FVP or Architect using the Web Client, the dialog box shown in Figure 78 appears.
Figure 78: Security Exception Dialog Box

Click Add Exception to add a security exception for the PernixData Management Server.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 92 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 NOTE

You can deploy an SSL certification to the Management Server by

following the instructions in PernixData KB article 1076.

5. The PernixData vSphere Web Client home page appears (Figure 79).
Figure 79: The PernixData Home Page

To view the PernixData Dashboard in the Web Client (Figure 80), expand Applications and then
click FVP.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 93 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 Figure 80: The FVP Dashboard in the vSphere Web Client

NOTE

You can also click the Launch PernixData Management

Console button to start the Management Console from within the
vSphere Web Client and automatically be logged in using your
current vCenter user account.

When you use the vSphere Web Client to access the Management Console, the Dashboard page is not
fully functional. It displays high-level summary information, but you cannot create or delete an FVP
Cluster. Clicking on the clusters opens the PernixData Management Console in a new tab, and FVP
cluster information is displayed on the new tab. The Web Client only enables you to view and work with
the Dashboard, but does not display FVP Cluster information.

NOTE

The vSphere Web Client session and the Management Console

are not linked to each other. For example, if you log off of the Web
Client, you are still logged on to the Management Console, and if
you log off the Management Console, you are still logged on to the
vSphere Web Client.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 94 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Appendix D: Connecting the Management Server Appliance to an
Existing Microsoft SQL Server Database
If you have an existing FVP installation using the Windows-based Management Server, then your
existing Microsoft SQL Server Database contains the FVP configuration and statistics. If you want to
migrate from the Windows-based Management Server to the Management Server Appliance, and you
want to preserve FVP configuration and statistics, you can connect the Management Server Appliance to
the existing Microsoft SQL Server Database. If you do this, then the Management Server Appliance uses
the Microsoft SQL Server Database instead of its built-in PostGres database, and the existing
configuration and statistics are preserved.
If you connect the Management Server Appliance to an existing Microsoft SQL Server Database, you
need to maintain Windows only for the Microsoft SQL Server Database instance.

NOTE

If there is an existing Microsoft SQL Server Database populated

with FVP configuration and history information, and you do not
connect the Management Server Appliance to that database, then
FVP does not have access to the configuration and history
information.
In this case, configure FVP in the same way as a fresh installation.
The previous history and reports are not available.

When you migrate an existing deployment from the Windows-based Management Server to the
Management Server Appliance, connecting to the existing Microsoft SQL Server Database preserves the
existing FVP configuration and statistics. Not connecting to the Microsoft SQL Server Database (and
instead using the PostGres database built into the appliance) loses the existing FVP configuration and
statistics.
If you are using Windows Authentication to access the Microsoft SQL Server Database, you must switch
the authentication method to SQL Server Authentication before you perform the migration procedure. If
you are already using SQL Server Authentication, skip this preliminary procedure and go to the migration
procedure (Step 1 on page 96).
The PernixData Management Server requires sysadmin rights to the database, so before you change the
authentication method, ensure that the database user name (see Step 3 on page 96) has sysadmin
rights. To change the authentication method from Windows Authentication to SQL Server
Authentication:
1. Follow the instructions in the Microsoft KB article Change Server Authentication Mode to enable
mixed mode authentication for the Microsoft SQL Server.
2. Locate the following configuration file on the Windows machine that contains the PernixData
Management Server:
C:\Program Files\PernixData\Management Server\Server\conf\hibernate.cfg.xml

In the hibernate.cfg.xml file, find the following line:

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 95 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 <property name="hibernate.connection.url">jdbc:sqlserver://server-
fqdn\vim_sqlexp;databaseName=prnx;integratedSecurity=true</property>

Remove the string “;integratedSecurity=true”. After you remove the string, the line
reads:
<property name="hibernate.connection.url">jdbc:sqlserver://server-
fqdn\vim_sqlexp;databaseName=prnx</property>
3. Locate the PernixData Management Server configuration file on the Windows machine that
contains the PernixData Management Server:
C:\Program Files\PernixData\Management Server\Server\conf\prnxms.config

Find the following three lines and update them as shown; if the lines are missing, add them to
the configuration:
prnxms.db.username=<db_user_name>
prnxms.db.password=<db_password>
prnxms.db.password.format=cleartext

This replaces the Windows Authentication parameters with SQL Server Authentication
parameters.

NOTE

Ensure that the user name has sysadmin rights to the database.
The PernixData Management Server requires sysadmin rights.

4. Restart the PernixData Management Server to ensure that it successfully connects to the
database. (If the connection is not successful, the Management Server UI does not start.) After
you restart the Management Server, the database password is automatically encrypted.

To migrate an existing deployment from the Windows-based Management Server to the Management
Server Appliance, follow this procedure:
1. Deploy the Management Server Appliance as described in Deploying the Management Server
Appliance.
2. Configure the powered-on appliance as described in Configuring the Management Server
Appliance.
3. Upgrade the Windows-based Management Server to the latest version so that the schema is up
to date (see the latest version of the PernixData FVP and Architect Upgrade Guide).
4. Ensure that the Windows-based Management Server starts successfully. This validates that the
Management Server can connect to the Microsoft SQL Server Database.
5. Stop the Windows-based Management Server service and disable it from automatically starting
in the future.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 96 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 6. Locate the following two configuration files on the Windows machine:
C:\Program Files\PernixData\Management Server\Server\conf\hibernate.cfg.xml
C:\Program Files\PernixData\Management Server\Server\conf\prnxms.config

You will use content from these two files to configure the Management Server Appliance to
communicate with the Microsoft SQL Server Database.
7. Change to the configuration directory on the Management Server Appliance:
cd /opt/pernixdata/pernixms/prnxms/conf

8. Back up the existing Management Server Appliance hibernate.cfg.xml file:

mv hibernate.cfg.xml hibernate.cfg.xml.back

9. Copy the Windows-based Management Server hibernate.cfg.xml file to the Management

Server Appliance opt/pernixdata/pernixms/prnxms/conf directory:
10. Open the prnxms.config file on the Management Server Appliance. Find the following line and
remove it from the configuration file:
prnxms.db.type=postgres

11. Copy the following parameters from the Windows prnxms.config file, and then replace the
analogous parameters in the Management Server Appliance prnxms.config file with the
parameters copied from the Windows prnxms.config file. The result looks like this:
prnxms.db.username=<username>
prnxms.db.password=<password>
prnxms.db.password.format=encrypted

12. Restart the Management Server Appliance. The Management Server Appliance is now
connected to the Microsoft SQL Server Database, and the existing FVP configuration and
statistics are preserved. The Management Server Appliance uses the Microsoft SQL Server
Database instead of its built-in PostGres database.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 97 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
Appendix E: Related Documentation
In addition to the PernixData FVP 3.5 and Architect 1.1 Installation Guide, PernixData provides a suite of
documents to support PernixData products. This appendix lists those documents, and provides links to
other relevant PernixData support documentation and third-party documentation:
• PernixData Guides
• Selected PernixData Support and KB Documentation
• Selected Third-Party Documentation

PernixData Guides

Most of the guides listed here are also available for older software release versions:
• PernixData FVP 3.5 and Architect 1.1 Installation Quick Start Guide for the Windows-Based
Management Server—Streamlined instructions for users who are already familiar with the
PernixData installation process and need only the commands and brief instructions to install the
Windows-based Management Server.
• PernixData FVP 3.5 and Architect 1.1 Installation Quick Start Guide for the Management Server
Appliance—Streamlined instructions for users who are already familiar with the PernixData
installation process and need only the commands and brief instructions to install the virtual
Management Server Appliance.
• PernixData FVP 3.5 and Architect 1.1 Upgrade Guide—How to upgrade to PernixData FVP 3.5
from earlier software versions.
• PernixData Release Notes (product-specific release notes, updated with each major, minor, and
issue fix release)—Release notes include descriptions of known and fixed issues, brief
descriptions of new and changed features, basic system requirements, and general information
about limitations and behaviors.
• PernixData FVP 3.5 and Architect 1.1 User Guide—How to configure and use the FVP software.
• PernixData FVP Freedom Edition 3.5 Installation Guide—Detailed instructions on how to install
the FVP Freedom Edition software.
• PernixData FVP 3.5 Freedom Edition Installation Quick Start Guide for the Windows-Based
Management Server—Streamlined instructions for users who are already familiar with the
PernixData installation process and need only the commands and brief instructions to install the
Windows-based Management Server.
• PernixData FVP 3.5 Freedom Edition Installation Quick Start Guide for the Management Server
Appliance—Streamlined instructions for users who are already familiar with the PernixData
installation process and need only the commands and brief instructions to install the virtual
Management Server Appliance.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 98 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • PernixData FVP 3.5 Freedom Edition Upgrade Guide—Detailed instructions on how to upgrade
the FVP Freedom Edition software.
• PernixData FVP 3.5 Freedom Edition Uninstallation Guide—Detailed instructions on how to
uninstall FVP Freedom Edition software.

Selected PernixData Support and KB Documentation

The PernixData customer support website (https://support.pernixdata.com) includes Knowledge Base

(KB) articles and other documentation. The support web site requires a login. If you are a customer and
you do not have a support login, email [email protected]. Here is a selection of useful support
site links (the support site has many more articles and resources than listed below):
• PernixData Support Matrix—Compatibility information, including:
• A matrix of ESXi host version vs. PernixData Host Extension Module support.
• Web browser support matrix.
• SQL Server, Windows, and Java support matrix.

• Moving the Management Server from the Current Server to a New Server (KB 1211)—How to
move the PernixData Management Server from one server to another server.

• Management Server and Java Autoupdate (KB 1333)—Java autoupdate issues.

• Find Management Server and Host Extension Module Version (KB 1261)—FVP UI and PowerShell
methods for viewing the PernixData Management Server and Host Extension Module versions.

• PernixData FVP 2.5 PowerShell Guide—Windows PowerShell cmdlet reference guide. You can
find the link to this guide on the PernixData Support website, on the Documents and Downloads
tab, at the bottom of the page in the FVP 2.5.0.x box.

• Updating PowerShell Cmdlets (KB 1338)—Newer versions of PernixData software might expect
different settings in some policy parameters than the settings created using older PowerShell
cmdlets. This article shows you how to update the PowerShell cmdlets to match the latest
installed version of PernixData software.

• Creating Custom SLL Certificates for FVP (KB 1076)—How to replace the certificate for the
PernixData Management Server.

• Default Core Dump Slot Size is Not Large Enough on ESXi 5.0 and 5.1 (KB 1189)—How to
increase the core dump slot size.

• Proxy Server Settings (KB 1312)—Procedure to enable Internet access by configuring a proxy
server.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 99 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345
 • How to specify a non-default TCP port for SQL Server when used by FVP (KB 1216)—Procedure
to use if your SQL Server uses a non-standard TCP port.

Selected Third-Party Documentation

Because FVP runs in VMware environments, knowledge about ESXi hosts and VMware in general can be
helpful when working with FVP. Here is a selection of useful links to VMware documents:
• http://www.vmware.com/products/vsphere—Information about VMware vSphere products.
• VMware RBAC documentation—Role based access control information.
• KB 1033696—Creating a persistent scratch location for ESXi 4.x and 5.x.
• KB 2004299—Configuring a diagnostic coredump partition on an ESXi 5.x/6.0 host.
• KB 1004128—Collecting diagnostic information from an ESX or ESXi host that experiences a
purple diagnostic screen.
• KB 1002769—Extracting a core dump file from the VMKCore diagnostic partition following a
purple diagnostic screen error.

PernixData FVP 3.5 and Architect 1.1 Installation Guide Page 100 of 100
© 2016, PernixData, Inc. All rights reserved. Confidential. ERN R104345