Hello,

my virtual machine running on ESXi 5.5 host. we have prepared new 6.7 vSAN infra.

How to migrate old virtual machine on 6.7 vSAN infra ?

thanks

jackyroy

Hi all,

i'm trying to find an upgrade possibility to migrate/upgrade an existing vCenter server v5.1 to a VCSA appliance (doesn't matter which version). The goal is to get rid of the Server 2008 R2 server that it is now running on. If possible I would like to leave the 5.1 ESXi hosts on version 5.1 and not upgrade them.

What would be the best solution or steps to achieve this? I can only find upgrades from Windows=>Windows or appliance=>appliance.

Hope you can help me on this

Hi, I need to upgrade the version of ESXi to v7 (from 6.7.0 U2) on our HP ProLiant DL380 Gen9 server.

I have patched the server's firmware so it can support v7, but on running the upgrade command I get the following errors :0

VIB QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820 requires vmkapi_2_2_0_0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

I'm using a custom ESXI package as follows :-

VMware-ESXi-7.0.0-16324942-HPE-700.0.0.10.5.5.32-Jun2020-depot.zip

I'm a bit nervous about removing those VIBs without knowing what thet are for, can anyone advise if these are safe to remove ? Thanks.

The upgrade was triggered from the vApp Management page.  Since it was stuck at 0%, all I every get is the progress screen.

Going from 7.0.0.10600 to the 7.0.1.00000

Regular HTML5 UI is fine and I can login and still use vCenter, it's like the update isn't even happening.

From SSH/Shell, I can see that the upgrade is "in progress" but not doing anything:

root@localhost [ ~ ]# cat /etc/applmgmt/appliance/software_update_state.conf

{

    "state": "INSTALL_IN_PROGRESS",

    "version": "7.0.1.00000",

    "latest_query_time": "2020-10-08T15:43:36Z",

    "operation_id": "/storage/core/software-update/install_operation"

}root@localhost [ ~ ]# cat /storage/core/software-update/install_operation

