3Com 3C996B-T User manual

Gigabit Server Network Interface Cards
3C996B-T and 3C996-SX
User Guide
http://www.3com.com/
http://support.3com.com/registration/frontpg.pl
Published November 2001
User guide version 1.0.2

3Com Corporation ■5400 Bayfront Plaza ■Santa Clara, California ■95052-8145 ■U.S.A.
Copyright © 2001 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to
make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.
3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part
of 3Com Corporation to provide notification of such revision or change.
3Com Corporation provides this documentation without warranty, term, or condition of any kind, either implied or expressed, including, but not
limited to, the implied warranties, terms or conditions of merchantability, satisfactory quality, and fitness for a particular purpose. 3Com may make
improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.
If there is any software on removable media described in this documentation, it is furnished under a license agreement included with the product as
a separate document, in the hard copy documentation, or on the removable media in a directory file named LICENSE.TXT or !LICENSE.TXT. If you are
unable to locate a copy, please contact 3Com and a copy will be provided to you.
UNITED STATES GOVERNMENT LEGEND
If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the
following:
All technical data and computer software are commercial in nature and developed solely at private expense. Software is delivered as “Commercial
Computer Software” as defined in DFARS 252.227-7014 (June 1995) or as a “commercial item” as defined in FAR 2.101(a) and as such is provided
with only such rights as are provided in 3Com’s standard commercial license for the software. Technical data is provided with limited rights only as
provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion
of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this user guide.
Portions of this documentation are reproduced in whole or in part with permission from (as appropriate).
Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries.
3Com, DynamicAccess, EtherCD, EtherLink and EtherLink II are registered trademarks and the 3Com logo is a trademark of 3Com Corporation.
Intel and Pentium are registered trademarks of Intel Corporation. Microsoft, Windows, and Windows NT are registered trademarks
of Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc. UNIX is a registered trademark in the United States and other
countries, licensed exclusively through X/Open Company, Ltd.
All other company and product names may be trademarks of the respective companies with which they are associated.

Contents
1Introduction
Contents 1
Advanced Server Features Overview 1
Load Balance 2
Advanced Server Features for Windows 2000 2
Advanced Server Features for Windows NT 3
Advanced Server Features for Novell NetWare 3
Advanced Server Features for Linux 4
3Com Management Programs 4
Creating a Driver Disk 5
2Installing and Connecting the NIC
System Requirements 7
Windows XP (64-bit) 7
Windows XP (32-bit) 7
Windows 2000 7
Windows NT 7
NetWare 8
Linux 8
UNIX 8
Solaris 8
Safety Precautions 9
Pre-Installation Checklist 9
Installing and Connecting the NIC 10
Installing the NIC 10
Connecting the Network Cables 12
Installing and Using the 3Com Connection Assistant 13
System Requirements 13
Installation 13
3Windows XP Driver Setup
Installing the Driver Software 15
Windows XP 32-bit 15
Windows XP 64-bit 16
Driver Installation Without Master Navigator 16
Verifying Successful Installation 17
Modifying Configuration Parameters 17
Removing the Driver Software 19
Installing Advanced Server Features 19
Uninstalling Advanced Server Features 20
Configuring Advanced Server Features 20
Configuring Teaming 20
Configuring VLANs 22
Advanced Server Control Suite 23

Contents
4Windows 2000 Driver Setup
Installing the Driver Software 25
Verifying Successful Installation 27
Modifying Configuration Parameters 27
Removing the Driver Software 29
Installing Advanced Server Features 30
Uninstalling Advanced Server Features 30
Configuring Advanced Server Features 30
Configuring Teaming 30
Configuring VLANs 32
Advanced Server Control Suite 34
Updating Mini-port (Core) Drivers 34
5Windows NT Driver Setup
Installing the Driver Software 37
Modifying Configuration Parameters 38
Updating the Driver Software 40
Removing the Driver Software 40
Installing Advanced Server Features 41
Uninstalling Advanced Server Features 41
Configuring Teaming 42
Configuring VLANs 44
Advanced Server Control Suite 45
Installing the Microsoft Loopback Adapter Driver 46
Performing a Fresh Installation of Windows NT on a
Backup Domain Controller 46
Setting up SERVER 2 47
Stopping the Net Logon Service on SERVER 1 48
Stopping the Net Logon Service on SERVER 2 48
Renaming Domain-2/SERVER-2 to DOMAIN-1/SERVER-2 48
Updating Mini-port (Core) Drivers 49
6Novell NetWare Driver Setup
Pre-Installation Requirements 51
Installing Novell NetWare Server 4.2 51
Installing Novell NetWare Server 5.1 54
Verifying or Modifying NIC Parameters 54
Removing Drivers from Autoexec.ncf 55
Installing Advanced Server Features 56
Uninstalling Advanced Server Features 56
Load Balance and Trunk Mode Selection 57
Loading Frame Types 57
Hot Standby 57
Configuring VLANs 57
Additional Command Line Keywords 59
Editing the AUTOEXEC.NCF File 59
Installing Advanced Server Features on Novell NetWare Server 4.2 and 5.1 63
NIC Driver Configuration Parameters for Novell NetWare 64

