D-Link DGE-560SX User manual

D-Link NetXtreme®
DGE-560SX User Guide
Gigabit Fiber (LC) PCI Express Server Adapter

D-Link DGE-560SX User Guide
2
Index
Chapter 1: Introduction .................................................................................................5
1.1 Functionality and Features:..............................................................................5
1.1.1 Features.................................................................................................5
1.1.2 Supported Operating Environments .....................................................6
1.2 Teaming ............................................................................................................7
1.2.1 Overview ...............................................................................................7
1.2.2 Load Balancing and Fault Tolerance......................................................7
1.3 Virtual LANs ...................................................................................................12
1.3.1 VLAN Overview ...................................................................................12
1.3.2 Adding VLANs to Teams ......................................................................14
1.4 SNMP Management .......................................................................................14
Chapter 2: Installing the Hardware..............................................................................17
2.1 System Requirements ....................................................................................17
2.1.1 Hardware Requirements .....................................................................17
2.1.2 Operating System Requirements ........................................................17
2.2 Safety Precautions..........................................................................................18
2.3 Preinstallation Checklist.................................................................................18
2.4 Installing the Adapter.....................................................................................19
Chapter 3: Installing the Driver Software.....................................................................20
3.1 Creating a Driver Disk.....................................................................................20
3.2 Broadcom Boot Agent Driver Software..........................................................20
3.2.1 Overview .............................................................................................21
3.2.2 Setting Up MBA in a Client Environment ............................................22
3.2.3 Setting Up MBA in a Server Environment ...........................................25
3.3 NDIS2 Driver Software ...................................................................................26
3.3.1 Preinstallation Requirements..............................................................26
3.3.2 Installing the NDIS2 Driver Software for Use on MS-DOS Platforms ..26
3.3.3 Installing the DOS NDIS2 Driver Software on the Hard Disk...............31
3.3.4 Configuring the NDIS2 Driver Software ..............................................32
3.3.5 Using Keywords for the B57.dos Drivers .............................................34
3.4 ODI Driver Software .......................................................................................35
3.4.1 Installing the Driver Software .............................................................35
3.4.2 Configuring Parameters for the B57.com Driver (in the Net.cfg file)..37
3.5 Linux Driver Software.....................................................................................38
3.5.1 Limitations...........................................................................................38
3.5.2 Packaging ............................................................................................38

D-Link DGE-560SX User Guide
3
3.5.3 Installing TG3 Driver Software ............................................................39
3.5.4 Network Installations ..........................................................................41
3.5.5 Patching PCI Files (Optional) ...............................................................41
3.5.6 Unloading/Removing the TG3 Driver..................................................41
3.5.7 Driver Messages..................................................................................42
3.5.8 Teaming with Channel Bonding ..........................................................43
3.6 NetWare Driver Software...............................................................................43
3.6.1 NetWare Core Driver Software ...........................................................43
3.6.2 Broadcom Advanced Server Program Driver Software (NetWare) .....54
3.6.3 SNMP Agent ........................................................................................71
3.7 Windows Driver Software..............................................................................71
3.7.1 Installing the Driver Software .............................................................71
3.7.2 Updating the Driver Software .............................................................74
3.7.3 Viewing or Changing the Properties of the Controller .......................74
3.7.4 Setting Power Management Options..................................................75
3.7.5 Removing the Device Drivers ..............................................................76
Chapter 4: Installing Management Applications..........................................................77
4.1 Installing Broadcom Advanced Control Suite and Related Management
Applications..........................................................................................................77
4.1.1 Using the Installer ...............................................................................77
4.1.2 Using Silent Installation.......................................................................78
4.2 Modifying Management Applications............................................................79
4.3 Repairing Management Applications.............................................................80
4.4 Removing Management Applications ............................................................80
Chapter 5: Using Broadcom Advanced Control Suite 4................................................81
5.1 Broadcom Advanced Control Suite Overview ................................................81
5.2 Starting Broadcom Advanced Control Suite...................................................81
5.3 Using Broadcom Advanced Control Suite ......................................................81
5.3.1 BACS Interface.....................................................................................82
5.3.2 Configuring Preferences......................................................................85
5.3.3 Connecting to a Host...........................................................................85
5.3.4 Managing the Host..............................................................................86
5.3.5 Managing the Network Adapter .........................................................88
5.4 Configuring Teaming ....................................................................................104
5.4.1 Using the Broadcom Teaming Wizard...............................................107
5.4.2 Using Expert Mode............................................................................116
Chapter 6: User Diagnostics .......................................................................................127
6.1 Introduction .................................................................................................127

