User’s Guide
Networking
3000/3100 Series
NE0154601-00 C
User’s Guide—Networking
3000/3100 Series
Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no
responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its
use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications
described in this document for any of these products are for illustrative purposes only. QLogic Corporation makes no
representation nor warranty that such applications are suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.
Document Revision History
Version 4.0, 1/07/09
Version 4.1, 1/27/09
Version 4.2, 3/23/09
Version 4.3, 4/09/09
Version 4.4, 4/20/09
Version 4.5, 4/30/09
Rev. A, Version 4.6, 6/15/09
Rev. B, Version 4.7, 2/26/10
Rev. C, Version 4.7, 2/8/11
Changes Sections Affected
Updated URL of downloads section of the QLogic
All
Web site.
Removed Application Notes section “Overview” on page 1-1
Updated the instructions for uninstalling the NIC
“Uninstall the NIC Driver” on page 5-6
driver in Windows Server 2003.
Updated the instructions for uninstalling the NIC
driver in Windows Server 2008.
“Windows Server 2008 NIC Driver Uninstall (Previous Version)” on page 6-12
ii NE0154601-00 C
Table of Contents
Preface
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Knowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
1Overview
Obtaining the Latest Software Release Information. . . . . . . . . . . . . . . . . . . 1-1
QLogic 3000 and 3100 Series Intelligent Ethernet Adapters . . . . . . . . . . . . 1-1
2 System Requirements
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Cable Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
SFP+ Optical Module Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Supported QLogic Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
3 Quick Start
QLogic Adapter Installation and Verification. . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Pre-installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
QLogic Adapter Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Verify the QLogic Adapter Installation . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Windows Server
Windows Server Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Pre-installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Windows Server 2008 and 2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Linux Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Pre-installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Verify and Remove Existing QLogic Adapter Driver and Tools Package 3-4
NE0154601-00 C iii
® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-2
User’s Guide—Networking
3000/3100 Series
Install the Driver (RPM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Red Hat
SUSE
®
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
®
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
QLogic Adapter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
4 Hardware Installation
QLE3044 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Ethernet Port Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
QLE3044 Status LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
QLE3044 Bracket Removal and Replacement . . . . . . . . . . . . . . . . . . 4-3
QLE3142 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
QLE3142 Status LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
QLE3142 Bracket Removal and Replacement . . . . . . . . . . . . . . . . . . 4-5
5 Windows Server 2003 Driver Installation
Driver Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Firmware ROM Image Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Windows Server NIC Driver Installation and Verification . . . . . . . . . . . . . . . 5-2
Windows Server 2003 NIC Driver Installation . . . . . . . . . . . . . . . . . . . 5-2
Windows Server 2003 NIC Driver Installation Verification. . . . . . . . . . 5-5
Uninstall the NIC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
6 Windows Server 2008 and 2008 R2 Driver Installation
Driver Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Firmware ROM Image Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Windows Server 2008 NIC Driver Installation and Verification. . . . . . . . . . . 6-2
Windows Server 2008 NIC Driver Installation . . . . . . . . . . . . . . . . . . . 6-2
Windows Server 2008 NIC Driver Installation Verification. . . . . . . . . . 6-5
Windows Server 2008 and 2008 R2 Teaming Driver Installation
and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Windows Server 2008 and 2008 R2 Teaming Driver Installation . . . . 6-6
Windows Server 2008 and 2008 R2 Teaming Driver Configuration . . 6-8
Windows Server 2008 NIC Driver Uninstall (Previous Version) . . . . . . . . . . 6-12
Windows Server 2008 NIC and Teaming Driver Uninstall . . . . . . . . . . . . . . 6-13
7 Windows Server 2003, 2008, and 2008 R2 Driver Configuration
NIC Driver Properties and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
QLogic Adapter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
QLogic Adapter Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Windows Server 2003 Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Performance Testing the QLogic Adapter with ntttcp . . . . . . . . . . . 7-13
iv NE0154601-00 C
ntttcp Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
ntttcps and ntttcpr Command Line Options . . . . . . . . . . . . . . . . 7-15
Tcp1323Opts Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Modifying the Tcp1323Opts Parameter . . . . . . . . . . . . . . . . . . 7-17
Creating the Tcp1323Opts Parameter . . . . . . . . . . . . . . . . . . . 7-18
Setting the TcpWindowSize Parameter . . . . . . . . . . . . . . . . . . . . . . 7-20
8 Linux Driver Installation and Configuration
Linux Driver Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Locate the Firmware ROM Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Locate the Driver File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Verify the Firmware Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Verify the Driver Version and Module Information . . . . . . . . . . . . . . . . 8-2
Locate the QLogic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Build the Linux Driver Source Code . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Enable the Inbox Kernel GPL and Commercial Drivers . . . . . . . . . . . 8-2
Check for MSI-X Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Inbox Kernel GPL Driver and Blacklisting . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Preparing for QLogic Adapter Driver Installation . . . . . . . . . . . . . . . . . . . . . 8-5
QLogic Adapter Driver Installation (RPM Format) . . . . . . . . . . . . . . . . . . . . 8-5
Install the Linux Driver Source in RPM Format . . . . . . . . . . . . . . . . . . 8-5
Create the Binary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Install the Binary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Install the QLogic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Linux QLogic Adapter Driver Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Ethtool Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Configure the QLogic Adapter on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Uninstall the Commercial GPL Driver and Tools Package . . . . . . . . . . . . . . 8-8
Diagnostic Tests for the QLogic Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Linux Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Performance Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Using the iperf Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
User’s Guide—Networking
3000/3100 Series
9 Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Linux Bonding Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Active-Backup or Mode=1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Round-Robin or Mode=0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Bonding Driver Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
NE0154601-00 C v
User’s Guide—Networking
3000/3100 Series
Bonding Driver Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
arp_interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
arp_ip_target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
downdelay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
lacp_rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
QLogic Adapter Bonding Modes Under Linux . . . . . . . . . . . . . . . . . . . 9-5
Configuring Virtual LAN (VLAN) Under Linux. . . . . . . . . . . . . . . . . . . . . . . . 9-7
10 Firmware Management
Windows Server Dynamic Firmware Download . . . . . . . . . . . . . . . . . . . . . . 10-1
Linux Dynamic Firmware Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
11 Troubleshooting Guidelines
Unable to Boot the Host System with the QLogic Adapter Installed . . . . . . 11-1
Unable to Send/Receive Network Traffic Using the QLogic Adapter . . . . . . 11- 1
Additional Configuration for Windows Server 2008 Teaming . . . . . . . . . . . . 11-2
Troubleshooting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Windows Server Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Linux Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Check for System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 -4
Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
MSI-X Interrupts for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
PCI Express Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
A Diagnostic Utility Commands
B Flash Update
Flash Update and Tool Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Flash Update Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
nxflash Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
NX Live CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
NX Live USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
NX Live Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
QLogic Adapter Flash Update—Windows Server . . . . . . . . . . . . . . . . . . . . B-3
Using the Flash Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Flash Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Updating the Flash on Multiple Standalone QLogic Adapters . . . . . . . B-7
vi NE0154601-00 C
User’s Guide—Networking
3000/3100 Series
QLogic Adapter Flash Update—Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Using the Flash Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Flash Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Glossary
Index
List of Figures
Figure Page
4-1 QLE3044 Port Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4-2 QLE3044 Status LEDs—Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4-3 QLE3044 Bracket Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4-4 QLE3044 Bracket Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4-5 QLE3142 Installation and Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4-6 QLE3142 Status LEDs—Side View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4-7 QLE3142 Bracket Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4-8 QLE3142 Bracket Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
5-1 Windows Server 2003—Found New Hardware Wizard Dialog Box. . . . . . . . . . . . . 5-2
5-2 Windows Server 2003—NIC Driver Location Information . . . . . . . . . . . . . . . . . . . . 5-3
5-3 Windows Server 2003—Select NIC Driver Location . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5-4 Windows Server 2003—Browse for Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5-5 Windows Server 2003—Software Installation Progress. . . . . . . . . . . . . . . . . . . . . . 5-4
5-6 Windows Server 2003—Software Installation Complete . . . . . . . . . . . . . . . . . . . . . 5-5
5-7 NIC Driver Installation Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
6-1 Windows Server 2008—Setup Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6-2 Windows Server 2008—License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6-3 Windows Server 2008 — Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6-4 Windows Server 2008—Select Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6-5 Windows Server 2008—Confirm Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6-6 Windows Server 2008—Installation Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
6-7 NIC Driver Installation Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
6-8 Windows Server 2008—Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
6-9 Windows Server 2008—Advanced Network Config Service Setup Wizard . . . . . . . 6-7
6-10 Windows Server 2008 Teaming—Select Network Configuration Service . . . . . . . . 6-8
6-11 Windows Server 2008 Teaming—Network Configuration Service Window . . . . . . . 6-9
6-12 Windows Server 2008 Teaming—Creating a Team . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
6-13 Windows Server 2008 Teaming—Create Team Window . . . . . . . . . . . . . . . . . . . . . 6-11
6-14 Windows Server 2008 Teaming—Create Team Progress Bar . . . . . . . . . . . . . . . . . 6-11
6-15 Windows Server 2008 Teaming—Team Management Window . . . . . . . . . . . . . . . . 6-12
6-16 Windows Server 2008 Teaming Uninstall Procedure . . . . . . . . . . . . . . . . . . . . . . . . 6-13
7-1 Adapter Properties—General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7-2 Network Connections Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7-3 Local Area Connection Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
7-4 Internet Protocol (TCP/IP) Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
NE0154601-00 C vii
User’s Guide—Networking
3000/3100 Series
7-5 Adapter Properties—Diagnostics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
7-6 Run Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
7-7 Location of ntttcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
7-8 Run Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
7-9 Registry Editor—HKEY_LOCAL_MACHINE Directory . . . . . . . . . . . . . . . . . . . . . . 7-17
7-10 Registry Editor—Parameter Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
7-11 New Key—DWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
7-12 Creating Tcp1323Opts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
7-13 Edit DWORD Value Window—Tcp1323Opts Parameter . . . . . . . . . . . . . . . . . . . . 7-20
7-14 Modifying the TcpWindowSize Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
7-15 Edit DWORD Value Window — TcpWindowSize Parameter. . . . . . . . . . . . . . . . . 7-21
List of Tables
Table Page
1-1 QLogic 3000 and 3100 Series Intelligent Ethernet Adapters . . . . . . . . . . . . . . . . . 1-1
2-1 Cable Specifications—Optical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2-2 Cable Specifications—Copper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
4-1 Mapping of Port Number, PCI Function, and Ethernet Interface . . . . . . . . . . . . . . . 4-2
4-2 QLE3044 LED Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
7-1 Advanced Properties Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7-2 ntttcps and ntttcpr Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
7-3 Tcp1323Opts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
7-4 Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
8-1 modprobe Command Optional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
9-1 Bonding Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
11-1 Troubleshooting Tools in Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
11-2 Troubleshooting Tools in Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
11-3 QLogic Adapter Device IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
A-1 Diagnostic Utility Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
B-1 Flash Utility Commands—Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
B-2 Flash Utility Commands—Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
viii NE0154601-00 C
Preface
Intended Audience
This guide is for system administrators and end-users of the QLogic 3000 and
3100 Series Intelligent Ethernet adapters.
Related Materials
Linux® man page % man nx_nic
nxudiag utility help (diagnostics)
nxudiag -h or nxudiag --help (Windows
% ./nxudiag -h or nxudiag --help (Linux
Check the QLogic Web site for updates.
Documentation Conventions
This guide uses the following documentation conventions:
®
)
®
)
NOTE: provides additional information.
Te x t in blue font indicates a hyperlink (jump) to a figure, table, or section in
this guide, and links to Web sites are shown in underlined blue
example:
Table 9-2 lists problems related to the installation.
See “Installation Checklist” on page 3-6.
For more information, visit www.qlogic.com
Te x t in bold font indicates user interface elements such as a menu items,
buttons, check boxes, or column headings. For example:
Click the Start button, point to Programs, point to Accessories, and
then click Command Prompt.
The Adapter Properties window opens with the General tab in front.
NE0154601-00 C ix
.
. For
Preface
Technical Support
Te x t in Courier font indicates a file name, directory path, command, or
screen text. For example:
nx3fwct.bin
C:\WINDOWS\system32\drivers
Te x t in Bold Courier font indicates a command to enter that performs a
specific task. For example:
rpm -iv nx_nic-[version].src.rpm
The italic text (version) indicates a variable.
A percent sign (%) is the cursor prompt when executing Linux commands.
The term <current release> refers to the current release of the software, For
example, release 4.0.305.
Key names and key strokes are indicated with UPPERCASE:
Press CTRL+P.
Press the UP ARROW key.
Te x t in italics indicates terms, emphasis, variables, or document titles. For
example:
For a complete listing of license agreements, refer to the QLogic
Software End User License Agreement.
What are shortcut keys?
/lib/modules/<kernel-version>/kernel/net/netxen
Technical Support
Customers should contact their authorized maintenance provider for technical
support of their QLogic products. QLogic-direct customers may contact QLogic
Technical Support; others will be redirected to their authorized maintenance
provider.
Visit the QLogic support Web site listed in Contact Information for the latest
firmware and software updates.
Availability
QLogic Technical Support for products under warranty is available during local
standard working hours excluding QLogic Observed Holidays.
x NE0154601-00 C
Training
QLogic offers training for technical professionals for all iSCSI, InfiniBand, Fibre
Channel, and Intelligent Ethernet products. From the main QLogic Web page at
www.qlogic.com
the Education & Training tab on the left. The QLogic Global Training Portal offers
online courses, certification exams, and scheduling of in-person training.
Technical Certification courses include installation, maintenance and
troubleshooting QLogic SAN products. Upon demonstrating knowledge using live
equipment, QLogic awards a certificate identifying the student as a Certified
Professional. The training professionals at QLogic may be reached by e-mail at
training@qlogic.com.
Contact Information
Please feel free to contact your QLogic approved reseller or QLogic Technical
Support at any phase of integration for assistance. QLogic Technical Support can
be reached by the following methods:
Preface
Technical Support
, click the Education and Resources tab at the top, then click
Web http://support.qlogic.com
Email support@qlogic.com
The QLogic knowledge database contains troubleshooting information for the
QLogic adapters. Access the data base from the QLogic Support Web page,
http://support.qlogic.com
specific troubleshooting information.
Knowledge Database
The QLogic knowledge database is an extensive collection of QLogic product
information that you can search for specific solutions. We are constantly adding to
the collection of information in our database to provide answers to your most
urgent questions. Access the database from the QLogic Support Center:
http://support.qlogic.com
. Use the Support Center search engine to look for
.
NE0154601-00 C xi
Preface
Technical Support
xii NE0154601-00 C
1 Overview
This guide describes the system requirements, installation, and setup required for
the QLogic 3000 and 3100 Series Intelligent Ethernet adapters listed in Tab l e 1 -1 .
Obtaining the Latest Software Release Information
To download the latest version of the drivers for this product, see the QLogic Web
site Downloads section:
http://driverdownloads.qlogic.com
QLogic 3000 and 3100 Series Intelligent Ethernet Adapters
The products in Tabl e 1 -1 are supported in this document.
Table 1-1. QLogic 3000 and 3100 Series Intelligent Ethernet Adapters
.
Product Product Definition
QLE3044-RJ Quad-port 1GbE Intelligent Ethernet Adapter Copper
QLE3142-CU Dual-port 10GbE Intelligent Ethernet Adapter Twinax
QLE3142-SR Dual-port 10GbE Intelligent Ethernet Adapter (short
range fiber)
QLE3142-LR Dual-port 10GbE Intelligent Ethernet Adapter (long
range fiber)
Table Notes
For OEM-branded QLogic 3000 and 3100 Series Intelligent Ethernet adapters, see the QLogic Web
site.
These products are collectively referred to as the QLogic adapter unless
otherwise noted.
The QLogic adapters are compatible with Windows, Linux, and other operating
systems (OSs). See the QLogic Web site Downloads section for more information.
NE0154601-00 C 1-1
Transfer
Medium
Optical
Optical
1–Overview
QLogic 3000 and 3100 Series Intelligent Ethernet Adapters
1-2 NE0154601-00 C
2 System Requirements
Before installing the QLogic adapter, make sure your system meets the
requirements listed in this section:
“Hardware Requirements” on page 2-1
“Supported QLogic Adapters” on page 2-2
Hardware Requirements
Cable Specifications
Make sure the cables you are using meet the specifications listed in Tables 2-1
and 2-2.
Table 2-1. Cable Specifications—Optical
Core
Product
QLE3142-SR 50 OM2 850 400 66
QLE3142-LR 9 N/A 1310 N/A 10,000
Diameter
(m)
62.5 OM1 160 26
10 N/A N/A 10,000
Optical
Mode
OM3 2,000 300
Wavelength
(nm)
Bandwidth
(MHz)
500 82
200 33
Distance
(m)
NE0154601-00 C 2-1
2–System Requirements
Supported QLogic Adapters
Table 2-2. Cable Specifications—Copper
Product Cable Type
QLE3044-RJ Cat5 LAN 100
QLE3142-CU Copper direct attach twinax LAN 10
SFP+ Optical Module Requirements
Use only the optical modules validated and shipped with the QLogic adapter.
Supported QLogic Adapters
Make sure you have one of the adapters listed in Tabl e 1 -1 .
Network
Type
Cable Length
(meters)
2-2 NE0154601-00 C
3 Quick Start
This section provides instructions for advanced users who are already familiar
with hardware and software installation procedures. See the appropriate section,
as applicable:
“QLogic Adapter Installation and Verification” on page 3-1
“Windows Server Driver Installation” on page 3-2
“Linux Driver Installation” on page 3-4
QLogic Adapter Installation and Verification
The following sections provide high-level instructions for installing the QLogic
adapter. For more detailed instructions, see “Hardware Installation” on page 4-1.
Pre-installation Checklist
Before installing the QLogic adapter:
1. Verify that the system meets the requirements specified in “System
Requirements” on page 2-1.
2. Power down the system.
QLogic Adapter Installation
To install the QLogic adapter:
®
1. Insert the QLogic adapter into an available PCI Express
2. Connect the appropriate cables to the QLogic adapter.
3. Power up the system.
For more information on the QLogic adapter installation, refer to “Hardware
Installation” on page 4-1.
NE0154601-00 C 3-1
slot.
3–Quick Start
Windows Server Driver Installation
Verify the QLogic Adapter Installation
To verify that the QLogic adapter has been installed correctly, perform the steps in
the appropriate section.
Linux
On Linux systems, execute the following command:
# lspci -vvv -d 4040:
Windows Server
®
On Windows Server systems, perform the following steps:
1. Do one of the following:
For Windows 2003, right-click My Computer, and then click Manage.
The Computer Management window opens.
For Windows Server 2008, right-click Computer, then click Manage.
The Server Manager window opens.
2. Do one of the following:
For Windows Server 2003, select Computer Management, select
System Tools, and then select Device Manager.
For Windows Server 2008, select Server Manager, select
Diagnostics, then select Device Manager.
3. Check under Other devices for an Unknown Device. The QLogic adapter
will be listed as an Unknown Device. It will have a yellow question mark next
to it prior to having the QLogic adapter driver installed.
4. Right-click the device and select Properties from the shortcut menu.
5. Click the Details tab. Look for VEN_4040 as part of the string. This text
indicates that the QLogic adapter is installed correctly.
Windows Server Driver Installation
Pre-installation Checklist
1. Download the driver package from the QLogic Web site,
http://driverdownloads.qlogic.com
2. Extract the driver package.
For more information, see the Driver Checklist in the section that corresponds to
your OS.
.
3-2 NE0154601-00 C
Windows Server 2003
To install the QLogic adapter driver:
1. From the Windows desktop, right-click My Computer. On the shortcut
menu, select Manage. The Computer Management window opens.
2. Select Computer Management, select System Tools, and then select
Device Manager.
3. Right-click the server’s host name and select Scan for hardware changes.
4. When prompted to connect to Windows Update, Click No, not at this time,
and then click Next.
5. Click Install from a list or specific location, then click Next.
6. Select Search for the best driver in these locations. Deselect the Search
removable media option. Select Include this location in the search.
7. Click Browse, and then provide the path to the directory where the driver is
located.
3–Quick Start
Windows Server Driver Installation
8. Locate the following files in the driver directory:
nx3fwct.bin
nx3fwmn.bin
nxnd5x86.sys (Windows 2003, 32 bit) or
nxnd5x64.sys (Windows 2003, 64 bit)
Click OK in the Browse for Folder window.
9. Click the Next button in the Hardware Update Wizard window.
For more details on the Windows Server 2003 driver installation, refer to
“Windows Server 2003 NIC Driver Installation” on page 5-2.
To configure the QLogic adapter:
1. Click the Start button, and then select Network Connections.
2. Verify that QLogic adapter icon says Connected.
3. Assign an IP address to the network interface.
Windows Server 2008 and 2008 R2
To install the QLogic adapter driver:
1. Open a Windows Explorer window.
2. Navigate to the Install_Packages directory from the release extracted
from the QLogic driver package.
3. Double-click the respective MSI package required for Windows Server 2008.
NE0154601-00 C 3-3
3–Quick Start
Linux Driver Installation
4. Follow the instructions on the screen to complete the installation.
For more details on the Windows Server 2008 driver installation, refer to
“Windows Server 2008 NIC Driver Installation” on page 6-2.
To configure the QLogic adapter:
1. Click the Start button, and then select Network Connections.
2. Verify that QLogic adapter icon says Connected.
3. Assign an IP address to the network interface.
Linux Driver Installation
Pre-installation Checklist
Download the driver package from the QLogic Web site,
http://driverdownloads.qlogic.com
See “Linux Driver Checklist” on page 8-1 for more information.
.
Verify and Remove Existing QLogic Adapter Driver and Tools Package
If you have a previous version of the QLogic adapter driver, perform the following
steps to remove the driver and tools package:
1. Type:
rpm -qa | grep nx_
2. Type:
ifconfig eth[n] down
3. Type:
rmmod nx_nic.ko
4. Type:
rpm -e nx_nic-[version]
5. Type:
rpm -e nx_tools-[version]
Install the Driver (RPM)
Red Hat
®
To install the driver on a Red Hat system:
1. Type the following command to extract the driver:
tar -zxvf qle30xx_qle31xx-src-[version].tar.gz
3-4 NE0154601-00 C
Linux Driver Installation
2. Type the following command to install the RPM source:
rpm -iv nx_nic-[version].src.rpm
3. Type the following command to build the binary RPM:
rpmbuild -bb /usr/src/redhat/SPECS/nx_nic-[version].spec
4. Type the following command to install the binary RPM:
rpm -ivh /usr/src/redhat/RPMS/[arch]/nx_nic-[version].[arch].rpm
The [arch] variable designates the system architecture. Some [arch]
variables are i386, i586, i686, x86_64, depending on the system.
5. Type the following command to install the tools RPM:
rpm -ivh nx_tools-[version].rpm
6. Type the following command to load the driver:
modprobe -v nx_nic
3–Quick Start
SUSE
®
To install the driver on a SUSE system:
1. Type the following command to extract the driver:
tar -zxvf qle30xx_qle31xx-src-[version].tar.gz
2. Type the following command to install the RPM source:
rpm -iv nx_nic-[version].src.rpm
3. Type the following command to build the binary RPM:
rpmbuild -bb /usr/src/packages/SPECS/nx_nic-[version].spec
4. Type the following command to install the binary RPM:
rpm -ivh /usr/src/packages/RPMS/[arch]2/nx_nic-[version].[arch].rpm
The [arch] variable designates the system architecture. Some [arch]
variables are i386, i586, i686, x86_64, depending on the system.
5. Type the following command to install the tools RPM:
rpm -ivh nx_tools-[version].rpm
6. Type the following commands to load the driver:
modprobe firmware_class
modprobe -v nx_nic
NE0154601-00 C 3-5
3–Quick Start
Linux Driver Installation
QLogic Adapter Configuration
To configure the QLogic adapter:
1. Type the following command to identify the Ethernet interface:
cat /proc/net/nx_nic/dev0/stats
2. Type the following command to assign an IP address:
ifconfig eth[n] [ip address]
3-6 NE0154601-00 C
4 Hardware Installation
RJ45
RJ45
RJ45
RJ45
Port 1
Port 2
Port 3
Port 4
This section provides installation instructions for the QLogic adapters. Please
follow all applicable ESD precautions when handling the QLogic adapter.
QLE3044 Installation
To install the QLE3044:
1. Verify that the system is powered off and unplug the power cord.
2. Remove the system cover.
3. Locate an empty x4 or higher PCIe
4. Insert the QLE3044 into the PCIe slot. Apply uniform pressure on top of the
QLE3044 until it is firmly seated in the PCIe bus connector.
5. Secure the bracket to the chassis and replace the cover.
6. Connect the appropriate cables to the QLE3044.
7. Plug in the power cord and power up the system.
®
slot.
The QLE3044 contains four ports that are organized as shown in Figure 4-1. Note
that the portion of the bracket covering the four RJ45 jacks is not shown.
Figure 4-1. QLE3044 Port Assignments
NE0154601-00 C 4-1
4–Hardware Installation
Port 1
Port 2
Port 3
Port 4
Top of board
Bi-color
Link LED
Green
Activity LED
PCIe connector
QLE3044 Installation
Ethernet Port Mapping
The mapping of port numbers on the QLE3044 is shown in Table 4-1.
Table 4-1. Mapping of Port Number, PCI Function, and Ethernet
Port Number PCI Function Ethernet Interface
1 0 Ethernet interface numbers are dynamically allo-
21
3 2
43
QLE3044 Status LEDs
The QLE3044 has two status LEDs per port. These LEDs are located on the port
itself, as shown in Figure 4-2. When viewing the QLE3044 from the front, the
bi-color green/orange link LED is on the left, and the green activity LED is on the
right.
Interface
cated by the host. As such, any eth[n] interface can
be connected to any port.
Figure 4-2. QLE3044 Status LEDs—Front View
The bi-color link LED indicates the speed of the connection as shown in Tab le 4- 2.
Table 4-2. QLE3044 LED Definitions
Green/Orange
Speed
Bi-Color Link
LED
10Mbps Off During power-up, the activity LED is on continu-
100Mbps Green On
1000Mbps Orange On
4-2 NE0154601-00 C
ously (solid). The LED blinks during normal operation when there is activity on the port for any of the
speed settings.
Green Activity LED
QLE3044 Bracket Removal and Replacement
1. Remove screw using
a Phillips screwdriver.
2. Slide the bracket upward
Bracket
until it clears the four RJ45
Ethernet jacks.
2. Fasten the screw using
a Phillips screwdriver.
1. Slide the bracket down
Bracket
over the four RJ45
Ethernet jacks.
RJ45
RJ45
RJ45
RJ45
Depending on the type of system, installation of the QLE3044 requires either a
long bracket or a short bracket. QLogic provides both of these brackets with the
product. The brackets for the QLE3044 are different from previous brackets in that
they slide over the top of the four RJ45 Ethernet jacks.
To remove and replace the bracket:
1. Remove the screw at the top of the QLE3044 that holds the bracket in place.
2. Slide the bracket upward towards the top of the QLE3044 until it clears all of
the Ethernet jacks. (The bracket covers the top of the RJ45 Ethernet jacks.)
3. To replace with a different bracket, reverse the process, sliding the new
bracket over the Ethernet jacks. Then fasten the bracket in place with the
screw.
The removal and replacement process is illustrated in Figure 4-3 and Figure 4-4,
respectively.
4–Hardware Installation
QLE3044 Installation
Figure 4-3. QLE3044 Bracket Removal
Figure 4-4. QLE3044 Bracket Replacement
NE0154601-00 C 4-3
4–Hardware Installation
QLE3142
SFP+ module slides into
housing on the board.
Ensure hinge is in upright position
when inserting module.
When the module is inserted
correctly, an audible ‘clicking’
SFP+ Optical
To remove the optical module, flip the hinge
downward. Pull on the hinge to remove
the module from the housing.
Housing
Housing
Module
SFP+ Optical
Module
sound will be heard.
Bracket
QLE3142 Installation
QLE3142 Installation
To install the QLE3142:
1. Verify that the system is powered down and unplug the power cord.
2. Remove the system cover.
3. Locate an empty PCIe x8 slot.
4. Remove the SFP+ optical modules from the QLE3142 if they are already
inserted (see Figure 4-5).
4-4 NE0154601-00 C
Figure 4-5. QLE3142 Installation and Removal
5. Insert the QLE3142 into the PCIe x8 slot. Apply uniform pressure on top of
the QLE3142 until it is firmly seated in the bus connector.
6. Connect the SFP+ module or copper direct-attach twinax cable. Listen for an
audible clicking sound when the optical module is inserted into the housing
(see Figure 4-5).
7. Secure the bracket to the chassis and replace the cover.
8. Connect the appropriate cables to the QLE3142.
9. Plug in the power cord and power up the system.
NOTE:
Port 1Port 2
Link
Link
Activity
Activity
Mounting bracket
Top of card
PCIe connector end
QLE3142
Housing
Housing
Mounting Bracket
1.Remove the two mounting screws.
2.Gently pull the bracket away from the board until it
clears the optical module housings.
The optical module must be seated correctly in the housing to ensure proper
operation.
QLE3142 Status LEDs
The QLE3142 has two status LEDs per port, one for link status and one for
activity. These LEDs are located next to the ports as shown in Figure 4-6. Both
SFP+ ports operate at 10Gbps.
4–Hardware Installation
QLE3142 Installation
Figure 4-6. QLE3142 Status LEDs—Side View
QLE3142 Bracket Removal and Replacement
Depending on the type of system, installation of the QLE3142 requires either a
long bracket or a short bracket. QLogic provides both of these brackets with the
product.
To remove and replace the bracket:
1. Remove the SFP+ optical modules from their housing (see Figure 4-7).
Figure 4-7. QLE3142 Bracket Removal
NE0154601-00 C 4-5
4–Hardware Installation
QLE3142
Housing
Housing
2. Fasten the two mounting screws.
1. Attach the new bracket. The two optical module
cutouts on the bracket slide over the housings on
the QLE3142. The mounting screw tabs on the bracket
should line up with the mounting screw holes
on the QLE3142. Note that the tabs will be on the
solder side of the board.
QLE3142 Installation
2. Remove the two screws at the top and bottom of the QLE3142 that hold the
3. Gently pull the bracket away from the QLE3142 until it disconnects from the
4. To replace with a different bracket, reverse the process, sliding the new
bracket in place.
optical module housings.
bracket over the module housings (see Figure 4-8). Note that the screw
mounting tabs on the bracket go on the solder side of the QLE3142. Fasten
the bracket in place with the two screws.
Figure 4-8. QLE3142 Bracket Replacement
4-6 NE0154601-00 C
5 Windows Server 2003
Driver Installation
This section describes the installation and configuration procedure for the QLogic
adapter NIC driver on a Windows Server 2003 operating system (OS).
For Windows Server 2008 driver installation instructions, see Section 6.
For Linux driver installation instructions, see Section 8.
Driver Checklist
Before installing the QLogic adapter NIC driver on a Windows Server 2003 OS:
1. Download the driver package from the QLogic Web site,
http://driverdownloads.qlogic.com
2. Make sure your system complies with the system requirements (see
“System Requirements” on page 2-1).
3. For existing installations:
a. Uninstall the old NIC driver and utilities (see “Uninstall the NIC Driver”
on page 5-6).
b. Install the new NIC driver (see “Windows Server NIC Driver Installation
and Verification” on page 5-2).
c. Update the Flash (contact Technical Support to see if this step is
required).
Firmware ROM Image Location
The firmware ROM image files (nx3fwct.bin and nx3fwmn.bin) are in the
C:\WINDOWS\system32\drivers directory.
A user interface and a command line interface (CLI) are provided for
communicating with the Flash utility.
NE0154601-00 C 5-1
5–Windows Server 2003 Driver Installation
Windows Server NIC Driver Installation and Verification
Windows Server NIC Driver Installation and Verification
The following subsections describe the installation and verification procedures for
Windows Server 2003.
Windows Server 2003 NIC Driver Installation
The following procedure is for a new NIC driver installation.
1. Extract the QLogic adapter NIC driver release package to a directory on the
host.
After the server system is powered up, Windows detects the QLogic adapter,
and the Found New Hardware Wizard dialog box opens (Figure 5-1).
Figure 5-1. Windows Server 2003—Found New Hardware Wizard Dialog Box
5-2 NE0154601-00 C
5–Windows Server 2003 Driver Installation
Windows Server NIC Driver Installation and Verification
2. Click No, not at this time, and then click Next. The wizard opens another
dialog box prompting for NIC driver location information (Figure 5-2).
Figure 5-2. Windows Server 2003—NIC Driver Location Information
3. Click Install from a list or specific location (Advanced), and then click
Next.
A dialog box opens, prompting for more information about the NIC driver
location (Figure 5-3).
Figure 5-3. Windows Server 2003—Select NIC Driver Location
4. Click Search for the best driver in these locations, and then select the
Include this location in the search check box.
5. Do one of the following:
Type the appropriate path to the QLogic adapter NIC driver directory in
the accompanying field, and then click Next.
NE0154601-00 C 5-3
5–Windows Server 2003 Driver Installation
Windows Server NIC Driver Installation and Verification
If the exact directory path is not known, click Browse. The Browse for
Folder dialog box opens (Figure 5-4).
Figure 5-4. Windows Server 2003—Browse for Folder
a. Select the QLogic adapter NIC driver directory.
b. Select the appropriate directory (x86 or x64), and then click OK.
The QLogic adapter supports both 32-bit and 64-bit OSs. The x86
directory contains the 32-bit NIC driver. The x64 directory contains the
64-bit NIC driver.
6. Click Next in the Hardware Update Wizard dialog box to install the NIC
driver.
The ‘Please wait while the wizard installs the software’ dialog box appears
while the NIC driver is being installed (Figure 5-5).
Figure 5-5. Windows Server 2003—Software Installation Progress
5-4 NE0154601-00 C
5–Windows Server 2003 Driver Installation
Windows Server NIC Driver Installation and Verification
When the installation completes, the Completing the Hardware Update
Wizard dialog box opens (Figure 5-6).
Figure 5-6. Windows Server 2003—Software Installation Complete
7. Click Finish.
Windows Server 2003 NIC Driver Installation Verification
To verify that the NIC driver was properly installed:
1. Click the Start button, right-click My Computer, and then select Device
Manager. A list of devices appears in right side of the window.
2. Verify that the QLogic adapter is listed under Network Adapters, as shown in
Figure 5-7.
Figure 5-7. NIC Driver Installation Verification
NE0154601-00 C 5-5
5–Windows Server 2003 Driver Installation
Uninstall the NIC Driver
Uninstall the NIC Driver
To uninstall the QLogic adapter NIC driver in Windows Server 2003:
1. Right-click My Computer, and then click Manage.
2. Double-click Device Manager.
Under Network Adapters, a list of devices in the computer is displayed.
3. Locate and right-click the QLogic adapter.
4. Click Uninstall.
The Confirm Device Removal dialog box opens.
5. Click OK.
6. Delete the following files from the corresponding directory:
File Directory
nxcoinst.dll C:\WINDOWS\system32
nx3fwct.bin C:\WINDOWS\system32\drivers
nx3fwmn.bin C:\WINDOWS\system32\drivers
nxnd5x64.sys C:\WINDOWS\system32\drivers
5-6 NE0154601-00 C
6 Windows Server 2008 and
2008 R2 Driver Installation
This section describes the installation and configuration procedure for the QLogic
adapter NIC driver and Teaming driver on Windows Server 2008 and 2008 R2
operating systems (OSs).
For Windows Server 2003 NIC driver installation instructions, see Section 5.
For Linux NIC driver installation instructions, see Section 8.
Driver Checklist
Before installing the QLogic adapter NIC or Teaming driver on a Windows
Server 2008 OS:
1. Download the driver package from the QLogic Web site,
http://driverdownloads.qlogic.com
2. Make sure your system complies with the system requirements (see
“System Requirements” on page 2-1).
3. Uninstall any previous version of the driver (see “Windows Server 2008 NIC
Driver Uninstall (Previous Version)” on page 6-12 or “Windows Server 2008
NIC and Teaming Driver Uninstall” on page 6-13).
Firmware ROM Image Location
The firmware ROM image files (nx3fwct.bin and nx3fwmn.bin) are in the
C:\WINDOWS\system32\drivers directory.
A user interface and a command line interface (CLI) are provided for
communicating with the Flash utility.
NE0154601-00 C 6-1
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 NIC Driver Installation and Verification
Windows Server 2008 NIC Driver Installation and Verification
Windows Server 2008 NIC Driver Installation
To install the NIC driver:
1. Navigate to the Install_Packages directory in the new NIC driver
package.
2. Extract the driver by running the appropriate self-extracting executable:
q3w32n6[version].exe
q3wx64n6[version].exe
q3ws8R2x64n6[version].exe
3. Double-click one of the following MSI packages, as appropriate:
Qancs_win2k8_x64.msi
Qancs_win2k8_x86.msi
Qancs_win2k8_R2_x64.msi
The Setup Wizard dialog box opens (see Figure 6-1).
Figure 6-1. Windows Server 2008—Setup Wizard
4. Click Next.
6-2 NE0154601-00 C
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 NIC Driver Installation and Verification
The License Agreement dialog box opens (see Figure 6-2).
Figure 6-2. Windows Server 2008—License Agreement
5. Read the License Agreement. Click I Agree, and then click Next.
The QLogic Advanced Network Config Service dialog box opens
(see Figure 6-3).
Figure 6-3. Windows Server 2008 — Installation Options
6. Do one of the following, and then click Next:
Click Typical Installation to install only the base NIC driver. Teaming
support will not be enabled.
Click Complete Installation if Teaming support is required.
NE0154601-00 C 6-3
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 NIC Driver Installation and Verification
The Select Installation Folder dialog box opens (see Figure 6-4).
Figure 6-4. Windows Server 2008—Select Installation Folder
7. Change the installation folder (if required), and then click Next.
The Confirm Installation dialog box opens (see Figure 6-5).
Figure 6-5. Windows Server 2008—Confirm Installation
8. Click Next to begin the installation.
6-4 NE0154601-00 C
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 NIC Driver Installation and Verification
At the end of the installation process, the Installation Complete dialog box
opens (Figure 6-6).
Figure 6-6. Windows Server 2008—Installation Complete
9. Click Close to complete the installation.
Windows Server 2008 NIC Driver Installation Verification
To verify that the NIC driver was properly installed:
1. Click the Start button, right-click My Computer, and then select Device
Manager. A list of devices appears in right side of the window.
2. Verify that the QLogic adapter is listed under Network Adapters, as shown in
Figure 6-7.
Figure 6-7. NIC Driver Installation Verification
NE0154601-00 C 6-5
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 and 2008 R2 Teaming Driver Installation and Configuration
Windows Server 2008 and 2008 R2 Teaming Driver Installation and Configuration
The following subsections describe how to install and configure the Windows
Server 2008 intermediate (Teaming) driver.
Windows Server 2008 and 2008 R2 Teaming Driver Installation
During the Windows Server 2008 NIC driver installation process, you can load
both the NIC and Teaming drivers, or only the NIC driver, as shown in Figure 6-8.
Figure 6-8. Windows Server 2008—Installation Options
If the Complete Installation option (default) shown in Figure 6-8 was selected
during the Windows Server 2008 NIC driver installation process, then the Teaming
driver has already been installed on the system.
6-6 NE0154601-00 C
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 and 2008 R2 Teaming Driver Installation and Configuration
If the base NIC driver was installed the first time the driver package was installed
(see the Typical Installation option in Figure 6-3), then you need to re-install the
driver to include Teaming:
1. Repeat Steps 1 through 5 from “Windows Server 2008 NIC Driver
Installation and Verification” on page 6-2.
The QLogic Advanced Network Config Service dialog box displays
(Figure 6-9).
Figure 6-9. Windows Server 2008—Advanced Network Config Service Setup
Wizard
2. Click Repair QLogic Advanced Network Config Service.
3. Click Finish.
NE0154601-00 C 6-7
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 and 2008 R2 Teaming Driver Installation and Configuration
Windows Server 2008 and 2008 R2 Teaming Driver Configuration
After the Teaming driver is installed, the Local Area Connection Properties dialog
box includes the QLogic Advanced Network Configuration Service option, as
shown in Figure 6-10.
Figure 6-10. Windows Server 2008 Teaming—Select Network Configuration
Service
6-8 NE0154601-00 C
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 and 2008 R2 Teaming Driver Installation and Configuration
Follow these steps to configure Teaming for the QLogic adapter:
1. Click the Start button, point to Programs, point to QLOGIC Corporation,
and then select NxTeamingUI.
The QLogic Advanced Networking Config Service Window opens (see
Figure 6-11).
Figure 6-11. Windows Server 2008 Teaming—Network Configuration Service
Window
NE0154601-00 C 6-9
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 and 2008 R2 Teaming Driver Installation and Configuration
2. Right-click Teams, and then click Create Team (Figure 6-12).
Figure 6-12. Windows Server 2008 Teaming—Creating a Team
NOTE:
For more help, see the information in the Status box.
6-10 NE0154601-00 C
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 and 2008 R2 Teaming Driver Installation and Configuration
After selecting Create Team, the Create Team dialog box opens
(Figure 6-12).
Figure 6-13. Windows Server 2008 Teaming—Create Team Window
NOTE:
For more help, see the information in the Message box.
3. Select the check boxes for the QLogic adapter ports to be Teamed, and then
click OK (Figure 6-13).
A progress bar appears as the Team is being created (Figure 6-14).
Figure 6-14. Windows Server 2008 Teaming—Create Team Progress Bar
NE0154601-00 C 6-11
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 NIC Driver Uninstall (Previous Version)
4. Verify the Team creation. When the Team creation is complete, the Teaming
Management tab in the QLogic Advanced Network Configuration Service
dialog box shows the formed Team (Figure 6-15).
Figure 6-15. Windows Server 2008 Teaming—Team Management Window
NOTE:
For more help, see the information in the How-to box.
Windows Server 2008 NIC Driver Uninstall (Previous Version)
If your system already has a NIC driver installed, and the version number is earlier
than 4.0.517, you must remove this driver before installing the latest NIC driver.
To uninstall the old driver:
1. Right-click Computer, and then click Manage.
2. Select Server Manager, select Diagnostics, and then select Device
Manager.
6-12 NE0154601-00 C
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 NIC and Teaming Driver Uninstall
Under Network adapters, locate the QLogic adapters.
3. Right-click the adapters to be uninstalled, and then select the Uninstall
option for each device to be uninstalled.
4. If prompted, select Delete the driver software from this device.
5. In the Confirm Device Uninstall dialog box, click OK.
6. Delete one of the following file sets from the corresponding directories:
File Directory
nxcoinst.dll C:\WINDOWS\system32
nx3fwct.bin C:\WINDOWS\system32\drivers
nx3fwmn.bin C:\WINDOWS\system32\drivers
nxnd6x64.sys C:\WINDOWS\system32\drivers
File Directory
nxnd6x86.sys C:\WINDOWS\system32\drivers
Windows Server 2008 NIC and Teaming Driver Uninstall
To uninstall the Windows Server 2008 Teaming driver:
1. Click the Start button, select Programs, select QLogic Corporation, and
then click Uninstall QANCS (see Figure 6-16).
Figure 6-16. Windows Server 2008 Teaming Uninstall Procedure
NE0154601-00 C 6-13
6–Windows Server 2008 and 2008 R2 Driver Installation
Windows Server 2008 NIC and Teaming Driver Uninstall
6-14 NE0154601-00 C
7 Windows Server 2003,
2008, and 2008 R2 Driver
Configuration
This section describes how to program your QLogic adapter and maximize its
performance in the Windows Server 2003, 2008, and 2008 R2 OSs. Topics
include:
“NIC Driver Properties and Configuration” on page 7-1
“QLogic Adapter Configuration” on page 7-9
“QLogic Adapter Diagnostic Tests” on page 7-11
“Windows Server 2003 Performance” on page 7-13
NIC Driver Properties and Configuration
The QLogic adapter NIC driver can be configured through the adapter properties
in Device Manager.
To access the Device Manager:
1. Click the Start button, right-click My Computer, and then click Device
Manager. A list of devices appears in the right side of the window.
2. Under Network Adapters, right-click the QLogic adapter, and then select
Properties.
The advanced properties window opens.
NE0154601-00 C 7-1
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Windows Server 2008
NIC Driver Properties and Configuration
The advanced properties window has the following tabs:
The General tab is in front (Figure 7-1).
Figure 7-1. Adapter Properties—General Tab
7-2 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
NIC Driver Properties and Configuration
The Advanced tab displays the driver properties.
Table 7-1 describes the Advanced tab selections.
Table 7-1. Advanced Properties Parameters
Parameter Description
Completion Queue Size This parameter indicates the size of the completion
queue.
Registry Key: CompletionQueueSize
Default: 4 (16,384 entries).
Values (entries): 0 (1024), 1 (2048), 2 (4096),
3 (8192), 4 (16,384), 5 (32,768)
Flow Control This parameter sets flow control parameters. There
are four flow control options: 0 (off), 1 (transmit),
2 (receive), and 3 (transmit/receive).
Registry Key: FlowControl
Default: 3 (Transmit and receive flow control
enabled.)
Values: 0, 1, 2, 3
Health Monitoring This parameter maintains the health of the device.
Disabling this parameter should performed under
advisement from QLogic.
Registry Key: Watchdog
Default: Health monitoring enabled.
Values: Enabled/Disabled
Interrupt Moderation This parameter provides interrupt moderation. When
this parameter is enabled, interrupts are moderated
automatically based on traffic patterns.
Registry Key: InterruptModeration
Default: Disabled
Values: Enabled/Disabled
IPv4 Checksum Offload This parameter enables/disables the IPv4 checksum
offload. There are four flow checksum options: 0 (off),
1 (transmit), 2 (receive), and 3 (transmit/receive).
Registry Key: IPChecksumOffloadv4
Default: 3 (Transmit and receive checksum
enabled)
Values: 0, 1, 2, 3
NE0154601-00 C 7-3
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
NIC Driver Properties and Configuration
Table 7-1. Advanced Properties Parameters (Continued)
Parameter Description
Large Receive Offload (LRO) This parameter specifies the large receive
offload—enable/disable options.
Registry Key: LRO
Default: Enabled
Values: Enabled/Disabled
Large Send Offload V1 IPv4 This parameter specifies the large send
offload—enable/disable options.
Registry Key: LsoV1IPv4
Default: Enabled
Values: Enabled/Disabled
Size of LSO: 64K maximum
Large Send Offload V2 IPv4
Large Send Offload V2 IPv6
a
This parameter specifies the large send
offload—enable/disable options.
Registry Key: LsoV2IPv4
Default: Enabled
Values: Enabled/Disabled
Size of LSO: 64K maximum
a
This parameter specifies the large send
offload—enable/disable options.
Registry Key: LsoV2IPv6
Default: Enabled
Values: Enabled/Disabled
Size of LSO: 64K maximum
Locally Administered Address This is the locally administered address (LAA) that
users/administrators can set on this interface to override the permanent address of the QLogic adapter
(that may have been Flashed into the hardware).
Registry Key: NetworkAddress
Format: Hex
Options: Value. (A value is required—enter the
12 hex bytes of the MAC address to be used, or
not present.)
7-4 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
NIC Driver Properties and Configuration
Table 7-1. Advanced Properties Parameters (Continued)
Parameter Description
Max Ethernet Frame Size This parameter specifies the Ethernet frame size for
packet transmission and receive (it does not include
the MAC header).
Reg Key: MaxFrameSize
Default: 1500 (corresponds to 1514 bytes on the
wire plus 4 bytes of CRC)
Max: 9600
Min: 64
Step: 1
Max Jumbo Buffers This parameter specifies the maximum number of
receive buffers per Jumbo frame.
Reg Key: RxJumboRingSize
Default: 2 (4096 buffers)
Values: 0 (1024), 1 (2048), 2 (4096), 3 (8192)
Max Offload Connections This parameter specifies the maximum number of
offload connections.
Reg Key: MaxOffloadConnections
Default: 512
Max: 512
Min: 0
Step: 1
NOTE: This feature is not supported at the time of
publication.
Number of Receive Buffers This parameter specifies the packet buffers used by
the driver for receive operations (DMA memory and
indicated to stack). Each buffer is 1536 bytes.
Registry Key: ReceiveBuffers
Default: 4 (16,384 entries)
Values (entries): 0 (1024), 1 (2048), 2 (4096),
3 (8192), 4 (16,384), 5 (32,768)
NE0154601-00 C 7-5
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
NIC Driver Properties and Configuration
Table 7-1. Advanced Properties Parameters (Continued)
Parameter Description
Number of Transmit Buffers This parameter specifies the packet buffers used by
the driver for transmit operations (DMA memory and
indicated to stack). Each buffer is 1536 bytes.
Registry Key: TransmitBuffers
Min: 1K
Max: 2K
Default: 1024
Values: 0 (1024), 1 (2048)
Optimization This parameter controls optimization and IP forward-
ing. Enable this function when the QLogic adapter is
used for IP forwarding.
Registry Key: Optimization
Default: Disabled
Values: Disabled/Enabled
Priority and VLAN Tag This parameter controls support for 802.1p/q priority
tagging. Enable this parameter to set the virtual LAN
(VLAN) ID. There are four options (values).
0: Both 802.1p/q priority tagging and VLAN tagging
disabled.
1: Priority tagging enabled, VLAN tagging disabled.
2: VLAN tagging enabled, priority tagging disabled.
3: Both 802.1p/q priority tagging and VLAN tagging
enabled.
Registry Key: PriorityVLANTag
Default: 3
Values: 0, 1, 2, 3
Receive Side Scaling This parameter enables/disables the receive side
scaling (RSS) feature.
Registry Key: RSS
Default: Enabled
Values: Enabled/Disabled
7-6 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
NIC Driver Properties and Configuration
Table 7-1. Advanced Properties Parameters (Continued)
Parameter Description
Receive Side Scaling Rings This parameter controls the number of rings used.
n
The total is calculated by 1KB 2
with a value of 5 for
a maximum of 32KB.
Registry Key: MaxStatusRings
Default: 2
Max: 4
Min: 1
Step: 1
TCP Checksum Offload IPv4 This parameter enables/disables the TCP checksum
offload for IPv4. There are four TCP checksum
options (values):
0: Off
1: Transmit
2: Receive
3: Transmit/receive
Registry Key: TCPChecksumOffloadv4
Default: 3 (Transmit and receive checksum
enabled)
Values: 0, 1, 2, 3
TCP Checksum Offload IPv6 aThis parameter enables/disables the TCP checksum
offload for IPv6. There are four TCP checksum
options (values):
0: Off
1: Transmit
2: Receive
3: Transmit/receive
Registry Key: TCPChecksumOffloadv6
Default: 3 (Transmit and receive checksum
enabled)
Values: 0, 1, 2, 3
NE0154601-00 C 7-7
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
NIC Driver Properties and Configuration
Table 7-1. Advanced Properties Parameters (Continued)
Parameter Description
UDP Checksum Offload IPv4 This parameter enables/disables the UDP checksum
offload. There are four UDP checksum options (values):
0: Off
1: Transmit
2: Receive
3: Transmit/receive
Registry Key: UDPChecksumOffloadv4
Default: 3 (Transmit and receive checksum
enabled)
Values: 0, 1, 2, 3
UDP Checksum Offload IPv6 aThis parameter enables/disables the UDP checksum
offload. There are four UDP checksum options (values):
0: Off
1: Transmit
2: Receive
3: Transmit/receive
Registry Key: UDPChecksumOffloadv6
Default: 3 (Transmit and receive checksum
enabled)
Values: 0, 1, 2, 3
VLAN ID This parameter sets the VLAN ID for this interface
(also exposed through the standard OID).
Registry Key: VlanId
Default: 0 (no VLAN)
Max: 4094
Min: 0
Step: 1
Range: 0–4094
a
Windows Server 2008 only
7-8 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
The Information tab contains information about the firmware version, BIOS
version, driver version, and other QLogic adapter properties.
The Diagnostics tab tests the QLogic adapter’s Flash, LED, and other
functions.
The Statistics tab displays information about the QLogic adapter.
The Flash update tab displays the current firmware version on the QLogic
adapter. You can update the firmware (if required).
The Driver tab displays driver information. From this tab, you can update,
uninstall, or restore a previous version of the QLogic adapter driver.
The Details tab displays detailed information about the QLogic adapter.
The Resources tab displays the resource settings for the QLogic adapter.
QLogic Adapter Configuration
To enable the connections to the QLogic adapter:
QLogic Adapter Configuration
1. Open the Network Connections window in the Control Panel, or directly from
the desktop if the icon exists (Figure 7-2).
Figure 7-2. Network Connections Window
If an IP address has not been assigned, the QLogic adapter entry says
Limited or no connectivity.
NE0154601-00 C 7-9
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
QLogic Adapter Configuration
If there is a red X next to QLogic adapter icon, the link is down. In this case,
do the following:
a. Verify that the card is seated properly in the PCI slot.
b. Make sure that the network cable is connected properly at both ends.
c. Make sure that the cable is good.
d. Assign an IP address to the interface if you have not already.
e. Verify that the SFP+ module is installed correctly (QLE3142).
See Section 11 for more information.
2. To check the status of the connection, right-click the adapter icon in the
Network Connections window, and then select Properties.
The Local Area Connection Properties dialog box opens (Figure 7-3).
Figure 7-3. Local Area Connection Properties Dialog Box
3. Assign an IP address manually by selecting the Internet Protocol (TCP/IP)
entry, and then clicking the Properties button.
7-10 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
QLogic Adapter Diagnostic Tests
The Internet Protocol (TCP/IP) Properties dialog box opens (Figure 7-4).
Figure 7-4. Internet Protocol (TCP/IP) Properties Dialog Box
4. Assign the appropriate IP, subnet mask, and default gateway values in the
Internet Protocol (TCP/IP) Properties dialog box, and then click OK.
5. Verify connectivity with another card or switch using the ping utility.
QLogic Adapter Diagnostic Tests
The Windows user diagnostics utility performs different tests using the
nxudiag.exe command. The syntax for these tests is:
nxudiag.exe [command-options-and-arguments]
See Table A-1 for a list of Windows diagnostic command options and arguments.
The QLogic adapter will be offline at this time.
NE0154601-00 C 7-11
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Windows Server 2008
QLogic Adapter Diagnostic Tests
Alternately, there is a Diagnostics tab in the QLogic adapter property sheet that
can perform the same tests (Figure 7-5).
Figure 7-5. Adapter Properties—Diagnostics Tab
7-12 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
Windows Server 2003 Performance
This section describes Windows performance tuning.
NOTE:
The tunable performance parameters are system and application specific.
Understanding the relationship between the parameter values, target
workload, performance applications, operating system, and system
configuration provides a better understanding of performance optimization
and bottlenecks.
Performance Testing the QLogic Adapter with ntttcp
To enhance Windows Server performance, change these parameters in the order
listed.
1. Enable Windows Server scaling (for Windows Server 2003).
Set the TCp1323Opts parameter value to 1. Note that this parameter is not
created by default. For more information about modifying a previously
created parameter, or creating a new parameter, see “Tcp1323Opts
Parameter” on page 7-16.
2. Set the TcpWindowSize parameter (for Windows Server 2003).
In the TcpWindowSize parameter window, set the value in the Value Data
box to either 200000 hexadecimal, or 2,097,152 decimal. Be sure to click
either hexadecimal or decimal in the Base box depending on the value
entered.
If the TcpWindowSize parameter does not exist, it can be created using
regedit. See “Setting the TcpWindowSize Parameter” on page 7-20 for
more information.
NE0154601-00 C 7-13
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
3. Run ntttcp.
a. Click the Start button, and then click Run. The Run dialog box opens.
b. Type cmd in the Open: box, and then click OK (Figure 7-6).
Figure 7-6. Run Dialog Box
c. Change the directory path to the location where ntttcp was
downloaded or copied. An example directory tree is shown in
Figure 7-7.
Figure 7-7. Location of ntttcp
For scripts, see the tools package included with the release.
ntttcp Overview
There are two switches on ntttcp that boost performance: -a and -rb.
ntttcp can be run without an optimal value for the -a switch and without the
-rb switch for the QLE3044.
When running ntttcp with the QLE3142, and in particular with fewer threads on
Windows Server, performance is limited by the receive window and by the
outstanding I/O (-a) value, regardless of hardware limitations.
7-14 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
For the receive side, the optimal value is 16 for -a and 512,000 for -rb (or
something similar). With these values, a single thread should perform closer to a
multi-thread configuration. From a DOS command prompt, type the following
command. Note that the command must be executed from the same directory in
which the executable files are located.
ntttcpr -m 16,0,<rcv ipaddr> -n <# of tcp segs for snd/rcv> -a 16
For the transmit side, -a should be a value less than eight. The more threads, the
lower the value.
NOTE:
The send (transmit) and receive side ntttcp commands must use the
receive side’s IP address.
ntttcps and ntttcpr Command Line Options
The ntttcps and ntttcpr command line options are listed in Table 7-2.
Table 7-2. ntttcps and ntttcpr Command Line Options
Command Default Notes
-l <length of buffer>
-n <number of buffers>
-p <port base>
-a <outstanding I/O>
-x <packet array size>
-rb <receive buffer size>
-sb <send buffer size>
-i
-f <file name>
-u
-w
-d
-t <runtime>
64K —
20K —
5001 —
2—
1 —
64K —
0 —
— Infinite loop
output.txt —
— UDP send/receive
— —
— Verify flag
— Runtime is in seconds.
-v
-6
NE0154601-00 C 7-15
— Enable verbose mode.
— Enable IPv6 mode.
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
Table 7-2. ntttcps and ntttcpr Command Line Options (Continued)
Command Default Notes
-fr
-mb
-m <mapping>
Tcp1323Opts Parameter
NOTE:
This parameter is only for Windows Server 2003.
This parameter determines whether TCP uses the time-stamping and window
scaling features described in RFC 1323, TCP Extensions for High Performance.
For more efficient use of high bandwidth networks, use a larger TCP window size.
The TCP window size field controls the flow of data and is limited to 2 bytes, or a
window size of 65,535 bytes.
— Full buffers posted on read opera-
tions.
— Multiple buffer post mode
— mapping is a session or sessions,
processor, receiver, and IP set. The
following example sets up four sessions on processor 0 to test a network on 1.2.3.4:
-m 4,0,1.2.3.4
Since the size field cannot be expanded, a scaling factor is used. The TCP
window option increases the maximum window size from 65,535 bytes to
1 gigabyte. The TCP receive window is the amount of data the sending host can
send on a connection at one time.
When the value for window size is added to the registry and its size is larger than
the default value, Windows attempts to use a scale value that accommodates the
new window size.
Tables 7-3 and 7-4 show the four Tcp1323Opts settings.
Table 7-3. Tcp1323Opts
Data Type
REG_DWORD 0 | 1 | 2 | 3 1
a
See Table 7-4
7-16 NE0154601-00 C
Range
a
Value
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Hex Value Meaning
0 Timestamps and window scaling are disabled.
1 Window scaling is enabled.
2 Timestamps are enabled.
3 Timestamps and window scaling are enabled.
To modify the scale factor, set Tcp1323Opts to 1. Note that this parameter is not
created by default. To modify a previously created parameter, see “Modifying the
Tcp1323Opts Parameter” on page 7-17. To create a new parameter, see
“Creating the Tcp1323Opts Parameter” on page 7-18.
Modifying the Tcp1323Opts Parameter
If the parameter was created previously, it can be modified as follows:
Windows Server 2003 Performance
Table 7-4. Range
1. Click the Start button, and then click Run. The Run dialog box opens.
2. Type regedit in Open: box (Figure 7-8), and then click OK.
Figure 7-8. Run Window
The Registry Editor window opens.
3. Click the HKEY_LOCAL_MACHINE directory (Figure 7-9).
Figure 7-9. Registry Editor—HKEY_LOCAL_MACHINE Directory
NE0154601-00 C 7-17
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
4. Navigate to the following directory path from the HKEY_LOCAL_MACHINE
directory:
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
Tc pip
Parameters
5. Locate the TCp1323Opts entry and change the value to 1.
Creating the Tcp1323Opts Parameter
If the TCp1323Opts parameter does not exist, it can be created as follows:
1. Click the Start button, and then click Run. The Run dialog box opens.
2. Type regedit in the Open: box, and then click OK (Figure 7-8).
The Registry Editor window opens.
3. Click the HKEY_LOCAL_MACHINE directory (Figure 7-9).
4. Navigate to the following directory path from the HKEY_LOCAL_MACHINE
directory:
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
Tc pip
Parameters
7-18 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
The Registry Editor window displays the parameters on the right side
(Figure 7-10).
Figure 7-10. Registry Editor—Parameter Directory
5. Right-click anywhere in the right side of the window and create a new key
with a DWORD value (Figure 7-11).
Figure 7-11. New Key—DWORD
6. Rename New Value #1 to TCp1323Opts (Figure 7-12).
Figure 7-12. Creating Tcp1323Opts
NE0154601-00 C 7-19
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
7. Right-click TCp1323Opts, and then click Modify. In the Value data box,
type 1 (the default value is 0), and then click OK. (Figure 7-13).
Figure 7-13. Edit DWORD Value Window—Tcp1323Opts Parameter
Setting the TcpWindowSize Parameter
NOTE:
This parameter is only for Windows Server 2003.
To set the TcpWindowSize parameter:
1. Click the Start button, and then click Run. The Run dialog box opens.
2. Type regedit in the Open: box, and then click OK (Figure 7-8).
3. Click the HKEY_LOCAL_MACHINE directory (Figure 7-9).
4. Navigate to the following directory path from the HKEY_LOCAL_MACHINE
directory:
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
Tc pip
Parameters
The Registry Editor window displays the parameters on the right side
(Figure 7-10).
5. Right-click anywhere in the right side of the window and create a new key
with a DWORD value (Figure 7-11).
6. Rename New Value #1 to TCpWindowSize.
7-20 NE0154601-00 C
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
7. Right-click TcpWindowSize, and then click Modify (Figure 7-14).
Figure 7-14. Modifying the TcpWindowSize Parameter
The Edit DWORD Value dialog box opens.
8. Type a the value in the Value data: box: either 200000 hexadecimal or
2,097,152 decimal. Be sure to select either the Hexadecimal or Decimal
button in the Base section depending on the value entered (Figure 7-15).
Figure 7-15. Edit DWORD Value Window — TcpWindowSize Parameter
For more information on setting the TCP window size, see “Tcp1323Opts
Parameter” on page 7-16.
NE0154601-00 C 7-21
7–Windows Server 2003, 2008, and 2008 R2 Driver Configuration
Windows Server 2003 Performance
7-22 NE0154601-00 C
8 Linux Driver Installation
and Configuration
This section describes the Linux driver installation and configuration procedure.
For the Windows Server 2003 driver installation procedure, see Section 5.
For the Windows Server 2008 driver installation procedure, see Section 6.
Linux Driver Checklist
Before installing and configuring the Linux driver, follow the instructions in these
sections:
“Locate the Firmware ROM Image” on page 8-1
“Locate the Driver File” on page 8-2
“Verify the Firmware Version” on page 8-2
“Verify the Driver Version and Module Information” on page 8-2
“Locate the QLogic Tools” on page 8-2
“Build the Linux Driver Source Code” on page 8-2
“Enable the Inbox Kernel GPL and Commercial Drivers” on page 8-2
“Check for MSI-X Support” on page 8-3
Locate the Firmware ROM Image
After installing the binary RPM, the firmware ROM image files (nx3fwct.bin and
nx3fwmn.bin) are placed in the /lib/firmware directory.
When the driver module is loaded, the firmware files located in the
/lib/firmware directory are dynamically loaded onto the QLogic adapter.
The dynamically downloaded firmware becomes the active firmware and
supersedes the default firmware Flashed on the QLogic adapter.
NE0154601-00 C 8-1
8–Linux Driver Installation and Configuration
Linux Driver Checklist
Locate the Driver File
The QLogic adapter driver is located at:
SUSE:
Red Hat 5: /lib/modules/[kernel version]/update
Red Hat 4:
/lib/modules/[kernel version]/update/drivers/net
/lib/modules/[kernel version]/kernel/drivers/net
Verify the Firmware Version
Type the following commands to view the firmware version, where n is the port
number:
% ethtool -i eth[n]
% dmesg | grep nx
Verify the Driver Version and Module Information
Type the following commands to view the driver version and module information,
where n is the port number:
% modinfo nx_nic
% ethtool -i eth[n]
Locate the QLogic Tools
Type the following command to go to the directory where the tools are located:
% cd /opt/netxen
These tools include:
nxflash
nxudiag
phantomcore_P3
[card type]-romimage
Build the Linux Driver Source Code
Linux kernel source/headers are required to compile the drivers provided in
source code format. Some Linux operating system (OS) distributions may not
install the kernel source/headers by default. The headers can be added from the
Linux OS Distribution disk using the RPM package manager.
Enable the Inbox Kernel GPL and Commercial Drivers
The inbox kernel GPL and commercial drivers are included in the Linux kernels
available from kernel.org.
8-2 NE0154601-00 C
8–Linux Driver Installation and Configuration
Linux Driver Checklist
NOTE:
The commercial GPL version of the driver (nx_nic.ko) contains the most
recent updates.
To determine which driver to use:
1. The driver name is:
netxen_nic.ko
2. Type the following command to identify the netxen_nic.ko driver:
% lsmod | grep netxen_nic
NOTE:
The netxen_nic.ko file is automatically blacklisted when the Linux
commercial GPL driver RPM is installed.
3. To disable the inbox kernel GPL driver (netxen_nic.ko):
a. Type the following command to remove the driver from the OS
memory:
% rmmod netxen_nic
b. Remove or rename the netxen_nic.ko file from the
/lib/modules/<uname -r>/kernel/drivers/net/netxen
directory.
The commercial GPL driver (nx_nic.ko) can be enabled after the inbox kernel
GPL driver module is disabled.
Check for MSI-X Support
MSI and MSI-X are supported by the QLogic adapter driver and firmware. Ensure
that the OS, kernel, and hardware support MSI-X.
Type the following command to see if MSI-X is supported:
% cat /proc/interrupts
NE0154601-00 C 8-3
8–Linux Driver Installation and Configuration
Inbox Kernel GPL Driver and Blacklisting
The output of this command is similar to the following:
[root@apps4242 ~]# cat /proc/interrupts
CPU0 CPU1
58: 164 7 PCI-MSI-X eth2
66: 0 0 PCI-MSI-X eth2:1
74: 6 0 PCI-MSI-X eth2:2
82: 0 0 PCI-MSI-X eth2:3
122: 3195 0 PCI-MSI-X eth3
130: 0 0 PCI-MSI-X eth3:1
138: 0 0 PCI-MSI-X eth3:2
146: 0 0 PCI-MSI-X eth3:3
NOTE:
Some older Linux kernel versions may not support MSI-X.
Inbox Kernel GPL Driver and Blacklisting
NOTE:
There are two drivers for the QLogic adapter:
netxen_nic.ko. This is the in-kernel (inbox) GPL driver. It is released
into the Linux upstream kernel and included in major Linux distributions.
nx_nic. This is the commercial GPL driver released by QLogic.
When the QLogic RPM binary package is installed, the inbox kernel GPL driver
(netxen_nic.ko) is blacklisted. Consequently, when the system is powered up,
the netxen_nic.ko driver will not load. To prevent this from happening, you can
execute the RPM erase command (rpm -e nx_nic-[version]
remove the QLogic RPM binary package so that the blacklisting will revert back to
the prior setting, and the netxen_nic.ko driver will load when the system is
powered up.
To check if the inbox kernel GPL driver has been installed on the system, check
the /lib/modules/<kernel-version>/kernel/net/netxen directory for
the netxen_nic.ko driver. Remove or rename this file, and then reboot.
Alternately, uninstall the driver by typing the following command before continuing
with the driver installation.
1
), which will
% rmmod netxen_nic
1
[version] refers to the RPM package currently on the system. RPM packages can be located by
typing the command: rpm -qa | grep nx_.
8-4 NE0154601-00 C
8–Linux Driver Installation and Configuration
Preparing for QLogic Adapter Driver Installation
The following sections describe how to install a new driver.
Preparing for QLogic Adapter Driver Installation
Check for prior versions of the QLogic adapter driver and tools. Remove the
packages from the system to prepare for installing the new release.
Use RPM to check for prior packages. For example, type:
% rpm -qa | grep nx_
Look for output similar to the following:
nx_nic-[prior_version]
nx_tools-[prior_version]
Remove each of the prior packages by typing the following commands:
% rpm -e nx_nic-[prior_version]
% rpm -e nx_tools-[prior_version]
QLogic Adapter Driver Installation (RPM Format)
The following sections describe how to install the Linux driver in RPM format,
create the binary, install the binary, and install the QLogic tools.
Install the Linux Driver Source in RPM Format
To install the Linux driver source in RPM format:
1. Type the following command to extract the driver:
tar -zxvf qle30xx_qle31xx-src-[version].tar.gz
2. Type the following command to install the Linux driver RPM source:
% rpm -iv nx_nic-[version].src.rpm
Create the Binary
Type the following command to create the binary RPM for Red Hat systems:
% rpmbuild -bb usr/src/redhat/SPECS/nx_nic-[version].spec
Type the following command to create the binary RPM for SUSE systems:
% rpmbuild -bb usr/src/packages/SPECS/nx_nic-[version].spec
Install the Binary
Type the following command to install the binary RPM for Red Hat systems:
% rpm -i usr/src/redhat/RPMS/[arch]/nx_nic-[version].[arch].rpm
NE0154601-00 C 8-5
8–Linux Driver Installation and Configuration
Linux QLogic Adapter Driver Options
Type the following command to install the binary RPM for SUSE systems:
% rpm -i usr/src/packages/RPMS/[arch]/nx_nic-[version].[arch].rpm
In these commands, the [arch] variable designates the system architecture.
Some [arch] variables include i386, i586, i686, x86_64, depending on the
system. The installed QLogic driver binary will be located in one of the following
directories:
/lib/modules/<uname -r>/updates/drivers/net/
/lib/modules/<uname -r>/kernel/drivers/net
Install the QLogic Tools
To install the QLogic tools:
1. Type the following command to extract the tools:
tar -zxvf qle30xx_qle31xx-linux_tools-[version].tar
2. Type the following command to install the tools:
% rpm -ivh nx_tools-[version].rpm
3. Type the following command to go to the directory where the tools are
located:
% cd /opt/netxen
These tools include:
nxflash
nxudiag
phantomcore_P3
[card type]-romimage ([card type] refers to the exact ROM image)
The release may contain multiple ROM images.
Linux QLogic Adapter Driver Options
Type the modprobe command to pass optional parameters to the driver, for
example:
% modprobe -v nx_nic <parameter>
8-6 NE0154601-00 C
The parameters are listed in Table 8-1.
Table 8-1. modprobe Command Optional Parameters
8–Linux Driver Installation and Configuration
Linux QLogic Adapter Driver Options
Parameter
tx_desc Sets the size of the command descrip-
tor rings (transmit).
jumbo_desc_1g
jumbo_desc Sets the size of the receive ring for
rdesc_1g Sets the size of the receive ring for
rdesc_10g Sets the size of the receive ring for
Sets the size of the receive ring for
jumbo frames (1GbE ports).
jumbo frames (10GbE ports).
normal packets (1GbE ports).
For firmware version 4.0.xyz, the maximum size is 8192.
normal packets (10GbE ports).
For firmware version 4.0.xyz, the maximum size is 8192.
Description Default Range
1024 256–1024
(must be
power of two)
1024
(x86 64-bit)
512
(x86 32-bit)
1024 64–1024
8192
(x86 64-bit)
2048
(x86 32-bit)
8192
(x86 64-bit)
4096
(x86 32-bit)
64–1024
(must be
power of two)
(must be
power of two)
64–8192
(must be
power of two)
64–8192
(must be
power of two)
use_msi Enables MSI interrupts. 1 0: Disabled
1: Enabled
use_msi_x Enables MSIx interrupts.
This parameter is available only in
kernel versions later than 2.6.8. When
this parameter is enabled, it takes precedence over MSI interrupts and the
use_msi parameter is ignored.
rss_enable Enables receive side scaling. This
parameter is available only when
MSI-X interrupts are enabled.
1 0: Disabled
1: Enabled
1 0: Disabled
1: Enabled
Ethtool Utility
The ethtool utility checks and configures additional driver options. See the
nx_nic Linux man pages for driver option configuration examples. See the
ethtool Linux man pages for additional details. Here is an example command:
% ethtool -K eth[n] tso off
NE0154601-00 C 8-7
8–Linux Driver Installation and Configuration
Configure the QLogic Adapter on Linux
Configure the QLogic Adapter on Linux
To configure the QLogic adapter:
1. Type one of the following commands to identify the Ethernet interface
(eth1, eth2, etc.) and the nx_nic driver from the command line:
% cat /proc/net/nx_nic/dev0/stats | grep eth or
% ifconfig -a
Look for the interface with a MAC address (HWaddr) prefix of
00:0E:1E:XX:XX:XX
2. Type the following to commands assign an IP Address and activate the
interface:
% ifconfig eth[n] down
% ifconfig eth[n] <IP Address> netmask <Netmask Value> up
3. Verify that the network services are running, and then type:
% service network restart
To verify connectivity, contact a different IP address using the ping
command.
Uninstall the Commercial GPL Driver and Tools Package
Type the following commands to uninstall the commercial GPL driver and tools,
which are part of the RPM package:
% rpm -qa | grep nx_
% ifconfig eth[n] down
% rmmod nx_nic.ko
% rpm -e nx_nic-[version]
% rpm -e nx_tools-[version]
1
Diagnostic Tests for the QLogic Adapter
The Linux user diagnostics utility performs various tests using the
./nxudiag -i eth[n] command.
The syntax for these tests is:
% ./nxudiag [command-options-and-arguments]
See Table A-1 for a list of Linux diagnostic utility commands.
1
[version] refers to the RPM package currently on the system. RPM packages can be located
by executing the command: rpm -qa | grep nx_.
8-8 NE0154601-00 C
NOTE:
While running these tests, the network traffic will be interrupted.
Linux Performance Tuning
This section describes Linux performance tuning.
NOTE:
The tunable performance parameters are system and application specific.
Understanding the relationship between the parameter values, target
workload, performance applications, operating system, and system
configuration provides a better understanding of performance optimization
and bottlenecks.
Performance Tools
8–Linux Driver Installation and Configuration
Linux Performance Tuning
Add the following parameters for performance tuning on Linux systems in the
/etc/sysctl.conf file:
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.optmem_max = 524287
net.core.netdev_max_backlog = 250000
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 87380 16777216
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_low_latency = 0
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_moderate_rcvbuf = 1
net.ipv4.route.flush = 1
NOTE:
Various factors including tools, kernel, stacks, and related parameters affect
system performance.
Using the iperf Tool
The iperf tool measures network performance. The following paragraphs show
how to use iperf; however, it can be further tuned depending on your system’s
requirements.
NE0154601-00 C 8-9
8–Linux Driver Installation and Configuration
Linux Performance Tuning
Here is an example of iperf from the server side:
% iperf -s -w lM -1 16k
Here is an example of iperf from the client side:
% iperf -c <ipAddr of Server> -w 1M -P12 -l 16k -P<number of threads>
Optimization
Note the following:
PCIe x8 provides optimal performance for 10GbE.
MSI and MSI-X interrupts perform better than legacy interrupts.
Linux kernel version 2.6.15 and higher provide better performance
optimization.
Check CPU utilization on the host for CPU-bound bottlenecks.
8-10 NE0154601-00 C
9 Linux Configuration for
Bonding Mode and Virtual
LAN (VLAN)
Linux Bonding Mode
Ensure that the steps required for installing the RPM source, creating the binary,
and installing the binary have been performed as described in “QLogic Adapter
Driver Installation (RPM Format)” on page 8-5 before setting up Linux bonding
mode.
Type the following command to verify that the QLogic adapter driver has been
installed:
% lsmod | grep nx_nic
Type the following command to install the driver (if it has not yet been installed):
% modprobe -v nx_nic
The steps for setting the Linux bonding mode are as follows. Note that these are
example commands. The actual commands may be different depending on the
system configuration.
1. % modprobe bonding mode=1 miimon=100 updelay=50000
primary=eth16
2. % ifconfig bond0 25.145.1.199 netmask 255.255.255.0
broadcast 25.145.1.255 up
3. % ifenslave bond0 eth15 eth16
Type the following command to bring down the bond:
% ifconfig bond0 down
NOTE:
These commands and steps have been tested under RHEL5. Other Linux
distributions and versions may enable and utilize bonding differently.
NE0154601-00 C 9-1
9–Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Linux Bonding Mode
After bonding, the MAC addresses for the two ports that were bonded appear to
be the same when running the ifconfig command. This similarity is due to the
formation of a bond to permit traffic to be passed between the ports.
After the bond has been brought down and the bonding driver removed, the
QLogic adapter’s original MAC addresses will resume on the ports.
Active-Backup or Mode=1
The active-backup policy allows only one slave in the bond to be active. A
different slave becomes active only if the active slave fails.
By setting mode=1, when ifenslave is executed, the bonding driver calls into
the bond_enslave() function and sets the slave link modes for the
corresponding two Ethernet ports to BOND_LINK_DOWN.
When the bond mode is 1 (BOND_MODE_ACTIVEBACKUP) and the primary device
is indicated, one slave device is configured as the active slave. The dmesg
command displays the primary port. Here is an example output of the dmesg
command:
bonding: bond0: making interface eth16 the new active one 0 ms
earlier
If the active connection goes down, then the slave port becomes the primary port.
Type the following command to monitor the bonding process during the
switch-over or port priority:
% cat /proc/net/bonding/bond0
The following message is displayed:
MII Status: up (for eth16)
The dmesg command shows the status of the slave port, for example:
bonding: bond0: link status up for interface eth15, enabling it in
50000 ms.
Type the following command to check the status of the primary port:
% cat /proc/net/bonding/bond0
The output for this command is:
MII Status: down (for eth16)
After 50 seconds, the dmesg command will print:
bonding: bond0: link status definitely up for interface eth15.
bonding: bond0: making interface eth15 the new active one.
Type the following command to check the status of the new primary port:
% cat /proc/net/bonding/bond0
9-2 NE0154601-00 C
The output for this command is:
MII Status: up (for eth15)
Round-Robin or Mode=0
This mode implements a round-robin scheme between the two Ethernet ports. To
set the round-robin mode, type the following command:
% modprobe bonding mode=0 miimon=100 updelay=50000 primary=eth16
After the command is executed, both links delay for 50 seconds before their states
are set to BOND_LINK_UP.
Type the following command to check the status of the bonding process:
% cat /proc/net/bonding/bond0
The output for this command is:
Ethernet Channel Bonding Driver: v3.0.1
Bonding Mode: load balancing (round-robin) MII Status: up MII
Polling Interval (ms): 100 Up Delay (ms): 50000 Down Delay (ms): 0
Slave Interface: eth16
MII Status: down
Link Failure Count: 0
Permanent HW addr: 00:0e:1e:00:11:d2
9–Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Linux Bonding Mode
<========== down state
Slave Interface: eth15
MII Status: down
Link Failure Count: 0
Permanent HW addr: 00:0e:1e:00:11:d3
<========= down state
After 50 seconds, type the command again to verify the MII status of the Ethernet
ports:
% cat /proc/net/bonding/bond0
NE0154601-00 C 9-3
9–Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Linux Bonding Mode
The output for this command is:
Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)
Bonding Mode: load balancing (round-robin) MII Status: up MII
Polling Interval (ms): 100 Up Delay (ms): 50000 Down Delay (ms): 0
Slave Interface: eth16
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:0e:1e:00:11:d2
Slave Interface: eth15
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:0e:1e:00:11:d3
The dmesg command output is:
bonding: bond0: link status definitely up for interface eth16.
bonding: bond0: link status definitely up for interface eth15.
<=========== up state
<=========== up state
Bonding Driver Options
Options for the bonding driver are supplied as parameters to the bonding module
at load time. They may be given as command line arguments to the modprobe
command, but are usually specified in the /etc/modules.conf or
/etc/modprobe.conf configuration file, or in a distribution-specific
configuration file (some of which are detailed in the next section).
Bonding Driver Parameters
The available bonding driver parameters are listed in the following sections. If a
parameter is not specified, the default value is used. When initially configuring a
bond, QLogic recommends that tail -f /var/log/messages be run in a
separate window to watch for bonding driver error messages.
It is critical to specify the following parameters; otherwise, serious network
degradation will occur during link failures.
miimon or arp_interval and
arp_ip_target
Most devices support miimon, so it is safe to use.
Options with textual values accept either the text name or, for backward
compatibility, the option value. For example, mode=802.3ad and mode=4 set the
same mode.
9-4 NE0154601-00 C
arp_interval
This parameter specifies the ARP link monitoring frequency in milliseconds. When
ARP monitoring is used in an etherchannel compatible mode (modes 0 and 2), the
switch must be configured in a mode that evenly distributes packets across all
links.
When the switch is configured to distribute the packets in an XOR fashion, all
replies from the ARP targets are received on the same link, which could cause the
other team members to fail. ARP monitoring should not be used with miimon. A
value of 0 disables ARP monitoring. The default value is 0.
arp_ip_target
This parameter specifies the IP addresses to use as ARP monitoring peers when
arp_interval is greater than 0. These are the targets of the ARP request sent
to determine the health of the link to the targets.
Specify these values in ddd.ddd.ddd.ddd format. Multiple IP addresses must
be separated by a comma. At least one IP address must be given for ARP
monitoring to function. The maximum number of targets that can be specified
is 16. The default value is no IP addresses.
9–Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Linux Bonding Mode
downdelay
This parameter specifies the time, in milliseconds, to wait before disabling a slave
after a link failure has been detected. This option is valid only for the miimon link
monitor. The downdelay value must be a multiple of the miimon value;
otherwise, the value will be rounded down to the nearest multiple. The default
value is 0.
lacp_rate
This parameter specifies the rate at which the link partner transmits LACPDU
packets in 802.3ad mode. Possible values are:
Slow or 0: Request partner to transmit LACPDUs every 30 seconds
(default).
Fast or 1: Request partner to transmit LACPDUs every 1 second.
QLogic Adapter Bonding Modes Under Linux
There are several modes that can be used for bonding the QLogic adapter under
Linux. Note that there are variations in support and usage with respect to the
hardware and Linux distributions, and that not all the modes work for a given
system and network topology.
NE0154601-00 C 9-5
9–Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Linux Bonding Mode
The bonding modes are described in Table 9-1.
Table 9-1. Bonding Modes
Mode
Number
0 balance-rr This mode uses a round-robin policy; it transmits
1 active-backup In this mode, one slave interface is active at all
2 balance-xor In this mode, transmissions are balanced across the
3 broadcast This mode transmits everything on all slave inter-
4 802.3a This mode provides standard IEEE 802.3ad
Mode Name Description
packets in sequential order, from the first available
slave through the last. This mode provides load balancing and fault tolerance.
times. If one interface fails, another interface takes
over the MAC address and becomes the active
interface. This mode provides only fault tolerance.
This mode does not require special switch support.
slave interfaces based on ((source MAC) XOR (dest
MAC)) modulo slave count. The same slave is
selected for each destination MAC. This mode provides load balancing and fault tolerance.
faces. This mode provides fault tolerance.
dynamic link aggregation. It requires 802.3ad support in the switch, and driver support for retrieving
the speed and duplex of each slave.
5 balance-tlb This mode provides adaptive transmit load balanc-
ing. Incoming traffic is received only on the active
slave. Outgoing traffic is distributed according to the
current load on each slave. This mode does not
require special switch support.
6 balance-alb This mode provides adaptive load balancing
through ARP negotiation; both transmit load balancing (TLB) and receive load balancing are supported
for IPv4. This mode does not require special switch
support, but does require the ability to change the
MAC address of a device while it is open.
9-6 NE0154601-00 C
9–Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Configuring Virtual LAN (VLAN) Under Linux
Configuring Virtual LAN (VLAN) Under Linux
To configure the VLAN function:
1. Type the following command to see if the 8021q.ko driver has been
loaded:
% lsmod | grep 8021q
Type the following command if the driver has not been loaded:
% modprobe -v 8021q
The vconfig add command creates a VLAN device on eth0 and will, in
turn, create an eth0.5 interface.
2. Type the following command for eth0 to add VLAN ID 5:
% vconfig add eth0 5
3. Type the ifconfig command to assign an IP address to the VLAN
interface:
% ifconfig eth0.5 192.168.1.100 netmask 255.255.255.0
broadcast 192.168.1.255 up
4. Type the following command to get detailed information about the VLAN
interface:
% cat /proc/net/vlan/eth0.5
Repeat Steps 2 and 3 if more than one VLAN is required.
Type the following commands to delete a VLAN interface:
% ifconfig eth0.5 down
% vconfig rem eth0.5
NE0154601-00 C 9-7
9–Linux Configuration for Bonding Mode and Virtual LAN (VLAN)
Configuring Virtual LAN (VLAN) Under Linux
9-8 NE0154601-00 C
10 Firmware Management
This section describes the firmware download process. When the driver package
is installed, the firmware files are installed onto the host operating system (OS).
The dynamic firmware download takes place when the driver module is loaded.
As the driver module is loaded, the firmware file downloaded from the host OS
becomes the active firmware version on the QLogic adapter.
Windows Server Dynamic Firmware Download
During the driver installation process, the firmware ROM image files are placed in
the C:\WINDOWS\system32\drivers directory.
Type the following command to determine if the firmware loaded successfully in
Windows Server. The n in “Local Area Connection n” refers to the port
being Flashed.
nxflash.exe -i “Local Area Connection n” --info (The quotation marks
are required.)
Check for the following entry:
Active Firmware version: 4.0.408
To determine the port number (n), click the Start button, right-click My Network
Places, and then click Properties. The Network Connections window opens.
The Network Connections window lists all of the ports and the type of device to
which they are connected.
Linux Dynamic Firmware Download
After the installation of the driver RPM, the firmware ROM image files are placed
in the /lib/firmware directory.
When the driver is installed, the firmware file located in the /lib/firmware
directory is dynamically loaded onto the QLogic adapter.
Type the following command to determine if the firmware has loaded successfully.
The [n] refers to the port number.
ethtool -i eth[n]
NE0154601-00 C 10-1
10–Firmware Management
Linux Dynamic Firmware Download
Check for the following entry:
Active Firmware version: 4.0.408
10-2 NE0154601-00 C
11 Troubleshooting Guidelines
Unable to Boot the Host System with the QLogic Adapter Installed
If the system does not boot after installing the QLogic adapter:
1. Remove the QLogic adapter and power up the system. Does the system
boot without the QLogic adapter? If so, power down the system, insert the
QLogic adapter into a different PCIe slot, and power up the system.
2. Ensure that the system BIOS configuration is up-to-date during the system
boot up process.
3. Ensure that the recommended minimum memory is installed on the host
system.
4. Note any error messages that appear during the operating system (OS) boot
sequence.
5. Check for system error messages.
Windows event viewer
% dmesg (display system messages on Linux)
Unable to Send/Receive Network Traffic Using the QLogic Adapter
If network traffic cannot be sent/received with the QLogic adapter:
1. Ensure that the network cable is plugged in properly.
2. Ensure that the SFP+ module is installed correctly (see “QLE3142
Installation” on page 4-4).
3. Ensure that the client machine is configured correctly and able to
communicate with other machines.
NE0154601-00 C 11-1
11–Troubleshooting Guidelines
Additional Configuration for Windows Server 2008 Teaming
4. Type lspci -v and look for vendor ID 4040.
a. Check to see if the QLogic adapter is visible on the PCI bus.
b. Check to see if the
slot.
5. Check if the driver is loaded correctly and the card is initialized.
Windows event viewer
dmesg (display system messages on Linux)
6. Check the network configuration.
a. Check for a valid IP address and subnet.
b. Check for duplicate IP address and subnet numbers.
c. Check the gateway address and network path (if connected through a
gateway).
d. Check the QLogic adapter MAC address values.
e. Verify the network link status as seen by the host OS.
f. Check for LED activity (using
g. Analyze the transmit and receive packets for the QLogic adapter using
network monitoring tools.
h. Verify the ARP entry and response.
QLogic
adapter is plugged into the appropriate PCIe
ping).
If none of the previous steps resolve the problem, run the QLogic user
diagnostics.
Additional Configuration for Windows Server 2008 Teaming
How-to tips can be found at the bottom of the Teaming Management tab in the
QLogic Advanced Network Config Service window (see Figure 6-15).
Troubleshooting Tools
The following sections explain how to use the Windows and Linux tools to help
solve potential problems.
11-2 NE0154601-00 C
Windows Server Tools
The troubleshooting tools available in Windows Server are described in
Table 11-1.
Table 11-1. Troubleshooting Tools in Windows Server
Tool What it Provides
systeminfo The systeminfo tool provides detailed information about the
Device manager The device manager shows the hardware configured on the
Driver tab The driver tab displays device status, QLogic adapter informa-
ipconfig The ipconfig tool shows IP network settings; it also releases
11–Troubleshooting Guidelines
Troubleshooting Tools
operating system version, CPU, system manufacturer and
model, memory configuration, hot fixes, and network cards.
system.
tion, debug counters for gathering support log details, diagnostics test cases, statistics, driver version, and resources.
and renews by adapter or connection.
%systemRoot%\
windows\inf\
QLsetup.log
Windows event log The Windows event log is the main source of information for
Linux Tools
The troubleshooting tools available in Linux are described in Table 11-2.
This log contains messages from the installer program (MSI);
these messages indicate if the installation was successful.
device driver problems and events. The QLogic adapter’s
device drivers indicate status by logging events in the system
event log.
Table 11-2. Troubleshooting Tools in Linux
Tool What is Provides
nxdebug1 Linux script does not require the nx_nic driver to be loaded. This tool
gathers information on the kernel, any GPL or nx_nic driver loaded,
RPM packages, processor, memory, interrupts, PCI bus, dmesg (last
50 messages), and network configuration.
nxdebug2 Linux script does require the nx_nic driver to be loaded. This tool
gathers kernel configuration, nx_nic device stats, multicast settings,
nx_nic driver messages from the /var/log/messages file, modprobe info, SLAB information, buddy information, I/O memory infor-
mation, sysctl information, the complete dmesg log, ethtool
details on the nx_nic interface, and specific nx_nic status.
NE0154601-00 C 11-3
11–Troubleshooting Guidelines
Check for System Errors
Check for System Errors
Linux
To check for system errors in Linux.
Check for error messages from the kernel using the following commands:
% dmesg
% cat /var/log/messages
Check routing table, gateway, and IP address conflicts for all interfaces
using the following command:
% route
Check network interface transmit and receive counts during pings using the
following command:
% ifconfig <network interface>
Use the wireshark, ethereal, tethereal, or tcpdump utility to capture
packets.
Windows Server
To check for system errors in Windows Server:
Use the
Check for system error messages using the Windows event viewer.
wireshark or ethereal utilities to capture packets.
Caveats
MSI-X Interrupts for Linux
Newer Linux OS distributions or kernel versions support MSI-X interrupts; some
older versions do not support MSI-X. If MSI-X is not available on the OS, then use
MSI or legacy mode in the OS.
Type the following command on the Linux host to check that PCI-MSI-X or
PCI-MSI is enabled for the Ethernet interface:
% cat /proc/interrupts
Determine if the installed Linux kernel has the MSI configuration option enabled
(earlier versions of the kernel may require an MSI patch).
Type the following command from the directory
version>
and verify that the MSI configuration option is supported/enabled:
/usr/src/kernels/<kernel
% make menuconfig
11-4 NE0154601-00 C
PCI Express Slot
The QLogic adapter can be located on the PCI Express bus using the following
Linux procedures.
Determine the vendor and device ID. To check if the PCIe slot has a x8
link for optimal PCIe performance, first determine the PCI vendor ID and
device ID code by typing the following command:
% lspci -n
You should see a message similar to:
06:00.0 0200: 4040:0100 (rev 42)
The QLogic vendor ID is 0x4040. A list of QLogic adapter device IDs is listed
in Tab le 11 -3 .
Product Device ID Description
11–Troubleshooting Guidelines
Caveats
Table 11-3. QLogic Adapter Device IDs
QLE3044 0124 Quad-port 1GbE copper interface
QLE3142-CU 0126 Dual-port 10GbE with twinax interface
QLE3142-SR 0126 Dual-port 10GbE with short-range fiber interface
QLE3142-LR 0126 Dual-port 10GbE with long-range fiber interface
Determine the interface attributes. To determine the attributes of the
interface, type the following command:
% lspci -n -d 4040:0100 -vvv | grep -i width
You should see a message similar to:
Link: Supported Speed 2.5 Gb/s, Width x8, ASPM L0s, Port 0
Link: Speed 2.5Gb/s, Width x8
Determine the width parameters. Check if the lspci output “negotiated
width” (the second width in the output) reflects the actual “supported width”.
In an system with a QLE3044, for example, type the following command to
determine if these two widths are the same:
% lspci -xxx -vvv -d 4040:0100
In the previous command, 4040 indicates the QLogic vendor ID and 0124
indicates a QLE3044. The device ID is 0126.
NE0154601-00 C 11-5
11–Troubleshooting Guidelines
...... 82 04 00 00 01 00 82
Supported
link width
Negotiated
link width
||_________ capability. “82 04" = x8 PCIe Gen2
c0: 10 00 02 00 02 80 00 00 00 10 0b 00 82 04 00 00
Caveats
Examine the following hex output:
From the
lspci hex output:
Note that some PCIe chip sets with a x16 link may not support a PCI
Express x8 link width. A link is required to support only its maximum width
and x1. Check the motherboard specification to determine if its PCIe x16 slot
can autonegotiate to x8.
On some motherboards, the PCIe slots are all the same physical size
required by a x16 slot, but electrically they are different widths. Check the
motherboard specification for the supported width of each of the PCIe slots.
11-6 NE0154601-00 C
A Diagnostic Utility
Commands
Table A-1 lists user-level diagnostic utility commands for the Linux and Windows
Server OSs.
Table A-1. Diagnostic Utility Commands
Command Description
-i
--interface
-a
--all
-D
--default
-R
--CRegs
-F
-FLASH
-I
--IRQS
-L
--IntLB
-H
--Hw
-S
--LinkST
This command specifies the interface type (Local Area Connection 1, Local Area Connection 2, etc.).
This command performs all tests, regardless of the default.
This command performs only the default test.
This command tests all control registers (default).
This command tests the Flash (default).
This command tests the interrupt mechanism (default).
This command performs an internal loopback test (default).
This command performs a hardware test (default).
This command tests the link status (default).
-l
--LED
NE0154601-00 C A-1
This command tests the LEDs (default).
A–Diagnostic Utility Commands
Table A-1. Diagnostic Utility Commands (Continued)
Command Description
-nR
--noCRegs
-nF
--noFLASH
-nl
--noIRQS
-nL
--noIntLB
-nH
--noHw
-nS
--noLinkSt
-nl
--noLED
-E
--ExtLB
-h
--help
This command disables control register testing (use with -D or
-a).
This command disables Flash testing (use with -D or -a).
This command disables interrupt testing (use with -D or -a).
This command disables internal loopback testing (use with -D or
-a).
This command disables hardware testing (use with -D or -a).
This command disables link status testing (use with -D or -a).
This command disables LED status testing (use with -D or -a).
This command performs an external full-duplex loopback test.
This command prints the help message.
-v
--version
-C
--Cmdif
A-2 NE0154601-00 C
This command displays version information.
This command performs an interface status test.
NOTE: This command is valid only in Linux.
B Flash Update
Under rare circumstances, it may be necessary update the Flash on the QLogic
adapter. Contact Technical Support to see if a Flash update is required. If so,
follow the instructions in this appendix.
Flash Update and Tool Guidelines
Consider the following before updating the Flash:
The update process should not be interrupted (do not reboot or stop the
update process).
A backup image of the existing Flash will be created at the start of the Flash
update process. The Flash utility will use the backup image to recover if
required.
The Flash tool will not start the Flash update process if the QLogic adapter
driver is not loaded.
The Flash tool auto-identifies the appropriate Flash image for the QLogic
adapter.
Flash Update Options
Options for updating the Flash are as follows. Do use these options unless
specified by Technical Support.
“nxflash Command” on page B-1
“NX Live CD” on page B-2
“NX Live USB” on page B-2
nxflash Command
Run the appropriate command from Linux or Windows Server, as described in the
following paragraphs.
NE0154601-00 C B-1
B–Flash Update
Flash Update Options
Windows Server
Type the following command, where “Local Area Connection n” specifies
the adapter being Flashed:
nxflash -i “Local Area Connection n” --all (the quotes are required)
You are prompted to answer Y(es) or N(o) to allow the upgrading of the Flash to
continue. Press the Y key to continue.
See “QLogic Adapter Flash Update—Windows Server” on page B-3 for more
information.
Linux
Type the following command, where [n] indicates the port number of the QLogic
adapter (0, 1, 2, etc.):
./nxflash -i [n] --all
See “QLogic Adapter Flash Update—Linux” on page B-8 for more information.
NX Live CD
To install the NX Live CD:
1. Download the QLogic Live ISO image file from the QLogic Web site,
2. Burn the ISO image onto a CD writable media (make sure your system has a
3. Insert the NX Live CD into the system that contains the QLogic adapter.
4. Change any BIOS settings to permit the CD to boot before the other devices
5. Boot the system from the CD.
6. Use the menu options (see “NX Live Menu Options” on page B-3) to show
Refer to the support page on the on QLogic Web site for more information on
downloading the NX Live CD.
NX Live USB
To install the NX Live USB:
www.qlogic.com
CD burner).
on the system.
current board information, update the firmware, or reboot the system
(remember to remove the NX Live CD if you need to revert back to the
operating system (OS) on the hard disk).
.
1. Download the NX Live USB zip image file from the QLogic Web site,
www.qlogic.com
2. Insert a USB Flash device in a USB slot.
B-2 NE0154601-00 C
.
Loading...