# rm oldhostname | HP UX System Management Software specs

If you know you have NFS PV3 and are having problems, check the /etc/rc.config.d/ nfsconf file for the configured parameter, MOUNTD_VER that defines the default mount to be PV2 or PV3; it must be set to 3.

Question:

Why is the LAN address different after replacing a client system?

Ignite-UX uses a separate directory for each client under /var/opt/ignite/clients. Each subdirectory is named based on the client’s LAN address. If you replace the client hardware or even the LAN interface that the old LAN address was based on, it will no longer access the same directory on the server.

The simplest solution is to obtain the new LAN address with the BCH command LanAddress or the EFI command lanaddress. Once you have the new address, manually rename the directory. You may just remove the hostname symlink (it will be recreated automatically). Note that the LAN address must be in all uppercase, and begin with 0x.

If you already booted from the client and caused the server to create a new directory, you can just remove that directory before renaming the old directory. To avoid losing the recovery information, be careful not to remove the original directory. For example:

#cd /var/opt/ignite/clients

#mv 0x00108300041F 0x00108300042A

#rm old_hostname

Question:

When recovering a system across multiple disks, how are the volumes assigned to disks?

Ignite-UX will do all it can to find a solution to refitting the volumes back to disks. If Ignite cannot find a solution, it will automatically turn off the mapping by setting the Disk Mapping value from Assigned Disk to Any. For information regarding how to set the Disk Mapping value, see “Volume parameters” and the File System/Swap Attributes section in instl_adm(4).

Question:

Why is the tape device different between making the recovery image and using the recovery image?

During the recovery process, when the file system is set up and the I/O tree is initialized, tape device files might be mapped differently from when the original recovery tape was made. Therefore, it is possible for a recovery tape to be created with one tape device file, for instance /dev/rmt/ 0m, and recovered from a different device file, such as /dev/rmt/2m, even though the physical device is the same.

Question:

How can I recover a system which has volume groups configured using Cluster-wide Device Special Files (cDSF)?

Ignite-UX supports cluster-wide Device Special Files (cDSF) from the C.7.16.x release. No extra steps need to be performed during the creation of an archive or during the recovery process. If a volume group is configured with cDSFs during the creation of an archive, it is recovered with the cDSFs..

IMPORTANT: During a recovery, the consistency of cDSFs is not checked across the systems sharing the storage. As a recovery archive is from a previous point in time and changes to the cDSFs visible to a system may have occurred, you must ensure that the volume group contains the correct cDSFs before you attempt to use it. Failing to do so may cause data corruption and/or an extended system or application outage. See the io_cdsf_config(1m) manual page for information on how to view, diagnose and correct potential conflicts with cDSFs.

System recovery 223

UX System Management Software specifications

HP-UX System Management Software is a robust suite of tools designed to facilitate the administration and management of HP's Unix-based operating system, HP-UX. As organizations increasingly rely on mission-critical applications, the need for a reliable and efficient management solution becomes paramount. HP-UX provides a comprehensive understanding of system performance, resource utilization, and enterprise-wide configuration, all while maintaining high availability and security.

One of the key features of HP-UX System Management Software is its Advanced System Administrator Toolkit. This toolkit includes a wide array of utilities that streamline daily administrative tasks such as monitoring system performance, managing user accounts, and configuring system settings. Tools such as Glance provide real-time monitoring of system resources, enabling administrators to identify bottlenecks and optimize performance.

The software also boasts an advanced security framework, including features such as Role-Based Access Control (RBAC) and Secure Shell (SSH) for secure data transmission. Security patches and updates can be managed through HP’s Service Pack for HP-UX, which provides a streamlined method for maintaining system integrity and compliance with various regulatory standards.

Another notable aspect is the extensive support for virtualization technologies. HP-UX supports HP’s Integrity Virtual Machines (IVMs) and vPars, allowing administrators to create multiple isolated environments on a single physical server. This not only enhances resource utilization but also improves disaster recovery planning by enabling easier backup and restore processes.

For storage management, HP-UX offers tools that enable easy setup and management of Logical Volume Managers (LVM). This allows simplified disk space allocation and management, ensuring that critical applications have the necessary resources without manual intervention.

Furthermore, HP-UX is designed with compatibility in mind, supporting a wide range of third-party applications and frameworks. Integration with management platforms like HP System Insight Manager enhances the ability to monitor and manage systems from a centralized perspective, providing alerts and reports that help in proactive decision-making.

In summary, HP-UX System Management Software delivers a streamlined approach to system administration, focusing on performance, security, and ease of management. Its advanced features, combined with an emphasis on virtualization and storage management, make it a powerful tool for organizations seeking reliability and efficiency in their Unix-based environments. As businesses continue to evolve, tools like HP-UX will remain crucial for ensuring consistent performance and operational excellence.