S2D seed is not discovered in SCOM

Question

Dear all,

I have encountered the difficulties of SCOM monitoring Storage Spaces direct.

Created Custer cl1 with 2 nodes cl1n1 and cl1n2. Installed the SCOM agents on both nodes and activated the agent proxy on these nodes.

Used a domain account as Agent Action Account that is a member of the local administrator's group on both Cluster nodes.

MP I imported:

I left these profiles empty.

As result S2S seed is not discovered in SCOM. All other S2D components are not discovered too.

Please tell me what I'm doing wrong? How to set up S2D monitoring in SCOM

Answer 1

The problem has been solved. On cluster in hclm\cluster "OSVersion" was set to "10 (17763)". S2Dseeddiscovery.ps1 script expects 10.0* value at "OSVersion". S2D discovery script start working after changing the OSVersion to the "correct" value.

Answer 2

Hi,

It sounds like you're having a tough time getting Storage Spaces Direct (S2D) to be properly discovered in SCOM.

Here are a few steps and checks that might help resolve the issue:

• Ensure that you have imported the correct and latest version of the S2D Management Pack for your SCOM version.
• Storage Spaces Direct Management Pack for Windows Server 2016 and above
• Review the SCOM event logs on the management server and the cluster nodes for any errors or warnings that might indicate what is going wrong.
• Monitor Windows Storage Spaces Direct 2016/2019 with SCOM Management Pack
• If the S2D components are still not discovered, consider removing and re-adding the cluster nodes in SCOM.

I hope these steps help you get S2D monitoring up and running in SCOM. Let me know if you need further assistance or if there's anything else I can help with!