One Identity Safeguard for Privileged Sessions 6.0.6 - Administration Guide

Redundant heartbeat interfaces

To avoid unnecessary takeovers and to minimize the chance of split-brain situations, you can configure additional heartbeat interfaces in One Identity Safeguard for Privileged Sessions (SPS). These interfaces are used only to detect that the other node is still available, they are not used to synchronize data between the nodes (only heartbeat messages are transferred). For example, if the main HA interface breaks down, or is accidentally unplugged and the nodes can still access each other on the redundant HA interface, no takeover occurs, but no data is synchronized to the secondary node until the main HA link is restored. Similarly, if connection on the redundant heartbeat interface is lost, but the main HA connection is available, no takeover occurs.

If a redundant heartbeat interface is configured, its status is displayed in the Basic Settings > High Availability > Redundant Heartbeat status field, and also in the HA > Redundant field of the System monitor. For a description of each possible status, see Understanding One Identity Safeguard for Privileged Sessions (SPS) cluster statuses.

The redundant heartbeat interface is a virtual interface with a virtual MAC address that uses an existing interface of SPS. The MAC address of the virtual redundant heartbeat interface is displayed as HA MAC. The MAC address of the redundant heartbeat interface is generated in a way that it cannot interfere with the MAC addresses of physical interfaces. Similarly, the HA traffic on the redundant heartbeat interface cannot interfere with any other traffic on the interface used.

If the nodes lose connection on the main HA interface, and after a time the connection is lost on the redundant heartbeat interfaces as well, the secondary node becomes active. However, as the primary node was active for a time when no data synchronization was possible between the nodes, this results in a split-brain situation, which must be resolved before the HA functionality can be restored. For details, see Recovering from a split brain situation.

SPS nodes use UDP port 694 to send each other heartbeat signals.

To configure a redundant heartbeat interface

1. Navigate to Basic Settings > High Availability > Interfaces for Heartbeat.

2. Select the interface you want to use as redundant heartbeat interface (for example Physical interface 1). Using an interface as a redundant heartbeat interface does not affect the original traffic of the interface.

   Figure 103: Basic Settings > High Availability — Configuring redundant heartbeat interfaces

   

3. Enter an IP address into the This node > Interface IP field of the selected interface. Note the following:

   • The two nodes must have different Interface IP.

   • If you do not use next hop monitoring on the redundant interface, you can use any Interface IP (even if otherwise it does not exist on that network).

   • If you use next hop monitoring on the redundant interface, the Interface IP address must be a real IP address that is visible from the other node.

   • If you use next hop monitoring on the redundant interface, the Interface IP must be accessible from the next-hop address, and vice-versa. For details on next hop monitoring, see Next-hop router monitoring.

   Use an IPv4 address.

4. If the two nodes are in a different subnetwork, enter the IP address of the local gateway into the This node > Gateway IP field. The Interface IP address of the node must be accessible from the Gateway IP address.

   Use an IPv4 address.

5. Enter an IP address into the Other node > Interface IP field of the selected interface. Note the following:

   • The two nodes must have different Interface IP.

   • If you do not use next hop monitoring on the redundant interface, you can use any Interface IP (even if otherwise it does not exist on that network).

   • If you use next hop monitoring on the redundant interface, the Interface IP address must be a real IP address that is visible from the other node.

   • If you use next hop monitoring on the redundant interface, the Interface IP must be accessible from the next-hop address, and vice-versa. For details on next hop monitoring, see Next-hop router monitoring.

   Use an IPv4 address.

6. If the two nodes are in a different subnetwork, enter the IP address of the local gateway into the Other node > Gateway IP field. The Interface IP address of the node must be accessible from the Gateway IP address.

   Use an IPv4 address.

7. Repeat the previous steps to add additional redundant heartbeat interfaces if needed.

8. Click .

9. Restart the nodes for the changes to take effect: click Reboot Cluster.

Next-hop router monitoring

By default, HA takeover occurs only if the primary node stops working or becomes unreachable from the secondary node. However, this does not cover the scenario when the primary node becomes unaccessible to the outside world while the secondary node would be still accessible (for example because it is connected to a different router).

To address such situations, you can specify IP addresses (usually next hop routers) to continuously monitor both the primary node and the secondary node by using ICMP echo (ping) messages. One such address can be set up for every interface.

When setting up next hop monitoring, you have to make sure that the primary and secondary nodes can ping the specified address directly. You can either:

• Choose the addresses of the redundant-HA One Identity Safeguard for Privileged Sessions (SPS) interfaces so that they are on the same subnet as the next-hop address

• Configure the next-hop device with an additional IP-address that is on the same subnet as the redundant-HA SPS interfaces facing it

If any of the monitored addresses becomes unreachable from the primary node while being reachable from the secondary node (in other words, more monitored addresses are accessible from the secondary node) then it is assumed that the primary node is unreachable and a forced takeover occurs — even if the primary node is otherwise functional.

