Search the VMware Knowledge Base (KB)
View by Article ID

Creating a host profile in vCenter Server 5.1/5.5 fails with the error: Invalid parameter type for parameter 'queueFullSampleSize' (2065692)

  • 2 Ratings

Symptoms

  • Cannot create a host profile from an ESXi 5.1/5.5 host in vCenter Server 5.1/5.5
  • Creating a host profile from an ESXi 5.1 or ESXi 5.5 host fails
  • You see the error: 

    Invalid parameter type for parameter 'queueFullSampleSize'

  • Host profile generation may succeed, but is non-compliant and has numerous datastore issues with the applied host.
  • In the vpxd.log file (located at: C:\ProgramData\VMware\VMware VirtualCenter\Logs), you see errors similar to:
[(vim.fault.ProfileUpdateFailed.UpdateFailure) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
profilePath = (vim.profile.ProfilePropertyPath) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
profilePath = 'storage.psa_psaProfile_PluggableStorageArchitectureProfile.psa_psaProfile_PsaDeviceConfigurationProfile["a3e610b019fce50ed4d82956be0c63bab94b37f7a81dae06f71e5f67eb438c2c"]',
policyId = 'psa.psaProfile.PsaDeviceConfigurationPolicy',
parameterId = 'queueFullSampleSize'
},
errMsg = (LocalizableMessageWithPath) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
key = 'com.vmware.vim.profile.host.UpdateError.InvalidParameterType.label',
arg = (vmodl.KeyAnyValue) [
(vmodl.KeyAnyValue) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
key = 'paramName',
value = 'queueFullSampleSize'
}
],
message = u"Invalid parameter type for parameter 'queueFullSampleSize'"
}
}, (vim.fault.ProfileUpdateFailed.UpdateFailure) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
profilePath = (vim.profile.ProfilePropertyPath) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
profilePath = 'storage.psa_psaProfile_PluggableStorageArchitectureProfile.psa_psaProfile_PsaDeviceConfigurationProfile["82c46f98ec3dbb40b18f46fd6a7872cdc4905b062f5e26dc263c064dd069c90c"]',
policyId = 'psa.psaProfile.PsaDeviceConfigurationPolicy',
parameterId = 'queueFullThreshold'
},
errMsg = (LocalizableMessageWithPath) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
key = 'com.vmware.vim.profile.host.UpdateError.InvalidParameterType.label',
arg = (vmodl.KeyAnyValue) [
(vmodl.KeyAnyValue) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
key = 'paramName',
value = 'queueFullThreshold'
}
],
message = u"Invalid parameter type for parameter 'queueFullThreshold'"
}
}, (vim.fault.ProfileUpdateFailed.UpdateFailure) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
profilePath = (vim.profile.ProfilePropertyPath) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
profilePath = 'storage.psa_psaProfile_PluggableStorageArchitectureProfile.psa_psaProfile_PsaDeviceConfigurationProfile["833532c61bf5c1ecff43c63a9b645d4162950e6c8545ede4cf3ce27fa078dd5c"]',
policyId = 'psa.psaProfile.PsaDeviceConfigurationPolicy',
parameterId = 'queueFullSampleSize'
  • When running the esxcli storage core device list command, you see one or more LUNs with a number of parameters without any value.

    For example:
    • naa.LUN_ID:
   Display Name:
   Has Settable Display Name: false
   Size: 0
   Device Type: No device type
   Multipath Plugin:
   Devfs Path:
   Vendor:
   Model:
   Revision:
   SCSI Level: 0
   Is Pseudo: true
   Status: off
   Is RDM Capable: false
   Is Local: false
   Is Removable: false
   Is SSD: false
   Is Offline: true
   Is Perennially Reserved: true
   Queue Full Sample Size: 1104400240
   Queue Full Threshold: 17
   Thin Provisioning Status: no
   Attached Filters:
   VAAI Status: unknown
   Other UIDs:
   Is Local SAS Device: false
   Is Boot USB Device: false
  • eui.LUN_ID:
   Display Name: 
   Has Settable Display Name: false
   Size: 0
   Device Type: No device type 
   Multipath Plugin: 
   Devfs Path: 
   Vendor: 
   Model: 
   Revision: 
   SCSI Level: 0
   Is Pseudo: true 
   Status: unknown
   Is RDM Capable: false
   Is Local: false
   Is Removable: false
   Is SSD: false
   Is Offline: true 
   Is Perennially Reserved: true 
   Queue Full Sample Size: 520810480
   Queue Full Threshold: 520810176
   Thin Provisioning Status: no
   Attached Filters: 
   VAAI Status: unknown
   Other UIDs: 
   Is Local SAS Device: false
   Is Boot USB Device: false
   No of outstanding IOs with competing worlds: 0

Cause

This issue occurs due to a dangling perennial reservation that persists for a LUN that is unpresented from the affected host. Normal operation is not impacted because the host is not utilizing the LUN. However, when vCenter Server attempts to create a host profile, it tries to validate the LUN information and is unable to complete because the parameters in the blank/malformed entry are not configured properly. 

These entries are created in the /etc/vmware/esx.conf file on the affected host that reference the unpresented LUNs. 
 

Resolution

To resolve this issue, references to LUNs that are not visible to the host must be removed from the /etc/vmware/esx.conf file:

Identifying LUNs with blank/malformed information:

  1. Connect to the affected host via SSH. For more information, see Using ESXi Shell in ESXi 5.0 and 5.1 (2004746).
  2. Run this command:

    esxcli storage core device list

  3. From the output, locate any LUNs that are missing any Display Name, Vendor, or Model information and are not currently in use by the ESXi host.

Removing LUNs that are blank/malformed:

After removing the LUNs, perform a rescan of the storage to refresh the information and then attempt to create a new host profile from the ESXi host.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 2 Ratings
Actions
KB: