You are browsing the archive for manuals.

Avatar of alkin

by alkin

OpsMgr Management pack APC ISX Central Integration Management Pack

1:54 pm in Uncategorized by alkin

This week I had to implement an APC management pack at a customer site and I will explain how to get it working. This customer is using APC to monitor and configure his Uninterruptible power supply (UPS) infrastructure.

The APC InfraStruXure (ISX) Central is a network appliance that collects data from, and monitors status of, devices that provide data-center-critical infrastructure.
The ISX Central Integration Management pack for Microsoft’s System Center Operations Manager 2007 provides a tight integration between the physical infrastructure space for whichISX Central provides unprecedented visibility and control and the systems infrastructure space for which OpsMgr provides the same type of solution.

The Management Pack integrates ISX Central through the new web services interface, available starting with version 5.1 of ISX Central. Make sure you install the ISX Central with a least version 5.1 that you can download from here http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SFISXC511 

 

To install the Management Pack, install the .msi package downloaded from the APC Web site (http://www.apc.com/tools/download) into an appropriate directory. The installation package consists of four
files: this document, the sealed Management Pack (.mp), the optional Overrides Management Pack
(.xml), and the registration utility (.exe).

 

Steps to configure the APC management pack:

  1. Configure your ISX Central
  2. Import your APC ISX management pack
  3. Run the ISX Central Registration tool
  4. Configure the run-as account

 

The registration utility is a tool that provides a user interface to set certain registry keys that are used by the Management Pack to perform the initial discovery of the InfraStruXure Central servers.

Start the ISX Central Registration tool that you can find in the management pack download folder. To add a new ISX Central registration, click Add. You will be asked to provide a name and FQDN for the ISX Central. The name can be any descriptive name.

image

The FQDN should be the IP address or FQDN of the ISX Central. Do not use a full URL here. The registry is updated immediately.

image

Look in the registry.

All registry changes are made in the key:
HKEY_LOCAL_MACHINE\Software\APC\ MsScOpsMgrMpForIsxc
• The registered names appear as the REG_SZ values Name0…Name<n>
• The registered FQDNs appear as the REG_SZ values

image

Create a run as account and associate it with the run-as profile. O

image

Click next

image

image

Click New which starts the Create Run As Account Wizard and opens the General Properties page

image

create a new run as account.

image

Click Next

image

The Run As account should be created as a Simple Authentication Run As Account. Simple Authentication – any generic user name and password combination, for example, Web form, SQL authentication, or anything else that accepts user name and password.

image 

The username and password should have access to the ISX Central.

image

“More secure” means that when you associate the Run As account with a Run As profile, you have to provide the specific computer names that you want the Run As credentials distributed to. By positively identifying the destination computers, you can prevent the spoofing scenario that was described before.

image

image

In the This Run As Account will be used to manage the following objects area select All targeted objects

image

image

image

On the Distribution tab, in the Selected computers: area, click Add to open the Computer Search tool; Search by computer name (Default), then type in the computer name. The computer name is the computer name where you have run the ISX Central Registration tool.

image 

image

Enable the “The InfraStruXure Central Registration discovery” discovery. This discovery targets computers running Windows Server (i.e. the Microsoft.Windows.Server.Computer Operations Manager class) and looks for the registry keys that are written by the registration utility. This rule is disabled by default, which renders the Management Pack dormant on import.

image

Enable the override for the computer object where the you have run the ISX Central Registration tool. Don’t forget to enable the “Agent Proxy” option under Agent Properties > Security.

image

After a while the ISX Central  will be discovered and you will be able to monitor your UPS infrastructure!!

image

Hope this helps,

Alexandre Verkinderen

Avatar of alkin

by alkin

Opsmgr Performance problems with healthservice on agents

8:59 pm in Uncategorized by alkin

On some occasions the scom agent can cause a lot of performance issues on the servers. Here I will describe some steps I take when I have performance problems and in most of the cases it works for me.

The first thing you should do is to configure the antivirus exclusions for opsmgr. Have a look at Kevin Holman’s blogpost Antivirus Exclusions for MOM and OpsMgr on how to do this. Configuring anti virus exlusions will help you gain some performance.

This is a screenshot of the performance of my cpu before the anti virus exclusions:

clip_image002[1]

 

And this one is after the anti virus exclusions:

clip_image002[3]

 

The second thing is to have a look at the healthservice.exe. We’ve created a collection performance rule in the previous post to collect the processor time % of the healthservice. If the healthservice is consuming more than 15 a 20 % of your cpu you have a problem . In my case I  had huge performance problems due to the healthservice.exe that was taking all the processor time. My healthservices.exe was taking about 50 to 60 % with peaks to 100% on my agents….You can imagine the reaction of my client….he was not very happy.

Performance view of my healthservice.exe on one of my agents:

clip_image001

So I did some tests, installed all the necessary hotfixes, deleted the healthservice cache, exception of programfiles\scom\ for the antivirus etc etc. But with no results.

So I tought it was WMI and did the following steps to rebuild the wmi:

· Net Stop WinMgmt

· Ren %WinDir%\System32\Wbem\Repository %WinDir%\System32\Wbem\OldRepository

· Net Start WinMgmt

Still no success, still had performance troubles. I contacted one of our company architects who send me a repairwmi.cmd “program” he developed . It will recompile all the mofiles, re-register all the dll’s, exe’s etc.

Steps to take:

1. Copy the content of the repairwmi.cmd to the %WinDir%\System32\Wbem\ folder

2. Run the repairwmi.cmd

3. Stop the opsmgr healthservice

4. Delete the healthservice cache

5. Start the opsmgr healthservice

And voila! All my performance problems where gone!!

clip_image002

clip_image003

clip_image004

clip_image005

clip_image006

 

As you can see this reduced drastically the processor time % of the healthservice!

 

Hope this helps,

Alexandre Verkinderen

Avatar of alkin

by alkin

Opsmgr DB Create wizard System.InvalidOperationException

7:19 pm in Uncategorized by alkin

Today I wanted to install my OperationsmanagerDB on my SQL cluster 2005 SP2 actif-passive.

So I started the DBCreatewizard.exe and I got a very strange error mentioning something about

 

Severity: Error Message: Database creation failed. The database might have been incompletly created or modified. System.InvalidOperationException: An error occurred while trying to create the database on your SQL Server. Check your logs for more information. at Microsoft.EnterpriseManagement.Setup.DBCreateWizard.Program.LaunchDBCreation() at Microsoft.EnterpriseManagement.Setup.DBCreateWizard.SummaryPage.BackgroundThread()

 

clip_image002

 

To make a long story short:

We had a lab environment and production environment. Both environments are exact replicas: ip, users, servers, everything is the same. I did the install in the lab environment on my sql cluster and didn’t encounter any problems.

Now in production I had this strange error and asked my dba (that installed the sql cluster in lab and production) to confirm that everything was ok and that everything was the exact replica of the lab….

Now here comes the catch….and also the moment I wanted to kill my DBA….

I analyzed the dbcreatewizard error log that you can find here:

 

C:\Documents and Settings\user\Local Settings\Temp\1

image

And found the following sentence

 

10:31: CreateDB:  Attempting to create OperationsManager on ELSQL3E\WSSCOM threw the following sql exception Cannot use file ‘J:\SCOMOPLOG\OperationsManager.ldf’ for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.

 

image

I checked on my cluster resource and indeed: the Log disk was missing as a dependency!!

image

So my production environment was not the exact replica as my lab environment. I had to add the Log file disk as a dependency for my sql resource group:

image

 

And now I was able to run the dbcreatewizard.exe succesfully!

 

image

 

Hope this helps,

Alexandre Verkinderen

Avatar of alkin

by alkin

Opsmgr Data Warehouse failed to enumerate database components to be deployed

9:04 am in Uncategorized by alkin

Today I ran into this issue:

image

 

Data Warehouse failed to enumerate database components to be deployed. Failed to enumerate Data Warehouse components for deployment. The operation will be retried. Exception ‘SqlException': Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Component Instance name: scom.be Instance ID: {AC6FACD9-

 

Issue:This error appears immediately after a management pack is imported. The installaion of the reports in the MP is failing.

Resolution:Run exec sp_updatestats on the OperationsManagerDW db (the data warehouse).

 

When running the exec sp_updatestats doesn’t help follow these steps:

 

Download and extract the following hotfix:

 

http://support.microsoft.com/?kbid=954643

image

 

Run the SQL query Managementpackinstall.sp.sql

image

 

And directly after running the query I got the following event:

image

 

Everything is fine now and I have green management server:

 

image

 

Hope this help,

Alexandre Verkinderen

http://scug.be

Avatar of alkin

by alkin

Reporting Deployment and Usage Troubleshooting

6:52 pm in Uncategorized by alkin

Finally!!

 

One guide with the most common reporting issues! Thank you Microsoft!

 

“There are several common configuration and usage issues that can cause Operations Manager Reporting errors.  This document addresses the most common issues you are likely to encounter, solutions to those issues, and tools that you can use to resolve these problems.”

[View:/cfs-file.ashx/__key/CommunityServer.Components.PostAttachments/00.00.00.09.78/OM2007_ReportTrouble.docx]

Have fun,

Alexandre Verkinderen

Avatar of alkin

by alkin

Define a Health Criteria for your web application Monitor Part III

9:52 pm in Uncategorized by alkin

W’re almost at the end! :-) Only 3 steps left. First we have to define a healt criteria for our web appliction and after that we can create our distributed appliction that will drive ou service level dashboard.

 

