The One Identity Safeguard for Privileged Sessions (SPS) hardware has five network interfaces: three physical interfaces for handling traffic, the HA interface for communicating with other nodes in a High Availability cluster, and the IPMI. The T10 hardware has two additional network interfaces available: the SFP+ interfaces labeled A and B. For details on hardware installation, see "One Identity Safeguard for Privileged Sessions Hardware Installation Guide" in the Installation Guide.
You can assign any number of logical interfaces (alias IP addresses and netmasks) to a physical interface, and each logical interface can have its own VLAN ID. For more information on managing logical interfaces, see Managing logical interfaces.
The routing rules determine which interface is used for transferring remote backups and syslog messages of SPS.
TIP: One Identity recommends that you direct backups, syslog and SNMP messages, and e-mail alerts to a dedicated interface. For details, see Configuring the routing table.
The HA interface is an interface reserved for communication between the nodes of SPS clusters. The HA interface uses the Ethernet connector labeled as 4 (or HA). For details on High Availability, see High Availability support in One Identity Safeguard for Privileged Sessions (SPS).
In case of T10 hardware, the SFP+ interfaces are available for both proxy traffic and for local services. This means that these interfaces can be used for the same purposes as the other 3 physical interfaces.
The Intelligent Platform Management Interface (IPMI) allows system administrators to monitor system health and to manage SPS events remotely. IPMI operates independently of the operating system of SPS.
High Availability support in One Identity Safeguard for Privileged Sessions (SPS)
The goal of HA clusters is to support enterprise business continuity by providing location-independent load balancing and failover.
In High Availability (HA) mode, two One Identity Safeguard for Privileged Sessions (SPS) units with identical configurations are operating simultaneously. These two units are the primary node and the secondary node (previously also referred to as the master node and the slave node). The primary node shares all data with the secondary node, and if the primary node stops functioning, the other one becomes immediately active, so the servers are continuously accessible.
You can find more information on managing a High Availability SPS cluster in Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster.
One Identity recommends using a High Availability SPS cluster instead of a standalone SPS appliance. A standalone SPS appliance can become a single point of failure (SPOF), and its failure can severely impact your business.
Firmware and High Availability
When powering on the One Identity Safeguard for Privileged Sessions (SPS) nodes in High Availability mode, both nodes boot and start the firmware. There is a difference, however, between the two nodes in the services that they start on booting. The secondary node will launch only a few services, those that are required for High Availability support (that is, for awareness of the primary node and data synchronization). The rest of the services (for example, managing connections) start only on the primary node.
Upgrading the SPS firmware via the web interface automatically upgrades the firmware on both nodes.
Versions and releases of One Identity Safeguard for Privileged Sessions (SPS)
The following release policy applies to One Identity Safeguard for Privileged Sessions (SPS):
One Identity Safeguard for Privileged Sessions customers choose between two paths for receiving SPS releases: Long Term Supported (LTS) release or feature release.
Frequency: Typically, every 2 years
Scope: Includes new features, resolved issues and security updates
Versioning: First digit identifies the LTS and the second digit is a 0 (for example, 6.0, 7.0, and so on)
Frequency: Typically, every 2 months
Scope: Includes the latest features, resolved issues, and other updates, such as security patches for the OS
Versioning: First digit identifies the LTS and the second digit is a number identifying the feature release (for example, 6.1, 6.2, and so on)
Frequency:Typically, every 2 months during full support
Scope: Includes critical resolved issues
Versioning: Third digit designates the LTS maintenance release (for example, 6.0.1)
Frequency:Only for highly critical issues
Scope: Includes highly critical resolved issue
Versioning: Third digit designates the feature maintenance release (for example, 6.1.1)
Typically 3 years after the original publication date or until the next LTS is published (whichever date is later)
Typically 6 months after the original publication date or until the next feature or LTS release is published (whichever date is later)
For a full description of long-term-supported and feature releases, open the SPS product page on the Support Portal and navigate to Self Service Tools > Product Support > Product Life Cycle & Policies > Product Support Policies > Software Product Support Lifecycle Policy.
Downgrading from a feature release is not supported. If you upgrade from an LTS release (for example, 6.0) to a feature release (6.1), you have to keep upgrading with each new feature release until the next LTS version (in this case, 7.0) is published.