vNext.be | Operations Manager, Opalis, PowerShell, …

CAT | OpsMgr / Scom

Jan/11

8

SCOM / OpsMgr: NetApp Management Pack

5 Comments · Posted by Christopher Keyaert in OpsMgr / Scom

Hi Guys,

Today, I will blog about the installation of the NetApp Management Pack for monitoring your storage environment directly in Microsoft Operations Manager 2007 R2.
This management is free and directly provided by NetApp, so there is no reason to not use it.

Pre-requisites

 

  • Available on the NetApp Connect Website, you have to download the ApplianceWatchPRO2.1_x64_NetApp.exe file.
  • Service account that could access to the NetApp Controller.

Installation

 

On the SCOM Root Management Server, each Management Servers and computers where you have SCOM console installed, run the ApplianceWatchPRO2.1_x64_NetApp.exe installer. The installation of this application is required everywhere you have SCOM console installed, if you want to be able to use Netapp task in directly from the Task pane of all your SCOM Consoles. If you don’t need that, just install the application on the RMS.

The setup is just a next-next, without any specific configuration. After the installation process, the official NetApp documentation and management packs are available in the installation folder.(by default located in : C:\Program Files\NetApp\ApplianceWatch PRO)

As always, read the documentation and after that import the following management pack (by default located in: C:\Program Files\NetApp\ApplianceWatch PRO) in SCOM Console:
DataONTAP.mp
DataONTAP.Reporting.mp

Configuration

 

Configure all your NetApp Controllers as Network Devices

Add all your NetApp Controllers as Network Devices, so you will have to know the Controllers IP and the SNMP community.
You could confirm the good working of the communication in the Network Devices State:

Set the credentials

After a few minutes, the controllers will appear in the Controllers
view from the NetApp folder in SCOM console, click on one controller and in the Action Pane
execute Data ONTAP : Manage Controller Credentials
Specify the credentials and protocol for each Controllers:

Enable the discovery

The Netapp management pack needs to run an automatic discovery every x times. Normally this discovery could be launch by any servers, but after several tests, I only succeeded to have it working when I run it from the RMS.

Go to Authoring > Management Pack Objects > Rules
and look for ‘Data ONTAP: Discovery Rule‘
Create an override to enable this rule and targeted it to the RMS:

The automatic discovery is now ok, if you want to force the discovery, go to Monitoring > Discovered Inventory and Change Target Type to Management Servers.


Click on the RMS and go to the Action Pane, and click on Data ONTAP : Run discovery task
and execute the task.

All the views

 

After a few hours, all the views will be populated with the data from the NetApp Controllers:


Conclusion

 

I hope this post help you with the installation of the NetApp Management for SCOM. Don’t hesitate to post a comment if you have any questions.
Christopher KEYAERT

· · · ·

Dec/10

8

SCOM : Gateway Primary and Failover MS

4 Comments · Posted by Christopher Keyaert in OpsMgr / Scom

If you want to change the Primary MS of your gateway server or if you want to add a failover MS to it, on the technet library on Deploying Gateway Server in the Multiple Server, Single Management Group Scenario, the following commands will be presented :
   

1
2
3
4
$primaryMS = Get-ManagementServer | where {$_.Name -eq 'corp-ms02.corp.contoso.local'}
$failoverMS = Get-ManagementServer | where {$_.Name -eq 'corp-r2.corp.contoso.local'}
$gatewayMS = Get-GatewayManagementServer | where {$_.Name -eq 'dmz01'}
Set-ManagementServer -GatewayManagementServer: $gatewayMS -primarymanagementserver: $primaryMS -FailoverServer: $failoverMS

When you run this command you have to be aware that when the current management server gets this update it will stop accepting connections from your gateway server (if it is not primary or failover management server in the new configuration). That could result in a orphaned gateway server, the gateway server is not allowed to communicate with any management server.

To avoid that, I wrote a little PowerShell Script that does all the task for you and avoid to have a orphaned gateway server. For writing this script, I took my idea from this excellent post : Ops Mgr R2 and multiple gateway servers

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
########################################
# Gateway Server : Primary / Failover
# Autor : Christopher Keyaert
# Email : christopher@vnext.be
# Website : http://www.vnext.be
# Date : 8 DEC 2010
# Version : 0.1
#
# Inspired by : http://contoso.se/blog/?p=831
########################################
# PARAM
########################################

#FQN NAME
$RMS = "xxx.CONTOSO.COM"
$Gateway = "xxx.CONTOSO.COM"
$PrimaryMS = "xxx.CONTOSO.COM"
$failoverMS = "xxx.CONTOSO.COM"

#Waiting time
$WaitingTime = 3 # Minutes

########################################
# SNAP-IN + RMS Conenction
########################################
if(-not (Get-pssnapin | Where-Object {$_.Name -eq "Microsoft.EnterpriseManagement.OperationsManager.Client"}))
{
Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client
}
new-managementGroupConnection -ConnectionString:$RMS
Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin ;
Set-Location $RMS -ErrorVariable errSnapin ;

########################################
# SCRIPT
########################################

Write-Host "#######################"
Write-Host "# Gateway Failover #"
Write-Host "#######################"
Write-Host ""
Write-Host "Gateway : "$Gateway
Write-Host "Primary : "$PrimaryMS
Write-Host "Failover : "$FailoverMS
Write-Host ""

#Get server details
$primaryMS = Get-ManagementServer | where {$_.Name -eq $PrimaryMS}
$failoverMS = Get-ManagementServer | where {$_.Name -eq $failoverMS}
$gatewayMS = Get-GatewayManagementServer | where {$_.Name -eq $Gateway}