Use the Web Application Editor to choose what conditions will cause an error or warning during a synthetic transaction. For the Service Level Dashboard, an error is equivalent to an availability exception, and a warning is equivalent to a performance exception. Availability exceptions will also affect performance reporting. You can also choose to generate an alert when the status changes. For example, if your transaction includes a request to a specific Web page, you can choose to generate an alert if the page is unavailable. This is done by changing the health status of the transaction when the HTTP status code is 404.

Synthetic transactions are created by recording a Web site or by manually creating requests. For more information about recording a Web site, see How to Capture a Web Application Recording in Operations Manager 2007. For more information about manually creating or editing individual requests, see

How to Create or Edit a Request in Operations Manager 2007.

To set health criteria for a request in a Web monitoring session

1. Open the Authoring pane.

2. Expand Management Pack Templates, and then click Web Application.

3. Select the object you want to edit, and then click Edit Web application settings.

4. In the Request Details pane, you can set criteria to generate an error or warning health state for the request. For example, select the Http Status Code check box, and then select Equals and 404 to change the status when the page is not found.

clip_image002[1]

5. If you want an alert generated when the health status changes, select the Generate an alert if any error criteria is met or Generate an alert if any warning or error criteria is met check boxes.

6. If you want the transaction to stop when an error or warning criteria is met, select the Stop processing the subsequent requests if any criteria is met check box.

