vcenter Operations Management Pack for SCOM Installation and Configuration Guide

Transcription

1 vcenter Operations Management Pack for SCOM Installation and Configuration Guide This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see EN

2 vcenter Operations Management Pack for SCOM Installation and Configuration Guide You can find the most up-to-date technical documentation on the VMware Web site at: The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: Copyright 2013 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc Hillview Ave. Palo Alto, CA VMware, Inc.

3 Contents vcenter Operations Management Pack for SCOM Installation and Configuration Guide 5 Updated Information 5 1 Introduction to the Management Pack for SCOM 7 How the Management Pack for SCOM Creates Resources 7 How the Management Pack Retrieves Data 8 How the Management Pack Groups SCOM Entities 9 Management Pack for SCOM Dashboards 9 Installation and Configuration Requirements 11 2 Installing the Management Pack for SCOM 13 Install the Management Pack for SCOM in a Standalone Installation 13 Install the Management Pack for SCOM in a vapp Installation 14 Management Pack for SCOM Folders and Files 15 3 Configuring the Management Pack for SCOM 17 Overview of Configuration Steps 17 Add a Management Pack Instance 17 Install Management Pack for SCOM Dashboards in a Standalone Installation 19 Modifying the Default Database Queries 20 Modifying Management Pack for SCOM Properties 26 Security Considerations 28 4 Troubleshooting the Management Pack for SCOM 29 Troubleshooting a Management Pack for SCOM Instance 29 Validating Data 29 Viewing System Log Files 30 Metrics for Management Pack for SCOM Hyper-V Clusters 31 Resolving Common Problems 31 Index 33 VMware, Inc. 3

4 vcenter Operations Management Pack for SCOM Installation and Configuration Guide 4 VMware, Inc.

5 vcenter Operations Management Pack for SCOM Installation and Configuration Guide The vcenter Operations Management Pack for SCOM Installation and Configuration Guide describes how to install and configure Management Pack for SCOM for vcenter Operations Manager. Intended Audience This information is intended for anyone who needs to install or configure Management Pack for SCOM. Updated Information The Management Pack for SCOM Installation and Configuration Guide is updated with each release of the product or when necessary. This table provides the update history of the Management Pack for SCOM Installation and Configuration Guide. Revision EN Description Changed name of product to vcenter Operations Management Pack for SCOM. Added Management Pack for SCOM Dashboards, on page 9 Added Mapping SCOM Events to vcenter Operations Manager Events and Alerts, on page 24 Added Security Considerations, on page 28 Significantly updated list of views in Installation and Configuration Requirements, on page 11 EN Added Database Permission Requirements, on page 11. EN Updated the contents of the lib folder in Management Pack for SCOM Folders and Files, on page 15. Corrected the default value for toplevelresourcekinds in Modifying Management Pack for SCOM Properties, on page 26. EN Added SCOM Entity Mappings, on page 8. EN Added the Instance name text box to Add a Management Pack Instance, on page 17. EN Added MS SCOM 2012 support to Installation and Configuration Requirements, on page 11. EN Changed the product name to reflect the new licensing model for the 5.6 release. Added the open_source_license.txt file to Management Pack for SCOM Folders and Files, on page 15. EN EN Added the maxresourcekindlength property to Modifying Management Pack for SCOM Properties, on page 26. The MS SCOM Adapter Technical Note is now the Microsoft SCOM Adapter Installation and Configuration Guide. The MS SCOM Adapter Technical Note is the initial release of this document. VMware, Inc. 5

6 vcenter Operations Management Pack for SCOM Installation and Configuration Guide 6 VMware, Inc.

7 Introduction to the 1 Management Pack for SCOM The Management Pack for SCOM is an embedded adapter for vcenter Operations Manager. The management pack collects time-series metrics, resource availability information, and resource relationships from a System Center Operations Manager (SCOM) database. This chapter includes the following topics: How the Management Pack for SCOM Creates Resources, on page 7 How the Management Pack Retrieves Data, on page 8 How the Management Pack Groups SCOM Entities, on page 9 Management Pack for SCOM Dashboards, on page 9 Installation and Configuration Requirements, on page 11 How the Management Pack for SCOM Creates Resources Management Pack for SCOM can use auto discovery or manual discovery to create resources in the vcenter Operations Manager database. The resources that the Management Pack for SCOM creates represent SCOM entities. You enable or disable auto discovery when you create a management pack instance. Auto discovery is disabled by default. When auto discovery is enabled, the management pack instance uses the discoverysql query to discover and create resources and the relationshipssql query to update relationships among the resources. The properties file for your source database type contains default queries. When you disable auto discovery, you must use manual discovery to create resources. With manual discovery, the management pack instance returns a list of resources, and you select the resources to create. The management pack instance creates relationships only among resources that already exist in the database and resources that it finds through manual discovery. The relationships between the resources you import are visible in vcenter Operations Manager. Management Pack for SCOM Resource Identification When the Management Pack for SCOM creates resources, it uses certain resource identifiers. You specify resource identifiers when you use the vcenter Operations Manager API to reference resources. MS SCOM AdapterKind The AdapterKind for the Management Pack for SCOM is MS SCOM adapter and the identifier is MS_SCOM_ADAPTER. VMware, Inc. 7

8 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Management Pack for SCOM Instance ResourceKind The adapter instance ResourceKind for the Management Pack for SCOM is MP for SCOM and the identifier is MP for SCOM Adapter Instance. ResourceKinds for SCOM Entity Types ResourceKinds for the resources that the Management Pack for SCOM imports represent SCOM entity types. ResourceKind names match the associated SCOM entity type names in the SCOM database (ManagedType:TypeName). Resource names are based on the display names in the SCOM database (BaseManagedEntity:DisplayName). The resources that the Management Pack for SCOM imports have certain identifiers. Table 1 1. SCOM Resource Identifiers Key Part of Uniqueness Default Name (en) Description EntityId Yes SCOM Entity Id SCOM entity identifier in the MS SCOM database (BaseManagedEntity:BaseManagedEntityId). SCOMServer Yes SCOM Server SCOM server identifier. The value is usually a string representation of the configured MS SCOM database, for example, host-port/dbname. FullName No Entity FullName Full name of the entity in the SCOM database (BaseManagedEntity:FullName). SCOM Entity Mappings SCOM entities correspond to certain vcenter Operations Manager objects. Table 1 2. MS SCOM Entity Mappings SCOM Server Entity Object Instance Counter DisplayName TypeName vcenter Operations ManagerObject Metric group name Instance name Metric name Resource name ResourceKind How the Management Pack Retrieves Data The Management Pack for SCOM uses SQL queries to collect time series metrics, resource availability information, resource relationships from the source database, maintenance information, and events and alerts. The properties file for your source database type contains default queries. During each collection cycle, the Management Pack for SCOM runs a query to check the availability state of resources in the source database, a query to collect time series metrics, and a query to update resource relationships, in that order. The relationship query runs during the collection cycle only if you enable auto discovery for the Management Pack for SCOM instance. The management pack instance collects metrics during each collection cycle, regardless of the auto discovery setting. 8 VMware, Inc.

