Sv Esxi Support En

VMware ESXi Monitoring ESXi systems with ServerView Suite

Edition July 2010

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:2000To 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:2000.

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

Copyright and TrademarksCopyright © 2010 Fujitsu Technology Solutions GmbH.

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 New features in VMware ESXi . . . . . . . . . . . . . . . . . . 5

1.1 Target groups and objective of this manual . . . . . . . . . . 5

1.2 Documentation for ServerView Suite . . . . . . . . . . . . . . 5

1.3 Notational Conventions . . . . . . . . . . . . . . . . . . . . . 6

1.4 Differences between VMware ESX and VMware ESXi . . . . . 8

1.5 Architecture of the ServerView solution . . . . . . . . . . . . 9

1.6 Information sources for server management . . . . . . . . . 131.6.1 ESXi traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.6.2 iRMC traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.6.3 RAID management . . . . . . . . . . . . . . . . . . . . . . . 14

2 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1 Requirements for each installation component . . . . . . . 15

2.2 "Coordinated" requirements . . . . . . . . . . . . . . . . . . 19

3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1 Installation steps . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2 Installing VMware ESXi . . . . . . . . . . . . . . . . . . . . 24

3.3 Configuring VMware ESXi . . . . . . . . . . . . . . . . . . . 253.3.1 Creating the administrator password and configuring the default

network behavior . . . . . . . . . . . . . . . . . . . . . . . . 263.3.2 Configuring ESXi for SNMP trap forwarding . . . . . . . . . . . 27

3.4 Creating a virtual machine . . . . . . . . . . . . . . . . . . . 29

3.5 Installing and configuring a guest operating system (example: CentOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contents

3.6 Installing and configuring ServerView RAID Manager . . . . 33

3.7 Configuring the iRMC trap destination . . . . . . . . . . . . . 36

3.8 Configuring ServerView Operations Manager to support the iRMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4 Monitoring an ESXi server . . . . . . . . . . . . . . . . . . . 39

4.1 ServerView Operations Manager . . . . . . . . . . . . . . . . 39

4.2 ServerView RAID Manager . . . . . . . . . . . . . . . . . . . 41

4.3 iRMC Web interface . . . . . . . . . . . . . . . . . . . . . . . 41

5 Local update management . . . . . . . . . . . . . . . . . . . 43

5.1 Current BIOS/firmware/driver versions and Update DVD . . . 43

5.2 Booting the server from the ServerView Suite DVD 1 and starting Update Manager Express . . . . . . . . . . . . . . . . . . . . 44

5.3 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 45

ServerView Operations Manager 5

1 New features in VMware ESXiBetween VMware ESX and VMware ESXi, a change to the software architecture has resulted in far-reaching changes for the monitoring software (see section "Differences between VMware ESX and VMware ESXi" on page 8). VMware ESX is still classic software (an agent is installed on the software for monitoring purposes), while VMware ESXi is more like firmware. This document explains how you can use ServerView to monitor a VMware ESXi server and describes the necessary installation and configuration steps.

1.1 Target groups and objective of this manual

This manual is aimed at system administrators, network administrators, and service professionals who have a sound knowledge of hardware and software. It explains how you can integrate a VMware ESXi server into a ServerView environment.

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

6 ServerView Operations Manager

Target groups and objective VMware ESXi

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.

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 System outputs are indicated using a fixed font.

semi-bold fixed font

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 placing a hyphen between the two key symbols.

Table 1: Notational conventions


VMware ESXi Target groups and objective

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.


VMware und VMware ESXi VMware ESXi

1.4 Differences between VMware ESX and VMware ESXi

VMware ESX and VMware ESXi are bare metal hypervisors, installed directly on the server hardware. Unlike older solutions, these two hypervisors no longer use a host operating system for resource management.

Both hypervisors also differ in terms of their architecture and operational management:

VMware ESX uses an integrated Linux operating system to execute the following two management functions: 1) script execution and 2) the installation of third-party agent software for hardware monitoring, backups, and system management. This latter function is known as the service console.

In order to achieve a considerably smaller code base for VMware ESXi, the service console has been removed from its range of program functions. Consequently, VMware ESXi is more like firmware than traditional software. In the case of VMware ESXi, you can use a Remote Command Line Interface, a Web interface or a special user interface to perform management tasks (see section "Configuring VMware ESXi" on page 25). To enable VMware ESXi to interact with software for monitoring and management tasks, it has been equipped with CIM providers that comply with the standards defined for system management.

