{"id":13867,"date":"2015-09-23T10:00:00","date_gmt":"2015-09-23T08:00:00","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=13867"},"modified":"2015-11-15T11:42:22","modified_gmt":"2015-11-15T10:42:22","slug":"pernixdata-fvp-3-0-configuration-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/pernixdata-fvp-3-0-configuration-pt-2\/","title":{"rendered":"PernixData FVP 3.0 configuration - pt. 2"},"content":{"rendered":"

\"fvp30configuration01\"<\/p>\n

PernixData FVP 3.0 configuration allows the administrators to enable the use of host-installed Flash and RAM to accelerate storage performance.<\/p>\n

The configuration process includes licensing, setup of acceleration resources and Datastores\/VMs to accelerate.<\/p>\n

<\/p>\n

 <\/p>\n

Blog series<\/h2>\n

PernixData FVP 3.0 installation - pt.1<\/a>
\nPernixData FVP 3.0 configuration - pt.2<\/p>\n

 <\/p>\n

License activation<\/h2>\n

FVP 3.0 introduced a new and easier way to manage licensing: you only need a valid license key<\/strong> and the activation takes places without further configuration.<\/p>\n

First step to perform before configuring FVP is the license activation<\/strong>.<\/p>\n

From your favorite browser access the FVP Management Console typing the address http:\/\/FVP_address:60001\/login<\/strong>. Enter\u00a0the correct credentials then click Login<\/strong>.<\/p>\n

\"fvp30configuration02\"<\/p>\n

 <\/p>\n

Start the trial<\/h4>\n

Select Licensing<\/strong> tab, select the vCenter to configure and click Start Trial<\/strong>.<\/p>\n

\"fvp30configuration03\"<\/p>\n

Click OK<\/strong> to activate the trial.<\/p>\n

\"fvp30configuration04\"<\/p>\n

The product has been activated.<\/p>\n

\"fvp30configuration05\"<\/p>\n

 <\/p>\n

Enter the license<\/h4>\n

If you bought the license, select Licensing<\/strong> tab and the vCenter to configure then click + Enter FVP License Key<\/strong>\u00a0option.<\/p>\n

\"fvp30configuration06\"Enter the License Key<\/strong>\u00a0and\u00a0click OK<\/strong>.<\/p>\n

\"fvp30configuration07\"<\/p>\n

The product has been activated.<\/p>\n

\"fvp30configuration08\"<\/p>\n

 <\/p>\n

Create a FVP Cluster<\/h2>\n

From PernixData Hub<\/strong> menu, select FVP<\/strong> to access the configuration page.<\/p>\n

\"fvp30configuration09\"<\/p>\n

Click + Create<\/strong> to create a FVP Cluster.<\/p>\n

\"fvp30configuration10\"<\/p>\n

Enter a Name<\/strong>, select the vSphere Cluster<\/strong> then click OK<\/strong>.<\/p>\n

\"fvp30configuration11\"<\/p>\n

The new FVP Cluster has been created successfully. Click the cluster name to access the setup page<\/strong>.<\/p>\n

\"fvp30configuration12\"<\/p>\n

From this page you can monitor and configure<\/strong> the FVP Cluster.<\/p>\n

\"fvp30configuration13\"<\/p>\n

 <\/p>\n

Add acceleration resources<\/h2>\n

Select the Configuration<\/strong> tab and click + Add<\/strong> to add Acceleration Resources<\/strong>.<\/p>\n

\"fvp30configuration14\"<\/p>\n

Same setup can be done from the dropdown menu.<\/p>\n

\"fvp30configuration15\"<\/p>\n

Select an option from the Resource Type<\/strong> menu to filter available resources.<\/p>\n

\"fvp30configuration16\"<\/p>\n

Select the resources to use and click OK<\/strong>. Just remember you can't add Flash and RAM<\/strong> from\u00a0the same server.<\/p>\n

\"fvp30configuration17\"<\/p>\n

Selecting RAM<\/strong> as resource instead, you need to specify the amount of memory to allocate. Click Done<\/strong> then\u00a0OK<\/strong> to save the setup.<\/p>\n

\"fvp30configuration18\"<\/p>\n

The selected resources have been\u00a0added to the cluster.<\/p>\n

\"fvp30configuration19\"<\/p>\n

 <\/p>\n

Add Datastores\/VMs to the FVP Cluster<\/h2>\n

Select Datastores\/VMs<\/strong> item and click + Add Datastores<\/strong> to add datastores to accelerate.<\/p>\n

\"fvp30configuration20\"<\/p>\n

In the screen are listed the supported datastores VMFS and NFS<\/strong> type. Select the Datastore to add to the FVP Cluster, specify the Write Policy<\/strong> and click OK<\/strong> to confirm.<\/p>\n

\"fvp30configuration21\"<\/p>\n

Two Write Policies type can be used:<\/p>\n

\"fvp30configuration22\"<\/p>\n

Click + Add VMs<\/strong> to add VMs to accelerate.<\/p>\n

\"fvp30configuration23\"<\/p>\n

From the list, select VMs to add to the FVP Cluster and specify the Write Policy<\/strong>\u00a0to use. You have to specify also the Write Replication<\/strong> if Write Back<\/strong> mode is chosen. Click OK<\/strong> to save the configuration.<\/p>\n

\"fvp30configuration24\"<\/p>\n

The VM is added to the FVP Cluster.<\/p>\n

\"fvp30configuration25\"<\/p>\n

 <\/p>\n

Configure Fault Domains<\/h2>\n

Fault Domains is a feature useful to control where the replica lands<\/strong> when the Write Back mode<\/strong> is used. By default the hosts configured in the FVP Cluster are identified under Default Fault Domain<\/strong> area.<\/p>\n

Click Add Fault Domain<\/strong> button to create Fault Domains. In the example two Fault Domains are created: fault01<\/em> and fault02<\/em>.<\/p>\n

\"fvp30configuration26\"<\/p>\n

During the Fault Domain configuration, you can add hosts in any order<\/strong> and control where the replica lands when VMs run in any host in Fault Domain. Type a Name<\/strong> then click OK<\/strong>.<\/p>\n

\"fvp30configuration27\"<\/p>\n

To logically partition<\/strong> the host, click the + plus icon<\/strong> to add a host to first Fault Domain. Select a host from the list and click OK<\/strong> to confirm.<\/p>\n

\"fvp30configuration28\"<\/p>\n

Repeat same step<\/strong> for the second Fault Doman.<\/p>\n

\"fvp30configuration29\"<\/p>\n

 <\/p>\n

Associate Fault Domains<\/h4>\n

To associate Fault Domains click the + plus icon<\/strong> in the Target<\/strong> area of the Fault Domain (i.e. fault01<\/em>) you want to configure. From the available Fault Domains, select the one (i.e. fault02<\/em>) you want to associate then click OK<\/strong> to confirm.<\/p>\n

\"fvp30configuration30\"<\/p>\n

Do the same for the fault02<\/em> Fault Domain.<\/p>\n

\"fvp30configuration31\"<\/p>\n

The result is that VMs running in fault01<\/em> host will have the replica landing<\/strong> in fault02<\/em> Fault Domain.<\/p>\n

\"fvp30configuration32\"<\/p>\n

If due to DRS or custom rules<\/strong> the VMs move to different hosts in fault01<\/em> or fault02<\/em>, the replication is automatically changed<\/strong>.<\/p>\n

 <\/p>\n

Advanced setup<\/h2>\n

In the Advance tab you can configure Blacklist, VADP and Network Configuration.<\/p>\n

 <\/p>\n

Blacklist<\/h4>\n

To ensure a VM is never accelerated<\/strong>, click + Add VMs<\/strong> to add the VM to the black list.<\/p>\n

\"fvp30configuration33\"<\/p>\n

 <\/p>\n

VADP<\/h4>\n

Specify VADP VMs in your environment so that FVP works seamlessly with relevant backup processes. VADP VMs won't be accelerated<\/strong> by FVP.<\/p>\n

\"fvp30configuration34\"<\/p>\n

 <\/p>\n

Network Configuration<\/h4>\n

By default FVP choses the vMotion network<\/strong> for the acceleration traffic, but you can specify a different network.<\/p>\n

\"fvp30configuration35\"<\/p>\n

Click Edit Networks<\/strong> to change the network to use. You have two options available.<\/p>\n

\"fvp30configuration36\"<\/p>\n

One network for all hosts<\/strong> option. Select the network to use then click OK<\/strong> to confirm.<\/p>\n

\"fvp30configuration37\"<\/p>\n

A network per host<\/strong> option. Select the network to use for the hosts in the cluster then click OK<\/strong> to confirm.<\/p>\n

\"fvp30configuration38\"<\/p>\n

 <\/p>\n

Reporting<\/h2>\n

From the Reporting<\/strong> tab, you have some analytics<\/strong> useful to figure out the FVP Cluster behavior.<\/p>\n

\"fvp30configuration39\"<\/p>\n

The configuration of PernixData FVP 3.0 is now complete.<\/p>\n

\"firma\"<\/p>\n","protected":false},"excerpt":{"rendered":"

PernixData FVP 3.0 configuration allows the administrators to enable the use of host-installed Flash and RAM to accelerate storage performance. The configuration process includes licensing, setup of acceleration resources and Datastores\/VMs to accelerate.<\/p>\n","protected":false},"author":3,"featured_media":13829,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[987,903],"tags":[1068,1614,960,629],"class_list":["post-13867","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pernixdata-en","category-vmware-en","tag-configuration-en","tag-fvp-3-0","tag-pernixdata-en","tag-setup-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/13867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=13867"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/13867\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/13829"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=13867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=13867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=13867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}