Ignite-UX (IUX) Frequently Asked Questions June 2013 About this FAQ -------------At the release of Ignite-UX version C.6.0, all FAQ entries were removed that applied to HP-UX 10.x or Ignite-UX versions prior to B.4.0. At the release of Ignite-UX version C.7.0 all FAQ entries that applied to Ignite-UX versions prior to version C.6.0 were removed. The current contents of this FAQ were created by the Ignite-UX engineering team from questions gathered from various sources.
1.20 1.21 1.22 understood and how do I work around it? Q: When using the graphical interface, why do errors occur when opening a terminal window to a client? Q: Why am I getting the following message? pax: Cannot access /sbin/pax_enh :No such file or directory. Q: Why do I see a problem while using March 2013 HP-UX OE media as install media? 2. Server Setup --------------2.1 Q: Should I use DHCP or bootp? 2.2 Q: Why did it call my client .0x080009....? 2.
5. General Installation ----------------------5.1 Q: How does Ignite-UX estimate needed file system sizes? Does it do anything other than add up the impacts statements? 5.2 Q: When does Ignite-UX configure software? 5.3 Q: How do I set the client's final networking information? 5.4 Q: I do not want to use DHCP, can I still have Ignite-UX automatically determine networking information for all my clients? 5.5 Q: How can I make software in a depot available for installations? 5.
8.3 archive do not end up on the client. Why? Q: What do these errors mean: pax_iux: X: Cross-device link, pax_iux: X: File exists, or pax_iux: X : Device busy? 9. Obtaining Ignite-UX ---------------------9.1 Q: What is different about the Web version? 9.2 Q: Is Ignite-UX available on media? 9.3 Q: How do I update my Ignite-UX server to a new version? 9.4 Q: How much of Ignite-UX do I need to install? 9.
11.19 Q: Why does the -n option to make_net_recovery not clean up old client recovery subdirectories? ============================================================================= == ---------------------------------------1. Known Problems ---------------------------------------1.1 Q: I updated my server; now it cannot find "/d_cfg_mnt_sb61/monitor_bpr". A: This is caused by having a mix of Ignite-UX fileset revisions on your server.
Place this configuration stanza in "/var/opt/ignite/config.local" or directly in the configuration file with the core sw_source: sw_source "core" { post_load_cmd += " swconfig -xautoselect_dependencies=false / -xenforce_dependencies=false SystemAdmin.SAM " } ============================================================================= == 1.
cached is what the RPC port number uses to contact the rpc.lockd daemon on the server and client. This RPC port information is cached in memory of the running rpc.statd/rpc.lockd process on both the server and client sides. The rpc.statd process keeps a file in the directory /var/statmon/sm for each client that it knows to contact in the event that the client reboots (or rpc.statd/rpc.lockd restarts). During a normal reboot or crash, rpc.
tape, or a make_net_recovery image: Executing: "/var/adm/sw/products/EMS-KRMonitor/KRMON-RUN/iux_postconfig". ERROR: Cannot install a dlkm driver. ERROR: Cannot configure a dlkm driver. ERROR: The script: "/var/adm/sw/products/EMS-KRMonitor/KRMON-RUN/iux_postconfig" failed, exit code was 1. The reason for this is when the recovery archive was created, the kernel the client was running was not created correctly (the DLKM information was out of sync).
but NFS over UDP performance does not seem to suffer. Ignite-UX uses an 11i installation kernel with versions Ignite-UX B.3.x, so if the Ignite-UX server is an 11i system the transport for NFS will be TCP and performance will suffer. HP-UX 11.00 only used UDP for NFS by default so the performance problems are not seen. There are several solutions available: 1. Change the switch duplex setting of the client being installed to autonegotiate for the duration of the installation. 2.
though not the current installation. Care should be taken when creating extra VxVM disk groups other than rootdg via the Ignite-UX GUI. During installation, no validation is done on a disk group name to see if it conflicts with a disk group name already in use for another unused disk on the system. If the name conflicts with another disk group, the attempt to create a disk group of the same name fails. This is a feature of VxVM to prevent the creation of duplicate disk groups.
group data from the other disks on the system, thus eradicating the duplicate disk group names. Note that LVM has the same sort of problem, but it would be observed when the duplicate group is imported back via vgimport. VxVM is different in that the problem is detected at volume group creation time. VxVM looks at all the disks on the system, and not just those selected for use in the current installation. ============================================================================= == 1.
unset SW_INITIAL_INSTALL /usr/sbin/mk_kernel -f -o /stand/vmunix " ============================================================================= == 1.14 Q: Does HP support Ignite-UX through a firewall? A: HP has not tested Ignite-UX through a firewall. It should be possible to configure a firewall such that Ignite-UX functions properly.
in the installation file system or config.local files and you have a nearly full / or /usr file system. ============================================================================= == 1.16 Q: What do I do when I get an error reading files greater than 2 GB in size? A: The C.6.5.61 (December 2005) and newer versions of Ignite-UX contain the B.11.23 patch PHKL_33110 which includes install kernels to resolve an issue where files on ISO9660 media cannot be correctly read if they are 2 GB or greater in size.
which was posted on 20-Mar-2006. Note: HPVM requires this patch if you are installing a virtual machine from an Ignite-UX server running B.11.11. Not having this patch installed on the server will cause the network boot to fail because of a firmware defect. No tftpd patch is required for B.11.23 onwards as the tftpd daemon supports the "tsize" option from first release. ============================================================================= == 1.
- From the "Advanced Options" menu, select "Edit (vi) config file" - From the vi editor, add one line such as: hw_instance_num = 0 "ioa" "sba" 0 - This will override the hw_instance_num values from the other config files on the tape. - The system will not attempt to restore any prior device file naming because of this. ============================================================================= == 1.19 Q: Why do I see errors about io.info version 0.
# SAMTERM=dtterm ignite or # SAMTERM=xterm ignite This variable is only supported on 11.23 with PHSS_31817 installed. 11.31 will use xterm, which does not have the hostname resolution problem. On 11.11 or 11.23 systems without the patch, you should specify an IP address in the DISPLAY variable. ============================================================================= == 1.21 Q: Why am I getting the following message? pax: Cannot access /sbin/pax_enh : No such file or directory.
======= 06/21/13 09:05:29 EDT Starting system configuration... * Configure_Disks: Begin * Will install B.11.31 onto this system. # If you were installing it from physical or virtual DVD media previously, a possible workaround is to use Ignite-UX server for installing the client. HP recommends you to try this workaround, though it might not be always successful. For getting the latest ISO images, contact HP Support Center. Mention that fixed HP-UX 1303 OE ISO images must be provided.
or both of the clients. ============================================================================= == 2.3 Q: How can I set the timezone for messages during the install? A: The HP-UX install kernel defaults to eastern US timezone. If you would like the log messages to come out in some other timezone, you can set the "TZ" environment variable within the *INSTALLFS files using instl_adm.
are combined and parsed. If there are conflicting or duplicate definitions, the order in which the files appear in the INDEX file determines the precedence with the last file listed (typically config.local) having precedence over all but the INSTALLFS definitions. A potential breakdown can occur if the client was previously installed and the per client directory in /var/opt/ignite/clients exists and is populated with the previously resolved configurations. In this case, the previously resolved config.
Q: Why does changing variable values in the "Additional" screen no longer control non-final networking settings (which should propagate to final networking settings) after updating to C.7.7? A: Prior to the C.7.7 release, it was possible to set final networking parameters (without using the "final" keyword) from the Additional screen with logic such as this: dns_nameserver[0] = "1.8.26.55" dns_domain = "default.corp.
Ignite-UX, which generated errors. for tftp? What files need to be accessible A: Only /opt/ignite and /var/opt/ignite are needed for tftp access. ============================================================================= == 4.2 Q: How do I duplicate a tape made with make_tape_recovery? A: For this information, refer to copy_boot_tape(1M).
File : hpux Arguments : hpux VINSTALL Loading : hpux.....175984bytes Loaded 110448 + 65536 + 865264 start 0xd01c88 Boot :tape(4/2/0.1.0;0)VINSTALL tape(4/2/0.1.0;0)VINSTALL:cannot open, or executable Exec failed : No such file or directory The correct method for booting any kernel from a tape is to add a colon (:) to the start of the kernel name. The colon tells the bootloader that it must read the kernel from the LIF at the start of the media.
============================================================================= == 4.8 Q: Can you move a volume that was created in a non-root volume to the root volume during recovery? A: When you recover a system using a recovery archive, you can extend the existing logical volume size in the Ignite-UX GUI, "File System" tab. However, the current tool does not allow you to create a new logical volume instead of using the old one.
# mv "/sbin/%sh" "/sbin/%sh.remove" Then continue the recovery installation process by typing "exit 2" (without quotes) and by pressing return. If you move the files to a name that has something in common, they will be easier to find and remove post recovery. Note: Files starting with % (such as /sbin/%sh) are created by Ignite-UX during a recovery or installation session. These files remain on a system if an error occurred during the last recovery or installation before they could be cleaned up.
'/dev/async' device file (which will be used in the examples below). You do have several options: 1. Change your per-system post recovery instructions to remind you to look at the setting of '/dev/async' (the minor number) to ensure it is as it should be for this system. 2. Write a startup script that looks at '/dev/async' and verifies that it has the minor number you would expect. If it is not the expected value, recreate it in the startup script.
============================================================================= == 5.2 Q: When does Ignite-UX configure software? A: The Software Distributor configuration and Ignite-UX "post_config_cmd" and "post_config_script" scripts are run after all software has been installed and the client has booted the final kernel from the target disk. ============================================================================= == 5.
After the configuration is created, run manage_index to make it visible in the Ignite-UX GUI. For example, for the following situation: SD depot machine: sdsource SD depot: /var/application_depot For release: 11.23 You would execute the following: # cd /var/opt/ignite/data/Rel_B.11.23 # make_config -s sdsource:/var/application_depot -c app_name.cfg # manage_index -a -f /var/opt/ignite/data/Rel_B.11.23/app_name.cfg \ -c "HP-UX B.11.23 Default" Note: The make_config command only works on bundles.
Most users have found that installing about twenty (20) clients at a time, from a single server, is the limit while maintaining reasonable performance and avoiding network errors. This seems to be a reasonable number for you to keep track of and test when the installations complete. Also, you may find it useful to stagger the installations so that they are not all doing the same operation at the same time, thus do not all complete at the same time.
Ignite-UX has incorporated patched versions of swagentd into its SYSCMDS archives. However, if you are using an operating system archive the archive may contain an older unpatched swagentd that gets deposited on top of the SYSCMDS version. This older, unpatched version then gets used and the hang may occur. In this case, the operating system archive requires a patched swagentd to fix the problem, and then it must be rebuilt.
configuration: mod_kernel += "swchunk 4096" With swchunk set to 4096, you are able to utilize up to 64 GB of swap, assuming that Ignite-UX had to set maxswapchunks to its maximum value of 16384. Note: Ignite-UX does not detect any changes you make to swchunk, it limits the total size of all swap space to 32 GB. To calculate how much swap can be utilized you multiply swchunk by maxswapchunks, for example: 16384 * 4096 = 67108864 Since swchunk is measured in KB 67108864 / (1024*1024) = 64 GB.
"Insert" key is inactive when entering data in the TUI by pressing it. ============================================================================= == 5.11 Q: What HP applications are tested for use with Ignite-UX? A: HP applications that have been tested with Ignite-UX have an OD1 option on the HP Corporate Product List (CPL), which indicates the factory integrate option. This option directs HP factories to install the software on the client before it leaves the factory.
============================================================================= == 6.2 Q: I set "control_from_server=true" and "run_ui=false" in the INSTALLFS, but I still get prompted for information on the client.
A: Check the following on the Ignite-UX server that you are trying to boot from are: - Messages from instl_bootd in /var/adm/syslog/syslog.log. If you need to add more IP addresses to /etc/opt/ignite/instl_boottab, messages are written to syslog.log similar to the following: instl_bootd: Denying boot request for host: 080009F252B3 to avoid IP address collision. Try booting again in 214 seconds, or add more IP addresses to /etc/opt/ignite - A message in syslog.
http://docs.hp.com/en/IUX/infolib.html - Use the bootsys command from the installation of the client. The *INSTALL and *INSTALLFS files to instructs it to boot from them. a network boot. Ignite-UX server to initiate the bootsys command copies the the client's local disks and This option avoids the need to do - Create a minimal bootable tape or CD to boot from, and then point the client to the Ignite-UX server once it is booted. For more information, refer to make_medialif(1M).
the client MAC address. Use "dhcptools -v" to validate the format of the /etc/bootptab file. ___ Check for entries in /etc/dhcpdeny to insure that bootpd is not set up to deny service for particular clients. ___ Check /var/adm/syslog/syslog.log for a message from bootpd that indicates it was started when a bootpd packet was received. Check tftpd for the following: ___ Check the tftp line in /etc/inetd.conf to make certain /opt/ignite and /var/opt/ignite directories are listed.
Q: Does Ignite-UX Support IPv6? A: No. Ignite-UX does not currently support installation over IPv6. ============================================================================= == ---------------------------------------7. Media Installation ---------------------------------------7.
- Run make_sys_image as such: # /opt/ignite/data/scripts/make_sys_image \ -f /tmp/specific_files -s local -d /var/tmp - Create your second archive containing the rest of the system (in this example, the /opt directory). Note that the archive content must "not" contain absolute paths. This is especially true for core operating system archives, but is a good idea for other archives as well. Using pax to create the tar archive: # cd / # pax -wx ustar -f - opt | gzip > /var/tmp/archive2.tar.
not found: WARNING: Could not find Q_BOOT device. Cannot determine what the boot device was. ERROR: Could not get io-device data (ioscan) WARNING: Could not find source device in ioscan output. You must select from the list of devices below to use for the source device: A few seconds after these messages are displayed, a USB attach message will show on the console. Use the r (rescan) option to request Ignite-UX to repeat I/O inventory to allow discovery of the vMedia device.
============================================================================= == 8.3 Q: What do these errors mean: pax_iux: X: Cross-device link, pax_iux: X: File exists, or pax_iux: X : Device busy? A: Both of these errors may occur when installing a client from an archive that does not have the same file system partitioning as the client on which the archive was created.
============================================================================= == 9.2 Q: Is Ignite-UX available on media? A: If you have subscription service for the Application Media Release then Ignite-UX is available to you on the media without a codeword. In other words, free. ============================================================================= == 9.
Below is a list of typical usages and a list of what parts of Ignite-UX you need. If you are not concerned with disk space, it is easiest just to install the bundles for the HP-UX releases you plan to work with. For all cases the IUX.IGNT-ENG-A-MAN fileset can be omitted or removed if you do not want on-line documentation. - Ignite-UX server to install HP-UX on clients - Install the Ignite-UX bundles for each HP-UX release which you plan to install onto clients.
============================================================================= == ---------------------------------------10. Loading Patches ---------------------------------------10.1 Q: How do I prevent backup copies of patched files from being saved? A: When installing HP-UX patches from SD depots, the normal behavior is that the patched files are saved in case you want to remove the patch at a later date.
should look at the setting of both "patch_state" and state in the swlist output. For example: # swlist -l patch -a state -a patch_state | grep PH If the "patch_state" is applied (the patch has not been superseded) and the state is installed, this may indicate an issue and you should configure the patch with the swconfig command. If the "patch_state" is superseded or committed, you do not have to worry about the state.
Q: How can I clone a client using make_net_recovery? A: The recovery configurations and archives created by make_net_recovery are stored in a separate directory on the Ignite-UX server for each client. Using the configuration and archive created by make_net_recovery on one client to install a different client involves manually copying some configuration files, and allowing NFS access to the source client's archive. The steps to clone a client using make_net_recovery are as follows: 1.
for more information. For Ignite-UX servers running 11.31 or later, you must edit the /etc/dfs/dfstab file to allow access to both the source and target clients as follows: # vi /etc/dfs/dfstab (append ",ro=target" to the -o argument of the source client's line) # shareall -F nfs where target is a fully qualified client name. Note that since this client should not be creating an archive, the client will not have write access to the archive directory. See dfstab(4) for more information. 6.
Omitting the -f causes list_expander to use only the essential files as input. This shows which disks or volume groups are recreated for the minimal archive.
11.6 Q: Which files does Ignite-UX change during an installation from a make_net_recovery configuration? A: During a client recovery, Ignite-UX strives to restore the client back to the way it was. However, Ignite-UX is a general purpose installation tool and as such it has the capabilities of modifying many client configuration files. When you run make_net_recovery, client configuration information is gathered and saved in configuration files that are used later when the client is recovered.
archive name. detail: The following procedure explains this process in 1. Login to the system where the archive is being stored; this system could be different from your Ignite-UX server. 2. Rename the archive. The name of the archive to save can be anything unique, but it should be outside the naming convention: "yyyy-mm-dd,hr:min". For example: # cd /var/opt/ignite/recovery/archives/system_name/ # mv old_archive_name saved_archive_name # mv 1999-05-11,15:14 Recovery_Archive.0511.save 3.
11.8 Q: How can I make configuration file additions to all recovery configurations for a given client? A: Create a new Ignite-UX configuration file called /var/opt/ignite/clients/0x/recovery/config.local. This config.local file is automatically included into your recovery configuration for this client each time you run the make_net_recovery command. The make_net_recovery command is run for you when you use the Ignite-UX GUI for network recovery.
The simplest solution is to obtain the new LAN address, which you can do from the boot-ROM console using a command like LanAddress (the actual command may vary depending on the hardware architecture). Once you have the new address then manually rename the directory under /var/opt/ignite/clients. You may remove the symbolic link to the host name because it is recreated automatically. The LAN address must be all in uppercase and begin with 0x.
Repeat execution of this command until all the DCO volumes are restored. or - Manually create an Ignite-UX configuration file that executes the VxVM commands as part of the actual recovery process. This method integrates the VxVM commands into an Ignite-UX configuration file. For make_net_recovery, create a new Ignite-UX configuration file called /opt/ignite/clients/0x/recovery/config.local; while for make_tape_recovery, create a new file called /var/opt/ignite/recovery/config.local.
For more information, refer to "VERITAS Volume Manager 3.x Administrator's Guide" at the HP technical documentation web site at: http://docs.hp.com/hpux/os/11i/oe/ ============================================================================= == 11.15 Q: Can I run make_tape_recovery/make_recovery in single user mode? If so, how? A: Yes. You can use these tools after booting or shutting down to single user mode. Choose the appropriate procedure for your situation.
# swagentd -r 3. Start the recovery tool you intend to use [make_tape_recovery/make_recovery]: # [make_tape_recovery/make_recovery] Note: The -s option of make_tape_recovery is not supported in the single user mode. ============================================================================= == 11.
You may instead choose to save the config file for the client in the path "/var/opt/ignite/clients/0x/recovery/config.local". In which case each time a new recovery archive is made, the config.local file will be automatically added to the new CINDEX entry. (See FAQ item 11.8) During a system recovery, the software bundles available in the depot will be available for selection from the user interface. ============================================================================= == 11.