Figure 1: Architecture of VMware ESXi (source: www.vmware.com)


VMware ESXi Architecture of the ServerView solution

1.5 Architecture of the ServerView solution

Sources of information

The architecture of VMware ESXi is such that you cannot install a ServerView agent on a VMware ESXi server. Even though such a server is detected in the ServerView Operations Manager server list, and you can view information about this server, you cannot manage the VMware ESXi server here (for information about this difference, refer to the manual "PRIMERGY ServerView Suite. ServerView Operations Manager").

Which sources does ServerView Operations Manager use to obtain information about a VMware ESXi server?

VMware ESXiVMware ESXi enables you to define alarm triggers (and the subsequent alarm actions) for certain events. SNMP trap forwarding is also offered as one such alarm action (see section "ESXi traps" on page 13 and section "Configuring VMware ESXi" on page 25).

iRMCSince iRMC is an autonomous system on the system board of a current PRIMERGY server, it also has autonomous alarm management, which enables you to configure alarms that are forwarded via SNMP to ServerView Operations Manager.


Architecture of the ServerView solution VMware ESXi

RAID ManagerA virtual appliance installed on a virtual server (with CentOS and ServerView RAID Manager) can retrieve RAID controller data from the VMware ESXi server via the CIM management interface (see figure "Architecture of VMware ESXi (source: www.vmware.com)" on page 8) and forward it to ServerView Operations Manager.

Figure 2: Architecture of the ServerView solution for VMware ESXi - trap sources (RAID Manager < V4.5)

SV Operations Manager

User Interface

SV-RAID-M.

CentOS

ESXi

RAID-Ctrl.

iRMChardware

VM

CIMOM

LSI CIM Provider


VMware ESXi Architecture of the ServerView solution

As of ServerView RAID Manager V4.5.0, you can also install ServerView RAID Manager together with ServerView Operations Manager on the system of the central management station:

Figure 3: Architecture of the ServerView solution for VMware ESXi trap sources (RAID Manager as of V4.5)

SV Operations Manager

User Interface

ESXi

RAID-Ctrl.

iRMChardware

VM

CIMOM

LSI CIM Provider

VM

SV-RAID-Manager


Architecture of the ServerView solution VMware ESXi

Monitoring tools

When you have installed and fully set up your environment as described in chapter "Installation" on page 23, you can use the following tools to monitor an ESXi server (see chapter "Monitoring an ESXi server" on page 39):

– The ServerView Operations Manager interface

– ServerView RAID Manager

– The iRMC Web interface


VMware ESXi Information sources

1.6 Information sources for server management

1.6.1 ESXi traps

When you have configured SNMP trap forwarding (see section "Configuring VMware ESXi" on page 25), VMware ESXi sends the following traps to ServerView:

1.6.2 iRMC traps

When you have configured SNMP trap forwarding (see section "Configuring the iRMC trap destination" on page 36), the iRMC sends traps to ServerView. The MIB file wmi.mib is the basis for iRMC traps.

Trap name Description Severity State

vmPoweredOn This trap is sent when a virtual machine is powered ON from a suspended or a powered off state.

INFORMA-TIONAL

OPERA-TIONAL

vmPoweredOff This trap is sent when a virtual machine is powered OFF.

INFORMA-TIONAL

NON-OPERA-TIONAL

vmHBLost This trap is sent when a virtual machine detects a loss in guest heartbeat.

MAJOR DEGRA-DED

vmHBDetected This trap is sent when a virtual machine detects or regains the guest heartbeat.

INFORMA-TIONAL

OPERA-TIONAL

vmSuspended This trap is sent when a virtual machine is suspended.

INFORMA-TIONAL

NON-OPERA-TIONAL

Table 2: ESXi traps


Information sources VMware ESXi

1.6.3 RAID management

ServerView RAID Manager logs all events for all RAID controllers. These events are then forwarded.

RAID Manager stores all event messages in plain text in an event file.

– All events appear in the logging mechanisms of the operating system.

– Furthermore, the ServerView RAID agent converts all events into SNMP traps. When the guest operating system is configured correctly (see section "Installing and configuring a guest operating system (example: CentOS)" on page 31), these traps are forwarded to ServerView.

The MIB file RAID.mib is the basis for the ServerView RAID agent.For a description and a list of all traps, refer to the manual "User Manual. ServerView RAID Manager".


2 Requirements

2.1 Requirements for each installation component

