4. NET-CONFIG Command Reference

 

 

This chapter describes the commands you can run from the NET-CONFIG command line. NET-CONFIG lets you examine, modify, and save configuration files for MultiNet network interfaces.

To invoke NET-CONFIG:

$ MULTINET CONFIGURE /INTERFACES

At any NET-CONFIG prompt, you can list the available commands by typing ?. Online help for each NET-CONFIG command is available through the NET-CONFIG HELP command.

Of the SET commands, the SET LOAD-EXOS-DRIVER and SET WINS-COMPATIBILITY commands require that you reboot the system after you use the command; all other SET commands can be executed without rebooting the system.

For details on configuring network interfaces, refer to the MultiNet Installation and Administrator’s Guide.

NET-CONFIG Command Summary

The below table lists the commands you can run from the NET-CONFIG prompt.

NET-CONFIG Command

Description

ADD

Adds a device to the network configuration.

ATTACH

Attaches a terminal to a process.

CHECK

Performs a check on the current configuration.

CLEAR

Deletes all devices from the network configuration.

CREATE

Create a Six-To-Four interface to carry IPv6 traffic over IPv4.

DELETE

Deletes a single device from the network configuration.

DISABLE

Disables a device and deletes it from the configuration.

ENABLE

Enables a device.

ERASE

Deletes all devices from the network configuration.

EXIT

Exits NET-CONFIG and saves the configuration if it changed.

GET

Reads in a nonstandard configuration file.

HELP

Displays command help information.

MODIFY

Changes a device configuration.

PUSH

Accesses the DCL command interpreter.

QUIT

Exits NET-CONFIG and prompts to save the configuration if it changed.

SAVE

Writes configuration parameters to a file.

SET ANONYMOUS-FTP-ACCESS

Restricts anonymous FTP access.

SET ANONYMOUS-FTP-DIRECTORY

Restricts anonymous FTP directory access.

SET CLUSTER-SERVICE-ADDRESS

Identifies the IP address to use when responding to address queries from hosts specified by CLUSTER-SERVICE-NAMES.

SET CLUSTER-SERVICE-NAMES

Lists the host names to use for load balancing.

SET DEFAULT-RMT-TAPE-DEVICE

Defines the default RMT server tape device.

SET DEFAULT-ROUTE

Defines the default IP route.

SET DOMAIN-NAMESERVERS

Configures the DNS domain resolver.

SET HOST-NAME

Defines the local host name and domain.

SET IP-CLUSTER-ALIASES

Specifies a list of cluster-wide Internet addresses to which this node responds.

SET LOAD-EXOS-DRIVER

Enables automatic loading of the Novell EXOS-compatible $QIO driver when MultiNet starts.

SET LOAD-PWIP-DRIVER

Enables automatic loading of the version 5 PATHWORKS server interface (PWIP) driver when MultiNet starts

SET LOCAL-DOMAIN

Overrides the default local domain derived from previous use of the SET HOST-NAME command.

SET LPD-DEFAULT-USERNAME

Specifies a default user name for print jobs received from a remote machine via the LPD protocol.

SET NAMESERVER-RETRANSMISSION

Specifies a time between and the number of name server requests that are made before the system stops sending name server requests to a nonresponding server.

SET SPOOL-DIRECTORY

Sets the default spool directory name.

SET TFTP-DIRECTORY

Sets the default directory for the TFTP server.

SET TIMEZONE

Sets the local time zone.

SET TIMEZONE-RULES

Specifies the time zone rules file name.

SET WHOIS-DEFAULT-SERVER

Sets the default WHOIS server.

SET WINS-COMPATIBILITY

Defines the logical names used with the WIN/TCP and Pathway products from The Wollongong Group.

SHOW

Displays the current configuration or device names.

SPAWN

Executes a DCL command.

STATUS

Displays the device count in the configuration.

USE

Reads in a nonstandard configuration file.

VERSION

Displays the NET-CONFIG and VMS versions.

WRITE

Writes the current configuration.

 

 

 

 

 

 

 


 

ADD

Adds a device to the network configuration.

 

FORMAT

ADD interface

 

PARAMETERS

interface

Specifies the name of the device interface to add.

Refer to the below table for a list of supported network interfaces and the corresponding interface parameters for which you are prompted. For descriptions of interface parameters, refer to the following table.

Type

Description

nsip

Interface name: nsip0, nsip1, ... nsip9
Device type: IPX-over-IP tunnel

 

Parameter Prompt

Example Value

IP address of remote system:

10.1.10.70

 

The nsip interface provides access to IPX-over-IP for connecting to Novell's IP tunnel feature.

pd

Interface name: pd0
Device type: Secondary Ethernet Address

 

Parameter Prompt

Example Value

TCP/IP

10.1.128.21

Hardware-Device

se0

IP SubNet Mask

None

Non-Standard IP Broadcast Address

None

pd0 (Secondary Ethernet Address)

Csr=None, Flags=%X0

IPv6 on this interface [DISABLED]

ENABLE

IPv6 global address [NONE]

fe80:0db8:ac10:fe01

IPv6 mask length

16

 

Careless assignment of a secondary address can cause network problems. In general, you should assign pseudo devices (pd) addresses on the same network or subnet as the se device to which the pd device is linked.

 

If the pd interface is not in the same IP network as its associated se interface, some TCP/IP packages retransmit broadcast packets for the other IP network back to the network segment from which they were transmitted. This can cause network storms.

 

 

Note: GateD will listen to traffic on pseudo devices in MultiNet. Some services listen to traffic on se interfaces only and ignore traffic on pd interfaces. One such service is the RIP listener in GATED.

 

ppp

Interface name: ppp0, ...
Device type: Any supported PPP terminal interface

 

Parameter Prompt                                                    Example Value

VMS Device:                                                               TTA0:
Baud Rate:                                                                    19200
PPP ACCM Mask:                                                        0
PPP Authentication Method:                                        None
PPP Protocol Compression:                                          OFF
PPP Address and Control Field Compression:             OFF
PPP Retry Count:                                                          0
PPP Idle Timeout:                                                         0
PPP MRU Size:                                                             0
PPP ICMP:                                                                    ENABLED
PPP TCP Compression:                                                OFF
PPP Termination Retry Count:                                     0
PPP Timeout:                                                                0
IP Address:                                                                    0.0.0.0
Point-to-Point Device IP Destination Address:            0.0.0.0
IP Subnet Mask:                                                            255.0.0.0

rp

Interface name: rp0, rp1, rp2, ...
Device type: Raw packet

 

Parameter Prompt             Example Value

IP Address:                              10.41.228.70
IP SubNet Mask:                     255.255.255.0

The rp interface allows IP packets that are normally destined for transmission to be directed instead to a user process by way of an AF_RAWPACKET socket.

se

Interface name: se0, se1, se2, ...
Device type: Any HP VMS Ethernet, FDDI, or Token-Ring Alpha controller

 

Parameter Prompt                                   Example Value

VMS Device:                                             XEA0
Link Level Encapsulation Mode:              ETHERNET
BSD Trailer Encapsulation:                      DISABLED
IP Address:                                                  10.41.228.70
IP SubNet Mask:                                         255.255.255.0
Non-Standard IP Broadcast Address:         10.41.228.71
DHCP CLIENT [DISABLED]:                  DISABLED
Jumbo Frames [DISABLED]:                    ENABLED
IPv6 on this interface [DISABLED]:         ENABLED
IPv6 global address [NONE]:                    3FFE:1200:3006::C673:8EBE
IPv6 mask length:                                      48

