User`s guide

IP Address Management
Connecting to a local IP network
Pipeline User’s Guide Preliminary January 30, 1998 3-7
If the IP addresses are assigned statically, use this setting instead:
Proxy Mode=Always
3
Close and save the profile.
Enabling DNS on the Pipeline
If the local network supports Domain Name System (DNS) servers, you can
configure the local domain name and the IP addresses of those servers in the
Ethernet profile.
If the Pipeline is configured for DNS, users can execute TCP/IP commands such
as Telnet and Ping from the Pipeline terminal server interface with host names
instead of IP addresses. In addition, the List Attempt parameter helps avoid
tearing down physical links by enabling the user to try one entry in the DNS list
of hosts, and if that connection fails, to try the next entry, and so on.
To configure the Pipeline for DNS:
1
Open the Ethernet > Mod Config > DNS menu.
2
Enter your domain name.
For example:
Domain Name=eng.abc.com
3
Specify the IP address of the primary and secondary DNS servers.
For example:
Pri DNS=10.2.3.56
Sec DNS=10.2.3.107
4
If your site supports multiple addresses for a DNS host name, turn on List
Attempt.
List Attempt=Yes
5
Close and save the profile.
Generating UDP checksums
User Datagram Protocol (UDP) supports the optional use of a checksum field for
checking the integrity of both the UDP header and data. The Pipeline always
checks the UDP checksum field of each UDP packet it receives, and generates