Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 VSE Management Software Version 4.0 Support Matrix

Windows CMS Requirements
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

spacerspacerspacer
spacer
spacer
  		 
 
Windows CMS Requirements

This section lists the following Windows CMS requirements:

  • Windows CMS hardware requirements: Table 1

  • Windows CMS software requirements: Table 2

  • Managed Node Requirements — Managing from a Windows CMS: Table 3

Table 1 Windows CMS Hardware Requirements

Supported Servers

c-Class ProLiant Blades: G3 or higher recommended

300/500/700 series DL/ML rack mount and tower: G3 or higher recommended for CMS

Processors

At least 1.6 GHz (2 GHz or higher recommended)

Two or more processing cores are required

MemoryAt least 4 GB RAM (6 GB RAM recommended for maximum hardware configuration)
Disk Space: Install Drive

HP SIM requires 900 MB. The VSE Management Software requires an additional 800 MB.

Log files are stored in the directory install-path\Virtual Server Environment\logs. These logs are not automatically trimmed.

Disk Space: Data Directory

Capacity Advisor requires a maximum of 4 GB for every 100 workloads to maintain 4 years of historic data. This data is stored in a directory that you choose at install time. The default directory is %ALLUSERSPROFILE%\Application Data\HP\Virtual Server Environment.

You can modify the amount of data retained in data collection by modifying the PROFILE_RETAIN_DAYS variable. For details, see the HP Capacity Advisor Version 4.0 User's Guide.

Disk Space: Database Storage

Global Workload Manager requires at least 1 GB. If you intend to keep historical data, HP recommends allowing 4 GB for every 100 workloads managed by gWLM. If you are not interested in historical data, you can trim the historical database by using the following command:

gwlm history --truncate

This space will be allocated on the MSQL Database server (or local to the CMS, if MSQL Express is used).

Disk Space: Paging Space6 GB total
Enclosures

C7000

C3000

NICs

c-Class embedded GbE NICs and mezzanine cards

HBAs

c-Class mezzanine FC HBAs (QLogic and Emulex)

Blade Interconnects

Virtual Connect-Ethernet and Virtual Connect-Fibre Channel

Cisco Ethernet switches outside encl. (65xx, 29xx, 37xx) and internal to enclosure

Shared Boot Storage: Boot and Data LUNs

HP MSA 1xxx; MSA 2000

HP EVA 4/6/8000; EVA LE

 

Table 2 Windows CMS Software Requirements

Operating System

Windows Server 2003 Standard SP2

Windows Server 2003 Enterprise SP2

Windows Server 2003 R2 Standard SP2

Windows Server 2003 R2 Enterprise SP2

Virtualization Platforms

VMware ESX 3.0.1 guest running a supported Windows CMS operating system[1]

VMware ESX 3.0.2 guest running a supported Windows CMS operating system

Databases

Microsoft SQL Server 2005 SP1 (local or remote)

Microsoft SQL Server 2005 Express SP1

Insight Control Management

ICM v2.30

  • HP Systems Insight Manager 5.2.1

  • HP BladeSystem Integrated Manager 3.2.1

  • HP Insight Power Manager 1.40

  • Performance Management Pack 4.7

  • Virtual Machine Management Pack 3.5

  • Server Migration Pack – Universal Edition 3.50

  • HP Virtual Connect Enterprise Manager 1.10

Browsers

Microsoft Internet Explorer 6 SP2

Microsoft Internet Explorer 7

Mozilla Firefox 1.5

Mozilla Firefox 2.0

CMS as a Managed SystemIf the CMS is also a managed system, then all of the additional requirements for managed systems apply to the CMS. For those requirements, see Table 3.

[1] Logical server operations require ESX 3.0.2 or later.

 

Table 3 Managed Node Requirements — Managing from a Windows CMS

Supported Servers

c-Class ProLiant Blades (G5 or higher required for some SMP-UE operations)[1]:

  • BL460c and BL480c — System ROM 2007.06.28 or later

  • BL465c and BL685c — System ROM 2007.04.05 or later

  • BL680c G5 — System ROM 2007.08.09 or later

  • BL860c — System, BMC and iLO2 version 1.01A

300/500/700 series DL/ML rack mount & tower (G5 or higher required for some SMP-UE operations)

p-class and c-Class Integrity blades (Windows, Linux, HP-UX)

HP Integrity servers (non-blade)

HP 9000

Enclosures

C7000

C3000

NICs

c-Class embedded GbE NICs and mezzanine cards:

  • NC370i, NC373i, and NC373m — Boot code version 1.9.6 and c-Class option ROM 1.1.3

  • NC326i, NC325m, and NC326m — Boot code version 3.28 and c-Class option ROM 1.1.3

  • NC360m and NC364m — c-Class option ROM 1.0.11

HBAs

c-Class mezzanine FC HBAs (QLogic and Emulex):

  • QLogic QMH2462 4Gb FC HBA (Integrity) — EFI 1.09 (in multiboot 1.64)

  • QLogic QMH2462 4Gb FC HBA (ProLiant) — 1.63 (with BIOS 1.26)

  • HP Emulex LPe 1105-HP 4Gb FC HBA — Emulex boot pair 6.00a2 and 3.2a1 HBAnywhere

