This article provides an overview of VMID, benefits, configuration guidance, and how it relates to performance.
VMware vSphere ESXi
VMID tags are able to be utilized by Fibre Channel (FC) switches, hypervisors, and software, to enhance visibility to identify FC data flowing through network infrastructure.
Use the following command in ESXi shell to verify if VMID is enabled:
# /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i MOD_PARM/qlogic -k DRIVERINFO -g | grep ql2xvmidsupport
Output: ql2xvmidsupport = 1
ql2xvmidsupport = 0
ql2xvmidsupport = 1
Use the following command in ESXi shell to verify if VMID is enabled:
# /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -i vmhbaX/Emulex -k vmid -g
‘X’ in ‘vmhbaX’ is a number:
Output: Key 'vmid':
lpfc VMID page: on
lpfc VMID page: off
” will be shown in the output.lpfc VMID page: on
” will be shown in the output.To enable, please use the following commands:
# esxcli system module parameters set -m qlnativefc -p 'ql2xvmidsupport=1'
# reboot
Set up the driver parameters to enable VMID on your ESXi host. For example:
# esxcli system module parameters set -p "lpfc_max_vmid=8 lpfc_vmid_app_header=1" -m lpfc
# reboot
lpfc_max_vmid
is the driver parameter that indicates the number of VMID VMs supported.
lpfc_vmid_app_header
is the driver parameter that enables Brocade VMID support on ESXi.
Set up the driver parameters to enable VMID on your ESXi host. For example:
# esxcli system module parameters set -p "lpfc_max_vmid=8, lpfc_vmid_priority_tagging=1" -m lpfc
# reboot
lpfc_max_vmid
is the driver parameter that indicates the number of VMID VMs supported.
lpfc_vmid_priority_tagging
is the driver parameter that enables Cisco VMID support on ESXi. The possible values are:
# esxcli system module parameters set -m qlnativefc -p 'ql2xvmidsupport=0'
# reboot
# esxcli system module parameters set -p "lpfc_vmid_app_header=0" -m lpfc
# reboot
# esxcli system module parameters set -p "lpfc_vmid_priority_tagging=0" -m lpfc
# reboot
Enabling VMID in Fibre Channel drivers may cause a minimal performance impact during intense I/O processing. The extent of this impact can vary based on available compute resources, workload, and other factors. Note that no errors, logs, or messages will be generated.
Potential impacts may include:
The delay which may impact performance is expected behavior since the driver I/O stack needs to perform a lookup for every I/O.
To mitigate effects arising out of VMID tagging, the user can disable tagging as outlined above.