31
OpsMgr / SCOM : NetApp Management pack 3.0 – Installation
No comments · Posted by Christopher Keyaert in Uncategorized
A few months ago, Netapp upgraded, renamed and grouped their Microsoft System Center management pack and Microsoft PowerShell command-lets into one new product, the OnCommand Plug-in for Microsoft.
This new version of this tool includes also new functionalities like:
· Opalis Integration Packs
· Discovery Agent for Hyper-V host
· Complete documentation for all these functionalities.
Here we will focus only on the Microsoft Operations Manager management pack. This application has to be installed on a management server, if possible, avoid installing it on the root management server.
Copy the file, OnCommand-PlugIn-Microsoft_3.0_x64_NetApp.exe, on the root management server and let’s start the installation by double clicking on it. Unfortunately, we don’t have the choice here, it must run from the RMS.
If a previous version of the management pack is installed, like the Data Ontap Appliance Watch PRO 2.1, it will be automatically uninstalled it.
Specify the destination folder and Click on Next to continue. ![]()
As we are only interested by the SCOM Management Pack, we will not install other component. ![]()
NetApp OnCommand needs to run a Web Service. Create a Service Account that will be local admin of the server on which you install the software. Set the credentials and click on Next.![]()
The installation is now in progress, it will install the application, but it will also automatically import/upgrade the NetApp management packs to the Operations Manager Infrastructure.![]()
Start the SCOM Console, the installation process automatically installed the new the NetApp Management packs. /! If you were previously using the Netapp management pack, extract your custom management pack because the upgrade will simply remove it, which could be really frustrating. After the upgrade, you are able to reinstall it. It seems that NetApp changed some class, be sure to check that your overrides are well targeting the right classes./! ![]()
The next step is to add the Netapp Controllers as Network device. Go to Administration > Network Devices > Discovery Wizard. Specified the IP range and start the discovery. ![]()
The controllers have been discovered as SNMP devices. Select all the controllers and click Finish. ![]()
Go to Monitoring > Data ONTAP > Storage Systems > Management Server, choose the root management server that will monitor your Netapp infrastructure and run the Data ONTAP : Run Discovery Task.
After a few moments, the Netapp Controllers will automatically appear in the Data Ontap > Storage Systems > Controllers view. ![]()
Extend the actions pane and click on Data ONTAP : Manage Controller Credentials task. ![]()
This will start the Netapp Credentials Manager, where we have to specify the credentials for all the NetApp Controllers. ![]()
When done, go back to the SCOM console, Go to the Authoring section > Management Pack Objects > Rules and search for the Data ONTAP: Discovery Rule.
This is the principal discovery rule for all Data ONTAP storage systems. Once you use the SNMP network device Discovery wizard in System Center Operations Manager to discover your Data ONTAP storage controllers, this rule contacts each storage controller and discovers all of its physical and logical storage elements.
This rule is disabled by default. You should enable the rule, via an override, for the management server that will monitor your Data ONTAP storage controllers.![]()
After a few moments, the entire infrastructure will be discovered and all the views will be populated. ![]()
operations manager · opsmgr · Scom
No comments yet.
Leave a Reply
<< SCOM / OpsMgr : Moving the Operations Manager DB – Notes from the field
