VMware Global Community
blackflamenco
Contributor
Contributor

Error al actualizar al vCenter 6.7 Update1

Buenos días,

Estoy teniendo a la hora de correr el asistente de migración de vCenter 6.7 U1.

En el paso de de configurar el acceso al appliance de vCenter y al host ESXi me dice "Unable to find the source appliance on the specified ESXi host or vCenter Server."

He revisado que todos los datos son los correctos como muestro en la imagen. Mi vCenter es la IP 192.168.0.102 y el servidor ESXi donde se encuenta la maquina virtual de vCenter es 192.168.0.106.

pastedImage_0.png

El log me indica un error que no me ayuda mucho:

2018-10-30T12:17:45.584Z - info: installerLogFile: C:\Users\Francis\AppData\Local\Temp\vcsaUiInstaller\installer-20181030-131745581.log

2018-10-30T12:17:45.620Z - info: networkLogFile: C:\Users\Francis\AppData\Local\Temp\vcsaUiInstaller\network-20181030-131745581.log

2018-10-30T12:18:08.801Z - debug: wizardTitle: Upgrade - Stage 1: Deploy appliance

2018-10-30T12:18:48.068Z - info: getDeploymentType() on source VC:192.168.0.102

2018-10-30T12:18:48.069Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:18:50.186Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:18:50.219Z - debug: session does not exist: 192.168.0.102,

2018-10-30T12:18:50.220Z - debug: Logging in to 192.168.0.102:443 as

2018-10-30T12:18:53.244Z - error: Failed to login to 192.168.0.102:443 as : ServerFaultCode: Cannot complete login due to an incorrect user name or password.

2018-10-30T12:19:24.111Z - info: THUMBPRINT(vCenterAppliance): 09:5D:E2:F8:54:DC:46:1D:9A:A6:3A:29:A3:8D:4C:13:EF:7B:B4:3A

2018-10-30T12:19:24.135Z - info: THUMBPRINT(esxiHost): 9C:3E:A7:ED:C9:07:8A:EE:DF:A4:99:CD:96:15:46:A7:D7:92:14:E2

2018-10-30T12:19:24.868Z - info: attemptHttpsConnToSourceVc

2018-10-30T12:19:24.907Z - info: login() to source VC:192.168.0.102

2018-10-30T12:19:24.907Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:19:24.974Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:19:24.998Z - debug: session does not exist: 192.168.0.102, administrator@vsphere.local

2018-10-30T12:19:24.998Z - debug: Logging in to 192.168.0.102:443 as administrator@vsphere.local

2018-10-30T12:19:25.111Z - info: Logged in to 192.168.0.102:443 as administrator@vsphere.local, session: 52308adf-a7b8-5e27-423e-988546287009

2018-10-30T12:19:25.112Z - info: Login successful to source VC, IP: 192.168.0.102

2018-10-30T12:19:25.112Z - info: login() to host managing the source VC:vm01.cpsi.local

2018-10-30T12:19:25.112Z - info: initializing vsphere API connection to vm01.cpsi.local:443

2018-10-30T12:19:26.065Z - info: vimService apiType: HostAgent, version: 6.5.0

2018-10-30T12:19:26.095Z - debug: session does not exist: vm01.cpsi.local, root

2018-10-30T12:19:26.095Z - debug: Logging in to vm01.cpsi.local:443 as root

2018-10-30T12:19:26.182Z - info: Logged in to vm01.cpsi.local:443 as root, session: 52568a7c-5ab7-389c-8b6d-042e83afb791

2018-10-30T12:19:26.182Z - info: Login successful to host for source VC, IP: vm01.cpsi.local:443

2018-10-30T12:19:26.183Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

2018-10-30T12:19:26.183Z - info: Source VC, version: 6.5.0, isOSLinux: true

2018-10-30T12:19:26.184Z - debug: isIp: 192.168.0.102: true

2018-10-30T12:19:26.185Z - debug: getVmWithIPFQDN: hostName 192.168.0.102 is associated with [ '192.168.0.102' ]

2018-10-30T12:19:26.254Z - debug: token:undefined, length:3, running total:3

2018-10-30T12:19:26.255Z - error: No VM found with hostname 192.168.0.102

2018-10-30T12:19:26.255Z - error: Error in getting VM: vm01.cpsi.local ,Error: [object Object]

2018-10-30T12:19:26.255Z - error: Failed to read the nodetype, Error: No VM found with hostname 192.168.0.102

2018-10-30T12:19:26.255Z - error: The source specified does not manage source VC, source host= vm01.cpsi.local ,error:[object Object]

2018-10-30T12:19:30.023Z - info: Log file was saved at: C:\Users\Francis\Downloads\installer-20181030-131745581.log

2018-10-30T12:20:02.030Z - debug: Source Host IP address in DOM input value is: 192.168.0.106

2018-10-30T12:20:02.030Z - debug: Source Host IP Value in data model is: 192.168.0.106