{

    "cancelable": true,

    "description": {

        "args": [],

        "default_message": "Install update",

        "id": "com.vmware.appliance.update.install_operation_description"

    },

    "end_time": null,

    "last_updated_time": "2020-10-08T16:05:00.791Z",

    "operation": "install",

    "progress": {

        "completed": 0,

        "message": {

            "args": [],

            "default_message": "Install in progress",

            "id": "com.vmware.appliance.update.install_task_message"

        },

        "total": 100

    },

    "service": "applmgmt/update",

    "start_time": "2020-10-08T16:05:00.791Z",

    "status": "RUNNING",

    "subtask_order": [

        "install"

    ],

    "subtasks": {

        "install": {

            "cancelable": true,

            "description": {

                "args": [],

                "default_message": "Installing the update",

                "id": "com.vmware.appliance.update.install_task_description"

            },

            "end_time": null,

            "last_updated_time": "2020-10-08T16:05:00.791Z",

            "operation": "install",

            "progress": {

                "completed": 0,

                "message": {

                    "args": [],

                    "default_message": "Install in progress",

                    "id": "com.vmware.appliance.update.install_task_message"

                },

                "total": 100

            },

            "service": "applmgmt/update",

            "start_time": "2020-10-08T16:05:00.791Z",

            "status": "RUNNING"

        }

    }

Pre checks succeeded, but I'm just waiting on this and there is no clear message in the applmgmt.log as to what is wrong/trying to be done.

Any help would be appreciated.

I am trying to setup a vCenter 7.0 server on Workstation 16Pro to do some testing in a lab environment. For the life of me I cannot get past this. I have a AD server running with DNS. A and PTR records are in place and tested. I deploy the VCSA appliance via the OVA in workstation. Connect to it over port 5480 and cannot get past this. This is the IP I deployed the VCSA VM on, and it pings fine. Any suggestions? Pulling my hair on this one. Erroring with Unable to Save IP Settings.

Hi,

I have a installed a VCSA 7.0 U1, it works fine. During the vCenter Server configuration of the network settings I have a probleme with the FQDN for the system name. When I try the IP Address or the FQDN I get the answer  saving of the IP configuration not possible. When I connect over SSH to the server I can check with nslookup the DNS configuration without problem, forward and backword. Now I hang in the configuration with no way out.

How can help me to finish my configuration to work with the VCSA.

Thanks for help

Bernd

Hello to everyone,

I am running a lab trying to see how Auto Deploy works.

According to the documentation for security reasons, Auto Deploy traffic should be isolated from the management network. But it seems that I can't find any resource/guide with this configuration.

My management network is VLAN 10, 172.16.10.0/24

VCSA, 172.16.10.20

Esxi host 1, 172.16.10.2 (Management NICs, vmnic0, vmnic1)

I created a new VLAN 201 for the Auto Deploy traffic.

TFTP server 172.16.201.20

In my Auto Deploy rule, I have only an image. I don't use host profile for now.

I have a new host that I want to provision. Identical hardware to esxi host 1.

I connect a NIC to VLAN 201.

Esxi host 2 boots and the deployment starts.

According to documentation, host should be added to the Datacenter in Vcenter.

The problem is that when boot is completed, the esxi host 2 has an IP from the range of VLAN 201 and not from VLAN 10. Thus, esxi host 2 is not added to Vcenter.

Any ideas how I can make this work?

Thank you in advance for your help.

In the past, when Dell provided their version of an update to Esxi, you could download it in the form of a zip file. You then applied it in this manner (from the esxi command line):

esxcli software profile update -d /VMware-VMvisor-Installer-7.0.0-15843807.x86_64-DellEMC_Customized-A00.zip -p DEL-ESXi-700_15843807-A00

When you go to the Dell website and attempt to download the latest version (Version 7.0, A02), the files are no longer there and, instead you are met with this message:

"Dell EMC has migrated the latest revision of the Dell customized ESXi images with customized drivers to VMware's website. This change aligns with industry-standard practices and brings the Dell EMC-customized image to the same location as our competitors. For customers who manage heterogeneous fleets, this simplifies the procurement of SW images as they will all be housed in one location. Please go to your my.vmware.com license portal or click the link below to be redirected now. Older revisions of these images can be downloaded from www.dell.com/support in case there is a requirement

ISO Image Link: https://my.vmware.com/en/web/vmware/downloads/details?downloadGroup=OEM-ESXI70GA-DELLEMC&productId=974"

One you go to the link provided, you no longer have any file available except the ISO file. I know of no way to upgrade from the command line via the ISO file.

Any ideas?

Hi,

So I'm trying to upgrade from 6.0 to 6.5 U3 and I followed several articles and videos and booted to the ISO that I burned from myvmware account. The host is an HP Proliant ML350 G9.  I get to the first few steps, but then get this message and can't upgrade: 

https://www.altaro.com/vmware/upgrade-datastores-vmfs-6/

I've been looking at this article about VMFS datastores and not sure if this applies to my situation. Any ideas of what I need to do? This is the current version:

Looks like I have VMFS5

Greetings,

I recently upgraded my VCSA to 6.7, and now wanted to upgrade my 3 Fujitsu servers through VUM. Everything went fine at the beginning, the upgrade got stuck at 47%. After Some while I took a look at the server console, and found the attached error message (sorry for not having the logs copied).

Apparently I need to disable the corresponding vib-files. I tried the following commands:

esxcli software vib remove -n lsiprovider

esxcli software vib remove --vibname vmware-esx-storcli-1.17.08

But got in both cases the following error message:

[DependencyError]

VIB VMware_locker_tools-light_10.3.10.12406962-14141615 requires esx-version >= 6.6.0, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

I tried to update using the latest 6.7 Fujitsu Custom ISO.

How should I proceed here? Would it be an option to upgrade with the regular, non-custom ISO? If so, how can I install the management software from Fujitsu afterwards by hand?

Thanks

Joshi

I am trying to get a VMware environment updated for a company still on 6.0. Their Vcenter is running on Server 2012r2 with an embedded Platform Services Controller and embedded database. Update Manager is also on this server. When I run the migration assistant, it comes back with an internal error during the pre-upgrade checks. Support flagged the following errors after examining the zip file that got generated, but they don't seem to be very willing to go too far with me on this since 6.0 is out of general support. Hoping someone on here can help me determine how I can get the migration tool working. Thanks!

Migration action from version 6.0.0 to 6.7.0
Error Detail:
Internal error occurs during VMware vCenter Server Database pre-upgrade checks.
2020-10-10T02:45:55.265Z WARNING wf.wf_processor State CollectRequirements com.vmware.vcdb has failed.
2020-10-10T02:45:55.265Z ERROR wf.wf_processor Workflow execution has failed

CollectRequirements_com.vmware.vcdb_2020_10_09_22_45.log
2020-10-10T02:45:15.762Z INFO vcdb.const DB type: embedded
2020-10-10T02:45:15.763Z INFO vcdb.const Validating source embedded schema...
2020-10-10T02:45:54.436Z INFO vcdb.const Source embedded schema validation completed.
2020-10-10T02:45:54.540Z ERROR __main__ Upgrade Phase 'vcdb:CollectRequirements' failed. Exception: (u'42P01', u'[42P01] ERROR: relation "user_segments" does not exist;\nError while executing the query')

Hey Guys,

I try upgrade my free version of esxi from 6.0 build-15517548 to 6.5 or 6.7 but everytime my server boot i get purple screen.

I upgrade like this to 6.5:

esxcli network firewall ruleset set -e true -r httpClient

esxcli software profile update -p ESXi-6.5.0-20200704001-standard \

-d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

esxcli network firewall ruleset set -e false -r httpClient

or to 6.7:

esxcli network firewall ruleset set -e true -r httpClient

esxcli software profile update -p ESXi-6.7.0-20200804001-standard \

-d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

esxcli network firewall ruleset set -e false -r httpClient

Best Regards

TaKeN

while installing ESXi 7.0  I kept getting password do not match after setting my root password. I  have tried different password but it still did not take. What can I do or can anybody suggest a good password that meet the requirement ?

I just upgraded to 7.0 u1 from 7.0 and it appears to be fine except the applmgmt gui keeps displaying this:

And appears to be stuck.

Yet All logs appear normal with no errors and all services are running.  vcenter says 7.0.1.:

root@vc6 [ /var/log/vmware ]# vpxd -v

VMware VirtualCenter 7.0.1 build-16858589

Running:

applmgmt lookupsvc lwsmd observability observability-vapi pschealth vlcm vmafdd vmcad vmdird vmonapi vmware-analytics vmware-certificateauthority vmware-certificatemanagement vmware-cis-license vmware-content-library vmware-eam vmware-envoy vmware-hvc vmware-infraprofile vmware-perfcharts vmware-pod vmware-postgres-archiver vmware-rbd-watchdog vmware-rhttpproxy vmware-sca vmware-sps vmware-statsmonitor vmware-stsd vmware-topologysvc vmware-trustmanagement vmware-updatemgr vmware-vapi-endpoint vmware-vdtc vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-ui vstats vtsdb wcp

Stopped:

vmcam vmware-imagebuilder vmware-netdumper vmware-vcha

I see in the log /var/log/vmware/applmgmt/update_microservice.log the following:

2020-10-20 01:18:45,451 - 59346 -        update_script::_executePatchRunnerAndSupplyUserData: 127 -    ERROR - Patch command patch failed

2020-10-20 01:18:45,460 - 59346 -        update_script::                _reportFailure: 159 -    DEBUG - Error status has been already reported

2020-10-20 01:18:45,464 - 59346 -           extensions::                      __call__: 107 -    DEBUG - The component script returned 'None'

2020-10-20 01:18:45,523 - 17819 -           update_b2b::                _runScriptHook: 344 -    DEBUG - update script result file '{\n    "end_time": "2020-10-20T01:18:45.232Z",\n    "error": {\n        "componentKey": "last_component:Patch",\n        "detail": [\n            {\n                "id": "ur.services.start.text",\n                "localized": "Failed to start all services after successful patching.",\n                "translatable": "Failed to start all services after successful patching."\n            }\n        ],\n        "problemId": null,\n        "resolution": null\n    },\n    "info": [],\n    "progress": 47,\n    "progress_message": {\n        "componentKey": "last_component:Patch",\n        "detail": [\n            {\n                "id": "ur.services.start.text",\n                "localized": "Failed to start all services after successful patching.",\n                "translatable": "Failed to start all services after successful patching."\n            }\n        ],\n        "problemId": null,\n        "resolution": null\n    },\n    "question": null,\n    "start_time": "2020-10-20T00:41:48.003Z",\n    "status": "error",\n    "warning": [\n        {\n            "msg": {\n                "id": "ur.services.retry.start.text",\n                "localized": "Failed to start all services, will retry operation.",\n                "translatable": "Failed to start all services, will retry operation."\n            },\n            "problemId": null,\n            "resolution": null\n        }\n    ]\n}'

2020-10-20 01:18:45,537 - 17819 -           update_b2b::                _runScriptHook: 362 -    DEBUG - Returning notifications {'errors': [{'id': 'com.vmware.apliance.noid', 'time': '2020-10-20T01:18:45.537Z', 'message': {'id': 'ur.services.start.text', 'default_message': 'Failed to start all services after successful patching.', 'args': []}, 'resolution': None}], 'info': [], 'warnings': [{'id': 'com.vmware.appliance.noid', 'time': '2020-10-20T01:18:45.536Z', 'message': {'id': 'ur.services.retry.start.text', 'default_message': 'Failed to start all services, will retry operation.', 'args': []}, 'resolution': None}]} from _runScriptHook

2020-10-20 01:18:45,537 - 17819 -           update_b2b::                       install:2265 -    DEBUG - PostInstall errors: [{'id': 'com.vmware.apliance.noid', 'time': '2020-10-20T01:18:45.537Z', 'message': {'id': 'ur.services.start.text', 'default_message': 'Failed to start all services after successful patching.', 'args': []}, 'resolution': None}]

2020-10-20 01:18:45,544 - 17819 -         task_manager::                        update:  79 -    DEBUG - UpdateTask: status=FAILED, progress=80, message={'id': 'com.vmware.appliance.postinstall_errors', 'default_message': 'Data conversion/Post install hook failed', 'args': []}

2020-10-20 01:18:45,664 - 17819 -          dbfunctions::                    executeDML:  54 -    DEBUG - Executing Query {INSERT INTO progress VALUES(NULL, ?,         DATETIME('now'), ?, ?, ?)} with parameters ('failed', 'Installation failed', 100, 95)

2020-10-20 01:18:45,684 - 17819 -           update_b2b::                       install:2272 -    DEBUG - Returning from install(), data conversion failed

Did the upgrade work?  It apear to have but the dialog will not go away.  If it is okay how can I reset this so the dialog goes away and the alliance management interface UI is usable again?

I have a snapshot and could rollback.

Regards,

dion

Id like to update vCenter and ESXI without having a gateway on my Management Network as denoted in vCenter. Instead I would like to update using the second nic connected to vCenter which does have a gateway and allows only vCenter updates though.

My lab is air gapped. I dont want to expose management services to the public internet. I will only use this other NIC1 as the update NIC, using vCenter as a ?proxy? tot he ESXI hosts.

If I need to I can put a VMK on the ESXI hosts to reach the public as well, but would rather not put Management services on that VMK. This would allow my system to be connected from the Public Network, defeating the idea of Air Gapped - I will only use this second connection while updating vCenter and ESXi hosts.

NIC0 - Management Network - No Gateway

NIC1 - DHCP with access to Internet (no management services assigned)

Is this possible? Am I missing something?

Maybe I should just make a soft proxy vm or something.

Thanks,

Eric

Hi,

I was having issues with 6.5 and rather than reinstalling, I stupidly upgraded to 7.0, which doesn't see much of the server's hardware, including the drive it's installed on as a datastore, even though under 6.5 it did.  My fault, I know.  I have now downloaded 6.5 and reinstalled it over 7.0 and it sees the hardware and datastore... but for some reason, I can't even see the 7.0 license, which I'm sure doesn't work for 6.5 anyway,.. but if doing the upgrade changed the license key to 7... how do I downgrade it to 6.5?  And if I don't need to downgrade it, but use my previous 6.5 license... how do I even get that back since when I click on anything that should point to my licenses the site just gives me an error and says that page isn't available.

Thoughts?

Thanks!

-Mark

Hi, please help me!

ESXI 7.0u1 no disk present to install flex system x240 (ibm blade system mt8721hc1)

Hello,

We are currently seeing the following error when upgrading to VCSA 7.0 from 6.7, this error occurs durning step 2 of the new VCSA.

Error

Encountered an internal error. Traceback (most recent call last): File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1752, in main vmidentityFB.boot() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 367, in boot self.registerTokenServiceWithLookupService() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 654, in registerTokenServiceWithLookupService raise e File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 650, in registerTokenServiceWithLookupService dynVars=dynVars) File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 710, in cloudvm_sso_cm_register serviceId = do_lsauthz_operation(cisreg_opts_dict) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 1058, in do_lsauthz_operation ls_obj = LookupServiceClient(ls_url, retry_count=60) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 314, in __init__ self._init_service_content() File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 294, in do_retry return req_method(self, *args, **kargs) File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 304, in _init_service_content self.service_content = si.RetrieveServiceContent() File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 556, in <lambda> self.f(*(self.args + (obj,) + args), **kwargs) File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 368, in _InvokeMethod return self._stub.InvokeMethod(self, info, args) File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1448, in InvokeMethod conn.request('POST', self.path, req, headers) File "/usr/lib/python3.7/http/client.py", line 1252, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1298, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1247, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.7/http/client.py", line 1026, in _send_output self.send(msg) File "/usr/lib/python3.7/http/client.py", line 966, in send self.connect() File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1085, in connect six.moves.http_client.HTTPSConnection.connect(self) File "/usr/lib/python3.7/http/client.py", line 1414, in connect super().connect() File "/usr/lib/python3.7/http/client.py", line 938, in connect (self.host,self.port), self.timeout, self.source_address) File "/usr/lib/python3.7/socket.py", line 727, in create_connection raise err File "/usr/lib/python3.7/socket.py", line 716, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused

Resolution

This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.

We are currently unsure why this error is occurring. This error appears as the Security Token Service (STS) is starting up during the install.

I'm currently running ESXi 6.0 on an HP ML350 G6 server for home lab uses. I have 3 VMs on it at the moment and my needs are pretty minimal. It's stable and works so perhaps I shouldn't rock the boat, but I can't help but wonder...

What benefits come with 7.0 that I might enjoy if any? Also, I know some of the hardware in my server is no longer supported officially, but if I just upgrade from current version would the existing drivers be preserved?

Hi COmmunity,

hope you can help me with this one.

I have this issue with multiple Customers at multiple sites.

I usually patch the Servers with the help of https://esxi-patches.v-front.de/ESXi-6.7.0.html

It shows in 3 simple commands (firewall off, update, firewall on) how to patch the ESX Server.

That worked fine in the past.

Nowadays, I almost always get the following issue:

[root@Server:~] esxcli software profile update -p ESXi-6.7.0-20201004001-standard \

> -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[OSError]

[Errno 28] No space left on device

Please refer to the log file for more details.

Sometimes it lists nothing like shown here, sometimes it lists a specific vib that has not enough space.

I've enabled swap and I have roughly 1TB of free space.

It affects all of my Servers (6.0, 6.5, 6.7 and 7.0)

ANY hint is greatly appreciated.