9 Chapter 1 Introduction to the Management Pack for SCOM How the Management Pack Groups SCOM Entities SCOM entities that are not configured as top level types appear as metric groups under the nearest top level parent entity. For example, if an entity named mydb of type Microsoft.SQLServer.Database is not configured as a top level type, it appears as an instanced group named Microsoft.SQLServer.Database:mydb. The Management Pack for SCOM assigns all metrics for mydb to the instanced group. If multiple levels of resources that are not top level appear under a top level resource, the Management Pack for SCOM creates groups within groups. The information that the relationshipssql query retrieves determines the group logic. You can use the toplevelresourcekinds property in the scom.properties file to configure SCOM entity types as top level ResourceKinds. Custom Groups for Microsoft Products The MS SCOM Resources tag shows custom groups for many Microsoft products. If a Management Pack for SCOM adapter discovers a new resource, the resource is automatically added to corresponding custom group. The following is a list of custom groups for Microsoft products. Active Directory Domain Services DHCP Servers DNS Servers Exchange Servers Web Servers (IIS) Hyper-V Hosts Hyper-V Virtual Machines SharePoint Servers SQL Servers TFS Servers Management Pack for SCOM Dashboards Dashboards provide the user interface you use to monitor and troubleshoot Management Pack for SCOM problems in vcenter Operations Manager. Table 1 3. Management Pack for SCOM Dashboards Dashboard SCOM MS SQL SCOM MS SQL CLUSTER Description Displays information about MS SQL server related resources in your environment, including database health, metric sparklines, alerts, and relationships. This dashboard is typically used to monitor the system to ensure that it is running smoothly. Displays a heatmap showing cluster health and availability, metric sparklines, and alerts. This dashboard is typically used to monitor behavior to ensure that the system is running smoothly. VMware, Inc. 9

10 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Table 1 3. Management Pack for SCOM Dashboards (Continued) Dashboard SCOM SQL SERVER ALERTS SCOM HYPER-V CLUSTER UTILIZATION SCOM HYPER-V HOST UTILIZATION SCOM HYPER-V VM UTILIZATION SCOM HYPER-V VM PERFORMANCE SCOM HYPER-V ALERTS SCOM MS EXCHANGE SCOM EXCHANGE ALERTS SCOM COMPUTER UTILIZATION SCOM COMPUTER PERFORMANCE SCOM ALERTS SCOM HYPER-V HEATMAPS Description Displays a list of alerts generated by on SQL Server related resources. You can select any of the alert items to display the Health Tree and Interesting Metrics for the selected server resource to help troubleshoot issues. Displays Top-N widgets for the key performance indicators CPU usage, memory usage, and net total KBPS. Select any instance to display a sparkline of the performance history. Use this dashboard to identify spikes in activity and troubleshoot potential issues. Displays Top-N widgets for the key performance indicators CPU usage, memory usage, and net total KBPS. Select any instance to display a sparkline of the performance history. Use this dashboard to identify spikes in activity and troubleshoot potential issues. Displays Top-N widgets for the key performance indicators CPU usage, memory usage, and net total KBPS. Select any instance to display a sparkline of the performance history. Use this dashboard to identify spikes in activity and troubleshoot potential issues. Displays Top-N widgets for the key performance indicators swap rate, read-write latency, used bandwidth, and disk queue length. You will primarily use this dashboard to troubleshoot ongoing, known performance issues. Displays a list of alerts generated by hypervisor related resources. You can select any of the alert items to display the Health Tree and Interesting Metrics for the selected hypervisor resource to help troubleshoot issues. Displays key performance indicators for an MS Exchange server, including Exchange CAS Availability, Exchange Mail Box Availability, Exchange Hub Transport Availability, and Exchange Database Availability Group Availability. You can select any of the resources to view its relationships and alerts to help troubleshoot any issues. Displays a list of alerts generated by Exchange related resources. You can select any of the alert items to display the Health Tree and Interesting Metrics for the selected Exchange server resource to help troubleshoot issues. Displays Top-N widgets for the key performance indicators CPU usage, memory usage, and net total KBPS. Select any instance to display a sparkline of the performance history. Use this dashboard to identify spikes in activity and troubleshoot potential issues. Displays Top-N widgets for the key performance indicators swap rate, read-write latency, used bandwidth, and disk queue length. You will primarily use this dashboard to troubleshoot ongoing, known performance issues. Displays a list of alerts generated by on a SCOM object. These alerts can be generated by vcenter Operations Manager or retrieved from SCOM. You can select any of the alert items to display the Health Tree and Interesting Metrics for the selected resource to help troubleshoot issues. Displays a heatmap showing memory usage metrics, and metric sparklines to show memory usage history for a selected metric in the heatmap. 10 VMware, Inc.

11 Chapter 1 Introduction to the Management Pack for SCOM Installation and Configuration Requirements Before you install the Management Pack for SCOM, verify that your system meets certain requirements. SCOM Compatibility The Management Pack for SCOM supports Microsoft SCOM 2007 SP1, Microsoft SCOM 2007 R2, and Microsoft SCOM 2012 SP1. Credential Requirements The Management Pack for SCOM requires the user name and password of a user account that can read the database that contains the source data. You use this user name and password when you create a credential for an Management Pack for SCOM instance. If you use Windows Integrated Security, you must provide the domain name, as well. Database Permission Requirements The Management Pack for SCOM requires the SELECT permission to collect data from the source database. The Management Pack for SCOM accesses certain views in the source database. Table 1 4. Source Database Views Source Type Category View Database General ManagedEntityGenericView ManagedType RelationshipGenericView RelationshipTypeview PerformanceDataAllView PerformanceCounterView Data Warehouse Events and Alerts Maintenance Mode Custom Relationships Selective Import General Events and Alerts Maintenance Mode AlertView MaintenanceModeView MTV_Microsoft$Windows$HyperV$VirtualMachine MTV_Computer RuleView ManagementPackView vmanagedentity vmanagedentitytype State.vStateRaw Relationship vrelationshiptype perf.vperfraw vperformanceruleinstance vperformancerule Alert.vAlert Event.vEvent vdisplaystring vmaintenancemode vmaintenancemodehistory VMware, Inc. 11

