Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

System requirements

The system requirements for Hitachi Ops Center Analyzer server, Ops Center Analyzer detail view server, and Analyzer probe server are explained.

For details about system requirements for using the virtual appliance, see the Hitachi Ops Center Virtual Appliance System Requirements.

System requirements for using the installer

Analyzer server requirements (Linux)

The requirements for Linux operating systems, the network configuration, the RPM packages, the kernel parameters, and the hardware are as follows:

Supported operating systems

  • Red Hat Enterprise Linux 6.5-6.9, 7.0-7.6 (x64)
  • Oracle Linux 6.7-6.9, 7.0-7.6 (Unbreakable Enterprise Kernel) (x64)
  • Oracle Linux 7.4-7.6 (Red Hat Compatible Kernel release 4) (x64)
NoteYou cannot send dashboard reports to users running Red Hat Enterprise Linux 6.x or Oracle Linux 6.x.
Network configuration

The Analyzer server supports IPv4 only.

Prerequisite RPM packages

Install the following RPM packages before installing the Analyzer server. You can check which RPM packages are missing by running the precheck tool (analytics_precheck.sh) provided by Ops Center Analyzer.

RPM packagesDetails
  • tcsh
  • net-tools
  • bc

If dashboard reports are to be sent to users, you must install the following packages and package group.

  • package
    • gtk3-3.22.10 or later
    • libXScrnSaver
    • nss-3.22 or later
  • package group
    • fonts
Kernel parameters

Before installing the Analyzer server on Linux, you must set the following kernel parameter values:

File*ParameterValue to be set

/etc/sysctl.conf

Fourth parameter (SEMMNI) of kernel.sem

The larger of 1024 and the following value: 24 + current-system-value

/etc/security/limits.conf

soft nofile

hard nofile

The larger of 8514 and the following value: 4418 + current-system-value

*: The file path differs according to the environment. In addition, kernel parameters can also be set for files that are not listed here.

Hardware requirements
PrerequisitesValue

Processor

Depends on the system scale1.

Memory

Depends on the system scale1.

Disk space

Installation directory2

Depends on the system scale1.

/tmp2

2 GB

/var2

5 GB

Notes:

  1. Refer to Hardware requirements based on system scale for more information.
  2. Make sure that these directories are not created on Network File System (NFS) partition.

Analyzer server requirements (Windows)

The requirements for Windows operating systems, the network configuration, and the hardware are as follows:

Supported operating systems
OS name EditionSP Architecture

Windows Server 2008 R21

  • Standard
  • Enterprise
  • Datacenter

SP1

x64

Windows Server 20122

  • Standard
  • Datacenter

No SP

x64

Windows Server 2012 R22

  • Standard
  • Datacenter

No SP

x64

Notes:

  1. Server core is not supported.
  2. Server core and Minimal Server Interface are not supported.
Network configuration

The Analyzer server supports IPv4 only.

Hardware requirements
Prerequisites Minimum Recommended

Processor

Dual-Core processor

Quad-Core processor

Memory

8 GB

16 GB minimum

Disk space

50 GB

100 GB minimum

Analyzer detail view server requirements

The requirements for operating systems, the network configuration, the java version, the RPM packages, the kernel parameters, and the hardware are as follows:

Supported operating systems

  • Red Hat Enterprise Linux 6.1, 6.5-6.9, 7.0-7.6 (x64)
  • Oracle Linux 6.7-6.9, 7.0-7.6 (Unbreakable Enterprise Kernel) (x64)
  • Oracle Linux 7.4-7.6 (Red Hat Compatible Kernel release 4) (x64)
Network configuration

The Analyzer detail view server supports IPv4 only.

Java version

JDK 1.8 update 91 or later (x64). For OpenJDK, the JDK must be equivalent to java-1.8.0-openjdk-devel.

NoteBefore installing the Analyzer detail view server, you must set the paths for the java and keytool commands.
Prerequisite RPM packages

Install the following RPM packages before installing the Analyzer detail view server. You can check which RPM packages are missing by running the precheck tool (analytics_precheck.sh) provided by Ops Center Analyzer.

