Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Integrity Virtual Machines Version 4.0 Installation, Configuration, and Administration > Chapter 8 Creating Virtual Networks

Troubleshooting Network Problems

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

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.

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:

# 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.

AVIO Supported Ethernet Cards

The following Ethernet cards are supported with AVIO on HP-UX guests:

  • A6794A — Core

  • A6825A — Core

  • A7109A — Core

  • A6847A — Add-in

  • AB465A — Combo Add-in

  • A9782A — Combo Add-in

  • A9784A — Combo Add-in

  • AB352 — Core

  • AB545A — Networking Add-in

  • A7011A — Networking Add-in

  • A7012A — Networking Add-in

  • AB290A — Combo Add-in

  • AB287A — Add-in (10 GbE)

  • AD331A — Add-in

  • AD332A — Add-in

  • AD193A — Combo Add-in

  • AD194A — Combo Add-in

  • AD221A — Add-in

  • AD222A — Add-in

  • AD337A — Add-in

  • AD338A — Add-in

  • AD339A — Add-in

  • AD385A — Add-in (10 GbE)

  • AD386A — Add-in (10 Gbe)

NOTE: In this release, AVIO is supported on only HP-UX 11i v2 and HP-UX 11i v3 guests.

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 VM Host, 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 VM Host 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 VM Host, where 4 is the host interface as shown in the hpvmnet command output.

# lanadmin -X send_cko_off 4 Hardware TCP/UDP (IPv4) transmit checksum offload is currently disabled
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.