12 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Table 1 4. Source Database Views (Continued) Source Type Category View Custom Relationships Selective Import vmanagedentitytypeproperty vmanagedentitypropertyset vrule vmanagementpack Event.vEventRule More Software Requirements for Windows Integrated Security If you configure the Management Pack for SCOM to use the sqljdbc driver and you use Windows Integrated Security, you must copy the sqljdbc_auth.dll file to the vcenter-ops/common/bin folder. Because a DLL file is required, you must install the Management Pack for SCOM on a Windows system. You must also configure the vcenter Operations Manager collector to run under an impersonated user account. For more information about using Windows Integrated Security with the Management Pack for SCOM, contact VMware technical support. NOTE The Management Pack for SCOM uses the jtds driver by default. Because the jtds driver does not require a DLL file, you can install the Management Pack for SCOM on a Linux system if you use the default driver. 12 VMware, Inc.

13 Installing the 2 Management Pack for SCOM How you install the Management Pack for SCOM depends on whether you have a vcenter Operations Manager Standalone or vapp installation. NOTE If you have a previous version of the Management Pack for SCOM, contact VMware technical support for information about installing a new version. This chapter includes the following topics: Install the Management Pack for SCOM in a Standalone Installation, on page 13 Install the Management Pack for SCOM in a vapp Installation, on page 14 Management Pack for SCOM Folders and Files, on page 15 Install the Management Pack for SCOM in a Standalone Installation If you have a standalone installation, you install the Management Pack for SCOM by extracting installation files from a TGZ file and running an installation utility. Prerequisites Download the TGZ file if you have not already done so. 1 Go to 2 Select the Cloud Management Marketplace tab. 3 Click the link for vcenter Operations Management Packs. 4 Use the navigation arrows to locate and click the link for Management Pack for SCOM. 5 Select the Resources tab. 6 Click the link to download the TGZ file. Procedure 1 Open the TGZ file and extract the TAR file to a temporary folder on your vcenter Operations Manager server. 2 In the temporary folder, open the TAR file and extract and run the installer for your operating system platform. 3 Log in to the Custom user interface as an administrator. 4 Select Admin > Support. VMware, Inc. 13

14 vcenter Operations Management Pack for SCOM Installation and Configuration Guide 5 On the Info tab, find the Adapters Info pane and click the Describe icon ( ). The Describe icon is located at the top right of the Adapters Info pane. 6 Click Yes to start the describe process and click OK. The Custom user interface finds the adapter files, gathers information about the abilities of the adapter, and updates the user interface with information about the adapter. If you have remote collectors, it installs the adapter on the remote collectors. The describe process might take several minutes. When the describe process is finished, the adapter appears in the Adapters Info pane. The build number is in the Adapter Version column. 7 Verify that the build number in the Adapter Version column for the adapter matches the build number in the TGZ file that you downloaded. The installer creates the msscom_adapter3 folder and msscom_adapter3.jar file under the vcenterops/user/plugins/inbound folder. Install the Management Pack for SCOM in a vapp Installation If you have a vapp installation, you install the Management Pack for SCOM from a PAK file. Prerequisites Download the PAK file if you have not already done so. 1 Go to 2 Select the Cloud Management Marketplace tab. 3 Click the link for vcenter Operations Management Packs. 4 Use the navigation arrows to locate and click the link for Management Pack for SCOM. 5 Click the Try button to download the installation PAK file. Procedure 1 Save the PAK file in a temporary folder. 2 Log in to the Admin user interface as the admin user. For example: 3 On the Update tab, click Browse to locate the temporary folder and select the PAK file. 4 Click Update and click OK to confirm the update. The Admin user interface uploads the PAK file. The upload might take several minutes. 5 Read and accept the EULA and click OK. 6 Click OK to confirm and start the update process. The update might take several minutes. Status information appears on the Update tab when the update is finished. 7 Log in to the Custom user interface as an administrator. For example: 8 Select Admin > Support. 9 On the Info tab, find the Adapters Info pane and click the Describe icon ( ). The Describe icon is located at the top right of the Adapters Info pane. 14 VMware, Inc.

15 Chapter 2 Installing the Management Pack for SCOM 10 Click Yes to start the describe process and click OK. The Custom user interface finds the adapter files, gathers information about the abilities of the adapter, and updates the user interface with information about the adapter. The describe process might take several minutes. When the describe process is finished, the adapter appears in the Adapters Info pane. The build number is in the Adapter Version column. 11 Verify that the build number in the Adapter Version column for the adapter matches the build number in the PAK file that you uploaded. The installation process creates the msscom_adapter3 folder and msscom_adapter3.jar file under the vcenterops/user/plugins/inbound folder. Management Pack for SCOM Folders and Files The management pack installation folder, vcenter-ops/user/plugins/inbound/msscom_adapter3, contains several subfolders and files. Table 2 1. Management Pack for SCOM Folders and Files Folder File Description conf describe.xml Describes the supported database for the source table. conf/scripts history.txt scom.properties sql_db.properties sql_dw.properties version.txt pre-install.bat pre-install.sh MSSCOMInstall.bat MSSCOMInstall.sh MSSCOMPostInstall.bat MSSCOMPostInstall.sh post-install.bat post-install.sh Describes the changes in each management pack version. Contains database settings for the management pack. Contains queries that the management pack uses to retrieve data from a source database of type Database. The default queries include discoverysql, relationshipssql2007, relationshipssql2012, availabilitysql which is empty by default, maincollectsql, maincollectselectivesql, eventssql, eventsselectivesql, maintenancesql, hypervvmdetailssql, and computerdetailssql. Contains queries that the management pack uses to retrieve data from a source database of type Data warehouse. The default queries includediscoverysql, relationshipssql, availabilitysql which is empty by default, maincollectsql, maincollectselectivesql, eventssql, eventsselectivesql, maintenancesql, hypervvmdetailssql, and computerdetailssql. Contains information about the management pack version The pre-install script is empty by default. Standalone installation scripts. Scripts to be run after standalone installation to import the standard set of dashboards Scripts run automatically to import the standard set of dashboards to a vapp installation VMware, Inc. 15

16 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Table 2 1. Management Pack for SCOM Folders and Files (Continued) Folder File Description open_source_license.txt Open source license file conf/dashboards dashboards.xml Dashboard configuration files lib OSS library files: jtds jar Non-OSS library files: sqljdbc.jar Database driver files. work lastcollect.properties Contains the last collection time, in milliseconds. The adapter instance creates this file. categories.properties blackandwhitelists_sample.propert ies Contains properties with a tag value as a property name and a comma separated list of ResourceKinds as a property value. A sample file that contains black lists and white lists of management packs and performance groups. 16 VMware, Inc.

