The nodenames utility displays a list of network interfaces on the node where it is run. It is used internally by the tlsutil utility and can also be run from the command line.
The information provided by nodenames is helpful when you generate a Certificate Signing Request (CSR) because it provides the common name (CN) and subject alternative names (SANs) that are used in the CSR.
The utility requires all of the database names provided by the user be found in DNS. Teradata recommends that these names:
- are fully qualified
- do not contain COP aliases
- do not contain IP addresses
- do not contain wildcards
There are times, such as with cloud databases, where the database names are not in the DNS. In that case, the -n option can be used to allow such database names.
Use the first name produced by nodenames as the CN attribute. Include all the names produced by nodenames in the SANs, including the CN name.
nodenames Syntax
nodenames [-n] [-v] database_name ...
Syntax Elements
- -n
- Causes nodenames to skip testing that the database names are in DNS. This is useful on cloud systems.
- -v
- Optional. Displays verbose output.
- database_name
- One or more names of the database. Teradata recommends using the fully qualified name of the database. For example: mydb.example.com.The fully qualified database name must be in DNS for nodenames to recognize it.
nodenames Example
From the command line, run:
#/opt/teradata/tdgss/bin/nodenames mydb.example.com
Result:
mydb1.example.com mydbcop1.example.com