HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

Port Number : 3
Port State : Active
Active VM : vm2
Untagged VlanId : none
Reserved VMs : vm2
Adaptor : avio_lan
Tagged VlanId : none
Port Number : 4
Port State : Active
Active VM : vm2
Untagged VlanId : 100
Reserved VMs : vm2
Adaptor : avio_lan
Tagged VlanID : none
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 thelanadmin 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.4.4 Guest-Based VLANs
To use guest-based VLANs, you must first enable the tagged VLAN IDs of the GBVs on the
vswitch port. To enable the tagged VLAN IDs, use the hpvmnet -S <vsw> -i command. To
disable the VLAN IDs, use the hpvmnet -o command option.
On a vswitch port, you cannot use a VLAN ID as both an untagged VLAN ID and a tagged
VLAN ID at the same time. That is, a VLAN ID used with the hpvmnet -u command option
cannot be used with the hpvmnet -i option.
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 network 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:
138 Creating Virtual Networks