Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux

8
Warning: Features in recent Integrity systems might result in duplicate MAC address for different client
systems. Use of HP Virtual Connect (VC) functionality is one example of how this issue might occur. Clearly,
you would not expect duplicate MAC addresses on the same subnet. However, the same VC MAC address
for clients on different subnets can be used successfully for typical network operations.
Ignite-UX uses MAC addresses as the method for differentiating client systems. Clients with duplicate MAC
addresses will see each other’s client-specific content on the Ignite-UX server. In addition, the hostname link
will generally point to the same client-specific directory.
You should manage your network configuration so an Ignite-UX server does not have multiple clients with
the same MAC address.
Server-Based Recovery
An Ignite-LUX server may be used as an HP-UX network recovery server. The Ignite-UX product must be
installed on the client system. The versions of Ignite-UX installed on the server and the client must match.
Ignite-UX uses a consistent version numbering scheme for the Ignite-UX product and the Ignite-LUX package.
Important: Your CMS might not include support for managing Ignite-UX recovery. There are various
technical approaches for client system recovery, including: reinstallation, mirroring, Dynamic Root Disk
(DRD), and storage. Consult your CMS documentation for specific solution information. Alternatively, you
canelect to manage Ignite-UX recovery outside CMS control.
You may use the Ignite-UX make_net_recovery command to save a client system recovery archive on the
Ignite-LUX server. The command runs on the HP-UX server and should operate as if the Ignite-LUX server
were an HP-UX system.
The Ignite-LUX server must provide NFS access for the following client-specific directory:
/var/opt/ignite/recovery/archives/<hostname> (read/write)
The recommended best practice is to restrict NFS access to the specific client.
We recommend creating the client-specific recovery archive directory as follows:
# mkdir -p /var/opt/ignite/recovery/archives/<hostname>
# chown bin:bin /var/opt/ignite/recovery/archives/<hostname>
If the make_net_recovery command cannot mount the client directory, an error message will be given.
The details in this error message describe how to resolve the issue on an HP-UX server. You will need to
adapt details for changing the NFS configuration for your Linux server.
Review Ignite-UX documentation for the use of make_net_recovery. The following is a simple command
line example to save the entire root volume group in a recovery archive: