Installing components

If you are deploying into an ESX/ESXi 4.x or 5.x environment, you can install the component from the template as downloaded. For installations into an ESX/ESXi 3.5 environment, you must first convert the descriptor file.

Before you begin

After you have downloaded the installation files, unzip each distribution package and save its components to one of the following locations:

  • A file system local to your virtualization environment
  • A network server accessible to your virtualization environment

To install the component

  1. Log on to the host via VMware vSphere Client software and select Deploy OVF template.
  2. Select a source for the descriptor file.
    You can select it from a file storage location or a website, depending on where you saved the extracted content of the distribution package.
  3. When you see the OVF template details, click Next.
  4. Type a unique name to identify this component.
  5. Select the network interface for your management and capture ports (for 

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    instances).
  6. Confirm your selection and click Finish to proceed with the import.

Next, allocate resources to the component according to the level of performance that you want. (For guidance, see Deployment-architecture and Sizing-considerations.) Then, switch the power ON, access the web interface, and verify the IP address (or assign a static IP address). Finally, complete the setup process by pointing a web browser to the IP address of the management port of the component.

Notes

For the Collector component:

  • The descriptor file for the Collector is preconfigured with the following network interfaces: a management port and a capture port. You must add them to appropriate virtual ports in your inventory. The management port requires a virtual network adapter. In the VMware vSphere Client or the VMware management console, the management network is listed first.
  • Each Collector instance can have as many as four capture ports. You must add a virtual network adapter for each capture port.
  • Capture ports must have Promiscuous Mode/Accept enabled.

For the Analyzer component:

  • The descriptor file for the Analyzer is not preconfigured with a storage disk. To store a large volume of data, you must configure a disk between 100 and 570 GB in size.
  • If you change the size of the storage disk after the Analyzer has saved data to it, all data is lost when you reboot the component instance.

To convert the component descriptor file for ESX/ESXi 3.5 deployment

Because VMware ESX 3.5 supports only version 0.9 of the OVF standard, you cannot deploy the

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

component templates directly on that version of the host. First, you must download a conversion tool (for example, VMware vCenter Converter) and use it for the deployment operation.

Note

VMware discontinued support for the OVF format in vCenter Converter 4.3. If possible, use version 4.0.

Using the converter requires a similar procedure to that of a OVF 1.0 deployment.

Warning

If you have a choice of deployment templates (OVF files), you must not choose a file that has resource dependencies that would exceed the capacity of VMware ESX 3.5.

  1. In VMware vCenter Converter, click Convert Machine, which launches a conversion wizard.
  2. On the first screen, select the source, which should be virtual appliance.
    Identify the location of the descriptor file provided in the distribution package.
  3. Enter a location for the installed appliance:
     For an ESX 3.5 host, select VMware Infrastructure virtual machine and type the server IP address, a valid user name, and the password.
  4. Select the location of the virtual machine, its name, and the storage to be used for it.
     Some delay occurs before validation.
  5. Change the parameters of the virtual machine before conversion.
  6. Adjust the memory, processor, network, and disk allocations according to your needs.

Following validation, the system shows a summary of the conversion tasks to be performed. After the conversion, boot the component and proceed with the setup process.

Notes

  • You can use vMotion to migrate components of this product. However, be aware that vMotion requires that all resources used by the virtual machine be on the current host and that they be shared. If this is not the case, you cannot perform live migrations via vMotion. This is a VMware limitation.
  • Cloning is not supported in this version.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*