D-Link DGE-560SX User Guide
4
6.2 System Requirements ..................................................................................127
6.3 Running D-Link NetXtreme User Diagnostics...............................................128
6.4 Diagnostic Test Descriptions ........................................................................131
6.5 Diagnostic Test Messages.............................................................................136
Chapter 7: Troubleshooting .......................................................................................139
7.1 Hardware Diagnostics ..................................................................................140
7.1.1 BACS Diagnostic Tests Failures ..........................................................140
7.1.2 BACS Network Test Failures...............................................................140
7.2 Troubleshooting Checklist ............................................................................141
7.3 Checking for Network Link and Activity .......................................................142
7.4 Checking if Current Drivers are Loaded .......................................................142
7.5 Testing Network Connectivity ......................................................................143
7.6 Software Problems and Solutions................................................................144
7.6.1 How to Add a Third-Party OEM Network Adapter to a RIS Installation
....................................................................................................................144
7.6.2 RIPREP Utility Problem......................................................................145
7.6.3 Linux and ASFIPMon .........................................................................147
7.6.4 Broadcom Boot Agent.......................................................................147
7.6.5 Broadcom Advanced Server Program (BASP)....................................147
7.6.6 Miscellaneous ...................................................................................148
Information in this document is subject to change without notice.
© 2011 Broadcom Corporation. All rights reserved.
Broadcom, the pulse logo, Connecting everything, the Connecting everything logo,
NetXtreme, Ethernet@Wirespeed, LiveLink, and Smart Load Balancing are among the
trademarks of Broadcom Corporation and/or its affiliates in the United States, certain other
countries, and/or the EU. Microsoft and Windows are trademarks of Microsoft Corporation.
Linux is a trademark of Linus Torvalds. NetWare is a trademark of Novell Corporation. Intel is
a trademark of Intel Corporation. Magic Packet is a trademark of Advanced Micro Devices, Inc.
Red Hat is a trademark of Red Hat, Inc. PCI Express is a trademark of PCI-SIG. Any other
trademarks or trade names mentioned are the property of their respective owners.

D-Link DGE-560SX User Guide
5
Chapter 1: Introduction
1.1 Functionality and Features:
D-Link NetXtreme Gigabit Ethernet adapters connect a PCI Express™ compliant system to a
Gigabit Ethernet network.
D-Link NetXtreme Gigabit Ethernet adapters target the increased congestion experienced at
the backbone and system in today's networks and provide a future upgrade path for systems
that require more bandwidth than Fast Ethernet can provide.
Using the Broadcom teaming software, you can split your network into virtual LANs (VLANs)
as well as group multiple network adapters together into teams to provide network load
balancing and fault tolerance functionality. See Teaming and Broadcom Gigabit Ethernet
Teaming Services for detailed information about teaming. See Virtual LANs for a description
of VLANs. See Configuring Teaming for instructions on configuring teaming and creating
VLANs on Windows and NetWare operating systems.
1.1.1 Features
The following is a list of the D-Link NetXtreme Gigabit Ethernet adapter features for all
supported operating systems:
Gigabit Ethernet (IEEE Std 802.3-1999)
Logical Link Control (IEEE Std 802.2)
Flow Control (IEEE Std 802.3x)
Standard Ethernet frame size (1518 bytes)
Jumbo frames (up to 9 KB)
NetWare 5.1 does not support Jumbo frames.
Layer-2 Priority Encoding (IEEE 802.1p)
High-speed on-chip RISC processor
Adaptive interrupt frequency
Up to 4 classes of service (CoS)