The se interface uses any Ethernet controller to provide access to a 10/100/1000 Mb/s Ethernet network, any FDDI controller to provide access to a 100 Mb/s FDDI network, and a Token-Ring controller to provide access to a 4 Mb/s or 16 Mb/s Token-Ring.

 

The se interface uses the standard VMS Ethernet driver to allow MultiNet to share the Ethernet devices with other protocols such as LAT, LAVC, and DECnet.

sl

Interface name: sl0, sl1, sl2, ...
Device type: Any VMS-supported terminal interface

 

Parameter Prompt                                                      Example Value

VMS Device:                                                                TTA0
Baud Rate:                                                                    19200
Header Compression Mode:                                         DISABLED
IP Address:                                                                   10.41.228.70
Point-To-Point Device IP Destination Address:          10.41.228.71
IP SubNet Mask:                                                          255.255.255.0

The MultiNet software supports SLIP with Van Jacobson's header compression algorithm, reducing the size of the headers and increases the bandwidth available to data. Header compression mode is determined by what both sides can support.

 

 

NET-CONFIG Prompts

Function

ACCM Mask

Asynchronous Control Character Map Mask. A 32-bit mask that indicates the set of ASCII control characters to be mapped into two-character sequences for transparent transmission over the line. The default is %x00000000.

Address and Control Field Compression (ACFC)

When ON, PPP eliminates the address and control fields when they are identical over a series of frames. The default is OFF.

Authentication Method

Determines the type of remote peer authentication required to allow network- layer protocol packets to be exchanged. Accepted values are PAP (Password Authentication Protocol) and NONE (the default).

Baud Rate

Indicates the baud rate of transmission. Possible values are: 110, 300, 1200, 2400, 4800, 9600, 19200, and UNSPECIFIED.

BSD Trailer Encapsulation

For 10Mb/sec Ethernet controllers only. Can be used to enable Berkeley Trailer encapsulation of IP packets on those Ethernets. There are two possible settings: NEGOTIATED or DISABLED. The default, DISABLED, prevents the use of trailer encapsulation.

Hardware Device

The name of the real Ethernet device; for example, se0.

Header Compression Mode

For PPP and SLIP devices, indicates whether to use Van Jacobson's TCP header compression algorithm. The parameter has three possible settings: DISABLED, ENABLED, or NEGOTIATED. DISABLED indicates that headers should never be compressed. ENABLED indicates that headers should always be compressed. The default is DISABLED. NEGOTIATED indicates that headers should not be compressed until a compressed header is received from the other side. At least one side of a link must be ENABLED for compression to be used; that is, both sides of a link cannot be set to NEGOTIATED for compression to be used.

ICMP

When ENABLED (the default), PPP allows ICMP packets over the PPP connection. Administrators may want to disable ICMP packets if they are concerned with "service attacks" from dial-up connections.

Idle Timeout

Determines how long (in seconds) the connection must be idle before PPP attempts to close it with "Terminate-Request" packets. The default is 0.

IP Address

Indicates the Internet address, in dotted decimal notation, associated with the interface. For PPP interfaces, you can specify 0.0.0.0 to indicate that the local IP address will be specified by the remote peer when a serial connection is established. The default is 0.0.0.0.

IP Address of remote system

Indicates the Internet address associated with the remote system.

IP Broadcast Address

For devices that support broadcasts, allows the setting of a non-standard IP broadcast address. The parameter defaults to an address whose host portion is all ones.

IP Subnet Mask

The subnet mask of the local interface in dotted decimal format. The default depends on the local interface IP address. For example, a class A address results in a default subnet mask of 255.0.0.0.

IPv6 global address

Indicates the global unique address associated with this interface.  The interface may also have a link-local address which will be automatically generated when the interface is started

IPv6 mask length

The length of the mask for the IPv6 address.

Link Level Encapsulation Mode

For Ethernet devices, indicates whether to use the standard Ethernet encapsulation of IP datagrams, or extended 802.2 encapsulation as specified in RFC 1042. Enter either ETHERNET or 802.2 as the value.

Maximum Receive Unit (MRU) Size

Determines the maximum number of 8-bit bytes for the PPP Information field, including Padding, but not including the Protocol field. Because opposite ends of a PPP connection may have different MRU values, PPP negotiates a suitable MRU for both systems. The default is 500.

Point-To-Point Device IP Destination Address

For point-to-point interfaces, indicates the IP address of the peer system on the other side of the connection. The default is 0.0.0.0.

Protocol Compression

When ON, PPP negotiates with the peer to use one byte instead of two for the Protocol fields to improve transmission efficiency on low-speed lines. Default is OFF.

Retry Count

Determines the number of attempts PPP makes to configure a connection with "Configure-Request" packets. The default is 0.

Termination Retry Count

Determines the number of attempts PPP makes to terminate a connection with "Terminate-Request" packets. The default is 0.

Timeout

Determines the time (in seconds) between successive Configure-Request or Terminate-Request packets. The default is 0.

VMS Device

For devices that use a VMS device driver to interface with the hardware, indicates the name of the VMS device that MultiNet will use. This parameter is used with HP Ethernet, PPP, and SLIP interfaces.

 

EXAMPLE

 

$ MULTINET CONFIGURE /NETWORK
MultiNet NFS Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
ADD PPP2
[Adding new configuration entry for device "PPP2"]
VMS Device: [TTA0]
RETURN
Baud Rate: [UNSPECIFIED] 9600
PPP ACCM Mask:  [%x0] RETURN
PPP Authentication Method: [NONE] PAP
PPP Protocol Compression: [OFF] ? ON
PPP Address and Control Field Compression: [OFF] ON
PPP Retry Count: [0] 10
PPP Idle Timeout: [0] 10
PPP MRU Size: [0] RETURN
PPP ICMP:  [ENABLED]  RETURN
PPP TCP Compression:  [OFF] RETURN
PPP Termination Retry Count: [0] 10
PPP Timeout:  [0]  10
IP Address: [NONE]  10.45.67.27
Point-to-Point Device IP Destination Address: [NONE] RETURN
IP Subnet Mask: [NONE] RETURN
NET-CONFIG> EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]

 

 

 

 


 

ATTACH

Detaches the terminal from the calling process and reattaches it to another process. Use the SPAWN SHOW PROCESS /SUBPROCESSES command to list the names of subprocesses. Use the DCL LOGOUT command to return to the original process. If the MULTINET_DISABLE_SPAWN logical is enabled, ATTACH does not work.

 

FORMAT

ATTACH process-name

 

PARAMETER

process_name

Specifies the name of a process to which you want our terminal attached. (Not all subprocesses can be attached; some testing may be required.)

 

EXAMPLE

$ MULTINET CONFIGURE  /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SPAWN
$ MM
MM>SPAWN SHOW PROCESS /SUB
...
There are 3 processes in this job:
_TWA42:
  PROC_1
   PROC_2 (*)
MM>
ATTACH _TWA42:
NET-CONFIG>ATTACH PROC_1
MM>QUIT
$ LOGOUT
NET-CONFIG>

This example shows the use and exit of attached subprocesses.

