About Defining Routes for Source and Target COP Entries - Teradata Data Mover

Teradata Data Mover Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
fsa1467305282096.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4102
Product Category
Analytical Ecosystem
Next, the network routes for the COP entries can be added to the /etc/sysconfig/network/routes file. Assume the eth2 interface is used for all public network traffic to and from the DM managed server and is, therefore, the default network interface for the server. Assume the IP address 153.64.107.254 is the gateway for all traffic coming into and out of the DM managed server. The following is added to the /etc/sysconfig/network/routes file on the DM managed server to add specific routes for the COP entries on dmdev and dmtest:
# default XXX.XXX.XXX.XXX - ethX
default 153.64.107.254 - eth2

# routes to system dmdev
153.64.209.91 153.64.107.254 - eth4
153.64.209.92 153.64.107.254 - eth4

# routes to system dmtest
153.64.106.78 153.64.107.254 - eth5
153.64.106.79 153.64.107.254 - eth5

These entries force all network traffic between the DM managed server and dmdev to use the eth4 interface and all network traffic between the DM managed server and dmtest to use the eth5 interface.