D-Link DGE-560SX User Guide
6
Up to 4 send rings and receive rings
Integrated 96 KB frame buffer memory
GMI/MII Management Interface
Statistics for SNMP MIB II, Ethernet-like MIB, and Ethernet MIB (IEEE Std 802.3z,
Clause 30)
4 unique MAC unicast addresses
Support for multicast addresses via 128 bits hashing hardware function
Serial EEPROM or serial NVRAM flash memory
Supports PXE 2.1 specification (Linux Red Hat PXE Server, Windows 2000 Server,
Windows Server 2003, Intel APITEST, DOS UNDI)
JTAG support
ACPI
LiveLink™ (supported in both the 32-bit and 64-bit Windows operating systems
Self boot
Adaptive Interrupt Frequency
The adapter driver intelligently adjusts host interrupt frequency based on traffic conditions,
to increase overall application throughput. When traffic is light, the adapter driver interrupts
the host for each received packet, minimizing latency. When traffic is heavy, the adapter
issues one host interrupt for multiple, back-to-back incoming packets, preserving host CPU
cycles.
Broadcom Advanced Control Suite
Broadcom Advanced Control Suite (BACS), a component of the Broadcom teaming software,
is an integrated utility that provides useful information about each network adapter that is
installed in your system. The BACS utility also enables you to perform detailed tests,
diagnostics, and analyses on each adapter, as well as to modify property values and view
traffic statistics for each adapter. BACS is used on Windows operating systems to configure
teaming and to add VLANs. See Using Broadcom Advanced Control Suite for detailed
information and instructions.
1.1.2 Supported Operating Environments
The D-Link NetXtreme Gigabit Ethernet adapter has software support for the following
operating systems:

D-Link DGE-560SX User Guide
7
Microsoft®Windows®(32-bit and 64-bit extended)
Linux®(32-bit and 64-bit extended)
MS-DOS®
NetWare®
1.2 Teaming
1.2.1 Overview
Adapter teaming allows you to group network adapters together to function as a team. The
benefits of teaming include allowing membership to VLANs, providing load balancing between
adapters, and offering fault tolerance. These benefits can be combined such that you can
couple the functionality of load balancing for the load balance members and the capability of
employing a failover with having the team participate on different VLANs.
Broadcom Advanced Server Program (BASP) is the Broadcom teaming software for Windows
Server 2003, Windows Server 2008, and NetWare operating systems. For Windows operating
systems, BASP is configured through the Broadcom Advanced Control Suite (BACS) utility.
For NetWare operating systems, teams are configured by loading BASP with all the necessary
frames for the team. For Linux operating systems, teaming is done with channel bonding.
BASP supports four types of load balancing teams:
Smart Load Balancing and Failover
Link Aggregation (802.3ad)
Generic Trunking (FEC/GEC)/802.3ad-Draft Static
SLB (Auto-Fallback Disable)
NOTE: Enabling Windows Server 2003 built-in bridging is not advisable when you
are using teaming software.
1.2.2 Load Balancing and Fault Tolerance
Teaming provides traffic load balancing and fault tolerance (redundant adapter operation in
the event that a network connection fails). When multiple adapters are installed in the same
system, they can be grouped with up to four teams.

D-Link DGE-560SX User Guide
8
Each team can consist of up to eight adapters, with one adapter used as a standby for Smart
Load Balancing and Failover (SLB) or SLB (Auto-Fallback Disabled) team types. If traffic is not
identified on any of the adapter team member connections due to failure of the adapter, cable,
or switch, the load will be distributed to the remaining team members with an active
connection. In the event that all primary adapters fail, traffic will be distributed to the standby
adapter. Existing sessions are maintained with no impact on the user.
Types of Teams
The available types of teams for the supported operating systems are shown in the following
table:
Table 1. Types of Teams
Operating System
Available Types of Teams
Windows Server 2003
Windows Server 2008
Smart Load Balancing and Failover
Link Aggregation (802.3ad)
Generic Trunking (FEC/GEC)/802.3ad-Draft Static
SLB (Auto-Fallback Disable)
Linux
Team adapters using the bonding kernel module and a
channel bonding interface. See your Red Hat documentation
for more information.
NetWare
Smart Load Balancing
Link Aggregation (802.3ad)
Generic Trunking
Smart Load Balancing™ and Failover
Smart Load Balancing™ and Failover is the Broadcom implementation of load balancing
based on IP flow. This feature supports balancing IP traffic across multiple adapters (team
members) in a bidirectional manner. In this type of team, all adapters in the team have
separate MAC addresses. This type of team provides automatic fault detection and dynamic
failover to other team member or to a hot standby member. This is done independently of
Layer 3 protocol (IP, IPX, NetBEUI); rather, it works with existing Layer 2 and Layer 3
switches. No switch configuration (such as trunk, link aggregation) is necessary for this type
of team to work.
NOTES:
oIf you do not enable LiveLink™ when configuring SLB teams, disabling
Spanning Tree Protocol (STP) at the switch or port is recommended. This

D-Link DGE-560SX User Guide
9
minimizes the downtime due to spanning tree loop determination when
failing over. LiveLink mitigates such issues.
oIPX balances only on the transmit side of the team; other protocols are
limited to the primary adapter.
oIf a team member is linked at 1000 Mbit/s and another team member is
linked at 100 Mbit/s, most of the traffic is handled by the 1000 Mbit/s team
member.
Link Aggregation (802.3ad)
This mode supports link aggregation and conforms to the IEEE 802.3ad (LACP) specification.
Configuration software allows you to dynamically configure which adapters you want to
participate in a given team. If the link partner is not correctly configured for 802.3ad link
configuration, errors are detected and noted. With this mode, all adapters in the team are
configured to receive packets for the same MAC address. The outbound load-balancing
scheme is determined by our BASP driver. The team link partner determines the
load-balancing scheme for inbound packets. In this mode, at least one of the link partners
must be in active mode.
Generic Trunking (FEC/GEC)/802.3ad-Draft Static
The Generic Trunking (FEC/GEC)/802.3ad-Draft Static type of team is very similar to the Link
Aggregation (802.3ad) type of team in that all adapters in the team are configured to receive
packets for the same MAC address. The Generic Trunking (FEC/GEC)/802.3ad-Draft Static)
type of team, however, does not provide LACP or marker protocol support. This type of team
supports a variety of environments in which the adapter link partners are statically configured
to support a proprietary trunking mechanism. For instance, this type of team could be used
to support Lucent's OpenTrunk or Cisco's Fast EtherChannel (FEC). Basically, this type of
team is a light version of the Link Aggregation (802.3ad) type of team. This approach is much
simpler, in that there is not a formalized link aggregation control protocol (LACP). As with the
other types of teams, the creation of teams and the allocation of physical adapters to various
teams is done statically through user configuration software.
The Generic Trunking (FEC/GEC/802.3ad-Draft Static) type of team supports load balancing
and failover for both outbound and inbound traffic.
SLB (Auto-Fallback Disable)

