Document revision date: 19 July 1999

The InfoServer system automatically serves its locally connected devices to clients when the server is first powered on or when a removable device (for example, a compact disc) is inserted into a drive. The server reads the volume label of each device and uses the label as the name of the service offered to clients.

If multiple servers offer the same services, the client uses a rating scheme to select the appropriate service. Refer to the CREATE SERVICE command description in the InfoServer System Operations Guide for more information.

When you remove a compact disc from a server drive, the InfoServer system ends all client connections to the associated service. The InfoServer system also stops offering the associated service to client systems.

23.1.2 High-Availability Feature to Reduce Service Interruptions

The InfoServer system provides a high-availability feature that is especially beneficial for OpenVMS clients. If the server ends a service connection for some reason (for example, the server reboots, or you remove a compact disc), the OpenVMS client enters mount verification for that volume. If the same service is offered by another InfoServer system on the LAN, the client automatically connects to that service.

For example, suppose you have two identical copies of the OpenVMS Online Documentation compact disc in drives on two different servers. If one server or drive fails, a new connection is established to the duplicate disc on the other server. File operations continue as normal, and users experience almost no service disruption.

23.1.3 Support for X Terminal Clients

X terminal clients use the InfoServer system to download their system software, provide font services, save configuration information, and page memory to and from InfoServer disks. For example, system files for Compaq's VXT 2000 windowing terminals can be installed from compact disc on the InfoServer system. Once installed, these files are downline loaded on demand to each terminal when it is powered on.

The terminals can dynamically allocate partitions on an InfoServer disk as needed. For example, when a user requests that terminal customizations be saved, the InfoServer system automatically creates a disk partition to hold the information and creates a network service name for that partition. Once customization information is saved, the user can recall the information at any time.

VXT 2000 terminals that are InfoServer clients can also be virtual memory machines. Such terminals can page sections of main memory to and from InfoServer disks as required. Because a VXT client has no local disk, it uses InfoServer disks as page disks. When main memory is paged out to disk, the VXT client requests the InfoServer system to create a partition. This partition is then automatically extended as needed. Partitions and their network service names are created dynamically, without requiring user action.

By default, the InfoServer disk DK1, which is the internal disk that ships with each InfoServer 150 system, is enabled to allow VXT 2000 clients to allocate partitions remotely. Other disks can also be enabled through the use of InfoServer commands.

23.2 Understanding LASTport Protocols

The InfoServer system uses the LASTport transport protocol and the LASTport/Disk and LASTport/Tape system application protocols to provide access to the virtual devices it serves to the LAN. These protocols provide high-performance access to disk and tape devices. The InfoServer system implements the server portion of the protocols, while the client systems that access InfoServer storage devices implement the client portion.

On OpenVMS systems running the LASTport transport, all Ethernet devices must be terminated either by attaching the devices to an active network or by using an appropriate terminator. Failure to terminate the devices causes a system crash.

23.2.1 LASTport Transport Protocol

The LASTport protocol is a specialized LAN transport protocol that allows many clients to access InfoServer systems and perform reliable transactions. For the InfoServer system, a transaction is a device read or write operation. The LASTport protocol allows many client systems concurrently to read information from, and and write information to, an InfoServer storage device.

Unlike timer-based protocols, the LASTport protocol is a transaction-oriented protocol. Normally, information does not pass between a client and an InfoServer system unless the client initiates a transaction. The client system then runs a timer on the transaction, normally waiting from two to five seconds before assuming that the transaction is lost and retrying the operation.

The LASTport protocol does not provide any routing functions; it runs only in a LAN. The LASTport protocol type is 80--41. If the extended LAN uses any filtering devices, the devices must allow this protocol type to pass unfiltered so that clients can access InfoServer systems across the filtering device.

The InfoServer system uses a multicast address feature of the LASTport protocol to establish connections to devices. The format of the multicast address is 09--00--2B--04--nn--nn, where nn depends on the work group enabled (refer to the InfoServer System Operations Guide).

23.2.2 LASTport/Disk Protocol

