Another interesting question, why does each socket show two different IDs?
SocketID ISetID PersistentMemoryType Capacity FreeCapacity HealthState 0 0xa354da902f248a22 AppDirectNotInterleaved 126.0 GiB 126.0 GiB Healthy 0 0x5190da905a2a8a22 AppDirectNotInterleaved 126.0 GiB 126.0 GiB Healthy 1 0x3fa4da90a52c8a22 AppDirectNotInterleaved 126.0 GiB 126.0 GiB Healthy 1 0xd590da90b42a8a22 AppDirectNotInterleaved 126.0 GiB 126.0 GiB Healthy
From your description, you're using 128Gb NVDIMMs so why does socket 0 show two different IDs?
I'm only asking because these are entirely new to me. Is Socket 0 actually a pair of DIMM slots so Socket 0 = 2x 128GB NVDIMMs??
Another interesting question, why does each socket show two different IDs?
SocketID ISetID PersistentMemor yType Capacity FreeCapacity HealthState erleaved 126.0 GiB 126.0 GiB Healthy erleaved 126.0 GiB 126.0 GiB Healthy erleaved 126.0 GiB 126.0 GiB Healthy erleaved 126.0 GiB 126.0 GiB Healthy
0 0xa354da902f248a22 AppDirectNotInt
0 0x5190da905a2a8a22 AppDirectNotInt
1 0x3fa4da90a52c8a22 AppDirectNotInt
1 0xd590da90b42a8a22 AppDirectNotInt
From your description, you're using 128Gb NVDIMMs so why does socket 0 show two different IDs?
I'm only asking because these are entirely new to me. Is Socket 0 actually a pair of DIMM slots so Socket 0 = 2x 128GB NVDIMMs??