Before starting this procedure, do the following:
If your deployment site can access the web-based Teradata EMS server, licensing information is passed between your site and the server over the Internet automatically. If your site cannot access the Internet, use this procedure to convey licensing information between the two locations manually.
Some steps require a device with Internet access, as well as access to the Teradata EMS server.
- Open a VMware vSphere PowerCLI shell version 5.5 or later.
- Navigate to the directory containing the Teradata Database on VMware deployment executable file (C:\mylocation\Teradata_Deployer\).
- [Optional] For troubleshooting purposes, make copies of the common.IT.properties.json and node.IT.properties.json properties files, label them according to the system to be deployed, and then save them.
- Run tdc.deploy.exe, using the properties files originally used to deploy the VMs.
At the prompt, type deploy, and press Enter.
- Select the Common Properties file, and press Enter.
- Select the Node Properties file, and press Enter.
- If a message warns you that running scripts is disabled, you must set the execution privileges, then proceed to the next step. See PowerCLI Requirements.
- From the PowerCLI terminal, type deploy. For a description of the actions this state (command) performs, see PowerCLI Commands for Teradata Database on VMware.
Type Y when the following warning appears.
Failed connecting to the given Teradata EMS Server: https://slem.teradata.com/ems Warning: Failed connecting to the Teradata EMS Server. Is this a non-internet connected site deployment? [Y] Yes [N] No [?] Help (default is "N"):
Record the following values from the system details that appear in the PowerCLI terminal:
- Package Type
Number of physical cores to be activated.
Client 1 Info
Equivalent to Locking Code on the Teradata EMS server.
- Directory where the license file is placed after the activation on the EMS server (C:\mylocation\Teradata_Deployer\telm).
–––-System Details---- EntitlementId: 9d843a13-76fa-3e67-9f8a-1e41f3d1ad0a Package Type: VMware Enterprise Activation Quantity: 4 Client 1 Info: *1RDV5L3RKL4TRM5 Info: After the license has been generated, place the license file <lservrc> in the following directory : C:\mylocation\Teradata_Deployer\telm\ then re-run tdc.deploy.exe
Using a device with Internet access, activate the license on the Teradata EMS server.
- Using a device with Internet access, log in to the Teradata EMS server: The URL is https://slem.teradata.com/ecp.
- Click to expand either the Products or Orders section.
Click Activate for the target product license, complete the following fields, then click Submit:
- Quantity to Activate: number of physical cores
- Locking Code: Client 1 Info string from the PowerCLI terminal message on the deployment site
- [Optional] User Activation Data
The Step 4 - Finish screen displays a message that the activation is complete, and that the license was emailed to the activator.
The email displays the license string created for the activation, and includes an attached file, license.zip, that also lists the license string.
- [Optional] Click Download License File to save a local copy of the file (license.zip).
- Expand the license.zip file from the email or download. You will use the resulting license file (lservrc) when you return to the deployment site.
- Click Done. In the Products and Orders sections of the home page, updated Activated and Available reflect the quantities of cores used and remaining.
- Back on the deployment site, place the license file (lservrc) in the telm directory indicated earlier in this procedure (C:\mylocation\Teradata_Deployer\telm).
From the PowerCLI terminal, select the deploy step and type Y when the following warning appears.
Cannot ping Teradata EMS Server Warning: Cannot connect to the Teradata EMS Server. Is this a non-internet connected site deployment?
If the license does not pass validation, the following error appears.
Error: The license file c:\mylocation\Teradata_Deployer\telm\lservrc does not belong to this configuration. Make sure you are choosing the correct common and node property files. Or place the correct license file and try again.To fix the issues, check the properties files, verify the correct license file has been copied to the correct path you recorded earlier in this procedure, and then return to step 14.
If there are no errors, the VM deploys. The deployment executable file is re-entrant, meaning if errors occur, they can be fixed and the executable runs all states again. Action is taken only as needed.
After the VM deploys, complete the applicable procedures under Deployment Verification.