Solaris 10 memory Information

Question

SCOM 2012 :   1.4.1-278
Hi All,  after installing on Solaris 10 - LDOMS.  I noticed I was getting erroneous "Memory Information" on most servers. 
AvailableMemory   17592186058094
UsedMemory        18446726481523518098
After some  jiggery pokery, I realised that if I have a ZFS file system on the server with at least
100 MB used in a fileset, the "Memory Information will report correctly.
AvailableMemory   13780
UsedMemory        10796
Only the servers without ZFS have the problem. Or ZFS with something less than 100 MB used.
Does anyone have any idea how the  task/monitor collects this data ( kstat, mdb ?? )
Is there any way to override this. ?
Solution at the moment is creating a zpool on a mkfile with a zfs fileset, and another 100M file in it.
Thanking you.

Answer 1

The agent uses kstat under the covers to collect the data and there is no way to override it unless you just want to disable it. My guess here is that there is an issue with the calculation of the memory in the scenarios you describe but without getting
trace logging it will be difficult to determine.
What other types of file systems are on the Solaris LDOMS?
I see you are running the [1.4.1-278] agent. There is a newer agent [1.4.1-292] that can be downloaded from here -->
http://www.microsoft.com/en-us/download/details.aspx?id=29696, can you give this agent a try on one of the Solaris systems and see if you still have the issues?
You can turn on trace logging by running [scxadmin -log-set ALL verbose] on the agents. The logs are under /var/opt/microsoft/scx/log. Run the following winrm query from a command prompt on the SCOM server and look through the logs to see if it gives any
idea what is going on.
winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_FileSystem?__cimnamespace=root/scx -username:<unix user> -password:<unix password> -r:https://<solaris system>:1270/wsman -auth:basic -skipCACheck -skipCNCheck -skiprevocationcheck -encoding:utf-8
To turn off trace logging run [scxadmin -log-reset] on the agent.
If any of the above does not resolve the issue I would open a support case with Microsoft and we will work directly with you to try to resolve the issue.
Regards,
-Steve