Moviri Integration for BMC Capacity Optimization Microsoft ... · Now you have to click on System enter Operations Manager _, access to properties (by right click), then insert SCOM

Moviri S.p.A. Via Schiaffino 11 - 20158 Milano - Italy

Phone: +39 02 495170 01, fax: +39 02 70059905 E-mail: [email protected] – Web: www.moviri.com

Moviri Integration for BMC Capacity Optimization – Microsoft SCOM

User’s Guide

Version: 3.0.01

Moviri Integration for BMC Capacity Optimization – Microsoft SCOM User’s Guide

Moviri SpA

HeadQuarter

Via Simone Schiaffino, 11

20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower

One Market Street Suite 3500

San Francisco, CA 94105

USA

Website: www.moviri.com

Email: [email protected]

2 / 44

Moviri Integration for BMC Capacity Optimization – Microsoft SCOM

User’s Guide 1 Overview of the Integration ........................................................................................................................ 3

2 Requirements .............................................................................................................................................. 4

3 Installation .................................................................................................................................................. 5

4 Datasource Check and Configuration ......................................................................................................... 9

5 Connector configuration ........................................................................................................................... 12

6 Managing Hyper-V Virtual Farm View ...................................................................................................... 18

7 Troubleshooting ........................................................................................................................................ 23

8 Appendix A. Configuration and Performance/Business Metrics Mapping ............................................... 25

9 Appendix B. Lookup Fields ........................................................................................................................ 40

10 Appendix C. Object Relationships ............................................................................................................. 41

11 Appendix D. Legal Notices......................................................................................................................... 43


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



3 / 44

1 Overview of the Integration

“Moviri Integration for BMC Capacity Optimization – Microsoft SCOM” is an additional component of the BMC Capacity Optimization product. It allows to collect information from Microsoft System Center Operation Manager tool and it is able to extract and summarize resources performance data, configuration data and relationships among infrastructure entities.

All collected data can be analyzed using BMC Capacity Optimization tool, in order to: Analyze resources usage Perform trend analysis and forecast analysis Gain at-a-glance control over IT infrastructure capacity with BCO Virtual Farm Views Perform capacity optimization and planning

The connector supports configuration parameters that allow systems and metric collection filtering, historical recovery, limiting data volume processed in a single run, specifying data resolution and many other settings. The documentation is targeted at BCO administrators, in charge of configuring and monitoring the integration between BCO and Microsoft SCOM.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



4 / 44

2 Requirements

2.1 Official name of data source software

Microsoft System Center Operation Manager

2.2 Supported versions of BMC Capacity Optimization

BMC Capacity Optimization 4.5 - SP1 (4.5.00.01) BMC Capacity Optimization 4.5 - CP1 (4.5.01.01) BMC Capacity Optimization 4.5 – SP2 (4.5.02.00) BMC Capacity Optimization 9.0 – SP1 (9.0.01.00) and later Service Packs BMC Capacity Optimization 9.5

2.3 Supported versions of data source software

Microsoft SCOM 2007 R2 Microsoft SCOM 2012 Microsoft SCOM 2012 SP1

