Cisco LAN2LAN Software

Document ID: 15007

Contents

Introduction
Prerequisites
      Requirements
      Components Used
Information
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

LAN²LAN for NetWare platforms v3.0 and later allow for support for multiple protocols between two NetWare v3.11 or later servers. Note that with this release of software you need to LOAD and BIND logical drivers for each line/rotary group even if IPX is the only protocol required.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

Information

The LAN²LAN MLID registers an arbitrary frame type and assigns these protocol IDs:

Table: Frame Type and Protocol
------------------------------
IPX                 8137
==============================
IP                  800
ARP                 806
APPLETALK           80007809B
APPLETALK ARP       80F3
------------------------------

LAN²LAN passes the protocol ID supplied by LSL for each packet across the communications link and gives it to the receiving LSL. This lets multiple protocols share the LAN²LAN communications link.

The LAN²LAN NLM load commands should be structured to create an instance of the driver for each line (or rotary group).

The LOAD command for LAN²LAN has one custom parameter. The PACKET= parameter is optional and is used to set the maximum packet size to be used on connections over the communications links.

When a LOAD command is issued, a name must be assigned to the logical board so that the logical driver is associated with a line and so that the BIND command can uniquely reference each logical board.

A naming convention has been adopted to inform the driver which line(s) this logical board is to service. These are examples of this naming convention:

1. NAME=P258L1 -- service link 1 on the board with port address 258.

2. NAME=P298L34 -- service links 3 and 4 as a rotary on the board with port address 298. The format for naming must be followed exactly to ensure correct operation.

These example commands activate a single LAN²LAN line, on the adapter whose port address is 258, with IPX, AppleTalk, and IP protocols:

LOAD LAN2LAN port=258 int=5 mem=D000 NAME=P258L1
  BIND IPX TO P258L1 net=fd0001
  BIND APPLETLK TO P258L1 net=6000-6049 zone={"NSS","NSS2"}
  BIND IP TO P258L1 addr=89.1.1.3

This example presents a more complex set of LOAD and BIND commands. This set applies to a single LAN²LAN with links 1 and 2 in rotary and links 3 and 4 operating independently:

LOAD LAN2LAN port=258 int=5 mem=D000 NAME=P258L12
  LOAD LAN2LAN NAME=P258L3
  LOAD LAN2LAN NAME=P258L4
  BIND IPX TO P258L12 net=fd0001
  BIND IPX TO P258L3 net=fd0002
  BIND IPX TO P258L4 net=fd0003
  BIND IP TO P258L12 addr=89.1.1.3
  BIND IP TO P258L3 addr=89.1.1.4
  BIND IP TO P258L4 addr=89.1.1.5
  BIND APPLETLK TO P258L12 net=50-100 zone={"Newport"}
  BIND APPLETLK TO P258L3 net=101-150 zone={"Newport"}
  BIND APPLETLK TO P258L4 net=151-200 zone={"Newport"}

The first LOAD command establishes the physical board and its associated port, IRQ, and RAM buffer to service lines 1 and 2 as a rotary. The second and third LOAD commands add lines 3 and 4 to this physical board. The root part of the names (P258_the board's port address) for these commands must correspond to that used for the first load command.

Note that each line or rotary group is now given a different IPX network number, contrary to previous practice. This network number must, of course, correspond to that assigned at the other end of the link or rotary group. The driver checks that links described as rotary are indeed terminated at the same remote LAN²LAN and gives a message similar to the following if a discrepancy is noted:

LAN2LAN boardname - link12 is not a rotary

A side effect of this change is that each LAN²LAN logical board has its own configuration table and statistics table. Surveyor and other network managers see each LAN²LAN logical board as a separate physical board. The name of the board as used in the LOAD and BIND commands are included in the Surveyor Drivers menu to help you select the correct driver. Selection of custom line statistics is similar to the current method. Except in the case of rotaries, only one line can be displayed per driver.

NetPro Discussion Forums - Featured Conversations

Related Information

• Technical Support & Documentation - Cisco Systems