Multi-System Configurations - Data Warehouse Appliances

2750 Platform Product and Site Preparation Guide

Product
Data Warehouse Appliances
Published
March 2018
Language
English (United States)
Last Update
2018-04-17
dita:mapPath
epb1471886869774.ditamap
dita:ditavalPath
2750.ditaval.ditaval
dita:id
flv1471648428019
Product Category
Hardware
In a multi-system configuration:
  • All systems must be running the same version of SMWeb Services (11.01 or later) .
  • All server management switches in individual systems are joined together in a single server management domain.
  • The multi-system configuration has a single server management Site ID.

Nodes in all multi-system configurations share the BYNET V5 InfiniBand switches.

A system consists of a set of Teradata Database nodes and disk arrays. A system contains one or more nodes and disk arrays. A system may contain one or more cliques.

Each system in a multi-system configuration is assigned a unique system name. For example:
  • One unique system name is assigned to each Teradata Database system (a set of associated nodes and disk arrays) in a 2750 production system.
  • Another system name is assigned to each Teradata Database system (a set of associated nodes and disk arrays) in a 2750 Test and Development system.
  • Another system name is assigned to the nodes in an Aster cluster.
  • Another system name is assigned to the nodes in a Hadoop cluster.

Shared system components (collectives and cabinets, VMSs, BYNET V5 InfiniBand switches, server management switches, and TMSs) are not assigned system names.

Contact Teradata Customer Support to verify which Teradata, Aster, Hadoop, and SAS HPA systems are valid in multi-system configurations, such as a Unified Data Architecture (UDA) environment.
Multi-System Topology

This figure only shows a multi-system configuration consisting of production and test/development 2750 systems.