Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

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.
To check this case, view the output from the command swlist Ignite-UX. All the filesets must have
the same revision. If not, you must install all consistent versions.
If you have boot helper systems, they also must have the Ignite-UX product updated to match the
same revision as the server that they reference.
Can the Ignite-UX GUI for make_tape_recovery span multiple tapes?
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 interactive client to be able to span multiple tapes.
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?
Before the archive process, a list of files to be archived is created. If the files are removed from
the client while creating such list, warnings regarding the files missing from the list are generated
at the time the files are actually archived. For more information, see make_tape_recovery(1M) and
make_net_recovery(1M).
When igniting from an archive, why do I get numerous samreg errors?
The problem is that the SAM filesets have not been configured when certain products are registered
with SAM.
The workaround is as follows:
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 "
}
Can an Ignite-UX server install clients on multiple subnets?
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 a single IP address
to contact their server, then the installation works. However, it is more effective for the client to use
the IP address of the server that is connected directly to the client's own subnet. If a client is on a
Frequently asked questions 9