サポートと今すぐチャット
サポートとのチャット

One Identity Safeguard for Privileged Sessions 7.5.1 - Installation Guide

Installing SPS as a Kernel-based Virtual Machine

The following describes how to install a new SPS as a Kernel-based Virtual Machine.

To install a new SPS as a Kernel-based Virtual Machine

  1. 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.

    • Guest operating system: Linux/Ubuntu 64-bit

    • 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.

    • The hard disk controller must be virtio.

    • 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.

    • SPS requires 4 network cards, all of them must be virtio.

      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 VMWare 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.

      Configure unused network cards — at least the fourth (eth3) — to use internal NAT.

    • To index connections without significant delay, add two CPU cores to the virtual machine. Note that these settings are suitable for evaluation purposes. To test SPS under significant load, contact One Identity for recommendations. The resource requirements of indexing depend heavily on the amount and type of the indexed traffic, and can also require using external indexer hosts (for details on external indexers, see Configuring external indexers in the Administration Guide).

  2. 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.

  3. Mount the ISO image and boot the virtual machine. Follow the on-screen instructions to install SPS.

Limitations of SPS under KVM

The following limitations apply to running version 7.5.1 of SPS under KVM:

  • SPS can be installed under KVM on most modern Linux distributions. One Identity currently tests the following KVM version:

    # virsh version
Compiled against library: libvirt 1.2.17
Using library: libvirt 1.2.17
Using API: QEMU 1.2.17
Running hypervisor: QEMU 1.5.3

  • SPS can only use fixed disk space assigned to the virtual host, it is not possible to use on-demand disk allocation scenarios.

  • 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.

Deploying One Identity Safeguard for Privileged Sessions from the Azure Marketplace

This guide provides detailed descriptions for deploying One Identity Safeguard for Privileged Sessions (SPS) from the Microsoft Azure Marketplace.

Before you start:

Before you start evaluating SPS, make sure you understand what SPS is and how it works. This information can greatly help you get SPS operational.

Prerequisites

The following prerequisites must be met to deploy SPS in Microsoft Azure:

  • You have a valid One Identity Safeguard for Privileged Sessions license. When deployed from the Microsoft Azure Marketplace, the One Identity Safeguard for Privileged Sessions uses the "Bring your own license" model. Note that to deploy two active SPS nodes as an availability set, you must purchase two standalone SPS licenses. To purchase a license, contact our Sales Team.

  • Microsoft recommends to use the Azure Resource Manager (ARM) deployment model. When you install SPS from the Azure Marketplace, SPS supports only this deployment method. If you need to deploy SPS into and infrastructure that uses the Classic deployment model, contact your One Identity sales representative.

  • You have a Microsoft Azure account.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択