The LASTport/Disk protocol is a specialized device protocol that uses the LASTport transport. That is, LASTport/Disk messages are delivered in LASTport messages. The LASTport/Disk protocol provides the mechanism for reading and writing logical blocks independent from any underlying file system. The clients that implement the LASTport/Disk protocol interpret the file system locally. By using the LASTport/Disk protocol for access to compact discs and read/write disks, the InfoServer system can support multiple client operating systems and on-disk structures concurrently.

The LASTport/Disk protocol also provides the naming facility to access compact discs and read/write disks. The InfoServer system assigns each virtual device a service name and allows clients to query the LAN for these names. When the requested service is found, the client connects to it, and device access can begin. When duplicate virtual devices are available under identical service names, the protocol provides a facility for load balancing among the available devices.

23.2.3 LASTport/Tape Protocol

Like the LASTport/Disk protocol, the LASTport/Tape protocol uses the LASTport transport. That is, LASTport/Tape messages are delivered in LASTport messages. The LASTport/Tape protocol provides the mechanism for reading and writing tape records. Tape devices attached to the InfoServer system appear to tape clients as locally attached devices.

The LASTport/Tape protocol also provides the naming facility to access tapes. The InfoServer system assigns each tape device a service name and allows clients to query the LAN for these names. When the requested service is found, the client connects to it, and tape access can begin.

23.3 Establishing a Server Management Session

You can establish a server management session from a local or remote console terminal:

• For a local session, you connect a terminal capable of interpreting VT100 ANSI escape sequences to the serial port on the rear of the InfoServer system unit (MMJ1 on the InfoServer 150 unit). The terminal must be set to 9600 baud, 8 bits, no parity.
• For a remote session, you make a connection to the InfoServer system through a local area terminal (LAT) server.
  Like many network servers, the InfoServer system advertises a LAT service for its management interface and accepts connections from remote terminals attached to terminal servers. Therefore, any terminal attached to a terminal server on the extended LAN can act as a console terminal for the InfoServer system (if the user knows the InfoServer management password).

Determining the Server's Default Service Name

To make a remote connection to the InfoServer system for the first time, you must determine the server's default name. To do this, add the four-character prefix LAD_ to the hexadecimal Ethernet datalink address on the InfoServer system's cabinet. You can change this default name by using the InfoServer command SET SERVER NAME.

The server's name is the LAT service name to which you connect. For example, if the default server name is LAD_08002B15009F, you would enter the following command at the terminal server's prompt to manage the InfoServer system:

Local> CONNECT LAD_08002B15009F

Refer to your terminal server user's guide for information about the establishment of LAT service connections.

Entering an InfoServer Password

After you connect to the InfoServer system, you must enter an InfoServer password to establish the management session. The default server password is ESS. You can change the password with the InfoServer command SET SERVER PASSWORD.

Example

The following example shows the establishment of a sample session using a DECserver 500 terminal server:

Local> CONNECT LAD_08002B133C1C Password: ESS (not echoed) Local -010- Session 1 to LAD_08002B133C1C established DEC InfoServer V3.1 InfoServer> SHOW SERVER

In this example, the terminal server's prompt is Local>, and a LAT session is established to the InfoServer system whose service name is LAD_08002B133C1C. The InfoServer system prompts for a server password. When you enter the correct password, the server prompts for InfoServer commands with the InfoServer> prompt.

Ending a Session

At the end of the management session, you can enter the EXIT command at the InfoServer> prompt. This command returns you to the terminal server's Local> prompt if the management session is over a LAT connection.

23.3.1 Server Management Commands

Table 23-1 summarizes InfoServer commands and their functions.

Table 23-1 Summary of InfoServer Commands

