Using Ignite-UX with Integrity VM

This example indicates that the VM myvm02 is connected to the virtual switch vswA. In the event no such entry exists for the
VM, then a virtual network connection must be defined. To create such a connection, use the hpvmmodify command as
follows:
# hpvmmodify –P myvm02 –a network:lan::vswitch:vswA
Note that the MAC address will not match that shown in this example as Integrity VM will automatically generate a MAC
address for the virtual LAN. Moreover, this MAC address is not that of the physical Integrity server’s network interface. The
virtual machine will have to be restarted before it recognizes the new network connection.
Setting up the Ignite-UX server
The Ignite-UX server is a system with the Ignite-UX software installed and a network connection to systems (clients) intended
to use Ignite-UX. Integrity servers with HP-UX 11i v2 are recommended for Ignite-UX servers to be used with Integrity VMs.
Older Ignite-UX servers, especially PA-RISC based systems, may not have firmware versions sufficient for network
communication with VMs.
The Ignite-UX software bundle is available for all HP Integrity and PA-RISC servers. The steps outlined here are based on the
HP-UX Installation Utilities (Ignite-UX), bundle IGNITE. For the latest Ignite-UX installation information, please reference the
Installing and Configuring an Ignite-UX Server section of the Ignite-UX Administration Guide available from
http://docs.hp.com.
Basic configuration and initialization of the Ignite-UX server can be done with the Ignite-UX user interface. Currently, the
Ignite-UX user interface does not fully accommodate configuration of the Ignite-UX server for use with Integrity servers. In
particular, the configuration files /etc/dhcptab or /etc/bootptab must be directly modified on the Ignite-UX server to
prepare it for use with Integrity servers, including Integrity VMs. Which of these files require modification depends on
whether IP addresses are assigned statically or the network provides DHCP services.
Setting up for a static IP environment
For Ignite-UX clients that have a static IP address assigned to them, you will need to modify the /etc/bootptab configuration
file. A defaults entry simplifies the process of adding new client entries (including those for Integrity VMs). An example of a
defaults entry, IADEF, and two client entries are shown in
Figure 1. has three entries – one that specifies a set of default values (IADEF) and two for Ignite-UX clients (myvm01 and
myvm02) that use those defaults. This particular default entry has four values that must be modified for your configuration:
• bp – The IP address of the Ignite-UX server to be used to respond to clients.
• sm – The subnet mask being used by the clients.
• gw – The network gateway address.
• ds – The domain name server address.
Typographical errors in any of these will cause no end of enigmatic problems. Check the entries carefully.
To add another entry for a new VM, you need to specify an entry similar to that of myvm01 or myvm02 in
Figure 1, where the first attribute is the hostname of the new VM. The other three attributes are defined as follows:
• tc – The defaults to be used for this group of clients (in the example above, this will be IADEF).
• ip – The (fixed) IP address of the client.
• ha – The client hardware (MAC) address.
The MAC address for a VM can be obtained from hpvmstatus or from the VM’s console (the VM console will be
discussed later). For example, the MAC address is the last field of its LAN entry displayed in the output of hpvmstatus:
# hpvmstatus -P myvm02 | grep lan
vswitch lan vswA 0 1 0 86-ab-c8-5d-75-09