17 Configuring the 3 Management Pack for SCOM To configure the Management Pack for SCOM, you must create a management pack instance and credential. You can optionally modify the default database queries and change database query properties to customize management pack operation. This chapter includes the following topics: Overview of Configuration Steps, on page 17 Add a Management Pack Instance, on page 17 Install Management Pack for SCOM Dashboards in a Standalone Installation, on page 19 Modifying the Default Database Queries, on page 20 Modifying Management Pack for SCOM Properties, on page 26 Security Considerations, on page 28 Overview of Configuration Steps Configuring the Management Pack for SCOM involves several steps. 1 Create one or more management pack instances and credentials. See Add a Management Pack Instance, on page (Optional) Modify the default database queries to collect the specific data that you need. See Modifying the Default Database Queries, on page (Optional) Modify database query properties to customize management pack operation. See Modifying Management Pack for SCOM Properties, on page 26. Add a Management Pack Instance You must create a Management Pack for SCOM instance. The management pack instance defines the management pack type, describes how to connect to the source database, and specifies the source database type. You can create multiple management pack instances, but you cannot assign different queries to each instance. All management pack instances that have the Database source database type use the queries in the sql_db.properties file. All management pack instances that have the Data warehouse source database type use the queries in the sql_dw.properties file. Prerequisites Install the Management Pack for SCOM. See Chapter 2, Installing the Management Pack for SCOM, on page 13. VMware, Inc. 17

18 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Create a credential, or, if you plan to create a credential when you define the management pack instance, become familiar with creating credentials. See Add a Credential, on page 19. Procedure 1 Log in to the Custom user interface as an administrator. 2 Select Environment > Configuration > Adapter Instances. 3 Select the collector to use from the Collector drop-down menu. Unless you added additional collectors, the only available collector is vcenter Operations Server. You can change the name of this collector when you install the standalone version. 4 Select MP for SCOM from the Adapter Kind drop-down menu. 5 Click the Add New Adapter Instance icon. 6 Type a name for the adapter in the Adapter Instance Name text box. 7 Configure how the adapter instance connects to the source database. Field Database host Database port Instance name Failover host Database source Database name Action Type the host name or IP address of the database host. Type the port to use to connect to the database. If you specified a named instance in the Instance Name text box, the adapter ignores this port number. Type the name of the SQL Server instance. IMPORTANT Leave this text box blank if the SQL Server instance is the unnamed default instance (usually MSSQLSERVER). Type the host name or IP address of a failover database server. Select the schema to use to connect to the MS SCOM database. The adapter instance uses the queries in the properties file that corresponds to the schema that you select. Adapter instances that have the Database source database type use the queries in the sql_db.properties file. Adapter instances that have the Data warehouse source database type use the queries in the sql_dw.properties file. Type the name of the database that contains the source data. 8 Select the time zone of the source database host from the Timezone drop-down menu. The adapter instance uses this value for time-series metric time stamps. vcenter Operations Manager adjusts the time stamps so that they correspond to the time stamps in the vcenter Operations Manager database. 9 Select true or false from the Auto Discovery drop-down menu to enable or disable auto-discovery. If you enable auto discovery, the adapter instance discovers new resources and creates the resources for you. If you disable auto discovery, you must discover resources manually. You might want to disable auto discovery to limit the number of resources that the adapter instance creates. 10 Select the credential to use to sign on to the data source from the Credential drop-down menu, or click Add to add a new credential. 11 (Optional) Click Test to test the adapter instance. 12 Click OK to save your configuration. What to do next If you disabled auto discovery, use the manual discovery process to discover resources. For information about using manual discovery, see the online help. 18 VMware, Inc.

19 Chapter 3 Configuring the Management Pack for SCOM Add a Credential A Management Pack for SCOM instance requires a user name and password to connect to the source database. You use this user name and password to create a credential for the management pack instance. You can add the credential before you create the adapter instance and select the correct credential when you define the adapter instance, or you can add the credential when you define the adapter instance. NOTE If you use Windows Integrated Security, you need to provide the domain name, as well. Prerequisites Install the Management Pack for SCOM. See Chapter 2, Installing the Management Pack for SCOM, on page 13. Procedure 1 Log in to the Custom user interface as an administrator. 2 Select Environment > Configuration > Credentials. 3 Select MP for SCOM from the Adapter Kind drop-down menu. 4 Select Database Credentials from the Credential Kind drop-down menu. 5 At the top of the list of credentials, next to Action, click Add. 6 Type a unique name for the credential instance in the Instance name text box. 7 Type the user name and password combination in the User name and Password text boxes. 8 Select the type of authentication to use from the Database Authentication drop-down menu. 9 (Optional) If you selected the Windows Authentication authentication type, type the name of the domain to which the user belongs in the Windows Domain text box. 10 Click OK to add the credential for the adapter kind. The credential appears in the list in the Manage Credentials window. Install Management Pack for SCOM Dashboards in a Standalone Installation Management Pack for SCOM dashboards load automatically when deployed to a vapp. For a standalone installation, you can import the dashboards manually using a batch file or shell script. Prerequisites Install Management Pack for SCOM as described in Install the Management Pack for SCOM in a Standalone Installation, on page 13. Procedure u Navigate to vcenter-ops/user/plugins/inbound/msscom_adapter3/conf/scripts and run the appropriate script file (MSSCOMPostInstall.bat for Windows, MSSCOMPostInstall.sh for Linux). VMware, Inc. 19

20 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Modifying the Default Database Queries Management Pack for SCOM uses SQL queries to collect data and discover resources. The sql_db.properties file contains the default queries for the Database source database type and the sql_dw.properties file contains the default queries for the Data warehouse source database type. Both properties files are in the conf folder. You can modify the default queries, but each query must return a result that contains certain columns. After you modify any queries, stop and restart collection for Management Pack for SCOM. NOTE In a vapp installation, you modify the properties files in the conf folder on the Analytics virtual machine. maincollectsql Query Columns The maincollectsql query returns the list of metrics collected in the SCOM database since the last Management Pack for SCOM collect call. The result of the maincollectsql query must include these columns. Table 3 1. maincollectsql Query Columns Column DISPNAME ENTITYID RESKIND FULLNAME ATTR INST GRP TS VALUE Description Name of the resource that generated the metric. Entity ID of the resource that generated the metric. Resource kind of the resource that generated the metric. Full name of the resource that generated the metric. Metric name. Instance name. Group name. Time stamp of the metric. Value of the metric. The maincollectsql query must have two parameters to specify the time window to retrieve metrics, for example: (pdav.timesampled >? AND pdav.timesampled <=?) ORDER BY TS discoverysql Query Columns The discoverysql query returns a list of existing resources. The result of the discoverysql query must include these columns. Table 3 2. discoverysql Query Columns Column DISPNAME FULLNAME RESKIND ENTITYID Description Display name of the entity. The management pack uses this value as the resource name. Full name of the entity. The management pack stores this name as an informational identifier. Entity type name. The management pack uses the entity type as a resource kind key. Entity ID. The management pack uses this ID and the SCOM server ID to uniquely identify the resource. 20 VMware, Inc.

