Ref: 99980866
Title: SW/IVECS-TCP Version 13010
Date: 3/12/87

Copyright 3Com Corporation, 1991.  All rights reserved.

Part Number: 86-0089-00
Revision 01

Overview

Integrated VAXTM Ethernet Communications Server (IVECS) is a
single board that allows a VAX running the VMSTM, UNIXTM 4.2 BSC,
or UltrixTM operating system to attach directly to an Ethernet
Local Area Network (LAN). IVECS permits up to 48 connections to
the VAX over the Ethernet.

Connections to IVECS can be made from the Bridge CS/1, CS/100,
CS/200, LS/1 servers with TCP/IP, from another IVECS, or from a
PC running TCPTerm either on the same network or via the Bridge
GS/3-IP, IB/1 or IB/2 server.

The IVECS operating software is fully compatible with all other
Bridge products that utilize the Transmission Control
Protocol/Internet Protocol (TCP/IP). Operating software for IVECS
is loaded from a Bridge Network Control Server/150. IVECS
supports the audit trail service, which gathers and records
session information such as connections attempted, whether
successfully completed, unsuccessful, or disconnected.

IVECS uses a 12 MHz 68000 processor and 1M bytes of memory. In
addition, a LANCE chip Ethernet Controller and 2901-based
micromachine are embedded in IVECS.

.h1;Installing Software on the NCS/150

If the NCS/150 is running SW/150-NCS-TCP, use the follow
procedure to copy the SW/IVECS-TCP Version 13010 software image
onto the SW/150-TCP-NCS diskette:

1.  Connect a terminal to port of the NCS/150.

2.  Insert the SW/150-TCP UTL diskette in the NCS/150 disk drive,
then press the Reset switch.  After the NCS/150 is finished
booting, press the following sequence on the keyboard:

<RETURN>.<RETURN>

3.  Remove the SW/150-TCP UTL diskette, insert the SW/150-NCS-TCP
diskette in the disk drive and enter the following command:

ls -lx /BIN

This command displays the contents of the software image
currently available on the diskette. The NCS/150 can only support
up to two products (cs1x, cs100x, cs200x, ivecsx).  If two
products are bound to the NCS/150, one of them must be removed;
then proceed to step 4. To remove the software image, use the
following command:

rm <filename>

4.  Create an IVECS file on the SW/150-NCS-TCP using the
following command:

cr /BIN/ivecs 140 rwx 508000

5.  To copy the software image from the SW/IVECS-TCP Version
13000 diskette to the SW/150-NCS-TCP diskette, enter the
following command:

cp #0 /BIN/ivecsx

When the system prompts for the master diskette, insert the
SW/IVECS-TCP Version 13010 diskette and press the return key.

When the system prompts for the destination diskette, insert
the SW/150-NCS-TCP diskette.

The copy process may go through several passes.

6.  Bind the IVECS to the NCS/150 using the following command:

BInd <Ethernet address> <Internet address> "ivecsx" 48
After the BInding process, the new "config" file with 48
configurations is created.

If the NCS/150 is running SW/150-NCS (XNS) and the software image
in it is SW/IVECS-A (XNS), use the following procedure to
transfer the configurations, global parameter, and macros from
the XNS system to TCP/IP system:

1.  Follow steps 1 through 6 in the previous procedure to copy
the SW/IVECS-TCP Version 13010 software to SW/150-NCS-TCP
diskette.

2.  To transfer the configurations, global parameter, and macros
from the XNS system to TCP/IP system, follow these steps:

a)  As a result of the BInd command as described in step 6 of
the previous procedure, a configuration file and globals
file for the client server will be created. The NCS/150
running SW/150-NCS-TCP names the configuration file
cfg.hhhhhhhh and the globals file gb1.hhhhhhhh, where
hhhhhhh is the 8-digit hexadecimal representation of the
client server's Internet address.

To find out the configuration file name for the IVECS,
enter the following command:

ls /CONFIGS

This command lists the configuration file name for the
TCP/IP IVECS as follows:

CONFIGS/cfg.hhhhhhhh

To find out the globals file name for the IVECS, enter
the following command:

ls /GLOBALS

This command lists the globals file name for the TCP/IP
IVECS as follows:

GLOBALS/gbl.hhhhhhhh

b)  Insert the SW/150-NCS (XNS) diskette in the disk drive
and press the Reset switch.  Rename the current
configuration file as follows:

cp /CONFIGS/configs.xxxx /CONFIGS/cfg.hhhhhhhh

Similarly, to rename the current globals file, use the following
command:

cp /GLOBALS/globals.xxxx /GLOBALS/gbl.hhhhhhhh

where xxxx is the last four digits of the IVECS's Ethernet
address, cfg.hhhhhhhh is the configuration file name, and
gbl.hhhhhhhh is the globals file name created by the BInd command
as described above.

c)  Boot the SW/150-TCP UTL diskette.

d)  To copy the configuration file from SW/150-NCS (XNS) to SW/
150-NCS-TCP, enter the following command:

cf /CONFIGS/cfg.hhhhhhhh

When the system prompts for the source diskette, insert the SW/
150-NCS (XNS) diskette and press the return key.

When the systemp prompts for the destination diskette, insert the
SW/150-NCS-TCP diskette and press the return key.

Similarly, to copy the globals file from SW/150-NCS (XNS) to SW/
150-NCS-TCP, enter the following command:

cp /GLOBALS/gbl.hhhhhhhh

When the systemp prompts for the source diskette, insert the SW/
150-NCS (XNS) diskette and press the return key.

