Typical hardware for the equipment tiers and operating systems is listed in Typical hardware for the equipment tiers.

Table 1. Typical hardware for the equipment tiers

Operating system

Platform equipment tier

Small (1–2 low end CPUs, 2 GB RAM)

Medium (2 CPUs, 4 GB RAM)

Large (2 CPUs, 4 GB RAM)

Extra large(4 CPUs, 4–8 GB RAM)

Red Hat Enterprise Linux

Any vendor,

1-2 Xeon 2.8 GHz

Any vendor,

2 Xeon 2.8

GHz

Any vendor,

2 Xeon 2.8 GHz

Any vendor,

4 Xeon 3.0 GHz

Solaris

UltraSPARC-T1 (T2000)

UltraS­PARC-T2 (T5220)

SPARC64 VII (M4000)

SPARC64 VII (M4000)

It is recommended that you work with Sun Microsystems, Inc. to determine models that meet or exceed these requirements in addressing your business needs.

Note:

Xeon processors vary a lot across models. The Xeon 3GHz 5160 is rated at about 16 at SpecInt for speed while the 2.93GHz Xeon X5670 is rated at about 37 for speed. If you require a specific speed processor, VMware recommends using the SpecInt (SPEC Integer) benchmark published by SPEC both for assessing the CPU speed and throughput ratings. SPEC is an organization of computer industry vendors dedicated to developing standardized benchmarks and publishing reviewed results.

CPUs may have multiple cores and cores may have multiple hardware threads. Cores and threads may share CPU resources with other cores and threads. This makes assessment of CPU capacity difficult. VMware recommends using the benchmark published by SPEC for assessing expected relative CPU performance. CPU2006 is the current version of the CPU component benchmark suite from SPEC.

The results are broken out by reported metric for:

  • CPU Speed: You can access this benchmark from:

    http://www.spec.org/cpu2006/results/cint2006.html

  • CPU Throughput: You can access this benchmark from:

    http://www.spec.org/cpu2006/results/rint2006.html

    While cint runs one copy of the benchmark, rint runs as many copies as there are threads in the machine.

    CPU speed and the number of CPUs available affect performance. You can get a sense of the expected performance by comparing the CPU speed directly to the speed ratings of the CPUs on which the benchmark is based. The current strategy for assessing the number of effective CPUs in a machine is to divide the throughput rating by the speed rating. In general, our software benefits more from faster CPU speed, than the comparable addition of more CPUs. Thus, it is preferred to have 1 CPU rated at 20, than 2 rated at 10.

    If you are installing more than one product, then your system must meet the products total memory and data disk space requirements.

    Required disk space for the Service Assurance Manager Server lists disk space requirements for installing the Service Assurance Manager Server.

Table 2. Required disk space for the Service Assurance Manager Server

Platform

Disk space

Solaris 9 and 10

730 MB

Red Hat Enterprise Linux AS 4 and 5

475 MB

Required disk space for the Service Assurance Manager console lists disk space requirements for installing the Service Assurance Manager console.

Table 3. Required disk space for the Service Assurance Manager console

Platform

Disk space

Solaris 10

485 MB

Red Hat Enterprise Linux AS 5

365 MB

CPU, memory, data disk space requirements lists minimum requirements for CPUs, memory, and data disk space that is used by the software for writable files such as logs, repository files, and output files.

Table 4. CPU, memory, data disk space requirements

VMware Smart Assurance product

CPUs

Memory (RAM)

Data disk space

Service Assurance Manager

2

512 MB

100 MB each

Global Console

1

256 MB

Not applicable

Global Console, Web Console, and Business Dashboard

1

256 MB

150 MB

VMware Smart Assurance Service Assurance Manager Adapter Platform

1

512 MB

100 MB each

Syslog Adapter

1

256 MB

50 MB each

SNMP Trap Adapter

1

256 MB

50 MB each

VMware Smart Assurance Adapter for UIM/O

1

256 MB

50 MB

XML Adapter

1

256 MB

See the following Note.

Note:

CPU means the number of physical CPU cores and not the number of CPUs displayed when hyperthreading is activated.

For the XML Adapter, disk space depends on the size of the output that you want to export. Each output file can range from 0 to 200 MB. If, for example, the XML Adapter communicates with 5 Service Assurance Global Managers and each output file is 200 MB, then 1 gigabyte (GB) is required.

If you are installing multiple products, then your system must meet the products’ total memory and data disk space requirements. Required disk space for the Service Assurance Manager Server defines required disk space and CPU, memory, data disk space requirements lists CPU, memory, and data disk space requirements.