SigmaSystemCenter 2.1 First Step Guide - nec.com fileSome icons used in this program are based on...

SigmaSystemCenter 2.1

First Step Guide

- Fourth Edition -

Copyright (C) NEC Corporation 2003-2009. All rights reserved.

Disclaimer of Warranty All the information, text, graphics, links or other items contained within this document is provided by copyright law. All Rights Reserved. No part of this document may be reproduced or transmitted without permission of NEC. NEC may make changes to this document, at any time without notice. NEC assumes no responsibility for errors or omissions in this document. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. NEC does not warrant the accuracy or completeness of this document.

Trademark Information Microsoft, Windows, Windows Server, Microsoft Internet Explorer, SQL Server, and Hyper-V are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a registered trademark or trademark of Linus Torvalds in the United States and/or other countries. SUSE is a registered trademark or trademark of Novell, Inc., in the United States and/or other countries. Red Hat is a registered trademark or trademark of Red Hat, Inc. in the United States and/or other countries. Intel, Pentium, Itanium, and Xeon are trademarks of Intel Corporation in the U.S. and other countries. AMD is a trademark of Advanced Micro Devices, Inc. EMC, Symmetrix, CLARiiON, and Navisphere are registered trademarks of EMC Corporation in the United States and other countries. VMware, ESX, ESXi and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and other countries. Xen, Citrix, XenServer, and XenCenter are registered trademarks or trademarks of Citrix Systems, Inc. PXE Software Copyright (C) 1997 - 2000 Intel Corporation. Copyright (C) 2005, 2007, ALAXALA Networks Corporation. All rights reserved. (C) 1992-2007 Cisco Systems Inc. All rights reserved. Foundry Networks, FastIron, ServerIron and the 'Iron' family of marks are trademarks or registered trademarks of Foundry Networks, Inc. in the United Status and other countries. BIG-IP is a registered trademark of F5 Networks, Inc. in the United States and/or other countries. InstallShield is a registered trademark and service mark of Macrovision Corporation and/or Macrovision Europe Ltd. in the United States and/or other countries. Java and all Java related trademarks are registered trademarks of Sun Microsystems, Inc. in the United States and other countries. This product includes software developed by the Apache Software Foundation. This product contains JRE (Java Runtime Environment), which is distributed by Sun Microsystems, Inc. without charge, and Tomcat, which is distributed by Apache Software Foundation without charge. Use these products after accepting their license agreements. For details of copyright and ownership rights, refer to the following license files: Tomcat: folder where Tomcat is installed\LICENSE JRE: folder where JRE is installed\LICENSE

Some icons used in this program are based on Silk Icons released by Mark James under a Creative Commons Attribution 2.5 License. Visit http://www.famfamfam.com/lab/icons/silk/ for more details. All other brands and products used in this document are the trademarks or registered trademarks of their respective trademark holders. The (R) and TM marks are not explicitly in this document.

iii

Contents Preface.................................................................................................................................... v

How to Use This Manual....................................................................................................................... v Manual Organization............................................................................................................................. v SigmaSystemCenter Manuals .............................................................................................................. vi Document Conventions......................................................................................................................... viii

1. About SigmaSystemCenter ........................................................................................... 3 1.1. What is SigmaSystemCenter? ................................................................................................. 4

1.1.1.Advantage of Adopting SigmaSystemCenter ........................................................................................... 4 1.2. What Can SigmaSystemCenter Do? ....................................................................................... 5

1.2.1.Machine Status and Failure Monitoring .................................................................................................... 5 1.2.2.Software Distribution ................................................................................................................................ 6 1.2.3.Machine Configuration Change ................................................................................................................ 7 1.2.4.Changing Usage....................................................................................................................................... 8 1.2.5.System Configuration Control................................................................................................................... 9 1.2.6.Optimized Placement of Resource and Improvement of Availability......................................................... 11 1.2.7.Failure Recovery (N+1 Recovery) ............................................................................................................ 12 1.2.8.Failure Recovery (Virtual Environment).................................................................................................... 13 1.2.9.Optimized Placement ............................................................................................................................... 14 1.2.10.Scale Out................................................................................................................................................ 15 1.2.11.Scale In .................................................................................................................................................. 16 1.2.12.SAN Boot................................................................................................................................................ 17

2. System Design................................................................................................................ 19 2.1. Examining the System Configuration of SigmaSystemCenter ................................................ 20

2.1.1.Standard Function of SigmaSystemCenter .............................................................................................. 20 2.1.2.Functions Enabled by Connecting with Other Products............................................................................ 22 2.1.3.How to Configure Components or Products ............................................................................................. 23 2.1.4.Example of System Configuration and Caution ........................................................................................ 25

2.2. Product Architecture and License of SigmaSystemCenter...................................................... 29 2.2.1.Edition ...................................................................................................................................................... 29 2.2.2.Licenses ................................................................................................................................................... 29

2.3. Flow of Operating SigmaSystemCenter .................................................................................. 31 3. Operational Environment............................................................................................... 37

3.1. Version Information of SigmaSystemCenter............................................................................ 38 3.2. Management Server ................................................................................................................ 39

3.2.1.System Requirements .............................................................................................................................. 39 3.3. Managed Machine – Physical Machine ................................................................................... 41

3.3.1.System Requirements .............................................................................................................................. 41 3.3.2.DPM Controllable Environment ................................................................................................................ 42 3.3.3.Out-of-Band Management Controllable Environment ............................................................................... 43

3.4. Manageable Virtual Machine Infrastructure ............................................................................. 44 3.4.1.Infrastructure of Virtual Machines ............................................................................................................. 44 3.4.2.Manageable Guest OS............................................................................................................................. 44

3.5. Managed Machine – Virtual Machine....................................................................................... 46 3.5.1.DPM Controllable Environment ................................................................................................................ 46

3.6. Network Devices ...................................................................................................................... 47 3.6.1.Network Management Software ............................................................................................................... 47 3.6.2.Support Models of Switches or Switch Blades ......................................................................................... 47 3.6.3.Support Models of Load Balancers........................................................................................................... 47

3.7. Storage..................................................................................................................................... 48 3.7.1.Storage Management Software and Support Models of Storage ............................................................. 48

4. Latest Version Information ............................................................................................ 49

iv

4.1. New Features and Enhancements...........................................................................................50 4.1.1.Enhanced Failure Recovery in Virtual Environment ..................................................................................50 4.1.2.Enhanced Operation Management ...........................................................................................................50 4.1.3.Tag VLAN Setting .....................................................................................................................................50 4.1.4.Power Control ...........................................................................................................................................50 4.1.5.Enhanced Optimized Placement and Optimized Startup...........................................................................51 4.1.6.New Target License Release ....................................................................................................................51 4.1.7.Enhanced Policy Function.........................................................................................................................51 4.1.8.VMware vSphere 4.0 Support ...................................................................................................................51

Appendix A Glossary..........................................................................................................55 Appendix B Revision History.............................................................................................61

v

Preface

How to Use This Manual SigmaSystemCenter First Step Guide is intended for first-time users and about the product summery, system design methods, and the information of latest operating environment of SigmaSystemCenter.

Manual Organization Part I Summary and Design of SigmaSystemCenter 1 "About SigmaSystemCenter": Explains the summary of the SigmaSystemCenter. 2 "System Design": Explains the system configuration methods for installation into the SigmaSystemCenter. Part II SigmaSystemCenter Latest Information 3 "Operational Environment": Explains the latest information that needs to be confirmed before installing. 4 "Latest Version Information": Lists information regarding the latest version of SigmaSystemCenter. Appendix Appendix A "Glossary" Appendix B "Revision History"

vi

SigmaSystemCenter Manuals The manuals of SigmaSystemCenter are configured for the various products and components as follows. In this manual, each of the following manuals is described as "How Manuals Are Called in This Manual." Products or Components

Manuals How Manuals Are Called in This Manual

SigmaSystemCenter 2.1 First Step Guide SigmaSystemCenter First Step Guide

SigmaSystemCenter 2.1 Installation Guide SigmaSystemCenter Installation Guide

SigmaSystemCenter 2.1 Configuration Guide

SigmaSystemCenter Configuration Guide

SigmaSystemCenter 2.1

SigmaSystemCenter 2.1 Reference Guide SigmaSystemCenter Reference Guide

NEC ESMPRO Manager 4.42

NEC ESMPRO Manager User’s Guide NEC ESMPRO Manager User’s Guide

DeploymentManager System Introduction Ver.5.2

DeploymentManager System Introduction

DeploymentManager (Basic) User’s Guide Ver.5.2

DeploymentManager Basic User’s Guide

DeploymentManager (Advanced) User’s Guide Ver.5.2

DeploymentManager Advanced User’s Guide

DeploymentManager 5.21

DeploymentManager (PackageDescriber) User’s Guide Ver.5.2

DeploymentManager PackageDescriber User’s Guide

System Monitor - Performance Monitoring Services 4.1.1

System Monitor - Performance Monitoring Services User’s Guide

System Monitor - Performance Monitoring Services User’s Guide

Reference: All the latest SigmaSystemCenter manuals are available in the following URL. http://www.nec.co.jp/sigmasystemcenter/download_eng.html

vii

