This section lists the release notes associated with virtual networks.
Vswitches are always in SHARED mode |
 |
The hpvmnet command displays the status of the vswitches,
including the mode. The vswitches are always in SHARED mode. This indicates
that the vswitch is set to promiscuous mode. Dedicated (non-promiscuous) mode
is not used.
Do not use the HP A5506B PCI 10/100Base-TX 4 Port interface for virtual
networking |
|
Host to guest connectivity may not be reliable when using the HP A5506B
PCI 10/100Base-TX 4 Port interface for guest networking.
MAC address validation can be enhanced |
|
When you add a virtual NIC to your guest, Integrity VM checks to make
sure the MAC address is unique.
By default, Integrity VM makes three attempts (each with a one-second
timeout) to determine the validity of the MAC address for the virtual NIC.
This process can result in up to ten seconds of delay for each defined virtual
NIC. To speed up this processing, add the following tunable to the /etc/rc.config.d/hpvmconf configuration
file:
Where n is the number of attempts
(1 to 30). The default is 3. A value of 1 or 2 increases performance at the
risk of missing a response from a slow NIC. Do not set the HPVMMACADDRFRAMES
tunable to 0. Setting this tunable to 0 can result in a virtual NIC having
a duplicate MAC address with another virtual or physical NIC.The first guest
to boot obtains the MAC address, so a guest with a duplicate MAC address would
fail to boot.
To boost virtual network performance, create additional vswitches and
allocate them across guests.
Auto port aggregation (APA) is supported on the VM Host, not the guest |
|
Integrity VM does not support running APA in the guest. You can run
APA on the VM Host.
APA can be configured on the VM Host to provide a highly available LAN
for the vswitch (APA in active/passive mode) or to increase the bandwidth
of the vswitch LAN (APA active/active mode). Before you stop APA, halt the
vswitches associated with it. Use the hpvmnet -h command
to halt the vswitches. If you do not halt the vswitch first, the hpvmnet command
reports an incorrect MAC address for the vswitch.
Do not run applications that set network devices into promiscuous mode |
|
Vswitches must not be connected to network devices that are set to promiscuous
mode. Do not run applications like tcpdump on the VM
Host on interfaces that are used for virtual switches.
Do not turn on TSO on the VM Host and on HP-UX guests |
|
TCP Segmentation Offload (TSO) is turned off by default in HP-UX. HP
recommends that you leave it turned off on both the VM Host system and on
HP-UX guests. This applies to both the virtual network interface cards in
the guest and any physical network interface cards in the VM Host that are
used by vswitches. Turning on TSO results in guest network interruption.
To verify whether TSO is turned on, enter the following command:
Where n is theVM Host interface, as displayed
by the hpvmnet. For example, to verify that lan0 is
on, enter the following command:
# lanadmin -x vmtu 0
Driver/Hardware supports TCP Segmentation Offload, Current VMTU = 32160
|
To turn TSO off on lan0, use the following
command:
# lanadmin -X vmtu 0 0
Virtual MTU is set to 0
|
Do not configure VLAN vswitches on HP-UX VLANs |
|
Do not use the hpvmnet command to create a virtual
switch that is associated with a VLAN port on the VM Host (that is, a LAN
created with lanadmin -V). This “nested VLAN” configuration
is not supported.
For VLANs between VM Host and guests, turn off CKO |
|
When you use a VLAN for communication between guests and the VM Host,
turn off transmit checksum offload (CKO) on the network interface used by
the vswitch. On the VM Host, identify the PPA of the network interface for
the vswitch using the hpvmnet command. For example:
# hpvmnet
Name Number State Mode PPA MAC Address IP Address
======== ====== ======= ========= ====== ============== ===============
localnet 21 Up Shared N/A N/A
vmlan0 22 Up Shared lan0 0x00306ea72c0d 15.13.114.205
vmlan4 23 Up Shared lan4 0x00127942fce3 192.1.2.205
vmlan900 24 Up Shared lan900 0x00306e39815a 192.1.4.205 |
Check the status of the transmit CKO using the following command:
# lanadmin -x cko 4
Hardware TCP/UDP (IPv4) transmit checksum offload is currently enabled.
Hardware TCP/UDP (IPv4) receive checksum offload is currently disabled.
|
In this example, the VLANs are configured over the vswitch vmlan4.
This vswitch is created on PPA 4 on the VM Host. To turn off CKO on PPA 4,
enter the following command on the VM Host:
# lanadmin -X send_cko_off 4
Hardware TCP/UDP (IPv4) transmit checksum offload is currently disabled.
|
Restarting vswitches |
|
It is necessary to restart the vswitch when:
You replace the physical network card associated with the
vswitch.
You change a VM Host IP address associated with the vswitch's
network interface card.
You change the network interface characteristics on the VM
Host; for example, by using the lanadmin command to change
checksum offloading (CKO).
For information about how to restart vswitches, see the HP
Integrity Virtual Machines Installation, Configuration, and Administration manual.
When you restart a vswitch, it is not necessary to restart the guests
using the vswitch.
Printable version
