DataFire ISA BRI NCM Driver Version 1.00 (04/21/97) Installation and Configuration Document Name: DGNCINST.TXT [Version 1.00a] Copyright (c) 1997. Digi International, Inc. 1.0 Introduction This document describes the installation and configuration of the Digi DataFire BRI ISA NCM driver for use with Novell's NIAS 4.x, MPR 3.1, and NetWare Connect 2.0 products. It describes the basic steps and unique procedures to operate this NCM driver within MPR and NetWare Connect. It is not intended as a guide to install or use these products. The user of this driver must be familiar with NIAS 4.x, MPR 3.1 and/or NetWare Connect 2.0. 1.1 Requirements The DataFire NCM driver (DGNCMDRV.NLM) is only intended to be used with Novell's NIAS 4.x, MPR 3.1 and NetWare Connect 2.0 products. Although it has a CAPI interface, it should not be used with any other applications. The DataFire NCM driver supports the following hardware and software: o Digi DataFire BRI ISA (U or S/T) Server Version (S1). o Digi DataFire/4 BRI ISA S/T. o NetWare 3.12, 4.10, or IntranetWare o NIAS 4.0 and NIAS 4.1 (Part of IntranetWare) o MPR 3.1 o NetWare Connect 2.0 Note: It is very important to apply all required Novell patches to the components you are using! The DataFire NCM driver supports a maximum of five (5) adapters of either type. The DataFire NCM driver can co-exist with Digi's previous NetWare ISDN driver PCIMAC.NLM. However, each adapter can only be configured and controlled by a single driver. These drivers cannot share adapters. Note: A DataFire adapter in another system running the PCIMAC.NLM driver will not be able to communicate to a DataFire running with MPR because PCIMAC.NLM does not support PPP. Novell supports Multi-link PPP in NIAS 4.1 or with a special patch to MPR 3.1. 1.2 Driver Disk Contents If you received this driver on a floppy or zip file, the disk will contain the files listed below. If this driver is part of NIAS 4.1, the driver is already installed in the SYS:SYSTEM directory on your server and it will not contain the files marked with an '*'. The installation disk contains the following files: ADP.BIN - Download file for DataFire adapter DGNCMCFG.NLM - Configuration utility DGNCMCFG.TXT - Configuration utility instructions DGNCMDRV.NLM - DataFire BRI ISA NCM driver DGNCMDRV.TXT - This document DGNCMRL.NCF - "Batch" file for reloading DGNCMDRV.NLM DGNCMSTS.NLM - Status and Tracing utility DGNCMSTS.TXT - Status and Tracing utility instructions *DGNCMUIN.NLM - Un-install utility used by PINSTALL.NLM *PINSTALL.HLP - Help messages for PINSTALL.NLM *PINSTALL.NLM - Main install utility *PSCRIPT.DAT - Script file for PINSTALL.NLM *WHSMCAPI.LAN - Updated version of Novell driver * These files are not included on Novell's NIAS 4.1 installation CD-ROM. The following files are created by the driver utilities in the sys:system\ directory: DGNCMDRV.CFG - DGNCMDRV.NLM configuration file DGNCMSTS.TRC - Default D-Channel binary trace file DGNCMSTS.ASC - Default D-Channel ascii trace file 2.0 Installation and Configuration If you will be using the Digi NCM Driver which is included with NIAS 4.1, you do not need to install the driver. It will be copied to the SYS:SYSTEM directory when you install NIAS 4.1. If you are upgrading or installing the NCM driver from a floppy, the disk label must be "DGNCM_1" or, if installing from a directory, the directory must be named "DGNCM_1". The installation process will copy the NCM driver files into the SYS:SYSTEM directory on the server. Here is an overview of the major steps to install and configure a system to use the DataFire ISA adapters: o Install NetWare OS and recommended patches. o Install NIAS 4.x, MPR 3.1 or NetWare Connect 2.0 and their current patches. o Install the DataFire adapter(s). o Install and configure the DataFire NCM driver. o Configure MPR and/or NetWare Connect. o Edit AUTOEXEC.NCF. These steps are detailed below. 2.1 Install NetWare OS and its current recommended patches. Install your NetWare OS if not already installed. You should apply the current patches to your OS as recommended by Novell. You can obtain information and the patch files from Novell's Web Site at: http://support.novell.com. 2.2 Install NIAS 4.x or MPR 3.1 If you do not require MPR, skip to the next step to install NetWare Connect. Install MPR 3.1 from the stand-alone product or from NIAS which is part of IntranetWare. Support for ISDN on MPR is provided in the base install. You do not need to install any other MPR extensions unless you need them for a different product. Note: IntranetWare comes standard with a one-port MPR license. Since each ISDN BRI line has two ports, only one WAN port (Network Interface) can be enabled at a time. You will need to add additional MPR licenses to use the other ports. Install the current NIAS 4.x or MPR 3.1 patches. Novell requires that the server be brought down and reloaded after applying any patches. 2.3 Install NetWare Connect 2.0 If you do not require NetWare Connect, skip to the next step. If you have NIAS 4.1, Netware Connect is included in this product and is now called Remote Access Services. Install NIAS 4.1 if you have not already installed it for MPR support. You should first familiarize yourself with the server side configuration of NetWare Connect or Remote Access Services before you continue. Be sure to apply any Novell recommended patches for NetWare Connect 2.0 or NIAS 4.1. Novell requires that the server be brought down and reloaded after applying any patches. 2.4 Install the DataFire adapter. Refer to the "DataFire Hardware Installation Manual" for instructions on installing your adapter. Remember to write down the I/O address you selected for each adapter. These addresses are required during driver configuration. DataFire I/O switch settings: Switch Positions I/O Addr 1 2 3 4 -------- ---------------- 0x110 dn dn up xx (up = off, dn = on) 0x140 dn up dn xx 0x150 dn up up xx 0x300 up dn dn xx 0x310 up dn up xx 0x340 up up dn xx 0x350 up up up xx 2.5 Install DataFire NCM driver. If you are installing from a floppy disk, and you created the disk yourself, be sure the disk has a volume label of DGNCM_1. If you would like to install the driver from a NetWare volume, copy the contents of the driver disk into a subdirectory on the server. The subdirectory must be named DGNCM_1. Load the NetWare install utility from the NetWare console prompt by typing: load install The following steps will vary for different versions of NetWare. Select "Product Options" from the installation program's main menu and press . For NetWare 3.12 systems: Press on the "Currently Installed Products" screen. If installing from a floppy, insert the floppy in the A: drive and press . If installing from the NetWare sys: volume, enter the FULL path to the driver installation directory and press . Example: sys:dgncm_1 For NetWare 4.x systems: Select option "View/Configure/Remove installed products" and press . Press to install or update a product. If installing from a floppy, insert the floppy in the A: drive and press . If installing from the NetWare sys: volume, press the key and enter the FULL path to the driver installation directory. Example: sys:dgncm_1 Select the "Install Product" option from the "Installation Options" menu. From the "Install to Servers" menu, add or delete servers you would like to install to by pressing the or keys. RSPAWN.NLM must be loaded on remote servers to see them in the list which appears when you press the key. Press the key to start the install process, and answer YES to the confirmation question. When the installation is completed, exit completely out of the install utility. 2.6 Configure Digi NCM driver The DataFire NCM driver is configured through the NCM Configuration Utility (DGNCMCFG.NLM). This utility configures adapter and line specific parameters. Start this utility from the NetWare console prompt by typing: load dgncmcfg Refer to the document DGNCMCFG.TXT on the driver disk for details on using this utility. There is also help available on each screen by pressing the key. If you are installing a leased or permanent line, see appendix A in this document for details. Once the driver configuration is complete, you will need to load the DGNCMDRV.NLM driver. This can be done from the "Load/Reload Driver" option in the Digi NCM Configuration Utility, or by loading it from the command line by typing: load dgncmdrv Note: If you select "Load/Reload Driver" from the main menu in the NCM Configuration Utility, you will be asked two questions. Answer YES to The first question. The second question will ask if you want to issue the "reinitialize system" command. Since you have not completed the installation yet, you should answer NO to this question. This command will be issued later during MPR or NWC configuration. Monitor the console messages (use or to switch screens) to see if all adapters and lines loaded successfully. You will add the "load dgncmdrv" command into the system's AUTOEXEC.NCF file in a later step so that the driver will load automatically at server boot time. If the driver loaded successfully, run the NCM Status Utility (DGNCMSTS.NLM) to check the Layer status for each configured line. Start this utility from the NetWare console prompt by typing: load dgncmsts This utility can also be loaded by selecting the "Load Driver Status Utility" from the NCM Configuration Utility's main menu. The layer status can be displayed by selecting "View Lines" from the main DGNCMSTS menu. Select the line to display from the list and press . Next select "Layer 3 (Q.931) Status" and press . Layer 3 should show "Active" for each configured End Point on the line. If it does not, you must resolve this problem before going further. Make sure the cable is connected. If you are using an S/T version of the adapter, make sure the NT1 is connected and powered on. Also make sure you have selected the proper switch type for your line and that you have coded the correct Address and SPID (if required) for your line. Euro-ISDN (NET3) type switches may shut down the ISDN line if there is no call activity for a period of time. When this occurs, all three layer displays in the NCM Status Utility will indicate a disconnected line. This is normal and you will not be able to verify the line's configuration until you place or receive a call on this line. Note: Whenever future changes are made to the Digi NCM Driver configuration, DGNCMDRV.NLM will need to be unloaded and reloaded. This can be done from the NCM Configuration utility through the "Load/Reload Driver" option, or by starting the reload NCF file from the system console: dgncmrl 3.0 MPR Configuration If you are not installing MPR, skip to section 4.0. The DataFire NCM driver presents each line on an adapter as a CAPI controller. Each CAPI controller then has two channels available. Thus, a single line DataFire will appear to MPR as a single CAPI Board with two ports. A DataFire/4 will appear as four CAPI Boards with two ports on each CAPI board. This mapping from CAPI channels to INETCFG ports is done through the INETCFG.NLM utility. Load this utility from the command prompt by typing: load inetcfg If this is the first time you have loaded INETCFG, it will ask you if it can move LAN commands from your AUTOEXEC.NCF file. You should answer YES to this question. Do not select the "Fast Setup" if prompted. WAN ports must be configured through the standard INETCFG menu. The major steps for configuring a "CAPI Board" are: o Add a WHSMCAPI Board o Configure Network Interfaces (Ports) o Configure Protocols o Bind Protocols to WHSMCAPI ports o Configure WAN Call Destinations (if any) o Reinitialize System 3.1 Add a WHSMCAPI Board For each DataFire ISDN line (CAPI controller) you will need to create a WHSMCAPI board. If the Board already exists, skip to the next step "Configure Network Interfaces". To create a board, select "Boards" from the main INETCFG menu and press . Press the key to create a new board and select the WHSMCAPI driver from the list and press . Enter a board name that will represent the ISDN line you are mapping to. The name does not have to match the name assigned to the DataFire line, but it will be easier to manage if you pick a name that relates to this line. The default name for DataFire Board 0 would be DGISDN0 and it's first line's name (CAPI controller name) would be DGISDN0_L0. From the WHSMCAPI Board Configuration screen, select "CAPI Board Options" and press . This is the only item which you should edit on this screen. When prompted "Should INETCFG automatically load the CAPI driver?", answer No. You will be presented with a list of all CAPI controllers currently loaded in the system. Select and press the key for the Digi CAPI controller you want to map to this WHSMCAPI board. Be careful not to pick a CAPI Controller that is already mapped to a different WHSMCAPI board. If you do not see the expected CAPI controller in the list, verify that DGNCMDRV.NLM is loaded and configured correctly. You must have DGNCMDRV.NLM loaded for lines to appear in the CAPI Controller list. Press from the "WHSMCAPI Board Configuration" screen, and answer YES to save the changes. Repeat the previous steps for each ISDN line you want to configure. 3.2 Configure Network Interfaces From the main INETCFG menu, select the "Network Interfaces" item and press . This screen allow you to configure each port (ISDN channel) on the WHSMCAPI board (ISDN Line). Select the Network Interface to configure and press . Select PPP as a Medium. On the "PPP Network Interface Configuration" screen, you must edit the following items: ISDN Address/Sub-Address: These parameters must be set to exactly match that of the End Points in the NCM Driver's Line you want the port to represent. WHSMCAPI uses these numbers to direct incoming and outgoing calls to the correct CAPI controllers. If only one End Point is defined for this ISDN line, enter the same Address of that End Point on both WHSMCAPI ports which map to that line. Note: If an ISDN line has only a single address (phone number), you will not be able to share its network interfaces between MPR and NetWare Connect. Modem/DCE Type: Select ISDN(AT Controlled) Authentication Options: Make sure "Inbound Call Processing" is set to "Enabled" if this interface is to answer incoming calls. Set "Inbound Authentication" to the desired protocol. This parameter only applies to incoming calls. If this is the first call you are setting up, you can simplify the configuration by selecting "None" for this parameter. Once you get the connection working, you can change this to the desired setting. Authentication Database: This option is used to enter PPP "Remote System ID" and its password into the authentication database. Negotiation Options: Press enter on this option. If the "MRU Maximum Size" option is larger than 1600 bytes, change this parameter to 1600. This is the largest frame the DataFire adapter can support (not including PPP overhead). Edit other parameters as required by your configuration. Reference the MPR 3.1 documentation for details on this process. Repeat the above steps for each WHSMCAPI port. 3.3 Sharing WAN Interfaces between MPR and NetWare Connect Note: Novell only supports the coexistence of MPR and NetWare Connect starting with NIAS 4.1. In the Digi NCM model, a WHSMCAPI Board is a virtual Board which represents an ISDN line. MPR and Remote Access Services (NetWare Connect) can share virtual boards, but they cannot share ports on those virtual boards. Interfaces (Ports) intended for MPR must be configured through INETCFG.NLM. Interfaces intended for NetWare Connect must be configured through NWCCON.NLM using the "Synchronous Interfaces" option. This option starts INETCFG.NLM in a special mode specifically for NetWare Connect. Once an "Unconfigured" Network Interface is configured as an MPR or Remote Access Services Interface, it cannot be changed to the other type of interface unless you first delete the interface (making it Unconfigured). You can determine which mode the interface has been configured by the name specified under the Media column. "PPP Routing" indicates the port is an MPR port. "PPP Remote Access" indicates the port belongs to Remote Access (Netware Connect). 3.4 Configure Protocols Select the "Protocols" option from the main menu to configure required protocols. Refer to the MPR documentation for more details. 3.5 Configure WAN Call Destinations If this server will be making outgoing calls, you will need to Select "WAN Call Directory" to create a WAN Call Destination. This is where you specify the phone number of the device you are calling, and which interface to use for the call. Refer to the MPR 3.1 documentation for more details. 3.6 Bind Protocols to WHSMCAPI ports Select the "Bindings" option from the main menu to bind protocols to the WHSMCAPI interfaces. If you want data on this port to automatically connect when the server is loaded or when there is a frame to send out the port, you must include a "WAN Call Destination" entry on this binding. Refer to the MPR 3.1/NIAS 4.x documentation for more details. 3.7 Reinitialize System Most changes made in INETCFG do not take effect immediately. Once all changes are complete, you must issue the "Reinitialize System" command (it is not usually necessary to down the server). This command can be issued from the main menu of INETCFG, or by typing the following command at the server console: reinitialize system Monitor the server console messages for any errors that may be displayed after this command is issued. Use INETCFG's "Console Messages" option in "View Configuration" if necessary to view messages which may have scrolled off of the screen. 3.8 Make a Call on an MPR port Load the MPR call manager from the console prompt by typing: load callmgr This utility is used to make outgoing calls and also to monitor incoming calls. On the server you will be initiating a call, press the key to display a list of defined WAN Call Destinations. Select the destination name to call and press . Next, select the protocol to use on the call and press . Monitor the "Remote Sys ID" and the "Status" fields. "Status" will switch to connected when the ISDN call was successful. The actual protocol will not be connected until a name or IP address appears in the "Remote Sys ID" field. If the call failed, switch to the main console screen and look for any error messages related to the call attempt. 4.0 NetWare Connect 2.0 Configuration If you would like to install NetWare Connect services and have NIAS 4.1 or higher, skip to section 5.0. NIAS 4.1 includes NetWare Connect services, but it is under the name of "Remote Access Services". If you are not installing NetWare Connect, skip to section 6.0. All NetWare Connect configuration is done through the NWCCON.NLM utility. Start this utility by entering the following command at the console prompt: load nwccon The ISDN lines are installed as a Synchronous Interface. The first time NWCCON is loaded it assumes that you will be installing an Asynchronous (AIO) driver. If you will not be installing an AIO driver, you must cancel the automated install process and skip the steps to add an AIO driver. The major steps for configuring the DataFire NCM Driver with NetWare Connect are: o Configure PPPRNS o Configure Synchronous Interfaces o Configure Network Interfaces o Reinitialize System o Configure NetWare Connect Ports o Configure Security Options. o Configure PPPRNS Services o Run Configuration Report o Restart NetWare Connect o NetWare Connect Monitoring 4.1 Configure PPPRNS From the main menu "NetWare Connect Options", select "Set Up NetWare Connect" and press . Select "Select NetWare Connect Services" and press . Select PPPRNS and press . NetWare Connect creates a common IP and IPX network for NetWare Connect Clients. Select and configure each protocol required in your environment. Escape back to the main menu "NetWare Connect Options". 4.2 Configure Synchronous Interfaces Select "Configure NetWare Connect" and press . Select "Synchronous Interfaces" and press . This will start INETCFG.NLM in a special mode for configuring NetWare Connect interfaces. For each DataFire ISDN line (CAPI controller) you will need to create a WHSMCAPI board. If the Board already exists, skip to the next step "Configure Network Interfaces". To create a board, select "Boards" from the main INETCFG menu and press . Press the key to create a new board and select the WHSMCAPI driver from the list and press . Enter a board name that will represent the ISDN line you are mapping to. The name does not have to match the name assigned to the DataFire line, but it will be easier to manage if you pick a name that relates to this line. The default name for DataFire Board 0 would be DGISDN0 and it's first line's name (CAPI controller name) would be DGISDN0_L0. From the WHSMCAPI Board Configuration screen, select "CAPI Board Options" and press . This is the only item which you should edit on this screen. When prompted "Should INETCFG automatically load the CAPI driver?", answer No. You will be presented with a list of all CAPI controllers currently loaded in the system. Select and press the key for the Digi CAPI controller you want to map to this WHSMCAPI board. Be careful not to pick a CAPI Controller that is already mapped to a different WHSMCAPI board. If you do not see the expected CAPI controller in the list, verify that DGNCMDRV.NLM is loaded and configured correctly. You must have DGNCMDRV.NLM loaded for lines to appear in the CAPI Controller list. Press from the "WHSMCAPI Board Configuration" screen, and answer YES to save the changes. Repeat the previous steps for each ISDN line you want to configure. 4.3 Configure Network Interfaces From the main INETCFG menu, select the "Network Interfaces" item and press . This screen allows you to configure each port (ISDN channel) on the WHSMCAPI board (ISDN Line). Select the Network Interface to configure and press . Select PPP as a Medium. On the "PPP Network Interface Configuration" screen, you must edit the following items: ISDN Address/Sub-Address: These parameters must be set to exactly match that of the End Points in the NCM Driver's Line you want the port to represent. WHSMCAPI uses these numbers to direct incoming and outgoing calls to the correct CAPI controllers. If only one End Point is defined for this ISDN line, enter the same Address of that End Point on both WHSMCAPI ports which map to that line. Note: If an ISDN line has only a single address (phone number), you will not be able to share its network interfaces between MPR and NetWare Connect. Repeat the above steps for each WHSMCAPI Network Interface. 4.4 Sharing WAN Interfaces between MPR and NetWare Connect Note: Novell only supports the coexistence of MPR and NetWare Connect starting with NIAS 4.1. In the Digi NCM model, a WHSMCAPI Board is a virtual Board which represents an ISDN line. MPR and Remote Access Services (NetWare Connect) can share virtual boards, but they cannot share ports on those virtual boards. Interfaces (Ports) intended for MPR must be configured through INETCFG.NLM. Interfaces intended for NetWare Connect must be configured through NWCCON.NLM using the "Synchronous Interfaces" option. This option starts INETCFG.NLM in a special mode specifically for NetWare Connect. Once an "Unconfigured" Network Interface is configured as an MPR or Remote Access Services Interface, it cannot be changed to the other type of interface unless you first delete the interface (making it Unconfigured). You can determine which mode the interface has been configured by the name specified under the Media column. "PPP Routing" indicates the port is an MPR port. "PPP Remote Access" indicates the port belongs to Remote Access (Netware Connect). 4.5 Reinitialize System Once all changes are complete, return to the main INETCFG menu "Internetworking Configuration". You must issue the "Reinitialize System" command. (it is not usually necessary to down the server). If your version of INETCFG does not have a "Reinitialize System" option, it must be issued from the server console by typing the following command: reinitialize system Monitor the server console messages for any errors that may be displayed after this command is issued. Use INETCFG's "Console Messages" option in "View Configuration" if necessary to view messages which may have scrolled off of the screen. Press from the "Internetworking Configuration" menu to return to NWCCON. 4.6 Configure NetWare Connect Ports On the "Configuration Options" menu, select "Ports" and press . This screen displays all of the configured NetWare Connect ports. Port names which start with "AIO_10xxxx" are ports which were configured using the "Synchronous Interfaces" option. "XXXX" is the relative index of the NetWare Connect specific synchronous interface which maps to AIOTSM.NLM. Note: There is not a permanent linkage between a Network Interface defined in INETCFG and the AIO_10xxxx port mapped to AIOTSM.NLM. The first NetWare Connect style Network Interface configured in INETCFG maps to AIO_100000, the second to AIO_100001, and so on. If you delete the first NetWare Connect specific Network Interface within INETCFG, AIO_100000 will then map to the next interface. Configure each AIO_10xxxx port by selecting it and pressing . Edit the port name and description as desired. For "Modem Type" select "ISDN(AT Controlled)". Select "" to change group and application related parameters. It is not necessary to change "Modem Parameters" or "Link Parameters" within this menu. They do not apply for ISDN lines. Press until you return back to the "Configuration Options" menu. 4.7 Configure Security Options. Select "Security" from the "Configuration Options" menu and press . Edit these parameters as necessary for your configuration. You MUST select a "Remote Client Password" for users which will be dialing in from clients which use PAP or CHAP for authentication. NWCAP clients do not require remote client passwords. Escape back to "Configuration Options" 4.8 Configure PPPRNS Services Select "Services" from the "Configuration Options" menu and press . Select "PPPRNS" and press . The "Configure Security" option is used to enable the required "Authentication Protocols" for your configuration. You will need PAP or CHAP for non-NetWare Connect Clients (i.e. Windows 95). The "Set IPX Parameters" option is used to specify an IPX Node address and Home Server for each user if required. These usually do not have to be specified to establish a connection. The "Set IP Parameters" option is used to specify Domain and Boot parameters for each user if required. You do not need to specify boot parameters unless your client requires BOOTP to get an IP address. Press to return back to the "Configuration Options" menu. 4.9 Run Configuration Report From the "Configuration Options" menu, select "Report" and press . Run a report to verify that there are no Consistency Check Warnings. Correct relevant errors before proceeding. Exit completely out of NWCCON. 4.10 Restart NetWare Connect To activate changes, issues the following commands at the console prompt. nwcstop nwcstart Note: If changes were made to internal IPX or IP numbers you will need to down the server. 4.11 NetWare Connect Monitoring The "View NetWare Connect Status" option of NWCCON can be used to monitor and trace the NetWare Connect ports. PPPCON.NLM and PPPTRACE.NLM are also useful utilities to monitor and trace PPPRNS connections. 5.0 Remote Access Services of NIAS 4.1 All Remote Access Services (RAS) configuration is done through the NWCCON.NLM utility. Start this utility by entering the following command at the console prompt: load nwccon The ISDN lines are installed as a Synchronous Interface. The first time NWCCON is loaded it assumes that you will be installing an Asynchronous (AIO) driver. If you will not be installing an AIO driver, you must cancel the automated install process and skip the steps to add an AIO driver. The major steps for configuring the DataFire NCM Driver with RAS are: o Configure PPPRNS o Configure Synchronous Interfaces o Configure Network Interfaces o Reinitialize System o Configure RAS Ports o Configure Security Options. o Configure PPPRNS Services o Run Configuration Report o Restart RAS o RAS Monitoring 5.1 Configure PPPRNS From the main menu "Remote Access Options", select "Set Up Remote Access Services" and press . Select "Select Remote Access Services" and press . Select PPPRNS and press . RAS creates a common IP and IPX network for RAS Clients. Select and configure each protocol required in your environment. Escape back to the main menu "Remote Access Options". 5.2 Configure Synchronous Interfaces Select "Configure Synchronous Interfaces" and press . This will start INETCFG.NLM in a special mode for configuring RAS interfaces. For each DataFire ISDN line (CAPI controller) you will need to create a WHSMCAPI board. If the Board already exists, skip to the next step "Configure Network Interfaces". To create a board, select "Boards" from the main INETCFG menu and press . Press the key to create a new board and select the WHSMCAPI driver from the list and press . Enter a board name that will represent the ISDN line you are mapping to. The name does not have to match the name assigned to the DataFire line, but it will be easier to manage if you pick a name that relates to this line. The default name for DataFire Board 0 would be DGISDN0 and it's first line's name (CAPI controller name) would be DGISDN0_L0. From the WHSMCAPI Board Configuration screen, select "CAPI Board Options" and press . This is the only item which you should edit on this screen. When prompted "Should INETCFG automatically load the CAPI driver?", answer No. You will be presented with a list of all CAPI controllers currently loaded in the system. Select and press the key for the Digi CAPI controller you want to map to this WHSMCAPI board. Be careful not to pick a CAPI Controller that is already mapped to a different WHSMCAPI board. If you do not see the expected CAPI controller in the list, verify that DGNCMDRV.NLM is loaded and configured correctly. You must have DGNCMDRV.NLM loaded for lines to appear in the CAPI Controller list. Press from the "WHSMCAPI Board Configuration" screen, and answer YES to save the changes. Repeat the previous steps for each ISDN line you want to configure. 5.3 Configure Network Interfaces From the main INETCFG menu, select the "Network Interfaces" item and press . This screen allows you to configure each port (ISDN channel) on the WHSMCAPI board (ISDN Line). Select the Network Interface to configure and press . Select "PPP Remote Access" as a Medium. On the "PPP Network Interface Configuration" screen, you must edit the following items: ISDN Address/Sub-Address: These parameters must be set to exactly match that of the End Points in the NCM Driver's Line you want the port to represent. WHSMCAPI uses these numbers to direct incoming and outgoing calls to the correct CAPI controllers. If only one End Point is defined for this ISDN line, enter the same Address of that End Point on both WHSMCAPI ports which map to that line. Note: If an ISDN line has only a single address (phone number), you will not be able to share its network interfaces between MPR and RAS. Repeat the above steps for each WHSMCAPI Network Interface. 5.4 Sharing WAN Interfaces between MPR and RAS Note: Novell only supports the coexistence of MPR and RAS starting with NIAS 4.1. In the Digi NCM model, a WHSMCAPI Board is a virtual Board which represents an ISDN line. MPR and Remote Access Services (NetWare Connect) can share virtual boards, but they cannot share ports on those virtual boards. Interfaces (Ports) intended for MPR must be configured through INETCFG.NLM. Interfaces intended for RAS must be configured through NWCCON.NLM using the "Synchronous Interfaces" option. This option starts INETCFG.NLM in a special mode specifically for RAS. Once an "Unconfigured" Network Interface is configured as an MPR or Remote Access Services Interface, it cannot be changed to the other type of interface unless you first delete the interface (making it Unconfigured). You can determine which mode the interface has been configured by the name specified under the Media column. "PPP Routing" indicates the port is an MPR port. "PPP Remote Access" indicates the port belongs to Remote Access. 5.5 Reinitialize System Once all changes are complete, return to the main INETCFG menu "Internetworking Configuration". You must issue the "Reinitialize System" command. (it is not usually necessary to down the server). If your version of INETCFG does not have a "Reinitialize System" option, it must be issued from the server console by typing the following command: reinitialize system Monitor the server console messages for any errors that may be displayed after this command is issued. Use INETCFG's "Console Messages" option in "View Configuration" if necessary to view messages which may have scrolled off of the screen. Press from the "Internetworking Configuration" menu to return to NWCCON. 5.6 Configure RAS Ports On the "Remote Access Options" menu, select "Configure Ports" and press . This screen displays all of the configured RAS ports. Port names which start with "AIO_10xxxx" are ports which were configured using the "Synchronous Interfaces" option. "XXXX" is the relative index of the RAS specific synchronous interface which maps to AIOTSM.NLM. Note: There is not a permanent linkage between a Network Interface defined in INETCFG and the AIO_10xxxx port mapped to AIOTSM.NLM. The first RAS style Network Interface configured in INETCFG maps to AIO_100000, the second to AIO_100001, and so on. If you delete the first RAS specific Network Interface within INETCFG, AIO_100000 will then map to the next interface. Configure each AIO_10xxxx port by selecting it and pressing . Edit the port name and description as desired. For "Modem Type" select "ISDN(AT Controlled)". Select "" to change group and application related parameters. It is not necessary to change "Modem Parameters" or "Link Parameters" within this menu. They do not apply for ISDN lines. Press until you return back to the "Configuration Options" menu. 5.7 Configure Security Options. Select "Configure Security" from the "Remote Access Options" menu and press . Edit these parameters as necessary for your configuration. You MUST select a "Remote Client Password" for users which will be dialing in from clients which use PAP or CHAP for authentication. NWCAP clients do not require remote client passwords. Escape back to "Remote Access Options" 5.8 Configure PPPRNS Services Select "Configure Services" from the "Remote Access Options" menu and press . Select "PPPRNS" and press . The "Configure Security" option is used to enable the required "Authentication Protocols" for your configuration. You will need PAP or CHAP for non-RAS Clients (i.e. Windows 95). The "Configure ISDN Short Hold Parameters" determines how long a connection idle period must be before the connection is disconnected. The "Set IPX Parameters" option is used to specify an IPX Node address and Home Server for each user if required. These usually do not have to be specified to establish a connection. Press to return back to the "Remote Access Options" menu. 5.9 Run Configuration Report From the "Remote Access Options" menu, select "Generate Configuration Report" and press . Run a report to verify that there are no Consistency Check Warnings. Correct relevant errors before proceeding. Exit completely out of NWCCON. 5.10 Restart RAS To activate changes, issues the following commands at the console prompt. nwcstop nwcstart Note: If changes were made to internal IPX or IP numbers you will need to down the server. 5.11 RAS Monitoring The NWCSTAT.NLM utility can be used to monitor and trace the NetWare Connect ports. PPPCON.NLM and PPPTRACE.NLM are also useful utilities to monitor and trace PPPRNS connections. 6.0 Updating AUTOEXEC.NCF The DGNCMDRV.NLM driver needs to be loaded before MPR or NetWare Connect services are started. The configuration utility, DGNCMCFG.NLM, will automatically check the AUTOEXEC.NCF file for this load line when you exit the main configuration screen. If the load line is not present, the user will be asked if it should be added to the file. If you answer yes, DGNCMCFG will add the load line to the AUTOEXEC.NCF file and rename the original file to AUTOEXEC.DG. If you answer no, you will need to manually add the load line to the file. To manually add the load line, edit the AUTOEXEC.NCF file through the INSTALL utility. Add the following line to the file BEFORE the command "sys:etc\initsys.ncf": load dgncmdrv To have NetWare Connect automatically start when the server loads, you must add the following command to the AUTOEXEC.NCF file after the "etc/initsys.ncf" command. The command is not preceded by "load": nwcstart 7.0 NCM Driver Status and Tracing The DGNCMDRV.NLM driver can be monitored through the status program "DGNCMSTS.NLM". This program can be started through the "Load Driver Statistics Utility" menu option within the Configuration Utility (dgncmcfg.nlm) or from the NetWare server console command line by typing: load dgncmsts This utility will display the current running configuration and status of the adapter. Refer to the "DataFire NCM Driver Status Program" in file DGNCMSTS.TXT for instructions on its operation. 8.0 Troubleshooting If you are having problems configuring or connecting with this driver, the following information can be helpful in determining the problem. Reference the NetWare Console for any related error messages. Use the "View Console Message" option within INETCFG to view messages which have scrolled off of the screen. DGNCMDRV.NLM maintains a separate message screen on the NetWare console. Refer to this screen for any error messages which may relate to your problem. Use the NCM Status Utility (DGNCMSTS.NLM) to monitor the state of the adapters. Use this tool to check the state of the ISDN lines. This utility can also trace an ISDN line's D-Channel. A D-Channel trace of an ISDN line which is not calling or answering correctly can provide important information to a technical support person. Other useful NetWare utilities: PPPCON.NLM - Displays status and statistics for each PPP port. PPPTRACE.NLM - Traces data and events at the PPP interface. CAPITRACE.NLM - Traces and decodes CAPI messages on a specific CAPI controller. MONITOR.NLM - The "LAN Information" option displays statistics for each WAN "Network Interface". TECHWALK.NLM - Captures all option settings in INETCFG to a file. If you call Digi's Technical Support, please provide this information: The versions of the NCM Driver components. This can be determined by issuing the following command at the console prompt: DGNCMVER This "batch" file will display the version and date of files associated with the NCM driver. Type and model of PC Version of OS and patch level Version of MPR and/or NWC and patch level The SYS:SYSTEM\DGNCMDRV.CFG file. Load TECHWALK.NLM to record INETCFG's configuration to SYS:ETC\TECHWALK.LOG and submit this file. Include the following files unless you are providing TECHWALK output: STARTUP.NCF (from the c: partition) SYS:SYSTEM\AUTOEXEC.NCF The console log messages during the time of the problem. By default, NetWare will log console messages to a file. The path to this file is SYS:ETC\CONSOLE.LOG. Make a copy of this file shortly after the problem occurs, and submit this file. Load SERVMAN.NLM and write SET command values to file. This is done by first selecting "Server Parameters" then pressing on the next menu. Then select "Copy all parameters to a file" and press . This will write all set parameter values to file SYS:SYSTEM\SETCMDS.CP. Submit this file. How to reach Digi's Technical Support: PHONE: 1-612-912-3444 FAX: 1-612-912-4958 EMAIL: support@dgii.com Appendix A Leased/Permanent line operation Background The NCM Driver considers a leased line to be an ISDN line which provides 2 B channels but no D channel. An outgoing call completion is simulated so that the application software will start to send out B channel data. An NCM Driver on the other side of this connection will simulate an incoming call when it sees an incoming B channel PPP frame which contains an LCP ConfigReq (the first frame on a new connection.) Configuration Summary Leased line operation is set from the Line configuration by choosing a switch style of "Leased/Permanent". The simplest configuration for lease line operation is to designate one side to be the calling side and the other to be the answering side. Calling Side The call must always be at 64Kbps. The last digit of the phone number for the outgoing call indicates which B channel should be used. 1 - B1 2 - B2 0, 3-9 - First available channel Unless you need to match a call with a specific B channel on the other side, use 0 as the dialing number to simplify the configuration. Please note that if you are making a Multilink PPP connection, you must specify the line speed as part of each additional phone number in the "MLP Phone List Configuration". This list is part of the Multilink Configuration of the Wan Call Directory in INETCFG.NLM. This is done by appending a "p2" to the end of each phone number listed, indicating that a 64Kbps call is to be made. Not doing so will cause the default 56Kbps calls to these numbers to fail. You will see messages on the main console similar to those below: DGNCMDRV: Call to "XXXX" on line DGISDN0_L0 failed! DGNCMDRV: Speed "56k (Rate Adapted)" is not supported DGNCMDRV: Leased Lines only support a call of 64Kbps DGNCMDRV: Connect Request on Line DGISDN0_L0 Cid: xxxx failed. DGNCMDRV: CAPI error (2007): "Illegal message parameter" Answering Side If only one endpoint is defined, both incoming calls will use the address coded on that endpoint as the called address. If two endpoints are defined, incoming data on B1 will cause a simulated call to appear on endpoint 0, and incoming data on B2 will cause a call to appear on endpoint 1. Steps: - Configure the line for a switch style of Leased/Permanent. - Define two endpoints. Assign an arbitrary address for each one like 9991 and 9992. These addresses must be unique among other address within this server, and must also be specified on the network interface in INETCFG. You can choose the same addresses for both sides of the link if you wish. - Within INETCFG, create a WHSMCAPI board to represent the line. Define the network interfaces and assign the addresses specified on each end point. Also assign the lines to the same group. - On the calling side, create a WAN Call Destination. It should be configured as a permanent connection. Use '0' as a phone number. This will select the first available B Channel. The call should always be made at 64Kbps, and should always retry failures. If you are using Multi-Link PPP with more than one link, configure the link as "Static" instead of "Bandwidth on Demand". - Bind your desired protocol to the group representing the leased network interfaces. You should also add a WAN Call Destination at the calling side binding definition if you want the call to automatically initiate at system load time. End of Document