RPM packagesDetails
  • perl
  • expect
  • openssl-devel (1.0.1e-fips 11 Feb 2013 or later)
  • parted
  • nss-3.21.0 or later
  • gcc
  • unzip
  • perl-CPAN
  • expat-devel
  • sysstat
  • zip
  • bc
  • net-tools
  • sudo
  • crontabs
  • nc or nmap-ncat (recommended)
  • lsof (recommended)
  • telnet (recommended)
  • fontconfig 2.13.0-4.3 or later
  • xorg-x11-font-utils 7.5-21 or later
  • xorg-x11-fonts-Type1
  • dejavu-sans-fonts
  • perl-IO-Socket-SSL
  • perl-XML-Simple
  • If nc (or nmap-ncat), lsof, and telnet are not installed or the path for jstack of the JDK is not set, some maintenance information cannot be obtained. If a problem occurs, you might be asked to obtain maintenance information. For this reason, we recommend that you make all of them available.
  • If you are using one of the following OSs, the package perl-XML-Simple is required:
    • Red Hat Enterprise Linux 7.0 or later
    • Oracle Linux 7.0 or later
Kernel parameters

Before installing the Analyzer detail view server on Linux, you must set the following kernel parameter values:

File*ParameterValue to be set

/etc/sysctl.conf

fs.file-max

327675 or greater

/etc/security/limits.conf

megha soft nofile

megha hard nofile

262140 or greater

*: The file path differs according to the environment. In addition, kernel parameters can also be set for files that are not listed here.

Hardware requirements
PrerequisitesValue

Processor

Depends on the system scale1.

Memory

Depends on the system scale1.

Disk space

Installation directory2,3

Depends on the system scale1.

/ (root)3

5 GB

/tmp3

100 MB

/usr/local3

1 GB

/home3

100 MB

Notes:

  1. The memory and disk capacity requirements vary depending on the managed resources. For example, if the managed storage systems contain a large number of volumes, the database will consume significant disk space. If you decrease the interval at which you obtain performance information from the managed resources, the volumes occupy more disk space in the database. Refer to Hardware requirements based on system scale for more information.
  2. When you run the analytics_install.sh command, do not install the Analyzer detail view server on the same disk where the operating system is installed. You must install the Analyzer detail view server on a physical disk.
  3. Make sure that these directories are not created on Network File System (NFS) partition.

Analyzer probe server requirements

The requirements for operating systems, the network configuration, the java version, the RPM packages, the kernel parameters, and the hardware are as follows:

Supported operating systems

  • Red Hat Enterprise Linux 6.1, 6.5-6.9, 7.0-7.6 (x64)
  • Oracle Linux 6.7-6.9, 7.0-7.6 (Unbreakable Enterprise Kernel) (x64)
  • Oracle Linux 7.4-7.6 (Red Hat Compatible Kernel release 4) (x64)
Network configuration

The Analyzer probe server supports IPv4 only.

Java version

JDK 1.8 update 91 or later (x64). For OpenJDK, the JDK must be equivalent to java-1.8.0-openjdk-devel.

NoteBefore installing the Analyzer probe server, you must set the paths for the java and keytool commands.
Prerequisite RPM packages

Install the following RPM packages before installing the Analyzer probe server. You can check which RPM packages are missing by running the precheck tool (dcaprobe_precheck.sh) provided by Ops Center Analyzer.

RPM packagesDetails
  • perl
  • perl-CPAN
  • gcc
  • expect
  • openssl-devel (1.0.1e-fips 11 Feb 2013 or later)
  • unzip
  • glibc.i686
  • glibc.x86_64
  • libstdc++.i686
  • libstdc++.x86_64
  • net-tools
  • tcsh
  • libyaml
  • libgcc.x86_64
  • nss-softokn-freebl.x86_64
  • iproute.x86_64
  • ncurses
  • openssh-clients
  • nss-3.21.0 or later
  • expat-devel
  • xinetd
  • sysstat
  • zip
  • bc
  • sudo
  • crontabs
  • make
  • nc or nmap-ncat (recommended)
  • lsof (recommended)
  • telnet (recommended)
  • perl-IO-Socket-SSL
  • perl-Digest-MD5
  • perl-XML-Simple
  • If nc (or nmap-ncat), lsof, and telnet are not installed or the path for jstack of the JDK is not set, some maintenance information cannot be obtained. If a problem occurs, you might be asked to obtain maintenance information. For this reason, we recommend that you make all of them available.
  • If you are using one of the following OSs, the packages perl-Digest-MD5 and perl-XML-Simple are required:
    • Red Hat Enterprise Linux 7.0 or later
    • Oracle Linux 7.0 or later
