Host profile non-compliant when checked against reference host!

[JayDeah]

i have a configured ESXi5.0 host which i created a host profile from, when i check compliance against it it fails with the following:

Expected user input parameters missing. Check answer file for host.

iSCSI Adapter IQN on the system for iSCSI adapter vmhba39 does not match to the one configured in the profile

Could not select an iSCSI HBA for the profile instance: 14fb1454020056c323baab7b01f5ca316c125c868498d3740a248be490b652ee. One of following may be true: (1) The Answer File is missing some of the required user-input parameters (2) The system does not have a matching hardware for the given 'Initiator Selection Policy'

Could not select an iSCSI HBA for the profile instance: 3ffe3a2f42e711212c5d14f39fb335a687a9a86415d2ef2ecf0adb4d8fda27b8. One of following may be true: (1) The Answer File is missing some of the required user-input parameters (2) The system does not have a matching hardware for the given 'Initiator Selection Policy'

Could not select an iSCSI HBA for the profile instance: 8f27c5010418bf4bd6a49bab8f65612135ba3e6e8bc71db9934c72668eefa22a. One of following may be true: (1) The Answer File is missing some of the required user-input parameters (2) The system does not have a matching hardware for the given 'Initiator Selection Policy'

Could not select an iSCSI HBA for the profile instance: 7855e687a7306e5c9dc810fb6642631b784add30fad266445db22458274057e8. One of following may be true: (1) The Answer File is missing some of the required user-input parameters (2) The system does not have a matching hardware for the given 'Initiator Selection Policy'

if i try and apply the profile it fails

i am using the SWISCSI adapter and it is vmhba39, it has 2x vmks/vmnics associated with it with MPIO going to an MD3200i

[admin]

Update your answer file for this to work.

Right click on the host, update answer file, save. Check for compliance..

[JG271269]

We have experienced the same issue and traced it to multi-function NICs. These NICs have both a network and iSCSI function and, when the iSCSI functionality is enabled an iSCSI hardware initiator is created.

If you disable this secondary function, the hardware initiator disappears. If you subsequently create a profile from this host, the error about the iSCSI HBA disappears.

For us, this fixed the issue.