First Edition · System Monitor Performance Monitoring Services 5.- 9 (hereafter referred to as "System Monitor - Performance Monitoring Services") is a software program that provides

System Monitor - Performance Monitoring Services 5.9

User's Guide

- First Edition -

Copyright (C) NEC Corporation 2004-2017.

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 ▪ NEC SigmaSystemCenter, SigmaSystemCenter, MasterScope, EXPRESSCLUSTER, SIGMABLADE and ProgrammableFlow are either registered trademarks or trademarks of NEC Corporation in the United States and/or other countries. ▪ ESMPRO is a registered trademark or trademark of NEC Corporation in Japan and other countries. ▪ Microsoft, Windows, Windows Server, Windows Vista, Internet Explorer, SQL Server, and Hyper-V are registered trademarks of Microsoft Corporation in the United States and other countries. ▪ Linux is a registered trademark or trademark of Linus Torvalds in the U.S. and/or other countries. ▪ Red Hat is a registered trademark or trademark of Red Hat, Inc. in the U.S. and/or other countries. ▪ PostgreSQL is a trademark or registered trademark of the PostgreSQL Global Development Group in the United States and/or other countries. Other names and brands used in this document may be registered trademarks or trademarks of their respective owners. Note that (R) and TM marks are not indicated in this document.

iii

Contents Preface ................................................................................................................................. vii

How to Use This Manual ....................................................................................................................... vii Manual Organization ............................................................................................................................. vii Document Conventions......................................................................................................................... viii

1. Functions....................................................................................................................... 3 1.1. Function Overview of System Monitor - Performance Monitoring Services ............................ 4 1.2. Basic Configuration of System Monitor - Performance Monitoring Services ........................... 6 1.3. Collected Performance Data .................................................................................................... 11

1.3.1.Types of Performance Indicators and Collecting Intervals ........................................................................ 12 1.3.2.Built-in Performance Indicator .................................................................................................................. 12 1.3.3.Custom Performance Indicator ................................................................................................................. 25 1.3.4.Storing Data that has been collected ........................................................................................................ 34

1.4. Summary Data ......................................................................................................................... 35 1.4.1.Storage of Summary Data ........................................................................................................................ 35 1.4.2.Usage of Summary Data .......................................................................................................................... 35

1.5. Data Management ................................................................................................................... 37 1.5.1.Data Management Tool ............................................................................................................................ 37 1.5.2.Database Size Monitoring Function .......................................................................................................... 37

1.6. Groups ..................................................................................................................................... 38 1.7. Connecting to Managed Machines .......................................................................................... 39

1.7.1.Specifications for Managed Machines ...................................................................................................... 39 1.7.2.Connection Setting for the Managed Machines ........................................................................................ 40 1.7.3.Settings on the Managed Machine ........................................................................................................... 41 1.7.4.Ports Used between Management Servers and Managed Machines ....................................................... 46

1.8. Displaying Performance Status and CSV File Output ............................................................. 47 1.8.1.Statistics ................................................................................................................................................... 47 1.8.2.Displaying Formats for Performance Status Graphs ................................................................................ 48 1.8.3.Graph Display Periods .............................................................................................................................. 50 1.8.4.The Graph Window ................................................................................................................................... 51 1.8.5.Output Graph Data to File ........................................................................................................................ 52 1.8.6.Output Data Using Command Line Tool ................................................................................................... 52

1.9. Threshold Monitoring and the Notification Function ................................................................ 53 1.9.1.Types of Thresholds ................................................................................................................................. 53 1.9.2.Units of Threshold Monitoring ................................................................................................................... 53 1.9.3.Performance Indicators Subject to Threshold Monitoring ......................................................................... 54 1.9.4.Notification Actions at Over-Threshold ..................................................................................................... 54

1.10. The SystemProvisioning Linkage Function .............................................................................. 57 1.10.1.System Configuration ............................................................................................................................. 57 1.10.2.Applying System Configuration Information ............................................................................................ 58 1.10.3.Timing of Applying of Configuration Information ..................................................................................... 61 1.10.4.Rules for Applying Configuration Information ......................................................................................... 61 1.10.5.Notifying Performance Abnormalities ..................................................................................................... 65 1.10.6.VM Optimization Linkage Function ......................................................................................................... 78

1.11. Command-Line Interface ......................................................................................................... 80 1.11.1.System Configuration ............................................................................................................................. 80 1.11.2.Data Format and Target ......................................................................................................................... 81

2. Configuration Settings ................................................................................................. 83 2.1. Starting the Performance Monitoring Service .......................................................................... 84

2.1.1.About the Performance Monitoring Service .............................................................................................. 84 2.1.2.How to Start the Performance Monitoring Service Manually .................................................................... 84

2.2. Registering the Management Server ....................................................................................... 85 2.3. Connection Settings to Managed Machines ............................................................................ 86

2.3.1.Setting the Connection Account to the Managed Machine ....................................................................... 86 2.4. Connection Settings to the Management Console .................................................................. 87

2.4.1.Port Number ............................................................................................................................................. 87

2.4.2.Firewall ...................................................................................................................................................... 89 2.5. The Execution Account for the Performance Monitoring Service ............................................ 91

2.5.1.Setting up the Performance Monitoring Service Execution Account.......................................................... 91 2.5.2.How to Change the Performance Monitoring Service Execution Account ................................................. 91 2.5.3.Rights for the Performance Monitoring Service Execution Account .......................................................... 92

2.6. SystemProvisioning Connection Settings ................................................................................ 94 2.7. Log Settings ............................................................................................................................. 97

3. Basic Operations ........................................................................................................... 99 3.1. Starting the Management Console and Connecting to the Management Server .................... 100

3.1.1.About the Management Console ............................................................................................................... 100 3.1.2.Starting the Management Console ............................................................................................................ 100 3.1.3.Connecting to the Management Server ..................................................................................................... 101 3.1.4.Specifying from the Navigation Tree Window ............................................................................................ 101 3.1.5.Notes on Operating with More than One Management Console ............................................................... 102

3.2. The Main Window .................................................................................................................... 104 3.2.1.The Structure of the Main Window ............................................................................................................ 104 3.2.2.Menu Bar ................................................................................................................................................... 104 3.2.3.The Toolbar ............................................................................................................................................... 106 3.2.4.The Navigation Tree Window .................................................................................................................... 107 3.2.5.Popup Menu for Management Server ....................................................................................................... 107 3.2.6.Search View .............................................................................................................................................. 108 3.2.7.The Graph Display Pane ........................................................................................................................... 108 3.2.8.Log Window .............................................................................................................................................. 108 3.2.9.The Status Bar .......................................................................................................................................... 109

4. Collecting Performance Data ........................................................................................ 111 4.1. Specifications for Managed Machines ..................................................................................... 112

4.1.1.Specifications in the Navigation Tree Window .......................................................................................... 112 4.1.2.How to Apply SystemProvisioning Configuration Information .................................................................... 123

4.2. Specifications for the Performance Data to be collected ......................................................... 125 4.2.1.How to Specify Performance Indicator Settings ........................................................................................ 125 4.2.2.How to Specify Collecting Data Settings ................................................................................................... 131 4.2.3.Collecting Data Settings Automatically Applied by SystemProvisioning Linkage ...................................... 137

4.3. Pausing and Restarting the Collecting of Performance Data .................................................. 141 4.4. Checking the Collecting Status for Performance Data............................................................. 142

5. Performance Status Display and File Output .............................................................. 147 5.1. Displaying Performance Graphs .............................................................................................. 148

5.1.1.How to Display Performance Graphs ........................................................................................................ 148 5.1.2.Graph Window .......................................................................................................................................... 154 5.1.3.Simple Graph Display Function ................................................................................................................. 155 5.1.4.Changing Performance Indicator Graphs .................................................................................................. 159

5.2. Saving Performance Status Display Specifications ................................................................. 160 5.3. File Output ................................................................................................................................ 161

5.3.1.File Output Methods .................................................................................................................................. 161 6. Threshold Monitoring and Notification ........................................................................ 163

6.1. Configuring Threshold Monitoring ............................................................................................ 164 6.1.1.How to set up threshold monitoring ........................................................................................................... 164 6.1.2.How to display over-threshold areas on graphs ........................................................................................ 170 6.1.3.Threshold setting automatically applied by SystemProvisioning linkage ................................................... 170

7. Management of Performance Data ............................................................................... 175 7.1. Data Management Tool ............................................................................................................ 176 7.2. Database Size Monitoring ........................................................................................................ 179

7.2.1.Database size warning setting .................................................................................................................. 179 7.2.2.Database size warning .............................................................................................................................. 180

8. Command-Line Interface .............................................................................................. 181 8.1. ssc-perf Command ................................................................................................................... 182

8.1.1.The Basic Syntax ...................................................................................................................................... 182

v

8.1.2.show performancedata Command............................................................................................................ 183 8.1.3.show performanceindicator command ...................................................................................................... 192 8.1.4.Add Performance Indicator Command ..................................................................................................... 194 8.1.5.Delete performance indicator command ................................................................................................... 197 8.1.6.show storageperiod command ................................................................................................................. 198 8.1.7.set storageperiod command ..................................................................................................................... 199 8.1.8.show databasesetting command .............................................................................................................. 200 8.1.9.set databasesetting command .................................................................................................................. 202 8.1.10.apply SystemProvisioningConfiguration command ................................................................................. 204

9. Troubleshooting ............................................................................................................ 207 9.1. The Event Log .......................................................................................................................... 208

9.1.1.Event Logs for Performance Monitoring Service ...................................................................................... 208 9.1.2.Event logs for Management Console ........................................................................................................ 215

9.2. What to do if the Performance Monitoring Service does not Start ........................................... 216 9.3. What to do if the Connection from Management Console to Server Fails............................... 223 9.4. What to do if Performance Data Collecting Fails ..................................................................... 225

9.4.1.Errors and Actions for when Performance Data Collecting Fails .............................................................. 225 9.4.2.Error Status Recovery Processing............................................................................................................ 232

9.5. What to do if Performance Data Collecting is delayed ............................................................ 234 9.5.1.Errors and Actions for when Performance Data Collecting is delayed...................................................... 234

9.6. What to do if there are SystemProvisioning Configuration Applying Errors ............................ 235 9.7. What to do if there are Errors when Performance Abnormalities are reported to

SystemProvisioning ................................................................................................................. 237 9.8. What to do if the SystemMonitor data management tool might not start ................................. 239 9.9. Database .................................................................................................................................. 242

9.9.1.Estimating the Disk Space Required for Saving Performance Data ......................................................... 242 9.9.2.Errors and Actions for when There is not Enough Disk Space ................................................................. 246 9.9.3.Errors and Actions for Database Faults .................................................................................................... 249 9.9.4.Procedure for Backing up and Restoring the Database ............................................................................ 250

9.10. Other ........................................................................................................................................ 254 10. Notes .............................................................................................................................. 255

10.1. The Estimated Number of Monitored Objects .......................................................................... 256 10.2. Notes on Database .................................................................................................................. 257 10.3. Notes on Graph Displays ......................................................................................................... 258 10.4. Notes on Linking to SystemProvisioning ................................................................................. 259 10.5. Release of Resources .............................................................................................................. 264 10.6. Notes on Upgrading/Updating .................................................................................................. 265

10.6.1.Changing the Setting of SystemProvisioning Configuration Path ........................................................... 265 10.6.2.Additional Setting for Managing Linux Machine with Multipath Configuration ......................................... 265 10.6.3.Changing the Performance Indicator Title .............................................................................................. 265 10.6.4.Changing the Error Code Format for User Scripts .................................................................................. 265 10.6.5.Additional Setting for Collecting Disk Speed Performance Data of Linux Virtual Machines in

KVM ............................................................................................................................................... 266 10.6.6.When Changing for Collecting Performance Data by Using Remote User Scripts ................................. 266 10.6.7.When Changing a Group Name ............................................................................................................. 267

10.7. Issues When Other Products to Monitor the Windows Managed Machine Coexist with System Monitor - Performance Monitoring Services ............................................................... 268

10.8. A Character Encoding for Collecting Data via SSH ................................................................. 269 Appendix A How performance values for groups are calculated .................................. 273 Appendix B Transferring the Database (For SQL Server) .............................................. 275

Using Windows Authentication Login ................................................................................................... 275 Using SQL Authentication Login ........................................................................................................... 282

Appendix C Transferring the Database (For PostgreSQL) ............................................. 289 Appendix D Performance Counter Information of VMware ESXi ................................... 293

Metric Group (category) ........................................................................................................................ 293

Counter, Rollup (counter) ...................................................................................................................... 294 Appendix E License Information ...................................................................................... 295

vii

Preface

How to Use This Manual System Monitor - Performance Monitoring Services 5.9 (hereafter referred to as "System Monitor - Performance Monitoring Services") is a software program that provides a simple means of monitoring the performance of multiple managed objects. This manual explains how to use System Monitor - Performance Monitoring Services.

Manual Organization Part I System Monitor - Performance Monitoring Services 1 Functions: Explains the functions and features of System Monitor - Performance Monitoring Services 2 Configuration Settings: Explains how to make configuration settings 3 Basic Operations: Explains startup methods and basic GUI operations. 4 Collecting Performance Data: Explains how to make settings relating to collecting performance data. 5 Performance Status Display and File Output: Explains how to make settings relating to displaying performance status. 6 Threshold Monitoring and Notification: Explains how to monitor thresholds for performance data and make settings for the notification function. 7 Management of Performance Data: Explains how to manage performance data. 8 Command-Line Interface: Explains how to use command-line interface. 9 Troubleshooting: Explains errors and how to handle them. 10 Notes: Explains various notes and issues. Appendices Appendix A How performance values for groups are calculated Appendix B Transferring the Database (For SQL Server) Appendix C Transferring the Database (For PostgreSQL) Appendix D Performance Counter Information of VMware ESXi Appendix E License Information

viii

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

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

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

Convention Used Item Example

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

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

Italic font Book or manual titles, and variable names

Configuration Guide add GroupName

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

Monospace font (courier)

Long text inputs, messages and command-line commands

Type the following text: Confidential–Class B

1

Part I System Monitor - Performance Monitoring Services

This section describes how to use System Monitor - Performance Monitoring Services. This part contains the following chapters: • 1 Functions • 2 Configuration Settings • 3 Basic Operations • 4 Collecting Performance Data • 5 Performance Status Display and File Output • 6 Threshold Monitoring and Notification • 7 Management of Performance Data • 8 Command-Line Interface • 9 Troubleshooting • 10 Notes

3

1. Functions This chapter explains the functions and features of System Monitor - Performance Monitoring Services. This chapter contains the following sections: • 1.1 Function Overview of System Monitor - Performance Monitoring Services ................ 4 • 1.2 Basic Configuration of System Monitor - Performance Monitoring Services ............... 6 • 1.3 Collected Performance Data......................................................................................11 • 1.4 Summary Data ...........................................................................................................35 • 1.5 Data Management .....................................................................................................37 • 1.6 Groups .......................................................................................................................38 • 1.7 Connecting to Managed Machines ............................................................................39 • 1.8 Displaying Performance Status and CSV File Output ...............................................47 • 1.9 Threshold Monitoring and the Notification Function ..................................................53 • 1.10 The SystemProvisioning Linkage Function ...............................................................57 • 1.11 Command-Line Interface ...........................................................................................80

1 Functions

System Monitor - Performance Monitoring Services User's Guide 4

1.1. Function Overview of System Monitor - Performance Monitoring Services

System Monitor - Performance Monitoring Services is a software program that supports monitoring the performance status of systems, and it provides features to view the performance state and to monitor thresholds by periodically collecting performance data from the system and accumulating those data. In System Monitor - Performance Monitoring Services, methods that are used to collecting performance data differ depending on managed objects. If the objects are machines, the data are collected from physical machines on which Windows or Linux is installed virtual machine servers or virtual machines such as VMware, Hyper-V, XenServer, or KVM by using methods provided by each OS or virtual infrastructures. If the objects are resource pools or sub resource pools in SystemProvisioning, the data are collected by using APIs provided by SystemProvisioning. If the objects are LUNs in NEC Storage, the data are collected by using SigmaSystemCenter Cooperation Script provided by NEC Storage.

If objects are SigmaSystemCenter Managed Objects, you can collect the Statistic Information of machine numbers from each tenant, category, or group in the operation view of SigmaSystemCenter Web Console; or all running machines. The data are collected via the API of SystemProvisioning. In addition to above, you can collect the data by performing a script in a management server or managed object.

You can efficiently keep the collected performance data for a long period because System Monitor - Performance Monitoring Services aggregates the data as "summary data" and accumulates those aggregated data.

System Monitor - Performance Monitoring Services provides graph view for the collected performance data which makes it easy to keep track of the performance status of the system.

For systems with large-scale configurations, the performance status of the entire system can be followed at a glance by using the function that grouped managed objects and graphs the performance status of each group. You can view the graph of the performance status on the SigmaSystemCenter Web console or the SystemMonitor management console. Performance problems (such as high load) can be discovered quickly by graphically displaying and monitoring the performance status of the system in real time. It is also possible to display performance data that has been collected in the past again. This enables the operational status of the system in the past to be checked.

The threshold monitoring feature can automatically compare the collected performance data and an arbitrary threshold, and, in case of exceeding threshold, it can log unusual loads on the monitored machine to the event log or notify SystemProvisioning of it. In notifying SystemProvisioning, SigmaSystemCenter can run the policy action in response to the notified events.

Function Overview of System Monitor - Performance Monitoring Services

5

To make the VM Optimized Placement feature available, which is the feature for load balancing or power saving in the virtual environment of SigmaSystemCenter, you must use the threshold monitoring feature of System Monitor - Performance Monitoring Services. Note that the threshold monitoring feature is not available if the managed objects are resource pools, LUNs, or SigmaSystemCenter Managed Objects.

You can use the monitoring profile settings from the SigmaSystemCenter Web console to configure collecting performance data or thresholds on System Monitor - Performance Monitoring Services. However, if the configuration requires any special customization, use the SystemMonitor management console.

1 Functions


1.2. Basic Configuration of System Monitor - Performance Monitoring Services

System Monitor - Performance Monitoring Services is one of the SigmaSystemCenter products, and it consists of a "Performance Monitoring Service function" that collects performance data and a "management console function" that is the user interface for using the Performance Monitoring Service. Typically, System Monitor - Performance Monitoring Services is used in combination with SystemProvisioning.

1 minute interval

5 minutes 15 minutes

1 day 1 hour

Aggregat-ing

System Monitor - Performance Monitoring

Services Management console

System Monitor - Performance Monitoring Services

Performance Monitoring Service

Applying configuration information (such as a monitoring profile)

Making settings

Displaying graphs

Saved for 3 days

1 week 1 month 3 months 5 years

Accumulates performance data

Management server

Obtaining the data for Web graph display

Notifying exceeding threshold

SystemProvisioning

Web graph display Obtaining

performance data

Managed machines

Aggrega- ting

Aggrega- ting

Aggrega-ting

Obtaining performance data of virtual machines in Hyper-V, KVM, or Xen; the current power information of physical machines; the performance data of resource pools; and the statistic information of SigmaSystemCenter Managed Objects.

Running policy actions

Setting a monitoring profile

Basic Configuration of System Monitor - Performance Monitoring Services

7

◆ The Performance Monitoring Service This function resides on the server, and acquires the performance data of managed objects. The performance data is collected and stored in a database. Keeping the collected performance data for a long period requires a large data space in a database. However, System Monitor - Performance Monitoring Service can aggregate the data to one collection of the data in a longer interval and accumulate the data preventing the data area from filling rapidly. The machine where the Performance Monitoring Service runs is called the "management server" and the object whose performance is monitored should be called the "managed object." The Performance Monitoring Service runs in the background as a Windows service and starts automatically when the OS starts.

◆ The Management Console This is one of the user interfaces for using the Performance Monitoring Service. Settings for the Performance Monitoring Service, such as which managed objects are monitored and which performance information is collected, are performed from the management console. The management console can also graphically display performance data. If you intend to use not System Monitor - Performance Monitoring Services but the SigmaSystemCenter features to manage a managed object, use the SigmaSystemCenter Web console (described later) instead of the System Monitor - Performance Monitoring Services management console.

The management console is installed on the management server along with the Performance Monitoring Service. Users connect to the Performance Monitoring Service by starting the management console on the management server. More than one management console can connect to the same Performance Monitoring Service at the same time. In addition, central management is available for multiple management servers from one management console. To implement performance monitoring on large-scale systems, separate managed objects into the appropriate units and prepare a management server for each.

1 Functions


◆ SystemProvisioning/SigmaSystemCenter Web console

SystemProvisioning is a core product of SigmaSystemCenter and performs configuration management and provisioning for managed objects in SigmaSystemCenter. To perform operations for configuring or provisioning managed objects, use the SigmaSystemCenter Web console. You can use the monitoring profile information (the set of performance indicator settings and thresholds monitoring settings) on the SigmaSystemCenter Web console to configure a managed object of System Monitor - Performance Monitoring Services and a performance indicator to be collected.

System Monitor - Performance Monitoring Services applies the monitoring profile information and the configuration information of SystemProvisioning to itself at the timing of execution of reflecting the configuration information of SystemProvisioning. This allows System Monitor - Performance Monitoring Services to automatically start performance monitoring for the managed object that you intend to register and allows to display the collected performance data in graph on the SigmaSystemCenter Web console.

Monitoring Target Range of Management Console

Management server1


Services

Managed machines

System Monitor - Performance

Monitoring Service

Management console

Management server2


Monitoring Services

Management server3


Services

Basic Configuration of System Monitor - Performance Monitoring Services

9

System Monitor - Performance Monitoring Services can notify SystemProvisioning of performance problems detected by it such as exceeding thresholds. This makes it possible to automatically start the policy action configured on SystemProvisioning. One SystemProvisioning can work with more than one System Monitor – Performance Monitoring Services. In performance monitoring in the large-scale system environment, managed objects can be grouped by group or model in SystemProvisioning and each managed object can be monitored on a management server. In this case, you can view the performance information for the managed object in graph on the Web console of each management server.

Operating Systems Supported operating systems for the management server and managed machines are as follows:

Supported operating systems

Management server Windows Server 2008 R2 Standard Edition SP1 Windows Server 2008 R2 Enterprise Edition SP1 Windows Server 2008 R2 Datacenter Edition SP1 Windows Server 2012 Standard Edition Windows Server 2012 Datacenter Edition Windows Server 2012 R2 Standard Edition Windows Server 2012 R2 Datacenter Edition Windows Server 2016 Standard Edition Windows Server 2016 Datacenter Edition

Managed machines Windows Server 2008 Standard Edition (including SP2) Windows Server 2008 Enterprise Edition (including SP2) Windows Server 2008 Standard x64 Edition (including SP2) Windows Server 2008 Enterprise x64 Edition (including SP2) Windows Server 2008 Datacenter x64 Edition (including SP2) Windows Server 2008 R2 Standard Edition (including SP1) Windows Server 2008 R2 Enterprise Edition (including SP1) Windows Server 2008 R2 Datacenter Edition (including SP1) Windows Server 2012 Standard Edition Windows Server 2012 Datacenter Edition Windows Server 2012 R2 Standard Edition Windows Server 2012 R2 Datacenter Edition Windows Server 2016 Standard Edition Windows Server 2016 DataCenter Edition Windows Vista Business Edition (including SP1, SP2) Windows Vista Enterprise Edition (including SP1, SP2) Windows Vista Ultimate Edition (including SP1, SP2) Windows 7 Professional Edition (including SP1) Windows 7 Enterprise Edition (including SP1) Windows 7 Ultimate Edition (including SP1) Windows 8 Pro Edition Windows 8 Enterprise Edition Windows 8.1 Pro Edition Windows 8.1 Enterprise Edition

1 Functions


Supported operating systems Windows 10 Red Hat Enterprise Linux 5, 6 and 7 Server (including x64) VMware ESXi 5.0, 5.1, 5.5, 6.0, 6.5 Citrix XenServer 6.0 Windows Server 2008 R2 Standard Hyper-V (including SP1) Windows Server 2008 R2 Enterprise Hyper-V (including SP1) Windows Server 2012 Hyper-V Windows Server 2012 R2 Hyper-V Red Hat Enterprise Linux 6.8 KVM Red Hat Enterprise Linux 7.3 KVM Guest operating systems on VMware ESXi Guest operating systems on Citrix XenServer Guest operating systems on Hyper-V Guest operating systems on KVM

Notes: ▪ When Windows Vista or Windows Server 2008 is running on the managed machine, it may take longer time to collect performance data because of the internal behavior of Windows. For detail, see "9.5 What to do if Performance Data Collecting is delayed" ▪ Regarding Red Hat Enterprise Linux 5, 6, 7 Server, these versions listed below are evaluated as a managed machine:

▪ The versions of 5.11, 6.8 and 7.3. For the later version, please confirm our latest evaluation status. ▪ Guest operating systems supported by VMware ESXi, Citrix XenServer, Hyper-V, and KVM are supported only if they are supported as operating systems for managed machines in System Monitor - Performance Monitoring Services. ▪ Management servers support only the Full Installation option. In this reason, it does not support the Server Core option, though this is the default install option for Windows Server 2016.

Collected Performance Data

11

1.3. Collected Performance Data System Monitor - Performance Monitoring Services periodically collects performance data from the managed objects. Collected Performance Indicators can be specified for each SystemMonitor management server, for each group or for each object. If they are specified for a management server, they are shared with all managed objects that are managed objects of the management server. You can configure to collect performance data for the managed object on the monitoring profile of SigmaSystemCenter or on the System Monitor – Performance Monitoring Services management console. Configuring on the monitoring profile of SigmaSystemCenter allows you to configure the managed object registered by reflecting the configuration information of SystemProvisioning. The specified performance indicator on the monitoring profile of SigmaSystemCenter is automatically applied to System Monitor - Performance Monitoring Services at the timing of reflecting the configuration information of SystemProvisioning. The configuration procedures of monitoring profiles are differ depending on managed objects:

◆ For machines, you can configure monitoring profiles in the Performance Monitoring tab (SigmaSystemCenter Web Console > an operation group, model, or host > Property). For the details, refer to, such as 4.11.3, "How to Create a Monitoring Profile" and 5.5.15, "Configuring Settings on the Performance Monitor Tab" in NEC SigmaSystemCenter Configuration Guide.

◆ For resource pools, the collect performance data setting is enabled by default. If you need to change the location of a System Monitor - Performance Monitoring Services server from the default, edit the following registry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\SysmonPerf

\ResourcePool For the details, refer to 4.11.3, "How to Create a Monitoring Profile" and 5.10.6, "Storing the Historical Data of Resource Pools" in NEC SigmaSystemCenter Configuration Guide.

◆ For LUNs, the collect performance data setting is disabled by default. To enable the setting, configure the setting in the following registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\SysmonPerf \iStorage

◆ For SigmaSystemCenter Managed Objects, the collect Statistic Information setting is enabled by default. If you need to change the location of a System Monitor - Performance Monitoring Services server from the default, edit the following registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\SysmonPerf \SSCManagedObject Note that this registry format is the same as the one of resource pools or LUNs.

For how to configure it on the management console of System Monitor - Performance Monitoring Services, see 4.2.2, "How to Specify Collecting Data Settings."

1 Functions


1.3.1. Types of Performance Indicators and Collecting Intervals

The Performance Indicators consist of "Resource", "Performance index" and "Instance". "Resource" is the target resource of the Performance Indicators, and includes CPU, physical disk and memory. "Performance index" is the type of data collected, and indicates CPU usage and disk transfer rates. "Instance" identifies a particular measurement object in situations where a resource contains multiple measurement objects. "Instance" is unique to "Performance index". The settings for "Instance" cannot be changed.

Performance data is collected from managed objects, the virtual infrastructures of virtual machines, or SystemProvisioning at regular intervals. These intervals are called "collecting intervals", and can be specified individually for each Performance Indicator item or collectively for all Performance Indicator items. Performance Indicators that have been configured to collect data, begin collecting from managed objects, the virtual infrastructures of virtual machines, or SystemProvisioning automatically when the Performance Monitoring Service starts.

1.3.2. Built-in Performance Indicator

System Monitor - Performance Monitoring Services comes with Built-in Performance Indicators that are common to all systems. Some typical Built-in Performance Indicator items are set up as default settings for each management server when System Monitor - Performance Monitoring Services is installed. With built-in performance indicators, the individual data per device in the managed object cannot be collected because built-in performance indicators collect performance data per managed object basis. If you need to collect individual performance data per device basis, use custom performance indicators instead.

For example, the performance data obtained with Network Packet Transfer Rate (Bytes/sec) is the total rate of all packets transferred through network adapters if the Windows machine of a managed object has more than one network adapters.

◆ Standard Performance Indicator With accessing managed machines directly, these indicators collect performance data from machines. The collection methods differ depending on the OS types or virtualization software of managed objects as the following:

For Windows In a usual Windows machine, the information is collected by using the APIs of NET Framework. In a Hyper-V server environment, Disk Space (MB) or Disk Space Ratio (%) is collected by using WMI.

For Linux The information is collected by performing a command in the managed machine via an SSH connection.

For VMware ESXi


13

The information is collected by using VMware vSphere API.

For Xen The information is collected by using Xen API.

Resource Performance indicator

ID Explanation

Managed machine OS

Window

s

Linux

ESXi

Xen

Hyper-V

KVM

CPU CPU Usage (%) 1 CPU Usage (%) is the percentage of elapsed time that the processor spends to execute a non-Idle thread.

x x x x x x

CPU System Usage (%)

2 CPU System Usage (%) is the percentage of elapsed time that the process threads spent executing code in privileged mode.

x x - - - x

CPU User Usage (%)

3 CPU User Usage (%) is the percentage of elapsed time the processor spends in the user mode.

x x - - - x

CPU Usage (MHz) 4 In case that the OS of the monitored machine is other than ESXi, CPU Usage (MHz) is the amount of used CPU resource that is calculated by CPU Usage (%) × the count of processors × CPU frequency. Getting the information of the amount of processor or frequency is required to cooperate with SystemProvisioning.

x x x x x x

Disk Disk Transfer Rate (Bytes/sec)

21 Disk Transfer Rate (Bytes/sec) is the rate bytes are transferred to or from the disk during write or read operations.

x x x - x x

Disk IO Count (IO/sec)

22 Disk IO Count (IO/sec) is the rate of read and write operations on the disk.

x x x - x x

Disk Read Transfer Rate (Bytes/sec)

23 Disk Read Transfer Rate (Bytes/sec) is the rate at which bytes are transferred from the disk during read operations.

x x x - x x

Disk Read Count (IO/sec)

24 Disk Read Count (IO/sec) is the rate of read operations on the disk.

x x x - x x

Disk Write Transfer Rate (Bytes/sec)

25 Disk Write Transfer Rate (Bytes/sec) is the rate at which bytes are transferred to the disk during write operations.

x x x - x x

Disk Write Count (IO/sec)

26 Disk Write Count (IO/sec) is the rate of write operations on disk.

x x x - x x

1 Functions


Disk Space (MB) 27 Disk Space (MB) displays the unallocated space, in megabytes, on the disk drive. One megabyte is equal to 1,048,576 bytes.

x x x x x x

Disk Space Ratio (%)

28 Disk Space Ratio (%) is the percentage of total usable space on the whole disk drive that was free.

x x x x x x

Network Network Packet Transfer Rate (Bytes/sec)

41 Network Packet Transfer Rate (Bytes/sec) is the rate at which data is transmitted and received across the all physical NICs. The value is total of Network Packet Reception Rate (Bytes/sec) and Network Packet Transmission Rate (Bytes/sec).

x x x x x x

Network Packet Reception Rate (Bytes/sec)

42 Network Packet Reception Rate (Bytes/sec) is the total rate at which data is received across the all physical NICs.

x x x x x x

Network Packet Transmission Rate (Bytes/sec)

43 Network Packet Transmission Rate (Bytes/sec) is the total rate at which data is transmitted across the all physical NICs.

x x x x x x

Memory Physical Memory Space (MB)

61 Physical Memory Space (MB) is the amount of physical memory, in Megabytes, immediately available for allocation to a process or for system use.

x x x x x x

Physical Memory Space Ratio (%)

62 Physical Memory Space Ratio (%) is the percentage of the available memory size to the installed physical memory size that is calculated by Physical Memory Space (MB) / the installed physical memory size × 100.

x x x x x x

Notes: ▪ About CPU Usage (MHz), heed the following descriptions. 1. The OS of the managed machine is other than ESXi, CPU Usage (MHZ) is available only for the physical machine whose configuration information is applied from SystemProvisioning. 2. Physical machines of KVM、Windows and Linux must be automatically registered to NEC ESMPRO Manager by SystemProvisioning. 3. CPU Usage (MHz) of physical machines of Windows and Linux does not take the amount of Core and Hyper threading into account. The information which is acquired from ESMPRO/ServerManager about the amount of CPU of physical machines of Windows and Linux is only the amount of Socket. Because the amount of Core cannot be acquired.

▪ When the Dynamic Memory feature of the managed virtual machines on Hyper-V is enabled, the amount of Physical Memory Space Ratio (%) for these virtual machines may be incorrect.


15

▪ Physical Memory Space Ratio (%) for a managed Windows machine/Hyper-V host is available only for the machine whose configuration information is applied from SystemProvisioning. Also, physical machines on Windows must be automatically registered to NEC ESMPRO Manager by SystemProvisioning.

▪ The performance data collected from Citrix XenServer consists of data obtained in the last several seconds before the performance data is collected. ▪ In the KVM managed machine, each value of Disk Space (MB) and Disk Space Ratio (%) is calculated as the total of the all storage pools on the KVM host. If multiple storage pools share the same disk space, the Disk Space (MB) and Disk Space Ratio (%) are incorrectly calculated because the shared disk spaces are redundantly calculated. When using storage pools, avoid that they share the same disk spaces. For example, the following use cases may cause issues in calculation of Disk Space and Disk Space Ratio: 1. Multiple directories on the same local file system are configured as individual storage pools.

2. Multiple directories on the same file system in the same NFS server are configured as individual storage pools.

◆ Performance Indicator for Virtual Machine These indicators collect performance data only for virtual machines. The collection methods differ depending on the Virtualization Platforms, in which managed objects reside, as the following:

For VMware ESXi The information is collected via VMware ESXi.

Note that you must include VMware ESXi, in which managed virtual machines reside, to managed objects. Also, these servers and virtual machines must be registered in a managed server with running status in the same SigmaSystemCenter because when collecting performance data for virtual machines via VMware ESXi, the information of VMware ESXi itself is collected via SystemProvisioning.

Except for VMware In Hyper-V, KVM, and Citrix XenServer, the information is collected via SystemProvisioning. Note that managed virtual machines must be applied to System Monitor - Performance Monitoring Services by using the "Applying SystemProvisioning Configuration" feature. In this reason, the managed machines must be registered in SigmaSystemCenter with running status before collecting performance data.

1 Functions



ID Explanation

Virtualization Platform

ESXi

Xen

Hyper-V

KVM

CPU Guest CPU Usage (%)

11 Guest CPU Usage (%) is the percentage of the total CPU resource that actively used by the VM to the available CPU resource for the VM.

x x x x

Guest CPU Usage (MHz)

12 Guest CPU Usage (MHz) is the total CPU resource that actively used by the VM.

x x x x

Host CPU Usage (%)

13 Host CPU Usage (%) is the percentage of the VM server CPU resource that actively used by the VM to the total CPU resource of the VM server.

x - x x

Host CPU Usage (MHz)

14 Host CPU Usage (MHz) is the VM server CPU resource that actively used by the VM.

x - x x

Disk Guest Disk Transfer Rate (Bytes/sec)

31 Guest Disk Transfer Rate (Bytes/sec) is the rate at which data is transferred to or from the virtual disk on the VM during write or read operations.

x - x x

Guest Disk IO Count (IO/sec)

32 Guest Disk IO Count (IO/sec) is the I/O count per second when data is transferred to or from the virtual disk on the VM during write or read operations.

x - - -

Guest Disk Read Transfer Rate (Bytes/sec)

33 Guest Disk Read Transfer Rate (Bytes/sec) is the rate at which data is transferred from the virtual disk on the VM during read operations.

x - - -

Guest Disk Read Count (IO/sec)

34 Guest Disk Read Count (IO/sec) is the I/O count per second when data is transferred from the virtual disk on the VM during read operations.

x - - -

Guest Disk Write Transfer Rate (Bytes/sec)

35 Guest Disk Write Transfer Rate (Bytes/sec) is the rate at which data is transferred to the virtual disk on the VM during write operations.

x - - -

Guest Disk Write Count (IO/sec)

36 Guest Disk Write Count (IO/sec) is the I/O count per second when data is transferred to the virtual disk on the VM during write operations.

x - - -

Guest Disk Usage (MB)

37 Guest Disk Usage (MB) is the datastore size consumed by the VM. If the target VM is running on VMware ESXi, this is the used space of the virtual disk allocated to the VM. This information is a guest OS information collected via VMwareTools and defines the sum of all LogicalDisk usage in the OS of the virtual machine.

x x x x


17

Guest Disk Usage (%)

38 Guest Disk Usage (%) is the percentage of the datastore size consumed by the VM to the size of the allocated virtual disk. If the target VM is running on VMware ESXi, this is the percentage of the used space of the virtual disk allocated to the VM. This information is a guest OS information collected via VMwareTools and defines the proportion of the sum of all LogicalDisk sage per the sum of all LogicalDisk sizes in the OS of the virtual machine.

x x x x

Network Guest Network Transfer Rate (Bytes/sec)

51 Guest Network Transfer Rate (Bytes/sec) is the rate at which data is transmitted and received across the all virtual NICs on the VM.

x - x x

Memory Guest Memory Usage (%)

71 - If the target VM is running on VMware ESXi, this is the percentage of the size of the VM server memory used actively by the VM. - If the target VM is running on Hyper-V, this is the percentage of current used memory of the VM to the total physical memory assigned to the VM. The value of following "Host Memory Usage (MB)" is used for "the total physical memory assigned to the VM." - If the target VM is running on Xen, this is the percentage of the memory size used by the VM to the memory size allocated to the VM.

x x x -

Guest Memory Usage (MB)

72 - If the target VM is running on VMware ESXi, this is the size of the VM server memory actively used by the VM. - If the target VM is running on Hyper-V, this is the size of current used memory of the VM. - If the target VM is running on Xen, this is the memory size used by the VM.

x x x -

Host Memory Usage (%)

73 Host Memory Usage (%) is the percentage of the size of the VM server memory consumed for the VM to the total memory size of the VM server.

x x x -

Host Memory Usage (MB)

74 Host Memory Usage (MB) is the size of the VM server memory consumed for the VM.

x x x -

Notes: ▪ Collecting the performance information of a virtual machine is available only for the virtual machine registered by the SystemProvisioning configuration information reflecting feature. ▪ When the managed machine is a virtual machine running on a VMware ESXi and performance data for Guest Disk Usage (%) or Guest Disk Usage (MB) is collected, it is necessary that VMware Tools installed and is running on the managed virtual machine. In case that VMware Tools was not running on the virtual machine, errors will occur in collecting performance data.

▪ To collect performance data for Guest Memory Usage (%) or Guest Memory Usage (MB) from a virtual machine running on Hyper-V, Dynamic Memory for the virtual machine must be enabled.

1 Functions


▪ The performance data for a virtual machine collected from Citrix XenServer, Hyper-V or KVM are the data obtained in the last several seconds before the performance data is collected regardless of the collecting interval.

◆ Performance Indicator for Physical Machine These are performance indicators only for a physical machine.

The information is collected from SystemProvisioning. It is necessary for collecting performance data for this indicator that the configuration information of the managed physical machine is applied from SystemProvisioning. And it is also necessary that configurations to make the OOB Management feature available for the monitored machine on SigmaSystemCenter.


ID Explanation

Power Supply

Current Power (W) 101 Current Power (W) is the current power consumption of a physical machine.

◆ Performance Indicator for Logical Disk on NEC Storage These are performance indicators for logical disk on NEC Storage disk array equipment.

In System Monitor - Performance Monitoring Services, the information is collected by using SigmaSystemCenter Cooperation Script contained in a managed server.

Resource Performance indicator Explanation

Other

LUN IOPS Obtain the number of times of the request for input-output per

unit time. This is calculated by measuring the number of times

of the external I/O first and then the result is divided by the time

length of measuring intervals.

LUN Average Transfer

Length (KB)

Obtain the average input-output data length per request for

input-out. This is calculated by measuring the sum of the

external forwarding data in unit measurement duration and the

number of times of the external I/O first. Then the former is

divided by the latter.

LUN Transfer Rate

(MB/sec)

Obtain the average forwarding rate which is executed in answer

to the request for input-output. This is calculated by measuring

the sum of the external data forwarding resources first and the

result is divided by the time length of measuring intervals.

LUN Average Response

Time (micro sec)

Obtain the average response time for the request for

input-output. This is calculated by measuring the sum of the

external response time in unit measurement duration and the


19

number of times of the external I/O first. Then the former is

divided by the latter.

The performance indicator listed above is defined as a built-in local script. The script can collect performance data of logical disk on NEC Storage disk array equipment in cooperation with NEC Storage Manager and NEC Storage PerformanceMonitor. To collect performance data, the following settings are needed.

• NEC Storage Manager and NEC Storage PerformanceMonitor environment, which are cooperated with SigmaSystemCenter Cooperation Script, are needed.

• In the management server of SigmaSystemCenter, you must activate the collect performance data of NEC Storage by editing the registry and configure a monitoring profile.

• The monitoring target disk array and logical disk must be managed on SigmaSystemCenter. Also, needs to be monitored in System Monitor - Performance Monitoring Service by applying the System Configuration Information of SigmaSystemCenter.

• Obtain SigmaSystemCenter Cooperation Script from NEC Storage Manager or NEC Storage PerformanceMonitor. And install it on the management server of System Monitor-Performance Monitoring Service which executing the script to collect performance data.

◆ Performance Indicator for Resource Pools These indicators are used for logging and saving the managed resource pools and sub resource pools information of SystemProvisioning. The information is collected from SystemProvisioning.


ResourcePool

VMNumber.Capacity The sum of virtual machines can be created in data

stores connected to virtual machine servers that reside

in the managed resource pools.

VMNumber.Consumed The sum of virtual machines created by the managed

resource pools.

VMNumber.Consumed (%) The proportion of created virtual machines per the sum

of virtual machines can be created.

VMNumber.Unused The sum of virtual machines can be created is displayed

as the number of unused virtual machines.

VMNumber.Unused (%) The proportion of unused virtual machines per the sum


VMNumber.Reserved The sum of upper limit numbers specified by sub

1 Functions


resource pools is displayed as the number of reserved

virtual machines.

VMNumber.Reserved (%) The proportion of reserved virtual machines per the sum


VMNumber.ActuallyConsumed The number of activated virtual machines that reside in

tenants or groups in the managed resource pools.

VMNumber.ActuallyConsumed

(%)

The proportion of activated virtual machines that reside

in tenants or groups in the managed resource pools per

the sum of virtual machines can be created.

CPU.Capacity (MHz) The sum of CPU frequency values of virtual machine

servers that reside in the managed resource pools.

CPU.Consumed (MHz) The sum of CPU resources allocated to tenants or

groups in the managed resource pools.

CPU.Consumed (%) The proportion of the sum of CPU resources allocated

to tenants or groups in the managed resource pools per

the sum of CPU frequency values of virtual machine

servers that reside in the resource pools.

CPU.Unused (MHz) The sum of CPU resources can be allocated to tenants

or groups in the managed resource pools is displayed

as the number of unused CPU resources.

CPU.Unused (%) The proportion of unused CPU resources per the sum of

CPU frequency values of virtual machine servers that

reside in the managed resource pools.

CPU.Reserved (MHz) The sum of upper limit numbers specified by sub


virtual machines.

CPU.Reserved (%) The proportion of reserved virtual machines per the sum

of CPU frequency values of virtual machine servers that

reside in the managed resource pools.

CPU.ActuallyConsumed (MHz) The sum of actual CPU consumption values of virtual

machines.

CPU.ActuallyConsumed (%) The proportion of the sum of actual CPU consumption

values of virtual machines per the sum of CPU


21

frequency values of virtual machine servers that reside

in the managed resource pools.

vCPUNumber.Capacity This value is calculated from the specified vCPU Unit

and virtual machine server information. It is displayed as

Capacity.

E.g.,

- When the frequency is selected as the vCPU unit:

vCPU Capacity= CPU Capacity/ vCPU Unit

- When the number of vCPU per core is selected as the

vCPU unit:

vCPU Capacity = Total CPU cores of the virtual

machine servers * vCPU Unit

vCPUNumber.Consumed The sum of the number of vCPUs allocated to tenants or

groups in the managed resource pools. It is displayed

as Consumed.

vCPUNumber.Consumed (%) The proportion of the Consumed value per the Capacity

value.

vCPUNumber.Unused The value calculated by subtracting the Consumed

value from the Capacity value. It is displayed as

Unused.

vCPUNumber.Unused (%) The proportion of the Unused value per the Capacity

value.

vCPUNumber.Reserved The sum of upper limit numbers specified by sub


virtual machines.

vCPUNumber.Reserved (%) The proportion of the Reserved value per the Capacity

value.

vCPUNumber.ActuallyConsumed The sum of the number of vCPUs of only activated

virtual machines that reside in tenants or groups in the

managed resource pools.

vCPUNumber.ActuallyConsumed

(%)

The proportion of the sum of the number of vCPUs of

only activated virtual machines that reside in tenants or

groups in the managed resource pools per the Capacity

1 Functions


value.

Memory.Capacity (MB) The sum of the memory size of virtual machine servers

that reside in the managed resource pools.

Memory.Consumed (MB) The sum of the memory size of virtual machines

allocated to tenants or groups in the managed resource

pools.

Memory.Consumed (%) The proportion of the sum of the memory size of virtual

machines allocated to tenants or groups in the managed

resource pools per the sum of the memory size of virtual

machine servers that reside in the managed resource

pools.

Memory.Unused The value calculated by subtracting the sum of the

memory size of virtual machines allocated to tenants or

groups in the managed resource pools from the sum of

the memory size of virtual machine servers that reside

in the managed resource pools. It is displayed as

Unused.

Memory.Unused (%) The proportion of the Unused value per the sum of the

memory size of virtual machine servers that reside in

the managed resource pools.

Memory.Reserved (MB) The sum of upper limit numbers specified by sub


virtual machines.

Memory.Reserved (%) The proportion of the number of reserved virtual

machines per the sum of the memory size of virtual


pools.

Memory.ActuallyConsumed (MB) The sum of actual memory usage size of virtual


pools.

Memory.ActuallyConsumed (%) The proportion of the sum of actual memory usage size

per the sum of the memory size of virtual machine

servers that reside in the managed resource pools.


23

Datastore.Capacity (GB) This value is calculated by multiplying the size of

untagged data stores connected to virtual machine

servers that reside in the managed resource pools and

the upper limit usage (%), and then summing it. It is

displayed as Capacity.

Datastore .Consumed (GB) The sum of the data store size of virtual machines

allocated to tenants or groups in the managed resource

pools. It is displayed as Consumed.

Datastore .Consumed (%) The proportion of the Consumed value per the Capacity

value.

Datastore .Unused (GB) The value calculated by subtracting the Consumed

value from the Capacity value. It is displayed as

Unused.

Datastore .Unused (%) The proportion of the Unused value per the Capacity

value.

Datastore .Reserved (GB) The sum of upper limit numbers specified by sub


virtual machines.

Datastore .Reserved (%) The proportion of the number of reserved virtual

machines per the Capacity value.

Datastore .ActuallyConsumed

(GB)

The sum of actual disk usage size of untagged data

stores that reside in the managed resource pools.

Datastore .ActuallyConsumed

(%)

The proportion of the sum of actual disk usage size of

untagged data stores that reside in the managed

resource pools per the Capacity value.

Notes: ▪ Sub pools cannot collect from CPU.Capacity (MHz) to CPU.ActuallyConsumed (%). ▪ For the details of each performance information, refer to 4.6.6, "VM Number/CPU/vCPU/Memory/Datastore/LUN of Root Resource Pool" in NEC SigmaSystemCenter Reference Guide.

1 Functions


◆ Performance Indicator for SigmaSystemCenter Managed Object This performance indicator is for collecting and accumulating the Statistic Information of machine numbers. The Statistic Information is collected from each tenant, category, or group in the operation view of SigmaSystemCenter Web Console; or all running machines (see the below).

• The number of machines • The number of machines per machine type • The number of machines per machine status

• The number of failure machines The details of the performance indicator are the following:


SSC

Statistics

Machine.Count The total number of running machines

Machine.Physical.Count The total number of running machines that the

machine type is Physical

Machine.VMServer.Count The total number of running machines that the

machine type is VM Server

Machine.VM.Count The total number of running machines that the

machine type is VM

Machine.PowerStatus.Running.Count The total number of running machines that the

power status is Running

Machine.PowerStatus.On.Count The total number of running machines that the

power status is On

Machine.PowerStatus.Off.Count The total number of running machines that the

power status is Off

Machine.PowerStatus.Suspend.Count The total number of running machines that the

power status is Suspend

Machine.PowerStatus.Unknown.Count The total number of running machines that the

power status is Unknown

Machine.OSStatus.On.Count The total number of running machines that the

OS status is On

Machine.OSStatus.Off.Count The total number of running machines that the

OS status is Off

Machine.OSStatus.Unknown.Count The total number of running machines that the


25

OS status is Unknown

Machine.HardwareStatus.Unknown.Count The total number of running machines that the

hardware status is Unknown

Machine.HardwareStatus.Ready.Count The total number of running machines that the

hardware status is Ready

Machine.HardwareStatus.Faulted.Count The total number of running machines that the

hardware status is Faulted

Machine.HardwareStatus.Degraded.Count The total number of running machines that the

hardware status is Degraded

Machine.Failure.Count The total number of failure machines

1.3.3. Custom Performance Indicator

System Monitor-Performance Monitoring Service can collect the performance data of performance indicators which are not default built-in performance indicators by defining them as custom performance indicators. The following describes about the type of the custom performance indicator that you can define in System Monitor-Performance Monitoring Services.

◆ Performance counters • For a Windows managed machine

You can define a custom performance indicator by specifying the same categories, counters, and instances for the Windows managed machine as those in Windows Performance Monitor. The custom performance indicator enables System Monitor - Performance Monitoring Services to collect the same performance information of the Windows machine as that collected by Windows Performance Monitor.

• For a VMware ESXi virtual machine server / virtual machine When the managed machine is the VMware ESXi virtual machine server or virtual machine, you can define the custom performance indicator by specifying "metric group", "counter", and "object" like you do in the Customize Performance Chart dialog box in VMware vSphere Client. The custom performance indicator enables System Monitor - Performance Monitoring Services to collect the same performance information of the VMware ESXi virtual machine server or virtual machine as that collected by vSphere Client. With provided counters, you can collect the information of each data store in a VMware ESXi virtual machine server. The information includes size, available size, and used size of each data store. To collect the information:

(1) On the Performance Indicator Settings dialog, select Datastore in Metric Group;

1 Functions


(2) Select datastore size, datastore free, and datastore usage in Counter List; and then select Datastore in Object List.

Note: In System Monitor-Performance Monitoring Service, the displayed value of VMware ESXi VM servers or VMs may differ with the displayed values in vSphere Client because in the former, the values are displayed without any modification after obtaining the values via the vSphere API.

For example, in System Monitor-Performance Monitoring Service, the displayed value of performance indicators with “percent” unit are 100 times larger than the displayed values in vSphere Client.

For details, see "Counter, Rollup (counter)" in Appendix D Performance Counter Information of VMware ESXi.

◆ User scripts The user script has a capability to collect its output as a performance data by executing an arbitrary script. The user script has two types: one is a remote user script which is executed on a monitored machine; another is a local user script which is executed on a management server.

• Remote user script

In a Windows / Linux managed machine, you can create custom performance indicators by specifying a script on the managed machine. When collecting the performance data, System Monitor - Performance Monitoring Services remotely connects to the managed machine using SSH, and executes the script on the managed machine at every collecting interval. Then, System Monitor - Performance Monitoring Services extracts the results from the [standard output] information to obtain the performance data.

When creating the custom performance indicator, you must specify the name of the script file on the managed machine as the executing string. You can add the string "remote+ssh://" before the executing string. Alternatively, you can specify the executing the string directly. Use the following execution examples by script type as a reference. We recommend that you use the full path to specify the script path to avoid execution errors.

For Windows In Windows managed machines, you can specify scripts such as batch files, Windows Script Host (WSH) and PowerShell on the managed machine. You can also run executable programs directly. Batch file

Specify the batch file path. E.g.) remote+ssh://cmd /c “C:\PerformanceMonitor\Script\test.bat”

WSH (Windows Script Host) script Specify the WSH script execution program and the path of the WSH file. E.g.) remote+ssh://CScript.exe //nologo C: \PerformanceMonitor\Script\test.vbs

PowerShell script


27

Specify the PowerShell script execution program, the path of the Power Shell script, and the "< /dev/null" string that corresponds to the operation of pressing the enter key. E.g.) remote+ssh://PowerShell.exe –File "C: \PerformanceMonitor\Script\test.ps1" </dev/null

For Linux Specify the Linux shell execution program and the path of the Linux shell script. E.g.) remote+ssh://sh /PerformanceMonitor/test.sh

System Monitor - Performance Monitoring Services gets the performance data and error information from the result of script execution as the information of the standard output. So, the script must output the result to the standard output in the following formats:

When the script execution succeeded Output the result to the standard output in the "@metric number [name=Performance Indicator] [datetime=Collection time]" format. You can write a remote user script so that it outputs the performance data for multiple performance indicators to a same script. In this case, allow the script to output multiple lines of @metric.

The number above indicates performance data. When specifying number, use integers, fractions, and floats. The name outputs the title for a custom performance indicator defined in System Monitor - Performance Monitoring Services. If you make the script output several lines of @metric, you must specify name to be output to the execution result to identify the performance indicator. If the script outputs only one "@metric" line, you can omit to specify name. In this case, the output is collected as the data of the performance indicator which sets the script to be executed. For datetime, specify the time when the performance data is collected. System Monitor - Performance Monitoring Services handles the datetime output as the data collection time. datetime is optional. If it is omitted, the time when the script was executed by System Monitor - Performance Monitoring Services is considered as the data collection time. For the format in which datetime is specified, see the description later. The following shows an output example:

echo @metric 1.1E+2 name=CustomPerformance datetime="2014/01/01 09:00:00"

When the script execution failed

Output the result as the error code to the standard output in the "@metric [name=Performance Indicator] [error=Error Message] [errorcode=Error Code]" format. Only integers are available for a numeric part of the error code. The Error and Error Code are optional.

Provide the script with the error, which indicates the error message when the script fails, to output it. Output the errorcode, which is an arbitrary code to categorize errors in a script, in an integer.

1 Functions


For example, specify "echo @metric name=CustomPerformance error=Failed to execute the command errorcode= -1" to output the error code.

If the script outputs multiple "@metric" lines, you must specify name to be output to the execution result to identify the performance indicator. If the script outputs only one "@metric" line, you can omit to specify the value "name." In this case, the output is handled as the error information of the custom indicator which sets the script to be executed. For the Windows monitored machine, use the default encoding to create a script file. Avoid other text strings than the default encoding to be contained in the script. For the Linux monitored machine, use the ASCII encoding or the UTF-8 (without BOM) encoding to create a script file.

You must use UTF-8N for a character encoding. For details, see 10.8, "A Character Encoding for Collecting Data via SSH."

• Local user script

You can create custom performance indicators by specifying a script on the management server. When collecting performance data, System Monitor - Performance Monitoring Services executes the script on the management server at every collecting interval. Then, System Monitor - Performance Monitoring Services extracts the results from the [standard output] information to obtain the performance data.

When creating a custom performance indicator, you must specify the name of the script file on the management server as the executing string. You must add the string "local://" before the executing string. Use the following execution examples by script type as a reference. Store the local user script to the following folder. < System Monitor -Performance Monitoring Service install folder>\script

When executing a local user script, the current directory is set to the folder above. If executing a local user script in the different folder, specify the full path of the script in order to avoid execution errors. You can specify scripts such as batch files, Windows Script Host (WSH) and PowerShell on the management server. Use the following execution examples as a reference. Batch file

Specify the batch file path.

E.g.)

Store the script in <System Monitor - Performance Monitoring Services install folder >\script

local://test.bat Store the script in other folders

local://C:\PerformanceMonitor\Script\test.bat


29

WSH(Windows Script Host) script Specify the WSH script execution program and the path of the WSH file. E.g.)

Store the script in <System Monitor - Performance Monitoring Services install folder >\script local://CScript.exe //nologo test.vbs

Store the script in other folders local://CScript.exe //nologo C:\PerformanceMonitor\Script\test.vbs

PowerShell script

You must specify the PowerShell script execution program, the path of the Power Shell script, and the "< NUL" string that is equivalent to the operation of pressing the enter key.

E.g.) Store the script in <System Monitor - Performance Monitoring Services

install folder >\script

local://PowerShell.exe -File test.ps1 < NUL Store the script in other folders

local://PowerShell.exe -File "C:\PerformanceMonitor\Script\test.ps1" < NUL

System Monitor - Performance Monitoring Services obtains the performance data and error information from the result of script execution as the information of the standard output. The script must output the result to the standard output in the following formats: When the script execution succeeded

Output the result to the standard output in the "@metric number name=Performance Indicator target= Target Machine [pathtype=pvm|sysmon] [datetime=Collection time]" format. You can write a local user script so that it outputs the performance data for multiple monitored machines and performance indicators to a same script. You must specify so that it outputs both name and target to identify the performance indicator and the monitored machine. The number above indicates performance data. When specifying number, use integers, fractions, and floats.

The name outputs the title for the custom performance indicator which is defined in System Monitor - Performance Monitoring Services. The target indicates the path of System Monitor - Performance Monitoring Services or SigmaSystemCenter which is required to identify the target machine. You can use the pathtype to explicitly specify whether the path specified in target is on System Monitor - Performance Monitoring Services (sysmon) or on SigmaSystemCenter (pvm). You need to provide the target output with a full path to the monitored machine on System Monitor - Performance Monitoring Services or SigmaSystemCenter in the format Group Name\Machine Name. If pathtime is omitted, the path specified in target is considered it is either on System Monitor - Performance Monitoring Services or on

1 Functions


SigmaSystemCenter. However, if the path is on both, it is considered the path on System Monitor - Performance Monitoring Services. The datetime is the data collection time specified by a script output. System Monitor - Performance Monitoring Services considers datetime is the time when the performance data was collected. datetime is optional. If it is omitted, the time when the script was executed by System Monitor - Performance Monitoring Services is considered as the data collection time. For the format in which datetime is specified, see the description later.

The following shows an output example: echo @metric 1.1E+2 name=CustomPerformance target=Group1\Machine1 pathtype=pvm datetime="2014/01/01 09:00:00"

When the script execution failed Output the result as the error code to the standard output in the format "@metric name=Performance Indicator target=Target Machine [error=Error Message] [errorcode=Error Code]". You do not have to specify error or errorcode because they are optional. Provide the script with the error, which indicates the error message when the script fails, to output it. Output the errorcode, which is an arbitrary code to categorize errors in a script, in an integer. For example, specify "echo @metric name=CustomPerformance error=Failed to execute command errorcode= -1" to output the error code. You must specify so that it outputs both name and target to identify the performance indicator and the monitored machine on which an error occurred.

• Rules for specifying each option of output character strings Use space characters to separate options.

If the specified text string of an option contains space characters, enclose the string with double quotation marks (").

If the specified text string of an option contains equal signs (=) and double quotation marks ("), add a backslash symbol (\) before an equal sign or double quotation mark to escape them. <Example>

When the performance indicators titled "customperf" on a monitored machine, whose group name is "Group 1" and whose machine name is "my=mach"ine ", specify the option as follows:

echo @metric 50 name=customperf target="Group 1\my\=mach\"ine" About the datetime format

Specify datetime in the format "yyyy/MM/dd HH:mm:ss". If you set the different time zone to a monitored machine from that of the System Monitor - Performance Monitoring Services management server, provide the strings to specify the time zone in the format "yyyy/MM/dd HH:mm:sszzz". yyyy: Provide the year. MM: Provide the month.


31

dd: Provide the day. HH: Provide the hour in a 24-hour time format. mm: Provide the minute

ss: Provide the second. zzz: Provide the difference between the time in the time zone and

Coordinated Universal Time(UTC); for example, provide "+09:00" for the Japan time zone. If omitted, the setting of the local time on a management server is set to this option.

• About specifying an argument of a script You can specify the command option for executing the script which is used in the Executing String of Performance Indicator. A command option can specify not only an optional character strings but also some various settings of monitored machine or any information as a variable name. Furthermore, it can specify an optional variable defined in a group, a host and a machine of the SystemProvisioning respectively as a custom property. When executing a user script, at first, change from a variable to an actual character string and then, transfer it to the script finally execute it. Multiple variables also can be specified during the command option. Use space characters to separate scripts from variables ,among

variables

In cases of including blanks in script or variable, use double quotation marks in initial point and terminus point of a specified character string.

The reserved variable and the custom properties are available to use. For the details of each kind of the variable, see the following descriptions: Reserved variable

A reserved variable has already been defined in System Monitor - Performance Monitoring. Any setting and information of the monitored machines which have been registered in System Monitor - Performance Monitoring can be referred by a reserved variable. Refer to the following list about the variables which are available to use.

Reserved variable name Explanation

$:SYSMON_Target This is the information to discriminant the collection target.

▪ In case of collecting machine data, either its IP address for

connection or its name is set.

▪ IP address is prior to the name. If IP address is not specified,

the machine name is set.

▪ In case of collecting performance data of the logical disk, its

identifier (eui) information is set.

$:SYSMON_PERFORMANCE_INDICATOR This is the title of Performance Indicators.

1 Functions



$:SYSMON_COLLECTION_INTERVAL This is the collection interval of Performance indicator. A minute

is used as a unit.

$:SYSMON_START_TIME This is the start time of collecting performance data. It is set in

the specified style of Regional and Language in the Control

Panel of System Monitor - Performance Monitoring Services

management server. As the value of this variable, not the actual

start time of the execution of the script but the start time when

System Monitor - Performance Monitoring Services commenced

collecting process is set. This time is an appropriate end of every

collection interval. Explaining it with detailed examples. In the

case that the collection interval is 5 minutes, even if each start

time is 17:40:**, 17:41:**, 17:42:**, 17:43**, 17:44:**, all these

start is 17:40:00. Similarly, if the start time is 17:45:**, 17:46:**,

17:47:**, 17:48**, 17:49:**, all these start is 17:45:00. In short,

less than 5 minutes are rounded down. Actions are changed in

the minimum integral multiplication of the collection time. A script

is executed with taking other monitored targets or performance

indicators into account, it avoids doing the execution in parallel.

Therefore, the execution of the script is later than the value of this

variable.

$:SYSMON_FIXED_START_TIME This is the start time of collecting performance data. It is set in

the specified style (ScriptInputDatetimeFormat) of the setting file

(rm_service_init.xml) of System Monitor - Performance

Monitoring Services. For the details, refer to the explanation of

$:SYSMON_START_TIME.

$:SYSMON_USERNAME This is the user account information to access the collection

targeted machine.

▪ In cases of Windows machine and Hyper-V host, use the

account information which is specified in Windows OS Account

of Machine Settings.

$:SYSMON_GROUP This is the group path of the collection targeted on System

Monitor - Performance Monitoring Services.

$:SYSMON_PVM_PATH This is the path of the collection targeted on SystemProvisioning.


33


The information of the path to the group is set.

<Example> In the setting of the Performance Indicators for collecting performance data of the logical disks on the NEC Storage, a reserved variable is used as follows. local://GetiStorageLDPerforData.bat $:SYSMON_COLLECTION_INTERVAL $:SYSMON_START_TIME

Custom Property Defining an optional variable by using SystemProvisioning custom property is available. In order to use custom property in the System Monitor - Performance Monitoring Services, custom property has already been defined in the SystemProvisioning and then it should be applied to the System Monitor - Performance Monitoring Services by reflecting the configuration information of SystemProvisioning in the System Monitor - Performance Monitoring Services. Custom property can be defined in the group property setting, host setting on the Operating view of Web console in the SigmaSystemCenter or in the Custom tab of the Machine Property Setting on the Resource view. Although, custom property can set the same property name in each of the operating group, the host and the machine, in accordance with the following priority, the highly rated setting is applied.

1. Host 2. Operating Group 3. Machine In case of specifying the custom property in the executing string of a script as a parameter, to add $ at the beginning of the property name is required.

Reference: For the details of Custom Property, See Subsection 1.6.4 "How to Define Reserved Variable (Custom Property)" in NEC SigmaSystemCenter Reference Guide.

• When you intend to output multiple performance data with a single user script If you intend to execute multiple remote user scripts for the same managed machine or if you intend to execute multiple local user scripts on a management server, we recommend that you write a user script so that it outputs the performance data for multiple managed machines and performance indicators because you can take the following advantages:

1 Functions


You only have to specify a same user script for multiple custom performance indicators. This reduces the number of user scripts and makes it easier to manage user scripts.

This can reduce the number of times user scripts execute. If a user script has already executed at the same timing of collecting data, the data which has been output at the time is obtained as a performance data without executing the user script. System Monitor - Performance Monitoring Services can cache the multiple performance data if they have been output in a same script, which makes it possible to reduce the number of times of the script execution as mentioned above.

Note: Use the script that can be executed in a short time wherever possible to prevent it from affecting on the behavior of collecting performance indicators. Note that long-running scripts may cause execution delays or failures on other scripts. Also, the script execution error may be caused by the script whose execution exceeds fixed timeout duration (30 seconds).

1.3.4. Storing Data that has been collected

System Monitor - Performance Monitoring Services automatically delete performance data after a certain amount of time has passed. The storage period can be set between one day and 30000 days. The default value is 3 days. You can change the storage period using the database management tool of System Monitor - Performance Monitoring Services. For how to change the storage period, see, 7.1 "Data Management Tool". Although the default storage period is three days, the performance data can be preserved for longer period because they are aggregated at various collecting intervals.

Summary Data

35

1.4. Summary Data System Monitor - Performance Monitoring Services manages data collected from managed objects, virtualization platforms of virtual machines, and SystemProvisioning as well as summary data obtained through statistical analysis of the collected performance data. Summary data, which is obtained through statistical analysis of data collected over a certain period of time (referred to below as the "summary interval"), is used to accelerate graph display of data collected over a long period and to store performance data efficiently.

1.4.1. Storage of Summary Data

System Monitor - Performance Monitoring Services manages summary data collected at four summary intervals. If the summary interval is small, performance data of the system can be stored in detail, but the amount of data becomes large. If the summary interval is large, performance data cannot be saved in detail, but performance data can be stored for an extended period of time. The storage period of data collected at each summary interval can be changed according to the usage of historical performance data or the free space of the management server.

The default storage periods for the summary data are as follows:

Summary interval Storage period

5 minutes 1 week

15 minutes 2 month

1 hour 3 months

1 day 5 years

To change the storage period for the data, use the System Monitor Data Management Tool. For details on the Data Management Tool, see "7.1 Data Management Tool".

1.4.2. Usage of Summary Data

In SigmaSystemCenter, summary data and collected data is used for displaying or creating a report as the following:

◆ Displays performance graphs in the SystemMonitor management console.

◆ Displays performance data by using the “ssc-perf show performancedata” command.

◆ Displays performance graphs in the SigmaSystemCenter web console.

◆ Creates a report by using the “ssc create report” command. As shown in the below, available data used for the above charts or the report differ depending on each plot interval.

1 Functions


Plot Interval Available Data

less than 5 minutes collected data

5 minutes to less than 15 minutes 5-minute summary data

15 minutes to less than 1 hour 15-minute summary data

1 hour to 1 day or less 1-hour summary data

more than 1 day 1-day summary data

Data Management

37

1.5. Data Management 1.5.1. Data Management Tool

Data Management Tool can be used to change the storage period for the performance data and summary data or to summarize the data. The Data Management Tool can be used when:

◆ The storage period is to be extended to store performance data over a longer period.

◆ The storage period is to be reduced to save data storage space. ◆ Data summarization is performed to utilize the data used in the previous version as

summary data.

For details on the Data Management Tool, see "7.1 Data Management Tool".

1.5.2. Database Size Monitoring Function

System Monitor - Performance Monitoring Services saves the performance data collected from managed objects, virtualization platforms of virtual machines, and SystemProvisioning as well as summary data that is obtained through summarization of the performance data in a database. The database size monitoring function outputs a warning log to notify the user when the database size exceeds the specified warning value. This function allows the user to be aware of the database engine exceeding a given size, or the lack of free disk space on the management server.

1 Functions


1.6. Groups System Monitor - Performance Monitoring Services can organize managed objects into groups and then monitor and graph the performance status of each group. This makes it possible to track the performance status trends for each group (for example, a group of machines with the same task) and for the entire system. When a performance problem (such as high load) occurs, it is possible to work out which managed object is the cause of the problem by switching from group-level view to managed object-level view.

System Monitor - Performance Monitoring Services expresses grouping units as nodes. There are three types of nodes: the management server node (management server), group nodes (groups), and managed object nodes (managed objects). Managed object nodes represent individual managed objects that have not been grouped. Groups can be created out of any combination of managed objects, except that each managed object can only belong to one group. If configuration is to be synchronized with SystemProvisioning, then the approach to grouping machines depends on SystemProvisioning. See "1.10 The SystemProvisioning Linkage Function" for information on applying SystemProvisioning configuration information.

Connecting to Managed Machines

39

1.7. Connecting to Managed Machines The following section provides general notes about the connection settings for the managed machines. To collect performance data for "Standard Performance Indicator", specify IP address, machine name and access account of the managed machine on System Monitor - Performance Monitoring Services because the managed machine is directly accessed for collecting performance data. For collecting performance data only for "Performance Indicator for Virtual Machine" or "Performance Indicator for Physical Machine", the note shown below is not necessary to be considered because these settings need to be applied from SystemProvisioning and the managed machine is not directly accessed for collecting performance data. For the type of performance indicator, see "1.3 Collected Performance Data".

1.7.1. Specifications for Managed Machines

Specify the IP Address (Optional) and the Machine Name (required) of the managed machine. These are used according to the following rules.

◆ When the IP address is set, System Monitor - Performance Monitoring Services accesses the managed machines using the specified IP address.

◆ When the IP address is not set, System Monitor - Performance Monitoring Services accesses the managed machines using the machine name.

When an IP address of the managed machines is not specified using the System Monitor - Performance Monitoring Services Management Console, the machine name is used to access the managed machine. The machine name is resolved to an IP address by the Management Server automatically. An access error results when it cannot be converted to an IP address. To enable name resolution, you must register the machine name in DNS or the management server hosts file. Specifically, when the managed machine OS is Linux, VMware ESXi, Citrix XenServer or KVM, the machine name is not resolved by default. See "Adding Machines" and "Adding Groups" in "4.1.1 Specifications in the Navigation Tree Window" for specifying machine names and IP addresses with System Monitor - Performance Monitoring Services.

1 Functions


Notes: ▪ Although System Monitor - Performance Monitoring Services supports both IPv4 addresses and IPv6 addresses, the available IP address protocol depends on whether the operating system on the managed machine supports the protocol. In all operating systems except Windows and Linux, only IPv4 address is available because the access using IPv6 addresses to the managed machine running those operating systems is not supported. When you use only a machine name to access the managed machine which can be accessed with IPv4 addresses only, configure the machine name to resolve to the IPv4 address. ▪ The SSH server software installed on a Windows managed machine must support IPv6 to use IPv6 addresses in collecting performance data with scripts on a Windows machine. ▪ When Citrix XenServer is added as a managed machine in the navigation tree window, confirm that the machine is a pool master machine. If the machine is a pool member machine, the performance data of the machine cannot be collected. When a pool member machine is added as a managed machine, use the SystemProvisioning linkage function. See "1.10 The SystemProvisioning Linkage Function" for more detail.

1.7.2. Connection Setting for the Managed Machines

Specify the account name and password so that the Performance Monitoring Service can access the managed machine. When using a SSH public key authentication method, you can use the OpenSSH or SECSH format for the file format of the private key file located in the management server. Use OpenSSH format for the file format of the public key files located in the managed machines. When VMware ESXi is the managed machine, VMware Web Service is used to access the managed machine, and protocol setting is ignored. When Citrix XenServer is the managed machine, XML-RPC protocol is used to access the managed machine, and protocol setting is ignored. Connection settings can be specified for each management server, each group or each individual machine.

◆ For each management server All machines under the management server are applicable targets. Use the Connection tab in the Configuration window.

◆ For each group All machines under the group are applicable targets. When connection settings are different for each group, you must specify connection settings for each group. Use the Connection tab in the Group Settings window.

◆ For each machine Applicable only to the machine. When connection settings are different for each machine, you must specify connection settings for each machine. Use the Connection tab in the Machine Settings window.


41

Targets Setting window Reference

For each management server

All machines under the management server

The Connection tab in the Configuration window.

"2.3.1 Setting the Connection Account to the Managed Machine"

For each group All machines under the group

The Connection tab in the Group Settings window

"4.1.1 Specifications in the Navigation Tree Window"

For each machine Only the machine The Connection tab in the Machine Settings window

"4.1.1 Specifications in the Navigation Tree Window"

The following figure shows which setting will be valid when you specify connection settings for management server, group and machine.

1.7.3. Settings on the Managed Machine

You must make the following settings on the managed machine for System Monitor - Performance Monitoring Services to connect to the managed machines.

Windows For managed machines running Windows, the following settings must be made on the managed machines:

◆ You must select "File and Printer Sharing for Microsoft Networks" in Local Area Connection Properties that is used for System Monitor - Performance Monitoring Services.

YES

YES

The connection settings

specified in the Configuration

of the management server are

used

The connection settings specified in the

Machine Settings are used

The connection settings specified in the

are used

Is connection settings specified

in the Machine Settings?

Is connection settings specified

in the Group Settings?

NO (Default)

NO (Default)

1 Functions


• Set the account name and password as specified with connection settings. The connection account must belong to the Administrators group or Performance Monitor Users group of the managed machine.

User privilege

Administrators Group

Performance Monitor Users Group

Managed OS Type Windows Vista x x

Windows 7 x x

Windows 8 x x

Windows 10 x x

Windows Server 2003 x x




• Configure the Security Settings for the account and for the group which that the account belongs to as follows:


43

Assign the "Access this computer from the network" right to the account or to the Administrators group or the Performance Monitor Users group which the account belongs to.

Avoid that the account and the Administrators group or the Performance Monitor Users group which the account belongs to are added to the list of the "Deny access to this computer from the network" right.

• Local Security Policy: When the managed machine OS is Windows Vista, Windows 7, Windows Server 2008, Windows 8, Windows 10, Windows Server 2012, or Windows Server 2016 and an Administrators group account is used for the access account for a managed machine, perform the following steps. This setting is not necessary if a domain user is used. 1. Start the Local Security Policy using the Administrative Tools in

Control Panel 2. The Local Security Settings are appeared. Select Security Options

of Local Policies from the tree on the left side. 3. When the built-in Administrator is used;

Display the properties by double-clicking User Account Control: Admin Approval Mode for the Built-in Administrator account. When an Administrators group account other than the built-in Administrator is used;

Display the properties by double-clicking User Account Control: Run all administrators in Admin Approval Mode.

4. Select Disabled and then Click OK.

Note: If some effects occur on the monitored machines when [User Account Control: Use Admin Approval Mode for the built-in Administrator account ］ is disabled, create a user account who belongs to the Performance Monitor Users group and specify it as the connection account. For example, the following effect may occur: If this policy setting is enabled, the UAC File Virtualization service cannot start. As a result, in some 32 bit applications which access to these directories such as "%ProgramFiles%", "%ProgramData%", "%SystemRoot%" and write the "HKLM\SOFTWARE" key may occur error and they cannot work properly.

• Service: Start the following services on the managed machines. Remote Registry Server

Perform the following steps. 1. Start Services using Administrative Tools in the Control Panel. 2. A list of the services is appeared. Select the service display name

described above and then double-click to open.

3. Set Startup type in General tab to Automatic.

1 Functions


• Firewall: When the Windows Firewall on the managed machine is enabled, set the exceptions for Windows Firewall using the following steps. 1. Start Windows Firewall in the Control Panel.

2. Select the Exceptions tab in the Windows Firewall window. 3. Check File and Printer Sharing.

If Windows 7, Windows Server 2008, Windows 8, Windows 10, Windows Server 2012, or Windows Server 2016 is the monitored machine, enable the rules shown below on Windows Firewall settings. If you specify These IP addresses under Remote IP address in the Scope tab of Inbound Rules, you must specify the scope of IP addresses and subnets include the management server IP address of System Monitor - Performance Monitoring Services.

File and Printer Sharing (NB-Name-In) File and Printer Sharing (NB-Session-In) File and Printer Sharing (SMB-In)

• Power Options: Set not to go to sleep mode or standby mode automatically. If a monitored machine goes to these modes, the performance data from this machine may not be collected.

◆ The following settings are required to collect performance data with the remote user script.

• In the scripted performance data collecting, the script specified in Performance Indicator Setting is executed after connected to a managed machine from a management server using SSH, which requires installation of the SSH server software on the Windows managed machine. The validated SSH server software includes OpenSSH (cygwin) 6.1.

• In Connection Setting, specify the account and password for the SSH connection. The account must belong to the administrators group on the managed machine.

• Windows PowerShell must be installed on a Windows managed machine to collect performance data using PowerShell, and the user you want to use must be permitted to execute PowerShell remotely. To do so, perform the followings. 1. Log on to the managed machine with the account that you want to use.

2. Click Start, click Run, and then type "PowerShell.exe" to start PowerShell.

3. Execute "Set-ExecutionPolicy RemoteSigned -Scope CurrentUser" to grant the execution right for PowerShell to remotely execute PowerShell to the account.

• Firewall：When a firewall has been setup, exempt SSH communications from firewall blocking.

• If you use the password authentication method, configure an account and password in the connection setting for an SSH connection and enable password authentication.


45

• If you use the public key authentication method, prepare a public key file (OpenSSH) and configure an account and password in the connection setting for an SSH connection.

• You must specify one of the algorithm to an SSH server for the SSH connection from aes128-ctr, aes192-ctr, aes256-ctr, aes128-cbc, aes192-cbc, aes256-cbc, arcfour, arcfour128, arcfour256, lowfish-cbc, cast128-cbc, twofish-cbc, twofish192-cbc, twofish128-cbc, and twofish256-cbc.

◆ In collecting the performance data using a local user script, configure the management server so that the script can be executed on the management server as follows:

• Collecting the performance data by using PowerShell requires the right to execute PowerShell scripts on the management server. To allow the script to be executed on a management server, perform the following: 1. Log on to the management server with an account that has administrator

rights.

2. Click Run from the Start menu, and then enter "PowerShell.exe" to start PowerShell.

3. Run "Set-ExecutionPolicy RemoteSigned" to grant the right to execute PowerShell on a management server.

Linux/KVM ◆ For managed machines that are running Linux or KVM is the managed machine,

the following settings must be made on the monitored machines:

• Enable SSH on each managed machine.

• When you configure a firewall, exclude the SSH port from the blocked ports of the firewall.

• If you use the password authentication method, configure an account and password in the connection setting for an SSH connection and enable password authentication.

• If you use the public key authentication method, prepare a public key file (OpenSSH) and configure an account and password in the connection setting for an SSH connection.

• You must specify one of the algorithm to "/etc/ssh/sshd_config" in an SSH server for the SSH connection from aes128-ctr, aes192-ctr, aes256-ctr, aes128-cbc, aes192-cbc, aes256-cbc, arcfour, arcfour128, arcfour256, lowfish-cbc, cast128-cbc, twofish-cbc, twofish192-cbc, twofish128-cbc, and twofish256-cbc.

• Specify “C” to “LC_ALL” and “LANG” environment variables for the configured account in the connection setting.

VMware ESXi ◆ If VMware ESXi is the managed machine, the following settings must be made on

the managed machines:

• Set the account name and password as specified with connection settings. • Assign a role other than "No Access" to the connection account using Virtual

Infrastructure Client.

1 Functions


• VMware Web Service is used to access the monitored machine. When a firewall has been set up, exempt SSL communications from firewall blocking.

Citrix XenServer ◆ If Citrix XenServer is the managed machine, the following settings must be made

on the managed machines:

• Set the account name and password as specified with connection settings.

• When a firewall has been set up, exempt SSL communications from firewall blocking.

1.7.4. Ports Used between Management Servers and Managed

Machines

The following ports are used for communications between the management server and managed machines.

Management Servers

Protocol Managed Machines Explanation

assigned automatically

TCP NetBIOS over TCP/IP (139) Direct Hosting SMB Service (445)

Used when Windows performance data is collected. *1

UDP NetBIOS over TCP/IP (137)


TCP 135 Used when the performance data of Hyper-V host disk size is collected.

1024-65535 *2


TCP SSH (22) *3 Used when Linux/KVM/Windows performance data is collected using SSH.


TCP SSL (443) Used when Citrix XenServer/VMware ESXi performance data is collected.

*1 If one of the NetBIOS (UDP-137, TCP-139) or SMB/CIFS (TCP-445) setting is enabled, the Windows performance data can be collected.

*2 See Microsoft KB300083 and KB154596 when you intend to restrict those ports.

*3 In Windows managed machine, the SSH (22) needs to be opened only when the performance data will be collected by executing a remote user script.

Displaying Performance Status and CSV File Output

47

1.8. Displaying Performance Status and CSV File Output

System Monitor - Performance Monitoring Services displays performance data for the system graphically. Displaying performance data graphically enables trends to be identified intuitively, and makes it easier to analyze the operational status of the system. Graphs of performance status information can be displayed for each group or for each individual managed object. Performance data is displayed as statistically calculated values. You can also output performance data in the graph display on the management console to a CSV file or a TEXT file.

In addition to the feature of the management console shown above, there is a command line feature to output performance data.

1.8.1. Statistics

"Statistics" are the statistical methods that are used to calculate the performance data collected during the plot interval when performance data is graphed.

◆ Maximum value: Shows the maximum value.

◆ Average value + standard deviation: Shows the relationship between the average value and the degree of scattering for all data.

◆ Average value: Shows the average value.

◆ Average value - standard deviation: Shows the relationship between the average value and the degree of scattering for all data.

◆ Minimum value: Shows the minimum value.

◆ Weighted average value: Shows the average value when weights that have been set up for monitored machines are applied to the data that has been collected. This method is effective when checking the performance status of groups that are made up of machines with different specifications.

◆ Summation value: Shows the summation value of all machines that belonged to the selected Group or Root node. When a machine node is selected, it shows the same value as the Average value.

Weights can be specified for each monitored machine, from 0.0 to 10000.0. For example, suppose there is a group that includes machines with different numbers of CPUs. If these machines are compared using the same performance index, machines with more CPUs are displayed as having lower usage rates even if the work load is the same. In this kind of situation, the processing ability of the group can be expressed more accurately by weighting machines according to the

1 Functions


number of CPUs that they have. See Appendix A, "How performance values for groups are calculated" for guidelines on weightings.

1.8.2. Displaying Formats for Performance Status Graphs

System Monitor - Performance Monitoring Services displays Performance Indicators using three different graph formats, as described below. 1. Node Comparison Display

In this format, the performance status for a particular Performance Indicator item and a particular statistic are displayed for each node. This format is valid for situations such as comparing groups or checking whether there is anything unusual about the performance status of a particular managed object in a certain group, in terms of, for example, the average values for CPU usage.

Figure 1-1: Displaying the Performance Status of Each Group


49

Figure 1-2: Displaying the Performance Status of a Group and a Particular Managed Object within the Group

2. Performance Indicators Display for a Specified Node

With this format, the performance status for a particular node and a particular statistic is displayed for each Performance Indicator item. This format is valid for situations such as investigating performance bottlenecks for a group by comparing, for example, the average values for CPU usage with the average values for disk transfer rates. Individual managed objects can be handled in the same way as groups.

Figure 1-3: Display Comparing CPU Usage and Disk Transfer Rate

3. Statistical Display for a Specified Node and Performance Indicators With this format, the performance status for a particular node and a particular Performance Indicator item is displayed for each statistic. This format is valid for

1 Functions


situations such as checking, for example, changes in the maximum, average and minimum values of CPU usage for a group. Individual managed objects can be handled in the same way as groups.

Figure 1-4: Displaying CPU Usage

To display the performance status for a particular group or managed object for a particular Performance Indicator item and a particular statistic (that is, to select particular elements for each factor), any of the display methods (1) to (3) above can be used.

1.8.3. Graph Display Periods

System Monitor - Performance Monitoring Services graphical displays can display performance status information in real time or historical information for data that has been collected in the past. 1. Realtime Display

Display the latest performance status information for a specified display period from the present time. The graph is updated according to specified update interval. This kind of display is suitable for situations where the current performance status needs to be checked in real time.

2. Historical Display Display the performance status for a specified period from a specified starting time. The graph is not updated periodically. This kind of display is suitable for situations where the past performance status needs to be checked.


51

Notes: ▪ With real-time displays, if performance data for the server being displayed cannot be collected within the collecting interval, data will not be displayed on the graph for the section where data has not been collected. The same applies if the performance status is displayed for a management server or a server group that includes a server for which performance data could not be collected. ▪ If performance data cannot be collected within the collecting interval three times in a row, the server is regarded as having error status, and the graph will not be displayed until the error status is recovered. For graphs of server groups that include a server with error status, the performance status for the remaining normal servers is displayed.

1.8.4. The Graph Window

The System Monitor management console GUI can arrange and display multiple graphs. Multiple node comparison performance status graphs can be arranged and displayed. Alternatively, node comparison performance status graphs can be arranged and displayed together with Performance Indicator comparison status graphs. This is effective when there is a need to keep track of the status of the system from multiple perspectives.

Figure 1-5: Displaying Multiple Windows

1 Functions


1.8.5. Output Graph Data to File

You can output performance data displayed in the graph window to an external file such as CSV with System Monitor - Performance Monitoring Services. Files are output in the following formats.

Line 1 Summary

Line 2 "Time" Column Name Column Name …

Line 3 Time Data Value Data Value …

… Time Data Value Data Value …

… … … … …

File summary is output to Line 1, performance data explanatory headings are output to Line 2, and time (Column 1) and performance data (from Column 2 onwards) are output from Line 3 onwards. Data start time, data end time, data time period, target node name, performance indicator title and statistical method name are output for summaries. For column names, type names of a comparative perspective are output according to the graph type specified from among node names, performance data names and statistical method names as names identifying performance data of identical rows from Row 3 onwards. For time, time axis values of each point plotted on the graph are output. Vertical axis values of points plotted on the displayed graph are output for data values. The column separator and encode format of output characters are as shown below according to the file type specified at file output.

Specified File Type Column Separator

Encode Format of Output Characters

CSV (Separated by Comma) Comma System default (current) encode

Text (Separated by Tab) Tab System default (current) encode

UTF-8 Text (Separated by Tab) Tab UTF-8

1.8.6. Output Data Using Command Line Tool

The ssc-perf command can display the performance data collected by System Monitor - Performance Monitoring Services on the command prompt. See "8.1 ssc-perf Command" about the ssc-perf command.

Threshold Monitoring and the Notification Function

53

1.9. Threshold Monitoring and the Notification Function

System Monitor - Performance Monitoring Services can detect and report load status errors in managed machines by monitoring thresholds for the collected performance data. The detected errors are also can notify to SigmaSystemCenter. This detecting and reporting features are available only when managed objects are machines and not available in resource pools, LUNs on NEC Storage. If you monitor resource pools, use a SystemProvisioning feature. For details, refer to 2.8.3, "Resource Pool Monitoring" in NEC SigmaSystemCenter Reference Guide. You can configure the thresholds to collecting performance information in group or machine units.

1.9.1. Types of Thresholds

The following four types of thresholds can be set up for a single item of Performance Indicator that is subject to threshold monitoring. More than one type of threshold can be selected.

◆ Upper-limit critical value: The status is regarded as "critical" if the target performance data reaches or exceeds this value.

◆ Upper-limit warning value: The status is regarded as "warning" if the target performance data reaches or exceeds this value.

◆ Lower-limit critical value: The status is regarded as "critical" if the target performance data drops to or below this value.

◆ Lower-limit warning value: The status is regarded as "warning" if the target performance data drops to or below this value.

These values must meet the following relationship:

(Lower-limit critical value) < (Lower-limit warning value) < (Upper-limit warning value) < (Upper-limit critical value)

1.9.2. Units of Threshold Monitoring

Thresholds can be set up for the following units.

Monitoring unit Explanation

Machine Threshold monitoring is performed for the specified machine.

Group Threshold monitoring is performed for the specified group. Performance data for the group (produced by statistically processing the performance data for all of the machines in the group) is used as the monitoring target.

All machines in group

Threshold monitoring is performed for each machine in the specified group. The Performance Indicator that is subject to threshold monitoring is the same for all machines in the group, but the threshold monitor monitors the performance data for each machine separately.

1 Functions


1.9.3. Performance Indicators Subject to Threshold Monitoring

Performance Indicators that are currently being collected can be set to be subject to threshold monitoring. If the monitoring unit is "group", the statistic must also be specified.

1.9.4. Notification Actions at Over-Threshold

The following actions can be performed at over-threshold:

◆ Write an event to the event log: This is the default behavior. This cannot be changed.

◆ Display in the navigation tree: Uses an icon to display the status of the machine or group in the over-threshold status. This is the default behavior. This cannot be changed.

◆ Display in the Log window: This is the default behavior. This cannot be changed.

◆ Notify SystemProvisioning: SystemProvisioning can be notified at over-threshold and at recovery. For notification, set notification category to notice. Set actions for notification category using the SigmaSystemCenter policy. See "1.10.5 Notifying Performance Abnormalities" for information on notification categories.

In order to distinguish between temporary load states and ongoing load states, it is also possible to configure the extent or number of over-threshold alert until the load state is considered "critical". The parameters specify the number of times the load state is checked. You can configure the parameters to define how many instances of over-thresholds before an abnormality is reported. By default, an abnormality is reported if over-threshold is found ten times out of ten checks. The check interval is the same as the data collecting interval.

You can also configure the amount of time before another report is made if the over-threshold status has not improved. By default, another report is made every 30 checks.

Example 1: Judging Over-Threshold Status This example shows how over-threshold status is judged when over-threshold status has been set as four threshold crossings out of five checks for upper-limit threshold monitoring. Data is ordered in time from left to right, so that the most recent data is at the far right. In this example, at the point when the data at the far right is collected, threshold crossings have been verified for four of the last five checks, and so the status is judged to be "over-threshold" and the action that has been set up by the user is executed.

Threshold Monitoring and the Notification Function

55

Example 2: Judging Recovery from Over-Threshold Status This example shows how recovery from over-threshold status is judged when over-threshold status has been set as four threshold crossings out of five checks for upper-limit threshold monitoring. In the same way as for when over-threshold status is judged, at the point when the data at the far right is acquired, performance data has been verified as being under the threshold for four of the last five checks, and so the status is judged to have recovered from over-threshold status. Threshold checks for determining recovery from over-threshold status start counting from the next performance data after the data for which over-threshold status was decided.

1 Functions


Example 3: Judging that Over-Threshold Status Continues The specified notification action can be executed again if recovery from over-threshold status cannot be recognized within the specified period (number of checks) from when the over-threshold status was first verified.

The SystemProvisioning Linkage Function

57

1.10. The SystemProvisioning Linkage Function

System Monitor - Performance Monitoring Services has functions that applies system configuration information from SystemProvisioning and notifies SystemProvisioning of performance abnormalities as one of the SigmaSystemCenter components.

1.10.1. System Configuration

The system configuration for System Monitor - Performance Monitoring Services and SystemProvisioning is as follows. During the applying process for system configuration information, the System Monitor - Performance Monitoring Services performance monitoring service acquires configuration information from SystemProvisioning and applies this to the configuration information for System Monitor - Performance Monitoring Services. When performance abnormalities occur, an event is notified to SystemProvisioning. The Performance Monitoring Service and SystemProvisioning do not have to be on the same management server.

Management server

Collecting

Saving performance

Displaying graphs

Making settings

Managed machines

Notifying performance abnormalities

Applying system configurations

System Monitor - Performance Monitoring Services Performance Monitoring Service

SigmaSystemCenter（SystemProvisioning）

Displaying graphs

Making settings

SigmaSystemCenter Web console


Monitoring Services Management

console

1 Functions


1.10.2. Applying System Configuration Information

In machines, SigmaSystemCenter configuration information can be applied to System Monitor - Performance Monitoring Services by enabling the performance monitoring setting for operation groups, models or hosts of SigmaSystemCenter. In resource pools or LUNs on NEC Storage, you can apply the configurations of SigmaSystemCenter to System Monitor - Performance Monitoring Services by enabling the performance monitoring setting in the registry of SystemProvisioning.

◆ Applying machine configurations Configure to apply the configuration information to System Monitor - Performance Monitoring Services in the monitoring settings on the operation group, model or host property of the SigmaSystemCenter Web console. At the timing of applying configuration information of SystemProvisioning, the corresponding group, whose "Performance Data Collection Settings" has been enabled on the property of SigmaSystemCenter group/model settings, is added automatically on System Monitor - Performance Monitoring Services and the configuration information of the managed machines in the specified SigmaSystemCenter group or model shown below is applied to the configuration information of System Monitor - Performance Monitoring Services.

Machine name

IP address

OS information

Machine status (normal or error status)

Account information

Collecting Data settings (Monitoring Profile)

Threshold Monitor settings (Monitoring Profile)

Custom Property When the performance data collecting setting is enabled in the group property of SigmaSystemCenter, if the group has several models, multiple groups mapped to their corresponding models will be created on System Monitor - Performance Monitoring Services. If a group has a model in itself and if collecting performance data is enabled for the higher group property or the target model property, the group for the model is created on System Monitor - Performance Monitoring Services.

The group created on System Monitor - Performance Monitoring Services will be named like "Category name - Group name" if the target to be applied is a group, "Category name - Group name - Model name" if the target to be applied is a model.

System Monitor - Performance Monitoring Services acquires the account settings and the monitoring profile settings (include collecting data settings and threshold monitor settings) from the Performance Monitor settings of the group, model or host property of SigmaSystemCenter and applies automatically to its own group settings and machine settings. For the default settings of the monitoring profile, see "Appendix" of SigmaSystemCenter Configuration Guide.


59

You cannot edit collecting data settings and threshold monitor settings specified in the monitoring profile by using the System Monitor Management Console. Use the SigmaSystemCenter Web Console or the ssc command for editing. For details, refer to NEC SigmaSystemCenter Configuration Guide or NEC SigmaSystemCenter ssc Command Reference. An access account can be configured on the Performance Monitor settings of SigmaSystemCenter. See "4.1 Specifications for Managed Machines" for details on how to configure this setting.

System Monitor - Performance Monitoring Services uses the Management IP address already set up using the host settings of SystemProvisioning to connect to the managed machines. Specify the Management IP address in the Host Setting window with the SigmaSystemCenter Web Console. When the Management IP address is not specified, System Monitor - Performance Monitoring Services uses the machine name to connect to the managed machines. Make settings so that managed machines can be accessed with their machine names.

Notes: ▪ You can also apply System Configuration Information by specifying the path of SystemProvisioning after enabling "Apply SystemProvisioning Configuration" in the group setting of the SystemMonitor Management Console (keep in mind that this is deprecated).

▪ When you specify a machine name, IP address has to be resolved as an IPv4 address for the managed machine running other operating system than Windows and Linux.

◆ Applying resource pool configurations All resource pools and sub resource pools in SigmaSystemCenter are registered to under "Resource Pool Group" in System Monitor - Performance Monitoring Services automatically at the timing of performing the applying configurations feature of SystemProvisioning. The following information of resource pools is also reflected to the configurations of System Monitor - Performance Monitoring Services automatically at this timing:

• Resource pool name • SigmaSystemCenter management ID • Collecting data settings

The collecting data settings (such as enabling or disabling the setting, or which monitoring profile is used) refer the values specified in the following registry by default. This setting is enabled by default. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\SysmonPerf\ResourcePool

The default monitoring profile name is "[Builtin]ResourcePool Monitoring Profile." For the details, refer to Appendix in NEC SigmaSystemCenter Configuration Guide.

1 Functions


Note that although the monitoring profile information (collecting data settings) cannot edit from the System Monitor - Performance Monitoring Services Management Console, but by using the web console of SigmaSystemCenter and ssc command, you can add, edit, and delete the information. For ssc command, refer to ssc Command Reference.

◆ Applying LUN configurations on NEC Storage You can configure monitoring profiles by enabling the collect setting in the following registry of SystemProvisioning: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\SysmonPerf\iStorage The registry keys of LUN is as same as the resource pool. For detail of registry items, please also refer to 5.10.6, "Storing the Historical Data of Resource Pools" in NEC SigmaSystemCenter Configuration Guide.

By configuring this: (1) Groups corresponded with the disk arrays of NEC Storage in SigmaSystemCenter are created in System Monitor - Performance Monitoring Services automatically at the timing of performing the applying configurations feature of SystemProvisioning. The following information of managed LUNs registered in SigmaSystemCenter is also reflected to the configurations of System Monitor - Performance Monitoring Services automatically at this timing: - Eui information

- SigmaSystemCenter management ID - Collecting data settings

(2) The monitoring profile information (collecting data settings), collected from the performance monitoring of SigmaSystemCenter, is reflected to the collecting data settings of System Monitor - Performance Monitoring Services automatically. For the default monitoring profile information, refer to "Appendix A" in NEC SigmaSystemCenter Configuration Guide. Note that although the monitoring profile information (collecting data settings) cannot edit from the System Monitor - Performance Monitoring Services Management Console, but by using the web console of SigmaSystemCenter and ssc command, you can add, edit, and delete the information. For ssc command, refer to ssc Command Reference.


61

◆ Applying SigmaSystemCenter Managed Object configurations Tenants, categories, or groups in the operation view of SigmaSystemCenter Web Console are automatically registered with "SSC Managed Object Group" of System Monitor - Performance Monitoring Services when the configurations of SigmaSystemCenter Managed Objects are applied. The applied information is the following: • SigmaSystemCenter Managed Object names • The SigmaSystemCenter management IDs of SigmaSystemCenter Managed

Objects • Collecting data settings

The collecting data settings (such as enabling or disabling the setting, or which monitoring profile is used) refer the values specified in the following registry by default. This setting is enabled by default.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\SysmonPerf\SSCManagedObject

The default monitoring profile name is "[Builtin]SSC Managed Object Monitoring Profile (1hour)." For the details, refer to Appendix in NEC SigmaSystemCenter Configuration Guide.

Note that although you cannot edit the collecting data settings in the monitoring profile by using a SystemMonitor Management Console, you can add, edit, or delete the collecting data settings by using the web console of SigmaSystemCenter or the ssc command. For the ssc command, refer to the ssc Command Reference.

1.10.3. Timing of Applying of Configuration Information

The system configuration information of SystemProvisioning can be applied manually or automatically. Using the automatic applying function, System Monitor - Performance Monitoring Services communicates with SystemProvisioning at regular intervals, and automatically updates any changes to the configuration information. By default, communication with SystemProvisioning is performed every 10 minutes to automatically apply the configuration information.

1.10.4. Rules for Applying Configuration Information

Applying by the performance monitoring setting in the group, model or host of SigmaSystemCenter; the performance monitoring settings of resource pools; or the performance monitoring settings of LUNs in NEC Storage. When the performance data collection settings for groups, models or hosts of SigmaSystemCenter is enabled, Applying the configuration information of SystemProvisioning in System Monitor - Performance Monitoring Services adds groups, managed object, performance indicators to be collected and thresholds

1 Functions


settings to be monitored or applies machine status to System Monitor - Performance Monitoring Services.

• Applying the group/managed object information When the performance data collection settings for groups or models of SigmaSystemCenter is enabled, applying the configuration information of SystemProvisioning in System Monitor - Performance Monitoring Services adds groups and machines which belong to the groups.

Configuration information comparison (whether monitoring profiles is configured)

Content applied to System Monitor - Performance Monitoring Services

Notes SigmaSystemCenter

group, model, host, or registry

System Monitor - Performance Monitoring Services group

Add/Delete a group

Add/Delete a managed object in the group

Performance data collecting operation

Configure Not exist Add groups Add managed objects

Started If performance monitoring is enabled on SigmaSystemCenter but no corresponding group exists in System Monitor - Performance Monitoring Services, a new group is added to System Monitor - Performance Monitoring Services and System Monitor - Performance Monitoring Services starts managing for the group.

Configure

Exist No changes No changes

Started If performance monitoring for a group is enabled on SigmaSystemCenter, System Monitor - Performance Monitoring Services starts managing for its corresponding group.

Not Configure Exist Not delete Delete managed objects

Stopped If performance monitoring is disabled on SigmaSystemCenter, System Monitor - Performance Monitoring Services stops performance managing.


63

• Applying the managed object information When the running state of the machine has been changed by executing Allocate Machine or Release Machine on SigmaSystemCenter, apply the SystemProvisioning configuration information to System Monitor - Performance Monitoring Services to add a machine or apply the machine state.

When the configurations of SystemProvisioning are changed by adding or deleting resource pools, this changes are reflected at the timing of performing the applying configurations feature of SystemProvisioning for System Monitor - Performance Monitoring Services. When the configurations of SystemProvisioning are changed by registering or deleting disk volumes or disk arrays, LUNs are added or deleted at the timing of performing the applying configurations feature of SystemProvisioning for System Monitor - Performance Monitoring Services.

Configuration information comparison (whether machines exist)


Notes Machines, resource pools, or LUNs on SigmaSystemCenter

Health state

Managed objects on System Monitor - Performance Monitoring Services

Add/Delete a managed object

Performance data collecting operation

Active Normal Not monitored Add managed objects

Started Exists only in the configuration information of SigmaSystemCenter.

Error Stopped

Active Normal Monitored No changes Started Exists in the configuration information of both SigmaSystemCenter and System Monitor - Performance Monitoring Services.

Error Stopped

Not active - Not monitored Delete Stopped Exists only in the configuration information of System Monitor - Performance Monitoring Services.

• Applying the performance information to be collected System Monitor - Performance Monitoring Services adds performance indicators to be collected based on the performance indicator settings in the monitoring profile specified in SigmaSystemCenter while applying the configuration information of SystemProvisioning.

1 Functions




Notes Is the performance indicator configured in the monitoring profile?

Is the performance indicator collected by System Monitor - Performance Monitoring Services?

Add/Delete the performance indicator to be collected

Yes No Add The performance indicator is added on the monitoring profile of SigmaSystemCenter.

Yes Yes Change (such as changing a collecting interval)

The performance indicator is changed on the monitoring profile of SigmaSystemCenter.

No Yes Delete The performance indicator is deleted from the monitoring profile of SigmaSystemCenter.

• Applying the threshold information to be monitored System Monitor - Performance Monitoring Services adds threshold information to be monitored based on the threshold settings in the monitoring profile specified in SigmaSystemCenter while applying the configuration information of SystemProvisioning.



Notes Is the threshold information configured in the monitoring profile?

Is the threshold monitored by System Monitor - Performance Monitoring Services?

Add/Delete the threshold information to be monitored

Yes No Add The threshold monitoring information is added on the monitoring profile of SigmaSystemCenter.

Yes Yes Change (frequency and sensitivity of notification)

The threshold monitoring information is changed on the monitoring profile of SigmaSystemCenter.

No Yes Delete The threshold monitoring information is disabled on or deleted from the


65

monitoring profile of SigmaSystemCenter.

System Monitor - Performance Monitoring Services assesses the operational states for machines with SigmaSystemCenter are as follows. When collecting performance data is impossible, System Monitor - Performance Monitoring Services interrupts to collect the performance data of the managed machine.

Status in which collecting data is possible

When meeting all following conditions. The status of the monitored machine can be confirmed by the operational states of the monitored machines in SigmaSystemCenter Web Console. Power Status: "On" OS Status: "On" Executing Status: Not "Executing"

Status in which collecting data is impossible

All other states

In applying configuration information of SystemProvisioning, a performance data collecting operation for the machine which is in a normal state will be still pausing when the collecting status for the machine has already been changed to paused status manually.

The information of machine status, hardware status and machine type applied from SystemProvisioning configuration is shown in the Summary tab on the Machine Settings window.

Note: See "10.4 Notes on Linking to SystemProvisioning" for the SystemProvisioning configuration information applying function.

1.10.5. Notifying Performance Abnormalities

Load status abnormalities with monitored machines that are detected by System Monitor - Performance Monitoring Services's threshold monitoring can be notified to SigmaSystemCenter. SigmaSystemCenter receives these notifications and executes actions (such as adding machines) according to its policies. Notifications can be made at over-threshold and at recovery. For notification, set notification category to notice. As actions according to policy cannot be set for SystemProvisioning category groups, when category groups are assigned to System Monitor - Performance Monitoring Services, they are disabled even when threshold definitions are set for groups. To link the recovery process to threshold monitoring, assign the SystemProvisioning groups or subgroups to groups of System Monitor - Performance Monitoring Services.

◆ Notification Categories "Notification categories" are the different classifications for associating the System Monitor - Performance Monitoring Services events that are sent when over-threshold conditions occur or recovery from over-threshold conditions occur with the SigmaSystemCenter recovery processes that are triggered by these

1 Functions


events. There are two types of notification categories with the different type of performance indicator that can be set. It is possible to set built-in notification categories and customized notification categories both for built-in performance indicators. But only customized notification categories can set for customized performance indicators.

• Built-In Notification Categories There are eight types of built-in notification categories for each built-in performance indicator. It is possible to set the recovery action from the policy setting in SigmaSystemCenter. The types of built-in notification categories are listed as follows:

① Upper Error Exceeded: The event is notified to the SigmaSystemCenter when the collected performance data reaches or exceeds the upper-limit critical value.

② Upper Error Recovery: The event is notified to the SigmaSystemCenter when the collected performance data drops to or below the upper-limit critical value.

③ Upper Warning Exceeded: The event is notified to the SigmaSystemCenter when the collected performance data reaches or exceeds the upper-limit warning value.

④ Upper Warning Recovery: The event is notified to the SigmaSystemCenter when the collected performance data drops to or below the upper-limit warning value.

⑤ Lower Warning Exceeded: The event is notified to the SigmaSystemCenter when the collected performance data drops to or below the lower-limit warning value.

⑥ Lower Warning Recovery: The event is notified to the SigmaSystemCenter when the collected performance data reaches or exceeds the lower-limit warning value.

⑦ Lower Error Exceeded: The event is notified to the SigmaSystemCenter when the collected performance data drops to or below the lower-limit critical value.

⑧ Lower Error Recovery: The event is notified to the SigmaSystemCenter when the collected performance data reaches or exceeds the lower-limit critical value.

The built-in notification categories are listed as follows:

Performance Indicator Event ID Event

CPU Usage (%)

0x20000100 CPU Usage (%) Lower Warning Recovery

0x20000101 CPU Usage (%) Lower Warning Exceeded

0x20000102 CPU Usage (%) Lower Error Recovery

0x20000103 CPU Usage (%) Lower Error Exceeded

0x20000104 CPU Usage (%) Upper Warning Recovery

0x20000105 CPU Usage (%) Upper Warning Exceeded

0x20000106 CPU Usage (%) Upper Error Recovery


67


0x20000107 CPU Usage (%) Upper Error Exceeded

CPU System Usage (%)

0x20000200 CPU System Usage (%) Lower Warning Recovery

0x20000201 CPU System Usage (%) Lower Warning Exceeded

0x20000202 CPU System Usage (%) Lower Error Recovery

0x20000203 CPU System Usage (%) Lower Error Exceeded

0x20000204 CPU System Usage (%) Upper Warning Recovery

0x20000205 CPU System Usage (%) Upper Warning Exceeded

0x20000206 CPU System Usage (%) Upper Error Recovery

0x20000207 CPU System Usage (%) Upper Error Exceeded

CPU User Usage (%)

0x20000300 CPU User Usage (%) Lower Warning Recovery

0x20000301 CPU User Usage (%) Lower Warning Exceeded

0x20000302 CPU User Usage (%) Lower Error Recovery

0x20000303 CPU User Usage (%) Lower Error Exceeded

0x20000304 CPU User Usage (%) Upper Warning Recovery

0x20000305 CPU User Usage (%) Upper Warning Exceeded

0x20000306 CPU User Usage (%) Upper Error Recovery

0x20000307 CPU User Usage (%) Upper Error Exceeded

CPU Usage (MHz)

0x20000400 CPU Usage (MHz) Lower Warning Recovery

0x20000401 CPU Usage (MHz) Lower Warning Exceeded

0x20000402 CPU Usage (MHz) Lower Error Recovery

0x20000403 CPU Usage (MHz) Lower Error Exceeded

0x20000404 CPU Usage (MHz) Upper Warning Recovery

0x20000405 CPU Usage (MHz) Upper Warning Exceeded

0x20000406 CPU Usage (MHz) Upper Error Recovery

0x20000407 CPU Usage (MHz) Upper Error Exceeded

Guest CPU Usage (%)

0x20000B00 Guest CPU Usage (%) Lower Warning Recovery

0x20000B01 Guest CPU Usage (%) Lower Warning Exceeded

0x20000B02 Guest CPU Usage (%) Lower Error Recovery

0x20000B03 Guest CPU Usage (%) Lower Error Exceeded

0x20000B04 Guest CPU Usage (%) Upper Warning Recovery

0x20000B05 Guest CPU Usage (%) Upper Warning Exceeded

0x20000B06 Guest CPU Usage (%) Upper Error Recovery

0x20000B07 Guest CPU Usage (%) Upper Error Exceeded

Guest CPU Usage (MHz)

0x20000C00 Guest CPU Usage (MHz) Lower Warning Recovery

0x20000C01 Guest CPU Usage (MHz) Lower Warning Exceeded

0x20000C02 Guest CPU Usage (MHz) Lower Error Recovery

0x20000C03 Guest CPU Usage (MHz) Lower Error Exceeded

0x20000C04 Guest CPU Usage (MHz) Upper Warning Recovery

0x20000C05 Guest CPU Usage (MHz) Upper Warning Exceeded

1 Functions



0x20000C06 Guest CPU Usage (MHz) Upper Error Recovery

0x20000C07 Guest CPU Usage (MHz) Upper Error Exceeded

Host CPU Usage (%)

0x20000D00 Host CPU Usage (%) Lower Warning Recovery

0x20000D01 Host CPU Usage (%) Lower Warning Exceeded

0x20000D02 Host CPU Usage (%) Lower Error Recovery

0x20000D03 Host CPU Usage (%) Lower Error Exceeded

0x20000D04 Host CPU Usage (%) Upper Warning Recovery

0x20000D05 Host CPU Usage (%) Upper Warning Exceeded

0x20000D06 Host CPU Usage (%) Upper Error Recovery

0x20000D07 Host CPU Usage (%) Upper Error Exceeded

Host CPU Usage (MHz)

0x20000E00 Host CPU Usage (MHz) Lower Warning Recovery

0x20000E01 Host CPU Usage (MHz) Lower Warning Exceeded

0x20000E02 Host CPU Usage (MHz) Lower Error Recovery

0x20000E03 Host CPU Usage (MHz) Lower Error Exceeded

0x20000E04 Host CPU Usage (MHz) Upper Warning Recovery

0x20000E05 Host CPU Usage (MHz) Upper Warning Exceeded

0x20000E06 Host CPU Usage (MHz) Upper Error Recovery

0x20000E07 Host CPU Usage (MHz) Upper Error Exceeded

Disk Transfer Rate (Bytes/sec)

0x20001500 Disk Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20001501 Disk Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20001502 Disk Transfer Rate (Bytes/sec) Lower Error Recovery

0x20001503 Disk Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20001504 Disk Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20001505 Disk Transfer Rate (Bytes/sec) Upper Warning Exceeded

0x20001506 Disk Transfer Rate (Bytes/sec) Upper Error Recovery

0x20001507 Disk Transfer Rate (Bytes/sec) Upper Error Exceeded

Disk IO Count (IO/sec)

0x20001600 Disk IO Count (IO/sec) Lower Warning Recovery

0x20001601 Disk IO Count (IO/sec) Lower Warning Exceeded

0x20001602 Disk IO Count (IO/sec) Lower Error Recovery

0x20001603 Disk IO Count (IO/sec) Lower Error Exceeded

0x20001604 Disk IO Count (IO/sec) Upper Warning Recovery

0x20001605 Disk IO Count (IO/sec) Upper Warning Exceeded

0x20001606 Disk IO Count (IO/sec) Upper Error Recovery

0x20001607 Disk IO Count (IO/sec) Upper Error Exceeded

Disk Read Transfer Rate (Bytes/sec)

0x20001700 Disk Read Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20001701 Disk Read Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20001702 Disk Read Transfer Rate (Bytes/sec) Lower Error Recovery


69


0x20001703 Disk Read Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20001704 Disk Read Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20001705 Disk Read Transfer Rate (Bytes/sec) Upper Warning Exceeded

0x20001706 Disk Read Transfer Rate (Bytes/sec) Upper Error Recovery

0x20001707 Disk Read Transfer Rate (Bytes/sec) Upper Error Exceeded

Disk Read Count (IO/sec)

0x20001800 Disk Read Count (IO/sec) Lower Warning Recovery

0x20001801 Disk Read Count (IO/sec) Lower Warning Exceeded

0x20001802 Disk Read Count (IO/sec) Lower Error Recovery

0x20001803 Disk Read Count (IO/sec) Lower Error Exceeded

0x20001804 Disk Read Count (IO/sec) Upper Warning Recovery

0x20001805 Disk Read Count (IO/sec) Upper Warning Exceeded

0x20001806 Disk Read Count (IO/sec) Upper Error Recovery

0x20001807 Disk Read Count (IO/sec) Upper Error Exceeded

Disk Write Transfer Rate (Bytes/sec)

0x20001900 Disk Write Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20001901 Disk Write Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20001902 Disk Write Transfer Rate (Bytes/sec) Lower Error Recovery

0x20001903 Disk Write Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20001904 Disk Write Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20001905 Disk Write Transfer Rate (Bytes/sec) Upper Warning Exceeded

0x20001906 Disk Write Transfer Rate (Bytes/sec) Upper Error Recovery

0x20001907 Disk Write Transfer Rate (Bytes/sec) Upper Error Exceeded

Disk Write Count (IO/sec)

0x20001A00 Disk Write Count (IO/sec) Lower Warning Recovery

0x20001A01 Disk Write Count (IO/sec) Lower Warning Exceeded

0x20001A02 Disk Write Count (IO/sec) Lower Error Recovery

0x20001A03 Disk Write Count (IO/sec) Lower Error Exceeded

0x20001A04 Disk Write Count (IO/sec) Upper Warning Recovery

0x20001A05 Disk Write Count (IO/sec) Upper Warning Exceeded

0x20001A06 Disk Write Count (IO/sec) Upper Error Recovery

0x20001A07 Disk Write Count (IO/sec) Upper Error Exceeded

Disk Space (MB)

0x20001B00 Disk Space (MB) Lower Warning Recovery

0x20001B01 Disk Space (MB) Lower Warning Exceeded

0x20001B02 Disk Space (MB) Lower Error Recovery

0x20001B03 Disk Space (MB) Lower Error Exceeded

0x20001B04 Disk Space (MB) Upper Warning Recovery

0x20001B05 Disk Space (MB) Upper Warning Exceeded

1 Functions



0x20001B06 Disk Space (MB) Upper Error Recovery

0x20001B07 Disk Space (MB) Upper Error Exceeded

Disk Space Ratio (%)

0x20001C00 Disk Space Ratio (%) Lower Warning Recovery

0x20001C01 Disk Space Ratio (%) Lower Warning Exceeded

0x20001C02 Disk Space Ratio (%) Lower Error Recovery

0x20001C03 Disk Space Ratio (%) Lower Error Exceeded

0x20001C04 Disk Space Ratio (%) Upper Warning Recovery

0x20001C05 Disk Space Ratio (%) Upper Warning Exceeded

0x20001C06 Disk Space Ratio (%) Upper Error Recovery

0x20001C07 Disk Space Ratio (%) Upper Error Exceeded

Guest Disk Transfer Rate (Bytes/sec)

0x20001F00 Guest Disk Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20001F01 Guest Disk Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20001F02 Guest Disk Transfer Rate (Bytes/sec) Lower Error Recovery

0x20001F03 Guest Disk Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20001F04 Guest Disk Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20001F05 Guest Disk Transfer Rate (Bytes/sec) Upper Warning Exceeded

0x20001F06 Guest Disk Transfer Rate (Bytes/sec) Upper Error Recovery

0x20001F07 Guest Disk Transfer Rate (Bytes/sec) Upper Error Exceeded

Guest Disk IO Count (IO/sec)

0x20002000 Guest Disk IO Count (IO/sec) Lower Warning Recovery

0x20002001 Guest Disk IO Count (IO/sec) Lower Warning Exceeded

0x20002002 Guest Disk IO Count (IO/sec) Lower Error Recovery

0x20002003 Guest Disk IO Count (IO/sec) Lower Error Exceeded

0x20002004 Guest Disk IO Count (IO/sec) Upper Warning Recovery

0x20002005 Guest Disk IO Count (IO/sec) Upper Warning Exceeded

0x20002006 Guest Disk IO Count (IO/sec) Upper Error Recovery

0x20002007 Guest Disk IO Count (IO/sec) Upper Error Exceeded

Guest Disk Read Transfer Rate (Bytes/sec)

0x20002100 Guest Disk Read Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20002101 Guest Disk Read Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20002102 Guest Disk Read Transfer Rate (Bytes/sec) Lower Error Recovery

0x20002103 Guest Disk Read Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20002104 Guest Disk Read Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20002105 Guest Disk Read Transfer Rate (Bytes/sec) Upper Warning Exceeded


71


0x20002106 Guest Disk Read Transfer Rate (Bytes/sec) Upper Error Recovery

0x20002107 Guest Disk Read Transfer Rate (Bytes/sec) Upper Error Exceeded

Guest Disk Read Count (IO/sec)

0x20002200 Guest Disk Read Count (IO/sec) Lower Warning Recovery

0x20002201 Guest Disk Read Count (IO/sec) Lower Warning Exceeded

0x20002202 Guest Disk Read Count (IO/sec) Lower Error Recovery

0x20002203 Guest Disk Read Count (IO/sec) Lower Error Exceeded

0x20002204 Guest Disk Read Count (IO/sec) Upper Warning Recovery

0x20002205 Guest Disk Read Count (IO/sec) Upper Warning Exceeded

0x20002206 Guest Disk Read Count (IO/sec) Upper Error Recovery

0x20002207 Guest Disk Read Count (IO/sec) Upper Error Exceeded

Guest Disk Write Transfer Rate (Bytes/sec)

0x20002300 Guest Disk Write Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20002301 Guest Disk Write Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20002302 Guest Disk Write Transfer Rate (Bytes/sec) Lower Error Recovery

0x20002303 Guest Disk Write Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20002304 Guest Disk Write Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20002305 Guest Disk Write Transfer Rate (Bytes/sec) Upper Warning Exceeded

0x20002306 Guest Disk Write Transfer Rate (Bytes/sec) Upper Error Recovery

0x20002307 Guest Disk Write Transfer Rate (Bytes/sec) Upper Error Exceeded

Guest Disk Write Count (IO/sec)

0x20002400 Guest Disk Write Count (IO/sec) Lower Warning Recovery

0x20002401 Guest Disk Write Count (IO/sec) Lower Warning Exceeded

0x20002402 Guest Disk Write Count (IO/sec) Lower Error Recovery

0x20002403 Guest Disk Write Count (IO/sec) Lower Error Exceeded

0x20002404 Guest Disk Write Count (IO/sec) Upper Warning Recovery

0x20002405 Guest Disk Write Count (IO/sec) Upper Warning Exceeded

0x20002406 Guest Disk Write Count (IO/sec) Upper Error Recovery

0x20002407 Guest Disk Write Count (IO/sec) Upper Error Exceeded

Guest Disk Usage (MB)

0x20002500 Guest Disk Usage (MB) Lower Warning Recovery

0x20002501 Guest Disk Usage (MB) Lower Warning Exceeded

0x20002502 Guest Disk Usage (MB) Lower Error Recovery

0x20002503 Guest Disk Usage (MB) Lower Error Exceeded

0x20002504 Guest Disk Usage (MB) Upper Warning Recovery

0x20002505 Guest Disk Usage (MB) Upper Warning Exceeded

0x20002506 Guest Disk Usage (MB) Upper Error Recovery

1 Functions



0x20002507 Guest Disk Usage (MB) Upper Error Exceeded

Guest Disk Usage (%)

0x20002600 Guest Disk Usage (%) Lower Warning Recovery

0x20002601 Guest Disk Usage (%) Lower Warning Exceeded

0x20002602 Guest Disk Usage (%) Lower Error Recovery

0x20002603 Guest Disk Usage (%) Lower Error Exceeded

0x20002604 Guest Disk Usage (%) Upper Warning Recovery

0x20002605 Guest Disk Usage (%) Upper Warning Exceeded

0x20002606 Guest Disk Usage (%) Upper Error Recovery

0x20002607 Guest Disk Usage (%) Upper Error Exceeded

Network Packet Transfer Rate (Bytes/sec)

0x20002900 Network Packet Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20002901 Network Packet Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20002902 Network Packet Transfer Rate (Bytes/sec) Lower Error Recovery

0x20002903 Network Packet Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20002904 Network Packet Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20002905 Network Packet Transfer Rate (Bytes/sec) Upper Warning Exceeded

0x20002906 Network Packet Transfer Rate (Bytes/sec) Upper Error Recovery

0x20002907 Network Packet Transfer Rate (Bytes/sec) Upper Error Exceeded

Network Packet Reception Rate (Bytes/sec)

0x20002A00 Network Packet Reception Rate (Bytes/sec) Lower Warning Recovery

0x20002A01 Network Packet Reception Rate (Bytes/sec) Lower Warning Exceeded

0x20002A02 Network Packet Reception Rate (Bytes/sec) Lower Error Recovery

0x20002A03 Network Packet Reception Rate (Bytes/sec) Lower Error Exceeded

0x20002A04 Network Packet Reception Rate (Bytes/sec) Upper Warning Recovery

0x20002A05 Network Packet Reception Rate (Bytes/sec) Upper Warning Exceeded

0x20002A06 Network Packet Reception Rate (Bytes/sec) Upper Error Recovery

0x20002A07 Network Packet Reception Rate (Bytes/sec) Upper Error Exceeded

Network Packet Transmission Rate (Bytes/sec)

0x20002B00 Network Packet Transmission Rate (Bytes/sec) Lower Warning Recovery

0x20002B01 Network Packet Transmission Rate (Bytes/sec) Lower Warning Exceeded


73


0x20002B02 Network Packet Transmission Rate (Bytes/sec) Lower Error Recovery

0x20002B03 Network Packet Transmission Rate (Bytes/sec) Lower Error Exceeded

0x20002B04 Network Packet Transmission Rate (Bytes/sec) Upper Warning Recovery

0x20002B05 Network Packet Transmission Rate (Bytes/sec) Upper Warning Exceeded

0x20002B06 Network Packet Transmission Rate (Bytes/sec) Upper Error Recovery

0x20002B07 Network Packet Transmission Rate (Bytes/sec) Upper Error Exceeded

Guest Network Transfer Rate (Bytes/sec)

0x20003300 Guest Network Transfer Rate (Bytes/sec) Lower Warning Recovery

0x20003301 Guest Network Transfer Rate (Bytes/sec) Lower Warning Exceeded

0x20003302 Guest Network Transfer Rate (Bytes/sec) Lower Error Recovery

0x20003303 Guest Network Transfer Rate (Bytes/sec) Lower Error Exceeded

0x20003304 Guest Network Transfer Rate (Bytes/sec) Upper Warning Recovery

0x20003305 Guest Network Transfer Rate (Bytes/sec) Upper Warning Exceeded

0x20003306 Guest Network Transfer Rate (Bytes/sec) Upper Error Recovery

0x20003307 Guest Network Transfer Rate (Bytes/sec) Upper Error Exceeded

Physical Memory Space (MB)

0x20003D00 Physical Memory Space (MB) Lower Warning Recovery

0x20003D01 Physical Memory Space (MB) Lower Warning Exceeded

0x20003D02 Physical Memory Space (MB) Lower Error Recovery

0x20003D03 Physical Memory Space (MB) Lower Error Exceeded

0x20003D04 Physical Memory Space (MB) Upper Warning Recovery

0x20003D05 Physical Memory Space (MB) Upper Warning Exceeded

0x20003D06 Physical Memory Space (MB) Upper Error Recovery

0x20003D07 Physical Memory Space (MB) Upper Error Exceeded

Physical Memory Space Ratio (%)

0x20003E00 Physical Memory Space Ratio (%) Lower Warning Recovery

0x20003E01 Physical Memory Space Ratio (%) Lower Warning Exceeded

0x20003E02 Physical Memory Space Ratio (%) Lower Error Recovery

0x20003E03 Physical Memory Space Ratio (%) Lower Error Exceeded

0x20003E04 Physical Memory Space Ratio (%) Upper Warning Recovery

0x20003E05 Physical Memory Space Ratio (%) Upper Warning Exceeded

0x20003E06 Physical Memory Space Ratio (%) Upper Error Recovery

0x20003E07 Physical Memory Space Ratio (%) Upper Error Exceeded

1 Functions



Guest Memory Usage (%)

0x20004700 Guest Memory Usage (%) Lower Warning Recovery

0x20004701 Guest Memory Usage (%) Lower Warning Exceeded

0x20004702 Guest Memory Usage (%) Lower Error Recovery

0x20004703 Guest Memory Usage (%) Lower Error Exceeded

0x20004704 Guest Memory Usage (%) Upper Warning Recovery

0x20004705 Guest Memory Usage (%) Upper Warning Exceeded

0x20004706 Guest Memory Usage (%) Upper Error Recovery

0x20004707 Guest Memory Usage (%) Upper Error Exceeded

Guest Memory Usage (MB)

0x20004800 Guest Memory Usage (MB) Lower Warning Recovery

0x20004801 Guest Memory Usage (MB) Lower Warning Exceeded

0x20004802 Guest Memory Usage (MB) Lower Error Recovery

0x20004803 Guest Memory Usage (MB) Lower Error Exceeded

0x20004804 Guest Memory Usage (MB) Upper Warning Recovery

0x20004805 Guest Memory Usage (MB) Upper Warning Exceeded

0x20004806 Guest Memory Usage (MB) Upper Error Recovery

0x20004807 Guest Memory Usage (MB) Upper Error Exceeded

Host Memory Usage (%)

0x20004900 Host Memory Usage (%) Lower Warning Recovery

0x20004901 Host Memory Usage (%) Lower Warning Exceeded

0x20004902 Host Memory Usage (%) Lower Error Recovery

0x20004903 Host Memory Usage (%) Lower Error Exceeded

0x20004904 Host Memory Usage (%) Upper Warning Recovery

0x20004905 Host Memory Usage (%) Upper Warning Exceeded

0x20004906 Host Memory Usage (%) Upper Error Recovery

0x20004907 Host Memory Usage (%) Upper Error Exceeded

Host Memory Usage (MB)

0x20004A00 Host Memory Usage (MB) Lower Warning Recovery

0x20004A01 Host Memory Usage (MB) Lower Warning Exceeded

0x20004A02 Host Memory Usage (MB) Lower Error Recovery

0x20004A03 Host Memory Usage (MB) Lower Error Exceeded

0x20004A04 Host Memory Usage (MB) Upper Warning Recovery

0x20004A05 Host Memory Usage (MB) Upper Warning Exceeded

0x20004A06 Host Memory Usage (MB) Upper Error Recovery

0x20004A07 Host Memory Usage (MB) Upper Error Exceeded

Current Power (W)

0x20006500 Current Power (W) Lower Warning Recovery

0x20006501 Current Power (W) Lower Warning Exceeded

0x20006502 Current Power (W) Lower Error Recovery

0x20006503 Current Power (W) Lower Error Exceeded

0x20006504 Current Power (W) Upper Warning Recovery

0x20006505 Current Power (W) Upper Warning Exceeded


75


0x20006506 Current Power (W) Upper Error Recovery

0x20006507 Current Power (W) Upper Error Exceeded

• Customized Notification Categories There are two customized notification categories, depending on the nature of the SigmaSystemCenter recovery process: a notification category for machines, and a notification category for groups. The customized notification categories are listed as follows:

Event Type Event ID Event

CustomizedMachineNotification 0x10000001 Customized machine notification1

0x10000002 Customized machine notification2








0x1000000A Customized machine notification10

CustomizedGroupNotification 0x11000001 Customized group notification１

0x11000002 Customized group notification2




With the "machine" notification category, recovery processes for individual machines can be set up, such as "shut down", "reboot", "replace" and so on. With the "group" notification category, recovery processes for groups can be set up, such as "add machine" or "delete machine" and so on. When the threshold method is used with target nodes, the threshold method for which the "group" customized notification category has been set cannot be associated with machine nodes. Similarly, the threshold method for which the "machine" customized notification category has been set cannot be associated with group nodes. Note also that customized notification categories can also be used from other components, and so uses may overlap if SystemProvisioning receives notifications from more than one component.

1 Functions


As actions according to policy cannot be set for SigmaSystemCenter category groups, when category group is allocated to System Monitor - Performance Monitoring Services group, they are invalid even if threshold definitions are set for groups. To set the recovery process linked to threshold monitoring, assign SystemProvisioning groups or subgroups as groups of System Monitor - Performance Monitoring Services.

◆ Applying Threshold Setting Information Linked to Changes in System Configurations

With System Monitor - Performance Monitoring Services, threshold monitoring settings can be applied for three types of monitoring units: "machine", " group" and "all machines in group".

Note that when machines are added to a group of SigmaSystemCenter as a result of such as a performance abnormality notification, you must reconfigure the group, so that the machines can be targeted for the threshold monitoring function.

The following table shows the status of the threshold monitoring setting when the System Monitor Management Console configuration information is changed.

Threshold monitoring unit before the configuration change

Change made to the configuration

State of the threshold monitoring setting after the configuration change

Notes

Machine Machine added Threshold monitoring settings are not set for the added machine.

Machine removed

Threshold monitoring settings are removed.

Group Machine added, removed or moved

- (Threshold monitoring settings for the group are unchanged.)

Threshold monitoring is performed for the machines that belong to the group.

Group removed Threshold monitoring settings for the group are removed.

All machines in group Machine added Threshold monitoring settings are set for the added machine.

Machine removed

Threshold monitoring settings are removed for the removed machine

Machine moved Threshold monitoring settings for the original group will be discarded, and the settings for the new group are set up.

Group removed Threshold monitoring settings are removed for all the machines in the group.


77

◆ Operational Notes • Warnings and abnormalities may occur at the same time if the values set for

abnormality and warning thresholds are very close, or if the load status changes suddenly. With SigmaSystemCenter, configurations can change automatically due to such processes as fault recovery, and during the configuration change, the performance status may change to an unexpected high load. A high load may also be detected again before the machine addition is completed. Conduct thorough operational planning before linking to SystemProvisioning configuration change processing.

• In a machine added by using Add Machine in SystemMonitor Management Console, you cannot use the policy feature of SigmaSystemCenter by using reported abnormal load status from the machines to SigmaSystemCenter. To use the policy feature, apply SigmaSystemCenter system configuration information (see, "1.10.2 Applying System Configuration Information") to monitor the threshold of the machine.

Note: See "10.4 Notes on Linking to SystemProvisioning" for more information on SystemProvisioning configuration changes triggered by threshold monitoring.

1 Functions


1.10.6. VM Optimization Linkage Function

SigmaSystemCenter executes a load balancing policy, which balances the load imposed by the grouped VM servers. It also applies a power saving policy, which powers off any unnecessary VM servers, by applying the VM optimization configuration to a VM server group and receiving a performance failure report from System Monitor - Performance Monitoring Services.

When the configuration information for a VM server model to which the VM optimization configuration has been applied in SystemProvisioning is reflected on System Monitor - Performance Monitoring Services, threshold settings that are tailored to the VM optimization configuration set in SystemProvisioning are automatically created as the configuration information is reflected. The threshold monitor settings are registered for all the servers in the group for which reflection was performed.

The threshold settings to be registered automatically are as listed below.

<Threshold Method for VM Server high load>

Item Setting Remark

Threshold method name "[VMServer] <SystemProvisioning path> CPU Usage (%) High Load threshold definition"

Unchangeable

Performance indicator CPU Usage (%) Unchangeable

Statistics Average value Unchangeable

Upper limit critical value High load bound value for the VM optimization configuration specified by the model setting in SigmaSystemCenter. The notification category during excess is "VM

Changeable only from SigmaSystemCenter

Management server

Collecting performance data

System Monitor – Performance Monitoring Services

SystemProvisioning

Notifying performance abnormalities

Applying system configuration

VM Optimization policy

VM server group

Executing recovery action


79

Item Setting Remark Server high load".

Upper limit warning value Not set. Unchangeable

Lower limit warning value Not set. Unchangeable

Lower limit critical value Not set. Unchangeable

Notification settings Default value (A notification is issued if the threshold is exceeded ten times in 10 checks. Another notification is issued every 10 checks.)

Changeable

<Threshold Method for VM Server low load>

Item Setting Remark

Threshold method name "[VMServer] <SystemProvisioning path> CPU Usage (%) Low Load threshold definition"

Unchangeable

Performance indicator CPU Usage (%) Unchangeable

Statistics Average value Unchangeable

Upper limit critical value Not set. Unchangeable

Upper limit warning value Not set. Unchangeable

Lower limit warning value Not set. Unchangeable

Lower limit critical value Low load bound value for the VM optimization configuration specified by the model setting in SigmaSystemCenter. The notification category during excess is "VM Server low load".

Changeable only from SigmaSystemCenter

Notification settings Default value (A notification is issued if the threshold is exceeded 30 times in 30 checks. Another notification is issued every 30 checks.)

Changeable

Notes: ▪ The SystemProvisioning path to be set in the server group of System Monitor - Performance Monitoring Services must be a full path to the model to use the VM Optimized Placement feature to register the target virtual machine server. ▪ Notification categories "VM Server high load" and "VM Server low load", which are used by the threshold method obtained from SigmaSystemCenter and then registered, cannot be used when the threshold method is registered manually.

1 Functions


1.11. Command-Line Interface Using the command-line tool (ssc-perf.exe) makes it possible to do the following things.

◆ The performance data collected by System Monitor - Performance Monitoring Services can be displayed on the command prompt. This makes it possible to track the performance of managed objects without starting the management console.

◆ Displaying, adding and deleting the custom performance indicators are possible. Setting the custom performance indicators easily is possible.

1.11.1. System Configuration

This tool is installed on the management server. This tool is executable on the management server.

An administrator privilege is needed to run this tool.

Management server

Collecting performance data

System Monitor - Performance Monitoring Services Performance Monitoring Service

Exporting Performance data Display Custom

performance indicators

Managed machines

Command-Line Tool (ssc-perf)

Querying performance data

Display/Add/Delete Custom performance

Indicators

Saving performance data

Command-Line Interface

81

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 ssc-perf commands.

1.11.2. Data Format and Target

The data format is same as the format shown in "1.8.5 Output Graph Data to File". The data is queried by the specified parameters (node, performance indicator, statistical method, period and so on). Node, performance indicator and statistical method are required parameters. You can specify multiple values for only one of the three required parameters.

For the detail of the usage of the tool, see "8.1 ssc-perf Command"

83

2. Configuration Settings This chapter explains how to make configuration settings. This chapter contains the following sections: • 2.1 Starting the Performance Monitoring Service ............................................................84 • 2.2 Registering the Management Server .........................................................................85 • 2.3 Connection Settings to Managed Machines ..............................................................86 • 2.4 Connection Settings to the Management Console ....................................................87 • 2.5 The Execution Account for the Performance Monitoring Service ..............................91 • 2.6 SystemProvisioning Connection Settings ..................................................................94 • 2.7 Log Settings ...............................................................................................................97

2 Configuration Settings


2.1. Starting the Performance Monitoring Service

2.1.1. About the Performance Monitoring Service

In order to use System Monitor - Performance Monitoring Services functions, the Performance Monitoring Service must have started on the management server. The Performance Monitoring Service resides in the background as a Windows service. The Performance Monitoring Service startup type is "Automatic" by default, so it runs automatically when the OS starts.

2.1.2. How to Start the Performance Monitoring Service

Manually

The Performance Monitoring Service can be started and stopped manually. The procedure is as follows.

1. Start Services from the Administrative Tools in Control Panel. The Services window appears. Double-click "System Monitor Performance Monitoring Service" from the services list.

The System Monitor Performance Monitoring Service Properties window appears.

2. On the General tab, click Start. The Performance Monitoring Service will start.

Registering the Management Server

85

2.2. Registering the Management Server To register the management servers in the management console, complete the following steps: 1. Start the management console. See "3.1.2 Starting the Management Console" for

more information about starting the management console.

2. Select Add Management Server from the Tools menu in the management console.

3. The Management Server window appears. Enter the required items.

Enter the hostname or IP address of the connection destination management server from the keyboard for the Host name.

Note: The '\' character cannot be used in the Host name text box.

The User name and Password specified at management console startup are displayed for User name and Password. Change these when using a connection account that differs for each management server. The default value for Port Number (26200) is already set, so no input is required. See "2.4.1 Port Number" for more information on port numbers.

4. Click OK to add the management server to the management console. The management server name is displayed in the navigation tree window. Connection to the management server is also performed.

You can delete registered management servers from the navigation tree window. The connection from the management console to the management server is lost when the management server registration is deleted. However, Performance Monitoring Service operations are unaffected at disconnection. The Performance Monitoring Service continues to monitor according to its settings. For information on how to delete registered management servers, see "3.1.4 Specifying from the Navigation Tree Window".



2.3. Connection Settings to Managed Machines

2.3.1. Setting the Connection Account to the Managed Machine

Set the account name and password so that the Performance Monitoring Service can access the monitored machine. To register, complete the following steps: 1. Start the management console. See "3.1.2 Starting the Management Console" for

information about starting the management console. 2. Right-click the management server name from the navigation tree window in the

main window of the management console.

A popup menu appears.

3. Click Set Configuration. A Configuration window with the name of the server appears.

4. In the Connection tab, specify a new account and password, and then click OK. If the OS on the managed machine is Linux/KVM, select the correct connecting options in the Protocol and Authentication Protocol boxes. If Public key authentication is selected, then specify the path for the private key file in Key file path. The private key is stored on the management server. The Protocol and Authentication Protocol settings are ignored if the managed machine is VMware ESXi or Citrix XenServer.

See "1.7 Connecting to Managed Machines" for applicable rules for connection settings to Managed Machines, general notes for settings and managed machine side settings.

Connection Settings to the Management Console

87

2.4. Connection Settings to the Management Console

The connection settings between the management server (Performance Monitoring Service) and management console are explained below.

2.4.1. Port Number

System Monitor - Performance Monitoring Services uses port number 26200 for communications from the management console to the Performance Monitoring Service, and port number 26202 for communicating from the Performance Monitoring Service to the management console.

Performance Monitoring Service protocol Management console

26200 TCP assigned automatically

assigned automatically TCP 26202

If this port number is already being used by another product, this port number must be changed. The procedure for changing the port number is as follows:

◆ Changing the port number for the performance monitoring service 1. Start the management console, and then connect to the management server.

See "3.1.2 Starting the Management Console" for information on how to start the management console.

2. Right-click the management server name in the navigation tree window in the main window of the management console.


3. Click Set configuration. A Configuration window appears.

4. In the Port tab, specify a new port number, and click OK.



The connection between the Performance Monitoring Service and the management console must be restarted. The Performance Monitoring Service runs with the new port number when the Service is restarted.

Reconnect to the Performance Monitoring Service from the management console using the following procedure:

1. Right-click the management server name in the navigation tree window in the Main window of the management console. A popup menu appears.

2. Select Connection.

3. Click Set. 4. The Management Server window appears. Specify the changed port number

in the Port Number field and click OK to reconnect.

Connection Settings to the Management Console

89

◆ Changing the port number for the management console 1. Start the management console.

2. Click Set Management Console from the Tools menu. The Management Console window appears.

3. In the Port number box, specify a new port number, and then click OK.

When you click OK, the management console reconnects using the specified port number.

2.4.2. Firewall

If the management console is to be run on a machine other than the management server, the management console and the Performance Monitoring Service will connect using the network. If a firewall has been set up on the management server, then unblock the Performance Monitor Service.

◆ Performance monitoring service Unblock the performance monitoring service. Unblock settings can be made when System Monitor - Performance Monitoring Services is installed. If unblock settings were not made when this product was installed, perform the following procedure.

1. On the Start menu, point to Control Panel, and then click Windows Firewall, and click Advanced settings to open Windows Firewall with Advanced Security.

2. Select Inbound Rules in the pane left and from Actions in the pane right and select New Rule and click to open New Inbound Rule Wizard.

3. By following the wizard, add Inbound Rules.

1) In the Rule Type screen, select Program. 2) In the Program, select This program path and specify

bin\rm_pfmservice.exe, which is located under the destination folder.

3) In the Action screen, select Allow the connection. 4) In the Profile screen, select or clear the Domain, Private and Public

checkbox, according to your environment.

5) In the Name screen, specify System Monitor-Performance Monitoring Service.

6) Click Finish.



◆ Management Console Unblock the management console by using the following procedure:

1. On the Start menu, point to Control Panel, and then click Windows Firewall, and click Advanced Settings to open Windows Firewall with Advanced Security.



1) In the Rule Type screen, select Program.

2) In the Program, select This program path and specify bin\RM_PFMCONSOLE.exe, which is located under the destination folder.

3) In the Action screen, select Allow the connection. 4) In the Profile screen, select or clear the Domain, Private and Public


5) In the Name screen, specify System Monitor-Performance Monitoring Service.

6) Click Finish.

The Execution Account for the Performance Monitoring Service

91

2.5. The Execution Account for the Performance Monitoring Service

2.5.1. Setting up the Performance Monitoring Service Execution

Account

The Performance Monitoring Service runs as the local system account. This is the default setting. You can change the execution account for the Performance Monitoring Service from the local system account and configure it to use a specific account for the Performance Monitoring Service. If the OS for the monitored machine is Windows 2000, the execution account must be changed from the local system account. See "2.5.2 How to Change the Performance Monitoring Service Execution Account" for changing the execution account.

If all of the following conditions are satisfied, the Performance Monitoring Service accesses the managed machine using the execution account:

◆ The operating system for the managed machine is Windows.

◆ The execution account is changed from the local system account. ◆ The connection account for the managed machines is not specified (account field

is blank).

The execution account must satisfy the following conditions.

◆ The execution account for the Performance Monitoring Service must possess management server OS administrator rights. There are also rights required for settings in order to start the Performance Monitoring Service. See "2.5.3 Rights for the Performance Monitoring Service Execution Account" for rights required and settings for the Performance Monitoring Service execution account.

◆ Use an account that does not have a blank password.

2.5.2. How to Change the Performance Monitoring Service

Execution Account

The procedure for changing the execution account is as follows:

1. Start Services from the Administrative Tools in Control Panel. The Services window appears.

2. Double-click "System Monitor Performance Monitoring Service" from the list of services.

3. In the Log On tab, set up the account and password.



In the example above, the "administrator" account for the management server is specified as the execution account.

4. The new execution account will take affect when the Performance Monitoring Service is restarted.

2.5.3. Rights for the Performance Monitoring Service Execution

Account

When using an account besides the local system account as the execution account, the Performance Monitoring Service cannot start if the specified account does not have the following rights:

◆ Log on as a service If the execution account is changed, then this right must been assigned. To verify that this right has been assigned, complete the following steps:

1. On the Start menu, point to the Control Panel, and then click Administrative Tools.

2. Double-click Local Security Policy. The Local Security Settings window appears.

3. Click Local Policies.

The Execution Account for the Performance Monitoring Service

93

4. Select User Rights Assignment.

5. Double-click Log on as a service.

The Log on as a service Properties window appears.

6. Verify that either the execution account for the Performance Monitoring Service or

the group that the account belongs to is displayed. If it is not displayed, add it by clicking the Add User or Group button.



2.6. SystemProvisioning Connection Settings SystemProvisioning information must be set in order to use the SystemProvisioning configuration applying function or the performance abnormality notification function. You must configure these settings. The procedure for configuring these settings is as follows:

1. Start the management console and connect to the management server. See "3.1.2 Starting the Management Console" for information on how to start the management console.

2. Right-click the management server name from the navigation tree window in the main window of the management console. A popup menu appears.

3. Click Set configuration. The Configuration window appears.

4. Specify the Server name on which SystemProvisioning is installed from the SystemProvisioning tab. The default value is a server name of the management server.

5. To automatically apply SystemProvisioning configuration information, check the Apply SystemProvisioning Configuration automatically box, and set a polling interval between one and 1000 minutes. The default status for this check box is checked. The default polling interval is 10 minutes.

6. To set up a polling start time, check the Specify polling start time box, and then set the polling start time.

7. Click OK.

SystemProvisioning Connection Settings

95

If the Performance Monitoring Service and SystemProvisioning are not on the same management server, following settings are necessary:

◆ Windows Firewall setting If the Windows firewall has been enabled, make exception settings by using the following procedure:

1. On the Start menu, point to Control Panel, and then click Windows Firewall, and click Advanced settings to open Windows Firewall with Advanced Security.



1) In the Rule Type screen, select Port. 2) In the Protocol or port screen, select TCP (T) and Specific local ports

and specify 26102 for Specific local ports. 3) In the Action screen, select Allow the connection. 4) In the Profile screen, select or clear the Domain, Private and Public


5) In the Name screen, specify SystemProvisioning UniversalConnector. 6) Click Finish.



◆ Service execution account setting When both the Performance Monitoring Service management server and the SystemProvisioning management server are participating in the domain, the OS administrator account of the SystemProvisioning management server must be set as the execution account of System Monitor Performance Monitoring Service.

When not participating in the domain, the same account and password must exist in both the Performance Monitoring Service management server and the SystemProvisioning management server. Also, its account must be set as the log on account of System Monitor - Performance Monitoring Services. See "2.5 The Execution Account for the Performance Monitoring Service" for information on how to set the service execution account.

Log Settings

97

2.7. Log Settings The output settings of the debug log can be changed using the System Monitor Management Console. A log level, a maximum size of the log file and the log file generation count can be changed. A log level can be specified between '0' and '4'. The higher a log level becomes, the more detailed the log becomes. When '0' is set as a log level, no log is output. The default value of log level is '3'.

You can specify the maximum size of log files from range of 1 to 1024 MB. The default is 50 MB. When a debug log file size exceeds the maximum size, the file backs up automatically after compressing with the gzip format. With the gzip format, the file can be compressed to about 10% of its original size results in you can significantly reduce disk usage.

The maximum file count can be specified between 2 and 1000. The default value of log file size is 20.

The same as its debug log, the event log of System Monitor - Performance Monitoring Service is saved as an output file. You can estimate disk usage of the debug log file and the event log file as the following:

(The maximum size of the log file * 1 + (the maximum number of the log file - 1) * the maximum size of the log file * 10%) * 2

For example, if the maximum size is 50 MB and the maximum number is 20, the calculation result is (50 * 1 + (20 - 1) * 50 * 10%) * 2 = 290 MB. The procedure for configuring these settings is as follows:

1. Start the management console and connect to the management server. See "3.1.2 Starting the Management Console" for information on how to start the management console.

2. Right-click the management server name from the navigation tree window in the main window of the management console. A popup menu appears.

Click Set configuration. The Configuration window appears.

3. Specify the debug log level, the file size and the file count on the Log tab.

4. Click OK.



99

3. Basic Operations This chapter explains startup methods and basic GUI operations. This chapter contains the following sections: • 3.1 Starting the Management Console and Connecting to the Management Server ....100 • 3.2 The Main Window ....................................................................................................104

3 Basic Operations


3.1. Starting the Management Console and Connecting to the Management Server

3.1.1. About the Management Console

The management console is the user interface for the Performance Monitoring Service. Start the management console and connect to the management server to configure the Performance Monitoring settings. The management console can also graphically display performance data. You can connect to multiple management servers from one management console. This allows for central management of multiple management servers. Also, more than one management console can connect to the same Performance Monitoring Service at the same time. See "3.1.5 Notes on Operating with More than One Management Console" for more information.

3.1.2. Starting the Management Console

Start the management console to initiate the connection between the management console and the management servers. The execution account of the management console must possess OS administrator authority of the Monitoring terminal. The procedure for starting the management console is as follows:

1. Point to SigmaSystemCenter under the All Programs section of the Start menu, and then click System Monitor Management Console.

2. When no management server is registered in the management console, enter the necessary items into the Management Server window.

Enter the hostname/IP address of the management server into Host name, the port number used for connecting to the management server into Port number, the connection account to the management server into User Name and the password into Password.

Starting the Management Console and Connecting to the Management Server

101

When a management server is already registered in the management console, enter the necessary items into the Logon window. The account is used for connecting all management server registered in the management console.

Enter the connection account to the management server into User Name and the password into Password.

3. Click OK to start the connection to the management server.

Note: If the management console program is blocked by Windows Firewall, Windows Security Alert window may appear. See "2.4.2 Firewall" and unblock the management console program.

3.1.3. Connecting to the Management Server

Start the management console to begin a connection between the management servers and the management console. The management servers that are already registered in the management console are now connected. The user name and password specified at management console startup are used for connecting to the management server. Only users that have OS administrator authority for the management server can log on to the management server. To connect, the Performance Monitoring Service must be started on the management server. See "2.1 Starting the Performance Monitoring Service" for information on how to start the Performance Monitoring Service.

If no management server is registered in the management console, the Management Server window appears when the management console loads. In the Management Server window, add a management server. See "2.2 Registering the Management Server" for information on how to add management server.

3.1.4. Specifying from the Navigation Tree Window

From the navigation tree window, the following actions are possible:

◆ Connecting to/Disconnecting from the management server To disconnect from the management server, complete the following steps: 1. Right-click the management server name.


2. Select Connection. 3. Click Disconnect.

3 Basic Operations


◆ Reconnect to the management server 1. Right-click the management server name.


2. Select Connection. 3. Click Connect.

◆ Changing connection settings To change the connection settings to the management server, complete the following steps: 1. Right-click the management server name.


2. Select Connection. 3. Click Set.

A Management Server window appears. 4. Change the settings, and then click OK.

◆ Deleting management server registration To delete management server registration, complete the following steps: 1. Right-click the management server name.


2. Click Delete management server. A confirmation window appears.

3. Verify that the management server was deleted from the navigation tree window.

3.1.5. Notes on Operating with More than One Management

Console

With System Monitor - Performance Monitoring Services, more than one management console can connect to the same Performance Monitoring Service at the same time. If these settings are changed on one management console, the changes are reflected on all management consoles. The displayed performance status information will also change. The following settings are unique for each Performance Monitoring Service:

◆ Specifications for managed objects ◆ Specifications for the Performance Indicators to be collected ◆ Specifications for threshold monitoring information

◆ Pausing and restarting the collecting of performance data ◆ Configuration settings

Starting the Management Console and Connecting to the Management Server

103

Also, setting changes may not take effect if similar changes are made from another management console at the same time.

It is possible to start multiple management consoles on a single machine. However, in order for this to work correctly, the port numbers for each management console should be set to a different value.


Management console

Management console

Displaying performance

status

Applying

Applying


status

Changing settings

Applying

Management console


status


Management console

Changing settings

Management console

Changing settings

3 Basic Operations


3.2. The Main Window 3.2.1. The Structure of the Main Window

The main window is displayed when users start the management console. The System Monitor - Performance Monitoring Services main window is shown below.

3.2.2. Menu Bar

Each menu in the main window and its options are explained below.

◆ File menu • Exit

Closes the management console. ◆ View menu

• Tree Window Shows or hides the navigation tree window.

Menu bar Toolbar

Search view

Navigation tree window

Status bar Log window Graph display pane

The Main Window

105

• Tree Window Search View Shows or hides the Tree Window Search View.

• Toolbar Shows or hides the toolbar.

• Status bar Shows or hides the status bar.

• Log Window Shows or hides the Log window.

◆ Graph menu • New

Displays the Graph Setting window. Select this menu item to create a new graph. See "5 Performance Status Display and File Output" for more information on the Graph Setting window.

• Set Display Displays the Graph Setting window for the active performance graph window in the current graph display pane. Select this menu item to change the settings for a graph that is being displayed. See "5 Performance Status Display and File Output" for more information on the Graph Settings window.

• Output File Displays the Output Settings window. Select this menu item to output performance data displayed in the graph window. See "5.3 File Output" for more information on the Output Settings window.

◆ Tool menu • Add Management Server

Displays the Management Server window. Select this option when adding a management server. See "2.2 Registering the Management Server" for more information on the Management Server window.

• Change Connection Status of Management Servers You can select Connect to all or Connect to Management Servers with error status. Select Connect to all to connect to all management servers with error status or those that are disconnected. Select Connect to Management Servers with error status to connect to all management servers with error status.

• Change Data Collecting Status You can select Restart All or Pause All. Specify restart/pause Performance Monitoring Service for all connected management servers.

• Apply SystemProvisioning Configuration to All Configuration information on SystemProvisioning is applied to all connected management servers. Select this menu item to apply configuration information immediately, regardless of periodic application performed by the automatic applying function.

3 Basic Operations


• Set Management Console Displays the Management Console window. See "2.4 Connection Settings to the Management Console" for more information on the Management Console window.

◆ Window menu • Cascade

Arranges the performance graphs so they overlap.

• Tile Horizontally Arranges the performance graphs horizontally.

• Tile Vertically Arranges the performance graphs vertically.

• A list of performance graphs that are being displayed Performance graphs that are being displayed are listed. The selected performance graph is activated.

◆ Help menu • Version Information

Displays version information for System Monitor - Performance Monitoring Services.

3.2.3. The Toolbar

Each tool button in the main window is explained below.

◆ Add Management Server tool button

Displays the Management Server window. Select when adding a management server. See "2.2 Registering the Management Server" for more information on the Management Server window.

◆ Restart Collecting Performance Data tool button

Restarts the Performance Monitoring Service for all connected management servers.

◆ Pause Collecting Performance Data tool button

Pauses the Performance Monitoring Service for all connected management servers.

◆ Apply SystemProvisioning Configuration to All tool button

Applies configuration information from SystemProvisioning to all the connecting management servers. Select this tool button to apply configuration information immediately, regardless of periodic application performed by the automatic applying function.

The Main Window

107

◆ Create a Graph tool button

Displays the Graph Setting window. Select this tool button to create a new graph. See "5 Performance Status Display and File Output" for more information on the Graph Setting window.

3.2.4. The Navigation Tree Window

Management servers and monitored machines are displayed in the navigation tree window. Operations for management servers such as collecting data settings and adding monitored machines are performed from the navigation tree window. See "3.2.5 Popup Menu for Management Server" for navigation tree window operations for each management server.

3.2.5. Popup Menu for Management Server

◆ Connection Specifies connect to/disconnect from the management server. Set menu displays Management Server window. See "2.2 Registering the Management Server" for more information on the Management Server window.

◆ Delete Management Server Deletes management server registration.

◆ Collecting Data Select the Set Performance Indicator Settings menu or the Set Collecting Data Settings menu. If the Set Performance Indicator Settings menu is selected, the Performance Indicator List window appears. Custom performance indicator setting can be added or modified on the Performance Indicator List window. If the Set Collecting Data Settings menu is selected, the Collecting Data Setting List window appears. You can specify which node and performance indicator should be monitored on the Collecting Data Setting List window. See "4.2 Specifications for the Performance Data to be collected" for more information about each window.

◆ Set Threshold Monitor Displays the Set Threshold Monitor window. See "6.1 Configuring Threshold Monitoring" for more information on the Set Threshold Monitor window.

◆ Change Data Collecting Status Specifies restart/pause Performance Monitoring Service for the management servers. You can select Restart or Pause.

◆ Apply SystemProvisioning Configuration Applies configuration information from SystemProvisioning to the management server. Select this menu to Apply configuration information immediately, regardless of periodic application performed by the automatic applying function.

3 Basic Operations


◆ Set Configuration Displays the Configuration window. See "2 Configuration Settings" for more information on the Configuration window.

◆ Add Group Displays the Group Settings window. See "4.1.1 Specifications in the Navigation Tree Window" for more information on the Group Settings window.

◆ Display Graph Creates a real-time graph using the simple graph display function. See "5.1.3 Simple Graph Display Function" for more information on the Simple graph display function.

3.2.6. Search View

Select Tree Window Search View from the View menu to display search view. Enter search character strings to the text box then click Search. When there is a node name partially matching to the search character string in the navigation tree window, the corresponding node switches to select status. Click Search again to switch the next corresponding node to select status. The search sequence is performed from the top of the navigation tree to the bottom of the navigation tree. When there are no corresponding nodes, the select status on the navigation tree window is not changed.

3.2.7. The Graph Display Pane

Performance graph windows are displayed in the graph display pane. See "5 Performance Status Display and File Output" for more information on the display content.

3.2.8. Log Window

Events that occur in Performance Monitoring Service and the management console are displayed in the Log window. Right-click in the log window area, and then click Setting. The Log Settings window appears. You can specify the contents to be displayed in the Log window in the Log Settings window. The line count to be displayed ranges from zero to 1000 lines, which can be specified in one-line units.

The Main Window

109

If you want to copy a log, select the log on the log window, right-click on the log window area and click Copy from the pop-up menu. You can save the log easily and quickly by copying and pasting the log into other file.

3.2.9. The Status Bar

The current time is displayed in the status bar.

111

4. Collecting Performance Data This chapter explains how to make settings relating to collecting performance data. This chapter contains the following sections: • 4.1 Specifications for Managed Machines .....................................................................112 • 4.2 Specifications for the Performance Data to be collected .........................................125 • 4.3 Pausing and Restarting the Collecting of Performance Data ..................................141 • 4.4 Checking the Collecting Status for Performance Data ............................................142

4 Collecting Performance Data


4.1. Specifications for Managed Machines 4.1.1. Specifications in the Navigation Tree Window

If managed objects are machines, in addition to registering it to System Monitor - Performance Monitoring Services automatically at the timing of performing the applying configurations feature of SystemProvisioning, you can also registering it from the System Monitor Management Console as shown in the following. Please note that if you use this registering method, you cannot use the SystemProvisioning linkage function. Additions, deletions and changes to managed machines are performed from the navigation tree window of the main window. Managed machines are configured for each management server.

System Monitor - Performance Monitoring Services manages managed machines in groups called "groups". Performance status information can be displayed for the entire group, so you must register groups of machines whose performances need to be monitored collectively as groups.

The following section explains how to register machines and groups. 1) Initial State

When there are registered servers, the management server name and group are displayed in the navigation tree window. The default name for the default group is "Group1".

Specifications for Managed Machines

113

2) Adding, Changing and Deleting Machines

◆ Adding Machines The procedure for adding machines to a group is as follows:

1. Right-click the group name. A popup menu appears.

2. Click Add Machine.

3. The General tab on Machine Settings window appears.

• Enter the host name or IP address for the machine in the Machine

Name text box. (Required)

Note： The '\' character cannot be used in the Machine Name text box.

• To set the IP address explicitly, enter the IP address in the IP Address text box. (Optional) If an IP address has been set up, the specified IP address is used to connect to this machine from the management server. An IP address only can be set up if the Apply IP address information to machines when applying SystemProvisioning Configuration box has not been checked in the Group Settings window. If the Apply IP address information to machines when applying SystemProvisioning Configuration box has been checked, then the IP address that was acquired from SystemProvisioning when SystemProvisioning configuration was applied is set up automatically. Windows and Linux support both IPv6 and IPv4 addresses. Other operating systems than Windows and Linux support IPv4 addresses only.



• Select the appropriate OS from the OS name list.

The OS Name list can only be set if the Apply SystemProvisioning Configuration box has not been checked in the Group Settings window. If the Apply SystemProvisioning Configuration box has been checked, then the OS name that was acquired from SystemProvisioning when SystemProvisioning configuration was applied is set up automatically.

• For Weight, specify a weighting for the machine between 0.0 and 10000.0. (Optional)

Set the Weight for this machine if you want the weighted average value statistic to be used.

• In the Memo field, enter in a memo or note to be displayed for the machine. (Optional)

4. Click the Connection tab and perform connection settings. When using connection settings of group, set the checkbox to ON. When performing connection settings individually, set the checkbox to OFF and specify the account/password.

When the managed machine OS is Windows, select Windows OS Account or SSH Account (only for script collection) according to your purposes.

• Specify the account information for performance data collecting with performance counters in Windows OS Account.

• Specify the account information for performance data collecting with scripts in SSH Account (only for script collection).

For the SSH user account in Windows or when the managed machine OS is Linux/KVM, select the protocol to be used for connection and the authentication method. When public key authentication method is selected, specify the full path name of the private key file stored in the Management Server. See "1.7 Connecting to Managed Machines" for applicable rules for connection settings to managed machines, general notes for settings and monitored machine side settings.


115

• When Managed Machine OS is Windows

• When Managed Machine OS is Linux or KVM



• When Managed Machine OS is VMware ESXi

• When Managed Machine OS is Citrix XenServer

5. Click the OK button when settings are completed.


117

6. Verify that the machine has been added to navigation tree window.

◆ Deleting Machines The procedure for deleting machines is as follows: 1. Right-click the machine name.


2. Click Delete Machine. A window appears to confirm that you want to delete the machine.

3. Click Yes. 4. Verify that the machine has been deleted from the navigation tree

window.

The machine is deleted from the navigation tree window, but information will still be stored in the database (for a storage period of one month). If a machine with the same machine name is added, the configuration will revert to the former state (the data stored in the database will become valid).

◆ Confirming or Modifying Machine Settings The procedure for confirming or modifying machine settings is as follows:

1. Right-click the machine name. A popup menu appears.

2. Click Machine Settings.

The Machine Settings window appears. 3. Confirm the machine settings. Enter the new machine settings if

necessary. The information on Summary tab in the Set server window is displayed based on SystemProvisioning configuration information. See "1.10.2 Applying System Configuration Information" for information on applying SystemProvisioning configuration information.

Note: The settings applied from SystemProvisioning are grayed out on this window. These settings cannot be modified. The settings on SystemProvisioning should be modified if necessary.

4. Enter the other new machine settings if necessary and Click OK. Verify that the new settings were applied if they were modified.

A monitored machine, which is reflected to System Monitor-Performance Monitoring Service through applying SystemProvisioning configuration, utilizes the account name/password configured in SystemProvisioning by default. If you want use the account name/password configured in System Monitor-Performance Monitoring Service, clear the Use connection setting of SystemProvisioning check box and execute the connection setting.



If you utilize the account name/password configured in SystemProvisioning, select the Use connection setting of SystemProvisioning check box.


119

Note: When the application of SystemProvisioning configuration information is performed, the access account which is specified on SystemProvisioning is applied to the machine settings of System Monitor - Performance Monitoring Service.

◆ Moving Machines The procedure for changing which group a machine belongs to is as follows: 1. Right-click the machine name.


2. Click Move machine. The Move Machine window appears. It contains a list of groups.

3. Select the new group from the window.

4. Click OK. 5. Verify that the machine has been moved to the new group in the

navigation tree window. You can also drag and drop the machine name to a different group, but you cannot move a machine to the group of another management server.

3) Adding, Changing and Deleting Groups

◆ Adding Groups The procedure for adding groups is as follows:

1. Right-click the management server. A popup menu appears.

2. Click Add Group.

3. The General tab on Group Settings window appears.



• Enter the name for the group in the Group Name field. (Required)

Note: The '\' character cannot be used in the Group Name field.

• To apply configuration information for SystemProvisioning on to the group that is being set up, check the Apply SystemProvisioning Configuration box and specify the path for the appropriate SystemProvisioning group/model in the Path text box. To apply IP address information to subordinate machines when configurations are applied, check the Apply IP address information to machines when applying SystemProvisioning Configuration box. (Optional)

• In the Memo field, enter in a memo or note to be displayed for the group. (Optional)

4. Click the Connection tab and perform connection settings. When using connection settings of the Configuration window, set the checkbox to ON. When performing connection settings individually, set the checkbox to OFF and specify the account/password. When the managed machine OS is Linux, select the protocol to be used for connection and the authentication method. When public key authentication method is selected, specify the path name of the private key file stored in the management server. See "1.7 Connecting to Managed Machines" for applicable rules for connection settings to managed machines, general notes for settings and monitored machine side settings.


121

5. Click the OK button when settings are completed. 6. Verify that the group has been added to the navigation tree window.

◆ Deleting Groups

The procedure for deleting groups is as follows: 1. Right-click the group.


2. Click Delete Group. A window appears to confirm that you want to delete the group.

3. Click Yes. 4. Verify that the group has been deleted from the navigation tree window.

Note: Performance data for groups that have been deleted becomes unusable. The performance status from before the deletion will not be displayed even if a group with the same name is added.



◆ Confirming or Modifying Group Settings The procedure for confirming or modifying group settings is as follows: 1. Right-click the group name.


2. Click Group Settings. The Group Settings window appears.

3. Confirm the group settings.

If the performance data collecting setting is enabled on the Performance Monitor settings about the corresponding group/model on SystemProvisioning, an access account can be configured there.

An access account can be configured on the Connection settings for each node on System Monitor - Performance Monitoring Service as well. You can select which account is used as an access account for this group. In order to use the access account specified on SystemProvisioning, set the Use connection setting of SystemProvisioning box to ON.

Note: When the application of SystemProvisioning configuration information is performed, the access account which is specified on SystemProvisioning is applied to the group settings of System Monitor - Performance Monitoring Service.

In order to use the access account specified on System Monitor - Performance Monitoring Service, set the Use connection setting of SystemProvisioning box to OFF and set the connection settings.


123

4. Enter the other new group settings if necessary and click OK. 5. Verify that the new group settings were applied if they were modified.

4.1.2. How to Apply SystemProvisioning Configuration

Information

SystemProvisioning configuration information can be applied to System Monitor - Performance Monitoring Services. Information can be applied manually or automatically. With the automatic applying function, System Monitor - Performance Monitoring Services communicates with SystemProvisioning at regular intervals, and automatically applies any changes to its configuration information.

◆ Applying SystemProvisioning Configurations Manually The procedure for applying SystemProvisioning configurations is as follows:

1. Select Apply SystemProvisioning Configuration to All from the Tools menu, or click on the Apply SystemProvisioning Configuration to All tool button. A window appears to confirm whether the SystemProvisioning configuration should be applied.

2. Click Yes. 3. Verify that the configuration has changed in the navigation tree window.



◆ Applying SystemProvisioning Configurations Automatically The setup procedure to apply SystemProvisioning configurations automatically is as follows:

1. Right-click the management server in the navigation tree window and click Set Configuration. The Configuration window appears.

2. In the SystemProvisioning tab, set the required items and click OK. See "2.6 SystemProvisioning Connection Settings" for more information.

3. Verify that every time SystemProvisioning is polled, any configuration changes that have been made are applied in the navigation tree.

Note: For some system configurations, there are cases where it is not possible to connect to monitored machines using the IP addresses acquired from SystemProvisioning configuration information. If a monitored server produces an error, disable Apply the IP address information function and set the IP address manually using the Set server window, DNS or the "hosts" file.

Specifications for the Performance Data to be collected

125

4.2. Specifications for the Performance Data to be collected

4.2.1. How to Specify Performance Indicator Settings

System Monitor - Performance Monitoring Services can collect performance data for the custom performance indicator as well as the built-in performance indicator. To specify performance indicator, complete the following steps:

1. Right-click the management server in the navigation tree window. A popup menu appears.

2. Click Collecting Data menu.

3. Click Set Performance Indicator Settings menu. The Performance Indicator List window appears.

The performance indicators written in "1.3.2 Built-in Performance Indicator" are registered as default settings. When you want to create a new performance counter except the built-in performance counter for the Windows machines and the ESXi virtual machine servers and virtual machines, or when you create a new scripted performance indicator for Windows or Linux machines, you can create it as the custom performance indicator.



◆ Adding Performance Indicators The procedure for adding new Custom Performance Indicators is as follows:

• Performance Counters 1. Click the Add Performance Counter button on the Performance

Indicator List dialog box. 2. The Performance Indicator Settings dialog box appears. It displays all

managed objects monitored by System Monitor - Performance Monitoring Services in the tree. The management server/node is selected and performance counter setting is disabled by default.

3. Select the source object node from the Object Node list to collect the information from the operating system on the selected node, and to set up performance counters.


127

4. Specify Type of Performance Counter. For VMware ESXi virtual machine servers, you can specify only

"VMware Esx Host". The "VMware Esx Host" obtains only performance data which a

virtual machine server can obtain from VMware ESXi.

For VMware ESXi virtual machines running Windows, You can specify both "VMware Esx Guest" and "Windows". For VMware ESXi virtual machines running other operating systems than Windows, you can specify "VMware Esx Guest" only. The "VMware Esx Guest" obtains performance counters which a

virtual machine can obtain from VMware ESXi.

The "Windows" obtains performance counters which Windows can obtain.

For other machines running Windows than VMware ESXi virtual machines, you can specify "Windows" only.

In all other cases, the performance counter is set to "Disable" and cannot be configured.

5. Click Get Counter. The list of performance counter information which can be configured on the selected object node is obtained and displays each performance counter information in "Performance Counter (Windows) / Metric Group (VMware ESXi)", "Counter", and "Instance (Windows) / Object (VMware ESXi)".



Note: It takes some time to initially obtain the performance counter information from managed machines running Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008 R2. This temporally causes lock condition in the System Monitor - Performance Monitoring Services console or might cause the time-out. If the process timed-out, click Get Counter to retry the process.

6. Select the resource you want to use from Performance Counter (Windows) / Metric Group (VMware ESXi), the counter from Counter, the instance from Instance (Windows) / Object (VMware ESXi) respectively. You can select multiple counters, instances (Windows), and objects (VMware ESXi) and add them in bulk. When you want to select or cancel the selection of multiple counters, instances (Windows), and objects (VMware ESXi) click Select All or Clear All.

7. Multiple performance indicators in Performance Counter (Windows) or Metric Group (VMware ESXi) can be configured by repeating the actions in step 6. When you are finished configuring the settings, click Close.

8. Click Apply All in the Performance Indicator List window to apply these settings to all the connected management servers.


129

• User Scripts 1. Click Add Executing Script button on the Performance Indicator List

dialog box.

2. The Performance Indicator Settings dialog box appears.

3. Specify a performance indicator: Type the title of the performance indicator. (Required)

Type the execution string into Executing String (Required)

Type the description of the performance indicator into Description. (Optional)

4. Confirm that the specified performance indicator is added to the performance indicator list.

5. Multiple performance indicators can be configured by repeating the actions in step 3. When you are finished configuring the settings, click Close.


Notes: ▪ Collecting performance data is not started only by adding the performance indicator settings to the performance indicator list. For data collection settings, see "4.2.2 How to Specify Collecting Data Settings". ▪ If Apply All is executed, the settings which had been already specified on other management servers connecting with the management console will be overwritten.



◆ Deleting Performance Indicators The procedure for deleting Performance Indicators is as follows:

1. Display the Performance Indicator List window. 2. Select the Performance Indicator item to be deleted from the Performance

Indicator list. You cannot delete the built-in performance indicator.

3. Click Remove. 4. Verify that the Performance Indicator item was deleted from the Performance

Indicator list.

Note: Performance data that has been deleted becomes unusable. The performance status from before the deletion will not be displayed even if the same settings are made again.

◆ Changing Performance Indicators The procedure for changing Performance Indicators is as follows:

• Performance counters 1. Display the Performance Indicator List window. 2. Select the Performance Indicator item to be changed from the

Performance Indicator list. Built-in performance indicators cannot be modified.

3. Click Modify. 4. The Performance Indicator Settings window appears.

5. Modify the Performance Indicator settings, and then click OK.


131


• User scripts 1. Open the Performance Indicator List dialog box. 2. Select the custom performance indicator that you want to modify from the

Performance Indicator List. Built-in performance indicators cannot be modified.

3. Click Modify.

4. The Performance Indicator Setting of the performance indicator to be modified appears.

5. Modify the performance indicator settings, and then click OK. 6. Click Apply All in the Performance Indicator List window to apply these

settings to all the connected management servers.

Note: If Apply All is executed, the settings which had been already specified on other management servers connecting with the management console will be overwritten.

4.2.2. How to Specify Collecting Data Settings

System Monitor - Performance Monitoring Services periodically collects performance data for managed objects. The Performance Indicators that are collected can be specified for each management server, for each group or for each managed object. The settings for collecting performance data from the managed object can be specified on the Collecting Data Setting List window by assigning the collecting data settings to the object node. The procedure for specifying settings for collecting performance data is as follows:



1. In the navigation tree window, right-click the management server, group or monitored machine that you want to configure the settings, and select Collecting Data. Click Set Collecting Data Settings menu. The Collecting Data Setting List window appears.

2. Select a node in the Object node list and the current settings for the selected node can be seen in the Collecting data setting list. It is set as inheriting from the parent node's settings by default.

3. To modify the settings for the selected node, clear the Inherit from parent settings box.


133

4. To add a collecting data setting to the list for the selected node, click Add. To remove a collecting data setting from the list for the selected node, select the setting to be removed and click Remove. To modify a collecting data setting, select the setting to be modified and click Modify.

Note: If the collecting data setting which is target of threshold monitoring is deleted, the threshold monitoring is stopped. But the corresponding threshold monitor settings are not deleted automatically. If necessary, delete these threshold monitor settings manually on the Set Threshold Monitor window. See "6.1.1 How to set up threshold monitoring" for details on the Set Threshold Monitor window.



5. Add or modify the collecting data setting performing the following procedure.

◆ Adding the collecting data setting ① The Collecting Data Settings window appears when Add is clicked.

② Specify the collecting data settings to be added.

• Select a resource name of the collecting data setting to be added or modified in the Resource list. To specify the custom performance indicator, select "Other".

• Select a performance indicator name of the collecting data setting to be added or modified in the Performance indicator list. You can select multiple performance indicators and add them in bulk. When you want to select or cancel the selection of multiple performance indicators, click Select All or Clear All. When the specified resource has performance indicator too many, you can use the search feature to find out them easily. Type a search string into the text box and click Search, then the performance indicators that contain the search string in their title are listed in the Performance indicator list.

• Select an interval of the collecting data setting to be added or modified in the Collecting interval list.

③ Click Add.


135

◆ Modifying the collecting data setting ① The Collecting Data Settings window appears when Modify is clicked.

② Specify the collecting data settings to be modified.

• Select a resource name of the collecting data setting to be modified in the Resource list. To specify the custom performance indicator, select "Other".

• Select a performance indicator name of the collecting data setting to be modified in the Performance indicator list.

• Select an interval of the collecting data setting to be modified in the Collecting interval list.

③ Click OK.



6. Verify that the new settings were applied to the list on the Collecting Data Settings List window.

7. Click OK. The following four performance indicators are the default settings:

Performance Indicator Location Collecting Interval

CPU Usage (%) Root 1 minute

Disk Transfer Rate (Bytes/sec) Root 1 minute

Disk Space (MB) Root 1 minute

Physical Memory Space (MB) Root 1 minute

Notes: ▪ The function of collecting performance data from Windows machine will not perform when the specified collecting interval is a day or longer. It is necessary for collecting performance data from Windows machine that a shorter interval than a day is specified as collecting interval.

▪ When you collect performance data from VMware ESXi, specify one hour and under as collecting interval. If you specify more than one hour, the specified performance data collecting for VMware ESXi machines or virtual machines on VMware ESXi, will not be performed.


137

4.2.3. Collecting Data Settings Automatically Applied by

SystemProvisioning Linkage

<Machines> For applying the settings on SystemProvisioning to System Monitor - Performance Monitoring Services automatically, it is necessary to specify the monitoring profile and enable the performance data collection settings on the group/model/host.



<Resource Pools> By configuring monitoring profiles in the registry to enable the monitoring performance feature, you can apply the data collection settings of resource pools to System Monitor - Performance Monitoring Services automatically.


139

<LUNs in NEC Storage> By configuring monitoring profiles in the registry to enable the monitoring performance feature, you can apply the data collection settings of disk arrays and logical disks to System Monitor - Performance Monitoring Services automatically.



<SigmaSystemCenter Managed Objects> The data collection settings are automatically applied to the SigmaSystemCenter Managed Objects of System Monitor - Performance Monitoring Services by configuring monitoring profiles in the registry to enable the monitoring performance feature.

Applied collecting data settings from SystemProvisioning to System Monitor - Performance Monitoring Services are listed in blue in the Collecting Data Setting List window.

It is impossible to delete or modify the applied collecting data settings, but it is possible to add other collecting data settings to the list for the automatically applied node.

Pausing and Restarting the Collecting of Performance Data

141

4.3. Pausing and Restarting the Collecting of Performance Data

System Monitor - Performance Monitoring Services can pause and restart the collecting of the performance data. To pause all performance data collection on all managed machines, select Change Data Collecting Status and then click Pause All from the Tool menu. To restart the collection of performance data, select Change Data Collecting Status and then click Restart All from the Tool menu. Performance data collecting can also be paused for the management server, the group or the managed object. To do this, complete the following steps: 1. In the navigation tree window, right-click the management server, group or

managed object that you want to pause.

2. Click Change Data Collecting Status 3. In the submenu that appears, click Pause. To restart the service, complete the following steps: 1. In the navigation tree window, right-click the management server name, group

name or managed object name. A popup menu appears.

2. Select Change Data Collecting Status. 3. Click Restart.



4.4. Checking the Collecting Status for Performance Data

The collecting status for performance data is displayed in the navigation tree window of the main window. The collecting status can be checked by looking at the icons in the tree display that shows the collecting status (the status can be any of the following: "collecting", "paused" or "error") for each management server, group or managed objects.

The meaning of each icon is as follows:

◆ Management Servers

Connected to the management server, data is being collected normally for all machines under the management server

Disconnected from the management server

Connection Error

Connected to the management server, data collecting for all machines under the management server has been paused

Connected to the management server, data collecting for a machine or machines under the management server has been paused

Connected to the management server, data collecting failed for a machine or machines under the management server

Connected to the management server, data is being collected normally for all machines under the management server and an over-threshold status has occurred

Checking the Collecting Status for Performance Data

143

Connected to the management server, data collecting for a machine or machines under the management server has been paused and an over-threshold status has occurred

Connected to the management server, data collecting failed for a machine or machines under the management server and an over-threshold status has occurred

◆ Managed Machines

Data is being collected

Data collecting has been paused

Collecting failed for some Performance Indicator items (performance indicator error status)

The machine cannot be accessed or collecting failed for all Performance Indicator items (access error status)

Data is being collected, and an over-threshold status (warning) has occurred

Data is being collected, and an over-threshold status (critical) has occurred

Collecting failed for some Performance Indicator items, and an over-threshold status (warning) has occurred

Collecting failed for some Performance Indicator items, and an over-threshold status (critical) has occurred

◆ Managed Machine Groups

Data is being collected normally for all machines in the group

Data collecting for the group has been paused

Data collecting for a machine or machines in the group has been paused

Collecting failed for some Performance Indicator items for a machine or machines in the group

A machine in the group cannot be accessed or collecting failed for all Performance Indicator for a machine or machines in the group



Data is being collected normally for all machines in the group and an over-threshold status (warning) has occurred

Data is being collected normally for all machines in the group and an over-threshold status (critical) has occurred

Data collecting for a machine or machines in the group has been paused and an over-threshold status (warning) has occurred

Data collecting for a machine or machines in the group has been paused and an over-threshold status (critical) has occurred

Collecting failed for some Performance Indicator items for a machine or machines in the group and an over-threshold status (critical) has occurred

One or more machines in the group cannot be accessed or collecting failed for all Performance Indicators for a machine in the group, and an over-threshold status (warning) has occurred

One or more machines in the group cannot be accessed or collecting failed for all Performance Indicators for a machine in the group, and an over-threshold status (critical) has occurred

One or more machines in the group cannot be accessed or collecting failed for all Performance Indicators for a machine in the group, and an over-threshold status (critical) has occurred

◆ Resource Pool




Collecting failed for all Performance Indicator items (access error status) ◆ Resource Pool Group

Data is being collected normally for all resource pools in the group


Data collecting for a resource pool or resource pools in the group has been paused

Checking the Collecting Status for Performance Data

145

Collecting failed for some Performance Indicator items for a resource pool or resource pools in the group

A resource pool in the group cannot be accessed or collecting failed for all Performance Indicator for a resource pool or resource pools in the group

◆ LUN




Data collecting for a resource pool or resource pools in the group has been paused

◆ DiskArray

Data is being collected normally for all LUNs in the group


Data collecting for a LUN or LUNs in the group has been paused

Collecting failed for some Performance Indicator items for a LUN or LUNs in the group

A resource pool in the group cannot be accessed or collecting failed for all Performance Indicator for a LUN or LUNs in the group

◆ SigmaSystemCenter Managed Objects




Collecting failed for all Performance Indicator items (access error status) ◆ SigmaSystemCenter Managed Object Groups

Data is being collected normally for all resource pools in the group




Data collecting for SigmaSystemCenter Managed Object(s) in the group has been paused

Collecting failed for some Performance Indicator items for SigmaSystemCenter Managed Object(s) in the group

A SigmaSystemCenter Managed Object in the group cannot be accessed or collecting failed for all Performance Indicator for SigmaSystemCenter Managed Object(s) in the group

147

5. Performance Status Display and File Output

This chapter explains how to make settings relating to displaying performance status. This chapter contains the following sections: • 5.1 Displaying Performance Graphs ..............................................................................148 • 5.2 Saving Performance Status Display Specifications .................................................160 • 5.3 File Output ...............................................................................................................161

5 Performance Status Display and File Output


5.1. Displaying Performance Graphs System Monitor - Performance Monitoring Services displays performance data for the system graphically. Displaying performance data graphically enables trends to be identified intuitively, and makes it easier to analyze the operational status of the system.

Graphs of Performance Indicators that are currently being collected can be displayed for each management server, for each group or for each individual managed object. See "5.1.1 How to Display Performance Graphs" for more information about displaying the Performance Indicator graphs. Also, see "5.1.3 Simple Graph Display Function" for information on the use of the simple graph display, which uses default values. See "5.3 File Output" for methods to output performance data displayed in a graph to CSV or other files.

5.1.1. How to Display Performance Graphs

Performance graphs are displayed based on performance data. The Performance Indicators must be configured prior to use. Specify graph displays using the following procedure:

1. Select New from the Graph menu or click the Create a Graph icon. The Graph Setting window appears.

Displaying Performance Graphs

149

2. Enter a graph title in the Graph Title box. A title is automatically generated if the Generate Graph Title Automatically box is checked. (Required)

3. Select which contents to display in the graph by using the Display Object tab. Articles for Select Item for Comparison, Nodes, Performance Indicators and Statistics are displayed in the Display Object tab. You can select multiple items for whichever choice you pick in the Item for Comparison area, and select one item in the other articles. For example, if you select Nodes in the Item for Comparison area, you can select multiple nodes in the Nodes article and one Performance Indicator in the Performance Indicators article and one statistic in the Statistics article. At least one item must be selected. (Required)

Note: In Performance Indicators, do not specify indicators that are not collecting targets. If you specify the indicators, the graphs of 1 minutes plotting intervals may be displayed slow.

4. To add nodes to the Nodes column, click Add.

A Browse nodes window appears. Select the nodes you want to add, and click OK.

5. Click the Horizontal Axis tab, and make specifications relating to the time axis. The settings that are made here depend on which display period was specified (Historical or Realtime). For Historical graphs, make the following specifications:

Display period

Specify the Start time and Period. Start time specifies when the graph will start displaying data, and Period specifies the period of time of which the data is displayed in the graph.

Period can be specified between one and 1000 and in the following units: minutes, hours, days, weeks, months, or years. You can specify Start time to start before the current time by checking the Start time is specified period before current time box.

Plotting interval Specify individual settings or automatic settings. For individual settings, the following time periods can be specified: 1 minute, 5 minutes, 30 minutes, 1 hour, 4 hours, 1 day, 1 week, or 1 month.

Gridlines Select automatic settings or individual settings for the gridline interval. For individual settings, the Major and Minor gridline intervals can be specified between one and 1000 and in the following units: minutes, hours, days, weeks, months, or years.

◆ For Realtime graphs, make the following specifications: Display period: The display period can be specified between 1 and 1000.

You can specify "minutes", "hours", "days", "weeks", "months", or "years" for the units.



Polling interval for updating data: You can specify "1 second", "5 seconds", "20 seconds", "1 minute", "5 minutes", "20 minutes", "1 hour", "4 hours", or "1 day" for the graph update interval

Plotting interval Specify individual settings or automatic settings. For individual settings, the following time periods can be specified: 1 minute, 5 minutes, 30 minutes, 1 hour, 4 hours, 1 day, 1 week, or 1 month.

Gridlines: Select either automatic settings or individual settings for the gridline interval. For individual settings, the Major and Minor gridline intervals can be specified between 1 and 1000. You can specify "minutes", "hours", "days", "weeks", "months", or "years" as the unit for the gridline interval.

6. Use the Vertical Axis tab on the Graph Setting window to change graph vertical

axis values from their default setting. The following specifications can be made:

◆ Display range Specify the upper- and lower-bounds between zero and 1000. The default upper-bound is 100, and the default lower-bound is zero.


151

◆ Gridlines Select either automatic settings or individual settings for the graduation interval. For individual settings, uncheck the automatically set gridlines display interval box and then specify the Major and Minor gridline intervals. The gridline intervals can be specified between one and 1000.

◆ Scale Select either automatic settings or individual settings for the Performance Indicator in the list box. The default behavior is for the scale to be set automatically. For individual settings, check the Set the scale box and select a scale for each Performance Indicator item as 10 to the nth power (where n is an integer between -10 and 10). The data values are multiplied by the specified scale. The scale should be set so that the data values fit within the vertical axis of the graph.

7. Use the Color and Line tab to modify the graph color and line settings from their default values.

The following specifications can be made:

◆ Graph lines



Select the graph feature that you want to modify from the Object list, and then specify Color, Line type and Width.

◆ Graph construction lines Specify Color, Line type (only for gridlines) and Width for the Vertical axis, Horizontal axis, Graph frame, and Major and Minor gridlines.

◆ Background Select the graph feature that you want to modify from the Object list. You can specify the colors for the following: the background of plotting area; the background of graph; the upper-limit critical area; the upper-limit warning area; the lower-limit critical area; and the lower-limit warning area.


153

8. Use the Threshold Display tab to specify graph thresholds.

① Check the Display threshold area box. ② Click Browse.

The Browse threshold definition window appears.



③ Select a threshold definition from the Threshold definition list, and then click OK to apply the threshold contents to the Threshold Display tab.

④ You can also manually specify each value for displaying threshold areas. To do so, you need to specify Performance Indicator title for using scale too.

9. After making these specifications, click OK. 10. Verify that your changes are reflected in the performance graph that is displayed in

the graph display pane.

5.1.2. Graph Window

Graph Window displayed on Graph Display Pane is explained below.

Graph Summary List

Graph


155

◆ Graph • Line Graph

Target data is displayed in line graph.

• Vertical Axis The vertical axis range of the graph is configured in Vertical Axis tab on Graph Setting Window.

• Horizontal Axis The horizontal axis range of the graph is configured in Horizontal Axis tab on Graph Setting Window.

• Threshold area The threshold areas on the graph are configured in the Threshold Display tab on Graph Setting Window and the colors of them are configured in Color and Line tab on Graph Setting Window.

◆ Graph Summary List • Node Name / Performance Indicator / Statistics

Target object names displaying as a graph are displayed. The settings in Display Object tab on Graph Setting Window are displayed.

• Color / Line Type Colors and line types used for displaying a graph are displayed. The settings in Color and Line tab on Graph Setting Window are displayed.

• Latest Value / Maximum Value / Average Value / Minimum Value Latest value, maximum value, average value and minimum value of the graph line currently shown on Graph Window are displayed.

• Scale Scale used to display the graph. Raw data values multiplied by the value of the scale are displayed in the graph. The specified setting is displayed when the scale is specified manually in Vertical Axis tab on Graph Setting Window. When automatical scale setting is enabled, an adjusted scale to display a whole graph within a default vertical display range of 0 to 100 is displayed.

Note: Scale is updated in real time when automatic scale setting is enabled. Shape of the graph will be changed when the scale is updated automatically.

5.1.3. Simple Graph Display Function

You can easily display real time graphs with default values. The following graph types use default values to quickly display graphs without having to configure specific information. The graph types and their default values are listed below.

◆ Graph Display from Management Server Node 1. Right-click the management server name from the navigation tree window,




2. Select Display Graph and click Groups, Performance Indicators, or Statistics to display the corresponding graph. The following default values are used.

◆ Graph Display from Group Node <Server Group>

1. Right-click the server group name from the navigation tree window. A popup menu appears.

2. Select Display Graph and click Machines, Performance Indicators, or Statistics to display the corresponding graph. The following default values are used.

Menu Node Performance Indicator Statistics Threshold

Machines All machines belonging to the group

This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of groups.

Average None

Performance Indicators

Group All Performance Indicators applied on Collecting Data Setting List window

Average None

Statistics Group This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of groups.

All statistics except Summation

None

<Resource Pool Group>

1. In the navigation tree window, right-click Resource Pool Group to open a popup menu.

2. Select Display Graph and then click Resource Pools to display a graph. The following is the default value.


Resource Pools All resource pools belonging to

This performance indicator is the top of Performance Indicator List that is

Average None


Groups All groups This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of management servers.

Average None


Management server

All Performance Indicators applied on Collecting Data Setting List window

Average None

Statistics Management server

This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of management servers.


None


157

the group allocated to the Collecting Data Setting of resource pools.

<Disk Array>

1. In the navigation tree window, right-click the disk array name to open a popup menu.

2. Select Display Graph and then click Logical Disks, Performance Indicators, or Statistics to display each graph. The following are the default values.


Logical Disks All logical disks belonging to the disk array

This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of disk arrays.

Average None


Disk array All Performance Indicators applied on Collecting Data Setting List window

Average None

Statistics Disk array This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of disk arrays.


None

<SigmaSystemCenter Managed Objects>

1. In the navigation tree window, right-click SSC Managed Object Group to open a popup menu.

2. Select Display Graph and then click SigmaSystemCenter Managed Objects to display each graph. The following are the default values.


SigmaSystemCenter Managed Objects

All SigmaSystemCenter Managed Objects belonging to the SSC Managed Object Group

This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of SigmaSystemCenter Managed Objects.

Average None

◆ Graph Display from Managed Object Node <Machines> 1. Right-click the machine name from the navigation tree window.


2. Select Display Graph and click Performance Indicators or VMServer Load Condition to display the corresponding graph. The following default values are used.





Machine All Performance Indicators applied on Collecting Data Setting List window

Average None

VMServer Load Condition

Virtual machine server and virtual machines running on it

This performance indicator is the top of Performance Indicator List that is allocated to the Collecting Data Setting of Virtual machine server

Average Bound value of the VM Optimized Placement settings on SystemProvisioning

The VMServer Load Condition menu is available in the following conditions:

• The selected machine is applied from SystemProvisioning configuration information.

• The selected machine is a virtual machine server or a virtual machine.

<Resource Pools> 1. In the navigation tree window, right-click the resource pool name to open a

popup menu. 2. Select Display Graph and then click Performance Indicators to display a

graph. The following is the default value.



Resource Pool All Performance Indicators applied on Collecting Data Setting List window

Average None

<Logical Disks>

1. In the navigation tree window, right-click the LUN name to open a popup menu.

2. Select Display Graph and then click Performance Indicators to display a graph. The following is the default value.



Logical Disk All Performance Indicators applied on Collecting Data Setting List window

Average None


159

<SigmaSystemCenter Managed Objects>

1. In the navigation tree window, right-click the SigmaSystemCenter managed object name to open a popup menu.

2. Select Display Graph and then click Statistics Information to display each graph. The following are the default values.


Statistics Information

SigmaSystemCenter Managed Object

All Performance Indicators applied on Collecting Data Setting List window

Average None

5.1.4. Changing Performance Indicator Graphs

The Performance Indicator graph settings can be changed using the following procedure: 1. Select the Performance Indicator graph that you want to modify. When you click

the graph, the title bar will turn blue.

2. Right-click the plotting area of the graph and select Set Display or select Set Display from the Graph menu. The Graph Setting window appears.

3. The specification method for the Graph Setting window is the same as for "5.1.1 How to Display Performance Graphs".

4. When you have finished modifying, click OK. 5. Verify the performance graph has changed.



5.2. Saving Performance Status Display Specifications

When the management console closes, settings relating to performance status display are saved, and these settings are inherited next time the management console starts. The settings that are saved are as follows: Node comparison display versus Performance Indicator comparison display Real-time display versus specified period display (and the display period)

Statistics to be displayed on the graph and graph display color. Show/hide settings for each Performance Indicator item Vertical axis display settings

Plot interval settings Time axis display settings The display size and arrangement of the management console window

The settings relating performance status display are unique to each management server. If multiple management consoles are started on a single management server, the settings for the last management console to be closed is used the next time a management console is started.

If multiple management consoles are closed at the same time, the following error message may be displayed during the termination processing. The settings for management consoles for which this error message is displayed will not be saved. The process cannot access the file "******" because it is being used by another process.

Management Server

Management console

Management console

File for saving display settings

When the management

console closes, performance status display settings are

File Output

161

5.3. File Output Outputs performance graph data displayed. It can be used with Microsoft Excel, and so forth, as the output file formats are CSV and tab delineated text files.

5.3.1. File Output Methods

You must display performance data of output target beforehand on the performance graph window before outputting files. See "5.1.1 How to Display Performance Graphs" for displaying performance graphs.

Output files in the following steps.

1. Set the performance graph of output target to active then click Output File in the Graph menu or right-click in the plot area of the target performance graph, and then select Output File to display the Output Settings window.

2. Specify filename Filename is automatically set when the output settings window is displayed. To change the filename, direct key input to the filename field or click the Browse button to select the output destination on the output file window. When the filename is changed to the relative path, the file is output to the relative path from the desktop path of the current user.

Filenames automatically set consist of the following two parts. [Path] + [Filename]

◆ Path: The desktop path of the current user is set when the output settings window is displayed for the first time. The path specified last time is set from the second time onward.

◆ Filename: Set in a format shown below; sysmon[Start Time]_[Span].[File Extension]

[Start Time] is the graph start time, and [Span] is the specified value of the graph display time span. For [File Extension], "csv" or "txt" is set according to the file type.

3. Set file type.



When file type is changed, filename file extension, column separator and character encode format of the file to be output are changed. See "1.8.5 Output Graph Data to File" for file type, column separator and character encode format compatibility.

4. Set [Output the data in same line if time is same] checkbox. Set the checkbox to ON to enable specification, outputs to same line as same time data when there are differences in seconds units in multiple performance data time. The time to output to the file is formatted as shown below at this time.

◆ When less than 30 seconds, round down seconds. ◆ When more than 30 seconds, round up seconds. To output at exact time where performance data is collected, set the checkbox to OFF. Specification is enabled while the checkbox is ON at preset.

5. Click the OK button to output the file with the specified filename. When a file already exists, an overwrite confirmation window is displayed. When no problems exist when overwriting an existing file, click the OK button.

163

6. Threshold Monitoring and Notification This chapter explains how to monitor thresholds for performance data and make settings for the notification function. This chapter contains the following sections: • 6.1 Configuring Threshold Monitoring ...........................................................................164

6 Threshold Monitoring and Notification


6.1. Configuring Threshold Monitoring System Monitor - Performance Monitoring Services can detect and report load status events on monitored machines by monitoring specified Performance Indicator thresholds Performance fault events can also be notified to SystemProvisioning. Please note that this feature is only available for managed machines. If managed objects are resource pools, LUNs in NEC Storage, or SigmaSystemCenter Managed Objects, this feature is not available. Thresholds can be set up for active Performance Indicators for both groups and individual machines.

6.1.1. How to set up threshold monitoring

Information for threshold monitoring is based on the set Performance Indicators that are collected. The Performance Indicator settings must be set up beforehand.

Specify threshold monitoring settings using the following procedure: 1. Right-click the management server name in the navigation tree window, or the

group name or machine name to be monitored with the threshold.

The pop-up menu appears.

2. Click Set Threshold Monitor to display the Set Threshold Monitor dialog box.

Configuring Threshold Monitoring

165

Configure combinations of the Object node and Threshold method as threshold monitoring items in the Performance monitor list.

3. Specify which node to monitor. The nodes that can be specified as monitoring objects are displayed as a tree, depending on the monitoring unit. Select the node from the tree. You can select one of the following three monitoring units: Monitor machine, Monitor group or Monitor all machines in group. See "1.9 Threshold Monitoring and the Notification Function" for more information on monitoring units.

4. Specify the threshold method.

◆ To create a new threshold method, click New in the Threshold method section.

◆ To modify an existing threshold method, select the threshold method from the list box, and then click Modify.

◆ To delete an existing threshold method, select the threshold method from the list box, and then click Remove.

5. Click New or Modify, The Threshold Method Settings window appears.



Specify the following items in the Threshold Method Settings window:

◆ Threshold method name Enter the name of the threshold method in the Threshold method name text box. A threshold method name can be generated automatically by clicking Generate Method Name. (Required)

◆ Performance Indicator and statistic Select the Performance Indicator item and the statistics for the threshold to be defined from the Performance Indicator and Statistics combo boxes. Statistics are only valid if the monitored object is a group. (Required)

◆ Threshold and notification settings Switch to the Upper Threshold, Lower Threshold and Notification Settings tabs and make further settings.

Note: The title of the threshold method obtained from SystemProvisioning and then registered begins with [VMServer] or [SystemProvisioning]. To make the names of the threshold method unique, prevent the titles of manually registered threshold method from beginning with [VMServer] or [SystemProvisioning].


167

6. When the Upper Threshold tab is selected, settings for upper-limit threshold values are displayed.

The following settings can be configured:

◆ To specify upper-limit critical value monitoring, check the Enable upper-limit critical value monitor box. When this box is checked, upper-limit critical value monitoring specifications can be made.

• Threshold: Specify the threshold for upper-limit abnormalities. Specify a value between 0 and 3.402823e+38.

• Notification to SystemProvisioning: Check this box to notify SystemProvisioning when the upper-limit warning value has been exceeded. When notifying SystemProvisioning, select notification types from the Over and At recovery boxes.

◆ To specify upper-limit warning value monitoring, check the Enable upper-limit warning value monitor box. When this box is checked, upper-limit warning value monitoring specifications can be made.

• Threshold: Specify the threshold for upper-limit warnings. Specify a value between 0 and 3.402823e+38.

• Notification to SystemProvisioning:



Check this box to notify SystemProvisioning when the upper-limit warning value has been exceeded. When notifying SystemProvisioning, select notification types from the Over and At recovery boxes.

7. When the Lower Threshold tab is selected, settings items for lower limit threshold values are displayed.

Specify the following items here:

◆ To specify lower-limit critical value monitoring, check the Enable lower-limit critical value monitor box. When this box is checked, lower-limit critical value monitoring specifications can be made.

• Threshold: Specify the threshold for lower-limit abnormalities. Specify a value between 0 and 3.402823e+38.

• Notification to SystemProvisioning: Check this box to notify SystemProvisioning when the lower-limit critical value has been exceeded. When notifying SystemProvisioning, select the notification types from the Over and At recovery boxes.

◆ To specify lower-limit warning value monitoring, check the Enable lower-limit warning value monitor box. When this box is checked, lower-limit warning value monitoring specifications can be made.

• Threshold:


169

Specify the threshold for lower-limit warnings. Specify a value between 0 and 3.402823e+38.

• Notification to SystemProvisioning: Check this box to notify SystemProvisioning when the lower-limit warning value has been exceeded. When notifying SystemProvisioning, select the notification types from the Over and At recovery boxes.

8. When the Notification Settings tab is selected, settings items relating to notification are displayed.

Specify the following items here:

◆ Notification conditions Set up notification conditions in terms of the number of times that over-threshold is detected during a sequence of performance data checks. The performance data check interval is the performance data collecting interval that was specified in the collecting data setting. By default, a notification is made if over-threshold is detected ten times out of ten checks. The number of checks and the number of over-threshold times can be set between one and 1000.

◆ If you want to send another notification if the performance status does not recover from over-threshold status, then check the in case of no recovery from the over-threshold status box. If this box is checked, then repeat notifications are enabled. Specify the timing for repeat notifications in terms of the number of checks since the previous notification. The number of checks can be specified between one and 1000.



9. After you make specifications for the threshold method settings, click OK, and then verify that the settings have been applied in the Threshold method list box in the Set Threshold Monitor window.

10. Select the item you want to configure as a threshold monitoring setting from the Object node or the Threshold method, and then click Add to add the threshold monitoring item to the Performance monitor list. Multiple threshold monitoring settings can be configured.

Note: The performance indicator of the performance monitor setting to be added must be set to collect from the target node.

11. To delete an existing threshold monitoring setting, select from the Performance

monitor list, and then click Remove to the right of the list.

6.1.2. How to display over-threshold areas on graphs

The configure threshold method information can be displayed in the background of graphs as over-threshold areas. In the Threshold Display tab of the Graph Setting window, check the Display thresholds area box and then select the threshold method information to be displayed. The background color for over-threshold areas is configured in the Color and Line tab of the Graph Setting window using the Background of threshold area option.

6.1.3. Threshold setting automatically applied by

SystemProvisioning linkage

◆ Threshold setting automatically applied by VM Optimized Placement When the configuration information for the group for which the above VM Optimization is enabled is reflected on System Monitor - Performance Monitoring Services of SystemProvisioning, threshold settings that are tailored to the VM Optimization settings and which are specified in SystemProvisioning are automatically created and applied to all the machines in the group. The automatically applied threshold setting can be checked in the Set Threshold Monitor dialog box.


171

The automatically applied threshold settings by VM Optimized Placement are listed in blue in the Set Threshold Monitor dialog box. In this dialog box, it is impossible to delete an automatically applied threshold setting or to manually add a monitoring setting using the automatically added threshold setting, but it is possible to change the notification setting for the threshold method.



◆ Threshold setting automatically applied by Performance Monitor settings When the configuration information for the group/model for which the Performance Monitor is enabled in SystemProvisioning is reflected on System Monitor - Performance Monitoring Services, threshold settings that are tailored to the monitoring profile settings and which are specified in SystemProvisioning are automatically created and applied to all the machines in the group. The automatically applied threshold setting can be checked in the Set Threshold Monitor dialog box.


173

The automatically applied threshold settings by Performance Monitor settings are listed in blue in the Set Threshold Monitor dialog box. In this dialog box, it is impossible to delete an automatically applied threshold setting or to manually add a monitoring setting using the automatically added threshold setting. And, in System Monitor - Performance Monitoring Services, it is not allowed to change the threshold value and the notification setting for the threshold method.

175

7. Management of Performance Data This chapter explains how to manage performance data. This chapter contains the following sections: • 7.1 Data Management Tool ...........................................................................................176 • 7.2 Database Size Monitoring ........................................................................................179

7 Management of Performance Data


7.1. Data Management Tool This section describes how to change the data storage period and perform data summarization.

1. On the Start menu, point to SigmaSystemCenter - Tools and then click System Monitor Data Management Tool to start the System Monitor Data Management Tool.

2. To change the storage period for the summary data, select the summary interval to be changed in the list and then click Modify to display the Summary Setting dialog box. Change the storage period, and then click OK.

Data Management Tool

177

Note: Make these settings so that the storage periods for the summary data items satisfy the following conditions.

Storage period for 5 minutes ≤ Storage period for 15 minutes ≤ Storage period for 1 hour ≤ Storage period for 1 day

3. To change the storage period for the collected data, change the collected data storage period setting for the System Monitor Data Management Tool.

4. Click Run to change the data storage period and then perform data summarization.



Notes: ▪ Before executing data summarization, stop System Monitor - Performance Monitoring Services. ▪ Recompilation may take some time depending on the amount of data to be recompiled. Keep this in mind with scheduling recompilation. ▪ If the warning value for the database size is exceeded during recompilation, recompilation is stopped. At this time, reduce the data storage period and then perform recompilation again.

5. In the confirmation dialog box that appears upon the completion of processing, click OK to close the System Monitor Data Management Tool.

Database Size Monitoring

179

7.2. Database Size Monitoring 7.2.1. Database size warning setting

The database size monitoring function checks the database size every hour while the Performance Monitoring Service is active. If the database size exceeds the specified value, a warning is issued. The default database size at which a warning is issued is 9.0 GB. This alarm value can be changed. Change the alarm value as described below. 1. Start up the System Monitor Management Console.

2. Right-click the management server name in the navigation tree window of the management console main window to display the pop-up menu.

3. Click Set Configuration.

4. Click the Database Size tab.

5. Change the warning value.

6. Click OK to close the Configuration dialog box.

Note: PostgreSQL does not have a database size limitation in its specification. If you use PostgreSQL for a database, specify an appropriate value to the warning value to suit the available capacity of your disk or partition.



7.2.2. Database size warning

If the database size exceeds the specified warning value, the following message appears in the log window of the connected management console, and is also recorded in the event log.

◆ Type Warning

◆ Event ID 67

◆ Message: The database size has exceeded warning value WarningSizeGB. The current size is CurrentSizeGB.

Notes: ▪ The database monitoring function monitors the size of the database area used by System Monitor - Performance Monitoring Services. The size of other database areas in the same database instance is not included in the target database size. ▪ Depending on SQL Server settings, the database size might not show the real size immediately after data have been deleted from it. In this case, manually compress the database file as needed.

181

8. Command-Line Interface This chapter explains how to use command-line interface. This chapter contains the following sections: • 8.1 ssc-perf Command ..................................................................................................182

8 Command-Line Interface


8.1. ssc-perf Command The ssc-perf command can execute the following things.

◆ The ssc-perf command can display the performance data collected by System Monitor - Performance Monitoring Services on the command prompt. This makes it possible to track the performance trends without starting the management console. When the System Monitor - Performance Monitoring Services is installed, the ssc-perf command module is installed in the directory shown below: <Installation Directory>\bin

(Default value：%ProgramFiles%\NEC\SystemMonitorPerformance\bin)

◆ The ssc-perf command can display, add and delete the setting of the custom performance indicators. It is useful to register the multiple custom performance indicators at the same time.

The ssc-perf command must be executed in the OS on the management server by the authorized user.

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 ssc-perf commands.

8.1.1. The Basic Syntax

This section explains the basic syntax of the ssc-perf command. Help is displayed if parameters are omitted. <Syntax>

<Parameters> The following values can be specified for the option:

Option Description

-h Display help.

-v Display version information.

ssc-perf option | command subcommand [parameter] …

ssc-perf Command

183

8.1.2. show performancedata Command

With this command, the specified performance data from those registered to System Monitor - Performance Monitoring Services is output to standard output in the CSV file format. If the data needs to be output to a file, redirect standard output to the file by specifying the file name.

To output the performance data, you must specify the following items:

◆ Output period ◆ Output interval

◆ Node ◆ Performance indicator ◆ Statistical method With these items specified, the performance data of the specified node, performance indicator and statistical method at a specified output interval for a specified output period is output per line in the CSV file format. You can specify so that the multiple performance data of Node/Performance indicator/Statistical method will be output per column in one line. However, you can specify only one of the Node/Performance indicator/Statistical methods.

If no data correspond to those you specified in the above, the performance data will not be output. If the data partially include hours that the performance data are not obtained, the line with the data will be output but the line without the data will not.

<Syntax>

<Parameters>

Parameter Required

/Optional

Description

-node Node *2

Required *1

Specify the path of the node on System Monitor - Performance Monitoring Services whose performance data you want to show. It is impossible to specify -path at the same time. Sample: -node "GroupName\MachineName" You can use either "\" or "/" to a path separator character. In a case of -node, you specify the path to the group without specifying the machine name, the statistic information of the group is shown. It is also impossible to specify multiple sets of -node and -indicator.

ssc-perf show performancedata {-node Node | -path Path [–resource Resource]} -indicator Indicator -statistic Statistic [-start StartTime] [-end EndTime] [-period Period] [-interval Interval] [-server Server] [-port PortNumber] [-user User] [-password Password] [-tab | -t] [-column Column] [-noblank]



Parameter Required

/Optional

Description

-path Path

*3

Required *1

Specify the path of the node Operation view on SigmaSystemCenter, whose performance data you want to display. It is impossible to specify -node at the same time. Sample: -path "CategoryName\GroupName\ModelName\HostName" You can use either "\" or "/" to a path separator character. If you do not use a model, omit the model name. In case of the -path, you specify root (“\” or “/”), tenant, category, group or model without specifying the host name, all machines under the specified path are specified. In case of the -path, whether specify single host or multiple ones you can also specify multiple values for -indicator.

-resource Resource

Optional Specify the resource type of objects whose performance data you want to show. This is only valid when "-path" is specified. You can specify the following parameters:

Parameter Description

machine To show machine performance data

group To show machine group statistic data

lun To show LUN performance data

resourcepool To show resource pool performance data

sscmanagedobje

ct

To show the statistic information of

SigmaSystemCenter managed objects

You can use any combination from the above. When you specify multiple parameters, use a space as a separator. Example: -resource machine group lun resourcepool If you omit the "-resource" parameter, the performance data of machines, machine groups, LUNs, resource pools is displayed. To display the statistic information of SigmaSystemCenter managed objects, the "-resource sscmanagedobject" parameter is required.

-indicator Indicator

*2 *3

Required Specify the title of the performance indicator whose performance data you want to show.

-statistic Required Specify the title of statistical method whose performance data you want to show.

ssc-perf Command

185

Parameter Required

/Optional

Description

Statistic

*2 *3

The following values can be specified:

Value Description

Ave Displays the average value.

Max Displays the maximum value.

Min Displays the minimum value.

WeightAve Displays the weighted average value.

UpperRange Displays the average + standard deviation value.

LowerRange Displays the average - standard deviation value.

Sum Displays the summation value.

[-start StartTime]

Optional Specify the start date and time of output period for the performance data. If you omit StartTime, the start date and time is determined based on the EndTime value and the Period value as follows: ▪ If omitted only StartTime, the start date and time is determined by the following formula: EndTime-Period ▪ If omitted both StartTime and EndTime, the start date and time is determined by subtracting Period from the time to execute the command (see the description of EndTime). For example, if the time to execute the command is "01:02", you specify "00:05" for Interval, and "01:00" for Period, StartTime becomes "00:00." This format depends on the date and time formats in the regional and language options of Control Panel of the Windows operating system on the management server. Specify the date and time in the same format as that in your operating system.



Parameter Required

/Optional

Description

[-end EndTime]

Optional Specify the end date and time of output period for the performance data. If you omit EndTime, the end date and time is determined as follows: ▪ If omitted only EndTime, the start date and time is determined by the following formula: StartTime+Period ▪ If omitted both StartTime and EndTime, the end date and time is the time rounded to the nearest Interval before the time the command was executed as the following example shows. For example, if the time to execute command is "01:02", you specify "00:05" for Interval, and "01:00" for Period, EndTime becomes "01:00."

[-period Period]

Optional Specify the period from the start date and time to the end date and time to show the performance data. In the figure above, specify from 00:00 to 01:00 as Period. ▪ If you specified both StartTime and EndTime, the Period value you specified is ignored and the actual period is determined by the following formula: EndTime-StartTime If omitted, the default is 01:00. Format: d | [d.]hh:mm[:ss] d: The number of days. If you specify the value for "d", the result of the formula d * 24 is added to the number of hours. hh: The number of hours mm: The number of minute ss: The number of seconds

[-interval Interval]

Optional Specify the interval of the data that are shown per line. In the figure above, the data are shown every five minutes. So specify the interval as five minutes. This determines the performance data type on the database that is used when outputting the data. The performance data on the database include four types of summary data and each type has different data interval. The data with the largest interval in intervals smaller than the Interval value you specified will be used. For details of the summary data, see 1.4.2 "Usage of Summary Data." If omitted, the default is 00:01.

Interval

Period

00:00 00:05 00:10 00:50 00:55 01:00

Execute time is "01:02"

ssc-perf Command

187

Parameter Required

/Optional

Description

Format: d | [d.]hh:mm[:ss] For more information about the format to specify this option, see the description about -period. E.g.) The performance data that will be used according to the -interval value you specified: If you specify "00:04:59" for –interval, the collected data will be used. If you specify "00:05" for –interval, the 5-minute summary data will be used. If you specify "00:15" for –interval, the 15-minute summary data will be used. If you specify "01:00" for –interval, the 1-hour summary data will be used. If you specify "1" for –interval, the 1-hour summary data will be used. If you specify "2" for –interval, the 1-day summary data will be used.

[-server Server]

Optional Specify an IP address or a host name of the management server whose performance data will be showing. When omit this option, the command will get the performance data of the local management server.

[-port PortNumber]

Optional Specify the port number of the service to connect. If omitted, the default is 26200.

[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want get the performance data from the local management server, you can omit it.

[-password Password]

Optional Specify the password of the specified logon user. The option can be omitted when you omit -user.

[-tab | -t] Optional Use a tab as a delimiter in displaying performance data. If omitted, use a comma as a delimiter.

[-column Column]

Optional Specify the kinds of columns of the table which you want to show the performance data. The option is valid only when both -path and –indicator specifies multiple ones. Values which are able to be entered are as follows.

Value Description

indicator In each node, output the performance data to one table. In

the table of the performance data, output each

performance data to the line.

node In each performance indicator, output the performance

data to one table. In the table of the performance data,

output each performance data to the line.

When omitting the specification, output each node’s performance data of the performance indicator to a table.

[-noblank] Optional Specify whether with or without spaces, for easy-to-read the show data, between the columns. The default is the data with spaces.



Parameter Required

/Optional

Description

If you want the data without spaces, specify this option.

*1 Either -node or -path is required. These two parameters cannot be specified at the same time.

*2 When you specify you -node、-indicator and –statistic at the same time, can specify multiple values for only one of the three required parameters (-node (or -path), -indicator and -statistic).

*3 When you specify -path、-indicator and –statistic at the same time, can specify multiple ones in each of –path and –indicator at the same time. However, in this case, the specification of -statistic must be one. When you specify multiple –statistic, the specification of –path and –indicator must be one respectively. In addition, even if the -path specify only one, in the case that there are multiple machines for it, this case is treated as the multiple specifications.

<Sample Output 1: -node>

C:\Users\Administrator>ssc-perf show performancedata -node Group1\machine1 Group1\machine2 -indicator "CPU Usage (%)" -statistic Ave -period 00:10

Period 2010/01/01 00:00:00-2010/01/01 00:10:00 00:10:00 Indicator:CPU Usage (%) StatisticalMethod:Average

DateTime , Group1\machine1, Group1\machine2

2010/01/01 00:00:30, 3.459734 , 3.534981

2010/01/01 00:01:30, 7.41076 , 1.907642

2010/01/01 00:02:30, 12.47074 , 0.7593492

2010/01/01 00:03:30, 23.86721 , 3.245667

2010/01/01 00:04:30, 27.60608 , 1.271073

2010/01/01 00:05:30, 27.60608 , 0.8400003

2010/01/01 00:06:30, 24.14691 , 7.729072

2010/01/01 00:07:30, 23.14114 , 10.35331

2010/01/01 00:08:30, 9.133735 , 8.398178

2010/01/01 00:09:30, 4.893562 , 1.193273

C:\Users\Administrator>

ssc-perf Command

189

<Sample Output 2: -path>

C:\Users\Administrator>ssc-perf show performancedata -path Group1\machine1 Group1\machine2 -indicator "CPU Usage (%)" -statistic Ave -period 00:10

Period2016/10/09 16:42:00-2016/10/09 16:52:00 00:10:00 Indicator:CPU Usage (%) StatisticalMethod:Average

DateTime , Group1\machine1 , Group1\machine2

2016/10/09 16:42:30, 38.44333 , 5.37

2016/10/09 16:43:30, 35.33 , 5.96

2016/10/09 16:44:30, 26.67 , 6.18

2016/10/09 16:45:30, 30.59 , 8.52

2016/10/09 16:46:30, 25.98667 , 5.743333

2016/10/09 16:47:30, 38.08667 , 6.703333

2016/10/09 16:48:30, 34.34667 , 8.556667

2016/10/09 16:49:30, 35.33 , 9.83

2016/10/09 16:50:30, 40.63667 , 7.076667

2016/10/09 16:51:30, 27.80667 , 7.746667




<Sample Output 3: -path and –indicator that both have multiple parameters>

C:\Users\Administrator>ssc-perf show performancedata -path Group1\machine1 Group1\machine2 -indicator "CPU Usage (%)" ”Disk Space (MB)” -statistic Ave -period 00:10

Period2016/10/09 16:39:00-2016/10/09 16:49:00 00:10:00 StatisticalMethod:Average

DateTime , Group1\machine1\CPU Usage (%), Group1\machine2\CPU Usage (%), Group1\machine1\Disk Space (MB), Group1\machine2\Disk Space (MB)

2016/10/09 16:39:30, 37.23 , 6.566667 , 503713 , 326187

2016/10/09 16:40:30, 47.32 , 6.333333 , 503713 , 326187

2016/10/09 16:41:30, 38.33333 , 6.03 , 503713 , 326187

2016/10/09 16:42:30, 38.44333 , 5.37 , 503713 , 326187

2016/10/09 16:43:30, 35.33 , 5.96 , 503713 , 326187

2016/10/09 16:44:30, 26.67 , 6.18 , 503526 , 326187

2016/10/09 16:45:30, 30.59 , 8.52 , 503526 , 326187

2016/10/09 16:46:30, 25.98667 , 5.743333 , 503526 , 326187

2016/10/09 16:47:30, 38.08667 , 6.703333 , 503526 , 326187

2016/10/09 16:48:30, 34.34667 , 8.556667 , 503526 , 326187


ssc-perf Command

191

<Sample Output 4: -path including a path to a group>

<Sample Output 5: Displaying the statistic information of SigmaSystemCenter managed objects by specifying an SSC path by using -path >

C:\Users\Administrator>ssc-perf show performancedata -path Group1 -indicator "CPU Usage (%)" ”Disk Space (MB)” -statistic Ave -period 00:10

Period2016/10/09 16:44:00-2016/10/09 16:55:00 00:11:00 Indicator:CPU Usage (%) StatisticalMethod:Average

DateTime , Group:Group1 , Group1\machine1 , Group1\machine2

2016/10/09 16:44:30, 13.01 , 26.67 , 6.18

2016/10/09 16:45:30, 19.555 , 30.59 , 8.52

2016/10/09 16:46:30, 15.865 , 25.98667 , 5.743333

2016/10/09 16:47:30, 22.395 , 38.08667 , 6.703333

2016/10/09 16:48:30, 21.45167 , 34.34667 , 8.556667

2016/10/09 16:49:30, 22.58 , 35.33 , 9.83

2016/10/09 16:50:30, 23.85667 , 40.63667 , 7.076667

2016/10/09 16:51:30, 17.77667 , 27.80667 , 7.746667

2016/10/09 16:52:30, 19.76167 , 28.96 , 10.56333

2016/10/09 16:53:30, 19.48833 , 30.95 , 8.026667

2016/10/09 16:54:30, 18.45333 , 29.69667 , 7.21


C:\Users\Administrator>ssc-perf show performancedata -path Group1 -resource sscmanagedobject -indicator “Machine.Count” -statistic Ave -period 06:00

Period2017/03/02 4:00:00-2017/03/02 16:00:00 12:00:00 Node: SSCManagedObject:Tanent\Group StatisticalMethod:Average

DateTime , Machine.Count

2017/03/02 11:30:00, 2

2017/03/02 12:30:00, 2

2017/03/02 13:30:00, 2

2017/03/02 14:30:00, 2

2017/03/02 15:30:00, 2

2017/03/02 16:30:00, 2



8.1.3. show performanceindicator command

Display the definition of the custom performance indicators registered in System Monitor - Performance Monitoring Services.

<Syntax>

<Parameter>

Parameter Required

/Optional

Description

[-indicator Title]

Optional Specify the title of Custom Performance Indicators. It is possible to specify multiple values by punctuating with space. In a case of omitting the specification, all the defined custom performance indicators registered in SystemMonitor management server are displayed.

[-server Server]

Optional Specify an IP address or a host name of the management server whose custom performance indicator will be showing. When omit this option, the command will show custom performance indicator of local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want show custom performance indicator of local management server, you can omit it.



ssc-perf show performanceindicator [-indicator Title] [-server Server] [-port PortNumber] [-user User] [-password Password]

ssc-perf Command

193

<Sample Output>

C:\Documents and Settings\Administrator>ssc-perf show performanceindicator

Title :LUN IOPS

Executing String :local://GetiStorageLDPerforData.bat $:SYSMON_COLLECTION_INTERVAL $:SYSMON_START_TIME

Description :

Type :Script

Title :LogicalDisk(C:)\Free Megabytes

Performance Object :LogicalDisk

Counter :Free Megabytes

Instance :C:

Description : Display the nonallocated region of disk drive with MB unit. 1 MB is 1,048,576 Bytes.

Type :Windows



8.1.4. Add Performance Indicator Command

Add the definition of custom performance indicators to the System Monitor - Performance Monitoring Services.

Title :cpu(0)\utilization (average)

Metricgroup :cpu

Counter :utilization (average)

Object :0

Description :CPU utilization as a percentage during the interval (CPU usage and CPU utilization might be different due to power management technologies or hyper-threading)

Type :VMware Esx Host

C:\Users\Administrator>ssc-perf show performanceindicator -indicator "LUN IOPS"

Title :LUN IOPS


Description :

Type :Script

C:\Users\Administrator>ssc-perf show performanceindicator -indicator "LUN IOPS" "LogicalDisk(C:)\Free Megabytes"

Title :LUN IOPS


Description :

Type :Script

Title :LogicalDisk(C:)\Free Megabytes

Performance Object :LogicalDisk

Counter :Free Megabytes

Instance :C:

Description : Display the nonallocated region of disk drive with MB unit. 1 MB is 1,048,576 Bytes.

Type :Windows

ssc-perf Command

195

<Syntax>

<Parameter>

Parameter Required

/Optional

Description

-indicator Required This parameter must be specified in the beginning of the definition of custom performance indicators. The definition of specification can specify multiple values by using comma (,) as a separator.

type=Type Required Specify the kinds of custom performance indicators. The enterable values are as follows.

Value Description

Windows Define the custom performance indicators for acquiring

the performance data of windows.

ESXHost Define the custom performance indicators for acquiring

the performance data of VMware ESXi virtual machine

server.

ESXGuest Define the custom performance indicators for acquiring

the performance data of VMware ESXi virtual machine.

Script Define the custom performance indicators for acquiring

the performance data by execution of the script.

[title=Title]

Windows,ESXHost,ESXGuest: Optional Script: Required

Specify the title of custom performance indicators. In case of omitting the specification, it is automatically named in the style of Category (Instance)\Counter. In case of Script, the specification is always required.

category=Category

Windows,ESXHost,ESXGuest: Required Script: disabled

Specify the performance object (Windows) or Metric Group (VMware ESXi). In case of the ESXHost, ESXGuest, specify the key of Metric Group.

counter=Counter

Windows,ESXHost,ESXGuest: Required Script:

Specify the counter. In case of ESXHost, ESXGuest, specify in the counter (roll-up).

ssc-perf add performanceindicator -indicator {type=Windows|ESXHost|ESXGuest [title=Title] category=Category counter=Counter [instance=Instance] [description=Description] | type=Script title=Title execString=ExecString [description=Description]} [-server Server] [-port PortNumber] [-user User] [-password Password]



Parameter Required

/Optional

Description

Disabled

[instance=Instance]

Windows,ESXHost,ESXGuest: Optional Script: Disabled

When specifying the instance (Windows) or the object (VMware ESX / ESXi). The performance indicators which do not require the instance, such as Windows memory, the performance indicators of an ESX Host unit or a virtual machine unit, the specification of this option can be omitted. In case of omitting it, null character strings are specified.

execString Windows,ESXHost,ESXGuest: Disabled Script: Required

Specify the executing strings of the script.

[description=Description]

Optional Specify the description of performance indicators. When not specifying the description, omit the specification of this option.

[-server Server]

Optional Specify an IP address or a host name of the management server that you add custom performance indicator to. When omit this option, the command will add custom performance indicator to the local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want add custom performance indicator to local management server, you can omit it.



Note: Comma cannot be used in the specified character strings of the each option of the command.

Reference: When adding the custom performance indicators to ESXHost, ESXGuest, see Appendix D "Performance Counter Information of VMware ESXi" for the details of the Metric Group and Counter information.

ssc-perf Command

197

<Execution Example>

8.1.5. Delete performance indicator command

Delete the custom performance indicators defined in the System Monitor - Performance Monitoring Services.

<Syntax>

<Parameter>

Parameter Required

/Optional

Description

-indicator Title

Required Specify the title of custom performance indicators. It can specify multiple values by using space as a separator.

[-server Server]

Optional Specify an IP address or a host name of the management server whose custom performance indicator will be deleting. When omit this option, the command will delete custom performance indicator from the local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want delete custom performance indicator from local management server, you can omit it.



C:\Documents and Settings\Administrator>ssc-perf add performanceindicator -indicator type="Windows" category="LogicalDisk" counter="Free Megabytes" instance="C:" description="Display the nonallocated region of diskdrive C with MB unit."

C:\Documents and Settings\Administrator>ssc-perf add performanceindicator -indicator type="Windows" category="LogicalDisk" counter="Free Megabytes" instance="C:" description="Display the nonallocated region of diskdrive C with MB unit.", type=" ESXHost" category="cpu" counter="utilization (average)" instance="0"

ssc-perf delete performanceindicator –indicator Title [-server Server] [-port PortNumber] [-user User] [-password Password]



<Execution Example>

8.1.6. show storageperiod command

This command displays the storage periods of collected data or summary data.

<Syntax>

<Parameter>

Parameter Required

/Optional

Description

[-server Server]

Optional Specify an IP address or a host name of the management server whose storage period settings will be showing. When omit this option, the command will show the storage period settings of the local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want show the storage period settings of the local management server, you can omit it.



<Output>

Description

Interval Displays the interval of collecting data and summary data.

Storage period Displays the storage periods.

C:\Documents and Settings\Administrator>ssc-perf delete performanceindicator -indicator "LogicalDisk(C:)\Free Megabytes"

C:\Documents and Settings\Administrator>ssc-perf delete performanceindicator -indicator "cpu(0)\utilization (average)" "LUN IOPS"

ssc-perf show storageperiod [-server Server] [-port PortNumber] [-user User] [-password Password]

ssc-perf Command

199

<Sample Output>

8.1.7. set storageperiod command

This command changes the storage periods of collected data or summary data. <Syntax>

<Parameter>

Parameter Required

/Optional

Description

– item interval= Interval period=Period,…

Required Specify a storage period per interval. You can specify multiple values by using ", (comma)" as a divider. interval: Specify intervals (required). Available values:

Value Description

00:01 1 minute collecting interval

00:05 5 minutes summarizing interval

00:15 15 minutes summarizing interval

01:00 1 hour summarizing interval

1 1 day summarizing interval

E.g., interval=00:01 period: Specify a storage period (required).

C:\Documents and Settings\Administrator>ssc-perf show storageperiod

Interval, Storage period

1 minute, 3 days

5 minutes, 1 week

15 minutes, 2 months

1 hour, 3 months 1 day, 5 years

ssc-perf set storageperiod –item interval= Interval period=Period,… [-server Server] [-port PortNumber] [-user User] [-password Password]



Parameter Required

/Optional

Description

Specify this in the format of a number and a unit. For days: specify an integer from 1 to 30000 Except days: specify an integer from 1 to 100 Available values: xdays xweeks xmonths xyears E.g., period=365days

[-server Server]

Optional Specify an IP address or a host name of the management server whose storage period settings will be changing. When omit this option, the command will change the storage period settings of local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want change the storage period settings of the local management server, you can omit it.



<Execution Example>

8.1.8. show databasesetting command

This command displays database settings. <Syntax>

C:\Documents and Settings\Administrator> ssc-perf set storageperiod -item interval=00:01 period=1weeks, interval=01:00 period=7months

The storage period is updated.

You need to restart performance monitoring service to take it effect.

ssc-perf show databasesetting [-server Server] [-port PortNumber] [-user User] [-password Password]

ssc-perf Command

201

<Parameter>

Parameter Required

/Optional

Description

[-server Server]

Optional Specify an IP address or a host name of the management server whose database settings will be showing. When omit this option, the command will show the database settings of local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want show the database settings of local management server, you can omit it.



<Output>

Description

Database Displays the type of the database that is in use.

Host Displays the IP address or host name of the database.

Instance Displays the instance name of SQL Server.

Server authentication

Displays the authentication mode of SQL Server. Windows: Windows authentication SQL: SQL authentication

Account Displays the user account of the database.

Port Displays the port number of PostgreSQL.

<Sample Output 1: For SQL Server with Windows authentication>

C:\Users\Administrator>ssc-perf show databasesetting

Database :SQL Server

Host :(local)

Instance :SSCCMDB Server authentication :Windows



<Sample Output 2: For SQL Server with SQL authentication>

<Sample Output 3: For PostgreSQL>

8.1.9. set databasesetting command

This command changes database settings.

<Syntax>

<Parameter>

Parameter Required

/Optional

Description

-dbtype

{"SQL Server" | "PostgreSQL"}

Required Specify the type of a database. Available values:

Value Description

SQL Server To use SQL Server

PostgreSQL To use PostgreSQL

[-host Optional Specify the host name of the database.


Database :SQL Server

Host :192.168.128.1

Instance :SSCCMDB

Server authentication :SQL

Account :sa


Database :PostgreSQL

Host : 192.168.128.1

Port :5432 Account :postgres

ssc-perf set databasesetting {-dbtype "SQL Server" [-host Host] [-instance Instance] {[-authentication Windows] | [-authentication SQL] [-dbaccount dbAccout] [-dbpassword dbPassword]} | -dbtype "PostgerSQL" [-host Host] [-postgresport Port] [-dbaccount dbAccount] [-dbpassword dbPassword]} [-server Server] [-port Port] [-user User] [-password Password]

ssc-perf Command

203

Parameter Required

/Optional

Description

Host] If you omit this parameter, it remains unchanged.

[-instance Instance]

Optional Specify the instance name of the database. This parameter is available only when SQL Server is specified If you omit this parameter, it remains unchanged.

[-authentication {Windows|SQL}]

Optional Specify the authentication mode of the database. This parameter is available only when SQL Server is specified Available values:

Value Description

Windows To use Windows authentication

SQL To use SQL authentication

If you omit this parameter, it remains unchanged.

[-postgresport Port]

Optional Specify the port number of PostgreSQL. This parameter is available only when PostgreSQL is specified. Specify an integer from 1 to 65535. If you omit this parameter, it remains unchanged.

[-dbaccount dbAccount]

Optional Specify a user account to log on the database. This parameter is available only when PostgreSQL or SQL Server with SQL authentication is specified. If you omit this parameter, it remains unchanged.

[-dbpassword dbPassword]

Optional Specify a password corresponding to the above user account. This parameter is available only when PostgreSQL or SQL Server with SQL authentication is specified. If you omit this parameter, it remains unchanged.

[-server Server]

Optional Specify an IP address or a host name of the management server whose database settings will be changing. When omit this option, the command will changed the database settings of local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want changed the database settings of local management server, you can omit it.





<Execution Example 1: For SQL Server with Windows authentication>

<Execution Example 2: For SQL Server with SQL authentication>

<Execution Example 3: For PostgreSQL>

8.1.10. apply SystemProvisioningConfiguration command

This command applies system configuration information.

<Syntax>

C:\Users\Administrator>ssc-perf set databasesetting -dbtype "SQL Server" -host 192.168.128.1 -instance SSCCMDB -authentication Windows

The database setting is updated.


C:\Users\Administrator>ssc-perf set databasesetting -dbtype "SQL Server" -host 192.168.128.1 -instance SSCCMDB -authentication SQL -dbaccount sa -dbpassword P@ssw0d



C:\Users\Administrator>ssc-perf set databasesetting -dbtype "PostgreSQL" -host 192.168.128.1 -postgresport 5432 -dbaccount postgres -dbpassword P@ssw0d



ssc-perf apply SystemProvisioningConfiguration [-server Server] [-port PortNumber] [-user User] [-password Password]

ssc-perf Command

205

<Parameter>

Parameter Required

/Optional

Description

[-server Server]

Optional Specify an IP address or a host name of the management server that Applying SystemProvisioning Configuration operation will be executed. When omit this option, the command will execute the Applying SystemProvisioning Configuration operation on the local management server.

[-port PortNumber]


[-user User]

Optional Specify a logon user with OS administrator privileges of the management server. If you want execute the Applying SystemProvisioning Configuration operation on the local management server, you can omit it.



<Execution Example>

C:\Documents and Settings\Administrator> ssc-perf apply SystemProvisioningConfiguration Applied the SystemProvisioning Configuration.

207

9. Troubleshooting This chapter explains errors and how to handle them. This chapter contains the following sections: • 9.1 The Event Log .........................................................................................................208 • 9.2 What to do if the Performance Monitoring Service does not Start ..........................216 • 9.3 What to do if the Connection from Management Console to Server Fails ..............223 • 9.4 What to do if Performance Data Collecting Fails .....................................................225 • 9.5 What to do if Performance Data Collecting is delayed ............................................234 • 9.6 What to do if there are SystemProvisioning Configuration Applying Errors ............235 • 9.7 What to do if there are Errors when Performance Abnormalities are reported to

SystemProvisioning ...................................................................................................................237 • 9.8 What to do if the SystemMonitor data management tool might not start ................239 • 9.9 Database..................................................................................................................242 • 9.10 Other ........................................................................................................................254

9 Troubleshooting


9.1. The Event Log System Monitor - Performance Monitoring Services records errors and operation event information in the event log on the management server under the event log name "System Monitor - Performance Monitoring Services".

9.1.1. Event Logs for Performance Monitoring Service

source name： SystemMonitorPerformanceService

ID Type category Description

1 Information Service Started Performance Monitoring Service.

2 Information Service Stopped Performance Monitoring Service.

3 Information Service Paused Performance Monitoring Service.

4 Information Service Restarted Performance Monitoring Service.

5 Error Service Error when starting Performance Monitoring Service.

6 Error Service Error when stopping Performance Monitoring Service.

7 Error Service Error when pausing Performance Monitoring Service.

8 Error Service Error when restarting Performance Monitoring Service.

9 Information Management console

The user (account: domain\account) from the machine ‘machine’ logged out.

10 Error Data collecting The specified performance data (title: 'title', category name: ’category’, instance name: ’instance’, counter name: ’counter’) cannot be collected on the monitored machine ‘Machine’. This type of performance data is not available for machine ‘Machine’.

11 Error Data collecting Failed to collect performance data (title: 'title', category name: ’category’, instance name: ’instance’, counter name: ’counter’) on the monitored machine ‘Machine’.

12 Error Other Failed to connect to the database (Server: Server\Instance, DataBase: DataBase).

13 Error Other Failed to update the database.

14 Error Other Failed to initialize the data.

15 Error Other Failed to reference the database.

16 Warning Service Failed to save the Performance Monitoring Service settings. Will read the previous settings at the next activation.

17 Warning Service Failed to read the Performance Monitoring Service settings. Will read the initial settings.

18 Error Management console

Failed to logon to the account (domain\account) from the machine ‘machine’.

19 Warning Data collecting Cannot access the monitored machine ‘Machine’.

20 Error Other Failed to initialize the logging facility.

21 Error Other Failed to stop the logging facility.


The user (account: domain\account) logged on from the machine ‘machine’.

The Event Log

209



An unknown user account attempted to connect.

24 Error Service Error in termination processing.

25 Error Service Error processing failed.

26 Error Other Internal error: message


Cannot connect to the Management Console (Uri: URL).

28 Error Other Failed to delete performance data after the storage period.

29 Error Service Stopped Performance Monitoring Service because an irrecoverable error was detected.

30 Error SystemProvisioning relation

Cannot use SystemProvisioning.


Error when applying SystemProvisioning Configuration.

32 Error Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistics’) of the group ‘Group’ (System provisioning group path: ’PvmGroupPath’) exceeded the upper critical threshold value or fell below the lower critical threshold value (Value).

33 Error Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) exceeded the upper critical threshold value or fell below the lower critical threshold value (Value).

34 Warning Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistic’s) of the group ‘Group’ (SystemProvisioning group path: ’PvmGroupPath’) exceeded the upper warning threshold value or fell below the lower warning threshold value (Value).

35 Warning Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) exceeded the upper warning threshold value or fell below the lower warning threshold value (Value).

36 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistics’) of the group ‘Group’ (SystemProvisioning group path: ’PvmGroupPath’) recovered from the critical value (Value).

37 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) recovered from the critical value (Value).

38 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistics’) of the group ‘Group’ (SystemProvisioning group path: ’PvmGroupPath’) recovered from the warning value (Value).

39 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) recovered from the warning value (Value).

40 Error Performance information

No performance indicator (title: ’Title’) specified for the OS of the object machine (machine name: ’Machine’).

9 Troubleshooting



41 Warning Data collecting Failed to collect performance data (title: ‘Title’, resource: ’Resource’, instance: ’Instance’, and performance index: ‘PerformanceIndex’) about the monitored machine ‘Machine’.


Failed to notify SystemProvisioning.

43 Error Performance information

Illegal specification of the performance indicator (title: ’Title’)

44 Information SystemProvisioning relation

Applied the SystemProvisioning Configuration.

45 Information Data collecting Already connected to the target machine 'Machine' (shared resource: 'Resource'). Use this connection for collecting performance data.

46 Error Data collecting Failed to disconnect to the target machine 'Machine' (shared resource: 'Resource').

47 Information System configuration

Added machine 'Machine' to group 'Group'.


Removed machine 'Machine' from group 'Group'.


Moved machine 'Machine' from group 'Group' to group 'Group'.


Changed setting for machine 'Machine'.

51 Error Data collecting Machine 'Machine' had an access error.

52 Information Data collecting Machine 'Machine' recovered from an access error.


Added group 'Group'.


Removed group 'Group'.


Changed setting for group 'Group'.

56 Information Setting Changed settings for collecting performance data.

57 Information Setting Changed settings for threshold monitoring.

58 Information Setting Changed settings for configuration.

62 Warning Data collecting No performance data (title: 'Title') about machine 'Machine' existed. Calculated performance data about group 'Group' at 'Time' without performance data about machine 'Machine'.

63 Warning Data collecting Cannot finish collecting performance data (title: 'Title') about machine 'Machine' in time (Time-Time)

64 Error Other Failed to output a debug log.

65 Warning SystemProvisioning relation

Made a notification to SystemProvisioning on the node 'Node'. SystemProvisioning Configuration Application is not enabled for the node 'Node'.

66 Error Data collecting An error occurred in the connection to the target machine 'Machine'.

The Event Log

211


67 Warning Other The database size has exceeded warning value WarningSizeGB. The current size is CurrentSizeGB.

69 Information Data collecting The collecting of the performance data (title: 'Title') is succeeded on the monitored machine 'Machine'.

70 Error Data collecting Failed to calculate performance data (machine: 'Machine', title: 'Title', resource: 'Resource', instance: 'Instance', performance index: 'Index').

71 Information Data collecting Paused collecting performance data of machine 'Machine'.

72 Information Data collecting Restarted collecting performance data of machine 'Machine'.

73 Information Data collecting Paused collecting performance data of group 'Group'.

74 Information Data collecting Restarted collecting performance data of group 'Group'.

75 Warning Data collecting Failed to calculate performance data (machine: 'Machine', title: 'Title', Category: 'Category', Instance: 'Instance', Counter: 'Counter').

76 Information Data collecting The output messages differ depending on the collection root of machine performance data as the following: 1. Windows machine (via .NET Framework) Performance data collect via 'Windows OS' for machine 'machine' recovered. 2. Hyper-V server (via WMI) Performance data collect via 'Windows WMI' for machine 'machine' recovered. 3. Windows machine (via remote user script) Performance data collect via 'Remote Script' for machine 'machine' recovered. 4. Linux machine and KVM server Performance data collect via 'Linux OS' for machine 'machine' recovered. 5. VMware ESXi server Performance data collect via 'VMware ESXi' for machine 'machine' recovered. 6. VMware ESXi virtual machine Performance data collect via 'VMware ESXi(VMServer)' recovered. 7. Xen server Performance data collect via 'Xen' for machine 'machine' recovered. 8. Hyper-V/KVM/Xen virtual machine (via SystemProvisioning) Performance data collect via 'SystemProvisioning(SystemProvisioning)' recovered.

9 Troubleshooting



77 Error Data collecting The output messages differ depending on the collection root of machine performance data as the following: 1. Windows machine (via .NET Framework) Performance data collect via 'Windows OS' for machine ‘machine’ had an access error. 2. Hyper-V server (via WMI) Performance data collect via 'Windows WMI' for machine ‘machine’ had an access error. 3. Windows machine (via remote user script) Performance data collect via 'Remote Script' for machine ‘machine’ had an access error. 4. Linux machine and KVM server Performance data collect via 'Linux OS' for machine ‘machine’ had an access error. 5. VMware ESXi server Performance data collect via 'VMware ESXi' for machine ‘machine’ had an access error. 6. VMware ESXi virtual machine Performance data collect via 'VMware ESXi(VMServer)' had an access error. 7. Xen server Performance data collect via 'Xen' for machine ‘machine’ had an access error. 8. Hyper-V/KVM/Xen virtual machine (via SystemProvisioning) Performance data collect via 'SystemProvisioning(SystemProvisioning)' had an access error.

78 Error Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistics’) of the group ‘Group’ (System provisioning group path: ’PvmGroupPath’) exceeded the upper critical threshold value or fell below the lower critical threshold value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

79 Error Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) exceeded the upper critical threshold value or fell below the lower critical threshold value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

80 Warning Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistic’s) of the group ‘Group’ (SystemProvisioning group path: ’PvmGroupPath’) exceeded the upper warning threshold value or fell below the lower warning threshold value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

81 Warning Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) exceeded the upper warning threshold value or fell below the lower warning threshold value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

The Event Log

213


82 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistics’) of the group ‘Group’ (SystemProvisioning group path: ’PvmGroupPath’) recovered from the critical value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

83 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) recovered from the critical value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

84 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ (Statistics: ’Statistics’) of the group ‘Group’ (SystemProvisioning group path: ’PvmGroupPath’) recovered from the warning value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

85 Information Threshold monitoring The performance indicator ‘PerformanceIndicatorTitle’ of the machine ‘Machine’ (SystemProvisioning path: ’PvmPath’) recovered from the warning value (Value). Reported [Event Category]eventcategory [Event]event to SystemProvisioning.

86 Error Data collecting Failed to collect performance data (title: 'title', executing string: 'executingstring') about the monitored machine 'machine'.


Error when applying SystemProvisioning Configuration for group (SystemProvisioning path: ' pvmGroupPath ').


Error when applying SystemProvisioning Configuration for DiskArray (SystemProvisioning path: ' diskArrayPath)'.

90 Error Data collecting The specified performance data (title: 'title', metric group: 'metricgroup', object: 'object', counter: 'counter') cannot be collected on the monitored machine ''machine''. This type of performance data is not available for machine ''machine''.

91 Error Data collecting The specified performance data (title: ''title'', resource: 'resource', instance: 'instance', performance index: 'performanceindex') cannot be collected on the monitored machine 'machine'. This type of performance data is not available for machine ''machine''.

110 Error Data collecting Failed to collect performance data by executing script 'localscript'.

111 Information Data collecting Succeeded to collect performance data by executing script ' localscript'.

112 Error Data collecting Failed to collect performance data on monitored target 'machine' by executing script 'remotescript'.

113 Information Data collecting Succeeded to collect performance data on monitored target ''machine ' by executing script ' remotescript'.

114 Error Data collecting Failed to read the encode setting which is used at gathering performance data by SSH connection.


Error when applying SystemProvisioning Configuration for resource pool.

116 Error Data collecting Failed to collect performance data (title: 'title') about the monitored resource pool ' resourcePool '.

9 Troubleshooting



117 Information Data collecting The collecting of the performance data (title: ' title ') is succeeded on the monitored resource pool ' resourcePool '.


Error when applying SystemProvisioning Configuration for SigmaSystemCenter managed objects.

127 Error Data collecting Failed to collect statistic information of SigmaSystemCenter managed objects.

128 Information Data collecting Succeeded to collect statistic information of SigmaSystemCenter managed objects.

Note: When collecting performance data of the managed machines which are registered in System Monitor - Performance Monitoring Services by SystemProvisioning Configuration Application is interrupted, the access errors are not output to the event logs. Only when the conditions of the machine meet the all following terms in the SystemProvisioning, data collection will be started. In any other cases, data collection will be interrupted. ◆ Power Status: "On"

◆ OS Status: "On" ◆ Executing Status: "Not Executing"

The Event Log

215

9.1.2. Event logs for Management Console

source name： SystemMonitorPerformanceConsole



Connected to Management Server 'Server'.


Disconnected to Management Server 'Server'.


An error occurred in the connecting/disconnecting to the Management Server 'Server'.


Internal error: message


Started management console.


The Management Console is closed.


Failed to initialize the connection. Change the settings of the Management Console.


The time difference between the management server Server and this console machine is larger than Time minutes.

Note: By default, previous logs are overwritten when the maximum log size is reached. To change these default settings, configure the Event Viewer settings. See 9.10 "Other 3. Situations where logs are not recorded in the event log" for information on how to change the Event Viewer settings.

9 Troubleshooting


9.2. What to do if the Performance Monitoring Service does not Start

After System Monitor - Performance Monitoring Services is installed, the Performance Monitoring Service (System Monitor Performance Monitoring Service) should start when the management server is restarted. If the Performance Monitoring Service does not start, this could be due to one of the causes listed as (1) to (7) below. Isolate the cause by checking the message that is output when the Performance Monitoring Service fails, and then take the action listed below. Error messages are also displayed when the Performance Monitoring Service is started manually. Refer to (7) if you enabled the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing policy in Local Computer Policy on the management server. Refer to (3), (4), (5), and (6) if you changed the execution account from the local system account.

When execution account is changed from a local system account, confirm the following.

◆ "User must change password at next logon" option has not been added.

◆ The password has not expired.

① The Database Settings are not correct SQL Server <Messages that are output>

• Event log

Log Type Source ID Description Notes

Application Error SystemMonitor Performance Service

0 Service cannot be started. System.Data.SqlClient.SqlException: Cannot open database requested in login 'RM_PerformanceDataBase2'. Login fails.


Error SystemMonitorPerformanceService

5 Error when starting Performance Monitoring Service. Details: Cannot open database requested in login 'RM_PerformanceDataBase2'. Login fails.



12 Failed to connect to the database (Server: Server\Instance, DataBase: dataBase). Details: Cannot open database requested in login 'RM_PerformanceDataBase2'. Login fails.

What to do if the Performance Monitoring Service does not Start

217

• Error messages

Message Notes

The System Monitor Performance Monitoring Service service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

<Action>

1. The database may be configured incorrectly. In this case, edit the configuration by using the database configuration tool of System Monitor - Performance Monitoring Services (System Monitor - Performance Monitoring Services installation folder\bin\rm_databasecfg.exe), and then restart the Performance Monitoring Service.

2. The database may not have been set up correctly, or a database file may be damaged. Reinstall System Monitor - Performance Monitoring Services.

PostgreSQL <Messages that are output>

• Event log



0 Service cannot be started. *************************************



5 Error when starting Performance Monitoring Service. Details: *************************************



12 Failed to connect to the database (Server: Server, DataBase: dataBase). Details: No connection could be made because the target machine actively refused it.



12 Failed to connect to the database (Server: Server, DataBase: dataBase).Details: 28P01: password authentication failed for user "user"



12 Failed to connect to the database (Server: Server, DataBase: dataBase). Details: 28000: no pg_hba.conf entry for host "server", user "user", database " database ", SSL off

• Error messages

Message Notes

Windows could not start the System Monitor Performance Monitoring Service service on local computer. Error 1503: The service did not response to the start or control request in a timely fashion.

9 Troubleshooting


<Action>

1. The PostgreSQL service may not be started. Start the PostgreSQL service (the service display name is started with "postgresql") manually.

2. The database may be configured incorrectly. The details differ depending on the massages:

• No connection could be made because the target machine actively refused it.

This message is displayed when the PostgreSQL server is inaccessible. Check the host name or port number in the database configuration. • 28P01: password authentication failed for user "user" This message is displayed when the account or password configured in the database is incorrect. Edit the configuration by using the database configuration tool of System Monitor - Performance Monitoring Services (System Monitor - Performance Monitoring Services installation folder\bin\rm_databasecfg.exe), and then restart the data management tool.

3. The access from the management server of System Monitor - Performance Monitoring Services to the PostgreSQL may not be permitted. In this case, the following message is displayed: • 28000: no pg_hba.conf entry for host "server", user "user", database

" database ", SSL off Give the permission by editing pg_hba.conf of the PostgreSQL, and then restart the PostgreSQL service.

4. The database files may be damaged. Re-install the PostgreSQL.

② The Database cannot be Referenced or Updated See "9.9.3 Errors and Actions for Database Faults".

③ The Execution Account and Password Settings for the Performance Monitoring Service are not correct <Messages that are output>

• Event log


System Error Service Control Manager

7000 The System Monitor Performance Monitoring Service service failed to start due to the following error: The service did not start due to a logon failure.


7038 The SystemMonitor Performance Service service was unable to log on as domain\account with the currently configured password due to the following error: Logon Failure: unknown user name or bad password.


219

• Error messages

Message Notes

Windows could not start the System Monitor Performance Monitoring Service service on Local Computer. Error 1069: The service did not start due to a logon failure.

<Action> Set the execution account and password for the Performance Monitoring Service correctly. See "2.5 The Execution Account for the Performance Monitoring Service" for information about execution account.

④ The Execution Account for the Performance Monitoring Service does not have OS Administrator Authority <Messages that are output>

• Event log



0 Service cannot be started. System.Security.SecurityException: Requested registry access is not allowed.


Error SystemMonitor Performance Service

5 Error when starting Performance Monitoring Service. Requested registry access is not allowed.

• Error messages

Message Notes

The System Monitor Performance Monitoring Service service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

<Action> The execution account for the Performance Monitoring Service must have OS administrator authority for the management server. Specify an account that has OS administrator authority as the execution account for the Performance Monitoring Service. See "2.5 The Execution Account for the Performance Monitoring Service" for information about execution account.

⑤ The Execution Account for the Performance Monitoring Service does not have "Log on as a Service" Rights <Messages that are output>

• Event log




9 Troubleshooting



7041 The SystemMonitor Performance Service service was unable to log on as domain\account with the currently configured password due to the following error:

Logon failure: the user has not been granted the requested logon type at this computer.

• Error messages

Message Notes

Windows could not start the System Monitor Performance Monitoring Service service on Local Computer. Error 1069: The service did not start due to a logon failure.

<Action> The execution account for the Performance Monitoring Service must have "Log on as a service" rights.

Add this right, referring to "2.5.3 Rights for the Performance Monitoring Service Execution Account". Also, if the account has "Deny log on as a service" rights, delete these rights.

⑥ An Account with an Empty Password has been specified as the Execution Account for the Performance Monitoring Service <Messages that are output>

• Event log





7038 The SystemMonitor Performance Service service was unable to log on as domain\account with the currently configured password due to the following error:

Logon failure: unknown user name or bad password.

• Error messages

Message Notes

Windows could not start the System Monitor Performance Monitoring Service on Local Computer. Error 1069: The service did not start due to a logon failure.

<Action> It is possible to specify the security option "Limit local account use of blank passwords to console logon only". If this option is enabled, accounts that have blank passwords cannot be used as the execution account for the Performance Monitoring Service. Use an account for which a password has been set up.


221

⑦ The policy "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing", which is in Security Settings in Local Computer Policy, is enabled on the management server <Messages that are output>

• Event log



0 Service cannot be started. System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

• Error messages

Message Notes

The System Monitor Performance Service service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

<Action>

RC2 is the default encryption algorithm used in SystemMonitor Performance Service. The algorithm is not compliant with FIPS 140-2 cryptographic algorithm, and, because of this, it causes an error when a service is started. You can work around this issue as follows:

1. On Local Computer Policy, disable the security setting of System cryptography: Use FIPS compliant algorithm for encryption, hashing, and signing, and then restart the System Monitor Performance Monitoring Service.

2. If your business security policy does not allow for you to disable System cryptography: Use FIPS compliant algorithm for encryption, hashing, and signing, perform the following procedure to change the encryption algorithm:

(1) Disable the System cryptography: Use FIPS compliant algorithm for encryption, hashing, and signing setting, and then return System Monitor Performance Monitoring Service to the state in which it can use the original encryption algorithm.

(2) On the System Monitor Performance Monitoring Service management server, add the following appSettings setting immediately under the configuration tag of .Net Framework's machine config (%windir%\Microsoft.NET\Framework64\v4.0.30319\Config) to change the encryption algorithm used in System Monitor Performance Monitoring Service from RC2 to 3DES. After changing the setting, start the System Monitor Performance Monitoring Service. <appSettings>

<add key="SystemMonitorPerformanceMonitoringEncryption" value="3DES"/>

</appSettings>

(3) On the SigmaSystemCenter management server, add the following appSettings setting immediately under the configuration tag of .Net Framework's machine config

9 Troubleshooting


(%windir%\Microsoft.NET\Framework\v4.0.30319\Config) to change the encryption algorithm used to connect to System Monitor Performance Monitoring Service from RC2 to 3DES. If the file is same as that changed in (2), the configuration change is not needed. After changing the setting, start the PVMService. <appSettings>

<add key=" SystemMonitorPerformanceMonitoringEncryption" value="3DES"/>

</appSettings>

(4) Enable the System cryptography: Use FIPS compliant algorithm for encryption, hashing, and signing setting.

Note: You must use the same encryption algorithm between a management console and a management server when you connect System Monitor - Performance Monitoring Services from a management console that is installed on a different server from a management server.

What to do if the Connection from Management Console to Server Fails

223

9.3. What to do if the Connection from Management Console to Server Fails

The following lists error messages output when connection from the management console to the management server failed, and actions to be taken.

Log Type Source ID Description


Error SystemMonitorPerformanceConsole

77 An error occurred in the connecting/disconnecting to the Management Server 'Server'. Details: No connection could be made because the target machine actively refused it.

Action

• Check whether the management server is running.

• Start the Performance Monitoring Service on the management server if it is not running already.

• Check whether there are any network problems between the management server and the management console machine.

• Check whether the port number for the Performance Monitoring Service has been changed. If so, specify the new port number.




77 An error occurred in the connecting/disconnecting to the Management Server 'Server'. Details: Logon failure.

Action

• Check the account and password specifications.

• Accounts that do not have OS administrator authority cannot log on. Check whether the account has OS administrator authority.

• If either the logon account or the groups to which it belongs has been set to any of the following in Security Settings, the account cannot logon. Check the Security Settings of the logon account and the groups it belongs to. Neither the user account nor any of the groups to which it belongs has been granted the

Access this computer from the network user right. The user account or one or more of the groups it is a member of has been listed in the

Deny access to this computer from the network.

• Check if the same encryption algorithm is used between a management console and a management server when you connect System Monitor - Performance Monitoring Services from a management console that is installed on a different server from a management server. For details, see ⑦ The policy "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing", which is in Security Settings in Local Computer Policy, is enabled on the management server

9 Troubleshooting





89 Failed to initialize the connection. Change the settings of the Management Console. Details: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Action

• The port number used for communications from the Performance Monitoring Service to the management console is already being used by another product. Change the port number in management console information.

• There is a possibility that multiple management consoles are running on a console machine. If multiple management consoles are already running, verify that each management console has different port number settings for its management console information.




77 An error occurred in the connecting/disconnecting to the Management Server 'Server'. Details: Illegal setting on management console information. Connection timeout due to no response from Performance Monitoring Service.

Action

• Check the host name setting for the management console information. Verify that the management server can access the management console machine using the specified host name.

• Check whether there are any problems with the network between the management server and the management console machine.




77 An error occurred in the connecting/disconnecting to the Management Server 'Server'. Details: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Action

• Check whether there are any problems with the network between the management server and the management console machine.

What to do if Performance Data Collecting Fails

225

9.4. What to do if Performance Data Collecting Fails

If the collecting of performance data fails, refer to the following actions. The collecting status for performance data is displayed using icons in the navigation tree window. See "4.4 Checking the Collecting Status for Performance Data" for the meanings of these icons. The navigation tree window:

Collecting failed for some Performance Indicator items (performance indicator

error status)

The machine cannot be accessed or collecting failed for all Performance

Indicators for the machine (access error status)

In Windows machines, VMware ESXi virtual machine servers or virtual machines data collecting, when Category and Counter is specified correctly but Instance is incorrect, the performance data will not be collected. But the monitored machine will not be set to be an error status. If performance data is not being collected even though no errors are recorded in the event log and the icon display do not indicate an error, then verify that the instance name for the Performance Indicator is correct.

9.4.1. Errors and Actions for when Performance Data Collecting

Fails

The event logs for when performance data collecting fails and the actions to take are listed below.



Warning SystemMonitor PerformanceService

19 Cannot access the monitored machine 'Machine'.

9 Troubleshooting




41 Failed to collect performance data (title: 'title', resource: 'Resource', instance: 'Instance', and performance index: 'PerformanceIndex') about the monitored machine 'Machine'.

Action

• Check the specifications for the machine name or IP address. OS names registered by using the "Applying SystemProvisioning Configuration" feature cannot change from System Monitor - Performance Monitoring Services. If the names are registered wrong by mistake, in the SigmaSystemCenter Web Console, you can correct the name by editing OS Type in Group, Model, or Host profile in Host Setting of the Operation view.

• The Performance Monitoring Service accesses managed machines using the specified account name and password. Check the following points concerning the user accounts for the managed machine: An account with the same account name and password as the execution account has

been registered on the managed machine.

The password for the account has not expired.

• Check that an IP address has been set up on the managed machine settings, or the name of the managed machine has been registered with DNS or the "hosts" file on the management server.

• Check the following when the SystemProvisioning configuration is applied to System Monitor - Performance Monitoring Services: System Monitor - Performance Monitoring Services uses the Management IP address

already set up using SystemProvisioning to connect to the managed machines. Specify the Management IP address in the Machine Settings window with the SigmaSystemCenter Web Console. When the IP address is not specified, System Monitor - Performance Monitoring Services uses the machine name to connect to the managed machines. If the managed machine is a Linux machine, VMware ESXi or Citrix XenServer, the machine name must be registered with either DNS or the "hosts" file on the System Monitor - Performance Monitoring Services management server.

Check the OS name on the machine settings. When this OS name is incorrect, check the configuration settings on SystemProvisioning.

• If the managed machine is running a Windows operating system:

Check File and Printer Sharing for Microsoft Networks is enabled in managed machines that are accessible from System Monitor - Performance Monitoring Services via the internet.

The Performance Monitoring Service accesses managed machines using the specified account name and password. According to the settings, the Performance Monitoring Service accesses managed machines using the service execution account. For conditions to be used


227

the service execution account as an access account, see "2.5.1 Setting up the Performance Monitoring Service Execution Account". Check the following points concerning the user accounts for the managed machine: This account belongs to the Administrator group or Performance Monitor Users group of

the managed machine.

The "User must change password at next logon" option has not been added to the account.

This account does not have a blank password.

If either the account or the groups to which it belongs has been set to any of the

following in Security Settings, the account cannot access the managed machine. Check Security Settings of the account and the groups it belongs to.

The "Access this computer from the network" right is not assigned to both the account and the group which the account belongs to.

The "Deny access to this computer from the network" right list contains the account or one or more groups which the account belongs to.

Start the following service for managed machines. Remote Registry Server

Check the following points concerning the connection to managed machines: If the Windows firewall function for the managed machine has been enabled, make

exception settings for the Windows firewall by referring to "1.7.4 Ports Used between Management Servers and Managed Machines"

• If the managed machine is running a Linux OS/KVM: SSH service has started. Authentication protocol is set correctly.

SSH communications have been exempted from firewall blocking. In an SSH server, check an algorithm is specified correctly in /etc/ssh/sshd_config. Note

that if you want to change the algorithm from the default, you must select from aes128-ctr, aes192-ctr, aes256-ctr, aes128-cbc, aes192-cbc, aes256-cbc, arcfour, arcfour128, arcfour256, lowfish-cbc, cast128-cbc, twofish-cbc, twofish192-cbc, twofish128-cbc, or twofish256-cbc.

• If VMware ESXi is the managed machine (VMware Web Service is used to connect): Check the following points concerning the user accounts for the managed machine:

An account with the same account name and password as the specified account has been registered on the managed machine.

A role other than "No Access" is assigned to the connection account on the VMware ESXi.

9 Troubleshooting


Check the following points: An IP address has been set up on the managed machine settings.

VMware Web Service has started on the VMware ESXi. SSL communications have been exempted from firewall blocking.

• If the managed machine is a virtual machine running on a VMware ESXi. Check the following points: The virtual machine and the VMware ESXi are monitored by the same management

server. Collecting performance data from the VMware ESXi is successfully performed.

• If Citrix XenServer is the managed machine:

Check the following points: An IP address has been set up on the managed machine settings. SSL communications have been exempted from firewall blocking.

The managed machine is a pool master machine or a target of the SystemProvisioning configuration application.

• Check whether the managed machine is running.

• Check whether there are any network problems between the management server and the managed machine.

• It may not be possible to access the managed machine if it is under high load. • Check whether the managed machine's OS is supported by System Monitor – Performance

Monitoring Services.

• In a physical machine of Current Power (W) or collecting performance data for Hyper-V/KVM/Xen, if the detail of a displayed message is "Cannot connect to SystemProvisioning. Check the settings for SystemProvisioning and the status of the SystemProvisioning Management Server," check the following: In System Monitor Management Console, check SystemProvisioning Management

Server name, the management server > Configuration > the SystemProvisioning tab, is specified correctly.

If the managed machines are clustered by using EXPRESSCLUSTER, check localhost or a floating IP is specified for SystemProvisioning Management Server Name.

In the same clustered group between System Monitor - Performance Monitoring Services and SystemProvisioning, check localhost or a floating IP is specified.

In the different clustered group between System Monitor - Performance Monitoring Services and SystemProvisioning, check a floating IP is specified.

Check the PVMService service is started in the SystemProvisioning Management server.


229




10 The specified performance data (title:'title', category name: 'category', instance name: 'instance', counter name: 'counter') cannot be collected on the monitored machine 'Machine'. This type of performance data is not available for machine 'Machine'. Details: *************************************



43 Illegal specification of performance indicator (title: 'title')

Action

Check the detailed information in the event log description (the section after "Details :").

• Fix any mistakes with the specification for Performance Indicators.

• If a Performance Indicator category is specified that is not supported by the operating system and applications on the managed machine, it may not be possible to collect the performance data because the specified category does not exist on the managed machine. The Performance Indicators that can be collected on a managed machine depend on the type of OS and on the applications that are installed. Check whether the specified Performance Indicator can be collected. See "1.3 Collected Performance Data" for information on the categories that System Monitor - Performance Monitoring Services supports.

• If both System Monitor - Performance Monitoring Services and other performance monitoring products monitor one Windows managed machine at the same time, the "Category does not exist" error might occur while collecting the performance data.

System Monitor - Performance Monitoring Services uses the Windows performance monitor feature to obtain the performance data from the Windows managed machine. This issue occurs other monitoring products also use the Windows performance monitor feature as well as System Monitor - Performance Monitoring Services. Use either System Monitor - Performance Monitoring Services or other products to monitor the Windows managed machine.

• If the icon is displayed for a managed machine, the machine is in a performance

indicator error status. Change the Performance Indicator settings for the machine.




112 Failed to collect performance data on monitored target 'machine' by executing script 'remotescript'. Details: *************************************

Action

Check the detailed information in the event log description (the section after "Details :"). Possible

9 Troubleshooting


causes for each problem are as follows.

• Cannot access the managed machine ‘Machine’. Check the power status and the OS status of the machine. Check the machine name or the IP address, and what OS name is specified. Check that the machine is established as an SSH server.

Check that the SSH service is enabled. When the firewall is enabled, check the firewall exception setting is configured. (If not, configure the firewall exception setting seeing "1.7.4 Ports Used between Management Servers and Managed Machines".) In an SSH server, check one of the following is used. You must select from aes128-ctr,

aes192-ctr, aes256-ctr, aes128-cbc, aes192-cbc, aes256-cbc, arcfour, arcfour128, arcfour256, lowfish-cbc, cast128-cbc, twofish-cbc, twofish192-cbc, twofish128-cbc, or twofish256-cbc for System Monitor - Performance Monitoring Services.

• User authentication failed. Check that the same account name and password with the specified account are

registered.

Check that the appropriate authentication protocol is specified. Check that the specified account has the SSH access right.

• ’"@metric value" was not outputted from the script.’ or ‘"@metric value" was not outputted from the script for performance indicator {1} of the machine {0}.’ If the performance indicator contains wrong execution strings specified, correct them.

The script is not written to output "@metric value" to the standard output. Review the contents of the script seeing "1.3.3, Custom Performance Indicator"

• The variable 'variable' is not a Reserved Variable. Review the specified reserved variable in the script.

• Because the monitoring target has not been registered by applying SystemProvisioning Configuration, cannot use the Custom Property ' customProperty'.Applying SystemProvisioning Configuration.

Delete the customized property from the script.

• Custom Property 'customProperty' has not been defined for the monitored machine in SystemProvisioning. Delete the customized property from the script. Define a customized property in SigmaSystemCenter.


231




110 Failed to collect performance data by executing script 'localscript'. Details: *************************************

Action

Check the detailed information in the event log description (the section after "Details :"). Possible causes for each problem are as follows.

• ’"@metric value" was not outputted from the script.’ or ‘"@metric value" was not outputted from the script for performance indicator {1} of the machine {0}.’

If the performance indicator contains wrong execution strings specified, correct them. The script is not written to output "@metric value" to the standard output. Review the

contents of the script seeing "1.3.3, Custom Performance Indicator"

• The variable 'variable' is not a Reserved Variable. Review the specified reserved variable in the script.

• Because the monitoring target has not been registered by applying SystemProvisioning Configuration, cannot use the Custom Property 'customProperty'.Applying SystemProvisioning Configuration. Delete the customized property from the script.

• Custom Property 'customProperty' has not been defined for the monitored machine in SystemProvisioning. Delete the customized property from the script.

Define the customized property in SigmaSystemCenter.




127 Failed to collect statistic information of SigmaSystemCenter managed objects. Details: *************************************

Action

• Cause This error occurs when SigmaSystemCenter Managed Objects are removed from SystemProvisioning just after the tenants, categories, or groups of SystemProvisioning are reconfigured.

• Action Perform "Apply SystemProvisioning Configuration" in the SystemMonitor Management Console to synchronize the information of System Monitor - Performance Monitoring Services with the configuration of SystemProvisioning.

9 Troubleshooting


9.4.2. Error Status Recovery Processing

System Monitor - Performance Monitoring Services stops data collecting processing for managed objects that it has failed to access or for which all Performance Indicators failed to be collected. Machines where data collecting processing has stopped are

displayed using the icon. Machines where data collecting processing has partially

failed are displayed using the icon.

Remove the error cause to restart data collecting. To restart data collecting in arbitrary timing, perform error status recovery. The procedure for error status recovery processing is as follows:

1. Right-click the managed object name and click Change Data Collecting Status. A window appears.

2. Click Recover from error status. When data collecting starts, the icon display for

the machine will change to .

When error status recovery processing is performed for a group, error status recovery processing is executed for every managed object in the group.

The procedure for error status recovery processing for groups is as follows:

1. Right-click the group name and select Change Data Collecting Status. A window appears.


233

2. Click Recover from error status. When data collecting starts, the icon display for

the group will change to and the icon display for machines in the group will

change to .

9 Troubleshooting


9.5. What to do if Performance Data Collecting is delayed

If the collecting of performance data is delayed, refer to the following actions. What we call "Data Collecting Delay" is the situation that a performance data collecting could not be finished within the specified period. When this delay occurs, a discontinued graph line may appear on the graph window and a notification of monitoring threshold may be delayed.

A warning log on the event log can be seen when the performance data collecting is delayed.

9.5.1. Errors and Actions for when Performance Data Collecting

is delayed

The event logs for when performance data collecting is delayed and the actions to take are listed below.




63 Cannot finish collecting performance data (title: 'Title') about machine 'Machine' in time (StartTime-EndTime).

Action

• The number of data to be collected within a specified period may be too much. Consider the following actions. Increasing the data collecting interval Reducing the number of Performance Indicator items that are collected

Reducing the number of managed objects that are monitored

• The load of the management server may be too high. Check the reason of this high load and exclude this reason from your system.

• An internal operation of Windows may let the data collecting operation take too long time when the OS of the managed machine is Windows Vista or Windows Server 2008 R1. If this entry is logged, consider to increase the data collecting interval.

What to do if there are SystemProvisioning Configuration Applying Errors

235

9.6. What to do if there are SystemProvisioning Configuration Applying Errors

SystemProvisioning configuration information can be applied to System Monitor - Performance Monitoring Services. If an error occurs during configuration applying process, identify the cause by checking the message that has been output, and then take the appropriate action.

① Cannot access the SystemProvisioning management server




30 Cannot use SystemProvisioning. Details: Cannot connect SystemProvisioning

Action

• Verify that the name of the SystemProvisioning management server is correct. Refer to Section, "2.6 SystemProvisioning Connection Settings" for information on how to make this setting.

• Verify that the SystemProvisioning management server is running correctly.

• Verify that each SystemProvisioning service is running correctly. • If the Performance Monitoring Service and SystemProvisioning are not on the same

management server and a Windows Firewall has been enabled on the SystemProvisioning management server, open the port for SystemProvisioning UniversalConnector. Refer to Section, "2.6 SystemProvisioning Connection Settings" for more information on firewall settings.

• If the Performance Monitoring Service and SystemProvisioning are not on the same management server, verify that the Performance Monitoring Service execution account is same as the OS administrator account of SystemProvisioning management server.

• When SystemProvisioning is clustered with EXPRESSCLUSTER, localhost or a floating IP cannot be used as SystemProvisioning Management Server name. In the same clustered group between System Monitor - Performance Monitoring Services

and SystemProvisioning, check localhost or a floating IP is specified.


9 Troubleshooting


② SystemProvisioning is not running correctly




31 Error when applying SystemProvisioning Configuration. Details: Input data contains invalid character.

Action

• Verify that the version of SystemProvisioning being linked is supported by System Monitor - Performance Monitoring Services.

③ Performance indicator does not exist




31 Error when applying SystemProvisioning Configuration. Details: Specified performance indicator is not found.

Action

• The monitoring profile is specified on SystemProvisioning, but a performance indicator which does not exist on System Monitor - Performance Monitoring Service is included in it.

• Verify whether the monitoring profile specified on SystemProvisioning is correct. • Verify whether the performance indicator is defined correctly on System Monitor - Performance

Monitoring Service.

What to do if there are Errors when Performance Abnormalities are reported to SystemProvisioning

237

9.7. What to do if there are Errors when Performance Abnormalities are reported to SystemProvisioning

System Monitor - Performance Monitoring Services can use monitoring thresholds for Performance Indicators that are collected to detect abnormalities in the load status of monitored machines and can report such abnormalities to SystemProvisioning.

If an error occurs when an abnormality is reported, identify the cause by checking the message that has been output, and then take the appropriate action. ① Cannot Access the SystemProvisioning Management Server




42 Failed to notify SystemProvisioning. Details: System error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Action

• Verify that the name of the SystemProvisioning management server is correct. Refer to Section, "2.6 SystemProvisioning Connection Settings" for more information.

• Verify that the SystemProvisioning management server is running correctly. • Verify that the "System Monitor Service" has started on the SystemProvisioning management

server.

• If the Performance Monitoring Service and SystemProvisioning are not on the same management server and a Windows Firewall has been enabled on the SystemProvisioning management server, open the port for System Monitor - vent Monitoring Services. Refer to Section, "2.6 SystemProvisioning Connection Settings" for more information on firewall settings.

• If the Performance Monitoring Service and SystemProvisioning are not on the same management server, verify that the Performance Monitoring Service execution account is same as the OS administrator account of SystemProvisioning management server.

• When SystemProvisioning is clustered with EXPRESSCLUSTER, localhost or a floating IP cannot be used as SystemProvisioning Management Server name. In the same clustered group between System Monitor - Performance Monitoring Services

and SystemProvisioning, check localhost or a floating IP is specified.


9 Troubleshooting


② SystemProvisioning is not running correctly




42 Failed to notify SystemProvisioning. Details: Could not resolve a call to the correct method.

Action

• Verify that the SystemProvisioning management server is running correctly. • Verify that each service on the SystemProvisioning management server is running correctly.

What to do if the SystemMonitor data management tool might not start

239

9.8. What to do if the SystemMonitor data management tool might not start

If an error message appears when you start the SystemMonitor data management tool, the tool might fail to connect to the database.

The following describes about possible causes and potential solutions for the error. Determine the cause based on the circumstances in which the error occurred and resolve the error.

SQL Server • Cannot connect to the database

This error message appears if the database service that uses System Monitor - Performance Monitoring Services is not started yet. If this message appears, start the SQL Server service as the following description.

The database service starts automatically at startup of the Performance

Monitoring Service. When starting it manually, start the service whose name is

"MSSQL$Instance Name" (the default instance name is "SSCCMDB"). After checking the above and eliminating the problem, restart the data management tool. • The execution account does not have the privilege to connect to the database

If the execution account without the privilege to connect to the database attempts to connect to the SQL Server database from the System Monitor data management tool, the following error occurs.

9 Troubleshooting


The user account to run the System Monitor data management tool must have the sysadmin privilege for the database. Typically this issue occurs if the user account to run the System Monitor data management tool is not same as that specified during SQL Server installation. To resolve this issue, log on to the management server with the user account that has the sysadmin privilege for the System Monitor - Performance Monitoring Services database, and grant the sysadmin privilege to the user account to run the System Monitor data management tool by using the following command. >sqlcmd -E -S (local)\SSCCMDB

1> exec master..sp_addsrvrolemember @loginame = N'domain\account', @rolename = N'sysadmin'

2> go

After checking the above and eliminating the problem, restart the data management tool.

PostgreSQL • Cannot connect to the database

This message is displayed when the PostgreSQL service is not started (in the default, the service is automatically started along with the service of System Monitor - Performance Monitoring Services). In this case, start the PostgreSQL service (the service display name is started with "postgresql") manually, and then restart the data management tool.

• An incorrect configuration for connecting PostgreSQL

What to do if the SystemMonitor data management tool might not start

241

This message is displayed when the configuration for connecting the PostgreSQL is incorrect (such as a user name, password, or port number). In this case, edit the configuration by using the database configuration tool of System Monitor - Performance Monitoring Services (System Monitor - Performance Monitoring Services installation folder\bin\rm_databasecfg.exe), and then restart the data management tool.

9 Troubleshooting


9.9. Database 9.9.1. Estimating the Disk Space Required for Saving

Performance Data

SQL Server • Machine

When 1 managed machine are to be monitored, there are 1 performance indicator, the collection interval is 1 minute, and the default storage period is to be used, then the data size can be estimated as follows.

Collected data 3 (days) * 60 KB = 180 KB

5-minute summary data 7 (days) * 30 KB = 210 KB

15-minute summary data 2 * 30 (days) * 7 KB = 420 KB

1-hour summary data 3 * 30 (days) * 2 KB = 180 KB

1-day summary data 5 * 365 (days) * 0.1KB = 182.5 KB

Total size (180 +210 + 420 + 180 + 182.5) (KB) * 1 (machines) * 1

(performance indicator) = 1172.5 (KB) = approximately 1.2

(MB)

• Resource Pool When the managing condition is 1 managed LUN, 1 performance indicator, the collection interval is 30 minutes, and storage period is default, you can estimate the size of a database as the following:



15-minute summary data 2 * 30 (days) * 3.5 KB = 210 KB



Total size (6 + 35 + 210 + 180 + 182.5) (KB) * 1 (machines) * 1

(performance indicator) = 613.5 (KB) = approximately 0.6 (MB)

By default, each resource pool can collect up to 45 performance information. So that you can estimate the size of a database per resource pool as the following:

0.6 * 45 = approximately 27 MB

Database

243

• LUN on NEC Storage When the managing condition is 1 managed LUN, 1 performance indicator, the collection interval is 1 minute, and storage period is default, you can estimate the size of a database as the following:






Total size (180 +210 + 420 + 180 + 182.5) (KB) * 1 (machines) * 1

(performance indicator) = 1172.5 (KB) = approximately 1.2

(MB)

By default, each LUN can collect up to 4 performance information. So that you can estimate the size of a database per LUN as the following:

1.2 (MB) * 4 = approximately 5 MB In LUNs, use the specified logging interval of stored performance data in NEC Storage Manager instead of the interval of System Monitor - Performance Monitoring Services for the collection interval.

• SigmaSystemCenter Managed Objects When the managing condition is 1 managed SigmaSystemCenter Managed Object, 1 performance indicator, the collection interval is 1 hour, and storage period is default, you can estimate the size of a database as the following:


5-minute summary data 7 (days) * 2.5 KB = 17.5 KB




Total size (3 + 17.5 + 105 + 180 + 182.5) (KB) * 1 (machines) * 1

(performance indicator) = 488 (KB) = approximately 0.5 (MB)

By default, each SigmaSystemCenter Managed Object can collect up to 17 performance information. So that you can estimate the size of a database per SigmaSystemCenter Managed Object as the following:

0.5 (MB) * 17 = approximately 8.5 MB PostgreSQL

• Machine

9 Troubleshooting


When 1 managed machine are to be monitored, there are 1 performance indicator, the collection interval is 1 minute, and the default storage period is to be used, then the data size can be estimated as follows.




1-hour summary data 3 * 30 (days) * 3.5 KB = 315 KB

1-day summary data 5 * 365 (days) * 0.2 KB = 365 KB

Total size (420 +280 + 840 + 315 + 365) (KB) * 1 (machines) * 1


• Resource Pool

When the managing condition is 1 managed resource pool, 1 performance indicator, the collection interval is 30 minutes, and storage period is default, you can estimate the size of a database as the following:






Total size (15 + 49 + 420 + 315 + 365) (KB) * 1 (machines) * 1


By default, each resource pool can collect up to 45 performance information. So that you can estimate the size of a database per resource pool as the following:

1.2 * 45 = approximately 54 MB

Database

245

• LUN on NEC Storage

When the managing condition is 1 managed LUN, 1 performance indicator, the collection interval is 1 minute, and storage period is default, you can estimate the size of a database as the following:






Total size (420 +280 + 840 + 315 + 365) (KB) * 1 (machines) * 1


By default, each LUN can collect up to 4 performance information. So that you can estimate the size of a database per LUN as the following:

2.2 (MB) * 4 = approximately 9 MB

In LUNs, use the specified logging interval of stored performance data in NEC Storage Manager instead of the interval of System Monitor - Performance Monitoring Services for the collection interval.

• SigmaSystemCenter Managed Objects

When the managing condition is 1 managed SigmaSystemCenter Managed Object, 1 performance indicator, the collection interval is 1 hour, and storage period is default, you can estimate the size of a database as the following:

Collected data 3 (days) * 2.5 KB = 7.5 KB

5-minute summary data 7 (days) * 3.5 KB = 24.5 KB




Total size (7.5 + 24.5 + 210 + 315 + 365) (KB) * 1 (machines) * 1


By default, each SigmaSystemCenter Managed Object can collect up to 17 performance information. So that you can estimate the size of a database per SigmaSystemCenter Managed Object as the following:

0.9 (MB) * 17 = approximately 15 MB

9 Troubleshooting


9.9.2. Errors and Actions for when There is not Enough Disk

Space

SQL Server

The event logs for when there is not enough disk space and the actions to take are listed below.




13 Failed to update the database. Details: Could not allocate space for object 'RM_PerformanceData' in database 'RM_PerformanceDataBase2' because the 'PRIMARY' filegroup is full.



29 Stopped Performance Monitoring Service because an irrecoverable error was detected. Details: Could not allocate space for object 'RM_PerformanceData' in database 'RM_PerformanceDataBase2' because the 'PRIMARY' filegroup is full.

Action

There is not enough disk space. Increase the amount of free space on the disk by deleting redundant files and so on. The amount of disk space can then be reduced by taking the following measures:

• Setting a shorter storage period for performance data • Increasing the data collecting interval

• Reducing the number of Performance Indicator items that are collected • Reducing the number of managed objects that are monitored




13 Failed to update the database. Details: Could not allocate new page for database 'RM_PerformanceDataBase2'. There are no more pages available in filegroup PRIMARY. Space can be created by dropping objects, adding additional files, or allowing file growth.



29 Stopped Performance Monitoring Service because an irrecoverable error was detected. Details: Could not allocate new page for database 'RM_PerformanceDataBase2'. There are no more pages available in filegroup PRIMARY. Space can be created by dropping objects, adding additional files, or allowing file growth.

Action

Database

247

The database size has reached 10 GB. System Monitor - Performance Monitoring Services uses SQL Server 2016 SP1 Express as its database engine. The maximum size supported by SQL Server 2016 SP1 Express is 10 GB. Upgrade to a higher edition of SQL Server 2016 SP1 Express, or delete data from the database by reducing the storage period for the performance data with the Data Management Tool. The procedure is shown below. 1. Close the management console. 2. Start the System Monitor Data Management Tool.

3. Reduce the storage periods for the collected and summary data and then perform data summarization.

After the data has been deleted, restore the performance data collecting interval to the original value. The amount of disk space can then be reduced by taking the following measures:

• Setting a shorter storage period for performance data

• Increasing the data collecting interval • Reducing the number of Performance Indicator items that are collected • Reducing the number of managed objects that are monitored




67

The Database size has grown into CurrentSizeGB, larger than the warning size WarningSizeGB

Action

The database size has exceeded the specified warning value. Either change the warning value or delete data from the database by reducing the storage period for the performance data with the Data Management Tool. The procedure is shown below.

1. Close the management console. 2. Start the System Monitor Data Management Tool. 3. Reduce the storage periods for the collected and summary data and then perform data

summarization. After the data has been deleted, restore the performance data collecting interval to the original value.

The amount of disk space can then be reduced by taking the following measures:

• Setting a shorter storage period for performance data • Increasing the data collecting interval

• Reducing the number of Performance Indicator items that are collected • Reducing the number of managed objects that are monitored

9 Troubleshooting


PostgreSQL The event logs for when there is not enough disk space and the actions to take are listed below.




13 Failed to update the database. Details: 53100: could not extend file "******": No space left on device

Action

The available space of the disk or partition is insufficient. To fix this shortage, delete unnecessary files, and then delete data in the database by reducing the storage period of performance data by using the data management tool. The procedure of deleting data in the database is the following: 1. Exit the management console.

2. Start the data management tool. 3. Reduce the storage period of collected data and summary data, and then recalculate the

summary data. Then configure the following to reduce the required disk space:

• Reduce the storage period of performance data. • Increase the number of the data collecting interval. • Reduce the number of the collecting performance indicators.

• Reduce the number of the managed targets.




67 The Database size has grown into CurrentSizeGB, larger than the warning size WarningSizeGB

Action

The database size exceeded the specified threshold number (the threshold number is to regulate the size of disks or partitions. PostgreSQL does not have a database size limitation in its specification). Check the available space of the disk or partition. If there is enough space, increase the threshold number.

If there is not enough space, delete data in the database by reducing the storage period of performance data by using the data management tool. The procedure of deleting data in the database is the following:

1. Exit the management console. 2. Start the data management tool. 3. Reduce the storage period of collected data and summary data, and then recalculate the

summary data. Then configure the following to reduce the required disk space:

• Reduce the storage period of performance data. • Increase the number of the data collecting interval.

• Reduce the number of the collecting performance indicators. • Reduce the number of the managed targets.

Database

249

9.9.3. Errors and Actions for Database Faults

SQL Server The event logs relating to database references and updates, and the actions to take are listed below.




13 Failed to update the database. Details: General network error. Check your network documentation.

or



15 Failed to reference the database. Details: General network error. Check your network documentation.



29 Stopped Performance Monitoring Service because an irrecoverable error was detected. Details: General network error. Check your network documentation.

Action

• Start the database service "MSSQL$SSCCMDB" if it has not started already. The database service starts automatically when the Performance Monitoring Service starts. The procedure for starting the service manually is as follows. When the instance name is changed from the default value, select "MSSQL$InstanceName" service name.

1. Start Services from the Administrative Tools control panel. 2. Select the service with the name "MSSQL$SSCCMDB" from the list of services that is

displayed, and double-click to open it.

3. Click Start in the General tab. 4. The database service will then start.

• Check whether there is a problem with the network connected to the management server. Check these points and resolve any problems, and then restart the Performance Monitoring Service. An error message may be output and the management console may terminate when the management console is started.

If so, start the management console again.

9 Troubleshooting


PostgreSQL

The event logs relating to database references and updates, and the actions to take are listed below.




13 Failed to update the database. Details *************************************

or



15 Failed to reference the database. Details: *************************************



29 Stopped Performance Monitoring Service because an irrecoverable error was detected. Details: *************************************

Action

• Check whether the PostgreSQL service is started (the service display name is started with "postgresql" and in the default, the service is automatically started along with the service of System Monitor - Performance Monitoring Services). If it is not started, start the service manually as the following:

1. Open Control Panel, click Administrative Tools, and then double-click Services. 2. In the list, double-click the PostgreSQL service that the service display name is

started with "postgresql." 3. Click Start in the General tab. 4. The service is started.

• Check whether there is a network issue between the server of System Monitor - Performance Monitoring Services and the server of PostgreSQL. After the issue is fixed, restart the System Monitor - Performance Monitoring Services.

When the management console is started, the console may abnormal end with an error message. In this case, restart the management console.

9.9.4. Procedure for Backing up and Restoring the Database

SQL Server

Backing up and restoring database is executed using sqlcmd command offered in SQL Server. • To back up

1. Close the management console by selecting Exit from the File menu of the management console main window.

2. Stop the Performance Monitoring Service.

Database

251

• Start Services from the Administrative Tools control panel. • From the list of services that is displayed, double-click the "System

Monitor Performance Monitoring Service".

• Stop the Performance Monitor Service by clicking Stop in the General tab.

3. Copy the following files to the backup destination: In the installation directory for System Monitor - Performance Monitoring Services (Default value：%ProgramFiles%\NEC\SystemMonitorPerformance)

• bin\rm_client.xml • bin\rm_service_init.xml • bin\rm_database.xml

• bin\rm_sshencode.xml • Script

4. Execute the database backup command. • Select All Programs from the Start menu, and then select

Accessories and then Command Prompt. • Specify the following command at the command line. In the example

shown here, a backup file called "sysmonbk.dat" is created in the \temp directory on the C drive. > sqlcmd -E -S (local)\SSCCMDB -Q "backup database RM_PerformanceDatabase2 to disk = 'c:\temp\sysmonbk.dat' with init"

Note: When the instance name is changed from the default value, specify "(local)\InstanceName".

• To restore

1. Close the management console by selecting Exit from the File menu of the management console main window.

2. Stop the Performance Monitoring Service. • Start Services from the Administrative Tools control panel. • From the list of services that is displayed, double-click the "System

Monitor Performance Monitoring Service" service.

• Stop the Performance Monitor Service by clicking Stop in the General tab.

3. Restore the following files from the backup directory: In the installation directory for System Monitor - Performance Monitoring Services

(Default value：%ProgramFiles%\NEC\SystemMonitorPerformance) • bin\rm_client.xml • bin\rm_service_init.xml

• bin\rm_database.xml

9 Troubleshooting



4. Execute the database restore command. • Select All Programs from the Start menu, and then select

Accessories and then Command Prompt. • Specify the following command at the command line. In the example

shown here, a backup file called "sysmonbk.dat" in the \temp directory on the C drive is restored. > sqlcmd -E -S (local)\SSCCMDB -Q "restore database RM_PerformanceDatabase2 from disk =

'c:\temp\sysmonbk.dat' with replace"

Note: When the instance name is changed from the default value, specify "(local)\InstanceName".

PostgreSQL • To back up

You can back up a database by using the pg_dump.exe of PostgreSQL.

1. In the management console main window, click File from the menu, and then click Exit.

2. Stop the System Monitor - Performance Monitoring Services. • Open Control Panel, click Administrative Tools, and then

double-click Services. • In the list, double-click the service that the service display name is

"System Monitor Performance Monitoring Service."

• Click Stop in the General tab.

3. Copy the following files to the backup destination. In the System Monitor - Performance Monitoring Services installation directory (the default: %ProgramFiles%\NEC\SystemMonitorPerformance):

• bin\rm_client.xml • bin\rm_service_init.xml • bin\rm_database.xml


4. Run the backup command of the database. • Click Start, click All Programs, click Accessories, and then click

Command Prompt. • Run the following command in the command prompt. This example

creates a backup file, sysmonbk.sql, in the temp folder of the C drive. > pg_dump.exe -h localhost -p 5432 -U postgres -F p -f C:\temp\sysmonbk.sql RM_PerformanceDataBase2

• To restore

Database

253

You can restore a database by using the psql.exe of PostgreSQL.

1. In the management console main window, click File from the menu, and then click Exit.

2. Stop the System Monitor - Performance Monitoring Services. • Open Control Panel, click Administrative Tools, and then

double-click Services. • In the list, double-click the service that the service display name is

"System Monitor Performance Monitoring Service."

• Click Stop in the General tab.

3. Overwrite the backed up files. In the System Monitor - Performance Monitoring Services installation directory (the default: %ProgramFiles%\NEC\SystemMonitorPerformance): • bin\rm_client.xml • bin\rm_service_init.xml

• bin\rm_database.xml • bin\rm_sshencode.xml • Script

4. Run the restore command of the database. • Click Start, click All Programs, click Accessories, and then click

Command Prompt. • Run the following command in the command prompt. This example

restores a backup file, sysmonbk.sql, from the temp folder of the C drive.

• If RM_PerformanceDataBase2 is exist in the PostgreSQL, first, delete it by using the following command: > dropdb.exe -h localhost -p 5432 -U postgres "RM_PerformanceDataBase2"

• Next, create RM_PerformanceDataBase2 in the PostgreSQL: > createdb.exe -h localhost -p 5432 -U postgres "RM_PerformanceDataBase2"

• And then restore sysmonbk.sql: > psql.exe -h localhost -p 5432 -U postgres -d RM_PerformanceDataBase2 -f C:\temp\sysmonbk.sql

Reference: You can also back up or restore PostgreSQL by using another method. For the details, refer to the following: https://www.postgresql.org/docs/9.5/static/backup.html

https://www.postgresql.org/docs/9.5/static/backup.html

9 Troubleshooting


9.10. Other 1. Perflib-related events recorded in the application log

Resolve the problem with the performance counter by contacting the developer of the application that owns the performance counter (recorded as "***.dll" in the log) for which the problem occurred.

See Microsoft support technical information for details on performance library errors.

2. Warning errors for MSSQL$SSCCMDB:ID19011 recorded in the application log

The following event may be displayed in the event viewer when the management server starts:

◆ Type: Warning

◆ Source: MSSQL$SSCCMDB ◆ Event ID: 19011 This warning message results from the specification for SQL Server, and does not indicate a problem with the execution of System Monitor - Performance Monitoring Services. See Microsoft support technical information (ID: 303411) for details. When the instance name is changed from the default value (SSCCMDB), "MSSQL$InstanceName" is displayed.

3. Situations where logs are not recorded in the event log In default setting for System Monitor - Performance Monitoring Services, previous logs are overwritten when maximum log size (16MB) is reached. If the settings for the event viewer is changed to system default, new logs may not be recorded when maximum log size is reached.

In this case, change the settings for the event viewer as follows:

(1) Start the Event Viewer from the Administrative Tools control panel. (2) Right-click System Monitor - Performance Monitoring Services and select

Properties. The System Monitor - Performance Monitoring Services Properties window appears.

(3) In the General tab, change the Log size items. 4. Time difference between the management server and the console machine

When the management server is different from the management console machine, a time difference may arise between the machines. System Monitor - Performance Monitoring Services adjusts the time difference between the machines for graph display. If the time difference is greater than one hour, a warning message is displayed.

255

10. Notes This chapter explains various notes and issues. This chapter contains the following sections: • 10.1 The Estimated Number of Monitored Objects .........................................................256 • 10.2 Notes on Database ..................................................................................................257 • 10.3 Notes on Graph Displays .........................................................................................258 • 10.4 Notes on Linking to SystemProvisioning .................................................................259 • 10.5 Release of Resources .............................................................................................264 • 10.6 Notes on Upgrading/Updating .................................................................................265 • 10.7 Issues When Other Products to Monitor the Windows Managed Machine Coexist

with System Monitor - Performance Monitoring Services .........................................................268 • 10.8 A Character Encoding for Collecting Data via SSH .................................................269

10 Notes


10.1. The Estimated Number of Monitored Objects

The maximum number of physical machines that can be specified as managed objects with the single System Monitor - Performance Monitoring Services is 300 units. The actual maximum number of units can be controlled by the quantity of collected performance data and collection intervals. When large-scale system configurations are handled with SystemProvisioning and the quantity of collected performance data is large and the collection intervals are short, it is recommended that the configuration is divided by group units and monitored using more than one System Monitor - Performance Monitoring Services or that the collection interval is extended.

The recommended maximum number of managed objects per management server is the following:

Approximately 300 for physical machines. Approximately 500 for virtual machines if the collection interval of performance

data is five minutes.

Approximately 100 for resource pools, approximately 500 for sub resource pools if the collection interval of performance data is 30 minute.

Approximately 500 for LUNs on NEC Storage if the collection interval of performance data is five minutes.

Approximately 500 SigmaSystemCenter Managed Objects when collecting performance data interval is 1 hour.

If you monitor managed objects more than these maximum numbers, expand the collection interval of performance data or increase the number of System Monitor - Performance Monitoring Services for monitoring to avoid the load peaks of management servers or networks.

For estimated time for the collection interval of performance data or configurations of System Monitor - Performance Monitoring Services, refer to 2.7, "Performance Monitoring" in NEC SigmaSystemCenter Reference Guide.

Notes on Database

257

10.2. Notes on Database Size of data

For the details about the database size of System Monitor - Performance Monitoring Services, see 9.9.1, "Estimating the Disk Space Required for Saving Performance Data."

In SQL Server 2016 SP1 Express, used by System Monitor - Performance Monitoring Services as the database engine, the maximum database size is 10 GB. Although a database file of 10 GB or more can be handled if SQL Server 2016 SP1 Express is upgraded to SQL Server 2016 SP1, the system must be designed so that the size of the performance data is less than or equal to 10 GB whenever SQL Server Express is being used. Determine the number of managed machines, resource pools, LUNs of NEC Storage, or SigmaSystemCenter Managed Objects to be monitored by a performance monitoring service based on the number of performance data items to be collected, the collection interval, and the data storage period.

Configuration of database The database is created when installing the System Monitor - Performance Monitoring Services, and also, the SQL server created on another server in the network can be used. Accessing to the database is executed frequently in the System Monitor - Performance Monitoring Services. So, if the database is transferred to the different server from the management server, any action may be affected due to not acquiring performance. Therefore, the transition of the data is not recommended. Using it on the same management server is recommended. In addition, for the transition of the database, see "Appendix B Transferring the Database".

10 Notes


10.3. Notes on Graph Displays The period for historical displays

If the period for historical displays is too long for the plot interval, it may take some time for the graph to be displayed in the management console. Reduce the display period, or increase the plot interval.

Discontinued graph line System Monitor - Performance Monitoring Services Management Console displays a graph as a "line" when there is a plot data in the previous or next plot interval. When there is no plot data in both the previous and next plot intervals, this plot data is displayed as only a "dot". The line of a displayed graph may be discontinued when the data required to draw the graph is not partly present because the service is restarted or a temporary access error occurs in a machine being monitored, or because the data collection interval exceeds the specified plot interval.

Graph display accuracy If graph lines are made finer, the graph drawing precision may drop, and lines may become broken. If this happens, make the lines thicker by modifying width in the Color and line tab of the Graph display setting window.

Data for graph display System Monitor - Performance Monitoring Services determines the data used for graph display according to the plot interval. If there is no data corresponding to the specified plot interval, the graph line for the period containing no data is not displayed. See "1.4.2 Usage of Summary Data" for more details.

Notes on Linking to SystemProvisioning

259

10.4. Notes on Linking to SystemProvisioning The following three sections provide notes on using managed objects managed by SystemProvisioning as monitored machines for System Monitor - Performance Monitoring Services. Applying changes in the system configuration information of SystemProvisioning to

System Monitor - Performance Monitoring Services The SystemProvisioning configuration information can be manually or automatically applied to System Monitor - Performance Monitoring Services. When this is automatic, System Monitor - Performance Monitoring Services is transmitted to SystemProvisioning at fixed intervals and the changed configuration information is automatically applied. Verify the following when enabling the application.

• Verify the following if the application of system configuration information is failed. If the connection to SystemProvisioning is correct and communication

fails between System Monitor - Performance Monitoring Services and SystemProvisioning, confirm that the name of the SystemProvisioning management server is correctly configured in the SystemProvisioning tab of the Configuration window from the management console of System Monitor - Performance Monitoring Services. When SystemProvisioning is clustered with EXPRESSCLUSTER, the virtual computer name cannot be used as SystemProvisioning Management Server name. Using the virtual computer name can cause a failure to connect SystemProvisioning.

In addition, if the Windows firewall function of the SystemProvisioning management server is valid; configure the Windows firewall to accept exceptions by referring to Section, "2.6 SystemProvisioning Connection Settings". When the automatic applying function is configured, consecutive errors generated after the second time are not recorded to the event log or displayed as a message on the GUI.

If the PVM Service has started. Start the PVM Service on the SystemProvisioning management server. If the PVM service has been restarted during operations, restart the service of System Monitor - Performance Monitoring Services (System Monitor Performance Monitoring Service) as well.

Whether the service execution account is proper.

If the Performance Monitoring Service is not running on the SystemProvisioning management server, the execution account of Performance Monitoring Service must have OS administrator authority for the SystemProvisioning management server. If a proper account has not been set, change the service execution account. See "2.5.2 How to Change the Performance Monitoring Service Execution Account" for information on how to change the service execution account. Apply the configuration information when the machine status returns to normal.

• Confirm the following point if the performance collecting status of a target machine is changed to a paused status from a normal status automatically.

10 Notes


Whether the target machine Power Status in SystemProvisioning is "Off" or "Suspend", OS Status is "Off" or Executing Status is "Executing".

• The automatic configuration applying function checks the configuration status at regular intervals, so SystemProvisioning configuration changes may not be applied immediately. Apply the configuration manually or adjust the polling interval for automatic configuration applying.

• If a managed machine is running Linux, VMware ESXi, Citrix XenServer or KVM, System Monitor - Performance Monitoring Services uses an IP address to connect to the managed machine. If the IP address of a managed machine is not specified using the System Monitor - Performance Monitoring Services management console then the machine name must be registered with either DNS or the "hosts" file on the System Monitor - Performance Monitoring Services management server. The IP address settings for System Monitor - Performance Monitoring Services managed machines can be acquired when SystemProvisioning configuration information is applied. If a machine is added using SystemProvisioning, IP address information can also be acquired as additional machine information at the same time, which means that operations can be automated. However, for some system configurations, there are cases where it is not possible to connect to monitored machines using the IP addresses acquired, and so if a managed machine produces an error, either set the IP address using the Machine Settings window of the System Monitor - Performance Monitoring Services management console or register the IP address with DNS or the "hosts" file. If an IP address has been set up by using the Machine Settings window or as a result of applying SystemProvisioning configuration information, the information registered in DNS or the "hosts" file will not be looked up. Then IP address has to be resolved as an IPv4 address.

• When the performance data collecting is enabled on the Performance Monitor settings for the group/model on SystemProvisioning and then the application of SystemProvisioning configuration information is performed on System Monitor - Performance Monitoring Service, the corresponding groups and machines are register automatically on System Monitor - Performance Monitoring Service. When the performance data collecting is disabled or "Do not Monitor" is selected as Profile Name on the Performance Monitor settings for the group/model on SystemProvisioning and then the application of SystemProvisioning configuration information is performed on System Monitor - Performance Monitoring Service, collecting performance data for the corresponding groups and machines is paused on System Monitor - Performance Monitoring Service. These group settings and machine settings are not deleted automatically from System Monitor - Performance Monitoring Service. If necessary, delete manually via the System Monitor Management Console.

Configuration change of SystemProvisioning triggered by threshold monitoring Load status abnormalities with monitored machines that are detected by threshold monitoring of System Monitor - Performance Monitoring Services can be notified to SystemProvisioning. SystemProvisioning receives these notifications and executes recovery process (such as adding machines) according to its policies. Note the following points when configuring the notifications.


261

• Conflicts with other products make notifications to SystemProvisioning. Notifications to SystemProvisioning are made from multiple monitoring products. Care must be taken so that these notifications do not duplicate System Monitor - Performance Monitoring Services notifications.

Standard notifications (notifications from Server Management Manager) Of all the events that can be used as SystemProvisioning standard notification events, do not set up policies for events relating to performance status (such as "CPU load failure") and policies for System Monitor - Performance Monitoring Services's threshold monitoring notification for the same machine or group. If both types of policies are set up, the recovery process specified in each policy may be executed for the same machine at the same time.

If actions such as "Reboot machine" are set up for System Monitor - Performance Monitoring Services's performance load abnormalities using SystemProvisioning policies, Server Management Manager may raise a "Machine down" event while the machine is restarting. If a SystemProvisioning policy has been set up for the "Machine down" event, a recovery process may be executed depending on the timing. Check the SystemProvisioning log and restore the machine to an appropriate state.

Custom notifications (notifications from optional products) Monitoring products other than Server Management Manager make notifications to SystemProvisioning using notification categories. Users can set up recovery processes for notification categories freely. For these monitoring products, set up notification categories for the events that will trigger these recovery processes. The same notification category can be assigned to more than one monitoring product, but the roles for the notification categories should first be defined and then set up so that they do not conflict when they are used. As with the standard notifications setting, be careful when setting up policies so that recovery processes actions are not duplicated.

• Execution and timing of the configuration change action sequence

System Monitor - Performance Monitoring Services can be configured to detect abnormalities using the frequency of threshold overruns with multiple checkpoints, to ensure that temporary load status is not notified when notifying abnormalities of performance loads. Similarly, if over-threshold status continues for an extended period of time, the timing for repeat notifications can also be set up. Thresholds can be set in terms of upper-limits and lower-limits, for "warning" or "critical". Use these settings functions to design policies so that conflicts do not occur when configuration changes are made. For example, appropriate settings are needed in the following kind of situation. Settings were made for a group to add a machine when the threshold

exceeds an upper-limit and to delete a machine when the threshold exceeds a lower-limit, but machines were added and deleted repeatedly. Review the settings for the upper- and lower-limit threshold values.

Settings were made for a group to add a machine when the threshold exceeds an upper-limit, but machines were added twice.

10 Notes


The performance load status had not recovered or high load may have been detected again before the first machine addition completed. For the second case, review the timing for repeat notifications.

If a certain group has been configured to move the VM when the threshold exceeds an upper-limit, the VM was moved repeatedly. Check the status of the destination VM server. Review the settings for the upper-limit threshold value and, if necessary, review the operating method (consider moving the VM manually, for example). SystemProvisioning discards notifications about machines for which actions are being executed. Logs are written for both discarded events and received events, so check the logs.

With SystemProvisioning, different actions for notifications can be set up for each group/model. As a result, different actions for the same customized notification category can be set up for different groups/models. Take care to avoid conflicts when setting up actions for notifications.

The policy specified in the model settings will be given priority when SystemProvisioning received a notification about the group which is set the full path to the model as a SystemProvisioning path.

The policy specified in the model settings will be given priority when SystemProvisioning received a notification about the machine. The policy specified in the group settings will be enabled when no policy is set in model settings. No recovery action will be executed when no policy is set in both group and model.

The SystemProvisioning path to be set in the group of System Monitor - Performance Monitoring Services must be a full path to the model to enable the VM Optimization Function.

Possible impacts made to performance status when SystemProvisioning configurations are changed The performance status of the machines and groups being managed by System Monitor - Performance Monitoring Services may be affected when any changes to the system configuration are made, including automatic changes executed by SystemProvisioning. The following situations may arise.

• When a machine fault occurs, performance data for the machine cannot be acquired. The performance status of the group of the failed machine changes. And unexpected load may appear on that group.

• When the machine is in maintenance, performance data for the machine cannot be acquired correctly, and the performance data for the group that includes the machine will not be valid.

With SystemProvisioning, configurations can change automatically, so if an unexpected load appears in the performance status, check the log information for SystemProvisioning.

Also, if threshold monitoring notification has been set up for the group that includes the machine, a recovery process (such as adding a machine to the group) may be executed by SystemProvisioning as a result of a notification for the abnormal load status that occurred temporarily. In order to prevent unwanted recovery processes from being executed, cancel settings for actions triggered by threshold monitoring


263

notification in situations where load can be anticipated in advance, such as when maintenance is performed. In the case of an unexpected situation, such as faults, configure the threshold with an allowance to ensure that an action is not generated at the same time, and specify a single action for the same machine or group. If an unnecessary recovery process has been generated, confirm the log information and return to the appropriate state.

10 Notes


10.5. Release of Resources System Monitor - Performance Monitoring Services releases resources such as the libraries used to obtain performance data, at AM 3:00 every day. The release of such resources is normally completed after several minutes. Note that the collection of performance data and the monitoring of the threshold are stopped during the release.

Notes on Upgrading/Updating

265

10.6. Notes on Upgrading/Updating 10.6.1. Changing the Setting of SystemProvisioning

Configuration Path

The path of SystemProvisioning configuration information must be a full path to the group/model. If a path to a SystemProvisioning category, which is inherited from an earlier version, is specified in the group settings of System Monitor - Performance Monitoring Services, change the setting to indicate the path to the group/model.

10.6.2. Additional Setting for Managing Linux Machine with

Multipath Configuration

An additional setting is necessary if a managed Linux machines has a multipath configuration using NEC Storage StoragePathSavior. Change the setting using the following procedure if the update module for SigmaSystemCenter 2.1 (SSC0201-0006-update2 or SSC0201-0015-update3) was applied to your system in past. 1. Stop the Management Console. 2. Stop the System Monitor Performance Monitoring Service.

3. Open the configuration file (\bin\rm_service_init.xml) on the installation directory with text editor after backing up it. (Default installation directory: %ProgramFiles%\NEC\SystemMonitorPerformance)

4. Change the setting of the LinuxDiskDeviceNameRegex tag as shown below: <LinuxDiskDeviceNameRegex>(?:hd|sd|xvd|dd)[a-z]+</LinuxDiskDeviceNameRegex>

5. Over write the configuration file and start the System Monitor Performance Monitoring Service.

10.6.3. Changing the Performance Indicator Title

If a title of the built-in performance indicator had been modified from the default title in SigmaSystemCenter 2.1 or earlier, the title will be changed automatically to the default title during upgrading procedure. Reconfigure the graph settings of the management console with a default performance indicator title.

10.6.4. Changing the Error Code Format for User Scripts

The format "@errorcode number," which is used in SigmaSystemCenter 3.2 or earlier, is deprecated in SigmaSystemCenter 3.3. SigmaSystemCenter 3.3 allows for you to use only the format "errorcode=number" as an error code format. If the format "@errorcode number" is used in a script to return an error code, change the format to "errorcode=number."

10 Notes


10.6.5. Additional Setting for Collecting Disk Speed Performance

Data of Linux Virtual Machines in KVM

In SigmaSystemCenter 3.4 or before, the following performance information cannot collect from Linux virtual machines in KVM.

Disk Transfer Rate (Bytes/sec) Disk IO Count (IO/sec)

Disk Read Transfer Rate (Bytes/sec) Disk Read Count (IO/sec) Disk Write Transfer Rate (Bytes/sec)

Disk Write Count (IO/sec) In this reason, if you upgrade SigmaSystemCenter from 3.4 or before, you must edit a service configuration file to collect the above information. Follow the procedure: 1. Stop the management console. 2. Stop System Monitor Performance Monitoring Service.

3. In the installed directory of SigmaSystemCenter, first, backup the service configuration file (\bin\rm_service_init.xml), and then open the file with a text editor.

4. Add "|vd" to the LinuxDiskDeviceNameRegex tag. Example: <LinuxDiskDeviceNameRegex>(?:hd|sd|xvd|dd|vd)[a-z]+</LinuxDiskDeviceNameRegex>

5. Save and close the file, and then start System Monitor Performance Monitoring Service.

10.6.6. When Changing for Collecting Performance Data by

Using Remote User Scripts

We have changed the way of collecting performance data by the remote user script in the certain windows environment because the library is used for the SSH connection of SigmaSystemCenter 3.5 has been updated.

In this reason, if you upgrade SigmaSystemCenter from 3.4 or before, you must change the following in the configuration of cygwin environment or the syntax of remote user scripts.

In the installed directory of cygwin, use "/bin/bash" (default) as the logon shell for

the connecting account in "/etc/passwd."

Notes on Upgrading/Updating

267

Syntax has changed when using a batch file that uses collecting performance data. You must add "cmd /c" before the path of the batch file. <Example>

Before: remote+ssh://C:\PerformanceMonitor\Script\test.bat After: remote+ssh://cmd /c “C:\PerformanceMonitor\Script\test.bat

Syntax has changed when using a powershell file that uses collecting performance data. You must change "< NUL" to "< /dev/null." <Example>

Before: remote+ssh://PowerShell.exe -File "C:\PerformanceMonitor\Script\test.ps1" < NUL After: remote+ssh://PowerShell.exe -File "C:\PerformanceMonitor\Script\test.ps1" < /dev/null

10.6.7. When Changing a Group Name

From SigmaSystemCenter 3.5, you cannot use a slash "/" for the group name of System Monitor - Performance Monitoring Services. In this reason, if you use slashes to the group names, they are converted to hyphens "-" at the timing of upgrading SigmaSystemCenter. If the converted name is already exist in the same group, a number-for example "(1)"-is added after the name. This conversion is applied only for the group names that are manually added from System Monitor Management Console.

10 Notes


10.7. Issues When Other Products to Monitor the Windows Managed Machine Coexist with System Monitor - Performance Monitoring Services

Adding to System Monitor - Performance Monitoring Services, if other performance monitoring products monitor Windows managed machines, the "Category does not exist" error might occur while collecting the performance data. System Monitor - Performance Monitoring Services uses the Windows performance monitor feature to obtain the performance data from the Windows managed machine. This issue occurs other monitoring products also use the Windows performance monitor feature as well as System Monitor - Performance Monitoring Services.

Use either System Monitor - Performance Monitoring Services or the other product to monitor the Windows managed machine.

A Character Encoding for Collecting Data via SSH

269

10.8. A Character Encoding for Collecting Data via SSH

System Monitor - Performance Monitoring Services converts character encodings for delivering the following between System Monitor - Performance Monitoring Services and SSH servers on managed objects. This conversion occurs when collecting performance data by using System Monitor - Performance Monitoring Services via SSH, such as when collecting the data from Linux managed machines or from windows managed machines by performing scripts. When executing scripts, which are sent from System Monitor - Performance

Monitoring Services, in a managed object (convert the character encoding of System Monitor - Performance Monitoring Services into the character encoding of the managed object).

The results from above scripts, which receive from managed objects (convert the character encoding of the managed object into the character encoding of System Monitor - Performance Monitoring Services).

System Monitor - Performance Monitoring Services operates by using the following character encoding sets by default.

System Monitor - Performance Monitoring Services: UTF-8 (fixed)

Managed objects: UTF-8 (default)

Note that managed objects use a specified character encoding in the service configuration file (<System Monitor - Performance Monitoring Services installed directory>\bin\rm_sshencode.xml). If you need to change this encoding, procedures are the following: <Example> If you add Shift-JIS to a machine (name: Machine) in a group (name: Group).

1. Stop the System Monitor Management Console. 2. Stop System Monitor Performance Monitoring Service. 3. In the installed directory of System Monitor - Performance Monitoring Services,

first, backup the service configuration file (\bin\rm_sshencode.xml), and then open the file with a text editor. Ref: The default install directory:

%ProgramFiles(x86)%\NEC\SystemMonitorPerformance

4. Add the following to the SshEncodes tag. Example:

<SshEncode> <node>Root\Group\Machine</node> <linux>shift_jis</linux>

</SshEncode> Note that configurable character encodings are .NET Framework supported character encodings. For details, refer to

10 Notes


"https://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx." This file also only supports the name of a character encoding, and does not support Code Page.

5. Save and close the file, and then start System Monitor Performance Monitoring Service.

https://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx

https://msdn.microsoft.com/en-us/library/system.text.encoding(v=vs.110).aspx

271

Appendixes • Appendix A How performance values for groups are calculated ····································· 273 • Appendix B Transferring the Database (For SQL Server) ············································· 275 • Appendix C Transferring the Database (For PostgreSQL) ············································ 289 • Appendix D Performance Counter Information of VMware ESXi ···································· 293 • Appendix E License Information ············································································· 295

273

Appendix A How performance values for groups are calculated

Usage rates (group performance) for a group made up of managed objects can be calculated as either the absolute performance values of each managed object or as the weighted average of the usage rate for each managed object, using performance ratios as coefficients. The following model formula is generally suitable for calculating group usage rates.

For CPU usage rates, the group usage rate can generally be calculated by using the published benchmark value for αi. Graphs that show the performance status of a group while taking into account the ability of the machines that make up the group can be displayed by setting this αi value in the Weight field in the Machine Settings window for the System Monitor - Performance Monitoring Services management console and selecting Weighted average value as the statistic in the Graph display object settings window. However, care is required if SMP or Hyper-Threading and so forth is being applied, as the trends are different to the benchmark values. (Performance improves by 50 to 100% for SMP and by 0 to 60% for Hyper-Threading (30% on average).) Further errors arise depending on the applications executing on the monitored machines. Pre-evaluations are needed in order to measure usage rates accurately. For disk usage rates, the trends are different to the benchmark values, and so αi must be derived accurately using pre-evaluations. However, if disks are generally under medium to heavy load, the performance of each disk can be regarded as almost the same (αi is constant), and the measurement error is about ±15% even the simple average of the usage rate for each machine is taken as the usage rate of the group. Disk usage rates can be specified using the Windows custom definitions of the Performance Indicator settings.

The views expressed here regarding the model formula and CPU and disk usage rates have been derived from test results using IIS/ASP. For actual operations, it is recommended that you set values based on pre-evaluations taking into account such factors as the characteristics of the applications being used.

ρ: Group usage rate

ρi: Machine usage rate αi: Performance value relative to other machines (performance ratio) ∑

∑=i i

ii i α

αρρ

275

Appendix B Transferring the Database (For SQL Server)

When an SQL Server is used for a database, the SQL Server is installed along with System Monitor - Performance Monitoring Services. Although this is the default, you can also transfer the SQL Server to the different server from the System Monitor - Performance Monitoring Services by configuring the server in the same network of the System Monitor - Performance Monitoring Services. We explain how to transfer for each authentication mode (Windows authentication and SQL Authentication) by using an example. In the example, the destination server name is "SERVER1" and the SQL Server 2016 Express instance (created in "SERVER1") name is "SSCCMDB."

Keep in mind that since System Monitor - Performance Monitoring Services accesses the database frequently and this configuration may not provide enough performance for the access, we do not recommend this transfer.

Note: You cannot transfer the database from PostgreSQL to SQL Server.

Using Windows Authentication Login Perform the following procedures to transfer the System Monitor - Performance Monitoring Services database when using the Windows authentication login.

Note: Windows Authentication Login is valid only if SERVER1 joins the domain. If SERVER1 joins the workgroup, use SQL Authentication Login.

1. Backing up System Monitor - Performance Monitoring Services Back up System Monitor - Performance Monitoring Services. For the procedure, see Subsection 9.9.4, "Procedure for Backing up and Restoring the Database."

Note: Set the name of the backup files as "sysmonbk.dat".

2. Creating Instance Setup the SQL Server 2016 SP1 Express on SERVER1.

1. Download the setup program of SQL Server 2016 SP1 Express from the following site.

https://www.microsoft.com/en-us/download/details.aspx?id=54284




2. Run the downloaded SQLEXPR_x64_ENU.exe and proceed with the setup according to the instructions on the screen.

3. The Instance Configuration dialog box appears. Select Named instance and type SSCCMDB into the text box.

4. The Server Configuration dialog box appears. Select NT Service\MSSQL$SSCCMDB for the account name of SQL Server Database Engine service.

5. The Database Engine Configuration dialog box appears. Select Windows authentication mode.

277

6. To specify the SQL Server administrator, Click Add….

7. The Select Users or Groups dialog box appears. Type SYSTEM in Enter the object names to select (examples): and then click OK.



8. The Database Engine Configuration dialog box appears. Click Next.

After this, follow the instructions that appear on the screen to complete the setup.

3. Enabling the network connection As SQL Server 2016 SP1 Express permits only the local client connection by default, you need to enable the network connection.

In addition, SQL Server Browser must be started and Firewall exceptions must be created.

• In SQL Server Configuration Manager, enable TCP/IP and Named pipes, and then restart the SQL Server (SSCCMDB) service.

• In SQL Server Configuration Manager, change the start mode of SQL Server Browser to Automatic, and then start SQL Server Browser.

• In Windows Firewall with Advanced Security, add the following inbound rules:

• TCP 1433 • UDP 1434 • In the SQL Server installation folder:

\MSSQL13.SSCCMDB\MSSQL\Binn\Sqlservr.exe The default path when you installed SQL Server 2016 SP1 Express with the default settings is one of the following:

C:\Program Files\Microsoft SQL Server\MSSQL13.SSCCMDB\MSSQL\Binn\Sqlservr.exe or

279

C:\Program Files (x86)\Microsoft SQL Server\MSSQL13.SSCCMDB\MSSQL\Binn\Sqlservr.exe

Reference: Go to the following sites for more details: ▪ http://msdn.microsoft.com/en-us/library/ms191294(v=sql.130).aspx ▪ http://msdn.microsoft.com/en-us/library/hh403394(v=sql.130).aspx ▪ http://msdn.microsoft.com/en-us/library/ms175043(v=sql.130).aspx

4. Creating a database Run the following command from a command prompt window on SERVER1.

Always use RM_PerformanceDataBase2 as the database name used as the System Monitor - Performance Services database.

E.g.1) > sqlcmd –E –S (local)\SSCCMDB –Q "create database RM_PerformanceDataBase2"

E.g.2) > sqlcmd –E –S (local)\SSCCMDB 1> create database RM_PerformanceDataBase2 2> go

5. Restarting the service 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 on SERVER1. Right-click the following service and click Restart.

Displayed Name: SQL Server (SSCCMDB) Service Name: MSSQL$SSCCMDB

6. Transferring the database to SERVER1 Restore the file backed up in the procedure 1. Put the backup file on the local disk of SERVER1 in advance. In the following example, the name of the backup file is set as C:\temp\sysmonbk.dat. E.g.1) > sqlcmd –E –S (local)\SSCCMDB –Q "restore database RM_PerformanceDataBase2 from disk = 'C:\temp\sysmonbk.dat' with replace"

E.g.2) > sqlcmd -E -S (local)\SSCCMDB 1> restore database RM_PerformanceDataBase2 from disk = 'C:\temp\sysmonbk.dat' with replace

http://msdn.microsoft.com/en-us/library/ms191294(v=sql.130).aspx

http://msdn.microsoft.com/en-us/library/hh403394(v=sql.130).aspx





2> go

7. Creating SQL Server Login Run the following command on a command prompt window on SERVER1.


> sqlcmd –E –S (local)\SSCCMDB 1> CREATE LOGIN [Login Name] FROM WINDOWS WITH DEFAULT_DATABASE=[RM_PerformanceDataBase2] 2> go 1> EXEC master..sp_addsrvrolemember @loginame = N'Login Name', @rolename = N'sysadmin' 2> go 1> exit

Notes: Replace the following data with the Login Name part:

▪ Domain Name\the computer name of the management server$. ▪ If the CREATE LOGIN command has been executed, the message which says "The server principal 'Login name' already exists" appears. In such a case, perform from the EXEC command to the end.

E.g.) An input example for the case of domain Domain name: Domain

The computer name of the management server: SSC_Management_Server > sqlcmd –E –S (local)\SSCCMDB 1> CREATE LOGIN [Domain\SSC_Management_Server$] FROM WINDOWS WITH DEFAULT_DATABASE=[RM_PerformanceDataBase2] 2> go 1> EXEC master..sp_addsrvrolemember @loginame = N'Domain\SSC_Management_Server$', @rolename = N'sysadmin' 2> go 1> exit

8. Environment settings Configure the environment settings and restart the SystemMonitor Performance Service.

1. Start System Monitor - Performance Services Installation folder\bin\ rm_databasecfg.exe on the management server.

2. The System Monitor – Database Setting Tool dialog box appears.

281

3. Type the appropriate name into the Host name box and the Instance name box, 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 SystemMonitor Performance Service and click Restart.

9. Deleting the database from the management server To delete the original database after the transfer, run the following by using the command prompt in the management server.

> sqlcmd -E -S .\SSCCMDB -Q "DROP DATABASE RM_PerformanceDataBase2"

Transferring the System Monitor - Performance Services database using Windows authentication login is now complete.



Using SQL Authentication Login Perform the following procedures to transfer the System Monitor - Performance Services database using the SQL authentication login.

1. Backing up System Monitor - Performance Services Back up System Monitor - Performance Services. For the procedure, see Subsection 10.3.1, "Backing up System Monitor - Performance Services" in NEC SigmaSystemCenter Configuration Guide.

Note: Set the name of the backup file as "sysmonbk.dat".

2. Creating Instance Setup the SQL Server 2016 SP1 Express on SERVER1.

1. Download the setup program of SQL Server 2016 SP1 Express from the following site.


2. Run the downloaded SQLEXPR_x64_ENU.exe and proceed with the setup according to the instructions on the screen.

3. The Instance Configuration dialog box appears. Select Named instance and type SSCCMDB into the text box.


283

4. Server Configuration dialog box appears. Select NT Service\MSSQL$SSCCMDB for the account name of SQL Server Database Engine service.

5. Database Engine Configuration dialog box appears. Select Mixed Mode (SQL Server authentication and Windows authentication). Enter the sa logon password in the Enter password box and the Confirm password box.

Note: The administrator determines the password.



6. To specify the SQL Server administrator, Click Add….

7. The Select Users or Groups dialog box appears. Type SYSTEM into Enter the object names to select (examples): and then click OK.

285

8. The Database Engine Configuration dialog box appears. Click Next.

After this, follow the instructions that appear on the screen to complete the setup.

3. Enabling the network connection As SQL Server 2016 SP1 Express permits only the local client connection by default, you need to enable the network connection. In addition, SQL Server Browser must be started and Firewall exceptions must be created.

• In SQL Server Configuration Manager, enable TCP/IP and Named pipes, and then restart the SQL Server (SSCCMDB) service.

• In SQL Server Configuration Manager, change the start mode of SQL Server Browser to Automatic, and then start SQL Server Browser.

• In Windows Firewall with Advanced Security, add the following inbound rules:

• TCP 1433 • UDP 1434

• In the SQL Server installation folder: \MSSQL13.SSCCMDB\MSSQL\Binn\Sqlservr.exe The default path when you installed SQL Server 2016 SP1 Express with the default settings is one of the following: C:\Program Files\Microsoft SQL Server\MSSQL13.SSCCMDB\MSSQL\Binn\Sqlservr.exe

or



C:\Program Files (x86)\Microsoft SQL Server\MSSQL13.SSCCMDB\MSSQL\Binn\Sqlservr.exe

Reference: Go to the following sites for more details: ▪ http://msdn.microsoft.com/en-us/library/ms191294(v=sql.130).aspx ▪ http://msdn.microsoft.com/en-us/library/hh403394(v=sql.130).aspx ▪ http://msdn.microsoft.com/en-us/library/ms175043(v=sql.130).aspx

4. Creating a database Run the following command on the Command Prompt window.


E.g.1) > sqlcmd –E –S (local)\SSCCMDB –Q "create database RM_PerformanceDataBase2"

E.g.2) > sqlcmd –E –S (local)\SSCCMDB 1> create database RM_PerformanceDataBase2 2> go

5. Restart the service 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 on the SERVER1.

Right-click the following service and click Restart.

Displayed Name: SQL Server (SSCCMDB) Service Name: MSSQL$SSCCMDB

6. Transferring the database to the SERVER1 Restore the file backed up in the procedure 1. Put the backup file on the local disk on the SERVER1 in advance. In the following example, the name of the backup file is set as C:\temp\sysmonbk.dat. E.g.1) > sqlcmd –E –S (local)\SSCCMDB –Q "restore database RM_PerformanceDataBase2 from disk = 'C:\temp\sysmonbk.dat' with replace"

E.g.2) > sqlcmd -E -S (local)\SSCCMDB 1> restore database RM_PerformanceDataBase2 from disk = 'C:\temp\sysmonbk.dat' with replace


http://msdn.microsoft.com/en-us/library/hh403394(v=sql.130).aspx


287

2> go

7. Environment settings Configure the environment settings and restart the SystemMonitor Performance Service.

1. Start System Monitor - Performance Services Installation folder\bin\ rm_databasecfg.exe on the management server.

2. The System Monitor – Database Setting Tool dialog box appears.

3. Type the appropriate name into the Host name box and the Instance name box, and select Use SQL authentication login. 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 SystemMonitor Performance Service and click Restart.

8. Deleting the database from the management server



To delete the original database after the transfer, run the following by using the command prompt in the management server. > sqlcmd -E -S .\SSCCMDB -Q "DROP DATABASE RM_PerformanceDataBase2"

Transferring the System Monitor - Performance Services database using SQL authentication login is now complete.

289

Appendix C Transferring the Database (For PostgreSQL)

After installing a PostgreSQL, you can transfer the PostgreSQL to the different server from a management server by configuring the server in the same network of the management server. We explain how to transfer by using an example. In the example, the destination server name is "SERVER1" and the version of transferring PostgreSQL is PostgreSQL 9.5.

Note: You cannot transfer the database from SQL Server to PostgreSQL.

1. Backing up System Monitor - Performance Monitoring Services For the details, see 9.9.4, "Procedure for Backing up and Restoring the Database."

Note: In this example, the file name of the backup is sysmonbk.sql.

2. Installing PostgreSQL on SERVER1 To install, refer to Appendix A, "Installing/Uninstalling PostgreSQL" > "Installing PostgreSQL" > "When configuring the database to a machine (database server) different from a management server" in NEC SigmaSystemCenter Installation Guide.

3. Creating a database Run the following by using the command prompt in SERVER1. Make sure use "RM_PerformanceDataBase2" as the name of the database. You can specify any user name after the -U option.

> psql.exe -h localhost -p 5432 -U postgres -d postgres -c "CREATE DATABASE \"RM_PerformanceDataBase2\";"

4. Restarting a service

To open Services in SERVER1, click Start, click Control Panel, double-click Administrative Tools, and then double-click Services. Right-click the following service, and then click Restart.

Service name: postgresql-x64-9.5 Display name: postgresql-x64-9.5 - PostgreSQL Server 9.5

5. Transferring the database to SERVER1

Appendix C Transferring the Database (For PostgreSQL)


To restore the file backed up at the procedure 1, copy the file to the local disk of SERVER1 (in this example, copy to "C:\temp\sysmonbk.sql"), and then run the following by using the command prompt in SERVER1.

> psql.exe -h localhost -p 5432 -U postgres -d pvminf -f "C:\temp\Backup.sql"

6. Environment Setting

Configure the environment and restart SystemMonitor Performance Service.

1. Start "System Monitor - Performance Monitoring Services installation folder\bin\ rm_databasecfg.exe" in the management server.

2. The Environment Setting window is displayed.

3. Type each information in the Host name, Port No, and User ID text box. In the Password and Confirm password text box, type the user password of the PostgreSQL. Click Save.

4. To open Services, click Start, click Control Panel, double-click Administrative Tools, and then double-click Services.

291

5. Right-click SystemMonitor Performance Service, and then click Restart. 7. Deleting the database from the management server

To delete the original database after the transfer, run the following by using the command prompt in the management server.

> psql.exe -h localhost -p 5432 -U postgres -d postgres -c "DROP DATABASE \"RM_PerformanceDataBase2\";"

End of the procedure.

293

Appendix D Performance Counter Information of VMware ESXi

Describe the specified value of each option when adding custom performance indicator of ESXHost, ESXGuest in ssc-perf add performanceindicator command.

Metric Group (category) Refer to the following list for specifying the category of the ssc-perf add performanceindicator commands.

Metric Group Specified value of the option

CPU cpu

Memory mem

Disk disk

Network net

System sys

Storage Adapter storageAdapter

Storage Path storagePath

Virtual Disk virtualDisk

Datastore datastore

Power power

vSphere Replication hbr

For the details of the Metric Group, refer to the following VMware's document "vSphere Monitoring and Performance".

Reference: Acquire the description document for the Metric Group of the VMware vSphere 6.5 from the following URL.

http://pubs.vmware.com/vsphere-65/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-65-monitoring-performance-guide.pdf



Appendix D Performance Counter Information of VMware ESXi


Counter, Rollup (counter) About specifying the counter of ssc-perf add performanceindicator command, see the following information of reference pages. When specifying the counter, the combinations of counters and rollups which are recorded in reference pages are used.

The specifying style is as follows: counter = counter (rollup) When specifying the counter, the value of the counter must be selected from the column of the COUNTER in the counter list table which is recorded in reference pages and the value of the rollup must be selected from the column of the ROLLUPTYPE in the counter list table which is recorded in reference pages.

Metric Group Reference pages of the counter list

CPU cpu_counters.html

Memory memory_counters.html

Disk disk_counters.html

Network network_counters.html

System system_counters.html

Storage Adapter storage_adapter_counters.html

Storage Path storage_path_counters.html

Virtual Disk virtual_disk_counters.html

Datastore datastore_counters.html

Power power_counters.html

vSphere Replication hbr_counters.html

For the details of the counter and rollup, refer to the following VMware's document "vSphere Monitoring and Performance".

Reference: Acquire the description document for the counter of the VMware vSphere 6.5 from the following URL.


http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/cpu_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/memory_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/disk_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/network_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/system_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/storage_adapter_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/storage_path_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/virtual_disk_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/datastore_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/power_counters.html

http://pubs.vmware.com/vsphere-65/topic/com.vmware.wssdk.apiref.doc/hbr_counters.html



295

Appendix E License Information This product includes certain open source software. Details of individual licenses are provided on the SigmaSystemCenter DVD <SigmaSystemCenter Installation DVD>\doc\OSS directory. Please contact us in order to obtain the source code of software that is distributed under the GPL/LGPL. ▪ This product contains Microsoft SQL Server Express which is distributed by Microsoft Corporation without charge. Use this product after accepting the license agreement. For details of copyright and ownership rights, refer to the following license files: <folder where Microsoft SQL Server Express is installed>\License Terms ▪ 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.