21 Chapter 3 Configuring the Management Pack for SCOM relationshipssql Query Columns The relationshipssql query returns pairs of resources that have parent-child relationships. The result of the relationshipssql query (whether for SCOM 2007 or SCOM 2012) must include these columns. Table 3 3. relationshipssql Query Columns Column SDISPNAME SENTITYID SFULLNAME SRESKIND TDISPNAME TENTITYID TFULLNAME TRESKIND Description Parent resource name. Parent resource entity ID. Parent resource full name. Parent resource resource kind. Child resource name. Child resource entity ID. Child resource full name. Child resource kind. Examples of Queries for the Database Source Database Type These are examples of queries for the Database source database type. Example maincollectsql Query for Database maincollectsql=select bme.displayname AS DISPNAME, bme.basemanagedentityid AS ENTITYID, mt.typename AS RESKIND, bme.fullname as FULLNAME, pc.countername AS ATTR, ps.perfmoninstancename AS INST, pc.objectname AS GRP, pdav.timesampled AS TS, pdav.samplevalue AS VALUE FROM PerformanceDataAllView pdav INNER JOIN PerformanceSource ps ON ps.performancesourceinternalid = pdav.performancesourceinternalid INNER JOIN PerformanceCounter pc ON ps.performancecounterid = pc.performancecounterid INNER JOIN BaseManagedEntity bme ON ps.basemanagedentityid = bme.basemanagedentityid INNER JOIN ManagedType mt on mt.managedtypeid=bme.basemanagedtypeid WHERE (bme.path IS NOT NULL) AND (bme.isdeleted = 0) AND (bme.ismanaged = 1) AND (pdav.timesampled >? AND pdav.timesampled <=?) ORDER BY TS Example discoverysql Query for Database discoverysql=select DISTINCT bme.displayname AS DISPNAME, bme.fullname as FULLNAME, bme.path AS RESPATH, mt.typename AS RESKIND, bme.basemanagedentityid AS ENTITYID FROM BaseManagedEntity bme inner join ManagedType mt on mt.managedtypeid=bme.basemanagedtypeid WHERE bme.isdeleted = 0 AND bme.ismanaged = 1 ORDER BY mt.typename, bme.displayname Example relationshipssql2007 Query for Database SELECT distinct se.displayname AS SDISPNAME, se.id AS SENTITYID, se.fullname AS SFULLNAME, smt.name AS SRESKIND, se.healthstate AS STATE, te.displayname TDISPNAME, te.id AS TENTITYID, te.fullname AS TFULLNAME, tmt.name AS TRESKIND FROM ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) se INNER JOIN ManagedTypeView smt ON smt.id = se.monitoringclassid) VMware, Inc. 21

22 vcenter Operations Management Pack for SCOM Installation and Configuration Guide LEFT JOIN ((RelationshipGenericView r INNER JOIN RelationshipTypeView rt ON r.id = rt.id and rt.name like '%Hosts%') INNER JOIN ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) te INNER JOIN ManagedTypeView tmt ON tmt.id = te.monitoringclassid ) ON te.id = r.targetmonitoringobjectid) ON se.id = r.sourcemonitoringobjectid UNION ALL SELECT distinct se.displayname AS SDISPNAME, se.id AS SENTITYID, se.fullname AS SFULLNAME, smt.name AS SRESKIND, se.healthstate AS STATE, te.displayname TDISPNAME, te.id AS TENTITYID, te.fullname AS TFULLNAME, tmt.name AS TRESKIND FROM ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) se INNER JOIN ManagedTypeView smt ON smt.id = se.monitoringclassid) LEFT JOIN ((RelationshipGenericView r INNER JOIN RelationshipTypeView rt ON r.id = rt.id and rt.name like '%Contains%') INNER JOIN ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) te INNER JOIN ManagedTypeView tmt ON tmt.id = te.monitoringclassid ) ON te.id = r.targetmonitoringobjectid) ON se.id = r.sourcemonitoringobjectid WHERE smt.name LIKE '%Microsoft.Windows.Cluster%' Example relationshipssql2012 Query for Database SELECT distinct se.displayname AS SDISPNAME, se.id AS SENTITYID, se.fullname AS SFULLNAME, smt.name AS SRESKIND, se.healthstate AS STATE, te.displayname TDISPNAME, te.id AS TENTITYID, te.fullname AS TFULLNAME, tmt.name AS TRESKIND FROM ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) se INNER JOIN ManagedTypeView smt ON smt.id = se.monitoringclassid) LEFT JOIN ((RelationshipGenericView r INNER JOIN RelationshipTypeView rt ON r.relationshipid = rt.id and rt.name like '%Hosts%') INNER JOIN ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) te INNER JOIN ManagedTypeView tmt ON tmt.id = te.monitoringclassid ) ON te.id = r.targetobjectid) ON se.id = r.sourceobjectid UNION ALL SELECT distinct se.displayname AS SDISPNAME, se.id AS SENTITYID, se.fullname AS SFULLNAME, smt.name AS SRESKIND, se.healthstate AS STATE, te.displayname TDISPNAME, te.id AS TENTITYID, te.fullname AS TFULLNAME, tmt.name AS TRESKIND FROM ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) se INNER JOIN ManagedTypeView smt ON smt.id = se.monitoringclassid) LEFT JOIN ((RelationshipGenericView r INNER JOIN RelationshipTypeView rt ON r.relationshipid = rt.id and rt.name like '%Contains%') INNER JOIN ((Select * From ManagedEntityGenericView Where Id = TypedManagedEntityId ) te INNER JOIN ManagedTypeView tmt ON tmt.id = te.monitoringclassid ) ON te.id = r.targetobjectid) ON se.id = r.sourceobjectid WHERE smt.name like '%Microsoft.Windows.Cluster%' Examples of Queries for the Data Warehouse Database Type These are examples of queries for the Data warehouse source database type. NOTE There is no default availabilitysql query for the Data warehouse source database type. 22 VMware, Inc.

