The key features previously mentioned (DCB, PFC, ETS, VLAN, and LLDP) are straightforward switch configurations shown in the attachments. The DCB, PFC, and ETS features ensure the infrastructure has a high reliance for day to day East-West Layer-2 communication within the same rack. For deployment, network configuration for node discovery uses the default Discovery VLAN 3939 and IPv6 MLD snooping protocol. Azure Network intents are in relation to the traffic type and how the node ports are configured to support the network traffic.
This document uses a simple, fully converged intent that includes the compute storage, management traffic flow through the same physical link port between nodes, and a switch. Post-deployment network traffic within the ACP Azure cluster will consist of three primary types of traffic management, compute, and storage. Management traffic flows between host nodes and remote management tools like PowerShell, Windows Admin Center (WAC), and external Data Center services. Compute traffic is tenant-based VM type traffic. Storage traffic is Server Message Block (SMB) or SMB Direct over RDMA.
The topology example below demonstrates the boundaries of the North-South traffic that leaves the Top of Rack (TOR) VLT switch pair and the East-West traffic that stays within the TOR VLT switch pairs. Examples of North-South traffic include management and compute traffic, while East-West includes storage traffic.
This example reviews a simple, ACP fully converged intent network topology of one pair of Top of Rack S5248F-ON switches using VLT port channel. The Out-of-Band (OOB) Management network can be an E or N Series switch to connect the Cluster nodes iDRAC interfaces and TOR Eth0 management ports. Review of the OOB interface is outside the scope of this document.