D-Link DGE-560SX User Guide
10
The SLB (Auto-Fallback Disable) type of team is identical to the Smart Load Balancing and
Failover type of team, with the following exception—when the standby member is active, if a
primary member comes back on line, the team continues using the standby member, rather
than switching back to the primary member.
If any primary adapter assigned to a team is disabled, the team functions as a Smart Load
Balancing and Failover type of team in which auto-fallback occurs.
All primary interfaces in a team participate in load-balancing operations by sending and
receiving a portion of the total traffic. Standby interfaces take over in the event that all
primary interfaces have lost their links.
Failover teaming provides redundant adapter operation (fault tolerance) in the event that a
network connection fails. If the primary adapter in a team is disconnected because of failure
of the adapter, cable, or switch port, the secondary team member becomes active,
redirecting both inbound and outbound traffic originally assigned to the primary adapter.
Sessions will be maintained, causing no impact to the user.
Limitations of Smart Load Balancing and Failover/SLB (Auto-Fallback
Disable) Types of Teams
Smart Load Balancing™ (SLB) is a protocol-specific scheme. The level of support for IP, IPX,
and NetBEUI protocols is listed below.
Table 2. Smart Load Balancing
Operating
System
Failover/Fallback—All
Broadcom
Failover/Fallback—Multivendor
Protocol
IP
IPX
NetBEUI
IP
IPX
NetBEUI
Windows Server
2003
Y
Y
N/S
Y
N
N/S
Windows Server
2008
Y
Y
N/S
Y
N
N/S
NetWare 5.1/6.5
Y
Y
N/S
Y
N
N/S
Red Hat Linux 3
and 4
Y
N/S
N/S
Y
N/S
N/S
Operating
System
Load Balance—All Broadcom
Load Balance—Multivendor
Protocol
IP
IPX
NetBEUI
IP
IPX
NetBEUI
Windows Server
Y
Y
N/S
Y
N
N/S

