OCPM 4.1 not properly discovering storage utilization

mrp — Thu, 05 Jun 2025 05:15:28 GMT

I am having literally the exact same issue as this user posted in the old forums: https://forums.netapp.com/message/139343#139343

I have built up a new SCOM 2012 R2 environment with OCPM 4.1. I have added our controllers and put in credentials for each controllers. Discovery appears to have worked fine and I am seeing aggregates, volumes, LUNs and qtrees but nothing in the committed % column for aggregates, or used space/current savings/storage efficiency for volumes in the state views on the monitoring pane (exactly as the original poster shows in the link above). I am also not seeing anything on the storage utilization dashboard. I am connecting to my controllers using the root account. Is there something else I am missing to unlock all the info in SCOM? The one reply in the OP's thread mentions "storage permissions for basic monitoring". Does this apply when using the root account?

For reference, I am working on setting up monitoring for two of our FAS3250 controllers running 8.2.1 7-mode.

EDIT: I am not using SCVMM or Orchestrator. Not sure how the PRO stuff in that article applies if I don't used these.

Re: OCPM 4.1 not properly discovering storage utilization

vinith — Fri, 30 Jan 2015 03:58:14 GMT

Please have a look at OCPM 4.1 BPG, it contains steps on setting up permissions, http://www.netapp.com/us/system/pdf-reader.aspx?pdfuri=tcm:10-130633-16&m=tr-4354.pdf&q=ocpm&cp=1.

Let me know if you need any further help.

Re: OCPM 4.1 not properly discovering storage utilization

mrp — Fri, 27 Feb 2015 18:09:09 GMT

I had an issue with my SQL database which was causing the issue. I needed to increase the size of my SCOM database which resolved the issue, I am now getting storage utilization.

topic Re: OCPM 4.1 not properly discovering storage utilization in Microsoft Virtualization Discussions

OCPM 4.1 not properly discovering storage utilization

Re: OCPM 4.1 not properly discovering storage utilization

Re: OCPM 4.1 not properly discovering storage utilization