VCenter vmotion error cross

I tested successfully a script powerCLI for cross vCenter vmotion with two vCenters on the same domain of SINGLE sign-on, but I'm unable to operate with two vCenter servers that are not on the same domain of SINGLE sign-on.  The error "a specified parameter is not correct: ServiceLocator.instanceUuid.

The hosts and vCenter servers running version 6.0.  The source that VC is running on windows and the remote works the linux device.  The script starts the task successfully, but the task fails immediately.  What log files should I look for more information or a stack trace?

The original source of the script was written by William Lam (thanks!)

(param

[parameter] $vm_name.

[parameter] $source_cluster.

[parameter] $source_vcenter.

[parameter] $target_cluster.

[parameter] $target_vcenter.

[parameter] $target_storage_pod.

[parameter] $pools_to_move.

[parameter] $folder

)

$sc_test_thumb = "XX".

$thumbprint = $sc_test_thumb

$source_vc = to connect-viserver $source_vcenter

$source_cl = get-cluster-server $source_vc-name $source_cluster

$source_pool = get-resourcepool-Server $source_vc-name $pools_to_move

$target_vc = to connect-viserver $target_vcenter

$target_cl = get-cluster-server $target_vc-name $target_cluster

$target_hosts = get-vmhost-Server $target_vc-location $target_cl

$target_pool = get-resourcepool-Server $target_vc-location $target_cl-name $pools_to_move

$target_datastores = get-data-server store $target_vc-location $target_storage_pod

$vm = get-vm-Server $source_vc-name $vm_name-location $source_pool

$destFolder = get-file-server $target_vc-name $folder

$rspec = new-Object VMware.Vim.VirtualMachineRelocateSpec

$rspec.folder = $destFolder.id

$rspec.datastore =.extensiondata.moref $target_datastores [0]

$rspec.host =.extensiondata.moref $target_hosts [0]

$rspec.pool = $target_pool.extensiondata.moref

# New Locator service required for vCenter Server Destination when do not part of the same domain SSO

$service = new-Object VMware.Vim.ServiceLocator

$credential = new-Object VMware.Vim.ServiceLocatorNamePassword

$credential.username = (get-VICredentialStoreItem-host $target_vcenter) .user

$credential.password = (get-VICredentialStoreItem-host $target_vcenter) .password

$service.credential = $credential

$service. InstanceUuid = $target_vc. InstanceUuid

$service.sslThumbprint = $thumbprint

$service.url = ("https://"+ $target_vcenter)

$rspec.service = $service

$rspec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] ($vm.networkadapters.count)

$devices = $vm.extensiondata.Config.Hardware.Device

$i = 0

{foreach ($device to $devices)

If ($device - is [VMware.Vim.VirtualEthernetCard]) {}

$rspec.deviceChange [$i] = new-Object VMware.Vim.VirtualDeviceConfigSpec

$rspec.deviceChange [$i]. Operation = "├editer."

$rspec.deviceChange [$i]. Device = $device

$nic = get-networkadapter - vm $vm - name $device. DeviceInfo.label

$destPG = get-vdportgroup-Server $target_vc-name $nic.networkname

$dvSwitchUuid = (get-View-Server $Id target_vc $destPG.extensiondata.Config.DistributedVirtualSwitch). Summary.Uuid

$rspec.deviceChange [$i]. Device.Backing = New-Object VMware.Vim.VirtualEthernetCardDistributedVirtualPortBackingInfo

$rspec.deviceChange [$i]. Device.Backing.Port = New-Object VMware.Vim.DistributedVirtualSwitchPortConnection

$rspec.deviceChange [$i]. Device.Backing.Port.PortgroupKey = $destPG.key

$rspec.deviceChange [$i]. Device.Backing.Port.SwitchUuid = $dvSwitchUuid

$i ++

}

}

Write-Host "' nMigrating $vm of $source_vc at $target_vc...". ' n »

Question # Cross VC-vMotion

$task = $vm.extensiondata.RelocateVM_Task ($rspec, "defaultPriority")

Disconnect-VIServer $source_vc - force - confirm: $false

Disconnect-VIServer $target_vc - force - confirm: $false

return $task

I found an error in the log vpxd.  The instanceUuid must be converted to upper case before he packed.