Command	Function
BACKUP	Saves InfoServer-formatted disks.
BIND	Establishes a connection to the specified ODS-2 service and creates the virtual device VDK1 for that service.
CLEAR	Erases the console terminal screen.
COPY	Copies data from one disk or partition to another.
CRASH	Causes the server software to take a recognizable bugcheck, creating a dump if crashdump processing is enabled.
CREATE	Creates a new partition or service.
DELETE	Deletes a partition or service that was previously created.
DISCONNECT	Terminates a LASTport or LAT terminal server session.
ERASE	Erases the specified disk or partition; erases FUNCTIONS or SERVICES data from nonvolatile random-access memory (NVRAM).
EXIT	Terminates the management session.
HELP	Displays help text for the InfoServer commands.
INITIALIZE	Formats a read/write disk into an InfoServer disk.
LOOP	Automatically repeats any valid InfoServer command.
MONITOR	Automatically repeats valid InfoServer commands every 3 seconds, clearing the screen and placing the cursor at the home position.
PURGE	Purges old versions of VXT software.
REBOOT	Shuts down and reboots the server.
RECORD	Records data from an InfoServer disk or partition to a compact disc.
RESTORE	Resets the server to a previously saved system configuration.
RETRIEVE	Restores InfoServer-formatted disks saved by the BACKUP command.
REWIND	Rewinds an InfoServer tape.
SAVE	Saves configuration and service data for recovery after a server reboot.
SET	Sets partition, service, or server parameters.
SHOW	Displays the server's parameters and counters.
UNBIND	Deletes the VDK1 virtual device and terminates the connection to the remote service.
UNLOAD	Rewinds and unloads an InfoServer tape.
UPDATE	Installs one or more new software products or functions.
VERIFY	Validates the on-disk structure of a device formatted with the INITIALIZE command.
ZERO	Sets internal server counters to 0.

The InfoServer system provides a Help facility that contains information about each server command, including parameters, qualifiers, and examples of its use. For detailed information about InfoServer commands, refer to the InfoServer System Operations Guide.

23.4 Understanding InfoServer Client for OpenVMS Functions

InfoServer Client for OpenVMS software enables clients running the OpenVMS operating system to access virtual device services offered by InfoServer systems on a LAN. Software components include the following ones:

• LASTport driver
  The LASTport driver provides reliable data transfer services for its clients. It interacts with the Data Link driver and the LASTport/Disk driver as an efficient transport for a virtual device service. The LASTport driver can support other applications, such as a primitive data queeing service.
• LASTport/Disk client driver
  The LASTport/Disk client driver presents a standard block device interface to the system. The OpenVMS file system interacts with the LASTport/Disk client as if the LASTport/Disk client were a local disk driver. The LASTport/Disk client driver supports both raw and buffered interfaces.
• LASTport/Tape client driver
  The LASTport/Tape client driver enables OpenVMS clients to access and use as local devices SCSI tapes attached to InfoServer systems.
• LASTCP and LADCP utilities
  These utilities allow you to start InfoServer Client software on your system, monitor transport status, and configure and maintain InfoServer device services. Section 23.5 and Section 23.6 introduce the utilities. For complete information about the utilities, refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.

InfoServer Client for OpenVMS software uses the LASTport protocol to communicate with InfoServer systems on an extended LAN. The protocol is implemented in the OpenVMS device driver ESS$LASTDRIVER.

The LASTport Control Program (LASTCP) utility is the management interface that allows you to control and diagnose ESS$LASTDRIVER. You can use LASTCP to perform the following tasks:

• Start and stop ESS$LASTDRIVER
• Display counters for circuits, lines, nodes, and ESS$LASTDRIVER
• Display node characteristics
• Display known clients and servers
• Display LASTport status
• Reset counters

The description of the LASTCP utility covers the following topics:

• Invoking and exiting the utility
• LASTCP command summary
• Starting InfoServer Client for OpenVMS software automatically

Use of LASTCP requires normal privileges, except where noted. To invoke LASTCP, enter the following command:

$ RUN SYS$SYSTEM:ESS$LASTCP %LASTCP-I-VERSION, ESS$LASTDRIVER V1.5 is running LASTCP>

At the LASTCP> prompt, you can enter LASTCP commands. To exit the utility, enter EXIT or press Ctrl/Z at the LASTCP> prompt.

You can also execute a single LASTCP command by using a DCL string assignment statement, as shown in the following example:

$ LASTCP :== $ESS$LASTCP $ LASTCP SHOW CLIENTS

LASTCP executes the SHOW CLIENTS command and returns control to DCL command level.

