Test Connectivity to a Managed Teradata System | Teradata Business Continuity Manager - Testing Connectivity to a Managed Teradata System - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide - 2.00
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
2.00
Published
August 2024
ft:locale
en-US
ft:lastEdition
2025-01-31
dita:mapPath
sko1694443904278.ditamap
dita:ditavalPath
ft:empty
dita:id
otc1639627713801
lifecycle
latest
Product Category
Analytical Ecosystem
Business Continuity Manager tool connTest.sh helps comprehensively test the connectivity to a managed Teradata system. This tool includes the proxycheck tool that was previously used.
  1. Run the following command to test connectivity.
    Usage: /opt/teradata/bcm/scripts/connTest.sh -s <TDPID Or Gateway hostname> (-u <system user> (-P <password> or -L <PEM file location>)) (-f|--force)
    Example:<bcm1>:/opt/teradata/bcm/scripts/connTest.sh -s <td1>
The following is checked after the test is run.
Basic connectivity
  • Teradata system is reachable (on all nodes).
  • Teradata Wallet (tdwallet) is ready to use.
  • Teradata Wallet has the right keys.
  • Business Continuity Manager (tdbcmgmt) user can connect with TD2 authentication using the password in Teradata Wallet.
  • Correct TDGSS version is installed.
Local proxy configuration
  • disableProxyConnection setting is set.
  • Business Continuity Manager user can connect using proxy authentication.
  • TDGSS xml configuration is correct.
  • Local TDGSS certs exist and are in the right place.
  • TDGSS binary matches the settings in the user xml file.
Remote proxy configuration
  • System timezone matches the Business Continuity Manager timezone.
  • TDGSS xml configuration is correct.
  • Gateway password looks correct.
  • TDGSS version is installed on the remote node.
  • Business Continuity Manager server and remote node have copies of each others public certificates.
  • When both the -P <password> and -L <PEM file location> options are provided, the PEM file is prioritized.
  • Place the -f | --force option last as it enforces the execution of all available checks.
  • If you are using a PEM file, make sure it is owned by the 'teradata' user and has permissions 600.
  • If connecting to database nodes with a non-root user (Example: ec2-user), make sure the user has sudo access.