#Get current primary
$CurrentPrimary = $gatewayMS | Get-PrimaryManagementServer

#Set Primary as failover for configuration transfert
Set-ManagementServer -GatewayManagementServer: $gatewayMS -primarymanagementserver: $primaryMS -FailoverServer: $CurrentPrimary

#Wait for config change
For($i = $WaitingTime; $i -gt 0; $i--)
{
Write-Host "Waiting $i minutes for configuration changes"
Start-Sleep 60
}

#Set the real configuration
Set-ManagementServer -GatewayManagementServer: $gatewayMS -primarymanagementserver: $primaryMS -FailoverServer: $failoverMS

#You can also run the following command shell commands to see he primary and failover server for a gateway server

$CheckPrimary = Get-GatewayManagementServer | where {$_.Name -like $Gateway} | Get-PrimaryManagementServer
If($CheckPrimary.Name -eq $PrimaryMS.Name)
{Write-Host "Primary server OK : "$PrimaryMS.name}
else{Write-Host "Primary server Failed : "$CheckPrimary.Name}

$CheckFailover = Get-GatewayManagementServer | where {$_.Name -like $Gateway} | Get-FailoverManagementServer
If($CheckFailover.Name -eq $failoverMS.name)
{Write-Host "FailOver server OK : "$failoverMS.Name}
else{Write-Host "FailOver server Failed : "$CheckFailover.Name}

Write-Host ""
Write-Host "END."

· · · · · ·

Nov/10

24

System Center Operations Manager 2012

No comments · Posted by Christopher Keyaert in OpsMgr / Scom

At the TechEd 2010, Microsoft presented a CTP (Community Technology Preview) version of System Center Operations Manager 2012. The video is available below : (http://www.msteched.com/2010/Europe/MGT205)

To complete that video, Marnix blogged on that topic :

SCOM vNext – Part I – The Next Generation of SCOM
http://thoughtsonopsmgr.blogspot.com/2010/11/scom-vnext-part-i-next-generation-of.html

SCOM vNext – Part II – Holistic View of Application Health
http://thoughtsonopsmgr.blogspot.com/2010/11/scom-vnext-part-ii-holistic-view-of.html

· · · · · ·

Nov/10

24

OpsMgr 2007 R2 Core MP’s updated 6.1.7695.0

No comments · Posted by Christopher Keyaert in OpsMgr / Scom

Microsoft just released an update of the Core Management Pack for System Center Operations Manager 2007 R2.

The download is available at the following url :
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=61365290-3c38-4004-b717-e90bb0f6c148

Feature Summary:

  • Local and Remote Monitoring of an Agent’s Health
  • Optional, Automatic Agent Remediation Capabilities
  • Detection of Problems and Misconfigurations with Run As Accounts and Profiles
  • Monitoring of problems with Running Workflows in Management Packs
  • Reports for identify drivers of data volumes in your environment
  • Operational Data Reporting

Kevin Holman already blogged on that new Core MP, I invite you to read his post :
http://blogs.technet.com/b/kevinholman/archive/2010/11/24/opsmgr-2007-r2-core-mp-s-updated-6-1-7695-0.aspx

· · · ·

Nov/10

19

SCOM : Collecting SQL Database size as a performance counter

No comments · Posted by Christopher Keyaert in OpsMgr / Scom

Kevin Holman just blogs on how Collecting SQL Database size as a performance counter with Operations Manager.

Link : http://blogs.technet.com/b/kevinholman/archive/2010/11/19/collecting-sql-database-size-as-a-performance-counter.aspx

No tags

Sep/10

19

How to convert a Microsoft VHD to a VMware VMK?

2 Comments · Posted by Christopher Keyaert in Opalis, OpsMgr / Scom, VMWare

Sometime, you have a Virtual Machine in a Microsoft VHD format and you would like to use it with your VMware Workstation application. So this little guide will explain how to perform this operation.

Pre-requisites

 

Step 1

 

Create a working folder on one of your computer drive and paste your VHD file into it.

Step 2

 

For the conversion, VMware Converter needs a VMC file. A VMC is the configuration file of the Microsoft Virtual Machine, it’s in this file that you the all the settings of the VM.

So, download the VMC file that is available here (http://www.vnext.be/wp-content/uploads/2010/09/MyVM.Rename-to-dot-vmc.txt), rename the extension to .vmc and paste it to your working folder:

Open it with notepad and edit the path to your VHD file like below:

Step 3

 

Start VMware Converter 4 standalone

Click on Convert Machine:

  • Select source type : Backup image or third-party virtual machine
  • Virtual machine file : The path to your VHD file


Click on Next and choose the following parameters:

  • Select destination type : VMware Workstation or other VMware virtual machine
  • Select VMware product : VMware Workstation 7.0.x

Click on Next and choose the following parameters:
Adapt the parameters to your need, but be sure that Install VMware Tools is set to YES

Click on Next and review all the information:

Click on Finish and wait the end of the process:

After a few minutes, the process is complete:

Go to your working folder, enter in the new created folder and double click on the .vmx file.

VMware workstation will now start:

Review your Virtual Machine configuration and start your new VM:

After you’re first Log on, Windows will install the drivers related to VMware Workstation, so let the process continue and restart you virtual machine when it’s done:

When all the drivers have been installed and you virtual machine restarted, you will have to reactive your copy of Windows:

When the activation process ended, you could now enjoy your virtual machine with VMware Workstation:

Christopher KEYAERT

· · · · ·

Sep/10

7

EventID 31567: Failed to deploy reporting component to the SQL Server Reporting Services server.

No comments · Posted by Christopher Keyaert in OpsMgr / Scom