============================================================================= IBM Auto LANStreamer MC32 Information 3/20/97 ============================================================================= UPDATES ------- The original diskette is now two diskettes. See "Diskette Organization" below for details. The adapter diagnostics (@8FA2.DGS 06/13/96) are updated to fix a continuous mode problem in the IBM Server 320 and 520 systems. The NDIS-2 drivers (IBMMPC.OS2/DOS) are updated to Version 4.54. The Netware driver (IBMMPCO.LAN) is updated to Version 2.07. (Certified) The NDIS-3 drivers are added at Certified/Tested levels: Windows NT STREAMER.SYS Version 3.06 Windows 95 STREAMER.VXD Version 2.83 Windows FW STREAMER.386 Version 2.83 Full Duplex Operation (FDX) is now supported for the following drivers: NDIS-2 OS2 IBMMPC.OS2 Version 4.54 NDIS-2 DOS IBMMPC.DOS Version 4.54 NW Server IBMMPCO.LAN Version 2.07 Windows NT STREAMER.SYS Version 3.06 See additional comments under "FDX" below. DISKETTE ORGANIZATION --------------------- The original 'Option/Driver' diskette is now two diskettes: an 'Option/Diags/NDIS-3' diskette and a 'Device Driver' diskette. The new Option/Diags/NDIS-3 diskette contains the adapter description file (ADF), the adapter diagnostics file (DGS), Ring Diagnostics, and the NDIS-3 drivers (Windows NT, Windows 95 and Windows For Workgroups) which were not originally shipped with the adapter. The new Device Driver diskette contains the NDIS-2 and Netware drivers. See FILELIST.LOG on each diskette for a brief description of the included files. COMMON PROBLEMS --------------- Windows NT 4.0 needs to be at ServicePack-2 (SP2) or have the NDIS.SYS hot fix mentioned in Microsoft KnowledgeBase Article # 156324 or it will improperly configure any MC adapter. (G/A: NDIS.SYS 120,976 bytes 08-08-96 09:30pm) (SP2: NDIS.SYS 122,224 bytes 09-27-96 11:17am) If performing Remote Unattended Installs (RUI) on Windows products, the Procedures and Diskette available within IBMRUI.EXE available for the Auto LANStreamer PCI Adapter also apply. Make sure the files in the network resource share contain the new NDIS.SYS if installing Win NT 4.0. With LAN Server, if multiple LANStreamer adapters are installed, in MPTS/LAPS, configure the LoopBack parameter to 'NO' for all adapters. In LAN Server, if experiencing NET3056 / NET3502 / SYS0054 errors, from the OS2 desktop, remove and reconfigure the adapters by using the "IBM LAN Services" icon - not the "MPTS" icon. If experiencing LTC0029 errors using a CID process, and the problem can be corrected by adding "/MCA" to the DEVICE=C:\IBMCOM\IBMMPC.OS2, the proper way to correct the problem is to copy the ABIOS.SYS and *.BIO files from the system Reference Disk to the OS2 subdirectory. If experiencing problems with large frames, the problem can be due to a complex network; maximum frame size may be restricted by an 8272 switch (4540 bytes) or a bridge (2052, 4472 or 8144 bytes). If installing multiple adapters, configure all adapters to FAIRNESS=ON. If attempting to use the adapter in promiscuous mode, such as a system monitor, the device drivers must support promiscuous copy. NDIS-2 IBMMPC.DOS/OS2 Version 4.01 or newer NDIS-3 STREAMER.SYS/386/VXD Version 3.03 or newer NETWARE IBMMPCO.LAN All versions DOS ODI IBMMPCO.COM All versions (NOTE: Using promiscuous copy places a higher load on the adapter and system resources.) SYSTEM COMPATIBILITY ISSUES --------------------------- The maximum number of adapters in a system may be limited by the Network Operating System (ie, LAN Server 3.0 = 4, LAN Server 4.0 = 8), the number of slots available, the system bus bandwidth, or several other system resource issues. Due to a PS/2 Bus Interface Control chip problem, the adapter will not work in any Model 9577 25/50 MHz systems. Compatibility problems have been encountered when installing the adapter in a split bus (MC/PCI) system; this resulted in a hardware change on the adapter and several device driver updates. The updated adapter carries a FRU level of 42H2706 or 42H2716 (depending on geography). IBM systems affected are: 6575-xxx 8639-Mxx 6585-xxx 8640-Mxx 6876-xxx 8641-MZx 6886-xxx 8641-MDx 8642-xxx IBM Server 320/520 Compatibility: - system should be at BIOS 23A or newer and set to "MCABiased" * press F1 key during memory count. * select "Advanced Setup" option at "Configration/Setup Utility" * select "System Resource Balance" * change the system resource balance from "Balanced" to "MCA biased" - any MC RAID adapters should be at firmware 2.19 or newer - any PCI RAID adapters should be at firmware 2.41 or newer - Lan Server 4 needs to be at FixPaks WRx8210 & IPx8227 or newer - WARP Server needs to be at FixPaks WRx8210 & IPx8260 or newer - in Lan Server, set adapter interrupts the same - in Lan Server, in PROTOCOL.INI ibmmpc_nif set LOOPBACK=NO - in Lan Server, default values in PROTOCOL.INI netbeui_nif need to be changed: DATAGRAMPACKETS should be increased from 10 to 80 or higher and PACKETS decreased from 350 to 280 or less - in Netware 4.11, if using both MC and PCI Streamer adapters, the MC adapter(s) must be loaded first IBM Server 720 Compatibility: - system should use the default MCA-biased planar ADF, check the file on the Server 720 Reference Disk (MCA: PFEE7.ADF 16,080 bytes 07-26-95 01:17pm) (PCI: PFEE7.ADF 17,049 bytes 10-24-95 03:43pm) - system should be at BIOS 9 or newer. - any MC RAID adapters should be at firmware 2.19 or newer - any PCI RAID adapters should be at firmware 2.41 or newer - Lan Server 4 needs to be at FixPaks WRx8210 & IPx8222 or newer - WARP Server needs to be at FixPaks WRx8210 & IPx8260 or newer - install from slot 1 toward slot 5 (do not use slots 6 or 7) - in Lan Server, set adapter interrupts the same - in Lan Server, in PROTOCOL.INI ibmmpc_nif set LOOPBACK=NO - in Lan Server, manually add the following to each instance of ibmmpc_nif in \IBMCOM\PROTOCOL.INI FIFOTHRESHOLD=10 - in Netware, load the driver with parameters LOAD IBMMPCO.LAN RXFIFO=32 TXFIFO=32 - in NT, configure each installed adapter with FIFO threshold (set to) 10 IBM PC 730/750 Compatibility: - system should be at BIOS 45A or newer to avoid warm-boot failures FULL DUPLEX OPERATION --------------------- The Auto LANStreamer MC Adapter is a high-performance Token-Ring Adapter capable of media-speed throughput. Switching from half-duplex operation to full-duplex operation effectively doubles the MC bus bandwidth required by the Auto LANStreamer MC Adapter. If you are using more than one adapter, switch to FDX and you begin to lose sessions and see network adapter congestion, it may be due to exceeding the bandwidth available on the system's MC bus. To operate the adapter in Full Duplex mode, the adapter must be at microcode level 'D0' or newer. The microcode is in flash and can be upgraded without removal from the system. Obtain STRFLASH.EXE version 1.50 or newer. Device drivers IBMMPC.OS2 and IBMMPC.DOS Version 4.54 and newer implement a new parameter called EnableTRFDX. The default setting for EnableTRFDX is "NO", so this parameter must be present in the ibmmpc_nif section of PROTOCOL.INI and set to "YES". For OS/2, use LAPS/MPTS to configure LAN Transports. Get to the "Current Configuration" window, highlight the LANStreamer Adapter entry, and select the Edit pushbutton. Look for the item, "Enable token ring full-duplex operation" and make sure that it is set to "YES". Exit LAPS/MPTS, saving the changes, shutdown and reboot. For DOS/LSP, use DXMAID to perform a similar function and reboot the system afterwards. Device driver STREAMER.SYS Version 3.06 and newer implement a new parameter called EnableFullDuplex. The default setting for EnableFullDuplex is "NO", so this parameter must be set to "YES". Using the network setup function in Windows NT, click through to the screen where the parameters for STREAMER1 can be customized. On that screen there will be a parameter to enable or disable full-duplex operation; make sure that it is enabled. The NetWare Server device driver IBMMPCO.LAN, has a new FDX parameter that can be specified on the LOAD line when loading IBMMPCO.LAN on the NetWare server; that parameter is ENABLEFDX. If ENABLEFDX is specified on the IBMMPCO.LAN load line, then IBMMPCO.LAN will attempt to open the adapter in FDX mode; if that open attempt fails, then IBMMPCO.LAN will not retry the open in HDX mode. If the adapter is configured for AutoSense (and ENABLEFDX is not specified) IBMMPCO.LAN will automatically attempt to open the adapter in FDX mode and, if unsuccessful, will then open the adapter in HDX mode. NOTE: If you have multiple adapters installed and would like to enable full-duplex operation on all adapters, be sure to set EnableTRFDX, EnableFullDuplex, or ENABLEFDX for each instance of the device driver. DETERMINING MICROCODE LEVEL --------------------------- Begin by getting to the Main Menu of the "Reference Diskette" by using one of the following. (This will depend on your actual system type. If in doubt, check the manual that came with your system.) a) perform a reboot (CTRL-ALT-DEL), while on the IBM Personal System/2 Logo screen, press PF1 b) perform a reboot (CTRL-ALT-DEL), hit CTRL-ALT-INS while the cursor is in the upper right-hand corner c) insert the system's Reference Diskette and reboot (CTRL-ALT-DEL) On the Main Menu, press CTRL-A to get to Advanced Diagnostics. (If you used the Reference Diskette, you will get an Instruction Panel. Per the Instruction Panel, replace the Reference Diskette with the Diagnostic Diskette, then press ENTER.) On the Advanced Diagnostics Menu, select Run System Checkout and press ENTER. (If you get a Question Page 1 of 2 panel, press Y if you have a second Diagnostic Diskette, otherwise press N.) If the Auto LANStreamer MC is on the list, press Y. (If not: you do not have an Auto LANStreamer in your system, it is not properly installed, the Option Diskette diagnostic file was not copied, or the adapter is defective.) On the Test Selection Menu, select Run The Tests One Time and press ENTER. On the Device Test Menu, use the down arrow to select Auto LANStreamer MC and press ENTER. You will be told the LANStreamer MC32 is in Slot X. Select the cable type in use (If you are not sure, select RJ45 STP/D + Token Ring Network.) and press ENTER. On Question Page 1 of 2, press N. On Instructions Page 1 of 3, press ENTER. On Instructions Page 1 of 2, press PF8. On Instructions Page 2 of 2, note the Code Level. It will appear as 000001E6E6F_F_C_F_40. The four blanks in the Code Level translate as: 000001E6E6F1F3C2F340 = 13B3 = B3 code 000001E6E6F1F4C2F440 = 14B4 = B4 code 000001E6E6F1F7C3F340 = 17C3 = C3 code 000001E6E6F1C1C4F040 = 1AD0 = D0 code Press ENTER. On Question Page 1 of 1, press Y. On Instructions Page 1 of 1, press ENTER. On the Test Selection Menu, press PF3. On Instructions Page 1 of 1, press ENTER. INSTRUCTION MANUAL UPDATES -------------------------- 1) All pages: The original 'Option/Driver' diskette is now two diskettes: 'Option/Diags/NDIS-3' and 'Device Driver'. 2) Page 1-7: To comply with ENN 55022 Class A, VDE 0871 Class A, and VCCI Class 1 concerning limits on radio interference, use of the adapter with UTP requires cabling with a ferrite core (IBM P/N 60G0659 or equivalent). The end of the cable with the ferrite core attaches to the network. If using UTP cabling, a media filter should not be used, as this has been incorporated onto the adapter and the use of an external filter could result in abnormal operation. 3) Page 2-5 If Automatic Configuration is used, Data Streaming will be Step 1: enabled. This can cause hangs, traps, abends or data errors in a non-streaming system. The IBM 32 bit MC systems that do not support streaming (all models unless models are specified) are: All 16 bit MC systems 8600 8570 9556 8573 9576 8580 9577 8590 9590 8595 9595-OLx 4) Page 2-6 The AutoSense function was modified beginning with level D0. Step 3: If AutoSense in used, the adapter will not open as the only station on the ring, regardless of whether the card is new. This change is a result of compatibility issues with speed detecting hubs. Servers should be set to 16 or 4 MBps. 5) Page 2-6 The generic requirement that multiple adapters be set to Step 3: the same interrupt level has been removed. 6) Page 2-10: Follow the instructions in file IBMMPCO.DOC. 7) Page 3-7: The various microcode levels will be shown as: 0000 01E6 E6F1 F3C2 F340 = B3 0000 01E6 E6F1 F4C2 F440 = B4 0000 01E6 E6F1 F7C3 F340 = C3 0000 01E6 E6F1 C1C4 F040 = D0 8) Page A-19: Disregard the following information. The NetWare files are NOT included with the Options/Driver diskette. ---------------------------------------------------------------- | Note: The following files are included in the NOVELL/DOS | | subdirectory on the Auto LANStreamer MC Adapter | | Option/Driver Diskette for your convenience. Copy the files | | to the target directory if you have not obtained more recent | | copies from your NetWare manufacturer. Use the file | | datestamps to determine which of two files is more recent. | | | | LSL.COM | | IPXODI.COM | | ROUTE.COM | | NETX.EXE | ---------------------------------------------------------------- IBM, Streamer, LANStreamer, Micro Channel and OS/2 are trademarks of IBM Corporation Netware is a trademark of Novell, Inc. Windows NT, Windows 95, WFW, and Windows For Workgroups are trademarks of Microsoft Corporation