Upgrade Storage Spaces Direct (S2D) from Windows Server 2016 to Windows Server 2019

s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Upgrade Storage Spaces Direct (S2D) from Windows Server 2016 to Windows Server 2019

How to upgrade a Storage Spaces Direct (S2D) cluster to Windows Server 2019. The four approaches to upgrading a S2D cluster from Windows Server 2016 to Windows Server 2019

• In-place upgrade while VMs are running
• Clean-OS installation while VMs are running
• In-place upgrade while VMs are stopped
• Clean-OS install while VMs are stopped*

The Video shows the "Clean-OS installation while VMs are running" with the use of Host OS boot on VHDX (Dual boot lab systems)

*For the last two Hosts in Part 2 I used the "Clean-OS install while VMs are stopped" for Host S046035 and S046036

• Upgrade a Storage Spaces Direct cluster to Windows Server 2019

The lab system used is a 6 Node S2D Cluster

• List Host Version and the Last Reboot time

After the upgrade enable Cluster Performance History

• Performance history for Storage Spaces Direct

Windows Server 2019 and SR-IOV

s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

How to use single root input/output virtualization (SR-IOV) in Windows Server 2019 with Guest VMs running Windows Server 2012R2, Windows Server 2016 and Windows Server 2019

SR-IOV #3 - Upgrade Drivers for SR-IOV in Windows Server 2012R2 Guest VMs

The Windows Server 2019 Host Network configuration

The demo/lab Host configuration with three physical network interface controller (pNIC)
The use of three pNIC is only to show the diffrent amount of Virtual Functions (VF)

1. Get-VMSwitch
2. Get-VMSwitch | ft Name,NetAdapterInterfaceDescriptions
3. Get-NetAdapter -Name *NIC* | sort name | ft name, InterfaceDescription, LinkSpeed -AutoSize
4. Get-NetAdapterSriov | sort name | ft Name, InterfaceDescription, SriovSupport, NumVFs -AutoSize
5. Note
6. Get-NetAdapterSriovVf | sort name | ft -AutoSize
7. Note

Validate-DCB Disconnected installation

s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Validator for RDMA Configuration and Best Practices

Validate-DCB Disconnected installation

Validate-DCB Fix 58 errors

More information about installation and review the result for Validate-DCB

• How to review the result from Validate-DCB
• How to do the Installation and first run in 5 minutes with Validate-DCB

More information on GitHub

• Validate-DCB
• WSLab Scripts for Validate-DCB

Validate-DCB Disconnected installation (Step-by-Step)

1. The installation failed do to no internet access (Disconnected)
2. From a Host with Internet access run "Save-Module Validate-DCB -Path C:\Temp"
3. The packages are downloaded
4. The Download complete
5. The six folders are created with all the modules
6. Select and copy the six folders
7. Change back to the disconnected Host, change to the folder "C:\Program Files\WindowsPowerShell\Modules"
8. Paste the files to the folder
9. Files are copied
10. Check that the files and folders are copied
    (Restart PowerShell CLI, to load with the new modules)
11. Now you can run the "Validate-DCB"
12. The prerequisite part "Global Unit" is check
13. If the "Global Unit" pass, the wizard will start and you are ready to add the information about your system
14. For more information about the next step go to the online installation guide [Link]
    (The next part is the same for online and disconnected systems)

Validate-DCB Behind the Scenes

s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Validator for RDMA Configuration and Best Practices

Validate-DCB - Behind the Scenes

The setup used for the recording of the Validate-DCB Videos

Validate-DCB - Behind the Scenes

Hardware:

• Microsoft Surface Pro 7
• Microsoft Surface Pro 5
• Microsoft Surface Pro 5 LTE
• Microsoft Surface Arc Mouse and Pen

Monitor:

• EIZO 24"
• Beetronics 10"

Camera:

• GoPro HERO8 Black - 4K
• Logitech Brio Ultra HD Pro Webcam - 4K
• iPhone 11 Pro - 4K

Microphone, Speaker and Headphone

• Røde Wireless GO
• Røde Lavalier GO
• Røde VideoMic Me-L
• Røde SC6-L Mobile Interview Kit
• Creative Sound Blaster Play! 3
• Jabra Speak 510
• Jabra Move Wireless

Light/Control

• Elgato Key Light
• Elgato Control Center for Windows
• Philips HUE
• LK IHC (Schneider Electric)

Software:

• Microsoft Windows 10
• Microsoft Garage Mouse without Borders
• TechSmith Camtasia 2019
• Logitech Capture
• Voicemeeter Potato Ultimate Mixer

Part 2

Server Hardware:

• Mellanox SN2100 - 100 GiB (10, 25, 40, 50, 56 and 100 GiB)
• Mellanox SX1012 - 56GiB (10, 40 and 56 GiB)
• Mellanox ConnectX-5
• Mellanox ConnectX-3-Pro VPI
• Dell, Fujitsu, Lenovo, SuperMicro, Cisco and HP Servers

Software:

• Microsoft Windows Server 2016
• Microsoft Windows Server 2019
• Microsoft Windows 10
• Microsoft PowerBI

***

Validator for RDMA Configuration and Best Practices

