SigmaSystemCenter 2.1 Reference Guide by tlyaappjdlag

VIEWS: 24 PAGES: 515

									SigmaSystemCenter 2.1




    Reference Guide

     - Sixth Edition-
Copyright (C) NEC Corporation 2003-2010. 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, 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.
Contents

Preface.................................................................................................................................... ix
  How to Use This Manual....................................................................................................................... ix
  Manual Organization............................................................................................................................. ix
  SigmaSystemCenter Manuals .............................................................................................................. x
  Document Conventions......................................................................................................................... xii
1.     Functions of SigmaSystemCenter ................................................................................ 3
  1.1.         Machine Management ............................................................................................................. 4
     1.1.1.Group Management.................................................................................................................................. 4
     1.1.2.Configuration of Groups and Levels ......................................................................................................... 4
     1.1.3.What Is a Model?...................................................................................................................................... 5
     1.1.4.What Is a Host? ........................................................................................................................................ 6
     1.1.5.What is a Role? ........................................................................................................................................ 6
     1.1.6.To Start Operation With SigmaSystemCenter .......................................................................................... 6
     1.1.7.What is a Pool Machine?.......................................................................................................................... 7
     1.1.8.The Status of Machines............................................................................................................................ 8
  1.2.         Machine Operation by SystemProvisioning ............................................................................. 10
     1.2.1.Machine Configuration Change ................................................................................................................ 10
     1.2.2.Transition of Machine Status .................................................................................................................... 13
     1.2.3.Operations Implemented by Group Management..................................................................................... 16
  1.3.         Functions Regarding Managing Machines .............................................................................. 19
     1.3.1.Machine Identification............................................................................................................................... 19
     1.3.2.Machine State and Failure Monitoring Function ....................................................................................... 19
     1.3.3.Performance Monitoring by System Monitor - Performance Monitoring Services..................................... 20
     1.3.4.What is a Policy? ...................................................................................................................................... 21
  1.4.         Distribution Software Management.......................................................................................... 23
     1.4.1.What Is a Scenario? ................................................................................................................................. 23
     1.4.2.What Is Local Script?................................................................................................................................ 24
  1.5.         Use of a Scenario..................................................................................................................... 25
     1.5.1.Flow from Creating a Scenario to Registering Distribution Software ........................................................ 25
     1.5.2.Distribution Methods and Types of Software ............................................................................................ 26
     1.5.3.Flow from Registering Operating Distribution Software to Activating the Machine ................................... 27
     1.5.4.Flow from Registering Standby Distribution Software to Deleting a Machine ........................................... 29
     1.5.5.Details of Distribution After Registration of Distribution Software ............................................................. 30
     1.5.6.Details of Specified Distribution Software................................................................................................. 34
     1.5.7.Difference Distribution of Distribution Software ........................................................................................ 35
     1.5.8.Redistribution of Software (Distribute All) ................................................................................................. 36
     1.5.9.Use of Master Machine............................................................................................................................. 37
     1.5.10.Registration of Distribution Software to Group ....................................................................................... 38
  1.6.         Use of Local Scripts ................................................................................................................. 40
     1.6.1.Details of Local Scripts ............................................................................................................................. 40
  1.7.         Network Management.............................................................................................................. 44
     1.7.1.What is VLAN? ......................................................................................................................................... 44
     1.7.2.Required Settings on a Switch.................................................................................................................. 44
     1.7.3.Usable VLAN Types ................................................................................................................................. 45
     1.7.4.Control of VLAN........................................................................................................................................ 45
     1.7.5.What is a Load Balancer? ........................................................................................................................ 48
     1.7.6.Settings on a Load Balancer .................................................................................................................... 48
     1.7.7.Control of Load Balancer.......................................................................................................................... 48
  1.8.         Storage Management .............................................................................................................. 53
     1.8.1.System Configuration for NEC Storage .................................................................................................... 54
     1.8.2.System Configuration for Symmetrix ........................................................................................................ 56
     1.8.3.Configuration for CLARiiON ..................................................................................................................... 57
     1.8.4.Connection Control of Disk Volume.......................................................................................................... 58
     1.8.5.Connection Control of NEC Storage (FC Model) Disk Volume................................................................. 60
     1.8.6.Connection Control of NEC Storage (iSCSI Model) Disk Volume............................................................. 62


                                                                                                                                                                 iii
     1.8.7.Necessary Preparation for NEC Storage Control ......................................................................................63
     1.8.8.Connection Control of Symmetrix..............................................................................................................66
     1.8.9.Necessary Preparation for Symmetrix Control ..........................................................................................67
     1.8.10.About Commands Used in Symmetrix Control ........................................................................................69
     1.8.11.Connection Control of CLARiiON ............................................................................................................70
     1.8.12.Necessary Preparation for CLARiiON Control.........................................................................................71
     1.8.13.About Commands Used in CLARiiON Control ........................................................................................74
 1.9.          Pool Machine Used for Configuration Change......................................................................... 75
     1.9.1.Operations of a Pool Machine ...................................................................................................................75
     1.9.2.Conditions to Use a Shared Pool Machine and Machine Name Configuration..........................................76
 1.10.         Changes in Machine Configuration.......................................................................................... 79
     1.10.1.Activating Machine / Allocate Machine (Physical Machine).....................................................................80
     1.10.2.Activating Machine / Scale Out (Physical Machine) ................................................................................81
     1.10.3.Activating Machine / Register Master Machine (Physical Machine) ........................................................83
     1.10.4.Deleting Machine / Release Resource (Physical Machine) .....................................................................85
     1.10.5.Deleting Machine / Scale In (Physical Machine) .....................................................................................86
     1.10.6.Replacing Machine (Physical Machine)...................................................................................................88
     1.10.7.Changing Machine Usage (Physical Machine)........................................................................................92
     1.10.8.Activating Machine / Create and Assign Machine (Virtual Machine) .......................................................96
     1.10.9.Activating Machine / Allocate Machine (Virtual Machine) ........................................................................98
     1.10.10.Activating Machine / Scale Out (Virtual Machine) .................................................................................100
     1.10.11.Activating Machine / Register Master Machine (Virtual Machine) .........................................................103
     1.10.12.Deleting Machine / Release Resource (Virtual Machine) ......................................................................104
     1.10.13.Deleting Machine / Scale In (Virtual Machine).......................................................................................105
     1.10.14.Delete VM .............................................................................................................................................107
     1.10.15.Move Virtual Machine (Virtual Machine)................................................................................................108
     1.10.16.Power Operation to Machine / Start ......................................................................................................111
     1.10.17.Power Operation to Machine / Restart ..................................................................................................112
     1.10.18.Power Operation to Machine / Shutdown ..............................................................................................112
     1.10.19.Power Operation to Machine / Suspend................................................................................................114
     1.10.20.Power Operation to Machine / Power ON .............................................................................................115
     1.10.21.Power Operation to Machine / Power OFF............................................................................................115
     1.10.22.Power Operation to Machine / Reset.....................................................................................................116
     1.10.23.Power Operation to Machine / Power Cycle..........................................................................................116
     1.10.24.Power Operation to Machine / ACPI Shutdown.....................................................................................117
     1.10.25.Power Operation to Machine / Investigate and Power OFF ..................................................................118
 1.11.         About Power Control ................................................................................................................ 119
     1.11.1.Products and Components That Power Control Uses .............................................................................119
     1.11.2.List of Power Control Operations ............................................................................................................126
     1.11.3.Sequences of Power Control...................................................................................................................128
     1.11.4.Setting Timeout Time and Waiting Time .................................................................................................130
     1.11.5.Timeout Time and Waiting Time of Power Control Operations ...............................................................131
     1.11.6.Time Out Period of Power Control Through BMC ...................................................................................133
     1.11.7.Timeout Time of Power Control Through DPM .......................................................................................134
     1.11.8.Timeout Time of Power Control Through Virtual Infrastructure ...............................................................134
 1.12.         About Other Maintenance Operations ..................................................................................... 138
2.     About Virtual Environment Management......................................................................141
 2.1.          System Configuration............................................................................................................... 142
     2.1.1.Hyper-V Environment ................................................................................................................................142
     2.1.2.System Configuration of Hyper-V Cluster..................................................................................................144
     2.1.3.Configuring Cluster in Hyper-V Environment.............................................................................................146
 2.2.          Creation of Virtual Machine...................................................................................................... 148
     2.2.1.Templates .................................................................................................................................................149
     2.2.2.Customization of Devices Assigned For VM (Machine Profile) .................................................................151
     2.2.3.Usage Example of Machine Profile ...........................................................................................................153
     2.2.4.Machine Profile Definitions in Levels.........................................................................................................154
     2.2.5.CPU Settings.............................................................................................................................................155
     2.2.6.Memory Settings .......................................................................................................................................156
     2.2.7.Network Settings .......................................................................................................................................157
     2.2.8.System Disk Settings ................................................................................................................................158
     2.2.9.Extended Disk Settings .............................................................................................................................158
 2.3.          Full Clone ................................................................................................................................. 160
     2.3.1.How to Create Full Clone ..........................................................................................................................161
 2.4.          HW Profile Clone...................................................................................................................... 162
iv
     2.4.1.How to Create HW Profile Clone .............................................................................................................. 163
 2.5.          Differential Clone...................................................................................................................... 164
     2.5.1.How to Create Differential Clone .............................................................................................................. 165
     2.5.2. Revert....................................................................................................................................................... 166
     2.5.3.Reconstruct .............................................................................................................................................. 167
     2.5.4.How to Use Differential Clone When Creating a New Master VM ............................................................ 168
     2.5.5.How to Use Differential Clone When Reconstructing ............................................................................... 169
 2.6.          Disk Clone................................................................................................................................ 170
     2.6.1.How to Create Disk Clone ........................................................................................................................ 171
 2.7.          Machine-Specific Settings in OS Deployment ......................................................................... 173
     2.7.1.About Sysprep .......................................................................................................................................... 173
     2.7.2.Machine-specific settings (Sysprep) ......................................................................................................... 175
     2.7.3.Preparing for Sysprep - DPM - ................................................................................................................. 176
     2.7.4.Preparing for Sysprep - vCenter Server - ................................................................................................. 176
     2.7.5.How to Use Sysprep - OS Deployment, HW Profile Clone (DPM) -.......................................................... 178
     2.7.6.How to Use Sysprep - Full Clone, Differential Clone (vCenter Server) -................................................... 180
     2.7.7.How to Use Sysprep - Disk Clone, Differential Clone (DPM) - ................................................................. 182
 2.8.          Image Management (Differential Clone, Disk Clone) .............................................................. 184
     2.8.1.Images and Replica VMs.......................................................................................................................... 184
     2.8.2.About Images Used When Creating Virtual Machines.............................................................................. 186
     2.8.3.Types of Replica VM ................................................................................................................................ 188
     2.8.4.Names of Images and Replica VMs ......................................................................................................... 190
 2.9.          Snapshot Management............................................................................................................ 191
 2.10.         Virtual Machine Mobility ........................................................................................................... 192
     2.10.1.Hot Migration/Cold Migration .................................................................................................................. 192
     2.10.2.Move....................................................................................................................................................... 193
     2.10.3.Failover................................................................................................................................................... 194
 2.11.         VM Optimized Placement Management .................................................................................. 195
     2.11.1.Capacity Control of the Virtual Machine Server ...................................................................................... 195
     2.11.2.VM Optimized Placement ....................................................................................................................... 195
     2.11.3.Conditions for VM Optimized Placement ................................................................................................ 196
     2.11.4.VM Optimized Creation .......................................................................................................................... 198
     2.11.5.Conditions for VM Optimized Creation ................................................................................................... 200
     2.11.6.VM Optimized Startup ............................................................................................................................ 203
     2.11.7.Example of VM Optimized Startup.......................................................................................................... 204
     2.11.8.VM Optimized Placement Rule............................................................................................................... 206
     2.11.9.Usage Examples of VM Optimized Placement Rule............................................................................... 207
 2.12.         About Virtual Environment ....................................................................................................... 210
     2.12.1.Recovery Action for Virtual Machine Server Down ................................................................................. 210
     2.12.2.Recovery Action for HW Predictive Alert ................................................................................................ 212
     2.12.3.About Monitoring Virtual Environments .................................................................................................. 214
     2.12.4.Server Down Monitoring of Virtual Machine Servers .............................................................................. 215
     2.12.5.Monitoring Hardware of Virtual Machine Servers ................................................................................... 217
     2.12.6.Monitoring Performance of Virtual Machine Servers .............................................................................. 219
     2.12.7.Monitoring System Disks of Virtual Machine Servers ............................................................................. 221
     2.12.8.Monitoring Datastore of ESX .................................................................................................................. 222
     2.12.9.About Failures in Virtual Environments................................................................................................... 227
     2.12.10.Policies in vCenter Server Management .............................................................................................. 230

3.     Details of Action Sequence ........................................................................................... 237
 3.1.          What is Action Sequence?....................................................................................................... 238
 3.2.          Running and Canceling Action Sequence ............................................................................... 238
 3.3.          Types of Action Sequence ....................................................................................................... 239
4.     Command Reference...................................................................................................... 243
 4.1.          Command Line Configuration Control by SystemProvisioning................................................ 244
 4.2.          Pvmutl Command..................................................................................................................... 244
     4.2.1.Conditions to Use pvmutl Commands and Supplementary Information.................................................... 244
     4.2.2.Changing Machine Usage (Moving a Machine) ........................................................................................ 246
     4.2.3.Replacing a Machine ................................................................................................................................ 248
     4.2.4.Adding Machine from Pool to Group......................................................................................................... 249
     4.2.5.Adding Machine from Pool to Group Specifying Host Information ............................................................ 250
     4.2.6.Releasing Machine from a Group to a Pool.............................................................................................. 251

                                                                                                                                                                      v
     4.2.7.Distributing Software in a Group Unit ........................................................................................................252
     4.2.8.Distributing Software Specifying Machine .................................................................................................253
     4.2.9.Executing Specific Software......................................................................................................................254
     4.2.10.Setting Maintenance Mode On or Off ......................................................................................................255
     4.2.11.Displaying Groups in List.........................................................................................................................255
     4.2.12.Displaying Machines Registered to a Group in List .................................................................................257
     4.2.13.Displaying Software Registered to a Group in List ..................................................................................258
     4.2.14.Shutting a Machine Down .......................................................................................................................259
     4.2.15.Rebooting a Machine ..............................................................................................................................260
     4.2.16.Powering On a Machine ..........................................................................................................................261
     4.2.17.Creating a Machine (Creating Machine in Group) (for Virtual Machine) ..................................................262
     4.2.18.Deleting a Machine (for Virtual Machine) ................................................................................................264
     4.2.19.Moving a Machine (Only Migrate) (for Virtual Machine) ..........................................................................265
     4.2.20.Moving a Machine (If Migrate Fails, Move) (for Virtual Machine) ............................................................266
     4.2.21.Job Commands .......................................................................................................................................267
     4.2.22.Changing a Password for a User Account...............................................................................................269
     4.2.23.Outputting Policies in List ........................................................................................................................269
     4.2.24.Changing a Group Policy ........................................................................................................................270
     4.2.25.Output Format of Progressing Status ......................................................................................................271

5.     Error Events and Policy Actions....................................................................................275
 5.1.          Event Monitoring and Policy..................................................................................................... 276
 5.2.          Events SigmaSystemCenter Can Detect ................................................................................. 277
     5.2.1.Events NEC ESMPRO Manager Can Detect ............................................................................................280
     5.2.2.Checking Events that Can Be Detected Through NEC ESMPRO Manager..............................................285
     5.2.3.Events System Monitor - Performance Monitoring Services Can Detect...................................................288
     5.2.4.Events the VMware (vCenter Server) Compatible Function Can Detect ...................................................290
     5.2.5.Events the VMware (ESXi) Compatible Function Can Detect ...................................................................299
     5.2.6.Events the Optimized Placement Function Can Detect.............................................................................300
     5.2.7.Events the Out-of-Band Management Can Detect ....................................................................................300
     5.2.8.Events the Hyper-V Cluster Function Can Detect .....................................................................................322
 5.3.          Policy Setting............................................................................................................................ 325
 5.4.          Configuring Actions .................................................................................................................. 326
     5.4.1.Flow Control of Multiple Actions ................................................................................................................326
     5.4.2.Suppression of Action Execution (Suppression of Error Event) ................................................................328
     5.4.3.Grouping Multiple Events ..........................................................................................................................329
 5.5.          Investigation Function .............................................................................................................. 330
     5.5.1.Investigation Function ...............................................................................................................................330
     5.5.2.Analysis of HW Sensor Conditions............................................................................................................333
 5.6.          About Standard Policy.............................................................................................................. 336
     5.6.1.Settings of a Standard Policy ....................................................................................................................337
     5.6.2.Settings of a Standard Policy (Virtual Machine) ........................................................................................341
     5.6.3.Settings of a Standard Policy (VM Server), Standard Policy (VM Server Predictive), Standard
                  Policy (VM Server Power save) ......................................................................................................343
     5.6.4.Standard Policy (VM Server ESXi) ............................................................................................................346
     5.6.5.Settings of a Standard Policy (VM Server Hyper-V), a Standard Policy (VM Server Hyper-V
                  Predictive) ......................................................................................................................................347
     5.6.6.Settings of a System Policy (Manager) .....................................................................................................350
     5.6.7.Settings of HW Predictive Monitoring Events ............................................................................................352
 5.7.          List of Policy Actions ................................................................................................................ 356
     5.7.1.Notification/ E-mail, Event Log ..................................................................................................................357
     5.7.2.Machine Status / Set Ready Status...........................................................................................................358
     5.7.3.Machine Status / Set Degraded Status .....................................................................................................358
     5.7.4.Machine Status / Set Faulted Status .........................................................................................................359
     5.7.5.Machine Status / Set Faulted Status by an Analysis of HW Sensor Conditions ........................................359
     5.7.6.Action for Machine / Startup Machine .......................................................................................................360
     5.7.7.Action for Machine / Reboot Machine .......................................................................................................360
     5.7.8.Action for Machine / Shutdown Machine ...................................................................................................360
     5.7.9.Action for Machine / Turn on LED .............................................................................................................360
     5.7.10.Action for Machine / Turn off LED ...........................................................................................................360
     5.7.11.Action for Machine / Replace Machine ....................................................................................................360
     5.7.12.Action for machine / Replace machine(Immediate Power OFF)..............................................................360
     5.7.13.Action for machine / Investigate and Power OFF ....................................................................................361
     5.7.14.Action for Group / Add a Machine to the Group ......................................................................................362
     5.7.15.Action for Group / Create a Machine to the Group ..................................................................................362
vi
     5.7.16.Action for Group / Delete a Machine From the Group to Pool ................................................................ 362
     5.7.17.Action for Group / Delete a Virtual Machine From the Group ................................................................. 362
     5.7.18.Action for Group / Startup a Machine in the Group................................................................................. 362
     5.7.19.Action for Group / Suspend a Machine in the Group .............................................................................. 362
     5.7.20.Action for Group / Shutdown a Machine in the Group ............................................................................ 362
     5.7.21.Action for Group / Apply VM Optimized Placement Rule........................................................................ 363
     5.7.22.Action for VMS / Move all running VMs on the VM server. (Failover) ..................................................... 363
     5.7.23.Action for VMS / Move all running VMs on the VM server. (Hot Migration) ............................................ 363
     5.7.24.Action for VMS / Move all running VMs on the VM server. (Hot Migration, Failover).............................. 364
     5.7.25.Action for VMS / Move all VMs on the VM server. (Failover) .................................................................. 364
     5.7.26.Action for VMS / Move all VMs on the VM server. (Hot Migration / Cold Migration) ............................... 364
     5.7.27.Action for VMS / Move all VMs on the VM server. (Hot Migration / Cold Migration, Failover)................. 365
     5.7.28.Action for VMS / Power Save VM server ................................................................................................ 365
     5.7.29.Action for VMS / Load Balance VM server ............................................................................................. 365
     5.7.30.Action for VMS / Apply VM Optimized Placement Rule .......................................................................... 366
     5.7.31.Execute Local Script............................................................................................................................... 366

6.     Caution Notes ................................................................................................................. 367
 6.1.          Software Distribution and Update Function ............................................................................. 368
     6.1.1.Notes for Environment Setup When Executing OS Installation by Disk Duplication ................................. 368
     6.1.2.Acquiring Update Authority....................................................................................................................... 368
     6.1.3.Installing Management Server for DPM.................................................................................................... 369
     6.1.4.Creating Scenarios ................................................................................................................................... 369
     6.1.5.Distributing Scenarios............................................................................................................................... 369
     6.1.6.Creating a Disk Image .............................................................................................................................. 369
     6.1.7.Password of Management Server for DPM .............................................................................................. 370
     6.1.8.About the Detailed Settings for Management Server for DPM ................................................................. 370
     6.1.9.Procedure to Add the Full Backup Operation ........................................................................................... 370
     6.1.10.About Running a Restore Scenario in SystemProvisioning .................................................................... 370
     6.1.11.About Suspending a Scenario Run by SystemProvisioning ................................................................... 371
     6.1.12.About Machine Name After Deleting Subsystems of Other Than DPM .................................................. 371
 6.2.          Virtual Environment Management Function............................................................................. 372
     6.2.1.About System Configuration ..................................................................................................................... 372
     6.2.2.About Setting Up the Virtual Environment (Setting for Compatible Product) ............................................ 374
     6.2.3.About Setting Up the Virtual Environment (Registering and Setting Compatible Product to
                 SigmaSystemCenter)..................................................................................................................... 378
     6.2.4.About Setting of Virtual Machine .............................................................................................................. 382
     6.2.5.About Operations on Virtual Machine Server ........................................................................................... 384
     6.2.6.About Template ........................................................................................................................................ 386
     6.2.7.About Operations to Virtual Machine ........................................................................................................ 387
     6.2.8.About Roll Back Server After Restoring Failure of Virtual Machine Server............................................... 393
     6.2.9.About Errors ............................................................................................................................................. 395
     6.2.10.Other Notes ............................................................................................................................................ 396
 6.3.          Notes on Operating MasterScope Network Manager .............................................................. 399
     6.3.1.About Functional Differences According to Versions................................................................................ 399
     6.3.2.About Operations for Switch Devices ....................................................................................................... 399
     6.3.3.Procedures on how to Recover When Port Assignment to VLAN or Releasing Port-VLAN
                 Assignment Fails ........................................................................................................................... 400
     6.3.4.Notes for Failure in Addition or Deletion of Load Balancers ..................................................................... 405
     6.3.5.About Physical Ports configured as Trunk, Link Aggregation and Port Channel ...................................... 406

7.     Trouble Shooting ............................................................................................................ 407
 7.1.          Coping With Error..................................................................................................................... 408
 7.2.          Trouble Shooting in SystemProvisioning ................................................................................. 409
     7.2.1.The Multiple Screens Become Variant Due to Operations From Multiple Browsers ................................. 409
     7.2.2.If You Cancel Running Process of Activating Machine or Making a Machine Stand by, or the
                  Process Fails, Status of Machine Does Not Return to the Status Before Execution...................... 409
     7.2.3.Cannot Operate Machine After Executing the Clear Installation of Windows OS From
                  SigmaSystemCenter or DPM......................................................................................................... 410
     7.2.4.A NIC or UUID of One Machine Is Registered as Multiple Machines by the Collect Function .................. 411
     7.2.5.Machine Type Is Not Displayed Correctly / Functions Depending on Machine Type Does Not
                  Operate Properly ........................................................................................................................... 412
     7.2.6.Cannot Stop PVM Service........................................................................................................................ 412
     7.2.7.Window Switches to Log In Window Automatically During Operation ...................................................... 413

                                                                                                                                                                vii
       7.2.8.Control Error Due to Wrong Recognition of Machine / Network Inaccessibility of Managed
                    Machine..........................................................................................................................................413
       7.2.9.Datastore Is Not Displayed Properly .........................................................................................................417
       7.2.10.VMware Infrastructure Web Access Does Not Launch / It Repeats Restarting .......................................417
       7.2.11.Cannot Shut Down a Managed Machine Running Windows ...................................................................418
       7.2.12.Distribution of DPM Scenario Registered Before Upgrading Fails ..........................................................418
       7.2.13.Creating a Virtual Machine Times Out.....................................................................................................419
       7.2.14.Creating a Template Times Out ..............................................................................................................420
       7.2.15.XenServer Pool Master Does Not Cognize Startup of XenServer...........................................................420
       7.2.16.Inconsistence Occurred Between SigmaSystemCenter and Actual XenServer Pool Master in
                    the Xen Environment ......................................................................................................................421
       7.2.17.A Virtual Machine Server Is Disconnected After Executing the Recovery Operation ..............................421
       7.2.18.Cannot Find a Movable Virtual Machine Server ......................................................................................422
       7.2.19.ESX Is Damaged and Cannot Use a Related Template..........................................................................423
       7.2.20.After Failover in a Standalone ESXi Environment, Managed Machines That Were Actually
                    Moved From a Virtual Management Server Look As If Not Moved.................................................423
       7.2.21.Cannot Use Differential Clone or Disk Clone Templates If the System Is Updated to
                    SigmaSystemCenter 2.1 Update 3 .................................................................................................424
       7.2.22.Events of Out-of-Band Management Are Not Detected With Displaying "Receiving SNMP Trap
                    is disabled." Message on the Operations Log Window...................................................................424
       7.2.23.Events of Out-of-Band Management Are Not Detected After "SNMP Trap Service stopped."
                    Message Is Displayed on the Operations Log Window. .................................................................425
       7.2.24.Out-of-Band Management Operations Fail..............................................................................................426
       7.2.25.A Virtual Management Server Remains in Maintenance Mode After Executing Switching
                    Operation of XenServer Pool Master..............................................................................................426
       7.2.26.Create and Assign Resource Fails in a Standalone ESXi Environment ..................................................427
       7.2.27.Cannot Use Replica VM Created From Differential Clone / Disk Clone Templates.................................427
  7.3.           Trouble Shooting In Managing Configuration Information ....................................................... 430
       7.3.1.Cannot Access to Database......................................................................................................................430
       7.3.2.When Starting a Management Server, Collect Process of Configuration Information Ends With
                  Warning ..........................................................................................................................................431

8.       Logs..................................................................................................................................433
  8.1.           Types of Logs........................................................................................................................... 434
  8.2.           Event Logs ............................................................................................................................... 435
       8.2.1.Event Logs of SystemProvisioning ............................................................................................................435
       8.2.2.Event Logs Regarding Compatibility With NEC ESMPRO Manager .........................................................451
  8.3.           List of Log Files ........................................................................................................................ 452
       8.3.1.Logs of SystemProvisioning ......................................................................................................................452
       8.3.2.Logs of DPM .............................................................................................................................................453
       8.3.3.Logs of System Monitor - Performance Monitoring Services.....................................................................455
       8.3.4.Logs of NEC ESMPRO Manager ..............................................................................................................456

Appendix A                      Network Ports and Protocols ....................................................................463
  SystemProvisioning .............................................................................................................................. 463
  DeploymentManager............................................................................................................................. 464
  NEC ESMPRO Manager....................................................................................................................... 469
  System Monitor - Performance Monitoring Services ............................................................................ 470
Appendix B                      Transferring the Configuration Database.................................................471
  Using Windows Authentication Login.................................................................................................... 471
  Using SQL Authentication Login ........................................................................................................... 476
Appendix C                      How to Estimate Database Usage .............................................................481
  SystemProvisioning .............................................................................................................................. 481
  System Monitor - Performance Monitoring Services ............................................................................ 484
  DeploymentManager............................................................................................................................. 485
Appendix D                      Glossary ......................................................................................................487
Appendix E                      Revision History .........................................................................................495


viii
Preface
How to Use This Manual
SigmaSystemCenter Reference Guide 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.


Manual Organization
Part I     SigmaSystemCenter Functions Reference

1       "Functions of SigmaSystemCenter": Explains the functions of SigmaSystemCenter
2       "About Virtual Environment Management": Explains the functions to manage virtual
environments.

Part II    How to Use the Commands

3          "Details of Action Sequence": Explains the action sequences.
4          "Command Reference": Explains the commands that can be used in SigmaSystemCenter.

Part III   Maintenance Information

5          "Error Events and Policy Actions": Describes the list of error events that
           SigmaSystemCenter can detect, the list of actions of policies, and the default disposals.
6          "Caution Notes": Lists caution notes of SigmaSystemCenter.
7          "Trouble Shooting": Describes the trouble shooting of SigmaSystemCenter.
8          "Logs": Explains the Event logs that are displayed by SigmaSystemCenter.

Appendix

Appendix A          "Network Ports and Protocols"
Appendix B          "Transferring the Configuration Database"
Appendix C          "How to Estimate Database Usage"
Appendix D          "Glossary"
Appendix E          "Revision History"




                                                                                                   ix
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   Manuals                                    How Manuals Are Called in This
Components                                                               Manual

SigmaSystemCenter 2.1         SigmaSystemCenter 2.1 First Step Guide     SigmaSystemCenter
                                                                         First Step Guide
                              SigmaSystemCenter 2.1 Installation Guide   SigmaSystemCenter
                                                                         Installation Guide
                              SigmaSystemCenter 2.1 Configuration        SigmaSystemCenter
                              Guide                                      Configuration Guide
                              SigmaSystemCenter 2.1 Reference Guide      SigmaSystemCenter
                                                                         Reference Guide
NEC ESMPRO Manager            NEC ESMPRO Manager User’s Guide            NEC ESMPRO Manager
4.5                                                                      User’s Guide
DeploymentManager 5.22        DeploymentManager System Introduction      DeploymentManager
                              Ver.5.2                                    System Introduction
                              DeploymentManager (Basic) User’s Guide     DeploymentManager
                              Ver.5.2                                    Basic User’s Guide
                              DeploymentManager (Advanced) User’s        DeploymentManager
                              Guide Ver.5.2                              Advanced User’s Guide
                              DeploymentManager (PackageDescriber)       DeploymentManager
                              User’s Guide Ver.5.2                       PackageDescriber User’s Guide
System Monitor -              System Monitor - Performance Monitoring    System Monitor - Performance
Performance Monitoring        Services User’s Guide                      Monitoring Services
Services 4.1.1                                                           User’s Guide
                              SigmaSystemCenter SSC Command              SSC Command Reference
                              Reference


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




x
The information regarding product summary, 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 summary, 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.




                                                                                                         xi
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        Type Exit and click Enter.
                   screen, short text input, screen      User License Confirmation screen
                   names, short command-line
                   commands, and command-line            Use the –prt command.
                   options                               Use the /a option.

Italic font        Book or manual titles, and variable   Configuration Guide
                   names                                 add GroupName
Quotation marks    Chapter titles and default values     See Chapter 9, "Add a Computer."
Monospace font     Long text inputs, messages    and     Type the following text:
(courier new)      command-line commands                 Confidential-Class B




xii
Part I                              SigmaSystemCenter
                                    Functions Reference




This part describes the functions of SigmaSystemCenter.

This part contains the following chapter:


•    1          Functions of SigmaSystemCenter ...............................................................................3
•    2          About Virtual Environment Management................................................................ 141




                                                                                                                              1
1.       Functions of SigmaSystemCenter




This chapter explains the functions of SigmaSystemCenter from the overview to detailed information,
such as internal processes.

This chapter contains the following sections:


•    1.1        Machine Management .................................................................................................4
•    1.2        Machine Operation by SystemProvisioning.............................................................. 10
•    1.3        Functions Regarding Managing Machines ............................................................... 19
•    1.4        Distribution Software Management .......................................................................... 23
•    1.5        Use of a Scenario ..................................................................................................... 25
•    1.6        Use of Local Scripts.................................................................................................. 40
•    1.7        Network Management............................................................................................... 44
•    1.8        Storage Management ............................................................................................... 53
•    1.9        Pool Machine Used for Configuration Change ......................................................... 75
•    1.10       Changes in Machine Configuration .......................................................................... 79
•    1.11       About Power Control............................................................................................... 119
•    1.12       About Other Maintenance Operations .................................................................... 119




                                                                                                                                         3
1 Functions of SigmaSystemCenter



1.1. Machine Management
           This section provides the management methods of managed machines with
           SystemProvisioning.



1.1.1.     Group Management
           SystemProvisioning manages multiple machines to be used for the same use as a
           group. By this group management, troublesome operations that used to be needed for
           each machine can be done once you execute the operation to a group once, so that the
           total management cost can be reduced. Also, the group management enables you not
           only to operate without feeling the distance of the remote environment, but also various
           other operations.



1.1.2.     Configuration of Groups and Levels
           A group is configured of categories and groups. You can create multiple levels with
           categories. Using leveled groups, makes to the management of large scale
           environment easier.


            Level 1: Category
               Category groups multiple groups to make group management easier. You cannot
               command operations, such as configuration change or software distribution, to
               categories. If you manage many groups, you can create categories for the groups,
               which reduce the number of groups displayed on the Web Console and makes
               management easier.
               For example, creating a category is useful when you run one service in multiple
               groups, such as a Web group or an Application group; you can define a category
               grouping these groups and create a noticeable category name. You can configure
               the access authority for each category.


            Level 2: Group
               Group is used for grouping multiple machines for one use. You need to define a
               group for one machine. Grouping is the basic concept of machine management of
               SystemProvisioning. Machine configuration change can be executed to this level
               of group. Also, you can hide the unique information of each machine when
               managing machines in groups.
               You can configure the settings of policies, software, VLAN, and load balancer to
               groups.
               A group can be used for its use, such as a Web group and application group.
               In addition, a group can have one pool. A pool is an idea of a group that manages
               a machine that is not activated in a condition that can be activated immediately.
               For details of machines that you can register in the pool, see Subsection 1.1.7,
               "What is a Pool Machine?"
                                                         SigmaSystemCenter 2.1 Reference Guide
4
                                                                            Machine Management




1.1.3.     What Is a Model?
           SystemProvisioning executes the changing configuration process that is suitable to
           each model type that comes from difference of machine type, such as a physical
           machine or virtual machine.
           There are three types of models, as follows. You can register only one type of models
           to a group.


            Physical for physical machines (excluding virtual machine servers)
             To this type of machines, standard configuration changes are executed, including
             software distribution or changing configuration of VLAN, load balancers, and
             storage.
            VM for virtual machines
             To this type of machines, configuration changes for a virtual machine are executed,
             including not only software distribution, but also changing configuration of virtual
             networks to which virtual machines are connected. Changing configuration of
             VLAN, load balancers, and storage is not executed.
            VM Server for virtual machine servers
             To this type of machines, configuration changes for a virtual machine server are
             executed, including software distribution and changing configuration of VLAN, load
             balancers, and storage, as well as virtual machine control, such as VM Optimized
             Placement.


           When you need to execute different changing configuration process to machines in a
           group according to differences, such as machine spec, you can register multiple
           models with the same model types to manage the machines.




Part I SigmaSystemCenter Functions Reference
                                                                                                   5
1 Functions of SigmaSystemCenter




1.1.4.     What Is a Host?
           Information to be assigned to a running machine, such as a host name and IP address,
           is managed as Host Setting.
           You need to define one or more hosts in a group.



1.1.5.     What is a Role?
           Access limitation can be set on categories / groups under the topmost category / group
           only from the Operation view.


           If Administrators link roles with categories / groups, the users who do not own the roles
           cannot access to the categories / groups. Access to categories / groups where roles
           are not configured will be controlled according to the authority that was determined
           when creating users.
           When roles are linked to some categories / groups, only users with the Administrator
           authority can configure and change all categories / groups.


           SigmaSystemCenter provides the following three authorities for users:


           Administrator           Can perform all operations such as configuring or changing the
                                   configuration of SigmaSystemCenter, and starting or stopping machines.

           Operator                Cannot configure or modify SigmaSystemCenter. Can perform
                                   operations for a managed machine such as starting or stopping
                                   machines.

           Observer                Cannot configure or modify SigmaSystemCenter. Cannot perform
                                   operations such as starting or stopping machines. Can check the
                                   statuses of machines, such as the Running Status.




1.1.6.     To Start Operation With SigmaSystemCenter
           To start operation with SigmaSystemCenter, you can either add a machine to a group
           and activate the machine or add a machine to a group pool.


            Adding a machine to a group and activating the machine
               Specify Host Properties registered to a group and allocate a resource to add a
               machine to the group and activate the machine. With SystemProvisioning, you can
               change the configurations, including Replace Machine and Change Machine
               Usage, of a machine that has activated in a group. Because machines are
               managed with their host name and IP address, you can operate by changing their
               configurations freely without paying attention to the existence of resources.
               Use Model Properties when allocating resources to Host Properties.

                                                           SigmaSystemCenter 2.1 Reference Guide
6
                                                                           Machine Management



            Adding a machine to the group pool
               Specify a resource and add a machine to a group pool. When a machine is added
               to a group pool, Model Properties are used.




           You can check active machines in a group or machines in standby in a group pool from
           the Operation view, and unused machines from the Resource view on the Web
           Console. SystemProvisioning stores information related to hosts and resources. If you
           want to refer to hardware information (information of a resource) for hardware
           maintenance, you can check the details of a resource on the Operation view.



1.1.7.     What is a Pool Machine?
           A machine in the pool is called a pool machine.
           A pool has two types; a pool that each machine group has and a pool that does not
           belong to any machine group, we call the pool a shared pool.


           There are three statuses of a pool machine that belongs to a machine group.
            A pool machine that belongs to one group
               This is a machine that belongs to one group pool.
            A pool machine that belongs to multiple groups
               If a machine is added to the pool by multiple groups, the pool machine can be
               shared between the multiple groups. (Virtual machines cannot be shared.) If you
               do, you can reduce the number of pool machines altogether.

Part I SigmaSystemCenter Functions Reference
                                                                                                   7
1 Functions of SigmaSystemCenter

            A pool machine that is in operation in other group
               This is a status changed from a pool machine that belongs to multiple groups
               status. A machine is active in one of the groups that the machine belongs to.
               Because the machine is used by the group, you cannot activate the machine for
               other groups. If the machine is deleted from the group and made to stand by, the
               machine can be used for any group.


           A pool machine in a shared pool; we call the machine a shared pool machine, is
           standing by in a condition that can be activated immediately. There are specific
           conditions to use a shared pool machine. For the conditions, see Subsection 1.9.2,
           "Conditions to Use a Shared Pool Machine and Machine Name Configuration."



1.1.8.     The Status of Machines
           SystemProvisioning manages status, including power status, running status, hardware
           status, and managed status, which are displayed on list or details of a machine or host
           on the Web Console. This helps you to grasp the situation of machine failure, On or Off
           of power, or action execution.


           Reference: See Subsection 1.1.4, "Status of a Machine" in SigmaSystemCenter Web
           Console Reference Guide for the actual status displayed on Web Console and
           description.


           SystemProvisioning displays the following status:


            Summary Status
             You can check the outline status of a machine, except power status and OS status.
             The management status, hardware status, and execution status are displayed
             collectively as the summary status, so you can check the action execution status,
             management status of a machine, and hardware failure status if you see this
             status.
            Running Status
               You can check if a machine is allocated to a host and running in a group.
               The running status turns to On when a machine is allocated to a host by
               commands, such as Allocate Machine.
               Also, this status turns to Off when the allocation of a machine to a host is released
               by commands, such as Release Resource.
            Hardware Status
               You can check if there is failure on machines.
               When a failure event occurs, actions of status setting are executed according to a
               policy, and the hardware status turns to Faulted or Degraded.
               If a recovery event occurs, this status displays Ready.
               You can also return this status to Ready by executing Clear Failure Status.


                                                          SigmaSystemCenter 2.1 Reference Guide
8
                                                                               Machine Management



            Power Status
               You can check the power status of a machine.
            OS Status
             You can check the status if an OS installed on a machine is running or stopped.
            Execute Status
             You can check the action execution status.
             If an execution result of an action is failed, Abort is displayed.
             If an action is being executed, In-process is displayed.
             If an action is not executed, - is displayed. In addition, an execution result of an
             action is completed, - is displayed.
            Policy Status
             You can check whether a policy action corresponding to an event occurred on a
             machine is executed or not.
             When a machine is allocated to a host, On is displayed. When On is displayed, a
             policy action can be executed.
             When the allocation of a host is released, Off is displayed. When Off is displayed,
             a policy action cannot be executed.
             If you execute an operation that turns the Power Status to Off, the Policy Status
             turns to Partial. When Partial is displayed, an action to a Machine inaccessible
             error is not executed. This function prevents the unintended recovery process from
             the Machine inaccessible error occurred by an operation from
             SigmaSystemCenter
            Maintenance Status
             You can check the status of the Maintenance Mode.
             Use the Maintenance Mode to prevent an unintended action from being executed
             automatically while you are maintaining a machine. By enabling the Maintenance
             Mode, you can restrain execution of policy actions and exclude a machine from
             target of automatic selection when an action is executed.
             By executing Maintenance On from the Web Console or the "pvmutl maintenance
             On" command, the Maintenance Status turns to On, and the Maintenance Mode is
             enabled.
             And by executing Maintenance Off from the Web Console or the "pvmutl
             maintenance Off" command, the Maintenance Status turns to Off, and the
             Maintenance Mode is disabled.
            Managed Status
               You can check the status whether a machine is managed in SystemProvisioning or
               not.




Part I SigmaSystemCenter Functions Reference
                                                                                                    9
1 Functions of SigmaSystemCenter



1.2. Machine          Operation                                                             by
     SystemProvisioning
           SystemProvisioning provides various operation           modes,    including   machine
           configuration change, a basis of operations.
           This section explains the machine operations by SystemProvisioning.



1.2.1.     Machine Configuration Change
           You can change managed machines into various system configurations and operating
           modes.
           Types of configuration change are as follows:


            Activating a machine
               •   Allocate Resource:
                   Activate a machine in a group by allocating a machine to a host.
               •   Register Master Machine:
                   Activate a machine that has been configured various settings for operation,
                   excluding distribution of software or network settings in a group. The machine
                   is called a master machine.
            Deleting a machine
               •   Release Resource:
                   Move an active machine to a pool to delete the machine from the list of active
                   machines.
            Replace Machine:
               Replace a machine on which a failure occurred with a pool machine to restore
               when the failure.
            Change Machine Usage:
               Move an active machine to other group and use the machine for a task of the
               group.
            Scale Out:
               Activate one of machines in standby in a group pool.
            Scale In:
               Make one of active machines standby in a group pool.




                                                           SigmaSystemCenter 2.1 Reference Guide
10
                                                        Machine Operation by SystemProvisioning




           The followings are configuration changes of a virtual machine:
            Activating a machine
               •   Create and Assign Machine:
                   Create a virtual machine on a virtual machine server.
               •   Allocate Machine:
                   Activate a virtual machine with customizing the virtual machine.
               •   Register Master Machine
                   Activate an existing virtual machine without customizing the virtual machine.
            Deleting a machine
               •   Release Resource:
                   Delete a virtual machine from a group.
               •   Delete Virtual Machine:
                   Delete a virtual machine from a virtual machine server.
            Move Virtual Machine:
               Move a virtual machine from a current virtual machine server to a different virtual
               machine server.
               •   Hot Migrate / Cold Migrate:
                   Move a virtual machine on a shared disk.
               •   Move:
                   Move a virtual machine that is OFF including its disk.
                   This takes longer time than Hot Migrate and Cold Migrate.
               •   Failover:
                   If a virtual machine server is down due to a failure, move a virtual machine on
                   a shared disk.




Part I SigmaSystemCenter Functions Reference
                                                                                                   11
1 Functions of SigmaSystemCenter



            Reconfigure
               Reconfigures running machines. Virtual machine names, UUID information and
               disk data other than system disks will be remained.
               •   Revert
                   Reverts a system disk back to the status of when virtual machines were
                   created.
               •   Reconstruct
                   Reconstructs virtual machines using a specified template.




                                                       SigmaSystemCenter 2.1 Reference Guide
12
                                                       Machine Operation by SystemProvisioning




1.2.2.     Transition of Machine Status
           This subsection explains the transition of the managed status of a managed machine.




           1.   Importing machines managed in a subsystem
                To manage machine in SystemProvisioning, import machines managed by
                compatible products, such as DPM and vCenter Server.


           2.   Registering a machine as a management target of SystemProvisioning
                To take the machine in a management target of SystemProvisioning, register the
                machine as a managed machine from the Resource view on the Web Console.
                The registered machine is managed as a managed machine.


           3.   Registering a machine as a pool machine
                Register a managed machine to a group pool as a standby machine for the group.
                At this timing, SystemProvisioning executes shut down to the machine. A virtual
                machine server to which the settings for a virtual machine or storage are not
                enabled does not shut down.
                The registered machine is managed as a pool machine.




Part I SigmaSystemCenter Functions Reference
                                                                                                 13
1 Functions of SigmaSystemCenter



           4.   Activating a pool machine in a group
                Activate a machine by allocating the machine resource to a host. A machine can
                be activated with the configuration changes, such as Allocate Resource, Replace
                Machine, and Change Machine Usage. At this timing, SystemProvisioning starts
                up to the machine. The activated machine is managed as a host.


           5.   Registering as a master machine
                Activate a machine of a managed machine that does not belong to any group,
                which is in the status of Procedure 2, "Registering a machine as a management
                target of SystemProvisioning" and 3, "Registering a machine as a pool machine."
                At this timing, SystemProvisioning starts up to the machine. The activated machine
                becomes the same status of after Procedure 4, "Activating a pool machine in a
                group."


           6.   Making an active machine standby in a pool
                Make an active machine in a group standby in a pool. A machine can be made to
                stand by with the configuration changes, such as Release Resource, Replace
                Machine, and Change Machine Usage. The machine after this operation is
                managed as a pool machine. At this timing, SystemProvisioning executes shut
                down to the machine. A virtual machine server to which the settings for a virtual
                machine or storage are not enabled does not shut down.
                The machine becomes the same status of after Procedure 3, "Registering a
                machine as a pool machine."


           7.   Deleting an active machine from the group
                Delete an active machine in a group from the group. A machine can be deleted
                with the configuration changes, such as Replace Machine and deleting the
                machine from the group. This operation deletes host. If the machine is not
                registered to the group pool, the machine will be in the status of
                SystemProvisioning management target but not being registered to any group. At
                this timing, SystemProvisioning executes shut down to the machine. A virtual
                machine server to which the settings for a virtual machine or storage are not
                enabled does not shut down. The deleted machine becomes the same status of
                after Procedure 2, "Registering a machine as a management target of
                SystemProvisioning."


           8.   Deleting a pool machine from the group
                Change the status of a pool machine to not belonging to any group. If the machine
                is not registered to other group pool, the machine will be in the status of
                SystemProvisioning management target but not being registered to any group.
                The deleted machine becomes the same status of after Procedure 2, "Registering
                a machine as a management target of SystemProvisioning"




                                                         SigmaSystemCenter 2.1 Reference Guide
14
                                                       Machine Operation by SystemProvisioning



           9.   Deleting a machine from the management target of SystemProvisioning
                Delete a machine from the management target of SystemProvisioning. This
                operation deletes the machine from the configuration management target.
                The deleted machine becomes the same status of after Procedure 1, "Importing
                machines managed in a subsystem."


           10. Using a shared pool machine
                If specific conditions are met when changing a configuration of a machine, with
                activating a machine or Replace Machine, you can activate a managed machine
                that does not belong to any group in a group.
                The activated machine is managed as a host.




Part I SigmaSystemCenter Functions Reference
                                                                                              15
1 Functions of SigmaSystemCenter




1.2.3.     Operations Implemented by Group Management
           The following operations are enabled by group management.


            Replace Machine (physical machine)
               You can prepare pool machines for each group. If an error occurs on an active
               machine within the group, you can replace the machine and restore the failed
               machine by installing the backed up disk image to the machine in advance.




            Sharing a pool machine
               You can register a pool machine to multiple groups. If a pool machine is shared
               between multiple groups, without arranging an exclusive pool machine for each
               group, the number of pool machine units for the entire system is reduced and high
               level of availability is maintained with minimal investment.




                                                        SigmaSystemCenter 2.1 Reference Guide
16
                                                         Machine Operation by SystemProvisioning



            Change Machine Usage
               You can use an active machine also as a pool machine. If heavy processing loads
               are expected for a task in a certain group, the machines from other group can be
               diverted to ensure a balance in load.
               This operating mode is a type of shared pool machine.




            Move Virtual Machine
               You can move active virtual machines in a group to a different virtual machine
               server. If a virtual machine server is expecting heavy loads with a certain task, the
               virtual machines can be moved to the virtual machine server without turning the
               virtual machines off, so that the load balance can be maintained.




Part I SigmaSystemCenter Functions Reference
                                                                                                   17
1 Functions of SigmaSystemCenter



               In addition, in a situation when virtual machines cannot access a virtual machine
               server because a failure happens, and the virtual machine server is turned off, if
               the virtual machines are created on a shared disk, such as SAN, NFS, and iSCSI,
               you can move the virtual machines to other virtual machine server.




            Create and Assign Machine (virtual machine)
               You can create a virtual machine and activate the machine in a group. If heavy
               processing loads are expected with a task in a certain group, active machines can
               be created to ensure a balance in load.




                                                        SigmaSystemCenter 2.1 Reference Guide
18
                                                         Functions Regarding Managing Machines



1.3. Functions                            Regarding                         Managing
     Machines
           SigmaSystemCenter has various functions regarding machine management.
           In this section, machine identification, the monitoring function, and various functions
           about machine management, including recovery actions in a failure are explained.



1.3.1.     Machine Identification
           SystemProvisioning uses general information of machines, such as a host name, IP
           address, UUID, MAC address for identifying machines. Using the information enables
           you to identify which machine managed in other operation management software
           corresponds to a machine managed.
           SystemProvisioning uses various kinds of software for recognizing and controlling the
           configuration of the IT environment; the software is called subsystems.
           SystemProvisioning collects a UUID or MAC address of a machine by the subsystems
           and manages them collectively in SystemProvisioning. If a machine has two or more
           NICs, the MAC address of the machine is identified with its NIC for management. The
           MAC address of the NIC for management is used as a special MAC address; a primary
           MAC address. Also, a NIC for a primary MAC address is expressed as a primary NIC.
           A primary NIC is configured its NIC number as a first NIC.
           Therefore, to manage one machine from multiple subsystems, the machine's NIC for
           management needs to be the same in the subsystems.


           A machine activated by being added to a group is managed with recognizable
           information in the subsystem (an IP address with NEC ESMPRO Manager) correlated
           to the machine’s host name.



1.3.2.     Machine State and Failure Monitoring Function
           SystemProvisioning can monitor the status, a failure, and recovery of managed
           machines by receiving an alert from components, such as NEC ESMPRO Manager,
           vCenter Server, and System Center Operations Manager 2007.
           A failure event detected in a managed machine or a group is alerted to
           SystemProvisioning.




Part I SigmaSystemCenter Functions Reference
                                                                                                 19
1 Functions of SigmaSystemCenter



           Also, if you need a status or detailed information of a machine, you can check the
           information using NEC ESMPRO Manager.
           The following figure is a model of a failure alerted to SystemProvisioning through NEC
           ESMPRO Manager and vCenter Server.




1.3.3.     Performance             Monitoring          by      System          Monitor          -
           Performance Monitoring Services
           SystemProvisioning is alerted by System Monitor - Performance Monitoring Services
           when load fluctuation is detected in the CPU, memory, or disk on a managed machine.


           Reference: For details regarding System Monitor - Performance Monitoring Services,
           see System Monitor - Performance Monitoring Services User's Guide.


           System Monitor - Performance Monitoring Services collects and monitors the
           performance information of a machine. If System Monitor - Performance Monitoring
           Services detects performance abnormality, such as exceeding threshold successively,
           the function alerts SystemProvisioning as a performance failure event.




                                                        SigmaSystemCenter 2.1 Reference Guide
20
                                                           Functions Regarding Managing Machines




1.3.4.     What is a Policy?
           SigmaSystemCenter manages machines based on policies. The management defines
           multiple rules of policies as a policy. The defined policy can be enabled by configuring
           the policy to a group.
           A rule of policy is a registration of "what process the system runs when a specific event
           occurs." SigmaSystemCenter configures policies by combining a recovery process
           (action) with event alerts. For example, configure the settings, such as "Add a machine
           to a group if a high CPU load error is received from NEC ESMPRO Manager."


           SigmaSystemCenter provides multiple policy templates (a Standard Policy) with
           standard Event Handler Settings configured in advance. You can use the policy
           templates without modification or customize the templates and use them.


           Reference: For the details of policy actions, see Chapter 5, "Error Events and Policy
           Actions." In addition, for how to configure the Policy Property Settings, see Section 2.6,
           "Details of Policies" and 2.7, "Policy Property Settings" in SigmaSystemCenter Web
           Console Reference Guide.


           The following is an example of actions from failure occurrence to execution of policy
           setting process.




           1.   A high CPU load error is generated.
           2.   NEC ESMPRO Agent sends alert of a high CPU load error to NEC ESMPRO
                Manager.


Part I SigmaSystemCenter Functions Reference
                                                                                                    21
1 Functions of SigmaSystemCenter



           3.   NEC ESMPRO Manager notifies to SystemProvisioning.
           4.   SystemProvisioning executes a coping process with the high CPU load error
                according to a policy set in a group.


           In addition, SigmaSystemCenter provides functions of notifying a sent alert by e-mail
           and registering an alert to the Event Log.


           The Policy Property Settings provide a function that suppresses error events. The
           configured actions are executed only when a recovery event has not been generated
           when a specific error event is detected after waiting a certain amount of time for an
           error recovery event.
           For example, the machine access error that is generated during the normal system
           reboot process can be suppressed.


           Reference: For the events that can be suppressed, see Subsection 5.4.2,
           "Suppression of Action Execution (Suppression of Error Event)."
           For how to configure the setting for suppression, see Subsection 3.9.5, "Configuring
           Policy Property Settings" in SigmaSystemCenter Configuration Guide.




                                                         SigmaSystemCenter 2.1 Reference Guide
22
                                                                  Distribution Software Management



1.4. Distribution Software Management
           Distribution software refers to the settings used when changing the machine
           configuration, such as activating or replacing machines. There are the following types
           of the distribution software;
            Scenario
               This is a configuration file regarding the installation of OS and applications. A
               scenario is created with DPM.
            Template
               This is a configuration file used when creating a virtual machine. Templates that
               you can use from SystemProvisioning are as follows:
               •    Full Clone template
               •    HW Profile Clone template
               •    Differential Clone template
               •    Disk Clone template
            Local Script
               This is an executable file used when certain process, which depends on a system
               configuration or environment, is run on the SystemProvisioning management
               server.


           Refer to the following subsections for detailed explanation of the distribution software.



1.4.1.     What Is a Scenario?
           A scenario is a file that summarizes the execution processes that are related to the
           installation of the OSs and applications. Scenarios are created in DPM. You can use
           scenarios created in DPM to distribute applications, middleware, patches, etc., to
           managed machines in SystemProvisioning.
           Not only can scenarios be used when setting up a first managed machine, but
           scenarios can be used for activating a machine or setting up an alternative machine
           when an error occurred.


           You can create a scenario, specifying the execution processes to machines managed
           in DPM. To run the specified processes, register the scenario to a machine and run the
           scenario. You can use scenarios to distribute disk images, images on a floppy disk,
           OSs, service packs, HotFixes, Linux patch files, and applications, and also back up and
           restore the machines.
           You can create a scenario with orderly execution processes.
           For example, a scenario that runs the processes in the order of updating BIOS,
           installing an OS, applying a service pack, and backing up the machine can be created.
           Once you create a scenario, you can use the scenario as many times as you want and
           register the scenario to multiple machines.


Part I SigmaSystemCenter Functions Reference
                                                                                                       23
1 Functions of SigmaSystemCenter



           In addition, you can take advantage of the various option settings that make operations
           smoother. For example, there are a power management setting for before and after
           running a scenario and multicast and unicast settings for distributing applications in
           option settings.


           Reference: Refer to Chapters 2, 3, 5, and 6 in DeploymentManager Basic User's
           Guide regarding details on configuration methods of scenarios.


           The DPM scenarios include the following kinds:
            Backup scenario
            Restore scenario
            OS clear installation scenario
            Scenario for installing applications
            Scenario for distributing patches


           For more details of the use of a scenario, see Section 1.5 "Use of a Scenario."



1.4.2.     What Is Local Script?
           A local script is an executable file that can execute a specific process which depends
           on a system configuration or environment when activating, changing usage, or
           replacing machines. Local scripts are stored on a SystemProvisioning management
           server.
           Local scripts can be registered to a group. Local scripts registered when activating a
           machine can be executed on a SystemProvisioning management server.
           For more details of a local script, see Section 1.6, "Use of Local Scripts."




                                                           SigmaSystemCenter 2.1 Reference Guide
24
                                                                                  Use of a Scenario



1.5. Use of a Scenario
           In this section, operational flow from creating a scenario to importing the scenario to
           SystemProvisioning and details of distribution method of a scenario are explained.



1.5.1.     Flow from Creating a Scenario to Registering Distribution
           Software
           This subsection explains the operational flow from creating a scenario using DPM to
           registering distribution software to SystemProvisioning.
           The flow differs according to OS that your managed machine is running.
           The following is a flow of machine running Windows.


           Note: Before you back up or restore in DPM, make sure to check the Disk number
           using the Disk Viewer. For details of the Disk Viewer, see Chapter 4, "Disk
           Configuration Check" in DeploymentManager Advanced User’s Guide.


           Reference: Refer to Section 1.2, "OS Setup (Linux) by Disk Duplication" in
           DeploymentManager Basic User’s Guide regarding Linux servers.


           1.   Creating a master machine
                To create an image to be used with a scenario, set up a software environment,
                including OS and applications that will be used by a machine on a single machine
                of copy image; we call the machine a master machine.


           2.   Creating a deployment disk image (DPM)
                Create a scenario to backup a machine with DPM. When the scenario is executed,
                a deployment disk image is created on DPM.
                The deployment disk image includes a disk image of the master machine without
                unique information of the master machine.


                After creating the deployment disk image, DPM restarts the master machine and
                restores the machine to the original state (the machine-specific information, host
                name and IP address, is configured).


           3.   Creating a restore scenario (DPM)
                Create a scenario to restore the created deployment disk image.




Part I SigmaSystemCenter Functions Reference
                                                                                                 25
1 Functions of SigmaSystemCenter



           4.   Registering as distribution software (SystemProvisioning)
                Collect the scenario information registered in DPM that is registered as a
                subsystem and register the information in SystemProvisioning as distribution
                software.
                To collect the information, you can take the either way: executing DPM Collect on
                the Base Information of software in the Resource view, or executing Collect with
                DPM as a subsystem specified on the details of the subsystem in the Management
                view.


           These are the operations to create a scenario in DPM and register the scenario as
           distribution software in SystemProvisioning.



1.5.2.     Distribution Methods and Types of Software
           To install the distribution software registered to SystemProvisioning, there are two
           methods; to register the distribution software to a machine unit, host setting unit, or
           group unit and distributes when the configuration of the machine is changed; we call
           this distribution method a Distribution After Registration, and to distribute the
           distribution software registered to SystemProvisioning when you want to distribute; we
           call this method a Specified Distribution.


           Reference: For details of these methods, see Subsection 1.5.5, "Details of Distribution
           After Registration of Distribution Software," and Subsection 1.5.6, "Details of Specified
           Distribution Software."


           In addition, there are two types of software distributed in distribution after registration
           as follows:
            Operating Distribution Software
                This is distribution software that is distributed when the machine is activated if the
                software is registered to a pool machine, Host Setting, model, or group.
            Standby Distribution Software
                This is distribution software that is distributed when the machine is deleted from its
                group if the software is registered to an active machine, Host Setting, model, or
                group.
            Software to be distributed when creating a replica
                This is a timing of software. Sysprep will be executed on the software that are
                configured at this timing when creating templates and images.
                When making the machine running in the group or making the machine stand by
                from the group, the software that are configured at this timing are ignored.


           "Flow from Registering Operating Distribution Software to Activating the Machine"
           (Subsection 1.5.3) and "Flow from Registering Standby Distribution Software to
           Deleting a Machine" (Subsection 1.5.4) will be explained in the following pages.

                                                           SigmaSystemCenter 2.1 Reference Guide
26
                                                                                 Use of a Scenario




1.5.3.     Flow from Registering Operating Distribution Software to
           Activating the Machine
           This subsection explains the operational flow of registering distribution software as
           operating distribution software to a machine, Host Setting, model, or group and
           activating the machine in a group.


           1.   Registering operating distribution software
                Register a created deployment disk image or software as operating distribution
                software in SystemProvisioning. You can register the distribution software in:
                •   Machine
                •   Host Setting
                •   Model
                •   Group


           2.   Adding the machine to a group
                If the machine is added to a group and activated, SystemProvisioning installs the
                registered operating distribution software to the machine. You can select any
                machine specific unique information, such as a host name and IP address, from
                the Host Setting registered to the group. Once the installation has completed, a
                machine with the information reflected to the created deployment disk image is set
                up.




Part I SigmaSystemCenter Functions Reference
                                                                                                 27
1 Functions of SigmaSystemCenter



               The state of the distribution software installation to the machine added to the group
               is as follows;




                                                          SigmaSystemCenter 2.1 Reference Guide
28
                                                                                   Use of a Scenario




1.5.4.     Flow from Registering Standby Distribution Software to
           Deleting a Machine
           This subsection explains the operational flow of registering distribution software as
           operating distribution software to a machine, Host Setting, model, or group and deleting
           the machine from the group.


           1.   Registering standby distribution software
                Register software to distribute as standby distribution software. You can register
                the distribution software in:
                •   Machine
                •   Host Setting
                •   Model
                •   Group


           2.   Deleting a machine from a group
                SystemProvisioning installs the registered standby distribution software to a target
                machine when you delete the machine and the machine is shifted to the standby
                status.




Part I SigmaSystemCenter Functions Reference
                                                                                                   29
1 Functions of SigmaSystemCenter




1.5.5.     Details of Distribution After Registration of Distribution
           Software
           With the distribution after registration, that is the method of if you register the
           distribution software to a machine unit, Host Setting unit, model unit, or group unit, the
           software is distributed when the configuration of the machine is changed, there are the
           following features:
            You can register the distribution software to a machine unit, Host Setting unit,
             model unit, and group unit and distribute the software to the unit.
            You can register the operating distribution software and standby distribution
             software to each target of registration.
            You can register multiple distribution software to each target of registration.
            You can change configuration of machines that will triggers off distributing
             distribution scenario.


           The following table shows the distribution target and the timing of distribution.


           Registration Target           Distribution Timing           Descriptions

           Physical or Virtual Machine   Operating / before group      Software to be distributed before
                                         distribution                  the distribution software
                                                                       registered to the group is
                                                                       distributed, when the machine is
                                                                       activated in the group.
           Physical or Virtual Machine   Operating / after group       Software to be distributed after
                                         distribution                  the distribution software
                                                                       registered to the group is
                                                                       distributed, when the machine is
                                                                       activated in the group.
           Virtual Machine               When replica creation         Sysprep will be executed on the
                                                                       software that are configured at
                                                                       this timing when creating
                                                                       templates and images.
                                                                       When making the machine
                                                                       running in the group or making
                                                                       the machine stand by from the
                                                                       group, the software that are
                                                                       configured at this timing are
                                                                       ignored.
           Physical or Virtual Machine   Standby / before group        Software to be distributed before
                                         distribution                  the distribution software
                                                                       registered to the group is
                                                                       distributed, when the machine is
                                                                       set to the standby state in the
                                                                       group.




                                                            SigmaSystemCenter 2.1 Reference Guide
30
                                                                                   Use of a Scenario


           Registration Target           Distribution Timing        Descriptions

           Physical or Virtual Machine   Standby / after group      Software to be distributed after
                                         distribution               the distribution software
                                                                    registered to the group is
                                                                    distributed, when the machine is
                                                                    set to the standby state from the
                                                                    group.
           Physical or Virtual Machine   Standby / after shutdown   Software to be distributed after
                                                                    the machine is shut down when
                                                                    the machine is set to the standby
                                                                    state from the group.
                                                                    (SystemProvisioning does not
                                                                    execute shutdown to a virtual
                                                                    machine server whose settings
                                                                    for a virtual machine and storage
                                                                    are not enabled so do not register
                                                                    the software at this timing.)
           Host Setting                  Operating / before group   Software to be distributed before
                                         distribution               the distribution software
                                                                    registered to the group is
                                                                    distributed, when the machine is
                                                                    activated in the group.
           Host Setting                  Operating / distribution   Software to be distributed when
                                                                    the machine is activated in the
                                                                    group.
           Host Setting                  Operating / after group    Software to be distributed after
                                         distribution               the distribution software
                                                                    registered to the group, when the
                                                                    machine is set to the active state
                                                                    in the group.
           Host Setting                  Standby / before group     Software to be distributed before
                                         distribution               the distribution software
                                                                    registered to the group, when the
                                                                    machine is set to the standby
                                                                    state from the group.
           Host Setting                  Standby / distribution     Software to be distributed when
                                                                    the machine is set to the standby
                                                                    state from the group.
           Host Setting                  Standby / after group      Software to be distributed after
                                         distribution               the distribution software
                                                                    registered to the group is
                                                                    distributed when the machine is
                                                                    set to the standby state from the
                                                                    group.
                                                                    (SystemProvisioning does not
                                                                    execute shutdown to a virtual
                                                                    machine server whose settings
                                                                    for a virtual machine and storage
                                                                    are not enabled so do not register
                                                                    the software at this timing.)
           Host Setting                  Standby / after shutdown   Software to be distributed after
                                                                    the machine is shut down when
                                                                    the machine is set to the standby
                                                                    state from the group.
           Model                         Distribution when the      Software to be distributed when
                                         machine is activated       the machine is activated in the
                                                                    group.

Part I SigmaSystemCenter Functions Reference
                                                                                                    31
1 Functions of SigmaSystemCenter


           Registration Target           Distribution Timing             Descriptions

           Model                         Distribution when the           Software to be distributed when
                                         machine is set to standby       the machine is set to the standby
                                                                         state from the group.
           Model                         Standby / after shutdown        Software to be distributed after
                                                                         the machine is shut down when
                                                                         the machine is set to the standby
                                                                         state from the group.
           Group                         Distribution when the           Software to be distributed when
                                         machine is activated            the machine is activated in the
                                                                         group.
           Group                         Distribution when the           Software to be distributed when
                                         machine is set to standby       the machine is set to the standby
                                                                         state from the group.
           Group                         Standby / after shutdown        Software to be distributed after
                                                                         the machine is shut down when
                                                                         the machine is set to the standby
                                                                         state from the group.
                                                                         (SystemProvisioning does not
                                                                         execute shutdown to a virtual
                                                                         machine server whose settings
                                                                         for a virtual machine and storage
                                                                         are not enabled so do not register
                                                                         the software at this timing.)
           Registry                      Standby                         If the SetDHCP scenario is
           (HKEY_LOCAL_MACHINE                                           registered in DPM, the scenario is
                                                                         distributed when the machine is
           \Software\NEC\PVM\                                            set to the standby state from the
           ActionSequence\Scenario\                                      group.
           SetDHCP)


           The software registered by distribution type is distributed in a predefined order.
           If there is no software registered by distribution type of the corresponding order, the
           distribution type is excluded and software registered by distribution types with the
           following distribution order is distributed.
           The distribution software is different between operating distribution software and
           standby distribution software.


           The following table shows the predefined distribution order of operating distribution
           software.


           Distribution   Registration Target               Distribution Type
           Order

           1              Physical or Virtual Machine       Distribution software registered to "Operating /
                                                            before group distribution"
           2              Host Setting                      Distribution software registered to "Operating /
                                                            before group distribution"
           3              Model                             Distribution software registered to "Distributing
                                                            when the machine is activated"
           4              Group                             Distribution software registered to "Distributing
                                                            when the machine is activated"

                                                            SigmaSystemCenter 2.1 Reference Guide
32
                                                                                    Use of a Scenario


           Distribution   Registration Target           Distribution Type
           Order

           5              Host Setting                  Distribution software registered to "Operating /
                                                        distribution"
           6              Host Setting                  Distribution software registered to "Operating /
                                                        after group distribution"
           7              Physical or Virtual Machine   Distribution software registered to "Operating /
                                                        after group distribution"


           The following table shows the predefined distribution order of standby distribution
           software.


           Distribution   Registration Target            Distribution Type
           Order

           1              Physical or Virtual Machine    Distribution software registered for "Standby /
                                                         before group distribution"
           2              Host Setting                   Distribution software registered for "Standby /
                                                         before group distribution"
           3              Model                          Distribution software registered for
                                                         "Distributing while the machine is on standby"
           4              Group                          Distribution software registered for “Standby /
                                                         distribution”
           5              Host Setting                   Distribution software registered to "Standby /
                                                         distribution"
           6              Host Setting                   Distribution software registered for "Standby /
                                                         after group distribution"
           7              Registry                       SetDHCP scenario registered to DPM
           8              Physical or Virtual Machine    Distribution software registered for "Standby /
                                                         after group distribution"
           9              Physical or Virtual Machine    Distribution software registered for "Standby /
                                                         after shutdown"
           10             Host Setting                   Distribution software registered for “Standby /
                                                         after shutdown”
           11             Model                          Distribution software registered for "Standby /
                                                         after shutdown"
           12             Group                          Distribution software registered for "Standby /
                                                         after shutdown"




Part I SigmaSystemCenter Functions Reference
                                                                                                      33
1 Functions of SigmaSystemCenter



           The registered distribution software is installed when you execute the following
           machine configuration change from the Web Console or command.
            Allocating Machine / Scale Out
               The operating distribution software registered to the machine, Host Setting, model,
               or group is distributed to a machine to be added.
            Release Resource / Scale In
               The standby distribution software registered to the machine, Host Setting, model,
               or group is distributed to a machine to be deleted.
            Changing Machine Usage
               The standby distribution software registered to the machine, Host Setting, model,
               or group of an original machine is distributed to the original machine.
               The operating distribution software registered to the machine, Host Setting, model,
               or group of a new machine is distributed to the new machine.
            Replacing a machine
               The standby distribution software registered to the machine, Host Setting, model,
               or group is distributed to an original machine.
               The operating distribution software registered to the machine, Host Setting, model,
               or group is distributed to a new machine.
            Create and Assign Machine
               The operating distribution software registered to the machine, Host Setting, model,
               or group is distributed to a created virtual machine to be activated.
            Redistributing software to a group or machine
               The operating distribution software registered to the machine, Host Setting, model,
               or group is distributed to machines in the target group or to the target machine.


               Reference: For the detailed information of redistribution of distribution software,
               see Subsection 1.5.8, "Redistribution of Software (Distribute All)."



1.5.6.     Details of Specified Distribution Software
           Single or multiple distribution software that a user specified is distributed to a machine
           at the timing that the user specified. To execute the specified distribution, distribution
           software needs to be registered to SystemProvisioning.




                                                          SigmaSystemCenter 2.1 Reference Guide
34
                                                                                    Use of a Scenario




1.5.7.     Difference Distribution of Distribution Software
           If you execute operations, such as distributing updates or adding applications to an
           active machine in a group, using multiple distribution software, it may cause differences
           in the installation state of distribution software between machines in a group.
           SystemProvisioning provides the difference distribution function to simply resolve the
           differences of distribution software between machines.
           The difference distribution function installs only distribution software that has not
           installed yet if there is such distribution software in a specific machine or all the
           machines in a group. To distribute the difference distribution software to all machines in
           a group, you can select between the following methods: Distribute to the servers in the
           group simultaneously (to distribute the software to all machines at the same time) or
           Distribute to the servers in the group sequentially (to distribute the software in order
           one unit at a time).




           Software that meet the following conditions are the target of difference distribution.
            The software scheduled for difference distribution is not included in the latest
             software distribution history. (AP1, Update and AP3 of Active machine #2 in the
             above figure fall under this.)
             Although the software scheduled for difference distribution is included in the latest
             software distribution history, the software scheduled for difference distribution is


Part I SigmaSystemCenter Functions Reference
                                                                                                    35
1 Functions of SigmaSystemCenter

               newer than the images included in the latest software distribution history. (OS (The
               date of image is old) of the Active machine #3 in the above figure falls under this.)
            Although the software scheduled for difference distribution is included in the latest
             software distribution history, an OS difference distribution must be executed before
             the software distribution.
            The type of the software scheduled for difference distribution is not script.


           If even one of the conditions above is missing, difference distribution is not executed.



1.5.8.     Redistribution of Software (Distribute All)
           In software maintenance, software that is already installed can be reinstalled.
           SystemProvisioning provides the redistribution function to simplify the reinstallation of
           software.
           The reinstallation function reinstalls all distribution software registered to a specific
           machine or all machines in a group. You can choose from two methods to distribute
           software to all the machines in a group: Distribute to the servers in the group
           simultaneously (to distribute the software to all machines at the same time) or
           Distribute to the servers in the group sequentially (to distribute the software in order
           one unit at a time).




                                                          SigmaSystemCenter 2.1 Reference Guide
36
                                                                                  Use of a Scenario




1.5.9.     Use of Master Machine
           A machine used to create a disk image, that is a master machine, can be used for
           operation. A machine used for a specific operation out of the SystemProvisioning
           managed system can also be used as a machine in a group in SystemProvisioning.
           SystemProvisioning provides the Master Machine Registration function to add a
           machine that has a software environment already configured to be used in the
           operation to the SystemProvisioning managed system.
           The master machine registration function does not install distribution software or apply
           Host Setting, such as a host name and IP address, when adding the target machine to
           a group. In other words, it is considered as the registered distribution software has
           already been installed, and the Host Setting to be used has already been applied to the
           active machine in the group.




Part I SigmaSystemCenter Functions Reference
                                                                                                  37
1 Functions of SigmaSystemCenter




1.5.10. Registration of Distribution Software to Group
           A group can be configured with levels of groups and models, and you can register
           distribution software to both groups and models.
           By registering the distribution software to both groups and models, you can set up an
           environment that is aware of differences in drivers according to machine types and
           differences of application specifications within groups with the same application. In
           addition, you can use backup type disk images.
           When the distribution software is registered to both a group and a model, the
           installation of the distribution software to the machine is conducted in the following
           order:
           1.   The distribution software registered to a model
           2.   The distribution software registered to a group




                                                          SigmaSystemCenter 2.1 Reference Guide
38
                                                                                Use of a Scenario



           An operating environment using the backup typed disk images (complete backup
           images of individual machines) can be configured by using models. In this case, you do
           not register the distribution software to the group. Register only one machine to each
           model, and register the distribution software to install a backup type disk image.




Part I SigmaSystemCenter Functions Reference
                                                                                                39
1 Functions of SigmaSystemCenter



1.6. Use of Local Scripts
           This section explains the use of local scripts.



1.6.1.     Details of Local Scripts
           The followings are the details of local scripts.
            Target file
               A file you can use as a local script is an executable file in .bat format.
            Storage folder
               The folder of the local script is the script folder directly under the installation folder
               of SystemProvisioning. A default storage folder:
                    C:\Program Files\NEC\PVM\Script
               The .bat file stored directly under this folder can be used as a local script.
               To register a local script, store the local script in the Script storage folder, click the
               software in the Resource view, and then, click Script Collect on the Operation
               menu, or click the Management view, and click Collect on the Configuration menu,
               so the information of SystemProvisioning is updated.
            Display format on the Web Console
               The local script is displayed in the following format on the Web Console of
               SystemProvisioning.
                    A script file name without an extension/<localhost>
               Accordingly, when the local script is created with the file name; localscript.bat, the
               file is displayed as distribution software on the Web Console as follows:
                    localscript/<localhost>
            Execution and interruption of local script
               Similar to DPM scenarios, by registering local script to a group, model, Host
               Setting, you can execute the local script when activating a machine to the group,
               or changing the usage of a machine.
               You can suspend the executed local script by cancelling the Job on the Web
               Console.
               In addition, if the local script does not complete in two hours, terminate the local
               script.
            Runtime current folder
               The current folder while running the local script is the local script storage folder
               mentioned above.




                                                              SigmaSystemCenter 2.1 Reference Guide
40
                                                                                 Use of Local Scripts



            Runtime command line arguments and environment variables
               Command line arguments cannot be specified while running the local script.
               The following environment variables can be used within the local script.


               Environment Variable Name                      Description

               PVM_HOST_NAME                                  A computer name specified to a
                                                              managed machine
               PVM_HOST_UUID                                  UUID of a managed machine
               PVM_MACHINE_TAG_COUNT                          The number of tags (keywords) specified
                                                              to a machine
               PVM_MACHINE_TAG_n                              The nth tag (keyword) specified to a
                                                              machine
               PVM_SERVER_DEFINITION_TAG_COUNT                The number of tags (keywords) specified
                                                              to a host
               PVM_SERVER_DEFINITION_TAG_n                    The nth tag (keyword) specified to a host
               PVM_MODEL_PATH                                 A name of a model where a machine is
                                                              running
               PVM_GROUP_PATH                                 A name of a group where a machine is
                                                              running
               PVM_CATEGORY_PATH                              A name of a category where a machine is
                                                              running
               PVM_DEFAULT_GROUP_PATH                         A full path of a model where a machine is
                                                              running

               Related to Networks

               PVM_NIC_COUNT                                  The number of NICs on a managed
                                                              machine
               PVM_MAC_ADDRESS_n                              MAC address of the nth (Primary) NIC.
                                                              Colon (:) delimited character string
                                                              format (e.g. AA:BB:CC:DD:EE:FF)
                                                                                    th
               PVM_MAC_ADDRESS_H_n                            MAC address of the n (Primary) NIC.
                                                              Hyphen (-) delimited character string
                                                              format (e.g. AA-BB-CC-DD-EE-FF)
               PVM_IP_COUNT_n                                 The number of IP addresses specified for
                                                                   th
                                                              the n NIC.
               PVM_IP_ADDRESS_n_m                             The mth IP address specified to the nth
                                                              NIC
               PVM_NETMASK_n_m                                The mth netmask specified for the nth
                                                              NIC. This is configured along with above
                                                              PVM_IP_ADDRESS_n_m.
               PVM_GATEWAY_n_m                                The mth default gateway specified for the
                                                              nth NIC

               Related to Storage

               PVM_STORAGE_COUNT                              The number of disk arrays
               PVM_STORAGE_ID_n                               The nth number of disk array
               PVM_HBA_WWN_COUNT_n                            The number of HBAs that is connected to
                                                              the nth disk array
Part I SigmaSystemCenter Functions Reference
                                                                                                        41
1 Functions of SigmaSystemCenter


               Environment Variable Name                      Description

               PVM_HBA_WWN_n_m                                An address of the mth HBA of the nth disk
                                                              array
               PVM_STORAGE_DEV_COUNT_n_m                      The number of LDs that is connected to
                                                                   th            th
                                                              the m HBA of the n disk array
               PVM_STORAGE_DEV_n_m_l                          Information of the lth LD that is connected
                                                              to the mth HBA of the nth disk array

               Numbers are sequentially assigned from 1 on n, m, and l.


            PVM_MACHINE_TAG_n
               Tag information that was registered to Machine Property Setting on the Resource
               view are stored in the following environmental path: PVM_MACHINE_TAG_n.
               When registering multiple tags, input them in space-delimited format.
               Tags are stored in ascending order. Information sorted in ascending order also can
               be checked from the Web Console.


               E.g.)
               If you register the tag below,
                   BBB AAA CCC
               Environment variables will be
                   PVM_MACHINE_TAG_1 = AAA
                   PVM_MACHINE_TAG_2 = BBB
                   PVM_MACHINE_TAG_3 = CCC


            The format of the address stored in PVM_HBA_WWN_n_m
               The format is different depending on types of the storage.


               •   CLARiiON
                   The format is changed from hyphen-delimited every 4 characters to
                   colon-delimited every 2 characters.
                   WWPN is stored prior to WWNN and m is numbered in this order.


                   E.g.)
                   WWPN: AAAA-BBBB-CCCC-DDDD
                   WWNN: EEEE-FFFF-GGGG-HHHH
                   PVM_HBA_WWN_1_1 = AA:AA:BB:BB:CC:CC:DD:DD
                   PVM_HBA_WWN_1_2 = EE:EE:FF:FF:GG:GG:HH:HH




                                                         SigmaSystemCenter 2.1 Reference Guide
42
                                                                                      Use of Local Scripts



               •   NEC Storage and Symmetrix
                   The delimiter can be changed by configuring the following registry if needed.


                   Registry Key:
                   HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\DPMProvider


                   Value Name          Description                                           Default Value

                   DelimiterWwn        If “0” is set, the delimiter is deleted.              0
                                       If “1” is set, the delimiter is not changed.


                   E.g.)
                   Address: AAAA-BBBB-CCCC-DDDD
                   If the registry value is “0”
                   PVM_HBA_WWN_1_1 = AAAABBBBCCCCDDDD
                   If the registry value is “1”
                   PVM_HBA_WWN_1_1 = AAAA-BBBB-CCCC-DDDD


            Judging method and setting of execution result
               If execution result of a local script is abnormal end, the following message is
               displayed on the Operation Log.


                   Failed to execute the local script (script name) for the server (servername).
                   (error code)


               Depending on process in a local script, there is a case that even though process
               failed, a local script seems to be completed as a result of execution.
               To make the system show the actual execution result, set an end code of a local
               script in the local script.
               To set the end code, describe the following at the end of the local script.


                   exit /b n


               If you put zero in n, process completes even though the process actually fails, and
               if you put other than zero, the process ends with abnormal end if the process fails.
               You can set the value of abnormal end freely.
               The value of n is output to the Operations Log as an error code.




Part I SigmaSystemCenter Functions Reference
                                                                                                       43
1 Functions of SigmaSystemCenter



1.7. Network Management
           SystemProvisioning can change the network environment of active machines when
           changing the configuration of managed machines. The details on the possible changes
           are as follows:
            Register or cancel a physical port of a switch that connects a managed machine to
             a VLAN that is used for operations
            Register or cancel a managed machine to a load balancer group configured to a
             load balancer device


           In this section, details of a VLAN and load balancer are explained.



1.7.1.     What is VLAN?
           A VLAN (virtual LAN) is a technology that sets up a logical network configuration other
           than a physical network configuration and divides the network into multiple broadcast
           domains.
           A port VLAN groups the physical ports of switches and creates multiple virtual VLANs
           on a switch. You can change the logical network easily by changing the configuration of
           VLAN of a physical port, not changing the configuration of physical devices.
           Because one VLAN supports a broadcast domain and a broadcast frame is sent only to
           the physical port of the VLAN, the heavy traffic in the device is restrained. In addition, a
           VLAN is the interface of a router and communication between VLANs needs a router;
           which enhances the security.
           VLAN control does not support a virtual machine.



1.7.2.     Required Settings on a Switch
           To use a VLAN on switch, you need to configure the VLAN name and a physical port
           which configures the VLAN.
           In addition, the VLAN name is managed, being replaced to numbers in switch, so you
           need to configure the management number (VID value). In other words, you need to
           configure one VID value for one VLAN name.




                                                            SigmaSystemCenter 2.1 Reference Guide
44
                                                                               Network Management




1.7.3.     Usable VLAN Types
           Switch blades support a port-based VLAN, a tag-based VLAN, and a management
           VLAN. SystemProvisioning supports the port-based VLAN and a management VLAN.
           Switches managed by the connection with MasterScope Network Manager support the
           port-based VLAN and tag-based VLAN.


            Port-based VLAN
               A port-based VLAN uses a physical port for each VLAN. Frames inputted from a
               physical port are handled as frames of the allocated VLAN.
            Tag-based VLAN
               A tag-based VLAN uses a physical port for multiple VLANs by adding information
               called tags in which VID information is embedded in the frame header. The frames
               inputted from the physical port are identified by the VID information in the frame
               headers.
            Management VLAN
               A management VLAN is a function to separate user-data networks from
               management networks without setting a VLAN tag in the CPU blade.
               The management VLAN is configured with multiple CPU ports (cpu 3 to 8) and a
               redirect port (mng). User ports (lan1 to 3) cannot be attached to the management
               VLAN. The management host is connected to the redirect ports to secure
               communications between each CPU blade and management host.
               If a management VLAN is registered, a port-based VLAN and a management
               VLAN can be set as members at the same time.
               SystemProvisioning uses managed CPU blades and management VLAN to
               communicate and manage.



1.7.4.     Control of VLAN
           If settings related to a VLAN exist in a group, SystemProvisioning adds and deletes
           physical ports connecting machines to the switch VLAN based on the changes to the
           configuration.
           The following explains the internal movements of a switch in case of activating, deleting,
           replacing, and changing the usage of a machine.




Part I SigmaSystemCenter Functions Reference
                                                                                                   45
1 Functions of SigmaSystemCenter



            Activating a machine
               Adds a physical port connected to a machine to activate to the switch VLAN.




            Deleting a machine
               Deletes a physical port connected to a machine to delete from the switch VLAN.




                                                        SigmaSystemCenter 2.1 Reference Guide
46
                                                                           Network Management



            Replacing a machine
               Deletes a physical port connected to an original machine from a VLAN, and adds a
               physical port connected to a new machine to the VLAN.




            Changing the usage of a machine
               Changes the VLAN settings by deleting and activating machines.




Part I SigmaSystemCenter Functions Reference
                                                                                              47
1 Functions of SigmaSystemCenter




1.7.5.     What is a Load Balancer?
           A load balancer is a device that manages demands from exterior networks collectively
           and transfers the demands to multiple machines. A load balancer can prevent system
           down because of the high load on a machine or delay of response speed.



1.7.6.     Settings on a Load Balancer
           A load balancer has three basic settings; a setting for a load balancer virtual server, a
           setting for a target node of load balancing distribution, and a setting for a load balancer
           group which connects load balancer virtual servers and load balancer real servers.
           These settings set up a load balancer virtual server. The load balancer virtual server
           actually accesses the virtual IP address allocated to the load balancer virtual server.
           The load balance is controlled without the user being aware of how the distribution
           node is configured under the load balancer virtual server.



1.7.7.     Control of Load Balancer
           SystemProvisioning checks the settings related to a load balancer in a group when
           changing the configuration of machines. If the settings related to the load balancer exist,
           SystemProvisioning adds and deletes machines to and from the load balancer group
           registered to the group.
           The following explains the internal movements of a load balancer in case of activating,
           deleting, replacing, and changing the usage of a physical machine, and creating,
           activating, deleting a virtual machine, or Move Virtual Machine.




                                                           SigmaSystemCenter 2.1 Reference Guide
48
                                                                             Network Management



            Activating a machine (physical machine)
               Adds a machine to activate to the target of a load balancer group.




            Deleting a machine (physical machine)
               Deletes a machine to delete from a load balancer group.




Part I SigmaSystemCenter Functions Reference
                                                                                            49
1 Functions of SigmaSystemCenter



            Replacing a machine (physical machine)
               Deletes an original machine from a load balancer group and adds a new machine
               to the group.




            Changing the usage of a machine (physical machine)
               Changes settings of a load balancer group by deleting and activating a machine.




                                                        SigmaSystemCenter 2.1 Reference Guide
50
                                                                              Network Management



            Activating a machine / Create and Assign Machine (virtual machine)
               Adds a created machine to a target of the load balancer group.




            Activating a machine / Allocate Machine (virtual machine)
               Adds a machine to activate to a distribution target of a load balancer group.




Part I SigmaSystemCenter Functions Reference
                                                                                               51
1 Functions of SigmaSystemCenter



            Deleting a machine (virtual machine)
               Deletes an active machine to delete from the management target of
               SystemProvisioning from the load balancer group.




            Move Virtual Machine (virtual machine)
               Moves with Hot Migration or Cold Migration, Move, and Failover do not change the
               settings of the load balancer group.


               •   Moving using Hot Migration or Cold Migration, Move, and Failover




                                                       SigmaSystemCenter 2.1 Reference Guide
52
                                                                               Storage Management



1.8. Storage Management
           During managed machines Provisioning, SigmaSystemCenter controls connections
           between disk volumes (generally called logical disks) that are on a disk array (a storage
           device) in SAN environment and the managed machines to use the disk volumes on
           the managed machines.
           This is Access Control, which is generally called LUN Masking.
           When returning the managed machines to pools, SigmaSystemCenter disconnect the
           disk volumes from the managed machines so that the disk volumes cannot be used on
           the managed machine. SigmaSystemCenter does not execute the connection control if
           targets of Provisioning are virtual machines.


           SigmaSystemCenter enables its storage control function using functions of storage
           management software. Depending on types of the target storages, necessary storage
           management software are different, shown as follows. SigmaSystemCenter's storage
           control function does not work in an environment where the storage management
           software cannot be used.


            NEC Storage: NEC Storage Manager, NEC Storage Manager Integration Base
            Symmetrix: Solutions Enabler
            CLARiiON: Navisphere CLI


           Managed machines and disk volumes will be connected if the following operations are
           executed.


            Allocate Resource
            Scale Out
            Replace Machine
            Change Machine


           Managed machines and disk volumes will be disconnected if the following operations
           are executed.


            Release Resource
            Scale In
            Replace Machine
            Change Machine


           Before executing the operations listed above, the operations as below must be
           executed beforehand to make the storage control work:




Part I SigmaSystemCenter Functions Reference
                                                                                                   53
1 Functions of SigmaSystemCenter



           1.   Set HBAs or NIC (when using IP-SAN) on managed machines.
           2.   Install a disk array and configure the initial settings of the disk array.
           3.   Construct a SAN environment including the managed machines and the disk array.
           4.   Install storage management software and configure the initial settings of the
                storage management software. Register information of the managed machines
                and of disk volumes to the storage management software.
           5.   Register information of the disk array that is to be the target of the connection
                control, the disk volumes, the HBAs and the paths to SigmaSystemCenter. Then,
                configure SigmaSystemCenter to associate managed machines with the disk
                volumes.


           This manual does not provide instructions on how to configure hardware of managed
           machines, disk array, and storage management software. Please refer to manuals of
           them.



1.8.1.     System Configuration for NEC Storage
           NEC Storage Manager and NEC Storage Manager Integration Base must be installed
           to control NEC Storage. NEC Storage Manager Integration Base must be installed on a
           management server where SystemProvisioning is installed. NEC Storage Manager can
           be used whether it is installed on a management server with SystemProvisioning or not.
           When installing NEC Storage Manager without SystemProvisioning, configure NEC
           Storage Manager Integration Base so that the management server of
           SigmaSystemCenter can access to NEC Storage Manager through LAN.
           NEC Storage and managed machines must be connected to the same SAN network.
           NEC Storage and NEC Storage Manager must be connected to either a LAN network
           or a SAN network. Generally, LAN access is used.
           If iSCSI is used, a SAN environment will be an IP-SAN environment. Configuration of
           NEC Storage Manager and other products in an IP-SAN environment is basically the
           same as that in a SAN environment.
           StoragePathSavior must be installed on managed machines in a redundant
           configuration that has multiple paths between the managed machines and NEC
           Storage.




                                                             SigmaSystemCenter 2.1 Reference Guide
54
                                                                                Storage Management



           The following figure is an example of configuration of the products installation.




           Install NEC Storage Manager and NEC Storage Manager Integration Base and
           configure the initial settings of them.


           1.   Configuring NEC Storage Manager


                •   Register a disk array as a monitoring target. When the disk array has multiple
                    paths, configure each of them to be a monitoring target.
                •   Register a user account of NEC Storage Manager.
                •   Release the Access Control license to be available.


           2.   Configuring the SG file of NEC Storage Manager Integration Base
                NEC Storage Manager Integration Base must be configured to connect to a
                management server of NEC Storage Manager.
                Set information about IP addresses and ports of the destination management
                server of NEC Storage Manager in the SG file.


           3.   Configuring the Management view and Add Subsystem of SigmaSystemCenter
                Add "NEC Storage Manager" as a subsystem type to the subsystem settings.




Part I SigmaSystemCenter Functions Reference
                                                                                                 55
1 Functions of SigmaSystemCenter




1.8.2.     System Configuration for Symmetrix
           To control Symmetrix, Solutions Enabler must be installed on a management server
           where SystemProvisioning is installed. A management server of Solutions Enabler
           must be connected to a SAN environment where the target Symmetrix exists through
           FC. If the management server is not connected to the SAN network,
           SigmaSystemCenter cannot control storages.
           PowerPath must be installed on managed machines in a redundant configuration that
           has multiple paths between the managed machines and Symmetrix.




           After installing Solutions Enabler, configure it as follows:


           1.   Configuring Solutions Enabler
                Verify that the path of Solutions Enabler is registered to the environmental variable
                PATH. If not, register the Solutions Enabler's path.


           2.   Configuring the Management view and Add Subsystem of SigmaSystemCenter
                Add "EMC Symmetrix" as a subsystem type to the subsystem setting.




                                                            SigmaSystemCenter 2.1 Reference Guide
56
                                                                              Storage Management




1.8.3.     Configuration for CLARiiON
           To control CLARiiON, Navisphere CLI must be installed on a management server
           where SystemProvisioning is installed. Navisphere CLI and CLARiiON must be
           connected to a LAN network. If they are not, SigmaSystemCenter cannot control
           storages.
           PowerPath must be installed on managed machines in a redundant configuration that
           has multiple paths between the managed machines and CLARiiON.




           After installing Navisphere CLI, configure it as follows:


           1.   Configuring Navisphere CLI
                Verify that the path of Navisphere CLI is registered to the environmental variable
                PATH. If not, register the Navisphere CLI's path.


           2.   Enabling the data access control
                Enable the data access control to activate LUN Masking control.


           3.   Configuring the Management view and Add Subsystem of SigmaSystemCenter
                Add "EMC CLARiiON" as a subsystem type to the subsystem setting.




Part I SigmaSystemCenter Functions Reference
                                                                                                 57
1 Functions of SigmaSystemCenter




1.8.4.     Connection Control of Disk Volume
           To connect disk volumes (with managed machines), SigmaSystemCenter issues an
           order to storage management software. This order is based on the following
           information obtained from the configuration database.


            Information about associations between HBAs on machines and disk volumes on a
             disk array, obtained from the host setting on the Operation view.
            Information about machines and a disk array to be targets of storage control,
             obtained from the setting of the machines and the disk array on the Resource
             view.


           If Machine1 is allocated to Host1 in the figure exemplified at the bottom, the following
           processes will run by the connection control of disk volume:


           1.   Obtaining the association information configured on the host setting.
                Obtains information of the association between HBAs and the both of Disk1 and
                Disk2 from the host setting of the Host1. The HBA's HBA number is 1. The Disk1
                and Disk2 exist in DiskArray1.


           2.   Obtaining information about machines
                Obtains information about HBA Address (WWPN and WWNN) and the path from
                the machine setting of the Machine1 that was allocated. HBA Address
                corresponds to HBA number1 which is configured on the host setting of Host1. The
                path information includes the combination of paths of the HBA's port and the port
                on the disk array, which is used for the connection process.


           3.   Obtaining information about a disk array.
                Obtains information about Disk1 and Disk2 in DiskArray1, such as disk array
                information and disk volume ID. The information is necessary for the connection
                process.


           4.   Connection process
                Calls commands to execute the connection process on storage management
                software and API by using the information obtained in Process 1 through 3. The
                connection process will run.




                                                            SigmaSystemCenter 2.1 Reference Guide
58
                                                                             Storage Management




           After executing Allocate Resource, disks that were connected will be recognized in the
           order of Disk1, Disk2, ...on Host1 as the figure below. When changing the order, an
           order registered in the Storage List on the host setting must be changed.
           If LocalDisk exists, Disk1 and Disk2 will be recognized as the second and the third
           respectively. Meanwhile, Disk1 is recognized as the first in a SAN boot configuration,
           and the system will boot on Disk1. If a disk other than the control target of
           SigmaSystemCenter is assigned, the disk will be recognized before Disk1. In this case,
           the system cannot boot on Disk1. Therefore, do not connect a disk other than the
           control target of SigmaSystemCenter using other tools.




Part I SigmaSystemCenter Functions Reference
                                                                                                59
1 Functions of SigmaSystemCenter




           Basically, the system will work as described above.
           However concepts, terms, preparations, etc. varies depending on the storage types.


           Explanations of the concepts and instructions on the preparation are provided
           according to the storage types in the next subsections.




1.8.5.     Connection Control of NEC Storage (FC Model) Disk
           Volume
           The concept of the connection control of NEC Storage (FC Model) is as the following
           figure.


           The connection control of disk volume is called Access Control for NEC Storage
           Manager.
           Access Control in NEC Storage Manager controls registration of information about LD
           Set and logical disk assignment to NEC Storage. Access Control registers the
           information, and NEC Storage permits managed machines to access to the logical
           disks.




                                                         SigmaSystemCenter 2.1 Reference Guide
60
                                                                            Storage Management



           LD Set is a concept that represents a path from the HBA on machines to a logical disk
           through the ports on a disk array. Before executing Access Control, HBAs on managed
           machines must be registered to the target LD Set and the mode of ports that are to be
           used by the disk array must be changed to WWN mode. WWPN information is
           necessary for identifying the HBA. SigmaSystemCenter has information of HBA
           numbers to manage HBAs virtually on the setting of a host where the specific machine
           information does not exist.
           When using redundant HBA configuration, all the HBAs must be registered to the LD
           Set setting on NEC Storage Manager. All HBAs that are to be used for associating the
           HBA numbers on the host setting with the disk volume must be registered to
           SigmaSystemCenter as well. However, combinations of the HBAs on machines and the
           ports on the disk array do not have to be registered.




Part I SigmaSystemCenter Functions Reference
                                                                                               61
1 Functions of SigmaSystemCenter




1.8.6.     Connection Control of NEC Storage (iSCSI Model) Disk
           Volume
           The concept of the connection control of NEC Storage (iSCSI Model) is as the following
           figure.


           The connection control of disk volume is called Access Control for NEC Storage
           Manager.
           Access Control in NEC Storage Manager controls registration of information about LD
           Set and logical disk assignment to NEC Storage. Access Control registers the
           information, and NEC Storage permits managed machines to access to the logical
           disks.
           LD Set is a concept that represents a path from the HBAs on machines to a logical disk
           through the ports on a disk array. Before executing Access Control, Initiators on
           managed machines must be registered to the target LD Set and the portals that are to
           be used by the disk array must be configured. iSCSI names and IP addresses must be
           configured on the Initiators and the portals respectively. SigmaSystemCenter uses
           information of HBA numbers to manage Initiators virtually on the setting of a host where
           the specific machine information does not exist.
           Combinations of the HBAs on machines and the portals on the disk array do not have
           to be registered.




                                                         SigmaSystemCenter 2.1 Reference Guide
62
                                                                              Storage Management




1.8.7.     Necessary Preparation for NEC Storage Control
           To control logical disks (LD, disk volume) and connections of managed machines, the
           following preparations are required.


            Configuring NEC Storage Manager
               •   Creating a logical disk
                   A logical disk that is to be the connection target of machines. When creating a
                   logical disk, Pool and RANK must be configured.
               •   Creating LD Set and configuring Access Control
                   Configure a port on a target controller of SigmaSystemCenter's control as
                   below.
                   -   Change the mode of the port to WWN mode.
               •   Create LD Set for each managed machine. Platforms and partitions must be
                   configured in addition to the LD Set names.
                   -   LD Set Name : Configure the LD Set name
                   -   Platform: Configure the platform according to the OS
                       During SigmaSystemCenter's connection control of disk volume,
                       appropriate values will be set depending on the OS type. Therefore, this

Part I SigmaSystemCenter Functions Reference
                                                                                                  63
1 Functions of SigmaSystemCenter

                       item does not have to be configured precisely if Access Control is not
                       executed by something other than SigmaSystemCenter.


                       The OS of a managed machine is Windows: WN
                       The OS of a managed machine is Linux: LX


                   -   Partition: Configure a target LD Set for control and partitions to which the
                       logical disk belongs.
                       If a LD Set is being associated with a logical disk, which belong to
                       different partition respectively, an error will occur during the storage
                       control. Therefore, you must configure the LD Set and the logical disk on
                       the same partition.


               •   WWPN of HBAs which are set on managed machines must be registered to
                   the LD Set setting as path information. The path information is to be used
                   when connecting to the LD Set. When using a redundant configuration,
                   register WWPN of all HBAs that compose the redundant configuration.
                   WWPN can be checked on the information printed on HBAs or on the BIOS
                   setting screen of HBAs.
                   When using iSCSI, configure the Initiator name of the iSCSI Initiator instead of
                   HBA's WWPN as path information.
               •   Assignments of LD Set and logical disks will be executed during
                   SigmaSystemCenter's control. Therefore, they do not have to be executed on
                   NEC Storage Manager.


            Configuring SigmaSystemCenter
               •   Registration of a disk array
                   Register information of a disk array that is to be a target of control from the
                   Resource view. Obtain information of the target disk array from the NEC
                   Storage Manager which is linked to the disk array. Therefore, the information
                   of the target disk array must be registered to NEC Storage Manager.
               •   Registration of disk volumes
                   After the registration of the disk array, register a logical disk (LD) on the
                   Resource view as the target of the control. When registering disk volumes, a
                   list of logical disks that are created in NEC Storage Manager are displayed as
                   options.
                   -   Name: Displays the name of the logical disk that is created in NEC
                       Storage Manager.
                   -   Number: Displays the number of the logical disk that is created in NEC
                       Storage Manager.
                   -   Share Status: Change the share status to Share when sharing the disk
                       volume with multiple machines.




                                                         SigmaSystemCenter 2.1 Reference Guide
64
                                                                              Storage Management



               •   Registration of HBAs
                   Register information of HBAs that are set on managed machines on the
                   Resource view / Machine Property Setting. A HBA setting information is
                   composed of a HBA number and information of WWPN. Select an arbitrary
                   number as a management number on SigmaSystemCenter for the HBA
                   number. The selected HBA number is used for identifying HBAs on managed
                   machines that are to connect to the disk volume. As for WWPN, a list of
                   WWPN information collected from NEC Storage Manager is displayed as
                   options for the setting. Select the appropriate WWPN.
                   The WWPN information of HBAs is collected from LD set registered in NEC
                   Storage Manager. Register the path of the LD Set in NEC Storage Manager
                   and execute the storage information collection. Then, configure HBAs on
                   SigmaSystemCenter.
                   When using iSCSI, configure the Initiator name of the iSCSI Initiator instead of
                   HBA's WWPN as path information.
               •   Registration of disk volumes to connect to hosts
                   Register combinations of disk volumes that are to be connected when
                   executing Allocate Resource and HBAs to the host setting. The disk volumes
                   are combinations of the target disk array and the disk volumes' name. The
                   HBAs are the HBA number.
                   SigmaSystemCenter identifies the target disk volume by the disk array name
                   and the disk volume name during the connection control. Then,
                   SigmaSystemCenter also identifies the target HBA and the path information
                   by the HBA number to execute the connection process.
                   When using a redundant configuration, do not specify individual HBA numbers.
                   Configure all HBAs to be connected.




Part I SigmaSystemCenter Functions Reference
                                                                                                  65
1 Functions of SigmaSystemCenter




1.8.8.     Connection Control of Symmetrix
           The concept of the connection control of Symmetrix is as the following figure.


           The connection control of disk volume is called Device Masking for Symmetrix.
           Device Masking combines the WWPN of managed machines' HBA, the ID of the disk
           array, the name of the director to be used, the port number and the device name of the
           LUN and registers it to the access control information of the disk array. The
           combinations that are registered to the access control information of the disk array are
           given permission to access to LUNs of the disk array.




                                                         SigmaSystemCenter 2.1 Reference Guide
66
                                                                                Storage Management




1.8.9.     Necessary Preparation for Symmetrix Control
           To control devices (disk volumes) and connections of managed machines, the following
           preparations are required.


            Configuring Symmetrix devices
               •   To create a device
                   Information about instructions on how to create Symmetrix device is not open.
                   When changing the configuration, such as creating a device, please contact
                   the Symmetrix support.


            Configuring SigmaSystemCenter
               •   Registration of a disk array
                   Register information of a disk array that is to be a control target on the
                   Resource view. The information of the disk array must be collected
                   beforehand.
               •   Registration of disk volumes
                   After registration of the disk array, register devices as control targets. When
                   registering disk volumes, a list of created devices is displayed as options. In
                   addition, Metadevice can be used from SigmaSystemCenter 2.1 Update 3.


                   -     Name: Displays the name of the created device.
                   -     Number: Displays the number of the device.
                   -     Share Status: Change the Share Status to Share when sharing the
                         device with multiple machines.


               •   Registration of information about HBAs and paths
                   Register WWPN information of HBAs that are set on managed machines and
                   information about paths between the managed machines and the disk array
                   by using the ssc command and by using Machine Property setting function of
                   the Web Console.


                   -     The disk array must be registered beforehand to register the path
                         information.
                   -     Display the path information of the disk array using the ssc command.


                       >ssc show diskarraypath 000290100434
                       000290100434/09A/0
                       000290100434/09A/1
                       000290100434/08B/0
                       000290100434/08B/1



Part I SigmaSystemCenter Functions Reference
                                                                                                     67
1 Functions of SigmaSystemCenter



                   -     Register the HBA addresses (WWPN, WWNN) and paths of the disk
                         array that is to be connected from the HBAs to SigmaSystemCenter. If a
                         number of combinations of the HBAs and the disk array's paths exist,
                         register all patterns of the combinations.


                       >ssc set hba CK100000 000290100434/09A/0
                       2000-0000-C92B-53D3
                       >ssc set hba CK100000 000290100434/09A/1
                       2000-0000-C92B-53D3
                       >ssc set hba CK100000 000290100434/08B/0
                       2000-0000-C92B-53D3
                       >ssc set hba CK100000 000290100434/08B/1
                       2000-0000-C92B-53D3
                       >ssc set hba CK100000 000290100434/09A/0
                       2000-0000-C92C-53D3
                       >ssc set hba CK100000 000290100434/09A/1
                       2000-0000-C92C-53D3
                       >ssc set hba CK100000 000290100434/08B/0
                       2000-0000-C92C-53D3
                       >ssc set hba CK100000 000290100434/08B/1
                       2000-0000-C92C-53D3


                   -     Obtain the HBA numbers which correspond to the HBA information
                         registered with the ssc command listed above and register them on the
                         Resource view / Machine Property setting.


               •   Registration of disk volumes to connect to a host
                   Register combinations of the disk volumes and the HBAs that are to be
                   connected when executing Allocate Resource to the host setting. For the disk
                   volumes' part of the combinations, specify combinations of the target disk
                   array name and the disk volume names. Specify the HBA numbers for the
                   HBA's part. When executing the connection control of the disk volumes,
                   SigmaSystemCenter identifies the target disk volumes by the disk array name
                   and the disk volume name and identifies the target HBAs and the path
                   information to execute the connection control.
                   When using a redundant configuration, do not specify individual HBA numbers.
                   Configure all HBAs to be connected.




                                                        SigmaSystemCenter 2.1 Reference Guide
68
                                                                            Storage Management




1.8.10. About Commands Used in Symmetrix Control
            Obtaining information of a disk array and a storage group
               Use the following commands to obtain information about a registered disk array
               (symmID) using ssc show disk arraypath command.


                 symcfg list -output XML
                 symcfg list -DIR ALL -address -sid [symmID] -output XML


            Obtaining LUN information
               Obtain a list of LUNs of the disk array (symmID) using the following command.


                 symcfg list -DIR ALL -address -sid [symmID] -output XML


            Connection control of disk volume
               Obtain information about hosts, addresses of HBAs, paths from the setting of
               SigmaSystemCenter and execute the connection control.


                 symmask -sid [symmID] -wwn [WWN] add devs [LD] -dir [DIR]
                 -p [PORT]
                 symmask -sid [symmID] refresh -noprompt


            Disconnection control of disk volume
               Obtain information about hosts, addresses of HBAs, paths from the setting of
               SigmaSystemCenter and execute the disconnection control.


                 symmask -sid [symmID] -wwn [WWN] remove devs [LD] -dir
                 [Dir] -p [Port] -force
                 symmask -sid [symmID] refresh -noprompt




Part I SigmaSystemCenter Functions Reference
                                                                                               69
1 Functions of SigmaSystemCenter




1.8.11. Connection Control of CLARiiON
           The concept of the connection control of CLARiiON is as the following figure.


           The connection control of disk volume is called Data Access Control for CLARiiON.
           Data Access Control assigns the combinations of information as listed below to the
           storage group to register them to the access control information of the disk array. The
           combinations that are registered to the access control information of the disk array are
           given permission to access to LUNs of the disk array.


            The name of the target storage group of assignment.
            The name of the destination host to which managed machines assigned when
             executing Allocate Resource.
            WWPN and WWNN of the managed machines' HBA
            The combinations of the name of the destination SP to which HBAs connects and
             the port number
            ALU and HLU of LUNs


           Connection information including the IP address of the SP and the account is needed
           during the connection control.




                                                         SigmaSystemCenter 2.1 Reference Guide
70
                                                                              Storage Management




1.8.12. Necessary Preparation for CLARiiON Control
           To control LUNs (disk volumes) and connections of managed machines, the following
           preparations are required.


            Configuring CLARiiON management tools such as Navisphere CLI
               •   To create LUNs
                   LUNs that are to be connected to machines can be created using the following
                   command and using Navisphere Manager.


                       naviseccli -h [IP of SP] bind [RAID Type] [LUN Number] -rg
                       [RAID Group ID] -cap [LUN Size] -sp [SP Name] -sq [Unit of
                       LUN Size]


                   RAID groups to which the LUNs are to belong must be created to create the
                   LUNs. SigmaSystemCenter does not support MetaLun.


               •   Creating a storage group
                   Create storage groups that correspond to the target managed machines of the
                   control. They can be created using the following command and using
                   Navisphere Manager.


                       naviseccli -h [IP of SP] storagegroup -create -gname [Storage
                       Group Name]


            Configuring SigmaSystemCenter
               •   Registration of a disk array and selection of commands
                   Register a disk array on the Resource view. Information about connecting to
                   an arbitrary SP of the disk array is required to register the CLARiiON disk
                   array. Specify IP Address, User Name, Password and Scope when
                   configuring the disk array. If none of User Name, Password, or Scope is
                   specified, an existing command, Navicli, will be called. However, do not use it
                   usually because it is an option remained for compatibility.


                   -     IP Address: Enter the IP address of the SP that is to be connected with
                         Navisphere CLI during the storage control. Select either of SPs if two SPs
                         exist.
                   -     User Name: Enter a user name. The user name will be used when
                         connecting the SP with Navisphere CLI (Naviseccli).
                   -     Password: Enter a password. The password will be used when
                         connecting SP with Navisphere CLI (Naviseccli).



Part I SigmaSystemCenter Functions Reference
                                                                                                  71
1 Functions of SigmaSystemCenter



                   -     Scope: Enter a value of scope of an account that is to be used when
                         connecting SP with Navisphere CLI (Naviseccli). Enter one of the
                         following integer values, "0", "1", "2", which indicate "global", "local",
                         "LDAP" respectively. Normally, specify "0".
                   -     If an error occurs on the registered SP, the control of the disk array
                         cannot be executed. Therefore, reregister another SP's connection
                         information to the setting of the disk array in that case.


               •   Registration of disk volumes
                   After registration of the disk array, register LUNs as target disk volumes of the
                   control. When registering the LUNs, a list of created LUNs is displayed as
                   options.


                   -     Name: Displays the name of the created LUN.
                   -     Number: Displays the number of the LUN.
                   -     Share Status: Change the Share Status to Share when sharing the disk
                         volume with multiple machines.


               •   Registration of information about HBAs and paths
                   Register WWNN and WWPN information of HBAs that are set on managed
                   machines and information about paths between the managed machines and
                   the disk array by using the ssc command and by using Machine Property
                   setting function of the Web Console.


                   -     The disk array must be registered beforehand to register the path
                         information.
                   -     Display the path information of the disk array using the ssc command.


                       >ssc show diskarraypath CK100000
                       SG20(CK100000/ SP A /0)
                       SG20(CK100000/ SP A /1)
                       SG20(CK100000/ SP B /0)
                       SG20(CK100000/ SP B /1)


                   -     Register the HBA addresses (WWPN, WWNN) and paths of the disk
                         array that is to be connected from the HBAs to SigmaSystemCenter.
                         WWNN must be specified for CLARiiON. If a number of combinations of
                         the HBAs and the disk array's paths exist, register all patterns of the
                         combinations.


                       >ssc set hba CK100000 "SG20(CK100000/ SP A /0)"
                       2000-0000-C92B-53D3 -wwnn 1000-0000-C92B-53D3
                       >ssc set hba CK100000 "SG20(CK100000/ SP A /1)"
                       2000-0000-C92B-53D3 -wwnn 1000-0000-C92B-53D3
                                                          SigmaSystemCenter 2.1 Reference Guide
72
                                                                           Storage Management

                       >ssc set hba CK100000 "SG20(CK100000/ SP B /0)"
                       2000-0000-C92B-53D3 -wwnn 1000-0000-C92B-53D3
                       >ssc set hba CK100000 "SG20(CK100000/ SP B /1)"
                       2000-0000-C92B-53D3 -wwnn 1000-0000-C92B-53D3
                       >ssc set hba CK100000 "SG20(CK100000/ SP A /0)"
                       2000-0000-C92C-53D3 -wwnn 1000-0000-C92C-53D3
                       >ssc set hba CK100000 "SG20(CK100000/ SP A /1)"
                       2000-0000-C92C-53D3 -wwnn 1000-0000-C92C-53D3
                       >ssc set hba CK100000 "SG20(CK100000/ SP B /0)"
                       2000-0000-C92C-53D3 -wwnn 1000-0000-C92C-53D3
                       >ssc set hba CK100000 "SG20(CK100000/ SP B /1)"
                       2000-0000-C92C-53D3 -wwnn 1000-0000-C92C-53D3


                   -     Obtain the HBA numbers which correspond to the HBA information
                         registered with the ssc command listed above and register them on the
                         Resource view / Machine Property setting.


               •   Registration of disk volumes to connect to a host
                   Register combinations of the disk volumes and the HBAs that are to be
                   connected when executing Allocate Resource to the host setting. For the disk
                   volumes' part of the combinations, specify combinations of the target disk
                   array name and the disk volume names. Specify the HBA numbers for the
                   HBA's part. When executing the connection control of the disk volumes,
                   SigmaSystemCenter identifies the target disk volumes by the disk array name
                   and the disk volume name and identifies the target HBAs and the path
                   information to execute the connection control.
                   When using a redundant configuration, do not specify individual HBA numbers.
                   Configure all HBAs to be connected.




Part I SigmaSystemCenter Functions Reference
                                                                                              73
1 Functions of SigmaSystemCenter




1.8.13. About Commands Used in CLARiiON Control
            Obtaining information of a disk array and a storage group
               Use the following commands to obtain information about a registered disk array (IP
               of the SP) using ssc show disk arraypath command.


                 naviseccli -h [IP of SP] getall -array
                 naviseccli -h [IP of SP] port -list
                 naviseccli -h [IP of SP] getall -sg


            Obtaining LUN information
               Obtain a list of LUNs of the disk array (IP of the SP) using the following command.


                 naviseccli -h [IP of SP] getall -lun


            Connection control of disk volume
               Obtain information about hosts, addresses of HBA, paths from the setting of
               SigmaSystemCenter and execute the connection control. LUNs are numbered
               sequentially (Host LUN Number). The first LUN is "0".


                 naviseccli -h [IP of SP] storagegroup -setpath -host [Host
                 Name] -hbauid [WWNN]:[WWPN] -sp [SP Name] -spport [SP Port]
                 -o
                 naviseccli -h [IP of SP] storagegroup -sethost -host [Host
                 Name] -type 3 -failovermode 1 -arraycommpath 1 -o
                 naviseccli -h [IP of SP] storagegroup -addhlu -gname
                 [Storage Group Name] -hlu [Host LUN Number] -alu [LUN
                 Number]
                 naviseccli -h [IP of SP] storagegroup -connecthost -host
                 [Host Name] -gname[Storage Group Name] -o


            Disconnection control of disk volume
               Obtain information about hosts, addresses of HBA, paths from the setting of
               SigmaSystemCenter and execute the disconnection control.


                 naviseccli -h [IP of SP] storagegroup -removehlu -gname
                 [Storage Group Name] -hlu [Host LUN Number] -o
                 naviseccli -h [IP of SP] storagegroup -disconnecthost
                 -host [Host Name] -gname [Storage Group Name] -o
                 naviseccli -h [IP of SP] port -removeHBA -hbauid
                 [WWNN]:[WWPN] -o




                                                         SigmaSystemCenter 2.1 Reference Guide
74
                                                     Pool Machine Used for Configuration Change



1.9. Pool Machine Used for Configuration
     Change
           A pool machine is used with various uses when changing the configuration of machines.
           In this section, operation of a pool machine and the use of a managed machine that
           does not belong to any group; we call the machine a shared pool machine.



1.9.1.     Operations of a Pool Machine
           SystemProvisioning uses a pool machine as follows when changing the configuration
           of machines:
            With Activating a machine, SystemProvisioning adds a new machine to activate
             from pool machines.
            With Replacing a machine, SystemProvisioning replaces a failed machine with a
             pool machine for recovery.
            With Changing Machine Usage, if you register a machine running in a group as a
             pool machine to a new group, you can change the usage of the machine to the
             new machine.


           In addition, when you perform operations, such as N+1 Failover, you need to prepare
           pool machines.


           Action name                  Overview of actions              Condition of pool machine

           Activating a machine         Adds a new logical machine to    A pool machine in a group:
                                        activate in a group.             Register one or more unused
                                                                         normal pool machines to the
                                                                         group which the machine
                                                                         belongs to.
                                                                         A pool machine that belongs to
                                                                         one group or multiple groups
                                                                         can be used.
                                                                         A shared pool machine:
                                                                         Prepare one or more normal
                                                                         pool machines that do not
                                                                         belong to any group.
           Replacing a machine          Replaces a failed machine with   A pool machine in a group:
                                        a normal pool machine.           Register one or more unused
                                                                         normal pool machines to the
                                                                         group that the machine
                                                                         belongs to.
                                                                         A pool machine that belongs to
                                                                         one group or multiple groups
                                                                         can be used.
                                                                         A shared pool machine:
                                                                         Prepare one or more normal
                                                                         pool machines that do not
                                                                         belong to any group.



Part I SigmaSystemCenter Functions Reference
                                                                                                    75
1 Functions of SigmaSystemCenter


           Action name                   Overview of actions            Condition of pool machine

           Changing usage of a machine   Temporarily stops an active    Register the machine to
                                         machine and uses the machine   change the usage as a pool
                                         for a different use.           machine to a new group.


           Using pool machines increases the availability of the system by dealing with machine
           failures and heavy loads on the system effectively. Each pool machine operating
           method has the following characteristics:
            Setting a pool machine always on standby
               Set at least one pool machine always on standby when operating the system.
               Doing so enables to deal with the machine configuration change any time, you can
               maintain the system availability.
               With this use, the required system costs depend upon the number of units in the
               pool server.
            Using an active machine as a pool machine
               By registering a machine running with certain tasks as a pool machine for other
               tasks (groups), the machine can be used by other tasks according to the machine
               load.
               With this use, the system costs can be reduced because exclusive pool machines
               are unnecessary.
            Not setting a pool machine
               If pool machines are not prepared, configurations cannot be changed
               automatically, such as Replace Machine by generation of an error.
               Each time a machine fails or a heavy load condition is generated on the system, a
               machine must be prepared to deal with these issues.



1.9.2.     Conditions to Use a Shared Pool Machine and Machine
           Name Configuration
           When changing the configuration, such as activating or replacing a machine, if the
           machine meets the following conditions, you can add a managed machine which does
           not belongs to any group to a group and activating the machine.


           Conditions of shared pools:
            If a target group permits to use shared pools.
             For more details, see Subsection 4.6.1, "General Tab" in SigmaSystemCenter
             Web Console Reference Guide.
            If there is no usable machine on standby in a pool of a target group.
            When an active machine exists in a target group, if a machine which model name
             coincides with that of an active machine exists in a shared pool.
            If a machine registered to a subsystem (DPM) that manages distribution software
             to distribute to a target machine exists in a shared pool.


                                                         SigmaSystemCenter 2.1 Reference Guide
76
                                                      Pool Machine Used for Configuration Change



           In addition, the hardware information can be configured by configuring the setting for a
           Model Name on the property window of a physical machine when the machine is not
           activated and is in a shared pool. If the Model Name is not configured,
           SystemProvisioning configures the value acquired from NEC ESMPRO Manager
           automatically when the machine is set to an active status in a group.


           The following is an example explaining model names in a shared pool.




           The Physical machine #1 and the Physical machine #2, for which model names are not
           configured, can be added to the Model #1 where there is no active machine. These
           machines cannot be added to the Model #2 where an active machine exists.


           Note: A model name is not configured to a newly set-up physical machine. If you are to
           activate the machine in a model where there is a machine with its model name
           configured, configure the model name in advance.




Part I SigmaSystemCenter Functions Reference
                                                                                                  77
1 Functions of SigmaSystemCenter




           By configuring the same model name on the properties of the Active machine #1, the
           Physical machine #1 can be added to the Model #1. This machine cannot be added to
           the Model #2 (an active machine for which a different model name configured exists).
           In addition, you can configure a specific value for the model name by clearing a check
           in the Auto update model name check box on the Machine Property Setting window.


           Note: If the Auto update model name check box is selected, a model name collected
           from NEC ESMPRO Manager can be updated automatically.
           Pay attention for an active machine with a certain model name and an active machine
           with a model name that is collected from NEC ESMPRO Manager not to exist.


           Reference: For the details of Machine Property Setting, see Subsection 3.11.1,
           "General Tab" in SigmaSystemCenter Web Console Reference Guide.




                                                        SigmaSystemCenter 2.1 Reference Guide
78
                                                                  Changes in Machine Configuration



1.10. Changes in Machine Configuration
           In following subsections, the processes of machine configuration changes, including
           activating, creating, deleting, replacing, moving, and changing the usage of a machine,
           are explained. The following symbols are used for each step of the processes:
            [Standard]: Required step, regardless of the use of optional products, such as
             VLAN and storage
            [Storage]: Step to manage storage
            [VLAN]: Step to manage a VLAN
            [LB]: Step to manage a load balancer
            [Management NW]: Step for only when a management network is configured


           In addition, SystemProvisioning runs action sequences when changing configurations
           of machines or running the processes of configuration changes. An action sequence is
           a definition of a series of actions, such as the configuration change and
           SystemProvisioning manages each one of action sequences as a Job.
           For more details of the action sequence, see Chapter 3, "Details of Action Sequence."


           Note: The order of VLAN Settings is changed from SigmaSystemCenter 2.1. If you
           want to change the order to the original order, change the name of the following Action
           Sequence XML files in the installation path of SystemProvisioning\ActionSequence,
           and replace the files. Move the original XML files to be replaced to an arbitrary folder.
               •    ChangeServerGroup_compat.xml
                    The XML file name to replace: ChangeServerGroup.xml
               •    MoveFromGroupToManaged_compat.xml
                    The XML file name to replace: MoveFromGroupToManaged.xml
               •    MoveFromGroupToPool_compat.xml
                    The XML file name to replace: MoveFromGroupToPool.xml
               •    MoveFromPoolToGroup_compat.xml
                    The XML file name to replace: MoveFromPoolToGroup.xml
               •    MoveMasterMachineToGroup_compat.xml
                    The XML file name to replace: MoveMasterMachineToGroup.xml
               •    TakeOverMachine_compat.xml
                    The XML file name to replace: TakeOverMachine.xml




Part I SigmaSystemCenter Functions Reference
                                                                                                   79
1 Functions of SigmaSystemCenter




1.10.1. Activating Machine / Allocate Machine (Physical Machine)
           Activates a specified pool machine in a group.


           The following operations are the targets of this operation:
            Operations view - Action menu - Allocate Machine - Select a machine manually -
             Select a machine from group pool
            pvmutl add
            pvmutl addspecname
            ssc assign machine


           Order   Step                                           Detail

           1       [Standard]                                     Checks that a specified machine is not
                   Checking that a specified machine is           running in a group.
                   running
           2       [Standard]                                     ▪ When Host Setting is specified
                   Searching for Host Setting                     Checks if the specified Host Setting is
                                                                  available.
                                                                  ▪ When Host Setting is not specified
                                                                  Checks if there exists available Host
                                                                  Setting.
           3       [Standard]                                     Checks that the status of the specified
                   Checking status of machine                     machine is not In-process.

           4       [Standard]                                     Updates the status of the machine to
                   Updating configuration information             In-process.

           5       [Standard]                                     Allocates an unused Host Setting, such as
                   Allocating Host Setting                        a host name and IP address, defined to the
                                                                  group.
           6       [Storage]                                      Connects a disk volume defined to the Host
                   Connecting to storage (disk volume)            Setting, allocated in the step 5, to the
                                                                  machine.
           7       [VLAN]                                         Registers a switch port connected to the
                   VLAN settings                                  machine to a VLAN.

           8       [Standard]                                     Distributes operating distribution software
                   Distributing operating distribution software   registered to the machine, its Host Setting,
                                                                  its model, and its group.
           9       [Standard]                                     Starts the machine.
                   Starting machine
           10      [Management NW]                                Registers the machine to the monitored
                   Registering to NEC ESMPRO Manager              target of NEC ESMPRO Manager.

           11      [Standard]                                     Collects the hardware information of the
                   Collecting and updating machine                machine from NEC ESMPRO Manager and
                   information                                    applies the information to the configuration
                                                                  database of the machine.



                                                              SigmaSystemCenter 2.1 Reference Guide
80
                                                                    Changes in Machine Configuration


           Order   Step                                        Detail

           12      [LB]                                        Registers the machine to a load balancing
                   Registering to load balancer group          node of a load balancer group.

           13      [Standard]                                  Updates the machine’s process completion
                   Updating configuration information          status, etc.




1.10.2. Activating Machine / Scale Out (Physical Machine)
           Selects a machine from a pool according to the Machine Pool Setting of the Group
           Property Setting and execute Allocate Machine to activate the machine in a group.


           The following operations are the targets of this operation:
            Operations view - Scale Out
            Operations view - Action menu - Allocate Machine - Select a machine
             automatically
            pvmutl add
            pvmutl addspecname
            ssc assign machine
            Action of a policy Action for Group / Add a Machine to the Group


           Order   Step                                        Detail

           1       [Standard]                                  Creates a list of machines that exist in a
                   Creating list                               specified group pool.

           2       Repeats the following process to search for a machine that can be activated in a group
                   and belongs to only one group pool.
                   If a target machine is found, then executes the step 6. If not, executes the step 3.
                   [Standard]                                  Selects a machine that belongs to only one
                   Selecting machine                           group pool in the list created in the step 1.

                   [Standard]                                  ▪ When Host Setting is specified
                   Searching for Host Setting                  Checks if the specified Host Setting is
                                                               available.
                                                               ▪ When Host Setting is not specified
                                                               Checks if there exists available Host
                                                               Setting.
                   [Standard]                                  Checks the status of the selected machine.
                   Checking status of machine                  If the status is not In-process, Error, or
                                                               Maintenance, the machine becomes a
                                                               target of the operation.
           3       Repeats the following process to search for a machine that can be activated in a group
                   and belongs to multiple group pool.
                   If a target machine is found, then executes the step 6. If not, executes the step 4.
                   [Standard]                                  Selects a machine that belongs to multiple
                   Selecting machine                           group pools in the list created in the step 1.



Part I SigmaSystemCenter Functions Reference
                                                                                                            81
1 Functions of SigmaSystemCenter


           Order   Step                                           Detail

                   [Standard]                                     ▪ When Host Setting is specified
                   Searching for Host Setting                     Checks if the specified Host Setting is
                                                                  available.
                                                                  ▪ When Host Setting is not specified
                                                                  Checks if there exists available Host
                                                                  Setting.
                   [Standard]                                     Checks the status of the selected machine.
                   Checking status of machine                     If the status is not In-process, Error, or
                                                                  Maintenance, the machine becomes a
                                                                  target of the operation.
           4       [Standard]                                     Creates a list of groups to which When the
                   Creating list                                  group pool doesn’t have an available
                                                                  machine, use a machine in the shared pool
                                                                  is configured to its Group Property Setting
                                                                  and in which available Host Setting exists.
                                                                  This list is created from a group with higher
                                                                  priority.
                                                                  In addition, a list of machines in the shared
                                                                  pool is also created.
           5       Repeats the following process to search for a machine that can be activated in a group
                   and belongs to the shared pool.
                   If a target machine is found, then executes the step 6. If not, the Job ends with an error.
                   [Standard]                                     Selects a group and machine from the list
                   Checking status of machine                     created in the step 4 and checks the
                                                                  following points:
                                                                  ▪ The status of the machine is not
                                                                  In-process, Error, Maintenance, or
                                                                  Discovered.
                                                                  ▪ A model name of the selected machine is
                                                                  the same as that of an already running
                                                                  machine.
                                                                  ▪ DPM that manages the machine is the
                                                                  same as that manages software which is
                                                                  set in a group, etc.
                                                                  ▪ The type of the machine and the type of
                                                                  the group (model) is the same.
           6       [Standard]                                     Updates the status of the machine to
                   Updating configuration information             In-process.

           7       [Standard]                                     Allocates an unused Host Setting, such as
                   Allocating Host Setting                        a host name and IP address, defined to the
                                                                  group.
           8       [Storage]                                      Connects a disk volume defined to the Host
                   Connecting to storage (disk volume)            Setting, allocated in the step 5, to the
                                                                  machine.
           9       [VLAN]                                         Registers a switch port connected to the
                   VLAN settings                                  machine to a VLAN.

           10      [Standard]                                     Distributes operating distribution software
                   Distributing operating distribution software   registered to the machine, its Host Setting,
                                                                  its model, and its group.
           11      [Standard]                                     Starts the machine.
                   Starting machine

                                                              SigmaSystemCenter 2.1 Reference Guide
82
                                                                  Changes in Machine Configuration


           Order   Step                                       Detail

           12      [Management NW]                            Registers the machine to the monitored
                   Registering to NEC ESMPRO Manager          target of NEC ESMPRO Manager.

           13      [Standard]                                 Collects the hardware information of the
                   Collecting and updating machine            machine from NEC ESMPRO Manager and
                   information                                applies the information to the configuration
                                                              database of the machine.
           14      [LB]                                       Registers the machine to a load balancing
                   Registering to load balancer group         node of a load balancer group.

           15      [Standard]                                 Updates the machine’s process completion
                   Updating configuration information         status, etc.



1.10.3. Activating Machine / Register Master Machine (Physical
           Machine)
           Activates a managed machine without customizing.
           You need to configure the settings for the machine to register, such as an IP address,
           same as the Host Setting.


           The following table shows the steps of activating a machine as a master machine,
           specifying the machine information. This is an action to activate a managed machine
           without distributing software.


           The following operations are the targets of this operation:
            Operations view - Action menu - Register Master Machine
            ssc assign machine


           Order   Step                                       Detail

           1       [Standard]                                 Checks that a specified machine is not
                   Checking that a specified machine is       running in a group.
                   running
           2       [Standard]                                 Acquires a group of a target of the operation
                   Acquiring group information                from specified groups (groups, models)

           3       [Standard]                                 Checks the following points with the
                   Checking status of machine                 specified machine:
                                                              ▪ The machine is managed in
                                                              SystemProvisioning.
                                                              ▪ The type of the specified machine and
                                                              that of a group (model) is the same.




Part I SigmaSystemCenter Functions Reference
                                                                                                        83
1 Functions of SigmaSystemCenter


           Order   Step                                        Detail

           4       [Standard]                                  When the specified machine is a virtual
                   Checking master machine registration of     machine server, checks the following
                   VM server group                             points:
                                                               ▪ The machine is registered in a manager.
                                                               ▪ Manager information and datacenter
                                                               information that are related to the target
                                                               virtual machine server match the
                                                               information that is set in a group.
           5       [Standard]                                  Updates the status of the machine to
                   Updating configuration information          In-process.

           6       [Standard]                                  Allocates a specified Host Setting such as a
                   Allocating Host Setting                     host name and IP address, defined in a
                                                               target group to a machine.
           7       [Storage]                                   Connects a disk volume defined to the Host
                   Connecting to storage (disk volume)         Setting, allocated in the step 1, to the
                                                               machine.
           8       [VLAN]                                      Registers a switch port connected to the
                   VLAN settings                               machine to a VLAN.

           9       [Standard]                                  Starts the machine.
                   Starting machine
           10      [Management NW]                             Registers the machine to the monitored
                   Registering to NEC ESMPRO Manager           target of NEC ESMPRO Manager.

           11      [Standard]                                  Collects the hardware information of the
                   Collecting and updating machine             machine from NEC ESMPRO Manager and
                   information                                 applies the information to the configuration
                                                               database of the machine.
           12      [LB]                                        Registers the machine to a load balancing
                   Registering to load balancer group          node of a load balancer group.

           13      [Standard]                                  Updates the machine’s process completion
                   Updating configuration information          status, etc.




                                                             SigmaSystemCenter 2.1 Reference Guide
84
                                                                     Changes in Machine Configuration




1.10.4. Deleting Machine / Release Resource (Physical Machine)
           Moves an active machine to a pool and deletes the machine from active machines.


            Returns to a group pool
             The following operations are the targets of this operation:
               •   Operations view - Action menu - Release Resource - Group Pool
               •   pvmutl delete
               •   ssc release machine


            Returns to the shared pool
             The following operations are the targets of this operation:
               •   Operations view - Action menu - Release Resource - Shared Pool
               •   ssc release machine


           Order   Step                                         Detail

           1       [Standard]                                   Checks the following points with the
                   Checking status of machine                   specified machine:
                                                                ▪ The machine is running in a group.
                                                                ▪ The status of the machine is not
                                                                In-process.
                                                                ▪ The machine is managed in
                                                                SystemProvisioning.
           2       [Standard]                                   Updates the status of the machine to
                   Updating configuration information           In-process.

           3       [LB]                                         Releases a machine from a load balancing
                   Releasing from load balancer group           node of a load balancer group.

           4       [Management NW]                              Deletes the machine from the monitored
                   Deleting from NEC ESMPRO Manager             object of NEC ESMPRO Manager.

           5       [Standard]                                   Distributes standby distribution software
                   Distributing standby distribution software   registered to the machine, its Host Setting,
                                                                its model, and its group.
           6       [Standard]                                   Shuts down the machine.
                   Shutting down machine                        If the machine is a virtual machine server,
                                                                shuts down a machine if storage setting is
                                                                configured to the virtual machine server.
           7       [VLAN]                                       Deletes a switch port connected to the
                   VLAN settings                                machine from a VLAN.

           8       [Storage]                                    Disconnects the connection between a disk
                   Disconnecting storage (disk volume)          volume and the machine.

           9       [Standard]                                   Distributes distribution software registered
                   Distributing standby after shutdown          for "Standby / after shutdown" in the
                   distribution software                        machine, its Host Setting, its model, and its
                                                                group.


Part I SigmaSystemCenter Functions Reference
                                                                                                          85
1 Functions of SigmaSystemCenter


           Order   Step                                          Detail

           10      [Standard]                                    Sets the Host Setting used by the machine
                   Releasing Host Setting                        to unused.

           11      [Standard]                                    Updates the machine’s process completion
                   Updating configuration information            status, etc.




1.10.5. Deleting Machine / Scale In (Physical Machine)
           Selects a running machine automatically and moves the machine to a pool to delete the
           machine from running machines.


           The following operations are the targets of this operation:
            Operations view - Scale In
            pvmutl delete
            ssc release machine
            Action of a policy Action for Group / Delete a Machine From the Group to Pool


           Note: Scale In from the Web Console or Scale In by the ssc command without
           specifying a host cannot be executed if the number of powered ON machines is less
           than the minimum number of powered ON machines. (The number of powered ON
           machines must be one or over.) Scale In by pvmutl delete command can be executed
           without verifying whether machines are powered ON or not.


           Order   Step                                          Detail

           1       [Standard]                                    Creates a list of machines running in the
                   Creating list                                 specified group.

           2       Repeats the following process to search for a machine that can be released its allocation
                   and belongs to multiple groups.
                   If a target machine is found, then executes the step 4. If not, executes the step 3.
                   [Standard]                                    Selects a machine that belongs to multiple
                   Selecting machine                             groups in the list created in the step 1.

                   [Standard]                                    Checks the status of the selected machine
                   Checking status of machine                    ▪ When the machine is returned to a group
                                                                 pool
                                                                 If the status is not In-process or
                                                                 Maintenance, the machine becomes a
                                                                 target of the operation.
                                                                 ▪ When the machine is returned to the
                                                                 shared pool
                                                                 If the status is not In-process, the machine
                                                                 becomes a target of the operation.
           3       Repeats the following process to search for a machine that can be released its allocation
                   and belongs to only one group.
                   If a target machine is found, then executes the step 4. If not, the Job ends with an error.


                                                             SigmaSystemCenter 2.1 Reference Guide
86
                                                                     Changes in Machine Configuration


           Order   Step                                         Detail

                   [Standard]                                   Selects a machine that belongs to only one
                   Selecting machine                            group in the list created in the step 1.

                   [Standard]                                   Checks the status of the selected machine
                   Checking status of machine                   ▪ When the machine is returned to a group
                                                                pool
                                                                If the status is not In-process or
                                                                Maintenance, the machine becomes a
                                                                target of the operation.
                                                                ▪ When the machine is returned to the
                                                                shared pool
                                                                If the status is not In-process, the machine
                                                                becomes a target of the operation.
           4       [Standard]                                   Checks the following points with the
                   Checking status of machine                   selected machine:
                                                                ▪ The machine is managed in
                                                                SystemProvisioning.
                                                                ▪ The machine is running in a group.
           5       [Standard]                                   Updates the status of the machine to
                   Updating configuration information           In-process.

           6       [LB]                                         Releases a machine from a load balancing
                   Releasing from load balancer group           node of a load balancer group.

           7       [Management NW]                              Deletes the machine from the monitored
                   Deleting from NEC ESMPRO Manager             object of NEC ESMPRO Manager.

           8       [Standard]                                   Distributes standby distribution software
                   Distributing standby distribution software   registered to the machine, its Host Setting,
                                                                its model, and its group.
           9       [Standard]                                   Shuts down the machine.
                   Shutting down machine                        If the machine is a virtual machine server,
                                                                shuts down a machine if storage setting is
                                                                configured to the virtual machine server.
           10      [VLAN]                                       Deletes a switch port connected to the
                   VLAN settings                                machine from a VLAN.

           11      [Storage]                                    Disconnects the connection between a disk
                   Disconnecting storage (disk volume)          volume and the machine.

           12      [Standard]                                   Distributes distribution software registered
                   Distributing standby after shutdown          for "Standby / after shutdown" in the
                   distribution software                        machine, its Host Setting, its model, and its
                                                                group.
           13      [Standard]                                   Sets the Host Setting used by the machine
                   Releasing Host Setting                       to unused.

           14      [Standard]                                   Updates the machine’s process completion
                   Updating configuration information           status, etc.




Part I SigmaSystemCenter Functions Reference
                                                                                                          87
1 Functions of SigmaSystemCenter




1.10.6. Replacing Machine (Physical Machine)
           Replaces an active machine with a pool machine.
           The new machine uses the same Host Setting, such as a host name and IP address,
           as that of an active machine.


           Note: SystemProvisioning does not support this operation for a virtual machine server.


            When a destination machine of Replacing machine is specified:


               The following operations are the targets of this operation:


               •   Operation view - Action menu - Replace Machine - Select a machine manually


               Order    Step                                   Detail

               1        [Standard]                             Checks that the Model Type of the group
                        Checking group                         where the target machine is running is not
                                                               VM.
               2        [Standard]                             Checks if a specified machine exists in a
                        Checking existence of machine          group.

               3        [Standard]                             Checks the following points with the
                        Checking status of machine             specified machine.
                                                               ▪ The machine is not running in any other
                                                               groups.
                                                               ▪ Managed machine
                                                               ▪ The status of the machine is not
                                                               In-process.
               4        [Standard]                             Updates the status of the machine to
                        Updating configuration information     In-process.

               5        [LB]                                   Releasing an original machine from a load
                        Releasing from load balancer group     balancing node of a load balancer group.

               6        [Management NW]                        Deletes the original machine from the
                        Deleting from NEC ESMPRO               monitored object of NEC ESMPRO
                        Manager                                Manager.

               7        [Standard]                             Distributes standby distribution software
                        Distributing standby distribution      registered to the original machine, its Host
                        software                               Setting, its model, and its group.

               8        [Standard]                             Shuts down the original machine.
                        Shutting down original machine         If the shutdown of the original machine
                                                               fails, Power OFF will be executed on the
                                                               original machine.
               9        [VLAN]                                 Deletes a switch port connected to the
                        VLAN settings                          original machine from a VLAN.




                                                             SigmaSystemCenter 2.1 Reference Guide
88
                                                                   Changes in Machine Configuration


               10       [Storage]                             Disconnects the connection between a disk
                        Disconnecting storage (disk volume)   volume and the original machine.

               11       [Standard]                            Distributes distribution software registered
                        Distributing standby after shutdown   for "Standby / after shutdown" in the
                        distribution software                 machine, its Host Setting, its model, and its
                                                              group.
               12       [Standard]                            Replaces the original machine with a new
                        Replacing machine                     machine.

               13       [Storage]                             Connects the disk volume to a new
                        Connecting storage (disk volume)      machine.

               14       [VLAN]                                Registers a switch port connected to the
                        VLAN settings                         new machine to a VLAN.

               15       [Standard]                            Distributes operating distribution software
                        Distributing operating distribution   registered to the new machine, its Host
                        software                              Setting, its model, and its group.

               16       [Standard]                            Starts the new machine.
                        Starting new machine
               17       [Management NW]                       Registers the new machine to the
                        Registering to NEC ESMPRO             monitored object of NEC ESMPRO
                        Manager                               Manager.

               18       [Standard]                            Collects the hardware information of the
                        Collecting and updating machine       new machine from NEC ESMPRO
                        information                           Manager and applies the information in the
                                                              configuration database of the machine.
               19       [LB]                                  Registers the new machine to a load
                        Registering to load balancer group    balancing node of a load balancer group.

               20       [Standard]                            Updates the power status of the new
                        Updating configuration information    machine, such as process completion
                                                              status.


            When a Replacing machine is not specified:


               The following operations are the targets of this operation:
               •    Operations view - Action menu - Replace Machine - Select a machine
                    automatically
               •    pvmutl replace
               •    Action of a policy Action for Machine / Replace Machine


               Order    Step                                  Detail

               1        [Standard]                            Checks that the Model Type of the group
                        Checking group                        where the target machine is running is not
                                                              VM.
               2        [Standard]                            Checks if a specified machine exists in a
                        Checking existence of machine         group.

               3        [Standard]                            Creates a list of machines that exist in a
                        Creating list                         pool of the group where the target machine
                                                              is running.

Part I SigmaSystemCenter Functions Reference
                                                                                                         89
1 Functions of SigmaSystemCenter


               Order   Step                                     Detail

               4       Repeats the following process to search for a machine that can be replaced and
                       belongs to only one group.
                       If a target machine is found, then executes the step 8. If not, executes the step 5.
                       [Standard]                               Selects a machine that belongs to only one
                       Selecting machine                        group in the list created in the step 3.

                       [Standard]                               Checks the status of the selected machine.
                       Checking status of machine               If the status is not In-process, Error, or
                                                                Maintenance, the machine becomes a
                                                                target of the operation.
               5       Repeats the following process to search for a machine that can be replaced and
                       belongs to multiple groups.
                       If a target machine is found, then executes the step 8. If not, executes the step 6.
                       [Standard]                               Selects a machine that belongs to multiple
                       Selecting machine                        groups in the list created in the step 3.

                       [Standard]                               Checks the status of the selected machine.
                       Checking status of machine               If the status is not In-process, Error, or
                                                                Maintenance, the machine becomes a
                                                                target of the operation.
               6       [Standard]                               ▪ If When the group pool doesn’t have an
                       Searching for shared pool machine        available machine, use a machine in the
                                                                shared pool is selected to a group where
                                                                the target machine is running:
                                                                Creates a list of machines that exist in the
                                                                shared pool.
                                                                ▪ If When the group pool doesn’t have an
                                                                available machine, use a machine in the
                                                                shared pool is not selected to a group
                                                                where the target machine is running:
                                                                The Job ends with an error.
               7       Repeats the following process to search for a machine that exists in the shared pool.
                       If a target machine is found, then executes the step 8. If not, the Job ends with an
                       error.
                       [Standard]                               Checks the following points with the
                       Checking status of machine               selected machine:
                                                                ▪ The status of the machine is not
                                                                In-process, Error, Maintenance, or
                                                                Discovered.
                                                                ▪ A model name of the selected machine is
                                                                the same as that of an already running
                                                                machine.
                                                                ▪ DPM that manages the machine is the
                                                                same as that manages software which is
                                                                set in a group, etc.
               8       [Standard]                               Updates the status of the machine to
                       Updating configuration information       In-process.

               9       [LB]                                     Releasing an original machine from a load
                       Releasing from load balancer group       balancing node of a load balancer group.

               10      [Management NW]                          Deletes the original machine from the
                       Deleting from NEC ESMPRO                 monitored object of NEC ESMPRO
                       Manager                                  Manager.

                                                             SigmaSystemCenter 2.1 Reference Guide
90
                                                                 Changes in Machine Configuration


               Order   Step                                  Detail

               11      [Standard]                            Distributes standby distribution software
                       Distributing standby distribution     registered to the original machine, its Host
                       software                              Setting, its model, and its group.

               12      [Standard]                            Shuts down the original machine.
                       Shutting down original machine        If the shutdown of the original machine
                                                             fails, Power OFF will be executed on the
                                                             original machine.
               13      [VLAN]                                Deletes a switch port connected to the
                       VLAN settings                         original machine from a VLAN.

               14      [Storage]                             Disconnects the connection between a disk
                       Disconnecting storage (disk volume)   volume and the original machine.

               15      [Standard]                            Distributes distribution software registered
                       Distributing standby after shutdown   for "Standby / after shutdown" in the
                       distribution software                 machine, its Host Setting, its model, and its
                                                             group.
               16      [Standard]                            Replaces the original machine with a new
                       Replacing machine                     machine.

               17      [Storage]                             Connects the disk volume to a new
                       Connecting storage (disk volume)      machine.

               18      [VLAN]                                Registers a switch port connected to the
                       VLAN settings                         new machine to a VLAN.

               19      [Standard]                            Distributes operating distribution software
                       Distributing operating distribution   registered to the new machine, its Host
                       software                              Setting, its model, and its group.

               20      [Standard]                            Starts the new machine.
                       Starting new machine
               21      [Management NW]                       Registers the new machine to the
                       Registering to NEC ESMPRO             monitored object of NEC ESMPRO
                       Manager                               Manager.

               22      [Standard]                            Collects the hardware information of the
                       Collecting and updating machine       new machine from NEC ESMPRO
                       information                           Manager and applies the information in the
                                                             configuration database of the machine.
               23      [LB]                                  Registers the new machine to a load
                       Registering to load balancer group    balancing node of a load balancer group.

               24      [Standard]                            Updates the power status of the new
                       Updating configuration information    machine, such as process completion
                                                             status.




Part I SigmaSystemCenter Functions Reference
                                                                                                        91
1 Functions of SigmaSystemCenter




1.10.7. Changing Machine Usage (Physical Machine)
           Moves an active machine to other group to change the usage of the machine.
           There are two methods to change machine usage and each of the methods has the
           following features:


            When a machine is specified:
               Moves a specified machine to a specified new group.
               The following operations are the targets of this operation:
               •   Operations view - Action menu - Change Machine Usage
               •   pvmutl move


               Note: You cannot change usage of a virtual machine server operating in a group
               of VM Server model type to a group of Physical model type.
               In addition, if you are using ESX version 3.0.x, a virtual machine server to change
               usage needs to be powered OFF when you execute the operation.


               Order   Step                                         Detail

               1       [Standard]                                   Creates a list of destination groups. This
                       Creating list                                list is created from a group with higher
                                                                    priority.
               2       Repeats the following process to search for a group to which the system can change
                       usage.
                       If a target group is found, then executes the step 3. If not, the Job ends with an error.
                       [Standard]                                   Checks if the specified machine exists in
                       Checking existence of machine                the destination group,

                       [Standard]                                   Checks if there exists Host Setting that
                       Searching for Host Setting                   can be used to the destination group.

               3       [Standard]                                   Updates the status of the machine to
                       Updating configuration information           In-process.

               4       [LB]                                         Releases the machine from a load
                       Releasing from load balancer group           balancing node of a load balancer
                                                                    group.
               5       [Management NW]                              Deletes the machine from the monitored
                       Deleting from NEC ESMPRO Manager             object of NEC ESMPRO Manager.

               6       [Standard]                                   Distributes standby distribution software
                       Distributing standby distribution software   registered to the machine in the original
                                                                    group, its Host Setting, its model, and its
                                                                    group.
               7       [Standard]                                   Shuts down the machine.
                       Shutting down machine
               8       [VLAN]                                       Deletes a switch port connected to the
                       VLAN settings                                machine from a VLAN.


                                                              SigmaSystemCenter 2.1 Reference Guide
92
                                                                  Changes in Machine Configuration


               Order    Step                                    Detail

               9        [Storage]                               Disconnects a disk volume from the
                        Disconnecting storage (disk volume)     machine.

               10       [Standard]                              Distributes distribution software
                        Distributing standby after shutdown     registered for "Standby / after shutdown"
                        distribution software                   in the machine, its Host Setting, its
                                                                model, and its group.
               11       [Standard]                              Sets the Host Setting used by the
                        Releasing Host Setting                  machine to unused.

               12       [Standard]                              Allocates an unused Host Setting, such
                        Allocating Host Setting                 as a host name and IP address, defined
                                                                to the new group to the machine.
               13       [Storage]                               Connects a disk volume defined to the
                        Connecting to storage (disk volume)     Host Setting allocated in the Order 12 to
                                                                the machine.
               14       [VLAN]                                  Registers a switch port connected to the
                        VLAN settings                           machine in the new group to a VLAN.

               15       [Standard]                              Distributes operating distribution
                        Distributing operating distribution     software the machine in the new group,
                        software                                its Host Setting, its model, and its group.

               16       [Standard]                              Starts the machine in the new group.
                        Starting machine
               17       [Management NW]                         Registers the machine to the monitored
                        Registering to NEC ESMPRO Manager       object of NEC ESMPRO Manager.

               18       [Standard]                              Collects the hardware information of the
                        Collecting and updating machine         machine from NEC ESMPRO Manager
                        information                             and applies the information to the
                                                                configuration database of the machine.
               19       [LB]                                    Registers the machine to a load
                        Registering to load balancer group      balancing node of a load balancer
                                                                group.
               20       [Standard]                              Updates the power status of the new
                        Updating configuration information      machine, such as process completion
                                                                status.


            When a machine is not specified:
               Searches for a machine and moves the machine to the destination group to
               change usage of the machine.
               The targets of the search are groups that have a pool machine that is running in
               the original group.


               The following operation is the targets of this operation:
               •    pvmutl move


               Order    Step                                    Detail

               1        [Standard]                              Creates a list of pool machines in a
                        Creating list                           destination group.

Part I SigmaSystemCenter Functions Reference
                                                                                                        93
1 Functions of SigmaSystemCenter


               Order   Step                                         Detail

               2       [Standard]                                   Creates a list of running machines in a
                       Creating list                                source group.

               3       Repeats the following process to search for a machine that can be changed its
                       usage.
                       If a target machine is found, then executes the step 4. If not, the Job ends with an
                       error.
                       [Standard]                                   Extracts the same machine in the list
                       Selecting machine                            created in the step 2 as those in the list
                                                                    created in the step 1.
                       [Standard]                                   Checks if there is Host Setting that can
                       Searching for Host Setting                   be used to the destination group.

                       [Standard]                                   Checks the status of the extracted
                       Checking status of machine                   machine.
                                                                    If the status of the machine is not
                                                                    In-process, Error, or Maintenance, the
                                                                    machine becomes a target of the
                                                                    operation.
               4       [Standard]                                   Updates the status of the machine to
                       Updating configuration information           In-process.

               5       [LB]                                         Releases the machine from a load
                       Releasing from load balancer group           balancing node of a load balancer
                                                                    group.
               6       [Management NW]                              Deletes the machine from the monitored
                       Deleting from NEC ESMPRO Manager             object of NEC ESMPRO Manager.

               7       [Standard]                                   Distributes standby distribution software
                       Distributing standby distribution software   registered to the machine in the original
                                                                    group, its Host Setting, its model, and its
                                                                    group.
               8       [Standard]                                   Shuts down the machine.
                       Shutting down machine
               9       [VLAN]                                       Deletes a switch port connected to the
                       VLAN settings                                machine from a VLAN.

               10      [Storage]                                    Disconnects a disk volume from the
                       Disconnecting storage (disk volume)          machine.

               11      [Standard]                                   Distributes distribution software
                       Distributing standby after shutdown          registered for "Standby / after shutdown"
                       distribution software                        in the machine, its Host Setting, its
                                                                    model, and its group.
               12      [Standard]                                   Sets the Host Setting used by the
                       Releasing Host Setting                       machine to unused.

               13      [Standard]                                   Allocates an unused Host Setting, such
                       Allocating Host Setting                      as a host name and IP address, defined
                                                                    to the new group to the machine.
               14      [Storage]                                    Connects a disk volume defined to the
                       Connecting to storage (disk volume)          Host Setting allocated in the Order 12 to
                                                                    the machine.
               15      [VLAN]                                       Registers a switch port connected to the
                       VLAN settings                                machine in the new group to a VLAN.


                                                             SigmaSystemCenter 2.1 Reference Guide
94
                                                               Changes in Machine Configuration


               Order   Step                                  Detail

               16      [Standard]                            Distributes operating distribution
                       Distributing operating distribution   software the machine in the new group,
                       software                              its Host Setting, its model, and its group.

               17      [Standard]                            Starts the machine in the new group.
                       Starting machine
               18      [Management NW]                       Registers the machine to the monitored
                       Registering to NEC ESMPRO Manager     object of NEC ESMPRO Manager.

               19      [Standard]                            Collects the hardware information of the
                       Collecting and updating machine       machine from NEC ESMPRO Manager
                       information                           and applies the information to the
                                                             configuration database of the machine.
               20      [LB]                                  Registers the machine to a load
                       Registering to load balancer group    balancing node of a load balancer
                                                             group.
               21      [Standard]                            Updates the power status of the new
                       Updating configuration information    machine, such as process completion
                                                             status.




Part I SigmaSystemCenter Functions Reference
                                                                                                     95
1 Functions of SigmaSystemCenter




1.10.8. Activating Machine / Create and Assign Machine (Virtual
           Machine)
           Creates a virtual machine. The created machine is activated in a group.
           Select the Register VM with DPM when VM is created check box on the Model Property
           Setting of the group. If you select this check box, the created virtual machine is
           registered to DPM automatically. If the system fails to register the machine to DPM, the
           process is aborted. In this case, perform the following operations depending on the
           template that you use to create the virtual machine:
            If you use a Full Clone template:
             Creating a virtual machine has been completed. Delete the virtual machine from its
             group once, register the virtual machine to DPM, and then, execute Register
             Master Machine.
            If you use a HW Profile Clone, Differential Clone, or Disk Clone template:
             Delete the virtual machine from its group once, execute Delete VM in the Virtual
             view, and then, execute Create and Assign Machine again.


           If the Register VM with DPM when VM is created check box is not selected, even if a
           virtual machine is created, distributing operating distribution software is not executed.
           In that case, the created virtual machine becomes the following conditions depending
           on the template that you use to create the virtual machine:
            If you use a Full Clone template:
             The virtual machine is activated without software distributed. To distribute software
             to a machine in this condition, after registering the virtual machine to DPM,
             execute distributing operations, such as redistribution.
            If you use a HW Profile Clone template:
             Creating a virtual machine fails.
            If you use a Differential Clone template for creating a template in Standalone ESXi
             or Hyper-V:
             Creating a virtual machine fails,
            If you use a Disk Clone template:
             Creating a virtual machine fails.


           If the The VM Server is selected automatically check box is selected on the Create and
           Assign Machine window, the destination virtual machine server where the virtual
           machine is to be created will be selected automatically.
           For information on auto selection, see Subsection 2.11.4, “VM Optimized Creation”. For
           information on criteria for selection of virtual machine servers, see Subsection 2.11.5,
           “Conditions for VM Optimized Creation”.




                                                          SigmaSystemCenter 2.1 Reference Guide
96
                                                                      Changes in Machine Configuration



           The following operations are the targets of this operation:


            Operations view - Action menu - Create and Assign Machine
            Action of a policy Action for Group / Create / Add a Machine to the Group
            pvmutl vmadd


           Order   Step                                           Detail

           1       [Standard]                                     Specifies a target group in the specified
                   Acquiring Host Setting                         groups (groups and models).


           2       [Standard]                                     Creates a list of groups (models) where a
                   Creating list                                  virtual machine can be created and
                                                                  activated.
           3       Repeats the following process to search for Host Setting and group to which a virtual
                   machine can be created and activated.
                   If a target is found, then executes the step 4. If not, the Job ends with an error.
                   [Standard]                                     Checks if the specified Host Setting is
                   Searching for Host Setting                     available.

                   [Standard]                                     Checks if a template is configured to a
                   Checking setting of template                   group or model.

           4       [Standard]                                     Updates the status of the machine to
                   Updating configuration information             In-process.

           5       [Standard]                                     Allocates a specified Host Setting, such as
                   Allocating Host Setting                        a host name and IP address, defined to a
                                                                  target group.
           6       [Standard]                                     Connects to virtual switches based on the
                   Allocating network settings                    network settings specified in the model.

           7       [Standard]                                     Creates a virtual machine from a template
                   Creating virtual machine                       defined to the group.

           8       [Standard]                                     Collects hardware information of a
                   Collecting and updating machine                machine from vCenter Server, XenCenter,
                   information                                    ESXi, or Hyper-V and collects information
                                                                  in the configuration database of the
                                                                  machine.
           9       [Standard]                                     Registers the machine to DPM. If it fails,
                   Registering to DPM                             the process is aborted with the machine
                                                                  status, "Error (Abort)."
           10      [Standard]                                     Distributes operating distribution software
                   Distributing operating distribution software   registered to the machine, its Host Setting,
                                                                  its model, and its group.
           11      [Standard]                                     Starts the machine.
                   Starting machine
           12      [LB]                                           Registers the machine to a load balancing
                   Registering to load balancer group             node of a load balancer group.

           13      [Standard]                                     Updates the status of the machine, such as
                   Updating configuration information             process completion status.

Part I SigmaSystemCenter Functions Reference
                                                                                                               97
1 Functions of SigmaSystemCenter




1.10.9. Activating Machine / Allocate Machine (Virtual Machine)
           Activates a machine in the operation ready state in a group.
           If the Register VM with DPM when VM is created check box on the Model Property
           Setting of the group is not selected, even if you execute Allocate Machine, distributing
           operating distribution software is not executed. The created machine is activated
           without software distributed. To distribute software to a machine in this condition, after
           registering the virtual machine to DPM, execute distributing operations, such as
           redistribution.


           Note:
           ▪ If the Guest OS of a virtual machine is Windows Vista, customizing during Allocate
           Machine or Scale Out is limited to once. To activate a virtual machine to which you
           have executed Allocate Machine or Scale Out in a group again, use Register Master
           Machine.
           ▪ If a type of a template registered in the Software setting of a group or model is Disk
           Clone or Differential Clone for creating a template in Standalone ESXi, Hyper-V or Xen,
           you cannot execute Allocate Machine.
           ▪ If the type of the template that is registered on the Software setting of Group or Model
           is HW Profile Clone (which was created in Standalone ESXi or Hyper-V), Forced
           execution of a reboot is performed before execution must be selected as the execution
           condition for the list scenario. For the details, see Subsection 2.1.3, "Creating a
           Scenario File" in DeploymentManager Basic User’s Guide.
           Under the condition that Allocate Machine is executed on virtual machines in power on
           status, if the host setting is different from that of the previous virtual machine, Allocate
           Machine will fail. In that case, turn off the virtual machine's power or execute Allocate
           Machine on the same host setting.


           The following operations are the targets of this operation:
            Operations view - Action menu - Allocate Machine - Select a machine manually -
             Select a machine from group pool
            Operations view - Action menu - Allocate Machine - Select a machine manually -
             Select a machine from shared pool
            pvmutl add
            pvmutl addspecname
            ssc assign machine




                                                            SigmaSystemCenter 2.1 Reference Guide
98
                                                                   Changes in Machine Configuration



           Order             Step                                  Detail

           1                 [Standard]                            Checks that the specified machine is
                             Checking that specified machine is    not running in other groups.
                             running
           2                 [Standard]                            ▪ When Host Setting is specified
                             Searching for Host Setting            Checks if specified Host Setting is
                                                                   available.
                                                                   ▪ When Host Setting is not specified
                                                                   Checks if there exists available Host
                                                                   Setting.
           3                 [Standard]                            Checks that the status of the specified
                             Checking status of machine            machine is not In-process.

           4                 [Standard]                            Updates the status of the machine to
                             Updating configuration information    In-process.

           5                 [Standard]                            Allocates a specified Host Setting such
                             Allocating Host Setting               as a host name and IP address,
                                                                   defined to a target group to a machine.
           6                 [Standard]                            Connects to virtual switches based on
                             Allocating network settings           the network settings specified in the
                                                                   model.
           7                 [Standard]                            Customizes the host name and IP
           (Only for a       Customizing machine                   address of the machine. If the power
           virtual machine                                         status of the machine is ON, the
           on ESX or ESXi                                          machine is shut down once, and then,
           managed in                                              customized.
           vCenter Server)
           8                 [Standard]                            Registers the added machine to DPM if
                             Registering to DPM                    the settings for machine registration to
                                                                   DPM are configured. If it fails, the
                                                                   process is aborted with the machine
                                                                   status, "Error (Abort)."
           9                 [Standard]                            Distributes operating distribution
                             Distributing operating distribution   software registered to the machine, its
                             software                              Host Setting, its model, and its group.

           10                [Standard]                            Starts the machine.
                             Starting machine
           11                [LB]                                  Registers the machine to a load
                             Registering to load balancer group    balancing node of a load balancer
                                                                   group.




Part I SigmaSystemCenter Functions Reference
                                                                                                           99
1 Functions of SigmaSystemCenter




1.10.10. Activating Machine / Scale Out (Virtual Machine)
           Selects a virtual machine according to the Machine Pool Setting of Group Property
           Setting, executes Allocate Machine to activate the virtual machine in a group,


           If the Register VM with DPM when VM is created check box on the Model Property
           Setting of the group is not selected, even if you execute Allocate Machine, distributing
           operating distribution software is not executed. The created machine is activated
           without software distributed. To distribute software to a machine in this condition, after
           registering the virtual machine to DPM, execute distributing operations, such as
           redistribution.


           Note:
           ▪ If the Guest OS of a virtual machine is Windows Vista, customizing during Allocate
           Machine or Scale Out is limited to once. To activate a virtual machine to which you
           have executed Allocate Machine or Scale Out in a group again, use Register Master
           Machine.
           ▪ If a type of a template registered in the Software setting of a group or model is Disk
           Clone or Differential Clone for creating a template in Standalone ESXi, Hyper-V or Xen,
           you cannot execute Allocate Machine.
           ▪ If the type of the template that is registered on the Software setting of Group or Model
           is HW Profile Clone (which was created in Standalone ESXi or Hyper-V), Forced
           execution of a reboot is performed before execution must be selected as the execution
           condition for the list scenario. For the details, see Subsection 2.1.3, "Creating a
           Scenario File" in DeploymentManager Basic User’s Guide.
           Under the condition that Allocate Machine is executed on virtual machines in power on
           status, if the host setting is different from that of the previous virtual machine, Allocate
           Machine will fail. In that case, turn off the virtual machine's power or execute Allocate
           Machine on the same host setting.


           The following operations are the targets of this operation:
            Operations view - Scale Out
            Operations view - Action menu - Allocate Machine - Select a machine
             automatically
            pvmutl add
            pvmutl addspecname
            ssc assign machine
            Action of a policy Action for Group / Add a Machine to the Group




                                                            SigmaSystemCenter 2.1 Reference Guide
100
                                                                   Changes in Machine Configuration



           Order          Step                                     Detail

           1              [Standard]                               Creates a list of machines that exist in
                          Creating list                            a specified group pool.

           2              Repeats the following process to search for a machine that can be activated in a
                          group and belongs to only one group pool.
                          If a target machine is found, then executes the step 6. If not, executes the step
                          3.
                          [Standard]                               Selects a machine that belongs to only
                          Selecting machine                        one group pool in the list created in the
                                                                   step 1.
                          [Standard]                               ▪ When Host Setting is specified
                          Searching for Host Setting               Checks if specified Host Setting is
                                                                   available.
                                                                   ▪ When Host Setting is not specified
                                                                   Checks if there exists available Host
                                                                   Setting.
                          [Standard]                               Checks the status of the selected
                          Checking status of machine               machine.
                                                                   If the status is not In-process, Error, or
                                                                   Maintenance, the machine becomes a
                                                                   target of the operation.
           3              Repeats the following process to search for a machine that can be activated in a
                          group and belongs to multiple group pool.
                          If a target machine is found, then executes the step 6. If not, executes the step
                          4.
                          [Standard]                               Selects a machine that belongs to
                          Selecting machine                        multiple group pools in the list created
                                                                   in the step 1.
                          [Standard]                               ▪ When Host Setting is specified
                          Searching for Host Setting               Checks if specified Host Setting is
                                                                   available.
                                                                   ▪ When Host Setting is not specified
                                                                   Checks if there exists available Host
                                                                   Setting.
                          [Standard]                               Checks the status of the selected
                          Checking status of machine               machine.
                                                                   If the status is not In-process, Error, or
                                                                   Maintenance, the machine becomes a
                                                                   target of the operation.
           4              [Standard]                               Creates a list of groups to which When
                          Creating list                            the group pool doesn’t have an
                                                                   available machine, use a machine in
                                                                   the shared pool is configured to its
                                                                   Group Property Setting and in which
                                                                   available Host Setting exists. This list
                                                                   is created from a group with higher
                                                                   priority.
                                                                   In addition, a list of machines in the
                                                                   shared pool is also created.




Part I SigmaSystemCenter Functions Reference
                                                                                                         101
1 Functions of SigmaSystemCenter


           Order             Step                                        Detail

           5                 Repeats the following process to search for a machine that can be activated in a
                             group and belongs to the shared pool.
                             If a target machine is found, then executes the step 6. If not, the Job ends with
                             an error.
                             [Standard]                                  Selects a group and machine from the
                             Checking status of machine                  list created in the step 4 and checks
                                                                         the following points:
                                                                         ▪ The status of the machine is not
                                                                         In-process, Error, Maintenance, or
                                                                         Discovered.
                                                                         ▪ A model name of the selected
                                                                         machine is the same as that of an
                                                                         already running machine.
                                                                         ▪ DPM that manages the machine is
                                                                         the same as that manages software
                                                                         which is set in a group, etc.
                                                                         ▪ The type of the machine and the type
                                                                         of the group (model) is the same.
           6                 [Standard]                                  Updates the status of the machine to
                             Updating configuration information          In-process.

           7                 [Standard]                                  Allocates a specified Host Setting such
                             Allocating Host Setting                     as a host name and IP address,
                                                                         defined in a target group to a machine.
           8                 [Standard]                                  Selects a virtual machine in a pool,
                             Allocating machine                          according to the Machine Pool Setting
                                                                         of Group Property Setting.
           9                 [Standard]                                  Customizes the host name and IP
           (Only for a       Customizing machine                         address of the machine. If the power
           virtual machine                                               status of the machine is ON, the
           on ESX or ESXi                                                machine is shut down once, and
           managed in                                                    customized.
           vCenter Server)
           10                [Standard]                                  Registers the added machine to DPM
                             Registering to DPM                          if the settings for machine registration
                                                                         to DPM are configured. If it fails, the
                                                                         process is aborted with the machine
                                                                         status, "Error (Abort)."
           11                [Standard]                                  Distributes operating distribution
                             Distributing operating distribution         software registered to the machine, its
                             software                                    Host Setting, and its group.

           12                [Standard]                                  Starts the machine.
                             Starting machine
           13                [LB]                                        Registers the machine to a load
                             Registering to load balancer group          balancing node of a load balancer
                                                                         group.




                                                                   SigmaSystemCenter 2.1 Reference Guide
102
                                                                    Changes in Machine Configuration




1.10.11. Activating Machine / Register Master Machine (Virtual
           Machine)
           Activates a managed virtual machine without customizing.
           You need to configure the settings for the virtual machine to register, such as an IP
           address, same as the Host Setting.


           The following table shows the steps of activating a machine as a master machine,
           specifying the machine information. This is an action to activate a managed virtual
           machine without distributing software.


           The following operations are the targets of this operation:
            Operations view - Action menu - Register Master Machine
            pvmutl vmadd
            ssc assign machine


           Order   Step                                         Detail

           1       [Standard]                                   Checks that the specified machine is not
                   Checking that specified machine is running   running in other groups.

           2       [Standard]                                   Acquires a target group in specified groups
                   Acquiring group information                  (groups and models).

           3       [Standard]                                   Checks the following points with the
                   Checking status of machine                   selected machine:
                                                                ▪ The machine is managed in
                                                                SystemProvisioning.
                                                                ▪ The type of the specified machine
                                                                matches the type of the group (model).
           4       [Standard]                                   Updates the status of the machine to
                   Updating configuration information           In-process.

           5       [Standard]                                   Allocates a specified Host Setting such as
                   Allocating Host Setting                      a host name and IP address, defined in a
                                                                target group to a machine.
           6       [Standard]                                   Configures Virtual NIC settings.
                   Network settings
           7       [Standard]                                   Registers the added machine to DPM if the
                   Registering to DPM                           settings for machine registration to DPM
                                                                are configured. If it fails, the process is
                                                                aborted with the machine status, "Error
                                                                (Abort)."
           8       [Standard]                                   Starts the machine.
                   Starting machine
           9       [LB]                                         Registers the machine to a load balancing
                   Registering to load balancer group           node of a load balancer group.



Part I SigmaSystemCenter Functions Reference
                                                                                                         103
1 Functions of SigmaSystemCenter


1.10.12. Deleting Machine / Release Resource (Virtual Machine)
           Deletes an active machine from its group


            To return the machine to a group pool:
             The following operations are the targets of this operation:
               •   Operations view - Action menu - Release Resource - Group Pool
               •   pvmutl vmdelete
               •   ssc release machine


            To return the machine to the shared pool:
             The following operations are the targets of this operation:
               •   Operations view - Action menu - Release Resource - Shared Pool
               •   pvmutl vmdelete
               •   ssc release machine


           Order   Step                                            Detail

           1       [Standard]                                      Checks the following points with the
                   Checking that a specified machine is            specified machine:
                   running                                         ▪ The machine is running in a group.
                                                                   ▪ The status of the machine is not
                                                                   In-process.
                                                                   ▪ The machine is managed in
                                                                   SystemProvisioning.
           2       [Standard]                                      Updates the status of the machine to
                   Updating configuration information              In-process.

           3       [LB]                                            Deletes a virtual machine from a load
                   Deleting from load balancer group               balancing node of a load balancer group.

           4       [Standard]                                      Distributes standby distribution software
                   Distributing standby distribution software      registered to the machine, its Host Setting,
                                                                   and its group.
           5       [Standard]                                      If the settings for machine registration to
                   Deleting machine registration to DPM            DPM are configured to the group, the
                                                                   registration of the target machine is
                                                                   deleted.
                                                                   If the settings are not configured, this
                                                                   process is skipped and the process of
                                                                   updating configuration information is
                                                                   executed.
           6       [Standard]                                      Sets the Host Setting used by the machine
                   Releasing Host Setting                          to unused.

           7       [Standard]                                      Updates the status of the machine, such as
                   Updating configuration information              process completion status.




                                                                SigmaSystemCenter 2.1 Reference Guide
104
                                                                      Changes in Machine Configuration




1.10.13. Deleting Machine / Scale In (Virtual Machine)
           Selects a running machine automatically and moves the machine to a pool to delete the
           machine from running machines.


            To return the machine to a group pool:
             The following operations are the targets of this operation:
               •   Operations view - Scale In
               •   pvmutl delete
               •   ssc release machine


            To return the machine to the shared pool:
             The following operations are the targets of this operation:
               •   pvmutl vmdelete
               •   ssc release machine


           Order   Step                                          Detail

           1       [Standard]                                    Creates a list of machines running in the
                   Creating list                                 specified group.

           2       Repeats the following process to search for a machine that can be released its allocation
                   and belongs to multiple groups.
                   If a target machine is found, then executes the step 4. If not, executes the step 3.
                   [Standard]                                    Selects a machine that belongs to multiple
                   Selecting machine                             groups in the list created in the step 1.

                   [Standard]                                    Checks the status of the selected machine
                   Checking status of machine                    ▪ When the machine is returned to a group
                                                                 pool
                                                                 If the status is not In-process or
                                                                 Maintenance, the machine becomes a
                                                                 target of the operation.
                                                                 ▪ When the machine is returned to the
                                                                 shared pool
                                                                 If the status is not In-process, the machine
                                                                 becomes a target of the operation.
           3       Repeats the following process to search for a machine that can be released its allocation
                   and belongs to only one group.
                   If a target machine is found, then executes the step 4. If not, the Job ends with an error.
                   [Standard]                                    Selects a machine that belongs to only one
                   Selecting machine                             group in the list created in the step 1.




Part I SigmaSystemCenter Functions Reference
                                                                                                         105
1 Functions of SigmaSystemCenter


           Order   Step                                            Detail

                   [Standard]                                      Checks the status of the selected machine
                   Checking status of machine                      ▪ When the machine is returned to a group
                                                                   pool
                                                                   If the status is not In-process or
                                                                   Maintenance, the machine becomes a
                                                                   target of the operation.
                                                                   ▪ When the machine is returned to the
                                                                   shared pool
                                                                   If the status is not In-process, the machine
                                                                   becomes a target of the operation.
           4       [Standard]                                      Checks the following points with the
                   Checking status of machine                      selected machine:
                                                                   ▪ The machine is managed in
                                                                   SystemProvisioning.
                                                                   ▪ The machine is running in a group.
           5       [Standard]                                      Updates the status of the machine to
                   Updating configuration information              In-process.

           6       [LB]                                            Deletes the virtual machine from a load
                   Deleting from load balancer group               balancing node of a load balancer group.

           7       [Standard]                                      Distributes standby distribution software
                   Distributing standby distribution software      registered to the virtual machine, its Host
                                                                   Setting, and its group.
           8       [Standard]                                      If the settings for machine registration to
                   Deleting machine registration to DPM            DPM are configured to the group, the
                                                                   registration of the target machine is
                                                                   deleted.
                                                                   If the settings are not configured, this
                                                                   process is skipped and the next process of
                                                                   updating configuration information is
                                                                   executed.
           9       [Standard]                                      Sets the Host Setting used by the virtual
                   Releasing Host Setting                          machine to the unused state.

           10      [Standard]                                      Updates the status of the machine, such as
                   Updating configuration information              process completion status.




                                                                SigmaSystemCenter 2.1 Reference Guide
106
                                                                      Changes in Machine Configuration




1.10.14. Delete VM
           If you choose to delete a virtual machine, the virtual machine is deleted from a group
           and its registration to DPM is also deleted. After that, the virtual machine is deleted
           from its virtual machine server and get out of management of SystemProvisioning.


           The following operation is the target of this operation:
            pvmutl vmdelete


           Order    Step                                         Detail

           1        [Standard]                                   Creates a list of machines that exist in the
                    Creating list                                specified group.

           2        [Standard]                                   Checks the status of the selected machine.
                    Checking status of machine                   If the status is not In-process or
                                                                 Maintenance, the machine becomes a
                                                                 target of the operation.
           3        [Standard]                                   Creates a new list of machines of
                    Creating list                                candidates in the step 2.

           4        [Standard]                                   Selects a virtual machine server with the
                    Selecting virtual machine server             least capacity left or fewest virtual machine
                                                                 numbers.
           5        [Standard]                                   Determines a machine that exists on the
                    Selecting machine                            virtual machine server selected in the step
                                                                 4 as a target of deletion.
           6        [Standard]                                   Checks the determined machine for the
                    Checking status of machine                   following points:
                                                                 ▪ The machine is managed in
                                                                 SystemProvisioning.
                                                                 ▪ The machine is running in the specified
                                                                 group.
           7        [Standard]                                   Updates the status of the machine to
                    Updating configuration information           In-process.

           8        [LB]                                         Deletes the virtual machine from a load
                    Deleting from load balancer group            balancing node of a load balancer group.

           9        [Standard]                                   Distributes standby distribution software
                    Distributing standby distribution software   registered to the virtual machine, its Host
                                                                 Setting, and its group.
           10       [Standard]                                   Shuts down the virtual machine.
                    Shutting down machine
           11       [Standard]                                   If the settings for machine registration to
                    Deleting machine registration to DPM         DPM are configured to the group, the
                                                                 registration of the target machine is
                                                                 deleted.
                                                                 If the settings are not configured, this
                                                                 process is skipped and the next process of
                                                                 updating configuration information is
                                                                 executed.

Part I SigmaSystemCenter Functions Reference
                                                                                                         107
1 Functions of SigmaSystemCenter


           Order   Step                                       Detail

           12      [Standard]                                 Sets the Host Setting used by the virtual
                   Releasing Host Setting                     machine to the unused state.

           13      [Standard]                                 Updates the status of the machine, such as
                   Updating configuration information         process completion status.

           14      [Standard]                                 Deletes the virtual machine from its virtual
                   Deleting virtual machine                   machine server.



           Note:
           ▪ Master VM and Replica VM (except Edge Cache Replica VM) cannot be deleted.
           ▪ If you delete a Differential Clone type virtual machine, an Edge Cache Replica VM to
           which the virtual machine refers will also be deleted automatically under the condition
           that there are no other virtual machines which refer to the Edge Cache Replica VM.
           However, if there are no other virtual machines which refer to the Edge Cache Replica
           VM by executing Reconstruct, the Edge Cache Replica VM will not be deleted
           automatically. In this case, you need to delete the Edge Cache Replica VM in another
           way. Additionally, if a Xen environment is used, the Edge Cache replica VM will not be
           deleted automatically.
           ▪ Delete unnecessary Edge Cache Replica VM manually in a Xen environment.
           ▪ Disk information of Replica VM in a Standalone ESXi environment will not be deleted
           even if you selected the Delete Disk Information check box.
           ▪ The virtual machine that were created by the disk switching function in
           SigmaSystemCenter 1.2 / 1.3 has "_(numbers)" in the name. Other virtual machines
           might refer to a disk image of the virtual machine. If you delete the virtual machine,
           other virtual machines will also be deleted from the virtual disk image at the same time.
           Therefore, if you want to delete the virtual machine, delete virtual machines on the
           virtual disk image first using vCenter Infrastructure Client.



1.10.15. Move Virtual Machine (Virtual Machine)
           The process of moving a virtual machine (Move Virtual Machine) moves a virtual
           machine to a different virtual machine server.


           Note:
           ▪ You cannot move a virtual machine on Hyper-V single server.
           ▪ Only Hot Migration / Cold Migration is supported in Hyper-V Cluster environment. Hot
           Migration and Cold Migration indicate Hyper-V Live Migration and VM movement
           between the nodes respectively. Move or Failover cannot be selected on the window.
           ▪ Standalone ESXi supports Move and Failover only to a virtual machine on the shared
           storage (except NFS). However, the Failover does not support the operation from the
           screen. It only supports when triggered by a policy and when a virtual machine server is
           specified as a target machine of evacuate machine command of the ssc command.
           ▪ This operation does not support Differential Clone virtual machines.


                                                          SigmaSystemCenter 2.1 Reference Guide
108
                                                                 Changes in Machine Configuration


           ▪ If you execute this operation on virtual machines in power ON status, they might be
           powered OFF.


           With SystemProvisioning, to move a powered ON virtual machine on a shared storage
           (SAN, NFS, iSCSI) to a different virtual machine server is called Hot Migrate, on the
           other hand, to move a powered OFF virtual machine to a different virtual machine
           server is called Cold Migrate.
           To move a powered OFF virtual machine to different virtual machine server, including
           its disk is called Move. The Move process takes longer time than Hot Migrate or Cold
           Migrate.
           In addition, to move a virtual machine to a different virtual machine server when a
           virtual machine server downed by an error is called Failover. To execute Failover, the
           virtual machine needs to be on a shared storage (SAN, NFS, iSCSI).


           If you specify to execute all the processes of Hot Migrate or Cold Migrate, Move, and
           Failover, Hot Migrate or Cold Migrate is executed first. If the process fails due to a
           virtual machine environment or running status, Move is executed. If the process of
           Move fails, then Failover is executed.


           The flow of the processes of Move Virtual Machine is as follows:




           The following table shows the steps to move a machine.


           Order   Step                                     Detail

           1       [Standard]                               Moves a machine in the active status or
Part I SigmaSystemCenter Functions Reference
                                                                                                   109
1 Functions of SigmaSystemCenter

                   Hot Migrate / Cold Migrate      suspended status or powered off.
           2       [Standard]                      Checks the power status of the virtual
                   Checking power status           machine.

           3       [Standard]                      Shuts down the virtual machine when its
                   Shutting down machine           power is ON.

           4       [Standard]                      Moves a machine in the suspended status
                   Move                            or powered off.

           5       [Standard]                      Moves the virtual machine with Failover.
                   Failover
           6       [Standard]                      Checks the power status of the virtual
                   Checking power status           machine.

           7       [Standard]                      Starts the virtual machine when its power is
                   Starting machine                OFF.




                                                SigmaSystemCenter 2.1 Reference Guide
110
                                                                      Changes in Machine Configuration




1.10.16. Power Operation to Machine / Start
            When a machine is specified:
             When a machine is specified, the operation is executed to the machine.

               The following operations are the targets of this operation:
               •   Operations view - Start
               •   Operation view - Action menu - Start
               •   Resource view - Start
               •   Virtual view - Start
               •   pvmutl poweron
               •   Action of a policy Action for Machine / Startup Machine


               Order    Step                                           Detail

               1        [Standard]                                     Updates the status of the machine to
                        Updating configuration information             In-process.

               2        [Standard]                                     Starts up the machine.
                        Starting machine
               3        [Standard]                                     Updates the status of the machine, such as
                        Updating configuration information             process completion status.



            When a group is specified:
             The following operations are the targets of this operation:
               •   Action of a policy Action for Group / Startup a Machine in the Group


               Order    Step                                           Detail

               1        [Standard]                                     Creates a list of machines running in the
                        Creating list                                  specified group.

               2        Repeats the following process to search for a machine that can be started up.
                        If a target machine is found, then executes the step 4. If not, the Job ends with an error.
                        [Standard]                                     Selects a machine in the list created in the
                        Selecting machine                              step 1.

                        [Standard]                                     Checks the status of the selected machine.
                        Checking status of machine                     If the status is not In-process, Error, or
                                                                       Maintenance, the machine becomes a
                                                                       target of the operation.
               3        [Standard]                                     Updates the status of the machine to
                        Updating configuration information             In-process.

               4        [Standard]                                     Starts up the machine.
                        Starting machine
               5        [Standard]                                     Updates the status of the machine, such as
                        Updating configuration information             process completion status.

Part I SigmaSystemCenter Functions Reference
                                                                                                          111
1 Functions of SigmaSystemCenter




1.10.17. Power Operation to Machine / Restart
           Restart is executed to a machine.


           The following operations are the targets of this operation:
            Operations view - Restart
            Operations view - Action menu - Restart
            Resource view - Restart
            Virtual view - Restart
            pvmutl reboot
            Action of a policy Action for Machine / Reboot Machine


           Order   Step                                           Detail

           1       [Standard]                                     Updates the status of the machine to
                   Updating configuration information             In-process.

           2       [Standard]                                     Starts up the machine.
                   Starting machine
           3       [Standard]                                     Updates the status of the machine, such as
                   Updating configuration information             process completion status.




1.10.18. Power Operation to Machine / Shutdown
            When a machine is specified:
             When a machine is specified, the operation is executed to the machine.

               The following operations are the targets of this operation:
               •    Operations view - Shutdown
               •    Operation view - Action menu - Shutdown
               •    Resource view - Shutdown
               •    Virtual view - Shutdown
               •    pvmutl shutdown
               •    Action of a policy Action for Machine / Shutdown Machine


               Order      Step                                        Detail

               1          [Standard]                                  Updates the status of the machine to
                          Updating configuration information          In-process.

               2          [Standard]                                  Shuts down the machine.
                          Shutting down machine
               3          [Standard]                                  Updates the status of the machine, such as
                          Updating configuration information          process completion status.


                                                               SigmaSystemCenter 2.1 Reference Guide
112
                                                                    Changes in Machine Configuration



            When a group is specified:
             The following operations are the targets of this operation:
               •   Action of a policy Action for Group / Shutdown a Machine in the Group


               Order    Step                                        Detail

               1        [Standard]                                  Creates a list of machines running in the
                        Creating list                               specified group.

               2        Repeats the following process to search for a machine that can be shut down.
                        If a target machine is not found, the Job ends with an error.
                        [Standard]                                  Selects a machine in the list created in the
                        Selecting machine                           step 1.

                        [Standard]                                  Checks the status of the selected machine.
                        Checking status of machine                  If the status is not In-process, Error,
                                                                    Maintenance, or powered on, the machine
                                                                    becomes a target of the operation.
               3        [Standard]                                  Updates the status of the machine to
                        Updating configuration information          In-process.

               4        [Standard]                                  Shuts down the machine.
                        Shutting down machine
               5        [Standard]                                  Updates the status of the machine, such as
                        Updating configuration information          process completion status.




Part I SigmaSystemCenter Functions Reference
                                                                                                       113
1 Functions of SigmaSystemCenter




1.10.19. Power Operation to Machine / Suspend
            When a machine is specified:
             When a machine is specified, the operation is executed to the machine.

               The following operations are the targets of this operation:
               •   Operations view - Suspend
               •   Operation view - Action menu - Suspend
               •   Resource view - Suspend
               •   Virtual view - Suspend


               Order    Step                                        Detail

               1        [Standard]                                  Updates the status of the machine to
                        Updating configuration information          In-process.

               2        [Standard]                                  Suspends the machine.
                        Suspending machine
               3        [Standard]                                  Updates the status of the machine, such as
                        Updating configuration information          process completion status.



            When a group is specified:
             The following operations are the targets of this operation:
               •   Action of a policy Action for Group / Suspend a Machine in the Group


               Order    Step                                        Detail

               1        [Standard]                                  Creates a list of machines running in the
                        Creating list                               specified group.

               2        Repeats the following process to search for a machine that can be suspended.
                        If a target machine is not found, the Job ends with an error.
                        [Standard]                                  Selects a machine in the list created in the
                        Selecting machine                           step 1.

                        [Standard]                                  Checks the status of the selected machine.
                        Checking status of machine                  If the status is not In-process, Error,
                                                                    Maintenance, or powered on, the machine
                                                                    becomes a target of the operation.
               3        [Standard]                                  Updates the status of the machine to
                        Updating configuration information          In-process.

               4        [Standard]                                  Suspends the machine.
                        Suspending machine
               5        [Standard]                                  Updates the status of the machine, such as
                        Updating configuration information          process completion status.




                                                             SigmaSystemCenter 2.1 Reference Guide
114
                                                                  Changes in Machine Configuration




1.10.20. Power Operation to Machine / Power ON
           Power ON is executed to a machine.


           The following operations are the targets of this operation:
            Resource view - Show Maintenance Command - Power ON


           Order   Step                                       Detail

           1       [Standard]                                 Updates the status of the machine to
                   Updating configuration information         In-process.

           2       [Standard]                                 Turns the power of the machine ON.
                   Turning machine on
           3       [Standard]                                 Updates the status of the machine, such as
                   Updating configuration information         process completion status.




1.10.21. Power Operation to Machine / Power OFF
           Power OFF is executed to a machine.


           The following operations are the targets of this operation:
            Resource view - Show Maintenance Command - Power OFF


           Order   Step                                       Detail

           1       [Standard]                                 Updates the status of the machine to
                   Updating configuration information         In-process.

           2       [Standard]                                 Turns the power of the machine OFF.
                   Turning machine off
           3       [Standard]                                 Updates the status of the machine, such as
                   Updating configuration information         process completion status.




Part I SigmaSystemCenter Functions Reference
                                                                                                     115
1 Functions of SigmaSystemCenter




1.10.22. Power Operation to Machine / Reset
           Reset is executed to a machine.


           The following operations are the targets of this operation:
            Resource view - Show Maintenance Command - Reset


           Order   Step                                       Detail

           1       [Standard]                                 Updates the status of the machine to
                   Updating configuration information         In-process.

           2       [Standard]                                 Resets the machine.
                   Resetting machine
           3       [Standard]                                 Updates the status of the machine, such as
                   Updating configuration information         process completion status.




1.10.23. Power Operation to Machine / Power Cycle
           Power Cycle is executed on a machine.


           The following operations are the targets of this operation:


            Resource view - Show Maintenance Command - Power Cycle


           Order   Step                                       Detail

           1       [Standard]                                 Updates the status of the machine to
                   Updating configuration information         In-process.

           2       [Standard]                                 Power Cycle the machine.
                   Power Cycle of machines
           3       [Standard]                                 Updates the status of the machine, such as
                   Updating configuration information         process completion status.




                                                          SigmaSystemCenter 2.1 Reference Guide
116
                                                                       Changes in Machine Configuration




1.10.24. Power Operation to Machine / ACPI Shutdown
           ACPI Shutdown is executed on a machine.


           The following operations are the targets of this operation:


            Resource view - Show Maintenance Command - ACPI Shutdown


           Order   Step                                           Detail

           1       [Standard]                                     Updates the status of the machine to
                   Updating configuration information             In-process.

           2       [Standard]                                     Executes ACPI shutdown on the machine.
                   ACPI shutdown of machines
           3       [Standard]                                     Updates the status of the machine, such as
                   Updating configuration information             process completion status.



           SigmaSystemCenter has confirmed that ACPI Shutdown is operational on OSs listed
           below if the machines are NEC Express 5800 series:


           OS Name     Windows Server 2003 Enterprise Edition R2 SP2 *1 *2
                       Windows Server 2003 Enterprise x64 Edition R2 SP2 *1 *2
                       Windows Server 2008 Enterprise (x86) SP2 *2
                       Windows Server 2008 Enterprise (x64) R2 *2
                       Windows Server 2008 Enterprise (x64) SP2 (Hyper-V environment) *2
                       Red Hat Enterprise Linux 5 (32bit)
                       Red Hat Enterprise Linux 5 (EM64T)
                       SUSE Linux Enterprise Server 9 Service Pack 3
           *1          When enabling ACPI shutdown even if you do not log in to managed machines,
                       configure the setting as follows:
                       ▪ Enable the Allow system to be shut down without having to log on under the
                       Security Options, located in Local Policy, which is displayed by clicking Administrative
                       Tool – Local Security Policy.
           *2          ACPI shutdown might fail under the conditions listed below:
                       ▪ The Allow system to be shut down without having to log on under the Security
                       Options, located in Local Policy, which is displayed by clicking Administrative Tool –
                       Local Security Policy is not enabled.
                       ▪ Screen savers with password authentication are active.
                       ▪ When logging in from a remote desktop.
                       ▪ When the computer is locked.
                       ▪ When running an application without saving the operation.




Part I SigmaSystemCenter Functions Reference
                                                                                                          117
1 Functions of SigmaSystemCenter




1.10.25. Power Operation to Machine / Investigate and Power OFF
           Investigates a machine and executes Shutdown or Power OFF according to the result.


           The following operations are the targets of this operation:
            Action of a policy Action for Machine / Investigate and Power OFF


           Order   Step                                        Detail

           1       [Standard]                                  Updates the status of the machine to
                   Updating configuration information          In-process.

           2       [Standard]                                  Acquires the status of the machine and
                   Investigating target machine                investigate the machine. The points to
                                                               investigate are as follows:
                                                               ▪ The status of a compatible product that
                                                               manages the target machine
                                                               ▪ The OS status of the target machine
                                                               ▪ The status of a disk of the target machine
                                                               If there is a defect, checks other machine
                                                               in a group. In that case, skips to the step 3.
                                                               However, if SystemProvisioning judges
                                                               that an error occurs on a single target
                                                               machine, skips to the step 5.
                                                               If there is no defect, SystemProvisioning
                                                               abandons the following process, and the
                                                               Job ends with an error.
           3       [Standard]                                  Creates a list of machines that are in the
                   Creating list                               same group with the target machine.

           4       Repeats the following process to search for a machine that has the same defect as that
                   of the target machine.
                   If a machine that has the same defect is not found, SystemProvisioning judges that the
                   defect is an error of a single target machine and skips to the step 5.
                   If a machine that has the same defect is found, SystemProvisioning abandons the
                   following step, and the Job ends with an error.
                   [Standard]                                  Selects a machine in the list created in the
                   Selecting machine                           step 3.

                   [Standard]                                  Acquires the status of the selected
                   Investigating selected machine              machine and investigates the machine.
                                                               The points to investigate are as follows:
                                                               ▪ The status of a compatible product that
                                                               manages the target machine
                                                               ▪ The OS status of the target machine
                                                               ▪ The status of a disk of the target machine
           5       [Standard]                                  Shuts down the machine.
                   Forcing the machine to be powered off       If shutting down the machine fails,
                                                               SystemProvisioning forces the machine to
                                                               be powered off.
           6       [Standard]                                  Updates the status of the machine, such as
                   Updating configuration information          process completion status.

                                                            SigmaSystemCenter 2.1 Reference Guide
118
                                                                              About Power Control



1.11. About Power Control
           This section explains the details and settings of power control that SigmaSystemCenter
           can execute to various machines.



1.11.1. Products and Components That Power Control Uses
           The power control function of SigmaSystemCenter is implemented by using multiple
           third-party products or internal functions that can control power of resources.
           SigmaSystemCenter selects an appropriate product or component according to types
           of a target managed machine or circumstances under control.


           The power control function uses the following products or components:


            Power control through DPM
               The functions of DeploymentManager are used.
               The Power On is performed with Wake On LAN by Magic Packet.
               By sending a packet called Magic Packet from a Management Server for DPM to a
               machine that you wish to start, SigmaSystemCenter can power on the machine.
               To shut down or restart, Client Service for DPM that is installed on a managed
               machine is used.
               To power control machines through DPM, the managed machines need to be
               registered in DPM.


               •   Start
                   Broadcasts Magic Packed from a Management Server for DPM and powers
                   on a managed machine. For a managed machine in the other segment, direct
                   broadcast is used. After powering on, the system waits until the system
                   confirms the start of OS. After confirming the start of the OS, the system
                   completes the process after waiting for certain period of time.
                   If power control through BMC is available, it is given priority over power
                   control through DPM. Power control through DPM is executed if power control
                   through BMC fails.
                   Power ON through DPM to virtual machines is not supported since virtual
                   machines do not support WOL. (You can execute Power ON to virtual
                   machines with the DPM Web Console; however, the operation ends with an
                   error,)


               •   Shutdown
                   Shuts down a managed machine by a command from a Management Server
                   for DPM to Client Service for DPM that is running on the managed machine.



Part I SigmaSystemCenter Functions Reference
                                                                                               119
1 Functions of SigmaSystemCenter



                   After shutting down the machine, the system waits for the process to complete
                   until the power status of the machine turns to Off using the power control
                   through BMC. If the system cannot acquire the power status of a machine with
                   the power control through BMC, the system completes the process after
                   waiting for certain period of time.
                   If the shutdown operation through DPM fails, the ACPI Shutdown operations
                   through BMC will be executed.*1
                   If a managed machine is a virtual machine or virtual machine server, power
                   control through virtual infrastructure products is given priority over power
                   control through DPM. If the process through a virtual infrastructure product
                   fails, power control through DPM is used.


               •   Restart
                   Restarts a managed machine by a command from a Management Server for
                   DPM to Client Service for DPM that is running on the managed machine. After
                   restarting the machine, the system waits until the system confirms the start of
                   OS. After confirming the start of the OS, the system completes the process
                   after waiting for certain period of time.
                   If a managed machine is a virtual machine or virtual machine server, power
                   control through virtual infrastructure products is given priority over power
                   control through DPM. If the process through a virtual infrastructure product
                   fails, power control through DPM is used.


            Power control through BMC (The power management function by OOB)
               The power management function by Out-of-Band (OOB hereafter) is used. This
               function uses EXPRESSSCOPE engine (a management chip generally called
               BCM, Baseboard Management Controller) loaded on a machine. This can operate
               machines in remote without depending on their actions status of OS.
               You cannot execute power control through BMC to virtual machines.
               To use this function, you need to connect management LAN to a port for
               management on a managed machine.
               You also need to set IP address to connect from a management server to BMC on
               a managed machine for control, an account, and password to
               SigmaSystemCenter.
               For details of the procedure to configure an account on SigmaSystemCenter, refer
               to Subsection 3.8.1, “Enabling Management Function by Out-of-Band (OOB)
               Management” and 3.11.6, “Configuring Settings on the Account Tab” in
               SigmaSystemCenter Configuration Guide.
               •   Start
                   Powers on a managed machine from a management server through BMC.
                   After powering on, the system checks the OS starting status through DPM and
                   waits until the system confirms the start of OS. After confirming the start of the
                   OS, the system completes the process after waiting for certain period of time.



                                                          SigmaSystemCenter 2.1 Reference Guide
120
                                                                                About Power Control



                   This is given priority over power control through DPM above, and if the
                   settings are registered, normally the start process is executed through BMC. If
                   this operation fails, start through DPM is executed.


               •   Power ON
                   Powers on a managed machine from a management server through BMC.
                   Unlike the start operation, the power on operation does not guarantee the OS
                   start-up. Therefore, there is a possibility that you cannot use the managed
                   machine after the process completes. Note this point when you execute any
                   operation to a managed machine after power on operation.
                   For this reason, this operation cannot be executed from the normal Operation
                   Command. It can only be executed from the Maintenance Command.


               •   Power OFF
                   Powers off a managed machine from a management server through BMC.
                   After powering off, the system waits until the power status of the machine
                   turns to Off,
                   This operation powers off the hardware of the machine without shutting down
                   the OS and it may cause a risk, such as disk damage, so do not use this
                   operation in the normal operation.
                   For this reason, this operation cannot be executed from the normal Operation
                   Command. It can only be executed from the Maintenance Command.
                   In addition, if a managed machine is diagnosed with failure by a policy's
                   investigating action, "Investigate / Power OFF", this operation is executed.


               •   Reset
                   Resets a managed machine from a management server through BMC. Unlike
                   the restart operation, the reset operation does not guarantee the OS start-up.
                   Therefore, there is a possibility that you cannot use the managed machine
                   after the process completes. Note this point when you execute any operation
                   to a managed machine after the reset operation.
                   In addition, this operation resets the hardware of the machine without
                   restarting the OS and it may cause a risk, such as disk damage, so do not use
                   this operation in the normal operation.
                   For these reasons, this operation cannot be executed from the normal
                   Operation Command. It can only be executed from the Maintenance
                   Command.


               •   Power Cycle
                   Executes Power Cycle from a management server through BMC of managed
                   machines. Normally, Power Cycle operation finishes when OS of a managed
                   machine is not started yet. Therefore, there is a possibility that you cannot use
                   the managed machine after the process completes. Note this point when you
                   execute any operation to a managed machine after the reset operation.

Part I SigmaSystemCenter Functions Reference
                                                                                                  121
1 Functions of SigmaSystemCenter



                   Additionally, this operation does not shut down OS, but turns off and turns on
                   the hardware. Therefore, disks might be damaged. Be sure not to use this
                   operation in usual management.
                   For the reasons noted above, Power Cycle cannot be executed form the
                   Operation menu. It can be executed only from maintenance operations.


               •   ACPI Shutdown
                   Executes ACPI shutdown from a management server through BMC of
                   managed machines. Availability of this operation depends on OSs of
                   managed machines. Be sure to configure the OS settings to work ACPI
                   shutdown properly.
                   For instructions on how to configure the OS settings, refer to Subsection
                   2.15.7, "Enabling ACPI Shutdown" in SigmaSystemCenter Configuration
                   Guide.
                   ACPI shutdown cannot be executed from the Operations menu because of the
                   reason described above. It can be executed from maintenance operations.


            Power control through virtual infrastructure products
               Performs power control of virtual machines and virtual machine servers using the
               power control function of virtual infrastructure products, such as VMware,
               XenServer, and Hyper-V.
               For virtual machine servers, only shutdown and restart can be executed.
               For Power OFF and Reset to virtual machines, the power control through BMC that
               is mentioned above is not executed and these operations can be executed through
               the virtual infrastructure products.
               To power control machines through virtual infrastructure products, the managed
               machines need to be registered in the virtual infrastructure products.


               •   Start
                   Powers on a virtual machine through virtual infrastructure products. After
                   powering on, the system waits until the system confirms the start of OS. After
                   confirming the start of the OS, the system completes the process after waiting
                   for certain period of time.
                   For a virtual machine server, as this operation cannot be executed through the
                   virtual infrastructure products, it is executed by the power control through
                   DPM or BMC.


               •   Power ON
                   Powers on a virtual machine through virtual infrastructure products. Unlike the
                   start operation, the power on operation does not guarantee the OS start-up.
                   Therefore, there is a possibility that you cannot use the managed machine
                   after the process completes. Note this point when you execute any operation
                   to a managed machine after power on operation.
                   Power ON can be executed only from the Maintenance Command.
                                                        SigmaSystemCenter 2.1 Reference Guide
122
                                                                               About Power Control



                   For a virtual machine server, as this operation cannot be executed through the
                   virtual infrastructure products, it is executed by the power control through
                   BMC.


               •   Quick start
                   By executing quick start, a virtual machine can be powered on more quickly
                   than usual. This operation can be executed by the /q option of the pvmutl
                   command and cannot be executed from the Web Console.
                   As the quick start powers on a machine with simplified confirmation of start of
                   OS after powering on, there is a higher possibility of a risk than normal
                   operations, such as the target machine cannot be used after this operation is
                   completed and a subsequent operation can throw an error; however, this
                   quicken process completion.
                   This operation can be executed only to a VMware virtual machine.


               •   Shutdown
                   Shuts down a virtual machine or virtual machine server through virtual
                   infrastructure products.
                   As for a virtual machine, the system waits for process completion after
                   shutdown until the Power Status of the target machine turns to Off.
                   And as for a virtual machine server, it waits for process completion until the
                   Power Status of the target machine turns to Off using the power control
                   through BMC after shutdown.
                   If the system cannot acquire the power status of the machine by the power
                   control through BMC, it ends the process after waiting for a certain period of
                   time.
                     If the shutdown process fails through virtual infrastructure products, the
                   shutdown operation through DPM is executed subsequently. If the shutdown
                   operation through DPM also fails, the ACPI shutdown operation through BMC
                   is finally executed. *1, *2


                   When shutting down a virtual machine server, operations to be executed for
                   virtual machines on the virtual machine server differ depending on each
                   product.
                   Note when you execute the shutdown operation to a virtual machine server as
                   it executes control that affects the virtual machines in use no matter what
                   product you are using.
                   -   VMware
                       Shuts down a running virtual machines.
                   -   XenServer
                       Shuts down a running virtual machines.
                       If there is a running virtual machine, the system does not execute the
                       shutdown operation to the virtual machine server and ends the process

Part I SigmaSystemCenter Functions Reference
                                                                                                    123
1 Functions of SigmaSystemCenter

                       with an error. After that, the power control through DPM is not executed
                       as well (SigmaSystemCenter 2.1 update 2 or before).


                   -   Hyper-V
                       Depending on the setting of the Automatic Stop Action of the virtual
                       machine server, the operation to be executed differs.
                       You need to set one of the following settings on the Hyper-V Manager.
                       ▪ Save the virtual machine state (Default setting)
                       ▪ Turn off the virtual machine
                       ▪ Shut down the guest operating system
                       In addition, control to the virtual machine of when the virtual machine
                       server is started the next time differs depending on the setting of the
                       Automatic Start Action.
                       Also about this setting, you need to configure on the Hyper-V Manager.
                       ▪ Nothing
                       ▪ Automatically start if it was running when the service stopped (Default
                       setting)
                       ▪ Always start this virtual machine automatically


                       If a virtual machine is started automatically after starting a virtual machine
                       server, the power status of the virtual machine is not reflected correctly to
                       SigmaSystemCenter. In that case, execute Collect to synchronize the
                       status.


                   Note: If virtual machines are running on a virtual machine server, shutdown
                   operations cannot be executed on the virtual machine server in Hyper-V
                   cluster environment. Be careful when shutting down a virtual machine server
                   because the shutdown operation might influence the cluster management.


               •   Reset
                   Only to a virtual machine, the system can execute Reset through virtual
                   infrastructure products.
                   To a virtual machine server, as the system cannot execute Reset through
                   virtual infrastructure products, the operation is executed through BMC.
                   Normally, Reset can be executed from the Maintenance Command. If Reset
                   of the Maintenance Command is executed, unlike the restart operation, the
                   reset operation does not guarantee the OS start-up. Therefore, there is a
                   possibility that you cannot use the managed machine after the process
                   completes. Note this point when you execute any operation to a managed
                   machine after power on operation.
                   If a managed machine is a Hyper-V virtual machine, this operation cannot be
                   executed.



                                                         SigmaSystemCenter 2.1 Reference Guide
124
                                                                              About Power Control



               •   Quick restart
                   By executing quick restart, a virtual machine can be restarted more quickly
                   than usual. This operation can be executed by the /q option of the pvmutl
                   command and cannot be executed from the Web Console.
                   As the quick restart powers on a machine with simplified confirmation of start
                   of OS after powering on, there is a higher possibility of a risk than normal
                   operations, such as the target machine cannot be used after this operation is
                   completed and a subsequent operation can throw an error; however, this
                   quicken process completion.
                   This operation can be executed only to a VMware virtual machine.


               •   Suspend
                   Suspends a virtual machine through virtual infrastructure products.


           *1 However, if the shutdown operation through DPM time out, the ACPI shutdown
           through BMC is not be executed.
           *2 ACPI shutdown operations through BMC are not executed on virtual machines.




Part I SigmaSystemCenter Functions Reference
                                                                                                 125
1 Functions of SigmaSystemCenter




1.11.2. List of Power Control Operations
           This subsection shows a list of power control operations that can be controlled by
           third-party products or components.
           The priority order of execution is 1 to 2.


           Control            Through       Through           Through          Notes
           Method             DPM           BMC               Virtual
                                                              Infrastructure

           Type          of   Other   VM    Other       VM    VMS       VM
           Management         than          than
                              VM            VM

           Start              2       N/A   1           N/A   N/A       1

           Power ON           2       N/A   1           N/A   N/A       1      ▪ No start check with OS

           Quick Start        N/A     N/A   N/A     N/A       N/A       1      ▪ High speed, but abbreviate
                                                                               a part of checks
                                                                               ▪ Not available for Hyper-V
                                                                               and Xen

           Shutdown           2       2     3           N/A   1         1      ▪ ACPI shutdown is
                                                                               executed through BMC

           Power OFF          N/A     N/A   1       N/A       N/A       1      ▪ High risk at disk damage,
                                                                               etc

           ACPI               N/A     N/A   1           N/A   N/A       N/A
           Shutdown

           Power Cycle        N/A     N/A   1           N/A   N/A       N/A    ▪ No start check with OS
                                                                               ▪ High risk at disk damage,
                                                                               etc

           Restart            2       2     N/A     N/A       1         1      ▪ Reset (via virtual
                                                                               infrastructure) is executed if
                                                                               restarting a VM failed due to
                                                                               time out

           Reset              N/A     N/A   1       N/A       N/A       1      ▪ High risk at disk damage,
                                                                               etc
                                                                               ▪ No start check with OS
                                                                               ▪ Not available for Hyper-V

           Quick Restart      N/A     N/A   N/A     N/A       N/A       1      ▪ High speed, but no check
                                                                               ▪ Not available for Hyper-V
                                                                               and Xen

           Suspend            N/A     N/A   N/A     N/A       N/A       1



           You can execute each power control operation from a window or command. The
           following table shows how you can execute the power operations.


                                                              SigmaSystemCenter 2.1 Reference Guide
126
                                                                                        About Power Control



           In the Operations view on the Web Console, you can execute power operations to all
           machines in a group.
           For Power ON, Power OFF, Reset, Power Cycle, and ACPI Shutdown, you need to
           execute Show the Maintenance Command. By default, the Maintenance Commands
           are not displayed so you need to execute Show the Maintenance Command to switch a
           window to display the Maintenance Commands.


           Operation         Web Console                                       Command
           Method
                             Operations       Resource        Virtual          pvmutl           ssc
                             view             view            view

           Start             X                X               X                poweron

           Power ON                           X
                                              (Maintenance
                                              Command) *1

           Quick Start                                                         poweron /q

           Shutdown          X                X               X                shutdown

           Power OFF                          X
                                              (Maintenance
                                              Command) *1

           ACPI                               X
                                              (Maintenance
           Shutdown
                                              Command) *1

           Power Cycle                        X
                                              (Maintenance
                                              Command) *1

           Restart           X                X               X                reboot

           Reset                              X
                                              (Maintenance
                                              Command) *1

           Quick                                                               reboot /q
           Restart

           Suspend           X                X               X
                                                              (Only for
                                                              Virtual
                                                              Machine)
           *1            When executing this operation on machines that are assigned to the host setting, set
                         the Maintenance Mode.




Part I SigmaSystemCenter Functions Reference
                                                                                                          127
1 Functions of SigmaSystemCenter




1.11.3. Sequences of Power Control
           This subsection explains details of start, shutdown, and restart of power control of
           SigmaSystemCenter. If you want to estimate processing time of power control or if the
           default setting values of power control does not suite your system, refer to the
           explanation in this subsection or the following section.


           See the following subsection (1.11.4, "Setting Timeout Time and Waiting Time") for the
           explanation of registry keys and default values for timeout time or waiting time
           described in this subsection.


           Note that if processing time of all power control operations exceeds the value of
           PowerControlTimeout, the operations end with a timeout error regardless of each
           setting of timeout time and waiting time.


            Start
               1.   Checks if OS of a target machine has already started.
                    If the OS has started, updates the OS Status information and Power Status
                    information to On and completes the process.
               2.   Executes the process of starting the target machine
                    In the priority order in Subsection 1.11.2, "List of Power Control Operations,"
                    the system repeats the process until the process succeeds. However, if the
                    process times out and throws an error, the subsequence process ends with an
                    error without being executed.
                    The values of "StartupTimeout" and "PowerOnTimeout" are used as the time
                    to wait till timeout. These values are used depending on a type of a target
                    machine and circumstances. For a machine type that does not have a value,
                    the process does not throw a timeout error in this step.
               3.   If the process succeeds, the system waits until it confirms start of the OS.
                    If the time to start the OS exceeds a certain period of time, the process ends
                    with a timeout error. The value of "Startup_PollingTimeoutXXXX" is used as
                    the time to wait for the OS to start. The value differs depending on a type of a
                    target machine. For a virtual machine, as the system has already checked its
                    start in the step 2, it goes forward to the next step without waiting. If the
                    system cannot confirm start of OS of a target machine (if the target machine is
                    not registered either to DPM or virtual infrastructure products), the system
                    goes forward to the next step.
               4.   Waits for a certain period of time.
                    If the system has confirmed start of OS of the target machine, it waits for the
                    time that is specified in "Startup_WaitTimeAfterOSOnXXXX". The value
                    differs depending on a type of a target machine.
                    If the system cannot confirm start of OS of a target machine (if the target
                    machine is not registered either to DPM or virtual infrastructure products), the
                    system waits for the time that is specified in
                    "Startup_WaitTimeAfterPowerOn".

                                                          SigmaSystemCenter 2.1 Reference Guide
128
                                                                                 About Power Control

               5.   Updates the OS Status information and Power Status information of the target
                    machine to On and completes the process.


            Shutdown
               1.   Checks if OS of a target machine has already stopped.
                    If the OS has stopped, updates the OS Status information and Power Status
                    information to Off and completes the process.
               2.   Executes the process of shutting down the target machine
                    In the priority order in Subsection 1.11.2, "List of Power Control Operations,"
                    the system repeats the process until the process succeeds. However, if the
                    process times out and throws an error, the subsequence process ends with an
                    error without being executed.
                    The values of "ShutdownTimeout" and "PowerOffTimeout" are used as the
                    time to wait till timeout. These values are used depending on a type of a target
                    machine and circumstances. For a machine type that does not have a value,
                    the process does not throw a timeout error in this step.
               3.   If the process succeeds, the system waits until the target machine powers Off.
                    If the time to start the OS exceeds a certain period of time, the process ends
                    with a timeout error. The value of "Shutdown_PollingTimeoutXXXX" is used
                    as the time to wait until the machine powers off. The value differs depending
                    on a type of a target machine. For a virtual machine, as the system has
                    already checked its power off status in the step 2, it does not wait.
               4.   If the system cannot confirm the power off status, it waits for a certain period
                    of time. The value of "Shutdown_WaitTimeAfterOSOffXXXX" is used as the
                    time to wait until the machine powers off in this step.
                    If the system has already confirmed the power off status, it does not wait.
               5.   Updates the OS Status information and Power Status information of the target
                    machine to Off and completes the process.



            Restart
               1.   Executes the process of restarting a target machine.
                    The system does a series of available processes in the following order. The
                    following controls are executed with each power control product. For the
                    priority between the power control products, see the table in the Subsection
                    1.11.2, "List of Power Control Operations,"
                        1.   Restart
                        2.   Combination of Shutdown and Start (Power ON)


                    If any process throws a timeout error, the system performs the following action
                    according to a target machine type:
                    -   If the target machine is a virtual machine, the system does not execute
                        the subsequent process, but Reset (or combination of Power OFF and
                        Power ON). After executing Reset, confirms the start of the OS, waits for
                        a certain period of time, and ends as normal process.


Part I SigmaSystemCenter Functions Reference
                                                                                                   129
1 Functions of SigmaSystemCenter

                    -   If a target machine is other than a virtual machine, the system does not
                        execute the subsequent process and end the process with an error.


               2.   The values of "RebootTimeout", "ResetTimeout", "StartupTimeout",
                    "PowerOnTimeout", "ShutdownTimeout", and "PowerOffTimeout" are used as
                    the time to wait till timeout. These values are used depending on a type of a
                    target machine and circumstances. For a machine type that does not have a
                    value, the process does not throw a timeout error in this step.
               3.   If you execute Combination of Shutdown and Start (Power ON) in the step 1,
                    the system waits until the OS of the target machine starts.
                    If the time to start the OS exceeds a certain period of time, the process ends
                    with a timeout error. The value of "Startup_PollingTimeoutXXXX" is used as
                    the time to wait for the OS to start. The value differs depending on a type of a
                    target machine. For a virtual machine, as the system has already checked its
                    start in the step 1, it does not wait.
               4.   Waits for a certain period of time.
                    The value of "Startup_WaitTimeAfterOSOnXXXX" is referred as the time to
                    wait. The value differs depending on a type of a target machine.
               5.   Updates the OS Status information and Power Status information of the target
                    machine to On and completes the process.



1.11.4. Setting Timeout Time and Waiting Time
           To configure settings for timeout time and waiting time of various components, you
           need to change their registry settings.
           The following subsections explain about the following settings.
            Subsection 1.11.5, "Timeout Time and Waiting Time of Power Control Operations"
             About the following settings:
               •    Entire timeout time for power control jobs
               •    Timeout time after power ON until OS Status ON
               •    Timeout time after shutdown (OS Status OFF) until Power Status OFF
               •    Waiting time for job completion
            Subsection 1.11.6, "Time Out Period of Power Control Through BMC"
               About timeout time of power control through BMC
            Subsection 1.11.7, "Timeout Time of Power Control Through DPM"
               About timeout time of power control through DPM
            Subsection 1.11.8, "Timeout Time of Power Control Through Virtual Infrastructure"
               About timeout time of power control through virtual infrastructure




                                                          SigmaSystemCenter 2.1 Reference Guide
130
                                                                                 About Power Control




1.11.5. Timeout Time and Waiting Time of Power Control
           Operations
           You can set the settings for entire timeout time for power control jobs, timeout time after
           power ON until OS Status ON, timeout time after shutdown (OS Status OFF) until
           Power Status OFF, waiting time for completion of Start job, and waiting time for
           completion of Shutdown job (if checking the Power Status is not available) with the
           following registry values.
           Note that all the power control jobs end with an error if the processing time exceeds the
           value of PowerControlTimeout in spite of settings of other timeout time or waiting time.


           If needed, configure the following registry values.


           Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\ActionSequence


            Timeout


           Value Name                                    Target Machine                         Default
                                                                                                Value
                                                                                                (Sec)

           Entire timeout time for power control Jobs

           PowerControlTimeout                           All                                    3600

           Timeout time after powering ON until the OS Status turns to ON

           Startup_PollingTimeout                        Machines other than virtual machine    1800
                                                         servers or virtual machines
           Startup_PollingTimeout_VMServer_VMware        VMware virtual machine servers         1800
           Startup_PollingTimeout_VMServer_Xen           Xen virtual machine servers            1800
           Startup_PollingTimeout_VMServer_HyperV        Hyper-V virtual machine servers        1800

           Timeout time after shutting down (the OS Status OFF) until the Power Status turns to OFF

           Shutdown_PollingTimeout                       Machines other than virtual machine    1800
                                                         servers or virtual machines
           Shutdown_PollingTimeout_VMServer_VMware       VMware virtual machine servers         1800
           Shutdown_PollingTimeout_VMServer_Xen          Xen virtual machine servers            1800
           Shutdown_PollingTimeout_VMServer_HyperV       Hyper-V virtual machine servers       1800




Part I SigmaSystemCenter Functions Reference
                                                                                                   131
1 Functions of SigmaSystemCenter



            Waiting time for completion of Start job


           Value Name                                              Target Machine                       Default
                                                                                                        Value
                                                                                                        (Sec)

           Waiting time after the OS Status turns to ON until the "Start" job completes

           Startup_WaitTimeAfterOSOn *1                            Machines other than virtual          60
                                                                   machine servers or virtual
                                                                   machines
           Startup_WaitTimeAfterOSOn_VMServer_VMware               VMware virtual machine servers       60
           *1
           Startup_WaitTimeAfterOSOn_VMServer_Xen *1               Xen virtual machine servers          60
           Startup_WaitTimeAfterOSOn_VMServer_HyperV               Hyper-V virtual machine servers      60
           *1
           Startup_WaitTimeAfterOSOn_VM_VMware                     VMware virtual machines              0
           Startup_WaitTimeAfterOSOn_VM_Xen                        Xen virtual machines                 0
           Startup_WaitTimeAfterOSOn_VM_HyperV                     Hyper-V virtual machines             0

           Waiting time after the Power Status turns to ON until the "Start" job completes (if the target
           machine is not registered to either DPM or virtual infrastructure products)

           Startup_WaitTimeAfterPowerOn                            Machines other than virtual          0
                                                                   machine servers or virtual
                                                                   machines


            Waiting time for completion of Shutdown job (if checking the Power Status is not
             available)


           Value Name                                                 Target Machine                    Default
                                                                                                        Value
                                                                                                        (Sec)

           Waiting time after the OS Status turns to OFF until the "Shutdown" job completes (if
           checking the Power Status is not available)

           Shutdown_WaitTimeAfterOSOff *2                             Machines other than virtual       60
                                                                      machine servers or virtual
                                                                      machines
           Shutdown_WaitTimeAfterOSOff_VMServer_VMware                VMware virtual machine servers    60
           Shutdown_WaitTimeAfterOSOff_VMServer_Xen                   Xen virtual machine servers       180
           Shutdown_WaitTimeAfterOSOff_VMServer_HyperV                Hyper-V virtual machine servers   60


           The following registry values are used if they exist.


           Note: These registry values remains for compatibility with previous versions. They might
           be unavailable in future versions. Therefore, try to minimize the use of them.




                                                                   SigmaSystemCenter 2.1 Reference Guide
132
                                                                                        About Power Control


           *1       The waiting time calculated from the following registry value will be used if it exists.
                    (In the case that the target machine is a virtual machine server, the larger of this waiting
                    time or above-mentioned waiting time will be used.)
                    ▪ HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\DPMProvider
                    -WaitingPowerON: Time(sec) from the beginning of “Start” job until completion of it
                    (includes waiting time after the OS status turns to ON). This value will be used only if the
                    target machine is not a virtual machine.
           *2       The waiting time calculated from the following registry value will be used if it exists.
                    ▪ HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\DPMProvider
                    -WaitingPowerOFF: Time(sec) from the beginning of “Shutdown” job until completion
                    of it (includes waiting time after the OS status turns to OFF). This value will be used only
                    if the target machine is not either a virtual machine server or a virtual machine.



1.11.6. Time Out Period of Power Control Through BMC
           If needed, you can configure the timeout time for power control through BMC from the
           following registry.


           Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Provider\Pim


            Timeout
                                                                     Value Name                   Default
                                                                                                  Value (Sec)

           Timeout time from the start of Power ON until the         PowerOnTimeout               180
           process completion

           Timeout time from the start of Power OFF until the        PowerOffTimeout              180
           process completion

           Timeout time from the start of Power Cycle until          PowerCycleTimeout            360
           the process completion

           Timeout time from the start of ACPI Shutdown until        ShutdownTimeout              900
           the process completion



           This registry does not have a value for ResetTimeout. Start is executed using Power
           On, so it refers to the value of PowerOnTimeOut.




Part I SigmaSystemCenter Functions Reference
                                                                                                               133
1 Functions of SigmaSystemCenter




1.11.7. Timeout Time of Power Control Through DPM
           If needed, you can configure the timeout time for power control through DPM from the
           following registry.


           Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\DPMProvider


            Timeout
                                                               Value Name                Default
                                                                                         Value (Sec)

           Timeout time from the start of shutdown until the   ShutdownTimeout           900
           process completion

           Timeout time from the start of restart until the    RebootTimeout             1800
           process completion



           Note that the start confirmation by Remote Power ON Timeout of DPM differs from the
           start confirmation of SigmaSystemCenter. The result of the start confirmation of DPM is
           not reflected. Therefore, the setting of Remote Power ON Timeout that can be
           configured on the Detailed Setting window opened from the Settings menu on the DPM
           Web Console does not effect on any actual action in SigmaSystemCenter.



1.11.8. Timeout           Time        of    Power         Control        Through         Virtual
           Infrastructure
           If needed, you can configure the timeout time for power control through virtual
           infrastructure from the following registry.


           Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Provider\VM
           This registry key is the specified value for any virtual infrastructure products. This is
           used if a specification value of a sub key of each product does not have a value or the
           value is zero.


            Timeout


                                                               Value Name                Default
                                                                                         Value (Sec)

           Timeout time from the start of start up until the   StartupTimeout            600
           process completion

           Timeout time from the start of Power ON until the   PowerOnTimeout            120
           process completion

                                                          SigmaSystemCenter 2.1 Reference Guide
134
                                                                                  About Power Control


           Timeout time from the start of shutdown until the    ShutdownTimeout           600
           process completion

           Timeout time from the start of Power OFF until the   PowerOffTimeout           60
           process completion

           Timeout time from the start of restart until the     RebootTimeout             600
           process completion

           Timeout time from the start of reset until the       ResetTimeout              180
           process completion

           Timeout time from the start of suspend until the     SuspendTimeout            120
           process completion



           Registry key:
           HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Provider\VM\VMware
           This sub key is used if a managed machine is managed in VMware.


            Timeout


                                                                Value Name                Default
                                                                                          Value (Sec)

           Timeout time from the start of start up until the    StartupTimeout            0
           process completion

           Timeout time from the start of Power ON until the    PowerOnTimeout            320
           process completion

           Timeout time from the start of shutdown until the    ShutdownTimeout           0
           process completion

           Timeout time from the start of Power OFF until the   PowerOffTimeout           260
           process completion

           Timeout time from the start of restart until the     RebootTimeout             0
           process completion

           Timeout time from the start of reset until the       ResetTimeout              380
           process completion

           Timeout time from the start of suspend until the     SuspendTimeout            320
           process completion




Part I SigmaSystemCenter Functions Reference
                                                                                                    135
1 Functions of SigmaSystemCenter



           Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Provider\VM\Xen
           This sub key is used if a managed machine is managed in XenServer.


            Timeout


                                                                Value Name         Default
                                                                                   Value (Sec)

           Timeout time from the start of start up until the    StartupTimeout     0
           process completion

           Timeout time from the start of Power ON until the    PowerOnTimeout     600
           process completion

           Timeout time from the start of shutdown until the    ShutdownTimeout    600
           process completion

           Timeout time from the start of Power OFF until the   PowerOffTimeout    600
           process completion

           Timeout time from the start of restart until the     RebootTimeout      600
           process completion

           Timeout time from the start of reset until the       ResetTimeout       600
           process completion

           Timeout time from the start of suspend until the     SuspendTimeout     600
           process completion




                                                         SigmaSystemCenter 2.1 Reference Guide
136
                                                                                  About Power Control



           Registry key:
           HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Provider\VM\HyperV
           This sub key is used if a managed machine is managed in Hyper-V.


            Timeout


                                                                Value Name                Default
                                                                                          Value (Sec)

           Timeout time from the start of start up until the    StartupTimeout            1800
           process completion

           Timeout time from the start of Power ON until the    PowerOnTimeout            120
           process completion

           Timeout time from the start of shutdown until the    ShutdownTimeout           1200
           process completion

           Timeout time from the start of Power OFF until the   PowerOffTimeout           60
           process completion

           Timeout time from the start of suspend until the     SuspendTimeout            180
           process completion



           Hyper-V does not have values for RebootTimeout or ResetTimeout. Restart is
           executed with the combination with shutdown and start, so it refers to values of
           ShutdownTimeout and StartupTimeout. Hyper-V does not support the reset process.




Part I SigmaSystemCenter Functions Reference
                                                                                                    137
1 Functions of SigmaSystemCenter



1.12. About Other Maintenance Operations
           This section provides details of other maintenance operations that can be executed on
           machines using Out-of-Band Management and instructions on how to configure the
           maintenance operations.
           The maintenance operations cannot be executed on virtual machines because they
           use BMC that are implemented on machines.
           To use the maintenance operations, management LAN must be connected to the ports
           for the management LAN of managed machines.


           IP address, an account and a password that are to be used when a management
           server connects to the BMC of managed machines must be configured in
           SigmaSystemCenter.
           For detailed instructions on how to configure the account on SigmaSystemCenter, see
           Subsection 3.8.1, "Enabling Management Function by Out-of-Band (OOB)
           Management" and 3.11.6, "Configuring          Settings   on   the   Account   Tab"   in
           SigmaSystemCenter Configuration Guide.


           The operations listed below can be executed on the window by displaying the
           maintenance operations.


            Dump
               This function obtains a dump from a management server through the BMC.
               Contents of a dump and behavior after completing Dump depend on settings on
               OSs. Therefore, the OS must be configured beforehand to use this function.
               For instructions on how to configure the OS, see Subsection 2.15.6, "Enabling
               Dump" in SigmaSystemCenter Configuration Guide.
               When executing this function on machines that are assigned to the host setting of
               the operation group, set them in the Maintenance mode before execution of this
               function.


            LED on / LED off
               This function turns on / off of the LED (of an indicator) from a management server
               through BMC on managed machines.


               When maintaining hardware of the target machine directly, this function can be
               used to make it easier to find the place where the target machine exists.
               If LED is turned on using the LED on, the LED will not be turned off automatically.


               Note: LED might be turned off automatically depending on the types of machines.
               In this case, LED will be turned off in a fixed time (about 4 minutes and 30
               seconds).


                                                         SigmaSystemCenter 2.1 Reference Guide
138
                                                            About Other Maintenance Operations



               To turn off LED, the LED off must be executed from SigmaSystemCenter.


               Note: Depending on the machine, if you have turned on the LED via
               SigmaSystemCenter, the LED is not turned off via other operations (e.g. Push
               indication switch). Also, if you have turned on the LED not using
               SigmaSystemCenter, the LED is not turned off via SigmaSystemCenter.




Part I SigmaSystemCenter Functions Reference
                                                                                              139
2.       About    Virtual                                                                      Environment
         Management




This chapter explains the functions of SigmaSystemCenter to manage virtual environments.

This chapter contains the following sections:


•    2.1        System Configuration ............................................................................................. 142
•    2.2        Creation of Virtual Machine .................................................................................... 148
•    2.3        Full Clone................................................................................................................ 160
•    2.4        HW Profile Clone .................................................................................................... 162
•    2.5        Differential Clone .................................................................................................... 164
•    2.6        Disk Clone............................................................................................................... 170
•    2.7        Machine-Specific Settings in OS Deployment ........................................................ 173
•    2.8        Image Management (Differential Clone, Disk Clone) ............................................. 184
•    2.9        Snapshot Management........................................................................................... 191
•    2.10       Virtual Machine Mobility.......................................................................................... 192
•    2.11       VM Optimized Placement Management ................................................................. 195
•    2.12       About Virtual Environment ...................................................................................... 210



Various operations are necessary to build and manage a virtual environment. Such operations can be
much easier by using SigmaSystemCenter.
SigmaSystemCenter provides functions that will be required for various stages in the life cycle of a
virtual environment, including building virtual machine servers, creating virtual machines, installing or
moving guest OS and recovering failure.
Additionally, SigmaSystemCenter supports major virtual platform software such as VMware, Hyper-V,
and XenServer.




                                                                                                                                         141
2 About Virtual Environment Management



2.1. System Configuration

2.1.1.     Hyper-V Environment
           Two methods, Hyper-V Cluster and Hyper-V single server, are provided to manage a
           Hyper-V environment.


            Hyper-V Cluster
               Manages a cluster of virtual machine servers that are managed by Microsoft
               Failover Cluster (MSFC).
               Microsoft Failover Cluster functions enable almost the same functions as other
               virtual infrastructures such as Hot Migration or Failover during failures. To manage
               target clusters from SigmaSystemCenter, register the target clusters at the
               subsystem window of the Web console.


            Hyper-V single server
               Manages Hyper-v virtual machine servers individually.
               The functions that are enabled by Microsoft Failover Cluster are not available.
               Furthermore, this management method is disabled by default.
               To enable this management method, Set Hyper-V To Be Managed on the Virtual
               view of the Web Console must be executed.


           SigmaSystemCenter can manage an environment where Hyper-V Cluster and Hyper-V
           single server are mixed.
           However, SigmaSystemCenter cannot manage one virtual machine server using both
           of two methods.
           Either of the methods must be selected.


           Functional differences between Hyper-V Cluster and Hyper-V single server are as
           follows:


           Function                         Hyper-V Cluster                Hyper-V single server

           Create VM / Delete /             Available                      Available
           Reconfigure (HW Profile / Disk
           / Differential Clone)
           Snapshot Management /            Available                      Available
           Image Management
           VM Power Control                 Available                      Available
           Move VM (Failover)               N/A                            N/A
                                            (operations from
                                            SigmaSystemCenter)


                                                              SigmaSystemCenter 2.1 Reference Guide
142
                                                                                 System Configuration


           Function                         Hyper-V Cluster                Hyper-V single server

           VM automatic Failover during     Available                      N/A
           failures                         (Provided by MSFC and SSC
                                            synchronizes with it
                                            automatically)
           VM automatic Hot Migration       Available                      N/A
           during failure Predictive
           VM Optimized Startup             Available                      Available
                                                                           (To Move to another server is
                                                                           not available.)
           VM Optimized Placement           Available                      N/A
           (Load Balancing, Power           (Only Load Balancing. Power
           Saving )
                                            Saving is not supported.)
           VM Optimized Placement           Available                      N/A
           Rule
           Virtual machine server           Available                      Available
           monitoring                       (MSFC automatically detects)
           VM monitoring                    Available                      N/A
                                            (MSFC automatically detects)
           Virtual Machine                  Available                      Available
           Server HW Predictive                                            (To move automatically by a
           Monitoring                                                      policy is not available.)
           Patch distribution to virtual    Available                      Available
           machine servers
           patch application distribution   Available                      Available
           to virtual machines
           Virtual machine server           N/A                            N/A
           Provisioning


           Microsoft Failover Cluster functions enable monitoring of virtual machine servers and
           virtual machines, and VM automatic Failover during failures.
           If Microsoft Failover Cluster detects any errors, SigmaSystemCenter can recognize the
           errors, record the events on operations log, update status information of virtual
           machine servers and virtual machines, and start policies.
           If a failure occurs, Microsoft Failover Cluster moves a virtual machine running on the
           virtual machine server where the failure occurred to another virtual machine server
           automatically. (This operation is called Failover.)
           SigmaSystemCenter detects the operations automatically and updates the
           configuration information database so that the actual situation and the configuration
           database will not be inconsistent.




Part I SigmaSystemCenter Functions Reference
                                                                                                    143
2 About Virtual Environment Management




2.1.2.     System Configuration of Hyper-V Cluster
           First, this subsection provides an explanation about system configuration of Hyper-V
           Cluster.


           A system would be composed of a management server of SigmaSystemCenter, a
           domain controller and virtual machine servers which are the management targets.
           Additionally, storage that is connected to SAN network is required to build a Cluster
           Shared Volumes (CSV). SigmaSystemCenter does not support CSV or cluster disk
           configuration with iSCSI. SigmaSystemCenter manages virtual machine servers which
           are the management targets as Hyper-V Cluster.


           Each of the virtual machine servers has a x64 processor. The functions of Intel VT and
           Hardware DEP are required. Further, we recommend that all virtual machine servers
           have the same model processors.


           Prepare two networks; one is LAN for management, the other is LAN for virtual
           machines. LAN for management is used for controlling or monitoring virtual machine
           servers. LAN for virtual machines is used for controlling virtual machines. Connect the
           management server, each of the virtual machine servers, and the domain controller to
           the both networks.
           There are two ways for LAN for Operation; one is to prepare another network, the other
           is to share LAN for virtual machines.


           The OS of a management server must be Windows Server 2008 R2. Install all products
           of SigmaSystemCenter to the management server. System Center Virtual Machine
           Manager (SCVMM) is unnecessary. SigmaSystemCenter can control each of Hyper-V
           virtual machine servers without SCVMM.


           Install Windows Server 2008 R2 to each of virtual machine servers and add a Hyper-V
           role and the Failover Clustering feature. In addition, install Client Service for DPM and
           NEC ESMPRO Agent as well.


           Each of the virtual machine servers must belong to the same Active Directory domain.




                                                          SigmaSystemCenter 2.1 Reference Guide
144
                                                                                 System Configuration




           Second, this subsection provides an explanation about configuration of a virtual
           machine server.


           The term "partition" is used to refer to virtual machines in Hyper-V. "Partition" is divided
           into the following two types:


            A partition for Hyper-V Management. It is called "parent partition". It will be called
             "virtual machine server" which is a term of SigmaSystemCenter in the following
             explanation.
            A partition where a normal guest OS runs. It is called “child partition”. It will be
             called "virtual machine" which is a term of SigmaSystemCenter in the following
             explanation.


           Client Service for DPM and NEC ESMPRO Agent must be installed on a virtual
           machine server (a parent partition).


           Hyper-V integration services and Client Service for DPM must be installed on each
           virtual machine (child partition).
           Virtual NIC of each virtual machine (child partition) must be connected to LAN for the
           virtual machines through virtual networks.

Part I SigmaSystemCenter Functions Reference
                                                                                                    145
2 About Virtual Environment Management




2.1.3.     Configuring Cluster in Hyper-V Environment
           This subsection provides the flow of Hyper-V from creation to registration to
           SigmaSystemCenter with explanation. For the detailed procedure, refer to Hyper-V
           documents of Microsoft Corporation and SigmaSystemCenter Configuration Guide.
           The explanation is provided on the assumption that OS and SigmaSystemCenter have
           already been installed on a management server and a domain controller.


           1.   Build Active Directory domain on a server of a domain controller. A DNS server
                must be enabled.
           2.   Building a virtual machine server
                1.   Install Windows server 2008 R2.
                2.   Join the domain.
                3.   Add Hyper-V role using Server Manager.
                4.   Add "Failover Clustering" feature using Server Manager.
           3.   Building storage LUNs and assignment
                1.   Build LUNs that is to be a shared storages on the storage and assign them to
                     each virtual machine server. LUNs must be accessible to all the virtual
                     machine servers.
           4.   Setting up a Cluster (on one virtual machine server)
                1.   Create a cluster using Failover Cluster Manager. In the cluster creation, add
                     all virtual machine servers that compose the cluster as nodes of the cluster.

                                                          SigmaSystemCenter 2.1 Reference Guide
146
                                                                             System Configuration

                2.   Make disks that are to be the shared storages online. Create volumes and
                     format them with NTFS.
                3.   Add the formatted volumes to Storage using Failover Cluster Manager.
                4.   Enable Cluster Shared Volumes of the cluster using Failover Cluster
                     Manager.
                5.   Add the volumes that were added to Storage to Cluster Shared Volumes using
                     Failover Cluster Manager. The volumes that are added in this procedure are
                     to be CSV.
           5.   Operations on SigmaSystemCenter
                1.   Register the cluster that was created in the above procedures to
                     SigmaSystemCenter as a "Hyper-V Cluster" subsystem from the Subsystem
                     window. Set the name or an IP address of the cluster as the host name.




Part I SigmaSystemCenter Functions Reference
                                                                                                147
2 About Virtual Environment Management



2.2. Creation of Virtual Machine
           To build a new virtual environment, many things related to virtual machine creation
           must be considered, which involves capacity and performance of destination virtual
           machine servers and Datastores, how to distribute images to virtual machines and how
           to configure guest OS. Therefore, it is a difficult problem for many IT engineers to build
           a virtual environment running with stability as required. SigmaSystemCenter's virtual
           machine creation function enables quick building of highly advanced virtual
           environments with following advantages:


           1.   Several image distribution methods with various advantages are prepared. They
                can be selected flexibly according to your system operation and building.
                SigmaSystemCenter obtains information and images from a master VM and
                creates virtual machines based on the information and the images.
                SigmaSystemCenter manages the information obtained from a master VM in
                templates. Management methods of images are different depending on types of
                templates.


           2.   Resource assignment to virtual machines can be defined in detail according to the
                usage.
                Resource assignment to devices including virtual CPU and a memory that
                compose virtual machines can be defined in Machine Profile. You can configure
                devices according to levels, such as a group or a model.


           3.   A large quantity of virtual machines can be designed and created easily because a
                destination to allocate virtual machines is decided automatically and appropriately.
                Destination virtual machine servers and Datastores to allocate virtual machines
                are decided automatically according to information from VM server models that are
                set to an operation group and templates. VM Optimized Creation function balances
                virtual machines on the destination virtual machine servers and Datastores.


           4.   Guest OS information on virtual machines can be configured and managed easily.
                Guest OS information including a host name and an IP address can be managed
                in operation group settings and host settings. Each piece of guest OS information
                can be configured or created at the same time by using ssc commands.


           In addition, SigmaSystemCenter’s system operating action such as action to cope with
           failure using policies can be configured at the same time as the above settings.
           Therefore, you can proceed to system operation quickly after building a virtual
           environment with SigmaSystemCenter.


           The following figure is an explanation of a basic operational flow of creating virtual
           machines and how to use the virtual machines.



                                                          SigmaSystemCenter 2.1 Reference Guide
148
                                                                       Creation of Virtual Machine




2.2.1.     Templates
           Templates are used for creating virtual machines. A template is composed of
           information involving a virtual machine's hardware settings and OS images. Installing
           operations or configuring operations does not have to be repeated by using templates.
           Templates are created from a virtual machine that is to be used as a master VM.
           Therefore, virtual machines that are created from the same template are the same as
           the master VM in basic information involving images and settings. Specific information
           for each virtual machine is configured based on the information of Machine Profile and
           guest OS settings.




Part I SigmaSystemCenter Functions Reference
                                                                                              149
2 About Virtual Environment Management



           Methods of managing images that are created from a master VM are different
           depending on the types of templates. Differential Clone and Disk Clone can manage
           several generations of the images that you create after updating operations such as
           patch application on the same template.


           The following four types of template methods can be used in SigmaSystemCenter.


           Template type          Operability   Performance     Capacity     Note
                                                of   creating
                                                virtual
                                                machines

           Full Clone             ★★★           ★★              ★★           Uses a standard template of virtual
                                                                             platform software. Use this
                                                                             template in VMware vCenter
                                                                             Server Management basically.
           HW Profile Clone       ★             ★               ★★           Virtual machines can be created
                                                                             as well as physical machines by
                                                                             using DPM's Back up and Restore
                                                                             function.
           Differential Clone     ★             ★★★             ★★★          Capacity is small and creation time
                                                                             is short because only difference
                                                                             information from a base is created.
                                                                             However, management of master
                                                                             VMs' snapshots is necessary and
                                                                             the management costs are high.
                                                                             Furthermore, the additional license
                                                                             for this template is required.
           Disk Clone             ★★            ★               ★★           Generational management of
                                                                             images can be done easily by
                                                                             using the image management
                                                                             function. Unlike Differential Clone,
                                                                             snapshots of master VMs are
                                                                             unnecessary, so management of
                                                                             this template is easy.


           Refer to the following table for the availability of templates in virtual environments.
           Information in brackets is the products that configure OS specific information. Bold font
           indicates what is recommended and italic font is what is not recommended.


           Environment       of   Full Clone          HW        Profile    Differential        Disk Clone
           a   management                             Clone                Clone
           target

           VMware (vCenter        Available           Available (DPM)      Available           Available (DPM)
           Server                 (vCenter Server)                         (vCenter Server)
           Management)
           Standalone ESXi        Unavailable         Available (DPM)      Available (DPM)     Available (DPM)
           XenServer              Unavailable *1      Unavailable          Available (DPM)     Available (DPM)
                                                                           *2
           Hyper-V Cluster        Unavailable         Available (DPM)      Available (DPM)     Available (DPM)

                                                                SigmaSystemCenter 2.1 Reference Guide
150
                                                                             Creation of Virtual Machine


           Hyper-V single     Unavailable         Available (DPM)     Available (DPM)      Available (DPM)
           server
           *1                 Unavailable to create virtual machines using Create and Assign Machine on
                              the Operation view. Virtual machines can be created on the Virtual view but
                              the guest OS's specific information cannot be configured.
           *2                 Differential Clone is recommended owing to its advantage for XenServer in
                              terms of performance. However, it has little advantage in terms of capacity.




2.2.2.     Customization of Devices Assigned For VM (Machine
           Profile)
           Resource assignment for the devices that compose virtual machines can be
           customized on SigmaSystemCenter. The device customization function of
           SigmaSystemCenter makes it easy to define various specifications of virtual machines
           according to the usage.


           The following devices can be defined using the device customization function. Devices
           other than the followings must be assigned to a master VM in advance using virtual
           platform products.


            CPU
            Memory
            Network
            System Disk
            Extended Disk


           Device settings can be defined and changed by the following operations.


           1.   Machine Profile
                Machine Profile is used to define hardware specifications of virtual machines that
                are to be created or to be reconstructed. It can be configured on the Operation
                view. When the following operations are executed, virtual machines with the
                hardware specifications that are defined in Machine Profile are created.


                •   Create and Assign Machine
                •   Reconstruct


           2.   Edit Virtual Machine
                The resource assignment for each device that is implemented on created virtual
                machines can be changed by operating Edit Virtual Machine. Execute the
                operations on the Virtual view.



Part I SigmaSystemCenter Functions Reference
                                                                                                        151
2 About Virtual Environment Management




           Machine Profile can be defined in each of the levels of an operation group, such as
           groups, models, and hosts. Therefore, Machine Profile can be operated flexibly
           according to requirements of the business. Hardware specs that are to be applied to
           several virtual machines widely should be configured on the group level. Hardware
           specs that are to be applied to virtual machines individually should be configured on the
           host level. A host and a model are associated not at the timing of creating the model,
           but at the timing of creating a new virtual machine. Therefore, several models can be
           prepared with hardware spec profiles for various situations. An appropriate profile will
           be selected from among the prepared hardware profiles depending on the situation of
           when creating virtual machines.


           In addition, each device can be configured depending on levels. Network settings that
           are to be used commonly in all levels should be configured on upper levels. On the
           other hand, devices that are to be customized depending on CPU or a memory should
           be configured in lower levels.


           Both Machine Profile and Edit Virtual Machine can be used regardless of template
           types.


           Machine Profile can be configured on models of which the type is VM group.


           The following setting items in old versions are integrated into Machine Profile setting.


            Setting on the Network tab on the Model (SigmaSystemCenter 2.1 Update 2 or
             before)



                                                           SigmaSystemCenter 2.1 Reference Guide
152
                                                                        Creation of Virtual Machine

               If SigmaSystemCenter is updated from SigmaSystemCenter 2.1 Update 2 or
               before to SigmaSystemCenter 2.1 Update 3 or later, the Network Setting of the
               Model's Machine Profile setting are set on the Network tab on the Model.


           Machine Profile and Edit Virtual Machine can be used in all of the virtual platform
           software, VMware, Hyper-V and Xen Server.


           Machine Profile can be used in all of the distribution methods, Full Clone、HW Profile
           Clone, Differential Clone and Disk Clone.



2.2.3.     Usage Example of Machine Profile
           The following figure is an example of a virtual machine group with four Machine
           Profiles: Network Profile, Profile A, Profile B, and Profile C.


           Define a common Network Profile for the entire group as a network definition. Assume
           that three levels of operation load are defined for CPU, memory, and a disk. Define
           three machine profiles as hardware specs that can cope with each of the three levels:
           Profile A, Profile B and Profile C.
           Set template_2003 with the OS image of Windows 2003 in VMGroup. Assume that
           each virtual machine under the virtual machine group works based on the same OS
           image.


           Define a minimum spec for Profile A (Machine Profile) to be used as a basic setting
           available in many operations and set it on VMGroup which is the top group. Set
           Network Profile on VMGroup as a common network setting for the entire group.
           Prepare two models under VMGroup: Small Model and Large Model,. Configure Small
           Model so that Profile A is used as a setting of VMGroup which is the upper group. Set
           Profile B (Machine Profile) on Large Model. High specifications to cope with high load
           operations are defined in Profile B. Configure the network setting of both models so
           that the VMGroup setting will be used.
           Do not define Machine Profile on the host settings: VMHost1 to VMHost6, so that the
           setting of upper levels will be used. When executing Create and Assign Machine on
           these hosts, select either of Small Model or Large Model considering prospective loads
           on the virtual machines to be created.
           Set Profile C (Machine Profile) on Special Host that is to be loaded extremely high. A
           special hardware spec is defined in Profile C.


           Do not define the network setting on every host so that upper settings can be used.




Part I SigmaSystemCenter Functions Reference
                                                                                                 153
2 About Virtual Environment Management




2.2.4.     Machine Profile Definitions in Levels
           Machine Profile can be defined in each level of groups, models and hosts. Definitions
           of lower levels are prior to those of upper levels. Whether to define devices at each
           level or not can be configured according to each of the devices, CPU, memories,
           networks, system disks and extended disks.


           You can check the result of the device definitions on the Machine Profile setting of
           hosts, the result that which Machine Profiles is used to create virtual machines.


            Group
               If there is no definition in models or hosts under a group, the definition of a group’s
               Machine Profile is used when creating virtual machines. The setting of the group is
               used as the default setting for models and hosts. If any template is set on a group,
               the setting of the template is used as the default setting for the group.
               If a template is assigned not to a group but to lower models, the template setting is
               not used as the default setting for the group. In this case, settings can be


                                                           SigmaSystemCenter 2.1 Reference Guide
154
                                                                          Creation of Virtual Machine

               configured easily referring to the information of the model setting to which the
               template is assigned.


            Model
               If no Machine Profile is defined in individual hosts on the host setting, a model
               setting which is to be specified at the timing of creating virtual machines is used as
               the Machine Profile for the virtual machines. The setting of the specified model can
               be used as the default setting on a Machine Profile setting window of hosts or
               groups.
               The default values of the model setting are set in groups or templates. If both a
               group and a template exist, the group's values are used as the default values.


            Host
               Define Machine Profiles for hosts individually. The default values that are defined
               in the host setting are surely used as a virtual machine's Machine Profile. If there is
               no definition in a host, the definition of a model's Machine Profile that was selected
               while creating virtual machines is used. If the selected model has no definition, the
               definition of upper groups or templates is used. If both a group and a template exist,
               the group's values are the default values.


            If no definitions in each level
               Each of the settings of devices in use on the templates is referred to when creating
               virtual machines.



2.2.5.     CPU Settings
           Configure the number or the ability of CPU that is to be assigned to virtual machines.


            The number of CPU
               Specify the number of virtual CPUs that are to be implemented on virtual
               machines.


            CPU Share
               Select the amount of the CPU resource allocation.
               Select from the followings. An arbitrary number can also be configured.


               •    4000 Highest
               •    2000 High
               •    1000 Normal
               •    500 Low
               •    250 Lowest



Part I SigmaSystemCenter Functions Reference
                                                                                                    155
2 About Virtual Environment Management



               SigmaSystemCenter uses the result of the following calculations when controlling
               each virtual platform product.


               VMware                   The set value * the number of CPU

               Hyper-V                  The set value / 10

               XenServer                The set value * 256 / 100



               Each of the virtual platform products decides the final amount of CPU resource
               assignment considering the number of virtual machines running on a virtual
               machine server in addition to the value of CPU Share. Therefore, the actual
               capacity of assignment may be bigger or smaller than the CPU Share value. Use
               CPU Share value as a relative value among virtual machines running on a virtual
               machine server.


            CPU Limit
               Configure the upper limit of CPU resource assignment. CPU Share setting is used
               as a relative value among other virtual machines' CPU Share setting. On the other
               hand, CPU resource is not assigned with exceeding the value of CPU Limit setting.
               CPU Limit setting is not used for XenServer.
               SigmaSystemCenter uses the result of the following calculations when controlling
               each virtual platform product.


               VMware                   Use the set value without change.

               Hyper-V                  The set value * 100 / (the number of CPU * the host clock frequency
                                        (MHz))


               If "0" is specified, CPU has no limit.



2.2.6.     Memory Settings
           Configure a memory to be assigned to virtual machines.


            Memory Size
               Specify a capacity of a memory to assign virtual machines in MB unit.


            Memory Share
               This setting is available only for VMware. This item cannot be configured in
               Machine Profile. This item can be configured only on the Edit Virtual Machine. The
               following four settings can be specified.



                                                             SigmaSystemCenter 2.1 Reference Guide
156
                                                                         Creation of Virtual Machine



               •    High : Calculates using the Memory Size setting as follows.
                    The specified Memory Size * 20.
               •    Standard : Calculates using the Memory Size setting as follows.
                    The specified Memory Size * 10.
               •    Low : Calculates using the Memory Size setting as follows.
                    The specified Memory Size * 5.
               •    Manual setting : Specify a numerical value.



2.2.7.     Network Settings
           Configure a virtual NIC to be assigned to virtual machines and the name of the
           destination to which the virtual NIC connects. Virtual NICs can be configured from #1 to
           #4. Network settings cannot be changed on the Edit Virtual Machine.


           A destination to which virtual NIC connects must be created on a virtual machine server
           using virtual platform software. The terms and the forms to define a destination to
           which virtual NIC connects are different according to virtual platform products.


            VMware
               Set a name of the destination port group.


            Hyper-V
               Set the name composed of the combination of the destination virtual network and
               VLAN as below:


               NetworkName-VLAN:VlanId


               •    NetworkName: Set the name of the destination virtual network
               •    -VLAN: The fixed string
               •    VlanID: Set the ID of the VLAN to be assigned to the virtual NICs. If you do not
                    set the VLAN ID, the fixed string, “NONE” is set.


            XenServer
               Set the name of the destination network.


           SigmaSystemCenter displays a list of destinations on the setting screen so that a
           destination can be configured easily. A destination can be selected from the list when
           the following settings are done on the destination.


            A destination to which a virtual NIC connects is already created on a virtual
             machine server using virtual platform software.

Part I SigmaSystemCenter Functions Reference
                                                                                                 157
2 About Virtual Environment Management



            A model to which a virtual machine server belongs is already configured on the
             setting of a VM Server model to which the virtual machines to be created belong.
            Templates are already created and the templates are already added to the
             software setting.


           If the above conditions are not satisfied, it is not displayed in the list because the
           information of the destination cannot be obtained. If a target destination is not displayed
           in the list, the name of the destination must be entered manually.



2.2.8.     System Disk Settings
           Define a disk in which a guest OS is to be installed. The setting cannot be changed on
           the Edit Virtual Machine.


            Type
               Select either Thick / Thin. This setting is disabled in Differential Clone of Hyper-V.
               •    Thick: Creates a disk of which the size is specified when created.
               •    Thin: Disks will be assigned dynamically as necessary. The specified size is
                    used as the upper limit when assigning the disk.


            Size
               Displays the size of the system disk in MB unit. If the information cannot be
               obtained from a template, the information is not displayed. This item cannot be
               changed.


            Destination Datastore
               Select the Datastore where the creating disk is to be stored. This item does not
               have to be selected. If this item is not selected, it will be selected automatically
               when creating the virtual machine.



2.2.9.     Extended Disk Settings
           Define a disk for data.


            Type
               Select either Thick / Thin.
               •    Thick: Creates a disk of which the size is specified when created.
               •    Thin: Disks will be assigned dynamically as necessary. The size entered here
                    is used as the upper limit when assigning the disk.




                                                           SigmaSystemCenter 2.1 Reference Guide
158
                                                                        Creation of Virtual Machine



            Size
               Displays the size of the system disk in MB unit. If the information cannot be
               obtained from a template, the information is not displayed. This item cannot be
               changed.


            Destination Datastore
               Select the Datastore where the creating disk is to be stored. This item does not
               have to be selected. If this item is not selected, it will be selected automatically
               when creating the virtual machine.




Part I SigmaSystemCenter Functions Reference
                                                                                                159
2 About Virtual Environment Management



2.3. Full Clone
           You can create virtual machines by using Full Clone.
           Full Clone creates virtual machines using each of virtual platform software's standard
           templates that were created from a master VM.


           Also, you can load each of virtual platform software's standard templates to
           SigmaSystemCenter and use them on the SigmaSystemCenter.


           Full Clone creates virtual machines by copying images of standard templates without
           change.
           Information of guest OS such as a host name and an IP address can be set from each
           of virtual platform software.


           Full Clone is available in VMware and XenServer. The function to set information of
           guest OS such as a host name and an IP address, however, is available only in
           VMware. If you are using Windows, use Sysprep to set information of guest OS.
           Sysprep is executed from vCenter Server.
           If you are using XenServer, information of guest OS such as a host name and an IP
           address must be changed manually after creating a virtual machine.




                                                        SigmaSystemCenter 2.1 Reference Guide
160
                                                                                          Full Clone




2.3.1.     How to Create Full Clone
           This subsection explains the operational flow of creating a Full Clone template that can
           be used in the VMware environment (except Standalone ESXi) and Xen environment,
           registering the template as distribution software to SystemProvisioning, and creating an
           active machine in a group.


           1.   Setting up a master VM
                To create a template, create a source virtual machine of a template, a master VM,
                on a virtual machine server. Set up the software environment, including an OS and
                all the necessary applications, for the machine to create.


           2.   Creating a template
                Create a Full Clone template from SystemProvisioning. You can also create a
                template in vCenter Server or XenCenter and use the template by collecting the
                information of the template in vCenter Server or XenCenter.


           3.   Registering the template to a group (In the VMware environment)
                Register the template to be a source of a machine to activate in a group to the
                group.
                If you are operating the Xen environment, you do not need to execute this
                operation.


           4.   Configuring detailed information of a model
                Configure detailed information to create a virtual machine.


           5.   Creating a virtual machine and activating the machine in the group
                If you are operating the VMware environment, create an active machine in a group
                by executing Create and Assign Machine, based on the template registered in the
                group.
                Machine-specific information, including a host name and IP address, are reflected
                to the created virtual machine. Register the information as Host Setting in the
                group.


                If you are operating the Xen environment, you cannot create a virtual machine by
                Create and Assign Machine. In addition, machine-specific information, including a
                host name, IP address, and administrator password, cannot be reflected, so you
                need to create a virtual machine in the Virtual view and register the machine in a
                group.




Part I SigmaSystemCenter Functions Reference
                                                                                                161
2 About Virtual Environment Management



2.4. HW Profile Clone
           HW Profile Clone creates virtual machines in the following flow.


            Creates an empty VM using HW Profile information that was obtained from a
             master VM.
            Restores a base image to the empty VM.


           HW Profile Clone uses DeploymentManager's function to backup / restore base images.
           Therefore, HW Profile Clone templates must be used with DeploymentManager's
           scenarios.


           If you are using Windows, use Sysprep to set information of guest OS. Sysprep is
           executed from DeploymentManager.


           HW Profile Clone can be used in Hyper-V and VMware.




                                                         SigmaSystemCenter 2.1 Reference Guide
162
                                                                                   HW Profile Clone




2.4.1.     How to Create HW Profile Clone
           This subsection explains the operational flow of creating a HW Profile Clone template
           that can be used in the VMware environment (recommended for Standalone ESXi) and
           Hyper-V environment, and a restore scenario of DPM, registering the template as
           distribution software to SystemProvisioning, and creating an active machine in a group.


           1.   Setting up a master VM
                To create a template, create a source virtual machine of a template, a master VM,
                on a virtual machine server. Set up the software environment, including an OS and
                all the necessary applications, for the machine to create.


           2.   Creating a scenario
                Create a restore scenario of DPM to deploy the OS and applications on the master
                VM to virtual machines.


           3.   Creating a template
                Create a HW Profile Clone template from SystemProvisioning.


                Note:
                ▪ A HW Profile Clone template indicates a virtual machine used as a source of
                clone when a virtual machine is created.
                ▪ A HW Profile Clone template is a concept of SystemProvisioning; the template is
                not created on ESX, ESXi, or Hyper-V.


           4.   Registering the template and scenario to a group
                Register the template and scenario to the operation group as distribution software.


           5.   Configuring detailed information of a model
                Configure detailed information to create a virtual machine.


           6.   Creating a virtual machine and activating the machine in the group
                Create an active machine in a group by executing Create and Assign Machine,
                based on the template registered in the group.
                Machine-specific information, including a host name and IP address, are reflected
                to the created virtual machine. Register the information as Host Setting in the
                group.




Part I SigmaSystemCenter Functions Reference
                                                                                                163
2 About Virtual Environment Management



2.5. Differential Clone
           You can create virtual machines by using Differential Clone.
           Differential Clone creates virtual machines using each basic image that was created
           from snapshots of a master VM. Basic images that were created from snapshots of a
           master VM are called Replica VM.
           A virtual machine that is created using Differential Clone retains only difference
           information between a replica VM and the virtual machine. Therefore, Differential Clone
           can reduce the usage of a disk and create virtual machines in a shorter time comparing
           to other Clone methods. Additionally, update operations of multiple virtual machines
           including patch application can be executed easily and quickly by using the
           management function for images and snapshots and the Reconstruct function.


           Virtual machines that were created using Differential Clone are related to replica VMs.
           Therefore, there is no influence on the virtual machines even if the master VM is
           updated.
           Also, you can create multiple virtual machines based on the same replica VM.


           In the case of Windows, Sysprep is used to set guest OS information involving a
           computer name and an IP address. If you are using VMware (vCenter Server
           Management), Sysprep is executed from vCenter Server. If you are using an
           environment other than the VMware (vCenter Server Management) environment,
           Sysprep is executed from DeploymentManager. If you are using an environment other
           than the VMware (vCenter Server Management) environment, Sysprep automatic
           execution scenario must be configured to be executed when creating a replica.


           Differential Clone can be used in VMware, Hyper-V and XenServer.
           To use Differential Clone, Differential Clone option is necessary in addition to the target
           licenses.




                                                           SigmaSystemCenter 2.1 Reference Guide
164
                                                                                   Differential Clone




2.5.1.     How to Create Differential Clone
           This subsection explains the operational flow of creating a Differential Clone template
           that can be used in VMware environments, Xen environments and Hyper-V
           environments, registering the template as distribution software to SystemProvisioning,
           and creating an active machine in a group.


           1.   Setting up a master VM
                To create a template, create a source virtual machine of a template, a master VM,
                on a virtual machine server. Set up the software environment, including an OS and
                all the necessary applications, for the machine to create.


           2.   Registering the master VM in DPM
                Register the master VM in DPM. If the virtual machine server is managed by
                vCenter Server, this procedure is unnecessary, so proceed to Procedure 6.


           3.   Creating a Disk Duplication Parameter File of DPM for the master VM
                Create a Disk Duplication Parameter File of DPM for the master VM.


           4.   Preparing for running Sysprep automatically
                Prepare for running Sysprep automatically.


           5.   Configuring to run Sysprep automatically towards the master VM
                Configure to run Sysprep automatically towards the master VM.


           6.   Creating a snapshot after turning Off the master VM
                Turn Off the master VM and create a snapshot.


           7.   Creating a template
                Create a Differential Clone template from SystemProvisioning.


                Note:
                ▪ A Differential Clone template indicates a virtual machine used as reference data
                when a virtual machine is created.
                ▪ A Differential Clone template is a concept of SystemProvisioning; the template is
                not created on an ESX, ESXi, or Hyper-V.


           8.   Registering the template to a group
                Register the template to the operation group as distribution software.




Part I SigmaSystemCenter Functions Reference
                                                                                                 165
2 About Virtual Environment Management



           9.   Configuring detailed information of a model
                Configure detailed information to create a virtual machine.


           10. Creating a virtual machine and activating the machine in the group
                Create an active machine in a group by executing Create and Assign Machine,
                based on the template registered in the group.
                Machine-specific information, including a host name and IP address, are reflected
                to the created virtual machine. Register the information as Host Setting in the
                group.



2.5.2.     Revert
           Management of created virtual machines' images is important when using Differential
           Clone.
           Differences between a master VM and virtual machines are small right after creating
           virtual machines. The capacity of OS differences is also small. As the virtual machines
           are being used, the capacity of OS differences grows. Therefore, OS differences
           capacity must be reduced to the initial status at regular intervals.
           To reduce OS differences capacity, execute Revert. Revert can be executed regularly if
           the OS scheduling function and ssc commands are combined.
           Extended disks remain unaffected by executing Revert operation so that users do not
           lose their data. The UUIDs of virtual machines also do not change and they are
           managed as the same machines after executing Revert operation.




                                                          SigmaSystemCenter 2.1 Reference Guide
166
                                                                                Differential Clone




2.5.3.     Reconstruct
           Another function is Reconstruct.
           Behavior of Reconstruct is as follows:
            First, executes system changes such as patch application towards a master VM.
            Second, creates a snapshot. After that, creates another replica VM from the
             snapshot.
            Finally, makes the replica VM as a new master image of virtual machines.


           Snapshots creation and settings of Reconstruct’s behavior can be executed at one time
           as a common operation for virtual machines that have the same template setting.
           Therefore, your systems can be updated efficiently.
           Reconstruct recreates virtual machines. Therefore, if Reconstruct is executed, OS
           differences will return to the initial status as executing Revert.
           Extended disks remain unaffected by executing Reconstruct operation so that users do
           not lose their data. The UUIDs of virtual machines also do not change and they are
           managed as the same machines after executing Reconstruct operation.




Part I SigmaSystemCenter Functions Reference
                                                                                              167
2 About Virtual Environment Management




2.5.4.     How to Use Differential Clone When Creating a New
           Master VM
           A basic operational flow of creating virtual machines using Differential Clone in a new
           environment is as the following figure. For procedures including the Sysprep operations,
           see Subsection 2.7.7, ”How to Use Sysprep - Disk Clone, Differential Clone (DPM) -.”


           Further, do not create images with assigning an extended disk to a master VM.
           Executing Differential Clone with assigning an extended disk to a master VM is not
           supported.




                                                         SigmaSystemCenter 2.1 Reference Guide
168
                                                                                    Differential Clone




2.5.5.     How to Use Differential Clone When Reconstructing
           A basic flow of executing Reconstruct is as the following figure.


           New templates do not have to be created because already created templates are
           available, but new images must be created.


           When executing Reconstruct towards multiple virtual machines simultaneously as the
           following figure, execution speeds and processing loads can be adjusted at the settings
           below.


            Max Number of Concurrent Processing: Processing time might be reduced if
             processes are multiplied.
            Interval: If there is a possibility that processing loads of Reconstruct influence the
             operation of your system, configure this setting to adjust loads of virtual machine
             servers.




Part I SigmaSystemCenter Functions Reference
                                                                                                  169
2 About Virtual Environment Management



2.6. Disk Clone
           You can create virtual machines by using Disk Clone.
           Disk Clone creates virtual machines using each basic image that is created from a
           master VM. Basic images that are created from a master VM are called Replica VM.
           Unlike virtual machines that were created using Differential Clone, virtual machines that
           are created using Disk Clone do not retain differences between a replica VM and the
           virtual machines. They are created by copying a replica VM's image without change.
           Disk Clone does not have advantages that Differential Clone has. For example,
           Differential Clone can reduce disk usage by sharing the basic images with other virtual
           machines, but Disk Clone cannot. However, Disk Clone has its own advantage that
           virtual machines that are created using Disk Clone are hardly influenced from other
           virtual machines' behavior because the images are owned individually.


           If you create a replica VM that is to be the basis of virtual machines using Disk Clone,
           the replica VM will be different from the master VM. Therefore, the replica VM is not
           influenced even if the master VM is updated.
           There is no influence on the virtual machines even if the master VM is updated.
           If you are using Windows, use Sysprep to set guest OS information such as a computer
           name and an IP address. Sysprep is executed from DeploymentManager. Sysprep
           automatic execution scenario of DeploymentManager must be configured to be
           executed when creating a replica.


           Disk Clone can be used in Hyper-V, XenServer, and Standalone ESXi.
           If you are using VMware (vCenter Server Management), use Full Clone. We do not
           recommend that use Disk Clone in VMware (vCenter Server Management) because
           there are some disadvantages. For example, Disk Clone templates cannot be used in
           vCenter Server and Disk Clone's performance of creating virtual machine is inferior to
           Full Clone.




                                                          SigmaSystemCenter 2.1 Reference Guide
170
                                                                                         Disk Clone




2.6.1.     How to Create Disk Clone
           This subsection explains the operational flow of creating a Disk Clone template that can
           be used in the VMware environment (recommend for ESXi), Xen environment, and
           Hyper-V environment, registering the template as distribution software to
           SystemProvisioning, and creating an active machine in a group.


           1.   Setting up a master VM
                To create a template, create a source virtual machine of a template, a master VM,
                on a virtual machine server. Set up the software environment, including an OS and
                all the necessary applications, for the machine to create.


           2.   Registering the master VM in DPM
                Register the master VM in DPM.


           3.   Creating a Disk Duplication Parameter File of DPM for the master VM
                Create a Disk Duplication Parameter File of DPM for the master VM.


           4.   Preparing for running Sysprep automatically
                Prepare for running Sysprep automatically.


           5.   Configuring to run Sysprep automatically towards the master VM
                Configure to run Sysprep automatically towards the master VM.


           6.   Creating a template
                Create a Disk Clone          template    with   a   master    VM   selected   from
                SystemProvisioning.


                Note:
                ▪ A Disk Clone template is a template that shows a virtual machine to be reference
                of a creating virtual machine.
                ▪ A Disk Clone template is a concept of SystemProvisioning; the template is not
                created on a XenServer, ESX, ESXi, or Hyper-V.


           7.   Registering the template to a group
                Register the template to the operation group as distribution software.


           8.   Configuring detailed information of a model
                Configure detailed information to create a virtual machine.




Part I SigmaSystemCenter Functions Reference
                                                                                                  171
2 About Virtual Environment Management



           9.   Creating a virtual machine and activating the machine in the group
                Create an active machine in a group by executing Create and Assign Machine,
                based on the template and scenario registered in the group.
                Machine-specific information, including a host name and IP address, are reflected
                to the created virtual machine. Register the information as Host Setting in the
                group.




                                                         SigmaSystemCenter 2.1 Reference Guide
172
                                                         Machine-Specific Settings in OS Deployment



2.7. Machine-Specific                                    Settings               in          OS
     Deployment

2.7.1.     About Sysprep
           Sysprep (System Preparation Utility) is the tool that is provided from Microsoft
           Corporation for Windows OS deployment.
           If you duplicate a master machine's image on multiple machines, the OSs of the
           duplicated machines will be available by using Sysprep.


           The basic processes of Sysprep are as follows:
           1.   Removes machine-specific information of the destination of a deployment.
           2.   Re-registers or initializes machine-specific information of the destination machine
                of a deployment.


           Machine-specific information is as follows:


            Computer name
            IP address
            Product Key
            The security identifier (SID)


           SigmaSystemCenter uses Sysprep of the following products which have an image
           duplication function and a deployment function. Usage is different depending on the
           products.


            DeploymentManager (DPM)
            vCenter Server (VC)


           Products used by SigmaSystemCenter are different depending on management targets
           as follows:


           Product                      Types of management targets

           DeploymentManager            Physical machines
                                        Hyper-V virtual machines
                                        XenServer virtual machines
                                        Standalone ESXi virtual machines
                                        When using HW Profile Clone



Part I SigmaSystemCenter Functions Reference
                                                                                                173
2 About Virtual Environment Management


           Product                      Types of management targets

           vCenter Server               VMware virtual machines (except for when using HW Profile Clone
                                        and Disk Clone)

           The basic procedure to execute duplication and deployment operations with Sysprep is
           as follows. Some of the steps from 1 to 5 in the basic procedure must be executed
           manually or are executed automatically, depending on types of management targets.


           1.   Create a master machine.
           2.   Prepare for Sysprep execution on the master machine. Execute Sysprep on the
                destination of the deployment to delete machine-specific information of the master
                machine.
           3.   Create an image of the master machine to be the original of the duplication.
           4.   Prepare for operations of duplication and deployment on DPM/VC.
           5.   Execute a duplication operation. The machine-specific information of the master
                machine will be reconfigured on the destination of the deployment.


           The number of Sysprep executions is limited according to the licenses. Make sure not
           to execute the disk duplication toward the master machine several times (Up to 3 times
           allowed for Volume license keys of Windows Vista or later). For information on how to
           prevent Sysprep from being executed several times in operations, refer to Subsection
           2.7.5, "How to Use Sysprep - OS Deployment, HW Profile Clone (DPM) -".




                                                          SigmaSystemCenter 2.1 Reference Guide
174
                                                       Machine-Specific Settings in OS Deployment




2.7.2.     Machine-specific settings (Sysprep)
           SigmaSystemCenter configures its setting values as machine-specific information
           values in Sysprep execution. Machine-specific information that SigmaSystemCenter
           configures are shown in the following table.


           Machine specific settings           SigmaSystemCenter settings and conditions, etc.

           Computer name                       Host name on the Host setting
           NIC settings (IP address, subnet    Host settings
           mask, default gateway)              The upper limit on the number of NIC is 7.
                                               The upper limit on the number of NIC for virtual machines
                                               is 4, which is same as the upper limit of a machine profile.
           Product key                         Template settings or host settings.
                                               Host settings are prior to template settings.
           Name, Company name, Time zone,      Template settings.
           License                             Valid only when using Full Clone templates or Differential
                                               Clone templates in VMware vCenter Server.
           Administrator's password            Group settings or Host settings.
                                               Specified in host settings which settings to use.
           Workgroup and domain to join        Group settings
           Primary DNS, Secondary DNS,         Group settings.
           Primary WINS, Secondary WINS        The upper limit of the number of NIC is 4.
                                               For virtual machines, it is valid only when using Full Clone
                                               templates or Differential Clone templates in VMware
                                               vCenter Server.




Part I SigmaSystemCenter Functions Reference
                                                                                                       175
2 About Virtual Environment Management




2.7.3.     Preparing for Sysprep - DPM -
           To prepare for Sysprep, perform the following procedure on a master machine (a
           master VM).
           If you are using Windows Server 2008, Windows Vista or Windows 7, enable the
           Administrator account and log on to the Administrator account beforehand.


           1.   Copy the Sysprep modules of DPM
                1.   Execute \DPM\TOOLS\SYSPREP\Windows\COPYSYSPREP.VBS which is in
                     SigmaSystemCenter's media.
                     Copy the Sysprep modules of DPM to C:\Sysprep on the master machine (if
                     the system drive is "C:").
                2.   Specify a product key while executing COPYSYSPREP.VBS. This procedure
                     is unnecessary when the master machine is Windows Server 2008 or
                     Windows Vista.
           2.   Copy Microsoft Sysprep
                1.   This procedure is unnecessary for Windows Server 2008, Windows Vista or
                     Windows 7.
                2.   Copy Sysprep.exe and Setupcl.exe stored in
                     \SUPPORT\TOOLS\DEPLOY.CAB, which is in the Windows OS media, to
                     C:\Sysprep.
                3.   Copy Netdom.exe stored in \SUPPORT\TOOLS\SUPPORT.CAB in Windows
                     OS media to Sysprep\i386\$OEM$\$$\SYSTEM32, which is created in Step 2
                     of Procedure 2.
           3.   Input an IP address of the DPM management server in the Server IP setting in
                SERVER.INI. SERVER.INI is located in Sysprep folder.
           4.   Join Work Group.
           5.   Delete Administrator's password. This procedure is unnecessary for Windows
                Server 2008, Windows Vista or Windows 7.



2.7.4.     Preparing for Sysprep - vCenter Server -
           Perform the following procedure on a management server of vCenter Server.


           1.   Obtain the module of Microsoft Sysprep
                •    Microsoft Download Center
                •    Windows OS media\SUPPORT\TOOLS\DEPLOY.CAB


           2.   Copy Microsoft Sysprep to the vCenter Server machine.
                1.   Deploy the Sysprep modules in the subfolder, located under the following
                     folder. This procedure is unnecessary for Windows Server 2008, Windows
                     Vista or Windows 7.

                                                         SigmaSystemCenter 2.1 Reference Guide
176
                                                        Machine-Specific Settings in OS Deployment



                    -   If Windows Server 2003 is installed in vCenter Server machine, the
                        destination folder to make a copy is

                        C:\<ALLUSERSPROFILE>\Application                   Data\Vmware\VMware
                        VirtualCenter\sysprep (if the system drive is C:).
                        Normally, <ALLUSERSPROFILE> is \Documents And Settings\All
                        Users\.


                    -   If Windows Server 2008 is installed in vCenter Server machine, the
                        destination folder to make a copy is

                        C:\<ALLUSERSPROFILE>\Vmware\VMware VirtualCenter\sysprep.
                        Normally, <ALLUSERSPROFILE> is \ProgramData\.



                    Destination subfolders for deployment are as follows. Each of the subfolders
                    corresponds to the OS types.


                    -   .\2k\
                    -   .\xp\
                    -   .\svr2003\
                    -   .\xp-64\
                    -   .\svr2003-64\


               2.   Verify that the following files exist in a subfolder of each OS.


                    -   deptool.chm
                    -   readme.txt
                    -   setupcl.exe
                    -   setupmgr.exe
                    -   setupmgx.dll
                    -   sysprep.exe
                    -   unattend.doc




Part I SigmaSystemCenter Functions Reference
                                                                                               177
2 About Virtual Environment Management




2.7.5.     How to Use Sysprep - OS Deployment, HW Profile Clone
           (DPM) -
           Sysprep is executed using DeploymentManager for physical machines and HW Profile
           Clone. DeploymentManager executes Sysprep on the source image of deployment and
           on the destination image of deployment, a total of 2 times. The number of Sysprep
           execution is limited, so you need to prevent the number of Sysprep execution from
           exceeding the limit in operations. Make a full backup image of a machine before
           executing Sysprep and restore it to the machine as Procedure 6 in the following figure.
           Sysprep will work at the timing of the processes described in blue with under lines in
           the following figure. When deleting specific information of the source machine of
           deployment, execute Sysprep manually.


           This process is called Disk Duplication OS Installation because the same operation as
           OS installation is executed in the process using the backup and restoring function of
           DeploymentManager.


           Sysprep is convenient to vary the same image to some extent and deploy them to
           multiple machines.
           However, a total processing time will take longer if Sysprep execution time is included.


           Therefore, in general, Sysprep customization is not configured in fault recovery action
           such as N+1 Recovery in which the process of the backup and restoring function is
           included.




                                                          SigmaSystemCenter 2.1 Reference Guide
178
                                               Machine-Specific Settings in OS Deployment




Part I SigmaSystemCenter Functions Reference
                                                                                     179
2 About Virtual Environment Management




2.7.6.     How to Use Sysprep - Full Clone, Differential Clone
           (vCenter Server) -
           If you execute Full Clone or Differential Clone on VMware virtual machines (managed
           by vCenter Server), vCenter Server executes deployment operations.


           Sysprep will work automatically at the timing of the processes described in blue with
           under lines in the following figure.


           In the following case, vCenter Server executes Sysprep.




                                                        SigmaSystemCenter 2.1 Reference Guide
180
                                               Machine-Specific Settings in OS Deployment




Part I SigmaSystemCenter Functions Reference
                                                                                     181
2 About Virtual Environment Management




2.7.7.     How to Use Sysprep - Disk Clone, Differential Clone
           (DPM) -
           Execute Sysprep using DeploymentManager which is targeted at the following virtual
           machines.


            Hyper-V
            XenServer
            Standalone ESXi
            vCenter Server (Disk Clone)


           If you follow the procedure in the following figure, Sysprep will be executed on a replica
           VM at all times. Therefore a master VM will keep the status of the master VM which
           was before executing Sysprep. Sysprep will work automatically at the timing of the
           processes described in blue with under lines in the following figure.


           Sysprep processing method of virtual machines is different from that of physical
           machines in that Sysprep is executed automatically on the source machine of
           deployment. "execsysprep.bat" calls Sysprep on a replica VM that is to be the
           destination of deployment. You need to register execsysprep.bat to
           DeploymentManager and SigmaSystemCenter as indicated by red with underline in the
           following figure.


           "execsysprep.bat" is installed in the folder below.


           SystemProvisioning Installation folder\opt




                                                           SigmaSystemCenter 2.1 Reference Guide
182
                                               Machine-Specific Settings in OS Deployment




Part I SigmaSystemCenter Functions Reference
                                                                                     183
2 About Virtual Environment Management



2.8. Image Management (Differential Clone,
     Disk Clone)

2.8.1.     Images and Replica VMs
           Generally, the term "image" refers to the binary data including OS or disks which form
           the basis for creating virtual machines. However, "image" in Differential Clone and Disk
           Clone refers to "replica VM".


           Replica VMs are:


            Differential Clone: Created based on a snapshot on a specified master VM.
            Disk Clone: Created based on a specified master VM.


           Images can be managed from the template setting window of Differential Clone and
           Disk Clone. A number of images can be managed on one template. Therefore, you can
           check generational relations with images which were created from the same master
           VM.
           This multiple images management function and the Reconstruct function reduces the
           number of procedures and enables easy and quick execution of various operations
           such as patch application.




                                                         SigmaSystemCenter 2.1 Reference Guide
184
                                               Image Management (Differential Clone, Disk Clone)




Part I SigmaSystemCenter Functions Reference
                                                                                            185
2 About Virtual Environment Management




2.8.2.     About Images Used When Creating Virtual Machines
           Templates can manage multiple images. The images that are to be used for virtual
           machine creation which is performed in the processes of Create and Assign Machine
           and the Reconfigure (Reconstruct) must be specified. You can specify the images by
           the following two ways:


           1.   The default images
                If you don't specify images in the way of 2, the default images will be used for
                creating virtual machines.
                The default images are set by the ways listed below:


                •   If you create a new template and an image at the same time, the image is
                    registered as the default.
                •   When creating a new image, you can specify whether or not to register the
                    image as the default.
                •   You can change a default image to a specified image from the Edit Template
                    or the Image List on the Edit Template.




           2.   A specified image on Group / Model Property Setting
                You can specify images that are to be used for creating virtual machines from the
                Group or Model Property Setting. If you specify images, the default images are not
                used. If a number of groups or models use one template, another image can be
                specified for each of the groups or the models separately. You can also remove
                the image specification to configure the setting back to use the default images.




                                                         SigmaSystemCenter 2.1 Reference Guide
186
                                               Image Management (Differential Clone, Disk Clone)




Part I SigmaSystemCenter Functions Reference
                                                                                            187
2 About Virtual Environment Management




2.8.3.     Types of Replica VM
           Replica VM of Differential Clone is divided into the following two types.
           You need not to be aware of the differences between the two types in normal use.


            Master Replica VM
               It is the first replica VM that was created directly from a master VM. It is called
               Master Replica VM because it is to be a master image of Edge Cache Replica VM
               described below. Information of Master Replica VM is used as detailed information
               of images (replica VMs).


            Edge Cache Replica VM
               If the destination Datastore where virtual machines are to be created and the
               destination Datastore where Master Replica VM is to be stored are different, a
               clone of the Master Replica VM is copied in the former Datastore and virtual
               machines are created based on the clone. This clone of Master Replica VM is
               used as a cache. Therefore, it is called Edge Cache Replica VM. Edge Cache
               Replica VM is created in all Datastores in use. Edge Cache Replica VM reduces
               the number of accesses to the Datastore where the Master Replica VM is stored
               during the process of creating a virtual machine and the working processes of the
               virtual machine.


           If you create a virtual machine from a Disk Clone template on a Datastore which is
           different from the Datastore where a Master Replica VM is stored, Edge Cache Replica
           VM is not created but an image of the virtual machine is copied directly from the Master
           Replica VM.


           Replica VMs are created or deleted at the following timings. Edge Cache Replica VMs
           are created or deleted automatically. Therefore, manual operations are unnecessary.


            A Master Replica VM is created automatically when creating an image or a
             template.
            A Master Replica VM and the related Edge Cache Replica VMs are deleted
             automatically at the timing of deleting templates or images:
               •    Deleting a template or an image will fail if a virtual machine which was created
                    from the image exists.
               •    Master VMs or Master Replica VMs cannot be deleted directly from the Virtual
                    view.
            When a virtual machine is created, an Edge Cache Replica VM is created
             automatically if any Edge Cache Replica VMs do not exist in the destination
             Datastore where the virtual machine is to be created.




                                                          SigmaSystemCenter 2.1 Reference Guide
188
                                               Image Management (Differential Clone, Disk Clone)




Part I SigmaSystemCenter Functions Reference
                                                                                            189
2 About Virtual Environment Management




2.8.4.     Names of Images and Replica VMs
           SigmaSystemCenter names new images in the following format automatically when
           creating the images.


            Image name : MasterVMName-Template-Generation-Name
               •   MasterVMName : This part is a virtual machine name of a master VM.
               •   Template : Multiple templates which are targeted at the same master VM are
                   numbered in sequential order.
               •   Generation : This part is a generation number. Multiple images which were
                   created on the same template are numbered in sequential order. A new
                   number is created for a new image by adding 1 to the maximum number of
                   existing images.
               •   Name : Arbitrary strings are selected when creating a new image. The default
                   value is “Image.”


           SigmaSystemCenter also name Replica VMs automatically.


            Master Replica VM name : Replica-ImageName
               •   ImageName : This part is an image name.


            Edge Cache Replica VM name : Replica-ImageName-cache-ChacheNumber
               •   ImageName : This part is an image name.
               •   ChacheNumber : Edge Cache Replica VMs that were created from the same
                   Master Replica VM are numbered in sequential order.




                                                       SigmaSystemCenter 2.1 Reference Guide
190
                                                                             Snapshot Management



2.9. Snapshot Management
           SigmaSystemCenter can create snapshots of virtual machines. When you create a
           snapshot, a virtual machine's status at the point of the snapshot creation is saved.
           When you restore the created snapshot, the virtual machine can restore the status at
           the point of the snapshot creation.
           Snapshots save only differences from the bases. Therefore, snapshots can be created
           with relatively small capacity. Additionally, creation / restoration of snapshots are
           relatively easy. Therefore, you can execute a slight test and can restore previous state
           easily if any mistake is discovered through the test.


           SigmaSystemCenter manages snapshots using functions of virtual platform software.
           The following functions can be used.


            Displays a list of snapshots of a specified virtual machine.
            Creates a snapshot of a specified virtual machine.
               •    To secure stationary status, turn off virtual machines and create snapshots.
               •    Snapshots of multiple virtual machines can be created in only one operation.
            Deletes a specified snapshot.
            Restores a virtual machine to a specified snapshot's status.


           Information of the base snapshots is recorded in snapshots' paths.
           SigmaSystemCenter can manage relations between snapshots hierarchically using
           information of the snapshots' paths as the following figure.




Part I SigmaSystemCenter Functions Reference
                                                                                                   191
2 About Virtual Environment Management



2.10. Virtual Machine Mobility
           Move VM is a function to move selected virtual machines to another virtual machine
           server. There are three approaches of move virtual machines:


            Hot Migration / Cold Migration
            Move
            Failover



2.10.1. Hot Migration/Cold Migration
           If a target virtual machine to be moved is allocated on a Datastore that is shared
           between the source virtual machine server and the destination virtual machine server,
           the virtual machine can be moved to the destination virtual machine server using Hot
           Migration / Cold Migration. The destination Datastore cannot be changed.
           The moving operations are called differently depending on target virtual machines'
           power status. It is called Hot Migration when target virtual machines are power ON and
           called Cold Migration when power OFF. Whether or not to start the virtual machines
           after moving can be chosen.




                                                        SigmaSystemCenter 2.1 Reference Guide
192
                                                                             Virtual Machine Mobility




2.10.2. Move
           A target virtual machine can be moved to another virtual machine server whether a
           Datastore is shared or not.
           If the target virtual machine to be moved is allocated on a Datastore that is not shared
           between the source virtual machine server and the destination virtual machine server,
           the virtual machine is moved to another Datastore that is connected to the destination
           virtual machine server. If there are several Datastores that are connected to the
           destination virtual machine server, the destination Datastore will be selected at
           random.
           If the target virtual machine to be moved is allocated on a Datastore that is shared
           between the source virtual machine server and the destination virtual machine server,
           the action of the moving operation is the same as Cold Migration.
           If the target virtual machine is power ON, it will be moved after shutdown.




Part I SigmaSystemCenter Functions Reference
                                                                                                 193
2 About Virtual Environment Management




2.10.3. Failover
           A target virtual machine can be moved to another virtual machine server when the
           source virtual machine server is power OFF.
           The target virtual machine must be allocated on a Datastore that is shared between the
           source virtual machine server and the destination virtual machine server.
           This function makes it possible to move virtual machines to another virtual machine
           even if the source virtual machine server cannot be started owing to various causes
           such as a failure. When a standard policy for virtual machine servers is applied, virtual
           machines that were running on a virtual machine server where a failure occurs can be
           automatically moved to another virtual machine server.




                                                          SigmaSystemCenter 2.1 Reference Guide
194
                                                             VM Optimized Placement Management



2.11. VM Optimized Placement Management

2.11.1. Capacity Control of the Virtual Machine Server
           SystemProvisioning provides a function that limits the number of virtual machines
           running on a virtual machine server. This function is effective to prevent required
           processing resources for virtual machines from exceeding the capacity of each virtual
           machine server.
           Configure a numeric value to the capacity value that corresponds to the processing
           resource capacity of the virtual machine server, and to the cost value that corresponds
           to the required processing resource to start the virtual machine.
           When starting, moving or creating virtual machines, it is ensured that the total cost
           value of the virtual machines (powered On) on the virtual machine server does not
           exceed the capacity value of it. For example, if the capacity value of the virtual machine
           server is 100, 10 virtual machines (powered On) with a cost value of 10 can be created.


           Note: Specify the capacity value and cost value on the Web Console. For details of
           how to specify the values, see Subsection 1.1.6, "Capacity Value and Cost Value" in
           SigmaSystemCenter Web Console Reference Guide.



2.11.2. VM Optimized Placement
           SystemProvisioning monitors the load status of each virtual machine server. If a virtual
           machine server under high load is detected, some of the virtual machines are moved
           from the virtual machine server to another one by Hot Migration.
           If the high load is not reduced enough by moving virtual machines, SystemProvisioning
           starts new virtual machine servers and migrates the virtual machines to them.
           Conversely, if a surplus of machine power, such as the use of multiple virtual machine
           servers with low loads, the virtual machines are automatically migrated to other virtual
           machine servers 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 by Hot Migration; 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.
           In addition, when a virtual machine server becomes down by failure or some other
           reason, SigmaSystemCenter moves virtual machines on a shared disk to other virtual
           machine server by Failover. In this case, the Optimized Placement function selects an
           appropriate virtual machine server of a destination.
           This function checks the memory usage of a virtual machine server and moves to not
           exceed the memory size

Part I SigmaSystemCenter Functions Reference
                                                                                                  195
2 About Virtual Environment Management

           You can configure whether you enable or disable the VM Optimized Placement
           function and the appropriate load condition when enabled to each VM Server model.
           Configure High Load Bound, Target Region, and Low Load Bound.
           SystemProvisioning automatically adjusts the number of virtual machines to the target
           region of each virtual machine server by Hot Migrating the virtual machines, based on
           the settings.




               Load on CPU of a Virtual Machine Server

            100% High Load Bound 80%


                    Target Region        45%~70%



                   Low Load Bound 40%
              0%

                      Instruct to move                                                                      Virtual
                       virtual machine                                                                      Machine
                                                                                                            Servers
                   SystemProvisioning     Notification   System Monitor - Performance Monitoring Services




           Let’s see an example of solving a high load to know how SigmaSystemCenter operates.
           SigmaSystemCenter monitors the performance of the virtual machine server using
           System Monitor - Performance Monitoring Services. When an alert of a high CPU load
           of a virtual machine server is received from the System Monitor - Performance
           Monitoring Services, SystemProvisioning migrates the virtual machines from the virtual
           machine server with a high CPU load status to a virtual machine server with a low CPU
           load status.


           Note: You can enable the VM Optimized Placement function on the Web Console. For
           the method, see Section 5.3, "Configuring to Use the VM Optimized Placement
           Function" in SigmaSystemCenter Configuration Guide.



2.11.3. Conditions for VM Optimized Placement
           The VM Optimized Placement function includes the following actions:
            Load balance by Hot Migrate
            Power save by Hot Migrate
            Failover


           To execute these operations, a destination and source virtual machine server and a
           target virtual machine must meet the following conditions:

                                                                   SigmaSystemCenter 2.1 Reference Guide
196
                                                            VM Optimized Placement Management



            Destination candidate virtual machine server
               •   Belongs to the same operation group with a source virtual machine server
               •   Shares the same storage with a source virtual machine server
               •   Its Hardware Status is not either Faulted or Degraded
               •   Power status is not Off and not being started
                   However, if SystemProvisioning cannot resolve the issue with operable virtual
                   machine servers, it uses stopped virtual machine servers after starting them
                   or virtual machines that are being started after completely started.
               •   Other operations are not executed (except the startup operation)
               •   Has free capacity
               •   Has free memory (This is out of a target for Failover)
               •   Not in the Maintenance Mode


            Target virtual machine
               •   Power status is ON
                   However, if you execute evacuate machine command with -all option or if the
                   policy action of Action for VMS / Move all VMs on the VM server is executed,
                   this condition is out of a target.
               •   Not in the Maintenance Mode
               •   Other operations are not executed
               •   Its Managed Status is Managed


           The Power Status that is displayed on the Web Console might be different from the
           actual power status. Therefore, SystemProvisioning checks the actual power status of
           virtual machines and virtual machine servers when executing various operations
           towards them. The Power Status that is displayed on the Web Console is not checked.
           For example, if the Power Status displayed on the Web Console is On and the actual
           status is Off, SystemProvisioning regards it as Off.
           However, when executing Failover, SystemProvisioning checks the Power Status
           displayed on the Web Console. In this case, if On is displayed on the Web Console, the
           machine is regarded as ON. If Off is displayed on the Web Console,
           SystemProvisioning checks the actual state of the machine.


           Power Saving function does not support Hyper-V. Only Load Balancing is available.




Part I SigmaSystemCenter Functions Reference
                                                                                               197
2 About Virtual Environment Management




2.11.4. VM Optimized Creation
           VM Optimized Creation is a function that SystemProvisioning selects an appropriate
           destination virtual machine server and Datastore when creating virtual machines.


           Virtual machines’ performance should be considered when creating the virtual
           machines. Virtual machines’ performance depends on various factors. A major factor is
           the load of a destination virtual machine server and Datastore.
           When the load of a virtual machine server and Datastore becomes high, the
           performance of virtual machines running on them gets worse. On the other hand, the
           load of a virtual machine server and Datastore is affected by the load of virtual
           machines running on them. In addition, the load of the virtual machine server and
           Datastore becomes higher as the number of virtual machines running on them
           increases. To use a virtual machine at the same level of performance at any time, the
           virtual machine’s performance in peak hours and in off-peak hours should not be
           different. A good solution for this problem is to distribute virtual machines evenly to
           several virtual machine servers and Datastores.
           VM Optimized Creation function selects a destination virtual machine server and
           Datastore automatically to allocate virtual machines evenly to virtual machine servers
           and Datastores. VM Optimized Creation function makes it easy to build a virtual
           environment that should consider load balance, because it is unnecessary to select
           destinations of virtual machines individually.


           If a destination virtual machine server or a Datastore is not specified when creating
           virtual machines, VM Optimized Creation function will work. VM Optimized Creation
           function is available for all of virtual platform software, VMware, Hyper-V and
           XenServer. Additionally, it is also available for all of templates, Full Clone, HW Profile
           Clone, Differential Clone and Disk Clone.




                                                          SigmaSystemCenter 2.1 Reference Guide
198
                                               VM Optimized Placement Management




Part I SigmaSystemCenter Functions Reference
                                                                            199
2 About Virtual Environment Management




2.11.5. Conditions for VM Optimized Creation

           1.   Basic Scope of Destination Virtual Machine Servers
                Basic scope of destination candidates is as follows:
                •      If a VM model for the target virtual machine to be created is configured to
                       relate to a VM Server model, virtual machine servers that belong to the VM
                       Server model can be destination candidates.
                •      If a VM model for the target virtual machine to be created is not configured to
                       relate to a VM Server model, virtual machine servers that belong to the same
                       datacenter as the specified template belongs to can be destination
                       candidates.


           2.   Requirements for Destination Virtual Machine Servers
                Destination virtual machine servers must satisfy all the following requirements:
                •      Management Status is Managed.
                •      Maintenance Status is Off.
                •      Executing Status is not In-process.
                •      Hardware Status is not either Faulted or Degraded.
                •      Running Status is On.
                •      Connected to all networks that are configured in Machine Profile for the target
                       virtual machine.
                •      Started and ready.


           3.   Virtual Platforms and Template Types
                Depending on virtual platform types and specified template types, the scope of
                destination candidates is limited as follows:
                Virtual      platform   Template type        Limited scope of destination candidates
                type

                VMware(VC               Full Clone           Virtual machine servers belong to the same
                Management)                                  Datacenter as the template belongs to.
                                        HW Profile Clone     Virtual machine servers belong to the same
                                                             Datacenter as the template belongs to.
                                        Differential Clone   Virtual machine servers belong to the same
                                                             Datacenter as the template belongs to.
                                        Disk Clone           Virtual machine servers connected to a
                                                             Datastore where the image of the template is
                                                             stored.
                Standalone ESXi         HW Profile Clone     Virtual machine servers connected to a
                                                             Datastore where the image of the template is
                                                             stored.
                                        Differential Clone   Virtual machine servers connected to a
                                                             Datastore where the image of the template is
                                                             stored.

                                                             SigmaSystemCenter 2.1 Reference Guide
200
                                                              VM Optimized Placement Management


                                     Disk Clone             Virtual machine servers connected to a
                                                            Datastore where the image of the template is
                                                            stored.
                XenServer            Full Clone             Virtual machine servers connected to a
                                                            Datastore where the template is stored.
                                     Differential Clone     Virtual machine servers belong to the same
                                                            Datacenter as the template belongs to.
                                     Disk Clone             Virtual machine servers belong to the same
                                                            Datacenter as the template belongs to.
                Hyper-V Cluster      HW Profile Clone       Virtual machine servers belong to the same
                                                            Datacenter as the template belongs to.
                                     Differential Clone     Virtual machine servers connected to a
                                                            Datastore where the image of the template is
                                                            stored.
                                     Disk Clone             Virtual machine servers connected to a
                                                            Datastore where the image of the template is
                                                            stored.
                Hyper-V Single       HW Profile Clone       Virtual machine servers belong to the same
                Server                                      Datacenter as the template belongs to.
                                     Differential Clone     Virtual machine servers where the image of
                                                            the template is stored.
                                     Disk Clone             Virtual machine servers where the image of
                                                            the template is stored.


           4.   Selection Criteria for Destination Virtual Machine Server and Datastore
                Virtual machine servers that satisfy all of the above condition, 1, 2 and 3 are to be
                destination candidates. All the Datastores that are connected to candidates of
                destination virtual machine server are to be candidates of destination Datastore. A
                destination virtual machine server and Datastore are selected from destination
                candidates on the basis of the following selection criteria:


                •   Selection criteria for a destination virtual machine server (described in
                    descending order of priority)
                    -    A virtual machine server that has the best Datastore is given priority. The
                         best Datastore is selected on the basis of "Selection criteria for a
                         destination Datastore" (described below).
                    -    A virtual machine server whose free capacity (see Subsection
                         2.11.1, ”Capacity Control of the Virtual Machine Server”) is the largest is
                         given priority.


                •    Selection criteria for a destination Datastore (described in descending order
                    of priority)
                    -    A Datastore without exceeding either the datastore capacity or the upper
                         limit of datastore usage after creating the virtual machine is given priority.
                         The datastore capacity and the upper limit of datastore usage can be
                         configured in the registry.



Part I SigmaSystemCenter Functions Reference
                                                                                                      201
2 About Virtual Environment Management

                         Registry key:
                         HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Engine


                         ▪ DatastoreCapacity – Datastores capacity. The upper limit of the
                            number of running (Running Status is On) virtual machines (common
                            to all Datastores). (The default value: 100)
                         ▪ DatastoreDesiredMaxPercentage - Upper limit of datastore usage
                            (common to all Datastores). (The default value: 80)
                         ▪ These above limits are not hard limits. If it is not possible to create the
                            virtual machine without exceeding these limits, they will be exceeded.


                    -    The number of virtual machine servers connected to the Datastore : A
                         Datastore that is the largest in number of connected virtual machine
                         servers is given priority.
                    -    Free datastore capacity : A Datastore whose free datastore capacity is
                         the largest is given priority.
                    -    Free space : A Datastore whose free space is the largest is given priority.


                Note: In SigmaSystemCenter 2.1 update 3 version, datastore capacity (upper limit
                of the number of running virtual machines) and upper limit of datastore usage
                (percentage of the datastore size) are common to all Datastores. Therefore, if
                some Datastores are extremely low-performance / small size, undesired
                destination Datastore might be selected (an extremely low-performance / small
                size Datastore might be selected) when creating virtual machine without specifying
                Datastore. When using this function, make sure that all Datastores have sufficient
                performance and size.


           5.   About the setting of destination Datastore in Machine Profile
                If a destination Datastore of the virtual disk is specified in a Machine Profile, the
                virtual disk is created according to the Machine Profile setting.


                •   If destination Datastore of the system disk is specified and destination
                    Datastore of the extended disk is not specified, the extended disk is created
                    on the same Datastore as the system disk.
                •   If a destination Datastore is specified when executing creation of the virtual
                    machine, and it is different from the destination Datastore specified in the
                    Machine Profile,
                    -    The system disk is created on the Datastore specified when executing
                         creation of the virtual machine.
                    -    The extended disk is created on the Datastore specified in the Machine
                         Profile.




                                                           SigmaSystemCenter 2.1 Reference Guide
202
                                                              VM Optimized Placement Management




2.11.6. VM Optimized Startup
           The VM Optimized Startup is a function that SystemProvisioning automatically selects
           an appropriate virtual machine server when starting or restarting the virtual machine.
           You can configure this function to each VM model.


           Normally, SystemProvisioning starts a virtual machine on a virtual machine server that
           is its current host; however, in the following cases, a virtual machine cannot be started
           on its current host.
            The host virtual machine server is stopped.
            The host virtual machine server is in maintenance mode. (Its Maintenance Status
             is On)
            The host virtual machine server does not have enough free capacity to start the
             target virtual machine.
            The target virtual machine is not allowed to start on the host virtual machine server
             by Optimized Placement Rules.


           If VM Optimized Startup is enabled, SystemProvisioning automatically moves the
           virtual machine to another virtual machine server and starts it there. The following table
           shows the setting of VM Optimized Startup and its effect.


           Starting on the current host   VM Optimized Startup            Effect

           Possible                       -                               Starts on the current host
           Impossible                     Disable                         Fails to start
           Impossible                     Enable                          Starts on another virtual
                                                                          machine server


           If there is no appropriate virtual machine server started and ready, a stopped virtual
           machine server will be started to start the target virtual machine on it. If a VM model for
           the target virtual machine is configured to relate to a VM Server model, the destination
           virtual machine server is selected from virtual machine servers that belong to the VM
           Server model. If the VM model is related to no VM Server model, the destination virtual
           machine server is selected from virtual machine servers that belong to the same
           datacenter as the target virtual machine belongs to. In selecting destination virtual
           machine server, a virtual machine server with lower load is given priority to balance
           load of virtual machine servers.




Part I SigmaSystemCenter Functions Reference
                                                                                                       203
2 About Virtual Environment Management




2.11.7. Example of VM Optimized Startup
           An example of the action of VM Optimized Startup is illustrated in the following figure.


           When VM3 is started, VM Optimized Startup moves VM3 to another virtual machine
           server before starting VM3 because VM Server2 which is the current host of VM3 is
           power Off.
           Destination candidates for VM3 are VM Server1, VM Server3, and VM Server4 which
           belong to DataCenter1 same as VM Server2. VM Server3 is selected from these
           candidates because of the following reasons:


            Both the total of the cost values and the load of running virtual machines on VM
             Server1 are the highest among the destination candidates. Therefore, VM Server1
             has less priority.
            Both the total of the cost values and the load of running virtual machines on VM
             Server4 are the lowest among the destination candidates. However, VM Server4
             does not share Datastore1 with VM Server2. Therefore, VM Server4 is excluded.




                                                          SigmaSystemCenter 2.1 Reference Guide
204
                                               VM Optimized Placement Management




Part I SigmaSystemCenter Functions Reference
                                                                            205
2 About Virtual Environment Management




2.11.8. VM Optimized Placement Rule
           The VM Optimized Placement Rule function constrains moving virtual machines by the
           Optimized Placement and Optimized Startup function. A specified virtual machine can
           be activated with connecting to a specified host using this function.
           When building your system using this function, you should follow the points listed below,
           and the system operations will not be stopped simultaneously even if hardware failure
           occurs.


            Consolidate virtual machines that are related to a specified operation to one host.
            Connect each of the virtual machines that should not be stopped simultaneously to
             different hosts.


           You can enable this function to each VM Server model.


           When the Optimized Placement and Optimized Startup function of SystemProvisioning
           moves virtual machines, a destination virtual machine server is selected in virtual
           machine servers that belong to the same group with the virtual machine server to which
           the target virtual machines currently belong.
           Normally, the Optimized Placement and Optimized Startup function select the
           destination virtual machine server automatically and you cannot control the selection;
           however, by using the VM Optimized Placement Rule function, you can restrict the
           selection of a destination.


           You can configure the setting to enable this function and the setting of rules for each
           VM Server model. The Optimized Placement and Optimized Startup function
           determines a destination according to the configured rules.


           The rules of this function are the rules between two machines, and you can specify the
           machines from Host Setting. Therefore, even if virtual machines or a virtual machine
           server is changed, the rules are maintained.
           You can configure multiple rules with one host match, but you cannot configure multiple
           rules with both hosts' match.


           The rule that can be configured with VM Optimized Placement Rule is a pinned rule. It
           pins virtual machines to a specified virtual machine server. If you specify this rule, the
           Optimized Placement and Optimized Startup function moves the virtual machines only
           to the pinned virtual machine server. If you pin one virtual machine to multiple virtual
           machine servers, the function moves virtual machines within the range.


           Even if a resource is not allocated to a destination virtual machine server, the rule is
           effective. Therefore, with such a rule, the Optimized Placement function and Optimized
           Startup function cannot execute move or startup operation towards the virtual machine.

                                                          SigmaSystemCenter 2.1 Reference Guide
206
                                                              VM Optimized Placement Management



           SystemProvisioning follows a configured rule as much as possible when executing
           Failover. However, if SystemProvisioning cannot move virtual machines owing to the
           rule, it ignores the rule. Configure rules with Force option to apply the rules even if
           Failover is executed. Note that if there are both rules, with Force option and without
           Force option, Failover action follows the rules with Force option and ignores the rules
           without Force option. Other functions follow all rules.


           Rules can be prioritized within the range from 1 to 4. The priority with small value takes
           priority over big one. The Optimized Placement function and Optimized Startup function
           follow it. Failover action also follows it, but Force option takes priority than it.


           The VM Optimized Placement Rule function conflicts with the Optimized Placement
           function and the Optimized Startup function. (However, the Optimized Placement
           function and the Optimized Startup function do not conflict.) If you configure a rule, it
           may affect on efficiency and processing speed of the Optimized Placement and
           Optimized Startup function. Therefore, note that you avoid configuring an excess
           setting and configure in the necessary range.
           In addition, we do not guarantee the operations with specifying over 5000 rules per a
           VM Server model.


           You can configure the VM Optimized Placement Rule with the ssc command. For more
           details, see SSC Command Reference.



2.11.9. Usage Examples of VM Optimized Placement Rule
           The VM Optimized Placement Rule function is effective in the following cases:


           1.   Several virtual machines that do the same operations are to be distributed surely
                to several virtual machine servers so that the system will not stop if a failure
                occurs.
           2.   A license contract of an application that is used on virtual machines is based on
                the number or the specific information of destination candidate virtual machine
                servers. To reduce the license fee, the number of the destination candidate virtual
                machine servers is to be reduced and the destination virtual machine servers to
                allocate virtual machines should be pinned.
           3.   The number of operable virtual machines on a virtual machine server is to be
                reduced deliberately so that the virtual machines that do special operations will not
                be affected by the load of other virtual machines. Therefore, the virtual machines
                that do special operations are to be pinned on a destination virtual machine server.


           An example of a system that is build to satisfy Requirement 1 is provided below.




Part I SigmaSystemCenter Functions Reference
                                                                                                  207
2 About Virtual Environment Management



           The following figure is an example of executing Optimized Placement Rule towards VM
           Server1, VM Server2, VM Server3, VM Server4 and VM Server5 on VMSModel under
           GroupA, and VM1, VM2, VM3, VM4, VM5, VM6, VM7 and VM8 that are operational on
           the virtual machine servers.


           The system has two operations; Operation A and Operation B. Operation A is running
           on VM1, VM3, VM5 and VM7 and Operation B is running on VM2, VM4, VM6 and VM8.
           To meet the requirements, two virtual machines that are composed of each of virtual
           machines of Operation A and Operation B are made to work on each virtual machine
           server. So the damage of each operation is minimized even if a failure occurs to the
           virtual machine server. Also, virtual machines running on a virtual machine server
           where a failure occurs are moved to VM Server5 which is a dedicated spare virtual
           machine server.


           To enable the above-mentioned, apply a pinned rule to each virtual machine. The
           pinned rule defines that each of the virtual machines are pinned to two virtual machine
           servers. One of the two virtual machine servers is for running and the other is for spare.
           Set the higher priority on the virtual machine server for running so that the virtual
           machines will work on the virtual machine server for running during operations. In the
           following figure, the pinned rules are indicated by green, red, blue and yellow. Each of
           pins binds the virtual machines with both virtual machine servers; for running and for
           spare. For example, the green pins bind VM1 with VM Server1 for running and VM
           Server 5.


           Each virtual machine cannot be moved to any virtual machine server other than the two
           virtual machine servers for running and for spare by this Optimized Placement Rule.
           However, it is except for during failure. If a failure occurs, Optimized Placement Rule
           might be ignored because the operations must be recovered as quickly as possible.


           Step 2 in the following figure is an example of ignoring Optimized Placement Rule
           during VM Server3’s failure.
           To apply Optimized Placement Rule strictly, specify Force option. System will work as
           required in Optimized Placement Rule if a spare machine is standby with powered ON.


           When virtual machines are out of Optimized Placement Rule, the virtual machines can
           be re-allocated according to Optimized Placement Rule by executing the re-allocating
           operation as Step 3 in the following figure.


           If you execute the re-allocating operation of virtual machines according to Optimized
           Placement Rule after VM Server 3 is recovered, VM5 and VM6 will be moved by Hot
           Migration according to the priority setting of Optimized Placement Rule.




                                                          SigmaSystemCenter 2.1 Reference Guide
208
                                               VM Optimized Placement Management




Part I SigmaSystemCenter Functions Reference
                                                                            209
2 About Virtual Environment Management



2.12. About Virtual Environment

2.12.1. Recovery Action for Virtual Machine Server Down
           One of SigmaSystemCenter's recovery functions for virtual environments is to recover
           virtual machines automatically when failure occurs.
           SigmaSystemCenter executes server down monitoring towards virtual machine servers
           from outside at regular intervals using the components such as NEC ESMPRO
           Manager. If a virtual machine server does not respond, SigmaSystemCenter moves
           virtual machines that are running on the virtual machine server to another virtual
           machine server (Failover).


           SigmaSystemCenter's recovery functions for virtual machine servers down have two
           major advantages:


            Power OFF virtual machine servers
               Although a virtual machine server is powered ON, a host on the virtual machine
               server may not respond.
               In such a half-dead case, Failover of virtual machines cannot be executed
               normally. Virtual machine servers must be powered OFF to execute Failover.
               However, normal shutdown often fails if a virtual machine server is half-dead. To
               cope with this phenomenon, SigmaSystemCenter executes Power OFF on virtual
               machine servers by power control through BMC. Owing to this, Failover can be
               surely executed even when virtual machines are in such a case.


            Investigates virtual machine servers
               When a failure occurs at storage or a network switch, it influences on the entire
               system. If such failures occur, or if a lot of virtual machine servers are down,
               recovery action may fail. Loads of the recovery action might make the situation
               worse. In such a case, the investigation process prevents recovery action being
               executed.
               Additionally, monitoring products might detect an access denied event by mistake
               if a virtual machine server is in high load temporarily, and unnecessary recovery
               action might be executed. The investigation process can also cope with such a
               problem. If the investigation process judges virtual machine servers are normal,
               recovery action will not be executed.


           Use Standard Policy (VM Server) to use these functions. Policies that cope with
           Machine Down are enabled by default in Standard Policy (VM Server). Other standard
           policies (except Hyper-V) for virtual environments are the same.




                                                        SigmaSystemCenter 2.1 Reference Guide
210
                                                                         About Virtual Environment

           The following figure is an explanation of recovery action for a Machine Down event in a
           VMware (vCenter Server Management) environment where Standard Policy (VM
           Server) is applied.




Part I SigmaSystemCenter Functions Reference
                                                                                               211
2 About Virtual Environment Management




2.12.2. Recovery Action for HW Predictive Alert
           Another recovery function is to evacuate virtual machines to another virtual machine
           server in advance automatically when a HW Predictive alert, such as a temperature
           abnormality, occurs.
           BMC, which are implemented on machines, can detect unusual condition of hardware.
           This is HW Predictive alert. If BMC detects unusual condition, an event notification
           through NEC ESMPRO Agent, NEC ESMPRO Manager, or Out-of-Band Management
           (OOB Management) occurs. SigmaSystemCenter receives the event notification and
           moves virtual machines running on the virtual machine server where the event
           occurred to another virtual machine server (Hot Migration). This enables
           SigmaSystemCenter to avoid the possibility that failures might stop systems.


           System operations stop temporarily by Failover. On the other hand, systems can be
           operated without stopping as possible by HW Predictive alert because failures of virtual
           machine server can be avoided beforehand.


           In an analysis of HW sensor conditions, OOB Management verifies the hardware
           condition after receipt of the event notification. If the hardware condition does not
           change, recovery action is executed. If OOB Management is disabled, an analysis of
           HW sensor conditions is skipped and the next action of a policy is executed.


           To use this function, the setting of automatic shutdown during failure of NEC ESMPRO
           Agent must be disabled. *1


           Use Standard Policy (VM Server Predictive) to use this function. Policies related to HW
           Predictive alert are enabled by default in Standard Policy (VM Server Predictive). When
           using other standard policies, enable the policies related to HW Predictive alert
           because they are disabled by default.


           The following figure is an explanation of recovery action for Predictive alert: Chassis
           Temperature Failure event in a VMware (vCenter Server Management) environment
           where Standard Policy (VM Server Predictive) is applied.




                                                         SigmaSystemCenter 2.1 Reference Guide
212
                                                                            About Virtual Environment




           *1        ▪ If you are using ESX (Linux)
                     Start ESMamsadm and display the Shutdown Setting screen from Base Setting. Clear
                     the Enable the function check box.
                     ▪ If you are using Hyper-V (Windows)
                     Click the General tab and click Report Setting on the NEC ESMPRO Agent Properties
                     dialog. The Alert Manager dialog appears. From the setting menu, select Base Setting
                     – Other. Change the color of Shut Down Delay Setting icon to red.



Part I SigmaSystemCenter Functions Reference
                                                                                                     213
2 About Virtual Environment Management




2.12.3. About Monitoring Virtual Environments

           The following table explains how SigmaSystemCenter monitors virtual environments.


           How to monitor   Details       of    Events to be        SigmaSystemCenter’s       Notes
                            monitoring          detected            behavior   during    an
                                                during failures     event occurrence
                                                (Event names
                                                of         policy
                                                properties)

           Server down      Monitors            Machine Down,       Automatically recovers    -
           monitoring       running status      VMS                 by Failover (moves the
                            of virtual          connection          virtual machine to
                            machine             state is red        another virtual machine
                            servers and         (during ESXi        server).
                            status of a         monitoring)
                            network
                            between a
                            management
                            server and the
                            virtual machine
                            servers.
           Hardware         Monitors HW         Predictive alert:   Automatically             -
           monitoring by    status of virtual   fan/cooling         evacuates the virtual
           IPMI             machine             device failure,     machine to another
                            servers.            Predictive alert:   virtual machine server
                                                voltage failure,    (Hot Migration)
                                                Predictive alert:
                                                power unit
                                                failure,
                                                Predictive alert:
                                                Coolant leak,
                                                Predictive alert:
                                                chassis
                                                temperature
                                                failure, CPU
                                                temperature
                                                failure, CPU
                                                failure, Memory
                                                degeneration,
                                                Memory failure
           Performance      Monitors load       over load           Automatic Load            -
           monitoring by    status of virtual   (SysmonPerf)        Balance by VM
           SystemMonitor    machine             low load            optimized placement,
                            servers in VM       (SysmonPerf)        automatic VM
                            optimized                               consolidation and
                            placement.                              Power Saving




                                                               SigmaSystemCenter 2.1 Reference Guide
214
                                                                                       About Virtual Environment


              Disk monitoring    Monitors              Machine Down,     Automatically recovers    Other than
                                 running status        Hard disk         by Failover (moves the    Standalone
                                 of disks which        recoverable       virtual machine to        ESXi cannot be
                                 virtual machine       failure, Alarm    another virtual machine   monitored, but
                                 servers use.          Datastore on      server).                  ESX of VMware
                                                       VMS can not be                              (vCenter Server
                                                       available (only                             Management)
                                                       on Standalone                               can be
                                                       ESXi)                                       monitored if a
                                                                                                   monitoring
                                                                                                   setting is
                                                                                                   added.




2.12.4. Server Down Monitoring of Virtual Machine Servers
              SigmaSystemCenter checks condition of virtual machine servers and communication
              pathways between a management server and virtual machine servers by server down
              monitoring at regular intervals.
              If a virtual machine server is down, hardware failure events might happen in addition to
              server down monitoring events. If the virtual machine server recovers by Failover, the
              same recovery action does not have to be executed several times on the same
              recovery target. If several events occur during virtual machine server down, only server
              down monitoring's failure detection triggers recovery action. It is defined in standard
              policies.


              Products / components that execute server down monitoring of virtual machine servers
              are different depending on the types of monitoring targets as the following table.


 Types         of   What             executes      A    Standard   Events              Notes
 monitoring         monitoring                     Policy to use   detected       by
 targets                                                           server     down
                                                                   monitoring

 ESX of VMware      NEC ESMPRO Manager             Standard        Machine Down        -
 (vCenter Server    and NEC ESMPRO Agent           Policy (VM
 Management),                                      Server)
 XenServer
 ESX of VMware      vCenter Server                 Standard        VMS                 If you are using ESXi,
 (vCenter Server                                   Policy (VM      connection          execute monitoring through
 Management)                                       Server)         state is red        vCenter Server because
                                                                                       NEC ESMPRO Agent
                                                                                       cannot be installed. Enable
                                                                                       vCenter Server’s processes
                                                                                       to deal with events because
                                                                                       they are disabled by default.
                                                                                       Disable policies that Target
                                                                                       Access is disabled. Enable
                                                                                       policies that VMS Access is
                                                                                       disabled.




Part I SigmaSystemCenter Functions Reference
                                                                                                               215
2 About Virtual Environment Management


 Standalone        SystemProvisioning           Standard       VMS            SystemProvisioning directly
 ESXi                                           Policy (VM     connection     executes monitoring
                                                Server ESXi)   state is red   because of the configuration
                                                                              without vCenter Server. To
                                                                              add ESXi as a monitoring
                                                                              target, click the Set ESXi to
                                                                              Be Managed on the Virtual
                                                                              view and click Add VM
                                                                              Server.
 Hyper-V Cluster   Microsoft Failover Cluster   Standard       Cluster Node   Microsoft Failover Cluster’s
                                                Policy (VM     Stopped        own restoration is executed.
                                                Server
                                                Hyper-V)


              The following figure is an explanation of the server down monitoring action that is
              executed by NEC ESMPRO Manager and NEC ESMPRO Agent.




                                                               SigmaSystemCenter 2.1 Reference Guide
216
                                                                              About Virtual Environment




2.12.5. Monitoring Hardware of Virtual Machine Servers
            SigmaSystemCenter monitors virtual machine servers' hardware using IPMI.
            IPMI is a standard interface specification that monitors condition of machines (involving
            temperatures, voltage, a fan and a bus) and executes recovery and remote control of
            machines. SigmaSystemCenter executes monitoring by IPMI using EXPRESSSCOPE
            engine (BMC) that are implemented on virtual machine servers.


            Routes to obtain events are different depending on the types of monitoring targets as
            follows.


 Types                Types of monitoring       A route to      Out-of-Band      Notes
                      targets                   obtain    an    Management
                                                event           (OOB
                                                                Management)
                                                                is necessary /
                                                                unnecessary

 NEC ESMPRO           Configurations with NEC   NEC             Unnecessary      However, if OOB
 Manager and NEC      ESMPRO Agent              ESMPRO                           Management is disabled,
 ESMPRO Agent                                   Agent obtains                    the process of an analysis
                                                BMC                              of HW sensor conditions is
                                                information                      skipped. To use OOB
                                                and sends it                     Management is strongly
                                                to NEC                           recommended.
                                                ESMPRO
                                                Manager by
                                                SNMP Trap.
 OOB Management       Configurations without    OOB             Necessary        SNMP components must
 of                   NEC ESMPRO Agent          Management                       be installed in a
 SystemProvisioning   such as ESXi              receives                         management server’s OS.
                                                events that                      Change how to receive
                                                are sent                         SNMP Trap so that SNMP
                                                directly by                      Trap can be received.
                                                BMC.
 *1                   Launch Operation Window of NEC ESMPRO Manager and click Option – Customize –
                      My Manager. Select the Use SNMP Trap Service(S) check box on the My Manager
                      dialog.


            Events of OOB Management might be sent from BMC in the case of using NEC
            ESMPRO Agent and NEC ESMPRO Manager. In this case, several events with same
            contents are sent. Therefore, SigmaSystemCenter ignores OOB Management events.


            Use Standard Policy (VM Server Predictive) which is a standard policy for Predictive
            alert and Standard Policy (VM Server Hyper-V Predictive) to use this function.


            Hardware monitoring events are mainly used as HW Predictive alert of hardware failure
            in standard policies for Predictive alert.


Part I SigmaSystemCenter Functions Reference
                                                                                                      217
2 About Virtual Environment Management



           Policy Action triggered by Predictive alert events checks hardware condition again in
           the process of HW sensor status analysis through BMC and executes recovery action
           that evacuates virtual machines automatically by Hot Migration in advance. Hardware
           failure events that can be used as Predictive alerts are as follows:


            Predictive alert: fan/cooling device failure
            Predictive alert: voltage failure
            Predictive alert: power unit failure
            Predictive alert: Coolant leak
            Predictive alert: chassis temperature failure


           Other serious failure events that cannot be used as Predictive alerts can also be
           obtained. However, in many cases, machines already fails at the timing of a failure is
           discovered and the machines cannot send events correctly. Even if the machines can
           send event notifications, they are often sent after recovery. Therefore, other serious
           failure events cannot be used as triggers of recovery action. When machines are down
           by failures, Machine Down events can be detected by server down monitoring.
           Considering the above-mentioned facts, only the two actions, mail notification and
           status changes, are basically configured in standard policies to cope with hardware
           failure events other than Predictive alert.
           However, recovery action that moves virtual machines to another virtual machine
           server by Failover is configured in the following event because they might occur during
           failure.


            CPU temperature failure




                                                            SigmaSystemCenter 2.1 Reference Guide
218
                                                                          About Virtual Environment




2.12.6. Monitoring Performance of Virtual Machine Servers
           SigmaSystemCenter uses high load events and low load events that are detected
           using System Monitor - Performance Monitoring Services as a trigger of Load
           Balancing and Power Saving.


           System Monitor - Performance Monitoring Services works as follows in the process of
           Performance Monitoring of VM Optimized Placement.


           1.   Setting thresholds automatically
                Sets the high load threshold and the low load threshold of a target virtual machine
                server’s CPU usage with reference to the setting information of VM optimized
                placement that is obtained from SystemProvisioning.


           2.   Obtaining performance data
                Calls API to obtain performance data towards a target virtual machine server and
                obtains the performance data of the virtual machine server remotely.

Part I SigmaSystemCenter Functions Reference
                                                                                                219
2 About Virtual Environment Management



           3.   Detecting high load / low load. Notify events.
                Compares the obtained data and the thresholds. If the conditions of high load
                (Load Balancing) / low load (Power Saving) are satisfied, notifies
                SystemProvisioning of that.


           The number of moving VM might be excessive in an environment where temporary
           high load happens intermittently and high load events occur frequently. To restrain
           excessive occurrence of events, System Monitor - Performance Monitoring Services
           reduces its sensitivity. System Monitor - Performance Monitoring Services regards the
           performance data as exceeding the threshold if the performance data continues to
           exceed the threshold 10 minutes in a row (in case of the high load monitoring for Load
           Balancing). For low load monitoring for Power Saving, System Monitor - Performance
           Monitoring Services reduces its sensitivity further. System Monitor - Performance
           Monitoring Services regards the performance data as falling below the threshold if the
           performance data continues to fall below the threshold 30 minutes in a row. This setting
           of sensitivity for thresholds can be changed.


           Obtained performance data is saved in the database as histories. Large amount of
           database capacity is required to save the obtained data for a long term. System
           Monitor - Performance Monitoring Services consolidates a number of obtained data so
           that the quantity of data accumulation will not increase quickly.




                                                           SigmaSystemCenter 2.1 Reference Guide
220
                                                                      About Virtual Environment




2.12.7. Monitoring System Disks of Virtual Machine Servers
           Even if disks become inaccessible from a virtual machine server's system, NEC
           ESMPRO Agent might be able to continue to work. In such a situation, server down
           monitoring of NEC ESMPRO Manager and NEC ESMPRO Agent regards the virtual
           machine server as normal and cannot detect the failure.


           To cope with the above problem, use HDD Access Monitoring Module.


           HDD Access Monitoring Module accesses system disks regularly to check the status of
           the system disk. If the system disk cannot be accessed, HDD Access Monitoring
           Module stops the SNMP Service on the virtual machine server and the response of
           SNMP packets from the virtual machine server will disappear. This enables NEC
           ESMPRO Manager to detect Machine Down of the virtual machine server.


Part I SigmaSystemCenter Functions Reference
                                                                                            221
2 About Virtual Environment Management



              HDD Access Monitoring Module is provided as an option of NEC ESMPRO Agent and
              normally not installed. It must be downloaded from the web site of NEC ESMPRO
              Manager and NEC ESMPRO Agent and installed to target virtual machine servers.


              HDD Access Monitoring Module is available only when a management target is ESX.




2.12.8. Monitoring Datastore of ESX
              Datastore monitoring is available only for Standalone ESXi by default.


 Types        of   vCenter   Enable      /   What          executes    A policy to    Events       to      be
 monitoring        Server    Disable by      monitoring                use            detected
 targets           version   default

 ESX in            4.0 or    Unavailable     VMware vCenter Server     Standard       Hard disk failure
 VMware (VC        later                                               Policy (VM
 Management)                                                           Server)
 ESX in            2.5       Unavailable     NEC ESMPRO Agent          Standard       Hard disk recoverable
 VMware (VC                                                            Policy (VM     failure
 Management)                                                           Server)
 Standalone        -         Available       SystemProvisioning        Standard       Alarm Datastore on
 ESXi                                                                  Policy (VM     VMs can not be
                                                                       Server ESXi)   available




                                                                  SigmaSystemCenter 2.1 Reference Guide
222
                                                                          About Virtual Environment



           Although Datastore monitoring is available only for Standalone ESXi by default, it can
           be available for ESX in VMware (vCenter Server Management) by adding a setting.
           How to add the setting is different according to vCenter Server versions and it will be
           explained in this subsection. As for HDD Access Monitoring Module, which is explained
           in Subsection 2.12.7, “Monitoring System Disks of Virtual Machine Servers”, it monitors
           only system disks and cannot detect Datastore failures.


            If vCenter Server version is 4.0 or later
               Now vCenter Server 4.0 or later version can detect an alert of a failure occurred at
               a Datastore to which ESX connects.
               By adding the following event handler setting to Standard Policy (VM Server),
               recovery action can run if a Datastore failure occurs.
               To use this function, you need to apply the Update Module (SSC0201-0017) to
               SigmaSystemCenter 2.1 Update 3.


               [SystemProvisioning Setting]
               1.   Add the monitoring event to Standard Policy (VM Server).
                    Add it from the Monitoring Events tab on the Policy Property Settings of
                    Standard Policy (VM Server).


                    Specify One Event: On
                    Event Category: Hard disk Failure
                    Report Source: VMwareProvider
                    Event: Storage path connectivity on VMS is lost
                    Action: Notification, Set faulted status, Investigate and Power OFF, Move all
                    running VMs on the VM server (Hot Migration, Failover)


            If vCenter Server version is 2.5
               According to VMware KB:1009553, if a failure occurs at a Datastore to which ESX
               connects and ESX cannot access the Datastore, ESX outputs a log which includes
               the string "Lost connectivity to storage device" into syslog.


               By using the above action of ESX, the syslog monitoring function of NEC
               ESMPRO Agent can detect the Datastore failure. However, SigmaSystemCenter
               cannot deal with this disk failure by default. Therefore, you need to add the setting
               of policies and events of NEC ESMPRO Agent and SystemProvisioning. After
               adding the setting, NEC ESMPRO Agent can notify SystemProvisioning of the
               failure through NEC ESMPRO Manager and activate the policy that deals with the
               failure event to execute recovery action if NEC ESMPRO Agent's syslog
               monitoring function detects the failure.




Part I SigmaSystemCenter Functions Reference
                                                                                                 223
2 About Virtual Environment Management



               NEC ESMPRO Agent cannot be installed on ESXi in VMware (vCenter Server
               Management). Therefore, Datastore monitoring by the syslog monitoring function
               cannot be executed on ESXi in VMware (vCenter Server Management).


           The following figure is an image of the syslog monitoring function's action.




                                                          SigmaSystemCenter 2.1 Reference Guide
224
                                                                           About Virtual Environment



            NEC ESMPRO Agent setting of ESX
                Configure ESX to check the Syslog keyword that the ESX outputs and to notify
                SystemProvisioning if the keyword is detected.


                Enable the Syslog Event Monitoring function of NEC ESMPRO Agent.


                     # vi /etc/syslog.conf

                     Add lines with (*) to the syslog.conf.
                     ---------------------------------
                     # Log all kernel messages to the console.
                     # Logging much else clutters up the screen.
                     #kern.*                /dev/console

                     (Omitted)

                     #send all local6.notice and higher messages to vmkernel log.
                     local6.notice           /var/log/vmkernel
                     local6.notice           /var/log/messages (*)
                     ---------------------------------


           1.   Set Syslog event
                For details, refer to Section 3.5, "Syslog Events Setting" in NEC ESMPRO Agent
                (for Linux) User's Guide.
                1.    Execute /opt/nec/esmpro_sa/bin/ESMamsadm.
                2.    Select Report Setting - Syslog Event Setting.
                3.    Select ON for Operation on Source at the Syslog Event Setting dialog and
                      click Add to display Add Syslog Item.
                4.    Enter the following in the Add Syslog Item dialog and click Done.
                5.    Source: ESXAlert
                      (Set an arbitrary name for the Source name depending on your system.)
                      EventID: C0000C00
                      Keyword1: Lost connectivity to storage device
                      (This string is outputted if a disk cannot be connected. Refer to VMware
                      KB:1009553.)
                      Trap Name: Lost Disk Connection
                6.    Click Set at the Syslog Event Setting dialog to display Syslog Application
                      Setting.
                7.    Configure the following setting at the Syslog Application Setting dialog and
                      click ok. Select SNMP on Destination ID List and click Add.
           2.   Do not change the default value of syslog monitoring intervals. (The default value
                is 300 seconds.)
                1.    Execute /opt/nec/esmpro_sa/bin/ESMagntconf.
                2.    Monitor Interval: 300 (Do not change the default value.)

Part I SigmaSystemCenter Functions Reference
                                                                                                 225
2 About Virtual Environment Management



            Settings of SystemProvisioning
               Add a new event that was defined in NEC ESMPRO Agent's Syslog setting to the
               event information definition file (EsmEvents.xml) of SystemProvisioning. Add the
               following lines with (*) to EsmEvents.xml. The lines define events. EsmEvents.xml
               is stored in the following directory.


                    SystemProvisioning installation directory\bin


                    Add lines with (*)


               ~Omitted~



                    <Source value="ESMDiskArray">
                      <Event>
                        <EventID>0x800403E9</EventID>
                        <TrapName lang="en">Disk Array Logical Device
               Critical</TrapName>
                        <TrapName lang="ja">Disk Array Logical Device
               Critical</TrapName>
                      </Event>
                    </Source>
                    <Source value="ESXAlert">                             (*)
                      <Event>                                         (*)
                        <EventID>0xC0000C00</EventID>                      (*)
                        <TrapName lang="en">Lost Disk Connection</TrapName> (*)
                        <TrapName lang="ja">Disk Connection Error</TrapName>   (*)
                      </Event>                                        (*)
                    </Source>                                         (*)
                  </OSType>


               ~Omitted~


               1.   Add a new policy that copes with the new event that has been added.
                    Add it from the Monitoring Events tab on the Policy Property Settings of
                    Standard Policy (VM Server).


                    Specify One Event: On
                    Event Category: Hard disk Recoverable Failure
                    Report Source: SystemMonitorEvent
                    Event: ESXALERT[0XC0000C00]
                    Action: Notification, Set faulted status, Investigate and Power OFF, Move all
                    running VMs on the VM server (Hot Migration, Failover)




                                                         SigmaSystemCenter 2.1 Reference Guide
226
                                                                                      About Virtual Environment

                    Specifications of ExmEvent.xml such as the format may be changed in future
                    versions. If SystemProvisioning is upgraded to the future versions, the additional
                    setting might not be succeeded and SystemProvisioning might not work.



2.12.9. About Failures in Virtual Environments

                The following failures might occur in virtual environments.




 No   Failure            Details    of   Influence of      How       to   SigmaSystemCenter’s         Others     (how   to
                         failure         failure           restore        default     function   to   increase
                                                                          deal with                   availability and so
                                                                                                      on).

 1    Management         HW/OS/SSC       Monitoring /      Change HW      -                           Backup at regular
      Server Failure     failure on a    controlling all   of a                                       intervals. Make a
                         management      machines          management                                 management
                         server          being             machine, OS                                server redundant
                                         managed is        reboot, etc.                               by using cluster
                                         disabled.                                                    software and FT
                                                                                                      servers.



Part I SigmaSystemCenter Functions Reference
                                                                                                               227
2 About Virtual Environment Management


 No   Failure            Details    of   Influence of      How         to   SigmaSystemCenter’s           Others     (how    to
                         failure         failure           restore          default     function     to   increase
                                                                            deal with                     availability and so
                                                                                                          on).

 2    Compatible         Failure of VC   VC:               Restart each     Notification on the           Make a
      products failure   or DPM          Monitoring /      product's        screen.                       management
                                         controlling       service.                                       server redundant
                                         VMS and VM                                                       by using cluster
                                         being                                                            software.
                                         managed is
                                         disabled.
                                         DPM: VM
                                         creation is
                                         disabled /
                                         patch and AP
                                         application is
                                         disabled.
 3    Management         A               Monitoring /      Change NIC       Event notification and        Make LAN
      Server             management      controlling all   cables.          notification on the           managed by a
      Communication      server's NIC    machines                           screen,                       management
      failure            failure / NW    being                                                            server and NIC
                         cable           managed is                                                       redundant.
                         disconnection   disabled.
 4    NW Switch          HW failure on   All operations    Change HW        Event notification and        Make NW switches
      failure            a NW switch     are disabled.     of NW            notification on the           redundant.
                                         Monitoring /      switch,          screen,
                                         controlling all   change the
                                         machines          setting.
                                         being
                                         managed is
                                         disabled.
 5    VMS                VMS             Control of        Change NIC       Automatic-recovery by         Make VMS's LAN
      Communication      management      VMS where         / cables.        Failover of VM to             for VM and NIC
      failure            LAN, NIC        failure                            another VMS, event            redundant.
                         failure / NW    occurred.                          notification, notification
                         cable           Almost all                         on the screen.
                         disconnection   controls
                                         including Hot
                                         Migration of
                                         VMs on the
                                         VMS where
                                         failure
                                         occurred are
                                         disabled.
 6    BMC                Failure of      Power source      Change the       Notification on the           -
      Communication      BMC and NIC     control /         HW failure       screen.
      failure            on VMS / NW     monitoring /      spot / cables.
                         cable           diagnosis
                         disconnection   through BMC
                                         are disabled.




                                                                     SigmaSystemCenter 2.1 Reference Guide
228
                                                                                        About Virtual Environment


 No   Failure            Details      of   Influence of     How       to    SigmaSystemCenter’s           Others     (how   to
                         failure           failure          restore         default     function     to   increase
                                                                            deal with                     availability and so
                                                                                                          on).

 7    VM                 Failure of        VM's             Restart VM.     -                             Make VMS's LAN
      Communication      LAN for VM        operations on                                                  for VM and NIC
      failure            and NIC on        VMS where                                                      redundant.
                         VMS / NW          failure
                         cable             occurred are
                         disconnection     disabled. VM
                                           creation is
                                           disabled
                                           (when using
                                           DPM) / patch
                                           and AP
                                           application
                                           disabled.
 8    VMS failure        HW / OS           VM's             Move VMs        Automatic-recovery by         -
                         failure on        operations on    on the VMS      Failover of VM to
                         VMS               VMS where        where failure   another VMS, event
                                           failure          occurred to     notification, notification
                                           occurred are     another VMS     on the screen.
                                           disabled.        and change
                                                            the VMS with
                                                            failure.
                                                            Remove the
                                                            OS failure
                                                            factor.
 9    VMS / HW           Nonfatal HW       VMS failure      Change the      Automatic detection of        -
      Predictive alert   failure on        might occur if   HW failure      predictive HW failure,
                         VMS               condition        spot. When      Automatic prior
                                           gets worse.      changing the    evacuation by Hot
                                                            body of         Migration of VM to
                                                            VMS, move       another VMS, Event
                                                            VMs on the      notification, Notification
                                                            VMS to          on the screen.
                                                            another
                                                            VMS.
 10   VMS high load      VMS is in         Operations       -               Automatic Load                -
      status             high load         delay by high                    Balancing of VM
                         status            loads.                           Optimized Placement.
 11   VMS low load       VMS is in low     Efficiency of    -               Automatic VM                  -
      status             load status       VMS usage                        consolidation by VM
                                           lowers.                          Optimized Placement
                                                                            and Power Saving.
                                                                            Hyper-V is not
                                                                            supported.
 12   VM failure         HW / OS           Operations of    Restart VM.     Event notification and        Make VMs
                         failure on        VM where                         notification on the           redundant by using
                         VMS               failure                          screen,                       cluster software.
                                           occurred are
                                           disabled.




Part I SigmaSystemCenter Functions Reference
                                                                                                                   229
2 About Virtual Environment Management


 No   Failure            Details       of   Influence of     How          to    SigmaSystemCenter’s           Others     (how     to
                         failure            failure          restore            default     function     to   increase
                                                                                deal with                     availability and so
                                                                                                              on).

 13   VMS multiple       Failure of         Operations       Changes            Event notification and        Make power
      simultaneous       shared             on stopped       shared             notification on the           devices redundant
      failure            devices such       VMS are          devices such       screen,                       and UPS
                         as a power         disabled.        as a power                                       introduction.
                         source (when                        source and
                         using blades)                       start them
                         and multiple                        after power
                         VMS stop by                         recovery.
                         a power
                         failure
 14   FC path failure    HBA failure        Operations of    Change HBA         Automatic-recovery by         Make HBA
                         on VMS / FC        VM where         / FC cables.       Failover of VM to             redundant.
                         cable              failure                             another VMS, event
                         disconnection      occurred are                        notification, notification
                                            disabled.                           on the screen.
 15   FC switch          FC switch          All operations   Change FC          Event notification and        Make FC switches
      failure            failure            are disabled.    switches.          notification on the           redundant.
                                                                                screen,
 16   Storage device     Port /             All operations   Change the         Event notification and        Make ports /
      failure            controller /       are disabled.    storage            notification on the           controllers
                         disk failure on                     failure spot.      screen,                       redundant. Setup
                         storage                             If data is lost,                                 disks in RAID
                                                             reconstruct                                      configuration for
                                                             the system.                                      redundancy.
 17   Shortage of        Shortage of        Creation of      Add                Event notification and        -
      Datastore          Datastore          new VM           Datastore or       notification on the
      capacity           capacity           disabled.        enhance the        screen,
                                            Disk             capacity.
                                            extension of
                                            VM disabled.

                Some of the detecting action and the details of recovery action are common, but many
                of them are different depending on the types of virtual platform software.
                An explanation of the detecting action and the details of recovery action according to
                the types of virtual platform software is provided in the next Subsection.



2.12.10. Policies in vCenter Server Management
                The following table explains action of Standard Policy (VM Server Predictive) that is
                applied to a VMware (vCenter Server Management) environment. Enable No.11, "VMS
                low load status" because it is disabled by default. No.17 explains System Policy
                (Manager).
                No.7 and No.12 describes failure of virtual machines and explains Standard Policy
                (VM).


                In the following table, "A summary of default action of policies during failure (The
                default value of some events are changed.)" explains recovery action for "Events to be
                detected (Event names of policy properties)".

                                                                       SigmaSystemCenter 2.1 Reference Guide
230
                                                                                 About Virtual Environment



 No   Failure            Events     to    be    A summary of action of       A summary of default action of
                         detected      (Event   failure detection            policies during     failure (The
                         names of policy                                     default value of some events
                         properties)                                         are changed.)

 1    Management         None                   None                         None
      Server Failure
 2    Compatible         None                   Detects access to manager    Failure events are not detected
      products failure                          disable in the process of    and recovery action by policies is
                                                using each product.          not executed.
 3    Management         Machine Down           If a management server       Executes mail notification and
      Server             (called VMS            becomes unable to access     event log output and change
      Communication      connection state is    VMS, NEC ESMPRO              VMS's status to fault status.
      failure            red for ESXi)          Manager (vCenter Server)     The investigation process judges
                                                detects VMS connection       the system is unrecoverable
                                                state is red.                because all VMS is inaccessible
                                                                             owing to the failure and ends with
                                                                             error status.
 4    NW Switch          Machine Down           If a management server       Executes mail notification and
      failure            (called VMS            becomes unable to access     event log output and change
                         connection state is    VMS, NEC ESMPRO              VMS's status to fault status.
                         red for ESXi)          Manager (vCenter Server)     The investigation process judges
                                                detects VMS connection       the system is unrecoverable
                                                state is red.                because all VMS is inaccessible
                                                                             owing to the failure and ends with
                                                                             error status.
 5    VMS                Machine Down           If a management server       Executes mail notification and
      Communication      (called VMS            becomes unable to access     event log output and change
      failure            connection state is    VMS, NEC ESMPRO              VMS's status to fault status.
                         red for ESXi)          Manager (vCenter Server)     The investigation process judges
                                                detects VMS connection       the system is recoverable
                                                state is red.                because only one VMS is
                                                                             inaccessible. Shuts down VMs on
                                                                             the target VMS using LAN for VM
                                                                             (through DPM). Executes Power
                                                                             OFF on the VMS. Moves VMs to
                                                                             another VMS by Failover and
                                                                             starts VMs to recover the system
                                                                             operations.
 6    BMC                None                   Detects BMC unavailable in   Failure events are not detected
      Communication                             the process of using BMC.    and recovery action by policies is
      failure                                                                not executed.
                                                                             The machine property setting
                                                                             screen of the Web Console
                                                                             displays OOB Management
                                                                             unable to connect.
 7    VM                 None                   None                         None
      Communication
      failure




Part I SigmaSystemCenter Functions Reference
                                                                                                           231
2 About Virtual Environment Management


 8    VMS failure        Machine Down          Machine Down (called VMS      Executes mail notification and
                         (called VMS           connection state is red for   event log output and change
                         connection state is   ESXi).                        VMS's status to fault status.
                         red for ESXi)         If a management server        The investigation process judges
                         CPU temperature       becomes unable to access      the system is recoverable
                         failure               VMS, NEC ESMPRO               because only one VMS is
                                               Manager (vCenter Server)      inaccessible. Shuts down VMs on
                                               detects VMS connection        the target VMS using LAN for VM
                                               state is red.                 (through DPM). Executes Power
                                               CPU temperature failure.      OFF on the VMS. Moves VMs to
                                                                             another VMS by Failover and
                                               Detects HW failure through    starts VMs to recover the system
                                               NEC ESMPRO Agent or           operations.
                                               OOB Management.
                                                                             An event of CPU temperature
                                                                             failure occurs right after VMS is
                                                                             down. Therefore, the
                                                                             investigation process and Power
                                                                             OFF are not executed.
 9    VMS / HW           Predictive alert:     Detects HW failure through    Disable NEC ESMPRO Agent's
      Predictive alert   fan/cooling device    NEC ESMPRO Agent or           setting of auto-shutdown during
                         failure               OOB Management.               failure beforehand in order to use
                         Predictive alert:                                   a policy of HW Predictive alert.
                         voltage failure                                     The policy executes the next
                         Predictive alert:                                   action.
                         power unit failure                                  First, it executes mail notification
                         Predictive alert:                                   and event log output and change
                         Coolant leak                                        VMS's status to fault status.
                         Predictive alert:                                   Second, it executes an analysis
                         chassis                                             of HW sensor conditions to
                         temperature failure                                 decide whether or not to execute
                                                                             recovery action. If it decides to
                                                                             execute the recovery action, it
                                                                             moves VMs on the target VMS to
                                                                             another VMS by Hot Migration. If
                                                                             Hot Migration fails, executes
                                                                             failover.
                                                                             Finally, it shuts down the target
                                                                             VMS.
 10   VMS high load      Over load             Detects high loads of VM      The policy executes VMS load
      status             (SysmonPerf)          servers by System Monitor -   balance action.
                                               Performance Monitoring        Moves VMs on a high load VMS
                                               Services                      to a low load VM by Hot Migration
                                                                             to balance the loads of VMS.
 11   VMS low load       Low load              Detects low loads of VM       Enable the policy for this failure
      status             (SysmonPerf)          servers by System Monitor -   event.
                                               Performance Monitoring        The policy executes VMS Power
                                               Services                      Save Action.
                                                                             Consolidates VMs automatically
                                                                             on a VMS that has relatively few
                                                                             VMs within the range of
                                                                             appropriate load. If the number of
                                                                             running VMs becomes 0, the
                                                                             VMS is shutdown to save the
                                                                             power consumption of the entire
                                                                             system.
 12   VM failure         None by default       vCenter Server detects        Executes mail notification and
                         (Machine Down)        Heartbeat alarm (disabled     event log output and change
                                               by default) *1                VMS's status to fault status.


                                                                SigmaSystemCenter 2.1 Reference Guide
232
                                                                                  About Virtual Environment


 13   VMS multiple      Machine Down           If a management server         Executes mail notification and
      simultaneous      (called VMS            becomes unable to access       event log output and change
      failure           connection state is    VMS, NEC ESMPRO                VMS's status to fault status.
                        red for ESXi)          Manager (vCenter Server)       The investigation process judges
                                               detects VMS connection         the system is unrecoverable if
                                               state is red.                  failure occurs on many VMSs and
                                                                              ends with error status.
 14   FC path failure   None by default        The followings can be          Executes mail notification and
                        (Machine Down,         detected by adding the         event log output and change
                        Hard disk              monitoring setting.            VMS's status to fault status.
                        recoverable failure)   Machine Down (System           The investigation process judges
                                               disk failure)                  the system is recoverable
                                               If failure occurs, NEC         because only one machine is
                                               ESMPRO Manager                 inaccessible. Executes Power
                                               (vCenter Server) detects       OFF on the VMS. Moves VMs to
                                               VMS connection state is red    another VMS by Failover and
                                               because NEC ESMPRO             starts VMs to recover the system
                                               Agent's HDD Access             operations.
                                               Monitoring Module cannot
                                               access from a management
                                               server to VMS. For how to
                                               add the monitoring, refer to
                                               SystemDisk Monitoring.

                                               Hard disk recoverable
                                               failure (Datastore failure)
                                               If a failure occurs, syslog
                                               monitoring of NEC
                                               ESMPRO Agent detects
                                               custom-add events. For
                                               how to set the monitoring,
                                               refer to Datastore
                                               Monitoring.
 15   FC switch         None by default        The followings can be          Executes mail notification and
      failure           (Machine Down,         detected by adding the         event log output and change
                        Hard disk              monitoring setting.            VMS's status to fault status.
                        recoverable failure)   Machine Down (System           The investigation process judges
                                               disk failure)                  the system is unrecoverable
                                               If failure occurs, NEC         because all VMS's disks are
                                               ESMPRO Manager                 inaccessible and no destination of
                                               (vCenter Server) detects       evacuation and ends with error
                                               VMS connection state is red    status.
                                               because NEC ESMPRO
                                               Agent's HDD Access
                                               Monitoring Module cannot
                                               access from a management
                                               server to VMS. For how to
                                               add the monitoring, refer to
                                               SystemDisk Monitoring.

                                               Hard disk recoverable
                                               failure (Datastore failure)
                                               If failure occurs, syslog
                                               monitoring of NEC
                                               ESMPRO Agent detects
                                               custom-add events. For
                                               how to set the monitoring,
                                               refer to Datastore
                                               Monitoring.


Part I SigmaSystemCenter Functions Reference
                                                                                                           233
2 About Virtual Environment Management


 16   Storage device   None by default        The followings can be          Executes mail notification and
      failure          (Machine Down,         detected by adding the         event log output and change
                       Hard disk              monitoring setting.            VMS's status to fault status.
                       recoverable failure)   Machine Down (System           The investigation process judges
                                              disk failure)                  the system is unrecoverable
                                              If failure occurs, NEC         because all VMS's disks are
                                              ESMPRO Manager                 inaccessible and no destination of
                                              (vCenter Server) detects       evacuation and ends with error
                                              VMS connection state is red    status.
                                              because NEC ESMPRO
                                              Agent's HDD Access
                                              Monitoring Module cannot
                                              access from a management
                                              server to VMS. For how to
                                              add the monitoring, refer to
                                              SystemDisk Monitoring.

                                              Hard disk recoverable
                                              failure (Datastore failure)
                                              If failure occurs, syslog
                                              monitoring of NEC
                                              ESMPRO Agent detects
                                              custom-add events. For
                                              how to set the monitoring,
                                              refer to Datastore
                                              Monitoring.
 17   Shortage of      Datastore              vCenter Server detects         The policy executes mail
      Datastore        Overallocation on      Datastore Over allocation or   notification and event log output.
      capacity         disk to red            Datastore usage alarm.

                       Datastore usage on
                       disk to red
 *1   Heartbeat alarm event might occur frequently owing to VM high load status and VM power control in a
      large-scale environment where many virtual machines exist. This might influence on the performance of
      management servers. Therefore, Heartbeat alarm monitoring is disabled by default.




                                                                SigmaSystemCenter 2.1 Reference Guide
234
Part II                              How   to                                            Use                          the
                                     Commands




This part describes the list and the usage of commands in SigmaSystemCenter.

This part contains the following chapters:


•    3          Details of Action Sequence..................................................................................... 237
•    4          Command Reference.............................................................................................. 243




                                                                                                                              235
3.         Details of Action Sequence




This chapter explains the action sequences.

This chapter contains the following sections:


•    3.1        What is Action Sequence?...................................................................................... 238
•    3.2        Running and Canceling Action Sequence .............................................................. 238
•    3.3        Types of Action Sequence...................................................................................... 239




                                                                                                                             237
3 Details of Action Sequence



3.1. What is Action Sequence?
            An action Sequence is a series of defined processes for machine configuration control.



3.2. Running and Canceling Action Sequence
            SystemProvisioning changes the configuration by running action sequences. There are
            three methods of running action sequences.
             Operation from the Web Console
             Processes by Policy
             Pvmutl Commands (For details of commands, see Section 4.2, "Pvmutl
              Command.")


            An action sequence executes a series of configuration changes as a Job. The action
            sequence can be run even when other action sequences are running. If machines of
            which configurations are changed do not depend on each other, you can change the
            configurations of multiple machines at the same time.
            If the resource is being used for an action sequence that has run earlier, other action
            sequences are suspended. And then, when the action sequence using the resource
            has completed, the suspended action sequence starts.


            Note: The starting order of the suspended action sequences is not always the order
            that the action sequences are suspended. If you want to run the action sequences in
            the order that you demand, you need to demand to run the next action sequence after
            the action sequence that has run earlier has completed.


            You can check a currently running action sequence with the following methods:
             Selecting Job or Dashboard icon in the Monitor tree on the Web Console
             Pvmutl command (For the details of the Pvmutl command, see "Displaying Jobs.")


            You can cancel a currently running action sequence with one of the following methods:
             Selecting Dashboard icon in the Monitor tree on the Web Console and clicking
              Cancel
             Pvmutl command (For the details of the Pvmutl command, see "Canceling Jobs.")


            Note: By canceling an action sequence, the machine may not return to the status
            before executing the action sequence. In that case, delete the machine from the group
            and register it to the group again.




                                                          SigmaSystemCenter 2.1 Reference Guide
238
                                                                                 Types of Action Sequence



3.3. Types of Action Sequence
            The following table shows action sequences.


NO.   Action Sequence Names               Functions                                        Physical   Virtual
      Corresponding            machine                                                     Machine    Machine
      configuration change

1     ChangeServerGroup                   Changes a machine running in the specified       A          N
      Change Machine Usage                group to another usage (move to another
      (Physical Machine)                  group).

2     CreateMachineToGroup                Creates a virtual machine and activates the      N          A
      Activating Machine / Create and     virtual machine in the specified group.
      Assign Machine (Virtual Machine)
3     DeleteManagedVirtualMachine         Deletes an entity of the virtual machine         N          A
                                          standing by as a management target.
4     DeleteVirtualMachine                Makes a virtual machine running in the           N          A
      Delete VM                           group stand by in the shared pool and
                                          deletes an entity of the virtual machine.
5     DistributeSoftwareToMachine         Distributes software to a machine running in     A          A
                                          the group.
6     DistributeSoftwareToMachinesInGro   Distributes software to all machines running     A          A
      up                                  in the group.
7     DistributeSoftwareToMachinesInGro   Distributes the specified software to all        A          A
      upWithScenario                      machines running in the group.
8     DistributeSoftwareToMachineWithS    Distributes the specified software to a          A          A
      cenario                             machine.
9     FailoverVMServer                    Moves the virtual machine(s) on the virtual      N          A
                                          machine server that generated an error to a
                                          different virtual machine server in the group.
10    LoadBalanceVMServer                 Moves the virtual machine(s) on the virtual      N          A
                                          machine server with a high load to a different
                                          virtual machine server in the group and
                                          alleviates the high load.
11    MoveFromGroupToManaged              Deletes and shuts down a machine running         A          A
      Deleting Machine / Release          in the group and makes the machine stand
      Resource (Physical Machine)         by in the shared pool.
                                          A virtual machine server whose settings for a
                                          virtual machine and storage are not enabled
                                          is not shut down.
                                          The deleted machine is removed from the
                                          monitoring target of NEC ESMPRO Manager
                                          (*1).




Part II How to Use the Commands
                                                                                                          239
3 Details of Action Sequence


NO.   Action Sequence Names                  Functions                                       Physical   Virtual
      Corresponding              machine                                                     Machine    Machine
      configuration change

12    MoveFromGroupToPool                    Deletes and shuts down a machine running        A          A
      Deleting Machine / Release             in the group and makes the machine stand
      Resource (Physical Machine)            by in a group pool.
      Deleting Machine / Scale In            A virtual machine server whose settings for a
      (Physical Machine)                     virtual machine and storage are not enabled
                                             is not shut down.
      Deleting Machine / Release
      Resource (Virtual Machine)             The deleted machine is removed from the
                                             monitoring target of NEC ESMPRO Manager
      Deleting Machine / Scale In (Virtual   (*1).
      Machine)
13    MoveFromManagedToPool                  Shuts down and adds a machine in the            A          A
                                             shared pool to the pool of the group.
                                             A virtual machine server whose settings for a
                                             virtual machine and storage are not enabled
                                             is not shut down.
14    MoveFromPoolToGroup                    Activates a machine in the pool of the group    A          A
      Activating Machine / Allocate          to run in the group. Distributes software,
      Machine (Physical Machine)             customizes the machine (*2), and registers
                                             to NEC ESMPRO Manager monitoring target
      Activating Machine / Scale Out         (*1). If automatic registration to DPM is
      (Physical Machine)                     configured, the machine is registered to
      Activating Machine / Allocate          DPM (*3).
      Machine (Virtual Machine)
      Activating Machine / Scale Out
      (Virtual Machine)
15    MoveFromPoolToManaged                  Deletes a machine standing by from the pool     A          A
                                             of the group and makes the machine stand
                                             by in the shared pool.
16    MoveMachine                            Moves a virtual machine to the other virtual    N          A
      Move Virtual Machine (Virtual          machine server.
      Machine)
17    MoveMasterMachineToGroup               Activates a machine standing by in the          A          A
      Activating Machine / Register          shared pool and group pool as a master
      Master Machine (Physical Machine)      machine. Distribution software is not
                                             distributed.
      Activating Machine / Register
      Master Machine (Virtual Machine)       In addition, register to NEC ESMPRO
                                             Manager monitoring target (*1). If automatic
                                             registration to DPM is configured, the
                                             machine is registered to DPM (*3).
18    RebootMachine                          Reboots a machine.                              A          A
      Power Operation to Machine /
      Restart
19    ShutdownMachine                        Shuts down a running machine.                   A          A
      Power Operation to Machine /
      Shutdown
20    StartupMachine                         Starts a stopped machine.                       A          A
      Power Operation to Machine / Start
21    SuspendMachine                         Suspends an active machine.                     A          A
      Power Operation to Machine /
      Suspend



                                                                SigmaSystemCenter 2.1 Reference Guide
240
                                                                                    Types of Action Sequence


NO.   Action Sequence Names                  Functions                                        Physical     Virtual
      Corresponding               machine                                                     Machine      Machine
      configuration change

22    TakeOverMachine                        Replaces a machine running in the group          A            N
      Replace Machine (Physical              with a pool machine. The new machine
      Machine)                               succeeds the information used by the old
                                             machine.
                                             The replaced machine is always made to
                                             stand by in a group pool.)
23    PowerOnMachine                         Power on a stopped machine.                      A *4         N
      Power Operation to machine /
      Power ON
24    PowerOffMachine                        Power off a running machine.                     A *4         N
      Power Operation to machine /
      Power OFF
25    ResetMachine                           Resets a running machine at hardware level.      A *4         N
      Power Operation to machine / Reset
26    PowerCycleMachine                      Power off and then Power on a running            A *4         N
      Power Operation to machine /           machine.
      Power Cycle
27    AcpiShutdownMachine                    Executes ACPI shutdown on a running              A *4,5       N
      Power Operation to machine / ACPI      machine.
      Shutdown
28    DumpMachine                            Send dump demand to a machine.                   A *4,5       N
      Dump Machine
29    LedTurnOnMachine                       Send LED on demand to a running machine.         A *4         N
30    LedTurnOffMachine                      Send LED off demand to a running machine.        A *4         N
*1          This operation is executed only when the target is a physical machine.
*2          If the target is a virtual machine, customizing the machine is executed. If the target is a physical
            machine, it depends on the type of distribution software.
*3          This operation is executed only when the target is a virtual machine.
*4          Out-of-Band Management must be enabled.
*5          OS on a target machine must be configured appropriately.

A: action sequence applicable
N: action sequence not applicable




Part II How to Use the Commands
                                                                                                               241
4.         Command Reference




This chapter explains the command line interface, CLI, which can be executed the operations of
SystemProvisioning from programs, such as Command Prompt.

This chapter contains the following sections:


•    4.1        Command Line Configuration Control by SystemProvisioning............................... 244
•    4.2        Pvmutl Command ................................................................................................... 244




                                                                                                                                 243
4 Command Reference



4.1. Command Line Configuration Control by
     SystemProvisioning
          SystemProvisioning provides a command line tool to use the configuration control of
          the managed machines from the Job management software or other operation
          management software.
          Using the command line tool makes your system operation more flexibly because the
          tool enables you to execute the configuration changing function, such as Replace
          Machine or Change Machine Usage from external software.
          This section provides types and directions of commands.



4.2. Pvmutl Command
          The pvmutl command controls the configuration of SystemProvisioning from the Job
          management software or other operation management software. This subsection
          explains the methods to use pvmutl commands.



4.2.1.    Conditions to Use pvmutl Commands and Supplementary
          Information
          The following conditions must be met when using the pvmutl command:


          The following conditions must be met to use pvmutl commands.
           Only users with administrator rights can execute pvmutl commands.


              Note: If the User Account Control, UAC, is valid, you need to execute with the
              Administrator mode. For example, right-click Command Prompt and click Run as
              administrator to launch the pvmutl commands.


           Group names can be specified in the format of "category\group."
              If a group has no category, the category part can be omitted.
              You can also specify a model in a group. If you specify a model, specify in the
              format of "category\group\model."
           Machine names are specified without group names.


          The execution results of pvmutl commands can be determined by their return values.
          Return values of pvmutl commands are as follows.




                                                        SigmaSystemCenter 2.1 Reference Guide
244
                                                                                          Pvmutl Command



           Values   Success/Fail   Causes

           0        Succeeded
           1        Failed         1. Command format errors, such as insufficient parameters
           2        Failed         1. The specified machine is not found.
                                   2. Active hosts are insufficient or an active host is not found.
                                   3. The specified machine is not a virtual machine. (The command is only
                                   for virtual machines.)
                                   4. The specified machine cannot be moved to a virtual machine server
                                   which is the virtual machine server on which the machine exists. (When
                                   running Migrate)
                                   5. The target virtual machine server is not found. (When creating a virtual
                                   machine or running Migrate)
                                   6. The target Datastore is not found. (When creating a virtual machine)
                                   7. The specified host already exists.
           3        Failed         1. Specified group is not found.
                                   2. The number of hosts registered to the destination group of changing
                                   machine usage is insufficient.
                                   3. The target machine is not found in a pool of the destination group of
                                   changing machine usage.
                                   4. The operation cannot be run in the group that you specified as a
                                   destination.
           4        Failed         1. The number of Host Setting registered to the group is insufficient.
                                   2. Any Host Setting that contains the specified host name (or the IP
                                   address) does not exist in the specified group.
                                   3. Any Host Setting that contains the specified host name (or the IP
                                   address) is being used.
           5        Failed         1. The number of moving machines is insufficient.
                                   2. Machines that is running on the specified host to change machine
                                   usage to do not exist.
                                   3. The specified machine is not found.
           6        Failed         1. SigmaSystemCenter connection error
                                   2. Cannot collect the Job history of started action sequence
                                   * You need to check the logs to determine which of above the cause is.
           7        Failed         1. Failed to run the action sequence (action sequence error).
           8        Failed         1. The specified distribution software is not found.
           9        Failed         1. Executed by a user without administrator authority.
           10       Failed         1. The specified machine already exists. (When creating a virtual
                                   machine.)
           11       Failed         1. The specified machine is already running in a group. (When activating
                                   a virtual machine.)
           14       Failed         1. You do not have the right to change the password.
                                   2. The user account is not found.
           15       Failed         1. The entered characters are too long or include a restricted character.
                                   2. The user name or password is incorrect.
           16       Failed         1. The specified policy is not found.




Part II How to Use the Commands
                                                                                                            245
4 Command Reference



          The following symbols are used in the explanation of the functions of pvmutl
          commands.
           [ ] (brackets) indicate optional items.
           | (vertical line) is a separator indicating that you can select either of the separated
            items.


          Other
           A help message appears when a pvmutl is executed from the command line and
            arguments are omitted.
           The Host Setting, such as a host name and IP address, are represented as IP pool
            on the pvmutl help messages.



4.2.2.    Changing Machine Usage (Moving a Machine)
          Changes usage of a machine between the GroupNameSrc group and the
          GroupNameDest group.
          Activate the machine running in the GroupNameSrc group in the GroupNameDest
          group.
          The target machine must be added to the GroupNameDest group pool to be activated
          in the GroupNameDest group.


          Note: This command cannot be used for a virtual machine.


          Reference: For more detail of Change Machine Usage, see Subsection 1.10.7,
          "Changing Machine Usage (Physical Machine)."


          [Syntax]
                  pvmutl move GroupNameDest GroupNameSrc [HostNameSrc | /c
                  count]




                                                         SigmaSystemCenter 2.1 Reference Guide
246
                                                                                          Pvmutl Command



           [Parameters and Options]


           GroupNameDest                                     Specify the group of new usage.
           (Required)                                        If you do not specify HostNameSrc, you can
                                                             specify a category name alone.
           GroupNameSrc                                      Specify the group of original use.
           (Required)                                        If you do not specify HostNameSrc, you can
                                                             specify a category name alone.
           [HostNameSrc]                                     Specify the host name of the original machine.
                                                             Specify a machine running in GroupNameSrc.
                                                             You can specify a failed machine or machine in
                                                             Maintenance Mode.
                                                             If you do not specify this option, the original
                                                             machine is selected automatically from all the
                                                             machines in GroupNameSrc. In this case, a
                                                             failed machine or machine in Maintenance
                                                             Mode is not selected.
           [/c count]                                        Specify the number of machines to be changed
                                                             the usage. Specify an integer 1 or bigger. If this
                                                             option is not specified, the default value "1" is
                                                             specified.
                                                             In the following cases, the process terminates
                                                             with an error.
                                                             ▪ If a number exceeding the active machine
                                                             units in GroupNameSrc is specified
                                                             ▪ If a number exceeding the number of unused
                                                             Host Setting in GroupNameDest is specified.
           You may not specify HostNameSrc and /c at the same time. If you do not specify either of them, the
           default value "1" is specified to /c.


           [Syntax examples]
                  >pvmutl move Category1 Grp2
                  >pvmutl move Category1\Grp1 Grp2 /c 10
                  >pvmutl move Category1\Grp1 Grp2 host01




Part II How to Use the Commands
                                                                                                           247
4 Command Reference




4.2.3.    Replacing a Machine
          Replaces the HostName machine in the GroupName group with a pool machine.
          The new machine succeeds the machine information of the original machine.


          Note: This command cannot be used for a virtual machine.


          Reference: For more detail of Replace Machine, see Subsection 1.10.6, "Replacing
          Machine (Physical Machine)."


          [Syntax]
                pvmutl replace GroupName HostName


          [Parameters and Options]


          GroupName                                  Specify the target group.
          (Required)                                 Specify a group where the machine specified as
                                                     HostName is running.
                                                     You may not specify a category name alone.
                                                     The new machine is automatically selected from
                                                     the pool of the group specified as GroupName.
                                                     In addition, if the group meets the conditions to
                                                     use a shared pool, machines in the shared pool
                                                     can also be selected.
          HostName                                   Specify the host name of the original machine.
          (Required)                                 Specify the host name of an active machine
                                                     running in the group specified to GroupName.




          [Syntax examples]
                >pvmutl replace Category\Grp1 host01




                                                      SigmaSystemCenter 2.1 Reference Guide
248
                                                                                       Pvmutl Command




4.2.4.     Adding Machine from Pool to Group
           Activates a machine in the GroupName group.
           Single or multiple machines in a pool are added to a group to activate the machines.


           Reference: For more detail of adding a machine, see Subsection 1.10.1, "Activating
           Machine / Allocate Machine (Physical Machine)" or 1.10.9, "Activating Machine /
           Allocate Machine (Virtual Machine)."


           [Syntax]
                  pvmutl add GroupName [MachineName | /c count]


           [Parameters and Options]


           GroupName                                     Specify the target group.
           (Required)                                    If you do not specify MachineName, you can
                                                         specify a category name alone.
                                                         If you do not specify a name of a group or
                                                         model, the target group is automatically
                                                         selected from groups under the specified
                                                         categories or groups with the higher priority.
           [MachineName]                                 Specify the machine in a pool. Only one unit can
                                                         be specified.
                                                         You can specify a pool machine in GroupName
                                                         alone.
                                                         You may not specify a temporary machine.
                                                         If you do not specify this option, the target
                                                         machine is automatically selected from all the
                                                         pool machines in GroupName.
           [/c count]                                    Specify the number of machines to be added
                                                         from the pool. Specify an integer 1 or bigger. If
                                                         this option is not specified, the default value "1"
                                                         is specified.
                                                         In the following cases, the process terminates
                                                         with an error.
                                                         ▪ If a number exceeding the pool machine units
                                                         in GroupName is specified
                                                         ▪ If a number exceeding the number of unused
                                                         Host Setting registered in GroupName is
                                                         specified.
           You may not specify MachineName and /c at the same time.


           [Syntax examples]
                  >pvmutl add Category1
                  >pvmutl add Category1\Grp1\Model1 Machine1
                  >pvmutl add Grp1 /c 10


Part II How to Use the Commands
                                                                                                        249
4 Command Reference




4.2.5.    Adding Machine from Pool to Group Specifying Host
          Information
          Activates a machine in the GroupName group.
          This command adds a machine to a group to activate the machine, specifying a host
          name or IP address defined to the group.


          Reference: For more detail of adding a machine, see Subsection 1.10.1, "Activating
          Machine / Allocate Machine (Physical Machine)" or 1.10.9, "Activating Machine /
          Allocate Machine (Virtual Machine)."


          [Syntax]
                pvmutl addspecname GroupName NetInfo [MachineName]


          [Parameters and Options]


          GroupName                                   Specify the target group.
          (Required)                                  If you do not specify MachineName, you can
                                                      specify a category name alone.
          NetInfo                                     Specify the host name or IP address with which
          (Required)                                  is used when you activate the machine.
                                                      The host name or IP address must be defined to
                                                      the Host Setting of the target group.


          [MachineName]                               Specify the machine in a pool.
                                                      You may specify a pool machine in
                                                      GroupName alone.
                                                      You may not specify a shared pool machine.


          [Syntax examples]
                >pvmutl addspecname Category1\Grp1\Model1 LogicalServer1
                Machine1
                >pvmutl addspecname Grp1 192.168.1.1 Machine1




                                                       SigmaSystemCenter 2.1 Reference Guide
250
                                                                                         Pvmutl Command




4.2.6.     Releasing Machine from a Group to a Pool
           Releases an active machine in the GroupName group to a pool.


           Note: By executing this command without specifying the machine name, the machine
           selected automatically from the active machines is moved to the pool and set to
           standby (shutdown). If a system-specific stop procedure exists, execute the stop
           procedure before stopping the machine, and then run the command, specifying the
           machine name.


           Reference: For more detail of moving a machine to the pool, see Subsection 1.10.4,
           "Deleting Machine / Release Resource (Physical Machine)" or 1.10.12, "Deleting
           Machine / Release Resource (Virtual Machine)."


           [Syntax]
                  pvmutl delete GroupName [HostName | /c count]


           [Parameters and Options]


           GroupName                                        Specify the target group.
           (Required)                                       If you do not specify HostName, you can
                                                            specify a category name alone.
           [HostName]                                       Specify the host name of the machine to
                                                            release.
                                                            If you do not specify this option, the target
                                                            machine is automatically selected from all the
                                                            machines running in the specified group.
                                                            A machine belongs to multiple groups is
                                                            selected preferentially.
           [/c count]                                       Specify the number of machines to release.
                                                            Specify an integer 1 or bigger. If this option is
                                                            not specified, the default value "1" is specified.
                                                            If a number exceeding the active machine units
                                                            in GroupName is specified, the process
                                                            terminates with an error.
           You may not specify HostName and /c at the same time. If you do not specify both of them, the
           default value "1" is specified to /c.


           [Syntax examples]
                  >pvmutl delete Category1
                  >pvmutl delete Grp1 host1
                  >pvmutl delete Grp1 /c 10




Part II How to Use the Commands
                                                                                                          251
4 Command Reference




4.2.7.    Distributing Software in a Group Unit
          Distributes the software to all active machines in the GroupName group.


          [Syntax]
                   pvmutl deploygrp GroupName [/f | /p SoftwareName
                   [,SoftwareName]...] [/seq]


          [Parameters and Options]


          GroupName                                         Specify the target group.
          (Required)
          [/f]                                              Forcibly redistributes the software registered to
                                                            the group (distributes also already distributed
                                                            distribution software).



          [/p SoftwareName]                                 Specify the software to distribute.
                                                            You can also specify the software not registered
                                                            to groups.
                                                            Specify the software name displayed in the
                                                            Resource view on the Web Console surrounded
                                                            in the quotation marks.
                                                            When specifying multiple pieces of software,
                                                            insert a comma between the software.
                                                            Regardless of the distribution status of the
                                                            software registered to the group, only the
                                                            specified software is distributed.
          [/seq]                                            Distributes software sequentially (one by one in
                                                            order). If you do not specify this option, the
                                                            software is distributed all at once.
          You may not specify /p and /f at the same time. If you do not specify both of them, the software
          registered to the group is distributed differentially.
          The software registered to the group indicates software registered to the specified group, model in
          the group, machine, and activated host.


          [Syntax examples]
                   >pvmutl    deploygrp     grp1
                   >pvmutl    deploygrp     grp1    /f /seq
                   >pvmutl    deploygrp     grp1    /f
                   >pvmutl    deploygrp     grp1    /p "soft1"
                   >pvmutl    deploygrp     grp1    /p "soft1","soft2","soft3"




                                                             SigmaSystemCenter 2.1 Reference Guide
252
                                                                                            Pvmutl Command




4.2.8.     Distributing Software Specifying Machine
           Distributes software to the HostName machine in the GroupName group.


           [Syntax]
                  pvmutl deploysrv GroupName HostName
                  [/a Software Name[,SoftwareName]... | /f |
                  /p SoftwareName [,SoftwareName]...]


           [Parameters and Options]


           GroupName                                           Specify the target group.
           (Required)                                          Specify a group where the machine specified as
                                                               HostName is running.
           HostName                                            Specify a name of the host on which you are
           (Required)                                          activating the machine.

           [/a Software]                                       Specify the software to distribute. If you do not
                                                               specify this option, the software registered to
                                                               the group is distributed.
                                                               Specify the software name displayed in the
                                                               Resource view on the Web Console surrounded
                                                               in the quotation marks.
                                                               When specifying multiple pieces of software,
                                                               insert a comma between the software.
           [/f]                                                Forcibly redistributes the software registered to
                                                               the group (distributes also already distributed
                                                               distribution software).
           [/p Software]                                       Specify the software to distribute.
                                                               You can also specify software not registered to
                                                               groups.
                                                               Specify the software name displayed in the
                                                               Resource view on the Web Console surrounded
                                                               in the quotation marks.
                                                               When specifying multiple pieces of software,
                                                               insert a comma between the software.
                                                               Regardless of the distribution status of the
                                                               software registered to the group, only the
                                                               specified software is distributed.
           You can specify only one of /a, /p and /f.
           If you do not specify any of them, the software registered to the group is distributed differentially.
           If you omitted /a and /p, the software registered to the group is distributed.
           The software registered to the group indicates software registered to the specified group and host,
           or the target machine and a model where the machine is.




Part II How to Use the Commands
                                                                                                            253
4 Command Reference



          [Syntax examples]
                >pvmutl    deploysrv    grp1
                >pvmutl    deploysrv    grp1   host01 /a "soft1"
                >pvmutl    deploysrv    grp1   host01 /a "soft1","soft2"
                >pvmutl    deploysrv    grp1   /p "soft1"
                >pvmutl    deploysrv    grp1   /p "soft1","soft2","soft3"
                >pvmutl    deploysrv    grp1   host01 /f



4.2.9.    Executing Specific Software
          Distributes the specified software to the specified managed machine.


          [Syntax]
                pvmutl deploypsv MachineName
                Software Name[,SoftwareName]...


          [Parameters and Options]


          MachineName                                 Specify a name of the managed machine.
          (Required)
          Software                                    Specify the software to distribute.
          (Required)                                  Specify the software name displayed in the
                                                      Resource view on the Web Console surrounded
                                                      in the quotation marks.
                                                      When specifying multiple pieces of software,
                                                      insert a comma between the software.


          [Syntax examples]
                >pvmutl deploypsv Machine01 "soft1"
                >pvmutl deploypsv Machine01 "soft1","soft2"




                                                       SigmaSystemCenter 2.1 Reference Guide
254
                                                                                     Pvmutl Command




4.2.10. Setting Maintenance Mode On or Off
           Changes the maintenance mode of a running machine in GroupName group.
           If the specified mode has set, the mode remains unchanged.


           [Syntax]
                  pvmutl maintenance {On|Off} GroupName [HostName]


           [Parameters and Options]


           On                                            Sets in the maintenance mode.
           (Required to select)
           Off                                           Releases the maintenance mode.
           (Required to select)
           GroupName                                     Specify the target group.
           (Required)
           [HostName]                                    Specify a name of the host on which you are
                                                         activating the machine.
                                                         You may not specify a pool machine. If you do
                                                         not specify this option, all the machines running
                                                         in the group become the targets.


           [Syntax examples]
                  >pvmutl maintenance on grp1
                  >pvmutl maintenance off grp1 host01



4.2.11. Displaying Groups in List
           Displays a list of groups and categories. The different levels are shown with indents.


           [Syntax]
                  pvmutl list group


           [Parameters and Options]
           Parameters are not variable.




Part II How to Use the Commands
                                                                                                      255
4 Command Reference



          [List result sample]
          If a group is defined as follow,
              group1 ← group
                   Model1_1 ← a model in the group1
                   Model1_2 ← a model in the group1
              group2 ← group
                   Model2_1 ← a model in the group2
                   Model2_2 ← a model in the group2
          The list looks will be displayed as shown below.


                ================
                ServerGroup List
                ================
                group1
                      model1_1
                      model1_2
                group2
                      model2_1
                      model2_2




                                                        SigmaSystemCenter 2.1 Reference Guide
256
                                                                                  Pvmutl Command




4.2.12. Displaying Machines Registered to a Group in List
           Lists machines registered in the model in the GroupName group. Pool machines are
           also listed. If the GroupName is a category, machines in models in all groups
           registered in the category. If the GroupName is a model name, machines are listed as
           well.


           [Syntax]
                 pvmutl list server GroupName


           [Parameters]


           GroupName                                  Specify the target group.
           (Required)



           [List result sample]
                 ===============================
                 Server List (Group = GroupName)
                 ===============================
                 Machine1
                 Machine 2

                 ===========
                 Pool
                 ===========
                 Machine 3


           [Syntax examples]
                 pvmutl list server grp1




Part II How to Use the Commands
                                                                                             257
4 Command Reference




4.2.13. Displaying Software Registered to a Group in List
          Lists distribution software registered to the group.
          Software registered to the models in the group is listed as well.


          [Syntax]
                pvmutl list soft GroupName


          [Parameters and Options]


          GroupName                                      Specify the target group.
          (Required)



          [List result sample]
                ====================================
                Soft List (Group = GroupName)
                ====================================
                Soft1
                Soft2


          [Syntax examples]
                >pvmutl list soft grp1




                                                          SigmaSystemCenter 2.1 Reference Guide
258
                                                                                  Pvmutl Command




4.2.14. Shutting a Machine Down
           Shuts down the machine running with HostName in the GroupName group.
           The operation is not executed to a machine that has already shut down.


           [Syntax]
                 pvmutl shutdown GroupName [HostName...]


           [Parameters and Options]


           GroupName                                   Specify the target group.
           (Required)                                  Specify a group where the host specified as
                                                       HostName is running.
                                                       If you do not specify HostName, you can
                                                       specify a category name alone.
           [HostName...]                               Specify the host name of the machine to shut
                                                       down. You can specify multiple hosts.
                                                       You may not specify a pool machine.


           [Syntax examples]
                 >pvmutl shutdown grp1 host01
                 >pvmutl shutdown grp1 host01 host02 host03
                 >pvmutl shutdown grp1




Part II How to Use the Commands
                                                                                                 259
4 Command Reference




4.2.15. Rebooting a Machine
          Reboots the machine running with HostName in the GroupName group.
          The operation is executed to a machine which power is OFF.


          Note: If a managed machine is VMware virtual machine, you can specify the quick start
          option.
          The quick start executes simplified power on completion confirmation process. So the
          possibility of operation's ending with an error becomes higher than the normal start
          operation in the case that a machine cannot be used after the operation's completion,
          for example. However, the process of the operation completes faster.


          [Syntax]
                 pvmutl reboot GroupName [HostName...] [/q]


          [Parameters and Options]


          GroupName                                    Specify the target group.
          (Required)                                   Specify a group where the host specified as
                                                       HostName is running.
                                                       If you do not specify HostName, you can
                                                       specify a category name alone.
          [HostName...]                                Specify the host name of the machine to reboot.
                                                       You can specify multiple hosts.
                                                       You may not specify a pool machine.
          [/q]                                         Executes the process of checking start of the
                                                       machine simplistically. This can completes the
                                                       process more quickly compared from when this
                                                       option is not specified.
                                                       This option can be enabled to only a VMware
                                                       virtual machine.


          [Syntax examples]
                 >pvmutl   reboot   grp1   host01
                 >pvmutl   reboot   grp1   host01 host02 host03
                 >pvmutl   reboot   grp1
                 >pvmutl   reboot   grp1   host01 /q
                 >pvmutl   reboot   grp1   /q




                                                        SigmaSystemCenter 2.1 Reference Guide
260
                                                                                   Pvmutl Command




4.2.16. Powering On a Machine
           Powers on the machine to run with HostName in the GroupName group.
           The operation is not executed to a machine that has already powered ON.


           Note: If a managed machine is VMware virtual machine, you can specify the quick start
           option.
           The quick start executes simplified power on completion confirmation process. So the
           possibility of operation's ending with an error becomes higher than the normal start
           operation in the case that a machine cannot be used after the operation's completion,
           for example. However, the process of the operation completes faster.


           [Syntax]
                  pvmutl poweron GroupName [HostName...] [/q]


           [Parameters and Options]


           GroupName                                    Specify the target group.
           (Required)                                   Specify a group where the host specified as
                                                        HostName is running.
                                                        If you do not specify HostName, you can
                                                        specify a category name alone.
           [HostName...]                                Specify the host name of the machine to reboot.
                                                        You can specify multiple hosts.
                                                        You may not specify a pool machine.
           [/q]                                         Executes the process of checking start of the
                                                        machine simplistically. This can completes the
                                                        process more quickly compared from when this
                                                        option is not specified.
                                                        This option can be enabled to only a VMware
                                                        virtual machine.


           [Syntax examples]
                  >pvmutl   poweron    grp1   host01
                  >pvmutl   poweron    grp1   host01 host02 host03
                  >pvmutl   poweron    grp1
                  >pvmutl   poweron    grp1   host01 /q
                  >pvmutl   poweron    grp1   /q




Part II How to Use the Commands
                                                                                                  261
4 Command Reference




4.2.17. Creating a Machine (Creating Machine in Group) (for
          Virtual Machine)
          Creates and activates a virtual machine in the GroupName group.
          In addition, you can register a virtual machine that is already set up in the shared pool
          as a master machine with an option. In this case, distribution software is not distributed.


          Reference: For the details of Register Master Machine, see Subsection 1.10.11,
          "Activating Machine / Register Master Machine (Virtual Machine)."


          Note: This command creates one virtual machine unit. Multiple units cannot be created
          simultaneously.
          This command is exclusive to virtual machines and cannot be used for any other
          machine.
          If the settings for the machine registration to DPM are configured to the target group of
          VM creation and software distribution by DPM is configured, the machine is registered
          to DPM first, and then software is distributed by DPM.
          The virtual machine server name and Datastore name displayed on the Virtual tree on
          the Web Console might be different from those displayed on the vCenter Server or
          XenCenter screen.
          Use the name that is displayed on the Web Console for the parameter specified with
          pvmutl.
          E.g.) The IP address name is specified to VMSName.
               The Datastore Name includes a bracket "[ ]" or colon ":".
          If you enclose a string whose last character is \ (backslash) in " " (double quotation
          marks), escape the last character with another \ (backslash).
          E.g.) If a Datastore name is "[cluster1] C:\ClusterStorage\Volume1\", the command will
          be:
               pvmutl vmdadd vmgroup vm1 /VMS host1.example.net /DATASTORE "[cluster1]
          C:\ClusterStorage\Volume1\\"


          [Syntax]
                pvmutl vmadd GroupName VMName
                [/VMS VMSName [/DATASTORE DatastoreName |
                /VMFS VMFSName] ] [/NETINFO NetInfo] [/a]


          [Parameters and Options]




                                                          SigmaSystemCenter 2.1 Reference Guide
262
                                                                          Pvmutl Command



           GroupName                          Specify the group where the machine will be
           (Required)                         created.
                                              If you do not specify a model, the model is
                                              selected from the models with higher priority in
                                              the specified group.
                                              You may not specify a category alone.
           VMName                             Specify the virtual machine to create.
           (Required)                         You may not specify the already existing virtual
                                              machine name.
           [/VMS VMSName]                     Specify the virtual machine server name.
                                              If you do not specify this option, a virtual
                                              machine server corresponding to the group to
                                              be created is automatically selected.
           [/DATASTORE DatastoreName]         Specify the Datastore name on which the virtual
                                              machine is created. If you specify this option,
                                              you need to specify the virtual machine server
                                              also.
                                              Specify a name of the Datastore which is on the
                                              specified virtual machine server.
                                              Specify the exact Datastore name. If the name
                                              includes a bracket or colon, specify them also.
                                              If you specify a Datastore, you need to specify
                                              VMS. If you do not specify this option, a
                                              Datastore corresponding to the group to be
                                              created is automatically selected.
           [/VMFS VMFSName]                   This /VMFS option is a substitute for the
                                              /DATASTORE option. If you specify the both,
                                              the system gives priority to the DATASTORE
                                              option. This option remains for compatibility.
           [/NETINFO NetInfo]                 Specify a host name or IP address to be
                                              allocated to the machine.
                                              The host name or IP address needs to be
                                              already specified to the Host Setting of the
                                              group to be created.
                                              Specify the IP address in the format of
                                              "xxx.xxx.xxx.xxx."
                                              If you do not specify this option, a host name or
                                              IP address is automatically selected from the
                                              Host Setting defined to the group to be created.
           [/a]                               Activates a virtual machine that has already
                                              created in a group as a master machine without
                                              creating a new virtual machine.
                                              If you specify this option, you need to specify
                                              the /NETINFO option as well.


           [Syntax examples]
                  >pvmutl vmadd Category1\Grp1 VM01 /VMS Vms01 /DATASTORE
                  [VMFS01] /NETINFO 192.168.1.100
                  >pvmutl vmadd Category1\Grp1 VM01 /VMS Vms01 /NETINFO
                  192.168.1.100
                  >pvmutl vmadd Category1\Grp1\Model1 VM01 /NETINFO
                  192.168.1.100 /a

Part II How to Use the Commands
                                                                                           263
4 Command Reference




4.2.18. Deleting a Machine (for Virtual Machine)
          Deletes a virtual machine running in the GroupName group.
          In addition, you can delete the virtual machine from the group and move the machine to
          the shared pool with an option.


          Reference: For the detail of deleting a machine, see Subsection 1.10.12, "Deleting
          Machine / Release Resource (Virtual Machine)."


          Note: This command deletes one virtual machine. You cannot delete multiple virtual
          machines simultaneously with this command.
          This command is exclusive to virtual machines and cannot be used for any other
          machine.


          [Syntax]
                 pvmutl vmdelete GroupName [HostName] [/d] [/u]


          [Parameters and Options]


          GroupName                                   Specify the group to delete.
          (Required)                                  If you do not specify HostName, you can specify
                                                      a category name alone.
                                                      If you do not specify a name of a group or
                                                      model, the target group is automatically
                                                      selected from groups under the specified
                                                      categories or groups with the lower priority.
          [HostName]                                  Specify the host name of the machine to delete.
                                                      Specify the machine running in GroupName.
                                                      If you do not specify this option, the machine is
                                                      automatically selected from all the machines
                                                      running in GroupName.
          [/d]                                        Executes only deletion from a group.
                                                      A machine belongs to multiple groups is
                                                      selected preferentially and automatically in
                                                      machines running in the group.
          [/u]                                        Deletes the virtual machine without deleting its
                                                      virtual disk.
                                                      If you do not specify this option, the virtual disk
                                                      is deleted.


          [Syntax examples]
                 >pvmutl vmdelete Category\Grp1 host01 /d
                 >pvmutl vmdelete Category



                                                       SigmaSystemCenter 2.1 Reference Guide
264
                                                                                       Pvmutl Command




4.2.19. Moving a Machine (Only Migrate) (for Virtual Machine)
           Moves a specified virtual machine to a different virtual machine server.
           Only execute Migrate process.


           Reference: For the detail of moving a machine, see Subsection 1.10.15, "Move Virtual
           Machine (Virtual Machine)."


           Note: This command moves one virtual machine. You cannot move multiple virtual
           machines simultaneously with this command.
           This command is exclusive to virtual machines and cannot be used for any other
           machine.
           To move a running machine with Migrate, you need the SAN environment. For more
           details, see product manuals of VMware, Inc.


           [Syntax]
                  pvmutl vmmigrate GroupName HostName VMSName [/n]


           [Parameters and Options]


           GroupName                                     Specify the group where the target machine
           (Required)                                    exists.
                                                         You may not specify a category alone.
           HostName                                      Specify the host name of the machine to move.
           (Required)                                    You may not specify the inactive machine.
           VMSName                                       Specify the destination virtual machine server.
           (Required)
           [/n]                                          By specifying this option, the target virtual
                                                         machine is not started after move.
                                                         If you do not specify this option, the virtual
                                                         machine is started after move.


           [Syntax examples]
                  >pvmutl vmmigrate Category1\Grp1 host01 VMS01
                  >pvmutl vmmigrate Category1\Grp1 host01 VMS01 /n




Part II How to Use the Commands
                                                                                                          265
4 Command Reference




4.2.20. Moving a Machine (If Migrate Fails, Move) (for Virtual
          Machine)
          Moves a specified virtual machine to a different virtual machine server.
          First, tries the Migrate process, and if it fails, starts the Move process.
          This operation does not execute Failover.


          Reference: For the detail of moving a machine, see Subsection 1.10.15, "Move Virtual
          Machine (Virtual Machine)."


          Note: This command creates one virtual machine unit. Multiple units cannot be created
          simultaneously.
          This command is exclusive to virtual machine and cannot be used for any other
          machine.
          Moving an active machine using the Migrate process requires a SAN environment. For
          the details of the SAN environment, see product manuals of VMware, Inc.


          [Syntax]
                 pvmutl vmmigrateandmove GroupName HostName VMSName [/n]


          [Parameters and Options]


          GroupName                                       Specify the group where the target machine
          (Required)                                      exists.
                                                          You may not specify a category alone.
          HostName                                        Specify the host name of the machine to move.
          (Required)                                      You may not specify the inactive machine.
          VMSName                                         Specify the destination virtual machine server.
          (Required)
          [/n]                                            By specifying this option, the target virtual
                                                          machine is not started after move.
                                                          If you do not specify this option, the virtual
                                                          machine is started after move.


          [Syntax examples]
                 >pvmutl vmmigrateandmove Category1\Grp1 host01 VMS01
                 >pvmutl vmmigrateandmove Category1\Grp1 host01 VMS01 /n




                                                           SigmaSystemCenter 2.1 Reference Guide
266
                                                                                   Pvmutl Command




4.2.21. Job Commands
           Job commands manage Job status.
           This subsection provides the details of the Job commands.


            Displaying Jobs
               Lists Jobs of running action sequences and their running status.


               [Syntax]
                 pvmutl asjob [-a | -s | -d]


               [Parameters and options]


               None                                       Lists Jobs of main action sequences and their
                                                          running status.
               [-a]                                       Lists Jobs of all running action sequences
                                                          and their running status.
               [-s]                                       Displays running phase names in addition to
                                                          the information specified with -a option.
               [-d]                                       Displays entered parameters in addition to
                                                          the information specified with -s option.


               [List sample]
               Displays as follows:
                 >pvmutl asjob

                 JobID Progress(%) StartTime         ActionSequence Name
                 -----+----------+------------------+------------------
                 00011 50        2003/12/01 13:05:25 ChangeServerGroup
                 00012 75        2003/12/01 12:50:31 MoveFromPoolToGroup

                 Total job : 2


               [Syntax examples]
                 pvmutl asjob




Part II How to Use the Commands
                                                                                                   267
4 Command Reference



           Canceling Jobs
              After displays the list of the Jobs with the asjob command, specify the JobID of the
              action sequence that you want to cancel.


              [Syntax]
                pvmutl ascancel [JobID]


              [Parameters and options]


              None                                       Lists Job IDs of running action sequences.
              [JobID]                                    Specify the JobID of the action sequence to
                                                         suspend. If you do not specify the option, the
                                                         list of Jobs is displayed.


              [Syntax examples]
              Displays as follows:
                >pvmutl ascancel

                ========================================
                ActionSequence List
                ========================================
                00011
                00012

                >pvmutl ascancel 00011


              [Syntax examples]
                pvmutl ascancel
                pvmutl ascancel 00011




                                                        SigmaSystemCenter 2.1 Reference Guide
268
                                                                                    Pvmutl Command




4.2.22. Changing a Password for a User Account
           Changes a password for a specified user account.


           [Syntax]
                 pvmutl changepassword UserName OldPassword NewPassword


           [Parameters and options]


           UserName                                   Specify the user name.
           (Required)
           OldPassword                                Specify the old password.
           (Required)
           NewPassword                                Specify the new password.
           (Required)


           [Syntax examples]
                 >pvmutl changepassword user01 pvmuser1 pvmuser2



4.2.23. Outputting Policies in List
           Lists policies registered in a group.


           [Syntax]
                 pvmutl policy show [GroupName]


           [Parameters and options]


           [GroupName]                                Specify the target group. If you specify a
                                                      category, all the groups in the category become
                                                      the targets.
                                                      If you do not specify this option, a list of all the
                                                      policies is displayed.




Part II How to Use the Commands
                                                                                                     269
4 Command Reference



          [Syntax examples]
          Displays as follows:


           When you specified a category:
                 group1-1 : policy1
                      model1 : policy1-1
                      model2 : policy1-2
                 group1-2 : policy2
                      model1 :


           When you specified a group:
                 group1-1 : policy1
                      model1 : policy1-1
                      model2 : policy1-2


           When you did not specify a group:
                 policy1 : Workinggroup Policy1
                 policy2 : Workinggroup Policy2
                 policy3 : System administration group Policy



4.2.24. Changing a Group Policy
          Changes a policy registered to a group.


          [Syntax]
                 pvmutl policy set GroupName [PolicyName] [/y]


          [Parameters and options]


          GroupName                                 Specify the target group.
          (Required)
          [PolicyName]                              Specify a name of the policy to change.
                                                    If you do not specify this option, the policy is
                                                    released from the group.
          [/y]                                      Skips confirmation message for the change or
                                                    release.


          [Syntax examples]
                 >pvmutl policy set grp1 policy2
                 >pvmutl policy set grp1
                 >pvmutl policy set grp1 /y




                                                     SigmaSystemCenter 2.1 Reference Guide
270
                                                                               Pvmutl Command




4.2.25. Output Format of Progressing Status
           This subsection explains the output format of progressing status.
           The following is an example of range of output when using power on command.


           1.   Error output
                After executing a command, when an error of an action is generated,
                SystemProvisioning outputs the error.


                 >pvmutl poweron category\group host1 host2 host3
                   JOB ID:00100 PROGRESS[10] PHASE:xxxxxxx
                   JOB ID:00100 PROGRESS[30] PHASE:xxxxxxx
                   Startup (host2) was failed. ->time out


           2.   Result status and summary of action
                After executing a command, SystemProvisioning outputs result status and
                summary of the action.


                   JOB ID:00100 PROGRESS [50] PHASE:xxxxxxx
                   JOB ID:00100 PROGRESS [100] PHASE:xxxxxxx
                   -------------------------------------------
                 [Success] starting up the machine(host1)
                 [AbnormalTermination] starting up the machine(host2)
                 [Success] starting up the machine(host3)


           3.   Number of the result status
                After executing a command, SystemProvisioning outputs the number of the
                execution result status.
                This example indicates "two Success and one Failure"


                 Success : 2
                 Failure : 1


           4.   Return value of the command
                After executing a command, the return value of the command is displayed.
                In this example, because a machine is aborted, 7, which means there was an
                action execution error, is displayed as a return value.


                 Execution end           code:7




Part II How to Use the Commands
                                                                                           271
Part III                                Maintenance Information




This part describes the maintenance of SigmaSystemCenter.

This part contains the following chapters:


•    5          Error Events and Policy Actions ............................................................................. 275
•    6          Caution Notes ......................................................................................................... 367
•    7          Trouble Shooting .................................................................................................... 407
•    8          Logs ........................................................................................................................ 433




                                                                                                                                            273
5.         Error Events and Policy Actions




This chapter explains the errors that SigmaSystemCenter can detect and the details of policy
actions to which corresponding event handler settings to the assumable errors can be configured.

This chapter contains the following sections:


•    5.1        Event Monitoring and Policy ................................................................................... 276
•    5.2        Events SigmaSystemCenter Can Detect................................................................ 277
•    5.3        Policy Setting .......................................................................................................... 325
•    5.4        Configuring Actions................................................................................................. 326
•    5.5        Investigation Function............................................................................................. 330
•    5.6        About Standard Policy ............................................................................................ 336
•    5.7        List of Policy Actions............................................................................................... 356




                                                                                                                                        275
5 Error Events and Policy Actions



5.1. Event Monitoring and Policy
            SigmaSystemCenter can monitor events and performance of managed machines. It
            can also change configuration of machines to restore from an event or error and notify
            a user that an event or error occurred.
            SigmaSystemCenter works with multiple compatible products and components, such
            as NEC ESMPRO Manager, NEC ESMPRO Agent, VMware vCenter Server, and
            System Monitor - Performance Monitoring Services for monitoring the running status,
            events, and performance of managed machines. If a compatible product or component
            detects a status change of a managed machine, it notifies the event to the policy
            control processing of SigmaSystemCenter.
            The policy control processing of SigmaSystemCenter outputs the event information to
            Operation Logs, and then, executes the processing to cope with the event according to
            policy setting.
            You can set actions to execute for each event, order to process events, and execution
            conditions to policy setting. In addition, you can assign policy setting to each operation
            group and model.




                                                           SigmaSystemCenter 2.1 Reference Guide
276
                                                             Events SigmaSystemCenter Can Detect



5.2. Events SigmaSystemCenter Can Detect
            Monitoring products and components that SigmaSystemCenter can work with and what
            they monitors are as follows,


             NEC ESMPRO Manager, NEC ESMPRO Agent
                 NEC ESMPRO Manager requests NEC ESMPRO Agent on a managed machine
                 to acquire information by SNMP periodically and if NEC ESMPRO Manager cannot
                 acquire the information, NEC ESMPRO Manager regards that the managed
                 machine is down and notifies Machine inaccessible error event to the policy control
                 processing of SigmaSystemCenter.
                 NEC ESMPRO Manager can also monitor boot disk I/O periodically by installing an
                 additional dedicated monitoring module. If a boot disk I/O error occurs, NEC
                 ESMPRO Manager notifies the policy control processing of SigmaSystemCenter of
                 Machine inaccessible error event.
                 In addition, if the monitoring module of the HDD access impossible is installed with
                 NEC ESMPRO Agent on a machine, NEC ESMPRO Agent can detect the server
                 access impossible even when a HDD cannot be accessed.
                 NEC ESMPRO Manager can also monitor the threshold of the statistical
                 information of each resource just like System Monitor - Performance Monitoring
                 Services described below.


                 In addition, if you install HDD Access Monitoring Module on the same machine to
                 which NEC ESMPRO Manager is installed, even when the machine cannot access
                 to the HDD, NEC ESMPRO Manager can enhance the accuracy of detecting
                 machine's inaccessibility.


                 Reference: For the details of or how to obtain the HDD Access Monitoring Module,
                 inquire of our sales representative.


             System Monitor - Performance Monitoring Services
              System Monitor - Performance Monitoring Services notifies to the policy control
              processing of SigmaSystemCenter when statistics on CPU load factor of a
              managed machine, a status of utilization, such as disk utilization, or statistics
              information of multiple machines in a group exceeds the threshold value.
              In addition, it is System Monitor - Performance Monitoring Services that monitors
              virtual machine servers for high or low load alert that triggers the actions of the VM
              Optimized Placement.


             Monitoring through VMware vCenter Server
              SigmaSystemCenter can monitor the following through vCenter Server.
                 •   Connection check of a virtual machine server (VMware)
                 •   CPU usage rate of a virtual machine server (VMware)
                 •   Memory usage rate of a virtual machine server (VMware)

Part III Maintenance Information
                                                                                                  277
5 Error Events and Policy Actions

                 •   Heartbeat status of a virtual machine (VMware)
                 •   CPU usage rate of a virtual machine (VMware)
                 •   Memory usage rate of a virtual machine (VMware)
                 •   Datastore usage rate
                 •   Allocation rate of disk on a Datastore
                 •   Status of the connection to a Datastore
                 •   Status of the connection to a network


                 When a failure occurs, an alert is generated in vCenter Server. If an alert related to
                 above is generated, SigmaSystemCenter notifies it to the policy control
                 processing.


             Monitoring VMware ESXi
              If a managed machine is VMware ESXi, SigmaSystemCenter monitors the
              machine directly by connecting remotely to monitor its running status.
              To monitor the existence of a machine, SigmaSystemCenter checks the
              connection from a management server to VMware ESXi. If the connection is
              disconnected, the component notifies Machine inaccessible error event to the
              policy control processing of SigmaSystemCenter and if the connection recovers,
              SigmaSystemCenter notifies a Machine inaccessible error recovery event to its
              policy control processing. In addition, SigmaSystemCenter checks the disk access
              status periodically and if the check fails, SigmaSystemCenter notifies a Hard disk
              failure event to its policy control processing.


             Optimized Placement function
              The Optimized Placement provides the load balancing function. When the load
              balancing function determines that high load status cannot be resolved even if all
              virtual machine servers in a group are used, it notifies SigmaSystemCenter’s
              policy control processing of Scaleout Recommendation event.


             Out-of-Band Management
                 Out-Of-Band Management receives PET directly from BMC of managed machines
                 and manages them to detect abnormality and failure in hardware. Out-Of-Band
                 Management can detect an event corresponds to the hardware failure event that is
                 detected by NEC ESMPRO Manager and NEC ESMPRO Agent. The difference is
                 Out-of-Band Management does not use services on OS. Therefore, Out-Of-Band
                 Management can detect hardware failure events even when OS cannot be
                 accessed.


                 Out-Of-Band Management monitors voltages and temperatures of chassis and
                 predicts that hardware will be in critical failure status to notify the policy control
                 processing of SigmaSystemCenter of HW Predictive events




                                                              SigmaSystemCenter 2.1 Reference Guide
278
                                                             Events SigmaSystemCenter Can Detect



                 Note: A managed machine where NEC ESMPRO Agent is installed does not send
                 PET but sends NEC ESMPRO Agent's reports. However, both ESMPRO Agent's
                 reports and PET might be sent depending on the timing of hardware failures. Even
                 if this is the case, Out-of-Band Management events will not occur on the machine
                 managed by NEC ESMPRO Agent.


             Monitoring through Microsoft Failover Cluster
                 If a managed machine is a Hyper-V virtual machine server or a Hyper-V virtual
                 machine managed by Microsoft Failover Cluster, SigmaSystemCenter obtains
                 events from Microsoft Failover Cluster and notifies the policy control processing of
                 SigmaSystemCenter of the events.
                 In order to register a machine to monitor with SigmaSystemCenter, add its
                 Hyper-V Cluster as a subsystem.
                 Microsoft Failover Cluster is a high-available system and so are the running virtual
                 machines running on it. For example, when a virtual machine fails, Microsoft
                 Failover Cluster failovers the virtual machine to another node. The role of
                 SigmaSystemCenter regarding Microsoft Failover Cluster events is to obtain
                 events detected by Microsoft Failover Cluster such as node down and virtual
                 machine failure, update the database with the information, and notify system
                 administrators of the events.


            This section explains the events that these products or component can detect and the
            checking procedure of detected events.




Part III Maintenance Information
                                                                                                  279
5 Error Events and Policy Actions




5.2.1.       Events NEC ESMPRO Manager Can Detect
              The following table shows the error events that NEC ESMPRO Manager can detect.
              You can check the following error events by specifying "SystemMonitorEvent" in the
              Report Source box on the Corresponding Event Handler Settings window, and a value
              that the Source Name in the following table and the event ID are combined, for
              example, ESM MYLEX SERVICE[0X80040205], is displayed in the Event box on the
              window.


Event Category        Events NEC ESMPRO Manager Can Detect

                      Source Name             Event ID        Description

Hard disk recovery    ESM MYLEX SERVICE       0X80040205      System Drive CRITICAL
failure
                      ESMDISKARRAY            0X800403E9      Disk Array Logical Device Critical
                      ASMBENOTIFY             0X0000200C      Member is down on array
                      ASMBENOTIFY             0X0000200D      Member is missing on array
                      ASMBENOTIFY             0X0000200E      Array is off-line; member failed
                      ASMBENOTIFY             0X00002023      Array is critical
                      ASMBENOTIFY             0X0000205C      Array is still critical
                      ASMBENOTIFY             0X0000B00E      Device is failed
                      ASMBENOTIFY             0X0000B033      Array is degraded
                      ASMBENOTIFY             0X0000B034      Second-level array is degraded
                      ASMBENOTIFY             0X0000B036      Array is degraded
                      ASMBENOTIFY             0X0000B037      Second-level array is degraded
Hard disk             ESM MYLEX SERVICE       0XC0040200      Physical Device DEAD
replacement failure
                      ESMDISKARRAY            0XC00403F3      Disk Array Physical Device Dead
                      ESMDISKARRAY            0X800403FC      Disk Array Physical Device S.M.A.R.T.
                                                              Error
                      ESMSTORAGESERVICE       0X800403E8      Hard Disk Failure Prediction:Exceed
                                                              Threshold
                      ESMSTORAGESERVICE       0X800403E9      Hard Disk Failure Prediction:S.M.A.R.T.
                                                              Error
                      ESM STORAGE             0XC00423F6      HD:Fatal Recovered Error
                      SERVICE
                      ESM STORAGE             0X800423F5      HD:Warning Recovered Error
                      SERVICE
                      ESM STORAGE             0XC00423F8      HD:Fatal Not Ready Error
                      SERVICE
                      ESM STORAGE             0X800423F7      HD:Warning Not Ready Error
                      SERVICE
                      ESM STORAGE             0XC00423FA      HD:Fatal Medium Error
                      SERVICE
                      ESM STORAGE             0X800423F9      HD:Warning Medium Error
                      SERVICE
                                                           SigmaSystemCenter 2.1 Reference Guide
280
                                                        Events SigmaSystemCenter Can Detect


Event Category       Events NEC ESMPRO Manager Can Detect

                     Source Name           Event ID         Description

                     ESM STORAGE           0XC00423FC       HD:Fatal Hardware Error
                     SERVICE
                     ESM STORAGE           0X800423FB       HD:Warning Hardware Error
                     SERVICE
                     ASMBENOTIFY           0X00002014       Reconstruct aborted due to I/O error
                     ASMBENOTIFY           0X00002017       Verify aborted due to I/O error, no
                                                            miscompares
                     ASMBENOTIFY           0X00002019       Initialize aborted due to I/O error
                     ASMBENOTIFY           0X0000202D       Reconstruct failed to start due to I/O error
                     ASMBENOTIFY           0X00002035       Update of array drives failed after Initialize
                     ASMBENOTIFY           0X00002038       Scheduled Reconstruct failed to start
                     ASMBENOTIFY           0X00002039       Scheduled Verify failed to start
                     ASMBENOTIFY           0X0000204E       Verify utility failed to start
                     ASMBENOTIFY           0X00002059       Dedicated spare not functional
                     ASMBENOTIFY           0X00002085       Verify aborted due to I/O error with fixed
                                                            miscompares
                     ASMBENOTIFY           0X00002090       Recovered error: SMART event received
                                                            for array
                     ASMBENOTIFY           0X00002091       Recovered error: SMART event received
                                                            for device
                     ASMBENOTIFY           0X00002094       I/O error aborted Verify, unfixed
                                                            miscompares
                     ASMBENOTIFY           0X000020AD       Device is down. A Hard Drive is down or
                                                            no longer responding.
                     ASMBENOTIFY           0X0000B069       Array is dead
                     ASMBENOTIFY           0X0000B090       Non-corrected ECC error found
                     ASMBENOTIFY           0X0000B11E       Channel offline
                     ASMBENOTIFY           0X0000B11F       Channel offline
                     ASMBENOTIFY           0X0000B121       Channel offline
                     ASMBENOTIFY           0X0000B122       Channel offline
                     ASMBENOTIFY           0X0000B123       Channel offline
Hard disk failure    ESM MYLEX SERVICE     0XC0040206       System Drive OFFLINE
                     ESMDISKARRAY          0XC00403EA       Disk Array Logical Device Offline
                     ASMBENOTIFY           0X0000200F       Array is off-line
                     ASMBENOTIFY           0X0000B057       Array is dead
                     ASMBENOTIFY           0X0000B058       Second-level array is dead
                     ASMBENOTIFY           0X0000B05A       Array is dead
                     ASMBENOTIFY           0X0000B05B       Second-level array is dead
                     ASMBENOTIFY           0X0000B06A       Second-level array is dead
CPU load failure     ESMCPUPERF            0XC0000064       CPU Load Error


Part III Maintenance Information
                                                                                                     281
5 Error Events and Policy Actions


Event Category         Events NEC ESMPRO Manager Can Detect

                       Source Name           Event ID         Description

                       ESMCPUPERF            0XC0000068       CPU Load Error
                       ESMCPUPERF            0X80000066       CPU Load Warning
                       ESMCPUPERF            0X8000006A       CPU Load Warning
CPU degeneracy         ESMCOMMONSERVICE      0X800002BD       CPU Reduce
failure
                       ESMCOMMONSERVICE      0X800002BF       CPU Reduce
                       ESMCOMMONSERVICE      0XC0000838       CPU Module FRB
CPU failure            ESMCOMMONSERVICE      0XC0000451       CPU Internal error
                       ESMCOMMONSERVICE      0XC0000454       CPU thermal trip event
                       ESMCOMMONSERVICE      0XC0000523       Processor Disabled
                       ESMCOMMONSERVICE      0X40000837       CPU Module Broken
                       ESMCOMMONSERVICE      0XC0000B04       CPU Self-Test Error
                       ESMCOMMONSERVICE      0X80000B03       Processor Warning
                       ESMCOMMONSERVICE      0XC0000B07       CPU Initialize Error
CPU temperature        ESMCOMMONSERVICE      0XC0000454       CPU thermal trip event
failure
Memory                 ESMCOMMONSERVICE      0X800002BE       Memory Reduce
degeneration failure
                       ESMCOMMONSERVICE      0X800002C6       Memory Reduce
                       ESMCOMMONSERVICE      0X80000515       POST memory resize
                       ESMCOMMONSERVICE      0X8000051A       POST cache Reduce
                       ESMCOMMONSERVICE      0XC000051C       Cache ECC multi
Memory failure         ESMCOMMONSERVICE      0XC000044C       ECC Multiple Error
                       ESMCOMMONSERVICE      0XC00008FC       ECC Uncorrectable Error
                       ESMCOMMONSERVICE      0XC0000903       ECC Uncorrectable Error
                       ESMCOMMONSERVICE      0X80000B1C       ECC Correctable Errors
                       ESMCOMMONSERVICE      0XC0000B18       Memory Parity Error
Memory                 ESMCOMMONSERVICE      0X80000BC2       Memory Utilization Warning
degeneration failure
                       ESMCOMMONSERVICE      0XC0000BC0       Memory Utilization Error
Machine                ESMDSVNT              0XC0000002       No response from the server
inaccessible error
Prediction: chassis    ESMCOMMONSERVICE      0XC0000066       Temp Lower Error
temperature failure
                       ESMCOMMONSERVICE      0XC0000070       Temp Lower Limit Error
                       ESMCOMMONSERVICE      0XC0000064       Temp Upper Error
                       ESMCOMMONSERVICE      0XC0000072       Temp Upper Limit Error
                       ESMCOMMONSERVICE      0XC000093E       Temperature Error
Prediction: power      ESMCOMMONSERVICE      0XC0000915       Power Unit Reduction
unit failure
Prediction: voltage    ESMCOMMONSERVICE      0XC00001FD       Voltage Lower Limit Error
failure
                       ESMCOMMONSERVICE      0XC00001FF       Voltage Lower Limit Error


                                                          SigmaSystemCenter 2.1 Reference Guide
282
                                                          Events SigmaSystemCenter Can Detect


Event Category         Events NEC ESMPRO Manager Can Detect

                       Source Name           Event ID         Description

                       ESMCOMMONSERVICE      0XC0000203       Voltage Upper Limit Error
                       ESMCOMMONSERVICE      0XC0000205       Voltage Upper Limit Error
                       ESMCOMMONSERVICE      0XC0000932       Voltage Error
Prediction:            ESMCOMMONSERVICE      0XC00000C8       Fan Unit Error
fan/cooling device
failure                ESMCOMMONSERVICE      0XC00000D0       Fan Lower Limit Error
                       ESMCOMMONSERVICE      0XC00000D2       Fan Lower Limit Error
                       ESMCOMMONSERVICE      0XC00000D6       Fan Upper Limit Error
                       ESMCOMMONSERVICE      0XC00000D8       Fan Upper Limit Error
                       ESMCOMMONSERVICE      0XC0000A8C       Liquid Leak Error
Recovery from the      ESM MYLEX SERVICE     0X40040204       System Drive ONLINE
hard disk recovery
failure                ESMDSIKARRAY          0X400403E8       Disk Array Logical Device Online
                       ASMBENOTIFY           0X00002013       Reconstruct completed
                       ASMBENOTIFY           0X0000B02D       Array is optimal
CPU load failure       ESMCPUPERF            0X40000067       CPU Warning Recovered
recovery
                       ESMCPUPERF            0X4000006B       CPU Warning Recovered
                       ESMCPUPERF            0X80000065       CPU Error Recovered
                       ESMCPUPERF            0X80000069       CPU Error Recovered
CPU temperature        ESMCOMMONSERVICE      0X40000949       CPU thermal trip Recovered
failure recovery
Memory                 ESMCOMMONSERVICE      0X80000BC1       Memory Utilization Error Recovered
degeneration failure
recovery               ESMCOMMONSERVICE      0X40000BC3       Memory Utilization Warning Recovered

Machine                ESMDSVNT              0X40000001       The server access recovered
inaccessible error
recovery
Clear Alert: chassis   ESMCOMMONSERVICE      0X8000006B       Temp Lower Error Recovered
temperature failure
recovery               ESMCOMMONSERVICE      0X8000006A       Temp Upper Error Recovered

Clear Alert: voltage   ESMCOMMONSERVICE      0X800001FE       Voltage Lower Limit Error Recovered
failure recovery
                       ESMCOMMONSERVICE      0X80000204       Voltage Upper Limit Error Recovered
                       ESMCOMMONSERVICE      0X40000BAD       Voltage Recovery
Clear Alert:           ESMCOMMONSERVICE      0X800000D1       Fan Lower Limit Error Recovered
fan/cooling device
failure recovery       ESMCOMMONSERVICE      0X800000D7       Fan Upper Limit Error Recovered
                       ESMCOMMONSERVICE      0X400002C3       Cooler Reduced
                       ESMCOMMONSERVICE      0X400000CD       Fan Unit Error Recovered
Cluster: Node down     CLUSTERPRO            0XC00008A4       Server down
                       CLUSTERPRO X          0X40000002       Server down
                       EXPRESSCLUSTER X      0X40000002       Server down
Cluster: Network       CLUSTERPRO            0XC0005217       Public LAN error
failure
                                             0XC000521B       Public LAN error

Part III Maintenance Information
                                                                                                    283
5 Error Events and Policy Actions


Event Category       Events NEC ESMPRO Manager Can Detect

                     Source Name           Event ID         Description

                                           0XC000521C       Public LAN error
                                           0XC000521D       Public LAN error




                                                      SigmaSystemCenter 2.1 Reference Guide
284
                                                             Events SigmaSystemCenter Can Detect




5.2.2.      Checking Events that Can Be Detected Through NEC
            ESMPRO Manager
            You can refer to events that can be detected through NEC ESMPRO Manager by using
            the "Save Monitor Event" function. Perform the following procedure to refer to the
            events.


            Note: The following procedure is for Windows.
            A document that shows events that can be detected through NEC ESMPRO Manager
            for Linux is provided individually. Inquire of our sales representative.


            1.   Start NEC ESMPRO Agent from Control Panel on the machine on which NEC
                 ESMPRO Agent installed.
            2.   Click Report Setting on the General tab to start the Alert Manager setting tool.




Part III Maintenance Information
                                                                                                    285
5 Error Events and Policy Actions



            3.   Select Save Monitor Event from the Options menu on the Alert Manager setting
                 tool.




            4.   The dialog box appears. Select the EventLog check box and Agent Events check
                 box, and then click Save.




                                                       SigmaSystemCenter 2.1 Reference Guide
286
                                                              Events SigmaSystemCenter Can Detect



            5.   The system starts writing the monitoring target to a file. The following dialog box is
                 displayed during writing.




            6.   When the writing process completes, the dialog box disappears.


            Writing the monitoring target completes.


            The first line is a header and from the second line, the written file is created in the CSV
            format. Refer to the event which "Manager" field is YES.


            Note: The events that SigmaSystemCenter can detect through NEC ESMPRO
            Manager are only default events monitored by NEC ESMPRO Agent. If you changed
            the monitoring target, you may not be able to check the event properly.




Part III Maintenance Information
                                                                                                    287
5 Error Events and Policy Actions




5.2.3.      Events         System          Monitor          -    Performance              Monitoring
            Services Can Detect
            System Monitor - Performance Monitoring Services can monitor the load status of a
            monitored machine, and send alert as an event to SystemProvisioning when the
            machine exceeds the threshold and when the machine recovers. In addition, if you use
            the VM Optimized Placement function, System Monitor - Performance Monitoring
            Services notifies the VM Server high load event when the load of a virtual machine
            server exceeds the high load bound, or the VM Server low load event when the load of
            a virtual machine server falls below the low load bound. The Event Categories of
            events that are notified from System Monitor - Performance Monitoring Services are as
            follows.
            You can check the following error events by specifying "SystemMonitorPerf" in the
            Report Source box on the Corresponding Event Handler Settings window.


            Event Category          Event ID     Event Name                            Description

            Customized              10000001     Customized machine notification1      Performance data of
            Machine Notification                                                       the target machine
                                    10000002     Customized machine notification2      exceeded the threshold
                                    10000003     Customized machine notification3      value / recovered from
                                                                                       the excess of the
                                    10000004     Customized machine notification4      threshold value. *1
                                    10000005     Customized machine notification5
                                    10000006     Customized machine notification6
                                    10000007     Customized machine notification7
                                    10000008     Customized machine notification8
                                    10000009     Customized machine notification9
                                    1000000A     Customized machine notification10
            Customized Group        11000001     Customized group notification1        Performance data of
            Notification                                                               the target group
                                    11000002     Customized group notification2        exceeded the threshold
                                    11000003     Customized group notification3        value / recovered from
                                                                                       the excess of the
                                    11000004     Customized group notification4        threshold value. *1
                                    11000005     Customized group notification5
            VM Server               11000006     VM Server high load                   The CPU usage rate of
            Notification                                                               the virtual machine
                                                                                       server exceeded the
                                                                                       high load bound. *2
                                    11000007     VM Server low load                    The CPU usage rate of
                                                                                       the virtual machine
                                                                                       server fell below the
                                                                                       low load bound. *2
            *1         You set content of the notification and the threshold values from System Monitor -
                       Performance Monitoring Services.
            *2         You set the boundary value from SystemProvisioning.


                                                                SigmaSystemCenter 2.1 Reference Guide
288
                                                           Events SigmaSystemCenter Can Detect



             Customized Machine Notification: This is used for notifying the performance error
              event of a single machine. For example, this is used for when SigmaSystemCenter
              executes recovery process that is triggered by exceeding threshold value of CPU
              usage of a specific machine. Configure the recovery actions for machines, such as
              Shutdown machine, Reboot machine, and Replace machine.
             Customized Group Notification: This is used for notifying the performance error
              event of a group. For example, this is used for when SigmaSystemCenter
              executes recovery process that is triggered by exceeding threshold value of CPU
              usage average of machines in a specific group. Configure the recovery actions for
              groups, such as Startup a machine (in the Group), Add a machine, and Delete a
              machine.
             VM Server Notification: This is used for notifying the performance error event when
              you use the VM Optimized Placement function. Configure the recovery actions,
              such as Load balance VM server and Power save VM server.


            You can configure the contents of events that custom notification events notify on the
            management console of System Monitor - Performance Monitoring Services.


            Reference: See System Monitor - Performance Monitoring Services User’s Guide for
            details regarding threshold monitoring and performance data.




Part III Maintenance Information
                                                                                                289
5 Error Events and Policy Actions




5.2.4.      Events the VMware (vCenter Server) Compatible Function
            Can Detect
            The error events on virtual machines or virtual machine servers that can be detected by
            working together with VMware (vCenter Server) are as follows.
            You can check the following error events by specifying "VMwareProvider" in the Report
            Source box on the Corresponding Event Handler Settings window.


            Classification            Event Category       Error                   Description *1

            Status of the             Machine              Alarm Host connection   The response from the
            connection to a virtual   inaccessible error   state on VMS changed    virtual machine server
            machine server            recovery             from gray to green      is revived.
                                      Machine              Alarm Host connection   Lost the response
                                      inaccessible error   state on VMS changed    from the virtual
                                                           from gray to red        machine server.
                                      Others               Alarm Host connection   Lost the response
                                                           state on VMS changed    from the virtual
                                                           from green to gray      machine server.
                                      Machine              Alarm Host connection   Lost the response
                                      inaccessible error   state on VMS changed    from the virtual
                                                           from green to red       machine server.
                                      Others               Alarm Host connection   Lost the response
                                                           state on VMS changed    from the virtual
                                                           from red to gray        machine server.
                                      Machine              Alarm Host connection   The response from the
                                      inaccessible error   state on VMS changed    virtual machine server
                                      recovery             from red to green       is revived.
            CPU usage rate on a       CPU load failure     Alarm Host CPU Usage    The CPU usage rate
            virtual machine server    recovery             on VMS changed from     of the virtual machine
                                                           gray to green           server becomes less
                                                                                   than n %.
                                                                                   (Default value: 75%)
                                      Others               Alarm Host CPU Usage    The CPU usage rate
                                                           on VMS changed from     of the virtual machine
                                                           gray to yellow          server becomes n %
                                                                                   or more.
                                                                                   (Default value: 75%)
                                      CPU load failure     Alarm Host CPU Usage    The CPU usage rate
                                                           on VMS changed from     of the virtual machine
                                                           gray to red             server becomes n %
                                                                                   or more.
                                                                                   (Default value: 90%)
                                      Others               Alarm Host CPU Usage    The CPU usage rate
                                                           on VMS changed from     of the virtual machine
                                                           green to gray           server becomes
                                                                                   unknown.




                                                             SigmaSystemCenter 2.1 Reference Guide
290
                                                              Events SigmaSystemCenter Can Detect


            Classification         Event Category         Error                  Description *1

                                   Others                 Alarm Host CPU Usage   The CPU usage rate
                                                          on VMS changed from    of the virtual machine
                                                          green to yellow        server becomes n %
                                                                                 or more.
                                                                                 (Default value: 75%)
                                   CPU load failure       Alarm Host CPU Usage   The CPU usage rate
                                                          on VMS changed from    of the virtual machine
                                                          green to red           server becomes n %
                                                                                 or more.
                                                                                 (Default value: 90%)
                                   Others                 Alarm Host CPU Usage   The CPU usage rate
                                                          on VMS changed from    of the virtual machine
                                                          yellow to gray         server becomes
                                                                                 unknown.
                                   CPU load failure       Alarm Host CPU Usage   The CPU usage rate
                                   recovery               on VMS changed from    of the virtual machine
                                                          yellow to green        server becomes less
                                                                                 than n %.
                                                                                 (Default value: 75%)
                                   CPU load failure       Alarm Host CPU Usage   The CPU usage rate
                                                          on VMS changed from    of the virtual machine
                                                          yellow to red          server becomes n %
                                                                                 or more.
                                                                                 (Default value: 90%)
                                   Others                 Alarm Host CPU Usage   The CPU usage rate
                                                          on VMS changed from    of the virtual machine
                                                          red to gray            server is unknown.
                                   CPU load failure       Alarm Host CPU Usage   The CPU usage rate
                                   recovery               on VMS changed from    of the virtual machine
                                                          red to green           server becomes less
                                                                                 than n %.
                                                                                 (Default value: 75%)
                                   Others                 Alarm Host CPU Usage   The CPU usage rate
                                                          on VMS changed from    of the virtual machine
                                                          red to yellow          server becomes less
                                                                                 than n %.
                                                                                 (Default value: 90%)
            Usage rate of memory   Memory                 Alarm Host Memory      The memory usage
            on a virtual machine   degeneration failure   Usage on VMS changed   rate of the virtual
            server                 recovery               from gray to green     machine server
                                                                                 becomes less than
                                                                                 n %.
                                                                                 (Default value: 75%)
                                   Others                 Alarm Host Memory      The memory usage
                                                          Usage on VMS changed   rate of the virtual
                                                          from gray to yellow    machine server
                                                                                 becomes n % or more.
                                                                                 (Default value: 75%)
                                   Memory                 Alarm Host Memory      The memory usage
                                   degeneration failure   Usage on VMS changed   rate of the virtual
                                                          from gray to red       machine server
                                                                                 becomes n % or more.
                                                                                 (Default value: 90%)

Part III Maintenance Information
                                                                                                   291
5 Error Events and Policy Actions


            Classification            Event Category         Error                    Description *1

                                      Others                 Alarm Host Memory        The memory usage
                                                             Usage on VMS changed     rate of the virtual
                                                             from green to gray       machine server
                                                                                      becomes unknown.
                                      Others                 Alarm Host Memory        The memory usage
                                                             Usage on VMS changed     rate of the virtual
                                                             from green to yellow     machine server
                                                                                      becomes n % or more.
                                                                                      (Default value: 75%)
                                      Memory                 Alarm Host Memory        The memory usage
                                      degeneration failure   Usage on VMS changed     rate of the virtual
                                                             from green to red        machine server
                                                                                      becomes n % or more.
                                                                                      (Default value: 90%)
                                      Others                 Alarm Host Memory        The memory usage
                                                             Usage on VMS changed     rate of the virtual
                                                             from yellow to gray      machine server
                                                                                      becomes unknown.
                                      Memory                 Alarm Host Memory        The memory usage
                                      degeneration failure   Usage on VMS changed     rate of the virtual
                                      recovery               from yellow to green     machine server
                                                                                      becomes less than
                                                                                      n %.
                                                                                      (Default value: 75%)
                                      Memory                 Alarm Host Memory        The memory usage
                                      degeneration failure   Usage on VMS changed     rate of the virtual
                                                             from yellow to red       machine server
                                                                                      becomes n % or more.
                                                                                      (Default value: 90%)
                                      Others                 Alarm Host Memory        The memory usage
                                                             Usage on VMS changed     rate of the virtual
                                                             from red to gray         machine server
                                                                                      becomes unknown.
                                      Memory                 Alarm Host Memory        The memory usage
                                      degeneration failure   Usage on VMS changed     rate of the virtual
                                      recovery               from red to green        machine server
                                                                                      becomes less than
                                                                                      n %.
                                                                                      (Default value: 75%)
                                      Others                 Alarm Host Memory        The memory usage
                                                             Usage on VMS changed     rate of the virtual
                                                             from red to yellow       machine server is less
                                                                                      than n %.
                                                                                      (Default value: 90%)
            Allocation rate of disk   Others                 Alarm DataStore          The allocation rate of
            on a Datastore                                   Overallocation on disk   the Datastore is less
                                                             on DATASTORE             than n %.
                                                             changed from gray to     (Default value: 400)
                                                             green
                                      Others                 Alarm Datastore          The allocation rate of
                                                             Overallocation on disk   the Datastore is less
                                                             on DATASTORE             than n %.
                                                             changed from gray to     (Default value: 700)
                                                             yellow

                                                               SigmaSystemCenter 2.1 Reference Guide
292
                                                          Events SigmaSystemCenter Can Detect


            Classification          Event Category   Error                    Description *1

                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore
                                                     on DATASTORE             becomes n % or more.
                                                     changed from gray to     (Default value: 700)
                                                     red
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore
                                                     on DATASTORE             becomes unknown.
                                                     changed from green to
                                                     gray
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore is less
                                                     on DATASTORE             than n %.
                                                     changed from green to    (Default value: 700)
                                                     yellow
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore
                                                     on DATASTORE             becomes n % or more.
                                                     changed from green to    (Default value: 700)
                                                     red
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore
                                                     on DATASTORE             becomes unknown.
                                                     changed from yellow to
                                                     gray
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore is less
                                                     on DATASTORE             than n %.
                                                     changed from yellow to   (Default value: 400)
                                                     green
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore
                                                     on DATASTORE             becomes n % or more.
                                                     changed from yellow to   (Default value: 700)
                                                     red
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore
                                                     on DATASTORE             becomes unknown.
                                                     changed from red to
                                                     gray.
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore is less
                                                     on DATASTORE             than n %.
                                                     changed from red to      (Default value: 400)
                                                     green
                                    Others           Alarm Datastore          The allocation rate of
                                                     Overallocation on disk   the Datastore is less
                                                     on DATASTORE             than n %.
                                                     changed from red to      (Default value: 700)
                                                     yellow
            Usage rate of disk on   Others           Alarm Datastore usage    The disk usage rate of
            a Datastore                              on disk on               the Datastore is less
                                                     DATASTORE changed        than n %.
                                                     from gray to green       (Default value: 75)



Part III Maintenance Information
                                                                                                 293
5 Error Events and Policy Actions


            Classification          Event Category      Error                    Description *1

                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore is less
                                                        DATASTORE changed        than n %.
                                                        from gray to yellow      (Default value: 85)
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore
                                                        DATASTORE changed        becomes n % or more.
                                                        from gray to red         (Default value: 85)
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore
                                                        DATASTORE changed        becomes unknown.
                                                        from green to gray
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore is less
                                                        DATASTORE changed        than n %.
                                                        from green to yellow     (Default value: 85)
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore
                                                        DATASTORE changed        becomes n % or more.
                                                        from green to red        (Default value: 85)
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore
                                                        DATASTORE changed        becomes unknown.
                                                        from yellow to gray
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore is less
                                                        DATASTORE changed        than n %.
                                                        from yellow to green     (Default value: 75)
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore
                                                        DATASTORE changed        becomes n % or more.
                                                        from yellow to red       (Default value: 85)
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore
                                                        DATASTORE changed        becomes unknown.
                                                        from red to gray
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore is less
                                                        DATASTORE changed        than n %.
                                                        from red to green        (Default value: 75)
                                    Others              Alarm Datastore usage    The disk usage rate of
                                                        on disk on               the Datastore is less
                                                        DATASTORE changed        than n %.
                                                        from red to yellow       (Default value: 85)
            Status of the           Hard disk failure   Storage path             Cannot access to the
            connection to a                             connectivity on VMS is   Datastore.
            Datastore                                   lost
                                    Others              Storage path             Storage redundancy
                                                        redundancy on VMS is     is lost.
                                                        lost




                                                          SigmaSystemCenter 2.1 Reference Guide
294
                                                              Events SigmaSystemCenter Can Detect


            Classification           Event Category       Error                     Description *1

                                     Others               Storage path              Storage redundancy
                                                          redundancy on VMS is      is degraded.
                                                          degraded
            Status of the            Others               Network connectivity on   Cannot connect to the
            connection to a                               VMS is lost               network.
            network
                                     Others               Network redundancy on     Network
                                                          VMS is lost               redundancy is lost.
                                     Others               Network redundancy on     Network
                                                          VMS is degraded           redundancy is
                                                                                    degraded.
            State of heart beat of   Machine              Alarm Virtual Machine     The heart beat value
            a virtual machine        inaccessible error   Heartbeat on VM           of the virtual machine
                                     recovery             changed from gray to      becomes more than
                                                          green                     the threshold value.
                                                                                    (Default value: 5)
                                     Machine              Alarm Virtual Machine     The heart beat value
                                     inaccessible error   Heartbeat on VM           of the virtual machine
                                                          changed from gray to      becomes less than the
                                                          red                       threshold value.
                                                                                    (Default value:5)
                                     Others               Alarm Virtual Machine     The heart beat value
                                                          Heartbeat on VM           becomes unknown.
                                                          changed from green to
                                                          gray
                                     Machine              Alarm Virtual Machine     The heart beat value
                                     inaccessible error   Heartbeat on VM           of the virtual machine
                                                          changed from green to     becomes less than the
                                                          red                       threshold value.
                                                                                    (Default value: 5)
                                     Others               Alarm Virtual Machine     The heart beat value
                                                          Heartbeat on VM           becomes unknown.
                                                          changed from red to
                                                          gray
                                     Machine              Alarm Virtual Machine     The heart beat value
                                     inaccessible error   Heartbeat on VM           of the virtual machine
                                     recovery             changed from red to       becomes more than
                                                          green                     the threshold value.
                                                                                    (Default value: 5)
            Usage rate of CPU on     CPU load failure     Alarm Virtual Machine     The CPU usage rate
            a virtual machine        recovery             CPU Usage on VM           of the virtual machine
                                                          changed from gray to      becomes less than
                                                          green                     n %.
                                                                                    (Default value: 75%)
                                     Others               Alarm Virtual Machine     The CPU usage rate
                                                          CPU Usage on VM           of the virtual machine
                                                          changed from gray to      becomes n % or more.
                                                          yellow                    (Default value: 75%)
                                     CPU load failure     Alarm Virtual Machine     The CPU usage rate
                                                          CPU Usage on VM           of the virtual machine
                                                          changed from gray to      becomes n % or more.
                                                          red                       (Default value: 90%)


Part III Maintenance Information
                                                                                                      295
5 Error Events and Policy Actions


            Classification          Event Category         Error                    Description *1

                                    Others                 Alarm Virtual Machine    The CPU usage rate
                                                           CPU Usage on VM          of the virtual machine
                                                           changed from green to    becomes unknown.
                                                           gray
                                    Others                 Alarm Virtual Machine    The CPU usage rate
                                                           CPU Usage on VM          of the virtual machine
                                                           changed from green to    becomes n % or more.
                                                           yellow                   (Default value: 75%)
                                    CPU load failure       Alarm Virtual Machine    The CPU usage rate
                                                           CPU Usage on VM          of the virtual machine
                                                           changed from green to    becomes n % or more.
                                                           red                      (Default value: 90%)
                                    Others                 Alarm Virtual Machine    The CPU usage rate
                                                           CPU Usage on VM          of the virtual machine
                                                           changed from yellow to   becomes unknown.
                                                           gray
                                    CPU load failure       Alarm Virtual Machine    The CPU usage rate
                                    recovery               CPU Usage on VM          of the virtual machine
                                                           changed from yellow to   becomes less than
                                                           green                    n %.
                                                                                    (Default value: 75%)
                                    CPU load failure       Alarm Virtual Machine    The CPU usage rate
                                                           CPU Usage on VM          of the virtual machine
                                                           changed from yellow to   becomes n % or more.
                                                           red                      (Default value: 90%)
                                    Others                 Alarm Virtual Machine    The CPU usage rate
                                                           CPU Usage on VM          of the virtual machine
                                                           changed from red to      becomes unknown.
                                                           gray
                                    CPU load failure       Alarm Virtual Machine    The CPU usage rate
                                    recovery               CPU Usage on VM          of the virtual machine
                                                           changed from red to      becomes less than
                                                           green                    n %.
                                                                                    (Default value: 75%)
                                    Others                 Alarm Virtual Machine    The CPU usage rate
                                                           CPU Usage on VM          of the virtual machine
                                                           changed from red to      becomes less than
                                                           yellow                   n %.
                                                                                    (Default value: 90%)
            Usage rate of memory    Memory                 Alarm Virtual Machine    The CPU usage rate
            on a virtual machine    degeneration failure   Memory Usage on VM       of the virtual machine
                                    recovery               changed from gray to     becomes less than
                                                           green                    n %.
                                                                                    (Default value: 75%)
                                    Others                 Alarm Virtual Machine    The memory usage
                                                           Memory Usage on VM       rate of the virtual
                                                           changed from gray to     machine becomes n %
                                                           yellow                   or more.
                                                                                    (Default value: 75%)




                                                             SigmaSystemCenter 2.1 Reference Guide
296
                                                              Events SigmaSystemCenter Can Detect


            Classification         Event Category         Error                    Description *1

                                   Memory                 Alarm Virtual Machine    The memory usage
                                   degeneration failure   Memory Usage on VM       rate of the virtual
                                                          changed from gray to     machine becomes n %
                                                          red                      or more.
                                                                                   (Default value: 90%)
                                   Others                 Alarm Virtual Machine    The memory usage
                                                          Memory Usage on VM       rate of the virtual
                                                          changed from green to    machine becomes
                                                          gray                     unknown.
                                   Others                 Alarm Virtual Machine    The memory usage
                                                          Memory Usage on VM       rate of the virtual
                                                          changed from green to    machine becomes n %
                                                          yellow                   or more.
                                                                                   (Default value: 75%)
                                   Memory                 Alarm Virtual Machine    The memory usage
                                   degeneration failure   Memory Usage on VM       rate of the virtual
                                                          changed from green to    machine becomes n %
                                                          red                      or more.
                                                                                   (Default value: 90%)
                                   Others                 Alarm Virtual Machine    The memory usage
                                                          Memory Usage on VM       rate of the virtual
                                                          changed from yellow to   machine becomes
                                                          gray                     unknown.
                                   Memory                 Alarm Virtual Machine    The CPU usage rate
                                   degeneration failure   Memory Usage on VM       of the virtual machine
                                   recovery               changed from yellow to   becomes less than
                                                          green                    n %.
                                                                                   (Default value: 75%)
                                   Memory                 Alarm Virtual Machine    The memory usage
                                   degeneration failure   Memory Usage on VM       rate of the virtual
                                                          changed from yellow to   machine becomes n %
                                                          red                      or more.
                                                                                   (Default value: 90%)
                                   Others                 Alarm Virtual Machine    The memory usage
                                                          Memory Usage on VM       rate of the virtual
                                                          changed from red to      machine becomes
                                                          gray                     unknown.
                                   Memory                 Alarm Virtual Machine    The CPU usage rate
                                   degeneration failure   Memory Usage on VM       of the virtual machine
                                   recovery               changed from red to      becomes less than
                                                          green                    n %.
                                                                                   (Default value: 75%)
                                   Others                 Alarm Virtual Machine    The CPU usage rate
                                                          Memory Usage on VM       of the virtual machine
                                                          changed from red to      becomes less than
                                                          yellow                   n %.
                                                                                   (Default value: 90%)
            *1         You can change the CPU usage rate, the memory usage rate, the Datastore usage
                       rate and the allocation rate of disk on a Datastore in vCenter Server.




Part III Maintenance Information
                                                                                                     297
5 Error Events and Policy Actions



            Note:
            ▪ The event of The heart beat value of the virtual machine is less than the threshold
            value. can be detected when you start a virtual machine. In that case, enable the error
            event controlling function.
            For how to configure the function, see Section 2.7, "Policy Property Settings" in
            SigmaSystemCenter Web Console Reference Guide.
            ▪ You can disable an event of virtual machine's Heart Beat status from generating by
            editing the Virtual Machine Heartbeat alarm definition in vCenter Server.
            In addition, if you cannot execute the above operation, set the following registry to
            delete an alarm from vCenter Server.
            Key: HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Provider\VM\VMware\Event
            Value (Type): DisableHeartbeatEvent (REG_DWORD)
            Value: 1
            ▪ The alarm definitions of virtual machines in Heartbeat status and events of the
            allocation rate of disk on a Datastore are disabled by default.




                                                            SigmaSystemCenter 2.1 Reference Guide
298
                                                               Events SigmaSystemCenter Can Detect




5.2.5.      Events the VMware (ESXi) Compatible Function Can
            Detect
            The error events on virtual machines or virtual machine servers that can be detected by
            working together with VMware (ESXi) are as follows.
            You can check the following error events by specifying "StandaloneEsxProvider" in the
            Report Source box on the Corresponding Event Handler Settings window.


            Classification            Event Category       Error                   Description

            Status of the Hard        Hard disk failure    Alarm Datastore on      Cannot use Datastore
            disk                                           VMS can not be          from a virtual machine
                                                           available               server.
            Status of the             Machine              Alarm Host connection   Lost the response
            connection to a virtual   inaccessible error   state on VMS changed    from the virtual
            machine server                                 from green to red       machine server.
                                      Machine              Alarm Host connection   The response from the
                                      inaccessible error   state on VMS changed    virtual machine server
                                      recovery             from red to green       is revived.



            Note:
            ▪ If you execute the restart operation of the PVMService and a virtual machine server,
            the "Hard disk failure" event that has already notified might be notified again.
            ▪ There is a case that if network failure occurred while SigmaSystemCenter checking
            the Datastore, the "Hard disk failure" is notified.




Part III Maintenance Information
                                                                                                       299
5 Error Events and Policy Actions




5.2.6.      Events the Optimized Placement Function Can Detect
            The error events that the Optimized Placement function can detect are as follows.
            You can check the following error events by specifying "VM Optimized Placement
            notification" in the Event Category box on the Corresponding Event Handler Settings
            window.


            Event Category           Event               Event Name                 Description

            VM Optimized             Scaleout            Scaleout                   As a result of load
            Placement notification   Recommendation      Recommendation             balancing, a virtual
                                                                                    machine that can be
                                                                                    moved is detected, but
                                                                                    there is not virtual
                                                                                    machine server in a
                                                                                    group that can be a
                                                                                    destination.



            Note: The "Scaleout Recommendation" event notifies resource deficiency of a group.
            Configure the recovery process for the group. You cannot use recovery process for
            each machine. In addition, this event is an internal event that SystemProvisioning has
            so you do not need to configure the event.



5.2.7.      Events the Out-of-Band Management Can Detect
            The error events that the Out-of-Band Management can detect are as follows.
            You can check the following error events by specifying the category in the Event
            Category and “OobManagement” in the Report Source.


            Classification   Event Category        Event ID       Message                      Description

            Temperature      Prediction:chassis    [PET]          Temperature: Lower           Fell below the
                             temperature failure   0x00010102     Critical - going low         lower critical limit
                                                                                               of the
                                                                                               temperature.
                                                   [PET]          Temperature: Lower           Fell below the
                                                   0x00010104     Non-recoverable - going      lower
                                                                  low                          non-recoverable
                                                                                               limit of the
                                                                                               temperature.
                                                   [PET]          Temperature: Upper           Exceeded the
                                                   0x00010109     Critical - going high        upper critical
                                                                                               limit of the
                                                                                               temperature.
                                                   [PET]          Temperature: Upper           Exceeded the
                                                   0x0001010B     Non-recoverable - going      upper
                                                                  high                         non-recoverable
                                                                                               limit of the
                                                                                               temperature.

                                                              SigmaSystemCenter 2.1 Reference Guide
300
                                                               Events SigmaSystemCenter Can Detect


            Classification   Event Category         Event ID     Message                      Description

                             Clear Alert: chassis   [PET]        Temperature: Lower           Recovered from
                             temperature failure    0x80010102   Critical - going high        the lower critical
                             recovery                                                         limit of the
                                                                                              temperature.
                                                    [PET]        Temperature: Upper           Recovered from
                                                    0x80010109   Critical - going low         the upper critical
                                                                                              limit of the
                                                                                              temperature.
                             Others                 [PET]        Temperature: Lower           Fell below the
                                                    0x00010100   Non-critical - going low     lower warning
                                                                                              limit of the
                                                                                              temperature.
                                                    [PET]        Temperature: Lower           Recovered from
                                                    0x80010100   Non-critical - going high    the lower
                                                                                              warning limit of
                                                                                              the temperature.
                                                    [PET]        Temperature: Lower           Recovered from
                                                    0x80010104   Non-recoverable - going      the lower
                                                                 high                         non-recoverable
                                                                                              limit of the
                                                                                              temperature.
                                                    [PET]        Temperature: Upper           Exceeded the
                                                    0x00010107   Non-critical - going high    upper warning
                                                                                              limit of the
                                                                                              temperature.
                                                    [PET]        Temperature: Upper           Recovered from
                                                    0x80010107   Non-critical - going low     the upper
                                                                                              warning limit of
                                                                                              the temperature.
                                                    [PET]        Temperature: Upper           Recovered from
                                                    0x8001010B   Non-recoverable - going      the upper
                                                                 low                          non-recoverable
                                                                                              limit of the
                                                                                              temperature.
                                                    [PET]        Temperature: Monitoring      An event of the
                                                    0x00010301   event occurred               temperature
                                                                                              occurred.
                                                    [PET]        Temperature: Monitoring      Recovered from
                                                    0x80010301   event cleared                an even of the
                                                                                              temperature.
                                                    [PET]        Temperature: Limit           The temperature
                                                    0x00010501   Exceeded                     exceeded the
                                                                                              limit.
                                                    [PET]        Temperature: Limit Not       The temperature
                                                    0x80010501   Exceeded                     did not exceed
                                                                                              the limit.
                                                    [PET]        Temperature: Transition to   The temperature
                                                    0x00010700   OK                           became normal.
                                                    [PET]        Temperature: Transition to   The temperature
                                                    0x80010700   Abnormal                     became
                                                                                              abnormal.
                                                    [PET]        Temperature: Transition to   The temperature
                                                    0x00010701   Non-Critical                 became the
                                                                                              warning level.
Part III Maintenance Information
                                                                                                     301
5 Error Events and Policy Actions


            Classification   Event Category         Event ID       Message                       Description

                                                    [PET]          Temperature: Transition to    The temperature
                                                    0x00010702     Critical                      became the
                                                                                                 critical level.
                                                    [PET]          Temperature: Transition to    The temperature
                                                    0x00010703     Non-recoverable               became the
                                                                                                 non-recoverable
                                                                                                 level.
            Voltage          Prediction: voltage    [PET]          Voltage: Lower Critical -     Fell under the
                             failure                0x00020102     going low                     lower critical limit
                                                                                                 of the voltage.
                                                    [PET]          Voltage: Lower                Fell under the
                                                    0x00020104     Non-recoverable - going       lower
                                                                   low                           non-recoverable
                                                                                                 limit of the
                                                                                                 voltage.
                                                    [PET]          Voltage: Upper Critical -     Exceeded the
                                                    0x00020109     going high                    upper critical
                                                                                                 limit of the
                                                                                                 voltage.
                                                    [PET]          Voltage: Upper                Exceeded the
                                                    0x0002010B     Non-recoverable - going       upper
                                                                   high                          non-recoverable
                                                                                                 limit of the
                                                                                                 voltage.
                                                    [PET]          Voltage: Transition to        The voltage
                                                    0x00020703     Non-recoverable               became the
                                                                                                 non-recoverable
                                                                                                 level.
                             Clear Alert: voltage   [PET]          Voltage: Lower Critical -     Recovered from
                             failure recovery       0x80020102     going high                    the lower critical
                                                                                                 limit of the
                                                                                                 voltage.
                                                    [PET]          Voltage: Upper Critical -     Recovered from
                                                    0x80020109     going low                     the upper critical
                                                                                                 limit of the
                                                                                                 voltage.
                                                    [PET]          Voltage: Transition to OK     The voltage
                                                    0x00020700                                   became normal.
                             Others                 [PET]          Voltage: Lower Non-critical   Fell below the
                                                    0x00020100     - going low                   lower warning
                                                                                                 limit of the
                                                                                                 voltage.
                                                    [PET]          Voltage: Lower Non-critical   Recovered from
                                                    0x80020100     - going high                  the lower
                                                                                                 warning limit of
                                                                                                 the voltage.
                                                    [PET]          Voltage: Lower                Recovered from
                                                    0x80020104     Non-recoverable - going       the lower
                                                                   high                          non-recoverable
                                                                                                 limit of the
                                                                                                 voltage.




                                                               SigmaSystemCenter 2.1 Reference Guide
302
                                                         Events SigmaSystemCenter Can Detect


            Classification   Event Category   Event ID     Message                       Description

                                              [PET]        Voltage: Upper Non-critical   Exceeded the
                                              0x00020107   - going high                  upper warning
                                                                                         limit of the
                                                                                         voltage.
                                              [PET]        Voltage: Upper Non-critical   Recovered from
                                              0x80020107   - going low                   the upper
                                                                                         warning limit of
                                                                                         the voltage.
                                              [PET]        Voltage: Upper                Recovered from
                                              0x8002010B   Non-recoverable - going       the upper
                                                           low                           non-recoverable
                                                                                         limit of the
                                                                                         voltage.
                                              [PET]        Voltage: Monitoring event     An event of the
                                              0x00020301   occurred                      voltage
                                                                                         occurred.
                                              [PET]        Voltage: Monitoring event     Recovered from
                                              0x80020301   cleared                       an event of the
                                                                                         voltage.
                                              [PET]        Voltage: Limit Exceeded       The voltage
                                              0x00020501                                 exceeded the
                                                                                         limit.
                                              [PET]        Voltage: Limit Not            The voltage did
                                              0x80020501   Exceeded                      not exceed the
                                                                                         limit.
                                              [PET]        Voltage: Performance Lags     Detected the
                                              0x00020601                                 voltage warning.
                                              [PET]        Voltage: Performance Met      Recovered from
                                              0x80020601                                 the voltage
                                                                                         warning.
                                              [PET]        Voltage: Transition to        The voltage
                                              0x80020700   Abnormal                      became
                                                                                         abnormal.
                                              [PET]        Voltage: Transition to        The voltage
                                              0x00020701   Non-Critical                  became the
                                                                                         warning level.
                                              [PET]        Voltage: Transition to        The voltage
                                              0x00020702   Critical                      became the
                                                                                         critical level.
            Current          Others           [PET]        Current: Monitoring event     An event of
                                              0x00030301   occurred                      voltage / electric
                                                                                         currents
                                                                                         occurred.
                                              [PET]        Current: Monitoring event     Recovered from
                                              0x80030301   cleared                       an event of
                                                                                         voltage / electric
                                                                                         currents.
                                              [PET]        Current: Limit Exceeded       Voltage / electric
                                              0x00030501                                 currents
                                                                                         exceeded the
                                                                                         limit.




Part III Maintenance Information
                                                                                                 303
5 Error Events and Policy Actions


            Classification   Event Category           Event ID       Message                      Description

                                                      [PET]          Current: Limit Not           Voltage / electric
                                                      0x80030501     Exceeded                     currents did not
                                                                                                  exceed the limit.
            FAN              Prediction:fan/cooling   [PET]          Fan(Speed): Lower Critical   The number of
                             device failure           0x00040102     - going low                  revolution of
                                                                                                  FAN fell below
                                                                                                  the lower critical
                                                                                                  limit.
                                                      [PET]          Fan(Speed): Lower            The number of
                                                      0x00040104     Non-recoverable - going      revolution of
                                                                     low                          FAN fell below
                                                                                                  the lower
                                                                                                  non-recoverable
                                                                                                  limit.
                                                      [PET]          Fan(Speed): Upper Critical   The number of
                                                      0x00040109     - going high                 revolution of
                                                                                                  FAN exceeded
                                                                                                  the upper critical
                                                                                                  limit.
                                                      [PET]          Fan(Speed): Upper            The number of
                                                      0x0004010B     Non-recoverable - going      revolution of
                                                                     high                         FAN exceeded
                                                                                                  the upper
                                                                                                  non-recoverable
                                                                                                  limit.
                                                      [PET]          Fan(Speed): Monitoring       An event of FAN
                                                      0x00040301     event occurred               occurred.
                             Clear Alert:             [PET]          Fan(Speed): Lower Critical   The number of
                             fan/cooling device       0x80040102     - going high                 revolution of
                             failure recovery                                                     FAN recovered
                                                                                                  from the lower
                                                                                                  critical limit.
                                                      [PET]          Fan(Speed): Upper Critical   The number of
                                                      0x80040109     - going low                  revolution of
                                                                                                  FAN recovered
                                                                                                  from the upper
                                                                                                  critical limit.
                                                      [PET]          Fan(Speed): Monitoring       Recovered from
                                                      0x80040301     event cleared                an event of FAN.
                             Others                   [PET]          Fan(Speed): Lower            The number of
                                                      0x00040100     Non-critical - going low     revolution of
                                                                                                  FAN fell below
                                                                                                  the lower
                                                                                                  warning limit.
                                                      [PET]          Fan(Speed): Lower            The number of
                                                      0x80040100     Non-critical - going high    revolution of
                                                                                                  FAN recovered
                                                                                                  from the lower
                                                                                                  warning limit.
                                                      [PET]          Fan(Speed): Lower            The number of
                                                      0x80040104     Non-recoverable - going      revolution of
                                                                     high                         FAN recovered
                                                                                                  from the lower
                                                                                                  non-recoverable
                                                                                                  limit.

                                                                 SigmaSystemCenter 2.1 Reference Guide
304
                                                         Events SigmaSystemCenter Can Detect


            Classification   Event Category   Event ID     Message                     Description

                                              [PET]        Fan(Speed): Upper           The number of
                                              0x00040107   Non-critical - going high   revolution of
                                                                                       FAN exceeded
                                                                                       the upper
                                                                                       warning limit.
                                              [PET]        Fan(Speed): Upper           The number of
                                              0x80040107   Non-critical - going low    revolution of
                                                                                       FAN recovered
                                                                                       from the upper
                                                                                       warning limit.
                                              [PET]        Fan(Speed): Upper           The number of
                                              0x8004010B   Non-recoverable - going     revolution of
                                                           low                         FAN recovered
                                                                                       from the upper
                                                                                       non-recoverable
                                                                                       limit.
                                              [PET]        Fan(Speed): Predictive      The FAN status
                                              0x00040401   Failure occurred            exceeded the
                                                                                       limit.
                                              [PET]        Fan(Speed): Predictive      The FAN status
                                              0x80040401   Failure cleared             became did not
                                                                                       exceed the limit.
                                              [PET]        Fan(Speed): Performance     Detected the
                                              0x00040601   Lags                        FAN warning.
                                              [PET]        Fan(Speed): Performance     Recovered the
                                              0x80040601   Met                         FAN warning.
                                              [PET]        Fan(Speed): Transition to   The FAN
                                              0x00040700   OK                          became normal.
                                              [PET]        Fan(Speed): Transition to   FAN became
                                              0x80040700   Abnormal                    abnormal.
                                              [PET]        Fan(Speed): Transition to   The FAN
                                              0x00040701   Non-Critical                became the
                                                                                       warning level.
                                              [PET]        Fan(Speed): Transition to   The FAN
                                              0x00040702   Critical                    became the
                                                                                       critical level.
                                              [PET]        Fan(Speed): Transition to   The FAN
                                              0x00040703   Non-recoverable             became
                                                                                       non-recoverable
                                                                                       level.
                                              [PET]        Fan(Speed): Redundancy      The FAN is
                                              0x00040B00   Full                        redundant
                                                                                       configuration.
                                              [PET]        Fan(Speed): Redundancy      The FAN
                                              0x00040B01   Lost                        became not
                                                                                       redundant
                                                                                       configuration.
                                              [PET]        Fan(Speed): Redundancy      The FAN is not
                                              0x00040B02   Degraded                    redundant
                                                                                       configuration but
                                                                                       available.




Part III Maintenance Information
                                                                                               305
5 Error Events and Policy Actions


            Classification   Event Category   Event ID       Message                        Description

                                              [PET]          Fan(Speed):                    The FAN is
                                              0x00040B03     Non-Redundant(Sufficient       non-redundant
                                                             Resources)                     configuration.
                                              [PET]          Fan(Speed):                    The FAN is
                                              0x00040B05     Non-Redundant(Insufficient     non-redundant
                                                             Resources)                     configuration
                                                                                            and unavailable.
            Security         Others           [PET]          Physical Security(Chassis      The cover
                                              0x00050301     Intrusion): Monitoring event   opened.
                                                             occurred
                                              [PET]          Physical Security(Chassis      The cover
                                              0x80050301     Intrusion): Monitoring event   closed.
                                                             cleared
                                              [PET]          Physical Security(Chassis      The cover
                                              0x00056F00     Intrusion): General Chassis    opened.
                                                             Intrusion occurred
                                              [PET]          Physical Security(Chassis      The cover
                                              0x80056F00     Intrusion): General Chassis    closed.
                                                             Intrusion cleared
                                              [PET]          Physical Security(Chassis      The Drive Bay
                                              0x00056F01     Intrusion): Drive Bay          cover opened.
                                                             Intrusion occurred
                                              [PET]          Physical Security(Chassis      The Drive Bay
                                              0x80056F01     Intrusion): Drive Bay          cover closed.
                                                             Intrusion cleared
                                              [PET]          Physical Security(Chassis      The cover of IO
                                              0x00056F02     Intrusion): I/O Card area      card area
                                                             Intrusion occurred             opened.
                                              [PET]          Physical Security(Chassis      The cover of IO
                                              0x80056F02     Intrusion): I/O Card area      card area
                                                             Intrusion cleared              closed.
                                              [PET]          Physical Security(Chassis      The cover of
                                              0x00056F03     Intrusion): Processor area     CPU area
                                                             Intrusion occurred             opened.
                                              [PET]          Physical Security(Chassis      The cover of
                                              0x80056F03     Intrusion): Processor area     CPU area
                                                             Intrusion cleared              closed.
                                              [PET]          Physical Security(Chassis      The LAN cable
                                              0x00056F04     Intrusion): LAN Leash Lost     is disconnected.
                                                             (System is unplugged from
                                                             LAN) occurred
                                              [PET]          Physical Security(Chassis      The LAN cable
                                              0x80056F04     Intrusion): LAN Leash Lost     is connected.
                                                             (System is unplugged from
                                                             LAN) cleared
                                              [PET]          Physical Security(Chassis      Unauthorized
                                              0x00056F05     Intrusion): Unauthorized       dock occurred.
                                                             dock occurred
                                              [PET]          Physical Security(Chassis      Unauthorized
                                              0x80056F05     Intrusion): Unauthorized       dock cleared.
                                                             dock cleared



                                                         SigmaSystemCenter 2.1 Reference Guide
306
                                                           Events SigmaSystemCenter Can Detect


            Classification   Event Category     Event ID     Message                          Description

                                                [PET]        Physical Security(Chassis        The FAN cover
                                                0x00056F06   Intrusion): FAN area             opened.
                                                             intrusion occurred
                                                [PET]        Physical Security(Chassis        The FAN cover
                                                0x80056F06   Intrusion): FAN area             closed.
                                                             intrusion cleared
            Security         Others             [PET]        Platform Security Violation      Front Panel
            Violation                           0x00066F00   Attempt: Secure Mode             Lockout
                                                             (Front Panel Lockout)
                                                             Violation attempt
                                                [PET]        Platform Security Violation      Entered an
                                                0x00066F01   Attempt: Pre-boot                incorrect user
                                                             Password Violation - user        password.
                                                             password
                                                [PET]        Platform Security Violation      Entered an
                                                0x00066F02   Attempt: Pre-boot                incorrect setup
                                                             Password Violation - setup       password.
                                                             password
                                                [PET]        Platform Security Violation      Entered an
                                                0x00066F03   Attempt: Pre-boot                incorrect
                                                             Password Violation -             network boot
                                                             network boot password            password.
                                                [PET]        Platform Security Violation      Entered an
                                                0x00066F04   Attempt: Other pre-boot          incorrect
                                                             Password Violation               password.
                                                [PET]        Platform Security Violation      OOB access
                                                0x00066F05   Attempt: Out-of-band             password
                                                             Access Password Violation        violation.
            CPU              CPU failure        [PET]        Processor: Transition to         CPU became
                                                0x80070700   Abnormal                         abnormal.
                                                [PET]        Processor: Transition to         CPU became
                                                0x00070701   Non-Critical                     the warning
                                                                                              status.
                                                [PET]        Processor: IERR occurred         A CPU internal
                                                0x00076F00                                    error occurred.
                                                [PET]        Processor: FRB1/BIST             A CPU error
                                                0x00076F02   failure occurred                 occurred.
                                                [PET]        Processor:                       An initialization
                                                0x00076F04   FRB3/Processor                   error occurred.
                                                             Startup/Initialization failure
                                                             (CPU didn't start) occurred
                                                [PET]        Processor: Processor             CPU was
                                                0x00076F08   disabled                         disabled.
                             CPU temperature    [PET]        Processor: Thermal Trip          CPU thermal trip
                             failure            0x00076F01   occurred                         occurred.
                             CPU temperature    [PET]        Processor: Thermal Trip          CPU thermal trip
                             failure recovery   0x80076F01   cleared                          ended.
                             Others             [PET]        Processor: Transition to         CPU became
                                                0x00070700   OK                               normal.
                                                [PET]        Processor: Transition to         CPU became
                                                0x00070702   Critical                         critical.

Part III Maintenance Information
                                                                                                     307
5 Error Events and Policy Actions


            Classification   Event Category   Event ID       Message                          Description

                                              [PET]          Processor: Transition to         CPU became
                                              0x00070703     Non-recoverable                  non-recoverable.
                                              [PET]          Processor: IERR cleared          Recovered from
                                              0x80076F00                                      the CPU internal
                                                                                              error.
                                              [PET]          Processor: FRB1/BIST             Recovered from
                                              0x80076F02     failure cleared                  the CPU error.
                                              [PET]          Processor: FRB2/Hang in          Hang in POST
                                              0x00076F03     POST failure occurred            failure occurred.
                                              [PET]          Processor: FRB2/Hang in          Recovered from
                                              0x80076F03     POST failure cleared             the Hang in
                                                                                              POST failure.
                                              [PET]          Processor:                       Recovered from
                                              0x80076F04     FRB3/Processor                   the initialization
                                                             Startup/Initialization failure   error.
                                                             (CPU didn't start) cleared
                                              [PET]          Processor: Configuration         A CPU
                                              0x00076F05     Error occurred                   configuration
                                                                                              error occurred.
                                              [PET]          Processor: Configuration         Recovered from
                                              0x80076F05     Error cleared                    the CPU
                                                                                              configuration
                                                                                              error.
                                              [PET]          Processor: SM BIOS               A System error
                                              0x00076F06     'Uncorrectable                   occurred on the
                                                             CPU-complex Error'               system bus.
                                                             occurred
                                              [PET]          Processor: SM BIOS               Recovered from
                                              0x80076F06     'Uncorrectable                   the system error
                                                             CPU-complex Error'               on the system
                                                             cleared                          bus.
                                              [PET]          Processor: Processor             CPU is
                                              0x00076F07     Presence detected                implemented.
                                              [PET]          Processor: Processor             CPU is removed.
                                              0x80076F07     Removed
                                              [PET]          Processor: Processor             CPU is enabled.
                                              0x80076F08     Enabled
                                              [PET]          Processor: Terminator            The terminator is
                                              0x00076F09     Presence Detected                implemented.
                                              [PET]          Processor: Terminator            The terminator is
                                              0x80076F09     Removed                          removed.
                                              [PET]          Processor: Processor             A CPU
                                              0x00076F0A     Automatically Throttled          automatically
                                                                                              throttle occurred.
                                              [PET]          Processor: Processor             Recovered from
                                              0x80076F0A     Recovered from                   a CPU
                                                             Automatically Throttled          automatically
                                                                                              throttle.
            Power Supply     Others           [PET]          Power Supply: Monitoring         An even t of the
                                              0x00080301     event occurred                   power supply
                                                                                              device occurred.

                                                         SigmaSystemCenter 2.1 Reference Guide
308
                                                         Events SigmaSystemCenter Can Detect


            Classification   Event Category   Event ID     Message                       Description

                                              [PET]        Power Supply: Monitoring      Recovered from
                                              0x80080301   event cleared                 a power supply
                                                                                         device event.
                                              [PET]        Power Supply: Transition to   The power
                                              0x00080700   OK                            supply device
                                                                                         became normal.
                                              [PET]        Power Supply: Transition to   The power
                                              0x80080700   Abnormal                      supply device
                                                                                         became
                                                                                         abnormal.
                                              [PET]        Power Supply: Transition to   The power
                                              0x00080701   Non-Critical                  supply device
                                                                                         became warning
                                                                                         status.
                                              [PET]        Power Supply: Transition to   The power
                                              0x00080702   Critical                      supply device
                                                                                         became critical.
                                              [PET]        Power Supply: Transition to   The power
                                              0x00080703   Non-recoverable               supply device
                                                                                         became
                                                                                         non-recoverable.
                                              [PET]        Power Supply:                 The power
                                              0x00080B00   Redundancy Full               supply device is
                                                                                         redundant
                                                                                         configuration.
                                              [PET]        Power Supply:                 The power
                                              0x00080B01   Redundancy Lost               supply device
                                                                                         became not
                                                                                         redundant
                                                                                         configuration.
                                              [PET]        Power Supply:                 The power
                                              0x00080B02   Redundancy Degraded           supply device is
                                                                                         non-redundant
                                                                                         configuration but
                                                                                         available.
                                              [PET]        Power Supply:                 The power
                                              0x00080B03   Non-Redundant(Sufficient      supply device is
                                                           Resources)                    non-redundant
                                                                                         configuration.
                                              [PET]        Power Supply:                 The FAN is
                                              0x00080B05   Non-Redundant(Insufficient    non-redundant
                                                           Resources)                    configuration
                                                                                         and unavailable.
                                              [PET]        Power Supply: Presence        The power
                                              0x00086F00   detected                      supply device
                                                                                         was detected.
                                              [PET]        Power Supply: Removed         The power
                                              0x80086F00                                 supply device
                                                                                         was removed.
                                              [PET]        Power Supply: Power           The power
                                              0x00086F01   Supply Failure detected       supply device’s
                                                                                         failure was
                                                                                         detected.


Part III Maintenance Information
                                                                                               309
5 Error Events and Policy Actions


            Classification   Event Category          Event ID       Message                      Description

                                                     [PET]          Power Supply: Power          The power
                                                     0x80086F01     Supply Recovered             supply device
                                                                                                 recovered.
                                                     [PET]          Power Supply: Predictive     Predictive failure
                                                     0x00086F02     Failure detected             was detected on
                                                                                                 the power supply
                                                                                                 device.
                                                     [PET]          Power Supply: Power          Power supply
                                                     0x00086F03     Supply input lost (AC/DC)    input from the
                                                                                                 power supply
                                                                                                 device is lost.
                                                     [PET]          Power Supply: Power          Power supply
                                                     0x00086F04     Supply input lost or         input from the
                                                                    out-of-range                 power supply
                                                                                                 device is lost or
                                                                                                 out-of-range.
                                                     [PET]          Power Supply: Power          Power supply
                                                     0x00086F05     Supply input out-of-range,   input from the
                                                                    but present                  power supply
                                                                                                 device is
                                                                                                 out-of-range.
                                                     [PET]          Power Supply:                Configuration
                                                     0x00086F06     Configuration error          error of the
                                                                    occurred                     power supply
                                                                                                 device occurred.
            Power Unit       Prediction:power unit   [PET]          Power Unit:                  The power unit
                             failure                 0x00090B05     Non-Redundant(Insufficient   is non-redundant
                                                                    Resources)                   configuration
                                                                                                 and unavailable.
                             Others                  [PET]          Power Unit: Device           The power unit
                                                     0x00090901     Enabled                      is enabled.
                                                     [PET]          Power Unit: Device           The power unit
                                                     0x80090901     Disabled                     is disabled.
                                                     [PET]          Power Unit: Redundancy       The power unit
                                                     0x00090B00     Full                         is redundant.
                                                     [PET]          Power Unit: Redundancy       The power unit
                                                     0x00090B01     Lost                         became
                                                                                                 non-redundant.
                                                     [PET]          Power Unit: Redundancy       The power unit
                                                     0x00090B02     Degraded                     became
                                                                                                 non-redundant
                                                                                                 but available.
                                                     [PET]          Power Unit:                  The power unit
                                                     0x00090B03     Non-Redundant(Sufficient     is non-redundant
                                                                    Resources)                   configuration.
                                                     [PET]          Power Unit: D0 Power         Device Power
                                                     0x00090C00     State                        State is D0.
                                                     [PET]          Power Unit: D1 Power         Device Power
                                                     0x00090C01     State                        State is D1.
                                                     [PET]          Power Unit: D2 Power         Device Power
                                                     0x00090C02     State                        State is D2.



                                                                SigmaSystemCenter 2.1 Reference Guide
310
                                                                 Events SigmaSystemCenter Can Detect


            Classification   Event Category           Event ID     Message                         Description

                                                      [PET]        Power Unit: D3 Power            Device Power
                                                      0x00090C03   State                           State is D3.
                                                      [PET]        Power Unit: Power Off /         The power unit
                                                      0x00096F00   Power Down                      is powered OFF.
                                                      [PET]        Power Unit: Power ON            The power unit
                                                      0x80096F00                                   is powered ON.
                                                      [PET]        Power Unit: Power Cycle         Power Cycle
                                                      0x00096F01                                   was executed.
                                                      [PET]        Power Unit: 240VA Power         240VA is Power
                                                      0x00096F02   Down                            Down.
                                                      [PET]        Power Unit: Interlock           The side cover
                                                      0x00096F03   Power Down                      was opened and
                                                                                                   Power Down
                                                                                                   was executed.
                                                      [PET]        Power Unit: AC lost             AC is lost.
                                                      0x00096F04
                                                      [PET]        Power Unit: Soft Power          Power Control
                                                      0x00096F05   Control Failure (unit did not   by software
                                                                   respond to request to turn      failed.
                                                                   on)
                                                      [PET]        Power Unit: Soft Power          Power Control
                                                      0x80096F05   Control Failure cleared         by software
                                                                                                   recovered.
                                                      [PET]        Power Unit: Power Unit          Power unit
                                                      0x00096F06   Failure detected                failure occurred.
                                                      [PET]        Power Unit: Power Unit          Recovered from
                                                      0x80096F06   Failure cleared                 the power unit
                                                                                                   failure.
                                                      [PET]        Power Unit: Predictive          Detected the
                                                      0x00096F07   Failure detected                predictive failure
                                                                                                   of the power
                                                                                                   unit.
                                                      [PET]        Power Unit: Predictive          Cleared the
                                                      0x80096F07   Failure cleared                 predictive failure
                                                                                                   of the power
                                                                                                   unit.
            Cooling          Prediction:fan/cooling   [PET]        Cooling Device: Lower           Fell below the
            Device           device failure           0x000A0102   Critical - going low            lower critical limit
                                                                                                   of the cooling
                                                                                                   device.
                                                      [PET]        Cooling Device: Lower           Fell below the
                                                      0x000A0104   Non-recoverable - going         lower
                                                                   low                             non-recoverable
                                                                                                   limit of the
                                                                                                   cooling device.
                                                      [PET]        Cooling Device: Upper           Exceeded the
                                                      0x000A0109   Critical - going high           upper critical
                                                                                                   limit of the
                                                                                                   cooling device.




Part III Maintenance Information
                                                                                                           311
5 Error Events and Policy Actions


            Classification   Event Category       Event ID       Message                      Description

                                                  [PET]          Cooling Device: Upper        Exceeded the
                                                  0x000A010B     Non-recoverable - going      upper
                                                                 high                         non-recoverable
                                                                                              limit of the
                                                                                              cooling device.
                                                  [PET]          Cooling Device: Transition   The cooling
                                                  0x000A0702     to Critical                  device became
                                                                                              the critical level.
                                                                                              The liquid might
                                                                                              spill.
                             Clear Alert:         [PET]          Cooling Device: Lower        Recovered from
                             fan/cooling device   0x800A0102     Critical - going high        the lower critical
                             failure recovery                                                 limit of the
                                                                                              cooling device.
                                                  [PET]          Cooling Device: Upper        Fell below the
                                                  0x800A0109     Critical - going low         upper critical
                                                                                              limit of the
                                                                                              cooling device.
                                                  [PET]          Cooling Device: Transition   The cooling
                                                  0x000A0700     to OK                        device became
                                                                                              normal.
                             Others               [PET]          Cooling Device: Lower        Fell below the
                                                  0x000A0100     Non-critical - going low     lower warning
                                                                                              limit of the
                                                                                              cooling device.
                                                  [PET]          Cooling Device: Lower        Recovered from
                                                  0x800A0100     Non-critical - going high    the lower
                                                                                              warning limit of
                                                                                              the cooling
                                                                                              device.
                                                  [PET]          Cooling Device: Lower        Recovered from
                                                  0x800A0104     Non-recoverable - going      the lower
                                                                 high                         non-recoverable
                                                                                              limit of the
                                                                                              cooling device.
                                                  [PET]          Cooling Device: Upper        Exceeded the
                                                  0x000A0107     Non-critical - going high    upper warning
                                                                                              limit of the
                                                                                              cooling device.
                                                  [PET]          Cooling Device: Upper        Recovered from
                                                  0x800A0107     Non-critical - going low     the upper
                                                                                              warning limit of
                                                                                              the cooling
                                                                                              device.
                                                  [PET]          Cooling Device: Upper        Recovered from
                                                  0x800A010B     Non-recoverable - going      the upper
                                                                 low                          non-recoverable
                                                                                              limit of the
                                                                                              cooling device.
                                                  [PET]          Cooling Device: Transition   The cooling
                                                  0x800A0700     to Abnormal                  device became
                                                                                              abnormal.




                                                             SigmaSystemCenter 2.1 Reference Guide
312
                                                         Events SigmaSystemCenter Can Detect


            Classification   Event Category   Event ID     Message                       Description

                                              [PET]        Cooling Device: Transition    The cooling
                                              0x000A0701   to Non-Critical               device became
                                                                                         the warning
                                                                                         level.
                                              [PET]        Cooling Device: Transition    The cooling
                                              0x000A0703   to Non-recoverable            device became
                                                                                         the
                                                                                         non-recoverable
                                                                                         level.
                                                                                         The liquid might
                                                                                         spill.
                                              [PET]        Cooling Device:               The cooling
                                              0x000A0B00   Redundancy Full               device is
                                                                                         redundant
                                                                                         configuration.
                                              [PET]        Cooling Device:               The cooling
                                              0x000A0B01   Redundancy Lost               device became
                                                                                         not redundant
                                                                                         configuration.
                                              [PET]        Cooling Device:               The cooling
                                              0x000A0B02   Redundancy Degraded           device is not
                                                                                         redundant but
                                                                                         available.
                                              [PET]        Cooling Device:               The cooling
                                              0x000A0B03   Non-Redundant(Sufficient      device is
                                                           Resources)                    non-redundant
                                                                                         configuration.
                                              [PET]        Cooling Device:               The cooling
                                              0x000A0B05   Non-Redundant(Insufficient    device is
                                                           Resources)                    non-redundant
                                                                                         configuration
                                                                                         and unavailable.
            Memory           Memory failure   [PET]        Memory: Uncorrectable         Uncorrectable
                                              0x000C6F01   ECC occurred                  ECC error
                                                                                         occurred.
                                              [PET]        Memory: Memory Parity         Memory Parity
                                              0x000C6F02   Error occurred                Error occurred.
                                              [PET]        Memory: Correctable ECC       1bit error occurs
                                              0x000C6F05   / other correctable memory    frequently.
                                                           error logging limit reached
                             Memory failure   [PET]        Memory: Uncorrectable         Recovered from
                             recovery         0x800C6F01   ECC cleared                   Uncorrectable
                                                                                         ECC error.
                             Others           [PET]        Memory: Transition to OK      The memory
                                              0x000C0700                                 became normal.
                                              [PET]        Memory: Transition to         The memory
                                              0x800C0700   Abnormal                      became
                                                                                         abnormal.
                                              [PET]        Memory: Transition to         The memory
                                              0x000C0701   Non-Critical                  became the
                                                                                         warning status.
                                              [PET]        Memory: Transition to         The memory
                                              0x000C0702   Critical                      became critical.

Part III Maintenance Information
                                                                                                313
5 Error Events and Policy Actions


            Classification   Event Category   Event ID       Message                      Description

                                              [PET]          Memory: Transition to        The memory
                                              0x000C0703     Non-recoverable              became
                                                                                          non-recoverable.
                                              [PET]          Memory: Redundancy Full      The memory is
                                              0x000C0B00                                  redundant
                                                                                          configuration.
                                              [PET]          Memory: Redundancy Lost      The memory
                                              0x000C0B01                                  became not
                                                                                          redundant
                                                                                          configuration.
                                              [PET]          Memory: Redundancy           The memory is
                                              0x000C0B02     Degraded                     not redundant
                                                                                          but available.
                                              [PET]          Memory:                      The memory is
                                              0x000C0B03     Non-Redundant(Sufficient     non-redundant
                                                             Resources)                   configuration.
                                              [PET]          Memory:                      The memory is
                                              0x000C0B05     Non-Redundant(Insufficient   non-redundant
                                                             Resources)                   configuration
                                                                                          and unavailable.
                                              [PET]          Memory: Correctable ECC      1bit error
                                              0x000C6F00     occurred                     occurred.
                                              [PET]          Memory: Correctable ECC      Recovered from
                                              0x800C6F00     cleared                      1bit error.
                                              [PET]          Memory: Memory Parity        Recovered from
                                              0x800C6F02     Error cleared                Memory Parity
                                                                                          Error.
                                              [PET]          Memory: Memory Scrub         Memory Scrub
                                              0x000C6F03     Failed (stuck bit)           failed.
                                              [PET]          Memory: Memory Scrub         Recovered from
                                              0x800C6F03     Error cleared (stuck bit)    Memory Scrub
                                                                                          error.
                                              [PET]          Memory: Memory Device        The memory is
                                              0x000C6F04     Disabled                     disabled.
                                              [PET]          Memory: Memory Device        The memory is
                                              0x800C6F04     Enabled                      enabled.
                                              [PET]          Memory: Correctable ECC      1bit error was
                                              0x800C6F05     have receded.                receded.
                                              [PET]          Memory: Presence             The memory is
                                              0x000C6F06     detected                     implemented.
                                              [PET]          Memory: Removed              The memory is
                                              0x800C6F06                                  removed.
                                              [PET]          Memory: Configuration        Memory
                                              0x000C6F07     error                        configuration
                                                                                          error occurred.
                                              [PET]          Memory: Configuration        Recovered from
                                              0x800C6F07     Error cleared                memory
                                                                                          configuration
                                                                                          error.
                                              [PET]          Memory: Spare entity         A spare of the
                                              0x000C6F08                                  memory.

                                                         SigmaSystemCenter 2.1 Reference Guide
314
                                                               Events SigmaSystemCenter Can Detect


            Classification   Event Category         Event ID     Message                        Description

                                                    [PET]        Memory: Not spare entity       Primary
                                                    0x800C6F08                                  memory.
                                                    [PET]        Memory: Memory                 The memory
                                                    0x000C6F09   Automatically Throttled.       automatically
                                                                                                throttle occurred.
                                                    [PET]        Memory: Memory                 Recovered from
                                                    0x800C6F09   recovered from                 the memory
                                                                 Automatically Throttled.       automatically
                                                                                                throttle.
                                                    [PET]        Memory: Critical               Over
                                                    0x000C6F0A   Overtemperature.               temperature of
                                                                                                the memory
                                                                                                occurred.
                                                    [PET]        Memory: Memory                 Recovered from
                                                    0x800C6F0A   Temperature Error              the over
                                                                 Recovered                      temperature of
                                                                                                the memory.
            Slot             Others                 [PET]        Drive Slot(Bay): Device        Devices are
                                                    0x000D0801   Inserted/Device Present        implemented on
                                                                                                the slot.
                                                    [PET]        Drive Slot(Bay): Device        Devices are
                                                    0x800D0801   Removed/Device Absent          removed from
                                                                                                the slot.
                                                    [PET]        Drive Slot(Bay): Device        Devices are
                                                    0x000D6F00   Presence                       implemented on
                                                                                                the slot.
                                                    [PET]        Drive Slot(Bay): Removed       Devices are
                                                    0x800D6F00                                  removed from
                                                                                                the slot.
                                                    [PET]        Drive Slot(Bay): Drive Fault   The failure of the
                                                    0x000D6F01                                  drive device of
                                                                                                the slot
                                                                                                occurred.
                                                    [PET]        Drive Slot(Bay): Drive         Recovered from
                                                    0x800D6F01   Recovered                      the failure of the
                                                                                                drive device of
                                                                                                the slot.
            POST Memory      Memory                 [PET]        POST Memory Resize:            Memory resize
                             degeneration failure   0x000E0301   Monitoring event occurred      occurred.
                             Memory failure         [PET]        POST Memory Resize:            Recovered from
                             recovery               0x800E0301   Monitoring event cleared       the memory
                                                                                                resize.
            POST Error       Others                 [PET]        POST Error: Monitoring         POST error
                                                    0x000F0301   event occurred                 occurred.
                                                    [PET]        POST Error: Monitoring         Recovered from
                                                    0x800F0301   event cleared                  the POST error.
                                                    [PET]        POST Error: System             Firmware error
                                                    0x000F6F00   Firmware Error.                occurred.
            Event logging    Others                 [PET]        Event Logging: Correctable     1bit error
                                                    0x00106F00   Memory Error Logging           records are
                                                                 Disabled                       invalid.


Part III Maintenance Information
                                                                                                       315
5 Error Events and Policy Actions


            Classification   Event Category   Event ID       Message                         Description

                                              [PET]          Event Logging: Specific         Specified events
                                              0x00106F01     Event Logging Disabled          records are
                                                                                             invalid.