Microsoft has documented a wide range of networking options for deployment of one and two node clusters. For enhanced network performance and/or clusters with more than two nodes, the preferred option is storage switched, non-converged, two TOR switches.
![This diagram shows the logical network component for storage switched, non-converged, two TOR switches.](/static/media/9198938f-8c47-5a0e-82d9-6db6a62cd3f7/DAM-7856d69b-fe7c-4ae3-8cfe-463b04b94401/out/image4=GUID-4ADB9212-A5FD-4EB9-A829-12DFA1348D0E=1=en-us=Low.png)
There are several important features supported by the physical connectivity components required for this pattern including:
- The cluster is implemented with two TOR switches for northbound/southbound traffic.
- Two teamed network cards are used to handle management and compute traffic connected to two TOR switches. Each NIC is connected to a different TOR switch.
- Two RDMA NICs in standalone configuration are connected to a different TOR switch for storage traffic.
![This diagram shows the logical network component for storage switched, non-converged, two TOR switches with a restricted firewall.](/static/media/9198938f-8c47-5a0e-82d9-6db6a62cd3f7/DAM-7856d69b-fe7c-4ae3-8cfe-463b04b94401/out/image5=GUID-653DDB28-A791-49AF-ADBB-664C3B7948DA=1=en-us=Low.png)
Azure Stack HCI requires periodic connectivity to Azure. If your organization's outbound firewall is restricted, you must request firewall changes including new outbound endpoints and internal rules and ports. There are required and recommended endpoints for the Azure Stack HCI core components, which include cluster creation, registration and billing, Microsoft Update, and cloud cluster witness access if needed.