The below table 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 Itanium). The sections in this chapter provide detailed information about each step.
|
Step |
Description |
|
1 |
Gather Information for the Installation |
|
2 |
Read the Release Notes |
|
3 |
Check OpenVMS and MultiNet Versions |
|
4 |
Use the Correct Media |
|
5 |
Back Up Your System Disk |
|
6 |
Reserve Sufficient Disk Space |
|
7 |
Log on as SYSTEM |
|
8 |
Ask Other Users to Log Off |
|
9 |
Update System Parameters |
|
10 |
Check the Location of the DCLTABLES.EXE File |
|
11 |
Review the MultiNet Directory Layout |
|
12 |
Load the PAK |
|
13 |
Run VMSINSTAL |
|
14 |
Establish an Initial Configuration |
|
15 |
Configure IP Transport |
|
16 |
Start the New Version of MultiNet |
|
17 |
Configure Services |
|
18 |
Add and Update User Exits |
|
19 |
Install MultiNet Commands in the DCLTABLES.EXE File |
Configuration procedures allow you to configure IP connectivity using one 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. The below table lists the information you must gather.
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.
|
|
Parameter Name |
Description |
|
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.EXAMPLE.COM). 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 10.1.2.3 is a class B IP address in which 10.1 is the network number and 2.3 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 10.1.2.3, and your subnet mask is 255.255.255.0, your network number is 10.1.2 instead of 2.3 (the network number implied by the class B IP address), and your host number is 3 instead of 2.3. Obtain your subnet mask from your network administrator or Internet service 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 10.1.2.3, and your subnet mask is 255.255.255.0, 10.1.2.126 can be a valid default route, but 10.1.128.126 (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 service 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. |
|
Timezone |
The standard abbreviation for your local time zone (For example: EST, CST, MST, or PST). Enter your local time zone, or, if your system clock is not in the local time zone, enter the time zone your system clock uses. When prompted for your time zone, type a question mark (?) to see a list of valid time zone abbreviations. Switching between Standard Time and Daylight Savings Time occurs automatically. |
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:MULTINET056.RELEASE_NOTES.
The same information is also available from the Process Software web site at www.process.com and on CD-ROM distributions: ([MULTINET056]MULTINET_RELEASE_NOTES.TXT).
Ensure your system is running VAX/VMS V5.5-2 or later, OpenVMS Alpha V6.2 or later, or OpenVMS Itanium 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 V4.3 or later; you cannot upgrade MultiNet directly from V4.2 or earlier versions.
To check your current MultiNet version:
$ TYPE MULTINET:MULTINET_VERSION.
If you are running a version of MultiNet earlier than V4.3, refer to your old MultiNet 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 a CD-ROM that contains the distributions for VAX, Alpha, and Itanium.
|
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 Itanium versions of MultiNet are available in the MultiNet V5.6 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.
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 Itanium 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.
$ 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
|
Note: 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.
|
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.
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:
· 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.
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]
MultiNet is licensed by a single PAK. You must register and load the PAK if this is the first time you’ve installed MultiNet on your system.
For more information about PAKs, refer to the VMS License Management Utility Manual. See Chapter 2 of this manual for an example of registering and loading a PAK.
To register your new PAK:
1. Start the VMSLICENSE utility with the command:
$ @SYS$UPDATE:VMSLICENSE
2. Register your new PAK. Answer YES when prompted whether you want it loaded.
3. Exit the VMSLICENSE utility when you have registered your new PAK.
Before beginning the installation, gather the information described in the section Gathering Information for the Installation.
|
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 MULTINET056. For Itanium, the name is MULTINET_I64056.
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:[MULTINET056]). If you are installing MultiNet from your login directory, use the logical name SYS$LOGIN:.
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 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-2019 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 will abort the installation.
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. 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. 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 Release Notes, if necessary. If you specified the parameter 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 Sample Installation in Chapter 2.
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:
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, 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.
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.
10. Verify your selections. VMSINSTAL 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 Step 1.
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 prints messages similar to the following (the messages may vary with the operating system version running on your system):
Installation of MULTINET V5.6
completed at 12:15
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
Creating installation data file: VMI$ROOT:[SYSUPD]MULTINET056.VMI_DATA
VMSINSTAL procedure done at 12:15
$
MultiNet is now installed.
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. Step 1 describes the information you need to gather.
|
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 appropriate chapter in this document.
|
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, AXP, or Itanium).
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 Step 1 of this installation procedure). To run the command procedure, type:
$ @CONFIGURE
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 CHECK 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.BIGBOOTE.MULTINET]START_MULTINET
To locate the startup command procedure, enter the following:
$ DIR
SYS$SYSDEVICE:[000000...]START_MULTINET.COM
Directory SYS$SYSDEVICE:MULTINET.BIGBOOTE.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.
|
Once you have established IP connectivity, you can configure services and other components. Documentation on configuring standard services are contained in this document.
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 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
You can use the de-installation command procedure to remove MultiNet. The procedure removes all MultiNet files from disk and all MultiNet commands from the DCLTABLES.EXE file. Before executing the procedure:
1. Use the LICENSE DISABLE or DELETE commands, or the VMSLICENSE command procedure to remove any registered MultiNet PAKs (Product Authorization Keys). Refer to the VMS License Management Utility Manual for more information about PAKs.
2. Remove the reference to START_MULTINET.COM from your system startup command procedure.
3. Remove system parameter changes in MODPARAMS.DAT made as part of the installation; invoke the AUTOGEN utility to set the parameters back to their pre-installation values. Refer to the Guide to Maintaining a VMS System for descriptions of MODPARAMS.DAT and AUTOGEN parameters.
4. Reboot your system (or systems, if you installed MultiNet on more than one node in a VMScluster environment).
To execute the MultiNet de-installation procedure, type this command if MultiNet is still running:
$ @MULTINET:REMOVE
Otherwise, type:
$ @device:[directory.node.SYSCOMMON.MULTINET]REMOVE
device, directory, and node are those you specified during Step 8 of the installation procedure.