Users Guide
Table Of Contents
- Table of Contents
- Preface
- 1 Functionality and Features
- 2 Configuring Teaming in Windows Server
- 3 Virtual LANs in Windows
- 4 Installing the Hardware
- 5 Manageability
- 6 Boot Agent Driver Software
- 7 Linux Driver Software
- Introduction
- Limitations
- Packaging
- Installing Linux Driver Software
- Load and Run Necessary iSCSI Software Components
- Unloading or Removing the Linux Driver
- Patching PCI Files (Optional)
- Network Installations
- Setting Values for Optional Properties
- Driver Defaults
- Driver Messages
- bnx2x Driver Messages
- bnx2i Driver Messages
- BNX2I Driver Sign-on
- Network Port to iSCSI Transport Name Binding
- Driver Completes Handshake with iSCSI Offload-enabled C-NIC Device
- Driver Detects iSCSI Offload Is Not Enabled on the C-NIC Device
- Exceeds Maximum Allowed iSCSI Connection Offload Limit
- Network Route to Target Node and Transport Name Binding Are Two Different Devices
- Target Cannot Be Reached on Any of the C-NIC Devices
- Network Route Is Assigned to Network Interface, Which Is Down
- SCSI-ML Initiated Host Reset (Session Recovery)
- C-NIC Detects iSCSI Protocol Violation - Fatal Errors
- C-NIC Detects iSCSI Protocol Violation—Non-FATAL, Warning
- Driver Puts a Session Through Recovery
- Reject iSCSI PDU Received from the Target
- Open-iSCSI Daemon Handing Over Session to Driver
- bnx2fc Driver Messages
- BNX2FC Driver Signon
- Driver Completes Handshake with FCoE Offload Enabled C-NIC Device
- Driver Fails Handshake with FCoE Offload Enabled C-NIC Device
- No Valid License to Start FCoE
- Session Failures Due to Exceeding Maximum Allowed FCoE Offload Connection Limit or Memory Limits
- Session Offload Failures
- Session Upload Failures
- Unable to Issue ABTS
- Unable to Recover the IO Using ABTS (Due to ABTS Timeout)
- Unable to Issue I/O Request Due to Session Not Ready
- Drop Incorrect L2 Receive Frames
- Host Bus Adapter and lport Allocation Failures
- NPIV Port Creation
- Teaming with Channel Bonding
- Statistics
- Linux iSCSI Offload
- 8 VMware Driver Software
- Introduction
- Packaging
- Download, Install, and Update Drivers
- Driver Parameters
- FCoE Support
- iSCSI Support
- 9 Windows Driver Software
- Supported Drivers
- Installing the Driver Software
- Modifying the Driver Software
- Repairing or Reinstalling the Driver Software
- Removing the Device Drivers
- Viewing or Changing the Properties of the Adapter
- Setting Power Management Options
- Configuring the Communication Protocol to Use with QCC GUI, QCC PowerKit, and QCS CLI
- 10 Citrix XenServer Driver Software
- 11 iSCSI Protocol
- iSCSI Boot
- Supported Operating Systems for iSCSI Boot
- iSCSI Boot Setup
- Configuring the iSCSI Target
- Configuring iSCSI Boot Parameters
- MBA Boot Protocol Configuration
- iSCSI Boot Configuration
- Enabling CHAP Authentication
- Configuring the DHCP Server to Support iSCSI Boot
- DHCP iSCSI Boot Configuration for IPv4
- DHCP iSCSI Boot Configuration for IPv6
- Configuring the DHCP Server
- Preparing the iSCSI Boot Image
- Booting
- Other iSCSI Boot Considerations
- Troubleshooting iSCSI Boot
- iSCSI Crash Dump
- iSCSI Offload in Windows Server
- iSCSI Boot
- 12 Marvell Teaming Services
- Executive Summary
- Teaming Mechanisms
- Teaming and Other Advanced Networking Properties
- General Network Considerations
- Application Considerations
- Troubleshooting Teaming Problems
- Frequently Asked Questions
- Event Log Messages
- 13 NIC Partitioning and Bandwidth Management
- 14 Fibre Channel Over Ethernet
- Overview
- FCoE Boot from SAN
- Preparing System BIOS for FCoE Build and Boot
- Preparing Marvell Multiple Boot Agent for FCoE Boot (CCM)
- Preparing Marvell Multiple Boot Agent for FCoE Boot (UEFI)
- Provisioning Storage Access in the SAN
- One-Time Disabled
- Windows Server 2016/2019/Azure Stack HCI FCoE Boot Installation
- Linux FCoE Boot Installation
- VMware ESXi FCoE Boot Installation
- Booting from SAN After Installation
- Configuring FCoE
- N_Port ID Virtualization (NPIV)
- 15 Data Center Bridging
- 16 SR-IOV
- 17 Specifications
- 18 Regulatory Information
- 19 Troubleshooting
- Hardware Diagnostics
- Checking Port LEDs
- Troubleshooting Checklist
- Checking if Current Drivers Are Loaded
- Running a Cable Length Test
- Testing Network Connectivity
- Microsoft Virtualization with Hyper-V
- Removing the Marvell 57xx and 57xxx Device Drivers
- Upgrading Windows Operating Systems
- Marvell Boot Agent
- Linux
- NPAR
- Kernel Debugging Over Ethernet
- Miscellaneous
- A Revision History
19–Troubleshooting
Linux
Doc No. BC0054508-00 Rev. R
January 21, 2021 Page 290 Copyright © 2021 Marvell
Problem: Routing does not work for 57xx and 57xxx 10GbE network adapters
installed in Linux systems.
Solution: For 57xx and 57xxx 10GbE 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” on page 45). Use ethtool to disable
TPA (LRO) for a specific 57xx and 57xxx 10GbE network adapter.
Problem: On a 57xx and 57xxx 1GbE network adapter in a C-NIC environment,
flow control does not work.
Solution: Flow control is working, but in a C-NIC environment, it has the
appearance that it is not. The network adapter is capable of sending pause frames
when the on-chip buffers are depleted, but the adapter also prevents the
head-of-line blocking of other receive queues. Because the head-of-line blocking
causes the on-chip firmware to discard packets inside the on-chip receive buffers,
in the case a specific host queue is depleted, the on-chip receive buffers are
rarely depleted, therefore, it may appear that flow control is not functioning.
Problem: Errors appear when compiling driver source code.
Solution: Some installations of Linux distributions do not install the development
tools by default. Before compiling driver source code, ensure that the
development tools for the Linux distribution you are using are installed.
Problem: L4 iSCSI offload boot from SAN fails (iscsiuio crashes). This problem is
seen on Linux OSs based on 4.5 kernel and later.
Solution: To override the kernel config option CONFIG_IO_STRICT_DEVMEM
and avoid crash of iscsiuio on OS boot, edit the OS grub and add the kernel
command line parameter iomem=relaxed during the start of OS installation or
OS boot.
Problem: iSCSI-Offload boot from SAN fails to boot after installation.
The iSCSI boot from SAN process is divided into two parts: pre switch-root and
post switch root.
During pre switch-root, when the drivers load, the open-iSCSI tool iscsistart
establishes the connection with the target and discovers the remote LUN. Then
iscsistart starts a session using the iBFT information.
The iscsistart utility program is not run to manage connection with target. (Its
primary use is to start sessions used for iSCSI root boot.)
After the post switch-root, as a part of initialize boot process, the open-iscsi tool
iscsid takes over the pre switch-root iSCSI connection. Therefore, iscsid manages
the iscsi connection with target during recovery.