23.5.2 LASTCP Command Summary

Table 23-2 summarizes LASTCP commands and their functions.

Table 23-2 Summary of LASTCP Commands

Command	Function
EXIT	Returns the user to DCL command level
HELP	Displays HELP text for LASTCP commands
SHOW CIRCUIT COUNTERS	Displays circuit counters
SHOW CLIENTS	Displays known clients
SHOW LINE COUNTERS	Displays line counters
SHOW NODE CHARACTERISTICS	Displays node characteristics
SHOW NODE COUNTERS	Displays node counters
SHOW SERVERS	Displays known servers
SHOW STATUS	Displays local status
SHOW TRANSPORT COUNTERS	Displays transport counters
START TRANSPORT	Starts LASTDRIVER
STOP TRANSPORT	Stops LASTDRIVER
ZERO COUNTERS	Resets counters

You can abbreviate LASTCP commands to the first unique characters of the command verb. For example, you can abbreviate the command SHOW SERVERS to SH SE.

LASTCP provides a Help facility that contains information about each command and its parameters and qualifiers, as well as examples of its use. For a complete description of LASTCP commands, refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.

23.5.3 Starting InfoServer Client for OpenVMS Software Automatically

You must start InfoServer Client for OpenVMS software using the ESS$STARTUP command procedure. To make sure the software is started automatically each time the system reboots, execute the startup procedure from within SYSTARTUP_VMS.COM.

How to Perform This Task

1. Determine the value of SCSNODE, your system's node name parameter. If the parameter is defined as the null string (the default value), InfoServer Client for OpenVMS software does not start.
   If you are running or plan to run DECnet for OpenVMS, SCSNODE must be defined as the system's DECnet node name. If you do not plan to run DECnet, and if the system is an OpenVMS cluster member, SCSNODE must be defined as the SCS system name, a 1- to 8-character node name that is unique in the cluster.
   To determine the value of SCSNODE, enter the following commands to invoke SYSMAN and display the parameter:

   $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SHOW SCSNODE

2. If SCSNODE is defined as the null string, perform these steps:
   1. Enter a command in the following format, where node-name is the system's DECnet node name or (if you do not plan to run DECnet for OpenVMS) the SCS system name:

      PARAMETERS SET SCSNODE "node-name"

      
      For example:

      SYSMAN> PARAMETERS SET SCSNODE "MYNODE"

   2. Enter the following commands to write the new value to the parameter file and exit from SYSMAN:

      SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT

   3. Add a line in the following format to the AUTOGEN parameter file SYS$SYSTEM:MODPARAMS.DAT to define the SCSNODE parameter:

      SCSNODE = "node-name"

      
      For example:

      SCSNODE = "MYNODE"

3. Invoke any editor to edit SYS$MANAGER:SYSTARTUP_VMS.COM and find the command that starts InfoServer Client software. For example:

   $ @SYS$STARTUP:ESS$STARTUP DISK

   
   Note that the parameters CLIENT and DISK are synonymous. If the command is preceded by the DCL comment delimiter (!), remove the delimiter. To enable tape functions, add the TAPE parameter to the command line:

   $ @SYS$STARTUP:ESS$STARTUP DISK TAPE

4. If SYSTARTUP_VMS.COM invokes the DECnet for OpenVMS startup procedure (SYS$MANAGER:STARTNET.COM), make sure SYSTARTUP_VMS.COM executes the InfoServer Client for OpenVMS startup procedure after invoking STARTNET.COM.
   The following example shows the network startup command line followed by the InfoServer Client for OpenVMS startup command line. Note that if you omit the TAPE parameter, only the disk function is started.

   $ @SYS$MANAGER:STARTNET . . . $ @SYS$STARTUP:ESS$STARTUP DISK TAPE

5. Optionally, edit the file SYS$STARTUP:ESS$LAST_STARTUP.DAT to specify desired startup qualifiers for the LASTport transport. (Refer to the InfoServer Client for OpenVMS LASTCP and LADCP Utilities manual.)

	privacy and legal statement
6017PRO_095.HTML