23 Chapter 3 Configuring the Management Pack for SCOM Example maincollectsql Query for Data Warehouse maincollectsql=select me.managedentityguid AS ENTITYID, me.fullname AS FULLNAME, me.displayname AS DISPNAME, mt.managedentitytypesystemname AS RESKIND, pru.objectname AS GRP, pri.instancename AS INST, pru.countername AS ATTR, pr.datetime AS TS, pr.samplevalue AS VALUE FROM perf.vperfraw as pr WITH (NOLOCK) INNER JOIN vmanagedentity me WITH (NOLOCK) on me.managedentityrowid = pr.managedentityrowid INNER JOIN vmanagedentitytype mt on me.managedentitytyperowid=mt.managedentitytyperowid INNER JOIN vperformanceruleinstance pri WITH (NOLOCK) on pri.performanceruleinstancerowid = pr.performanceruleinstancerowid INNER JOIN vperformancerule pru WITH (NOLOCK) on pru.rulerowid = pri.rulerowid WHERE (pr.datetime >? AND pr.datetime <=?) ORDER BY TS Example discoverysql Query for Data Warehouse discoverysql=select DISTINCT mt.managedentitytypesystemname AS RESKIND, me.managedentityguid AS ENTITYID, me.fullname AS FULLNAME, me.displayname AS DISPNAME FROM vmanagedentity me INNER JOIN vmanagedentitytype mt on me.managedentitytyperowid=mt.managedentitytyperowid Example relationshipssql Query for Data Warehouse relationshipssql=select distinct sst.newhealthstate AS STATE, se.displayname AS SDISPNAME, se.managedentityguid AS SENTITYID, se.fullname AS SFULLNAME, smt.managedentitytypesystemname AS SRESKIND, te.displayname TDISPNAME, te.managedentityguid AS TENTITYID, te.fullname AS TFULLNAME, tmt.managedentitytypesystemname AS TRESKIND FROM (vmanagedentity se INNER JOIN vmanagedentitytype smt ON smt.managedentitytyperowid = se.managedentitytyperowid INNER JOIN State.vStateRaw sst ON sst.managedentitymonitorrowid = se.managedentityrowid INNER JOIN ((vrelationship r INNER JOIN vrelationshipproperty rp ON r.relationshiprowid = rp.relationshiprowid AND rp.todatetime IS NULL INNER JOIN vrelationshiptype rt ON r.relationshiptyperowid = rt.relationshiptyperowid and rt.relationshiptypesystemname like '%Hosts%') INNER JOIN (vmanagedentity te INNER JOIN vmanagedentitytype tmt ON tmt.managedentitytyperowid = te.managedentitytyperowid ) ON te.managedentityrowid = r.targetmanagedentityrowid) ON se.managedentityrowid = r.sourcemanagedentityrowid) INNER JOIN (SELECT MAX(DateTime) AS MaxDateTime, ManagedEntityMonitorRowID FROM State.vStateRaw group by ManagedEntityMonitorRowID) sst2 ON sst.datetime = sst2.maxdatetime AND sst.managedentitymonitorrowid = sst2.managedentitymonitorrowid UNION ALL SELECT distinct sst.newhealthstate AS STATE, se.displayname AS SDISPNAME, se.managedentityguid AS SENTITYID, se.fullname AS SFULLNAME, smt.managedentitytypesystemname AS SRESKIND, VMware, Inc. 23

24 vcenter Operations Management Pack for SCOM Installation and Configuration Guide te.displayname TDISPNAME, te.managedentityguid AS TENTITYID, te.fullname AS TFULLNAME, tmt.managedentitytypesystemname AS TRESKIND FROM (vmanagedentity se INNER JOIN vmanagedentitytype smt ON smt.managedentitytyperowid = se.managedentitytyperowid INNER JOIN State.vStateRaw sst ON sst.managedentitymonitorrowid = se.managedentityrowid INNER JOIN ((vrelationship r INNER JOIN vrelationshipproperty rp ON r.relationshiprowid = rp.relationshiprowid AND rp.todatetime IS NULL INNER JOIN vrelationshiptype rt ON r.relationshiptyperowid = rt.relationshiptyperowid and rt.relationshiptypesystemname like '%Contains%') INNER JOIN (vmanagedentity te INNER JOIN vmanagedentitytype tmt ON tmt.managedentitytyperowid = te.managedentitytyperowid ) ON te.managedentityrowid = r.targetmanagedentityrowid) ON se.managedentityrowid = r.sourcemanagedentityrowid) INNER JOIN (SELECT MAX(DateTime) AS MaxDateTime, ManagedEntityMonitorRowID FROM State.vStateRaw group by ManagedEntityMonitorRowID) sst2 ON sst.datetime = sst2.maxdatetime AND sst.managedentitymonitorrowid = sst2.managedentitymonitorrowid WHERE smt.managedentitytypesystemname like '%Microsoft.Windows.Cluster%' Mapping SCOM Events to vcenter Operations Manager Events and Alerts If the addscomeventsalerts property is true, the Management Pack for SCOM sends queries to the database or data warehouse and retrieves events and alerts. Events are supported for a SCOM data warehouse only. Alerts are available for both a SCOM database and a SCOM data warehouse. vcenter Operations Manager creates alarms and alerts based on events and alerts from the SCOM environment. All SCOM events are mapped to notification events as shown in the following table. Table 3 4. SCOM Events Mapping SCOM Event Level information undefined warning critical error audit vcenter Operations Manager Event Level info none warning critical critical All SCOM alerts are mapped to notification events as shown in the following table. Table 3 5. SCOM Alerts Mapping SCOM Alert Severity information warning critical vcenter Operations Manager Event Level info warning critical 24 VMware, Inc.

25 Chapter 3 Configuring the Management Pack for SCOM Use the following query to import alerts from a SCOM database. SELECT av.name AS EVENT_NAME, av.description AS EVENT_DESCRIPTION, av.monitoringobjectid AS ENTITYID, av.monitoringobjectdisplayname AS DISPNAME, v.monitoringobjectfullname AS FULLNAME, av.monitoringruleid, av.severity AS EVENT_LEVEL, av.timeraised AS TS, mtv.name AS RESKIND FROM AlertView av INNER JOIN ManagedTypeView mtv ON mtv.id = av.monitoringclassid WHERE av.languagecode = 'ENU' AND MonitoringObjectName IS NOT NULL AND MonitoringObjectPath IS NOT NULL AND mtv.name IN (%s) AND av.timeraised <? AND av.timeraised >=? Use the following query to import events and alerts from a SCOM data warehouse. SELECT * FROM (SELECT av.alertname AS EVENT_NAME, av.alertdescription AS EVENT_DESCRIPTION, me.managedentityguid AS ENTITYID, me.displayname AS DISPNAME, me.fullname AS FULLNAME, mt.managedentitytypesystemname AS RESKIND, av.severity AS EVENT_LEVEL, av.raiseddatetime AS TS FROM Alert.vAlert av INNER JOIN vmanagedentity me ON me.managedentityrowid = av.managedentityrowid INNER JOIN vmanagedentitytype mt ON mt.managedentitytyperowid = me.managedentitytyperowid UNION SELECT DS.Name as EVENT_NAME, DS.Description as EVENT_DESCRIPTION, ME.ManagedEntityGuid as ENTITYID, ME.DisplayName as DISPNAME, ME.FullName as FULLNAME, MET.ManagedEntityTypeSystemName as RESKIND, (case when E.EventLevelId = 0 then 3 when (E.EventLevelId = 1 OR E.EventLevelId = 16) then 2 when E.EventLevelId = 2 then 1 when E.EventLevelId = 4 then 0 end) AS EVENT_LEVEL, E.DateTime as TS FROM Event.vEvent E INNER JOIN vmanagedentity ME on EventPublisherRowId = ME.ManagedEntityRowId INNER JOIN vmanagedentitytype MET on ME.ManagedEntityTypeRowId = MET.ManagedEntityTypeRowId INNER JOIN vdisplaystring DS on DS.DisplayStringRowId = E.EventDisplayNumber WHERE DS.LanguageCode like 'ENU') temp WHERE RESKIND in (%s) AND TS <? AND TS >\=? VMware, Inc. 25

