VMware PACKAGE MANAGER 1.1 Manuel d'utilisateur

Naviguer en ligne ou télécharger Manuel d'utilisateur pour Logiciel VMware PACKAGE MANAGER 1.1. Zenoss Service Dynamics Resource Manager Installation Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 95
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 0
Zenoss Service Dynamics
Resource Manager
Installation
Release 4.2.5
Zenoss, Inc.
www.zenoss.com
Vue de la page 0
1 2 3 4 5 6 ... 94 95

Résumé du contenu

Page 1 - Installation

Zenoss Service DynamicsResource ManagerInstallationRelease 4.2.5Zenoss, Inc.www.zenoss.com

Page 2

Installation considerations3file systems can be detrimental to I/O performance. At a minimum, Zenoss recommends using a separate filesystemfor $ZENHOM

Page 3

Installation considerations41.6. Post-installation performance tuningAfter your installation is complete, there are several configuration settings you

Page 4

5Chapter 2. Installing Resource ManagerThis chapter provides detailed instructions for installing Resource Manager on RHEL or CentOS systems, versions

Page 5

Installing Resource Manager6• Scientific support• Server PlatformTo determine which package groups are installed on a host, log in to the host as root

Page 6 - 3. Related guides

Installing Resource Manager7yum -y remove $(rpm -qa | egrep -i '(jdk|jre|java)')b. Download the self-installing binary of Oracle Java SE Run

Page 7 - 5. We welcome your comments

Installing Resource Manager81. Download the Resource Manager RPM file from the Zenoss Support site. Contact your Zenoss representative forlogin creden

Page 8 - 1.3. Hardware requirements

Installing Resource Manager9IPv6: service ip6tables stop; chkconfig ip6tables off NoteYou may open all ports at this time, and then close unneeded por

Page 9 - 1.3.2. Storage considerations

Installing Resource Manager102.6. Install and initialize ZenUpThis release of Resource Manager includes a recommended patch set (RPS) to fix issues un

Page 10

Installing Resource Manager112.8. (Optional) Install the WMI-based Windows Monitor-ing PackageNoteIf the Windows systems to monitor in your environmen

Page 11 - Installation considerations

Installing Resource Manager122.10. Getting startedAfter installation, use your Web browser to browse to the hostname of the server where Resource Mana

Page 12

Zenoss Service Dynamics Resource Manager InstallationCopyright © 2014 Zenoss, Inc., 11305 Four Points Drive, Bldg 1 - Suite 300, Austin, Texas 78726,

Page 13 - 2.2. Preparation tasks

Installing Resource Manager13Figure 2.2. Setup Wizard: Step 12.10.1. Set the administrator password and create a userFollow these steps to select a pa

Page 14

Installing Resource Manager14Figure 2.3. Setup Wizard: Step 22.10.2. Add devicesYou can add devices manually, or give Resource Manager network or IP a

Page 15

Installing Resource Manager151. Select the Autodiscover devices option.Figure 2.4. Setup Wizard: Step 22. For each network or IP range in which you wa

Page 16 - 2.5. Install MySQLTuner

Installing Resource Manager162.10.2.3. LDAP configurationAfter adding or discovering devices, you have the option to configure LDAP for single sign-on

Page 17 - 2.7. Start Resource Manager

17Chapter 3. Adding a collectorThis chapter describes how to add a local or remote collector to Resource Manager.Adding local collectors to the Resour

Page 18

Adding a collector18Table 3.1.Option Name Security Scenario Notesroot user pass-word• The Resource Manager administrator hasthe root password of the c

Page 19 - 2.10. Getting started

Adding a collector19a. Log in as root, or as a user with superuser privileges.b. Change to enforcing in permissive mode (avoiding the need to reboot)

Page 20

Adding a collector20for svc in memcached snmpd; do chkconfig $svc on; service $svc start; done3.2.2. Root user passwordFollow these steps to install a

Page 21 - 2.10.2. Add devices

Adding a collector214. Log in to the master host as user zenoss and enter the following command. Substitute the fully-qualified domainname of the coll

Page 22

Adding a collector22b. If the preceding command returns a result, remove the packages.yum -y erase $(rpm -qa | egrep -i "matahari|qpid")3. E

Page 24 - Chapter 3. Adding a collector

