All Posts

Marked correct for the reset from ESX console. Turned off didn't allow me to change the network config, but the reset did clear the network fields and allowed to choose the VM Network again. Thanks again for the help!

This is what I see when I attempt to change (or add a new) nic: Addition or reconfiguration of network adapters attached to non-ephemeral distributed virtual port groups (dpg_storage) is not supported.

Thanks! In the meantime, I was looking at this: https://kb.vmware.com/s/article/1008127 I don't understand the article though, its unclear what the example text should be; vmnic is which field exactly from the list commands shown above. The examples they give are unrelated to the fields from list command. I hope that makes sense. Or perhaps those steps won't help me? What do you think?

Where i find the TXT Feature, it doesn't show up ? CPU AES-NI Enabled System Password Empty Confirm System Password Empty Setup Password Empty Confirm Setup Password Empty Password Status Unlocked SHA256 hash of the System password Empty Salt string appended to the System password prior to hash Empty SHA256 hash of the Setup password Empty Salt string appended to the Setup password prior to hash Empty TPM Security On TPM Information Type: 2.0 NTC TPM Firmware 7.2.2.0 TPM Hierarchy Enabled TPM Advanced Settings AMD DRTM Off Power Button Enabled AC Power Recovery Last AC Power Recovery Delay Immediate User Defined Delay (120s to 600s) 120 UEFI Variable Access Standard SMM Security Mitigation Disabled Secure Boot Disabled Secure Boot Policy Standard Secure Boot Mode Deployed Mode Authorize Device Firmware Disabled UEFI CA Certificate Scope Device Firmware and OS  

Same issue today when running Update baseline compliance check on vSphere 8.0.1 Would also like to know where to check VUM logs.  2023-11-02T12:36:00.611-04:00 error vpxd[06334] [Originator@6876 sub=Default opID=1af4207b] [VpxLRO] -- ERROR lro-6892054 -- 525c07bb-81d3-888f-3734-5741e5c176cb(52f4f985-079c-f718-0ba8-b2eeffa66e1a) -- EsxHostAdvSettings-58 -- vim.option.OptionManager.queryView: :vim.fault.InvalidName --> Result: --> (vim.fault.InvalidName) { --> faultCause = (vmodl.MethodFault) null, --> faultMessage = <unset>, --> name = "UserVars.PXEBootEnabled", --> entity = <unset> --> msg = "Received SOAP response fault from [<<io_obj p:0x00007fb940858c98, h:67, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-58/vpxa>]: queryView --> Received SOAP response fault from [<<io_obj p:0x000000ae001516d8, h:26, <TCP '127.0.0.1 : 26382'>, <TCP '127.0.0.1 : 8307'>>, /sdk>]: queryView --> 'UserVars.PXEBootEnabled' is invalid or exceeds the maximum number of characters permitted." --> } --> Args: --> --> Arg name: --> "UserVars.PXEBootEnabled" 2023-11-02T12:36:00.649-04:00 error vpxd[06140] [Originator@6876 sub=Default opID=98c126a] [VpxLRO] -- ERROR lro-6892056 -- 525c07bb-81d3-888f-3734-5741e5c176cb(52f4f985-079c-f718-0ba8-b2eeffa66e1a) -- EsxHostAdvSettings-58 -- vim.option.OptionManager.queryView: :vim.fault.InvalidName --> Result: --> (vim.fault.InvalidName) { --> faultCause = (vmodl.MethodFault) null, --> faultMessage = <unset>, --> name = "UserVars.ImageCachedSystem", --> entity = <unset> --> msg = "Received SOAP response fault from [<<io_obj p:0x00007fb9684225a8, h:36, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-58/vpxa>]: queryView --> Received SOAP response fault from [<<io_obj p:0x000000adff823368, h:19, <TCP '127.0.0.1 : 56146'>, <TCP '127.0.0.1 : 8307'>>, /sdk>]: queryView --> 'UserVars.ImageCachedSystem' is invalid or exceeds the maximum number of characters permitted." --> } --> Args: --> --> Arg name: --> "UserVars.ImageCachedSystem"

Cleary, you didn't actually read the blog post ... it mentions nothing about checking all VMs. Please give it another read as the answer or your question is literally explained there.  Furthermore, its EXACTLY these types of use cases where Automation and the use of vSphere API is meant to help to search for various types of information and does not impact your workloads, especially when you look for specific things rather than returning the full VM configuration. 

Hi @hamidsattarrana , It looks to me more of browser cache related issue. Did we try to perform same action from any different browser? Also, Login to SSH of ESXi host and try below: df -h esxcfg-scsidevs -l https://kb.vmware.com/s/article/1014953 Above KB article has some commandlets to explore more onto storage side.