Kernel parameters

Before installing the Analyzer probe server on Linux, you must set the following kernel parameter values:

File*ParameterValue to be set

/etc/sysctl.conf

fs.file-max

327675 or greater

/etc/security/limits.conf

megha soft nofile

megha hard nofile

262140 or greater

*: The file path differs according to the environment. In addition, kernel parameters can also be set for files that are not listed here.

Hardware requirements
PrerequisitesValue for Analyzer probe serverValue for RAID Agent

Processor

Depends on the system scale*.

Memory

Depends on the system scale*.

Disk space

Installation directory

Depends on the system scale*.

/ (root)

5 GB

--

/tmp

100 MB

350 MB

/usr/local

1 GB

--

/opt/jp1pc

--

1 GB

/home

100MB

--

*: The memory and disk capacity requirements vary depending on the managed resources. For example, if the managed storage systems contain a large number of volumes, the database will consume significant disk space. If you decrease the interval at which you obtain performance information from the managed resources, the volumes occupy more disk space in the database. Refer to Hardware requirements based on system scale for more information.

Analyzer Windows probe requirements

The requirements for operating systems, the network configuration, the locale, the software, and the hardware are as follows:

Supported operating systems
OS name EditionSP Architecture

Windows Server 2008 1

  • Standard
  • Enterprise
  • Datacenter
  • SP1
  • SP2
  • No SP
  • x64
  • x86

Windows Server 2008 R21

  • Standard
  • Enterprise
  • Datacenter
  • SP1
  • No SP

x64

Windows Server 20122

  • Standard
  • Datacenter

No SP

x64

Windows Server 2012 R22

  • Standard
  • Datacenter

No SP

x64

Windows Server 20163

  • Standard
  • Datacenter

No SP

x64

Notes:

  1. Server core is not supported.
  2. Server core and Minimal Server Interface are not supported.
  3. Server core and Nano Server are not supported.
Network configuration

The Windows probe supports IPv4 only.

Locale

The Analyzer Windows probe must be installed on a windows machine with one of the following English locales:

  • Australia
  • Belize
  • Canada
  • Caribbean
  • India
  • Ireland
  • Jamaica
  • Malaysia
  • New Zealand
  • Philippines
  • Singapore
  • South Africa
  • Trinidad and Tobago
  • United Kingdom
  • United States
  • Zimbabwe

The Display language and Input Method language on a Windows machine must be set to English.

Software requirements
Software name VersionProtocol

Microsoft .NET Framework

3.5 Service Pack1 or later

HTTP

4.5 or later

  • HTTP
  • HTTPS
Hardware requirements
Prerequisites Minimum

Memory

8 GB

Disk space (system drive)

50 GB

NoteYou must install one Analyzer Windows probe for every 100 machines.

Port requirements

Before you install the Analyzer server, Analyzer detail view server or Analyzer probe server, review the desktop, port, and firewall requirements.

Note
Default port number for Analyzer server

Source IP address

Target IP address

Default port

Protocol

User Desktop

Analyzer server

22015

HTTP

22016

HTTPS

Analyzer server

RAID Agent Server

or

Tuning Manager - Agent for RAID Server

24221

HTTP

24222

HTTPS

22

SSH

Ops Center Common Services

443

TCP

Default port number for Analyzer detail view server

Source IP address

Target IP address

Default port

Protocol

User Desktop, Analyzer server

Analyzer detail view server

8443

