VMware PACKAGE MANAGER 1.1 Uživatelský manuál Strana 91

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 95
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 90
Port requirements
Collector Daemons
Daemon Port Proto Dir Source / Destination Notes
zenpython * TCP OUT monitored devices
*See note 5.
zenrender† 8091 TCP IN nginx
zenrrdcached†
$ZENHOME/var/rrdcached.sock
unix
zenstatus * TCP OUT monitored devices
*zenstatus attempts to
open a TCP connection to
the port defined for each
monitored IP Service on
each device where the
service is monitored.
zensyslog 514 (Syslog) UDP IN monitored devices
zentune 13306 TCP OUT zends
zentrap 162 (SNMPTrap) UDP IN monitored devices
zenucsevents 80 (HTTP) TCP OUT monitored devices
zenvcloud 443 (HTTPS) TCP OUT monitored devices
zenvmwareevents
443 (HTTPS) or 80 (HTTP)
TCP OUT monitored devices
zenvmwaremodeler
443 (HTTPS) or 80 (HTTP)
TCP OUT monitored devices
zenvmwareperf
443 (HTTPS) or 80 (HTTP)
TCP OUT monitored devices
zenvsphere
443 (HTTPS) or 80 (HTTP)
TCP OUT monitored devices
zenwebtx 80 (HTTP) TCP OUT monitored devices
zenwin 135 (EPMAP)
*
TCP
TCP
OUT
IN/OUT
monitored devices
monitored devices
*See note 2.
zenwinperf 445 (MS-DS) TCP OUT monitored devices
zredis 16379 TCP IN Zenoss master server
and collector servers
Required on the master
host and every remote
collector.
1. zencommand: In addition to running commands on monitored devices, the zencommand daemon is also used to
run commands (for example, Nagios plugins) on the collector. Those commands often then connect to the
monitored device. See the Additional Monitoring Port Usage section below for more information.
2. zeneventlog, zenwin: These daemons use Windows RPC to communicate with the WMI service on the remote
device. By default, Windows RPC allocates a dynamic port, in addition to port 135, in the range of 49152–65535
or 1025–5000 depending on the version of Windows. See the Service overview and network port requirements
for Windows Microsoft support article for more information.
3. zeneventlog: This daemon will attempt to monitor the Windows event logs of any devices where the
zWmiMonitorIgnore configuration property is set to False (unchecked) and the zWinEventlog configuration
property is set to True (checked), which is the default configuration on the /Server/Windows device class.
4. zenjmx: The zenjmx daemon provides monitoring of remote Java® applications using Java Monitoring Extensions
(JMX) using either RMI (Remote Method Invocation) or JMXMP (JMX Messaging Protocol). Device class specific
configuration properties are used to define the remote port and authentication credentials.
Note that the RMI protocol requires a second connection that, by default, goes to a dynamically allocated
(essentially random) port number. See the Java 2 Platform Standard Edition chapter in Zenoss Service Dynamics
Extended Monitoring for more information.
5. zenpython: The zenpython daemon runs Python monitoring code supplied by other ZenPacks, such as
Microsoft.Windows. The ports zenpython requires are defined by the ZenPacks that call it.
B-5
Zobrazit stránku 90
1 2 ... 86 87 88 89 90 91 92 93 94 95

Komentáře k této Příručce

Žádné komentáře