Requirements: ServerView Operations Manager

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

Requirements: VMware ESXi

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 In case you use ESXi 4.0: With patch 4 installed ServerView Operations Manager can automatically detect the iRMC’s IP address of an ESXi host server. Once the IP address has been detected, you can double-click the ESXi 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 Operations Manager", section "Server list".


If you use ESXi 3.5, you can also use the classic remote command line interface to configure ESXi for SNMP trap forwarding. However, the remote command line interface does not have any write permissions for the free variant of ESXi 3.5. If you are using a free ESXi 3.5, you must switch to one of the licensed variants (VI Foundation, VI Standard or VI Enterprise).


Requirements for each installation component Requirements

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

– Supported server platform (refer to the VMware Compatibility Guide)

– 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):Basic SCSI controller (Adaptec Ultra-160/Ultra-320, LSI Logic Fusion-MPT, most NCR/Symbios SCSI controllers);RAID controller (Adaptec RAID, LSI MegaRAID, LSI IME or 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: CentOS

The latest requirements for CentOS are available at:

http://hardware.redhat.com/hcl/

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


Requirements Requirements for each installation component

– For some Linux distributions, 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 ESXi server:

– At least ESXi 3.5 with Update 3

– LSI MegaRAID/ LSI IME controllerUp to Version 4.1 ESXi supports only SAS MegaRAID/ SASIME controllers for management purposes. As of version 4.1 ESXi supports LSI IME controllers.

– 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 ESXi 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 ESXi server.

As of version 4.5, ServerView RAID Manager monitors up to 128 VMware ESXi servers from a central management station.

Requirements: iRMC Web interface



Requirements for each installation component Requirements


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 must 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.]


Requirements "Coordinated" requirements

2.2 "Coordinated" requirements

The requirements for the individual installation components are listed below according to the location of the installation:

Requirement for: Source of requirement:

In your network

- A network configuration that allows you to determine the IP address belonging to the server name

RAID Manager

- 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 must obtain the IP address.

iRMC

"Physical server“

- Server platform supported by VMware ESXi VMware ESXi

- Server with x86 CPU in 64-bit mode VMware ESXi

- At least 2 GB RAM VMware ESXi

- One or more gigabits or a 10Gb Ethernet controller

VMware ESXi

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

VMware ESXi

- SAS MegaRAID/ SASIME controller RAID Manager


"Coordinated" requirements Requirements

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

VMware ESXi

- Serial ATA (SATA): The hard disk must be connected via supported SAS controllers or supported on-board SATA controllers.

VMware ESXi

- At least ESXi 3.5 with Update 3 RAID Manager

- In case you use ESXi 4.0: Patch 4 (see section "Configuring ServerView Operations Manager to support the iRMC" on page 38)

ServerView Operations Manager/ iRMC

- In case you use ESXi 3.5: Patch 19 (see section "Configuring ServerView Operations Manager to support the iRMC" on page 38)

ServerView Operations Manager/ iRMC

Virtual machine/ central management station

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

RAID Manager

- 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

RAID Manager

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

RAID Manager

Monitoring (any host with a browser)

- Internet Explorer as of V6 and a Mozilla-based browser

RAID Manager

- Internet Explorer as of V6 or Mozilla as of V1.5 iRMC

- Sun Java Runtime Environment as of V1.5.0 RAID Manager

- Sun Java Virtual Machine as of 1.5.0_06 iRMC


Requirements "Coordinated" requirements


"Coordinated" requirements Requirements


3 InstallationThis 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.

3.1 Installation steps

The following installation steps are required to ensure optimum monitoring of an ESXi server by ServerView. Detailed information is provided in the following subchapters:

1. Installing ESXi

2. Configuring ESXi

– Administrator password and default network behavior

– SNMP trap forwarding

3. Creating a virtual machine

4. Installing a guest operating system

5. Installing and configuring ServerView RAID Manager

6. Configuring the iRMC trap destination

7. (Configuring ServerView Operations Manager to support the iRMC)


Installing VMware ESXi Installation

3.2 Installing VMware ESXi

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 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 ESXi 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 ESXi Installable and ESXi Embedded on the same host.

Installing VMware

Ê Boot from the CD "ESXi 4.0 Installable".

The welcome screen is displayed.

Ê Follow the user prompts in preparation for the installation.

Ê Press F11 to 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 ESXi as the start drive.


Installation Configuring VMware ESXi

3.3 Configuring VMware ESXi

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.

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