D-Link DGE-560SX User Guide
11
2003
Windows Server
2008
Y
Y
N/S
Y
N
N/S
NetWare 5.1/6.5
Y
Y
N/S
Y
Y
N/S
Red Hat Linux 3
and 4
Y
N/S
N/S
Y
N/S
N/S
Legend:
Y = yes
N = no
N/S = not supported
Drivers for third-party network adapters must be NetWare Event Service Layer (NESL)
compliant for NetWare to be fault-tolerant and load-balanced in a multivendor team.
The Smart Load Balancing type of team works with all Ethernet switches without having to
configure the switch ports to any special trunking mode. Only IP traffic is load-balanced in
both inbound and outbound directions. IPX traffic is load-balanced in the outbound direction
only. Other protocol packets are sent and received through one primary interface only.
Failover for non-IP traffic is supported only for Broadcom network adapters. The Generic
Trunking type of team requires the Ethernet switch to support some form of port trunking
mode (for example, Cisco's Gigabit EtherChannel or other switch vendor's Link Aggregation
mode). The Generic Trunking type of team is protocol-independent, and all traffic should be
load-balanced and fault-tolerant.
NOTE: If you do not enable LiveLink™ when configuring teams, disabling Spanning Tree
Protocol (STP) at the switch is recommended. This minimizes the downtime due to the
spanning tree loop determination when failing over. LiveLink mitigates such issues.
LiveLink™ Functionality
LiveLink™ functionality is a feature of BASP that is available only for the Smart Load
Balancing™ and Failover type of teaming. The purpose of LiveLink is to detect network
connectivity beyond the switch and to route traffic only through team members that have a
live link. This function is accomplished though the teaming software. The teaming software
periodically probes (issues a link packet from each team member) one or more specified
target network adapter(s). The probe target(s) responds when it receives the link packet. If
a team member does not detect a response within a specified amount of time after a specified
number of retries, the teaming software discontinues passing traffic through that team