Contents
7Linux Driver Setup
Installation Overview 65
Installing the Source RPM Package 65
Building the Driver From a TAR File 65
Patching PCI Files (Optional) 66
Unloading and Removing the Driver 66
Optional Parameters 66
Advanced Server Features 67
Installing Advanced Server Features 68
Configuring Teams 69
8UNIX and
SCO OpenServer Driver Setup
UnixWare 7 Driver 75
Package Creation 75
Driver Installation 75
MAC Address 76
Jumbo MTU Size 76
SCO OpenServer Release 5 Driver 76
Installation Diskette 76
Driver Installation 77
Jumbo Frames and Other Advanced Parameters 77
9Solaris Driver Setup
Driver Installation 79
Uninstalling the Driver 79
Customizing the Driver Configuration 80
ForceSpeedDuplex 80
FlowControl 80
MaxJumboFrameSize 81
TxPacketDescCnt 81
RxStdDescCnt 81
RxJumboDescCnt 81
RxCoalescingTicks 81
RxMaxCoalescedFrames 81
TxCoalescingTicks 81
TxMaxCoalescedFrames 82
RxCoalescingTicksDuringInt 82
TxCoalescingTicksDuringInt 82
RxMaxCoalescedFramesDuringInt 82
TxMaxCoalescedFramesDuringInt 82
StatsCoalescingTicks 82
DoubleCopyTxBufferSize 82
ndd Command 83

Contents
10 3Com Management Programs
Overview 85
Installing the Management Programs 85
Removing the Management Programs 86
Initializing the Management Programs 86
Vital Sign 86
Diagnostics 87
Cable Analysis 88
Load Balance/Virtual LANs 89
Saving the Configuration 91
Restoring the Configuration 91
Load Balance/Virtual LAN Statistics 91
11 Troubleshooting
Hardware Diagnostics 93
Checking Port LEDs 93
Troubleshooting Checklist 94
Checking if Proper Drivers are Loaded 94
Windows 94
NetWare 95
Linux 95
Running Cable Analysis 95
Length 96
Cable Diagnostics Display 96
Testing Network Connectivity 96
Windows 96
NetWare 96
Linux 97
DOS Diagnostic Failures 97
Wake-on-Lan 97
Known Problems 97
Windows 2000 97
Linux 98
AKey Protocols and Interfaces
CIM 99
DMI 100
SNMP 100
NIC Teaming 101
Load Balancing 101
Link Aggregation (802.3ad) 101
Generic Link Aggregation (Trunking) 101
Failover Teaming 102
VLANs Overview 102
VLAN Support 102

Contents
BInstalling and Using the Managed PC Boot Agent
Booting From the Network 105
Using the Boot ROM on the NIC to Boot from the Network 105
Enabling or Disabling the Boot ROM Setting 106
CSpecifications
10/100/1000 BASE-T Cable Specifications 107
Performance Specifications 107
Physical Characteristics 107
Power Requirements 107
Environmental Specifications 108
DTechnical Support
Online Technical Services 109
World Wide Web Site 109
3Com KnowledgeBase Services 109
3Com FTP Site 109
Support from Your Network Supplier 110
Support from 3Com 110
Returning Products for Repair 111
Regulatory Information
FCC Class A Verification Statement 113
FCC Class B Statement 113
FCC Declaration of Conformity 114
Index

