This chapter presents an overview of MultiNet configuration tasks and the configuration tools that MultiNet provides.
MultiNet configuration consists of the following tasks:
|
Establishing Basic IP Connectivity |
Configures your system so it can reach other systems with commands such as FTP (for transferring files) and TELNET (for connecting to remote systems), both of which are described in the MultiNet User's Guide. The configuration options offered during MultiNet installation (see the Installation and Introduction) allow you to establish basic IP connectivity over a single Ethernet interface. To establish basic IP connectivity over any of the other MultiNet-supported network interfaces, see Chapter 11. |
|
Configuring services |
Allows other hosts to access resources on your MultiNet system such as OpenVMS print queues, files, and fonts for X displays. By default, installing MultiNet configures several of the most often used services. To learn about MultiNet services in general, see Chapter 12. For details
on configuring specific services such as GATED (for dynamic routing),
DOMAINNAME (for Domain Name System-based host name lookup service), and FTP
(for file transfers), refer to the appropriate chapters |
When MultiNet starts, it obtains configuration parameter values from a set of configuration files all found in the MULTINET: directory. Once MultiNet is running, you can change the configuration by modifying the current configuration in memory using the MULTINET SET command or by defining MultiNet logicals.
Note! Modifying the current MultiNet configuration using the MULTINET SET command and MultiNet logicals does not affect the MultiNet configuration files. Consequently, your changes are lost the next time unless you also modify MultiNet configuration files.
To start MultiNet, issue the following commands at the DCL prompt:
$ REPLY/ENABLE=NETWORK/TEMP
$ @MULTINET:START_MULTINET
You must add an invocation of START_MULTINET.COM to the OpenVMS SYSTARTUP procedure, so MultiNet starts automatically the next time your system reboots.
To make sure MultiNet is running, use the MULTINET CHECK command. If the message "all tests passed" appears, MultiNet is running. If error messages appear, note the source of the errors, and refer to the corresponding chapter in this guide for details on modifying the configuration.
MultiNet starts with accounting enabled by default. To disable accounting in the Master Server, define the logical name MULTINET_SERVER_NOACNT with value 1 in the SYSTEM table before the Master Server starts.
There are instances when you have to restart MultiNet. You can do this without rebooting VMS by executing the START_SERVER.COM command procedure in the MultiNet directory. This doesn’t reinitialize any interfaces, it most likely will not affect any running processes, it will not reload the kernel.
Note! FTP and many other servers (POP3, REXEC, TELNET, etc.) will be unavailable for a short period so there could be brief interruptions with services.
MultiNet configuration utilities, which you invoke with the MULTINET CONFIGURE command, provide a command-line interface for each MultiNet configuration function.
Note! In general, you should never directly edit the configuration files. In the case of a network interface configuration, however, you may need to manually create and edit a device-specific configuration (see Chapter 11).
Modifying MultiNet configuration files with the CONFIGURE utility's command-line interface consists of the following steps.
Before running MULTINET CONFIGURE, make sure the logical names MULTINET and MULTINET_ROOT are defined. These logical names are defined during installation but can be undefined manually or by rebooting without starting MultiNet automatically. To verify these logical names are defined, issue this command:
$ SHOW LOGICAL MULTINET*
If the logical names are undefined, issue this command:
$ @SYS$SYSDEVICE:[MULTINET.your_hostname.MULTINET]START_MULTINET LOGICALS
If the logical names are already defined, executing this command does not cause a problem.
To start the command-line configuration utilities, enter:
$ MULTINET CONFIGURE /qualifier
/qualifier specifies the MultiNet feature you want to configure.
This table lists the tools available for editing configuration files and the commands that invoke them:
|
Configuration Type |
Configuration Utility |
DCL Command |
|
Network Interfaces |
NET-CONFIG |
$ MULTINET CONFIGURE /INTERFACE |
|
Electronic Mail |
MAIL-CONFIG |
$ MULTINET CONFIGURE /MAIL |
|
Remote Print Queues |
PRINTER-CONFIG |
$ MULTINET CONFIGURE /PRINTERS |
|
MultiNet Servers |
SERVER-CONFIG |
$ MULTINET CONFIGURE /SERVERS |
|
MultiNet DECnet-over-IP Circuits |
DECNET-CONFIG |
$ MULTINET CONFIGURE /DECNET |
|
MultiNet NFS Server |
NFS-CONFIG |
$ MULTINET CONFIGURE /NFS |
Once the utility is started, its name appears as a prompt (such as NET-CONFIG>) at which you can enter commands.
By default, each command-line configuration utility modifies the configuration files that MultiNet reads when it starts. Usually, you need only modify configuration information and exit from the utility to change a configuration file.
To maintain multiple configuration files, however, use the configuration utility GET command to load and replace the configuration currently loaded. This feature is useful for abandoning modified configurations without quitting the utility.
For example, to load a test configuration file named MULTINET:TEST.CONFIGURATION into NET-CONFIG, enter:
NET-CONFIG>GET MULTINET:TEST.CONFIGURATION
After you modify the configuration, you can save the file under the same name or a different name.
Note! Although all command-line configuration utilities allow you to maintain multiple configuration files under different names, MultiNet only reads the standard configuration files, all of which are in the MULTINET: directory.
|
Feature |
File and Description |
|
BOOTP |
BOOTP-SERVER.CONFIGURATION — Provides booting information for diskless hosts using the BOOTP protocol. This file can be edited; use a text editor to maintain this file. |
|
Configuration |
NETWORK_DEVICES.CONFIGURATION — Lists network devices and their configurations. This file is maintained by NET-CONFIG, and is read when MultiNet starts. Do not edit this file! |
|
DHCP |
DHCPD.CONF — Provides booting information for diskless hosts using the DHCP or BOOTP protocol. This file can be edited; use a text editor to maintain this file. |
|
DNS |
NAMED.CONF — Contains configuration information for the Internet DNS (Domain Name System) and the locations of other name service database files. This file can be edited; use a text editor to maintain this file. |
|
General |
MULTINET_VERSION — Contains the MultiNet version and revision level. Do not edit this file! |
|
Host Tables |
HOSTS.LOCAL — Contains the local host table, with protocols and services for your local network. This file can be edited; use a text editor to maintain this file.
HOSTS.SERVICES — Contains the official protocols and services supported by the local host (refer to RFC-943 for additional information). Do not edit this file!
HOSTS.TXT — Contains the DDN NIC host table, which lists the host names and Internet addresses of the Internet hosts known to the NIC. Because of the large size of this file, the HOSTS.TXT file provided with the MultiNet distribution includes an entry for NIC.DDN.MIL (the NIC information server system) only, rather than the entire file. You can retrieve a current copy of the NIC host table from NIC.DDN.MIL (formerly SRI-NIC.ARPA) via anonymous FTP. Do not edit this file! The HOSTS.TXT file located on NIC.DDN.MIL is no longer maintained by the DDN NIC. This file contains out-of-date information, and should be used with caution. If your host is connected to the Internet, it is highly recommended that you use DNS to provide host-to-IP address mappings.
HOSTTBLUK.DAT — Contains a compiled, binary version of the two host table files MULTINET:HOSTS.LOCAL and MULTINET:HOSTS.TXT. It contains the names of all hosts (in alphabetical order) in the host table files. MultiNet utilities refer to HOSTTBLUK.DAT when attempting to complete a partially specified host name. Do not edit this file!
NETWORK_DATABASE — A compiled, binary version of the host, protocol, and services information contained in the files MULTINET:HOSTS.LOCAL, MULTINET:HOSTS.SERVICES, and MULTINET:HOSTS.TXT. The NETWORK_DATABASE file allows applications to quickly look up the name or address of any host known in the host table files. Do not edit this file! When DNS is disabled, the NETWORK_DATABASE file provides the sole host lookup facility. When DNS is enabled, this database is only referred to if a name service query fails. |
|
NFS |
NFS.CONFIGURATION — Contains configuration information for the MultiNet NFS Client and NFS Server products. Do not edit this file! |
|
NTP |
NTP.CONF — Contains configuration information for the Network Time Protocol (NTP) service. This file can be edited; use a text editor to maintain this file. |
|
Printing |
REMOTE-PRINTER-QUEUES.COM — Configuration file for customizing printer queues. You must use MULTINET CONFIGURE/PRINTER to modify this file. You cannot edit it directly. |
|
RARP |
RARP.CONFIGURATION — Used by the MultiNet RARP server to determine Ethernet-to-IP address mappings so hosts and PCs can query the server to obtain their IP address. This file can be edited; use a text editor to maintain this file. |
|
“R” services |
HOSTS.EQUIV — Used by BSD "R" services to perform authentication on incoming connections. This file can be edited; use a text editor to maintain this file. |
|
Routing |
GATED.CONF — Used by the Gateway Daemon (GATED) service to configure the RIP, EGP, HELLO, OSPF, and BGP dynamic IP routing protocols. This file can be edited; use a text editor to maintain this file. |
|
Servers |
SERVICES.MASTER_SERVER — Contains a list of the MultiNet servers and their configurations. This file is maintained by SERVER-CONFIG and is used by the MultiNet master server process. Do not edit this file! |
|
SNMP |
SNMPD.CONF — Contains configuration information for the MultiNet SNMP (Single Network Management Protocol) agent. Edit this file manually. |
|
SMTP |
SMTP_ALIASES — Contains SMTP (Simple Mail Transfer Protocol) mail alias and mailing list expansions. This file can be edited; use a text editor to maintain this file.
START_SMTP.COM and START_SMTP_LOCAL.COM — Contain SMTP configuration information. Do not edit these files. |
|
SSH |
SSH2_DIR:SSHD_CONFIG - Contains configuration information for the SSH server. This file can be edited; use a text editor to maintain this file.
SSH2_DIR:SSHD2_CONFIG - Contains configuration information for the SSH2 server. This file can be edited; use a text editor to maintain this file. |
|
TELNET |
MAP3270.DAT — Contains a keymap used by the TN3270 module of the TELNET client. The keymap maps keystrokes on standard ASCII terminals to IBM 327x special function keys. This file can be edited; use a text editor to maintain this file. |
Once you have loaded a configuration file into the configuration utility, you can modify the configuration with any commands the utility offers. Most utilities provide an assortment of SET and ADD commands. For guidelines on configuring with each utility, refer to the corresponding chapter in this guide.
For complete details on the commands available in each utility, refer to the corresponding chapter in the MultiNet Administrator's Reference or refer to the equivalent online reference by entering:
$ HELP MULTINET CONFIGURE qualifier
qualifier is the qualifier corresponding to the utility.
All of the TN3270 and TN5250 clients have been modified to properly handle large key mapping files like MAP3270.DAT and MAP5250.DAT without causing any access violations.
The extended TN3270 client has been modified to allow you to change its notion of the local language.
To use the extended TN3270 client, do the following:
$ DEFINE MULTINET_TN3270_EMULATOR DPC_EXTENDED
To change the local language,
$ DEFINE MULTINET_DPC_TN3270_LANGUAGE language
The language parameter can be one of the following:
|
BRAZILIAN |
FRENCH CANADIAN |
NEW HEBREW |
SPANISH |
|
BUILTIN HEBREW |
GERMAN |
OLD BELGIAN |
SPANISH SPEAKING |
|
DANISH |
ICELANDIC |
OLD HEBREW |
SWISS |
|
FINNISH |
ITALIAN |
OLD PORTUGUESE |
UK ENGLISH |
|
FRENCH |
NEW BELGIAN |
PORTUGUESE |
US ENGLISH |
Because modified configuration files are not read until the next time MultiNet starts, it is useful to verify the validity of your changes before restarting. The NET-CONFIG and SNMP-CONFIG configuration utilities provide a CHECK command specifically for verifying your configuration. To verify changes made with either of these configuration utilities, use the CHECK command at the configuration utility prompt.
Note! All MultiNet configuration utilities automatically execute the CHECK function when you exit.
If there is a problem in the configuration, CHECK issues an error or warning message describing the problem.
· An ERROR message indicates a potentially fatal problem; for example, a problem that could cause network access to fail completely.
· A WARNING message indicates a less serious problem; for example, a problem that could cause the network to function in an unexpected manner.
If the utility displays error messages, use the SHOW command to view your changes and spot the error that caused the message. Correct the error using the configuration utility, then use the CHECK command to confirm the validity of the configuration.
The following example shows the automatic operation of CHECK after a NET-CONFIG session. Because the user executed an ADD command but specified a nonexistent OpenVMS device, CHECK issued an ERROR message. Because the user gave no IP address, CHECK issued a WARNING message.
NET-CONFIG>ADD SL1
[Adding new configuration entry for device "sl1"]
VMS Device [TTA0] TXA0
Baud Rate: [UNSPECIFIED] RETURN
Header Compression Mode: [DISABLED] RETURN
IP Address: [NONE] RETURN
Point-to-Point Device IP Destination Address: [NONE] RETURN
IP SubNet Mask: [NONE] RETURN
[add (Serial Line IP): Csr=NONE, Flags=%X0]
NET-CONFIG>EXIT
ERROR: sl1 can't $ASSIGN to SLIP Device:
%SYSTEM-W-NOSUCHDEV, no such device available
WARNING: sl1 has no protocol addresses specified
This network configuration FAILED the sanity check.
Write startup file anyway ? [NO] NO
$
After making changes to the configuration you have read in, use the configuration utility's SAVE or WRITE command to save the configuration either to the default or to non-standard files.
For example, to save network interface parameters, enter the following NET-CONFIG command:
NET-CONFIG>SAVE
Note! If you use the EXIT command to exit a configuration utility, the corresponding configuration files and startup command procedures are updated automatically.
If you do not want to save the edited configuration, you have two choices:
· Quit the utility without saving.
· Load the original configuration file back into the utility.
To quit a configuration utility without saving your changes, use the QUIT command and enter NO when prompted to save the configuration.
To save the configuration and exit:
· Use the EXIT command, which automatically saves the configuration without prompting.
· Use the QUIT command and enter YES when prompted to save the configuration.
Note! Most configuration changes take effect the next time MultiNet starts. In some cases, however, such as when you add new network interfaces and change some global parameters, the changes take effect only after the system reboots. The configuration procedures in this guide tell you when to restart MultiNet or reboot your system.
In almost all cases, you must restart some portion of MultiNet when you change MultiNet configuration files. In some cases, such as adding new network interfaces or changing some global parameters, you may have to reboot your system before the changes take effect.
Certain configurations of some features, such as the SNMP agent, can be reloaded into the current configuration without restarting the MultiNet master server process (MULTINET_SERVER).
The configuration procedures in this guide indicate when reloading, restarting the MULTINET_SERVER process, or rebooting your system is required.
The MULTINET SET command provides a mechanism for knowledgeable system managers to manipulate the current configuration without restarting the MULTINET_SERVER process or rebooting the system. Use MULTINET SET with caution.
You can use MULTINET SET to:
· Modify local timezone information
· Modify DECnet-over-IP circuits
· Modify network interface configuration
· Manipulate the ARP table
· Manipulate the routing table
If you use the /SNMP_HOST qualifier, MULTINET SET can affect ARP tables, routing tables, and network interface configuration of remote hosts running a MIB-II-compliant SNMP agent, such as the MultiNet SNMP agent (see Chapter 23).
For a detailed description of MULTINET SET, refer to the MultiNet Administrator's Reference.
Note! Because MULTINET SET affects only the current configuration and does not affect the configuration files, any changes made with MULTINET SET are lost the next time you start MultiNet.