This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Discovery 11.3
Discovery does not sync the Host memory "logical ram" attribute to CMDB
Discovery has two fields for memory - "logical_ram" and "ram". The CMDB sync takes the ram attribute and populates the TotalPhysicalMemory field on the BMC_ComputerSystem class. However, the CMDB doesn't have a "logical ram" field, so this is not sync'd.
It is often the case with VMs that logical_ram is the only thing that can be discovered. In this case, there are two choices:
- Write a CMDB sync extension pattern to push "logical_ram" to the TotalPhysicalMemory field. There are two problems with this: first, since logical RAM is not the same as pyhsical RAM, the pattern would essentially be putting an invalid value in this field. Also, the pattern could override the use of physical RAM for systems where it does exist. This could be avoided this by adding some logic to use logical_ram only if ram is not available.
- A better choice may be to add a new custom attribute to CMDB for logical RAM, the write a CMDB sync extension pattern to push "logical_ram" to the new field.
See attached for a sample pattern. Please note that sample patterns are provided as examples only. Writing/troubleshooting custom patterns are considered to be user customizations and are not within the scope of customer support.
This has been discussed before on communities, where more info and additional sample patterns can be found: