Dynamically adding luns, Dynamically adding targets, Fc/fcoe driver configuration parameters – Dell Emulex Family of Adapters User Manual
Page 1013: Table 3-1
Emulex Drivers Version 10.2 for VMware ESXi User Manual
P010087-01A Rev. A
3. Configuration
FC and FCoE Driver Configuration
1013
Dynamically Adding LUNs
For instructions on dynamically adding LUNs, refer to the “Using Rescan” section of
the VMware SAN Configuration documentation.
Dynamically Adding Targets
VMware does not provide a native mechanism for this process. After all target/LUN
configuration steps have been successfully completed, add the target to the intended
fabric zone.
To get the driver to log into the target, either the target or initiator link must be
bounced. If the target is configured with security ACLs, the same link bounce
requirement applies after the security ACLs are corrected.
To force the ESXi server to rescan all devices:
Run the following command:
esxcfg-rescan vmhbaX
-Or-
From the vSphere Client, click Configuration Tab > Storage Adapters, and
then click Rescan All.
FC/FCoE Driver Configuration Parameters
Table 3-1, FC and FCoE Driver Parameters, lists the FC and FCoE driver module
parameters, their descriptions, and their corresponding values in previous ESXi
environments and in ESXi 5.5 native mode.
Note: For ESXi 5.0 and 5.1 systems, all adapter-specific parameters must have an
lpfcX_ prefix (where X is the driver instance number). For example, setting
lpfc0_lun_queue_depth=20 makes 20 the default maximum number of
commands that can be sent to a single logical unit (disk) for lpfc instance 0.
Dynamic parameters do not require a system reboot for changes to take effect.
Table 3-1 FC and FCoE Driver Parameters
Module
Parameter
Description
ESXi 5.0, 5.1
Legacy
Driver Model
Values
ESXi 5.5 OP
Native Mode
Driver Model
Values
Comments
throttle_log_cnt Do not exceed this number
of messages logged within
‘throttle_log_time’
Default (Def) =
10
Minimum (Min)
= 1
Maximum (Max)
= 1000
For the native mode
driver.
Logging mechanism
intended to speed up
issue diagnosis by
reducing the necessity
to enable driver
logging.