Building a “Sample” SCOM Management Pack for Dynamically Building Virtual Machines based on Performance of physical or virtual machines

[アーティクル]
07/10/2009

In today’s post, I will focus on how I worked with our System Center Operations Manager (SCOM) team to build the actual infrastructure and setup alerting for our infrastructure to ensure that if our Configuration Manager Distribution Points (DPs) are getting a high number of connections, we will spin up additional virtual machines to help with the load.

For the most part, there are some requirements that should be in place for this post to be useful:

Virtual Machine Manager 2008 should be present in your environment
SCVMM Library has the appropriate Hardware & Guest OS Profiles built along with a template

If you have the above requirements, then you will be able to follow this blog to expand your infrastructure with SCOM 2007 to do active monitoring of your client services and “dynamically” respond to their performance by building additional infrastructure to remove the load.

Example Infrastructure Design for SCOM 2007 (& R2)

First off, I have to give a shout out to my resident SCOM experts – Duncan Ngarachu, JJ Lindner, and Ivan Ivanov – who guided me through getting a better understanding of SCOM. I knew what I wanted it to do but I wasn’t sure how to articulate how to get SCOM to do it. Big shout out…

With that said, let’s explain a small-scale design for our SCOM infrastructure for a bit of understanding. The primary thing that most folks realize is that ConfigMgr infrastructures depend heavily on Active Directory (AD) and this makes the requirement that SCOM has this ability to cross forests where applicable. For our environment, we have our System Center Virtual Machine Manager (SCVMM) infrastructure & SCOM in a privately hosted domain that has a one-way trust to our service infrastructure. Because of this, we have to rely on two management servers – one Root Management Server (RMS) and another that is a Gateway server hosted in our services infrastructure domain.

In this scenario, you use Machine Authentication between the SCOM Gateway and SCOM RMS server so you can manage services that exist in the domains where your users getting manage exist. For the Management Infrastructure, where SCOM & SCVMM servers live, you manage all of your other services. I will post a blog a bit later that outlines exactly how to setup PKI correctly to support SCOM Gateway as I have found most documentation to not be completely accurate.

NOTE: You must have the SCVMM and SCOM servers in the same forest or have two-way trusts. You will also need to ensure that you have a service account in each domain with privileges to take actions in the Services Forest. You will also need to get SCOM & SCVMM integrated per the following post from Cheng’s Blog.

Downloading & Importing the Management Packs

After you get your SCOM infrastructure planned out and you have the correct infrastructure in place, you will need to move to the next step of downloading and importing your management packs. For our purposes, I am going to share the management packs that we have installed so that you can take the sample management pack and alter as you see fit. For now, we have the following management packs as a requirement to get dynamic provisioning working:

Management Pack Name	Description	Download
Microsoft.SystemCenter.DataWarehouse.Library	Contains the Definitions and workflows required to support the forwarding of data to the Ops Mgr Data Warehouse.	Download Here
Microsoft.Windows.Library	Assists in tracking, managing, and reporting on your LOB application service level compliance	Download Here
Microsoft.SystemCenter.Library	Operations Mgr Management Pack	Download Here

You will notice that we don’t include things like SCVMM, etc. and this is on purpose. We could have built the management pack to be dependant on the SCVMM class library though every time we would like to modify we would have to “revision” and re-import. This seemed costly so we included bare miminum though the ones listed above aren’t completely bare either. However, you need them in order to successfully import. (This happens when the author – Ivan Ivanov – has these as the defaults for his authoring console and I don’t have the knowledge yet to figure out how to strip them out).

Installing SCOM agents on your Service Infrastructure Servers

The last step is to get agents distributed to your infrastructure pieces you would like to monitor. SCOM has the ability to extend AD to allow auto deployment but for the purposes of this post I’m going to consider this out of scope. There is also the ability to discover windows servers and install the agents manually and I will step through this process today.

At minimum, you should install agents on your Virtual Machine Manager server as well as any of your ConfigMgr infrastructure. This is pre-req to ensuring that you have what you need to get these up and running.

To Install agents manually on your server, do the following:

Open the SCOM Administrators Console
Click Administration
Right-click on Agent Managed, select Discovery Wizard
Select Windows Computers from the device to manage wizard
Click Next
Click either Automatic discovery to use Active Directory or advanced to select a specific type of client or server
Click the Domain, and select it
For the Administrator account, keep the default to Use selected Management Server Action Account
Click Discover
Select the object and then the agent will install

