ServerOptix™ Prerequisites

VMware

Installation VM (Where ServerOptix™ Is Installed)

  • OS: Ubuntu 22.04 LTS recommended. Other options, such as RHEL, are possible. Please contact QiO if another option would be preferable.
  • CPUs: 4
  • RAM: 8GB
  • Storage: 150GB
  • SSL Configuration: The VM must have valid certificates to interface with vCenter correctly.
  • Internal Connectivity: The Installation VM must be on the same network as the target servers. All vCenters that manage the target servers should be accessible from this VM. This will require port 443 to be opened on the machine where vCenter is hosted. If some of your vCenters and target servers are in a separate inaccessible network, please setup an Installation VM in each individual network.
  • External Connectivity: Internet access is not required, but if available will allow for a fast online install via our website. If it is unavailable, contact QiO who will support an offline install.
  • Software client should install prior to ServerOptix™ installation: Either Docker or Podman

Target Servers (Physical Servers to Be Optimized)

  • Target servers are physical servers.
  • Recommended CPUs. Contact QiO for CPUs that fall outside this specification:
    • Intel Xeon. Skylake SKU or later.
    • AMD EPYC
  • BIOS Settings: OS Power Management enabled (change requires a server restart)
  • OS: VMware ESXi 6.7 or later
  • vCenter Configuration:
    • Please configure a minimal custom account for QiO vSphere API access, with an account username comprised of letters, numbers, and hyphens only. This video guide will show you how: Creating a minimal custom account for vSphere API access
    • For target servers running ESXi v6.x or v7.x please follow this video guide to manually enable the Custom power policy: Setting ESXi v6.x or v7.x to a Custom power policy
    • While not strictly required for optimization, in order for the power reduction to be measured and displayed in the ServerOptix™ GUI, server power must be reported and visible within vCenter.

Linux

Installation VM (Where ServerOptix™ Is Installed)

  • OS: Ubuntu 22.04 LTS recommended. Other options, such as RHEL, are possible. Please contact QiO if another option would be preferable.
  • CPUs: 4
  • RAM: 8GB
  • Storage: 150GB
  • Internal Connectivity: The Installation VM must be on the same network as the target servers. All target servers should be accessible from the Installation VM. Ports 8086 and 8090 need to be open on this VM. If some of your target servers are in a separate inaccessible network, please setup an Installation VM in each individual network.
  • External Connectivity: Internet access is not required, but if available will allow for a fast online install via our website. If it is unavailable, contact QiO who will support an offline install.
  • Software client should install prior to ServerOptix™ installation: Either Docker or Podman

Target Servers (Physical Servers to Be Optimized)

  • Target servers are physical servers.
  • Recommended CPUs. Contact QiO for CPUs that fall outside this specification:
    • Intel Xeon. Skylake SKU or later.
    • AMD EPYC
  • BIOS Settings: OS Power Management enabled (change requires a server restart)
  • The CPU driver acpi-cpufreq must be loaded. You can check which driver is currently in use by running the command:
    $ cpupower frequency-info --driver
    If you need to change the driver, a server restart is required. Contact QiO if you need help.
  • ServerOptix™ requires SSH access to each target server. This will require port 22 to be open. An account with minimal access permissions, so that ServerOptix™ can only control precisely what it needs to and nothing more, can be created by running the following commands:
      root $ useradd qiocontroller
      root $ passwd qiocontroller
      root $ visudo -f /etc/sudoers.d/qiocontroller
        Cmnd_Alias QIO_CONTROLLER_CMDS = /usr/bin/cpupower, /bin/ipmitool sdr
        qiocontroller ALL=(ALL) NOPASSWD: QIO_CONTROLLER_CMDS
  • Telegraf needs to be installed and configured on each target server.
  • telegraf.conf
    
    [agent]
        interval = "1m"  # Adjust the collection interval as needed
        round_interval = true
        metric_batch_size = 1000
        metric_buffer_limit = 10000
        collection_jitter = "0s"
        flush_interval = "1m"  # Adjust the flush interval as needed
        flush_jitter = "0s"
        precision = ""
    
        # "hostname" should automatically be assigned based on the server's hostname
        # if this does not match the FQDN of the host listed in the JSON config file
        # please enable and populate the value below appropriately
        # hostname = "<Target Host address>"
    
        omit_hostname = false
    
    [[inputs.cpu]]
        interval = "5m"
        tags = { destination = "oe" }
    
    [[inputs.cpu]]
        interval = "1h"
        tags = { destination = "gui" }
    
    [[inputs.ipmi_sensor]]
        interval = "1h"
        use_sudo = true
        timeout = "5m"
        tags = { destination = "gui" }
    
    [[outputs.influxdb_v2]]
        urls = ["<Installation VM>:8086"]
        token = "<Influx Token>"
        organization = "qio"
        bucket = "telemetry"
        tagpass = { destination = ["oe"] }
    
    [[outputs.influxdb_v2]]
        urls = ["<Installation VM>:8089"]
        token = "<Influx Token>"
        organization = "qio"
        bucket = "telemetry"
        tagpass = { destination = ["gui"] }