HP Ignite-UX manual Add the -soption to /usr/lbin/tftpd

Page 7

#mkdir –p /etc/opt/ignite

#mkdir –p /var/opt/ignite

#mkdir –p /opt/ignite/boot

#chown bin:bin /var/opt/ignite

#chmod 555 /var/opt/ignite

#chown bin:bin /etc/opt/ignite

#chmod 755 /etc/opt/ignite

#chown bin:bin /opt/ignite/boot

#chmod 555 /opt/ignite/boot

4.Add the -soption to /usr/lbin/tftpd

Add the -soption to the /usr/lbin/tftpd file on all cluster nodes that can run the Serviceguard package containing Ignite-UX. Each cluster node that can run Ignite-UX must have an entry in /etc/inetd.conf that is similar to the following:

tftp dgram udp wait root /usr/lbin/tftpd tftpd -s \ /opt/ignite\

/var/opt/ignite

For more information about the tftpd -soption, see tftpd (1m).

The directories /opt/ignite and /var/opt/ignite are also required for Ignite-UX to work correctly. If ignite-UX is installed on only one cluster node, these directory entries will not be present and must be manually added.

The /etc/inetd.conf file must be reconfigured for the changes to take effect. Run the "inetd -c"command to reconfigure the /etc/inetd.conf file.

If the -soption is not present in the /usr/lbin/tftpd file, the kernel routing table will determine the IP address used to reply to the client. The booting client might not accept the reply, because this might not be the expected IP address. This might result in intermittent network boot errors. On HP Integrity systems, errors such as PXE-E18 might be displayed, whereas on HP9000 systems, it might be difficult to diagnose the errors. In cases where the -s option is not added to the /usr/lbin/tftpd file, the possibility of the error occurring depends on package movements and the order in which packages are started in the cluster node on which the Ignite-UX package is running.

5.Mount /var/opt/ignite and create required directories on the first cluster node

Create /var/opt/ignite/data, /var/opt/ignite/clients, and /var/opt/ignite/recovery/archives on the first cluster node, then set permissions and ownership. These directories are exported when the service runs, so they must be there prior to installing Ignite.

#mount /dev/vg01/lvol2 /var/opt/ignite

#mkdir /var/opt/ignite/data

#mkdir /var/opt/ignite/clients

#mkdir –p /var/opt/ignite/recovery/archives

#chown bin:bin /var/opt/ignite/clients

7

Page 6 Page 8
Image 7
Page 6 Page 8
Contents Table of Contents Configuring an Ignite-UX server under HP ServiceguardFor more information About this document Advantage of running Ignite-UX under ServiceguardSetting up Ignite-UX to run under Serviceguard Serviceguard packages and scriptsPage Create logical volumes for the shared file systems MWC Create mount points for the shared file systemsAdd the -soption to /usr/lbin/tftpd Import volume group data on all cluster nodes Configure group for exclusive access and exportCopy NFS toolkit cluster scripts in place Etc/cmcluster/ha-iux/hanfs.sh Etc/cmcluster/ha-iux/nfs.cntl Create package config and scriptsPage Add the new package to the cluster on the first node Copy completed package directory to all nodesBring up the package on each node and install Ignite-UX Page Execute pkgrecdepot on the first node only Page Objects /var/opt/ignite/depots/recoverycmds Page Update the Ignite server IP address Best practices Edit scripts on all cluster nodes for NFS client mounts Booting from the cluster using /etc/bootptabManaging recovery images for cluster nodes For more information
Related manuals
Manual 9 pages 7.38 Kb

Ignite-UX specifications

HP Ignite-UX is a sophisticated system recovery tool developed for the HP-UX operating system. It plays a vital role in ensuring that HP-UX environments can be efficiently restored to a known good state in the event of a system failure, corruption, or mishap. The tool provides administrators with a user-friendly interface and comprehensive features that enable them to quickly deploy, recover, and maintain HP-UX systems.

One of the defining features of HP Ignite-UX is its ability to create system recovery archives. These archives can encapsulate a fully configured HP-UX system, including both the operating system and installed applications. This allows for quick restoration of systems to their exact configurations when necessary, saving both time and resources. Additionally, Ignite-UX supports network-based installations, making it possible to deploy systems remotely, which is particularly advantageous for organizations with multiple servers spread out across different locations.

Another significant aspect of Ignite-UX is its integration with the HP-UX Model. The tool leverages the underlying technologies of HP-UX, such as LVM (Logical Volume Management) and filesystem structures, to ensure that recovery processes are both efficient and reliable. By working closely with these features, Ignite-UX can handle complex restoration tasks with minimal user intervention. This ability to interact seamlessly with other HP-UX components reinforces its reputation as a critical utility for system administrators.

Ignite-UX is designed to be flexible and adaptable, catering to a variety of use cases. It supports creation of bootable recovery media on different formats, including DVD, USB, and network images, enabling easy access during disaster recovery scenarios. Furthermore, the tool includes a set of advanced diagnostics to help troubleshoot issues, providing detailed logs and reports to assist administrators in identifying root causes of system failures.

Security is also a top priority for HP Ignite-UX. The tool ensures that backups are securely encrypted, safeguarding sensitive data against unauthorized access during the restore process.

In conclusion, HP Ignite-UX stands out as a robust solution for system recovery and management within HP-UX environments. With its comprehensive features, including system recovery archives, network-based installations, seamless integration with HP-UX technologies, flexible media options, and strong security measures, Ignite-UX is an invaluable asset for organizations looking to enhance their system reliability and minimize downtime.
Top Page Image Contents