To use DvFilter virtual switches in solutions, you must specify in the Open Virtualization Format (OVF) descriptor which components represent the ethernet adapter for DvFilter data and which components represent the ethernet adapter for DvFilter control.

You When using a DvFilter virtual machine, an ESX agent virtual machine requires at least two types of ethernet adapter.

One or more ethernet adapters to control the DvFilter virtual switch

One or more ethernet adapters for data

Optionally, one or more management networks

When you deploy ESX agent virtual machines, you can obtain information about the configuration of the DvFilter virtual switch on the ESX host. You can also obtain information about the MAC addresses that are assigned to the ethernet adapters that the DvFilter switch uses for data and control. You must also set the dvFilterEnabled Boolean value to true in the configuration of the ESX agent. See Configure an ESX Agency and ESX Agents.

When the solution deploys and powers on an ESX agent virtual machine, you can read the OVF environment in the guest. The OVF environment lists the Ethernet adapters and provides the OVF network name and MAC address for each adapter. By reading this list you can determine from the guest which Ethernet card is connected to which OVF network.

You have a solution that installs a DvFilter virtual switch on the ESX server on which it operates.

1

Verify that the ESX agent virtual machine that you deploy from OVF has a CD-ROM drive.

2

Set the OVF transport mechanism to ISO in the OVF descriptor file.

<VirtualHardwareSection ovf:transport="iso">

When the ESX agent virtual machine runs, it reads the OVF environment from the ovf-env.xml file on the CD-ROM. The EAM Sample Solution creates empty virtual machines, so it does not read the OVF environment.

Note

Some operating systems require you to mount the CD-ROM drive first.

3

Add entries in the <NetworkSection> element of the OVF descriptor for the data and control networks of the DvFilter virtual switch.

<NetworkSection>
 <Info>The list of logical networks</Info>
 <Network ovf:name="eam-data">
   <Description>The dvFilter data network</Description>
 </Network>
 <Network ovf:name="eam-control">
   <Description>The dvFilter control network</Description>
 </Network> 
 ...
 ...
</NetworkSection>
4

In the <VirtualHardwareSection><Item> elements of the OVF descriptor, specify the network for the ethernet adapter that the DvFilter virtual switch uses for control.

<Item>
  ...
  <rasd:Connection>eam-control</rasd:Connection>
  ...
</Item>
5

In the <VirtualHardwareSection><Item> elements of the OVF descriptor, specify the network for the Ethernet adapter that the DvFilter virtual switch uses for data.

<Item>
  ...
  <rasd:Connection>eam-data</rasd:Connection>
  ...
</Item>
6

Specify any other Ethernet adapters that the solutiuon requires for network management.

7

In the AgentConfigInfo implementation in the program that manages ESX agents in your solution, set the dvFilterEnabled Boolean value to true and provide a URL to the offline vSphere installation bundle (VIB) that contains the DvFilter virtual switch.

You configured the OVF descriptor for an ESX agent virtual machine to use a DvFilter virtual switch.