The information regarding product summery, installation, configuration, operation and maintenance of SigmaSystemCenter are included in the following four manuals. The purposes of the manuals are as follows. SigmaSystemCenter First Step Guide This manual is intended for users who use SigmaSystemCenter for the first time and explains the product summery, system design methods and operating environment. SigmaSystemCenter Installation Guide This manual is intended for system administrators who install, upgrade, or uninstall SigmaSystemCenter and explains how to. SigmaSystemCenter Configuration Guide This manual is intended for system administrators who configure the whole system after installation and who operate and maintain the system after the configuration. Actual operational flow is used to explain the process from the configuration after installation to the operating procedures. This manual also explains the maintenance process. SigmaSystemCenter Reference Guide This manual is intended for administrators of SigmaSystemCenter and explains its functions, the operational methods, information of maintenance and trouble shooting, and lists all the operating screens. This manual is a supplement to SigmaSystemCenter Installation Guide and SigmaSystemCenter Configuration Guide.

viii

Document Conventions In this manual, information that needs attention and references are described as follows:

Note: indicates caution notes, and supplementary explanation for functions, operations, and settings.

Reference: indicates why and where you should refer to. In addition, this manual uses the following document conventions.

Convention Used Item Example

Bold font Items that a user selects on a screen, short text input, screen names, short command-line commands, and command-line options

Type Exit and click Enter. User License Confirmation screen Use the –prt command. Use the /a option.

Italic font Book or manual titles, and variable names

Configuration Guide add GroupName

Quotation marks Chapter titles and default values See Chapter 9, "Add a Computer."

Monospace font (courier new)

Long text inputs, messages and command-line commands

Type the following text: Confidential–Class B

1

PPaarrtt II SSuummmmaarryy aanndd DDeessiiggnn ooff SSiiggmmaaSSyysstteemmCCeenntteerr

This section explains the product summary and system design methods of SigmaSystemCenter. • 1 About SigmaSystemCenter • 2 System Design

3

1. About SigmaSystemCenter This chapter explains the product summary of SigmaSystemCenter. This chapter contains the following sections: • 1.1 What is SigmaSystemCenter?.....................................................................................4 • 1.2 What Can SigmaSystemCenter Do? ...........................................................................5

1 About SigmaSystemCenter

SigmaSystemCenter 2.1 First Step Guide 4

1.1. What is SigmaSystemCenter? SigmaSystemCenter is "platform management software" that helps reducing IT cost and supports real-time management with optimization of IT resource configuration.

1.1.1. Advantage of Adopting SigmaSystemCenter As installation and configuration methods differ according to machine types, OS types, and software, system administrators must have been aware of their differences when configuring, operating, and maintaining the system. The "complex management of each OS" has caused increases in management costs. SigmaSystemCenter provides a system environment where you can collectively configure, operate, and maintain machines grouped for their usage. The work load of the administrators will be broadly reduced and system administrative costs will be alleviated by adopting SigmaSystemCenter, as "operations that require an awareness of differences between managed machines can be handled collectively", regarding hardware maintenance with failures, configuration of each OS, software installations, and patch applications. In addition, SigmaSystemCenter enables you to manage not only physical hardware, such as servers and storage, but also virtual environment collectively on the same console with the same operations. SigmaSystemCenter can change the system configuration using spare machines that are prepared in advance and machines used for other usage, so recovering system from failures, checking performance state, and changing the configuration of system are realized by "reallocating system resources flexibly." In the past, in order to deal with load fluctuation, that is high load, and failures on machines, you needed spare machines for each task; however, with SigmaSystemCenter, you do not need numbers of spares any more because machines can be used all around on your demand. In management of virtual environment, if a failure occurred on a virtual machine server, SigmaSystemCenter improves availability by moving virtual machines on the server to other sound virtual machine server. In addition, monitoring load status of virtual machine servers and moving virtual machines, SigmaSystemCenter can keep work load of virtual machine servers moderate. Therefore, SigmaSystemCenter provides you a next-generation system management and operating standard with flexibility, availability, and serviceability.

What Can SigmaSystemCenter Do?

Part I Summary and Design of SigmaSystemCenter 5

1.2. What Can SigmaSystemCenter Do? SigmaSystemCenter can manage machines regardless of machine types or OS types. Using SigmaSystemCenter, you can manage not only hardware machines (We call the hardware machine a physical machine), but also virtual machines. SigmaSystemCenter manages multiple machines used for the same service in a group, so that the operations that used to be needed for each machine can be executed collectively to groups. SigmaSystemCenter has various operations that are based on the management by grouping.

1.2.1. Machine Status and Failure Monitoring SigmaSystemCenter can monitor the status of the machines. This function monitors usage and operating status of each machine resource including terminal equipments, such as CPU blades, in real-time. In addition, the function monitors errors and thresholds of CPU, memories, or disks periodically and if any failure is generated, the function reports you immediately. The system can recover from a failure when an event is detected by the machine status monitoring function.



1.2.2. Software Distribution SigmaSystemCenter can distribute OS and application updates to each machine group where machines are operating for the same service or to the whole system with simple operations. In addition, software can be sequentially distributed to each machine in a group. When updating system whose service level cannot be decreased, you can update the system in the period of time when the system load is low. SigmaSystemCenter can install OSs and applications collectively to multiple machines when you set up your system, which reduces the burden of establishing additional machines.



1.2.3. Machine Configuration Change A system administrator can change configuration of machines with simple operations using Web Console or Command-line Interface according to your needs in SigmaSystemCenter. Machine configuration changes that he / she can execute with SigmaSystemCenter are as follows:

Physical Machine

• Activating a machine To activate a machine in a group, there are two ways: Allocate Machine which activates a machine with software distributed and network settings configured and Register Master Machine which activates a machine to which settings for operations have configured without any setting needed in activating.

• Deleting a machine To move a running machine to a pool and deactivate the machine, which is called Release Resource in SigmaSystemCenter.

• Replacing a machine To replace a machine, on which failure or other problem occurred, with a spare machine registered in a pool to restore the problem

• Changing Usage (See Subsection 1.2.4) To move a running machine in a group to other group and activate the machine in the group with other usage.

Virtual Machine

• Activating a machine To activate a machine in a group, there are three ways to activate a virtual machine: Create and Assign Resource which creates a new virtual machine on a virtual machine server, Allocate Machine which customizes an existing virtual machine and activates the machine, and Register Master Machine which activates an existing virtual machine without customizing.

• Deleting a machine There are two ways to delete a virtual machine: Release Resource which moves a running virtual machine to a pool and deactivates the machine and Delete VM which deletes a virtual machine from its virtual machine server.

• Moving VM To move a running virtual machine to other virtual machine server, there are the following three ways: - Hot Migrate / Cold Migrate:

To move a powered ON virtual machine, use Hot Migrate and to move a powered OFF virtual machine, use Cold Migrate. These can be executed when a target virtual machine exists on a shared disk.

- Move: To move a virtual machine including its virtual disk after shutting down the virtual machine.

- Failover: To restart a virtual machine on other virtual machine server when its virtual machine server is down due to some reason, such as failure. This can be executed when a target virtual machine exists on a shared disk.



• Changing machine resources: You can change resources that are the number of CPUs and memory capacity to assign to a virtual machine, keeping its running status.

1.2.4. Changing Usage SigmaSystemCenter can change usage of physical machine by switching disk images of shared machines in response to the fluctuations in service load, service reduction, and service expansion. This operation standardizes the operational rate of the machines, which increases the effective utilization of resources. You can change usage of machines even if you are using different OSs for each machine as this operation switches the image of machines; you can change the system configurations between different platforms, for example, from Windows to Linux, and you can do it the other way also. The operation can be executed by simple procedure on the Web Console, or by simple command. Furthermore, executing this operation from Task Scheduler enables to change usage with your operational schedule.



1.2.5. System Configuration Control SigmaSystemCenter can control configuration of the whole system, including compatible products, triggered by a machine configuration change.

Storage Control Configuration of storage connected to a machine can be changed according to a configuration change of the machine. Note: You need to purchase storage management products. If you are using NEC Storage, you need the related products, including NEC Storage Manager Integration Base and NEC Storage Manager Server to your storage. These are not included in the package of SigmaSystemCenter.

Network Control Configuration of network devices connected to a machine can be changed according to a configuration change of the machine. SigmaSystemCenter can update settings of a switch connected to the machine automatically and change configuration of VLAN. Also, load distribution setting of load balancer can be updated automatically. Note: If VLAN control is not configured, the network is fixed. In that case, you can change the machine configuration only in the same network.



The following is an example of registering a switch port. Normal Operation There are machines running for Operation A and B, and a spare machine.

Add a Spare Machine The spare machine is added as a machine for the Operation A.

Added to VLAN by the Configuration Change The system adds the switch port of the added machine to VLAN by adding the machine.



1.2.6. Optimized Placement of Resource and Improvement of

Availability

If you set how to deal with an event, such as a failure or high load, in advance for when it occurs, SigmaSystemCenter can execute restoration process automatically when a failure event or high load is detected. The followings are parts of operating models.

Failure Recovery (N+1 Recovery) (1.2.7) Failure Recovery (Virtual Environment) (1.2.8) Optimized Placement (1.2.9) Scale Out (1.2.10) Scale In (1.2.11) SAN Boot (1.2.12)



1.2.7. Failure Recovery (N+1 Recovery)