Adding a collector23Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)6. Install the Zenoss dependencies repository.RHEL/CentOS 5: rpm -U

Page 25 - 3.2.1. Preparing to install

Adding a collector24chmod 700 .sshtouch .ssh/authorized_keyschmod 600 .ssh/authorized_keys2. Log in to the master host as user zenoss and enter the fo

Page 26

Adding a collector25chkconfig --level 2345 zenoss on

Page 27 - 3.2.3. Root user SSH keys

26Chapter 4. Installing a hubThis chapter describes how to install a Resource Manager hub on a host other than the master host. The zenhubdaemon is CP

Page 28 - 3.2.4. Zenoss user SSH keys

Installing a hub27yum clean all5. Install Libxslt, Memcached, and Net-SNMP, configure them to start when the host starts, and start them.yum -y instal

Page 29

Installing a hub284.2. Deploying a hubResource Manager provides 3 optons for adding hub hosts, to support different security scenarios. The following

Page 30 - 3.2.4.3. Configure SSH access

Installing a hub29• Hub ID, the logical name of the hub.The name can be any unique combination of letters, digits, and dashes.• Host, the fully-qualif

Page 31

Installing a hub30 hub-host "cat - >> /root/.ssh/authorized_keys"The ssh command prompts you to confirm the connection.5. E

Page 32 - Adding a collector

Installing a hub314.2.3. Zenoss user SSH keysPerform these procedures to install a new hub using the SSH authentication keys of the zenoss user on the

Page 33 - Chapter 4. Installing a hub

Installing a hub32./jre-6u45-linux-x64-rpm.bine. Add the JAVA_HOME environment variable to /etc/profile.echo "export JAVA_HOME=/usr/java/default&

Page 34

Zenoss Service Dynamics Re-source Manager Installationiv4.2.3.3. Configure SSH access ...

Page 35 - 4.2. Deploying a hub

Installing a hub336. Remove the weekly cron job that packs the Zope Object Database (ZODB).rm -f /etc/cron.weekly/zenoss7. Set a new password for the

Page 36 - 4.2.2. Root user SSH keys

Installing a hub34The convention of presenting an incremented port number when creating a new hub is used to avoid port collisionon the Resource Manag

Page 37

35Chapter 5. Performance tuningThe sections in this chapter describe the options for optimizing the performance of Resource Manager.5.1. Packing the Z

Page 38 - 4.2.3. Zenoss user SSH keys

Performance tuning36Figure 5.1. ZenTuneTo run ZenTune, click Update (located at the bottom left of the page).ZenTune returns information about current

Page 39

Performance tuning37Run memcached as close to the master as possible, as zopectl and zeneventd are its biggest users. In very large databasescenarios

Page 40 - 4.2.3.3. Configure SSH access

Performance tuning38Increasing the values of write_timeout and write_delay to some multiple of the polling period (by default, 5 minutes)will decrease

Page 41

Performance tuning39exchange.default.compression = Value where possible values are:• deflate - Use DEFLATE algorithm• none - Do not compress messagesB

Page 42 - Chapter 5. Performance tuning

Performance tuning40• Use the -b or --amqpheartbeat option at the command line.NoteSetting the heartbeat value to 0 turns it off.5.9. Increasing the m

Page 43 - 5.4. Memory caching

Performance tuning41• http://www.rabbitmq.com/memory.html• http://www.rabbitmq.com/configure.htmlTo check the current theshold setting, enter the foll

Page 44

42Chapter 6. Upgrading Version 3.2.1Zenoss fully supports upgrading Zenoss Enterprise 3.2.1 installations to Resource Manager version 4.2.5. However,t

Page 45 - 5.7.2. Message compression

Zenoss Service Dynamics Re-source Manager Installationv8.8. Performance tuning ...

Page 46 - 5.7.4. Queue expiration

43Chapter 7. Upgrading Version 4.1.1This chapter provides instructions for upgrading Resource Manager version 4.1.1 installations to version 4.2.5. Se

Page 47

Upgrading Version 4.1.1442. Stop Resource Manager daemons on collector hosts.ssh zenoss@remote-collector-hostzenoss stopOccasionally, the stop command

Page 48

Upgrading Version 4.1.145zenpack --list | grep DistributedPingCorrelationc. Remove the ZenPack, if installed.zenpack --remove=ZenPacks.zenoss.Distribu