D-Link DGE-560SX User Guide
12
member. Later, if that team member begins to detect a response from a probe target, this
indicates that the link has been restored, and the teaming software automatically resumes
passing traffic through that team member. LiveLink works only with TCP/IP.
LiveLink™ functionality is supported in both 32-bit and 64-bit Windows operating systems,
but is not supported in NetWare systems. For similar functionality in Linux operating systems,
refer to Channel Bonding in your Red Hat documentation.
Teaming and Large Send Offload/Checksum Offload Support
Large Send Offload (LSO) and Checksum Offload are enabled for a team only when all of the
members support and are configured for the feature.
1.3 Virtual LANs
1.3.1 VLAN Overview
Virtual LANs (VLANs) allow you to split your physical LAN into logical parts, to create logical
segmentation of workgroups, and to enforce security policies for each logical segment. Each
defined VLAN behaves as its own separate network with its traffic and broadcasts isolated
from the others, increasing bandwidth efficiency within each logical group. Up to 64 VLANs
(63 tagged and 1 untagged) can be defined for each Broadcom adapter on your server,
depending on the amount of memory available in your system.
VLANs can be added to a team to allow multiple VLANs with different VLAN IDs. A virtual
adapter is created for each VLAN added.
Although VLANs are commonly used to create individual broadcast domains and/or separate
IP subnets, it is sometimes useful for a server to have a presence on more than one VLAN
simultaneously. Broadcom adapters support multiple VLANs on a per-port or per-team basis,
allowing very flexible network configurations.

D-Link DGE-560SX User Guide
13
Figure 1: Example of Servers Supporting Multiple VLANs with Tagging
Figure 1 shows an example network that uses VLANs. In this example network, the physical
LAN consists of a switch, two servers, and five clients. The LAN is logically organized into
three different VLANs, each representing a different IP subnet. The features of this network
are described in Table 1:
Table 1: Example VLAN Network Topology
Component
Description
VLAN #1
An IP subnet consisting of the Main Server, PC #3, and PC #5. This subnet
represents an engineering group.
VLAN #2
Includes the Main Server, PCs #1 and #2 via shared media segment, and PC
#5. This VLAN is a software development group.
VLAN #3
Includes the Main Server, the Accounting Server and PC #4. This VLAN is an
accounting group.
Main Server
A high-use server that needs to be accessed from all VLANs and IP subnets.
The Main Server has a Broadcom adapter installed. All three IP subnets are
accessed via the single physical adapter interface. The server is attached to
one of the switch ports, which is configured for VLANs #1, #2, and #3. Both
the adapter and the connected switch port have tagging turned on. Because
of the tagging VLAN capabilities of both devices, the server is able to
communicate on all three IP subnets in this network, but continues to
maintain broadcast separation between all of them.
Accounting
Server
Available to VLAN #3 only. The Accounting Server is isolated from all traffic
on VLANs #1 and #2. The switch port connected to the server has tagging
turned off.
PCs #1 and
Attached to a shared media hub that is then connected to the switch. PCs #1

D-Link DGE-560SX User Guide
14
#2
and #2 belong to VLAN #2 only, and are logically in the same IP subnet as
the Main Server and PC #5. The switch port connected to this segment has
tagging turned off.
PC #3
A member of VLAN #1, PC #3 can communicate only with the Main Server
and PC #5. Tagging is not enabled on PC #3 switch port.
PC #4
A member of VLAN #3, PC #4 can only communicate with the servers.
Tagging is not enabled on PC #4 switch port.
PC #5
A member of both VLANs #1 and #2, PC #5 has an Broadcom adapter
installed. It is connected to switch port #10. Both the adapter and the switch
port are configured for VLANs #1 and #2 and have tagging enabled.
NOTE: VLAN tagging is only required to be enabled on switch ports that create trunk links
to other switches, or on ports connected to tag-capable end-stations, such as servers or
workstations with Broadcom adapters.
1.3.2 Adding VLANs to Teams
Each team supports up to 64 VLANs (63 tagged and 1 untagged). Note that only Broadcom
adapters and Alteon®AceNIC adapters can be part of a team with VLANs. With multiple
VLANs on an adapter, a server with a single adapter can have a logical presence on multiple
IP subnets. With multiple VLANs in a team, a server can have a logical presence on multiple
IP subnets and benefit from load balancing and failover. For instructions on adding a VLAN to
a team, see Adding a VLAN for Windows operating systems or see Configuring VLANs for
NetWare operating systems.
NOTE: Adapters that are members of a failover team can also be configured to support
VLANs. Because VLANs are not supported for an Intel LOM, if an Intel LOM is a member of a
failover team, VLANs cannot be configured for that team.
1.4 SNMP Management
BASP Subagent
The BASP subagent, baspmgnt.dll, is designed for the Windows Server 2003, and Windows
Server 2008 SNMP service. It is required to install the SNMP service before installing the
BASP subagent.

