Hp Linux Server Management Software Uživatelský manuál Strana 1

Procházejte online nebo si stáhněte Uživatelský manuál pro Software Hp Linux Server Management Software. HP Linux Server Management Software User Manual Uživatelská příručka

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 98
  • Tabulka s obsahem
  • ŘEŠENÍ PROBLÉMŮ
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 0
Distributed Systems Administration Utilities
User’s Guide
HP Part Number: T2786-90337
Published: March 2009
Edition: 2.1
Zobrazit stránku 0
1 2 3 4 5 6 ... 97 98

Shrnutí obsahu

Strany 1 - User’s Guide

Distributed Systems Administration UtilitiesUser’s GuideHP Part Number: T2786-90337Published: March 2009Edition: 2.1

Strany 2

HP Encourages Your CommentsHP encourages your comments concerning this document. We are truly committed to providingdocumentation that meets your need

Strany 3 - Table of Contents

1 IntroductionThe Distributed Systems Administration Utilities provide several tools for simplifying themanagement of groups of systems and of Service

Strany 4 - 4 Table of Contents

the distribution of ssh keys. The companion utility Parallel Distributed Copy (pdcp) enablesfile and directory copies to be performed in parallel to a

Strany 5 - Table of Contents 5

Table 1-3 Command Fanout Commands (continued)When to Use itWhat it DoesCommandTo check uptime, users, and load averages.Reports uptime(1) information

Strany 6 - List of Figures

Table 1-7 Open Source syslog-ng CommandWhat it DoesCommandTool that performs consolidated logging.syslog-ng1.3 Distributed Systems Administration Util

Strany 7 - List of Tables

The values of the environment variables such as $SGCONF are used in shell command examples.1.5 Red Hat and SLES File Path DifferenceThe location of th

Strany 9 - About this Document

2 Configuration SynchronizationManaging the configuration and configuration drift of a set of distributed systems is a constantchallenge for system ad

Strany 10 - HP Encourages Your Comments

appropriate for each group of managed clients. For example, every five minutes, once anhour, or once a day. The administrator can also invoke cfagent

Strany 11 - 1 Introduction

Figure 2-1 cfengine Overview13452cfexecd cron + /var/opt/dsau/cfengine/inputs -update.conf -cfagent.conf -cfservd.conf -cfrun.hosts+ /var/opt/dsau

Strany 12

CopyrightCopyright ©2007, 2009 Hewlett-Packard CompanyLegal NoticesConfidential computer software. Valid license from HP required for possession, use

Strany 13 - 1.2 Open Source Components

synchronization service to groups of remote client systems. Those clients can be standalonesystems or Serviceguard clusters. The cluster providing the

Strany 14

NOTE: If you have used the wizard previously to configure a cfengine master server and rerunit to reconfigure the master server, stop the currently ru

Strany 15

Enter choice: 1The cfengine master server is being configured on: local_hostnameThe wizard then asks if you would like to additionally configure manag

Strany 16