TCP

Analyzer probe server

Analyzer detail view server

9092

TCP

Analyzer probe server

Analyzer detail view server / FTP Server

22

SFTP

7443

HTTPS

21

FTP

990

FTPS

Analyzer probe server

Analyzer detail view server

8443

HTTPS

User Desktop

Analyzer detail view server

8080

TCP

Notes:

Default port number for Analyzer probe server

Source IP address

Target IP address

Default port

Protocol

User Desktop

Analyzer probe server

8443

TCP

22

TCP

8080

TCP

Analyzer probe server

Tuning Manager server

22015

HTTP

22016

HTTPS

Notes:

Probe port and firewall requirements

Probe name

Collection method

Source IP address

Target IP address

Default port

Protocol

Storage systems

Hitachi AMS

SNM2API

Analyzer probe server

AMS Controller

2000

TCP

Hitachi Enterprise Storage

RAID Agent

or

Tuning Manager - Agent for RAID

Analyzer probe server

RAID Agent Server

or

Tuning Manager - Agent for RAID Server

24221

HTTP

24222

HTTPS

RAID Agent Server

or

Tuning Manager - Agent for RAID Server

10996, 110997, 51099, and 51100

Storage systems that are managed through SVP

TCP

RAID Agent5

RAID Agent Server

GUM(CTL)

80

HTTP

443

HTTPS

Hitachi Device Manager API

Analyzer probe server

Hitachi Device Manager Server

2001

HTTP

2443

HTTPS

Hitachi Ops Center API Configuration Manager API

Analyzer probe server

Hitachi Ops Center API Configuration Manager Server

23450

HTTP

23451

HTTPS

Hitachi NAS

RUSC

Analyzer probe server

HNAS SMU

22

SSH

REST API

8444

HTTPS

IBM XIV1

xcli

Analyzer probe server

XIV Storage System Management IP

7778

TCP

NetApp

ONTAP API

Analyzer probe server

NetApp Filer

443

HTTPS

VMAX

Unisphere REST API

Analyzer probe server

Unisphere Server

8443

TCP

SYMCLI

Analyzer probe server

Solution Enabler

2707

TCP

VNX Block2

naviseccli

Analyzer probe server

VNX Storage Processor A and B

443

HTTPS

80

HTTP

VNX File

VNX CLI Station CLI

Analyzer probe server

VNX Storage

22

SSH

XtremIO

XMS (Rest API)

Analyzer probe server

XMS

443

HTTPS

Pure Storage

Rest API

Analyzer probe server

Pure Storage

80

HTTP

443

HTTPS

HPE 3PAR

CLI

Analyzer probe server

HPE 3PAR StoreServ Storage

22

SSH

Hypervisors

VMware

VMware vCenter API

Analyzer probe server

VMware vCenter Server/VMware ESXi Host

443

TCP

Windows (Hyper-V)

WMI

Windows probe

Windows Host/Hyper-V

135

TCP

Perfmon

445

SCOM

SCOM server

5723, 5724, and 51905

SCCM

SCCM server

1433

FC Switches

Brocade FC Switch (BNA)

BNA (REST API)

Analyzer probe server

BNA server

80

HTTP

443

HTTPS

Brocade FC Switch (CLI)

Brocade Switch CLI

Analyzer probe server

Brocade FC Switch

22

SSH

Cisco DCNM

3

DCNM (Web Services)

Analyzer probe server

DCNM Server

80

HTTP

443

HTTPS

Cisco SAN Switch

Cisco Switch CLI

Analyzer probe server

Cisco FC Switch

22

SSH

Hosts

Linux

ssh

Analyzer probe server

Linux host

22

SSH

xinetd

Linux host

Analyzer probe server

11114

TCP

Notes:

  1. The CLI installer (xivcli-3.0.1-build3-linux32.tar) for IBM XIV probe is available from the IBM support site, deployed on the probe.
  2. The NaviCLI runs locally on the probe machine, which internally makes HTTP or HTTPS calls to the VNX storage.
  3. Cisco DCNM 10.0 does not support HTTP.
  4. For virtual appliances, Any is open.
  5. This port is required if the REST API is used.
  6. This port is used to monitor storage systems other than VSP 5000 series.
  7. This port is used to monitor VSP 5000 series storage systems.

