Networking for Analytics Database Configuration | Teradata VantageCore | EDW - Networking for Analytics Database Configuration - Teradata VantageCore VMware

Teradata® VantageCore powered by Dell Technologies - Enterprise Data Warehouse

Teradata VantageCore VMware
April 2024
English (United States)
Last Update
Product Category
Each Teradata Analytics Database node is connected to the following nodes:
  • Two 25GbE fabrics for BYNET and storage
  • Two 25GbE fabrics for LAN, management (vSphere/CMIC), and ecosystem services (Viewpoint)
  • One 1GbE management fabric for BMC/iDRAC

Analytics Database requires node-to-node communication for BYNET message passing layer and node-to-storage network connectivity for iSCSI storage traffic. These dependent data flows are enabled within this architecture by using dual (redundant) 25GbE networks.

The interfaces allocated to BYNET on the nodes have one network interface aligned to the 25GbE NIC in Slot 1, and the other aligned to the 25GbE NIC in Slot 2, as shown in the following image. This configuration makes BYNET fault-tolerant against failure of a single 25 GbE switch or a single 25 GbE NIC.

The similarly connected storage I/O provides maximum protection from the network card, link, switch, and controller failure. Each host has two dedicated physical connections to Controller A through one 25GbE switch and two dedicated physical connections to Controller B through the other 25GbE switch.

On the array side, each controller has one 25GbE connection to each 25GbE switch, for a total of two connections for the array to each 25GbE switch, as shown in the following image:

PowerVault ME5 Fabric Connectivity

LACP and Bonding of the NIC ports for BYNET and storage are not used by design on the Analytics Database nodes because load balancing across the discrete or individual network paths is performed internally to Vantage by BYNET and the Teradata Multi-path driver in the Guest OS.

Separate VLANs are configured for Storage and BYNET traffic across the shared set of physical switches to enable the application of optimal network configurations for each, and to improve the isolation of broadcast traffic between the two. For example, the VLAN for BYNET is configured for RoCEv2 protocol for large-scale systems, while the VLAN for Storage is not because the storage does not support iSER.

Each Analytics Database node is connected to two 25GbE leaf switches for different functions and supporting applications, including ecosystem monitoring and management (vSphere, CMIC, Viewpoint). The interfaces for these two specific switches are bonded with LACP on each SQLE node.

For this implementation, the 1GbE BMC connectivity to the nodes for iDRAC management is supported through the connectivity from the BMC port on the node to the 48-port TOR 1/10GbE network switch.