Fixed this line:

$service. InstanceUuid = $target_vc. InstanceUuid.toUpper)

Thanks LucD!

Tags: VMware

Similar Questions

  • Long distance vmotion and cross-vcenter vmotion are incompatible, with MRS?

    We plan our updates of 5.5 to 6.0. Two sites have involved SRM. We would like to be able to deploy to make long distance and cross-vCenter vMotion possible in the future. However it seems that these may be incompatible with MRS.

    Cross-vCenter vMotion requires enhanced link mode. Improved link mode requires the vCenters using the same PSC. A dependency between the protected site and recovery site that would be created by putting the two SRM vCenters in bound mode is a non-starter. You must be able to connect to your vCenter site recovery if the protected site is swept away by a tornado.

    The answer is maybe; Cross-vCenter vMotion is not compatible with SRM unless you create the deployment model with PSC servers redundant load balancing. Locate a CFP that is geographically separated from the protected site. Even in this scenario, it is clear to me if you would have to re-pointer the vCenter site disaster recovery. Again, I think that increased vMotion requires literally the 2 vCenters to be directed to the * same * PSC, CSP not only in the same SSO domain.

    I have a box to open with VMware and I'll share the results if it is useful. The two protected site site and recovery use our company Active Directory as an identity source, but I don't think it will help us if we are in bound mode and lose a PSC.

    Well, the weakness of my logic is in bound mode extended vCenters must point to the * same * PSC.  At least in SRM 6.1 there is some good news here.

    Thank you Federal VMware supported;

    Site Recovery Manager 6.1 Documentation Center

  • VMotion error: host vmware cpu is not compatible with the requirements of the judgment of the VM to CPUID level register 0 x 1 'ecx '.

    Problem: I can't move my Exchange vmserver2 a vmserver1 server.

    Error: "host vmware cpu is not compatible with the requirements of the judgment of the VM to CPUID level register 0 x 1"ecx"


    Details:

    Vmware KB:

    * Ensure that the hosts have the same features enabled in the BIOS of the servers. If there is an incompatibility between the servers BIOS configuration even if they are physically identical, they always show a compatibility error message. The two most common to check features are the No-Execute memory Protection (NX / XD) and virtualization technology (VT / AMD - V).

    A ran the CPU utility Vmware as referenced by

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003718


    "CPU that have similar features. "This means that the need of processors from the same manufacturer (AMD or Intel), be of the same family (Pentium, Xeon, etc.), and have common features extended between ESX servers involved in the VMotion.

    My results:

    vmserver1 Dell Inc.    PowerEdge 2950 2 Intel Xeon E5405 of CPU @ 2.00GHz
    vmserver2 Dell Inc.    PowerEdge 2950 2 Intel Xeon L5410 of CPU @ 2.33 GHz

    They both share exactly the same characteristics:
    FT support
    Enable VT
    VT Capable
    NX/XD
    FFXSR
    RDTSCP
    SSE
    SSE2
    SSE3

    Support Relaxations:
    NX/XD
    RDTSCP

    Relaxations unsupported:
    All THE features of the SSE
    FFXSR
    CMPXCHG18B

    In the 'Show Windows debug' it reads 'of the compatible CPU"

    This virtual Exchange machine works since Esxi version 3.5.  I am testing now vCenter Server 5.0 with version 5.0.1 on the Esxi server.

    Note: I've also been meeting random uses CPU high, leading from Windows Server 2008 to lock up completely.  I have found no trace of problems within the Windows host and Vcenter is not questions.  I have "reset" of the virtual machine in order to get the server back online.  The CPU to the top lock is random and the server can run for days with no problems. * Don't know if it's related...

    Virtual host config Exchange computer:
    Guest operating system: MS Windows Server 2008 64 bit
    version 8 of virtual machine
    CPU: 4vCPU
    Memory: 10240MB
    Overload memory: 420,61 MB
    vSphere HA Protection: protected
    Host CPU consumed: the 209 MHz

    Maps: vmserver1 watch "CPU is not compatible" CPU: 0% (none of the virtual machine running)
    Consumed host memory: 9823,00 MB
    Active memory of Fords: 409,00 MB

    Views of storage: I have a warning symbol on the QNAP iSCSI disk that hosts the virtual Exchange computer but I see no record... I'm new here...

    I understand that vmotion apply restrictions on the movement of VM compatibility to avoid it.  The components of the HA does not apply to these requirements.  We tested yesterday HA, succsessfully and this how we came to be stuck with the Exchange vm on vmserver2 and it cannot migrate to vmserver1.

    I appreciate your time and consideration,
    Tim

    It seems that you have two different processor speeds. Try the VCA mode and also check the BIOS version you and make sure they match.

  • Add vCenter Workflow error: unexpected status code: 404

    Hello

    I am trying to add a vCenter vRO 7.0.1 host using the plugin existing VC (ver. 6.0.2.3435085) and I run a strange question.

    If I choose NO for the option ' will you orchestrate this instance "then the workflow completes successfully.  This does allow me to run workflows against the vCenter.

    When I remove the existing vCenter and re - run the workflow of vCenter Add, this time by choosing YES, the workflow fails with error validation process: unexpected status code: 404 (Workflow: Add a vCenter server instance / validate (item2) #1)

    Any ideas why check YES causes this?

    My entries:

    Host: fqdn.servername.com

    Port: 9443

    Path: /sdk

    Ignore the Cert: Yes

    Thank you.

    Hello

    This error probably means that the port number is incorrect.

    Are you sure 9443 is the correct port number? Usually, the port number is 443, not 9443 (port 9443 is where vSphere Web Client is available). Could you re-run the workflow with port 443?

  • VCenter converter error "host key < ip > cannot be found."

    Hello friends, how are you?

    I'm trying to convert a physical machine with Redhat 3 have the latest version of VMware vCenter Converter (5.5.3)

    On the machine with Redhat, I have disabled firewall, IP address as name solves well and are in the same network as the host.

    At one point, after target partition and format the disk on the server, I get the following error in the log:

    FAILURE: A general system error occurred:

    Network error. 192.168.0.142 host key cannot be recovered. (code 2 back)

    Can someone help me?

    Thank you very much!

    Solved friends, was a mine very stupid mistake!

    He put a different vm to support mask of the subnet of the vCenter.

    Everything solved!

  • vCenter Server: error 29102

    Hola a todos, estoy instalando vCenter in una Máquina virtual y me arroja el siguiente error:

    vCenter.jpg

    Tengo than tener wont vCenter Single Sign-On? If lo instalo no me toca nada of mi Active Directory? Porque vi some options del 'Site name' y UN number del dominio "vsphere.local." Quiero estar seguro that no me haga cambios in the mi dominio instalarlo antes infrastructure config.

    Saludos.

    Hola,

    If you have than instalarlo. In el propio Assistant tienes los clearly previos para cada parte of the instalacion del vCenter. Para instalar el vCenter antes tienes than tener wont como minimo el vCenter Single-Sign-On y el vCenter Inventory Service, sino los tienes obtienes pones el that error. SSO El none go you a touch el Active Directory, "simplemente" lo go a usar para autenticar users of dominio con los Sue al vCenter a traves del vSphere Client Access o del Web client vSphere. Dentro del SSO tienes than configurar UN identity Source aren't otra cosa that indicate UN dominio driver y unas credenciales validas en el Active Directory para that el SSO can see post of users. If esto no esta hecho o no podras works solo connect al vCenter con users local del propio Server vCenter. El dominio vsphere.local're a number FQDN el vCenter usa para sus users local solo y no tiene none Relación con el Active Directory.

    Para una correcta instala el todo instalacion software "of arriba abajo" where por el Single Sign - on is if todo el proceso goes well tendras el vCenter operating system.

    Kind regards

  • vCenter install error: Error 25003 Setup cannot create vCenter Server repository

    Hello

    I build vCenter server install 5.5.0U1C with the two server model where the instance a host DB and others welcome rest the vCenter Binaries.Below is the error that I got when running vCentererror.jpg

    I ran the query

    SELECT CASE WHEN 'A' = 'a' THEN 'NOT CASE SENSITIVE' ELSE 'CASE SENSITIVE' END


    I got back as "NOT case sensitive.


    But if I'm correct error it says precisely because of the failure as "the database is installed using insensitive case" that proves this query.


    I fell the Mode Case Insensitive mode case-sensitive mode by changing the ranking "SQL_Latin1_General_CP1_CS_AS'.


    I have this time received the error


    2.jpg


    I have no idea which has now gone wrong make install failed.


    BTW, the version of the Client on the remote DB server and application server are the same and I use MS SQL 2012 SP1 with windows 2008 R2 SP1 on windows OS both side.


    Please help me find the solution, I have really now clueless with the cause of it.



    Thanks in advance


    BR,


    MG

    Nevermind, I got this problem fixed by the server being destruction and reconstruction new virtual machine and install this on it.

  • Chargeback add vcenter SQL error

    Hello

    I'm trying to adds a server vCenter ChargeBack.

    I get the following error message:

    The invalid vCenter Server database. The vCenter Server database must have the following views: VPXV_HIST_STAT_DAILY, VPXV_HIST_STAT_WEEKLY, VPXV_HIST_STAT_MONTHLY and VPXV_HIST_STAT_YEARLY

    On this post, (https://communities.vmware.com/thread/236730) say that the sql account must be db_owner on the vCenter database, I have that and say that we create the views.

    In SQL management Studio, I see these views, but exactly. I have the same names, but like this: VMW. VPXV_HIST_STAT_DAILY, VMW. VPXV_HIST_STAT_WEEKLY...

    Is this normal?

    Best regards

    Hello

    I solved my problem.

    In fact, I changed the schema (in sql) for the user to sql dbo to MVW vCCM and I can add a vcenter.

  • vSphere SSL for the Web Client (device vCenter) certificate error

    Hello

    I installed ESXi 5.5 and right once I deployed the device vCenter. After the configuration and a few reboots, I navigates to the web client, and I get this error when I try to logon:

    "Based on the current configuration, the authentication server's SSL certificate was not reliable."

    I have until this google everything on the subject and outside tutorials on how to change certificates in the Windows version of vCenter, nothing on the device of vCenter. I was happy when I found the 'Certificate regeneration enabled' checkbox, but that did not help either. I can test successfully SSO settings in the control panel of vCenter.

    Everyone please?


    Edit: I should also mention that I am not able to connect to vCenter with the vSphere client. I get the "Cannot complete the connection by incorrect username or password". I use [email protected] as user name.

    Have you tried that? VMware KB: Troubleshooting the vCenter Server Appliance with Single Sign-On login

  • Update 5.1.0U1b to 5.5 vCenter fails (error 1603)

    I keep getting errors when trying to install vCenter 5.5 Single Sign-On which translates a restore.

    I tried with a Simple installation and custom installation.

    I tried already to remove the CIS folder and install Vmware-python in the requirements folder and check the value of FqdnIp in the registry.

    Check the log, I found the error 1603 in it.

    OS: Windows 2008 R2 SP1 Std.

    DB: MS SQL 2008 R2 SP2 Std.

    Thank you very much for your help!

    Hi Rapster,

    1. the journal indicates that the FqdnIp registry key has no value in this document, you would confirm please?

    HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc. \VMware Infrastructure\SSOServer\FqdnIp.

    Please also attached the certificate SSL SSO to see what value is there to object and subject ALT name

    2. If your SSO 5.1 was installed after joining a domain, it seems that Yes, based on the journal, for example, vc. SOFTWERK.local, then the registry should have value of

    VC. key FqdnIp SOFTWERK.local.

    Please check the following points if SSO 5.1 was installed with machine joined to a domain:

    1 FqdnIp registry key has a correct value of the domain COMPLETE (for example the vc. SOFTWERK.local)

    2. make sure SSO SSL certificate has same FQDN in object / subject Alt name

    3 If the CIS under %ProgramData%\VMware folder exists, delete or rename the folder CIS

    4. repeat the upgrade of SSO

    Thank you.

  • last upgrade vCenter device error

    Hi all!

    I'm trying to upgrade a vcenter 5.0.1 for 5.1.0 application. I use the oracle db

    If I followed the instructions (upgrade to VMware vCenter Server Appliance).

    When I choose "default sso config", I get an error 500 impossible to connect to the remote server: 10xxxxx

    If I don't use default values, I have to enter the DB connection. First test is with the db user sys to the dba.

    This resulted in an error "login as SYS should be as SYSDBA or SYSOPER.

    Then, the next thing: our dba has created a new user with sufficient privileges.

    Following error:

    [+ 2045] INFO | Database validation failed: BadTablespace - Tablespace RSA_DATA missing or not visible by the user.

    [+ 2048] INFO | Return code is: BadTablespace / 9

    [+ 2049] INFO | COMPLETED

    VC_CFG_RESULT = 720 (error: did not find the storage space required for the installation of the SSO.) Please, consult the installation and Configuration Manual on how to create spaces for storage.)

    It's not funny :-(

    Advice how to fix this?

    Thank you & see you soon

    Stefan

    On your oracle database, you will need to run these two files after appropriate change 'rsaIMSLiteOracleSetupTablespaces.sql' and 'rsaIMSLiteOracleSetupUsers.sql '.

    They are available on the iso image available for windows install under the single folder sign On\DBScripts\SSOServer\schema\oracle.

    I don't know if I'm allowed to join these files here in this forum.

    Concerning

    Girish

  • last upgrade vCenter %s error

    I try to do the upgrade to vCenter 4.1 vCenter 5 but it does not work. I have this error:

    Entries by the user DB has no required permissions to install and configure vCenter Server with DB selected. Please correct the mistakes of set-aside: %s

    I have all rights on my database, 'his', and _dbo seems to be accurate. Currently my vCenter works well, it's only the upgrade. What is the problem.

    It seems that you are hit with the same problem as in KB

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2006904

  • vCenter device error

    Hello

    everything by deploying the file ovf which giving an error like "ovf" is a namespace not declared. Line 1, position 2.

    I have attached error screenshot please help me about this error.

    As written the vCenter Server Appliance consists of 3 parts:

    • VMware vCenter Server 5.0 device - OVF file (file size: 8.1 K)
    • VMware vCenter Server 5.0 device - system disk (file size: 4. 0 g)
    • VMware vCenter Server 5.0 device - data disk (file size: 40 M)

    You can also check checksums to ensure that downloads are compatible.

    For downloads and see checksum:

    http://downloads.VMware.com/d/details/VC50/dHRAYnQldEBiZHAldw==

    To find out how check the seat of MD5 checksum:

    http://www.VMware.com/download/MD5.html

    André

  • Uninstalling vShield on ESX - vmotion error

    We tested trend deep security on our virtual machines for a few frames, and we want to uninstall it in our environment.

    What we see, is that we cannot vmotion virtual machine installed on an ESX Server with vShield endpoint that does not have vShield installed.

    In one of our cluster (5 guests), we where able to uninstall vShield on two hosts, but now we cannot uninstall the last three. We get an error on vmotion after 82%.

    We had the problem when we wanted to move the virtual machine from one cluster to another. We have solved it by installing vShield on the new cluster, and in this way we could vmotion virtual machine on.

    But now we want to first uninstall it complete, we are not able to uninstall the last three guests.

    Any ideas?

    Off the deep Trend Micro Security console virtual machine before trying to vmotion

    Otherwise, it is a limitation of vShield, you can only vMotion to another host vShield activated, see FAQ here:

    http://www.VMware.com/support/VShield/doc/faq_vshield_41.html

    If a virtual machine of comments is vMotioned to another ESX host, lost all dashboard application and endpoint security?

    No, security policies can suite of virtual machines as long as vMotion is configured to require that these policies migrate. vMotion moves a protected virtual machine is blocked if the target ESX is not enabled for the security solution. Make sure that the list of resources for vMotion of virtual machines protected contains security only enabled the ESX host.

  • During the restart of Vcenter Server - error 1053: the Service has not respond to the start or control

    Hi all

    I couldn't use the vSphere Client to enter in vCenter (from my office).

    I could not Remote Desktop on the server vCenter resides on.

    I could go on the console of the server vCenter resides on.     I couldn't use vSphere Client from there either.

    I tried rebooting vCenter and got this error message:

    Unable to stop the VMware VirtualCenter Server Service on Local computer.

    Error 1053: The service did not respond initially or control in a timely manner.

    Any ideas where to look for more clues or ideas on what might be the case?

    Thank you.

    I could not Remote Desktop on the server vCenter resides on.

    This is not vcenter Server.

    Check the configuration of Windows.

    Have you tried restarting your vCenter Server system?

    André

Maybe you are looking for