Supported ciphers

The Analyzer detail view server and Analyzer probe server support various different ciphers when transferring data using HTTPS or SFTP connections.

Supported ciphers for Analyzer probe

The following ciphers are supported while transferring data using SFTP and HTTPS connections from the Analyzer probe server to the Analyzer detail view server or Intermediate FTP server:

NoteThe first matching algorithm on the Analyzer detail view server or Intermediate FTP server is used for the SSL handshake.
Kex algorithm: diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1, diffie-hellman-group1-sha1
Host key algorithm: ssh-rsa, ssh-dss
Encryption algorithm: aes256-cbc, aes192-cbc, aes128-cbc, aes256-ctr, aes192-ctr, aes128-ctr, twofish256-cbc, twofish192-cbc, twofish-cbc, twofish256-ctr,
twofish192-ctr, serpent256-cbc, serpent192-cbc, serpent128-cbc, serpent256-ctr, serpent192-ctr, serpent128-ctr, 3des-cbc, 3des-ctr, cast128-cbc, cast128-ctr,
arcfour256, arcfour128, arcfour, idea-cbc, idea-ctr, blowfish-ctr, none
MAC algorithm: hmac-sha2-512-96, hmac-sha2-512, hmac-sha2-256-96, hmac-sha2-256, hmac-sha1-96, hmac-sha1, hmac-md5-96, hmac-md5, none
Compression algorithm: zlib, none

Supported ciphers for Analyzer Windows probe

The following ciphers are supported while transferring data using an HTTPS connection from the Analyzer Windows probe to the Analyzer detail view server or Intermediate FTP server:

NoteThe first matching algorithm on the Analyzer detail view server or Intermediate FTP server is used for the SSL handshake.
Kex algorithm: diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1, diffie-hellman-group1-sha1
Host key algorithm: ssh-rsa, ssh-dss
Encryption algorithm: aes256-cbc, aes192-cbc, aes128-cbc, aes256-ctr, aes192-ctr, aes128-ctr, twofish256-cbc, twofish192-cbc, twofish-cbc, twofish256-ctr, twofish192-ctr, serpent256-cbc, serpent192-cbc, serpent128-cbc, serpent256-ctr, serpent192-ctr, serpent128-ctr, 3des-cbc, 3des-ctr, cast128-cbc, cast128-ctr, arcfour256, arcfour128, arcfour, idea-cbc, idea-ctr, blowfish-ctr, none
MAC algorithm: hmac-sha2-512-96, hmac-sha2-512, hmac-sha2-256-96, hmac-sha2-256, hmac-sha1-96, hmac-sha1, hmac-md5-96, hmac-md5, none
Compression algorithm: zlib, none

The following ciphers are supported while transferring data using an SFTP connection from the Analyzer Windows probe to the Analyzer detail view server or Intermediate FTP server:

Kex algorithm: AES-256-CBC, AES-192-CBC, AES-128-CBC, DES-EDE3-CBC encryption
MAC algorithm: hmac-sha2-512-etm@openssh.com, hmac-sha2-256-etm@openssh.com
Host key algorithm: ecdsa-sha2-nistp521, ecdsa-sha2-nistp384, ecdsa-sha2-nistp256, ssh-rsa, ssh-dss
Encryption algorithm: aes256-cbc, aes256-ctr, aes192-cbc, aes192-ctr, aes128-cbc, aes128-ctr, 3des-cbc, 3des-ctr

Supported browsers

The following browsers are supported:

Web browser/other Version

Firefox

ESR 68.0

Internet Explorer

11*

Chrome Browser for enterprise

Latest version of stable channel

Flash Player

21.0 or later (to use Report Builder with the Analyzer detail view server)

*: Browser subwindows may open behind the main (parent) window.

Monitoring target requirements

You can monitor the following storage system series, hypervisors, hosts, and FC switches.