7. Click Verify to test your changes.

image

8. After the changes are verified, click Apply, and then close the Web Application Editor.

Important   Repeat this process for every monitor that you create.

 

Next we will create a distributed appliction to drive the service level dashboard.

 

Greetz,

Alexandre Verkinderen

http://scug.be/blogs

Avatar of alkin

by alkin

Configuring the Service Level Dashboard Part V

9:08 pm in Uncategorized by alkin

After you create your monitors and distributed applications, you must take some additional steps to configure the Service Level Dashboard group and service level goal properties. Discovery finds all the objects that are associated with a distributed application. The current setting of these attributes is displayed in the Service Level Dashboard Attributes view in the Operations Console. This view lists the distributed applications that can be shown on the Service Level Dashboard, their Dashboard group, and their current service level goals.

 

Property

Default

Description

Name

 

The distributed application name

Availability Service Level Threshold

95

The percentage of availability the application must achieve to be shown as in compliance with the availability service level

Performance Service Level Threshold

95

The percentage of performance the application must achieve to be shown as in compliance with the performance service level

Dashboard Group

1

The Dashboard Group setting controls which dashboard the model will display on. All applications are assigned a default setting of 1, which allows multiple dashboards to be created for multiple views of the applications, or for views of different applications.

GUID

 

The GUID of the distributed application

 

