The Set Configuration Defaults step allows you to specify default settings used by the Configure Teradata Vantage operation. By setting the values here you do not have to specify settings at several places throughout the configuration process. This is most useful when running in Typical mode, but can also be used in Custom mode.
For each item listed, the initial value is the current default for that item. You can override one or more of the items listed as needed. To retain the current settings as your defaults, click Next without changing them.
The values selected here are used only for new configurations or new storage being added to an existing configuration. For existing configurations, information from the vconfig.gdo is used in place of these settings.
| Field Name | The value in the field: |
|---|---|
| Partition Stripe Width | Allows you to specify the number of sectors to be used as the stripe width when creating new partitions on a disk device. This setting applies to partitions on all disk devices except Teradata storage arrays. For Teradata storage arrays, the value specified for Disk Segment Size is also used as the Partition Stripe Width. The default is 64 sectors. If you want to change the value, it must be divisible by 8. |
| Number of Blocks per Disk Cylinder | Allows you to specify the number of data blocks (disk sectors) to be mapped to each disk cylinder. It is strongly recommended that you use the default value of 3872. Changing the blocks-per-cylinder value can have serious performance impact on Vantage software. |
| RAID Level & Number of LUNS per Drive Group |
Allows you to specify the default RAID level to use when creating LUNs on Teradata disk arrays. The available choices are:
|
| Platform Family |
Allows you to select the type of system family required:
If platform family 7000 Series is selected, a second screen displays asking the user to select one of the following platform 7000 variants:
|
| System Name (Cannot contain spaces) | Allows you to assign an alphanumeric name to the overall configuration. |
| Enable Hot Standby Support (for Teradata Database release V2R5 or later) | This value applies only to MPP systems running Teradata Database release V2R5 or later. Selecting this option on such a system opens the Hot Standby definition screen in the CliqueAmpModeling step and allows you to designate which TPA nodes should be configured as Hot Standby nodes. Clearing this option causes the Hot Standby definition screen to be skipped and no Hot Standby nodes are configured. |
| Enable ECN/ECS Host Channel Support (for Teradata Database release 13.10 or later) and Network TDP (for Teradata Database release 14.10 or later) | Triggers PUT to engage the ECN/ECS Channels Configure step during the Configure Teradata Vantage operation, and allows the user to configure Network Teradata Director Program communication over TCP/IP between the mainframe and the Vantage node. Normally, the presence of one or more channel adapters on a TPA node triggers PUT to engage in the Configure Channels step during the Configure Teradata Vantage operation. When there are external channel adapters, you must select the Enable ECN/ECS Host Channel Support configuration option to prompt PUT to interact with the Configure ECN/ECS Channels step. ECN/ECS configuration is only allowed on Teradata Database release 13.10 or later. Network TDP configuration is only allowed on Teradata Database release 14.10 or later.
|
| Default number of PE vprocs for new nodes | Is the default number of new PE vprocs defined for each new TPA node being added to the system. |
| Enable 5000-series coexistence mode (ADM) for 6000 systems | Allows you to add 6000-series cliques with all-HDD storage to existing 5000-series systems. This option should not be used unless specified by the GSC Change Control in effect for this system expansion. For any questions or additional information on its use, please contact the Teradata Global Support Center.
|
| Force system-wide 4K pdisk alignment |
For systems running Teradata Database release 14.10 or later. Checking this box on a system running Teradata Database release 14.10 or later with no GDOs causes PUT to specify pdisk alignment and block size of 4096 bytes for every pdisk in the system. It is ignored for systems running Teradata Database releases prior to 14.10. For some platforms, PUT enables this option automatically regardless of the setting here.
|
| 6680 coexistence with 6700 | Used to add coexistent 6700 cliques to an existing 6680 system. When selected, this indicates to PUT that the 6700 cliques should be configured according to the guidelines for 6680/6700 coexistence. |
| 6690 coexistence with 6750 | Used to add coexistent 6700 cliques to an existing 6690 system. When selected, this indicates to PUT that it should verify any new 6700 cliques have the appropriate node CPU settings for 6690 coexistence mode. |
| 6700 coexistence with 6750 | Used to add coexistent 6750 cliques to an existing 6700 system. When selected, this indicates to PUT that it should verify any new 6750 cliques have the appropriate node CPU settings for 6700 coexistence mode. |
| Enable CISeg support (for Teradata Database release 15.10 or later) | Enables the Cylinder Index Segregation feature. This feature is allowed only on 1700/1800 platforms with Teradata Database release 15.10 or later. If selected, PUT generates the pfd.conf file. |
| Enable AMP-less TPA Node Support | Allows you to specify which TPA nodes are to be designated as AMP-less TPA nodes. An AMP-less TPA node is a node that has no AMPs or Teradata storage associated with it, but is a TPA node in all other respects. It is sometimes referred to as a PE-only node. If this option is selected, the mpplist step displays the option to define AMP-less TPA nodes. If this option is not selected, the Configure MPPLIST step does not display the AMP-less TPA node option and all TPA nodes must have at least some available storage for use by Teradata. |