• Validator for RDMA Configuration and Best Practices
• Part 1
• Part 2
• Part 3
• Part 4
• How to review the result from Validate-DCB

How to review the result from Validate-DCB

s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Validator for RDMA Configuration and Best Practices

How to review the result from Validate-DCB

• How to do the Installation and first run in 5 minutes with Validate-DCB

More information on GitHub

• Validate-DCB
• WSLab Scripts for Validate-DCB

The results output consists of two unit

1. [Global Unit] Prerequisites and requirements to run the modal tests. 
2. [Modal Unit] Each Cluster Host configuration and best practices feedback

How to review the Error(s)

Example 1: Jumbo Packet Missing from vNIC SMB02

1. The Validate-DCB list one FailedCount
2. Scroll back to we find the red lines. Expect 9014 but the value was 1514 looks like the Jumbo Packet was not Enabled on the vNIC
3. Review the Properties for the vNIC SMB02 on Host S046036, The finding is correct, the Jumbo Packet was Disabled. To fix the Error just enable Jumbo Packet
4. Change the Value to 9014 Bytes
5. Scan the Host S046036 again with Validate-DCB
6. Now the Failed Count is back on 0

Review with PowerBI

Run the Validate-DCB and add the Report Path, copy the XML to the machine with PowerBI
Download the Validate-DCB.pbix fle from GitHub (Link)

1. Run "validate-dcb -ConfigFilePath C:\Temp\S046036.ps1 -ReportPath C:\Temp"
2. Copy the XML to the machine with PowerBI
3. Click on "Validate-DCB.pbix" to open PowerBI
4. Import the XML
   A: Edit Queries
   B: Data source settings
   C: Change Source... Select the XML
5. Review the "Failure" and make the necessary changes

Tilføj billedtekst

List Version and Reboot Time

s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

PowerShell Script to list the Windows Version and Last Reboot Time:

List my three S2D Cluster versions and the last reboot time

“Thanks to Steffen Brandsborg, Sentia Denmark for creating the PowerShell used below”

# Cluster S2D01
 $ComputerList = "S046031","S046032","S046033","S046034","S046035","S046036"
# Cluster S2D02
 $ComputerList += "S047027","S047028"
# Cluster S2D03
 $ComputerList += "S048001","S048002","S048003","S048004"

$InvokeResult = invoke-command -ComputerName $ComputerList -ScriptBlock {
    $BuildBranch = (Get-ItemProperty "HKLM:\Software\Microsoft\Windows NT\CurrentVersion").BuildBranch
    $CurrentVersion = (Get-ItemProperty "HKLM:\Software\Microsoft\Windows NT\CurrentVersion").CurrentVersion
    $CurrentBuildNumber = (Get-ItemProperty "HKLM:\Software\Microsoft\Windows NT\CurrentVersion").CurrentBuildNumber
    $UBR = (Get-ItemProperty "HKLM:\Software\Microsoft\Windows NT\CurrentVersion").UBR
    $BootTime = ((Get-WmiObject Win32_OperatingSystem).ConvertToDateTime((Get-WmiObject Win32_OperatingSystem).LastBootUpTime)).ToString("yyyy-MM-dd HH:mm:ss")
    $ProductName = (Get-ItemProperty "HKLM:\Software\Microsoft\Windows NT\CurrentVersion").ProductName

    $Result =  @{
        Computername = $env:COMPUTERNAME
        ProductName = $ProductName
        WindowsVersion = ("$CurrentVersion.$CurrentBuildNumber.$UBR")
        BootTime = $BootTime
    }
    New-Object -TypeName PSObject -Property $Result
}
$InvokeResult | Sort Computername | Select ComputerName, ProductName, WindowsVersion, BootTime | ft 

Validator for RDMA Configuration and Best Practices

s2d.dk is not responsible for any errors, or for the results obtained from the use of this information on s2d.dk. All information in this site is provided as "draft notes" and "as is", with no guarantee of completeness, accuracy, timeliness or of the results obtained from the use of this information. Always test in a lab setup, before use any of the information in production environment. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Validator for RDMA Configuration and Best Practices

How to do the Installation and first run in 5 minutes with Validate-DCB

• How to review the result from Validate-DCB

More information on GitHub

• Validate-DCB
• WSLab Scripts for Validate-DCB

Video part 1 to 4

Part 1 - Installation

Part 2

Part 3

Part 4

Installation

• Install-Module Validate-DCB

After installation of the Validate-DCB Module you can run the wizard:

1. Run the Validate-DCB from PowerShell and the wizard will start <Next>
2. Add the Cluster name
3. Resolve
4. The Cluster Nodes are listed
5. Next
6. Add vSwitch Name
7. Add pNIC, vNIC and vlan information
8. Select RDMA type iWARP or RoCE
9. Select the Jumbo Frames (Ethernet MTU size)
   Note: the MTU for RDMA is not the same as Ethernet MTU
   For Mellanox list the Ethernet and RoCE/RDMA MTU with "mlx5cmd.exe -Stat"
   Both the pNIC and the vNIC for SMB need to have the same MTU Size
10. Next
11. Policy Name
12. Bandwidth Reservation
13. Next
14. Save the configuration file
15. Export (the job will start)