Ignite-UX Frequently Asked Questions

ManualsBrandsHP ManualsSoftwareHP Ignite-UX

Table Of Contents

Local Disk
- C:\Users\raoamr\Desktop\IUX\1303\iux_faq.htm

Ignite-UX (IUX) Frequently Asked Questions

@(#) IUX FAQ $Revision$ $Date$

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.

You may obtain a copy of this FAQ from:

http://www.hp.com/go/sw-deployment-docs

and select the product: HP-UX Ignite-UX

TABLE OF CONTENTS

-----------------

1. Known Problems

-----------------

1.1 Q: I updated my server; now it cannot find "/d_cfg_mnt_sb61/monitor_bpr".

1.2 Q: Can the Ignite-UX GUI for make_tape_recovery span multiple tapes?

1.3 Q: Why do I get Warnings from pax concerning files that are not on the

client when I run either make_tape_recovery or make_net_recovery?

1.4 Q: When igniting from an archive, why do I get numerous samreg errors?

1.5 Q: Can an Ignite-UX server install clients on multiple subnets?

1.6 Q: Why do some applications and shells hang over NFS after igniting?

1.7 Q: Why do the iux_postconfig scripts associated with EMS KRM sometimes

fail?

1.8 Q: Can I run make_net_recovery from a PA-RISC server to create an

archive for an Itanium-based client or vice versa?

1.9 Q: Why does installing or recovering a client via NFS from an HP-UX 11i

v1 Ignite-UX server take so long compared to an 11.00 server?

1.10 Q: My VxVM installation has stopped with the message: ERROR: Disk group

dg02:cannot create: Disk group exists and is imported. What is the

problem and how can I resolve it?

1.11 Q: Is SecurePath (previously known as AutoPath) supported by Ignite-UX

during installation or recovery?

1.12 Q: Why is install.log so difficult to read?

1.13 Q: Why is the message 'Cannot open /dev/vx/rdsk/rootdg/standvol'

displayed during an Itanium-based installation via golden image?

1.14 Q: Does HP support Ignite-UX through a firewall?

1.15 Q: What do I do when I get file system full messages during installation

or recovery when _hp_ignore_sw_impacts is set to 1?

1.16 Q: What do I do when I get an error reading files greater than 2 GB in

size?

1.17 Q: Why is the network boot of my Itanium-based system slow?

1.18 Q: How can I workaround recovery failure: 'ERROR: A conflict has been

detected while attempting to restore the prior device file names'?

1.19 Q: Why do I see errors about io.info version 0.5 not being

understood and how do I work around it?

1.20 Q: When using the graphical interface, why do errors occur when opening

a terminal window to a client?

2. Server Setup

---------------

2.1 Q: Should I use DHCP or bootp?

2.2 Q: Why did it call my client <hostname>.0x080009.... ?

2.3 Q: How can I set the timezone for messages during the install?

3. Configuration Files

----------------------

3.1 Q: What should go in which configuration file? Also, what should go in

INSTALLFS?

3.2 Q: How do I preview configuration file changes?

3.3 Q: Is there a way to set the configuration files to ignore the disk

warnings, which can prevent automated installations?

3.4 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?

Summary of content (36 pages)

PAGE 1
Ignite-UX (IUX) Frequently Asked Questions @(#) IUX FAQ $Revision$ $Date$ 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.
PAGE 2
4. Recovery (make_tape_recovery & make_net_recovery) ---------------------------------------------------4.1 Q: 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? 4.2 Q: How do I duplicate a tape made with make_tape_recovery? 4.3 Q: How do I deal with hot-swappable disk devices during recovery? 4.4 Q: What is the maximum amount of data that a make_tape_recovery tape can hold? 4.
PAGE 3
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? 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.5 Q: How can I copy Ignite-UX from media to a local depot such that Ignite-UX from this new local depot will be installable on all HP-UX B.11.
PAGE 4
=============================================================================== 1.2 Q: Can the Ignite-UX GUI for make_tape_recovery span multiple tapes? A: No. We use pax as the tool to create the archive tape and there is no current communication between pax and the GUI to prompt the user on the GUI when pax requests a second tape. You need to use make_tape_recovery on the interactively client to be able to span multiple tapes.
PAGE 5
which files have been previously locked, both the client and server cache information about each other. Part of the information that is 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.
PAGE 6
=============================================================================== 1.8 Q: Can I run make_net_recovery from a PA-RISC server to create an archive for an Itanium-based client or vice versa? A: Yes =============================================================================== 1.9 Q: Why does installing or recovering a client via NFS from an HP-UX 11i v1 Ignite-UX server take so long compared to an 11.
PAGE 7
1.10 Q: My VxVM installation has stopped with the message: ERROR: Disk group dg02:cannot create: Disk group exists and is imported. What is the problem and how can I resolve it? A: This is a known issue with Ignite-UX and VxVM installations involving disk group names that were used on disks in a prior installation though not the current installation. Care should be taken when creating extra VxVM disk groups other than rootdg via the Ignite-UX GUI.
PAGE 8
issues you may encounter please read the latest version of the Ignite-UX release notes (and search for EVA). You should note that these issues do NOT affect active/active EVA GL or any EVA XL disk arrays. These disk arrays are fully supported for use with Ignite-UX. =============================================================================== 1.12 Q: Why is install.log so difficult to read? A: The installation messages that are logged into install.
PAGE 9
there is enough free space for an installation or recovery. Setting '_hp_ignore_sw_impacts' to 1 means that Ignite-UX will not resize the file systems according to impacts to guarantee some free space. If you set '_hp_ignore_sw_impacts' to 1, you must ensure that there is some free space available in / and /usr during installation or recovery (at least 20MB) to avoid file system full issues. If you do not set '_hp_ignore_sw_impacts' to 1, you can ignore this information.
PAGE 10
while restoring a prior instance number assignment of the ext_bus class devices (this instance number appears in the device file names for disks following the 'c' character). For VxVM, the device files must not be renamed prior to the kernel knowing about the new instance assignments, and for LVM/whole-disk, they must be renamed prior. So when the system has a 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.
PAGE 11
a terminal window to a client? A: If errors occur when Ignite-UX attempts to bring up a terminal to a client (for instance, to enter a password), it could be because hpterm does not work with some name-services (like LDAP) and is unable to resolve a hostname specifed in the DISPLAY environment variable. For HP-UX 11.23, the following patch introduced support of an environment variable SAMTERM: PHSS_31817 s700_800 11.23 ObAM Patch The value of this variable will determine which type of terminal is opened.
PAGE 12
# echo 'env_vars += "TZ=MST7MDT"' >> /tmp/installfs.out # instl_adm -f /tmp/installfs.out Note: The "timezone" keyword in the Ignite-UX config file determines what timezone is actually applied to the system after the installation is complete. Setting the TZ env variable as shown above is only used during the installation. (See instl_adm(4) for the "timezone" keyword). =============================================================================== ---------------------------------------3.
PAGE 13
A: We do have an environment variable which should do what you need. Look in instl_adm(4) for INST_ALLOW_WARNINGS. This can be used to keep you from going interactive when warnings are received. You will need to put the setting of this environment variable in INSTALLFS for it to have effect.
PAGE 14
=============================================================================== 4.3 Q: How do I deal with hot-swappable disk devices during recovery? A: Ignite-UX only supports hot-swappable disks that are completely installed and present when creating a recovery image. Proper software and hardware procedures must be used for hot swap disk removal or replacement before or after recovery, but not during.
PAGE 15
The make_tape_recovery manual page defines inc_cross as follows: -x inc_cross=file|dir Includes the file or directory in the recovery archive and crosses mount points to access any directories that are mounted or files contained in directories that are mounted. =============================================================================== 4.7 Q: Are multi-byte characters supported in file names in Ignite-UX? A: At this time, multi-byte characters are not supported in file names.
PAGE 16
to do so can cause problems with subsequent recoveries. =============================================================================== 4.11 Q: How do I perform two-step recovery? A: When recovering an Itanium-based system from a recovery image created with make_tape_recovery that does not support Itanium-based tape boot, you must perform a two-step recovery. This requires both a recovery tape of the system and a bootable CD or DVD containing the same revision of Ignite-UX; for example, C.6.6.x.
PAGE 17
A: Ignite-UX adds in minfree (normally 10%) to the amount required by the software impact. You may have software bundles that have overlapping contents: filesets and/or files. The make_config command makes sw_impact statements for each bundle without doing anything special to guard against over-counting when the bundles overlap. For example, the Ignite-UX-11-XX bundles all overlap so when you install all of them using Ignite-UX it estimates too much space.
PAGE 18
-c "HP-UX B.11.23 Default" Note: The make_config command only works on bundles. If the software is not contained within a bundle you must either create bundles for it using the make_bundles command or manually create configuration files for your software. =============================================================================== 5.6 Q: FDDI software is included in my archive, yet Ignite-UX requires that I select it.
PAGE 19
At this point in the process, Ignite-UX attempts to start swagentd. Because of a signal problem with swagentd, the parent process waits infinitely for a signal from the child process which cannot occur. If you press "CTRL-C" on the client console, you see a message similar to the following appears: NOTE: ERROR: run_cmd: Process: 223 (/usr/sbin/swagentd): killed by signal: 2. swagentd returned an error. You are asked if you want to push a shell, and you should answer yes.
PAGE 20
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. Ignite-UX lets you configure more space in swap space than what the kernel can use so getting swchunk and maxswapchunks set correctly for a large configuration is important.
PAGE 21
A: 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.conf file on the server should have an entry similar to: tftp dgram udp wait /opt/ignite\ /var/opt/ignite root /usr/lbin/tftpd tftpd\ If not, fix inetd.conf and run "inetd -c". Kill any tftpd processes that may be running. Installing Ignite-UX should set inetd.conf. - Using a tftp entry for the client that is referencing a nonexistent boot file (bf).
PAGE 22
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.
PAGE 23
Instead, a BOOTP/DHCP server such as HP-UX bootpd must be configured and /etc/bootptab entries made for each client. If this Ignite-UX server has been configured and the client still does not boot, the following is a checklist of items to verify: Check inetd for the following: ___ Check /etc/inetd.conf to make certain bootps and tftp entries have been uncommented.
PAGE 24
7.1 Q: Why do I get DCE/RPC errors (RPC exceptions) during the configuration stage? A: In addition to these errors, there is a 10+ minute hang at the end of the SD configure stage and a failure message appears at the end of the installation. There is an apparent problem with certain SD operations (for example, swacl) when only loopback networking is enabled. This occurs if the media-only installation option is selected.
PAGE 25
containing the archive. Do not use instl_combine on the subsequent CDs as they should not have a LIF area. =============================================================================== 7.3 Q: Which HP-UX releases support install using vMedia? A: HP-UX 11.31 for September 2007, HP-UX 11.23 for December 2007, or a later release is needed for vMedia install. =============================================================================== 7.
PAGE 26
client on which the archive was created. The first error, "pax_iux: X: Cross-device link", is caused when two files exist as hard links in the archive, and if these two files would reside in separate file systems. For example, if you created an archive on a client that did not use LVM the root file system is all one file system and the files, /usr/local/bin/f1 and /opt/myprod/bin/f2, are hard linked.
PAGE 27
- Do not modify any files under the /opt/ignite directory. If you need to modify any configuration files under /opt/ignite, copy them to an equivalent directory under /var/opt/ignite then modify the INDEX file to use them in the new location instead. Some files and scripts contain comments that describe the recommended modification procedure to use.
PAGE 28
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. However, this takes up additional space in the /var directory so you may want to turn that feature off.
PAGE 29
Guide" at: http://docs.hp.com/en/IUX/infolib.html - These manpages are applicable to network recovery are as follows: * * * * * * make_net_recovery(4) make_boot_tape(1M) pkg_rec_depot(1M) instl_adm(1M) instl_adm(4) ignite(5) - The Ignite-UX Release Notes that detail new features, enhancements and known problems with the product. It is located in Information Library and in the /opt/ignite/share/doc/release_note directory.
PAGE 30
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.
PAGE 31
disks and volume groups. =============================================================================== 11.5 Q: How can I use make_net_recovery if I need to be able to recover from a tape? A: There are two ways you can recover from a tape with make_net_recovery. The following method that you choose depends on your needs: - The first method is useful when you want to create a totally self-contained recovery tape.
PAGE 32
An alternative, better approach to saving known good archives is to rename the archive and edit the configuration file to include the new archive name. The following procedure explains this process in detail: 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".
PAGE 33
modify the /var/opt/ignite/clients/0x/CINDEX file for the client you are recovering. The CINDEX file contains one or more configuration clauses that refer to the recovery images you have previously created with make_net_recovery. Add a new configuration file entry to the clause from which you intend to recover. If you want to add the HP standard file system choices, add the file: # /opt/ignite/data/Rel_/config where is the operating system release on the client you intend to recover.
PAGE 34
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. This method integrates the VxVM commands into an Ignite-UX configuration file.
PAGE 35
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: The -s option of make_tape_recovery is not supported in the single user mode. 7. When complete, return the resolv.
PAGE 36
containing the additional software. Then add the path to that config file to each recovery clause desired in the /var/opt/ignite/clients//CINDEX file. The example below will create a config file and add it to all entries in the client's CINDEX file. # make_config -s -c /var/opt/ignite/data/Rel_B.XX.YY/sw.cfg # manage_index -a -f /var/opt/ignite/data/Rel_B.XX.YY/sw.