VMware Cloud Community
sunvmman
Enthusiast
Enthusiast
Jump to solution

cannot change the host configuration

i shutdown my vm that is on emc san drives and zoned it for a second esx server.

when i scan i can see the disks but i do not see a datastore. so i try add storage, keep signature and it tells me "cannot change the host configuration"

1) what do i do 2) i tried vmotion and it didn't work

Reply
0 Kudos
1 Solution

Accepted Solutions
Troy_Clavell
Immortal
Immortal
Jump to solution

this is happening within vCenter, correct? I had this happen in beta. Log into your ESXi Host and then "add storage"

View solution in original post

Reply
0 Kudos
10 Replies
Troy_Clavell
Immortal
Immortal
Jump to solution

this is happening within vCenter, correct? I had this happen in beta. Log into your ESXi Host and then "add storage"

Reply
0 Kudos
sunvmman
Enthusiast
Enthusiast
Jump to solution

Yes, this is happening via virtual Center. So now by going directly to the server i was able to bring up the machine etc.

But now i tried to vmotion the vm back to the original esx server and it tells me it can not find the rdm's. so it seems that if i go directly to the server it works but via virtual center it doesn't. That is a big problem how do i vmotion

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

does it make sense to restart the virtual center service from ESX? i.e. vmware-vpxa service after removing the server from Virtual center. then add the server back to the datacenter?

Reply
0 Kudos
mtnbiker5
Contributor
Contributor
Jump to solution

I am having a similar issue - although maybe not exactly the same. I have 4 new Vsphere hosts - when I go to add storage, I can see the shared LUN that my other hosts can see, but when I go to finish the process, I get an error which states "cannot change host configuration" and the storage does not get added.

Everything seems to be configured the same on all of these servers. Anyone have an idea or a starting point?

Reply
0 Kudos
JimmyDean
Enthusiast
Enthusiast
Jump to solution

I'm having the same issues. I have been working on this issue for the last few days...

Reply
0 Kudos
sunvmman
Enthusiast
Enthusiast
Jump to solution

the correct way to do this is to add the lun to the machine .. it will give it a signature that will allow you to automatically add to any machine

Reply
0 Kudos
mtnbiker5
Contributor
Contributor
Jump to solution

I found the answer to my situation - essentially it appeared that I had a signature issue. What I did was to remove the 2 VM's from the inventory (This is a pre production installation so that was not a big deal), then go to add storage, add a LUN and then chose the option to create a new signature. Once I did that, all of my VM hosts simply saw the storage as they should. The one thing that was interesting was that when the newly found storage came on line - it had a prefix of SNAP, which means to me that I had some sort of conflict between the one host that could see the storage and the others that couldn't. I simply renamed the storage, rebooted the host with the conflict and all 8 see the storage and seem happy. The last step was to simply re-add the VM's back onto the inventory.

Reply
0 Kudos
patchezz
Contributor
Contributor
Jump to solution

The solution is to use the vSphere client to connect directly to the

host, not Virtual Center, and add the LUNs there. Works perfectly and

they show up in Virtual Center as you’re adding them.

Reply
0 Kudos
juchestyle
Commander
Commander
Jump to solution

Yeah, the answer is there, connect to the esx not vCenter. Worked like a champ for me too!

Matthew

Kaizen!
Reply
0 Kudos
juchestyle
Commander
Commander
Jump to solution

I have to laugh at the irony.  I read the last post from some guy named juchestyle, and thought some internal thoughts.  Then I realized that was me.

Here is what I have learned since then.  logging directly into the ESX may not solve the underlying issue.  It will allow you to add, but that doesn't mean the issue is resolved.  Figure out why a lun(s) won't add into everything properly, it should, if it doesn't there is an issue that will bite you later if you ignore it.

I figured that out after I posted the last post.  (reason why I was shaking my head at the lack of experience I had on this issue back then.

Respectfully (even to my past self),

Matthew

Kaizen!
Reply
0 Kudos