Monitoring target storage systems

You can monitor the following storage system series:

Storage system series Storage system Microcode/HNAS model Analyzer probe name
VSP Hitachi Virtual Storage Platform 70-06-33 or later Hitachi Enterprise Storage probe1, 2
VSP F series VSP Fx00 models Hitachi Virtual Storage Platform F400 (VSP F400) 83-02-01 or later
Hitachi Virtual Storage Platform F600 (VSP F600)
Hitachi Virtual Storage Platform F800 (VSP F800)
88-01-03 or later4 Hitachi Virtual Storage Platform F350 (VSP F350)
Hitachi Virtual Storage Platform F370 (VSP F370)
Hitachi Virtual Storage Platform F700 (VSP F700)
Hitachi Virtual Storage Platform F900 (VSP F900)
VSP F1500 Hitachi Virtual Storage Platform F1500 80-05 or later
VSP G series VSP Gx00 models Hitachi Virtual Storage Platform G200 (VSP G200) 83-02-01 or later
Hitachi Virtual Storage Platform G400 (VSP G400)
Hitachi Virtual Storage Platform G600 (VSP G600)
Hitachi Virtual Storage Platform G800 (VSP G800)
Hitachi Virtual Storage Platform G350 (VSP G350) 88-01-03 or later4
Hitachi Virtual Storage Platform G370 (VSP G370)
Hitachi Virtual Storage Platform G700 (VSP G700)
Hitachi Virtual Storage Platform G900 (VSP G900)
VSP G1000 Hitachi Virtual Storage Platform G1000 80-03-31 or later
VSP G1500 Hitachi Virtual Storage Platform G1500 80-05 or later
VSP N series

See "Notes on notation of the VSP N series" below.

Hitachi Virtual Storage Platform N400 (VSP N400)83-06-01 or later
Hitachi Virtual Storage Platform N600 (VSP N600)
Hitachi Virtual Storage Platform N800 (VSP N800)
VSP 5000 series Hitachi Virtual Storage Platform 510090-02 or later
Hitachi Virtual Storage Platform 5500
Hitachi Virtual Storage Platform 5100H
Hitachi Virtual Storage Platform 5500H
HUS VM Hitachi Unified Storage VM 73-03-40 or later
HUS100 Hitachi Unified Storage 110 (HUS110) 09-10 or later Hitachi Adaptor Modular Storage (AMS) probe
Hitachi Unified Storage 130 (HUS130)
Hitachi Unified Storage 150 (HUS150)
Hitachi NAS HNAS
  • 3080
  • 3090
  • 4040
  • 4060
  • 4080
  • 4100
  • VSP G400 (Unified)
  • VSP G600 (Unified)
  • VSP G800 (Unified)
  • VSP F400
  • VSP F600
  • VSP F800
  • VSP N400
  • VSP N600
  • VSP N800
HNAS probe3

Notes:

  1. If performance data is collected using a command device, make sure that the RAID Manager LIB is installed on the same server as the Hitachi Enterprise Storage probe.
  2. The storage systems from which the Hitachi Enterprise Storage probe can collect data are the same regardless of using the RAID Agent or Tuning Manager - Agent for RAID.
  3. To view Hitachi NAS configuration and performance of reports, access the Analyzer detail view server.
  4. The required microcode version differs depending on the performance data collection method.
    • When using the command device and the SVP, one of the following microcode versions is required: 88-01-03 to 88-01-04 and 88-02-01.
    • When using the command device and the REST API, microcode version 88-02-01 or later is required.
    • When using the SVP and the REST API, microcode version 88-02-01 is required.
    • When using only the REST API, microcode version 88-02-01 or later is required.
Note
  • The following storage systems might be referred to as Hitachi Enterprise storage systems:
    • VSP
    • VSP F series
    • VSP G series
    • VSP 5000 series
    • HUS VM
  • Hitachi Enterprise storage systems support Granular Data Collection.
  • To manage additional Hitachi storage system information (such as storage capacity and hosts), use Device Manager 8.4.1 or later.
  • For I/O control settings using Server Priority Manager, use Automation Director 8.5.0 or later (except 8.5.1).
