Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
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
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
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
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
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
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."
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.
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.
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.
xii
Part I SigmaSystemCenter
Functions Reference
1
1. Functions of SigmaSystemCenter
This chapter explains the functions of SigmaSystemCenter from the overview to detailed information,
such as internal processes.
3
1 Functions of SigmaSystemCenter
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
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.
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.
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.
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."
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.
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.
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.
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.
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.
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 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.
Refer to the following subsections for detailed explanation of the distribution software.
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.
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.
For more details of the use of a scenario, see Section 1.5 "Use of a Scenario."
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.
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).
These are the operations to create a scenario in DPM and register the scenario as
distribution software in SystemProvisioning.
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.
The state of the distribution software installation to the machine added to the group
is as follows;
The following table shows the distribution target and the timing of distribution.
The following table shows the predefined distribution order of operating distribution
software.
The following table shows the predefined distribution order of standby distribution
software.
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.
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
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.
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.
Related to Networks
Related to Storage
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
• 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
Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\DPMProvider
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
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.
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.
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.
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.
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:
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.
Install NEC Storage Manager and NEC Storage Manager Integration Base and
configure the initial settings of them.
• 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.
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:
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.
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.
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 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.
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.
- 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.
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.
• 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.
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.
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.
- 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.
symmask -sid [symmID] -wwn [WWN] add devs [LD] -dir [DIR]
-p [PORT]
symmask -sid [symmID] refresh -noprompt
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.
Connection information including the IP address of the SP and the account is needed
during the connection control.
RAID groups to which the LUNs are to belong must be created to create the
LUNs. SigmaSystemCenter does not support MetaLun.
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.
- 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.
In addition, when you perform operations, such as N+1 Failover, you need to prepare
pool machines.
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.
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 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.
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.
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
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.
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.
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.
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.
Note: SystemProvisioning does not support this operation for a virtual machine server.
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.
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.
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.
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”.
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.
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.
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.
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.
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.
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.
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.
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.
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.
▪ If you execute this operation on virtual machines in power ON status, they might be
powered OFF.
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.
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.
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.
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.
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.
• 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.
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.
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.
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.
• 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
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
• 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.
• 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.
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
Power OFF N/A N/A 1 N/A N/A 1 ▪ High risk at disk damage,
etc
Power Cycle N/A N/A 1 N/A N/A N/A ▪ No start check with OS
▪ High risk at disk damage,
etc
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
You can execute each power control operation from a window or command. The
following table shows how you can execute the power operations.
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.
Start X X X poweron
Power ON X
(Maintenance
Command) *1
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.
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".
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.
- 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.
Timeout
Timeout time after shutting down (the OS Status OFF) until the Power Status turns to OFF
Waiting time after the OS Status turns to ON until the "Start" job completes
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)
Waiting time for completion of Shutdown job (if checking the Power Status is not
available)
Waiting time after the OS Status turns to OFF until the "Shutdown" job completes (if
checking the Power Status is not available)
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.
*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.
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.
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.
Timeout
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
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
Timeout time from the start of Power ON until the PowerOnTimeout 320
process completion
Timeout time from the start of Power OFF until the PowerOffTimeout 260
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
Timeout
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
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
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
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.
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).
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.
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
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.
Functional differences between Hyper-V Cluster and Hyper-V single server are as
follows:
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.
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.
The term "partition" is used to refer to virtual machines in Hyper-V. "Partition" is divided
into the following two types:
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
The following setting items in old versions are integrated into Machine Profile setting.
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.
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.
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
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.
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
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.
Hyper-V The set value * 100 / (the number of CPU * the host clock frequency
(MHz))
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.
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
XenServer
Set the name of the destination network.
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.
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.
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.
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.
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.
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.
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.
If you are using Windows, use Sysprep to set information of guest OS. Sysprep is
executed from DeploymentManager.
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.
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.
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.
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.
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.
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.
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.
New templates do not have to be created because already created templates are
available, but new images must be created.
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.
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.
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.
Computer name
IP address
Product Key
The security identifier (SID)
DeploymentManager (DPM)
vCenter Server (VC)
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.
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) -".
C:\<ALLUSERSPROFILE>\Application Data\Vmware\VMware
VirtualCenter\sysprep (if the system drive is C:).
Normally, <ALLUSERSPROFILE> is \Documents And Settings\All
Users\.
C:\<ALLUSERSPROFILE>\Vmware\VMware VirtualCenter\sysprep.
Normally, <ALLUSERSPROFILE> is \ProgramData\.
- .\2k\
- .\xp\
- .\svr2003\
- .\xp-64\
- .\svr2003-64\
- deptool.chm
- readme.txt
- setupcl.exe
- setupmgr.exe
- setupmgx.dll
- sysprep.exe
- unattend.doc
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.
Sysprep will work automatically at the timing of the processes described in blue with
under lines in the following figure.
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.
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.
• 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.
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).
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.
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.
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.
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.
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.
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.
To execute these operations, a destination and source virtual machine server and a
target virtual machine must meet the following conditions:
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.
Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Engine
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.
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.
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 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.
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.
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.
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.
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.
SigmaSystemCenter's recovery functions for virtual machine servers down have two
major advantages:
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.
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.
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.
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.
Products / components that execute server down monitoring of virtual machine servers
are different depending on the types of monitoring targets as the following table.
The following figure is an explanation of the server down monitoring action that is
executed by NEC ESMPRO Manager and NEC ESMPRO Agent.
Routes to obtain events are different depending on the types of monitoring targets as
follows.
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.
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:
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.
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.
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.
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
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.
[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).
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.
# vi /etc/syslog.conf
(Omitted)
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.
~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).
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.
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)".
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.
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.
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.
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.
This part describes the list and the usage of commands in SigmaSystemCenter.
235
3. Details of Action Sequence
237
3 Details of Action Sequence
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.
This chapter explains the command line interface, CLI, which can be executed the operations of
SystemProvisioning from programs, such as Command Prompt.
243
4 Command Reference
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.
The execution results of pvmutl commands can be determined by their return values.
Return values of pvmutl commands are as follows.
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.
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.
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]
[Syntax examples]
>pvmutl move Category1 Grp2
>pvmutl move Category1\Grp1 Grp2 /c 10
>pvmutl move Category1\Grp1 Grp2 host01
Reference: For more detail of Replace Machine, see Subsection 1.10.6, "Replacing
Machine (Physical Machine)."
[Syntax]
pvmutl replace GroupName HostName
[Syntax examples]
>pvmutl replace Category\Grp1 host01
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]
[Syntax examples]
>pvmutl add Category1
>pvmutl add Category1\Grp1\Model1 Machine1
>pvmutl add Grp1 /c 10
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]
[Syntax examples]
>pvmutl addspecname Category1\Grp1\Model1 LogicalServer1
Machine1
>pvmutl addspecname Grp1 192.168.1.1 Machine1
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]
[Syntax examples]
>pvmutl delete Category1
>pvmutl delete Grp1 host1
>pvmutl delete Grp1 /c 10
[Syntax]
pvmutl deploygrp GroupName [/f | /p SoftwareName
[,SoftwareName]...] [/seq]
[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"
[Syntax]
pvmutl deploysrv GroupName HostName
[/a Software Name[,SoftwareName]... | /f |
/p SoftwareName [,SoftwareName]...]
[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
[Syntax]
pvmutl deploypsv MachineName
Software Name[,SoftwareName]...
[Syntax examples]
>pvmutl deploypsv Machine01 "soft1"
>pvmutl deploypsv Machine01 "soft1","soft2"
[Syntax]
pvmutl maintenance {On|Off} GroupName [HostName]
[Syntax examples]
>pvmutl maintenance on grp1
>pvmutl maintenance off grp1 host01
[Syntax]
pvmutl list group
================
ServerGroup List
================
group1
model1_1
model1_2
group2
model2_1
model2_2
[Syntax]
pvmutl list server GroupName
[Parameters]
===========
Pool
===========
Machine 3
[Syntax examples]
pvmutl list server grp1
[Syntax]
pvmutl list soft GroupName
[Syntax examples]
>pvmutl list soft grp1
[Syntax]
pvmutl shutdown GroupName [HostName...]
[Syntax examples]
>pvmutl shutdown grp1 host01
>pvmutl shutdown grp1 host01 host02 host03
>pvmutl shutdown grp1
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]
[Syntax examples]
>pvmutl reboot grp1 host01
>pvmutl reboot grp1 host01 host02 host03
>pvmutl reboot grp1
>pvmutl reboot grp1 host01 /q
>pvmutl reboot grp1 /q
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]
[Syntax examples]
>pvmutl poweron grp1 host01
>pvmutl poweron grp1 host01 host02 host03
>pvmutl poweron grp1
>pvmutl poweron grp1 host01 /q
>pvmutl poweron grp1 /q
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]
[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
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]
[Syntax examples]
>pvmutl vmdelete Category\Grp1 host01 /d
>pvmutl vmdelete Category
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]
[Syntax examples]
>pvmutl vmmigrate Category1\Grp1 host01 VMS01
>pvmutl vmmigrate Category1\Grp1 host01 VMS01 /n
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]
[Syntax examples]
>pvmutl vmmigrateandmove Category1\Grp1 host01 VMS01
>pvmutl vmmigrateandmove Category1\Grp1 host01 VMS01 /n
Displaying Jobs
Lists Jobs of running action sequences and their running status.
[Syntax]
pvmutl asjob [-a | -s | -d]
[List sample]
Displays as follows:
>pvmutl asjob
Total job : 2
[Syntax examples]
pvmutl asjob
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]
[Syntax examples]
Displays as follows:
>pvmutl ascancel
========================================
ActionSequence List
========================================
00011
00012
[Syntax examples]
pvmutl ascancel
pvmutl ascancel 00011
[Syntax]
pvmutl changepassword UserName OldPassword NewPassword
[Syntax examples]
>pvmutl changepassword user01 pvmuser1 pvmuser2
[Syntax]
pvmutl policy show [GroupName]
[Syntax examples]
Displays as follows:
[Syntax]
pvmutl policy set GroupName [PolicyName] [/y]
[Syntax examples]
>pvmutl policy set grp1 policy2
>pvmutl policy set grp1
>pvmutl policy set grp1 /y
1. Error output
After executing a command, when an error of an action is generated,
SystemProvisioning outputs the error.
Success : 2
Failure : 1
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.
275
5 Error Events and Policy Actions
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.
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.
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.
This section explains the events that these products or component can detect and the
checking procedure of detected events.
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
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
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.
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.
5. The system starts writing the monitoring target to a file. The following dialog box is
displayed during writing.
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.
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.
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.
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.
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.
The table below displays the condition of discarding SNMP Trap filtered by
SigmaSystemCenter.
*3 Virtual machines go into the Paused-Critical state if the free space of CSV falls below
200MB. CSV[Critical] event is notified when a virtual machine is in the Paused-Critical
state.
CSV[NonCritical] event is notified when the capacity monitoring detects the free space
of CSV exceeds 200MB, which does not automatically recover virtual machines from its
Paused-Critical state. Those virtual machines need to be manually started after verifying
that there is sufficient free space.
*4 Cluster: Node recovery events do not occur in all recovery case. Events might not occur
depending on the recovery way.
Success:
Executes an action that is registered one above the action that you are setting and
executes the action that you are setting when the action that is registered one
above is completed.
If the action registered one above is not executed or its execution result is an error,
the action that you are setting is not executed.
Completed:
Executes the action that you are setting when the action that is registered one
above is completed.
If the action registered one above is not executed, the action that you are setting is
not executed.
If you cancel the execution of an action while the action is being executed, the
execution process is aborted and the Job ends with an error. In this case, latter actions
are not executed and end no matter what execution results are set.
The execution result of all actions is displayed as completed only when all the actions
are completed. Even one action ends with an error, other actions end with an error.
Note: If the action of an analysis of HW sensor conditions or the Set Faulted Status
ends with an error, the next action will not be executed. However, the execution result
of all actions is displayed as completed exceptionally.
The following is an example of when the following settings are set as the corresponding
event handler settings for the Machine inaccessible error, supposing that there
occurred a Machine inaccessible error on a virtual machine server.
Reference: For instructions on how to set suppression events, see Subsection 3.9.5,
"Configuring Policy Property Settings" in SigmaSystemCenter Configuration Guide.
A policy action of the investigation function, Investigate and Power OFF, ends with an
error if the recovery process cannot be executed because the error has an influence on
a whole group or if an error machine is judged normal. If the investigation function
judges that there is a possibility for the recovery process to succeed, the function
aborts the managed machine and completes the process. Ensure to set Success to the
execution condition of recovery action after executing the Investigate and Power OFF
action.
Note: The root password must be set for ESX. If not, verification of connection will fail.
The root password can be set from the Virtual Resource tab or the Subsystem Edit
window. The Virtual Resource tab appears by clicking the Environment icon on the
Management view. The Subsystem Edit window appears by clicking the Subsystem
icon on the Management view.
For further information on how to set the root password, see Subsection 2.13.4, "Virtual
Resource Tab" in SigmaSystemCenter Reference Guide Web Console.
The investigation function can be used only when a managed machine is a virtual
machine server (VMware, XenServer). If the Investigate and Power OFF action is
executed on a managed machine other than virtual machine servers (VMware,
XenServer), Investigation will not be executed but Shutdown or Power OFF will be
executed. For the details of the policy action, see Subsection 5.7.13, “Action for
machine / Investigate and Power OFF”.
If the function can connect to VMware vCenter Server or Pool Master of XenServer
that manages an error machine
If there are two or more managed machines that raises Faulted as their Hardware
Status in a group to which the error machine belongs
If the function connects to an (host) OS of managed machines
(The function checks this point on up to five machines in the same group as the
error machine other than the error machine.)
The details of abnormal end of the Investigate and Power OFF action are as shown in
the following table:
ESXi Standalone ▪ If connection to an error machine ends ▪ When there are many
with an authority error or is disconnected machines that cannot connect
in SSC. to an OS or access to the
▪ There are two or more failed machines disk, the investigation function
in one group (other than the error judges the circumstances that
machine). it should not execute the
recovery process and ends
▪ When the number of machines that the process with an error.
cannot connect to an OS of machines in
the same group (including the error
machine)
- When there are two to four machines in
the group: two or more
- When there are five or more machines in
the group: three or more
▪ When the number of machines that
cannot connect to the shared disk in the
same group (including the error machine)
- When there are two to four machines in
the group: two or more
- When there are five or more machines in
the group: three or more
▪ If an error machine is normal.
The Machine status / Set faulted status by an analysis of HW sensor conditions policy
action ends abnormally when it decides that the machine suspected of failure is normal.
And the rule of diagnosis of machine depends on the type of triggered event or
machine status.
There are cases that the action cannot obtain the sensor status properly because of the
machine power status. In this case the action decides the result as following by the
machine power status.
Case: The machine power status changes while the action runs
This case may occur if the machine is automatically shut down or rebooted by HW
failure. In this case, the action decides that the machine has HW failure and sets
faulted status and ends normally.
Case: The machine power status is already off before the action runs
The machine power turned off before the action runs because the machine was in
critical or non-recoverable state. In this case, the action decides that the machine
has HW failure and sets faulted status and ends normally.
Note:
▪ This action targets the power-on machine where HW failure occurred. Therefore, you
cannot obtain an accurate result if you execute this action to the power-off machine.
▪ When you executes this action for the machine which the OOB Management function
is not enabled, this action sets faulted status and ends normally.
▪ The criteria of severity of sensor status are independent from event categories.
Therefore, there is a case the action decides the machine is normal if it was executed
by the event categorized in failure.
▪ It is recommended that you should use this action only provided in Standard Policies
because it is difficult to manipulate this action and unexpected failure may occur.
The following tables show the detail description of the relationships among the type of
the triggered event, connection and machine status and the result of action.
The case: the machine power is on before and after this action executes.
OobManagement event The sensor, which sent a This action sets faulted status
categorized in HW Predictive predictive event, is in critical and ends normally.
events state.
The sensor, which sent a There is no failure, and this
predictive event, is in warning action does not set faulted
or normal state. state and ends abnormally.
This action cannot get This action ends in a status
information of the sensor depends on the event severity.
which sent a predictive event. If the severity of event is
critical, this action sets faulted
status and ends normally.
▪ This action could not This action ends in a status
communicate with BMC. depends on the event severity.
▪ This action failed to execute If the severity of event is
IPMI command to BMC. critical, this action sets faulted
status and ends normally.
▪ An unexpected error
occurred.
Other OOBManagement Even one of the sensors in the This action sets faulted status
events machine is in critical state. and ends normally.
All sensors in the machine are There is no failure, and this
in warning or normal state. action does not set faulted
state and ends abnormally.
The following table: the relation between power status of the machine and result of
action.
These situations have a priority over the sensor analysis result.
The power status changes before and after This action sets faulted status and ends
sensor analysis. normally.
The power status is off before the sensor This action sets faulted status and ends
analysis. normally.
Standard policies that are registered by default are “OK” will be registered when
applying the edition license.
The System Policy (Manager) is automatically applied to managers to monitor them,
such as share resources. One System Policy (Manager) exists on one system.
Configuring the System Policy on a group is unnecessary because it is not applied for
managed machines.
Do not delete the System Policy (Manager) or do not change its name. If its name is
changed, it will not be automatically applied because it is not recognized as the System
Policy (Manager). If the System Policy (Manager) should be deleted by mistake or its
name should be changed, it can be restored by restarting the PVMService. It can not
be added from the Add Policy menu.
When disabling the System Policy (Manager), disable the monitoring event setting.
Note: If you select an event of a Standard Policy configured with multiple events on the
Policy Property Setting window and open the Corresponding Event Handler Setting
window of the event, the All event in category check box is selected automatically, and
Others is displayed in the Event Category box. In addition, Component Events column
is displayed below the Event Name box, on which a list of corresponding events is
displayed.
Machine
status / Set
degraded
status
Disk failure SystemMonitorEvent All events in the Hard disk Set Faulted Notification/ Enable
failure event category Status E-mail, Event
Log
Machine
status / Set
faulted status
disk recovery SystemMonitorEvent All events in the Hard disk Set Machine Enable
failure recovery failure event degraded status / Set
category status degraded
status
Recovery from SystemMonitorEvent All events in the Recovery Set Ready Notification/ Enable
the disk from the hard disk recovery Status E-mail, Event
recovery failure failure event category Log
Machine
status / Set
ready status
machine down SystemMonitorEvent ESMDSVNT[0xC0000002] Set Faulted Notification/ Enable
No response from the server Status E-mail, Event
Log
VMwareProvider All events in the Machine Machine
inaccessible error event status / Set
category faulted status
start up SystemMonitorEvent ESMDSVNT[0x40000001] Set Ready Notification/ Enable
machine The server access recovered Status E-mail, Event
Log
VMwareProvider All events in the Machine Machine
inaccessible error recovery status / Set
event category ready status
Memory SystemMonitorEvent All events in the Memory Set Notification/ Enable
degeneration degeneration failure event Degraded E-mail, Event
failure category status Log
VMwareProvider Alarm Virtual Machine Machine
Memory Usage on VM status / Set
changed from green to red degraded
status
Alarm Virtual Machine
Memory Usage on VM
changed from yellow to red
Alarm Virtual Machine
Memory Usage on VM
changed from yellow to red
Memory failure SystemMonitorEvent All events in the Memory Set Faulted Notification/ Enable
failure event category Status E-mail, Event
Log
Machine
status / Set
faulted status
Cluster:Node SystemMonitorEvent CLUSTERPRO[0xC00008A4] Set Faulted Notification/ Enable
has stopped Status E-mail, Event
Log
Machine
status / Set
faulted status
Cluster:Network SystemMonitorEvent CLUSTERPRO[0xC0005217] Set Faulted Notification/ Enable
failure Status E-mail, Event
Log
Machine
status / Set
faulted status
custom group SystemMonitorPerf 11000001 no action no action Disable
notification 1
custom group SystemMonitorPerf 11000002 no action no action Disable
notification 2
custom group SystemMonitorPerf 11000003 no action no action Disable
notification 3
custom group SystemMonitorPerf 11000004 no action no action Disable
notification 4
custom group SystemMonitorPerf 11000005 no action no action Disable
notification 5
custom SystemMonitorPerf 10000001 no action no action Disable
machine
notification 1
custom SystemMonitorPerf 1000000A no action no action Disable
machine
notification 10
custom SystemMonitorPerf 10000002 no action no action Disable
machine
notification 2
custom SystemMonitorPerf 10000003 no action no action Disable
machine
notification 3
custom SystemMonitorPerf 10000004 no action no action Disable
machine
notification 4
custom SystemMonitorPerf 10000005 no action no action Disable
machine
notification 5
custom SystemMonitorPerf 10000006 no action no action Disable
machine
notification 6
High CPU VMwareProvider Alarm Virtual Machine Set Faulted Status Notification/ Enable
Load CPU Usage on VM E-mail, Event
changed from yellow to Log
red
Machine status /
Alarm Virtual Machine Set faulted
CPU Usage on VM status
changed from green to
red
Alarm Virtual Machine
CPU Usage on VM
changed from gray to red
High CPU VMwareProvider Alarm Virtual Machine Set Ready Status Notification/ Enable
Load CPU Usage on VM E-mail, Event
Recovery changed from gray to Log
green
Machine status /
Alarm Virtual Machine Set ready status
CPU Usage on VM
changed from yellow to
green
Alarm Virtual Machine
CPU Usage on VM
changed from red to
green
Machine VMwareProvider Alarm Virtual Machine Set Faulted Status Notification/ Enable
Down Heartbeat on VM E-mail, Event
changed from gray to red Log
Alarm Virtual Machine Machine status /
Heartbeat on VM Set faulted
changed from green to status
red
Machine Off VMwareProvider VM on VMS in DC is Set Faulted Status Notification/ Enable
powered off E-mail, Event
Log
Machine status /
Set faulted
status
Machine Up VMwareProvider Alarm Virtual Machine Set Ready Status Notification/ Enable
Heartbeat on VM E-mail, Event
changed from gray to Log
green
Machine status /
Alarm Virtual Machine Set ready status
Heartbeat on VM
changed from red to
green
VM on VMS in DC is
powered on
Shortage of VMwareProvider Alarm Virtual Machine Set Degraded Machine status / Disable
Memory Memory Usage on VM Status Set degraded
changed from gray to red status
Alarm Virtual Machine
Memory Usage on VM
changed from green to
red
Alarm Virtual Machine
Memory Usage on VM
changed from yellow to
red
Shortage of VMwareProvider Alarm Virtual Machine Set Ready Status Machine status / Disable
Memory Memory Usage on VM Set ready status
recovery changed from gray to
green
Alarm Virtual Machine
Memory Usage on VM
changed from red to
green
Alarm Virtual Machine
Memory Usage on VM
changed from yellow to
green
Machine Up HyperVProvider Resources(VM)[Online] Set Ready Status Notification/ Enable
Notification E-mail, Event
Log
Machine status /
Set ready status
Machine HyperVProvider Resources(VM)[Failed] Set Faulted Status Notification/ Enable
Down E-mail, Event
Notification Log
Machine status /
Set faulted
status
*1 A suppressing function is configured to event monitoring. (For the details of the suppressing
function, see Subsection 1.3.4, "What is a Policy?")
The corresponding events and suppressing events are as follows:
▪ The suppressing event of the event High CPU Load is High CPU Load Recovery
▪ The suppressing event of the event High CPU Load Recovery is High CPU Load
▪ The suppressing event of the event Machine Down is Machine Up
▪ The suppressing event of the event Machine Up is Machine Down
▪ The suppressing event of the event Shortage of Memory is Shortage of Memory recovery
▪ The suppressing event of the event Shortage of Memory recovery is Shortage of Memory
In addition, the time to monitor these suppressing events is set to 180 seconds.
*2 Suppression events of the Policy Property setting window cannot be set on the above events.
VMS connection VMwareProvider Alarm Host connection Set Ready Notification/ Disable
state is green *1 state on VMS changed Status E-mail, Event
from gray to green Log
Alarm Host connection Machine
state on VMS changed status / Set
from red to green ready status
VMS connection VMwareProvider Alarm Host connection Move all Notification/ Disable
state is red *1 state on VMS changed running VMs E-mail, Event
from gray to red on the VM Log
Alarm Host connection server
Machine
state on VMS changed status / Set
from green to red faulted status
Action for
machine/
Investigate
and Power
OFF
Action for
VMS / Move
all running
VMs on the
VM server.
(Hot
Migration,
Failover)
Machine Up SystemMonitorEvent ESMDSVNT[0x40000001] Set Ready Notification/ Enable
he server access Status E-mail, Event
recovered Log
Machine
status / Set
ready status
*1 This is a monitoring setting for events of machine down and startup of a virtual machine
server available with working together with vCenter Server. You can select the operation
mode of configuring to switch machine down and startup machine available with working
together with NEC ESMPRO Manager and restoration process.
*2 Disabled in Standard Policy (VM Server) and Standard Policy (VM Server Predictive).
Enabled in Standard Policy (VM Server Power Saving).
*3 You can set the Suppress Machine inaccessible error towards the VMS Access Impossible
event and the Target Access Impossible event.
The Suppress CPU Load failure is not set.
For instructions on how to set the suppression on an event, see Subsection 3.9.5,
“Configuring Policy Property Settings” in SigmaSystemCenter Configuration Guide.
VMS connection VMwareProvider Alarm Host connection state on Move all Notification/ Disable
state is red VMS changed from gray to red running E-mail,
Alarm Host connection state on VMs on Event Log
VMS changed from green to the VM
server Machine
red status / Set
faulted
status
Action for
machine/
Investigate
and Power
OFF
Action for
VMS/ Move
all VMs on
the VM
server.
(Failover)
Machine Up SystemMonitorEvent ESMDSVNT[0x40000001] The Set Ready Notification/ Disable
server access recovered Status E-mail,
Event Log
Machine
status / Set
ready
status
Machine Down SystemMonitorEvent ESMDSVNT[0xC0000002] No Set Notification/ Disable
response from the server Faulted E-mail,
Status Event Log
Machine
status / Set
faulted
status
Network Interface HyperVProvider NetworkInterface[Failed] Set Notification/ *2
Failure NetworkInterface[Unavailable] Degraded E-mail,
status Event Log
NetworkInterface[Unreachable]
Machine
status / Set
degraded
status
Network Interface HyperVProvider NetworkInterface[Up] no action no action Disable
Recovery
In addition to the above events, the HW Predictive event (refer to Subsection 5.6.7) is provided.
▪ The HW Predictive event is disabled in Standard Policy (VM Server Hyper-V).
▪ The HW Predictive event is enabled in Standard Policy (VM Server Hyper-V Predict). (Recovery events are
disabled.)
*1 Failure and recovery events of connectivity to virtual machine servers are monitored through
Microsoft Failover Cluster. An alternative way to monitor virtual machine servers is provided
by NEC ESMPRO Manager. The operation form of the alternative way is that replaces
recovery action with “Machine Access Impossible” and “Machine Access Recovery” which
are detected by NEC ESMPRO Manager.
*2 Disabled in Standard Policy (VM Server Hyper-V) .
Enabled in Standard Policy (VM Server Hyper-V Predictive)
Content of mails and event logs are different from the content of other policies’
notification. (Refer to Subsection 5.7.1, “Notification/ E-mail, Event Log”.)
SystemMonitorEvent ESMCOMMONSERVICE[0XC0000066]
ESMCOMMONSERVICE[0XC0000070] * Standard
Policy
ESMCOMMONSERVICE[0XC0000064] (Server
ESMCOMMONSERVICE[0XC000093E] shutdown /
ESMCOMMONSERVICE[0XC0000072] Move all
VMs on the
Predictive OobManagement [PET] 0x00090B05 VM server)
alert : power for VM
unit failure SystemMonitorEvent ESMCOMMONSERVICE[0XC0000915]
Server ESXi
Predictive OobManagement [PET] 0x00020102
alert : voltage [PET] 0x00020104
failure
[PET] 0x00020109
[PET] 0x0002010B
[PET] 0x00020703
SystemMonitorEvent ESMCOMMONSERVICE[0XC00001FD]
ESMCOMMONSERVICE[0XC00001FF]
ESMCOMMONSERVICE[0XC0000203]
ESMCOMMONSERVICE[0XC0000205]
ESMCOMMONSERVICE[0XC0000932]
Predictive OobManagement [PET] 0x000A0102
alert : FAN / [PET] 0x000A0104
Cooling device
failure [PET] 0x000A0109
[PET] 0x000A010B
[PET] 0x00040102
[PET] 0x00040104
[PET] 0x00040109
[PET] 0x0004010B
[PET] 0x00040301
SystemMonitorEvent ESMCOMMONSERVICE[0XC00000D0]
ESMCOMMONSERVICE[0XC00000D2]
ESMCOMMONSERVICE[0XC00000D6]
ESMCOMMONSERVICE[0XC00000D8]
ESMCOMMONSERVICE[0XC00000C8]
Predictive OobManagement [PET] 0x000A0702
alert : Coolant
leak SystemMonitorEvent ESMCOMMONSERVICE[0XC0000A8C]
SystemMonitorEvent ESMCOMMONSERVICE[0X800001FE]
ESMCOMMONSERVICE[0X80000204]
ESMCOMMONSERVICE[0X40000BAD]
Clear alert : OobManagement [PET] 0x800A0102 no action
FAN / Cooling [PET] 0x800A0109
device failure
recovery [PET] 0x000A0700
[PET] 0x80040102
[PET] 0x80040109
[PET] 0x80040301
SystemMonitorEvent ESMCOMMONSERVICE[0X800000D1]
ESMCOMMONSERVICE[0X800000D7]
ESMCOMMONSERVICE[0X400002C3]
ESMCOMMONSERVICE[0X400000CD]
* Suppression events of the Policy Property setting window cannot be set on the
above events.
Action settings that Event Handler Settings Name are “Diagnose the Sensor / Set
Faulted Status” are as follows:
Action settings that Event Handler Settings Name are “Move all running VMs on the VM
server” are as follows:
Action settings that Event Handler Settings Name are “Move all running VMs / Server
shutdown” are as follows:
(Standard Policy (Server shutdown / Move all VMs on the VM server) for VM Server
ESXi.)
Note: If you are using a Xen environment, make sure to configure the recovery
actions of HW Predictive alert events without the Action for machine / Shutdown
machine. (It is selected by default.) If it is configured with the Action for machine /
Shutdown machine, Pool Master will shut down in the recovery actions and you
might not access the Xen environment. Execute shutdown of XenServer in HW
Predictive alert events manually as necessary.
Note:
▪ To detect OOB Management events, see Section 2.15, “Preparing for the Use of
Out-of-Band (OOB) Management” in SigmaSystemCenter Configuration Guide and
perform the procedures from Subsection 2.15.1, “Configuring IP Address of BMC” to
Subsection 2.15.5, “Checking the Setting of Firewall”. However, OOB Management
events cannot be detected from a managed machine where NEC ESMPRO Agent is
working.
▪ If you are using ESX (Linux), disable the shutdown function of a machine to be
monitored during an error occurrence, referring to Subsection 3.2.2, "Other Setting" in
NEC ESMPRO Agent (for Linux) User's Guide to use events of SystemMonitorEvent.
▪ If you are using Hyper-V (Windows), disable the shutdown function of a machine to
be monitored during the error occurrence by performing the following procedure:
1. From Control Panel, double-click NEC ESMPRO Agent. Click the General tab and
Report Setting on the NEC ESMPRO Agent Properties dialog box to activate the
Alert Manager.
2. Select Base Setting, located on the setting menu on the Alert Manager.
3. Click the Function valid/invalid status on the setting of the time until shutdown,
located on the Other tab to change from green to red.
Note:
▪ Policy actions for moving a single virtual machine are abolished with
SigmaSystemCenter 2.0. In substitution, policy actions for Power save Virtual Machine
server and Load balance Virtual Machine Server are added,
If you were using the abolished policy actions before upgrading SigmaSystemCenter,
the policy actions are converted to No action.
▪ You need to note the point below for the actions:
Action for Group / Delete a machine from the group to pool
Action for Group / Delete a virtual machine from the group
Action for Group / Suspend a machine in the group
Action for Group / Shutdown a machine in the group
Action for machine / Shutdown machine
Action for machine / Investigate and Power OFF
• This action is not executed if there is only one machine that is running in not
faulted status, but powered ON status, left in a target group.
However, if multiple actions, such as "Delete a machine from the group,"
"Shutdown a machine in the group," or "Suspend a machine in the group," are
set to an event, all running machines can vanish.
For example, when you are running two machines in a group, if an event to
which two "Delete a machine from the group" is set is generated, the
execution is not suppressed since there are two machines, but the machines
are deleted by the action.
Registering an event to the event logs and E-mail notification are commanded at the
timing of event detection, starting an action, or completing an action.
For details of setting E-mail destination address or other settings, see Subsection
2.13.2, "Notification Tab" in SigmaSystemCenter Web Console Reference Guide.
You cannot set E-mail notification and event log registration to each policy and event.
This action can be executed in parallel with other operations on the same machine.
Note:
▪ You are notified by SystemPolicy (Manager) only when receiving an event.
▪ Contents of notification by SystemPolicy (Manager) is defined in the following file,
stored in the SystemProvisioning installation folder:
SystemProvisioning installation folder\conf\PvmCustom.xml
Additionally, this action does not change hardware status and ends abnormally if any
sensors have no problems. If the next action’s execution condition is ”Success”, the
next action will not be executed.
Sensors are displayed in the Sensor tab. To display the Sensor tab, click the Resource,
the Machine icon, and the IPMI information on Configuration menu. Then, click the
Sensor on the IPMI Information screen. If a sensor’s Exclude from sensor diagnosis
check box is not selected, the sensor is a target of the sensor analysis. For details, see
Subsection 3.12.2, "Sensor tab" in SigmaSystemCenter Web Console Reference
Guide.
Note:
▪ To use this function correctly, see Subsection 5.5.2, "Analysis of HW Sensor
Conditions."
▪ You can see the detected sensor alerts at the Sensor tab, which is displayed by
clicking Resource - Machine icon - IPMI Information - Sensor. However, sensors with
problems might not be detected in the following cases:
▪ You collected sensor information after finishing the sensor analysis.
▪ You clicked the Refresh on the Sensor tab after finishing the sensor analysis.
▪ During the sensor analysis, “Faulted” status was set because the sensor could not
be read or BMC did not respond.
In the above cases, you cannot see the sensor alerts at the Sensor tab but you can see
logs of the sensor analysis at the Job List and the Event List instead. The Job List and
the Event List appear on the Main Window by clicking the Job on the Monitor view.
At the Job List, you can see the details of a job of sensor analysis by clicking an event
number link of the job. Also you can see it at the Event List in the same way.
First, this action diagnoses whether SystemProvisioning can recover the failed
machine or not by the investigation function in detail. If the failed machine is a virtual
machine server (VMware or XenServer), SystemProvisioning executes the function.
By the result of diagnosis, if SystemProvisioning judges that the machine does not
need the recovery process or that SystemProvisioning should not execute the recovery
process at the timing because of the circumstances, the process ends with an error. If
SystemProvisioning judges that there is a possibility of recovery of the machine,
SystemProvisioning starts the Power OFF process of the failed machine to recover the
machine.
Reference: For the details of the investigation function, see Section 5.5, "Investigation
Function."
Operations are not executed to virtual machines to which the Optimized Placement
Rule is not set.
5.7.22. Action for VMS / Move all running VMs on the VM server.
(Failover)
Moves a virtual machine running on a target virtual machine server to other virtual
machine server.
As the moving method, Failover is used.
This action is only valid for events detected on virtual machine servers.
In addition, if the target virtual machine server is Pool Master of XenServer and the
machine is stopped, SystemProvisioning executes the process of switching Pool
Master with other virtual machine server.
5.7.23. Action for VMS / Move all running VMs on the VM server.
(Hot Migration)
Moves a virtual machine running on a target virtual machine server to other virtual
machine server.
As the moving method, Hot Migration is used.
This action is only valid for events detected on virtual machine servers.
In addition, if the target virtual machine server is Pool Master of XenServer and the
machine is stopped, SystemProvisioning executes the process of switching Pool
Master with other virtual machine server.
5.7.24. Action for VMS / Move all running VMs on the VM server.
(Hot Migration, Failover)
Moves a virtual machine running on a target virtual machine server to other virtual
machine server.
As the moving method, Hot Migration is used. If Hot Migration fails, Failover is used.
This action is only valid for events detected on virtual machine servers.
In addition, if the target virtual machine server is Pool Master of XenServer and the
machine is stopped, SystemProvisioning executes the process of switching Pool
Master with other virtual machine server.
5.7.25. Action for VMS / Move all VMs on the VM server. (Failover)
Moves all virtual machines on a target virtual machine server to other virtual machine
server.
As the moving method, Failover is used.
This action is only valid for events detected on virtual machine servers.
In addition, if the target virtual machine server is Pool Master of XenServer and the
machine is stopped, SystemProvisioning executes the process of switching Pool
Master with other virtual machine server.
5.7.26. Action for VMS / Move all VMs on the VM server. (Hot
Migration / Cold Migration)
Moves all virtual machines on a target virtual machine server to other virtual machine
server.
As the moving method, Hot Migration or Cold Migration is used.
This action is only valid for events detected on virtual machine servers.
In addition, if the target virtual machine server is Pool Master of XenServer and the
machine is stopped, SystemProvisioning executes the process of switching Pool
Master with other virtual machine server.
5.7.27. Action for VMS / Move all VMs on the VM server. (Hot
Migration / Cold Migration, Failover)
Moves all virtual machines on a target virtual machine server to other virtual machine
server.
As the moving method, Hot Migration or Cold Migration is used. If Hot Migration or Cold
Migration fails, Failover is used.
This action is only valid for events detected on virtual machine servers.
In addition, if the target virtual machine server is Pool Master of XenServer and the
machine is stopped, SystemProvisioning executes the process of switching Pool
Master with other virtual machine server.
Operations are not executed to virtual machines to which the Optimized Placement
Rule is not set.
For how to check action parameters name to set, see Section 3.20, "Base Information
of Software" in SigmaSystemCenter Web Console Reference Guide.
A local script that you actually want to execute with this action can be specified on the
Action Parameter Settings window. For how to set the setting, see Subsection 3.9.6,
"Configuring Event Handler Settings of a Policy Monitoring Event" in
SigmaSystemCenter Configuration Guide.
If you changed the local script name itself, specify its parameter (script file name) on
the Action Parameter Settings window again.
367
6 Caution Notes
If you execute 101 or more scenarios with the settings, restart the managed machine.
By restarting the machine, you can execute another 100 scenarios.
For the details of the alert settings, see Section 2.6, "Configuring the Setting for
Sending Failure Events From the Managed Machine" in SigmaSystemCenter
Configuration Guide.
Failed to create a parameter file Linux while executing the scenario (software
name) for the server (host name).
For how to create a parameter file, see Chapter 1, "OS Installation by Disk Duplication"
in DeploymentManager Basic User’s Guide.
Reference:
▪ For the operational environment, see Section 3.4, "Manageable Virtual Machine
Infrastructure" in SigmaSystemCenter First Step Guide.
▪ For the system configuration, see Subsection 2.1.4, "Example of System
Configuration and Caution" in SigmaSystemCenter First Step Guide.
When creating a new virtual machine, the system attempts to acquire the IP
address automatically before configuring the static IP address on the Windows OS.
If an IP address cannot be acquired from the DHCP server, the IP address setting
process may take another several tens of seconds to several minutes.
If you make a virtual machine participate in a domain, you need to configure DNS
setting. (In the Xen and Hyper-V environment, configure DNS setting to master VM
in advance). If you make a virtual machine which is already participating in domain
participate in domain by executing Allocate Machine, take the virtual machine out
of domain first and execute Allocate Machine. If not, the virtual machine may not
work properly.
For VMware
vCenter Server uses the default TCP/IP ports of "80" and "433".
Port conflict might occur depending on your environments. If it occurs, the default
values of the ports must be changed so that the port conflict will not occur.
Change the http port of vCenter Server from “80” to other ports such as
“10080”.
• When coexisting with DPM
The default ports of vCenter Server might conflict with the port that is used by
Apache Tomcat.
You need to change the port of Web Server for DPM. For instructions on how to
change the port, see in ""Apache Tomcat" does not start" in Section 17, "Web
Console" in DeploymentManager Advanced User’s Guide.
For Xen
XenServer Pool Master uses the default TCP/IP ports of "80" and "433."
For Hyper-V
For VMware
Key: HKEY_LOCAL_MACHINE\Software\NEC\PVM\Provider\VM\VMware
Value (Type): EnableIPSetting(RED_DWORD)
Default Value: 1 *
* If zero is set as the value or the value does not configured, a machine is
registered with its host name. If any number other than zero is specified, a
machine is registered with its IP address.
You can set Domain Suffix in the Domain Suffix box on the OS Setting tab of the
Group Property window. Do not specify "." as an initial letter.
• Administrator password
If you are using VMware, clear the manager password of the master VM
before creating a template.
If the password is not cleared, the password configured after creating the
virtual machine is not configured as a specified password. The password
configured to the master VM remains unchanged.
• SCSI controller
When creating Differential Clone type virtual machines using vCenter Server
4.0 Update 1 or before, LsiLogic SAS cannot be used for SCSI controller of a
master VM.
• Disk
Create only one disk for a master VM as the system disk.
If you are creating a system disk and an extended disk (data disk) at the same
time when creating a virtual machine and are using both of them in operations,
do not add the extended disk to a template (the source master VM to be
copied) and configure the template with only one system disk.
About VM Console
• This function supports only VMware.
• The version of MouseKeyboardScreen plugin that this function supports is
only 2.1.0.0.
• This function does not support Firefox3.
• This function does not monitor status change of the console, such as
connection status change or resolution modification.
• MouseKeyboardScreen plugin is not installed automatically. Install it
manually.
• If you execute the power operations of a virtual machine or move a virtual
machine, the VM Console is disconnected.
• To exit from the full screen mode of the VM Console, press Ctrl+Alt. If you exit
the full screen mode otherwise, the resolution of the management server
monitor can be changed.
For Xen
For Hyper-V
* If you configure a value other than 1 or do not configure any values, group names
that are configured on SystemProvisioning will be registered without change.
Be sure to follow the rules below. If you do not follow the rules, the registration
process to DPM of the virtual machine may fail.
If you are using Xen, when creating a new virtual machine from a Disk Clone
template, if you configure more NICs than the number of NICs registered in the
template, the setting is ignored.
For VMware
Do not register vCenter Server as a subsystem with both IP address and host
name.
For Xen
Do not register XenServer as a subsystem with both IP address and host name.
For Hyper-V
When registering a Hyper-V Cluster, all the nodes of the cluster must be up and
running.
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Value (Type): ServicesPipeTimeout (DWORD)
Default value: 30000 (millisecond)
and the machine startup might fail because of this value setting. Therefore, we
recommend changing this registry value of the master VM.
For VMware
For Xen
configured from the Web Console are not reflected, configure an IP address to a
virtual machine manually.
For Hyper-V
For VMware
For Xen
For Hyper-V
If the template is a Full Clone template, you do not need to re-create the template.
For more details of the function when you select the VM Server is selected
automatically, see Subsection 1.10.8, "Activating Machine / Create and Assign
Machine (Virtual Machine)."
About account
A template account is succeeded to virtual machines.
Delete unnecessary master VM accounts before creating templates.
In addition, if you are using Windows Vista, the Administrator account is invalid.
Do not delete all accounts that have administrator rights.
For VMware
• When you execute Create and Assign machine, and when you make a virtual
machine to participate in a domain, if the NIC number is only one, you may not
be able to execute the operation. If you do, add two or more NICs to the virtual
machine.
About Create and Assign Machine for a virtual machine using a HW Profile Clone
template
When executing Create and Assign Machine on a standalone ESXi, if there is a
virtual machine that is used as a source image of a HW Profile Clone template on
the shared disk, and the virtual machine is ON, Create and Assign Machine fails.
For VMware
About Failover
During Failover of a VMware virtual machine, if an original ESX is recovered, the
virtual machine may be returned to the original virtual machine server. In this case,
the virtual machine information in SystemProvisioning and the virtual machine
information in vCenter Server become inconsistent; however, you can make the
information consistent by executing the power operation to the target virtual
machine from SystemProvisioning.
Key: HKEY_LOCAL_MACHINE\SOFTWARE\NEC\PVM\Provider\VM\VMware
Value (Type): EnableIndependentDiskMode (DWORD)
Value: 1
For Xen
You cannot execute Allocate Resource to Xen virtual machines. To start a Xen
virtual machine, execute Register Master Machine or Create and Assign Machine.
For Hyper-V
For VMware
When ESXi is restored from failure, if failover of virtual machines is executed, the
moved virtual machines are registered to multiple ESXi redundantly.
With the following procedure, you can organize the virtual machines:
Prerequisites
1. An account and password of the ESXi is set
2. ESXi to restore is running
3. ESXi to restore is connected to ESXi in the same datacenter
Notes
• If ESXi in the same datacenter with the ESXi to restore is in the following
conditions, the ESXi becomes out of target:
- The Connection status is Disconnected
- If the ESXi cannot be connected due to some defect, such as network
failure
• If there is ESXi that becomes out of target or if the restore process fails,
execute the restore process again or delete virtual machine registered
redundantly from vSphere Client.
For Xen
• Start all XenServers in a Pool once when current XenServer Pool Master is
running. If not, the XenServer Pool Master may not cognize startup of its
Slave.
• To execute restore operations to old XenServer Pool Master after XenServer
Pool Master is switched, ensure to execute the operations when current
XenServer Pool Master is running. In addition, after the restore operations,
ensure to restart the restored machine when the current XenServer Pool
Master is running. After the restart, the old XenServer Pool Master is used as
a Slave.
• To shut down XenServer Pool Master after XenServer Pool Master are
switched, start all XenServers in a Pool once and then, shut down the
machine.
About virtual machines that are being started up when a failure occurs on
XenServer Pool Master
Virtual machines that are being started up when a failure occurs on XenServer
Pool Master may not be completed to start up. In that case, abort the virtual
SigmaSystemCenter 2.1 Reference Guide
394
Virtual Environment Management Function
machines once from XenCenter and then, start the virtual machines again.
About virtual machines that are being created when a failure occurs on XenServer
Pool Master
Virtual machines that are being created when a failure occurs on XenServer Pool
Master will not be created. In addition, unused disks may remain in storage. If you
cannot delete the disks from XenCenter when you wish to delete them, perform the
following procedure:
• If an error occurs when deleting the disks, try to delete them again after
restarting the current Master.
• If you cannot delete the disks although no error occurs, run sr-forget of the xe
command.
For VMware
In this case, execute the operations for the virtual machine again.
For Hyper-V
About the issue that some heart beat services do not start if a lot of virtual
machines are started
Restart virtual machines where errors occurred individually, or, start the heart beat
services in the virtual machines.
Creation of virtual machines and configuring RDM cannot be executed at the same
time on SigmaSystemCenter
Create a template of a virtual machine where RDM is not configured and duplicate
the template. After that, configure RDM on each of virtual machines using vSphere
Client.
Note: If you create a template of a virtual machine that is used as RDM and
duplicate the template, RDM will be released. Data on RDM will be copied and will
be created as a virtual disk on Datastore.
If virtual machines cannot be operated from the Operation view, perform the
following procedure to recover.
For VMware
For Xen
For Hyper-V
How to deal with a virtual machine that remains even after deleted
If you delete a virtual machine on Hyper-V Manager, the virtual machine might
remain on SigmaSystemCenter. In that case, start up all virtual machine servers
and execute Collect operation on the Manager right under the Virtual view. (Select
the manager by clicking "Hyper-V" for Hyper-V single server or the corresponding
cluster name for Hyper-V Cluster environment.) In a cluster environment, make
sure that there are no virtual machines with offline VM configuration on cluster
before executing Collect operation.
If you are using Fastlron Edge series switches of Foundry Networks products:
If port assignment to VLAN fails while executing the Allocate Machine
If releasing port-VLAN assignment fails while executing the Release Resource
If port assignment to VLAN fails while editing VLAN
If releasing port-VLAN assignment fails while editing VLAN
If you are using switches other than Fastlron Edge series switches of Foundry
Networks products:
If port assignment to VLAN fails while executing the Allocate Machine
If releasing port-VLAN assignment fails while executing the Release Resource
If port assignment to VLAN fails while editing VLAN
If releasing port-VLAN assignment fails while editing VLAN
[If you are using Fastlron Edge series switches of Foundry Networks products]
Note: When connecting to a switch using telnet, see manuals of your switch.
1. Check operations logs for a failure factor and remove the failure factor.
2. Login to the switch via telnet.
3. Run show running-config command to verify condition of the VLAN.
4. Verify the VLAN that is configured on the VLAN setting, located on the Group
Property Setting on the Operation view and the port assignment that is
configured on the Network tab, located on the Machine Property Setting on
the Resource view. Compare the condition of the VLAN to that of VLAN
displayed on telnet.
E.g.)
If the settings are configured as follows:
- VLAN that is configured on the VAN setting tab on the Group Property
Setting
VLAN ID 10 / NIC: 2
- The port that is configured on the Network tab on the Machine Property
Setting
NIC: 2 / Port 3
- Condition of the VLAN that is configured on the device
Port 4 is assigned to the VLAN10.
Delete VLAN10 on the device, and then, re-create VLAN10. Assign Port 3 to
VLAN10.
* If Port 4 is assigned to other machines, Port 4 must be assigned to VLAN10
with other machines.
5. Execute the Release Resource from the Host List, located on the details of
the operation group.
6. Execute the Allocate Machine again from the Host List, located on the details
of the operation group.
1. Check operations logs for a failure factor and remove the failure factor.
2. Login to the switch via telnet.
3. Run show running-config command to verify condition of the VLAN.
4. Verify the VLAN that is configured on the VLAN setting, located on the Group
Property Setting on the Operation view and the port assignment that is
configured on the Network tab, located on the machine property setting on
the Resource view. Compare the condition of the VLAN to that of VLAN
displayed on telnet.
E.g.)
If the settings are configured as follows:
- VLAN that is configured on the VAN setting tab on the Group Property
Setting
VLAN ID 10 / NIC: 2
- The port that is configured on the Network tab on the Machine Property
Setting
NIC: 2 / Port 3
- Condition of VLAN that is configured on the device
Port 4 is assigned to the VLAN10.
Delete VLAN10 on the device, and then, re-create VLAN10. Assign Port 3 to
VLAN10.
5. Execute the Release Resource from the Host List, located on the details of
the operation group.
1. Check operations logs for a failure factor and remove the failure factor.
2. Login to the switch via telnet.
3. Run show running-config command to verify condition of the VLAN.
4. Verify the VLAN that is configured on the VLAN setting, located on the Group
Property Setting on the Operation view and the port assignment that is
configured on the Network tab, located on the Machine Property Setting on
the Resource view. Compare the condition of the VLAN to that of VLAN
displayed on telnet.
E.g.)
If the settings are configured as follows:
- VLAN List located on the details of the switch:
No port is assigned to VLAN10
- Condition of VLAN that is configured on the device:
Port 4 is assigned to the VLAN10.
Delete VLAN10 on the device, and then, re-create VLAN10. Assign Port 3 to
VLAN10.
* If Port 4 is assigned to other machines, Port 4 must be assigned to VLAN10
with other machines.
Part III Maintenance Information
403
6 Caution Notes
5. Execute the Release Resource from the Host List, located on the details of
the operation group.
1. Check operations logs for a failure factor and remove the failure factor.
2. Login to the switch via telnet.
3. Run show running-config command to verify condition of the VLAN.
4. Verify the VLAN that is configured on the VLAN setting, located on the Group
Property Setting on the Operation view and the port assignment that is
configured on the Network tab, located on the Machine Property Setting on
the Resource view. Compare the condition of the VLAN to that of VLAN
displayed on telnet.
E.g.)
If the settings are configured as follows:
- VLAN List located on the details of the switch:
Port 3 is assigned to VLAN10.
- Condition of VLAN that is configured on the device:
Port 4 is assigned to the VLAN10.
Delete VLAN10 on the device, and then, re-create VLAN10. Assign Port 3 to
VLAN10.
* If Port 4 is assigned to other machines, Port 4 must be assigned to VLAN10
with other machines.
SigmaSystemCenter 2.1 Reference Guide
404
Notes on Operating MasterScope Network Manager
5. Execute the Release Resource from the Host List, located on the details of
the operation group.
[If you are using switches other than Fastlron Edge series switches of Foundry
Networks products]
Situation Procedure
Fails to add a load balancer when activating a 1. Check a failure factor in operations logs and
standby machine remove it.
2. Execute the Release Resource.
3. Execute the Allocate Machine.
Part III Maintenance Information
405
6 Caution Notes
Fails to delete a load balancer when making a 1. Check a failure factor in operations logs and
started machine standby remove it.
2. Execute the Release Resource.
For example, the ports 17, 18 of a SIGMABLADE GbE intelligent switch are the inter
link ports to connect with the neighboring slots and they are Trunk configuration by
default. Therefore, SigmaSystemCenter cannot execute the VLAN control on the ports.
This chapter explains how to cope with errors occurred when configuring or operating
SigmaSystemCenter.
407
7 Trouble Shooting
[Cause]
The process of Internet Information Services (IIS) misidentifies references from
multiple browsers as a connection from one browser, so the information becomes
inconsistent, and the system displays the message,
[Solution]
Click main menu, such as Operation, on the Web Console to switch the view, update
the screen, and then, execute the operation again.
[Solution]
Execute one of the following:
If the process of activating the machine in a group failed: Delete the machine from
the group once, and remove the cause of the error, and then, execute the
operation of activating in the group again.
If the process of making the machine stand by failed: After removing the cause of
the error, execute the operation for making the machine stand by again.
If the machine status does not return to the status before the execution, you need to
specify the related matters, referring to the Event logs and Operation logs. Check the
setting for the GUI or device and the Hardware status again.
[Solution]
Update the machine using a program, such as Windows Update, or release the PSSU
manually. To release the PSSU, log on to the machine and close the security update
screen.
[Solution]
Delete one machine of the machines registered doubly from SigmaSystemCenter, and
after confirming that the UUID and MAC Address are registered to the other machine,
execute Collect to collect information from each subsystem again.
1. Decide which machine to delete from the machines, checking the registration
status of the NIC and UUID and other information configured to the machines.
2. If the machine is registered as a management target of SigmaSystemCenter,
delete the registration and set the machine to unmanaged.
3. Delete the registration of the machine in each subsystem.
• If the type of the machine is Blade or Unitary: Delete the machine from DPM.
• If the type of the machine is VM Server or Virtual Machine: Delete the
Inventory of the machine from vCenter Server.
4. Execute Collect in SigmaSystemCenter.
Make sure to confirm that the machine is deleted from SigmaSystemCenter after
the Collect process completed.
5. Register a MAC Address that can be recognized by subsystems from which you
deleted the machine in Procedure 3 to the machine that you did not delete. If the
subsystems do not recognize the MAC Address, make DPM recognize the UUID of
the machine, register the machine, and then, execute Collect to DPM to register
the UUID to the machine.
6. Re-register the machine to all the subsystems from which you deleted the machine
in Procedure 3.
7. Execute Collect in SigmaSystemCenter.
[Cause]
The machine can be registered doubly.
[Solution]
Check the UUID or Mac Address of the machine not to be registered to other machine.
If the UUID or Mac Address is registered doubly, execute the solution in Subsection
7.2.4, "A NIC or UUID of One Machine Is Registered as Multiple Machines by the
Collect Function."
[Cause]
If you disconnect the network after the connection to Web Server for DPM is
established, the process request to DPM waits for a timeout for five minutes.
In this situation, if you stop the PVMService from the Services Snap-In, the stopping
process is set to wait, and the message for a timeout appears.
[Solution]
After the message is displayed, wait for completing the stopping process of the
PVMService. You can check the completion by updating the Services Snap-In.
[Solution]
Log in to SigmaSystemCenter again, and execute the operation.
If the phenomenon continues, the following causes can be considered. Remove the
cause, referring to the following items.
Recycle of a worker process or the configured time for the memory recycle has
passed in the Worker Process Isolation mode of IIS 6.0.
The asax file or config file is a target of the virus scan in anti-virus software.
Available memory is insufficient in the system.
[Cause]
A machine that is running out of SystemProvisioning management is started due to
operation misses or a power management product.
[Solution]
Solutions differ depending on your environment is Windows or Linux. Configure the
function according to the environment.
Note:
▪ Do not execute this operation on managed machines when executing SetDHCP.
▪ You may not use this function, depending on the environment of applications
because it may cause changes of the host name and IP address.
▪ By default, the following registry is configured, SystemProvisioning checks if
there is a scenario in DPM when moving an active machine to a pool. If there is a
scenario, SystemProvisioning executes this function automatically, regardless of
the software setting of the machine, Host Setting, model, and group. Delete the
following registry to not execute the SetDHCP scenario automatically.
Key: HKEY_LOCAL_MACHINE\Software\NEC\PVM\ActionSequence\Scenario
Name: HaltScenario
Type: Character string type
Value: SetDHCP
1. Registering the application for the function of changing a host name and IP
address
Configure this setting in DPM.
2. Creating a scenario for the function of changing a host name and IP address
1. Start the DPM Web Console, and change the access mode to the Update
Mode.
2. From the Scenarios menu, click Create Scenario File to display the Create
Scenario File window,
3. Click the Application tab, and enter and select items as follows:
Application Name list: Local-SetDHCP that you created in Procedure 1
Transmit data using unicast check box: On
Scenario Name box: SetDHCP
4. Click OK, and click Finish.
3. Configuring the scenario for the function of changing a host name and IP
address
Note: Make sure to configure the line break code for Linux (<LF>) in the script
file. If not, the created file may not work properly.
2. Creating a scenario for the function of changing a host name and IP address
1. Start the DPM Web Console, and change the access mode to the Update
Mode.
2. From the Scenarios menu, click Create Scenario File to display the Create
Scenario File window,
3. Click the Application tab, and enter and select items as follows:
Application Name list: Local-SetDHCP that you created in Procedure 1
Transmit data using unicast check box: On
Scenario Name box: SetDHCP
4. Click the Option tab, and select the Turn off power after execution check
box.
5. Click OK, and click Finish.
3. Configuring the scenario for the function of changing a host name and IP
address
[Cause]
The database can be updated with wrong information because the information is
collected in SigmaSystemCenter when the device information is inconsistent.
[Solution]
Make the device information consistent with the following procedure:
[Solution]
You need to change the ports that Tomcat of DPM use. For the procedure, see
""Apache Tomcat" does not start" in Chapter 17, "Web Console" in
DeploymentManager Advanced User’s Guide.
[Cause]
If the machine is in one of the following conditions, the machine is not shut down.
Locked by the WorkStation Lock
Locked by a screen saver with a password
Connected from Remote Desktop, Terminal Service, or other remote connection
software
If there is an editing data or application that does not reply to a shut down request
[Solution]
Release the above lock status and execute shutdown again.
[Cause]
When you registered Management Server for DPM to the DPM Web Console again
after upgrading, you registered a registration name of Management Server for DPM
that differs from what you had registered before upgrading by case, and the system
recognized that there are two Management Server for DPM.
[Solution]
Delete the Management Server for DPM that you registered after the upgrade from the
DPM Web Console once, and register the Management Server for DPM again with the
same name that you had registered before the upgrade again, and then, execute
Collect.
[Cause]
The operation of creating a virtual machine waits for a host name and IP address to be
reflected to the virtual machine. This action varies according to a type of guest OS of
the virtual machine to create or load condition of a management server; therefore, this
timeout may occur.
[Solution]
If waiting for setting a host name times out, create the following registry with a value
specified in seconds:
If waiting for setting IP address times out, create the following registry with a value
specified in seconds:
[Cause]
In the operation of creating a template, the time that is required to complete the process
of cloning a virtual machine varies according to disk size of a source virtual machine
and load condition of VMware ESX; therefore, waiting for cloning completion may time
out.
[Solution]
Change the following registry with a value specified in seconds:
[Cause]
There is a possibility that XenServer Pool Master has switched and a Slave may not
cognize the current XenServer Pool Master.
[Solution]
Run the following xe command on the Console of the current XenServer Pool Master:
xe pool-recover-slaves
For the details of the xe command, see the product manuals of Citrix Systems, Inc.
[Cause]
Ensure to start all servers in a Pool every time XenServer Pool Master is switched. In
addition, restore old XenServer Pool Master when current XenServer Pool Master is
started. If not, XenServer Pool Master may be switched automatically.
[Solution]
Execute the following steps:
1. Start all servers in a Pool.
2. Run the following xe command on the Console of current XenServer Pool Master:
xe pool-recover-slaves
For the details of the xe command, see the product manuals of Citrix Systems, Inc.
3. Edit XenServer Pool Master on the subsystem window of SigmaSystemCenter to
change the address of XenServer Pool Master to that of current XenServer Pool
Master.
[Cause]
In the vCenter Server environment, even if VMware ESX is down, vCenter Server may
cognize that the ESX is in the normal state. This is why vCenter Server disconnects the
VMware ESX before the move operation is executed.
[Solution]
Execute the following steps to the disconnected ESX:
1. Click Virtual on the Title bar to switch to the Virtual view.
2. Select the icon of the target ESX in the Virtual tree and click Reconnect.
[Cause 2]
If Move fails in the VMware environment, there is a possibility of shortage of free disk
capacity of a destination virtual machine server.
[Solution 2]
Check the disk capacity of the destination virtual machine server.
[Cause 3]
If Hot Migrate fails in the VMware environment, setting of VMotion for virtual machine
servers may not be enabled in vCenter Server.
[Solution 3]
Check the setting of VMotion for virtual machine servers (VMotion Enabled). For the
details, see the product manuals of VMware Inc.
[Cause 4]
If you are using the VMware environment, virtual machine servers may be in the
configuration where virtual machines cannot be moved.
[Solution 4]
Check the configuration of your virtual machine server, including HW, datacenter
configuration, pool configuration, and license.
For the details, see the product manuals of VMware, Inc.
[Solution]
If Datastore is on the local disk, you need to back up or restore the Datastore. If the
template is on the shared disk, such as SAN or NFS, restore the template with the
following steps:
1. Delete the failed ESX in vCenter Server Client.
2. Register a template with the same name as before to the Datastore browser of
other ESX.
[Cause]
A virtual machine server where an error occurred does not recognize that virtual
machines that were running on the virtual management server have moved to another
virtual machine server.
[Solution]
Update information of the virtual machine server where an error occurred, referring to
Subsection 7.6.3, "Operations After Failing Over in the Standalone ESXi Environment"
in SigmaSystemCenter Configuration Guide.
[Solution]
Execute the following operations on unusable templates.
[Cause]
SNMP Trap Service is disabled in a management server where SigmaSystemCenter is
installed. Or, SNMP Trap Service is not installed on the management server.
[Solution]
1. If SNMP Trap Service is not installed, install SNMP referring to "1. Install the
Simple Network Management Protocol (SNMP)" in Subsection 2.15.4, "Enabling
PET reception on a Management Server" in SigmaSystemCenter Configuration
Guide.
2. Click the Start menu and click Control Panel(C) - Administrative Tools -
Service to display the Service dialog box.
3. Double click on the SNMP Trap Service to display the SNMP Trap Service
Properties dialog box.
SigmaSystemCenter 2.1 Reference Guide
424
Trouble Shooting in SystemProvisioning
[Cause]
SNMP Trap Service might have stopped while the PVMService was starting.
[Solution]
1. Click the Start menu and click Control Panel(C) - Administrative Tools -
Service to display the Service dialog.
2. Double click on the SNMP Trap Service to display the SNMP Trap Service
Properties dialog box.
3. Verify that the service status is Stopped.
4. Select Automatic in the Startup Type and click Start.
5. Click OK to close the SNMP Trap Service Properties dialog box.
6. Select and right-click the PVMService on the Service dialog box and select
Restart.
[Cause]
Operations and information acquisition of Out-of-Band Management might fail
because UDP is used and Packet Loss occurs.
Initializing process is executed on the target machine during power operations.
BMC might not respond depending on the timing.
[Solution]
The operations execute retry to improve reliability.
However, Packet Loss might occur depending on the network traffic owing to UDP
connection. To ensure communication quality, reconfigure the network configuration.
Separate the LAN that is used for communicating with BMC from the LAN that is
used for other purposes physically.
Design the network configuration so that the number of network switches between
managed machines and SigmaSystemCenter management server can be
reduced.
Do not execute Packet Forwarding in internal network switches.
If BMC does not respond because of initializing process of the system, retry the
operation after a while.
[Solution]
Connect to XenServer Pool Master using XenCenter and release Maintenance Mode of
the target virtual management server. For detailed procedure to release Maintenance
Mode of Xen products, see product manuals of Citrix Systems, Inc.
[Cause]
A disk of a virtual machine that was previously used might remain on Datastore.
[Solution]
After verifying that the machine is not registered as a virtual machine, delete the disk of
the virtual machine from Datastore browser of vSphere Client or on ESXi.
[Solution]
Verify that the replica VM is powered Off before performing this procedure.
When above command is executed from the Server Console of XenCenter, UUID
of a replica VM is displayed.
xe template-list name-label=:Frozen-Replica
snapshot_of="UUID of the replica VM obtained in Procedure
1"
When the above command is executed from the Server Console of XenCenter, a
snapshot (Frozen-Replica) of the replica VM is displayed.
When the above command is executed from the Server Console of XenCenter,
UUID (vdi-uuid) of the disk of the replica VM is displayed.
When the above command is executed from the Server Console of XenCenter,
UUID of the disk that is copied from the snapshot (Frozen-Replica) is displayed.
Note: Be sure to take notes of the UUID that is displayed here because the UUID
is difficult to be checked later.
When the above command is executed from the Server Console of XenCenter, the
disk that is created is connected to the replica VM.
7. Verify that the disk that is connected in Procedure 6 is configured on the replica
VM.
Select the Storage tab of the replica VM from XenCenter. Verify that the disk is
configured on the Device Position "0".
[Cause1]
The service of the configuration database can be stopped.
[Solution1]
Use Service, the management tool of Windows, to check that the service that
corresponds to the instance name of the database that is used for the configuration
management data is in operation. If you have not transferred the database after
installing SystemProvisioning, the service name of the management server is
"MSSQL$SSCCMDB."
Restart SystemProvisioning after starting the service.
[Cause2]
The information of the connection to the configuration database can be changed.
[Solution2]
Check the connection information on the Configuration information management dialog
box.
Check that the items displayed on the dialog box, including the machine name,
instance name, authentication mode, account name, password, are correct.
For the details of the Configuration information management dialog box, see Section
7.1, "Configuration Information Management Dialog Box" in SigmaSystemCenter Web
Console Reference Guide.
Restart SystemProvisioning after configuring the connection information.
[Cause]
If the PVM Service is started after restarting a management server, configuration
information is collected.
Right after OS is started, if collect is executed before the NEC Storage Manager
Service is started, this phenomenon occurs.
[Solution]
If the cause of the Warning is failure of collect due to the not started NEC Storage
Manager Service (if the above message is displayed on the Log), execute Collect
manually after starting the NEC Storage Manager Service is completed.
If it succeeds, there is no problem.
433
8 Logs
Operations Log
The operational situation of SystemProvisioning is recorded.
You can see the Operations Log on the Operations Log window in the Monitor
view.
The operations log displayed on this window is stored in the database. If the
number of logs exceeds the maximum output number, logs are deleted from the
oldest one.
In addition, you can output the logs in csv using the ssc command.
Event Log
You can check the event logs on Application on the Event Viewer.
Debug Log
SystemProvisioning outputs debug logs for failure analysis into a file. For the list of
debug logs, see Section 8.3, "List of Log Files."
Reference: For the Event logs of System Monitor - Performance Monitoring Services,
see Section 9.1, "The Event Log" in System Monitor - Performance Monitoring Services
User’s Guide.
The events in this section can be checked on Application on the Event Viewer started
by clicking the Start menu, clicking Control Panel, double-clicking Administrative Tools
from Control Panel, and double-clicking Event Viewer.
101 The PVM service started. Information The PVM Service is Nothing
started.
102 Failed to start the PVM Error An error occurred Collect a log and restart
service.(Content: Failed to when starting the the service.
start["information"]) PVM Service.
Failed to start the PVM service. "Information": A
(Content: Failed to start) module name that
failed to start.
105 Stopping the PVM operation. Error An error occurred Collect a log.
when stopping the
PVM Service.
106 Terminates the PVM service by the Information The PVM Service is Nothing
stop operation stopped by a stop
operation.
107 Product License expires in Information The product license Update the license to a
"number of remaining days" day(s). that you are using is full support version.
for evaluation and it
is going to be
expired in a week.
107 Product License has expired. Information The product license Update the license to a
for evaluation has full support version.
expired.
“EventID” : event
number
”Manager Name” :
manager name
Information” : Event
message
502 The action ("information") was Information Started an action of Nothing
started. Management the policy that
ID:"Management ID" contains
"Notification/ E-mail,
Event Log."
"Information":
Information of the
action
"Management ID":
The management
number of the action
502 The action ("information") has Information Completed an action Nothing
been completed. Management of the policy that
ID:"Management ID" contains
"Notification/ E-mail,
Event Log."
"Information":
Information of the
action
"Management ID":
The management
number of the action
501 The action ("information") was Information Failed to run an Nothing
terminated because an error action of the policy
occurred. Management that contains
ID:"Management ID" "Notification/ E-mail,
Event Log."
"Information":
Information of the
action
"Management ID":
The management
number of the action
2035 Aborted the action adding the Warning Failed to add a Activating the machine in
machine to the group. machine to a group. the group has failed.
Management ID:"Management ID" Check the cause in the
The machine which is waiting to SystemProvisioning log,
the pool of a group.("machine remove the cause, and
name") The group which works a execute the process
machine.("group name") again. If a machine with
the status displayed as
Error in the group, delete
the machine from the
group, remove the cause
of the error, and then,
register the machine to
the group again.
2036 Canceled the action adding the Information Adding a machine to Nothing
machine to the group. a group Is canceled.
Management ID:"Management ID"
The machine which is waiting to
the pool of a group.("machine
name")
2037 Started the action removing a Information Makes a machine Nothing
running machine from the group. running in a group
Management ID:"Management ID" stand by.
Machine to be running in the
group.("machine name") The
group in which the machine is
running.("group name")
Started the action deleting Information Deletes a machine Nothing
substance of the virtual machine (virtual machine)
from the group. Management running in a group
ID:"Management ID" Machine to from the group, and
delete which is running in the delete the resource.
group.("machine name") The
group in which the machine is
running.("group name")
2038 Completed the action removing a Information Completed a Nothing
running machine from the group. process of making a
Management ID:"Management ID" machine running in
Machine to be running in the a group stand by,
group.("machine name")
Completed the action deleting Information Completed a Nothing
substance of the virtual machine process of deleting
from the group. Management a machine (virtual
ID:"Management ID" machine) running in
a group from the
group and deleting
the resource.
2040 Aborted the action removing a Warning Failed to make a The process of making
running machine from the group. machine running in the machine running in a
Management ID:"Management ID" a group stand by, group stand by has
failed. Check the cause
in the
SystemProvisioning log,
remove the cause, and
execute the process
again.
Aborted the action deleting Warning Failed to delete a The process of making
substance of the virtual machine machine (virtual the machine running in a
from the group. Management machine) running in group stand by has
ID:"Management ID" a group from the failed. Check the cause
group and deleting in the
the resource. SystemProvisioning log,
remove the cause, and
execute the process
again
2041 Canceled the action removing a Information Making a machine Nothing
running machine from the group. running in a group
Management ID:"Management ID" stand by is
canceled,
Canceled the action deleting Information Deleting a machine Nothing
substance of the virtual machine (virtual machine)
from the group. Management running in a group
ID:"Management ID" from the group and
deleting the
resource is
canceled.
2042 Started the action replacing the Information Replaces a machine Nothing
specified machine to standby running in a group
machine. Management with a stand by
ID:"Management ID" Source machine.
machine.("machine name")
2043 Completed the action replacing the Information Completed Nothing
specified machine to standby replacing a machine
machine. Management running in a group
ID:"Management ID" Source with a stand by
machine.("machine name") machine.
Destination machine.(“machine
name)
2044 Aborted the action replacing the Warning Failed to replace a Replacing a machine
specified machine to standby machine running in running in a group with a
machine. Management a group with a stand stand by machine has
ID:"Management ID" Source by machine. failed. Check the cause
machine.("machine name") in the
SystemProvisioning log,
remove the cause, and
execute the process
again. If a machine with
the status displayed as
Error in the group, delete
the machine from the
group, remove the cause
of the error, and then,
register the machine to
the group again.
2045 Canceled the action replacing the Information Replacing a Nothing
specified machine to standby machine running in
machine. Management a group with a stand
ID:"Management ID" Source by machine is
machine.("machine name") canceled.
2050 Started the action changing the Information Changes a usage of Nothing
use of a machine. Management a machine.
ID:"Management ID" Use change
machine.("machine name") Use
change former group.("group
name") Use change place
group.("group name")
2051 Completed the action changing the Information Completed Nothing
use of a machine. Management changing a usage of
ID:"Management ID" Use change a machine.
machine.("machine name")
2052 Aborted the action changing the Warning Failed to change a Changing a usage of the
use of a machine. Management usage of a machine. machine running in the
ID:"Management ID" group to that of other
group has failed. Check
the cause in the
SystemProvisioning log,
remove the cause, and
execute the process
again. If a machine with
the status displayed as
Error in the group, delete
the machine from the
group, remove the cause
of the error, and then,
register the machine to
the group again.
2053 Canceled the action changing the Information Changing a usage Nothing
use of a machine. Management of a machine is
ID:"Management ID" canceled.
2054 Started the action creating a virtual Information Creates a machine Nothing
machine and adding it to the in a group,
group. Management
ID:"Management ID" VM to
create("machine name") The group
which works a machine("group
name") The machine definition of
VM to create("host name")
2055 Completed the action creating a Information Completed creating Nothing
virtual machine and adding it to the a machine in a
group. Management group.
ID:"Management ID" the created
VM("machine name")
2056 Aborted the action creating a Warning Failed to create a Creating a machine in a
virtual machine and adding it to the machine in a group. group has failed. Check
group. Management the cause in the
ID:"Management ID" the created SystemProvisioning log,
VM("machine name") remove the cause, and
execute the process
again. If a machine with
the status displayed as
Error in the group, delete
the machine from the
group, remove the cause
of the error, and then,
register the machine to
the group again.
2092 Aborted the action Power off the Warning Failed to power OFF A process of powering
machine. Management a machine. OFF the machine has
ID:"Management ID" Machine to failed. Check the cause
be power off.("machine name") in the
SystemProvisioning log,
remove the cause, and
execute the process
again.
2093 Canceled the action Power off the Information Powering OFF a Nothing
machine. Management machine is
ID:"Management ID" Machine to canceled.
be power off.("machine name")
2094 Started the action resetting the Information Resets a machine. Nothing
machine. Management
ID:"Management ID" The resetting
machine.("machine name")
2095 Completed the action resetting the Information Completed resetting Nothing
machine. Management a machine.
ID:"Management ID" The resetting
machine.("machine name")
2096 Aborted the action resetting the Warning Failed to reset a A process of resetting the
machine. Management machine. machine has failed.
ID:"Management ID" The resetting Check the cause in the
machine.("machine name") SystemProvisioning log,
remove the cause, and
execute the process
again.
2097 Canceled the action resetting the Information Resetting a machine Nothing
machine. Management is canceled.
ID:"Management ID" The resetting
machine.("machine name")
2098 Started the action Investigate the Information Investigates a Nothing
machine. Management machine.
ID:"Management ID" Machine to
be Investigated.("machine name")
2099 Completed the action Investigate Information Completed Nothing
the machine. Management investigating a
ID:"Management ID" machine.
2100 Aborted the action Investigate the Warning Failed to investigate A process of
machine. Management a machine. investigating the machine
ID:"Management ID" has failed. Check the
cause in the
SystemProvisioning log,
remove the cause, and
execute the process
again.
2101 Canceled the action Investigate Information Investigating a Nothing
the machine. Management machine is
ID:"Management ID" canceled.
2102 Started the action Investigate the Information Investigating the Nothing
machine by hardware sensor
InvestigateTargetType. status of a machine
Management ID:"Management ID" is started.
Machine to be
Investigated.("machine name")
Investigation type.("Type")
2103 Completed the action Investigate Information Investigating the Nothing
the machine by hardware sensor
InvestigateTargetType. status of a machine
Management ID:"Management ID" is completed. A
Machine to be error state was
Investigated.("machine name") detected. The state
(true) is investigated as
"faulted status".
2104 Aborted the action Investigate the Warning Investigating the Nothing
machine by hardware sensor
InvestigateTargetType. status of a machine
Management ID:"Management ID" is completed.
Machine to be Any errors were not
Investigated.("machine name") investigated in all
the sensors or the
sensor event
occurred.
A process of
investigating the
hardware sensor
status is canceled.
2105 Canceled the action Investigate Information Investigating the Nothing
the machine by hardware sensor
InvestigateTargetType. status of a machine
Management ID:"Management ID" is canceled.
Machine to be
Investigated.("machine name")
2106 Started the action Power cycle the Information Power cycle of the Nothing
machine. Management machine is started.
ID:"Management ID" Machine to
be powercycled.("machine name")
2107 Completed the action Power cycle Information Power cycle of the Nothing
the machine. Management machine is
ID:"Management ID" Machine to completed.
be powercycled.("machine name")
2108 Aborted the action Power cycle the Warning Power cycle of the A process of Power cycle
machine. Management machine is aborted. of the machine has failed.
ID:"Management ID" Machine to Check the cause in the
be powercycled.("machine name") SystemProvisioning log,
remove the cause, and
execute the process
again.
2109 Canceled the action Power cycle Information Power cycle of the Nothing
the machine. Management machine is
ID:"Management ID" Machine to canceled.
be powercycled.("machine name")
2110 Started the action Dump the Information Dumping of the Nothing
machine. Management machine is started.
ID:"Management ID" Machine to
be dumped.("machine name")
2111 Completed the action Dump the Information Dumping of the Nothing
machine. Management machine is
ID:"Management ID" Machine to completed.
be dumped.("machine name")
2112 Aborted the action Dump the Warning Dumping of the A process of dump the
machine. Management machine is failed. machine has failed.
ID:"Management ID" Machine to Check the cause in the
be dumped.("machine name") SystemProvisioning log,
remove the cause, and
execute the process
again.
2113 Canceled the action Dump the Information Dumping of the Nothing
machine. Management machine is
ID:"Management ID" Machine to canceled.
be dumped.("machine name")
2114 Started the action AcpiShutdown Information AcpiShutdown of the Nothing
the machine. Management machine is started.
ID:"Management ID" Machine to
be acpishutdown.("machine
name")
2115 Completed the action Information AcpiShutdown of the Nothing
AcpiShutdown the machine. machine is
Management ID:"Management ID" completed.
Machine to be
acpishutdown.("machine name")
2116 Aborted the action AcpiShutdown Warning AcpiShutdown of the A process of
the machine. Management machine is failed. AcpiShutdown of the
ID:"Management ID" Machine to machine has failed.
be acpishutdown.("machine Check the cause in the
name") SystemProvisioning log,
remove the cause, and
execute the process
again.
2117 Canceled the action AcpiShutdown Information AcpiShutdown of the Nothing
the machine. Management machine is
ID:"Management ID" Machine to canceled.
be acpishutdown.("machine
name")
2118 Started the action Turn on the LED Information Turning on the LED Nothing
of machine. Management of the machine is
ID:"Management ID" Machine to started.
turn on LED.("machine name")
2119 Completed the action Turn on the Information Turning on the LED Nothing
LED of machine. Management of the machine is
ID:"Management ID" Machine to completed.
turn on LED.("machine name")
2120 Aborted the action Turn on the Warning Turning on the LED A process of tuning on
LED of machine. Management of the machine is the LED of the machine
ID:"Management ID" Machine to Failed. has failed. Check the
turn on LED.("machine name") cause in the
SystemProvisioning log,
remove the cause, and
execute the process
again.
2121 Canceled the action Turn on the Information Turning on the LED Nothing
LED of machine. Management of the machine is
ID:"Management ID" Machine to canceled.
turn on LED.("machine name")
2122 Started the action Turn off the LED Information Turning off the LED Nothing
of machine. Management of the machine is
ID:"Management ID" Machine to started.
turn off LED.("machine name")
2123 Completed the action Turn off the Information Turning off the LED Nothing
LED of machine. Management of the machine is
ID:"Management ID" Machine to completed.
turn off LED.("machine name")
2124 Aborted the action Turn off the Warning Turning off the LED A process of tuning on
LED of machine. Management of the machine is the LED of the machine
ID:"Management ID" Machine to failed. has failed. Check the
turn off LED.("machine name") cause in the
SystemProvisioning log,
remove the cause, and
execute the process
again.
2125 Canceled the action Turn off the Information Turning off the LED Nothing
LED of machine. Management of the machine is
ID:"Management ID" Machine to canceled.
turn off LED.("machine name")
2126 Started the action Execute Load Information Load balancing for Nothing
Balancing for VM Server. VM Server is
ID:"Management ID" Target VM started.
Server.("machine name")
2127 Completed the action Execute Information Load balancing for Nothing
Load Balancing for VM Server. VM Server is
ID:"Management ID" Target VM completed.
Server.("machine name")
2128 Aborted the action Execute Load Warning Load balancing for Check the cause in the
Balancing for VM Server. VM Server is failed. SystemProvisioning log,
ID:"Management ID" Target VM remove the cause.
Server.("machine name")
2129 Canceled the action Execute Load Information Load balancing for Nothing
Balancing for VM Server. VM Server is
ID:"Management ID" Target VM canceled.
Server.("machine name")
2130 Started the action Execute Power Information Power saving for Nothing
Saving for VM Server VM Server is
ID:"Management ID" Target VM started.
Server.("machine name")
2131 Completed the action Execute Information Power saving for Nothing
Power Saving for VM Server VM Server is
ID:"Management ID" Target VM completed.
Server.("machine name")
2132 Aborted the action Execute Power Warning Power saving for Check the cause in the
Saving for VM Server VM Server is failed. SystemProvisioning log,
ID:"Management ID" Target VM remove the cause.
Server.("machine name")
2133 Canceled the action Execute Information Power saving for Nothing
Power Saving for VM Server VM Server is
ID:"Management ID" Target VM canceled.
Server.("machine name")
2134 Started the action Apply VM Information Apply VM Optimized Nothing
Optimized Placement Rule Placement Rule is
ID:"Management ID" Target started.
Group.("group name") Target VM
Server.("host name")
2135 Completed the action Apply VM Information Apply VM Optimized Nothing
Optimized Placement Rule Placement Rule is
ID:"Management ID" Target completed.
Group.("group name") Target VM
Server.("host name")
2136 Aborted the action Apply VM Warning Apply VM Optimized Check the cause in the
Optimized Placement Rule Placement Rule is SystemProvisioning log,
ID:"Management ID" Target failed. remove the cause, and
Group.("group name") Target VM execute the process
Server.("host name") again.
2137 Canceled the action Apply VM Information Apply VM Optimized Nothing
Optimized Placement Rule Placement Rule is
ID:"Management ID" Target canceled.
Group.("group name") Target VM
Server.("host name")
2500 Software ("software name") will be Information Distributes software Nothing
distributed to machine "machine to a machine.
name".
2501 Failed to distribute software Error Failed to distribute Distributing software to a
("software name") to the machine software to a machine has failed.
("machine name"). machine. Check the cause in the
log, remove the cause,
and execute the process
again.
2502 Software ("software name") has Information Completed Nothing
been distributed to machine distributing software
("machine name"). to a machine.
2652 VLAN ("VLAN name","port name") Error Failed to create a Creating a VLAN of a
of switch ("switch name") could not VLAN of a switch. switch has failed. Check
be created. the cause in the log,
remove the cause, and
execute the process
again.
2655 VLAN ("VLAN name") of switch Error Failed to delete a Deleting a VLAN of a
("switch name") could not be VLAN of a switch, switch has failed. Check
removed. the cause in the log,
remove the cause, and
execute the process
again.
2658 Port ("port name") could not be Error Failed to register a Registering a port to a
registered to VLAN ("VLAN name") port to a VLAN of a VLAN of a switch has
of switch ("switch name"). switch. failed. Check the cause
in the log, remove the
cause, and execute the
process again.
2659 Failed to remove port ("port name") Error Failed to remove a Removing a port from a
from VLAN ("VLAN name") port from a VLAN of VLAN of a switch has
because it cannot connect to a switch, failed. Check the cause
switch ("switch name"). in the log, remove the
cause, and execute the
process again.
2666 VLAN ("VLAN name","port name") Information Succeeded in Nothing
of switch ("switch name") was creating a VLAN of a
created. switch,
2667 VLAN ("VLAN name") of switch Information There is no VLAN of Nothing
("switch name") is not found. a switch,
2668 VLAN ("VLAN name") of switch Information Succeeded in Nothing
("switch name") was removed. deleting a VLAN of a
switch,
2670 Port ("port name") was registered Information Succeeded in Nothing
to VLAN ("VLAN name") of switch registering a port to
("switch name"). a VLAN of a switch,
2671 Port ("port name") was removed Information Succeeded in Nothing
from VLAN ("VLAN name") of removing a port
switch ("switch name"). from a VLAN of a
switch,
2901 Failed to create the virtual Error Failed to create the An error occurred when
machine. The request for creating virtual machine. creating a virtual
the virtual machine failed. machine. Remove the
Cause:{0} cause of the error and try
the operation again.
2903 Failed to delete the virtual Error Failed to delete the An error occurred when
machine. The request for deleting virtual machine. deleting a virtual
the virtual machine failed. machine. Remove the
Cause:{0} cause of the error and try
the operation again.
101 NvBase System Service Error The service of NEC Check that the NvBase
has not been started. ESMPRO Manager System Service of NEC
(NvBase System Service) ESMPRO Manager is
is not started. started. If it is not started,
start the service.
102 NvBase System Service Information Since the service of NEC Nothing
has been started. Resumed ESMPRO Manager
monitoring events. (NvBase System Service)
is started, monitoring
events was resumed.
103 NvBase System Service is Error NEC ESMPRO Manager Install NEC ESMPRO
not installed. is not installed. Manager.
SystemProvisioning
Folder SystemProvisioning installation folder\log\
(Default installation folder: C:\Program Files\NEC\PVM\log)
Files UsualLogx.log
ActionJobx.log
ActionSequencex.log
CmdbApix.log
ComponentManagerx.log
DataAccessx.log
Engine.x.log
EsmproMonitorx.log
EsmproProviderx.log
InformationCollectx.log
JobManagerx.log
PimProviderx.log
ProviderCommonx.log
PvmClarixx.log
PvmEventlogx.log
PvmiStoragex.log
PvmMachineEventx.log
PvmNetvisorprox.log
PVMReportx.log
PvmSwitchBladex.log
PvmSymmetrixx.log
pvmutlx.log
ResourceEventListenerx.log
ResourceEventSenderx.log
SystemEventx.log
UniversalConnectorx.log
VMwareProvider.x.log
VMwareProviderEventx.log
XenProvider.x.log
CmdbApiAccessx.log
CmdbConverterx.log
CmdbSqlSessionx.log
DataAccessErrorx.log
DpmLibWrapperx.log
SigmaSystemCenter 2.1 Reference Guide
452
List of Log Files
DpmProviderx.log
HyperVProvider.x.log
ResourceEventListx.log
UniversalConnectorDefectx.log
VMwareProviderEventx.log
MaintenanceCmdbx.log
ssc.log
ssc-old.log
PvmStoragex.log
(x: 0 to1)
Recording If the size of a log file exceeds the maximum size, the log file switches from
*0.log to *1.log.
Method
These files are created when SystemProvisioning output each log. There is a
case that all the above files do not exist.
Supplement ▪ You can check the log files with Text Editor.
▪ You can change the maximum output size from the Management tree -
Environment Setting icon - Log tab - The Maximum Output Size box.
Files Web-GUI.log
Web-GUI.log.1
Recording The maximum size of the file is 16 MB and the file is managed up until the
second generation.
Method
When Web-GUI.log has reached the maximum size, it is renamed to
Web-GUI.log.1 and the new Web-GUI.log is created. (If Web-GUI.log.1
already exists, it is deleted.)
Supplement You can check the log files with Text Editor.
Files apiserv.csv
apitrace.log
bkressvc.csv
clistart.csv
cliwatch.csv
DepInit.csv
depssvc.csv
DIBPkgMake.csv
ftsvc.csv
pmdb.log
pminfo.log
pxemtftp.csv
pxesvc.csv
rupdssvc.csv
schwatch.csv
snrwatch.csv
rupdssvc_Machine Name_MAC Address.log
Recording The maximum size of each cave file is 10 MB and the file is managed up until the
fifth generation.
Method
The maximum size of apitrace.log is 1000 KB and the file is not managed by
generation management.
The maximum size of pmdb.log and rupdssvc_Machine Name_MAC Address.log is
16 KB and the files are managed in one generation.
Files Scenario.rpt
Files Index.rpt
MAC Address.rpt
Recording The files are managed individually with a MAC address for each client.
Method The size is up to 3 MB in sum of the size of files in the folder.
Files MngSelfJSLog_YYYYMMDD.csv
MngUserJSLog_YYYYMMDD.csv
CmdSelfJSLog_YYYYMMDD.csv
(YYYYMMDD: Date)
Contents Audit log (Internal action in the management server / operation by a user)
Recording The above three kinds of files are created once a day. There is no limitation in file
size. 31 files are saved for each kind of files.
Method
Recording The files are managed individually with MAC address for each managed machine.
Method They are overwritten every time a scenario is executed.
Files error.log
trace.log
Contents Error logs and trace logs of Web Server for DPM
Recording The default size of each file is 1000 Kbytes. You can change the setting from the
DPM Web Console.
Method
Debug Logs
Folder System Monitor - Performance Monitoring Services installation folder\log\
(Default installation folder: C:\Program Files\NEC\
SystemMonitorPerformance\log)
Files rm_service.log
rm_client.log
rm_tool.log
rm_command.log
Recording The default maximum log size is 10 MB and if a size of a file reaches the limit,
an output file is switched. The file is managed up until the second generation.
Method
Supplement You can check the log files with Text Editor.
Files Files with a name of a server name with .dat or .bak added
• Alert logs
Folder The Alert directory in the directory that the registry
[HKEY_LOCAL_MACHINE\SOFTWARE\NEC\NVBASE] WorkDir
locates
Recording If the number of logs exceeds the maximum number of logs on the
General of the Option dialog box ([Tools] - [Options] menu) of
Method
AlertViewer, logs are deleted from the oldest one.
Supplement If you use the AlertLogAutoSave Settings, files are saved according to
the setting.
Note: If NEC ESMPRO Agent is installed first, the default installation folder is
C:\ESM\AlertMan.
(If NEC ESMPRO Manager is installed first, the default installation folder is
C:\ProgramFiles\ESMPRO\AlertMan.)
Folder C:\ProgramFiles\ESMPRO\AlertMan\Work\
Files AMVSCKR.log
Action of If a Size Reaches the Renamed to a .bak file and .log is newly created.
Maximum Capacity
Until What Generation the Files Second generation (.log and .bak)
Are Managed
Folder C:\ProgramFiles\ESMPRO\AlertMan\Work\
Files NVCRTCPY.LOG
Folder C:\ProgramFiles\ESMPRO\AlertMan\Work\
Files NvIRTCp2.log
NvIRTCpy.log
Action of If a Size Reaches the Renamed to a .bak file and .log is newly created.
Maximum Capacity
Until What Generation the Files Second generation (.log and .bak)
Are Managed
If Logs Are Increasing in Yes: If you configure the setting of received information.
Operation
Folder C:\ProgramFiles\ESMPRO\NVWORK\AMWORK\SCK\
Files AMVSCKR.LOG
Action of If a Size Reaches the Information is updated from the oldest one
Maximum Capacity
461
Appendix A Network Ports and
Protocols
Components in SigmaSystemCenter are configured to use the following network ports
by default. This appendix provides the information of network ports and protocols.
SystemProvisioning
Item Execution File Port Proto Direc Connecting Target Port Execution File
Name No. col tion No. Name
Web Server for Auto TCP > Web Server for 8080 \Program
DPM matic DPM Files\Apache
Software
Foundation\Tom
cat
6.0\bin\tomcat6.
exe
Hyper-V \Program Auto TCP > WMI (Hyper-V) 135
Management Files\WINDOW matic (DCO
S\System32\svc M)
host.exe
Hyper-V \Program Auto TCP > WMI (Hyper-V) 1024-
Management Files\NEC\PVM\ matic (DCO 65535
bin\PVMService M) *2
Proc.exe
UC \Program 26102 TCP < UC Client Auto
*1 Files\NEC\PVM\ matic
bin\PVMService
Proc.exe
UCWebService \Program 26150 TCP < UC Client Auto
*1 Files\NEC\PVM\ matic
bin\PVMService
Proc.exe
Web Console 80 TCP < A Web browser Auto
matic
Out-of-Band \Program Auto UDP > BMC 623
Management Files\NEC\PVM\ matic
bin\PVMService
Proc.exe
\WINDOWS\Sys 162 UDP < BMC Auto
tem32\snmptrap (SNM matic
.exe P
Trap)
162
*1 Used by connection from System Monitor - Performance Monitoring Services and
SystemProvisioning modules, including the Web Console and pvmutl.
*2 To restrict ports, note the points on Microsoft KB300083 or KB154596.
463
Appendix A Network Ports and Protocols
DeploymentManager
Web Server for DPM
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Appendix
465
Appendix A Network Ports and Protocols
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Management Server for DPM uses the following protocols other than the above table.
Appendix
467
Appendix A Network Ports and Protocols
NFS Server
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Database Server
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Appendix
469
Appendix A Network Ports and Protocols
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Item Execution File Port Prot Direct Connecting Target Port Execution File
Name No. ocol ion No. Name
Note: You cannot setup the database of System Monitor - Performance Monitoring
Services on a server which is not a management server.
1. Backing up SystemProvisioning
Back up SystemProvisioning.
For the procedure, see Subsection 9.2.1, “Backing up SystemProvisioning" in
SigmaSystemCenter Configuration Guide.
2. Creating Instance
Setup the SQL Server 2005 Express Edition on the SERVER1.
1. Download the setup program of SQL Server 2005 Express Edition from the
following site.
http://www.microsoft.com/downloads/details.aspx?FamilyID=3181842a-4090-
4431-acdd-9a1c832e65a6&DisplayLang=en
2. Run the downloaded SQLEXPR.EXE and proceed with the setup according to
the instructions on the screen.
471
Appendix B Transferring the Configuration Database
3. The Registration Information dialog box appears during setup. Clear the
Hide advanced configuration options check box.
4. The Instance Name dialog box appears. Select Named instance. and enter
SSCCMDB in the text box.
Complete the setup according to the instructions that appear on the screen.
4. Creating a database
Run the following command on the Command Prompt window. Always use pvminf
as the database name used as the configuration database.
E.g.1)
> sqlcmd -E -S (local)\SSCCMDB -Q "create database pvminf"
E.g.2)
> sqlcmd -E -S (local)\SSCCMDB
1> create database pvminf
2> go
Appendix
473
Appendix B Transferring the Configuration Database
E.g.1)
> sqlcmd -E -S (local)\SSCCMDB -Q "restore database
pvminf from disk = 'C:\temp\backup.dat' with replace"
E.g.2)
> sqlcmd -E -S (local)\SSCCMDB
1> restore database pvminf from disk =
‘C:\temp\backup.dat’ with replace
2> go
7. Adding a user
If you use Windows authentication login, you need to add a user to a group to
which the access right to SQL Server 2005 of SERVER1 is assigned.
1. Click the Start menu, and click Control Panel. From Control Panel,
double-click Administrative Tools. From Administrative Tools, and
double-click Computer Management to open the Computer Management
dialog box.
2. Click System Tools, Local Users, and Groups.
3. The following group is created in the displayed group list. Right-click the group
and click Add to Group.
Group name: SQLServer2005MSSQLUser$SERVER1$SSCCMDB
4. Add the following user on the property dialog box. The user differs depending
on when SERVER1 is participating in Work Group or when participating in
domain.
- In Work Group: NT AUTHORITY\ANONYMOUS LOGON
- In domain: The domain name\the Computer Name of management server
3. Enter values in the Host name and Instance name boxes, and select Use
Windows authentication login. Click Save.
4. Click the Start menu, and click Control Panel. From Control Panel,
double-click Administrative Tools. From Administrative Tools, and
double-click Services to start the Services Snap-in.
5. Right-click PVMService and click Restart.
Appendix
475
Appendix B Transferring the Configuration Database
1. Backing up SystemProvisioning
Back up SystemProvisioning.
For the procedure, see Subsection 9.2.1, "Backing up SystemProvisioning" in
SigmaSystemCenter Configuration Guide.
2. Creating Instance
Setup the SQL Server 2005 Express Edition on the SERVER1.
1. Download the setup program of SQL Server 2005 Express Edition from the
following site.
http://www.microsoft.com/downloads/details.aspx?FamilyID=3181842a-4090-
4431-acdd-9a1c832e65a6&DisplayLang=en
2. Run the downloaded SQLEXPR.EXE and proceed with the setup according to
the instructions on the screen.
3. The Registration Information dialog box appears during setup. Clear the
Hide advanced configuration options check box.
5. The Authentication Mode dialog box appears during setup. Select Mixed
Mode (Windows Authentication and SQL Server Authentication), and
enter the sa logon password in the Enter password and Confirm password
boxes.
Complete the setup according to the instructions that appear on the screen.
Appendix
477
Appendix B Transferring the Configuration Database
4. Creating a database
Run the following command on the Command Prompt window. Always use pvminf
as the database name used as the configuration database.
E.g.1)
> sqlcmd -E -S (local)\SSCCMDB -Q "create database pvminf"
E.g.2)
> sqlcmd -E -S (local)\SSCCMDB
1> create database pvminf
2> go
E.g.1)
> sqlcmd -E -S (local)\SSCCMDB -Q "restore database pvminf
from disk = 'C:\temp\backup.dat' with replace"
E.g.2)
> sqlcmd -E -S (local)\SSCCMDB
1> restore database pvminf from disk =
‘C:\temp\backup.dat’ with replace
2> go
3. Enter values in the Host name and Instance name boxes, and select Use
SQL authentication login. Enter sa in the Account box, and enter the sa
password entered in Procedure 2 in the Password and Confirm password
boxes. And then, click Save.
4. Click the Start menu, and click Control Panel. From Control Panel,
double-click Administrative Tools. From Administrative Tools, and
double-click Services to start the Services Snap-in.
5. Right-click PVMService and click Restart.
Appendix
479
Appendix C How to Estimate Database
Usage
SystemProvisioning, System Monitor - Performance Monitoring Services and
DeploymentManager use the database in SigmaSystemCenter.
SystemProvisioning
Estimates of disk capacities are described below according to the machine types.
Physical machines
About 4.1 KB is used for management of a blade chassis and a blade server.
Use the following information as a guide of individual calculation.
Necessary disk capacity 20.5 KB = 5 (the number of blade servers) * 4.1 KB.
However, if the numbers of NIC and memories to connect to the machine increase,
necessary disk capacity also increases.
481
Appendix C How to Estimate Database Usage
Virtual machines
vCenter Server or ESX must be built to manage virtual machines.
About 9.0 KB is used for management of a virtual machine.
Use the following information as a guide of individual calculation.
E.g.1)
When building vCenter Server * 1, DataCenter * 5, ESX * 50, a virtual machine *
1500, and a template* 300, necessary disk capacity is calculated to about 5.4 MB
according to the following formula.
Logical settings
Logical settings include server groups, host definitions and IP address definitions.
Use the following information as a guide of individual calculation.
E.g.1)
When creating a server group with 10 host definitions that are configured 1 IP
address for each, necessary disk capacity is calculated to about 12.5 KB.
E.g.2)
When creating 50 server groups with 500 host definitions of DHCP operations for
each, necessary disk capacity is calculated to about 17.5 MB.
The size of operations log (KB) = The number of operations log records * (0.6 + 2.8 / 3) KB
E.g.)
When recording 100,000 records of operations log, necessary disk capacity is
about 153 MB. (100,000 is the maximum number of operations logs which can be
recorded.)
Appendix
483
Appendix C How to Estimate Database Usage
* Performance data that exceeds the data retention period will be deleted regularly.
When using the default values, a rough estimate of necessary database capacity can
be calculated according to the following formula.
The size of total amount in the default data retention period = 4 MB * <The number of machines to
be monitored by System Monitor - Performance Monitoring Services>
Necessary database capacity for the performance data can be configured by adjusting
the number of monitoring performance information items, data storage period, and data
collection period.
A rough estimate of database capacity necessary for future increases can be made
according to the following formula.
E.g.)
When the number of registered computers is 40,000 and the number of registered
packages is 100, necessary disk capacity is about 1.0 GB.
Appendix
485
Appendix D Glossary
A
ACPI Abbreviation for Advanced Configuration and Power
Interface. This is a specification for power management for a
computer, which enables operating system-directed
configuration and detailed power management.
B
Blade Server Refers to a model of Express5800/BladeServer series that
supports SystemProvisioning.
Blade Server Enclosure Unit Refers to a chassis that store CPU blades of a blade server.
C
CLARiiON A name of a storage product of EMC Corporation.
D
Datacenter A kind of group that can unify virtual machine servers. When
managing the vCenter Server environment, datacenters in
SigmaSystemCenter corresponds to datacenters in vCenter
Server. When managing the Xen environment, you can create
one datacenter in a Pool.
Clusters of vCenter Server are managed as datacenters in
SigmaSystemCenter.
487
Appendix D Glossary
Deployment Disk Image A deployment disk image is a disk image that does not have
machine's unique information and that is created by deleting
the machine's unique information from data of OS which is
installed on a machine.
A tool called Sysprep is used to create a deployment disk
image.
Disk Clone Disk Clone creates virtual machines by copying a basic image
created from a master VM without change.
E
ESX A product of VMware Inc. that implements a virtual machine.
F
Full Backup Disk Image A full backup disk image is an image that is a backup image of
a machine without modifying its information.
H
HBA Abbreviation for Host Bus Adapter.
Refers to the FibreChannel controller.
I
IIS Abbreviation for "Internet Information Services." This is
software for internet server provided by Microsoft Corporation.
L
Load Balancer A device that balances load of machines by managing
demands from an external network and transferring demands
to the target machine.
SystemProvisioning supports SS8000, BIG-IP, and
ServerIron series.
Load Balancer Virtual Server A setting of a server created on a load balancer. This setting
is a setting that makes multiple pieces of hardware be shown
as one logical server. The setting has an IP address, protocol,
and port of a target server of load distribution process.
Load balancer Group Used when setting up a load balancing environment. Refers
to a setting of the load balancing configuration that correlate a
load balancer virtual server and a load balancing node to be a
distribution target.
Appendix
489
Appendix D Glossary
Local Script Function A function that executes an execution file, which is called a
local script, in .bat format on a SigmaSystemCenter
management server. This is used when you adding, changing
usage, or replacing a machine, and if you want to perform
specific processes that depend on system configuration or
environment on the SigmaSystemCenter management
server.
M
MAC Address Abbreviation for Media Access Control Address, and it is an
address of NIC that identifies each host (machine) connected
to a network.
Management Server for DPM A component of DPM that manages DPM managed
machines.
Management Server for DPM executes process to managed
machines by instructions from DPM Web Console.
MasterScope Network Manager Software for managing operations using networks. This
software is used for controlling and grasping configuration of
network devices.
N
NEC ESMPRO Manager These are the machine management software included in
Express5800 series.
NEC ESMPRO Agent
NEC Storage Manager The generic name of the NEC Storage management software
that is used for controlling storage by SystemProvisioning.
P
Physical Machine A generic name for hardware machines that has an entity.
In SigmaSystemCenter manuals, a physical machine includes
a general machine, blade server, and virtual machine server.
S
SAN Abbreviation for Storage Area Network.
With a storage dedicated network, this provides storage to
machines.
Shared Pool A pool that does not belong to any operation group.
Shared Pool Machine A managed physical machine that belongs to a shared pool. If
certain conditions are met, a shared pool machine is used for
a configuration change.
Appendix
491
Appendix D Glossary
System Monitor - Performance Software that monitors the usage status of machine
resources. In case of a performance failure, System Monitor -
Monitoring Services
Performance Monitoring Services can send an alert to
SystemProvisioning.
T
Tag Cloud A function to classify and summarize various information of
managed machines as Tag. Also, information of all managed
machines can be displayed visually as multiple Tags.
If you select a Tag, machines classified under the Tag will be
displayed.
U
Unused Machine Refers to a machine that has not activated in a group although
the machine is registered as a management target in
SystemProvisioning, or a machine that is not registered to a
group pool.
V
vCenter Server A product of VMware Inc. that manages multiple ESXs and
virtual machines on ESXs collectively.
(formerly VirtualCenter)
vSphere Client A product of VMware, Inc. that has the user interface from
which a user can create, manage, and monitor virtual
(formerly Virtual Infrastructure machines and resources on a virtual machine.
Client)
W
Web Console There are two Web Consoles; a component of
SigmaSystemCenter and a component of DPM. In this
manual, a word Web Console refers to the Web Console of
SigmaSystemCenter.
Web Console of SigmaSystemCenter is a console for
configuring and operating SigmaSystemCenter from a
browser.
Web Console of DPM is a browser from which a user can
operate Management Server for DPM.
In SigmaSystemCenter manuals, the Web Console of DPM is
described as DPM Web Console.
WOL (Wake On LAN) A function that power on a computer connected to LAN from
other computer.
Appendix
493
Appendix D Glossary
X
XenCenter A product of Citrix Systems, Inc. that manages multiple
XenServers and virtual machines on XenServers collectively.
Added description regarding addition of the support for Hyper-V Cluster environment
Chapter 2 2.1.1 "Hyper-V Environment"
2.1.2 "System Configuration of Hyper-V Cluster"
2.1.3 "Configuring Cluster in Hyper-V Environment"
Chapter 5 5.2 "Events SigmaSystemCenter Can Detect"
5.2.8 "Events the Hyper-V Cluster Function Can Detect"
495
Appendix E Revision History
Added description regarding addition of the Linked Clone and Disk Clone functions
Chapter 1 1.4 "Distribution Software Management"
1.4.2 "What Is a Template?"
1.6 "Use of a Template"
1.11.6 "Activating a Machine / Create and Assign Machine (Virtual Machine)"
1.11.7 "Activating a Machine / Allocate Machine (Virtual Machine)"
1.11.8 "Activating a Machine / Scale Out (Virtual Machine)"
Chapter 5 5.2.10 "About Deleting a Virtual Machine (VMware)"
5.2.11 "About Backing up a Virtual Machine (VMware)"
5.2.18 "Master VM"
5.2.22 "About Executing Allocate Machine to a Virtual Machine Host"
5.2.25 "Other Notes"
Appendix D "Glossary"
Appendix
497
Appendix E Revision History
Modified the description and added a section regarding MasterScope Network Manager
Chapter 1 1.8.3 "Usable VLAN Types"
1.10.1 "Operations of a Pool Machine"
Appendix D "Glossary"
Appendix
499
501