Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Teradata & resolving DNS
- Thread starter ADB1
- Start date
Not sure I understand your requirement, but add this to your hosts file:
#IP address #COP[processor]
111.11.1.11 testcop1.company.com
222.22.2.22 testcop2.company.com
This assumes a 2-node system.
In your middleware configuration file,
use "test" as your hostname.
Hope this helps.
Good luck.
#IP address #COP[processor]
111.11.1.11 testcop1.company.com
222.22.2.22 testcop2.company.com
This assumes a 2-node system.
In your middleware configuration file,
use "test" as your hostname.
Hope this helps.
Good luck.
- Thread starter
- #3
Hi,
WinCLI use GetHostByName("aliascop1"
where alias is the name you give in the login string.
.logon alias/user,password;
How GetHostByName is implemented by Windows is a mystery.
I think it first looks in LMHOSTS, then in HOSTS, then it sends a message to the DNS server on the system to see if it can resolve it. That host may inturn forward it to another DNS server. Or maybe its the other way around., DNS then HOSTS then LMHOSTS.
because we are relying on Windows to handle this resolution if the system is confugured for DNS and there is no DNS server available ( lets say you are traveling and your laptop isn't connected to the network anymore ), GetHostByName can take upwards of 5 minutes to time out
the request sent to the Server. This makes it appear like Logon is taking a long time.
This Timeout is a Windows Network tuneable somewhere in the registry.
--
WinCLI use GetHostByName("aliascop1"
where alias is the name you give in the login string..logon alias/user,password;
How GetHostByName is implemented by Windows is a mystery.
I think it first looks in LMHOSTS, then in HOSTS, then it sends a message to the DNS server on the system to see if it can resolve it. That host may inturn forward it to another DNS server. Or maybe its the other way around., DNS then HOSTS then LMHOSTS.
because we are relying on Windows to handle this resolution if the system is confugured for DNS and there is no DNS server available ( lets say you are traveling and your laptop isn't connected to the network anymore ), GetHostByName can take upwards of 5 minutes to time out
the request sent to the Server. This makes it appear like Logon is taking a long time.
This Timeout is a Windows Network tuneable somewhere in the registry.
--
Hi all,
Couple of things that may help...
1) I'm fairly certain that DNS uses the HOSTS file (either on your pc or on a dns server). WINS resolution uses the LMHOSTS - I haven't got my networking books to hand but I think you'll find that's how it works.
2) speeding up wincli logon can be done by adding one line per Teradata system to your autoexec.bat file (it's true, DOS is still alive and kicking !). The line tells the WinCli s/w how many i/p adresses there are for each system. Assume that you've got a system called TDLIVE which has three i/p addresses, add the following line to your autoexec.bat file:
set tdlive=3
On one of our internal systems this took our logon time from 20-25 seconds down to 2-3.
3) I've never tried the hosts entry with the ".company.com" entry on the end. What does this do ?
Cheers,
Dave
Couple of things that may help...
1) I'm fairly certain that DNS uses the HOSTS file (either on your pc or on a dns server). WINS resolution uses the LMHOSTS - I haven't got my networking books to hand but I think you'll find that's how it works.
2) speeding up wincli logon can be done by adding one line per Teradata system to your autoexec.bat file (it's true, DOS is still alive and kicking !). The line tells the WinCli s/w how many i/p adresses there are for each system. Assume that you've got a system called TDLIVE which has three i/p addresses, add the following line to your autoexec.bat file:
set tdlive=3
On one of our internal systems this took our logon time from 20-25 seconds down to 2-3.
3) I've never tried the hosts entry with the ".company.com" entry on the end. What does this do ?
Cheers,
Dave
To remove the requirement that you add the <hostname>cop<n> aliases to your hosts file you can add them to the dns directly.
It can be a big deal visiting many workstations just to update hosts files, so much better to add the cop IP addresses to your site's DNS database.
Contact the administrator of your network/DNS to discuss how this can be done.
Of course this does nothing to resolve the issue of setting the environment variable for your host to the number of COPs available...
Some examples:
System name is mytera and has PEs running on 10.1.1.10 thru 10.1.1.13
Domain name is needlenose.com
Add the following to your hosts file or DNS database
10.1.1.10 myteracop1.needlenose.com
10.1.1.11 myteracop2.needlenose.com
10.1.1.12 myteracop3.needlenose.com
10.1.1.13 myteracop4.needlenose.com
You may omit the needlenose.com if you do not usually fully qualify internal system names and you are using the hosts file.
And to speed up CLI logons set an environment variable MYTERA=4 (since 4 COPs are available). You can use a batch file to do this, but I prefer setting a SYSTEM variable using the Environment Variables dialog accessible from the System control panel applet on NT/W2K
Regards,
TeraOz
It can be a big deal visiting many workstations just to update hosts files, so much better to add the cop IP addresses to your site's DNS database.
Contact the administrator of your network/DNS to discuss how this can be done.
Of course this does nothing to resolve the issue of setting the environment variable for your host to the number of COPs available...
Some examples:
System name is mytera and has PEs running on 10.1.1.10 thru 10.1.1.13
Domain name is needlenose.com
Add the following to your hosts file or DNS database
10.1.1.10 myteracop1.needlenose.com
10.1.1.11 myteracop2.needlenose.com
10.1.1.12 myteracop3.needlenose.com
10.1.1.13 myteracop4.needlenose.com
You may omit the needlenose.com if you do not usually fully qualify internal system names and you are using the hosts file.
And to speed up CLI logons set an environment variable MYTERA=4 (since 4 COPs are available). You can use a batch file to do this, but I prefer setting a SYSTEM variable using the Environment Variables dialog accessible from the System control panel applet on NT/W2K
Regards,
TeraOz
- Status
Similar threads
- Locked
- Question