When a failure is generated on a physical machine, SigmaSystemCenter can recover the failure by replacing the machine with a spare machine. When a recovery process is configured for a specific event in advance; we call the setting a recovery process setting in this manual, the recovery process is automatically started for the event. Any operation failure can be handled by preparing at least one shared spare machine unit for multiple operations (N+1 recovery). The following is an example of failure recovery.

Normal Operation There are physical machines for Operation A and B and a spare machine, which can be activated for either operation.

Failure Detected The system detects failure on the machine for Operation A using the machine status monitoring function.

Automatic Installation and Setup Triggered by the detection of failure, OS and applications are installed and necessary settings, such as storage settings and network settings, are configured automatically according to the recovery process setting.

Replaced and Recovered The system replaces the failure machine with the spare machine that has set up for the Operation A and starts its operation quickly.



1.2.8. Failure Recovery (Virtual Environment) SigmaSystemCenter monitors failure of hardware and software of host servers of virtual machines. Detecting predictor of hardware failure, it restores the system by moving virtual machines on the virtual machine server to other sound virtual machine server with live migration. If SigmaSystemCenter cannot live-migrate, for example, when a host server of virtual machines is stopped due to failure, SigmaSystemCenter restores the system by failing over the virtual machines to other sound host server.

If you consider operation with failure recovery on a virtual machine, set up a virtual machine on a shared disk (SAN).



1.2.9. Optimized Placement SystemProvisioning maintains the proper load of a virtual machine server by monitoring the load status of the virtual machine server.

If the load is high, the load is adjusted by Hot Migrating virtual machines from a loaded virtual machine server to other virtual machine server which loads are not very high. If the high load is not alleviated by moving virtual machines, SystemProvisioning can start and use new virtual machine servers. Conversely, if a condition of surplus machine power due to the use of multiple virtual machine servers with low loads is detected, virtual machines can be automatically moved to virtual machine servers with fewer virtual machine units, without exceeding the appropriate load. SystemProvisioning shuts down a virtual machine server which number of virtual machines has reached zero. After that, if the load increases, SystemProvisioning maintains the appropriate load condition by starting the virtual machine server that was shut down and moving the virtual machines on the virtual machine server with Hot Migrate; therefore, SystemProvisioning can operate, saving its power by shutting down and starting virtual machine servers in response to the load condition as well as maintain the appropriate load.



1.2.10. Scale Out If the load of machines for a specific service is expanded, SigmaSystemCenter improves the whole system performance by adding machines according to restoration process configured in advance. Adding a physical machine, SigmaSystemCenter installs OSs and applications that are required to the machine automatically. When adding a virtual machine. A created virtual machine is added to a group after being customized. Therefore, operation can be continued without troublesome tasks. We call this operation Scale Out. The following is an example of Scale Out.

High Load Detected The high load condition of the system is detected in a group for Operation A.

Automatic Installation and Setup Triggered by the detection of the high-load condition, an OS and applications are installed and necessary settings, such as storage settings and network settings, are configured automatically according to the recovery process setting.

Adding the Machine The system adds the machine that has set up for the Operation A.



1.2.11. Scale In Scale In is the opposite operation of Scale Out. The system can make a machine unnecessary for its belonging service queue in a pool as a spare machine when the load decrease is detected in the service to keep the load condition moderate. This operation make machines queue until there is one machine left in the service group. Note: This operation may cause ▪ Insufficient performance by deleting machines. ▪ Repetition of scaling out and in if you configure to scale out and in automatically using the machine status monitoring function. The following is an example of Scale In. Low Load Detected The low load condition of the system is detected in a group for Operation A.

Machines Deleted The system make unnecessary machines queue as spare machines to balance the system load.



1.2.12. SAN Boot SAN Boot is the function that can switch access to the storage by machine configuration change and boot a boot disk by placing the boot disks on storage on SAN in advance. This function can reduce the installation time of disk images. Also, with SAN Boot, when a failure is generated on a machine, you can boot its OS after switching the machine to a spare machine, which enables to restore the error status at an early time. The following is an example of SAN Boot. If a failure should be generated, SigmaSystemCenter applies necessary configurations, such as applications, OS, configuration for VLAN, and disk volume for boot, for each machine automatically and the restores the status autonomously at once by running SAN Boot.

Even if a disk image should be damaged, SigmaSystemCenter can restore the disk image with a backup from the management server.

Note: ▪ SigmaSystemCenter supports only the SAN boot configurations composed of specific hardware and software. ▪ Depending on a system, if you change machine configurations with switching access to multiple storages simultaneously, it may take longer than installing disk images because of the waiting time for switching storage.

19

2. System Design This chapter explains the methods to determine the system configuration when installing SigmaSystemCenter. This chapter contains the following sections: • 2.1 Examining the System Configuration of SigmaSystemCenter ..................................20 • 2.2 Product Architecture and License of SigmaSystemCenter .......................................29 • 2.3 Flow of Operating SigmaSystemCenter ....................................................................31

2 System Design


2.1. Examining the System Configuration of SigmaSystemCenter

This section explains functions of SigmaSystemCenter and components included in SigmaSystemCenter. Examine configurations of your system, including software to install on your management server and managed machines, and network, according to your demanding operation model, using the example of system configuration drawn in the following subsection for reference.

2.1.1. Standard Function of SigmaSystemCenter SigmaSystemCenter consists of the following functions. Interaction of these functions realizes various functions of SigmaSystemCenter.

System Management Function This function works together with the various functions of SigmaSystemCenter or products listed in Subsection 2.1.2, "Functions Enabled by Connecting with Other Products" to build managed machines, change the configuration of machines, and execute autonomous recovery during machine failures. SigmaSystemCenter implements this function using SystemProvisioning. The Web Console and CLI are provided as user interface. This function uses SQL Server 2005 as a database. The information of system configuration that is configured by this function is stored in the configuration database at any time.

Machine Monitoring Function This function centrally manages the active and error status of managed machines. SigmaSystemCenter monitors physical machines through NEC ESMPRO Manager. If managed machines are VMware virtual machines, SigmaSystemCenter monitors the machines via VirtualCenter. With virtual machine servers (ESX), SigmaSystemCenter monitors the machines via NEC ESMPRO Manager and VirtualCenter. And with virtual machine servers (ESXi), SigmaSystemCenter itself monitors them.

Performance Monitoring Function This function periodically collects the load status of CPU, memory capacity, and disk of managed machines, and graphs the results. In addition, these results can be reported to the System Management Function (SystemProvisioning) in response to increasing and decreasing loads. SigmaSystemCenter implements this function using the System Monitor - Performance Monitoring Services.

Examining the System Configuration of SigmaSystemCenter


Software Distribution and Update Function

This function distributes software, such as OSs, middleware, and patches. SigmaSystemCenter implements this function using DPM. This function consists of the following elements, and these elements need to be installed on machines that are appropriate for each element to work properly in the network. • Web Server for DPM • Management Server for DPM • Package Web Server • Web Console *1 • Client Service for DPM • Image Builder (Remote Console) • PackageDescriber • Command Line for DPM • Database (DPM) *1 This is the DPM Web Console.

SystemProvisioning can connect to multiple instances of Web Server for DPM, and instructs them to distribute features and to update. Reference: See Section 1, "Before Installing DPM" in DeploymentManager System Introduction for details of installation configuration.

2 System Design


2.1.2. Functions Enabled by Connecting with Other Products SigmaSystemCenter has functions that are implemented by connecting with other hardware or software. In this subsection, the functions are introduced. For operations using these functions, see Section 1.2, "What Can SigmaSystemCenter Do?"

Storage Management Function This function changes the configuration of storage connected to machines when the machine’s system configurations are changed. SigmaSystemCenter implements this function by working with storage management software; NEC Storage, EMC Symmetrix, and EMC CLARiiON.

Network Management Function This function controls VLAN and load balancers when system configurations are changed. SigmaSystemCenter implements this function by working with MasterScope Network Manager.

Virtual Environment Management Function This function controls virtual machines and virtual machine servers. This function enables SigmaSystemCenter to manage virtual machine servers; ESX and ESXi of VMware, Inc., XenServer Enterprise Edition of Citrix Systems, Inc., and Hyper-V of Microsoft Corp., and virtual machines configured on these virtual machine servers collectively.



2.1.3. How to Configure Components or Products For your best and highest use of SigmaSystemCenter, you need to install each function of SigmaSystemCenter with appropriate configuration. You can install all the manager functions on the same management server, or on separate management servers. The following tables show configuration of installing manager functions and client functions. Examine how you want to configure your system, referring to these tables. The following table is configuration of installation for manager functions.

Server Component or Product

SigmaSystemCenter management server SystemProvisioning NEC ESMPRO Manager System Monitor - Performance Monitoring Services NEC ESMPRO Agent (to use the alert function) *1 Command Line for DPM *2 NEC Storage Manager Integration Base (to work with NEC Storage Manager) Solutions Enabler (to work with EMC Symmetrix)Navisphere CLI, Navisphere Agent (to work with EMC CLARiiON)

Windows/Linux Software Distribution Web Server

Web Server for DPM

Windows/Linux Software Distribution Management Server

Management Server for DPM Image Builder

Network Management Server MasterScope Network Manager (to work with MasterScope Network Manager)

Storage Management Server NEC Storage Manager (to work with NEC Storage Manager) ControlCenter/Symmetrix Manager, SAN Manager (to work with Symmetrix) Navisphere Manager (to work with CLARiiON)

