|
|
United States-English | |
|
|
 |
|
HP-UX 11i Release Notes: HP 9000 Computers > Chapter 4 HP-UX 11i Operating Environments
HP-UX 11i Operating Environment (new) |
|
|
The HP-UX 11i Operating Environment consists of the HP-UX operating system, the 11i Operating Environment (OE) software bundle, and additional applications and drivers that you can selectively install. The HP-UX 11i Operating Environment includes the following applications:
The Apache Web Server for HP-UX Version 1.4 (01.03.12.03) is an HTTP/1.1 compliant server which implements the latest protocols, including HTTP/1.1 (RFC2616). The server includes software developed by the Apache Group for use in the Apache HTTP server project. It can be customized by writing software modules using the Apache module API. The HP-UX 11i release of the Apache Web Server includes pre-compiled binaries that have been preconfigured to run on HP-UX 11.0 and later releases. It is supported on 32-bit and 64-bit systems. It runs as a 32-bit binary on 64-bit HP-UX 11.0 and 11i. It is NOT supported on HP-UX 10.20. This version of the Apache Web Server is a 32-bit product with 128-bit strong encryption. Apache SSL connections use a default dummy certificate provided by HP.
For HP-UX 11i, the Apache Web Server is perl-enabled but not configured, and will not allow the execution of perl scripts unless mod_perl is configured. Detailed configuration and installation instructions are provided in the online Apache release notes (/opt/apache/apache.release.notes) included with the Apache Web Server software.
If you are installing Apache Web Server for HP-UX separately from the rest of the OE bundle, or if you obtained the Apache product (B9415AA) independently of the HP-UX 11i Operating Environment, follow these steps:
Installing a product or a fileset may automatically install dependent filesets necessary to run the selected items. If an HP or non-HP version of Apache is already on the system, swinstall preserves the existing configuration files under /opt/apache/conf, /opt/apache/conf/jserv and /opt/tomcat/conf by renaming <files> to <file>.save. It also preserves certificates and certificate-related files under /opt/apache/conf/ssl.* directories by renaming <file> to <file>.save. In this way, you will not lose previous configuration information. However, the original configuration file (<file>.save) will be over-written if you re-install Apache. Upon successful installation, swinstall runs Apache Web Server automatically. Installation instructions are also included in the online Apache release notes (/opt/apache/apache.release.notes) that come with the Apache software. For more information on the Apache Software Foundation, see: With CIFS/9000 Client and CIFS/9000 Server Version A.01.04, Hewlett-Packard provides a Common Internet File System (CIFS). CIFS is the Microsoft protocol for remote file access. CIFS is built into the operating system of all recent Windows systems including Windows 95, 98, NT 4.0, and 2000. By providing both server and client, CIFS/9000 provides file and print interoperability for environments with a mix of UNIX and Windows platforms. The following changes have been made for HP-UX 11i:
Product documentation is also available on the HP-UX 11i Instant Information CD and on the web at: The documents available include:
The Event Monitoring Service (EMS) Version A.03.20.01 is a framework that is used to monitor various system resources. In addition to the basic monitoring framework, the EMS product includes a set of general monitors for basic network interfaces, system resources and ServiceGuard cluster objects. EMS is being released for use with the HP-UX 11.0 and HP-UX 11i operating systems, and is included in the HP-UX 11i Operating Environment. This release has all the features found in earlier versions in addition to new functionality, defect repairs and support for new hardware configurations. The EMS Version A.03.20.01 is a minor release, with minor changes and defect fixes. The contents of EMS releases A.03.00 through A.03.10 have been incorporated, together with all A.03.10 patches.
With HP-UX 11i, EMS adds a new state to the package monitor: UNAVAIL. If the monitor does not have sufficient information to determine status, the current value for the resource is set to UNAVAIL.
The user's manual for this version is Using the Event Monitoring Service (B7612-90015). Also, refer to the Event Monitoring Service Version A.03.20 Release Notes (B7609-90011) for additional information. Both of these publications are available on the HP-UX 11i Instant Information CD and on the web at: The HP-UX Runtime Environment for the Java™ 2 (JRE) Platform Version 1.2.2.04Ha contains the basic components for executing a Java application on HP 9000 Enterprise Servers, HP 9000 Workstations, and HP Visualize Workstations.
This release is a maintenance release that provides many defect fixes. The previous release was 1.2.2.03. See “Execute Protected Stacks (new)” for the impact to Java of the new Execute Protected Stacks feature. Java documentation is provided on the HP-UX 11i Instant Information CD and on the web at: A complete set of HP-UX Support Tools for verifying, troubleshooting, and monitoring HP 9000 system hardware, including CPUs, memory, interface cards, and mass storage devices are available for online, offline and automatically with EMS Hardware Monitors. Support Tools Manager (STM) is the platform for executing online diagnostics. The commands to start it are xstm (GUI interface), mstm (menu-driven interface), cstm (command line interface) or stm (general). Offline Diagnostic Environment (ODE) is the platform for executing offline diagnostics. Normally it is run from the Support Plus CD with the system offline. EMS Hardware Monitors allow you to monitor the operation of a wide variety of hardware products and be alerted immediately if any failure or other unusual event occurs. The EMS Hardware Monitors are started automatically with no user intervention. The HP-UX Support Tools have been modified to support new products, such as, Superdome systems. With HP-UX 11i, the Support Tools are automatically installed when the Operating Environment bundle is installed from the HP-UX 11i Operating Environment CD. It is no longer necessary to load the Support Tools from the Support Plus Media. The Support Plus Media, also containing the Support Tools, will continue to be distributed. As always, offline tools are run from the Support Plus CD, and they cannot be run from the HP-UX 11i Operating Environment CD.
Disk space required by the HP-UX 11i Support Tools is comparable to the disk space required for previous releases in the range of 60-70MB. There are minor changes in monconfig, the user interface for configuring EMS Hardware Monitors. These changes relate to the client configuration files which have been added to support the multiple-view (Predictive-enabled) feature. If you have scripts which invoke monconfig, the scripts may have to modified. For more information on these changes, refer to "Adding a Monitoring Request" in Chapter 2 of the EMS Hardware Monitors User's Guide (June 2000 or later edition) available on the web at: Alternately, you can just run monconfig on HP-UX 11i to see the revised dialog. For detailed descriptions of the individual changes over the past releases of the Support Tools, see the DIAGNOSTICS.readme, the STM Release Notes, and the EMS Hardware Monitors: Release Notes. These publications are available on the web at: This site also has tutorials, FAQs, Release Notes, and manuals documenting the Support Tools. Some documentation is available through other means, for example, the Support Plus CD and the HP-UX 11i Instant Information CD. However, the web pages should provide the latest information. The instant Capacity on Demand (iCOD) Version B.02.01 provides additional processor capacity instantly on N-, L-, and V-Class servers without requiring a system reboot. That is, this can be done dynamically while HP-UX is running. This enables applications to take advantage of the additional CPU power while staying online. For HP-UX 11i, the iCOD client software bundle, in coordination with Online Diagnostics, provides the functionality to activate processors while online and monitor iCOD processors. There are correlated process management and command changes that are being made to properly track statistics related to iCOD processors. The iCOD software supports participation in the iCOD program, iCOD processors can be ordered and installed or added to the N-, L-, and V-Class processors. These processors remain inactive until activated through the iCOD client software. This allows you the flexibility to increase the processor capacity on your servers as needed for capacity growth. These systems must be set up to send e-mail direct to HP for monitoring purposes of iCOD purchases. Applications may or may not respond immediately to the additional processor capacity without restarting. The normal OS process is to begin scheduling processes on the newly activated processors. However, the application may have specific threads bound to processors that aren't bound to the new processor and optimization to the new processing environment may not occur until the application is restarted. Per processor licensing by applications may also be impacted and have to be assessed. Correlated, and HP-UX 11i approved, changes to process management system calls related to deallocation and allocation of iCOD processors have been made. These changes affect the system calls pstat_getdynamic and mpctl. pstat_getdynamic returns the number of active processors in pst_dynamic.psd_proc_cnt. Previously, it was always the same as pst_dynamic.psd_max_proc_cnt. The pst_dynamic.psd_proc_cnt field now excludes deactivated processors. In the past, a call to pstat_getdynamic returned fields psd_proc_cnt (number of active processors) and psd_max_proc_cnt (max active = processors), and they usually had the same value. This is because all processors in the system are usually active. Consequently, these fields could be used interchangeably even though they had different meanings. With iCOD these fields are no longer interchangeable. Care must be taken to use the proper field for the intended use. The pstat system call has changed such that a call to pstat_getdynamic() returns with the pst_dynamic.psd_proc_cnt field containing the number of active processors. This value is less than pst_dynamic.psd_max_proc_cnt when iCOD CPUs are present in the system. Four other fields are adjusted in pst_dynamic structure. They are psd_avg_1_min, psd_avg_5_min, psd_avg_15_min, and psd_cpu_time[]. psd_avg_1_min is calculated by summing up the corresponding entries in psd_mp_avg_1_min[] and dividing by psd_max_proc_cnt. In effect, psd_avg_1_min reflects the average values of psd_mp_avg_1_min[]. The change is made to exclude the values of the deactivated processors when summing up entries in psd_mp_avg_1_min[]. The sum is then divided by psd_proc_cnt. This eliminates taking values of deactivated processors into account. psd_avg_5_mim and psd_avg_15_min is adjusted in a similar way. Similarly, psd_cpu_time[i] reflects the average values in psd_mp_cpu_time[][i]. The adjustment is again to exclude the values of deactivated processors in psd_mp_cpu_time[][i] and dividing by psd_proc_cnt. This eliminates taking values of deactivated processors into account for each load average value. Notice that even though these average fields are adjusted, no information is lost because psd_mp_avg_*_min and psd_mp_cpu_time[] still contain deactivated processor values. The mpctl() changes include:
This is in line with the current specification of pstat and mpctl. Prior to HP-UX 11i, the following commands incorrectly used the fields in pstat and mpctl: top, sar, uptime, iostat, and vmstat. These commands are fixed in HP-UX 11i in order to work correctly on iCOD systems. These changes are only relevant to iCOD systems and systems running the LPMC monitor in OnlineDiag; they do not affect other systems. This feature improves performance by allowing additional parallel processing capacity for applications when iCOD activations occur. It has a temporary side effect of allowing additional I/O interrupt handling capacity via the deactivated processors. This aspect changes once I/O revectoring is implemented. Applications that are aware of the number of processors in the system may need to be modified to work properly on an iCOD system. Applications that are dependent on the number of active processors most likely are dependent on the system calls mpctl and pstat. System measurement software may or may not be impacted by iCOD because of these process management changes. Written properly, the measurement software will correctly measure the active processors only. MeasureWare and GlancePlus fall in the category of working correctly. The system call pstat_getdynamic() returns a structure which contains the fields psd_proc_cnt. This field was previously always equal to psd_max_proc_cnt. However, now that processors can be deallocated, psd_proc_cnt can be less than psd_max_proc_cnt. Some products and commands which use these fields have done so incorrectly. For example, given a system with eight processors four of which are deallocated, psd_proc_cnt will contain four and psd_max_proc_cnt will contain eight. Previously, the fixes to mpctl and pstat, psd_proc_cnt would contain eight. iCOD customers are required to assess if their applications function correctly with iCOD. A workaround is available to run iCOD systems in an "offline" activation mode which would allow any application to work properly in an iCOD environment. For more detailed information about iCOD, see the following documents:
The Runtime Plug-in (JPI) Version 1.2.2.04Ha for HP-UX 11.0 and 11i Java™ Edition allows you to utilize a version of the JRE that is different from the JRE embedded with Netscape Navigator 4.61 or later. Using this release of the Runtime Plug-in for HP-UX, Java Edition, you can access the HP-UX Runtime Environment for the Java 2 Platform from within Netscape Navigator 4.61 or later.
For HP-UX 11i, the Runtime Plug-in is packaged as a standalone product. The size of the Runtime Environment for Java 2 .depot file has been reduced considerably by removing the Plug-in and offering it as a separate downloadable file. Netscape Communicator Version 4.7x (B.11.11.05) includes Netscape's popular web browser Navigator, as well as Messenger and Composer. Communicator offers the complete set of tools for browsing dynamic web content plus complete email capability. Netscape provides periodic maintenance releases for enterprise customers that include minor feature enhancements as well as improvements to overall stability. Pluggable Authentication Modules (PAM) Kerberos Version B.11.11 is an authentication service for authenticating users or services across an open network. HP-UX 11i provides Kerberos authentication through a Kerberos-Client product which is a part of the HP-UX operating system core. Kerberos is the primary authentication mechanism for Windows 2000. Windows 2000 integrates Kerberos authentication mechanism with Active Directory Service to provide enterprise-wide account management. This necessitates the implementation of the Kerberos authentication mechanism on HP-UX as a Pluggable Authentication Module. Pluggable Authentication Modules (PAM) [OSF RFC 86] is the standard mechanism which is easily configurable to support multiple authentication technologies on HP-UX. PAM Kerberos provides the PAM mechanism and encryption support. The PAM service modules were implemented as a shared library, libpam_krb5.1. This library is built by linking with libkrb5.1, and is therefore not dependent on the libsys.sl library. The HP-UX 11i implementation of Kerberos Version 5 protocol provides enterprise-wide strong user authentication. Using encryption during the user authentication process, Kerberos infrastructure provides privacy and integrity of user login information since passwords are no longer communicated in clear text over the network. HP-UX system entry services can work with any Kerberos V5 Server, namely, MIT Kerberos and Microsoft Windows 2000. Thus, passwords can be effectively unified in an Intranet with heterogeneous systems such as UNIX and Microsoft Windows 2000. Furthermore, support of password change protocol automates propagation of password changes. These two features can significantly reduce user administration complexity in a heterogeneous environment. The HP-UX applications using PAM include telnet, login, remsh, ftp, rexec, rlogin, dtlogin, and rcp. PAM Kerberos interoperates with a Key Distribution Center (KDC) operating on either a UNIX or a Microsoft Windows 2000 server. The PAM Kerberos module is compliant with IETF RFC 1510 and Open Group RFC 86. PAM Kerberos is also available under the product number J5849AA on the Applications Software CD. This product provides a libpam_krb5.1 library, a pam_krb5(1) manpage and a release note document. The minimum disk space required to install the product is 1MB. Additional disk space of about 1KB per user in the system /tmp file is required to store initial Ticket Granting Ticket in the credential cache file. HP-UX PAM Kerberos is implemented under the PAM framework that allows new authentication service modules to be plugged in and made available without modifying the application or rebooting the system. PAM Kerberos works on HP 9000 workstations or servers with a minimum of 32MB of memory and sufficient swap space (a minimum of 50MB is recommended).
PAM Kerberos (libpam_krb5.1) and PAM DCE (libpam_dce.1) plug-in modules can not be stacked together in the pam.conf file because of different principal styles and credential file paths. If so stacked, the results will be unpredictable. The Kerberos system ftp service may list the /etc/issue file before the expected output. The sis(5) manpage provides detailed information. You cannot login if the password has expired on a Microsoft Windows 2000 KDC. You will be asked for a new password but you cannot log in. This is a known problem in Windows 2000. When changing passwords on a MIT KDC with a version prior to 1.1, up to 45 seconds may elapse before the password is actually changed due to the protocol selection mechanism of the change password protocol. The following changes apply for HP-UX 11i:
ServiceControl Manager (SCM) Version A.01.01.05 allows you to manage groups of HP-UX systems from a central server. This helps to reduce IT costs and makes it easier to manage multiple systems. For HP-UX 11i, SCM includes the following enhancements:
The following changes apply for HP-UX 11i:
The Netscape Directory Server Version B.04.11 is an industry-standard Lightweight Directory Access Protocol (LDAP) directory server. Netscape Directory Server 4.11 for HP-UX is now a selectable product for the HP-UX 11i Operating Environment. This release includes features from earlier versions in addition to defect repairs.
You must purchase Extranet Client Access Licenses to use the Netscape Directory Server for HP-UX if the directory contains any entries for Extranet Users. An Extranet User is an entry in the Netscape Directory that represents a person that is not an employee nor a full-time independent contractor of the company to which the Netscape Server is licensed. Contact your HP sales representative to purchase licenses. For contact information, see: For installation instructions, refer to the Netscape Directory Server 4.11 for HP-UX Release Notes (J4257-90006) available on the HP-UX 11i Instant Information CD and on the web at: The I/O cards with drivers that are selectable during HP-UX 11i installation include:
The HP Web Quality of Service (WebQoS) Peak Packaged Edition Version B.01.02.06 is a web-based solution that provides the quality of service needed to maintain your web applications. This product is now available on HP-UX 11i. There are no new features for this release.
Installation requirements for this product are:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
