This tutorial describes the possibilities and limitations of installing One Identity Safeguard for Privileged Sessions (SPS) 7.5.1 as a virtual appliance under a Hyper-V server.
Preface
Introduction
Package contents inventory
One Identity Safeguard for Privileged Sessions Hardware Installation Guide
Hardware specifications
One Identity Safeguard for Privileged Sessions (SPS) Appliance 3000
One Identity Safeguard for Privileged Sessions (SPS) Appliance 3500
One Identity Safeguard for Privileged Sessions (SPS) Appliance 4000
One Identity Safeguard for Privileged Sessions Software Installation Guide
One Identity Safeguard for Privileged Sessions VMware Installation Guide
One Identity Safeguard for Privileged Sessions Hyper-V Installation Guide
Installing One Identity Safeguard for Privileged Sessions as a Kernel-based Virtual Machine
Deploying One Identity Safeguard for Privileged Sessions from the Azure Marketplace
Virtual appliance maintenance
One Identity Safeguard for Privileged Sessions Hyper-V Installation Guide
One Identity Safeguard for Privileged Sessions Hyper-V Installation Guide
Limitations of SPS under Hyper-V
One Identity Safeguard for Privileged Sessions Hyper-V Installation Guide > Limitations of SPS under Hyper-V
Version 7.5.1 of SPS has no special support for running under Hyper-V. While the basic functionality of SPS is not affected by running as a virtual appliance, the following limitations apply:
-
If High Availability (HA) operation mode is required in a virtual environment, use the HA function provided by the virtual environment.
-
Hardware-related alerts and status indicators of SPS may display inaccurate information, for example, display degraded RAID status.
-
When running SPS under Microsoft Hyper-V, ensure that the network interfaces are actually connected to the network. When running under Hyper-V, SPS indicates on the Basic Settings > Network > Ethernet links page that there is a link even if the network interface is configured and enabled, but not connected to the network.
-
When rebooting SPS in Hyper-V, the following critical error message may appear in the event log of the Hyper-V host:
<Virtual machine name> was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault.
This is normal, there is no problem with SPS. For details, see Triple fault in event log shows reset of Linux virtual machines.
Installing SPS under Hyper-V
One Identity Safeguard for Privileged Sessions Hyper-V Installation Guide > Installing SPS under Hyper-V
The following describes how to install a new SPS under Hyper-V.
To install a new SPS under Hyper-V
-
Create the virtual machine for SPS using the following settings. Note that these settings are suitable for evaluation purposes. To test SPS under significant load, contact One Identity for recommendations.
-
Choose Generation 1 for the virtual machine.
-
Allocate memory for the virtual machine. SPS requires a minimum of 8 GiB of memory. The recommended size for the memory depends on the exact environment, but consider the following:
-
The base system requires 8 GiB of memory.
-
SPS requires about 1-5 MiB of memory for every active connection, depending on the type of the connection — graphical protocols require more memory.
-
-
Do not use RAID for the hard disk, use the data duplication features of your virtual environment instead. That way, a single hard disk is sufficient for the system. If you need to use the built-in RAID support of SPS for some reason, use two hard disks, and SPS will automatically use them in software RAID.
Caution: Hazard of data loss When you install or reinstall SPS in a virtual environment, always create new hard disks. Using existing hard disks can cause unexpected behavior and operational problems.
-
Configure a fixed size disk with at least 30 GiB space. About 15 GiB is required for the base system, the remaining disk space is used to store data. To increase the initial disk size, see Modifying the disk size of a SPS virtual appliance.
NOTE: SPS will use the network card with the lowest PCI ID as eth0 (Physical interface 1), the card with the second lowest PCI ID as eth1 (the Physical interface 2), and so on. In some cases, this might differ from the labels in the Hyper-V management interface, for example, it is possible that eth0 will be labeled as Network adapter 4, and as a result, the SPS Welcome Wizard will not be available on Network adapter 1.
-
SPS requires at least one network card to function. Configurations can use up to 6 network cards.
NOTE: The fourth (eth3) network card is reserved for High Availability mode by default. Therefore, make sure you enable, but do not attach, the fourth (eth3) network card to a network.
Caution: Hyper-V offers two kinds of virtual Network Adapters (NICs): Legacy and Synthetic. Due to a known issue (Hyper-V network adapters are mapped to a different eth on every boot), using Legacy and Synthetic NICs within the same configuration will result in improper network setup. If you have to use more than one NICs, we recommend using only Legacy NICs.
-
-
Login to your support portal and download the latest One Identity Safeguard for Privileged Sessions installation ISO file. Note that you need to have purchased SPS as a virtual appliance or have partner access to download One Identity Safeguard for Privileged Sessions ISO files. If you are a partner but do not see the ISO files, you can request partner access within support portal.
-
Mount the ISO image and boot the virtual machine. Follow the on-screen instructions to install SPS.
Installing One Identity Safeguard for Privileged Sessions as a Kernel-based Virtual Machine
Installing One Identity Safeguard for Privileged Sessions as a Kernel-based Virtual Machine
This tutorial describes the possibilities and limitations of installing One Identity Safeguard for Privileged Sessions (SPS) 7.5.1 as a virtual appliance using the Kernel-based Virtual Machine (KVM) solution.