26 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Modifying Management Pack for SCOM Properties The scom.properties file in the conf folder contains general settings that apply to all database queries. You can modify these queries to customize management pack operation. After you modify query properties, stop and restart collection for the Management Pack for SCOM. Table 3 6. scom.properties File Properties Property Description Default Value addscomeventsalerts blackandwhitelists createexternalrelationships generatedownalert jdbcdriver maxsendchunkinterval maxquerywindow minquerywindow Boolean. When you set the addscomeventsalerts property to true, the management pack sends queries to the database or data warehouse to retrieve events and alerts. For more information on configuring alerts and events, see Mapping SCOM Events to vcenter Operations Manager Events and Alerts, on page 24 This property provides the name of a file in the vcenterops/user/plugins/inbound/msscom_adapte r3/work directory that lists black and white lists used to allow selective import of SCOM metric data and events. Black lists identify management packs and performance objects that are not queried for metric information. White lists identify management packs and performance objects that are the only objects that are queried for metric information. Boolean. Set this value to true to enable relationship creation between SCOM and VMware objects. Boolean. Set this value to true to generate Resource Down alerts for resources that the management pack does not create. JDBC driver that the management pack uses to access the SCOM database. Valid values are jtds and sqljdbc. To use Windows Integrated Security with the sqljdbc driver, you must install Management Pack for SCOM on a Windows system, copy the sqljdbc_auth.dll file to the vcenter-ops/common/bin folder, and configure the collector to run under an impersonated user account. The jtds driver does not require a DLL file and you do not need to run the collector as a domain user to use Windows authentication. Maximum data buffering interval, in milliseconds. This property specifies how long the management pack keeps data to send when historic mode is enabled. Maximum trailing time, in minutes, from the current time to query. Minimum trailing time, in minutes, from the current time to query. false blank false true jtds (1 hour) VMware, Inc.

27 Chapter 3 Configuring the Management Pack for SCOM Table 3 6. scom.properties File Properties (Continued) Property Description Default Value nameprefix toplevelresourcekinds Resource name prefix for the resources that the management pack creates. Comma-delimited list of MS SCOM entity types that vcenter Operations Manager represents as separate resources. Entities of different types that belong to a subtree of a top-level entity become metric groups under the nearest top-level entity in the user interface. Entities that do not belong to defined top-level entity subtrees do not appear in the user interface. To have them appear in the UI, you must add their types, or the types of their direct or indirect parents, as top-level ResourceKinds. For information about adding top-level ResourceKinds, see Adding Top Level ResourceKinds, on page 27. null Microsoft.Windows.Computer,Micros oft.sqlserver.dbengine,microsoft.sq LServer.Agent,Microsoft.SQLServer.A nalysisservices,microsoft.sqlserver.d atabase,microsoft.sqlserver.reportin gservices,microsoft.windows.hyperv.virtualmachine,microsoft.windows. HyperV.ServerRole,Microsoft.Exchang e ClientAccessRole,Microsoft.Exch ange CommonRole,Microsoft.Exchang e HubTransportRole,Microsoft.Exc hange MailboxRole,Microsoft.Exchange Mailbox.DatabaseAvailabilityGro up,microsoft.windows.cluster,micros oft.windows.server.ad.site Adding Top Level ResourceKinds By default, the Management Pack for SCOM recognizes a default list of ResourceKinds. You can configure additional top level ResourceKinds. Prerequisites Install the Management Pack for SCOM. See Chapter 2, Installing the Management Pack for SCOM, on page 13. Procedure 1 Run one of the following two queries, depending on the type of storage. a b For a database, run the query SELECT Name FROM ManagedTypeView ORDER BY Name. For a data warehouse, run the query SELECT ManagedEntityTypeSystemName FROM vmanagedentitytype ORDER BY ManagedEntityTypeSystemName. The query returns all SCOM entities, their types, and identifiers. 2 Find the entity to add as a top level ResourceKind and make a note of the value in the RESKIND column. 3 Edit the scom.properties file to add the value from the RESKIND column to the comma separated list in the toplevelresourcekinds property. 4 Save your changes and close the scom.properties file. 5 Optionally, add the ResourceKind to the categories.properties file, assigning it to the category group Appliances, Applications, Operating Systems, Services, Servers, or Virtualization. 6 Stope and restart collecting for the Management Pack for SCOM instance. VMware, Inc. 27

28 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Security Considerations There are security issues that must be considered when installing the Management Pack for SCOM. vcenter Operations Manager administrators can install a variety of management packs. VMware creates some management packs, while others are written by third party developers. Although adapters execute independently, they execute within a common runtime environment in the vcenter Operations Manager collector host. Java language security protects adapters from interference with other adapters, but all execute within the common JRE process trust zone. You should only load and use management packs that you have obtained from a publisher you trust. You should verify the management pack's code integrity before loading into vcenter Operations Manager. You can verify the integrity of a management pack by generating an md5 or sha1 hash for the management pack's binary, and comparing it to the sha1 or md5 hash file accompanying the management pack binary. Although adapters execute independently, they can make configuration changes to the collector host or Java runtime environment that can affect the security of other adapters. For example, at installation time an adapter can modify the list of trusted certificates. During execution, an adapter can change the TLS/SSL certificate validation scheme, and thereby change how other adapters validate certificates. The vcenter Operations Manager system and collector hosts do not isolate adapters beyond the natural isolation provided by Java execution. The system trusts all adapters equally. Adapters are responsible for their own data security. When collecting data or making configuration changes to data sources, each adapter provides its own mechanisms and guarantees regarding the confidentiality, integrity, and authenticity of collected data. The Management Pack for SCOM adapter uses a unencrypted channel between the adapter and the Management Pack for SCOM database. You should use the Management Pack for SCOM adapter only over a trusted network and behind a corporate firewall. 28 VMware, Inc.

