Memory speed value mismatch between webui and winrm

[MPala11]

Hi,
I'm trying to enumerate CIM_PhysicalMemory using winrm and getting details as below
===========

CIM_PhysicalMemory
BankLabel = BANK 0
Capacity = 2147483648
CreationClassName = CIM_PhysicalMemory
ElementName = Managed System Memory Chip
FormFactor = 13
Manufacturer = 830B
MemoryType = 24
PartNumber =xxxx
SerialNumber =xxx
Speed = 0
Tag = 9876543210

CIM_PhysicalMemory
BankLabel = BANK 2
Capacity = 4294967296
CreationClassName = CIM_PhysicalMemory
ElementName = Managed System Memory Chip
FormFactor = 13
Manufacturer = Kingston
MemoryType = 24
PartNumber =xxxx
SerialNumber =xxx
Speed = 0
Tag = 9876543210 (#2)
===================
Speed is always coming as 0 only, but if i check through webui(http://ipaddress:16992) speed is showing as 1333 MHZ.All other values are matching except Speed, Why there is difference in speed value between Soap API and WS-Man

Thanks,
Mani

[Gael_H_Intel]

I will look into this - sorry for the delay. I was out last week.

[Gael_H_Intel]

It is odd that WS-MAN would be returning a 0 for speed... Could you try using PowerShell? Here is a blog on how to run the powshell snippets and where to get it:http://software.intel.com/en-us/blogs/2011/05/16/using-powershell-drives-to-manage-intel-amt/?wapkw=powershell+module

Unless there is some kind of coding issue, it is strange that you would be seeing different results.

[MPala11]

Hi Gael,
In powershell also it's coming as 0 only. Please check memory details below

10.0.6.109 Memory
10.0.6.109 Memory:Memory 0
Access.............. Read/Write Supported
BlockSize........... 1
ConsumableBlocks.... 4294967296
NumberOfBlocks...... 4294967296
Volatile............ True
10.0.6.109 Memory:Devices
10.0.6.109 Memory:Devices: (#1)
BankLabel........... BANK2
Capacity............ 1073741824
FormFactor.......... TSOP
Manufacturer........ Kingston
MemoryType.......... DDR3
PartNumber..........xxxxxxx
SerialNumber........ 2908079
Speed............... 0
Tag................. (#1)
10.0.6.109 Memory:Devices: (#2)
BankLabel........... BANK3
Capacity............ 1073741824
FormFactor.......... TSOP
Manufacturer........ Kingston
MemoryType.......... DDR3
PartNumber.......... xxxxx
SerialNumber........ 5307E17
Speed............... 0
Tag................. (#2)
10.0.6.109 Memory:Devices: (#3)
BankLabel........... BANK4
Capacity............ 1073741824
FormFactor.......... TSOP
Manufacturer........ Kingston
MemoryType.......... DDR3
PartNumber..........xxxxxxx
SerialNumber........ 8308459
Speed............... 0
Tag................. (#3)
10.0.6.109 Memory:Devices:CIM_PhysicalMemory Tag
BankLabel........... BANK1
Capacity............ 1073741824
FormFactor.......... TSOP
Manufacturer........ Kingston
MemoryType.......... DDR3
PartNumber..........xxxxxxxxxx
SerialNumber........ 8308C39
Speed............... 0
Tag................. CIM_PhysicalMemory Tag

Thanks,
Mani

[Gael_H_Intel]

Interestesting.

I thought you had provided the xml file from running the SCS Discovery tool - but perhaps not (maybe that was from a different question.) Could you run the tool and send it over so I can see what your components are?

How to run the SCS Discovery Tool (version 8 is there)

Note that we have done a refresh on the site:

New, AMT 8 SDK.

Updated DTK (still version 7 but has fixes.)

New SCS (the link is in my blog, above)

-----

UPDATE:

I tested the latest DTK on my AMT 8 system and it is also being displayed as 0 - whether I select WS-MAN or not. This is sounding like a FW issue. Can you check your OEM site to ensure you have the latest FW on your system?

--Gael

[Ylian_S_Intel]

I looked into it a little and this seems like a firmware issue. I do get the correct memory speed using SOAP, but get 0 with WS-MAN. I tested this on an Intel AMT 5.0 machine. I had seen this a while back and changed the OpenDTK code to hide the speed of memory when it's zero.

Ylian
OpenDTK

[Gael_H_Intel]

And just so you know, I escalated this to our AMT Developement team as well and am waiting to hear back from them.

Gael

[Gael_H_Intel]

For a brief update, this is a known issue. There seems to be a problem with the DMTF standard and the API cannot handle values greater than 1000 - so if thats the case, 0 gets reported. That's why it works with SOAP and that's why if you bring up the WebUI (which is just a web server that displays info directly from the ME) it gets reported correctly.

At one point there was a WSMAN API that would result in the correct values but it was beta at the time the AMT SDK was being worked on and so we couldn't include it. Sorry if this is a little "sketchy" - I will provide more updates as I get them.

[MPala11]

Thanks Gael for the update. Please let me know once the issue is fixed

Cheers,
Mani