HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

network:adapter-type:[hardware-address]:vswitch:vswitch-name
The guest virtual network device information consists of the following fields, separated by colons:
• network
• adapter-type, which can be either lan or avio_lan
• [hardware-address] (optional), formatted as bus,device,mac-addr. If you do not
specify the hardware address, or a portion of it, the information is generated for you. HP
recommends allowing Integrity VM to generate the hardware address. The hardware address
consists of the following information:
◦ bus (virtual network device PCI bus number)
◦ device (virtual network device PCI slot number)
◦ mac-addr (the virtual network device MAC address) in either of the following formats:
0xaabbcc001122 or aa-bb-cc-00-11-22. The MAC address that you enter is checked
to make sure it does not conflict with any of the VSP’s physical network adapter MAC
addresses.
• vswitch
The virtual switch information is formatted as vswitch:vswitch-name (where
vswitch-name is the name assigned to the virtual network switch when you create it using
the hpvmnet command)
10.3.1 Adding vNICs
You can define a vNIC for a guest using the hpvmmodify command. For example, the following
command adds a vNIC to the guest named host1.
# hpvmmodify -P host1 -a network:lan:0,0,0x00306E39F70B:vswitch:clan1
The guest configuration file /var/opt/hpvm/guests/guestname/vmm_config.current
contains an entry for each guest virtual network device. When the guest is booted (through the
hpvmstart or hpvmconsole command), the guest LAN is configured as specified in the LAN
entry in the guest configuration file. For example:
.
.
.
# Virtual Network Devices
#
lan(0,0).0x00306E39F70B = switch(clan1).4
.
.
.
The localnet vswitch can be used as a local network ,and vNICs can be specified for a guest.
For example:
# hpvmmodify -P host1 -a network:lan::vswitch:clan0
NOTE: Never modify the guest configuration files directly. Always use the Integrity VM commands
to modify virtual devices and virtual machines. Failure to follow this procedure can result in
unexpected problems when guests are started.
10.3 Managing vNICs 151