D-Link DGE-560SX User Guide
15
The BASP subagent allows an SNMP manager software to actively monitor the configurations
and performance of the Broadcom Advanced Server features. The subagent also provides an
alarm trap to an SNMP manager to inform the manager of any changes to the conditions of
the BASP component.
The BASP subagent allows monitoring of the configurations and statistics for the BASP teams,
the physical NIC adapters participating in a team, and the virtual NIC adapters created as the
result of teaming. Non-teamed NIC adapters are not monitored at this time. The BASP
configuration data includes information such as team IDs, physical/virtual/VLAN/team
adapter IDs, physical/virtual/VLAN/team/ adapter descriptions, and MAC addresses of the
adapters.
The statistics include detailed information such as data packets transmitted and received for
the physical/virtual/VLAN/team adapters.
The alarm trap forwards information about the changes in configuration of the physical
adapters participating in a team, such as physical adapter link up/down, and adapter
installed/removed events.
To monitor this information, an SNMP manager must load the Broadcom BASP MIB database
files to allow monitoring of the information described above. These files, which are shown
below, are included with the installation CD:
baspcfg.mib
baspstat.mib
basptrap.mib
BASP Extensible-Agent
The D-Link NetXtreme Gigabit Ethernet Controller Extended Information SNMP
extensible-agent, bcmif.dll, is designed for Windows Server 2003, and Windows Server 2008
SNMP service.
The extensible-agent allows the SNMP manager software to actively monitor the
configurations of the D-Link NetXtreme adapter. It is intended to supplement the information
already provided by the standard SNMP Management Network Interface information.

D-Link DGE-560SX User Guide
16
The extensible-agent provides in-depth information about a D-Link NetXtreme adapter such
as:
MAC address
Bound IP address
IP subnet mask
Physical link status
Adapter state
Line speed
Duplex mode
Memory range
Interrupt setting
Bus number
Device number
Function number
To monitor this information, a SNMP manager needs to load the Broadcom Extended
information MIB file to allow monitoring of the information described above. This file,
bcmif.mib, is included on the D-Link NetXtreme adapter installation CD.
The monitored workstation requires the installation of the Broadcom Extended Information
SNMP extensible-agent, bcmif.dll, and requires the Windows Server 2003, and Windows
Server 2008 SNMP service to be installed and loaded.

D-Link DGE-560SX User Guide
17
Chapter 2: Installing the Hardware
2.1 System Requirements
Before you install the D-Link NetXtreme Gigabit Ethernet adapter, verify that your system
meets the requirements listed for your operating system:
2.1.1 Hardware Requirements
Pentium-based system that meets operating system requirements
One open 32-bit or 64-bit PCI Express slot
128-MB RAM (minimum) for Windows and Linux. 64-MB RAM (minimum) for NetWare
2.1.2 Operating System Requirements
General
PCI Express 2.0 Host Interface
Microsoft Windows
One of the following versions of Microsoft Windows:
Windows Server 2003 Family
Windows Server 2008 Family
Novell NetWare
One of the following versions of Novell NetWare: NetWare 4.2, NetWare 5.1, NetWare 6.0, or
NetWare 6.5, with the latest support pack.
Linux
NOTE: The current version of the adapter driver has been tested on the latest Red Hat,
SuSE, and other Linux distributions for i386, ia64, and x86_64 CPU architectures using 2.4.x
and 2.6.x kernels. The driver has been tested up to kernel version 2.4.33 and 2.6.13. The
driver should work on other little endian or big endian CPU architectures, but only very limited