1.      The first command uses SPAWN to create a subprocess. MM is invoked from the DCL command line. Next, the SPAWN SHOW PROCESS/SUB command is used to list all the subprocess names. The display shows that three subprocesses are active. (Process _TWA42: is NET-CONFIG, PROC_1 is MM, and PROC_2 is the SPAWN SHOW PROCESS/SUB command.)

2.      In the next command, the MM ATTACH command returns control to the NET-CONFIG process. From this utility, ATTACH returns control to MM. To exit, QUIT is invoked from MM, and LOGOUT is invoked at the original spawned DCL command line; control returns back to NET-CONFIG. (If SPAWN SHOW PROCESS/SUB had been entered, only this command and the configuration processes would be active.)

 

 

 

 


 

CHECK

Checks the configuration parameters to ensure all required information is provided. If a problem is found, an error message displays; otherwise, if the check is successful, no information displays.

 

FORMAT

CHECK

 

DESCRIPTION

CHECK provides a check of the current configuration. The following messages can display:

Message

Description

ERROR: device_name can't $ASSIGN to FFI device: value

The specified X device does not exist, or a lack of privileges made opening the device impossible.

ERROR: device_name can't $ASSIGN to SLIP device: value

The specified device does not exist, or a lack of privileges made opening the device impossible.

ERROR: device_name: Default route cannot be the local machine: default_route

The default route is the gateway that connects this system to the Internet; it cannot be the local system.

ERROR: device_name: Default route route must be directly connected

The IP address specified in the SET DEFAULT-ROUTE command must be for a system connected to the Internet.

ERROR: device_name: Illegal value for IP Address: address

The specified IP address either has an octet above 255, or contains an illegal character such as a space, an alphabetical character, or a control character. Use the MODIFY command to specify a new value.

ERROR: device_name: Illegal value for IP Broadcast Address: address

The specified IP broadcast address either has an octet above 255, or contains an illegal character such as a space, an alphabetical character, or a control character. Use the MODIFY command to specify a new value.

ERROR: device_name: Illegal value for IP SubNet Mask: mask

The specified IP subnet mask value either has an octet above 255, or contains an illegal character such as a space, an alphabetical character, or a control character. Use the MODIFY command to specify a new value.

ERROR: device_name is slave to  nonexistent device hardware_device

The MultiNet device points to a device that does not exist for the local system.

ERROR: device_name's DECnet peer must be DECnet node name, not address

DECnet node names are alphanumeric strings of six characters or less; specify the correct value.

ERROR: device_name's point-to-point destination is unspecified

A destination address was not specified for a point-to-point device, such as a SLIP line.

ERROR: device_name's PSI peer must be PSI DTE, not node.

The "IP Over PSI Peer Host's DTE" prompt is requesting the DTE destination name; specify the correct value.

ERROR: device_name's PSI local must be PSI DTE, not node.

The "IP Over PSI Local Host's DTE" prompt is requesting the DTE source name; specify the correct value.

ERROR: The host name is not a domain-style host name and domain name service is enabled.

The domain name did not contain dot separators.

ERROR: There is no Host Name specified.

A host name value was not entered either in the configuration file you are creating or in a read-in configuration file.

WARNING: device_name has no FFI device specified

The added or modified device requires that an FFI device be specified.

WARNING: device_name has no protocol addresses specified

The added or modified device requires that protocol addresses be specified.

WARNING: device_name's DECnet peer is unspecified (link will not come up)

Both ends of a point-to-point DECnet link must be specified.

WARNING: device_name's hardware device is unspecified

A device name must be entered for this device.

WARNING: device_name's PSI peer is unspecified (link will not come up)

Both ends of a point-to-point PSI link must be specified.

WARNING: device_name's PSI local DTE is unspecified (link will not come up)

Both ends of a point-to-point PSI link must be specified.

 

EXAMPLE

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
ADD PPP1
[Adding new configuration entry for device "ppp1"]
VMS Device: [TTA0] 
TTA1
Baud Rate:  [UNSPECIFIED] 9600
PPP ACCM Mask:  [%x0] RETURN
PPP Authentication Method: [NONE] PAP
PPP Protocol Compression: [OFF] ON
PPP Address and Control Field Compression: [OFF] ON
PPP Retry Count: [0] 10
PPP Idle Timeout: [0] 10
PPP MRU Size: [0] 10
PPP ICMP:  [ENABLED] RETURN
PPP TCP Compression: [OFF] RETURN
PPP Termination Retry Count: [0] RETURN
PPP Timeout: [0] RETURN
IP Address: [NONE] RETURN
Point-to-Point Device IP Destination Address: [NONE] 10.45.24.13
IP Subnet Mask: [NONE] RETURN
[ppp] (Point-to-Point Protocol): Csr=NONE, Flags=%X0]
NET-CONFIG>
CHECK
WARNING: ppp1 has no protocol addresses specified
NET-CONFIG>
EXIT
$

 

 

 

 


 

CLEAR

Deletes all devices from the current network configuration.

 

FORMAT

CLEAR

 

EXAMPLE

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
CLEAR

 

 

 

 


 

CREATE

Create a Six-to-Four IPv6 interface.

 

FORMAT

CREATE

 

EXAMPLE

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
CREATE SIX-TO-FOUR
IPv4 address to use [none]:
192.43.1.1
Mask Length [48]:

 

Note that RFC 1597 private address (10.*.*.*, 172.16.*.*, 192.168.*.*) and RFC 3927 IPv4 link-local addresses (169.254.*.*) are not allowed for the IPv4 address.

 

 

 

 


 

DELETE

Removes a single device from the network configuration.

 

FORMAT

DELETE interface

 

PARAMETER

interface

Specifies the name of the interface for the device being removed.

 

EXAMPLE

This example deletes a SLIP device, SL0, from the current configuration.

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
DELETE SL0

 

 

 

 


 

DISABLE

Disables a device. A disabled device is deleted from the configuration and is not configured at network boot.

 

FORMAT

DISABLE interface

 

PARAMETER

interface

Specifies the name of the interface for the device being disabled.

 

EXAMPLE

This example disables a SLIP device, SL0.

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
DISABLE SL0

 

 

 

 


 

ENABLE

Enables a device.

 

FORMAT

ENABLE interface

 

PARAMETER

interface

Specifies the name of the interface for the device being enabled.

 

EXAMPLE

This example enables a SLIP device, SL0.

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
ENABLE SL0

 

 

 

 


 

ERASE

Erases all configured devices from the current configuration. (Functionally equivalent to CLEAR.)

 

 

 

 


 

EXIT

Saves the current configuration, if it has been modified, and exits the configuration program. (Use the STATUS command to display whether the configuration was modified.)

 

FORMAT

EXIT

 

EXAMPLES

When the configuration has not been changed, a message displays indicating that the configuration file is not updated.

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
EXIT
[Configuration not modified, so no update needed]
$

When the configuration has changed, a message displays indicating that the configuration file has been updated.

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
CLEAR
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$

 

 

 

 


 

GET

Reads in a nonstandard configuration file.

 

FORMAT

GET filename

 

PARAMETER

filename

Specifies the name of the configuration file to read; by default, NETWORK_DEVICES.CONFIGURATION in the current working directory.

 

EXAMPLE

This example retrieves the configuration file MULTINET:TEST.CONFIGURATION into the NET-CONFIG workspace.

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
GET MULTINET:TEST.CONFIGURATION

 

 

 

 


 

HELP

Displays help information by listing either the command names or information about specific commands. You can also display help information by adding a question mark to other NET-CONFIG commands.

 

