Remote/Distributed Servers

What does this do?

A Remote Server runs Monitors and reports their status back to one or more Master Servers. The Distributed Remote Servers option enables the Reveille Server to run in multiple geographic locations, running the same or different sets of Monitors at each location.

Remote Servers are configured using the Reveille Reveille Admin console before they can communicate to one or more Master Servers, and are administered from the Distributed Remote Servers page on the Reveille Web interface. 

The Master Server is a full Reveille Server used to view the status and reports for all Monitors from the Remote Servers. This server houses a database that contains data from Remote Monitors for all the Remote Servers. This data is kept current through automated synchronizations between the Remote Servers and Master Server using encrypted Web services connections.

For additional availability, a Secondary Master Server can be set up installing another Master Server to point to the same database. The Remote Server tries the Secondary Master Server if the Primary Server is not available.

When would I use this?

A Distributed Server enables the Reveille Server to operate at multiple geographic locations, running the same or different sets of Monitors at each location. Reveille Remote Servers run local Monitors, and then send monitoring results over encrypted web services connections. Optional: Local alerts can be sent to one or more Reveille Master Servers.

A Reveille Remote Monitor’s status and reports can be viewed as if the Monitors were located and running on the Reveille Master Server.

Where do I see a change after using this?

After distributed servers are defined and enabled, users will see the remote servers listed in the System Dashboards section of the Reveille Web interface.

How do I use this?

For an overview of server set-up and usage, see Servers:

• Use the Reveille Admin console to set up and configure distributed servers.
• Use the Reveille Web interface (on the Master Server) to manage Remote Servers and for Enabling and Disabling a Remote Server. This causes the Master Server to refuse the connection from the Remote Server.