Change the Service Level Dashboard Attributes for an Application

To change the Service Level Dashboard attributes, use overrides.

To override Service Level Dashboard attributes for a distributed application

1. Open the Authoring pane.

2. Expand Management Pack Objects, and then click Object Discoveries.

3. In the Look for box, type SLDBase and then click Find Now.

clip_image002[1]

4. Click Enterprise Service Monitoring Service Level Dashboard Discovery and then, in the Actions pane, click Overrides.

clip_image002[3]

5. Click Override the Object Discovery and then click For a specific object of type: Service Level Dashboard Application.

6. In the Select Object box, select the distributed application that contains attributes you want to edit, and then click OK.

7. Select the Override check box next to the attribute you want to edit.

clip_image002[5]

8. Enter the adjusted setting in the Override Setting column.

a. For Dashboard Group, enter an integer or a string.

b. For the Performance and Availability Service Level Thresholds, enter the uptime percentage in a decimal number, without any symbols.

9. Click OK.

 

Now that everything is configured we can start using our service level dashboard!

 

Greetz,

ALexandre Verkinderen

Avatar of alkin

by alkin

Creating the Distributed Application Models to Drive the Service Level Dashboard Part IV

9:06 pm in Uncategorized by alkin

The distributed application model interface provides a flexible way to customize the Service Level Dashboard display to your needs. The Service Level Dashboard accepts a simple distributed application model as its configuration for application listings and transaction groupings. This model allows you to group Web applications or other monitors on the Service Level Dashboard into applications and regions. You can define how the health rolls up to the component group and the application as a whole by editing the health rollup of the distributed application model.

Important   Note that these distributed application models are in addition to any distributed application models you might have already created for your applications. The Service Level Dashboard works only with a specific style of distributed application model—one that is based on the Service Level Dashboard Application template.

The Service Level Dashboard display shows three levels. The top level lists applications by their distributed application model names, the second level shows the component groups, and the third level lists the actual transaction names. Each level can contain several entries.

 

To create a distributed application model

1. In the Operations Console, click Authoring, right-click Distributed Applications, and then click Create a new distributed application.

clip_image002[1]

2. In the Name box, type a name for the distributed application, which will appear on the Service Level Dashboard. In the Description box, you can type a description.

3. Under Template, select the Service Level Dashboard Application template.

4. In the Management Pack drop-down box, choose the management pack created in the previous steps from the list of unsealed management packs. (By default, the distributed application you create is saved to the Default Management Pack.) Or, click New to create a new management pack. Click OK.

To design your distributed application model

1. The diagram pane in the distributed application designer displays the component groups of your distributed application. You will see two component groups defined by the template: Component Group 1 and Component Group 2. Right-click each component group to review it. If necessary, edit the object types that are included in your distributed application, and modify the name. On the toolbar, click Add Component to create a new component group. Component groups are generally used to define regions or other groups of transactions on the report.

2. The buttons at the bottom of the Objects pane list all object types that are defined by the template you chose earlier. If your distributed application does not contain one or more of the components shown in the list, click Organize Object Types to view a list of all currently included object types. Clear the check box for any object type that is not part of your distributed application.

3. Click each of the remaining buttons at the bottom of the Objects pane to view the objects that are listed in each. By default, the list contains all the discovered objects on your network that are of that object type.

4. Right-click each object that is a component of your distributed application, point to Add To, and then click the name of the component group to which this object belongs. (These objects may be the Web monitors defined earlier, or other types of objects that you want to display on the Service Level Dashboard at the transaction level. Any item in the component group displays as a transaction, with its health state calculated.) Click Save.

clip_image002[3]

5. To configure the health rollup of the distributed application (and by extension the Service Level Dashboard), in the Component Group Details pane, click the Configure health rollup link, and create an override for the rollup algorithm for the component group (or entire model) that rolls up in the manner expected.

6. To save the distributed application to a management pack, click Save.

 

