Firewall Settings
G-SIM uses TCP and UDP ports for its connections. These ports must be enabled in the firewall settings (firewall rule). The table shows the ports used for TCP and UDP:
TCP Ports |
|
TCP 8090 |
G-SIM Server <-> Operator Console/ ManCon/ ReCon G-SIM Control Server <-> G-SIM Controlled Client Servers G-SIM Server <-> Agent and Health Agent |
TCP 8091 |
G-SIM Cluster Servers Sync (G-SIM Server <-> G-SIM Server) |
TCP 8092 |
Data Access Server Port used by DAS for on-demand requests for alarm data, process data, and audit data, as well as for communication with other G-SIM servers in the global environment to enforce synchronization when a user changes. |
TCP 8098 |
G-SIM Server SAM Proxy |
TCP 8099 |
Agent and Health Agent <-> G-SIM Server |
TCP 9092 |
The G-SIM server Kafka client communicates with other Kafka servers via the IP address of the G-SIM server, using this port for communication. |
TCP 13180 |
Export Service |
TCP 13181 |
Map Tiles Service |
TCP 13210 |
App Instance Manager Service |
UDP Ports |
|
UDP 8090 |
Port used by servers to exchange status messages with each other. |
UDP 8099 |
Agent and Health Agent Cluster |
Comments:
-
Operator Console, Management Console and Agent use ICMP for “pinging”.
-
GeViSoft Proxy connections run only locally via NamedPipes (URL
net.pipe://localhost/GSIM
), so that no firewall rules need to be created. -
G-Core, GeViScope, Pelco and GeViSoft use standard ports for outgoing connections to the servers. The same ports are also used for connections via SDK.
-
G-Core SAM connections from third-party systems are handled via SDK.
-
If an SQL server runs on a remote machine, then the SQL TCP ports also need to be enabled.