The prerequisites for manually installing scale unit node firmware to the latest release differ slightly depending on whether the scale unit is running 13G or 14G servers. The follow procedure indicates if a step depends on a specific server generation.
Note: Use the OEM VM for the procedure.
- Regardless of PowerEdge server generation, obtain a copy of the compliance checker scripts from Dell Technologies Support. Extract the Compliance Tools folder to the root of C:\.
The folder, as shown in the following figure, contains PowerShell scripts that are used during the manual update procedure.
Figure 2. Compliance Tools folder
- Create a C:\DUPS folder. Share the folder with Everyone and Administrator with read/write permissions.
- Download the Dell EMC Cloud for Microsoft Azure Stack Hub Customer Toolkit for 1906 release and for the correct server platform.
- Extract the Cloud for Microsoft Azure Stack Hub Customer Toolkit <1906 version specific to server generation>.zip file to C:\Temp. Create the temp folder if it does not already exist.
- Create a second temp folder called C:\Temp2. From C:\Temp, extract the contents of the AzS-DellEMC-OEMPkg_<1906 version specific to server generation>.zip file to C:\Temp2.
- After you extract the files, go to the C:\Temp2\Firmware\Servers directory and find the updated firmware files for the scale unit nodes.
The following figure shows an example from the 13G OEM extension package for the 1906 release. The versions of these files will vary based on the server generation and version of the package.
Figure 3. Example of 13G OEM extension package for 1906 release
- Copy or move the files to C:\DUPS folder.
- Copy the Catalog.xml file from C:\Temp\<Customer Toolkit folder>\Compliance\Catalog to C:\ComplianceTools\Catalog.
- Go to the C:\ComplianceTools\Catalog folder and open the Catalog.xml file in Notepad.
- Search for the following headers: <Display lang="en">SU Node Server Model</Display>, where ‘SU Node Server Model’ equals the PowerEdge server used for the scale unit nodes. For example:
- For 13G, the PowerEdge server would be R730xd.
- For a 14G hybrid configuration, the PowerEdge server would be R740xd.
- For a 14G all-flash configuration, the PowerEdge server would be the R640.
Directly under the header is a series of “Package path” statements that identify the updates that are required for the scale unit nodes. The following list shows an example of this section for an R730xd scale unit node:
- Search for the following header: <Display lang="en">HLH Server Model</Display>, where ‘HLH Server Model’ equals the PowerEdge Server used for the HLH. For example:
- For 13G, the PowerEdge server would be R430.
- For 14G, the PowerEdge server would be R640.
Directly under the header, is a series of “Package path” statements that identify the updates that are required for your HLH server. The following list shows an example of this section for an R430 HLH:
- As a best practice, load the files in the order listed in the Catalog.xml file. The exception is the iDRAC update, which is applied prior to all the other updates. This prevents SMB and Share Violation errors while running remote commands or accessing share points during the update process.
- We recommend that you disable all Azure Stack Hub Infrastructure Backups before applying any updates. Disabling these backups not only prevents the system from hanging on open file handles used by the backup system; it also avoids increased run times.