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
106
Emulex Drivers for VMware ESXi User Guide
The following table shows how protection data gets placed for each supported profile.
B.4.2 lpfc_prot_guard
This parameter specifies the type of CRC that the ESXi hypervisor passes to the lpfc driver. The following table shows the
three guard types: CRC, IP checksum, and TYPE_ALL with values of 0x1, 0x2, and 0x3 respectively.
The default value for lpfc_prot_guard is VMK_SCSI_GUARD_TYPE_ALL_VALID, which results in registering capabilities
for all guard types. This value defines the format for the Guard tag when the data is transferred between the host and the
adapter. When data is transferred on the wire, the protection data Guard tag is always translated into a T10 DIF CRC.
The SCSI layer typically uses an IP checksum as the method for computing the protection data Guard tag because it uses
less CPU overhead.
Table 14: Protection Data Placement for Supported Profiles
Flag Value BlockGuard Profile Operation
VMK_SCSI_TYPE1_PROT 1A1 READ_STRIP/WRITE_INSERT
VMK_SCSI_DIX_TYPE0_PROT 8 AST2 READ_INSERT/WRITE_STRIP
VMK_SCSI_DIX_TYPE1_PROT
VMK_SCSI_TYPE1_PROT
17 AST1 / C1 READ_PASS/WRITE_PASS
Table 15: lpfc_prot_guard Guard Types
Flag Value Indicates
VMK_SCSI_GUARD_CRC 1 Adapter supports T10 DIF CRC
VMK_SCSI_GUARD_IP 2 Adapter supports both T10 DIF CRC and IP checksum
VMK_SCSI_GUARD_TYPE_ALL_VALID 3 Adapter supports both T10 DIF CRC and IP checksum