2018-10-30T12:20:02.031Z - debug: Source Host IP Value in data model after correction is: 192.168.0.106

2018-10-30T12:20:02.136Z - info: THUMBPRINT(vCenterAppliance): 09:5D:E2:F8:54:DC:46:1D:9A:A6:3A:29:A3:8D:4C:13:EF:7B:B4:3A

2018-10-30T12:20:02.158Z - info: THUMBPRINT(esxiHost): 9C:3E:A7:ED:C9:07:8A:EE:DF:A4:99:CD:96:15:46:A7:D7:92:14:E2

2018-10-30T12:20:03.083Z - info: attemptHttpsConnToSourceVc

2018-10-30T12:20:03.121Z - info: login() to source VC:192.168.0.102

2018-10-30T12:20:03.122Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:20:03.942Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:20:03.963Z - debug: session exists: 192.168.0.102, administrator@vsphere.local, 52308adf-a7b8-5e27-423e-988546287009

2018-10-30T12:20:03.979Z - info: successfully logged out from 192.168.0.102, administrator@vsphere.local, 52308adf-a7b8-5e27-423e-988546287009

2018-10-30T12:20:03.979Z - info: initializing vsphere API connection to 192.168.0.102:443

2018-10-30T12:20:04.030Z - info: vimService apiType: VirtualCenter, version: 6.5.0

2018-10-30T12:20:04.030Z - debug: Logging in to 192.168.0.102:443 as administrator@vsphere.local

2018-10-30T12:20:04.135Z - info: Logged in to 192.168.0.102:443 as administrator@vsphere.local, session: 5288c16a-5e21-7905-26cc-f9b0424b5a11

2018-10-30T12:20:04.136Z - info: Login successful to source VC, IP: 192.168.0.102

2018-10-30T12:20:04.136Z - info: login() to host managing the source VC:192.168.0.106

2018-10-30T12:20:04.137Z - info: initializing vsphere API connection to 192.168.0.106:443

2018-10-30T12:20:05.021Z - info: vimService apiType: HostAgent, version: 6.5.0

2018-10-30T12:20:05.077Z - debug: session does not exist: 192.168.0.106, root

2018-10-30T12:20:05.077Z - debug: Logging in to 192.168.0.106:443 as root

2018-10-30T12:20:05.160Z - info: Logged in to 192.168.0.106:443 as root, session: 52a61557-5c65-44a6-fa15-99b77b4fb0b8

2018-10-30T12:20:05.161Z - info: Login successful to host for source VC, IP: 192.168.0.106:443

2018-10-30T12:20:05.161Z - info: sourceVcService: Source VC Version=6.5, minVersion=6, maxVersion=6.7

2018-10-30T12:20:05.161Z - info: Source VC, version: 6.5.0, isOSLinux: true

2018-10-30T12:20:05.161Z - debug: isIp: 192.168.0.102: true

2018-10-30T12:20:05.161Z - debug: getVmWithIPFQDN: hostName 192.168.0.102 is associated with [ '192.168.0.102' ]

2018-10-30T12:20:05.208Z - debug: token:undefined, length:3, running total:3

2018-10-30T12:20:05.208Z - error: No VM found with hostname 192.168.0.102

2018-10-30T12:20:05.208Z - error: Error in getting VM: 192.168.0.106 ,Error: [object Object]

2018-10-30T12:20:05.208Z - error: Failed to read the nodetype, Error: No VM found with hostname 192.168.0.102

2018-10-30T12:20:05.208Z - error: The source specified does not manage source VC, source host= 192.168.0.106 ,error:[object Object]

2018-10-30T12:20:44.605Z - info: Log file was saved at: C:\Users\Francis\Downloads\installer-20181030-131745581.log

Muchas gracias.

Tags (1)
0 Kudos
3 Replies
diegodco31
Leadership
Leadership

Hi

It seems to be a problem with the root password.

What is vcenter version of source?

Diego Oliveira
LinkedIn: http://www.linkedin.com/in/dcodiego
0 Kudos
blackflamenco
Contributor
Contributor

Hola Diego,

La contraseña del root del vCenter y el ESXi estan correctas.

La version de vCenter es 6.5 Update1.

Gracias.

0 Kudos
e_espinel
Virtuoso
Virtuoso

Saludos.

Adjunto links que te podrian orientar.

Step-by-Step: Upgrading to VCSA 6.7 -- Virtualization Review

https://patriciocerda.com/vsphere-6-7-novedades-vcenter-server/

Enrique Espinel
Senior Technical Support on IBM, Lenovo, Veeam Backup and VMware vSphere.
VSP-SV, VTSP-SV, VTSP-HCI, VTSP
Please mark my comment as Correct Answer or assign Kudos if my answer was helpful to you, Thank you.
Пожалуйста, отметьте мой комментарий как Правильный ответ или поставьте Кудо, если мой ответ был вам полезен, Спасибо.
0 Kudos