FORMAT

HELP command

 

PARAMETER

command

Specifies the command for which to list help information. Use a question mark (?) to list all command names. Entering a question mark on the NET-CONFIG command line has the same effect as using the HELP ? command.

 

EXAMPLE

$ MULTINET CONFIGURE /NETWORK_DEVICES

MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
HELP ?
ADD     ATTACH   CHECK   CLEAR    DELETE  DISABLE  ENABLE   ERASE
EXIT    GET      HELP    MODIFY   PUSH    QUIT     SAVE     SET
SHOW    SPAWN    STATUS  USE      ERSION  WRITE
NET-CONFIG>

 

 

 

 


 

MODIFY

Modifies an existing device configuration. If the device has not already been configured, an error message displays.

Use MODIFY to modify configuration parameters for an existing network interface. MODIFY produces the same sequence of prompts for network interface parameter values as the ADD command, but uses the current settings for default values.

 

FORMAT

MODIFY interface

 

PARAMETER

interface

Specifies the name of the interface for the device being modified.

 

EXAMPLE

 

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
MODIFY SE0
[Modifying configuration entry for device "se0"]
VMS Device: [EZA0]
RETURN
Link Level Encapsulation Mode: [ETHERNET]  ? EXTENDED-802.2
BSD Trailer Encapsulation: [DISABLED] RETURN
IP Address: [10.45.678.90] RETURN
IP Subnet Mask: [255.255.255.0] RETURN
Non-Standard IP Broadcast Address: [NONE] RETURN
se0 (Shared VMS Ethernet/FDDI): Csr=NONE, flags=%x0)
NET-CONFIG>

 

 

 

 


 

PUSH

Starts and attaches a DCL subprocess. If a parent process exists, attach to it. To return from DCL, use the ATTACH or the LOGOUT command. To switch back from a DCL subprocess, use the ATTACH command.

If the MULTINET_DISABLE_SPAWN logical is set, PUSH does not work.

 

FORMAT

PUSH

 

 

 

 


 

QUIT

Prompts you to save the current configuration if it was modified, and then exits.

 

FORMAT

QUIT

 

EXAMPLE

$ MULTINET CONFIGURE /NETWORK_DEVICES
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
DISABLE SL0
NET-CONFIG>QUIT
Configuration modified, do you want to save it?  [NO]
RETURN

 

 

 

 


 

SAVE

Saves the configuration parameters.

 

FORMAT

SAVE [/STARTUP] [filename]

 

PARAMETER

filename

Specifies the file name for the configuration file or the startup command procedure. The default for filename when saving the configuration data is the file from which the configuration was read. The default for filename when saving the MultiNet startup command procedure is MULTINET:START_MULTINET.COM.

 

QUALIFIER

/STARTUP

Specifies that NET-CONFIG saves the MultiNet startup commands in filename.

 

 

 

 


 

SET ANONYMOUS-FTP-ACCESS

Defines file access rights for the ANONYMOUS FTP user to read, write, delete, and list files in addition to spawning a new process.

If your configuration permits users to make anonymous file transfers via the VMS ANONYMOUS account, use the ANONYMOUS-FTP-ACCESS parameter to restrict file access for that account.

You can change the value of ANONYMOUS-FTP-ACCESS without rebooting by also defining or redefining the system-wide MULTINET_ANONYMOUS_FTP_ACCESS logical name.

 

FORMAT

SET ANONYMOUS-FTP-ACCESS (access [access])

 

PARAMETERS

access

NOLIST - Disables the listing of files.

NOWRITE - Disables the storing of files.

NOSPAWN - Disables the SPAWN command.

NOREAD - Disables reading of files.

NODELETE - Disables the deleting/renaming of files.

 

EXAMPLE

The following example sets the ANONYMOUS-FTP-ACCESS parameter to NOWRITE, and then sets the system-wide MULTINET_ANONYMOUS_FTP_ACCESS  logical name. By setting this logical name, ANONYMOUS_FTP_ACCESS can be set without rebooting the system. Setting the NOWRITE parameter will prevent anonymous users from storing files.

$ MULTINET CONFIGURE /INTERFACE

MultiNet Network Configuration Utility V5.6(104)

[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]

[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]

NET-CONFIG>SET ANONYMOUS-FTP-ACCESS NOWRITE
NET-CONFIG>
EXIT

[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next MultiNet reload]

$ DEFINE /SYSTEM /EXECUTIVE MULTINET_ANONYMOUS_FTP_ACCESS "NOWRITE"

 

 

 

 


 

SET ANONYMOUS-FTP-DIRECTORY

Restricts directory tree access of an anonymous FTP account.

If your configuration permits users to make anonymous file transfers via the VMS ANONYMOUS account, use the ANONYMOUS-FTP-DIRECTORY parameter to restrict access for that account to a specific directory tree.

You can change the value of ANONYMOUS-FTP-DIRECTORY without rebooting by also defining or redefining the system-wide MULTINET_ANONYMOUS_FTP_DIRECTORY logical name.

 

FORMAT

SET ANONYMOUS-FTP-DIRECTORY [directory]

 

PARAMETER

directory

Specifies the name of the directory tree to which the account is restricted. To cancel the restriction, enter the command without a directory name.

 

EXAMPLE

This example sets the ANONYMOUS-FTP-DIRECTORY parameter to USERS:[ANONYMOUS], then sets the system-wide MULTINET_ANONYMOUS_FTP_DIRECTORY logical name. By setting the system-wide logical name, ANONYMOUS-FTP-DIRECTORY can be set without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET ANONYMOUS-FTP-DIRECTORY USERS:[ANONYMOUS]
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE -
_$ MULTINET_ANONYMOUS_FTP_DIRECTORY "USERS:[ANONYMOUS]"
$

 

 

 

 


 

SET CLUSTER-SERVICE-ADDRESS

Identifies the IP address to be used when responding to address queries for hosts specified by CLUSTER-SERVICE-NAMES.

If your host is configured with more than one interface, the DOMAINNAME service is enabled, and you are using cluster load balancing, use the CLUSTER-SERVICE-ADDRESS parameter to identify the IP address that this host will return in response to address queries for any host specified by CLUSTER-SERVICE-NAMES.

If you do not specify an address, an interface is chosen at random.

 

FORMAT

SET CLUSTER-SERVICE-ADDRESS [ip_address]

 

PARAMETER

ip_address

Specifies the IP address returned when responding to address queries from hosts identified by CLUSTER-SERVICE-NAMES.

 

EXAMPLE

This example sets the CLUSTER-SERVICE-ADDRESS parameter to 10.43.154.10 and then sets the system-wide MULTINET_CLUSTER_SERVICE_ADDRESS logical name. By setting the system-wide logical name, the CLUSTER-SERVICE-ADDRESS can be set without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET CLUSTER-SERVICE-ADDRESS 10.43.154.10
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE -
_$ MULTINET_CLUSTER_SERVICE_ADDRESS "10.43.154.10"
$ @MULTINET:START_SERVER
$

 

 

 

 


 

SET CLUSTER-SERVICE-NAMES

Lists host names to which cluster load balancing applies, and allows you to configure hosts so that TCP-based connections are directed to the host with the lightest load at the time of the request. The DOMAINNAME service must be enabled on each host. To establish this environment:

1.      Configure the primary name server for the parent domain so that it delegates authority for each host specified with the CLUSTER-SERVICE-NAMES parameter to this host.

