Virtual Appliance - ESX¶
To deploy the Plixer FlowPro virtual appliance for ESX environments, take note of the following additional requirements and proceed with the subsequent setup process:
The Plixer FlowPro virtual appliance for ESX is provided as an all-in-one OVF template to streamline the deployment process.
20GB SATA drive
2.0 GHz Quad Core CPU
Deploying the OVF Template¶
After downloading the latest version of the Plixer FlowPro virtual appliance, connect to the ESX host where the appliance will be deployed using VMware, vSphere, or vCenter.
Select File > Deploy OVF Template.
Select Deploy from File, navigate to the OVF Template, and click Next.
Review the OVF template details and click Next.
Provide a name for the Plixer Scrutinizer virtual appliance and continue to follow the deployment wizard.
Review the Virtual Settings, and click Finish to complete importing the OVF Template.
The virtual appliance is configured with 2 network adapters (mgmt and mon1), with mon1 already in promiscuous mode. By default, it will start listening for traffic on the default virtual network. A mirror port of a Virtual Distributed Switch or a mirror port using a physical NIC on the ESXi host will have to be configured if a different network needs to be monitored.
Power on the Plixer FlowPro virtual machine.
Navigate to the Console tab and log in using the username
After the machine performs a quick setup and reboots, log in again with the same credentials and enter the answers to the configuration questions that follow.
After the Plixer FlowPro reboots to apply the new settings, log in with the new credentials
entered during the previous step.
edit licensecommand to enter the license key.
Paste the license key between the EOT markers after the label
license=in the [Client] section of the plixer.ini file. The license key may span multiple lines.
Press CTRL+X to save.
The interface must be enabled for the Plixer FlowPro processes that will run on that interface using the enable command.
For example, to activate Plixer FlowPro Defender montoring on mon1:
enable defender mon1
The commands to enable the other Plixer FlowPro processes on specific interfaces are:
enable apm \<interface\> \<apmMode\> <enable_apm>
enable flowpro \<interface\> <enable_flowpro>
When adding additional monitoring interfaces to the virtual appliance, be sure to use the interface naming convention monX so that Plixer FlowPro recognizes them as monitoring interfaces (for example: mon1, mon2).
Upgrading the Virtual Machine Hardware Version¶
To upgrade the Virtual Machine hardware version:
Shut down the virtual machine.
Right-click on the virtual machine in vSphere (or vCenter) and select Upgrade Virtual Hardware.