This document includes step-by-step instructions for enabling and configuring TCP/IP networking services on OpenVMS 8.4. This example was created using OpenVMS running on an AXPbox Alpha simuator while logged in as SYSTEM. However, this document may be applicable to other versions of OpenVMS, and/or running on a physical AlphaServer.
This example uses the following network values:
Domain: colornet.com
Gateway: 192.168.100.1
BIND: 8.8.8.8 (Google DNS)
This example uses the following node specific values:
TCP/IP Address: 192.168.100.102
Node Name: stimpy.colornet.com
MAC Address: 08-00-2B-E5-40-02
For networking exmples elsewhere on this site with another Alpha VMS node, these instructions were repeated by substituting the following node specific values:
TCP/IP Address: 192.168.100.101
Node Name: ren.colornet.com
MAC Address: 08-00-2B-E5-40-01
Please adjust all of these values to whatever is appropriate for your environment. For reference, the full example network is documented here: OpenVMS Simulator Network
This example configures and starts the following services (client & server): telnet, ssh
1. Run TCP/IP Configuration command procedure
$ @sys$manager:tcpip$config.com
2. Select Core Environment
HP TCP/IP Services for OpenVMS Configuration Menu
Configuration options:
1 - Core environment
2 - Client components
3 - Server components
4 - Optional components
5 - Shutdown HP TCP/IP Services for OpenVMS
6 - Startup HP TCP/IP Services for OpenVMS
7 - Run tests
A - Configure options 1 - 4
[E] - Exit configuration procedure
== Main Menu 1 - Core Environment ==
HP TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
3. Domain - Core Environment Option 1
DOMAIN Configuration
Enter Internet domain: colornet.com
4. Interfaces - Core Environment Option 2
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=Not Configured, Active=Not Configured
Configuration options:
0 - Set The Target Node (Current Node: STIMPY)
1 - WE0 Menu (EWA0: TwistedPair 100mbps)
[E] - Exit menu
Enter configuration option: 1
HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu (Node: STIMPY)
Configuration options:
1 - Add a primary address on WE0
2 - Add an alias address on WE0
3 - Enable DHCP client to manage address on WE0
[E] - Exit menu
Enter configuration option: 1
* Is this address used by Clusters over IP (IPCI) [NO]:
IPv4 Address may be entered with CIDR bits suffix.
E.g. For a 16-bit netmask enter 10.0.1.1/16
Enter IPv4 Address []: 192.168.100.102
Default netmask calculated from class of IP address: 255.255.255.0
IPv4 Netmask may be entered in dotted decimal notation,
(e.g. 255.255.0.0), or as number of CIDR bits (e.g. 16)
Enter Netmask or CIDR bits [255.255.255.0]:
Enter hostname []: stimpy.colornet.com
Requested configuration:
Node : STIMPY
Interface: WE0
IPCI : No
Address : 192.168.100.102/24
Netmask : 255.255.255.0 (CIDR bits: 24)
Hostname : stimpy.colornet.com
* Is this correct [YES]:
5. Router - Core Environment Option 3
DYNAMIC ROUTING Configuration
Dynamic routing has not been configured.
You may configure dynamic ROUTED or GATED routing.
You cannot enable both at the same time. If you want
to change from one to the other, you must disable the
current routing first, then enable the desired routing.
If you enable dynamic ROUTED routing, this host will use the
Routing Information Protocol (RIP) - Version 1 to listen
for all dynamic routing information coming from other
hosts to update its internal routing tables.
It will also supply its own Internet addresses to
routing requests made from remote hosts.
If you enable dynamic GATED routing, you will be able to
configure this host to use any combination of the following
routing protocols to exchange dynamic routing information
with other hosts on the network:
Routing Information Protocol (RIP) - Version 1 & 2
Router Discovery Protocol (RDISC)
Open Shortest Path First (OSPF)
Exterior Gateway Protocol (EGP)
Border Gateway Protocol (BGP-4)
Static routes
* Do you want to configure dynamic ROUTED or GATED routing [NO]:
A default route has not been configured.
* Do you want to configure a default route [YES]:
Enter your Default Gateway host name or address: 192.168.100.1
192.168.100.1 is not in the local host database.
If you want to enter the default gateway in the local host
database, enter its host name. Otherwise, enter <CR>.
Enter the Default Gateway host name []: vmsnet.colornet.com
6. BIND Resolver - Core Environment Option 4
BIND RESOLVER Configuration
A BIND resolver has not been configured.
HP TCP/IP Services for OpenVMS supports the Berkeley Internet Name
Domain (BIND) resolver. BIND is a network service that enables clients
to name resources or objects and share information with other objects
on the network.
Before configuring your system as a BIND resolver, you should
first be sure that there is at least one system on the network
configured as either a BIND primary or secondary server for
this domain.
You can specify a BIND server by its address or name;
however, if specified by name, an entry for it must
exist in the TCPIP$HOST database.
You will be asked one question for each server.
Press Return at the prompt to terminate the list.
Enter your BIND server name: 8.8.8.8
8.8.8.8 is not in the local host database.
If you want to enter the server in the local host
database, enter the server name. Otherwise, enter <CR>.
Enter remote BIND server name []: dns.google.com
Enter next BIND server name:
7. Select Client Environment
HP TCP/IP Services for OpenVMS Configuration Menu
Configuration options:
1 - Core environment
2 - Client components
3 - Server components
4 - Optional components
5 - Shutdown HP TCP/IP Services for OpenVMS
6 - Startup HP TCP/IP Services for OpenVMS
7 - Run tests
A - Configure options 1 - 4
[E] - Exit configuration procedure
== Main Menu 2 - Client Components ==
HP TCP/IP Services for OpenVMS Client Components Configuration Menu
Configuration options:
1 - DHCP Client Disabled Stopped
2 - FTP Client Disabled Stopped
3 - NFS Client Disabled Stopped
4 - REXEC and RSH Disabled Stopped
5 - RLOGIN Disabled Stopped
6 - SMTP Disabled Stopped
7 - SSH Client Disabled Stopped
8 - TELNET Disabled Stopped
9 - TELNETSYM Disabled Stopped
A - Configure options 1 - 9
[E] - Exit menu
8. SSH Client - Client Components Option 7
SSH CLIENT configuration options:
1 - Enable service on this node
[E] - Exit SSH_CLIENT configuration
Enter configuration option: 1
The SSH SERVER is not enabled.
* Do you want to configure SSH SERVER [NO]: yes
SSH configuration options:
1 - Enable service on this node
[E] - Exit SSH configuration
Enter configuration option: 1
* Create a new default server host key? [YES]:
* Please enter host key type DSA or RSA [RSA]:
Creating private RSA key file: TCPIP$SSH_DEVICE:[TCPIP$SSH.SSH2]HOSTKEY
Creating public RSA key file: TCPIP$SSH_DEVICE:[TCPIP$SSH.SSH2]HOSTKEY.PUB
9. TELNET - Client Components Option 8
TELNET configuration options:
1 - Enable service on this node
[E] - Exit TELNET configuration
Enter configuration option: 1
10. Start TCP/IP Services
HP TCP/IP Services for OpenVMS Configuration Menu
Configuration options:
1 - Core environment
2 - Client components
3 - Server components
4 - Optional components
5 - Shutdown HP TCP/IP Services for OpenVMS
6 - Startup HP TCP/IP Services for OpenVMS
7 - Run tests
A - Configure options 1 - 4
[E] - Exit configuration procedure
== Main Menu 6 - Startup HP TCP/IP Services for OpenVMS ==
Begin Startup...
...
Startup request completed.
11. Test TCP/IP Services
$ tcpip ping www.google.com
PING www.google.com (172.217.11.4): 56 data bytes
64 bytes from 172.217.11.4: icmp_seq=0 ttl=116 time=114 ms
64 bytes from 172.217.11.4: icmp_seq=1 ttl=116 time=54 ms
64 bytes from 172.217.11.4: icmp_seq=2 ttl=116 time=93 ms
----www.google.com PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 54/91/114 ms
12. Add TCP/IP Services to OpenVMS Startup & Reboot
$ set def sys$manager
$ edit systartup_vms.com
Uncomment the following line (by removing $!):
$!$ @SYS$STARTUP:TCPIP$STARTUP.COM
$ @sys$system:shutdown
...
Should an automatic system reboot be performed [NO]? yes
...
