Avatar of msidnam
Flag for United States of America asked on

Question regarding Host Profiles and reconnecting a host to a cluster

Hello everyone. We are in the process of updating the RAID controller firmware on our hosts due to an issue the current firmware that doesn't seem to be playing nice with ESXi 5.1U2. (See THIS link)

We move all of the VMs and templates from the host and then put it in maintenance mode. we turn off the host and update the firmware. Then what we did with a couple hosts is remove it from vCenter and then reinstall esxi (we want to make sure everything is fresh). We then add the host back to the cluster and apply a host profile that we took before shutting it down and reinstalling.

My 2 questions are:
1. When attaching and applying the host profile to the host it says its not compliant. Even though we copied it from the same host before uninstalling. Everything looks to be working but im not sure if im messing anything up by keeping it in a non compliant state.

2. I was thinking, instead of removing the host from the cluster i will just do the above and then reconnect it to the cluster. but im not sure if that will cause any problems. I'm pretty sure it will prompt me to accept the key again when re-adding but would anything else be messed up by doing it this way?

thank you.

Avatar of undefined
Last Comment
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

8/22/2022 - Mon
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Agreed. I'm just not sure what it is. i will need to go through the host profile and comb through i guess. But we kept all the adapters, vswitches and nics the same. we didn't change any hardware.

if i detach host profile does that remove all vswitches, dvswitches, etc?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Have you checked the vmnic order is the same, we've installed ESXi many times on different hosts, and found the vmnic order changes!

e.g. is the vmnic to physical nic mapping identical

Why you are reinstalling on firmware update? Maximum you may upgrade related hardware driver...
Your help has saved me hundreds of hours of internet surfing.

I guess i'm being overly cautious.

How would you get around in my place with >70 ESXi hosts?

With that many hosts, i think it would be to do some automation.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.

On the latest driver tune

One thing i see is that the Software iSCSI on a couple machines changed from vmhba39 to vmhba41. I then see in the profile things like:

Host state doesn't match specification: Rule 65435 of class VAAI needs to be deleted from the host

Specification state absent from host: device naa.6000402001d812bd7cd88a5500000000 parameters needs to be set to Is Perennially Reserved = "false"

Specification state absent from host: device eui.0011223344550001 parameters needs to be set to Is Perennially Reserved = "false"

The last two i think have to do with my SANs. I also see others like that.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

anything different, e.g. hba numbering can cause profiles to be non-compliant.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck

yes. it looks like my software iscsi adpater on a couple servers changed from vmhba39 to vmhba41

not sure why. probably something with 5.1?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

It always happens, random events can occur, when installing, and hba numbering changes, this can be rectified by editing the configuration files.