VirtualCenter Management Server VirtualCenter Server (to work with VMware) VirtualCenter Web Service (to work with VMware)

VirtualCenter Client VirtualCenter Client (to work with VMware)

XenCenter XenCenter (to work with VMware)

2 System Design


The following table is configuration of installation for client functions.

Server or Machine Component or Product

Managed Machine

NEC ESMPRO Agent Client Service for DPM

Virtual Machine Server (ESX) NEC ESMPRO Agent for VMware Infrastructure 3 Client Service for DPM

Virtual Machine Server (ESXi) No agent needed to be installed

Virtual Machine Server (Citrix XenServer Enterprise Edition)


Virtual Machine Server (Windows Server 2008 Hyper-V)


Virtual Machine Client Service for DPM

*1 NEC ESMPRO Agent needs to be installed to set to notify the NEC ESMPRO Manager of events (SNMP Trap) from SystemProvisioning.

*2 Not required if you install Management Server for DPM on the SigmaSystemCenter Management Server.

The following products are not included in SigmaSystemCenter product media:

NEC ESMPRO Agent is not included in SigmaSystemCenter. Use NEC ESMPRO Agent included in NEC EXPRESS series. NEC ESMPRO Agent for Xen Server is available individually. Ask your sales representative for NEC ESMPRO Agent for Xen Server.

Purchase and install the following products as needed. If you are considering to:

Use storage NEC Storage, NEC Storage Manager Integration Base ControlCenter/Symmetrix Manager, SAN Manager, Solutions Enabler Navisphere Manager, Navisphere CLI, Navisphere Agent

Manage the network environment MasterScope Network Manager

Manage a virtual environment Virtualization infrastructure software



2.1.4. Example of System Configuration and Caution In this subsection, an example of the system configuration using SigmaSystemCenter and notes on configuring the system are explained. Configure to set up peripheral devices that you examine to use properly.

Managed Machine

LAN for management LAN for operationFC Cable Firewall


Switch Load Balancer

Managed Machine Group


Storage

Router DHCP Server

SoftwareDistribution Server

Management Server for DPM

SigmaSystemCenterManagement Server

Software Distribution Server

Router

Management Server for DPM

SystemProvisioningNEC Storage Manager Integration Base Solutions Enabler Navisphere CLI Navisphere Agent System Monitor - Performance Monitoring Services NEC ESMPRO Manager NEC ESMPRO Agent Command Line for DPM Web Server for DPM NEC Storage Manager MasterScope Network Manager

DHCPServer

2 System Design


<Notes>

About separating LAN for management and LAN for operation We recommend that you separate LAN for management and LAN for operation in consideration of network load and security. You cannot control VLAN with LAN for management because LAN for management needs to be connected at all times. Also, if you use LAN for management, a mng port needs to be used as an external port. However, we do not recommend using the mng port as a management network for distributing software because the mng port of switch blades has very law transferring rate to other external port.

About using UDP SigmaSystemCenter uses not only TCP but also UDP, such as SNMP, for communication. UDP does not guarantee the packet delivery confirmation, so design the system network to prevent packet loss.

About Management Server for DPM You can install Management Server for DPM on a machine with SystemProvisioning or different machine. If you install Management Server for DPM and SystemProvisioning on different machine, install Command Line for DPM on the machine that you installed SystemProvisioning on. You cannot install multiple instances of Management Server for DPM in a network. Also, the Management Server for DPM can manage only one network. If you set up a server connecting to multiple networks as a DHCP server and install the Management Server for DPM on the server, restrict the network segments provided by the DHCP server to the network segment that is managed by the Management Server for DPM.

About DHCP server To use DPM, a DHCP server is required in the same network as Management Server for DPM. If you do not set up a DHCP server, a part of SigmaSystemCenter features are restricted. Prepare a DHCP server before installing SigmaSystemCenter. You can set up the DHCP server on a machine on which Management Server for DPM is installed or on other machine. If you install a DHCP server on the machine that the Management Server for DPM is installed, you cannot install and use a third party DHCP server. Use a Windows OS standard DHCP server. If you set up a DHCP server on a different machine, you can set up multiple DHCP servers in one network segment.

If you are considering managing Symmetrix storage Solutions Enabler and Symmetrix need to be connected with Fibre Channel (FC.) Connect a SystemProvisioning management server and Symmetrix storage with FC.



The following figure is the example of system configuration of managing virtual environment.

If you install Management Server for DPM and SystemProvisioning on different machines: Install Command Line for DPM on a machine on which you install SystemProvisioning.

SystemProvisioning System Monitor - Performance Monitoring Services NEC ESMPRO Manager VirtualCenter Management ServerCommand Line for DPM

SigmaSystemCenter Management Server

Virtual Machine Server (ESX)

Virtual Machine Server

(Xen Server)

Virtual Machine Server (ESXi)


(Hyper-V)

Management Server for DPM Web Server for DPM DHCP Server

LAN for management LAN for virtual machine connection

DPM Management Server

Managed Machines

Management Console

Firewall

Switch

Virtual Infrastructure ClientXenCenter Hyper-V Manager

2 System Design


If you install Management Server for DPM and SystemProvisioning on the same

machine:

<Notes>

For virtual machine servers, at least two NICs, NIC for management that connects virtual machine servers with the management server and NIC for virtual machine connection that connects virtual NIC of virtual machines set up on a virtual machine server to a physical network, are required.

The server on which Management Server for DPM is installed needs to be connected to both the LAN for management and LAN for virtual machine connection. Multiple instances of Management Server for DPM cannot be installed in one network.

About Hyper-V Manager Hyper-V Manager is required to manage Hyper-V. You can install Hyper-V Manager on Vista or Windows Server 2008. If the host OS of Hyper-V is not Server Core, you can use Hyper-V Manager on the host OS from the remote desktop.

Virtual Machine Server (ESX)


(Xen Server)

Virtual Machine Server (ESXi)


(Hyper-V)

SystemProvisioning System Monitor - Performance Monitoring Services NEC ESMPRO Manager VirtualCenter Management Server Management Server for DPM Web Server for DPM DHCP Server

LAN for management LAN for virtual machine connection

Managed Machines

Management Console

Firewall

Switch

Virtual Infrastructure ClientXenCenter Hyper-V Manager

SigmaSystemCenter Management Server

Product Architecture and License of SigmaSystemCenter


2.2. Product Architecture and License of SigmaSystemCenter

In this section, an edition and the licenses that SigmaSystemCenter provides are explained.

2.2.1. Edition The feature of SigmaSystemCenter Standard Edition is as follows.

SigmaSystemCenter Standard Edition

This edition supports Windows and Linux servers and clients of Windows XP. SigmaSystemCenter Standard Edition is for a middle-scale system, that can manage the server OS up to 100 units, and the client OS up to 4000 units. In addition, this edition features a configuration control function for machines, storage, network, and virtual machine, which enables you to integrate both machines and clients.

2.2.2. Licenses A license for one management server is included in the SigmaSystemCenter Standard Edition. For one management server, one main license is necessary; hence, to add one management server, prepare an additional license for a management server for each management server.

To change manage the virtual environment, you need Virtual Server Management Option.

Adding SigmaSystemCenter Enterprise License to the SigmaSystemCenter Standard Edition to upgrade enables you to manage the unlimited numbers of OSs in SigmaSystemCenter. In addition, SigmaSystemCenter Enterprise License includes the Virtual Server Management Option; you do not need to purchase this license besides the SigmaSystemCenter Enterprise License.

SigmaSystemCenter have two kinds of target licenses.

OS Target License The number of required target licenses of SigmaSystemCenter is corresponded to the number of active OSs. Prepare target licenses for the number of OSs that you are going to use with SigmaSystemCenter.

VM Host Socket License A license that is specialized for virtualization environment management. This license corresponds to the number of CPU sockets of your VM hosts (virtual machine servers.) Prepare the licenses for each CPU socket on VM hosts to be activated with SigmaSystemCenter. You do not need to prepare OS Target Licenses for each virtual machine running on a VM host.

To manage a virtualization environment, choose which to use in OS Target License or VM Host Socket License.

2 System Design


If you are going to distribute software products to managed machines using SigmaSystemCenter, check how many license you need for each product. The license system differs according to the product.

In addition, SigmaSystemCenter provides the following optional licenses. Prepare the license according to your operation plan.

Virtual Server Management Option

This option enables the virtual environment management function. This is included in SigmaSystemCenter Enterprise License.

Management Server Clustering License This license is for operating a management server in the cluster configuration. You need this license for each unit of a stand by server.

Flow of Operating SigmaSystemCenter


2.3. Flow of Operating SigmaSystemCenter In the previous chapters, we have explained the summery of SigmaSystemCenter. Start setting up SigmaSystemCenter through the following work flow, referring to the corresponding manuals. 1. Checking the operational environment

After you have determined how to configure your system, check if the operational environment of SigmaSystemCenter suitable for your environment.

See Chapter 3, "Operational Environment."

2. Installing SigmaSystemCenter Install SigmaSystemCenter to your management server and managed machines according to the determined configuration.

See Chapter 2, "Installing SigmaSystemCenter" in SigmaSystemCenter Installation Guide.

3. Setting up Compatible Products

Set up compatible products that you determine to use. If you have already set up the environment, you do not need to set up again. • Setting up the network devices

