Coexistence Rules for Processing Nodes - Active Enterprise Data Warehouse

6800 Platform Product and Site Preparation Guide

Product
Active Enterprise Data Warehouse
Published
February 2018
Language
English (United States)
Last Update
2018-04-19
dita:mapPath
vyt1471885165825.ditamap
dita:ditavalPath
6800.ditaval.ditaval
dita:id
jso1471649458844
Product Category
Hardware
Contact your Teradata representative to confirm the exact version of the Teradata Database, the operating system, and PDE packages required for the platform.
Coexistence Rules for Processing Nodes
Component Rules
Software All nodes (TPA and non-TPA) in the coexistence system must be running Linux SLES 11. Before you add TPA nodes, the software and firmware on the existing TPA nodes must be at the same level as the new TPA nodes.
Teradata Database All systems must be running Teradata Database: 14.10.xx.xx or 15.00.xx.xx and later
Node Generation There must be at least two nodes of a generation to be included in a coexistence system.
Cabinet All cabinets in 6800 coexistence systems are 47 inches deep. The following cabinet configurations apply.
  • 6800 nodes in expansion cabinets may be added to the 36-port BYNET V5 InfiniBand switches in 6700 cabinets, if switches are present or to BYNET V5 InfiniBand switches in BYNET V5 InfiniBand cabinets.
  • 6800 nodes in expansion cabinets may be added to BYNET V5 InfiniBand switches in BYNET V5 InfiniBand cabinets
  • Available 36-port BYNET V5 InfiniBand switches already installed in the 6800 cabinet can be used for BYNET V5 connectivity of the other nodes
Cliques Nodes within a clique must be of the same generation (that is, all 6800, 6750, 6700, 6690, or 6650 C/H nodes).

Cliques within a system can be of different generations.

Hot Standby Nodes Coexistence supports hot standby nodes.

Clique rules on the node type also apply to hot standby nodes.

Memory All 6750, 6700, 6690, and 6650 nodes must have the maximum memory configuration available.

Nodes within a system can have different memory sizes, but memory sizes cannot be different within a clique.

AMPs The database can only use AMP storage to the capacity of the smallest AMP. In some cases due to configuration differences, data integrity features, or use of different drive capacities, there may be unused space on some AMPs. Some or all of that unused space may be usable on a future upgrade/expansion if the size of the smallest AMP is increased.

Additional memory may be required on the nodes within the faster cliques that have more AMP VPROCs. The faster nodes can then have at least the same amount of FSG-cache benefit per AMP VPROC as the slower cliques that have fewer AMP VPROCs.

New nodes should be configured so that they have an appropriate number of AMP VPROCs per node, depending on configuration and workload mix.