Supported Versions and Platforms
|
HX Data Platform
|
3.5(2a) and later
Important
|
If your cluster is running on releases earlier than 3.5(2a), ensure that you upgrade your existing cluster to 3.5(2a) at the
minimum.
|
|
Compute-only Nodes and Storage Options |
Attention
|
UCS B200 M5 blade servers with M.2 SATA drives.
HW RAID M.2 (UCS-M2-HWRAID and HX-M2-HWRAID) is not supported on Compute-only nodes.
UCS B200 M4 blade servers with local SAS or Fibre Channel SANs.
|
|
Windows ISO
|
Customer provided Windows 2016 Datacenter edition ISO.
|
Maximum Compute to Converged ratio
|
1:1
|
Maximum Cluster Size
|
A single cluster can have a maximum of 32 nodes.
|
Network Speed
|
Mixing network speeds between compute-only nodes and HyperFlex converged nodes is not recommended. For example, if the existing
network connectivity of the converged nodes is 40 GbE, then the compute-only nodes should also be connected at 40 Gb speeds.
|
Determine Boot Disk Connection
|
Based on your topology, and the type of compute-only nodes that you want to add, choose one of the following expansion scenarios:
-
Cluster Expansion for UCS M5 blade servers with M.2 SATA drives, or UCS M4 blade servers with Local SAS drives
Note
|
HW RAID M.2 (UCS-M2-HWRAID and HX-M2-HWRAID) is not supported on Compute-only nodes.
|
-
Cluster Expansion for UCS M4 blade servers with Fibre Channel
|
Boot Disk Capacity
|
Ensure that you have only ONE boot disk of size greater than 240GB during Windows OS installation. After cluster expansion is complete, you may choose additional disks.
|
Stage
HyperFlex Driver Image
|
The Windows ISO and HyperFlex Driver image files must be placed on a shared location (such as HX Installer) that is reachable from Cisco UCS Manager and the Out-of-band
subnet. Use the following steps to download and host the HyperFlex Driver Image and Windows ISO in a shared location within
the installer VM.
For Windows Server 2016,
perform the following steps to prepare a suitable
Driver image for automated OS install.
-
Connect to your HX Installer VM and browse to the folder that contains the /var/www/localhost/images/.
-
Copy the HyperFlex Driver Image (/opt/springpath/packages/latest.img) to the images folder ( /var/www/localhost/images/).
For
Windows Server 2019,
perform the following steps to prepare a suitable
Driver image for automated OS install.
-
Copy the HyperFlex Driver Image. For example, run the following command:
rsync -avzP /opt/springpath/packages/latest.img /var/www/localhost/images/install.img
-
Mount the HyperFlex Driver Image. For example, run the following command:
mkdir -p /mnt/install-img && mount -o loop,rw /var/www/localhost/images/install.img /mnt/install-img
-
Copy the answer file specific to Windows Server 2019. For example, run the following command:
cp /opt/springpath/packages/FactoryUnattendXML/WindowsServer2019/Autounattend.xml.ro /mnt/install-img/Autounattend.xml
-
Edit the Autounattend.xml file by changing the value for Size to increase the boot partition size. For example:
<CreatePartition wcm:action="add">
<Order>2</Order>
<Extend>false</Extend>
<Size>92160</Size>
<Type>Primary</Type>
</CreatePartition>
Change the value of <Size> from 92160 to 195668.
-
Unmount the HyperFlex Driver Image. For example, run the following command:
umount /mnt/install-img
Note
|
You cannot install Windows Server 2019 or 2016 on SD cards.
|
Note
|
The DiskID referenced in autounattend.xml should correctly point to the local disk on the compute node where the OS is installed.
|
|
Multipathing with Fibre Channel SAN
|
Do NOT use multipathing with Fibre Channel SANs.
|
Fabric Interconnect Support
|
Compute-only node expansion is supported only when the compute node are on the same Fabric Interconnects.
|