Monitoring of VMware-based PRIMERGY Servers with ServerViewmanuals.ts.fujitsu.com/file/10346/sv-esxi-cim-support-en.pdf · User Guide - English FUJITSU Software ServerView Suite Monitoring

User Guide - English

FUJITSU Software ServerView Suite

Monitoring of VMware-based PRIMERGY Servers with ServerView VMware vSphere Hypervisor (ESXi - V4.0 and V4.1)

Edition February 2018

Comments… Suggestions… Corrections…The User Documentation Department would like toknow your opinion of this manual. Your feedback helpsus optimize our documentation to suit your individual needs.

Feel free to send us your comments by e-mail to [email protected].

Certified documentation according to DIN EN ISO 9001:2008To ensure a consistently high quality standard anduser-friendliness, this documentation was created tomeet the regulations of a quality management system which complies with the requirements of the standardDIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

Copyright and TrademarksCopyright 2011 FUJITSU LIMITED

All rights reserved.Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

mailto:[email protected]

http://www.cognitas.de

Contents

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Target groups and purpose of this manual . . . . . . . . . . . 8

1.2 Documentation for ServerView Suite . . . . . . . . . . . . . . 8

1.3 Notational conventions . . . . . . . . . . . . . . . . . . . . . 9

2 Functionality and architecture . . . . . . . . . . . . . . . . . 11

2.1 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Event Management . . . . . . . . . . . . . . . . . . . . . . . 132.2.1 Alarm management with ServerView . . . . . . . . . . . . . . 142.2.2 Alarm management for iRMC . . . . . . . . . . . . . . . . . . 14

2.3 Power management . . . . . . . . . . . . . . . . . . . . . . 15

2.4 Update management . . . . . . . . . . . . . . . . . . . . . . 15

2.5 RAID management . . . . . . . . . . . . . . . . . . . . . . . 16

2.6 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.6.1 VMware vSphere . . . . . . . . . . . . . . . . . . . . . . . . 172.6.2 VMware vSphere and CIM . . . . . . . . . . . . . . . . . . . . 172.6.3 Hardware management with CIM . . . . . . . . . . . . . . . . 17

3 Using the Fujitsu ServerView solution . . . . . . . . . . . . 19

3.1 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1.1 VMware vSphere-based servers in the server list . . . . . . . . 193.1.2 Querying server data . . . . . . . . . . . . . . . . . . . . . . 213.1.2.1 Querying information about the VMware vSphere host . . . 213.1.2.2 Querying information about the virtual machines . . . . . . 223.1.3 Management via iRMC . . . . . . . . . . . . . . . . . . . . . 23

3.2 Power management . . . . . . . . . . . . . . . . . . . . . . 23

3.3 Event Management . . . . . . . . . . . . . . . . . . . . . . . 24

3.4 RAID management . . . . . . . . . . . . . . . . . . . . . . . 24

Contents

3.5 Local Update Management . . . . . . . . . . . . . . . . . . . 253.5.1 Current BIOS/firmware/driver versions and Update DVD . . . . . 253.5.2 Booting the server from the ServerView Suite DVD 1 and starting

Update Manager Express . . . . . . . . . . . . . . . . . . . . . 253.5.3 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4 Software provision and licensing . . . . . . . . . . . . . . . 27

4.1 System image including Fujitsu CIM providers . . . . . . . . 284.1.1 Order with a new PRIMERGY server - Embedded VMware vSphere

Hypervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.1.2 Download from the Fujitsu website . . . . . . . . . . . . . . . . 284.1.3 Download from the VMware website . . . . . . . . . . . . . . . 28

4.2 Fujitsu CIM providers (individual component): . . . . . . . . 294.2.1 Download from the ServerView Suite DVD 1 . . . . . . . . . . . 294.2.2 Download from the Fujitsu website . . . . . . . . . . . . . . . . 29

4.3 Licensing the software . . . . . . . . . . . . . . . . . . . . . 304.3.1 License for ServerView Suite . . . . . . . . . . . . . . . . . . . 304.3.2 License for VMware vSphere . . . . . . . . . . . . . . . . . . . 30

5 Requirements - Installing and Updating . . . . . . . . . . . . 33

5.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 335.1.1 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . 335.1.2 Software requirements . . . . . . . . . . . . . . . . . . . . . . 335.1.2.1 Requirements: ServerView Operations Manager . . . . . . . 345.1.2.2 Requirements: VMware vSphere . . . . . . . . . . . . . . . 345.1.2.3 Requirements: ServerView RAID Manager . . . . . . . . . . 365.1.2.4 Requirements: ServerView Event Manager . . . . . . . . . . 375.1.2.5 Requirements: iRMC monitoring function . . . . . . . . . . . 37

5.2 Installing components for managing VMware vSphere-based servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.2.1 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . . 385.2.2 Installing ServerView Operations Manager . . . . . . . . . . . . 395.2.3 Installing and configuring ServerView RAID Manager . . . . . . 395.2.4 Installing VMware vSphere . . . . . . . . . . . . . . . . . . . . 41

Contents

5.2.5 Configuring VMware vSphere . . . . . . . . . . . . . . . . . . 435.2.5.1 Creating the administrator password and configuring the default

network behaviour . . . . . . . . . . . . . . . . . . . . . . 445.2.5.2 Enabling use of Fujitsu CIM providers . . . . . . . . . . . . 445.2.5.3 Additional Settings . . . . . . . . . . . . . . . . . . . . . . 455.2.5.4 Setting up user ID for ServerView on VMware vSphere-based

server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.2.6 Configuring the iRMC trap destination . . . . . . . . . . . . . . 465.2.7 Configuring ServerView Operations Manager . . . . . . . . . . 485.2.7.1 Configuring ServerView Operations Manager to query data of

Fujitsu CIM providers . . . . . . . . . . . . . . . . . . . . . 485.2.7.2 Configuring ServerView Operations Manager to support the

iRMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.3 Subsequently installing or updating Fujitsu CIM providers as an individual component . . . . . . . . . . . . . . . . . . . . . 49

6 Security issues . . . . . . . . . . . . . . . . . . . . . . . . . 51

Contents

ServerView Operations Manager 7

1 Overview

Virtualization solutions from Fujitsu

Fujitsu is committed to total virtualization - from servers to storage to networks - and to virtualization software and operation management tools. The partnership between VMware and Fujitsu brings you continuity of technology assets, more efficient resource use, and steps toward the elimination of IT complexity.