VMware ESXi 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 ESXi 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 an ESXi host.For detailed information about the vSphere command line interface, refer to the VMware manual "vSphere Command Line Interface Installation and Reference 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 Client, see http://pubs.vmware.com/vsp40u1_i/.

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).

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


Configuring VMware ESXi Installation

Auto configuration phase

When you have installed and started ESXi 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.

3.3.1 Creating the administrator password and configuring the default network behavior

The administrative user name for the ESXi 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 ESXi 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.


Installation Configuring VMware ESXi

3.3.2 Configuring ESXi for SNMP trap forwarding

An SNMP agent that is embedded into hostd and can send traps as well as receive queries (e.g. GET requests) has been integrated into ESXi. This embedded SNMP agent is disabled by default.

Requirement

To enable the embedded SNMP agent and to configure it in such a way that it can send traps, you require the vSphere CLI.

I If you want to use ESXi 3.5, you can also use the classic remote command line interface to configure ESXi for SNMP trap forwarding. However, the remote command line interface does not have any write permissions for the free variant of ESXi 3.5. If you are using a free ESXi 3.5, you must switch to one of the licensed variants (VI Foundation, VI Standard or VI Enterprise).

Source of reference:You can download the vSphere CLI from the VMware Web site as follows:www.vmware.com – Downloads – VMware vSphere 4 – Driver & Tools –Automation Tools and SDKs – VMware vSphere CLI

Documentation:For detailed information about installing and operating vSphere CLI, and for information about its command structure, refer to the VMware manual "vSphere Command Line Interface Installation and Reference Guide".

Installing the vSphere CLI

Ê Download the required installation package from the VMware Web site.

Ê Open a shell, navigate to the required target directory, and save and unpack the installation package.

Ê Start the installer and follow the installation notes.


Configuring VMware ESXi Installation

Configuring ESXi for SNMP trap forwarding

To enable the ESXi SNMP agent to send SNMP traps, you must configure the IP address of the ServerView Management Station and the joint ESXi server and ServerView Management Station community. Since the ESXi SNMP agent uses UDP port 162 as the target system port by default, you do not need to specify a port here.

To configure ESXi for SNMP trap forwarding, proceed as follows:

Ê Open a command line.

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

Enable the ESXi SNMP agent.

Ê Enter the following command:

vicfg-snmp --server <IP address of the ESXi host> --username <user name> --password <user password> --communities <community> --enable

Configure a trap destination.


vicfg-snmp --server <IP address of the ESXi host> --username <user name> --password <user password> --targets <IP address of the SV management station>@<port>/<community>

Execute a test trap.


vicfg-snmp --server <IP address of the ESXi host> --username <user name> --password <user password> --test

The ESXi SNMP agent sends a trap to the destination that you have configured.


Installation Creating a virtual machine

In ServerView Operations Manager, the MIB for interpreting incoming traps from ESXi SNMP agents (see section "ESXi traps" on page 13) is integrated as of Version 4.91.

If you have added the ESXi server to the server list, ServerView can now receive and display traps from the ESXi server.

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

3.4 Creating a virtual machine

This section describes how to use vSphere Access to create a virtual machine (see the section entitled "VMware ESXi interface options" on page 25).

For detailed information about vSphere Web Access, see http://pubs.vmware.com/vsp40/.

Activating and calling vSphere

Ê Use the root ID to log on to the ESXi server.

Ê Check whether the Web Access service is active. To do this, enter the following command:

service vmware-webAccess status

The system notifies you of the status of the Web Access service.

If the Web Access service is not active, use the following command to start it:

service vmware-webAccess start


Creating a virtual machine Installation

Ê Start a Web browser.

Ê In the Web browser, enter the URL of the ESXi server:

https://<host or server name>/ui

The login window opens.

Ê In the login window, enter the user name and password, and click Log In.

I The system will notify you if the popup function has been enabled in your browser. Disable this popup function.

The main vSphere Web Access screen opens.

Creating a virtual machine

Ê In the Web Access interface, choose the following:Virtual Machine – Create Virtual Machine.