Note that when configuring a master server but not adding any managed clients during theserver configuration, the members entry (list of managed clien

Strany 17 - 2.1 cfengine Overview

Configuration Synchronization Wizard Menu=========================================(1) Set up a cfengine master server(2) Add a client(3) Remove a cli

Strany 18

Once the storage infrastructure is configured and the IP address obtained, press return to accessthe default answer of ‘yes’ and proceed with creating

Strany 19 - Master Server

Verifying that the master has an entry in the /etc/hosts fileon each client...Starting cfengine on the master server and any managed clients.This may

Strany 20 - 2.3 Configuring cfengine

update.conf and cfagent.conf define the master configuration synchronization server tobe the registered DNS name for the relocatable IP address of the

Strany 21 - 2.3 Configuring cfengine 21

NOTE: When adding members to a cluster, consider the following:• When adding a member to a cluster that is configured as a highly available master ser

Strany 22

A remote Serviceguard cluster can be configured as a managed client. However, each membermust be configured individually. Repeat the configuration tas

Strany 23 - 2.3 Configuring cfengine 23

Table of ContentsAbout this Document...9Intende

Strany 24

NOTE: You can use csshsetup to configure a trust relationship between the master serverand the managed clients. This will allow you to use command fan

Strany 25 - 2.3 Configuring cfengine 25

the client’s domain could be determined based on the client’s IP address or subnet, asfollows:classes: # host in these ip address ranges xyz_dom

Strany 26

9. The file /var/opt/dsau/cfengine_master/inputs/cfservd.conf controls whichmanaged clients have access to the files served by cfservd on the master.

Strany 27 - 2.3 Configuring cfengine 27

Serviceguard package and the mechanism used to distribute cfengine’s security keys. Follow allthe steps described below.• Initial Serviceguard Package

Strany 28

It is critical to keep this file very simple and avoid errors. Errors in this file will requiremanually copying a new version to each managed client.T

Strany 29 - 2.3.2 Manual Configuration

• Edit the cfservd.conf FileThe file /var/opt/dsau/cfengine_master/inputs/cfservd.conf controls whichmanaged clients have access to the files served b

Strany 30

This will create keys named localhost.priv and localhost.pub in the directory/var/opt/dsau/cfengine/ppkeys.2. The public key, localhost.pub is then co

Strany 31 - 2.3 Configuring cfengine 31

# cp /dsau/share/serviceguard/templates/csync.script.templatecsync# chmod +x csync3. Edit the csync.conf package ASCII configuration file to replace t

Strany 32

5. Distribute the package control script and package ASCII configuration files clusterwide:# ccp csync csync.conf $SGCONF/csync/6. Apply the package a

Strany 33 - 2.3 Configuring cfengine 33

# scp localhost.pub master_server:\ /var/opt/cfengine/ppkeys/root-client_IP_address.pubIt is important to use a utility such as secure copy (see scp(

Strany 34

3.3.1 Using the Log Consolidation Wizard...503.3.1.1 Configuring a

Strany 35 - 2.3 Configuring cfengine 35

synchronization. For details on using cfexecd in daemon-mode, refer to the cfengine tutoriallocated in /opt/dsau/doc/cfengine/.2.4 Security Notescfeng

Strany 36 - • Create the csync Package

2.4.3 EncryptionIn general, file transfer traffic between the master server and a managed client is not encrypted.For many system management related c

Strany 37

• Most cfagent.conf actions such as "copy," "editfiles," and "processes," supporta syslog = true option to cause the spe

Strany 38

cfrun(0): ... [ Hailing host1 ] ...cfrun(0): ... [ Hailing host2 ] ...cfrun:host2: Couldn’t open a socketcfrun:host2: sock

Strany 40 - 2.4 Security Notes

3 Consolidated LoggingDistributed Systems Administration Utilities offers consolidated logging features, including thestandard logging features offere

Strany 41 - 2.6 Logging Options

Table 3-2 syslog Facilities Messages (continued)DescriptionMessageUSENET news subsystem.LOG_NEWSMessages generated internally by syslogd.LOG_SYSLOGGen

Strany 42 - 2.7 cfengine Troubleshooting

• Improved filtering functionality. In addition to syslog's facility/priority level filtering,syslog-ng can perform regular expression filtering

Strany 43

Figure 3-1 syslog-ng Log-Forwarding Configuration1432syslog-ngfifosyslog-ngsyslogd cmcld TCP/IPor UDPLogreader+/var/log/ messages maillog+ /usr/loc

Strany 44

Figure 3-2 syslog-ng Log Consolidator Configuration132syslog-ngfifosyslog-ngsyslogd cmcld TCP/IPor UDPLogreader+/var/log/ messages mail logA BCCon

Strany 45 - 3 Consolidated Logging

A.3 Uninstalling the DSAU rpm from your System...91B HP-Supported Open Sourc

Strany 46 - 3.1.2 Message Filtering

IMPORTANT: The following notes are particularly for SLES 10 users.On Red Hat syslogd and syslog-ng coexist and both have different start up scripts wh

Strany 47 - 3.2.2 syslog Co-existence

For a standalone system, the wizard first displays introductory paragraphs explaining logconsolidation and then asks:Do you want to configure log cons

Strany 48 - 48 Consolidated Logging

source s_syslog_tcp { tcp(port(tcp_port) keep-alive(yes)max-connections(N)); };where N is the expected number of clients.Next, the wizard prompts for

Strany 49 - -xclock.log

The wizard will set up and create a Serviceguard package for the consolidated logging service.Make sure that this cluster’s MAX_CONFIGURED_PACKAGES va

Strany 50

LVM” in the chapter “Building an HA Cluster Configuration,” in the Managing Serviceguardmanual.NOTE: The wizard only supports creating packages based

Strany 51

to local port port_number using the TCP protocol. For high availability the Serviceguard package "clog" will be configur

Strany 52 - 52 Consolidated Logging

DSAU maintains two configuration files that control whether the instance of syslog-ng on aparticular cluster member operates as a consolidation server

Strany 53

stanzas added in this section direct syslog-ng to filter package log messages into theappropriate consolidated package logs.— The clog_tail log monito

Strany 54 - 54 Consolidated Logging

After entering the hostname or IP address of the log consolidation server, the wizard asks if youwant to use the TCP transport when forwarding log mes

Strany 55

When forwarding a cluster’s package logs, manual configuration is required on the consolidationserver in order to add the syslog-ng filtering lines to

Strany 56 - 56 Consolidated Logging

List of Figures2-1 cfengine Overview...

Strany 57 - - Consolidation server

Manual configuration is required for the following cases:• When a cluster is a log forwarding client and forwarding package logs, manual configuration

Strany 58 - 58 Consolidated Logging

destination d_syslog { file(“<%FS%>/syslog/syslog.log”); }; becomes:destination d_syslog { file(“/clog/syslog/syslog.log”); }; Make sure that th

Strany 59 - Starting syslog-ng

default suppresses duplicate messages. If you issue multiple logger test messages, makesure each is unique.3.3.2.2 Manually Configuring a Serviceguard

Strany 60 - 60 Consolidated Logging

1. To configure syslog-ng, start with the same syslog-ng.conf templates used by theclog_wizard. On one cluster member, copy/opt/dsau/share/clog/templa

Strany 61

2. Manually replace the tokens in /etc/syslog-ng.conf.client on Red Hat or /etc/syslog-ng/syslog-ng.conf.client on SLES as follows:a. Delete the <%

Strany 62 - 62 Consolidated Logging

3.3.2.2.1 Creating the clog PackageTo create the consolidated logging or clog package, start by copying the package templates:# mkdir $SGCONF/clog# cd

Strany 63

7. Find the line “FS_FSCK_OPT[0]=“<%SG_PKG_FS_FSCK_OPT%>”” and replace the tokenwith any filesystem specific fsck options. The token can be dele

Strany 64 - 64 Consolidated Logging

1. Run /sbin/syslog-ng with the -s or --syntax-only option to verify the syntax ofthe/etc/syslog-ng.conf.server and/etc/syslog-ng.conf.client files on

Strany 65

5. Validate that log forwarding is working properly. If consolidating the cluster’s local syslogs,use “logger <test message>” and make sure this

Strany 66 - SUBNET[0]= 192.119.152.0

3.3.2.3.1 Manually Configuring a Standalone Log Forwarding Client1. To configure syslog-ng, start with the same syslog-ng.conf templates used by thecl

Strany 67

List of Tables1 Conventions...

Strany 68 - 68 Consolidated Logging

2. The syslog-ng startup procedure, /etc/init.d/syslog-ng, relies on severalconfiguration variables. Edit as follows:/etc/sysconfig/syslog-nga. Change

Strany 69

1. To configure syslog-ng, start with the same syslog-ng.conf templates used by theclog_wizard.On one cluster member, copy the /opt/dsau/share/clog/te

Strany 70 - 70 Consolidated Logging

2. The syslog-ng startup procedure, /etc/init.d/syslog-ng, relies on severalconfiguration variables. Edit /etc/sysconfig/syslog-ng as follows:a. Chang

Strany 71

6. Test the configuration by performing the following steps:a. Run /sbin/syslog-ng with the -s or --syntax-only option to verify the syntaxof the /etc

Strany 72 - 72 Consolidated Logging

CLOG_TEXT_LOG[1]=/var/adm/logs/mylog.logCLOG_TEXT_FORMAT[1]="custom"If the text file is already formatted using the syslog-compatible format

Strany 73

1. For each text log that will be forwarded from a client, add the following destination, filterand log lines to the file syslog-ng.conf.server, after

Strany 74 - 74 Consolidated Logging

Restart syslog-ng on all cluster nodes.3. For each text log that is deleted from a client that is forwarding its text logs, delete thecorresponding de

Strany 75

3.4 Disabling Log ConsolidationThe clog_wizard enables log consolidation configurations but does not have an unconfigureor deconfigure option. Thus yo

Strany 76 - 76 Consolidated Logging

2. Edit the /etc/sysconfig/syslog-ng file and change the CLOG_CONFIGURED line tothe following:CLOG_CONFIGURED=0Remove all other CLOG lines except for

Strany 77

traffic within a Serviceguard cluster (member to member). Standard TCP or UDP is used forintra-cluster log traffic.ssh port forwarding is transparent

Strany 79

Then from each log consolidation client, perform a standard ssh key exchange with the relocatableIP address of the clog package. One way to do this is

Strany 80 - 3.6 Viewing Consolidated Logs

3.6.2 Using the System Log ViewerThe System Log Viewer will display the syslog-related logs for the system. By default, thisincludes the local logs fo

Strany 82

4 Command FanoutCommand fanout utilities allow the system administrator to replicate shell commands acrossmultiple systems. Traditionally, administrat

Strany 83 - 4 Command Fanout

• Parallel copy commandThe pdcp command provides a parallelized copy command to copy a local source file tomultiple targets.• Setting ssh argumentsUse

Strany 84 - 4.2 pdsh Utility Wrappers

ckill ckill allows the administrator to signal a process by name since the pid of a specificprocess will vary across a set of systems or the members o

Strany 85 - 4.3 Security Configuration

If the “r” services are not disabled, use of the pdsh -R rsh option by unprivileged users is stilldisabled by default because of the inherent security

Strany 86

Table 4-3 Target Node Error MessagesTo CorrectCauseMessageUse full paths to specify commands.The command does not exist on thetarget node. The remote

Strany 88

A Installing DSAU on LinuxThis appendix describes how to install DSAU on Linux to run on supported HP Integrity andProliant servers. These instruction

Strany 89 - A Installing DSAU on Linux

About this DocumentDistributed Systems Administration Utilities provide tools to simplify the management of groupsof systems and of Serviceguard clust

Strany 90

Configuring the syslog-ng startup scripts.Configuring System Log Viewer for Systems Insight ManagerConfiguring System Log Viewer for System Management

Strany 91

Use "/etc/init.d/hpsmhd restart".The installation of the HP Distributed Systems Administration Utilities (DSAU) has finished.To complete the

Strany 93

B HP-Supported Open Source pdsh OptionsThis release of DSAU includes open source pdsh code that was compiled with the followingoptions:• readline supp

Strany 95

IndexAadoptive node, 28, 55alertchecksum, 41authentication errors, 42Bbackup file, 26Bastille, 80Berkeley commands, 85blanksin configuration files, 42

Strany 96 - 96 Index

Kkeyexchange, 40integrity, 39public/private, 27, 35security, 29, 38known host fingerprint, 79Llockdown toolBastille, 80log consolidation, 55configurat

Strany 97

LVM, 24subdirectoriestimestamped, 26synchronization clientconfiguring, 28syslogintroduction, 45message format, 45syslog-ng, 47syslogd, 45, 47System Ma

Komentáře k této Příručce

Žádné komentáře