For different versions of data source software please contact Moviri (www.moviri.com) or BMC Support (http://www.bmc.com/support).

2.4 Supported configurations of data source software

Moviri Integration for Microsoft SCOM supports SCOM instances mandatorily configured with data warehouse component.

The supported DBMS versions, for the data warehouse DB, are Microsoft SQL Server 2005, 2008 and 2012. For different versions of DBMS please contact Moviri (www.moviri.com) or BMC Support (http://www.bmc.com/support).

2.4.1 Virtual Machine Manager

In order to extract virtualization metrics, the connector requires:

1. The Microsoft Virtual Machine Manager (VMM from now on) management tool, which is in charge of collecting data for the Microsoft virtual environment

2. A working connection among Microsoft SCOM and Virtual Machine Manager 3. The SCOM Virtual Machine Manager Management Packs

The following matrix presents the supported versions of the above mentioned components.

SCOM VMM SCOM Management Packs

2012 2012 Microsoft.SystemCenter.VirtualMachineManager.2012.Reports,

Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery,

Microsoft.SystemCenter.VirtualMachineManager.2012.Library

2007 R2 2008 Microsoft.Virtualization.Reports.2008.R2,

Microsoft.SystemCenter.VirtualMachineManager.2008.R2

http://www.bmc.com/support

http://www.bmc.com/support


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



5 / 44

3 Installation

This section provides the information needed to download and install the Additional Component “Moviri Integration for BCO - Microsoft SCOM”. The installation procedure is quick and easy, as it relies on the “patching” mechanism provided by BCO under the section ADMINISTRATION >SYSTEM >Maintenance.1

3.1 Preparing for installation

Before you can install the Additional Component, you must have previously installed one of the versions of BMC Capacity Optimizations listed in Section 2.2Errore. L'origine riferimento non è stata trovata..

3.2 Downloading the additional component

The Additional Component File can be downloaded from the BMC Electronic Product Distribution site2 and consists of the following archive:

Moviri Integration Version 3.0.01 for BMC Capacity Optimization - Microsoft SCOM.zip

3.3 Installing the additional component

To install the Additional Component, follow these steps:

1. Access the BCO Console

2. Navigate to Administration > System > Maintenance

3. Upload the Additional Component File (as indicated in Figure 1).

Figure 1: Upload Additional Component File

4. Read the End User License Agreement. If the terms are accepted, please click on the “Yes, I Accept” button (as indicated in Figure 3: End User License Agreement and Figure 4) in order to proceed with the installation. Otherwise, the installation procedure will stop.

1 Official documentation about this can be found in the BMC Capacity Optimization Administration Guide in PDF Format or online at

https://docs.bmc.com/docs/display/public/bcmco90/Maintenance 2 http://www.bmc.com/support/downloads-patches

https://docs.bmc.com/docs/display/public/bcmco90/Maintenance

http://www.bmc.com/support/downloads-patches


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



6 / 44

Figure 2: Installation first step

Figure 3: End User License Agreement

Figure 4: End User License Agreement Acceptance

5. Select the BCO scheduler instances on which the additional component shall be installed. Although it is possible to install it on any combination of BCO schedulers, it is suggested to perform the


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



7 / 44

installation on all ETL-Engines (i.e. their scheduler instances), so that tasks configured to use "Moviri Integration to Microsoft SCOM" can be executed on any of them. Please do not install the additional component on non-ETL Engine schedulers (e.g. BCO Application Server not installed in “AS+EE” configuration)

Figure 5: Scheduler Instance selection

6. A successful execution will result in a green line in the “Additional components” table.

Figure 6: Successful outcome of the patching operation

7. It is possible (and recommended, in case of unsuccessful outcome, e.g. a yellow WARNING line) to inspect the deployment log, which can be done by clicking on the icon highlighted in Figure 7. This opens a new page in which the various upload executions are listed; for each of these lines the detailed log (containing, when applicable, a backup version of any replaced files) can be downloaded (as indicated in Figure 8)

Figure 7: Access to ETL Deployment Log


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



8 / 44

Figure 8: Deployment Logs page


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



9 / 44

4 Datasource Check and Configuration

4.1 Preparing to connect to the data source software

As a first step, please ensure that the correct version of SCOM is installed. You can perform this check from the “About” section of the SCOM Console (as shown in Figure 2).

Figure 9: Version Check in MS SCOM Console

In order for SCOM to store historical metrics, it needs to be configured to use data warehouse database.

Please also ensure that the data warehouse DBMS version is compliant with the requirement indicated in Section Errore. L'origine riferimento non è stata trovata..

The connector needs a Login that has at least read rights on the data warehouse DB. SQL Server allows two authentication types:

SQL Server Authentication

Windows Authentication

If your SQL Server authentication mode is set to “Mixed mode” it is suggested to use a user with SQL Server Authentication for the connector, however both Authentication types are supported.

4.2 Connect VMM to SCOM

A working network connection between VMM and SCOM is required to have VMM collected metrics available into the SCOM datawarehouse.

4.2.1 VMM 2012 to SCOM 2012

The connect SCOM 2012 to VMM 2012 you need to access the VMM 2012 Settings panel and click on “Settings” (Red square), then on “System Center settings” (blue square) as shown in the following figure


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



10 / 44

Now you have to click on “System Center Operations Manager”, access to properties (by right click), then insert SCOM management server hostname and credentials, as shown in the following figure:

4.2.2 VMM 2008 to SCOM 2007 R2

The same steps are valid also for the connection between SCOM 2007 and VMM2008 and shown in the following figure:


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



11 / 44

4.3 SCOM Data Availability Check

In order to make ensure data is available in SCOM DWH, please make sure that the SCOM Monitoring views do present the relevant metrics by selecting them and setting a proper chart time frame. Please repeat this step for each desired management pack and entity type you are interested in.

As an example, the following figure shows the Host Performance view of the SCOM 2012 Virtual Machine Manager Management Pack.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



12 / 44

5 Connector configuration

5.1 Connector configuration attributes

This section describes the available configuration properties for the ETL using BCO 9.0.01 or higher. BCO 4.5 display a single SCOM-specific ETL configuration tab called Custom Properties, with the same properties as shown in the table below

Tab SCOM - Data Selection

Property Name Type Required? Description

Metric classes to import Checkbox Yes

import metric classes belonging to selected classes: - CPU and Memory (Basic) - Memory (Advanced) - Logical Disk Performance - Logical Disk Occupation - Physical Disk Performance - Network Interface - Internet Information Services - Database - Hyper-V (with Relationships)

Management pack to import Checkbox Yes

Import metrics and entity belonging to the selected SCOM management packs - Windows - SQL Server - Hyper-V

Custom Management Pack String No If defined, the ETL will look for the standard Windows Server metrics in the custom management pack.

Management pack filter String No Advanced property - Semicolon-separated list of management packs whose data is going to be imported. Empty list means all.

Activate filtering on Checkbox No

For each box checked, the console shows two additional properties: whitelist and blacklist, which can be filled with a semicolon-separated list of SQL Like operator expressions, in order to filter imported entities (for detailed instructions see par. 5.1.1) Filters are available for the following entity types: - Physical servers - Database - Virtual machines - Virtual hosts - Virtual clusters

Extract the subtree roots on whitelisted system

Boolean Yes If "yes" will be imported all entities contained in currently filtered entities

Tab SCOM - Settings

Property Name Type Required? Description

Default last counter (YYYY-MM-DD HH24:MI:SS)

String yes Default value of the last counter. By default, if no last counter has been set, data will be extracted from this date

Recovery mode active Boolean yes If it is set to true the “Since date” and “To date” parameters will be took in to account as lower and upper bound of the import time interval. The last counters will not be affected

Since (YYYY-MM-DD HH24:MI:SS) String No Lower bound of the import time interval. This property is required if it is needed to import data for a specific time period.

To (YYYY-MM-DD HH24:MI:SS) String No Upper bound of the import time interval. This property is required if it is needed to import data for a specific time period.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



13 / 44

Relocate all series in time zone * String yes SCOM stores all data in UTC format. This property allows timestamps to be shifted to your timezone of choice. Time zone name has to be in Java format – see below. For no shifting fill with “UTC”.

Assign time zones to series Boolean yes

If set to true, information about the time zone chosen in the previous property will be recorded into BCO. If set to false the timestamps computed according to the previous property will be loaded without time zone information.

Remove SQL Server prefix Boolean yes If it is set to false the database instances name format will be like “HOST:DATABASEINSTANCE”, otherwise it will be “DATABASEINSTANCE”

Compute size and occupation metrics even for aggregated data**

Boolean yes If set to true, the computed metrics will be computed even for hourly data

Data Resolution Radio yes If it is set to ‘RAW’, raw data will be imported, otherwise, if it is set to ‘HOUR’ hourly data will be imported

Max days to extract in a single run Integer No If recovery mode is not active, this property specifies the maximum number of days the etl can extract in a single run, empty or zero means no limit.

Table 1 – Configuration Attributes

(*)The property “Relocate all series to time zone” has to be filled with the name of the time zone in IANA (Internet Assigned Numbers Authority, see http://www.iana.org/time-zones/) format. Some time zone names examples are the following: Europe/Rome, Europe/London, America/New_York.

(**)”Compute size and occupation metrics even for aggregated data”: some of the metrics the connector extracts are not directly available in the SCOM data warehouse database. They are computed using other metrics – they are called derived metrics (for more details, see section 6.2.3) . It could happen that the base metrics (upon which the derived are computed) are collected from the SCOM Agent at different time instants. In this case, if the connector is extracting data at raw level, the related derived metric will be not computed.

If the connector is extracting data at hour level, there might be a chance that the related derived metric could be wrong, in case the SCOM Agent sample them at different instants. For those reasons, it is possible to choose whether enable or not the computation of the derived metrics, setting properly the ”Compute size and occupation metrics even for aggregated data” property.

5.1.1 Filtering systems with whitelist and blacklist

In order to restrict SCOM ETL extraction only to chosen entities, it is possible to activate filtering by entity type based on combination of whitelist and blacklist. If whitelist and blacklist are empty, no filter will be applied.

The two properties accept list of expressions semicolon separated, and expression can be:

Flat Strings (e.g. websrv105;appsrv20) SQL like operator expressions: accept wildcard “%” (matches any group of characters) and “_”

(matches any single character)

In Figure 10 is shown a configuration example: filtering is active on physical servers, databases and virtual machines.

Physical servers: Included: all servers matching websrv% or appsrv%


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



14 / 44

Excluded: websrv25 Databases:

Included: all DB instances Excluded: all DB instances matching DBTEST%

Virtual machines: Included: all VM matching vm1__ Excluded: no VM excluded

Figure 10 – Filters configuration


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



15 / 44

5.1.2 Connector configuration example

The following figure shows an example of a valid ETL configuration.

Figure 11 – Data Selection Properties

Figure 12 – Settings Properties

In this particular configuration, the following properties are set:

Data about all metrics classes is imported Metrics are retrieved from all supported management pack: Windows, SQL Server and Hyper-V; Metrics are retrieved for all the available systems (no filters are set) Raw data is imported The series will be relocated to time zone “Europe/Rome” No time zone info will be assigned to each data series If lastcounter has not been already defined, data is retrieved from 2013-05-12 00:00:00 In order to control data volume extraction, each run extract maximum 3 days of data


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



16 / 44

5.1.3 Database Connection parameters configuration

Moviri ETL allows to connect to SCOM DWH using SQL Server Authentication or Windows Authentication. Below are shown how to configure the database connection attributes in “Connection parameters” tab

SQL Server Authentication

Database type: “Microsoft SQL Server” Database user: <SCOM_DWH_username> Database password: <SCOM_DWH_password> JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver Host Name: <SCOM_DWH_hostname> Port: <SCOM_DWH_port> Database Name: <SCOM_DWH_DB_name>

Figure 13 – Connection parameters (SQL Server Authentication)

Windows Authentication

Database type: “Other Database” Database user: <Domain_username> Database password: <Domain_password> JDBC Driver: net.sourceforge.jtds.jdbc.Driver JDBC Url: jdbc:jtds:sqlserver://

<SCOM_DWH_hostname>:<SCOM_DWHport>/<SCOM_DWH_DB_name>;domain=<Domain_name>

Figure 14 – Connection parameters (Windows Authentication)

For connection requiring Windows authentication you may also use database type= “Microsoft SQL Server (JTDS)”


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



17 / 44

5.2 Historical data extraction

In order to perform an historical import, in tab “SCOM – Settings ” is available the Recovery mode option. When activated, fields “Since date” and “To date” will be shown, and the task imports data for the defined time interval without taking into account the last counters and without modifying them, “max days to extract in a single run” property is ignored too.

Figure 15 – Recovery mode configuration

5.3 Supported Platforms

The following table outlines the supported platform and the mapping to BCO entity types.

Supported Platform BCO Entity Type

Standalone Windows Instance Generic

Windows Internet Information Services Web Server Generic

SQL Server Instance Database Instance

Hyper-V Cluster Virtual Cluster – Microsoft HyperV

Hyper-V Hypervisor Virtual Host – Microsoft HyperV

Hyper-V Virtual Machine Virtual Machine – Microsoft HyperV


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



18 / 44

6 Managing Hyper-V Virtual Farm View

The Hyper-V Virtual Farm is a built-in BCO view that allows you to manage the capacity of a virtualized infrastructure running Microsoft Hyper-V hypervisor based virtualization system. It presents key capacity metrics and charts for Hyper-V hosts and domains. You can use Hyper-V views to see the total capacity, used capacity, remaining capacity and growth trend for CPU and memory sub-systems. Refer to the BMC Capacity Optimization documentation for further details.

The Hyper-V Virtual Farm view enables you to identify:

which host should the new domains be added to

whether certain hosts require a better load balancing between them

which systems in a particular domain have exceeded their threshold values

The present connector is designed to integrate the required metrics that lets you leverage this view capabilities.

6.1 Hyper-V Hosts View

The Host View tab provides an overview of all available Hyper-V hosts in the Hyper-V virtualization environment, including details about CPU and memory utilization, unused resources and more.

The following figure shows the Hyper-V Host View tab displaying all Hyper-V hosts present in the BPA domain.

The Hyper-V Hosts table lists all Hyper-V hosts in the selected domain. Each row corresponds to a Hyper-V host and shows the following information:

Field Description

Host Name of the Hyper-V host

Cluster Name of the cluster that contains the Hyper-V host


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



19 / 44

Field Description

Physical Cores Number of CPU cores in the host

Unused cores Total number of unused CPU cores

CPU Utilization [%] CPU used by the Hyper-V host

Total Virtual Processors Total number of virtual CPU processors configured for all partitions

CPU Model Model name of the CPU

VCPU density Ratio of virtual CPUs over physical CPU cores

CPU Frequency [Ghz] Processing capacity (in Gigahertz) of the Hyper-V CPU

Memory Utilization [%] Memory used by the host

Memory configured Total physical memory in GB configured for the Hyper-V host

Memory Used [GB] Total physical memory in GB consumed the Hyper-V host

Unused Memory [GB] Unused memory in the Hyper-V host

Total Spec Rating The total SPEC benchmark performance rating of the host, based on the CPU model and number of CPU cores

Spec Rating Used Used SPEC rating of the host, based on CPU utilization and the total SPEC rating

Unused Spec Rating Unused SPEC rating of the host, based on CPU utilization and the total SPEC rating

Network Rate [Mbit/s] Average network input/output rate, measured in Megabits per second

Disk I/O Rate [MB/s] Average disk input/output rate, measured in Megabytes per second

Configured Partitions Number of configured partitions in the Hyper-V host

Host Name of the Hyper-V host

Cluster Name of the cluster that contains the Hyper-V host

Physical Cores Number of CPU cores in the host

Unused cores Total number of unused CPU cores

CPU Utilization [%] CPU used by the Hyper-V host

Total Virtual Processors Total number of virtual CPU processors configured for all partitions


VCPU density Ratio of virtual CPUs over physical CPU cores











Configured Partitions Number of configured partitions in the Hyper-V host




Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



20 / 44

Field Description









6.2 Hyper-V Partitions View

The Hyper-V Partition View tab provides an overview of the available partitions in the Hyper-V virtualization environment, including details about online processors, CPU and memory utilization, memory configured, and more.

The following figure shows the Hyper-V Partition View tab.

The Hyper-V Partitions table lists all partitions present in the selected Hyper-V host. Each row corresponds to a Hyper-V partition and shows the following information:


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



21 / 44

Field Description

Hyper-V Name of the Hyper-V partition

Host Name of the host the Hyper-V partition belongs to


CPU Frequency [Ghz] Processing capacity (in Gigahertz) of the CPU

Virtual Processors Number of active virtual processors in the partition

CPU Utilization [%] Percentage of CPU used by the partition normalized by the number of virtual processors configured for the partition

Memory Configured [GB] Total physical memory configured for the partition, in GB



6.3 Hyper-V Virtual Farm Treemap View

Treemaps provide a graphical representation of the Virtual Farm capacity. They are implemented using the data visualization tool ‘treemaps’, and display system entities in a hierarchical fashion using a series of clustered rectangles, which together represent a whole system.

On the left side of the map, the virtual farm environment is represented using a tree structure. The nodes at the first level of the tree contain the Hyper-V hosts; expanding each host, you can see the contained Hyper-V partitions, represented as leaves.

The size of the box is defined by the metric selected in the ‘Chart Type’, and the color is determined by the threshold set for the entity.

The following figure shows the Hyper-V Virtual Farm Treemap with Memory Utilization selected in the Chart Type list, displaying the utilization pattern for all Hyper-V hosts belonging to the BPA domain.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



22 / 44


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



23 / 44

7 Troubleshooting

Once installed, the status of any ETL can be quickly verified from the list under ADMINISTRATION >SCHEDULER >ETL tasks, as shown in Figure 3.

Figure 16 – ETL List example

As indicated in the online Administration Guide3, three exit statuses exist for BCO tasks:

OK - The ETL task completed successfully.

WARNING - It can be generated by a large number of causes (missing or corrupted data, etc.), for which a complete stop of the ETL is not considered necessary.

FAILED - The ETL task was aborted, due for example to a network failure or a bad configured parameter that could prevent an ETL from connecting to a database or mounting a network folder. An example of this is detailed in Figure 4, in which the ETL was configured with wrong access credentials to the database.

Figure 17 – Example log of a failed ETL Task

The log shown in the figure above can be accessed from the BCO web interface as indicated in the next figure.

3 https://docs.bmc.com/docs/display/public/bcmco90/Managing+ETL+tasks

https://docs.bmc.com/docs/display/public/bcmco90/Managing+ETL+tasks


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



24 / 44

Figure 18 – Log Access Link

Missing data can also represent a common problem; as indicated above, in this case a WARNING would be associated to the ETL task. This can be due to a number of scenarios, among which:

The data is not available on SCOM. In this case, it is recommended to check the SCOM Console settings and status. May be that SCOM is not collecting data.

The data is available on SCOM but the ETL is not able to extract it. For Raw data, this can be due to the lack of overlap of the “extraction window”, as indicated in Figure 19. In the Figure, the ETL is trying to extract data for a time period for which there are no data in the data warehouse DB. In any case, it is possible to manually run the actual queries used for data collection against the SCOM data warehouse, as they are indicated in the ETL log (when the ETL Log Level is set to 5 – Medium), in order to ascertain the presence of the data in that desired time range.

Figure 19 – Dataset empty log


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



25 / 44

8 Appendix A. Configuration and Performance/Business Metrics Mapping

8.1.1 Configuration Metrics

The following configuration metrics are imported into BCO:

Management pack: Microsoft.Windows.Library

SCOM Metric Name BCO Metric Factor

OS Version OS_VER

OS Version Display Name OS_TYPE

Physical Memory TOTAL_REAL_MEM 1024

Logical Processors CPU_NUM

Management pack: Microsoft.SQLServer.Library


Instance Name DB_NAME

Edition SQLSERVER_EDITION_C

Collation BYDB_COLLATION_C

Database Autogrow BYDB_AUTOGROW_C

Log Autogrow BYDB_LOG_AUTOGROW_C

Management pack: Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery


Number Of Processors CPU_NUM

No Of VMs Running GM_ON_NUM

No Of VMs Deployed GM_NUM

Total RAM TOTAL_REAL_MEM

Host Failure Reserve CLUSTER_FAILOVER_TOLERANCE

Number Of Nodes HOST_NUM

Commit State CLUSTER_COMMIT_STATE_C

CPU Count CPU_NUM

Max Memory MB MEM_LIMIT 1048576

No Of Virtual Disks DISK_NUM

No Of NICs NETIF_NUM

Total Size Of Virtual Disks DISK_USED_SPACE

MaxSize (VirtualDiskDrive) DISK_SIZE

Dynamic Memory MEM_DYNAMIC_ALLOCATION_C

State VM_LAST_STATUS

Host Name HOST_NAME

Cloud CLOUD_NAME

OperatingSystem OS_TYPE

Management pack: Microsoft.SystemCenter.VirtualMachineManager.2008.R2


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



26 / 44


HostFailureReserve CLUSTER_FAILOVER_TOLERANCE

NoOfNodes HOST_NUM

NoOfVMsDeployed GM_NUM

NoOfVMsRunning GM_ON_NUM

NumberOfProcessors CPU_NUM

TotalRAM TOTAL_REAL_MEM

Processor CPU_NUMCount TOTAL_REAL_MEM 1048576

NoOfVirtualDisks DISK_NUM

NoOfNICs NETIF_NUM

TotalSizeOfVirtualDisks DISK_USED_SPACE

MaxSize (VirtualHardDisk) DISK_SIZE

State VM_LAST_STATUS

HostName HOST_NAME

OperatingSystem OS_TYPE

Table 2 - Configuration Metrics

8.1.2 Performance Metrics

Management pack: Microsoft.Windows.Server.2012.Monitoring

SCOM Object SCOM Counter BCO Metric Factor

Logical Disk % idle time BYLDISK_UTIL (1-(value*0.01))

Logical Disk Avg. Disk sec / Transfer BYLDISK_RESPONSE_TIME_C 1

Logical Disk Avg. Disk sec / Write BYLDISK_WRITE_RESPONSE_TIME_C 1

Logical Disk Avg. Disk sec / Read BYLDISK_READ_RESPONSE_TIME_C 1

Logical Disk Current Disk Queue Length BYLDISK_QUEUE_SIZE_C 1

Logical Disk Free Megabytes BYLDISK_FREE_SPACE 1048576

Logical Disk % Free Space BYLDISK_USED_SPACE_PCT 1-(value*0.01)

Physical Disk Avg. Disk sec / Read BYDISK_READ_RESPONSE_TIME_C 1

Physical Disk Avg. Disk sec / Write BYDISK_WRITE_RESPONSE_TIME_C 1

Physical Disk Avg. Disk sec / Transfer BYDISK_RESPONSE_TIME 1

Physical Disk Disk Bytes / sec BYDISK_TRANSFER_RATE 1

Physical Disk Disk Read Bytes / sec BYDISK_READ_RATE 1

Physical Disk Disk Write Bytes / sec BYDISK_WRITE_RATE 1

Physical Disk Disk Writes / sec BYDISK_PHYS_IO_WRITE_RATE 1

Physical Disk Disk Reads / sec BYDISK_PHYS_IO_READ_RATE 1

Physical Disk Current Disk Queue Length BYDISK_QUEUE_SIZE 1

Physical Disk % Idle Time BYDISK_UTIL 1-(value*0.01)

Memory Available MBytes Total MEM_FREE 1048576

Memory Pages / sec MEM_PAGE_RATE 1

Memory Percent Memory Used MEM_UTIL 0.01


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



27 / 44

Memory Free System Page Table Entries Total MEM_FREE_SYS_PTE_C 1

Memory Pool Non Paged Bytes MEM_POOL_NONPAGED_BYTES_C 1

Memory Pool Paged Bytes MEM_POOL_PAGED_BYTES_C 1

Memory Pool Paged Resident Bytes MEM_POOL_PAGED_RESIDENT_BYTES_C 1

Memory Page Reads / sec MEM_PAGE_IN_RATE 1

Memory Page Writes / sec MEM_PAGE_OUT_RATE 1

Memory Cache Bytes MEM_CACHED 1

Memory %committed Bytes in Use MEM_UTIL_COMMITTED_C 0.01

Memory Committed Bytes MEM_COMMITED 1

Network Adapter Percent Bandwidth Used Total BYIF_UTIL 0.01

Network Adapter Percent Bandwidth Used Read BYIF_IN_UTIL 0.01

Network Adapter Percent Bandwidth Used Write BYIF_OUT_UTIL 0.01

Network Interface Bytes Total / sec BYIF_BIT_RATE 8

Network Interface Bytes Received / sec BYIF_IN_BIT_RATE 8

Network Interface Bytes Sent / sec BYIF_OUT_BIT_RATE 8

Network Interface Current Bandwidth BYIF_BANDWIDTH 8

Processor Information % Processor Time CPU_UTIL 0.01

Processor Information % Interrupt Time CPU_UTIL_INTERRUPT_HANDLING 0.01

Paging File %usage SWAP_SPACE_UTIL 0.01

System Processor Queue Length CPU_RUN_QUEUE 1

System Context Switches / sec CTX_SWITCH_RATE 1

Management pack: Microsoft.Windows.Server.2008.Monitoring




















Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



28 / 44




















Processor % Processor Time CPU_UTIL 0.01

Processor % Interrupt Time CPU_UTIL_INTERRUPT_HANDLING 0.01




Management pack: Microsoft.Windows.Server.2003

















Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



29 / 44
























Processor % Interrupt Time CPU_UTIL_INTERRUPT_HANDLING 0.01




Management pack: Microsoft.Windows.Server.2000


Logical Disk % idle time BYLDISK_UTIL 1-(value*0.01)












Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



30 / 44





Management pack: Microsoft.Windows.InternetInformationServices.2012


Web Service Bytes Received / sec WEBSRV_IN_BYTE_RATE_C 1

Web Service Bytes Sent / sec WEBSRV_OUT_BYTE_RATE_C 1

Web Service Connection Attempts / sec WEBSRV_CONNECTION_ATTEMPTS_RATE_C 1

Web Service Current Connections WEBSRV_CURRENT_CONNECTIONS_C 1

Web Service Total Method Requests / sec WEBSRV_HIT_RATE_C 1











Management pack: Microsoft.SQLServer.2012.Monitoring


:Database:Filegroup DB Filegroup Allocated space left (MB) BYDBFILEGRP_ALLOCATED_FREE_SPACE_C 1048576

:Database:Filegroup DB Filegroup free space (MB) BYDBFILEGRP_TOTAL_FREE_SPACE_C 1048576

:Database:DBlogfile DB Log File Allocated space left (MB) BYDBFILEGRP_LOG_ALLOCATED _FREE_SPACE_C 1048576

:Database:Filegroup DB Filegroup Allocated space left (%) BYDBFILEGRP_ALLOCATED_USED_SPACE_PCT_C (1-(value*0.01))

:Database:Filegroup DB Filegroup Free Space (%) BYDBFILEGRP_TOTAL_USED_SPACE_PCT_C (1-(value*0.01))

:Database:DBLogfile DB Log File Allocated Space Left (%) BYDBFILEGRP_LOG_ALLOCATED_USED_ SPACE_PCT_C (1-(value*0.01))

%:database DB Allocated Size (MB) BYDB_DATA_ALLOCATED_SPACE_C 1048576

%:database DB Total Free Space (%) BYDB_TOTAL_FREE_SPACE_PCT_C 0.01

:storageenginequery Avg Time / query DB_QUERY_RESP_TIME_C 1000

:locks Lock Requests / sec DB_LOCK_RATE 1

:locks Lock Time outs/sec DB_LOCK_TIMEOUT_RATE_C 1

:locks Lock waits / sec DB_LOCK_WAIT_RATE_C 1

:generalstatistics Logins / sec DB_LOGON_RATE 1

:locks Number of Deadlocks / sec DB_DEADLOCK_RATE_C 1

:processing Rows read/sec DB_ROWS_READ_RATE_C 1

:processing Rows written / sec DB_ROWS_WRITTEN_RATE_C 1

Sqlstatistics Sql Compilations / sec DB_SQL_COMPILATION_RATE_C 1


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



31 / 44

Sqlstatistics Sql re-compilations / sec DB_SQL_RECOMPILATION_RATE_C 1

:databases Transactions / sec DB_TRAN_RATE 1

:buffermanager Buffer cache hit ratio DB_BUFFER_HIT_RATIO 0.01

Brokerstatistics Broker Transaction Rollbacks DB_TRANSACTION_ROLLBACKS_C 1











:storageenginequery Avg Time / query DB_QUERY_RESP_TIME_C 1000






:processing Rows read/sec DB_ROWS_READ_RATE_C 1

:processing Rows written / sec DB_ROWS_WRITTEN_RATE_C 1














%:database DB Size (MB) BYDB_SIZE_MSSQL_C 1048576



%:database DB Free Space (%) BYDB_FREE_SPACE_PCT_MSSQL_C 0.01


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



32 / 44











Management pack: Microsoft.SystemCenter.VirtualMachineManager.2012.Reports


Memory Available MBytes MEM_FREE 1048576

Hyper v Logical Processor %Total Run Time CPU_UTIL 0.01

Logical Disk Free Megabytes DISK_FREE 1048576

Logical Disk Disk read Bytes / sec DISK_READ_RATE 1

Logical Disk Disk Write Bytes / sec DISK_WRITE_RATE 1

Logical Disk %Free space DISK_USED_SPACE_PCT 1-(value*0.01)

Network Interface Bytes Received / sec BYIF_IN_BYTE_RATE 1

Network Interface Bytes sent / sec BYIF_OUT_BYTE_RATE 1

VM CPU CPU_UTIL 0.01

VM Mem MEM_CONSUMED 1048576

VM Disk DISK_TRANSFER_RATE 1

VM Net Received NET_IN_BYTE_RATE 1

VM Net Sent NET_OUT_BYTE_RATE 1

Memory % Committed Bytes In Use MEM_UTIL_COMMITTED_C 0.01

Memory Available MBytes MEM_FREE 1048576

win32_perf formatted data_hvstats_hyperv hypervisor logical processor

Percent Total Run Time CPU_UTIL 0.01

processor %Processor Time CPU_UTIL 0.01

logicaldisk %Free Space DISK_USED_SPACE_PCT (1-(value*0.01))

logicaldisk Disk Bytes / sec DISK_TRANSFER_RATE 1

Network Interface Bytes total / sec NET_BYTE_RATE 1

Table 3 - Performance Metrics


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



33 / 44

8.1.3 Derived Metrics

In addition to the metrics available in the data source, the following derived metrics are computed by the connector:

Metric Category Derived BCO Metric Source BCO Metrics

Memory MEM_USED MEM_FREE; MEM_UTIL

Disk Occupation BYLDISK_SIZE BYLDISK_FREE_SPACE; BYLDISK_USED_SPACE_PCT

BYLDISK_USED_SPACE BYLDISK_SIZE; BYLDISK_USED_SPACE_PCT

DISK_USED_SPACE DISK_FREE; DISK_USED_SPACE_PCT

Disk Performance BYDISK_PHYS_IO_RATE BYDISK_PHYS_IO_WRITE_RATE; BYDISK_PHYS_IO_READ_RATE

DISK_TRANSFER_RATE DISK_WRITE_RATE; DISK_READ_RATE

Database Storage BYDBFILEGRP_ALLOCATED_SPACE_C BYDBFILEGRP_ALLOCATED_FREE_SPACE_C; BYDBFILEGRP_ALLOCATED_USED_SPACE_PCT_C

BYDBFILEGRP_ALLOCATED_USED_SPACE_C BYDBFILEGRP_ALLOCATED_SPACE_C; BYDBFILEGRP_ALLOCATED_USED_SPACE_PCT_C

BYDBFILEGRP_TOTAL_SPACE_C BYDBFILEGRP_TOTAL_FREE_SPACE_C; BYDBFILEGRP_TOTAL_USED_SPACE_PCT_C

BYDBFILEGRP_TOTAL_USED_SPACE_C BYDBFILEGRP_TOTAL_SPACE_C; BYDBFILEGRP_TOTAL_USED_SPACE_PCT_C

8.1.4 Metric Classes

All the metrics managed by the connector are grouped in “Metric Classes”:

Logical Disk Occupation

Logical Disk Performance

CPU and Memory Basic

Memory Advanced

Network Interface

Physical Disk performance

Database

Hyper-V

The following table shows for each metric class the contained metrics:

Metric Class BCO Metric

Logical Disk Performance BYLDISK_UTIL

BYLDISK_RESPONSE_TIME_C

BYLDISK_WRITE_RESPONSE_TIME_C

BYLDISK_READ_RESPONSE_TIME_C

BYLDISK_QUEUE_SIZE_C

Logical Disk Occupation BYLDISK_FREE_SPACE

BYLDISK_USED_SPACE_PCT

CPU and Memory Basic MEM_FREE


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



34 / 44


MEM_PAGE_RATE

MEM_UTIL

Memory Advanced MEM_FREE_SYS_PTE_C

MEM_POOL_NONPAGED_BYTES_C

MEM_POOL_PAGED_BYTES_C

MEM_POOL_PAGED_RESIDENT_BYTES_C

MEM_IN_PAGE_RATE

MEM_OUT_PAGE_RATE

MEM_CACHED

MEM_UTIL_COMMITTED_C

MEM_COMMITTED

CPU_UTIL

CPU_UTIL_INTERRUPT_HANDLING

SWAP_SPACE_UTIL

CPU_RUN_QUEUE

CTX_SWITCH_RATE

Network Interface BYIF_UTIL

BYIF_BIT_RATE

BYIF_BANDWIDTH

Internet Information Services WEBSRV_IN_BYTE_RATE_C

WEBSRV_OUT_BYTE_RATE_C

WEBSRV_CONNECTION_ATTEMPTS_RATE_C

WEBSRV_CURRENT_CONNECTIONS_C

WEBSRV_HIT_RATE_C

Database BYDBFILEGRP_ALLOCATED_FREE_SPACE_C

BYDBFILEGRP_TOTAL_FREE_SPACE_C

BYDBFILEGRP_LOG_ALLOCATED _FREE_SPACE_C

BYDBFILEGRP_ALLOCATED_USED

_SPACE_PCT_C

BYDBFILEGRP_TOTAL_USED_SPACE_PCT_C

BYDBFILEGRP_LOG_ALLOCATED_USED_ SPACE_PCT_C

BYDB_TOTAL_FREE_SPACE_PCT_C

BYDB_DATA_ALLOCATED_SPACE_C

DB_QUERY_RESP_TIME_C

DB_LOCK_RATE

DB_LOCK_TIMEOUT_RATE_C

DB_LOCK_WAIT_RATE_C

DB_LOGON_RATE


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



35 / 44


DB_DEADLOCK_RATE_C

DB_ROWS_READ_RATE_C

DB_ROWS_WRITTEN_RATE_C

DB_SQL_COMPILATION_RATE_C

DB_SQL_RECOMPILATION_RATE_C

DB_TRAN_RATE

DB_BUFFER_HIT_RATIO

DB_TRANSACTION_ROLLBACKS_C

Hyper-V BYIF_IN_BYTE_RATE

BYIF_OUT_BYTE_RATE

CLOUD_NAME

CLUSTER_COMMIT_STATE_C

CLUSTER_FAILOVER_TOLERANCE

CPU_NUM

CPU_UTIL

DISK_FREE

DISK_NUM

DISK_READ_RATE

DISK_SIZE

DISK_TRANSFER_RATE

DISK_USED_SPACE

DISK_USED_SPACE_PCT

DISK_WRITE_RATE

GM_NUM

GM_ON_NUM

HOST_NAME

HOST_NUM

MEM_CONSUMED

MEM_DYNAMIC_ALLOCATION_C

MEM_FREE

MEM_LIMIT

MEM_UTIL_COMMITTED_C

NET_BYTE_RATE

NETIF_NUM

NET_IN_BYTE_RATE

NET_OUT_BYTE_RATE

TOTAL_REAL_MEM

VM_LAST_STATUS


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



36 / 44

Table 4 - Metric Classes

The ETL can be configured to collect only specific metric classes by configuring the related custom properties.

8.2 Entities and Metrics

The following table describes how the metrics are assigned to the entities according to their types.

Metric Generic DB Instance Hyper-V Cluster

Hyper-V Host

Hyper-V VM

BYLDISK_UTIL X

BYLDISK_RESPONSE_TIME_C X

BYLDISK_WRITE_RESPONSE_TIME_C X

BYLDISK_READ_RESPONSE_TIME_C X

BYLDISK_QUEUE_SIZE_C X

BYLDISK_FREE_SPACE X

BYLDISK_USED_SPACE_PCT X

MEM_FREE X

MEM_PAGE_RATE X

MEM_UTIL X

MEM_FREE_SYS_PTE_C X

MEM_POOL_NONPAGED_BYTES_C X

MEM_POOL_PAGED_BYTES_C X

MEM_POOL_PAGED_RESIDENT_BYTES_C X

MEM_IN_PAGE_RATE X

MEM_OUT_PAGE_RATE X

MEM_CACHED X

MEM_UTIL_COMMITTED_C X

MEM_COMMITTED X

CPU_UTIL X

CPU_UTIL_INTERRUPT_HANDLING X

SWAP_SPACE_UTIL X

CPU_RUN_QUEUE X

CTX_SWITCH_RATE X

BYIF_UTIL X

BYIF_BIT_RATE X

BYIF_BANDWIDTH X

WEBSRV_IN_BYTE_RATE_C X

WEBSRV_OUT_BYTE_RATE_C X

WEBSRV_CONNECTION_ATTEMPTS_RATE_C X


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



37 / 44


Hyper-V Host

Hyper-V VM

WEBSRV_CURRENT_CONNECTIONS_C X

WEBSRV_HIT_RATE_C X

BYDBFILEGRP_ALLOCATED_FREE_SPACE_C X

BYDBFILEGRP_TOTAL_FREE_SPACE_C X

BYDBFILEGRP_LOG_ALLOCATED _FREE_SPACE_C

X

BYDBFILEGRP_ALLOCATED_USED

_SPACE_PCT_C

X

BYDBFILEGRP_TOTAL_USED_SPACE_PCT_C X

BYDBFILEGRP_LOG_ALLOCATED_USED_ SPACE_PCT_C

X

BYDB_DATA_ALLOCATED_SPACE_C X

BYDB_TOTAL_FREE_SPACE_PCT_C X

DB_QUERY_RESP_TIME_C X

DB_LOCK_RATE X

DB_LOCK_TIMEOUT_RATE_C X

DB_LOCK_WAIT_RATE_C X

DB_LOGON_RATE X

DB_DEADLOCK_RATE_C X

DB_ROWS_READ_RATE_C X

DB_ROWS_WRITTEN_RATE_C X

DB_SQL_COMPILATION_RATE_C X

DB_SQL_RECOMPILATION_RATE_C X

DB_TRAN_RATE X

DB_BUFFER_HIT_RATIO X

DB_TRANSACTION_ROLLBACKS_C X

BYIF_IN_BYTE_RATE X

BYIF_OUT_BYTE_RATE X

CLOUD_NAME X

CLUSTER_COMMIT_STATE_C X

CLUSTER_FAILOVER_TOLERANCE X

CPU_NUM X X

CPU_UTIL (VM SCOM Object) X

CPU_UTIL (Hyper-V Logical Processor SCOM Object)

X

DISK_FREE X

DISK_NUM X

DISK_READ_RATE X

DISK_SIZE X


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



38 / 44


Hyper-V Host

Hyper-V VM

DISK_TRANSFER_RATE X

DISK_USED_SPACE X X

DISK_USED_SPACE_PCT X

DISK_WRITE_RATE X

GM_NUM X

GM_ON_NUM X

HOST_NAME X

HOST_NUM X

MEM_CONSUMED X

MEM_DYNAMIC_ALLOCATION_C X

MEM_FREE X

MEM_LIMIT X

MEM_UTIL_COMMITTED_C X

NET_BYTE_RATE X

NETIF_NUM X

NET_IN_BYTE_RATE X

NET_OUT_BYTE_RATE X

TOTAL_REAL_MEM X X

VM_LAST_STATUS X

8.3 Entity Naming Conventions

SCOM managed entities are mapped to BCO ones according to their Display Name.

Exceptions to this rule are described in the next sections.

8.3.1 SCOM Lower-level entities

The BCO entity name is extracted from the Path or Fullname SCOM managed entity attributes, in case SCOM metrics refers to lower-level entities.

This applies for example to Disks, which SCOM models as first-class managed entities (Display Name is for example “C:”) but BCO treats them as metric subobjects assigned to the host system.

8.3.2 Hyper-V Root Partition

Every Hyper-V hypervisor hosts a particular virtual machine for management purposes, called root (or parent or host) partition. The root partition has the same name of the hypervisor system.

As traditional agents can be installed on this partition (such as SCOM Agent for Windows monitoring), metric clashing could possibly occur if the agent inside the root partition measures metrics that are also provided at the hypervisor level (i.e. CPU_UTIL).

In order to avoid such circumstances and clearly distinguish between the two concepts, BCO represents root partitions and hypervisors as distinct entities.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



39 / 44

To achieve this, the BCO name of the root (parent) partition is prefixed with a specific label (“Root:”). A prefix is also used for naming lookup: the lookup name is prefixed with the “hvrootpart:” label for this purpose.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



40 / 44

9 Appendix B. Lookup Fields

Moviri Integration for BCO connector uses standard BCO ETL lookup mechanism. One single entry is used as entity identifier: Lookup field = “DEFAULT”. The following table shows, for each supported entity, what information is used as lookup value field.

BCO Entity Type Lookup value field

System (Generic) hostname

Virtual Host hostname

Virtual Machine hostname

Database Instance hostname:instancename

Here below some lookup tables as example:


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



41 / 44

10 Appendix C. Object Relationships

The connector provides a set of object relationships that aims at organizing imported entities in BCO workspace according to the following rules.

10.1.1 Assignment of imported entities to a specified domain

The connector arranges the collected systems under a domain of choice.

Relationship Type: APP – SYS [identified by its data source name, DS_SYSNM], where APP is the domain of choice (as selected in the “Object Relationships” tab in the Run Configuration wizard)

Meaning: To group systems collected from the same data source

A hierarchy rule associated to the ETL is automatically created by BCO to process the Object-Relationship data.

Figure 20 – Hierarchy Rule

10.1.2 SQL Server Instances and Databases

The SQL Server instances are shown in the BCO tree as children of the host on which they are running (Figure 5).

Figure 5


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



42 / 44

In the above figure each host has one or more SQL Server instances.

Each SQL Server instance could have one or more Databases. The connector represents databases as subobject of their SQL Server instance.

The connector also imports, for each database, data about filegroups. Filegroups are represented within BCO as subobject of the SQL Server instances.

All the database space metrics are associated to the SQL Server instance. They have as subject the database name if they are related to the whole DB, while, if they are related to a specific filegroup of a database, they have a subobject composed by the database name and the filegroup name.

10.1.3 Hyper-V Clusters, Hosts and Virtual Machines

Hyper-V entities are organized according to the following relationships:

Hosting: represents the relation existing between an Hyper-V host and a Virtual Machine running on it

Containment: represents the relation existing between an Hyper-V Cluster and the contained Hyper-V host

An example of such relationships is presented in Figure 6.

Figure 6

In this particular example, the cluster system “Cluster04” contains a single Hyper-V system “hyperv-laptop” which is hosting three virtual machines (“Root:hyperv-laptop”, “WinSrv2008 – 3”, “WinSrv2008 – 4”). Furthermore, the standalone Hyper-V system “movsrv19” is hosting six virtual machines (“Mediaroom 2008”, “Media”, “RD”, “Root:movsrv19”, “WinSrv2008”, “WinSrv2008 – memdyn”).

A relation among the Hyper-V host and its root partition is also provided.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



43 / 44

11 Appendix D. Legal Notices

11.1 Warranty

Moviri S.p.A. makes no warranty of any kind with regard to this document, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Moviri S.p.A shall not be held liable for direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

11.2 Copyright Notices.

©Copyright 2010-2013 Moviri S.p.A, all rights reserved. No part of this document may be copied, reproduced, or translated to another language without the prior written consent of Moviri S.p.A. The information contained in this material is subject to change without notice.

11.3 Trademark Notices

BMC Software, Microsoft Corporation and the names of all their products referenced herein are registered trademarks of their respective owners.


Moviri SpA

HeadQuarter


20158 Milan IT

T: +39 02 49517001 – F: +39 02 70059905

Spear Tower



USA



44 / 44

* 445057*

Documents

Moviri Integration for BMC Capacity Optimization Microsoft ... · Now you have to click on System enter Operations Manager _, access to properties (by right click), then insert SCOM