HP-UX System Administrator's Guide: Overview HP-UX 11i Version 3 HP Part Number: 5992-6573 Published: September 2009 Edition: 4
© Copyright 2008, 2009 Hewlett-Packard Development Company, L.P Legal Notices Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Warranty The information contained herein is subject to change without notice.
Table of Contents Preface.........................................................................................................................................9 Intended Audience...............................................................................................................9 About this Series...................................................................................................................9 About this Document:...............................................................
Workload Manager (WLM)...........................................................................................28 Technology Summary..............................................................................................28 Tools to Administer/Configure................................................................................28 How to Obtain..........................................................................................................29 For Further Information........................
Kernel Modules.............................................................................................................43 Adding/Removing Kernel Modules........................................................................43 Kernel Tunables.............................................................................................................44 The HP-UX Directory Structure.........................................................................................44 Key HP-UX Directories............
Disabling Swap Space..............................................................................................72 Guidelines for Setting Up Swap Areas....................................................................73 Device Swap Guidelines.....................................................................................73 File System Swap Guidelines..............................................................................74 Guidelines for Assigning Swap Priority................................
LiveDump (Memory Dumps of Running Systems).........................................................106 Limitations of Live Dumps..........................................................................................107 Operating System and Software (Installation, Modification, and Removal) ...................107 Software Distributor....................................................................................................107 Other Software Operating System Installation Technologies..............
Tools for Monitoring the Performance of Applications..............................................127 Data Protection Tools........................................................................................................128 Protecting Against Unauthorized Access to Your Servers and Data..........................128 Protecting Against Data Loss......................................................................................128 Protecting Against Hardware Failure...................................
Preface Intended Audience The HP-UX System Administrator’s Guide series is written for administrators of HP-UX systems of all skill levels needing to administer HP-UX systems, beginning with HP-UX Release 11i Version 3. While many topics in this set apply to previous releases, much has changed in HP-UX 11i as of Version 3. Therefore, for information about prior releases, please refer to Managing Systems and Workgroups: A Guide for System Administrators.
Chapter 2: HP-UX Virtualization Technologies, Discusses the many technologies available for use with HP-UX to help you get the most out of your computing resources and provides information to help you understand how these technologies relate to each other. Chapter 3: Major Components of HP-UX, Discusses the major pieces of HP-UX and how the pieces relate to each other.
Table 1 Finding HP-UX Information (continued) If you need to. . . Refer to . . . Located at . . . Administer an HP-UX system For Releases Prior to HP-UX 11i • HP Instant Information (English only) Version 3: • HP Technical Documentation web site • Managing Systems and http://docs.hp.
Table 2 HP-UX 11i Releases (continued) OS Version Identifier Release Name Supported Processor Architecture B.11.31.0809 HP-UX 11i Version 3, September 2008 Update HP 9000 and Integrity B.11.31.0909 HP-UX 11i Version 3, September 2009 Update HP 9000 and Integrity For information on supported systems and processor architecture for different versions of HP-UX, refer to the HP-UX system release notes specific to your version of HP-UX (for example, the HP-UX 11i Version 3 Release Notes).
command line, you can enter man audit or man 5 audit to view the manpage. See man(1). Document Title The title of a document. On the web and on the Instant Information DVD, it may be a hot link to the document itself. Command A command name or qualified command phrase. ComputerOut Text displayed by the computer. Emphasis Text that is emphasized. Emphasis Text that is strongly emphasized. KeyCap The name of a keyboard key. Note that Return and Enter both refer to the same key.
{ } The brace metacharacters enclose required content in formats and command descriptions. | The bar metacharacter separates alternatives in a list of choices, usually in brackets or braces. ... The ellipsis metacharacter after a token (abc...) or a right bracket ([ ]...) or a right brace ({ }...) metacharacter indicates that the preceding element and its preceding whitespace, if any, may be repeated an arbitrary number of times. ... Ellipsis is sometimes used to indicate omitted items in a range.
Print, HP Technical Documentation web site http:// docs.hp.com Third Edition September 2008, 5992-4580, HP-UX 11i version 3 (B.11.31 September 2008 Update) Printed, DVD (Instant Information), and Web (http:// www.docs.hp.com) Fourth Edition September 2009, 5992-6573, HP-UX 11i version 3 (B.11.31 September 2009 Update) Printed, DVD (Instant Information), and Web (http:// www.docs.hp.com) NOTE: The documents in the HP-UX System Administrator’s Guide may be updated independently.
1 HP-UX Version 3 at a Glance This chapter highlights some of the key features of HP-UX 11i version 3. However, the comprehensive source for what is new and changed in any given HP-UX version, compared with that version’s previous releases, is the HP-UX 11i Release Notes. For HP-UX 11i version 3, see HP-UX 11i Version 3 Release Notes. How HP-UX is Delivered HP-UX is comprised of many components and subsystems. This section covers how those components are packaged and delivered.
Third-Party Products As with most operating systems, HP-UX 11i is the core of an entire suite of products, not all of which come from HP. Thousands of applications that run on HP-UX 11i (both on HP 9000 servers and on HP Integrity Servers) are available from software vendors. HP-UX 11i Version 3 Highlights With each new release, HP-UX gains new features and enhancements to previously existing features (to enhance their ease of use). Here are a few key features of HP-UX 11i version 3.
Hardware Threading A hardware technique used in Itanium processors to enhance the computational performance of a core. Itanium processors are those used in HP Integrity Servers. Software Threading A parallel computing technique used by applications and operating systems to enhance processing efficiency. Server Formerly referred to as a “system” or “computer”, this document primarily uses the term “server” to describe the physical cabinet containing cell boards, processors, memory, and power supplies.
• • • Allows you to establish multiple hardware paths to disk and other mass storage devices using a single device special file. Allows the kernel to automatically bypass failed hardware paths without having to change the device’s associated device special file. Allows you to relocate (logically or physically) a disk device to a new hardware location without having to change its device special file.
either the kernel tunable dump_concurrent_on (see dump_concurrent_on(5)), or the crash-processing configuration command crashconf (see crashconf(1M)). For additional information on the crash dump sequence, see “Abnormal Shutdowns (System Crashes)” (page 93). For More Information on HP-UX 11i Version 3 For complete descriptions of what is new/changed in HP-UX 11i version 3, please read HP-UX 11i Version 3 Release Notes.
2 HP-UX Virtualization Technologies Enterprise computing is now heavily focused on enabling you to use your computing resources as efficiently as possible by extracting the most performance from each of your server’s resources. Many technologies are available to help you configure HP enterprise servers to suit almost any need, and to adjust your configuration as your computing needs change with minimal disruption to your business. Collectively, these technologies are known as virtualization technologies.
Figure 2-1 Virtualization Technology Categories Matrix Examples: • One operating system, running on a single one processor/one core (1P/1C) server is a standalone system (or a one-node network). • Multiple operating systems running on one multiple core server utilizes partitioning technology.
Standalone Systems (One Single-Core Server, One Operating System Instance) The simplest case, a single 1P/1C server, running a single instance of HP-UX, is a standalone system. It is a computer not connected to a network (or is the sole server on a network). Today, these are probably dedicated machines, perhaps running highly secure or highly specialized applications. For whatever reason, these are systems in isolation.
represent multiple physical paths to a mass storage device and traffic can be balanced among the physical paths for more efficient data transfer. • Common Desktop Environment (CDE) CDE allows you to configure multiple (virtual) workspaces using the X Window technology. You can group and organize various types of work into these workspaces and name the workspaces for easy identification.
Process Resource Manager (PRM) Technology Summary Process Resource Manager (PRM) is a resource management tool used to control the amount of resources that processes use during peak system load (when the server is at 100% core, 100% memory, or 100% disk bandwidth utilization). Processes and users are assigned to PRM Groups. The PRM Groups are then allocated dedicated cores and memory. This both dedicates resources to the groups and isolates the group’s members from using other system resources.
Workload Manager (WLM) The Process Resource Manager allows you to manually dedicate resources to specific applications. However, many factors are likely to change constantly, such as system load, resource utilization, resource needs, and the mix of applications that are running at any given time. If the conditions and needs of your server environment are constantly changing, WLM can continuously monitor and adjust resources to maintain application performance and business goals.
NOTE: WLM manages workloads on individual servers. To manage workloads on multiple servers, install and configure WLM on each of the servers. WLM can be integrated with HP Serviceguard by storing the WLM configuration file in a file system shared by all nodes in the cluster and then activating the configuration on each node independently. Alternatively, you can use the HP Integrity Essentials Global Workload Manager (gWLM) to manage workloads across multiple servers.
How to Obtain The PSET technology is included in HP-UX 11i version 3. For Further Information See the following documents (available on docs.hp.
iCAP You purchase (for a small price) memory, processors, or cell boards for which you do not yet have usage rights. When you need these resources, you purchase usage rights for them and receive codewords to activate them. From that point on, you own those resources. TiCAP Similar to iCAP, but the usage rights that you purchase are only temporary (TiCAP is currently sold in 30-day increments).
How to Obtain The capability to activate instant capacity components is part of the HP-UX Foundation Operating Environment (and is therefore available in all operating environments that build upon the Foundation Operating Environment). However, in order to use the instant capacity technologies, you must have purchased and installed components without usage rights to activate.
Pay per use (PPU) Med Low High Pay per use (PPU) is a product that enables you to “pay as you go”. Pay per use is a pricing model in which you are charged for your actual usage of computing resources. Technology Summary With Pay per use, you treat computer processing capacity as you would electricity, water, or other utilities.
• • • • • Display current settings Test communications to HP Set usage caps Specify hostnames and system identifiers for use in reporting usage to HP and for your use when viewing usage information on the portal Specify which utility meter a server or partition should use to report its usage information How to Obtain Pay per use is shipped with the HP-UX Foundation Operating Environment and is customer configurable on all HP-UX servers.
• • • • Serviceguard Clusters Extended Campus / Extended Distance Clusters Metropolitan Clusters Continental Clusters Serviceguard A Serviceguard cluster is a networked group of HP Integrity or HP 9000 servers (known to Serviceguard as nodes) having sufficient redundancy of software and hardware that a single point of failure will not significantly disrupt service. The ability to continue operating in spite of a software or hardware failure makes Serviceguard clusters highly available.
as all copies of the package contents remain running. All copies of System Multi-node packages halt if even one of the copies in the cluster halts. System Multi-node packages do not fail over. HP supports them only for specific applications. Serviceguard clusters use TCP/IP networking services for reliable communication among nodes in the cluster. This includes heartbeat messages (signals from each functioning node that are central to the operation of the cluster).
for disaster tolerant architecture are followed. The maximum distance between nodes in an extended distance cluster is set by the limits of the data replication and networking technology used. Sometimes referred to as an extended campus cluster, this cluster type services an area approximately the size of a college or corporate campus.
On HP 9000 servers, you can also have multiple versions of HP-UX (or other supported operating systems) installed on different disks (or logical boot volumes) and select your desired boot volume at boot time. NOTE: This multiple boot capability works equally well for servers with more than one active core. It is presented here because this is an available function for servers containing only one active core.
• • • • • Implemented at the cell board level. Provides both functional and electrical isolation. Partitions are referred to as nPartitions. nPartitions can be further sub-divided using Software Partitioning. On servers that support them, nPartitions can run HP-UX, Linux, Microsoft Windows, or all of these operating systems (in separate partitions). Software Partitioning vPar 1 vPar 2 vPar 3 Software partitioning provides for finer grained partitioning than nPartitions.
• • nPartitions can be further subdivided using software partitioning vPars only supports instances of HP-UX Comparing Partitioning Technologies The following table compares the three partitioning technologies (nPartitions, vPars, and Integrity Virtual Machines): Table 2-1 A Partitioning Technology Comparison nPartitions vPars Integrity Virtual Machines Isolation Operating System and Electrical Operating System Operating System Partition boundaries Cell Board Groups Cores and Memory Chunks Time
Figure 2-2 The Virtualization Technology Stack Shipping Department Web Server Database Server 1 Database Server 2 Other Users HP Global Workload Manager PRM Group A PRM Group B memory memory core core core core Integrity VM Guest OS memory core core core core vPar 1 Integrity VM Guest OS memory memory core core core core core core core core vPar 2 nPartition 1 Integrity VM Host nPartition 2 Hardware Platform Networking (Multiple Operating Systems, Multiple Servers) Unless the phys
There are many well established applications, protocols, and networking technologies. They work between multiple HP-UX operating systems, and between HP-UX and other operating systems as well. Table 2-2 lists a few common networking technologies. Table 2-2 Common Networking Technologies Technology Used For...
3 Major Components of HP-UX Operating systems are complex pieces of software designed to control the many resources of a computer so that many users and processes can use those resources cooperatively and efficiently. HP-UX 11i, a version of the UNIX operating system, is comprised of many components that work together to control the resources of HP Integrity Servers, HP 9000 servers, and others. This chapter describes the main components of HP-UX, what they do, and how they relate to each other.
Kernel Tunables Kernel tunables are settings that determine things like how many processes can simultaneously be active or how much memory can be allocated for certain data structures within the kernel. For more information on kernel tunables, what they are, and how to adjust them, see the HP-UX System Administrator’s Guide: Configuration Management. NOTE: Some kernel tunables have their values set at boot time and cannot be changed without rebooting.
Figure 3-1 Directory Tree Example / adm bin lib share vue man man1.Z man1M.Z man2.Z man3.Z man4.Z man5.Z man7.Z man9.Z cat.1 Key HP-UX Directories This section describes many of the key directories in the HP-UX directory structure and what they are used for. /dev Contains device special files. Though they appear in the directory tree like regular disk files, device special files are associated with physical devices or pseudodevices.
• • /etc supported in HP-UX 11i version 3 and function as they always have. persistent device special files reference their corresponding devices based on a world-wide unique identifier that is built into, or associated with, the device. Because persistent device special files are not dependent on specific hardware paths, they allow for multiple hardware paths to be represented by a single device special file.
server (and if the home directory location is left at its default), the home (login) directory for Thomas will be /home/thomas. /opt The /opt directory contains application software and other system components of the HP-UX 11i operating system that are not considered to be part of the minimum-level installation needed for a viable system. /sbin Contains statically linked versions of critical programs needed at boot time or when important shared libraries have become corrupted.
/usr/sbin Contains dynamically linked non-essential commands used to administer the system once it is in multiuser mode. These commands are available only when the file system that contains them is mounted. /var “var” stands for variable. This directory (usually associated with a mountable file system) contains variable data; that is, files that need to change as the system is running (for example, log files that need to be written to).
• • protection. Storage Area Networks work at the block I/O layer, below the file system layer. Network Attached Storage (NAS), an alternate network storage solution, working at the file system layer using standard network protocols (NFS, CIFS) Off line storage or removable media.
• • SAN - Storage Area Networks (physical drives attached to a dedicated network) NAS - Network Attached Storage (storage attached to dedicated servers accessed through standard network file system protocols) Individual disk drives (whether standalone or in an array or enclosure) are often referred to as LUNs.
NOTE: The pools of space are called volume groups in the Logical Volume Manager and disk groups in the VERITAS Volume Manager. Both volume managers can co-exist on a server. Each volume manager keeps track of which disks it is controlling and any given physical disk can only be a controlled by one volume manager at a time. The utility vxvmconvert can convert an LVM physical volume to a VxVM disk if you want to migrate a disk from LVM to VxVM for greater configuration flexibility.
Table 3-1 Volume Manager Feature and Terminology Comparison (continued) Feature HP Logical Volume Manager (LVM) VERITAS Volume Manager (VxVM) Volume and Volume Group configuration information is stored in... a special reserved area at the beginning of each physical volume. a special area known as a “private region” of each physical volume. Mirrors (copies of data) You need to add the MirrorDisk/UX product to your system to support mirroring.
(Logical) Volumes Once you have grouped physical disk drives into disk/volume groups, the collective space can be divided into logical storage containers that can be smaller or larger than any individual drive in the group.
are not merely pointers indicating which file is in which directory; these are the low level pointers and other vital information, for example: • which disk blocks belong to which file • which disk blocks are currently unused (so that specific disk blocks are not simultaneously used for more than one purpose and order is maintained) • linked lists of directory navigation information File systems also have other important functions, for example maintaining ownership and access privilege information so that H
Disk Striping Disk striping spreads data over multiple physical devices in such a way that successive writes occur on different devices. In this way, the second chunk of data to be written does not have to wait for the device writing the first chunk to finish. In essence, if you have n devices striped together, then you can write n chunks of data simultaneously (or nearly simultaneously) without having to wait for devices to become ready for subsequent data.
File System Type Your choice of file system type can also affect the efficiency of accessing your data. The VERITAS File System (VxFS) is generally faster than using the HFS file system. Establishing Multiple Paths to a Device (for efficiency) Beginning with HP-UX 11i version 3, HP-UX 11i supports device multipathing, a new technology that associates device files with devices by using unique device IDs rather than the hardware path to the devices.
Establishing Multiple Paths to a Device (for redundancy) One of the key points to protecting your data is eliminating single points of failure. RAIDs and other Disk Arrays, Disk Mirroring, and Data Backups, and Serviceguard are all about eliminating single points of failure. Beginning with HP-UX 11i version 3, HP-UX 11i supports device multipathing, a technology that associates device files with devices by using unique device IDs rather than the hardware path to the devices.
• • HP-UX 11i v3 HA-OE HP-UX 11i v3 DC-OE Mirrordisk/UX supports up to three copies of data if you are using LVM with Version 1 volume groups, and up to six copies of data if you are using LVM with Version 2 volume groups. Using the base version of VERITAS Volume Manager you can mirror only your root file system. By purchasing and installing the full version of VERITAS Volume Manager, you can mirror other disk groups and have up to 32 mirror copies of a volume’s address space.
• vxdump vxdump copies to magnetic tape all files in a VxFS file system that have been changed after a certain date. See vxdump(1M). • • fbackup (recover data using frecover), an HP-UX specific backup utility for backing data up to the previous media types. tar tar (called the “tape archiver”) can write to disk archive files or optical media. tar is compatible with many other operating systems, including other versions of UNIX, Linux, and Microsoft Windows.
Table 3-2 Storage Components and how they are Addressed (continued) Stack Component How it is addressed (Logical) Volumes The logical containers allocated from space in a volume group or disk group are addressed by their volume name. Because these volumes are disk drives from the perspective of the operating system, they have associated device files.
The first two items in the list above are determined by the major number of a device special file, the latter two items are determined by the minor number of a device special file.
/dev/rdsk/c0t6d0sdisk card instance 2 SCSI target 6 SCSI LUN 0 section 0 at address 0/0/0/3/0.6.
(and therefore without requiring changes to other configuration files). If you replace a disk associated with a persistent device special file (the type of device special files that provide agile device addressing), you can use the io_redirect_dsf command to update the persistent device special file to reference the replacement disk. For details, see the manpage io_redirect_dsf(1M).
wt_round_robin This load balancing policy selects an I/O path based on a weighted round robin algorithm Use the scsimgr command to specify which of the previous policies should be used for a given device. NOTE: Not every device supports every load balancing policy. The type of device determines which of the previous policies you can use.
/dev/disk/disk15_p3 /dev/rdisk/disk7_p1 The following directories still exist in HP-UX 11i version 3 for backwards compatibility. They contain the legacy device special files defining the physical drives on a server (the legacy form): Contains legacy device special files for block mode access to physical /dev/dsk disk devices on a server. /dev/rdsk Contains legacy device special files for character mode access to physical disk devices on a server.
Mass Storage Hardware Paths (three formats) Hardware paths, as the name implies, define the physical paths that data travels to reach devices. In HP-UX 11i version 3 there are three formats to specific hardware paths to mass storage devices. Legacy Hardware Paths This is the format used in releases prior to HP-UX 11i Version 3.
Instead of a series of bus-nexus addresses (corresponding to specific hardware paths) leading to the HBA, virtual hardware paths use a virtual bus-nexus (known as the virtual root node) with an address of 64000. Addressing beneath that virtual root node consists of a virtual bus address and a virtual LUN ID, delimited by slash characters (“/”). 64000/0xfa00/0x22 is an example of a virtual hardware address.
insf could be run to create device special files for that new hardware without having to wait for a reboot of the system)3. See insf(1M) for details. With the -L option, insf enables the legacy naming model. mksf Used to create a single device special file, usually with non-default characteristics. For details on specifying the parameters for your device special file, see mksf(1M). If you wish to create a single device special file, perhaps with specific parameters, use mksf instead of insf.
a disk drive and are using legacy device special files, refer to the scsimgr(1M) manpage for assistance with remapping the device special file to the new device. The scsimgr command to do this is replace_leg_dsf.
NOTE: There is one exception to the rule that a given logical volume cannot be used for both file system space and device swap. If you have unused space between the end of a file system and the end of the logical volume in which it resides (that is, the file system is smaller than the logical volume it is in), the unused space (not allocated to the file system), can be used as device swap space.
Lazy Swap Another technology that takes advantage of the fact that not all swap space that is reserved is actually used is lazy swap. The lazy swap feature causes HP-UX to not reserve swap space for a process-private page until the associated process actually modifies the page. This can significantly reduce the amount of allocated swap space. Lazy swap is configured on a process by process basis.
Unless the amount of physical memory on your system is extremely large, the minimum amount of swap space should equal the amount of physical memory on the system. In general, size your server’s swap space to be roughly two to four times the amount of physical memory that is used by HP-UX on your server, nPartition, or virtual partition. Swap space usage increases with system load.
• • your system must be running HP-UX 11i Version 3 September 2008 Update, or later sufficient swap space must remain active (following the change) to continue to operate your system Use the swapoff command to disable paging to a specific swap area. For example: /usr/sbin/swapoff /dev/vg00/lvol2 Guidelines for Setting Up Swap Areas There are some guidelines to consider when configuring swap space on your system. Most of these are focused on maximizing the performance of HP-UX.
File System Swap Guidelines When you need more swap space and you have no devices available for additional device swap, or if you need to swap to a remote system, you can dynamically add file system swap to your system. Use the following guidelines: • Interleave file system swap areas for best performance. Two swap areas on different disks perform better than one swap area with the equivalent amount of space.
fstab(4) The file /etc/fstab not only defines which file systems should be mounted to which mount points in the directory tree (see “The HP-UX Directory Structure” (page 44)), it is also one of the key places you configure swap space. lvlnboot(1M) lvlnboot prepares an LVM logical volume to be root, boot, primary swap, or a dump volume. swapinfo(1M) swapinfo prints information about device and file system paging space.
Printing Printing on HP-UX is accomplished through a subsystem known as the HP-UX Line Printer Spooling System. Overview of the HP-UX Line Printer Spooling System The Line Printer Spooling System (spooler) is a set of programs, shell scripts, and directories that controls your printers and the flow of data going to them. The spooler ensures that output from multiple users or processes doesn’t arrive on a printed page intermixed, yielding a printout that is useful to no one.
Interface files (written as shell scripts) near the end of the data flow serve as pumps that “pump” the orderly flow of data to the printers. The line printer scheduler: • • • • prevents intermixed listings monitors printer/print request priorities adjusts printer status and availability logs spooler activities If one printer’s “drain gets clogged”, you can reroute a print request from that printer to another by using the lpmove command.
Figure 3-7 Line Printer Spooler “Plumbing” Diagram 78 Major Components of HP-UX
Remote Spooling You can also send print requests to a printer configured on a remote system, using remote spooling. When you use remote spooling, a shell script (“pump”) sends data to a remote system via the rlp command. A remote spooling program (a daemon called rlpdaemon), running on the remote system, receives data and directs it into the remote system’s spooler. rlpdaemon can also run on your local system to receive requests from remote systems.
HP-UX provides a library of sample files corresponding to most HP printers (or printer families) -- examples: “laserjet”, “colorlaserjet”, “PCL5” -- and some sample files corresponding to generic printer families (for example “postscript”). When you set up a printer in the line printer spooling system (whether through a tool like the System Management Homepage or directly by using the shell based lpadmin command), you specify a printer model script to be associated with the printer you are setting up.
A remote printer may be physically connected or simply configured to a computer and accessed over a network. To access the remote printer, your system sends requests over the network to another system. To configure a remote printer into your local spooler, you must be able to access the remote system via the network. To configure a remote printer, see HP-UX System Administrator’s Guide: Configuration Management (Chapter 6: Configuring Printers).
Print Destination The print destination is the printer or printer class where a file containing the print job will be queued. Several commands for the spooler require you to specify a print destination. You can appoint one print destination in your spooler to be the system default printer. Each user can also personalize which printer is their default printer by setting a shell environment called LPDEST.
the day to be printed in the evening when the fence priority was lowered. See lpadmin(1M) and lpfence(1M) for additional details. Printer Logging Every spooling system request is logged in a log file located in /usr/spool/lp/log. The file contains a record of each spooling system request, including request ID, user name, printer name, time, error messages, and reprints due to failure.
• • • • • Move specified print requests from one queue to another without having to stop the scheduler (Note: the print requests cannot be actively printing when you move them) Change the priority of a queued print request Change the number of copies that will print (of the specified print requests) Change the print options (for example, change portrait to landscape printing) for queued print requests Change the title that will print on a banner page associated with specified print requests lpfence Each
In this way, by configuring printers in one place (the LDAP server), you can automatically add printers to (or remove printers from) numerous client systems automatically. NOTE: Even if a client system is configured to use LDAP-UX and its Printer Configurator Services, a system administrator can still configure printers in the client’s spooler manually.
Controlling Access to Data Using Security Containment Technologies Traditional UNIX file access mechanisms are adequate for many basic installations, but today’s security and privacy conscious world requires a lot more control over who has access to which data. With traditional security methods, a typical weak link in the mechanism is the superuser (or root user). The term superuser refers to any account with a User ID (or any program or process with an effective User ID) of “0” (zero).
privileges, processes are granted only the privileges needed for the task and, optionally, only for the time needed to complete the task. Applications that are privilege-aware can elevate their privilege to the required level for the operation and lower it after the operation completes. Role-Based Access Control Typically, UNIX system administration commands must be run by a superuser (root user).
Start-up and Shutdown Whenever you turn on (or reset) your computer, the hardware, firmware, and software must be initialized in a carefully orchestrated sequence of events known as the boot sequence. A similar sequence, known as the shutdown sequence, refers to the orderly sequence of steps needed to halt HP-UX.
NOTE: There is a different but similar run level known as S (upper-case S). It is functionally the same as run level s (lowercase) with the exception that the capabilities of the true system console are switched to the terminal where you are logged in making it a virtual system console. With modern remote access to a server through its management processor, the distinction between run levels s and S is pretty much semantic. run level 1 Just above run level s is run level 1.
2. run level transitions. /sbin/rc.utils also logs output from startup and shutdown scripts to the file /etc/rc.log. The rc daemon then runs/etc/rc.config which processes all scripts in the directory /etc/rc.config.d. The scripts in /etc/rc.config.d set variables that control the execution of the startup and shutdown scripts that are subsequently run by the rc daemon. IMPORTANT: You control what the startup and shutdown (kill) scripts do by setting variables in their corresponding scripts in the /etc/rc.
Example 3-4 Run Level Transition Examples The following two examples show what happens during two typical situations: Transition up The file /etc/inittab contains an entry telling init that the initial run level for the system during boot-up should be run level 3: init:3:initdefault: To reach run level 3, the system transitions: • From run level 0 (the halted state) • to run level 1 (running scripts pointed to by links in the /sbin/rc1.
init init is both a daemon and a command. The init command interacts with the init daemon. You use the init command to set or change run levels. The init daemon, started at boot time spawns processes as defined in the /etc/inittab file. These processes in turn control how HP-UX interacts with the outside world (for example, which terminals to accept input from, and whether or not to export local file systems via NFS for use by other servers).
2. 3. the boot process. They also locate and initialize communications with console display and keyboard devices, and a boot device. Pre-boot firmware/software routines then load and execute the HP-UX boot loader. The HP-UX boot loader: — Locates, opens, and reads the kernel file and copies the kernel into memory — Initiates the HP-UX kernel 4. HP-UX goes through its initialization process and begins normal operation.
At other times, the cause of the crash might not be so obvious. In extreme cases, you might want or need to analyze a snapshot of the computer’s memory at the time of the crash, or have HP do it for you, in order to determine the cause of the crash. Overview of the Dump / Save Cycle When the system crashes, in order to preserve the evidence of what caused the crash, HP-UX tries to save the image of physical memory, or certain portions of it, to predefined locations called dump devices.
The dump process exists so that you have a way of capturing what your system was doing at the time of a crash. This is not for recovery purposes; processes cannot resume where they left off following a system crash. Rather, this is for analysis purposes in order to help you determine why the system crashed and hopefully prevent it from happening again.
system back up quickly. And, if you happen to already know why the computer crashed (for example, if somebody accidently disconnected the wrong cable), there’s little or no need for a dump anyway. With HP-UX, a runtime dump subsystem gives you a lot more control over the dump process. With it you can override dump definitions configured into the kernel while the system is running. An operator at the system console can even override the runtime configuration as the system is crashing.
When you define dump devices, whether in a kernel build or at run time, you can list which classes of memory must always get dumped and which classes of memory should not be dumped. If you leave both of these lists empty HP-UX will decide for you which parts of memory should be dumped based on what type of error occurred. In nearly all cases it is best to let HP-UX determine which pages to dump. IMPORTANT: You can interrupt the dump at any time by pressing the ESC (escape) key.
By reducing the time required to store the entire dump the recovery period is shorter and your system can be returned to service much sooner. Dump compression provides a greater time saving on systems that have large amounts of memory. • Dump compression is not forced, it is only a user request that will be honored if possible. At the time of a system crash the dump subsystem examines the state of the system and its resources to determine whether it is possible to use compression.
The boot time utility called savecrash can be configured (by editing the file /etc/ rc.config.d/savecrash) to compress or not compress the data as it copies the memory image from the dump devices to the HP-UX file system area during the reboot process. This has system recovery time implications in that compressing the data can take longer if the saving occurs as foreground processing (for example, when HP-UX is trying to quickly evacuate a dump device that is also used for paging).
Crash Information Integrity Use this section if your most important criterion is to make sure you capture the part of memory that contains the instruction or piece of data that caused crash.
Example 3-5 Example of a Crash During the Very Early Stages of the Boot Process Consider a server that has ten gigabytes (10 GB) of physical memory. If you were to define system dump devices with a total of two gigabytes (2 GB) of space in the kernel file, and then define an additional nine gigabytes (9 GB) of disk space in the /etc/ fstab file, you would have enough dump space to hold the entire memory image (a full dump) by the time the system was fully up and running.
Disk Space Needs Use this section if you have very limited disk resources for the post-crash dump and/or the post-reboot save of the memory image to the HP-UX file system area. The factors you have to consider here are: • • • Dump Level Compressed Save versus Non-compressed Save Partial Save (savecrash -p) Dump Level You are reading this section because disk space is a limited resource on your server. Obviously, the fewer pages that you have to dump, the less space is required to hold them.
NOTE: It is possible to analyze a crash dump directly from dump devices using a debugger that supports this feature7. But, if you need to save it to removable media or send it to someone you will first need to copy the memory image to the HP-UX file system area. For More Information on Defining Dump Devices The following resources have additional information on defining dump devices: • • • • The manpage crashconf(1M) describes the primary command used to configure crash dumps.
Use the /sbin/crashconf command to configure these options. See the crashconf(1M) for details on how to configure the various options. Operator Override Options When a HP-UX panics, the current dump control option settings are displayed at the system console during a crash. You then have 10 seconds to interact with the system console before the current settings are used to proceed with dump processing.
While the dump is in occurring, status messages on the system console indicate the dump’s progress. IMPORTANT: You can interrupt the dump at any time by pressing the ESC (escape) key. It can take as long as 15 seconds to abort. If you interrupt a dump, it will be as though a dump never occurred; that is, you will not get a partial dump. Following the dump, the system attempts to reboot.
in order to gain the space you need for the savecrash operation; or you can run the savecrash command manually, specifying an alternate destination for the saved data. CAUTION: If you are using your devices for both paging and dumping, do not disable the savecrash boot processing or you will lose the dumped memory image to subsequent system paging activity.
Limitations of Live Dumps There are some key differences between live dumps and true crash dumps, some of which represent limitations: • The key difference between a live dump versus a crash dump is, of course, that HP-UX continues to run while the dump is in progress. The good news is that users of the system continue to work, and are unaffected by the livedump process.
Other Software Operating System Installation Technologies There are several other pieces of the software installation picture: Ignite/UX If you need to install a common set of HP-UX software on multiple systems and would like to do it at one time, from one location, you can use Ignite/UX. See “Ignite-UX” (page 114). update-ux The update-ux command updates the HP-UX operating system from new HP-UX media. See the manpage update-ux(1M) for details.
basically the same functions as the older (still available) utilities cpio and tar. sd(5) sd — overview of Software Distributor: commands to create, distribute, install, monitor, and manage software. shar(1) The shar command bundles the named files and directories into a distribution package suitable for mailing or moving to a new location. Use the posix shell (/usr/bin/sh) to unpack the archive.
elm Though not formally supported by HP, you can also use the following commonly used utilities for reading, composing, and sending electronic mail: Mozilla Mozilla is shipped with HP-UX as it is needed as a default browser for accessing the System Management Homepage. Mozilla includes a built-in E-mail client. rmail If you have installed and use the GNU Emacs editor, you can use its built in E-mail client, rmail.
FTP FTP (file transfer protocol) is an open standard for transferring files between computers. HP-UX, Linux, and Microsoft Windows based computers all support ftp server and client software. FTP is generally used in interactive mode. The user establishes a connection between their local system (the FTP client) and the remote system (running an FTP server).
Remotely Mounted File Systems HP-UX 11i version 3 implements several ways to share file systems and directories between multiple computers. These include: NFS NFS (Network File System) allows you to export file systems or directories from a server to a pre-defined set of servers which in turn will mount the exported file system so that users and processes of those servers can access the remotely mounted file systems as if they were local file systems.
4 System Administration Tools Whether you are managing a single server, multiple servers, multiple operating systems in hard or soft partitions on a multiple cell server or a multiple core server, HP-UX 11i version 3 offers a wide variety of tools to manage and control those resources. This chapter highlights the key system administration tools that are available and what they allow you to control. Table 4-1 System Administration Tools Tool Best Suited for...
Ignite-UX Ignite-UX addresses the need for HP-UX system administrators to perform system installations and deployment, often on a large scale. It provides the means for creating and reusing standard system configurations. It provides the ability to archive a standard system configuration, and to use that archive to replicate systems, with the added benefit of speeding up the process. It also permits post-installation customizations, and is capable of both interactive and unattended operating modes.
Though HP SMH does not have an X Window native interface8, a few applications launched by HP SMH continue to open in ObAM based X Window or ObAM based TUI. A majority of the applications in the Graphical User Interface (GUI) of HP SMH support multi-byte locales. However, the Text User Interface (TUI) of HP SMH does not support locales other than English. Therefore, HP recommends that you run smh(1m) TUI in C locale. NOTE: tool.
where name_of_system_to_administer is the network hostname (or IP address) of the system you want to administer. This will cause the web server on the system to start a secure web interface to the HP SMH. IMPORTANT: For remote web access to HP SMH to be successful, the system you are trying to administer must have its web server running. By default, this means that HP-UX must be at run-level 3 or higher. For a discussion of run-levels, “Run Levels” (page 88).
When the HP SMH GUI interface is launched in a browser, it presents the above screen and requires you to authenticate yourself (log in). Upon a successful login the GUI version of HP SMH presents a slightly different menu than the terminal version does.
• • • • Used for single system management (for single point of control management of multiple systems, “HP Systems Insight Manager (HP SIM)”) Web based (accessible from any supported browser) Secure (uses SSL-secure authentication) Capable of managing a single system running one of these OS types: — HP-UX 11i — Linux (versions of Linux supported by HP) — Microsoft Windows What is HP SMH Doing on Your Behalf? When you perform actions using the HP System Administration Homepage, the interface you interact
HP-UX provides the following commonly used shells for command entry: • • • sh - the POSIX shell ksh - the Korn shell csh - the C shell Though not officially shells, two related utilities work closely with shells to provide multiple sessions on a single terminal: shl The Shell Layer Manager provides a means for interacting with more than one shell from a single using shell layers. Each layer represents a virtual device. The current layer is the one that can receive keyboard input.
Managing Multiple Servers from a Single Point of Control Using HP SIM While the HP Systems Insight Manager can be used to manage a single HP-UX server, it is probably better to use the “HP System Management Homepage (HP SMH)” for that purpose. HP Systems Insight Manager allows you to manage multiple servers called managed systems from a Central Management Server (CMS). Collectively, the CMS and the managed systems are referred to as a management domain.
HP Systems Insight Manager is Based on the WBEM Open Standard The HP Systems Insight Manager is based on the Web Based Enterprise Management (WBEM) standard, a set of technologies designed to consolidate the management of multiple servers of possibly varying OS types, as well as several other open standards. Supplies Information to OpenView As your need grow, the HP Systems Insight Manager can grow with you.
Other System Management Tools There are also other tools to assist you with various aspects of administering an HP-UX system. These include: EVM - Event Management In HP-UX 11i version 3, the kernel, software applications, and the server hardware can post events to the Event Management Daemon. Users can then subscribe to these events in order to be alerted to occurrences of events that concern them.
— Remove cell boards from a partition — Move a cell board from one partition to another • Control power to various server components — Cabinets — I/O Chassis — I/O Slots9 Software Distributor (SD) Software Distributor is a collection of tools used for installing and maintaining applications and other software on an HP-UX server.
swask Used by SD control scripts to solicit information from a user about the software choices they have made. The answers given by the user are stored for later use by swinstall and swconfig. swconfig Configures, unconfigures, or reconfigures software on a server. swconfig transitions software between the INSTALLED and CONFIGURED states independently of swinstall and swremove.
HP-UX 11i version 3 supports the following volume managers: LVM The Logical Volume Manager (LVM) is detailed in HP-UX System Administrator’s Guide: Logical Volume Management. LVM is the default volume manager for HP-UX 11i. VxVM The VERITAS Volume Manager (VxVM) has many features, some of which are not available with LVM or MirrorDisk/UX (the companion product to LVM that allows you to mirror data onto multiple physical disks).
manager you are using. Refer to the documentation for the volume manager you are using for specific information on the differences. Performance Monitoring Tools There are many tools available to help you monitor performance of HP-UX based servers, networks, and applications. Some of these tools are included with HP-UX, some are downloadable from hp.com, and some are commercial products from HP or other companies. This section discusses a few of these tools.
processes listed first in the top output are consuming the most processing time. top also shows global system load factors. vmstat The vmstat command reports certain statistics kept about process, virtual memory, trap, and CPU activity. It also can clear the accumulators in the kernel sum structure. Tools for Monitoring the Performance of a Network Monitoring the performance of a network can be an involved process involving many different variables.
Data Protection Tools Security of servers, networks, and data has never been more important than it is today. HP-UX has many tools for securing your servers and data. For most HP-UX users, securing your servers and data from unauthorized access ranges from important to critical. Unauthorized access (whether malicious or accidental) is only one of many threats to the integrity and security of your data.
• You can backup your data to tapes, optical media, or disk archive files on alternate devices. Some utilities that will allow you to do this include: — HP OpenView Storage Data Protector Software, part of the HP OpenView Suite of products, automates high performance backup and recovery, from disk or tape, over unlimited distances, to ensure 24x7 business continuity and maximize IT resource utilization. For complete details on the HP OpenView Suite, see http:// openview.hp.com.
Disk Mirroring Disk mirroring writes multiple copies of data to separate (physical or logical) devices simultaneously. If you are using LVM (HP’s Logical Volume Manager), you will need to install the optional product, MirrorDisk/UX to use disk mirroring. MirrorDisk/UX supports up to three copies of data if you are using LVM with Version 1 volume groups, and up to six copies of data if you are using LVM with Version 2 volume groups.
on the functions of the failed server while the original is repaired. Persistent Device Special Files HP-UX 11i version 3 introduces a new type of device special file called a persistent device special file. Unlike legacy device special files10 that address devices by the hardware path to them, persistent device special files use unique identifiers built into (or associated with) supported devices to address them.
NOTE: If the driver is not a core driver (one that is always present in the kernel), you will need to install a driver when adding in the new card, even if it is the same type as the one that was deleted. If the driver is a core driver, a new instance of the driver will be created when you add back the new card of the same type. Network Administration Tools Configuring a network can be an involved process involving many different variables.
Use the nwmgr command to configure network interfaces. See the manpage nwmgr(1M) for details on the numerous tasks nwmgr can do. TIP: For users familiar with networking on previous versions of HP-UX, the nwmgr command performs the functions previously served by the (now deprecated) commands: • lanadmin • lanscan • linkloop See nwmgr(1M) for details on using the nwmgr command, and discontinue using lanadmin, lanscan, and linkloop.
Glossary accept One of four commands that control the flow of print requests through the Line Printer Spooling System (spooler). accept instructs the spooler to allow new print requests to be added to the print queue of a printer or class. See also reject, enable, disable. Agile View A view of the I/O device tree using the more flexible and scalable persistent device special files, LUN hardware paths. See also Legacy View. ASCII American Standards Committee on Information Interchange.
Device file types: • • Legacy Device Special Files — the traditional, hardware path dependent style of device special file. Each path to a device has its own device special file. Moving a device means using different device special files to access the device. Persistent device special files — the newer, hardware path independent style of device special files.
Event Management Daemon Part of the Event Manager subsystem, the event management daemon (/usr/sbin/evmd) provides posting and notification services for system and application clients running on the local system. See also Event Manager (EVM) and the evmd1M manpage. Event Manager (EVM) An HP-UX subsystem that provides a mechanism for the posting and retreiving of events. See also events and the evm5 manpage. extended campus cluster See extended distance cluster.
HP SMH (System Management Homepage) The primary single system administration tool beginning with HP-UX 11i version 3. HP SMH supports HP-UX, HP supported versions of Linux, and Microsoft Windows operating systems. iCAP (Instant Capacity) A group of technologies that allow you to activate/deactivate pre-purchased “stand-by” hardware components, paying only for the computing resources you actually consume. This allows you to handle temporary usage demands more cost efficiently.
logical volume A subdivision of a volume group, a logical volume can span multiple physical volumes or represent only a portion of one physical volume. The size of a logical volume is measured in units called extents. The size of logical volumes can be altered after they are initially created. Logical volumes can be extended and, if their contents permit, reduced. Once created, logical volumes can be treated just like disk partitions.
(Directory Tree) In the HP-UX directory tree, each directory, file, or link represents a node. Similarly, HP-UX keeps track of I/O devices using a hierarchy where each component in a hardware path (regardless of which addressing scheme is used) represents a node on the I/O tree. nPartitions Available on cell based servers, nPartitions (also known as hard partitions) provide both operating system and electrical isolation.
of a printer model script. Once created, the printer interface script can then be customized to tailor it to your needs. printer model scripts Scripts — usually supplied as part of HP-UX or by a printer vendor — used as templates (models) from which printer interface scripts are created at the time printers are configured into the Line Printer Spooling System.
run-level A configuration of system processes. Processes spawned by boot init is assigned to one or more run-levels. Only processes having an assignment corresponding to the current system run-level are processed. SAM (System Administration Manager) The primary single system administration tool prior to HP-UX 11i version 3. SAM is supported only the HP-UX operating system. See also HP SMH (HP System Management Homepage). secondary swap HP-UX begins by paging on a single device only (see primary swap).
Utility Meter The software and hardware device that receives PPU utilization information from the PPU software. The utility meter is initially installed and configured by an HP service representative. virtual LUN ID The final element in a LUN hardware path (0x3 in the following example): virtual machine Abstractions of real, physical machines. Multiple virtual machines can share a common set of physical resources. See also Integrity VM guest.
Index A abnormal shutdowns, 93 accept, 83 access control, 85 adding kernel modules, 43 addressing storage, 59 agile addressing benefits of, 62 application performance, 127 auditing, 86 B backing up data, 58 backup utilities, 58 backups, 128 boot loader, 43, 92 boot sequence, 92 booting multiple operating systems, 37 C C shell, 118 cancel, 83 CDFS file system, 54 cell boards, 38 grouping printers.
swlist, 123 swmodify, 123 swpackage, 123 swreg, 123 swremove, 123 swverify, 123 tar, 108 telnet, 41, 110 top, 126 tsm, 118 update-ux, 108, 114 vmstat, 126 who -r, 91 compartments, 86 compressed dumps, 97 compressed saves, 98, 102 concurrent dumps, 97 see dump concurrency, 20 configuring a network interface, 132 containment technologies, 86 Continental Clusters, 34, 37, 42 controlling access to directories and files, 85 core, 18 cpio, 58 crash dumps, 94 compressed dumps, 97 compressed saves, 98 configuring y
efficient data access, 54 electronic mail. See E-mail, 109 enable, 83 enabling swap space, 72 Enterprise-wide management of HP-UX, 121 event management, 122 EVM (the event manager), 122 Extended Campus Clusters, 34, 36, 42 Extended Distance Clusters, 34, 36 F FAT32 file system, 54 fbackup, 58 fence priority (printer).
usage rights, 30 Integrity Virtual Machines, 39 Integrity VM, 39 interface files (printer), 76 iostat, 126 J JBOD, 48 K kernel, 43 adding modules, 43 configuration, 43 logging errors and notification with ProvderSvcsBase, 122 modules, 43 removing modules, 43 tunables, 44 nswapdev, 73 key directories, 45 kill scripts, 89 Korn shell, 118 L lanadmin, 132 lanscan, 132 lazy swap, 71 LDAP-UX, 84 legacy device special files, 45 legacy hardware paths, 66 line printer scheduler, 76 Line Printer Spooling System, 7
terminal emulation, 109 web access, 109 networking technologies, 23, 41 FTP, 41 HTTP, 41 NFS, 41 rcp, 41 rlogin, 41 ssh, 41 telnet, 41 NFS, 48, 112 NFS (Networked File System), 41 nomenclature directory paths, 44 server, 19 noncompressed saves, 98, 102 nPartitions, 38 managing with parmgr, 122 O ObAM, 114 OL*, 20 Online Addition and Replacement PCI cards, 130 Operating Environments, 17, 27 operating systems, 17 electrical isolation, 38 hardware isolation, 38 optical discs, 58 optical media, 48 oserrlogd da
RAID 1, 57 RAID 5, 55 RAID levels, 55 RBAC. See Roll-Based Access Control, 86 rc daemon, 89 rcp, 110 rcp (Remote Copy), 41 rebooting HP-UX, 93 Redundant Arrays of Independent Disks. See RAIDs, 128 reject, 83 Release Notes, 21 remote copy.
defining, 73 device swap, 69, 73 disabling, 72 enabling, 72 file system swap, 69, 70, 74 interleaving, 74 lazy swap, 71 primary swap, 71 pseudo swap, 69, 70 secondary swap, 71 types of, 69 swapinfo, 73, 74 swapoff, 72 swapon, 72 swask, 123 swconfig, 123 swcopy, 123 swinstall, 123 swjob, 123 swlist, 123 swmodify, 123 swpackage, 123 swreg, 123 swremove, 123 swverify, 123 system, 18 System Administration Manager.
VxFS file system, 54 VxVM, 57 See VERITAS Volume Manager, 50 volumes, 52 W web access, 109, 111 web server, 111 WLM, 28 Workload Manager.