The Create Virtual Machine wizard opens. Follow the user prompt through the following steps (detailed information is available at http://pubs.vmware.com/vsp40/):

– Define a name and storage location for the virtual machine.

– Select a guest operating system.

I If you intend to install CentOS as a guest operating system, note the following:When creating a virtual machine, CentOS is not offered as a selection option. Therefore, when creating a virtual machine, choose the options Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 5 64-bit.

– Specify the disk space size and the number of processors.

I If you intend to install CentOS as a guest operating system, note the following:Configure at least 512 MB memory for the virtual machine.If you configure less memory for the virtual machine, CentOS will issue error messages when you load certain VMware drivers.


Installation Installing a guest operating system

– Assign a hard disk.

– Assign a network card.

– Assign a CD or DVD drive.

– Assign a floppy drive.

– Assign a USB controller.

– Check and/or change the hardware configuration.

Ê To finish creating the virtual machine, click Finish.

The new virtual machine is now added to the list of virtual machines on the ESXi server.

3.5 Installing and configuring a guest operating system (example: CentOS)

The latest step-by-step description of the installation as well as descriptions of other guest operating system installations is available in the VMware manual "Guest Operating System. Installation Guide" and at http://pubs.vmware.com/vsp40u1_i/. The latest installation steps for CentOS (as at September 2009) are provided below.

Setting up a virtual machine

A new virtual machine is like a physical computer with a blank hard drive. You must partition and format the virtual hard disk, and install an operating system. Most installation programs organize the partitioning and formatting of the virtual hard disk.

Installing the guest operating system - example: CentOS

Installing an operating system on a virtual machine is the same as installing an operating system on a physical server. In other words, you have to partition and format the virtual disk space.

The easiest way to do this is to use the Standard CentOS Distributions CD to install CentOS:


Installing a guest operating system Installation

Requirements:

– When creating a virtual machine, CentOS is not offered as a selection option. Therefore, when creating a virtual machine, choose the options Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 5 64-bit.

– Configure at least 512 MB memory for the virtual machine.If you configure less memory for the virtual machine, CentOS will issue error messages when you load certain VMware drivers.

– CentOS does not provide a driver for the BusLogic SCSI adapter.Choose the LSI Logic SCSI adapter.

Installation:You can use vSphere Web Access and its remote console function to install the guest operating system. More detailed information is available at http://pubs.vmware.com/vsp40/.

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

Ê Place the installation CD in the CD drive.

Ê Power on the virtual machine.

Ê Follow the installation wizard. Note the following:

– Do not choose the option Virtualization during the installation.

– Pay attention to your partitioning concept during the installation.

I Disable the screensaver in the CentOS guest operating system.Screensavers demand a great deal of processing power. On an XFree86 3.x X server, a screensaver can cause the X server to stop.


Installation Installing ServerView RAID Manager

Additional notes:

I Install the necessary VMware tools on your guest operating system.Additional information is available on the VMware Web site at:http://kb.vmware.vom/kb_/340.

Settings in the guest operating system - example: CentOS

ServerView RAID Manager requires a network configuration that allows you to use a DNS or the host database to determine the IP address belonging to the server name (see section "Requirements for each installation component" on page 15).

Ê If your network configuration does not satisfy this requirement, configure the following settings in the configuration file /etc/hosts after you install the guest operating system:

<IP address><host name of CentOS>

<IP address><host name of VMware host>

3.6 Installing and configuring ServerView RAID Manager

Installing ServerView RAID Manager on the virtual machine

When you have installed the guest operating system, you can install ServerView RAID Manager on the virtual machine in the same way as you would install it on any physical server.

For more information, refer to the manual "ServerView RAID Manager".

Configuring ServerView RAID Manager

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


Installing ServerView RAID Manager Installation

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.

Ê 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 ESXi (see section "Configuring ESXi for SNMP trap forwarding" on page 29).


Installation Installing ServerView RAID Manager

ServerView RAID Manager as of V4.3.6In ServerView RAID Manager, you can use amCLI to 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 amCLI to 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_1 to 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.Under ESXi 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 < V4.5, only the first entry is evaluated.

Ê Restart ServerView RAID Manager to make the configuration effective.


Configuring the iRMC Installation

3.7 Configuring the iRMC trap destination

iRMC S2 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:

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

Ê Open a Web browser.

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

The login screen is displayed.

Ê Enter the login data and confirm the entry.

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

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

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

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


Installation Configuring the iRMC

Figure 4: Page for SNMP Trap Destination

SNMP CommunityName of the SNMP community

Ê Click Apply to 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 Apply to enable the SNMP server as a trap destination.

Ê Click Test to test the connection to the SNMP server.

Ê If necessary, click Apply All to enable all settings.

Ê Close the browser window.


Configuring the iRMC Installation

3.8 Configuring ServerView Operations Manager to support the iRMC

If the ServerView Operations Manager has the iRMC’s IP address of an ESXi host server, you can double-click the ESXi host server in the server list to open the iRMC’s Web interface (see section "iRMC Web interface" on page 41).

I In case of an ESXi V4.0-system with patch 4 or in case of an ESXi V3.5-system with patch 19 ServerView Operations Manager detects the iRMC’s IP address of an ESXi host server.

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


4 Monitoring an ESXi serverWhen you have installed and fully set up your environment as described in chapter "Installation" on page 23, you can use the following tools to monitor an ESXi server:

– The ServerView Operations Manager interface

– ServerView RAID Manager

– The iRMC Web interface

4.1 ServerView Operations Manager

The architecture of VMware ESXi is such that you cannot install a ServerView agent on a VMware ESXi server. Even though such a server is detected in the ServerView Operations Manager server list, and you can view information about this server, you cannot manage the VMware ESXi server here (for information about this difference, refer to the manual "ServerView Suite. ServerView Operations Manager").

VMware ESXi server in the server list

The VMware ESXi host server is detected by its network address, model, and operating system information.

As of VMware ESXi V 3.5, VMware servers are displayed as a special group within the server list under All Servers. When you click this group, the VMware server and the associated virtual servers (virtual machines - VMs) are displayed in the area on the right.

The associated virtual servers are displayed with their current VMware names in the Name column in the server list under the ESXi host server.


ServerView Operations Manager Monitoring an ESXi server

Figure 5: VMware ESXi server in the server list




You cannot use the server list to manage the VMware ESXi host server.


Monitoring an ESXi server ServerView RAID Manager

4.2 ServerView RAID Manager

When you have installed and set up ServerView RAID Manager as described in section "Installing and configuring ServerView RAID Manager" on page 33, you can use the entire range of ServerView RAID Manager functions.

You can start ServerView RAID Manager from any browser. For detailed information, refer to the manual "User Manual. ServerView RAID Manager".

4.3 iRMC Web interface

iRMC S2 has its own operating system, acts as a Web server, and provides its own Web interface. If your ESXi server has iRMC S2 and you have set it up as described in section "Installing and configuring ServerView RAID Manager" on page 33, this Web interface provides a comprehensive monitoring tool.

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





iRMC Web interface Monitoring an ESXi server


5 Local update managementWith Update Manager Express from the PRIMERGY ServerView Suite, you can install firmware and BIOS of the various server components on the current PRIMERGY servers.

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

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

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.

Also in the period between two successive editions of the ServerView Suite DVD 1, Fujitsu Technology Solutions offers constantly updated versions of BIOS/firmware/drivers, Update Manager Express and ASPs for downloading at ftp://ftp.ts.fujitsu.com/images/serverview.

Update DVD

You can always update your server’s BIOS/firmware/drivers by, if necessary, downloading the DVD ISO image Repository_<version>.iso of the latest version from ftp://ftp.ts.fujitsu.com/images/serverview, creating an Update DVD from it and then using this for the BIOS/firmware/driver update.

I The Update DVD is not bootable.

ftp://ftp.ts.fujitsu.com/images/serverview


ftp://ftp.ts.fujitsu.com/fsc/supportcds



Starting Update Manager Express Update Management

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

I Because the Update DVD is not bootable, you must also boot the server from the ServerView Suite DVD 1 if you want to start Update Manager Express from the Update DVD.

I Using Update Manager Express to install PSPs is not possible, if Update Manager Express has been started from the ServerView Suite DVD 1 oder from the Update DVD.

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.

Ê 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].

Ê In the BIOS setup, change the boot sequence to “Boot from CD”.

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

Ê Click Continue.

The Update Manager Express main window is displayed.


Update Management Documentation

Starting Update Manager Express from the Update DVD

Proceed as follows:

Ê Boot the server from the ServerView Suite DVD 1:

Ê Switch on the server.

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

Ê 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].

Ê In the BIOS setup, change the boot sequence to “Boot from CD”.

Ê Wait until the Installation Manager start window is displayed.

Ê Remove the ServerView Suite DVD 1 from the drive of the managed server.

Ê Place the Update DVD with the current BIOS/firmware versions in the drive of the managed server.

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

Ê Click Continue.

The Update Manager Express main window is displayed.

5.3 Documentation

For more information about Update Manager Express, refer to the manual "Update Manager Express".


Documentation Update Management

Documents

Sv Esxi Support En