The common.IT.properties.json File

Teradata Database on VMware Base, Advanced, Enterprise Tiers Getting Started Guide

brand
Cloud
prodname
Teradata Database on VMware
vrm_release
Deployer 3.01
category
Configuration
Installation
featnum
B035-5958-097K

The common.IT.properties.json file defines the VMware vSphere configuration settings common across all Teradata Database on VMware deployments. Configure the settings in this file each time something in the virtual environment changes.

Unless otherwise indicated, all property settings are required.
Property Category Properties Description
Teradata System Name TDsystemname The name of the Teradata System.
Domain Setting domain

The domain of the system being deployed which will be placed into the /etc/hosts file.

Example:
  • domain:corp.company.com
Public Virtual Switches public_vswitch The physical adapter with port group for the virtual network. The default setting is VM Network.
Example:
  • public_vswitch:VM Network
BYNET Virtual Switches

byn_vswitch1

byn_vswitch2

The labels of the BYNET switches. The first is required in MPP systems. The second is for redundancy and performance in MPP systems. This setting is the name specified when you created the vSwitch in vSphere. The setting should be empty for single-node systems.
CMIC Virtual Switches

cmic_vswitch1

cmic_vswitch2

The labels of the server management switches. These are only used in MPP systems with server management. The second is for redundancy and performance in MPP systems. This setting is the name specified when you created the vSwitch in vSphere.
DSC Virtual Switch dsu_vswitch The label of the DSC switch. This setting is the name specified when you created the vSwitch in vSphere.
Public Submask Setting public_submask The public submask name in dot-decimal notation.
Example:
  • public_submask:192.168.253.0
Gateway Setting gateway The gateway name or IP address.
Example:
  • gateway:10.26.23.254
Domain Name System Settings

dns1

dns2

The DNS name or IP address.
Examples:
  • dns1:192.168.0.256
  • [Optional] dns2:192.168.1.256
External NTP Server Settings

ntp1

ntp2

The host name or IP address of the ntp1 server is required, however the ntp2 server is optional.
Examples:
  • ntp1:time00.company.com
  • ntp2:time01.company.com

You must configure the NTP servers if you plan to use the Temporal feature.

Time Zone Setting OSTimeZone [Optional] The time zone of the VM. Enter either a fixed time zone displacement from GMT or the time zone file name. See the file LinuxTimeZoneStrings.txt for the valid settings for OSTimeZone.

If you are not enabling Temporal, the database time zone syncs with the operating system.

The default time zone is US/Pacific.

Examples:

  • OSTimeZone=GMT+11
  • OSTimeZone=US/Eastern

For additional Teradata time zone information, see Temporal Time Zone Strings.

PDisk Datastore Match Criteria PDisk_Datastore_Match Use this property to find the database datastores to attach data disks. The default setting is _data, which detects any datastores that contain _data in their name to be usable for database storage. Change this setting to match your datastores.
Ensure the value of PDisk Datastore Match Criteria does not match the pattern of the ESXI Datastore property in the node.IT.properties.json properties file by choosing different naming conventions for PDisk Datastore Match Criteria and ESXI Datastore.

Example: If you name the pdisk datastores LUN_01 and LUN_02, and the OS datastore LUN_OS, and enter LUN as the value of PDisk_Datastore_Match, the scripts cannot differentiate internally between the pdisk datastores and the OS datastore. To resolve this issue, rename the OS datastore so LUN is not in the name.

Physical Disk Settings pdiskSizeGB The size of the Teradata Database system pdisks.
Example:
  • pdiskSizeGB:800
Physical Disk Settings uniqueDisks Knowledge of Teradata Database systems and vSphere storage set up is necessary to use this setting.

Teradata recommends keeping the default setting to true. Do not change the default setting if you do not plan to use this feature.

Change the setting to false if you want more than one Teradata Database system data disk to be placed into each Teradata Database datastore. The deployment executable file enumerates the datastores found on a given ESXi host using the PDisk_Datastore_Match expression. If set to false, the Teradata Database (TPA) nodes create pdisks without considering ownership when deploying on shared storage, SANs, or when there is not enough disks available. Database performance may be impacted. You can create as many Teradata Database system data disks of pdiskSizeGB that fit into the first one and then move to the next one.

Example:
  • If each of the enumerated datastores were 900GB and the pdiskSizeGB was set to 300GB, then during deployment three Teradata Database system data disks would be placed in each datastore until each vNode has three Teradata Database system data disks.
System Setting PhysicalCoresPerTPA Changes the number of physical cores assigned to each Teradata Database (TPA) VM. This does not affect the other node types.

The total physical cores consumed by your Teradata entitlement (license) equals the PhysicalCoresPerTPA setting times the number of TPA nodes.

Temporal Settings

Temporal

TemporalDaylightSavings

TemporalTimeDateWZControl

TemporalTimeZoneHour

TemporalTimeZoneMinute

TemporalTimeZoneString

If you plan to use Temporal, change the setting to true. If you do not plan to use it, accept the default of false. Refer to Temporal Settings.

You must enable Temporal before deployment. If you did not enable it before deployment, you must redeploy the VM to enable it. If you do not want to redeploy the VM, contact your Teradata Sales representative to purchase a customer engagement.

If you plan to enable Temporal and restore data from a different Teradata Database, review Knowledge Article KAP1BACEE , Migrating to TimeDateWZControl first. This scenario can result in subtle data quality issues which are outlined in the Knowledge Article.
Example:
  • Temporal:false
  • TemporalDaylightSavings:false
  • TemporalTimeDateWZControl:0
  • TemporalTimeZoneHour:0
  • TemporalTimeZoneMinute:0
  • TemporalTimeZoneString:America Pacific
Other Teradata Database Feature Settings

SecureZones

RowLevelSecurity

Columnar

[Optional] Columnar, Row Level Security, and Secure Zones are Teradata Database features that can be enabled by setting it to true. If you do not plan to use a feature, accept the default of false. Columnar must be purchased to be enabled.
Secure Zones is supported on Teradata Database 15.10 and later.
Site ID SiteID The Site ID representing this system. This is optional.
Mainframe Settings MainframeLHID

The logical Host ID for mainframe connectivity. The default is -1 to indicate the deployed system will not connect to a mainframe.

Example:
  • MainframeLHID:-1
Folder Setting Folder Folder name where the VM is being deployed on the vSphere server.
IP Address Setting IPAddressSetting Indicates whether to use a static or dynamic IP address. For a two node MPP deployment, the IP address must be static.
License Settings Tier Database license tier that matches the software package you ordered.
  • ET - Enterprise tier (default)
  • AT - Advanced tier
  • BT - Base tier
See Teradata Database License Tiers.
EntitlementID Unique string of characters that enable you to use the licensed software.

Obtain the EID from the email you received when you purchased the license.

LicensePeriodInYears Duration of license period, in years.
  • 1 (default)
  • 3

Obtain this integer from the email you received when you purchased the license.

The license period is visible as a suffix to the name in the Product column after you log in to the Teradata EMS server.

TeradataEmsURL URL used to verify Teradata license, assuming you are deploying on a system with Internet access. The default is https://slem.teradata.com/ems.

Change this setting only if your site uses a proxy server.