HP vPars and Integrity Virtual Machines V6.1 Administrator Guide
0/0/0/4/0/0/0 (lan2)
0/0/0/4/0/0/1 (lan3)
DATA CRITICAL RESULTS:
Interface lan2: COMMAND cmnetd PID 2907
Interface lan2: COMMAND cmnetd PID 2907
Service-Guard(SG) Usage:
The interfaces listed below are being used by SG:
lan2
Use the hvmdevinfo command to display the hardware device mapping between vPar/VM and
the VSP. You can run this command on the VSP or the vPar/VM:
VSP:
# hpvmdevinfo
Virtual Machine Name Device Type Bus,Device,Target Backing Store Type Host Device Name
Virtual Machine Device Name
==================== =========== ==================== ================== ================
===========================
atcvpar2 disk [0,0,0] disk /dev/rdisk/disk13
/dev/rdisk/disk3
atcvpar2 disk [0,0,2] disk /dev/rdisk/disk21
/dev/rdisk/disk5
atcvpar2 hba [0,5] npiv /dev/fcd0
/dev/gvsd2
atcvpar2 lan [0,6,0x7E06F5393261] hwpath 0/0/0/4/0/0/0
0/0/0/6/0 (lan3)
vPar/VM:
# hpvmdevinfo
Device Type Bus,Device,Target Backing Store Type Host Device Name Virtual Machine Device
Name
=========== ================= ================== ================ ===========================
disk [0,0,0] disk /dev/rdisk/disk13 /dev/rdisk/disk3
disk [0,0,2] disk /dev/rdisk/disk21 /dev/rdisk/disk5
hba [0,5] npiv /dev/fcd0 /dev/gvsd2
lan [0,6] hwpath 0/0/0/4/0/0/0 0/0/0/6/0 (lan3)
For current limitations, see the HP-UX vPars and Integrity VM V6.1 Release Notes on the BSC
website at http://www.hp.com/gp/hpux-hpvm-docs
10.6 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.
• AVIO LAN devices not claimed by guest with DOWN vswitch at boot time.
In addition to running ioscan, you must re-run the necessary network startup scripts, so that
IP addresses can be reconfigured on the network interface cards (NICs). For example:
/sbin/rc2.d/S340net start
/sbin/rc2.d/S340net-ipv6 start
10.6.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:
162 Creating virtual networks