1
1Introduction
This guide describes how to install and configure the 3Com®Gigabit Server NICs in
Windows XP, Windows 2000, Windows NT, Novell NetWare, Linux, UNIX, and, Solaris
operating system environments.
Contents
■3Com Gigabit Server NIC
Keep the NIC in its package until ready for installation.
■3Com Installation CD with Gigabit Server driver software and online user guide.
■Quick start guide.
Inform your network supplier of any missing or damaged items. If you need to return the
NIC, you must use the original (or equivalent) packaging.
Advanced Server Features Overview
The Advanced Server Features program is an intermediate software driver for Windows
2000 Server operating systems (Server, Advanced Server, and Datacenter Server),
Windows NT Server operating systems (Server and Enterprise Server), NetWare, and Linux.
The Advanced Server Features provide load balancing, failover, and VLAN configuration.
These features are provided by creating teams (virtual NICs) that consist of multiple NICs.
A team can consist of one to eight NICs, and each NIC can be designated primary or
standby. All primary NICs in a team will participate in load balancing operations by
sending and receiving a portion of the total traffic. Standby NICs will take over in the
event that all primary NICs have lost their links. VLANs can be added to a team to allow
multiple VLANs with different VLAN IDs. A virtual NIC is created for each VLAN added.
Load balancing and failover features will work with any third-party NIC. VLANs work with
3Com, Broadcom, Alteon, and Intel NICs.
NOTE: Standby can be used only in load balance mode (see “Load Balance”
below).

1Introduction
2
Load Balance
Load balance is a protocol-specific scheme. The levels of support for IP, IPX, and other
protocols are listed below.
Load balance mode works with all Ethernet switches without configuring the switch ports
to any special trunking mode. Only IP traffic will be load-balanced in both inbound and
outbound directions. IPX traffic will be load-balanced in the outbound direction only.
Other protocol packets will be sent and received through one primary NIC only. Failover
for non-IP traffic is supported using 3Com,Broadcom,Alteon, and Intel NICs. The generic
trunking mode requires the Ethernet switch to support some form of port trunking mode
(for example, Cisco Systems Gigabit EtherChannel or other switch vendors’ link
aggregation mode). This mode is protocol-independent and all traffic should be load-
balanced and fault-tolerant.
Advanced Server Features for Windows 2000
The following options are supported under Windows 2000 Server operating systems
(Server, Advanced Server, Datacenter Server). See “Windows 2000 Driver Setup” on
page 25 for additional information.
Failover and Load Balance
■Adapter teaming for failover (heterogeneous support for 3Com 10/100 server NICs,
Alteon AceNIC, released Intel 10/100 server NICs, released Intel 1000BaseSX server
NICs, and Intel 82559 LAN on Motherboard [LOM])
■Load balance
■Generic Link Aggregation (GEC/FEC, open trunk)
■Link aggregation (IEEE 802.3ad) static implementation only
Virtual LAN (VLANs)
■Up to 64 VLANs per team using IEEE 802.1Q-1988 tagging
Offloading
■IP, TCP/UDP checksum
■Support for segmentation of large TCP packets
■Jumbo frames (9K)
Power Management
■Remote Wake Up (magic packet, specific pattern)
PCI Hot-Plug
■Microsoft
Protocol Load Balancing Failover
IP Yes Yes
IPX Yes* Yes**
Other protocols No Yes**
*Only outbound load-balancing for IPX (on NetWare only).
**For 3Com NICs.
NOTE: Wake-on-LAN (WOL) is not supported with the fiber version of the
Gigabit Server NIC (3C996-SX). WOL must be disabled when using the fiber
Gigabit Server NIC.

