Configuring Failover in OpManager

• How does Failover work?
• What are the prerequisites?
• How to configure failover instance in OpManager?
• Encrypted File Transfer (Windows only)

How does Failover work?

The primary server updates a value called heartbeat in the database. The heartbeat value is a counter that is incremented by the primary server at a specific frequency of time. The secondary server monitors the heartbeat value to check if it is being updated in the specified time interval. When the primary server goes down, it will not be able to update the heartbeat  value in the database. If the heartbeat value in the database is not updated for the last 60 seconds, the primary server is considered to have gone down and the secondary monitoring instance takes over. This secondary server will continue monitoring the network as long as it is up. Meanwhile, if the primary server is up (recovered and restarted), it will take the standby mode and let the secondary server continue monitoring.

The information between the primary and secondary instances are synced periodically, thus ensuring that you don't miss critical monitoring data ( such as device status, traps, syslog messages etc., ) when your primary OpManager instance goes down.

What are the prerequisites?

• Apply the failover add-on: Apply the Failover - Hot Standby Engine  add-on in your primary instance. You can purchase the add-on for Professional Edition from here and for OpManager Plus from here. ( Note: Failover is supported in both MSSQL, and Remote PGSQL setups. To configure failover for remote PGSQL setup, click here.)
• Have the database in a separate server: Ensure that the database for your OpManager installation is setup in a separate server and not the same server in which the primary or secondary OpManager instance is installed (MSSQL or remote PGSQL setup).
• Create a shared folder in a separate server: Some data in OpManager are stored in files which are present in the local directory. When failover is configured, instead of a local directory, these files are stored in a shared folder that is accessible by both primary and secondary servers . This ensures that there is no data loss when the secondary server takes over the monitoring process.
  Create a folder in a separate server  and share it with both the primary and secondary servers. Ensure that both primary and secondary servers have access to the shared folder with write permission.
  ( Note: The server in which the folder is created should be in the same domain in which your primary and secondary servers are configured. Also, the server in which the folder is created should not be the same server in which the primary or secondary instance is configured). Learn how to share a folder with both primary and secondary instances in Windows and Linux.
• Select a Connection type: The connection types refer to the methods by which users can establish communication with servers in a network environment. Depending on their needs for flexibility, redundancy, or specific configurations, they can choose between three connection types. Click here for more information.
• Hardware and software requirements
  • The same version of OpManager should be installed in both servers.
  • Both primary and secondary OpManager services should have the same port and protocol ( http / https ).
  • Both primary and secondary servers should have the same time and time zone.
  • Both primary and secondary servers should have the same hardware configurations.
• Network requirements
  • Both primary and secondary servers should have a static IP address.
  • The primary server and secondary server should be able to resolve each other's host name and IP address.
  • Both the servers should have high connectivity and bandwidth.
  • The primary, secondary and the server in which the shared folder is created should all be in the same domain.
  • The Syslogs, SNMP traps and Flows are forwarded to the virtual IP address.

How to configure failover instance in OpManager?

In your primary instance, go to  Settings -> General Settings  -> Failover Details and enter the following details:

• Connection Type: Users have the flexibility to choose between different connection types: Virtual IP, Virtual hostname, or none. The primary and secondary servers can either reside on the same subnet or different subnets.
• Virtual IP: A Virtual IP (VIP) address is an IP address shared by both primary and secondary servers on the same subnet. When one server goes down, the other server takes over the VIP address and responds to requests sent to the VIP. The VIP and both servers must be part of the same subnet.



• The VIP option is available only when both primary and secondary servers are on the same subnet.
• If the servers are in different subnets, you must use a virtual hostname instead of a VIP.
• The virtual IP should be static and in IPv4 format.
• Subnet mask (optional): The subnet mask is used to bind the Virtual IP. By default, it is typically set to 255.255.255.0. If you need to modify the subnet value after configuring failover, follow these steps.
• Virtual hostname: A Virtual hostname is shared by both the primary and secondary servers. Only the active server responds to requests sent to the virtual hostname. This setup allows you to configure failover servers either on a single subnet or across two different subnets.

  

  • DNS Type: For virtual hostname configuration, you need to choose one of the supported DNS types by OpManager, i.e., either Microsoft or BIND DNS Servers.
  • Microsoft: A DNS server type
    • User name/Password: Credentials for the Microsoft DNS server

  Note: For Microsoft DNS, make sure required the RSAT packages are installed in the Primary & Secondary servers.

  • RSAT can be installed on a Windows client machine. For Windows 10 and above, you can install it via the Optional Features option.
  • Go to Settings -> Apps -> Optional features -> Add a feature.
  • Search for "RSAT" and install the necessary tools such as RSAT: DNS Server Tools.
  • Bind: The DNS Server type (Applicable for linux)
    • TSIG:When interacting with BIND DNS, transaction signatures (TSIG) are required instead of administrator credentials. Configure your BIND DNS name server in the DNS zone to use the TSIG key when configuring failover. The key must use the HMAC_SHA256 message authentication code with a key size between 1 and 512 bytes. Use the dnssec-keygen utility from your BIND installation to generate a new key. If you haven't used TSIG with BIND DNS before, update the BIND configuration file to allow DNS updates signed by the new TSIG.

    

    • TSIG Shared Secret Key Name: The name given to the key in the configuration file.
    • TSIG Shared Key Value: The value from the .private file generated when creating the TSIG secret. Use the string after Key: in this file.
    • DNS Zone: A DNS zone is where you store name information for the domains you manage. You can divide your network into multiple subordinate DNS zones for better management, organization, or performance. Both the Primary and Secondary DNS servers must be managed within the same DNS zone, even if it spans multiple subnets.

  Note: When a failover uses a virtual hostname, issues may arise where the failover does not appear to work due to caching problems. The client DNS cache may take up to one minute to redirect traffic to the active server.
  
  However, since browser DNS caches often do not respect the DNS Time to Live (TTL) value, the retention time can vary between browsers, ranging from 60 seconds to 24 hours. To ensure successful redirection to the new active server, it may be necessary to flush the browser's DNS cache.

  • None: In scenarios where neither Virtual IP nor Virtual hostname is preferred or required, users have the option to establish connections using individual IP addresses and hostnames of the Primary and Secondary servers.

    

    However, consider the following if you are choosing the None option:

    • Identifying the Active Server: Users must independently determine the active server to access the client application.
    • Redirection of Traffic: End devices need to be configured to redirect traffic to the Primary server when it is active; when the Primary server fails, traffic must be redirected to the Secondary server.