Fujitsu has considerable experience in developing mainframe solutions and developing proprietary virtualization technologies, and now combines that experience and solutions with best in class partners like VMware to provide bundled solutions for servers, storage and network - this allows for speedy implementation of a proven, easy-to-use system with fast return on investment.

VMware and Fujitsu ServerView integrated virtualization support

VMware vSphere - also known as VMware ESXi -, is the Hypervisor, which is the industry standard in terms of reliability, performance and ecosystem support. VMware vSphere Hypervisor provides an easy introduction to the world of virtualization. The optimized RAM and CPU management in VMware vSphere enables you to execute up to twice as many virtual machines compared with the first generation of hypervisor solutions. Fujitsu PRIMERGY rack, tower and blade servers have been optimized to support VMware’s server virtualization technology since many years. All current-generation PRIMERGY server models from Fujitsu are tuned to deliver best results in performance, efficiency and reliability for VMware’s new cloud computing platform, providing a solid foundation stone for datacenter consolidation projects.

ServerView supports the CIM management standard, making it possible to monitor and manage VMware vSphere based environments more reliably and securely. Administrators can view all physical and virtual machines through a single interface, with automatic grouping of VMware vSphere hosts making adminstration simple.

ServerView Operations Manager is the server monitoring software where PRIMERGY servers and associated storage extension units in the network can be monitored and analyzed, and it includes VMware management. It automatically detects virtual machines (with ServerView-Agents) and shows the status of hosts and guests. This offers single point of console management and the advantage of ServerView Event Management for alerting.

8 ServerView Operations Manager

Target groups and purpose VMware vSphere

1.1 Target groups and purpose of this manual

This manual is intended for system administrators, network administrators and service technicians who already have a basic knowledge of hardware and software.

The manual provides you with the facility to monitor a VMware vSphere-based server with ServerView and with support of CIM providers. It describes the necessary steps of installation and configuration.

1.2 Documentation for ServerView Suite

The documentation for the ServerView Suite can be found on the ServerView Suite DVD 2 supplied with each server system.

The documentation can also be downloaded free of charge from the Internet. You will find the online documentation at http://manuals.ts.fujitsu.com under the link Industry standard servers.

http://manuals.ts.fujitsu.com


VMware vSphere Notational conventions

1.3 Notational conventions

The following notational conventions are used in this manual:

References to text or sections of text in this manual are shown with the chapter or section heading and the page on which that chapter or section begins.

Screen outputs

Please note that the screen output is dependent in part on the system used and therefore some details may not correspond exactly to the output you will see on your system. You may also see system-dependent differences in the menu items available.

V Caution This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment.

I This symbol highlights important information and tips.

Ê This symbol refers to a step that you must carry out in order to continue with the procedure.

italics Commands, menu items, names of buttons, options, variables, file names and path names are shown in italics in descriptive text.

fixed font Systems outputs are indicated using a fixed font.

fixed font semi-bold

Commands to be entered via the keyboard are written in a semi-bold fixed font.

<abc> Angle brackets are used to enclose variables which are to be replaced by actual values.

[Key symbols] Keys are shown according to their representation on the keyboard. If uppercase letters are to be entered explicitly, then the Shift key is shown, e.g. [SHIFT] - [A] for A. If two keys need to be pressed at the same time, this is shown by replacing a hyphen between the two key symbols.

Table 1: Notational conventions


Notational conventions VMware vSphere


2 Functionality and architecture

ServerView Operations Manager and Fujitsu CIM Provider

ServerView Operations Manager enables you to use the Fujitsu CIM provider to monitor VMware vSphere-based servers.

The Fujitsu CIM provider is either integrated into the Fujitsu VMware vSphere system image or as a stand-alone component for initial installation or for updating an existing CIM provider.

Additional information sources for ServerView Operations Manager for a VMware vSphere-based server are the ServerView RAID Manager and the iRMC monitoring function.

2.1 Monitoring

ServerView Operations Manager provides a browser-based console for managing the servers and representing the information determined. The managed servers are automatically displayed in a server list, which can be structured as required. Integrated grouping and filter options offer improved clarity, particularly in larger networks.

ServerView Operations Manager detects VMware vSphere-based servers with their network address, model, and operating system information. The virtual servers associated with the host server are displayed in the server list under the entry for the host server with their current VMware names. In addition, there are individual views in which you can query information about the host server and the virtual machines installed on it.

For monitoring purposes, the following information sources are evaluated:

– CIM-based using the Fujitsu CIM provider,

– Monitoring messages from iRMC, and

– Information from ServerView RAID Manager.


Monitoring Functionality and architecture

Figure 1: Monitoring of VMware vSphere-based servers with ServerView

Additional monitoring tools:

In addition to ServerView Operations Manager, an extended ServerView environment provides additional monitoring tools for monitoring a VMware vSphere Hypervisor-based server:

– The ServerView RAID Manager console for information from the RAID CIM provider

– The iRMC monitoring function for the iRMC monitoring data

ServerViewRAID

ServerViewOpsMgr.

CMS

Raid traps

CIM providerSV -Raid

CIM providerServerView

RAID-ctrl.

DVD

PRIMERGYServer

iRMC

HW-events

VM 1 VM ... VM n

ESXiHypervisor

updateconsole

Update Manager Express

managed server


Functionality and architecture Event Management

2.2 Event Management

The configurable alarm system in ServerView Event Manager ensures that reliable information about faults that occur is available rapidly. This results in a targeted response: System messages are detected, evaluated, filtered, forwarded and saved.

Figure 2: Event Management of VMware vSphere-based servers with ServerView (up to V5.3)

ServerView Event Manager integrates the following components into ServerView Operations Manager:

Alarm Monitor:In the ServerView Operations Manager main window, the alarms for the selected servers are displayed.

Alarm Configuration:You can configure settings for handling alarms: Alarm rules, filter rules, and general settings.

ServerView RAID Manager evaluates the iRMC messages and the CIM-based messages recorded.

ServerViewRAID

ServerViewOpsMgr.

CMS

Raid traps



RAID-ctrl.

DVD

PRIMERGYServer

iRMC

HW-events

VM 1 VM ... VM n

ESXiHypervisor

updateconsole


managed server

HW-events


Event Management Functionality and architecture

2.2.1 Alarm management with ServerView

In order to be able to communicate with a server using VMware vSphere, ServerView RAID Manager logs in as as "subscriber" on the Small Footprint Code Broker (SFCB - CIMOM), which is part of VMware vSphere (1). This login qualifies ServerView RAID Manager to receive messages about defined events from VMware vSphere from now on.

Figure 3: CIM-based information in ServerView alarm management

