
Appendix C: Clustered Deployment
110
RMS Enterprise - Installation Guide
Network infrastructure requirements
In a clustered deployment, the nodes must find each other using multicast UDP communication and need to all
be on the same subnet.
By default, RMS uses the following multicast ports for a clustered deployment: 45564, 45588, and 46655
Communication between the nodes provides a variety of functions:
1. Configuration changes made via the Flex UI.
For example, when a configuration change within the Flex UI is made (e.g. SMTP Server), that change is
persisted to the database and propagated to the other servers.
2. Search index write operations: when locations are created and client gateways and their assets are
registered with the server, this information must be indexed on the shared file storage.
Only one server can write to the index at a time, so RMS employs a dynamic master-slave approach:
The first server to start in a cluster becomes the master, and subsequent servers become slaves.
The slaves send their index updates to the master who will perform the index writes for them.
If the master node goes down, the second server that was started becomes the new master and
performs the index writes.
3. Search index read operations (via SMB network file storage).
4. A distributed data grid (between the nodes) stores the last time each REST-based client gateway
communicated with the server. This allows RMS to determine when a client has gone off-line.
5. Licensing checks. Each server must communicate with the Sentinel license service approximately every
10 minutes.
If the Sentinel license service goes down, RMS will continue to operate for a 24 hour grace period.
Bandwidth costs
Many factors influence the bandwidth costs, including the number of servers in the cluster as well as the
number of locations, client gateways, and assets.
Comentários a estes Manuais