Set up the network devices that are controlled from SigmaSystemCenter. Register switches and a load balancer to MasterScope Network Manager. See Section 2.2, "Configuring Settings for a Switch" or Section 2.3, "Configuring Setting for a Load Balancer" in SigmaSystemCenter Configuration Guide or product manuals of MasterScope Network Manager.

• Setting up the storage management software Using storage management software, configure settings for storage to be managed by SigmaSystemCenter or set up disk volumes. See Section 2.4, "Configuring the Setting for Storage" in SigmaSystemCenter Configuration Guide for confirming the setup flow, and for the procedure, see product manuals of your storage management software.

• Setting up the VM environment Set up a VM environment and create a master VM. See Section 2.9, "Preparing for the Use of VMware" and Section 2.10, "Creating a Template Using a Master VM in VirtualCenter," Section 2.11, "Preparing for the Use of Xen" and Section 2.12, "Creating a Template Using a Master VM in XenCenter," 2.13, "Preparing for the Use of ESXi," or 2.14, "Preparing for the Use of Hyper-V" in SigmaSystemCenter Configuration Guide for confirming the setup flow, and for the procedure, see product manuals of VMware, Inc., Citrix Systems, Inc., or Microsoft Corp.

• Setting up for Out-of-Band (OOB) Management Configure settings to BMC to use the OOB Management. See Section 2.15, "Preparing for the Use of Out-of-Band (OOB) Management" in SigmaSystemCenter Configuration Guide.

2 System Design


4. Configuring the initial settings to monitor system performance

Configure the initial settings of System Monitor - Performance Monitoring Services to monitor usage status or management status of machine resources in real-time and execute a recovery action, such as Scale Out. SystemProvisioning configuration information can be applied to System Monitor - Performance Monitoring Services. The information can be applied manually or automatically.

See Section 2.5, "Configuring the Setting for Monitoring Performance by System Monitor - Performance Monitoring Services" in SigmaSystemCenter Configuration Guide or System Monitor - Performance Monitoring Services User’s Guide.

5. Configuring the initial settings of DPM SigmaSystemCenter can install OS, applications, patches to managed machines, or start up or shutdown the machines using DPM; to perform these functions, you need to register managed physical machines to DPM in advance. Configure the initial settings of DPM and register the managed machines to DPM.

See Section 2.7, "Configuring DPM" in SigmaSystemCenter Configuration Guide or DeploymentManager Basic User’s Guide.

6. Configuring the initial settings of SigmaSystemCenter Start up the Web Console and register license keys and users on the Management view.

See Chapter 1, "Preparing Before Setting up the System" in SigmaSystemCenter Configuration Guide.

7. Adding subsystems Register compatible products that manage resources to use as a subsystem. Register compatible products, such as DPM, from the Subsystem of the Management view.

See Chapter 3.2, "Adding a Subsystem" in SigmaSystemCenter Configuration Guide.

8. Beginning managing machines Register machines to be managed in SigmaSystemCenter in the Resource view on the Web Console. To register machines in the Resource view on the Web Console, select physical machines or virtual machines that are managed in DPM, VMware Virtual Center, and XenServer Pool Master, which are registered as subsystems. You can start up or shut down the registered machines.

See Section 3.6, "Registering a Machine" in SigmaSystemCenter Configuration Guide.

To begin managing ESXi or Hyper-V, create a virtual manager of ESXi or Hyper-V and add virtual machine servers in the virtual manager to a datacenter in the Virtual view. You can perform operations, such as power operation of ESXi or Hyper-V registered as a management target, creating a virtual machine on ESXi or Hyper-V, and power operation of the virtual machine.

See Subsection 3.7, "Managing ESXi and Hyper-V" and 3.7.2, "Adding a Virtual Machine Server" in SigmaSystemCenter Configuration Guide.

To enable the power control function by OOB Management, register an account of the OOB Management to a managed machine. This operation can be executed with the ssc command.

See Section 3.8, "Enabling Power Control Function by Out-of-Band (OOB) Management" in SigmaSystemCenter Configuration Guide.

Flow of Operating SigmaSystemCenter


9. Registering the network devices or storages

Register network devices and storage to be managed by SigmaSystemCenter in the Resource view on the Web Console. Select network devices that are registered to MasterScope Network Manager or storage management servers as subsystems to register them in the Resource view on the Web Console.

See Section 3.3, "Registering a Switch," Section 3.4, "Registering a Load Balancer," and Section 3.5, "Registering Storage" in SigmaSystemCenter Configuration Guide.

10. Creating scenarios A setting file that is used to install OS and applications when adding a machine by Scale Out or when restoring failure by Replacing Machine is called a scenario. Create scenarios in DPM. The created scenarios are reflected to the Software on the Resource view on the Web Console.

See Section 2.8, "Creating a Scenario Using a Master Machine in DPM" in SigmaSystemCenter Configuration Guide.

11. Creating templates Create templates to create virtual machines based on a master VM. You can create a template on the Web Console, VirtualCenter, or XenCenter. A template for Hyper-V and standalone ESXi can be created from SigmaSystemCenter. To create a template on the Web Console, you can create the template in the Virtual view. The created template is reflected to the Software of the Resource view on the Web Console.

See Subsection 5.2, "Creating a Template" in SigmaSystemCenter Configuration Guide.

To create a template on VirtualCenter or XenCenter, create the template from each VM environment.

See Section 2.10, "Creating a Template Using a Master VM in VirtualCenter" or Section 2.12, "Creating a Template Using a Master VM in XenCenter" in SigmaSystemCenter Configuration Guide for confirming the setup flow, and for the procedure, see product manuals of VMware, Inc. and Citrix Systems, Inc.

12. Creating Recovery Process Settings Set up process SigmaSystemCenter executes automatically when a failure is generated in the System. For example, to execute Scale Out, you need to configure the setting, such as "Add a machine to a group if the high load status is reported from System Monitor - Performance Monitoring Services." We call these settings policies. You can configure the policy in the Management view on the Web Console.

See Section 3.9, "Creating a Policy" in SigmaSystemCenter Configuration Guide.

13. Creating groups SigmaSystemCenter manages grouping multiple managed machines for the same use as a group. Register the created scenarios, templates and Recovery Process Settings to the group so that SigmaSystemCenter can operate following the Recovery Process Settings. Create groups in the Operation view on the Web Console.

See Section 4.3, "Adding an Operation Group" in SigmaSystemCenter Configuration Guide.

2 System Design


14. Activating machines in a group

Activate machines in the group. SigmaSystemCenter start operating the machines following the Recovery Process Settings.

See Section 6.2, "Activating a Machine in a Group" in SigmaSystemCenter Configuration Guide.

35

PPaarrtt IIII SSiiggmmaaSSyysstteemmCCeenntteerr LLaatteesstt IInnffoorrmmaattiioonn

This section describes the latest SigmaSystemCenter information. The latest information includes the hardware and software operating environments and the latest releases of enhanced points. • 3 Operational Environment • 4 Latest Version Information

37

3. Operational Environment Design the system with a sufficient understanding of the system conditions and hardware environment before installing SigmaSystemCenter. This chapter explains the operating environments of the SigmaSystemCenter. This chapter contains the following sections: • 3.1 Version Information of SigmaSystemCenter .............................................................38 • 3.2 Management Server ..................................................................................................39 • 3.3 Managed Machine – Physical Machine .....................................................................41 • 3.4 Manageable Virtual Machine Infrastructure...............................................................44 • 3.5 Managed Machine – Virtual Machine ........................................................................46 • 3.6 Network Devices........................................................................................................47 • 3.7 Storage ......................................................................................................................48

3 Operational Environment


3.1. Version Information of SigmaSystemCenter

The following table provides the version information of SigmaSystemCenter 2.1:

Edition and License Function Version

Standard Enterprise

SystemProvisioning 5.1 Included Included

DeploymentManager Ver5.21 Included Included

NEC ESMPRO Manager Ver4.42 Included Included ESMPRO

NEC ESMPRO Agent *1

System Monitor - Performance Monitoring Services 4.1.1 Included Included

*1 NEC ESMPRO Agent is not included in the package of SigmaSystemCenter. NEC ESMPRO Agent for each Windows and Linux comes with EXPRESSBUILDER that is included in the NEC Express series. NEC ESMPRO Agent for VMware and XenServer needs to be purchased individually.

Management Server

Part II SigmaSystemCenter Latest Information 39

3.2. Management Server In this section, system requirements of management server are explained.

3.2.1. System Requirements You need the following system requirements to your management server to operate the standard functions of SigmaSystemCenter. If SigmaSystemCenter and the compatible products use the same management server, the system requirements for the compatible products must be met. For information of the system requirements for the Virtual Environment Management function, see Subsection 3.4, "Manageable Virtual Machine Infrastructure."

CPU Intel Compatible, 2 GHｚ 2 Core or greater

Memory Capacity 2 GB or greater

Disk Capacity *1 2 GB or greater

Network Interface Card 1Gbps

OS Windows Server 2003 Standard Edition (x86) SP1 / R2 / SP2 / R2 SP2 Windows Server 2003 Enterprise Edition (x86) SP1 / R2 / SP2 / R2 SP2 Windows Server 2008 Standard (x86) noSP / SP2 *4 Windows Server 2008 Enterprise (x86) noSP / SP2 *4

Display Resolution 1024 × 768 pixels or greater

