Teradata Vantage on VMware on DSU | Teradata DSA | DSU - 17.00 - Teradata Vantage on VMware on DSU - BAR - Data Stream Architecture - Data Stream Utility

Teradata® DSA - DSU Installation, Configuration, and Upgrade Guide

Product
BAR
Data Stream Architecture
Data Stream Utility
Release Number
17.00
Release Date
August 2020
Content Type
Configuration
Installation
Publication ID
B035-3153-129K
Language
English (United States)

The DSU on VMware template is Teradata Vantage on VMware and hosts the DSC component and the DSC repository. Teradata Vantage on VMware is a SUSE Linux Enterprise Server (SLES) operating system and Advanced SQL Engine packaged into a virtual machine that runs in a virtualized environment on third-party hardware.

This guide shows how to set up a DSU instance and integrate it into an existing Teradata system.

Audience

This guide is intended for those experienced in vSphere, vCenter, and ESXi terminology and who have an understanding of the following:
  • Standard switches, datastores, VM templates, ova, ovf, etc.
  • Teradata configurations, including TPA, CMIC, Viewpoint and DSU.
  • Basic network setups for these node types on a bare metal install and how that relates to a vSphere installation

Software Requirements

VMware vCenter 5.5 or higher

Hardware Requirements

pNode/Server: For example, Dell PowerEdge R720xd, Dell PowerEdge R730xd, Dell PowerEdge R740xd, HP Gen9 or similar with the following minimum resources:

Item Resource
CPU 4
Memory 16 GB
Storage Datastore must be able to fit a 500 GB VMware image.

The OS drive uses approximately 200 GB of space and the DSU repository uses approximately 300 GB of space

Separate Physical Networks 1 – public

1 – DSU (10 GB network, optional)

Special Switch Requirements

vCenter allows for distributed and local virtual switches. This version of vCenter only supports local virtual switches, so each ESXi host must have local virtual switches for the public network, and any optional CMIC or DSU networks.

The DSU virtual switches must have MTU values of 9000 for optimum performance.
  • For best performance, all virtual switches must be on their own physical network.
  • For low performance systems (for example, development or test), the virtual adapters can be placed on the same physical network, recognizing that performance is reduced with the shared bandwidth.

    With the exceptions of the public and CMIC subnets, using an MTU value of 9000 may cause problems on subnets that are using an MTU of a different size.

All virtual instances require static IPs.