29 Troubleshooting the 4 Management Pack for SCOM Known troubleshooting information can help you diagnose and correct problems with the Management Pack for SCOM. This chapter includes the following topics: Troubleshooting a Management Pack for SCOM Instance, on page 29 Validating Data, on page 29 Viewing System Log Files, on page 30 Metrics for Management Pack for SCOM Hyper-V Clusters, on page 31 Resolving Common Problems, on page 31 Troubleshooting a Management Pack for SCOM Instance Perform these general troubleshooting tasks to diagnose and correct problems with a Management Pack for SCOM instance. 1 View the collection status and collection state for the management pack instance on the Environment Overview page in vcenter Operations Manager. For more information about viewing resources in the user interface, see the online help. 2 Validate the data that the Management Pack for SCOM instance retrieves. See Validating Data, on page Check the adapter and collector logs for errors. See Viewing System Log Files, on page 30. Validating Data You can use the Custom user interface to verify that the Management Pack for SCOM retrieves data correctly. Verify Resources and Metrics You can use the Custom user interface to verify that the Management Pack for SCOM creates resources and retrieves metrics correctly. Procedure 1 Select Environment > Environment Overview. 2 Verify that the expected resources appear on the Environment Overview page. 3 Select a resource that the Management Pack for SCOM created and click the Show Detail icon. VMware, Inc. 29

30 vcenter Operations Management Pack for SCOM Installation and Configuration Guide 4 Compare the metric values that the Management Pack for SCOM collected to the metric values in the source database. Verify Resource Relationships You can use the Custom user interface to verify that the Management Pack for SCOM creates resource relationships correctly. Procedure 1 Select Environment > Advanced > Resource Relationships. 2 In the Parent Selection pane, select a parent resource that the Management Pack for SCOM loaded. 3 Verify that the parent resource displays the child resources defined in the relationships table in the source database. What to do next If the Management Pack for SCOM cannot create resource relationships, see Management Pack Cannot Create Relationships, on page 32. Verify Resource Availability States You can use the Custom user interface to verify that the Management Pack for SCOM updates resource availability states correctly. Procedure 1 Select Environment > Environment Overview. 2 Select the Management Pack for SCOM instance to verify. 3 Verify that the Collection Status column for resources that have the Not Available state in the source database contains Resource Down. vcenter Operations Manager generates a Resource Down alert for resources in the source database that have the Not Available state. Viewing System Log Files You can view Management Pack for SCOM errors in the adapter and collector log files in vcenter Operations Manager. You can view adapter and collector log files in the user interface or in an external log viewer. Management Pack for SCOM log files are in the vcenter-ops/user/log/adapters/scomadapter folder. Collector log files are in the vcenter-ops/users/log folder. The logging level is set to ERROR by default. To troubleshoot issues, set the logging level to INFO. To view detailed messages, including micro steps, queries, and returned results, set the logging level to DEBUG. You can set the logging level for each class in the log4.properties file in the vcenterops/log/conf/collector folder, for example: log4.logger.com.integrien.adapter3.scom.scomadapter=debug NOTE If you set the logging level to DEBUG, log files can become large very quickly. Set the logging level to DEBUG only for short periods of time. For information about viewing log files and modifying logging levels, see the online help. 30 VMware, Inc.

31 Chapter 4 Troubleshooting the Management Pack for SCOM Management Pack for SCOM Classes The Management Pack for SCOM uses certain classes. Table 4 1. Management Pack for SCOM Classes Class com.integrien.adapter3.scom.scomadapter com.integrien.adapter3.scom.scomproperties com.integrien.adapter3.scom.util.dbutil com.integrien.adapter3.scom.util.scomutil Description Main adapter logic. Property file loader. Database utility class. General utility class. Metrics for Management Pack for SCOM Hyper-V Clusters Management Pack for SCOM collects metrics from Hyper-V clustered virtual machines and uses formulas to derive metrics for Hyper-V clusters. The Management pack for SCOM collects metrics from Hyper-V clustered virtual machines and uses formulas to derive Metrics for Hyper-V clusters. Table 4 2. Hyper-V Cluster Metrics Metric Key Metric Name Description ClusterMetrics % Processor Time % Processor Time Average processor time of all clustered virtual machines in the cluster ClusterMetrics PercentMemoryUsed PercentMemoryUsed Average percent of used memory of all clustered virtual machines in the cluster ClusterMetrics Pages/sec Pages/sec Total swap I/O rate in pages/sec of all clustered virtual machines in the cluster ClusterMetrics Network KBytes Total/sec ClusterMetrics Avg. Disk ms/transfer ClusterMetrics Current Disk Queue Length Network KBytes Total/sec Avg. Disk ms/transfer Current Disk Queue Length Total network throughput for of all clustered virtual machines in the cluster Average Disk I/O latency of all clustered virtual machines in the cluster Total disk queue length of all clustered virtual machines in the cluster Resolving Common Problems Follow recommended procedures when you resolve common problems. Management Pack Cannot Connect to the Source Database The Management Pack for SCOM instance cannot connect to the SCOM database. Problem vcenter Operations Manager returns an error when you click Test on the Add Adapter Instance window. Cause The management pack instance is misconfigured. VMware, Inc. 31

32 vcenter Operations Management Pack for SCOM Installation and Configuration Guide Solution Check the management pack instance and verify that the database connection parameters are configured correctly. Management Pack Cannot Create Relationships Management Pack for SCOM cannot create resource relationships in vcenter Operations Manager. Problem Resource relationships are not updated in the Custom user interface. Cause The relationshipssql2007 or relationshipssql2012 select statement in the properties for your source database type is incorrect or the management pack instance is misconfigured. NOTE Management Pack for SCOM can create a relationship between a SCOM Computer and a SCOM Hyper-V virtual machine only in SCOM This option is not available in SCOM Solution 1 Verify that the fields in the relationshipssql2007 or relationshipssql2012 select statement match the field names in the source relationship table. 2 Check the management pack instance and verify that the database connection parameters are configured correctly. 32 VMware, Inc.

33 Index A adapter instances 17 adapter classes 31 alerts, mapping 24 audience information 5 C common problems and solutions 31 configuration steps 17 credentials 19 Custom Groups for MS Products 9 D database queries 20 database connection problems 31 discoverysql query 20 E events, mapping 24 S sample queries 21, 22 SCOM entity mappings 8 scom.properties file 26 security 28 system requirements 11 T top-level resource kinds 27 troubleshooting steps 29 U updated information 5 V validating data 29 verifying the adapter 29, 30 G grouping MS SCOM entities 9 H Hyper-V Cluster metrics 31 I installation files 15 installation steps 13 installing the adapter 13, 14 introduction 7 L log files 30 M maincollectsql query 20 metrics 31 R relationshpssql query 21 resource identifiers 7 resource relationship problems 32 resources 7 retrieving data 8 VMware, Inc. 33

34 vcenter Operations Management Pack for SCOM Installation and Configuration Guide 34 VMware, Inc.