For more information on installing & discovering servers & clients, see the following KB.

Sample Custom Management Pack for System Center Configuration Manager DPs

After installing your agents, you will notice that all of the pre-defined monitoring groups setup by the management packs for Configuration Manager show no objects (e.g. servers) in your infrastructure. This is often the case as the discovery logic is broken, I have found, for many of the groups because servers are missing the appropriate registry and\or file settings to get discovered. You can manually fix this by using SCOM to determine what the discover logic is or you can do your own detection. For our purposes, we created our own discovery logic that is based on a registry key.

On each of of our DP infrastructure pieces, we have added the following registry key for detection:

Path: HKLM\System\Software\Microsoft

Key: MPSD (or Org Name)

String Name: RedmondDP (stands for DPs in Redmond but could be anything)

String Value: RedmondDP

For our management pack, we have one called DynamicDP that does a discovery of any servers that have this registry key and if detected will then assume it is a DP. The same logic can be used for a DynamicMP or DynamicSUP with a different management pack which is what we do.

We have some logic setup whereby we create monitors and alerts based on Web Service Concurrent Connections (e.g. the total number of connections open currently on the Web server which is what a DP is). In this section, we create an alert that says the following:

Throw Alert:	Description of Alert
If connections greater than 30	If 30 concurrent connections exist on a single DP in our environment then create a critical alert.NOTE: 30 is a very, very low number but is easy to show this in action. I highly recommended that you use performance data to determine the sweet spot for this number.
If connections stay greater than 30 over 3 samplings	If Part A (greater than 30) happens 3 consecutive times then change the health of the server to critical.NOTE: Again, 3 is a low sampling rate and for demo-friendly purposes. However, the concept doesn’t change the fact that you take actions depending on what your threshold is.

As I said, this is a sample but to give you a blueprint I’m going to share out our sample Management Pack XML which you should be able to open in the Authoring Console and modify to your liking.

Code Snippet

