MultiNet FAQ: Miscellaneous


If a system has two interfaces on it, can I assign an address to both cards so if one card fails the address can still be reached?

Yes, by using MultiNet's paired network interface support and pseudo devices.

If the system is to be accessed via the IP address

  1. Configure the two interfaces to have an IP address in a different subnet than the system's IP address of You can use the private network addresses 192.168.0.X or any other addresses that do not conflict with your site's addressing scheme.
  2. Configure the interface PD-0 to have the 'real' IP address,, and to use one of the real interfaces as its hardware device. Then, if it does not exist,
  3. Create or add to MULTINET:LOCAL_INITIALIZATION.COM an MU SET/INTERFACE/COMMON_LINK command instructing MultiNet that the interfaces are on a common network: MU SET/INTERFACE/COMMON_LINK=SE1 SE0

Here is an example configuration that demonstrates the above:

MultiNet Network Configuration Utility
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]


Interface      Adapter      CSR         Flags/
                           Address      Vector
---------      -------     -------      ------
 se0 	(Shared VMS Ethernet/FDDI)
                -NONE-      -NONE-      -NONE-
[VMS Device: EWA0, Link Level: Ethernet]

 se1	(Shared VMS Ethernet/FDDI)
                -NONE-      -NONE-      -NONE-
[VMS Device: EWB0, Link Level: Ethernet]

 pd0 	(Secondary Ethernet Address)
                -NONE-      -NONE-      -NONE-
[Hardware-Device: se0]


With this configuration if either SE0 or SE1 is brought down with the command MU SET/INTERFACE/DOWN or if a fatal error is detected on either interface, the pseudo device and any routing table entries using that device will failover to the other. Also, when sending a packet if one of the interfaces is busy, the packet will be sent out via the other interface, resulting in better throughput.

Why is the configuration file missing a block?

The configuration file that is being referred to is the SNMP_AGENT.CONFIGURATION file and the error indicates that the format of the file is invalid. The file should be edited and corrected. If you are not using SNMP you can disable it. SNMP is enabled by default. If SNMP is not being used on the system, it can be disabled by issuing the following:

[The Selected SERVER entry is now SNMP]

Is there any way to make the NTY session show up as REMOTE instead of LOCAL?

Yes, a kernel variable needs to be set by the following command:


This command has to be executed each time MultiNet is started. If it exists, MultiNet executes the file MULTINET:LOCAL_INITIALIZATION.COM after starting. You can add the SET/KERNEL command to the file if it already exists, or create the file and add the SET/KERNEL command if the file does not already exist.

Why is the message not transferred to the client when a POP3 user has a large attachment to an email?

To be successfully sent, attachments to email messages cannot be larger than the page file quota set in the user's account. If this has been a problem, just increase the user's PGFLQUOTA appropriately.

Why can I not make an Rshell connection when my .rhost and my host.equiv files seem correct?

There are a number of things that effect a valid connection for the R-services:

  1. Due to security reasons, if the client is accessing the SYSTEM account on the server, the server will not use the HOST.EQUIV file in the MULTINET directory. The entry MUST be in the .rhost file in the SYS$LOGIN directory of the system account.
  2. If you use DNS, make sure that the server and client are both in DNS for forward and reverse lookup. The R-services server need to be able to translate IP address to names and names to IP addresses.
  3. The entry in either the .rhost file and HOST.EQUIV file cannot be ip addresses and must be the fully qualified domain name.
  4. And last but not least, whenever you make any change to either file, flush the table on the server: MU NETCONTROL RSHELL FLUSH. (You can replace RSHELL with RLOGIN or REXEC; it is all the same table.)

Why does the process hang when I try to MOUNT RMTalloc device?

Be sure that SYLOGIN.COM and LOGIN.COM have the following two lines:




If problems still occur, verify in UAF that the account they are logging into on the remote server is not executing some other command procedure at startup. Check LGICMD in UAF. If they are, add the 2 lines to that file also.

Information Needed to analyze a crash

Process Software will need the following information in order to do a speedy crash analysis.

All information on the crash MUST include:

  1. The VMS version and machine architecture (VAX or AXP)
  2. The MultiNet version that was running and any patches that had been applied, especially any driver patches. The dump cannot be analyzed without this information.
  3. Has anything unusual occurred recently or is the crash occurring on installing MultiNet? Unusual events include:
    1. changed hardware configuration on local node or network
    2. changed software configuration including: MultiNet configuration, VMS SYSGEN, and new applications on server or client
    3. an unusual load
  4. Some SDA information could be useful:
    SDA> read/exec (don't need this output)
    SDA> show crash
    SDA> format @r3	(optional)
    SDA> format @r5	(optional)
    	- if this shows up as UCB$... structure, then do
    SDA> show device/address=@r5
    SDA> show stack

This information should be sent to Process Software’s Technical Support Department to expedite the crash analysis. In most cases a valid system dump from the crash will also have to be provided.

Why can't I read directories with TFTP even though they are in the translations file?

Using TFTP TFTP.FILENAME-TRANSLATIONS does not work. The correct translation is in the file but the directories are not being translated.

Make sure the directories in the file are listed from deepest or most specific to least deep or less specific.

For example:


Can I install MultiNet in a cluster with different versions of OpenVMS?

MultiNet must be installed once for each version of OpenVMS. Each of the installs must be done into a new MultiNet root.