A few weeks ago NetApp released their management pack also called “OnCommand Plug-In 3.1 for Microsoft” (OCPM) for SCOM 2012. This week I got the chance to install the latest NetApp MP 3.1. Here I would like to share my experience…
Requirements
- Data ONTAP requirements Data ONTAP 7 product family, operating in 7-Mode:
7.3 or later
7.3.3 or later for MultiStore support - Data ONTAP 8 product family operating in 7-Mode:
8.0.1, 8.0.2, and 8.0.3
8.1.0 and 8.1.1
You cannot upgrade automatically from OnCommand Plug-in 3.0 for Microsoft to OnCommand Plug-in 3.1 for Microsoft. To correctly install OnCommand Plug-In 3.1 for Microsoft, you must first uninstall any earlier versions of OCPM. The installer will prompt during installation and exit if older versions are found. Also, make sure that firewalls, proxies, or other network devices do not interfere with traffic. The required ports are SNMP, and HTTP or HTTPS. Remote operations also require that Windows Web services be enabled. This uses port 808 by default.
Prior to execute the setup I have each of the controller discovered as SNMP device using the SNMP discovery wizard in SCOM. They appear under “Network Devices” in SCOM.
Installation
Execute the OnCommand-PlugIn-Microsoft_3.1_x64_NetApp.exe…
Click “Next”…
Choose the destination folder, I leave the defaults…
The OnCommand Plug-In 3.1 provides support for Orchestrator and you could also install a “Discovery Agent” which is a Windows Management Instrumentation (WMI) provider to assist you with SCOM host discovery, provisioning, cloning, and disaster recovery cmdlet functionality used on Hyper-V hosts. We are just selecting the “SCOM Management Packs” and “Documentation (optional)”…
OnCommand Plug-In 3.1 installs a Web Service which needs a local administrator account…
I added the SRVNetAppWS account to the local administrator group on the management server…
“Install”…
“Finish”…
The setup installs several management packs automatically…
Next I run the “Data ONTAP Add Controller” task…
We need to add the community string and the IP for each controller…
Now we have added the controllers and they should appear if you run the “Data ONTAP Manage Controller Credentials” Task…
Add for each controller the user name and password using an account which has appropriate permission. For basic monitoring you need the following minimal permissions…
|
|
 |
Finally you should have on every controller a green check mark…
Next we need to enable the automatic discovery which runs every 24h. Select “Data ONTAP Discovery Rule”…
…and override the discovery “For all object of class: Management Server”.
Set the parameter “Enabled” to value “True” and save it into a dedicated management pack…
Now we are ready to run the “Data ONTAP Run Discovery task”…
If your permission for the task are set properly your task will end in success. Short after all the NetApp objects will be discovered…
Views
After a successful installation you will get several views as you can see in the monitoring pane…
Besides all the state views I uploaded the diagram view so you get an idea what is being discovered. Go here to get the diagram view.
Reports
The installation wizards also deploys several reports. The “OnCommand Data ONTAP Reports”…
and “OnCommand Data ONTAP Virtualization Reports” which just make sense if you implemented the virtualization part of this plug-in completely.
Well, this is a brief overview of the “OnCommand Plug-In 3.1 for Microsoft” from NetApp.
I hope it helps!
Cheers,
Stefan
Hi,
Thanks for write this info, I made the installation, but the management pack “oncommand data onta pro” was not automatically imported. do you know if there any way that I can import it manually?
Also on the monitoring tab I have some empty values like on Volumes (Used space, Current Savings%, Storage efficiency%) how long takes scom 2012 to populate this info?
Hi
I would check the installation directory for missing management packs. The setup wizard imports the management packs automatically. The default installation directory is “C:Program FilesNetAppOnCommandMS_Plugin” check it if there are the missing files and import it using the SCOM wizard.
Today I installed the MP for a customer SCOM infrastructure, it took about 5-10 minutes until I saw some stuff discovered and I guess it took up to an hour until most of the objects appeared.
Regards,
Stefan
Hi Stefan,
I found the mp on the installation directory, when trying to import it manually it says that it have these dependencies:
Microsoft.SystemCenter.VirtualMachineManager.Library
Microsoft.SystemCenter.VirtualMachineManager.Pro.Library
Microsoft.SystemCenter.VirtualMachineManager.Pro.V2.Library
So it seems that I have to install the system center virtual machine manager
management pack.
Thanks.
We only have NetApp NAS , will this work for NAS or only works for SAN
Hi Kitaab
You can use this MP for NetApp storage systems which have the Data ONTAP OS installed as described in the prerequisite. Those systems can be configured as NAS and SAN as far I know.
Regards,
Stefan
When i try to click on Task Data ONTAP:Add Controller
I get the following error
—————————
Operations Manager
—————————
Application: %OCSCOMPATH%OC.OM.Management.Controller.AddController.exe
Parameters:
Error Message: The system cannot find the file specified
However I could find the files Present at C:Program FilesNetAppOnCommandMS_Plugin
And ran them manually
Also I could not Find data OnTAP discovery rule that you enabled.
however when i clicked on run discovery task , it did run fine.
Hi Kitaab
Concerning the error, you can only start the task on that management Server where you have installed the ONTAP plug-in. After Installation you might have to close and re-open the SCOM console.
The discovery rule is a rule not a discovery. Therefore you need to look in the rule section in the SCOM console.
Cheers,
Stefan
Thanks Once i closed and Re-open the console , The tasks did work fine.
I did looked into the Rules and not discoveries and didn’t find that
But as mentioned , the controllers are being monitored fine,
Has anyone come across any issues when trying to install the Data ONTAP PRO Management Pack? It did not install automatically so I tried to install it manually. But I get an error stating that dependent management packs are missing.
The missing MP’s are VMM Library packs:
Microsoft.SystemCenter.VirtualMachineManager.Library
Microsoft.SystemCenter.VirtualMachineManager.Pro.Library
Microsoft.SystemCenter.VirtualMachineManager.Pro.V2.Library
all of them are at version 3.0.6005.0. I am unable to find these MP’s anywhere – the only version I can find is version 2.0.3451.0.
Does anyone know what I can do?
Hi Oliver
Here you could find the latest MP http://systemcenter.pinpoint.microsoft.com/en-US/applications/monitoring-pack-for-system-center-2012-virtual-machine-manager-12884940307 . Did you try those?
Regards,
Stefan
Hi Stefan
Many thanks for your reply. I couldnt find the latest MP anywhere, but the link you provided has worked.
Regards,
Oliver
Look Above you have to install scvmm there are in the install dir the needet mp’s it tooks me also a day to find. but well now im stucking on the discovery task.
Maybe some one have an idea?.
Now we are ready to run the “Data ONTAP Run Discovery task”… is ending up with an error.
Im just a bit unsure witch credentials i have to put in for the discovery taks. i let it by default. after the timout witch i can also set im getting the following error:
The Event Policy for the process started at 16:15:55 has detected errors in the output. The ‘StdErr’ policy expression:
a+
matched the following output:
C:Program FilesSystem Center 2012Operations ManagerServerHealth Service StateMonitoring Host Temporary Files 73160ONTAPDiscovery.vbs(61, 3) OC.OM.Server: DataONTAP discovery – caught exception during commit.
Command executed: “C:Windowssystem32cscript.exe” /nologo “ONTAPDiscovery.vbs” xxxxxxxx.xxx.local
Working Directory: C:Program FilesSystem Center 2012Operations ManagerServerHealth Service StateMonitoring Host Temporary Files 73160
One or more workflows were affected by this.
Workflow name: DataONTAP.Discovery.Task
Instance name: xxxxxxx.xxx.local
Instance ID: {FD74BB05-6E25-88C8-C63E-B52ACE75D27C}
Management group: xxx
Error Code: -2130771918 (Unknown error (0x80ff0032)).
Sorry never minde…. fu … netapp.. thy told me to create an role on the netapp with the following rights: Create Role
useradmin role add scom -a login-http-admin,api-system-get-version,api-system-get-info,api-system-get-vendor-info,api-cf-status,api-system-get-ontapi-version,api-vfiler-list-info,api-ems-autosupport-log,api-aggr-list-info,api-volume-list-info,api-lun-list-info,api-disk-list-info,api-storage-shelf-list-info,api-license-list-info,api-lun-map-list-info,api-volume-autosize-get,api-aggr-options-list-info,api-qtree-list,api-storage-shelf-environment-list-info,api-lun-get-space-reservation-info,api-volume-options-list-info,api-perf-object-get-instances,api-snmp-get,api-snapmirror-get-status,api-quota-report-iter-start,api-quota-report-iter-next
this is crap with this role rights you cant do the discovery …. thx netapp
Hi,
I am getting the same error as you received.
The Event Policy for the process started at 6:13:08 AM has detected errors in the output. The ‘StdErr’ policy expression:
a+
matched the following output:
C:Program FilesSystem Center 2012Operations ManagerServerHealth Service StateMonitoring Host Temporary Files 2608910ONTAPDiscovery.vbs(61, 19) OC.OM.Server: DataONTAP discovery – caught exception during commit.
Command executed: “C:Windowssystem32cscript.exe” /nologo “ONTAPDiscovery.vbs” NCDSANOM01MS.dev.sd.local
Working Directory: C:Program FilesSystem Center 2012Operations ManagerServerHealth Service StateMonitoring Host Temporary Files 2608910
One or more workflows were affected by this.
Workflow name: DataONTAP.Discovery.Task
Instance name: NCDSANOM01MS.dev.sd.local
Instance ID: {0F00F744-4332-8081-F105-F5C5D915DFEE}
Management group: SDSCOM12
Error Code: -2130771918 (Unknown error (0x80ff0032)).
I see that you posted
netapp.. thy told me to create an role on the netapp with the following rights: Create Role
useradmin role add scom -a login-http-admin,api-system-get-version,api-system-get-info,api-system-get-vendor-info,api-cf-status,api-system-get-ontapi-version,api-vfiler-list-info,api-ems-autosupport-log,api-aggr-list-info,api-volume-list-info,api-lun-list-info,api-disk-list-info,api-storage-shelf-list-info,api-license-list-info,api-lun-map-list-info,api-volume-autosize-get,api-aggr-options-list-info,api-qtree-list,api-storage-shelf-environment-list-info,api-lun-get-space-reservation-info,api-volume-options-list-info,api-perf-object-get-instances,api-snmp-get,api-snapmirror-get-status,api-quota-report-iter-start,api-quota-report-iter-next
this is crap with this role rights you cant do the discovery …. thx netapp
Can you elaborate on this as I am not able to figure it out how to resolve this isssue ? Appreciate your help….
I am seeing the exact error reported by Maheshwer and Sanktis, Has anyone developed a resolution to this? Many thanks.
nice article.
We have installed and configured netapp 3.1 on SCOM 2012 succesfully, but the alerts seems to be not having detail information. for example LUN latency alert, it just says “Please see alert context for details”. only in alert context we can see the values in SCOM console. we are also not able to add alert context in SCOM notification, same is the case for volume space related alerts also. is it same for you? or did I miss anything? pls suggest.
Hi,
I have this scenario, Two different servers as Management Server, and other server with the SQL Server and two instance for Operational Database and the DataWarehouse Database.
When I install the plug-in in one of the management servers, the wizar finish Ok, but in SCOM I can’t view the reports of OnCommand created.
The scenario is:
-Windows Server 2008 R2 SP1 for all servers.
-SCOM 2012 RTM
-SQL 2008 R2 RTM
Could anyone help me? Something about rights?
J.
Hi, I’m unable to monitor the snapmirror, do you know if there is something that have to be changed on the MP? I see the rules and monitors for snapmirror and are enabled, but the view is empty
Thanks for the write up. Does the 24 hour discovery interval mean an alert could be a day old (and then another 24 hours for an alert to clear)? I was thinking of changing this value to 1 hour or even 30 minutes. I also setup SNMP alert destinations on the NetApp to my 2 management servers.
Anyone have some real world experience with this setting? I’m on the latest 4.0 version of the OnCommand Plug-in. Thanks!!
Hi
The discovery interval determines only how Long it takes to discover your NetApp Controllers. It has nothing to do with alerting. If you set this value lower it takes less time until objects appear in SCOM. Don’t change this value, running this discovery once a day is efficient and sufficent.
Cheers,
Stefan
Hi Stephan,
We had installed OCPM 3.2 in our SCOM environment. We had some issues with object discovered, I mean for some devices volumes are not appearing unde monitoring –>volumes tab. However under controller tabs its showing the device is discovered.
Regards,
Daya Ram
Just a word of caution about this MP/Plug-In, we’ve found that some of the rules that run/sync each day, actually Close all open alerts, ie. Data ONTAP: Volume Space Utilization (%) monitoring, then after a few minutes all of the closed alerts will re-open. This can cause 2 alert storms: 1. for Closed alerts 2. for New alerts. NetApp tech support states that because the re-sync rule, the one that syncs up with the NetApp controllers every so often (ie. every night), basically clears all such open alerts and then reopens them when it discovers threshold breaches. According to NetApp tech support, this is by design. I believe it is a flaw, but there is no word on whether or not they will fix or enhance this so that open alerts stay open and the repeat count gets incremented.
Anyone received similar issue and resolved ?
The Event Policy for the process started at 4:04:42 AM has detected errors in the output. The ‘StdErr’ policy expression:
a+
matched the following output:
C:Program FilesSystem Center 2012Operations ManagerServerHealth Service StateMonitoring Host Temporary Files 177864ONTAPDiscovery.vbs(61, 19) OC.OM.Server: DataONTAP discovery – caught exception during commit.
Command executed: “C:Windowssystem32cscript.exe” /nologo “ONTAPDiscovery.vbs” NCDSANOM01MS.dev.sd.local
Working Directory: C:Program FilesSystem Center 2012Operations ManagerServerHealth Service StateMonitoring Host Temporary Files 177864
One or more workflows were affected by this.
Workflow name: DataONTAP.Discovery.Task
Instance name: NCDSANOM01MS.dev.sd.local
Instance ID: {0F00F744-4332-8081-F105-F5C5D915DFEE}
Management group: SDSCOM12
Error Code: -2130771918 (Unknown error (0x80ff0032)).
Is this a free MP (NetApp OnCommand Plug-in 3.1)? or one need to pay licence for it?
Hi
It is free for NetApp customers.
Cheers,
Stefan
Does the ONTAP discovery/monitoring work on Gateway Managed Sites (untrusted forest)? I’m trying to delegate the discovery/monitoring task to the Gateway server on the site where the Netapp is but without success.
I followed all the recommendations on the installation guide.
I always get: ActiveX component can’t create object: ‘NetApp.OM.Server.Discovery.StorageDiscovery’.
Only 5723 TCP Communication between Gateway and MS.
@ricardosgarrido
did you succeed to install it without opening ports between the untrusted zones?
Hello Stefan,
hello everyone,
Does anyone have the same issue with hundreds of connectors installed from the Netapp MP?
https://community.netapp.com/t5/Data-ONTAP-Discussions/OnCommand-Clustered-Data-ONTAP-4-1-1-7474-SCOM-Internal-Connectors/td-p/122268
Did anybody solve and is still using the MP?
Cheers from far away
Tobias