Document ID: 15009
Contents
Introduction
Prerequisites
Requirements
Components Used
Upgrade Information
Related Information
Introduction
This document discusses an upgrade from LAN2LAN Version 2.x to 3.0 in a 3.11 Server.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Upgrade Information
If you upgrade LAN²LAN for NetWare platforms from earlier versions to version 3.0 in a NetWare v3.11 server and you use more than one line on the LAN²LAN, you need to make a few changes. These changes let LAN²LAN support multiple protocols.
Refer to the LAN²LAN for NetWare Platforms User's Guide for further explanation.
First, you must include a LOAD and a BIND command for each communications port (line) that you intend to use. If you plan to use multiple protocols, then you must BIND each protocol to each line over which you intend to route that protocol.
Secondly, each IPX BIND must declare a different network address. Previously all lines on a LAN²LAN were required to have the same IPX network address (When installed in a v2.x server/router, they still do). This has an effect on the connected routers/servers, whether they are v2.15 or v3.11, since the network address at each end of the line must be the same. If you use v2.x servers or routers and find it necessary to change the address, then the NetWare utility DCONFIG eases this chore. You should also follow the proper naming convention so that the software associates the correct network addresses with the intended ports.
In summary, in the first LOAD command for a particular LAN²LAN adapter, you include a "NAME=PpppLn" statement. Where ppp is the base I/O address of the adapter and n is the port number. For example, P258L1. (If you were loading LAN²LAN for a two-line rotary group, the name might be P258L12, if ports 1 and 2 were in rotary.)
When you load the second line in the same LAN²LAN adapter, you do not need to specify the "port=", "int=" and "mem=" parameters again, since the suffix of the NAME=P258L2 used in this LOAD command associates the lines for the LAN²LAN driver.
When you BIND protocols to the particular line or rotary group, use the assigned name to identify the binding, as in this example:
load LAN2LAN port=258 mem=D0000 int=5 NAME=P258L1 load LAN2LAN NAME=P258L2 bind IPX to P258L1 net=FACE01 bind IPX to P258L2 net=FACE02
Related Information
| Updated: Oct 06, 2005 | Document ID: 15009 |