The CIMOM (SFCB) informs the CIM provider which events messages are required for under the new subscription (2).

The CIM provider uses hardware-related protocols to monitor the server infrastructure (3). It converts the data identified into specific messages and forwards these to the CIMOM (SFCB) (4).

On the ServerView RAID Manager side, the indication notifications reach the CIM listener (5) via the CIM/XML protocol, which then forwards the event messages to the alarm manager (6).

2.2.2 Alarm management for iRMC

As an autonomous system on the system board of a current PRIMERGY server, the iRMC features independent alarm management. This alarm management enables you to configure how an alarm is forwarded to ServerView Operations Manager.

If this SNMP trap forwarding is enabled, the iRMC sends traps to the ServerView alarm management.


Functionality and architecture Power management

2.3 Power management

As well as power management for the physical hose server, ServerView Operations Manager provides power control functions for the virtual machines that are installed on it.

Power management in ServerView Operations Manager is utilized by selecting the relevant server from the server list. The functions available (for example, Power ON, Power OFF, Shutdown) can be used on both physical servers and virtual servers.

2.4 Update management

Figure 4: Update Management of VMware vSphere-based servers with ServerView

ServerView Update Manager Express enables you to update the BIOS and firmware for various sever components on VMware vSphere-based PRIMERGY servers.

When updating, Update Manager Express relies on self-extracting and self-installing software packages, known as Autonomous Support Packages (ASPs) for the BIOS and firmware.

ServerViewRAID

ServerViewOpsMgr.

CMS

Raid traps



RAID-ctrl.

DVD

PRIMERGYServer

iRMC

HW-events

VM 1 VM ... VM n

ESXiHypervisor

uconsole


managed server

update consoleUpd. Mgr. Express


RAID management Functionality and architecture

You can boot a VMware vSphere-based server from the ServerView suite DVD 1 and then install or update current firmware or the BIOS using ServerView Update Manager Express.

In the period between two successive editions of the ServerView suite DVD 1, Fujitsu continuously provides updated versions of BIOS/firmware/drivers, Update Manager Express and ASPs on the Internet.

2.5 RAID management

ServerView RAID Manager allows you to monitor and manage all RAID controllers installed in PRIMERGY servers centrally and based on CIM. ServerView RAID Manager forwards its information, so that you can access it using the ServerView Operations Manager interface.

Figure 5: RAID Management of VMware vSphere-based servers with ServerView

In addition, ServerView RAID Manager has its own graphical interface and a command line interface. To manage VMware vSphere-based servers, ServerView RAID Manager is installed on the central management station.

ServerViewRAID

ServerViewOpsMgr.

CMS

Raid traps



RAID-ctrl.

DVD

PRIMERGYServer

iRMC

HW-events

VM 1 VM ... VM n

ESXiHypervisor

updateconsole


managed server


Functionality and architecture Architecture

2.6 Architecture

2.6.1 VMware vSphere

VMware vSphere is the new name for the VMware hypervisor. VMware vSphere is delivered as a single ISO image or is preinstalled on PRIMERGY servers. A VMware license is used to enable the different features on the various VMware vSphere editions. An upgrade of those editions is possible by entering the relevant license key without the need to install or upgrade the image.

2.6.2 VMware vSphere and CIM

VMware vSphere is available in two different architectures called ESX and ESXi. While ESX is delivered with a service console, which allows the installation of ServerView agents, ESXi contains only the hypervisor without the service console.

Management tasks for ESXi are performed using a remote command line interface, a Web interface or the VMware vSphere Client.

For interaction with ServerView ESXi has been equipped with CIM providers, which comply with system management standards.

2.6.3 Hardware management with CIM

With the Common Information Model (CIM) the Distributed Management Task Force (DMTF) devised an object-oriented standard for management information in IT environments, which defines the description of the managed units, their construction and their relationships with one another. Object orientation makes CIM a comparatively powerful model, which can handle classes, inheritance and relationship concepts, object paradigms and methods. When implemented, CIM and WBEM use an infrastructure consisting of CIM Object Manager (CIMOM) and CIM providers:

CIMOM is the central software component that receives and processes WBEM queries. CIMOM knows which classes exist and which system components they correspond to. To keep CIMOM as flexible as possible, it does not access the managed system resources directly. Instead, WBEM makes use of a modular concept, with a CIM provider used for each instance of a class.


Architecture Functionality and architecture

Thus, a CIM provider is a software component that allows management access to device drivers and hardware components. Conceptually, these providers specialize in a particular management task and are designed for as small a range of programs as possible.

CIMOM forwards external queries, e.g. from management software, to the CIM providers and/or collates their information and returns the result to the requesting application using standard APIs.


3 Using the Fujitsu ServerView solution

Comprehensive monitoring and management of VMware vSphere-based servers is possible with the Fujitsu ServerView solution for VMware. This chapter describes the key processes for central monitoring and management using ServerView Operations Manager. It also makes reference to other functionalities of the individual solution components.

3.1 Monitoring

ServerView Operations Manager provides a browser-based console for managing the servers and representing the information determined. The managed servers are displayed in a server list, which can be structured as required. Integrated grouping and filter options offer improved clarity, particularly in larger networks.

3.1.1 VMware vSphere-based servers in the server list

ServerView Operations Manager detects VMware vSphere-based servers with their network address, model, and operating system information. The virtual servers associated with the host server are displayed in the server list under the entry for the host server with their current VMware names in the Name column.

Status of VMware vSphere server and query options

In the server list the status of the CIM providers on the VMware vSphere host is displayed in the form of an icon before the VMware vSphere host:

OK: The connection to the VMWare vSphere server is established, and the host has the status OK.

You can open SingleSystemView for this VMware vSphere server -refer to "Querying server data" on page 21.

Table 2: VMware vSphere server icons in the ServerList window


Monitoring VMware vSphere

Management Controller mode: No connection can be established to the CIM providers on the VMware vSphere server. But a valid IP address and a valid user ID are available for the iRMC of the VMware vSphere server.

You can open the iRMC's Web interface -refer to "Management via iRMC" on page 23.


Management not possible: No connection can be established to the CIM providers on the VMware vSphere server.The VMware vSphere server may be switched off or is unavailable as no valid user/password combination was given -refer to "Configuring ServerView Operations Manager to query data of Fujitsu CIM providers" on page 48. It is also possible that the CIM providers do not respond to the host or the iRMC is either not configured or does not respond-refer to "Configuring ServerView Operations Manager to support the iRMC" on page 49.


Unknown: The VMware vSphere server is not available via the network.



