-------------------------------------------------------------------- Installing the ATMworks 350L NetWare 4.x ODI Server Driver on NetWare 4.02 and 4.1 Servers -------------------------------------------------------------------- CONTENTS -------- Section 1.0 SYSTEM REQUIREMENTS Section 2.0 ATMworks 350L HARDWARE INSTALLATION 2.1 Initial Hardware Verification 2.2 Attaching Cables to the ATMworks 350L 2.3 RJ45 Pinout 2.4 ATMworks 350L Specifications Section 3.0 LOADING THE DRIVER SOFTWARE Section 4.0 DRIVER CONFIGURATION 4.1 Overview 4.1.2 Creating Configuration Files 4.1.3 Driver Configuration Types 4.1.4 Hints on Selecting Ethernet Frame Types 4.2 Configuration Parameters 4.3 Sample Driver Configurations 4.3.1 LAN Emulation Configuration 4.3.2 Classical IP Client Configuration 4.3.3 Classical IP Server Configuration 4.3.4 PVC Configuration over Classical IP Section 5.0 VERIFYING THE INSTALLATION 5.1 Restarting NetWare to use the ATMworks 350L Section 1.0 SYSTEM REQUIREMENTS ------------------------------- - Operating System: Novell NetWare 4.02 or 4.1 - Unused PCI bus master full-size slot. - Rev 2.0 or higher PCI compliant system. - 1MB disk space for ATMworks/350L driver - .5MB memory for ATMworks/350L driver Minimum system memory requirements depend on the modules loaded in your server. Preliminary testing with the ATMworks/350L driver in a NetWare server with three or four Windows/NT clients indicate the following minimum requirements: 16MB RAM if not running TCP/IP or NetWare/IP 24MB RAM if running TCP/IP or NetWare/IP Optional System Software (tested versions): ------------------------- NetWare/IP: v2.1 for NetWare 4.1 TCP/IP: v2.02l or later for NetWare 4.02 v3.00b or later for NetWare 4.10 Section 2.0 HARDWARE INSTALLATION --------------------------------- This section provides information on installing a single ATMworks 350L in a Novell Server. Digital Equipment Corporation's ATMworks 350L is compliant with the PCI 2.1 specification, which describes operation requirements. However, refer to the system manufacturer's documentation for any system specific installation instructions. CAUTION: To avoid possible damage to components of the ATMworks 350L card or your system, use the anti-static grounding wrist strap when handling the card. To install the ATMworks 350L on your computer: --------------------------------------------- 1. Shut down the system and power it off, but do not unplug the system from the power source. 2. Remove the cover of the system chassis. 3. Touch the system chassis or connect the copper end of the antistatic wrist strap to a metal component of the chassis to provide grounding. 4. Insert the ATMworks 350L into the appropriate bus slot. The EISA (and ISA) slots are longer than the PCI slots. 5. Press the card firmly into the slot to ensure that it is properly seated. 6. Using a Phillips screwdriver, tighten the retaining screw that holds the ATMworks 350L in place. 7. Replace the chassis cover and apply power to the machine. 2.1 Initial Hardware Verification Procedures After you have installed the ATMworks 350L hardware, you need to run the decdiag diagnostics utility provided with the card to ensure proper operation of the hardware. The diagnostics software must be run from DOS. You need to boot from DOS (5.0 or greater) disks and then run the diagnostics procedure. To initially test ATMworks 350L functionality: ---------------------------------------------- 1. Boot from the hard drive or, if DOS is not loaded, insert a DOS 5.0 or greater boot diskette into the diskette drive and reboot the machine. 2. When the command prompt appears, remove the DOS diskette and insert the "DOS Diagnostics" diskette. Change the working drive to the diskette drive. 3. From the command line, issue the "decdiag" command. 4. If desired, list the decdiag command set using the "help" command. 5. Execute the ATMworks 350L selftest by issuing the "selftest" command, which automatically executes each of the tests listed in "help" under "Specific diagnostic commands supported" except for hbi_int, sar_mem_e, and atm_external. 6. Execute the SAR extended memory test by issuing the "sar_mem_e" command. 7. If you have an external loopback cable, you can use the "atm_external" command to test the external ATM connection to the ATMworks 350L. a. Attach the loopback cable to the ATMworks 350L ports, connecting transmit to receive. b. Issue the "atm_external" command. 8. If any of the diagnostic tests fail, record the error message displayed and contact a Digital Authorized VAR or distributor, or Digital Customer Service. 9. If the ATMworks 350L passed all of the above tests, remove the loopback cable (if necessary) and connect the product's ports to your ATM switch. 10. Type "q" or "quit" to exit the diagnostic utility. 11. Remove the DOS Diagnostics diskette from the drive and reboot the machine. 2.2 Attaching Cables to the ATMworks 350L Take care to protect optical connectors against dust and physical contact with all other objects. Never touch the ends of the cables. All disconnected optical connectors must be covered with dust protecting caps. Do not remove these caps until immediately before mounting the ATMworks 350L in the chassis. When connecting optical cables between the ATMworks 350L and the switch, care must be taken so that the transmitter cable of the switch is connected to the receiver connector on the ATMworks 350L. Likewise, the switch's receiver cable must be connected to the transmitter connector on the ATMworks 350L. The LED on the card is lit when the ATMworks 350L is properly connected. When using simplex (single) SC connectors, ensure that the transmitter connector from the switch is attached to the connector marked with a receive symbol, and the receiver connector from the switch must be attached to the connector marked with a transmit symbol. When using a duplex SC connector assembly, the connector can only be plugged in the correct way. NOTE: Be careful not to twist or bend the optical cable to the point where it may break the glass fiber inside the cable. 2.3 RJ45 Pinout The pinout of the jack on the ATMworks 350L is different than a standard Ethernet RJ45 pinout. Ethernet loopback connectors will not operate correctly on this card. Cat 5 Pinout on the RJ45 Connector Jack on the adapters left to right: Pin Signal --- ---------- 1 Transmit + 2 Transmit - 7 Receive + 8 Receive - 2.4 ATMworks 350L Specifications 1. General PCI Adapter Technical Specifications for MMF and Category 5 Size: Single slot adapter PCI Frequency: Up to 33 MHz Bus Master: 32-bit bus master capability, bursting up to 64-byte burst size. Line code: NRZ Line rate: 155.52 Mbit per second Rate tolerance: +or- 100 ppm Power: Max 1.5 amps @ +5V, +or- 5% Max 0.2 amps @ +12V Temperature: Operating: 0 to 70 C Non-operating, storage: -40 to 100 C Humidity: 5% to 95% noncondensing 2. Multi-mode Fiber Technical Specifications Connector: SC style optical interface, multi-mode fiber Core diameter: 62.5 micrometer Cladding diameter: 125 mirometer Min. modal bandwidth: 500 MHz*km Operating distance: 0 to 2 km Transmitter type: LED Wavelength: 1260 to 1360 nm Max spectral width: 200 nm Mean launched power: -20 to -14 dBm Max extinction ratio: 10 dB Maximum rise time: 3 ns Min sensitivity: -30 dBm Max overload: -14 dBm Path power penalty: 1 dB 3. Category 5 Technical Specifications Connector: RJ45, 8-contact, shielded Category 5 jack UTP: Category 5 (4 twisted pairs) unused pairs are common mode terminated. Operating distance: 0 m to 100 m Transmitter type: Transformer-coupled differential line driver Differential Sig. Level: 940 mv to 1060 mv Rise/Fall time: 1.5 ns to 3.5 ns Receiver: Transformer-coupled differential line receiver with adaptive equalization Section 3.0 LOADING THE DRIVER SOFTWARE ---------------------------------------- The driver files must first be installed on the server before being configured to use specific ATM services. This section describes the loading of the driver files. Section 4 discusses the configuration options and procedures. To load the driver files: ------------------------- 1. On the server command line, enter the command: LOAD INSTALL 2. From the "Installation Options" menu select "Driver options" 3. From the "Driver Options" menu select "Configure network drivers" 4. From the "Additional Driver Actions" menu select "Select a[n additional] Driver" 5. Place the DOS-format Distribution Diskette (Disk 2) into the server floppy drive then press to scan for NetWare 4.x ODI server drivers using the default path of A:\. 6. When the pathname message comes up, accept the default. 7. Select YES in response to the question: "Do you want to copy the driver ?". This will copy the driver onto the server. Section 4.0 DRIVER CONFIGURATION -------------------------------- 4.1 Overview By default, the driver is configured to act as a LAN Emulation Client (LEC). If no configuration is loaded, the LEC uses the Interim Local Management Interface (ILMI) to retrieve the LAN Emulation Configuration Server (LECS) address from the connected switch. The LEC communicates with the LECS to connect to a LAN Emulation Server on the network. The NetWare LOAD command can be used to configure the driver to use Classical IP instead of LANE or to modify the LANE configuration. However, some of the ATM parameters that can be specified (such as an ATM address) are too long to be input using the standard NetWare installation interface. These ATM parameters can be specified on the from a Configuration File. 4.1.2 Creating Configuration Files Creating a Configuration File allows you to specify each command line parameter on a separate line for readability. Each configuration file you create should be named to indicate the driver type and should have a .cfg extension (for example CLIPSRV.CFG). To create a configuration file, use the commmand: LOAD EDIT SYS:SYSTEM\.CFG where is indicates the type of configuration. 4.1.3 Driver Configuration Types The ATMworks 350L driver can be configured as one of the following: 1. LAN Emulation (for IPX, IP or any of the ODI protocol stack) 2. Classical IP Server: it acts as the Address Resolution Protocol server for the entire LAN 3. Classical IP client (provides no ARP server function): - Using Permanent Virtual Channels (PVCs) only - Using Switched Virtual Channels (SVCs) only - Using a mix of SVCs and PVCs Classical IP and LAN Emulation can run simultaneously on the same NIC provided different frame types are used (See Section 3). 4.1.4 Hints on Selecting Ethernet Frame Types It is important to specify the correct Ethernet frame type to interoperate with Novell NetWare clients. If using the IPX protocol, match the driver's frame type with that of the clients. If using TCP/IP or NetWare/IP then select Ethernet_II or Ethernet_snap as the frame type. To allow client connections from all supported frame types, you can load the server driver multiple times, once for each frame type. You must bind a protocol for each instance. See the NetWare documentation for information on how to do this. 4.2 Configuration Parameters CLIP_CLIENT - Classical IP client. This keyword is used to determine whether Classical IP will be used by the driver. If you configure the NetWare server to be a Classical IP client then you must also provide the CLIP_PROT_ADDR_LOCAL and CLIP_SUBNET_MASK parameters. If using SVCs, you must also specify CLIP_SERVER_ATM_ADDR. CLIP_PROT_ADDR_LOCAL - Local Classical IP protocol address. This parameter provides the IP address for a station configured for Classical IP. Enter the address in dot notation format where nnn is a decimal value in the range 0 - 255: nnn.nnn.nnn.nnn CLIP_SERVER - Classical IP server. This keyword is used to determine whether Classical IP will be used by the driver. The station becomes the Classical IP ARP server. If you configure the NetWare server to be a Classical IP server then also include the CLIP_PROT_ADDR_LOCAL and CLIP_SUBNET_MASK parameters in the configuration file. Note that if you also include CLIP_CLIENT in the configuration file the driver will fail to initialize. There can be only one Classical IP server in a subnet. CLIP_SERVER_ATM_ADDR - Classical IP server's ATM address. If you configure the NetWare server to be a Classical IP client then this parameter is required. It provides the ATM address of the Classical IP server. The ATM address contains a 13 byte prefix, a 6 byte ESI, and a 1 byte selector. The address may be entered as nnnnnn..., or nn nn nn..., or nn-nn-nn... for a total of twenty bytes in hexadecimal notation (nn is one hexadecimal byte). The letters A-F may be entered in either upper or lower case. For example, a valid ATM address follows: 3999990000000008002BA56880AA000302FF1100 CLIP_SUBNET_MASK - Classical IP subnet mask. If you configure the server for Classical IP this parameter is required. It indicates how to partition IP addresses into subnetwork addresses and local host addresses. See the NetWare 4 TCP/IP Reference for more information. Enter the mask in dot notation format where nnn is a decimal number from 0 - 255: nnn.nnn.nnn.nnn LES_ADDR - LAN Emulation Server (LES) address. This parameter may be used to provide the address of the LAN Emulation Server. If this parameter is not provided the LAN Emulation Configuration Server will be used to locate the LES. Use this parameter in ELAN.CFG or another configuration file being used to start LAN Emulation. The ATM address contains a 13 byte prefix, a 6 byte ESI, and a 1 byte selector. The address may be entered as nnnnnn..., or nn nn nn..., or nn-nn-nn... for a total of twenty bytes in hexadecimal notation. The letters A-F may be entered in either upper or lower case. For example, a valid ATM address follows: 3999990000000008002BA56880AA000302FF1100 LIS - Classical IP Logical IP Subnet (LIS). This parameter allows you to set up PVCs to remote stations. This version of the driver can accept a maximum of two LIS parameters each containing up to eight PVCs. NOTE: It is necessary to set up your switch to support the PVC(s) you define at the end station. Also, if there are multiple switches between your end station and the remote station you must configure each switch to support the PVC(s). The format for entering this parameter follows: LIS =3D [MASK=3Dnnn.nnn.nnn.nnn, PVC=3D(VPI=3Dn, VCI=3Dn, PROT_ADDR_REMOTE=3Dnnn.nnn.nnn.nnn, ATM_ADDR_REMOTE=3Dnn-nn-nn-nn-nn-nn-nn-...), PVC=3D(VPI=3Dn, VCI=3Dn, PROT_ADDR_REMOTE=3Dnnn.nnn.nnn.nnn, ATM_ADDR_REMOTE=3Dnn-nn-nn-nn-nn-nn-nn-...)] where: MASK - is the subnet mask associated with the LIS PVC - requests a permanent virtual circuit and contains additional parameters required for the PVC: VPI - Virtual Path Identifier: 0-15 VCI - Virtual Channel Identifier: 31 - 255 PROT_ADDR_REMOTE - The IP protocol address of the station to which the PVC will be established. ATM_ADDR_REMOTE (optional) - The remote station's ATM address, 20 bytes in hexadecimal notation. The [] brackets are required to group all the parameters for a single LIS. The () brackets are required to group all the parameters for a PVC within. a LIS. NO_SIG - Disable signaling. This parameter may be used if PVCs are used exclusively and signaling is not required (no SVCs are being used). Note that PVCs can be used while signaling is active. SDH - Synchronous Digital Hierarchy framing. The default ATM framing is SONET, Synchronous Optical Network. To select SDH, Synchronous Digital Hierarchy, framing over the ATM link add the SDH parameter to the command line. The framing is controlled at the physical layer of the ATMworks 350L. UNI_30 - Changes the User-Network Interface version from the default (UNI 3.1) to UNI 3.0. 4.3 Sample Driver Configurations The following sections provide examples of configuration files for each of the "flavors" of driver: LAN Emulation, Classical IP client Classical IP server, and the use of PVCs. These are only examples; please update all addresses, IP and ATM, to reflect those in your ATM network. NOTE: In the following examples the ATM addresses are presented in the format that allows them to fit on one line. You may format them using hyphens as delimiters (39-99-99-00-00-00-00-...) in your configuration files to aid in readability. This driver supports either IPX or IP over LAN emulation. It also supports IP over Classical IP. Both LAN Emulation and Classical IP can be configured to run at the same time by using different frame types. NetWare uses the Ethernet_II or Ethernet_snap frame type for IP as well as IPX. If your network uses IP you may configure the driver to use the Ethernet_II frame type and either the ELAN.CFG file for LAN Emulation, or the CLIPxxxx.CFG files for Classical IP. If your network uses IPX you may configure the driver to use any of the frame types (provided Ethernet_II is not being used simultaneously for IP). Use the ELAN.CFG file for LAN emulation. 4.3.1 LAN Emulation Configuration The driver defaults to using LAN Emulation. To use LAN Emulation, the driver's LAN client needs to connect to a LAN Emulation Server. The client must have the ATM address of a LAN Emulation Configuration Server (LECS) that will connect the client to a LANE Server (LES). Normally, the switch will provide the LECS address to the client using ILMI. However, if that is not possible, the client will try to connect to a "well-known address" specified in the LANE Specification. If that is not possible, the client will use a reserved PVC (VPI=3D0, VCI=3D17). You can configure the client to connect directly to a LAN Emulation Server by specifying the LES ATM address in a configuration file. The ATM address is too long to specify on the command line, however. Example 1: IPX over LAN Emulation using a ELAN.CFG config file > LOAD d155mid NAME=3Dd155mib_8022 FRAME=3DEthernet_802.2 @ELAN.CFG > BIND IPX d155mib_elan NET=3D12345678 Contents of ELAN.CFG: --------------------- LES_ADDR =3D 3999990000000008002BA56880AA000302FF1100 NOTE: The NAME and FRAME arguments are is optional on the LOAD command. NET is required to specify the network number on the BIND command. The LOAD command must be followed by BIND. Example 2: IP over LAN Emulation using a config file > LOAD d155mid NAME=3Dd155mib_eii FRAME=3DEthernet_eii @ELAN.CFG > BIND IP d155mib_eii ADDRESS=3D195.1.1.2 MASK=3D255.255.255.0 NOTE: The MASK (subnet mask) and ADDRESS (IP address of the server) are required on the BIND command. If not supplied, the user is prompted by the system. Example 3: IPX and IP over LAN Emulation using the config file > LOAD d155mid NAME=3Dd155mib_elan FRAME=3DEthernet_802.3 @ELAN.CFG > LOAD d155mid NAME=3Dd155mib_eii FRAME=3DEthernet_eii @ELAN.CFG > BIND IPX d155mib_8022 NET=3D12345678 > BIND IP d155mib_eii ADDRESS=3D195.1.1.2 MASK=3D255.255.255.0 4.3.2 Classical IP Client Configuration To set up Classical IP such that your NetWare server is a Classical IP client (there is another system in the network that is the Classical IP ARP server) each of the following parameters are required on the command or in a configuration file: CLIP_CLIENT CLIP_PROT_ADDR_LOCAL =3D CLIP_SUBNET_MASK =3D CLIP_SERVER_ATM_ADDR =3D <40-char. ATM address> Example: Specifying a Configuration File (CLIPCLNT.CFG) on the command line: > LOAD d155mid NAME=3Dd155mid_1_eii FRAME=3DEthernet_II @CLIPCLNT.CFG > BIND IP d155mid_1_eii ADDRESS=3D196.1.1.2 MASK=3D255.255.255.0 Contents of CLIPCLNT.CFG: ------------------------- CLIP_CLIENT CLIP_PROT_ADDR_LOCAL =3D 192.1.1.2 CLIP_SUBNET_MASK =3D 255.255.255.0 CLIP_SERVER_ATM_ADDR =3D 3999990000000008002BA56880AA000302FF1100 NOTE: The ADDRESS and MASK parameters on the BIND command MUST match the address/subnet mask specified on the LOAD command (whether on the command line or in a configuration file). 4.3.3 Classical IP Server Configuration To set up Classical IP to make your NetWare server the Classical IP ARP server, the following parameters must be specified on the command line or in a configuration file: CLIP_SERVER CLIP_PROT_ADDR_LOCAL =3D CLIP_SUBNET_MASK =3D Example: Specifying a Configuration File (CLIPCLNT.CFG) on the command line: > LOAD d155mid NAME=3Dd155mid_1_eii frame=3DEthernet_II @CLIPSRVR.CFG > BIND IP d155mid_1_eii ARP=3Dyes ADDRESS=3D196.1.1.2 MASK=3D255.255.255.0 Contents of CLIPSRVR.CFG: ------------------------- CLIP_SERVER CLIP_PROT_ADDR_LOCAL =3D 196.1.1.2 CLIP_SUBNET_MASK =3D 255.255.255.0 NOTE: The ADDRESS and MASK parameters on the BIND command MUST match the address/subnet mask specified on the LOAD command (whether on the command line or in a configuration file). 4.3.4 PVC Configuration over Classical IP You can create up to 8 PVCs in each of two Classical IP Logical IP Subnets (LIS). The NO_SIG parameter is optional. Signaling can be active even if you are using PVCs exclusively. The following example sets up two PVCs in a single LIS. Example: Setting up two PVCs in a single LIS. > LOAD d155mid NAME=3Dd155mid_pvc frame=3DEthernet_II @CLIPPVC.CFG > BIND IP d155mid_pvc ADDRESS=3D196.1.1.2 MASK=3D255.255.255.0 Contents of CLIPPVC.CFG: ------------------------ CLIP_CLIENT CLIP_PROT_ADDR_LOCAL =3D 192.1.1.2 CLIP_SUBNET_MASK =3D 255.255.255.0 LIS =3D [MASK=3Dnnn.nnn.nnn.nnn, PVC=3D(VPI=3Dn, VCI=3Dn, PROT_ADDR_REMOTE=3Dnnn.nnn.nnn.nnn, ATM_ADDR_REMOTE=3Dnn-nn-nn-nn-nn-nn-nn-...), PVC=3D(VPI=3Dn, VCI=3Dn, PROT_ADDR_REMOTE=3Dnnn.nnn.nnn.nnn, ATM_ADDR_REMOTE=3Dnn-nn-nn-nn-nn-nn-nn-...)] NOTE: It is necessary to set up your switch to support the PVC(s) you define at the end station. Also, if there are multiple switches between your end station and the remote station you must configure each switch to support the PVC(s). Section 5.0 VERIFYING THE INSTALLATION --------------------------------------- A NetWare 4.x system not running NetWare/IP can verify or alter the configuration parameters for the ATMworks 350L by selecting the INSTALL option "NCF file options". Select "Edit AUTOEXEC.NCF file" to verify or alter the load and bind command lines. A system running NetWare/IP can verify the configuration by running INETCFG.NLM. View the configuration to ensure that the installation went as planned. 5.1 Restarting NetWare to use the ATMworks 350L When you are finished with the installation and the configuration parameters, DOWN the server, and EXIT to DOS. Make sure that the configuration file contains the correct values for your network. Failure to join an Emulated LAN will occur if you select LES_ADDR and have an error in the LES ATM address. Or, a failure to connect to another node on an IP network will occur if your IP address or the ARP server's ATM address is incorrect. Restart the server with the ATMworks 350L NetWare 4.x ODI server driver by entering the following command at the DOS prompt: SERVER The changes made to the STARTUP.NCF and AUTOEXEC.NCF files, or to the NetWare/IP files in section II above, take effect. -------------------------------------------------------------------------- ***TRADEMARKS*** Digital and ATMworks 350L are trademarks of Digital Equipment Corporation. Novell and NetWare are registered trademarks and NetWare Loadable Module and NLM are trademarks of Novell, Incorporated.