RC-E User Manual
Installation and Removal
Port 25 (inbound and outbound):
Used by
recording servers
to listen for SMTP information. Also, some devices
use SMTP (e-mail) for sending event messages and /or for sending images to the surveillance system server via e-
mail. SMTP (Simple Mail Transfer Protocol) is a standard for sending e-mail messages between servers.
Port 80 (inbound and outbound):
While not directly used by RC-E , but by
management servers
, port 80 is
typically used by the IIS (Internet Information Services) Default Web Site for running the RC-E Management Server
service.
Port 554 (inbound and outbound):
Used by
recording servers
for RTSP traffic in connection with H.264 video
streaming.
Port 1024 and above (outbound only (except ports listed in the following)):
Used by
recording servers
for
HTTP traffic between cameras and servers.
Port 5210 (inbound and outbound):
Used for communication between
recording servers
and
failover servers
when databases are merged after a failover server has been running.
Port 5432 (inbound and outbound):
Used by
recording servers
to listen for TCP information; some devices use
TCP for sending event messages.
Port 7563 (inbound and outbound):
Used by
recording servers
and
Ocularis Client
for handling PTZ camera
control commands and for communicating.
Port 8080 (inbound and outbound)
:Used for internal system communication
.
Port 8844 (inbound and outbound):
Used for communication between
failover servers
.
Port 9993 (inbound and outbound):
Used for communication between
recording servers
and
management
servers
.
Port 11000 (inbound and outbound):
Used by
failover servers
for polling (i.e. regularly checking) the state of
recording servers
.
Port 65101(inbound and outbound):
Used by
recording servers
for communication between recording servers and
drivers (internally, used for example when SMTP events are received).
Any other port numbers you may have selected to use.
Examples: If you have changed the IIS Default Web Site
port from its default port number (80) to another port number, or if you have integrated RC-C servers into your RC-E
system, in which case a port must be allocated for use by RC-C's Image Server service.
Multiple Management Servers (Clustering)
The RC-E management server can be installed on multiple servers within a cluster of servers. This ensures that RC-E
has very little down-time: if a server in the cluster fails, another server in the cluster will automatically take over the
failed server's job running the RC-E management server. The automatic process of switching over the RC-E server
service to run on another server in the cluster only takes a very short time (up to 30 seconds).
Note that the allowed number of failovers is limited to two within a six hour period. If exceeded, Management Server
services are not automatically started by the clustering service. The number of allowed failovers can be changed to
better fit your needs. See Microsoft's homepage http://technet.microsoft.com/en-
us/library/cc787861%28WS.10%29.aspx (see http://technet.microsoft.com/en-us/library/cc787861(WS.10).aspx -
http://technet.microsoft.com/en-us/library/cc787861(WS.10).aspx) for details on how to do this.
Is clustering the same as federated architecture?
No, clustering is not the same as
federated architecture
(see
"
OnSSI Federated Architecture Overview
" on page 173). Clustering is a method to obtain failover support for a
management server on a site. With clustering, it is only possible to have one active management server per
surveillance setup, but other management servers may be set up to take over in case of failure. On the other hand,
federated architecture, is a method to combine multiple independent corporate sites into one large setup, offering
flexibility and unlimited possibilities.
On-Net Surveillance Systems, Inc.
24
