I have a customer who has a NetApp cluster with FAS8040s running 8.2.1 in cluster-mode. The have SCOM 2012 R2 UR6 and the OnCommand 4.1 SCOM plug-ins. I can do an initial discovery of the cluster and it pulls back the SVM, but no other objects are discovered...no LIFs, no Nodes, no Volumes etc.
I've been over the install doc many times and have not found where I might be doing something wrong. I've also searched on the interwebs and found a few suggestions, but none have changed the outcome.
I've ensured the overrides are appropriate and to be sure its not a rights thing, I'm using "the" admin account. I see no indication of issues in:
The SQL side is fine and the account is cluster scoped, but you do make me wonder if the problem lies in the fact that they set the account up locally, rather than as a domain account and thats causing issues with SCOM getting the information. I'm working with my customer to reveiw the account used. I'll report back when I know if that is the answer or not.
Log Name: Operations Manager Source: Health Service Modules Date: 8/3/2015 6:27:00 PM Event ID: 22406 Task Category: None Level: Error Keywords: Classic User: N/A Computer: SCOM_SERVER Description: The PowerShell script failed with below exception
System.Management.Automation.MethodInvocationException: Exception calling "CreateDomain" with "3" argument(s): "The specified user does not have a valid profile. Unable to load 'Microsoft.EnterpriseManagement.HealthService.Internal, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=121212121212121212'."At line:40 char:12 + return [AppDomain]::CreateDomain("OC.Cluster.OM.Powershell.NonDefaultAppDoma ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ at System.Management.Automation.ExceptionHandlingOps.ConvertToMethodInvocationException(Exception exception, Type typeToThrow, String methodName, Int32 numArgs, MemberInfo memberInfo) at CallSite.Target(Closure , CallSite , RuntimeType , String , Object , Object ) at System.Dynamic.UpdateDelegates.UpdateAndExecute4[T0,T1,T2,T3,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3) at System.Management.Automation.Interpreter.DynamicInstruction`5.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
Sorry for the delay, I was out of town with another customer.
Thanks for the reply and the link. I'd seen that earlier in my search to find an answer and I'm fairly certain the ID is set up properly. As I indicated in an earlier reply, I moved to using a domain account specifically to allow me to log into the SCOM server with that ID and build the local profile.
Is there some mechanism I can use to verfy that the ID I've put in as the default action account, the configured account for the storage system, or some other account is being used by the discovery rules?