VMware PACKAGE MANAGER 1.1 Manual de usuario

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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)

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

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

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

iiiPreface ...

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

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

Adding a collector25chkconfig --level 2345 zenoss on

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

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

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

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

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

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

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&

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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-

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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