VMware PACKAGE MANAGER 1.1 Manuel d'utilisateur Page 48

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 69
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 47
Installing Collectors and Hubs
41
Installing for RHEL 5 or CentOS 5
Installing for RHEL 6 or CentOS 6
5.2.2. Deploying Remote Hubs
The following sections provide detailed information needed to deploy hubs:
Requirements
Limitations
Configuring Zenoss DataStore
Prerequisite Tasks
Deployment
5.2.2.1. Requirements
Hub deployments must meet these requirements:
The Resource Manager server host name must be a resolvable, fully qualified domain name or IP address.
Any server hosting a remote hub must have the Zenoss DataStore installed (but not running). The Zenoss
DataStore is needed for a client library that allows MySQL connections.
Remote hubs need to communicate on these default Resource Manager ports:
Port 13306 - Zenoss DataStore
Port 8084 - Resource Manager events system
Port 5672 - Resource Manager queuing system
You must update all hubs after you:
Update your version of Resource Manager
Install patches
Install, update, or remove ZenPacks
5.2.2.2. Limitations
The system is not compatible with Security-Enhanced Linux (SELinux) in enforcing mode. You must disable
enforcing mode for all platforms running the Resource Manager daemons (Resource Manager master, remote
hubs, and remote collectors).
To disable enforcing mode:
1. Edit the /etc/selinux/config file.
2. Set the following line:
SELINUX=disabled
Note
You also can disable enforcing mode temporarily (avoiding the need to reboot) with the command:
echo 0 > /selinux/enforce
For more information about SELinux, browse to http://en.wikipedia.org/wiki/SELinux, or to the SELinux home
page at http://www.nsa.gov/research/selinux/index.shtml.
5.2.2.3. Configuring Zenoss DataStore for Remote Hubs
Hubs on remote servers need access to the Zenoss DataStore. By default this is set to localhost, but will not
work for remote hubs. Distributed collector attempts to set this field to the fully qualified domain name of the
Resource Manager server when it is installed. If remote hubs appear to be having trouble connecting to the
Vue de la page 47
1 2 ... 43 44 45 46 47 48 49 50 51 52 53 ... 68 69

Commentaires sur ces manuels

Pas de commentaire