VMware vSphere Monitoring

3.1.2 Querying server data

In addition to the information in the server list, there are individual views (SingleSystemView), in which you can query information about the VMware vSphere host server and the virtual machines installed on it.

Opening SingleSystemView for a VMware vSphere server:

Ê In the server list click VMware vSphere host.

This will open SingleSystemView for the CIM providers on this VMware vSphere server.

SingleSystemView for the CIM providers of a VMware vSphere server

The SingleSystemView window allows you to query detailed information about the VMware vSphere server selected.

This window consists of different areas. Some areas can be expanded and collapsed as required. At the bottom left of this window Information/Operation has menus for further information and operations.For more information about all these options refer to the manual "ServerView Operations Manager V5.0. Server Management".

3.1.2.1 Querying information about the VMware vSphere host

You can find the Virtualization menu under Information/Operation at the bottom left of the SingleSystemView window.

The view Virtualization Overview offers a brief explanation of the menu items.

You can use the menu item Host Properties for more information about the VMware vSphere host:

– status– server identification data– hardware data– virtualization software– operating system information


Monitoring VMware vSphere

3.1.2.2 Querying information about the virtual machines

You can find the Virtualization menu under Information/Operation at the bottom left of the SingleSystemView window.

You can use the menu item Virtual Machines for more information about the virtual machines on the VMware vSphere server. All virtual machines are listed on the left in the tree structure. On the right there is a list of all virtual machines of the VMware vSphere host selected in the server list. The table contains the following columns:

Column with checkboxesSelect the virtual machine by checking the box.

StatusStatus of virtual machine

NameName of virtual machine

Power StatePower state of virtual machine

NetworkNetwork name of virtual machine

OSInstalled operating system

OS DescriptionDescription of the installed operating system

Click the name of a virtual machine in the table or tree structure to access the individual view for this virtual machine. This individual view contains detailed information about the virtual machine selected.


VMware vSphere Power Management

3.1.3 Management via iRMC

iRMC has its own operating system, acts as a Web server, and provides its own Web interface, which offers another comprehensive monitoring tool.

Detailed information is available in the chapter "iRMC Web interface" in the manual "ServerView Suite - iRMC".

If the ServerView Operations Manager has the iRMC's address of an VMware vSphere host server, you can double-click the ESXi host server list to open the iRMC's Web interface.

I In the case of a VMware vSphere Hypervisor V4.1 system or a VMware vSphere Hypervisor V4.0 system with patch 4 ServerView Operations Manager automatically detects the iRMC's IP address of a VMware vSphere Hypervisor host server.

Without patch 4 installed the IP address has to be configured manually. For details refer to the manual "ServerView Suite. ServerView Operations Manager", section "Server list".

3.2 Power management

I For security reasons the use of these functions is linked to integrated User Management- refer to "Configuring ServerView Operations Manager to query data of Fujitsu CIM providers" on page 48.

You can use ServerView Operations Manager to switch the virtual server on a VMware vSphere-based server on and off

Ê Open the view Virtual Machine - refer to "Querying information about the virtual machines" on page 22.

Ê Select the virtual machines in the list. Do this by clicking the checkbox next to the virtual machines you require.

Ê Then click the appropriate button:

StartSwitches the virtual machine on.

StopSwitches the virtual machine off.


Event Management VMware vSphere

SuspendTemporarily stops the virtual machine.

ResumeRestarts the virtual machine last suspended.

The individual buttons are enabled/disabled depending on the status of the virtual machines.

3.3 Event Management

The configurable alarm system in ServerView Event Manager ensures that reliable information about faults that occur is available rapidly. This results in a targeted response: System messages are detected, evaluated, filtered, forwarded and saved. The components of ServerView Event Manager are incorporated in the ServerView Operations Manager interface.

For detailed information about the range of functions and use of ServerView Event Manager refer to the manual "ServerView Event Manager".

3.4 RAID management

ServerView RAID Manager forwards its information so that you can access it using the ServerView Operations Manager interface. ServerView RAID Manager also has its own graphical interface and a command line interface.

For detailed information about the range of functions and use of ServerView RAID Manager refer to the manual "RAID Management".


VMware vSphere Local Update Management

3.5 Local Update Management

With Update Manager Express from the PRIMERGY ServerView Suite, you can install firmware and BIOS of the various server components on the current PRIMERGY server.

If VMware vSphere is installed on your PRIMERGY server, you can boot the server from the ServerView Suite DVD 1 and then install the firmware an/or BIOS with the help of Update Manager Express.

BIOS/firmware are installed locally on the server on which Update Manager Express is started.

3.5.1 Current BIOS/firmware/driver versions and Update DVD

The current versions of BIOS, firmware and drivers (and of the ASPs and Update Manager Express) for your PRIMERGY server are available on the ServerView Suite DVD 1, the latest version of which is issued approx. every two months. An updated version of the ServerView Suite DVD 1, which contains the latest versions of BIOS, firmware and drivers, is issued once every two months or so.

3.5.2 Booting the server from the ServerView Suite DVD 1 and starting Update Manager Express

I If your server does not automatically restart after completing BIOS/firmware installation, you can boot it by specifically closing Update Manager Express.

I If you boot the server from the ServerView Suite DVD 1, use a USB memory stick to back up the log file.

Starting Update Manager Express from the ServerView Suite DVD 1

Proceed as follows:

Ê Switch on the server.

Ê Place the current ServerView Suite DVD 1 in your server's DVD-ROM drive.


Dokumentation Update Management

Ê Reboot the server, e.g. by pressing the reset button on the front or switching the server off and then on again after a few seconds.

Ê Once the server is started, press [F2] (BIOS setup) or [F12] (boot menu).

Ê In the BIOS setup / boot menu, change the boot sequence to "Boot from CD".

While booting the server from the ServerView Suite DVD 1, Installation Manager will prompt you to select the required interface language.

Ê Select the required interface language.

Ê In the Installation Manager start screen, select the option Update Mgr Express Mode.

Ê Click Continue.

The Update Manager Express main window is displayed.

3.5.3 Documentation

For detailed information about Update Manager Express refer to the manual "ServerView Suite. Local System Update of PRIMGERY Servers".


4 Software provision and licensingYou receive the Fujitsu CIM providers either integrated into the Fujitsu VMware vSphere system image or as an individual component for initial installation and upgrades.

You can obtain the required software components in the following ways:

System imageincluding Fujitsu CIM providers

– Order with a new PRIMERGY server

– Download from the Fujitsu website

– Download from the VMware website

