THE DOS ODI2NDI MODULE ______________________ OVERVIEW ________ The DOS ODI2NDI Module was developed to provide Novell DOS Workstation support for IBM NDIS MAC Driver Adapters. ODI2NDI is a transparent link between the Netware Link Support Layer (LSL) and the NDIS MAC Driver. That is, to the NDIS MAC Driver, ODI2NDI is an Network Device Interface Specification (NDIS) Protocol Stack, and to the Netware LSL, ODI2NDI is an Open Data-Link Interface (ODI) MAC Driver. ODI2NDI allows coexistence for Netware and other NDIS Protocol stacks. ODI2NDI CONFIGURATION _____________________ ODI2NDI is a Terminate and Stay Resident (TSR) program. ODI2NDI is sensitive to the order in which Netware and NDIS modules are loaded. NDIS modules (with the excep- tion of NETBIND) are device drivers that are loaded during config.sys processing. The Netware Requestor modules are TSR programs that are loaded either during autoexec.bat processing or following autoexec.bat processing. Therefore, the NDIS modules are loaded prior to ODI2NDI (again, with the exception of NETBIND) and the Netware Workstation modules. LOAD ORDER ODI2NDI has a REQUIRED load order with respect to the Netware Requestor modules and the NDIS NETBIND. It must be loaded after the Netware LSL.COM, and before the NDIS NETBIND, ROUTE.COM and IPXODI.COM. In addition, the NETBIND must be loaded prior to the IPXODI.COM. For example: LSL.COM ODI2NDI.COM NETBIND.COM ROUTE.COM (For Token Ring Source Routing) IPXODI.COM NETX.COM CONFIGURATION PARAMETERS ODI2NDI has no command line parameters but supports three NET.CFG keywords and five PROTOCOL.INI keywords. NET.CFG is the configuration file for the Netware Requestor envi- ronment and PROTOCOL.INI is the configuration file for the NDIS environment. The supported NET.CFG keywords are: o NODE ADDRESS o FRAME o PROTOCOL The supported PROTOCOL.INI keywords are: o DRIVERNAME o BINDINGS o NETADDRESS o TOKEN-RING o TOKEN-RING_SNAP ODI2NDI reads the NET.CFG file first, and then reads the PROTOCOL.INI file. The keywords in the PROTOCOL.INI will override the keywords in NET.CFG. The NET.CFG file and keywords are optional. The PROTOCOL.INI file is required. There must be an ODI2NDI section, a DRIVERNAME and a BINDINGS keyword. The instructions that follow will detail the necessary configuration information. INSTALLATION AND CONFIGURATION PROCEDURE The following steps explain how to configure DOS ODI2NDI NetWare Workstation support for IBM Adapters. Step 1 - Install the IBM adapter hardware o Use the hardware installation documentation provided with the adapter to install the adapter hardware. Step 2 - Install the NDIS MAC Driver This can be accomplished in one of two ways: 1. Install the IBM adapter hardware and use the LAN Support Program V1.3x Installation Aid (DXMAID) to install the NDIS MAC Driver for your adapter. The LSP V1.3x Installation Aid will modify the CONFIG.SYS, PROTOCOL.INI and AUTOEXEC.BAT files to while installing the NDIS MAC Driver. NOTE: If this method of installation is used for the NDIS MAC Driver, Step 5 "Install Protocol Manager" step can be skipped. 2. Install the IBM adapter and NDIS MAC Driver using the manual installation instructions provided with the adapter. Step 3 - Install the Netware Workstation Software o Install and configure NetWare Workstation Software on the workstation. See the NetWare documentation for instructions. o Use TOKEN.COM for the adapter ODI MAC Driver. NOTE: If you access a NetWare server through an IBM Token-Ring Network bridge, be sure to install the source routing module ROUTE.COM. IBM Token-Ring Networks use source routing to move information between LANs. ******************************************************** Step 4 - Install ODI2NDI o Create an ODI2NDI directory. o Copy all files from the ODI2NDI\DOS directory on the adapter device driver diskette to the ODI2NDI directory. o Edit the AUTOEXEC.BAT file that was modified during the Netware DOS Requestor installation. Replace the line containing TOKEN.COM with the following two lines: *:\ODI2NDI\ODI2NDI.COM *:\ODI2NDI\NETBIND.COM These two statements will load ODI2NDI and bind ODI2NDI to the NDIS MAC Driver. NOTE: If you installed the NDIS MAC Driver with the LSP Installation Aid during Step 2 "Install the NDIS MAC Driver", the install inserted a NETBIND invoca- tion at the beginning of the autoexec.bat. Comment out the NETBIND invocation from the autoexec.bat. The NETBIND must occur after ODI2NDI has been loaded and before IPXODI and NETX are loaded. ************************************************** Step 5 - Install Protocol Manager NOTE: If the NDIS MAC Driver was installed using the IBM LAN Support Program Installation Aid, or Protocol Manager is already installed, this step can be skipped. Please proceed to Step 6 "Modify the PROTOCOL.INI" file. 1. Edit the CONFIG.SYS file on the root directory of your boot drive. a. Insert a line at the top of the file to load Protocol Manager. The Protocol Manager must be the first device driver loaded. The inserted line should be as follows: DEVICE=*:\ODI2NDI\PROTMAN.DOS /i:*:\ODI2NDI b. The /i option indicates to the protocol manager to search for the PROTOCOL.INI file in the *:\ODI2NDI directory. Step 6 - Modify the PROTOCOL.INI file NOTE: If the Protocol Manager was installed in Step 5 "Install the Protocol Manager", the sample PROTOCOL.INI can be used. If the Protocol Manager was not installed in Step 5, Use the example in the sample PROTOCOL.INI file as a guide to update the existing PROTOCOL.INI file. o Add a protocol stack section for ODI2NDI with the following lines: [ODI2NDI_MOD] DRIVERNAME=ODI2NDI$ The first is the Protocol stack section header, and the second provides the protocol stack name. These two lines are required. o There are four ODI2NDI PROTOCOL.INI keywords. The following keywords should be placed following the Protocol stack section header. The BINDINGS keyword is required in the PROTOCOL.INI file. - BINDINGS=MACNAME Add a BINDING keyword in the ODI2NDI section in the PROTOCOL.INI file. This must be present or the ODI2NDI can not function. A example is included in the sample PROTOCOL.INI. Replace MACNAME in the example with the name of the IBM adapter NDIS MAC Driver. This name can be found in the NDIS MAC Driver documentation for the IBM adapter. NOTE: ODI2NDI is only capable of binding to one NDIS MAC Driver at a time. - TOKEN-RING="yes" or TOKEN-RING="no" TOKEN-RING_SNAP="yes" or TOKEN-RING_SNAP="no" ODI2NDI supports two frame types. Frame Type can be configured with a keyword entry in the PROTOCOL.INI file. Frame type can also be configured via a NET.CFG file keyword. Step 7 "Modify the NET.CFG File" covers modifying the NET.CFG file. ODI2NDI defaults to frame type Token-Ring. - NETADDRESS="4000xxxxxxxx" ODI2NDI requires that the NET ADDRESS be config- ured to the same address in all NDIS protocol stacks that will be binding to the NDIS MAC Driver. Node Address can be configured with a NETADDRESS keyword entry in the PROTOCOL.INI file. The default NETADDRESS is the Universally Administered Address. Net Address can also be configured via a NET.CFG file keyword. Step 7 "Modify the NET.CFG File" covers modifying the NET.CFG file. Step 7 - Modify the NET.CFG file Using the example in the sample NET.CFG file on the option diskette as a guide, add a LINK DRIVER section for ODI2NDI. The LINK DRIVER line in the NET.CFG file should be as follows: LINK DRIVER name "name" being the name of the NDIS MAC Driver that is specified in the BINDINGS statement for ODI2NDI in the PROTOCOL.INI file. There are three supported NET.CFG keywords o NODE ADDRESS 4000xxxxxxxx ODI2NDI reqiures that the NODE ADDRESS be configured to the same address in all NDIS protocol stacks that will be binding to the NDIS MAC Driver. Node address can also be configured via the PROTOCOL.INI file. Step 6 covers modifying the PROTOCOL.INI file. ODI2NDI defaults to the uni- versally administered address of the adapter. o FRAME ODI2NDI supports two frame types. These can be specified with a FRAME keyword entry in the NET.CFG file. The two frame types are: FRAME TOKEN-RING FRAME TOKEN-RING_SNAP Frame type can also be configured via the PROTOCOL.INI file. Step 6 covers modifying the PROTOCOL.INI file. ODI2NDI defaults to frame type Token-Ring. o PROTOCOL IPX This keyword allows ODI2NDI to be configured to support various protocols. ODI2NDI default protocol is IPX. Step 8 Install any IBM products that coexist with the NetWare Requester (i.e. IBM LAN Support Program) Step 9 Restart the workstation to activate DOS ODI2NDI NetWare Requester support.