Configuring a hub on your secondary server - Genetec™ Intrusion Protocol 5.0.0

Genetec™ Intrusion Protocol Extension Guide 5.0.0

Applies to
Genetec™ Intrusion Protocol 5.0.0
Last updated
2022-04-14
Content type
Guides > Plugin and extension guides
Language
English
Product
Genetec™ Intrusion Protocol
Version
5.0

To make sure your Genetec™ Intrusion Bridge can connect to a secondary server when failover occurs, you must configure a hub on the secondary server.

What you should know

When failover occurs, the Intrusion Manager role moves to its secondary server and the Genetec™ Intrusion Bridge loses its connection with the hub. The Genetec™ Intrusion Bridge then tries to connect to the second hub in its list, which must be the hub located on your secondary server. After the Genetec™ Intrusion Bridge connects to the hub on secondary server, it is connected to the Intrusion Manager role on the secondary server as well.

Configuration page for hubs in the Genetec™ Intrusion Bridge web app

Procedure

  1. Enable a hub on the Genetec™ Intrusion Protocol extension.
  2. Log on to the Genetec™ Intrusion Bridge web app.
  3. Select Hubs from the panel on the left side, and click Add.
  4. Enter the following:
    Server
    The address of the secondary server.
    Port
    The same port used by the hub on the primary server. This is configured in the Hub port field on Intrusion Manager > GIP > Extensions > Hub on the secondary server.
    App key
    Enter an app key for the hub. This is configured in the App key field on Intrusion Manager > Genetec™ Intrusion Protocol > Extensions > Hub on the secondary server.
    Certificate thumbprint
    Leave this field empty so the certificate is assigned automatically when the Genetec™ Intrusion Bridge connects to this hub for the first time.
  5. Click Save.