After you create your monitors and distributed applications, you must take some additional steps to configure the Service Level Dashboard group and service level goal properties.

Greetz,

Alexandre Verkinderen

http://scug.be/blogs

Avatar of alkin

by alkin

Add a recording to an existing Web Application object Part II

11:05 am in Uncategorized by alkin

First you will have to create a web application monitor. See my previous post on how to

create a web application monitor in opsmgr.

 

To add a recording to an existing Web Application object

1. Open the Authoring pane.

2. Expand Management Pack Templates, and then click Web Application.

3. Select the object to which you want to add a recording.

4. In the Actions pane, click Edit Web application settings.

5. Select the request from the list where you want the recording to be inserted. Recordings are inserted after the request you select.

6. In the Actions pane, click Start capture. Internet Explorer will open. If you receive an error message about third-party extensions being disabled, follow these steps:

a. Click Tools, and then click Internet Options.

b. Click the Advanced tab.

c. Under Browsing, select Enable third party browser extensions.

d. Close Internet Explorer, and then click Start capture to open the browser again.

7. In the browser window, follow the actions you want to be monitored. For example, you might click some links or add a product to a shopping cart.

 

image


When you have completed the recording, click Stop in the left pane of Internet Explorer. Or, in the Actions pane, under Run Now, you can click Run Test to run the synthetic transaction immediately and see the results.

image

 

image

 

Now we have to define our health criteria  and a create the distributed application model to will drive the service level dashboard.

grtz,

Alexandre Verkinderen

http://scug.be/blogs

Avatar of alkin

by alkin

Create a Web Application Monitor in opsmgr Part I

8:58 am in Uncategorized by alkin

At the moment I’m testing web application monitoring, service level dashboard, etc. So the upcoming posts will handle on how to set up a web application monitoring, how to configure the service level dashboard etc.

The Web Application Monitor provides the synthetic transaction for the Service Level Dashboard. It monitors the Web application and then changes the health state of an object associated with the Web application, based on the results of the synthetic transaction. It is this change in health state that the Service Level Dashboard records and reports on.

petshop

 

To create a new Web Application Monitor

1. In the Operations Console, click the Authoring button.

2. In the Authoring pane, click Management Pack Templates.

3. Under Actions, click Add Monitoring Wizard.

4. In the Add Monitoring Wizard, on the Select Monitoring Type page, click Web Application, and then click Next.

image

5. On the General Properties page, do the following:

a. Type the Name for the object, such as Petshop.

b. Optionally, type a Description for the object.

c. From the list, click the management pack created in the previous step or click New to create a management pack. It is recommended to create one management pack per application, and group all transactions for a specific application into this management pack.

clip_image002

Note   Because the object type will be added to the specified management pack, only unsealed management packs are listed. For more information, see Management Packs in Operations Manager 2007.

 

6. Click Next.

7. On the Enter and Test Web Address page, do the following:

a. Select http:// or https:// from the list.

b. Type the URL for the Web application, such as http://petshop.com.

c. Click Test.

d. When the test succeeds, click Next.

Note   It is possible to proceed through the wizard without this test succeeding. If the test returns an error, check the URL and click Details for more information.

clip_image002[9]

8. On the Choose Watcher Nodes page:

a. Select the watcher nodes on which you want to run the transaction.

Note   Operations Manager groups the results of the selected watcher nodes into a single monitor. To create separate monitors for different watcher nodes, you must create separate Web Application Monitors, even if they contain the same transaction.

b. Set the Run this query every value to the time that you want—the minimum is 30 seconds.

c. Click Next.

clip_image002[11]

9. On the Summary page, review the settings. You can select the Configure Advanced Monitoring or Record a browser session check box, and then click Create. If you select this check box, move to step 6 in the following procedure.

Note   Selecting Configure Advanced Monitoring or Record a browser session runs the Web Application Editor. For more information, see Web Application Editor in Operations Manager 2007.

clip_image002[13]

grtz,

Alexandre Verkinderen

http://scug.be/blogs

Visit Us On TwitterVisit Us On Linkedin