Cisco Cisco Process Orchestrator 3.1 User Guide
13-172
Cisco Process Orchestrator 3.1 User Guide
Appendix 13 Using Adapters
VMware vCenter, ESX, and ESXi Adapter
- independent_persistent—The disk operates normally except that changes to the disk are
permanent even if the virtual machine is reverted to a snapshot.
permanent even if the virtual machine is reverted to a snapshot.
- persistent—All disk writes issued by software running inside a virtual machine are
immediately and permanently written to a virtual disk that is configured as an independent disk.
immediately and permanently written to a virtual disk that is configured as an independent disk.
–
Time out if not completed within—Check the check box and enter the time period the activity
should wait for completion before failing. Click the time unit link to change the time interval
should wait for completion before failing. Click the time unit link to change the time interval
Step 5
Enter the information in the remaining tabs as necessary, then click Save to complete the activity
definition.
definition.
Adding a Network Adapter to a Virtual Machine
Use the Add VM Network Adapter activity to add a network adapter to a specified virtual machine.
Step 1
In the Process Editor Toolbox, choose VMware vSphere > Add VM Network Adapter, then drag and
drop the activity onto the Workflow pane.
drop the activity onto the Workflow pane.
Step 2
Click the General tab and enter the appropriate information.
Step 3
Click the Network Adapter Settings tab and specify the following properties:
•
Virtual machine—Enter the inventory path to the virtual machine. The information in this field is
case-sensitive. For example:
case-sensitive. For example:
TEST-ENV/UCS/vm/TESTDEV-W2K8-64-02
•
Adapter type—select the appropriate network adapter type.
–
E1000—Emulates the functioning of an E1000 network card. It is the default adapter type for
virtual machines that run 64-bit guest operating systems.
virtual machines that run 64-bit guest operating systems.
–
Flexible—Supported on virtual machines that were created on ESX Server 3.0 or greater and
that run 32-bit guest operating systems.
that run 32-bit guest operating systems.
–
Vlance—An emulated version of the AMD 79C970 PCnet32- LANCE NIC, an older 10Mbps
NIC with drivers available in most 32-bit guest operating systems except Windows Vista and
later.
NIC with drivers available in most 32-bit guest operating systems except Windows Vista and
later.
–
VMXNET—This virtual network adapter has no physical counterpart and is optimized for
performance in a virtual machine. Because operating system vendors do not provide built-in
drivers for this card, VMware Tools must be installed to have a driver for the VMXNET network
adapter available.
performance in a virtual machine. Because operating system vendors do not provide built-in
drivers for this card, VMware Tools must be installed to have a driver for the VMXNET network
adapter available.
–
VMXNET 2—The VMXNET 2 adapter is based on the VMXNET adapter but provides some
high-performance features commonly used on modern networks, such as jumbo frames and
hardware offloads. This virtual network adapter is available only for some guest operating
systems on ESX/ESXi 3.5 and later. VMXNET 2 is supported only for a limited set of guest
operating systems
high-performance features commonly used on modern networks, such as jumbo frames and
hardware offloads. This virtual network adapter is available only for some guest operating
systems on ESX/ESXi 3.5 and later. VMXNET 2 is supported only for a limited set of guest
operating systems
–
VMXNET 3—The VMXNET 3 adapter offers all the features available in VMXNET 2, and
adds several new features like multiqueue support, IPv6 offloads, and MSI/MSI-X interrupt
delivery. VMXNET 3 is supported only for virtual machines version 7 and later, with a limited
set of guest operating systems
adds several new features like multiqueue support, IPv6 offloads, and MSI/MSI-X interrupt
delivery. VMXNET 3 is supported only for virtual machines version 7 and later, with a limited
set of guest operating systems
•
Network—Enter the inventory path of the virtual network to use for this adapter.
•
Connect on power on—Check this check box to indicate that the host should be connected when it
was started.
was started.