2.      Use the CLUSTER-SERVICE-NAMES parameter to identify the hosts for which this host will accept connections.

For example, if authority for CLUSTER.EXAMPLE.COM is delegated to NODE1, NODE2, and NODE3 on the primary name servers, each node must include CLUSTER.EXAMPLE.COM in its CLUSTER-SERVICE-NAMES list. When a TCP service request is made to CLUSTER.EXAMPLE.COM, DNS returns the IP addresses of the nodes NODE1, NODE2, or NODE3, ordered by load rating.

If the host is configured with more than one interface, specify the desired interface with the CLUSTER-SERVICE-ADDRESS parameter.

 

FORMAT

SET CLUSTER-SERVICE-NAMES hostlist

 

PARAMETER

hostlist

Specifies a comma-separated list of fully qualified host names for which cluster load balancing is implemented.

 

EXAMPLE

This example sets the CLUSTER-SERVICE-NAMES parameter to CLUSTER.EXAMPLE.COM, then sets the system-wide MULTINET_CLUSTER_SERVICE_NAMES logical. By setting the system-wide logical, CLUSTER-SERVICE-NAMES can be set without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET CLUSTER-SERVICE-NAMES CLUSTER.EXAMPLE.COM
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE/SYSTEM/EXECUTIVE -
_$ MULTINET_CLUSTER_SERVICE_NAMES "CLUSTER.EXAMPLE.COM"
$ @MULTINET:START_SERVER
$

 

 

 

 


 

SET DEFAULT-RMT-TAPE-DEVICE

Defines the default VMS tape drive that the RMT server uses. (This drive is the VMS equivalent of the UNIX /dev/rmt0 interface, and is the drive used by the rdump and rrestore programs.) If the parameter is not set, the server searches for interface types in the following order and uses the first interface it finds: MU, MK, MF, MT, and MS.

You can change the value of DEFAULT-RMT-TAPE-DEVICE without rebooting by also defining or redefining the system-wide logical name MULTINET_RMT_TAPE_DEVICE.

 

FORMAT

SET DEFAULT-RMT-TAPE-DEVICE drive_name

 

PARAMETER

drive_name

Specifies the name of the default drive.

 

EXAMPLE

This example sets DEFAULT-RMT-TAPE-DEVICE to HSC001$MUA1:, then sets the MULTINET_RMT_TAPE_DEVICE system-wide logical name. By setting this logical name, the tape device can be given a new value without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET DEFAULT-RMT-TAPE-DEVICE HSC001$MUA1:
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE MULTINET_RMT_TAPE_DEVICE "HSC001$MUA1:"
$

 

 

 

 


 

SET DEFAULT-ROUTE

Defines the default IP route-that is, the IP address of the gateway that MultiNet uses for all packets sent from the local network.

You can specify more complex routing information by either:

·         Creating a MULTINET:LOCAL_ROUTES.COM file that contains a list of MULTINET
SET/ROUTE
commands that set up the routing tables on a per-network basis.

·         Running a dynamic-routing protocol such as RIP, HELLO, EGP, or BGP by configuring the GATED service.

 

 

Note: Any GATED configuration overrides a default IP route set with NET-CONFIG. Once started, GATED takes complete control of your routing.

 

 

You can change the default route without rebooting by using the MULTINET SET/ROUTE command to delete the old default route and add the new default route.

 

FORMAT

SET DEFAULT-ROUTE ip_address

 

PARAMETER

ip_address

Specifies the IP address of the gateway.

 

EXAMPLE

This example sets the gateway DEFAULT-ROUTE to 10.41.228.100, then performs the commands that change DEFAULT-ROUTE without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET DEFAULT-ROUTE 10.41.228.100
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
MULTINET SET/ROUTE -
_$ /DELETE=(DESTINATION=0.0.0.0, GATEWAY=10.41.228.100)
$ MULTINET SET/ROUTE -
_$ /ADD=(DESTINATION=0.0.0.0, GATEWAY=10.41.228.100)

 

 

 

 


 

SET DOMAIN-NAMESERVERS

Configures the DNS domain resolver, the portion of MultiNet called when a host name must be translated into an Internet address. If you are using DNS, use this parameter to define the Internet addresses of the Domain Name Servers to which the resolver will send requests.

The usual setting for the parameter is the loopback address (127.0.0.1), which directs the resolver to send inquiries to the server on the local system.

To disable DNS and use the host tables instead of the service, enter the SET DOMAIN-NAMESERVERS command with no options.

You can change the value of DOMAIN-NAMESERVERS without rebooting by also defining or redefining the system-wide logical name MULTINET_NAMESERVERS and restarting the MULTINET_SERVER (@MULTINET:START_SERVER) and SMTP_SYMBIONT (@MULTINET:START_SMTP) processes.

 

FORMAT

SET DOMAIN-NAMESERVERS [address [,address ...]]

 

PARAMETER

address

Specifies the IP address of a name server. When you list multiple addresses, the resolver successively attempts to send a packet to the addresses, in the listed order, until it receives a response.

 

RESTRICTION

The resolver nameserver list can only include three IP addresses. This list is controlled by the MULTINET_NAMESERVERS logical (which is controlled by the DOMAIN-NAMESERVERS parameter).

 

EXAMPLES

This example tells the resolver to try only the local nameserver. The subsequent DCL commands change domain nameservers without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET DOMAIN-NAMESERVERS 127.0.0.1
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXEC MULTINET_NAMESERVERS "127.0.0.1"
$ DEFINE /SYSTEM /EXEC UCX$BIND_SERVER000 "127.0.0.1"
$ DEFINE /SYSTEM /EXEC UCX$BIND_DOMAIN "EXAMPLE.COM"
$ DEFINE /SYSTEM /EXEC TCPIP$BIND_SERVER000 "127.0.0.1"
$ DEFINE /SYSTEM /EXEC TCPIP$BIND_DOMAIN "EXAMPLE.COM"
$ @MULTINET:START_SERVER
$ @MULTINET:START_SMTP
$

 This example configures the resolver to try the local name server and, if it fails, to try 10.0.0.1.

NET-CONFIG>SET DOMAIN-NAMESERVERS 127.0.0.1,10.0.0.1
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
$
DEFINE /SYSTEM /EXEC MULTINET_NAMESERVERS "127.0.0.1", "10.0.0.1"
$ DEFINE /SYSTEM /EXEC UCX$BIND_SERVER000 "127.0.0.1"
$ DEFINE /SYSTEM /EXEC UCX$BIND_SERVER001 "10.0.0.1"
$ DEFINE /SYSTEM /EXEC UCX$BIND_DOMAIN "EXAMPLE.COM"
$ DEFINE /SYSTEM /EXEC TCPIP$BIND_SERVER000 "127.0.0.1"
$ DEFINE /SYSTEM /EXEC TCPIP$BIND_SERVER001 "10.0.0.1"
$ DEFINE /SYSTEM /EXEC TCPIP$BIND_DOMAIN "EXAMPLE.COM"
$ @MULTINET:START_SERVER
$ @MULTINET:START_SMTP
$

