Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
End-to-End Single-Node Deployment: Microsoft HCI Solutions from Dell Technologies
Single-node deployment
Single-node deployment
Operating system deployment
Install roles and features
Change the hostname
Registry settings
PAL and DPOR registration for Azure Stack
Joining cluster nodes to an Active Directory domain
Single-node configuration
Updating a standalone node before adding it to the cluster
Network connectivity for single node clusters
Creating the host cluster
Enabling Storage Spaces Direct
Updating the page file settings
Azure onboarding for Azure Stack HCI operating system
Best practices and recommendations

Single-node configuration

Single-node configuration

  • A single-node cluster has only one node in a cluster. Like a multi-node Azure Stack HCI OS cluster, a single node cluster is delivered as an Azure service and has all the hybrid cloud features. Since disk is the fault domain for a single-node cluster, it does not have to replicate any data over the network. Nevertheless, Dell Engineering still recommends having an RDMA NIC in the setup as it can help in future expansion (once it is supported by Microsoft) or be used in virtual machine traffic. The 25 GbE or 100 GbE adapters can also be used for application replication, Hyper-V Replica, or Shared Nothing Live Migration of VMs to other clusters.

    The following figures show network topology configurations that take advantage of the RDMA adapters in the system.

    Figure 2. Configuration 1
    Configuration 1 shows how to use the rNDC or RDMA PCIe adapter to create a SET team and use the SET team for Management, VM traffic, and Live Migration traffic (if desired).
    Figure 3. Configuration 2

    Configuration 2 shows how traffic can be bifurcated between the rNDC and the RDMA PCIe adapter in the system. Lower bandwidth rNDCs can be used for Management traffic while higher bandwidth PCIe adapters can be used for VM Network, Hyper-V Replica, or Shared Nothing Live Migration to move VMs and the associated storage from one cluster to another.

    Deployment instructions for single-node cluster

    This section provides an example of the commands used to configure networking of a single-node cluster. 

    #Create VMSwitch for Management using rNDC
    New-VMSwitch -Name S2DSwitch -AllowManagementOS 0 -NetAdapterName "NIC1","NIC2" -MinimumBandwidthMode Weight -Verbose
    #Create VMSwitch for LiveMigration/Application Replication using RDMA adapters
    New-VMSwitch -Name Migration_VM -AllowManagementOS 0 -NetAdapterName "SLOT 6 Port 1","SLOT 6 Port 2"  -MinimumBandwidthMode Weight -Verbose

    #Assign VLANs as needed
    Add-VMNetworkAdapter -ManagementOS -Name "Management" -SwitchName S2DSwitch -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 202 -Verbose
    Add-VMNetworkAdapter -ManagementOS -Name "LM" -SwitchName Migration_VM -Passthru | Set-VMNetworkAdapterVlan -Access -VlanId 210 -Verbose

    #Set Jumbo Frames as needed
    Set-NetAdapterAdvancedProperty -Name "SLOT 6 Port 1" -DisplayName "Jumbo Packet" -DisplayValue "9014"
    Set-NetAdapterAdvancedProperty -Name "SLOT 6 Port 2" -DisplayName "Jumbo Packet" -DisplayValue "9014"

    #Host Management Adapter
    New-NetIPAddress -InterfaceAlias 'vEthernet (Management)' -IPAddress 172.18.48.71 -DefaultGateway 172.18.32.1 -PrefixLength 19 -AddressFamily IPv4 -Verbose
    #LiveMigration Adapter
    New-NetIPAddress -InterfaceAlias 'vEthernet (LM)' -IPAddress 192.168.200.71 -PrefixLength 24 -AddressFamily IPv4 -Verbose

    #Set minimum bandwidhth weight for all adapters. Helpful if you use the same adapter for all traffic. This can be changed as needed by the customer.
    Set-VMNetworkAdapter -ManagementOS -Name Management -MinimumBandwidthWeight 10
    Set-VMNetworkAdapter -ManagementOS -Name LM -MinimumBandwidthWeight 20
    Set-VMSwitch -Name S2DSwitch -DefaultFlowMinimumBandwidthWeight 10
    Set-VMSwitch -Name Migration_VM -DefaultFlowMinimumBandwidthWeight 10

    #DNS server address 
    Set-DnsClientServerAddress -InterfaceAlias 'vEthernet (Management)' -ServerAddresses 172.18.40.10,172.18.40.9

    #Disable RDMA on the RDMA adapter as it won’t be used in this configuration.
    Disable-NetAdapterRdma 'slot 6*'