Fujitsu CIM providers (individual component)

– Download from the ServerView Suite DVD 1

– Download from the Fujitsu website


Provision/ licensing VMware vSphere

4.1 System image including Fujitsu CIM providers

4.1.1 Order with a new PRIMERGY server - Embedded VMware vSphere Hypervisor

"Embedded VMware vSphere Hypervisor" is available as an option for certified PRIMERGY servers. Because of the short access times, the system is available immediately after starting up.

4.1.2 Download from the Fujitsu website

Ê The ISO image of the Fujitsu ESXi Custom Image can be found on the Fujitsu website at:

http://ts.fujitsu.com/support/downloads

Ê Select the required PRIMERGY model.

Ê Select VMwareas the operating system.

Ê Select the required VMware edition.

Ê Follow the instructions to download.

4.1.3 Download from the VMware website

Ê The ISO image of the Fujitsu Customized Installer CDs can be found on the VMware website at:

http://www.vmware.com – Support & Downloads – Download vSphere Hypervisor (ESXi) – Drivers & Tools – OEM Customized Installer CDs – VMware ESXi 4.x - Fujitsu Customized Installer CDs



VMware vSphere Provision/ licensing

4.2 Fujitsu CIM providers (individual component):

4.2.1 Download from the ServerView Suite DVD 1

Ê The installation package for the ServerView ESXi CIM provider can be found on the ServerView Suite DVD 1 under:

ServerView – Agents and Providers – Linux and VMware


4.2.2 Download from the Fujitsu website

Ê The installation package for the ServerView ESXi CIM provider can be found on the Fujitsu website at:

http://ts.fujitsu.com/support/downloads

Ê Select the required PRIMERGY model.

Ê Select VMwareas the operating system.

Ê Select the required VMware Embedded edition.

Ê Select the Server Management software.

Ê Select the ServerView - ESXI CIM provider.

Ê Select the required installation package and follow the instructions to download.



4.3 Licensing the software

Licenses for VMware vSphere are available from Fujitsu or from VMware.

4.3.1 License for ServerView Suite

The Fujitsu CIM providers are subject to the general terms and conditions of business from the software usage and service agreement with Fujitsu.

The ServerView Suite is a licensed software component of the PRIMERGY server hardware. It may only be used with hardware, software, or services from Fujitsu.

The terms of the end user license agreement for the ServerView Suite, regulating copying and distribution of the software to third parties, must be complied with.

Further information can be found in the end user license agreement (EULA) on ServerView Suite DVD 1 or at http://ts.fujitsu.com.

4.3.2 License for VMware vSphere

VMware vSphere includes a variety of functions whose availability depends on the license for the relevant vSphere edition. VMware currently supplies the following editions (in increasing order of the range of functions):

Edition Target group Privileges

VMware vSphere Standard Entry-level version Write privileges

VMware vSphere Advanced(will be not anymore available with vSphere 5)

For commercial use Write privileges

VMware vSphere Enterprise With additional features for cost reduction, downtime minimization and automation

Write privileges

Table 6: VMware vSphere editions


VMware vSphere Provision/ licensing

I From Version 3.5 Update 4, for ESXi/VMware vSphere with a free license, VMware has restricted write privileges to a VMware vSphere-based server. This means that various functions are not available - including starting and stopping virtual machines or correctly displaying the status of the VMware vSphere-based host. If you are using VMware vSphere with a free license, you must switch to a version with a paid license.

Further information can be found at:http://www.vmware.com – Products – Datacenter Products – VMware vSphere

VMware vSphere Enterprise Plus Ideal solution for cloud computing

Write privileges

Edition Target group Privileges

Table 6: VMware vSphere editions




5 Requirements - Installing and Updating

5.1 Requirements

5.1.1 Hardware requirements

You can find a list of the PRIMERGY systems supported on the Fujitsu website at:

Ê Enter the following Web address:ts.fujitsu.com/products/standard_servers/server_solutions/vmware.htm

Ê You can find an up-to-date file listing the PRIMERGY systems supported using the link Released operating systems.

5.1.2 Software requirements

ServerView Operations ManagerVersion 5.00.06With this version or higher VMware vSphere servers monitored via CIM providers are displayed in the ServerList of ServerView Operations Manager.For information about using lower versions refer to the manual "VMware ESXi - Monitoring VMware ESXi systems with ServerView Suite".

VMware vSphereVersion 4.0 or 4.1Monitoring via CIM providers is possible with these versions.For information about using lower versions (at least for ESXi 3.5) refer to the manual "VMware ESXi - Monitoring VMware ESXi systems with ServerView Suite".


Requirements VMware vSphere

ServerView RAID ManagerVersion 4.5.0 or higherServerView RAID Manager has to be installed on the same physical computer as the central management station of ServerView Operations Manager.For information about using lower versions refer to the manual "VMware ESXi - Monitoring VMware ESXi systems with ServerView Suite".

ServerView Event Managerparallel to ServerView Operations Manager

iRMC monitoring functionno restrictions in terms of version

5.1.2.1 Requirements: ServerView Operations Manager

The current software and hardware requirements for ServerView Operations Manager are available in the manual "ServerView Suite. ServerView Operations Manager".

5.1.2.2 Requirements: VMware vSphere

The latest hardware and system resource requirements for VMware ESXi are available in the VMware manual "Getting Started with ESXi" or "ESXi Installable and vCenter Server Setup Guide".

I If you wish to use VMware vSphere 4.0 and analyze the iRMC traps:With patch 4 installed ServerView Operations Manager can automatically detect the iRMC's IP address of an VMware vSphere-host server. Once the IP address has been detected, you can double-click the VMware vSphere-host server in the server list in order to open the Web interface of its iRMC. Without patch 4 installed the IP address has to be configured manually. For details refer to the manual "ServerView Suite. ServerView Operations Manager", section "Server list".


VMware vSphere Requirements

The latest hardware requirements for VMware vSphere 4.0 (as at October 2009) are provided below:

– Supported server platform -refer to the VMware Compatibility Guide:

as database at:http://www.vmware.com/resources/compatibility

as PDF file at:http://partnerweb.vmware.com/comp_guide/pdf/vi_systems_guide.pdf

