
              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              Update of TCPIP.NLM and SNMP Agent
DOCUMENT ID:        TID000507
DOCUMENT REVISION:  A
DATE:               09AUG93
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         TCP162.EXE

NOVELL PRODUCT and VERSION:
TCP/IP 2.02

ABSTRACT:

This patch contains updates for both the TCPIP and SNMP NLMS.  It resolves
problems with FDDI frame types, crashes with the Compaq Prosignia computer and
Netflex card, and enables static subnet routing.

_________________________________________________________________

DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
_________________________________________________________________

Self-Extracting File Name:  TCP162.EXE

Files Included     Size     Date        Time

\
  TCP162.TXT          (This File)
AFTER311.NLM      11738   01-26-93      4:45p
FILEDATA.DAT       1851   05-12-93      2:42p
INSTRUCT.TXT       5147   07-27-93      3:34p
     PIN.DAT      43577   05-07-93      6:07p
PINSTALL.NLM      10344   05-07-93      6:07p
RELNOTES.TXT       1201   05-11-93      3:13p
    SNMP.CFG       1057   09-11-92     11:34a
    SNMP.NLM      57660   04-06-93      3:44p
TRAPTARG.CFG       1697   03-17-93     08:50a
\TCPIP\
IPCONFIG.NLM       8439   02-22-93     12:35p
   TCPIP.NLM     188964   07-12-93      5:11p


PURPOSE OF THIS PATCH
---------------------

This patch includes a version of TCPIP.NLM v2.02j. It includes the new,
extensible SNMP Agent (SNMP v2.08) and other supporting modules.

This version of TCPIP includes the following:

1.) This fixes the problem of NetWare 3.11 server abending when the hardware
platform is Compaq ProSignia and the Lan card is NetFlex when TCPIP v1.0 or
v1.01 is loaded.

2.) ARP packets transmitted on FDDI LANs will be sent with the Ethernet
hardware type (1) instead of the LLC 802.2 hardware type (6).  The TCPIP NLM
will accept ARP packets from FDDI LANs with either the Ethernet or LLC 802.2
hardware type. This change is to assure connectivity through translation
bridges.

3.) The TCPIP NLM will not force the TCP checksum field to FFFFh when the
checksum is calculated to be 0h.  This change provides compatability with
implementations that do not accept FFFFh interchangably with 0h in the
checksum field.

4.) This patch enables users to configure static subnet routing using the
/etc/gateways file. The usage instructions are given below.

WARNING:
--------

Do not install this patch unless you are currently using TCPIP version 1.0,
1.01, 2.02, 2.02h, or 2.02i.  Do not install this patch over TCPIP 2.02w or
higher.

!!CAUTION!!

      Please use the installation instructions in instruct.txt.

Do NOT install the TCP/IP NLM, IPCONFIG NLM, SNMP NLM, or the AFTER311 NLM
from the Upgrade diskette to a system on which MultiProtocol Router, WAN
Links, or MultiProtocol Router Plus has been installed.

Novell's MultiProtocol Router, WAN Links and MultiProtocol Router Plus
products already contain coordinated versions of the TCP/IP, IPCONFIG, SNMP,
and AFTER311 NLMs.  Installing this patch will overwrite the existing
MultiProtocol Router and WAN Links NLMs and will disable the routing.


Refer to the relnotes.txt file for Release Notes.

INSTALLATION:
-------------

1.) Copy the files into a subdirectory called SNMP_1. If the files are
compressed into a single file TCP162.ZIP, copy TCP162.ZIP into the
subdirectory and then decompress using the command PKUNZIP -d TCP162.  The -d
option will cause PKUNZIP to create the needed subdirectories.

If installation is from floppy disk, give the disk a label of SNMP_1.  Copy
the unzipped version of TCP162.ZIP to the disk.

2.) Follow the instructions in file INSTRUCT.TXT.


Configuring Static Subnet Routing:
----------------------------------

If you require static routes, you should indicate the static routes in the
SYS:\ETC\GATEWAYS file and then load the IPCONFIG NLM after you load the TCPIP
NLM and bind IP.

It is possible to do static routing as well as static subnet routing with this
version of IPCONFIG.NLM (v2.02) along with TCPIP (v2.02).

Format of SYS:ETC\GATEWAYS
--------------------------

Each line in SYS:ETC\GATEWAYS has the following format:


{NET network_name | {network_number[/network_mask]} | HOST host}
    GATEWAY gateway [METRIC cost]  [ {ACTIVE | PASSIVE } ]

where:

The network_name is the name of a network in SYS:ETC\NETWORKS.

The network_number/network_mask is the IP network address and its subnet mask;
the subnet mask is optional.  If the network_mask is not specified, the subnet
mask is derived from the network number, excluding all trailing zeros.

The host is the IP address of a host or the name of a host in SYS:ETC\HOSTS.

The gateway is the IP address of a gateway on a locally connected network or
the name of such a gateway in SYS:ETC\HOSTS.

The cost, or measure of expense, is a value greater than or equal to 1 but
less than or equal to 15.

The active or passive indicates the type of route for routing information.

For example:

NET 2.0.0.0 GATEWAY 193.1.1.1

HOST 129.1.0.3 GATEWAY 193.1.1.1 PASSIVE

NET 130.57.1.0/255.255.255.0 GATEWAY 193.1.1.1 PASSIVE

Loading the IPCONFIG NLM
------------------------

To add the static routes in SYS:ETC\GATEWAYS to the routing database, you must
load the IPCONFIG NLM.  This can be done by entering the LOAD IPCONFIG command
at the system console.  Normally,  you place this command in your
SYS:SYSTEM\AUTOEXEC.NCF file after loading tcpip and binding IP to interfaces
so that the static routes are added  each time the system is loaded.

The command is as follows:

LOAD IPCONFIG

NOTE:  If you do not have any static routes to configure, you do not need to
load IPCONFIG.

IPCONFIG reads SYS:ETC\GATEWAYS, places each route into the routing database,
and then exits.  While you are "debugging" your GATEWAYS file, problems in the
file may cause IPCONFIG to print diagnostic messages.

For each route IPCONFIG finds in SYS:ETC\GATEWAYS, IPCONFIG adds a routing
entry for the host or network indicated.  The first hop in the new routing
entry is the provided gateway and the metric is the given cost.  If no metric
is given, a cost of 1 is used.

IPCONFIG will support a static subnet route if the subnet mask is associated
with the subnetwork number in /etc/gateway.

Placing the keywork active on the line indicates that the route is maintained
by the indicated gateway using normal RIP updates.  Active routes are subject
to normal RIP rules.  They may be replaced by routes with lower metric values
and they time out and disappear if no RIP updates are received for them.

The keyword passive, which is the default if neither active nor passive is
specified, indicates a route for which no RIP information will ever be
available.  Such routes never time out and IP ignores RIP information for
them. They can be deleted or modified using TCPCON.