Advanced Server Features Overview
3
Advanced Server Features for Windows NT
The following options are supported under Windows NT Server operating systems
(Server and Enterprise Server). See “Windows NT Driver Setup” on page 37 for additional
information.
Failover and Load Balance
■Adapter teaming for failover (heterogeneous support for 3Com 10/100 server NICs,
released Alteon AceNIC, Intel 82559 LAN on Motherboard (LOM), released
Intel 10/100 server NICs, and released Intel 1000BaseSX server NICs).
■Load balance
■Generic Link Aggregation (GEC/FEC, open trunk)
■Link aggregation (IEEE 802.3ad) static implementation only
Virtual LAN (VLANs)
■Up to 64 VLANs per team using IEEE 802.1Q-1988 tagging.
Offloading
■Jumbo frames (9K)
PCI Hot-Plug
■Contact your OEM for more information.
Advanced Server Features for Novell NetWare
The following options are supported under Novell NetWare. See “Novell NetWare Driver
Setup” on page 51 for additional information.
Failover and Load Balance
■Adapter teaming for failover (heterogeneous support for 3Com 10/100 server NICs,
Alteon Tigon2/3, Intel 82559 LAN on Motherboard (LOM), Intel 10/100 server NICs,
and Intel 1000BaseSX server NICs).
■Load Balance
■Generic Link Aggregation (GEC/FEC, open trunk)
NESL Compliance
For optimal fault tolerance and recovery operations, BASP.LAN relies on the NIC drivers to
generate NESL (NetWare Event Service Layer) events during link changes and other failure
events. NESL is an optional feature in the ODI driver specification and not all drivers
support it. For NESL events to propagate properly to BASP.LAN, ODINEB.NLM must be
loaded before the NESL compliant ODI drivers.
Do the following to determine if a NIC driver supports NESL events:
■Load BASP.LAN and create a team by binding the NIC to the virtual slot (see
instructions and examples below). In the Virtual Adapter X Team Members screen
of the BASP.LAN menu interface, the Link status of all bound NICs are shown.
Disconnect or connect the NIC cable. The link status shown on the screen should
change immediately if the NIC driver supports NESL events.

1Introduction
4
Virtual LAN (VLANs)
■Up to 64 VLANs per NIC using IEEE 802.1Q-1988 tagging (64 is the maximum
configurable, although 32 is the maximum operable).
Offloading
■IP, TCP/UDP checksum—NetWare 5.0 or greater only
PCI Hot-Plug
■Contact your OEM for more information.
Advanced Server Features for Linux
The Gigabit Ethernet NIC supports the Linux driver. See “Linux Driver Setup” on page 65
for additional information.
■Packaging—The driver has been released in two packaging formats, source RPM and
compressed TAR formats.
■Module Parameters—Optional parameters for the driver can be supplied as
command-line arguments to the insmod command.
■Advanced Server Features—A kernel module designed for Linux 2.2 kernel that
provides load balancing, failover, and VLAN features.
3Com Management Programs
The 3Com Management Programs is a graphical user interface that functions with the
Windows 2000 Server operating systems (Server, Advanced Server, and Datacenter
Server). See “3Com Management Programs” on page 85 for additional information.
3Com Management Programs have the following features:
■Vital Sign—The Vital Sign screen allows you to view vital NIC information, network
status, and network connectivity. Active NICs are listed.
■Diagnostics—The Diagnostics screen allows you to view information and utilize
functions to test this network interface card or LOM.
■Cable Analysis—From the Cable Analysis screen the user can monitor conditions of an
Ethernet CAT5 cable connection within a cable plant in an Ethernet network. The
software detects various cable conditions such as cable lengths between two given
nodes, cable pair breakage, cable pair polarity, and data skew between cable pairs.
■Load Balance/Virtual LANs—The Load Balance/Virtual LANs screen allows you to
configure advanced features. Any available NIC can be configured as part of a team.
■Statistics—The Statistics screen allows you view traffic statistics for most NICs.
Statistical values and coverage are more comprehensive for some NICs than
for others.

Creating a Driver Disk
5
Creating a Driver Disk
Create driver disks using the MakeDisk utility (setup.exe file). This utility will allow you to
create disks with the following drivers:
■Windows XP 32-bit Driver
■Windows XP 64-bit Driver
■Windows 2000 Driver
■Windows NT Driver
■NetWare Driver
■Advanced Server Features—Windows XP 64-bit Driver
■Advanced Server Features—Windows 2000 Driver
■Advanced Server Features—Windows NT Driver
■Advanced Server Features—NetWare Driver
■Advanced Server Features—Linux Driver
1Insert the 3Com Installation CD in the CD-ROM drive. Allow your operating system’s
autorun feature to launch the Master Navigator.
2Click NIC Software.
3Click Installation Utilities.
4Click Create Installation Diskette.
5In the Welcome window of the Diskette Creation Utility, click Next.
6Insert a 3.5” disk into floppy drive A (default) or B. Click Next.
7Follow the remaining Diskette Creation Utility commands and insert diskettes when
prompted. When all driver diskettes have been created, the message “Diskette Copy
Complete” appears on your screen.
8Click OK to end the Diskette Creation Utility.
9When all driver diskettes have been created, the information screen will appear,
confirming that the drivers were successfully created. Click OK.

