IBM 16-4 User Manual
16/4 Token-Ring PCI Management Adapter
User’s Guide
Note
Before using this information and the product it supports, be sure to read “Safety Information” on page 81 and “Appendix G.
Notices” on page 79.
First Edition (April 2000)
This edition applies to the IBM 16/4 Token-Ring PCI Management Adapter.
You can submit comments online to http://www.ibm.com/networking/support/feedback.nsf/docsoverall
© Copyright International Business Machines Corporation 2000. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this manual .......................vii
Who should read this manual....................vii
How this manual is organized ...................vii
Related publications .......................viii
Chapter 1. Introduction to the IBM 16/4 Token-Ring PCI Management
Adapter ...........................1
Adapter installation checklist ....................1
Environment limitations on number of adapters .............2
Package contents ........................2
Automatic Configuration and Power Interface (ACPI) ..........2
WakeonLAN.........................2
Chapter 2. Installing the adapter hardware ..............5
Installing the adapter .......................5
Selecting adapter cables......................5
Chapter 3. Software installation ..................7
Novell NetWare 3.12 Server ....................9
Server driver installation in new NetWare 3.12 Server .........10
Server driver installation in existing NetWare 3.12 Server ........11
Novell NetWare 4.11 Server ....................12
Server driver installation in new NetWare 4.11 Server..........13
Server driver installation in existing NetWare 4.11 Server ........14
Novell NetWare 5.0 Server ....................16
Server driver installation during NetWare 5.0 Server installation ......16
Server driver installation in existing NetWare 5.0 Server .........17
Novell Client DOS/Windows 3.1x ..................18
OS/2 NDIS 2 device driver using MPTS................19
OS/2 NDIS 2 device driver using other installation programs ........20
OS/2 Novell NetWare Requester ..................20
DOS NDIS 2..........................21
DOS Novell NetWare Requester (16-bit) ...............22
Windows NT Version 3.51 .....................23
Windows NT Version 4.0 .....................24
Windows 95 ..........................25
Installing the driver when Windows 95 Retail is already installed......25
Installing the driver when Windows 95 OSR2 is already installed .....26
Installing the driver for a first-time Windows 95 installation ........26
Windows 98 ..........................28
Installing the driver for a first-time Windows 98 installation ........28
Installing the driver when Windows 98 is already installed ........29
Windows 2000 .........................30
Installing the driver for a first-time Windows 2000 installation .......30
Updating the driver when Windows 2000 is already installed .......32
Remote unattended installation of Windows 95, Windows 98, Windows 2000,
and Windows NT .......................32
Novell IntranetWare Client for Windows NT ..............32
Novell Client for Windows 95....................33
Windows for Workgroups with NDIS 3 ................33
Managed Driver Upgrade for Windows 95, Windows 98, Windows NT, and
Windows 2000 ........................34
Running Managed Driver Upgrade locally ..............34
© Copyright IBM Corp. 2000 iii
Running Managed Driver Upgrade remotely .............35
Chapter 4. Problem solving....................37
Starting the troubleshooting process .................37
Using Troubleshooting Utility ....................37
Installing Troubleshooting Utility ..................38
Starting Troubleshooting Utility ..................38
Using Troubleshooting Utility ...................38
Running adapter diagnostics ....................42
Running 4/16 Mbps diagnostics ..................42
Understanding the adapter LEDs and labels ..............43
Understanding the adapter LEDs .................44
Understanding the adapter labels .................45
Solving problems with driver installation ................45
Solving an adapter communication problem ..............46
Using PCISETUP ........................46
DOS, Novell, Windows, or Windows 95 (adapter driver not in CONFIG.SYS) 46
DOS, Novell, Windows, or Windows 95 (adapter driver in CONFIG.SYS) 47
OS/2 ...........................47
Windows NT .........................47
Contacting IBM product support...................47
Downloading code from the Web ..................47
Tech tips and frequently asked questions ...............47
Other performance enhancements..................47
Appendix A. CD-ROM content and software packages .........49
Software packages .......................50
Diskette images ........................50
Product documentation ......................51
Appendix B. NDIS 2 device driver parameters ............53
Appendix C. NDIS 2 device driver messages .............59
Appendix D. Novell NetWare Server driver parameters .........65
Appendix E. Novell NetWare Server messages ............71
Appendix F. Novell NetWare DOS ODI driver parameters ........77
Appendix G. Notices ......................79
Trademarks ..........................80
Safety Information ........................81
Telecommunications Safety Requirements in the United Kingdom .....85
Statement of Compliance with the United Kingdom Telecommunications Act
1984 ...........................85
Electronic Emission Notices ....................85
Federal Communications Commission (FCC) Statement .........86
Other Electronic Emission Notices for STP Media ............86
Industry Canada Class B Emission Compliance Statement ........86
Avis de conformité aux normes d’Industrie Canada ..........86
European Norm (EN) Statement .................86
Hinweis zur Elektromagnetischen Verträeglichkeit (EMVG) ........87
Japanese Voluntary Control Council for Interference (VCCI) Statement . . . 87
Other Electronic Emission Notices for UTP Media ............87
Federal Communications Commission (FCC) Statement .........87
iv IBM 16/4 Token-Ring PCI Management Adapter
Industry Canada Class A Emission Compliance Statement ........88
European Norm (EN) Statement .................88
Japanese Voluntary Control Council for Interference (VCCI) Statement . . . 89
Taiwanese Class A Warning Statement ...............89
Power Cord Notices for UTP Media ................89
IBM License Agreement for Productivity Aids ..............90
IF YOU DOWNLOAD OR USE THIS PROGRAM YOU AGREE TO THESE
TERMS. .........................91
NetWare Network Computing Products from IBM ............92
Protection and Security ......................92
Glossary ...........................97
Index ............................103
Contents v
vi IBM 16/4 Token-Ring PCI Management Adapter
About this manual
This manual contains the information you need to install and use the IBM 16/4
Token-Ring PCI Management Adapter.
Also on the CD-ROM are the installation aids, device drivers, and documentation for
the adapter.
Who should read this manual
This manual is intended for use by network administrators and other end users of
the IBM 16/4 Token-Ring PCI Management Adapter who install token-ring adapter
hardware and software.
How this manual is organized
“Chapter 1. Introduction to the IBM 16/4 Token-Ring PCI Management Adapter” on
page 1 describes the adapters covered in this manual, gives a checklist for
installation, and describes some of the features of the adapters.
“Chapter 2. Installing the adapter hardware” on page 5 describes the procedure for
installing the adapter into your computer.
“Chapter 3. Software installation” on page 7 describes the procedure for software
installation for a number of network operating environments.
“Chapter 4. Problem solving” on page 37 describes troubleshooting procedures and
fixes that might be needed for your environment.
“Appendix A. CD-ROM content and software packages” on page 49 describes the
files that are on the adapter CD-ROM.
“Appendix B. NDIS 2 device driver parameters” on page 53 lists the NDIS 2
parameters, describes their usage, and lists their values.
“Appendix C. NDIS 2 device driver messages” on page 59 lists the NDIS 2 system
messages, explains the meaning, and lists user actions.
“Appendix D. Novell NetWare Server driver parameters” on page 65 lists the Novell
and LAN Client parameters, describes their usage, and lists their values.
“Appendix E. Novell NetWare Server messages” on page 71 lists the Novell and
LAN Client messages, explains the meaning, and lists user actions.
“Appendix F. Novell NetWare DOS ODI driver parameters” on page 77 lists the
Novell parameters, describes their usage, and lists their values.
“Appendix G. Notices” on page 79 lists the legal notices required for the IBM 16/4
Token-Ring PCI Management Adapter.
© Copyright IBM Corp. 2000 vii
Related publications
Refer to these publications for additional information:
v IBM Token-Ring Adapter Features
v ISO/IEC 8802-5:1998 Base Standard 4/16 HDX and related amendments
v IBM Token-Ring Network Problem Determination Guide, SX27-3710
v IBM LAN Technical Reference IEEE 802.2 and NETBIOS API, SC30-3587
v IBM Transmission Control Protocol/Internet Protocol Version 2.1 for DOS:
Programmer’s Reference, SC31-7046
v LAN Adapter and Protocol Support Configuration Guide, S96F-8489
v MPTS/2 Configuration Guide, S10H-9693
v IBM LAN Server Command and Utilities, S10H-9686
v Guide to LAN Server Books, S10H-9688
v DOS LAN Services and User’s Guide, S10H-9684
v Microsoft LAN Manager Installation and Configuration Guide
v Microsoft Windows NT System Guide
v Novell Workstation for DOS and MS Windows
v Novell NetWare installation and system administration manuals appropriate to the
version of Novell NetWare you have installed
IBM adapter books and other documentation are available on the IBM Networking
Web site:
http://www.ibm.com/networking
viii IBM 16/4 Token-Ring PCI Management Adapter
Chapter 1. Introduction to the IBM 16/4 Token-Ring PCI Management Adapter
This chapter describes the adapter, the contents of the adapter kits, and the other
materials you will need to install the adapter.
It is important that you are familiar with the computer in which the adapter will be
installed and the computer’s operating system and network software.
The adapter is 32-bit, bus-master, token-ring for the PCI bus architecture. The
unique, high-quality filter design supports connection to a token-ring network that is
wired with shielded twisted-pair (STP) or unshielded twisted-pair (UTP) cabling. The
adapter can be used in PCI-compatible slots that operate at speeds up to 33 MHz.
Features of this adapter include:
v Adapter management capability that is provided by SNMP.
v Desktop Management Interface (DMI) provided by the LAN Adapter Management
Agent. For an end-to-end management solution, you can use the agent in
conjunction with the Nways
Manager for AIX®Version 1.2 or later.
v Automatic ring-speed detection.
v Support for a wide variety of network operating systems and network
applications.
v Support for full-duplex (FDX), token-ring LAN operation.
v Support for microcode update.
v Automatic configuration of I/O, memory, ROM space, and interrupt level by PCI
BIOS on power-up.
v Designed for use with either a half-size or full-size, 5-V or 3.3-V signaling, 32-bit
or 64-bit PCI-bus slot.
v The IBM 16/4 Token-Ring PCI Management Adapter uses less than 1 watt of
power.
®
Workgroup Manager Version 1.1 or later and Nways
See IBM Token-Ring Adapter Features for information regarding the following
features:
v DHCP
v Remote Program Load (RPL)
v LAN Adapter Management Agent
v Route Switching
v Class of Service (CoS)
v Redundant NIC (RNIC)
v Tivoli
®
Management Agent
Adapter installation checklist
To install your adapter, complete the following steps. You might want to mark this
page for easy retrieval or make a copy for reference.
1. Prepare for installation. You will need the following items:
v The manual provided with your computer
v The manual provided with your network operating system or network
application
v Your operating system and network application software
© Copyright IBM Corp. 2000 1
2. Check the shipping package contents list “Package contents”.
3. Install the adapter hardware. See “Chapter 2. Installing the adapter hardware”
on page 5.
4. Install the adapter software. See “Chapter 3. Software installation” on page 7.
After the software is installed, installation is complete.
Environment limitations on number of adapters
There is a limit to the number of adapters that can be accommodated in certain
operating environments. The limits are listed in the following table.
Table 1. Environment limitations
Device Driver Maximum Number of adapters
Novell ODI OS/2
Novell ODI DOS Client 1
NDIS 2.0 DOS 1
®
Client 2
Package contents
The IBM 16/4 Token-Ring PCI Management Adapter comes with the following
features:
v Automatic Configuration and Power Interface (ACPI)/PCI power management
feature
v Wake on LAN feature
These features are described in the following sections.
Automatic Configuration and Power Interface (ACPI)
If your computer supports ACPI, then it has built-in energy-saving capabilities.
When ACPI is enabled (usually through the computer BIOS settings), the operating
system is allowed to control the power management features of your computer. Not
all operating systems support ACPI BIOS mode. Refer to your operating system
documentation to determine if ACPI is supported. Refer to your computer system
documentation to determine if ACPI BIOS is offered and the method by which it can
be enabled. The adapter implements the PCI Bus Power Management Interface
Specification Version 1.0 that works together with ACPI. Under control of the
operating system, the adapter (and the entire system) can be placed in various
power-saving modes and be dynamically configured to look for network
protocol-specific events. Upon detection of these events, the adapter can signal a
wake-up condition which will bring the system to a fully-powered (operational) state.
Some systems might need to be configured through BIOS settings
(configuration/setup utilities) to allow PCI devices to wake a system. Refer to your
computer system documentation for automatic power-on feature settings (or PCI
wake-up features).
Wake on LAN
Adapters that support this feature can turn on a system that is powered off. The
adapter uses an auxiliary 3-volt power pin that is available on the PCI bus
beginning with PCI version 2.2. No additional auxiliary power cables are required.
The 3-volt PCI auxiliary power pin supplies power to the adapter. A control register
on the adapter determines whether the adapter is powered on by the 3-volt auxiliary
power source. This register is controlled by the system BIOS. If the BIOS enables
the control register bit, then the adapter always has a source of power, even when
2 IBM 16/4 Token-Ring PCI Management Adapter
the system is powered off (system power cord is connected to a live power outlet).
When the system is powered off, the adapter automatically inserts into the network
and looks for a special frame. This frame is commonly referred to as a magic
packet. Upon detection of the magic packet, the adapter signals the system to turn
on the power supply, thus turning on the computer system. The magic packet is a
frame sent by another computer system usually running an application that provides
remote system management.
Attention: Some PCs with multiple PCI slots that support Wake on LAN and
3.3-volt auxiliary power may not have an adequate 3.3-volt power supply to power
more than just a few of the slots with auxiliary 3.3 volts. Check with your PC
supplier to determine the number of PCI slots that can be concurrently populated,
and still meet the current limit of 375 mA per slot (for auxiliary 3.3 volts). This limit
is specified in the PCI Bus Power Management Interface Specification Revision 1.1.
Chapter 1. Introduction to the IBM 16/4 Token-Ring PCI Management Adapter 3
4 IBM 16/4 Token-Ring PCI Management Adapter
Chapter 2. Installing the adapter hardware
This chapter describes how to install the IBM 16/4 Token-Ring PCI Management
Adapter.
Installing the adapter
Your adapter comes configured from the factory with RPL/PXE and expansion ROM
enabled.
Before you begin to install this adapter, be sure to read “Safety Information” on
page 81.
To install your adapter, perform the following procedure:
1. Switch OFF the PC and all attached devices.
Note: In the U.K., by law, telephone line cables must be disconnected from
the PC before the power cord.
2. Remove the power cord from the outlet.
3. Remove all cables from your PC. Label each cable for easier reconnection at
the end of this procedure.
4. Follow the instructions provided in your PC manual for removing the cover or
otherwise accessing the adapter slots and inserting the adapter.
5. Install the adapter according to the instructions for adapter installation in the
manual that came with your PC.
6. Secure the adapter in the PCI slot with the retaining screw or other bracket
lockdown mechanism.
7. Reinstall all removed covers.
8. Connect the token-ring cable to the adapter and to the network. See “Selecting
adapter cables” for a description of the correct token-ring cables to use.
9. Reconnect all cables to your computer and then connect the power cord.
Follow all safety instructions.
Note: In the U.K., by law, the power cord must be connected before the
telephone line cable.
10. The hardware installation is complete. See “Chapter 3. Software installation” on
page 7.
Selecting adapter cables
To connect your adapter to a token-ring network, you will need one of the cables
shown in Figure 1 on page 6. These cables are not included with the adapter.
© Copyright IBM Corp. 2000 5
Figure 1. STP and UTP cables
The network end of the cable must be compatible with the network faceplate or
other device to which the adapter will be connected.
Note: No more than one data cable may be connected to the adapter at a time.
Your adapter can use any of these cables.
6 IBM 16/4 Token-Ring PCI Management Adapter
Chapter 3. Software installation
This chapter describes how to install the driver software for your token-ring adapter.
To install the software, perform the following procedures:
1. Get the latest level of LAN driver updates for your operating system to ensure
that your code is at the latest level.
2. Make sure that your adapter has already been installed in your computer. If it
has not, follow the instructions in “Chapter 2. Installing the adapter hardware” on
page 5.
3. Get the driver for your environment. There are three places to find the driver.
We recommend the first one listed here. All three methods will place the driver
in a directory according to the structure in Table 2 on page 8.
v Method A: Get the driver from a software package on the IBM Networking
Web site. This will ensure that you get the latest driver.
a. Go to x:\startcd.htm (where x is your CD-ROM drive).
b. Select your adapter from the section IBM Networking Web site - current
information.
c. Select Downloads and select the appropriate software package for your
environment.
d. Run the package to expand the files. The driver will be placed in the
directory listed in Table 2 on page 8.
Note: You can also access the Web site directly at
http://www.ibm.com/networking/support.
v Method B: Use the driver shipped on this CD-ROM directly with your network
operating system’s installation software. Note the directory containing the
driver (see Table 2 on page 8).
v Method C: Get the driver from a software package shipped on this CD-ROM.
a. Go to x:\startcd.htm (where x is your CD-ROM drive).
b. Select your adapter from the section CD-ROM - release date information.
c. Select Downloads and choose the appropriate software package for your
environment.
d. Execute the package to expand the files. The driver will be placed in the
directory listed in Table 2 on page 8.
4. Install the driver. Use Table 3 on page 9 to find the location of the installation
instructions for your environment. We recommend that you install the latest
service pack for your operating environment before installing the adapter
software.
© Copyright IBM Corp. 2000 7
Table 2. Driver file directory structure
Operating System Directory
®
Windows NT
4.0 \(root)
Windows NT 3.51 \win32
Windows
®
95 Retail \win32
Windows 95 OSR2 \(root)
Windows 98 \(root)
Windows 2000 \(root)
Windows for Workgroups \WFW
Novell NetWare Server and 32-bit Client \NOVELL\NETWARE
Novell NetWare DOS Requester (16-bit) \NOVELL\DOS
Novell NetWare OS/2 Requester (16-bit) \NOVELL\OS2
OS/2 \OS2
DOS \DOS
8 IBM 16/4 Token-Ring PCI Management Adapter
Table 3. Installation instructions
Environment Page
DOS with Windows Version 3.1x
NetWare Requester 22
DOS LAN Services 21
IBM TCP/IP for DOS (Version 2.1) 21
Windows for Workgroups with NDIS 33
DOS (without Windows)
NetWare Requester 22
DOS LAN Services 21
IBM TCP/IP for DOS (Version 2.1) 21
NetWare Requester 22
NDIS2 21
OS/2
OS/2 (MPTS) 19
NetWare Requester 20
OS/2 Warp Connect or Server 20
NetWare Server
NetWare Server Version 3.12 9
NetWare Server Version 4.11 12
NetWare Server Version 5.0 16
Novell Client 18
Windows 32-bit
Windows NT 3.51 23
Windows NT 4.0 24
Windows 95 25
Windows 98 28
Windows 2000 30
Remote Unattended Installation (Windows NT, Windows 95,
Windows 98, Windows 2000)
Novell IntranetWare Client for Windows NT 32
Novell Client for Windows 95 33
Managed Driver Upgrade (Windows NT, Windows 95,
Windows 98, Windows 2000)
32
34
Novell NetWare 3.12 Server
Before you start this installation, get the latest level of LAN driver updates for
NetWare 3.12 from Novell’s support Web site at http://support.novell.com.You
will install them during the following procedure.
If Novell NetWare Server is not installed on your machine, use the following
instructions. If it is installed, see the instructions in “Server driver installation in
existing NetWare 3.12 Server” on page 11.
Chapter 3. Software installation 9
Server driver installation in new NetWare 3.12 Server
Changes from the usual NetWare installation are necessary because this driver is
written to a new specification level that requires new NetWare loadable modules
(NLMs). The installation program is not aware of this, though, and these NLMs must
be loaded during installation of the server device driver and after the server
installation.
1. Create a diskette containing the extracted files from the NETWAREP.EXE
package file on the adapter CD-ROM.
2. Refer to Novell’s Installation and Upgrade manual for installation instructions.
Follow the procedure for the installation of Novell NetWare 3.12 until the
section titled “Load LAN Drivers” is next.
3. Insert the diskette that you created in step 1 into drive A. Enter the following
commands at the server prompt:
LOAD A:\NOVELL\NETWARE\NBI31X.NLM
LOAD A:\NOVELL\NETWARE\MSM31X.NLM
LOAD A:\NOVELL\NETWARE\TOKENTSM.NLM
Note: A message referring to protected-mode BIOS access might appear
before installation of Novell patches. It is for information only, and can
be ignored.
4. Load the server device driver. Enter the following command at the server
prompt:
LOAD X:\NOVELL\NETWARE\IBMTRPO.LAN DATARATE=M16
It is recommended for servers that the DataRate be set to M16 or M4, and
clients be set to Auto.
Note: See “Appendix D. Novell NetWare Server driver parameters” on page 65
for a complete list of parameters that can be specified in the LOAD
IBMTRPO command in the AUTOEXEC.NCF file.
5. Follow the instructions in the Novell manual, beginning with “Bind the Protocol
to the LAN Driver” and continue until you are in the file server STARTUP.NCF
file panel.
6. In addition to the instructions in the Novell manual, add the following line to
STARTUP.NCF:
Set Minimum Packet Receive Buffers = 48
Note: Increase the minimum packet receive buffers by 48 for each additional
adapter that is installed.
7. Perform the instructions in “Create an AUTOEXEC.NCF file” in the Novell
manual. Add the following lines to the AUTOEXEC.NCF file immediately after
the IPX INTERNAL NET statement (replace C:\SERVER.312\ with the location of
the NetWare Server program):
LOAD C:\SERVER.312\NBI31X.NLM
LOAD C:\SERVER.312\MSM31X.NLM
LOAD C:\SERVER.312\TOKENTSM.NLM
LOAD C:\SERVER.312\IBMTRPO.LAN NAME=IBMLS1 DATARATE=M16
BIND IPX TO IBMLS1 NET=<unique net number>
Make sure that the line containing IBMTRPO.LAN has the complete path
name.
10 IBM 16/4 Token-Ring PCI Management Adapter
Notes:
a. See “Appendix D. Novell NetWare Server driver parameters” on page 65 for
a complete list of parameters that you can specify on the LOAD IBMTRPO
command in the AUTOEXEC.NCF file.
b. If you experience any problems after loading the Novell NLM files, contact
Novell to ensure that you have the current version of these files.
Press Esc and answer Yes to save the new file to disk. Press Esc again to
return to the server console.
8. Shut down your server by entering down and then entering exit from the server
prompt.
9. Make sure that the diskette you created in step 1 is inserted in drive A. Enter
the following commands at the server prompt. You might be prompted to
perform a file overwrite; it is OK to overwrite these files.
COPY A:\NOVELL\NETWARE\NBI31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\MSM31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTRPO.LAN C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTRPO.LDI C:\SERVER.312
10. Go to the Novell server directory and enter server at the DOS prompt to
restart the server.
11. Install the patches obtained earlier now. Make sure to select the V3.31 ODI
LAN Updates for Hardware if given the opportunity.
12. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files are loading successfully. There are no error
messages.
v The adapter LEDs indicate normal operation: Green ON, Amber OFF. See
“Understanding the adapter LEDs and labels” on page 43.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
For information concerning NetWare Server error messages, see “Appendix E.
Novell NetWare Server messages” on page 71.
Server driver installation in existing NetWare 3.12 Server
If Novell NetWare is already installed in your computer, perform the following steps
to install the adapter server device driver.
1. Create a diskette containing the extracted files from the NETWAREP.EXE file
on the adapter CD-ROM.
2. Install the patches obtained earlier now. Make sure to select the V3.31 ODI
LAN Updates for Hardware if given the opportunity. Return to the server
console when the installation is complete.
3. Make sure that the diskette you created in step 1 is inserted in drive A. Enter
the following commands at the server prompt. You might be prompted to
perform a file overwrite; it is OK to overwrite these files.
COPY A:\NOVELL\NETWARE\NBI31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\MSM31X.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTRPO.LAN C:\SERVER.312
COPY A:\NOVELL\NETWARE\IBMTRPO.LDI C:\SERVER.312
Chapter 3. Software installation 11
Note: If you experience any problems after loading the Novell NLM files,
check the Novell Web site to ensure that you have the current version
of these files.
4. In the directory where Novell is installed on your hard disk, enter server at the
DOS prompt to start the server.
5. At the server console prompt, enter load install.
6. From the Installation Options menu, select System Options and press Enter.
7. Select Edit STARTUP.NCF File and press Enter.
8. Add the following line to the STARTUP.NCF file:
Set Minimum Packet Receive Buffers = 48
Note: Increase the minimum packet receive buffers by 48 for each additional
adapter that is installed.
9. Press Esc and then answer Yes to save changes to the STARTUP.NCF file.
10. Select Edit AUTOEXEC.NCF File and press Enter. Edit this file and, after the
IPX internal net statement, include the following statements. (Replace
C:\SERVER.312\ with the location of the NetWare Server program.)
It is recommended for servers that the DataRate be set to M16 or M4, and
clients be set to Auto.
LOAD C:\SERVER.312\NBI31X
LOAD C:\SERVER.312\MSM31X
LOAD C:\SERVER.312\TOKENTSM
LOAD C:\SERVER.312\IBMTRPO NAME=IBMLS1 DATARATE=M16
BIND IPX TO IBMLS1 NET=<unique net number>
See “Appendix D. Novell NetWare Server driver parameters” on page 65 for a
complete list of parameters that can be specified on the LOAD IBMTRPO
command in the AUTOEXEC.NCF file.
Press Esc and then answer Yes to save the new file to disk. Press Esc again
to return to the server console.
11. Shut down your server by entering down and then entering exit from the
server prompt.
12. Enter server to restart the server.
13. Shut down and restart the computer to apply the changes.
14. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files are loading successfully. There are no error
messages.
v The adapter LEDs indicate normal operation: Green ON, Amber OFF. See
“Understanding the adapter LEDs and labels” on page 43.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
For information concerning NetWare Server error messages, see “Appendix E.
Novell NetWare Server messages” on page 71.
Novell NetWare 4.11 Server
Before you start this installation, get the latest level of patches from Novell’s support
Web site at http://support.novell.com and install them.
12 IBM 16/4 Token-Ring PCI Management Adapter
If Novell NetWare is not installed on your machine, use the following instructions. If
it is installed, follow the instructions in “Server driver installation in existing NetWare
4.11 Server” on page 14.
Server driver installation in new NetWare 4.11 Server
Changes from the usual NetWare installation are necessary because this driver is
written to a new specification level that requires new NetWare loadable modules
(NLMs). The installation program is not aware of this, though, and these NLMs must
be loaded during installation of the server device driver and after the server
installation.
Note: A message referring to protected-mode BIOS access might appear before
installation of Novell patches. It is for information only, and can be ignored.
1. Create a diskette containing the extracted files from the NETWAREP.EXE
package file on the adapter CD-ROM.
2. When you see INSTALL Found the following : PCI LAN Controller
xxxx.xxxx.xxxx press Enter. Then press the Insert key to install the unlisted
driver.
3. Press Alt+Esc to toggle to the server console, and enter the following LOAD
statements (make sure that the diskette that you created in step 1 is inserted
in drive A):
LOAD A:\NOVELL\NETWARE\MSM.NLM
LOAD A:\NOVELL\NETWARE\TOKENTSM.NLM
4. Press Alt+Esc to toggle back to the INSTALL panel.
5. Press F3 on the next panel to specify a:\novell\netware as the directory path.
6. Press Enter and then follow the instructions on the panel to complete the
installation of the driver. If you need to make any custom configuration
changes to the driver, do so at this time.
7. Follow the instructions in the Novell manual Create an AUTOEXEC.NCF file.In
addition to the instructions in the manual, add the following lines to the
AUTOEXEC.NCF file immediately after the IPX INTERNAL NET statement (if
necessary, replace c:\nwserver with the location of the SERVER.EXE
executable):
LOAD C:\NWSERVER\NBI.NLM
LOAD C:\NWSERVER\MSM.NLM
LOAD C:\NWSERVER\TOKENTSM.NLM
LOAD C:\NWSERVER\IBMTRPO.LAN NAME=IBMLS1 DATARATE=M16
Note: There will be existing LOAD and BIND IPX statements in the
AUTOEXEC.NCF. Delete the LOAD statement (we have replaced it with
stated LOAD C:\NWSERVER\IBMTRPO.LAN statement). Also, make
any needed modifications to the existing BIND IPX statement Refer to
the ″Bind the Protocol to the LAN Driver″ section of the Novell manual
for additional information.
See “Appendix D. Novell NetWare Server driver parameters” on page 65 for a
complete list of parameters that can be specified on the LOAD IBMTRPO
command in the AUTOEXEC.NCF file.
8. Press Esc and answer YES to save the new file to disk. Press Esc again to
return to the server console.
9. Type the following commands from the server prompt to shut down the server
and exit to DOS: down, then exit.
Chapter 3. Software installation 13
10. Perform the following COPY commands, making sure that the diskette that you
created in step 1 is inserted in drive A. Note that it will prompt you at each of
the following files to ask if you want to perform a file overwrite; it is OK to
overwrite these files.
COPY A:\NOVELL\NETWARE\NBI.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\MSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTRPO.LAN C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTRPO.LDI C:\NWSERVER
11. Go to the Novell server directory and enter server at the DOS prompt to
restart the server.
12. Install the latest available Novell patches for NetWare 4.11 now. Make sure to
select the Version 3.31 ODI LAN Updates for Hardware if given the
opportunity.
13. Issue the down command to bring the server down.
14. Reboot the server by entering restart server.
15. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files are loading successfully. There are no error
messages.
v The adapter LEDs indicate normal operation. Green ON, Amber OFF. See
“Understanding the adapter LEDs and labels” on page 43.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
For information concerning NetWare Server error messages, see “Appendix E.
Novell NetWare Server messages” on page 71.
Server driver installation in existing NetWare 4.11 Server
If Novell NetWare is already installed in your computer, perform the following steps
to install the adapter server device driver.
Note: If you are altering the configuration of a previously loaded adapter, unload
that adapter before proceeding with these instructions.
1. Create a diskette containing the extracted files from the NETWAREP.EXE file
on the adapter CD-ROM.
2. Be sure that your adapter has already been installed in your computer. If it has
not, follow the instructions in “Chapter 2. Installing the adapter hardware” on
page 5.
3. Install the latest available Novell patches for NetWare 4.11. Make sure to
select the Version 3.31 ODI LAN Updates for Hardware if given the
opportunity. Return to the server console when the installation is complete.
4. Issue the down command from the server prompt to bring the server down.
5. Reboot the server by entering restart server.
6. Check to see if the device driver is loaded. If it is, unload it using the following
command: unload ibmtrpo
7. Type load install on the server.
8. Select Driver Options.
9. Select Configure Network Drivers.
10. Select Select Drivers.
11. Press the Insert key to install the unlisted driver.
14 IBM 16/4 Token-Ring PCI Management Adapter
12. Insert the diskette that you created in step 1.
13. Press F3 and specify the path a:\novell\netware.
14. Follow the instructions on the panels to complete the installation of the driver.
If you need to make any custom configuration changes to the driver, do so at
this time.
15. Follow the instructions in the Novell manual Create an AUTOEXEC.NCF file.In
addition to the instructions in the manual, add the following lines to the
AUTOEXEC.NCF file, immediately after the IPX INTERNAL NET statement (if
necessary, replace c:\nwserver with the actual location of the SERVER.EXE
executable):
LOAD C:\NWSERVER\NBI.NLM
LOAD C:\NWSERVER\MSM.NLM
LOAD C:\NWSERVER\TOKENTSM.NLM
LOAD C:\NWSERVER\IBMTRPO.LAN NAME=IBMLS1 DATARATE=M16
Note: There will be existing LOAD and BIND IPX statements in the
AUTOEXEC.NCF. Delete the LOAD statement (we have replaced it with
the stated LOAD C:\NWSERVER\IBMTRPO.LAN statement).
Also, make any needed modifications to the existing BIND IPX statement.
Refer to the ″Bind the Protocol to the LAN Driver″ section of the Novell manual
for additional information.
See “Appendix D. Novell NetWare Server driver parameters” on page 65 for a
complete list of parameters that can be specified on the LOAD IBMTRPO
command in the AUTOEXEC.NCF file.
16. Press Esc and answer YES to save the new file to disk. Press Esc again to
return to the server console.
17. Type the following commands from the server prompt to shut down the server
and exit to DOS: down, and then exit.
18. Type the following commands, making sure that the diskette that you created
in step 1 is inserted in drive A. Note that it will prompt you at each of the
following files to ask if you want to perform a file overwrite; it is OK to
overwrite these files.
COPY A:\NOVELL\NETWARE\NBI.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\MSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\TOKENTSM.NLM C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTRPO.LAN C:\NWSERVER
COPY A:\NOVELL\NETWARE\IBMTRPO.LDI C:\NWSERVER
19. Go to the Novell server directory and enter server at the DOS prompt to
restart the server.
20. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files are loading successfully. There are no error
messages.
v The adapter LEDs indicate normal operation. Green ON, Amber OFF. See
“Understanding the adapter LEDs and labels” on page 43.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
For information concerning NetWare Server error messages, see “Appendix E.
Novell NetWare Server messages” on page 71.
Chapter 3. Software installation 15
Novell NetWare 5.0 Server
If Novell NetWare is not installed on your machine, use the following instructions. If
it is installed, follow the instructions in “Server driver installation in existing NetWare
5.0 Server” on page 17.
Server driver installation during NetWare 5.0 Server installation
Installation of the network board and its device driver occurs during the combined
storage device and network board installation step. Use the following instructions to
install the network board and its driver during a new NetWare 5.0 Server
installation.
1. Create a device driver installation diskette containing the extracted files from the
NETWAREP.EXE package file on the adapter CD-ROM.
2. Select a storage device and a network board:
v Select and configure the storage device.
Storage devices such as hard disks, CD-ROMs, and tape devices require a
software driver to communicate with the storage adapter. The software driver
for the storage device is called a custom device module (CDM). Each type of
storage device requires a CDM.
The installation program auto-detects many types of storage devices such as
IDE drives, SCSI drives, CD-ROM drives, and tape drives. If your storage
device is not detected, choose the appropriate driver from the list of available
drivers provided with NetWare 5 or add a new driver from a diskette. CDMs
can be obtained from the storage device manufacturer.
v Select and configure the network board.
The software driver for a network board is called a LAN driver. The
installation program auto-detects many types of network boards. If your
network board is not detected, choose the driver for the network board from
the list provided with NetWare 5 or use a new or updated driver from the
diskette that you created in step 1.
The network board must be installed and configured correctly. For servers, it
is recommended that DATARATE be set to M16 or M4, and clients be set to
Auto. You might be able to influence certain network board properties by
configuring the system and the network board or both.
v Load a NetWare Loadable Module TM program, if required.
Certain server and network configurations might require you to load a
NetWare Loadable Module (NLM) before you can complete the server
installation. An example is loading ROUTE.NLM for a token-ring environment
that requires it.
16 IBM 16/4 Token-Ring PCI Management Adapter
3. Add, delete, or modify drivers as needed.
v To add a driver:
a. In the Options box, select Modify.
b. Select the driver and press Enter.
c. Press Insert to select from a list of drivers provided with NetWare.
d. Press Insert again to install a driver from diskette.
v To delete a driver:
a. In the Options box, select Modify.
b. Select the driver and press Enter.
c. Select the driver to delete and press Delete.
v To modify a driver:
a. In the Options box, select Modify.
b. Select the driver and press Enter.
c. Select the driver to modify and press Enter.
d. Select the property to modify.
Server driver installation in existing NetWare 5.0 Server
The following procedure explains how to use NWCONFIG to load a LAN driver and
bind a protocol.
1. Create a diskette containing the extracted files from the NETWAREP.EXE
package file on the adapter CD-ROM.
2. At the server console prompt, enter NWCONFIG.
3. Select Driver Options → Configure network drivers.
4. To select the driver from all of the available drivers, select Select a driver. The
screen will display a list of all available drivers.
5. Press Insert. Follow the instructions on the panels. Use the diskette that you
created in step 1 when you are prompted to supply an unlisted driver. The
directory is a:\novell\netware.
Chapter 3. Software installation 17
Note: For some drivers, a message might appear indicating that the driver
must be loaded manually (at the console prompt). To load a driver
manually, follow the screen prompts or press F1 for more information.
6. Set protocols. When the window containing protocol choices is displayed,
select the protocol that you want to use and press the space bar. If you select
TCP/IP, enter the IP address and the IP mask.
7. Set parameters. Use the down arrow key to move the cursor to the parameter
window. Enter parameter values as needed. Press F1 for help.
It is recommended for servers that the Data Rate be set to 4 Mbps or 16
Mbps, and clients be set to Automatic.
In some cases, the system displays a pop-up list of values for the field from
which you select the desired value. In other cases, you must type in a value
and press Enter to move to the next field.
8. To specify a particular frame type for a token-ring driver, press F3 to display a
list of frame types. Use the arrow keys to move up and down the list.
9. Press Enter to select a frame type.
10. When finished, press F10.
If you do not specify a particular frame type, all frame types are loaded
automatically, but only those found on the network are actually bound to the
driver.
11. Select Save parameters and load driver.
12. Confirm bindings of the protocol with the driver and the network number.
13. To add another adapter, shut down the server, power off the server, and insert
the additional driver. NetWare will load the appropriate driver automatically.
Then repeat step 12.
Novell Client DOS/Windows 3.1x
1. Download Novell Client DOS/Windows 3.1x Version 2.5 or later from Novell’s
Web site at http://support.novell.com.
2. Unzip the downloaded file to a directory on your computer.
3. Exit Windows.
4. From a DOS prompt, go to the directory where you put the file. Run
INSTALL.EXE.
5. Select Yes or No to respond to the Novell License Agreement.
6. Select Novell Client Windows Support and Work Station Manager 3.X.
Press F10 to save and continue.
7. Select 32-bit LAN Drivers and press F10 to save and continue.
8. Select USER SPECIFIED 32-Bit Driver and press Enter.
9. Insert the CD-ROM or the diskette containing the device drivers into the
appropriate drive. Enter the path to the 32-bit ODI driver: x:\novell\netware
where x is your CD-ROM drive letter. The panel should say
IBM Token-Ring PCI Family Adapter
Press Enter, configure the parameters, and press F10 to save and continue.
10. At the panel entitled Installation Configuration Summary, confirm that the
values are what you selected, and press F10 to save and continue.
The files will be copied at this point.
11. Reboot the computer and start Windows to connect to and log in to your
server.
18 IBM 16/4 Token-Ring PCI Management Adapter
12. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files are loading successfully. There are no error
messages.
v The adapter LEDs indicate normal operation: Green ON, Amber OFF. See
“Understanding the adapter LEDs and labels” on page 43.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
OS/2 NDIS 2 device driver using MPTS
Use the following procedure to install the OS/2 NDIS 2 device driver using the
Multiple Protocol Transport Services (MPTS).
1. When updating an existing device driver, error message X100035, which
indicates that the driver could not be installed and the previous version could
not be restored, can be prevented by performing the following steps before
beginning the update. This is particularly useful when the existing driver was
installed from the adapter CD-ROM.
v From an OS/2 window, go to the drive where OS/2 is installed. Change to
the ibmcom subdirectory (where x is your drive letter):
x:
cd \ibmcom
v Enter the following two commands:
attrib -r ibmtrp.* /s
attrib -r la1*.msg
2. Start MPTS by performing either of the following actions:
v From the OS/2 desktop, double-click the MPTS icon.
v From an OS/2 window, go into the ibmcom subdirectory and enter mpts at
the OS/2 prompt.
3. Select OK on the MPTS logo panel.
4. Select Install. You will be prompted for the source of the .NIF file. Enter the
path to the driver directory. Select OK once the Installation Complete message
appears. You will return to the main menu.
5. Select Configure in the MPTS dialog box.
6. On the Configure panel, make sure that LAN adapters and protocols is
preselected and then select Configure at the bottom of the panel.
7. In the Configuration panel, in the Network Adapters group box, select IBM
Token-Ring PCI Family Adapter (IBMTRP.OS2) and select ADD.
Note: You can edit parameter settings for this adapter. Highlight your adapter
in the Current Configuration list box and select Edit.
8. In the Protocols list box, select the protocols used by your network application.
Highlight each protocol and select ADD.
Note: If you are not sure which ones to use, select IBM IEEE 802.2 and IBM
OS/2 NetBIOS protocol drivers or ask your network administrator.
The protocol drivers you have selected will appear under the adapter driver
name in the Current Configuration list box.
Note: You can edit parameter settings for the protocols. Highlight a protocol
and select Edit.
Chapter 3. Software installation 19
9. Select OK when you have finished selecting and editing protocols in the MPTS
Configuration panel.
10. Select Close on the Configure panel.
11. Select Exit in the MPTS dialog box.
12. Select Exit on the Update CONFIG.SYS panel to update the CONFIG.SYS
file.
13. Select OK when you get the message that the CONFIG.SYS has been
successfully updated.
14. Select Exit on the Exiting MPTS panel.
15. Shut down and restart the computer to apply the changes.
16. At system startup, check for the following conditions to determine whether the
adapter is working correctly and whether installation has been completed
successfully:
v The device driver files loaded successfully. There are no error messages.
v The adapter LEDs indicate normal operation: Green ON, Amber OFF.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
For information concerning NDIS driver error messages, see “Appendix C. NDIS 2
device driver messages” on page 59.
OS/2 NDIS 2 device driver using other installation programs
Use the following procedure to install the OS/2 NDIS 2 device driver using
installation programs other than MPTS.
1. Insert the CD-ROM or the NDIS Drivers diskette into the appropriate drive.
2. Use your product documentation to install the driver (IBMTRP.OS2) that is
located in the root directory on both the CD-ROM and diskette.
3. Modify the parameters if needed. See “Appendix B. NDIS 2 device driver
parameters” on page 53 for a list and explanation of parameters.
IBM TCP/IP for OS/2 and Warp Connect are examples of products that provide
driver installation programs.
4. Shut down and restart the computer to apply the changes.
5. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files load successfully. There are no error messages.
v The adapter LEDs indicate normal operation: Green ON, Amber OFF.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
For information concerning NDIS driver error messages, see “Appendix C. NDIS 2
device driver messages” on page 59.
OS/2 Novell NetWare Requester
Before installation, copy IBMTRPO.SYS from the CD-ROM to the root directory
containing your Novell NetWare Requester source files.
Refer to the workstation basics and installation manuals from Novell. When a dialog
box titled Requester Installation appears during the installation process, perform the
following procedure:
20 IBM 16/4 Token-Ring PCI Management Adapter
1. If you are installing the NetWare Requester on a workstation, select Edit
CONFIG.SYS and Copy All Files.... If the NetWare Requester is already
installed on the workstation and only a driver update is needed, then select
Only Edit CONFIG.SYS....
2. On the next panel, specify the name of the adapter driver: IBMTRPO.SYS.
3. When you get to the panel labeled Copy ODI LAN Driver files, select Copy
only the default driver.
4. Follow the instructions on the panels to continue installation.
5. When Installation Complete appears in the Requester window, go to the
Configuration menu and select This workstation....
6. Select Edit to accept the default location for the NET.CFG file.
7. In the edit box titled Current NET.CFG File Contents, type the following lines:
link driver IBMTRPO
SLOT 10001
link support
BUFFERS 8 4096
Notes:
a. See “Appendix F. Novell NetWare DOS ODI driver parameters” on page 77
for a complete list of parameters that you can specify in the NET.CFG file.
b. To enable source routing, changes will have to be made to the
CONFIG.SYS file. Refer to Novell’s Workstation for OS/2 manual for
instructions on how to enable source routing.
c. The lines in the NetWare Requester section of the CONFIG.SYS file must
be in a certain order. Do not reorder the lines in this section of
CONFIG.SYS. Refer to the Novell manuals for more information.
8. Select Save to complete the NetWare Requester installation.
9. Reboot the computer to apply the changes.
DOS NDIS 2
Note: To make changes in the NetWare Requester configuration, double-click
the Novell icon on the desktop. Double-click the Install icon in the Novell
window. Go to the Configuration and select This workstation.... Make
sure that the correct NET.CFG is shown in the next dialog box and select
Edit. Edit the NET.CFG file in the edit box titled Current NET.CFG File
Contents. When the changes are complete, select Save and reboot the
computer to apply the changes.
10. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files loaded successfully. There are no error messages.
v The adapter LEDs indicate normal operation: Green ON, Amber OFF.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
Use the following procedure to install the DOS NDIS 2 device driver:
1. Insert the CD-ROM or the NDIS Drivers diskette into the appropriate drive.
2. Use your operating system documentation to install the driver (IBMTRP.DOS).
This driver is located in the \dos subdirectory on both diskette and the CD-ROM.
3. Modify the parameters, if needed. See “Appendix B. NDIS 2 device driver
parameters” on page 53.
Chapter 3. Software installation 21
Note: If you use Microsoft Windows for Workgroups and want to configure the
NetAddress parameter for the NDIS device driver, remember to enclose
the address in double quotes (" "). The NetAddress parameter is used to
set a locally administered address for the adapter.
4. Shut down and restart the computer to apply the changes.
5. Check for the following conditions to determine whether the adapter is working
correctly and whether installation has been completed successfully:
v The device driver files load successfully. There are no error messages. If
error messages are displayed or if you do not see messages that indicate
that the drivers have been installed, see “Starting the troubleshooting
process” on page 37.
v The adapter LEDs indicate normal operation: Green ON, Amber OFF.
If you experience problems, see “Chapter 4. Problem solving” on page 37.
For information concerning NDIS driver error messages, see “Appendix C. NDIS 2
device driver messages” on page 59.
DOS Novell NetWare Requester (16-bit)
The 16-bit DOS Novell NetWare Requester environment supports access to servers
running Novell NetWare 3.11 or later.
To install the IBMTRPO.EXE ODI driver on a computer running DOS, perform the
following procedure:
Note: Consult your Novell NetWare documentation for instructions regarding how to
create the NetWare Client for DOS and MS Windows diskettes.
1. Create a diskette containing the extracted files from the DOSODIP.EXE file on
the adapter CD-ROM.
2. Insert the NetWare Client for DOS and MS Windows Disk 1 into the
appropriate drive.
3. At the command prompt, type x:, where x is your drive letter, and then press
Enter.
4. Type install and then press Enter.
5. Follow the instructions as they appear. In step 5 of those instructions, select
the driver for your network board by scrolling down through Network Boards,
highlighting Other Drivers, and pressing Enter.
6. Insert the CD-ROM or the diskette that you created in step 1 of this procedure
into the appropriate drive. When prompted, specify the location to the chosen
media and press Enter. Specify the path as A:\NOVELL\DOS (or at
X:NOVELL\DOS for the CD-ROM version).
7. Highlight your adapter and press Enter.
8. At this time you can change the default parameters. When you complete the
changes, press F10. “Appendix F. Novell NetWare DOS ODI driver parameters”
on page 77 contains the parameters that can be configured in the NET.CFG
file.
9. Follow the instructions presented to complete the installation.
Note: If source routing is required, edit the STARTNET.BAT file that is in the
client directory (usually C:\NWCLIENT) and add the following line after
the IPXODI statement:
22 IBM 16/4 Token-Ring PCI Management Adapter
Loading...