HP-UX System Administrator's Guide: Overview HP-UX 11i Version 3 HP Part Number: B3921-90011 Published: September 2010 Edition: 5
© Copyright 2008, 2009, 2010 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..............................................................................................................................11 Intended Audience................................................................................................................................11 About this Series...................................................................................................................................11 About this Document:.......................................
Instant Capacity (iCAP/TiCAP/GiCAP)..........................................................................................27 Technology Summary................................................................................................................27 Tools to Administer/Configure..................................................................................................27 iCAP Commands............................................................................................................
Storage and Data Redundancy........................................................................................................49 Establishing Multiple Paths to a Device (for redundancy)........................................................50 RAIDs and other Disk Arrays....................................................................................................50 Disk Mirroring.......................................................................................................................
Stopping (Shutting Down) HP-UX..................................................................................................77 Abnormal Shutdowns (System Crashes).........................................................................................78 Overview of the Dump / Save Cycle..........................................................................................78 Preparing for a System Crash....................................................................................................
Performance Monitoring Tools...........................................................................................................102 Tools for Monitoring the Performance of a Server........................................................................102 Tools for Monitoring the Performance of a Network....................................................................103 Tools for Monitoring the Performance of Applications.................................................................
List of Figures 2-1 2-2 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 8 Virtualization Technology Categories Matrix...............................................................................21 The Virtualization Technology Stack............................................................................................37 Directory Tree Example.................................................................................................................40 Logical Volumes can be Resized.............................
List of Tables 1 2 3 2-1 2-2 3-1 3-2 4-1 Finding HP-UX Information.........................................................................................................12 HP-UX 11i Releases.......................................................................................................................12 OS Version, System Architecture, and Machine Model................................................................13 A Partitioning Technology Comparison............................................
List of Examples 3-1 3-2 3-3 3-4 3-5 4-1 10 Directory Path Name Nomenclature.............................................................................................40 Hardware Path Format Summary.................................................................................................58 Default Printer (example)..............................................................................................................69 Run Level Transition Examples...........................................
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.
Finding HP-UX Information Table 1Outlines where to find general system administration information for HP-UX. This table does not include information for specific products. Table 1 Finding HP-UX Information If you need to. . . Refer to . . . Located at . . . Find out: • What has changed in HP-UX releases • The content of the Operating Environments • Firmware requirements, and supported systems for a specific release The HP-UX 11i Release Notes specific to your version of HP-UX.
Table 2 HP-UX 11i Releases (continued) OS Version Identifier Release Name Supported Processor Architecture B.11.31.0803 HP-UX 11i Version 3, March 2008 Update HP 9000 and Integrity 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 B.11.31.1003 HP-UX 11i Version 3, March 2010 Update HP 9000 and Integrity B.11.31.
Emphasis Text that is strongly emphasized. KeyCap The name of a keyboard key. Note that Return and Enter both refer to the same key. Term The defined use of an important word or phrase. UserInput Commands and other text that the user types. Variable The name of a variable that you may replace in a command or function or information in a display that represents several possible values. $ User command prompt. # Superuser (root) command prompt.
func ( param[, param]...); For example: setuname ( name[, namelen]...); The function syntax elements are the same as for commands, except for the options. Publication History The document publication date and part number indicate its current edition. The publication date will change when a new edition is released. To ensure that you receive the new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details.
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.
Processor Terminology The HP-UX System Administrator’s Guide uses the following terminology: NOTE: The items in this list represent an introduction to terminology used throughout the HP-UX System Administrator's Guide. A more comprehensive list of terms is located in the “Glossary” (page 109). Core Represented in this document by the double-gear symbol above, a “core,” (formerly referred to as a “CPU”) is an individual processing unit on a processor chip (see processor).
Server Nomenclature When describing servers, cell boards, or other components capable of holding processor chips, HP now uses the nomenclature xP/yC, where x refers to the maximum number of processors the item can hold, and y refers to the maximum number of cores the item can hold. Examples: • A server defined as a 1P/1C server (representing one processor/one core) is the simplest of all functional configurations. It contains one, single-core processor.
can be configured to split the task of dumping memory and write to the devices in parallel. This process is called dump concurrency and is configured using 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 78).
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.
• • • 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. One operating system spanning multiple2 servers represents clustering technology The following sections discuss each of the virtualization categories and describe which HP-UX technologies to use if you need to configure your system(s) to take advantage of each category. 2.
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.
Load Balancing (One Multiple Core Server, One Operating System Instance) While the HP-UX scheduler does a good job of utilizing multiple cores when they are available, sometimes you need (or want) to override the default scheduling algorithms, for example to dedicate processing resources to an important application.
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. Tools to Administer/Configure The Process Resource Manager can be configured using the HP System Management Homepage or from a series of PRM management and configuration commands.
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.
• • Instant Capacity Compatibility with Processor Sets VSE Concepts and Terminology Instant Capacity (iCAP/TiCAP/GiCAP) Technology Summary Instant Capacity technology allows you to purchase at a significantly reduced price: cores, memory, and cell boards that you do not yet own (and cannot yet use). These components, known as iCAP components or components without usage rights, are standing by, ready for activation when you need them.
icapmanage Global Instant Capacity (GiCAP) management commands for GiCAP groups. icapmodify icapmodify - Activate and deactivate cores. Specify system contact e-mail address. Change Instant Capacity (iCAP) configuration information. Specify Instant Capacity from e-mail address. Specify system identifier. Specify temporary capacity warning period. Apply iCAP codewords.
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.
For Further Information You can find comprehensive information about Pay per use and the Utility Meter in the following documents: • • • 30 Utility Meter User Guide—See the latest version of this guide at http://www.hp.com/go/ hpux-core-docs. HP Pay per use (PPU) User's Guide—See the latest version of this guide at http://www.hp.com/ go/hpux-core-docs. You can get additional information and access the sign-in page for the Pay per use Portal at http://www.hp.com/go/payperuse.
Clustering (Multiple Servers, One Operating System) Clustering technologies enable multiple servers to work in unison to present the appearance of a single computing environment. Technically, each server is running its own operating system, but they work together as if they were one.
System Multi-node System Multi-node Packages run (simultaneously) on all nodes in Serviceguard cluster. They remain running as long 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.
Continental Clusters A continental cluster is a group of clusters that use routed networks or common carrier networks for data replication and cluster communication to support package failover between separate clusters in different data centers. Continental clusters are often located in different cities or different countries, and can span hundreds or even thousands of miles.
Multiple Boot (One Single-Core Server, Multiple Operating Systems) Or HP Integrity Servers are capable of running multiple types of operating systems (for example, HP-UX 11i, Linux, and Microsoft Windows). Depending on your server model, multiple versions of these operating systems might also be supported. If you only have a single available core, you cannot have multiple operating systems running simultaneously.
Partitioning (Multiple Operating Systems, One Multi-processor Server) When you have multiple cores available, more virtualization possibilities become available as well. This area of virtualization technology is known as partitioning. There are several types of partitioning available on HP systems, but they fall into two major categories—hardware partitioning and software partitioning.
Software Partitioning vPar 1 vPar 2 vPar 3 Software partitioning provides for finer grained partitioning than nPartitions. HP offers two products to accomplish software partitioning: 1. 2. vPars - Virtual Partitions Integrity VM - Integrity Virtual Machines Using either of these two products, you can partition your server at the processing core level. Integrity VM even allows sub-core-level partitioning.
Combining Partitioning Technologies for Greater Flexibility By themselves, the various server partitioning technologies give you a very flexible compute environment, but you can combine them for even greater flexibility and control. The following illustration shows how nPartitions, vPars, and Integrity Virtual Machines can be combined on a single server to support a large amount of work.
Networking (Multiple Operating Systems, Multiple Servers) Unless the physical servers are each running in standalone mode — “Standalone Systems (One Single-Core Server, One Operating System Instance)”) — when you have multiple operating systems running on an equal or lesser number of physical servers, the virtualization technologies that can be used to flexibly use their resources fall into the networking category of virtualization technologies.
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.
NOTE: Some kernel tunables have their values set at boot time and cannot be changed without rebooting. Other kernel tunables can be “tuned” (have their settings adjusted) while the kernel is running. The HP-UX Directory Structure HP-UX 11i, like all versions of UNIX and many other operating systems, is based on a hierarchical directory structure that contains all of the operating system directories and files, as well as all user and application files.
devices, get status of the devices, or to control those devices in some other way.
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.
tmp files are not usually removed during system startup, but when (or whether) files in either of the tmp directories are removed is configurable and installation specific. Storage on HP-UX Of all the resources managed by any operating system, arguably the most important is storage. Storage is a generic term referring to devices that store data. Storage can take many forms, including: • Physical disk drives locally attached to a server: — SCSI hardware protocol disks — Fibre Channel disks — USB 2.
• • • DLT tape drives / libraries Magneto-optical drives / libraries DDS tapes Disk drives can be: • Individual drives • Drive enclosures (groups of multiple disk drives that are treated as individual drives) • Disk Arrays (like drive enclosures but with an added disk controller for local intelligence in managing the contained storage (for example, RAIDs) • SAN - Storage Area Networks (physical drives attached to a dedicated network) • NAS - Network Attached Storage (storage attached to dedicated servers
Selecting a Volume Manager With HP-UX 11i version 3, there are two volume managers to choose from: • The HP Logical Volume Manager (LVM) • The VERITAS Volume Manager (VxVM) You can use both simultaneously (on different physical disks), but usually you will choose one or the other and use it exclusively. Table 3-1 provides a comparison of the two volume managers to help you determine which will best suit your needs.
NOTE: VERITAS Volume Manager is available in several versions as of the Release of HP-UX 11i version 3. Values and features shown are for VxVM Version 4.1. Consult the VERITAS Volume Manager Release Notes of the appropriate version for that version’s specifications. The VERITAS Volume Manager has two licensing levels, base and full. Unless stated otherwise, the features listed in the previous table are for the base level license.
(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.
Supported File Systems As with volume managers, HP-UX offers you several choices of file system types to choose from. Specifically: HFS The HP proprietary High-Performance File System supports files and file system sizes up to 128GB. VxFS The VERITAS File System Version 4.1 supports file sizes up to 16TB and file system sizes up to 40TB. VxFS is also known as OnlineJFS/JFS 4.1.
RAID 5 Striping using data blocks with parity information evenly distributed across the devices in the stripe set. The parity information can be used to reconstruct the missing data if a drive should fail. The stripe set can function with one missing drive and, when the failed drive is replaced, the parity information on the remaining drives can be used to reconstruct the missing data (formerly on the failed drive).
• • Do you need off site copies of your data? How often do the data change? 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.
Data Backups At any point in time, data can be copied using any one of a number of utilities. The destination for the copies of data can be removable media that can be stored off site or shipped to another location for safe keeping. Removable media that can be used for backups include: • other disks • magnetic tapes — DLT — DDS • optical discs — recordable DVDs — recordable CDs — magneto-optical disk libraries You can even back up files to a file on an alternate disk (as in the case of a tar archive).
Table 3-2 Storage Components and how they are Addressed Stack Component How it is addressed File System Once created, a file system is usually addressed by its mount point, the directory in the HP-UX directory tree that represents the root of the files in that file system. RAW access Not all logical / physical volumes contain file systems.
The Anatomy of a Device Special File Device Special Files (DSFs) are comprised of the following parts: file name This is the name of the file that appears in the /dev directory tree major number A number used to identify which driver to use to communicate with the device/LUN associated with that device special file The major number is an index for the device driver into one of two kernel tables — bdevsw, the block device switch table and cdevsw, the character device switch table.
===================================================== 64000/0xfa00/0x2 disk HP 36.4GMAN3367MC 64000/0xfa00/0x3 disk HP 36.4GMAN3367MC Legacy versus Agile Device Addressing Beginning with HP-UX 11i version 3, mass storage devices are referenced by device instances rather than by the hardware paths to the devices. This has many benefits over the previous addressing scheme which associated a given device special file with the hardware path to a device.
is the default load balancing algorithm for serial devices (for example tape drives). preferred_path The I/O path set in the preferred_path attribute is preferably used for I/O transfer. If this I/O path is not available or if the preferred_path attribute was not set, any other path is selected for I/O transfer. This policy is useful for certain disk arrays, which may exhibit some performance degradation if I/Os are transferred via several I/O paths to a LUN simultaneously.
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 disk devices /dev/dsk on a server. /dev/rdsk Contains legacy device special files for character mode access to physical disk devices on a server.
Lunpath Hardware Paths This format is used for addressing LUNs in agile mode. It is identical to the legacy hardware path format up to the host bus adapter (HBA). Beneath the HBA, two additional address elements are represented (in hexadecimal): Target address A transport dependent address identifying the physical device associated with the hardware path LUN address A 64-bit representation of the LUN identifier reported by the target. 0/2/1/0.0x50001fe1500170ac.
Example 3-2 Hardware Path Format Summary The three formats described previously are different ways of referring to the same LUN, so a single LUN could have all of the following addresses: 0/2/1/0.1.4.0.0.2.7 0/2/1/0.1.5.0.0.2.7 0/4/1/0.1.4.0.0.2.7 0/4/1/0.1.5.0.0.2.7 0/2/1/0.0x50001fe1500170ac.0x4017000000000000 0/2/1/0.0x50001fe1500170ad.0x4017000000000000 0/4/1/0.0x50001fe1500170ac.0x4017000000000000 0/4/1/0.0x50001fe1500170ad.
ioscan ioscan performs many functions. Primarily it scans a server’s hardware, binding new hardware with appropriate drivers. With regard to device special files, ioscan can display the mapping between legacy device special files and persistent device special files. See ioscan(1M) for details on ioscan’s many functions and options. scsimgr scsimgr, like ioscan, has many functions other than working with device special files.
Types of Swap Space There are three types of swap space used for paging operations: • Device Swap • File System Swap • Pseudo Swap Device Swap Swap space is initially allocated when you configure your disks. Device swap space occupies a logical volume or disk partition that is typically reserved expressly for paging purposes. This space may also be configured as a dump area but doing so has implications for memory dump integrity if a crash occurs.
If you choose to use the pseudo swap capability (actually, it is enabled by default), an amount of pseudo swap space equal to 7/8ths of the amount of physical ram available to your server, nPartition, or virtual partition is used as pseudo swap. Lazy Swap Another technology that takes advantage of the fact that not all swap space that is reserved is actually used is lazy swap.
NOTE: To get a snapshot of the total amount of swap space currently being used, use the command: # /usr/sbin/swapinfo -tam TYPE dev Mb Mb Mb PCT START/ AVAIL USED FREE USED LIMIT 4096 0 4096 0% 0 - 1 - 0 - reserve - 257 -257 memory 1940 562 1378 29% total 6036 819 5217 14% Mb RESERVE PRI NAME /dev/vg00/lvol2 This number will vary over time, depending on the current mix of applications running, but if the total percentage used is regularly high, roughly 90% or greater, t
If you have only one disk and need to increase swap space, try to move the primary swap area to a larger region on the disk. To see which devices are already being used for device swap use the command: swapinfo -d • Try to keep multiple device swap areas similar in size. Device swap areas should have similar sizes for best performance.
For More Information on Configuring and Managing Swap Space The following manpages contain important information on configuring swap 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 40)), 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.
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.
Figure 3-7 Line Printer Spooler “Plumbing” Diagram 66 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.
Printer model files are required in the following procedures: • • • Adding a Local Printer to the LP Spooler — see HP-UX System Administrator’s Guide: Configuration Management (Chapter 6: Configuring Printers) Adding a Remote Printer to the LP Spooler — see HP-UX System Administrator’s Guide: Configuration Management (Chapter 6: Configuring Printers) Adding a Network-Based Printer — see HP-UX System Administrator’s Guide: Configuration Management (Chapter 6: Configuring Printers) The model scripts are ASC
printer class called “accounts”. A printer can belong to more than one class, however remote printers cannot belong to a printer class. It is not necessary to have every printer be part of a class; you can have some of your printers grouped in classes while others remain independent. To use a printer class you direct print requests to the class, name rather than to a specific printer. The print request is spooled to a single print queue and printed by the first available printer in the class.
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. Summary of Line Printer Spooling System Commands These are the commands associated with the line printer spooling system and a summary of what they do. See their respective manpages for complete details.
reject Prohibits new print requests from being submitted to a print queue (associated with a printer or class). enable Allows the printing of queued print requests to the specified printer. disable Inhibits the printing of queued print requests to the specified printer. If the print queue associated with the printer is still accepting new requests the requests will build up in the queue until the printer is again enabled.
Directories Who can search the contents of the directory, add files to, remove files from, or rename files in the directory, and who can cd to the directory. There is a lot more to the topic of legacy Unix file ownership and privileges and there are other, more powerful, mechanisms that allow you to carefully control and monitor who is accessing the files and directories on your system. An entire volume of the HP-UX System Administrator’s Guide is devoted to the topic of security.
system call access, access is usually “all or nothing” based on the user's effective UID. HP-UX Role-Based Access Control (HP-UX RBAC) enables you to group common or related tasks into a role. For example, a common role might be User and Group Administration. Once the role is created, you assign to specific users a role or set of roles that enables them to run the commands defined by those roles.
transitioning down through the run levels it cleanly terminates all running processes and writes any memory based information to disk, ensuring properly structured file system linkages on disk. run level s Also known as single user mode, run level s allows input only from the terminal (or pseudo-terminal) known as the system console. This allows one user, usually a system administrator, to have exclusive access to the server usually for maintenance operations that must be done on a quiescent system.
2. /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.config.d directory.
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.
NOTE: If your goal is to transition HP-UX to single-user mode from a higher run level, do not use init s. This could leave processes running and disks mounted that you do not want present. Use the shutdown command with no parameters to transition to run level s, or to be absolutely certain no undesirable processes or mounted file systems are present, reboot the system to single-user mode by interrupting the boot process and using the secondary boot loader (hpux.
1. 2. 3. First, notify everyone who is likely to be affected by the shutdown, giving them a chance to complete work in progress, and if necessary unmount file systems that were NFS-mounted from your system. Then, shutdown any programs you might be running that would not be safely shutdown by one of the system’s kill scripts (“Startup and Kill Scripts (Run Level Transitions)”). Finally, use the shutdown command to shut down the system. The shutdown command: a.
• • • In the kernel During system initialization when the initialization script for crashconf runs (and reads entries from the /etc/fstab file) During run time, by an operator or administrator manually running the /sbin/crashconf command Preparing for a System Crash 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.
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. You have control over the following crash dump features: • • • Which classes of memory get dumped. Run-time crash dump configuration.
Likewise, if at the time of a crash you know what caused it (and therefore do not need the system dump) but have previously defined a full or selective dump an operator at the system console at the time of a crash can override those definitions and request that no dump be performed. Concurrent Dumps On servers with very large amounts of memory, the process of writing memory contents to disk can take a very long time.
• • If your server uses virtual partitions (vPars), the dump might not be compressed but the dump process will proceed. If more than one crash occurs in close succession, it might not be possible for HP-UX to compress the dump. Compressed Save versus Noncompressed Save System dumps can be very large, so large that your ability to store them in your HP-UX file system area can be taxed. The boot time utility called savecrash can be configured (by editing the file /etc/ rc.config.
Full Dump versus Selective Dump You have chosen this section because it is critical to you to capture the specific instruction or piece of data that caused your system crash. The only way to guarantee that you have it is to capture everything. This means selecting to do a full dump of memory. Be aware, however, that this can be costly from both a time and a disk space perspective.
NOTE: The preceding example is presented for completeness. The actual amount of time between the point where kernel dump devices are activated, and the point where runtime dump devices are activated is very small (a few seconds), so the window of vulnerability for this situation is very small. Using a Device for Both Paging and Dumping (Crash Integrity) It is possible to use a specific device for both paging purposes and as a dump device.
Partial Save (savecrash -p) If you have plenty of dump device space but are limited on space in your HP-UX file system, you can use the -p option to the savecrash command. This command copies only those pages on dump devices that are endangered by paging activity (the pages residing on devices that are being used for both paging and dumping). Pages that are on dedicated dump devices are not copied.
You can choose to do the following: C option [CURRENT] Proceed with the current settings. Use this to immediately proceed with the current settings, not waiting for the 10-second override period to automatically expire. S option [SELECTIVE] Proceed with a selective dump with both compression and concurrency turned off, regardless of what was previously configured. F option [FULL DUMP] This option is available if enough dump space has been configured to hold the contents of the entire physical memory.
Dual-Mode Devices (dump / swap) By default, savecrash is enabled and performs its copy during the boot process. You can disable this operation by editing the /etc/rc.config.d/savecrash file, setting the SAVECRASH environment variable to a value of 0. This is generally safe to do if your dump devices are not also being used as paging devices.
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.
when an opportunity to reboot the system is available, the patched or updated clone can be booted. This reduces system downtime to just the time it takes to reboot to the clone. Also, if necessary, the changes can be quickly backed out by simply rebooting to the original clone. Software Manager Software Manager is used by Ignite-UX and Update-UX to perform software installation.
NOTE: Before you can use any of the networking services, you need to configure at least one network interface on your server. Use the nwmgr command to configure the interface. See the nwmgr(1M) manpage and “Configuring a Network Interface” (page 107) for additional information.
Windows based system. In addition to the following protocols, applications and custom programs can transfer files using inter process communication (via system calls): 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.
Samba 92 Samba is an implementation of Microsoft’s SMB (Server Message Block) protocol (and other protocols) that allows for a directory and its sub-directories to be shared between multiple computers.
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...
Update-UX The update-ux command is the tool to use to update one version of HP-UX to a newer version (provided that you are using a supported upgrade path). For details on supported upgrade paths and general update procedures, see the latest version of the HP-UX 11i v3 Installation and Update Guide. For details on the update-uxcommand and its options, see the update-ux(1M) manpage.
-------------------------------------------------------------------------------a - Auditing and Security c - Auditing and Security Attributes Configuration(new) d - Peripheral Devices e - Resource Management f - Disks and File Systems g - Display k - Kernel Configuration l - Printers and Plotters(new) n - Networking and Communications p - Printers and Plotters s - Software Management u - Accounts for Users and Groups -------------------------------------------------------------------------------x-Exit smh
IMPORTANT: Read carefully any warnings that appear when you start your web browser. There are possible security implications in launching the System Management Homepage in this way and HP SMH will identify safer alternatives to launch the System Management Homepage via a secure http (https) URL should you require that.
• • Software Installation, Removal, and Management and many others Using the HP System Management Homepage you can also: • • Launch (X-based) Applications Run Commands TIP: Unlike SAM, the HP System Management Homepage (because it is based on the WEBM industry standard) can also administer Linux and Microsoft Windows based systems.
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.
NOTE: HP Systems Insight Manager is capable of managing large groups of systems but for Enterprise-wide operations HP recommends the more powerful OpenView Suite of tools. 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.
To subscribe to events, a user (or system administrator) can use the System Management Homepage (use Tools →Evweb →Subscription Administration) or the evweb command (see the evweb(1) and evweb_subscribe(1) manpages). ProviderSvcsBase New since March, 2009 is the ProviderSvcsBase product, which notifies subscribing clients of HP-UX kernel error log records. A daemon called oserrlogd reads the records, stores them in the circular log files, and then sends EVM notification to subscribing clients.
Utilities for Creating and Maintaining Packages of Software for use by the Above Utilities The following Software Distributor utilities are used for creating and maintaining packages and installation bundles of software and software installation sources (known as software depots) that are used by swinstall, swlist, swremove, and swverify: sd Invoke interactive interface to display and monitor SD job information, to remove SD jobs, and to clone/recreate SD jobs.
Volume managers allow you to group collections of physical storage (usually disk drives) and then divide the collections into logical entities called logical volumes if you are using the HP Logical Volume Manager, or simply volumes if you are using the VERITAS Volume Manager. 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.
HP Caliper The primary purpose of HP Caliper is profiling individual applications, however Caliper is also capable of displaying overall system performance information. HP Caliper can be downloaded from: http://www.hp.com/go/ caliper HP Caliper is also supported on versions of Linux for HP Integrity servers. NOTE: HP Caliper is available only for HP Integrity Servers. For HP 9000 servers, consider using Prospect, a performance monitoring tool. See http:// www.hp.com/go/prospect.
Example 4-1 Testing network performance using ping To test a network connection between two systems called “thissystem” and “thatsystem”, from a local command prompt on “thissystem” enter the command: /usr/sbin/ping thatsystem PING thatsystem.xxx.yyy.com: 64 byte packets 64 bytes from 10.17.123.456: 64 bytes from 10.17.123.456: 64 bytes from 10.17.123.456: 64 bytes from 10.17.123.456: icmp_seq=0. icmp_seq=1. icmp_seq=2. icmp_seq=3. time=1. time=0. time=0. time=0.
Trusted Mode Offers a complete C2-level set of security features. Passwords are not stored in the /etc/passwd file, but are instead stored in /tcb/files for additional security. Protecting Against Data Loss The best way to protect your data against loss is to have another copy of the data somewhere when the primary copy is lost. There are many technologies that will help you make those extra copies.
with Version 1 volume groups, and up to six copies of data if you are using LVM with Version 2 volume groups. If you are using the VERITAS Volume Manager, the ability to mirror your root volume group is built in to the base product. By licensing the full version of the VERITAS Volume Manager, you gain the ability to mirror all your volume groups, up to 32 copies of the data. RAIDs and Surestore Disk Arrays Data redundancy can also be accomplished at the hardware level.
Online Replacement suspends the driver instance associated with the failed card and powers down the slot so the card can be replaced with a new one of the same type. Then power can be restored to the slot and new card, and the driver resumed. Online Deletion removes from the running kernel the driver instance associated with the failed card and powers down the slot so the card can be removed. You can then (optionally) install a new card of the same or different type using Online Addition.
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. Refer to the HP-UX LAN Administrator's Guide for information on these basic tasks. There are many networking documents to assist you with the specific components of networking you want to use.
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 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. extended distance cluster A cluster with alternate nodes located in different data centers separated by some distance.
Installed Product Database A database of software currently installed on a server, created and maintained by the Software Distributor suite of utilities. See “Software Distributor (SD)” (page 100). Integrity VM guest An instance of HP-UX running within an Integrity virtual machine. interleaved swap Swap space spanning multiple physical devices for read/write efficiency, similar to disk striping. See also disk striping.
major number The part of a device special file that determines whether the file is used for block access or character access and also used to determine which device driver to use when communicating with the device. managed systems Any system managed by HP Systems Insight Manager, including servers, desktop PCs, and Remote Insight Boards. management domain A collection of resources called managed systems that have been placed under the control of the HP SIM.
operating system Software that controls the resources of a system (or partition). An instance of HP-UX running in an nPartition, vPars virtual partition, or HPVM virtual machine Other operating systems commonly found on HP Integrity servers include Linux and Microsoft Windows. partition A grouping of server resources dedicated to an instance of an operating system. See also nPartition, virtual partition, Integrity VM guest.
reject One of four commands that control the flow of print requests through the Line Printer Spooling System (spooler). reject instructs the spooler to prevent print requests from being added to a print queue. See also accept, enable, disable. remote printer A printer connected directly to a remote instance of HP-UX (“system”). Print requests to a remote printer must first travel over a network to the remote system.
stale device special file A device special file no longer associated with a valid device. For example, a device file associated with a device that has been removed from a server. storage stack The various layers of hardware and software the comprise HP-UX based storage systems.
virtualized LUN hardware path See LUN hardware path. volume group A collection of physical volumes (physical disks), used by the Logical Volume Manager. Volume groups can be subdivided into logical volumes (flexible virtual disks that can contain file systems, swap space, or used as dump devices or raw disk access). See also logical volume. vPars See Virtual Partition.
Index A abnormal shutdowns, 78 accept, 70 access control, 71 adding kernel modules, 39 addressing storage, 51 agile addressing benefits of, 54 application performance, 104 auditing, 72 B backing up data, 51 backup utilities, 51 backups, 105 boot loader, 39, 77 boot sequence, 77 booting multiple operating systems, 34 C C shell, 97 cancel, 70 CDFS file system, 48 cell boards, 35 grouping printers.
telnet, 38, 90 top, 102 tsm, 97 update-ux, 88, 94 vmstat, 102 who -r, 76 compartments, 72 compressed dumps, 81 compressed saves, 82, 84 concurrent dumps, 81 see dump concurrency, 19 configuring a network interface, 107 containment technologies, 72 Continental Clusters, 31, 33, 38 controlling access to directories and files, 71 core, 18 cpio, 51 crash dumps, 78 compressed dumps, 81 compressed saves, 82 configuring your system for, 79 crash information integrity, 82 defining dump devices, 83 dump concurrency,
F fbackup, 51 fence priority (printer).
nswapdev, 62 key directories, 40 kill scripts, 74 Korn shell, 97 L lanadmin, 107 lanscan, 107 lazy swap, 61 LDAP-UX, 71 legacy device special files, 40 legacy hardware paths, 56 line printer scheduler, 64 Line Printer Spooling System, 64 classes, 68 commands, 64, 70–71 components of, 64 Integration with LDAP-UX, 71 plumbing diagram of, 64 printer groups (classes), 68 remote spooling, 67 system default printer, 69 linkloop, 107 LiveDump system dumps without the crash, 87 livedump command, 87 LiveDump limita
Operating Environments, 17, 25 operating systems, 17 electrical isolation, 35 hardware isolation, 35 optical discs, 51 optical media, 43 oserrlogd daemon, 100 P paging, 59 paging devices, 82, 84 parmgr, 100 partial saves, 82, 85 Partition Manager, 100 Partitioning hardware, 35 hardware versus software, 35 types of, 35 partitioning technologies, 21 combining, 37 comparison of, 36 isolation, 36 partition boundaries, 36 terminology, 36 pax, 51 Pay per use, 29 Active Cores, number of, 29 Core percent utilizati
root file system, 40 mirroring, 50 root volume group, 102 run level transitions, 74 run levels, 73, 76 S SAM, 94 Samba, 91 sar, 102 savecrash, 84, 85 savecrash processing, 86 SCSI-3 hardware paths, 57 sd, 100 secondary swap, 61 Secure FTP, 90 security, 71 auditing, 72 compartments, 72 containment technologies, 72 fine-grained privileges, 72 Roll-Based Access Control, 72 Standard mode, 72 Trusted mode, 72 user database, 72 selective dump, 83, 84 server, 18 Server message Block Protocol, 91 server nomenclatu
dump sequence, 86 non-compressed save, 84 operator override options, 85 partial saves, 85 post reboot activities, 87 preparing for, 79 rebooting, 86 savecrash processing, 86 selective dump, 84 what happens during a crash, 85 system default printer, 69 System Management Homepage. See HP SMH, 94 system recovery time, 80, 82 system run levels, 76 T tapes, 43 tar, 51 telnet, 38, 90 terminal emulation, 89, 90 Terminal Session Manager, 97 TOC.