Blade Interconnects

Virtual Connect-Ethernet and Virtual Connect-Fibre Channel

Cisco Ethernet switches outside encl. (65xx, 29xx, 37xx) and internal to enclosure

Shared Boot Storage: Boot and Data LUNs

HP MSA 1xxx; MSA 2000

HP EVA 4/6/8000; EVA LE

Operating Systems

Windows Server 2008 Standard

Windows Server 2008 Standard x64[2]

Windows Server 2008 Enterprise Windows Server 2008 Enterprise x64[2]

Windows Server 2008 Itanium-based (IA64)

Windows Server 2003 Standard SP2

Windows Server 2003 Standard SP2 x64[2]

Windows Server 2003 Enterprise SP2

Windows Server 2003 Enterprise SP2 x64[2]

Windows Server 2003 R2 Standard SP2

Windows Server 2003 R2 Standard SP2 x64[2]

Windows Server 2003 R2 Enterprise SP2

Windows Server 2003 R2 Enterprise SP2 x64[2]

Windows 2003 Datacenter IA64

Windows 2003 Enterprise IA64

HP-UX 11i v1 OE/AR 0412 or later[3]

HP-UX 11i v2 OE/AR 0409 or later[3]

HP-UX 11i v3 OE/AR 0709 or later[3]

Red Hat Enterprise Linux 5 for Intel Itanium

Red Hat Enterprise Linux 5 x86, Update 1[4]

Red Hat Enterprise Linux 5 AMD64/EM64T, Update 1[4]

Red Hat Enterprise Linux 4 for Intel Itanium

Red Hat Enterprise Linux 4 x86, Update 6[4]

Red Hat Enterprise Linux 4 AMD64/EM64T , Update 9[4]

Red Hat Enterprise Linux 3 x86, Update 9[4]

Red Hat Enterprise Linux 3 AMD64/EM64T, Update 9[4]

Red Hat Linux 9[4]

Red Hat Linux 8[4]

Red Hat Linux 7.3 Workstation[4]

SUSE Linux Enterprise Server 10 for Intel Itanium

SUSE Linux Enterprise Server 10 x86, SP1[4]

SUSE Linux Enterprise Server 10 AMD64/EM64T, SP1[4]

SUSE Linux Enterprise Server 9 for Intel Itanium

SUSE Linux Enterprise Server 9 x86, SP4[4]

SUSE Linux Enterprise Server 9 AMD64/EM64T, SP4[4]

SUSE Linux Enterprise Server 8/UL 1.0[4]

Virtualization Platforms

VMware ESX 3.0.1 guest running a supported operating system (x86 Windows, x86 Linux)[5]

VMware ESX 3.0.2 guest running a supported operating system (x86 Windows, x86 Linux)[6]

VMware ESX 3.5 Update 1 guest running a supported operating system (x86 Windows, x86 Linux)[7]

Integrity VM guest running a supported operating system (HP-UX, Integrity Windows, Integrity Linux)

Microsoft Virtual Server 2005 R2 SP1

Other Requirements

Virtual Connect v1.24

iLO2 1.5

Onboard Administrator 2.20

HP WBEM Services for HP-UX: A.02.00 minimum required; A.02.05 or higher recommended for security and performance improvements.

Pegasus 2.5 required for Integrity Linux.

WMI Mapper for Integrity Windows v2.4.1.0 required for Integrity Windows managed nodes.

HP-UX Secure Shell (SSH) A.04.40 or higher.

Utilization Provider (for Windows managed nodes)

The Utilization Provider is required on all VSE managed systems. It provides utilization data for Virtualization Manager and Capacity Advisor.

Microsoft Windows requires version A.01.07 or later.

Additional Requirements for Managing HP Integrity SystemsIf you intend to manage HP Integrity systems from a Windows CMS, see Table 6 for additional agent and provider requirements for the managed systems.

[1] Logical servers are only support c-Class blades (with Virtual Connect) and 300/500/700 series DL/ML with ESX.

[2] Utilization Provider and vseassist run in 32-bit mode on these systems.

[3] Memory patch PHSS_33349 must be installed in order to use Virtualization Manager and Capacity Advisor.

[4] These systems have the following limitations:

  • Supported on x86 only (not supported on Integrity).

  • Standalone ML/DL servers: display only, no data collection, no meters.

  • Blade (BL) servers: display only, no data collection, no meters, logical server movement is supported.

  • Vmware Linux guests: data and display through VMM, logical server movement is supported.

[5] Logical server operations are not supported on VMware ESX 3.0.1 systems.

[6] VMware Virtual Center 2.0 is required for logical server operations on an ESX 3.0.2 guest.

[7] VMware Virtual Center 2.5 Update 1 is required for logical server operations on an ESX 3.5 Update 1 guest.

 



VSE Management Software Version 4.0 Support Matrix
  		 


HP-UX CMS Requirements  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.