Cloning of the vCenter

I realize that my question may seem strange.

Before udating a vCenter I want to test in a lab environment, just to see what is happening and to get answers to any questions.

So my idea is cloning the current vCenter, reconfigure the cloned vCenterso that it is not connect with any node ESXi, turn the cloned vCenter and launch the update of the Conference on disarmament.

Once familiar with the procedure I'll fill it out on the real vCenter.

Is there a problem to consider before attempting to clone my vCenter?

Can I cause any problem to my vSphere infrastructure while attempring to clone the vCenter?

Should I rather restore from a backup?

Concerning

Marius

You can make the clone of the vCenter, but when isolate you it, it will connect to the database in the case of external vCenter service will not start.

You can update the vCenter server but how you will test the vCenter update?

Kind regards

Vijay.NB

Tags: VMware

Similar Questions

  • How to configure the agent to monitor performance only the vcenter vmware and esx, not need to monitor virtual machines

    How to configure the agent to monitor performance only the vcenter vmware and esx, not need to monitor virtual machines

    This is not possible with the way in which we collect information.

  • ESXi hosts are disconnected from the vCenter (5.5)

    Hi all

    We have a little problem with our vCenter.

    We have two hosts that are connected to the vCenter, unfortunately, they are listed as disconnected.

    It seems that the problem are the SSL certificates on ESXi hosts that are no longer valid.

    If I replace the old certificates with new ones, that I have to restart the ESXi host, am I right?

    If so, that's the problem.

    We do not use any what automatic vMotion and as long as the hosts are not connected to the vCenter I can't manually, move right?

    Is it possible to connect hosts to vCenter without SSL?

    Sorry for my bad English, I'm not a native speaker.

    See you soon,.

    Johannes

    You need to replace the ESXi host SSL certificates.

    See the Docs for the replacement of ESXi Cert below.

    ttp://www.BlueBox-Web.com/2013/04/18/replace-ESXi-certificate/

    Documentation Centre of vSphere 5.5

    I had regenerate the ESXi 5.5 SSL certificates, which I did without any stop to virtual machines.

    Certificate replacement process can change based on the esxi version.

    According to the Doc, vSphere 6.0 Documentation Centre ESXi6 host must be rebooted to replace certificates.

    Anyway, in current state disconnected, you can try to regenerate the self signed SSL certs, restart management agents and try to reconnect host in vCenter.

    Thank you

    Hentzien

  • vCenter install fails when you try to install the vcenter Server to the node of the PSC in HA mode

    Hi all

    We have two controllers on duty platform build in HA mode. We are trying to install the vCenter server and we get the error message below.

    VCSCAValidateRemoteSSO: Unable to retrieve the remote SSO version: 12029

    2016-03-30 17:07:16.656 + 11:00 | vcsInstUtil-2656758 | I: PitCA_MessageBox: Displays the message: "Setup VMware vCenter Server could not verify that the distance vCenter Single Sign-On Server is version 6.0.0 or later. Check if the Server Single Sign-On remote vCenter is accessible and is version 6.0.0 or later. »

    Has anyone in the community runs vcenter server 6 HA with PSC inspectors sitting behind the f5 load balancer? Please share your thoughts if you have seen a similar problem.

    Thank you.

    Hi all

    We are able to go beyond the question of the installation. We did the capture of packets on both ends and discover that the reset was issued the installer by the licensing vCenter service running on the PSC.

    We have also created firewall rules more 18 altogether since the server vcenter for our f5 load balancing program, then 6 VIP of the F5 on the two controllers on duty Platform.

    I hope this helps other people who sought to install PSC in HA mode.

  • ESXi host running 6 VCSA disconnected from the vCenter

    Hi guys,.

    I have a weird problem with my vCenter build 6. Single cluster of ESXi hosts. Running VCSA 6.0 and 6.0 ESXI. Making a storage of the vCenter vMotion initially got stuck at 77% and the ESXi host running the disconnected from vCenter vCenter. But I can connect directly to the ESXi host with vsphere client and see the vCenter VM works perfectly well. If I try to manually connect host ESXi and vCenter, I get the error "Failed to contact the host specified") both are in the same subnet and VLAN. I can migrate to other virtual machines without problem. I even restarted the host and yet I am not able to connect to vCenter. The host connects to vCenter if I reboot vCenter, but after a few minutes, disconnects again (even if no task does run on this topic.) I have no HA or DRS enabled at this point that I build this new environment and only presented a single LUN as a store of test data to the cluster.

    Any ideas?

    OK, I think I fixed that or have at least a work around. So the underlying question was hiding ID mode/CPU EVC. I'm under the cluster to a level of EVC to reduce until I have migrate workloads from old environment and I think that this created a problem for the unit vCenter. To resolve this problem, I turned off the unit, directly connected to the ESXi host that had the camera running, edited the virtual machine and reset the masking of CPUID. Also, I've hidden the flag NX/XD of the guest. It's temporary (I hope) as once I increase the EVC to the Haswell, I will expose the NX/XD comments and test. For the moment, it is of the workaround I did. It may be of some use to someone.

  • The vCenter 5.5 to 6.0 upgrade, which can be bad...?

    Hello

    I am trying to upgrade our server vCenter version 5.5 to 6.0, but this is a boxing match, and so far the vCenter Server won I'm afraid...

    The problem is that I get an error when you install saying: "unable to install the servie collector syslog", and list a few files, then an error saying "Installtion of the component VCSServiceManager failed with error 1603" code.

    Our implementation: Windows server 2008 R2, all services of vcenter, including sql is on the same server. Only a vcenter server as well.

    I have read a lot about this kind of problem and tested a few things, but have not yet found any solution.

    Things I have tryied:

    • The time is the same on the vcenter server as on the rest of the field.
    • Windows install the value automatic and started
    • The ODBC can communicate with sql and leak white spaceat the end of the name
    • An IPv4 address is set and no IP address conflict.
    • The user to make the upgrade a sysadmin on the database.
    • Tryied with a fully patched Server
    • TCP/IP and named pipes are enabled in the configuration of sql

    What can we check? What could be the problem here?

    Thanks in advance! See attachment on the error

    Problem is now solved.

    Read today that vmware has released a new version, the vcenter 6.0 Update 1, build 3040890. After a score tie to install that instead of build 2656757 it worked like a charm. No error and no warings, everything rolls.

  • ESXi 5.5 build 2456374 is unable to reconnect to the vcenter after reboot

    Hello

    Have been hitting my head against it for the past few weeks. A host that has worked very well to a previous 5.5 build fails to reconnect to the vcenter after reboot once upgraded to build the 2456374. This also happens to the newly built guest. When a reconnection is started manually, it produces up to 80% (data of the host processing), then dies with a "general system error: internal error. I tried to remove the vpxa account, resetting the config network via the console, Cup NIC of the vswitch, removal of additional interfaces vkernel. The network via the console configuration reset allows me to reconfigure the net and tie vcenter and complete the host host configuration. However, as soon as I restart the host, is no longer, it reconnects to vcenter and I'm back where I started.

    Unfortunately, this is not a 100% event. If I rebuild a host enough times, one of the new buildings will finally works correctly.

    any ideas on how to solve this problem would be appreciated.

    Elmārs

    QUESTION REOLVED!

    Ok. so that was the easy part. Open a folder with vmware to identify the cause for this. After much digging, friction, pull hair, we found a clue in the hostd.log on the ESXi host.

    2015-04 - T 02, 04: 49:05.481Z [23381 B 70 error 'Hostsvc.NetworkProvider' user opID=HB-host-185064@917-1d029f4d-d2 = vpxuser] an error occurred during extraction of stack instance configuration: incompatible value of ccalgo for the Netstack instance: defaultTcpipStack.

    In my network performance test I did recently, I have significantly improved network iSCSI performance from the cubes NewReno network congestion control algorithm. For each of these hosts, as part of the installation procedure I now set the control algorithm of congestion on cube through the web interface. Finally, it is a little bug with that VMware believed fixed. Is not.

    To confirm doubling you encounter this problem, connect to the host (ssh or remote cli) and run the following command:

    list of esxcli ip network netstack

    You should get a message saying that there is an inconsistency in the netstack configuration.

    To fix, run the following command:

    esxcli network ip put netstack defaultTcpipStack cubic n - c

    the netstack from above list command should now display detailed information and will now be able to connect to vcenter.

    If I understand correctly, an article will be published on this in the near future.

  • Cannot connect to the vcenter until 10 minutes after the vcenter server computer starts

    I get the unable to connect to remote server message in vsphere client when I try to connect the server vcenter. However if I wait more than 10 minutes, I can properly connect to the vcenter server.

    Is there something wrong with it?

    And I wonder if the competent services to process the requests of connection on the vcenter server are not started immediately from the start?

    Where is installed your database? On the same box of vCenter server? If so, change the other boot option that delayed may not work because your vCenter will try to start before the database is online.

  • Is there a way to get the list of hosts and its groups of belonging to the vCenter folder level in 5.5 web vsphere client plugin development?

    Hello

    I need to get the list of all hosts and its groups of belonging to the vcenter folder level.

    1. I created a view giving the extension point: vsphere.core.folder.monitorViews.

    2. After this step, I wrote the constraint as in my class of mediator,

    var ListConstraint:Constraint =

    QuerySpecUtil.createConstraintForRelationship ( _contextObject, 'childEntity');

    I was expecting a list of all child entities such as hosts, dc, cluster... But I have only the immediate child object which is only the Datacenter as my result.

    Is it possible to get all hosts and vCenter folder level Clusters because I need the entire list to vCenter (highest level).

    Other info:

    Object file has only two properties:

    1 childEntity - list of entities

    2 childType in-kind folder ('Virtual Machine', 'Data center'...)

    Is it possible to write a constraint specifying which list of childEntities I need using childType in.

    Example: Make Me childEntities that has a 'Host' and 'Cluster' childType but childType in doesn't have these two types.

    In addition, at this level, I could see the 'Associated objects' tab which has all the information I need, such as Clusters and Cluster tab hosts and host tab respectively.

    So, I think its possible to get this list to vCenter folder level.

    I have attached a screenshot representing the need. Kindly ignore the Conventions of naming in there since I edited the example comes with the sdk program.


    Query:

    1. How can I get the host and Cluster (table of relationship) list to vCenter folder level or even at the level of the vise.global.view?

    2. once I get this list, is it possible for me to manipulate that list and send the new list to IU?

    3. is there another way to do the same thing without the help of model classes and mediator?


    Pointers to this will be very useful.

    It is not possible to obtain all hosts a folder specific vCenter from a single query Data Manager.  You need to get the list of centers of data first and then get a list of data center hosts.

    It is best to make these repeated requests to the java level and return only the list that you want to the user interface.

    You can get all the objects in the host of the system with a simple query using a constraint with targetType = 'HostSystem', but you will need to eliminate those from other vCenter servers.  See how this chassis example queries all hosts the Java later in the getHosts() method: samples/chassis-app/chassisRackVSphere-service/src/main/java/com/vmware/samples/chassisRackVSphere/ChassisRackVSphereDataAdapter.java

    Another option is to use the vSphere Web Services SDK to browse vCenter. See the vSphere management forum for help on these APIs.  See this plugin of the sample using this SDK

    samples/vsphereviews/vsphere-wssdk-provider/src/main/java/com/vmware/samples/wssdkprovider/VmDataProviderImpl.java

  • Move the vCenter to another cluster... How?

    We rotate the camera 5.5.0 vcenter and need to move from a cluster with ESX 4.1.0 hosts in a cluster hosts ESXi 5.5.0.  Two clusters are in the same data center, but no space for common storage.

    We have migrated all the old cluster to the new VM using vMotion.  It is now time for the vCenter himself.

    How should I go about this?  Some downtime for vCenter is probably inevitable.

    Thank you... Lyle

    With the help of Support, here's what I did:

    -a clone of the vCenter VM for the cluster target & storage, but do not start the new virtual machine

    -change the properties for the new virtual machine so its MAC address is the same as the old VM

    -stop vCenter with its interface web admin

    -with vSphere client connected to the source host, stop the guest OS (suse) of the former VM

    -with customer vSpere connected to the destination host, turning on the new virtual machine

    Thanks to all for the comments... Lyle

  • Integration of VCAC of existing scripts of VCENTER in "Manager of customization in the VCENTER client specifications.

    I have existing templates that I use to create plans, now I have not found the client is wanting to use the custom scripts that exist in the VCenter-> Home-> "customization specifications Manager.

    How can I incorporate these scripts in the VCAC action plan?

    ' Copy the name of the specification of the personalization of vCenter and paste in ' Cutomization Spec ' on the tab 'Build '.

  • Locking ESXi 4.1 mode access confirmation no access to the vCenter Server

    Hello

    ESXi 4.1.  I see options in conflict with access to a crowd that had lockdown normal mode activated via a server vCenter VM on a host in the cluster.  The vCenter server that sits on one of the hosts in the cluster lockeddown then became inaccessible or unresponsive connectivity wise.  So no connectivity between vCenter VM or VM vCenter and hosts.  Is someone can confirm if you can connect to this host lockedown by DCUI with root and disable lockdown configuration to allow the vSphere client to then connect to the host with root and troubleshoot the server vCenter VM?

    I read in some messages that this is only possible if the vCenter VM is in place and the communication to the host.  I also read that it is possible no matter what the State of the vCenter server once Total lockdown (disabling DCUI) is not enabled.

    I have this reference of the 'The new lock in ESXi 4.1 Mode' blog http://blogs.vmware.com/vsphere/2010/09/the-new-lockdown-mode-in-esxi-41.html

    "With active locking Mode, the only direct access to the host that remains open is through the DCUI. This allows to perform administrative tasks limited outside vCenter Server, such as restarting the management agents and the display of the log files. In addition, you can also disable Mode of Lockdown since the DCUI. This can be useful if vCenter Server is down or unavailable, and you want to return to a direct management of the host. Normally, without locking Mode, any user to the Administrator role can open a session in the DCUI.  However, in lock Mode, the root password is necessary; no other user can connect.

    Can anyone confirm.

    Any other person who may not be sure these questions, I can confirm that with root credentials, you can connect to the host directly and disable the lock mode regardless of the availability of vCenter.  Only if the Total lock mode turned on, or should I say DCUI is disabled, then you have no choice but to go through vCenter or reinstall and reconfigure the network.  VM would be always available if local or have to be reassembled and re inventoried etc.

  • Cannot install the Vcenter for Esxi 5.5. Windows 7

    Hi Experts,

    When I run the simple setup, it stops when tried to install the SSO, the message "cannot install the single sign on, this package is not compatible with your processor,..." I'm running a Lenovo T430, the processor in an INTELCore I5 vPro.

    I installed the client vsphere without problems. And I know that in the other lenovo T430 people install the VCenter correctly. I am running Windows 7 Professional.

    Any idea or solution?

    Thank you very much friends!

    Jesus

    Center Server is supported only on 64-bit Windows server in operating systems (see VMware Compatibility Guide: search guest conductor /)

    André

  • 5.5 ESXi hosts disconnection of the vCenter 5.5.0b

    Good evening.  I recently deployed some new hosts HP BL465c G8 running the HP OEM install ESXi 5.5 (not the one just released 02/18) and the two hosts have been disconnect from vCenter four times in the past week.  I can sometimes connect to the host via ILO and restart the vCenter agent, but more often without having to start the host hard.  In addition, one of the VMFS5 content of the data store disappeared and the virtual machines residing on this data store have declined because the hosts could not find the configuration of the virtual machine files. Strangely enough, the data store showed spaced used and I could see all the directories within the CLI, but not vCenter client or Web-based Client.  I have two tickets to windows with VMware from HP support team, but I wanted to know if someone had a similar problem.  I'm tempted to rebuild with the latest OEM installation or rebuild as 5.1 or 5.0 if version 5.5 is not fully cooked.  Thank you.

    Scott

    The issue proved to be the OEM HP install and specifically the pilot v1.1.7 for HBA QMH2572 adapters that it contains.  We have rebuilt our 5.5 ESXi hosts using installation OEM HP published 02/14 (contains recommendations
    v1.1.12 pilot) and that solved the problem of stability.

    Scott

  • Isolate the vCenter and management host ESXi5.1 of LAN traffic

    I would add two Dell switches to an existing installation, create a private management network (192.168.x.x subnet) containing the hosts and vCenter server, so that the management traffic is isolated and in no way dependent on connectivity LAN... for now that the vCenter server and the hosts are on the local network using public IP addresses.

    Is this possible with vCenter as vCenter that one IP can be configured and how should we switch be configured to allow access to vCenter from the local network via the web and customer management interface vSphere.

    Thank you very much

    Gary

    Facing your audience of LAN?  I think it depends a little bit of what looks like your LAN.  I don't think - you need not NAT your management network.  If you simply use public IPs rather than private to your internal LAN, the answer is no.  I have a client who does this same thing using 191.x.x.x for its internal network.  You try to access your network over the Internet?  It would be a different matter, and I recommend that to consult a competent network engineer.

    In short, just because you go to a public IP address range a private range of IP addresses does not mean you need to NAT.  You see NAT several times when these IP address ranges are used because they are intended.  For example, a company has a single public IP address assigned.  It uses private in its local network IP addresses.  For devices that must leave the LAN and access the Internet, you would NAT because everyone has to share this single public IP.

    Without knowing a little more, I think you'd be fine with the standard range or switching (inter - VLAN routing layer 3).

    All the best,

    Mike

    -----------------------------------------

    Remember to mark this reply 'proper' or 'useful', if you found it useful.

    Mike Brown

    NetApp, VMware and Cisco data center guy

    Consultant engineer

    [email protected]

    Twitter: @VirtuallyMikeB

    Blog: http://VirtuallyMikeBrown.com

    LinkedIn: http://LinkedIn.com/in/michaelbbrown

Maybe you are looking for