
Port requirements
Port Requirements for Prerequisite Software
Resource Manager depends on various third-party software packages, some of which include daemons that must be
accessible either locally, over the network, or both. By default, all Resource Manager software and its dependencies are
installed initially on the Resource Manager master host. For increased performance, some of the third-party daemons
can be run on a separate, dedicated (physical or virtual) server, noted as “off-host” in the table below.
Port Requirements for Prerequisite Software
Daemon Port Proto Dir Source / Destination Notes
(bind) 53 (DNS) UDP OUT DNS Server(s)
Very strongly recommended.
ntpd 123 (NTP) UDP IN/OUT Zenoss servers,
network time servers
Strongly recommended for Zenoss
instances with more than one
server. Should be run on all Zenoss
hosts.
memcached 11211 (memcache) TCP IN zenactiond,
zeneventserver,
zenhub, zenjobs, zope
Required on the master server and
every remote hub.
rabbitmq 5672 (AMQP) TCP IN zenactiond,
zencatalogservice,
zeneventd,
zeneventserver,
zenhub, zenjobs, zope
One RabbitMQ instance (or
cluster) is required for each Zenoss
instance. Can be run off-host.
sshd 22 (SSH) TCP IN ssh client, Zenoss
master server
Inbound access is required on all
Zenoss servers.
(various) 22 (SSH) TCP OUT Zenoss master server
Outbound SSH access is required
on the master host.
zends (mysql)
/var/lib/zends/zends.sock
13306
unix
TCP
—
IN
zenactiond,
zencatalogservice,
zeneventd,
zeneventserver,
zenhub, zenjobs, zope
One instance is required. The
object database and event
database can be located on
separated instances. Local
connections use the unix socket.
Remote connections
conventionally go to TCP port
13306. Can be run off-host.
B-2
Comentarios a estos manuales