Table 1-1 lists the steps required to install MultiNet. As indicated by the footnotes, you need only perform some of the steps if you are installing this version of MultiNet for the first time; you can skip some steps if you have already installed this version of MultiNet on one VMScluster node of the same architecture (VAX, Alpha or I64). The sections in this chapter provide detailed information about each step.
Table 1-1 Installation Steps (Continued)
|
Step |
Read the Section... |
|
1 | |
|
2 | |
|
3 | |
|
4 | |
|
5 | |
|
6 | |
|
7 | |
|
8 | |
|
9 | |
|
10 | |
|
11 | |
|
12 | |
|
13 | |
|
14 | |
|
15 | |
|
16 |
Step 16: Configure the IP Transport Over the Standard Network Interface |
|
17 | |
|
18 | |
|
19 | |
|
20 | |
|
21 | |
|
22 |
Step 22: Install MultiNet Commands in the DCLTABLES.EXE File |
|
23 |
Configuration procedures allow you to configure IP connectivity using one HP LAN interface.
However, you can upgrade MultiNet without changing your existing configuration. As a result, if you upgrade MultiNet on one node in a VMScluster environment, you only need to reboot other nodes of the same architecture to have the upgrade take effect.
During installation, you have the option of configuring IP connectivity for the first network device the configuration procedure finds. If you plan to perform this initial configuration, gather the required information before running VMSINSTALL. Table 1-2 lists the information you must gather. (The table also provides a convenient place for you to record this information so you may refer to it later during the installation.)
If the default configuration is not appropriate for your system, you can configure MultiNet after completing the installation.
Note! If you are upgrading a system already running MultiNet, you do not have to configure anything unless you want to change the existing configuration.
Table 1-2 IP Transport Parameter Checklist (Continued)
|
Parameter Name |
Description |
Your Value |
|
Internet host name |
The name by which your system will be known. If you plan to use DNS to resolve host names, you must use the fully qualified host name supplied by your network administrator or Internet access provider (for example, BIGBOOTE.FLOWERS.COM). Note: It is generally a good idea to use the well-known name for this host; other systems will rely on DNS or host tables to resolve your host name to the appropriate IP address. | |
|
IP address |
The dotted-decimal representation of your system’s IP address. For example, the address 191.87.34.22 is a class B IP address in which 191.87 is the network number and 34.22 is the host number. Obtain your IP address from your network administrator or Internet access provider. | |
|
Subnet mask |
The dotted-decimal representation of a 32-bit mask that determines the network portion of your IP address to allow your network to be subdivided into multiple network segments. For example: If your IP address is 191.87.34.22, and your subnet mask is 255.255.255.0, your network number is 191.87.34 instead of 191.87 (the network number implied by the class B IP address), and your host number is 22 instead of 34.22. Obtain your subnet mask from your network administrator or Internet access provider. | |
|
Default route |
The dotted-decimal representation of the IP address of the router to which IP packets are sent when there is no route to the destination host or network in your system’s routing table. The default route must have the same network number as your system. For example: If your IP address is 191.87.34.22, and your subnet mask is 255.255.255.0, 191.87.34.15 can be a valid default route, but 191.87.57.15 (on a different subnet) cannot be. Obtain the default route from your network administrator or Internet access provider. | |
|
Use DNS |
The answer to the question, "Does your system have access to the Internet to take advantage of DNS (Domain Name System) to resolve host names to IP addresses?". Ask your network administrator or Internet access provider. If your system does not have access to the Internet, you will not be able to resolve host names after completing the installation until you configure the DNS server or host tables on your system. |
Yes | No |
|
Timezone |
The standard abbreviation for your local timezone (For example: EST, CST, MST, or PST). Enter your local timezone, or, if your system clock is not in the local timezone, enter the timezone your system clock uses. When prompted for your timezone, type a question mark (?) to see a list of valid timezone abbreviations. Switching between Standard Time and Daylight Savings Time occurs automatically. |
Perform the following tasks before installing MultiNet Secure/IP:
• Decide which nodes will act as MultiNet Secure/IP authentication servers and which will be authentication clients. Install the MultiNet Secure/IP Client on every OpenVMS system you want to protect with MultiNet Secure/IP authentication. Your MultiNet Secure/IP license only affects your ability to run MultiNet Secure/IP Server on a single system. You can install MultiNet Secure/IP Client on as many hosts as you like.
Note! The MultiNet Secure/IP Server must have correct name and address mappings (via DNS or host tables) for all MultiNet Secure/IP Clients.
Note! Secure/IP can now be installed as a part of the MultiNet installation if you have one of the following licenses:
– MULTINET
– SECURE_IP
– EDULIB
– EVALUATION
Note! You can install MultiNet Secure/IP on a VMScluster, and configure each node individually to enable the MultiNet Secure/IP Client or the MultiNet Secure/IP Server on selected nodes.
A Kerberos server (KDC) can also be a logical choice for installing the MultiNet Secure/IP Server.
The connection between MultiNet Secure/IP Clients and Servers must be trusted. If physically secure connections are not possible, you can use a Kerberized connection between the MultiNet Secure/IP Clients and Servers. To configure the MultiNet Secure/IP Client and Server to authenticate each other with Kerberos V4, use the ACCESS-CONFIG SET MUTUAL-AUTHENTICATION command (see Chapter 16). By default, mutual authentication is disabled. MultiNet Secure/IP Client systems must have valid Kerberos configurations and KERBEROS.SRVTAB files.
The Release Notes contain important information about this release that may not be published in this guide or in the other publications in the MultiNet documentation set. You can display or print the Release Notes during the installation.
After the installation, you can find the Release Notes in the file SYS$HELP:MULTINET053.RELEASE_NOTES.
The same information is also available on CD-ROM distributions: ([MULTINET053]MULTINET_RELEASE_NOTES.TXT).
Ensure your system is running VAX/VMS V5.5-2 or later, OpenVMS VAX V6.1 or later, OpenVMS Alpha V6.2 or later, or OpenVMS I64 V8.2 or later. If you are not running one of these operating system versions, you must upgrade before installing MultiNet.
If you are upgrading from an earlier release of MultiNet, ensure the existing version of MultiNet is V3.1 or later; you cannot upgrade MultiNet directly from V3.0 or earlier versions.
To check your current MultiNet version:
$ TYPE MULTINET:MULTINET_VERSION.
If you are running a version of MultiNet earlier than V3.1, refer to your old MultiNet for OpenVMS Installation and Administrator’s Guides for instructions on removing MultiNet from your system. Then, install this release of MultiNet as a new installation, not an upgrade.
Ensure you have the proper distribution medium: MultiNet is distributed on two CD-ROMs: one that contains the distribution for VAX and Alpha, and one that contains the distribution for I64.
All magnetic tape media contain only the OpenVMS/VAX savesets.
Note! If you have already installed on another VMScluster node of the same architecture, you do not need to install from the distribution medium again.
Make a backup copy of your system disk using the OpenVMS BACKUP (or standalone BACKUP) utility.
If you are installing MultiNet for the first time, ensure you have sufficient disk space.
To find out how much free space is available on your system disk, use the following DCL command:
$ SHOW DEVICE SYS$SYSDEVICE
The information displayed includes the number of free blocks on the disk. The disk space requirements for VAX, Alpha and I64 versions of MultiNet have been moved to the MultiNet V5.3 Release Notes.
The installation procedure copies files onto the system disk (or another disk you specify). You must be logged in as user name SYSTEM (or as another fully privileged user) to perform the installation.
Make sure other users log off the system before you start the installation or before you modify any system parameters. You may need to reboot.
Before installing MultiNet, you may need to update various system parameters.
Note! With the exception of upgrades to Secure/IP, if an earlier release of MultiNet is installed on your system, you do not need to adjust any system parameters. [ If you are using host tables instead of DNS, to ensure they load properly, check the size of the NETWORK_DATABASE. and HOSTTBLUK.DAT files, and increase the ADD_GBLPAGES statement value by 1 for each disk block used by these files, and increase the ADD_GBLSECTIONS value by 2, one for each file.]
1 If you are installing MultiNet on your system for the first time, modify SYS$SYSTEM:MODPARAMS.DAT as follows:
• On VAX systems, add the following lines to SYS$SYSTEM:MODPARAMS.DAT:
MIN_INTSTKPAGES = 10
MIN_CHANNELCNT = 200
ADD_SPTREQ = 1700
ADD_GBLSECTIONS = 20
ADD_GBLPAGES = 340
• On OpenVMS Alpha systems, add the following lines to SYS$SYSTEM:MODPARAMS.DAT:
MIN_CHANNELCNT = 200
ADD_GBLSECTIONS = 20
ADD_GBLPAGES = 1550
• On OpenVMS on Integrity systems, add the following lines to SYS$SYSTEM:MODPARAMS.DAT:
MIN_GH_EXEC_DATA = 1496
MIN_GH_EXEC_CODE = 4183
2 Execute SYS$UPDATE:AUTOGEN.COM to generate a new system parameter file, and reboot your system to activate the new values. Refer to your OpenVMS system management documentation for information about AUTOGEN.
3 If you are going to upgrade MultiNet Secure/IP during the installation, disable LOGINOUT callouts with the following commands:
$ MCR SYSMAN
SYSMAN>SET ENVIRONMENT /CLUSTER
SYSMAN>SET PROFILE /PRIVILEGE-CMKRNL
SYSMAN>PARAMETER USE ACTIVE
SYSMAN>PARAMETER SET LGI_CALLOUTS 0
SYSMAN>PARAMETER WRITE ACTIVE
SYSMAN>EXIT
Before installing MultiNet, ensure the DCLTABLES.EXE file to which you want the MULTINET verb added resides in the SYS$COMMON:[SYSLIB] directory. VMSINSTAL requires you to do this because it will not update copies of DCLTABLES.EXE in a system-specific directory.
Unless you specify otherwise, the MultiNet installation procedure creates a top-level [MULTINET] directory on your system disk to hold all the MultiNet files. Depending on the platform on which you are installing, a [.AXP_COMMON], [.VAX_COMMON] or [I64_COMMON] subdirectory is created in the [MULTINET] directory. As MultiNet is installed on each node, a node- or system-specific directory is also created in the [MULTINET] directory. System-specific MultiNet files are stored in the node-specific directories, and architecture-common files are stored in either the [.AXP_COMMON], [.VAX_COMMON] or [.I64_COMMON] subdirectory.
Note! If you are upgrading from MultiNet V4.0 or earlier, you can choose to upgrade in the old location, or install in a new location.
If you are upgrading an existing directory structure, that structure is retained.
While each of [MULTINET.AXP_COMMON], [MULTINET.VAX_COMMON] and [MULTINET.I64_COMMON can exist in a multi-architecture cluster in the same directory structure, common configuration files will only be shared by similar architecture nodes.
Unless you specify otherwise, the system-specific directory name is determined by the first of the following values that exist:
• The SYSGEN parameter SCSNODE
• The logical name SYS$NODE
• The logical name SYS$TOPSYS
The system-specific directory is created in the [MULTINET] top-level directory.
Two directories are created under each system-specific directory (as shown in Figure 1-1):
|
MULTINET.DIR |
Contains node-specific files. |
|
SYSCOMMON.DIR |
A file entry that points to the architecture-specific common directory. (Subsequent node-specific directories are created similarly.) |
MultiNet relies on the logical name MULTINET_COMMON_ROOT to locate shared files, and on the logical name MULTINET_ROOT to locate system-specific files. MULTINET_ROOT is a search list of the system-specific directory and the MULTINET_COMMON_ROOT directory. The MultiNet startup command procedure, START_MULTINET.COM, automatically defines these logical names.
Figure 1-1
The MultiNet Directory Structure
[MULTINET]
[.AXP_COMMON] <--+
[.MULTINET] |
[.SEUSS] |
[.MULTINET] |
[.SYSCOMMON] ----+ This is a pointer to [MULTINET.AXP_COMMON]
[.TOMMY] |
[.MULTINET] |
[.SYSCOMMON] --+ This is also a pointer to [MULTINET.AXP_COMMON]
[.I64_COMMON] <--+
[.MULTINET] |
[.JLS] |
[.MULTINET] |
[.SYSCOMMON] ---+ This is a pointer to [MULTINET.I64_COMMON]
[.VAX_COMMON] <--+
[.MULTINET] |
[.ZANE] |
[.MULTINET] |
[.SYSCOMMON] ---+ This is a pointer to [MULTINET.VAX_COMMON]
In MultiNet version 4.0 and earlier, you needed a Product Authorization Key (PAK) for individual components. Starting with Version 4.1, there is only one PAK. You must register and load the PAK if:
• This is the first time you have installed MultiNet on your system.
• The VERSION field in your existing PAK is not blank. If your existing PAK is from Process Software, the VERSION field will always be blank. If your existing PAK is from TGV or Cisco, the VERSION field may show 0.0, which is equivalent to a blank field. If your existing PAK is dated before February 29, 1996, and you want to upgrade to MultiNet v4.1 or higher, you must call your Process Software Account Representative for a new PAK.
For more information about PAKs, refer to the Hewlett-Packard VMS License Management Utility Manual. See the section Step 13: Load the PAK (Product Authorization Key) for an example of registering and loading a PAK.
In some situations you need to delete existing PAKs. You need to delete the PAKs if:.
• You are upgrading from a MultiNet Version 3.5 or earlier to V5.3.
• Need to register a new PAK.
You do not need to delete the PAK if you are upgrading from Version 4.1 to Version 5.3.
To delete any existing PAKs:
$ @MULTINET:PAK-DELETE
Note! Delete only PAKs for versions issued by TGV or Cisco, or for Version 3.5 issued by Process Software.
To register your new PAK:
1 Start the VMSLICENSE utility with the command:
$ @SYS$UPDATE:VMSLICENSE
2 Delete any existing PAKs, if you need to do so. See the section Step 13: Load the PAK (Product Authorization Key) for guidelines about deleting PAKs.
If you are upgrading from a previous version of MultiNet, be sure to complete the upgrade before you reboot your system.
Note! The LMF AMEND option does not work properly and should not be used to alter the state of the MultiNet PAK.
3 Register your new PAK. Answer YES when prompted whether you want it loaded.
4 Exit the VMSLICENSE utility when you have registered your new PAK.
Before beginning the installation, gather the information described in the section Step 1: Gather Information for the Installation
When you install the MultiNet Consolidated Distribution, you have the option of installing all included components.
If you are adding a software component, such as MultiNet Secure/IP, to a system already running MultiNet, you must also re-install any software components that were already installed.
If you are upgrading from a previous version of MultiNet and plan to add a software component already running, such as Secure/IP, then you must also re-install that component.
Note! If you are installing MultiNet on one node in a homogeneous VMScluster environment, and have already installed MultiNet on another node of the same architecture, you do not need to run VMSINSTAL; all required files are already in place.
In this procedure, default values appear in square brackets ([default]). To accept the default value, press RETURN. To abort the installation at any time, press Ctrl/Y.
1 Load your distribution media.
2 Start the VMSINSTAL utility:
$ @SYS$UPDATE:VMSINSTAL product -
_$ loc [OPTIONS N,AWD=device:[directory]]
product is the name of the MultiNet product:
• For VAX and Alpha, the name is MULTINET053.
• For I64, the name is MULTINET_I64053
loc is the device/directory where the installation kit is stored. If you are installing MultiNet from:
• CD-ROM, then mount the CD and specify the full path name of the installation save set directory (such as DKB0:[MULTINET053]).
• Your login directory, use the logical name SYS$LOGIN:.
• TK50 tape, specify the tape device name (for example, MUA0:).
Use the OPTIONS N parameters if you want to be prompted to view or print the Release Notes.
Use the OPTIONS AWD parameters if there is insufficient space on your system disk to accommodate the temporary files created during installation. See the Hewlett-Packard VMS System Manager's Manual for more details about AWD.
Messages similar to the following will appear. The exact wording depends on your system's operating system and architecture:
OpenVMS AXP Software Product Installation Procedure V8.2
It is 08-MAY-2005 at 11:10.
Enter a question mark (?) at any time for help.
3 Ensure your system is in the proper state. If you are not logged in as SYSTEM (or as another fully privileged user), or if any user processes are still running, you are alerted before being asked if you want to continue.
Note! Do not continue the installation until you are logged in using a fully-privileged user name such as SYSTEM, and all other users have logged off. You do not, however, need to disable DECnet to install MultiNet.
Any such messages are followed by the prompt:
* Do you want to continue anyway [NO]?
When you are ready, enter YES. If you enter NO, VMSINSTAL stops and control returns to DCL.
4 Make sure you have a reliable copy of your system disk. The installation copies files onto your system disk. The following prompt appears:
* Are you satisfied with the backup of your system disk [YES]?
If your system disk has not been backed up and you would like to back it up now, enter NO. The installation procedure terminates and the DCL prompt appears. After you have made a backup copy of your system disk, restart the installation procedure.
If your system disk is already backed-up, press RETURN or enter YES.
5 Indicate whether the media is ready, if necessary.
If you are installing from CD-ROM, the installation begins immediately. If you are installing MultiNet from a TK50 cartridge, you are prompted to load the first volume.
Load the distribution media into the drive, and enter YES when you are ready to continue. The following message appears:
%MOUNT-I-MOUNTED, MLTNET mounted on _location:
VMSINSTAL then begins the MultiNet installation.
6 Process the Consolidated Release Notes, if necessary. If you specified the parameters OPTIONS N when you started VMSINSTAL in Step 2, you are asked if you want to print or display the Release Notes. Respond as desired. For an example of printing the Release Notes, see the section Step 3: Read the Release Notes "Sample Installation Dialog".
7 Read the Terms and Conditions displayed in the MultiNet Restricted Rights notice.
8 Ensure proper specification of the MultiNet directory structure. If you are upgrading a running version of MultiNet, the logical names MULTINET_ROOT and MULTINET_COMMON_ROOT will be displayed for verification. If you are upgrading from a version of MultiNet prior to V4.0, the display will have the following form:
The logicals MULTINET_ROOT and MULTINET_COMMON_ROOT are already defined, with the following values:
disk:[SYSn.][MULTINET]
disk:[SYSn.SYSCOMMON.][MULTINET]
If you are upgrading MultiNet V4.0 or later, the display may be of this form:
The logicals MULTINET_ROOT and MULTINET_COMMON_ROOT are already defined, with the following values:
disk:[MULTINET.nodename.][MULTINET]
disk:[MULTINET.nodename.SYSCOMMON][MULTINET]
You are then asked whether you want to upgrade:
You may either upgrade the version of MultiNet installed in this location, or install a fresh copy of MultiNet in another location.
* Do you want to upgrade your MultiNet installation [YES] ?
If you reply NO, or if this is a new installation, you are prompted for an installation location and a name for the system-specific directory:
* Where do you want to install MultiNet [SYS$SYSDEVICE:[MULTINET]]:
* What do you want to call the system-specific directory [AXP01]:
CAUTION! If you respond NO in Step 8, and install MultiNet in a new location, your new installation will not contain any of your original MultiNet configuration files.
Several lines of copyright notices appear, then you are prompted for each component installation.
9 Specify the software components you want to install.
Note! If you plan to run MultiNet or MultiNet Secure/IP on any nodes in your VMScluster environment, be sure to install these software components now. Instructions for installing MultiNet Secure/IP begin at the next section.
Enter YES for each software component you want to install, and NO for each one you do not want on your system (previously installed components will be removed). Include all MultiNet products you want to run on any node in your VMScluster environment.
Note! You must install all software components you want to use, even if they are already installed. For example, if you are already running MultiNet TCP/IP applications, and want to install MultiNet Secure/IP, you must install both MultiNet Secure/IP and the TCP/IP applications.
10 Verify your selections. VMSINSTAL next lists the components to be installed and the software components, if any, to be removed from your system during installation. You are asked if you want to revise the list of software components to be installed or removed:
* Would you like to change your selections [NO]?
To change the list of software components to install, enter YES, and repeat Step 9. To accept the list, enter NO.
11 Decide whether to install user commands:
* Do you want to install the user commands in DCLTABLES [YES]?
This prompt lets you choose whether or not to install additional MultiNet DCL commands in the DCLTABLES.EXE file. Doing this allows you to issue the following commands without the "MULTINET" prefix:
If you are installing MultiNet for evaluation, or if you have commands with these same names from another vendor, enter NO. You can still access the MultiNet utilities by preceding the command with the keyword MULTINET, or by creating symbols such as:
$ TELNET :== MULTINET TELNET
Otherwise, enter YES to install the user commands in the DCLTABLES.EXE file.
Note! You can install the MultiNet user commands in the DCLTABLES.EXE file after completing the installation.
If you have not installed your MultiNet license PAK, you are warned that you do not have the required license. You can still continue to install MultiNet. To continue the process, enter YES at the following prompt:
* Do you want to continue the installation anyway [NO]?
You must register the PAK before you can start and use MultiNet. When you finish the installation and configuration, run VMSLICENSE to register the PAK as shown in the section Load the PAK.
12 Decide whether to purge files:
* Do you want to purge files replaced by this installation [YES]?
If you want VMSINSTAL to purge files replaced by this version of the software, press RETURN or enter YES. If you do not want the replaced files to be purged, enter NO.
Note! Even if you choose to purge files, the installation procedure does not purge configuration files.
CAUTION! If you upgrade MultiNet in a VMScluster environment, do not purge the old files during installation. Instead, wait until you have rebooted each node in the cluster.
13 Decide whether to configure software components. If you are installing the TCP/IP applications, you are asked if you want to configure those software components after installation. Enter YES if you are installing MultiNet for the first time, or if you need to reconfigure.
The installation continues with no additional prompts.
If this is the first time you have installed MultiNet, the installation procedure creates the MultiNet directories and copies the files from the distribution kit into those directories.
VMSINSTAL also optionally installs the MultiNet user commands in SYS$LIBRARY:DCLTABLES.EXE. The MULTINET verb is always installed in your DCLTABLES.EXE file.
If you have previously installed MultiNet on your system, the installation procedure deletes old copies of files replaced during this installation. A series of %VMSINSTAL-I- and %MULTINET-I- informational messages appear during these operations to indicate which files are being installed, merged, or removed, and the save sets from which they came.
If you chose to configure the TCP/IP applications, respond to the prompts with the information you gathered in the section Step 1: Gather Information for the Installation.
The configuration procedure then compiles the ASCII network, host, and service configuration files into binary format and creates or updates various configuration files. As it performs these operations, it prints a number of informational messages.
Upon completion, the installation procedure print messages similar to the following (the messages may vary with the operating system version running on your system):
Installation of MULTINET V5.3 completed at 12:15
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
Creating installation data file: VMI$ROOT:[SYSUPD]MULTINET053.VMI_DATA
VMSINSTAL procedure done at 12:15
$
When you upgrade from an earlier version of MultiNet, all existing configuration settings are preserved unless you intentionally change them during installation.
If you are installing MultiNet for the first time, however, you have the opportunity during installation to configure the MultiNet IP transport over one standard network interface simply by responding to a series of prompts.
If you have already installed MultiNet on one VMScluster node and are now installing MultiNet on another VMScluster node of the same architecture and operating system, or if you chose not to configure MultiNet during the installation, you can configure the MultiNet IP transport over the standard interface using the CONFIGURE.COM command procedure. Gather the required configuration information before configuring. See the section Step 1: Gather Information for the Installation.
CAUTION! If your system does not have one of the standard network interfaces, do not use CONFIGURE.COM to establish connectivity. If you do not use the command procedure, you will need to manually enter configuration information. For details on establishing connectivity with all supported network interfaces, refer to the MultiNet for OpenVMS Installation and Administrator's Guide.
Follow these steps to configure the MultiNet IP transport over the standard network interface:
1 Set your default directory to the architecture-specific common directory, device:[MULTINET.arch_COMMON.MULTINET], device is the device you chose in Step 8 of the installation procedure, and arch is the architecture (either VAX or AXP).
2 The MultiNet configuration command procedure CONFIGURE.COM provides a default location for the new node-specific directories and prompts you for correction. It will create the new directories and logical names to get your system up and running on the local subnet by prompting you for the information in your configuration checklist (see the section Step 1: Gather Information for the Installation). To run the command procedure, type:
If this is the first time you are installing MultiNet Secure/IP, follow Table 1-3
Table 1-3 After Installing MultiNet Secure/IP (Continued)
|
Task |
See the Section... |
|
To use the Security Dynamics method | |
|
To configure your network firewalls | |
|
To unpack the S/KEY clients for PC and Mac users |
Note! If you are upgrading MultiNet Secure/IP from an earlier release, your configuration is preserved. If you are installing for the first time, you must configure MultiNet Secure/IP as described in Chapter 12.
If you are using the Security Dynamics method:
1 Copy the file /var/ace/sdconf.rec from the ACE/Server to the MULTINET: directory (MULTINET_COMMON_ROOT:[MULTINET] on a VMScluster).
2 Verify that the Security Dynamics sdconf.rec file contains meaningful data with the SECURID_CLIENT_CHECK program, as shown in the following example:
$ DIR /SECURITY MULTINET:SDCONF.REC
Directory MULTINET_ROOT:[MULTINET] SDCONF.REC;1 [1,4] RWED,RWED,,)
Total of 1 file.
$ RUN MULTINET:SECURID_CLIENT_CHECK
read configuration file function configuration file is version 1
The configuration structure is 356 bytes long
The ACE/Server limits are:
Client retry is 5 times and the Client timeout is 3 seconds
There is a master and a slave configured
DES has been enabled with sdconfig
Duress mode has been disabled by sdconfig
Addresses are resolved by name service
Number of bad Cardcodes is 3
Number of bad PINS is 3
master = mel-brooks
The address of the master ACE/Server is 161.44.224.66
slave = hq
The address of the slave ACE/Server is 161.44.224.70
sdpropd_port is 5510
The service name is securid
acmprotocol = udp
acm_port is 2200
When a network has a gateway system that controls all incoming access, that gateway is known as a firewall. To allow MultiNet Secure/IP to authenticate users, firewalls must accept incoming TELNET access and silently connect authorized users with RLOGIN to their actual login. The MULTINET_ROOT:[MULTINET.EXAMPLES]CAPTIVE-LOGIN.COM file is an example of a command procedure that provides a captive RLOGIN service for those using TELNET to access a host from over the network. This command procedure can also be used to remind users not to enter their passwords over any unprotected communication channel from which their TELNET session originates.
When you use this command procedure, RLOGIN must be enabled on the local hosts to which users will connect.
To use CAPTIVE-LOGIN.COM:
1 Create accounts on the firewall for all MultiNet Secure/IP users.
2 Use OpenVMS AUTHORIZE to ensure this procedure is invoked when users log in.
3 Copy the command procedure from the EXAMPLES directory to the SYS$MANAGER: directory.
The following example demonstrates these steps:
$ SET PROC/PRIV=SYSPRV
$ SET DEF SYS$SYSTEM
$ RUN AUTHORIZE
UAF>ADD FRED/LGICMD=SYS$MANAGER:INTERNET-LOGIN.COM/FLAG=(CAPTIVE) -
_UAF>/DIR=[FRED]/UIC=[123,123]
%UAF-I-ADDMSG, user record successfully added
%UAF-I-RDBADDMSGU, identifier FRED value [000123,000123] added to rights database
UAF>EXIT
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-NAFNOMODS, no modifications made to network proxy database
%UAF-I-RDBDONEMSG, rights database modified
$ COPY MULTINET_ROOT:[MULTINET.EXAMPLES]CAPTIVE-LOGIN.COM -
_$ SYS$MANAGER:INTERNET-LOGIN.COM
$ SET FILE/OWNER=[1,4]/PROTECTION=(S:RWED,O:RWED,G:RE,W:RE) -
_$ SYS$MANAGER:INTERNET-LOGIN.COM
If you use the S/KEY method, Apple Macintosh and PC client programs are provided in the MULTINET_COMMON_ROOT:[EXAMPLES] directory. The MACOPIE.HQX file in this directory contains the Macintosh client, which can be unpacked with Stuffit. The SKEY-DOS.BCK file contains the PC client, which can be unpacked with the OpenVMS BACKUP utility.
You can also download the Macintosh and PC client programs over the Internet from thumper.bellcore.com by anonymous FTP to the /pub/skey directory. MacOpie is also available from the Info-Mac archives and its associated mirrors.
Note! MacOpie uses the MD5 Message Digest algorithm by default. To use MacOpie with MultiNet Secure/IP, the MD4 Message Digest must be selected under the References menu section.
If you installed MultiNet on a system already running MultiNet, perform these four steps after completing the installation to ensure its success; MultiNet then starts automatically:
1 Recompile the host lookup table: [ Recompiling the host lookup table is only necessary on the first node of a given architecture in a VMScluster environment.]
$ MULTINET HOST_TABLE COMPILE
2 Reboot your system to load the new kernel.
3 Run the MultiNet CheckOut Utility.
$ MULTINET CHECK
4 Rectify any problems found.
If you have successfully installed and configured MultiNet for the first time on your system, as described in the previous sections, you are ready to start MultiNet. You do not have to reboot if your system has never run any TCP/IP stack; however, you may need to reboot after running AUTOGEN to activate any system parameter changes you made.
Successful configuration of MultiNet defines the logical name MULTINET and creates the file MULTINET:START_MULTINET.COM. However, if you have rebooted, the MULTINET logical may not be defined. Ensure the logical name is defined. Enter:
$ SHOW LOGICAL MULTINET
Also ensure the file exists. Enter:
$ DIRECTORY MULTINET:START_MULTINET.COM
If the logical name and the file are not present, check for installation errors and configuration problems, and correct them before proceeding. If they are not present because you rebooted, then add the following line to your system startup command procedure:
$ @SYS$SYSDEVICE:[MULTINET.HYDRA.MULTINET]START_MULTINET
To locate the startup command procedure, enter the following:
$ DIR SYS$SYSDEVICE:[000000...]START_MULTINET.COM
Directory SYS$SYSDEVICE:MULTINET.HYDRA.MULTINET]
START_MULTINET.COM;1
Use the following commands to start MultiNet:
$ REPLY/ENABLE=NETWORK/TEMPORARY
$ @MULTINET:START_MULTINET
You may use the MULTINET logical name here, as it is defined by the configuration procedures. Be sure your system startup command procedure refers to the disk and directory where you installed MultiNet.
Note! Regardless of where you installed MultiNet, you do not have to define the MULTINET logical name — this is done automatically in the first lines of the START_MULTINET.COM command procedure.
If you are upgrading from MultiNet V3.n to V5.3, but want to retain the old directory structure — or you are upgrading a MultiNet V4.n system that is already using the new directory structure introduced with MultiNet V4.0 Rev A — you do not need to make any changes to your system startup command procedure.
If you are upgrading from MultiNet V3.n to V5.3, and chose to adopt the new directory structure, modify the existing START_MULTINET.COM call in your system startup command procedure. Edit the procedure as follows:
$ @device:[directory.nodename.MULTINET]START_MULTINET.COM
device, directory, and nodename correspond to those you chose in Step 8 of the installation procedure.
If you are installing MultiNet for the first time, add the following line to your system startup command procedure:
$ @device:[directory.nodename.MULTINET]START_MULTINET.COM
device, directory, and nodename correspond to those you chose in Step 8 of the installation procedure. [ If the name of your system is HOBBES, and you chose the default values for your V4.0 directory structure, the startup command will read
$ @SYS$SYSDEVICE:[MULTINET.HOBBES.MULTINET]START_MULTINET.COM]
Note! The START_MULTINET.COM file will not exist until you configure MultiNet
If you are also running DECnet, ensure the call to the MultiNet startup procedure is placed after the call to SYS$MANAGER:STARTNET.COM.
Once you have established IP, you can configure services and other components. Table 1-4 indicates where to locate documentation on configuring standard services and the optional components you can install.
Note! Additional information about these services may be found in the Release Notes.
Table 1-4 Where to Find Information about Configuring Services (Continued)
|
To configure this service... |
See this MultiNet publication |
|
GATED (IP Routing) |
Installation and Administrator's Guide |
|
DNS (Domain Name System) |
Installation and Administrator's Guide |
|
DHCP (Dynamic Host Configuration Protocol) |
Installation and Administrator’s Guide |
|
NTP (Network Time Protocol) |
Installation and Administrator's Guide |
|
SMTP (Simple Mail Transfer Protocol) |
Installation and Administrator's Guide |
|
LPD (Line Printer Daemon) printing services |
Installation and Administrator's Guide |
|
RMT (Remote Tape) Services |
Installation and Administrator's Guide |
|
FTP (File Transfer Protocol) Server |
Installation and Administrator's Guide |
|
XDM (X Display Manager) |
Installation and Administrator's Guide |
|
Font Server |
Installation and Administrator's Guide |
|
SNMP (Simple Network Management Protocol) |
Installation and Administrator's Guide |
|
Kerberos Authentication |
Installation and Administrator's Guide |
|
NFS (Network File System) Client |
Installation and Administrator's Guide |
|
NFS (Network File System) Server |
Installation and Administrator's Guide |
|
X11 Gateway |
Installation and Administrator's Guide |
|
DECnet-over-IP |
Installation and Administrator's Guide |
|
MultiNet Secure/IP |
Installation and Administrator’s Guide |
|
Secure Shell (SSH) ServerSecure Shell (SSH) Client |
Installation and Administrator’s GuideUser’s Guide |
|
TCP/IP Services for DECnet Applications |
Messages, Logicals, and TCP/IP Services for DECnet Applications |
MultiNet allows you to customize some functions through the use of user exits. If you are upgrading MultiNet and have modified any user exits prior to this installation, merge your modifications into the user exits replaced during the installation. For more information about customizing user exits, see the MultiNet for OpenVMS Installation and Administrator’s Guide.
If you did not install the MultiNet user commands in the DCLTABLES.EXE file during installation, you can install them manually with the following commands:
$ SET COMMAND /TABLES=SYS$COMMON:[SYSLIB]DCLTABLES -
_$ /OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES MULTINET:USER.CLD
$ INSTALL REPLACE SYS$COMMON:[SYSLIB]DCLTABLES
The MultiNet documentation set is available on the product CD in PDF and HTML formats.
The MultiNet documentation set has the following PDF files:
|
Installation & Administrator |
MULTINET_ADMIN_GUIDE.PDF |
|
Administrator Reference |
MULTINET_ADMIN_REFERENCE.PDF |
|
Messages, Logicals, & DECnet Apps |
MULTINET_MESSAGES.PDF |
|
Programmer Reference |
MULTINET_PROGRAMMERS_REFERENCE.PDF |
|
User Guide |
MULTINET_USER_GUIDE.PDF |
|
MultiNet Master Index |
MULTINET_MASTER_INDEX.PDF |
The PDF format is readable from a PC, a VAX, Alpha or I64 system. There is a PDF reader on the CD for VAX and AXP platforms.
• Use Acrobat Reader to read the PDF files from a PC. Your PC must have 386 architecture or later to use Acrobat Reader. You can get Acrobat Reader from Adobe Systems website: www.adobe.com. It is free!
• Use the XPDF Reader (found in the [XPDF] directory) to read the PDF files from a VAX or Alpha system. The [XPDF.AXP] directory contains the Alpha architecture reader XPDF.EXE. The [XPDF.VAX] directory contains the VAX architecture reader XPDF.EXE.
Note! The XPDF Reader does not work on a PC.
PCs running the Windows or NT operating system cannot read Process Software's CD. You cannot load files from the MultiNet CD directly to a PC. Load them to your VAX, Alpha or I64 machine, then transfer them to your PC.
We suggest using FTP to transfer these files. The following is an example using MS-DOS:
C:> ftp node
ftp> binary
ftp> mget cd:*.pdf
In addition, Process Software has included LYNX, the character-cell web browser for VMS. It is in the [LYNX] directory.
To read the PDF files using Acrobat Reader:
1 Double click Acrobat Exchange.
2 Choose Open from the File menu.
3 Select the .pdf file you want to open.
4 Use the menu bar at the top of the screen to navigate the document or click a Table of Contents entry (on the left) to go directly to that information.
Note! The binocular icon opens search functions. The magnifying glass icon enlarges the text and illustrations.
Thanks to Derek B. Noonburg for letting us download his XPDF application.
Note! You need a three-button mouse to use XPDF.
At the DCL prompt from the directory in which XPDF.EXE is stored (VAX/Alpha only), do the following:
1 Type RUN XPDF. The XPDF screen appears.
2 Position the arrow on any of the icons (except the ? icon) on the bottom of the screen.
3 Press the right mouse button to display choices.
4 Select OPEN to display the list of PDF files.
5 Select the PDF file you want and click OPEN to read the file.
6 Use the icons on the bottom of the screen to search for the information you want.
To view the online help for XPDF:
1 Position the cursor on the question mark (?) icon.
2 Press the left mouse button to open the online help.
Online documentation is available as HTML files you can use either with a PC browser or with a character cell browser. The documentation files and their contents are listed next.
Table 1-5 MultiNet HTML Documentation Files (Continued)
|
Document |
Directory Title |
HTML File Names |
Contents |
|
Installation and Administrator’s Guide |
ADMINISTRATOR |
CH1.HTM |
Installing and Upgrading MultiNet for OpenVMS |
|
CH2.HTM |
Example Procedures |
||
|
CH3.HTM |
Files that may be Added to your System Disk |
||
|
CH4.HTM |
Removing MultiNet for OpenVMS |
||
|
CH5.HTM |
MultiNet Documentation and Online Help |
||
|
CH6.HTM |
Introduction to MultiNet and TCP/IP Concepts |
||
|
CH7.HTM |
Devices, Protocols, and MultiNet Internals |
||
|
CH8.HTM |
Getting Additional Information |
||
|
CH9.HTM |
Configuration Overview |
||
|
CH10.HTM |
Host Table and DNS |
||
|
CH11.HTM |
Establishing IP Connectivity |
||
|
CH12.HTM |
Configuring MultiNet Services |
||
|
CH13.HTM |
Configuring Network Routing |
||
|
CH14.HTM |
Network Time Protocol (NTP) |
||
|
CH15.HTM |
Configuring Electronic Mail |
||
|
CH16.HTM |
Printer Configuration |
||
|
CH17.HTM |
RMT Server and Client |
||
|
CH18.HTM |
Configuring and Managing FTP |
||
|
CH19.HTM |
DHCP Client |
||
|
CH20.HTM |
Configuring the Font Server |
||
|
CH21.HTM |
Remote Systems with RARP, BOOTP, and DHCP |
||
|
CH22.HTM |
Managing XDM |
||
|
CH23.HTM |
Configuring MultiNet SNMP Agents |
||
|
CH24.HTM |
Configuring MultiNet Kerberos Authentication Service |
||
|
CH25.HTM |
X11-Gateway Configuration |
||
|
CH26.HTM |
Configuring DECnet-over-IP Circuits |
||
|
CH27.HTM |
Configuring the MultiNet NFS Server |
||
|
CH28.HTM |
Using the NFS Client |
||
|
CH29.HTM |
Configuring the Secure Shell (SSH) v1 Server |
||
|
CH30.HTM |
Configuring the Secure Shell (SSH) v2 Server |
||
|
CH31.HTM |
Configuring IPSEC and SETKEY |
||
|
APPA.HTM |
Server Configuration Parameters |
||
|
User's Guide |
USER_GUIDE |
CH1.HTM |
Exploring Your Network Environment |
|
CH2.HTM |
Sending and Receiving Electronic Mail |
||
|
CH3.HTM |
Using Kerberos Authentication |
||
|
CH4.HTM |
Accessing Remote Systems with the RSHELL, RLOGIN, and TELNET Utilities |
||
|
CH5.HTM |
Remote File Access with the RCP, FTP, and TFTP Utilities |
||
|
CH6.HTM |
Using DECwindows with MultiNet |
||
|
CH7.HTM |
Accessing Remote Systems with the Secure Shell (SSH) Utilities |
||
|
CH8.HTM |
Secure File Transfer |
||
|
APPA.HTM |
DCL User Commands |
||
|
APPB.HTM |
FTP Command Reference |
||
|
APPC.HTM |
TELNET Command Reference |
||
|
APPD.HTM |
TFTP Command Reference |
||
|
Administrator'sReference |
ADMIN_REF |
CH1.HTM |
MultiNet DCL Command Reference |
|
CH2.HTM |
MultiNet Secure/IP DCL Commands |
||
|
CH3.HTM |
DECNET-CONFIG Command Reference |
||
|
CH4.HTM |
MAIL-CONFIG Command Reference |
||
|
CH5.HTM |
NET-CONFIG Command Reference |
||
|
CH6.HTM |
NFS-CONFIG Command Reference |
||
|
CH7.HTM |
NTYCP Command Reference |
||
|
CH8.HTM |
ACCESS-CONFIG Command Reference |
||
|
CH9.HTM |
PRINTER-CONFIG Command Reference |
||
|
CH10.HTM |
SERVER-CONFIG Command Reference |
||
|
Programmer’s Reference |
PROGRAMMER |
CH1.HTM |
MultiNet Programming Tutorial |
|
CH2.HTM |
Socket Library Functions |
||
|
CH3.HTM |
QIO Interface |
||
|
CH4.HTM |
SNMP Extensible Agent API Routines |
||
|
CH5.HTM |
RPC Fundamentals |
||
|
CH6.HTM |
Building Distributed Applications with RPC |
||
|
CH7.HTM |
RPCGEN Compiler |
||
|
CH8.HTM |
RPC RTL Management Routines |
||
|
CH9.HTM |
RPC RLT Client Routines |
||
|
CH10.HTM |
RPC RTL Port Mapper Routines |
||
|
CH11.HTM |
RPC RTL Server Routines |
||
|
CH12.HTM |
RPT RTL XDR Routines |
||
|
Messages, Logicals, and DECnet Apps |
MESSAGES |
CH1.HTM |
Troubleshooting |
|
CH2.HTM |
MultiNet Messages |
||
|
CH3.HTM |
MultiNet Logicals |
||
|
CH4.HTM |
Utility Return Codes |
||
|
CH5.HTM |
Error Codes |
||
|
CH6.HTM |
What is DECnet Applications? |
||
|
CH7.HTM |
Configuring DECnet Applications |
||
|
CH8.HTM |
NOT-CONFIG Commands |