Required Software ASP.NET 2.0 IIS 6.0 or later version .NET Framework 3.5 Service Pack 1 *3 Web browser *2

Reference ▪ A DHCP server is required on the same network with Management Server for DPM. ▪ If you install DPM on your management server, you need JRE (32-bit Java Runtime Environment) 6.0 Update 7. *5 ▪ If you install Web Server for DPM on your management server, you need Tomcat 6.0.16. *6

*1 ▪ This is the capacity that is needed to install SigmaSystemCenter components; SystemProvisioning, NEC ESMPRO Manager, System Monitor - Performance Monitoring Services, DPM, and instances of SQL Server 2005, and .NET Framework 3.5 Service Pack 1. ▪ Disk capacity for database used by SigmaSystemCenter is required separately. ▪ DPM may need disk capacity separately, depending on the component that you install. In addition, disk capacity for the actual storage size of the installation data and backup image is required separately. For more details, see Section 1, "Before Installing DPM" in DeploymentManager System Introduction. ▪ If you install compatible products on your management server, disk capacity for the products is needed separately.



*2 We have verified the Web Console operations on Internet Explorer 6, 7, and Firefox 3 and 3.5.

*3 The SigmaSystemCenter installer installs .NET Framework 3.5 Service Pack 1,

*4 Supports only the Full Installation.

*5 This product includes JRE6.0 Update7.

*6 This product includes Tomcat 6.0.16.

Managed Machine – Physical Machine


3.3. Managed Machine – Physical Machine In this section, system requirements and settings you should check if you enable DPM control of physical machines that are managed in SystemProvisioning and power control by the Out-of-Band Management are explained.

3.3.1. System Requirements The following table shows the system requirements of managed physical machines. For a managed physical machine, you need to use a machine that supports WOL (Wake On LAN). Out-of-Band management power control supports only a physical machine which has Baseboard Management Controller (BMC) and supports RMCP/RMCP+. Requirements of CPU, memory capacity and disk capacity of a machine are based on the regulations of each OS and applications on the machine. Follow the regulations in configuring.

Network Interface Card 100 Mbps or faster

OS *1 *2 Windows 2000 Server SP4 *3 Windows 2000 Advanced Server SP4 *3 Windows Server 2003 Standard Edition noSP / SP1 / R2 / SP2 /R2 SP2 Windows Server 2003 Standard x64 Edition noSP / R2 / SP2 / R2 SP2 Windows Server 2003 Enterprise Edition noSP / SP1 / R2 / SP2 / R2 SP2 Windows Server 2003 Enterprise x64 Edition noSP / R2 / SP2 / R2 SP2 Windows Server 2003 Enterprise Edition for Itanium-based Systems noSP / SP1 / SP2 Windows Server 2008 Standard (x86) SP1 / SP2 *4 Windows Server 2008 Standard (x64) SP1 / SP2 *4 Windows Server 2008 Enterprise (x86) SP1 / SP2 *4 Windows Server 2008 Enterprise (x64) SP1 / SP2 *4 Windows Server 2008 for Itanium-based Systems SP1 / SP2 *5 Red Hat Enterprise Linux ES 3 (32bit) Red Hat Enterprise Linux AS 3 (32bit) Red Hat Enterprise Linux AS 3 (EM64T) Red Hat Enterprise Linux ES 4 (32bit) Red Hat Enterprise Linux ES 4 (EM64T) Red Hat Enterprise Linux AS 4 (32bit) Red Hat Enterprise Linux AS 4 (EM64T) Red Hat Enterprise Linux 5 (32bit) Red Hat Enterprise Linux 5 (EM64T) Red Hat Enterprise Linux 5 AP (32bit) Red Hat Enterprise Linux 5 AP (EM64T)



SUSE Linux Enterprise Server 9 Service Pack 3VMware ESX 3.0, 3.5.0, 4.0 VMware ESXi 3.5, 4.0 Citrix XenServer Enterprise Edition 5.0, 5.5 Windows Server 2008 Standard (x64) SP1 / SP2 (Hyper-V environment) Windows Server 2008 Enterprise (x64) SP1 / SP2 (Hyper-V environment)

*1 Managed OS that can be used in your environment is regulated by a type of your target license.

*2 Provided functions differ according to OS supported by the corresponding hardware.

*3 Requires Windows .NET Framework 1.1 or greater.

*4 Supports the Full Installation and Server Core Installation. The Disk Duplication OS Installation function of DPM supports only the Full Installation.

*5 Supports only the Full Installation.

3.3.2. DPM Controllable Environment If you want to control managed physical machines on DPM, confirm the following settings on each server from the BIOS setting screen.

Confirm that the WakeOnLAN settings of the NIC connected to the management network are valid.

Confirm that the PXE boot is valid. The NIC that uses PXE boot is set to start before other NICs and a hard disk start.

In addition, if you run Disk Duplication OS Installation in the environment to which Windows OS is installed, note the following points.

Set up the Windows boot drive in the C drive. If you add or change a drive other than the C drive, the drive letter of the added or changed drive may be changed after Disk Duplication.

If you distribute a master image by Disk Duplication, a drive letter is reassigned when resetting the OS. If you are operating a basic disk, drive letters are reassigned to the drives in the recognized order during the installation according to the specification of Microsoft Corp. For more detailed information or other notices, see the following support technical information of Microsoft Corp.

KB928386 Sysprep functions and known issues Reference: For other notes, see DeploymentManager User’s Guide.

Managed Machine – Physical Machine


3.3.3. Out-of-Band Management Controllable Environment SigmaSystemCenter provides a function to operate power control not by using software on a managed machine, but by communicating with BMC (Baseboard Management Controller) on a managed machine using IPMI (Intelligent Platform Management Interface) on the machine. Enabling this function increases the reliability of a power on operation and makes it possible to execute operations, such as force power off. If you want to control power of machines by the OOB management, confirm the following settings.

An Administrator user is set to BMC of a managed machine and you can log into it. Connection to 623/UDP is not blocked by some obstacle, such as firewall.

Reference: For the preparation to use OOB Management, see Section 2.15, "Preparing for the Use of Out-of-Band (OOB) Management" in SigmaSystemCenter Configuration Guide.



3.4. Manageable Virtual Machine Infrastructure

SigmaSystemCenter can manage the following virtual infrastructures collectively. VMware Xen Hyper-V

In this section, the virtual environment that SigmaSystemCenter supports is explained. Note: You need to purchase Virtual Server Management Option to use the virtual environment management function with SigmaSystemCenter Standard Edition.

3.4.1. Infrastructure of Virtual Machines SigmaSystemCenter supports the following infrastructure or management software of virtual machines.

Infrastructure or Software of Virtual Machines

VMware VirtualCenter 2.5 VMware vCenter Server 4.0 VMware ESX 3.0, 3.5.0, 4.0 VMware ESXi 3.5, 4.0 Citrix XenServer Enterprise Edition 5.0, 5.5 Windows Server 2008 Hyper-V

3.4.2. Manageable Guest OS Guest OSs on an infrastructure of virtual machines that SigmaSystemCenter supports are as follows.

Infrastructure of Virtual Machines Guest OS

VMware ESX / ESXi *1 Windows Server 2008 Standard (x86) SP1 *2 / SP2 Windows Server 2008 Enterprise (x86) SP1 *2 / SP2 Windows Server 2003 noSP / SP1 / SP2 / R2 SP2 Windows Server 2003 Standard Edition R2 (32bit) Windows Server 2003 Enterprise Edition R2 (32bit) Windows 2000 Server SP 4 Windows 2000 Advanced Server SP 4 Windows XP Professional SP 1 Windows XP Professional SP 2 (32bit) Windows XP Professional SP 3 (32bit) Windows Vista Business Windows Vista Ultimate

Manageable Virtual Machine Infrastructure


Windows Vista SP1 / SP2 Red Hat Enterprise Linux ES 3 (32bit) Red Hat Enterprise Linux AS 3 (32bit) Red Hat Enterprise Linux ES 4 (32bit) Red Hat Enterprise Linux AS 4 (32bit) Red Hat Enterprise Linux AS 5 SUSE Linux Enterprise Server 9 Service Pack 3SUSE Linux Enterprise Server 10

Citrix XenServer Enterprise Edition Windows 2000 Server SP4 Windows 2000 Advanced Server SP4 Windows Server 2003 Standard Edition SP2 / R2 SP2 Windows Server 2003 Enterprise Edition SP2 / R2 SP2 Windows XP Professional SP3 (32bit) Windows Vista SP2 Windows Server 2008 Standard (x86) SP2 Windows Server 2008 Enterprise (x86) SP2

Windows Server 2008 Hyper-V *4 Windows Server 2008 Standard (x86, x64) SP1 / SP2 Windows Server 2008 Enterprise (x86, x64) SP1 / SP2 Windows Server 2003 Standard (x86) SP2 Windows Server 2003 Standard (x64) SP2 *3 Windows Server 2003 Enterprise (x86) SP2 Windows Server 2003 Enterprise (x64) SP2 *23Windows 2000 Server SP4 Windows 2000 Advanced Server SP4 Windows XP Professional (x86) SP3 Windows XP Professional (x86) SP2 Windows XP Professional (x64) SP2 Windows Vista Business (x86) SP1 / SP2 Windows Vista Business (x64) SP1 / SP2 Windows Vista Enterprise (x86) SP1 / SP2 Windows Vista Enterprise (x64) SP1 / SP2

