There is one known problem with having an Ignite-UX server that is multi-homed (connected to multiple subnets): The "server " keyword that specifies the IP address for your Ignite-UX server can only correspond to one of the LAN interfaces. If each subnet is routed such that all clients can use the one IP address to contact their server, then the installation will work. See similar questions...

Yes. It requires that you setup a boot-helper on the remote subnets, or limit yourself to using the bootsys command. Because the network boot firmware uses a broadcast BOOTP packet to find an Ignite-UX server to boot from, these packets do not normally cross over subnets. This limits clients to booting from Ignite-UX servers only on their local subnet. Set up a boot-helper system on the client's subnet that has the IUX.MinimumRuntime product installed. See similar questions...

Depending on what you are using Ignite-UX for, you may be able to reduce the disk space usage by not installing the full product. 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. See similar questions...

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 client to be able to span multiple tapes. If files are removed from the client between the time the list of files to be archived is created and the time the files are actually archived, warnings are generated. See similar questions...

In general, each new version of Ignite-UX is compatible with any scripts or configuration files that were delivered with older versions. If you follow some simple guidelines, updating to a new version of Ignite-UX involves running swinstall to install the new version; this is the same procedure as installing it for the first time. There is no need to remove the old version. See similar questions...

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. See similar questions...

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. See similar questions...

This assumes that you start Apache the standard way by using the "apachectl" script. You will need to become "root" user to do this. Note: Prior to running this script, ensure that none of processes (like Apache, Tomcat, Webmin, Stunnel, rotatelogs, logresolv) are running. Some Apache binaries such as htpasswd expect shared libraries to be in standard locations. To run them you will need to set the SHLIB_PATH. See similar questions...

You must reinstall Helix Server from your Installer file (that you either downloaded from our web site or purchased on a CD-ROM). The first time you launch Helix Server, it will ask for your Serial Number and Enablement Key. Enter these numbers and the Server will be configured per your expanded license. See similar questions...

Why do the text fields in the Ignite-UX TUI not accept my input, and the dialogs re-open or loop? 6. Network Installation See similar questions...

The Rev. A C3700 and J6700 models were two short-lived systems that had the PA-8700 2.2 chipset revision and 1.6 firmware revision. They were only supported on HP-UX 11.00. Since the WINSTALL kernel is 11i v1-based and PHKL_27152 (or one of its predecessors) is included in that kernel, it is not possible to boot the installation kernel on these systems. They must be upgraded to Rev. B, which includes the PA-8700 2.3 chipset. There is a service note, A7277A, which addresses this situation. See similar questions...

It depends on what SecurePath is controlling. Ignite-UX does not support active/passive EVA GL (EVA3000/EVA5000) disk arrays because of multiple known issues. For more information about potential 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. See similar questions...

Ignite-UX generates an error indicating that you must select the FDDI software for installing if the following conditions exist: Ignite-UX provides the error prior to starting the configuration phase to avoid the client being unable to complete the installation due to the lack of the FDDI drivers. Ignite-UX does not have any way of detecting the inclusion of FDDI software in an archive so it assumes that it is not. See similar questions...

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 your client before it leaves the factory. HPmanufacturing installs the software from a depot using the Ignite-UX process. No applications are tested for proper installation or operation when included in a golden image archive that is installed with Ignite-UX. See similar questions...

Yes. MiniVend supports multiple independent catalogs. There are users who run more than 500 catalogs on a single machine. The capacity is usually a function of how busy the catalogs are and how much memory and processor speed your system has. See similar questions...

Compiling the source66. I'm trying to compile WinVNC and the compiler complains about various missing files! Getting Started Q1 Where can I get VNC? The latest versions of VNC and this documentation are always available from the AT&T Labs Cambridge web site at http://www.uk.research.att.com/vnc. In addition, various add-ons, extras, and ports to other platforms can be found on the contribs page. See similar questions...

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. You should be able to add the sw_impact of all the sw_sels that you are installing and to calculate the required file system size. See similar questions...