Document ID: 15024
LAN²LAN Technical Bulletin #3
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
NetWare v2.x Token Ring Configurations
NETGEN/BRGEN
ROUTEGEN/INSTALL
NetWare v3.11 ISA Token Ring Configurations
NetWare v3.11 Micro Channel Token Ring Configurations
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
These considerations apply to the use of LAN²LAN with an IBM (or 100% compatible) Token Ring adapter.
The IBM Token Ring adapter uses shared RAM, which defaults to D800 for a primary adapter and D400 for an auxiliary adapter. When you perform NETGEN, ROUTEGEN, or BRGEN for a PC, which includes both a Token Ring adapter and one or more LAN²LAN cards, the Token Ring adapter is normally LAN A, Option 0. This reduces the configuration options available to LAN²LAN to those with RAM buffers at A000, 9000, A0000, or C0000 (the last two are in high memory).
If only one LAN²LAN is to be installed, you are able to use one of the available options. If your PC has a VGA adapter, then A000 is not available and you probably need to use D000 for LAN²LAN. If two or three LAN²LAN cards are installed in the same PC, it is usually best to assign the D000 RAM buffer to be used by all of the LAN2LANs by means of the shared RAM option. In these cases, Cisco recommends that you set the Token Ring adapter option to 8.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
NetWare v2.x Token Ring Configurations
NETGEN/BRGEN
When you perform NETGEN or BRGEN, the configuration options for the Token Ring adapter show two memory addresses. For example, Option 0 shows C800 and D800. The first address is that of the ROM of the adapter and the second address that of the shared RAM of the adapter. Option 0 is, in fact, the default for the Token Ring adapter.
If you use a Token Ring adapter in which the RAM address is set by software, you need to edit your CONFIG.SYS file. You should already have a line similar to this in the CONFIG.SYS file:
device=DXMC0MOD.SYS ....
This line loads the driver for the Token Ring adapter. Edit this line so that the second parameter is CC00 as shown in this example line for a primary adapter:
device=DXMC0MOD.SYS ,CC00
If this parameter is not set as shown, the adapter retains its default RAM address of D800, even though you selected Option 8 during NETGEN/BRGEN. This usually prevents correct operation of LAN²LAN.
ROUTEGEN/INSTALL
When you perform ROUTEGEN for NetWare v2.2, the Token Ring adapter is shown as self-configuring, even for an ISA bus. Before you run ROUTEGEN, you need to modify your ATOKENA2.OBJ, BTOKENA2.OBJ, CTOKENA2.OBJ and/or DTOKENA2.OBJ file(s) in the LAN_DRV_.001 directory in accordance to which driver(s) is/are to be used for Token Ring adapter(s). Change to the LAN_DRV_.001 directory and, if you use the A driver for your Token-Ring adapter, type:
TRCONFIG A
When prompted, if you wish to match the CONFIG.SYS entry previous shown, in order to change the shared RAM segment as required, enter:
MEMP=CC00
NetWare v3.11 ISA Token Ring Configurations
If you use NetWare v3.11 when you load the TOKEN.NLM, you must specify a RAM address such as this:
LOAD TOKEN MEM=CC000
NetWare v3.11 Micro Channel Token Ring Configurations
If you use NetWare v3.11 in a Micro Channel computer, the ROM and RAM addresses are set if you run the REFERENCE program. When the Reference program asks, Automatically configure the system? (Y/N), then answer (N) for No. You can now set both the ROM and RAM addresses.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for LAN |
| Network Infrastructure: LAN Routing and Switching |
| Network Infrastructure: Getting Started with LANs |
Related Information
- LAN Product Support Pages
- LAN Switching Support Page
- Technical Support & Documentation - Cisco Systems
| Updated: Jun 20, 2007 | Document ID: 15024 |
