HP Integrity Virtual Server Manager 6.3 User Guide

With HP Integrity VM, AVIO requires a vswitch that has a physical network device as the
backing device (local vswitches such as localnet are not supported). In addition, the physical
NIC that backs the virtual switch must have an AVIO-compatible driver.
For more information about AVIO requirements, see the HP Integrity Virtual Machines
documentation available at http://www.hp.com/go/hpux-hpvm-docs.
Create the virtual switch by performing the following steps:
1. (Required) Enter a virtual switch name.
• The name must be 8 characters or fewer.
• The allowable characters are A-Z, a-z, 0-9, dash (-), underscore (_), and period (.).
• The name cannot begin with a dash and cannot remain blank.
2. Specify the virtual switch type (whether it is to be dedicated or shareable). The default is
shareable.
NOTE: The terms "shareable" and "dedicated" refer to how the switch is assigned to the
VMs.
• A dedicated vswitch can be used by only one started VM at a time and is dedicated to
providing network throughput to that VM. More than one VM can have the same dedicated
switch as a resource, but only one is allowed to start.
• A shareable vswitch can be used at any given time by all the associated VMs that contain
the virtual network device (NIC) backed by a shareable vswitch.
NOTE: All VMs with virtual NICs backed by a shareable vswitch are not required to
be running. If you have a stopped VM that uses the shareable vswitch, you can always
start the VM (unless other problems prevent it from starting).
3. (Required) From the table, select the VSP's physical network device that will be the physical
backing of the vswitch.
Choices include the following:
• Any physical network cards (adapters) configured on the VSP
• Any APA (Automatic Port Aggregation) configured on the VSP
The display shows the APA name in one column and the individual devices or cards in
the next column; however, the letters "APA" do not appear in either column. In HP-UX,
any LAN port with port number 900 or greater is an APA (for example, lan900 or lan901).
• None
This creates a local vswitch. When no physical network device on the VSP is chosen, the
vswitch is a local vswitch. A local vswitch has no connection with any physical network
device on the VSP. VM virtual network interface cards (vNICs) can communicate only
with other VMs on the same VSP that are connected to the same local vswitch.
4. Specify whether or not to start the vswitch after it is created. The default is to start the vswitch.
Clicking OK does the following:
• Creates the new vswitch, using the hpvmnet command.
• If you chose to make the vswitch dedicated, configures the vswitch as a dedicated vswitch,
using the hpvmdevmgmt command.
• If you chose to have the switch started, starts the vswitch, using the hpvmnet command.
A preview of these commands is shown in the Command Preview area. After you click OK, any
errors that occur with the execution of these commands is displayed on a separate error page that
106 Working with VMs or vPars