The memory data in the snmpagent on the ESX Servers are reported by the Host Resources MIB and contained in the oids below
hrStorageType, 1.3.6.1.2.1.25.2.3.1.2
.<Index> = 1.3.6.1.2.1.25.2.1.20 This response translates to "Real Memory"
hrStorageDescr = 1.3.6.1.2.1.25.2.3.1.3. look for the Index that has this value 5265616C204D656D6F7279 the Hex equivalent Real Memory
The corresponding Index found above should also have values for these three oids as well that smarts will use to calculate utilization.
hrStorageSize = "1.3.6.1.2.1.25.2.3.1.5",
hrStorageUsed = "1.3.6.1.2.1.25.2.3.1.6",
hrStorageAllocationUnits = "1.3.6.1.2.1.25.2.3.1.4"
The snap file that I reviewed reported the following:
.1.3.6.1.2.1.25.2.3.1.2.29|.1.3.6.1.2.1.25.2.1.20|
.1.3.6.1.2.1.25.2.3.1.3.29|5265616C204D656D6F7279|
.1.3.6.1.2.1.25.2.3.1.4.29|1024|
.1.3.6.1.2.1.25.2.3.1.5.29|402554112|
.1.3.6.1.2.1.25.2.3.1.6.29|316335308|
As you can see this data is in the Host Resources Storage / Filesystem data. This is why you will not see memory reflected in the topology for Smarts IP. The memory is monitored by the following FileSystem_Performance_HostResources instrumentation.
The default Filesystem Performance Thresholds do not include any members by default. To resolve you will need to setup matching criteria in the File Systems.
Default Threshold values are ModerateUtilizationPct: 80, MaxUtilizationPct: 95 in Smarts IP. IN P&T of IP domain for FileSystem has matching Criteria as '~' instead of '' hence none of the ESX Servers are members of this group.