Note that Novell Sentinel Log Manager appliance uses the following ports for communication, and some of them are opened on the firewall:
Table 4-1 Network Ports Used by Sentinel Log Manager
Ports |
Description |
---|---|
TCP 1289 |
Used for Novell Audit connections. |
TCP 289 |
Forwarded to 1289 for Novell Audit connections. |
TCP 22 |
Used for secure shell access to the Sentinel Log Manager appliance. |
UDP 1514 |
Used for syslog messages. |
UDP 514 |
Forwarded to 1514 for syslog messages. |
TCP 8080 |
Used for HTTP communication. |
TCP 80 |
Forwarded to 8080 for the Sentinel Log Manager Web Server for HTTP communication. |
TCP 8443 |
Used for HTTPS communication. |
TCP 1443 |
Used for SSL encrypted syslog messages. |
TCP 443 |
Forwarded to 8443 for the Sentinel Log Manager Web server for HTTPS communication. Also used by the Sentinel Log Manager Appliance for the update service. |
TCP 61616 |
Used for communication between Collector Managers and the server. |
TCP 10013 |
Used by the Event Source Management user interface SSL Proxy. |
TCP 54984 |
Used by the Sentinel Log Manager appliance Management Console (WebYaST). |
TCP 1468 |
Used for syslog messages. |
Table 4-2 Ports Used for Communication Locally
Ports |
Description |
---|---|
TCP 61617 |
Used for internal communication between the Web server and the server. |
TCP 5556 |
Used on the loop back interface for internal communication, with the internal_gateway_server and internal_gateway. It is used for communication between the agent engine and the Collector Manager. |
TCP 5432 |
Used for the PostgreSQL database. You do not need to open this port by default. However, if you are developing reports by using the Sentinel SDK, then you must open this port. For more information, see Sentinel Plug-in SDK Web site. |
Two additional randomly selected TCP ports |
Used for internal communication between the agent engine and the Collector Manager. |
TCP 8005 |
Used for internal communication with Tomcat processes. |
TCP 32000 |
Used for internal communication between the agent engine and the Collector Manager. |