HP Integrity Virtual Machines Installation, Configuration, and Administration

8.4.3 Configuring VLANs on Physical Switches
When communicating with a remote VM Host or guest over the network, you might need to
configure VLANs on the physical switches. The physical switch ports that are used must be
configured specifically to allow the relevant VLANs. If the remote host is VLAN aware, You
must configure VLAN interfaces on the host for the relevant VLANs. Use the lanadmin(1M)
command to configure VLANs on a remote HP-UX host. For example, to configure a VLAN
interface with VLAN ID 100 on lan4, enter the following command:
# lanadmin -V create vlanid 100 4
Successfully configured
lan5000: vlanid 100 name UNNAMED pri 0 tos 0 tos_override IP_HEADER pri_override CONF_PRI ppa 4
8.5 Troubleshooting Network Problems
This section describes some commonly encountered problems using virtual networks.
• Do not kill hpvmnetd
Do not use the kill command to remove the hpvmnetd process. If you do, the following
error message indicates that the hpvmnet daemon has been killed:
hpvmnetd: Switch 0000564d4c414e31 already exists
If the hpvmnetd process is removed, vswitches do not work properly.
8.5.1 Redefining PNICs for HP-UX Guests
Changing the hardware address of a vswitch has the same effect as moving a nework adapter
from one hardware slot to another on an HP Integrity system. Similar to other HP-UX systems,
the guest file /etc/rc.config.d/netconf must be modified so that INTERFACE_NAME[0]
reflects the new LAN PPA assigned by the HP-UX network driver on the first guest reboot after
the modification. At this first reboot, the LAN interfaces configuration fails, as follows:
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.
8.5.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.
110 Creating Virtual Networks