Notes on notation of the VSP N seriesBecause the VSP N series is equivalent to the VSP F series or VSP G series, Ops Center Analyzer uses the VSP F series or VSP G series storage model names to indicate the VSP N series. (The model descriptions are equivalent as well.)

The following table lists the correspondence.

Storage system model in the VSP N seriesNotation in Ops Center Analyzer

VSP N400

VSP F400 or VSP G400

VSP N600

VSP F600 or VSP G600

VSP N800

VSP F800 or VSP G800

Monitoring target hypervisors

You can monitor the following hypervisors:

Product name Version Analyzer probe name
VMware vCenter server
  • 5.0
  • 5.1
  • 5.5
  • 6.0
  • 6.5
  • 6.5u2
  • 6.6
  • 6.7
VMware probe
VMware ESXi
  • 5.0
  • 5.1
  • 5.5
  • 6.0
  • 6.5
  • 6.5u2
  • 6.6
  • 6.7
Hyper-V Windows Server 2008 R2 Hyper-V*

--

Windows probe
Windows Server 2012 Hyper-V*
Windows Server 2012 R2 Hyper-V*
Windows Server 2016 Hyper-V

*: Server core is not supported.

Monitoring target hosts

You can monitor the following hosts:

OS name Version/Edition Analyzer probe name
Windows Windows Server 20081
  • Standard
  • Enterprise
  • Datacenter
Windows probe
Windows Server 2008 R21
  • Standard
  • Enterprise
  • Datacenter
Windows Server 20121
  • Standard
  • Datacenter
Windows Server 2012 R21
  • Standard
  • Datacenter
Windows Server 20162
  • Standard
  • Datacenter
Linux Red Hat Enterprise Linux
  • 6.1
  • 6.5
  • 6.9
  • 7.1
  • 7.2
  • 7.3
  • 7.4
  • 7.5
  • 7.6
Linux probe
SUSE Linux Enterprise Server
  • 11
  • 12
Oracle Linux
  • 6.8
  • 7.0
  • 7.3
  • 7.4
  • 7.5
  • 7.6
CentOS
  • 6.6
  • 7.1
  • 7.2

Notes:

  1. Server core is not supported.
  2. Nano Server is not supported.

Hardware requirements based on system scale

This section provides guidelines for determining the size of your environment based on the number of monitoring targets. Based on the sizing and scalability recommendations, you can identify the hardware requirements and scale your Ops Center Analyzer environment to meet workload demands.

System scale

Maximum number of resources
HypervisorStorageFC Switch
VMESXVolumeStorage

Small scale

40

5

5000

1

1

Medium scale

1,000

15

35,000

5

5

Large scale

6,000

120

70,000

10

40

6,000

120

200,000

40

40

The hardware requirements for Ops Center Analyzer components vary depending on the size of your environment.

Hardware requirements for Analyzer server

System scale

CPU (cores)*Memory (GB)Disk (GB)

Small scale

4

8

100

Medium scale

4

8

100

Large scale

8

16

100

16

32

100

*: Based on an Intel(R) Xeon(R) Processor E5-2670 v2 @ 2.50 GHz.

Hardware requirements for Analyzer detail view server

System scale

CPU (cores)*Memory (GB)Disk (GB)
Data retention period
14 days32 days365 days

Small scale

4

8

150

150

800

Medium scale

4

8

150

300

3,000

Large scale

9

24

300

500

5,000

24

64

700

2,000

12,000

*: Based on an Intel Xeon Processor E5-2670 v2 @ 2.50 GHz.

Hardware requirements for Analyzer probe server

System scale

CPU (cores)1Memory (GB)Disk (GB)

Small scale

4

10

100

Medium scale

10

32

500

Large scale2

12

64

1,0003

Notes:

  1. Based on an Intel Xeon Processor E5-2670 v2 @ 2.50 GHz.
  2. If you are monitoring a system similar to, or larger than Large scale, consider installing multiple Analyzer probe servers.
  3. The types of disks used are SAN disks.