<?xml version="1.0" encoding="utf-8"?><ManagementPack ContentReadable="true" xmlns:xsd="https://www.w3.org/2001/XMLSchema" xmlns:xsl="https://www.w3.org/1999/XSL/Transform">
<Manifest>
<Identity>
<ID>DynamicProvisionDP</ID>
<Version>1.0.0.11</Version>
</Identity>
<Name>DynamicProvisionDP</Name>
<References>
<Reference Alias="SCDW">
<ID>Microsoft.SystemCenter.DataWarehouse.Library</ID>
<Version>6.1.7221.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
<Reference Alias="Windows">
<ID>Microsoft.Windows.Library</ID>
<Version>6.1.7221.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
<Reference Alias="Performance">
<ID>System.Performance.Library</ID>
<Version>6.1.7221.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
<Reference Alias="System">
<ID>System.Library</ID>
<Version>6.1.7221.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
<Reference Alias="SystemCenter">
<ID>Microsoft.SystemCenter.Library</ID>
<Version>6.1.7221.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
<Reference Alias="SystemHealthLibrary6170430">
<ID>System.Health.Library</ID>
<Version>6.1.7221.0</Version>
<PublicKeyToken>31bf3856ad364e35</PublicKeyToken>
</Reference>
</References>
</Manifest>
<TypeDefinitions>
<EntityTypes>
<ClassTypes>
<ClassType ID="DynamicProvisionDP.RedmondDP" Accessibility="Internal" Abstract="false" Base="Windows!Microsoft.Windows.Server.OperatingSystem" Hosted="true" Singleton="false" />
</ClassTypes>
</EntityTypes>
</TypeDefinitions>
<Monitoring>
<Discoveries>
<Discovery ID="DynamicProvisionDP.RedmondDP_Discovery" Enabled="true" Target="Windows!Microsoft.Windows.Server.OperatingSystem" ConfirmDelivery="false" Remotable="true" Priority="Normal">
<Category>Discovery</Category>
<DiscoveryTypes>
<DiscoveryClass TypeID="DynamicProvisionDP.RedmondDP" />
</DiscoveryTypes>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.FilteredRegistryDiscoveryProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<RegistryAttributeDefinitions>
<RegistryAttributeDefinition>
<AttributeName>RedmondDP</AttributeName>
<Path>SOFTWARE\Microsoft\MPSD\RedmondDP</Path>
<PathType>1</PathType>
<AttributeType>1</AttributeType>
</RegistryAttributeDefinition>
</RegistryAttributeDefinitions>
<Frequency>3600</Frequency>
<ClassId>$MPElement[Name="DynamicProvisionDP.RedmondDP"]$</ClassId>
<InstanceSettings>
<Settings>
<Setting>
<Name>$MPElement[Name="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Name>
<Value>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</Value>
</Setting>
</Settings>
</InstanceSettings>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Values/RedmondDP</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">RedmondDP</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</DataSource>
</Discovery>
</Discoveries>
<Rules>
<Rule ID="DynamicProvisionDP.DynamicProvisionDP.DP_ConcurrentConnections" Enabled="true" Target="DynamicProvisionDP.RedmondDP" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>PerformanceCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Performance!System.Performance.OptimizedDataProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<CounterName>Current Connections</CounterName>
<ObjectName>Web Service</ObjectName>
<InstanceName>_Total</InstanceName>
<AllInstances>false</AllInstances>
<Frequency>60</Frequency>
<Tolerance>0</Tolerance>
<ToleranceType>Absolute</ToleranceType>
<MaximumSampleSeparation>1</MaximumSampleSeparation>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WriteToDB" TypeID="SystemCenter!Microsoft.SystemCenter.CollectPerformanceData" />
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData" />
</WriteActions>
</Rule>
</Rules>
<Monitors>
<UnitMonitor ID="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor" Accessibility="Internal" Enabled="true" Target="DynamicProvisionDP.RedmondDP" ParentMonitorID="SystemHealthLibrary6170430!System.Health.EntityState" Remotable="true" Priority="Normal" TypeID="Performance!System.Performance.AverageThreshold" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/InstanceName$</AlertParameter1>
<AlertParameter2>$Data/Context/ObjectName$</AlertParameter2>
<AlertParameter3>$Data/Context/CounterName$</AlertParameter3>
<AlertParameter4>$Data/Context/Value$</AlertParameter4>
<AlertParameter5>$Data/Context/TimeSampled$</AlertParameter5>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success" />
<OperationalState ID="OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error" />
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<CounterName>Current Connections</CounterName>
<ObjectName>Web Service</ObjectName>
<InstanceName>_Total</InstanceName>
<AllInstances>false</AllInstances>
<Frequency>60</Frequency>
<Threshold>30</Threshold>
<NumSamples>3</NumSamples>
</Configuration>
</UnitMonitor>
</Monitors>
<Recoveries>
<Recovery ID="MomUIGenaratedRecovery65313795f8d6405ba9e9da455b77898e" Accessibility="Public" Enabled="true" Target="DynamicProvisionDP.RedmondDP" Monitor="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor" ResetMonitor="false" ExecuteOnState="Error" Remotable="true" Timeout="300">
<Category>Custom</Category>
<WriteAction ID="MomUIGenaratedModule0c16fda31365426e82f744cab8f7db6c" TypeID="Windows!Microsoft.Windows.ScriptWriteAction">
<ScriptName>RedmondDPRecovery.vbs</ScriptName>
<Arguments />
<ScriptBody>Set wshShell = WScript.CreateObject ("WSCript.shell")
wshshell.run "c:\windows\system32\notepad.exe", 6, True
set wshshell = nothing</ScriptBody>
<TimeoutSeconds>300</TimeoutSeconds>
</WriteAction>
</Recovery>
</Recoveries>
</Monitoring>
<Presentation>
<Views>
<View ID="DynamicProvisionDP.StateView" Accessibility="Internal" Enabled="true" Target="DynamicProvisionDP.RedmondDP" TypeID="SystemCenter!Microsoft.SystemCenter.StateViewType" Visible="true">
<Category>StateCollection</Category>
<Criteria />
</View>
<View ID="View_04fa006bc6f54c7d84616c6e8af3ad32" Accessibility="Public" Enabled="true" Target="DynamicProvisionDP.RedmondDP" TypeID="SystemCenter!Microsoft.SystemCenter.StateViewType" Visible="true">
<Category>Operations</Category>
<Criteria>
<InMaintenanceMode>false</InMaintenanceMode>
</Criteria>
<Presentation>
<ColumnInfo Index="0" SortIndex="0" Width="100" Grouped="false" Sorted="true" IsSortable="true" Visible="true" SortOrder="Descending">
<Name>State</Name>
<Id>DynamicProvisionDP.RedmondDP</Id>
</ColumnInfo>
<ColumnInfo Index="1" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="true" SortOrder="Ascending">
<Name>Maintenance Mode</Name>
<Id>InMaintenanceMode</Id>
</ColumnInfo>
<ColumnInfo Index="2" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="true" SortOrder="Ascending">
<Name>Name</Name>
<Id>Name</Id>
</ColumnInfo>
<ColumnInfo Index="3" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="true" SortOrder="Ascending">
<Name>Path</Name>
<Id>Path</Id>
</ColumnInfo>
<ColumnInfo Index="4" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Operating System Version</Name>
<Id>OSVersion</Id>
</ColumnInfo>
<ColumnInfo Index="5" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Operating System Version Display Name</Name>
<Id>OSVersionDisplayName</Id>
</ColumnInfo>
<ColumnInfo Index="6" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Product Type</Name>
<Id>ProductType</Id>
</ColumnInfo>
<ColumnInfo Index="7" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Build Number</Name>
<Id>BuildNumber</Id>
</ColumnInfo>
<ColumnInfo Index="8" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>CSD Version</Name>
<Id>CSDVersion</Id>
</ColumnInfo>
<ColumnInfo Index="9" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Service Pack Version</Name>
<Id>ServicePackVersion</Id>
</ColumnInfo>
<ColumnInfo Index="10" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Serial Number</Name>
<Id>SerialNumber</Id>
</ColumnInfo>
<ColumnInfo Index="11" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Install Date</Name>
<Id>InstallDate</Id>
</ColumnInfo>
<ColumnInfo Index="12" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>System Drive</Name>
<Id>SystemDrive</Id>
</ColumnInfo>
<ColumnInfo Index="13" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Windows Directory</Name>
<Id>WindowsDirectory</Id>
</ColumnInfo>
<ColumnInfo Index="14" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Physical Memory (KB)</Name>
<Id>PhysicalMemory</Id>
</ColumnInfo>
<ColumnInfo Index="15" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Logical Processors</Name>
<Id>LogicalProcessors</Id>
</ColumnInfo>
<ColumnInfo Index="16" SortIndex="-1" Width="100" Grouped="false" Sorted="false" IsSortable="true" Visible="false" SortOrder="Ascending">
<Name>Display Name</Name>
<Id>DisplayName</Id>
</ColumnInfo>
</Presentation>
<Target />
</View>
<View ID="View_46f83bae82cd49bf96314437efec81ad" Accessibility="Public" Enabled="true" Target="DynamicProvisionDP.RedmondDP" TypeID="SystemCenter!Microsoft.SystemCenter.PerformanceViewType" Visible="true">
<Category>Operations</Category>
<Criteria>
<RuleList>
<Rule>64c1b2b1-be82-31ef-eb27-61e3645f6aee</Rule>
</RuleList>
</Criteria>
<Presentation>
<SortedColumnIndex>0</SortedColumnIndex>
<SortOrder>0</SortOrder>
<StartTime>2009-06-15T19:38:17.561611-07:00</StartTime>
<EndTime>2009-06-16T19:38:17.561611-07:00</EndTime>
<DynamicTimeTicks>864000000000</DynamicTimeTicks>
<IsDynamic>true</IsDynamic>
<Is3DMode>false</Is3DMode>
<ShowAlerts>false</ShowAlerts>
<ShowMaintenanceMode>false</ShowMaintenanceMode>
<BaselineMode>false</BaselineMode>
<ShowPointLabels>false</ShowPointLabels>
<EnableSmartLabels>true</EnableSmartLabels>
<RightAngleAxes>false</RightAngleAxes>
<ClusterSeries>false</ClusterSeries>
<Title />
<TitleFont>Microsoft Sans Serif,12,Regular</TitleFont>
<ChartFont>Microsoft Sans Serif,8.25,Regular</ChartFont>
<ShowBands>false</ShowBands>
<BandColor>-1579033</BandColor>
<ChartType>Line</ChartType>
<Depth>100</Depth>
<GapDepth>100</GapDepth>
<Perspective>10</Perspective>
<GraphXRotation>0</GraphXRotation>
<GraphYRotation>0</GraphYRotation>
<XLabelAngle>0</XLabelAngle>
<LabelColor>-16777216</LabelColor>
<LabelFont>Microsoft Sans Serif,8.25,Regular</LabelFont>
<XAxisVisible>True</XAxisVisible>
<XShowMajorGridlines>false</XShowMajorGridlines>
<XShowMinorGridlines>false</XShowMinorGridlines>
<ShowInterlaceStrips>false</ShowInterlaceStrips>
<XInterlaceColor>16777215</XInterlaceColor>
<XShowSideMargin>true</XShowSideMargin>
<XAxisFont>Microsoft Sans Serif,8.25,Regular</XAxisFont>
<AutoAxis>true</AutoAxis>
<AxisMax>100</AxisMax>
<AxisMin>0</AxisMin>
<YAxisVisible>True</YAxisVisible>
<YShowMajorGridlines>true</YShowMajorGridlines>
<YShowMinorGridlines>false</YShowMinorGridlines>
<YShowInterlaceStrips>false</YShowInterlaceStrips>
<YShowSideMargin>true</YShowSideMargin>
<YAxisFont>Microsoft Sans Serif,8.25,Regular</YAxisFont>
<BackgroundColor1>-1</BackgroundColor1>
<BackgroundColor2>-1</BackgroundColor2>
<GradientType>None</GradientType>
<Series />
</Presentation>
<Target />
</View>
</Views>
<Folders>
<Folder ID="Folder_04a15710e108455fac112f27934b76ed" Accessibility="Public" ParentFolder="SystemCenter!Microsoft.SystemCenter.Monitoring.ViewFolder.Root" />
</Folders>
<FolderItems>
<FolderItem ElementID="DynamicProvisionDP.StateView" Folder="SystemCenter!Microsoft.SystemCenter.Monitoring.ViewFolder.Root" />
<FolderItem ElementID="View_04fa006bc6f54c7d84616c6e8af3ad32" Folder="Folder_04a15710e108455fac112f27934b76ed" />
<FolderItem ElementID="View_46f83bae82cd49bf96314437efec81ad" Folder="Folder_04a15710e108455fac112f27934b76ed" />
</FolderItems>
<StringResources>
<StringResource ID="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor_AlertMessageResourceID" />
</StringResources>
</Presentation>
<LanguagePacks>
<LanguagePack ID="ENU" IsDefault="false">
<DisplayStrings>
<DisplayString ElementID="DynamicProvisionDP">
<Name>DynamicProvisionDP</Name>
<Description>This management pack will detect "high" usage of DPs and take action</Description>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor">
<Name>DP Connections Monitor</Name>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.DynamicProvisionDP.DP_ConcurrentConnections">
<Name>DP Connections</Name>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.RedmondDP">
<Name>RedmondDP</Name>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.RedmondDP_Discovery">
<Name>DynamicProvisionDP.RedmondDP_Discovery</Name>
</DisplayString>
<DisplayString ElementID="Folder_04a15710e108455fac112f27934b76ed">
<Name>DynamicProvisionDP</Name>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.StateView">
<Name>DP State</Name>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor_AlertMessageResourceID">
<Name>DP Connections Monitor</Name>
<Description>Instance {0}
Object {1}
Counter {2}
Has a value {3}
At time {4}</Description>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor" SubElementID="OverThreshold">
<Name>OverThreshold</Name>
</DisplayString>
<DisplayString ElementID="DynamicProvisionDP.DP_ConcurrentConnectionsMonitor" SubElementID="UnderThreshold">
<Name>UnderThreshold</Name>
</DisplayString>
<DisplayString ElementID="View_04fa006bc6f54c7d84616c6e8af3ad32">
<Name>DP State</Name>
</DisplayString>
<DisplayString ElementID="View_46f83bae82cd49bf96314437efec81ad">
<Name>DP Performance</Name>
</DisplayString>
<DisplayString ElementID="MomUIGenaratedRecovery65313795f8d6405ba9e9da455b77898e">
<Name>RedmondDPRecovery</Name>
</DisplayString>
</DisplayStrings>
</LanguagePack>
</LanguagePacks>
</ManagementPack>

Configuring Recovery Tasks for SCOM’s Root Management Server

The “typical’ design of a management pack is to take “recovery” actions against the target server whose state is critical. For example, if your Web server is sitting at 100% CPU you would take a recovery action against that server such as recycle the application pool. The target in this case is the server who through the alert.

However, in the case of scaling your infrastructure, the target completely changes as you are interested in using the “state” of a machine and asking it to do nothing. For example, I want my Web server who is sitting at 100% CPU to do nothing other than go unhealthy so I can take action. This is a bit trickier overall.

In this case, you would use SCOM’s Channel, Subscriptions, and Notifications to setup the alert to take action through a command action. This also could be email, text message, or IM you when the problem occurs. The extreme action is to spin up additional servers to help support the load that is currently in place.

How do I do this? Glad you asked…

Create Channel

The following step will create our appropriate recovery action to initiate the recovery steps when our target servers get in a state which we don’t desire such as Critical. To do this, do the following:

NOTE: To perform these actions, you will need the appropriate SCOM privileges setup

Open the SCOM Administrators Console
Click the Administration Tab
Click Channels under Notifications
Under New, select Command
In the Command Notification wizard, input the Channel Name & Description
Click Next
For the Notification Channel, input the command to execute (e.g. dp_recovery.cmd), select Alert Source (this isn’t used in our scenario), and the startup folder (the command-line parameters are optional)
Click Finish

This will successfully create the channel for us that initiates the command-line action. It uses a local path because if you remember that we know the SCOM server will take all the actions so we can safely assume that the directory is highly available.

Add Subscriber

The purpose of the Subscriber is to bind the “who” to the what which is the channel. So we need to add a active subscriber to our infrastructure. In our case, the subscriber is the SCVMM server for our infrastructure.

To setup a subscriber, do the following:

Open the SCOM Administrators Console
Click the Administrators tab
Click Subscriber under Notification
Right click, select New to open the New Subscriber Wizard
Input the Subscriber name
Select to always send notifications (this is a nice thing to have where you could scope it to a schedule if you needed too)
Click the Add on the Notification Subscriber Wizard which starts an additional wizard
In the Describe the Subscriber Address, input the address name such as SCVMM
Let’s then provide the Channel & Delivery Address to use (delivery address isn’t really used)
Click the Command Channel drop down and select DP Recovery (or whatever you named it)
For the Delivery address, input address
Click Next
Select Always Send Notifications for scheduling
Click Finish

The completed setup for this section should result in something similar to the following:

Create Subscription

The next, and last, step is to create a subscription. In this section I will walk you through creating your subscription so that you have completed the process of creating the channel, subscriber, and subscription. The following are the steps to create the subscription:

Open the SCOM Administrator’s Console
Click the Administration Tab
Click the Subscriptions under Notifications
Right-click and select New to open the Notification Subscription Wizard
Enter a subscription name such a Redmond DP and a Description
In the criteria selection, select the following:
Click Next
To search, you would select the following based on the name of your MP:
In the subscriber search, select the available subscribers created above:
Highlight and click Add
Click Add on the Channels wizard, and then click Search
Click Finish

That’s it. You now have your SCOM wired up to monitor your DP, and based on criteria you created, take an action that would include the opportunity to build you a new DP.

NOTE: Your SCOM server’s service account is used for the creation of your virtual machine. In order for this to work, you will need to add your SCOM service account to the administrator’s role in SCVMM. You can also add additional accounts for notification if you prefer to specify a different account is used.

Summary

What we focused on today and how we tied together the two pieces of our infrastructure – SCVMM & SCOM and focused heavily on how to correctly set these up so that you can “scale” on demand. The key piece of this puzzle is the management pack which we have built along with several other posts I have made that make up the building blocks of this entire principle - “scale on demand” – not after it is too late. For us, we focused on how to build a “typical” SCOM infrastructure, including installing agents, and how to effectively get the management packs imported so you can effectively use your custom management pack since we are dependent on them.

I will start soon pulling this all together so that you can see what “dynamic provisioning” using System Center is all about!

Enjoy!

-Chris

次の方法で共有