Naturally, if the secondary node is not capable of taking over the primary node (for example, because there is data not yet synchronized from the current primary node), no takeover is performed.

To configure next hop monitoring

1. Navigate to Basic Settings > High Availability > Next hop monitoring.

2. Select the interface to use for monitoring its next-hop router.

   Figure 104: Basic Settings > High Availability — Configuring next hop monitoring

   

3. Enter the IP address to monitor from the current primary node (for example, the IP address of the router or the switch connected to the interface) into the This node > Next hop IP field of the selected interface. This IP address must be a real IP address that is visible from the interface, and must be on the same local network segment.

   Use an IPv4 address.

4. Enter the IP address to monitor from the current secondary node (for example the IP address of the router or the switch connected to the interface) into the Other node > Next hop IP field of the selected interface. This IP address must be a real IP address that is visible from the interface, and must be on the same local network segment.

   Use an IPv4 address.

5. Repeat the previous steps to add IP addresses to be monitored from the other interfaces if needed.

6. Click .

   Caution: For the changes to take effect, you have to restart both nodes. To restart both nodes, click Reboot Cluster.

Upgrading One Identity Safeguard for Privileged Sessions (SPS)

One Identity Safeguard for Privileged Sessions (SPS) appliances are preinstalled with a Long Term Support (LTS) release. One Identity recommends that you upgrade to the latest LTS maintenance release as soon as possible. Each LTS release is supported for 3 years after original publication date, and for 1 year after the succeeding LTS release is published (whichever date is later). You are encouraged to upgrade to succeeding LTS releases.

Feature Releases provide additional features which are not yet consolidated to an LTS release. To gain access to these features, you may install a supported Feature Release on the appliance, with the following conditions:

• You cannot roll back to an LTS release from a Feature Release.

• Feature Releases are released and supported in a timeline of 6 months. You have to keep upgrading SPS to the latest Feature Release to ensure that your appliance is supported.

For both LTS and Feature Releases, One Identity regularly incorporates security patches and bugfixes, and issues updated Revisions of the released product. One Identity strongly recommends always installing the latest Revision of the used software Release.

The following sections describe how to keep SPS up to date, and how to install a new license:

• Prerequisites: Upgrade checklist.

• Upgrading a single node: Upgrading One Identity Safeguard for Privileged Sessions (SPS) (single node). To upgrade SPS without using the web interface, see Firmware update using SSH.

• Upgrading a high availability cluster: Upgrading a high availability One Identity Safeguard for Privileged Sessions (SPS) cluster.

• Troubleshooting: Troubleshooting.

• Renewing the SPS license: Updating the SPS license.

• Exporting the configuration of SPS: Exporting the configuration of One Identity Safeguard for Privileged Sessions (SPS).

• Importing the configuration of SPS: Importing the configuration of One Identity Safeguard for Privileged Sessions (SPS).

Upgrade checklist

The following list applies to all configurations:

• You have created a configuration backup of One Identity Safeguard for Privileged Sessions (SPS).

  For detailed instructions, refer to Exporting the configuration of One Identity Safeguard for Privileged Sessions (SPS).

• You have a valid support portal account.

  To download the required firmware file and license, you need a valid support portal account. Note that registration is not automatic, and might require up to two working days to process.

• You have downloaded the latest SPS firmware from the Downloads page.

• You have read the Release Notes of the firmware before updating. The Release Notes might include additional instructions specific to the firmware version.

  The Release Notes are available at the Downloads page.

• You have verified that SPS is in good condition (no issues are displayed on the System Monitor).

• Optional: You have exported core dump files, if necessary for debugging, from Basic Settings > Troubleshooting > Core files. These files are removed during upgrade.

If you have a high availability cluster:

• You have IPMI access to the secondary node. You can find detailed information on using the IPMI interface in the following documents:

  For Safeguard Sessions Appliance 3000 and 3500, see the X9 SMT IPMI User's Guide.

• You have verified on the Basic Settings > High Availability page that the HA status is not degraded.

If you are upgrading SPS in a virtual environment:

• You have created a snapshot of the virtual machine before starting the upgrade process.

• You have configured and enabled console redirection (if the virtual environment allows it).

During the upgrade, SPS displays information about the progress of the upgrade and any possible problems in the following places:

• On the web interface of SPS, at any of the Listening addresses configured at Basic settings > Local Services > Web login (admin and user). (After booting, you are directed to the login screen of SPS.)

  NOTE: If you are upgrading to version 6.0 from version 5.0.x, this feature is enabled after the first boot to version 6.0. So during the upgrade to version 6.0, you will not be able to see any upgrade logs on the web interface.

• On the console, which you can monitor with IPMI (ILOM) or console access.

The information displayed in the browser and on the console is the same.

One Identity strongly recommends that you test the upgrade process in a non-production (virtual, and so on) environment first.

Upgrading SPS requires a reboot. We strongly suggest that you perform the upgrade on the production appliance during maintenance hours only, to avoid any potential data loss.