session for use in subsequent sessions. For more information regarding configuration files, see “Using configuration files” (page 161).

To specify a saved configuration as the default, define it in your server’s /var/opt/ignite/ data/INDEX file, or use the bootsys command with the -ioption and name you have given it.

Specifying defaults in the config.local file

The /var/opt/ignite/config.local file is normally included in every configuration (cfg) clause in the /var/opt/ignite/data/INDEX file. It provides a convenient location, in which to store default parameters that are the same for all configurations. Typically these are networking parameters, default software selections and kernel modifications.

The following is an example of what a config.local file look like. The sw_sel definitions depend on what you have defined in other configuration files on the Ignite-UX server.

dns_domain="corp.com"

dns_nameserver[0] = "10.2.72.2" nis_domain="corpdomain" wait_for_nis_server=FALSE root_password="JPDw02THwAhiQ" timezone="MST7MDT" ntpdate_server="10.1.48.1" init sw_sel "Misc_Patches"=TRUE init sw_sel "B3919DA_AGP"=TRUE mod_kernel += "maxuprc 100" set_kernel += "dbc_max_pct 20"

NOTE: After making manual edits to config.local, always use the following command to verify that the syntax is correct and to avoid installation errors:

instl_adm -T -f config.local

Setting defaults with instl_adm

Some network parameters must be known by the client when it first boots. The netmask and gateway can be supplied in the installation or RAM file system ([WVI]INSTALLFS). You can do this by using the instl_adm command, which has options to set the client’s netmask, gateway, Ignite-UX /tftpserver, and so on.

For example, you might want to set the keyboard language so you are never prompted for it when booting from Ignite-UX. To do this, first display the current configuration information and redirect it to a temporary file for editing. Then, edit the file to include the new configuration information. Finally, apply the new configuration information from the temporary file.

In the following example, the keyboard language is set to PS2_DIN_US_English.

#instl_adm -d > /tmp/installfs.out

#echo '_hp_keyboard="PS2_DIN_US_English"' >> /tmp/installfs.out

#instl_adm -f /tmp/installfs.out

For more information, see “Using configuration files” (page 161) , instl_adm(1M), and instl_adm(4).

Using the per-client configuration file

When Ignite-UX begins an installation session, it scans the directory /var/opt/ignite/clients for a directory matching the MAC address of the client. For example, if the MAC address of the client is 0x08000992E346, Ignite-UX looks for a file named config in /var/opt/ignite/ clients/0x08000992E346. However, to enable you to find clients easily Ignite-UX also creates a symbolic link between the client’s name and the MAC address. If the client has more than one LAN interface, the MAC address of each interface is used until a matching directory is found.

Specifying defaults in the config.local file 175

Page 174 Page 176
Page 175
Image 175
HP UX System Management Software manual Specifying defaults in the config.local file, Setting defaults with instladm
Page 174 Page 176

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.
Top Page Image Contents