– Server with x86 CPU in 64-bit mode(64-bit-processors: AMD Opteron processors, Intel Xeon processors (series 3000/3200, 3100/3300, 5100/5300, 5200/5400, 7100/7300, 7200/7400, Intel Nehalem processors)

– At least 2 GB RAM

– One or more gigabits or a 10Gb Ethernet controller (refer to the VMware Compatibility Guide)

– One or more of the following controllers (all combinations possible):SCSI-Basic controller (Adaptec Ultra-160/ Ultra-320, LSI Logic Fusion-MPT, most NCR/Symbios SCSI controllers);RAID controller (Adaptec RAID, LSI MegaRAID, LSI IME oder IBM (Adaptec) ServeRAID controller)

– SCSI hard disk or local RAID-LUN with a non-partitioned area for virtual machines

– Serial ATA (SATA)- the hard disk must be connected via supported SAS controllers or supported on-board SATA controllers


Requirements VMware vSphere

5.1.2.3 Requirements: ServerView RAID Manager

The latest resource requirements for ServerView RAID Manager are available in the manual "User Manual. ServerView RAID Manager". The latest requirements for ServerView RAID Manager (as at October 2009) are provided below:

– At least 35 MB disk space, additional disk space for the log files

– For some Linux destributions, you must install additional 32-bit software packages:CentOS: compat-libstd++-33-3.2.3-61.rpm.

– A network configuration that allows you to use a DNS or the host database to determine the IP address belonging to the server name

Requirements for using ServerView RAID Manager to monitor a VMware vSphere-server:

– Al least VMware vSphere 3.5 with Update 3

– LSI MegaRAID/ LSI IME controllerUp to version 4.1 VMware vSphere supports only LSI MegaRAID controllers for management purposes. As of version 4.1 VMware vSphere supports LSI IME-Controller.

– If you are using a ServerView RAID Manager version < V4.5.0:Installation on one of the following Linux derivatives as a guest operating system:Linux CentOS 5.1/2/3/4 or 5.1/2/3/4 EM64T, Linux RedHat EL5 U3 or EL5 U3 EM64T, Linux SLES 10 SP3/ SLES 10 SP3 EM64T/ SLES 11/ SLES 11 EM64T

I If you are using a ServerView RAID Manager version < V4.5.0, ServerView RAID Manager can only ever monitor the VMware vSphere-server on which it has been installed and on which the virtual Linux machine is running.We recommend that you install a virtual machine with this constellation on every VMware vSphere-server.

As of version 4.5.0, ServerView RAID Manager monitors up to 128 VMware vSphere-servers from a central management station.


VMware vSphere Requirements

5.1.2.4 Requirements: ServerView Event Manager

The components of ServerView Event Manager are incorporated in the ServerView Operations Manager interface - the requirements for ServerView Operations Manager apply accordingly (refer to"Requirements: ServerView Operations Manager" on page 34).

5.1.2.5 Requirements: iRMC monitoring function

I If you wish to use VMware vSphere 4.0 and analyze the iRMC traps:With patch 4 installed ServerView Operations Manager can automatically detect the iRMC's IP address of an VMware vSphere-host server. Once the IP address has been detected, you can double-click the VMware vSphere-host server in the server list in order to open the Web interface of its iRMC. Without patch 4 installed the IP address has to be configured manually. For details refer to the manual "ServerView Suite. ServerView Operations Manager", section "Server list".

In your network:

– Your network must have a DHCP server.

– If you want to use a symbolic name (instead of an IP address) to log on to the iRMC S2 Web interface, the DHCP server in your network must be configured for a dynamic DNS.

– A DNS must be configured. Otherwise, you mus obtain the IP address.

[At a remote workstation:

– Windows: Internet Explorer as of version 6.x;Linux: Mozilla Firefox 1.5.

– For a console redirect:Sun Java Virtual Machine 1.5.0_06 or higher.]


Installation VMware vSphere

5.2 Installing components for managing VMware vSphere-based servers

This section describes only those installation and configuration steps required for the purposes of this manual, while the relevant specialist literature and VMware documentation contain detailed information about installing and configuring virtual machines and their hosts.

5.2.1 Installation steps

See below for a description of the installation steps required to monitor a VMware vSphere-based server via ServerView using the Fujitsu CIM providers.

Other information sources can also be incorporated here: information from ServerView RAID Manager and iRMC.

Brief overview of the installation steps:

1. Install ServerView Operations Manager (including ServerView Event Manager) on the central management station

2. Install ServerView RAID Manager on the central management station and configure

3. Install VMware vSphere (or Fujitsu CIM providers as individual component - refer to"Subsequently installing or updating Fujitsu CIM providers as an individual component" on page 49)

4. Configure VMware vSphere

– Administrator password and default network behavior

– Enable Fujitsu CIM providers

– Set up user ID for ServerView

5. Configuring the iRMC trap destination

6. Configure ServerView Operations Manager to support

– query data of Fujitsu CIM providers

– of iRMC


Installation Installing ServerView Operations Manager

5.2.2 Installing ServerView Operations Manager

For detailed information about installing ServerView Operations Manager and ServerView Event Manager refer to the manuals "ServerView Suite. ServerView Operations Manager. Installation under Linux" and "ServerView Suite. ServerView Operations Manager. Installation under Windows".

5.2.3 Installing and configuring ServerView RAID Manager

Requirement

I ServerView RAID Manager has to be installed on the same physical computer as the central management station of ServerView Operations Manager.

Installing ServerView RAID Manager

For detailed information about installing ServerView RAID Manager refer to the manual "Manual.ServerView RAID Manager".

Configuring ServerView RAID Manager

ServerView RAID Manager requires connection information for VMware vSphere. The required configuration steps change between V4.2.8 and V4.3.6.

ServerView RAID Manager ≤ V4.2.8

Ê Open a console window on the virtual machine.

Ê Navigate to the directory/opt/fujitsu/ServerViewSuite/RAIDManager/bin.

Ê Open the filepiLSIStoreLibCIM.ini.


Installing ServerView RAID Manager Installation

Ê Configure the following settings. To do this, uncomment them (remove the leading semicolon) and use valid values:

I You must place path names or entries that contain blank characters or special characters between inverted commas (").

CIM_HOST = <host name of the VMware host>

CIM_HOST_PORT = 5989

CIM_HOST_USERID = <user name>

CIM_HOST_PASSWD = <password>

CIM_HOST_CERT = <optional: file path of host certificate>

CIM_CLIENT_CERT = <optional: file path of client certificate>

CIM_CLIENT_KEY = <optional: file path of client key file>

Ê Restart ServerView RAID Manager.

I You can configure specific settings to considerably improve performance in VMware vSphere (see "Additional Settings" on page 45).

ServerView RAID Manager as of V4.3.6In ServerView RAID Manager, you can use amCLIto add connection information. amCLI is the Command Line Interface for ServerView RAID Manager. You use it to create, delete or manage RAID associations from the command line or scripts. You can also use it to control ServerView RAID Manager. For more information, refer to the manual "ServerView RAID Manager".

Ê Open a console window on the virtual machine.

Use amCLIto add the connection information.For example:

amCLI -e 21/0 add_server name=<server name|IP-address> port=5989 username=<user name> password=<password>

This command adds a new server with the name esxi_1to the ServerView RAID Manager configuration. When the connection to this machine is set up, the port 5989,the user name <user name> and the password <password> are used. The password is stored encrypted.


Installation Installing VMware vSphere

Under VMware vSphere the usual method is to connect to the CIMOM with this information via an https connection on port 5989.

If you want to connect to the CIMOM via an http connection on port 5988, you can change the connection information with the following command:

amCLI -e 21/0 modify_server name=<server name|IP-address> port=5988

You use the following command to delete the connection information from the configuration file:

amCLI -e 21/0 delete_server name=<server name|IP-address>

I You can add more than one server to the configuration. However, if you are using a ServerView RAID Manager version < V 4.5.0, only the first entry is evaluated.

Ê Restart ServerView RAID Manager to make the configuration effective.

5.2.4 Installing VMware vSphere

You receive the Fujitsu CIM providers either integrated into the Fujitsu VMware vSphere system image or as an individual component for initial installation and upgrades. To learn how to obtain the necessary installation packages see "Software provision and licensing" on page 27.

Take note of the following:

I From Version 3.5 Update 4, for ESXi/VMware vSphere with a free license, VMware has restricted write privileges to a VMware vSphere-based server. This means that various functions are not available - including starting and stopping virtual machines or correctly displaying the status of the VMware vSphere-based host. If you are unsing VMware vSphere with a free license, you must switch to a version with a paid license -refer to "License for VMware vSphere" on page 30.

I This section describes only those installation and configuration steps required for the purposes of this manual, while the relevant specialist literature and VMware documentation contain detailed information about installing and configuring virtual machines and their hosts.


Installing VMware vSphere Installation

Installation

The latest step-by-step description of the installation is available in the VMware documentation at http://pubs.vmware.com/vsp40u1_i/.

The latest installation steps for VMwarevSphere /ESXi 4.0 (as at October 2009) are provided below:

Requirements

– You must set the server hardware clock to UTC (system BIOS).

– You must connect a monitor and keyboard to the server on which you will install the VMware vSphere software.

– You must disconnect the network storage connection. This will shorten the time required by the installation program to search for available hard disk drives.

– Never install VMware vSphere /ESXi Installable and VMware vSphere /ESXi Embedded on the same host.

Installing Vmware

Ê Boot from the installation CD.

The welcome screen is displayed.

Ê Follow the user prompts in preparation for the installation.

Ê Press F11to start the installation.

Ê When the installation is complete, remove the installation CD from the CD drive.

Ê Press Enter to restart the host.

Ê In BIOS, define the drive on which you have installed VMware vSphere Hypervisor as the start drive.



5.2.5 Configuring VMware vSphere

The latest step-by-step description of the installation is available in the VMware documentation at http://pubs.vmware.com/vsp40u1_i/.

VMware VMware vSphere interface options

VMware provides the following interface options

vSphere Web Access (free of charge)A Web interface that provides the basic configuration options for managing and configuring virtual machines. It also provides console access.The interface is installed on the VMware vSphere host.For detailed information about vSphere Web Access, see http://pubs.vmware.com/vsp40/.

vSphere Command-Line Interface (free of charge)A command line interface for configuring a VMware vSphere host.For detailed information about the vSphere command line interface, refer to "vSphere Command Line Interface Installation and Scripting Guide".

vSphere Client (subject to a fee)A convenient user interface (subject to a fee) for creating and managing virtual machines, their resources, and their hosts with console access to virtual machines.For detailed information about vSphere Web Access, see http://pubs.vmware.com/vsp40/.

The necessary configuration steps (for use with vSphere Web Access and vSphere CLI) are described below. For detailed information about a configuration that uses vSphere Client, refer to the documentation (see above).


Installing VMware vSphere Installation

The latest installation steps for VMwarevSphere /ESXi 4.0 (as at October 2009) are provided below:

Auto configuration phase

When you have installed and started VMware vSphere for the first time, the host starts the auto configuration phase. The system network and storage devices are configured with default values.

When the host has concluded the auto configuration phase, the direct console is called.

Ê To check the default configuration, press F2.

5.2.5.1 Creating the administrator password and configuring the default network behaviour

The administrative user name for the VMware vSphere host is Root. By default, the administrator password is not set.

Ê In the direct console, choose the option Configure Password and follow the user prompt.

DHCP defines the IP address, subnet mask, and default gateway by default. If your network does not have a DHCP server, manually configure the IP settings for VMware vSphere from the direct console:

Ê Choose the option Configure Management Network and press Enter.

Ê Choose the option IP Configuration and press Enter.

Ê Enter an IP address, subnet mask, and default gateway, and press Enter.

Ê Finally, press Enter to save the settings and exit the direct console.

5.2.5.2 Enabling use of Fujitsu CIM providers

Ê Open a command line.

Ê Navigate to the directory in which you installed vSphere CLI and run the following command:

vicfg-advcfg <conn_options> -s 1 UserVars.CIMsvsProviderEnabled

For detailed information about usage of the vSphere command line interface, refer to "vSphere Command Line Interface Installation and Scripting Guide".



5.2.5.3 Additional Settings

You can use the following settings in the configuration file /etc/scfb/sfcb.conf to considerably improve performance, especially for ServerView RAID Manager:

keepaliveTimeout = 10000

keepaliveMaxRequest = 10000

5.2.5.4 Setting up user ID for ServerView on VMware vSphere-based server

To allow ServerView Operations Manager to access the VMware vSphere-based server, a user (any) needs to be set up with Administrator rights for the object ESXi host on the VMware vSphere-based server.

I For security reasons you should not grant the root user the role of Administrator. Take note of further information about users, groups, authorizations and roles on a VMware vSphere-based server in the manual "Manual for Server Configuration for ESXi".

For more information about authentication and user management on a VMware vSphere host refer to the manuals "Manual for Server Configuration for ESXi" and "vSphere Command-Line Interface Installation and Reference Guide".

See below for a description of how to set up such identification using vSphere CLI:

Ê Open a command line.

Ê Navigate to the directory in which you installed vSphere CLI.

Ê Enter the following command:

vicfg-user.pl <conn_options> -e user -o add -l <User> -p <Password> -r administrator

For more information about storing user IDs in the User/Password list of ServerView Operations Manager see "Configuring ServerView Operations Manager to query data of Fujitsu CIM providers" on page 48.


Configuring the iRMC Installation

5.2.6 Configuring the iRMC trap destination

iRMC S2/S3 has its own operating system, acts as a Web server, and provides its own Web interface, which you can use to configure the trap destination for iRMC S2/S3:

I Detailed information is available in the "iRMC Web interface" chapter in the manual "ServerView Suite.Remote Management.iRMC S2/S3 - integrated Remote Management Controller".

Ê Open a Web browser.

Ê Enter the (configured) DNS name or the IP address of iRMC S2/S3.

The login screen is displayed.

Ê Enter the login data and confirm the entry.

The iRMC S2/S3 Web interface opens and the Overview page is displayed.

Ê In the navigation area, choose the entries Alerting – SNMP Traps.

The SNMP Trap Destinationpage opens. Here, you can view and configure the settings for the SNMP trap destination trap destination (SNMP alarm forwarding):

I SNMP traps can be forwareded to up to seven SNMP servers.


Installation Configuring the iRMC

Figure 6: Page for SNMP Trap Destination

SNMP CommunityName of the SNMP community

Ê Click Applyto apply the name of the community.

SNMP Server1 .. SNMP Server7 (trap destination addresses)DNS names or IP addresses of the servers that belong to this SNMP community and are to be configured as trap destinations.

Ê Click Applyto enable the SNMP server as a trap destination.

Ê Click Testto test the connection to the SNMP server.

Ê If necessary, click Applyto enable all settings.

Ê Close the browser window.


Configuring ServerView Operations Manager Installation

5.2.7 Configuring ServerView Operations Manager

5.2.7.1 Configuring ServerView Operations Manager to query data of Fujitsu CIM providers

In some cases ServerView Operations Manager needs a valid user ID in order to authenticate itself when querying information or performing operations on a managed server. User IDs are required for example to add virtual servers to the server list or to query server data via Fujitsu CIM providers.

Such user IDs on the VMware vSphere-based server must have Administrator rights.

In cases of authentication ServerView Operations Manager provides the option of storing user IDs in a User/Password list. The password is stored encrypted. ServerView Operations Manager will then search this list for a valid user ID. ServerView Operations Manager makes a sequential search through the list.

For information about setting up user IDs for ServerView on VMware vSphere-based server see "Setting up user ID for ServerView on VMware vSphere-based server" on page 45.

Storing user IDs in the User/Password list of ServerView Operations Manager

I For more information about the User/Password list of ServerView Operations Manager refer to the manual "ServerView Suite. ServerView Operations Manager V5.0".

Use User/Passwords in the Administration menu to generate a list of the users/passwords stored in ServerView Operations Manager.

Ê Select User/Passwords in the Administration menu.

The User Password window will open.

Ê Enter the user name in User name and Password as well as the relevant password set up on the VMware vSphere-based server.Confirm the password with Confirm Password.

Ê Use Apply to confirm your input.Then confirm your input with OK, and the window will close.


Installation Installing or updating CIM providers

5.2.7.2 Configuring ServerView Operations Manager to support the iRMC

If the ServerView Operations Manager has the iRMC's address of an VMware vSphere host server, you can double-click the ESXi host server list to open the iRMC's Web interface.

I In case of a VMware vSphere /ESXi V4.0-system with patch 4 or in case of a VMware vSphere /EXSi V3.5-system with patch 19 ServerView Operations Manager detects the iRMC's IP address of a VMware vSphere host server.

Without patch 4 installed the IP address has to be configured manually. For details refer to the manual "ServerView Suite. ServerView Operations Manager", section "Server list".

5.3 Subsequently installing or updating Fujitsu CIM providers as an individual component

Subsequently installing Fujitsu CIM providers on an existing VMware vSphere system or updating them corresponds to a classical VMware vSphere update. Installing, uninstalling and updating VMware vSphere add-ons is described in detail in the "ESXi - Setup Guide" for VMware.

For information about installing Fujitsu CIM providers as an individual component refer to the manual "Installation ServerView ESXi CIM Provider V5.30. VMware vSphere Hypervisor (ESXi) Version 4.0 or higher".

Important:

Offline packagesFor information about the provision of Fujitsu CIM providers see "Fujitsu CIM providers (individual component):" on page 29.

ProcedureVMware offers a number of tools for installing, uninstalling and updating add-ons to VMware vSphere. The following are available: vSphere Host Update Utility, vCenter Update Manager and via vSphere-CLI, the command line utility program vihostupdate.


Installing or updating CIM providers Installation

All necessary information about the vihostupdate command line utility program can be found in the VMware manuals "ESXi - Setup Guide", "vSphere Command-Line Interface. Installation and Scripting Guide" and in the "vSphere Command-Line Interface Reference" at www.vmware.com.

Important steps following an installation/updateAfter performing installation/update make sure you at least check the following settings:

– Fujitsu CIM providers enabled

- see"Enabling use of Fujitsu CIM providers" on page 44

– ServerView Operations Manager configured to query data of Fujitsu CIM providers

- seeConfiguring ServerView Operations Manager to query data of Fujitsu CIM providers

For detailed information about setting up an environment for monitoring VMware vSphere-based servers see "Installing components for managing VMware vSphere-based servers" on page 38.


6 Security issuesThe "lean" virtualization of the bare metal solution VMware vSphere makes it easier to safeguard the server environment:

– The reduced code basis means that VMware vSphere provides significantly fewer opportunities for attacks and security gaps than other virtualization solutions.

– VMware vSphere is independent of a higher-level partition or a console, which is based on an all-purpose operating system. This results in fewer interfaces, which could also be used for attacks.

– Unstructured, console-based administration interactions are replaced by authenticated and tested interfaces such as the VI client and remote CLI.

Virtualization software, like other infrastructure software, requires a possibility to manage the solution components. This is done using a management interface, which combines virtualization ghosts, management servers, IP-based storage and additional services, for example authentication and monitoring. Isolation of virtual machines from the Hypervisor interfaces is the most important step towards achieving secure virtual provision in development and implementation of a strict separation of the management level from other network traffic. This reduces the risk of attacks on virtual machines, with effects on the virtualization levels of the other virtual machines.


Security issues

Documents

Monitoring of VMware-based PRIMERGY Servers with ServerViewmanuals.ts.fujitsu.com/file/10346/sv-esxi-cim-support-en.pdf · User Guide - English FUJITSU Software ServerView Suite Monitoring