Dell PowerEdge R740 EMC NVDIMM-N Persistent Memory User Guide - Page 40

PowerShell Cmdlets, NVDIMM-N Interleaving

Get Dell PowerEdge R740 PDF manuals and user guides View all Dell PowerEdge R740 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 40 highlights

PowerShell Cmdlets #Get-PmemDisk • Returns one or more logical persistent memory disks. • The returned object has information about size, atomicity type, health status, and underlying physical devices. #Get-PmemPhysicalDevice • Returns one or more physical persistent memory devices (NVDIMMs). • The returned object has information about size(s), RFIC, device location, and health/operational status. #New-PmemDisk • Creates a new disk out of a given unused region. • Writes out the labels to create the namespace then rebuilds the SCM stacks to expose the new logical device. • Optional parameters: ○ FriendlyName gives the persistent memory disk a friendly name. Default is "PmemDisk" ○ AtomicityType lets you set BTT. Default is "none" #Remove-PmemDisk • Removes the given persistent memory disk. It accepts the output of Get-PmemDisk. • Deletes the namespace's labels and then rebuilds the SCM stacks to remove the logical device. • Requires user confirmation, which can be overridden with -Force. #Get-PmemUnusedRegion • Returns aggregate pmem regions available for provisioning a logical device. • Returned object has a unique region ID, total size, and list of physical devices that contribute to the unused region #Initialize-PmemPhysicalDevice • Writes zeroes to the label storage area, writes new label index blocks, and then rebuilds the SCM [Storage class memory] stacks to reflect the changes. • Requires user confirmation, which can be overridden with -Force. • This cmdlet is intended as a "big hammer" recovery mechanism. It is not recommended for normal use. NVDIMM-N Interleaving Windows Server 2019 supports NVDIMM-N interleaving which can further enhance system performance across various applications. This option can be configured through the BIOS Setup Menu. In the OS, this is visible as a single logical device across several physical devices on that socket. Two interleaved persistent memory disks should be visible, one for each socket in the Device Manager, if there are NVDIMM-N modules plugged in on both the sockets. Figure 29. Interleaved Persistent Memory Disk in Device Manager 40 Windows

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
PowerShell Cmdlets
#Get-PmemDisk
•
Returns one or more logical persistent memory disks.
•
The returned object has information about size, atomicity type, health status, and underlying physical devices.
#Get-PmemPhysicalDevice
•
Returns one or more physical persistent memory devices (NVDIMMs).
•
The returned object has information about size(s), RFIC, device location, and health/operational status.
#New-PmemDisk
•
Creates a new disk out of a given unused region.
•
Writes out the labels to create the namespace then rebuilds the SCM stacks to expose the new logical device.
•
Optional parameters:
○
FriendlyName gives the persistent memory disk a friendly name. Default is "PmemDisk<N>"
○
AtomicityType lets you set BTT. Default is "none"
#Remove-PmemDisk
•
Removes the given persistent memory disk. It accepts the output of Get-PmemDisk.
•
Deletes the namespace’s labels and then rebuilds the SCM stacks to remove the logical device.
•
Requires user confirmation, which can be overridden with -Force.
#Get-PmemUnusedRegion
•
Returns aggregate pmem regions available for provisioning a logical device.
•
Returned object has a unique region ID, total size, and list of physical devices that contribute to the unused region
#Initialize-PmemPhysicalDevice
•
Writes zeroes to the label storage area, writes new label index blocks, and then rebuilds the SCM [Storage class memory] stacks to
reflect the changes.
•
Requires user confirmation, which can be overridden with -Force.
•
This cmdlet is intended as a "big hammer" recovery mechanism. It is not recommended for normal use.
NVDIMM-N Interleaving
Windows Server 2019 supports NVDIMM-N interleaving which can further enhance system performance across various applications. This
option can be configured through the BIOS Setup Menu.
In the OS, this is visible as a single logical device across several physical devices on that socket. Two interleaved persistent memory disks
should be visible, one for each socket in the Device Manager, if there are NVDIMM-N modules plugged in on both the sockets.
Figure 29. Interleaved Persistent Memory Disk in Device Manager
40
Windows