Install Secondary Hubs

Most deployments have at least one additional hub. For load balancing, enterprise deployments can have several to hundreds. Secondary hubs are typically dedicated servers. They are used:
uim835
Most deployments have at least one additional hub. For load balancing, enterprise deployments can have several to hundreds. Secondary hubs are typically dedicated servers. They are used:
  • To provide failover capability if the primary hub is unavailable.
  • In enterprise deployments, to host services and management consoles, such as Unified Management Portal (UMP) and the Alarm Server (NAS).
  • For data collection and dispersion. In an enterprise deployment, tunnels and queues connect secondary hubs to form a hierarchy that securely transports monitoring data to the primary hub.
Set Up Secondary Hub Servers
Follow these steps on each server that will host a secondary hub:
  1. Install a supported version of Windows, Linux or Solaris.
    For supported versions, see the Compatibility Support Matrix.
  2. Disable disk compression, if needed.
  3. On Linux systems:
    • Install the standard C++ library.
    • Ensure the /etc/hosts file maps
      127.0.0.1
      to
      localhost
      , and its own IP address to its hostname.
  4. Restart the server.
Setup is complete.
After installing a secondary hub, complete the following:
  • Set up queues connecting the secondary hubs to the primary hub to enable communication on the message bus.
  • Set up tunnels between hubs separated by firewalls. This ensures secure communication.
  • If you are using Admin Console, you must also install the ppm probe on your secondary hubs. If you do not have ppm installed on your secondary hubs, the Admin Console probe configuration GUIs will be unavailable.
Because of the time required for hub authentication and synchronization, it may take several minutes for a new robot to show up under the hub in Infrastructure Manager or Admin Console. Keep in mind that ports 48000 to 48002 need to be open between hubs.