When the system prompts for the destination diskette, insert the
SW/150-NCS-TCP diskette and return key.

e)  To copy the macros file from SW/150-NCS (XNS) to SW/150-
NCS-TCP, enter the following command:

cp macros

When the system prompts for the source diskette, insert
the SW/150-NCS (XNS) diskette and press the return key.

When the system prompts for th destination diskette, insert the
SW/150-NCS-TCP diskette and press the return key.

Due to the differences in naming and addressing conventions
between XNS and TCP/IP, when copying a macros file from SW/150-
NCS to SW/150-NCS-TCP, perform the following steps:

+ If a macro references clearinghouse names, after converting
from XNS to TCP/IP, the same name should be used to redefine name
servers in the TCP/IP system.

+ If a macro references Ethernet addresses, after converting from
XNS to TCP/IP this macro should be redefined to contain Internet
addresses.

+ Some commands in the XNS system are not applicable in the TCP/
IP system. When such commands are embedded in the macros, these
macros should also be redefined to avoid "illegal command"
messages.

.h1;Features

SW/IVECS-TCP Version 13010 has the following features:

1.  Permant Virutal Circuits (PVCs) is supported. Permanent
Virtual Circuits allow automatic circuit reestablishment upon
disconnection.

Once a permanent virtual circuit is defined, it will be
reestablished whenever the server is rebooted. After the
PermanentVC parameter is set, the first connection attempt
will begin in approximately 30 seconds.  If the connectiona
attempt fails or if the permanent virtual circuit is
disconnected for any reason, the system will attempt to
reestablish the circuit every 60 seconds. PVCs can only be
defined on a host port.  The destination end of the
connection can be either a terminal or host port. The PVC may
be defined on both ends of the circuit. In addition, PVCs may
accept names.

Permanent VC commands have the following syntax:

- SETDefault (!portid) PermanenetVC="<address>"

Defines a permanent virtual circuit between a local host
port and any port on the network. <address> can be either
a physical address or a name. The name can be up to 12
characters long.

- SETDefault (!portid) PermanentVC=""

Removes any previous PVC definition, but does not
disconnect any existing connection. The existing circuits
can be disconnected using the DisConnect of Listen
command.

- SHow (!portid) DefaultParameter PermanentVC

Displays the current permanent virtual circuit for
portid.

2.  The ARP-based routing has been improved. When a packet is
transmitted to a destination with a different network number
in its address, an initial route is set up using the default
gateway. If the default gateway is zero when such an initial
transmission is made, SW/IVECS-TCP Version 13010 will attempt
to resolve the address on the local segment via an ARP
request.

3.  Macros can now be defined when remote to the IVECS by using
the DEFine command. However, the macro prompt will not
appear. Each command in the macro except the last command
must end with a backslash ().

Example:

ivecs prompt# DEFine macroname = (\ command 1 \ command 2 \
  . \ . \ ) ivecs prompt#


.h1;Corrections in the  IVECS INSTALLATION GUIDE

Due to a memory limitation in SW/IVECS-TCP Version 10030.

Table 3-4 on page 3-10 of the  IVECS Installation Guide
should be as follows:

______________________________________________________________________________________________________________________________
|                                       Table 3-4 Maximum Recommended Number of DMF32s                                        |
|                                                   to be Emulated by IVECS                                                   |
|_____________________________________________________________________________________________________________________________|
|  VAX Type                                                 DMF32s to be Emulated                                             |
|                                                                                                                             |
|  11/780 &     10 total:   6 on one IVECS and 4 on the second IVECS                                                          |
|  11/785                                                                                                                     |
|                                                                                                                             |
|  11/750       6                                                                                                             |
|  11/730       2                                                                                                             |
|_____________________________________________________________________________________________________________________________|

In Table 4-6 on page 4-27 of the same manual, the DMF32 board shorting
plug positions should be configured as follows:

 ________________________________________________________
|                                                        |
|________________________________________________________|
|                                                        |
| Number of DMF32 Boards           Shorting Plug         |
|                               3-4              5-6     |
|    2                          In               In      |
|    4*                         Out              In      |
|    6                          in               Out     |
|                                                        |
|________________________________________________________|

.h1;Limitations

SW/IVECS-TCP Version 13010 has the following limitations:

1.  SW/IVECS-TCP Version 13010 supports no more than 48 sessions.

2.  Internet addresses can only be defined for rotary ports.  In
order to establish a connection to the IVECS, virtual ports
should be grouped in the rotary and an Internet address will
then be assigned to the rotary using the command described in
the USER INTERFACE section.

3.  In order to use the local floppy as the Name Server's address
database, the primary Name Server's address must be defined
as that unit's Internet address.

4.  IVECS with TCP/IP can emulate up to 6 DMF32s.

.h1;User Interface

SW/IVECS-TCP Version 13010 has the following user interface
commands:

- SETDefault (!<port-id>) Internet Port = <Internet address>

Assigns Internet addresses to rotary ports.

- SETDefault (!<port-id>) InternetPort = 0.0.0.0

Removes the Internet address of a rotary port.

- SETDefault DefaultGateway = <Internet address>

Allows all remote net packets to be sent to the gateway.

- SETDefault PrimaryNameServer = <Internet address>

Assigns an Internet address for the primary Name Server.  The
Primary Name Server will be queried first for name resolution.
The primary Name Server's Internet address can be defined to be
on a remote network.

- SETDefault SecondaryNameServer = <Internet address>

Assigns an Internet address for the secondary Name Server.  The
secondary Name Server will be queried if the primary Name Server
does not yield a name to address resolution.
