Ignite-UX Release Notes (769572-001, March 2014)

If your configurations use NFS to access archives on systems other than the Ignite-UX server,
then those systems should have NFS over TCP enabled as well.
User interface issues
• The user interface does not currently allow you to directly specify kernel parameters. The
target's kernel can be manipulated via the "mod_kernel" configuration file keyword. For
details, see instl_adm(4). There is also a way to make kernel modifications user selectable in
the UI by treating them as software.
• The DNS server in the "System" tab for setting up network information must be specified as
an IP. It cannot be specified as a host name.
• The "Change Depot Location" menu on the "Software" tab has a selector called "Interactive
swinstall". Setting this selector to "yes" means that an interactive swinstall (or swm if B.11.31
or later) session will be run on the target machine and must be controlled on the target console.
It is not currently possible to control an interactive swinstall/swm session from the Ignite-UX
server GUI.
• The help dialog for the configuration tabs has a "Print" button that is not functional when
running on a client in Terminal User Interface(TUI) mode. Pressing the "Print" button on the
help dialog while in the TUI will cause the user interface to fail, and the session will have to
be restarted. It is not possible to print in TUI mode, because there are no printers set up.
Issues when installing from archives
• When performing multiple, simultaneous archive installations from a single server (using the
ftp archive access method), you may get some tftp errors.They will be displayed on the target
console or in the log file at /var/opt/ignite/clients/<LLA>/install.logas: "tftp:
recvfile: recvfrom: Can't assign requested address". A workaround is to use one of the other
archive access methods; for example: nfs or remsh.
• There is currently no tool support for creating configuration files for archive software.
Configuration file templates for this purpose are supplied in: /opt/ignite/data/examples
• If an archive is not accessible, Ignite-UX does not find out until it actually tries to extract the
archive on the target machine. Even then, the error indicators are non-intuitive (usually get a
message to load the next tape!). When this happens, check that:
◦ the archive is named correctly in the configuration file,
◦ the archive actually exists,
◦ the archive is readable, and
◦ the archive is accessible via the method you specified.
Common problems loading patches
• When setting up an SD depot containing patches, you need to ensure that all patches are
compatible with the target systems on which you plan to install them.
• By default, Ignite-UX does not use the "-xpatch_match_target=true" option to swinstall;
it calls out the software bundles explicitly. This causes selected patches to be loaded even
when the software they patch is not loaded. Note that for 11.23 and later patch bundles,
they are packaged in a way so that make_config will omit the sd_software_list attribute
which will result in those bundles being implicitly selected which avoids these problems.
To change the default behavior of Ignite-UX to use a "-xpatch_match_target=true"
type swinstall, the sd_command_line keyword can be used to define this. For example:
sd_command_line += " -xpatch_match_target=true "
User interface issues 27