Qlogic 8400 Series User Manual
  1. Manuals
  2. Brands
  3. Qlogic Manuals
  4. Adapter
  5. 8400 Series
  6. User manual

Qlogic 8400 Series User Manual

Converged network adapters and intelligent ethernet adapters
Hide thumbs Also See for 8400 Series:
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
Table of Contents

Advertisement

Quick Links

User's Guide
Converged Network Adapters and Intelligent
Ethernet Adapters
8400, 3400 Series
83840-546-00 D

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 8400 Series and is the answer not in the manual?

Questions and answers

Related Manuals for Qlogic 8400 Series

Summary of Contents for Qlogic 8400 Series

  • Page 1 User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series 83840-546-00 D...

  • Page 2: Document Revision History

    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.
  • Page 3 User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series Added FCoE boot support for VMware ESXI 5.5 “VMware ESXi FCoE Boot Installation” on and 6.0 page 242 Added NPAR support for VMware ESXi 6.0 “Supported Operating Systems for NIC Partition- ing”...
  • Page 4 User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series 83840-546-00 D...

  • Page 5: Table Of Contents

    QLogic Control Suite ........
  • Page 6 Removing the Device Drivers........Installing QLogic Management Applications ......
  • Page 7 User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series Unloading/Removing the Linux Driver ......Unloading/Removing the Driver from an RPM Installation .
  • Page 8 User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series bnx2x Driver ..........Driver Sign On .
  • Page 9 User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series Teaming with Channel Bonding ........Statistics .
  • Page 10 Configure OpenPegasus on the Server ....Install QLogic CMPI Provider ......
  • Page 11 Starting QLogic Control Suite ........
  • Page 12 LiveLink ..........Using the QLogic Teaming Wizard ......
  • Page 13 Installing the Microsoft iSCSI Initiator ..... Configuring QLogic iSCSI Using QCS ....
  • Page 14 Specify BIOS Boot Protocol (if required) ....Prepare QLogic Multiple Boot Agent for FCoE Boot ....
  • Page 15 User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series Errors During Windows FCoE Boot from SAN Installation ..Configuring FCoE..........NIC Partitioning and Bandwidth Management Overview .
  • Page 16 Data Center Bridging in Windows Server 2012 ..... . QLogic Teaming Services Executive Summary ......... .
  • Page 17 User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series Preboot Execution Environment ......General Network Considerations .
  • Page 18 User’s Guide—Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series SLB (Auto-Fallback Disable) ....... . Limitations of Smart Load Balancing and Failover/SLB (Auto-Fallback Disable) Types of Teams.
  • Page 19 Expert Mode—Create a Team with a VLAN....... 10-1 QLogic 577xx/578xx Ethernet Boot Agent ....... . 10-2 CCM Device List .
  • Page 20 User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series 10-9 Configuring VLANs—CCM Device List ........10-10 Configuring VLANs—Multiboot Agent Configuration .
  • Page 21 Windows Operating Systems and iSCSI Crash Dump..... . . QLogic 8400/3400 Series Linux Drivers........
  • Page 22 User’s Guide Converged Network Adapters and Intelligent Ethernet Adapters 8400, 3400 Series xxii 83840-546-00 D...

  • Page 23: Preface

    This guide is intended for personnel responsible for installing and maintaining computer networking equipment. What Is in This Guide ® This guide describes the features, installation, and configuration of the QLogic 8400/3400 Series Converged Network Adapters and Intelligent Ethernet Adapters. The guide is organized as follows: ...

  • Page 24: Related Materials

     Appendix A, Adapter LEDS describes the adapter LEDs and their significance. Related Materials For information about downloading documentation from the QLogic Web site, see “Downloading Updates” on page xxvii. xxiv 83840-546-00 D...

  • Page 25: Documentation Conventions

     “Installation Checklist” on page  For more information, visit www.qlogic.com.  Text in bold font indicates user interface elements such as a menu items, buttons, check boxes, or column headings. For example: ...

  • Page 26: License Agreements

    License Agreements Refer to the QLogic Software End User License Agreement for a complete listing of all license agreements affecting this product. xxvi...

  • Page 27: Technical Support

    Service Program Web page at http://www.qlogic.com/Support/Pages/ServicePrograms.aspx. Downloading Updates The QLogic Web site provides periodic updates to product firmware, software, and documentation. To download firmware, software, and documentation: Go to the QLogic Downloads and Documentation page: driverdownloads.qlogic.com.

  • Page 28: Training

    Training QLogic Global Training maintains a Web site at www.qlogictraining.com offering online and instructor-led training for all QLogic products. In addition, sales and technical professionals may obtain Associate and Specialist-level certifications to qualify for additional benefits from QLogic. Contact Information QLogic Technical Support for products under warranty is available during local standard working hours excluding QLogic Observed Holidays.

  • Page 29: Legal Notices

    Agency Certification The following sections contain a summary of EMC and EMI test specifications performed on the QLogic adapters to comply with emission and product safety standards. EMI and EMC Requirements FCC Rules,CFR Title 47, Part 15, Subpart B:2013 Class A This device complies with Part 15 of the FCC Rules.

  • Page 30: Product Safety Compliance

    Preface Legal Notices CE Mark 2004/108/EC EMC Directive Compliance EN55022:2010 Class A1:2007/CISPR22:2009+A1:2010 Class A EN55024:2010 EN61000-3-2:2006 A1 +A2:2009: Harmonic Current Emission EN61000-3-3:2008: Voltage Fluctuation and Flicker VCCI VCCI:2012-04; Class A AS/NZS CISPR22 AS/NZS; CISPR 22:2009+A1:2010 Class A KC-RRA KN22 KN24(2013) Class A Product Safety Compliance UL, cUL product safety: UL60950-1 (2nd Edition), 2007...

  • Page 31: Product Overview

     Adapter Specifications Functional Description The QLogic 8400/3400 Series adapters are based on a new class of Gigabit Ethernet (GbE) and 10GbE converged network interface controller (C-NIC) that can simultaneously perform accelerated data networking and storage networking on a standard Ethernet network. The C-NIC offers acceleration for popular protocols used in the data center, such as: ...

  • Page 32: Features

    1–Product Overview Features Using the QLogic teaming software, you can split your network into virtual LANs (VLANs) and group multiple network adapters together into teams to provide network load balancing and fault tolerance. See Chapter 18 Chapter 17 detailed information about teaming. See Chapter 13 for a description of VLANs.
  • Page 33  QLogic Control Suite diagnostic and configuration software suite. See the QLogic Control Suite GUI Installation Guide, QLogic Control Suite GUI online help and the QLogic Control Suite Command Line Interface User’s Guide for more information.  Supports the pre-execution environment (PXE) 1.0 and 2.0 specifications ...

  • Page 34: Iscsi

    TCP layer. iSCSI processing can also be offloaded, thereby reducing CPU use even further. The QLogic 8400/3400 Series adapters target best-system performance, maintains system flexibility to changes, and supports current and future OS convergence and integration. Therefore, the adapter's iSCSI offload architecture is unique because of the split between hardware and host processing.

  • Page 35: Power Management

    CPU cycles. ASIC with Embedded RISC Processor The core control for QLogic 8400/3400 Series adapters resides in a tightly integrated, high-performance ASIC. The ASIC includes a RISC processor that provides the flexibility to add new features to the card and adapt to future network requirements through software downloads.

  • Page 36: Standards Specifications

    1–Product Overview Adapter Specifications Standards Specifications  IEEE 802.3ae (10Gb Ethernet)  IEEE 802.1q (VLAN)  IEEE 802.3ad (Link Aggregation)  IEEE 802.3x (Flow Control)  IPv4 (RFC 791)  IPv6 (RFC 2460)  IEEE 802.1Qbb (Priority-based Flow Control)  IEEE 802.1Qaz (data center bridging exchange (DCBX) and enhanced transmission selection [ETS]) ...

  • Page 37: Installing The Hardware

    Preinstallation Checklist  Installation of the Network Adapter System Requirements Before you install a QLogic 8400/3400 Series adapter, verify that your system meets the following hardware and operating system requirements: Hardware Requirements  IA32- or EMT64-based computer that meets operating system requirements ...

  • Page 38: Safety Precautions

    Requirements. Verify that your system is using the latest BIOS. NOTE If you acquired the adapter software on a disk or from the QLogic Web Site driverdownloads.qlogic.com), verify the path to the adapter driver files. If your system is active, shut it down.

  • Page 39: Installation Of The Network Adapter

    Installation of the Network Adapter Installation of the Network Adapter The following instructions apply to installing the QLogic 8400/3400 Series adapters in most systems. Refer to the manuals that were supplied with your system for details about performing these tasks on your particular system.

  • Page 40: Connecting The Network Cables

    Connecting the Network Cables Connecting the Network Cables The QLogic 8400/3400 Series adapters have either an RJ-45 connector used for attaching the system to an Ethernet copper-wire segment, or a fiber optic connector for attaching the system to an Ethernet fiber optic segment.

  • Page 41: Multi-Boot Agent (Mba) Driver Software

    Multi-Boot Agent (MBA) is a software module that allows your network computer to boot with the images provided by remote servers across the network. The QLogic MBA driver complies with the PXE 2.1 specification and is released with split binary images. This provides flexibility to users in different environments where the motherboard may or may not have built-in base code.

  • Page 42: Setting Up Mba In A Client Environment

    QLogic network adapter using the Comprehensive Configuration Management (CCM) utility. To configure the MBA driver on LOM models of the QLogic network adapter, check your system documentation. Both the MBA driver and the CCM utility reside on the adapter Flash memory.

  • Page 43: Mba Configuration Menu

    3–Multi-boot Agent (MBA) Driver Software Setting Up MBA in a Client Environment Select the adapter to configure and press ENTER. The Main Menu displays. Select MBA Configuration to display the MBA Configuration menu (Figure 3-1). Figure 3-1. MBA Configuration Menu Use the up arrow and down arrow keys to move to the Boot Protocol menu item.

  • Page 44: Setting Up The Bios

    Linux. The Initrd.img file distributed with Red Hat Enterprise Linux, however, does not have a Linux network driver for the QLogic 8400/3400 Series adapters. This version requires a driver disk for drivers that are not part of the standard distribution.

  • Page 45: Windows Driver Software

    When Windows first starts after a hardware device has been installed (such as a QLogic 8400/3400 Series adapter), or after the existing device driver has been removed, the operating system automatically detects the hardware and prompts you to install the driver software for that device.

  • Page 46: Using The Installer

    4–Windows Driver Software Installing the Driver Software Using the Installer If supported and if you will use the QLogic iSCSI Crash Dump utility, it is important to follow the installation sequence:  Run the installer  Install the Microsoft iSCSI Software Initiator along with the patch To install the QLogic 8400/3400 Series drivers When the Found New Hardware Wizard appears, click Cancel.

  • Page 47: Using Silent Installation

    4–Windows Driver Software Installing the Driver Software http://www.microsoft.com/downloads/en/details.aspx?familyid=12cb3c1a-15 d6-4585-b385-befd1319f825&displaylang=en. Install Microsoft patch for iSCSI crash dump file generation (Microsoft KB939875) from http://support.microsoft.com/kb/939875. To determine if you need to install the Microsoft patch, see Table 4-1. Table 4-1. Windows Operating Systems and iSCSI Crash Dump MS iSCSI Software Microsoft Patch (MS Operating System...

  • Page 48: Removing The Device Drivers

    /s /v” /qn DOWNGRADE=Y” Removing the Device Drivers Uninstall the QLogic 8400/3400 Series device drivers from your system only through the InstallShield wizard. Uninstalling the device drivers with Device Manager or any other means may not provide a clean uninstall and may cause the system to become unstable.

  • Page 49: Viewing Or Changing The Adapter Properties

    4–Windows Driver Software Viewing or Changing the Adapter Properties Viewing or Changing the Adapter Properties To view or change the properties of the QLogic network adapter In Control Panel, click QLogic Control Suite 4. Click the Advanced section of the Configurations tab.

  • Page 50: Setting Power Management Options

    4–Windows Driver Software Setting Power Management Options Setting Power Management Options You can set power management options to allow the operating system to turn off the controller to save power. If the device is busy doing something (servicing a call, for example) however, the operating system will not shut down the device. The operating system attempts to shut down every possible device only when the computer attempts to go into hibernation.
  • Page 51 4–Windows Driver Software Setting Power Management Options CAUTION Do not select Allow the computer to turn off the device to save power for any adapter that is a member of a team. 83840-546-00 D...

  • Page 52: Linux Driver Software

    Linux Driver Software  Introduction  Limitations  Packaging  Installing Linux Driver Software  Unloading/Removing the Linux Driver  Patching PCI Files (Optional)  Network Installations  Setting Values for Optional Properties  Driver Defaults  Driver Messages  Teaming with Channel Bonding ...

  • Page 53: Introduction

    5–Linux Driver Software Introduction Introduction This section discusses the Linux drivers for the QLogic 8400/3400 Series network adapters. Table 5-1 lists the 8400/3400 Series Linux drivers. For information about iSCSI offload in Linux server, see “iSCSI Offload in Linux Server” on page 208.

  • Page 54: Bnx2X Driver

     Red Hat  kmod-kmp-netxtreme2-{kernel]-version.i686.rpm  kmod-kmp-netxtreme2-{kernel]-version.x86_64.rpm The QLogic Control Suite CLI management utility is also distributed as an RPM package (QCS-{version}.{arch}.rpm). See “Installing on a Linux System” on page 85 for information on installing Linux QCS. 83840-546-00 D...
  • Page 55 5–Linux Driver Software Packaging  Source Packages Identical source files to build the driver are included in both RPM and TAR source packages. The supplemental tar file contains additional utilities such as patches and driver diskette images for network installation. The following is a list of included files: ...

  • Page 56: Installing Linux Driver Software

    5–Linux Driver Software Installing Linux Driver Software Installing Linux Driver Software  Installing the Source RPM Package  Building the Driver from the Source TAR File NOTE If a bnx2x, bnx2i, or bnx2fc driver is loaded and the Linux kernel is updated, the driver module must be recompiled if the driver module was installed using the source RPM or the TAR package.
  • Page 57 5–Linux Driver Software Installing Linux Driver Software For RHEL 6.4 and legacy versions, either of the following: yum install fcoe-utils-<version>.rhel.64.qlgc.<subver>.<arch>.rpm -or- rpm -ivh fcoe-utils-<version>.rhel.64.qlgc.<subver>.<arch>.rpm For SLES11 SP2: rpm -ivh open-fcoe-<version>.sles.sp2.qlgc.<subver>.<arch>.rpm For RHEL 6.4 and SLES11 SP2 and legacy versions, the version of fcoe-utils/open-fcoe included in your distribution is sufficient and no out of box upgrades are provided.
  • Page 58 For SLES, use YaST to configure your Ethernet interfaces to automatically start at boot by setting a static IP address or enabling DHCP on the interface. For FCoE offload and iSCSI-offload-TLV, disable lldpad on QLogic converged network adapter interfaces. This is required because QLogic uses an offloaded DCBX client.

  • Page 59: Installing The Kmp Package

    5–Linux Driver Software Installing Linux Driver Software For SLES12: systemctl restart lldpad For FCOE offload, restart fcoe service to apply new settings For SLES11 SP1, RHEL 6.4, and legacy versions: service fcoe restart For SLES11 SP2: rcfcoe restart For SLES12: systemctl restart fcoe Installing the KMP Package NOTE...

  • Page 60: Load And Run Necessary Iscsi Software Components

    Load and Run Necessary iSCSI Software Components The QLogic iSCSI Offload software suite consists of three kernel modules and a user daemon. Required software components can be loaded either manually or through system services.

  • Page 61: Unloading/Removing The Linux Driver

    5–Linux Driver Software Unloading/Removing the Linux Driver Unloading/Removing the Linux Driver  Unloading/Removing the Driver from an RPM Installation  Removing the Driver from a TAR Installation Unloading/Removing the Driver from an RPM Installation NOTE  The examples used in this procedure refer to the bnx2x driver, but also apply to the bnx2fc and bnx2i drivers.

  • Page 62: Uninstalling Qcs

    5–Linux Driver Software Patching PCI Files (Optional) Uninstalling QCS RPM Package Use the following command: % rpm -e QCS Patching PCI Files (Optional) NOTE The examples used in this procedure refer to the bnx2x driver, but also apply to the bnx2fc and bnx2i drivers. For hardware detection utilities, such as Red Hat kudzu, to properly identify bnx2x supported devices, a number of files containing PCI vendor and device information may need to be updated.

  • Page 63: Setting Values For Optional Properties

    5–Linux Driver Software Setting Values for Optional Properties Setting Values for Optional Properties Optional properties exist for the different drivers:  bnx2x Driver  bnx2i Driver  bnx2fc Driver bnx2x Driver disable_tpa The disable_tpa parameter can be supplied as a command line argument to disable the Transparent Packet Aggregation (TPA) feature.

  • Page 64: Dropless_Fc

    5–Linux Driver Software Setting Values for Optional Properties dropless_fc The dropless_fc parameter can be used to enable a complementary flow control mechanism on 8400/3400 Series adapters. The default flow control mechanism is to send pause frames when the on-chip buffer (BRB) is reaching a certain level of occupancy.

  • Page 65: Pri_Map

    5–Linux Driver Software Setting Values for Optional Properties pri_map The optional parameter pri_map is used to map the VLAN PRI value or the IP DSCP value to a different or same CoS in the hardware. This 32-bit parameter is evaluated by the driver as an 8 value of 4 bits each. Each nibble sets the desired hardware queue number for that priority.

  • Page 66: Bnx2I Driver

    CAUTION Do not use error_mask if you are not sure about the consequences. These values are to be discussed with QLogic development team on a case-by-case basis. This is just a mechanism to work around iSCSI implementation issues on the target side. Without proper knowledge of iSCSI protocol details, users are advised not to experiment with these parameters.

  • Page 67: Sq_Size

    28 connections. Defaults: 128 Range: 32 to 128 Note that QLogic validation is limited to a power of 2; for example, 32, 64, 128. rq_size “Configure RQ size”, used to choose the size of asynchronous buffer queue size per offloaded connections.

  • Page 68: Bnx2Fc Driver

    5–Linux Driver Software Driver Defaults bnx2fc Driver Optional parameter debug_logging can be supplied as a command line arguments to the insmod or modprobe command for bnx2fc. debug_logging "Bit mask to enable debug logging", enables/disables driver debug logging. Defaults: None. For example: insmod bnx2fc.ko debug_logging=0xff modprobe bnx2fc debug_logging=0xff IO level debugging = 0x1...

  • Page 69: Bnx2X Driver

    5–Linux Driver Software Driver Defaults Coalesce RX Frames IRQ: 6 (range is 0–255) Coalesce TX Microseconds: 80 (range is 0–1023) Coalesce TX Microseconds IRQ: 80 (range is 0–1023) Coalesce TX Frames: 20 (range is 0–255) Coalesce TX Frames IRQ: 20 (range is 0–255) Coalesce Statistics Microseconds: 999936 (approximately 1 second) (range is 0–16776960 in increments of 256) MSI: Enabled (if supported by the 2.6 kernel and the interrupt test passes)

  • Page 70: Driver Messages

    NIC Link is Up, 10000 Mbps full duplex Link Down Indication bnx2x: eth# NIC Link is Down MSI-X Enabled Successfully bnx2x: eth0: using MSI-X bnx2i Driver BNX2I Driver Signon QLogic 8400/3400 Series iSCSI Driver bnx2i v2.1.1D (May 12, 20xx) 83840-546-00 D...

  • Page 71: Network Port To Iscsi Transport Name Binding

    5–Linux Driver Software Driver Messages Network Port to iSCSI Transport Name Binding bnx2i: netif=eth2, iscsi=bcm570x-050000 bnx2i: netif=eth1, iscsi=bcm570x-030c00 Driver Completes handshake with iSCSI Offload-enabled CNIC Device bnx2i [05:00.00]: ISCSI_INIT passed NOTE This message is displayed only when the user attempts to make an iSCSI connection.

  • Page 72: Cnic Detects Iscsi Protocol Violation - Fatal Errors

    5–Linux Driver Software Driver Messages CNIC Detects iSCSI Protocol Violation - Fatal Errors bnx2i: iscsi_error - wrong StatSN rcvd bnx2i: iscsi_error - hdr digest err bnx2i: iscsi_error - data digest err bnx2i: iscsi_error - wrong opcode rcvd bnx2i: iscsi_error - AHS len > 0 rcvd bnx2i: iscsi_error - invalid ITT rcvd bnx2i: iscsi_error - wrong StatSN rcvd bnx2i: iscsi_error - wrong DataSN rcvd...

  • Page 73: Cnic Detects Iscsi Protocol Violation - Non-Fatal, Warning

    - MBL 0x800 FBL 0x800MRDSL_I 0x800 MRDSL_T 0x2000 bnx2fc Driver BNX2FC Driver Signon: QLogic NetXtreme II FCoE Driver bnx2fc v0.8.7 (Mar 25, 2011 Driver Compiles Handshake with FCoE Offload Enabled CNIC Device bnx2fc [04:00.00]: FCOE_INIT passed Driver Fails Handshake with FCoE Offload Enabled CNIC Device...

  • Page 74: No Valid License To Start Fcoe

    5–Linux Driver Software Driver Messages No Valid License to Start FCoE bnx2fc: FCoE function not enabled <ethX> bnx2fC: FCoE not supported on <ethX> Session Failures Due to Exceeding Maximum Allowed FCoE Offload Connection Limit or Memory Limits bnx2fc: Failed to allocate conn id for port_id <remote port id> bnx2fc: exceeded max sessions..logoff this tgt bnx2fc: Failed to allocate resources Session Offload Failures...

  • Page 75: Teaming With Channel Bonding

    5–Linux Driver Software Teaming with Channel Bonding Teaming with Channel Bonding With the Linux drivers, you can team adapters together using the bonding kernel module and a channel bonding interface. For more information, see the Channel Bonding information in your operating system documentation. Statistics Detailed statistics and configuration information can be viewed using the ethtool utility.

  • Page 76: Vmware Driver Software

    VMware Driver Software  Packaging  Download, Install, and Update Drivers  Networking Support  FCoE Support Packaging The VMware driver is released in the packaging formats shown in Table 6-1. For information about iSCSI offload in VMware server, see “iSCSI Offload on VMware Server”...

  • Page 77: Download, Install, And Update Drivers

    6–VMware Driver Software Download, Install, and Update Drivers Download, Install, and Update Drivers To download, install, or update the VMware ESXi driver for 8400/3400 Series 10 GbE network adapters, go to http://www.vmware.com/resources/compatibility/search.php?deviceCategory=io and do the following: Type the adapter name (in quotes) in the Keyword window (such as "QLE3442"), and then click Update and View Results (Figure 6-1).

  • Page 78: Pci Identifiers

    6–VMware Driver Software Download, Install, and Update Drivers Mouse over the QLE3442 link in the results section to show the PCI identifiers (Figure 6-3). Figure 6-3. PCI Identifiers Click the model link to show a listing of all of the driver packages (Figure 6-4).

  • Page 79: Download Driver Package

    6–VMware Driver Software Download, Install, and Update Drivers Log in to the VMware driver download page and click Download to download the desired driver package (Figure 6-5). Figure 6-5. Download Driver Package This package is double zipped—unzip the package once before copying the offline bundle zip file to the ESXi host.

  • Page 80: Networking Support

    6–VMware Driver Software Networking Support Networking Support This section describes the bnx2x VMware ESXi driver for the QLogic 8400/3400 Series PCIe 10 GbE network adapters. Driver Parameters Several optional parameters can be supplied as a command line argument to the vmkload_mod command.

  • Page 81: Num_Tx_Queues

    6–VMware Driver Software Networking Support num_tx_queues The optional parameter num_tx_queues may be used to set the number of Tx queues on kernels starting from 2.6.27 when multi_mode is set to 1 and interrupt mode is MSI-X. The number of Rx queues must be equal to or greater than the number of Tx queues (see num_rx_queues parameter).

  • Page 82: Dropless_Fc

    QLogic network adapters. The default flow control mechanism is to send pause frames when the BRB is reaching a certain level of occupancy. This is a performance targeted flow control mechanism. On QLogic network adapters, you can enable another flow control mechanism to send pause frames if one of the host buffers (when in RSS mode) is exhausted.

  • Page 83: Unloading And Removing Driver

    Most systems are set to level 6 by default. To see all messages, set the level higher. Driver Sign On QLogic 8400/3400 Series 10Gigabit Ethernet Driver bnx2x 0.40.15 ($DateTime: 2007/11/22 05:32:40 $) NIC Detected eth0: QLogic 8400/3400 Series XGb (A1) PCI-E x8 2.5GHz found at mem e8800000, IRQ 16, node addr...

  • Page 84: Multiqueue/Netqueue

    CPUs on the machine. FCoE Support This section describes the contents and procedures associated with installation of the VMware software package for supporting QLogic FCoE C-NICs. Enabling FCoE To enable FCoE hardware offload on the C-NIC Determine the ports that are FCoE-capable:...
  • Page 85 NOTE The label Software FCoE is a VMware term used to describe initiators that depend on the inbox FCoE libraries and utilities. QLogic's FCoE solution is a fully state connection-based hardware offload solution designed to significantly reduce the CPU burden encumbered by a non-offload software initiator.

  • Page 86: Installation Check

    (for L2 networking) and on behalf of the bnx2fc (FCoE protocol) and CNIC drivers. bnx2fc The QLogic VMware FCoE driver is a kernel mode driver used to provide a translation layer between the VMware SCSI stack and the QLogic FCoE firmware/hardware. In addition, the driver interfaces...

  • Page 87: Installing Management Applications

     Management Applications (Windows) Overview The QLogic Control Suite (QCS) is a management application for configuring the 8400/3400 Series of converged network adapters and intelligent Ethernet adapters. QCS software operates on Windows and Linux server and client operating systems. This chapter describes how to install the QCS management application.

  • Page 88: Communication Protocols

    7–Installing Management Applications Installation Tasks Communication Protocols A communication protocol enables exchanging information between provider and the client software. These are proprietary or open-source implementations of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) standards from the Distributed Management Task Force (DMTF). Network administrators can choose the best option based on the prevailing standard on their network.

  • Page 89: Ws-Man

    7–Installing Management Applications Installation Tasks WS-MAN The following steps install the WS-MAN protocol for communication between the client and managed host (server). WS-MAN is supported on both Windows and Linux clients and servers. Windows Server On Windows servers, configure the WinRM service as follows: Install the WinRM Software Component on Server.

  • Page 90: Linux Client

    7–Installing Management Applications Installation Tasks Configure OpenPegasus on the Server. Install QLogic CMPI Provider. Perform additional configuration, if required, such as firewall configuration. “Perform Linux Firewall Configuration, If Required” on page Follow the procedure for “Installing QCS and Related Management Applications”...

  • Page 91: Linux Client

    7–Installing Management Applications Detailed Procedures Linux Client To use HTTP, no special configuration is required on the Linux client system. Only the QCS management application must be installed. Perform the following configuration steps: Configure HTTPS on Linux Client. Follow the procedure for “Installing QCS and Related Management Applications”...

  • Page 92: Perform Basic Configuration On The Server

    7–Installing Management Applications Detailed Procedures For Windows XP and Windows Server 2008, install Windows Management Framework Core, which includes WinRM 2.0 and Windows Powershell 2.0, from the following link: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11829 Perform Basic Configuration on the Server The Windows firewall must be enabled for WinRM to work properly. For detailed information about firewall configuration, see “Additional Server Configuration”...
  • Page 93 7–Installing Management Applications Detailed Procedures Under Computer Configuration, open the Administrative Templates folder and then open the Windows Components folder. Select Windows Remote Management (WinRM). Under Windows Remote Management (WinRM), select WinRm Client. Under WinRM Client, double-click Trusted Hosts. In the TrustedHostsList, enter the host names of the clients. If all clients are trusted then enter an asterisk (*) only.

  • Page 94: Perform Https Configuration On The Server (To Use Https Instead Of Http)

    7–Installing Management Applications Detailed Procedures Perform HTTPS Configuration on the Server (to use HTTPS Instead of HTTP) This step consists of two distinct processes: generating a self-signed certificate, if certificate does not exist, and importing it to a Windows server. If one does not already exist, you must configure a self-signed certificate on the Windows server to enable HTTPS/SSL communication with the QCS GUI on the Windows or Linux client.
  • Page 95 State or Province Name (full name) []: California  Locality Name (city) []: Irvine  Organization Name (company) []: QLogic Corporation  Organizational Unit Name (section) []: Engineering  Common Name (your name) []: Enter the host name or IP address of the Windows server.
  • Page 96 To generate a self-signed certificate that is active for 365 days, enter the following command: openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt The following output appears: Signature ok subject=/C=US/ST=California/L=Irvine/O=QLogic Corporation/OU=Engineering/CN=MGMTAPP- LAB3/emailAddress= Getting Private key Enter the following command to verify the generated self-signed certificate. openssl verify server.crt The following output appears: server.crt:/C=US/ST=California/L=Irvine/O=QLogic...
  • Page 97 7–Installing Management Applications Detailed Procedures In Linux, the certificate should have the extension “.pem”. The extension “.crt” and “.pem” are the same, so there is no need to use the openssl command to convert from .crt to .pem. You can simply copy the file as-is. NOTE A separate certificate must be generated for an IPv4 address, IPv6 address, and Hostname.

  • Page 98: Configure Winrm Https/Ssl On The Server

    7–Installing Management Applications Detailed Procedures Right-click on the certificate, and then select Properties to open the MGMTAPP-LAB3 Properties dialog box (Figure 7-1). Figure 7-1. MGMTAPP-LAB3 Dialog Box Ensure that only Server Authentication is enabled, as shown in the figure. Open Trusted Root Certification Authorities and then open Certificates. Follow the instructions from Step 11 Step 17...
  • Page 99 7–Installing Management Applications Detailed Procedures For example, if the certificate is created with a host name, the host name will appear. Double-click the certificate to open it. Click the Details tab. Scroll down and select the Thumbprint field. Select and copy the thumbprint in the Details window so you can insert it in the next step.

  • Page 100: Additional Server Configuration

    7–Installing Management Applications Detailed Procedures Test HTTPS/SSL connection on the server. At the command prompt on the server, enter the following command: winrs -r:https://yourserver:5986 -u:username -p:password hostname If setup correctly, the output of the command shows the server host name. To check WinRM Service Configuration, run the following command: winrm get winrm/config/service Additional Server Configuration...

  • Page 101: Ws-Man-Windows Client

    7–Installing Management Applications Detailed Procedures Useful WinRM Commands Table 7-2 lists some useful WinRM commands. Table 7-2. WinRM Commands Command Description winrm quickconfig or winrm qc Configures WinRM with default settings winrm enumerate Helps to check which service listener are winrm/config/Listener or winrm enabled and listening on which port and IP e winrm/config/Listener...

  • Page 102: Perform Https Configuration (If You Plan To Use Https)

    7–Installing Management Applications Detailed Procedures Enable Allow Basic Authentication and click OK. Run the following command from the command prompt to test the connection: winrm id -remote:<remote machine Hostname or IP Address> Perform HTTPS Configuration (if you plan to use HTTPS) After you generate a self-signed certificate, as described in “Generate a Self-Signed Certificate for Windows/Linux Server”...

  • Page 103: Configure Winrm Https/Ssl

    7–Installing Management Applications Detailed Procedures Configure WinRM HTTPS/SSL You can run winrm from a client to retrieve information from the server using WinRM HTTPS connection. Use the following steps to test the WinRM HTTPS/SSL connection from client: To retrieve the server operating system information, enter the following command.

  • Page 104: Install Openpegasus From The Inbox Rpm (Red Hat Only)

    Note that in inbox Pegasus, HTTP is not enabled by default. After Inbox OpenPegasus is installed successfully, if no further configuration is required, then follow the instructions in “Install QLogic CMPI Provider” on page 79. To enable HTTP, see “Enable HTTP” on page...

  • Page 105: Install Openpegasus From Source (Red Hat And Suse)

    7–Installing Management Applications Detailed Procedures Install OpenPegasus From Source (Red Hat and SuSE) The OpenPegasus source can be downloaded from www.openpegasus.org. NOTE  If not already installed, download and install the openssl and libopenssl-devel rpm. This step is optional and required only if you are planning to use HTTPS to connect the client to the managed host.
  • Page 106 7–Installing Management Applications Detailed Procedures Additional Settings The $PEGASUS_HOME variable must be set up in the shell environment, and $PEGASUS_HOME/bin needs to be appended to the $PATH environment. Examples  export PEGASUS_PLATFORM="LINUX_X86_64_GNU"  export PEGASUS_CIM_SCHEMA="CIM222"  export PEGASUS_ENABLE_CMPI_PROVIDER_MANAGER=true  export PEGASUS_ROOT="/share/pegasus-2.10-src" ...

  • Page 107: Start Cim Server On The Server

    7–Installing Management Applications Detailed Procedures Build and install OpenPegasus From $PEGASUS_ROOT (the location of the Pegasus source root directory), run the following: make clean make make repository NOTE Whenever OpenPegasus is built from source, all configurations are reset to the default values. If you are rebuilding OpenPegasus, you must redo the configuration as described in “Configure OpenPegasus on the Server”...
  • Page 108 Enable Authentication The following OpenPegasus properties have to be set as described in this section. Otherwise, the QLogic CIM Provider will not work properly. Ensure the following are set before launching QCS and connecting to the provider. Start CIM server if it is not already started. Then, set the following: ...

  • Page 109: Install Qlogic Cmpi Provider

    CIM server for the new configuration to take effect. Install QLogic CMPI Provider Ensure that OpenPegasus is installed properly before installing CMPI Provider. Install Enter following command to install QLogic CMPI Provider. % rpm -i QLGC_CMPIProvider-{version}.{arch}.rpm Uninstall Enter following command to uninstall QLogic CMPI Provider:...

  • Page 110: Ws-Man And Cim-Xml-Linux Client

    7–Installing Management Applications Detailed Procedures SuSE Click Compute and then click YaST. Select Security & Users on the left pane. On the right pane, double-click Firewall. Select Custom Rules on the left pane. On the right pane click Add. Enter the following values: ...

  • Page 111: Install Qcs Management Application

    7–Installing Management Applications Detailed Procedures Copy hostname.pem that you created in “Generate a Self-Signed Certificate for Windows/Linux Server” on page 64, into the certificate directory of the Linux client. For example, if the certificate directory is /etc/ssl/certs, copy hostname.pem to /etc/ssl/certs. Change directory to /etc/ssl/certs.

  • Page 112: Set Up Namespace Security Using Wmi Control

    7–Installing Management Applications Detailed Procedures Set up Namespace Security Using WMI Control The WMI Control provides one way to manage namespace security. You can start the WMI Control from the command prompt using this command: wmimgmt On Windows 9x or Windows NT4 computers that have WMI installed, use this command instead: wbemcntl.exe Alternatively, you can access the WMI Control and the Security tab as follows:...

  • Page 113: Grant Dcom Remote Launch And Activate Permission

    7–Installing Management Applications Detailed Procedures Grant DCOM Remote Launch and Activate Permission In the Windows domain environment, the domain administrator account has the necessary privilege level to access the WMI component for QCS management and, therefore, no special configuration is needed. In a large enterprise, however, a user who is accessing the local or remote host using the QCS client GUI may not always have the domain administrator account privilege.

  • Page 114: Special Configuration For Wmi On Different Systems

    7–Installing Management Applications Detailed Procedures In the Permissions for Everyone area (Figure 7-2), select Allow for Remote Launch and Remote Activation, and then click OK. Figure 7-2. Launch and Activation Permission For more information, see Securing a Remote WMI Connection on the Microsoft Developer Network site.

  • Page 115: Installing Qcs And Related Management Applications

    QLogic-provided driver CD or from one of the Windows driver packages available driverdownloads.qlogic.com or by using the silent install option. If you have already installed the QLogic device drivers, then QCS 3 and the related management applications were installed at that time. For information on installing the QCS 3 application, see “Installing QLogic Management Applications”...

  • Page 116: Management Applications (Windows)

    7–Installing Management Applications Management Applications (Windows) To install QCS Download the latest QCS management application RPM package. Install the RPM package using the following command: % rpm -i QCS-{version}.{arch}.rpm To use QCS  To use the GUI, on XWindow, double-click the QCS desktop icon, or access the QCS program from the task bar under System Tools.

  • Page 117: Removing Management Applications

    7–Installing Management Applications Management Applications (Windows) Click Repair to repair errors in installed applications. Click Next to continue. Click Install. Click Finish to close the wizard. Removing Management Applications To remove the management application using the CLI: Enter following command: rpm -e QCS 83840-546-00 D...

  • Page 118: Using Qlogic Control Suite

    QCS operates on Windows and Linux operating systems. ASP, which runs within QLogic Control Suite, is used to configure teams for load balancing, fault tolerance, and virtual local area networks (VLANs). ASP is available only on systems that use at least one QLogic network adapter.

  • Page 119: Starting Qlogic Control Suite

    Starting QLogic Control Suite In Control Panel, click QLogic Control Suite 4, or click the QCS icon in the taskbar located at the bottom of the Windows or Windows Server desktop. On Linux systems, you can double-click the QCS desktop icon, or access the QCS program from the task bar under System Tools.

  • Page 120: Explorer View Pane

    8–Using QLogic Control Suite QCS Interface By default, the Explorer View pane is docked and pinned on the left side of the main window (Figure 8-1), the Context View pane on the right, the Context View selector below the menu bar, and the Description pane below the Context View pane.

  • Page 121: Context View Selector

    8–Using QLogic Control Suite QCS Interface The icon next to each device in the Explorer View pane shows its status. An icon next to a device name that appears normal means the device is connected and working.  X. A red “X” that appears on the device’s icon indicates the device is currently not connected to the network.

  • Page 122: Menu Bar

    Explorer View: Displays/hides the Explorer View pane.  Tool Bar: Displays/hides the tool bar.  Status Bar: Displays/hides the status bar.  QLogic Logo: Displays/hides the QLogic Logo on QCS to optimize the maximum viewable space.  Tools menu  Options: Used for configuring QCS preferences.

  • Page 123: Manage Targets Wizard

    8–Using QLogic Control Suite Configuring Preferences in Windows Manage Targets Wizard The Manage Targets Wizard is available from the iSCSI menu. Follow the prompts in the wizard to add and remove targets, and to login or logout of a target.

  • Page 124: Connecting To A Host

    8–Using QLogic Control Suite Connecting to a Host Setting the Explorer View refresh time in Windows From the Tools menu, select Options. Select Auto to set the Explorer View refresh time to 5 seconds. Otherwise, select Custom and select a time, in seconds.

  • Page 125: Managing The Host

    8–Using QLogic Control Suite Managing the Host Managing the Host At the host level, you can view host information and configure parameters from the following tabs:  Information  Configuration To view host information, select the host in the Explorer View pane, and then...

  • Page 126: Information Tab: Host Information

    Portal List Displays all iSCSI portal IP addresses configured on the selected host. NOTE Some information may not be available for all QLogic network adapters. To configure the host, select the host in the Explorer View pane, and then select the Configuration tab to configure host-level parameters (Figure 8-3).

  • Page 127: Configuration Tab: System Management

    8–Using QLogic Control Suite Managing the Network Adapter Configuration Tab: System Management Chimney Offload State Enable or disable chimney offload at the host level, rather than at the device level, and then click Apply. Configuration Tab: iSCSI Initiator Name The current IQN name is displayed. Click the IQN name to modify the host’s iSCSI initiator name, and then click Apply.

  • Page 128: Viewing Resource Information

    The Resources section of the Information tab displays information about connections and other essential functions for the selected network adapter. NOTE Some information may not be available for all QLogic network adapters. Information Tab: Resources Bus Type The type of input/output (I/O) interconnect used by the adapter.

  • Page 129: Viewing Hardware Information

    Some information may not be available for all QLogic network adapters. Information Tab: Hardware ASIC Version The chip version of the QLogic adapter (this information is not available for adapters made by others). Bootcode Version The version of the boot code. This information is only available for QLogic 8400/3400 Series adapters.

  • Page 130: Managing Ethernet Controller (Port)

    8–Using QLogic Control Suite Managing Ethernet Controller (Port) Managing Ethernet Controller (Port) From QCS, you can group various traffic classes in to priority group and allocate bandwidth to each priority group. When the Ethernet controller is selected in the Object Explorer panel, following four tabs will be displayed in the context view panel: ...

  • Page 131: Viewing Vital Signs

     Information about QLogic network adapters may be more comprehensive than information about network adapters made by others.  Some information may not be available for all QLogic network adapters. Figure 8-5. QCS Vital Signs MAC Address A physical MAC (media access control) address that is assigned to the adapter by the manufacturer.
  • Page 132 Duplex The adapter is operating in the indicated duplex mode. Speed The link speed of the adapter, in megabits per second. Offload Capabilities The offload capabilities supported by the adapter. This information is only available for QLogic 8400/3400 Series adapters.  iSCSI. iSCSI offload for block-level transfer of data.

  • Page 133: Viewing Nic Partitioning Information

    NOTE Some information may not be available for all QLogic network adapters. NIC partitioning divides a QLogic 8400/3400 Series 10 Gigabit Ethernet NIC into multiple virtual NICs by having multiple PCI physical functions per port. Each PCI function is associated with a different virtual NIC. To the OS and the network, each physical function appears as a separate NIC port.

  • Page 134: Testing The Network

    8–Using QLogic Control Suite Managing Ethernet Controller (Port) Maximum Bandwidth (%)  The maximum bandwidth setting defines an upper threshold value, ensuring that this limit will not be exceeded during transmission. The valid range for this value is between 1 and 100. The maximum bandwidth value is defined as a percentage of the physical link speed.

  • Page 135: Qcs—Network Test

    8–Using QLogic Control Suite Managing Ethernet Controller (Port) To run the network test using the QCS GUI Click the name of the adapter to test in the Explorer View pane. From the Select a test to run list, select Network Test (Figure 8-6).

  • Page 136: Running Diagnostic Tests In Windows

    The Diagnostic Tests option on the Diagnostics tab lets you check the state of the physical components on a QLogic network adapter. You can trigger the tests manually, or choose to have QCS continuously perform them. If the test are performed continuously, then the number of passes and fails in the Result field for each test increments every time the tests are performed.
  • Page 137  You must have administrator privileges to run diagnostic tests.  The network connection is temporarily lost while these tests are running.  Some tests are not supported on all QLogic adapters. To run the diagnostic tests once using the QCS GUI:...
  • Page 138 8–Using QLogic Control Suite Managing Ethernet Controller (Port) Interrupt This test verifies that the Network Device Driver Interface Specification (NDIS) driver is able to receive interrupts from the adapter. Loopback MAC and Loopback PHY These tests verify that the NDIS driver is able to send packets to and receive packets from the adapter.

  • Page 139: Analyzing Cables In Windows

     This option is not available for 8400/3400 Series 10GbE network adapters.  This option is not available for all QLogic network adapters. To run a cable analysis using QCS GUI Connect the cable to a port on a switch where the port is set to Auto and the Speed &...

  • Page 140: Qcs—Cable Analysis

    8–Using QLogic Control Suite Managing Ethernet Controller (Port) In the error message window that warns of the network connection being temporarily interrupted, click Yes. Figure 8-7. QCS—Cable Analysis Distance The valid cable length in meters (except when the Noise result is returned).

  • Page 141: Managing The Lan Device

    8–Using QLogic Control Suite Managing the LAN Device  Cable quality. Category 3, 4, 5, and 6 may affect the test results.  Electrical interference. The testing environment may affect the test results. To run a cable analysis using QCS CLI You can use the following CLI commands to run cable analysis for the specified target.

  • Page 142: Viewing Ndis Information

     Information about QLogic network adapters may be more comprehensive than information about network adapters made by others.  Some information may not be available for all QLogic network adapters. Figure 8-8. QCS—NDIS-level Information Viewing Driver Information Information Tab: Driver Information Driver Status The status of the adapter driver.

  • Page 143: Information Tab: Vital Signs

    Permanent MAC Address The unique hardware address assigned to the network adapter. Offload Capabilities The offload capabilities supported by the adapter. This information is only available for QLogic 8400/3400 Series adapters.  iSCSI. iSCSI offload for block-level transfer of data.

  • Page 144: Qcs—Configure Ndis-Level Parameters

     The list of available properties for your adapter may be different.  Some properties may not be available for all QLogic network adapters.  If an adapter is included as a member of a team and you change any advanced property, then you must rebuild the team to ensure that the team’s advanced properties are properly set.
  • Page 145 When you enable the Large Send Offload property, the TCP segmentation can be done by the network adapter. The default setting for this property is Enabled. This property is only available for QLogic 8400/3400 Series adapters. IPv6 Checksum Offload Normally, the checksum function is computed by the protocol stack.
  • Page 146 Ethernet frames that are greater than 1514 bytes, but less than or equal to 9614 bytes in length. This property requires the presence of a switch that is able to process jumbo frames. This property is only available for QLogic 8400/3400 Series adapters.
  • Page 147 8–Using QLogic Control Suite Managing the LAN Device Locally Administered Address The Locally Administered Address is a user-defined MAC address that is used in place of the MAC address originally assigned to the network adapter. Every adapter in the network must have its own unique MAC address.
  • Page 148 8–Using QLogic Control Suite Managing the LAN Device  100 Mb Full. Sets the speed at 100 Mbit/s and the mode to Full-Duplex.  100 Mb Half. Sets the speed at 100 Mbit/s and the mode to Half-Duplex.  1 Gb Full. Sets the speed at 1000 Mb Full-Duplex mode only. Not available for 1 Gb ports.
  • Page 149 Risk Assessment of VLAN Tagging through the NDIS Miniport Driver  QLogic's NDIS 6.0 miniport driver provides the means to allow a system containing a QLogic adapter to connect to a tagged VLAN. On Windows Server systems, this support was only provided through the use of an intermediate driver (ASP).
  • Page 150 DCBX Willing mode, which means that the incoming switch DCBX settings take precedence over the Server QoS service settings if the two are not comparable. To revert to standard QCS control over the QLogic DCB feature set, uninstall the Microsoft QoS service feature (entire host) or disable Quality of Service in the NDIS advance properties page (per port).

  • Page 151: Viewing Resource Information

    The Resources section of the Information tab displays information about connections and other essential functions for the selected network adapter. NOTE Some information may not be available for all QLogic network adapters. Information Tab: Resources Bus Type The type of input/output (I/O) interconnect used by the adapter.

  • Page 152: Viewing Statistics

    Click Refresh to get the most recent values for each statistic. Click Reset to change all values to zero for the current QCS session. NOTE  Team statistics are not compiled for a QLogic network adapter if it is disabled.  Some statistics may not be available for all QLogic network adapters.

  • Page 153: General Statistics

    8–Using QLogic Control Suite Viewing Resource Information General Statistics General Statistics show the transmitted and received statistics to and from the adapter. Frames Tx OK A count of the frames that were successfully transmitted. This counter is incremented when the transmit status is reported as Transmit OK.
  • Page 154 8–Using QLogic Control Suite Viewing Resource Information Login Authentication Failed Responses The number of login requests that failed due to party authentication failure. Login target authentication failure The number of instances where the login could not authenticate the target. Login target negotiation failure The number of instances where the login could not negotiate the sessions parameters.

  • Page 155: Ieee 802.3 Statistics

    Custom Statistics NOTE Custom statistics are available only for an enabled QLogic network adapter. Out of Recv. Buffer The number of times the adapter ran out of Receive Buffer Descriptors. This information is only available for QLogic 8400/3400 Series adapters.

  • Page 156: Viewing Resource Reservations

    License keys are installed on the motherboard for use with LOMs and are preprogrammed in add-in NICs. To view resource reservations Click the name of the QLogic 8400/3400 Series system device in the Explorer View pane. From the Resource Reservations section, open the wizard by selecting the Configure button.

  • Page 157: Maximum Number Of Offload Connections

    8–Using QLogic Control Suite Viewing Resource Information To configure resource reservations Select Reserved Resources for the Offload Configuration setting. Reservations allocate the minimum number of connections per technology. Table 8-1 for the maximum number of connections available for various configurations.

  • Page 158: Configuring The Ip Address For Iscsi Offload

     Not all offload technologies are available with all adapters. The Licenses section shows the number of connections available for iSCSI FCoE offload technologies. To view licenses Click the name of the QLogic 8400 Series system device in the Explorer View pane. 83840-546-00 D...

  • Page 159: Configuring Teaming

    LiveLink mitigates such issues.  ASP is available only if a system has one or more QLogic network adapters installed.  To physically remove a teamed NIC from a system, you must first delete the NIC from the team.

  • Page 160: Team Types

    Smart Load Balance and Failover type teams in the Teaming Wizard. NOTE 8400 Series network adapter ports with iSCSI-Offload enabled can coexist only with SLB type teams. Ports with FCoE-Offload enabled can coexist with SLB teams and with some switch vendor LACP teams.

  • Page 161: Slb (Auto-Fallback Disable)

    8–Using QLogic Control Suite Configuring Teaming SLB (Auto-Fallback Disable) This team is identical to Smart Load Balance and Failover, with the following exception: when the standby member is active, if a primary member comes back online, the team continues using the standby member rather than switching back to the primary member.

  • Page 162: Using The Qlogic Teaming Wizard

    8–Using QLogic Control Suite Configuring Teaming Using the QLogic Teaming Wizard You can use the QLogic Teaming Wizard to create a team, configure an existing team if a team has already been created, or create a VLAN. Create or edit a team: To create a new team, select Create a Team from the Team menu, or right-click one of the devices in the “Unassigned Adapters”...

  • Page 163: Entering A Team Name

    8–Using QLogic Control Suite Configuring Teaming Type the team name and then click Next (Figure 8-12). If you want to review or change any of your settings, click Back. Click Cancel to discard your settings and exit the wizard. The team name cannot exceed 39 characters, cannot begin with spaces, and cannot contain any of the following characters: &...

  • Page 164: Configuring The Team Type

    OK, and continue. NOTE 8400 Series network adapters with iSCSI or FCoE enabled can coexist with SLB team types. FCoE can also coexist with some vendors’ switches LACP teaming mode.To continue with the creation of...

  • Page 165: Adding An Adapter To A Team

    8–Using QLogic Control Suite Configuring Teaming The Large Send Offload (LSO) and Checksum Offload (CO) columns indicate if the LSO, Jumbo MTU, and/or the CO properties are supported for the adapter. The LSO, Jumbo MTU, and CO properties are enabled for a team only when all of the members support and are configured for the feature.

  • Page 166: Configure Auto-Fallback Disable

    8–Using QLogic Control Suite Configuring Teaming The Auto-Fallback Disable mode feature allows the team to continue using the standby member rather than switching back to the primary member if the primary member comes back online. To enable this feature, select Enable...
  • Page 167 8–Using QLogic Control Suite Configuring Teaming Select the probe interval (the number of seconds between each retransmission of a link packet to the probe target) and the maximum number of probe retries (the number of consecutively missed responses from a probe target before a failover is triggered).

  • Page 168: Adding A Vlan

    The benefit of this is that your system can have one network adapter that can belong to multiple subnets. NOTE VLANs can only be created when all team members are QLogic adapters. Figure 8-17. Adding a VLAN 83840-546-00 D...

  • Page 169: Naming The Vlan

    8–Using QLogic Control Suite Configuring Teaming Type the VLAN name and then click Next (Figure 8-18). The VLAN name cannot exceed 39 characters, cannot begin with spaces, and cannot contain any of the following characters: & \ / : * ? < > | .

  • Page 170: Entering A Vlan Tag Value

    8–Using QLogic Control Suite Configuring Teaming Type the VLAN tag value and then click Next (Figure 8-20). The value must be between 1 and 4,094. Figure 8-20. Entering a VLAN Tag Value Select Yes to add or manage another VLAN and then click Next. Repeat until you do not want to add or manage any additional VLANs.

  • Page 171: Commit Changes And Exit The Teaming Wizard

    Finish (Figure 8-21). Figure 8-21. Commit Changes and Exit the Teaming Wizard At any point in the QLogic Teaming Wizard procedure, click Preview to get a visual representation of what the team will look like before committing any changes (Figure 8-22).

  • Page 172: Using Expert Mode

    Use Expert Mode to create a team, modify a team, add a VLAN, and configure LiveLink for a Smart Load Balance and Failover and SLB (Auto-Fallback Disable) team. To create a team using the wizard, see “Using the QLogic Teaming Wizard” on page 132.

  • Page 173: Creating A Team

    8–Using QLogic Control Suite Configuring Teaming Creating a Team NOTE Enabling Dynamic Host Configuration Protocol (DHCP) is not recommended for members of an SLB type of team. From the Teams menu, select Create a Team, or right-click one of the devices in the “Unassigned Adapters”...
  • Page 174 You can assign any other available adapter to be a standby member by selecting it from the Standby Member list. NOTE  There must be at least one QLogic network adapter assigned to the team.  A team created with a single adapter will not have load balancing or failover capabilities.
  • Page 175 8–Using QLogic Control Suite Configuring Teaming Repeat steps through to define additional teams. As teams are defined, they can be selected from the team list, but they have not yet been created. Click the Preview tab to view the team structure before applying the changes.

  • Page 176: Modifying A Team

    8–Using QLogic Control Suite Configuring Teaming On the General tab, click Internet Protocol (TCP/IP), and then click Properties. Configure the IP address and any other necessary TCP/IP configuration for the team, and then click OK when finished. Modifying a Team After you have created a team, you can modify the team in the following ways: ...

  • Page 177: Adding A Vlan

    You can define up to 64 VLANs per team (63 VLANs that are tagged and 1 VLAN that is not tagged). VLANs can only be created when all teams members are QLogic adapters. If you try to create a VLAN with a non-QLogic adapter, an error message is displayed.

  • Page 178: Expert Mode—Create A Team With A Vlan

    8–Using QLogic Control Suite Configuring Teaming To configure a team with a VLAN From the Teams menu, select Add VLAN. The Welcome screen appears. Click Expert Mode. On the Create Team tab of the Manage Teams window, click Manage VLAN(s).

  • Page 179: Viewing Vlan Properties And Statistics And Running Vlan Tests

    8–Using QLogic Control Suite Configuring Teaming Viewing VLAN Properties and Statistics and Running VLAN Tests To view VLAN properties and statistics and to run VLAN tests Select one of the listed VLANs. Click the Information tab to view the properties of the VLAN adapter.
  • Page 180 To configure LiveLink From the Teams menu, select Edit Team. Click Expert Mode (to configure LiveLink using the Teaming Wizard, see “Using the QLogic Teaming Wizard” on page 132). In the Manage Teams window, click the Edit Team tab. Select Enable LiveLink. The LiveLink Configuration options appear below.

  • Page 181: Saving And Restoring A Team Configuration

    8–Using QLogic Control Suite Configuring Teaming Click Update. Repeat these steps for each of the other listed team members. Click Apply/Exit. Saving and Restoring a Team Configuration To save a configuration From the File menu, select Team Save As. Type the path and file name of the new configuration file, and then click Save.

  • Page 182: Viewing Asp Statistics

    Utility An alternate method to QCS for configuring QLogic network adapters is with QCS CLI, which is a QLogic utility that allows you to view information and configure network adapters using a console in either a non-interactive command line interface (CLI) mode or an interactive mode. As with QCS, QCS CLI provides information about each network adapter, and enables you to perform detailed tests, run diagnostics, view statistics, and modify property values.

  • Page 183: Firmware Upgrade

    Firmware Upgrade QLogic provides a Windows and Linux utility for upgrading adapter firmware and bootcode. Each utility executes as a console application that can be run from a command prompt. Upgrade VMware firmware with the VMware vSphere plugin. Upgrading Firmware for Windows...
  • Page 184 C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 16A1 000E1E508E20 Yes [0061] QLogic 57840 10 Gigabit Ethernet #61 1 16A1 000E1E508E22 Yes [0062] QLogic 57840 10 Gigabit Ethernet #62 Upgrading MFW Forced upgrading MFW1 image: from ver MFW1 7.10.39 to ver MFW1 7.12.31 Upgrading MFW2 image to version MFW2 7.12.31...
  • Page 185 C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 16A1 000E1E508E20 Yes [0061] QLogic 57840 10 Gigabit Ethernet #61 1 16A1 000E1E508E22 Yes [0062] QLogic 57840 10 Gigabit Ethernet #62 Upgrading MBA Updating PCI ROM header with Vendor ID = 0x14e4 Device ID = 0x16a1 Updating PCI ROM header with Vendor ID = 0x14e4 Device ID = 0x16a1 Forced upgrading MBA image: from ver PCI30 MBA 7.11.3 ;EFI x64 7.10.54 to ver...
  • Page 186 C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 16A1 000E1E508E20 Yes [0061] QLogic 57840 10 Gigabit Ethernet #61 1 16A1 000E1E508E22 Yes [0062] QLogic 57840 10 Gigabit Ethernet #62 Upgrading L2T Forced upgrading L2T image: from ver L2T 7.10.31 to ver L2T 7.10.31 Forced upgrading L2C image: from ver L2C 7.10.31 to ver L2C 7.10.31...

  • Page 187: Upgrading Firmware For Linux

    Linux firmware upgrade utility for your adapter. In a Linux command line window, type the following command: # ./LnxQlgcUpg.sh ****************************************************************************** QLogic Firmware Upgrade Utility for Linux v2.7.13 ****************************************************************************** C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 1639 0026B942B53E Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em1)
  • Page 188 9–Firmware Upgrade Upgrading Firmware for Linux C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 1639 0026B942B53E Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em1) 1 1639 0026B942B540 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em2) 2 1639 0026B942B542 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em3) 3 1639 0026B942B544 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em4) 4 16A1 000E1E503150 Yes BCM57840 NetXtreme II 10 Gigabit Ethernet rev 11 (p1p1) 5 16A1 000E1E503152 Yes BCM57840 NetXtreme II 10 Gigabit Ethernet rev 11 (p1p2)
  • Page 189 9–Firmware Upgrade Upgrading Firmware for Linux ****************************************************************************** QLogic Firmware Upgrade Utility for Linux v2.7.13 ****************************************************************************** C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 1639 0026B942B53E Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em1) 1 1639 0026B942B540 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em2)
  • Page 190 9–Firmware Upgrade Upgrading Firmware for Linux ****************************************************************************** QLogic Firmware Upgrade Utility for Linux v2.7.13 ****************************************************************************** C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 1639 0026B942B53E Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em1) 1 1639 0026B942B540 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em2)
  • Page 191 9–Firmware Upgrade Upgrading Firmware for Linux NIC is not supported. C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 1639 0026B942B53E Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em1) 1 1639 0026B942B540 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em2) 2 1639 0026B942B542 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em3) 3 1639 0026B942B544 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em4) 4 16A1 000E1E503150 Yes BCM57840 NetXtreme II 10 Gigabit Ethernet rev 11 (p1p1)
  • Page 192 9–Firmware Upgrade Upgrading Firmware for Linux ****************************************************************************** QLogic Firmware Upgrade Utility for Linux v2.7.13 ****************************************************************************** C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 1639 0026B942B53E Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em1) 1 1639 0026B942B540 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em2)
  • Page 193 9–Firmware Upgrade Upgrading Firmware for Linux ****************************************************************************** QLogic Firmware Upgrade Utility for Linux v2.7.13 ****************************************************************************** C Brd Name - ---- ------------ --- ------------------------------------------------------ 0 1639 0026B942B53E Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em1) 1 1639 0026B942B540 Yes PowerEdge R710 BCM5709 Gigabit Ethernet rev 20 (em2)

  • Page 194: Iscsi Protocol

    For both Windows and Linux operating systems, iSCSI boot can be configured to boot with two distinctive paths: non-offload (also known as Microsoft/Open-iSCSI initiator) and offload (QLogic’s offload iSCSI driver or HBA). Configuration of the path is set with the HBA Boot Mode option located on the General Parameters screen of the iSCSI Configuration utility.

  • Page 195: Iscsi Boot Setup

    Target LUN  Initiator IQN  CHAP ID and secret Configuring iSCSI Boot Parameters Configure the QLogic iSCSI boot software for either static or dynamic configuration. Refer to Table 10-1 for configuration options available from the General Parameters screen. 83840-546-00 D...

  • Page 196: Configuration Options

    10–iSCSI Protocol iSCSI Boot Table 10-1 lists parameters for both IPv4 and IPv6. Parameters specific to either IPv4 or IPv6 are noted. NOTE Availability of IPv6 iSCSI boot is platform/device dependent. Table 10-1. Configuration Options Option Description TCP/IP parameters via This option is specific to IPv4.

  • Page 197: Mba Boot Protocol Configuration

    Set to disable when the host OS is configured for software initiator mode and to enable for HBA mode. This option is available only on 8400 Series adapters. This parameter can- not be changed when the adapter is in Multi-Function mode.

  • Page 198: Ccm Device List

    10–iSCSI Protocol iSCSI Boot In the CCM device list (Figure 10-2), use the up or down arrow keys to select a device, and then press ENTER. Figure 10-2. CCM Device List In the Main menu, select MBA Configuration (Figure 10-3), and then press ENTER.

  • Page 199: Iscsi Boot Configuration

    10–iSCSI Protocol iSCSI Boot In the MBA Configuration menu (Figure 10-4), use the up or down arrow keys to select Boot Protocol. Use the left or right arrow keys to change the boot protocol option to iSCSI. Press ENTER. Figure 10-4. Selecting the iSCSI Boot Protocol NOTE If iSCSI boot firmware is not programmed in the 8400/3400 Series network adapter, the iSCSI Boot Configuration option will not be...

  • Page 200: Selecting Iscsi Boot Configuration

    10–iSCSI Protocol iSCSI Boot To configure the iSCSI boot parameters using static configuration: In the Main menu, select iSCSI Boot Configuration (Figure 10-5), and then press ENTER. Figure 10-5. Selecting iSCSI Boot Configuration In the iSCSI Boot Main menu, select General Parameters (Figure 10-6), and then press ENTER.
  • Page 201 10–iSCSI Protocol iSCSI Boot  IP Version: As Required (IPv6, non-offload)  HBA Boot Mode: As required NOTE For initial OS installation to a blank iSCSI target LUN from a CD/DVD-ROM or mounted bootable OS installation image, set Boot to iSCSI Target to One Time Disabled.

  • Page 202: Saving The Iscsi Boot Configuration

    10–iSCSI Protocol iSCSI Boot In the 1st Target Parameters menu, enable Connect to connect to the iSCSI target. Type values for the following parameters for the iSCSI target, and then press ENTER:  IP Address  TCP Port  Boot LUN ...
  • Page 203 Initiator Parameters screen. If no value was selected, then the controller defaults to the name: iqn.1995-05.com.qlogic.<11.22.33.44.55.66>.iscsiboot where the string 11.22.33.44.55.66 corresponds to the controller’s MAC address. If DHCP option 43 (IPv4 only) is used, then any settings on the Initiator Parameters, 1st Target Parameters, or 2nd Target Parameters screens are ignored and do not need to be cleared.

  • Page 204: Enabling Chap Authentication

    10–iSCSI Protocol iSCSI Boot  DHCP Vendor ID: As Required  Link Up Delay Time: As Required  Use TCP Timestamp: As Required  Target as First HDD: As Required  LUN Busy Retry Count: As Required  IP Version: As Required ...

  • Page 205: Configuring The Dhcp Server To Support Iscsi Boot

    DHCP iSCSI Boot Configuration for IPv6 DHCP iSCSI Boot Configurations for IPv4 The DHCP protocol includes a number of options that provide configuration information to the DHCP client. For iSCSI boot, QLogic adapters support the following DHCP configurations:  DHCP Option 17, Root Path ...

  • Page 206: Dhcp Option 43 Suboption Definition

    The target name in either IQN or EUI format (refer to RFC 3720 for details on both IQN and EUI formats). An example IQN name would be “iqn.1995-05.com.QLogic:iscsi-target”. DHCP Option 43, Vendor-Specific Information DHCP option 43 (vendor-specific information) provides more configuration options to the iSCSI client than DHCP option 17.

  • Page 207: Dhcp Iscsi Boot Configuration For Ipv6

     DHCPv6 Option 17, Vendor-Specific Information NOTE The DHCPv6 standard Root Path option is not yet available. QLogic suggests using Option 16 or Option 17 for dynamic iSCSI Boot IPv6 support. DHCPv6 Option 16, Vendor Class Option DHCPv6 Option 16 (vendor class option) must be present and must contain a string that matches your configured DHCP Vendor ID parameter.

  • Page 208: Configuring The Dhcp Server

    3315. Preparing the iSCSI Boot Image  Windows Server 2008 R2 and SP2 iSCSI Boot Setup  Windows Server 2012/2012 R2 iSCSI Boot Setup  Linux iSCSI Boot Setup  Injecting (Slipstreaming) QLogic Drivers into Windows Image Files 83840-546-00 D...
  • Page 209 Load the latest QLogic MBA and iSCSI boot images onto NVRAM of the adapter. Configure the BIOS on the remote system to have the QLogic MBA as the first bootable device, and the CDROM as the second device. Configure the iSCSI target to allow a connection from the remote device.
  • Page 210 Windows Server 2012/2012 R2 iSCSI Boot Setup Windows Server 2012/2012 R2 supports booting and installing in either the offload or non-offload paths. QLogic requires the use of a “slipstream” DVD with the latest QLogic drivers injected. See “Injecting (Slipstreaming) QLogic Drivers into Windows Image Files”...
  • Page 211 Remove any local hard drives on the system to be booted (the “remote system”). Load the latest QLogic MBA and iSCSI boot images into the NVRAM of the adapter. Configure the BIOS on the remote system to have the QLogic MBA as the first bootable device and the CDROM as the second device.
  • Page 212 Note that SLES 10.x and SLES 11 have support only for the non-offload path. For driver update, obtain the latest QLogic Linux driver CD. Configure the iSCSI Boot Parameters for DVD direct install to target by disabling the Boot from target option on the network adapter.
  • Page 213 10–iSCSI Protocol iSCSI Boot (RHEL) Choose to “skip” media testing. Continue installation as desired. A drive will be available at this point. After file copying is done, remove CD/DVD and reboot the system. When the system reboots, enable “boot from target” in iSCSI Boot Parameters and continue with installation until it is done.
  • Page 214 10–iSCSI Protocol iSCSI Boot For IPv6, you can now change the IP address for both the initiator and the target to the desired IPv6 address in the NVRAM configuration. SUSE 11.1 Remote DVD installation workaround Create a new file called boot.open-iscsi with the content shown below. Copy the file you just created to /etc/init.d/ folder and overwrite the existing one.
  • Page 215 10–iSCSI Protocol iSCSI Boot Content of the new boot.open-iscsi file: #!/bin/bash # /etc/init.d/iscsi ### BEGIN INIT INFO # Provides: iscsiboot # Required-Start: # Should-Start: boot.multipath # Required-Stop: # Should-Stop: $null # Default-Start: # Default-Stop: # Short-Description: iSCSI initiator daemon root-fs support # Description: Starts the iSCSI initiator daemon if the root-filesystem is on an iSCSI device...
  • Page 216 10–iSCSI Protocol iSCSI Boot iscsi_mark_root_nodes() $ISCSIADM -m session 2> /dev/null | while read t num i target ; ip=${i%%:*} STARTUP=`$ISCSIADM -m node -p $ip -T $target 2> /dev/null | grep "node.conn\[0\].startup" | cut -d' ' -f3` if [ "$STARTUP" -a "$STARTUP" != "onboot" ] ; then $ISCSIADM -m node -p $ip -T $target -o update -n node.conn[0].startup -v onboot done...

  • Page 217: Booting

    "Usage: $0 {start|stop|status|restart|reload}" exit 1 esac rc_exit Injecting (Slipstreaming) QLogic Drivers into Windows Image Files See these instructions in the FCoE topic. Booting After that the system has been prepared for an iSCSI boot and the operating system is present on the iSCSI target, the last step is to perform the actual boot.

  • Page 218: Configuring Vlans For Iscsi Boot

    Layer-2 VLAN to segregate it from general traffic. When this is the case, make the iSCSI interface on the adapter a member of that VLAN. During a boot of the Initiator system, press CTRL+S to open the QLogic CCM pre-boot utility (Figure 10-8).

  • Page 219: Other Iscsi Boot Considerations

    10–iSCSI Protocol iSCSI Boot In the MBA Configuration menu (Figure 10-11), use the up or down arrow keys to select each of following parameters.  VLAN Mode: Press ENTER to change the value to Enabled  VLAN ID: Press ENTER to open the VLAN ID dialog, type the target VLAN ID (1–4096), and then press ENTER.

  • Page 220: Virtual Lans

    Ensure that all Runlevels of network service are on. Ensure that the 2, 3, and 5 Runlevels of iSCSI service are on. Update iscsiuio. You can get the iscsiuio package from the QLogic CD. This step is not needed for SuSE 10.

  • Page 221: Troubleshooting Iscsi Boot

    IPv6 address and the target configured using a router-configured IPv6 address. Solution: This is a known Windows TCP/IP stack issue. Problem: The QLogic iSCSI Crash Dump utility will not work properly to capture a memory dump when the link speed for iSCSI boot is configured for 10 Mbps or 100 Mbps.

  • Page 222: Iscsi Crash Dump

    SFP+ defaults to 10 Gbps operation and does not support autonegotiation. iSCSI Crash Dump If you will use the QLogic iSCSI Crash Dump utility, it is important to follow the installation procedure to install the iSCSI Crash Dump driver. See “Using the Installer”...

  • Page 223: Iscsi Offload In Windows Server

    Configuring iSCSI Offload With the proper iSCSI offload licensing, you can configure your iSCSI-capable 8400 Series network adapter to offload iSCSI processing from the host processor. The following process enables your system to take advantage of QLogic’s iSCSI offload feature.

  • Page 224: Installing Qlogic Drivers And Management Applications

    Microsoft, go to http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=18986 and locate the direct link for your system. Configuring QLogic iSCSI Using QCS QCS is used to manage all of QLogic’s network adapters and advanced features. For more information, see Chapter Open QCS.

  • Page 225: Iscsi View

    10–iSCSI Protocol iSCSI Offload in Windows Server This section describes VLAN configuration on Windows Server 2012 R2 using the QCS GUI. (You can also use the QCS CLI; see the CLI release notes in your software distribution for command information.) Open QCS and select iSCSI VIEW from the Filter drop-down list (Figure 10-13).

  • Page 226: Selecting The Iscsi Adapter

    10–iSCSI Protocol iSCSI Offload in Windows Server Select the iSCSI adapter for the port, as shown in Figure 10-14. Figure 10-14. Selecting the iSCSI Adapter 83840-546-00 D...

  • Page 227: Specifying A Vlan Id

    10–iSCSI Protocol iSCSI Offload in Windows Server Click the Configuration tab and enter a VLAN ID (Figure 10-15). If DHCP is enabled, changing the VLAN ID initiates a new request for an IP address from the DHCP server. If DHCP is disabled, manually update the IP Address, Subnet Mask and Default Gateway for the iSCSI adapter.

  • Page 228: Configure Microsoft Initiator To Use Qlogic's Iscsi Offload

    Now that the IP address has been configured for the iSCSI adapter, you need to use Microsoft Initiator to configure and add a connection to the iSCSI target using QLogic iSCSI adapter. See Microsoft’s user guide for more details on Microsoft Initiator.

  • Page 229: Iscsi Initiator—Add A Target Portal

    10–iSCSI Protocol iSCSI Offload in Windows Server Select the Discovery tab (Figure 10-18), and click Add to add a target portal. Figure 10-18. iSCSI Initiator—Add a Target Portal Enter the IP address of the target and click Advanced (Figure 10-19). Figure 10-19.

  • Page 230: Selecting The Local Adapter

    10–iSCSI Protocol iSCSI Offload in Windows Server From the General tab, select QLogic 10 Gigabit Ethernet iSCSI Adapter for the local adapter (Figure 10-20). Figure 10-20. Selecting the Local Adapter Select the adapter IP address for the Initiator IP, and then click OK (Figure 10-21).

  • Page 231: Adding The Target Portal

    10–iSCSI Protocol iSCSI Offload in Windows Server In the iSCSI Initiator Properties dialog box (Figure 10-22), click OK to add the target portal. Figure 10-22. Adding the Target Portal 83840-546-00 D...

  • Page 232: Logging On To The Iscsi Target

    10-24), click Advanced..Figure 10-24. Log On to Target Dialog Box On the General tab, select QLogic 10 Gigabit Ethernet iSCSI Adapter for the local adapter, and then click OK to close Advanced settings. Click OK to close the Microsoft Initiator.

  • Page 233: Iscsi Offload Faqs

    Offload FAQs Q: How do I assign an IP address for iSCSI offload? A: Use the Configurations tab in QLogic Control Suite (QCS). Q: What tools should be used to create the connection to the target? A: Use Microsoft iSCSI Software Initiator (version 2.08 or later).
  • Page 234 10–iSCSI Protocol iSCSI Offload in Windows Server Table 10-5. Offload iSCSI (OIS) Driver Event Log Messages Message Severity Message Number Error Maximum command sequence number is not serially greater than expected command sequence number in login response. Dump data contains Expected Command Sequence number followed by Maximum Command Sequence number.
  • Page 235 10–iSCSI Protocol iSCSI Offload in Windows Server Table 10-5. Offload iSCSI (OIS) Driver Event Log Messages Message Severity Message Number Error CHAP Response given by the target did not match the expected one. Dump data contains the CHAP response. Error Header Digest is required by the initiator, but target did not offer it.
  • Page 236 10–iSCSI Protocol iSCSI Offload in Windows Server Table 10-5. Offload iSCSI (OIS) Driver Event Log Messages Message Severity Message Number Information A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name.
  • Page 237 10–iSCSI Protocol iSCSI Offload in Windows Server Table 10-5. Offload iSCSI (OIS) Driver Event Log Messages Message Severity Message Number Error Target failed to respond in time to a logout request sent in response to an asynchronous message from the target. Error Initiator Service failed to respond in time to a request to con- figure IPSec resources for an iSCSI connection.

  • Page 238: Iscsi Offload In Linux Server

    Offload in Linux Server  Open iSCSI User Applications  User Application - qlgc_iscsiuio  Bind iSCSI Target to QLogic NX2 iSCSI Transport Name  VLAN Configuration for iSCSI Offload (Linux)  Making Connections to iSCSI Targets  Maximum Offload iSCSI Connections ...

  • Page 239: User Application - Qlgc_Iscsiuio

    # qlgc_iscsiuio -v Start brcm_iscsiuio # qlgc_iscsiuio Bind iSCSI Target to QLogic NX2 iSCSI Transport Name In Linux, each iSCSI port is an interface known as iface. By default, the open-iscsi daemon connects to discovered targets using a software initiator (transport name = tcp) with the iface name default.

  • Page 240: Vlan Configuration For Iscsi Offload (Linux)

    Iface.port = 0 #END Record NOTE Although not strictly required, QLogic recommends configuring the same VLAN ID on the iface.iface_num field for iface file identification purposes. Setting the VLAN ID on the Ethernet Interface If using RHEL5.X versions of Linux, it is recommended that you configure the iSCSI VLAN on the Ethernet interface.

  • Page 241: Making Connections To Iscsi Targets

    This is a sample list of commands to discovery targets and to create iscsi connections to a target. Add Static Entry iscsiadm -m node -p <ipaddr[:port]> -T iqn.2007-05.com.qlogic:target1 -o new -I <iface_file_name> iSCSI Target Discovery Using 'SendTargets' iscsiadm -m discovery --type sendtargets -p <ipaddr[:port]> -I <iface_file_name>...

  • Page 242: List All Sessions

     In the scenario where multiple CNIC devices are in the system and the system is booted with QLogic’s iSCSI boot solution, ensure that the iscsi node under /etc/iscsi/nodes for the boot target is bound to the NIC that is used for booting.

  • Page 243: Assigning A Vlan Number

    Offload on VMware Server Similar to bnx2fc, bnx2i is a kernel mode driver used to provide a translation layer between the VMware SCSI stack and the QLogic iSCSI firmware/hardware. Bnx2i functions under the open-iscsi framework. iSCSI traffic on the network may be isolated in a VLAN to segregate it from other traffic.

  • Page 244: Configuring The Vlan On Vmkernel

    10–iSCSI Protocol iSCSI Offload on VMware Server Configure the VLAN on VMKernel (Figure 10-26). Figure 10-26. Configuring the VLAN on VMKernel 83840-546-00 D...

  • Page 245: Overview

    (NAS), management, IPC, and storage, are used to achieve the desired performance and versatility. In addition to iSCSI for storage solutions, FCoE can now be used with capable QLogic C-NICs. FCoE is a standard that allows Fibre Channel protocol to be transferred over Ethernet by preserving existing Fibre Channel infrastructures and capital investments by classifying received FCoE and FIP frames.

  • Page 246: Fcoe Boot From San

    Preparing System BIOS for FCoE Build and Boot Modify System Boot Order The QLogic initiator must be the first entry in the system boot order. The second entry must be the OS installation media. It is important that the boot order be set correctly or else the installation will not proceed correctly.

  • Page 247: Prepare Qlogic Multiple Boot Agent For Fcoe Boot

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Prepare QLogic Multiple Boot Agent for FCoE Boot During POST, press CTRL+S at the QLogic Ethernet Boot Agent banner to invoke the CCM utility. Select the device through which boot is to be configured ().

  • Page 248: Fcoe Boot—Enable Dcb/Dcbx

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Ensure DCB/DCBX is enabled on the device (Figure 11-2). FCoE boot is only supported on DCBX capable configurations. As such, DCB/DCBX must be enabled, and the directly attached link peer must also be DCBX capable with parameters that allow for full DCBX synchronization.

  • Page 249: Fcoe Boot—Target Information

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Configure the desired boot target and LUN. From the Target Information Menu (Figure 11-4), select the first available path. Figure 11-4. FCoE Boot<Variable>—Target Information 83840-546-00 D...

  • Page 250: Fcoe Boot—Specify Target Wwpn And Boot Lun

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Enable the Connect field. Enter the target WWPN and Boot LUN information for the target to be used for boot (Figure 11-5). Figure 11-5. FCoE Boot<Variable>—Specify Target WWPN and Boot LUN Figure 11-6. FCoE Boot Target Information Press ESC until prompted to exit and save changes.

  • Page 251: Uefi Boot Lun Scanning

    11–Fibre Channel Over Ethernet FCoE Boot from SAN UEFI Boot LUN Scanning UEFI boot LUN scanning eases the task of configuring FCoE boot from SAN by allowing you to choose from a list of targets and selecting a WWPN instead of typing the WWPN.

  • Page 252: Fcoe Target Parameters Window

    11–Fibre Channel Over Ethernet FCoE Boot from SAN In the FCoE Target Parameters window, there are eight target entries in which you can enable the target (Connect n), select or type a WWPN (WWPN n), and type a boot LUN number (Boot LUN n) (Figure 11-8).

  • Page 253: Provisioning Storage Access In The San

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Provisioning Storage Access in the SAN Storage access consists of zone provisioning and storage selective LUN presentation, each of which is commonly provisioned per initiator WWPN. Two main paths are available for approaching storage access: ...

  • Page 254: One-Time Disabled

    224. One-Time Disabled QLogic's FCoE ROM is implemented as Boot Entry Vector (BEV). In this implementation, the Option ROM only connects to the target once it has been selected by BIOS as the chosen boot device. This is different from other implementations that will connect to the boot device even if another device has been selected by the system BIOS.

  • Page 255: One-Time Disabled

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Wait through all option ROM banners. Once FCoE boot is invoked, it will connect to the target, and provide a four second window to press CTRL+D to invoke the bypass. Press CTRL+D to proceed to installation. Figure 11-10.

  • Page 256: Fcoe Boot Installation

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Windows Server 2008 R2 and Windows Server 2008 SP2 FCoE Boot Installation Ensure that no USB flash drive is attached before starting the OS installer. The EVBD and OFC/BXFOE drivers need to be loaded during installation. Go through the normal procedures for OS installation.

  • Page 257: Load Bxfcoe Driver

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Then load the bxfcoe (OFC) driver (Figure 11-12). Figure 11-12. Load bxfcoe Driver Select the boot LUN to be installed (Figure 11-13). Figure 11-13. Selecting the FCoE Boot LUN 83840-546-00 D...

  • Page 258: Windows Server 2012/2102 R2 Fcoe Boot Installation

    Windows Server 2012/2102 R2 FCoE Boot Installation For Windows Server 2012/2012 R2 Boot from SAN installation, QLogic requires the use of a “slipstream” DVD or iso image with the latest QLogic drivers injected. “Injecting (Slipstreaming) QLogic Drivers into Windows Image Files” on page 187 in the iSCSI chapter.

  • Page 259: Linux Fcoe Boot Installation

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Linux FCoE Boot Installation Configure the adapter boot parameters and Target Information (press CTRL+S and enter the CCM utility) as detailed in “Preparing System BIOS for FCoE Build and Boot” on page 216.

  • Page 260: Choosing Driver Update Medium

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Follow the on screen instructions to choose the Driver Update medium and load drivers (Figure 11-15). Figure 11-15. Choosing Driver Update Medium Once the driver update is complete, select Next to continue with OS installation.
  • Page 261 11–Fibre Channel Over Ethernet FCoE Boot from SAN When requested, click Configure FCoE Interfaces. Ensure FCoE Enable is set to yes on the 10GbE QLogic initiator ports you wish to use as the SAN boot path(s). 83840-546-00 D...
  • Page 262 11–Fibre Channel Over Ethernet FCoE Boot from SAN For each interface to be enabled for FCoE boot, click Change Settings and ensure FCoE Enable and AUTO_VLAN are set to yes and DCB required is set to no. For each interface to be enabled for FCoE boot, click on Create FCoE VLAN Interface.
  • Page 263 11–Fibre Channel Over Ethernet FCoE Boot from SAN Once complete with configuration of all interface, click OK to proceed. Click Next to continue installation. YaST2 will prompt to activate multipath. Answer as appropriate. 83840-546-00 D...
  • Page 264 11–Fibre Channel Over Ethernet FCoE Boot from SAN Continue installation as usual. Under the Expert tab on the Installation Settings screen, select Booting. Select the Boot Loader Installation tab and then select Boot Loader Installation Details, make sure you have one boot loader entry here. Delete all redundant entries.

  • Page 265: Rhel6 Installation

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Click OK to proceed and complete installation. RHEL6 Installation Boot from the installation medium. For RHEL6.3, an updated Anaconda image is required for FCoE BFS. That updated image is provided by Red Hat at the following URL http://rvykydal.fedorapeople.org/updates.823086-fcoe.img.
  • Page 266 11–Fibre Channel Over Ethernet FCoE Boot from SAN When prompted Do you have a driver disk, enter Yes. NOTE RHEL does not allow driver update media to be loaded over the network when installing driver updates for network devices. Use local media.
  • Page 267 11–Fibre Channel Over Ethernet FCoE Boot from SAN Select Specialized Storage Devices when prompted. Click Add Advanced Target. 83840-546-00 D...
  • Page 268 11–Fibre Channel Over Ethernet FCoE Boot from SAN Select Add FCoE SAN. and select Add drive. For each interface intended for FCoE boot, select the interface, deselect Use DCB, select Use auto vlan, and then click Add FCoE Disk(s). 83840-546-00 D...
  • Page 269 11–Fibre Channel Over Ethernet FCoE Boot from SAN Repeat steps 8 through 10 for all initiator ports. Confirm all FCoE visible disks are visible under Multipath Devices and/or Other SAN Devices. Click Next to proceed. Click Next and complete installation as usual. Upon completion of installation, the system will reboot.

  • Page 270: Linux: Adding Additional Boot Paths

    11–Fibre Channel Over Ethernet FCoE Boot from SAN Linux: Adding Additional Boot Paths Both RHEL and SLES require updates to the network configuration when adding new boot through an FCoE initiator that was not configured during installation. The following sections describe this procedure for each supported operating system.
  • Page 271 11–Fibre Channel Over Ethernet FCoE Boot from SAN SLES 11 SP2 and Above On SLES11 SP2, if the system boots through an initiator that has not been configured as an FCoE interface during installation, the system will fail to boot. To add new boot paths, the system must boot up through the configured FCoE interface.

  • Page 272: Vmware Esxi Fcoe Boot Installation

    FCoE Boot from SAN VMware ESXi FCoE Boot Installation FCoE Boot from SAN requires that the latest QLogic 8400 Series async drivers be included into the ESXi (5.1, 5.5, 6.0) install image. Refer to Image_builder_doc.pdf from VMware on how to slipstream drivers.
  • Page 273 11–Fibre Channel Over Ethernet FCoE Boot from SAN Press F11 to accept the agreement and continue. Select the boot LUN for installation and press Enter to continue. 83840-546-00 D...
  • Page 274 11–Fibre Channel Over Ethernet FCoE Boot from SAN Select the desired installation method. Select the keyboard layout. Enter a password. 83840-546-00 D...
  • Page 275 11–Fibre Channel Over Ethernet FCoE Boot from SAN Press F11 to confirm the install. Press Enter to reboot after installation. On 57800 and 57810 boards, the management network is not vmnic0. After booting, open the GUI console and display the configure management network >...

  • Page 276: Configuring Fcoe Boot From San On Vmware

    11–Fibre Channel Over Ethernet FCoE Boot from SAN For BCM57800 and BCM57810 boards, the FCoE boot devices need to have a separate vSwitch other than vSwith0. This allows DHCP to assign the IP address to the management network rather than to the FCoE boot device.

  • Page 277: Booting From San After Installation

    Figure 11-16. FCoE Reboot Driver Upgrade on Linux Boot from SAN Systems Remove the existing installed 8400 Series package. Log in as root. Query for the existing 8400 Series package and remove it using the following commands: # rpm -e <8400 Series package name>...

  • Page 278: Errors During Windows Fcoe Boot From San Installation

    11–Fibre Channel Over Ethernet Booting from SAN After Installation Install the binary RPM containing the new driver version. Refer to the linux-nx2 package README for instructions on how to prepare a binary driver RPM. Use the following command to update the ramdisk: ...

  • Page 279: Configuring Fcoe

    Configuring FCoE By default, DCB is enabled on QLogic 8400 Series FCoE-, DCB-compatible C-NICs. QLogic 8400 Series FCoE requires a DCB-enabled interface. For Windows operating systems, use QLogic Control Suite (QCS) or QLogic’s Comprehensive Configuration Management (CCM) utility to configure the DCB parameters.

  • Page 280: Overview

    QCS or CCM for Windows User’s Guide. Overview NIC partitioning divides a QLogic 8400/3400 Series 10 Gigabit Ethernet NIC into multiple virtual NICs by having multiple PCI physical functions per port. Each PCI function is associated with a different virtual NIC. To the OS and the network, each physical function appears as a separate NIC port.

  • Page 281: Supported Operating Systems For Nic Partitioning

    12–NIC Partitioning and Bandwidth Management Configuring for NIC Partitioning Supported Operating Systems for NIC Partitioning The QLogic 8400/3400 Series 10 Gigabit Ethernet adapters support NIC partitioning on the following operating systems:  Windows Server 2008 family  Windows Server 2012 family ...

  • Page 282: Network Mac Address

    12–NIC Partitioning and Bandwidth Management Configuration Parameters Network MAC Address The MAC address of the port. iSCSI MAC Address If an iSCSI adapter is loaded onto the system, the iSCSI MAC address will appear. Flow Control The flow control setting of the port. Physical Link Speed The physical link speed of the port, either 1G or 10G.
  • Page 283 12–NIC Partitioning and Bandwidth Management Configuration Parameters  It is possible for the sum of all maximum bandwidth values across the four functions of a single port to exceed the physical link speed value of either 10 Gbps or 1 Gbps. This case is called oversubscription. In a case where oversubscription congestion occurs on transmit, the Relative Bandwidth Weight value comes into effect.

  • Page 284: Vlan Overview

    Up to 64 VLANs (63 tagged and 1 untagged) can be defined for each QLogic adapter on your server, depending on the amount of memory available in your system. VLANs can be added to a team to allow multiple VLANs with different VLAN IDs.

  • Page 285: Example Vlan Network Topology

    VLAN is an accounting group. Main Server A high-use server that needs to be accessed from all VLANs and IP QLogic subnets. The Main Server has a adapter installed. All three IP subnets are accessed through the single physical adapter inter- face.

  • Page 286: Adding Vlans To Teams

    VLAN tagging is only required to be enabled on switch ports that create trunk links to other switches, or on ports connected to tag-capable end-stations, such as servers or workstations with QLogic adapters. For Hyper-V, create VLANs in the vSwitch-to-VM connection instead of in a team, to allow VM live migrations to occur without having to ensure the future host system has a matching team VLAN setup.

  • Page 287: Overview

    (VF), a lightweight PCIe function that can be directly assigned to a virtual machine (VM), bypassing the hypervisor layer for the main data movement. Not all QLogic adapters support SR-IOV; refer to your product documentation for details. Enabling SR-IOV Before attempting to enable SR-IOV, ensure that: ...
  • Page 288 Enable SR-IOV. SR-IOV must be done now and cannot be enabled after the vSwitch is created. Install the QLogic drivers for the adapters detected in the VM. Use the latest drivers available from your vendor for the host OS (do not use the inbox drivers).

  • Page 289: Sr-Iov And Storage

    14–SR-IOV Enabling SR-IOV SR-IOV and Storage Storage (FCoE or iSCSI) can be enabled on an SR-IOV-enabled adapter. However, if storage is used on an NPAR-enabled physical function (PF), then the number of virtual functions for that PF is set to zero; therefore, SR-IOV is disabled on that PF.

  • Page 290: 15 Microsoft Virtualization With Hyper-V

    Microsoft Virtualization with Hyper-V Microsoft Virtualization is a hypervisor virtualization system for Windows Server 2008 and 2012. This section is intended for those who are familiar with Hyper-V, and it addresses issues that affect the configuration of 8400/3400 Series network adapters and teamed network adapters when Hyper-V is used.

  • Page 291: Supported Features

    15–Microsoft Virtualization with Hyper-V Supported Features Supported Features Table 15-1 identifies Hyper-V supported features that are configurable for 8400/3400 Series network adapters. This table is not an all-inclusive list of Hyper-V features. Table 15-1. Configurable Network Adapter Hyper-V Features Supported in Windows Server Feature Comments/Limitation...

  • Page 292: Single Network Adapter

    15–Microsoft Virtualization with Hyper-V Single Network Adapter Single Network Adapter Windows Server 2008 When configuring a 8400/3400 Series network adapter on a Hyper-V system, be aware of the following:  An adapter that is to be bound to a virtual network should not be configured for VLAN tagging through the driver’s advanced properties.

  • Page 293: Teamed Network Adapters

    15–Microsoft Virtualization with Hyper-V Teamed Network Adapters Teamed Network Adapters Table 15-2 identifies Hyper-V supported features that are configurable for 8400/3400 Series teamed network adapters. This table is not an all-inclusive list of Hyper-V features. Table 15-2. Configurable Teamed Network Adapter Hyper-V Features Supported in Windows Server Version Feature...

  • Page 294: Windows Server 2008

    15–Microsoft Virtualization with Hyper-V Teamed Network Adapters Table 15-2. Configurable Teamed Network Adapter Hyper-V Features (Continued) Supported in Windows Server Version Feature Comments/Limitation 2008 2008 2012 Hyper-V virtual – switch over a teamed adapter Hyper-V virtual – switch over a VLAN iSCSI boot *Remote boot to SAN is sup- ported.

  • Page 295: Windows Server 2008 R2

    15–Microsoft Virtualization with Hyper-V Teamed Network Adapters Windows Server 2008 R2 When configuring a team of 8400/3400 Series network adapters on a Hyper-V system, be aware of the following:  Create the team prior to binding the team to the Hyper-V virtual network. ...

  • Page 296: Upgrading Windows Operating Systems

    From Windows Server 2008 to Windows Server 2008 R2  From Windows Server 2008 R2 to Windows Server 2012 Prior to performing an OS upgrade when a QLogic 8400/3400 Series adapter is installed on your system, QLogic recommends the procedure below. Save all team and adapter IP information.

  • Page 297: Overview

    Data Center Bridging (DCB)  Overview  DCB Capabilities  Configuring DCB  DCB Conditions  Data Center Bridging in Windows Server 2012 Overview Data Center Bridging (DCB) is a collection of IEEE specified standard extensions to Ethernet to provide lossless data delivery, low latency, and standards-based bandwidth sharing of data center physical links.

  • Page 298: Dcb Capabilities

    16–Data Center Bridging (DCB) DCB Capabilities DCB Capabilities Enhanced Transmission Selection (ETS) Enhanced Transmission Selection (ETS) provides a common management framework for assignment of bandwidth to traffic classes. Each traffic class or priority can be grouped in a Priority Group (PG), and it can be considered as a virtual link or virtual interface queue.

  • Page 299: Configuring Dcb

    16–Data Center Bridging (DCB) Configuring DCB Configuring DCB By default, DCB is enabled on QLogic 8400/3400 Series DCB-compatible C-NICs. DCB configuration is rarely required, as the default configuration should satisfy most scenarios. DCB parameters can be configured through QCS. See “Using...

  • Page 300: Data Center Bridging In Windows Server 2012

    PowerShell User Scripting Guide” in the Microsoft Technet Library. To revert to standard QCS control over the QLogic DCB feature set, uninstall the Microsoft QOS feature or disable Quality of Service in the QCS or Device Manager NDIS advance properties page.

  • Page 301: Executive Summary

    This section describes the technology and implementation considerations when working with the network teaming services offered by the QLogic software shipped with servers and storage products. The goal of QLogic teaming services is to provide fault tolerance and link aggregation across a team of two or more adapters.

  • Page 302: Glossary

    17–QLogic Teaming Services Executive Summary Glossary Table 17-1. Glossary Item Definition Address Resolution Protocol QLogic Control Suite ASP (intermediate driver) Domain Name Service G-ARP Gratuitous Address Resolution Protocol Generic Trunking Switch-dependent load balancing and failover type of team in (FEC/GEC)/802.3ad-...

  • Page 303: Teaming Concepts

    17–QLogic Teaming Services Executive Summary Table 17-1. Glossary (Continued) Item Definition Preboot Execution Environment RAID redundant array of inexpensive disks Smart Load Balanc- Switch-independent failover type of team in which the primary ing™ and Failover team member handles all incoming and outgoing traffic while the standby team member is idle until a failover event (for example, loss of link occurs).

  • Page 304: Network Addressing

    17–QLogic Teaming Services Executive Summary Network Addressing To understand how teaming works, it is important to understand how node communications work in an Ethernet network. This document is based on the assumption that the reader is familiar with the basics of IP and Ethernet network communications.

  • Page 305: Description Of Teaming Types

    17–QLogic Teaming Services Executive Summary For switch-independent teaming modes, all physical adapters that make up a virtual adapter must use the unique MAC address assigned to them when transmitting data. That is, the frames that are sent by each of the physical adapters in the team must use a unique MAC address to be IEEE compliant.
  • Page 306 17–QLogic Teaming Services Executive Summary Table 17-2. Available Teaming Types Link Aggregation Switch-Dependent Control (Switch must Teaming Type Protocol Load Balancing Failover support specific Support type of team) Required on the Switch Generic Trunking ✔ ✔ ✔ (FEC/GEC)/802. 3ad-Draft Static...
  • Page 307 17–QLogic Teaming Services Executive Summary Smart Load Balancing enables both transmit and receive load balancing based on the Layer 3/Layer 4 IP address and TCP/UDP port number. In other words, the load balancing is not done at a byte or frame level but on a TCP/UDP session basis.
  • Page 308 17–QLogic Teaming Services Executive Summary When the clients and the system are on different subnets, and incoming traffic has to traverse a router, the received traffic destined for the system is not load balanced. The physical adapter that the intermediate driver has selected to carry the IP flow carries all of the traffic.
  • Page 309 17–QLogic Teaming Services Executive Summary In this teaming mode, the intermediate driver controls load balancing and failover for outgoing traffic only, while incoming traffic is controlled by the switch firmware and hardware. As is the case for Smart Load Balancing, the ASP intermediate driver uses the IP/TCP/UDP source and destination addresses to load balance the transmit traffic from the server.

  • Page 310: Software Components

    The QLogic supplied teaming support is provided by three individual software components that work together and are supported as a package. When one component is upgraded, all the other components must be upgraded to the supported versions.

  • Page 311: Hardware Requirements

    17–QLogic Teaming Services Executive Summary Hardware Requirements  Repeater Hub  Switching Hub  Router The various teaming modes described in this document place certain restrictions on the networking equipment used to connect clients to teamed systems. Each type of network interconnect technology has an effect on teaming as described in the following sections.

  • Page 312: Router

    The QLogic Control Suite utility is used to configure teaming in the supported operating system environments. The QLogic Control Suite (QCS) utility is designed to run on 32-bit and 64-bit Windows family of operating systems. QCS is used to configure load balancing and fault tolerance teaming, and VLANs.
  • Page 313 17–QLogic Teaming Services Executive Summary Table 17-4. Comparison of Team Types (Continued) Switch-Independent Fault Load Switch-Dependent Dynamic Link Type of Team Tolerance Balancing Static Trunking Aggregation (IEEE 802.3ad) SLB with Function Generic Trunking Link Aggregation Standby Switch link fault tol-...
  • Page 314 Same IP address for all team mem- bers Load balancing by IP address Load balancing by Yes (used for MAC address no-IP/IPX) SLB with one primary and one standby member. Requires at least one QLogic adapter in the team. 83840-546-00 D...

  • Page 315: Selecting A Team Type

    17–QLogic Teaming Services Executive Summary Selecting a Team Type The following flow chart provides the decision flow when planning for Layer 2 teaming. The primary rationale for teaming is the need for additional network bandwidth and fault tolerance. Teaming offers link aggregation and fault tolerance to meet both of these requirements.

  • Page 316: Teaming Mechanisms

    17–QLogic Teaming Services Teaming Mechanisms Teaming Mechanisms  Architecture  Types of Teams  Attributes of the Features Associated with Each Type of Team  Speeds Supported for Each Type of Team 83840-546-00 D...

  • Page 317: Architecture

    17–QLogic Teaming Services Teaming Mechanisms Architecture The ASP is implemented as an NDIS intermediate driver (see Figure 17-2). It operates below protocol stacks such as TCP/IP and IPX and appears as a virtual adapter. This virtual adapter inherits the MAC Address of the first port initialized in the team.

  • Page 318: Outbound Traffic Flow

    Teaming Mechanisms Outbound Traffic Flow The QLogic Intermediate Driver manages the outbound traffic flow for all teaming modes. For outbound traffic, every packet is first classified into a flow, and then distributed to the selected physical adapter for transmission. The flow classification involves an efficient hash computation over known protocol fields.

  • Page 319: Protocol Support

    17–QLogic Teaming Services Teaming Mechanisms When an inbound IP Datagram arrives, the appropriate Inbound Flow Head Entry is located by hashing the source IP address of the IP Datagram. Two statistics counters stored in the selected entry are also updated. These counters are used in the same fashion as the outbound counters by the load-balancing engine periodically to reassign the flows to the physical adapter.

  • Page 320: Performance

    Types of Teams Switch-Independent The QLogic Smart Load Balancing type of team allows two to eight physical adapters to operate as a single virtual adapter. The greatest benefit of the SLB type of team is that it operates on any IEEE compliant switch and requires no special configuration.

  • Page 321: Switch-Dependent

    Outbound Load Balancing using MAC Address - No.  Outbound Load Balancing using IP Address - Yes  Multivendor Teaming – Supported (must include at least one QLogic Ethernet adapter as a team member). Applications The SLB algorithm is most appropriate in home and small business environments where cost is a concern or with commodity switching equipment.
  • Page 322 The following are the key attributes of Generic Static Trunking:  Failover mechanism – Link loss detection  Load Balancing Algorithm – Outbound traffic is balanced through QLogic proprietary mechanism based L4 flows. Inbound traffic is balanced according to a switch specific mechanism. ...
  • Page 323 The following are the key attributes of Dynamic Trunking:  Failover mechanism – Link loss detection  Load Balancing Algorithm – Outbound traffic is balanced through a QLogic proprietary mechanism based on L4 flows. Inbound traffic is balanced according to a switch specific mechanism. ...

  • Page 324: Livelink

    The attributes of the features associated with each type of team are summarized Table 17-5. Table 17-5. Attributes Feature Attribute Smart Load Balancing User interface QLogic Control Suite (QCS) Number of teams Maximum 16 Number of adapters per team Maximum 16 Hot replace Hot add Hot remove...
  • Page 325 17–QLogic Teaming Services Teaming Mechanisms Table 17-5. Attributes (Continued) Feature Attribute Failover event Loss of link Failover time <500 ms Fallback time 1.5 s (approximate) MAC address Different Multivendor teaming 83840-546-00 D...
  • Page 326 17–QLogic Teaming Services Teaming Mechanisms Table 17-5. Attributes (Continued) Feature Attribute Generic Trunking User interface QLogic Control Suite (QCS) Number of teams Maximum 16 Number of adapters per team Maximum 16 Hot replace Hot add Hot remove Link speed support...
  • Page 327 17–QLogic Teaming Services Teaming Mechanisms Table 17-5. Attributes (Continued) Feature Attribute Dynamic Trunking User interface QLogic Control Suite (QCS) Number of teams Maximum 16 Number of adapters per team Maximum 16 Hot replace Hot add Hot remove Link speed support...

  • Page 328: Speeds Supported For Each Type Of Team

    17–QLogic Teaming Services Teaming and Other Advanced Networking Properties Speeds Supported for Each Type of Team The various link speeds that are supported for each type of team are listed in Table 17-6. Mixed speed refers to the capability of teaming adapters that are running at different link speeds.

  • Page 329: Checksum Offload

    Checksum Offload Checksum Offload is a property of the QLogic network adapters that allows the TCP/IP/UDP checksums for send and receive traffic to be calculated by the adapter hardware rather than by the host CPU. In high-traffic situations, this can allow a system to handle more connections more efficiently than if the host CPU were forced to calculate the checksums.

  • Page 330: Large Send Offload

    Teaming and Other Advanced Networking Properties Large Send Offload Large Send Offload (LSO) is a feature provided by QLogic network adapters that prevents an upper level protocol such as TCP from breaking a large data packet into a series of smaller packets with headers appended to them. The protocol...

  • Page 331: Preboot Execution Environment

    The only supported ASP team configuration when using Microsoft Virtual Server 2005 is with a Smart Load Balancing team-type consisting of a single primary QLogic adapter and a standby QLogic adapter. Make sure to unbind or deselect “Virtual Machine Network Services” from each team member prior to creating a team and prior to creating Virtual networks with Microsoft Virtual Server.

  • Page 332: Teaming Across Switches

    This is true for all types of teaming supported by QLogic. Therefore, an interconnect link must be provided between the switches that connect to ports in the same team.

  • Page 333: Teaming Across Switches Without An Interswitch Link

    17–QLogic Teaming Services General Network Considerations Furthermore, a failover event would cause additional loss of connectivity. Consider a cable disconnect on the Top Switch port 4. In this case, Gray would send the ICMP Request to Red 49:C9, but because the Bottom switch has no entry for 49:C9 in its CAM Table, the frame is flooded to all its ports but cannot find a way to get to 49:C9.

  • Page 334: Teaming Across Switches With Interconnect

    17–QLogic Teaming Services General Network Considerations The addition of a link between the switches allows traffic from/to Blue and Gray to reach each other without any problems. Note the additional entries in the CAM table for both switches. The link interconnect is critical for the proper operation of the team.

  • Page 335: Failover Event

    17–QLogic Teaming Services General Network Considerations Figure 17-5 represents a failover event in which the cable is unplugged on the Top Switch port 4. This is a successful failover with all stations pinging each other without loss of connectivity. Figure 17-5. Failover Event...

  • Page 336: Spanning Tree Algorithm

    17–QLogic Teaming Services General Network Considerations Spanning Tree Algorithm  Topology Change Notice (TCN)  Port Fast/Edge Port In Ethernet networks, only one active path may exist between any two bridges or switches. Multiple active paths between switches can cause loops in the network.

  • Page 337: Topology Change Notice (Tcn)

    17–QLogic Teaming Services General Network Considerations Topology Change Notice (TCN) A bridge/switch creates a forwarding table of MAC addresses and port numbers by learning the source MAC address that received on a particular port. The table is used to forward frames to a specific port rather than flooding the frame to all ports.

  • Page 338: Teaming With Hubs (For Troubleshooting Purposes Only)

    17–QLogic Teaming Services General Network Considerations Teaming with Hubs (for troubleshooting purposes only)  Hub Usage in Teaming Network Configurations  SLB Teams  SLB Team Connected to a Single Hub  Generic and Dynamic Trunking (FEC/GEC/IEEE 802.3ad) SLB teaming can be used with 10/100 hubs, but it is only recommended for troubleshooting purposes, such as connecting a network analyzer when switch port mirroring is not an option.

  • Page 339: Slb Team Connected To A Single Hub

    17–QLogic Teaming Services General Network Considerations SLB Team Connected to a Single Hub SLB teams configured as shown in Figure 17-6 maintain their fault tolerance properties. Either server connection could fail without affecting the network. Clients could be connected directly to the hub, and fault tolerance would still be maintained;...

  • Page 340: Teaming With Microsoft Nlb

    Multiple adapters may be used for each of these purposes: private, intracluster communications and public, external client communications. All QLogic teaming modes are supported with Microsoft Cluster Software for the public adapter only.

  • Page 341: Clustering With Teaming Across One Switch

    17–QLogic Teaming Services Application Considerations Figure 17-7 shows a 2-node Fibre-Channel cluster with three network interfaces per cluster node: one private and two public. On each node, the two public adapters are teamed, and the private adapter is not. Teaming is supported across the same switch or across two switches.

  • Page 342: High-Performance Computing Cluster

    17–QLogic Teaming Services Application Considerations High-Performance Computing Cluster Gigabit Ethernet is typically used for the following three purposes in high-performance computing cluster (HPCC) applications:  Inter-Process Communications (IPC): For applications that do not require low-latency, high-bandwidth interconnects (such as Myrinet, InfiniBand), Gigabit Ethernet can be used for communication between the compute nodes.

  • Page 343: Oracle

    17–QLogic Teaming Services Application Considerations Oracle In our Oracle Solution Stacks, we support adapter teaming in both the private network (interconnect between RAC nodes) and public network with clients or the application layer above the database layer. Figure 17-8. Clustering With Teaming Across Two Switches...

  • Page 344: Teaming And Network Backup

    17–QLogic Teaming Services Application Considerations Teaming and Network Backup  Load Balancing and Failover  Fault Tolerance When you perform network backups in a nonteamed environment, overall throughput on a backup server adapter can be easily impacted due to excessive traffic and adapter overloading.

  • Page 345: Load Balancing And Failover

    Figure 17-10 shows a network topology that demonstrates tape backup in a QLogic teamed environment and how smart load balancing can load balance tape backup data across teamed adapters. There are four paths that the client-server can use to send data to the backup server, but only one of these paths will be designated during data transfer.

  • Page 346: Fault Tolerance

    If a network link fails during tape backup operations, all traffic between the backup server and client stops and backup jobs fail. If, however, the network topology was configured for both QLogic SLB and switch fault tolerance, then this would allow tape backup operations to continue without interruption during the link failure. All failover processes within the network are transparent to tape backup software applications.

  • Page 347: Network Backup With Slb Teaming Across Two Switches

    17–QLogic Teaming Services Application Considerations To understand how backup data streams are directed during network failover process, consider the topology in Figure 17-10. Client-Server Red is transmitting data to the backup server through Path 1, but a link failure occurs between the backup server and the switch.

  • Page 348: Troubleshooting Teaming Problems

    17–QLogic Teaming Services Troubleshooting Teaming Problems Troubleshooting Teaming Problems  Teaming Configuration Tips  Troubleshooting Guidelines When running a protocol analyzer over a virtual adapter teamed interface, the MAC address shown in the transmitted frames may not be correct. The analyzer does not show the frames as constructed by ASP and shows the MAC address of the team and not the MAC address of the interface transmitting the frame.

  • Page 349: Troubleshooting Guidelines

    Disabling the device driver of a network adapter participating in an LACP or GEC/FEC team may have adverse affects with network connectivity. QLogic recommends that the adapter first be physically disconnected from the switch before disabling the device driver to avoid a network connection loss.

  • Page 350: Frequently Asked Questions

    Question: What network protocols are load balanced when in a team? Answer: QLogic’s teaming software only supports IP/TCP/UDP traffic. All other traffic is forwarded to the primary adapter.
  • Page 351 Question: How can I determine the performance statistics on a virtual adapter (team)? Answer: In QLogic Control Suite, click the Statistics tab for the virtual adapter. Question: Can I configure NLB and teaming concurrently? Answer: Yes, but only when running NLB in a multicast mode (NLB is not supported with MS Cluster Services).
  • Page 352 Question: Where do I monitor real time statistics for an adapter team in a Windows server? Answer: Use the QLogic Control Suite (QCS) to monitor general, IEEE 802.3 and custom counters. Question: What features are not supported on a multivendor team? Answer: VLAN tagging, and RSS are not supported on a multivendor team.

  • Page 353: Event Log Messages

    Table 17-9. As a QLogic adapter driver loads, Windows places a status code in the system event viewer. There may be up to two classes of entries for these event codes depending on whether both drivers are loaded (one set for the base or miniport driver and one set for the intermediate or teaming driver).
  • Page 354 17–QLogic Teaming Services Event Log Messages Table 17-8. Base Driver Event Log Messages (Continued) Message Severity Message Cause Corrective Action Number Error Failed to access The driver cannot For add-in adapters: configuration infor- access PCI configura- reseat the adapter in mation.
  • Page 355 17–QLogic Teaming Services Event Log Messages Table 17-8. Base Driver Event Log Messages (Continued) Message Severity Message Cause Corrective Action Number Informational Network controller The adapter has been No action is required. configured for 1Gb manually configured for full-duplex link.
  • Page 356 Driver initialization Unspecified failure Reinstall the driver, failed. during driver initializa- update to a newer tion. driver, run QLogic Con- trol Suite diagnostics, or replace the adapter. Informational Network controller The adapter has been No action is required. configured for 10Gb manually configured for full-duplex link.

  • Page 357: Intermediate Driver (Virtual Adapter/Team)

    17–QLogic Teaming Services Event Log Messages Intermediate Driver (Virtual Adapter/Team) The intermediate driver is identified by source BLFM, regardless of the base driver revision. Table 17-9 lists the event log messages supported by the intermediate driver, explains the cause for the message, and provides the recommended action.
  • Page 358 17–QLogic Teaming Services Event Log Messages Table 17-9. Intermediate Driver Event Log Messages (Continued) System Event Severity Message Cause Corrective Action Message Number Warning Network adapter is The physical adapter Check that the net- disconnected. is not connected to the...

  • Page 359: Virtual Bus Driver

    17–QLogic Teaming Services Event Log Messages Table 17-9. Intermediate Driver Event Log Messages (Continued) System Event Severity Message Cause Corrective Action Message Number Informational Network adapter is A physical adapter has No action is required. activated and is partic- been added to or acti- ipating in network traf- vated in a team.
  • Page 360 17–QLogic Teaming Services Event Log Messages Table 17-10. VBD Event Log Messages (Continued) Message Severity Message Cause Corrective Action Number Informational The network link is The adapter has lost Check that the net- down. Check to make its connection with its...
  • Page 361 17–QLogic Teaming Services Event Log Messages Table 17-10. VBD Event Log Messages (Continued) Message Severity Message Cause Corrective Action Number Informational Network controller The adapter has been No action is required. configured for 1Gb manually configured full-duplex link. for the selected line speed and duplex set- tings.

  • Page 362: Asp Overview

    (called “Channel Bonding”), refer to your operating system documentation. ASP Overview ASP is the QLogic teaming software for the Windows family of operating systems. ASP settings are configured by QCS utility. ASP provides heterogeneous support for adapter teaming to include QLogic 8400/3400 Series adapters and QLogic-shipping Intel NIC adapters/LOMs.

  • Page 363: Load Balancing And Fault Tolerance

    18–Configuring Teaming in Windows Server Load Balancing and Fault Tolerance Load Balancing and Fault Tolerance Teaming provides traffic load balancing and fault tolerance (redundant adapter operation when a network connection fails). When multiple Gigabit Ethernet network adapters are installed in the same system, they can be grouped into teams, creating a virtual adapter.

  • Page 364: Smart Load Balancing And Failover

    Load Balancing and Fault Tolerance Smart Load Balancing and Failover Smart Load Balancing and Failover is the QLogic implementation of load balancing based on IP flow. This feature supports balancing IP traffic across multiple adapters (team members) in a bidirectional manner. In this type of team, all adapters in the team have separate MAC addresses.

  • Page 365: Generic Trunking (Fec/Gec)/802.3Ad-Draft Static

    18–Configuring Teaming in Windows Server Load Balancing and Fault Tolerance Generic Trunking (FEC/GEC)/802.3ad-Draft Static The Generic Trunking (FEC/GEC)/802.3ad-Draft Static type of team is very similar to the Link Aggregation (802.3ad) type of team in that all adapters in the team are configured to receive packets for the same MAC address.

  • Page 366: Auto-Fallback Disable) Types Of Teams

    Smart Load Balancing is a protocol-specific scheme. The level of support for IP, IPX, and NetBEUI protocols is listed in Table 18-1. Table 18-1. Smart Load Balancing Failover/Fallback — All Failover/Fallback — QLogic Multivendor Operating System Protocol NetBE NetBE Windows Server 2008...

  • Page 367: Teaming And Large Send Offload/Checksum Offload Support

    Other protocol packets are sent and received through one primary interface only. Failover for non-IP traffic is supported only for QLogic network adapters. The Generic Trunking type of team requires the Ethernet switch to support some form of port trunking mode (for example, Cisco's Gigabit EtherChannel or other switch vendor's Link Aggregation mode).
  • Page 368 “CIM-XML” on page QLogic's implementation of CIM will provide various classes to provide information to users through CIM client applications. Note that QLogic CIM data provider will provide data only, and users can choose their preferred CIM client software to browse the information exposed by QLogic CIM provider.
  • Page 369 ASP provides events through event logs. Users can use the “Event Viewer” provided by Windows server platforms, or use CIM to inspect or monitor these events. QLogic CIM provider will also provide event information through the CIM generic event model. These events are __InstanceCreationEvent, __InstanceDeletionEvent and __InstanceModificationEvent, and are defined by CIM.

  • Page 370: Introduction

    Performing Diagnostics  Diagnostic Test Descriptions Introduction QLogic 8400/3400 Series User Diagnostics is an MS-DOS based application that runs a series of diagnostic tests (see Table 20-2) on the QLogic 8400/3400 Series network adapters in your system. QLogic 8400/3400 Series User Diagnostics also allows you to update device firmware and to view and change settings for available adapter properties.

  • Page 371: Performing Diagnostics

    Table 20-1. uediag Command Options Command Description Options uediag Performs all tests on all QLogic 8400/3400 Series adapters in your system. uediag -c Specifies the adapter (device#) to test. Similar to -dev (for back- <device#> ward compatibility).
  • Page 372 <raw_image> uediag -fump Specifies the bin file to update UMP firmware. <ump_image> uediag -help Displays the QLogic 8400/3400 Series User Diagnostics (uediag) command options. uediag -I Specifies the number of iterations to run on the selected tests. <iteration#> uediag -idmatch Enables matching of VID, DID, SVID, and SSID from the image file with device IDs: Used only with -fnvm <raw_image>.

  • Page 373: Diagnostic Test Descriptions

    -T Enables certain groups/tests. <groups/tests> uediag -ver Displays the version of QLogic 8400/3400 Series User Diagnos- tics (uediag) and all installed adapters. Diagnostic Test Descriptions The diagnostic tests are divided into four groups: Basic Functional Tests (Group A), Memory Tests (Group B), Block Tests (Group C), and Ethernet Traffic Tests (Group D).
  • Page 374 20–User Diagnostics in DOS Diagnostic Test Descriptions Table 20-2. Diagnostic Tests (Continued) Test Description Number Name Verifies that a Message Signaled Interrupt (MSI) causes an MSI message to be DMA’d to host memory. A negative test is also performed to verify that when an MSI is masked, it does not write an MSI message to host memory.
  • Page 375 Name Group B: Memory Tests TXP Scratchpad The Group B tests verify all memory blocks of the QLogic 8400/3400 Series adapters by writing various TPAT Scratch- data patterns (0x55aa55aa, 0xaa55aa55, walking zeroed, walking ones, address, and so on.) to each...
  • Page 376 (identifying the TCP, IP, and UDP header data structures) and calculates the checksum/CRC. The TPAT block results are compared with the values expected by QLogic 8400/3400 Series User Diagnos- tics and any errors are displayed. FIO Register The Fast IO (FIO) verifies the register interface that is exposed to the internal CPUs.
  • Page 377 Enables MAC loopback mode in the adapter and trans- mits 5000 Layer 2 packets of various sizes. As the packets are received back by QLogic 8400/3400 Series User Diagnostics, they are checked for errors. Packets are returned through the MAC receive path and never reach the PHY.
  • Page 378 MAC loopback mode and transmitting large TCP packets. As the packets are received back by QLogic 8400/3400 Series User Diagnostics, they are checked for proper segmentation (according to the selected MSS size) and any other errors. The adapter should not be connected to a network.

  • Page 379: Hardware Diagnostics

    Troubleshooting  Hardware Diagnostics  Checking Port LEDs  Troubleshooting Checklist  Checking if Current Drivers are Loaded  Running a Cable Length Test  Testing Network Connectivity  Possible Problems and Solutions Hardware Diagnostics Loopback diagnostic tests are available for testing the adapter hardware. These tests provide access to the adapter internal/external diagnostics, where packet information is transmitted across the physical link (for instructions and information on running tests in an MS-DOS environment, see...

  • Page 380: Qcs Network Test Failures

    21–Troubleshooting Checking Port LEDs Below are troubleshooting steps that may help correct the failure. Remove the failing device and reseat it in the slot, ensuring the card is firmly seated in the slot from front to back. Rerun the test. If the card still fails, replace it with a different card of the same model and run the test.

  • Page 381: Troubleshooting Checklist

    “Safety Precautions” on page The following checklist provides recommended actions to take to resolve problems installing the QLogic 8400/3400 Series adapters or running them in your system.  Inspect all cables and connections. Verify that the cable connections at the network adapter and the switch are attached properly.

  • Page 382: Linux

    Instead, you can view the logs to verify that the proper driver is loaded and will be active upon reboot: dmesg | grep -i "QLogic" | grep -i "bnx2" 83840-546-00 D...

  • Page 383: Running A Cable Length Test

    Windows Network connectivity can be tested using the “Testing the Network” on page 104 feature in QLogic Control Suite. An alternate method is to use the ping command to determine if the network connection is working. Click Start, and then click Run.

  • Page 384: Possible Problems And Solutions

    21–Troubleshooting Possible Problems and Solutions Possible Problems and Solutions This section presents a list of possible problems and solutions for the components and categories:  Multi-boot Agent   Linux  NPAR  Miscellaneous Multi-boot Agent Problem: Unable to obtain network settings through DHCP using PXE. Solution: For proper operation make sure that the STP is disabled or that portfast mode (for Cisco) is enabled on the port to which the PXE client is connected.

  • Page 385: Linux

    21–Troubleshooting Possible Problems and Solutions Problem: A system containing an 802.3ad team causes a Netlogon service failure in the system event log and prevents it from communicating with the domain controller during boot up. Solution: Microsoft Knowledge Base Article 326152 (http://support.microsoft.com/kb/326152/en-us) indicates that Gigabit Ethernet adapters may experience problems with connectivity to a domain controller due to link fluctuation while the driver initializes and negotiates link with the network...
  • Page 386 21–Troubleshooting Possible Problems and Solutions Problem: Routing does not work for 8400/3400 Series 10 GbE network adapters installed in Linux systems. Solution: For 8400/3400 Series 10 GbE network adapters installed in systems with Linux kernels older than 2.6.26, disable TPA with either ethtool (if available) or with the driver parameter (see “disable_tpa”...

  • Page 387: Npar

    Solution: Enable iSCSI Crash Dump from the Advanced section of the QCS Configuration tab. Problem: The QLogic 8400/3400 Series adapters may not perform at optimal level on some systems if it is added after the system has booted. Solution: The system BIOS in some systems does not set the cache line size and the latency timer if the adapter is added after the system has booted.
  • Page 388 Problem: The network adapter has shut down and an error message appears indicating that the fan on the network adapter has failed. Solution: The network adapter was shut down to prevent permanent damage. Contact QLogic Support for assistance. 83840-546-00 D...

  • Page 389: A-1 Network Link And Activity Indicated By The Rj-45 Port Leds

    Ethernet connections and SFP+, the state of the network link and activity is indicated by a single LED located adjacent to the port connector, as described in Table A-2. QLogic Control Suite also provides information about the status of the network link and activity (see “Viewing Vital Signs” on page 101).
  • Page 391 International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan © 2014, 2015 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic and the QLogic logo are registered trademarks of QLogic Corporation.

This manual is also suitable for:

3400 series

Table of Contents