Users Guide
Table Of Contents
- Table of Contents
- Chapter 1: Introduction
- Chapter 2: Installation
- Chapter 3: Configuration
- 3.1 ESXi Command Line Tool Transition
- 3.2 FC Driver Configuration
- 3.2.1 Configuration Methods for FC Driver Parameters
- 3.2.2 Emulex ExpressLane Support
- 3.2.3 FC-SP-2 Authentication (DH-CHAP) Support
- 3.2.4 Trunking Support
- 3.2.5 Dynamically Adding LUNs
- 3.2.6 Dynamically Adding Targets
- 3.2.7 FC Driver Module Parameters
- 3.2.8 Creating an FC Remote Boot Disk
- 3.2.9 Managing Devices through the CIM Interface
- 3.2.10 Installing the Emulex CIM Provider
- 3.2.11 Creating, Deleting, and Displaying vPorts
- 3.2.12 Configuring VVols
- 3.2.13 Adjusting the LUN Queue Depth
- 3.3 Configuring NVMe over FC on a NetApp Target
- 3.4 Configuring NVMe over FC on an Initiator System
- Chapter 4: Troubleshooting the FC Driver
- Chapter 5: Troubleshooting the NVMe Driver
- Appendix A: esxcli Management Tool
- Appendix B: lpfc Driver BlockGuard Functionality
- Appendix C: Using the VMID Feature on a Brocade Switch
- Appendix D: Using the VMID Feature on a Cisco Switch
- Appendix E: NPIV Configuration
- Appendix F: License Notices
Broadcom DRVVM-UG128-100
104
Emulex Drivers for VMware ESXi User Guide
B.2 Enabling BlockGuard
BlockGuard is disabled by default. To enable it, the parameter lpfc_enable_bg must be passed to the driver as follows:
esxcli system module parameters set -m lpfc -p "lpfc_enable_bg=1"
Additional module parameters can be added to this line, separated by spaces.
B.3 SCSI Command Support – SCSI Operation Codes
When there are both READ and WRITE requests, the CDB passed to the adapter from the initiator host has a read protect/
write protect (RDPROTECT/WRPROTECT) field that indicates to the target whether to perform data integrity verification. It also
indicates whether to transfer protection data between the initiator and the target. The adapter does not know if a target
supports protection information or the type of protection with which it has been formatted. The initiator host, which has this
knowledge, will always prepare a CDB with the appropriate RDPROTECT/WRPROTECT information, depending on the target
format and capabilities. The request also includes information about the protection type with which the target has been
formatted.
In addition, the initiator host will also provide the adapter with an operation code that tells the controller how to place the
protection data for the type of I/O to perform. Each I/O is logically a two-step process. The data is transferred between the
initiator host and the adapter (over the PCI bus) and between the adapter and the target (over the SAN) as shown in the
following figure. The type of operation defines whether the data transfer has protection data.
Figure 2: Data Transfer between the Initiator Host and the Adapter
The initiator operations are listed in the following table.
Table 12: Initiator Operations
Initiator Operation Initiator Host <-> Adapter Adapter <-> Target Comment
NORMAL Unprotected Unprotected Used for unprotected I/O.
READ_INSERT Protected Unprotected Reads the data from the target. The adapter then
generates the protection data and transfers both data
and protection data to the initiator host. No protection
data is sent on the SAN. The adapter can insert the
protection data Guard tag as a CRC or an IP checksum.
READ_PASS Protected Protected Reads the data and the protection data from the target
on the
SAN. The adapter verifies data integrity and
transfers both data and the protection data to the initiator
host. The adapter can convert the protection data Guard
tag from CRC to IP checksum.