Solution overview. Dell AX-750, AX-640, AX-6515, AX-740XD, AX-7525, AX-650

Add to My manuals
76 Pages

advertisement

Solution overview. Dell AX-750, AX-640, AX-6515, AX-740XD, AX-7525, AX-650 | Manualzz

2

Solution overview

This chapter presents the following topics:

Topics:

Introduction

Solution integration and network architecture

Introduction

Dell Solutions for Azure Stack HCI offers stretched cluster solutions with AX nodes from Dell Technologies. Built using industryleading PowerEdge servers, AX nodes offer fully validated HCI nodes for a variety of use cases. A robust set of configurations and different models allows you to customize your infrastructure for application performance, capacity, or deployment location requirements.

Stretched clusters and Storage Replica

An Azure Stack HCI stretched cluster solution is a disaster recovery solution that provides an automatic failover capability to restore production quickly, with little or no manual intervention. Storage Replica, a Windows Server technology, enables replication of volumes between servers across sites for disaster recovery. For more information, see Storage Replica overview .

A stretched cluster with Azure Stack HCI consists of servers residing at two different locations or sites, with each site having two or more servers, replicating volumes either in synchronous or asynchronous mode. For more information, see Stretched clusters overview .

A stretched cluster can be set up as either Active-Active or Active-Passive. In an Active-Active setup, both sites will actively run VMs or applications; therefore the replication is bidirectional. In an Active-Passive setup, one site is always dormant unless there is a failure or planned downtime.

Sites can be on the same campus or in different places. Stretched clusters using two sites provides disaster recovery if a site experiences an outage or failure.

Solution overview 7

The following figure shows an Active-Active setup:

Figure 1. An Active-Active setup

Sites can be logical or physical. For logical sites, a stretched cluster can exist on single or multiple racks or in different rooms in the same data center. For physical sites, the stretched cluster can be in different data centers on the same campus or in different cities or regions. Stretched clusters using two physical sites provide disaster recovery and business continuity should a site suffer an outage.

Solution integration and network architecture

Dell Solutions for Azure Stack HCI stretched clusters offer distinct network topologies that are validated with the following stretched cluster configurations:

● Basic configuration

● High throughput configuration

Basic configuration sees a network topology that requires minimal changes to a traditional single-site Azure Stack HCI configuration. This configuration uses a single network/fabric for management, VM, and replication traffic, keeping host networking simple. The customer network team must configure quality of service (QoS) on an external firewall or routers to throttle inter-site bandwidth and thereby ensure that Replica/VM traffic does not saturate the Management network.

High throughput configuration suits customer environments that are dense and involves higher write IOPs compared to a basic configuration. This configuration requires a dedicated channel (network interface cards (NICs) or fabric) for Replica traffic (using SMB-Multichannel). This network topology should be used only if inter-site bandwidth is higher than 10 Gbps. The network team must configure multiple static routes on the host to ensure that Replica traffic uses the dedicated channel that has been created for it. If the customer environment does not use Border Gateway Protocol (BGP) at the ToR layer, static

8 Solution overview

routes are needed on the L2/L3 to ensure that the Replica networks reach the intended destination. Subsequent sections of this guide provide more information about the expectations of customer networking teams.

A stretched cluster environment has two storage pools, one per site. In both topologies described in the preceding section, storage traffic requires Remote Direct Memory Access (RDMA) to transfer data between nodes within the same site. Because

Storage and Replica traffic produces heavy throughput on an all-flash or NVMe configuration, we recommend that you keep the

Storage traffic on separate redundant physical NICs.

This table shows the types of traffic, the protocol used, and the recommended bandwidth:

Table 1. Types of traffic

Types of traffic

Management

Replica

Intra-site storage

Compute Network

Protocol used

TCP

TCP

RDMA

TCP

Recommended bandwidth

1/10/25 Gb

1/10/25 Gb

10/25 Gb

10/25 Gb

Here are some hovers over consider about network configuration:

● Management traffic uses Transmission Control Protocol (TCP). Because management traffic uses minimal bandwidth, it can be combined with Storage Replica traffic or even use the LOM, OCP, or rNDC ports.

● VM Compute traffic can be combined with management traffic.

● Inter-site Live Migration traffic uses the same network as Storage Replica.

● Storage Replica uses TCP as RDMA is not supported for replica traffic over L3 or WAN links. Depending on the bandwidth and latency between sites and the throughput requirements of the cluster, consider using separate redundant physical NICs for Storage Replica traffic.

Solution overview 9

advertisement

Related manuals

advertisement

Table of contents