HP Ignite-UX manual Create package config and scripts

Page 9

10.Create package config and scripts

Create the package configuration file and the package control script template for Ignite on the first node.

#cmmakepkg -p /etc/cmcluster/ha-iux/nfs.conf The package template has been created.

This file must be edited before it can be used.

#cmmakepkg -s /etc/cmcluster/ha-iux/nfs.cntl Package control script is created.

This file must be edited before it can be used.

11.Edit parameters in Ignite scripts and config files on the first node as follows.

Substitute your system names for the example system names such as sgiux3.fc.hp.com along with your IP addresses.

/etc/cmcluster/ha-iux/hanfs.sh

XFS[0]="-o anon=2 /var/opt/ignite/data" XFS[1]="-o anon=2 /var/opt/ignite/clients" XFS[2]="-o sec=sys,anon=2,rw=sgiux3.fc.hp.com: sgiux4.fc.hp.com:sgiux5.fc.hp.com:sgiux6.fc.hp.com /var/opt/ignite/recovery/archives" NFS_SERVICE_NAME[0]="nfs.monitor" NFS_SERVICE_CMD[0]="/etc/cmcluster/ha-iux/nfs.mon" NFS_SERVICE_RESTART[0]="-r 3" NFS_FILE_LOCK_MIGRATION=1

/etc/cmcluster/ha-iux/nfs.cntl

VG[0]=vg01

LV[0]=/dev/vg01/lvol1; FS[0]=/etc/opt/ignite;

FS_MOUNT_OPT[0]="-o rw"; FS_UMOUNT_OPT[0]="";

FS_FSCK_OPT[0]=""; FS_TYPE[0]="vxfs"

LV[1]=/dev/vg01/lvol2; FS[1]=/var/opt/ignite;

FS_MOUNT_OPT[1]="-o rw"; FS_UMOUNT_OPT[1]="";

FS_FSCK_OPT[1]=""; FS_TYPE[1]="vxfs"

LV[2]=/dev/vg01/lvol3; FS[2]=/opt/ignite/boot;

FS_MOUNT_OPT[2]="-o rw"; FS_UMOUNT_OPT[2]="";

FS_FSCK_OPT[2]=""; FS_TYPE[2]="vxfs"

IP[0]="15.1.53.116"

SUBNET[0]="15.1.48.0"

function customer_defined_run_cmds

{

#If /etc/bootptab exists, move aside. Link shared version. if [[ -f /etc/bootptab ]];then

mv /etc/bootptab /etc/bootptab.iux.backup

fi

ln -s /etc/opt/ignite/bootptab /etc/bootptab

#If /etc/dhcptab is not a file or does not exist then we only

#need to create the symlink if it doesn't already exist.

#This can happen in the event of a failure.

9

Image 9
Contents Table of Contents Configuring an Ignite-UX server under HP ServiceguardFor more information Setting up Ignite-UX to run under Serviceguard Advantage of running Ignite-UX under ServiceguardServiceguard packages and scripts About this documentPage Create logical volumes for the shared file systems MWC Create mount points for the shared file systemsAdd the -soption to /usr/lbin/tftpd Configure group for exclusive access and export Import volume group data on all cluster nodesCopy 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 Managing recovery images for cluster nodes Booting from the cluster using /etc/bootptabFor more information Edit scripts on all cluster nodes for NFS client mounts
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.