HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

Configure LAN interfaces ............................ . FAIL
*
When the guest is running, you can use the lanscan command to identify the new LAN PPA and
to modify netconf. For example:
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/5/0 0x02636C6E3030 1 UP lan3 snap3 1 ETHER Yes 119
In the preceding example, before the modification, the LAN PPA was 0. The new LAN PPA on the
first boot after the modification is 3. Therefore, you must first bring the guest network down, then
you must change the INTERFACE_NAME[0] from lan0 to lan3. You can then use /sbin/
rc2.d/S340net to restart the guest network. For example:
# /sbin/rc2.d/S340net stop
# ch_rc -a -p "INTERFACE_NAME[0] = "lan3"
# /sbin/rc2.d/S340net start
The guest network begins to function.
10.6.2 Troubleshooting VLAN problems
When VLANs are configured on the vswitch, the partitioned LAN must have its own set of network
servers to service requests on the VLAN. For example, the VLAN's DNS server or a router setup
on the VLAN should be set up on the VLAN. If guests start slowly or hang during starting, determine
whether the guest network interface is on a VLAN, and whether the appropriate network services
(like DNS) are set up and available on the VLAN. You might need to either set up the appropriate
services on the VLAN, or disable some of these network services on the guest before booting up
the guest on a VLAN.
When VLANs are configured on the vswitch and the guests are required to communicate over a
VLAN with a remote node outside the VSP, you might need to set up the physical network
appropriately for the VLAN. For information about configuring VLANs on the switches, see the
product documentation for the physical network adapters.
If TCP/UDP applications have trouble communicating between a guest and the local VSP over a
VLAN, it is possible that the host interface for the vswitch is checksum-offload capable. To resolve
the problem, identify the interface used by the vswitch and run the following command on the VSP
to disable the CKO feature, where 4 is the VSP interface as shown in the hpvmnet command
output.
# lanadmin -X send_cko_off 4
Hardware TCP/UDP (IPv4) transmit checksum offload is currently disabled
Checksum offloading (CKO) is not supported. On most of the physical interfaces that are not of
10 Gigabyte type, CKO is turned off by default. Consult your interface card documentation for
details.
Turning on CKO can cause host-to-guest connections as well as guest-to-host communication over
a VLAN to fail. If you are receiving failures with host-to-guest connections or guest-to-host
communication using a VLAN, ensure that the CKO is turned off in the host interface driver. If that
does not fix the problem, reboot the vswitch.
To turn off the CKO on the VSP, 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
10.6 Troubleshooting network problems 163