The SET DOMAIN-NAMESERVERS disables the local DNS domain server; only host tables are used to translate names and addresses.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET DOMAIN-NAMESERVERS
NET-CONFIG>EXIT
$
$
DEASSIGN /SYSTEM /EXEC MULTINET_NAMESERVER
$ DEASSIGN /SYSTEM /EXEC UCX$BIND_SERVER000
$ DEASSIGN /SYSTEM /EXEC UCX$BIND_SERVER001
$ DEASSIGN /SYSTEM /EXEC UCX$BIND_DOMAIN
$ DEASSIGN /SYSTEM /EXEC TCPIP$BIND_SERVER000
$ DEASSIGN /SYSTEM /EXEC TCPIP$BIND_SERVER001
$ DEASSIGN /SYSTEM /EXEC TCPIP$BIND_DOMAIN
$ @MULTINET:START_SERVER
$ @MULTINET:START_SMTP
$

 

 

 

 


 

SET HOST-NAME

Specifies the local computer's host name and defines the default local domain. If your configuration includes Domain Name Service (DNS), you must specify the host name in dotted format, for example, HAMLET.CALTECH.EDU or JETSON.SPROCKETS.COM.

The default local domain is derived from the HOST-NAME parameter. For example, with a host name of HAMLET.CALTECH.EDU, the default local domain is .CALTECH.EDU. MultiNet uses the default local domain to complete abbreviated host names. For example, with the default of CALTECH.EDU, if you entered the command: 

$ TELNET ROMEO

TELNET would attempt to connect to a ROMEO.CALTECH.EDU host.

You can change the value of HOST-NAME without rebooting by also defining or redefining the system-wide logical name MULTINET_HOST_NAME and restarting the MULTINET_SERVER (@MULTINET:START_SERVER) and SMTP_SYMBIONT (@MULTINET_START_STMP) processes.

 

FORMAT

SET HOST-NAME host

 

PARAMETER

host

Specifies the name of your host.

 

EXAMPLE

This example sets the HOST-NAME to HAMLET.CALTECH.EDU, then issues the commands that change the parameter without rebooting the system.

$ MULTNET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET HOST-NAME HAMLET.CALTECH.EDU
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXEC MULTINET_HOST_NAME "HAMLET.CALTECH.EDU"
$ DEFINE /SYSTEM /EXEC ARPANET_HOST_NAME "HAMLET.CALTECH.EDU"
$ DEFINE /SYSTEM /EXEC UCX$INET_HOST "HAMLET.CALTECH.EDU"
$ DEFINE /SYSTEM /EXEC UCX$BIND_DOMAIN "FLOWERS.COM"
$ DEFINE /SYSTEM /EXEC TCPIP$INET_HOST "HAMLET.CALTECH.EDU"
$ DEFINE /SYSTEM /EXEC TCPIP$BIND_DOMAIN "FLOWERS.COM"
$ @MULTINET:START_SERVER
$ @MULTINET:START_SMTP
$

 

 

 

 


 

SET IP-CLUSTER-ALIASES

Specifies a list of cluster-wide Internet addresses to which this node should respond.

In a VMScluster, the nodes coordinate among themselves so that only one node responds to the cluster-wide addresses at any one time. Should that node fail or be shut down, another node immediately takes over this task.

You can use this parameter with connectionless protocols (such as NFS) for automatic failover.
IP-CLUSTER-ALIASES specifies a list of IP addresses to which this node should respond in addition to the address(es) that are configured for the interfaces you define.

Disable IP-CLUSTER-ALIASES by entering the value without specifying an address.

You can change the value of IP-CLUSTER-ALIASES without rebooting by also defining or redefining the system-wide logical name MULTINET_IP_CLUSTER_ALIASES and restarting the MULTINET_SERVER (@MULTINET:START_SERVER) process.

 

FORMAT

SET IP-CLUSTER-ALIASES [address [,address ...]]

 

PARAMETER

address

Specifies the Internet address to which to respond.

 

EXAMPLE

This example sets IP-CLUSTER-ALIASES to 10.1.1.2, then executes the commands that change this parameter without rebooting the system.

$ MULTNET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET IP-CLUSTER-ALIASES 10.1.1.2
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE MULTINET_IP_CLUSTER_ALIASES "10.1.1.2"
$ @MULTINET:START_SERVER

 

 

 

 


 

SET LOAD-EXOS-DRIVER

Enables automatic loading of the Novell EXOS-compatible $QIO driver when MultiNet starts. The driver allows MultiNet to support Novell's EXOS programming interface.

Reboot your system after setting LOAD-EXOS-DRIVER so that the change is recognized by the operating system.

 

FORMAT

SET LOAD-EXOS-DRIVER {TRUE | FALSE}

 

PARAMETERS

TRUE

Enables the EXOS $QIO programming interface.

 

FALSE

Disables the EXOS $QIO programming interface (the default setting).

 

EXAMPLE

$ MULTNET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET LOAD-EXOS-DRIVER TRUE

 

 

 

 


 

SET LOAD-PWIP-DRIVER

Enables automatic loading of the version 5 PATHWORKS server interface (PWIP) driver when MultiNet starts. You must enable the PWIP driver to use version 5 PATHWORKS.

 

Note: Earlier versions of PATHWORKS use the UCX interface.

 

 

Reboot your system after setting LOAD-PWIP-DRIVER so that the change is recognized by the operating system.

 

FORMAT

SET LOAD-PWIP-DRIVER {TRUE | FALSE}

 

PARAMETERS

TRUE

Enables the PWIP driver.

 

FALSE

Disables the PWIP driver (the default setting).

 

 

 

 


 

SET LOCAL-DOMAIN

Overrides the default local domain derived from a previous SET HOST-NAME command.

If your configuration includes a Domain Name System (DNS) domain server, you can use the LOCAL-DOMAIN parameter to override the default local domain derived from the HOST-NAME parameter.

You can change the value of LOCAL-DOMAIN without rebooting by also defining or redefining the system-wide logical name MULTINET_LOCALDOMAIN and restarting the MULTINET_SERVER (@MULTINET:START_SERVER) and SMTP_SYMBIONT (@MULTINET_START_SMTP) processes.

 

FORMAT

SET LOCAL-DOMAIN domain

 

PARAMETER

domain

Specifies the default domain name.

 

EXAMPLE

This example sets LOCAL-DOMAIN to EXAMPLE.COM, then invokes the commands that change this parameter without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from ULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET LOCAL-DOMAIN EXAMPLE.COM
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE MULTINET_LOCALDOMAIN "EXAMPLE.COM"
$ DEFINE /SYSTEM /EXECUTIVE UCX$BIND_DOMAIN "EXAMPLE.COM"
$ DEFINE /SYSTEM /EXECUTIVE TCPIP$BIND_DOMAIN "EXAMPLE.COM"
$ @MULTINET:START_SERVER
$ @MULTINET:START_SMTP
$

 

 

 

 


 

 

SET LPD-DEFAULT-USERNAME

Specifies a default user name for print jobs received from a remote system via the LPD protocol.

The LPD-DEFAULT-USERNAME parameter allows all print jobs requested by remote users to be processed, regardless of whether each user has a local VMS user name. The parameter defines a default user name for users without local user names.

You can change the value of LPD-DEFAULT-USERNAME without rebooting by also defining or redefining the system-wide logical name MULTINET_LPD_DEFAULT_USERNAME.

 

FORMAT

SET LPD-DEFAULT-USERNAME user

 

PARAMETER

user

Specifies the default user name, which must be an existing name in the OpenVMS system.

 

EXAMPLE

