Ignite-UX (IUX) Frequently Asked Questions (FAQ) Document HP-UX 11i v3 Abstract This document is intended for Ignite-UX users and administrators, who have questions, which is frequently asked, and answers and solutions to those questions.
Copyright 2003, 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents HP secure development lifecycle......................................................................7 1 About this FAQ (frequently asked questions) document.....................................8 2 Known problems........................................................................................9 Frequently asked questions.........................................................................................................9 I updated my server; now it cannot find /d_cfg_mnt_sb61/monitor_bpr.
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?...............21 5 Recovery (make_tape_recovery and make_net_recovery)...............................22 Frequently asked questions.......................................................................................................
8 Media installation....................................................................................35 Frequently asked questions.......................................................................................................35 Why do I get DCE/RPC errors (RPC exceptions) during the configuration stage?........................35 How can I put an operating system archive on multiple CDs?...................................................35 Which HP-UX releases support install using vMedia?........
Why does the -n option to make_net_recovery not clean up old client recovery subdirectories?.....50 13 Documentation feedback.........................................................................
HP secure development lifecycle Starting with HP-UX 11i v3 March 2013 update release, HP secure development lifecycle provides the ability to authenticate HP-UX software. Software delivered through this release has been digitally signed using HP's private key. You can now verify the authenticity of the software before installing the products, delivered through this release. To verify the software signatures in signed depot, the following products must be installed on your system: • B.11.31.
1 About this FAQ (frequently asked questions) document 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 based on the questions gathered from various sources. You may obtain a copy of this FAQ from www.hp.
2 Known problems Frequently asked questions Following are the frequently asked questions as known problems, which is a compilation of all the available feedback from the users. I updated my server; now it cannot find /d_cfg_mnt_sb61/monitor_bpr This is caused by having a mix of Ignite-UX fileset revisions on your server. In most cases, it happens when you update only one release bundle (like Ignite-UX 11.23) even though you install other releases from that server.
subnet that does not have a route to the IP address specified by the server, then it will not be able to contact the server after it boots. The workaround for this problem are as follows: • Manually correct the IP address of the server on the networking screen that appears on the client console when you boot the client. • Use a boot helper on each subnet. When using a boot helper, the IP address of the server can be specified correctly on each helper system.
Why do the iux_postconfig scripts associated with EMS KRM sometimes fail? On some HP-UX 11.x clients you might encounter the following errors when recovering a client from a make_net_recovery or make_tape_recovery 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.
# instl_adm -d -F /opt/ignite/boot/INSTALLFS > /tmp/installfs.out Edit /tmp/installfs.out to add the following line: _hp_nfs_mount_opts="-oproto=udp" (or change the _hp_nfs_mount_opts variable if it already exists to add -oproto=udp) Then, save the changes back into the INSTALLFS after saving the file: # instl_adm -F /opt/ignite/boot/INSTALLFS -f /tmp/installfs.out 3. Ignite-UX provides the libraries required to use the lanadmin -X option with 100BT and 1000BT interfaces.
ERROR: Disk group dg02: cannot create: Disk group exists and is imported ERROR: Command "/sbin/vxdg init dg02 dg0201=c17t12d0 dg0202=c17t13d0"failed. The configuration process has incurred an error, would you like to push a shell for debugging purposes? (y/[n]): If the affected disk group contains any important volume like /usr, /opt, or /var, this installation is unlikely to succeed as those volumes are required to boot and bring a system up.
Why is the message Cannot open /dev/vx/rdsk/rootdg/standvol displayed during an Itanium-based installation via golden image? It is caused by the major number change between B.11.23 first release and B.11.23 September 2004 for VxVM volumes. You will see this message if the golden image was created on a system running B.11.23 first release, and then the golden image is installed using version 'C' of Ignite-UX. You can move the kernel build a little earlier in the process to avoid the message.
cannot be correctly read if they are 2 GB or greater in size. When encountering this problem the symptoms look like: • Loading_software: Begin • Installing boot area on disk • Formatting HP Service Partition • Enabling swap areas. • Backing up LVM configuration for "vg00" • Processing the archive source (hp client archives) • Thu Nov 03 12:37:56 EST 2005: Starting archive load of the source (B.11.
mixture of VxVM and LVM/whole-disk, there is a chance that device files used by one or the other need to be exchanged resulting in a conflict. In the case of fibre channel devices, the kernel can sometime assign different instances for the ext_bus devices each time the system boots Ignite-UX. So in these cases, if you get the error, simply rebooting and retrying might result in success.
3. 4. Use the client's console to boot from the Ignite-UX server. Delete the io.info file in the client's directory. When using the graphical interface, why do errors occur when opening a terminal window to a client? If errors occur when Ignite-UX attempts to bring up a terminal to a client (for instance, to enter a password), it can be so because hpterm does not work with some name-services (like LDAP) and is unable to resolve a hostname specified in the DISPLAY environment variable. For HP-UX 11.
The following are the symptoms associated with the issue: • During installation of HP-UX 11i v3 March 2013 from physical or virtual media, the installation aborts unexpectedly and displays the following error: Checking configuration for consistency... NOTE: run_cmd: Process: 113 (net_cfg_prep): killed by signal: 11. ERROR: Could not open /tmp/env.vars: No such file or directory errno = 2). ERROR: Could not execute net_cfg_prep NOTE: System rebooting...
3 Server setup Frequently asked questions Following are the frequently asked questions for setting the server, which is a compilation of all the available feedback from the users. Should I use DHCP or bootp? There are some advantages and disadvantages to both DHCP and bootp. In general, DHCP allows you to specify more complete networking information. However, there are no good tools to manage the database so that you can enforce the LLA <-> IP-address mapping ahead of time.
4 Configuration files Frequently asked questions Following are the frequently asked questions in configuring the files, which is a compilation of all the available feedback from the users. What should go in which configuration file? Also, what should go in INSTALLFS? Here is a short description of the common uses of the various configurations.
in INSTALLFS for it to have effect. The line you would add to allow an automated installation to proceed after the warning is as follows: env_vars += "INST_ALLOW_WARNINGS=10" 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? Prior to the C.7.
5 Recovery (make_tape_recovery and make_net_recovery) Frequently asked questions Following are the frequently asked questions in various modes of recovery, which is a compilation of all the available feedback from the users. We tried running the recovery system option from a client booted in Ignite-UX, which generated errors. What files need to be accessible for tftp? Only /opt/ignite and /var/opt/ignite are needed for tftp access.
to install it from an LIF. The above errors are the result of the bootloader attempting to read the kernel from an HFS file system, which is not possible on a tape. Older releases of the bootloader prepended a colon (:) to the VINSTALL kernel name. This provision is unavailable from the bootloader for 11i v1. In this case, the correct boot string would be: bo 4/2/0.1.0 :VINSTALL Not: bo 4/2/0.1.
This would backup the entire vg00 volume group and the one file anyFile from the directory myDataVolume. Assuming that myDataVolume is on the other volume group, the layout of the other volume group will be saved and restored during recovery (along with anyFile).
NOTE: If the /dev/async device file needs to be customized, make the change before the database starts. How do I recover a system which has cluster-wide device special file (cDSF) configured? Starting from Version 7.16.x Ignite-UX supports cDSF. No additional steps are required to recover a system on which cDSF have been configured. The consistency of cDSF is not checked across the systems sharing the storage during recovery and the cDSF is not synchronized. The user is responsible for ensuring the same.
6 General installation Frequently asked questions Following are the frequently asked questions in installation in general, which is a compilation of all the available feedback from the users. How does Ignite-UX estimate needed file system sizes? Does it do anything other than add up the impacts statements? Ignite-UX adds in minfree (normally 10%) to the amount required by the software impact. You might have software bundles that have overlapping contents: filesets and/or files.
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.
My installations are hanging; what is going on? In certain circumstances installations might hang and this can be due to a problem with swagentd. If you are using an operating system archive, the hang occurs after the following message appears: * Running /opt/upgrade/bin/tlinstall -v and correcting transition link permissions. If you are using swinstall only, the hang occurs after the following message appears in install.
If the amount of swap created is more than 32 GB, you must increase the kernel tunable swchunk from its default of 2048. This is not an automatic process. If there is insufficient kernel resources configured to enable you to use the swap being created, a message appears indicating this during the installation process.
No applications are tested for proper installation or operation when included in a golden image that is installed with Ignite-UX. They might work fine in this mode, but it is up to you to verify proper installation and operation. Running swconfig -x reconfigure=true\* after installation might cause some software to properly configure itself after installing from a golden image archive.
7 Network installation Frequently asked questions Following are the frequently asked questions in installing the network, which is a compilation of all the available feedback from the users. When the client searches for bootable devices, the Ignite-UX server does appear on the list. When I try to boot, I get the error: IPL error: bad LIF magic. Why? Typically, this has been caused by one of the following situations: • Not having tftp access to /opt/ignite and /var/opt/ignite, the /etc/ inetd.
When executing search lan install on the client, the Ignite-UX server does not appear in the list. Why? 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.
Itanium-based clients differ from PA-RISC clients because the Ignite-UX instl_bootd boot protocol server cannot be used. The Configure Booting IP Addresses button on the Server Configuration tab of the Ignite-UX GUI and the /etc/opt/ignite/instl_boottab file do not apply to Itanium 2-based clients. Instead, a BOOTP/DHCP server such as HP-UX bootpd must be configured and /etc/bootptab entries made for each client.
3. 4. When network boots a system any network information gained by DHCP must provide the hostname of the system, not doing so will lead to errors during the recovery if a system has aggregate LAN interfaces defined on HP-UX 11i v1 or v2. Changing the hostname during a recovery on a system that has aggregate LAN interfaces defined on HP-UX 11i v1 or v2. Doing so will lead to errors during a recovery. For more information on APA, see Admin Guide chapter 15 under section Verifying Recovery Image Results.
8 Media installation Frequently asked questions Following are the frequently asked questions in installing the media, which is a compilation of all the available feedback from the users. Why do I get DCE/RPC errors (RPC exceptions) during the configuration stage? In addition to these errors, there is an approximate 10 minute hang at the end of the SD configure stage and a failure message appears at the end of the installation.
change_media=TRUE Now, you can put these archives and configuration files on the CDs. The first CD contains the LIF data created using make_medialif and all the configuration files referencing all your archives. For more information, see make_medialif(1M) and the Ignite-UX Administration Guide at http:// docs.hp.com/en/IUX/infolib.html The second and subsequent CDs need to have a file system containing only the archive. Do not use instl_combine on the subsequent CDs as they must not have an LIF area.
9 Archive installation (Golden images) Frequently asked questions Following are the frequently asked questions in archiving the installation (Golden images), which is a compilation of all the available feedback from the users. What does the following gunzip error indicate? gunzip: stdin: unexpected end of file pax_iux: The archive is empty. ERROR: Cannot load OS archive (HP-UX Core Operating System Archives) It appears that the NFS mount succeeded, but the file was not accessible from the client.
To avoid the errors, the client that the archive is created from must not contain soft links between directories that are likely to be created as separate file systems.
10 Obtaining Ignite-UX Frequently asked questions Following are the frequently asked questions in obtaining Ignite-UX (IUX), which is a compilation of all the available feedback from the users. What is different about the Web version? Usually nothing, other than the software might be available prior to the media release. Additionally, you can download one depot containing all supported operating system releases.
• Using only make_tape_recovery on clients— Create the recovery commands depot on your Ignite server and install the HP-UX release specific bundle applicable to your system or if you have downloaded Ignite-UX from the website, install the release specific version of Ignite-UX from that depot. That bundle contains everything required to create a recovery tape.
11 Loading patches Frequently asked questions Following are the frequently asked questions in loading patches, which is a compilation of all the available feedback from the users. How do I prevent backup copies of patched files from being saved? When installing HP-UX patches from SD depots, the normal process is that the patched files are saved in case you want to remove the patch at a later date. However, this takes up additional space in the /var directory so you might want to turn that feature off.
12 Network recovery Frequently asked questions Following are the frequently asked questions in recovering the network, which is a compilation of all the available feedback from the users. How can I learn more about network recovery? In addition to the information in this FAQ, there are several other sources of information on network recovery: • See the System Recovery chapter in Ignite-UX Administration Guide at http://www.hp.com/ go/ignite-ux-docs.
# find CINDEX recovery | cpio -pdvma ../ 5. Give the target client NFS access to the archive of the source client by logging into the Ignite-UX server that holds the archive. Typically, each client has its own directory for storing the archives, and the directory is exported only to the individual client. For Ignite-UX servers running releases prior to 11.
Table 1 Output In? dsk/vg name minor# Associated disks _______ _ ________ _________ _________ ___________________ 0 d /dev/dsk/c0t3d0 1 v /dev/vg00 0x00 /dev/dsk/c0t6d0 /dev/dsk/c0t4d0 0 v /dev/vg01 0x01 /dev/dsk/c0t1d0 0 v /dev/vg02 0x02 /dev/dsk/c0t2d0 The first column shows, for each disk or volume group, if it will be: 2= included in full (INC_ENTIRE dsk/vg specified); the disk or volume group is re-created and files from the archive are restored 1= included in part (some fi
to be protected from modification by using the /save_file/ function. The os_arch_post_l script uses the merge_file function on files into which appropriate information is merged. The files operated on by merge_file, and those that have a commented out save_file line are those that are likely to be modified by Ignite-UX. Comments in this file explain any exceptions.
. . } to: cfg "Saved Recovery Archive" { description "Weekly System Recovery Archive" . . . } How can I make configuration file additions to all recovery configurations for a given client? 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.
/var/opt/ignite/clients. You might 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. If you have already booted the client from the server, which caused it to create a new directory, you can remove that directory before renaming the old directory. Do not delete the original directory or you will lose the recovery information.
methods of reconfiguring lost DCO log volumes; choose the method that is appropriate for your situation: • Wait until the client is recovered and then execute the following VxVM command: # vxassist -g rootdg addlog homevol logtype=dco 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.
1. Mount all file systems: # /sbin/mountall 2. Disable DNS so that /etc/hosts is used: # mv /etc/resolv.conf /etc/resolv.conf.save 3. Set your client's host name: # /sbin/rc1.d/S320hostname start 4. Set up loop back networking: # /sbin/rc2.d/S008net.init start 5. Start the networking daemon: # swagentd 6. Start the recovery tool you intend to use [make_tape_recovery/make_recovery]: # [make_tape_recovery/make_recovery] NOTE: 7.
How can I install additional software from depots during a recovery? In situations where a system needs additional software installed to support restoring a recovery archive onto a different hardware platform, or perhaps a vPar or HP-VM, you can load additional software from a depot during the recovery. To do this, generate a config file using make_config for the depot containing the additional software.
13 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback. NOTE: For more information about support policy of HP-UX, see HP-UX support policy.