*1 VMware VirtualCenter does not support creating a virtual machine running Red Hat Enterprise Linux ES/AS 4 or Red Hat Enterprise Linux AS 5 (RHEL4 / 5). Therefore, a RHEL4 / 5 virtual machine cannot be created in SystemProvisioning. However, one that is already created in other software can be managed using SystemProvisioning.

*2 Creating a new virtual machine with the Full Clone method is not supported.

*3 Creating a new virtual machine on Hyper-V using with the HW Profile Clone template method is not supported.

*4 The supported maximum number of virtual CPUs differs on each OS. For the detail, see the following page. http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx

http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx



3.5. Managed Machine – Virtual Machine In this section, settings you should check if you control virtual machines by DPM are explained.

3.5.1. DPM Controllable Environment If you use the following functions, you need to enable the PXE boot function of a target virtual machine; otherwise, you do not need to configure the setting.

Creating a virtual machine using the HW Profile Clone method Using the disk duplication function, the backup function or the restore function

provided by DPM to the virtual machine In that case, confirm the following settings on each machine (other than Hyper-V) from the BIOS settings screen.

Confirm that the PXE boot is valid. The NIC that uses PXE boot is set to start before other NICs and a hard disk start.

A virtual machine on Hyper-V does not have a BIOS screen, so check the following points on the machine.

A legacy network adapter is added. A legacy network adapter is set upper than IDE at the startup order of the BIOS

setting.

Network Devices


3.6. Network Devices In this section, the network management software, and models of switches, switch blades, and load balancers that SigmaSystemCenter supports are explained.

3.6.1. Network Management Software SigmaSystemCenter supports the following network management software that is required when controlling your network environment.

Software MasterScope Network Manager 2.0 and 3.0 MasterScope Network Manager NetworkProvisioning Function License

3.6.2. Support Models of Switches or Switch Blades Reference: Check each product manual for the latest information of support models for a switch for MasterScope Network Manager.

Hardware Model Supported models of MasterScope Network Manager NetworkProvisioning Function License

Required Software MasterScope Network Manager 2.0, 3.0 and MasterScope Network Manager NetworkProvisioning Function License

3.6.3. Support Models of Load Balancers Reference: Check each product manual for the latest information of support models for a load balancer of MasterScope Network Manager.

Hardware Model Supported models of MasterScope Network Manager NetworkProvisioning Function License

Required Software MasterScope Network Manager 2.0, 3.0 and MasterScope Network Manager NetworkProvisioning Function License



3.7. Storage In this section, models of the storage management software and storage that SigmaSystemCenter supports are explained.

3.7.1. Storage Management Software and Support Models of Storage You need an HBA, FC controller, on your managed machine, If you use Symmetrix storage, you need an HBA on your storage management server.

Hardware Model NEC Storage S series NEC Storage D series *1 NEC Storage E series EMC Symmetrix EMC CLARiiON

NEC Storage NEC Storage Manager Ver3 or later NEC Storage Manager Integration Base Ver3.1 or later

Symmetrix ControlCenter/Symmetrix Manager ControlCenter/SAN Manager EMC Solutions Enabler 6.2, 6.4, 6.5

Required Software

CLARiiON Navisphere Agent/CLI FOE 02.24, FOE 03.24, FOE 02.26, FOE 03.26, FOE 02.28, FOE 03.28

*1 If you use the partitioning function of NEC Storage, you can only control in each partition from SigmaSystemCenter. SigmaSystemCenter does not support configuration change over multiple partitions. The partitioning function is a function to set up virtual storage with independent resources by dividing resources, including disks, cache memory, ports, of a disk array according to their logic, such as applications, and manage the virtual storage.

49

4. Latest Version Information This chapter explains the latest information of the SigmaSystemCenter. The features and improvements added to the newest releases are listed. This chapter contains the following sections: • 4.1 New Features and Enhancements ............................................................................50

4 Latest Version Information


4.1. New Features and Enhancements

4.1.1. Enhanced Failure Recovery in Virtual Environment Enabled automatic recovery with failing over ESXi that is managed directory from SigmaSystemCenter without VirtualCenter. When an ESXi is failed, SigmaSystemCenter recovers the system automatically by restarting virtual machines on other sound ESXi. This can be done without VirtualCenter, which consequently realized a low-cost practical virtualization environment. In addition, in Xen Server, automatic recovery of Pool Master with failover is now available. When failure occurred on a Pool Master, SigmaSystemCenter executes failover automatically with a Slave host graded up to Pool Master.

4.1.2. Enhanced Operation Management In this release, the operation management function of SigmaSystemCenter is enhanced centering around functions required to manage a large-scale environment. This enables to reduce burden in setting up the system and realizes operational improvement of the Web Console.

Enhanced the ssc command along with the SystemProvisioning setup procedure. Operations that previously you needed to set for each machine can be now executed with this command.

You can now create multiple Host Settings simultaneously from the Web Console besides the ssc command.

About the Host setting registered in an operation group, this release supports the function to show a list of the settings without opening the Property window.

From this release, you can exports contents of a configured policy to an xml file, import the information, and use it when setting up the environment. Importing and exporting policies can be executed with the ssc command.

When a failure is detected on a managed machine, SigmaSystemCenter raises a failure flag besides an icon of a target machine. Previously, the flag was put only to a target machine; however, with this release, it is also put to a category and group to which the target machine belongs, which simplifies specification of failing place.

4.1.3. Tag VLAN Setting This release enables a Tag VLAN setting of a network switch. You can change a VLAN setting as needed in failure recovery or scale of with a spare machine. For this function, MasterScope Network Manager is required.

4.1.4. Power Control This release adds support for the power control function with IPMI. This enables you to execute starting and stopping a machine certainly. In addition, even if a failed server is stalled, SigmaSystemCenter can force power off the machine.

New Features and Enhancements


4.1.5. Enhanced Optimized Placement and Optimized Startup Optimized process of when starting up multiple virtual machines concurrently is

demanded to multiple virtual machine hosts. For example, to start 20 virtual machines each on four hosts, previous releases executed starting up 20 virtual machines on each host. This release executes the process of starting up 5 virtual machines to four hosts at the same time and repeats this process four times at intervals. This can reduce load on a host at one time so the time to complete starting up all machines can be shortened.

This rerelease adds support for the function to place virtual machines according to placement rules, which enables to activate, assigning a specific virtual machine to a specific host. With the following settings, operations such as preventing both virtual machine hosts and virtual machines to be down due to hardware failure become possible. • Aggregating virtual machines regarding a specific service to one host • Assigning virtual machines that you want to avoid stopping simultaneously to

each different host. If high load is detected on a virtual machine host (VMware ESX or XenServer),

SigmaSystemCenter moves virtual machines on the virtual machine host to other host with low load by Live Migration to distribute load. At this timing, if there is no virtual machine host to which the virtual machines can be moved in an operation group, SigmaSystemCenter can scale out, that is, adding machines to activate in a group. This enhancement is added in this release.

4.1.6. New Target License Release A license specialized for virtualization environment management. Activating virtual machines unlimitedly on one virtual machine host is now available by preparing licenses for the number of CPU sockets to be loaded on the virtual machine host.

4.1.7. Enhanced Policy Function Now you can execute local scripts as actions of a policy. Also you can set a startup condition of actions. This allows you to specify recovery actions flexibly.

4.1.8. VMware vSphere 4.0 Support From this release, VMware vSphere 4.0 can be managed in SigmaSystemCenter. SigmaSystemCenter Update 2 supports only existing functions in VMware Infrastructure 3 and virtual machine server provisioning, which is a function to execute from installing virtualization software to configuration automatically to a spare server, is not supported for ESX 4.0.

53

AAppppeennddiixx • Appendix A Glossary • Appendix B Revision History

55

Appendix A Glossary

A

API Abbreviation for Application Program Interface.

B

Blade Server Refers to a model of Express5800/BladeServer series that supports SystemProvisioning.

Blade Server Enclosure Unit Refers to a chassis that store CPU blades of a blade server.

BMC Abbreviation for Baseboard Management Controller.

C

CLARiiON A name of a storage product of EMC Corporation.

CLI Abbreviation for Command Line Interface.

Client Service for DPM A component of DPM. Client Service for DPM is installed to DPM managed machines to manage DPM managed machines.

Command Line for DPM A component of DPM. Command Line for DPM is a function from which a user can instruct Management Server for DPM to check the status of DPM managed machine and execute various process to DPM managed machine by entering a command from a key board.

Configuration Database A database to store data, such as system resources managed by SystemProvisioning. SQL Server 2005 is used as the database engine.

CPU Blade Refers to one blade of a blade server.

D

Datacenter A kind of group that can unify virtual machine servers. When managing the VirtualCenter environment, datacenters in SigmaSystemCenter corresponds to datacenters in VirtualCenter. When managing the Xen environment, you can create one datacenter in a Pool.

DHCP Server Abbreviation for Dynamic Host Configuration Protocol. This is a server with the function to dynamically assign an IP address to a computer in a network. A predetermined IP address, subnet mask, domain name and other information are assigned upon request from a DHCP client.

Disk Volume In SigmaSystemCenter, disk volume refers to a logical disk composed of multiple physical disks and recognized as one disk.

Appendix A Glossary


