Highlighted
Super Contributor.
Super Contributor.
750 views

difference in the physical memory size

Hi Team,

 

I have a question about the physical memory. It looks like the Host resource and application by Shell job is discovering only the C: drive and not the rest of the space like D or E drive

 

Example: We have 800GB in a server but the physical memory size shows as 16 GB (16771724 MB in UCMDB).  I have checked the comm logs and see a lot of things and not sure how to proceed. Please find it attached.

 

I am confused on how the physical memory size is being calculated in UCMDB. Can anyone help me understand this concept please.

 

Thank you.

 

Regards

Mathew

 

 

 

 

0 Likes
8 Replies
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: difference in the physical memory size

Several questions:

-Which CP

-Which CIT and attribute we are talking about?

 

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: difference in the physical memory size

Hi Dima,

 

UCMDB 9.05 CUP 12.351 and CP 11.10.828

 

CIT: FileSystem and Attribute is : file system size

 

 

Regards

Mathew

0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: difference in the physical memory size

Hi Dima/Team,

 

Any thoughts on this one?

 

Regards

Mathew

0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: difference in the physical memory size

As an update, I cross checked with my Dev server which is on 10.01 CUP 2.145 and CP 12.0.825 and found the same issue.

Only C drive physical memory space is being discovered not the other drives.

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: difference in the physical memory size

We'll need to see comm log with results. If you concering publishing here please send it in PM or attach to support case.

FYI, I can't find known issue...

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: difference in the physical memory size

Hi Dima,

 

I have shared the comm log but will raise a request too.

 

Thank you.

 

Regards

Mathew

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: difference in the physical memory size

 

According to provided log the destination has 4 logical disks

 

 <log start="3:28:50" severity="debug">found disk: C, sizeInMB=20245, freespace=6843125760, type=3</log>
 <log start="3:28:50" severity="debug">found disk: D, sizeInMB=49089, freespace=45116162048, type=3</log>
 <log start="3:28:50" severity="debug">found disk: E, sizeInMB=856700, freespace=898101587968, type=3</log>
 <log start="3:28:50" severity="debug">found disk: F, sizeInMB=0, freespace=0, type=5</log>

 

It was received from WMI request:

CMD>[CDATA&colon; wmic path win32_logicaldisk get ProviderName, deviceId, driveType, freespace, size /value &lt; %SystemRoot%\win.ini]</CMD>
  <RESULT>[CDATA&colon;

 

 

DeviceID=C: DriveType=3 FreeSpace=6843125760 ProviderName= Size=21229447168
DeviceID=D: DriveType=3 FreeSpace=45116162048 ProviderName= Size=51473801216

DeviceID=E: DriveType=3 FreeSpace=898101587968 ProviderName= Size=898315694080

DeviceID=F: DriveType=5 FreeSpace= ProviderName= Size=]

 

You could try to check the answer on the destination perfoming "Select * from Win32_LogicalDisk" in WMI Explorer http://www.hostmonitor.biz/download/wmiexplorer.zip.

 

At the end of the script we could see that following CI were sent back to  UCMDB:

    <object class="disk" isReference="false" is_anchor="false">
     <attribute name="root_container" type="host">
      <object id="71fd50015fccdfa37b13e8642004faa6" id_type="CmdbObjectID" class="host" isReference="false" is_anchor="false" />
     </attribute>
     <attribute name="disk_type" type="String">FixedDisk</attribute>
     <attribute name="disk_size" type="Double">20245.0</attribute>
     <attribute name="name" type="String">C</attribute>
     <attribute name="data_name" type="String">C</attribute>
    </object>
    <object class="disk" isReference="false" is_anchor="false">
     <attribute name="root_container" type="host">
      <object id="71fd50015fccdfa37b13e8642004faa6" id_type="CmdbObjectID" class="host" isReference="false" is_anchor="false" />
     </attribute>
     <attribute name="disk_type" type="String">FixedDisk</attribute>
     <attribute name="disk_size" type="Double">49089.0</attribute>
     <attribute name="name" type="String">D</attribute>
     <attribute name="data_name" type="String">D</attribute>
    </object>
    <object class="disk" isReference="false" is_anchor="false">
     <attribute name="root_container" type="host">
      <object id="71fd50015fccdfa37b13e8642004faa6" id_type="CmdbObjectID" class="host" isReference="false" is_anchor="false" />
     </attribute>
     <attribute name="disk_type" type="String">FixedDisk</attribute>
     <attribute name="disk_size" type="Double">856700.0</attribute>
     <attribute name="name" type="String">E</attribute>
     <attribute name="data_name" type="String">E</attribute>
    </object>

 

Next steps:

 

We need to check if this data was went through redandant filter and then check cmdb.reconciliation.audit.log on server side  to see that info was inserted into UCMDB. 

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: difference in the physical memory size

Hi Dima,

 

Thank you looking into this issue and for the heads up. I am trying to check the cmdb.reconciliation.audit.log file if UCMDB has inserted the information.

 

Regards

Mathew

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.