600-SERIES HARDWARE MANUAL
Event Server Overview
Chapter-Page
3-1
3
Communication /Event Server Overview
This chapter covers the Galaxy Communication and Event Server and its role in the Hardware
system. Use this chapter for troubleshooting or to understand how the Event Server works.
3.1
Description of the Communication Server
Core GCS Services and usually the System Galaxy software run on the Communication Server.
GCS Communication Service [port 4000]
(aka Comm service) is the hub of the GCS Services
Handles transmission of events to and from the Database (via DBWriter), SG Monitoring Software
(via Gateway) and the access control panels (via Event service).
GCS DBWriter Service [port 4001]
logs the events to the Database from the Communication Service.
If the DBWriter looses connection with the SQL Server, it will induce a shutdown. Any DBWriter
shutdown (whether induced by manual or automated means) will spawn a shutdown of the Comm
Service. This protects against lost / dropped events and ensures that the access control panel
will retain the events in its buffer until IP connectivity is restored.
Note that Galaxy hardware does not operate in degraded mode if IP connections are interrupted;
this is known as Off-line event buffering. The panel continues to be fully functional and buffers up
to 10,000 events at the CPU. Events are re-transmitted to the database once IP connections are
restored. Off-line events become available in system reports after being retransmitted / logged.
GCS Client Gateway Service [port 4002]
Retrieves the SysID for the System Galaxy software running on Clients and Servers
Handles sending SG operator commands, converts incoming events into man-readable messages;
In SG 10 it also buffers incoming SG Alarms, which was done at the software level in SG 9.
GCS Event Service [port 4003]
The 600 controller initiates the connection to the Event service
Transmits events to the Communication Service.
This service must run local to the time-zone of the panel; more than one instance of the Event
service can run if needed.
Cross-panel communications rely on the Event server to be running for real-time execution.
IMPORTANT: Galaxy Event Servers must use a static IP Address
in order for the
controllers to make connections to the GCS Event Service.
