Updated: 24 May 2001

DIGITAL TCP/IP Services for OpenVMS

This manual describes new features and changes to the software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections.

Revision Information: This is a new manual.

Operating Systems: OpenVMS Alpha Versions 7.1, 7.2 OpenVMS VAX Versions 7.1,7.2

Software Version: DIGITAL TCP/IP Services for OpenVMS Version 5.0

Compaq Computer Corporation Houston, Texas

Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor.

Compaq conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community.

© Compaq Computer Corporation 1999. All rights reserved.

The following are trademarks of Digital Equipment Corporation: ACMS, ALL-IN-1, Alpha, Compaq, DECdtm, DDCMP, DEC, DECnet, DECNIS, DECserver, DECsystem, DIGITAL, DIGITAL UNIX, DNA, InfoServer, LAT, OpenVMS, PATHWORKS, POLYCENTER, ULTRIX, VAX, VAXstation, VMS, VMScluster, and the Compaq logo.

The following are third-party trademarks:

IBM and OS/2 are registered trademarks of International Business Machines Corporation.

JOIN is a trademark of Competitive Automation, Inc.

NFS, PC--NFS, and Sun are registered trademarks of Sun Microsystems, Inc.

UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd.

All other trademarks and registered trademarks are the property of their respective holders.

Contents

The DIGITAL TCP/IP Services for OpenVMS product is the Compaq implementation of the TCP/IP protocol suite and internet services for OpenVMS Alpha and OpenVMS VAX systems.

For installation instructions, see the manual DIGITAL TCP/IP Services for OpenVMS Installation and Configuration.

Intended Audience

These release notes are intended for:

• System managers using the POLYCENTER Software Installation utility
  For complete installation information, see the DIGITAL TCP/IP Service for OpenVMS Installation and Configuration manual.
• Managers of OpenVMS layered products
• OpenVMS system managers
• Network managers (who may or may not be familiar with UNIX)

Reader's Comments

We welcome your comments on this manual or any of the DIGITAL TCP/IP Services for OpenVMS documents. Send us your comments through any of the following channels:

Internet	openvmsdoc@zko.mts.dec.com
Fax	603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08
Mail	Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698

Conventions

All IP addresses in this book represent fictitious addresses. The following conventions apply to this book.

Convention	Meaning
UPPERCASE TEXT	Indicates names of OpenVMS and UCX commands, options, utilities, files, directories, hosts, and users.
lowercase special type	Indicates UNIX system output or user input, commands, options, files, directories, utilities, hosts, and users.
bold text	Indicates a new term.
italic type	Indicates a variable.
[Return]	Indicates that you press the Return key.
[Ctrl/] x	Indicates that you press the Control key while you press the key noted by x.
[ ]	In command format descriptions, indicates optional elements. The elements are separated by vertical bars (|). You can enter as many as you want.
{ }	In command format descriptions, indicates you must enter at least one listed element. The elements are separated by bars (|).

Version 5.0 completes the change initiated several releases ago when the product name changed from "ULTRIX Connection (UCX)" to "DIGITAL TCP/IP Services for OpenVMS."

"TCPIP" replaces the identifier "UCX" in the following:

• Registered product facility code
• Management command prompt
• All messages, examples, and banners
• All product file names, queues, and databases
• All logical names
• All associated product documentation

This release provides backward compatibility for all UCX logical names and support for most UCX> commands.

Customers should not, at this time, need to upgrade their applications or command procedures that rely on UCX names. The logical name UCX$DEVICE will continue to work. However, Compaq encourages customers to use the new naming convention as soon as possible. Support for the old naming convention is not guaranteed in subsequent releases.

No changes to the License Management Facility (LMF) Product Authorization Keys are required.

The rest of this chapter introduces new features and other changes provided by the DIGITAL TCP/IP Services for OpenVMS Version 5.0 product.

New features in this release include:

• New kernel, based on the DIGITAL UNIX protocol stack ( Section 1.2)
• New option for dynamic routing, the Gateway Routing Daemon (GATED) ( Section 1.3)
• New UNIX style management interface ( Section 1.5)
• New implementation of DNS/BIND ( Section 1.6)
• New method for cluster load balancing ( Section 1.7)
• Dynamic Host Configuration Protocol (DHCP) ( Section 1.8)
• New implementations of NTP and SNMP ( Section 1.9 and Section 1.10)
• Support for OpenVMS External Authentication ( Section 1.11)
• New TELNET Port Driver QIO Interface ( Section 1.12)

Changes for this release include:

• Enhanced error messages ( Section 1.13)
• Installation change for VAX systems ( Section 1.15)
• Timezone configuration changes ( Section 1.17
• Enhanced socket-based application programming interface ( Section 1.18)
• Obsolete commands ( Section 1.19)
• FTP enhancements ( Section 1.20)
• NFS server changes ( Section 1.23)
• SMTP changes ( Section 1.24)

The following sections detail these features and changes.

1.2 New Kernel

The Version 5.0 release incorporates the widely used and proven IPv4 kernel ported from DIGITAL UNIX Version 4.0D.¹ This kernel incorporates several performance enhancements either developed or extended by Compaq, including Classless Inter-domain Routing (CIDR), path MTU discovery, and an optimized TCP/IP stack.

Internet memory buffers (MBUFs) are allocated from nonpaged pool in large groups previously known as clusters. All MBUFs are 512 bytes and are always on a 512--byte boundary. This eliminates the need to allocate small and large MBUFs as previous versions of this product did; quotas and other restrictions no longer apply.

Data structures that are not allocated in MBUFs are allocated directly from the OpenVMS nonpaged pool.

Management control program commands that display statistics have changed accordingly.

1.3 Gateway Routing Daemon

The TCP/IP Services product now implements the gateway routing daemon GATED (pronounced gate-dee) as an alternative to dynamic routing with ROUTED. The Compaq implementation is based on GATED Release 3.5 from the Gatedaemon Project at Cornell University.

GATED differs from ROUTED because it supports both interior and exterior gateway protocols. It obtains information from several routing protocols and selects the best routes based on that information. (ROUTED communicates using the Routing Information Protocol (RIP) only and is intended for small-to-medium networks.)

The protocols are configured in one file TCPIP$GATED.CONF which is read when the gateway routing daemon starts. After GATED starts, you can make configuration changes by editing the configuration file and stopping and restarting GATED.

GATED supports the following protocols:

• Routing Information Protocol (RIP), Version 1 (RFC 1058) and RIP, Version 2 (RFC 1388)
  RIP is a commonly used interior protocol that selects the route with the lowest metric (hop count) as the best route.
• Open Shortest Path First (OSPF), Version 2 (RFC 1583)
  Another interior routing protocol, OSPF is a link-state protocol (shortest path first) and better suited than RIP for use in complex networks with many routers.
• Exterior Gateway Protocol (EGP) (RFC 904)
  EGP exchanges reachability information between autonomous systems. An autonomous system is usually defined as a set of routers under a single administration, using an interior gateway protocol and common metric to route packets. Autonomous systems use exterior routing protocols to route packets to other autonomous systems.
• Border Gateway Protocol (BGP) (RFC 1163, RFC 1267, RFC 1654)
  Like EGP, BGP exchanges reachability information between autonomous systems but supports nonhierarchical topologies. BGP uses path attributes to provide more information about each route. Path attributes can include, for example, administrative preferences based on political, organizational, or security considerations.
• Router Discovery (RFC 1256)
  This protocol is used to inform hosts of the availability of hosts it can send packets to and is used to supplement a statically configured default router.

For more information about GATED protocols and configuration details, see the DIGITAL TCP/IP Services for OpenVMS Management guide. For a list of known GATED problems, see the GateD Consortium home page at

http://www.gated.org/gated-web/support/index.html

1.4 New Management Control Program Commands

The following management control program commands are new for this release. Enter these commands at the TCPIP> prompt. For full descriptions, see the DIGITAL TCP/IP Command Reference or type HELP command at the TCPIP> prompt.

• VERIFY TIMEZONE_INFORMATION
• CONVERT /CONFIGURATION BIND
• SET GATED
• START ROUTE /GATED
• SET NAME_SERVICE /PATH
• SET ROUTE /MASK

Support for UNIX management utilities is now available for system managers experienced in managing a UNIX network subsystem. The utilities listed below are available at the TCPIP> prompt.

Table 1-1 Supported UNIX Management Commands

UNIX Utility	Function
ifconfig	Configures or displays network interface parameters, redefines an address for a particular interface, or sets options such as an alias list, broadcast address, or access filter.
netstat	Displays network statistics of sockets, data link counters, specified protocols or aliases, network interfaces, and a host's routing table.
sysconfig	Displays and maintains the network subsystem attributes.
route	Manually manipulates the routing table.
arp	Controls and displays ARP tables.

Refer to UNIX manual reference pages for valid command flags and other options.

You can also enter the commands listed in Table 1-1 at the DCL prompt by defining them as foreign commands. The command procedure TCPIP$DEFINE_COMMANDS defines these and other UNIX commands. To run this command procedure enter the following:

$ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS

This release provides a new BIND implementation based on the Internet Software Consortium's (ISC) BIND 8.1.2.

1.6.1 BIND Highlights

BIND 8.1.2 offers:

• Dynamic updates
• Change notification
• New configuration
• Flexible categorized logging system
• IP address-based access control for queries, zone transfers, and updates that may be specified on a zone-by-zone basis
• More efficient zone transfers
• Improved performance for servers with thousands of zones
• A resolver that lets you specify a domain search list

This release brings significant changes in the way the BIND name server is configured:

• Some BIND server databases no longer exist; others are renamed.
• BIND 8.1.2 reads configuration information from the ASCII file TCPIP$BIND.CONF.

If you want to use your old configuration, you must convert your old name server configuration to the new BIND 8.1.2 format with the following command:

TCPIP> CONVERT /CONFIGURATION BIND

This command creates the ASCII configuration file TCPIP$BIND.CONF. To modify your name server configuration, choose one of the following methods:

• Edit the template file TCPIP$BIND_CONF.TEMPLATE located in SYS$SPECIFIC:[TCPIP$BIND]. See DIGITAL TCP/IP Services for OpenVMS Management for more information.
• Enter SET CONFIGURATION BIND commands as you did with previous versions of the product.
  If you use SET commands, you must convert the database to the new BIND 8.1.2 format using the CONVERT/CONFIGURATION BIND command. If you enter a SHOW CONFIGURATION BIND command, your configuration changes will appear. However, if you do not also convert the configuration information with the CONVERT/CONFIGURATION BIND command, BIND will not pick up your changes.

You may also use the self-documenting command procedure SYS$MANAGER:TCPIP$BINDSETUP.COM to set up your BIND 8.1.2 environment. This command procedure modifies the ASCII configuration file TCPIP$BIND.CONF. In previous releases, the command procedure UCX$BINDSETUP.COM made changes to the configuration database TCPIP$CONFIGURATION.DAT. Note this change.

1.6.4 BIND Resolver

Default behavior of the BIND resolver has changed since UCX. The BIND resolver once had a search list consisting of the default domain and each of its parent domains with two or more labels. The default search list now contains only the default domain. Also, with the old behavior, as its last step the resolver would do the lookup on what you actually typed in. Now the resolver tries this first, as long as it has at least one dot in it. If there are no dots (for example, just a host name) it is tried as-is, after the resolver appends the elements of the search list.

For example, if you enter TCPIP SHOW HOST FRED and no search list is defined, the resolver performs the following searches by default (assuming FRED could not be found during each search and the default domain is parrot.birds.com):

The V4.x method:

fred.parrot.birds.com fred.birds.com fred.com

The V5.0 method:

fred.parrot.birds.com fred (only tried first here if at least one dot is present)

The UCX to TCP/IP Services rollover performed from TCPIP$CONFIG.COM will create a domain search list for you. The rollover takes the default domain and creates a list consisting of each parent domain. For example, if the default domain is DAISY.DUCK.BIRDS.COM, the search list becomes: DAISY.DUCK.BIRDS.COM, DUCK.BIRDS.COM, BIRDS.COM. You can modify the search list with the SET CONFIGURATION NAME_SERVICE /PATH command. See the DIGITAL TCP/IP Services for OpenVMS Management Command Reference for more information about this new command.

1.7 New Method for Cluster Load Balancing: Load Broker

This release provides a configurable, calculated load-balancing mechanism for distributing the load among cluster members. This method is different from round-robin scheduling (default method used by name servers) in that the calculated load-balancing mechanism takes into account the load on all cluster members. In this scheme, software called the load broker polls cluster members and updates the namespace by sending a dynamic update request to the specified name server.

For information about configuring the new load broker, see DIGITAL TCP/IP Services for OpenVMS Management.

1.8 New DHCP Implementation

The Version 5.0 release provides a new Dynamic Host Configuration Protocol (DHCP) implementation based on the JOIN software product from Competitive Automation.

DHCP provides a centralized approach to configuration and maintenance of IP address space. It allows the system manager to configure various clients on the network from a single location.

The DHCP server allocates temporary or permanent IP addresses to client hosts on the network from a pool of addresses. The server can also configure client parameters such as default gateway parameters, domain name server parameters, and subnet masks for each host running as a DHCP client.

DHCP facilitates network administration by allowing:

• Consistent application of network parameters such as subnet masks and default routers to all hosts on a network
• Support for both DHCP and BOOTP clients
• Static (permanent) mapping of hardware addresses to IP addresses
• Dynamic (temporary) mapping of hardware addresses to IP addresses where the client leases the IP address for a defined length of time

The DHCP protocol is a superset of the BOOTP protocol. In addition to the BOOTP functionality, DHCP offers robust configuration services including IP addresses, subnet masks, default gateways, and more.

Previous versions of TCP/IP Services provided BOOTP-only functionality. The Version 5.0 release also includes a BOOTP-only server that is based on the BOOTP server from previous versions of the product.

You must decide whether to use the previous BOOTP-only implementation or the new DHCP server implementation:

• If you choose to use the BOOTP-only implementation, you cannot use any of the new DHCP functionality. The components cannot coexist on the system because each uses port 67.
• If you choose to use the DHCP implementation, you can configure the DHCP server to support BOOTP clients.

For information about configuring your host as a DHCP server, see the DIGITAL TCP/IP Services for OpenVMS Management guide.

Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal

6551.HTML