This example sets LPD-DEFAULT-USERNAME to PYWACKET, then executes the commands that change this parameter without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET LPDD-DEFAULT-USERNAME PYWACKET
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE MULTINET_FPD_DEFAULT_USERNAME "PYWACKET"

 

 

 

 


 

SET NAMESERVER-RETRANSMISSION

Controls the time between requests and the number of name server requests made before the system stops sending requests to a nonresponding server. The first argument is the time in seconds; the optional second argument is the number of tries to make.

You can change the value of NAMESERVER-RETRANSMISSION without rebooting by also defining or redefining the system-wide logical names MULTINET_NAMESERVER_RETRANS and MULTINET_NAMESERVER_RETRY and restarting the MULTINET_SERVER (@MULTINET:START_SERVER) and SMTP_SYMBIONT (@MULTINET_START_SMTP) processes.

 

FORMAT

SET NAMESERVER-RETRANSMISSION seconds retries

 

PARAMETERS

seconds

Specifies the time between retransmissions, in seconds (by default, 4 seconds).

 

retries

Specifies the number of retransmissions to make before giving up (by default, 4 tries).

 

EXAMPLE

This example specifies that the name server waits eight seconds between retries, and makes up to four retries before the system stops sending requests to the nonresponding server. The commands after setting this parameter allow the parameter to take effect immediately without rebooting the system.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET NAMESERVER-RETRANSMISSION 8 4
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE MULTINET_NAMESERVER_RETRANS 8
$ DEFINE /SYSTEM /EXECUTIVE MULTINET_NAMESERVER_RETRY 4
$ @MULTINET:START_SERVER
$ @MULTINET:START_SMTP

 

 

 

 


 

SET SNMP-MAX-CONNECTIONS

Defines the maximum number of connections that the SNMP agent will report on.

 

Format

SET SNMP-MAX-CONNECTIONS number

 

Parameter

number

Specifies the maximum number of connections that he SNMP agent will report on.

 

Description

Use the SNMP-MAX-CONNECTIONS parameter to increase the maximum number of connections that the SNMP agent will report on.  A number that is too low will prevent the SNMP agent from reporting on any connections.  If this parameter is not set, the SNMP agent uses the default of 256 connections. The maximum value is 3276.

 

 

 

 


 

SET SNMP-MAX-ROUTES

Defines the maximum number of routes that the SNMP agent will report on.

 

Format

SET SNMP-MAX-ROUTES number

 

Parameter

number

Specifies the maximum number of routes that the SNMP agent will report on.

 

Description

Use the SNMP-MAX-ROUTES parameter to increase the maximum number of routes that the SNMP agent will report on.  A number that is too low will prevent the SNMP agent from reporting on any routes.  If this parameter is not set, the SNMP agent uses the default of 256 connections. The maximum value is 2978.

 

 

 

 


 

SET SPOOL-DIRECTORY

Changes the MultiNet spool directory from its default of MULTINET_COMMON_ROOT:[MULTINET.SPOOL]. The spool directory is used to store transient mail and print files.

You can change the value of SPOOL-DIRECTORY without rebooting by also defining or redefining the system-wide logical name MULTINET_SPOOL.

 

FORMAT

SET SPOOL-DIRECTORY directory

 

PARAMETER

directory

Specifies the new spool directory.

 

EXAMPLE

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET SPOOL-DIRECTORY SYS$SYSROOT:[TMP]
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE MULTINET_SPOOL "SYS$SYSROOT:[TMP]"

 

 

 

 


 

SET TFTP-DIRECTORY

Defines the TFTP server's default directory.

 

FORMAT

SET TFTP-DIRECTORY directory

 

PARAMETER

directory

Specifies the name of the new default directory.

 

DESCRIPTION

Use the TFTP-DIRECTORY parameter to define the TFTP server's default directory. When the parameter is not set, there is no default directory.

You can change the value of TFTP-DIRECTORY without rebooting by also defining or redefining the system-wide logical name MULTINET_TFTP_DEFAULT_DIRECTORY, then issuing the MULTINET NETCONTROL TFTP RELOAD command.

 

EXAMPLE

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET TFTP-DIRECTORY USERS:[TFTP-FILES]
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE –

_$ MULTINET_TFTP_DEFAULT_DIRECTORY "USERS:[TFTP-FILES]"
$ MULTINET NETCONTROL TFTP RELOAD
$

 

 

 

 


 

SET TIMEZONE

Although VMS does not keep track of time zones, MultiNet requires this information. The TIMEZONE parameter sets the time zone for your system and indirectly specifies the offset from GMT (and UTC) at which the local VMS clock is run. MultiNet automatically adjusts for Daylight Savings Time (DST) if appropriate for the rules in effect.

If your VMS clock time and your local time differ, set the TIMEZONE parameter to correspond to the VMS clock.

You can change the value of TIMEZONE without rebooting by using the MULTINET SET TIMEZONE command.

 

FORMAT

SET TIMEZONE timezone

 

PARAMETER

timezone

Specifies the abbreviation for the time zone, for example, PST.

 

EXAMPLE

This example sets the time zone to PST (Pacific Standard Time), then uses SET TIMEZONE to assign the same value to the system-wide variable.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET TIMEZONE PST
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
MULTINET SET/TIMEZONE PST
$

 

 

 

 


 

SET TIMEZONE-RULES

Sets the time zone rules in effect for your system.

The normal time zone rules in MultiNet include zones for the United States and a number of other countries around the world. Certain countries, such as Canada, have their own Daylight Savings Time rules for time zones such as PST, Pacific Standard Time. The TIMEZONE-RULES parameter is used to override the default rules.

You can change the value of TIMEZONE-RULES without rebooting by using the MULTINET SET TIMEZONE command.

 

FORMAT

SET TIMEZONE-RULES zonelist

 

PARAMETER

zonelist

Specifies a comma-separated list of countries and time zones for which to load rules. These can be found in MULTINET:TIMEZONES.DAT.

 

EXAMPLE

This example sets the TIMEZONE-RULES to US/ARIZONA, then sets the system-wide variable to the same value so that the system does not have to be rebooted for the new rules to take effect.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET TIMEZONE-RULES US/ARIZONA
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
MULTINET SET/TIMEZONE MST/SELECT="US/ARIZONA"
$

 

 

 

 


 

SET WHOIS-DEFAULT-SERVER

Sets the default server for the WHOIS command. The WHOIS command displays host information obtained from the RS.INTERNIC.NET host server.

By default, WHOIS connects to the server on the host RS.INTERNIC.NET, but can be overridden using the /HOST qualifier. Use this command to change the default server.

You can change the value of WHOIS-DEFAULT-SERVER without rebooting by also defining or redefining the system-wide logical name MULTINET_WHOIS_DEFAULT_SERVER.

 

FORMAT

SET WHOIS-DEFAULT-SERVER host

 

PARAMETER

host

Specifies the name of the server to which to connect. If not specified, the host defaults to RS.INTERNIC.NET.

 

EXAMPLE

This example sets WHOIS-DEFAULT-SERVER to FNORD.EXAMPLE.COM, then sets the system-wide logical name MULTINET_WHOIS_DEFAULT_SERVER to the same value to avoid rebooting the system after changing the WHOIS default server parameter.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET WHOIS-DEFAULT-SERVER FNORD.EXAMPLE.COM
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$
DEFINE /SYSTEM /EXECUTIVE -
_$ MULTINET_WHOIS_DEFAULT_SERVER "FNORD.EXAMPLE.COM"

 

 

 

 


 

