|
|
United States-English | |
|
|
 |
|
E1197: Planning and Configuring HP DCE 1.7 > Chapter 3 Before Installing HP DCE/9000 Version
1.7
Preinstallation Planning |
|
|
In general, preinstallation planning involves deciding how many cells to configure at your site, which systems to include in each cell, and where to run DCE services (Security, CDS, DTS, and GDA). This section gives you some guidelines for making decisions prior to installation. Before installation you should map the boundaries of your cell by listing the systems that will compose your cell. You may find it practical or necessary to divide your site into more than one cell. Consider the following factors when determining the cell boundaries:
To implement intercell communications, you must start at least one Global Directory Agent (GDA) daemon per cell. You can start a GDA daemon when you configure your cell, as described in Chapter 5, "Configuring HP DCE". In addition, you must name your cells according to Domain Name Service (DNS) convention. When a query cannot be resolved within a cell, GDA passes the query to a DNS server. The following is an example of a cell name using the DNS format: /.../xyz.abc.com If your site is connected to the Internet and you want to obtain a unique DNS name, contact the administrator in charge of the domain under which you want to name your cell. For more information on cell naming, see the OSF DCE Administration Guide - Core Services. For configuration information, see Chapter 5, "Configuring HP DCE". This section outlines some considerations and restrictions on HP DCE/9000 Version 1.7 software that will help you map out the installation of your cell. Core Services are contained in the DCE-Core product. This product must be installed on every system in your cell. Security server software is contained in the DCE-SEC-Server product. The system(s) running the security server should be reliably accessible and physically secure. They should also have enough disk space to hold a registry database that could expand significantly over time as the number of users increases. HP has found the following guidelines to be sufficient:
More information about DCE Security Services may be found
in the In configuring CDS servers and clients, pay careful attention to the HP DCE/ 9000 hardware requirements for the DCE product. (See "Hardware and Software Requirements" in this chapter.) Appropriate kernel configuration, memory, disk, and especially swap space are essential to the proper functioning of the CDS subsystem. Tape backups of the CDS server database are extremely important for recovery from catastrophic problems. HP strongly recommends regular tape back ups of all CDS server databases, especially those containing any master replicas. Tape backups and restorations require the CDS server in question to be temporarily shut down. Most CDS problems, however, do not require resorting to tape backup. Directory replication provides continuous online backup for most failures, with faster recovery and less stale data. This makes directory replication highly desirable for all DCE cells. Every cell should configure at least two CDS servers, and read-only replicas of all directories should be created on the backup server. In this configuration, backup is continuous, and recovery only involves switching the role of the servers. Multiple CDS servers can be configured for specific purposes in the cell. Multiple CDS servers with read-only replicas of all directories in the name space should always be present for backup and recovery purposes. Performance considerations may also make the configuration of other CDS servers desirable. For instance, administrators of very busy cells or cells with large numbers of nodes should consider adding additional CDS servers to share the name space processing load. Similarly, administrators of cells with groups of nodes separated by WAN links should consider providing a local CDS server for each group to enhance performance. Administrators with very large cells may want to partition the name space among several CDS servers, replicating only the locally used directories, to distribute the storage overhead of the name space. Each of these CDS configuration strategies is documented in the OSF DCE Administration Guide - Core Services. A minimum of three DTS servers is recommended for any cell with three or more member systems. If you use an external time provider, you can have only one of these running in a cell. If you are running AFS, be sure to run the AFS daemon (afsd)
with the See the OSF DCE Administration Guide -- Core Services for more information about DCE Distributed Time Services. At this release, intercell time synchronization is not supported. The HP DCE/9000 Version 1.7 software is divided into products and filesets. Tables Table 3-1 “HP DCE/9000 Version 1.7 Products and Filesets—Core HP-UX” and Table 3-2 “HP DCE/9000 Version 1.7 Products and Filesets—Applications Release” show the HP DCE 1.7 filesets, arranged according to product, and gives the approximate disk space requirement for each file set. Table Table 3-1 “HP DCE/9000 Version 1.7 Products and Filesets—Core HP-UX” includes the products that are bundled with HP-UX; Table Table 3-2 “HP DCE/9000 Version 1.7 Products and Filesets—Applications Release” contains the products distributed on the Applications Release media. Note that the information in Tables Table 3-1 “HP DCE/9000 Version 1.7 Products and Filesets—Core HP-UX” and Table 3-2 “HP DCE/9000 Version 1.7 Products and Filesets—Applications Release” is also available from swinstall. Note the following:
Table 3-1 HP DCE/9000 Version 1.7 Products and Filesets—Core HP-UX
Table 3-2 HP DCE/9000 Version 1.7 Products and Filesets—Applications Release
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