Page 49

Upgrading Version 4.1.146rpm -Uvh http://deps.zenoss.com/yum/zenossdeps-4.2.x-1.el5.noarch.rpm10.Clean up yum caches.yum clean all11.If either of the

Page 50

Upgrading Version 4.1.147If you are using a remote Zenoss DataStore host, enter the following command:chkconfig zends off7.3.1. Upgrading a remote Zen

Page 51 - 7.2. Preparing to upgrade

Upgrading Version 4.1.1487.5. Post-installation stepsPerform these steps on the Resource Manager master host.1. Log in to the Resource Manager master

Page 52

Upgrading Version 4.1.149• The ZenUp RPM file.• The "pristine" file for Resource Manager 4.2.5.• The most recent RPS (.zup) file.Contact you

Page 53

Upgrading Version 4.1.150• ZenPacks.zenoss.ActiveDirectory• ZenPacks.zenoss.IISMonitor• ZenPacks.zenoss.MSExchange• ZenPacks.zenoss.MSSQLServer• ZenPa

Page 54

Upgrading Version 4.1.1511. Log in as zenoss, and stop all daemons.zenoss stopOccasionally, the stop command does not terminate all of the Resource Ma

Page 55 - 7.5. Post-installation steps

Upgrading Version 4.1.1522. Upgrade Java.a. Download the self-installing RPM of Oracle Java SE Runtime Environment 6u45 from the Java SE 6 Downloadspa

Page 56 - 7.7. Migrating data

viPrefaceZenoss Service Dynamics Resource Manager Installation provides detailed information and procedures you will useto install and upgrade Resourc

Page 57

Upgrading Version 4.1.153rm -f $ZENHOME/etc/zredis.conf4. Switch user root, or to a user with root privileges.su -5. Upgrade Java.a. Download the self

Page 58 - 7.11. Upgrading remote hubs

54Chapter 8. Upgrading Version 4.2.3 or4.2.4, ZenUp in useThis chapter provides Resource Manager upgrade instructions for installations that match the

Page 59

Upgrading Version 4.2.3or 4.2.4, ZenUp in use55Occasionally, the stop command does not terminate all of the Resource Manager daemons. To check, enter

Page 60 - 7.13. Performance tuning

Upgrading Version 4.2.3or 4.2.4, ZenUp in use561. Log in to the Resource Manager master host as zenoss.2. Create a backup.zenbackup3. Create a copy of

Page 61 - 4.2.4, ZenUp in use

Upgrading Version 4.2.3or 4.2.4, ZenUp in use57master host needs upgraded client libraries, both to communicate with Zenoss DataStore, and to copy the

Page 62 - 8.2. Preparing to upgrade

Upgrading Version 4.2.3or 4.2.4, ZenUp in use585. Start Zenoss DataStore.service zends start8.4. Upgrading Resource ManagerPerform the following proce

Page 63

Upgrading Version 4.2.3or 4.2.4, ZenUp in use595. Switch user to root, or to a user with superuser privileges.su -6. Configure Resource Manager to sta

Page 64

Upgrading Version 4.2.3or 4.2.4, ZenUp in use60• The current RPS (.zup) file.Contact your Zenoss representative for login credentials.2. Log in as use

Page 65

Upgrading Version 4.2.3or 4.2.4, ZenUp in use613. Install the RPS.zenup install zenoss_resmgr-version-SPXXX.zupNoteThe zenup command works for a while

Page 66

Upgrading Version 4.2.3or 4.2.4, ZenUp in use62NoteReview the current port requirements in Appendix B, "Port Requirements", to determine whe

Page 67

PrefaceviiTitle Description Zenoss Service Dynamics Service Impact Installation andAdministrationProvides conceptual and procedural information to hel

Page 68 - 8.6. Upgrading remote hubs

Upgrading Version 4.2.3or 4.2.4, ZenUp in use631. Log in to the collector host as zenoss.2. Delete the RRDtool files of a misnamed collector.find $ZEN

Page 69

64Chapter 9. Upgrading Version 4.2.3 or4.2.4, ZenUp not in useThis chapter provides Resource Manager upgrade instructions for installations that match

Page 70 - 8.8. Performance tuning

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use65pgrep -fl ${ZENHOME}If the pgrep command returns a result, kill the processes.pkill -f ${ZENHOME}9.