D-Link DGE-560SX User Guide
18
testing has been done on some of these machines. The Makefile may have to be modified to
include architecture-specific compile switches, and some minor changes in the source files
may also be required. On these machines, patching the driver into the kernel is
recommended.
2.2 Safety Precautions
CAUTION! The adapter 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:
oRemove any metallic objects or jewelry from your hands and wrists.
oMake sure to use only insulated or nonconducting tools.
oVerify that the system is powered OFF and unplugged before you touch
internal components.
oInstall or remove adapters in a static-free environment. The use of a properly
grounded wrist strap or other personal antistatic devices and an antistatic
mat is strongly recommended.
2.3 Preinstallation Checklist
1. Verify that your server meets the hardware and software requirements listed under
System Requirements.
2. Verify that your server is using the latest BIOS.
NOTE: If you acquired the adapter software on a floppy disk or from the Broadcom
support website
(http://www.broadcom.com/support/ethernet_nic/downloaddrivers.php), verify the
path to the adapter driver files.
3. If your system is active, shut it down.
4. When system shutdown is complete, turn off the power and unplug the power cord.
5. Holding the adapter card by the edges, remove it from its shipping package and place
it on an antistatic surface.

D-Link DGE-560SX User Guide
19
6. Check the adapter for visible signs of damage, particularly on the card edge connector.
Never attempt to install any damaged adapter.
2.4 Installing the Adapter
The following instructions apply to installing the D-Link NetXtreme Gigabit Ethernet adapter
(add-in NIC) in most servers. Refer to the manuals that were supplied with your server for
details about performing these tasks on your particular server.
1. Review the Safety Precautions and Preinstallation Checklist. Before installing the
adapter, ensure the system power is OFF and unplugged from the power outlet, and
that proper electrical grounding procedures have been followed.
2. Open the system case, and select any empty PCI Express slot. If you do not know
how to identify any of these PCI slots, refer to your system documentation.
3. Remove the blank cover-plate from the slot that you selected.
4. Align the adapter connector edge with the connector slot in the system.
5. Applying even pressure at both corners of the card, push the adapter card into the
slot until it is firmly seated. When the adapter is properly seated, the adapter port
connectors are aligned with the slot opening, and the adapter faceplate is flush
against the system chassis.
CAUTION! Do not use excessive force when seating the card as this may
damage the system or the adapter. If you have difficulty seating the adapter,
remove it, realign it, and try again.
6. Secure the adapter with the adapter clip or screw.
7. Close the system case and disconnect any personal antistatic devices.

D-Link DGE-560SX User Guide
20
Chapter 3: Installing the Driver
Software
3.1 Creating a Driver Disk
Create driver disks using the Broadcom MakeDisk utility (Setup.exe file). This utility runs
under Windows and allows you to create disks with the following drivers:
Windows Server 2003 (IA32, IA64, X64 (AMD64))
NetWare 5.x/6
NetWare BASP
MS-DOS Open Data-Link Interface (ODI)
To create a driver disk or file
1. Insert a 3.5-inch disk into drive A (default) or create a folder on your hard disk.
2. Insert the installation CD into your system CD-ROM drive.
3. If the CD does not automatically run, then browse to the MakeDisk folder on the CD
and double-click Setup.exe.
4. Follow the onscreen instructions.
5. Select the driver or drivers of choice. Note that selecting multiple drivers results in
creating multiple disks.
6. Click Next.
7. Click OK.
8. If more than one driver was selected, Setup Needs the Next Disk is displayed
again. Insert another 3.5-inch disk or browse to another folder and click OK.
When all driver disks have been created, an information screen is displayed confirming that
the disks were successfully created. Click OK.
3.2 Broadcom Boot Agent Driver Software