
Appendix B. Port requirements
This appendix details the network ports and protocols that Resource Manager needs to function properly. The exact
requirements for a specific installation depend on how its components are distributed and/or replicated from the master
host, and what classes of devices are being monitored. In most cases, the port numbers used by Resource Manager
daemons are set by their configuration file(s) in $ZENHOME/etc. Some monitoring templates use a configuration
property to specify the target port on monitored devices.
In the default, single-server installation, all communication among components is through the loopback network (lo) and
local (unix) sockets.
This appendix describes the ports used by a standard Resource Management installation with the Windows Monitoring
ZenPack installed. For ZenPacks not included in the standard installation, refer to Zenoss Service Dynamics Extended
Monitoring, or the individual ZenPack’s documentation.
Browser Connections to the Zenoss Web Server
By default, the Resource Manager web server load balancer (nginx) listens on TCP port 8080, but can be configured to
accept requests on the default HTTP port (80), the HTTPS port (443), or an arbitrary port.
Zenoss Administrator’s / Operator’s Browser to Zenoss UI
Description Port Proto Direction Source / Destination Notes
Web UI 8080* TCP OUT nginx
*Port number is configurable.
Google Maps portlet
(Dashboard)
80 (HTTP) TCP OUT callhome.zenoss.com,
Various Google sites
This portlet can be removed.
Default site portlet
(Dashboard)
80 (HTPP) TCP OUT www2.zenoss.com
This portlet can be removed
or reconfigured to access
another website.
Comentarios a estos manuales