How to install a Integrity VM Guest using an Ignite-UX server
This article explains the basic process to install a Integrity VM Guest using an Igniteu-UX server.
- 1 Abstract
- 2 Install the latest Ignite-UX Software
- 3 Assign a virtual lan card to your VM guest
- 4 Setting up for a static IP environment (simplest method)
- 5 4) Creating the software depot on the Ignite-UX host server
- 6 Setup and configure the Ignite-UX host server for deployment
- 7 6) Verify and configure the Ignite-UX deployment server
- 8 Loading the OS from the Ignite server to the VM guest
Install the latest Ignite-UX Software
Can download the software from the following link:
Make sure to download all Bundles, so that your Ignite-Server supports all supported Operating Systems.
Assign a virtual lan card to your VM guest
Note: Make sure Ignite server is on the same subnet with Host’s lan, so create vswitch for that Guest:
# hpvmnet –c –S <nameofvswitch> –n <lan#> # hpvmnet –b –S <nameofvswitch>
Add network device:
# hpvmmodify -P <vmname> -a network:lan::vswitch:<nameofvswitch>
Add network device with explicit address to be used with Ignite server:
# hpvmmodify –P <vmname> –a network:lan:1,1,0x86abcdefabc2:vswitch:<nameofvswitch>
Start the VM and go to the console (in one step):
# hpvmconsole –P <vmname> –fi –c ‘pc –on’
In order to boot from the lan card you would need to set the Load File entry for your virtual MAC in the EFI Boot Options:
EFI Boot option maintenance menu --> Boot from File --> Load File (with virtual MAC) (Use Load File entry with MAC address that will be used on the /etc/bootptab entry in Ignite server)
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 (simplest method)
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 and two host entries are shown below.
Entries in /etc/bootptab to accommodate Integrity VM clients
System-IPF:\ tc=ignite-defaults:\ bp=126.96.36.199:\ sm=255.255.240.0:\ gw=188.8.131.52:\ vm=rfc1048:\ dn=bpo.hp.com:\ ds=184.108.40.206: vmguest1:tc=System-IPF:ip=220.127.116.11:ha=9258eeee1516: vmguest2:tc=System-IPF:ip=18.104.22.168:ha=42de2d02b285:
System-IPF specifies a set of default values and two for Ignite-UX clients (vmguest1 and vmguest2) 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 vmguest1 and vmguest2 above, where the first attribute is the host name 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 System-IPF).
- 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:
vmhost:/>hpvmstatus -P vmguest1 | grep lan vswitch lan vswa 0 0 0 92-58-ee-ee-15-16
Uncomment the following line on /etc/inetd.conf:
bootps dgram udp wait root /usr/lbin/bootpd bootpd
and force inetd to reread the /etc/inetd.conf:
# inetd -c
4) Creating the software depot on the Ignite-UX host server
Note Ignite must be installed and operational following a reboot prior to making depots, shown in step 1 below. If the make_depots command fails after installing Ignite, reboot the server using the shutdown –r –y 0 command.
1. Install the software depot on the host deployment server (Ignite server)
- Insert the HP-UX B.11.31 installation DVD-ROM into the CD/DVD drive of the Ignite server.
- Type the following command in the host and press Enter:
# make_depots -r B.11.31 -s /dev/dsk/c0t0d0
[Use your CD/DVD drive name, if different]
The software depot is normally created in the following directory /var/opt/ignite/depots/Rel_B.11.31, but can be placed in a common deployment location on another server.
It can take up to two hours (depending on your DVD drive speed) to create the B.11.31 software depot on an HP rx2620 or similar deployment server.
If necessary, add the Integrity VM application software for VM Hosts and Guests to the depot
Here's an example using a tar-format depot file: (/var/opt/ignite/depots/Rel_B.11.31/apps)
# make_depots –r B.11.31 –s /tmp/depots/T2767AC,r_A.03.50,a_HPUX_B.11.31_IA.tar # make_depots –r B.11.31 –s /tmp/depots/VMProvider,r_A.03.50,a_HPUX_B.11.31_IA.tar # make_depots –r B.11.31 –s /tmp/depots/VMMigrate,r_A.03.50,a_HPUX_B.11.31_IA.tar # make_depots –r B.11.31 –s /tmp/depots/VMMGR,r_A.03.50,a_HPUX_B.11.31_IA.tar
2. Remove the DVD from the drive when completed and store in a safe place
The depots are usually stored in /var/opt/ignite/depots/. Make sure you have enough space. 16GB should be sufficient.
Setup and configure the Ignite-UX host server for deployment
1. Create the Ignite-UX configuration files for the depot. At the prompt, type the following exactly as shown below. Press Enter at the end of each line shown below. Takes about 10 minutes.
# /opt/ignite/bin/make_config -c /var/opt/ignite/data/Rel_B.11.31/core_cfg –s <igniteserverip>:/var/opt/ignite/depots/Rel_B.11.31/core
2. Run manage_index to update the INDEX file. You can type: manage_index to view the manage_index definition. Type the following and press Enter.
# manage_index -a -f /var/opt/ignite/data/Rel_B.11.31/core_cfg -r B.11.31
3. Change to the /var/opt/ignite/data/Rel_B.11.31 directory. Type the following commands and press Enter.
# cd /var/opt/ignite/data/Rel_B.11.31/ # ls
4. Examine the core_cfg file using the more command. Type the following
# more core_cfg and press Enter.
This file was built by the make_config command. Notice the following information in the configuration file (these can be located a few lines from the top of the file). Always verify these before continuing.
- source_format= SD
- sd_server= (the host Ignite server deployment LAN IP address). Important! Ensure the IP address is correct. If not, the installation will not function.
- sd_depot_dir= (directory path must match the last line in step 1 above). Addresses must be correct or deployment will not function.
5. Verify that the /var/opt/ignite/INDEX file contains the new depot information. Type:
# more /var/opt/ignite/INDEX and press Enter.
The INDEX file groups the configuration files into configuration stanzas. When you install a client you will choose a configuration stanza. This will determine all the config files that will be used to install the client.
Look in the configuration stanza for HP-UX B.11.31 Default. You should see the name(s) of the configuration files built by make_config.
6) Verify and configure the Ignite-UX deployment server
1. Ensure that NFS is running on your Ignite deployment server.
# ps –ef|grep nfsd
2. Ensure that TFTP is properly enabled by verifying that the following line in /etc/inetd.conf is correct and not commented out:
tftp dgram udp wait root /usr/lbin/tftpd tftpd -l \ /opt/ignite \ /var/opt/ignite
The -l option is to generate syslog messages in the Ignite server.
3. Ensure that bootpd is enabled on ports 67/68 by verifying that the following line in /etc/inetd.conf is not commented out (around line 44):
bootps dgram udp wait root /usr/lbin/bootpd bootpd –d 9
The –d option is to generate syslog messages in the Ignite server.
4. Verify that the instl_boots daemon on ports 67/68 in /etc/inetd.conf is commented out (around line 44 in the inetd.conf file).
# instl_boots dgram udp wait root \ /opt/ignite/lbin/instl_bootd instl_bootd
5. If changes were made, restart the inetd daemon and kill any running bootpd daemons.
# inetd –c # ps –ef | grep bootpd # kill <pid>
6. Login to another terminal window (or use the existing window) on the host Ignite server and view syslog.log using the following command in the new window just opened:
# tail -20 –f /var/adm/syslog/syslog.log
Syslog.log is useful for troubleshooting during the Server LAN connection and software installation process.
Loading the OS from the Ignite server to the VM guest
- Log into the VM Console and enter the EFI Boot Option Maintenance Menu --> Boot from File --> Load File (with virtual MAC) (Use Load File entry with MAC address that was used on the /etc/bootptab entry in Ignite server and the assigned to the VM Guest).
- If the VM Guest is able to communicate with the Ignite server you should be able to select the OS to install