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
Tech Book—Dell Integrated System For Microsoft Azure Stack HCI
Preface Business Transformation and Data Center Modernization Evolution of Data Centers to HCI and Hybrid Cloud A Closer Look at Microsoft Azure Stack HCI Azure Stack HCI Architecture and Building Blocks Dell Integrated System for Microsoft Azure Stack HCI Portfolio – AX Nodes Networking Topologies for Azure Stack HCI Solutions Stretch Clustering with Azure Stack HCI
Stretch Clustering with Azure Stack HCI
Azure Stack HCI stretch clustering
Comparison of traditional and stretched clusters
Business continuity planning
Stretch clustering topology
Servers Storage pools Volumes Setup configuration Preferred site configuration Affinity and anti-affinity VMs Cloud witness
Azure Stack HCI stretch clustering scenarios and concepts
Active/passive setup Active/Active Synchronous replication Asynchronous replication
Stretch clustering best practices with Azure Stack HCI
Validated network topology
Basic configuration High throughput configuration Server and site affinity rules for VMs
Managing the Hybrid Cloud Sizing and Configuration Best Practices Dell Support and Services Conclusion Additional Resources

Validated network topology

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 22H2 and earlier > Tech Book—Dell Integrated System For Microsoft Azure Stack HCI > Validated network topology

Validated network topology

  • Basic configuration

    Figure 47. Network topology for a stretched cluster (basic)


    This section describes the host network configuration and network cards that are required to configure a basic stretched cluster. The purpose of this topology is to keep the host and inter-site configuration simple with little or no change to a standard stand-alone cluster networking architecture.

    This topology uses two 25 GbE NICs for each host on both sites. One NIC is dedicated to intra-site storage traffic, similar to a stand-alone Storage Spaces Direct environment. The second NIC is used for management, compute, and Storage Replica traffic. To ensure management traffic is not bottlenecked due to high traffic on the Replica network, the customer network team should throttle traffic between the two sites using QoS rules. It is recommended that the network bandwidth is throttled to 50 percent of the capacity of the total number of network cards supporting the management NIC team.