7
2Installing and Connecting the NIC
System Requirements
Before installing the Gigabit Ethernet NIC, be sure your system meets the requirements
listed for your operating system.
Windows XP (64-bit)
■Itanium-based computer that meets Windows XP software requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■256 MB RAM (minimum)
■Microsoft Windows XP (64-bit version)
■Gigabit Ethernet NIC driver software for Windows XP
Windows XP (32-bit)
■Pentium-based computer that meets Windows XP software requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■128 MB RAM (minimum)
■Microsoft Windows XP (32-bit version)
■Gigabit Ethernet NIC driver software for Windows XP
Windows 2000
■Pentium-based computer that meets Windows 2000 software requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■128 MB RAM (minimum)
■Microsoft Windows 2000 (Server, Advanced Server, or Datacenter Server)
■Gigabit Ethernet NIC driver software for Windows 2000:
Windows NT
■Pentium-based computer that meets Windows NT 4.0 software requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■128 MB RAM (minimum)
■Microsoft Windows NT 4.0 (Server or Enterprise Server) with Service Pack 5 or later
■Gigabit Ethernet NIC driver software for Windows NT

2Installing and Connecting the NIC
8
NetWare
■Pentium-based computer that meets Novell NetWare 4.2/5.x/6.x software
requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■128 MB RAM (minimum)
■One of the following versions of Novell NetWare:
■Novell NetWare 5.0 or higher, with Support Pack 3 or the most recent NetWare 5
Support Pack
■Novell NetWare 4.2 with Support Pack 7 or the most recent Support Pack, including
the optional ODI v3.31 LAN drivers (MISC/ODI331).
You can get the appropriate updates from the Novell support Web site
■Gigabit Ethernet NIC driver software for Novell NetWare. (Note that the server ODI
driver can be found at the \netware\driver directory).
Linux
■Pentium-based computer that meets Linux software requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■128 MB RAM (minimum)
UNIX
■Pentium-based computer that meets corresponding UNIX software requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■128MB RAM (minimum)
Solaris
■Pentium-based computer that meets Solaris 8 software requirements
■One open 32-bit or 64-bit PCI slot
■PCI v2.2 33/66 MHz or PCI-x v1.0 64 bit 133 MHz
■128MB RAM (minimum)
■Solaris 8 operating system
NOTE: Although the driver should work with many Linux kernel versions and
distributions, it has only been tested on RedHat 6.2 and 7 Linux distributions for
i386 (kernel version 2.2.14 and 2.2.16), and the 2.4.0 test kernel. Furthermore,
the driver has only been tested as a loadable module.

Safety Precautions
9
Safety Precautions
Observe the following safety precautions.
Pre-Installation Checklist
1Check that your server meets the hardware and software requirements listed under
“System Requirements” on page 7.
2Verify that your system is using the latest BIOS.
3Review the information in the release.txt file on the 3Com Installation CD for
important information not available at the time this manual was created.
4If your system is active, shut it down.
■Under Windows 2000
If Windows 2000 is currently running, close all applications and select Start/Shut
Down. When the window appears, select Shut Down from the pull-down options,
and click OK.
■Under Windows NT
If Windows NT is currently running, close all applications and select Start/Shut
Down. Shut down the computer.
■Under NetWare
If Novell NetWare is currently running, use the down command (NetWare 5) or the
down and exit commands (NetWare 4) at the server_name prompt to gracefully
shut down the server functions and reach the DOS prompt:
server_name: down
server_name: exit
■Under Linux
If Redhat Linux is currently running, close all applications and at the command
prompt type init 0 to halt the machine. Once the machine is halted, you may
have to turn off the power switch manually.
5When system shut down is complete, turn the power off and unplug your system.
6Holding the NIC card by the edges, remove it from its shipping package and place it
on an anti-static surface.
7Check the NIC for visible signs of damage, particularly on the edge connector. Never
attempt to install any damaged NIC. If the NIC is damaged, report it to your supplier.
WARNING: The NIC is being installed in a system that operates with voltages that
can be lethal. Before you remove the cover of your system, you must observe the
following precautions to protect yourself and to prevent damage to the system
components.
■Remove any metallic objects or jewelry from your hands and wrists.
■Use only insulated or nonconducting tools.
■Verify that the system is powered OFF and unplugged before removing
the cover.
■Install or remove NICs only in a static-free environment. The use of a properly
grounded wrist strap (or other personal anti-static device) and an anti-static
mat are strongly recommended.
NOTE: If you acquired the adapter software on a floppy disk or from a third-party
support Web site, please check the appropriate source for the most recent
information.