DPM Abbreviation for "DeploymentManager." DPM distributes and updates software, such as the OS, applications, and patches to managed machines, and starts or stops machines by the instruction of SystemProvisioning.

E

ESX A product of VMware Inc. that implements a virtual machine.

G

Group A set of machines used for the same service. By managing multiple machines as a group, the load and costs on the machine management can be reduced.

H

HBA Abbreviation for Host Bus Adapter. Refers to the FibreChannel controller.

Hyper-V Refers to the virtualization technology of Microsoft Corporation. This is standardly integrated in Windows Server 2008 (x64) Standard Edition or later.

Hyper-V Manager A Hyper V management console which is standardly provided by Microsoft Corporation.

I

IIS Abbreviation for "Internet Information Services." This is software for internet server provided by Microsoft Corporation.

Image Builder A tool of DPM that creates image files, such as OS, and registers to Management Server for DPM.

Integration Services A component to install on a virtual machine on Hyper-V. Installing this component improves performance and enables you to use additional functions.

IPMI Abbreviation for Intelligent Platform Management Interface, which provides interfaces to acquire information of a sensor, hardware logs and to control target power state.

L

Load Balancer A device that balances load of machines by managing demands from an external network and transferring demands to the target machine. SystemProvisioning supports SS8000, BIG-IP, and ServerIron series.

Local Script Function A function that executes an execution file, which is called a local script, in .bat format on a SigmaSystemCenter management server. This is used when you adding, changing usage, or replacing a machine, and if you want to perform specific processes that depend on system configuration or environment on the SigmaSystemCenter management server.

Appendix 57

M

Machine A generic name of a physical machine and virtual machine that can be managed by SigmaSystemCenter.

Management Server for DPM A component of DPM that manages DPM managed machines. Management Server for DPM executes process to managed machines by instructions from DPM Web Console.

MasterScope Network Manager Software for managing operations using networks. This software is used for controlling and grasping configuration of network devices.

N

NEC ESMPRO Manager NEC ESMPRO Agent

These are the machine management software included in Express5800 series.

NEC Storage A name of storage product of NEC.

NEC Storage Manager The generic name of the NEC Storage management software that is used for controlling storage by SystemProvisioning.

NIC Abbreviation for Network Interface Card. Standard built-in server or an optional adapter for LAN.

O

OOB Abbreviation for Out-of-Band. This is a management method to manage and operate HW not through communication with software which is working on the HW, but directory.

OS Abbreviation for operating system.

P

PackageDescriber A component of DPM. PackageDescriber is a tool for creating a package and registering the package to Web Server.

Package Web Server A web server of DPM for sharing a package created with PackageDescriber.

PCI Slot An opening for inserting a PCI card to a motherboard.

Physical Machine A generic name for hardware machines that has an entity. In SigmaSystemCenter manuals, a physical machine includes a general machine, blade server, and virtual machine server.

PXE Boot Abbreviation for Preboot eXecution Environment. A BIOS function to start a server or install an operating system using the network. This is used by DPM to detect servers and distribute software.

Appendix A Glossary


R

RMCP/RMCP+ Abbreviation for Remote Management Control Protocol. This is a protocol that executes directions of IPMI through networks and uses UDP.

Recovery Process Setting A configuration that process of restore to be executed when an event is generated. With SystemProvisioning, we call this configuration a policy.

S

SAN Abbreviation for Storage Area Network. With a storage dedicated network, this provides storage to machines.

SNMP Trap SNMP Agent’s notifying events to a manager through communication on the SMNP, Simple Network Management Protocol.

SQL Server 2005 Management software of Microsoft Corporation for configuring and operating a relational database.

Switch The generic name of switches and switch blades managed by MasterScope Network Manager.

Switch Blade Refers to a switch that can be built in a blade enclosure.

SYMCLI Command line interface to manage Symmetrix of EMC Corporation.

Symmetrix A name of a storage product of EMC Corporation.

System Monitor - Performance Monitoring Services

Software that monitors the usage status of machine resources. In case of a performance failure, System Monitor - Performance Monitoring Services can send an alert to SystemProvisioning.

SystemProvisioning A package to change configuration of machines. SystemProvisioning is the core of SigmaSystemCenter.

T

Task Scheduler An automatic running utility program that is included in a Windows OS. By using Task Scheduler, a program can be executed automatically at the time you set in advance.

Threshold The monitoring functions of SigmaSystemCenter, such as NEC ESMPRO and System Monitor - Performance Monitoring Services, judges an error or normal by comparing data of managed machines and threshold

V

VirtualCenter A product of VMware Inc. that manages multiple ESXs and virtual machines on ESXs collectively.

VirtualCenter Management Server

A product of VMware, Inc. that is a service that operates as a central administrator for VMware servers connected to networks. VirtualCenter Management Server instructs process to virtual machines or virtual machine servers.

Appendix 59

Virtual Infrastructure Client A product of VMware, Inc. that has the user interface from which a user can create, manage, and monitor virtual machines and resources on a virtual machine.

Virtual Machine Refers to a virtual machine that is implemented on a virtual machine server.

Virtual Machine Server Refers to a server that implements virtual machines. SystemProvisioning can manage ESX and ESXi of VMware, Inc., Xen Server of Citrix Systems, Inc., and Hyper-V of Microsoft Corp.

Virtual Manager A group that unifies datacenters. When managing standalone ESXi or Hyper-V, create a virtual manager from SystemProvisioning. When managing the VirtualCenter environment or Xen environment, VirtualCenter or XenServer Pool Master is a virtual manager.

VLAN A technology that divides a network into multiple broadcast domains by configuring a logical network configuration other than a physical network configuration.

W

Web Console There are two Web Consoles; a component of SigmaSystemCenter and a component of DPM. In this manual, a word Web Console refers to the Web Console of SigmaSystemCenter. Web Console of SigmaSystemCenter is a console for configuring and operating SigmaSystemCenter from a browser. Web Console of DPM is a browser from which a user can operate Management Server for DPM. In SigmaSystemCenter manuals, the Web Console of DPM is described as DPM Web Console.

Web Server for DPM A component of DPM. Web Server for DPM connects Management Server for DPM and Web Console / Command Line for DPM, and transfers processes.

WOL (Wake On LAN) A function that power on a computer connected to LAN from other computer.

X

XenCenter A product of Citrix Systems, Inc. that manages multiple Xen Servers and virtual machines on Xen Servers collectively.

XenServer Pool Master A Xen Server to be specified as a communication base when managing multiple Xen Servers as a Pool collectively.

XenServer Enterprise Edition A product of Citrix Systems, Inc. that implements virtual machines.

Appendix 61

Appendix B Revision History

Fourth Edition (July 2009): Revised to include the functional enhancements in Update 2.

Added information regarding new features and enhancements

Chapter 4 4.1.1 "Enhanced Failure Recovery in Virtual Environment" 4.1.2 "Enhanced Operation Management" 4.1.3 "Tag VLAN Setting" 4.1.4 "Power Control" 4.1.5 "Enhanced Optimized Placement and Optimized Startup" 4.1.6 "New Target License Release" 4.1.7 "Enhanced Policy Function" 4.1.8 "VMware vSphere 4.0 Support"

Deleted the note by enhanced storage management

Chapter 3 3.7.1 "Storage Management Software and Support Models of Storage"

Added description regarding VM Host Socket License release

Chapter 3 2.2.2 "Licenses"

Added description regarding a power management function by Out-of-Band Management

Chapter 3 3.3.1 "System Requirements" 3.3.3 "Out-of-Band Management Controllable Environment"

Appendix Appendix A "Glossary"

Appendix B Revision History


Third Edition (February 2009): Revised to include the functional enhancements in

Update 1.

Added information regarding new features and enhancements

Chapter 4 4.1.7 "Creating a Virtual Machine by Linked Clone Method" 4.1.8 "Creating and Assigning Xen Server Virtual Machine" 4.1.9 "Enhanced VMotion Compatibility of VMware" 4.1.10 "Collective Configuration for Managed Machine by Commands" 4.1.11 "Virtual Machine Controlling Commands" 4.1.12 "Policy Configuration"

Added and deleted the description regarding Server Core installation support

Chapter 2 2.1.3 "How to Configure Components or Products"

Chapter 3 3.3.1 "System Requirements"

Added information regarding Citrix XenServer 5.0 support

Chapter 3 3.3.1 "System Requirements" 3.4.1 "Infrastructure of Virtual Machines"

Second Edition (November 2008): Revised to include the new network

management function of MasterScope Network Manager.

Modified the description and added a section regarding MasterScope Network Manager

Chapter 1 1.2.11 "Switch Control" 1.2.12 "Load Balancer Control"

Chapter 2 2.1.2 "Functions Enabled by Connecting with Other Products" 2.1.3 "How to Configure Components or Products" 2.3 "Flow to Operating SigmaSystemCenter"

Chapter 3 3.6.1 "Network Management Software" 3.6.2 "Support Models of Switches or Switch Blades" 3.6.3 "Support Models of Load Balancers"

Chapter 4 4.1.4 "Network Management"

Appendix Appendix A "Glossary" Appendix B "Operational Environment of Coordinating Functions"

First Edition (October 2008): New

SigmaSystemCenter 2.1 First Step Guide - nec.com fileSome icons used in this program are based on...

Documents

Transcript of SigmaSystemCenter 2.1 First Step Guide - nec.com fileSome icons used in this program are based on...