View Only
  • 1.  Cannot chage the Host Configuration

    Posted Nov 02, 2016 09:31 PM

    I am running vCenter 6.5RC on a ESXi 6.5 host.

    I have external storage connected via iSCSI

    After I present my volume to ESX, I try to create a datastore.

    During the datastore creation I get the following error message:

    Cannot change the host configuration.

    Does anyone know why this may be happening?

    What logs should I loook at.

    Thank you

  • 2.  RE: Cannot chage the Host Configuration

    Posted Apr 06, 2017 01:35 AM

    You can check for the esxi vmkernel logs and vCenter vpxd log

    In my opinion, this could be

    1. vCenter Beta/RC issue

    cannot change the host configuration

    workaround/resolution: add storage directly from ESXi host

    upgrade vCenter if possible

    2. Has some partitions that VMware cannot write

    resolution: use partedutil to fix the issue

    3. MTU mismatch

    VMware vSphere error “Cannot change the host configuration” adding storage | Vodka RedBull Please

    resolution: review MTU configuration end to end

    Most likely issue #1

  • 3.  RE: Cannot chage the Host Configuration

    Posted Apr 06, 2017 02:23 AM

    This is a tough one and I could not really find anything except what Bayu already listed. As a troubleshooting step, are you able to try to make a local VMFS datastore? Perhaps this could narrow it down to a SAN issue.

    If this were an older version of ESXi then that same error could have been blamed on a LUN size over 2TB, but that limit has since been raised to 64TB.

  • 4.  RE: Cannot chage the Host Configuration

    Posted Nov 17, 2017 11:20 PM

    I have the same issue. What was the solution? I am leaning towards a bug in 6.5?

    As I had to label local scsi disk to make them become a VMware datastore.

    The storage presented to vSphere by the VNXe fails any way shape or form. It's almost like it does not have the rights to write to the gpt partitions. I cannot add labels using partedUtil. Stumped.

    cpu13:65862)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60060160ce904500aaff0d5a47e06304" state in doubt; requested fast path state update...

    2017-11-17T14:38:42.884Z cpu13:65862)ScsiDeviceIO: 2962: Cmd(0x439501285f80) 0x2a, CmdSN 0x3 from world 111270 to dev "naa.60060160ce904500aaff0d5a47e06304" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

    2017-11-17T14:38:42.884Z cpu0:111270)BC: 2466: Failed to write (uncached) object 'naa.60060160ce904500aaff0d5a47e06304': Timeout

    2017-11-17T14:38:45.654Z cpu12:66254)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x4306846c74f0 network resource pool netsched.pools.persist.iscsi associated