2Installing and Connecting the NIC
10
Installing and Connecting the NIC
This manual covers two types of Gigabit Server NICs: server Ethernet NIC (3C996B-T):
and server fiber NIC (3C996-SX):
The procedure for installing a NIC in a system is identical for both NICs. Connecting the
network cables is different for Ethernet and fiber NICs (see “Connecting the Network
Cables” on page 12”).
Installing the NIC
1Review the precautions and pre-installation instructions. Before installing the NIC,
ensure the system power is off, the system is unplugged from the power outlet, and
that proper electrical grounding procedures have been followed. Refer to the
following figure to complete the remaining steps.
2Remove the system cover, and select any empty PCI slot. If you do not know how to
identify a PCI slot, refer to your system documentation.

Installing and Connecting the NIC
11
3Remove the blank cover plate from the slot that you selected (see item 1 in the
figure, below).
4Holding the PCI card by the edges, align the NIC’s connector edge with the PCI
connector dock.
5Applying even pressure at both corners of the card, push the NIC until it is firmly
seated in the PCI slot. When properly seated, the NIC’s port connectors will be aligned
with the slot opening, and its faceplate will be flush against the system chassis.
6Secure the NIC with the screw (see item 2 in the figure, below).
7Replace the system cover and disconnect any personal anti-static devices.
8Turn the system power on.
After the system returns to normal operation, the NIC hardware is fully installed. The next
step is to connect the network cables.
NOTE: For optimal performance, select a PCI-X slot. For second best
performance, select a 64-bit PCI slot.
NOTE: The connector dock in a 32-bit PCI slot is shorter than in a 64-bit PCI slot.
Although the NIC is designed to fit in either slot type, when installed in a 32-bit
PCI slot, part of the NIC’s connector edge will remain undocked. This is perfectly
normal.
CAUTION: Do not use excessive force when seating the card, as this may damage
the system or the NIC. If the card resists seating, remove it from the system,
realign it, and try again.
1
2

2Installing and Connecting the NIC
12
Connecting the Network Cables
Choose your type of NIC (Ethernet or fiber) and follow the procedure.
Ethernet NICs
Gigabit Ethernet NICs have one RJ-45 connector for attaching the system to an Ethernet
copper-wire segment. When automatic link negotiation is disabled, the port can be
configured for 10 Mbps or 100 Mbps signaling and either half-duplex or full-duplex
operation. To configure the port for 1000 Mbps, both link partners must be configured for
autonegotiation.
Follow this procedure for connecting a network cable to the Gigabit Ethernet NIC:
1Prepare an appropriate cable. The following table lists the cable characteristics for
connecting to 10/100/1000BASE-T ports:
2Connect one end of the cable to the Gigabit Ethernet NIC.
3Connect the other end of the cable to an RJ-45 Ethernet network port.
For driver installation and configuration instructions, refer to the software configuration
for that specific driver.
After the NIC hardware and its driver software have been properly installed on your
system, the LEDs indicate the following NIC states:
Port Type Connector Media Maximum Distance
10BASE-T RJ-45 CAT 3, 4, or 5 UTP 100 meters (325 feet)
100BASE-T RJ-45 CAT 5 UTP (two pair) 100 meters (325 feet)
1000BASE-T RJ-45 CAT5 UTP (four pair) 100 meters (325 feet)
NOTE: 1000BASE-T signaling requires four twisted pairs of Category 5 balanced
cabling, as specified in ISO/IEC 11801:1995 and EIA/TIA-568-A (1995) and tested
using procedures defined in TIA/EIA TSB95.
LED State Description
1000 On Good Gigabit Ethernet link.
Off No 1000 Mbps link; possible link at different speed, possible bad
cable, bad connector, or configuration mismatch.
100 On Good 100 Mbps Fast Ethernet link.
Off No 100 Mbps link; possible link at different speed, possible bad cable,
bad connector, or configuration mismatch.
10 On Good 10 Mbps Fast Ethernet link.
Off No 10 Mbps link; possible link at different speed, possible bad cable,
bad connector, or configuration mismatch.
ACT Blinking Brief bursts of data detected on the port.
On Streams of data detected on the port.
Off No data detected on the port.