Page 71 - 4.2.4, ZenUp not in use

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use662. Create a backup.zenbackup3. Delete the RRDtool files of a misnamed collector.find $ZENHOME -name

Page 72 - 9.2. Preparing to upgrade

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use67NoteThe files are different for versions 4.2.3 and 4.2.4, and are located in different places on th

Page 73

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use685. Make the script executable.chmod +x /path-to-script/zencheckrps6. Start the script./path-to-scri

Page 74

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use69NoteThe Zenoss DataStore upgrade installer preserves Resource Manager data, plus any customizations

Page 75

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use70service zends start9.5. Upgrading Resource ManagerPerform the following procedure on the Resource M

Page 76

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use715. Upgrade any ZenPacks developed by you, the Zenoss community, or Zenoss Professional Services. Fo

Page 77

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use72Perform this procedure if the following statements are true.• You have not previously monitored Win

Page 78

1Chapter 1. Installation considerationsThis chapter describes the Resource Manager deployment architecture considerations.1.1. Installation packagesRe

Page 79

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use733. Install the RPS.zenup install --force zenoss_resmgr-version-SPXXX.zupNoteThe zenup command works

Page 80 - 9.7. Upgrading remote hubs

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use745. Clean up yum caches.yum clean all6. Install Nagios plugins.yum -y install nagios-plugins nagios-

Page 81

Upgrading Version 4.2.3or 4.2.4, ZenUp not in use756. Update Memcached, Net-SNMP, and RRDtool, and install Redis.yum -y install memcached net-snmp net

Page 82 - 9.9. Performance tuning

76Appendix A. Upgrading RabbitMQServerThis appendix describes how to upgrade RabbitMQ Server without upgrading Resource Manager. Follow these pro-cedu

Page 83 - A.2. Stop Resource Manager

Upgrading RabbitMQ Server77exit3. Log in to each hub host, and stop Resource Manager daemons.ssh root@remote-hub-hostservice zenoss stopexit4. Log in

Page 84 - A.3. Stop RabbitMQ Server

Upgrading RabbitMQ Server78A.4. Upgrade RabbitMQ Server1. If you are upgrading a RabbitMQ Server instance on a Resource Manager host, use the Zenoss d

Page 85 - A.5. Start Resource Manager

Upgrading RabbitMQ Server792. Start Resource Manager.zenoss start3. Start remote hubs, if any.ssh zenoss@remote-hubzenoss start4. Start remote collect

Page 86 - 3. Start remote hubs, if any

Appendix B. Port requirementsThis appendix details the network ports and protocols that Resource Manager needs to function properly. The exact requir

Page 87 - This portlet can be removed

Port requirementsPort Requirements for Prerequisite SoftwareResource Manager depends on various third-party software packages, some of which include d

Page 88 - /var/lib/zends/zends.sock

Port requirementsEvent Server DaemonsThe daemons listed below are required. They are normally run on the master host. As noted below, some of them can

Page 89 - Event Server Daemons

Installation considerations21000 devices x 100 data points per device = 100,000 data points100000 / 300 seconds / 250 dps = 1.333 collectorsIn this sc

Page 90 - Collector Daemons

Port requirementsHub DaemonsThe zenhub daemon must run on every hub host.Hub DaemonsDaemon Port Proto Dir Source / Destination Noteszenhub 8081180908

Page 91

Port requirementsCollector DaemonsDaemon Port Proto Dir Source / Destination Noteszenpython * TCP OUT monitored devices*See note 5.zenrender† 8091 TC

Page 92

Port requirementsResource Manager Collectors by Device ClassThis table details the collector daemons invoked by default on devices in each device clas

Page 93

Port requirementsCollector to Monitored Devices by Device ClassDevice Class Port Proto Daemon / Notes/Devices/Network/Cisco/IDS 443 (HTTPS) TCP zenco

Page 94

Port requirementsCollector to Monitored Devices by Device ClassDevice Class Port Proto Daemon / Notes/Devices/Server/SSH† — —/Devices/Server/SSH/AIX

Page 95 - 389 (LDAP)

Port requirementsAdditional Monitoring Port UsageAdditional monitoring functionality can be added to a device or device class by binding the appropria

Commentaires sur ces manuels

Pas de commentaire