TAG | mp
Sometime you want to monitor a server, a workstation or a network device, but you don’t need to have all the monitors provided by your management packs installation in Operations Manager 2007 R2, and a ping will be enough.
OpsLogix has released already sometimes ago the OpsLogix Ping Management Pack. This management pack has the advantage to have a fully integration, an easy configuration and it’s free.
OpsLogix Web site: http://www.opslogix.com/ping
Step 1: Run the management pack installer
- Run OpsLogix.Ping.ManagementPacks.msi
- Accept the license agreement
- Unpack the files to a folder on disk
Step 2: Import the management packs
- Open the SCOM console
- Goto Administration
- Select “Import Management Packs”
Import these three management packs from the folder on disk:
Step 3: Run the console extension installer
On one computer that has the Operations Manager 2007 console installed:
For Operations Manager 2007 SP1 installations:
- Run OpsLogix.Console.Extension.SP1.msi
For Operations Manager 2007 R2 RTM installations:
- Run OpsLogix.Console.Extension.R2RTM.msi
That will extract the file OpsLogix.IMP.Base.UI.dll and you have to copy that file on every computer that has the Operations Manager 2007 Console installed in “%ProgramFiles%\System Center Operations Manager 2007″
If you don’t copy the dll, you will have the following message in the configuration part:
Select your watcher node(s)
Select your watcher node, add the Target Display Name and Target Ip Address
You could also directly import a csv file with all your targets.
In Host, you have the general health of your watcher node(s)
In Status, you could see the state of all your targets, if the devices are answering to the ping.
In Response Times, you have a view about the answer times of your targets
In Alerts, you could see the targets that are not answering to ping
By default, the targets are pinged every 60 seconds, if you want to change that value, just create an override on the monitor: Target Host Ping Check.
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.
- 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.
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:
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:
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.
The download is available at the following url :
- 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 :
Jimmy Harper recently found that many Event Log rules in the Active Directory Management Pack for Windows Server 2008 (version 6.0.7065.0) do not work correctly, resulting no alert being generated for these rules. This is happening because the MP uses the old event sources from Server 2003 in its event rules, rather than the new ones for Server 2008/R2.
He wrote a little management pack for correcting this issue
Microsoft has just realease a new management pack for SCOM2007 : Active Directory Federation Services 2.0 Management Pack
- Events that indicate service outages and operational errors or warnings
- Alerts that indicate configuration issues and background tasks failures or warnings
- Whether auditing is occurring successfully
- Communication between the federation server and the federation server proxy
- Notification of malformed access requests
- Website availability
- The health of the Secure Sockets Layer (SSL) certificate of the federation passive website in Internet Information Services (IIS)