SET WINS-COMPATIBILITY

Enables automatic definition of the logical names required for compatibility with applications developed for the WIN/TCP and Pathway for OpenVMS products from The Wollongong Group. The logical names allow MultiNet to support applications that run under those products. You must also generate a UNIX-format host table using the MULTINET HOST_TABLE COMPILE/UNIX command.

 

FORMAT

SET WINS-COMPATIBILITY {TRUE | FALSE}

 

PARAMETERS

TRUE

Enables the definition of the WIN/TCP and Pathway for OpenVMS compatibility logical names.

 

FALSE

Disables the definition of the WIN/TCP and Pathway for OpenVMS compatibility logical names.

 

EXAMPLES

 

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SET LOCAL-DOMAIN EXAMPLE.COM
NET-CONFIG>
EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]

Use the following DCL commands to enable WINS compatibility mode without a reboot:

$ DIRECTORY = F$TRNLNM("MULTINET_SPECIFIC_ROOT")  - "]"
$
DEFINE/SYSTEM/EXEC/TRANSLATION_ATTRIBUTES=CONCEAL TWG$ETC -
$_
’DIRECTORY’MULTINET.], ’DIRECTORY’SYSCOMMON.MULTINET.]
$
DEFINE/SYSTEM/EXEC/TRNASLATION_ATTRIBUTES=CONCEAL TWG$TCP
$
DEFINE/SYSTEM/EXEC INET_DOMAIN_NAME ’EXAMPLE.COM"
$
DEFINE/SYSTEM/EXEC INET_NAMESERVER_LIST "127.0.0.1"
$
DEFINE/SYSTEM/EXEC WINS_MAILSHR MULTINET:SMTP_MAILSHR
$
DEFINE/SYSTEM/EXEC DECW$TRANSPORT_WINTCP DECW$TRANSPORT_TCIP

Whether you choose to reboot or not, use the following commands to create a UNIX-format host table:

$ SET DEFAULT MULTINET_COMMON_ROOT:[MULTINET]
$
MULTINET HOST_TABLE COMPILE /UNIX
$

 

 

 

 


 

SHOW

Displays the current MultiNet device configuration.

 

FORMAT

SHOW command

 

PARAMETER

command

Specifies the type of display. Accepted values are CURRENT (the default) or MAXIMUM. If a command is not entered, the default is CURRENT.

 

EXAMPLE

This example lists the current configuration.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading in configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>
SHOW

Interface

Adapter

CSR Address

Flags/Vector

se0  (Shared VMS Ethernet)
     [TCP/IP: 10.41.228.78]
     [VMS Device: ESA0]

-NONE-

-NONE-

-NONE-

s10  (Serial Line IP)
     [TCP/IP: 192.41.228.78==>10.41.228.80]
     [VMS Terminal: TTA2, 9600 Baud]
     [Header Compression DISABLED]

-NONE-

-NONE-

-NONE-

*s11 (Serial Line IP)
     [VMS Terminal: TXA0]
     [Header Compression DISABLED]

-NONE-

-NONE-

-NONE-

 

Official Host Name:        BANANA.EXAMPLE.COM
Default IP Route:          10.41.228.71
Domain Nameservers:        127.0.0.1
Local Domain:              example.com
Timezone:                  PST
SMTP Host Name:            EXAMPLE.COM
Default RMT Tape:          MKB100:
Default TFTP Directory:    MULTINET_ROOT:[MULTINET.TFTP]
Anonymous FTP Directory:   USERS:[ANONYMOUS]
Load EXOS $QIO driver:     TRUE
Load UCX $QIO driver:      TRUE
WINS Compatibility:        TRUE
NET-CONFIG>
QUIT
$

 

 

 

 


 

SPAWN

Executes a single DCL command, or if entered without options, starts a subprocess with the same effect as PUSH. To return from DCL, use the LOGOUT command. If the MULTINET_DISABLE_SPAWN logical is set, SPAWN does not work.

 

FORMAT

SPAWN [command]

 

PARAMETERS

command

Specifies a command to execute. If you omit command, a DCL command line subprocess is created.

 

QUALIFIERS

/INPUT=file-spec

Specifies an input file to the command you enter with SPAWN.

 

/LOGICAL_NAMES
/NOLOGICAL_NAMES

Specifies that logical names and logical name tables are not copied to the subprocess.

 

/SYMBOLS
/NOSYMBOLS

Specifies that global and local names are not passed to the subprocess.

 

/WAIT
/NOWAIT

Returns control without waiting for the command to complete. Do not use this qualifier with commands that have prompts or screen displays.

 

/OUTPUT=file-spec

Specifies a file that retains the output of the command invoked with SPAWN. This qualifier only works when a single command is entered without creating a DCL subprocess. In addition, this qualifier is positional; you must enter it immediately after SPAWN or other qualifiers.

 

EXAMPLES

This example displays terminal information, captures the output in a file, then displays the information with the TYPE command.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>SPAWN/OUTPUT=FOO. SHOW TERM
NET-CONFIG>SPAWN TYPE FOO.
...

This example invokes a command procedure.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>SPAWN @COMPROC
...

This example displays help information about the NET-CONFIG utility. Use the LOGOUT command to return control to NET-CONFIG.

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>SPAWN RETURN
$ HELP MULTINET CONFIGURE /NETWORK_DEVICES
...
$ LOGOUT
NET-CONFIG>

 

 

 

 


 

STATUS

Displays the status of the current configuration.

 

FORMAT

STATUS

 

EXAMPLE

 

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>STATUS
There is the MultiNet network configuration program Version 5.6 (nnn)
There are 3/1024 devices in the current configuration.
There are 190/1024 devices in the MAXIMUM configuration.
The configuration MULTINET:NETWORK_DEVICES.CONFIGURATION is not modified.
The startup file MULTINET:START_MULTINET.COM is not modified.
NET-CONFIG>QUIT
$

 

 

 

 


 

USE

Reads in a configuration file. (Functionally equivalent to GET.)

 

FORMAT

USE config_file

 

PARAMETER

config_file

Specifies the name of the configuration file to read in.

 

 

 

 


 

VERSION

Displays the NET-CONFIG version and release information.

 

FORMAT

VERSION

 

EXAMPLE

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>VERSION
This is the MultiNet network configuration program Version 5.6 (nnn)
NET-CONFIG>QUIT
$

 

 

 

 


 

WRITE

Writes the current configuration to a file. (Functionally equivalent to SAVE.)

 

FORMAT

WRITE [config_file]

 

PARAMETER

config_file

Specifies the name of the configuration file to write out (by default, the same file from which the configuration was read).

 

EXAMPLE

$ MULTINET CONFIGURE /INTERFACE
MultiNet Network Configuration Utility 5.6 (nnn)
[Reading in MAXIMUM configuration from MULTINET:MULTINET.EXE]
[Reading configuration from MULTINET:NETWORK_DEVICES.CONFIGURATION]
NET-CONFIG>WRITE
[Writing configuration to MULTINET_ROOT:[MULTINET]NETWORK_DEVICES.CONFIGURATION.7]
NET-CONFIG>EXIT
[Writing configuration to MULTINET:NETWORK_DEVICES.CONFIGURATION]
[Writing Startup file MULTINET:START_MULTINET.COM]
[Changes take effect after the next VMS reboot]
$